MT-C2_BASE_PWS_DATED_01-09-19_FINAL_CM_Copy.docx

DOCX document 172 KB Posted

Attached to
Medical Training Command and Control - MT-C2
Solicitation number
ID04190058
Issued by

About this file

PWS - Updated 9 Jan 2019

View the file

Other files

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

PERFORMANCE WORK STATEMENT

for

MEDICAL TRAINING COMMAND AND CONTROL (MT-C2)

PRODUCTION (BASE)

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

Engineering

Prepared By: ____________________Concurrence: ____________________
Tony HazbounVanette Johnson
Lead EngineerChief Engineer, JPM MMS
Date: __________Date: __________

Acquisition Logistics

Prepared By: ____________________Approved By: ____________________
Pete SuarezLTC Robert Carter
Product Support ManagerPdM MedSim
Date: _________Date: ___________

Program Management

Submitted By: ____________________ CPT Tony Prudhomme APM MedSim Date: ___________

REVISION LOG

Revision Number
Date
Log of Changes Made and Description of Reason Changes
Approved By
1.0
8-1-18
Initital version of document
1.1
8-3-18
Final version of document with incorporated changes by CE
1.2
8-10-18
Final version of document with incorporated changes by ACC
1.3
10-4-18
Incorporated clarifications due to vendor responses to draft RFP
1.4
10-29-18
Document changed from SOW to PWS
1.5
12-4-18
Changed Quantity of sites to 21, 3 year IDIQ
1.6
01-09-19
Changed language in Paragraph 3.1

Table of Contents

1.SCOPE1
1.1Background1
2.APPLICABLE DOCUMENTS2
2.1Department of Defense Documents2
2.2Availability of Department of Defense Specifications3
2.3Other Governement Documents3
2.4Commercial Standards and Specifications3
3.REQUIREMENTS3
3.1Product Fielding3
3.2Program Management4
3.2.1Risk Management4
3.2.2Quality Management4
3.2.3Management Reviews4
3.2.3.1Post Award Conference (PAC)4
3.2.3.2Program Management Reviews (PMR)4
3.2.3.3Integrated Product Team (IPT) Meetings5
3.2.4Integrated Master Schedule (IMS)5
3.3Systems Engineering5
3.3.1Hardware Engineering6
3.3.2Software Engineering6
3.3.3Product Definition Data (PDD)6
3.3.4Cybersecurity6
3.3.4.1Cybersecurity Artifacts8
3.4Logistics8
3.4.1Logistics Support Analysis8
3.4.2Spares8
3.4.3Supportability Analysis and Logistics Management Information8
3.4.3.1LPD Summaries/Reports9
3.4.4Field Feedback9
3.4.5Disposal Analysis9
3.4.6Logistics Change Planning and Analysis10
3.4.7Item Unique Identification (IUID) Analysis10
3.4.8Fielding Support10
3.4.9Technical Publications10
3.4.9.1Commercial Off-The-Shelf Manuals (COTS)11
3.4.9.2Operator User’s Manual (OUM)11
3.4.9.3System Maintenance Manual (SMM)11
3.4.9.4Validation11
3.4.9.5Verification12
3.4.9.6Publications In Process Reviews (IPRs)12
3.4.10Training Products12
3.4.10.1New Equipment Training (NET) and Support13
3.4.10.1.1Instructor / Operator (I/O) Training13
3.4.10.1.2Maintenance Training13
3.4.11Interim Contractor Support (ICS)14
3.4.11.1Transition Planning14
3.4.11.2Site Survey and Training Facility Report/Faciltiy Access Report14
3.4.11.3System Installation15
3.5Operations Security/Anti-Terrorism Requirements15
3.5.1Anti-Terrorism (AT) Level 1 Training15
3.5.2Access and General Protection Policy and Procedures15
3.5.3iWATCH16
3.6Government Acceptance16
3.6.1Test Discrepancies16
3.7Travel16
4.0CONTRACTOR MANPOWER REPORTING APPLICATION (CMRA).16

PWS-2018-057

09 January 2019

PWS-2018-057

09 January 2019 iv

Performance Work Statement For Medical Training Command and Control

1. SCOPE

This Performance Work Statement (PWS) defines the effort required, under a single award indefinite delivery/indefinite quantity (ID/IQ) contract, for delivering, installing, testing, managing and documenting changes and updates to the Medical Training Command and Control (MT-C2) System.

1.1 Background

The U.S. Army Program Executive Office Simulation, Training and Instrumentation (PEO STRI) Product Manager for Medical Simulation (PdM MedSim) has a requirement for the production and installation of MT-C2 into the Medical Training Simulation Centers (MSTCs).

The MSTC Program of Record (POR) is a standardized Army training program with locations at various military installations worldwide, delivering effective medical training with a standardized training platform to re-certify Army 68W Military Occupational Specialty (MOS) Soldier Medics. The MSTC provides medical training and education on new battlefield procedures and equipment, while affording soldier medics the ability to provide comprehensive training in several formats such as the classroom setting, practical hands-on training simulation, trauma lanes, and distance learning.

Each MSTC provides a medical skills training platform where Soldiers obtain sustainment and validation of their medical skills in accordance with Training Circular (TC) No. 8-800, Medical Education and Demonstration of Individual Competence (MEDIC), and the Combat Life Saver (CLS) Programs of Instruction (POI).

As a System of Systems, the MSTC is is comprised of the Instructor Support System (ISS), the Virtual Patient System (VPS) and the Medical Training Command and Control (MT-C2) System.

The ISS provides the Instructors/Operators with the capability to simulate and record combat conditions for a training event. The ISS is comprised of; a smoke machine, strobe lights, scent and sound generator, video cameras, and After Action Review (AAR) capabilities. The VPS capability within the MSTC is a collection of high and low fidelity manikins, portable bleeding system and airway management trainers providing realistic, live simulated patients.

The MT-C2 system is a command and control center that allows for remote training platform management by interfacing with the ISS and VPS. During a MSTC training event, Soldiers perform tasks on training devices within the simulated environment. The MT-C2 system enables medical scenario integration, mannequin control, audio video (AV) surveillance and recording as well as providing the capability to manipulate the environments in which scenarios take place in order to maximize the positive impact and training experience.

The MT-C2 is only integrated with two of the high fidelity patient simulators that comprise the VPS; KGS Trauma F/X Traumatic Amputation Task Trainer (TATT) and Laerdal’s SimMan Trauma.

The Government has already fielded two prototype MT-C2 systems at Ft Hood, TX and Camp Humphreys, South Korea under a developmental contract, in which a baseline software and Technical Data Package (TDP) were developed. Under this production contract, the Government has a requirement to:

1- Upgrade the remaining 19 MSTCs: Ft. Lewis, WA; Ft. Drum, NY; Ft. Riley, KS; Ft. Bliss,TX; Vilseck, Germany; Ft. Carson, CO; Ft. Campbell, KY; Ft. Stewart, GA; Ft. Bragg, NC; Camp Shelby, MS; Ft. McCoy, WI; Ft. Dix, NJ; Ft. Wainwright, AK; Schofield Barracks, HI; Camp Dodge, IA; Camp Ripley, MN; Camp Atterbury, IN; Ft. Indian Town Gap, PA; Ft. Benning, GA.

2- Retrofit Ft. Hood and Camp Humphreys with the MT-C2 production configuration described in this PWS.

After production and installation, the MT-C2 system must be able to demonstrate compliance with the System Requirements Document (SRD) PRF-PT-654. A TDP developed for the prototype contract will be provided with the solicitation as Government Furnished Information (GFI).

The requirements defined herein form the basis for all work that will be performed as part of the Task Orders (TOs) the Government will issue under the MT-C2 IDIQ contract. Management of the IDIQ and the TOs shall be in accordance with the requirements of this PWS and the individual TOs. Unless otherwise specified all requirements of the base PWS will apply to the individual TOs.

2. APPLICABLE DOCUMENTS

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

2.1 Department of Defense Documents

DoDI 8500.01Cybersecurity
DoDI 8510.01Risk Management Framework (RMF) for DoD Information Technology (IT)
DoD 8570.01-MInformation Assurance Workforce Improvement Program
DoDI 8582.01Security of Unclassified DoD Information on Non-DoD Information Systems

2.2 Availability of Department of Defense Specifications

Copies of the DoD documents are available on the World Wide Web (www) at URL: http://www.dtic.mil/whs/directives/.

2.3 Other Governement Documents

MIL-STD-31000ATechnical Data Packages
AR 25-2Information Assurance
MIL-PRF-29612BTraining Data Products Performance Specification
PRF-PT-654MT-C2 Systems Requirements Document (SRD)
AR 525-13Antiterrorism & Force Protection
AR 190-13The Army Physical Security Program

2.4 Commercial Standards and Specifications

GEIA-STD-0007Logistics Product Data
TA-STD-0017Product Support Analysis
ISO 9000:2015Quality Management Systems

3. REQUIREMENTS

The contractor shall assemble and install the MT-C2 system at each MSTC to interface with the Instructor Support System (ISS) and Virtual Patient System (VPS) located at each installation. The contractor shall:

1- Assemble and install the MT-C2 at 19 MSTC sites as defined by the TDP and GFI sofware provided by the Government.

2- Retrofit the MT-C2 systems fielded at Camp Humphreys and Ft. Hood with the latest production configuration.

3.1 Product Fielding

The contractor shall establish a fielding strategy for the MT-C2 system in a manner that maximizes the number of fieldings in the least amount of time based on geographical proximity of the MSTC locations. The fielding strategy shall be approved by the Government prior to execution.

3.2 Program Management

The Contractor shall deliver and install an MT-C2 system that meets the requirements as defined in this PWS, SRD, and the TDP.

The Contractor shall provide all resources, facilities, equipment, and personnel necessary to complete the tasks in this PWS. The Contractor shall perform all activities as required to assemble and install the hardware and software to achieve a fully functional system.

The Contractor shall provide the overall management and administrative efforts necessary to ensure that the requirements of this contract are accomplished. The Contractor shall plan, implement, and maintain a management process that shall minimize the system overall cost.

3.2.1 Risk Management

The Contractor shall prepare, implement, and maintain a risk management process that includes identification, analysis, mitigation planning, mitigation plan implementation, and tracking.

3.2.2 Quality Management

To ensure that the requirements of the contract are met, the contractor shall manage quality of the finished product via industry accepted best practices IAW ISO 9001:2015 and with the contractor’s internal processes.

3.2.3 Management Reviews

3.2.3.1 Post Award Conference (PAC)

The contractor shall conduct a PAC within 15 working days after contract award. The purpose of the conference shall be to establish the framework of the Contractor and Government interaction during the performance period of the contract. The Contractor shall place emphasis on the operating procedures, methodologies, and processes to be used in the execution of the contract. The Contractor shall develop and present a program Integrated Master Schedule (IMS), IPT structure, management concept, organizational structure, and the interfaces with the Government that are employed to perform the MT-C2 mission. The Contractor shall document action items and due dates, coordinate resolution, and track action items until closure. Action item closure shall require Contractor and Government approval.

3.2.3.2 Program Management Reviews (PMR)

The Contractor shall conduct program management reviews at the contractor’s facility on a quarterly basis in accordance with the IMS. The first PMR shall be no more than 45 calendar days after the combined Start of Work Meeting / PAC. The PMR shall provide a program overview and shall include as a minimum:

a. Hardware status

b. Risk Assessment

c. Subcontract management/progress

d. Production planning and status

e. Logistics planning

f. Test planning

g. Training and technical publications status

h. Schedule status

i. Pre-selected topics of interest

j. Cybersecurity

Status and information at the review shall reflect currency since the previous review. Other program reviews such as technical reviews, technical manual reviews, etc shall be combined into the PMR when possible. The Contractor shall also be responsible for generating minutes of the meetings and provide them to the Government for approval. The Contractor shall document action items due dates, coordinate resolution, and tracking of action items until closure.

3.2.3.3 Integrated Product Team (IPT) Meetings

The Contractor shall establish an IPT structure to address major areas of program schedule, system procurement, testing, and logistics. The IPT meetings/teleconferences shall be held bi-weekly, and used to address systems status of activities, questions and issues in a timely manner between management reviews. The Contractor shall document action items and due dates, coordinate resolution, and track action items until closure. Action item closure shall require Contractor and Government approval.

3.2.4 Integrated Master Schedule (IMS)

The Contractor shall develop an Integrated Master Plan (IMP) and an Integrated Master Schedule (IMS). The Contractor shall manage to and maintain the IMP and IMS it has developed including appropriate program milestones with corresponding entrance and exit criteria. The IMS shall include a detailed account of all tasks necessary to accomplish the goals and objectives of the contract.

((DI-MGMT-81650) Integrated Master Schedule (IMS))

3.3 Systems Engineering

The contractor shall provide the requisite technical expertise to complete the required tasks of the individual TO. The Contractor shall assess proposed changes in the functional architecture, physical hierarchy, and baselines as changes are required, as a result of conducting cost-benefit trades to support refinement of the SRD requirements. The contractor shall objectively trade alternatives to balance performance, cost, schedule, and risk prior to Government approval.

3.3.1 Hardware Engineering

The Contractor shall procure and install the system hardware identified in the TDP. In the event that changes to the hardware baseline become necessary, the Contractor shall procure and install hardware that satisfies the performance and cybersecurity requirements stated in the SRD. All changes to the baseline shall require Government approval.

3.3.2 Software Engineering

The Government will provide the MT-C2 software as Government Furnished Information (GFI). The Contractor shall identify and request software baseline changes to the Government for Post Deployment Software Support (PDSS) contractor integration into the GFI baseline. The contractor shall be responsible for overall system functionality and compatibility with COTS items within the TDP should changes to the product baseline become necessary.

3.3.3 Product Definition Data (PDD)

As required, the contractor shall maintain the PDD in accordance with MIL-STD-31000A that accurately depicts the final product.

1. The PDD shall disclose complete design, logistics, manufacturing requirements, and the means of measuring compliance with the requirements.

1. The contractor shall obtain document numbers from the Government for the PDD elements. All unused numbers shall be returned upon completion of PDD preparation.

1. The contractor shall identify the following data elements to assist in the procurement of spares/repair parts: Commercial and Government Entity (CAGE) code, National Stock Number (NSN), manufacturer’s part number, alternate part numbers, and the reliability and maintainability data if available.

1. The contractor shall determine performance characteristics for each re-procurable spare part, component, and assembly in accordance with the established logistic repair procedures.

Source control drawings may be included in the product baseline but require Government approval.

((DI-SESS-81000E) Product Drawings/Models and Associated Lists- Annex to Exhibit B-Option Selection Worksheet)

3.3.4 Cybersecurity

The Government intends to conduct all Cybersecurity activities for this Type III stand-alone connected system. In the event of changes to the baseline, the Contractor shall address and implement the Risk Management Framework (RMF) that has the appropriate security categorization levels for Confidentiality, Integrity and Availability. The Contractor shall work with the Government and follow the RMF processes as governed by DoDI 8500.01 and DoDI 8510.01.

All Cybersecurity and Cybersecurity-enabled products shall be securely configured IAW DoD approved security configuration guidelines. The Contractor shall obtain Security Technical Implementation Guides (STIGs) http://iase.disa.mil/stigs/Pages/index.aspx and implement each STIG into the design. As part of the system design and component selection process, Cybersecurity shall be considered as a requirement for all systems used to enter, process, store, display, or transmit information. Cybersecurity shall be achieved through the acquisition and appropriate implementation of evaluated or validated GOTS or COTS Cybersecurity and Cybersecurity-enabled IT products. All Commercial-Off-The-Shelf (COTS) Cybersecurity products and Cybersecurity-enabled products shall be certified compliant with National Security Telecommunications and Information Systems Security Policy Number 11 (NSTISSP-11) by labs accredited under the National Information Assurance Partnership (NIAP) Common Criteria Evaluation and Validation Scheme (CCEVS) or National Institute of Standards and Technology (NIST) Federal Information Processing Standards (FIPS) Cryptographic Module Validation Program (CMVP). Similarly, Government Off-The-Shelf (GOTS) Cybersecurity products or Cybersecurity-enabled products employed by the system shall be evaluated by the National Security Agency (NSA) or in accordance with NSA approved processes.

The Army has mandated the Universal Gold Master (UGM) as the Windows-based standard operating system. UGM license can be obtained from Computer Hardware, Enterprise Software and Solutions (CHESS) website (https://chess.army.mil) or Softmart (http://www.softmart.com). Because UGM Windows operating systems requires valid activation, the Government CAC card readers MUST be purchased.

If UGM cannot be used, (contractor shall provide written explanation as to why UGM cannot be used) a Cybersecurity approved operating system shall be configured in accordance with the latest DISA Security Technical Implementation Guides (STIGs), written for that operating system. In addition, the STIGs apply not only to the operating system but also to other software or hardware component.

For hardware and software products not available through CHESS or Softmart, the contractor shall select the Cybersecurity validated products from one of the links below. If CHESS items are not on the Common Criteria Certified Products list or NIAP Validated Product List , all Cybersecurity and Cybersecurity-enabled products must be selected from the APLITS.

1. Common Criteria Certified Products http://www.commoncriteriaportal.org/products.html

2. The Common Criteria Evaluation and Validation Scheme - NIAP Validated Product List http://www.niap-ccevs.org/cc-scheme/vpl/

3. Approved Products List Integrated Tracking System (APLITS) – CAC Card is required.

https://aplits.disa.mil/processAPList.do

Note: There shall be no waiver issued by the Government for unapproved Cybersecurity products.

All contractor employees and associated sub-contractor employees shall complete the DOD IA Awareness Training before issuance of network access and annually thereafter. All contractor employees working IA/IT functions must comply with DOD and Army training requirements in DOD 8570.01-M and AR 25-2 at the start of work. The contractor shall secure all unclassified DoD information on Non-DoD information systems in accordance with DoDI 8582.01.

3.3.4.1 Cybersecurity Artifacts

As changes to the baseline occur, the Contractor shall produce all of the necessary artifacts to complete the RMF package, in accordance with DoDI 8500.01 and DoDI 8510.01, to deliver and operate a fully accredited system that has the appropriate security categorization levels for Confidentiality, Integrity and Availability.

((DI-MISC-80711A) Scientific and Technical Reports)

3.4 Logistics

The contractor shall perform reliability analysis to ensure that any new COTS components procured outside of the allocated baseline (TDP) meets the same (or higher) level of reliability as the current component that the item is replacing.

3.4.1 Logistics Support Analysis

The Contractor shall analyze existing Life Cycle Contractor Support (LCCS) support structures and optimized support infrastructure for production and deployment of the MT-C2 system. The recommended support resources shall be sufficient to allow another contractor with comparable skills to assume operation, maintenance, and support of the system and sustain the system availability requirement. The Contractor shall only use the form, fit, function, and interface requirements in the performance specifications for provisioning, training, and maintenance planning.

3.4.2 Spares

The Contractor shall analyze the design per the TDP and present a recommended spares list for Government approval.

3.4.3 Supportability Analysis and Logistics Management Information Logistics Product Data (LPD) is a subset of Product Support Analysis documentation. The Contractor shall use, as a baseline, all current Logistics Product Data for the MT-C2 system. The contractor shall establish and maintain a Logistics Product Data (LPD) database IAW GEIA-STD-0007 and the requirements contained in the SRD. The LPD database shall be used to satisfy applicable and related data items as specified in the CDRL and LPD data product worksheets. The contractor shall provide the Government access to their online LPD account.

((DI-SESS-81758) Updates to Logistics Product Data - Annex to Appendix B)

3.4.3.1 LPD Summaries/Reports

As changes to the baseline occur, the contractor shall be responsible for entering any additional data to the Attribute Selection Sheet required to generate the following reports:

· Maintenance Allocation Chart (LSAR-044)

· Authorization List Items Report (LSAR-040)

· Task Code to SMR Code Verification Report (LSAR-068)

· Bill of Materials Report (LSAR-080)

· Preventive Maintenance, Checks and Services product (LSAR 033)

· Indentured Parts List (IPL) Product

· Common and Bulk Items List Product ((DI-SESS-81759) Logistics Product Data Summaries)

3.4.4 Field Feedback

The contractor shall collect and analyze all usage and maintenance data (supportability related field data) of the already fielded prototype systems (2). Feedback shall include collection of Built in Test (BIT) metrics and diagnostics to validate their effectiveness and performance against requirements. The data collected shall inform the procurement of COTS for the production baseline. The contractor shall document activity outputs in the Logistics Product Data database.

((DI-SESS-81759) Logistics Product Data Summaries)

3.4.5 Disposal Analysis

The contractor shall perform analysis to identify disposal procedures associated with the MT-C2 focusing on those components, assemblies, sub-assemblies, parts and materials that contain hazardous materials, wastes and pollutants. The analysis shall also identify those items that can be recycled, reused or salvaged.

((DI-SESS-81759) Logistics Product Data Summaries)

3.4.6 Logistics Change Planning and Analysis

Without duplicating any effort in this PWS and only if design changes to the MT-C2 baseline are required, the contractor shall identify the reasons for the deviation and propose methods of correcting deficiencies and enhancing system readiness IAW TA-STD-0017, Activity 17.2 and 17.4-17.5. This includes updating the Product Support Package’s IPS elements, conducting tests, and analyzing test results.

((DI-SESS-81759) Logistics Product Data Summaries)

3.4.7 Item Unique Identification (IUID) Analysis

The contractor shall identify new equipment or repairable items with a cost greater than $5,000; all LRU and hardware configuration items; Special Test Equipment; Special Inspection Equipment; Special Tooling; and embedded subassemblies and components or parts that may be serially managed, that are mission essential or are controlled inventory items. The contractor shall perform an engineering analysis required to determine the appropriate method for marking each item that requires unique identification. For such items as approved by the Government, the contractor shall provide DoD unique item identification. Exceptions to marking items for which IUID is mandated prior to delivery to the Government, if granted by the Government, will be processed as specified in DFARS 211.274-2.

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

3.4.8 Fielding Support

The contractor shall be responsible for shipping, inspecting and staging the equipment at each production site prior to insallation. The contractor shall assist the Government during site inventory of all system equipment.

3.4.9 Technical Publications

The Contractor shall update existing technical publications as required. The operations and maintenance instructions shall accurately provide the technician with all the information needed to keep the equipment operational. It shall provide system and subsystem oriented instructions for installation, operation, maintenance, and testing. All tools, test equipment, and consumable items required to accomplish any maintenance or installation shall be identified just prior to and as part of the task. 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 Government technical manuals and COTS manuals shall be reviewed to ensure changes, updates, revisions, or supplementation is not required to reflect the components actually being installed. All publications shall reflect the configuration of fielded hardware as documented in the product baseline. The Contractor shall prepare Operator and System Maintenance Manuals that provide instructions suitable for use by the intended audience of the system. The Operator Manual shall also include operator maintenance tasks such as preventive maintenance checks and services, inspection, lubrication, adjustment, and operator level repair and replacement tasks as needed. The Contractor shall identify and document maintenance tasks for both levels of the maintenance concept. The Contractor shall identify all required spare parts, consumables, tools, and test/support equipment associated with each task and identify the level of maintenance at which each task shall be performed.

3.4.9.1 Commercial Off-The-Shelf Manuals (COTS)

The contractors shall deliver, compiled in a consolidated binder, Commercial-Off-The-Shelf (COTS) manuals specific to the design, operation and maintenance requirements for each of the devices delivered.

3.4.9.2 Operator User’s Manual (OUM)

The Contractor shall update existing OUM documenting tasks as necessary to operate the system. The Contractor shall identify and document operator specific tasks for preventive maintenance checks, inspection, lubrication, adjustment, and operator level repair and replacement tasks. The Contractor shall identify all required spare parts, consumables, tools, and test/support equipment associated with the operation and operator’s preventive maintenance tasks.

((MIL-STD-40051-2B) Updates to Page-Based Technical Manuals)

3.4.9.3 System Maintenance Manual (SMM)

The Contractor shall update existing SMM documenting tasks as necessary to maintain the system. The Contractor shall identify and document maintainer specific tasks for detailing installation, fault isolation, Line Replaceable Units (LRU) procedures, software update procedures, and all necessary maintenance procedures to maintain the trainer. The Contractor shall identify all required spare parts, consumables, tools and test/support equipment associated with the maintenance tasks.

((MIL-STD-40051-2B) Updates to Page-Based Technical Manuals)

3.4.9.4 Validation

The contractor shall accomplish a validation and support Government verification of all changes, supplemental data, and revisions to existing technical publications.

1. Publications shall be validated prior to start of system testing.

1. A technical publication shall not be ready for validation or verification until the following conditions have been fulfilled:

1. An engineering technical review has been completed

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

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

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

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

3.4.9.5 Verification

The contractor shall assist in the Government verification of any revisions to the Technical Manuals (TM) as required to ensure their accuracy, content, understandability, consistency, and usefulness. The contractor shall incorporate correction of discrepancies and changes resulting from training, testing, and reviews into the TMs. The contractor shall provide system equipment, technical, and engineering support and facilities as required to aid in the performance of the verification effort. The contractor shall incorporate all comments from compliance-reviews, technical accuracy reviews and verification reviews into final submission of the technical publications. The contractor shall support the re-verification of corrections/updates as required. Verification shall be rescheduled if more than 15 percent of the pages involved require correction.

3.4.9.6 Publications In Process Reviews (IPRs)

The Contractor shall host and co-chair publication reviews to ensure revisions to the technical publications are being prepared according to contracts. Each IPR shall be scheduled to coincide with a system level program reviews defined in the integrated master plan. The Contractor shall act on reported decisions and discrepancies resulting from or associated with each IPR. Each review shall include a review of incorporated corrections or comments from previous IPR’s prior to proceeding with the current IPR. If any IPT member identifies previous IPR comments that are not included in the technical publications, the IPR shall be considered incomplete.

3.4.10 Training Products

The Contractor shall use, to the maximum extent possible, all previously developed data that can be applied toward satisfying the data requirements of MIL-PRF-29612B, Training Data Products. This includes Government Furnished Information (GFI) and data developed by the contractor incident to other contractual requirements.

((DI-ILSS-80872) Updates to Training Materials) ((DI-81527C) UpDates to Training System Support Document) ((DI-SESS-81523C) Updates to Training Situation Document) ((DI-ILSS-81522C) Updates to Course Conduct Information Package) ((DI-ILSS-81523B) Updates to Course Training Conduct Support Document) ((DI-SESS-81526C) Updates to Instructional Media Package) ((DI-SESS-81520B) Updates to Instructional Media Design Package) ((DI-SESS-81519C) Updates to Instructional Media Requirements Document)

3.4.10.1 New Equipment Training (NET) and Support

The Contractor shall update existing documentation, define, develop, and conduct training for users/operators to understand the functional and operational capabilities. The Contractor shall provide training and training system documents required to support setup, installation, configuration, and operation of system software and hardware, system tools, techniques, methodologies, and for sustainment. The Contractor shall update a complete and exportable training support package that integrates training products, materials, and other pertinent information necessary for system training. The Contractor shall update this training support package using instructional systems design processes.

3.4.10.1.1 Instructor / Operator (I/O) Training

The Contractor shall plan, conduct, and document the completion of the initial instructor and operator course for the initial cadre instructors. The course shall provide comprehensive training for instructors in the concepts, skills, and aptitude to efficiently operate the system. The course shall provide familiarization with simulator operating techniques and shall emphasize the utilization of the instructor facility, its functions, and controls. The course shall address the physical and functional descriptions and operation of the equipment including features, advantages, and configurations.

3.4.10.1.2 Maintenance Training

The Contractor shall plan, update, conduct, and document the completion of maintainer course for the initial cadre of maintenance personnel. The course shall provide comprehensive training for maintainers in the concepts, skills, and aptitude to efficiently operate the system. 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. After completion of the course, all personnel shall be capable of operating, maintaining, and troubleshooting the simulator to the board replacement level.

3.4.11 Interim Contractor Support (ICS)

The Contractor shall provide Interim Contractor Support (ICS) consisting of helpdesk support and onsite assistance, if required, for 12 months immediately after Government acceptance at each fielded site. The contractor shall provide system/configuration management necessary to perform ICS of the MT-C2 system.

3.4.11.1 Transition Planning

The Contractor shall provide support for the transfer of ICS responsibility to the Government or another contractor. Support shall include those services required to insure the effective, efficient transfer of responsibility as well as technical data, tools, and test equipment and repair and spare parts in sufficient detail and coverage to enable other personnel with comparable skills to maintain the system. The transition effort shall include an analysis of all failures and maintenance actions undertaken during the interim support and revising technical publications subject to Government approval to reflect actual fielded experience. The ICS transfer shall include 100 percent of spares, repair parts, and Special Tools and Test Equipment (STTE).

3.4.11.2 Site Survey and Training Facility Report/Faciltiy Access Report The Contractor shall conduct a survey at the installation site prior to finalizing the production baseline. 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 update the Government furnished Trainer Facilities Report (TFR)/Facility Access Report (FAR) for each MSTC site after the completion of a site survey.

During the survey, the contractor shall:

a. Review the status of the building or location where the system shall be installed;

b. Confirm the required positions of equipment, assemblies, cableways, access ways, and any other unique feature, and measure to insure clearance during the installation;

c. Review and confirm 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. Determine the availability of required services;

e. Review and confirm arrangements for hours of work, access to work areas, supporting workshop facilities, and on-site personnel participation.

f. Discuss and resolve any outstanding issues pertaining to the installation program.

g. Assess ventilation and environment characteristics (i.e., temperature average, HVAC, dust content) of control room and validation room(s).

h. Clearly indicate the correct layout of the MT-C2 system, and hardware quantities required for each of the components listed in the TDP.

i. Clearly indicate any obsolete components listed in the TDP, and the contractor’s proposed replacement component.

j. Any hardware deviation from the TDP, including obsolete items, shall require Government approval.

((DI-FACR-80966) Updates to the Trainer Facilities Report)

3.4.11.3 System Installation

The contractor shall perform all installation work without additional on-site personnel support. The contractor shall plan and schedule all work to be performed during regular site hours unless agreed to by the Government. The contractor shall present the Government with an installation and test activities plan for each installation prior to site fielding.

3.5 Operations Security/Anti-Terrorism Requirements

3.5.1 Anti-Terrorism (AT) Level 1 Training

All contractor employees, to include subcontractor employees, requiring access to Army installations, facilities and controlled access areas shall complete AT Level I Awareness Training prior to the first system delivery. The contractor shall maintain a file with certificates after completion of training by all employees and subcontractor personnel. When required by local combatant commander Contractor employees shall be available to receive Government provided area of responsibility (AOR) specific AT awareness training as directed by AR 525-13. Specific AOR training content is directed by the combatant commander with the unit AT Officer being the local point of contact. AT Level I Awareness Training is available at the following website: https://atlevel1.dtic.mil/at.

3.5.2 Access and General Protection Policy and Procedures

All contractor employees and all associated sub-contractor employees shall comply with applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by Government representative). The contractor shall also provide all information required for background checks to meet installation access requirements to be accomplished by the installation Provost Marshal Office, Director of Emergency Services or Security Office. The contractor’s workforce shall comply with all personal identity verification requirements as directed by DoD, HQDA, and/or local policy. Contractor and all associated sub-contractors employees shall comply with adjudication standards and procedures using the National Crime Information Center Interstate Identification Index (NCIC-III) and Terrorist Screening Database (TSDB) (Army Directive 2014-05/AR 190-13), applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by Government representative), or, at OCONUS locations, in accordance with status of forces agreements and other theater regulations.

For contractors requiring a Common Access Card (CAC), the contractor employee shall require, at a minimum, a favorably adjudicated National Agency Check with Inquiries (NACI) or an equivalent or higher investigation IAW Army Directive 2014-05.

3.5.3 iWATCH The contractor and all associated sub-contractors shall brief all employees performing under this contract on the iWATCH program. This training shall be completed within 60 calendar days of contract award.

3.6 Government Acceptance

The contractor shall conduct a Government Acceptance Test (GAT) at each MSTC facility after the installation of the MT-C2 system to validate that all installed configuration items operate in accordance with the requirements specified in the SRD. A test coordination meeting shall be held between all stakeholders prior to the GAT, and testing shall be conducted by Government and contractor personel, and in accordance with approved test procedures.

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

3.6.1 Test Discrepancies

The Contractor shall document all test discrepancies from the GAT, and track the failure analysis and corrective action for each test discrepancy until correction and regression tests are successfully completed. The Contractor shall establish a suspense system to ensure timeliness of analysis and corrective action of each test discrepancy. Upon correction of each discrepancy, the Contractor shall re-test the system to ensure that the correction of each discrepancy did not interfere with or alter the functionality of the system.

3.7 Travel

The contractor shall travel both CONUS and OCONUS to support the efforts as required under this Contract. All contractor personnel travel shall be approved by the Government prior to commencement of travel. The Contractor shall comply with Antiterrorism/Force Protection for Defense Contractors outside the US. Non-local national Contractor personnel must comply with theater clearance requirements.

4.0 CONTRACTOR MANPOWER REPORTING APPLICATION (CMRA).

The Contractor shall report ALL Contractor labor hours (including subcontractor labor hours) required for performance of services under this contract for PEO STRI via a secure data collection site. The Contractor is required to completely fill in all required data fields using the following web address: http://www.ecmra.mil/. Reporting inputs will be for labor executed during the period of performance during each Government Fiscal Year (FY) which runs October 1 through 30 September. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year. Contractors can find User Guides, Frequently Asked Questions and may direct questions to the help desk at http://www.ecmra.mil/.

image1.png

File details come from the government source that posted it.