Draft_OneSAF_PWS_21June2017_TO_0002.pdf

PWS-2017-037

RFP W900KK-18-R-0010

DISTRIBUTION STATEMENT A. Approved for public release: distribution unlimited.

Performance Work Statement (PWS)

For

One Semi-Automated Forces (OneSAF)

PRODUCTION AND SUPPORT

Indefinite Delivery Indefinite Quantity

Task Order 0002

21 June 2017 Version 1.0

Prepared by U.S. Army PEO Simulation, Training, and Instrumentation

(PEO STRI)

12350 Research Parkway Orlando, FL 32826-3276 ii

Revision

Level Document Date Summary of Change Pages Affected

1.0 21 June 2017 Initial release of document All iii

1.0 SCOPE

1.1 Background

1.2 Development Environment

2.0 APPLICABLE DOCUMENTS

2.1 Department of Defense (DoD) Guidance

2.2 Other Government Documents, Drawings, and Publications

2.3 OneSAF Products

3.0 REQUIREMENTS

3.1 Program Management

3.2 OneSAF Processes

3.3 Systems Engineering

3.3.1 Systems Integration

3.3.2 Software Engineering and Development

3.3.2.1 Software Processes

3.3.2.2 Software Integration

3.3.3 Quality Assurance (QA)

3.3.4 Configuration Management (CM) and Control

3.4 OneSAF Software Product Line Management and Support

3.5 Test Program

3.6 Maintenance and Problem Ticket Report (PTR) Support

3.7 Co‐Developer Support

3.8 Cloud Enabled

3.9 OneSAF Software Product Baseline Release

3.9.1 Tailored OneSAF Software Product Baseline Release

3.10 Capability Development

3.10.1 Concurrency Capability Development

3.10.1.1 Mission Command Adapter (MCA)

3.10.1.2 Standard File Format (SFF)

3.10.1.3 Environmental Runtime Component (ERC)

3.10.1.4 Military Organization and Equipment Representation Currency

3.10.2 P3I Capability Development

3.10.2.1 P3I – Version 9.0 Capability Development

3.11 Customer Support

3.12 OneSAF Help Desk

3.13 Software Distribution

3.14 Training

iv

3.15 OneSAF Integrated Development Environment (IDE)

3.16 OneSAF Secure Lab Environment Support

3.17 Transition

3.18 Cybersecurity

3.19 Security and Data Handling

3.20 Operations Security (OPSEC)

3.21 Travel

3.22 Technical Data, Noncommercial Computer Software and Noncommercial Computer Software Documentation

4.0 Acronym List

Performance Work Statement

For One Semi-Automated Forces (OneSAF)

1.0 SCOPE

This Performance Work Statement (PWS) defines the effort required for providing the capabilities needed to execute the overarching OneSAF program requirements for development, test, integration, interoperability, support, and delivery of software, data, and documentation products to the Assistant Project Manager OneSAF (APM OneSAF); the U.S. Army Modeling and Simulation (M&S) Communities (Acquisition, Analysis, Experimentation, Intelligence, Test and Evaluation, and Training); and the rest of the OneSAF user community. The OneSAF user community includes, without limitation, other U.S. Army Program Executive Offices (PEOs) and Program Managers (PMs), Training and Doctrine Command (TRADOC) Battle Labs, Research Development and Engineering Centers (RDECs) and agencies, other Department of Defense Services and Joint agencies, Government civilian organizations and agencies, academic institutions, foreign countries, and other OneSAF Co-Developers. OneSAF supports force modernization and transformation from weapons systems to brigade. OneSAF supports the Army goal of cloud and web-based software application development in order to reduce hardware and support costs and to enable rapid training at both home station and distributed locations.

OneSAF is a software product line consisting of a set of interacting components where multiple components utilize common services to satisfy a diverse set of OneSAF use cases. The OneSAF Product Line Architecture Specification (PLAS) defines the System Compositions, Products, and Components within the OneSAF product line. The PLAS defines and describes the overall architecture that governs the products and components within the OneSAF product line and illustrates how the product line can be used to construct systems that meet the OneSAF requirements.

The OneSAF Production & Support effort consists of conceptual modeling, architectural, engineering, and software development support required to enhance the OneSAF product line and correct deficiencies identified by the OneSAF Community. With Government concurrence, the OneSAF effort also includes accepting, modifying, integrating, and testing handover packages and new capabilities in support of the requirements and the OneSAF user community.

The effort provides life-cycle sustainment of the released versions. This life-cycle sustainment involves addressing maintenance updates, Problem Ticket Reports (PTRs), and security patches.

The effort also entails on-site and remote support and training for the worldwide OneSAF Community. The effort includes final acceptance and test activities required to deliver the annual and tailored version releases and patches to support OneSAF Community requirements.

1.1 Background

OneSAF was formalized as an acquisition program in April 2000 with its designation as an Acquisition Category (ACAT) III program and delegation of the Milestone Decision Authority

(MDA) to Commanding General (CG), Army Materiel Command (AMC). APM OneSAF was formally chartered by the Army Acquisition Executive (AAE) to manage all OneSAF efforts on 01 May 2000. On 16 May 2000, the MDA responsibility was delegated to the Commander STRICOM (subsequently re-designated as PEO STRI). In December 2003, Milestone B/C was approved by the MDA and the program moved forward with development of the Full Operational Capability (FOC) baseline. FOC was met in March 2006 and fielding was initiated in September 2006 with the release of OneSAF Version 1.0. Additional versions continue to be fielded with Pre-Planned Product Improvements (P3I) and Co-Developer handovers integrated into the baseline. Version 8.6 was released in August 2016 and v8.7 is planned for release in August of 2017. OneSAF reached the ACAT II status and is currently in the production and support phase of the life- cycle with ongoing software production and implementation of Pre- Planned Product Improvements (P3I) as approved by the TRADOC Project Office (TPO) OneSAF.

Through these efforts, capability enhancements are continuously being developed and integrated into the baseline typically resulting in at least a yearly version release. OneSAF has been fielded to multiple Army users within the U.S. Army M&S Communities, as well as other DoD agencies and a multitude of industry, Foreign Military Sales (FMS), and academic locations. Concurrent with P3I enhancements, customer requirements, and user feedback, needs are continuously addressed to assure maximum utilization of the system throughout the growing user community.

1.2 Development Environment

APM OneSAF has established a development environment that brings together Community/User representatives, Government team members, and Contractor software developers into a single facility. The continued goal for this Integrated Development Environment (IDE) is to have the OneSAF Production and Support effort as well as Government staff co-located within a single facility. This development environment is located at 3045 Technology Parkway, Orlando, FL 32826, and provides a working environment for contractors with access to all network infrastructure and software needed to promote effective software development. Facility operations, such as structural maintenance, physical access to the building will be provided by the Government. The development environment is a Common Access Card (CAC)-enabled, protected network-connected environment that provides for development, integration, and testing of the OneSAF software. This environment provides the ability to share information to all authorized Government organizations, users, and developers simultaneously through the dev.onesaf.mil and rt.onesaf.mil web portals. The development environment allows the contribution of ideas, comments, and suggestions as well as exchanging program information and collaboration in a distributed environment.

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

2.1 Department of Defense (DoD) Guidance

The following DoD guidance documents are available on the WWW at URL:

http://www.dtic.mil/

DFARS 252.225-7043 Antiterrorism/Force Protection for Defense Contractors Outside the US

DoD 8570.01-M Information Assurance Workforce Improvement Program DoD 5220.22-M National Industrial Security Program Operating Manual DoDD 8140.01 Cyberspace Workforce Management DoDI 5000.02 Operation of the Defense Acquisition System DoDI 5000.64 Accountability and Management of DoD Equipment and

Other Accountable Property DoDI 8500.01 Cybersecurity DoDI 8510.01 Risk Management Framework (RMF) for DoD Information

Technology (IT)

2.2 Other Government Documents, Drawings, and Publications

The following are available on the WWW at URL http://csrc.nist.gov/publications/PubsSPs.html

NIST SP 800-53 Security and Privacy Controls for Federal Information Systems and Organizations

NIST SP 800-53A Guide for Assessing the Security Controls in Federal Information Systems and Organizations

NIST SP 800-171 Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations

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

Army Regulation (AR) 25-1 Army Information Technology AR 25-2 Information Assurance AR 525-13 Antiterrorism AR 735-5 Property Accountability Policies

Joint Travel Regulation - http://www.defensetravel.dod.mil/site/travelreg.cfm Army Cloud Computing Strategy -http://ciog6.army.mil/Portals/1/Home/Tabs/Strategy/20150424_Army_Cloud_Computing_St rategy.pdf Enteprise Architecture for LandWarNet 2020 and Beyond -http://ciog6.army.mil/Architecture/tabid/146/Default.aspx

2.3 OneSAF Products

The following products are available from the OneSAF development environment:

OneSAF accreditation documentation OneSAF application software, documentation and training materials OneSAF Distribution Agreement (DA) OneSAF Electronic Process Guide (EPG) OneSAF Operational Requirements Document (ORD) V1.1, dated August 2004 OneSAF Product Line Requirement Specification (PLRS) v8.7 OneSAF Product Line Architecture Framework (PLAF) v8.7 OneSAF Product Line Architecture Specification (PLAS), v8.7 OneSAF System Integration Plan (SIP), v8.7 OneSAF V8.7 RIB Items OneSAF V8.7 Use Cases

3.0 REQUIREMENTS

The requirements defined herein shall form the basis for all work that shall be performed as part of Task Order 0002 under the OneSAF Production & Support IDIQ.

3.1 Program Management

RESERVED

3.2 OneSAF Processes

The Contractor shall execute the overarching OneSAF processes and procedures established in the EPG.

3.3 Systems Engineering

The Contractor shall establish and maintain an effective systems engineering program throughout the requirements, design, testing, and integration processes in order to deliver the OneSAF capabilities in an efficient, effective and agile manner. The Contractor shall provide the management and execution of all engineering elements of the contract. The Contractor shall leverage new and evolving technologies and leverage and reuse existing products to the fullest extent practicable with the goal of reducing overall life-cycle costs.

The Contractor shall use an open systems approach as the design strategy to:

(1) Choose commercially supported specifications and standards for selected system interfaces (external, internal, functional and physical), products, practices, and tools;

(2) Integrate cloud-based technology in support of the Army’s goals including data discovery, enrichment, and reuse. The cloud computing capability shall utilize and leverage commercial technology and commodity, non-proprietary components to the maximum extent possible;

(3) Build open system architectures as the primary foundation in developing the proposed system and its elements; and

(4) Identify the means for ensuring conformance to open systems standards and profiles throughout the development process.

The Contractor shall evolve the OneSAF product line architecture over time to address new requirements and to keep pace with the advancing technical environment. Through the system engineering process, the Contractor shall provide updates to the PLAS and Product Line Requirements Specification (PLRS).

(DI-MISC-80711A) Scientific and Technical Report (OneSAF Product Line Architecture Specification) (DI-MISC-80711A) Scientific and Technical Report (OneSAF Product Line Requirement Specification)

3.3.1 Systems Integration

The Contractor shall develop and implement applicable program-level specifications and design documents for the OneSAF Product Line with consideration for critical software items, data rights and interfaces sufficient to support verification & validation, operations, maintenance, and modifications of OneSAF. The Contractor shall provide updates to the System Integration Plan (SIP), including hardware and software development/integration plans, to achieve an optimal system design, production software item, and documentation package.

(DI-MISC-80711A) Scientific and Technical Report (OneSAF System Integration Plan)

3.3.2 Software Engineering and Development

The Contractor shall establish a robust and comprehensive capability to provide conceptual modeling, knowledge acquisition and engineering; requirements analysis, code design, development and unit test; and software integration and test phases in support of activities across the entire OneSAF community. For all software development activities, the contractor shall follow industry-accepted software development best practices that apply Level 3 Capability Maturity Model Integration for Development (CMMI-DEV) equivalent processes and methodologies. The Contractor shall develop the system software to meet the incremental baseline requirements for new functionality. The Contractor shall ensure the software design is based upon a common infrastructure and common infrastructure services; that interoperability and security are built-in; and that information made available is trusted and interoperable. The Contractor shall analyze requirements concerning computer resource utilization and allocate computer resources among the software items, continuously monitor the utilization and reallocate or identify the need for additional resources. The Contractor shall conduct testing that demonstrates that the new capabilities, change sets, PTR/DR fixes, and handover packages integrated meet the requirements and their respective Use Cases as provided by the Government.

3.3.2.1 Software Processes

The Contractor shall adopt the current software development build methodology, where each capability is developed during a series of builds. The Contractor can propose tailoring as required with Government approval. The build typically consists of the Knowledge Acquisition/Knowledge Engineering (KA/KE) phase followed by subsequent builds that consist of the Requirement Analysis (RA), Design, Code and Unit Test (CUT), and Software Integration and Test (SWIT) phases. The Contractor shall perform software capability evaluations and stakeholder peer reviews at appropriate phases of the OneSAF development process to ensure that designs are supportable, testable, and conform to the OneSAF architectural specifications.

3.3.2.2 Software Integration

The Contractor shall continuously support the acceptance, modification, integration, and test of internally-developed and Co-Developer capabilities daily in order to deliver the OneSAF software, data, and documentation products. The Contractor shall support complete integration through automation and automated tests and regression testing of the product baseline utilizing supported software configurations and in supported interoperability configurations. The Contractor’s integration and testing processes shall ensure that new capabilities, handover packages, change sets, and PTR/DR fixes are fully implemented and satisfy their requirements and respective Use Cases without impacting existing capability prior to integration into the main OneSAF Software Product Line.

3.3.3 Quality Assurance (QA)

The Contractor shall implement and maintain a QA program using industry-accepted best practices and subject to Government program approval. The Contractor shall establish the QA process with full Government insight. The Contractor shall maintain records of quality conformance and shall make these records available for Government review upon request.

The Contractor shall maintain a structured quality control process on the project that ensures the prompt detection of deficiencies and initiation of necessary corrective actions for any software artifacts or deliverables found non-compliant with this PWS or the Contractor’s internal practices. The Contractor shall introduce appropriate quality controls and establish measurement points that shall 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 utilize a discrepancy tracking system with the ability to produce complete permanent records of all discrepancies. The Contractor shall establish a suspense system to ensure timeliness of analysis and corrective action for discrepancies and risk reduction items. The Contractor shall make all data exportable in a readable/manipulatable acceptable format for Government use.

The Government shall monitor the Contractor’s performance under this contract in accordance with the Government’s Quality Assurance Surveillance Plan (QASP).

3.3.4 Configuration Management (CM) and Control

The Contractor shall identify and manage the software product baseline configuration items and adopt and expand the established OneSAF CM process to ensure that the OneSAF product conforms to the product requirements and is identified and documented in sufficient detail to support its life-cycle. The Contractor shall follow the established OneSAF processes, contained in the EPG, to maintain system requirements, system configuration information, and all relevant information about the system. The CM process shall address the evolving production configuration and support environments (engineering, implementation and test) used to generate and test the product line. The Contractor shall exercise the CM control on all configuration baselines. The Contractor shall establish and maintain a program-level Configuration Control Board (CCB), and submit Contractor Change Proposals (CCP) or Engineering Change Proposals (ECP) for any recommended change, deviation, or waiver in accordance with (IAW) the established CM process for Government concurrence. The Contractor shall maintain the current CM processes, evaluating them and recommending improvements. The Contractor shall document and the Government shall review all changes to established baselines. The Contractor shall maintain and manage system requirements in an application that provides import/export of data in a format that is compatible with the Dynamic Object Oriented Requirements Systems (DOORS) software application.

(DI-CMAN-80639C) Engineering Change Proposal

3.4 OneSAF Software Product Line Management and Support

RESERVED

3.5 Test Program

RESERVED

3.6 Maintenance and Problem Ticket Report (PTR) Support

RESERVED

3.7 Co-Developer Support

RESERVED

3.8 Cloud Enabled

RESERVED

3.9 OneSAF Software Product Baseline Release

The Contractor shall facilitate the final user acceptance testing to demonstrate that all changes made to the OneSAF Software Product Line Baseline meet the applicable requirements and their respective Use Cases without impacting existing capability. The Contractor shall prepare and deliver one annual version release. The Contractor shall maintain and update OneSAF version deliverable support documentation for each release.

The Contractor shall coordinate with the Government to identify and prioritize test areas, test threads, test scenarios, vignettes; and any other special test needed to evaluate the functionality and stability of the OneSAF software release baseline. The Contractor shall participate in planning conferences with the TPO and M&S Communities to finalize the Release Test Plan. In preparation to the final acceptance, the Contractor shall dry-run all identified threads, vignettes, large scale exercises, and bi-directional interoperability with live Mission Command (MC) devices with user involvement. The Contractor shall collect metrics throughout the dry-runs and report the results back to the Government during the weekly IPT meeting. The Contractor shall ensure that the OneSAF software baseline under test meets the requirements as identified in ORD, PLRS, and P3I lists as well as any specific additional requirements identified in the Release Test Plan prior to the final acceptance test. The Contractor shall capture all data required to measure the capability and stability of the OneSAF baseline, and shall support the Government during the final acceptance test. When appropriate, the Contractor shall ensure the developed capability is adequately tested to meet the appropriate live, virtual, construction, and gaming simulation requirements. The Contractor shall identify and provide all the test requirements needed, including test plans and resources, to assess the newly developed functionality and its impact on the stability of the software product line baseline. The final acceptance test shall be performed by the Government in an operationally relevant environment prior to all annual software product line baseline releases.

(DI-AVCS-80700) Computer Software Product End Item (OneSAF Software Product Version Release) (DI-MISC-80711A) Scientific and Technical Report (OneSAF Operator Manual) (DI-MISC-80711A) Scientific and Technical Report (OneSAF Maintenance Manual) (DI-IPSC-81442A) Software Version Description (VDD) (OneSAF VDD) (DI-IPSC-80603A) Software Test Plan (Product Release Test Plan)

3.9.1 Tailored OneSAF Software Product Baseline Release

The Contractor shall deliver one tailored product version after each major product baseline release which could include an international, domestic minus, or a focused baseline in support of a particular user or user event. The list of entities, units and behaviors to be removed shall be provided by APM OneSAF to the Contractor prior to generating the tailored baseline. The Contractor shall assess the defined specific requirements to facilitate preparation of the tailored product baseline. The Contractor shall modify and remove certain entities, units, behaviors and technical terms, and parameters from the product baseline and remove all references in the associated documentation that are considered sensitive, non-releasable data. The Contractor shall review, analyze, and reconcile all the software products modified to maintain requisite fidelity and consistency with other system components and representations. The Contractor shall perform integration and test of the software product to ensure that the functionality is maintained and that the software product usability is not impaired by the tailoring process. The Contractor shall conduct an acceptance test of the tailored product prior to the delivery and acceptance by APM OneSAF. The Contractor shall conduct final acceptance testing of any tailored product baseline maintenance patches. The Contractor shall deliver additional tailored product baseline versions as engineering change proposals at the request of the Government.

(DI-AVCS-80700) Computer Software Product End Item (OneSAF Software Product Version Release) (DI-MISC-80711A) Scientific and Technical Report (OneSAF Operator Manual) (DI-MISC-80711A) Scientific and Technical Report (OneSAF Maintenance Manual) (DI-IPSC-81442A) Software Version Description (VDD) (OneSAF VDD) (DI-IPSC-80603A) Softwrae Test Plan (Product Release Test Plan)

3.10 Capability Development

The Contractor shall perform capability development and enhancements/improvements of the OneSAF Software Product Line in order to sustain and evolve current and future M&S Community requirements. Requirements for capability development will also be derived from the needs of Army PEOs/PMs, other PEO STRI programs, other Government Agencies, Foreign Military Sales, State and local Government agencies, or similar entities. The Contractor shall analyze proposed capabilities for impact to the OneSAF product baseline configuration and work within the IPT to provide recommendation for architectural enhancements, implementation, and integration in order to deliver the product line software that meets the requirements.

3.10.1 Concurrency Capability Development

3.10.1.1 Mission Command Adapter (MCA)

The OneSAF MCA communicates in a bidirectional manner with real world MC systems using the appropriate tactical message traffic. The Contractor shall maintain and develop software capabilities to stimulate the latest Common Operating Environment (COE) software updates for mission command stimulation as directed by the Government for each software product baseline annual release.

3.10.1.2 Standard File Format (SFF)

The Contractor shall incorporate the current version of the Army Materiel Systems Analysis Activity (AMSAA) SFF as directed by the Government for each software product baseline annual release.

3.10.1.3 Environmental Runtime Component (ERC)

The Contractor shall incorporate ERC improvements as directed by the Government for each software product baseline annual release.

3.10.1.4 Military Organization and Equipment Representation Currency

The Contractor shall incorporate updates to the modeling and representation of military organization structures and equipment as directed by the Government for each software product baseline annual release.

3.10.2 P3I Capability Development

The Requirement Integration Board (RIB) process is executed on an annual basis and is the process that defines the TPO’s requirements for every annual release. The TPO chairs this process and works with the M&S user communities on updating and prioritizing the OneSAF notional P3I Capabilities list. The Contractor shall support the requirements integration and prioritization process by performing an initial analysis of the identified capabilities and developing an initial Rough Order of Magnitude (ROM) estimate for the production of a selected number of capabilities to APM OneSAF to support the final requirement prioritization. At the end of the process the TPO delivers the final RIB items, Use Cases, and updated version of the OneSAF notional P3I capability to APM OneSAF. For each approved version capability requirement set, the Contractor shall conduct the systems engineering process and perform requirement analysis, conceptual modeling, engineering design, development, production, test, and integration and deliver the completed capabilities. Version 8.8 capability is currently under development and the delivery is scheduled for 2018 by the incumbents.

3.10.2.1 P3I – Version 9.0 Capability Development

For Version 9.0, the RIB process has already been executed by the TPO and the results are contained in the OneSAF V9.0 TPO Memorandum and associated Use Cases attached to the request for proposal. The Contractor shall execute the systems engineering process and perform requirement analysis, conceptual modeling, engineering design, development, production, test, and integration of the v9.0 RIB items for release with the Version 9.0 software baseline.

3.11 Customer Support

RESERVED

3.12 OneSAF Help Desk

RESERVED

3.13 Software Distribution

RESERVED

3.14 Training

RESERVED

3.15 OneSAF Integrated Development Environment (IDE)

RESERVED

3.16 OneSAF Secure Lab Environment Support

RESERVED

3.17 Transition

RESERVED

3.18 Cybersecurity

RESERVED

3.19 Security and Data Handling

RESERVED

3.20 Operations Security (OPSEC)

RESERVED

3.21 Travel

RESERVED

3.22 Technical Data, Noncommercial Computer Software and Noncommercial Computer Software Documentation

The Government shall have unlimited rights in all Technical Data, Noncommercial Computer Software and Noncommercial Computer Software Documentation developed as part of this contract. Any 3rd party licensed software shall be provided with a transferable license. When the addition of new software or hardware is proposed or developed using other than full Government funding, the contractor shall ensure that unlimited rights in technical data, software, and documentation are procured. Government approval is required for other than unlimited rights.

4.0 Acronym List

Acronym Description AAE Army Acquisition Executive ACA Associate Contractor Agreement ACAT Acquisition Category AMC Army Materiel Command ANSI/EIA American National Standards Institute/Electronics Industries Alliance AOR Area Of Responsibility

APM

OneSAF

Assistant Project Manager One Semi-Automated Forces

ATCTS Army Training Certification Tracking System AT Antiterrorism CAC Common Access Card CCB Configuration Control Board CCP Contractor Change Proposal CDRL Contract Data Requirements List CG Commanding General CHESS Computer Hardware, Enterprise Software Solutions CM Configuration Management CMMI-DEV Capability Maturity Model Integration for Development CNSSI Committee on National Security Systems Instruction COE Common Operating Environment CONUS Continental United States COR Contracting Officer Representative COTS Commercial off the shelf CUT Code and Unit Test CWBS Contractor Work Breakdown Structure DA Distribution Agreement DFARS Defense Federal Acquisition Regulation Supplement DIACAP DoD Information Assurance Certification and Accreditation Process DoD Department of Defense DoDD Department of Defense Directives DoDI Department of Defense Instructions DOORS Dynamic Object Oriented Requirements Systems DR Discrepancy Report DREN Defense Research & Engineering Network ECP Engineering Change Proposal eCMRA Enterprise-wide Contractor Manpower Reporting Application EPG Electronic Process Guide ERC Environmental Runtime Component EIS Enterprise Information Systems FISMA Federal Information Security Management Act

FMS Foreign Military Sales FOC Full Operational Capability GOTS Government Off The Shelf HBSS Host Based Security System IA Information Assurance IAVA Information Assurance Vulnerability Alert IAW In accordance with IBR Integrated Baseline Review IDIQ Indefinite Delivery Indefinite Quantity IPR In Progress Review IPT Integrated Product Team IT Information Technology KA/KE Knowledge Acquisition and Knowledge Engineering M&S Modeling and Simulation MoA Memorandum of Agreement MC Mission Command MDA Milestone Decision Authority NACI National Agency Check with Inquiries NAWCTSD Naval Air Warfare Center Training Systems Division NETCOM Network Enterprise Technology Command NLT No Later Than OneSAF One Semi-Automated Forces OPM Office of Personnel Management OPSEC Operations Security ORD Operational Requirements Document P3I Pre-Planned Product Improvements PoP Period of Performance PAC Post Award Conference PEO Program Executive Office PEO STRI Program Executive Office for Simulation, Training, and Instrumentation PLAF Product Line Architectural Framework PLAS Product Line Architecture Specification PLRS Product Line Requirement Specification PM Program Manager PMR Program Management Review PTR Problem Ticket Report PWS Performance Work Statement QA Quality Assurance RA Requirement Analysis RDEC Research Development and Engineering Centers RIB Requirement Integration Board RMF Risk Management Framework ROM Rough Order of Magnitude

S2T Synthetic Simulation Transformation SAF Semi-Automated Force SFF Standard File Format SIP System Integration Plan SRR Software Resources Reporting STIG Security Technical Implementation Guides STrP Software Transition Plan SWIT Software Integration and Test TARP Threat Awareness Reporting Program TIM Technical Interchange Meeting TPO TRADOC Project Office TRADOC Training and Doctrine Command URL Uniform Resource Locator VIP Very Important Person WWW World Wide Web