Attachment_9_Statement_of_Work_(Revised_24_Nov_14).doc

Attachment 9 Statement of Work, 7 Pages, 21 Nov 14

STATEMENT OF WORK

FOR

AFSOC REMOTELY PILOTED AIRCRAFT OPERATIONS CENTERS

GROUND CONTROL STATION CONVERSION

CANNON AFB, NM

1. Overview

1.1. To enable the effective implementation of the designed enterprise infrastructure and as a result enable the operations of Ground Control Stations (GCSs) to interface with the MQ-1 Predator and MQ-9 Reaper weapons systems, conversion of Mobile Ground Control Stations (MGCSs) to a Fixed Ground Control Station (FGCS) configuration is required. These converted GCS units will be installed in a security- and flight-certified configuration inside building 848, in the new RPA Operations Center (ROC) at Cannon AFB, NM. The primary work areas will be within buildings 780 and 848 at Cannon AFB. Room 157 of Bldg. 848 will be provided as required to accomplish required staging activities. Due to limited space available to perform GCS conversion activities and ongoing combat mission requirements, conversions will only be performed on one MGCS at a time, with additional staging and parallel activity as authorized by government personnel.

2. GCS Conversion

2.1. The contractor will convert seven (7) existing Block 15 Mobile Ground Control Station units to Fixed Ground Control Station for Cannon AFB. Converted GCSs must contain all required SOF modifications (as documented in applicable 1067, red-line T.O., etc.) and related required components as specified by Contract Officer Representative (COR) and/or Contracting Officer (CO). The contractor will install MGCS hardware into a Fixed Facility suite and assist with all required validation of solution by coordinating re-certification thru System Program Office Detachment and other government representatives, as directed by CO or COR. This modification will be performed jointly in coordination with contracted and government sustainment and Depot-level activity support personnel. Note: The depot level activity is the entity that performs Air Force acceptance and certification of all GCS for flight operations. Contractor is responsible for integration and configuration of the converted GCS units into the larger operations center facility to the extent applicable to organizational-level authorized activities and as otherwise directed by CO or COR. Please see attachment 2 GCS Conversion Proof of Concept and List of Materials.

2.1.1. MGCS Relocation. At Cannon AFB, contractor is responsible for relocating MGCS unit from current location behind building 780, over to the designated area in building 848 prior to commencing de-integration effort. This will include one MGCS unit already converted into a FGCS configuration as a proof-of-concept (inside building 780).

2.1.2. MGCS de-integration. Contractor will identify, disconnect and remove all wire harnesses; fiber and cable connections, hardware components, infrastructure, and all related sub-assemblies in accordance with applicable weapon system technical orders and associated documentation. De-installation of required components from the MGCS will include (but is not limited to):

2.1.2.1. Removal of Multi-Function Workstation (MFW) racks; disconnect and remove all components, infrastructure, and line-replaceable units (LRU) from MFWs as required; and disconnect MFW rack assembly from shock mounts and remove from MGCS. Contractor must accomplish these actions for all components, to include MFW3, MFW2, MFW1, and Aux rack assembly.

2.1.2.2. Removal of Pilot/Sensor Operator (P/SO) seats, floorboards and center console/tracks.

2.1.2.3. Remove PPO1/2 CCA, foot pedal, Heads-Up Display (HUD), tracker, Keyboard Video and Mouse (KVM) switches and assemblies, and aux monitors; identify and remove all applicable wire harnesses, fiber and cable connections from PPO1; remove PPO1/2 Rack assembly.

2.1.2.4. Remove and disconnect center rack LRU's and VME's; identify and remove all associated wiring harnesses, fiber and cable connections; and remove Center Rack Assembly.

2.1.2.5. Remove remaining harnesses, fiber, cabling, and floor mounted ICU. Attach all racks to base assemblies and re-install LRU's/wiring in reverse order of removal.

2.1.3. Installation. Contractor will conduct equipment movement from conversion area and perform installation activities in the fixed-facility configuration. Placement of systems and equipment in fixed facility suites will be in accordance with specified physical configuration (see attachment 3 GCS Room Layout). Fixed configuration installation will include the re-integration of all GCS components and subcomponents as outlined in 2.1.1. Re-integration will match approved component integration as depicted in T.O. 1Q-1(M)B-2-2 and related technical specifications, and will include all special weapons system modifications as documented by the Special Programs Officer (SPO) via AF Form 1067 or authorized government personnel designated by the COR in 27 SOW/XP.

2.1.4. Configuration. With the exception of the items listed in Section 5 Government-Furnished Property (GFP) and Attachment 4- Government Furnished Materials, the contractor will acquire, install and perform all additive equipment and/or modifications as necessary to implement FGCS configuration of the GCS system, to include machining and/or other electrical and physical modification where required. Physical modifications to the GCS systems that are not already specified within technical orders and other GCS-system associated specifications must be reviewed by the COR prior to execution. The work to be performed to execute this conversion will include the procurement and installation of required assemblies and components to convert MGCS units to match current FGCS model as specified by appropriate technical instruction and related approved modifications. All applicable maintenance actions will follow T.O. 1Q-1(M) B-2-2, as well as operational check of all systems.

2.1.5. Transportation. The contractor shall provide all necessary equipment to perform the required service.

2.2. Certification. Following conversion and integration with supporting infrastructure, the contractor shall perform systems testing prior to the first flight of an aircraft to guarantee safety and ensure operational success. To demonstrate airworthiness before going operational, GCS will be qualified by acceptance test procedure (ATP) for MD-1A/B ground control station, as referenced in applicable T.O., ASI-02378, and with variances only as authorized by the government; contractor will coordinate with COR on a case-by-case basis as required. Installation and configuration activities will be in accordance with all applicable regulations and government guidance, to include but not limited to: Institute of Electrical and Electronics Engineers (IEEE) standards 1428-2004, 802.3-2012, 802.3-2008, C57.12.70-2011, and 1156.2-1996, except as waived or amended by CO and COR.

2.2.1. All contract activities must be available for inspection at all times by engineering, sustainment, operations, and security teams. Contractor will be responsible for implementing fix actions necessary to correct noted deficiencies validated by COR.; identified deficiencies will be corrected as soon as feasible, but in all cases within 5 days of notification unless otherwise coordinated with COR.

2.2.2. Contractor technical personnel must be available for configuration operational tests and system functional evaluations as required to support ad-hoc system configuration and related conversion issues, up to and including active mission operational validation.

2.3. Notice to Proceed. Due to operational need, the government may allow no more than 1 GCS system to being converted and moved at a time but more or less are possible depending on Government discretion and associated contractor agreement. Conversion of a second GCS may begin while previous GCS is in the certification process as coordinated with the COR. The contractor must receive a notice to proceed before they move on to converting the next GCS unit. The limiting factor will be the number of operational GCS units, so that will be the factor used for notice to proceed. The Contracting Officer Representative (COR) in coordination with the Contracting Officer (CO) will provide the authorization needed to move the GCS being converted from their current location to the new location.

3. General Information

3.1. Project Manager. The contractor shall provide an on-site project manager who shall be responsible for the schedule and performance of this requirement. The project manager shall directly interface with the COR to coordinate project execution and integration requirements.

3.2. Security. To support operation and conversion in an active TS/SCI environment, all personnel conducting modification and installation activities must possess an active TS/SCI clearance. Contractor will coordinate with COR to get focal point read-in required to operate in ROC and SOC facilities. The Government will be able to provide all requested TS/SCI read-ins the contractor may require for eligible personnel. Refer to ICD 503 and related security regulatory guidance for additional security requirements. Contractor personnel shall report security problems to the supporting Special Security Office and/or Security Police as appropriate and notify COR and CO no later than the next business day.

3.2.1. The contractor shall provide measures that ensure the confidentiality, availability, and integrity of classified and sensitive information processed by, stored in, and moved through the operations centers systems and applications. The contractor shall follow all necessary procedures to protect operations centers systems through proper cryptographic and boundary control interconnections using effective security procedures to include Communications Security (COMSEC) inventory, installation, and destruction of encryption material.

3.3. Turnover. Contractor must perform a turnover action with the existing RPA Operations Center/Squadron Operations Center (ROC/SOC) sustainment contractor for each GCS delivered. This is meant to be done during operational validation and is necessary for the sustainment contractor to be familiar with the specific GCS to be supported and to ensure proper system support can occur after completion of conversions contract. Contractor will additionally submit a Phase-Out Plan for contract completion tasks 45 Days Prior to contract expiration. The requirements for the plan will be detailed in a CO tasking letter. At a minimum, it is anticipated the following items will need to be addressed in the plan: identification of all tasks required for complete contract transition, joint inventory of all assets involving government and contractor personnel, transfer of publications, and identification of data records.

3.3.1. Upon verification and certification of installed converted GCS units to resume active flight operations in new configuration, the contractor will turnover equipment and all related documentation within 14 days. Contractor will deliver any updates to hardware/software configurations resultant from conversion activities, in conformance with existing configuration and other mandatory documentation, to be maintained as part of the overall RPA operations center infrastructure configuration management plan.

3.4. Contractor employees who will handle the physical conversion must have a minimum of 3 years’ experience working on MQ-1 Predator and MQ-9 Reaper systems with relevant experience modifying ground systems to include modification and de-modification of system components to include platform IT configuration and a minimum two contractor employees must have Security + certification. These individuals must be dedicated solely to this requirement. Support personnel such as Logistician or Technical Writers will not be required to have the minimum of 3 years’ experience since their function will be to supportive in nature and will not have to be solely dedicated to this requirement. Multiple shifts will be authorized and Bldg. 848 will be available 24hrs.

4. Meetings

4.1. Technical Meetings. The contractor shall attend and participate in government-organized Technical Interchange Meetings (TIMs) and Integrated Product Teams (IPTs). The number of technical meetings is estimated at four (4) per month. Technical meetings will be held at Cannon AFB, NM or via telephone conference based on coordination with COR.

4.2. Project Management Review (PMR). The contractor shall attend Project Management Reviews when scheduled by the COR. If the contractor is requested to brief by the COR, they will provide a copy of their intended briefing to COR and requesting office a minimum of two workdays prior to brief. The contractor shall provide minutes with decisions and action items for all meeting held to the COR. Minutes are due no later than 10 workdays after event in electronic format. PMRs will be held at government discretion, and are estimated to be once a month.

5. Government-Furnished Property (GFP)

5.1. Government-Furnished Equipment (GFE). The government shall provide the contractor with access to common user computer terminals and SOF-specific software, as required for performance of contract activities, to include SIPRNET and unclassified internet accounts. Contractor personnel requiring accounts will coordinate with COR to complete required documentation prior to being authorized access to government networks. The government shall provide two SIPRNET Computers, two NIPR computers, one phone, two desks, and 200 sq. feet of office space and routine office supplies for contractor personnel working in the government's facilities. Additional GFE shall include access to printers (black and white and color), facsimile machines (unclassified and classified), document reproduction machines, classified storage, and shredders for destruction of classified material.

5.2. Government-Furnished Information (GFI). The government shall provide the contractor with GFI, as required, to meet the tasks as defined and to prepare contract deliverables. GFI includes, but is not limited to, operations centers layout diagrams, system employment schedule, and initial equipment inventory.

5.3. Government-Furnished Services (GFS). The government shall provide Common Access Cards to all personnel assigned on-site. Contractor must apply and complete requirements to be issued a CAC. The government shall provide appropriate facilities for any storage or warehousing of mission equipment procured under this contract, as deemed sufficient by the government.

5.4. Government-Furnished Materials (GFM). The government shall provide all long lead time materials required for conversions, as referenced in Attachment 4, Government Furnished Materials. The materials listed in Attachment 4 will be provided for each GCS conversion, for a total of 7 GCS conversions all together at the time of the first conversion. The Government will give the contractor three weeks’ notice on the availability of all the items listed in Attachment 4.

6. Contractor Manpower Reporting Language for Contract Performance Work Statements and Related Background Information. "The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the United States Air Force via a secure data collection site. The contractor is required to completely fill in all required data fields using the following web address: http://www.ecmra.mil/

Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year, beginning with 2013. Contractors may direct questions to the help desk at help desk at: http://www.ecmra.mil/.

7. Deliverables

7.1. Documentation. The government shall retain unlimited rights to all iterative and final deliverables derived from this requirement. Upon modification, this data will be entered on the applicable AFTO Form 95/AFTO Form 781 and automated database(s) as required. Each modification will be documented to ensure conformity to all approved procedures, to allow for review and approval by technical, engineering, safety, security, and operations personnel.

7.2. Quality Control Plan. The contractor shall develop and implement a Quality Control Program. As part of the program, the contractor shall develop a Quality Control Plan, which identifies the processes and procedures for producing defect-free services and for preventing defective services from recurring. The contractor shall submit the plan as part of their proposal. The contractor shall revise and update the plan as needed and submit to the CO for acceptance.

7.3. Delivery Schedule. The contractor shall provide a matrix of contract deliverables that includes title, initial delivery date, date provided, date returned for correction (if applicable), date resubmitted, date approved by designated government representative, subsequent delivery dates projected, and any additional remarks.

7.4. Contract Schedule. The contractor shall develop a Contract Schedule that adheres to the delivery milestones of each GCS conversion as detailed in Attachment 1 Gantt Schedule. The Contract Schedule shall contain work element milestones and the percentage of effort required for each work element. All conversions must be completed IAW the period of performance presented in the Gantt Schedule. The contractor shall submit the initial schedule as a Microsoft Project in PDF format as part of their proposal. Contract schedule shall identify any discrepancies outside contractor control and required delivery dates for each respective item. The contractor shall update the percent of the project completed monthly and submit as an attachment to the Monthly Report.

7.5. Monthly Report. Contractor shall submit a monthly report NLT the 15th of each month detailing all work completed to date, planned actions in the next period, government and other dependencies, as well as projected project schedule and related updates as applicable. Contractor should provide additional interim updates as needed to ensure on-schedule delivery of systems, as required, at technical integration meetings (TIM); outlined in 4.1.

7.6. Organizational Conflict of Interest Plan. The recommended course of action for avoiding, neutralizing, or mitigating the organizational conflict of interest, based on the general rules in FAR 9.505 is to require each interested vendor to submit an OCI Plan as part of their proposal. Even if an offeror doesn’t feel they have any OCIs, they must submit a plan on how they plan to avoid any OCIs if any do arise before or after award. The contractor must clearly address all potential organizational conflict of interests and how they plan on avoiding them, also the contractor must ensure personnel tasked against this effort are required to be dedicated to it. The government defines dedicated employees as those who will handle the physical conversion and are required to have a minimum of 3 years’ experience working on MQ-1 Predator and MQ-9 Reaper systems with relevant experience modifying ground systems to include modification and de-modification of system components to include platform IT configuration as outlined in Section 3.4. Dedicated employees will not include support personnel such as Logistician or Technical Writers who will act in a supportive nature to this requirement as outlined in section 3.4.

7.7. As-built Diagrams and Technical Data. The contractor shall submit complete as-built drawings and technical data for each installed system not later than 14 calendar days after installation is completed and GCS has been certified as per process outlined in para 2.3. The drawings shall show the location and configuration details of all equipment and shall include an equipment listing with serial/model numbers, and specifications. Drawings shall also show and detail the physical installation of GCS MFWs and P/SO racks and stations in the FGCS suite, the attachment of these into the fixed facility suite infrastructure, the placement of electrical connections for the systems, and the communications connections associated with each installation. The contractor shall use other available technical data to understand and maintain the system for all installed equipment not organic to the weapons system. All hardware and software configuration documentation, to include specific as-activated settings and related installation/activation data shall be included. Any corrections or changes to the diagrams after initial submission will be coordinated by the contractor with the COR, and shall be submitted no later than 5 business days after notification of change requirement. All drawings and as-builds shall be provided in Visio format.

8. References

IEEE Standards 1428-2004: IEEE Guide for Installation Methods for Fiber Optic Cables in Electric Power Generating Stations and in Industrial Facilities (Section 2.3 Certification) IEEE Standards 802.3-2012: IEEE Standard for Ethernet (Section 2.3 Certification)

IEEE Standard 802.3-2008: IEEE Standard for Information technology--Telecommunications and information exchange between systems--Local and metropolitan area networks--Specific requirements Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications (Section 2.3 Certification)

IEEE Standard C57.12.70-2011: IEEE Standard for Standard Terminal Markings and Connections for Distribution and Power Transformers (Section 2.3 Certification)

IEEE Standard 1156.2-1996: IEEE Standard for Environmental Specifications for Computer Systems (Section 2.3 Certification)

T.O., ASI-02378 (Section 2.3 Certification)

T.O. (1Q-1(M) B-2-2) (Attachment 2- GCS Conversion Proof of Concept and List of Materials) List of Attachments Attachment 1- Gantt Schedule Attachment 2- GCS Conversion Proof of Concept and List of Materials Attachment 3- GCS Room Layout Attachment 4- Government Furnished Materials

UNCLASSIFIED