M67854-15-R-5007_A0001.pdf

M67854-15-R-5007

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83)

Prescribed by GSA

FAR (48 CFR) 53.243

The purpose of this Amendment is to:

(1) Change the NAICS code from 355311 to 541712;

(2) Update the Statement of Work (See Bold and Highlights);

(3) Update Inspection and Acceptance

(4) Update the Delivery Schedule (See Bold and Highlights);

(5) Add FAR clause 52.225-1;

(6) Update Performance Specification (See Bold and Highlights);

(7) Update Clauses in Section K; and

(5) Address questions from industry.

All other terms and conditions remain unchanged and in full force and effect.

1. CONTRACT ID CODE PAGE OF PAGES

J 1 84

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 29-Sep-2015

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X M67854-15-R-5007

X 9B. DATED (SEE ITEM 11)

28-Aug-2015

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, X is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE

RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

24-Sep-2015

CODE

MARCORSYSCOM - PG15

ATTN: EBONY GUEST

2200 LESTER ST.

QUANTICO VA 22134

M67854 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION B - SUPPLIES OR SERVICES AND PRICES

Global Changes

CLIN 0001 -- SUBCLIN 0003AV

The NAICS code has changed from 335311 to 541712.

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

STATEMENT OF WORK

Statement of Work

Mobile Electric Hybrid Power

Sources (MEHPS)

Prepared by

Product Manager - Expeditionary Power Systems

Marine Corps Systems Command

1.0 SCOPE

The USMC has identified a future need for Mobile Electric Hybrid Power Sources (MEHPS). This Statement of

Work (SOW) defines the effort required to develop this capability for transition to production (separate contract)`.

The desired attributes for this capability are defined in the associated Performance Specification (PSpec).

The contractor shall provide the requisite program management and technical effort to define, demonstrate, and deliver the stated capability. This program will be executed in a stepped fashion in order to refine the concept, layout, and eventual configuration while reducing risk.

This acquisition embraces the use of the contractor's configuration management along with the contractor’s product information and documentation to the greatest extent possible.

The contractor shall be responsible to design, and deliver the items that have been proposed, accepted, and verified by the Government.

The contractor is responsible for providing all material, services, and necessary support documentation needed to complete the tasks identified in this SOW.

A key aspect of this project is the interface of the USMC family of future tactical generators with a hybrid system, and the associated means to accomplish this. The contractor shall be responsible for all interfaces between contractor selected / contractor furnished components, and any contractor selected / government furnished components.

2.0 APPLICABLE DOCUMENTS

The following documents specified form a part of this SOW to the extent specified herein. The most recent revision of the referenced document at the time of contract shall be used unless otherwise specified. The Performance

Specifications in Attachment 2 identify additional applicable documents. In the event of conflict between the applicable documents and this SOW, the SOW shall take precedence. Nothing in this document supersedes applicable laws and regulations unless a specific exemption has been obtained. The following Military Standards and Specifications shall have Mandatory Compliance during this contract, where applicable.

2.1 Military Standards and Specifications - Mandatory Compliance.

MIL-STD-129 Military Marking for Shipment and Storage

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

MIL-STD-882 Standard Practice for System Safety

MIL-STD-961 Defense and Program-Unique Specifications Format and Content

MIL-STD-1332 Definitions of Tactical, Prime, Precise, and Utility Terminologies for

Classification of the DoD Mobile Electric Power Engine Generator Set Family

MIL-STD-1366 DoD Interface Standard for Transportability Criteria

MIL-STD-1472 Human Engineering

MIL-STD-46855 Human Engineering Requirements for Military Systems, Equipment, and

Facilities

2.2 Handbooks - Guidance Only.

The following Handbooks are considered Guidance during this contract, where applicable.

MIL-HDBK-61A Configuration Management Guidance

MIL-HDBK-217 Reliability Prediction of Electronic Equipment

MIL-HDBK-470 Designing and Developing Maintainable Products and Systems

MIL-HDBK-633 Mobile Electric Power Engine Generator Standard Family General

Characteristics

MIL-HDBK-781 Reliability Test Methods, Plans, and Environments for Engineering

Development, Qualification, and Production

2.3 Other Government Documents – Guidance Only.

Unless otherwise stated, the following documents may be obtained from http://www.documentservices.dla.mil/ or

DLA Document Services, 5450 Carlisle Pike Bldg. 09, PO Box 2020, Mechanicsburg, PA 17055-0788.

DoDI 8500. 01 Cybersecurity

DoD 5220.22-M National Industrial Security Program Operating Manual

NAVSEAINST 9310.1B Naval Lithium Battery Safety Program

TM S9310-AQ-SAF-010 Technical Manual for Batteries, Navy Lithium Safety Program

Responsibilities and Procedures, dated 15 July 2010

(Copies of TM S9310-AQ-SAF-010, dated 15 July 2010 are available from http://www.marcorsyscom.usmc.mil/sites/pmeps/mep_policy_documents.asp or Naval Weapons Support Center, Code 3057, Building 36, Crane, IN 47522-5060)

NAVAL SEA SYSTEMS COMMAND

SG270-BV-SAF-010 -High-Energy Storage System Safety Manual

(Copies of this document are available from Naval Weapons Support Center, Code 3057, Building 36, Crane, IN 47522-5060.)

2.4 Non-Government Documents.

ASME Y14.34 Associated Lists

ASME Y14.100 Engineering Drawing Practices

(Copies of ASME documents are available from www.asme.org or American Society of Mechanical

Engineers Information Central Orders/Inquiries, P.O. Box 2300, Fairfield, NJ 07007-2300.)

EIA-649 National Consensus Standard for Configuration Management

3.0 REQUIREMENTS

The contractor shall perform all tasks required and delineated in this SOW to design, develop, integrate, test, produce prototypes, deliver and prepare associated documentation, provide test support, provide technical support, and provide system operations prior to developmental test for the MEHPS in the quantities of four (4) Light and four

(4) Medium systems as specified in the contract. The contractor shall provide all materials, equipment, hard tooling, personnel, and facilities necessary to manufacture, fabricate, integrate, produce, and deliver the types and quantities of deliverables specified by the contract.

3.1 Government Furnished Property.

3.1.1 Government Furnished Equipment.

The Government Furnished Equipment (GFE) for this contract consists of military standard generators for the Light and Medium MEHPS variants and Advanced Integrated Solar Panel Case Assembly (AISPCA) as the renewable energy source. Items will be requested and shipped to the contractor upon receipt of contractor's written request to the Marine Corps Systems Command program office. The contractor shall provide for accountability, security, and storage for the GFE provided in accordance with the Government Property clauses incorporated into this contract.

The contractor shall inspect and inventory all GFE received and identify and report any discrepancies/deficiencies.

The Government will forward an accountability agreement to the contractor for signature on an annual basis. The

Management Control Activity, Marine Corps Logistics Base (Code 827-2/MCA), Albany, Georgia, is the control and coordination point for all Marine Corps GFE.

CDRL B001, DI-MGMT-80389B, Receipt of Government Materiel Report

3.1.2 Government Furnished Information.

The Government Furnished Information (GFI) for this contract will consist of drawings and dimensions of the required railing system for the M1102 trailer mounting of the Advanced Medium Mobile Power Sources (AMMPS);

as well as the specifications for the AISPCA. The Government will furnish the GFI identified in the contract upon written request from the contractor to the Marine Corps Systems Command program office. The contractor shall notify the Government of any deficiencies in the GFI received.

CDRL B002, DI-MGMT-80596, Government Furnished Information Deficiency Report

3.2 Meetings, Formal Reviews, Conferences, and Audits.

3.2.1 Contractor Responsibilities.

The contractor shall plan, host, attend, coordinate, support and conduct the meetings, formal reviews, conferences, and audits (hereinafter called "reviews"). The reviews shall be conducted at mutually agreed upon Government and contractor facilities. Reviews requiring demonstration and/or examination of equipment shall be conducted at the contractor's facility. All such reviews shall be included in the program schedule using standard Microsoft Project software and may be held concurrently with the Government’s approval. The contractor shall prepare agendas and conference presentation materials prior to each review, and provide minutes and reports following each review. The

Government reserves the right to cancel any review or to require any review to be scheduled at critical points during the period of performance. Action item documentation, assignment of responsibility for completion, and due dates shall be determined prior to adjournment of all reviews. A summary of all action items, responsible parties, and estimated completion dates shall be included with the minutes. At the meeting the contractor shall provide to the

Government a copy of all presented material and any referenced documents.

CDRL B003, DI-ADMN-81249A, Conference Agenda

CDRL B004, DI-ADMN-81250A, Conference Minutes

Purpose Frequency Locations Start of Work Meeting Once Quantico VA In Process Review As Req TBD Preliminary Design Review @ 3months after contract award Once Contractor Critical Design Review @ 6 months after contract award Once Contractor Test Readiness Review @ 12 months after contract award Once Bethesda, MD

3.2.2 Start of Work Meeting.

The contractor shall attend a Start of Work meeting at the Government facility within 30 days of contract award.

The purpose of this meeting is for the Government to present information on the Government team and organizational structure, invoicing information through Wide Area Work Flow (WAWF), and what is expected of the contractor during the terms of the contract. At this meeting the contractor will be provided an opportunity to ask for clarification on this SOW and the PSpec. The contractor shall present management, key personnel, and program implementation processes.

3.2.3 In-Process Review.

In Process Reviews (IPR) will be held on a quarterly basis or as needed basis, at a date and location mutually agreed upon. The Government reserves the right to cancel any review or to require any review to be scheduled during the period of performance. The contractor’s progress, management, technical support services (if any), assurance of compliance with contract requirements, program status, funding, problem identification and resolutions, and actual versus expected performance of each area shall be addressed. The contractor shall prepare presentation materials providing an overview of all agenda items.

3.3 Systems Engineering.

The contractor shall establish and maintain an effective systems engineering program throughout the design, prototype, testing, and production processes.

3.3.1 Technical Reviews.

Technical reviews will be conducted in accordance with MCSCO 5400.5, Naval Systems Engineering Policy; its

Enclosure 2, the Naval Systems Engineering Technical Review (SETR) Handbook; and its Enclosure 4, Land

Systems Specific SETR Guidance invoking the MARCORSYSCOM Technical Review Handbook. The contractor shall respond to assigned Requests for Information (RFI) and Request for Action (RFA) generated during the technical reviews within the time period specified at the review. The contractor shall deliver to the Government all information presented and referenced at technical reviews no later than 30 days after the review.

3.3.1.1 Preliminary Design Review.

The contractor shall participate in a system level Preliminary Design Review (PDR) conducted three (3) months after contract award, unless otherwise agreed upon by the Government. At the PDR the contractor shall have all studies, estimates, analyses, designs, and reports available for the Government to review at least 15 days prior to the

PDR. The PDR shall be used to resolve any issues in the PSpec; however, it will not be used as an opportunity to impose additional requirements. The PDR shall include each equipment, hardware and software configuration item, and related peculiar support equipment. The contractor shall show and/or demonstrate that evaluations of materials, lead times, tooling, fabrication techniques, assembly methods, test equipment, skills, processes, and inspection techniques have been accomplished for each equipment, hardware and software configuration item, and related support equipment; that producibility objectives have been achieved; and also shall identify all single source, sole source, and diminishing source(s). This review will evaluate the progress, technical adequacy, and risk resolution

(on a technical, cost, and schedule basis) of the design and will assess the technical risk associated with the selected manufacturing (assembly) methods (processes). The contractor shall deliver to the Government all information presented and referenced at technical reviews no later than 30 days after the review. Topics the contractor shall cover at the PDR shall include, but not be limited to the following:

a. Detailed Program Plan indicating Design, Fabrication, and Test Phases

b. Electrical and mechanical design

c. Environment control and thermal design aspects

d. Electromagnetic compatibility of the preliminary design

e. Power distribution and grounding design aspects

f. Preliminary mechanical and packaging design of consoles, racks, drawers, printed circuit boards, connectors, etc.

g. ESOH engineering considerations

h. Preliminary lists of materials, parts, and processes

i. Pertinent reliability/maintainability/availability data

j. Preliminary weight data

k. Development test data

l. Corrosion prevention/control considerations

m. Transportability, packaging, and handling considerations

n. Standardization considerations

o. Trade-studies and design studies results

p. Functional flow, requirements allocation data, and schematic diagrams

q. Equipment layout drawings and preliminary drawings, including any proprietary or restricted design/process/ components and information

r. Interface requirements contained in configuration item development specifications and interface control data (e.g., interface control drawings) derived from these requirements

CDRL A001, DI-SESS-81757A, Design Review Information Package (PDR)

3.3.1.2 Critical Design Review.

The contractor shall participate in a system level Critical Design Review (CDR) conducted six (6) months after contract award, unless otherwise agreed upon by the Government. At the CDR the contractor shall have all studies, estimates, analyses, designs, and reports available for the Government to review at least 15 days prior to the CDR.

The contractor shall present a final design that incorporates all deficiencies identified from the PDR. The contractor shall provide a detailed review of the hardware design for the MEHPS and all data items required by the contract.

The contractor shall provide a trace capable of demonstrating that the design furnished at CDR implements the performance requirements of the MEHPS, and present the methods used to verify and validate the design. The contractor shall present the results of producibility analyses conducted on system hardware for Government assessment to ensure detailed producibility design solutions satisfy the established requirements. The contractor shall deliver to the Government all information presented and referenced at technical reviews no later than 30 days after the review. Topics the contractor shall cover at the CDR shall include, but not be limited to the following:

a. Detailed Program Plan indicating Design, Fabrication, and Test Phases

b. Interface specification/drawings

c. Detailed Electrical/Mechanical/Software Design

d. EMI/Thermal/Cooling Design

e. Detailed Reliability/Maintainability Analysis

f. Detailed weight data

g. Environment, Safety, and Occupational Health (ESOH) Analysis

h. Packaging/Handling/Storage/Transportation

i. Testing documents

j. Interoperability

k. Transportability

l. Corrosion Prevention and Control (CPAC)

m. Critical Safety Items (CSIs)

n. Diminishing Manufacturing Sources and Material Shortages (DMSMS)

o. Open Systems Design

p. Quality and Producibility for manufacturing

q. Supportability

r. Mock-ups, breadboards, and/or prototype hardware developed

CDRL A002, DI-SESS-81757A, Design Review Information Package (CDR)

3.3.1.3 Test Readiness Review

The contractor shall participate in a Test Readiness Review (TRR) conducted twelve (12) months after contract award upon system delivery, unless otherwise agreed upon by the Government. The contractor shall have all studies, estimates, analyses, designs, and reports available for the Government to review at least 15 days prior to the TRR.

The Test Readiness Review (TRR) is a multi-discipline product and process assessment to ensure that the system under review can proceed into formal test. The TRR assesses test objectives, test methods and procedures, scope of tests, and determines if the required test resources, including test articles, have been properly identified and coordinated to support planned tests. Topics the contractor shall cover at the TRR shall include, but not be limited to the following:

a. Overview of system operation

b. Results of testing conducted prior to delivery

c. Discrepancies or issues discovered during testing, including changes made as a result

d. Known limitations of the system which may cause issues during government testing

e. Review of Requirement Traceability Matrix (RTM) for system

CDRL A003, DI-SESS-81757A, Design Review Information Package (TRR)

3.3.2 Requirements Traceability Matrix.

At the design reviews the contractor shall provide RTM data to the Government. The RTM uniquely identifies program requirements to ensure that the requirements can be traced and verified through the design, build, test, and verification phases of development. The contractor RTM shall state the specific system part that is achieving the requirement for each requirement set forth in the PSpec. The contractor shall update the RTM at each design review and provide to the Government for review.

CDRL A004, DI-MISC-80508B, Technical Report / Study Services (RTM)

3.3.3 Corrosion Prevention and Control.

At the design reviews, the contractor shall describe the specific measures to be implemented for corrosion prevention and control design decision and identify materials and corrosion control methods that will be used to manufacture the MEHPS prototypes. The contractor shall address the techniques and processes to be applied in assuring that the products to be delivered will meet the requirements contained in the MEHPS PSpec. At a minimum, the contractor shall provide the following information 15 days prior to the design reviews with the other design review information for Government review.

a. Discussion of corrosion prevention techniques employed in design, including measures taken to minimize water collection/entrapment and collection of debris, mitigate corrosion in areas inaccessible to cleaning and maintenance, and minimize dissimilar metal contact.

b. Process instructions detailing application of coatings and other corrosion prevention compounds

(if any). Process instructions should address personnel training and qualification, material inspection, surface preparation, and coating or compound application procedures.

c. Any test data developed by the MEHPS prototype manufacturer for coatings and materials.

d. Identification of coating/substrate combinations for which no testing was required or performed.

e. Recommended corrosion control-specific maintenance.

f. Identification of any hazardous material in the Corrosion Prevention and Control process.

3.3.4 Reliability and Maintainability Program.

The contractor shall maintain a comprehensive Reliability and Maintainability (R&M) program to ensure the

MEHPS design meets the R&M standards set forth in the PSpec. The design shall be monitored throughout the entire period of performance to identify and assess any changes, which would impact reliability or maintainability.

The contractor shall develop reliability analysis and predictions as required to ensure compliance with the PSpec.

The program shall encompass all aspects of reliability with respect to design selection of components, predictions, and testing. If it is determined that an item is a throwaway, an analysis shall be performed at the next higher indenture level. The contractor shall maintain and make available to the Government all R&M data on any vendor or subcontractor supplied item and shall inform the Government of any part or component, which will degrade system R&M requirements. The R&M program shall minimally include the following task:

3.3.4.1 Procedures and Controls.

The contractor shall maintain procedures and controls, which ensure products, obtained from suppliers, vendors and subcontractors meet reliability requirements.

a. Establish, implement, and maintain documented procedures, which detect and/or preclude the use of substandard or counterfeit parts in the production process, and impose similar requirements on subcontractors.

b. Provide the Government with reasonable notice of any special R&M program review meetings scheduled with subcontractors so Government representatives may attend at their discretion.

3.3.5 Testability.

The contractor shall develop and implement a Testability Program to ensure the MEHPS is designed to provide the end-user and technicians assurance of system operation and ease in fault isolation. The Testability Program shall be included with the Reliability and Maintainability Program.

3.3.6 Human Systems Integration.

The contractor shall apply effective Human Systems Integration (HSI) principles and design activities during

MEHPS design, production and integration, and operation. The contractor shall develop and execute an HSI program that ensures Human Factors Engineering, Manpower, Personnel, Training, Environmental, Safety, Occupational Health (ESOH), Personnel Survivability, and Habitability aspects and requirements have been coordinated and incorporated into the layout, design, and development of systems having operator, maintainer and supporter interfaces. Human Factors Engineering (HFE) aspects of the HSI program shall be conducted in accordance with MIL-STD-46855A, and MIL-STD-1472. Environmental, Safety, Occupational Health (ESOH) aspects of the program shall be conducted in accordance with MIL-STD-882D.

3.3.6.1 Human Factors Engineering.

Human factors design requirements shall be established to develop effective man-machine interfaces and preclude system characteristics that require: extensive cognitive, physical, or sensory skills; complex manpower or training intensive tasks; or result in frequent or critical errors.

3.3.7 Open Architecture.

The Government intends to procure system(s) having an Open Systems Architecture and corresponding components.

As part of this contract, the contractor will be required to define, document, and follow an open systems approach for using modular design, standards-based interfaces, and widely-supported consensus-based standards in the design and manufacturing of the system. This effort will be verified during the design reviews

3.3.7.1 Design Approach Characteristics.

The contractor shall incorporate the following system architecture approach characteristics:

a. Open Architecture. The contractor shall develop and maintain a system (hardware/software) architecture that incorporates appropriate considerations for re-configurability, portability, maintainability, technology insertion, vendor independence, reusability, scalability, interoperability, upgradeability, and long-term supportability. The contractor shall ensure that external information exchange requirements are implemented in a standard and open manner as part of this effort.

b. Modular, Open Design. The contractor shall develop an architecture that is modular and limits the use of non-standard hardware, operating systems, and middleware. The contractor's design approach shall be applied to all subsystems and components. As part of the design reviews, the contractor shall, at a minimum, describe how the proposed system architecture meets these goals, including the steps taken to use non-proprietary or non-vendor unique components wherever practicable.

· Module Coupling - The contractor's design approach shall result in modules that have minimal dependencies on other modules (loose coupling), as evidenced by simple, well-defined interfaces and by the absence of implicit data sharing. The purpose is to ensure that any changes to one module will not necessitate extensive changes to other modules, and hence facilitate module replacement and system enhancement. The approach used to determine the level of coupling and the design trade-off approach shall be described during the design reviews.

· Module Cohesion - The contractor's design shall result in modules that are characterized by the singular assignment of identifiable and discrete functionality (high cohesion). The purpose is to ensure that any changes to system behavioral requirements can be accomplished by changing a minimum number of modules within the system. The approach used to determine the level of cohesion and the design trade-off approach shall be described during the design reviews.

c. System Requirements Accountability. The contractor shall ensure that all system requirements in the PSpec are accounted for through a demonstrated ability to trace each requirement to one or more modules that consist of components that are self-contained elements with well-defined, open and published interfaces implemented using open standards.

d. Inter-component Dependencies. The contractor's design approach for hardware/software of the system shall result in a layered system design, maximizing software independence from the hardware, thereby facilitating technology refresh. The design shall be optimized at the lowest component level to minimize inter-component dependencies. The layered design shall also isolate the application software layers from the infrastructure software (such as the operating system) to enhance portability and to facilitate technology refresh.

The interfaces between the layers shall be built to open standards or available to the Government with the technical data rights as required by DFARS clauses 252.227-7013 and 252.227-7015.

e. Technology Insertion. The contractor's architectural approach shall support the rapid and affordable insertion and refreshment of technology through modular design, the use of open standards, and open interfaces. The contractor shall define the functional partitioning and the physical modularity of the system to facilitate future replacement of specific subsystems and components without impacting other parts of the system and to encourage third-party vendors’ participation.

f. Interface Design and Management. The contractor shall:

i. Clearly define and describe all component and system interfaces;

ii. Define and document all subsystem and configuration item (CI) level interfaces to provide full functional, logical, and physical specifications;

iii. Identify processes for specifying the lowest level (i.e. subsystem or component) at and below which it intends to control and define interfaces by proprietary or vendor-unique standards and the impact of that upon its proposed logistics approach. Interfaces described shall include, but not be limited to, mechanical, electrical

(power and signal wiring), software, firmware, and hardware interfaces;

iv. Identify the interface and data exchange standards between the component, module or system and the interconnectivity or underlying information exchange medium;

v. Consider using these interfaces to support an overall information assurance strategy that implements Cybersecurity in accordance with DoD Instruction 8500.01 (dated 14 March 2014);

vi. If applicable, select external interfaces from existing open or Government standards with an emphasis on enterprise-level interoperability. The contractor shall describe how its selection of interfaces will maximize the ability of the system to easily accommodate technology insertion (both hardware and software) and facilitate the insertion of alternative or reusable modular system elements.

vii. Describe the extent that the change or configuration management process proposed will use

"community of interest" teams in an integrated team approach to effectively identify how individual changes impact the system's internal or external interfaces and information exchange standards.

g. Treatment of Proprietary or Vendor-Unique Elements. The contractor shall explain the use of proprietary, vendor-unique, or closed components or interfaces. If applicable, the contractor shall define its process for identifying and justifying proprietary, vendor-unique or closed interfaces, code modules, hardware, firmware, or software to be used. When interfaces, hardware, firmware, or modules that are proprietary or vendor-unique are required, the contractor shall demonstrate to the Government that those proprietary elements do not preclude or hinder other component or module developers from interfacing with or otherwise developing, replacing, or upgrading open parts of the system.

h. Open Business Practices. The contractor shall demonstrate that the modularity of the system design promotes the identification of multiple sources of supply and/or repair, and supports flexible business strategies that enhance subcontractor competition. The contractor shall conduct a market survey to identify candidate COTS, proprietary, open source software (OSS) and other reusable NDI capable of achieving the performance requirements of solutions that it proposes to custom build. The survey results shall be provided to support each design review.

i. Third Party Development. The contractor shall address how it will provide to the Government information needed to support third-party development and delivery of competitive alternatives of designs for software or other components or modules on an ongoing basis. The contractor shall provide a list of those proprietary, vendor-unique elements that it requests be exempt from this review at the preliminary design review.

j. Life Cycle Management and Open Systems. The contractor's architecture shall provide for insertion of COTS into the system and demonstrate that COTS, reusable NDI, and other components are logistically supported throughout the life cycle. The contractor shall describe and demonstrate the strategy for reducing product or system and associated supportability costs through insertion of COTS and other reusable COTS or NDI products.

The contractor shall establish a process to logistically support COTS or NDI products. The contractor shall describe the availability of commercial repair parts and repair services, facilities, and manpower required for life cycle support and demonstrate they are adequate to ensure long term support for COTS or NDI products. The contractor shall provide the proposed methodology for pass through of COTS warranties to the Government.

3.4 Producibility.

The contractor shall apply effective producibility principles during the MEHPS prototype design process to ensure that the production units will be easy to manufacture using the anticipated production facilities, equipment, materials, manpower, and processes. The producibility planning effort shall also maximize the ease of production control, quality control, tooling and inspection. The contractor shall report on the progress of this effort during the

PDR and CDR and make any data created available to the Government upon request.

3.4.1 Producibility Analysis.

The contractor shall prepare and deliver a Producibility Analysis Report.

CDRL A005, DI-MGMT-80797 – Producibility Analysis Report

3.5 Environment, Safety, and Occupational Health.

3.5.1 System Safety.

The contractor shall identify and evaluate environmental, safety, and health hazards, define risk levels, and establish a program that manages the probability and severity of all hazards associated with development, use, and disposal of the system in accordance with MIL-STD-882. Risks will be evaluated by the Government in accordance with MIL-

STD-882 and accepted as appropriate prior to exposing people, equipment, or the environment to known system related Environment, Safety, and Occupational Health (ESOH) risks. The contractor must identify all explosive safety risks as such in the system safety documentation.

3.5.1.1 Safety Assessment.

The contractor shall perform and document a Safety Assessment to identify all safety features of the hardware, software, and system design and to identify procedural, hardware and software related hazards that may be present in the MEHPS including specific procedural controls and precautions that should be followed. In addition, the contractor shall make recommendations applicable to hazards at the interface of the MEHPS with other system(s).

3.5.1.2 Safety Assessment Report.

The contractor shall provide a Safety Assessment Report (SAR) that documents the Safety Assessment and clearly identifies risks of the MEHPS. The SAR shall include a signed statement that all identified hazards have been eliminated or their associated risks controlled to acceptable levels and that the MEHPS is ready to test, field, or operate.

CDRL A006, DI-SAFT-80102C, Safety Assessment Report (SAR)

3.5.1.3 System Hazard Analysis.

The contractor shall perform and document a System Hazard Analysis (SHA) to identify hazards and assess the risk of the total system design, including software, batteries, and subsystem interfaces. The SHA shall verify system compliance with safety requirements contained in system specifications; identify previously unidentified hazards associated with the subsystem interfaces and system functional faults; and recommend actions necessary to eliminate identified hazards and/or control their associated risk to acceptable levels. The SHA shall include selected hazards, hazardous areas, or other specific items to be examined or excluded.

3.5.1.4 System Safety Hazard Analysis Report.

The contractor shall provide a System Safety Hazard Analysis (SSHA) report to the Government and identify risks that require Government acceptance.

CDRL A007, DI-SAFT-80101C, System Safety Hazard Analysis (SSHA) Report

3.5.1.5 Operating and Support Hazard Analysis.

The contractor shall perform and document an Operating and Support Hazard Analysis (O&SHA) to evaluate activities for hazards or risks introduced into the system by operational and support procedures and to evaluate adequacy of operational and support procedures used to eliminate, control or abate identified hazards or risks. The

O&SHA shall document system safety assessment of procedures involved in system production, deployment, installation, assembly, test, operation, maintenance, servicing, transportation, storage, modification, demilitarization, and disposal. The O&SHA shall include the minimum hazard probability and severity reporting thresholds and the specific procedures to be evaluated.

3.5.1.6 Operating and Support Hazard Analysis Report.

The contractor shall provide an Operating and Support Hazard Analysis (O&SHA) report to the Government.

CDRL A008, DI-MISC-80508B, Technical Report, Study/Services (OSHA)

3.5.1.7 Health Hazard Assessment.

The contractor shall perform and document a Health Hazard Assessment (HHA) to identify health hazards, evaluate proposed hazardous materials, and propose protective measures to reduce the associated risk to a level acceptable by the Government. The HHA shall include the minimum hazard probability and severity reporting thresholds and selected hazards, hazardous areas, hazardous materials, or other specific items to be examined or excluded and be presented at the CDR.

CDRL A009, DI-MISC-80508B, Technical Report, Study/Services (HHA)

3.5.2 Environmental Considerations.

The contractor shall provide information on the potential for adverse environmental impacts from the manufacturing, operation, maintenance, and disposal of the MEHPS. This information will be used to assist the

Government in making a preliminary National Environmental Policy Act (NEPA) decision and in the preparation of formal NEPA documents, which include Categorical Exclusion (CATEX), Environmental Assessments (EA), and

Environmental Impact Statements (EIS). Such environmental impacts include air, soil, wetlands, water, flora, fauna, endangered species, emissions and toxic waste resulting from development, maintenance (coatings and primers), operation, disposal, etc.

CDRL A010, DI-MISC-80508B, Technical Report, Study/Services (EC)

3.6 Configuration Management Process.

The contractor shall maintain a Configuration Management (CM) process for the control of all requirements, hardware, software and external system interface configuration documentation, media and parts representing or comprising the MEHPS.

3.6.1 Interface Control Working Group.

The contractor shall participate in joint Government-contractor working groups to ensure successful achievement of interface and interoperability requirements and problem resolution for the MEHPS. As part of this effort the contractor shall develop, maintain, update (as required), and deliver an Interface Control Document (ICD) that describes the physical/functional relationship for system/components for each MEHPS model. The ICD shall also contain the entire electrical connection configuration, pin outs of connectors, software interfaces, communication protocol between components, data transitioned between components, rate of transmission, and any other information needed to operate the system components with each other and outside systems.

CDRL A011, DI-SESS-81248B, Interface Control Document (ICD)

3.6.2 Baseline Management.

The contractor shall be responsible for maintaining the currency and accuracy of the established baseline to ensure form, fit, function, and interface of the MEHPS. The contractor shall establish definitive processes, which identify how the baseline will be managed/maintained. These processes shall be defined in the contractor's CM plan and made available for Government review at the design reviews and upon request.

3.6.2.1 Functional Baseline.

The approved configuration documentation describing a system’s or top-level CIs/Software Configuration Items

(SCI) performance (functional, interoperability, and interface characteristics) and the verification required to demonstrate the achievement of those specified characteristics is referred to as the functional baseline.

3.6.2.2 Allocated Baseline.

The allocated baseline is the approved performance oriented documentation, for a CI/SCI to be developed, which shall describe the functional and interface characteristics that are allocated from those of the higher level CI/SCI and the verification required to demonstrate achievement of those specified characteristics which shall include; (1) essential CI functional characteristics; (2) external and internal interface requirements for each CI/SCI; (3) physical characteristics necessary to ensure compatibility with associated systems and CI’s; (4) constraints on the design of a

CI, including GFE employed, component standardization, and Integrated Logistics Support requirements.

The allocated baseline shall be established after successful completion of the overall system PDR with all associated documentation.

3.6.2.3 Product Baseline.

The product baseline is the approved technical documentation that describes the configuration of a CI/SCI during the production, fielding/deployment and operational support phases of its life cycle. The product baseline shall prescribe; (1) all necessary physical or form, fit, and functional characteristics of a CI/SCI; (2) the selected functional characteristics designated for production acceptance testing and; (3) the production acceptance test requirements. The contractor shall establish the product baseline at the CDR. No changes shall be made to this baseline without prior government approval.

3.7 Engineering Drawings.

3.7.1 Developmental Design Drawings/Models.

The contractor shall create developmental design drawings/models and deliver them to the Government. If furnished by the Government, the contractor shall use existing drawings/models as the basis for creating the developmental design drawings/models. Revised and/or updated existing drawings/models and new drawings/models shall be included in the package. Developmental design drawings/models shall be used as the engineering data to support design analysis and the development of pre-production hardware. They shall serve as the basis for establishing the allocated baseline and for future development of the product drawings. These drawings/models shall also be used for configuration management and for controlling and using materials, parts, and assemblies whether produced in-house or vendor supplied.

CDRL A012, DI-SESS-81002F, Developmental Design Drawings/Models and Associated Lists

3.7.2 Commercial Drawings/Models.

The contractor shall provide commercial drawings/models to the Government for commercial items approved for use in the design and not covered by Government or nationally recognized industry association specifications and standards. The contractor shall provide evidence that the part complies with the requirements of the applicable part documentation. Existing test data shall be used to the maximum extent practicable.

CDRL A013, DI-SESS-81003E, Commercial Drawings/Models and Associated Lists

3.7.3 Product Drawings/Models.

The contractor shall develop a complete product drawing/models package and provide it to the Government. This process may require the revision and update of existing drawings, and/or development of new drawings to meet the requirements of product drawings/models and associated lists. Existing, revised, and new product drawings/models and associated lists shall be used as the engineering data for procuring, controlling, and using materials, parts, and assemblies whether produced in-house or supplied by the vendor. The drawings/models shall be used for the manufacture, assembly, inspection, testing, and configuration management of the materials, parts, modules, subassemblies, and assemblies of the equipment covered under this contract. The product drawings shall also include control drawings for all COTS items that do not conform to recognized Government or industry specifications, NDI, and items developed at private expense for which the Government had not acquired at least

Government Purpose rights (GPR). These control drawings shall provide the applicable performance specification of form, fit, and function and provide interface information needed for competitive re-procurement of that item or an interchangeable item. New product drawings/models shall conform to ASME Y14.100 and ASME Y14.34.

CDRL A014, DI-SESS-81000E, Product Drawings/Models and Associated Lists

3.8 Testing/Verification.

3.8.1 Contractor Support to Government Testing.

The contractor shall support Government Developmental Test (DT) efforts for 6 months after delivery of all items.

This support shall commence on the date the last system is delivered to the Government and shall be all-inclusive for parts, labor and travel to testing sites within 100 miles of Washington DC. The contractor shall be prepared to provide (1) one on-site technical person for a maximum of (5) days to support the testing efforts for a maximum of three (3) trips. Any user level maintenance not addressed in the Operations and Maintenance Manual shall be covered under this service.

3.9 Power.

3.9.1 Lithium Batteries.

3.9.1.1 Transportation Data.

The contractor shall provide all relevant Department of Transportation and United Nations Transportation data available on the battery. The contractor shall provide an analysis of battery transportation for the system. The contractor shall provide all information on how/why its battery is compliant with 49 CFR 173.185 shipping regulations.

CDRL A015, DI-MISC-80508B, Technical Report/ Study Services (BT)

3.9.1.2 Lithium Battery Safety Qualification.

The contractor shall develop a safety data package that shall document and demonstrate the stability of design and validity of the lithium battery selection IAW NAVSEAINST 9310.1B, TM S9310-AQ-SAF-010, dated 15 July

2010, and SG270-BV-SAF-010.

The contractor shall provide data from contractor testing of the complete system/item.

CDRL A016, DI-MISC-80508B, Technical Report/ Study Services (LB)

3.9.1.3 Lithium Battery Safety Assessment.

The contractor shall document all contractor and Government lithium battery safety assessment efforts in the Safety

Assessment Report (SAR). The SAR shall include the lithium battery risk assessment, recommendations, procedures and other corrective actions to reduce hazards to an acceptable level.

4.0 Security Requirements

The information provided to the contractor will be unclassified and/or sensitive unclassified information. The contractor is not required or expected to have a Facility Clearance and contractor personnel supporting this effort are not required to possess Personnel Clearance Levels. However, the contractor is responsible for complying with the requirements in the clause at DFARS 252.204-7012, Safeguarding of Unclassified Controlled Technical

Information, including maintaining adequate security for its information systems. Any contractor personnel requiring access to U.S. Government sensitive unclassified information shall possess a completed background investigation (minimum of a NACI) for this Public Trust Position.

SECTION E - INSPECTION AND ACCEPTANCE

The Acceptance/Inspection Schedule for CLIN 0001 has been changed from:

INSPECT AT INSPECT BY ACCEPT AT ACCEPT BY

Origin Government Destination Government

To:

Destination Government Destination Government

The Acceptance/Inspection Schedule for SUBCLIN 0001AA has been changed from:

The Acceptance/Inspection Schedule for SUBCLIN 0001AB has been changed from:

The Acceptance/Inspection Schedule for CLIN 0002 has been changed from:

SECTION F - DELIVERIES OR PERFORMANCE

DELIVERY INFORMATION

DELIVERY SCHEDULE

CLIN Description Qty Due Date Del. Destination

Design and

Fabrication N/A N/A N/A

0001AA

Design and

Fabrication-

Light MEHPS 4 12 months

ADC

N00167

Naval Surface Warfare Center-

Caderock

Attn: Eric Shields

BLDG 12 RM 204

9500 Macarthur Blvd

Bethesda, MD 20817-5700

0001AB

Design and

Fabrication-

Medium MEHPS 4 12 months

ADC

N00167

Naval Surface Warfare Center-

Caderock

Attn: Eric Shields

BLDG 12 RM 204

9500 Macarthur Blvd

Bethesda, MD 20817-5700

Testing and

Verification

Begin 12 months

ADC through 6 months After

Delivery of all items

Within 100 miles of

Washington, DC

Contract Data

Requirement

List

N/A N/A N/A

0003AA

CDRL DATA ITEM

B001

5 Calendar Days after Receipt of

GFE

See Contract Data

Requirements Lists

0003AB

CDRL DATA…