SPN-50_SOW_10.05.15.pdf

Statement of Work For

Shipboard Air Traffic Radar (SATR)

AN/SPN-50(V)1

Prepared by

SATR AN/SPN-50(V)1 IPT

5 October 2015

PID: N00019-16-P1-PMA-213-0002

N00019-15-R-0081

5 October 2015

pg. 2

Table of Contents

1 Scope

2 Background

3 Applicable Documents

4 System

4.1 Pre-CDR EDM Radar Systems (CLIN 0001, 0002)

4.2 CDR Compliant EDM Radar Systems (CLIN 0003, 0004)

5 Program Management

5.1 Program Planning and Control

5.2 Integrated Master Plan / Integrated Master Schedule for EVM Contracts

5.3 Financial Management Report

5.4 Contractor Cost Data Reporting (CCDR)

5.5 Life Cycle Cost Estimate

5.6 Program Management Reviews

5.7 Bi-Weekly Status Update

5.8 Contractor Integrated Performance Management

5.9 Integrated Baseline Review (IBR)

5.10 Subcontract Cost/Schedule Management and Reporting

5.10.1 Non FFP Subcontracts

5.11 Contract Work Breakdown Structure (CWBS)

5.12 Over Target Baseline (OTB)/Over Target Schedule (OTS)/Restructure

5.13 Schedule Risk Assessment (SRA)

5.13.1 Program Schedule Assessment (PSA) and SRA Instructions

5.14 Annual Schedule Risk Assessments

6 Configuration Management / Data Management

6.1 Configuration Management (CM)

6.2 Configuration Identification

6.3 Configuration Change Control

6.4 Requests for Variances

6.5 Configuration Status Accounting

5 October 2015

pg. 3

6.6 Configuration Verification and Audit Plan

6.7 Configuration Audit Summary Report (CASR)

6.8 Contractor Internal Data Requirements (Data Accession List)

6.9 Data Submittals

7 Systems Engineering

7.1 Systems Engineering Management Plan

7.2 Systems Engineering Activities

7.3 Systems Engineering Technical Reviews (SETR)

7.4 Reserved

7.5 Technical Working Groups

7.6 Reserved

7.7 Performance Risk

8 Software Activities

8.1 Software Planning

8.2 Software Version Release

8.3 Open Systems Approach and Goals

9 Spectrum Supportability (SS)

9.1 Spectrum Supportability Risk Assessment (SSRA)

9.2 Frequency Assignment Requests and Equipment Spectrum Certifications (ESCs)

9.3 Electromagnetic Environmental Effects (E3)

10 Reliability Planning

10.1 Reliability and Maintainability (R&M) Program Plan

10.2 Reliability Block Diagrams and Maintenance Models

10.3 Electronic Parts/Circuits Tolerance Analysis Report

10.4 Reserved

10.5 Reliability Prediction and Documentation of Supporting Data

10.6 Failed Item Analysis Report

10.7 Corrective Action Plan

10.8 Failure Summary and Analysis Report

10.9 Failure Modes, Effect, and Criticality Analyses (FMECA)

10.10 Thermal Analysis and Survey

5 October 2015

pg. 4

10.11 R&M Testing

10.11.1 Component/Spare Acceptance Testing

10.11.2 Environmental Test Procedures

10.11.3 Environmental Test Reports

10.11.4 Reliability Demonstration/Reliability Growth

11 System Safety Program

11.1 System Safety Program Plan

11.2 System Safety Working Group

11.3 System Safety Analysis and Documentation

11.4 Software Safety

12 Human Systems Integration

12.1 Human Systems Integration Program Plan (HSIPP)

12.2 Human Engineering Design Approach Document

12.2.1 Operator

12.2.2 Maintainer

13 Maintenance Planning

13.1 Maintainability Planning

13.1.1 Logistics Product Data

13.1.2 AN/SPN-50(V)1 Supportability Data

13.1.3 Maintainability Prediction

13.1.4 Maintainability Demonstration (M-DEMO) and BIT Assessment Tests

13.1.5 Corrosion Prevention and Control

13.1.6 Life Cycle Support Concept

13.2 Training

13.2.1 Training Course: Pre-CDR

13.2.2 Maintenance Training Plan

13.2.3 Maintenance Training Materials

13.2.4 Operator Training Materials

13.2.5 Training Course: Post CDR

14 Supply Support

14.1 Data Rights and Product Drawings

5 October 2015

pg. 5

14.1.1 Design Drawings and Associated Lists

14.2 Engineering Data for Provisioning

14.3 Diminishing Manufacturing Sources and Material Shortage (DMSMS) and

Obsolescence

14.4 Bill of Materials

14.5 Lead-Free Control Plan

14.6 Counterfeit Components Program

14.7 Item Unique Identification (IUID)

14.8 Radio Frequency Identification (RFID)

14.9 Packaging, Handling, Storage & Transportation (PHS&T)

14.9.1 PHS&T Program

14.9.2 Packaging

14.10 Technical Publications

14.11 Support Equipment

14.12 Performance-Based Logistics (PBL) Business Case Analysis (BCA)

14.13 Industrial Overhaul and Repair

14.14 Demilitarization & Disposal

15 Material

15.1 Lead Time List and Interim Spares List

15.2 Logistics Product Data

15.3 Interim Spares and Repair Parts Management

15.4 Repair Management

16 Test and Evaluation

16.1 Contractor Test Support Personnel

16.2 EMD Risk Reduction Test Plan

16.3 Test & Evaluation Working IPT (T&E WIPT)

16.4 Deficiency Review Board (DRB)/Trouble Report (TR) Support

16.5 Software Test Acceptance

16.6 Master Test Plan

17 Production

17.1 Manufacturing Planning

5 October 2015

pg. 6

17.2 Subcontractor/Supplier Management Program

17.3 Quality Management System

17.4 Incremental Production Readiness Reviews

17.5 Production and Quality IPT Meeting

18 Information Assurance

5 October 2015

pg. 7

1 Scope

This Statement of Work (SOW) is for the Engineering Manufacturing and Development (EMD) phase of the Shipboard Air Traffic Radar (SATR) AN/SPN-50(V)1 Program. The Government is the Lead System Integrator (LSI) for this effort. The contractor will provide hardware, documentation and technical services to support the AN/SPN-50(V)1 Program EMD phase requirements.

The hardware requirements include two (2) Engineering Design Model (EDM) radar systems early in the EMD phase to be used as AN/SPN-50(V)1 Pre-CDR configuration EDM Radar

Systems (PCC-EDM), one (1) CDR configuration EDM Radar System later in the EMD phase, upgrade of the two (2) PCC-EDM Radar Systems to the CDR configuration, and the spare/repair parts to support all radar systems through the EMD phase.

Upon installation at Webster Field AN/SPN-50(V)1 System Installation Lab, and successful completion of the Government approved functional checkout for the AN/SPN-50(V)1 PCC-

EDM, the first PCC-EDM Radar System shall be used for testing, training, and familiarization.

After successful completion of the Government approved functional checkout for the AN/SPN-

50(V)1 PCC-EDM Radar System, the second PCC-EDM Radar System will be stored and supported at the Offeror’s factory/ test facility. To support EMD risk reduction activities, the contractor shall conduct radar system testing to identify and evaluate moderate-to-high risk areas, including but not limited to the following areas: support package design trades, test and evaluation planning, provide performance metrics for product support and organic support requirements, workload estimates, specification compliance, logistic requirements, prototype demonstration events, fabrication, and calibration. Prior to the start of Developmental Test, the two PCC- EDM Radar Systems will be upgraded to the CDR compliant configuration. The

PCC-EDM Radar Systems that have been upgraded to the CDR compliant configuration and the

CDR compliant radar manufactured during the EMD phase will be used to support testing events leading to Initial Operating Capability (IOC).

2 Background

AN/SPN-50(V)1 program has been initiated to design, develop, produce, and deploy an Air

Traffic Radar improved radar system that will replace the aging AN/SPN-43C radar used for Air

Traffic Control aboard U.S. Navy Aircraft Carriers and Amphibious ships. The AN/SPN50(V)1

Radar System will replace the AN/SPN-43C System, and mitigate current performance gaps. The

AN/SPN-43C is an analog radar with no modern signal processing capability. Its performance suffers from excessive clutter displayed on the screen, mounting maintenance costs, restrictions when operating the radar close to shore, and operating frequency range reduction due to the proliferation of Long-Term Evolution (LTE) cellular data networks.

5 October 2015

pg. 8

3 Applicable Documents

The following documents are applicable to this SOW:

1. AN/SPN-50(V)1 Shipboard Air Traffic Radar (SATR) Systems Requirements Document

(PMA213-0100, 2 October 2015) (AN/SPN-50(V)1 SRD) also known as the AN/SPN-

50(V)1 System Specification.

2. DoD Corrosion Prevention and Control Planning Guidebook for Military Systems Spiral

No. 4 of February 2014

3. DoD Instruction 5000.02 Operation of the Defense Acquisition System Dated 7 January

4. DoD Directive 5000.01, The Defense Acquisition System, May 12, 2003

5. NAVAIRINST 4355.19 Systems Engineering Technical Review Process (SETR)

Handbook

6. PMA213 Formal Data Item Deliverable Process Guide for PMA213, February 2014

7. Draft System Engineering Plan for AN/SPN-50(V)1, Shipboard Air Traffic Radar

8. Draft PMA-213 SATR Item Unique Identification (IUID) Plan

9. Draft Test and Evaluation Master Plan for AN/SPN-50(V)1 SATR

10. MIL-STD-882E, System Safety, 11 May 2012

11. Programmatic Environment, Safety, and Occupational Health Evaluation for the

AN/SPN(V)1 SATR Program, 23 June 2015

12. EIA-649-1 Configuration Management Requirements for Defense Contracts

13. MIL-STD-1629 Procedures for Performing a Failure Mode, Effects, and Criticality

Analysis ( 24 Nov 1980)

14. MIL-HDBK-1568C Design Criteria Standard Materials and Processes for Corrosion

Prevention and Control in Aerospace Weapons Systems 12 Aug 2014

15. GEIA-STD-0005-1 Performance Standard for Aerospace and High Performance

Electronic Systems Containing Lead-free Solder

16. GEIA-STD-0005-2 Standard for Mitigating the Effects of Tin Whiskers in Aerospace and

High Performance Electronic Systems

17. GEIA-HB-0005-1 Program Management/Systems Engineering Guidelines for Managing the Transition to Lead-Free Electronics

18. SAE AS5553A Counterfeit Electronic Parts; Avoidance, Detection, Mitigation, &

Disposition Jan 2013

19. SAE AS6081 Fraudulent/Counterfeit Electronic Parts: Avoidance, Detection, Mitigation, & Disposition – Distributors Counterfeit Electronic Parts 4 Apr 2015

20. NAVINST 11000.1 Identification and Documentation of Facility Requirements in

Support of Naval Aviation Weapons Systems June 12, 2013

21. DoD Product Support Business Case Analysis (BCA) Guidebook, dated April 2011

22. DoD Suppliers’ Passive RFID Information Guide, Version 14, dated September 2009, 5 October 2015

pg. 9

23. DoDI 4140.01-R DoD Supply Chain Material Management Policy dated 24 Dec 2014

24. DoD 5220.22-M National Industrial Security Program Operating Manual, (NISPOM).

Feb 28, 2006

25. DoDI 4650.1 Policy and Procedures for Management and Use of the Electromagnetic

Spectrum

26. DoDM 5000.04-M-1, Cost and Software Data Reporting (CSDR) Manual November

27. DoD Instruction 8500.2 Information Assurance Implementation (dated February 6, 2003)

28. DoN Automatic Identification Technology (AIT) Implementation Manual, dated June

2006,

29. DoD Joint Software Systems Safety Handbook ( 27 Aug 2010) (JSSSEH)

30. MIL-DTL-24784/4 Rev C DETAIL SPECIFICATION SHEET: COMMERCIAL OFF-

THE-SHELF (COTS) EQUIPMENT MANUAL REQUIREMENTS (03 NOV 2007).

31. MIL-HDBK-46855A Department Of Defense Standard Practice Human Engineering

Requirements for Military Systems, Equipment, and Facilities 24 May 2011

32. MIL-HDBK-470A Designing and Developing Maintainable Products and Systems (

Volume 1) 4 Dec 1997

33. MIL-HDBK-472 Military Standardization Handbook: Maintainability Prediction (24

May 1966)

34. MIL-HDBK-61A, Configuration Management Guidance (07 Feb 2001)

35. MIL-HDBK-781 Reliability Test Methods, Plans, and Environments for Engineering , Development, Qualification and Production ( 01 Apr 1996)

36. MIL-STD-100G Standard Practice for Engineering Drawings ( 9 Jun 1997) ASME

Y14.100,ASME Y14.24, Y14.34M,Y14.35M, Y14.41

37. MIL-STD-130, Identification Marking of U.S. Military Property

38. MIL-P-24534A Planned Maintenance System, Development of Maintenance

Requirement Cards, Maintenance Index pages, and Associated Documentation 7 May

39. MIL-STD-464C, Department Of Defense Interface Standard: Electromagnetic

Environmental Effects, Requirements For Systems December 2010

40. MIL-STD-881C Department Of Defense Standard: Work Breakdown Structures (WBS)

For Defense Materiel Items October 2011

41. MIL-STD-1399 Military Standard Interface Standard for Shipboard Systems Section

300A Electrical Power, Alternating Current

42. MIL-STD-1472G, 11 January 2012, Department of Defense Design Criteria Standard, Human Engineering

43. MIL-STD-167-1A Mechanical Vibrations of Shipboard Equipment (Type I -

Environmental and Type II – Internally Excited)

44. MIL-STD-3018 Department of Defense Standard Practice: Parts Management (15 Oct

2007)

5 October 2015

pg. 10

45. MIL-STD-461F Requirements for the Control of Electromagnetic Interference

Characteristics of Subsystems and Equipment

46. MIL-STD-464 Electromagnetic Environmental Effects Requirements for Systems

47. MIL-STD-810G Department of Defense Test Standard: Environmental Engineering

Considerations and Laboratory Tests, 15 April 2015

48. MIL-STD-882E Department of Defense Standard Practice: System Safety

49. MIL-S-901, Military Specification: Shock Tests. H.I. (HIGH-IMPACT) Shipboard

Machinery, Equipment, and Systems, Requirements for

50. NAVAIR 00-80T-105 CV NATOPS Manual

51. NAVAIR 00-80T-106 LHA/LHD NATOPS Manual

52. NAVAIRINST 2400.1 Electromagnetic Environmental Effects and Spectrum

Supportability Policy and Procedures

53. NAVAIRINST 4130.1D Naval Air Systems Command Configuration Management

Process 19 December 2006

54. NAVAIR Instruction 4790.35, Diminishing Manufacturing Sources and Material

Shortages 17 May 2010

55. NAVSEA 04L, A Program Manager's Guide to the Application for Performance Based

Logistics (PBL), dated of 8 October 2008

56. NAVSEA TE000-AB-GTP-010 Parts Derating Requirements and Application Manual for

Navy Electronic Equipment: Parts Application Manual – Part 1 (28 Feb 1991)

57. NAVSEA Tech. Spec. 9090-700 (Series) Configuration Data Manager’s Database-Open

Architecture (CDMD-OA)

58. NAVSEAINST 4790.8C, March 2013 Ships Maintenance and Material Management (3-

M) Manual

59. NAWCAD document 43140-00991, General Acceptance Test Plan

60. Open Architecture Computing Environment Technologies and Standards v1.0 – Open

Architecture Program: An Enterprise Approach to Introducing Open Architecture into

Navy Warfare Systems… And Beyond (23 Aug 2004)

61. OPNAVINST 1500.57A Surface Warfare Training Strategy

62. OPNAVINST4790.4F Ships Maintenance and Material Management (3-M) System

Policy 27 October 2014

63. OPNAV 4442.5A (N4) Readiness Based Sparing Aug 15 2011

64. OPNAVINST 2400.20F Electromagnetic Environmental Effects (E3) and Spectrum

Supportability Policy and Procedures

65. OPNAV M-5090.1 Environmental Readiness Program Manual dated 10 January 2014

66. PMA213 Naval Air Traffic Management Systems Office of Primary Responsibility

Configuration Management Plan October 2013

67. Aerospace and Defense Industries Association of Europe (ASD) (Formerly AECMA)

Specification S1000D.

68. ANSI/EIA-748-B Industry Guidelines for Earned Value Management Systems (EVMS)

5 October 2015

pg. 11

69. Federal Information Processing Standard 140-2 (FIPS 140-2) Security Requirements for

Cryptographic Modules May 25, 2001

70. SAE-GEIA-STD-0007 Logistics Product Data Handbook

71. SAE TA-HB-0007-1 Logistics Product Data Reports Handbook

72. IEEE/EIA Std 12207-2008 Standard for Information Technology – Software Life Cycle

Processes, 21 March 2008

73. ISO 10005:2005 Quality Management Systems – Guidelines for Quality Plans

74. ISO 10303/AP233 Industrial Automation Systems and Integration Part 233

75. NTIA Manual of Regulations and Procedures for Federal Radio Frequency Management

(RedBook)

76. Open Architecture Computing Environment Design Guidance v1.0 23 Aug 2004

77. SAE AS6500 Manufacturing Management Program

78. SAE/AS9100C Quality Management Systems: Requirements for Aviation, Space &

Defense Organizations

79. SAE AS9102B Aerospace First Article Inspection Requirements

80. SAE-GEIA-STD-0007 Logistics Product Data Handbook, Feb 10 2014

81. SD-22 DMSMS Guidebook August 2012

82. TechAmerica-STD-0016 Standard for Preparing a Diminishing Manufacturing Sources and Material Shortages (DMSMS) Management Plan

83. TechAmerica-EIA-GEB-1, Diminishing Manufacturing Sources and Material Shortages

(DMSMS) Management Practices

84. Title 47 USC Sections 305 Government Owned Stations and 901-904 ( Definitions, Findings Policy) ( Establishment: assigned functions) , ( Spectrum Management

Activities), (General Administrative Provisions, (Public Law 102-538

Telecommunications Authorization Act of 1992)

85. Schedule Risk Assessment (SRA) Instruction

86. Program Schedule Assessment (PSA) Instruction

87. PMA213 Risk Opportunity Management Plan

88. NIST SP800-53 revision 4, April 2013

89. CNSSI No. 1253 Security Categorization and Control Selection for NSS. March 2014

90. DON CIO Memo, Information Assurance Policy for Platform IT, dated 26 April 2010; in support of Platform Information Technology (PIT) Risk Approval (PRA) Certification and Accreditation (C&A)

91. 2014 DON CIO Memo, Information Assurance Policy for Platform IT, dated 26 January

92. DoD 8570.01-M, IA Workforce 19 Dec 2005

93. DoDI 8510.01, Risk Management Framework (RMF) March 12, 2014

94. DoDI 8500.01, "Cybersecurity," March 14, 2014

95. DoDI 5200.44 Trusted Systems and Networks, November 2012

96. NIST SP800-30, "Guide for Conducting Risk Assessments," September 2012

5 October 2015

pg. 12

97. DON Guide for Developing Performance Based Logistics Business Case Analysis (P07-

006) 6 Nov 2007

98. AN/SPN-50(V)1 Systems Integration Laboratory (SIL) Facilities Plan

99. MIL-STD-31000A, DoD Standard Practice: Technical Data Packages (TDP), 26

February 2013

100. IAW MIL-HDBK-217, Military Handbook: Reliability Prediction of Electronic

Equipment, December 1991

101. MIL-STD-810, DoD Test Method Standard, October 2008

4 System

This contract will include the procurement of three radar systems defined as two pre-CDR EDM

Radar Systems and one post CDR Configured EDM Radar System. The two (2) Pre-CDR Radar

Systems shall be accepted after successful completion of the factory performance testing and

Government acceptance of the test results in accordance with (IAW) CDRL A084. The CDR

Compliant EDM Radar System and updated two pre-CDR Radar systems shall not be accepted for final delivery until they have successfully completed the Government approved and

Government witnessed System Operations and Verification Tests (SOVT) and are found compliant with the AN/SPN-50(V)1 System Specification.

4.1 Pre-CDR EDM Radar Systems (CLIN 0001, 0002)

a) The contractor shall provide two (2) PCC-EDM Radar Systems for Government and contractor testing that are in compliance with the contractor’s radar production specifications. Any PCC-EDM radar system non-compliance with the AN/SPN-50(V)1

System Specification will be documented and provided IAW CDRL A001. Each PCC-

EDM radar system shall consist of the following:

1) One (1) contractor’s shipboard radar system with all related equipment and material including but not limited to all cables, wires, and material necessary to connect all system components.

2) One (1) radar maintenance and control console to be installed in the below deck equipment rack.

3) One (1) remote Radar Set Control (RSC).

b) The contractor shall provide radar component information including size, weight, system constraints, cooling and prime power requirements IAW CDRL A001.

c) The contractor shall provide Interface Control Drawings conforming to the Technical

Data Package specification for Limited Design Disclosure, Production Level drawings as

5 October 2015

pg. 13 defined in MIL-STD-31000A and IAW CDRL A003, and CDRL A086.The contractor shall provide a Bill of Materials IAW CDRL A007.

d) The contractor shall provide radar performance data for the Equipment Location -

Certification Information Database request (EL-CID documentation) IAW CDRL A008.

e) The contractor shall provide operator and maintainer training to the Government personnel as defined in section 13.2.

f) The contractor shall provide sparing and repair parts to the Government as defined in section 15.3.

g) The PCC-EDM radars shall have passed factory performance testing in accordance with the contractor’s performance tests, and the results of those tests shall be delivered to the government IAW CDRL A084.

h) The contractor shall conduct and provide a site survey at Webster Field, MD, IAW

CDRL A002.

i) The contractor shall provide documentation on the installation of the PCC-EDM radars, to include unpacking, initial turn on, configuration, and alignment IAW CDRL A001.

4.2 CDR Compliant EDM Radar Systems (CLIN 0003, 0004)

a) The contractor shall provide one (1) EDM system based upon the previously designed system and in compliance with the AN/SPN-50(V)1 System Specification. The EDM systems shall include the following:

1) One (1) Critical Design Review (CDR) approved configuration radar system of the contractor’s shipboard radar with all related equipment and material including but not limited to all cables, wires, and material necessary to connect all system components.

2) One (1) local radar maintenance and control console to be installed with the below deck equipment rack.

3) One (1) remote Radar Set Control (RSC).

b) The contractor shall perform installation, unpacking, initial turn on, configuration, adaptation, and alignment of the Post-CDR radars at St. Inigoes, MD IAW the procedures provided under CDRL A001.

c) The contractor shall provide updated system component information IAW CDRL A001 including size, weight, system constraints, cooling and prime power requirements.

d) The contractor shall provide Interface Control Drawings conforming to the Technical

Data Package specification for Limited Design Disclosure, Production Level drawings as defined in MIL-STD-31000A and IAW CDRL A003, and CDRL A086.

e) The contractor shall update the Bill of Materials IAW CDRL A007.

f) The contractor shall provide radar performance data for the EL-CID documentation IAW

CDRL A008.

5 October 2015

pg. 14

g) The contractor shall provide operator and maintainer training to the Government personnel as defined in section 13.2 of this SOW.

h) The contractor shall provide sparing and repair parts to the Government as defined in

Section 15.3.

i) The contractor shall retrofit the software, hardware, and provide the technical manual changes required to update the two PCC-EDM radars to the AN/SPN-50(V)1 Critical

Design Review (CDR) Government approved configuration. The update changes shall be documented IAW CDRLs A009 and A010.

j) The contractor shall provide a Systems Operation and Verification Test (SOVT) procedure for review and approval by the Government IAW CDRL A047.

k) Acceptance of the three CDR compliant EDM radar systems is contingent on the EDMs successfully passing the Government approved and Government witnessed SOVT, and delivery of the SOVT data IAW CDRL A053.

CLIN 0003, 0004 (Non-recurring)

5 Program Management

The contractor shall be responsible for all contractor performance requirements activities under this contract, including all subcontractors, suppliers, and sub-tier contractors. The contractor shall identify points of contact for program management, engineering, software, configuration management, contracts, reliability, quality, integration support, and logistics. The contractor shall host a post award conference that addresses the requirements of FAR 42.5 within 30 calendar days of contract award.

5.1 Program Planning and Control

The contractor shall develop and implement a Management Program that clearly defines how the

AN/SPN-50(V)1 Acquisition Program will be managed and controlled. Using MIL HDBK-881 as a reference, a contractor Work Breakdown Structure (CWBS) built upon the Government provided WBS shall be developed in sufficient detail to identify contractor and sub-contractor responsibilities IAW CDRL A011.

5.2 Integrated Master Plan / Integrated Master Schedule for EVM Contracts

The contractor shall develop and implement an Integrated Master Plan (IMP) and an Integrated

Master Schedule (IMS), to which the Government shall have continuous access. The IMP shall define the structure of the events, accomplishments, and criteria for executing the program.

Detail shall be such that the Government and contractor can utilize the schedule(s) for program planning, procurement planning, tracking and execution of the AN/SPN-50(V)1 Acquisition

Program development effort, decision and problem analysis, risk analysis, and schedule reporting

5 October 2015

pg. 15 to be documented IAW CDRL A012. The IMS shall contain the contract events and milestones, accomplishments, criteria, and activities from contract award to the completion of the contract.

IMS tasks shall be directly traceable to control accounts included in the cost system, as collected by WBS and integrated with the Cost Summary Data Report (CSDR) IAW CDRL A013.

The contractor shall manage the execution of the AN/SPN-50(V)1 EMD program contract effort using the IMS and associated IMP as day-to-day execution tools and to periodically assess progress in meeting program requirements. The contractor shall deliver an IMS covering the work scope of the EMD phase contract IAW CDRL A019. The contractor shall include all subcontractor interfaces, dependencies (including external platform integration events) and program schedule activities commensurate with the level of detail in the Prime Contractor’s IMS.

The contractor shall display the first six months of program effort to the level of detail commensurate with work package level in the first IMS submission. This level of detail will be the basis for the future Performance Measurement Baseline (PMB) establishment. The contactor shall display the remaining period of performance in the first IMS deliverable, at a level consistent with the contractor's EVM processes.

5.3 Financial Management Report

The contractor shall provide a report summarizing the authorized value, incurred value (both labor and material), and estimate at completion (EAC) in dollars and hours and schedule to completion IAW CDRL A013.

5.4 Contractor Cost Data Reporting (CCDR)

The contractor shall systematically collect and report actual contract costs to provide DoD cost analysts with needed data to estimate future costs IAW CDRLs A014, A015, and A016.

The contractor shall:

a) Use the most current approved DoD 5000.04-M-1 EMD Contract CSDR Plan, DD Form

2794 Cost of Software Data Reporting, as the baseline for reporting.

b) Provide relevant DD Form 1921, 1921-1, and 1921-2 data for every indicated element identified within the EMD Contract CSDR Plan.

c) Provide DD Form 1921-3 to describe overhead cost by contractor site. (if applicable)

d) Provide updates to the EMD Contract CSDR Plan and Production Resource Distribution

Table (RDT) for Government approval via the Contractor Working Integrated Product

Team (CWIPT). Updates include, but are not limited to: aligning reporting Subcontractor effort to a single WBS element and updating the RDT as new Subcontracts are awarded.

e) Flow-down Contractor Cost Data Reporting requirements to any Subcontracts valued at over $50 million or any Subcontracts valued between $20 million and $50 million that

5 October 2015

pg. 16 are designated by the program as high risk, high value, or high technical interest.

Reporting thresholds are inclusive of all modifications and are given in then-year dollars.

f) A post award meeting will be held after contract award at the contractor’s facility to include a discussion of the contractor’s standard Cost and Software Data Reporting

(CSDR) process that 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.

5.5 Life Cycle Cost Estimate

The contractor shall create, update, and maintain a Life Cycle Cost Estimate (LCCE) in constant

FY 2015 dollars using the latest OSD Inflation Indices. The LCCE shall be based on MIL-STD-

881C Appendix B, Electronic Systems, and the approved CSDR Contract Plan. The contractor shall include a description of the cost methodology used to estimate each WBS element. The contractor shall also include all prime contractor and subcontractor costs for development, production, fielding, sustainment, and disposal. The contractor shall use Microsoft Excel, 2007 version or newer, as the basis of the LCCE model and provide the capability to accommodate varying acquisition, technical, and programmatic changes by the Government to make informed program decisions. It is imperative that all electronic copies of the LCCE model contain functioning, traceable spreadsheet formulas. The contractor shall submit the LCCE, the LCCE model, and supporting data IAW the System LCCE and Model IAW CDRL A017.

5.6 Program Management Reviews

The contractor shall conduct a Program Management Review (PMR) with Government representation every six months, at the contractor’s facilities with the use of teleconference/video teleconference (VTC)/Government-provided online file sharing service. The duration of each

PMR event is expected to be no more than three (3) days. The PMRs shall be conducted to provide the Government the necessary visibility into the conduct and consequences of the various efforts of the contractor and its subcontractors. During the review, the contractor shall present and review the status of issues surrounding the technical, financial, and schedule performance of the contract and highlight problem areas and recommendations for corrective actions. The contractor shall structure the PMRs in an Integrated Product Team (IPT) format and ensure the agendas shall include the following topics and provided IAW with A085:

a) A brief overview and status and progress toward achieving program objectives.

b) Earned value review. A review of updated IMS, IMP and CWBS elements, including critical path analysis. IPT leads or functional managers shall include cost information in discussions of schedule status, technical performance, and risk using earned value as an integrating tool. The following shall be addressed: Cost and schedule trends; significant cost, schedule, and technical variances; projected impacts; quantified risk assessments;

and corrective action plans.

5 October 2015

pg. 17

c) Risk status.

d) Staffing.

e) Changes in established system design and configuration and rationale for those same changes.

f) Hardware and software development status.

g) Reliability program status.

h) Review of contract modifications and changes since last PMR and proposed additional contract modifications, changes, including rationale.

i) Technical Performance Measures, Metrics status.

j) Leading performance indicators in use by the contractor.

k) Software process improvement status.

l) Open Architecture status of key interfaces and design considerations in other IPT efforts.

m) Logistics.

n) Test status, including test planning and results, and any issues relative to test resources, assets, and facilities.

o) Cyber Security and System Security status.

p) Subcontractor activities and status and results of subcontractor reviews since last PMR.

q) Action Item review.

The contractor shall provide minutes IAW CDRL A018. These minutes shall cover significant questions, deviations, conclusions, and action items resulting from each program review meeting. The minutes will constitute the meeting report. Conclusions from discussions conducted during concurrent meetings (e.g., side meetings) shall be summarized in the main meeting and appropriate comments shall be incorporated into the official minutes.

Recommendations not accepted shall be recorded together with the reason for non-acceptance.

5.7 Bi-Weekly Status Update

The contractor shall conduct bi-weekly program management status update meetings during weeks that do not include other major engineering or management reviews, such as SETRs, IBRs, PMRs or as agreed upon between the contractor and Government. The information supporting the bi-weekly performance review meeting shall be available to the Government team at least four working hours prior to the meeting start time (i.e., if the meeting start time is 0800, the slides shall be available to the Government team by 1300 the previous working day.) The review is intended to be a summary of individual IPT meetings held during the reporting period, bringing forward only those items deemed significant enough to be discussed at the PM level.

The data shall be summarized by IPT and Organizational Category (i.e., each Control Account

Manager's (CAM's)/IPT Lead's area of responsibility shall be statused and reviewed discretely).

At a minimum, the following information should have been discussed at the IPT level and summarized for review by exception at the bi-weekly PM level meeting:

5 October 2015

pg. 18

a) Program Calendar. This shall include a 60 day look-ahead of significant upcoming events.

b) CDRL Look-ahead. CDRL deliveries and Government responses due within a six-week rolling wave of the weekly meeting shall be statused. Delinquent contractor deliveries and Government responses shall be reported.

c) Critical Path. This shall include briefing of any issues or concerns with tasks on the critical or driving paths.

i. Overall program critical path.

ii. At a minimum, the current driving paths to selected IMP Events and/or major milestones as determined by the Government Program Manager.

d) Contract Action Status.

e) Risks. The Contractor shall manage risk in accordance with the PMA-213 Risk, Issues, and Opportunity Management Plan. This shall include a status of Estimated Completion

Date (ECD)s on all risk mitigation steps overdue and due prior to the next Program Risk

Advisory Board (PRAB) and potential candidate risks. Updated projections of cost and schedule impacts should also be addressed.

f) Staffing Status. The staffing categories shall be consistent with the Integrated Program

Management Report (IPMR) Format 4. This data shall also include and identify consultants and contract support services. The data shall include current week and forward looking data for at least six weeks. The data shall be cumulative from contract award. The following categories shall be reported:

i. Planned weekly and actual hours by IPT and/or Organizational Category.

ii. Planned weekly and actual equivalent heads by IPT and/or Organizational

Category. The Manpower Conversion Factors shall be provided.

iii. Planned weekly and actual persons (head count by name) by IPT and/or

Organizational Category.

g) Staffing Vacancies and Forward-looking Staffing. This shall include current vacancies and future projected vacancies. This shall include open requisition status by IPT and

Organizational Category, the need date for these resources, the forecast date for acquiring these resources, and the functionality for which these resources will be assigned

h) Schedule Status for each IPT and Organizational Category. This shall include last week’s task activity by UID and Task Name, this week’s tasks by UID and Task Name, the next six weeks’ planned schedule tasks by UID and Task Name, and any issues, concerns and help needed. The contractor shall also include a graph and table summary of the planned starts versus actual starts and planned finishes versus actual finishes for each IPT and

Organizational Category. The data shall also be cumulative from contract award. In addition to the UID and Task Name, the following shall be included:

i. Baseline Start and /Finish.

ii. Forecast Start and Finish as reflected in the IMS.

iii. Slack and Float to next major milestone.

5 October 2015

pg. 19

iv. Critical and near-critical delinquent task identification.

v. Any associated comments related to the missed start and finish (impact to overall program).

i) Issues and Help Needed. This shall be listed for each CAM/IPT Lead.

j) Subcontractor Status, for subcontractors required to be fully integrated into the Prime’s

IMS (as delineated in the ‘Subcontract Cost/Schedule Management and Reporting’ section of this document): Each Subcontractor will be reported as per items f, g and, h above, with the exception that the subcontractor can be reported as a single whole entity vice broken out to individual IPTs and Organizational Categories.

k) Subcontractor status for Subcontractors not covered by item j above (i.e., not fully integrated into the IMS). This shall include an overall status of schedule and cost for all subcontractors responsible for delivery of critical components.

i. Subcontractors with Cost or Firm Fixed Price over $4M shall additionally provide the following as part of the status:

1. Staffing Status.

a. Status (see f above for required reporting information).

b. Planned and required skill level of position vs. actual skill level of filled position.

2. Critical tasks – status of critical tasks to meet the contractor’s schedule.

l) Action Items. This shall include status of all program action items.

Additional information shall be included as dictated by individual program requirements. The contractor shall provide minutes IAW CDRL A018. These minutes shall cover significant questions, deviations, conclusions, and action items resulting from each program review meeting. The minutes will constitute the meeting report. Conclusions from discussions conducted during concurrent meetings (e.g., side meetings) shall be summarized in the main meeting and appropriate comments shall be incorporated into the official minutes.

Recommendations not accepted shall be recorded together with the reason for non-acceptance.

The bi-weekly management status updates will be held via teleconferencing.

5.8 Contractor Integrated Performance Management

The IPMR shall be developed, maintained, updated/statused and reported on a monthly basis

IAW CDRLs A019 and A020 requirements. The contractor shall establish, maintain, and use in the performance of this contract, an integrated management system that is in compliance with the

Industry Guidelines for Earned Value Management Systems (EVMS) ANSI/EIA-748-B as determined by the Defense Contract Management Agency (DCMA). The application of these concepts shall provide for early indications of contract cost and schedule problems. Earned value assessments shall correlate with technical achievement.

5 October 2015

pg. 20

5.9 Integrated Baseline Review (IBR)

The purpose of the IBR is to achieve an understanding of the Performance Management Baseline

(PMB) and its relationship to the underlying EVM systems and processes that will operate during the contract execution and shall be documented IAW CDRL A019. The objectives are to gain insight into cost, schedule, technical, management processes and resource risk areas associated with the remaining effort, as well as develop confidence in the program’s operating plans. This will be accomplished by evaluating the PMB to ensure it captures the entire remaining technical scope of work, is consistent with contract schedule requirements, and has adequate resources assigned. The IBR Process will consist of these five events: 1) Joint Government/Prime

Management Systems Training, 2) Prime Management Systems Assessment, 3) Subcontractor

IBRs, 4) Schedule Risk Assessment (SRA) and 5) Total Contract IBR. These events are described below.

a) Joint Management Systems Training. Prior to the end of the first full accounting period, the contractor shall host and facilitate a joint Government/prime training session on the contractor's system description and procedures governing the implementation and operation of its management control systems. This shall include an overview of: EVMS;

Baseline Establishment; Planning, Scheduling and Budgeting; Earned Value Methods;

Performance Measurement Analysis; Baseline Maintenance; (EAC) Process; and

Material and Supplier Management/Subcontract Processes, including Inter-Divisional

Processes.

b) Prime Management Systems Assessment (MSA). Prior to the end of the third full accounting period, the contractor shall demonstrate the development of its PMB in accordance with the contractor's approved management systems processes. The contractor shall ensure that the baseline includes the entire contract technical scope of work at the prime level and is consistent with contract schedule requirements, adequate management processes are being employed, and has adequate resources assigned. The contractor shall demonstrate to the Government that effective earned value methods are used to accurately status contract cost, schedule, and technical performance. The contractor shall make MSA documentation available for Government review at least two weeks prior to the MSA in electronic, searchable format. The documentation shall include, but is not limited to, Organizational Charts, Responsibility Assignment Matrix, Control Account Plans (including Work Packages and Planning Packages), Work

Authorization Documents, Baseline Control Logs, Baseline Change Requests, Program unique directives and procedures, CLIN to WBS cross-reference matrix, proposed subcontractors and definitization schedule, and Data (WBS/IMS) dictionary.

c) Subcontractor IBRs. IBRs shall be conducted on subcontractors that report EVM data.

The subcontractor IBR shall be led by the prime contractor with Government participation. All subcontractor IBRs shall be within 90 days of Subcontract Authority to

Proceed.

5 October 2015

pg. 21

d) Schedule Risk Assessment. The Government will participate in the Probabilistic SRA in accordance with SOW Paragraph 5.13 “Schedule Risk Assessments”. The SRA shall be completed prior to the end of the fifth full month accounting period.

e) Total Contract IBR. This IBR shall be conducted no later than 180 calendar days after contract award. The Government will assess the contractor’s baseline, including all awarded subcontracted effort, to be used for performance measurement to ensure complete coverage of the statement of work, logical scheduling of work activities, adequate resourcing, and identification of inherent risks. Detailed planning, to the greater of, “six months beyond the IBR date” or “the next major milestone following the IBR” is required. IBR documentation and updated documentation shall be made available to the

Government at least four weeks prior to the review. The documentation includes but is not limited to that listed in paragraph (b) above. The Government will verify during the

IBR, and follow-on IBRs when warranted, that the contractor has established and maintains a reliable performance measurement baseline. The contractor will ensure that the baseline includes the entire contract technical scope of work consistent with contract schedule requirements, adequate management processes are being employed, and has adequate resources assigned. The contractor will assure the Government that effective earned value methods are used to accurately status contract cost, schedule, and technical performance.

Subsequent baseline reviews may be performed upon incorporation of major modifications, incorporation of an Over Target Budget/Over Target Schedule, review subsequent detail planning windows (often referred to as Rolling Wave or Block Planning) unavailable at the previous IBR event, in support of EAC site visits, or per Government program manager discretion.

5.10 Subcontract Cost/Schedule Management and Reporting

The contractor shall manage all of their subcontracts, including those that are Firm Fixed Price

(FFP), to include the timely award of the subcontract, integration of the subcontractor’s plans into appropriate schedules with sufficient detail, and monitoring the subcontractor’s staffing plans, to include the execution of those staffing plans to the required levels with the required skills.

5.10.1 Non FFP Subcontracts

IPMR requirements shall be applicable to non-FFP subcontracts at or exceeding $20M in then-year dollars and reported IAW CDRL A019.

5 October 2015

pg. 22

5.11 Contract Work Breakdown Structure (CWBS)

The contractor shall develop and maintain the CWBS and CWBS dictionary in accordance with

Military Standard-881 (MIL-STD-881 Current Version), which can be traced and reported to the work breakdown structure contained in CSDR Plan, Appendix C.

The Work Breakdown Structure (WBS) shall be the basis for further extension to control accounts and work packages during performance of the contract. The CWBS matrix (CWBS to functional responsibility) shall show expansion down to and including the control account level.

The contractor shall use the CWBS as the framework for reporting contract planning, budgeting, technical status, and schedule status.

During the performance of the contract, the contractor shall not change the approved CWBS or associated definition, or any of the reporting elements, without prior written approval from the

Government. As additional system definition is accomplished, the contractor shall update the

CWBS and CWBS dictionary and submit IAW CDRL A011.

5.12 Over Target Baseline (OTB)/Over Target Schedule (OTS)/Restructure

The contractor may conclude the baseline no longer represents a realistic plan in terms of budget and schedule execution. In the event the contractor determines an OTB, OTS, or Restructuring action is necessary, the contractor shall obtain Government approval prior to implementing an

OTB/OTS/Restructuring action. The request shall also include detailed implementation procedures as well as an implementation timeframe. The contractor will not implement the

OTB/OTS/Restructuring prior to receiving written approval from the Contracting Officer. The implementation procedures and IBR(s) shall be accomplished at no change to the incentive fee structure of CLIN 0003.

5.13 Schedule Risk Assessment (SRA)

Schedule Risk Assessments with Government: The Government will participate in the

Probabilistic Schedule Risk Assessments (SRA) as per the frequency delineated in the IPMR.

The annual SRA shall be scheduled to support the Government Estimate-at-Complete (EAC) process. In addition to the paths identified in the CDRL A019, the contractor shall also report optimistic, pessimistic, and most likely remaining durations and rationale for the values for each task and activity on any of the following paths: driving path to the next Major Milestone, and the next three near-driving paths to the next Major Milestone.

5.13.1 Program Schedule Assessment (PSA) and SRA Instructions

The AIR-4.2 PSA and SRA Instructions shall be used when conducting the SRA. A complete

SRA can be performed outside of routine scheduled occurrences, at the request of the PMA, particularly when the schedule is a significant issue for the PMA due to operational

5 October 2015

pg. 23 requirements, funding limitations, or when scheduling is considered a major risk element to the acquisition effort.

5.14 Annual Schedule Risk Assessments

The contractor shall participate in a Government conducted annual Program Risk/Opportunity

Assessments (PRA). The PRA is to provide program management with an understanding of the potential cost, technical, and schedule impacts associated with existing and emerging program risks, and opportunities to shorten schedule or reduce cost. Program risks and opportunities shall be reported by the Contractor in accordance with the guidance provided in the PMA213 Risk

Opportunity Management Plan. Locations for the PRA Events will be at the contractor’s facilities with the use of teleconference/video teleconference (VTC)/Government-provided online file sharing service. The duration of each PRA event is expected to be no more than one

(1) day.

6 Configuration Management / Data Management

6.1 Configuration Management (CM)

The contractor shall establish, maintain, and execute an integrated CM program IAW EIA-649-1 and the Government approved CM Plan submitted IAW CDRL A009. The CM Plan shall include CM Planning & Management, Configuration Identification, Configuration Change

Control, Configuration Status Accounting, and Configuration Verification & Audits. The contractor shall describe in the CM Plan how CM and DM are accomplished and how consistency between the product definition, the product configuration, and the CM Records is achieved and maintained through the applicable phase of the product life cycle.

6.2 Configuration Identification

The contractor shall establish, assign, and maintain hardware/software Configuration Item (CI) identifiers IAW the Government approved CM Plan IAW CDRL A009 and EIA-649-1. Once assigned, the contractor shall keep these identification numbers consistent and use them to provide management traceability.

The contractor shall identify hardware and software Configuration Items (CIs), assign unique identifiers to each, and establish a CI structure and hierarchy. The contractor shall deliver a

Baseline Description Document for the Post CDR Configuration IAW CDRL A010.

6.3 Configuration Change Control

The functional baseline is defined by the AN/SPN-50(V)1 System Specification and Government approved Interface Control Drawings (ICD). The functional baseline is controlled by the

Government. Changes to the SRD or the Government approved ICD cannot be made without

5 October 2015

pg. 24 approval of the PMA213 Decentralized Configuration Control Board through submittal of an

Engineering Change Proposal (ECP) IAW EIA-649-1 and CDRL A021.

6.4 Requests for Variances

The contractor shall obtain Government approval on any product that is, or will, be produced as defective or nonconforming to the requirements of the Functional Baseline, before delivery to the

Government IAW CDRL A022.

6.5 Configuration Status Accounting

The contractor shall capture and maintain the AN/SPN-50(V)1 configuration information to account for the configuration of the AN/SPN-50(V)1 throughout the duration of the contract. The contractor shall make the Configuration Status Accounting (CSA) system and AN/SPN-50(V)1 configuration information readily available to the Government.

6.6 Configuration Verification and Audit Plan

The Contractor shall develop and submit a AN/SPN-50(V)1 Configuration Audit Plan IAW

CDRL A023 in support of the Functional Configuration Audit (FCA).

The Contractor shall perform the FCA, with the Government as co-chair. The FCA shall verify that the hardware, firmware, and software CIs meet the documented performance requirements identified in the AN/SPN-50(V)1 System Specification.

6.7 Configuration Audit Summary Report (CASR)

The Contractor shall deliver a Configuration Audit Summary Report IAW CDRL A024.

6.8 Contractor Internal Data Requirements (Data Accession List)

The Contractor shall make available…