PWS - TES.docx

UNCLASSIFIED: Distribution Statement A. Approved For Public Release: Distribution Unlimited

RFP: W56HZV-16-R-0064 UNCLASSIFIED

PWS

C.1 INTRODUCTION & OBJECTIVES

C.1.1 Introduction. This non-personal service Performance Work Statement (PWS) establishes the requirements for contractor-provided services to the Tank-Automotive Research, Development and Engineering Center (TARDEC). This PWS describes the scope and content of the technical and engineering services to be provided by the contractor in order to assist TARDEC in its In-Service engineering and Science and Technology missions. These missions emphasize technical and engineering services for Program and Project Managers (PMs) within Program Executive Office (PEO)-Ground Combat Systems and PEO Combat Support & Combat Service Support or their successor organizations. TARDEC also develops and manages Science and Technology, including Technology Enabled Capability Demonstration (TECD) programs, along with providing technical engineering services to other Army and Government organizations or their successor in the Government ground systems domain.

C.1.2 Objectives. The contractor shall provide, on a Work Directive (WD) basis, the required expertise to TARDEC in performing and completing its missions. The contractor shall advise TARDEC on technical and programmatic issues. The contractor shall provide personnel on-site at TARDEC and other CONUS and OCONUS locations. This PWS defines the services required to deliver technical and engineering services to TARDEC which include lifecycle engineering to the PMs in all phases of the life cycle from Material Solution Analysis to Operations & Support. The effort provides engineering support in the acquisition and development of survivability systems, military ground vehicle robotics, software development and Post Production Software Support (PPSS), electrical and electronics architectures, high voltage power electronics, information systems security, mechanical engineering, science and technology, research and development projects, security engineering, and systems engineering on projects within TARDEC, projects managed and supported by TARDEC personnel, and projects in support of the PMs’ main weapon systems platforms. The furnishing of Continental United States (CONUS) and Outside CONUS (OCONUS) Field Service Representatives and vehicle maintenance is also covered by this PWS.

C.1.2.1 The technical and engineering services specified herein are in support of the TARDEC projects and the vehicles platforms identified below:

-- Project Director (PD), Main Battle Tank Systems (MBTS), -- PM Armored Fighting Vehicles (AFV), -- PM Stryker, -- PM Armored Multi-Purpose Vehicle (AMPV), -- PM Mine Resistant Ambush Protection (MRAP), and;

-- TARDEC organization programs

C.1.3 The contractor shall work as an independent contractor and not as an agent or employee of the Government and provide up to 2,622,600 man-hours, inclusive of all options. Contractor personnel, consultants, and subcontractor personnel providing services hereunder are under the sole administrative control and supervision of the contractor, regardless of location. The Government shall not exercise any supervision or control over the contractor personnel, consultants, or subcontractor personnel performing the services herein. Such personnel shall be accountable solely to the contractor.

C.1.4 Work Directives. All work shall be performed IAW the Work Directives (WDs) to include reference to applicable PWS paragraphs, issued by the Procuring Contracting Officer (PCO). Pursuant to the terms outlined in Section H.9 of this contract, WDs can be executed under this contract either as Term scope or Completion scope through exercise of available hours. Each WD shall be within the general scope of this contract and will be incorporated as an attachment to the contract. No work shall commence until the contractor has received a fully executed WD. Each WD will include the information stated in Section H.10.

C.1.4.1 Work Directive Type. Each WD will indicate if it is a Term WD (also referred to as Level-of-Effort (LOE)) or completion WD based on the requirements stated within the WDs.

C.1.4.1.1 Term WDs describe the work in general terms and obligate the contractor to devote a specified level of effort for a stated time period. At its discretion, the Government may exercise additional hours to continue the effort. Term WDs will only be funded as Cost Plus Fixed Fee (CPFF).

C.1.4.1.2 Completion WDs describe a WD scope that states a definite goal or target and specified end product. Completion scope WDs require the contractor to complete and deliver the specified end product (e.g. a final report of research accomplishing the goal or target) regardless of the number of hours awarded and/or performed. Completion WDs may be either CPFF or Firm Fixed Price (FFP) based on the requirements stated within the WD.

C.2 APPLICABLE DOCUMENTS. Performance may be required in accordance with (IAW) any of the documents listed in Section C.2.1 thru C.2.2 below. This is not an exhaustive list and other documents may be required as specified in the individual WDs. The specific sections of the document will be specified in the individual WD as necessary. The contractor shall be responsible for the most recent version of the regulations, standards, handbooks, specifications, and other Government publications.

C.2.1 Specifications, standards, and handbooks:

Army Regulation (AR) 25-1 (Army Information Technology)

AR 25-2 (Information Assurance)

AR 380-5 (Department of the Army Information Security Program)

AR 380-10 (Foreign Disclosure and Contacts with Foreign Representatives)

AR 380-67 (Personnel Security Program)

Military Standard (MIL-STD) 1472G (Department of Defense Design Criteria Standard Human Factors Engineering)

Military Handbook (MIL-HDBK) 48655A (Department of Defense Handbook Human Engineering Program, Process, and Procedures)

Department of Defense Instruction (DoDI) 8510.01 (Risk Management Framework for DoD Information Technology)

Department of Defense Manual 8570.1 (Information Assurance Workforce Improvement Program)

C.2.2 Configuration Management and Data Management References. The contractor is encouraged to use:

American Society of Mechanical Engineers (ASME) Y14.1 (Decimal Inch Drawing Sheet Size and Format);

ASME Y14.5 (Geometric Dimensioning and Tolerancing);

ASME Y14.24 (Types and applications of engineering drawings);

ASME Y14.34 (Associated Lists);

ASME Y14.35 (Revision of Engineering Drawings and Associated Documents);

ASME Y14.38 (Abbreviations and Acronyms for Use on Drawings and Related Documents);

ASME Y14.100 (Engineering Drawing Practices);

DoDI 5230.24 (Distribution Statements on Technical Documents);

Department of Defense Directive (DoDD) 5230.25 (Withholding of Unclassified Technical Data From Public Disclosure);

DFARS 252.211-7003 – Item Unique Identification and Valuation

Government Electronics and Information Technology Association (EIA) EIA-649-1, (Configuration Management Requirements for Defense Contracts);

GEIA-859 (Data Management (DM));

MIL-HDBK-61 (Configuration Management Guidance);

MIL-STD-31000 (Technical Data Packages); and

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

C.2.3 Contract Data Item List (CDRL) Data Item Descriptions (DID). The CDRL DIDs listed in Exhibit A can be found at http://quicksearch.dla.mil/. Insert the 12 digit authority reference (including dashes) in Box 4 of the CDRL in the Document ID box and click submit.

C.3 GENERAL REQUIREMENTS

C.3.1 Reserved

C.3.2 Access to Data. On request by the PCO or Contracting Officer’s Representative (COR), the contractor agrees to provide access to records and data pertaining to performance of work on this contract. The Government shall have access rights to all data (e.g. hard copy and computer files generated under this contract, and all underlying data and files) generated under this contract as well as reports, assessments, software programs, technical reports and analyses.

C.3.3 The contractor shall use computer software, which is compatible with the hardware and software utilized by TARDEC including: PC Microsoft Office 2010 and Microsoft Project 2010.

C.3.3.1 Artifacts shall be prepared using tools and formats compatible with TARDEC design tools.

C.3.4 The Government may provide to the contractor components, subsystems (built up from several components), systems, vehicles, Government Furnished Material (GFM), Government Furnished Systems (GFS), or data as Government Furnished Equipment (GFE), or Government Furnished Information (GFI) for installation onto or into projects or programs for integration, testing and evaluation.

C.3.5 The contractor shall be responsible for integrating and or installing components or sub-systems (built up from several components) delivered by independent developers or other Government contractors for testing and evaluation.

C.3.5.1 The contractor shall establish and maintain non-disclosure agreements (NDAs) with other willing commercial industry entities and provide a copy of the NDAs to the COR and PCO. Many programs TARDEC is involved in make use of proprietary information that requires NDAs. To be fully engaged in those programs on behalf of TARDEC the contractor will be required to access that information but provide assurance that said information will not be proliferated.

C.3.5.2 The contractor is responsible for providing executed NDAs for all personnel supporting TARDEC under this contract in order to protect all proprietary, restricted, competition sensitive, or any other restricted (e.g. non-foreign disclosure due to public law) data that will be used or accessed during the execution of this contract. The NDAs shall be provided IAW Section L provision 52.215-4405, “Access to the Detroit Arsenal; Identifying Contractor Employees; Non-Disclosure Statement.” The contractor shall provide the executed NDAs to the COR and the PCO prior to commencing work under the contract or obtaining the badges permitting access to the property.

C.3.6 The contractor shall not duplicate or otherwise provide efforts for any requirements under this contract that it has performed or is performing under any current or past Government contract(s). In the event that the Government issues a WD under this contract that is a duplication of any prior work or effort, the contractor shall promptly notify the PCO and the COR and shall identify and explain the duplication of work.

C.3.7 The contractor shall manage and control the resources necessary to ensure timely achievement of all requirements of this contract in the most economical manner possible.

C.3.8 The contractor shall (i) establish a single focal point, as Program Manager, who has management and fiscal responsibility over the entire contract and (ii) maintain a supporting program management system tailored to accomplishing the administrative, management, technical, and financial requirements of the tasks associated with each individual WD.

C.3.9 Reserved

C.3.10 Place of Performance. The contractor shall perform the work under this contract at Detroit Arsenal, Warren, MI; Selfridge Air National Guard Base (SANG), Harrison Twp., MI; Contractor Location; and other CONUS and OCONUS location as defined by the individual TIs.

C.3.11 Anticipated Travel. In conjunction with required engineering services, and to the extent specified per the individual WDs, the contractor shall be required to travel for purposes such as: to observe or conduct tests, ensure compatibility of configuration changes and other integration services, and furnish guidance to operational and maintenance personnel regarding the techniques of product/system modifications. Contractor personnel potentially may also travel to attend project meetings, present papers and attend technical conferences. The number of trips and types of personnel shall be limited to the minimum required to accomplish work requirements.

C.3.11.1 Reimbursement of Travel Costs. Reimbursement for travel, subsistence, and lodging will be paid to the contractor only to the extent that is it necessary for performance of a WD under the contract and allowable under the Joint Travel Regulation (JTR).

C.3.11.1.1 All travel costs associated with the contractor employee(s) driving to/from work shall be at the contractor’s expense and not reimbursable by the Government. All other travel expenses are subject to the JTR and PCO approval. The Government will not pay any travel expenses for the contractor employee to travel to/from his place of residence to/from worksite unless authorized as Rest and Recuperation (R&R) associated with OCONUS performance. There will be no reimbursement for local travel in and around the Contractor’s place of performance at TARDEC (within a 50 mile radius). The Government will not pay for any non-mission related travel.

C.3.11.1.2 Fee/profit on travel expenses is not an allowable cost on any WD issued under this contract.

C.3.11.2 A trip report (including dates, time, location of travel, summary of the activities and an Action Item list) is required to be delivered to the COR or A-COR, no later than five business days after completion of each trip (CDRL A016).

C.3.12 Contracting Officer Representative (COR). The COR will monitor all technical aspects of the contract and assist in contract administration. The COR is authorized to perform the following functions:

--Assure the contractor performs the technical requirements of the contract;

--Perform inspections necessary in connection with contract performance;

--Maintain written and oral communications with the contractor concerning technical aspects.

The COR is not authorized to direct any changes to the contract. If the contractor believes an out of scope change has been directed, it is to notify the PCO in writing immediately and not proceed with this work until written authorization is received from the PCO.

C.4. SPECIFIC REQUIREMENTS.

As required by WD, the contractor shall perform engineering activities to develop architectures, system designs, software applications, laboratory tools, systems and subsystems for TARDEC manned and unmanned military ground vehicle programs. The contractor’s efforts will fall within C.4.1 thru C.4.21. The contractor shall implement a System Engineering approach for analyzing, developing, and enhancing TARDEC and PEO/PM Program ongoing programs. The contractor shall investigate, analyze and consider cost variables and affordability issues, and conduct cost, schedule, performance, and technical trade off analyses for each work category defined below.

C.4.1 Technical/Engineering Management.

C.4.1.1 The contractor shall develop and execute engineering and technical management plans detailing the technical and management approach, key project milestones, and decision points to achieve project success. Plans shall be documented in a technical report (CDRL A002).

C.4.1.2 The contractor shall establish and maintain project level Integrated Master Schedules (IMS) and work breakdown structures (WBS).

C.4.1.3 The contractor shall conduct technical and management reviews to establish and control baselines. Reviews include Requirements Reviews, Design Reviews, Test Readiness Reviews, Functional and Physical Configuration Audits, Milestone Reviews, In-Process Management Reviews, and Project Decision Gate Reviews. The contractor shall provide content, information, and recommendations to facilitate key decision points at these reviews. The contractor shall provide presentation materials associated with these reviews as required by the WD (CDRL A006).

C.4.2 Engineering Analyses.

C.4.2.1 The contractor shall perform engineering analyses including market and technology surveys, trade studies, architecture evaluations, technology road-mapping, and cost modeling (CDRL A002).

C.4.2.2 The contractor shall conduct engineering analyses of current and future technologies and RDTE Plans for organizational strategic planning (CDRL A002).

C.4.2.3 The contractor shall develop domain models, operational vignettes, and use cases to analyze systems (CDRL A004).

C.4.3 System Requirements Analysis and Definition.

C.4.3.1 The contractor shall perform system requirements analyses for new systems and new applications of existing systems. Systems requirements analyses include functional, performance, interface, and environmental requirements and shall consider the system users’ requirements and growth capability. (CDRL A002)

C.4.3.2 The contractor shall enter and maintain requirements in Dynamic Object Oriented Requirements System (DOORS).

C.4.4 System Design.

C.4.4.1 The contractor shall generate system designs based on the system’s functional and performance requirements using concurrent engineering practices to include human factors engineering, packaging engineering, security engineering, survivability, safety, producability and software engineering. Human factors engineering shall adhere to human factors guidelines, principles, and practices, contained in MIL-STD-1472G and MIL-STD-48655A. The contractor shall allocate functions to hardware and software through engineering design synthesis. (CDRL A004)

C.4.4.2 The contractor shall investigate existing and future technologies as part of the system engineering process.

C.4.4.3 The contractor shall prepare Level 2 and Level 3 Technical Data Packages (TDPs) IAW CDRL A008 that document detailed designs to include one-wire diagrams, two-wire diagrams, systems architecture diagrams, Bill of Materials (utilizing format as specified in the individual WD) and detailed mechanical and electrical designs.

C.4.5 System Fabrication.

C.4.5.1 The contractor shall provide technical expertise, analyses, conceptual and detail design, design and fabrication of prototypes, demonstrators, advanced concept technology demonstrators and advanced technology demonstrators for manned or unmanned military ground vehicles. (CDRLs A002, A004)

C.4.5.2 The contractor shall develop and produce prototype or demonstrator mechanical, electro-mechanical, electrical, and electronic components for specified military manned or unmanned ground vehicle system and sub-system configurations.

C.4.5.3 The contractor shall assemble prototype or demonstrator mechanical, electro-mechanical, electrical, and electronic components into the specified military manned or unmanned ground vehicle system and sub-system configurations.

C.4.5.4 The contractor shall identify and provide engineering lifecycle activities to support transformational technologies for manned or unmanned military ground vehicles and other platforms.

C.4.5.5 The contractor shall develop technical data for fabricated components, prototypes, and demonstrators (CDRL A004). Technical data includes Level 1, 2 and 3 drawings, Computer Aided Design (CAD) concept models, and 3-D solid model CAD drawings for engineering concept analysis and prototype fabrication.

C.4.6 Software.

C.4.6.1 Software Requirements Definition.

C.4.6.1.1 The contractor shall conduct software requirements analysis for new and modified Computer Software Configuration Items (CSCI) for new and existing systems using Unified Modeling Language (UML) constructs and modeling tools. Analyses may include functional, performance, interface, and environmental requirements. The contractor shall consider the system users’ requirements and system growth capability when assessing potential solutions to system problems, system improvements, or interface problems. The contractor shall use UML constructs and modeling tools as specified in the individual WD to analyze and document the requirement. (CDRLs A002, A007)

C.4.6.1.2 The contractor shall perform formal requirements management including:

(a) Maintaining a software requirements database,

(b) Establishing baselines,

(c) Controlling changes,

(d) Establishing traceability to source requirements, derived requirements, functional allocation, and performing verification and test.

C.4.6.2 Software Architecture.

C.4.6.2.1 The contractor shall conduct analyses on software architectures for new and modified systems containing software (CDRLs A002, A004).

C.4.6.2.2 The contractor shall identify key and latent use cases for the system under development and identify technical aspects being overlooked in the context of efficient architecture design.

C.4.6.2.3 The contractor shall conduct assessments of current application and network architecture as defined by project goals and use cases.

C.4.6.2.4 The contractor shall develop design options and recommend strategies for implementation factoring in identification of risk areas and suggestions for mitigation given the context of the program or system (CDRLs A002, A004).

C.4.6.2.5 The contractor shall analyze and document the architectural patterns and design to be used to meet identified software systems quality factors (CDRLs A002, A004).

C.4.6.3 Software Design.

C.4.6.3.1 The contractor shall generate software designs based on the specified software architecture and functional and performance requirements. The contractor shall ensure software designs consider human factors engineering, packaging engineering, software assurance, and software engineering to meet all the system software requirements. The software architecture designs shall maximize the use of industry standards and open systems architectures and shall emphasize modularity, commonality, adaptability, autonomy, agility, scalability, maintainability and ease of product evolution and new product integration (CDRL A004).

C.4.6.3.2 The contractor shall allocate functions to Computer Software Components (CSC) and units while working within a defined software architecture using a defined engineering process.

C.4.6.3.3 The contractor shall investigate existing and emerging technologies as part of the software engineering process.

C.4.6.4 Software Development.

C.4.6.4.1 The contractor shall develop new or modify existing software code. The contractor shall model, document, and test the developed or modified software code. The software shall be written in compliance with the Government defined software architectures using Government defined languages and coding procedures. When specific language and coding procedures are not specified, the contractor shall use an engineered approach using best practices during software development to include adhering to a defined style guide and using varying levels of unit testing. All software developed or modified under this contract shall be delivered IAW CDRL A007.

C.4.6.4.2 The contractor shall collect and report key software development and quality metrics.

C.4.6.4.3 The contractor shall develop software project management control plans.

C.4.6.4.4 The contractor shall implement management controls as defined in individual WD Software Project Management Plans (SPMP).

C.4.6.4.5 The contractor shall ensure that software development maximizes the use of GFE/M/P/S and other available technology components and software. The contractor shall notify the COR in advance if it proposes to use any software that will restrict Government rights beyond Unlimited Rights. If any existing software, including COTS/GOTS/or contractor owned, will be used on this contract, the contractor shall request, in writing, prior approval from the COR or PCO before said software is used.

C.4.6.5 Software Test.

C.4.6.5.1 The contractor shall conduct software testing for manned or unmanned military ground vehicles and dismounted soldier systems.

C.4.6.5.2 The contractor shall develop test plans, test descriptions, software test code, and test reports. (CDRL A002)

C.4.6.6 Software Process Engineering and Control.

C.4.6.6.1 The contractor shall develop, document, and implement software quality processes and procedures for TARDEC developed software based on industry best practices IAW the Software Engineering Institute (SEI) Capability Maturity Model Integrated (CMMI).

C.4.6.6.2 The contractor shall monitor and track software metrics and recommend improvements to existing software processes.

C.4.6.6.3 The contractor shall maintain and further enhance TARDEC’s current CMMI level processes and process improvement efforts designed to raise TARDEC’s process maturity to higher levels of the CMMI.

C.4.6.7 Lifecycle Software Engineering.

C.4.6.7.1 The contractor shall perform Software technical and engineering management services including:

(a) Economic analysis,

(b) Product lifecycle planning,

(c) Interoperability analysis,

(d) Integrated master scheduling/planning (IMS/IMP) risk management,

(e) Configuration management,

(f) Data management,

(g) Integrated Product Team (IPT) engineering services, and

(h) Material release activities

C.4.7 System and Subsystem Integration.

C.4.7.1 The contractor shall perform hardware/software integration, and subsystem and system integration. The contractor shall assure that all hardware components, software modules, and subsystems within the specified system are communicating and performing in accordance with the system requirements and design.

C.4.8 System Testing.

C.4.8.1 The contractor shall develop test plans, test descriptions, software test code, and test reports for testing of manned and unmanned military ground vehicles and dismounted soldier systems. (CDRL A002)

C.4.8.2 The contractor shall conduct software and hardware testing of manned and unmanned military ground vehicles or dismounted soldier systems. Testing efforts may include software from the Computer Software Unit level, and hardware from the module to Line Replaceable Unit (LRU) level. System level testing shall flow from individual LRUs up to final system configuration.

C.4.9 System Maintenance.

C.4.9.1 The contractor shall provide engineering services to maintain and upgrade existing systems including detecting problems, isolating failures, and implementing corrective actions.

C.4.9.2 The contractor shall perform technology upgrades into existing systems including modifying and debugging hardware and software required to maintain operation of manned or unmanned military ground vehicles and dismounted soldier systems.

C.4.10 Experimentation and Testing.

C.4.10.1 The contractor shall conduct laboratory and field experiments at Government test sites. The contractor shall prepare test plans; prepare test procedures; perform logistical activities; perform shipment and movement of vehicles; perform system operation, system troubleshooting, data acquisition, data reduction and analysis; and prepare experiment reports. All experimentation and testing documentation and results shall be submitted as a technical report IAW CDRL A002.

C.4.10.2 The contractor shall provide diesel, JP-8, and regular gasoline fuels, when required by the WDs, for any vehicles that are used in experiments.

C.4.11 Independent Verification and Validation (IV&V).

C.4.11.1 The contractor shall perform IV&V tasks to include:

(a) Evaluating design processes,

(b) Document reviews,

(c) Software audits and validation of software testing for in-house TARDEC, PEO, and PM programs.

C.4.12 System and Laboratory Tool Enhancement.

C.4.12.1 The contractor shall develop and implement system and laboratory tool enhancements to enhance the fidelity and performance of specified systems and laboratory tools. The contractor shall modify crew station configurations; develop and implement additional emulators and software; develop and implement simulations and models; develop and implement warfighter machine interfaces; and develop and implement software code to provide additional capability and realism to the specified system or tool.

C.4.12.2 The contractor shall provide engineering services to design and improve the TARDEC Labs both from a facility viewpoint and a process viewpoint.

C.4.13 Systems Engineering, Interoperability, and Information Assurance.

C.4.13.1 The contractor shall design, develop, integrate, test, and sustain Command, Control, Communications, Computers, Intelligence, Surveillance, and Reconnaissance (C4ISR) capabilities on ground combat systems.

C.4.13.2 The contractor shall identify and analyze requirements to integrate ground combat systems to the Global Information Grid and meet Net Ready-Key Performance Parameters and Common Operating Environment (COE) compliance.

C.4.13.3 The contractor shall generate, coordinate, and update Information Support Plans (ISPs). The contractor shall coordinate with applicable Government agencies to obtain required products and information for incorporation in ISPs.

C.4.13.4 The contractor shall perform all Risk Management Framework tasks for information systems and platform information systems being developed under the programs supported by this contract.

C.4.13.5 The contractor shall perform security engineering to capture and refine information protection requirements to ensure their integration into information systems acquisition and information systems development.

C.4.13.6 The contractor shall coordinate and facilitate obtaining Army Interoperability Certification for ground combat systems.

C.4.13.7 The contractor shall conduct data modeling of wireless networks to include: throughput, bandwidth, frequency, and range. (CDRL A004)

C.4.14 Product Transfer and Support Transition.

C.4.14.1 The contractor shall provide product support services and develop product artifacts to enable the transition and continued operation of products delivered under this contract. The contractor shall provide the following for the products developed under this contract:

(a) New equipment training (including safety of use),

(b) Installation and assembly,

(c) Field Support Representative,

(d) Software maintenance, troubleshooting

(e) Defect tracking,

(f) Maintenance

(g) Training materials,

(h) Set-up and assembly instructions and diagrams,

(i) Operational and support documents (including maintenance), and

(j) Field support manuals.

C.4.15 Program Management Support Services.

C.4.15.1 The contractor shall provide program management support to include:

(a) Conducting technology investigations,

(b) Preparing and presenting technical papers,

(c) Attending technical information exchange meetings,

(d) Participating in and attending technology demonstrations, program milestone events and trade shows.

(e) Conducting contract level meetings and reviews.

C.4.16 Systems Integration Laboratory (SIL) Support.

C.4.16.1 The contractor shall develop, maintain, and upgrade TARDEC labs and SILs to include developing software applications, simulations laboratory tools, and demonstration systems for TARDEC programs. The contractor shall identify and integrate SIL components into a functional development and test environment suitable for specified verification, validation, and certification activities.

C.4.16.2 The contractor shall provide Information Assurance and Cyber Security support to the various SILS to ensure conformance with DoD Information Assurance requirements in AR25-2.

C.4.17 System Installation.

C.4.17.1 The contractor shall perform installation activities for electronic systems and components on manned or unmanned military ground vehicles and other TARDEC supported systems to include:

(a) Design, development, and fabrication of installation kits including mounting brackets, isolation systems, harnesses and cables;

(b) Modification of manned or unmanned military ground vehicles to accept new equipment;

(c) Component fit checks;

(d) Physical installation of equipment; and

(e) Verification that new equipment operates as intended with the vehicle environment (thermal, shock and vibration).

C.4.18 Field Support.

C.4.18.1 The contractor shall provide Field Service Representatives (FSRs) and Field Service Engineers (FSE) for CONUS and OCONUS field support for manned and unmanned military ground vehicles. FSRs and FSEs shall perform the following activities:

(a) Installation of electrical and electronic equipment and software;

(b) Integration of electrical and electronic equipment and software;

(c) Testing of electrical and electronic equipment and software;

(d) Troubleshooting and fault isolation and reporting of electrical and electronic equipment and software;

(e) Maintenance on electrical and electronic equipment and software;

(f) Component replacement for electrical and electronic equipment and software; and

(g) Shipment and movement of vehicles

C.4.19 New Equipment Training.

C.4.19.1 The contractor shall provide new equipment training for Operator and Field Level Maintenance for manned or unmanned military ground vehicle electrical and electronic equipment and other TARDEC supported systems.

C.4.19.2 The contractor shall conduct training analysis to:

(a) Determine key learning objectives;

(b) Develop training plans (CDRL A002);

(c) Develop programs of instructions and associated training resources (CDRLs A002, A006);

(d) Conduct operational and maintenance training;

(e) Gather feedback on the effectiveness of provided training, and make course adjustments.

C.4.20 Administrative Services.

C.4.20.1 The contractor shall provide the following administrative services:

(a) Meeting coordination by scheduling, contacting meeting attendees, and reserving facilities;

(b) Resource tracking by project location, availability, and schedule;

(c) Travel coordination including making reservations and preparing necessary travel documents, purchase requisitioning and locating sourcing of items to be purchased;

(d) Management by maintaining and tracking the list of automatic data processing inventory;

(e) Facility maintenance coordination including making required maintenance requests and monitoring corrective maintenance actions;

(f) Database maintenance of different databases maintained by the TARDEC areas;

(g) Forms preparation;

(h) Document preparation;

(i) Arranging field test sites; and

(j) Preparing presentation material for TARDEC.

C.4.21 Configuration Management (CM).

C.4.21.1 The contractor shall establish a CM program for configuration identification, control, status accounting, audit, and data management using best practices to implement the technical and program management principles fundamental to CM. (CDRL A012) C.4.21.2 The contractor shall establish production configuration baselines and support associated audits to include: as-designed, as-integrated, as-built, and as-delivered configuration baselines and audits; and physical configuration audits. (CDRLs A013, A014, A015) C.4.21.3 The contractor shall develop and maintain Data Accession Lists and Configuration Status Accounting Information. (CDRLs A014, A015) C.4.21.4 The contractor shall prepare and submit Engineering Change Proposals (ECPs), Value Engineering Change Proposals (VECPs), Variance Requests for Deviation (RFDs), Notice of Revisions (NORs), and Engineering Release Records (ERRs). (CDRLS A009, A010, A011) C.4.21.5 The contractor shall design, develop, manage, and maintain the product data under this contract. Product data consists of product data that is fully defined and sufficient for competitive re-procurement. Product data includes all product data, indentured product-structure (part-relationship / parent to child), associated lists, specifications, standards, product related documents (e.g. engineering bill of material, special tools and materials, and test and calibration requirements), and all approved and implemented engineering changes.

C.4.21.5.1 The contractor shall manage, securely store, release, validate, and track as-designed, as-integrated, as-built, and as-delivered configuration baselines, including management of product structures, product definition documents/data, test and analysis data, GFI, and other related technical data.

C.4.21.6 The contractor shall develop technical data packages to include product design data; form, fit, and function technical data. (CDRL A008)

C.5 Meetings.

C.5.1 Post Award Start of Work Meeting. The contractor shall conduct a Post Award Start of Work meeting within 20 days after contract award at the U.S. Army TACOM LCMC facility in Warren, Michigan. The contractor shall coordinate a mutually acceptable meeting date with the COR within 14 days after contract award. The contractor shall prepare and submit a proposed agenda for the start of work meeting at least three business days before the scheduled meeting date. The contractor shall prepare and distribute meeting minutes (CDRL A005), inclusive of summary of discussion a listing of action items, and list of attendees.

C.5.2 In-Process Reviews. The contractor shall conduct In-Process Reviews (IPR) every three months to review cost, schedule, and performance. The contractor shall schedule the reviews with the COR. The reviews shall be held either at the contractor’s facility, sub-contractor’s facility or at the U.S. Army TACOM LCMC facility in Warren, Michigan. The agenda shall be coordinated in advance of each IPR between the contractor and the COR. The reviews shall include demonstration and delivery of any data results, test results, CAD models, and simulation models completed to date for the individual WD. The contractor shall prepare and submit a proposed agenda for each IPR at least three business days before the scheduled meeting date. The contractor shall prepare and distribute meeting minutes (CDRL A005), inclusive of a summary of discussion, a listing of action items, and list of attendees.

C.5.3 Annual Contract Performance Review by individual WD. The contractor shall conduct a contract performance review every 12 months after contract award to review cost, schedule, and performance of the entire contract. The contractor shall schedule the reviews with the COR. The reviews shall be held either at the contractor’s facility, or at the U.S. Army TACOM LCMC facility in Warren, Michigan. The location and date for the contract performance reviews shall be mutually agreed upon between the contractor and the COR. The contractor shall coordinate the agenda with the COR in advance of each IPR. The reviews shall include demonstration and delivery of any data results, test results, CAD models, and simulation models completed to date (CDRL A002, A004, A006). The contractor shall prepare and submit a proposed agenda for each annual performance review at least five business days before the scheduled meeting date. The contractor shall prepare and distribute meeting minutes (CDRL A005), inclusive of summary of discussions, a listing of action items, and list of attendees.

C.5.4 Contract Weekly Conference Call. The contractor shall participate in weekly conference calls to report on the overall status of the contract and identify any issues by individual WD. The conference calls shall begin one week after contract award and shall be coordinated on a mutually agreeable time and day.

C.5.5 Meetings and Working Groups. The contractor shall facilitate, attend and participate in all meetings and working groups, and provide research and guidance for each working group’s area of responsibility as specified by the individual WD.

C.6 Deliverables.

C.6.1 Contract Performance & Monthly Status Reports. The contractor shall submit a monthly Contract Performance & Monthly Status report IAW CDRL A001 for the duration of the contract.

C.6.2 Technical Reports. The contractor shall submit technical reports IAW CDRL A002 as required by the individual WDs. Technical reports include project plans, analyses results, and test and experimentation documentation resulting from the efforts under C.4-C.4.21.6 above.

C.6.3 TI Final Reports. The contractor shall submit WD Final Reports IAW CDRL A003 when required by the individual WDs.

C.6.4 Technical Data. The contractor shall deliver engineering technical data, product drawings, models, and associated list resulting from the efforts under C.4-C.4.21.6 above IAW CDRL A004 as specified by the WDs.

C.6.5 Meeting Minutes. The contractor shall provide meeting minutes IAW CDRL A005.

C.6.6 Presentation Materials. The contractor shall provide presentation materials IAW CDRL A006.

C.6.7 Software. The contractor shall deliver all deliverable software and software development and support documentation to the Government IAW CDRL A007.

C.6.8 Technical Data Package (TDP). The contractor shall deliver TDPs to the Government IAW CDRL A008.

C.6.9 Engineering Change Proposal (ECP) / Notice of Revision (NOR). The contractor shall deliver ECP/NORs IAW CDRL A009.

C.6.10 Request for Variance (RFV). The contractor shall deliver RFVs IAW CDRL A010.

C.6.11 Engineering Release Record (ERR). The contractor shall deliver ERRs IAW CDRL A011.

C.6.12 Configuration Management Plan (CMP). The contractor shall deliver CMPs IAW CDRL A012.

C.6.13 Configuration Audit Plan (CAP). The contractor shall deliver CAPs IAW CDRL A013.

C.6.14 Configuration Status Accounting Information (CSAI). The contractor shall deliver CSAI IAW CDRL A014.

C.6.15 Configuration Audit Summary Report (CASR). The contractor shall deliver CASRs IAW CDRL A015.

C.6.16 Trip Report. The contractor shall deliver Trip Reports IAW CDRL A016.

C.7 ADDITIONAL REQUIREMENTS AND CONSIDERATIONS

C.7.1 Security. The contractor shall process and protect all classified data IAW the requirements of the DD Form 254, Attachment 0008.

C.7.1.1 The contractor shall refer to Section H.13 of this contract for additional facility and personnel security requirements.

C.7.2 Off-Duty Employment. Contractor personnel, consultants, and subcontractor personnel shall neither employ nor establish a compensatory arrangement with any person who is an employee of the United States Government, either civilian or military, without verifying that the employee has complied with the Joint Ethics Regulation (DoD 5500.7-R) and any appropriate department regulation pertaining to off-duty employment for Government personnel.

C.7.3 Disclosure of Information. There shall be no disclosure or publication of information developed under this contract unless prior written approval has been obtained from the PCO. In order to comply with DFARS 252.204-7000, Disclosure of Information, copies of the information to be released are required at least 45 days prior to the scheduled release date. The locations as to where these copies should be sent to can be found at DFARS 252.204-7000.

C.7.4 Accident Reporting and Responsibilities.

C.7.4.1 Accident investigation and reporting to higher command levels will remain with the U.S. Army at the host installation.

C.7.4.2 The contractor shall report within one hour of an accident to the COR all available facts relating to each instance of damage to Government property and material or injury to contract personnel.

C.7.4.3 The contractor shall immediately secure the accident area and wreckage until released by the accident investigation authority from the host installation. The COR will prepare the notification of release of equipment impacted by the accident or wreckage.

C.7.4.4 If the Government conducts an investigation of the accident, the contractor shall cooperate fully with the Government personnel until the investigation is completed.

C.8 PERFORMANCE STANDARDS

C.8.1 The contractor services requirements are summarized into performance objectives that relate directly to mission essential items. The performance standards in C.8.2 through C.8.10 briefly describe the minimum acceptable levels of services for each requirement which are critical to mission success.

C.8.2 The contractor develops credible designs, studies, analyses, and work products using sound analytical techniques and processes which are delivered on time. Determination of acceptable performance will be based on the submitted deliverables conforming to applicable policy and regulations (section C.2) and Government guidance provided under the applicable WD and require no more than one revision 98% of the time, and the deliverables are submitted on time 95% of the time IAW the submission times in the WDs. Government surveillance will be 100% review of submissions at all meetings and reviews and random sampling of products submitted IAW WDs other than for meetings and reviews.

C.8.3 The contractor prepares high quality, fully documents reports (CDRL A002) for all studies, tests, analyses, and projects for each WD which are accurate, complete, and delivered on time. Determination of acceptable performance will be based on the submitted reports demonstrating the contractor applied applicable policy and regulations (section C.2) and Government guidance provided under the applicable WD and require no more than one revision per report, and the reports are submitted on time 95% of the time IAW the submission times in the WDs. Government surveillance will be random sampling of products submitted IAW CDRL A002 – Technical Reports.

C.8.4 The contractor develops high quality plans, presentation materials, and briefings, as required to support tasks, meetings, and reviews which are accurate, complete, and delivered on time. Determination of acceptable performance will be based on the submitted deliverables requiring no more than one revision per deliverable submission, and deliverables are submitted on time 100% of the time IAW the submission times in the WDs. Government surveillance will be random sampling of technical data deliverables IAW CDRL A004, and random sampling of presentation materials IAW CDRL A006.

C.8.5 The contractor attends and actively participates in all required meetings and reviews. Determination of acceptable performance will be based on the contractor attending 100% of the meetings IAW the WDs; contractor attendees are prompt, prepared, and provide the appropriate subject matter expertise as required by the individual WD 98% of the time; and the method of attendance for meetings is the most effective and cost-efficient choice 100% of the time. Government surveillance will be periodic sampling of attendance at meetings as documented IAW CDRL A005 – Meeting Minutes, and 100% inspection of subject matter expertise and cost effectiveness as documented by CDRL A005 – Meeting Minutes with COR confirmation.

C.8.6 The contractor delivers progress and monthly task status reports (CDRL A001) that are timely accurate and complete. Determination of acceptable performance will be based on each report containing a minimum of 95% of the required data and having a maximum error rate of no more than 5%, and the Government receiving the reports no later than the 25th business day of the month 98% of the time. Government surveillance will be 100% review of CDRL A001 - Status Report & Funds and Man-Hours Expenditure Report submissions by the COR with the COR confirmation.

C.8.7 The contractor manages WD projects to schedules established in each WD to achieve all WD requirements on time. Determination of acceptable performance will be based on the WD projects being on schedule 90% of the time. Government surveillance will be 100% review of CDRL A001 submissions by the COR and COR tracking via WD project meetings.

C.8.8 The contractor accurately prepares and timely delivers trip reports (CDRL A016) for all travel under the contract. Determination of acceptable performance will be based on trip reports being submitted within 5 days of trip completion 98% of the time, each trip report contains all information required by CDRL A016 100% of the time, and the contractor maintains an error-free rate of 95% for each trip report submission. Government surveillance will be 100% inspection of CDRL A016 submission by the COR.

C.8.9 The contractor demonstrates software process compliance. Determination of acceptable performance will be based on the contractor complying with TARDEC CMMI process 100% of the time. Government surveillance will be period sampling through Government sampling inspections and audits.

C.9 GOVERNMENT INCENTIVES/REMEDIES

C.9.1 The contractor shall perform IAW the requirements specified within this PWS. This section C.9 is in addition to any of the rights provided by FAR clause 52.246-4, Inspection of Services, and any other rights and remedies the Government has under statute or common law.

C.9.2 Incentives. The COR performing surveillance will document high quality performance and ensure this record of performance becomes a part of the Contractor Performance Assessment Report (CPAR) for this order.

C.9.3 Remedies. If the Contractor does not perform IAW the PWS requirements stated herein, the following may result as applicable:

(a) A CPAR rating applicable to the level of work performed;

(b) Loss of contract financing;

(c) Withholding of payments until the Government can determine the ramifications of the below-standard performance;

(d) Withhold exercise of remaining options; and/or

(e) Contractor correction at no additional cost to the Government.

UNCLASSIFIED

UNCLASSIFIED