MISTE_1_BASE_SOW_PSN.PDF

PEO-STRI-2017-W071

v0.1

20 July 2018

Distribution C – Authorized to U.S. Government agencies and their contractors in support of this contracting effort. Other requests for this document shall be referred to PM ITTS, IMO.

i

Table of Contents

1 SCOPE

1.1 Introduction

1.2 Goals and Objectives

1.3 Background

2 APPLICABLE DOCUMENTS

2.1 Department of Defense Directive (DoDD)

2.2 Department of Defense Instruction (DoDI)

2.3 Department of Defense Manual (DoDM)

2.4 Other Government Documents, Drawings, and Publications

2.5 Availability of Other Government Documents and Publications

3 REQUIREMENTS

3.1 TISE Pillars

3.1.1 Test Communication and Networks Categories

3.1.2 Sensor and Data Collection Categories

3.1.3 Test Environments Categories

3.2 Management, Organization and Processes

3.3 Enterprise Management

3.3.1 TISE

3.3.1.1 TISE Development and Installation

3.3.1.2 TISE Administration

3.3.1.3 TISE Data Management

3.3.1.4 TISE Data Maintenance

3.3.1.5 TISE Transition

3.4 Program Management

3.4.1 Integrated Product and Process Development (IPPD)

3.4.2 Integrated Master Plan (IMP) and Integrated Master Schedule

(IMS)

3.4.3 Integrated Performance Management System

3.4.4 Contractor Integrated Performance Management

3.4.4.1 IBR

3.4.5 Program and Design Reviews

3.4.6 Risk Management

3.4.7 Associate Contractor Agreements (ACAs)

3.4.8 Subcontractor Management

3.4.9 Cost as an Independent Variable (CAIV)

3.4.10 Contracting Invoice and Payment

3.5 Systems Engineering (SE)

3.5.1 Enterprise Instrumentation Asset Development and Evolution

3.5.2 Product Development, Integration, and Fielding

3.5.3 Contractor Facility

20 July 2018

Distribution C – Authorized to U.S. Government agencies and their contractors in support of this ii

3.5.4 Property Management Plan

3.5.5 Intellectual Property and Data Rights

3.5.6 Cybersecurity (CS)

3.5.6.1 CS Artifacts

3.5.6.2 Information Assurance Vulnerability Management Program

(IAVMP)

3.5.6.3 RMF Assess Only

3.5.6.4 HBSS

3.5.6.5 Spectrum Management

3.5.6.6 IA Contractor Training and Certification

3.5.6.7 Security Engineering

3.5.7 Software Engineering

3.5.7.1 Software Design and Implementation

3.5.7.2 Software Development Test

3.5.7.3 Software Requirements and Architecture Development and

Review

3.5.8 Hardware Engineering

3.5.9 Security

3.5.9.1 Handling or Access to Classified Information

3.5.9.2 Threat Awareness and Reporting Program (TARP)

3.5.10 Requirement Traceability Verification Matrix (RTVM)

3.5.11 Test Engineering

3.5.12 System Safety Program

3.5.13 Supportability Engineering

3.5.14 Hardware Component Manufacturing

3.5.15 Quality Assurance

3.5.16 Reliability Engineering Program

3.5.17 Maintainability Engineering Program

3.5.18 Manpower and Personnel Integration (MANPRINT)

3.5.19 Value Engineering

3.6 Logistics

3.6.1 Instructional Systems Development

3.7 Anti-Terrorism (AT) Requirements

3.7.1 AT Level 1 Training

3.7.2 iWATCH Training

3.7.3 Operations Security (OPSEC) Program

3.7.4 Requirement for OPSEC Training

3.7.5 Access and General Protection Policy and Procedures for CAC .. 25

3.7.6 Access to Government Information Systems

3.7.7 IA/IT Training

3.8 Contract Data Requirements List (CDRL)

20 July 2018

Distribution C – Authorized to U.S. Government agencies and their contractors in support of this iii

3.9 U.S. Army Major and Minor Test Ranges

3.10 Disclosure of Information

LIST OF TABLES

Tables Title Page Table 3.2-1: Management, Organization and Processes Table 3.5.1-1: Tasks and Activities of Test Instrumentation Asset Development and

Evolution Table 3.5.2-1: Tasks and Activities of Test Instrumentation Development, Integration, and Fielding Table 3.6-1: Logistics Tasks and Activities Table 3.8-1: Types of CDRLs

20 July 2018

Distribution C – Authorized to U.S. Government agencies and their contractors in support of this

STATEMENT OF WORK (SOW)

For

MODERNIZING INSTRUMENTATION SOLUTIONS FOR TEST AND EVALUATION

(MISTE)

1 SCOPE

This SOW defines the scope of the Project Manager for Instrumentation, Targets, Threat Simulators and Special Operations Forces Training Systems (PM ITTS) Instrumentation Management Office’s (IMO) MISTE Indefinite Delivery Indefinite Quantity (IDIQ) contract.

The MISTE IDIQ may be utilized by Department of Defense (DOD) organizations and agencies that have related test instrumentation needs. These agencies include, but are not limited to, Army Program Executive Offices (PEOs), Army Test and Evaluation Command (ATEC), and Navy, Air Force and Joint test community organizations in support of DOD test ranges. Ranges within the DOD Test and Evaluation (T&E) community that benefit from these modernization efforts are those among ATEC and/or the Test Resource Management Center (TRMC) Major Range and Test Facility Base (MRTFB). MISTE provides for the design, development, integration, testing and fielding of test capabilities and/or related test infrastructure among these test ranges through a series of Delivery Orders (DOs). DOs will be issued under the general scope of this base IDIQ contract SOW pursuant to Federal Acquisition Regulations (FAR) Part 16.5.

MISTE is designed to deliver test instrumentation utilizing an enterprise approach that focuses on commonality and interoperability in the phased execution of subsequent DOs.

This approach is referred to as management of the MISTE Test Instrumentation Systems Enterprise (TISE). The enterprise management of TISE includes a system that optimizes the process of speed to award for successive DOs through effective collaboration with the Government that ensures expedited performance and full integration of program objectives. Also as capabilities are fielded, the contractor shall initiate the evolution of the TISE that assesses common requirements and interoperability as a baseline requirement for all Dos, unless deemed financially untenable by the Government. Considerations include compatibility, commonality, and interoperability with the previously fielded capabilities within the MISTE TISE, and the ability to create a common, efficient, and effective strategy for sustaining fielded capabilities. The enterprise construct will employ a decision tree process in recognizing the proper conditions that affordably reflect life cycle benefits through engaging further processes that involve appropriate requirements tracing, and asset tracking mechanisms for the Government’s TISE. The approach shall include governance, standards, processes, tools, and environments for the development, testing, delivery, training, and measures for life cycle optimization of test instrumentation systems and subsystems, where applicable.

This SOW defines the general requirements that PM ITTS IMO needs under the MISTE IDIQ contract. Individual DOs will include the detailed requirements in each respective SOW and specification (as needed) or Performance Work Statement, if determined

20 July 2018

Distribution C – Authorized to U.S. Government agencies and their contractors in support of this appropriate. Based on the enterprise approach, its tools and system will identify redundancies, commonalities, and potential technology insertions for pending developments, which is expected to lead to efficiencies. The contract will deliver test instrumentation systems and related range infrastructure that support the three pillars of the TISE (Test Communication/Networks, Sensors and Data Collection, and Test Environments).

This contract includes potential ancillary services:

a. Enterprise Capability Analysis

b. Enterprise Tools and Methodologies

c. Instrumentation Asset Development and Automation

d. Facility Upgrades

e. Distributed Configuration Management

f. Program Management

g. Test Instrumentation Development

h. System Engineering

i. Software Integration

j. Hardware Integration

k. Instrumentation System Integration

l. Testing/Automated Testing

m. Testing as a Service

n. Virtualization - Infrastructure

o. New Equipment Training

p. Technical Documentation Development

1.1 Introduction

The MISTE contract will satisfy PM ITTS IMO’s requirement for a consolidated, integrated, and streamlined enterprise approach for acquiring T&E instrumentation capabilities in support of Army PEOs, ATEC, Navy, Air Force and Joint test community organizations. This enterprise approach protects and leverages the Army’s future investments in test instrumentation systems and related range infrastructure. The contract will also facilitate the evolution of the TISE data system based on test instrumentation requirements as they emerge over the term of contract performance. The enterprise data system will provide information for acquisition life cycle optimization for test instrumentation and related range infrastructure to organizations operating within it.

The MISTE contractor shall develop the core test instrumentation/infrastructure capabilities where applicable, while providing PM ITTS IMO an efficient, effective, and agile method to:

a. Expedite DO awards through collaborative preliminary documentation reviews, market research, and decision-making for applying best value resources to required instrumentation capabilities developments;

20 July 2018

Distribution C – Authorized to U.S. Government agencies and their contractors in support of this

b. Establish the TISE approach for the procurement of test instrumentation capabilities;

c. Identify repeatable acquisition, technology and logistics life cycle system management optimization of systems/products that are developed within the TISE framework; and,

d. Support of external interoperability initiatives.

1.2 Goals and Objectives

The primary goal of the MISTE contract is to support the expedited development and fielding of test instrumentation products/systems within the TISE. The strategic objective of the MISTE contract is to initiate a methodical evolution of technology insertions in the TISE. This will provide an efficient acquisition life cycle optimization to PM ITTS IMO stakeholders operating within the TISE framework.

The MISTE contract supports the business goals of PM ITTS IMO to include:

a. Reducing capability delivery time to requiring activities;

b. Reducing operational cost and complexity;

c. Aligning and supporting product development (requirements-based, common standards, and interfaces);

d. Reducing development sustainment costs;

e. Increasing technological agility (open systems and open architectures);

f. Leveraging other T&E systems; and,

g. Allowing for technology modernization and insertions as systems age to extend operability/capability life cycles.

1.3 Background

In Accordance With (IAW) Army Regulation (AR) 73-1, PEO STRI is the Materiel Developer for Army major test instrumentation systems used by the developmental and operational test centers of the Army and Joint-Services customers. This includes DOD acquisition-defined Army and other DOD Major Tests that are funded at test ranges. PM ITTS IMO recognizes the inefficiencies that exist in the stove-piped acquisitions and development approaches utilized in the procurement of the legacy T&E instrumentation systems across the test community. Subsequently, PM ITTS IMO developed the TISE approach to efficiently and effectively procure future test instrumentation capabilities.

This approach focuses on analysis of test instrumentation requirements of developmental and operational test capabilities under development within the TISE across all test centers. The strategic objectives capitalize on instrumentation commonality, component reuse, and system interoperability vs. obsolescence. The expected benefits are to enable the Army to streamline the acquisition process and minimize the redundant cost of test instrumentation capabilities across the enterprise. This maximizes opportunities for instrumentation standardization, repurposing test capabilities, and technology insertion.

20 July 2018

Distribution C – Authorized to U.S. Government agencies and their contractors in support of this

As new military weapons systems are designed and developed, the need for new test instrumentation to keep pace with the testing of those technology developments will be required. The IMO efforts listed below encompass, but are not limited to, the potential contract DO instrumentation requirements for MISTE:

a. Integrated Live-Virtual-Constructive Test Environment

b. Accelerated Vehicle Durability Test

c. Applied Environments Modernization

d. System-of-Systems Controlled Environment Test & Evaluation Infrastructure

e. Future Wireless Network

f. Test Network Modernization

g. Fiber Modernization

h. Robotics Unmanned Autonomous System Instrumentation Suite

i. Telemetry Systems Modernization

j. Hypersonic Test Capability Improvement

k. Mobile High Energy Laser Measurement

l. Dense Plasma Focus

m. Autonomous System Test Capability

n. Radio Frequency Multipath Electromagnetic Environment

o. ATEC Integrated Mission Management System

2 APPLICABLE DOCUMENTS

The following documents form a part of this SOW to the extent specified herein. In the event of a conflict between documents referenced herein, and the contents of this SOW, the contents of the base IDIQ SOW and individual DOs shall be the governing requirements.

2.1 Department of Defense Directive (DoDD)

DoDD 8570.01 Information Assurance (IA) Training, Certification, and Workforce Management

DoDD 5000.01 The Defense Acquisition System

2.2 Department of Defense Instruction (DoDI)

DoDI 5230.24 Distribution Statements On Technical Documents DoDI 8500.01 Cybersecurity DoDI 8510.01 Risk Management Framework (RMF) for DoD Information

Technology (IT) DoDI 8582.01 Security of Unclassified DoD Information on Non-DoD

Information Systems DoDI 5000.02 Operation of the Defense Acquisition System DoDI 5200.46 DoD Investigative and Adjudicative Guidance for Issuing the Common Access Card (CAC)

20 July 2018

Distribution C – Authorized to U.S. Government agencies and their contractors in support of this

2.3 Department of Defense Manual (DoDM)

DoDM 8570.01 IA Workforce Improvement Program

(http://www.esd.whs.mil/Portals/54/Documents/DD/issuanc es/dodm/857001m.pdf)

DoDM 5220.22 National Industrial Security Program Operating Manual

(NISPOM)

(http://www.esd.whs.mil/Portals/54/Documents/DD/issuanc es/dodm/522022M.pdf)

DoDM 5200.1 Acquisition Systems Protection Program

2.4 Other Government Documents, Drawings, and Publications

Army Directive (AD) 2014-05

Policy and Implementation Procedures for Common Access Card Credentialing and Installation Access for Uncleared Contractors

FAR 52.204-2 Security Requirements (www.acquisition.gov/far/) FAR 52.204-9 Personal Identity Verification of Contractor Personnel Office of Management and Budget (OMB) Circular A-11

OMB Circular A-11

Committee on National Security Systems Instruction

(CNSSI) 1253

Security Categorization and Control Selection for National Security Systems

Committee on National Security Systems Policy (CNSSP) No. 11

National Policy Governing the Acquisition of IA and IA-Enabled Information Technology Products (https://www.cnss.gov/CNSS/issuances/Policies.cfm)

National Institute of Standards and Technology Special Publications (NIST

SP) 800-53

Security and Privacy Controls for Federal Information Systems and Organizations

Communications Tasking Order (CTO) 07-12

Deployment of Host Based Security System (HBSS) (https://www.jtfgno.mil/)

Military-Handbook

(MIL-HDBK) 189C

Reliability Growth Management (http://www.dote.osd.mil/docs/dote-temp-guidebook/MIL-HDBK-189C.pdf)

MIL-HDBK-61A Configuration Management Guidance (acc.dau.mil/adl/en-US/142238/file/27622/MIL-

HDBK-

61A(SE)%20Configuration%20Management%20Gui dance.pdf ) http://www.esd.whs.mil/Portals/54/Documents/DD/issuanc http://www.esd.whs.mil/Portals/54/Documents/DD/issuanc http://www.acquisition.gov/far/) http://www.cnss.gov/CNSS/issuances/Policies.cfm) http://www.cnss.gov/CNSS/issuances/Policies.cfm) http://www.jtfgno.mil/) http://www.jtfgno.mil/) http://www.dote.osd.mil/docs/dote-temp-

20 July 2018

Distribution C – Authorized to U.S. Government agencies and their contractors in support of this

Military Standard

(MIL-STD) 882

Department of Defense Standard Practice: System Safety

American National Standards Institute/Electronic Industries Alliance

(ANSI/EIA) 748

Earned Value Management (EVM)

Institute of Electrical and Electronics Engineers (IEEE) 12207:2017

Systems and Software Engineering – Software Life Cycle Processes

IEEE 15288:2015 Systems and Software Engineering – System Life Cycle Processes

IEEE 15288.1 Standard for Application of Systems Engineering on Defense Programs

IEEE 15288.2 Standard for Technical Reviews and Audits on Defense Programs

AR 5-12 Army Management of the Electromagnetic Spectrum

AR 25-2 IA

AR 190-13 The Army Physical Security Program

AR 602-2

Human Systems Integration in the System Acquisition Process

AR 70-1 Army Acquisition Policy (Research, Development and Acquisition)

AR 73-1 Test and Evaluation Policy AR 380-5 Department of the Army (DA) Information Security

Program AR 380-10 Foreign Disclosure and Contacts with Foreign

Representatives AR 380-49 Industrial Security Program AR 381-12 Threat Awareness and Reporting Program AR 530-1 Operations Security

2.5 Availability of Other Government Documents and Publications Copies of the above documents are available as stated above or from: Army Contracting Command – Orlando, Contract Specialist, Joseph Candelaria, (joseph.candelaria5.civ@mail.mil/407-208-3220).

20 July 2018

Distribution C – Authorized to U.S. Government agencies and their contractors in support of this

3 REQUIREMENTS

The requirements defined herein form the basis for all efforts outlined in potential DOs to be issued under the MISTE contract for the design, development, integration, prototype production, testing, and fielding of major and minor test instrumentation. The contractor shall deliver test instrumentation systems, including ancillary support services, which support the three pillars of the TISE.

3.1 TISE Pillars

The three primary test instrumentation requirement pillars are Test Communication/Networks, Sensors and Data Collection, and Test Environments and include, but are not limited to:

3.1.1 Test Communication and Networks Categories

a. Telemetry Systems

b. Range Test Networks

c. Range Wireless Networks

d. NextGen Data Management

e. Flight Termination Systems

f. Frequency Surveillance System Replacement

3.1.2 Sensor and Data Collection Categories

a. Explosive Weapons Fragmentation Characteristics

b. Radar Cross-Sections

c. High Energy Lasers

d. Robotics and Autonomous Systems

e. NextGen Common Data Collectors

f. Advanced Sensors Test Lab

g. Active Protection Systems

h. Advanced Power Systems

3.1.3 Test Environments Categories

a. Hypersonic

b. Electronic Warfare Simulators/Stimulators

c. Pulsed Neutron Emissions

d. Cyber Constructive Environments

e. Military Vehicle Durability

f. Autonomous Systems

g. MIL-STD Physical and Environmental Effect (chambers, simulators/stimulators)

3.2 Management, Organization and Processes

The contractor shall perform the programmatic activities which provide for an optimized knowledge base system enterprise organizational structure. The contractor’s approach shall ensure efficient processes for the management and oversight of the enterprise

20 July 2018

Distribution C – Authorized to U.S. Government agencies and their contractors in support of this technical activities, including resources utilized across all MISTE DOs. The following table provides a representative list of ancillary tasks and activities that could be required by specific DOs with respect to management, organization and processes.

Table 3.2-1: Management, Organization and Processes

Technical Planning Interface Management Requirements Management Configuration Management Risk Management Technical Assessment Technical Data Management Customer Interface Management Decision Analysis Organizational Planning Technology Forecasting Metrics, Measurement and Tracking Technology Assessment Interoperability Assessment Resource Planning and Management Facilities Assessment Integrated Product Team Management Technical Reviews Business Strategy Concept of Operations Reuse Analysis Data Repository Transition Planning Training Development

3.3 Enterprise Management

The contractor shall implement an enterprise management approach to efficiently and effectively address future developmental and operational testing capability requirements.

This approach shall allow the Government to make informed decisions on future development and best value procurements of test instrumentation capabilities. As required, the contractor shall conduct configuration management to a level that facilitates accurate decision making analysis on procuring a new test instrumentation capability vice enhancing a current capability. Enhancement of current capability with technology insertion to meet a new capability requirement at a reduced cost is preferred. The contractor shall identify instrumentation commonality, component reuse, and system interoperability across all instrumentation systems and products delivered within the MISTE domain space.

3.3.1 TISE

The contractor shall develop, protect, and leverage the Army’s TISE knowledge base system investment, while evolving test instrumentation capabilities. TISE processes and tools shall allow the Government to make informed decisions on future development and best value procurements of test instrumentation capabilities.

The contractor shall establish a TISE that provides an online, interactive, collaborative, and access controlled environment. The Government and contractor/subcontractor team members shall be able to exchange information and collaborate in a distributed environment. The TISE shall be based on processes and standards that support data and requirements management, and stores collaborative artifacts, software, tools, Technical Data Package (TDP) artifacts, and architecture products.

20 July 2018

Distribution C – Authorized to U.S. Government agencies and their contractors in support of this

The TISE shall provide an efficient, effective, and agile method to:

a. Develop, integrate, test, maintain, and evolve the enterprise;

b. Support systems and System-of-Systems (SoS) capabilities;

c. Evolve the architectural and system developments, in support of external interoperability initiatives such as Live, Virtual, Constructive, Common Operating Environments, and DOD Service initiatives; and,

d. Achieve PM ITTS IMO Business Goals: reduce delivery time of test instrumentation; reduce operation costs and complexity; align and support product development (common standards, interfaces, etc.); reduce development costs;

increase technology insertion agility; and leverage other DOD test instrumentation systems and Commercial Off-The-Shelf (COTS) technologies.

The contractor shall include software applications and database services for the generation, integration, storage, indexing, distribution, simultaneous on-line sharing of digital data among all Government and contractor team members, and delivery of TDP products with associate contractors, subcontractors, and Government organizations.

The contractor shall maximize the use and capabilities of existing open source software products as the contractor defines the TISE components. Specifically, integrated automated databases are required which shall allow technical data sharing at the database level, rather than at the physical file level, with multiple formats of the same data from a common, configuration-controlled source available to different users. The TISE shall provide program personnel complete visibility into the system at every stage of development, regardless of data location.

The contractor shall ensure that all contractor personnel associated with this project have access to information required to properly perform their duties.

3.3.1.1 TISE Development and Installation

The contractor shall provide a TISE with the following capabilities:

a. Ability to capture information as it is created;

b. Ability to manage product structures;

c. Real-time information sharing and work flow implementation;

d. Team access to the most current information;

e. Ability to assign rules regarding information access;

f. Common information architecture that is distributed geographically;

g. Electronic notification of changes to program and product information;

h. Ability to present a single interface to the entirety of the contractor’s and subcontractors' data creation activities;

i. Ability to recover from unexpected loss of program data due to environmental disasters, operator error, equipment failure, and hostile intruders; and, 20 July 2018

Distribution C – Authorized to U.S. Government agencies and their contractors in support of this

j. Ability to provide access to program data using standards defined through an open systems approach.

3.3.1.2 TISE Administration

The contractor shall provide a web-enabled electronic knowledge base system to facilitate the electronic data interchange of UNCLASSIFIED data.

a. The contractor shall provide the Government and contractor team members with the capabilities for on-line review, comment, acceptance and approval of deliverable data.

b. The contractor shall establish appropriate audit trails to identify the sources of these additions and to maintain configuration control.

c. The contractor shall develop and implement procedures for establishing and administering user accounts for the TISE.

d. The contractor shall develop, maintain, and implement an online, interactive, self-taught user-training program to ensure users are able to operate within the TISE and understand their roles and responsibilities within the TISE processes.

e. The contractor shall provide access to all tools, test equipment, and consumable items required to accomplish any development, maintenance or installation identified per DO.

f. The contractor shall provide the Government and Government support contractors the ability to download any software that was developed and accepted by individual DOs for the ordering period of the contract.

3.3.1.3 TISE Data Management

The contractor shall establish, implement, and maintain a data management capability within the TISE for the integration, storage, access, management, delivery, and exchange of data furnished by the Government or generated by any contract work effort, including subcontractors and vendors. The system shall be capable of maintaining a record and reporting the status of data accession and data deliveries for each DO. The contractor shall generate and maintain a master listing of all documents located at the test site delivered for each DO. The listing shall include all operations and maintenance publications, engineering drawings and specifications, software source code, software databases, training materials, and baseline description documents.

3.3.1.4 TISE Data Maintenance

The contractor shall develop and maintain a technical information validation process to validate the adequacy and accuracy of the technical data contained within the TISE. The contractor shall initially populate operation and maintenance or engineering data at each test site to reflect the latest DOs. These libraries shall consist of the technical publications, product definition data, tools, architecture products, software application, source code and hardware configuration and programming data delivered by each DO.

The contractor shall perform an audit of technical publications and product definition data

20 July 2018

Distribution C – Authorized to U.S. Government agencies and their contractors in support of this and make any changes necessary to each library so that a complete set of documentation exists.

3.3.1.5 TISE Transition

The contractor shall develop a Transition Plan and provide support for the transfer of the TISE responsibility to the Government or another contractor when required. [DI-MISC- 80711, Scientific and Technical Reports (Transition Plan)]

3.4 Program Management

The contractor shall provide the overall management and administrative effort necessary to ensure the requirements of this contract are accomplished in an efficient and cost effective manner. The contractor shall track DO progress utilizing metrics specified by the Government, and ensure that a robust Quality Control Program (QCP) is implemented and maintained at the DO level. The contractor shall implement an agile process to address improved performance for time to award DOs. The contractor shall plan, implement, and maintain a Life Cycle Cost (LCC) management process to minimize the system cost and use LCC to conduct trade studies, evaluate design, support alternatives, and recommend resource support requirements. The contractor shall define and monitor Technical Performance Measures (TPMs) to ensure conformance of the test instrumentation systems with contract requirements. (DI-MGMT-80227, Contractor’s Progress, Status and Management Report)

3.4.1 Integrated Product and Process Development (IPPD)

The contractor shall establish and maintain a process for IPPD and participate in joint Government/contractor Integrated Product Teams (IPTs) in a performance-based business environment to manage and integrate all DOs, tasks, activities, and data. The contractor shall provide a process/tool to facilitate Government insight into contract activities, and provide regular program status reviews on all issued DOs. The contractor shall make available to the Government all technical, cost, and schedule data. The level of information will be determined by each DO. The contractor shall maintain the processes approved by the Government for the ordering period of the contract.

3.4.2 Integrated Master Plan (IMP) and Integrated Master Schedule (IMS) The contractor shall develop an IMP and an IMS. The contractor shall maintain and manage to the IMP and IMS developed for each specific DO, including appropriate program milestones with corresponding entrance and exit criteria. The IMP shall include a detailed account of all tasks necessary to accomplish the goals and objectives of each specific DO which supports the processes/tools identified in Table 3.2-1.

The contractor shall develop and maintain an IMS by logically networking detailed program activities including synchronization of all active DOs. The IMS shall address total program activities performed by the contractor and any subcontractors involved with each DO. These activities shall be keyed to the Contract Work Breakdown Structure (CWBS). The contractor shall quantify risk in hours, days, or weeks of delay and provide

20 July 2018

Distribution C – Authorized to U.S. Government agencies and their contractors in support of this the most likely duration for each IMS activity and event. The contractor shall conduct critical path analysis of the tasks and identify problem areas and corrective actions required to eliminate or reduce schedule impacts.

3.4.3 Integrated Performance Management System

If the DO requires Earned Value Management System (EVMS), the contractor shall integrate cost, schedule, and performance management information as defined in FAR 34.2, Defense Federal Acquisition Regulation Supplement (DFARS) 234.2 and OMB Circular A-11. The contractor shall develop, implement, maintain, and use an EVMS that complies with Industry Guidelines ANSI/EIA-748 and meets contractual requirements.

The contractor shall document the integrated cost and schedule status of work progress on the contract, and relate technical performance with cost and schedule accomplishment using procedures for planning work, controlling costs, and measuring performance based on ANSI/EIA-748. The contractor’s EVMS shall be determined compliant by the Government. The contractor is advised that, when EVMS is applicable, the Government will perform an Integrated Baseline Review (IBR) per FAR 34.202 on individual DOs that meet the threshold requirements for EVMS, as stated at DFARS 234.2, within 30 days of DO issuance.

3.4.4 Contractor Integrated Performance Management

As specified by individual DOs, the contractor shall establish, maintain, and use in the performance of each DO, an integrated performance management system that results in an accurate and supportable Performance Measurement Baseline (PMB) and mitigates program risk. Central to this integrated system shall be a validated EVMS IAW the basic contract clauses and the EVMS guidelines contained in ANSI/EIA-748. To establish the integrated performance management system, the EVMS shall be linked to and supported by the contractor’s management processes and systems to include the IMS, CWBS, change management, material management, procurement, cost estimating, and accounting. The correlation and integration of these systems and processes shall provide for early indication of cost and schedule problems, and their relation to technical achievement.

3.4.4.1 IBR

As specified by individual DOs, the contractor shall engage jointly with the Government’s program manager in IBRs to evaluate the risks inherent in the contractor’s planned PMB.

This shall occur as soon as feasible, but not later than the date specified by each DO award that requires EVM oversight. Each IBR shall verify the contractor is using a reliable PMB, which includes the entire contract scope of work, is consistent with contract schedule requirements, and has adequate resources assigned. Each IBR shall also record any indications that effective EVM is not being used. IBRs shall also be conducted on subcontracts that meet or exceed the EVM application threshold. The prime contractor shall lead the subcontractor IBRs, with active participation by the Government.

20 July 2018

Distribution C – Authorized to U.S. Government agencies and their contractors in support of this

3.4.5 Program and Design Reviews

As specified by individual DOs, the contractor shall conduct program and design reviews (e.g., Preliminary Design Review, System Design Review, System Requirements Review, Critical Design Review) and applicable Technical Interchange Meetings for the Government and IPT members.

3.4.6 Risk Management

As specified by individual DOs, the contractor shall implement an integrated risk management system with risk planning, identification, assessment, mitigation, and monitoring functions to improve technical, cost, and schedule performance.

3.4.7 Associate Contractor Agreements (ACAs)

As specified by individual DOs, the contractor shall implement ACAs for exchanging data, accessing and using third party software and equipment, receiving technical support, working interface issues, and transitioning from associate contractor to the test centers.

ACAs shall be maintained to achieve interoperability and common component goals, as applicable.

3.4.8 Subcontractor Management

The contractor shall manage and execute to each approved DO subcontractor management plan as applicable. The contractor shall integrate subcontractors into program IPTs. Additionally, subcontractors shall be included in program management and tracking systems, such as management information systems, EVMS, etc. The contractor shall ensure the requirements of this contract and subsequent DOs are applied to all subcontracts and associate contracts. The contractor shall track program progress and inform the Government of program impacts, positive or negative, to cost, schedule, and performance. (DI-MGMT-80227, Contractor’s Progress, Status and Management Report)

3.4.9 Cost as an Independent Variable (CAIV)

As specified by individual DOs, the contractor shall participate on joint Government-contractor cost performance IPTs to discuss tradeoff options for implementing CAIV concepts and guidance.

3.4.10 Contracting Invoice and Payment

The contractor shall document and track the status of all funds associated with the contract to include obligations, payments, cancellations, invoices, and disbursements against each contract line item and sub-line item.

As specified by individual Cost Reimbursement or Time and Material DOs, the contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services under this contract for the MISTE via a secure data collection site. The contractor is required to completely fill in all required data fields using the following web address: http://www.ecmra.mil/. Reporting inputs will be for labor executed http://www.ecmra.mil/

20 July 2018

Distribution C – Authorized to U.S. Government agencies and their contractors in support of this during the period of performance during each Government Fiscal Year (FY), which runs 1 October through 30 September. While inputs may be reported any time during the FY, all data shall be reported no later than 31 October of each calendar year. Contractors can find User Guides, Frequently Asked Questions and may direct questions to the help desk at http://www.ecmra.mil/. (DI-MGMT-81651, Contract Invoicing and Payment Report).

3.5 Systems Engineering (SE)

The contractor’s SE practices shall support the standards and practices prescribed in the Defense Acquisition Guidebook Chapter 3, IEEE 15288, IEEE15288.1, and IEEE15288.2 in managing program requirements. The contractor shall provide the requisite technical and programmatic support to complete each DO associated with the test instrumentation system requirements. Each DO shall encompass the efforts associated with the development, dissemination, engineering, management, and maintenance of the enterprise architecture, components, and documentation. Each DO shall include the work efforts associated with the engineering, management, and tracking of TISE-fielded test instrumentation assets.

3.5.1 Enterprise Instrumentation Asset Development and Evolution The contractor shall perform the necessary tasks and activities to continue the development, evolution, and maintenance of the TISE knowledge base system. The Government will address the specific requirements in each DO. The following table provides a representative list of tasks and activities that could be required by specific DOs with respect to Enterprise Instrumentation Asset Development and Evolution:

Table 3.5.1-1: Tasks and Activities of Test Instrumentation Asset Development and

Evolution Architecture Development Technology Assessments Architecture Validation Domain Analysis Decision Analysis Manufacturing Assessments Re-Use Analysis Service/Component Development Requirements Engineering Test and Verification Enterprise User Training Version Control Technology Insertion Life Cycle Support Plan Configuration Management Producibility Analysis Performance Verification and Validation Quality Assurance System of System Model Management and Enhancement

Test as a Service and Infrastructure as a Service Development

Training Development

3.5.2 Product Development, Integration, and Fielding

The contractor shall perform the necessary tasks and activities for product development, integration, prototype production, testing, and fielding. The Government will address the specific requirements in each DO. The following table provides a representative list of http://www.ecmra.mil/

20 July 2018

Distribution C – Authorized to U.S. Government agencies and their contractors in support of this tasks and activities that could be required by specific DOs with respect to product development, integration, and fielding:

Table 3.5.2-1: Tasks and Activities of Test Instrumentation Development, Integration, and Fielding Concept Development Functional Analysis Requirements Analysis System Engineering Software/Hardware Engineering System Design Prototyping Software Integration System Integration Testing and Test Engineering Fielding Training Verification Testing Validation Testing System Demonstration RMF Testing and Certification Configuration Management Security Engineering Trade Studies Quality Engineering

3.5.3 Contractor Facility

As specified by individual DOs, the contractor shall establish and enforce security procedures IAW security classification of products and services and the Contracts Security Classification Specifications, DD Form 254 and addendum sheets according to NISPOM requirements. The contractor shall have a Defense Security Service (DSS) cleared facility at time of contract award based on the DD Form 254 security classification, and shall be maintained throughout the term of the contract.

3.5.4 Property Management Plan

As specified by individual DOs, the contractor shall implement their property management plan (IAW requirements in Contract Section H) for Government Furnished Property (GFP) provided and Contractor Acquired Property (CAP) acquired under this contract. This plan shall initiate and maintain the processes, systems, procedures, records, and methodologies necessary for effective and efficient control of GFP and CAP. The contractor shall update the plan as necessary and notify the Government of any significant changes prior to implementation. All property shall be administered to ensure compliance with FAR Part 45 requirements entitled Government Property. The contractor’s Property Management System (PMS) will be reviewed for compliance in accordance with FAR 45.105 and per Defense Contract Management Agency (DCMA) Instruction 124 by the cognizant DCMA Property Administrator, if delegated by individual DOs.

3.5.5 Intellectual Property and Data Rights

On all DOs, the contractor shall provide the Government non-proprietary products. The contractor shall obtain and deliver to the Government a minimum of Government Purpose Rights to any intellectual property, software code, and data produced in the course of designing, configuring, testing, operating, deploying, training, and supporting any products delivered under this contract, such that the Government can:

20 July 2018

Distribution C – Authorized to U.S. Government agencies and their contractors in support of this

a. Use, maintain, modify, reproduce, release, perform, display, or disclose technical data within the Government without restriction;

b. Release or disclose technical data outside the Government and authorize persons to whom release or disclosure has been made to use, maintain, modify, reproduce, release, perform, display, or disclose that data for United States Government purposes;

c. Maintain, repair, modify, and upgrade test instrumentation systems using Government personnel and other Government contractors; and,

d. Compete future test instrumentation system requirements, maintenance, repair, modification, and upgrades.

All delivered data shall be marked accordingly.

3.5.6 Cybersecurity (CS)

As specified by individual DOs, the contractor shall integrate CS into their programmatic processes, document decisions, specify and track CS requirements, document assessment efforts, identify possible solutions, and maintain operational systems security IAW DoDI 8500.01, DoDI 8510.01, DoDM 8570.01, CNSSI 1253, NIST SP 800-53, DoDI 8582.01, and AR 25-2. The contractor shall secure all DOD information on non-DOD information systems IAW DoDI 8582.01.

As part of the system design and component selection process, CS shall be considered a requirement for all systems used to enter, process, store, display, or transmit DOD information. CS shall be achieved through the acquisition and appropriate implementation of evaluated or validated COTS or Government Off-The-Shelf (GOTS) CS and CS-enabled IT products. All CS products and CS-enabled products shall be certified compliant with CNSSP-11 by labs accredited under the National IA Partnership Common Criteria Evaluation and Validation Scheme or NIST Federal Information Processing Standards Cryptographic Module Validation Program. Similarly, GOTS CS products or CS-enabled products employed by the system shall be evaluated by the National Security Agency (NSA) or IAW NSA-approved processes. All CS and CS-enabled products shall be securely configured IAW DOD-approved security configuration guidelines. As specified by individual DOs, the contractor shall obtain Security Technical Implementation Guides (STIGs) (http://iase.disa.mil/stigs/index.html) and implement each applicable STIG into the design.

3.5.6.1 CS Artifacts

As specified by individual DOs, the contractor shall comply with the CS process IAW DoDI 8510.01 RMF for DoD IT, CNSSI 1253, and the NIST SP 800-53.

The contractor shall produce all components of the RMF package necessary to deliver and operate a fully accredited system. As specified by individual DOs, the contractor shall ensure that the CS requirements and procedures are met IAW all required DOD and ARs per the confidentiality, integrity and availability levels specified for the system.

http://iase.disa.mil/stigs/index.html)

20 July 2018

Distribution C – Authorized to U.S. Government agencies and their contractors in support of this

3.5.6.2 Information Assurance Vulnerability Management Program (IAVMP) As specified by individual DOs, and as part of IAVMP, the contractor shall document the incorporated and unincorporated IA Vulnerability Alerts, IA Vulnerability Bulletins, and IA Vulnerability Technical Advisories. The IAVMP plan shall include, but is not limited to, identifying and assessing potential threats to determine risks. It also involves developing and implementing controls, countermeasures, or solutions. The contractor shall monitor the system for compliance and success, while evaluating and refining the IAVMP as necessary. The contractor shall incorporate all applicable DOD and DA IA Vulnerability Management messages issued on behalf of the DA G2, Chief Information Officer (CIO)/G6 and Joint Task Force-Global Network Operations. The contractor shall provide justification for each unincorporated IAVMP message (i.e., describe the specific negative impact the IAVMP message incorporation would have on the system operation).

3.5.6.3 RMF Assess Only

As specified by individual DOs, the contractor shall ensure compliance with the policies and guidance with the RMF Assess Only Process. The contractor shall control and manage change via Change Configuration and Release Management and an established Configuration Control Board (CCB) to include members of the Government for oversight management. RMF Assess Only formalizes the configuration management process and provides a mechanism to record, review, and approve these changes. IT below system level is assessed for the purpose of being accepted and connected into an existing authorized computing environment. The contractor shall provide all applicable information required to conduct the RMF Assess Only assessments.

3.5.6.4 HBSS

As specified by individual DOs, HBSS compatibility and compliance shall be established for any system that touches the Army Network directly or indirectly, or has the capability to connect, providing network administrators and security personnel with mechanisms to prevent, detect, track, report, and remediate malicious computer-related activities and incidents across all DOD networks and information systems IAW the JTF-GNO released CTO 07-12 (HBSS) mandating the deployment of HBSS on all Component Command, Service and Agency networks within DOD. All HBSS compliance and guidance will be coordinated through PEO STRI’s CIO Systems Engineering Office (SEO).

3.5.6.5 Spectrum Management

As specified by individual DOs, the contractor shall ensure compliance with the policies and procedures for the Army Frequency Allocation to Equipment (Joint/Frequency -12) Process as described in AR 5-12, Chapter 4 for any system that operates in an electromagnetic spectrum. The contractor shall assist in obtaining an approved DD Form 1494, Application for Frequency Allocation, and ensure the equipment can operate in spectrum bands per the national and international tables of spectrum allocation. The contractor shall provide Spectrum Supportability Risk Assessments, which identify regulatory, operational, technical spectrum supportability issues and provide mitigation measures. The contractor shall integrate existing Army approved

20 July 2018

Distribution C – Authorized to U.S. Government agencies and their contractors in support of this spectrum/electromagnetic compatibility hardware and software tools into system procurements whenever possible. All coordination with the Army Spectrum Management Office will be conducted through PEO STRI’s CIO SEO.

3.5.6.6 IA Contractor Training and Certification

As specified by individual DOs, the contractor shall ensure personnel accessing information systems have the proper and current IA certification to perform IA functions in accordance with DoD 8570.01-M, IA Workforce Improvement Program. The contractor shall meet the applicable IA certification requirements, including:

a. DOD-approved IA workforce certifications appropriate for each category and level as listed in the current version of DoD 8570.01-M; and,

b. Appropriate operating system certification for IA technical positions as required by

DoD 8570.01-M.

Upon request by the Government, the contractor shall provide documentation supporting the IA certification status of personnel performing IA functions.

Contractor personnel who do not have proper and current certifications shall be denied access to DOD information systems for the purpose of performing IA functions.

3.5.6.7 Security Engineering

The contractor shall ensure that system security engineering processes are integrated, aligned to, and adequately documented in the system engineering process, and are executed with sufficient rigor to ensure required CS controls are implemented, which culminates in the lowest level of residual risk to system operation. Before software development, all CS and CS-enabled products shall be configured IAW Defense Information Systems Agency (DISA) Security Implementation Specifications and Guides.

Examples of such specifications include the STIG, the Security Content Automation Protocol, Security Checklist, and Security Recommendation Guides.

3.5.7 Software Engineering

As specified by individual DOs, the contractor shall develop the system software and firmware and shall follow the contractor’s organizational software development practices.

The contractor shall provide evidence that the producing software development organizations have software management and development processes documented.