09 06 09 PWS Final.pdf

Performance Work Statement (PWS) For

Systems Technical Support (STS) Contract June 9, 2009

09 June 2009

United States Special Operations Command Program Executive Office – Special Programs 7701 Tampa Point Boulevard MacDill AFB, FL 33621-5323

SECTION C – DESCRIPTION/SPECIFICATIONS/WORK STATEME NT

C.1 General.

C.1.1 Background. The Program Manager (PM), Family of Special Operations Vehicles (FOSOV) is responsible for evaluation of emerging vehicle technologies, testing of candidate commercial and tactical vehicle systems, research, development, engineering, procurement, and sustainment of FOSOV material solutions. PM-FOSOV is responsible for central program management of Special Operations Forces (SOF) Ground Mobility Platforms from cradle to grave. Standard engineering and testing services along with associated test courses, facilities, ranges, and instrumentation must be available to support the PM. This PWS outlines those engineering and testing tasks that the PM requires in order to properly execute the program responsibilities of SOF ground mobility acquisition.

C.1.2 Scope/Objectives. This Performance Work Statement (PWS) defines the Systems Technical Support (STS) the contractor will perform for the SOF Ground Mobility Platform series of vehicles.

C.1.2.1. The contractor shall provide engineering, quality, testing, and related technical support functions for all SOF Ground Mobility platforms which are managed by the Program Manager for Family of Special Operations Vehicles (PM-FOSOV). The SOF Ground Mobility Platform series of vehicles which supported by this STS Contract includes, but is not limited to: the Lightweight Tactical All-Terrain Vehicle (LT-ATV), Light Mobility Vehicle (LMV), Ground Mobility Vehicle (GMV), Mine Resistant Ambush Protection (MRAP) vehicle, and Non-Standard Commercial Vehicle (NSCV). This effort applies to all phases of vehicle life cycles. The contractor shall be required to undertake one or more of the activities specified herein, via approved task orders. The Government may modify and/or cancel task order(s) in whole or in part, and change the relative order of priority assigned to task orders. The contractor shall perform no effort unless authorized by a task order from the Contracting Officer or an appointed Contracting Officer’s Representative and shall furnish the supplies and services necessary to accomplish the efforts required herein. The contractor’s responsibilities shall include maintaining control of subcontractor and/or vendor efforts to ensure Government requirements are met. The types of tasks covered by this effort include but are not limited to those set forth below:

• Government-directed Engineering Change Proposals (ECPs) to include drawing package for spare and repair parts (including all the down parts), refer to sec C.2.10.1.

• Design analysis, design and system engineering, and prototype fabrication, refer to section C.2, and C.2.1 – C.2.7.

• Field failure analysis and corrective action to include fleet retrofit, refer to section C.2.1 and C.2.4.

• Tradeoff analyses/Total Ownership cost Reduction/Risk Management activities. The contractor will make attempts to reduce costs of vehicle(s) systems and in doing so will perform engineering tradeoff analyses (i.e., if a tradeoff should be made for cost vs. performance for a certain part).

Also risk associated with the vehicle and any possible changes to the vehicle will be determined and brought to the attention of the Government.

The contractor will recommend the next step forward which will be reviewed for approval by the Government. Refer to sections C.2.1 and C.2.10.1.3.

• Modeling and Simulation, refer to section C.2.11.

• Testing and Test Support, refer to section C.7.

• Production improvements and/or enhancements, such as diagnostics or horizontal technology insertion. The contractor will take initiative in introducing improved methods of engineering vehicle(s) or incorporating advanced vehicle systems from other Government agencies or from Industry. These enhancements may be used if approved by Government.

Refer to section C.2.

• Configuration Management to include technical documentation maintenance and support, refer to C.2.10.

• System Design Technical Support of Global War on Terror (GWOT) Vehicle enhancements. The contractor will support vehicle modifications being implemented for ever-changing threats faced in GWOT. Refer to section C.2.4.

• Reliability and maintainability support. The contractor will support current vehicle sustainment for vehicles current useful life and also to possibly extend the vehicle’s useful life. Refer to section C.2.

• Engineering and Test Logistics support. The contractor will provide logistics support to the Government’s engineering and test efforts. The Government may need help in acquiring Commercial off-the-shelf (COTS) items and the contractor may assist as necessary. Refer to section C.2.4.

• Value engineering. The contractor will identify and propose changes to the vehicle(s) which will help lower the vehicle’s lifecycle cost by identifying parts that may be substituted for a lower cost part, processes which can be simplified and done at lower cost to the Government, etc.

Refer to sections C.2.1 and C.2.10.1.3.

• Environmental issues. The contractor will test the vehicle(s) to determine how various environmental situations (i.e., Desert, Mountainous terrain, etc.) affect USSOCOM’s vehicles and parts. Possible solutions will be identified to any negative effects. Refer to section C.2.13.

• Human factors engineering/MANPRINT, refer to section C.5.

• Safety, refer to section C.6.

• Component qualification testing. The contractor will perform qualification tests of vehicle components to determine if they meet Government quality specifications and standards. Refer to section C.7.1.

• Mod Kit application. The contractor will help the Government develop Mod Kits which will be installed either at the depot or in the field. Kit will be designed for ease of installation depending on what maintenance level is performing install. Refer to section C.2.4.

• Obsolescence investigation. The contractor will study the vehicle(s) component structure and determine any parts which are obsolete and that should be replaced. This helps SOCOM in keeping vehicle(s) current with other vehicle systems and fulfills goal of commonality across vehicle platforms as much as possible. Refer to section C.2.9.

• Fire support and munitions studies. The contractor will support the Government in performing testing of weapon systems and armor solutions and evaluation of test results. The extent of the support required will be specified in the individual task orders. Refer to section C.7.1.

• Reset/Recapitalization of vehicles. The contractor will support the Government’s efforts in restoring units to a desired level of combat capability commensurate with mission requirements. This support includes design analysis, design and system engineering to help with restoring units. Refer to section C.2.4.

C.1.3 Start of Work Meeting.

The contractor shall host a start of work meeting at its facility, unless some other location is designated in the contract, within 30 days after contract award. The contractor shall at a minimum invite the Contracting Officer's Representative (COR) identified in Section G or in an appointment letter, the Contract Specialist identified on the face page of this document, and the Contracting Officer (KO).

The COR, Contract Specialist, and KO shall be given at least 14 days advance notice of the time, date, and location of the start of work meeting. The preferred method of notification is by email.

C.1.4 Organizational Conflicts of Interest:

To prevent conflicting roles which may bias the contractor’s quotes, judgment or objectivity, and to preclude the contractor from obtaining unfair competitive advantage in concurrent or future acquisitions, the contractor shall be restricted as set forth in subparagraphs below.

The contractor warrants and represents to the best of its knowledge and belief that it does not presently have any organizational conflict of interest which would diminish its capacity to give impartial, technically sound, and objective assistance and advice or would result in a biased work product or might result in an unfair competitive advantage except that which flows from the normal benefit or performance of this contract.

Whenever, in the performance of this contract, the contractor provides recommendations or advice related to the development of specifications, work statements, data or other information for hardware/software items, the contractor will not enter into any contract either as a prime or subcontractor to furnish said items or components thereof during the life of this contract or through the initial production contract whichever is longer.

Whenever, in the performance of this contract, the contractor provides recommendations or advice related to the development of specifications, work statements, data, or other information for hardware/software items, the contractor will not enter into any contract with the item supplier to provide any support, analysis or consulting services. The prohibition will apply during the life of the contract through completion of the final task order.

The contractor may be required to perform technical evaluation of contractor offers and/or products as well as advisory and assistance services relative to the same. In these instances, the contractor will not evaluate or advise the Government concerning its own products or activities. When required to evaluate other contractor offers and/or products or provide advisory and assistance services to the same, the contractor will preserve its objectivity and protect the Government interests. If the contractor performs technical evaluation of contractor proposal and/or products or services or provides advisory services in relation thereto, the contractor shall not be allowed to furnish any supplies or services either as a prime or subcontractor as part of a joint venture. This provision shall be permanent.

During the course of this contract, use of other company's proposal information or proprietary data shall be necessary for contract performance. Access to this proprietary data shall be accomplished either directly from the other company or, if available, from USSOCOM. The contractor shall enter into a written agreement with each of said other companies in which the contractor;

* obtains the permission to use the other companies\quote proprietary data, whether obtained directly from the other company or from USSOCOM, in the performance of this contract;

* agrees to protect the proprietary data from unauthorized use or disclosure for as long as it remains proprietary; and,

* agrees to refrain from using the proprietary data for any purpose other than in the performance of this contract.

The contractor further agrees:

* to adopt operating procedures and physical security measures designed to protect the proprietary data from disclosure or release to authorized third parties;

* to indemnify the Government, its agents and employees from all liability arising out of, or in any way related to, the misuse or unauthorized disclosure by the contractor, its employees or agents of any proprietary data it received;

* to hold the Government, its agents and employees, harmless against any claim or liability, including attorney fees, costs and expenses, arising out of the misuse of unauthorized disclosure of any proprietary data supplied to the contractor;

* to provide a copy of their agreements with the other companies to the Contracting Officer prior to obtaining access to the proprietary data; and,

* to provide, on request from the Contracting Officer, evidence of the steps taken to protect against unauthorized use or disclosure of the proprietary data.

Whenever a contractor must obtain proprietary technical data or computer software (including limited rights or government purpose license rights technical data and restricted rights computer software) from the Government to perform under a task order under this contract, the contractor will be required to furnish a copy of its proprietary technical data or computer software exchange agreement with the owner of the data as a necessary condition to receiving said proprietary technical data or computer software from the Government.

If the Contracting Officer finds that said written agreement or procedures taken are not adequate, the Government has the right to withhold access to the proprietary data. Additionally, if the Contracting Officer finds that a contractor employee, agent, or subcontractor made unauthorized use or disclosure of any of said proprietary data, the Government has the right to bar that employee, agent, or subcontractor from having further access to said proprietary data at no liability to the Government.

The provisions of this clause are fully applicable to all subcontractors utilized by the contractor and that this clause shall be included in all subcontracts the contractor enters into to support, either directly or indirectly, this contract.

No form of business insulation quote technique to avoid, evade or substitute for the restrictions set out herein shall be permitted except in the absolute discretion of the Government the exercise of which shall not be subject to the Disputes Clause.

In the event the contractor breaches or violates any of the warranties, convenience, restrictions, disclosures or nondisclosure under this provision, the Government may terminate this contract for default and pursue any other remedies as provided by law.

Additionally, it is agreed that the prohibitions contained herein against competing for or performing as a prime contractor, subcontractor or as a consultant to a prime or subcontractor to provide services, hardware or software, shall apply to all programs managed or overseen by USSOCOM or its subordinate elements with respect to which services may be ordered under this contract. The USSOCOM wide exclusion shall cease upon expiration of the final ordering period of this contract.

The Head of the Contracting Activity may at his/her sole discretion, grant individual waivers to the USSOCOM-wide exclusion on a case-by-case basis.

Such waivers shall be binding. However, the contractor shall have no right to such waivers, and the failure to grant a waiver shall not be grounds for protest against any solicitation or acquisition as to which the waiver was denied, nor shall the refusal to grant a waiver be subject to appeal under the Disputes Clause of this contract.

During the course of this contract there is a potential for changes in relationships that may occur and accordingly, the contractor agrees to adjust and take any and all measures deemed necessary to comply with this clause and FAR 9.5. The contractor agrees to immediately notify the Contracting Officer of changes in relationships and a description of the action the contractor has taken or proposes to take to avoid, eliminate or neutralize the conflicts of interest.

C.1.5 Government Furnished Information (GFI)/Government Furnished Equipment (GFE). GFI/GFE to be provided to the contractor for use under this contract will be specified per each task order.

C.1.6 Reports and Data.

C.1.6.1. The contractor shall prepare technical data in the format and scope specified in the applicable Data Item Descriptions (DIDs) (DD Form 1664) included in (MIL-DTL-31000C). This information shall be furnished in accordance with the requirements, quantities, and schedules set forth in the Contract Data Requirements List (CDRL) (DD Form 1423) and as specified in individual task orders. Data shall be submitted in an electronic format compatible with Microsoft programs (such as Word, Access, Excel, Power Point, etc.) unless otherwise specified in the PWS, CDRL, or task order. All data deliverables required under this contract that are updates to previously existing documents shall have change bars in the margin where revisions or updates were made by the contractor.

C.1.6.2. Digital documents of standard DIDs called for under this contract can be ordered by going to the Acquisition Streamlining and Standardization Information System (ASSIST) at http://assist.daps.dla.mil/online/start/.

C.1.6.3. Although a DID for this effort may make reference to a military standard or specification, that standard or specification is to be used by the contractor for guidance only, unless otherwise stated. The only exception shall be for military specifications and standards specifically called out as required within this PWS or in the task orders, and then only to the extent described.

C.1.7 Meetings. (LOE)

C.1.7.1.The contractor shall conduct informal project status meetings with the Contracting Officer Technical Representative (COTR) and Functional Technical Representatives (FTRs) on a monthly basis unless otherwise directed by the COTR. Meetings shall be conducted by teleconference, Video Teleconference (VTC), at the contractor’s facility, subcontractor/vendor facility or any Government facility when requested. The purpose of the meetings shall be to review status and progress of all projects under task orders for this contract. At a minimum, the contractor shall identify project numbers and titles, start of work date for each project, original and current scheduled completion date, rationale for change in project completion date, and contractor's efforts during reporting period. Meeting location, time and attendance shall be coordinated with the COTR. The contractor shall attend, take part in, prepare written or visual presentations for briefings or review meetings and prepare minutes IAW CDRL A016, DIADMN-81505 unless otherwise directed by the COTR. An agenda shall be prepared by the contractor IAW CDRL A010, DI-ADMN-81249A and coordinated between Government personnel and the contractor prior to meetings and reviews unless otherwise directed by the COTR.

C.1.7.2. The contractor shall provide support (to include contractor participation, supporting documentation) to PM-FOSOV for selected Government briefings and presentations, Start of Work meetings, Preliminary Design Reviews, and Critical Design Reviews in accordance with task order. The contractor shall attend, take part in, prepare written or visual presentations for briefings or review meetings and prepare minutes IAW CDRL A016, DIADMN-81505 unless otherwise directed by the COTR. An agenda shall be prepared by the contractor IAW CDRL A010, DI-ADMN-81249A and coordinated between Government personnel and the contractor prior to meetings and reviews unless otherwise directed by the

COTR.

C.1.8 Financial Reports. The contractor shall submit monthly Performance and Cost Reports in accordance with CDRL A001, DI-FNCL 80912, providing the status of hours and funds allocated and expended for each task order.

C.1.9 Task Orders. All work conducted under the STS effort shall be performed only as directed by the task orders issued and approved by the Contracting Officer.

C.2 System Engineering/Technical Effort Description.

The contractor shall provide satisfactory solutions to design problems, design improvement investigations, and field problems. Satisfactory solutions are those which maintain compatibility of all physical, functional, and technical interfaces with the established system design and definition. This shall be accomplished without degradation to the established system design as defined in all FOSOV ICDs, CDDs and CPDs unless otherwise approved by the Government. The contractor shall integrate scientific and engineering investigations/studies to ensure compatibility of all physical, functional, and technical program interfaces with the established design and definition. Unless otherwise stated, reports, studies, engineering and logistic analyses, etc., shall be prepared in the contractor's format in accordance with CDRL A002, DI-MISC-80508B.

C.2.1. The contractor shall conduct failure and structural (stress, finite element, dynamic, etc) analysis to identify root cause for failure of vehicles, parts, components and assemblies identified by the Government. The contractor shall conduct studies to correct known or potential deficiencies, to recommend product improvements and cost reductions. Such studies may be required with respect to proposals for engineering changes and attendant processes and methods. All efforts shall consider logistics and any impact to maintainability or supportability.

In performance of these efforts, the contractor may be required to contact or coordinate with current manufacturers and major vendors in order to resolve issues, ensure continued producibility, etc. Issues affecting these other companies must be considered and related risks weighed under the performance of this contract.

C.2.2. The contractor shall prepare cost estimates, technical reports, calculations, layouts, drawings and computer-aided design (CAD) models, sketches, schematics charts, and other visual depictions (including photographs and videos documenting test results or vehicle or component conditions), purchase descriptions, and recommend Engineering Change Proposals (ECPs) for current and future production versions of the contract item and modifications thereof.

C.2.3. The contractor shall prepare and submit technical reports identifying the results of investigations, studies or evaluations. Include recommendations for future course(s) of action as well as the supporting rationale and documentation.

The supporting documentation shall include the items identified in paragraph C.2.2 to the extent necessary to support all conclusions made in the report.

When the report recommends an ECP, the report shall also address the potential impact on Integrated Logistics Support (ILS) (initial or follow-on provisioning, technical manuals, U.S. Army Test, Measurement, and Diagnostic Equipment (TMDE) Activity, tools, training, etc.) as well as any anticipated cost and weight effects associated with the change.

C.2.4. The contractor shall fabricate and conduct trial installations of component part(s), modification thereof, and/or testing related to processes and methods that are required to evaluate the part (form, fit and function). The contractor shall provide parts, materials, and supplies required to support and conduct engineering and logistic evaluations, maintenance, rebuild, and restoration of the contract item or modification thereof for items undergoing such tests. To meet emergency requirements, the COTR may direct the contractor to ship such parts by the most expeditious means available to specified destinations.

C.2.5. The Contractor shall modify existing engineering and test versions of the FOSOV variants and fabricate subsystems, components, prototypes and mock-ups for future FOSOV versions.

C.2.6. The contractor shall perform various methods of conceptual design of drawings and models; such as rapid prototyping, build physical models based upon computer models, conduct form, fit and function analysis, and use physical models and physical testing to validate computer models and simulation parameters in accordance with CDRL A013, DI-SESS-81001C.

C.2.7. The contractor shall provide, as specified by a signed task order, on-call and on-site engineering support necessary to technically conduct or support systems analysis, engineering, tests and evaluation, simulation, manufacturing (pre- through post-production) integration, technical meetings, and design or field review of part, assembly, end item identified with deficient or defective items.

This includes technical expertise to fulfill systems operation and maintenance, safety, human factors engineering, product assurance, manufacturing science and technology (MS&T), and value engineering requirements.

C.2.8. (LOE) The contractor shall maintain GFE vehicles and items in their possession; perform necessary repairs and maintenance to keep items in a serviceable condition suitable for intended efforts under this contract.

C.2.9 Parts Standardization Plan.

C.2.9.1. The contractor shall select parts and conduct a parts management program, in accordance with the contractor's standard procedures, which ensures the equipment (or system) meets the specification performance requirements with the greatest Improved Operational Effectiveness (described as function of performance, reliability, availability, and life cycle costs).

C.2.9.2. (LOE) The contractor shall prepare a Parts Management Plan, detailing the documented internal procedures. The Plan shall be submitted in accordance with CDRL A004, DI-SDMP-81748, which lists the minimum coverage necessary for a contractor's Parts Management Plan. The Plan shall include provisions for Government (PM-FOSOV) approval or disapproval for final disposition.

C.2.9.3. (LOE) The contractor may request parts selection and application advice from the Acquisition Activity or the Military Parts Control Advisory Group

(MPCAG).

C.2.10 Configuration Management (LOE). The contractor shall maintain the PM- FOSOV Technical Drawing Packages (TDP) that are developed under this contract; keeping them current, legible, and available for intended uses. These intended uses include: follow-on vehicle production, spare parts procurements, vehicle modification, system design, maintenance and integration. The contractor shall maintain a record of past and ongoing engineering changes and drawing revisions.

C.2.10.1 Engineering Change Proposals (ECPs). The contractor shall be capable of submitting ECP data electronically. All ECP submittals shall be delivered as electronic data and be submitted within time period specified by the Government in each request for task order. MIL-HDBK-61A and Electronic Industries Association EIA-649 may be used for additional guidance. The contractor is responsible for insuring that ECP files are correctly tagged and digital 2D and 3D CAD and graphic image files are properly represented prior to delivering the electronic ECP package to the Government. The Government reserves the right to reject electronic ECP files containing errors.

C.2.10.1.1. The contractor shall prepare all Class I and Class II ECPs in accordance with CDRL A005, DI-CMAN-80639C. Proposed changes to specifications and engineering documents will be described using Notices of Revision (NORs) prepared in accordance with CDRL A006, DI-CMAN-80642C and the Data Delivery Description (DDD) for NORs. See section 6.2 and 6.4 of MIL-HDBK-61A for additional guidance on Class I and II ECPs.

C.2.10.1.2. All Class I ECPs will detail how proposed changes affect transportability, safety, technical manuals, packaging, integrated logistics support, or MANPRINT. All related documentation changes required to support these subject items shall be included as part of the ECP in accordance with

CDRL A005, DI-CMAN-80639C.

C.2.10.1.3 Value Engineering Change Proposals (VECPs). The contractor shall prepare VECPs in the same manner as Class I ECPs.

C.2.10.1.4 ECP Numbers (LOE). The contractor shall request ECP numbers via e-mail to the Configuration Data Manager (CDM) representative or as otherwise directed by the Government. The contractor shall utilize these numbers on an individual basis as a control identifier for ECPs and related Engineering Release Records (ERRs). Once an ECP number is assigned to the first submission of a change proposal, that number shall be retained for all subsequent submissions of that change proposal. The contractor shall maintain records of where and when each ECP number was used.

C.2.10.1.5 ECP Co-User Requirements.

a. When the contractor prepares a Class I ECP that affects two or more configuration items or systems for which the contractor is custodian of the data, the contractor shall provide a complete reproducible ECP package to each of the Governments co-user(s) CDM representative requesting comments on the change. Additionally, when the contractor is not the custodian of the data proposed for change, the contractor shall provide an ECP package to both the custodian contractor and Government co-user(s) CDM representative(s), requesting comments and approval of the change. The contractor must coordinate with the custodian and co-user(s) (both Government and contractor) before submitting the ECP package for formal review to the PM-FOSOV Configuration Control Board (CCB). When all comments have been received, the contractor shall submit the ECP package, including all solicited comments, for processing. The contractor shall include documentation in the ECP package indicating which item(s) are co-used, who is custodian of the co-used data, and include applicable co-user points of contact. The Government will notify the prime contractor(s) when the disposition of the ECP has been made and, if approved, the custodian(s) will be directed to incorporate the change and prepare an Engineering Release Record (ERR). Following the preparation of the ERR, the custodian of data under this contract shall send the ERR and the revised data to Special Operations Forces Support Activity (SOFSA), headquartered at Bluegrass Station in Lexington, Kentucky, for review and approval by the PM-FOSOV CDM. Upon ERR approval, the CDM will release the revised documents to the applicable co user(s).

b. ECP Review by Custodial Contractor. When a second party or co-user of vehicle data proposes an engineering change, the contractor shall prepare a response to the proposed change and submit it for PM-FOSOV review, along with a copy of the initiator's ECP, to the CDM representative for PM-FOSOV, within 20 days of receipt or as specified by the COTR in a specific task order.

The CDM representative will staff the proposed change to the PM-FOSOV CCB Chair and additional CCB members as necessary. The custodial contractor shall return the Government and custodian-coordinated ECP package to the ECP originator for further disposition. If PM-FOSOV agrees to accept the ECP for formal review, the ECP originator (second party, co-user, etc.) will resubmit the complete ECP package, including all solicited comments, to PM-FOSOV, for formal evaluation by the vehicle CCB.

C.2.10.1.6 ECP Spare and Repair Parts Data. The contractor shall include an ECP Spare and Repair Parts Data Statement as part of the electronic ECP package in accordance with CDRL A005, DI-CMAN 80639C when interchangeability is affected and or when there is a substitution of parts.

C.2.10.1.7 ECP Enclosure List. The contractor shall identify and list all documents contained in the ECP package and submit as part of the ECP in accordance with CDRL A005, DI-CMAN-80639C. In addition, the contractor shall identify all end items affected and: 1) identify what specific elements will be affected, 2) what other ECPs are pending against the documents listed, and 3) what NSN, if any, will be impacted by any part number change reference in the

ECP.

C.2.10.2 Engineering Release Record Preparation (ERR): All ERR submittals shall be delivered as electronic data to SOFSA in accordance with CDRL A007, DI-CMAN-80463C.

C.2.10.2.1 Engineering Release Record Preparation (ERR): The contractor shall prepare an Engineering Release Record (ERR) for each approved ECP, initial or direct release of a configuration item (CI) and Technical Data Package (TDP) in accordance with CDRL A007, DI-CMAN-80463C. ERR documentation shall include:

a. ERR number

b. Date

c. Sheet number of total sheets

d. Baseline established or changed

e. Type of release (initial or change)

f. ECP Number and ECP approval date

g. Functional Assembly and Nomenclature

h. System or Configuration item nomenclature (all end item affected by model number)

i. Remarks or Miscellaneous Information

j. Drawing Data Information:

1. CAGE code

2. Doc Type

3. Drawing size and Drawing number

4. Sheet of sheets

5. Revision letter

6. Revision date

7. Release (Initial or New Application) or Change (Change or Chg Application)

8. Distribution (as applicable)

k. Name and address of submitting office

l. Government approval block

C.2.10.2.2. Contractor format is acceptable for preparing this ERR. The following are additional instructions that the contractor shall comply with:

a. ERR Package Content - The ERR Package submitted by the contractor shall consist of one (1) ERR for each approved ECP. Electronic drawings, models and documents prepared in accordance with the requirements of this contract shall accompany the ERR that is submitted to the Government. Multiple ECP releases under one ERR will not be allowed unless specifically approved by the Government.

b. When there are multiple vehicles or end item applications, additional ERR sheets will be used for clarification of end-item applicability.

c. Supplemental ERRs, incremental ERRs may only be used for the initial release of major item vehicles or components.

d. ERR Package Submittal - The contractor shall submit ERR packages within 90 days of ECP approval to PM-FOSOV and SOFSA in accordance with CDRL A007, DI-CMAN-80463C. The contractor shall notify the Government CDM representative by e-mail when conditions exist that prevent the contractor from creating or submitting ERRs. The contractor shall electronically submit a separate letter of transmittal to the CDM representative indicating the ERR package has been submitted to the workflow and include a list of enclosures for each ERR.

C.2.10.3 Configuration Status Accounting Information.(LOE) In accordance with CDRL A008, DI-CMAN-81253A, the contractor shall submit the following:

C.2.10.3.1. (LOE) A Configuration Status Accounting Report (CSAR) for changes affecting FOSOV which provides a detail description of DWOs, PPEPs, ECPs and ERRs in process, completed, and canceled. Contractor format is acceptable.

C.2.10.3.2 (LOE) An ERR Report which shall include ERRs submitted & awaiting Government approval; ERRs awaiting submittal pending new drawing approval;

and ECPs and ERRs awaiting Government action on affected product data.

C.2.10.3.3. (LOE) A Master Source Data Report on the Master Data set for the FOSOV. This report shall list engineering drawings, models, and associated lists, associated documents, schematics, installations, diagrams, instructions, software configurations, UID, decals, labels, warnings, critical safety items, kits, armor, manufacturing and process specifications, and other data comprising the FOSOV TDPs. This report shall include the following information:

a. Part (Drawing, 2D-3D Model) and Document Number

b. Current Released Revision and ERR Number

c. Data Type [Part (CSI, Source Control, Vendor Item, Kit, etc.), installation, specification, instruction, schematic, diagram, quality data, packaging data, etc.]

d. Product Baseline (PBL) ERR # & date

e. Source or Master (Linen, Mylar, Word, Excel, 2D AutoCAD, 3D Solid UG- NX, etc.)

f. Data Restrictions (U=Unlimited Rights, G=Government Purpose Rights, L=Limited Rights, SL=Special License Rights, R=Restricted Rights, SN=specifically Negotiated License Rights)

g. Distribution Statement

h. Export Controlled (Yes/No)

i. Applicable End Item Models

j. CAGE

k. DWOs, Open PPEPs & ECPs

l. Data Format(s) Delivered to Government (Latest Revision)

m. Nomenclature

n. Status (Active, Obsolete, Superseded by.., unreleased, etc.)

o. UID item

C.2.10.3.4. (LOE) A FOSOV Drawing Master Matrix List, updated with changes resulting from released ERRs.

C.2.11 Engineering Drawings, Models, Associated Lists and Records.

C.2.11.1 (LOE) The contractor shall prepare and maintain engineering drawings and models, specifications and other technical data comprising the configuration baseline for the Government approved vehicle systems under this Contract in accordance with CDRL A003, DI-SESS-81000C. The Government has unlimited rights to all technical data developed or generated under this contract. The contractor shall securely archive all delivered source digital data in the contractor’s computer software application and provide the COTR with an updated copy when requested.

C.2.11.2 General. Product drawings and models shall provide the necessary design, engineering, manufacturing, and quality assurance requirements information necessary to enable the procurement or manufacture of an interchangeable item that duplicates the physical and performance characteristics of the original product, without additional design engineering effort or recourse to the original design activity. Product drawings and models shall reflect the level of design maturity that the item has attained at the appropriate configuration item lifecycle phase.

C.2.11.3. The contractor shall possess computer aided design (CAD) capabilities to produce drawings and models. The CAD program shall be capable of Modeling and Simulation (M&S) operations. The M&S program will be used for creating three-dimensional models and performing simulations to predict performance and reliability on the vehicle and its subsystems. The contractor will also be able to provide failure analysis through M&S, which will be compared with any associated physical testing. The contractor shall recommend corrective actions when necessary.

C.2.11.4 Product Data (Design Engineering Drawings, Models and Associated Lists).

C.2.11.4.1. Product data for new (initial or direct release) configuration items and/or revised through ECP for modification of the affected system or equipment items shall be developed and delivered IAW CDRL A003, DI-SESS-81000C, (MIL-DTL-31000C; Technical Data Package), TDP Option Worksheets, and Tailoring Checklist.

C.2.11.4.2.The product data shall be in native and neutral computer aided design (CAD) formats using Digital Product Definition Data Sets and Model Based Definition (MBD) Practices IAW American Society of Mechanical Engineers ASME Y14.100, ASME Y14.41 and ISO 10303 STEP AP 214 (part, assembly models, File, and product (PDM Schema) structure). The contractor shall construct encapsulated product data sets that include part and assembly drawings, models, associated lists, material and process specifications; and identify, by reference or entity, installation drawings, special tools and materials, and specify installation test and calibration requirements.

C.2.11.4.3. (LOE) The contractor shall provide and update (in revision cycle) a geometry and CAD creation standard for 2D Drawings, and 2D and 3D CAD models for the Government to determine contractor’s application and disclosure of product data definition set elements in use of delivered product data sets.

Refer to paragraph C.2.11.4.1, Product Solid Models TDP Option Worksheet, Block 5, for delivery.

C.2.11.4.4. The contractor shall not prepare drawings for standard military components or for items for which Government released drawings exist, unless directed by a signed task order.

C.2.11.5 Source Control and Vendor Item Control Drawings.

C.2.11.5.1. The contractor shall prepare (IAW ASME Y14.24) Source Control and Vendor Item Control Drawings only upon receipt of a signed task order. Source Control and Vendor Item Control Drawings shall have listed two (2) or more sources of supply. Requests for Government authorization shall be accomplished by contractor’s written justification to the COTR delineating the need for source control and vendor item control drawings in the use of commercial or vendor-developed configuration items for Government procured systems.

C.2.11.5.2. In conjunction with delivery of source control and vendor item control drawings for commercial or vendor developed configuration items, the contractor shall deliver associated part and assembly native 3D CAD explicit (non-parametric) shrink-wrap solid models complete with sufficient envelope, mounting and mating dimensions, applicable interface characteristics, accurate weight and center of gravity for part items, and approximate weight and center of gravity for assembly configuration items, and part-to assembly hierarchical CAD product structure schema and user-defined metadata attributes.

C.2.11.6 Acceptance of Product Data (Engineering Drawings, Models, and Associated Lists).

C.2.11.6.1. Prior to initial or direct release of 2D digital and CAD product drawings and associated lists due to ECP approval; the assigned vehicle system

Government Design Engineer must sign off to authenticate newly generated or revised product drawings in the Design Engineer's Approval Block, ASME Y14.1 (Block G) prior to ERR release. In addition to Engineers Approval Block G entry, the contractor shall permanently record the Government approval name and organization user-defined metadata attributes in the contractor’s PDM system, engineering release system, and CAD source software system.

C.2.11.6.2. Prior to initial or direct release of newly generated or revised 3D solid model product data; the contractor must obtain the Government Design Engineer technical acceptance. The contractor shall permanently record the Government approval name and organization user-defined metadata attributes in part and assembly 3D CAD model files, contractor’s PDM system, engineering release system, and CAD source software system.

C.2.12 Data Management.

C.2.12.1 Drawing Number Assignment (LOE): The contractor, when required, shall assign Government-issued Army Ordnance Part Numbers (AOPNs) to all product drawings, models, and associated documents, including package content and kit drawings produced and released under this contract. The contractor shall request additional blocks of numbers on an as needed basis via e-mail to the CDM representative.

C.2.12.2 Drawing Part Numbers for Privately Developed Items: The contractor is prohibited from assigning drawing and part numbers to privately developed items prior to Government approval. If an item is approved for incorporation into the design, the contractor shall assign an AOPN and/or a National Stock Number (NSN) to the item in accordance with C.2.12.1.

C.2.12.3 Product Data Drawings, Models, MBD datasets, and Documents Custodianship (LOE): The contractor is responsible for all original data in its possession. As custodian, the contractor shall make changes authorized by Contracting Officer Technical Representative (COTR) to the original data, and provide CDM representative with compliant data as part of the ERR package in accordance with the ERR requirements of this contract. The contractor shall distribute additional copies of changed data to co-users and other recipients as described in the PWS & CDRLs. Upon request, the contractor shall provide copies of data to the PM-FOSOV CDM, CM, or Engineering Technician, within 7 calendar days of request. The contractor shall not transfer any Government data to vendors or subcontractors without written approval from the COTR.

C.2.12.4 Procedures for Transferring Product Data Documents, Drawings, Models, and Associated Lists (LOE): The contractor shall transfer master data not already in the Government’s possession from completed task orders to the CDM Representative by the end of contract performance period in accordance with CDRL A008, DI-CMAN 81253A. The contractor shall transfer these source

2D non-digital and digital, native, and neutral 3D CAD solid models, and other software generated master files as attachments to a closeout ERR or Change Notice object. Paper, Mylar, or other hard copy drawings and documents shall be packaged and shipped (by mail or courier) in separate containers, using the following categories:

a. Obsolete and superseded drawings and documents

b. A & B size drawings (laying flat)

c. C & D size drawings (laying flat)

d. E through K size drawings (rolled)

e. Quality Assurance Provisions (QAPs) and Final Inspection Records (FIRs)

f. PDs

C.2.13 Environmental Management. During design modifications and ECP submissions, the contractor shall identify alternatives to hazardous substances and environmentally unfriendly materials such as mercury, cadmium (electroplating), and hexavalent chromium (coating and electroplating). In addition, Class I & II Ozone depleting substances, asbestos, and radioactive materials are prohibited for use on the PM-FOSOV. The contractor shall certify that all activities under this contract are in compliance with applicable federal, state, and local environmental laws.

C.2.14 Transportability Engineering. The contractor, when required, shall prepare a Transportability Report in accordance with CDRL A009, DI-PACK- 80880C for modifications affecting the system's overall weight, dimensions, center of gravity, or transportability capability requirements. The contractor shall perform transportability testing for design modifications affecting vehicle transportability.

C.3 CRITICAL SAFETY ITEMS (CSI).

C.3.1. The contractor shall identify Critical Safety Items (CSIs) within the Technical Data Package (TDP).

C.3.2. The following definitions apply:

C.3.2.1 Critical Safety Item. A part, assembly, installation, or production system with one or more critical characteristics that, if not conforming to the design data or quality requirements, would result in an unsafe condition. Unsafe conditions include conditions which would cause loss or serious damage to the end item or major components, loss of control, or serious injury to personnel.

C.3.2.2 Critical Safety Characteristics. Any feature (i.e., tolerance, finish, material composition, manufacturing, assembly or inspection process) of product, material, or process, which if nonconforming or missing would cause the failure or malfunction of the critical item.

C.3.3. Each CSI and assembly process shall be clearly identified as such on the part drawing and assembly drawing and in all associated Quality Assurance documentation (i.e., Quality Assurance Requirements and Quality Assurance Provisions (QAR/QAP)). The critical safety characteristic(s) for each CSI shall also be clearly identified as such on the engineering part and assembly drawing, and in all QARs and QAPs. Critical safety characteristics will require 100% inspection per the QAR or QAP. The specific method for marking drawings shall be as delineated in ASME Y14.100 Engineering Drawing Practices.

C.3.4. Identification of CSIs shall be including, but not limited to, the following data sources:

C.3.4.1 Sound engineering analysis and judgment.

C.3.4.2 Failure modes and effects, criticality analysis SAE ARP 5580.

C.3.4.3 Safety assessment and safety hazard analysis (MIL-STD-882D).

C.3.4.4 Development testing and operational testing results.

C.3.4.5 RAM engineering assessments.

C.3.4.6 Previous experience using like items or designs.

C.3.4.7 Logistics Management Information data.

C.3.4.8 Component qualification test results.

C.3.5. The requirements pertaining to CSIs must be validated to ensure that all critical safety aspects of the design are accurately reflected, parts and materials operate well below fatigue limits and stress levels, and the design allows for assessment by inspection and nondestructive inspection equipment. Validation must be based on engineering analysis of the critical safety item characteristics and should consider changes and deterioration through time or use, fatigue life, and operating conditions.

C.3.6. (LOE) Contractor shall generate a CSI list and be maintained and updated throughout the life of the contract. The CSIs shall also be referenced on the vehicle class and division drawing. This list shall be dynamic in nature with changes taking place as experience and knowledge is obtained and design changes incorporated. Reports shall be developed in accordance with CDRL A011, DI-SAFT-80970A. The Government shall be permitted access to the contractor's backup documentation whenever requested.

C.3.7. Components having a requirement for nuclear hardening must be included as part of the CSI effort and must be incorporated in the CSI list. The nuclear hardening requirement shall be highlighted as a critical safety characteristic in the TDP.

C.4 QUALITY ASSURANCE REQUIREMENTS.

C.4.1. The contractor shall implement and adhere to a quality assurance system acceptable to the Government (i.e., QS, ISO 9000, or any other industry-recognized and accepted quality model). The contractor's quality system shall ensure product quality throughout all contract requirements, to include management, design, fabrication, testing, processing, shipping, storage, site installation, etc.

C.4.2. The contractor shall utilize the C.4.1 quality system for inspection, validation, control, and inspection results of engineering drawings and Quality Assurance Technical Documentation (QATD) changes. This system shall also provide a means for incorporating data received from Test Incident Reports (TIRs) and Quality Deficiency Reports (QDRs). The contractor shall ensure that all drawings and documentation submitted within the Technical Data Package (TDP) are coordinated with all appropriate department elements within their organization and are adequate for the manufacture and acceptance of quality material and for competitive procurement. The contractor shall ensure that data resulting from engineering efforts and any deficiency reports which may affect the adequacy and accuracy of the QATD being developed and maintained under the contract, are coordinated with its product assurance office and included in all engineering drawing packages and QATD packages submitted for Government review.

C.4.3 Quality Engineering.

C.4.3.1. (LOE) The contractor shall perform Quality Engineering Reviews to audit and assess the quality of its quality control system. The contractor shall perform quality engineering reviews of all TDP documentation affected by a task order and recommend the amount and type of inspection and test controls required to achieve the requisite quality of the contract item throughout all production and operational phases.

C.4.3.2. Studies shall be undertaken at a point in time which will assure that the resulting recommended inspection controls are processed as part of any proposed Engineering Change Proposal (ECP).

C.4.3.3. The contractor shall ensure that all sketches, contract part drawings, and ordnance type drawings are provided in accordance…