RFP_LTRaC-MAC2_SectionJ-Attach-1_SOW_18Dec2023.pdf

SOW-2024-002

18 December 2023

Version 1.0

APPROVED FOR PUBLIC RELEASE

Statement of Work (SOW) for the

Live Training, Ranges, and Combat Training Centers (LTRaC)

Indefinite Delivery / Indefinite Quantity (ID/IQ)

Multiple Award Contract (MAC) 2

U.S. Army Program Executive Office for

Simulation, Training and Instrumentation (PEO STRI)

12211 Science Drive

Orlando, FL 32826-3276

Approved by:

Product Manager Tactical Training Systems

December 18, 2023

And

Product Manager Combat Training Instrumentation System December 18, 2023

Version 1.0 ii

REVISION LOG

Date Version Author Section Revision Description

18 DEC 23 1.0 Stinefast All Initial Release

Version 1.0 iii

TABLE OF CONTENTS

1 Scope

1.1 LTRaC Introduction

1.2 Background

1.3 MAC 2 Scope

2 Applicable Documents

2.1 Department of Defense Standards

2.2 Availability of Department of Defense Standards

2.3 Department of Defense Directives

2.4 Availability of Department of Defense Directives

2.5 Department of Defense Instructions

2.6 Availability of Department of Defense Instructions

2.7 Department of Defense Manuals

2.8 Availability of Department of Defense Manuals

2.9 Other Government Documents, Drawings, and Publications

2.10 Availability of Other Government Documents and Publications

3 Requirements

3.1 Program Management

3.1.1 Integrated Product Team (IPT)

3.1.2 Contracting Invoice and Payment

3.1.3 Program Schedule

3.1.4 Program Reviews

3.1.4.1 Start of Work / Post Award Meetings

3.1.4.2 Program Management Reviews (PMR)

3.1.4.3 Technical Design Reviews (TDR)

3.1.4.4 Technical Interchange Meetings (TIM)

3.1.5 Risk Management

3.1.6 Associate Contractor Agreements (ACA)

3.1.7 Subcontractor Management

3.1.8 Data Rights

3.1.9 Computer Hardware, Enterprise Software and Solutions (CHESS)

3.1.10 Transition Support

3.1.11 Live Training Transformation (LT2) Synchronization

3.1.12 Government Furnished Property / Contractor Acquired Property (GFP /

CAP)

3.1.13 Counterfeit Risk Management (CRM) Program

3.1.14 Quality Control Plan (QCP)

3.2 Systems Engineering

3.2.1 Product Continuous Technology Refreshment (CTR), Obsolescence, Concurrency, Upgrades and Disposal

3.2.2 Hardware Engineering

3.2.3 Hardware Test Engineering

3.2.4 System Integration

3.2.5 Software Engineering

3.2.6 System Safety Program

Version 1.0 iv

3.2.7 Supportability Engineering

3.2.8 Quality Engineering

3.2.9 Reliability and Maintainability (R&M) Engineering Program

3.2.10 Producibility Engineering Program

3.2.11 Manpower and Personnel Integration (MANPRINT)

3.2.12 Interface Management

3.2.13 Product Definition Data

3.3 Cybersecurity

3.3.1 Information System (IS) Security

3.3.2 Cybersecurity Training

3.4 Logistics

3.4.1 Supportability Analysis and Logistics Product Data

3.4.2 Technical Publications

3.4.2.1 Commercial-Off-the-Shelf Manuals

3.4.2.2 Publications In Process Reviews (IPRs)

3.4.2.3 Publications Validation / Verification

3.4.3 New Equipment Training (NET)

3.4.3.1 NET Verification

3.4.4 Interim Contractor Support (ICS)

3.4.4.1 ICS Engineering Services

3.4.4.2 ICS Transition Planning

3.4.4.3 Transition to Life Cycle Contractor Support

3.4.5 Item Unique Identification (IUID)

3.4.6 Diminishing Manufacturing Sources and Material Shortages (DMSMS) / Obsolescence Management

3.5 Operations Security (OPSEC) Program

3.5.1 Requirements for OPSEC Training

3.5.2 Antiterrorism Threat (AT) Awareness Level 1 Training

3.5.3 AT Awareness Training for U.S. Based Contractor Personnel Traveling Overseas

3.5.4 Access and General Protection Policy Procedures

3.5.5 Army Training Certification Tracking System (ATCTS) Registration for Contractor Employees Who Require Access to Government Information Systems

3.5.6 Cybersecurity / Information Technology (IT) Training

3.5.7 Cybersecurity / IT Certification

3.5.8 Threat Awareness Reporting Program (TARP)

3.5.9 Credentialing

3.5.10 iWATCH Training

3.5.11 Performance or Delivery in a Foreign Country

3.5.12 Handling or Access to Classified Information

3.6 Contract Data Requirements List (CDRL)

3.7 Disclosure of Information

3.8 Regulation and Policy Updates

Version 1.0

STATEMENT OF WORK

FOR THE

LIVE TRAINING, RANGES, AND COMBAT TRAINING CENTERS (LTRaC)

INDEFINITE DELIVERY / INDEFINITE QUANTITY (ID/IQ)

MULTIPLE AWARD CONTRACT (MAC) 2

1 Scope

1.1 LTRaC Introduction

This SOW is for the MAC 2 contract vehicle which is one of three contract vehicles under the larger LTRaC umbrella. The objective of LTRaC is to establish a consolidated contracting approach for range and instrumentation efforts within the live training domain. It will provide maximum competition while ensuring streamlined Delivery Order (DO) awards. This will provide the Department of Defense (DoD) with the ability to rapidly deliver new and upgraded capabilities to the nation’s warfighters. LTRaC will enable Project Manager Training Devices (PM TRADE) and other DoD organizations to perform tasks such as trade studies, analysis and forecasting, data collection, design, development, impact assessment, information assurance, procurement, integration, installation, testing, system training, documentation, logistics support, and disposal. Individual program efforts will define the detailed requirements on the DO level.

The programs included, but not limited to, under this contract are:

• Future Army System of Integrated Targets (FASIT)

• Digital Range Training System (DRTS)

• Combat Training Center – Instrumentation System (CTC-IS)

• Homestation Instrumentation Training System (HITS)

• Joint Pacific Multinational Readiness Capability – Instrumentation System

(JPMRC-IS)

• Synthetic Training Environment – Live Training Systems (STE-LTS)

• Marine Corps Live Training Efforts

All efforts performed under this contract may be required, determined by each DO, to be synchronized with the previously established Live Training Transformation (LT2) processes and standards, which are available at https://www.lt2portal.mil/Home.aspx.

1.2 Background

PM TRADE is the Army's solution provider for live instrumented training systems.

PM TRADE's mission is to develop, acquire, field, and sustain a family of interoperable live training solutions for use at Homestations, CTCs, institutions, and deployed sites to improve Warfighter readiness. By managing the acquisition of training systems to meet the user's requirements, the goal is to deliver the systems https://www.lt2portal.mil/Home.aspx

Version 1.0 on schedule and within cost and to provide life cycle management to ensure the best value products for the Army and external customers.

PM TRADE envisions that LTRaC will support the evolution of live training systems by leveraging the following initiatives and technical concepts:

• LT2 methodology

• Architectural initiatives o Common Training Instrumentation Architecture (CTIA) o FASIT o Live Training Engagement Composition (LTEC) o Future LT2 Architectures

• Government Furnished Information (GFI) software, build to print drawings and manuals via the LT2 Portal or via other means, as necessary.

• Product sustainment (synchronization with PEO STRI Life Cycle Contractor Support (LCCS))

• Reliability, Availability and Maintainability (RAM) assessment for spare listing and support management

1.3 MAC 2 Scope

This MAC will be a Small Business Set Aside and will consist of less-complex / lower risk efforts (limited to minimal sub-systems with no complex interface(s) or dependencies to other subsystems) for the CTC-IS, DRTS (Tier 1), FASIT, HITS, JPMRC, and STE-LTS instrumentation efforts. These efforts may include new fieldings, Continuous Technology Refreshments (CTR) / modification / modernization of existing instrumentation sub-systems and delivery of new sub-system capabilities. Tasks under this MAC may include studies, analysis, design, development, prototyping, procurement, production, integration, testing, fielding, documentation, training, sustainment, and disposal of live-fire training systems that are within the Continental United States (CONUS) and Outside the Continental United States (OCONUS).

MAC 2 will include, but is not limited to, the work previously performed under the Targetry Range Automated Control and Recording (TRACR) Plus and Army Combat Training Instrumentation Contract (ARCTIC) contracts. The previous work includes the following:

TRACR Plus - New IT hardware installations and CTRs of FASIT ranges, from small lane-based ranges with a single computer system to more complex maneuver ranges utilizing multiple computers with after action review capabilities and new / CTR of the Location of Miss and Hit (LOMAH) systems.

ARCTIC - The procurement and delivery of material and equipment in support of total lifecycle support for anticipated lifecycle upgrades including material / hardware equipment, with related integration, installation, and testing.

Version 1.0

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 SOW shall be the governing requirement.

2.1 Department of Defense Standards

MIL-STD-882E System Safety

MIL-STD-31000B Technical Data Packages

MIL-STD-40051-2B Preparation of Digital Technical Information for Page-Based Technical Manuals

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

2.2 Availability of Department of Defense Standards

Copies are available at URL: http://quicksearch.dla.mil/qsSearch.aspx.

2.3 Department of Defense Directives

DoD 8570.01-M Information Assurance Workforce Improvement Program

DoDD 8570.01 Information Assurance Training, Certification and Workforce Management

DoD 5220.31 National Industrial Security Program

2.4 Availability of Department of Defense Directives

Copies are available at URL: https://www.esd.whs.mil/Directives/issuances/dodd/

2.5 Department of Defense Instructions

DoDI 8500.01 Cybersecurity

DoDI 8510.01 Risk Management Framework for DoD Systems

DoDI 8582.01 Security of Non-DoD Information Systems Processing Unclassified Nonpublic DoD Information

2.6 Availability of Department of Defense Instructions

Copies are available at URL: https://www.esd.whs.mil/Directives/issuances/dodi/

2.7 Department of Defense Manuals

DoDM 5200.01 DoD Information Security Program (All Volumes)

2.8 Availability of Department of Defense Manuals

http://quicksearch.dla.mil/qsSearch.aspx https://www.esd.whs.mil/Directives/issuances/dodd/ file:///C:/Users/alexander.j.stinefas/Downloads/%20https:/www.esd.whs.mil/Directives/issuances/dodi

Version 1.0

Copies are available at URL: https://www.esd.whs.mil/Directives/issuances/dodm/

2.9 Other Government Documents, Drawings, and Publications

LT2-TRADE-PLN-000384 LT2 Consolidated Product-Line Management (CPM) Operations Guide (https://www.lt2portal.mil/Home.aspx)

Army Directive 2014-05 Policy and Implementation Procedures for Common Access Card Credentialing and Installation Access for Uncleared Contractors

AR 25-2 Army Cybersecurity

AR 190-13 The Army Physical Security Program

AR 380-5 Army Information Security Program

AR 381-12 Threat Awareness and Reporting Program

AR 525-13 Antiterrorism

AR 530-1 Operations Security

AR 700-145 Item Unique Identification

CNSSI 1253 Security Categorization and Control Selection for National Security Systems

FAR Federal Acquisition Regulation (https://www.acquisition.gov/browse/index/far)

DFARS Defense Federal Acquisition Regulation Supplement (https://www.acquisition.gov/dfars)

GEIA Handbook 0007 Logistics Product Data Handbook

GEIA STD 0007 Logistics Product Data

MIL-PRF-32216 Evaluation of Commercial Off-the-Shelf Manuals and Preparation of Supplemental Data

NIST SP 800-53 National Institute of Standards and Technology (NIST) Special Publication (SP) 800-53: Security and Privacy Controls for Federal Information Systems and Organizations

STIGs Security Technical Implementation Guides (https://public.cyber.mil/stigs/)

ANSI/TA-STD-0016 Preparing a Diminishing Manufacturing Sources and Material Shortages (DMSMS) Management Plan

TA-HB-0007-1 Logistics Product Data Reports Handbook

Copies are available at URL http://apd.army.mil/doctrine/ and http://quicksearch.dla.mil/qsSearch.aspx.

2.10 Availability of Other Government Documents and Publications file:///C:/Users/alexander.j.stinefas/Downloads/%20https:/www.esd.whs.mil/Directives/issuances/dodm https://www.lt2portal.mil/Home.aspx https://www.acquisition.gov/browse/index/far https://www.acquisition.gov/dfars https://public.cyber.mil/stigs/ http://apd.army.mil/doctrine/ http://quicksearch.dla.mil/qsSearch.aspx

Version 1.0

Copies of the documents are available from ACC-Orlando, 12211 Science Dr., Orlando, FL 32826.

Version 1.0

3 Requirements

The requirements defined herein shall form the basis for all work that shall be performed as part of the Government issued DOs under LTRaC’s MAC 2 for the studies, analysis, design, development, prototyping, procurement, production, integration, testing, fielding, documentation, training, contractor support, sustainment, and disposal of live-fire training systems.

3.1 Program Management

The contractor shall provide overall program management and administrative support to ensure the requirements of the base contract and DOs are met. The contractor shall monitor and track key cost, schedule, performance, supportability metrics, and risks monthly and notify the Government of any issues and concerns that arise. The contractor shall track and maintain resources to ensure overall programmatic performance.

3.1.1 Integrated Product Team (IPT)

As specified by the individual DO, the contractor shall establish IPTs with their Government counterparts. The contractor shall support IPT meetings on a pre-determined frequency with all IPT members. The contractor shall facilitate Government insight into contract activities and establish working relationships with Government personnel that will enable continuing insight into all contract activities.

3.1.2 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 DO line item and sub-line item. The contractor shall document and track to levels which represent how they plan to accomplish the entire contract work’s scope, and which are consistent with internal organizations and processes.

These documents shall serve as the framework for contract planning, budgeting, and reporting of cost and schedule statuses. The contractor shall identify major elements of subcontracted work on their invoices.

3.1.3 Program Schedule

As specified by the individual DO, the contractor shall develop, manage to, update, and maintain an Integrated Master Plan (IMP) / Integrated Master Schedule (IMS).

The IMP / IMS shall show planned efforts to achieve each significant accomplishment and event relating to the effort. The schedule shall contain the planned events and milestones, accomplishments, exit criteria, dependencies, and activities from contract award to the completion of the contract. The contractor shall quantify risk in hours, days, or weeks of delay and provide the most likely duration for each IMP / IMS activity and event.

3.1.4 Program Reviews

Version 1.0

As specified by the individual DO, the contractor shall conduct and participate in program reviews. The reviews shall provide a forum for IPT members to clarify development, integration, testing, logistics, and management issues. The contractor shall document action items, coordinate resolutions, and track action items until closure. The contractor shall record and provide to the Government, meeting minutes within two business days of the completion of program reviews. At a minimum, the contractor shall ensure all meeting minutes include a list of attendees, key topics of discussion, and action items.

3.1.4.1 Start of Work / Post Award Meetings

As specified by the individual DO, the contractor shall host a Start of Work / Post Award meeting either virtually or at the contractor’s facility after a DO award. The Start of Work meeting shall be limited to the contractor’s key team members and shall be no more than two days in length. The contractor shall introduce key participants with emphasis on top level management of the program, identify points of contact, discuss the contractor’s understanding of the scope of work, agree on metrics that will be used as management indicators, identify the contractor’s partnering approach, and any contract concerns or issues.

3.1.4.2 Program Management Reviews (PMR)

As specified by the individual DO, the contractor shall conduct PMRs to provide the Government a high-level status update of the effort. These reviews shall include a review of completed activities; management issues; program risks; and cost, schedule, and performance metrics. The contractor shall provide visibility into the progress, performance, and status of major subcontractor and subcontracting efforts.

3.1.4.3 Technical Design Reviews (TDR)

As specified by the individual DO, the contractor shall conduct specific design reviews to include Systems Requirements Review (SRR), Preliminary Design Review (PDR), Critical Design Review (CDR), and Technical Design Review (TDR).

Reviews shall be driven by technical issues, challenges, and integration efforts. The reviews shall be a formal technical assessment of the basic design approach, the allocated baseline, and changes made to the allocated baseline. The reviews shall cover the progress and technical adequacy of the selected design approach. The reviews shall allow the Government to evaluate the technical risk associated with the selected design approach. The reviews shall include a subsystem block and functional diagram, design standards and logistic considerations (including training and manuals), and interference analysis.

3.1.4.4 Technical Interchange Meetings (TIM)

As specified by the individual DO, the contractor shall support TIMs. TIMs shall address specific topics or issues, address status of development or test activities

Version 1.0 between management reviews or coordinate and provide guidance for engineering / logistical data or technical publications.

3.1.5 Risk Management

As specified by the individual DO, the contractor shall conduct risk management to systematically control the uncertainty in the project’s ability to meet cost, schedule, and performance objectives. The contractor shall conduct that part of risk management that directly impacts the technical effort and involves risk management preparation, risk identification, risk assessment, risk-handling option assessment, risk analysis, risk mitigation and risk control, including but not limited to scheduling of manpower requirements if more than one DO is awarded. The contractor shall cover risk management to product requirement objectives at all program and technical reviews, and at any time the contractor identifies a potential impact to cost, schedule, or performance. The contractor shall use their internal risk management tools to perform risk management. The contractor shall provide Government insight into the contractor’s tools, assessment, mitigation, and control techniques.

3.1.6 Associate Contractor Agreements (ACA)

As specified by the individual DO, the contractor shall implement ACAs for exchanging data, accessing, and using third party software and equipment, receiving technical support, working interface issues, transitioning to LCCS, and agreeing on equipment use and time. The contractor shall ensure ACAs achieve interoperability and common component goals, as applicable.

3.1.7 Subcontractor Management

The contractor shall ensure the requirements of this contract and subsequent DOs are applied to all subcontracts and associate contracts. The contractor shall integrate subcontractors into program IPTs.

3.1.8 Data Rights

The Government desires Government Purpose Data Rights for technical data and documentation applicable to both software and hardware, so that the Government can maintain and modify the system(s) using Government personnel and third-party contractors. The contractor shall make a willful attempt to analyze feasible non-proprietary solutions and incorporate them, when applicable for each individual DO.

This includes, but is not limited to, software rights, data, source codes, drawings, warranties, and integration efforts. The contractor shall inform the Government if the proposed data rights prohibit the Government from:

• Using, maintaining, modifying, reproducing, releasing, performing, displaying, or disclosing technical data within the Government without restriction

• Releasing or disclosing technical data outside the Government and authorizing persons to whom releasing, or disclosure has been made to use, Version 1.0 maintain, modify, reproduce, release, perform, display, or disclose that data for United States Government purposes

• Maintaining, repairing, modifying, and upgrading the system using Government personnel and other Government contractors

• Competing future requirements, maintenance, repair, modifications, and upgrades

3.1.9 Computer Hardware, Enterprise Software and Solutions (CHESS)

The contractor shall comply with the Army’s CHESS program. Under PEO Enterprise Information Systems (EIS), CHESS is the mandatory source for commercial IT purchases. CHESS contracts provide IT products and services that comply with Network Enterprise Technology Command (NETCOM), Army, and DoD policy and standards. Purchasers of commercial hardware and software must satisfy their IT requirements by utilizing CHESS contracts and DoD Enterprise Software Initiative agreements first, regardless of dollar value. Any purchase made outside of CHESS contracts requires a waiver. A complete list of CHESS contracts and the on-line waiver process can be found at https://chess.army.mil.

3.1.10 Transition Support

As specified by the individual DO, the contractor shall synchronize with the PEO STRI LCCS contractor for the bi-directional communication regarding the DO components, subsystems, and systems. The contractor shall provide the applicable System Support Package (SSP), transitional training, and transition support to the LCCS contractor.

3.1.11 Live Training Transformation (LT2) Synchronization

As specified by the individual DO, the contractor shall implement and sustain inherent processes and oversight to coordinate and synchronize the activities described in this SOW with the overarching LT2 construct and implementation (as described in the LT2 Operations Guide) to minimize duplication of efforts and ensure common component integrity is maintained. The contractor shall monitor LT2 requirements and framework as they mature. The contractor shall participate in the Core Asset Working Group (CAWG) meetings and support affiliated studies, tasks, and analyses. The contractor shall work with the Government and the CPM Plus contractor to ensure the maximum utilization of LT2 common components.

3.1.12 Government Furnished Property / Contractor Acquired Property (GFP / CAP)

As specified by the individual DO, the contractor shall have a property management plan that addresses a system of internal controls to manage (control, use, preserve, protect, repair, and maintain) Government Furnished Property and Contractor Acquired Property in its possession. The contractor shall maintain the equipment in the same functional and physical state as received except for normal wear and tear.

The contractor shall initiate and maintain processes, systems, procedures, records, https://chess.army.mil/

Version 1.0 and methodologies necessary for effective and efficient control of Government property. The contractor shall disclose any significant changes to its property management system to the Property Administrator prior to implementation of the changes. The contractor shall establish and implement property management plans, systems, and procedures at the contract, program, site, or entity level to enable the oversight of GFP / CAP acquisition, receipt, documentation, physical inventory, any subcontractor associated control, utilization, associated maintenance, and property close out. The contractor shall submit annual inventory reports to the Government.

The contractor may employ customary commercial practices, Voluntary Consensus Standards (VCS), or Industry-Leading Practices (ILPs) and standards that provide effective and efficient Government property management that is necessary and appropriate for the performance of this contract (except where inconsistent with law or regulation). The contractor shall establish and maintain procedures necessary to assess its property management system effectiveness and shall perform periodic internal reviews, surveillances, self-assessments, or audits. Significant findings or results of such reviews and audits pertaining to Government property shall be made available to the Property Administrator (Property Management System Analysis).

The Government shall have access to the contractor’s premises and all Government property, at reasonable times, for the purposes of reviewing, inspecting, and evaluating the contractor’s property management plan(s), systems, procedures, records, and supporting documentation that pertain to Government property.

3.1.13 Counterfeit Risk Management (CRM) Program

The contractor shall implement a CRM program to address counterfeit parts and materiel management of the supply chain. The contractor shall use new and authentic materials, commodities, items, assemblies, subassemblies, and components. The contractor shall purchase materials directly from original equipment / component manufacturers, manufacturer authorized / franchised distributors, or authorized aftermarket manufacturers. When requesting a quote, the contractor shall include the company name and location of the source of supply, and a representation that seller is authorized to sell the material. The contractor shall request and obtain access to the Government-Industry Data Exchange Program (GIDEP) (https://www.gidep.org) for both counterfeit prevention and counterfeit notification.

The contractor shall report all counterfeit or suspected counterfeit parts to the Procuring Contracting Officer (PCO) within 5 days and GIDEP no later than 60 days of making that determination. In reporting this to the PCO, the contractor shall also address the impact of this determination on current contract requirements.

3.1.14 Quality Control Plan (QCP)

As specified by individual DOs, the Government is committed to a highly interactive relationship between quality control by the contractor and quality assurance by the Government recipient of services. This relationship will be achieved through an effective Prevention Based Quality Control Program dedicated to ensuring the best https://www.gidep.org/

Version 1.0 possible products and services to end users. The contractor shall provide their final written Quality Assurance Program Plan no later than sixty (60) days after DO award and within ten (10) days of any proposed change to the PCO and Contracting Officer’s Representative (COR).

As specified by individual DOs, the contractor’s quality program shall demonstrate its prevention-based outlook by meeting the objectives stated in the SOW throughout all areas of performance. The contractor shall specify their responsibilities for management and quality control actions in the QCP to meet the terms of the contract. The QCP, as a minimum, shall address continuous process improvement;

procedures for scheduling, conducting and documentation of inspection; discrepancy identification and correction; corrective action procedures to include procedures for addressing Government discovered non-conformances; procedures for root cause analysis to identify the root cause and root cause corrective action to prevent re-occurrence of discrepancies; procedures for trend analysis; procedures for collecting and addressing customer feedback / complaints.

As specified by individual DOs, the contractor shall provide all reports generated because of the contractor’s quality control efforts within three (3) days of completion.

This shall include any summary information used to track quality control, including any charts / graphs.

As specified by individual DOs, the contractor’s QCP shall be incorporated into and become part of this contract after the plan has been accepted by the PCO. Proposed changes made after PCO acceptance shall be submitted in writing through the COR to the PCO for review and acceptance prior to implementing any revision. The contractor’s QCP shall be maintained throughout the life of the contract and shall include the contractor’s procedures to routinely evaluate the effectiveness of the plan to ensure the contractor is meeting the performance standards and requirements of the DO.

3.2 Systems Engineering

The contractor shall provide the requisite technical and programmatic support to complete the required tasks of the individual DOs. These tasks shall encompass the efforts associated with the software / hardware development, dissemination, engineering, management, maintenance, CTR, technology insertion, obsolescence, concurrency, upgrades and disposal of the hardware components, and documentation. These tasks shall also include the work efforts associated with the engineering, management, and tracking of fielded products, services, and core assets.

3.2.1 Product Continuous Technology Refreshment (CTR), Obsolescence, Concurrency, Upgrades and Disposal

As specified by individual DOs, the contractor shall conduct engineering analyses to establish quantitative and qualitative supportability design guidelines. The contractor shall conduct trade studies, evaluate design and support alternatives, and establish system supportability preliminary design configurations consistent with system

Version 1.0 readiness, availability, and life cycle cost goals. The contractor shall review all Commercial Off-the-Shelf (COTS) manuals to ensure changes, updates, revisions, or supplementation are completed and address the components being installed In Accordance With (IAW) MIL-PRF-32216. The contractor shall perform the necessary tasks and activities for logistics, fielding, and sustainment. 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 delivery orders with respect to logistics, support resources, publications, training, fielding and sustainment:

Requirements Analysis Publication In Process Reviews

Accounting Requirements Codes Reliability Analyses

Authentication Repair Level Analyses

Baseline Drawing Revisions Repair Procedures

Commercial Off The Shelf Publications SCORM Compliance

Common and Bulk Items Serial Numbers

Course Conduct Information Site Support

Diagnostic Procedures Software Support Environment

Engineering Services Source, Maintenance, and Recovery Codes

Facility Analyses and Summary Spares and Support and Test Equipment

Fielding Plans Supply Support

Initial Spares and Repair Parts Lists Support Analyses

Instructional Media Design Support Concepts

Instructional Media Package Supportability Analysis

Instructional Media Requirements Sustainment Transition

Instructional Performance Requirements Technical Publications

Interim Contractor Support Test and Evaluation

Inventory Support Tools and Test Equipment

IUID Marking and Reporting Training and Support

Life Cycle Software Engineering Environment

Training Assessments

Logistics Database Management Training Conduct Support

Logistics Demonstration Training Facility and Equipment

Maintenance Actions Training Products

Maintenance Planning Training Reviews

Manpower, Personnel and Training Training Situation Document

Materiel Component List Training System Support

Parts Management Transition Planning

Pocket Guides Validation

Post Production Support Verification

Provisioning Parts List Warranty Data

3.2.2 Hardware Engineering

Version 1.0

As specified by the individual DO, the contractor shall design, develop, integrate, assemble, and test the system hardware and associated firmware that satisfies the performance and cybersecurity requirements stated in the DO. The contractor shall conduct market surveillance and market investigations to maximize the use of commercial and non-developmental items. The contractor shall apply the systems engineering process during each level of system development (system, subsystem, and component) to add value (additional detail) to the products defined in the prior application of the process. Through each of the design stages, the contractor shall document the information generated in an integrated database.

3.2.3 Hardware Test Engineering

As specified by the individual DO, the contractor shall develop, implement, and maintain a system test process satisfying all test requirements, which is traceable throughout the design process, is integrated with other system engineering requirements, and is disseminated to design personnel and subcontractors. The contractor shall establish controls for ensuring that each subcontractor’s test practices are consistent with overall system requirements. The contractor shall define the means for verifying and validating that the diagnostic capability meets specified requirements, using maintainability demonstrations, test program verification, and other demonstration methods. The contractor shall ensure that as test and evaluation of the system progresses, problems presented by new failure modes, test voids, ambiguities, and test tolerance difficulties are recognized and defined, solutions are traceable to diagnostic hardware and software, and technical publication procedures are updated. The contractor shall define an approach for the analysis of acceptance test and evaluation results to determine how built-in test hardware and software, automated test equipment hardware and firmware, and maintenance documentation performed as a means for satisfying production testing, and meeting test requirements. The contractor shall establish a test program that accomplishes the following:

• Establishment of sufficient, achievable, and affordable diagnostic concept and state-of-the-art testability built-in and off-line test performance requirements.

• Integration of testability into equipment and systems during the design process in coordination with the maintainability design process.

• Evaluation of the extent to which the design meets testability requirements.

• Inclusion of testability in the program review process.

• End-to-end alignment, synchronization, and integration with LT2 test strategy.

3.2.4 System Integration

The contractor shall perform all activities to integrate and assemble the hardware and software to achieve a fully functional system that performs and operates in accordance with the system’s requirements. The contractor shall verify the complete integration of the hardware and software of each subsystem and the overall system through the utilization of formalized test procedures. The contractor shall complete a system level production approval review to demonstrate that the total system has

Version 1.0 been verified to satisfy specification and baseline requirements for each system level, and to confirm readiness for production, distribution, operations, support, training, continuing improvement, and disposal.

3.2.5 Software Engineering

The contractor shall follow the LT2 processes for all software reuse, development, and testing. The contractor shall utilize the LT2 core assets for software to the maximum extent possible and shall use the CAWG when new software is to be developed or utilized.

As specified by the individual DO, the contractor shall design, implement, integrate, test and field system minor or unique software and firmware, and shall follow the contractor’s organizational software development practices. The contractor shall provide sufficient evidence that the producing software development organizations have software management and development processes documented. The contractor shall incorporate features that promote assessment of open-source software products, ease of operation, cybersecurity, ease of software maintenance, ease of future updates and modifications, data void work around, and any smart designs that can justify a reduction in the amount of documentation into the design process. The contractor shall conduct market surveillance and market investigations to maximize the use of open-source software, commercial software, and non-developmental software. The contractor shall employ well-defined security policy models, structured, disciplined, and rigorous hardware and software development techniques, and sound system / security engineering principles. The contractor shall follow formal industry-accepted software development practices that are consistent with at least Level 3 of the Capability Maturity Model Integration for Development

(CMMI-DEV).

3.2.6 System Safety Program

As specified by the individual DO, the contractor shall maintain a safety process to identify, evaluate, and eliminate or control hazards throughout the contract. The contractor shall ensure all hardware, products, and software services are designed to minimize safety and health risks to operators and maintainers in accordance with

MIL-STD-882E.

3.2.7 Supportability Engineering

As specified by the individual DO, the contractor shall conduct engineering analyses to establish quantitative and qualitative supportability guidelines. The contractor shall establish system supportability configurations consistent with system readiness and availability and life cycle cost goals specified in each specific DO. The contractor shall coordinate with existing LCCS using ACAs, develop initial fielding plans for the system and verify that the maintenance actions and support structure are aligned with the maintenance concept.

3.2.8 Quality Engineering

Version 1.0

As specified by the individual DO, the contractor shall establish measurement points that will provide maximum visibility into new and prior processes to assure contractual requirements are being met. The contractor shall select the proper methods to analyze these processes to continuously improve the system. Metrics shall be developed to assist management visibility into an adequate process control system. The contractor shall establish and maintain a computerized discrepancy tracking system with the ability to produce complete permanent records of all discrepancy or database listings. The contractor shall establish a suspense system to ensure timeliness of analysis and corrective action for discrepancies and risk reduction items. All discrepancy corrections shall be documented and entered in an integrated database.

3.2.9 Reliability and Maintainability (R&M) Engineering Program

As specified by the individual DO, the contractor shall establish and maintain active and effective R&M programs that meet program objectives. The R&M programs shall ensure that Commercial Items and Non-Developmental Items to be delivered to the Government because of the required Training Aids, Devices, Simulators and Simulations (TADSS) modifications, meet the R&M requirements specified in the individual DO Specification and the corresponding SOW. The contractor shall include the R&M programs as topics of discussion during scheduled program reviews.

3.2.10 Producibility Engineering Program

As specified by the individual DO, the contractor shall perform production planning to ensure a smooth, timely, and cost-effective initiation of production. Planning tasks shall include those actions required to ensure that the product has stabilized, the manufacturing processes have been proven, and production facilities, equipment, capability, and capacity are in place to support the required delivery schedule.

3.2.11 Manpower and Personnel Integration (MANPRINT)

As specified by the individual DO, the contractor shall conduct a program integrating the activities of the seven domains of MANPRINT to influence design decisions beginning at program conception and continuing through the development and fielding phases. The seven domains are: 1) Manpower, 2) Personnel, 3) Training, 4) Human Factors, 5) System Safety, 6) Health Hazards, and 7) Survivability. The contractor shall track domain issues as an integral part of scheduled program reviews. Objectives shall include balance of system performance and cost of ownership by ensuring that the system design is compatible with the capabilities and limitations of the personnel who will operate and maintain the item as each specific DO requires. Each program shall be coordinated with the training, test, and supportability engineering activities to achieve an integrated effort without duplication.

3.2.12 Interface Management

Version 1.0

As specified by the individual DO, the contractor shall maintain and sustain the Interface Control Documents (ICD) and interface boundaries between all hardware and software configuration items and any interfaces available to outside systems.

These descriptions shall include references to commercial standards, message protocols, and security issues and precautions.

3.2.13 Product Definition Data

As specified by the individual DO, during the systems engineering and design, and in accordance with MIL-STD-31000B, the contractor shall develop, produce, and maintain Product Definition Data (PDD) that accurately depicts the final product. The PDD is the technical description of items adequate for supporting an acquisition strategy, production, engineering, and logistics support. The PDD shall disclose complete design, logistics, manufacturing requirements, and the means of measuring compliance with the requirements. Piece part information (drawings, computer aided design files and meta data) and associated lists shall provide the necessary design, engineering, manufacturing, and quality assurance requirements information necessary to enable the procurement of an interchangeable item that duplicates the physical and performance characteristics of the original product, without additional design engineering effort or recourse to the original design activity.

3.3 Cybersecurity

As specified by the individual DO, the contractor shall integrate cybersecurity into their management processes, document decisions, specify and track cybersecurity requirements, document certification efforts, identify possible solutions, and maintain operational systems security.

The contractor shall leverage the National Information Assurance Partnership (NIAP) and the Common Criteria Evaluation and Validation Scheme (CCEVS) to ensure Defense Information Systems Agency (DISA) approved software and hardware are utilized within the contract’s supported components, services, and assets. The contractor shall also ensure that the products developed and maintained within the development environment are implemented in accordance with DISA Security Technical Implementation Guide (STIG) compliance. The contractor shall deliver upgrades to the system in a configuration that will pass a certification and will not negatively impact the existing accreditation. The contractor shall implement protective measures to address identified vulnerabilities and weaknesses. When classified or controlled information is introduced into an effort, the contractor shall adhere to the provisions within AR 380-5 regarding the classification, transmission, transportation, and safeguarding of this information. The contractor shall integrate protective mechanisms into the system and applications to provide identification and authentication, access control, accountability, availability, confidentiality, privacy, data integrity, and non-repudiation.

The contractor shall ensure prototyping efforts apply the appropriate cybersecurity considerations in the decision-making process. The contractor shall leverage LT2 cybersecurity processes and procedures to the maximum extent possible. The

Version 1.0 contractor shall work with the Government cybersecurity personnel to coordinate a transition to post deployment and production cybersecurity sustainment. The contractor shall maintain cybersecurity compliance up to 30 days of full system acceptance by the Government of each individual program location to minimize the effort required when the cybersecurity responsibility is transitioned to the sustainment contractor.

3.3.1 Information System (IS) Security

The contractor shall consider and integrate a holistic approach to IS security and data security that protects against unauthorized (accidental or intentional) disclosure, modification, or destruction.

• The IS security shall consider the following:

o All hardware and software functions, characteristics, and features o Operational procedures o Accountability procedures o Access controls, remote computers, and terminal facilities o Management constraints

• The security system shall provide an adequate level of protection for the IS and data contained in the IS. An adequate system ensures a security approach commensurate with the risk and magnitude of harm resulting from the loss, misuse, or unauthorized access to or modification of information.

• The IS security system and cybersecurity approach shall include controls that are part of the day-to-day operations of the system, and are compliant with AR 25-2, DoDI 8500.01, DoDI 8510.01, CNSSI 1253, NIST SP 800-53, and DoDI 8582.01. The contractor shall support accreditations under the Risk Management Framework (RMF) IAW 8500.01 and DoDI 8510.01.

3.3.2 Cybersecurity Training

As specified by the individual DO, the contractor shall develop and provide operator and maintenance training with respect to the nature, personnel, and criticality of the protective mechanisms in place to secure the IS assets.

• This shall include the methods, skills, use, and mechanisms to maintain the level of security of the IS.

• The training shall be geared toward the audience and their roles and responsibilities with respect to the system’s operation and maintenance (i.e., system administrator, network administrator, hardware maintenance).

• The contractor shall utilize DoD 8570.01-M as a guide in the development of the cybersecurity training content.

3.4 Logistics

As specified by the individual DO and Contract Data Requirements Lists (CDRL), the contractor shall utilize the latest version of GEIA STD 0007, GEIA Handbook 0007 and TA-HB-0007-1. The contractor shall conduct engineering analysis to establish

Version 1.0 quantitative and qualitative supportability design guidelines. The contractor shall identify the supportability analysis methodology (e.g., simulation, test, demonstration) utilized to perform the analyses and document the results. The contractor shall develop or continue a maintenance concept that consists of two levels: Field and Sustainment. Field maintenance, also known as Unit and Direct Support (DS), consists of onsite preventative maintenance, daily readiness checks and services, adjustments to controls and other maintenance that can be accomplished by the operator or on-site trained technician without the aid of special tools, support equipment, additional training knowledge, or skills. It includes system activation, adjusting and aligning to specific parameters, troubleshooting, removal, and replacement of failed components. Sustainment maintenance, also known as General Support (GS) and depot level, consists of off-site maintenance capabilities conducted at the LCCS contractor facility or a designated contractor facility. It includes the use of designated repair points operated by the LCCS contractor, original equipment manufacturers and vendors, to repair, overhaul, rebuild, replace, or calibrate failed equipment. The contractor’s design shall minimize life cycle costs and maximize life cycle supportability by avoiding the use of proprietary items, recurring fees and maximize system / subsystem commonality. The contractor shall identify all system components subject to life cycle repair or replacement and ensure all components identified match the as built configuration at each fielding location.

3.4.1 Supportability Analysis and Logistics Product Data

As specified by the individual DO, the contractor shall conduct repair analyses, develop diagnostic, preventative maintenance, and repair procedures, conduct facilities analyses, refine hardware and software maintenance and support concepts, and identify support resource requirements including required spares and support equipment. The contractor shall produce a consolidated periodic maintenance plan that addresses all legacy and new instrumentation systems / subsystems (e.g., target lifters, cameras, battle effects, computer hardware, etc.). Using Source Maintenance and Recoverability (SMR) codes, the contractor shall develop an items list identifying which should be repaired, removed / replaced, be discarded and the level of maintenance at which the actions should be performed with the associated cost. The contractor will document all input data, the corresponding value / cost and data source. The contractor shall provide the information required to assist the Government in the development of storage and transportation load plans.

Commercial warranties shall be transferable to a third-party contactor. The contractor shall document and report to the Government:

• Maintenance Allocation Chart

• Failures Modes Effects and Criticality Analysis (FMECA)

• Reliability Centered Maintenance (RCM)

• Maintenance Task Analysis (MTA)

• Provisioning Parts List (PPL)

• Repair Parts and Special Tools List (RPSTL)

• Maintenance Plan Report Indentured Parts List

• Spares and Support Equipment Identification List

Version 1.0

• Support Equipment Tool List

• Bill of Materials

• Periodic Maintenance Plan

• Level of Repair Analysis (LORA)

• Support and Test Equipment

• Manpower, Personnel, and Training

• Inventory Catalog with DA Form 3161 / 2062

• Packaging, Handling, Storage, and Transportation

• Post-Deployment Software Support (PDSS)

• Warranty Information

• Physical Configuration Audit (PCA)

• Logistics Product Data (LPD) Initial Spares

As specified by the individual DO, to reduce cost and…