ID05180020_SSN-RFI_PWS_Draft.pdf

PERFORMANCE WORK STATEMENT (PWS)

Joint Airborne Intelligence, Surveillance, and Reconnaissance (AISR) Sensor Data Transport Infrastructure Enterprise Integration and Sustainment

GSA ID # ID05180020

3 May 2019

1. Background:

The Department of Defense (DoD) has a requirement for systems engineering, integration and sustainment for the envisioned DoD level Airborne Intelligence, Surveillance, and Reconnaissance (AISR) Data Transport Infrastructure--a global, joint infrastructure supporting the transport of manned and unmanned sensor data between assets and authorized strategic, operational, and tactical consumers. The initiative was jumpstarted by United States Special Operations Command (USSOCOM) with the long term intent of transitioning it to a DoD level entity. The anticipated performance work statement will detail the fielding, integration, and management of required enterprise AISR transport infrastructure systems, solutions, and equipment in order to provide 24/7 support of the global operations of existing USSOCOM and future DoD sensor data transport infrastructures.

The USSOCOM AISR Data Transport Infrastructure enables manned and unmanned platforms to communicate with operationally relevant consumers and intelligence analysts via Regional Ground Entry Points (RGEPs), through tactical sensor data backhaul systems, and across a combination of satellite and terrestrial transport solutions. The USSOCOM AISR Data Transport Infrastructure has been resourced, developed and deployed to support global Special Operations Forces (SOF) missions. However, as Service AISR assets, Quick Reaction Capabilities (QRCs), Government Owned Contractor Operated (GOCO), Contractor Owned Contractor Operated (COCO) and other AISR platforms entered the operational environment they have leveraged the global capabilities that USSOCOM’s AISR Data Transport Infrastructure provides. Therefore, the infrastructure exists in reality, not as a SOF unique solution, but as the precursor to a cohesive joint enterprise strategy supporting the larger DoD, to include USSOCOM, the Services, Combat Support Agencies (CSAs), and Geographic Combatant Commands (GCCs).

2. Scope of Work:

The Contractor(s) will have an understanding of the DOD sensor data transport infrastructures (to include but not limited to hardware, software, waveforms, satellites, terrestrial networks, and terminals) and the criticality of the missions supported. The AISR Data Transport Infrastructure is defined as the communications architecture connecting an AISR platform to an enterprise sensor data processing and/or distribution node to the intended consumers. This includes a combination of satellite communications (SATCOM) links, regional ground entry points and/or large satellite gateways, ground-based sensor data processing capabilities, terrestrial connectivity, and networking infrastructure necessary to provide management and monitoring for the sensor data transport infrastructure from end to end.

This scope of work includes all satellite processing and terrestrial networking equipment supporting sensor data transport for AISR assets through RGEPs, Defense Information Systems Agency (DISA) Large Satellite Gateways, the compatible ground terminal/node equipment, and required distribution to, with, and through the Unified Video Dissemination System (UVDS) for the intended recipient/authorized consumer.

The Government intends to manage this holistic support as three key elements supporting the overall AISR transport infrastructure: manned/unmanned downlink, ingest and processing;

terrestrial data transport; and the overarching program/project management and engineering necessary to manage and sustain the sensor data transport enterprise. These three key elements shall be maintained as needed under the respective, individual task orders.

3. Government Relationships:

3.1 Government Relationships: The efficient and effective conduct of this effort shall make it necessary for the Contractors to establish and maintain working relationships with a variety of Department of Defense Services and Agencies (Air Force, Army, Marine Corps, Navy, Joint Chiefs of Staff (JCS), National Security Agency (NSA), etc.), and other Government Departments and Agencies (e.g., DISA, National Geospatial Agency (NGA), etc.) with regard to information on architectures and other activities technically or operationally affecting the AISR Data Transport Infrastructure.

3.2 Contractor Relationships: The Contractors(s) are expected to coordinate, share, and openly communicate system information, and pertinent data as needed to manage the AISR data transport infrastructure. This may include the need for non-disclosure agreements to protect Contractor proprietary data rights if specifically authorized by the Government. The Contractors shall participate in meetings where the open exchange of viewpoints and ideas is common and expected in order to communicate technical issues and explore innovative solutions with elements of Governmental, scientific, and industrial communities, as appropriate and pertinent to agreed-upon tasks.

4. Enterprise Vision:

The Department’s Joint AISR Sensor Data Transport Infrastructure shall: remain secure, operationally effective, and as fiscally efficient as possible; be able to react flexibly and dynamically in response to pre-existing operations as well as surge in response to emerging operations on a global scale; and the data transported shall be accessible at the time, place, quantity, and quality dictated by tactical, operational, and strategic consumers. Geographical Combatant and Joint Commanders must be able to obtain accurate and timely situational awareness for ongoing operations in order to afford target engagement authority direction facilitating smarter and better-informed decisions at the tactical edge. In order to achieve these goals, the supported PEOs, PMOs, and SPOs, must have full and unabated insight into the three key elements of the data transport infrastructure architecture. While individual components may be Contractor specific solutions, the overall enterprise shall be managed as a system-of-systems--with unbiased information sharing. This information sharing shall be necessary to minimize duplication and maximize teaming where appropriate and avoid repeating missteps to the greatest extent possible.

The AISR Data Transport Infrastructure must provide the flexibility needed to support a wide-variety of assets, an ever-increasing number and diversity of sensors, and most importantly, afford “no fail” support for a leaner, more agile joint force.

To that end, the Contractor(s) selected shall provide comprehensive systems engineering and integration support to:

• Ensure information is available, discoverable, accessible, and understandable without regard to source, location, time, quality, and/or quantity;

• Assure transport infrastructure components are resilient, secure, and trusted;

• Limit access to sensor data and the transport infrastructure to only authorized consumers;

• Promote consistent risk management criteria across the Government for sensor data and the transport infrastructure;

• Implement flexible approaches for risk management to balance benefits and risks, against access and availability; and

• Ensure the data transport infrastructure, critical components, and capabilities are operated, secured, and defended in a synchronized manner to achieve mission success globally and across the wide spectrum of operations and supported consumers.

6. General Information:

6.1. The Contractor shall meet all requirements and responsibilities as outlined in this PWS.

All staff shall be fully trained, professional, and customer oriented and shall consistently provide responsive, flexible, and cost effective service. Quality work performance in accordance with applicable standards and guidelines shall be ensured. The Contractor(s) shall perform the standards of this PWS in an environmentally acceptable manner consistent with all Federal, State and local laws as well as applicable Instructions. The Government shall review and approve all Contractor resumes prior to commencement of work.

6.2.The Contractor shall furnish everything required to perform all services required by this PWS with the exception of those items or services specifically stated to be provided by the Government

6.3.The Contractor shall comply with all regulations listed in the below table.

Publication Number Title Date

6.4.Period of Performance: The period of performance is a five year ordering period. The Contractor shall honor all orders placed within the five year period.

6.5.Location of Work: The work to be performed under this PWS shall be performed at various Government sites and Contractor facilities—both Continental United States (CONUS) and Outside Continental United States (OCONUS). All Contractor(s) shall be expected to support integration and testing at Government designated systems integration and engineering labs and to actively engage and interface with the Government and other Contractor(s) supporting the AISR Data Transport Infrastructure.

7. Field Service Support and Travel:

7.1. The Contractor may be required to travel in support of the IDIQ Task Orders.

The Government may recommend Contractor travel to seminars, conferences, workshops, meetings, events or training that is Government unique or is necessary to maintain the requirements of the Task Order PWS. The Contractor shall obtain written approval from the Contracting Officer or TPOC prior to Contractor personnel incurring any travel expense. The Contractor shall identify personnel who shall be traveling and provide travel cost estimates to the Government 10 business days prior to departure but a minimum of 2 business days prior to departure when there are extenuating circumstances to the projected travel date. Contractor costs for travel will be reimbursed in accordance with FAR 31.205-46, in arrears. The travel costs shall be reasonable and allowable as defined in FAR 31.201 and in accordance with the limitations of the JTR/FTR/DSSR. Reimbursement shall only be authorized in support of Government-directed travel. Travel to other Government or civilian facilities outside the local area may be required. The Contractor shall invoice monthly on the basis of cost incurred. The Contractor must provide documentation in support of all travel expenses. The contactor shall not be reimbursed for local travel (within a 50-mile radius of the Government/Contractor’s facility) or commuter travel (commute from home to work site).

Commuter travel (recurring travel from an offeror’s location to the customer’s site) is not reimbursable. The Contractor shall follow all appropriate travel directives regarding cost and safety. Invoice submissions including travel costs shall include completed travel expense sheets (i.e., travel voucher) for each trip and each employee who traveled. The travel expense report, receipts of $75 or more (with exceptions being lodging and transportation), and supporting documentation (e.g., approval email for exceeding per diem rates, cost comparisons, etc.) shall be submitted with the invoice. Expense report(s) must include the traveler’s name, dates of travel, destination, purpose of travel, Approval Authority documentation (e.g., copy of the e-mail authorizing travel by Government official), and cost for each trip. All travel costs shall be compiled into the Government provided travel expense sheet (PWS Addendum I) or similar document that has been determined to be acceptable by the Government. The entire submission shall be complete and organized to enable the Government to complete an efficient review. Submissions that are not complete and organized are subject to rejection.

7.1.1. Joint Travel Regulation: The Contractor shall use the JTR and FTR for all applicable cost reimbursable travel actions.

7.1.2. Travel Advisories: The Contractor shall review State Department and other travel advisories prior to travel abroad.

7.1.3. Recruitment and retention incentives in accordance with the Department of State Standardized Regulations (DSSR) may be authorized for Contractors providing required support when in travel status. Danger Pay and Post (Hardship) Differential allowances for such travel shall be authorized in accordance with the DSSR. The allowances for such costs shall be identified separately. The allowance for a specific location, as determined by the Department of State Office of Allowances, shall be considered effective when the Contractor lands on the ground of such location (i.e. “wheels down”).

7.1.4. DBA Travel Insurance is required for all OCONUS travel.

7.1.5. Access to the Synchronized Pre-deployment and Operational Tracker (SPOT) is required to support overseas travel.

7.2.Travel may include but is not limited to: Support integration meetings, working groups, communities of interests, demonstrations, testing, and/or user evaluations. Use of teleconferencing and video teleconferencing is approved and recommended to reduce travel cost.

7.3.Support may include Field Support Representative (FSR) as well as related program management and deployment readiness activities for various locations (TBD). The following are assumed during Contractor deployment to deployed locations to NON-hazard zones.

TBD

7.4.In the event the Contractor is required to travel to State Department identified Hazard Zones, the Government shall assist in providing documents included but not limited to LOA’s bases access, and security/badging requirements.

7.5.Trip Reports: For all long distance travel, the Contractor shall submit Trip Reports five working days after completion of a trip. The Trip Report shall include the following information:

• Personnel traveled

• Dates of travel

• Destination(s)

• Purpose of Trip; Task objective supported; GCC supported (if applicable);

training (be specific)

• Actual Trip Costs

• Approval Authority (Copy of the e-mail authorizing travel by technical POC)

• Summary of trip events and accomplishments

The Contractor shall reconcile the Trip Reports with each invoice such that they can be matched month by month. Trip reports shall be submitted in GSA’s ITSS contracting system and sent to the technical POC.

8. Quality Assurance: Inspections shall be conducted in accordance with the contract terms and conditions with unacceptable or unsatisfactory work being addressed as outlined therein.

Services shall be monitored for contract compliance on an ongoing basis as designated in the Quality Assurance Surveillance Plan (QASP).

9. Information Assurance: Any equipment provided by the Contractor shall include the ability for the equipment to meet all IA requirements as requested by the certification and accreditation Approving Official and to obtain an Authorization to Operate (ATO)/Authority to Connect (ATC) prior to the new equipment’s installation. The Contractor shall verify the system meets the security requirements defined in the DoD 8510 application manual and that the design includes items on the Approved Products List (APL) for general use by the DoD. Additionally, the lead Contractor shall support IA management and risk reduction activities, as requested, to maintain compliance with DoD Cybersecurity and risk/vulnerability management guidance. This includes establishing and implementing security policies, procedures and controls that are compliant with DoD and agency specific Directives and Policy including but not limited to DoD Directive 8500.1 Cybersecurity, DoDI 8510.01 Risk Management Framework (RMF) for DoD Information Technology; Assured Compliance Assessment Solution (ACAS); etc on a task order by task order basis.

10. Quality Control Plan (QCP):

The Contractor(s) shall establish and maintain a complete QCP to ensure the requirements of this task order are provided as specified in accordance with the applicable Inspection clause (52.246- 4 Inspection of Services—Fixed-Price and 52.246-6 Inspection—Time-and-Material and Labor- Hour). The Contracting Officer shall notify the Contractor of acceptance or required modifications to the plan. The Contractor(s) shall make appropriate modifications (at no additional costs to the Government) and obtain acceptance of the plan by the Contracting Officer. The Government has the right to require revisions of the QCP (at no cost to the Government) should the plan fail to control the quality of the services provided at any time during the task order performance. The plan shall include, but is not limited to the following:

• A description of the inspection system covering all services listed.

• The specification of inspection frequency.

• The title of the individual(s) who shall perform the inspection and their organizational placement.

• A description of the methods for identifying, correcting, and preventing defects in the quality of service performed before the level becomes unacceptable.

On-site records of all inspections conducted by the Contractor(s) are required. The format of the inspection record shall include, but is not limited to, the following:

• Date, time, and location of the inspection.

• A signature block for the person who performed the inspection.

• Rating of acceptable or unacceptable.

• Area designated for deficiencies noted and corrective action taken.

• Total number of inspections.

10. Security Requirements: Security shall be in accordance with the attached DD254.

Contractor team individual(s) supporting this task shall be cleared at the TOP SECRET level at the start of the task. At the discretion of the Government, selected individuals supporting certain task orders shall require access to Special Access Program (SAP) information.

Access to SAP information requires the requisite security clearance based on a security investigation with a date less than 5 years old and requires employees to undergo additional personnel security screening meeting the DoD SAP-accessing directives and policies.

Contractors shall require access to COMSEC, SCI, NATO, Foreign Government Information and ACCM material in performance of this effort. Contractor shall require access to NIPRNET/SIPRNET computer systems at Government facilities and at the Contractor facility. JWICS computer system access is restricted to Government facilities. Select Contractors shall require the use of Commercial Solutions for Classified (CSfC) Mobile Devices. Contractor shall be authorized to courier classified information up to Secret in performance of official duties upon approval of and designation by the COR.

Contractors requiring the use of the CSfC Mobile Devices for use outside of secure Government and/or Contractor facilities shall submit a USSOCOM IMT 33, CSfC Device

User Agreement and Hand Receipt, and Director, Headquarters (HQ) Directorate/Special Staff endorsed Authorization of Issuance Memorandum to HQ USSOCOM Industrial Security. As acknowledged on the Use Agreement, Contractor shall ensure safeguarding measures are adhered to and necessary privacy is available to eliminate the possibility of compromise of classified information. Any misuse of the device outside of mission purposes or security incidents associated with or involving the device, may result in Contractor's termination of access or subject the Contractor to appropriate disciplinary or criminal action.

The Contractor(s) shall ensure requirements for safeguarding classified information and classified materials, for obtaining and verifying personnel security clearances, for verifying security clearances and indoctrination of visitors, for controlling access to restricted areas, for protecting Government property, and for the security of automated and non-automated management information systems and data are fulfilled. The Contractor(s)’ management system shall prevent unauthorized disclosure of classified and sensitive unclassified information. The Government shall be immediately notified of any security incident or any indication of a potential unauthorized disclosure or compromise of classified or sensitive unclassified information.

The Contractor(s) shall provide security management support. Typical efforts include, but are not limited to, performing classified document control functions, classified materials inventories, program access requests, preparing and monitoring personnel indoctrination and debriefing agreements, and maintaining and using security-related databases.

11. Physical and Information Security: The Contractor(s) shall administer and comply with physical security programs for facilities and activities up to and including TS/SCI. These materials and data, as well as the access of task order individuals to this information shall be handled in accordance with the applicable security instructions or directives. The Contractor(s) shall ensure that classified data is handled in accordance with appropriate DoD security regulations.

12. Disclosure of Information: The Contractor shall have access to sensitive information. The Contractor shall not divulge or release information developed or obtained in the course of project performance, except to authorized Government personnel or upon written approval of the applicable Government program/project manager. Any question on the release or use of information, or doubt of a person’s authority to request information, will be addressed to the applicable Government program/project manager. The Contractor providing this support may be required to execute an SF-312, Non-Disclosure Agreement.

13. Inquiries, Comments, and Complaints: The Contractor shall direct all inquiries, comments, or complaints arising from matters observed, experienced, or learned as a result of, or in connection with performance, the resolution of which may require dissemination of official information, to the applicable Government program/project manager.

14. Release of Information: Contractor shall not release any information (including photographs, files, public announcements, statements, denials or confirmations) on any part/phase of the project hereunder without the prior written approval of the GCC (e.g.

USCENTCOM, USAFRICOM, USPACOM, etc.) program/project manager. The Contractor shall not release information regarding individuals associated with the project hereunder without the prior written approval of the applicable GCC (e.g. USCENTCOM, USAFRICOM, USPACOM, etc.) program/project manager.

15. IDIQ Management: The Contractor shall ensure that the base IDIQ and each Task Order shall have a designated Contractor Point of Contact (POC). The IDIQ/Task Order POC shall be responsible for serving as the coordinating single point of contact between the Contractor and Government. The POC shall be fully authorized to manage the activities of Contractor and third-party Contractors needed to meet the Task Order requirements, providing a corporate escalation path for issues that may develop on individual Task Orders.

16. Other Direct Costs (ODC): It is anticipated that the Contractor may be directed to purchase material during the course of contract performance. The Contractor shall be authorized to purchase material as required by the Government. Material purchases exceeding TBD shall be supported by three (3) price quotes for the same line items for approval by the GSA Contracting Officer for approval prior to purchase. Reimbursement for other direct costs that fall within the scope of the contract shall only be made after the item has been received and accepted and the Contractor has submitted the vendor’s invoice verifying the cost for such items or services. All purchased materials and equipment shall become the property of the Government.

17. Monthly Invoice: The Contractor shall provide a monthly invoice for each TO to be submitted simultaneously with the monthly status report by email to the TPOC and in GSA’s IT- Solutions Shop (ITSS) system. The monthly invoice shall be submitted by the 15th of each month. If any information is missing or incorrect the invoice shall be rejected. The invoice shall include but not be limited to:

• Task Order number.

• The Contractor shall provide an itemized invoice for all items included in the submittal.

• Travel costs (if needed) shall be captured in accordance with the Field Service Support and Travel section of this PWS.

• Invoice submissions including travel costs shall include completed travel expense sheets for each trip for each employee.

• The Contractor shall comply with line item billing requests.

• The Contractor shall include number of hours expended per labor category, the labor category, and the rate for the month being invoiced.

• The Contractor shall include a total amount of labor hours and total dollars expended.

18. Contractor Submission: Deliverables are to be transmitted with a cover letter, on the prime Contractor’s letterhead, describing the contents, electronically through the General Services Administration’s (GSA) web-based procurement system, Information Technology Solutions Shop (ITSS), Government TPOC, and to any other destination(s) as required per the Government’s request. The Contractor shall provide hard copy deliverables as required upon the Government’s request. All deliverables shall be produced using recommended software tools/versions as approved by the Government. Reports shall be accomplished utilizing the MS Office Software Suite (to include MS Project as required) or Adobe .pdf. All raw and summarized data, test results, drawings, pictures, modeling, analytics, process orders, methodologies and coding shall be unrestricted and submitted electronically with final test reports, provided to the Government in Microsoft Word, Excel, and PowerPoint presentation formats. All final reports shall be presented to the Government through in-person briefings summarizing all results and recommendations as well as final documented reports.

19. Administration: Work is to be accomplished through the General Services Administration, Federal Acquisition Service (FAS), Great Lakes Region, through its contract with the selected Contractor. Certification by the Government of satisfactory services provided is contingent upon the Contractor performing in accordance with the terms and conditions of the referenced contract, this document, the approved technical and price quote, and all amendments.

Government TPOC, GSA's representatives, and the Contractor's representative(s) shall meet when deemed necessary by the Government TPOC. The Government TPOC, the GSA representatives, and the Contractor’s representative may meet at the place determined by the Government.

20. Kickoff Meeting: The Contractor in conjunction with the GSA Contracting Officer (CO) shall meet with key Government representatives within 30 business days after award to ensure a common understanding of the requirements, expectations, and ultimate end products. The Contractor shall discuss the overall understanding of the project and review the background information and materials provided by the Government representatives. Discussions shall also include the scope of work, deliverables to be produced, how the efforts shall be organized, projects completed, assumptions made/expected and results. A concerted effort shall be made to gain a thorough understanding of the Government expectations. However, nothing discussed in this or in any subsequent meetings or discussions between the Government and the Contractor shall be construed as adding, deleting, or modifying any Task Order requirements, including deliverable specifications and due dates.

21. Post Award Conference/Periodic Progress Meetings: The Contractor agrees to attend any post award conferences convened by the TPOC, contracting activity or contract administration office in accordance with Federal Acquisition Regulation Subpart 42.5. The Contracting Officer, TPOC, GSA COR, and other Government personnel, as appropriate, may meet periodically with the Contractor to review the Contractor's performance. At these meetings the Contracting Officer and/or TPOC shall apprise the Contractor of how the Government views the Contractor's performance and the Contractor shall apprise the Government of problems, if any, being experienced. Appropriate action shall be taken to resolve outstanding issues. The Contractor(s)’ Program Manager and Lead Engineer attendance may be required. The Contractors, as applicable, shall determine meeting dates and locations with Government concurrence. Prepare and provide agenda(s) and presentation material(s) for Government review and approval prior to all meetings and reviews. The Contractors shall take minutes and provide a written report on all meetings and reviews with the Government, to include meetings and significant decisions made via telephone. These meetings shall be at no additional cost to the Government.

22. Monthly Status Report (MSR): The Contractor shall provide a MSR for each TO to be submitted simultaneously with the monthly invoice by email to the TPOC and in ITSS. The MSR may be submitted more frequently if directed by the TPOC. The MSR may include any technical report as appropriate. The Contractor(s) shall also provide in-process reviews on demand. These in-process reviews shall generally take the form of Technical Reports. The Contractor(s) shall document the technical work performed in each of the subject areas agreed to with the TPOC in the form of a Technical Report. Within the MSR, the Contractors shall provide at a minimum the following information:

• Summary of effort, progress and status of all activities/requirements by task linked to deliverables as appropriate

• New work added since the previous MSR

• Brief summary of activity planned for the next reporting period

• Deliverables submitted for the period by task

• Identification of trip reports as previously discussed in the PWS

• All standards followed in support of the requirements

• Staffing

• Milestone updates and schedule changes, issues and/or variances.

• Problems or issues and/or resolutions

• Government action requested or required

• Labor hour burn rate

• Monthly and cumulative costs (shall provide a separate notice when burn rate exceeds 75% of incremental funding) to include travel and other Other Direct Costs (ODCs)

• Key programmatic risks

• Concerns or issues affecting the cost, schedule, or performance

• Plans for the next month’s activities

In addition, the MSR shall include labor charges for Support Items, which are authorized in the contract (e.g., travel, training, etc.). Charges shall not exceed the authorized cost limits established for labor and Ssupport Items. The Government will not pay any unauthorized charges. The Contractor(s) must provide travel documentation in accoradance with the Field Service Support and Travel section of the PWS.

23. Identification of Contractor Employees: All contract personnel attending meetings, answering Government telephones, and working in other situations where their Contractor status is not obvious to third parties are required to identify themselves as such to avoid creating an impression in the minds of members of the public that they are Government officials. They must also ensure that all documents or reports produced by Contractors are suitably marked as Contractor products or that Contractor participation is appropriately disclosed.

24. Contractor Performance: The Contractor shall establish and provide a qualified workforce capable of performing the required tasks. All staff shall be fully trained, professional, and customer oriented and shall consistently provide responsive, flexible, and cost effective service.

The Government shall approve all key personnel resumes. The Contractor shall monitor work performance, measure results, ensure delivery of contracted product deliverables and services, support management and decision making, and facilitate communication. The Contractor shall bring problems or potential problems affecting performance to the attention of the TPOC and GSA PM as soon as possible. The Contractor shall provide in writing the results of all meetings with the TPOC that affect and/or change conditions, or result in additional agreements or requirements to the GSA PM. The Contractor shall not perform any work outside the scope or requirements of this PWS and resultant orders without express written approval of the GSA

Contracting Officer. Verbal reports shall be followed up with written reports within 48 hours of submission of the verbal report. The Contractor shall establish and maintain a documented set of disciplined, mature, and continuously improving processes for administering all contract and Task Order efforts with an emphasis on cost efficiency, schedule, performance, responsiveness, and consistently high-quality delivery. Quality work performance in accordance with applicable standards and guidelines shall be ensured. The Contractor shall perform the standards of this PWS in an environmentally acceptable manner consistent with all Federal, State and local laws.

25. Non-Personal Services: The Government will neither supervise Contractor employees nor control the method by which the Contractor performs the required tasks. Under no circumstances shall the Government assign tasks to, or prepare work schedules for, individual Contractor employees. It shall be the responsibility of the Contractor to manage its employees and to guard against any actions that are of the nature of personal services, or give the perception of personal services. If the Contractor feels that any actions constitute, or are perceived to constitute personal services, it shall be the Contractor’s responsibility to notify the TO Contracting Officer (CO) immediately. These services shall not be used to perform work of a policy/decision making or management nature, i.e., inherently Governmental functions. All decisions relative to programs supported by the Contractor shall be the sole responsibility of the Government.

26. Organizational Conflicts of Interest (OCI): If at any time during performance of PWS requirements, the Contractor becomes aware of an actual or potential Organizational Conflict of Interest (OCI) situation or issue, or the appearance of an actual or potential OCI situation or issue exists, the Contractor shall identify in writing, to the COR and CO, the nature of the OCI situation or issue, along with a plan to mitigate the OCI situation or issue.

27. Personnel Retention: The Contractor shall make every effort to retain personnel in order to ensure continuity until Order completion. If it should become necessary to substitute or replace personnel, the Contractor shall immediately notify the COR in writing of any potential vacancies and shall make every effort to submit the qualifications/resume(s) of replacement personnel within 14 calendar days of the notification. The Contractor shall submit the qualifications/resume(s) of all potential personnel selected to perform under this IDIQ to the COR and Contracting Officer for Government review and acceptance/rejection. Upon Government acceptance of qualifications/resume(s), the candidate shall be available to begin performance within 14 calendar days. Prior to the submission of qualifications/resumes, the Contractor shall ensure that the candidate(s) satisfy the applicable security requirements to reduce staffing delays. The Contractor shall ensure continuity of operations during periods of personnel turnover and long-term absences. Long-term absences are considered those longer than one week in duration.

28. Non-Compliance: Failure to comply with the procedures outlined in the IDIQ Task Order PWS may result in payment being delayed at no additional cost to the Government.