USMC_ISMT_SOW_Final_1_July_2013.pdf

STATEMENT OF WORK

FOR

INDOOR SIMULATED MARKSMANSHIP TRAINER - UPGRADE (ISMT)

MARCORSYSCOM

PROGRAM MANAGER FOR TRAINING SYSTEMS

12350 RESEARCH PARKWAY

ORLANDO, FLORIDA 32826-3275

Prepared by:

Major Edwin Norris ISMT Project Manager

Approved by:

William Fondriest Product Manager for Individual Systems

ISMT SOW

M67854-13-R-7815

1 July 2013 i

TABLE OF CONTENTS

1 SCOPE

1.1 System Overview

1.2 Definitions

1.2.1 Acquisition Streamlining

1.2.2 Contract Requirements

1.2.3 Commercial Item

1.2.4 Non-Developmental Items (NDI)

1.2.5 Trainer Peculiar Equipment (TPE)

1.2.6 Interim Contractor Support (ICS)

1.2.7 Intial Support Kit (ISK)

1.3 Security Requirements

2 APPLICABLE DOCUMENTS

2.1 Government Documents

2.2 Military Standards and Specifications - Guidance Only

2.3 Federal Standard - Mandatory

2.4 Handbooks - Guidance Only

2.5 Other Government Documents

2.7 Non-Government Documents

3 REQUIREMENTS

3.1 General

3.2 Program and Data Management

3.2.1 General

3.2.2 Integrated Project Management

3.2.3 Integrated Product Team (IPT)

3.2.3.1 Working Groups

3.2.3.1.1 Scenario Working Group

3.2.3.2 Communications

3.2.4 Program Management

3.2.4.1 Integrated Master Schedule (IMS)

3.2.4.2 Milestones

ii

3.2.4.3 Risk Management Program (RMP)

3.2.4.3.1 Risk Mitigation

3.2.5 Subcontractor Management

3.2.6 Data Management

3.2.6.1 Technical Proposal

3.2.6.2 Assignment of Responsibility and Authority

3.3 Government Furnished Property

3.3.1 Government Furnished Equipment (GFE)

3.3.2 Government Furnished Information

3.4 Meetings, Reviews, Conferences

3.4.1 Contractor Responsibilities

3.4.2 Post Award Conference (PAC)

3.4.2.1 PAC Entry Criteria

3.4.2.2 PAC Exit Criteria

3.4.3 System Requirements Review (SRR)

3.4.3.1 SRR Entry Criteria

3.4.3.2 SRR Exit Criteria

3.4.4 Preliminary Production Review (PPR)

3.4.4.1 PPR Entry Criteria

3.4.4.2 PPR Exit Criteria

3.4.5 Critical Production Review (CPR)

3.4.5.1 CPR Entry Criteria

3.4.5.2 CPR Exit Criteria

3.4.6 In-Process Reviews (IPRs)

3.4.6.1 Technical Documentation (TD) IPRs

3.4.6.1.1 30 percent TD IPR Entry Criteria

3.4.6.1.2 30 percent TD IPR Exit Criteria

3.4.6.1.3 80 percent TD IPR Entry Criteria

3.4.6.1.4 80 percent TD IPR Exit Criteria

3.5 Systems Engineering (SE)

3.5.1 Systems Engineering (SE) Process

iii

3.5.2 Requirements Analysis and Functional Allocation

3.5.3 Generation of Specifications

3.5.4 Reliability and Maintainability (R&M) Program

3.5.5 Quality Management System

3.6 Software

3.6.1 Source Code and Executable Software

3.6.2 Computer Software and Technical Data Rights

3.7 Engineering Drawings

3.7.1 Commercial Drawings

3.7.2 Product Drawings

3.8 System Test and Evaluation (T&E)

3.8.1 Responsibility for tests

3.8.1.1 Test authority

3.8.1.2 T&E program planning

3.8.1.3 Test resources and facilities

3.8.2 Test methods

3.8.2.1 Test criteria

3.8.2.2 Tolerance Data

3.8.2.3 Alignment

3.8.2.4 Test log

3.8.2.5 Changes during testing

3.8.2.6 Changes after testing

3.8.3 T&E Deficiency Reporting System

3.8.3.1 Deficiency Report (DR) Categories

3.8.4 T&E program components

3.8.4.1 In-process inspections

3.8.4.2 Incremental Contractor Preliminary Inspection

3.8.4.3 Test Readiness Review

3.8.4.3.1 TRR Entry Criteria

3.8.4.3.2 TRR Exit Criteria

3.8.4.4 Conformance Inspections

iv

3.8.4.4.1 Functional Configuration Audit

3.8.4.4.2 Government Preliminary Inspection

3.8.4.4.3 Joint Final Inspection

3.8.4.4.4 Physical Configuration Audit

3.9 Information Assurance

3.9.1 Initial Defense IA Certification and Accreditation Process (DIACAP) Meeting ... 34

3.9.1.1 IA Certification and Accreditation Support

3.9.1.2 Software Integrity Testing and Certification

3.9.1.3 IA Compliance

3.9.1.4 IA Vulnerability Management Program (IAVMP)

3.9.1.5 IA Contractor Training and Certification

3.9.1.6 DIACAP Implementation Plan (DIP) Review and Update

3.9.1.7 Information Security

3.9.1.7.1 IA Documentation Deliverables

3.9.1.8 Network Scans

3.9.1.9 Analysis of the System Development Life Cycle (SDLC)

3.9.1.10 Security Test and Evaluation (ST&E)

3.10 Environment, Safety, and Occupational Health

3.10.1 System Safety Tasks

3.10.1.1 System Safety Analysis and Assessment

3.10.1.2 Material Safety Data Sheets

3.10.1.3 ESOH Compliance Assessment

3.10.1.4 Lithium Battery Safety Qualification

3.10.1.5 Site Safety

3.10.1.6 Hazardous Material Use

3.10.1.7 Unforeseen Hazardous Material

3.10.1.8 Certification

3.10.1.9 Accidents

3.11 Quality Assurance Program

3.11.1.1 Quality Inspection and Test Records

3.11.1.2 Product Assurance Source Audits and Surveillance Inspection v

3.12 Configuration Management Process

3.12.1 Configuration Identification

3.12.2 Configuration Status Accounting

3.12.3 Configuration Status Accounting Serialized Tracking

3.12.4 Configuration Status Accounting Modification Tracking

3.12.5 Configuration Identification (CI)

3.12.6 Baseline Management

3.12.7 Product Baseline

3.12.8 Allocated Baseline

3.12.9 Functional Baseline

3.12.10 Configuration Control

3.12.11 Notification of Changes to Commercial Equipment/Software

3.13 Parts Management

3.14 Item Unique Identification (IUID)

3.14.1 Parent End Item Data Plate Information

3.14.2 Sub Assembly Data Plate Information

3.15 Diminishing Manufacturing Sources and Material Shortages (DMSMS)

3.16 Commercial and Non-Developmental Items (CaNDI)

3.17 Integrated Logistic Support

3.18 Logistics Management Information (LMI)

3.18.1 Buy Through the Prime (BTTP) (Option)

3.18.2 Warranty Performance System

3.18.2.1 Standard Commercial Warranty

3.18.3 Maintenance Planning

3.19 Supply Support

3.19.1 Provisioning Conference

3.20 Training Products and Services

3.20.1 Training Products

3.20.1.1 Modeling and Simulation Verification and Validation (M&S V&V) Report - Option 47

3.20.1.2 Manpower and Personnel Analysis (MA)

vi

3.20.1.3 Training Conduct Support Document (TCSD)

3.20.2 Training Services

3.20.2.1 Instructor-Operator-Maintainer Training Courses

3.20.2.2 Maintenance Training Courses

3.21 Technical Publications

3.21.1 Technical Documentation Orientation Conference (TDOC)

3.21.2 Technical Manuals

3.21.3 Commercial Manuals

3.21.4 Copyright Release

3.22 Packaging

3.23 Training System Installations and Support

3.24 Interim Contractor Support (ICS) (Option)

3.24.1 ICS Responsibilities

3.24.2 ICS Transition

3.25 Trainer Equipment Disposal

1 SCOPE

This Statement of Work (SOW) provides guidance to design, develop, integrate, test, install, produce and prepare associated documentation, provide an information assurance compliant system, provide logistic support, provide technical and maintenance support, provide training, and develop operation, maintenance and technical manuals for the Indoor Simulated Marksmanship Trainer - Upgrade (ISMT).

1.1 System Overview

The ISMT shall be a three-dimensional, simulation-based system for indoor use capable of instructing in basic and advanced marksmanship, shoot/no-shoot judgment, combat marksmanship, supporting arms, and weapons employment tactics. The ISMT system shall consist of an Instructor/Operator Station (IOS), audio/visual system, host computer, input/output network system, and weapons. The ISMT systems shall be used both within the Continental United States (CONUS) and Outside Continental United States (OCONUS). The ISMT shall be capable of being deployed on US Navy ships and US embassies.

1.2 Definitions

1.2.1 Acquisition Streamlining

This effort will incorporate acquisition streamlining where appropriate. Acquisition streamlining includes any efforts that result in more efficient and effective use of resources to develop, produce or deploy quality systems. This effort includes ensuring that only necessary requirements are included, at the most appropriate time in the acquisition cycle, in the design, development or production of new systems and/or for integration of existing simulated weapon components.

1.2.2 Contract Requirements

In addition to specified performance requirements, Contract Requirements include those defined in the SOW; Product Requirements, International Standards Organization (ISO) Standards, and the Contract Data Requirements List (CDRL); management systems; and contract terms and conditions.

1.2.3 Commercial Item

Per the Federal Acquisition Regulations (FAR), Part 2.101, “Commercial Item” means:

a. Any item, other than real property, that is of a type customarily used for non- Governmental purposes and that--

(1) Has been sold, leased, or licensed to the general public; or,

(2) Has been offered for sale, lease, or license to the general public;

http://www.arnet.gov/far/

b. Any item that evolved from an item described in paragraph a. of this definition through advances in technology or performance and that is not yet available in the commercial marketplace, but will be available in the commercial marketplace in time to satisfy the delivery requirements under a Government solicitation;

c. Any item that would satisfy a criterion expressed in paragraphs a. or b. of this definition, but for-

(1) Modifications of a type customarily available in the commercial marketplace; or

(2) Minor modifications of a type not customarily available in the commercial marketplace made to meet Federal Government requirements. Minor modifications mean modifications that do not significantly alter the non- Governmental function or essential physical characteristics of an item or component, or change the purpose of a process. Factors to be considered in determining whether a modification is minor include the value and size of the modification and the comparative value and size of the final product. Dollar values and percentages may be used as guideposts, but are not conclusive evidence that a modification is minor;

d. Any combination of items meeting the requirements of paragraphs a., b., c., or e. of this definition that are of a type customarily combined and sold in combination to the general public;

e. Installation services, maintenance services, repair services, training services, and other services if such services are procured for support of an item referred to in paragraphs a., b., c., or d. of this definition, and if the source of such services--

(1) Offers such services to the general public and the Federal Government contemporaneously and under similar terms and conditions; and

(2) Offers to use the same work force for providing the Federal Government with such services as the source uses for providing such services to the general public;

f. Services of a type offered and sold competitively in substantial quantities in the commercial marketplace based on established catalog or market prices for specific tasks performed under standard commercial terms and conditions. This does not include services that are sold based on hourly rates without an established catalog or market price for a specific service performed;

g. Any item, combination of items, or service referred to in paragraphs a. through f., notwithstanding the fact that the item, combination of items, or service is transferred between or among separate divisions, subsidiaries, or affiliates of a contractor; or

h. A Non-Developmental Item, if the procuring agency determines the item was developed exclusively at private expense and sold in substantial quantities, on a competitive basis, to multiple State and local Governments.

1.2.4 Non-Developmental Items (NDI)

Per the Federal Acquisition Regulations, Part 2.101, NDI means:

a. Any previously developed item of supply used exclusively for Governmental purposes by a Federal agency, a State or local Government, or a foreign Government with which the United States has a mutual defense cooperation agreement;

b. Any item described in paragraph a. of this definition that requires only minor modification or modifications of a type customarily available in the commercial marketplace in order to meet the requirements of the procuring department or agency;

or

c. Any item of supply being produced that does not meet the requirements of paragraph

a. or b., solely because the item is not yet in use.

1.2.5 Trainer Peculiar Equipment (TPE)

The following types of equipment are defined as TPE:

a. Trainer equipment which has not been classified by the Government as a Commercial Item, "NDI that is exempt from TPE requirements", Government-Furnished Equipment (GFE), or Contractor Acquired Operational Equipment (CAOE), and which is to be delivered to the Government as a result of the requirements of the contract.

b. Trainer equipment, which is to be delivered to the Government as a result of the requirements of the contract, which has been classified as a Commercial Item, NDI, GFE, or CAOE, and:

(1) Needs other than minor modifications (see 1.1.3, c., (2)) or modifications which are not of a type customarily available in the commercial marketplace to meet the requirements of the contract, or:

(2) Has insufficient existing product documentation for Government logistic support.

1.2.6 Interim Contractor Support (ICS)

Temporary contractor support that allows a Service to defer investment in all or part of required support resources (spares, technical data, support equipment, training equipment, etc.) while an organic support capability is phased in.

1.2.7 Intial Support Kit (ISK)

The Initial Support Kit (ISK) would typically include:

a. Spares (repairable items) and repair parts that are manufactured, subcontracted, or modified by the prime contractor having the design control responsibility.

b. Spares that support vendor hardware utilitzed by the device, which can be procured on the open market or from established sources and for which the prime contractor is not the design activity.

http://www.arnet.gov/far/

c. Support items that are not an integral part of the end item, but are required to inspect, test, calibrate, service, repair, or overhaul the end item, which are manufactured, subcontracted, or modified by the prime contractor having the design control responsibility.

d. Items required for support of the trainer system (excluding common hand tools), which can be procured on the open market or from established sources and for which the prime contractor is not the design activity.

1.3 Security Requirements

The information provided to the contractor will be unclassified and sensitive unclassified information. All contractor personnel requiring access to U.S. government sensitive Information and Data shall possess a completed background investigation (minimum of a NACI) for this Public Trust Position. The prime contractor and all sub-contractors (though the prime contractor) shall certify in writing to the Government that personnel supporting this contract are "Qualified U.S. contractors" per DoD Directive 5220.22-M Chapter 2. Qualified U.S.

contractors are restricted to U.S. citizens, persons admitted lawfully into the United States for permanent residence, and are located in the United States. All personnel identified on the certification and/or supporting this contract shall be in compliance with Department of Defense, Department of the Navy, and Marine Corps Information and Personnel Security Policy to include completed background investigations (as required) prior to start. The Government shall assist the contractor in gaining access to Government agencies and installations related to the systems in question.

When/if access to classified information is required after contract award; a DoD Contract Security Classification Specification (DD Form 254) will be issued as an attachment to a contract modification. The contractor would then require a valid Facility Clearance (at the appropriate level) prior to classified performance. The contractor would also require Safeguarding (at the appropriate level) prior to hosting classified meetings at the contractor’s facility.

NOTE: Public Trust Position: To ensure reciprocity, contract trustworthiness determinations (NACI) will be completed by OPM and sent to the Department of the Navy, Central Adjudication Facility (DONCAF). The DoNCAF will forward a disk (containing the NACI results) to this command for a local risk determination. The local risk determination decision will be recorded on the INV FORM 79A and then returned to OPM for inclusion into the Central Verification System. Favorable trustworthy determinations will support public trust positions only. This scope of investigation does not meet the standards for clearance eligibility.

2 APPLICABLE DOCUMENTS

The following documents listed form a part of this SOW. The most recent revision of the referenced document at the time of contract shall be used unless otherwise specified. In the event of a conflict between documents referenced herein and the contents of this SOW, the contents of this SOW take first precedence with the exception that nothing in this SOW shall be interpreted to allow reduction or elimination of the ISMT System Specification Requirements hereafter referred to as Specification. Nothing in this SOW, however, supersedes applicable laws and regulations, unless a specific exemption has been obtained. This SOW is designated as a first tier document. The documents referenced directly in this SOW are designated as second tier documents and are considered part of this SOW to the extent specified herein. Documents referenced in successive tiers are not part of this SOW and are to be used for guidance only.

2.1 Government Documents

MIL-PRF-29612 Training Data Products

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

MIL-STD-882 Standard Practice for System Safety

MIL-STD-961 Defense and Program-Unique Specifications Format and

Content

MIL-STD-129P(4) Military Marking for Shipment and Storage

MIL-STD-2073-1E(1) Standard Practice for Military Packaging

MIL-STD-3018 Parts Management

DI-MISC-80508B Technical Report / Study Services (LB)

NAVSEAINST 9310.1B Naval Lithium Battery Safety Program

TM S9310-AQ-SAF-010 Batteries, Navy Lithium Safety Program Responsibilities and Procedures

DoDI 8500.2 Information Assurance (IA) Implementation

DoDI 8510.01 Information Assurance Certification and Accreditation

Process (DIACAP)

DoDI 8500.01E Information Assurance

DoDI 8570.01M DoD Computer Network Defenses (CND) Service Provider

Certification and Accreditation Process Program Manual

USMC IA Guidance and Bulletins

MARCORSYSCOM IV&V PM Guidebook

Marine Corps Certifying Authority (CA) Life Cycle

Management Guidebook

DON DIACAP Handbook

DFARS 252.239-7001 Defense Federal Acquisition Regulations Supplement

(DFARS)-Information Assurance Contractor Training and Certification (DFARS Clauses are downloadable from http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/d fars/Dfar1TOC/htm#TopOfPage)

2.2 Military Standards and Specifications - Guidance Only

MIL-STD-2073-1 Standard Practice for Military Packaging

CMS-1A/21A Communications Security Material System Policy and Procedures Manual

DI-PACK-80120C Preservation and Packing Data

DI-PACK-80121C Special Packaging Instructions

ASTM D4169 Standard Practice for Performance Testing of Shipping Containers and Systems

2.3 Federal Standard - Mandatory

29 CFR 1910, Subpart Z Toxic and Hazardous Substances, Occupational Safety and Health Administration (OSHA)

2.4 Handbooks - Guidance Only

MIL-HDBK-61A Configuration Management Guidance

2.5 Other Government Documents

Not Applicable.

2.7 Non-Government Documents

ASME Y14.100 Engineering Drawing Practices

ASME Y14.34 Associated Lists

EIA-649 National Consensus Standard for Configuration

Management

ANSI/ASQC-Q9000 Quality Management and Quality Assurance Standards –

Guidelines for Selection and Use

ANSI/ASQC Q9002 Quality Systems – Model for Quality Assurance in

Production, Installation, and Servicing

ANSI/ASQC-Q9004 Quality Management and Quality System Elements

3 REQUIREMENTS

3.1 General

The contractor shall perform all tasks required and delineated in this SOW to design, develop, integrate, test, produce, manufacture, deliver and prepare associated documentation, provide logistic support, provide technical support, provide field service support, provide training, develop technical manuals and deliver the ISMT in the quantity specified in the contract. The contractor shall provide all materials, equipment, hard tooling, personnel, and facilities necessary to manufacture, fabricate, integrate, produce, and deliver the types and quantities of deliverables specified by the contract. Upon successful completion of developmental test, operational test, first article test, the Government may exercise contract options for integration, production, and fielding.

3.2 Program and Data Management

3.2.1 General

The contractor shall organize, coordinate, and control all program activities to ensure compliance with the contract requirements and the timely delivery of the required product and services. The contractor shall provide the necessary system engineering, design engineering, materials, services, equipment, testing, technical, management, logistics, manufacturing, and clerical support for the efforts described in this SOW and the ISMT Specification. The contractor shall report the progress of all the work performed under the contract. The contractor shall prepare Contractor Progress, Status, and Management Reports IAW CDRL B001.

3.2.2 Integrated Project Management

The contractor shall integrate and manage all of the program management, engineering, and logistics disciplines necessary for the manufacture, test, delivery, and Interim Contract Support (ICS) for the ISMT system.

3.2.3 Integrated Product Team (IPT)

The contractor shall establish a Government/contractor Integrated Product Team (IPT) partnership that is beneficial to achieving program goals and reduces the overall level of Government oversight required. The IPT shall be made up of representatives from each of the functional areas and of program management representatives. During the IPT meetings, the Integrated Master Schedule (IMS) will be reviewed along with the risk management plan and action items.

3.2.3.1 Working Groups

The working groups shall be established by the IPT for scenario development, training product content, and additional working groups as requested by the Government.

3.2.3.1.1 Scenario Working Group

The objective of this working group shall be to create, review, document and modify scenarios to be accepted by the Government.

3.2.3.2 Communications

A written record of all decisions and updates to the IMS shall be made after each IPT meeting and distributed by the contractor via email to members of the IPT. IPT meetings (teleconferences) shall be held as needed. Face-to-face meetings shall be arranged at a time and location appropriate to the program phase only as needed.

3.2.4 Program Management

The contractor shall establish and maintain program management practices throughout the period of performance. Program management practices shall provide visibility into the contractor’s organization and techniques used in managing the program, specifically subcontractor and data management. Documentation shall be readily available to Government representative(s) as needed. The contractor shall prepare Contractor Progress, Status, and Management Reports

IAW CDRL B001.

3.2.4.1 Integrated Master Schedule (IMS)

The contractor shall develop and maintain an IMS for the entire program IAW CDRL B002.

The IMS shall be included with the Contractor’s Progress, Status and Management Reports submission. The IMS shall be a tiered scheduling system showing all critical milestones and prerequisite events. The lower tiered schedules shall display increasing levels of detail.

Subcontractor schedules shall be integrated into the contractor’s scheduling system. The contractor shall notify the Government in writing of any anticipated or projected work stoppages or delays that will impact schedules.

3.2.4.2 Milestones

The IMS shall include all critical program milestones comprising conferences, meetings, design reviews, data and equipment delivery dates, GFE/GFI/GFS delivery dates, testing events, installation dates, and Ready for Training (RFT) dates. A milestone status summary shall be provided during all conferences and meetings. The contractor shall construct the schedule to assure that these milestones shall be met and to assure deliveries as specified in the contract.

3.2.4.3 Risk Management Program (RMP)

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 risk management on all areas of performance called out under this contract that directly impacts desired outcomes and involves risk-management preparation, risk identification, risk assessment, risk-handling option assessment, risk analysis, risk mitigation and risk control. Risk management to all key program objectives shall be covered at all program and technical reviews.

The contractor shall use the contractor’s internal risk management tools to perform risk management. The contractor shall provide insight to the Government into the contractor’s tools, assessment, mitigation, and control. Risk management shall be documented as part of the monthly Contractor Progress, Status, and Management Reports IAW CDRL B001.

3.2.4.3.1 Risk Mitigation

For each risk, a mitigation strategy to minimize any impact on the overall program schedule and performance shall be identified. Mitigation strategies may include such approaches as redundant capabilities, alternate vendors, or alternate solutions.

3.2.5 Subcontractor Management

The contractor shall be responsible for the performance of requirements delineated in this SOW and shall institute appropriate management actions relative to subcontractor performance.

Requirements that are contractually specified shall apply equally to subcontractor performance;

however, the contractor shall be accountable for the subcontractor’s compliance and is responsible for ensuring all deliverable products comply with the contract requirements.

3.2.6 Data Management

The contractor shall establish a single, centralized system for management of all data required under this contract. The contractor, in developing information that shall be furnished to the Government, shall make the maximum use of existing data and provide maximum multiple use of technical information. Any electronic databases or applications used to store, track, share, transmit or display information pertaining to this contract shall be made available to the Government within the next business day of the request. Government use of the contractor’s data management system shall not require installation of client software on Government computer systems (with the exception of Internet Explorer and Microsoft Office). Specific data management functions shall include schedule control for deliverables, maintenance of deliverables, delivery of data in required format, and distribution and delivery of data products.

The contractor shall include facilities for storage of all data developed or utilized for this contract, and shall provide equal access to data by the Government. The contractor shall ensure all data is available for Government review to ensure continuity of the system fabrication and supporting documentation. The Government reserves the right to review all data associated with and developed for the ISMT.

3.2.6.1 Technical Proposal

The contractor's Technical Proposal, as negotiated and accepted by the Government, shall be incorporated by reference into the resultant contract.

3.2.6.2 Assignment of Responsibility and Authority

The contractor shall identify the organizational elements responsible to conduct the activities delineated in this SOW. Responsibilities shall be assigned and clear lines of authority defined for determining and controlling the resources necessary to satisfy each element of this SOW.

The contractor shall notify the Government within ten (10) days of any changes regarding personnel changes made by the contractor during the period of performance.

3.3 Government Furnished Property

3.3.1 Government Furnished Equipment (GFE)

The Government will notify the contractor of the availability of Government Furnished Equipment (GFE). Items will be provided to the contractor within 60 days of receipt of contractor's written request to the Government. Proposals shall list required delivery date of GFE to meet proposed delivery schedules. The contractor shall provide for accountability, security and storage for the GFE provided. The contractor shall inspect and inventory all GFE received and identify and report any discrepancies/deficiencies to include associated costs (materials, labor and test (if applicable)) for repair of the GFE to like new conditions. Upon approval by the Government, the contractor shall conduct the necessary repair actions. The Government will forward an accountability agreement to the contractor for signature on an annual basis via DD-1149, Requisition and Invoice Shipping Document. See Appendix B, Table B-1 and B-2 of the ISMT Spec. GFE provided for modification shall become the responsibility of the contractor for maintenance, repair and upkeep.

3.3.2 Government Furnished Information

The Government will provide the Government Furnished Information (GFI) identified in the contract upon written request from the contractor to the Government. The contractor shall notify the Government of any deficiencies in the GFI received. GFI to be provided includes V&V Plan, ISMT Spec Appendices A-K, and any additional items listed in the SOW.

3.4 Meetings, Reviews, Conferences

3.4.1 Contractor Responsibilities

The contractor shall plan, host, attend, coordinate, support and conduct the meetings, reviews, and conferences. The reviews shall be conducted at Government and contractor facilities.

Reviews requiring demonstration and/or examination of equipment shall be conducted at the contractor's facility. All such reviews shall be included in the program schedule and may be held concurrently with the Government’s approval. The contractor shall prepare agendas IAW CDRL B003 and conference presentation materials, and provide minutes IAW CDRL B004 and reports following each review. The Government reserves the right to cancel any review or to require any review to be scheduled at critical points during the period of performance. Action item documentation, assignment of responsibility for completion and due dates shall be determined prior to adjournment of all reviews. A summary of all action items, responsible parties, and estimated completion dates shall be included with the minutes. Except where noted herein, conferences and reviews shall be considered fulfilled when the following items are completed:

a. A formal meeting has been conducted and the conference and reviews are presented to the Government

b. Topics required for discussion and presentation have been covered

c. Action items requiring contractor response have been resolved

d. The Government has accepted the conference minutes

3.4.2 Post Award Conference (PAC)

The contractor shall host a Post Award Conference (PAC) at the contractor's facility within 30 days after Contract Award. The PAC shall be conducted jointly by the Government and the contractor. The purpose of the PAC is for the contractor to review and demonstrate to the Government the management procedures, provide progress assessments, review of technical and other specialty area status, and to establish schedule dates for near term critical meetings/actions.

The contractor shall present management, key personnel, and program implementation processes. At the PAC, the contractor shall present an IMS showing the critical milestones and supporting events, including logistics, leading to these milestones. The PAC shall include the presentation and discussion of information and data relating to:

a. Introduction and Contract Overview

b. Discussion and clarification of Spec and SOW requirements

c. Identification of the critical paths within the IMS

d. CDRL delivery schedule and status

e. Program specific Risk Management Planning approach and processes

f. Program IA Implementation Planning approach and processes

g. IPT structure, membership, and responsibilities

h. Action item reporting and status

i. Long lead time item identification and status

j. Updated team contact list (names, IPT memberships, phone numbers, and email address)

k. Defense Reutilization Management Office (DRMO) activities

3.4.2.1 PAC Entry Criteria

Entry criteria for the PAC shall consist of Government concurrence with the following:

a. Contractor-submitted PAC agenda is complete and acceptable

3.4.2.2 PAC Exit Criteria

Exit criteria for the PAC shall consist of Government concurrence with the following:

a. Required PAC topics have been satisfactorily presented, discussed, and documented

b. Critical path discussions are complete, accurate, and realistic

c. IPT structure, membership, and responsibilities are satisfactorily defined, documented, and implemented

d. PAC minutes and presentation materials have been submitted and accepted

e. Action items have been assigned with suspense date for closure

f. Establishment of all required working groups as requested by the Government

g. Government will provide V&V Plan

3.4.3 System Requirements Review (SRR)

The contractor shall conduct an SRR as part of the PAC or within 30 days of completion of the PAC. The SRR is intended to confirm that the systems requirements and derived functional requirements have been translated into system specific technical requirements. The SRR shall demonstrate system requirements and derived functional performance requirements are defined and consistent with cost, schedule, defined system constraints, risk and that risks are well understood and mitigation plans are in place. The SRR is a multi-disciplined product and process assessment to ensure that the system under review can proceed into preliminary production, and that all system requirements and derived functional performance requirements are defined and consistent with cost, schedule, risk, and other system constraints. The SRR shall assess the system functional requirements and ensure that all required system performance is fully decomposed and is traceable to the Government provided System Specification. At the SRR, the contractor shall:

a. Identify and discuss resource availability to support the schedule

b. Present and discuss a schedule Critical Path (IMS)

c. Provide current status vs. Critical Path

d. Provide a complete program organizational structure

e. Identify relevant contractor subject matter experts (SMEs) to be used during development and testing

f. Show that all functional requirements are traceable to the system requirements

g. Show that all explicit and derived requirements are quantified and documented

h. Address the following applicable functional areas:

(1) Electromagnetic Environment Effects (E3)

(2) Environment, Safety, and Occupational Health

(3) Logistics

(4) Technical Data (Data management and CDRL status)

(5) Facilities

(6) Information Assurance

(7) Quality Management

(8) Configuration Management

i. Present the results of a comprehensive risk assessment for design, integration, and test.

3.4.3.1 SRR Entry Criteria

Entry criteria for the SRR shall consist of:

a. Government concurrence that the PAC exit criteria have been met.

b. Delivery and acceptance (when applicable) of all the CDRL items scheduled to be delivered prior to SRR.

c. Government concurrence that the contractor submitted SRR agenda is complete and acceptable.

d. All PAC action items requiring contractor response have been completed and closed.

e. IMS is resourced at reasonable levels with realistic performance expectations.

f. Program technical risks identified.

g. Program execution risks identified.

3.4.3.2 SRR Exit Criteria

Exit criteria for SRR shall consist of Government determination of acceptable risk in all the SRR elements listed above, and in the following specific criteria:

a. All SRR issues were captured in Requests for Action (RFAs) and properly adjudicated and assigned.

b. All SRR RFAs were completed (closed).

c. The required technical areas were represented at the review.

d. Functional requirements, as disclosed, will satisfy the training needs.

e. System functional definition and functional decomposition is detailed enough to support preliminary detailed production.

f. System Functional Baseline been established to enable preliminary design to proceed under Configuration Management

g. Processes and metrics are in place

h. Risks are identified and are manageable for implementation of the functional requirements

i. Program schedule is executable within the anticipated cost and technical risks

j. Program is properly staffed.

k. Requirements Verification Traceability Matrix (RVTM) has been submitted. RVTM depicts hierarchical relationships between the system specification requirements and the contractors system requirements

3.4.4 Preliminary Production Review (PPR)

The contractor shall conduct a Preliminary Production Review (PPR). The purpose of the PPR is for the Government to formally review the activities and work products generated by the contractor during the performance of the preliminary production stage and to verify that the approach for the system production is ready to proceed into the detailed production phase. The contractor shall present and describe the training system and program status. The following items shall be topics of discussion and presentation at the PPR:

a. Training system hardware and software, including:

(1) Instructor Operator Station (IOS)

(2) Trainee station

(3) Computational system

(4) Visual system

(5) Communication and audio systems

(6) Network

(7) Instructional system

(8) Software tools

(9) Use of developmental and Commercial and Non-developmental (CaNDI) software and databases

(10) Trainer databases

(11) Software development files

(12) Hardware and software interfaces

(13) Design modularity and commonality

(14) Facility Integration Planning

b. Electromagnetic Environmental Effects (E3) impacts

c. Reliability and Maintainability (R&M), and Systems Safety program progress, including

R&M predictions and preliminary identification of hazards

d. Logistics aspects and concerns

e. Parts management program progress and identification of long lead time items

f. Item Unique Identification (IUID) marking of trainer equipment and the Initial Spares Kit

(ISK)

g. Test and evaluation

h. Information Assurance (IA)

i. Program problem and risk areas, recommended solutions, and evaluation of alternatives

j. Requirements Verification Traceability Matrix (RVTM) has been submitted portraying hierarchical relationships between the system requirements and the component requirements.

3.4.4.1 PPR Entry Criteria

Entry criteria for the PPR shall consist of:

a. SRR exit criteria met

b. Delivery of all the CDRL items scheduled to be delivered prior to PPR

c. Availability of updated RTVM showing traceability of requirements

d. Development of risk assessments and risk mitigation plans

e. R&M requirements have been allocated to the design

f. IMS shows critical path through Critical Production Review (CPR)

g. Program technical risk medium or lower

h. Program execution risk medium or lower

i. Submittal and acceptance of the PPR agenda

3.4.4.2 PPR Exit Criteria

Exit criteria and final acceptance of the PPR shall consist of:

a. Satisfactory discussion of the CDRL items that were part of the PPR entry criteria

b. Updated RVTM demonstrates forward and backward traceability

c. Satisfactory discussion of risk assessments and risk mitigation plans. Risks and their respective mitigation plans are in place and manageable for implementation of the functional requirements into a preliminary design.

d. Program schedule is executable within the anticipated cost and technical risks

e. Program is properly staffed

f. Successful resolution and closure of all PPR action items

g. Availability of the PPR presentation materials

h. Per the IMS, an executable schedule has been presented within the existing budget

i. Submittal and acceptance of the PPR minutes

3.4.5 Critical Production Review (CPR)

The contractor shall conduct a CPR. The purpose of the CPR is for the Government to formally review the activities and work products generated by the contractor during the performance of the critical production stage and to verify that the system is ready to proceed into the hardware/software coding, assembly, and integration phase. The contractor shall present and describe the finalized training system and program status, and address all changes made since the PPR. The following items shall be topics of discussion and presentation at the CPR:

a. Training system hardware and software, including:

(1) IOS

(2) Trainee station

(3) Computational system

(4) Visual system

(5) Communication and audio systems

(6) Network

(7) Instructional system

(8) Software tools

(9) Use of developmental and CaNDI software and databases

(10) Trainer databases

(11) Software development files

(12) Hardware and software interfaces

(13) Design modularity and commonality

(14) Facility Integration Planning

b. E3 impacts

c. R&M and System Safety programs progress, including updated R&M predictions and hazards analysis results

d. Logistics design aspects and concerns

e. IUID marking of trainer equipment and ISK

f. Parts management program status

g. Test and evaluation

h. IA

i. Program problem and risk areas, recommended solutions, and evaluation of alternatives

j. Updated RVTM demonstrates forward and backward traceability.

3.4.5.1 CPR Entry Criteria

Entry criteria for the CPR shall consist of:

a. PPR exit criteria met

b. Delivery of all the CDRL items scheduled to be delivered prior to CPR

c. Availability of updated RVTM demonstrates forward and backward traceability.

d. Availability of updated risk assessment and risk mitigation plans

e. Risks and their respective mitigation plans are in place and manageable for implementation of the functional requirements into a preliminary design

f. R&M requirements have been addressed in the design

g. All trade-off analyses complete

h. Logistics Analysis complete and plans established

i. Facility Integration Planning complete

j. IMS shows critical path through testing

k. Final scenarios accepted by the Government

l. Submittal and acceptance of the CPR agenda

3.4.5.2 CPR Exit Criteria

Exit criteria and final acceptance of the CPR shall consist of:

a. Satisfactory discussion of the CDRL items that were part of the CPR entry criteria

b. The updated RVTM demonstrates forward and backward traceability.

c. Satisfactory discussion of updated risk assessments and risk mitigation plans. Risks and their respective mitigation plans are in place and manageable for implementation of the functional requirements into a final design.

d. Program schedule is executable within the anticipated cost and technical risks

e. Program is properly staffed

f. Successful resolution and closure of all CPR action items

g. Availability of the CPR presentation materials

h. Per the IMS, an executable schedule has been presented within the existing budget

i. Submittal and acceptance of the CPR minutes.

j. Allocated baseline has been established

3.4.6 In-Process Reviews (IPRs)

In Process Reviews (IPR) shall be held at a minimum quarterly or as needed, at a date and location mutually agreed upon. The Government reserves the right to cancel any review or to require any review to be scheduled during the period of performance. The contractor’s progress, management, technical support services, integrated logistics support, administrative, assurance of compliance with contract requirements, program status, funding, problem identification and resolutions shall be agenda items. Actual versus expected performance of each area shall be addressed. The contractor shall prepare presentation materials providing an overview of all agenda items.

The IPR agenda shall include review of the following:

• Contractor’s progress to include, but not limited to, the status of the overall program, including the training system design (hardware and software), Quality Management System (QMS), CM, E3, testing, and production

• Management

• Technical support services (if any)

• Integrated logistics support program review

• Administrative

• Assurance of compliance with contract requirements

• Program schedule status

• Funding Status

• Problem identification and resolution

• Review of program risks

• Review of updated RVTM

3.4.6.1 Technical Documentation (TD) IPRs

The contractor shall hold and participate in technical documentation (TD) IPRs for each manual or group of manuals to be held at the contractor’s facility, Electronic Data Transfer (EDT) or Video Teleconference Call (VTC) on mutually agreed dates, at approximately the 30 percent and 80 percent completion points of the deliverable TD. The TD IPRs shall be IAW the Technical Manual Contract Requirements (TMCR). The contractor shall satisfy the entry and exit criteria for each TD IPR as described in the TMCR. The contractor shall prepare the Conference Agenda and Conference Minutes for each TD IPR IAW CDRL B004. The contractor shall meet following entry and exit criteria for the required IPRs:

3.4.6.1.1 30 percent TD IPR Entry Criteria

Entry criteria for the 30 percent TD IPR shall consist of Government concurrence for the following:

a. Tentative date for 30 percent IPR is listed in the IMS

b. Agenda approved by Government

c. Review draft copies of TD available IAW CDRL requirements

d. Contractor’s plan for TD Quality Assurance (QA) (to include plans for performing

Validation) is available for review

e. Maintenance significant drawings are in development and a list is available for review

f. Subsystems identified to Line Replaceable Unit (LRU) level of assembly

g. O&M manual text (including Preventive Maintenance System (PMS) and

Instructor/Operator information) is in development (Description, Installation, Operation, Theory of Operation, Maintenance tasks) and approximately 30 percent complete

h. COTS Manuals listing available for review

i. Acquired COTS Manuals available for review

j. Request for Government reproduction rights forwarded to vendors, copies available for

Government review.

3.4.6.1.2 30 percent TD IPR Exit Criteria

Exit criteria for the 30 percent TD IPR shall consist of Government concurrence for the following:

a. Submittal and acceptance of 30 percent TD IPR minutes

b. Action items assigned with suspense dates, as required

c. Comments/discrepancies identified during TD IPR documented

d. Schedule for 80 percent TD IPR tentatively established

e. Contractor’s plan for TD QA has been reviewed; plan for validation is acceptable

f. Format and content of draft documentation reviewed meets requirements established in the TMCR and appropriate Data Item Descriptions (DIDs)

g. Maintenance significant drawing list is acceptable

h. COTS Manuals listing is acceptable

i. Available COTS Manuals are acceptable according to criteria in the TMCR or identified as requiring supplementation

j. Requests for Government reproduction rights for COTS Manuals have been forwarded to vendors.

3.4.6.1.3 80 percent TD IPR Entry Criteria

Entry criteria for the 80 percent TD IPR shall consist of Government concurrence for the following:

a. Agenda has been coordinated by the IPT

b. 30 percent TD IPR comments have been incorporated into the applicable documentation

c. Review draft copies of TD are prepared and distributed 30 days prior to TD IPR in numbers sufficient to support Government review during the TD IPR

d. COTS Manuals are identified and made available to the Government at the TD IPR

e. Text of O&M is complete to the extent of data available

f. Drawings are nearing completion and are available to the Government for review

g. Government/contractor IPT participation has been coordinated

h. Any completed validation records are available for Government review.

3.4.6.1.4 80 percent TD IPR Exit Criteria

Exit criteria for the 80 percent TD IPR shall consist of Government concurrence for the following:

a. Submittal and acceptance of 80 percent TD IPR minutes

b. Action items assigned with suspense dates

c. Comments/discrepancies identified during TD IPR documented

d. COTS Manual development and content are acceptable to the Government.

e. The progress of text development of the O&M is acceptable to the Government.

f. The progress of the COTS Manuals identification is acceptable to the Government.

g. The Drawings are reviewed and are acceptable to the Government.

3.5 Systems Engineering (SE)

The contractor shall plan, document, implement, and control an integrated technical effort IAW this SOW, to develop a total training system solution that meets the performance requirements of the training products of the contract.

3.5.1 Systems Engineering (SE) Process

The contractor shall apply a system engineering approach to produce the ISMT product baselines that are verifiable from functional baselines for all training products, as described in this SOW.

The contractor shall document, implement, control, and maintain a collection of technical plans, processes, and schedules necessary to guide the project toward accomplishment of its objectives and proper conclusion. The contractor shall establish a System Engineering Plan (SEP) that details the technical planning of the IMS. The SEP shall be the planning document for all technical efforts and shall describe the tailored application of the contractor’s SE Process. The SEP policies and procedures shall specify requirements for the planning, implementation, and control of product and process development. The contractor policies and procedures shall address the following:

a. The application of the SEP throughout the training system life cycle

b. The preparation and acceptance of the IMS

c. The preparation and acceptance of data deliverables

d. Monitoring and reporting technical progress of the program

e. The preparation for, and conduct of, technical reviews

f. The contents and maintenance of an integrated data repository

g. The implementation of the test and evaluation program

3.5.2 Requirements Analysis and Functional Allocation

The contractor shall perform and document an analysis to verify that all requirements from the ISMT specification, the SOW, and derived requirements are met and are traceable to each configuration item and subsequent lower level units of decomposition. The contractor shall develop a RVTM to document the results of this task.