Attachment 1 - BEST MAC Base SOW.pdf

PEO-STRI- SOW-2022-060

W900KK-23-R-BEST MAC

27 March 2023

DISTRIBUTION STATEMENT A:

Approved for public release; distribution is unlimited.

Statement of Work For

Bridge to Enduring STE TESS Multi-Award Contract (BEST-MAC)

Indefinite Delivery/Indefinite Quantity (ID/IQ) Version 1.2

U.S. Army Program Executive Office for Simulation, Training, and Instrumentation (PEO STRI)

12211 Science Drive Orlando, FL 32826-3276

Yung Doan Systems Engineer, PdM LTS

Paul Smith Chief Engineer, PdM LTS

PM ST PM ST

Robert Jones Logistician, PdM LTS

Brian Frech Product Support Manager, PdM LTS

PM ST PM ST

Dave Brunat Project Officer, PdM LTS

PM ST

Michael T. Powell Product Manager, PdM LTS

PM ST

http://www.peostri.army.mil/apps/

Change History

Revision Date Section Description

1.0 03/03/2023 All Initial Release.

1.1 03/13/2023 Section 2 and 3.7 References documents and CDRLs

1.2 03/27/2023 Section 2.2, 2.4, 3.2.4.1, 3.6, 3.6.9, 3.6.13,3.6.14, 3.7, 3.10

Reference documents, ECP, Logistics, ICS, IUID, DSMSS, CDRL, Counterfeit Management iii

TABLE OF CONTENTS

1.0 SCOPE

1.1 BACKGROUND

1.2 BEST-MAC STRUCTURE

1.2.1 BEST-MAC Lot Structure

2.0 APPLICABLE DOCUMENTS

2.1 DEPARTMENT OF DEFENSE SPECIFICATIONS

2.2 DEPARTMENT OF DEFENSE STANDARDS

2.3 OTHER GOVERNMENT DOCUMENTS, DRAWINGS, AND PUBLICATIONS

2.4 NON-GOVERNMENT STANDARDS AND OTHER PUBLICATIONS

3.0 REQUIREMENTS

3.1 MANAGEMENT, ORGANIZATION AND PROCESSES

3.1.1 Core Asset Evolution

3.1.2 Product Integration, Fielding and Sustainment

3.2 PROGRAM MANAGEMENT

3.2.1 Integrated Product and Process Development (IPPD)

3.2.2 Integrated Master Plan (IMP) and Integrated Master Schedule (IMS)

3.2.3 Earned Value Management (EVM) System

3.2.4 Configuration Management

3.2.5 Risk Management

3.2.6 Associate Contractor Agreements (ACAs)

3.2.7 Meetings and Program Reviews

3.2.8 Subcontractor Management

3.2.9 Cost as an Independent Variable (CAIV)

3.2.10 Computer Hardware, Enterprise Software Solutions (CHESS) Program

3.2.11 Government Purpose Rights (GPRs)

3.3 SYSTEMS ENGINEERING

3.3.1 Software Engineering

3.3.2 Hardware Engineering

3.3.3 Test Engineering

3.3.4 Hardware and Software Integration

3.3.5 Technology Insertion

3.3.6 System Safety Program

3.3.7 Product Definition Data (PDD)

3.4 SUPPORTABILITY ENGINEERING

3.4.1 Reliability Engineering

3.4.2 Maintainability Engineering

3.4.3 Quality Engineering

3.4.4 Producibility Engineering

3.4.5 Manpower and Personnel Integration (MANPRINT)

3.4.6 Value Engineering

3.5 CYBERSECURITY

3.5.1 Anti-Terrorism (AT) Level 1 Training

3.5.2 iWATCH Training

3.5.3 Protection Policy & Procedures

3.5.4 Access to Government Information Systems

3.5.5 Operations Security (OPSEC) Plan

3.5.6 Information Assurance/Information Technology (IA/IT) Training iv

3.5.7 Spectrum Management

3.6 LOGISTICS

3.6.1 Contractor Support

3.6.2 Disclosure of Information

3.6.3 Weapon and Ammunition Storage and Transportation

3.6.4 Supportability Analysis and Logistics Product Data

3.6.5 Initial Spares

3.6.6 Publications Validation/Verification

3.6.7 New Equipment Training (NET)

3.6.8 NET Verification

3.6.9 Interim Contractor Support (ICS)

3.6.10 ICS Engineering Services

3.6.11 ICS Transition Planning

3.6.12 Transition to Life Cycle Contractor Support (LCCS)

3.6.13 Item Unique Identification (IUID)

3.6.14 Diminishing Manufacturing Sources and Material Shortages DMSMS/Obsolescence

Management

3.7 CONTRACT DATA REQUIREMENTS LIST (CDRL)

3.8 DISCLOSURE OF INFORMATION

3.9 MARKING

3.10 COUNTERFEIT MANAGEMENT

3.10.1 Counterfeit Risk Management (CRM) Program

3.10.2 Reporting Counterfeit or Suspected Counterfeit Parts

APPENDIX A - ACRONYM LIST

27 March 2023

Statement of Work For

Bridge to Enduring STE TESS Multi-Award Contract (BEST-MAC) Indefinite Delivery/Indefinite Quantity (ID/IQ)

1.0 Scope

This Statement of Work (SOW) defines the work required to be performed for the Project Manager Soldier Training’s (PM ST) Bridge to Enduring STE TESS Multi-Award Contract (BEST-MAC). The MAC will enable PM ST and other Department of Defense (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. This SOW defines the general tasks to be performed under the BEST-MAC in support of live training requirements. Individual program efforts will define the detailed requirements on the Delivery Order (DO) level.

The existing TESS products included, but not limited to, under this MAC are:

• Individual Weapons Systems (IWS)

• Tactical Vehicle Systems (TVS)

• Combat Vehicle Systems (CVTESS)

• Shoulder Launched Munitions (SLM)

• Controller Devices (UCD)

• Ancillary equipment associated with each of the product lines

1.1 Background

PM ST is the Army's solution provider for live instrumented training systems. PM ST's mission is to develop, acquire, field and sustain a family of interoperable live training solutions for use at Home Station, 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 on schedule and within cost and to provide life cycle management to ensure the best value products for the Army and external customers. The BEST-MAC objective is to modify existing TESS as well as procure new TESS, similar to existing TESS to meet the Army’s evolving training strategy. The MAC will provide maximum competition while ensuring streamlined DO awards. This will provide the DoD with the ability to rapidly deliver upgraded and/or new capabilities to the nation’s warfighters.

PM ST envisions that BEST-MAC will support the evolution of live training systems by leveraging the following initiatives and technical concepts:

- LT2 methodology

- Architectural initiatives

• Common Training Instrumentation Architecture (CTIA)

• Live Training Engagement Composition (LTEC)

• Future LT2 Architectures

• Government Furnished Information (GFI) via the LT2 Portal or via other

27 March 2023 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.2 BEST-MAC Structure

1.2.1 BEST-MAC Lot Structure

The primary focus of this contract will be hardware and software centric efforts. The BEST-MAC contract is broken out into two Lots.

Lot 1 - Modify existing TESS to extend product life and meet the Army’s evolving requirements. The focus of Lot 1 is to provide Service Life Extension Programs (SLEP) to existing TESS. The scope of this Lot may include up to 210,000 systems over the 10 year life of the contract. The number of domestic/US Army TESS to undergo a SLEP in any given year is expected to be in the thousands. It is estimated that SLEP funding will exceed $300M spread over 10 years in this Lot. The intent is to SLEP IWS and SLM initially to ensure compatibility, commonality, and interoperability with current TESS and the platforms each system is required to support, throughout the acquisition life cycle.

The weapon platform managers continue to modify existing systems and field new variants. This requires TESS to make modifications to maintain weapon platform relevancy. The projected modification effort within this Lot is estimated to be four updates to LTEC and five vehicle kit modifications. In addition, modifications are required to interoperate with STE LTS products. This work will be defined as the STE Live product lines evolve.

The intent is to modify the existing fleet to extend the product life, adapt to evolving weapon platforms and to interoperate with STE LTS products for a minimum of 10 years.

The TESS will be required to be compliant with the existing and new Government provided requirements / performance specifications. Partner nation requirements cannot be projected but may be additive to this requirement.

Lot 2 – Procure new TESS similar to existing TESS in the field today. Lot 2 will focus on Army Force Structure changes and modernization of the current TESS. This Lot is required to procure new systems similar to the current TESS systems in the field today.

Based on historical data, it is estimated that there will be three changes to Force Structure requiring additional TESS. These new system projections include all five TESS product lines. In addition, it is estimated that there will be at least three new weapon platforms requiring new TESS. These new weapon systems will all have fire control systems that require an interface with TESS. They will also have new weapon systems that must be replicated. This Lot will also address modernization of current TESS through procurement instead of SLEP. This lot may also be used to fulfill selected requirements for Foreign Military Sales (FMS). These procurements could be variants of existing TESS or new systems to interoperate with new weapon platforms and STE LTS products. These procurements may incorporate Interim Contract Support (ICS) until

27 March 2023 transition to Training Support Operations (TSO).

2.0 Applicable Documents

The following documents form a part of this SOW to the extent specified herein:

2.1 Department of Defense Specifications

MIL-PRF-32216B Evaluation of Commercial Off-the-Shelf (COTS) Manuals and Preparation of Supplemental Data

Copies are available on the WWW at URL: https://quicksearch.dla.mil/qsSearch.aspx

2.2 Department of Defense Standards

The following specifications, standards, and handbooks form a part of this document to the extent specified herein.

MIL-STD-130N Identification Marking of U.S. Military Property MIL-STD-882E System Safety MIL-STD-31000B Technical Data Packages MIL-STD-40051-2D Preparation of Digital Technical Information for Page-Based

Technical Manuals (TMs)

Copies are available on the WWW at URL: https://quicksearch.dla.mil/qsSearch.aspx

2.3 Other Government Documents, Drawings, and Publications

AR 5-12 Army Use of the Electromagnetic Spectrum AR 25-2 Army Cyber Security AR 381-12 Threat Awareness and Reporting Program AR 525-13 Antiterrorism AR 530-1 Operations Security AR 700-145 Item Unique Identitification AR 702-20 Counterfeit Risk Management Product Assurance Copies are available on the WWW at URL: https://armypubs.army.mil DoD 5100.76-M Physical Security of Sensitive Conventional Arms, Ammunition, and Explosives (AA&E) DoD 5220.22-M National Industrial Security Program Operating Manual

(NISPOM)

DoDD 5230.24 Distribution Statements on DoD Technical Information DoDI 4140.67 DoD Counterfeit Policy DoDI 5200.48 Controlled Unclassified Information (CUI) DoDD 8570.01 Information Assurance Training, Certification and Workforce

Management DoDD 8140.01 CyberSpace Workforce Management https://quicksearch.dla.mil/qsSearch.aspx https://quicksearch.dla.mil/qsSearch.aspx

27 March 2023

Copies are available on the WWW at URL: https://www.esd.whs.mil/DD/

Title 32 CFR Part 2002 Controlled Unclassified Information

(https://www.ecfr.gov/current/title-32/subtitle-B/chapter- XX/part-2002)

DFARS 252.234-7001 Notice of Earned Value Management System (https://www.acquisition.gov/dfars)

DFARS 252.234-7002 Earned Value Management System (https://www.acquisition.gov/dfars)

DFARS 252.211-7003 Item Unique Identification and Valuation (http://www.acq.osd.mil/dpap/pdi/uid/index.html)

LT2-TRADE-PLAN-2013-00009 LT2 Product Line Configuration Management Operational Procedures Guide (www.lt2portal.mil)

LT2-TRADE-PLN-000384 LT2 Consolidated Product Line Management (CPM) Operations Guide (www.lt2portal.mil)

2.4 Non-Government Standards and Other Publications

ANSI/EIA-748 Standard for Earned Value Management Systems ANSI/TA-STD-0016 Standard for Preparing a DMSMS Management Plan Copies are available on the WWW at URL http://www.apd.army.mil/ GEIA-STD-0007C Logistics Product Data GEIA-HB-0007B Logistics Product Data Handbook TA-HB-0007-1 Logistics Product Data Reports Handbook Copies are available on the WWW at URL https://www.sae.org/standards/

3.0 Requirements

The requirements defined herein shall form the basis for all work that shall be performed as part of the Government issued delivery orders under the BEST-MAC within Lots.

3.1 Management, Organization and Processes

In support of the BEST MAC, the contractor shall perform programmatic activities, providing for an optimized Product Line (P/L) organizational structure. The contractor’s approach shall ensure efficient processes for the management and oversight of the BEST MAC technical activities including resources utilized across all BEST MAC delivery orders.

The following table provides a representative list of tasks and activities that could be required by specific delivery orders.

Associate Contractor Agreements Interface Management Business Strategy Life Cycle Support Concept of Operations Meetings & Program Reviews Conferences Metrics, Measurement and Tracking https://www.esd.whs.mil/DD/ https://www.govinfo.gov/content/pkg/CFR-2018-title32-vol6/pdf/CFR-2018-title32-vol6-part2002.pdf https://www.ecfr.gov/current/title-32/subtitle-B/chapter-XX/part-2002 https://www.ecfr.gov/current/title-32/subtitle-B/chapter-XX/part-2002 https://www.acquisition.gov/dfars https://www.acquisition.gov/dfars http://www.acq.osd.mil/dpap/pdi/uid/index.html http://www.lt2portal.mil/ http://www.lt2portal.mil/ http://www.apd.army.mil/ https://www.sae.org/standards/

27 March 2023

Configuration Change Management Organizational Planning Configuration Identification Post Award Conference Configuration Management Program Management Configuration Management Planning and Management

Program Management Review

Configuration Status Accounting Requirements Management Configuration Verification and Audit Resource Planning and Management Customer Interface Management Reuse Analysis Data Repository Risk Management Decision Analysis Technical Assessment Design Review Technical Data Management Earned Value Management Technical Interchange Meetings Engineering Change Proposal Technical Planning Facilities Management Technical Reviews Financial Management Technology Forecasting Hardware Audit Test Readiness Review Integrated Baseline Review Training Integrated Master Schedules / Plans Variance / Variance Management Integrated Product Team Management Visitor Support

3.1.1 Core Asset Evolution

The contractor shall perform the necessary tasks and activities to continue the development, evolution, and sustainment of the BEST MAC LT2 Core Assets. All efforts performed under this contract will be synchronized with the previously established Live Training Transformation (LT2) processes and standards. The contractor shall follow the LT2 Product Line Configuration Management Operational Procedures Guide (LT2- TRADE-PLAN-2013-00009) and LT2 Consolidated Product Line Management (CPM) Operations Guide (LT2-TRADE-PLN-000384). The Government will address the specific requirements in each delivery order. The following table provides a representative list of tasks and activities that could be required by specific delivery orders with respect to BEST MAC LTS Core Asset Development & Evolution:

Architecture development P/L Developer Training Architecture evaluation Performance Verification & Validation Architecture validation Quality Assurance Configuration Management Requirement Engineering Decision Analysis Re-Use Analysis Domain Analysis Service/Component Development LT2 Configuration Change Control Technology Insertion LT2 Configuration Identification Test & Verification LT2 Configuration Management Planning Variation Management LT2 Configuration Status Accounting Version Control Obsolescence Management and Planning

27 March 2023

3.1.2 Product Integration, Fielding and Sustainment

The contractor shall perform the necessary tasks and activities for product development integration, prototype production, testing, fielding and sustainment. The Government will address the specific requirements in each delivery order. The following table provides a representative list of tasks and activities that could be required by specific delivery orders with respect to Integration, Fielding and Sustainment:

Assembly Production Code and Unit Test Production Planning Cold Start Test Production Readiness Review Component Testing Prototyping Concept Development Quality Assurance Configuration Management Quality Engineering Cyber Security Reliability Engineering Electromagnetic Environmental Effects Test & Analysis

Requirements Analysis, Management & Traceability

Fabrication Risk Management Framework Testing and Certification

Factory Inspection Safety Assessment Fielding Safety Engineering First Article Test Security Engineering Full Rate Production Software Engineering Functional Analysis Software Integration Government Acceptance Test Spectrum Management Hardware / Software Integration System Demonstration Hardware Engineering System Design Hardware Integration System Engineering Hazards Tracking & Risk Resolution System Integration Health Hazard Assessments System Modification Information Assurance Vulnerability Management

Systems Verification Test

Integrated Testing & Test Planning Test and Inspection Report Low Rate Initial Production (LRIP) Test Discrepancy Management Maintainability Engineering Test Support Manpower and Personnel Integration

(MANPRINT)

Testing & Test Engineering

Operations Security Training Post-Deployment Software Support

(PDSS)

Training Product Verification & Validation

Post-Production Software Support

(PPSS)

Validation Testing

Producibility Engineering Verification Testing Product Definition Data (PDD)

27 March 2023

3.2 Program Management

The contractor shall establish and maintain an integrated program management system, which shall plan, direct, integrate and control the administrative, management, technical, logistical, financial, production and support functions of each specific order. The contractor shall maintain procedures to respond to requirements of Request for Proposals (RFPs) and delivery order modifications. The contractor shall manage work efforts to optimize total product performance, ensure interoperability and common solutions, and minimize total ownership cost.

3.2.1 Integrated Product and Process Development (IPPD)

As specified by individual delivery orders, the contractor shall establish and maintain a process for IPPD and participate in joint Government/contractor Integrated Product Teams (IPT) in a Performance-Based Business Environment to manage and integrate all tasks, activities and data. 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. The contractor shall provide real-time, reliable and user-friendly electronic remote access to all data produced under the contract to enable review of contract status and demonstrate readiness to complete significant events. The contractor shall make available to the Government all technical, cost and schedule data for each specific order of the order IPT. The contractor shall maintain processes that facilitate completion of delivery order.

3.2.2 Integrated Master Plan (IMP) and Integrated Master Schedule (IMS)

As specified by individual delivery orders, the contractor shall develop an IMP and an IMS.

The contractor shall manage to and maintain the IMP and IMS it has developed for each specific order, including appropriate program milestones with corresponding entrance and exit criteria. The IMP and IMS shall include a detailed account of all tasks necessary to accomplish the goals and objectives of each specific delivery order. The contractor shall develop and maintain an Integrated Master Schedule (IMS) by logically networking detailed program activities including synchronization of all active delivery orders. The schedule shall contain the planned events and milestones, accomplishments, exit criteria, 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 IMS activity and event.

3.2.3 Earned Value Management (EVM) System

The contractor shall use EVM System as each specific delivery order defines.

3.2.3.1 Contractor Integrated Performance Management

As specified by individual delivery orders, the contractor shall establish, maintain, and use in the performance of each delivery order, an integrated performance management system. Central to this integrated system shall be a validated Earned Value Management System (EVMS) in accordance with Defense Federal Acquisition Regulation Supplement

27 March 2023

(DFARS) 252.234-7001, DFARS 252.234-7002, 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, contract work breakdown structure, 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.2.3.2 Integrated Baseline Review

As specified by individual delivery orders, the contractor shall participate with the Government in the assessment of program risk and the degree to which the following have been established:

• Technical scope of work is fully included and is consistent with authorizing documents.

• Project schedule key milestones are identified and supporting schedules reflect a logical flow to accomplish the work.

• Resources (budget, facilities, personnel, skills, etc.) are available and are adequate for the assigned tasks.

• Tasks are planned and can be measured objectively relative to the technical progress.

• Rationales underlying the review are reasonable.

• Management processes support successful execution of the project.

3.2.4 Configuration Management

As specified by individual delivery orders, the contractor shall use an automated internal configuration management process to monitor, update, and control all configuration documentation, physical media, and physical parts representing or comprising the system configuration items (CIs). The contractor shall plan and implement an automated configuration management function to perform configuration control, configuration identification, audits, and status accounting in a system engineering environment. The contractor shall develop, maintain, and update configuration management procedures and processes for control of all hardware and software baselines. The process shall allow Government simultaneous access to the common product data model coupled with the ability to coordinate and update immediate changes to the product definition data. The configuration management process must handle all levels of product and process integration to build and support the product as well as manage the sequence of significant events. The Government will maintain control of the functional baseline (FBL) defined by the system performance specification, interface control documents, and software requirement specifications.

27 March 2023

3.2.4.1 Engineering Change Proposals (ECP)

As specified by individual delivery orders, the contractor shall prepare or update ECPs for all hardware and software changes. The contractor shall submit all ECPs for Government approval. The contractor shall document all changes to established baselines and all changes to the requirements (other than the functional baseline), including changes to the statement of work, contract data requirements list (CDRL), the contract schedule, and the general provisions of the contract.

3.2.4.2 Variances

As specified by individual delivery orders, the contractor shall document the rationale and the potential impact of any variance. The contractor shall obtain approval before varying from any Government-controlled baseline.

3.2.5 Risk Management

As specified by individual delivery orders, 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 in the event that more than one delivery order 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.2.6 Associate Contractor Agreements (ACAs)

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

3.2.7 Meetings and Program Reviews

As specified by individual delivery orders, the Contractor shall attend and conduct meetings, reviews and working groups. The Contractor shall document action items, coordinate resolutions and track action items until closure.

3.2.8 Subcontractor Management

As specified by individual delivery orders, the contractor shall maintain the capability to manage subcontractors in accordance with the delivery orders’ Subcontractor

27 March 2023

Management Plan. The contractor shall integrate subcontractors into program IPTs.

Additionally, subcontractors shall be included in program management and tracking systems such as management information systems, EVM system, etc. The contractor shall ensure the requirements of this contract and subsequent delivery orders are applied to all subcontracts and associate contracts.

3.2.9 Cost as an Independent Variable (CAIV)

As specified by individual delivery orders, the contractor shall participate on joint Government-contractor Cost Performance IPTs to discuss tradeoff options for implementing CAIV concepts and guidance.

3.2.10 Computer Hardware, Enterprise Software Solutions (CHESS) Program

As specified by individual delivery orders, the contractor shall comply with the Army’s CHESS program. Under PEO Enterprise Information Systems (EIS), CHESS is the mandatory source for commercial Information Technology (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.2.11 Government Purpose Rights (GPRs)

As specified by individual delivery orders, the contractor shall provide the Government no less than Government Purpose Rights in any software or technical data developed under this contract with Government. The Government will retain Government Purpose Rights for the life of this contract. Upon expiration of the contract, the Government will have unlimited rights in any applicable technical data. The contractor shall ensure that sufficient rights are procured with the addition of new software or hardware proposed for the BEST MAC. The rights shall be procured such that the Government can maintain and modify the system using Government personnel and third party contractors.

3.3 Systems Engineering

As specified by each delivery order, the contractor shall provide the requisite technical and programmatic support to complete the required engineering tasks of the individual DOs.

These tasks shall encompass the efforts associated with the development, dissemination, engineering, management, maintenance, Continuous Technology Refreshment (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. Market surveillance and market investigations shall be conducted in order to maximize the use of commercial and non-developmental items. The contractor shall apply the systems engineering process during each level of system development https://chess.army.mil/

27 March 2023

(system, subsystem, and component) to add value (additional detail) to the products defined in the prior application of the process. Through each of the following design stages, information generated shall be documented in an integrated database.

3.3.1 Software Engineering

As specified by each delivery order, the contractor shall provide the requisite technical and programmatic support to complete the required software engineering tasks of the individual DOs. These tasks shall encompass the efforts associated with the development, dissemination, engineering, management, and maintenance of the TESS architecture, components, and documentation. 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 Core Asset Working Group (CAWG) when new software is developed or utilized. As specified by the individual DO, the contractor shall design, implement, integrate, test and field system 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 design process 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. The contractor shall conduct market surveillance and market investigations, in order 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.3.2 Hardware Engineering

As specified by each delivery order, the contractor shall design, develop, integrate, assemble, and test the system hardware that satisfies the performance and requirements stated in the delivery order. The contractor shall conduct market surveillance and market investigations in order 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 following design stages, information generated shall be documented in LT2 portal; ensuring architecture and reuse are considered at each phase and each delivery order.

3.3.3 Test Engineering

As specified by each delivery order, the contractor shall develop, implement, and maintain a system testability process satisfying all testability requirements, which is traceable throughout the design process, is integrated with other system engineering

27 March 2023 requirements, and is disseminated to design personnel and subcontractors. The contractor shall establish controls for ensuring that each subcontractor’s testability 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, automatic test equipment hardware and software, and maintenance documentation performed as a means for satisfying production testing, and meeting testability requirements. The contractor shall establish a testability program that accomplishes the following:

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

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

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

d. Inclusion of testability in the program review process.

3.3.4 Hardware and Software Integration

As specified by each delivery order, the Contractor shall perform all activities to integrate and assemble the hardware and software to achieve a fully functional and accreditable system, with all support systems, that performs and operates in accordance with the requirements defined in the DO. The Contractor shall verify the complete integration of the hardware and software of each hardware and software subsystem and the overall system through the utilization of formalized test procedures. The contractor shall verify the complete integration of the hardware and software of each hardware and software subsystem and the overall system through the utilization of formalized test procedures. A system level production approval review shall be completed to demonstrate that the total system has 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 specific to each delivery order.

3.3.5 Technology Insertion

As specified by each delivery order, BEST MAC shall provide a path-ahead for migration to and incorporation of future Force On Force (FOF) technological advancements. This includes the establishment of a TESS baseline configuration that is adaptable and can be extended to incorporate future technologies to provide benefits such as more realistic FOF training capability; reduced life-cycle (LC) support costs; and more realistic simulation for Army TESS. The contractor shall work with the Government to investigate new technology insertion plans through system analysis and trade studies.

27 March 2023

Possible candidates for new technologies to be considered in the future include but are not limited to the following:

a. Improving laser transmission through environments obscurants.

b. Improving supportability, increase mean time between essential function failures.

c. Reducing the size and weight of the devices.

d. Lighter weight sensor and detector with improved detection fidelity.

e. Reducing number and complexity of physical connections (cables and connectors).

f. Improving the ability to quickly and easily introduce system upgrades.

g. Minimizing test measurement and diagnostics equipment.

h. System component modularity.

i. Mobile Ad-hoc Network (MANET) System.

j. GPS Position Logger.

k. Direction and Position encoding on Laser Link.

l. Incorporation of Fast Code.

m. 1.55 µm Laser/Detector.

n. Optical Communications Link.

o. Passive helmet.

p. Geometric pairing link.

q. New laser diode.

r. Future Army fire control systems, vehicle types, weapon systems.

s. Weapon effects on vehicle crew within and outside the vehicle.

t. Incorporation of total rounds fired data field, updated with every shot.

u. Other technologies agreed upon via the I-MILES IPT.

v. Vehicular Integration for Command, Control, Communication, Computers, Intelligence, Surveillance, Reconnaissance/Electronic Warfare (C4ISR/EW) Interoperability (VICTORY) bus integration.

w. Encoding Azimuth, Deflection and Shooter Position into the MCC while maintaining backwards compatibility.

x. LT2 PAN Crew Kill Modules

y. Multifunction Vehicle Port (MFVP).

z. Additional weapons and ammunition.

aa. Additional Player IDs.

bb. LTEC revisions.

27 March 2023

3.3.6 System Safety Program

As specified by the individual DOs, the contractor shall maintain a safety process to identify, evaluate, and eliminate or control hazards throughout the BEST-MAC contract. As specified by individual delivery orders, the contractor shall perform Safety Engineering to meet the availability and specific safety requirements of each specific delivery order. The contractor shall ensure all BEST-MAC hardware, products and software services are designed to minimize safety and health risks to operators and maintainers in accordance with MIL-STD-882E.

3.3.7 Product Definition Data (PDD)

As specified by the individual DOs, during the systems engineering and design, and in accordance with MIL-STD-31000B, the contractor shall develop, produce, and maintain 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.4 Supportability Engineering

As specified by the individual DOs, 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.4.1 Reliability Engineering

As specified by individual delivery orders, the contractor shall perform reliability engineering to meet the availability and specific Reliability requirements of each specific delivery order.

3.4.2 Maintainability Engineering

As specified by individual delivery orders, the contractor shall perform a maintainability engineering to meet the availability and specific Maintainability requirements.

3.4.3 Quality Engineering

As specified by the individual DOs, the contractor shall establish measurement points that

27 March 2023 will provide maximum visibility into 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 listing. The contractor shall establish a suspense system to ensure timeliness of analysis and corrective action for discrepancies and risk reduction items. All discrepancy correction shall be documented and entered in an integrated database.

3.4.4 Producibility Engineering

As specified by the individual DOs, 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.4.5 Manpower and Personnel Integration (MANPRINT)

As specified by individual DOs, the contractor shall establish and maintain a formal Manpower and Personnel Integration (MANPRINT) engineering program as each specific delivery order requires.

3.4.6 Value Engineering

As specified by individual DOs, the contractor shall implement and use a value engineering program employing the value methodology. The contractor shall conduct multi-disciplined Joint Government value engineering methodology workshops in order to identify and implement areas for program/process improvement.

3.5 Cybersecurity

As specified by individual DOs, the contractor shall develop and maintain a Cybersecurity process to guide management and modification actions, document decisions, specify and track Cybersecurity requirements, document certification efforts, identify possible solutions, and maintain operational systems security. The contractor shall establish or adopt standards for managing Cybersecurity requirements and capabilities and a Cybersecurity engineering approach that emphasizes purposeful modification or configuration of security solutions. The contractor shall configure, integrate, and implement all architectures, plans, policies and security controls IAW the Department of Defense Risk Management Framework process.

3.5.1 Anti-Terrorism (AT) Level 1 Training

All contractor employees, to include subcontractor employees, requiring access to Army installations, facilities and controlled access areas shall complete AT Level I awareness training within 60 calendar days after contract start date or effective date of incorporation

27 March 2023 of this requirement into the contract, whichever is applicable. The contractor shall submit certificates of completion for each affected contractor employee and subcontractor employee, to the COR or to the contracting officer, if a COR is not assigned, within 30 calendar days after completion of training by all employees and subcontractor personnel.

AT level I awareness training is available at the following website:

https://atlevel1.dtic.mil/at.

All US based contractor employees and associated sub-contractor employees shall receive Government provided area of responsibility (AOR) specific AT awareness training as directed by AR 525-13.

3.5.2 iWATCH Training

The contractor and all associated sub-contractors shall brief all employees of the types of behavior to watch (training standards provided by the requiring activity ATO). This local developed training will be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity to the COR, military police, or local law enforcement. Training shall be completed within 60 calendar days of contract award and with 60 calendar days for new employees commencing performance with the results reported to the COR NLT 90 calendar days after contract award.

3.5.3 Protection Policy & Procedures

The contractor and all associated sub-contractors employees shall comply with applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by government representative). The contractor shall also provide all information required for background checks to meet installation access requirements to be accomplished by installation Provost Marshal Office, Director of Emergency Services or Security Office. Contractor workforce must comply with all personal identity verification requirements as directed by DOD, HQDA and/or local policy.

In addition to the changes otherwise authorized by the changed clause of this contract, should the Force Protection Condition (FPCON) at any individual facility or installation change, the Government may require changes in the contractor security matters or processes.

3.5.4 Access to Government Information Systems

All contractor employees with access to a government information system shall be registered in the Army Training Certification Tracking System (ATCTS) at commencement of services, and must successfully complete the DOD Information Assurance Awareness training prior to assess to the Information System and then annually thereafter.

3.5.5 Operations Security (OPSEC) Plan

3.5.5.1 OPSEC Training

Per AR 530-1, Operations Security, all contractor employees must complete annual Level I OPSEC awareness training. New contractor employees must complete Level I OPSEC training within 30 calendar days of their reporting for duty.

https://atlevel1.dtic.mil/at

27 March 2023

3.5.5.2 Threat Awareness Reporting Program (TARP)

For all contractors with security clearances, per AR 381-12 Threat Awareness and Reporting Program (TARP), contractor employees shall receive annual TARP training by a counterintelligence agent.

3.5.6 Information Assurance/Information Technology (IA/IT) Training

All contractor employees and associated sub-contractor employees must complete the DOD Information Assurance Awareness Training before issuance of network access and annually thereafter. Per DODD 8140.01 and AR 25-2, the contractor employees supporting CS/IT functions shall be appropriately certified upon contract award. The baseline certification as stipulated in DODD 8140.01 shall be completed upon delivery order award. Computer environment certification must be comply with within 6 months of employment.

3.5.7 Spectrum Management

As specified by each delivery order, the contractor shall ensure compliance with the policies and procedures for the Army Frequency Allocation to Equipment (Army J/F-12) Program as described in AR 5-12, Chapter 4 for any system that operates in an electromagnetic spectrum.

3.6 Logistics

As specified by each delivery order, 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 readiness and availability and life cycle cost goals. All Commercial Off-the-Shelf (COTS) manuals shall be reviewed to ensure changes, updates, revisions, or supplementation are completed and address the components actually being installed IAW MIL-PRF-32216B. The contractor shall perform the necessary tasks and activities for logistics, fielding and sustainment. The Government will address the specific requirements in each delivery order. 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

27 March 2023

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 Conducts 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.6.1 Contractor Support

The contractor shall perform the tasks necessary to operate, maintain and support the core assets, products, and fielded systems as each specific order defines. As specified by each delivery order, the contractor shall provide all supplies, services and system/configuration management necessary to perform Interim contractor Support (ICS).

3.6.2 Disclosure of Information

The contractor shall comply with the protection standards and guidance described in DoDM 5200.48 to prevent foreign intelligence collection and/or the unauthorized disclosure of information.

3.6.3 Weapon and Ammunition Storage and Transportation

The contractor shall comply with the requirements of DoD 5100.76-M when handling conventional arms, ammunition, and explosives.

3.6.4 Supportability Analysis and Logistics Product Data

As specified by individual DOs, the contractor shall conduct repair analyses, develop…