Loren Data's SAM Daily™

FBO DAILY - FEDBIZOPPS ISSUE OF MARCH 15, 2014 FBO #4494
SOLICITATION NOTICE

69 -- Transport Medical Trainer Laboratory (TMTL) Synopsis

Notice Date

3/13/2014
 

Notice Type

Presolicitation
 

NAICS

333318 — Other Commercial and Service Industry Machinery Manufacturing
 

Contracting Office

PEO STRI Acquisition Center, 12350 Research Parkway, Orlando, FL 32826-3276
 

ZIP Code

32826-3276
 

Solicitation Number

W900KK-14-R-0040
 

Response Due

3/28/2014
 

Archive Date

5/12/2014
 

Point of Contact

Karen Sorapuru, 407-208-3430
 

E-Mail Address

PEO STRI Acquisition Center
(karen.m.sorapuru.civ@mail.mil)
 

Small Business Set-Aside

Total Small Business
 

Description

OVERVIEW The U.S. Army, Program Executive Office Simulation, Training and Instrumentation (PEO STRI), Project Manager for combined Arms Tactical Trainers (PM CATT), Product Manager for Medical Simulation (PM MedSim) intends to procure and field all of the requisite equipment, simulators, and ancillary classroom items needed to establish the Transport Medical Trainer Laboratory (TMTL). The TMTL is a customer-funded initiative in support of the US Army Medical Department Center and School (AMEDD C&S) Critical Care Flight Paramedic Program. NOTICE OF INTENT This effort will be solicited as a 100% small-business-set-aside under NAICS Code 333318, with a size standard of 1000 employees. Per this decision, any firm desiring to participate as a prime contractor in this solicitation must be recognized as a Small Business Concern under NAICS Code 333318, in accordance with FAR 19.301. For those interested Small Businesses, please familiarize yourself with the Limitations on Subcontracting requirements under FAR 52.219-14. The resultant TMTL contract will be a 2-year (base year plus one option) standalone, Firm-Fixed-Price contract. Contract years are based on design, build, installation, and training. This is a SYNOPSIS FOR CONTRACTING BY NEGOTIATION in accordance with Federal Acquisition Regulations (FAR) Part 15, as supplemented with additional information included in this notice. This effort will be solicited as a 100% small-business-set-aside under NAICS Code 333318 with a small business size standard of 1000 employees. This synopsis is provided for informational purposes and is not to be considered a request for proposal. Key Milestone Dates of the acquisition are as follows: Issue DRAFT RFP 28 March 2014 Issue Final RFP 30 April 2014 Proposals Due 30 May 2014 Contract Award 30 July 2014 Questions and or concerns regarding this synopsis shall be directed to Karen Sorapuru, Contract Specialist, at 407-208-3430 or via e-mail at karen.m.sorapuru.civ@mail.mil or to Dan Veenstra, Contract Specialist, at 407-208-3308 or via e-mail at dan.veenstra@us.army.mil. The Contracting Officer for this acquisition is Felix Marrero who may be contacted at 407-208-3267 or via e-mail at felix.r.marrero@us.army.mil. DRAFT STATEMENT OF WORK For the Transport Medical Trainer Laboratory 1.SCOPE This Statement of Work (SOW) defines the effort required for designing, developing, integrating, testing, managing, documenting, and delivering the Transport Medical Trainer Laboratory (TMTL). The TMTL is a customer-funded initiative in support of the US Army Medical Department Center and School (AMEDD C&S) Critical Care Flight Paramedic Program. 1.1Background The U.S. Army Program Executive Office Simulation, Training and Instrumentation (PEO STRI) has a requirement to assist in the elevation of the medical capability on the battlefield by increasing the number of Flight Medics, ensuring that all receive further education to become Nationally Registered Paramedics with critical care training. The focus of this Critical Care Flight Paramedic Program initiative is to provide a Transport Medical Trainer Laboratory (TMTL) at Fort Sam Houston. The US Army Medical Department Center & School (AMEDD C&S) will be responsible for the facility; PEO STRI will procure and field all of the requisite equipment, simulators, and ancillary classroom items. This project is a US Army Medical Command priority and is supported by the AMEDD C&S Commanding General, Army Surgeon General and the Army Chief of Staff. The TMTL will be incorporated into the third phase of training as part of the eight week Critical Care Clinical Skill rotations. Flight Paramedics attend three phases of training: Phase 1. Flight Medic Course (4 weeks) Phase 2. National Registry of Emergency Medical Technician-Paramedic certification (26 weeks) Phase 3. Critical Care training/clinical skill rotations (8 weeks) The TMTL will be a dynamic indoor setting that will provide realistic, high fidelity training to flight medics on patient loading, unloading, and treatment and transfer of patients requiring intensive or critical care. The TMTL will consist of the following five areas: Transport Medical Trainer Room Instructor Control Room (ICR) Student Classroom (Debrief Area) Student Training Area Forward Surgical Team (FST) Training Laboratory 2.APPLICABLE DOCUMENTS The following documents are applicable to this SOW to the extent specified herein. In the event of a conflict between documents referenced herein and the contents of this SOW, the contents of this SOW shall be the governing requirement. 2.1Department of Defense Documents DoDI 5000.2Operation of the Defense Acquisition System DoDI 8500.2Information Assurance Implementation DoDI 8510.01DoD Information Assurance Certification and Accreditation Process (DIACAP) Copies of the DoD documents are available on the World Wide Web (www) at URL: http://www.dtic.mil/whs/directives/. 2.2Other Government Documents MIL-STD-130NIdentification Marking of U.S. Military Property MIL-STD-31000 Technical Data Packages GEIA-STD-0007Logistics Product Data AR 25-2Information Assurance ISO 9001:2000Quality Management and Quality Assurance PEO STRI Basic Accreditation Manual (BAM v6.0 30 September 2011) - Appendix D DIACAP Stand-alone System IA C&A Process. DIACAP Implementation Plan (DIP) for Standalone System for Mission Assurance Category (MAC) III, Confidentially Level Sensitive. The Standalone DIP has 32 controls. Stand Alone IS and Closed Restricted Networks Information Assurance Certification & Accreditation (IA C&A) requirements Version 1.0 08-DC-M-0010 10 OCT 2008. 3.REQUIREMENTS Data Rights. Software, technical data, and products direct from the prime contractor shall be provided with Government Purpose Rights (GPR) in accordance with applicable clauses contained in the Defense Federal Acquisition Regulation Supplement (DFARS). This includes software, technical data, and products developed by a sub-contractor to support this effort. Any licensed COTS software and technical data shall be provided with a transferable license that allows distribution and use for any PM MEDSIM purpose by any DoD contractor at no additional cost. 3.1Program Management The Contractor shall design, build, integrate and deliver a TMTL that meets the requirements as defined in this SOWand Systems Requirement Document (SRD) PRF-PT-00619. The Contractor shall provide all efforts, resources, facilities, equipment, and personnel necessary to complete the tasks in this SOW. The Contractor shall perform all activities to integrate and assemble the hardware and software to achieve a fully functional system, with all support systems, that performs and operates in accordance with the system specifications and contractor generated specifications. The Contractor shall provide the overall management and administrative efforts necessary to ensure that the requirements of this contract are accomplished. The Contractor shall track program progress utilizing metrics. The Contractor shall plan, implement, and maintain a Life Cycle Cost (LCC) management process to minimize the system cost and use LCC to conduct trade studies, evaluate design and support alternatives, and select the resource support requirements. The Contractor shall define and monitor metrics and technical performance measures (TPMs) to evaluate the performance of each critical technical and management process and conformance of the evolving products with contract requirements and objectives including cost requirements and objectives. The Contractor shall develop, implement, manage to, update, and maintain the contract Integrated Master Schedule (IMS). The Contractor shall conduct critical path analysis of the tasks and identify problem areas and corrective actions required to eliminate or reduce schedule impacts. The Contractor's Progress, Status and Management Report shall contain the IMS in Microsoft Project like format. DI-MGMT-80227 Contractor's Progress, Status, and Management Report 3.1.1Configuration Management The Contractor shall plan and implement an automated configuration management function to perform configuration control, configuration identification, audits, and status accounting in a system engineering environment. The Contractor shall develop, maintain, and update configuration management procedures and processes for control of all hardware and software baselines. The process shall allow simultaneous access to the common product data model coupled with the ability to coordinate and update immediate changes to the product definition data. The configuration management process must handle all levels of product and process integration to build and support the product as well as manage the sequence of significant events. The Government will maintain control of the functional baseline defined by the system performance specification, interface control documents, and software requirement specifications. 3.1.1.1Configuration Management Planning and Management The Contractor shall establish processes and tools to establish and maintain consistency between system requirements, system configuration information, and all relevant information about the system. The configuration management process shall include changes made to the IA configuration and associated documentation. 3.1.1.2Configuration Identification The Contractor shall identify unique identifiers for selected system attributes, system information and components to be used as the basis for configuration management. 3.1.1.3Configuration Change Management The Contractor shall establish a systematic and measurable configuration change management process for managing product configuration changes and variances. Once the system requirements have been approved by an authorized management activity, the Contractor shall effect changes to the baseline requirements only after the proposed change has been approved using the change process. 3.1.1.4Configuration Verification and Audit The Contractor shall verify and audit the system configuration information to ensure that requirement attributes are met and accurately documented. 3.1.1.4.1Request for Deviation (RFD) After PDR, the Contractor shall document the rationale and obtain the Government's written approval before deviating from any Government approved baseline. 3.1.2Risk Management The Contractor shall prepare, implement, and maintain a risk management process that includes identification, analysis, mitigation planning, mitigation plan implementation, and tracking. The Contractor shall develop and implement IA risk management, which will include security safeguards. These safeguards shall include but are not limited to, local policy and guidance; identification of threats, problems and requirements, and an adequate plan for the required resources. The Contractor's risk management process shall measure future uncertainties in achieving program goals within defined cost, schedule, and performance constraints. The IA risk shall be addressed across the risk management process and can be addressed in multiple areas. 3.1.3Management Reviews 3.1.3.1Start of Work Meeting / Post Award Conference (PAC) The contractor shall conduct a combined Start of Work Meeting / PAC, to be held 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 meeting shall include the Contractor's key team members identified in the proposal with emphasis on top-level management of the program, agreement on metrics that will be used as management indicators during the program, and partnering approach to be implemented. The Contractor shall present the program Integrated Master Schedule, IPT structure, management concept, organizational structure, and the interfaces with the Government that are employed to perform the TMTL 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.1.3.2Program Management Reviews (PMR) The Contractor shall conduct program management reviews on a monthly basis in accordance with the IMS. The first PMR shall be no more than 30 calendar days after the combined Start of Work Meeting / PAC. The program management review shall provide a program overview and shall include as a minimum: a.Hardware and software design status b.Risk Assessment c.Subcontract management/progress d.Data collection and modeling e.Production planning and status f.Logistics planning g.Test planning h.Training and technical publications status i.Schedule status j.Pre-selected topics of interest k.I/A Security l.Human Factors Engineering 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. Action item closure shall require Contractor and Government approval. 3.1.3.3DIACAP Implementation Plan (DIP) Review The Contractor shall assist PEO STRI with the DIACP Implementation Plan (DIP) Review. The DIP Review shall be held no less than 30 days prior to the Preliminary Design Review (PDR) to ensure IA requirements are agreed upon and allocated in the system design. 3.1.3.4Integrated Product Team (IPT) Meetings. The Contractor shall establish an IPT structure to address major areas of system development (e.g., systems engineering, hardware design, software design, integrated logistics support testing). The Contractor shall establish IPT charters and host regularly scheduled IPT meetings or teleconferences. The IPT meetings/teleconferences shall be used to address systems development 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.1.4Integrated Digital Environment (IDE) The Contractor shall provide an Internet based IDE to facilitate the electronic data interchange of all program data. All management, technical, cost, and schedule data (including all internal documents produced to design, develop, test and manage the program) shall be made available to all Government and contractor team members in an integrated, electronic, and query capable database, accessible via the Internet. The Contractor shall provide the capabilities for on-line review, comment, acceptance and approval of all deliverable data. 3.1.4.1Antiterrorism (AT) / Operations Security (OPSEC) When required to be at an Army controlled installation, facility or area, the Contractor and all associated sub-contractors shall comply with applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by government representative) and all requirements of the clauses in the contract. The Contractor shall also provide all information required for background checks to meet installation access requirements to be accomplished by installation Provost Marshal Office, Director of Emergency Service or Security Office. The Contractor workforce must comply with all personal identity verification requirements 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 (FPCON) at any individual facility or installation change, the Government may require changes in contractor security matters or processes. 3.2Systems Engineering The Contractor shall translate the basic operational needs, requirements and objectives, interface, and other design constraints including cost, into preliminary, verifiable, functional requirements and objectives, while conducting cost-benefit trades to support refinement of the preliminary functional requirements. The Contractor shall complete the system design (balanced with respect to performance, cost, schedule, and risk) and verify it meets the system requirements. The Contractor shall assess proposed changes in the evolving functional architecture, physical hierarchy, and baselines and objectively trade alternatives to balance performance, cost, schedule, and risk prior to approval. 3.2.1System Design The Contractor shall use the specifications and requirements documents associated with the TMTL as the basis for development of all implementing specifications. The design concept shall include incorporating an open systems approach which 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) shall be used for selected system interfaces, products, practices and tools. Selected designs and specifications shall be based on performance, cost, industry acceptance, long term availability, supportability, and upgrade potential. 3.2.1.1Preliminary Design Stage The Contractor shall initiate subsystem design and create subsystem-level definition and quote mark design-to quote mark baselines to guide component development. The Contractor shall decompose identified subsystem functions into lower-level functions, allocate functional and performance requirements to component-level functional and physical architectures. Each preliminary subsystem requirements and verification definition and preliminary quote mark design-to quote mark baseline shall be evolved into a subsystem requirement and verification definition and quote mark design-to quote mark baseline. Preliminary component requirements and verification definition and build-to baselines shall be defined for the components and the subsystem being developed. Final subsystem definition shall include identification of recommended components and interfaces; resolution of subsystem-level risks; assessment of component risks; and design for quality factors to include producibility, verifiability, usability, supportability, trainability, and disposability for each subsystem. Subsystem reviews (IPT meetings) shall be completed for each subsystem. The Contractor shall present the TMTL preliminary design to the Government at a Technical Review. 3.2.1.2Detailed Design Stage The Contractor shall complete subsystem design down to the lowest component level, create a component requirements and verification definition and build-to component baseline for each component. Final component definition shall include identification of recommended parts and interfaces, and resolution of component-level risks. For each component, down to the lowest sub-component, the design for quality factors will include producibility, verifiability, usability, supportability, trainability, and disposability. Component reviews (IPT meetings) shall be completed for each component at the completion of the detailed design stage. The results of the evaluation shall be documented. The Contractor shall present the completed TMTL design to the Government at the Critical Design Review (CDR). 3.2.1.3Fabrication, Assembly, Integration and Test Stage The Contractor shall fabricate, assemble and integrate the subsystems into a complete system that meets the requirements of the specifications and requirements documents. The Contractor shall resolve product deficiencies when specifications for the system, product, subsystem, assembly, or component are not met, as determined by inspection, analysis, demonstration, Government agreed certifications or tests. The Contractor shall test the system and subsystems needed to verify that the products meet the performance requirements stated in the associated System Requirement Document (SRD) PRF-PT-00619. 3.2.2Hardware Engineering The Contractor shall integrate and assemble the system hardware that satisfies the performance and IA requirements stated in the developed specifications. The Contractor shall conduct market surveillance and market investigations in order to maximize the use of commercial and non-developmental items. The Contractor shall apply the systems engineering process during each level of system development (system, subsystem, and component) to add value (additional detail) to the products defined in the prior application of the process. Through each of the following design stages (system/hardware requirements analysis; hardware requirements analysis; preliminary design; detailed design; fabrication; testing; system integration and testing), information generated shall be documented in an integrated database. 3.2.3Software Engineering The Contractor and associated subcontractors shall follow software development practices that are compliant with at least Level three (3) of the Software Engineering Institute's Capability Maturity Model Integration (CMMI). The design process shall incorporate features that promote assessment of open source software products with ease of operation, integration, software maintenance, future updates, and modifications. Computer programs and computer data systems shall be fully integrated in accordance with the system specification. The Contractor shall conduct market surveillance and market investigations in order to maximize the use of open source software, commercial software, Government owned, and non-developmental software. 3.2.3.1Software Requirements and Architecture Development and Review The Contractor shall develop software requirements and architecture in accordance with the contractor's software development process plan. All analysis and results shall be documented in an integrated database. The Contractor is encouraged to suggest revisions to government requirements where such revisions would result in cost or schedule reduction or performance improvements. The Contractor shall define and record the operational concept for the system, define and record the architectural design of the system (identifying the components of the system, their interfaces, and a concept of execution among them) and the traceability between the system components and system requirements. Based upon analysis of system requirements, system design, and other considerations, the contractor shall define and record the software requirements to be met by each software item, the methods to be used to ensure that each requirement has been met, and the traceability between the software item requirements and system requirements. 3.2.3.2Software Design and Implementation The Contractor shall design software, develop executable code, perform unit testing, and integrate software components (with each other and with hardware components) to meet system requirements. Software design includes not only design to requirements but also selection of existing software products, including open source software, to meet system requirements and iterating the requirements to allow use of existing products when indicated by cost as an independent variable (CAIV) or schedule as an independent variable (SAIV) trades. DI-IPSC-81435 Software Design Description (SDD) DI-IPSC-81441 Software Product Specification (SPS) 3.2.3.3Software Development Test The Contractor shall establish and execute a software item qualification test program consisting of program or module and cycle or system levels of testing. For each software item, the contractor shall determine if that item warrants a verification effort and the degree of organizational independence of that effort needed. If the item warrants an independent verification effort, a qualified organization responsible for conducting the verification shall be selected. The Contractor shall document the life cycle activities for each software item subject to verification; the required verification tasks for each life cycle activity; and related resources, responsibilities, and schedule. The Contractor shall establish test cases (in terms of inputs, expected results, and evaluation criteria) and establish traceability between the test case and the system requirements, detailed procedures for conducting the test, and test data for testing the software corresponding to each software item. The Contractor shall test the software corresponding to each software item. The testing shall be in accordance with the unit test cases and procedures. The Contractor shall analyze the results of item testing and shall record the test and analysis results. Prior to the start of final test, the contractor shall upgrade the commercial-off-the-shelf (COTS) products to the latest versions approved by the system software configuration control board. The Contractor shall conduct a software item test readiness review prior to initiating the formal qualification test. 3.2.3.4Software Integrity Certification The Contractor shall verify and certify that the system application software functions are designed in a properly secured operating system environment and is free of elements that might be detrimental to the secure operation of the resource operating system, as described in DoDI 8500.2. 3.2.4Hardware and Software Integration The Contractor shall perform all activities to integrate and assemble the hardware and software to achieve a fully functional system. All support systems shall perform and operate in accordance with the system specification and Contractor generated specifications. The Contractor shall verify the complete integration of the hardware and software of each hardware and software subsystem and the overall system through the utilization of formalized testing. 3.2.5Information Assurance The Contractor shall address and implement the IA security requirements for a connected system that has a Mission Assurance Category (MAC) III and a Sensitive confidentiality level. The Contractor shall follow the PEO STRI BAM and standard DIACAP processes and procedures for a Sensitive MAC III accredited system to account for all security system changes. All IA and IA-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/index.html and implement each STIG into the design. As part of the system design and component selection process, IA shall be considered as a requirement for all systems used to enter, process, store, display, or transmit information. IA shall be achieved through the acquisition and appropriate implementation of evaluated or validated GOTS or COTS IA and IA-enabled IT products. All Commercial-Off-The-Shelf (COTS) IA products and IA-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) IA products or IA-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) an IA 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 IA validated products from one of the links below. If CHESS items are not on the Common Criteria Certified Products (1) or NIAP Validated Product List (2), all IA and IA-enabled products must be on the APLITS (3). 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 will be no waiver issued by the government for unapproved IA products. 3.2.5.1Information Assurance Artifacts The Contractor shall comply with the IA process in accordance with DoD 8510.01 (DIACAP) and PEO STRI BAM. The Contractor shall produce all components of the DIACAP package necessary to deliver and operate a fully accredited system. The Contractor shall ensure that the security requirements and procedures are met in accordance with all required DoD and Army regulation per the Mission Assurance Category and Confidentiality levels agreed upon for the system. DI-MISC-80711 Scientific and Technical Reports 3.2.5.2Information Assurance Vulnerability Management Program As part of the Information Assurance Vulnerability Management Program (IAVMP), the contractor shall document the incorporated and unincorporated Information Assurance Vulnerability Alerts (IAVAs), Information Assurance Vulnerability Bulletins (IAVBs), and Information Assurance Vulnerability Technical Advisories (IAVTAs). The IAVMP plan shall include, but is not limited to, identifying and assessing potential threats to determine risks. It also involves developing and implementing controls, countermeasures, or solutions. The Contractor shall monitor the system for compliance and success while evaluating and refining the IAVMP as necessary. The Contractor shall incorporate all applicable DoD and Department of the Army (DA) Information Assurance Vulnerability Management messages issued on behalf of the Department of Army G3, CIO/G6 and Joint Task Force-Global Network Operations. The Contractor shall provide justification for each unincorporated IAVMP message (i.e., describe the specific negative impact the IAVMP message incorporation would have on the system operation). 3.2.6Specialty Engineering The Contractor shall provide Supportability Engineering, Reliability, Availability and Maintainability (RAM) Engineering, Safety Engineering, Quality Engineering, Human Factors Engineering, Electromagnetic Environment Effects (E3) Engineering, Containment and Corrosion Control, Standardization and Human System Integration as defined in the sections below. 3.2.6.1Supportability Engineering The Contractor shall ensure the supportability of the system through planning, implementation, and verification of materials, services and resources required to satisfy the operational requirements. Supportability by the requesting agency or a third party Contractors for hardware, software and documentation for maintenance shall be a requirement. Readiness, availability, supportability and Life Cycle Cost (LCC) shall be the primary design factors. The Contractor shall evaluate reliability, availability and maintainability factors in the design process. Design for supportability shall include the use of common fasteners and connectors, common commercial standards, and proven technology to the maximum extent possible. The system design shall minimize life-cycle costs and maximize life-cycle supportability by avoiding the use of proprietary items; components with limited sources for spare parts, support, or maintenance; recurring usage or service fees; and the need for special tools or test equipment. 3.2.6.2Reliability Engineering The Contractor shall develop, implement, and manage a system reliability process satisfying all reliability objectives and be completely integrated within the systems engineering process. The reliability process shall support economical achievement of overall program objectives and ensure sustained product integrity, personal safety, and logistics support information is derived from early reliability engineering analysis such that reliability engineering can be applied to influence the design effort. The process shall: a.Improve operational readiness and mission success of the system. b.Reduce system demand for maintenance manpower and logistic support. c.Provide essential management information. d.Hold down the reliability programs own impact on overall program cost and schedule. Specific reliability design and verification criteria shall be established. Quantitative reliability requirements for the system, all major subsystems, and equipment shall be included in section 3 and section 4 of the system and item specifications. All reliability data and information used for logistics support analysis and engineering activities shall be based upon, and traceable to, the outputs of the reliability process. Reliability status shall be included as part of each program review. The Contractor shall conduct trade off studies to ensure quantitative issues such as stress levels, selection of parts, parts simplicity and redundancy are properly considered in the design trade off. The Contractor shall verify that reliability requirements are attained through analyses and test. 3.2.6.3Maintainability Engineering The Contractor shall develop, implement, and maintain a system maintainability process satisfying all maintainability and related objectives and be completely integrated within the systems engineering process. The maintainability process shall form the basis of concurrent and subsequent life cycle planning. The maintainability effort shall measure complexity, accessibility, and testability to enhance servicing, preventive maintenance, corrective maintenance, and diagnostic capabilities. Specific design and verification criteria shall be established through performance specifications of qualitative and quantitative factors to be expressed as measures of maintainability achievement for system, segment, subsystem, and equipment levels. 3.2.6.4Safety Engineering The Contractor shall develop 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-80102B Safety Assessment Report (SAR) 3.2.6.4.1Health Hazard Assessment The Contractor shall identify potential health hazards and recommend engineering controls, equipment and protective procedures to reduce the associated risk to an acceptable level. The Contractor shall assess system, facility, and personnel protective equipment design requirements to allow safe operation and maintenance. When feasible engineering designs are not available to reduce hazards to acceptable levels, the contractor shall develop alternative protective measures. The Contractor shall address the hazardous materials listed in the Environmental Protection Agency's (EPA) toxics release inventory (available at http://www.epa.gov/tri/chemical/index.htm) and the list of Class I and Class II stratospheric ozone depleting substances (ODSs), as listed 29CFR1910.1200. 3.2.6.5Quality Engineering 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. Metrics shall be developed to assist management visibility into an adequate process control system. The Contractor shall establish and maintain a computerized discrepancy tracking system within the IDE with the ability to produce complete permanent records of all discrepancy or database listings. The Contractor shall establish a suspense system to ensure timeliness of analysis and corrective action for discrepancies and risk reduction items. All discrepancy correction shall be documented and entered in an integrated database. The contractor shall use process controls and continuous process improvement to achieve quality hardware and software. The Contractor shall update, maintain, and execute a Quality Program to achieve these ends. Quality Management System shall be IAW ISO 9001:2000, AS9100 (Series) or equivalent. The Contractor shall upon request by the Procuring Contracting Officer (PCO), the Contracting Officer Representative (COR), or as part of regularly scheduled program reviews, present quality status related to overall quality system status, procedure/process changes or initiatives, or areas of concern/quality issues. At the Governments discretion, the PM may conduct a quality audit to validate compliance to AS 9100/ISO 9001 or the equivalent commercial standard being used and compliance to contract requirements. The Government must give the Contractor thirty (30) days written notice or appropriate lead-time of their intent to conduct this quality audit. The frequency of these audits will be no more than once a year unless program problems or hardware issues dictate that additional audits are required. 3.2.6.5.1Test Discrepancies The Contractor shall document all test discrepancies for Contractor conducted tests and track the failure analysis and corrective action for each test discrepancies until correction and regression test are successfully completed. The Contractor shall establish a suspense system to ensure timeliness of analysis and corrective action of each test discrepancy. The Contractor shall establish a process to receive test discrepancies from any IPT member and accomplish data entry. Upon correction of the test discrepancies, the Contractor shall test the system to ensure that the correction of the test discrepancies did not interfere with or alter the functionality of the system. Upon closeout of a discrepancy, the contractor's process shall notify the government designated test director that an integrated database has been updated. 3.2.6.5.2Discrepancy Processing The Contractor shall document a detailed description defining the changes made to the equipment, hardware, and software to correct each discrepancy. Each discrepancy correction that modifies or changes any baseline shall be documented and entered in the configuration management system. Discrepancies ready for recheck shall normally accumulate into sufficient quantities to permit at least eight (8) hours of continuous testing. 3.2.6.5.3Test Discrepancy Priorities The Contractor shall assign level of effort to test discrepancies based on the priority codes assigned by the test team in accordance with the ground rules established by the IPT. The following priorities shall be assigned with the government reserving the right to make the final determination of the priority of any test discrepancy: PriorityDescriptionSchedule Impact 1Safety item or system failureTesting halted 2Subsystem failureSome testing impossible 3Training impact which may affect testingFix prior to next assessment milestone 4Training impact which has no testing impact Fix prior to DD Form 250 5IA Vulnerabilities (CAT I & II) CAT III vulnerabilities must have mitigations approved by the DAAFix prior to becoming operational and Prior to DD Form 250 6Minor training impactFix TBD 3.2.6.6Human Factors Engineering The Contractor shall plan and implement a human factors engineering program to insure the satisfaction of system objectives and personnel safety of the operator and maintainer. The Contractor shall insure management control of the human engineering effort and specifically ensure that: a.System requirements are achieved by consideration of the capabilities and limitations of the human component; b.Through proper design of equipment, software and associated user interfaces, and environment, the personnel-equipment-software combination meets system performance goals; c.Design features will not constitute an undue hazard to personnel; d.Trade-off points between automated versus manual operation have been chosen for peak system effectiveness within appropriate cost limits; e.The application of human engineering principles to system design is technically adequate; f.The equipment is designed to facilitate required maintenance; g.Procedures for operating and maintaining equipment are efficient, reliable, and safe; h.Potential error-inducing equipment design features are minimized; and i.The layout of the facility and the arrangement of equipment affords efficient communication and use. 3.2.6.7Electromagnetic Environmental Effects (E3) Engineering The Contractor shall determine the criteria and verification method to ensure that the system electronic or electrical hardware configuration is not a source of electromagnetic interference (EMI) or a victim of E3 in the intended operational environment in which it is installed or at its operational locations. The Contractor shall establish and maintain a process to verify and assure that the system operations functionality is not affected by E3. 3.2.6.8Contaminate and Corrosion Control The Contractor shall incorporate the latest state-of-the-art corrosion control technology as determined by logistic support analysis into the system design process, the manufacturing process, and all levels of maintenance, supply, and storage processes. The objective is to minimize corrosion by using design and manufacturing practices that address selection of materials; coatings and surface treatments; production processes; process specifications; system geometry; material limitations; environmental extremes; storage and ready conditions; preservation and packaging requirements; and repairs, overhaul, and spare parts requirements. Design concepts shall reflect realistic environments and resource availability as determined by logistic support analysis. 3.2.6.9Standardization The Contractor shall influence the system design to achieve maximum subsystem, component, and repair parts commonality. The Contractor shall minimize equipment and parts proliferation through a standardization effort. The standardization effort shall include coordination with PEO STRI Life Cycle Contractor Support (LCCS) contractors to maximize use of parts already in the inventory or to determine that the existing logistics support resources will benefit from the items chosen for the system. 3.2.6.10Human System Integration (HSI) The Contractor shall establish a plan for Human System Integration for any program that requires personnel (as operators, maintainers or supporters) to ensure a total system approach that will accommodate the cognitive, physical and sensory skills of the specified user population. 3.2.7Design Reviews Contractor shall conduct reviews, to include design reviews (system, subsystem, component, life cycle processes, test readiness, production approval) and audits (functional and physical configuration), for the purpose of assessing technical progress. The Contractor shall document the results of the review, including any resulting action items. 3.2.7.1Preliminary Design Review (PDR) The Preliminary Design Review (PDR) is a multi-disciplined product and process assessment to ensure that the system can proceed into detailed design and can meet the stated performance requirements within cost (program budget), schedule (program schedule), risk, and other system constraints. This review will assess the system preliminary design as captured in performance specifications for each configuration item in the system (allocated baseline) and ensures that each function in the functional baseline has been allocated to one or more system configuration items. PDR determines whether the hardware and software preliminary designs are complete and the IPT is prepared to start detailed design and test procedure development. See Appendix A for Entry and Exit Criteria and PDR Products. 3.2.7.2Critical Design Review The Critical Design Review (CDR) is a multi-disciplined product and process assessment to ensure that the system can proceed to system fabrication, demonstration, and test and can meet the stated performance requirements within cost (program budget), schedule (program schedule), risk, and other system constraints. This review will assesses the system final design as captured in product specifications for each configuration item in the system (product baseline), and ensures that each product in the product baseline has been captured in the detailed design documentation. Product specifications for hardware must enable the fabrication of configuration items, and shall include product definition data. Product specifications for software (e.g. Software Design Documents) must enable coding of a Computer Software Configuration Item (CSCI). Configuration items may consist of hardware and software elements. The subsystem detailed designs shall be evaluated to determine whether they correctly and completely implement all system requirements allocated to the subsystem and whether the traceability of final subsystem requirements to final system detail design is maintained. At this review, the IPT shall also review the results of peer reviews on requirements and final detail design documentation and ensure that latest estimates of cost (development, production, and support) are consistent with the detail design. A successful review is predicated on the IPT's determination that the subsystem requirements, subsystem detail design, results of peer reviews, and plans for testing form a satisfactory basis for proceeding to system fabrication, demonstration, and test. See Appendix A for Entry and Exit Criteria and CDR Products. Once the Government has approved the design at CDR, the Contractor shall submit Engineering Change Proposals (ECPs) when a change is proposed to the configuration management baseline for Government review and approval prior to proceeding. 3.2.8Product Definition Data (PDD) During the systems engineering and design, and in accordance with MIL-STD-31000, the contractor shall develop, produce, and maintain product definition data (PDD) that accurately depicts the final product. The PDD is the technical description of items adequate for supporting an acquisition strategy, production, engineering, IA, and logistics support. The PDD shall disclose complete design, IA, 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, IA, manufacturing, and quality assurance requirements information necessary to enable the procurement or manufacture of an interchangeable item that duplicates the physical, IA, and performance characteristics of the original product without additional design engineering effort or recourse to the original design activity. The Contractor shall identify the higher-level components and assemblies to be repetitively procured as spare components and assemblies or that may be procured independently. For each higher-level component or assembly, the Contractor shall determine and document the functional requirements for the item, the environment in which it must operate, interface and interchangeability characteristics, and criteria for verifying Logistics Support criteria. DI-SESS-81003C Commercial Drawings and Associated List DI-SESS-81000C Product Drawings and Associated List 3.3Logistics The Contractor shall conduct engineering analyses to establish quantitative and qualitative supportability design guidelines. The Contractor shall conduct trade studies, evaluate design and support alternatives, and establish system supportability preliminary design configurations consistent with system readiness and availability and life cycle cost goals. The Contractor shall coordinate with existing life cycle contractor support (LCCS) using associate contractor agreements, develop initial fielding plans for the system, and verify that the maintenance actions and support structure are aligned with the maintenance concept. 3.3.1Logistics Support Analysis The Contractor shall identify support resources and infrastructure necessary for test and evaluation activities. The Contractor shall analyze existing LCCS support structures and develop and define an optimized support infrastructure for production and deployment. 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.3.2Supportability Analysis and Logistics Management Information The Contractor shall conduct repair level analyses; develop diagnostic, preventative maintenance and repair procedures; conduct facilities analyses; refine hardware and software maintenance and support concepts; and identify support resource requirements including required spares and support equipment. Using SM&R Codes, the contractor shall develop a listing of which items should be repaired and which should be discarded and the level of maintenance at which the repair should be performed with the associated cost. The Contractor shall document the following in a database: a.All input data and their corresponding value and source of the data; b.Operational scenario modeled, assumptions made, constraints assumed, and non-economic factors imposed; c.Maintenance alternatives considered; d.Analytical method and models used to perform the economic evaluations; and e.Discussion of the sensitivity evaluation performed and results obtained. DI-SESS-81758 Logistics Product Data 3.3.3Technical Publications The Contractor shall describe each operation and maintenance task in detail and in logical, systematic steps for the work to be accomplished. 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. DI-TMSS-80527 Commercial Off The Shelf Manuals & Associated Supplemental Data 3.3.3.1Operator User's Manual (OUM) The Contractor shall deliver an OUM documenting tasks necessary to operate the trainer. 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-2BPreparation of Digital Technical Information for Page Based Technical Information (Table A-II) 3.3.3.2System Maintenance Manual (SMM) The Contractor shall deliver an SMM documenting tasks necessary to maintain the trainer. 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-2BPreparation of Digital Technical Information for Page Based Technical Information (Table A-IV) 3.3.3.3Publications In Process Review's (IPR's) The Contractor shall host and co-chair publication reviews to ensure 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.3.4Item Unique Identification (IUID) The Contractor shall coordinate among the IPT members to determine items requiring unique identification including embedded subassemblies, components, and parts and identify the UID to be used for each item. The Contractor shall provide unique item identification, or a DoD-recognized unique identification equivalent, for all identified items delivered. UID marking design for each item shall be both machine readable and human readable in accordance with MIL-STD-130N. DI-MGMT-81858 Unique Identification (IUID) Marking and Verification Report 3.3.5Training 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. This includes Government Furnished Information (GFI) and data developed by the contractor incident to other contractual requirements. 3.3.5.1Course Conduct Information Package The system training data product shall provide data required by the government for outsourcing the conduct of training. The system product shall provide sufficient information for an accurate evaluation of a student's capabilities to meet all learning objectives of a course and shall identify prerequisite knowledge and skills of students entering the course. The product shall inform students of the training syllabus, organization, operation, scheduling, and other pertinent information. The product shall also provide information on an evaluation of a trainee's performance, the trainee evaluation of training, and shall provide the trainee with a certificate of training. DI-SESS-81522 Course Conduct Information Package 3.3.5.2 New Equipment Training (NET) and Support The Contractor shall 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 develop a complete and exportable training support package that integrates training products, materials, and other pertinent information necessary for system training. The Contractor shall design and develop this training support package using instructional systems design processes. 3.3.5.2.1Instructor / Operator (I/O) Training The Contractor shall plan, develop, 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.3.5.2.2Maintenance Training The Contractor shall plan, develop, conduct, and document the completion of the initial maintainer course for the initial cadre of maintenance personnel prior to government acceptance. 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.4Interim Contractor Support (ICS) The Contractor shall provide ICS services at the fielding location for 12 months immediately after User Acceptance Test (UAT). The Contractor shall maintain a high level of security awareness commensurate with the Mission Assurance Category (MAC) and Confidentiality Level. The Contractor shall implement the Army approved Information Assurance Vulnerability Management program during the ICS period and shall assist in compliance reporting. A one-year ICS period was considered as the desired capability in lieu of the LCCS that could not be fully provided by the first unit equipped date because of time or acquisition program constraints. The ICS contract identified minimum data to be provided to the Government by the contractor (such as defective or nonconforming parts, task frequency, parts usage, and repair times at each maintenance level; mean times between maintenance failures; engineering changes; and skills/training needed). 3.4.1Software Support The Contractor shall provide services to maintain and update system software for the duration of the ICS effort. At the end of the ICS effort, the contractor shall deliver, install, and check-out for proper operation a subset of the development software support environment to serve as the sole means to sustainment for the system software. The software support environment shall include all commercial, government-funded, and contractor proprietary software, all necessary documentation/specifications, plus executing hardware with all applicable licenses necessary to enable the government to fully support all system software. 3.4.2Site Support The Contractor shall provide support and management of site logistical operations to obtain a Government-designated readiness rate of 90 percent. In accomplishing this mission, the contractor shall perform the administrative, operational, maintenance, supply, technical documentation change and revision program, and other support functions required. 3.4.3Engineering Services The Contractor shall provide engineering services to support the program and operational use of the system. Engineering services efforts are limited to those non-repetitive investigation, inspection, analysis, evaluation, design, documentation, fabrication, and testing tasks that are in addition to those services required by the ICS effort or to deliver acceptable hardware items after start of production. 3.4.4Transition 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).
 

Web Link

FBO.gov Permalink
(https://www.fbo.gov/spg/USA/STRICOM/W900KK/W900KK-14-R-0040/listing.html)
 

Place of Performance

Address: PEO STRI Acquisition Center 12350 Research Parkway, Orlando FL

Zip Code: 32826-3276
 

Record

SN03310470-W 20140315/140313235539-4e6f64ccb36e5027727cf673facaccd7 (fbodaily.com)
 

Source

FedBizOpps Link to This Notice
(may not be valid after Archive Date)

---

| FSG Index  |  This Issue's Index  |  Today's FBO Daily Index Page |