AF_UH-60A_SOW.pdf

SOW No. SOW-2017-053

STATEMENT OF WORK

For

Afghanistan Air Force (AAF) Special Mission Wing (SMW)

UH-60A Flight Training Devices (FTDs)

ENGINEERING

Prepared By: ________________ Concurrence: _________________

Jorge Cadena Jeffery Miester

APM CENTCOM , PL FMS Chief Engineer, PM TRADE

Date: _______________ Date: _______________

ACQUISITION LOGISTICS

Prepared By: _________________ Concurrence: _________________

Joseph E. Cooper Roberto Capote

Acquisition Logistician, PL FMS Product Support Manager, PM TRADE

PRODUCT MANAGEMENT

Submitted By: _________________ Approved By: _________________

Jorge Cadena Roberto Gomez

APM CENTCOM, PL FMS Product Lead, Foreign Military Sales

U.S. Army Program Executive Office for

Simulation, Training, and Instrumentation (PEO STRI)

12350 Research Parkway

Orlando, FL 32826-3276

30 November 2017

CadenaJ Typewritten Text in lieu of

CadenaJ Typewritten Text

6-DEC-2017

CadenaJ Typewritten Text

6-DEC-2017

CadenaJ Typewritten Text

6-DEC-2017

joseph.e.cooper2 Typewritten Text

6 DEC 2017

Change History

Change Author Date

Table of Contents

1. SCOPE

2. APPLICABLE DOCUMENTS

3. REQUIREMENTS

3.1 System Requirements

3.2 System Design

3.2.1 Hardware Design

3.2.2 Software Design

3.2.3 Hardware and Software Integration

3.3 Supportability Engineering

3.3.1 Logistics Support

3.3.2 Spares

3.3.3 Licenses

3.3.4 Antiterrorism (AT)

3.3.4.1 AT Level 1 Training

3.3.4.2 Access and General Protection Policy and Procedures for Contractor Requiring

Common Access Card (CAC)

3.3.4.3 AT Awareness Training for US Based Contractor Personnel Traveling Overseas 8 3.3.4.4

3.3.4.4 Army Training Certification Tracking System (ATCTS) Registration for

Contractor Employees Who Require Access to Government Information Systems

3.3.5 Operations Security (OPSEC)

3.3.5.1 OPSEC Program

3.3.5.2 Requirement for OPSEC Training

3.3.5.3 Performance or Delivery in a Foreign Country

3.3.5.4 Threat Awareness Reporting Program (TARP)

3.3.5.5 Anti-Terrorism Awareness Training for contractor personnel traveling overseas . 9

3.3.5.6 Travel

3.3.6 Logistics Product Data

3.3.7 Technical Publications

3.3.7.1 Commercial Manuals

3.3.7.2 Operator User Manual

3.3.7.3 System Maintenance Manual

3.3.7.4 Publications Validation

3.3.7.5 Publications Verification

3.3.8 Obsolescence Management and Technology Insertion

3.3.9 Product Definition Data (PDD)

3.3.10 Item Unique Identification (IUID)

3.4 Safety Engineering

3.5 Packaging, Handling, Storage, and Transportation

3.6 Program Management

3.6.1 Financial Management

3.6.2 Personnel Conduct

3.6.3 Synchronized Pre-deployment and Operational Tracker (SPOT)

3.7 Integrated Product and Process Management (IPPM)

3.7.1 Integrated Master Schedule (IMS)

3.7.2 Program Reviews and Conferences

3.7.2.1 Program and Technical Reviews

3.7.2.2 Program Management Review (PMR)

3.8 Configuration Management (CM)

3.9 CM Process

3.10 Configuration Validation/Verification

3.10.1 Software Configuration Management

3.11 Quality Assurance

3.12 Integrated Testing and Inspections

3.12.1 Evaluation

3.12.2 Test Readiness Review (TRR)

3.12.3 Factory Acceptance Test (FAT)

3.12.4 Site Acceptance Test (SAT)

3.12.5 Test Discrepancies

3.13 Training Products

3.13.1 Operator Training

3.13.2 Maintenance Training

3.14 Site Requirements

Appendix A – Event Entrance and Exit Criteria

1. Post Award Conference (PAC)

1.1 PAC Entry Criteria

1.2 PAC Exit Criteria

2. SRR Entrance and Exit Criteria

2.1 SRR Entrance Criteria

2.2 SRR Exit Criteria:

3. PDR Entrance and Exit Criteria

3.1 PDR Entrance Criteria

3.2 PDR Exit Criteria

4. CDR Entrance and Exit Criteria

4.1 CDR Entrance Criteria

4.2 CDR Exit Criteria

5. Formal System Test (FAT/SAT) Entrance and Exit Criteria

5.1 Test Entrance Criteria

5.2 Test Exit Criteria

5.3 Test Discrepancy Priorities

1. SCOPE

The Afghanistan Air Force (AAF) Special Mission Wing (SMW) has a requirement for UH-60A

Flight Training Devices (FTDs). This Statement of Work (SOW) defines the effort for production, installation and support required for the UH-60A FTDs. The training devices, software, spares and associated technical data, including all operating, maintenance, and manufacturer documentation, shall be delivered and installed. The effort includes operator and maintenance training courses to be conducted immediately after Ready for Training (RFT). The contractor shall conduct installation and Site Acceptance Test (SAT) of the UH-60A FTD simulators in Afghanistan. After installation is complete The contractor shall also conduct two

(2) years of on-site Contractor Logistical Support (CLS) for each FTD.

2. APPLICABLE DOCUMENTS

In the event of a conflict between documents referenced herein and the contents of this SOW, the contents of the SOW shall be the governing requirement.

Document Document number Date

GENERAL

Identification Marking of U. S. Military Property UID

MIL-STD-130N

w/Change-1

16-NOV-2012

SYSTEM SPECIFICATION For The Afghanistan Air

Force (AAF) Special Mission Wing (SMW) UH-60A.

AF_UH-60A_SPEC 8-AUG-2017

US Army Training and Doctrine Command (TRADOC)

Force Protection

TRADOC REG 525-13 12-DEC-1997

Logistics Product Data Availability of Government

Documents, Drawings, and Publications

GEIA-STD-0007-B 1-AUG-2015

AIRCRAFT SPECIFIC

Operator Manual for Helicopter UH-60A

TM 1-1520-237-10

(CHANGE 10)

30 SEPT 2002

Operator and Crewmember Checklist Helicopter UH-60A TM 1-1520-237-CL 31 OCT 1996

Maintenance Test Flight Manual Helicopter UH-60A TM 1-1520-237-MTF 31 MAR 1997

3. REQUIREMENTS

3.1 System Requirements

The contractor shall provide all effort, resources, equipment, and personnel necessary to complete the tasks in this SOW and associated System Specification Document for the UH-60A

FTD Simulators. The contractor shall perform all activities to integrate the UH-60A FTD hardware and software to achieve a fully functional training system that performs and operates in accordance with this SOW and System Specification Document. The contractor shall verify the complete integration and installation on site of the hardware and software of each hardware and software subsystem and the overall system through the utilization of formalized test procedures.

3.2 System Design

The contractor shall use referenced documentation as the basis for development of all lower level specifications. The design concept shall incorporate an open systems approach. The design concept shall be based on an engineering and business strategy to choose specifications and standards adopted by industry standards bodies or de facto standards (set by the market place) for selected system interfaces, products, practices and tools. Selected designs and standards shall be based on performance, cost, industry acceptance, reliability, and supportability.

(DI-IPSC-81431A) System/Subsystem Specification (SSS)

3.2.1 Hardware Design

The contractor shall provide a design to integrate and assemble the system hardware that satisfies the system requirements. The contractor shall maximize the use of commercial and non-developmental items included in the design. The contractor shall apply the systems engineering process during each level of system design (system, subsystem, and component) to produce a system that satisfies the specified requirements, increases the probability of program success, reduces risk and reduces total-life-cycle cost.

3.2.2 Software Design

The contractor shall use systematic, documented methods for all software activities and establish and apply standards and practices for representing requirements, design, code, test cases, test procedures, and test results. Traceability shall be maintained between levels of requirements, between requirements and design, between design and the software that implements it, and between requirements and qualification test information. Computer hardware resource utilization requirements shall be established, measured, and documented.

The contractor shall integrate software components in a manner that meet all system requirements. The contractor shall design the system software and firmware in accordance with recognized industry standards and internal documented processes. The design shall incorporate features that promote ease of operation, ease of software maintenance, and that facilitate future updates and modifications.

Computer programs and computer data shall be fully integrated in accordance with system requirements. The contractor shall maximize the procurement and incorporation of commercial and non-developmental software. Networks and interface connections shall provide adequate throughput, update rates, and bandwidth to support worst case network traffic conditions.

(DI-IPSC- 81442A) Software Version Description (SVD)

3.2.3 Hardware and Software Integration

The contractor shall perform all activities to integrate and assemble the hardware and software to achieve a fully functional system that performs and operates in accordance with the system requirements. The contractor shall verify through independent testing or other means the viability of the complete integrated design of all hardware and software subsystems, and the overall system, through the utilization of formalized test procedures.

3.3 Supportability Engineering

3.3.1 Logistics Support

The contractor shall provide for two (2) years of Contractor Logistics Support (CLS) for each of the two (2) training devices. The CLS period will commence at the Ready for Training (RFT) date of the devices. The support will be provided by qualified UH-60A Field Engineers (FE).

The on-site CLS effort includes operation support, device maintenance, and material management. CLS technicians shall also perform daily Preventative Maintenance (PM) checks and initial “turn on” of the devices at the start of each training day and “shut down” at the conclusion of each training day. The contractor shall maintain configuration management of the device hardware and software baseline. The contractor shall review and track status of the delivered configuration of the hardware and software baseline. Operational Hours for the FTDs are eight (8) hours per day, five (5) days per week, 52 weeks per year. The contractor will maintain a minimum operational availability of 85%.

The contractor shall be required to provide transportation services for the simulators from the United States to the delivery location in Afghanistan. The SCO (or U.S. Government representative) will confirm receipt of all materiel deliveries.

3.3.2 Spares

The spare parts package will support the operation of the training systems during the two years of CLS. The spare parts package will be replenished as spares are used and contain the original range and quantity at the conclusion of the CLS period at contractor expense. Shipping cost for equipment and material for spares used in maintenance of the training devices will be at contractor expense.

A spare parts storage system (metal, enclosed and lockable bins) with a system for easy and rapid identification and retrieval of individual spare parts, tools, test equipment and other support equipment shall be provided as part of the delivered comprehensive spare parts and equipment package for the training system.

3.3.3 Licenses

The contractor shall provide licenses for hardware and software, as necessary to operate, maintain, and support the training systems. The licenses shall transfer to the U.S. Government at

Ready for Training (RFT).

3.3.4 Antiterrorism (AT)

3.3.4.1 AT Level 1 Training

All Contractor employees, to include Subcontractor employees, requiring access Army installations, facilities and controlled access areas shall complete AT Level I awareness training in accordance with AR381-12 within thirty (30) calendar days after contract start date or effective date of incorporation of this requirement into the contract, whichever is applicable. The contractor shall submit certificates of completion for each affected Contractor employee and

Subcontractor employee, to the COR or to the contracting officer, if a COR is not assigned, within thirty (30) calendar days after completion of training by all employees and Subcontractor personnel. AT level I awareness training is available at the following website: http://jko.jten.mil.

3.3.4.2 Access and General Protection Policy and Procedures for Contractor Requiring

Common Access Card (CAC)

Contractor and all associated Subcontractors employees shall provide all information required for background checks to meet installation access requirements to be accomplished by installation Provost Marshal Office, Director of Emergency Services or Security Office.

Contractor workforce must comply with all personal identity verification requirements (FAR clause 52.204-9, Personal Identity Verification of Contractor Personnel) as directed by DOD, HQDA and/or local policy. In addition to the changes otherwise authorized by the changes clause of this contract, should the Force Protection Condition at any individual facility or installation change, the Government may require changes in Contractor security matters or processes.

Before CAC issuance, The contractor employee requires, at a minimum, a favorably adjudicated

National Agency Check with Inquiries (NACI) or an equivalent or higher investigation in accordance with Army Directive 2014-05. The contractor employee will be issued a CAC only if duties involve one of the following: (1) Both physical access to a DOD facility and access, via logon, to DOD networks on-site or remotely; (2) Remote access, via logon, to a DOD network using DOD -approved remote access procedures; or (3) Physical access to multiple DOD facilities or multiple non- DOD federally controlled facilities on behalf of the DOD on a recurring basis for a period of 6 months or more. At the discretion of the sponsoring activity, an initial CAC may be issued based on a favorable review of the FBI fingerprint check and a successfully scheduled NACI at the Office of Personnel Management. Contractor shall be responsible for providing all adequate badging necessary for personnel supporting this effort requiring base installation access.

3.3.4.3 AT Awareness Training for US Based Contractor Personnel Traveling Overseas

All US based Contractor employees and associated Subcontractor employees must take

Government provided Area Of Responsibility specific AT awareness training as directed byAR

525-13. Specific Area Of Responsibility training content is directed by the combatant commander with the unit AT Office being the local point of contact.

3.3.4.4 iWATCH Training

The contractor and all associated Subcontractors shall brief all employees on the local iWATCH program (training standards provided by the requiring activity AT Office). This local developed training will be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity to the COR. This training shall be completed within 30 calendar days of contract award and within thirty (30) calendar days of new employees commencing performance with the results reported to the COR no later than sixty (60) calendar days after contract award.

3.3.4.4 Army Training Certification Tracking System (ATCTS) Registration for Contractor

Employees Who Require Access to Government Information Systems

All Contractor employees with access to a Government information system must be registered in the ATCTS at commencement of services, and must successfully complete the DOD Information

Assurance Awareness prior to access to the IS and then annually thereafter.

3.3.5 Operations Security (OPSEC)

3.3.5.1 OPSEC Program

The contractor shall develop an OPSEC Standing Operating Procedure (SOP)/Plan within 90 calendar days of contract award, to be reviewed and approved by the responsible Government

OPSEC officer. This plan will include a process to identify critical information, where it is located, who is responsible for it, how to protect it and why it needs to be protected. The contractor shall implement OPSEC measures as ordered by the commander. In addition, The contractor shall have an identified certified Level II OPSEC coordinator per AR 530-1.

3.3.5.2 Requirement for OPSEC Training

Per AR 530-1, Operations Security, new Contractor employees must complete Level I OPSEC training within thirty (30) calendar days of their reporting for duty. All Contractor employees must complete annual OPSEC awareness training. The contract shall ensure all applicable employees have completed OPSEC initial training and annual refresher training and shall certify that their work force has completed the training through the submission of completion certificates(s) to the COR within 30 30 days of arrival on the installation. OSPEC training can be accomplished at the Defense Security Services website at:

https://securityawareness.usalearning.gov/opsec/index.htm

3.3.5.3 Performance or Delivery in a Foreign Country

The contractor shall comply with DFARS clause 252.225-7043, Antiterrorism/Force Protection for Defense Contractors Outside the US. Non-local national Contractor personnel must comply with theater clearance requirements.

3.3.5.4 Threat Awareness Reporting Program (TARP)

For all Contractors with security clearances, per AR 381-12 Threat Awareness and Reporting

Program (TARP), Contractor employees must receive annual TARP training by a counterintelligence agent or other trainer as specified in 2-4b.

3.3.5.5 Anti-Terrorism Awareness Training for contractor personnel traveling overseas

All US based contractor employees and associated sub-contractor employees shall receive

Government provided area of responsibility (AOR) specific AT awareness training as directed by

AR 5

3.3.5.6 Travel

This contract will require contractor personnel to travel to, from and within CONUS (Contiguous

United States) and OCONUS (Outside Continental United States) locations as specified herein.

All travel shall be IAW with the Joint Federal Travel Regulations (JTR). The JFTR, while not wholly applicable to contractors, shall provide the basis for the determination as to the reasonableness and allow ability of all travel costs.

Contractor personnel traveling abroad shall possess a valid U.S. passport and all appropriate visas required to conduct the assigned overseas missions.

Contractor personnel traveling OCONUS shall complete the following before departing for

Afghanistan:

SERE (Survival Evasion Resistance and Escape) 100 Training

Attend CONUS Replacement Center (CRC) theater specific individual readiness training. This includes the following:

o Medical and dental testing o Theater specific training o Computer Based Training (CBT)

3.3.6 Logistics Product Data

The contractor shall record all hardware being delivered which will allow for the creation of parts lists, inventory records, property accountability, and property transfers. Prior to shipping to the fielding site. The contractor shall plan and conduct an inventory of the system equipment with a Government representative. The contractor, in conjunction with the Government, shall conduct a physical inventory of the hardware, spares / repair parts, special tools and test equipment (ST&TE). Upon completion of the inventory, representatives shall sign a hardcopy of the inventory record to ensure all required items are delivered and a baseline is established. The

Logistics Product Data (LPD) shall include indentured provisioning parts lists, recommended initial spare lists, special tools and test equipment lists, an Equipment Inventory Report (EIR), and all other required lists as stated in the LPD deliverable.The contractor shall ensure that the

LPD match the as-built configuration, in accordance with (IAW) GEIA-STD-0007-A.

(DI-SESS-81758A) Logistics Product Data

3.3.7 Technical Publications

The contractor shall prepare operation and maintenance manuals which shall accurately document all the information needed to keep the equipment operational for the training system.

The manuals shall provide system and subsystem oriented instructions for installation, operation, maintenance, and testing. The contractor shall describe each operation and maintenance task in detailed, logical, and systematic steps. All tools, test equipment and consumable items required to accomplish maintenance and installation shall be identified. Government furnished material, Government technical manuals or Government-approved commercial operation and maintenance manuals shall be used as references for system and subsystem maintenance. All publications shall reflect the configuration of fielded hardware as documented in the product baseline. The contractor shall deliver all technical publications in English.

3.3.7.1 Commercial Manuals

The contractor shall provide COTS manual(s) for all equipment used in the system.

(DI-TMSS-81816) Commercial Off-The-Shelf (COTS) Manual and Associated

Supplemental Data (C002)

3.3.7.2 Operator User Manual

The contractor shall provide an Operator User Manual (OUM) for all end items delivered. In the manual(s). The contractor shall describe each operator task in detail and in logical, systematic steps for the work to be accomplished. The manual(s) shall detail general information, equipment descriptions, theory of operation, special tools and associated equipment involved in operation, system set up, operator procedures/instructions, installation procedures, operator & preventive maintenance instruction, operational level troubleshooting procedures, and any other supporting information. It shall provide system and subsystem oriented instructions for installation, operation, maintenance, and testing. All special tools, test equipment, and consumable items required to accomplish any operator or install task shall be identified just prior to and as part of the task.

(MIL-STD-40051-2C) Page-Based Technical Manual

3.3.7.3 System Maintenance Manual

The contractor shall provide a System Maintenance Manual (SMM) for the overall system. This manual shall provide instruction for detailed installation, removal, replacement, fault isolation, general maintenance, and proper use of test equipment. The manual shall describe cold start and system initialization processes for each system/subsystem to include all configuration options and settings necessary to configure and initialize the system/subsystem in conformance with the documented product baseline. The SMM shall include piece-part information (drawings, computer aided design files, and meta data) as necessary. The SMM shall also include applicable associated lists that provide the design, engineering, manufacturing, and quality assurance information necessary to enable the procurement of an interchangeable item that duplicates the physical and performance characteristics of the original product, without an additional design engineering effort.

(MIL-STD-40051-2C) Page-Based Technical Manuals

3.3.7.4 Publications Validation

The contractor shall validate all technical publications, changes, supplemental data, and revisions before submitting them to the Government. Publications shall be validated prior to start of system testing. A technical publication shall not be ready for validation or verification until the following conditions have been fulfilled:

(a) Engineering technical review has been completed.

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

(c) Procedural instructions are clearly expressed and adequate to perform all operations and maintenance functions.

(d) All procedures have been performed to assure accuracy and completeness.

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

(f) Hardware of the proper configuration is available for the validation and verification effort.

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

3.3.7.5 Publications Verification

The contractor shall assist the Government in the verification of technical documentation to ensure its accuracy. The verification may be performed concurrently with the validation effort.

The contractor shall incorporate corrected discrepancies and changes resulting from training, testing and reviews into the technical publications. The contractor shall provide system equipment, technical and engineering support, and any other resources as required to aid in the completion of the verification effort.

3.3.8 Obsolescence Management and Technology Insertion

The contractor shall research, select, test, verify, validate, install, and deploy new technology as necessary to ensure that the deployed systems remain supportable in accordance with the supportability approach. The contractor shall make recommendations for incorporation of new technology and shall test and incorporate approved items. The contractor shall perform cost benefit analysis of candidates for technology insertion to provide necessary information to support Integrated Product Team (IPT) decisions.

3.3.9 Product Definition Data (PDD)

During the systems engineering and design phase, The contractor shall provide and deliver an initial version of the Product Definition Data (PDD). The contractor shall update and maintain the PDD so that it accurately reflects the final product. The PDD is the technical description of items adequate for supporting an acquisition strategy, and all production, engineering and logistics efforts. The PDD shall disclose complete design, logistics, manufacturing requirements, and the means of measuring compliance with the requirements. Piece part information (drawings, computer aided design files and meta data.) and associated lists shall provide the necessary design, engineering, manufacturing, and quality assurance information necessary to enable the procurement of an interchangeable item that duplicates the physical and performance characteristics of the original product, without additional design engineering effort or recourse to the original design activity.

(DI-SESS-81000E) Product Drawings and Associated Lists

(DI-SESS-81003E) Commercial Drawings/Models and Associated Lists

3.3.10 Item Unique Identification (IUID)

The contractor shall implement an IUID of tangible items program in accordance with MIL-STD

130N.The unique Item Identifier (UII) will be marked on the hardware IAW MIL-STD 130N.

The (UII) is a set of data that is globally unique, unambiguous, and robust enough to last through the life of the system/component. These requirements apply to developed and commercial items.

The contractor shall provide IUID labels for all systems, as necessary, in accordance with MTL-

STD 130N. Compliance of the IUID requirement shall be submitted through Wide Area Work

Flow (WAWF)

(DI-MGMT-81858) Unique Identification (IUID) Marking and Verification Report

3.4 Safety Engineering

The contractor shall provide and implement tasks and activities to identify, evaluate, and eliminate or control hazards throughout the systems life cycle. The contractor shall ensure the safety of the system's design, operation, transportation, maintenance, support, and disposal. The contractor shall conduct safety analyses, hazard identification and classification, and hazards tracking integral to the system design effort. A hazard risk index including hazard severity and hazard probability levels shall be developed for all hazards.

(DI-SAFT-80102C) Safety Assessment Report (SAR)

3.5 Packaging, Handling, Storage, and Transportation

The contractor shall pack, handle, and transport the trainers, training aids, and related components in accordance with best commercial practices. The contractor shall provide insurance for shipment of the training system. The contractor shall be responsible for obtaining export licenses for the training systems. The contractor shall be responsible for moving the simulators into the building where they will be installed.

3.6 Program Management

The contractor shall develop an overall plan for the management and administrative effort necessary to ensure that the requirements of this contract are accomplished. The contractor shall track program progress utilizing metrics. The contractor shall measure, monitor and assess the progress of the work performed and costs incurred under the contract. The government expects the structure of program management for this contract to be streamlined, responsive, flexible, and able to make decisions without unnecessary delays from staffing or bureaucratic processes.

When applicable the government will use an Integrated Product Team (IPT) approach to fulfilling requirements on this contract. The contractor shall track overall program, schedule, and payment status and provide invoicing as stipulated in the terms of the contract.

The contractor shall prepare The contractor’s Progress, Status and Management Report

(CPSMR), and shall ensure that all significant activity reportable during the month is addressed.

(DI-MGMT-80227) Contractor’s Progress, Status and Management Report (A001)

3.6.1 Financial Management

The contractor shall plan, budget, schedule, and control the resources allocated to meet the requirements of the contract. The contractor shall identify major elements of subcontracted work.

The contractor shall track the status of all appropriated funds associated with the contract, to include payments, cancellations and invoices against each contract line item and sub-line item.

3.6.2 Personnel Conduct

The contractor shall document and hold accountable all employees and subcontractors to a comprehensive ethical code of conduct. The contractor shall ensure that employees conduct themselves in accordance with applicable US and partner nation laws and regulations. The contractor shall take every action possible to ensure that its employees do not engage in activities that may embarrass or cause harm to the U.S. Government, the Department of Defense, PEO

STRI, or the Government of the applicable partner nation(s) within which its personnel are operating. Accordingly, Contractors shall be well-versed in policies related to ethics, behavior, receiving gratuities, or giving inappropriate gifts that may give the perception of improper behavior.

3.6.3 Synchronized Pre-deployment and Operational Tracker (SPOT)

SPOT has been designated as the Joint Enterprise contractor management and accountability system to provide a central source of contingency contractor information and a summary of contract services IAW DoDI 3020.41. Government representatives are required to maintain, by-name, contractor accountability within SPOT. Contractor administrators shall register for a

SPOT account at https://spot.dmdc.mil and provide the necessary information for all deploying contractor personnel. All contractor data shall be entered into the SPOT database for all

Contractor employees traveling to any OCONUS and CONUS location. The contractor shall coordinate with the Army Contracting Command (ACC) Procuring Contracting Officer (PCO), and respective Combatant Command (COCOM).

Contractor administrators shall register for a SPOT account at https://spot.dmdc.mil and provide the necessary information for all deploying contractor personnel. All contractor data shall be entered into the SPOT database for all Contractor employees traveling to any OCONUS and

CONUS location. The contractor shall coordinate with the ACC PCO, and respective COCOM.

Contractor personnel must have a Synchronized Pre-deployment and Operational Tracker

(SPOT)-generated letter of authorization (LOA) signed by the cognizant Government Procuring

Contracting Officer (PCO) in order to process through a deployment center or to travel to, from, or within the designated operational area. The letter of authorization also will identify any additional authorizations, privileges, or Government support that contractor personnel are entitled to under this contract.

3.7 Integrated Product and Process Management (IPPM)

The contractor shall execute a management technique that simultaneously integrates all essential acquisition activities through the use of multidisciplinary teams to optimize the design, manufacturing, and support processes. The contractor shall utilize systems engineering tools and overlay a management concept that encourages the use of IPTs during the execution phase of the program.

3.7.1 Integrated Master Schedule (IMS)

The contractor shall develop and deliver an Integrated Master Schedule (IMS) and develop, implement, manage to, update, and maintain the contract IMS. All contract schedule information delivered or presented at program reviews shall originate from the IMS and shall contain all critical events and exit criteria, accomplishments, predecessors and successors’ events, and their dependencies. The IMS shall address total program activities including activities performed by major subcontractors. The contractor shall conduct critical path analysis of the tasks and identify problem areas and corrective actions required to eliminate or reduce schedule impacts.

(DI-MGMT-81861A)Integrated Program Management Report (IPMR)

3.7.2 Program Reviews and Conferences

When required, The contractor shall support CONUS and OCONUS meetings and reviews. The contractor shall have key personnel, support, and subcontractors as appropriate, available to execute the meetings. The contractor shall prepare the Conference Agenda, Conference Minutes, and Presentation Material for the conferences and reviews IAW the CDRL (DI-ADMN-81250B).

3.7.2.1 Program and Technical Reviews

The contractor shall conduct program and technical reviews, to include a Post Award Conference

(PAC), System Requirements Review (SRR), a Preliminary Design Review (PDR), and a

Critical Design Review (CDR) (See Appendix A). The location of the PAC, SRR, PDR, and

CDR shall be at The contractor’s facility. The reviews shall at a minimum address:

a) System requirements and allocations to ensure that requirements are unambiguous, consistent, complete, feasible, verifiable, and traceable to top-level system requirements.

b) Design maturity based on technical goals, accomplishments, and empirical analysis and test data supporting progress to date.

c) Life cycle processes and infrastructure necessary for product sustainability throughout the system life cycle.

d) Determination to proceed with the next application of the systems engineering process or corrective actions necessary before proceeding.

(DI-ADMN-81250B) Conference Minutes

3.7.2.2 Program Management Review (PMR)

The contractor shall host formal program management reviews on an average of one every three months after CDR. The location of the reviews shall be at The contractor’s facility. The program management review shall provide a program overview and a detailed discussion of pre-selected topics. Status and information at the reviews shall reflect progress since the previous review.

Risk management to product requirement objectives shall be covered at all program and technical reviews, and at any time The contractor identifies a potential impact to cost, schedule, and performance. Early identification of risk, proactive measures to mitigate it, and communication with the Government are expected and should be addressed in The contractors

CPSMR. The contractor shall use their internal risk management tools to perform risk management.

The location and timing of these reviews may be in conjunction with other reviews. With

Government concurrence, some technical reviews may be conducted via teleconference and through the use of an approved online enterprise collaboration tool or combined with other program events. The contractor shall record meeting minutes for all program reviews and distribute them to the Government after each review.

3.8 Configuration Management (CM)

The contractor shall use an internal configuration management process to monitor, update, and control all configuration documentation, physical media, and physical parts representing or comprising the system configuration items (CIs) for the training system.

3.9 CM Process

The contractor shall use an automated internal configuration management process to monitor, update, and control all configuration documentation, physical media, and physical parts representing or comprising the system hardware and software configuration items (CIs). The contractor shall implement an automated configuration management function to perform configuration control, configuration identification, audits, and status accounting in a system-engineering environment.

3.10 Configuration Validation/Verification

The contractor shall validate the system configuration information to ensure that requirement attributes are met and accurately documented. This will be accomplished through validation of the system drawings with the system to ensure that the system functions meet contract requirements and the physical configuration of the system is accurately reflected in the drawings.

The contractor shall assist the Government during its functional and physical configuration audits of the system. These audits will occur at Factory Acceptance Test.

3.10.1 Software Configuration Management

The contractor shall establish and document a software configuration management process. The software configuration management plan may be incorporated into the software process plans or may be a separate configuration management plan. The plan shall include configuration management of all related updates and patches applied to ensure the secure operation of the system.

3.11 Quality Assurance

The contractor shall establish measurement points that will provide maximum visibility into new and prior processes to assure contractual requirements are being met. The contractor shall select the proper methods to analyze these processes to continuously improve the system. All discrepancy corrections shall be documented.

3.12 Integrated Testing and Inspections

The contractor shall coordinate, establish, and implement a comprehensive test and evaluation

(T&E) program to include all configurations of the training system. System T&E refers to the test and evaluation activities which use the production hardware together with the software to validate that the system meets the operational and technical performance requirements as stated in the system specification. System test shall include a process to prepare the executable software, including any batch files, data files, or other software files needed to install and operate the software on the target computer platforms. The contractor shall provide support resources and infrastructure necessary for test and evaluation activities for the training system.

The contractor shall develop step-by-step test procedures to be performed on items undergoing testing. The contractor shall identify items to be tested, the test equipment and support required, the test conditions to be imposed, the parameters to be measured, and the pass and fail criteria against which the test results will be measured. The test planning and test procedures shall be structured to integrate all operational, modeling, and simulation activities.

(DI-NDTI-80603A) Test Procedure (TP)

3.12.1 Evaluation

The Contractor shall coordinate, establish, and implement comprehensive evaluation processes and criteria to be used to validate the training device. The Contractor shall provide support resources and infrastructure necessary for conducting all evaluation activities. The evaluation process shall be throughout the contract period of performance to minimize program risk and to avoid deferring all evaluation activities until after product development.

3.12.2 Test Readiness Review (TRR)

The Contractor shall address the following key issues during a TRR prior to the start of formal

Factory Acceptance Test (FAT) and Site Accpetance Test (SAT) to ensure that the system and all test resources are ready to undergo testing:

(a) Test procedures comply with plans and descriptions, are adequate to accomplish test requirements, and satisfy requirements for verification.

(b) New or modified test equipment, facilities and procedure manuals required to accomplish test and evaluation are available and are approved by the Government.

3.12.3 Factory Acceptance Test (FAT)

The Contractor shall conduct a FAT to verify that the training systems operate to the specified system requirements. Testing shall be conducted using the approved test procedures. The

Contractor shall document the result of the test. The FAT will be witnessed by the Government or designated Government representatives.

(DI-NDTI-80809B) Test/Inspection Report

3.12.4 Site Acceptance Test (SAT)

The contractor shall assist in the conduct of the Government SAT for the training systems to verify that the installed configuration items operate to the specified system requirements.

Testing shall be conducted using approved acceptance test procedures. The SAT shall be conducted by the Government or designated Government representatives. Any discrepancies found during testing shall be corrected at no cost to the Government. The contractor shall provide support resources and infrastructure necessary for SAT activities for the training system.

(DI-NDTI-80809B) Test/Inspection Report

3.12.5 Test Discrepancies

The contractor shall establish an automated database system to facilitate timeliness of analysis and corrective action of each test discrepancy. The contractor shall establish a process to receive and record test discrepancies. Upon resolution of a discrepancy, The contractor shall notify the

Government designated test director that the integrated database has been updated. Government concurrence shall be required for the closure of all documented formal test discrepancies.

3.13 Training Products

The contractor shall provide Operator and Maintenance Training through a combination of classroom, written instructions, and hands-on operation for the training systems. The contractor shall provide all training courseware including programs of instruction, lesson plans, and practical exercises for the training systems. The contractor shall deliver all training products to include classroom presentations and instruction in English.

3.13.1 Operator Training

The contractor shall develop and provide a combined operator training through a combination of classroom, written instructions, and hands-on operation for the training system. The contractor shall provide operator training through a combination of classroom, written instructions, and hands-on operation for the training systems. The contractor shall provide all training courseware including programs of instruction, lesson plans, and practical exercises for the training systems.

The contractor shall deliver all training products to include classroom presentations and instruction in English. The contractor shall provide an operator training course consisting of no less than 40 hours of instruction. The course shall be conducted at the fielded location. The course shall provide comprehensive training for operators in the concepts, skills, and aptitude necessary to efficiently operate the systems. The course shall provide familiarization with trainer operations and shall include the utilization, functions, and controls of the instructor station. The course shall address the physical and functional descriptions and operation of all systems operational equipment. The training course shall consist of a classroom presentation, lesson plans, practical exercises, and an end-of-course test. The contractor shall document and provide certificate of completion for each student that successfully completes each operator training course.

The training shall include all aspects of the operation of the training device including training for instructor development of customized training scenarios. A copy of the training materials shall be provided with the training systems upon completion of the training course.

(DI-ILSS-80872) Training Materials

3.13.2 Maintenance Training

The contractor shall provide a maintenance training course consisting of no less than 40 hours of instruction. The contractor shall conduct a maintenance training course on-site prior to the training systems being accepted as RFT. The course shall provide comprehensive training for maintainers in the concepts, skills, and aptitude necessary to efficiently maintain the training device. This course shall consist of instruction in troubleshooting and maintenance, diagnostics to fault isolation, calibration, adjustments, remove and replace procedures, use of built in test, and repair that is beyond operator level maintenance. The course shall provide the knowledge necessary to operate, maintain, and troubleshoot the trainers. The training course shall consist of a classroom presentation, lesson plans, practical exercises, and an end-of-course test.

(DI-ILSS-80872) Training Materials

3.14 Site Requirements

The contractor shall conduct a site survey at the installation site at least three months prior to the delivery of the training system. The purpose of the survey is to discuss and confirm arrangements for the installation and to provide information on any modifications required at the installation site. The contractor shall submit the results of the site survey in a Trainer Facilities

Report that documents:

(a) The status of the building or location where the system will be installed.

(b) The planned positions of equipment, assemblies, cableways, access ways, and any other unique feature, and measurements required to ensure clearance during the installation.

(c) The existing and proposed location of power distribution boxes, switches, water and air supply points and air ducting, and other unique building or location features.

(d) The arrangements for any required services.

(e) The arrangements for hours of work, access to work areas, required support facilities, and required on-site personnel participation.

(f) Any outstanding issues pertaining to the installation program.

The Afghanistan National Security Forces shall provide controlled environment facilities for the

FTD

(DI-FACR-80966) Trainer Facilities Report (TFR)

Appendix A – Event Entrance and Exit Criteria

1. Post Award Conference (PAC)

The purpose of the PAC shall be to establish the framework of the contractor and Government interaction during the performance period of the contract. The PAC shall include:

Introduction and contract overview

Discussion and clarification of Specification and SOW requirements.

Presentation, discussion and clarification of contract assumptions and responsibilities.

Presentation of a complete, accurate, and realistic IMS and detailed schedule with status.

Identification of the critical paths within the IMS and detailed schedule.

CDRL delivery schedule and status.

Configuration Management (CM) Process overview.

Risk management approach discussed.

IPT structure, membership, and responsibilities.

Action item reporting and status.

Long lead time item identification and status (if identified prior to SRR).

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

1.1 PAC Entry Criteria

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

Contractor-submitted PAC agenda is complete and acceptable.

Contractor has completed the program specific PAC documents.

1.2 PAC Exit Criteria

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

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

IMS and detailed schedule are complete, accurate, and realistic.

2. SRR Entrance and Exit Criteria

2.1 SRR Entrance Criteria

A preliminary agenda has been coordinated 30 days prior to the SRR.

SRR technical products listed below for both hardware and software system elements have been made available to the SRR participants 15 days prior to the review:

o Draft System/subsystem specification (SSS).

o All Design Change Requests (DCRs). DCRs must be presented with detailed rationale for the change, impact assessment of the change (with respect to cost, schedule and performance) and associated risk mitigations.

o Program and technical risks identified.

o Updated IMS.

2.2 SRR Exit Criteria:

The SRR is considered complete when:

All known DCRs are documented and provided to the Government, All Contractor Action Items are approved

SRR review minutes have been submitted and accepted by the Government.

Risks are known and are manageable for implementation of the functional requirements into a preliminary design.

Program schedule is executable with the anticipated technical risks.

3. PDR Entrance and Exit Criteria

3.1 PDR Entrance Criteria

A preliminary agenda has been coordinated 30 days prior to the PDR.

PDR technical products for each system hardware and software configuration item have been made available to the PDR participants 10 days prior to the review:

o SRR/SFR exit criteria met o All SRR Action Items requiring contractor response have been completed and closed o Submission of all the CDRL items scheduled to be delivered prior to PDR o Updated SSS submitted, reflecting any changes since SRR close out.

o Updated program and technical risk assessment is medium or lower.

o Updated IMS.

o Submittal and approval of the PDR agenda and presentation materials

3.2 PDR Exit Criteria

The PDR is considered complete when:

All PDR issues were captured as Action Items (AIs) and properly adjudicated or assigned all known DCRs are documented and provided to the Government, Risks and their respective mitigation plans are in place and manageable for implementation of the functional requirements into a detailed design.

Any adjustments to the schedule (IMS) updated

PDR review minutes have been submitted and been accepted by the Government.

4. CDR Entrance and Exit Criteria

4.1 CDR Entrance Criteria

A Preliminary Design Review (PDR) has been successfully completed, and all PDR actions have been closed or assigned government-approved due dates.

All PDR exit criteria key issues have been satisfied.

A preliminary agenda has been coordinated 30 days prior to the CDR.

CDR technical products (hardware and software elements of the product baseline to be reviewed and approved at the CDR) have been made available to the CDR participants…