PBWS for EGI Contract

PR # FD2060-11-30649 1

PERFORMANCE-BASED WORK STATEMENT

(PWS)

of the

Embedded Global Positioning System Inertial Navigation System (EGI)

PR # FD2060-11-30649 2

HEADQUARTERS

AEROSPACE SUSTAINMENT DIRECTORATE

ROBINS AIR FORCE BASE, GEORGIA 31098-1813

PR NUMBER: FD20601130649 DATE 25 July 11

PERFORMANCE-BASED WORK STATEMENT (PWS)

TYPE WORK: This effort is for the modernization, integration, fabrication, test, qualification, and support of a standard EGI. This PWS identifies program requirements essential to continue production and sustainment of an EGI to meet multiple platform requirements.

CONTENTS

SECTION TITLE

SECTION 1 DESCRIPTION OF SERVICES 3

PAGE

SECTION 2 SERVICES SUMMARY 9

SECTION 3 GOVERNMENT FURNISHED PROPERTY AND SERVICES 9

SECTION 4 GENERAL INFORMATION 10

SECTION 5 APPENDICES 20

DISTRIBUTION STATEMENT C: Distribution authorized to U.S. Government agencies and their contractors (Administrative or Operational Use). Other request for this document shall be referred to WR-ALC/GRWBCA, Robins AFB GA 31098-1813

PR # FD2060-11-30649 3

1.0 DESCRIPTION OF SERVICES

1.1 Scope

This PWS defines contractor’s tasks for the integration, modernization, fabrication, test, qualification, repair, and support of a standard EGI. This PWS identifies program requirements essential to continue production and sustainment of an EGI to meet multiple platform requirements. However, not all the provisions in this PWS apply to each delivery order. Each Platform/User will submit individual decentralized delivery orders that will specify which PWS provisions apply.

1.2 Prime Mission Equipment

The Prime Mission Equipment (PME) shall be an EGI in a single Line Replaceable Unit (LRU) that meets the requirements as defined in each platform Prime Item Development Specification (PIDS). The current and future supported platforms are listed in Table 1. This list of platforms is not all encompassing.

TABLE I: Current and future Platforms for EGI Installation

ARMY NAVY AIR FORCE OTHER

AH-64D

OH-58D

MH-47

MH-60

MH-6

UH-60

CH-47F

AH-6

UH-60M

HH60-M

JPALS

SOA P31

AH-1W

F-14 F-18

S-3B

VH-60N

C-2/E-2

CH-53E

CH-53K

UCAS

ES-3A

UH-1

UH-1Y/Z

H-53

CH-46

LCAC

A-10 F-15 F-16

KC-135

C-130-J C-27

HH-60J (USCG)

HH-65 (USCG)

HC-144A (USCG)

MH-F60T

* Note: This list of platforms is not all encompassing.

1.2.1 Group B Integration Components

As required by individual delivery order, the contractor shall fabricate, test, and deliver the EGI in compliance with requirements contained in the Prime Item Development Specification (PIDS).

The PIDS shall be based on the contractor’s Non-Developmental Item (NDI) system. The EGI shall be integrated as necessary to meet the requirements of each specific platform PIDS.

Integration provides non-recurring efforts required for hardware and software modifications necessary to a core EGI for use on a specific platform. Integrations require only changes to the existing core EGI software and hardware to permit physical and electronic interface with the platform. Modernization provides for the retrofit, modification, or upgrade of an existing

PR # FD2060-11-30649 4

platform EGI to meet a platform’s new requirements in a timely manner. It may require changes to the integrated EGI software and hardware to permit a change in the physical, graphical user, and electronic interfaces and communications with the platform. Modernizations may include changes due to Diminishing Manufacturing Sources & Material Shortages (DMSMS), new functionality, technology insertion, or new requirements such as Selective Availability/Anti- Spoofing Module (SAASM) or Military GPS User Equipment (MGUE). The EGI shall include associated mounts for platform installation. The contractor shall support the integration of the EGI with each aircraft.

1.2.2 Engineering Approach

The contractor shall use each platform Prime Item Development Specification (PIDS) to define Platform Application. Each platform EGI shall meet the requirements of the individual platform

EGI PIDS.

1.2.3 Mission Critical Computer Resources (MCCR)

The contractor shall manage, design, develop, code, integrate, test, validate, fully document, and maintain the necessary computer resources for the EGI system. Non-Developmental Software (NDS) shall be used to the maximum extent practical. The contractor shall develop any changes to NDI software/firmware: operational, support, developmental, mission, or system oriented, required for integration or modernization of the EGI in accordance with established contractor software development processes. Any major changes to these processes shall be reported to the government and briefed at program reviews. For the purposes of this PWS, the term "software" applies to all operational software, firmware that is not contained in off-the-shelf commodity parts, diagnostic software, and software tools used for developing, supporting, or testing any and all EGI software. (DI-MCCR-80700)

1.2.3.1 Design of Software Interfaces

The contractor shall develop a design for the interfaces external to each Computer Software Configuration Item (CSCI) documented in the Software Requirements Specification (SRS) (DI-

IPSC-81433A).

1.2.4 Form and Fit Model(s)

As required for EGI Integrations, the contractor shall fabricate and deliver full-scale nonfunctional model(s) of the EGI LRU configurations including associated mounts. The model(s) may be constructed of any material which shall allow accurate form and fit assessment of the various installation requirements and wiring interfaces for the platforms identified herein.

Model(s) shall conform to the physical form of the EGI LRU configuration including handle and connector sizing considerations.

1.3 System Test and Evaluation (T&E)

As required by individual delivery order, the contractor shall evaluate and demonstrate the EGI equipment by conducting engineering evaluation tests, demonstrations, analyses, and inspections and by supporting flight line and flight tests to verify compliance with all contractual requirements. The contractor shall determine the number and allocation of units necessary for contractor testing as defined in Section 4 of each Prime Item Development Specification (PIDS).

PR # FD2060-11-30649 5

The contractor shall develop and document test procedures for the evaluation of all hardware and software. The contractor shall submit complete documentation (e.g. test plans/procedures and test results) of any previous testing which he feels may satisfy test requirements of Section 4 of the PIDS for government review. If the procuring activity agrees that the submitted test documentation satisfies the intent of the test requirements, that data will be accepted in lieu of further testing. This determination will be made no later than the Engineering Design Review (EDR). The EGI equipment shall undergo both contractor conducted and government conducted testing to verify compliance with each PIDS. (DI-NDTI-80566A /DI-NDTI-80603A)

1.3.1 Test Plan

As required by individual delivery order, the contractor shall develop a comprehensive test plan which provides sufficient testing to adequately demonstrate that the EGI meets all requirements.

The contractor shall determine the extent of this test program, the number of EGI resources necessary to complete these tests within the allocated schedule, and the personnel required to support government-conducted field tests. (DI-NDTI-80566A)

1.4 Contractor Test and Evaluation

1.4.1 Test Notification

All contractor-conducted tests, both formal and informal, shall be open for government observation. The contractor shall notify the Contracting Officer (CO) in writing fourteen (14) working days prior to starting any test requiring an approved plan or procedure. Tests requiring approved plans and procedures shall not be conducted prior to government approval.

1.4.2 Acceptance Tests

As required by individual delivery order, the contractor shall provide detailed Acceptance Test Procedures (ATP) for the platform specific configuration for the individual delivery order Contract Data Requirements List (CDRL) requirement. The government platform’s Program Manager/Contracting Officer will approve these procedures prior to production. The contractor shall conduct acceptance tests IAW the government approved ATP on each EGI LRU prior to the start of qualification testing. The contractor shall document acceptance test results. The acceptance tests shall validate that the PME meets all specified requirements. (DI-NDTI-

80603A, DI-NDTI-80809B)

1.4.3 Qualification Tests

As required by individual delivery order, the contractor shall perform inspections, tests, demonstrations, and analyses to ensure that all configuration items meet all requirements within their PIDS. All qualification efforts shall be satisfactorily completed prior to the applicable Functional Configuration Audit (FCA).

1.4.4 Functional Tests

As required by individual delivery order, the contractor shall conduct the functional tests on the PME IAW the approved test plans and procedures, and document the results. The functional tests shall include, but not be limited to, system level performance and interface testing. The

PR # FD2060-11-30649 6

functional tests shall validate that the PME meets all specified requirements. All functional test efforts shall be satisfactorily completed prior to FCA. (DI-NDTI-80809B)

1.4.5 Environmental Tests

As required by individual delivery order, the contractor shall conduct and document the environmental tests on the PME IAW approved test plans and procedures. The environmental tests shall be based on the information obtained through the contractor's environmental process.

The environmental test shall validate that the EGI equipment meets all specified environmental requirements. (DI-NDTI-80809B)

1.4.6 Electromagnetic Tests

As required by individual delivery order, the contractor shall conduct and document their Electromagnetic Interference (EMI) tests on the PME IAW the EMI test plans and procedures.

The EMI tests shall consist of the tests listed in the EMI testing section of the PIDS. The EMI tests shall validate that the EGI equipment meets all specified EMI requirements. . The intent of this approach is to ensure that between the EGI contractor and the integrator, the EGI is provided with the necessary electromagnetic protection/isolation. (DI-EMCS-80200C, DI-EMCS- 80201C)

1.4.7 Software Tests

As required by individual delivery order, the contractor shall conduct software tests for the EGI to verify that the EGI meets the requirements of the PWS, PIDS, and the SRS.

1.4.7.1 Formal Software Tests

As required by individual delivery order, the contractor shall conduct a separate formal software test to be witnessed by the government for each system processor OFP CSCI. The contractor shall provide a traceability matrix to show how each requirement of the SRS is tested by a formal procedure identified and described in the Software Test Plan (STP). The contractor shall provide records of the formal qualification testing performed on each CSCI in the Software Test Report

(STR). (DI-IPSC-81438A, DI-IPSC-81433A, DI-IPSC-81440A)

1.4.7.2 Informal Software Testing

As required by individual delivery order, the contractor shall perform and document informal testing IAW the contractor’s internal procedure and shall submit to the government.

1.4.8 MIL-STD-1553B Interface Test

As required by individual delivery order, the contractor shall verify MIL-STD-1553 interface requirements on new integrations or modernization by conducting MIL-STD-1553 verification tests or by analysis/similarity to already qualified equipment. If the verification method is “test”, tests shall be performed with reference to guidance in Section 100 of MIL-HDBK-1553, RT Validation Test Plan. The newest available operational software and firmware shall be used during the tests. The equipment shall pass all tests to be performed on each configuration type without configuration (hardware, software, or firmware) change. The contractor shall document all test results. The contractor shall correct all software and/or hardware design deficiencies uncovered as a result of these tests and shall incorporate any corrections into all equipment. The

PR # FD2060-11-30649 7

contractor shall evaluate a change in a unit's configuration (hardware, software, or firmware) subsequent to successful completion of all tests on a unit, to determine whether or not the tests were invalidated as a result of the change and whether any tests need to be conducted again.

Contractor's recommendations as to whether tests need to be conducted again shall be approved by the government platform’s Program Manager/Contracting Officer. If the tests need to be conducted again, then the contractor shall perform the tests as stated above. (DI-NDTI-80809B)

1.4.9 Correction of Deficiencies

If testing is required under Section 1.4, the contractor shall incorporate all changes and required corrective actions resulting from previous testing prior to conducting and further serial tests.

During the course of all testing the contractor shall be responsible for any maintenance or modification required to correct deficiencies resulting in nonconformance with design/performance specification. The contractor shall maintain identical hardware and software configurations of all systems undergoing test. In the event of concurrent tests, deficiencies uncovered and corrected in one test shall be corrected in all systems, including those in other tests.

1.5 Government Test and Evaluation

1.5.1 Platform Integration/Modification Support

As required by individual delivery order, the contractor shall provide on-site and/or on-call support and assistance during the platform installation/modification. The contractor shall provide Group B integration components IAW paragraph 1.2.1. The contractor shall provide “mating connector sets” for integration if specifically required by individual delivery order.

Upon completion of each integration activity, all integration units shall be refurbished to the latest production configuration and returned to the government.

1.5.2 Flight Tests

As required by individual delivery order, the contractor shall support government ground and flight test efforts by providing onsite personnel and in-house support. The contractor shall support each government test program by providing maintenance, logistics, and technical support while deployed simultaneously to different field locations. The contractor shall provide all required organizational level peculiar support equipment and spare parts needed to maintain the EGI during each test effort. The contractor shall analyze test data, conduct failure analysis, and maintain a data tracking system throughout all flight test efforts.

1.6 System Engineering

1.6.1 Systems Engineering Master Schedule (SEMS) and Systems Engineering Management Plan (SEMP) As required by individual delivery order, the contractor shall use a systems engineering approach to achieve equipment integrity and specified functional performance. The contractor shall implement a total systems engineering process and document this in a contractor generated System Engineering Management Plan (SEMP). The contractor shall also implement the EGI program Systems Engineering Master Schedule (SEMS) that depicts major program milestones

PR # FD2060-11-30649 8

that are event oriented along with milestone entrance and exit criteria. The SEMS shall provide the basis for all subsequent detailed planning and its milestones reflected in all program schedules submitted to the Government. The contractor shall report on work in progress IAW the SEMS at each program review. An updated SEMP and SEMS shall be submitted with each new integration or modernization. (DI-SESS-81785)

1.6.2 Engineering Study

As required by individual delivery order, the contractor shall conduct, as directed by the CO, a platform interface or an engineering study in accordance with a government-provided statement of work specific for that study effort. These studies could address a technical issue of a particular integration, modernization, or address technology insertion across the EGI product line. The results from the potential candidate investigation shall be reported separately and delta requirements assessed to determine impacts of all design/cost drivers. (DI-MISC-80711A)

1.6.3 Durability Assessment

As required by individual delivery order, the contractor shall perform a durability assessment for all the applicable EGI modifications. This assessment determines if the EGI still meets the service life requirement stated in the Prime Item Development Specification. The Durability/Service life analyses shall be conducted for EGI modifications to integrate the EGI to meet the requirements of any specific platform. This assessment must be completed by the Engineer Design Review (EDR) and shall include environmental and usage application requirements and resulting stress levels stated in the government baseline for the service life.

Where the new application usage and environment are more severe than the original and/or the designed conditions, the contractor shall recognize and define the new life limits.

1.6.4 Failure Summary and Analysis Report

The contractor shall establish, implement, and maintain a Failure Summary and Analysis Report for EGI contractor depot repairs (CDR). The contractor shall record failure information from failures on fielded systems in failure summary reports. Beginning in January 2013, the reports shall include existing failures on the previous FA8626-06-C-2065 contract. (DI-RELI-80255/T)

1.6.5 Human Engineering

As required by individual delivery order, the contractor shall address all human factor aspects relative to system installation for each new integration and/or modernization. The contractor shall include in its design analyses consideration for effective maintenance actions and for maintenance personnel wearing Chemical/ Biological gear and other operational gear. The contractor shall present human engineering design information and rationale at the integration and/or modernization EDR.

PR # FD2060-11-30649 9

2.0 SERVICE SUMMARY

Performance Objective PWS

Para Performance Threshold

1 Data Submittal/Test Plans/Procedures/Reports

1.3.1, 1.4.2, 1.4.4, 1.4.5, 1.4.6, 1.4.7.1, 1.4.8, 1.6.1, 1.6.2, 1.6.4, 4.2.3, 4.3, 4.3.3, 4.4.1, 4.5.6.1, 4.5.6.2, 4.5.8, 4.6.11

The contractor shall submit data, technical plans/procedures/reports in accordance with the established suspense for completion of the task as identified in specific delivery order and associated defined CDRL. Government directed revisions shall not exceed one per quarter. Revisions shall be submitted within thirty (30) working days after notification that report must be rewritten. The contractor’s final report shall be 100% accurate and contain zero discrepancies.

2 Repair Turn Around Time 4.6.1.1, 4.6.1.2, 4.6.1.3

All products shall meet or exceed minimum performance specifications and be defect free.

Each item will pass the Acceptance Test Plan (ATP) which includes a complete inspection and functional test of the item and all deficiencies corrected/repaired. Inspection and functional test shall be performed in accordance with applicable OEM technical order.

Turn Around Time (TAT) is 22 working days

ARO

3 Technical/Engineer Support

1.5.1, 1.5.2, 4.5.8, 4.5.9

The contractor shall provide technical assistance and/or solution in accordance with the appropriate delivery order. Technical solution shall be accurate and sound 100% of the time with zero discrepancies.

3.0 GOVERNMENT FURNISHED PROPERTY AND SERVICES

The Government Furnished Equipment in Section 5, Table III will transfer from contract Number FA8626-06-C-2065 to the new contract.

PR # FD2060-11-30649 10

4.0 GENERAL INFORMATION

4.1 Performance of Services during crisis declared by the President of the United States, the Secretary of Defense, or Overseas Combatant Commander.

The Functional Director has determined that the performance of these services is not considered to be mission essential during time of crisis. Should a crisis be declared, the Contracting Officer or his/her representative will verbally advise the contractor of the revised requirements, followed by written direction, in accordance with DoDI 1100.22, Policy and Procedures for Determining Workforce Mix, 12 Apr 10.

4.2 Project Management

The contractor shall establish and maintain a program management system, which will direct and control the administrative, technical, logistical, financial and production functions of this program.

4.2.1 Program Manager

The contractor shall designate a single program manager for the EGI program who shall be responsible and shall have authority for the control and coordination of all work performed under this contract.

4.2.2 Program Reviews

The contractor shall conduct EGI User’s Program Management Reviews (PMR) for the purpose of reviewing and coordinating program status and resolving program problems. The contractor shall include in the program reviews an assessment of production status, subcontract management, quality assurance, and logistics issues. The contractor shall address any issues and the corrective actions. In addition, the contractor shall report on topics concerning the previous FA8626-06-C-2065 contract until such time that all deliveries have been completed for that contract. PMRs shall be held every 6 months at the contractor's facility. The contractor shall provide presentation materials for all formal meetings.

The contractor shall support bi-weekly EGI Program Teleconference Meetings. These meetings will encompass the overall EGI program to include the previous FA8626-06-C-2065 contract.

The contractor shall conduct platform specific program reviews, if specifically required by individual delivery order, for the purpose of reviewing and coordinating program status and resolving program problems related to integration and modification. (DI-ADMN-81249A, DI-

ADMN-81250A)

4.2.3 Status Reports

The contractor shall submit monthly status reports to the government as required by individual delivery order. These reports shall cover logistics, technical, and engineering support provided by the contractor during the previous monthly period. The contractor shall document task status, data deliverables, contract issues and actions, and expenditure data. Regular updating of cumulative cost versus estimated total cost shall be submitted in the monthly status report. A Funds Expenditures chart that plots actual and planned expenditures and man-hours against time

PR # FD2060-11-30649 11

shall be included with each status report. In addition, all problem areas will be covered with recommended solutions and the outcome after solution implementation. (DI-MGMT-80368A)

4.3 Technical Reviews

As required by individual delivery order, the contractor shall conduct technical reviews for the purpose of reviewing and coordinating technical status and resolving program problems.

Reviews shall be held at the contractor's facility unless otherwise agreed upon. The contractor shall provide agenda, presentation materials and document the minutes. This task shall be accomplished as required in accordance with each individual order. (DI-ADMN-81249A, DI-

ADMN 81250A)

4.3.1 Systems Requirements Review (SRR)

As required by individual delivery order, the contractor's Prime Item Development Specification (PIDS) will be reviewed against the system requirements for each integration and/or modernization. The milestone schedule for all technical events shall be reviewed. (DI-ADMN-

81249A, DI-ADMN 81250A)

4.3.2 Engineering Design Review (EDR)

As required by individual delivery order, the contractor shall conduct an EDR to ensure a full understanding of the specification(s) and interface requirements and to verify that the contractor's design will meet its performance requirements. The contractor shall provide the agenda for the meetings, presentation material and document the minutes. Emphasis will be placed on review of any changes made since the submission of the proposal. (DI-ADMN-81249A, DI-ADMN 81250A)

4.3.3 Technical Interchange Meeting (TIM)

As required by individual delivery order, the contractor shall conduct and support TIMs at its facility upon the request of the contracting activity. The contractor shall provide the agenda for the meetings, presentation material and document the minutes. The Government may request specific topics to be addressed. (DI-ADMN-81249A, DI-ADMN 81250A)

4.3.4 Interface Control Working Group (ICWG)

As required by individual delivery order, the contractor shall support integration and/or modernization ICWGs. Support shall include the preparation, review, and coordination of interface specifications, which define the EGI electrical, mechanical and signal interface with the designated platform or systems and to assist in resolving integration problems. The contractor shall establish Associate Contractor Agreement(s) with other contractors, as necessary to support this task. The contractor shall make all reasonable efforts to put in place the necessary protections such as Proprietary Information Agreement, ACA, or other agreements to effectively support the ICWG activities.

4.3.5 Test Readiness Review (TRR)

As required by individual delivery order, the contractor shall schedule, host, and conduct a TRR prior to the start of the formal CSCI testing. The contractor shall use MIL-STD-973 as a guide to define the requirements, criteria, and procedures for conducting the TRR. The contractor shall

PR # FD2060-11-30649 12

brief the latest Software Test Plan (STP) and demonstrate the adequacy of the STP, including demonstration of traceability of SRS requirements to STP test cases. The contractor shall review the results of informal testing and assure the system, including software and hardware, is ready for formal testing. (DI-ADMN-81249A, DI-ADMN 81250A)

4.4 Data Management

The contractor shall maintain a data management system to monitor all data activity and submit contract data in accordance with the CDRLs. The contractor shall utilize the government established SharePoint system for delivery of all CDRLs.

4.4.1 Data Accession List (DAL)

The Contractor shall maintain a complete listing of all generated technical data resulting from this contract and shall provide this data upon request from the government. (DI-MGMT- 81453A)

4.4.2 Engineering Data

The contractor shall document the engineering design, material identifications, manufacturing processes, fabrication and assembly sequences, test procedures, acceptance test parameters, quality control procedures and acceptance parameters, and source data for purchased material with engineering data, for the life of the contract. (DI-MISC-80711A)

4.5 Configuration Management

The contractor shall implement and execute a Configuration Management Program to perform configuration identification, control, audit, and status accounting. The contractor shall establish a program that will identify and document the functional, allocated, and physical baselines. The program shall ensure that configuration information is current, accurate, and readily accessible and interface requirements are documented and controlled via configuration management processes. (DI-CMAN-80858B)

4.5.1 Configuration Identifiers

The contractor shall maintain the program baseline documentation for each platform EGI for the life of the contract.

4.5.2 Specifications

As required by the individual delivery order, the contractor shall prepare Prime Item Development Specifications for each EGI LRU configuration. The contractor shall prepare an SRS for each System Processor OFP CSCI. (DI-SDMP-81493A)

4.5.2.1 Interface Control Document

As required by the individual delivery order, the contractor shall prepare an Interface Control Document for each EGI configuration. (DI-CMAN-81248A)

4.5.3 Configuration Control

The contractor shall maintain the EGI baseline configuration documentation and prepare ECPs, CCPs and specification change notices as required.

PR # FD2060-11-30649 13

4.5.4 Engineering Change Proposals (ECPs)

Changes to approved baseline configuration items shall be documented through ECPs. A Specification Change Notice (SCN) shall be submitted in conjunction with the ECPs or any changes made to an approved specification. Since, PIDS normally change as the program matures, baseline configuration shall be defined at completion of FCA/PCA. SCNs or ECPs would be submitted for any documentation change after the baseline configuration is established at FCA/PCA. (DI-CMAN-80639C, DI-CMAN-80643C)

4.5.4.1 Request for Deviation (RFD)

The contractor shall process RFDs from the approved configuration documentation. Guidance for this documentation is available in MIL-STD-973, paragraph 5.4.3, and subparagraphs, and Appendix E. (DI-CMAN-80640C)

4.5.5 Request for Nomenclature/Computer Program Identification Number (CPIN) As required by individual delivery order, the contractor shall request nomenclature and CPIN for each integration and/or modernization. The contractor will contact the individual delivery order POC for specific instruction for submittal of CPIN. (DI-CMAN-81254A, DI-MISC-81454B)

4.5.6 Configuration Audits

As required by individual delivery order, the contractor shall support and host configuration audits for each unique integration and/or modernization to establish a production baseline and verify that performance requirements have been met.

4.5.6.1 Functional Configuration Audit (FCA)

As required by individual delivery order, the contractor shall support and host an FCA for each integration and/or modernization to verify the system’s performance against its approved documentation. FCAs may be held concurrent with or prior to PCAs. The contractor shall provide an agenda, presentation materials and document the minutes. (DI-ADMN-81249A, DI-

ADMN-81250A)

4.5.6.2 Physical Configuration Audit (PCA)

As required by individual delivery order, the contractor shall support and host a PCA for each integration and/or modernization to ensure that the “as built configuration” of the unit matches the configuration identification documentation for it. The contractor shall provide an agenda, presentation materials and document the minutes. (DI-ADMN-81249A, DI-ADMN 81250A)

4.5.7 Software Data

The contractor shall document all EGI software. All changes or updates to these documents to maintain the product baseline, shall reflect the latest configuration developed under this PWS.

As required by individual delivery order, the contractor shall prepare a Software Version Description (SVD)/ Version Description Document (VDD) for each system processor OFP developed, modified, or tailored under this contract. (DI-IPSC-81442A)

4.5.8 Technical Support

PR # FD2060-11-30649 14

The contractor shall provide technical support, as required by individual delivery order. This support may include but is not limited to support of special government projects involving the EGI, analysis of data from such projects, evaluation of EGI failures (outside warranty and other contractual coverage), and technical evaluation of potential future EGI platforms requirements.

The Contracting Officer authorization will provide a description of the technical support that is required in the individual delivery order.

4.5.9 Quick Time Engineer Support

As required by individual delivery order, the contractor shall provide on-site engineering, technical and/or testing support to assist the government with anomalies, installation, integration, and testing issues of the EGI. Each delivery order shall establish a response time for contractor to be on-site. The contractor shall respond with a report of finding within 10 working days of the contractor team’s departure from the Government location.

4.6 Logistics Support

Through an integrated Systems Engineering process, the contractor shall provide and support the nine logistics elements of maintenance planning, manpower/personnel, supply support, support equipment, technical data, training, computer resources support, facilities, and design interface to assure effective and economical support during the useful life of the EGI. The EGI logistics support shall be integrated with the systems design engineering process and be included in all formal system and design reviews.

The logistics support program shall integrate the logistics support elements and shall provide the interface between producability engineering, human factors engineering, design engineering, technical documentation, and training. The contractor shall conduct the logistics support effort to conform to the support concept of two levels of maintenance.

4.6.1 Contractor Depot Repair

As required by individual delivery order, the contractor shall repair all EGI units acquired under current and prior production options.

4.6.1.1 Repair Acceptance Criteria

All EGI units received for repair will be tested and repaired utilizing repair components that are equal to or superior to those provided by the Original Equipment Manufacturer (OEM). All products shall meet or exceed minimum performance specifications and be defect free. The contractor shall not incur any repair cost or perform any repair activity on an asset until the cognizant government contracting officer provides specific authorization for repair of that asset by funding via issuing a Delivery Order under this contract. If, upon receipt of an asset, contractor determines that the asset is misidentified, improperly packaged, or incomplete, the asset shall be placed in a bonded storeroom awaiting disposition instructions from the Ordering Contracting Officer.

4.6.1.2 Repair Turn-Around Time

The repair turn-around time required is 22 working days. TAT start date entry criteria: receipt of unit and funded delivery order. The TAT exit/stop criteria are upon government acceptance.

PR # FD2060-11-30649 15

Contractor shall make every effort to deliver repaired units to meet fastest turn-around times possible.

4.6.1.3 Repair Inspection and Functional Test

Each item will pass the functional acceptance testing which includes a complete inspection and functional test of the item and all deficiencies corrected/repaired. Inspection and functional test shall be performed in accordance with applicable OEM technical order. Neither design nor functional capabilities shall be changed, modified, or altered without written approval from the procuring agency.

4.6.1.4 Deficiency Reports

In the event the EGI is inoperable upon initial installation in an aircraft, a deficiency report will be generated by the end user. When requested, the Contractor shall assist the contract administering organization in the evaluation of exhibits of items originally manufactured and/or repaired to determine the cause for deficiencies reported from field organizations through the Material Deficiency Report/Product Quality Deficiency Report (MDR/PQDR) process.

MDRs/PQDRS for USAF and FMS will be handled in accordance with Technical Order (TO) 00-35D-54 USAF Deficiency Reporting, Investigation, and Resolution.

4.6.1.5 Condemnation

The contractor shall not condemn any asset unless the asset has sufficient damage which results in 75% of the asset having to be replaced. Condemnation shall be approved by the government platform program manager/contracting officer. Dispose of asset in accordance with local plant procedures.

4.6.2 Option for Non-Supported EGI LRU

In the event that the contractor no longer wants to support the EGI LRU at the end of this contract, the contractor shall provide the option for the government to purchase a production drawing package, depot-level technical data, depot-level support equipment requirements documents, and the depot-level support equipment.

4.6.3 Support Equipment Recommendation Data

RESERVED

4.6.4 Supply Support (Provisioning)

This task is only for new EGI integration or modification and is done in accordance with the individual delivery order. Contractor shall identify and recommend logical spare/repair parts sufficient to meet system/equipment operation and supportability in accordance with the Air Force Initial Provisioning Performance Specification (IPPS). MIL-PRF-49506 should be used as a guide. Format must be consistent with existing government Provisioning data system (D220).

The following Data Item Descriptions (DIDs) apply:

• Provisioning Technical Documentation (PTD) (DI-ALSS-81529) o Provisioning Parts List (PPL) o Short Form Provisioning Parts List (SFPPL) o Design Change Notices (DCNs)

PR # FD2060-11-30649 16

o Long Lead Items List (LLIL) o Statement of Prior Submission (SPS)

• Supplemental Data For Provisioning (SDFP) (DI-ALSS-81557)

• SE Recommendation Data (SERD) – Standard/Modified Hand Tools List (DI-

ALSS-81530)

o Support Equipment Recommendation Data (SERD) o Standard Modified Hand Tools List

4.6.5 Spares and Repair Parts

Under the Contractor Depot concept, the contractor shall establish and maintain a supply support function for all spares and repair parts necessary for the repair and maintenance of the end item.

4.6.6 Commercial Asset Visibility (CAV)

The contractor shall report using the Commercial Asset Visibility (CAV). The contractor shall provide data related to the tasks and efforts conducted for each repairable unit under contractor depot repair.

For Air Force requirements, if CAVAF (Air Force) training is required, contact 406 SCMS/GUMA, Donna Allred, Robins AFB GA 31098, Phone 478-327-6602 or Doug Branham, 478-327-6603 for additional information. The contractor shall conduct production reporting on a daily or as transactions occur basis. The contractors shall obtain a valid DoD PKI certificate to log into CAV. Each user shall be required to have an Identity Certificate only; an encryption certificate is not required. (DI-MGMT-81634B)

For Navy requirements, the contractor shall comply with the requirements contained in the Web- Based Commercial Asset Visibility Statement of Work, Version 7.3, dated September 24, 2010.

For Air Force requirements, the contractor shall comply with the requirement contained in the CAF AF Statement of Work, dated 22 February 2010.

CAV reporting is not required for FMS.

4.6.7 Technical Manual Source Data

As required by individual delivery order, the contractor shall develop Organizational Level Maintenance Source Data if commercial manuals are not adequate/approved for government use to support organizational level (remove and replace) maintenance for the EGI. Source data shall be developed for current platforms and each new integration and/or modernization.

4.6.8 Packaging, Handling, Storage, and Transportation

The Honeywell designed "box-in-box" will be used for all new build and repairs for all services.

EGIs are packaged in accordance with AFMC Form 158 requirement for using Commercial Best Practices (CBP). Should an EGI be returned in a re-usable container, the container is returned to the appropriate service for re-use. Unserviceable containers shall be disposed of and replaced with containers that meet the requirements of Honeywell’s “box-in-box.”

PR # FD2060-11-30649 17

The contractor shall perform packaging and marking in accordance with : MIL-STD-2073-1E, dated 23 May 08, Standard Practice for Military Packaging and MIL-STD-129P W/Change 4, dated 19 Sept 07, Military Marking for Shipment and Storage.

4.6.9 Markings

The contractor shall mark all items packaged for shipment IAW MIL-STD-129P and as contractually stipulated. All reusable containers shall be marked "REUSABLE DO NOT DESTROY". Additional markings that exceed those of MIL-STD-129P for shipment to North Atlantic Treaty Organizations (NATO) countries shall be marked as specified in the NATO AAP-44(A), NATO Standard Bar Code Handbook, and the Standardization Agreement (STANAG) 4281, NATO Standard Marking for Shipment and Storage (marking of military cargo). (Contract Attachments 5 and 8 respectively) DoD policy requires Unique Identification (UID) marking for all EGI units produced on this contract. The contractor shall provide appropriate UID marking defined in the latest version of MIL-STD-130N, as called out in

DFARS 252.211-7003).

4.6.10 System Safety Program

As required by individual delivery order, the contractor shall conduct a System Safety Program IAW MIL-STD-882D. The contractor shall identify potential hazards associated with the EGI system and the integration of the system with each of the integrations or modernization. The contractor shall define the mishap severity categories IAW MIL-STD-882D, APPENDIX A, Section A.4.4.3.2.1, Table A-I. and mishap probability levels IAW MIL-STD-882D, APPENDIX A, Section A.4.4.3.2.2, Table A-II. These definitions shall be used to form a hazard risk assessment matrix IAW MIL-STD-882D, Appendix A, Table A-III, Contractor shall conduct safety assessments for each new integration and/or modernization. (DI-SAFT-80102B)

4.6.11 Safety Review of ECPs and Request for Deviations

The contractor shall provide an Engineering Change Proposal System Safety Report for any design changes. (DI-SAFT-80103B)

4.6.12 Manufacturing Management

The contractor shall continue to manage the production program in accordance with the manufacturing management plan. Changes to the plan shall be reported at EGI Users PMRs.

(DI-MGMT-81255)

4.6.13 Diminishing Manufacturing Sources and Material Shortages (DMSMS) Program/Electronic Parts Screening The contractor shall utilize an Electronics Parts Screening process that shall identify Diminishing Manufacturing Sources (DMS) for parts for the end item design. The contractor shall be responsible for its subcontractors’ parts obsolescence awareness. The contractor shall regularly check the Government-Industry Data Exchange Program (GIDEP) database for DMSMS items during all program phases, and shall determine if any of these items are used in, or planned to be used in the system. This program shall be reviewed at program reviews and as requested by the government. (DI-SESS-81656)

PR # FD2060-11-30649 18

4.6.14 Subcontractor/Vendor Management

The contractor shall update and maintain the existing supplier management plan to ensure all program requirements are met. The contractor shall ensure that effective integration of key subcontractors’ and suppliers’ activities into the overall program plans, activities and schedules are accomplished. The contractor shall provide for the identification, analysis, management and abatement of risks, including environmental issues at key sub-contractors and suppliers, and assure integration of these activities in the overall program risk management efforts. The contractor shall identify to the cognizant Contract Administration Services office and the Procuring Agency any subcontractor/vendor schedule, cost, quality, and performance problems in time to permit corrective action required to prevent or minimize program impacts. The contractor shall ensure that procuring agency representatives have access, through the prime, to major component subcontractors to obtain information necessary to resolve any problems experienced in the field.

4.6.15 Quality Systems

The contractor shall provide and maintain a quality system which at a minimum, adheres to the requirements of ISO 9001-2000, or an equivalent quality model acceptable to the government.

Third party registration of contractor’s quality system shall not be required. Registration of contractor’s quality system shall not restrict government quality surveillance. Quality records shall be as prescribed by the contractor’s quality plan or procedures and be readily available to the government.

4.6.16 Calibration

The contractor shall maintain a calibration system that ensures the accuracy of measuring and test equipment used to verify technical requirements for this contract. All documentation and testing for this system shall be made available for review upon request.

4.6.17 Software Quality Assurance

The contractor shall maintain, update, and implement the existing Software Quality Program (SQP) on all aspects of the EGI system for Software Quality Assurance (SQA). The SQP shall encompass all aspects of the established baseline software and systems. SQA for software modified or developed, shall be in accordance with the contractors SQP and SQA. The contractor shall demonstrate, as requested by the government, that adequate configuration control exists over the established baseline software and modified software for all product applications. The contractors Software Quality Assurance Systems and associated results, testing and data are subject to government review upon request.

4.7 Reserved

4.8 Security Requirements:

1. General: Actual knowledge of, generation, or production of classified information is not required for performance of the contract. Cleared personnel are required to perform this service because security measures which are in force do not preclude access to classified information.

PR # FD2060-11-30649 19

2. Operations Security (OPSEC): Contractor personnel will participate in the OPSEC program locally administered by the AF activity.

3. Employee Clearances: Contractor employees that need access to Government owned Automated Information Systems (AIS) will require the minimum of a Favorable National Agency Check (NAC). Submit a Standard Form 85P (fingerprint cards if available) to the Security Team for processing.

4. Security Incidents and Violations: The contractor will immediately notify the wing security team of any actual security violation, security incident, or of any indication of a potential unauthorized disclosure or compromise of classified or sensitive but unclassified information.

5. Security Education: All full-time contractor employees occupying physical space on Robins AFB, will comply with the Security Education and Awareness program. The program consists of four components: initial training, annual refresher training, and periodic tailored training.

PR # FD2060-11-30649 20

5.0 APPENDICES

The publication below shall be considered as guidance only unless specifically referenced in this PWS or in the individual delivery order.

TABLE II: Publication

Name of Publication Date of Publication and Changes Title of Publication

MIL-STD-129P W

Change 4

19 Sept 07 Military Marking for Shipment and Storage

MIL-STD-130N 17 Dec 2007 Identification Marking of U.S. Military Property

MIL-STD-882D 10 Feb 00 System Safety

MIL-STD-973 17 Apr 92 Configuration Management

MIL-STD-1553B

Revision B Change Notice 4

23 Mar 95 Digital Time Division Command/Response Multiple Data Bus

MIL-STD-2073-1E 23 May 08 Standard Practice for Military Packaging

MIL-STD-1686C 25 Oct 1995 Electrostatic Discharge Control Handbook for Protection of Electrical and Electronic Parts, Assemblies and Equipment (excluding Electrically Initiated Explosive Devices) Metric (MIL-STD-1686C and MIL-HDBK- 263B used simultaneously)

PR # FD2060-11-30649 21

MIL-HDBK-263B 31 Jul 1994 Electrostatic Discharge Control Handbook for Protection of Electrical and Electronic Parts, Assemblies and Equipment (excluding Electrically Initiated Explosive Devices) Metric (MIL-STD-1686C and MIL-HDBK- 263B used simultaneously)

PBWS 4.1.1

MIL-HDBK-454A 03 Nov 2000 General Guidelines for Electronic Equipment

MIL-HDBK-1553

Revision A Change Notice 2

23 Mar 95 Multiplex Application Handbook

MIL-HDBK-5400T 30 Nov 1995 Electronic Equipment, Airborne General Guidelines

ISO 10012-2003(E) 01 Aug 1992 Measurement Management Systems- Requirements for Measurement Process and Measuring Equipment

ISO 9001 17 Apr 2001 Quality Management Systems- Requirements

TO 00-35D-54 1 May 2007 USAF Deficiency Reporting and Investigating System

J-STD-001B Oct 96 Joint Industry Standard, Requirements for Soldered Equipment and Electronics Assemblies

TM-86-01J 1 Jun 01 Technical Manuals Contract Requirements

PR # FD2060-11-30649 22

Table III: Honeywell International Government Furnished Property

Description P/N -- Location

Qty Unit Cost Serial Num.

EMBEDDED GPS/INS-9.8

EGI (S-3)

34209950-RN12-001

Honeywell Eng 1 131,233.00 11473

EMBEDDED GPS/INS-F15

SAASM

34200750-R041-960 Honeywell Eng 1 64,000.00 11062

EMBEDDED GPS/INS(AH-

64 P3I SAASM)

34209950-R004-960 Honeywell Eng 1 139,276.00 10098

EMBEDDED GPS/INS(AH-

64 P3I SAASM)

34209950-R004-960 Honeywell Eng 1 114,000.00 10492

INDICATOR ATTITUDE

DIREC

1 2,000.00 None

INDICATOR HEAD 1 100 6910

INDICATOR ATTITUDE

(ADI)

139602-01-01 Honeywell Eng 1 8,645.00 114

MEMORY LOADER

VERIFIER S

1 35,000.00 TFU0359

CONTAINER, SHIPPING 1 500 None CONTAINER, SHIPPING 1 500 None