LTRaC Base PWS DRAFT090722v1.docx

Performance Work Statement (PWS) for the Live Training Ranges and Combat Training Centers (LTRaC) Indefinite Delivery/Indefinite Quantity (ID/IQ) Multiple Award Contract (MAC)

U.S. Army Program Executive Office for Simulation, Training, and Instrumentation (PEO STRI) 12211 Science Drive Orlando, FL 32826-3276

Engineering

Prepared By: ____________________ Concurrence: ____________________

Acquisition Logistics

Prepared By: ____________________ Concurrence: ____________________

Program Management

Submitted By: ____________________ Approved By: ____________________

REVISION LOG

TABLE OF CONTENTS

PWS-2022-027

29 July 2022 Version 0.1 iv

PERFORMANCE WORK STATEMENT

FOR THE

LIVE TRAINING RANGES AND COMBAT TRAINING CENTERS (LTRaC)

INDEFINITE DELIVERY/INDEFINITE QUANTITY (ID/IQ)

MULTIPLE AWARD CONTRACT (MAC)

Scope This Performance Work Statement (PWS) defines the work required to be performed for Project Manager Soldier Training’s (PM ST) LTRaC contract. This 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. All efforts performed under this contract will be synchronized with the previously established Live Training Transformation (LT2) processes and standards.

The LTRaC contract objective is to establish a consolidated contracting approach for range and instrumentation efforts within the live training domain. The MAC will provide maximum competition while ensuring streamlined Delivery Order (DO) awards. This will provide the DoD with the ability to rapidly deliver new and upgraded capabilities to the nation’s warfighters.

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

Future Army System of Integrated Targets (FASIT) Digital Range Training System (DRTS) Combat Training Center – Instrumentation System (CTC-IS) Home Station Instrumentation Training System (HITS) Joint Pacific Multinational Readiness Center (JPMRC) Marine Corps Live Training Efforts LTRaC Lot Structure The primary focus of this contract will be hardware centric efforts but may include software products as part of a larger hardware effort. The LTRaC contract is broken out into four focus areas or Lots.

Lot 1: Range Target Systems Lot 1 is continuous technical refreshment (CTR) of existing range target systems once the Military Construction (MilCon) / Department of Public Works (DPW) infrastructure work has been completed. Lot 1 may involve work at any live fire training area to include deployable ranges, Home Station ranges, and the U.S. Army’s CTCs. Lot 1 includes presentation devices (i.e. Stationary Infantry Targets [SIT], Stationary Armor Targets [SAT], Moving Infantry Targets [MIT], Moving Armor Targets [MAT]), communication devices, range control hardware and software, and ancillary hardware. This effort will utilize the Government provided target lifter Technical Data Package (TDP) to produce target lifters to the new baseline. Lastly, this effort includes the delivery of Information Technology (IT) hardware and the Government approved range control software in order to operate the range.

Lot 2 – Small Business Set Aside Lot 2 will consist of less-complex/low risk efforts (limited to one sub-system with no complex interface(s) or dependencies to other subsystems) for the CTC-ISs, HITS, JPMRC, and Live Synthetic Training Environment (STE) Instrumentation efforts. These efforts will include CTRs of existing instrumentation sub-systems and delivery of new sub-system capabilities. Tasks include studies, analysis, development, integration, testing, production, and fielding of new capabilities to one or more sites for instrumentation subsystems.

Lot 2 will also include the work previously performed under the Targetry Range Automated Control and Recording (TRACR) Plus and Army Combat Training Instrumentation Contract (ARCTIC) contracts. This is as follows:

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.

Lot 3 – Digital Range Training System (DRTS) Lot 3 will include the work tasks associated with updating DRTS ranges. These tasks include the premier live fire ranges for Abrams, Bradley, Stryker, and other Ground Combat Vehicles crew and unit qualification. The complexity of these ranges requires vendors experienced with DRTS to perform this work to reduce the risk of issues when work is performed. This will include tasks such as CTRs of IT equipment, player units, aviation systems and other ancillary hardware.

Lot 4 – Instrumentation Systems – Complex Integration Tasks Lot 4 will include the complex efforts (effort across multiple subsystems or external interfaces with complex dependencies) performed for programs that contain Instrumentation Systems to include the CTCs, HITS locations, JPMRC, and FASIT. These efforts will include CTRs, upgrades, and modernization of existing instrumentation or new sub-systems and the development of new capabilities. Tasks include studies, analysis, development, integration, testing, production, and fielding of new capabilities to one or more sites for instrumentation subsystems (e.g. Range Data Management Subsystem (RDMS), Range Monitoring and Communication Subsystem (RMCS), After Action Review (AAR), Core Instrumentation System (CIS), video, voice).

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.

This PWS defines the general tasks to be performed under the LTRaC contract in support of live training requirements. Individual program efforts will define the detailed requirements on the DO level. PM ST envisions that LTRaC 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)

· FASIT

· Live Training Engagement Composition (LTEC)

· Future LT2 Architectures Government Furnished Information (GFI) software and build to print drawings 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

Applicable Documents The following documents form a part of this PWS to the extent specified herein. In the event of a conflict between documents referenced herein and the contents of this PWS, the contents of the PWS shall be the governing requirement.

Department of Defense Standards

Availability of Department of Defense Standards Copies are available on the WWW at URL:

http://quicksearch.dla.mil/qsSearch.aspx Department of Defense Directives

Availability of Department of Defense Directives Copies are available on the WWW at URL:

https://www.esd.whs.mil/Directives/issuances/dodd/ Department of Defense Instructions

Availability of Defense of Defense Instructions Copies are available on the WWW at URL: https://www.esd.whs.mil/Directives/issuances/dodi/ Department of Defense Manuals DODM 5200.01 DoD Information Security Program Availability of Defense of Defense Manuals Copies are available on the WWW at URL: https://www.esd.whs.mil/Directives/issuances/dodm/ Other Government Documents, Drawings, and Publications

Copies are available on the WWW at URL http://www.apd.army.mil/

Copies are available on the WWW at URL http://armypubs.army.mil/doctrine/ Availability of Other Government Documents and Publications Copies of the documents are available from ACC-Orlando, 12211 Science Dr., Orlando, FL 32826.

Requirements The requirements defined herein shall form the basis for all work that shall be performed as part of the Government issued DOs under the LTRaC contract for the analysis, design, development, procurement, integration, prototype production, production, testing, fielding, documentation, sustainment, and disposal of live fire training systems.

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 on a monthly basis and notify the Government of any issues and concerns that arise. The contractor shall track and maintain resources to ensure overall programmatic performance.

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.

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 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 status. The contractor shall identify major elements of subcontracted work.

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 (IMP/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.

Program Reviews 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.

Start of Work Meetings As specified by the individual DO, the contractor shall host a Start of Work meeting either virtually or at the contractor’s facility within fifteen working days 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 partnering approach, and any contract issues.

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 on the progress, performance, and status of major subcontractors.

Technical Design Reviews (TDR) The contractor shall conduct, when appropriate for each individual DO, 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.

Technical Interchange Meetings (TIM) The contractor shall support TIMs. TIMs shall address specific topics or issues, address status of development or test activities between management reviews or coordinate and provide guidance for engineering/logistical data or technical publications.

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.

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 maintain ACAs achieve interoperability and common component goals, as applicable.

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.

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 to the effort. 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, 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.

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.

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. As specified by the individual DO, the contractor shall provide the applicable System Support Package (SSP), transitional training, and transition support to the LCCS contractor.

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 PWS with the overarching LT2 construct and implementation (as described in the LT2 Operations Guide) in order to minimize duplication of efforts and ensure common components 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 the hardware and software components that are part of the LT2 product line Systems Engineering The contractor shall provide the requisite technical and programmatic support to complete the required tasks of the individual DOs associated with the LTRaC engineering and management. These tasks shall encompass the efforts associated with the 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.

Product CTR, Obsolescence, Concurrency, Upgrades and Disposal As specified by individual DOs, the contractor shall perform the necessary tasks and activities for product/system fielding, CTR, hardware obsolescence, concurrency, upgrades, disposal, prototype production, technology insertion, testing, delivery, and sustainment. The following table provides a representative list of tasks and activities that could be required by specific DOs:

Testing and Certification

RAM Analysis

Hardware Engineering 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 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 design stages, information generated shall be documented in an integrated database.

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, automatic 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.

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 specification. 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. 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.

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 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).

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 LTRaC contract. The contractor shall ensure all LTRaC hardware, products and software services are designed to minimize safety and health risks to operators and maintainers in accordance with MIL-STD-882E.

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.

Quality Engineering 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 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.

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 as a result 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.

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 rate production facilities, equipment, capability, and capacity are in place to support the required delivery schedule.

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.

Interface Management 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.

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.

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 LTRaC supported components, services, and assets. The contractor shall also ensure that the products developed and maintained within the LTRaC 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 LTRaC, 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 the prototyping efforts within this PWS 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 contractor shall work with the LT2 cybersecurity personnel to coordinate a transition to Post Deployment Software Support (PDSS)/Post Production Software Support (PPSS) and 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 PDSS/PPSS contractor.

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:

· All hardware and software functions, characteristics, and features

· Operational procedures

· Accountability procedures

· Access controls, remote computers, and terminal facilities

· 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 CS approach shall include controls that are part of the day-to-day operations of the system, and are compliant with AR25-2, DoDI 8500.01, DoDI 8510.01, CNSSI 1253, NIST SP 800-53, and DoDI 8582.01. The contractor shall support accreditations under the RMF IAW 8500.01 and DoDI 8510.01.

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.

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 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 check 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, in order 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.

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). 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 Indentured Parts List Spares and Support Equipment Identification List Support Equipment Tool List Bill of Materials Consolidated 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-Production Support Warranty Information Initial Spares As specified by the individual DO, to reduce cost and mitigate obsolescence risk, the contractor shall procure initial spares. The contractor shall provide the rational for the recommended spare parts list. Items such as acquisition lead time, system criticality, and failure rate shall be considered as part of the rational. The contractor shall provide spare components that are the same as, interchangeable with, or meet the form, fit, and function requirements of the components included in the delivered training system and other deliverable hardware. The contractor shall ensure that these items are configured identically to the respective training device like components. When possible, the contractor shall procure initial spares on the same purchase order as the system hardware. After on-site delivery, the Government reserves the right to test all or a portion of the initial spares. The contractor shall replace all failed or utilized spares prior to Government acceptance.

Technical Publications As specified by the individual DO and CDRLs, the contractor shall utilize the latest version of MIL-STD-40051. The contractor shall describe each operation and maintenance task in detail and in logical, systematic steps for the work to be accomplished. The manuals shall provide system and subsystem-oriented instructions for installation, operation, maintenance, and testing. The operations and maintenance instructions shall accurately provide the technician with all the information needed to keep the equipment operational. The contractor shall identify all required spare parts, consumables, tools, and test/support equipment associated with each operator or maintenance task and identify the level of maintenance at which each task shall be performed. The contractor shall prepare Operator/User’s Manuals (OUM) that provide instructions suitable for use by the LCCS contractor or the system operator. The OUM shall also include operator maintenance tasks such as preventive maintenance checks and services (PMCS), inspection, lubrication, adjustment, and operator level repair and replacement tasks as needed. The contractor shall identify and document system maintenance tasks for the two (2) level maintenance concept. The System Maintenance Manual (SMM) shall provide detailed component installation/removal procedures, fault isolation, Line Replaceable Units (LRU) removal and replacement procedures, firmware update procedures, preventive/scheduled maintenance and unscheduled/corrective maintenance procedures, calibration, and proper use of test equipment for the training system. All tools, test equipment and consumable items required to accomplish any system/subsystem PMCS, maintenance or installation shall be identified just prior to and as part of the task. The SMM shall describe system initialization processes for each system/subsystem, settings, and system requirements necessary to sustain the system/subsystem to the documented product baseline. The contractor shall provide an updated copy of the technical publications and manuals after acceptance of each system. The contractor shall provide a final set of technical publications and manuals after acceptance for each DO.

Commercial-Off-the-Shelf (COTS) Manuals As specified by the individual DO and CDRLs, the contractor shall deliver COTS technical publications for all commercial equipment delivered with the training system or modification. The contractor shall review all COTS manuals and augment with changes, updates, revisions, or supplementary data for inclusion in the appropriate technical manual, that is required to reflect the components being integrated into the system/subsystem. All COTS publications shall reflect the configuration of fielded hardware as documented in the product baseline and be sufficient to support the operation and maintenance of all COTS components per MIL-PRF-32216.

Publications In Process Reviews (IPRs) As specified by the individual DO, the contractor shall host and co-chair publication reviews to ensure the technical publications are accurate. Each IPR shall be scheduled to coincide with a system level program review defined in the IMP/IMS. The contractor shall act on reported decisions and discrepancies resulting from or associated with each IPR. Each review shall include a review of incorporated corrections or comments from previous IPR’s prior to proceeding with the current IPR. If an IPT member identifies a previous IPR comment was not included in the technical publications, the IPR shall be considered incomplete.

Publications Validation/Verification As specified by the individual DO, the contractor shall complete the validations on all technical publications, changes, supplemental data and revisions prior to CDRL submission. The contractor shall assist PEO STRI IPT members with the verifications to confirm that the Technical Manuals (TM) are accurate. The IPT may choose to perform manual verification concurrently with the validation effort. Correction of discrepancies and changes resulting from training, testing, and reviews shall be incorporated into the TM. The contractor shall provide system equipment, technical and engineering support and facilities as required to aide in the performance of verification efforts. The contractor shall incorporate all comments from compliance-reviews, technical accuracy reviews and verification reviews into the final submission of TM. Verification shall be rescheduled if it resulted in more than fifteen percent of the manual requiring correction. A technical publication shall not be ready for validation or verification until the following conditions have been fulfilled:

Engineering technical review has been completed.

Information, illustrations, and parts lists reflect correct configurations of the system and equipment, to include all engineering changes.

Procedural instructions are readily understandable by the intended user and adequate to perform all operations and maintenance functions.

All procedures have been performed to assure accuracy and performance requirements.

Adequacy of data is checked to ensure that it supports the approved maintenance and support plan.

The proper hardware configuration is available for the validation and verification effort.

All safety hazards identified in the safety assessment report are resolved and identified within the text as cautions or warnings necessary to protect the equipment or personnel as appropriate.

The use of any hazardous material has been identified.

New Equipment Training (NET) As specified by the individual DO, the contractor shall define, develop and provide NET to an initial cadre of users/operators and maintainers to understand the functional, operational and maintenance capabilities and requirements.