Attachment 9_ Task Order 01 PWS-AMDT0002.docx

Lead Integrator PMO Support for AISR Transport Infrastructure Page PAGE 7

PERFORMANCE WORK STATEMENT (PWS)

Solicitation PIID 47QFLA

GSA ID05180020001

PROJECT TITLE:

Airborne Intelligence, Surveillance, and Reconnaissance (AISR) Sensor Data Transport Infrastructure Enterprise Program Management Office (PMO) Support

Task Order 001

1.1 Description of Services

This Performance Work Statement (PWS) outlines Contractor tasks required to support United States Special Operations Command (USSOCOM), Department of Defense (DoD) Chief Information Officer (CIO), the Defense Information Systems Agency (DISA) with Program Management Office (PMO) and various other team members support for their Airborne Intelligence, Surveillance, and Reconnaissance (AISR) Transport Infrastructure initiatives. Specifically, for the integration, expansion, and buildout of additional capability/capacity within USSOCOM’s Regional Ground Entry Points (RGEPs) and DISA Large Satellite Gateways (LSGs). The intent is for this task order to provide the program management for all future task orders; if the Government determines additional need under this task order is required, a modification to this task order may be completed instead of awarding a new task order for the needed support. All work under this task order is advisory in nature and does not allow for the contractor to perform Inherently Governmental Functions.

1.2 Background

The DoD’s AISR Transport Infrastructure supports 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) assets tasked with the collection of intelligence information/data. The USSOCOM RGEPs and DISA LSGs are regionally positioned, globally connected, and afford downlink (via satellite terminals) and processing (via compatible gateway components) capability for distribution of the collected information/data into the hands of the intended consumer (e.g., supporting tactical forces, intelligence analysts, target engagement authority decision-makers) at the time, quantity, quality, and speed required to support their mission objectives. The ever-increasing demand signal for a wide variety of intelligence information/data continues to increase the numbers of assets employed to secure it and places an equally large demand signal for additional AISR Transport Infrastructure capability/capacity.

The execution of the associated integration, expansion, and preparation will necessitate a functionally oriented workforce with a wide variety of skills surrounding the AISR Transport Infrastructure capabilities and components, including but not limited to:

· Satellite Terminals in the forms of 6.3 Meter Commercial/Wideband Global SATCOM (WGS) Ka Fixed Satellite Subsystem Terminals (FSSTs), 6.3 Meter Commercial Ku FSSTs, and/or Ground Mobile Terminals (GMTs) with 3.9 Meter Quad-band Large Aperture Antennas (Q-LAAs)

· SATCOM Remote Video Terminals (SRVTs)/Predator Receive Terminals (PRTs) (if applicable) for unmanned asset support

· ArcLight2 (AL2) Hubs for manned asset support

· Unclassified and Collateral AISR Transport Convergence (UATCON & CATCON) Routers serving as distribution points of presence (PoPs) between USSOCOM’s RGEPs, DISA’s LSGs, and DISA’s Unified Video Dissemination System (UVDS).

The unique but mission critical nature of these AISR Transport Infrastructure components and the capability they provide predicates the demand for a highly skilled team of DoD-specific program/project management, integration/engineering, cyber security personnel as well as AISR Transport Infrastructure-specific subject matter experts.

1.3.2 The Contractor shall assist the Government with system/program management office (SPO/PMO) functions including:

1.3.2.1 Program Management – Provides Enterprise-level advice and assistance to ensure successful accomplishment of Government program manager initiatives and activities affecting the execution/implementation of AISR Data Transport Infrastructure. The Lead Integrator Program Manager possesses comprehensive knowledge of the enterprise architecture, baseline strategies, operations goals, and familiarity with all aspects of the functional/capability-oriented positions described below. The Lead Integrator Program Manager is the Government’s point of contact (POC) for all tasked deliverables, guides requirements definition and solution delivery, supports resource identification and execution, and assists in overall oversight and management of Lead Integrator activities supporting the AISR Transport Infrastructure. In addition, the Lead Integrator Program Manager assists Government program manager(s) in production/review of AISR Transport Infrastructure specific documentation/requirements, attends AISR Transport Infrastructure councils, boards, working groups, and integrated product teams.

1.3.2.2 Requirements Management – Provides management and assistance to ensure Government program manager(s) maintain cross-functional awareness of enterprise-wide requirements.

Proposes the Enterprise Requirements Plan (ERP) for solicited, unsolicited, validated and not yet validated requirements, and develops the format, template, and numbering scheme for solicited/submitted AISR Transport Infrastructure Requirements (e.g., 1067s, AISR Transport Change Requests {CRs}, etc.). Assists Government program manager(s) in the day-to-day management and execution of validated and resourced AISR Transport Infrastructure requirements.

1.3.2.3 Project Management – Assists the Government program manager(s) in the management of all enterprise-level implementations and/or site-specific capability/capacity projects supporting expansion of the global AISR Transport Infrastructure. Identifies technical, architectural, and systematic ways ahead for current and future integration activities, planned expansions, and/or site activations. Given the magnitude of the tasked effort, serves as the single point of contact (POC) (e.g., Site Activation Lead) responsible for coordinating with the Government customer(s) in the resolution of any planning, engineering, and/or logistical issues impacting terminal equipment, real property, and/or facilities, associated sensor data downlink/distribution/processing, and/or network components/terrestrial connectivity.

Interfaces and coordinates with site level communications, civil engineering, and supply personnel. Closely coordinates with the Government AISR Transport Infrastructure program manager(s).

1.3.2.4 Contracts Management and Auditing – Assists the Government program manager(s) in the solicitation and review of Performance Work Statements (PWS’) and Proposals for technical compliance, cost efficiency, and satisfaction of the validated AISR Transport Infrastructure requirement. Ensures vendor proposals account for/address location, facility, and environmental factors potentially impacting proposed materiel solutions (e.g., CONUS/OCONUS, ambient temperature, power conditioning/voltage/phasing, etc.).

Additionally, assists the Government program manager(s) with technically-relevant information either positively and/or negatively impacting performance assessment or invoicing.

1.3.2.5 Cost Estimating and Budgeting – Assists with cost estimation, budget development, tracking and managing, and the timely execution of resources allocated to Lead Integrator specific AISR Transport Infrastructure contract activities. Assists in the development of spend plans, reports on commitment/obligation rates for AISR Transport Infrastructure initiatives/activities.

Provides monthly updates to the Government program manager(s) focused on the proactive identification of any underrun/over execution issues/concerns potentially impacting the cost, performance, and/or timely for contracted activities.

1.3.2.6 Purchasing and Acquisition – Assists the Government program manager(s) in the identification of local, national, and international sources for services, personnel, and materials in order to support AISR Transport Infrastructure activities and initiatives. This includes identification of local sourcing to the extent possible (to reduce transportation time and costs) while ensuring compliance with applicable federal, DoD, and state directives and governance.

Maintains accountability for purchased items from initial order through delivery and introduction to the established Life Cycle Logistics/Integrated Logistics Support process(es).

1.3.2.7 Systems Engineering/Integration – Serve in an enterprise-level advisory and assistance capacity ensuring cross-functional awareness of wide-diversity of requirements, initiatives, and activities affecting the execution/implementation/operation of the AISR Transport Infrastructure. Dependent upon scope and breadth of activity, the Systems Engineering/Integration personnel possess significant subject matter expertise on the enterprise architecture, baseline strategies, and operational requirements for supported AISR assets (e.g., Manned, Unmanned, etc.), Radio Frequency (RF) terminal solutions/operations, OEM-specific downlink/processing gateways, black and red-side configurations, and/or terrestrial network connectivity and associated distribution solutions (e.g., DISA’ Unified Video Dissemination Solution {UVDS}). They coordinate/accomplish Government and OEM-centric lab activities and orchestrate controlled testing and pre-deployment analysis of proposed AISR Transport Infrastructure baselines and configurations, evolutionary technology insertion, new asset and sensor technologies, and sanctioned proofs of concept and pilot tests for AISR assets and the AISR Transport Infrastructure. Additionally, they assist the Government program manager(s) in reviewing documentation/requirements, and as required, attend/lead AISR Transport Infrastructure working groups, and integrated product teams, and assist with the production of briefings, papers, and other tasked deliverables to ensure cohesive, integrated requirements definition and solution delivery for AISR Transport Infrastructure functionality.

1.3.2.8 Test and Evaluation – Schedules and supervises controlled testing and pre-deployment analysis for proposed AISR Transport Infrastructure enterprise baselines and configurations, Security Technical Implementation Guides (STIGs) and Information Assurance (IA) hardening, evolutionary technology insertion, new asset and sensor technologies, and sanctioned proofs of concept and pilot tests. Works closely with systems engineering/integration personnel as they leverage Government and Industry lab environments to ensure thorough evaluation of proposed technology insertions, capability/capacity enhancements, and cyber security hardening in isolated industry-centric mockups and during scenario-based pre-operations deployment ensuring comprehensive documentation for test and evaluation criteria, performance, and exit/back out strategies.

1.3.2.9 Cyber Security (specifically, Risk Management Framework) – Oversees and manages Information Assurance (IA) and Certification & Accreditation (C&A) for Lead Integrator managed AISR Data Transport Infrastructure capabilities and commodities. Coordinates and ensures delivery of required OEM Risk Management Framework (RMF) packages to support operationally dictated and Certifying Accrediting Authority (CAA) specified timelines.

Coordinates and ensures delivery of asset and sensor based RMF documentation to ensure associated Approvals to Connect (ATCs) prior to authorizing access/connectivity to the AISR Transport Infrastructure.

1.3.2.10 Configuration Management – Provides Enterprise Configuration Management for implementation/execution of the AISR Data Transport Infrastructure. Proposes the Enterprise Configuration Management Plan (CMP), and develops the format, template, and numbering scheme for all required configuration management deliverables (e.g. 1067s, Deficiency Reports, AISR Transport Change Requests {CRs}, etc.), maintains a database/repository for submitted/approved deliverables, and ensures appropriate tracking of documents submitted/vetted for Configuration Control Board (CCB) approval.

1.3.2.11 Life Cycle Logistics/Integrated Logistics Support – Oversees activities including transportation, shipping, transportation, delivery, inventory, receiving, staging, storing, and warehousing for Lead Integrator managed AISR Data Transport Infrastructure capabilities and commodities. Facilitates Customs processing, receipts for shipments, and provides verification of inventories (to include spares). Ensures components remain under positive control and remain viable from “cradle to grave”—this includes final disposition for excess, unserviceable, and/or no longer required items.

1.3.3 The Contractor shall maintain all project related documentation from start to finish and develop new AISR Transport Infrastructure Gateway artifacts supporting Configuration Management (CM) and the Risk Management Framework (RMF) programs.

1.3.4 The Contractor shall advise and assist the government with the PMO management documentation including standardizing existing checklists, operating instructions, and support agreements, including local service level agreements (SLAs) and MOAs established between the host facility organization and USSOCOM/DISA.

1.3.5 The Contractor shall advise and assist the government with contracting and finance documentation required to support AISR purchases; this includes assisting in the preparation of Statements of Work, Performance Work Statements, Cost Estimates, and Technical Evaluations in terms of determining technical specifications.

1.3.6 The Contractor shall support the pre-existing USSOCOM AISR Sensor Data Transport Infrastructure and its supporting communications architecture (e.g., UVDS connectivity). This includes assisting with the sensor producing platform integration, the SATCOM ground terminals used to downlink the produced sensor data, the processing and distribution ground entry point/gateways used to process and distribute the sensor data, and the terrestrial transport used to route/deliver the processed sensor data to/with/among the intended/authorized consumers.

1.3.7 The Contractor shall support DISA’s AISR Sensor Data Transport Infrastructure and its supporting communications architecture (e.g., UVDS connectivity). This includes assisting with the sensor producing platform integration, the SATCOM ground terminals used to downlink the produced sensor data, the processing and distribution ground entry point/gateways used to process and distribute the sensor data, and the terrestrial transport used to route/deliver the processed sensor data to/with/among the intended/authorized consumers.

1.3.8 The Contractor will provide planning, engineering, oversight, and management for fully integrated, “turn-key” AISR Transport Infrastructure Gateway installations (e.g., USSOCOM RGEP and/or DISA ISR Ground Entry Points IGEP) at new facilities/locations as awarded in subsequent task order awards.

1.3.9 In addition to the fixed RGEP and DISA IGEPs, the Contractor will assist with the planning, engineering, oversight, and management of a mobile/deployable variant. This variant would entail similar planning, engineering, logistics, acquisition of required ODCs, 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.

1.3.10 The Contractor will provide 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.

1.3.11 Specifically, the Contractor will assist the Government with the planning, engineering, oversight, and management for integration and operationalization of:

1.3.11.1 Legacy and current US Air Force (USAF) and US Army unmanned asset downlink, processing, and distribution supporting a wide variety of sensor data (including standard definition and high definition full motion video), proprietary waveforms, and/or Type-1 encryption technologies.

1.3.11.2 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.

1.3.11.3 Network transrate/transcode capabilities 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.

1.3.11.4 Collateral 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.

1.3.11.5 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.

1.4 General Performance Requirements Resources

1.4.1 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 PWS.

1.5 Government Furnished Equipment (GFE)/Government Furnished Information (GFI)

1.5.1 The Government will provide Common Access Cards (CACs) to Contractor individuals who have a valid need for them in order to perform their duties to meet the requirements on this contract.

1.5.2 The Government will provide a SOFNET-S connection, SOFNET-S terminals, and secure email accounts for Contractor personnel with the proper clearance and need-to-know to process, transmit or store classified data related to any OEM-specific (Contractor) cybersecurity support activities. The Contractor shall provide an approved secure area/room for this equipment.

1.6 Site Security

1.6.1 The Contractor shall abide by and follow all local site security plans and procedures including facility, physical, and/or personnel security requirements documented in the Site Security Plan (SSP) and Risk Management Framework (RMF) package.

1.7 Program Management Support

1.7.1 The Contractor shall provide USSOCOM/DISA program/project management personnel with current and relevant levels and breadth of acquisition and program management experience and expertise.

1.7.2 On a monthly basis, the Contractor shall be responsible for providing a summary of financial expenditures (e.g. travel).

1.8 Site Installation Support

1.8.1 The Contractor shall assist the government with OEM Contractor support with pre-install, install, and post site installation support for AISR equipment. The Contractor shall assist with installation management and verification of OEM installs upon completion of the installation the systems shall:

1.9 Security Requirements

1.9.1 Cybersecurity Requirements. The Contractor shall ensure that all personnel that require privileged access to the site computing or networking environment meet, or shall meet with 6 months of assignment, the certification requirements established in DoD 8570.01-M. The Contractors shall assess the specific functions performed by OEM-specific Senior Technician(s) in the positions and how they best align with those identified in the Table C3.T5 in DoD 8570.01-M. This table describes tasks performed by IAT Level II personnel, at minimum, that provide network environment (NE) and advanced level CE support.

1.9.2 The Contractor shall ensure all individuals who fill these positions meet the requirements of Table C3.T4 in DoD 8570.01-M and hold DoD approved 8570 baseline certifications for IAT Level II as identified in the table on the DISA IASE website at https://iase.disa.mil/iawip/Pages/iabaseline.aspx. The Contractor shall verify that each individual has obtained at least one of the certifications listed in this table for IAT Level II or III and has maintained the certification status through continuous education or sustainment training. If an OEM-specific Senior Technician does not hold any of these certifications, then the Contractor shall ensure that he or she obtains the CompTIA Security + CE certification within 6 months of assignment. The Contractor shall annually review the certification status of all personnel assigned to support AISR sites to ensure their certifications are active.

1.10 Deliverables

Monthly Status, Labor Hour, and Expenditure Report (MSR)

Monthly 15th day of the Month submitted in ITSS/ASSIST in and to the Government POC.

Invoices

15th day of the Month submitted in ITSS/ASSIST in and to the Government TPOC.

submitted in ITSS/ASSIST in and to the Government TPOC

15th day of the Month submitted in ITSS/ASSIST in and to the Government TPOC.

15th day of the Month submitted in ITSS/ASSIST in and to the Government TPOC.

1.11 Travel

All travel must be coordinated and authorized by the Contracting Officer (CO), the Contracting Officer’s Representative (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. 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:

1.12 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.

1.13 Location of Performance

1.13.1 As required to support PWS requirements at the following locations to include: MacDill AFB, FL, Pope Army Air Field (AAF) NC, Hurlburt Field FL, Ramstein Air Base (AB), Germany; Kadena AB, Japan; Sigonella, Sicily (Italy) and other locations as specifically tasked/funded by the Government. The locations listed above are current, however the locations are subject to change given the evolving real world events.

1.14 Security Requirements

1.14.1 Shall require a Top Secret SCI clearance.

1.15 Nonpersonal Services

1.13.1 This contract is a “non-personal services contract” as defined in FAR 37.101. It is, therefore, understood and agreed that the Contractor: (1) shall perform the services specified herein as an independent Contractor; (2) shall be responsible for their own management and administration of the work required and bear sole responsibility for complying with any and all technical, schedule, or financial requirements or constraints associated with performance of this contract; (3) shall be free from supervision or control by any Government employee with respect to the manner or method or performance of the services specified; but (4) shall, pursuant to the Government’s right and obligation to inspect, accept or reject the work, comply with such general direction of the Contracting Officer, or the duly authorized representative of the Contracting Officer as is necessary to ensure accomplishment of the contract objectives.

1.16 Meetings

1.16.1 Kick-Off Meeting. Within 15 days of award, the Contractor shall coordinate an Overall Task Order kickoff meeting, at which time all parties involved in the Task Order execution shall be represented and roles/responsibilities clearly outlined. During the kickoff meeting, the Contractor shall be prepared to discuss the Task Order at the parent level as well as details for each technical activity. In addition, individual technical activity area kick-off meetings shall occur for every funded area. The intent of the technical activity area kick-off meeting is to review the sub-task schedule, objectives of each technical activity area, and review roles and responsibilities of the players.

1.16.2 Meetings. The Contractor shall plan to participate in monthly and quarterly progress meetings, detailing the progress, issues, needs, and/or unforeseen items that occur. The Contractor shall be responsible for coordinating and scheduling all meetings; however, the Government Technical Point of Contact (TPOC) shall maintain approval authority for date, time, and location of all meetings. The Contractor shall prepare appropriate status documentation in advance of any meeting for Government TPOC approval. The Government TPOC has authority to attend or not attend any scheduled meetings. The Contractor shall capture and track all action items, decisions, and minutes from all meetings and telecoms. A detailed review of each technical activity area shall be required.

1.17 ODCs:

The Government may require the contractor to purchase materials and equipment and ODCs, to include hardware, software, and related supplies critical and related to the services being acquired under the contract/order. Such requirements will be identified at the time the contract/order is issued or may be identified during the course of a contract/order by the Government or the contractor. The Contractor must obtain permission from the CO prior to incurring any ODCs with a value over $250,000.00. If the contractor has an approved purchasing system, they shall submit the Request to Initiate Purchase (RIP) (PWS Attachment D). If the prime contractor does not have an approved purchasing system, they shall submit Consent to Purchase (CTP) (PWS Attachment E). The RIP and CTP shall include the purpose, specific items, estimated cost, cost comparison, and rationale. The contractor shall not make any purchases with a value above $250,000.00 without an approved RIP or CTP.

1.18 Period of Performance:

The Period of Performance shall be a 12 Month base period with four (4) additional 12 month option periods.

1.19. Special Instructions:

All terms listed in the base IDIQ Performance Work Statement are applicable.

1.20. PWS Attachments