Attachment_P12_Sample_Task_Order_3_PBSOW.docx

UNCLASSIFIED

FOR OFFICIAL USE ONLY

TASK ORDER #3 (SAMPLE)

TASK ORDER TITLE: Laboratory Simulator Development

Reference: 1) Statement of Work for Contract N00421-15-R-0016

1.0 INTRODUCTION: The Laboratory Simulator Development project supports the Naval Air Warfare Center (NAWC) laboratory and installed system test facilities. This effort shall be funded with increments. Periodic reviews shall be conducted to determine if additional funding is necessary and appropriate in subsequent fiscal years.

1.2 (U) SCOPE: This Task Order (TO) covers the development and improvement of a laboratory simulator for the Air Combat Environment Test & Evaluation Facility (ACETEF). The overall effort includes the administration and management to update the simulator, as well as the detailed design, development, and implementation of updates to the hardware and software components required for the simulator. Additionally, this TO includes detailed design and development of updates to the environment simulation portion of the system, as well as for the delivery, on-site installation and integration, system validation, training, and documentation of the system.

2.0 REFERENCE DOCUMENTS: The Government will provide system description documentation. The Government will provide all necessary reference documents not generally available to the Contractor as required. Throughout the life of this TO, if any instruction or document is replaced or superseded, the replacement or superseding instruction or document shall be applicable to the requirements defined in this TO.

3.0 TECHNICAL REQUIREMENTS: The contractor shall update, test, and deliver one laboratory simulator system. This simulator shall emulate:

· The receiving, processing, display and control contained in the actual system to include functional interfaces to external systems and other simulators where applicable.

· The environmental simulation required to support installed system testing.

The following paragraphs in this section detail functionality and tasks that are required to complete the laboratory simulator system development.

3.1 PROGRAM MANAGEMENT: The contractor shall prepare and execute a program management plan. A draft program management plan shall be submitted within 30 days of TO acceptance. The plan shall include a work break down structure, schedule, resources (labor and materials) and appropriate cost and schedule controls. Program management shall also include a monthly report on all tasks to the Government. The contractor shall maintain an overall schedule and budget and shall provide the progress of the overall task versus planned schedule. (CDRL A003; A005; A007)

3.2 SYSTEMS ENGINEERING: The contractor shall develop detailed design requirements; hardware, firmware, and software subsystem definitions; as well as the unit and integrated testing of these implementations. The contractor shall incorporate sustainability, maintainability, and configuration management best practices wherever feasible and appropriate. Cost and performance tradeoffs and testing priorities approved by the Government shall be incorporated by the contractor into the detailed system requirements and design. The implementations shall meet the system performance parameters established at a Critical Design Review (CDR) within the constraints defined by the tradeoffs noted above. The contractor shall provide system information and data to support the system validation process. The contractor shall also design, implement and document calibration procedures and operational test procedures for the laboratory simulator system. (CDRL A003; A007)

3.3 COMPONENT, INTERFACE AND FUNCTIONS DEVELOPMENT: All component interfaces will be designed and documented in accordance with the guidelines established by the development team. Interfaces and data structures used by the system shall be approved by the Government prior to implementation. Unless otherwise stated, the Contractor shall include all required power supplies, equipment racks and internal cabling. All material purchase orders shall be approved by the COR prior to execution. (CDRL A003; A004; A007)

3.4 INTEGRATION AND TEST: The Contractor shall conduct factory and on-site integration and testing. The contractor shall provide hands-on training to Navy personnel as part of the integration and test activity. The contractor shall deliver an Acceptance Test Plan and conduct the test as specified in the plan. Upon completion of acceptance, the contractor shall deliver an Acceptance Test Report. Separate test procedures and test result reports will be delivered by the contractor for both the Factory Acceptance Test (FAT) and Site Acceptance Test (SAT). Detailed test plans for factory and on-site testing shall be prepared and submitted for approval no later than 30 days prior to scheduled testing. FAT shall also include selected sections from any prior FAT to ensure that the original functionality and performance has not been degraded during this update effort. SAT plans and procedures will be generated from a subset of the FAT plan and procedures with additional test plans and procedures for those functions and interfaces that are only operational on site. The repetition of FAT procedures should demonstrate that system functionality and performance has not degraded during shipping and site installation. Upon completion of FAT or SAT, any necessary updates to the system will be documented along with any other CM requirements. (CDRL A003; A004)

3.5 DOCUMENTATION: For those components that are to be delivered, the Contractor shall prepare and deliver an Interface Control Document (ICD) detailing all external interfaces and schematics. These include all electrical and mechanical connections. External electrical and mechanical connections and interfaces shall be non-proprietary. Schematics (soft copy, if available) shall be of generally accepted industry standards and reflect details to the component level. The contractor shall provide any documentation, source code, etc. required to program copies of any programmable logic circuit devices. The contractor shall deliver the source code in electronic format for all contractor developed software and firmware. The contractor shall document all hardware designs and interfaces in the form of Development Drawings. The data package shall include diagrams, mechanical and electrical drawings and schematics. Commercial, off-the-shelf components shall be cited by vendor information on the assembly drawing(s) and commercial documentation for the equipment shall be provided. The contractor shall also prepare a User’s Guide that shall be of sufficient detail to operate, maintain, and repair to the component level. (CDRL A003; A007; A008; A009)

3.6 VALIDATION: The contractor shall support Initial Operating Capability (IOC) simulator validation by providing all necessary design and measured parametric data to conduct validation in accordance with applicable instructions. The general nature of this support is expected to include performing analyses, responding to specific documentation requests, and reviewing material generated by the designated validation personnel. Required parametric data will be identified by the Government 30 days prior to scheduled FAT. (CDRL A004)

3.7 MONTHLY COST AND PERFORMANCE REPORTS: The contractor shall provide monthly cost and performance reports (CDRL A001). This report should include, but is not limited to the following:

· Budget & Amount Funded

· Amount Invoiced Reporting Period/Cumulative

· Labor/ODC Utilized Reporting Period/Cumulative

· Technical Progress

· Articulate technical progress made and any significant accomplishments

· Include cost/schedule status

· Identify problem areas with recommended solutions

· Deliverables generated

· Brief summary of plan for next reporting period

3.8 REVIEWS: The contractor will conduct, as required, technical meetings to facilitate the exchange of technical information and enhance effective communication among all interested parties authorized by the COR. Anticipate four milestone reviews as well as five quarterly reviews. The contractor shall also present program management reviews (PMRs) to designated government representatives that shall include a summary of technical achievements, schedule status, and cost performance. These reviews shall emphasize progress and problems since the last meeting, plans for the future and establish the date and place for the next meeting. In addition to the PMRs, the contractor may be required to conduct formal oral and visual presentations to invited government and industry representatives. The contractor shall provide Conference Agenda, Presentation Materials and Conference Minutes. (CDRL A002)

3.9 SOURCE CODE DELIVERY: The contractor shall provide the source code for all software developed in the design, development and delivery of the system in electronic format. (CDRL A008)

3.10 (U) FINAL REPORT: At task completion, the contractor will complete and submit a Final Report (CDRL A010).

4.0 PLACE OF PERFORMANCE: Work is to be performed at the Naval Air (NAVAIR) Systems Command in Patuxent River, MD and within properly cleared contractor support facilities.

5.0 (U) TRAVEL: The Government will reimburse the contractor for allowable travel costs incurred by the contractor in performance of the order in accordance with FAR Subpart 31.2 and FAR 52.232-22. Travel will be coordinated with and approved by the COR prior to travel. Contractor travel is anticipated to Washington, DC, Lakehurst, NJ, Patuxent River, MD and Point Mugu, CA. Travel to other locations may be required. (CDRL A006)

6.0 PERIOD OF PERFORMANCE: The period of performance for this effort is from award to award plus 12 months.

7.0 Funding

Anticipated funding levels for this Task Order are listed in the Table below. All funds will be RDT&E.

Base Year x/xx/2016 - x/xx/2017 Option Year 1 x/xx/2017 – x/xx/2018 Option Year 2 x/xx/2018 – x/xx/2019

Labor

Travel

Material

NMCI

8.0 Points of Contact

Technical points of contract for this task order are: