Attachment 1_ SOW_ ID05180020-AMDT0001.docx

STATEMENT OF WORK

A procurement by the U.S. General Services Administration Region 5 Contracting Division on behalf of

CLIENT AGENCY:

United States Special Operations Command

CLIENT PROGRAM:

Joint Airborne Intelligence, Surveillance, and Reconnaissance (AISR)

PROJECT TITLE:

AISR Sensor Data Transport Infrastructure Enterprise Integration

PROJECT NUMBERS:

ID05180020

47QFLA18K0005

Original Version Dated:

12.16.20

Post Award Document Revision History

Contents

1 INTRODUCTION

1.1 Organization

U.S. Special Operations Command (USSOCOM), Defense Information Systems Agency (DISA), Air Force Special Operations Command (AFSOC), United States Air Force (USAF), and other mission partners require a lead integrator to manage the various planning, acquisition of ancillary items needed for the integration of different systems, engineering, logistics, and integration functions supporting capability expansion for the Joint Airborne Intelligence, Surveillance, and Reconnaissance (AISR) Sensor Data Transport Infrastructure.

In its most comprehensive form, the site level integration required by this Statement of Work (SOW) entails a compilation of all end-to-end components needed to support sensor data backhaul from airborne assets to global customers. This includes supporting the air vehicle configurations, satellite equipment, the integrated ground entry point/gateway, and the terrestrial circuits required to satisfy a Government-specified capacity, or a specific number of simultaneous operations (SIMOPS) and/or threads. This support includes the Department of Defense (DoD) satellite gateways and the ability to leverage DISA’s Unified Video Dissemination System (UVDS) for distribution of sensor data to global special operations forces and the other Geographical Combatant Commands (GCCs).

1.2 Objective

USSOCOM, as the predecessor for the greater DoD efforts, is spearheading this requirement for a Lead Integrator (the Contractor) to provide planning, systems engineering, integration and operationalization for existing and future Joint DoD AISR Sensor Data Transport Infrastructure--a globally provisioned, regionally oriented, joint infrastructure providing the downlink of sensor data from manned and unmanned assets, and high quality, low latency distribution for authorized strategic, operational, and tactical consumers.

1.3 Scope

The Contractor shall provide program and project management support focused on system integrator roles; specifically, to assist with the planning, engineering, integration, and delivery of capabilities and capacity for the DoD AISR Sensor Data Transport Infrastructure.

The Contractor must comply with Advisory Assistance Services contract mandates executed under the Engineering and Technical Services category. This category includes contractual services used to support program offices during the acquisition cycle. It provides systems engineering and technical direction (FAR 9.505-1(b)) to ensure the effective operation and maintenance of a weapon system, or major system, as defined in the Office of Management and Budget (OMB) Circular A-109. Alternatively, it provides direct support to non-deadly components of a weapons system essential to the Research and Development, production, and/or maintenance of the system.

The Contractor must understand the DoD’s pre-existing AISR Sensor Data Transport Infrastructure (e.g., hardware, software, waveforms, satellites, terrestrial networks, and terminals supporting a wide variety DoD assets—see figure 1) and be intimately familiar with the Original Equipment Manufacturers (OEMs) and industry partners currently supporting USSOCOM’s AISR Transport Infrastructure. The current AISR infrastructure serves as the near term template for continued expansion at planned Air Combat and Air Force Special Operations Command (ACC and AFSOC) Remote Piloted Aircraft Relay Sites as well as DISA Large Satellite Gateways.

Figure 1:

1.4 Background

The Government uses a wide variety of manned (e.g., MC-12Ws, U-28s, B-350s, etc.) and unmanned (e.g., MQ-1B Predators, MQ-9A Reapers, and MQ-1C Gray Eagles) aircraft to collect intelligence data. To support the associated sensor data distribution, these aircraft have a transmit capability allowing them to relay sensor data, via Commercial Ku, Commercial Ka, and/or Wideband Global Satellite Communications (SATCOM) Ka satellites to ground entry points/gateways outside the Line of Site (LoS) footprint. The sensor data is then downlinked, processed, and distributed terrestrially to the various authorized consumers at the Strategic (e.g., Processing, Exploitation, and Dissemination {PED} Cells), Operational (Joint/Tactical Operations Centers {JOCs/TOCs}), and Tactical (e.g., Local Area Network {LAN} based target engagement authority {TEA} decision-makers) levels to support their mission objectives.

The Contractor shall assist with sustainment and for future AISR Transport Infrastructure capability and/or capacity expansion. This includes requirements management, budgeting, supporting the design of new sites, management of OEM integration, installation, cyber security accreditation, and sustainment activities. The Contractor shall support specified USSOCOM and DISA ground entry point/gateway locations, provide acquisition and logistics support, manage relationships with host site personnel and their support contractors, and forge relationships with the applicable OEMs to ensure day-to-day global operations remain viable/successful. Given the critical nature of the sensor data transport infrastructure in supporting the DoD’s global mission, the Contractor must possess an understanding, knowledge, and experience with the pre-existing, end-to-end Joint AISR Transport Infrastructure.

1.5 Applicable Documents

The documents (i.e., certifications, specifications, standards, policies, and procedures), versions current at time of contract/order award, identified in the list below are incorporated with the same force and effect as if provided in full text. Succeeding revisions may be substituted or incorporated as required with full notice and disclosure to the contractor. The Government will provide access to available documents and technical information as required and upon contractor request, if not available via a hyperlink within this SOW.

· DoD Instruction 8500.01 “Cybersecurity”

· DoD Instruction 5000.02, “Operation of the Defense Acquisition System”

· DoD Instruction 8510.01, “Risk Management Framework (RMF) for DoD Information Technology (IT)

· DoD 8570.01-M “Information Assurance Workforce Improvement Program”

· DoD Directive 8140.01 “Cyberspace Workforce Management,”

· AISR-CM-PLN-001 Configuration Management Plan for Airborne Intelligence, Surveillance and Reconnaissance Transport

2 REQUIREMENTS AND TASKS

2.1 General Performance Requirements

· Resources

Unless otherwise stipulated, the contractor shall furnish or provide all personnel, personnel management and supervision, all related internal supporting business functions (including background and “overhead” personnel), materials, supplies, equipment, and facilities to perform the full range of services required by this SOW.

· General Communication

Regular and direct contractor interface with the Contracting Officer (CO); the Contracting Officer’s Representative (COR), and other identified Government representatives is mandatory. The contractor shall not contact nor take direction from unauthorized Government representatives, under any circumstances.

· Identification

All contractor personnel shall be required to wear Government-approved or provided picture identification badges so as to distinguish themselves from Government employees when working at the Government site. Additionally, the contractor shall comply with all visitor identification requirements when visiting the Government site. When conversing with Government personnel during business meetings, over the telephone or via electronic mail, contractor personnel shall identify themselves as such to avoid situations arising where sensitive topics might be better discussed solely between Government employees. Contractors shall identify themselves on any attendance sheet or any coordination documents they may review. Electronic mail signature blocks shall identify their company affiliation. Where practicable, contractors occupying collocated space with the Government should identify their work space area with their name and company affiliation

· Business Relations

A primary element of project success is the business relationship between the contractor and Government representatives. Within this context the Government will monitor the contractor’s contribution to business relations and provide feedback when required. The contractor shall make every effort to establish and maintain clear and constant communication channels with the Government primaries (CO, COR, and other identified Government representatives) of the contract/order for the purpose of:

· Promptly identifying SOW and/or business relationship issues of controversy and the bilateral development and implementation of corrective action plans.

· Ensuring the professional and ethical behavior of contractor personnel.

· Maintaining effective and responsive subcontractor management (if applicable).

· Ensuring the contractor support team is fully aware and engaged in strengthening the interdependency that exists between the contractors and their Government counterparts.

· Facilitating contractor–Government collaboration for continuous improvement in performing SOW tasks, reducing risks and costs, and meeting the mission needs.

· Contractor Response

The contractor shall ensure prompt response to Government inquiries, requests for information or requests for contractual actions

· Professional Appearance

Contractor personnel shall present a neat and professional appearance appropriate to the work being performed at all times when interacting with Government representatives, working in Government facilities, or representing the Government at meetings or before third parties.

2.2 General Meeting Requirements

The contractor shall participate in the following meetings. Nothing discussed in any meetings or discussions between the Government and the contractor shall be construed as adding, deleting, or modifying the contractual agreement without written authorization from the CO.

· Initial Business/Kickoff Meeting

Within 30 business days following the contract/order award (or other time mutually agreed between the parties), the contractor shall meet with the GSA CO, GSA COR, and other identified Government representatives to ensure a common understanding of the requirements, goals, expectations, end products, and objectives of the contract/order. The contractor shall discuss the overall understanding of the project and review the background information and materials provided by the Government. Discussions will also include the scope of work, deliverables to be produced, how the efforts will be organized and project conducted; assumptions made/expected end 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 contract/order requirements, including deliverable specifications and due dates. The contractor shall also address the status of any issues that will affect contractor start-up/ramp-up toward achieving full service/support capability. The contractor will be responsible for taking minutes of this meeting.

· Ad hoc Technical / Work Status

The contractor shall, if requested by the Government, participate in monthly status meetings or ad hoc technical meetings at a mutually agreeable time and place to discuss tasking, work progress, technical problems, performance issues, or other technical matters. During these meetings the contractor shall at least provide accomplishments, problems and issues, and planned actions. The contractor shall take minutes of these meetings and include them in the Monthly Status Report. These meetings will occur at a time and place mutually agreed upon by the parties.

· Contract Administration Meetings

The CO may require the authorized contractor representative to meet or participate in a teleconference with authorized Government personnel as often as deemed necessary to discuss performance or administrative issues. The contractor may also request a meeting with the CO when deemed necessary. The content of meetings shall be documented in writing, as agreed between the parties. Minutes shall be approved by both parties and shall be included in the Government contract file.

2.3 Program/Project Management

· General Program/Project Management Requirements

The contractor shall be solely responsible for managing the work performed in the execution of the contract/order. This includes the responsibility to:

· Assign appropriate resources to each task.

· Maintain clear organizational lines of authority.

· Ensure effective task management and administration, following the requirements set forth in the SOW.

· Maintain the personnel, organization, and administrative control necessary to ensure that the work delivered meets the specification requirements.

· Establish and use proven policies, processes, analyses, and best practices.

· The contractor shall be fully responsible for management, control, and performance of any subcontractor used in support of the contract/order. Use of a subcontractor on the contractor’s team shall not relieve the prime contractor of responsibility nor accountability in the execution of the contract/order

Additionally, the contractor shall:

· Bring problems or potential problems affecting performance to the attention of the CO as soon as possible.

· Notify the COR, CO, and other identified Government representatives immediately of any projected, anticipated, or known delays that may impede contactor performance.

· When requested, deliver written reports to the CO to memorialize all verbal reports.

· Provide, in writing, the results of all meetings in which proposals are put forth that have the potential for affecting and/or changing contract agreements, requirements or conditions, and these shall be brought to the attention of the CO.

· Phase-In Support

The contractor shall provide phase-in support in accordance with the phase-in plan as required per SOW paragraph 4.7.

· Phase-Out Support

The contractor shall provide phase-out support in accordance with the phase-out plan as required per SOW paragraph 4.8.

2.4 Site Level Information Assurance Support

The Contractor personnel shall assist the Government with Information Assurance support when any new OEM specific equipment is installed, or significantly modifies or affect the enterprise baseline. This includes but is not limited to updating site plans, site rack elevations, site interface control documents, and assisting with required security scans.

2.5 Cyber Security

The Department’s Joint AISR Sensor Data Transport Infrastructure must 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 afford timely and guaranteed access to the transported sensor data transported at the time, place, quantity, and quality dictated by tactical, operational, and strategic users/consumers. Specifically, 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.

The Contractor shall provide cyber security and configuration management support to USSOCOM and DISA for RGEP/IGEP (respectively) authority to connect or IA accreditations.

2.6 Contractor Capability

The Contractor shall buildout ground entry points/large satellite gateways. This shall include providing planning support, systems engineering, integration, and operationalization of new satellite data ingest capabilities, ground sensor data processing, and terrestrial circuit acquisition and buildout.

The Contractor shall assist the Government with system program management office (SPO/PMO) functions, including, but not limited to:

· Program Management

· Requirements Management

· Project Management

· Contracts Management and Auditing

· Cost Estimating and Budgeting

· Purchasing and Acquisition

· Site buildout (Continental United States (CONUS)/ Outside of Continental United States (OCONUS))

· Shipping, Receiving, and Inventory

· Systems Engineering

· System Integration

· Test and Evaluation

· Cyber Security (specifically, Risk Management Framework)

· Configuration Management

· Life Cycle Logistics/Integrated Logistics Support

The Contractor shall understand the pre-existing AISR Sensor Data Transport Infrastructure and its supporting communications architecture (see figure 1). This includes the sensor producing platform, the SATCOM/radio frequency (RF) links used to transport the produced sensor data, the processing and distribution ground entry point/gateways used to downlink and process the transported sensor data, and the terrestrial transport used to route/deliver the processed sensor data to/with/among the intended/authorized consumers. This includes management and monitoring for the sensor data transport infrastructure (e.g., the SATCOM/RF links, the processing and distribution ground entry points/gateways, ground-based sensor data processing capabilities, distribution points of presence, the associated networking infrastructure, and terrestrial connectivity necessary to provide end-to-end signal flow).

The Contractor shall have a thorough understanding of the DoD’s current day satellite processing and terrestrial network equipment (see figure 1) supporting sensor data transport for AISR assets (e.g., manned and unmanned); specifically, USSOCOM’s Regional Ground Entry Points (RGEPs), DISA’s Intelligence, Surveillance, and Reconnaissance (ISR) Ground Entry Points (IGEPs) within the Large Satellite Gateways, and DISA’s Unified Video Dissemination System (UVDS) heavily leveraged for distribution to/with/among the intended recipients/authorized consumers.

A fully integrated, “turn-key” AISR Transport Infrastructure Gateway would entail a Government-defined combination to include, but not limited to, any/all of the above capabilities/capacities at an identified CONUS/OCONUS location. The Contractor shall manage the planning, engineering, logistics, acquisition (if other than GFE components), integration, and operationalization of the implemented gateway capability in a fixed facility.

The DoD seeks a Contractor capable of providing planning, engineering, oversight, and management for either capability and/or capacity expansion at the commodity level (e.g., current baseline and/or industry-wide analysis of new and innovative technologies) for pre-existing facilities/locations; or, as needed planning, engineering, oversight, and management for a fully integrated, “turn-key” AISR Transport Infrastructure Gateway at an entirely new facility/location.

A capability and/or capacity expansion at the commodity level could but is not limited to require integration of any one, or a combination, of the following:

· A fixed large aperture terminal supporting Commercial Ku Band frequency transmission/receipt.

· A fixed large aperture terminal supporting Commercial Ka Band frequency transmission/receipt.

· A fixed large aperture terminal supporting Wideband Global SATCOM (WGS) Ka Band frequency transmission/receipt.

· A fixed large aperture terminal supporting WGS X Band frequency transmission/receipt.

· A mobile/deployable large aperture terminal supporting Commercial Ku Band frequency transmission/receipt.

· A mobile/deployable large aperture terminal supporting Commercial Ka Band frequency transmission/receipt.

· A mobile/deployable large aperture terminal supporting Wideband Global SATCOM (WGS) Ka Band frequency transmission/receipt.

· A mobile/deployable large aperture terminal supporting WGS X Band frequency transmission/receipt.

· A terminal/frequency agnostic fixed facility multi-terminal, matrixed distribution switch interface.

· An unmanned (specifically legacy and current USAF unmanned assets) downlink, processing, and distribution solution supporting a wide variety of sensor data (including standard definition and high definition full motion video), proprietary waveforms, and/or Type-1 encryption technologies.

· A manned (specifically legacy and current USAF manned assets as well as industry-standard contractor-owned/contractor operated assets currently leased in support of DoD users) bi-directional, processing, and distribution solution supporting a wide variety of sensor data (including standard definition and high definition full motion video), command & control communications services, proprietary waveforms, and/or Type-1 encryption technologies.

· A transrate/transcode solution to support the ingest, manipulation, and if appropriate, modification of full motion video to include standard definition and high definition full motion video including associated key length variable, telemetry, and positioning data.

· A collaterial level (red) Internet Protocol point of presence affording required interconnectivity for manned and/or unmanned sensor data processing systems, associated command & control communications providers, and among/between/with local area network and/or wide area network consumers.

· An unclassified level (black) Internet Protocol point of presence affording required interconnectivity for manned and/or unmanned sensor data processing systems, collateral level (red) Internet Protocol points of presence, the DoD’s Information Network (DoDIN), DISA’s Unified Video Dissemination Solution (UVDS), and among/between/with local area network and/or wide area network consumers.

· An industry-standard network operations management system of systems providing monitoring and hazardous condition and outage reporting, and local and enterprise notification capabilities.

In addition to the above fixed facility AISR Transport Infrastructure Gateway, the Government may also require a mobile/deployable variant. This variant would entail similar planning, engineering, logistics, acquisition (if other than GFE components), integration, and operationalization of the required gateway capability but in a mobile/deployable variant with options for organic power management, backup power (generator and shore power options), and associated deployable terminal and/or fixed terminal connectivity.

The contractor shall provide any capability and/or capacity or AISR Transport Infrastructure Gateway instantiation deliverable to include all required artifacts supporting a Risk Management Framework (RMF) authority to operate/approval to connect: incorporates physical and logical diversity/redundancy (if applicable), and meets/exceeds the throughput/capacity (e.g., # of Threads, # of SIMOPS, # of concurrent connections/downlinks, etc.) specified in the associated task order.

2.7 RESERVED

3 QUALITY

Both the contractor and the Government have responsibilities for providing and ensuring quality services, respectively.

3.1 Contractor Quality Management

The contractor shall identify and implement its approach for providing and ensuring quality throughout its solution to meet the requirements of the SOW via the contractor’s Quality Management Plan (QMP). The QMP shall describe the application of the appropriate methodology (i.e., quality control and/or quality assurance) for accomplishing performance requirements. The QMP shall describe how the appropriate methodology integrates with the Government’s requirements. The contractor shall make the QMP available to the Government for review upon request and shall obtain acceptance of the QMP by the CO as required. The contractor shall make appropriate modifications to the QMP (at no additional cost to the Government). The Government has the right to require revisions of the QMP (at no cost to the Government) should the QMP fail to deliver the quality of the services required at any time during performance.

3.2 Performance Based Requirements - Service Delivery Summary

Performance Standards, Acceptable Quality Levels (AQLs), and Incentives/Disincentives are defined in SOW Attachment A, the Service Delivery Summary (SDS). The SDS criteria will be used to determine if performance requirements are met.

3.3 Government Quality Assurance

The Government will perform periodic reviews of the contractor’s performance in accordance with the Government’s Quality Assurance Surveillance Plan (QASP). The Government reserves the right to review services to be provided, including those developed or performed at the contractor's facilities, to determine conformity with performance and technical requirements.

4 DELIVERABLES

4.1 Contractor Submission

Deliverables are to be transmitted with a cover letter, on the prime contractor’s letterhead, describing the contents, electronically through GSA’s web-based procurement system, as required, and to any other destination(s) as required per the Government’s request. The contractor shall provide hard copy deliverables as required per the Government’s request. All deliverables shall be produced using software tools/versions as approved by the Government.

4.2 Government Review

Government personnel will have 10 business days to review deliverables (to include resubmissions) and provide written acceptance/rejection. Authorized Government representatives will notify the contractor of deliverable acceptance or provide comments in writing. The contractor shall incorporate Government comments, or provide rationale for not doing so within 5 business days of receipt of comments. Government acceptance of the final deliverable will be based on resolution of Government comments or acceptance of rationale for non-inclusion. Additional changes volunteered by the contractor will be considered a resubmission of the deliverable.

· Government Delays in Reviewing Deliverables or Furnishing Items

If contractor performance or submission of deliverables is contingent upon receipt of Government furnished items (data, equipment, materials, facilities, and support) or input, or upon Government review and approval of interim items or draft documents (collectively referred to as Government Performance), the Government shall specify, if not already specified within this SOW, when it will provide such items or input, or the time it will need to perform reviews or give approvals. If the Government fails to meet item, input, review, or approval deadlines, contractor performance or submission of deliverables shall automatically be extended one business day for each day of government delay. The contractor shall promptly advise the Contracting Officer of any delays in receipt of Government furnished items, input, reviews, or approvals.

4.3 Deliverable Table

The contractor shall deliver the deliverables listed in the following table on the dates specified in ITSS/ASSIT and by email to the Government.

4.4 Monthly Invoice

The contractor shall provide a monthly invoice, no later than the 15th calendar day of the month following the monthly reporting period, to be submitted simultaneously with the MSR. As applicable, the invoice shall include but is not limited to:

· Clear identification of all costs.

· Labor hours expended (for labor hours tasks). The labor hours expenditure information shall include the identification of the employee name, labor category, hourly labor rate, and total number of labor hours expended.

· Timecards. As required, the contractor shall provide a copy of each employee’s timecard/sheet. The timesheet shall identify the contractor employee name and number of hours claimed per day.

· Travel costs.

· Supporting documentation for travel costs. Refer to SOW 5.3 for specific requirements.

· Other Direct Costs.

· Supporting documentation for other direct costs. Refer to SOW 9.6 for specific requirements.

· As required, the contractor shall comply with line item (i.e., per individual positions, different programs, program areas, etc.) invoicing requests.

4.5 Monthly Status Report

The contractor shall provide a MSR, no later than the 15th calendar day of the month following the monthly reporting period, to be submitted simultaneously with the monthly invoice. The MSR shall include, but is not limited to, the items identified below.

· Status of tasks, schedules, deliverables. Status of tasks shall include a summary description and schedule of all tasks completed during the reporting period, all tasks currently on-going during the reporting period and all known tasks assigned for future reporting periods.

· Resource hours and costs against Government defined tasks to support accurate project cost accounting using Government formats and tools.

· Current and cumulative task funding status (direct labor, travel, and other direct cost funding status to be reported separately, as required).

· Outstanding issues, and proposed resolution approaches and actions to resolve any outstanding issues.

· Staffing report identifying current staffing roster, all current vacancies, and a record of all staffing departures.

4.6 Trip Report

For all long-distance travel, the contractor shall submit Trip Reports after completion of a trip. The contractor shall reconcile the Trip Reports with each invoice such that they can be matched month by month. The Trip Report shall include the following information:.

· Personnel traveled.

· Dates of travel.

· Destination(s).

· Purpose of trip (be specific).

· Actual trip costs.

· Approval Authority (copy of the e-mail authorizing travel by the identified Government representative).

· Summary of trip events and accomplishments.

4.7 Phase-In Plan

The contractor may or may not propose a separately priced transition period, for a duration to be determined and proposed by the contractor, but shall not exceed a period of 30 calendar days. The transition period is defined as the period of time (during the phase-in) when the new contractor and the incumbent contractor will both be providing support to the client as required to support the transition to the newly awarded contract/order. If the contractor chooses to propose a transition period, such period shall be included and addressed within the below identified phase-in plan.

The contractor shall develop a phase-in plan. Such phase-in plan shall present a clear understanding of the phase-in tasks required, the issues likely to result from non-incumbent contractor performance, and the contractor’s proposal to resolve such issues. The phase-in plan shall include a clear and feasible strategy for delivering services required within the periods specified by the plan and shall include a detailed plan-of-action and milestones to transition the functions identified in this SOW in a well-planned, orderly, and efficient manner. The phase-in plan shall include, at a minimum:

· Staffing plan.

· Development and submission of required deliverables.

· Interface with the Government and incumbent contractor (if applicable) during phase-in, to include meetings or status reports, as required.

· Approach to maintaining quality and minimizing disruption during phase-in.

· Development and dissemination of operating instructions, procedures, and control directives.

4.8 Phase-Out Plan

During phase-out of the contract/order, which is determined to be a period of 30 calendar days prior to the lifecycle end date of the contract/order, a smooth and orderly transition between the incumbent contractor and the successor contractor is necessary to ensure a minimum disruption to vital Government business. The contractor shall cooperate to the extent required to permit an orderly changeover to the successor contractor. The phase-out will be deemed completed by the COR and/or other identified Government representatives when it is determined by the Government that the transition of property, data, and information developed as a part of the contract/order have been successfully changed over from the outgoing contractor to the Government and the successor contractor as required. Phase-out activities include, but are not limited to, the tasks below.

· Submission of official comprehensive phase-out plan.

· Daily communication of staffing status (i.e. projection of when incumbent contractor employees will off-board from the incumbent contract/order and identification of additional incumbent resources, such as a transition team, that may be needed to support the transition efforts) and overall phase out status, in accordance with the accepted phase-out plan.

· Maintain the phase out schedule included within the phase-out plan.

· Transition of property.

· Transition of supporting documentation.

· Transition of accounts (e.g. user accounts and user access).

· Knowledge transfer on the established installation, operation, and maintenance procedures of the technologies supported. The phase out plan shall clearly describe the proposed methodologies to be utilized for such transfer (e.g., written documentation, manuals, formal classroom type training, one-on-one training sessions, etc.).

· Execution and submission of phase out checklist, to include Government acceptance.

5 PERFORMANCE

5.1 Period of Performance

The anticipated period of performance(s) is/are identified below.

· 5 year ordering period

5.2 Place of Performance

The work to be performed under this SOW shall be performed at various Government sites and Contractor facilities—both CONUS and OCONUS. The Contractor will be required to support integration and testing at Government designated systems integration and engineering labs, and to actively engage and/or interface with the Government and/or OEM partners supporting the DoD’s AISR Sensor Data Transport Infrastructure. The primary place of performance will be identified at the task order level.

· Applicability of Telework

All work performed at locations other than those identified as Government and/or contractor facilities shall be approved prior to performing the work. Federal contractors are not governed by Office of Personnel Management (OPM), GSA, or the individual agency policies; however, this does not prohibit contractor personnel from actually working at an alternate site, when/as appropriate and specifically authorized by the Government. The contractor shall develop telework policies to comply with the following requirements and address such requirements at a generic level within their QMP. Alternate work arrangements for contractors shall be negotiated with the contractor’s own employer and the appropriate agency official, to ensure policies and procedures are in close alignment and there is a clear and concise arrangement documenting the agreement. It remains the contractor’s responsibility to ensure the services are performed in accordance with the terms and conditions of the contract/order.

· The contractor shall address the pertinent facts impacting performance and ensure all affected contractor resumes and other related documentation reflects the applicable work site. The contractor shall provide justification to the Government when identifying and submitting an individual as a telecommuter and address implementation processes and procedures within the QMP. The contractor shall be responsible for ensuring the Government has the required access/details necessary for the Government to perform quality assurance responsibilities.

· The contractor shall comply with all agency security telework policies. The contractor shall ensure all services provided from an alternate site comply with the Federal Information Security Management Act of 2002 (FISMA) and address the following, as a minimum:

· Controlling access to agency information and information systems;

· Protecting agency information (including personally identifiable information) and information systems;

· Limiting the introduction of vulnerabilities;

· Protecting information systems not under the control of the agency that are used for teleworking;

· Safeguarding wireless and other telecommunications capabilities that are used for teleworking; and

· Preventing inappropriate use of official time or resources that violates subpart G of the Standards of Ethical Conduct for Employees of the Executive Branch by viewing, downloading, or exchanging pornography, including child pornography.

· Performance at Contractor Facilities

Work performed at contractor facilities shall be performed according to the contractor’s standard commercial practice; however, the contractor representatives at these facilities must be available for interaction with Government employees during the core hours identified in the paragraph entitled “Normal Business Day”, with the exception of Government designated holidays or facility closures.

· Unplanned Government Facility Closures

In the event of unplanned closure of the Government facility for any reason (e.g. natural disasters, Government shut-down, or severe weather) the Contractor shall make its best effort to mitigate loss of work time. If Contractor employees are working on the Government installation, this may be done by moving employees to an off-site location. If performance under this contract/order is not possible, the Contractor shall take steps to assign employees to other projects on a temporary basis or place them in leave status to minimize non-productive costs to the Government under this contract/order. Additional instructions may be provided by the Contracting Officer on a case-by-case basis. Disagreements between the parties resulting from closures shall be settled through negotiations to the maximum extent possible or shall otherwise be settled pursuant to the provisions of the Disputes provisions of this contract/order.

In the event the Government facility experiences a closure (e.g., natural/man-made disaster, act of God, etc.), mission essential/non-essential service determinations will be specified (by the Government) at the order level with specific guidance for Contractor responsibilities (e.g., personal protective equipment, “ride out” procedures, evacuation/muster direction, stop movement orders, etc.).

5.3 Travel

Travel must be coordinated and authorized by the CO, the COR, and/or other identified Government representatives prior to incurring costs. 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.

The contractor shall invoice monthly on the basis of cost incurred. The contractor must provide documentation in support of all travel expenses. The contactor will 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).

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 whereby receipts are required regardless of dollar value), 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 (SOW Attachment B) 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.

5.4 Hours of Work

· Standard Duty Hours Support

The contractor shall provide standard duty hours support as defined below.

5.4.●.1 Normal Business Day - (work hour category A)

A standard normal business day is defined as any 8 hours of productive labor which must include the Core Business hours of 0900 through 1500 PM local time, Monday through Friday, excluding Federal Holidays. Exceptions may be required and shall be coordinated with the COR and/or other identified Government representatives, to include short-term or long-term requirements for staggered business days.

5.4.●.2 Staggered Business Day - (work hour category B)

A standard staggered business day requires that on-site support shall be provided 0700 through 2100 local time, Monday through Friday, excluding Federal Holidays. Exceptions may be required and shall be coordinated with the COR, if coverage is required outside the established timeframe.

5.4.●.3 Staggered Business Day - (work hour category C)

A standard staggered business day requires that on-site support shall be provided 24 hours per day, 6 days per week, 1700 Sunday through 1700 Friday, local time, excluding Federal Holidays. Exceptions may be required and shall be coordinated with the COR and/or identified Government representatives, if coverage is required outside the established timeframe.

· Non-Standard Duty Hours Support

The contractor shall provide for scheduled (planned work hours) and unscheduled (other than planned work hours), non-standard duty hours support as required. The contractor shall identify a primary and alternate point of contact for non-standard, unscheduled duty hours requirements. To ensure the applicable labor hours allocations are not exceeded (typically 40 hours per week), labor hours expended in support of non-standard duty hours requirements shall be offset by reducing the number of standard duty work hours by an equivalent number within an off-set time period that doesn’t impact the contractor’s ability to complete the contract/order requirements. The contractor shall not place restrictive limitations on the off-set time period.

5.4.●.1 Scheduled (work hour category D)

Scheduled non-standard duty hours support shall be coordinated with the authorized Government point of contact and the contractor’s designated point of contact. The Government may request non-standard duty hour support (fiscal year close-out periods, deployment/release periods, and peak operational periods). Scheduled non-standard duty hour support may also be required to support a short term surge in requirements.

5.4.●.2 Unscheduled (work hour category E)

The Government may also request that the contractor provide un-scheduled (e.g., emergency technical support), non-standard duty hours support. The contractor shall respond within 15 minutes of notification. When off-site support can resolve the issue, the contractor’s personnel shall begin immediately upon notification. The contractor shall assess the cause, determine the scope of the problem, advise the appropriate Government organization, provide an estimated restoration time, and identify and implement action for problem resolution. When required, on-site support shall begin within one hour of notification to the contractor’s designated individual. This unscheduled support may include:

· Remote telephone support with the Government staff and/or customers.

· Remote support on Government Furnished Equipment (GFE). Contractor personnel may be equipped with GFE that enables remote access/log-on. The Government will not incur any costs associated with home-based WiFi or LAN access to the Internet.

· Onsite support.

5.5 Limitations on Contractor Performance

The contractor shall NOT perform the following functions in connection with the services provided under the contract/order.

· Approve, decide, or sign as a Contracting Officer;

· Negotiate with Government suppliers;

· Accept or reject supplies or services;

· Determine acquisition, disposition, or disposal of Government property;

· Direct other contractor or Government personnel;

· Determine cost reasonableness, allowability, or allocability;

· Vote on a source selection board;

· Supervise Government personnel;

· Approve Government requirements or plans;

· Determine Government policy.

6 PERSONNEL

6.1 General Requirements

All contractor personnel shall meet the minimum general requirements listed below.

· All personnel shall be capable of working independently.

· All personnel shall have training and experience that is appropriate for the tasks to which they will be assigned.

· The contractor shall provide personnel that are capable of conducting themselves in a professional manner and have proper telephone and e-mail etiquette, customer service techniques, and organizational skills.

· Contractor personnel performing in a leadership capacity shall be capable of directing contractor personnel and interfacing with the Government and customers.

· Ability to communicate applicable technical subject matter expertise to management and others.

· Strong written and oral communication skills in the English language. All contractor personnel must be able to read, write, speak and understand English.

· Exceptional customer service skills.

· Strong time-management and prioritization skills.

6.2 Specific Expertise and Experience

The contractor shall provide personnel with the appropriate skill levels. While each individual contractor employee may not possess expertise and experience in each area below, the Government requires that the overall contractor staff possess the aggregate skills, expertise, and experience in each of the areas identified to successfully complete all requirements.

· The Program Manager must have a minimum of 20 years’ experience in the AISR Transport Infrastructure field

· All Subject Matter Experts (SMEs) must have a minimum of 20 years’ experience in their field

· The Cybersecurity Lead must be a senior cybersecurity professional with no less than 10 years’ experience leading cybersecurity teams

· The Configuration Management Lead must have 15 years’ experience leading configuration management activities

6.3 Training

·…