RFP N00019-19-R-0040.pdf

N0001919R0040

Section A - Solicitation/Contract Form

SECTION A

GOVERNMENT POINT OF CONTACT:

Contract Specialist Holly Alemar Email: holly.alemar@navy.mil

Procuring Contracting Officer Christin J. Simpson Email: christin.simpson@navy.mil

PREAMBLE:

NOTE 1: The Government expects to award six (6) Small Businesses and six (6) Large Businesses Indefinite Delivery, Indefinite Quantity (IDIQ) Contracts under a Multiple Award Contract (MAC) as a result of this solicitation to support the PMA-281, Strike Planning and Execution Systems portfolio.

NOTE 2: The ceiling value of $497,500,000.00 set forth herein represents the maximum total value that will be awarded under this MAC. The $497,500,000.00 maximum total value is the cumulative ceiling amount that will be the ceiling on each awardee’s IDIQ Contract. The pricing contained within Section B is to establish the ceiling per Contract Line Item Number (CLIN) at the basic MAC level.

NOTE 3: The ordering period of the PMA-281, Strike Planning and Execution Systems MAC shall commence at date of award of contract and shall continue for a period of 60 months.

NOTE 4: The guaranteed minimum dollar value for each awardee is $1,000.00. The Government will award a Delivery Order (DO) for $1,000 for the submittal of the Operations Security (OPSEC) Plan (CLIN 0013), which will satisfy the minimum guarantee price, to each Offeror selected for an IDIQ award under the PMA-281 MAC.

NOTE 5: Unless otherwise specified in a specific order issued under this IDIQ MAC, the terms and conditions of this contract shall apply to each delivery order issued under this IDIQ MAC. The CLIN types utilized in this contract are Cost-Plus-Fixed-Fee (CPFF), Firm-Fixed-Price (FFP), and COST.

With regard to CPFF CLINs, the maximum fee to be proposed is 10%, although offerors may propose less than 10%. Each order thereafter will be capped at the basic MAC fee or less, if proposed. Subcontractor fee is capped at the same rate as the prime. A proposed fee that is higher than the maximum fee rate shall render the Contractor’s proposal unacceptable.

Subcontractor maximum pass-through rate is 10%. Pass-through Rate is defined as the cumulative amount of the two elements listed below divided by the price paid to the subcontractor or the vendor:

1. Any and all indirect costs including, but not limited to, program management, subcontract management, invoice processing, quality assurance, overhead, material handling charges, General Administrative (G&A), burdens and mark-ups; and

2. Any and all prime contract profit or fee.

The Prime Contractor shall not apply any additional fees or burdens on the elements of pass-through. Other than the elements of pass-through, no addition costs, charges, indirect rates or fees shall be proposed or applied to subcontract costs.

mailto:christin.simpson@navy.mil

For purposes of the maximum pass-through, any effort provided by a division, subsidiary or any other entity of the prime Contractor shall not be considered subcontracted effort and all fee/profit must be provided at the prime level subject to the limitations specified in this contract.

Other Direct Cost (ODCs): Unless otherwise authorized at the order level, no fee is allowed on ODCs, which includes material, equipment and travel. Indirect cost elements such as G&A and material handling may be applied but shall not include fee.

NOTE 6: Performance of orders issued hereunder shall be in accordance with individual delivery orders.

NOTE 7: It is anticipated that there may be requirements for access to classified information by Contractors under the IDIQ MAC. The highest security levels that may be required by the Contractor to perform on individual delivery orders under this contract are up to a TOP SECRET (TS) / SENSITIVE COMPARTMENTED INFORMATION (SCI) with a SECRET safeguarding capability. These security requirements will be a condition for basic contract award.

All classified delivery orders will require a facility security clearance issued by the Defense Security Service (DSS) at delivery order award. Contractor personnel shall be required to have a security clearance at the level required for each specific delivery order. The security classification and guidance of classified delivery orders will be specified in the Contract Security Classification Specification DD Form 254, to be provided when required at the delivery order level.

Unclassified delivery orders do not require a facility clearance issued by DSS, or a DD Form 254. Any planned utilization of non-U.S. Citizens for performance under the delivery order requires identification of each such individual by name and country of citizenship in the delivery order proposal.

Foreign Nationals shall not be allowed access to Classified or Critical Program Information unless approved on a case-by-case basis by DSS.

NOTE 8: The Contractor will not be permitted access to classified information until a final DD254 is incorporated as an attachment at the Delivery Order level.

Section B - Supplies or Services and Prices

ITEM NO SUPPLIES/SERVICES MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

0001 1 Lot

SOFTWARE AND HARDWARE DEVELOPMENT RDT&E

CPFF

IN ACCORDANCE WITH (IAW) SECTION C STATEMENT OF WORK

(SOW)

FOB: Destination

MAX COST

FIXED FEE

TOTAL MAX COST + FEE

UNIT UNIT PRICE MAX AMOUNT

0002 1 Lot

SOFTWARE AND HARDWARE PROCUREMENT OP,N

CPFF

IN ACCORDANCE WITH (IAW) SECTION C STATEMENT OF WORK

UNIT UNIT PRICE MAX AMOUNT

0003 1 Lot

SOFTWARE AND HARDWARE SUSTAINMENT O&M,N

CPFF

IN ACCORDANCE WITH (IAW) SECTION C STATEMENT OF WORK

UNIT UNIT PRICE MAX AMOUNT

0004 1 Lot

SOFTWARE AND HARDWARE FMS

CPFF

UNIT UNIT PRICE MAX AMOUNT

0005 1 Lot

SOFTWARE AND HARDWARE DEVELOPMENT RDT&E

FFP

IN ACCORDANCE WITH (IAW) SECTION C STATEMENT OF WORK

MAX

NET AMT

UNIT UNIT PRICE MAX AMOUNT

0006 1 Lot

SOFTWARE AND HARDWARE PROCUREMENT OP,N

FFP

IN ACCORDANCE WITH (IAW) SECTION C STATEMENT OF WORK

UNIT UNIT PRICE MAX AMOUNT

0007 1 Lot

SOFTWARE AND HARDWARE SUSTAINMENT O&M,N

FFP

IN ACCORDANCE WITH (IAW) SECTION C STATEMENT OF WORK

UNIT UNIT PRICE MAX AMOUNT

0008 1 Lot

SOFTWARE AND HARDWARE FMS

FFP

IN ACCORDANCE WITH (IAW) SECTION C STATEMENT OF WORK

UNIT UNIT PRICE MAX AMOUNT

0009 1 Lot

OTHER DIRECT COSTS (ODC) RDT&E

COST

ODCS MAY INCLUDE MATERIAL, EQUIPMENT, AND TRAVEL

UNIT UNIT PRICE MAX AMOUNT

0010 1 Lot

OTHER DIRECT COSTS (ODC) OP,N

UNIT UNIT PRICE MAX AMOUNT

0011 1 Lot

OTHER DIRECT COSTS (ODC) O&M,N

UNIT UNIT PRICE MAX AMOUNT

0012 1 Lot

OTHER DIRECT COSTS (ODC) FMS

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

0013 1 Each

OPERATIONS SECURITY (OPSEC) PLAN

FFP

MINIMUM GUARANTEE

IN ACCORDANCE WITH CONTRACT DATA REQUIREMENT LIST (CDRL)

A01H

UNIT UNIT PRICE MAX AMOUNT

0014 1 Each

MANAGEMENT PLAN

FFP

IN ACCORDANCE WITH CONTRACT DATA REQUIREMENT LIST

(CDRL) A002

UNIT UNIT PRICE MAX AMOUNT

0015 1 Each

SYSTEMS ENGINEERING MANAGEMENT PLAN

FFP

IN ACCORDANCE WITH CONTRACT DATA REQUIREMENT LIST

(CDRL) A00B

UNIT UNIT PRICE MAX AMOUNT

0016 1 Each

SOFTWARE DEVELOPMENT PLAN

FFP

IN ACCORDANCE WITH CONTRACT DATA REQUIREMENT LIST

(CDRL) A00T

UNIT UNIT PRICE MAX AMOUNT

0017 1 Each

CONTRACTOR’S RISK MANAGEMENT PLAN

FFP

IN ACCORDANCE WITH CONTRACT DATA REQUIREMENT LIST

(CDRL) A00L

UNIT UNIT PRICE MAX AMOUNT

0018 1 Lot

DATA FOR ITEMS 0001 - 0017

FFP

TECHNICAL, FINANCIAL AND ADMINISTRATIVE DATA

CLAUSES INCORPORATED BY REFERENCE

5252.215-9535 PRICE AT LINE ITEM LEVEL OCT 2005

Section C - Descriptions and Specifications

SECTION C

Item 0001, 0002, 0003 and 0004 - As a Cost-Plus-Fixed-Fee (CPFF) Completion effort for supplies, the Contractor shall provide all efforts necessary to provide software and hardware products in accordance with the Statement of Work in Section C of this contract and the applicable Delivery Order(s).

Item 0005, 0006, 0007 and 0008 - As a Firm-Fixed-Price (FFP) effort for supplies, the Contractor shall provide all efforts necessary to provide software and hardware products in accordance with the Statement of Work in Section C of this contract and the applicable Delivery Order(s).

Item 0009, 0010, 0011 and 0012 - The contractor shall provide Other Direct Costs (ODC) which includes material/equipment and travel in accordance with the Statement of Work in Section C of this contract and the applicable Delivery Order(s).

Item 0013 – The Contractor shall provide an Operations Security (OPSEC) Plan in accordance with the Data Item Description (DID) Number: DI-MGMT-80934C, see Attachment 3 in Section J of this contract.

Item 0014 – The Contractor shall provide a Management Plan in accordance with the Data Item Description (DID) Number: DI-MGMT-80004A, see Attachment 4 in Section J of this contract.

Item 0015 – The Contractor shall provide a Systems Engineering Management Plan in accordance with the Data Item Description (DID) Number: DI-SESS-81785A, see Attachment 5 in Section J of this contract.

Item 0016 – The Contractor shall provide a Software Development Plan in accordance with the Data Item Description (DID) Number: DI-IPSC-81427B, see Attachment 6 in Section J of this contract.

Item 0017 – The Contractor shall provide a Risk Management Plan in accordance with the Data Item Description (DID) Number: DI-MGMT-81808, see Attachment 7 in Section J of this contract.

Item 0018 – The technical, financial and administrative data to be furnished hereunder shall be provided in accordance with Exhibit A (Contract Data Requirements List (CDRL), DD Form 1423) located in Section J of this contact.

STATEMENT OF WORK (SOW)

PMA-281 Software/Hardware

Indefinite-Delivery / Indefinite-Quantity Multiple-Award Contract

(IDIQ/MAC)

Statement of Work (SOW)

Prepared by

PMA-281

7 January 2020

DISTRIBUTION STATEMENT D. Distribution authorized to the Department of Defense and U.S. DoD contractors only (Administrative or Operational Use) (3 August 2019). Other requests shall be referred to Program Manager, Strike Planning and Execution Systems (PMA-281), 47123 Buse Road, RADM William A. Moffett Building, Room 251, Patuxent River MD 20670

DESTRUCTION STATEMENT: Destroy by any method that will prevent disclosure of contents or reconstruction of this document.

Contents

1.0 INTRODUCTION 17

1.1 PROGRAM OBJECTIVES 17

1.1.1 DELIVERY ORDER SPECIFIC OBJECTIVES – RESERVED 17

1.2 SCOPE 17

1.2.1 DELIVERY ORDER SPECIFIC SCOPE – RESERVED 18

2.0 APPLICABLE DOCUMENTS 18

2.1 REFERENCE DOCUMENTS 18

3.0 REQUIREMENTS 20

3.1 PROJECT MANAGEMENT 20

3.1.1 PROJECT MANAGEMENT 20

3.1.2 MANAGEMENT CONTROL SYSTEMS 21

3.1.3 CONTRACT WORK BREAKDOWN STRUCTURE 22

3.1.3.1 DELIVERY ORDER SPECIFIC CONTRACT WORK BREAKDOWN STRUCTURE – RESERVED 22

3.1.4 EARNED VALUE MANAGEMENT (EVM) 22

3.1.4.1 DELIVERY ORDER SPECIFIC EVM – RESERVED 23

3.1.5 DATA MANAGEMENT AND THE INTEGRATED DATA ENVIRONMENT 23

3.1.5.1 DELIVERY ORDER SPECIFIC DATA MANAGEMENT AND THE INTEGRATED DATA ENVIRONMENT –

RESERVED 23

3.1.6 INTEGRATED MASTER SCHEDULE 23

3.1.6.1 DELIVERY ORDER SPECIFIC INTEGRATED MASTER SCHEDULE – RESERVED 24

3.1.7 INTEGRATED PRODUCT TEAMS 25

3.1.7.1 DELIVERY ORDER SPECIFIC INTEGRATED PRODUCT TEAMS – RESERVED 25

3.1.8 PROGRAM MEETINGS AND REVIEWS 25

3.1.8.1 PROGRAM MANAGEMENT REVIEWS 25

3.1.8.1.1 POST-AWARD CONFERENCE 25

3.1.8.1.2 PROGRAM MANAGEMENT REVIEWS (PMRS) 26

3.1.8.1.3 DELIVERY ORDER SPECIFIC PROGRAM MANAGEMENT REVIEW REQUIREMENT - RESERVED 26

3.1.8.2 PROGRAM TECHNICAL REVIEWS 26

3.1.8.2.1 PROGRAM SYSTEMS ENGINEERING TECHNICAL REVIEWS 26

3.1.8.2.3 DELIVERY ORDER SPECIFIC PROGRAM TECHNICAL INTERCHANGE MEETINGS – RESERVED 28

3.1.8.3.1 DELIVERY ORDER SPECIFIC GOVERNMENT-LED TECHNICAL, PROGRAMMATIC, AND ENGINEERING

TECHNICAL INTERCHANGE MEETINGS – RESERVED 28

3.1.9 GOVERNMENT FURNISHED PROPERTY/INFORMATION (GFP/I) 28

3.1.9.1 DELIVERY ORDER SPECIFIC GOVERNMENT FURNISHED PROPERTY/INFORMATION – RESERVED 29

3.2 SYSTEM ENGINEERING 29

3.2.1 GENERAL SYSTEMS ENGINEERING REQUIREMENTS 29

3.2.1.1 DELIVERY ORDER SPECIFIC GENERAL SYSTEMS ENGINEERING REQUIREMENTS – RESERVED 29

3.2.2 OPEN ARCHITECTURE (OA) 29

3.2.2.1 DELIVERY ORDER SPECIFIC OPEN ARCHITECTURE – RESERVED 30

3.2.3 REQUIREMENTS TRACEABILITY 30

3.2.3.1 DELIVERY ORDER SPECIFIC REQUIREMENTS TRACEABILITY – RESERVED 31

3.2.4 MODEL BASED SYSTEMS ENGINEERING 31

3.2.4.2 DELIVERY ORDER SPECIFIC SOFTWARE ARCHITECTURE – RESERVED 33

3.2.5 TECHNICAL PERFORMANCE MEASURES (TPMS) 33

3.2.5.2 DELIVERY ORDER SPECIFIC SOFTWARE TECHNICAL PERFORMANCE MEASURES – RESERVED 34

3.2.5.4 DELIVERY ORDER SPECIFIC HARDWARE TECHNICAL PERFORMANCE MEASURES – RESERVED 34

3.3 HUMAN SYSTEMS ENGINEERING & INTEGRATION 34

3.3.1 DELIVERY ORDER SPECIFIC HSE&I– RESERVED 35

3.4 RISK MANAGEMENT 36

3.4.1 DELIVERY ORDER SPECIFIC RISK MANAGEMENT – RESERVED 36

3.5 SYSTEM SAFETY 36

3.5.1 DELIVERY ORDER SPECIFIC SYSTEM SAFETY – RESERVED 37

3.6 CERTIFICATIONS 37

3.6.1 AIRWORTHINESS 37

3.6.1.1 DELIVERY ORDER SPECIFIC AIRWORTHINESS – RESERVED 37

3.6.2 SPECTRUM CERTIFICATION 38

3.6.2.1 DELIVERY ORDER SPECIFIC SPECTRUM CERTIFICATION – RESERVED 38

3.6.3 JOINT INTEROPERABILITY 38

3.6.3.1 DELIVERY ORDER SPECIFIC JOINT INTEROPERABILITY – RESERVED 38

3.7 CONFIGURATION MANAGEMENT 38

3.7.1 CONFIGURATION IDENTIFICATION 39

3.7.1.1 DELIVERY ORDER SPECIFIC CONFIGURATION IDENTIFICATION – RESERVED 40

3.7.2 CONFIGURATION CONTROL 40

3.7.2.1 DELIVERY ORDER SPECIFIC CONFIGURATION CONTROL – RESERVED 40

3.7.3 SOFTWARE BUILD CONFIGURATION CONTROL 40

3.7.3.1 DELIVERY ORDER SPECIFIC SOFTWARE BUILD CONFIGURATION CONTROL – RESERVED 41

3.7.4 CONFIGURATION STATUS ACCOUNTING (CSA) 41

3.7.4.1 DELIVERY ORDER SPECIFIC CONFIGURATION STATUS ACCOUNTING – RESERVED 42

3.7.5 CONFIGURATION AUDITS 42

3.7.5.1 DELIVERY ORDER SPECIFIC CONFIGURATION AUDITS – RESERVED 42

3.7.6 ENGINEERING CHANGE PROPOSALS 42

3.7.6.1 DELIVERY ORDER SPECIFIC ENGINEERING CHANGE PROPOSALS – RESERVED 42

3.8 SOFTWARE DESIGN, DEVELOPMENT, INTEGRATION, TEST, DELIVERY, PROCUREMENT, AND SUSTAINMENT

3.8.1 SOFTWARE DOCUMENTATION 43

3.8.1.1 DELIVERY ORDER SPECIFIC SOFTWARE DOCUMENTATION – RESERVED 44

3.8.2 SOFTWARE DEVELOPMENT 44

3.8.2.1 DELIVERY ORDER SPECIFIC SOFTWARE DEVELOPMENT – RESERVED 45

3.8.3 SOFTWARE TROUBLE REPORTING 46

3.8.3.1 DELIVERY ORDER SPECIFIC SOFTWARE TROUBLE REPORTING – RESERVED 46

3.8.4 SYSTEM INTEGRATION LABORATORY (SIL) 46

3.8.4.1 DELIVERY ORDER SPECIFIC SYSTEM INTEGRATION LABORATORY – RESERVED 47

3.8.5 SOFTWARE DEVELOPMENT KIT/ SOFTWARE DEVELOPMENT GUIDE 47

3.8.5.1 DELIVERY ORDER SPECIFIC SOFTWARE DEVELOPMENT KIT / SOFTWARE DEVELOPMENT GUIDE –

RESERVED 48

3.8.6 OPEN SOURCE SOFTWARE (OSS) PRODUCTS 48

3.8.6.1 DELIVERY ORDER SPECIFIC OPEN SOURCE SOFTWARE PRODUCT REQUIREMENTS – RESERVED 49

3.8.7 SOFTWARE STATIC AND DYNAMIC SOFTWARE CODE ANALYSIS 49

3.8.7.1 DELIVERY ORDER SPECIFIC STATIC AND DYNAMIC SOFTWARE CODE ANALYSIS – RESERVED 50

3.8.8 AUTOMATED UNIT-LEVEL TESTING 50

3.8.8.1 DELIVERY ORDER SPECIFIC AUTOMATED UNIT-LEVEL TESTING REQUIREMENTS – RESERVED 50

3.8.9 SOFTWARE FORMAL QUALIFICATION TESTING 50

3.8.9.1 DELIVERY ORDER SPECIFIC FORMAL QUALIFICATION TESTING REQUIREMENTS – RESERVED 51

3.8.10 SOFTWARE MAINTENANCE AND CORRECTION OF DEFECTS 52

3.8.10.1 DELIVERY ORDER SPECIFIC SOFTWARE MAINTENANCE AND CORRECTION OF DEFECTS – RESERVED

3.8.11 SYSTEM INTEGRATION 52

3.9 STUDIES AND PROTOTYPES 53

3.9.1 DELIVERY ORDER SPECIFIC STUDIES AND PROTOTYPES – RESERVED 53

3.10 HARDWARE DESIGN, DEVELOPMENT, INTEGRATION, TEST, DELIVERY, PROCUREMENT, AND

SUSTAINMENT 53

3.10.1 HARDWARE DOCUMENTATION 53

3.10.1.1 DELIVERY ORDER SPECIFIC HARDWARE DOCUMENTATION - RESERVED 54

3.10.2 HARDWARE DEVELOPMENT 54

3.10.2.1 DELIVERY ORDER SPECIFIC HARDWARE DEVELOPMENT – RESERVED 55

3.10.3 HARDWARE PROCUREMENT 55

3.10.3.1 DELIVERY ORDER SPECIFIC HARDWARE PROCUREMENT – RESERVED 55

3.10.4 HARDWARE INSTALLATION 55

3.10.4.1 DELIVERY ORDER SPECIFIC HARDWARE INSTALLATION – RESERVED 55

3.10.5 HARDWARE MAINTENANCE AND CORRECTION OF DEFECTS 55

3.10.5.1 DELIVERY ORDER SPECIFIC HARDWARE MAINTENANCE AND CORRECTION OF DEFECTS – RESERVED

3.11 SECURITY 56

3.11.1 DELIVERY ORDER SPECIFIC SECURITY – RESERVED 59

3.11.2 FACILITY CLEARANCE, PERSONNEL SECURITY CLEARANCE AND BACKGROUND INVESTIGATIONS 59

3.11.2.1 DELIVERY ORDER SPECIFIC FACILITY CLEARANCE, PERSONNEL SECURITY CLEARANCE AND

BACKGROUND INVESTIGATIONS – RESERVED 59

3.11.3 CYBERSECURITY 59

3.11.3.1 DELIVERY ORDER SPECIFIC CYBER SECURITY – RESERVED 61

3.12 PROGRAM PROTECTION 61

3.12.1 DELIVERY ORDER SPECIFIC PROGRAM PROTECTION – RESERVED 61

3.13 ANTI-TAMPER 61

3.13.1 DELIVERY ORDER SPECIFIC ANTI-TAMPER – RESERVED 63

3.14 TEST AND EVALUATION 64

3.14.1 TEST PLANNING, EXECUTION, AND REPORTING 64

3.14.1.1 DELIVERY ORDER SPECIFIC TEST PLANNING, EXECUTION, AND REPORTING REQUIREMENTS –

RESERVED 65

3.14.2 AUTOMATED TEST 65

3.14.2.1 DELIVERY ORDER SPECIFIC AUTOMATED TEST REQUIREMENTS – RESERVED 65

3.14.3 ACCEPTANCE TESTING 66

3.14.3.1 DELIVERY ORDER SPECIFIC ACCEPTANCE TESTING – RESERVED 66

3.14.4 T & E WIPT 66

3.14.4.1 DELIVERY ORDER SPECIFIC T & E WIPT – RESERVED 66

3.15 INTEGRATED LOGISTICS SUPPORT 66

3.15.1 LIFE CYCLE LOGISTICS 66

3.15.1.1 DELIVERY ORDER SPECIFIC LIFE CYCLE LOGISTICS REQUIREMENTS – RESERVED 67

3.15.2 INTEGRATED LOGISTICS SUPPORT DOCUMENTATION 67

3.15.2.1 DELIVERY ORDER SPECIFIC INTEGRATED LOGISTICS SUPPORT DOCUMENTATION – RESERVED 68

3.15.3 PRODUCT SUPPORT STRATEGY 68

3.15.3.1 DELIVERY ORDER SPECIFIC PRODUCT SUPPORT STRATEGY – RESERVED 68

3.15.4 TRAINING 68

3.15.4.1 DELIVERY ORDER SPECIFIC TRAINING – RESERVED 69

3.15.5 HELP DESK 69

3.15.5.1 DELIVERY ORDER SPECIFIC HELP DESK – RESERVED 70

3.15.6 ON-SITE TECHNICAL SUPPORT 70

3.15.6.1 DELIVERY ORDER SPECIFIC ON-SITE TECHNICAL SUPPORT – RESERVED 70

3.15.7 INVENTORY MANAGEMENT 70

3.15.7.1 DELIVERY ORDER SPECIFIC INVENTORY MANAGEMENT SUPPORT – RESERVED 71

4.0 APPENDICES 71

4.1 CONTRACT DATA REQUIREMENTS LIST (CDRL) 71

4.2 ACRONYM LISTING 75

4.2.1 DELIVERY ORDER SPECIFIC ACRONYM LISTING - RESERVED 78

1.0 Introduction

The purpose of this Statement of Work (SOW) is to describe the work to be performed on the PMA-281 Software/Hardware (SW/HW) Indefinite-Delivery / Indefinite-Quantity Multiple-Award Contract (IDIQ/MAC). This SOW describes the work to be performed on the IDIQ/MAC in general terms and serves as a guide for SOWs developed for subsequent delivery orders.

The Contractor shall only perform to the boxes marked with a “☒” that will be the requirements set forth under the individual delivery orders.

1.1 Program Objectives

The overall objective of this Contract is to deliver capabilities to the joint service warfighters. Under the IDIQ/MAC, the Contractors shall provide capabilities necessary to meet both domestic and Foreign Military Sales (FMS) user requirements.

1.1.1 Delivery Order Specific Objectives – Reserved

☐ Reserved for delivery order specific objectives.

1.2 Scope

The scope of the PMA-281 SW/HW IDIQ/MAC contract includes development, integration, test and evaluation, deployment/delivery, modifications, and operations/sustainment of hardware and software products supporting both PMA-281 domestic and FMS programs. These efforts include, but are not limited to, the following:

☐ Development and evolution of Naval Mission Planning Systems (NavMPS) capabilities and components;

☐ Development and evolution of International Program (IP)/FMS capabilities and components;

☐ Development and evolution of Common Control Systems (CCS) capabilities and components;

☐ Development and evolution of Theater Mission Planning Center (TMPC) capabilities and components;

☐ Development and evolution of Washington Planning Center (WPC) capabilities and components;

☐ Development and evolution of Airwing Ship Integration (AWSI) capabilities and components;

☐ Upgrade and maintenance of PMA-281-provided products;

☐ Design/support/upgrade of software/hardware solutions for fielded systems using Commercial-Off-The-Shelf/Government-Off-The-Shelf products; and

☐ Conduct studies, analyses, and/or prototyping efforts.

1.2.1 Delivery Order Specific Scope – Reserved

☐ Reserved for delivery order specific scope.

2.0 Applicable Documents

2.1 Reference Documents

☐ The capabilities shall be delivered in accordance with the documents and references in Table 2-1 to include updates and revisions as specified in individual delivery orders.

Table 2-1 Reference Documents

--- --- Document Title Number / Revision

Date

☐ A MIL-STD-881D D 9 April 2018 ☐ B NAVAIRINST 4355.19 Systems Engineering

Technical Review Process E 6 February 2015

☐ C ANSI/EIA-748, Earned Value Management Systems (EVMS)

☐ D PMA-281 Software Metrics Plan ver 2.2 12 March 2019 ☐ E Reserved --- --- ☐ F MIL-STD-1472 Version G 11 January 2012 ☐ G PMA-281 Risk, Issue, and Opportunity

Management Plan Version 1.0 30 Jul 2018

☐ H MIL-STD-882E Revision E 11 May 2014 ☐ I NAVAIRINST 13034.1, Airworthiness and

Cybersecurity Safety Policies for Air Vehicles and Aircraft Systems

Rev F 30 June 2016

☐ J MIL-HDBK-516, Airworthiness Certification Criteria

Rev C 12 December 2014

☐ K PMA 281 Configuration Management Plan Draft, ver 0.3 27 Sep 2019 ☐ L IEEE/EIA 12207 Systems and Software

Engineering —Software Life Cycle Processes

Latest version

☐ M MIL-STD-3034A --- 29 April 2014 ☐ N MIL-STD-167-1A --- 2 November 2005 ☐ O MIL-STD-461G --- 11 December 2015 ☐ P MIL-DTL-901E --- 20 June 2017 ☐ Q DoDI 8500.01, Cybersecurity --- 14 March 2014 ☐ R DoDD 8140.01, Cyberspace Workforce

Management --- 11 August 2015

☐ S DoD 5200.01 Vol 3 Chg 2, DoD Information Security Program: Protection of Classified Information

--- 19 March 2013

☐ T DoDI 8510.01 Risk Management Framework (RMF) for DoD Information Technology (IT)

Change 2 28 July 2017

☐ U DoDI 8582.01 Chg 1, Security of Unclassified DoD Information on Non-DoD Information Systems

--- 27 October 2017

☐ V SECNAVINST 5239.3C Department of the Navy Cybersecurity Policy

--- 2 May 2016

☐ W SECNAVINST 5239.20 Department of the Navy Cyberspace Information Technology and Cybersecurity Workforce Management and Qualification

--- 10 Feb 2016

☐ X CNSSI No. 1253, Committee National Security Systems Instruction, Security Categorization and Control Selection for National Security Systems

Rev 4 27 Mar 2014

☐ Y CNSSP No. 11, National Policy Governing the Acquisition of Information Assurance (IA) and IA-Enabled Information Technology Products

--- 10 June 2013

☐ Z MIL-HDBK-61A(SE) --- 7 February 2001 ☐ AA SAE EIA-649-1 --- 20 November 2014 ☐ AB DoD 5220.22-M, National Industrial Security

Program Operating Manual Change 2 18 May 2016

☐ AC DOD Manual 5200.01, Volumes 1 – 4, DoD Information Security Program

☐ AD DODI 5200.39, Critical Program Information (CPI) Identification and Protection

Change 2 15 October 2018

☐ AE MIL-HDBK-1785 --- 1 August 1995 ☐ AF NAVAIR Airworthiness and Cybersafe

Process Manual M-13034.1 --- 13 April 2016

☐ AG NAVAIRINST 13034.1F Airworthiness and CyberSecurity Safety Policies for Air Vehicles and Aircraft Systems

--- 30 June 2016

☐ AH NAVAIR Instruction 3960.2D, Acquisition Test and Evaluation

--- 30 May 2012

☐ AI NAVAIR Instruction 3960.4C Change 1 9 April 2013 ☐ AJ NAVAIRINST 3905.1A, Test Reporting

Policy for Air Vehicles, Air Vehicle Weapons and Air Vehicle Installed Systems Test

--- 17 January 2019

☐ AK NAVAIR M-3905.1, Test Reporting Manual Version 3 22 May 2017

☐ AL MIL-HDBK-2155 --- 11 Dec 1995

☐ AM Department of Defense Instruction 5000.02, Operation of the Defense Acquisition System

Change 3 10 August 2017

☐ AN www.dau.mil/policy/policydocuments/the126 6ulss.doc

Table 2-2 Delivery Order Specific References

3.0 Requirements

3.1 Project Management

3.1.1 Project Management

☐ The Contractor shall manage and report on all aspects of the contract including, but not limited to, program planning and control, cost and scheduling, subcontractor control, financial management, data management, systems engineering management, risk management, and configuration management.

☐ The Contractor shall establish a management plan that describes the Contractor’s organizational structure, program management methodology, personnel, security, management procedures/policies and reporting requirements for the conduct of contractually-imposed tasks, projects, or programs.

☐ The Contractor’s management plan shall document subcontractor functions, duties, and responsibilities and describe how the Contractor shall manage and control all work executed by subcontractor(s).

☐ The Contractor shall integrate subcontractor plans into execution schedules, ensure subcontractor staffing meets execution needs and ensure subcontractor execution performance meets contractual requirements.

☐ AO MIL-STD-40051, Preparation of Digital Technical Information for Interactive Electronic Technical Manuals (IETMs)

--- 15 December 2015

☐ AP NIST Special Publication 800-171, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations (https://csrc.nist.gov/publications/detail/sp/80 0-171/rev-1/final)

Rev 1 7 June 2018

☐ AQ Instructions for Submitting Media (www.acq.osd.mil/dpap/dars/pgi/docs/Instruc tions_for_Submitting_Media.docx)

--- --- Document Title Number / Revision

Date

☐ XX Reserved for references specific to individual delivery orders

☐ The Contractor’s status report shall include technical achievements, progress against plans, cost performance, resource commitments and expenditures, risk identification and tracking, problem identification, and corrective action plans.

☐ The contractor shall develop and deliver a status report, Contract Data Requirements

List (CDRL) A001 – Status Report.

☐ The Contractor shall develop, deliver and maintain a Management Plan, CDRL A002

– Management Plan.

3.1.1.1 Delivery Order Specific Management Control System Requirements – Reserved

☐ Reserved for delivery order specific Program Management tasking.

3.1.2 Management Control Systems

☐ The Contractor shall maintain an integrated Management Control System (MCS) that measures program progress and ensures fulfillment of program requirements.

☐ The Contractor shall prepare and deliver cost reports.

☐ The Contractor’s MCS shall track manpower as well as any hardware/software costs.

☐ The Contractor’s MCS shall update and forecast contract funds requirements, plan funding changes, and develop funding requirements and budget estimates in support of future, contracted work.

☐ The Contractor’s MCS data shall be derived from the Earned Value Management

System (EVMS) (when applicable), cost status/assessment, performance measurements, and any other execution data required to manage the effort.

☐ The Contractor’s MCS shall include all prime contractor as well as subcontractor data required to manage the effort.

☐ The Contractor shall report ALL Contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract.

☐ The Contractor shall prepare and deliver a contract funds status report, CDRL A007 -

Contract Funds Status Report.

☐ The Contractor shall prepare and deliver a cost data summary report, CDRL A008 - Cost Data Summary Report

3.1.2.1 Delivery Order Specific Management Control System Requirements –

☐ Reserved for delivery order specific Management Control System tasking.

3.1.3 Contract Work Breakdown Structure

☐ The Contractor shall develop, implement, and maintain a Contract Work Breakdown

Structure (CWBS) in accordance MIL-STD-881.

☐ The CWBS shall extend to the lowest appropriate level required to provide adequate management, oversight, and performance measurement of the work.

☐ The CWBS shall include all work performed by subcontractor(s).

☐ The CWBS shall be the basis for tracking, controlling, measuring and reporting all contracted cost and schedule performance.

☐ The Contractor shall deliver and maintain a CWBS, CDRL A003 Contract Work

Breakdown Structure.

3.1.3.1 Delivery Order Specific Contract Work Breakdown Structure – Reserved

☐ Reserved for delivery order specific Contract Work Breakdown Structure tasking.

3.1.4 Earned Value Management (EVM)

☐ The Contractor shall implement an Earned Value Management System (EVMS) in accordance with ANSI/EIA-748.

☐ The Contractor shall have its EVMS system certified by Defense Contract management Agency for contract values meeting or exceeding $50M.

☐ The Contractor shall require subcontractors to submit EVM data for contracts types other than firm fixed price that exceed $20M

☐ The Contractor shall prepare and deliver an Integrated Program Management Report, CDRL A004 Integrated Program Management Report (IPMR) Version 1.

3.1.4.1 Delivery Order Specific EVM – Reserved

☐ Reserved for delivery order specific EVM tasking.

3.1.5 Data Management and the Integrated Data Environment

☐ The Contractor shall implement and maintain an Integrated Data Environment (IDE) for exchange of technical and programmatic data with the Government.

☐ The Contractor shall provide for up to 20 Government personnel (including knowledge-based support contractors) to access the IDE.

☐ The Contractor shall ensure that the IDE contains all program development information, including intermediate and final artifacts, both in-work and completed, developed and used as a part of the development activity, to include, at a minimum, all design data items, review materials (briefings and reports), technical reports and briefings, all measures and metric reports, peer review reports, program schedules, architectural System Models, and all Software Development Folders (SDF) (including all requirements, design documents, code, test cases, and test results).

☐ The Contractor shall implement Cybersecurity to protect PMA-281 data stored on the

IDE.

☐ The Contractor shall implement security safeguards to protect confidentiality, integrity, and availability of PMA-281 data products on the IDE.

☐ The Contractor shall implement receive and maintain IDE authority to operate from

Defense Security Services (DSS).

☐ The Contractor shall prepare and deliver a Data Accession List (DAL), CDRL A009 –

DAL

3.1.5.1 Delivery Order Specific Data Management and the Integrated Data Environment – Reserved

☐ Reserved for delivery order specific Data Management and IDE tasking.

3.1.6 Integrated Master Schedule

☐ The Contractor shall develop, deliver, and maintain an Integrated Master Schedule (IMS). Note: The Integrated Program Management Report CDRL has two versions.

Version 1 is applicable to all delivery orders that have an EVM requirement. Version 2 is applicable to delivery orders without an EVM requirement.

☐ The contractors IMS shall be fully integrated, contain duration of planned events, identify milestones, identify accomplishments, identify exit criteria, and activities from delivery order award to completion.

☐ The Contractor shall incorporate identified risk mitigation and opportunity steps in the

IMS. The Contractor shall identify schedule impacts for tasks that fail to complete on time in the IMS.

☐ The Contractor’s IMS shall include work performed by the subcontractor(s).

☐ The Contractor’s IMS shall be consistent with the CWBS.

☐ The Contractor’s IMS shall encompass all contracted scope of work.

☐ The Contractor’s IMS shall identify critical and high-risk efforts

☐ The Contractor’s IMS shall identify and specify critical milestones, critical path and scheduled programmatic and technical reviews.

☐ The Contractor’s IMS shall be extended and expanded as the work packages are implemented (e.g., rolling wave detail planning or scope changes).

☐ The Contractor’s IMS shall present a current, integrated view of the tasking that is consistent with resource plans and other approved contract documentation.

☐ The Contractor’s IMS shall include detailed analysis comparing work completed with work not completed.

☐ The Contractor’s IMS shall include tracking information related to deliverable completion

☐ The Contractor shall prepare and deliver CDRL A004 Integrated Program

Management Report (IPMR) Version 1.

☐ The Contractor shall prepare and deliver an IPMR, CDRL A005 IPMR Version 2.

3.1.6.1 Delivery Order Specific Integrated Master Schedule – Reserved

☐ Reserved for delivery order specific integrated master schedule tasking.

3.1.7 Integrated Product Teams

☐ The Contractor shall establish Integrated Product Teams (IPTs) necessary to conduct the contracted work.

☐ The contractor shall align contractor IPTs with established Government IPTs.

3.1.7.1 Delivery Order Specific Integrated Product Teams – Reserved

☐ Reserved for delivery order specific Integrated Product Team tasking.

3.1.8 Program Meetings and Reviews

☐ The Contractor shall conduct program meetings and reviews in support of contracted work.

☐ The Contractor shall establish agenda and content for each meeting and review.

☐ The Contractor shall participate in Government-led technical, programmatic, engineering Technical Interchange Meetings (TIMs). Whenever possible, meetings shall be combined and/or virtual to minimize Government and Contractor travel and documentation requirements.

3.1.8.1 Program Management Reviews

3.1.8.1.1 Post-Award Conference

☐ The Contractor shall conduct a post-award conference (PAC). The purpose of the PAC is to ensure both Government and Contractor personnel have a clear understating of all contract requirements.

☐ The Contractor shall work collaboratively with the Government to establish the agenda for the PAC and shall deliver conference minutes following the PAC.

☐ The Contractor shall prepare and deliver presentation material, CDRL A01V – Presentation Material.

☐ The Contractor shall prepare and deliver conference minutes, CDRL A006 – Conference Minutes

3.1.8.1.2 Program Management Reviews (PMRs)

☐ The Contractor shall conduct quarterly Program Management Reviews (PMRs) to provide the Government with visibility into the various efforts by the Contractor and its subcontractors.

☐ The Contractor shall work collaboratively with the Government to establish the agenda for the PMRs.

☐ The Contractor shall present and review the status of the technical, financial, quality, test, and schedule performance of the program during the PMR.

☐ The Contractor shall highlight problem areas in the program and provide recommendations for corrective actions during the PMR.

☐ The Contractor shall prepare and deliver presentation material, CDRL A01V – Presentation Material.

3.1.8.1.3 Delivery Order Specific Program Management Review Requirement -

☐ Reserved for delivery order specific Program Management review tasking.

3.1.8.2 Program Technical Reviews

3.1.8.2.1 Program Systems Engineering Technical Reviews

☐ The Contractor shall prepare and conduct technical reviews in accordance with the

NAVAIR Systems Engineering Technical Review (SETR) Process, reference (B).

☐ Table 3-1 provides a listing of SETR events.

Table 3-1 Applicable SETR Events

Applicable Review

NAVAIRINST 4355.19 SETR Event

☐ System Requirements Review ☐ System Functional Review ☐ Software Specification Review ☐ Preliminary Design Review

Review

NAVAIRINST 4355.19 SETR Event

☐ Release Backlog Review ☐ Critical Design Review ☐ Integration Readiness Review ☐ Test Readiness Review ☐ Flight Readiness Review ☐ Integrated Baseline Review ☐ Schedule Risk Assessment ☐ Functional Configuration Audit ☐ System Verification Review ☐ Production Readiness Review ☐ Physical Configuration Audit ☐ In-service Review ☐ Reserved for delivery order specific SETR Events

☐ The Contractor shall work collaboratively with the Government to establish SETR event agenda, entrance criteria, and exit criteria.

☐ The Contractor shall work collaboratively with the Government to assess the maturity of data artifacts leading to the SETR event.

☐ The Contractor shall implement the principles of Model Based Systems Engineering by using collaborative, readily accessible data tools and models to conduct SETR reviews.

☐ The Contractor shall prepare and deliver presentation material, CDRL A01V –

Presentation Material.

3.1.8.2.2 Program Technical Interchange Meetings

☐ The Contractor shall host Technical Interchange Meetings (TIMs) to discuss requirements, design, and/or other technical issues.

☐ The Contractor shall prepare and deliver presentation material, CDRL A01V –

Presentation Material.

3.1.8.2.3 Delivery Order Specific Program Technical Interchange Meetings –

☐ Reserved for delivery order specific program technical interchange meetings.

3.1.8.3 Government-led Technical, Programmatic, and Engineering Technical Interchange Meetings

☐ The Contractor shall participate in Government-led technical, programmatic, and engineering TIMs. Table 3-2 provides a listing of Government-led TIMs requiring Contractor participation.

Table 3-2 Government-Led Technical, Programmatic, and Engineering TIMs

3.1.8.3.1 Delivery Order Specific Government-led Technical, Programmatic, and Engineering Technical Interchange Meetings – Reserved

☐ Reserved for delivery order specific Government-led technical, programmatic, and engineering TIM tasking.

3.1.9 Government Furnished Property/Information (GFP/I)

TIM

Government-Led TIM Frequency

☐ Requirements Working Group Defined in the delivery order

☐ Risk Management Working Group Defined in the delivery order

☐ Architecture Working Group Defined in the delivery order ☐ Interface Control Working Group Defined in the delivery order ☐ System Safety Working Group Defined in the delivery order ☐ Safety Review Boards Defined in the delivery order ☐ Hazard Assessment Working Group Defined in the delivery order ☐ Test Plan Working Group Defined in the delivery order ☐ Test and Evaluation Working IPT Defined in the delivery order ☐ Program Management Reviews Defined in the delivery order ☐ Cybersecurity Working Group Defined in the delivery order ☐ Unmanned Systems (UxS) Control

Segment (UCS) Working Group Defined in the delivery order

☐ Technical Governance Group Defined in the delivery order ☐ Reserved for delivery order specific

TIMs

☐ The Contractor shall have an approved system for storage and tracking of all GFP/I provided by the Government.

☐ The Contractor shall ensure that all GFP/I shall be traceable to the project WBS.

☐ The Contractor shall prepare and deliver a Government Furnished Equipment Report, CDRL A00A – Status of Government Furnished Equipment Report.

3.1.9.1 Delivery Order Specific Government Furnished Property/Information –

☐ Reserved for delivery order specific GFP/I requirements.

3.2 System Engineering

3.2.1 General Systems Engineering Requirements

☐ The Contractor shall implement systems engineering processes which deliver hardware and/or software that meet the requirements established in the program / project Performance Specification.

☐ The Contractor shall ensure that systems engineering, technical, and management activities are conducted in accordance with an industry recognized standard equivalent to EIA-632.

☐ The Contractor shall ensure systems engineering, technical, and management activities are in accordance with the Government Systems Engineering Plan (SEP)

☐ The Contractor shall prepare and deliver a systems engineering management plan, CDRL A00B - Systems Engineering Management Plan

3.2.1.1 Delivery Order Specific General Systems Engineering Requirements –

☐ Reserved for delivery order specific systems engineering requirements.

3.2.2 Open Architecture (OA)

☐ The Contractor shall adopt an OA approach to meeting PMA-281 SW/HW requirements. The Government will procure system(s) having Open Architecture designs and corresponding components.

☐ The Contractor shall implement an OA approach using modular design, standards-based interfaces, and widely supported consensus-based standards.

☐ The Contractor shall implement and maintain an OA that allows for re-configurability, portability, maintainability, technology insertion, vendor independence, reusability, scalability, interoperability, and long-term supportability.

☐ The OA design shall allow for future upgrades, permit incremental technology insertion, and allow for incorporation of higher performance elements with minimal impact on the existing systems without large-scale redesign of the system.

☐ The Contractor shall demonstrate compliance with an OA design at Technical

Reviews and Technical Interchange Meetings.

☐ The Contractor shall implement an open system management plan.

☐ The Contractor’s open systems management plan shall, at a minimum, describe how the proposed system architecture meets these requirements, including the steps taken to use open, consensus-based interfaces, COTS, or reusable NDI components wherever practical.

☐ The Contractor shall prepare and deliver an Open Systems Management Plan, CDRL

A020 – Open Systems Management Plan.

3.2.2.1 Delivery Order Specific Open Architecture – Reserved

☐ Reserved for delivery order specific OA tasking.

3.2.3 Requirements Traceability

☐ The Contractor shall record, trace, and manage requirements at all levels, including operational, system, technical, and component levels, throughout the system life cycle.

☐ The Contractor shall allocate requirements to software and/or hardware components of the system.

☐ The Contractor’s requirements traceability tool shall be compatible with the

Government’s Dynamic Object Oriented Requirements System™ requirements traceability tool.

☐ The Contractor shall develop system/subsystem specification(s).

☐ The Contractor’s SSS shall be maintained in a relational data base compatible with the Government’s Dynamic Object Oriented Requirements System™ traceability tool.

☐ The Contractor shall develop a Requirement Traceability and Verification Matrix. The

RTVM shall provide bidirectional traceability from high-level system performance requirements, to the lowest-level requirements.

☐ The Contractor’s RTVM shall document traceability and allocation of the requirements contained in the specifications (e.g., performance specification, detailed specification, subsystem specification, software requirements specification, interface specification and design documentation).

☐ The Contractor’s RTVM shall document the verification method of each requirement.

☐ The Contractor’s RTVM shall be maintained in a relational data base compatible with the Government’s Dynamic Object Oriented Requirements System™ traceability tool.

☐ The Contractor shall prepare and deliver a system/subsystem specification, CDRL

A00V - System/Subsystem Specification

☐ The Contractor shall develop, deliver, and maintain a Requirements Traceability and

Verification Matrix (RTVM), CDRL A00W – Requirements Traceability Verification Matrix

3.2.3.1 Delivery Order Specific Requirements Traceability – Reserved

☐ Reserved for delivery order specific requirements traceability tasking.

3.2.4 Model Based Systems Engineering

☐ The Contractor shall implement a Model Based Systems Engineering (MBSE) process in accordance with IEEE 15288:2015 Systems and Software Engineering – System Life Cycle Processes Engineering resulting in digital representations of program and technical data being used to support all phases of systems development.

3.2.4.1 Architecture System Model

☐ The Contractor shall develop and implement a complete architectural System Model

(SM). The SM shall serve as "system architecture truth" for all other System

Development Life Cycle (SDLC) deliverables. Whenever there is a technical conflict between the SM and another deliverable, the SM will prevail.

☐ At a minimum, the SM shall:

☐ Use the Object Management Group (OMG) Systems Modeling Language (SysML), Service Oriented Architecture Modeling Language (SOAML), or Unified Modeling Language (UML);

☐ Shall identify all software components implemented as part of the contracted effort.

A software component is a unit of deployable software that is not further decomposed into other separately managed software components. A software component may be as small as a single service participant or as large as a complete domain or collection of domains;

☐ Include interfaces and functions of all services. Interface definition shall include identification of all published and subscribed messages;

☐ Provide a trace from service interfaces to the exchanges defined in SM Systems/Service Resource Flow Matrix (e.g., SV-6 matrix);

☐ Include a data model. The data model shall be linked to the services interfaces.

The data model shall include all messages and data elements in the Interface Definition Language (IDL) files;

☐ Include the relationship between software components and services;

☐ Trace System Requirements Specification requirements to services;

☐ Provide deployment views to show the relationship between services, software components, containers, and hardware.

☐ The SM shall demonstrate full Verification & Validation (V&V) support for all elements across the System Development Life Cycle (SDLC).

All System Architecture, Analysis and Design model elements for work artifacts shall either directly or indirectly (i.e., transitively) satisfy the System Functional and Non- Functional Requirements. All test cases for unit, integration, and system verification and validation shall test all model elements.

☐ The Contractor shall prepare and deliver an architecture model, CDRL A00C -

Architecture System Model

☐ The Contractor shall prepare and deliver an architecture model, CDRL A00D – System

Architecture Document.

☐ The SM shall be delivered in all of the following tool-independent document formats:

XML Model Interchange (XMI), HTML, RTF and PDF. In addition, all SM derived deliverables shall be accompanied by the SM View or specific Package from which it was derived in all the same tool-independent document formats listed above.

☐ The Contractor shall also deliver any tool-proprietary format(s) of the modeling tool used to generate the aforementioned SM and SM-derived deliverables in tool-independent formats. All SM and SM-derived deliverables shall be compatible with CAMEO version 19 or later.

3.2.4.2 Delivery Order Specific Software Architecture – Reserved

☐ Reserved for delivery order specific Model Based Systems Engineering requirements.

3.2.5 Technical Performance Measures (TPMs)

☐ The Contractor shall develop, monitor, and report TPMs.

☐ The Contractor shall report the status of TPMs monthly and at TIMs, PMRs, and SETR events consistent with the design approach and the agreed upon measurement plan.

In the case of parallel design paths, the Contractor shall provide TPMs for each path.

3.2.5.1 Software Performance Metrics

☐ The Contractor shall develop software performance metrics.

☐ The Contractor shall base software performance metrics on information contained in

Reference (D). The Contractor shall submit a description of planned approach for software metric and provide rationale for the metrics selection.

☐ The Contractor shall implement the following minimum set of core software TPMs:

☐ Software Size/Stability;

☐ Software organization including: manpower requirements (including staffing profile metrics, skills and certification required, training plan), training metrics (actual training vs. required by plan, and required experience), and staff turnover metrics;

☐ Software cost/schedule against an approved baseline, including cost and schedule variances and cost and schedule performance indices. The Contractor shall provide the basis for software cost estimation (e.g., parametric/analogous software size, historical software coding productivity);

☐ Percentage of total system functionality to be provided by software, percentage of total system functionality to be provided by software;

☐ Planned (expected) versus actual code size to include new, modified, reuse, auto-generated and/or code provided by open source/COTS/GOTS/NDI.

☐ Software quality, including defect density metrics and trends (e.g., defects per Software Lines Of Code, defects per unit, defects per interface).

☐ The Contractor shall prepare and deliver a Software Management Metric Report, CDRL A00E - Software Management Metrics Report.

3.2.5.2 Delivery Order Specific Software Technical Performance Measures –

☐ Reserved for delivery order specific Software metrics.

3.2.5.3 Hardware Performance Metrics

☐ The Contractor shall develop hardware performance metrics.

☐ The Contractor shall prepare and deliver a Hardware Management Metric Report, CDRL A00F – Hardware Management Metrics Report

3.2.5.4 Delivery Order Specific Hardware Technical Performance Measures –

☐ Reserved for delivery order specific Model Based Systems Engineering requirements.

3.3 Human Systems Engineering & Integration

☐ The Contractor shall develop and implement a Human Systems Engineering &

Integration (HSE&I) process based upon the latest version of MIL-STD-1472, reference (F).

☐ The Contractor shall ensure that the HSE&I process addresses the integration and management of human considerations in system design, development, and validation.

☐ The HSE&I process implementation shall maximize mission effectiveness and ensure the system can be operated and maintained in a cost-effective and safe manner consistent with manpower structure, personnel aptitudes, training, and resource constraints.

☐ The Contractor shall incorporate HSE&I with other program elements and processes associated with hardware and software design, system safety, training, test and evaluation, sustainment, reliability, maintainability, configuration management, and risk management.

☐ The Contractor shall conduct a Task Analysis to provide a basis for evaluation of the design of the system, equipment, or facility.

☐ The Contractor’s HSE&I process shall eliminate or mitigate any tasks that have an adverse effect on cost, system reliability, efficiency, effectiveness, or safety.

☐ Any HSE&I tasks that effect cost, system reliability, efficiency, effectiveness, or safety shall be tracked via the Risk Management Program.

☐ The Contractor shall continuously assess Task Analysis from early design, development, test/evaluation of the system, equipment selection, system deployment, and system sustainment

☐ The Contractor shall implement Human Engineering Simulation Concept to describe the intended use of mock-ups and simulators in support of engineering analysis, design support, test/evaluation, and sustainment.

☐ The Contractor shall develop and deliver a Human Engineering Design Approach

Document – Operator (HEDAD-O). The HEDAD-O quantitatively and qualitatively evaluates how equipment having an interface with operators meets human performance requirements and human engineering criteria.

☐ The Contractor shall prepare and deliver a critical task analysis, CDRL A00G – Critical

Task Analysis

☐ The Contractor shall prepare and deliver a human Engineering simulation concept, CDRL A00H – Human Engineering Simulation Concept

☐ The Contractor shall prepare and deliver a Human Engineering Design Approach

Document – Operator, CDRL A00J – Human Engineering Design Approach Document

– Operator)

☐ The…