SCARS_RFP_Attachment_1A_IDIQ_PWS.pdf

Simulator Common Architecture Requirements and Standards –

SCARS

21 December 2018

Performance Work Statement (PWS)

RFP NO: FA8621-18-R-0002

Prepared For:

Department of the Air Force Air Force Life Cycle Management Center AFLCMC/WNS Wright-Patterson AFB Dayton, Ohio 45433

Distribution A. Approved for public release: distribution unlimited

TABLE OF CONTENTS

1. GENERAL INFORMATION

1.1. SCARS SCOPE

1.2. SCARS PRIME, AFFILIATES, AND PARTNERS

1.3. CONTRACTOR PERSONNEL

1.3.1. Location and Hours of Work

1.3.2. Voluntary Protection Program

2. APPLICABLE DOCUMENTS

2.1. DOD HANDBOOKS AND MANUALS AND DIRECTIVES

2.2. U.S. AIR FORCE STANDARDS AND INSTRUCTIONS

2.3. INDUSTRY STANDARDS

2.4. JOINT MANUALS

2.5. US GOVERNMENT PUBLICATIONS, INSTRUCTIONS, AND GUIDES

2.6. ORDER OF PRECEDENCE

3. SCARS INCREMENTAL DEFINITION, DESIGN, DELIVERY,

DEPLOYMENT AND SUSTAINMENT

3.1. INCREMENT OVERVIEW

3.2. INCREMENT IMPLEMENTATION

4. SIMULATOR COMMON ARCHITECTURE (SCA)

4.1. OVERVIEW

4.2. SCA AND REFERENCE ARCHITECTURE

4.2.1. Preparatory Services

4.2.2. Network Expansion Services

4.2.3. SOC Equipment and Software

4.2.4. OPE and Software

4.2.5. Network Equipment and Software

4.2.6. Network Services

4.2.7. SOC Baseline Recovery

4.2.8. Software Baseline Recovery Unit (SBRU)

4.3. SCARS SITE STAND UP AND INSTALLATION

4.3.1. Site Survey and Installation Planning Services

4.3.2. Reserved

4.3.3. SCARS SOC Equipment Install Services

4.3.4. SCARS Network Equipment Install Services

4.3.5. OPE Site Install Services

4.3.6. Renovation Services

4.3.7. Relocation Services

4.4. MATERIAL INSPECTION AND RECEIVING REPORT (DD250)

4.5. QUICK REACTION SYSTEM SUPPORT (QRSS)

4.5.1. Quick Reaction Material

4.6. SCA OPEN SYSTEM REQUIREMENTS

4.6.1. System Requirements Accountability

4.6.2. Inter-component Dependencies

4.6.3. Modular Open Systems Approach (MOSA)

4.6.4. Design Information Documentation

4.6.5. Reserved

4.6.6. Interface Design and Management

4.6.7. Treatment of Proprietary or Vendor-Unique Elements

4.6.8. As Built Configuration List Identification of Modification Items and Funding

Source

4.6.9. Open Business Practices

4.6.10. Reuse of Pre-existing or Common Items

4.6.11. Product Reuse Demonstration

4.6.12. Third-Party Development

4.6.13. Life Cycle Management and Open Systems

4.7. REFERENCE ARCHITECTURE SERVICES

4.7.1. Model Based Systems Engineering (MBSE)

4.7.2. MBSE Development, Maintenance, Access and Licensing

4.7.3. MBSE Coordination and Integration

4.8. MOSA METRICS

4.9. AIR FORCE RESEARCH LABORATORY (AFRL) SCARS SUPPORT SERVICES .. 33

4.9.1. AFRL Working Group

4.9.2. AFRL Future Efforts

5. OPERATIONS & FACILITIES

5.1. SCARS SECURITY AND MAINTENANCE EVENTS

5.1.1. Remote Scan Events

5.1.2. Remote Restore Events

5.2. SCARS LIBRARY SERVICES

5.3. SOC PROCEDURES

5.4. SOC NETWORK SERVICES

5.5. SCARS HELP DESK

5.6. SCARS ASSESS AND AUTHORIZE (A&A) SUPPORT SERVICES

5.7. CYBERSECURITY CONTRACTOR TRAINING AND CERTIFICATION

5.8. NETWORK ACCESS REQUIREMENTS

5.9. SOC FACILITY

5.9.1. Temporary SOC Contractor Facility

5.9.2. Data Processing and Storage Restrictions

5.9.3. Facility Physical Security

5.9.4. Government Facilities Key and Combination Control

5.9.5. Access to Government Facilities

5.9.6. Contingency Procedure for Government Facilities

5.9.7. Contingency Planning (CP)

5.9.8. Facilities Requirements

6. MANAGEMENT SERVICES AND SOFTWARE

6.1. ESTABLISH AND EXECUTE AGREEMENTS

6.1.1. Service Level Agreements (SLA)

6.1.2. Associate Contractor Agreements (ACA)

6.2. STAKEHOLDER COLLABORATION WEBSITE

6.3. CYBER SECURE OPERATING SYSTEMS (OS) SERVICES

6.4. MANAGE AND MAINTAIN STANDARDS

6.4.1. Standards Services

6.4.2. Standards Publishing

6.4.3. Standards Deployment Tracking

6.4.4. Standards Collaboration

6.5. STANDARDS DEPLOYMENT SUPPORT SERVICES

6.6. TESTING

6.7. SYSTEM SECURITY

6.7.1. Acquisition Systems Protection

6.7.2. Network Security

6.7.3. Assessment and Authorization (A&A) for the SCA

6.7.4. Cybersecurity Risk Assessment

6.7.5. Remanence Security

6.7.6. System Security Working Group

6.7.7. Emissions Security

6.7.8. Program Protection

6.7.9. Operations Security

6.7.10. Documentation Control

6.8. CONFIGURATION MANAGEMENT (CM)

6.8.1. Configuration Baseline Management

6.8.2. Functional Baseline

6.8.3. Allocated Baseline

6.8.4. Product Baseline

6.8.5. Change Proposals

6.8.6. Flowdown of CM Requirements to Subcontractors

6.9. SCHEDULE MANAGEMENT

6.10. RISK MANAGEMENT

6.11. MEETINGS AND CONFERENCES

6.11.1. Post Award Conference

6.11.2. PMRs and TIMs

6.12. PERFORM TECHNICAL DEVELOPMENT REVIEWS

6.13. SYSTEMS ENGINEERING

6.13.1. Software Development:

6.13.2. Software License Management

6.14. ORGANIZATIONAL CONFLICT OF INTEREST (OCI)

6.15. GOVERNMENT REVIEWS

6.16. FINANCIAL REPORTING

6.16.1. Cost and Software Data Reporting (CSDR)

6.16.2. Integrated Program Management Report (IPMR)

6.17. CONTRACTOR MANPOWER REPORTING

6.18. PRODUCT SUPPORT

6.18.1. Product Support Logistics

6.18.2. Supply Support

6.18.3. Item Unique Identification

6.18.4. Demilitarization and Disposal

6.18.5. Transition Planning Services

6.18.6. Reserved

6.18.7. Packaging, Handling, Storage and Transportation (PHS&T) Services .. 72

6.18.8. Data 72

6.18.9. Facilities and Infrastructure

6.18.10. Educational Information & Training Materials

6.18.11. Warranty

6.19. SMALL BUSINESS PARTICIPATION

6.20. TRAVEL

7. WORKING GROUPS, BOARDS, AND MEETINGS

8. SERVICES SUMMARY

8.1. QUALITY ASSURANCE

8.1.1. Method of Surveillance: Complaint

8.1.2. Method of Surveillance: Periodic Surveillance

8.1.3. Method of Surveillance: Reports/Analysis

8.1.4. Quality Control Program

8.1.5. PCO review

8.1.6. Changes

8.1.7. Help Desk Metrics

APPENDIX A - GLOSSARY OF TERMS

APPENDIX B – ACRONYM LIST

1. GENERAL INFORMATION

The Air Force Training System portfolio contains disparate training systems with a wide range of modern and legacy technologies. The overall cost of sustaining those systems has increased significantly due to both increasing obsolescence and the steadily increasing cybersecurity posturing required to mitigate complex cybersecurity threats.

These sustainment costs are multiplied further by the fact that the Air Force Training System portfolio is made up of multi-baseline simulation devices requiring unique development, production, testing, and support. To combat these rising support costs, adopt a strong cybersecurity posture, and enhance warfighter readiness, the Air Force is establishing the Simulator Common Architecture Requirements and Standards (SCARS) sustainment initiative.

1.1. SCARS Scope

This SCARS sustainment initiative calls for the definition, design, delivery, deployment, and sustainment of a Simulator Common Architecture (SCA) across the Air Force’s training portfolio, along with the creation of a Security Operations Center (SOC) and Library and the execution of SCARS Management Services. The SCARS initiative will also incrementally implement a Modular Open Systems Approach (MOSA) as well as a set of common standards for Air Force simulators. This PWS presents the definition, design, delivery, deployment, and sustainment tasks the SCARS Prime will need to perform in its support of SCARS. Specific requirements will be defined in the SCARS System Requirements Document (SRD) and subsequent task orders.

1.2. SCARS Prime, Affiliates, and Partners

Successfully executing the SCARS Sustainment Initiative presents a unique collaborative challenge for both the Government and the SCARS Prime. The Air Force’s portfolio of Training Systems contains simulators, training centers, and networks that have been developed and sustained by multiple DoD contractors. To succeed both the Government and the Prime will have to cooperate and collaborate with the training systems’ original equipment manufacturers, as well as the contractors responsible for sustaining and maintaining both the systems themselves and the networks that connect them. This range of contractors for the existing system and its network-providers will be separately contracted by the Government to participate in the overall SCARS Sustainment Initiative.

This complex range of interested parties requires careful definition and clear terminology:

SCARS Prime. For the purposes of this PWS the Prime Contractor for the overall SCARS Sustainment Initiative will be referred to as the SCARS Prime.

SCARS Affiliates. For the purposes of this PWS the DoD contractors or entities developing or sustaining the Air Force’s existing training systems and participating in the SCARS sustainment initiative will be referred to as SCARS Affiliates. At this time, there are no FMS SCARS Affiliates.

SCARS Partners. DoD Contractors or entities developing or sustaining the training systems’ networks will be referred to as SCARS Partners. Examples include the Distributed Mission Operations (DMO) Networks and Air Reserve Component Network

(ARCNET).

Where applicable, each section of this PWS is followed by a list of the relevant CDRLs to provide traceability between described tasks and contract deliverables.

1.3. Contractor Personnel

The SCARS Prime shall accomplish the assigned work by using qualified personnel with appropriate combinations of education, training and experience to accomplish the tasks included in this PWS and subsequent task orders.

The Procuring Contracting Officer (PCO) or base commander may restrict employment of any contract employee, or prospective contract employee, at a Government installation, who is identified as a potential threat to the health, safety, security, general well-being, or operational mission of the installation and its populace. Contract managers and supervisors are included in the definition of employees. All contract employees must be able to read, write, speak, and understand the English language. All contract employees must be able to pass the Test of English as a Foreign Language (TOEFL) with a score of 60 (competent user) or higher.

Contract personnel shall present a neat appearance and be easily recognized as contractor support personnel. In accordance with Defense Federal Acquisition Regulation Supplement (DFARS) 211.106, the SCARS Prime employees shall identify themselves as contractor personnel by introducing themselves or being introduced as such and displaying distinguishing badges for meetings with Government personnel.

SCARS Prime personnel shall identify themselves as contractor employees in telephone conversations and in formal and informal written correspondence.

The SCARS Prime shall not employ any person who is an employee of the Government if the employment of that person would create a conflict of interest, nor shall The SCARS Prime employ any person who is an employee of the Department of Defense (DoD) or any subordinate branch of the DoD, either military or civilian, unless such person seeks and receives approval in accordance with the Joint Ethics Regulation, DoD 5500.07R, and any applicable regulations of their subordinate branch of the DoD.

1.3.1. Location and Hours of Work

The location and hours of work for the effort described in this PWS will be defined in subsequent task orders.

1.3.2. Voluntary Protection Program

The SCARS Prime shall produce a Safety and Health Plan and generic site safety checklist (customizable for all sites). The SCARS Prime’s plan shall include appropriate measures to ensure the SCARS Prime reacts promptly to investigate, correct, and track alleged safety and health violations and/or uncontrolled hazards in contractor work areas. Installation-specific references and policies may be included (or attached) to this contractor-developed plan.

The SCARS Prime shall comply with the specific health and safety requirements identified in this PWS, as well as the Occupational Safety Health Act (Public Law 91- 596). The SCARS Prime shall comply with the health and safety rules of the Government installation that concern related activities not directly addressed in this

PWS.

The SCARS Prime shall take reasonable steps and precautions to prevent accidents and preserve the health and safety of contractor and Government personnel involved with or in any way coming in contact with the tasks required for the performance of this requirement. The SCARS Prime shall also take any additional immediate precautions identified by the PCO for health and safety purposes.

2. APPLICABLE DOCUMENTS

The following documents form a part of this PWS to the extent specified herein. The SCARS Prime shall maintain current and complete regulations, manuals, and other directives deemed necessary to perform contract requirements. The SCARS Prime shall comply with all regulations, manuals, and other directives as referenced in the contract.

Any reference to a publication includes the basic and all its supplements and amendments. Supplements or amendments may be issued during the life of the contract. In the event of conflict between the documents (other than those implementing Public Law) referenced herein and the contents of this PWS, then contents of this PWS shall be considered as superseding requirements.

Applicable documents listed below which are not explicitly referenced elsewhere in this PWS may be referenced in future task orders.

2.1. DoD Handbooks and Manuals and Directives

DoD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM), 28 Feb 2006 DoD 5500.07R, Joint Ethics Regulation, 17 Nov 2011 DoD SD–22, Diminishing Manufacturing Sources and Material Shortages (DMSMS) Guidebook, Jan 2016 DoDD 5000.01, The Defense Acquisition System, 12 May 2003 DoDD 5200.47E, Anti-Tamper (AT), 28 Aug 2017 DoDD 5230.25, Withholding Unclassified Technical Data from Public Release, 18 Aug 1995 DoDI 2040.02, International Transfers of Technology, Articles, and Services, 27 Mar 2014 DoDI 4140.01, DoD Supply Chain Material Management Policy, 14 Sep 2017 DoDI 4151.24, Depot Source of Repair (DSOR) Determination Process, 13 Oct 2017 DoDI 4161.02, Accountability and Management of Government Contract Property, 29 Sep 2017 DoDI 5000.02, Operation of the Defense Acquisition System, 10 Aug 2017 DoDI 5000.64, Accountability and Management of DoD Equipment and Other Accountable Property, 21 Jul 2017

DoDI 5000.67, Prevention and Mitigation of Corrosion on DoD Military Equipment and Infrastructure, 21 Nov 2017 DoDI 5000.73, Cost Analysis Guidance and Procedures, 2 Oct DoDI 5200.39, Critical Program Information (CPI) Identification and Protection Within Research, Development, Test, and Evaluation (RDT&E), 28 May 2015 DoDI 5200.44, Protection of Mission Critical Functions to Achieve Trusted Systems and Networks (TSN), 27 Jul 2017 DoDI 5220.22, National Industrial Security Program (NISP), 1 May 2018 DoDI 5230.24, Distribution Statements on Technical Documents, 1 Nov 2017 DoDI 8500.01, Cybersecurity, 14 Mar 2014 DoDM 4140.01-V3, DoD Supply Chain Materiel Management Procedures: Materiel Sourcing, 13 Dec 2017 DoDM 4140.68, Integrated Materiel Management of Nonconsumable Items, 20 Nov 2017 DoDM 5000.04-M-1, Cost and Software Data Reporting (CSDR) Manual, 18 Apr 2018 DoDM 5200.01-V1, DoD Information Security Program, Overview, Classification, and Declassification, 24 Feb 2012 DoDM 5200.01-V2, DoD Information Security Program, Marking Of Classified Information, 24 Feb 2012 DoDM 5200.01-V3, DoD Information Security Program, Protection Of Classified Information, 24 Feb 2012 DoDM 5200.01-V4, DoD Information Security Program, Controlled Unclassified Information (CUI) , 24 Feb 2012 DoDM 5200.02, Procedures for the DoD Personnel Security Program (PSP), 3 Apr 2017 DoDM 5205.07, SAP Security Manual, Volume 1 (V1) General Procedures, 12 Feb 2018 DoDM 5205.07, SAP Security Manual, Volume 2 (V2) SAP Access Determination Process, 12 Feb 2018 DoDM 5205.07, SAP Security Manual, Volume 3 (V3) Physical Security Guidance for Special Access Program Facilities (SAPFs), 12 Feb 2018

DoDM 5205.07, SAP Security Manual, Volume 4 (V4) Classification and Marking Guidance, 9 May 2018 Guidebook for Contract Property Administration, Department of Defense, December 2014.

Intelligence Community Directive (ICD) 503, IC Information Technology Systems Security Risk Management, Certification and Accreditation, 15 Sep 2008 Intelligence Community Directive (ICD) 705, Sensitive Compartmented Information Facilities, 26 May 2010 Intelligence Community Directive (ICD) 705-1, Physical and Technical Security Standards for Sensitive Compartmented Information Facilities, 17 Sep 2010 MIL-HDBK-217F(2), Reliability Prediction of Electronic Equipment, 28 Feb 95 MIL-HDBK-502A, Product Support Analysis, 6 Mar 2018 MIL-HDBK-61A, Configuration Management Guidance, 7 Feb MIL-HDBK-896A, Manufacturing Management Program Guide, 25 Aug 2016 MIL-STD 129R, Military Marking for Shipping and Storage, 24 May 2018 MIL-STD 130N, Identification Marking of U.S. Military Property, 17 Dec 2017 MIL-STD 881D, Work Breakdown Structures for Defense Materiel Items, 19 Jun 2018 MIL-STD-3048A, Air Force Business Rules for the Implementation of S1000D, 29 Apr 2016 MIL-STD-882E Environment, Safety, and Occupational Health (ESOH), 11 May 2012 OSD Operating and Support Cost Estimating Guide, March

2.2. U.S. Air Force Standards and Instructions

AFI 10-701, Operations Security (OPSEC), 8 Jun 2011 AFI 16-1404, Air Force Information Security Program, 29 May

AFI 16-402, Aerospace Vehicle Programming, Assignment, Distribution, Accounting, and Termination, 30 May 2013 AFI 17-101, Risk Management Framework (RMF) For Air Force Information Technology (IT), 02 February 2017 AFI 17-130, Air Force Cybersecurity Program Management, 19 March 2018 AFI 20-112, Logistics Readiness Quality Assurance Program, 6 Oct 2017 AFI 21-101, Aircraft and Equipment Maintenance Management, 31 May 2018 AFI 21-102_AFMCSUP, Depot Maintenance Management, 22 Jun 2018AFI 21-103, Equipment Inventory, Status and Utilization Reporting, 16 Dec 2016 AFI 23-101, Air Force Materiel Management, 30 Jul 2018 AFI 23-119, Exchange, Sale, or Temporary Custody of Non- Excess Personal Property, 3 July 2018 AFI 36-2251, Management of Air Force Training Systems, 5 Jun AFI 63-101, Integrated Life Cycle Management, 9 May 2017 AFI 91-203, Air Force Consolidated Occupational Safety Instruction, 18 Jul 2018 AFMAN 16-1405, Air Force Personnel Security Program, 1 Aug AFMAN 16-703, Special Access Program (SAP) Security Manual, Volume 3 (V3) Physical Security, 31 Dec 2015 AFMAN 17-1301, Computer Security (COMPUSEC), 10 Feb AFMAN 17-1302-O, Communications Security (COMSEC) Operations, 10 Feb 2017 AFMAN 17-1303, Cybersecurity Workforce Improvement Program, 3 Feb 2017 AFMAN 33-285, Cybersecurity Workforce Improvement Program, 20 Mar 2015 AFMAN 63-143, Centralized Asset Management Procedures, 12 Aug 2015 AFMC 21-401, Engineering Drawing Data Storage, Distribution and Control System, 16 Jun 2017

AFMC SUP 21-101 / AFI 21-101, Non-Standard Organization (NSO) Logistics Maintenance Management, 15 Aug 2016 AFMC SUP 21-102 / AFI 21-102, Depot Maintenance Management, 22 Jun 2018 AFMC SUP 21-103 / AFI 21-103, Equipment Inventory, Status and Utilization Reporting, 11 Oct 2017 AFMCI 20-104, Item Unique Identification, 17 Nov 2017 AFMCI 21-100, Depot Maintenance Management, 8 Sep 2018 AFMCI 21-101, Depot Maintenance Activation Planning, 14 Jun AFMCI 21-401, Engineering Drawing, Data Storage, Distribution and Control Systems, 16 Jun 2017

2.3. Industry Standards

EIA-649-1, Configuration Management Requirements for Defense Contracts, 20 Nov 2014 EIA-649-B, Configuration Management Standard, 1 Apr 2011 GEIA-HB-649, Configuration Management Implementation Guide, 1 Mar 2016 IEEE STD 1278, IEEE Standard for Distributed Interactive Simulation Series:

IEEE 1278.1TM-2012, IEEE Standard for Distributed Interactive Simulation - Application Protocols, 19 Dec 2012 IEEE 1278.2TM-2015, IEEE Standard for Distributed Interactive Simulation - Communication Services and Profiles, 6 Nov 2015 IEEE 1278.3TM-1996, IEEE Standard for Distributed Interactive Simulation Exercise Management & Feedback (EMF) - Recommended Practice (superseded by IEEE 1730TM-2010), 30 Nov 1996 (reaffirmed 17 Jun 2010) IEEE 1278.4TM-2003, IEEE Recommended Practice for Distributed Interactive Simulation - Verification, Validation, & Accreditation, 30 Nov 1997 (reaffirmed 6 Dec 2010) ISO/IEC/IEEE 12207-2017, ISO/IEC/IEEE International Standard – Systems and Software Engineering – Software Life Cycle Processes, 15 Nov 2017 ISO/IEC/IEEE 15289-2015, ISO/IEC/IEEE International Standard Systems and software engineering -- Content of life-cycle information items (documentation), 15 May 2015

IEEE 24765-2017, ISO/IEC/IEEE International Standard – Systems and Software Engineering – Vocabulary, 28 Aug 2017 IEEE STD 1516 High Level Architecture Series:

IEEE STD 1516.2TM-2010, Standard for Modeling and Simulation High Level Architecture - Object Model Template, 18 Aug 2010 IEEE STD 1516-1TM-2010, IEEE Standard for Modeling and Simulation High Level Architecture - Federate Interface Specification, 18 Aug 2010 IEEE STD 1516TM-2010, IEEE Standard for Modeling and Simulation High Level Architecture - Framework and Rules, 18 Aug 2010 IEEE STD1516.4TM-2007, IEEE Recommended Practice for Verification, Validation, and Accreditation of a Federation - An Overlay to the High Level Architecture Federation Development and Execution Process, 20 Dec 2007 SISO-REF 010, Enumerations for Simulation Interoperability, 27 Apr 2018 SISO-REF 010.1, Operations Manual for the Distributed Interactive Simulation Product Support Group (DIS PSG) Enumerations Working Group (EWG), 21 Jan 2015

2.4. Joint Manuals

Department of Defense Joint SAP (Special Access Program) Implementation Guide (JSIG), 11 Apr 2016

2.5. US Government Publications, Instructions, and Guides

CNSSI 1253, Security Categorization and Control Selection for National Security Systems UCDMO CDS Overlay, 27 Mar 2014 National Communications Security Committee Directive 4 /

NACSIM 5100A

CNSSI 4009, Committee on National Security Systems (CNSS) Glossary, 6 Apr 2015 NIST SP 800-18 R1, Guide for Developing Security Plans for Information Technology Systems, 24 Feb 2006 NIST SP 800-30, Guide for Conducting Risk Assessments, Sep NIST SP 800-34, Contingency Planning Guide for Federal Information Systems, 11 Nov 2010

NIST SP 800-37, Guide for Applying the Risk Management Framework to Federal Information Systems, Feb 2010 NIST SP 800-39, Managing Information Security Risk:

Organization, Mission, and Information System View, Mar 2011 NIST SP 800-53, Recommended Security Controls for Federal Information Systems and Organizations, 30 April 2013 NIST SP 800-53A, Guide for Assessing the Security Controls in Federal Information Systems and Organizations, Building Effective Security Assessment Plans, Dec 2014 NIST SP 800-61, Computer Security Incident Handling Guide, 16 Jan 2004 NIST SP 800-161, Supply Chain Risk Management Practices for Federal Information Systems and Organizations, April 2015

2.6. Order of Precedence

In case of a conflict between this document and these references cited herein, this document shall take precedence. Nothing in this document supersedes applicable laws and regulations unless a specific exemption has been obtained.

3. SCARS INCREMENTAL DEFINITION, DESIGN, 1

DELIVERY, DEPLOYMENT AND SUSTAINMENT 2

The SCARS capability is dependent on the SCARS Prime maintaining and publishing 3 the standards chosen by the SCARS Engineering Capability Board (SECB) and 4 approved by the Government according to the processes described in the SECB 5 charter. The SECB is composed of Permanent Members, the SCARS Prime Secretariat, 6 Rotating Members, and Optional Members. The definitions and responsibilities of the 7 members are specified in the SECB Charter. The SCARS capability will be deployed 8 consistent with the SCARS Prime-developed and SECB-approved SCARS Increment 9 Deployment Plans and available funding. The SCARS Prime shall meet weekly, via 10 telecom, with the SECB Permanent members to discuss status updates. 11 SCARS standards will be released on an annual basis consistent with the SCARS 13 Standards Maintenance Process (SMP). SCARS Increments will be considered as the 14 hardware/software (HW/SW) required to execute a series of annually-adopted 15 standards, required configuration baseline changes to the Simulator Common 16 Architecture, and any additional applications, services, and/or microservices adopted by 17 the SECB. SCARS capability will continue to mature over a series of annual cycles in 18 response to training readiness needs, changing cyber threats, technology 19 obsolescence, and the migration to common applications. The SCARS Prime shall be 20 responsible for documenting an increment’s definition and establishing an Increment 21 Deployment Plan for each SCARS Increment. SCARS Affiliates will retain responsibility 22 for the performance of their training system, and will be responsible for providing 23 accurate information to the SCARS Prime through the SECB and standards 24 maintenance processes. 25 o A005 - CDRL - Management Plan (DI-MGMT-80004A/T) 27 [SUBTITLE: Increment Deployment Plan] 28 o A024 - CDRL - Software Development Plan (SDP) (DI-IPSC-81427B) 29 o A025 - CDRL - Software Installation Plan (SIP) (DI-IPSC-81428A) 30

[SUBTITLE: Increment Deployment Plan] 31 o A049 - CDRL - Software Requirements Specification (SRS) (DI-IPSC-81433A) 32

3.1. Increment Overview 34

The SCARS Prime shall facilitate, assess, author, vet, and seek Government approval 35 for SCARS standards, any configuration baseline changes to the Simulator Common 36 Architecture, or any additional applications, services, and/or microservices for each 37 SCARS Increment. This process shall occur through the Government-chaired SECB as 38 described in the SECB Charter and Standards Maintenance Plan (SMP). 39 o A001 - CDRL - Conference Agenda (DI-ADMN-81249B) 41 o A002 - CDRL - Conference Minutes (DI-ADMN-81250B/T) 42 o A003 - CDRL - Presentation Materials (DI-ADMN-81373) 43

The specific standard(s), required configuration baseline changes to the Simulator 45 Common Architecture, and additional applications, services, and/or microservices that 46 define a SCARS Increment will incrementally expand the SCA Reference Architecture. 47 Each SCARS Increment and its associated Increment Deployment Plan will include the 48 roles and responsibilities of the SCARS Prime, SCARS Affiliates, SCARS Partners, and 49 the Government for its deployment. The deployment of a specific increment could span 50 multiple years depending on implementation requirements of individual SCARS sites 51 (the locations with SCARS On-Premise Equipment (OPE)), contract actions, and 52 available funding. Deployment of a SCARS Increment may also require task orders or 53 modification to the SCARS Prime, SCARS Partner, and SCARS Affiliate contract(s). 54 The SCARS Prime shall integrate and manage the approved and funded Increment 55 Deployment Plans within the SCARS Integrated Master Schedule (IMS). 56 o A005 - CDRL - Management Plan (DI-MGMT-80004A/T) 58 [SUBTITLE: Increment Deployment Plan] 59 o A025 - CDRL - Software Installation Plan (SIP) (DI-IPSC-81428A) 60 [SUBTITLE: Increment Deployment Plan] 61

SCARS Increments will be established and adopted sequentially on an annual basis. 63 Deployment of SCARS Increments may overlap. SCARS Increments may not be 64 applicable to all SCARS sites. As new SCARS sites are stood up some may require the 65 deployment of multiple increments. Previously established SCARS sites may only 66 require the increments established since their last upgrade. Increments can include 67 hardware and software in the releases. Each increment shall constitute a major 68 software release including new tools, updates, etc. The SCARS Prime shall deploy 69 minor software releases (not part of an increment), at a minimum, quarterly. The 70 SCARS Prime shall deploy additional minor software releases as necessary to facilitate 71 successful implementation. Minor software releases that are determined to be critical to 72 the success of a previously implemented SCARS Increment shall be incorporated into 73 an updated baseline release for that previously released SCARS Increment. 74 o A018 - CDRL - Interface Design Description (IDD) (DI-IPSC-81436A) 76 A023 - CDRL - Software Design Description (SDD) (DI-IPSC-81435A) 77 o A026 - CDRL - Software Product Specification (SPS) (DI-IPSC-81441A) 78 o A027 - CDRL - Software Version Description (SVD) (DI-IPSC-81442A/T) 79 o A029 - CDRL - System/Subsystem Design Description (SSDD) (DI-IPSC-80

81432A/T) 81 [SUBTITLE: MBSE System Model] 82 o A046 - CDRL - Database Design Description (DBDD) (DI-IPSC-81437A) 83

3.2. Increment Implementation 84

The SCARS Prime shall implement increments as specified by task orders. The SCARS 85 Prime shall leverage the SECB process to develop and seek approval of the SCARS 86 Increment Deployment Plan. It is possible that implementation of SCARS at a specific 87 site will include multiple increments of functionality depending on time and available 88 funding. 89 o A005 - CDRL - Management Plan (DI-MGMT-80004A/T) 90 [SUBTITLE: Increment Deployment Plan] 91 o A025 - CDRL - Software Installation Plan (SIP) (DI-IPSC-81428A) 92 [SUBTITLE: Increment Deployment Plan] 93

4. Simulator Common Architecture (SCA) 95

4.1. Overview 96

The SCA will be defined and documented in a Reference Architecture. The Reference 97 Architecture will be the culmination of SCARS standards established through the SMP 98 process and include the associated data established through the SMP and SECB. The 99 SCA is a standard set of equipment and software which is built to the Reference 100 Architecture and based on Modular Open System Approach (MOSA) principles. The 101 SCA will evolve over time through the aforementioned increments. 102

4.2. SCA and Reference Architecture 103

The SCARS Prime shall be responsible for the overall definition, design, delivery, 104 deployment and sustainment of the SCA. The SCARS Prime shall define and document 105 the SCA in a Reference Architecture defined by standard approved through the SCARS 106 SMP and SECB. The SCA shall allow for growth as the SCA is further defined through 107 the SMP and SECB. The SCA shall remain consistent with the Reference Architecture 108 as the Reference Architecture is further defined through the SMP and SECB. 109 The SCARS Prime shall plan incremental updates to the SCA and maintain a version 111 release process. The SCARS Prime shall maintain all fielded SCA versions and have a 112 plan to patch and phase out SCA equipment. The SCARS Prime shall deliver all 113 Commercial Off the Shelf (COTS) and Government Off the Shelf (GOTS) equipment 114 and software to the Government, to include sufficient technical data, documents, 115 information, licenses, and data rights IAW the SCARS H-Clauses. 116 o A007 - CDRL - Supplier’s Configuration Management Plan (DI-SESS-80858C) 117 o A027 - CDRL - Software Version Description (SVD) (DI-IPSC-81442A/T) 118 o A062 - CDRL - Technical Data Package (DI-SESS-80776A/T) 119

4.2.1. Preparatory Services 120

SCARS Preparatory Services are the non-recurring design aspects of the SCA. The 121 SCARS Prime shall provide the preparatory services necessary to architect and 122 maintain the SCA, SOC and Library and the execution of SCARS Management 123 Services. These preparatory services shall include all engineering services and security 124 services necessary to design and establish SCARS infrastructure which has the ability 125 to sustain the SCARS sites as they are connected to that infrastructure. The SCARS 126 Prime shall submit a System Safety Program Plan and an initial Safety Assessment 127 Report. 128

In addition, the SCARS Prime shall procure, deliver, set up, and test the SCARS OPE 129 and network connection for the first SCARS Affiliate service. This first SCARS Affiliate 130 service shall be considered complete when the SCARS SOC and the SCARS Affiliate 131 receive an Authority to Operate (ATO) on the network without adverse impacts to 132 training operations. 133 o A079 - CDRL - Safety Assessment Report (SAR) (DI-SAFT-80102C) 134 o A080 - CDRL - System Safety Program Plan (SSPP) (DI-SAFT-81626/T) 135

4.2.2. Network Expansion Services 136

The SCARS Prime shall provide the preparatory services necessary to expand the 137 design and infrastructure of SCARS as directed by the Government in a task order. 138

4.2.3. SOC Equipment and Software 139

The SCARS Prime shall define, design, deliver, deploy, and sustain SOC equipment 140 and software IAW a Government task order. 141 o A018 - CDRL - Interface Design Description (IDD) (DI-IPSC-81436A) 143 A023 - CDRL - Software Design Description (SDD) (DI-IPSC-81435A) 144 o A027 - CDRL - Software Version Description (SVD) (DI-IPSC-81442A/T) 145 o A029 - CDRL - System/Subsystem Design Description (SSDD) (DI-IPSC-146

81432A/T) 147 [SUBTITLE: MBSE System Model] 148

4.2.4. OPE and Software 149

The SCARS Prime shall define, design, deliver, deploy, and sustain OPE and software 150 to SCARS Affiliate sites. The SCARS Prime shall also provide SCARS Partners OPEs 151 as necessary and execute recurring integration and/or regression testing with SCARS 152 Affiliate and SCARS Partner systems. The SCARS Prime shall maintain both an 153 operational mode and a development mode. 154 o A018 - CDRL - Interface Design Description (IDD) (DI-IPSC-81436A) 156 A023 - CDRL - Software Design Description (SDD) (DI-IPSC-81435A) 157 o A027 - CDRL - Software Version Description (SVD) (DI-IPSC-81442A/T) 158 o A029 - CDRL - System/Subsystem Design Description (SSDD) (DI-IPSC-159

81432A/T) 160 [SUBTITLE: MBSE System Model] 161

4.2.5. Network Equipment and Software 162

The SCARS Prime shall define, design, deliver, deploy, and sustain network equipment 163 and software to SCARS sites. The SCARS Prime shall provide SCARS Partners 164 network equipment and software as necessary to maintain recurring integration and/or 165 regression testing with SCARS Partner systems. 166 o A018 - CDRL - Interface Design Description (IDD) (DI-IPSC-81436A) 168 A023 - CDRL - Software Design Description (SDD) (DI-IPSC-81435A) 169 o A027 - CDRL - Software Version Description (SVD) (DI-IPSC-81442A/T) 170 o A029 - CDRL - System/Subsystem Design Description (SSDD) (DI-IPSC-171

81432A/T) 172 [SUBTITLE: MBSE System Model] 173

4.2.6. Network Services 175

The SCARS Prime shall provide WAN equipment and software as required, which meet 176 requirements in the SRD. The SCARS Prime shall manage the ordering (leasing) of the 177 circuits and/or network as required. 178

The SCARS Prime shall manage and maintain Wide Area Network (WAN) infrastructure 179 services except when there is an existing WAN Connection to the SCARS Affiliate 180 system sites (provided by a SCARS Partner). 181

The SCARS Prime shall maintain a routing, port and protocols, and filtering Plan for 182 SCARS networks. 183

If the Government decides to transition parts of the network from contractor provided to 184 Government provided, the SCARS Prime shall manage the ordering of the Government 185 network and circuits. 186 o A018 - CDRL - Interface Design Description (IDD) (DI-IPSC-81436A) 187 A023 - CDRL - Software Design Description (SDD) (DI-IPSC-81435A) 188 o A027 - CDRL - Software Version Description (SVD) (DI-IPSC-81442A/T) 189 o A029 - CDRL - System/Subsystem Design Description (SSDD) (DI-IPSC-190

81432A/T) 191 [SUBTITLE: MBSE System Model] 192

4.2.7. SOC Baseline Recovery 193

The SCARS Prime shall define, design, deliver, deploy, and sustain a SOC baseline 194 recovery capability. 195 o A018 - CDRL - Interface Design Description (IDD) (DI-IPSC-81436A) 196 A023 - CDRL - Software Design Description (SDD) (DI-IPSC-81435A) 197 o A027 - CDRL - Software Version Description (SVD) (DI-IPSC-81442A/T) 198 o A029 - CDRL - System/Subsystem Design Description (SSDD) (DI-IPSC-199

81432A/T) 200 [SUBTITLE: MBSE System Model] 201

4.2.8. Software Baseline Recovery Unit (SBRU) 202

The SCARS Prime shall define, design, deliver, deploy, and sustain Software Baseline 203 Recovery Units (SBRUs) representative of each OPE software configuration. The 204 SCARS Prime shall ensure that SBRUs can remotely restore the OPE software 205 configurations from a centrally managed location. The SCARS Prime shall also provide 206 on-site SBRUs with the OPE to enable local recovery of the OPE. 207 o A018 - CDRL - Interface Design Description (IDD) (DI-IPSC-81436A) 208 A023 - CDRL - Software Design Description (SDD) (DI-IPSC-81435A) 209 o A027 - CDRL - Software Version Description (SVD) (DI-IPSC-81442A/T) 210 o A029 - CDRL - System/Subsystem Design Description (SSDD) (DI-IPSC-211

81432A/T) 212 [SUBTITLE: MBSE System Model] 213

4.3. SCARS Site Stand up and Installation 214

4.3.1. Site Survey and Installation Planning Services 215

The SCARS Prime shall perform a site survey for each SCARS site as directed by the 216 Government. The SCARS Prime shall travel as necessary to perform site surveys. The 217 SCARS Prime shall collaborate and coordinate with the SCARS Affiliates, SCARS 218 Partners, and/or site (base) personnel in determining the method of integration, 219 implementation and deployment for local networking and server infrastructure. The 220 SCARS Prime shall produce a site survey report for each SCARS site. 221

The SCARS Prime shall work with the Government and SCARS Affiliates to identify 222 changes to the SCARS sites and continue to update the plan as necessary. The 223 installation plan shall provide flexibility to accommodate training priorities of the SCARS 224 Affiliates. 225

The SCARS Prime shall notify the Government and applicable host base 226 representatives in advance of all SCARS equipment deliveries and shall provide weekly 227 schedules of all SCARS Prime activities. The SCARS Prime shall ensure all employees 228 obtain needed personnel and vehicle passes from the host base and comply with host 229 base regulations for their control and the use of base facilities. The SCARS Prime shall 230 permit host base safety, fire and health officials to conduct inspections of work areas 231 and comply with local safety reporting procedures and base fire prevention directives. 232 The SCARS Prime shall report SCARS and/or Simulators facility maintenance problems 233 to the applicable host base representative. The SCARS Prime shall provide the host 234 base communications office adequate prior notice of new OPE and/or Wide Area 235 Network connections installations. 236

a) The SCARS Prime shall comply with base policy and base directives concerning 237 facility management. 238

b) The SCARS Prime shall be responsible for the general safety, security, and 239 operation of the facilities and equipment required under this contract. The 240

SCARS Prime shall accompany and assist Government facilities personnel (Fire 241 Department, Security Forces, Safety, Civil Engineering, Building Manager, etc.) 242 in the performance of their duties, as required. As part of the Logistics Plan, the 243 SCARS Prime shall address Facilities and Infrastructure. 244 o A022 - CDRL - Site Survey Report (SSR) (DI-MISC-82104) 246

4.3.2. Reserved 247

4.3.3. SCARS SOC Equipment Install Services 248

The SCARS Prime shall install and configure the necessary components to establish 249 the SOC IAW a task order. 250 o A031 - CDRL - Test Plan (DI-NDTI-80566A) 251 o A032 - CDRL - Test Procedures (DI-NDTI-80603A) 252

[SUBTITLE: Acceptance Test Procedures] 253

4.3.4. SCARS Network Equipment Install Services 255

The SCARS Prime shall install and configure the necessary components to establish 256 WAN connectivity to the SCARS Affiliate sites without existing SCARS Partner WAN 257 connectivity. 258

The SCARS Prime shall collaborate and coordinate with the SCARS Affiliates, SCARS 259 Partners, and/or site (base) personnel in determining the timing of the installation of the 260 network equipment. The SCARS Prime shall ensure training system site downtime does 261 not exceed 5 training days (8 training days when installed with OPE Site Install) including 262 equipment installation, integration and functional checks at each SCARS install site 263 unless otherwise specified in the task order. The SCARS Prime shall provide support to 264 SCARS Affiliates and SCARS Partners during recertification of classified facilities. 265

The SCARS Prime shall complete successful functional checks for each SCA 266 component. 267 o A031 - CDRL - Test Plan (DI-NDTI-80566A) 268 o A032 - CDRL - Test Procedures (DI-NDTI-80603A) 269

[SUBTITLE: Acceptance Test Procedures] 270

4.3.5. OPE Site Install Services 271

The SCARS Prime shall install and configure the OPE to enable integration with the 272 SCARS Affiliate site. The OPE shall be integrated with the SCARS WAN or SCARS 273 Partner WAN connection as directed in the task order to enable the SCARS SOC to 274 engage with the SCARS Affiliate site during SCARS Events. 275

The SCARS Prime shall collaborate and coordinate with the SCARS Affiliates, SCARS 276 Partners, and/or site (base) personnel in determining the timing of the installation of the 277 OPE. The SCARS Prime shall ensure training system site downtime does not exceed 5 278 training days (8 training days when installed with SCARS Network Equipment Install) including 279 equipment installation, integration and functional checks at each SCARS site unless 280 otherwise specified in the task order. The SCARS Prime shall provide support to 281 SCARS Affiliates and SCARS Partners during recertification of classified facilities. 282

The SCARS Prime shall complete successful functional checks for each SCA 283 component. 284 o A031 - CDRL - Test Plan (DI-NDTI-80566A) 285 o A032 - CDRL - Test Procedures (DI-NDTI-80603A) 286

[SUBTITLE: Acceptance Test Procedures] 287

4.3.6. Renovation Services 289

The SCARS Prime shall Renovate SCARS SOC location as specified by the 290 Government in a task order. 291

4.3.7. Relocation Services 292

The SCARS Prime shall relocate SCARS equipment as specified by the Government in 293 a task order. 294

4.4. Material Inspection and Receiving Report (DD250) 295

At the time of each delivery of supplies or services under this contract, the SCARS 296 Prime shall prepare and furnish to the Government a Material Inspection and Receiving 297 Report in the manner and to the extent required by 10 U.S.C § 2227, DFARS 252.246-298 7000, 252.232-7003, and Appendix F, Material Inspection and Receiving Report, of the 299 Defense FAR Supplement. The SCARS Prime shall ensure two copies of the receiving 300 report (DD250 paper copies or the Invoicing, Receipt, Acceptance, and Property 301 Transfer (iRAPT) (formerly WAWF) electronic report) are distributed with the shipment, 302 in accordance with Appendix F, Part 4, F-401, Table 1, of the Defense FAR 303 Supplement. Information regarding WAWF is available on the Internet at 304 https://wawf.eb.mil/. 305

4.5. Quick Reaction System Support (QRSS) 306

The SCARS Prime shall establish a quick reaction system support capability to 307 implement emerging and Government directed capabilities into the SCA baseline. The 308 Quick Reaction System Support shall be established to conduct any associated 309 research, development, production, deployment, and sustainment tasks specific to 310 emerging training requirements to include, but not limited to, studies, additional 311 integration support, adding and enhancing GFP data to the Library, USCYBERCOM 312 https://wawf.eb.mil/

TASKORD-directed patching, deploying GOTS and or COTS HW/SW, and/or the 313 additional hardware needed. The QRSS shall be accomplished as directed in a 314 subsequent task order. 315

4.5.1. Quick Reaction Material 316

The SCARS Prime shall procure material required to execute QRSS as required in a 317 task order. 318

4.6. SCA Open System Requirements 319

The SCARS Prime shall define and design the SCA to be layered and modular and 320 uses standards-based Commercial Off the Shelf/Non-developmental Item (COTS/NDI) 321 hardware, operating systems, and middleware. The SCARS Prime shall ensure critical 322 abstraction layers are vetted through the SECB or the Systems Engineering design 323 reviews. The SCARS prime shall provide the affiliates and partners sufficient SCA 324 definition and design detail to allow for third party application development and 325 integration with the SCA. The SCARS Prime’s design approach shall be applied to 326 subsystems and components. The SCARS Prime shall deliver and maintain an Open 327 System Management Plan (OSMP). 328

The OSMP shall describe how the SCA will incorporate re-configurability, portability, 330 maintainability, technology insertion, vendor independence, reusability, scalability, 331 interoperability, upgradeability, and long term supportability. 332

The OSMP shall describe how external information exchange requirements will be 333 implemented in a standard and open manner. 334

The OSMP shall document how SCA modules shall have minimal dependencies on 335 other modules (loose coupling) as evidenced by simple well defined interfaces and by 336 the absence of implicit data sharing. 337

The SCARS Prime shall ensure that changes to system behavioral requirements can be 338 accomplished by changing the minimum number of modules in the system. 339

The OSMP shall document how SCA modules will be characterized by the singular 340 assignment of identifiable, discrete functionality (high cohesion). 341 o A020 - CDRL - Open Systems Management Plan (DI-MGMT-82099) 342

During implementation of all SCA components, the SCARS Prime shall use an open 343 systems approach to utilize modular design, standards-based interfaces, and widely-344 supported consensus-based standards throughout all increments of the design. The 345 SCARS Prime shall demonstrate compliance with the OSMP during all design reviews. 346 The SCARS Prime shall update the OSMP with each increment. The proposed OSMP 347 will be incorporated into the contract with any increment, changes, alterations, and/or 348 modifications requiring Government approval. 349

The SCARS Prime shall provide copies of license agreements related to the use of 350 these components for Government approval prior to use as part of the SCA OSMP. The 351 SCARS Prime shall seek licenses through AF Enterprise License Agreement (ELA) 352 programs where applicable through the DoD Enterprise Software Initiative (DoD ESI) at 353 www.esi.mil. 354

The Government defines “component” consistent with the Institute of Electrical and 355 Electronics Engineers (IEEE) definition from IEEE 24765-2017, “one of the parts that 356 make up a system. A component may be hardware or software and may be subdivided 357 into other components.” 358

The SCARS Prime shall include planning that identifies the SCARS Prime’s specific 359 approach to ensuring system and interface data is well-defined, available to all SCARS 360 Affiliates, SCARS Partners, and the Government and uses a standards-based tool for 361 definition within the context of DoD and Service upgrade programs. 362

The SCARS Prime shall develop system upgrades, IT system capabilities and business 363 rules that ensure that: 1) data will be posted to shared spaces for users to access and 364 download except when limited by security, policy, or regulations; 2) data shall provide 365 for interoperability with many-to-many exchanges of data, and verified trust and 366 integrity of users and applications; and 3) data shall be transmitted through well and 367 openly defined interfaces. 368

4.6.1. System Requirements Accountability 369

The SCARS Prime shall ensure that SRD requirements are traced to one or more 370 modules consisting of components that are self-contained elements with well-defined, 371 open and published interfaces implemented using open standards. 372

4.6.2. Inter-component Dependencies 373

The SCARS Prime shall ensure the interfaces between the system layers shall be built 374 to open standards or the technical data describing the interface shall be available to the 375 Government with at least Government Purpose Rights. 376

The SCARS Prime shall ensure the system architecture has minimal inter-component 377 dependencies to allow components to be decoupled and reused, where appropriate, 378 across various DoD or Service programs and platforms. 379

4.6.3. Modular Open Systems Approach (MOSA) 380

The SCARS Prime shall describe its rationale for the modularization choices as the 381 SCA evolves in the OSMP. The SCARS Prime’s design approach shall produce a 382 system that consists of hierarchical collections of software and hardware configuration 383 items (components). These components shall be of a size that supports competitive 384 acquisition as well as reuse. The SCARS Prime’s design approach shall emphasize the 385 selection of components that are available commercially or within the DoD, to avoid the 386 http://www.esi.mil/ need to redevelop products that already exist and that can be reused. The SCARS 387 Prime’s rationale shall explicitly address any tradeoffs performed, particularly those that 388 compromise the modular and open nature of the system. 389

The SCARS Prime’s architectural approach shall enable the rapid and affordable 390 insertion and refreshment of technology through modular design, the use of open 391 standards and open interfaces. The SCARS Prime shall define the functional 392 partitioning and the physical modularity of the system to facilitate future replacement of 393 specific subsystems and components without impacting other parts of the system and to 394 encourage third-party vendor’s participation. 395

4.6.4. Design Information Documentation 396

The SCARS Prime shall document and model the system or component (e.g., software, 397 hardware, middleware) design information using industry standard formats (e.g., Unified 398 Modeling Language). It shall also document and model how it will use tools that are 399 capable of exporting model information in a standard format (e.g., Extensible Markup 400 Language Metadata Interchange (XMI) and AP233/ISO 10303). 401 o A029 - CDRL - System/Subsystem Design Description (SSDD) (DI-IPSC-402 81432A/T) 403 [SUBTITLE: MBSE System Model] 404

4.6.5. Reserved 406

4.6.6. Interface Design and Management 407

The SCARS Prime shall…