Attachment_(1)-PWS_03_Jul_18.pdf

Basic

PERFORMANCE-BASED WORK STATEMENT

For the

Embedded Global Positioning System

Inertial Navigation System Modernization

Production and Sustainment IDIQ Follow-on

Northrop Grumman System Corporation

PR: FD2060-16-91124

1 May 2018

AFLCMC/WNY

Positioning, Navigation, and Timing (PNT) – Program Office Air Force Life Cycle Management Center

235 Byron St, Suite 19A Robins AFB, GA 31098

PR: FD2060-16-91123 PWS Basic 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 AFLCMC/WNY, Robins

AFB GA 31098-1813

2 PR: FD2060-16-91124 PWS Basic

Table of Contents

1. DESCRIPTION OF supplies and SERVICES

Objective

Benefit to the Government

Background

2. Services Summary

Period of Performance

Place of Performance

Performance Evaluation

Objectives and Thresholds

Performance of Services During Crisis

3. Government Property and Services

Government Property

Report of Government Property

Return/Retention of Government Property

Government Systems

Base Support

4. Technical Requirements

Program Manager

Monthly Status Reports (MSR)

Technical Meeting and Working Group Support

Integrated Master Plan & Integrated Master Schedule

Integrated Program Management Report

Cost Analysis and Reporting

4.6.1 Contract Work Breakdown Structure

4.6.2 Cost and Software Data Reporting

4.6.3 Cost and Software Data Reporting Post Award Conference

Contract Data Requirements Lists

Item Unique Identification

Counterfeit Electronic Parts

Commercial Asset Visibility

System Engineering

3 PR: FD2060-16-91124 PWS Basic

4.11.1 Platform Integration/Modification Support

4.11.2 Engineering Services

4.11.3 Integrated Master Schedule & Systems Engineering Management Plan 18

4.11.4 Engineering Study

4.11.5 Human Engineering

4.11.6 Program Reviews

4.11.7 Reserved

4.11.8 Technical Reviews

4.11.9 Systems Requirements Review

4.11.10 Engineering Design Review (EDR)

4.11.11 Technical Interchange Meeting

4.11.12 Interface Control Working Group

4.11.13 Test Readiness Review (TRR)

4.11.14 Technical Support

4.11.15 Quick Time Engineer Support

4.11.16 Specifications

4.11.17 Interface Control Document

4.11.18 Configuration Control

4.11.19 Engineering Change Proposals

4.11.20 Corrective Action for Defects Reported

4.11.21 Request for Variance

4.11.22 Request for Nomenclature/Computer Program Identification Number ... 22

4.11.23 Configuration Audits

4.11.24 Functional Configuration Audit (FCA)

4.11.25 Physical Configuration Audit (PCA)

4.11.26 Software and Hardware Development / Data

4.11.27 System Safety Program

4.11.28 Data Accession List (DAL)

Testing

4.12.1 Test Plan

4.12.2 System Test and Evaluation

4.12.3 Contractor Test and Evaluation

4 PR: FD2060-16-91124 PWS Basic

4.12.4 Government Test and Evaluation

Order and Delivery Requirements

4.13.1 Customer Support

4.13.2 Production

4.13.3 Configuration Control

4.13.4 Repairs

Repair Processes

4.14.1 Turn-Around-Time Calculation

4.14.2 Over and Above (O&A)

4.14.3 Cannibalization

4.14.4 Condemnation

4.14.5 Diminishing Manufacturing Sources and Material Shortages (DMSMS) 32

4.14.6 Demilitarization

4.14.7 Configuration Management

4.14.8 Repair CLINS

Security Engineering

4.15.1 Program Protection Planning and Implementation

4.15.2 Anti-Tamper (AT)

4.15.3 Cybersecurity

4.15.4 Software Assurance

Provisioning

5. General Information

Security Requirements

5.1.1 Security Regulations

5.1.2 Operations Security

5.1.3 Reserved

5.1.4 Security of Contractor System(s)

5.1.5 Affirmative Procurement Programs

Safety

5.2.1 Contractor Safety Compliance

5.2.2 Voluntary Protection Program (VPP)

5.2.3 Mishap Notification and Investigation

5 PR: FD2060-16-91124 PWS Basic

5.2.4 Safety and Health Plan

Inspection of Services

Trafficking in Persons

Environmental Management System

Small Business Subcontractor Program

Quality Management System

Contractor Manpower Reporting

Travel

Invoicing for Payment and Receipt or Acceptance

Appendix A – References

Appendix B – CDRL List

Appendix C – Acronyms

CHANGE HISTORY

Change Date

Basic 1 May 2018

Change 1 21 June 2018

6 PR: FD2060-16-91124 PWS Basic

1. DESCRIPTION OF SUPPLIES AND SERVICES

This Performance-based Work Statement (PWS) defines the Contractor requirements for the Embedded GPS/Inertial Navigation System (INS) (EGI) and the EGI-Modernization

(EGI/EGI-M) Production and Sustainment (P&S) contract. This contract supports:

Production o Continue EGI Production o Initiate EGI-M production. After the modernized units become available, legacy EGI/ will only be available for Foreign Military Sales (FMS) unless the waiver is obtained by the customer and presented with the order for EGI-

M units.

Sustainment o Repair legacy EGI and EGI-M o EGI-M acceptance Testing o Technical Services Support (Studies as-well-as new platform integration and testing)

Objective

The objective of this effort is to perform integration, modernization, fabrication, repair, technical support, and engineering support of the EGI and EGI-M across multiple

Department of Defense (DoD) platforms in order to maximize platform capabilities for the warfighter while maintaining the highest level of quality as required under the contract.

This effort will support the transformation of DoD units from legacy systems to the modernized systems supporting Military Code (M-code), Automatic Dependent

Surveillance–Broadcast (ADS-B) Out, and other requirements. This will increase navigational accuracy, provide better interface with weapons systems, eliminate interference from threats, and satisfy legal mandates.

Benefit to the Government

This Air Force Life Cycle Management Center’s (AFLCMC/WNY) Positioning, Navigation, and Timing (PNT) - Program Office (PNT-PO), formerly the Joint Service System

Management Office (JSSMO) is the organization responsible for centralized program management and oversight of EGI/EGI-M contracts. This P&S contract will maintain life-cycle support to the warfighters and reduce life-cycle cost of the EGI/EGI-M family of products by reducing configurations and meeting all military and civil mandates (ADS-B

Out, M-Code, etc.).

Background

The existing EGI IDIQ contract utilized decentralized ordering for the EGI family of products. The acquisition strategy for this contract will be to centralize EGI-M ordering and continue decentralized ordering for individual technical service orders and Legacy

7 PR: FD2060-16-91124 PWS Basic

EGI. The AFLCMC PNT-PO will become Operational Safety, Suitability, and

Effectiveness (OSS&E) for ordering EGI-Ms.

2. SERVICES SUMMARY

Required tasks may include, but are not limited to, designing, modernization, testing, engineering support services, repair and production for the EGI/EGI-M. The Contractor shall provide production, engineering and other technical services essential to deliver modernized EGI-Ms to meet multiple platform requirements and DoD and Government mandates, such as ADS-B Out and M-Code. This PWS will provide a means for all customers/Services to bring their EGI/EGI-M program up to full rate production of service ready assets. However, not all paragraphs in this PWS apply to each delivery order.

Individual delivery orders will specify which PWS paragraphs apply.

Period of Performance This contract will include ten one-year ordering periods. The contractor will price the first 3 one-year ordering periods. The remaining years’ pricing will be dependent upon development and acceptance of the EGI-M design(s).

Place of Performance

This contract will be performed at the Contractor’s facilities and/or sub-contractor’s facilities as required, and at Government installations for System Integration or Non-

Recurring Engineering (NRE).

Performance Evaluation

The Government shall evaluate the services provided to determine whether they comply with the performance standards listed below. In the case of issued Corrective Action

Reports (CARs), the Contracting Officer shall take appropriate measures according to the

“Inspection of Services” clause.

Objectives and Thresholds

Performance Objective

PWS Para Performance Threshold

Quality of Repair 4.13.4; 5.7 There shall be no more than two (2) validated PQDR reports in a 12-month period.

8 PR: FD2060-16-91124 PWS Basic

Delivery of Repair 4.13.4 Turnaround Time (TAT) shall be from the date an item has been inducted at the Source of Repair (SOR) and the date the item is completed at the SOR.

TAT for minor repair shall be 30 business days. TAT for major repair is as follows:

LN-100 = 150-days

LN-251 = 100-days

LN-260 = 65-days

EGI/EGI-M Variants = To be determined after EMD Phase.

There shall be no more than 5 late delivery(s) per quarter. The Contractor shall notify the Government if the delivery of any asset will not meet the scheduled delivery date and notification shall occur prior to negotiating a revised delivery date. The late asset shall be delivered by the revised delivery date acceptable to the Government.

CAV-AF & Navy CAV Reporting

4.10 The Contractor shall report repairable

items in CAV-AF and Navy CAV. The

Contractor shall provide data on the actions conducted for each unit. The

Contractor shall report as actions occur.

Delivery of Production Units

4.13.2 At least 95% of production / upgrade

units shall be delivered IAW the periods of performance specified in the task order; the remaining 5% shall be delivered within 30 calendar days of the period of performance specified in the task order. Production orders will be filled as soon as possible. Production shall be able to handle 150 units a month for delivery NLT nine (9) months ARO.

9 PR: FD2060-16-91124 PWS Basic

Quality of Data Submittal/Test Plans/Procedures /Reports

3.1, 4.1 thru 4.5, 4.6.1, 4.6.2, 4.7;4.8, 4.9, 4.11.2 thru 4.11.13, 4.11.15 thru 4.11.28, 4.12.1, 4.12.2,

4.12.3.2 thru 4.12.3.10, 4.12.4.2, 4.13.4, 4.15.1, 4.15.1.1, 4.15.2, 4.15.3, 4.15.3.1, 4.15.3.3, 4.15.4, 4.16, 5.2.4, 5.6, 5.7 and 5.9

The Contractor shall deliver all data/reports associated with all CDRLs, as specified by each CDRL, with no more than one rejection of each deliverable. There shall be no more than three (3) total rejections of deliverables per 12 month period. The Government will reject a deliverable if one (1) or more technical errors or five

(5) or more minor errors are found within the deliverable. A technical error is defined as the format not being IAW the CDRL or the content not being accurate or complete IAW the CDRL, PWS or contract. A minor error is defined as a typographical or grammatical error. The rejected deliverable shall be corrected and resubmitted IAW the associated DD Form 1423 instructions/requirements.

Receipt of Data/Documents

3.1, 4.1 thru 4.5, 4.6.1, 4.6.2, 4.7, 4.8, 4.9, 4.11.2 thru 4.11.13, 4.11.15 thru 4.11.28, 4.12.1, 4.12.2,

4.12.3.2 thru 4.12.3.10, 4.12.4.2,

4.13.4 thru 4.13.7, 4.15.1, 4.15.1.1, 4.15.2, 4.15.3, 4.15.3.1, 4.15.3.3, 4.15.4, 4.16, 5.2.4, 5.6, 5.7 and 5.9

The Contractor shall deliver all CDRLs with no more than three (3) late submissions of deliverables per (12) month period. The Contractor shall notify the Government 30 calendar days prior to the delivery of any data/document that will not meet the scheduled delivery date and negotiate a revised delivery date. The data/document shall be delivered by the revised delivery date acceptable to the Government.

Engineering/ Manufacturing/ Development/

4.13.2 The Contractor shall produce required

units (legacy or modernized) according to Prime Item Development Specification (PIDS) and PWS in the agreed upon timeframes.

Contractor Manpower Reporting

5.8 Within 30 calendar days of

contract/order award, the Contractor shall establish a record for the contract/order in eCMRA including

10 PR: FD2060-16-91124 PWS Basic order data, contact data and location data.

The Contractor shall provide an annual count of Contractor/subcontractor personnel performing services and report all Contractor/subcontractor labor hours required for performance of services for each fiscal year. All data shall be reported no later than October 31 of the following fiscal year.

Adherence to Contractor QMS

5.7 100% compliance with the Quality Management System (QMS) is required, to include, but not limited to, performance thresholds for quality of repair, delivery of repaired assets, and delivery of production units as specified in this Services Summary.

Table 1 - Requirements Summary

Services include, but are not limited to the following platforms in table 2 below.

ARMY NAVY AIR FORCE FMS

None E/A-6B F-18

CH-53K

F-5 P-3

F-16 F-22 E-3 E-8

CF-18

RAAF F/A-18

Fire Scout

AH-64D FMS

F-16 FMS

Chile P3 FMS

Table 2 - Current and Future Platforms for EGI/EGI-M Installations

* Note: This list of platforms is not all encompassing

11 PR: FD2060-16-91124 PWS Basic

Performance of Services During Crisis

The Functional Director has determined that performance of services in this contract is not considered to be mission essential during time of crisis declared by the President of the United States, the Secretary of Defense, or Overseas Combatant Commander IAW

DoDI 1100.22, Policy and Procedures for Determining Workforce Mix, 12 Apr 10 .

3. GOVERNMENT PROPERTY AND SERVICES

Government Property

Contractor shall furnish all material and parts necessary for performance of all requirements. If any Government-Furnished Property (GFP) is provided it will be annotated on an attached contracting form and changes made will be reported on the

Monthly Status Report (MSR). Government Furnished Equipment (GFE) will be annotated on the Contract. Updates as needed will be reported with the MSR.

The Government will provide, without cost to the Contractor, the equipment listed in the attachment to the contract to be used only for performance of this contract. The

Contractor shall manage GFP IAW FAR 52.245-1.

(CDRL A001, DI-MGMT-80368A)

Report of Government Property

The Contractor shall create and maintain records of all Government property accountable to the contract, including GFP and Contractor-Acquired Property (CAP) IAW the Federal Acquisition Regulation (FAR), applicable supplements, guidance and clauses listed in the contract.

Note: Item Unique Identity (IUID) Registry reporting may not be applicable for FMS acquisitions.

Consult with the PCO.

For reporting loss of GFP, the Contractor shall use the Defense Contract Management Agency (DCMA) eTools software application to report loss of GFP at the site below IAW the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract. The reporting requirement does not change any liability provisions or other reporting requirements that may exist under the contract/order.

http://www.dcma.mil/aboutetools

Return/Retention of Government Property:

All GFP remains the property of the Government and shall be returned to the Government upon completion of the contract/order unless the Procuring Contracting Officer (PCO) directs the Contractor to retain the property for continued use under a successor contract.

Retention of the property by the Contractor will require modification of both losing and gaining contracts IAW the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract. All GFP shall be returned to the Government in the condition provided, minus normal wear and tear, unless http://www.dcma.mil/aboutetools

12 PR: FD2060-16-91124 PWS Basic approved in advance by the PCO.

All material generated under the contract/order becomes the property of the Government and shall be returned to the Government upon completion of the contract/order. All

Department of Defense (DoD) Form 1423-1, Contract Data Requirements List (CDRL), and deliverables become the property of the Government upon receipt.

For cost type contracts, the Government obtains title to CAP acquired or fabricated by the

Contractor to perform tasks under the contract IAW the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract.

CAP shall be returned to the Government upon completion of the contract unless the PCO allows the CAP to be retained by the Contractor for continued use under a successor contract. If retained by the Contractor for a successor contract, CAP becomes GFP added to the successor contract by modification of both losing and gaining contracts.

Government Systems

The Government will provide Contractor personnel access to systems necessary to perform tasks under the contract/order, i.e. Joint Engineering Data Management Information Control System (JEDMICS) or Technical Manual systems. Common Access Cards (CAC) shall be required to access Government systems.

The Contractor shall ensure a CAC is obtained/maintained and managed by all Contractor/subcontractor personnel who require a CAC for access to DoD computer networks and systems, for DoD installation entry control and/or for physical access to facilities and buildings to perform tasks under the contract/order in IAW the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract. Upon completion/termination of the Task Order or transfer/termination of Contractor personnel, the Contractor shall ensure the system account(s) are closed. The Contractor is responsible for obtaining and maintaining all forms and publications needed to perform the contract.

Base Support

Government base support may be required for integration of EGI/EGI-M activities.

4. TECHNICAL REQUIREMENTS

The Contractor shall satisfy all technical requirements of this PWS and individual task order requirements. All efforts must be in compliance with the EGI/EGI-M PIDS and System

Requirements Document which accompanies this PWS as well as any CDRLs listed herein. The government will provide EGI-M PIDS/SRD documents prior to release of RFP for production. If there are differences between this PWS and CDRLS, contact AFLCMC

PNT- PO PCO or COR for resolution.

13 PR: FD2060-16-91124 PWS Basic

Program Manager

The Contractor shall provide Program Management support for this IDIQ contract who shall be responsible and have authority for the control and coordination of all work efforts under this contract. The PM support shall manage the administrative, technical, manufacturing, and financial functions of this effort. This includes planning, organizing, staffing, controlling and directing the effort to successfully execute the program. The PM support shall maintain a status of the effort towards achieving the PWS objectives, including all technical and manufacturing activities, problems or deficiencies, impacts, recommended solutions, and results of meetings and reviews.

Monthly Status Reports (MSR)

The Contractor shall provide an MSR to document technical, schedule, and financial status for each task order. MSRs shall cover complete accounting of everything done the previous month such as production, repair, and delivery of EGI/EGI-Ms and, engineering support provided by the Contractor during the previous monthly period. The MSR will document task status, data deliverables, contract issues and actions, expenditure data, and cumulative cost versus estimated total cost. A Funds Expenditures chart that plots actual and planned expenditures and man-hours against time will be included with each status report. In addition, all problem areas will be covered with recommended solutions and the outcome after solution implementation.

(CDRL A001, DI-MGMT-80368A)

Technical Meeting and Working Group Support

The Contractor shall conduct a Kickoff Meeting within 30 days of contract award. The

Contractor shall conduct a preliminary status meeting approximately 90 days after receipt of contract. The Contractor shall support, as a minimum, a bi-weekly telecom with the

Government to provide status updates and issue resolutions. Unscheduled telecoms may be accomplished at the request of either party. The Contractor shall prepare and submit an agenda, meeting minutes and required presentation materials for the Kickoff Meeting and all scheduled program development integration and modernization Technical

Interchange Meetings (TIMs) and Interface Control Working Groups (ICWGs). Support shall include the preparation, review, and coordination of interface specifications.

Coordination shall also include working with designated platform engineering or platform systems engineers to assist in minimizing future integration problems as EGI/EGI-M system functional requirements are incorporated. With program scheduled TIMs/ICWGs, a typical sequence would be a design TIM on day one and an ICWG on day two for each of these periodic scheduled events. As a minimum, the meeting minutes shall include an attendance list, action item list, and any material presented during the meeting.

(CDRL A002, DI-ADMN-81249B/T)

(CDRL A003, DI-ADMN-81250B/T)

(CDRL A004, DI-ADMN-81373/T)

14 PR: FD2060-16-91124 PWS Basic

Integrated Master Plan & Integrated Master Schedule

For individual technical services task orders, the Contractor shall provide an Integrated

Master Plan (IMP) and Integrated Master Schedule (IMS) that clearly and concisely states the plans for executing activities. The IMS shall include all appropriated Systems

Engineering events including: Production Readiness Reviews, ICWGs, Test Readiness

Reviews (TRRs), and critical Government TIMs. The Contractor shall execute the IDIQ events specified within the IMP IAW the IMS. In the event of any unplanned or unforeseen schedule issues, the Contractor shall notify the Government PM within 10 calendar days of the issue becoming known, so as to be able to establish corrective actions or schedule modifications for the IDIQ schedule of CDRL, task, and production deliveries.

(CDRL A005, DI-MISC-80508B/T)

(CDRL A006, DI-MGMT-81861A/T)

Integrated Program Management Report

For individual technical services task orders valued over $20M placed on this contract, the Contractor shall develop, operate and maintain a financial management tracking system. The Contractor shall provide access to supporting reports and documentation that augment the joint Government/Contractor system management capability. The

Contractor shall implement and maintain an Earned Value Management System (EVMS) that incorporates cost/schedule variance reporting. The EVMS shall be used in the management of cost and fixed-price portions of this contract. The EVMS shall track program cost and schedule against established criteria and milestones. The reporting level is defined as the WBS level. The Contractor shall develop and maintain a WBS to execute all tasks IAW the MIL STD-881C and DoD 5000.04-M-1 at the current at time of final RFP release. The Contractor shall comply with Defense Federal Acquisition

Regulation Supplement (DFARS) 252.234-7001, Notice of Earned Value Management

System (Apr 2008) and DFARS 252.234-7002, Earned Value Management System (May

2011). As prescribed in DODI 5000.2, an Earned Value Management System (EVMS) compliant with ANSI/EIA-748 is required for DOD cost or incentive contracts, subcontracts, intra- Government work agreements, and other agreements valued at or greater than $20 million. The EVMS for DOD cost or incentive contracts, subcontracts, and other agreements valued at or greater than $50 million must be formally validated and accepted by the cognizant contracting officer. Although validation is not required below

$50 million, the Contractor must still comply with ANSI/EIA-748. The Contractor shall prepare Integrated Program Management Report, Formats 1-7 on CDRL A01Q and CDRL

A01R.

(CDRL A01Q, DI-MGMT-81861A/T)

(CDRL A01R, DI-MGMT-81468)

15 PR: FD2060-16-91124 PWS Basic

Cost Analysis and Reporting

4.6.1 Contract Work Breakdown Structure

For individual technical services task orders valued over $20M placed on this contract, the Contractor shall develop and maintain a Contract Work Breakdown Structure (CWBS) to execute all tasks IAW the MIL STD-881C and DoD 5000.04-M-1. The CWBS shall encompass the total contracted effort and be extended to the lowest manageable units of work the Office of the Secretary of Defense (OSD) Defense Cost and Resource Center

(DCARC) Deputy Director of Cost Assessment-approved CSDR Plans, or Service Cost

Director. Engineering Change Proposals (ECPs) and supplemental agreements shall require the same level of detail as the basic contract. The contractor shall use the CWBS as the framework for contract planning, budgeting, and reporting of cost, schedule, and performance. The Contractor shall align the CWBS with the IMP and IMS. The Contractor shall notify the Government if the Contractor changes subcontractors or makes new subcontract awards.

(CDRL A01H, DI-MGMT-81334D)

4.6.2 Cost and Software Data Reporting

For individual technical services task orders valued over $20M placed on this contract, the contractor shall systematically collect and report actual contract costs in order to provide DoD cost analysts with needed data to estimate future costs. The Contractor shall establish management procedures that provide for the generation of timely and reliable information for the Contractor Cost Data Reports (CCDRs) and Software Resources Data

Reports (SRDRs) required by the CCDR and SRDR data items of this contract. The

Contractor shall require and flow down the requirement for CSDR reporting to subcontractors at any tier with a subcontract IAW the FAR and all applicable supplements or designated by the Government as being high risk, high value or high technical interest.

The contractor shall notify the Government if the subcontracts exceed $50 million. The contractor shall use the Government-approved CSDR plan for this contract, DD Form

2794, and the related Resource Distribution Table as the basis for reporting. The CSDR shall include cost and useful life information for support equipment with a cost equal to or greater than $100,000. The contractor shall prepare reports IAW DFAR 252.234-7004, DoD 5000.02 and DoD 5000.04-M-1.

(CDRL A01J, DI-FNCL-81565C/T)

(CDRL A01K, DI-FNCL-81566C/T)

(CDRL A01L, DI-FNCL 81567C/T)

(CDRL A01M, DI-FNCL-81765B/T)

(CDRL A01N, DI-MGMT-82035)

(CDRL A01P, DI-FNCL-81992/T)

4.6.3 Cost and Software Data Reporting Post Award Conference

For individual technical services task orders valued over $20M placed on this contract, the Contractor shall host a CSDR post award conference as specified in DFARS

242.503-2 to validate that

16 PR: FD2060-16-91124 PWS Basic the Contractor’s standard CSDR process satisfies the guidelines contained in the DoD

5000.04-M- 1, CSDR Manual, and the requirements in the Government-approved CSDR plan for the contract, DD Form 2794, and related Resource Distribution Table.

Contract Data Requirements Lists

The Contractor shall deliver all data/reports associated with all CDRLs, with no more than one rejection of each deliverable. There shall be no more than three (3) total rejection(s) of deliverables per 12 month period. The Government will reject a deliverable if (1) or more technical errors or five (5) or more minor errors are found within the deliverable. A technical error is defined as the format not being IAW the CDRL or the content not being accurate or complete IAW the CDRL, PWS or contract. A minor error is defined as a typographical or grammatical error. The rejected deliverable shall be corrected and resubmitted IAW the associated DD Form 1423 instructions/requirements.

No more than three (3) late submission(s) of deliverables per 12 month period will be allowed. The Contractor shall notify the Government 30 calendar days prior to required delivery date if any data/document will not meet the scheduled delivery date. The Government will determine if a revised delivery date is acceptable. Unless otherwise specified in this PWS, a specific CDRL or DID, the government shall have 30 calendar days to review and respond to each CDRL delivery. No response from the government within the 30 calendar day timeframe per individual CDRL final delivery connotes concurrence.

Item Unique Identification

Item Unique identification (IUID) is a method of marking items with unique item identifiers which have machine-readable data elements. IUID is required for all items to be delivered to the DoD that meet the criteria established IAW the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract.

The Contractor shall manage the Item Unique Identification (IUID) Requirements Program for the EGI/EGI-M IAW Defense Federal Acquisition Regulation Supplement (DFARS)

252.211-7003, Item Identification and Valuation and Department of Defense (DoD)

4100.39-M, Federal Logistics Information System (FLIS). All assets subject to marking must be recorded in the DoD IUID Registry.

The Contractor shall mark items in accordance contract clauses, and Military Standard

(MIL-STD)-130N, Department of Defense Standard Practice / Identification Marking of

U.S. Military Property.

IAW the Department of Defense Guide to Uniquely Identifying Items Assuring Valuation, Accountability and Control of Government Property, the Government agent or Contractor representative responsible for causing “life cycle events” (i.e., abandoned, consumed, destroyed by accident, destroyed by combat, donated, exchanged, repaired, sold, exchanged by warranty, expended, experimental or target, expended in normal use, leased, loaned, lost, reintroduced, retired, scrapped, sold to foreign Governments, sold for historic purpose, sold for non-Governmental purposes, sold to other federal agencies, 17 PR: FD2060-16-91124 PWS Basic sold to state or local agencies, and stolen) will update applicable item record(s) in the IUID Registry.

(CDRL A007, DI-MGMT-81858/T)

18 PR: FD2060-16-91124 PWS Basic

Counterfeit Electronic Parts

The Contractor shall establish and maintain a counterfeit electronic part detection and avoidance system to mitigate the risk of counterfeit electronics parts being installed in end items or otherwise entering the USAF/DoD inventory. The Contractor shall generate, submit and use a Counterfeit Parts Prevention Plan.

The system shall incorporate processes and procedures to address the requirements listed IAW the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract. The Government's review of the Contractor’s plan will be accomplished as part of the evaluation of the Contractor’s purchasing system IAW the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract.

(CDRL A008, DI-MISC-81832/T)

Commercial Asset Visibility

The Contractor shall report repairable items using Commercial Asset Visibility-Air Force

(CAV-AF). The Contractor shall provide data on the actions conducted for each unit. The

Contractor shall report daily or as actions occur. The following metrics will be monitored:

Government Furnished Material (GFM) In-Transit, Repairable GFM Accountability and

Assets Not on Contract. If CAV-AF training is required, Contractor may send an email to:

406scms.cav.af.ar@us.af.mil

The Contractor shall report all repairable items on attachment “A” to the CDRL A00A for

Navy through electronic submission in the Navy CAV web site IAW Navy CAV SOW

(Statement of Work). This information will be accessed by NAVSUP in order to track repair status and inventory. Data will be submitted by the Contractor as repair transactions occur. Training will be provided by NAVSUP (215) 697-6983/1281. DD 1423-1 applies to both repairable material and Government-furnished repairable.

(CDRL A00B, DI-MGMT-81634C)

(CDRL A00A, DI-MGMT-81634C/T)

System Engineering

4.11.1 Platform Integration/Modification Support

The Contractor shall provide on-site and/or on-call support and assistance during the platform installation/modification. The Contractor shall provide “mating connector sets” for integration if specifically required by individual delivery orders.

4.11.2 Engineering Services

The Contractor shall analyze and resolve technical, operational, integration, testing and logistical issues or concerns that may arise. Efforts will include studies, analyses and recommended solutions as well as aircraft integration and testing support as directed. For

Operational Safety, Suitability, and Effectiveness (OSS&E) authority configurations, technical manual updates shall be provided with appropriate information for c o m m o d i t y mailto:406scms.cav.af.ar@us.af.mil

19 PR: FD2060-16-91124 PWS Basic technical manuals. Individual task orders and associated PWSs may be issued for individual platform integration.

(CDRL A005, DI-MISC-80508B/T)

(CDRL A01T, TM-86-01Q/T)

4.11.3 Integrated Master Schedule & Systems Engineering Management Plan

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/EGI-M program

IMS that depicts major program milestones that are event oriented along with milestone entrance and exit criteria. The IMS 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 IMS at each program review. An updated SEMP and IMS shall be submitted with each new integration or modernization.

(CDRL A00C, DI-SESS-81785A)

4.11.4 Engineering Study

The Contractor shall conduct, as directed and funded by task order by the Contracting

Officer (CO), a platform interface or an engineering study IAW a Government-provided

SOW specific for that study effort. These studies could address a technical issue of a particular integration, modernization, or address technology insertion across the EGI/EGI-

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

(CDRL A00D, DI-MISC-80711A)

4.11.5 Human Engineering

The Contractor, as directed and funded by task order by the CO, 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

Engineering Design Review (EDR).

(CDRL A00D, DI-MISC-80711A)

4.11.6 Program Reviews

The Contractor shall host and conduct platform specific program reviews as required by the individual delivery order. The Contractor shall provide a review agenda, meeting minutes and any required presentation materials.

(CDRL A002, DI-ADMN-81249B/T)

20 PR: FD2060-16-91124 PWS Basic

(CDRL A004, DI-ADMN-81373/T)

4.11.7 Reserved

4.11.8 Technical Reviews

The Contractor shall host and 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 minutes. This task shall be accomplished as required IAW each individual order.

(CDRL A002, DI-ADMN-81249B/T)

(CDRL A003, DI-ADMN-81250B/T)

(CDRL A004, DI-ADMN-81373/T)

4.11.9 Systems Requirements Review

The contractor's PIDS will be reviewed against the system requirements document for each new configuration. The milestone schedule for all technical events shall be reviewed.

(CDRL 002, DI-ADMN-81249B/T)

(CDRL 003, DI-ADMN-81250B/T)

(CDRL 004, DI-ADMN-81373/T)

4.11.10 Engineering Design Review (EDR)

The Contractor shall conduct, as funded under individual task order, an EDR to demonstrate its understanding of the specification(s) and interface requirements.

Analytical and technical information should be presented with enough details to give high confidence the design will meet the 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.

(CDRL A002, DI-ADMN-81249B/T)

(CDRL A003, DI-ADMN-81250B/T)

(CDRL A004, DI-ADMN-81373/T)

4.11.11 Technical Interchange Meeting

The Contractor shall conduct and support TIMs at its facility upon the request of the contracting activity, as funded under individual task orders. The Contractor shall provide the agenda for the meetings, presentation material and document the minutes. The

Government may request specific topics to be addressed.

(CDRL A002, DI-ADMN-81249B/T)

(CDRL A003, DI-ADMN-81250B/T)

(CDRL A004, DI-ADMN-81373/T)

4.11.12 Interface Control Working Group

The Contractor shall support integration and/or modernization ICWGs, as funded under individual task orders. Support shall include the preparation, review, and coordination of interface specifications which define

21 PR: FD2060-16-91124 PWS Basic the EGI/EGI-M electrical, mechanical and signal interface with the designated platform or systems and to assist in resolving integration problems. The Contractor shall establish an

Associate Contractor Agreement (ACA) 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.

(CDRL A002, DI-ADMN-81249B/T)

(CDRL A003, DI-ADMN-81250B/T)

(CDRL A004, DI-ADMN-81373/T)

4.11.13 Test Readiness Review (TRR)

The Contractor shall schedule, host, and conduct a TRR prior to the start of the formal

Computer Software Configuration Item (CSCI) testing, as funded under individual task orders. The Contractor shall use MIL- STD-973 as a guide to define the requirements, criteria, and procedures for conducting the TRR. The Contractor shall brief the latest

Software Test Plan (STP) and demonstrate the adequacy of the STP, including demonstration of traceability of Software Requirement Specification (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.

(CDRL A002, DI-ADMN-81249B/T)

(CDRL A003, DI-ADMN-81250B/T)

(CDRL A004, DI-ADMN-81373/T)

4.11.14 Technical Support

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/EGI-M, analysis of project data, evaluation of EGI/EGI-M failures

(outside warranty and other contractual coverage), and technical evaluation of potential future EGI/EGI-M platforms requirements.

4.11.15 Quick Time Engineer Support

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/EGI-M, as funded under individual task orders. Specific tasks and execution timeframes will be identified in individual order. The Contractor shall respond with a report of finding within 10 working days of the Contractor team’s departure from the location.

(CDRL A00E, DI-NDTI-80809B)

4.11.16 Specifications

As required by the individual delivery order, the Contractor shall prepare and deliver PIDS for each EGI/EGI-M Line Replaceable Unit (LRU) configuration. The Contractor shall prepare and deliver a SRS for each system Operational Flight Plan (OFP) or CSCI.

(CDRL A00F, DI-SDMP-81493A)

(CDRL A00Z, DI-IPSC-81433A)

22 PR: FD2060-16-91124 PWS Basic

4.11.17 Interface Control Document

As required by the individual delivery order, the Contractor shall prepare and deliver an Interface Control Document for each EGI/EGI-M platform configuration.

(CDRL A00G, DI-SESS-81248B)

4.11.18 Configuration Control

The Contractor shall maintain the EGI/EGI-M baseline configuration documentation and prepare Engineering Change Proposals (ECPs), Contract Change Proposals (CCPs) and specification change notices as required. The Contractor shall classify all changes to the hardware or software as either major (Class I) or minor (Class II) IAW criteria specified in section 5.3.1.3 of EIA-649-B. Proposed Class I ECPs shall be submitted IAW DI-SESS- 80639D for review and approval. Proposed Class II ECPs shall be submitted to the Government DCMA for concurrence in classification. I t i s t h e n t h e r e s p o n s i b i l i t y o f D C M A t o p r o v i d e t h i s i n f o r m a t i o n t o t h e L e a d S y s t e m E n g i n e e r w i t h i n A F L C M C / W N Y . DCMA and the EGI/EGI-M System Engineer will have 10 working days to agree or disagree with the ECP classification. The Contractor may proceed with production and delivery at their own risk pending Government approval. No response from the Government will constitute concurrence.

(CDRL A00H, DI-SESS-80639D)

4.11.19 Engineering Change Proposals

The Contractor shall ensure there are no configuration conflicts such as use of the same Government part number or national stock numbers (NSN) with different software or OFP versions. All software changes warrant an NSN and Government part number change which the customer will be responsible to provide Engineering Change Proposals.

Changes to approved baseline configuration items shall be documented through ECPs.

A Specification Change Notice (SCN) shall be submitted to the Government 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 Functional Configuration Audit (FCA)/Physical Configuration Audit (PCA). SCNs or ECPs would be submitted for any documentation change after the baseline configuration is established at FCA/PCA. The Contractor shall provide an ECP System Safety Report for any design changes.

(CDRL A00H, DI-SESS-80639D)

(CDRL A00J, DI-SESS-80643D)

(CDRL A00K, DI-SAFT-80103C)

4.11.20 Corrective Action for Defects Reported

The Contractor shall provide timely correction, reporting of defects found, and corrective actions of repeat discrepancies, in response to Government generated Quality Deficiency

Reports. When requested, the Contractor shall assist the PNT-PO Program Office in the evaluation of LRUs and/or components originally manufactured and repaired under this contract to determine the root cause for deficiencies reported from field organizations through the Material Deficiency Report (MDR)/Product and Quality Deficiency Report

(PQDR) process. MDRs/PQDRs for DoD and FMS will be handled IAW Air Force

23 PR: FD2060-16-91124 PWS Basic

Technical Order (TO) 00-35D-54 USAF Deficiency Reporting, Investigation, and

Resolution. Failure analyses shall be documented in Failure Summary and Analyses

Report. If the cause of the failure cannot be determined, the Contractor shall retain the test record as part of the quality/reliability records.

(CDRL A017, Failure Summary and Analysis Report, DI-RELI-80255A/T)

4.11.21 Request for Variance

The Contractor shall process Request for Deviation (RFDs) or Variance (RFVs) from the approved configuration documentation. Guidance for this documentation is available in

MIL-STD-973, paragraph 5.4.3, and subparagraphs, and Appendix E.

(CDRL A00L, DI-SESS-80640D)

4.11.22 Request for Nomenclature/Computer Program Identification Number

The Contractor shall request nomenclature and/or Computer Program Identification

Number (CPIN) for each integration and/or modernization component. The Contractor shall contact the individual delivery order point of contact (POC) for specific instructions for submittal of CPIN.

(CDRL A00M, DI-SESS-81254C)

(CDRL A00N, DI-MISC-81454C)

4.11.23 Configuration Audits

The Contractor shall support and host configuration audits for each unique integration and/or modernization to establish a production baseline and verify performance requirements have been met. The Contractor shall provide a Configuration Audit Summary

Report and Certification within 30 days of completion of the audit.

(CDRL A00P, DI-SESS-81022D)

4.11.24 Functional Configuration Audit (FCA)

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.

(CDRL A002, DI-ADMN-81249B/T)

(CDRL A003, DI-ADMN-81250B/T)

(CDRL A004, DI-ADMN-81373/T)

4.11.25 Physical Configuration Audit (PCA)

The Contractor shall support and host a PCA for each integration and/or modernization to ensure the “as built configuration” of the unit matches the configuration identification documentation. The Contractor shall provide an agenda, presentation materials and document the minutes.

(CDRL A002, DI-ADMN-81249B/T)

24 PR: FD2060-16-91124 PWS Basic

(CDRL A004, DI-ADMN-81373/T)

4.11.26 Software and Hardware Development / Data

Contractor shall develop firmware, OFPs, and all other software related to the functionality of the EGI/EGI-M IAW the approved software requirements. Software development shall be continuous in nature with the process lending itself to be reactive to issues arising from testing and/or platform integration, enabling delivery of incremental/iterative software solutions quickly, meeting mission needs at the earliest date possible. The Contractor shall document all software developed to include any improvements/updates/upgrades beyond the initial software baseline.

Note: All requirements listed in paragraphs 4.11.26.1 through 4.11.26.2.1.3 are per funded individual task orders.

4.11.26.1 Hardware/Software Enhancements

The Contractor shall provide technical insertions or modifications for future growth such as new requirements and capabilities. This includes 3rd party software applications for alternative PNT navigation with multiple 18-month Period of Performance (PoP) cycles that can be started at any time during the Production and Sustainment Phase. A notional roadmap schedule shall be developed for visualization of incremental software build development, testing, and delivery. Incremental builds containing the new capability shall be delivered to the Government upon request. The Contractor may elect to provide the government with a prioritized list of recommendations for hardware technology insertion due to obsolescence or new technologies and/or categorized candidate software enhancements with new capabilities.

4.11.26.1.1 Hardware/Software Enhancement Priorities

Hardware enhancement/technical insertion and/or software enhancements with new added software capability shall be categorized and prioritized based on government

EGI/EGI-M Joint Requirements Identification and Prioritization (JRIP) process resulting in a priority funding list based on Research, Development, Test, and Evaluation

(RDT&E) funding for hardware modifications or software development.

4.11.26.1.2 New/Modified Test Equipment

Modification projects for hardware technology insertion or software enhancements with new capability includes integration & test and/or modifications of existing test equipment or new test equipment. Software enhancements with new added software capabilities requiring new or modification of test equipment or test software including test simulations will be part of the EGI/EGI-M JRIP prioritization process for budgetary planning purposes.

4.11.26.1.3 Documentation

25 PR: FD2060-16-91124 PWS Basic

When directed, the Contractor shall update all hardware/software documentation affected by modifications/enhancements and deliver to the Government. The

26 PR: FD2060-16-91124 PWS Basic

Requirements Verification Traceability Matrix (RVTM) shall be updated and traceability from PIDS to test reports demonstrated. In addition, the Contractor shall develop/update

EGI/EGI-M Core PIDS, ICD’s, and core Platform Integration guides and deliver to the

Government, as required.

4.11.26.1.4 Technical reviews, TIMS and Other Meetings

The Contractor shall schedule and conduct all meetings on an as required basis per individual order.

4.11.26.1.5 Testing

The Contractor may be required to perform a complete Functional Qualification Test

(FQT) to include regression testing and updated software testing required as a result of each new software enhancement and/or new capability. Regression testing shall include cybersecurity testing as needed for modified or new Computer Software Configuration

Items (CSCIs).

4.11.26.1.6 Airworthiness and Certifications

The Contractor shall maintain all certifications or airworthiness qualifications for EGI-

M. This includes any re-certifications to maintain compliance with MSO-145B, air worthiness for safety-critical software, and all DAL requirements associated with EGI-

M.

4.11.26.2 Platform Support

The Contractor shall provide technical and logistic support to platforms during operational test and evaluation (OT&E) as required per individual delivery order. This includes end to end and weapons testing that may result from EGI/EGI-M OFP modifications.

4.11.26.2.1 Software Management and Administrative Support

4.11.26.2.1.1 Maintain Core Software Support

Contractor shall maintain a core software support team to sustain and modify the specified systems and software. The Contractor shall perform requirements analysis, functional analysis, software unit testing, system testing, software quality assurance, configuration management, program control, and software programming as necessary.

The Contractor shall update and deliver their EGI/EGI-M software development plan for each new CPCI developed or each CPCI modified.

(CDRL A012, DI-IPSC-81427B/T)

27 PR: FD2060-16-91124 PWS Basic

4.11.26.2.1.2 Software Modification

Software modifications are changes to address software discrepancy reports or changes to fielded software modules. All software modifications shall produce the required functionality within the timeframe required by the government per individual delivery order.

4.11.26.2.1.3 Software Enhancements

The Contractor shall…