N00024-15-R-6406_Amendment_0001.pdf

15NR94422

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) update the Points of Contact for the Contract Specialist and Procuring Contracting Officer (PCO);

and (2) provide responses to industry questions, w hich update Attachment 1, Attachment 3, Attachment 4, Attachment 8, Attachment 11, Exhibit A, Exhibit C, Exhibit D, Exhibit E, and revise N00024-15-R-6406 accordingly.

1. CONTRACT ID CODE PAGE OF PAGES

S 1 96

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

16C. DATE SIGNED

BY 28-Jan-2016

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 N00024-15-R-6406

X 9B. DATED (SEE ITEM 11)

16-Dec-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 X is extended, 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 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

28-Jan-2016

CODE

NAVAL SEA SYSTEMS COMMAND (HQ)

1333 ISAAC HULL AVE SE

WASHINGTON NAVY YARD DC 20376-2060

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N00024-15-R-6406

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The required response date/time has changed from 16-Feb-2016 12:00 PM to 01-Mar-2016 12:00 PM.

The Issued By organization below has been deleted:

NAVAL SEA SYSTEMS COMMAND (HQ)

1333 ISAAC HULL AVE SE

WASHINGTON NAVY YARD DC 20376-2060

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

PART 3 SCOPE OF WORK

3.1 SCOPE

This Scope of Work defines the work required for design, engineering, and production of the MK 54 LWT Common Parts hardware and software in accordance with the contract baseline (Section J, Attachment 1). It shall include Proof of Design (POD) Kits, Proof of Manufacture (POM) Kits, MK 54 LWT Common Parts Kits, MK 54 MOD 0 LWT PGA and MK 54 MOD 0 LWT W4 Cable, exercise fuel tanks, engineering services, production support material, tested spare components, hardware repair, GFE maintenance and repair services, warranty on supplies, non-recurring engineering data, Technical Data Package (TDP) update, and production data. This effort also includes the modification of test equipment capable of verifying the performance requirements in accordance with the contract baseline.

The pre-production effort for MK 54 LWT Common Parts Kits includes a required demonstration and production of POD and POM units provided to the Government for qualification and validation testing.

This will verify and validate the design prior to production.

There Contractor shall resolve obsolescence issues within the current design that impact the current software (SW), middleware (MW), and firmware (FW). Firmware consists of all programs that are embedded in a component or test equipment including portions of Built In Test (BIT), loaders, and Programmable device logic. Software consists of all programs that are downloadable and reprogrammable including middleware, Fault Detection Fault Localization (FDFL), operating system (OS), Board Support Package (BSP), and portions of Built In Test (BIT). The Government will supply the SW, MW, FW, OS, and BSP in the current design as GFI to assist the Contractor’s efforts on this contract. The Contractor shall modify, reuse, or replace the provided SW, MW, and FW as necessary to meet the requirements of the Contract Baseline (Attachment 1). In addition to torpedo component obsolescence issues, the GFE factory test equipment (FTE) commonly known as the Automatic Lightweight Integration Test Set (AutoLITS) may also require updates to the software baseline due to design changes in the product. FTE software baseline updates shall also be performed by the Contractor.

3.1.1 BACKGROUND

The MK 54 LWT maximizes the use of non-developmental item (NDI) technologies, incorporating the proven technologies from existing torpedo programs with state of the art commercial off-the-shelf (COTS) processors and is a modular upgrade to the LWT torpedo inventory. The MK 54 LWT is primarily intended as an Anti-Submarine Warfare (ASW) torpedo in littoral scenarios. The MK 54 LWT can be deployed by surface ships, fixed or rotary winged aircraft, missiles, and specially equipped unmanned vehicles. The MK 54 LWT operates in the challenging acoustic environment encountered in littoral scenarios, is effective in the presence of threat countermeasures, and has MK 46 torpedo ASW capability in deep-water scenarios. The MK 54 LWT provides direct and urgent-attack capability for both surface and air platforms.

3.2 APPLICABLE DOCUMENTS

To the extent referenced herein, the following documents form a part of this SOW and are hereby incorporated by reference. In the event of a conflict between the documents referenced herein and the contents of the SOW, the contents of the SOW shall take precedence. Other documents and specifications provided as Government Furnished Information (GFI) are identified in Attachment 3.

3.2.1 CONTRACT BASELINE DOCUMENTS

Attachment 1 – Contract Baseline, provides the list of design specifications, performance specifications, interface requirement documents, assembly drawings, and part drawings applicable to this contract.

3.2.2 PROGRAM UNIQUE DOCUMENTS

Title Date and/or Revision

OPNAVINST S5513.5C – Undersea Warfare Program Security Classification Guides (SCGs) SCG ID: 139.2, MK 48 ADCAP (MODS 5 and beyond), MK 50, AND MK 54 Torpedoes (See Attachment 3 – GFI)

26 April 2010

Torpedo FY11 Kit System Safety Program Plan (SSPP) (See Attachment 3 –

GFI)

April 2014 Rev 1

Undersea Weapons Program Office, Risk Process Description (See Attachment 3 – GFI)

8 September 2003

Configuration Management Plan for Undersea Weapons Program (PMS 404), PEO SUB S0199-133-A-O-C (See Attachment 3 – GFI)

August 2010 Rev D

3.2.3 OTHER GOVERNMENT DOCUMENTS

Title Date and/or Revision

National Industrial Security Program Operating Manual (NISPOM) (DoD 5220.22M) (See http://quicksearch.dla.mil/)

28 February 2006

Configuration Management Guidance(MIL-HDBK-61) (See http://quicksearch.dla.mil/)

7 February 2001 Rev A

Environmental Stress Screening (ESS) of Electronic Equipment (MIL-HDBK-

344) (See http://quicksearch.dla.mil/)

16 August 1993 Rev A

General Guidelines for Electronic Equipment (MIL-HDBK-454) (See http://quicksearch.dla.mil/)

12 December 2012 Rev B

Failure, Reporting, Analysis and Corrective Action Taken (MIL-HDBK-2155) (See http://quicksearch.dla.mil/)

11 December 1995

Military Marking for Shipment and Storage (MIL-STD-129) (See http://quicksearch.dla.mil/)

18 February 2014 Rev R

Title Date and/or Revision Identification Marking of U.S. Military Property (MIL-STD-130) (See http://quicksearch.dla.mil/)

16 November 2012 Rev N Chg 1

Joint Electronics Type Designation System (MIL-STD-196) (See http://quicksearch.dla.mil/)

11 September 2013 Rev F

DoD Standard Practice System Safety (MIL-STD-882) (See http://quicksearch.dla.mil/)

11 May 2012 Rev E

Standard Practice for Military Packaging (MIL-STD-2073) (See http://quicksearch.dla.mil/)

7 January 2011 Rev E Chg 1

Electrostatic Discharge Control Program For Protection of Electrical and Electronic Parts, Assemblies and Equipment (Excluding Electrically Initiated Explosive Devices) (MIL-STD-1686) (See http://quicksearch.dla.mil/)

25 October 1995 Rev C

Technical Data Packages (MIL-STD-31000) (See http://quicksearch.dla.mil/) 26 February 2013 Rev A

National Aerospace Standard, Hazardous Materials Management Program (NAS 411) (See http://quicksearch.dla.mil/)

19 January 1995

Navy Manufacturing Screening Program (NAVMAT P-9492) (See http://quicksearch.dla.mil/)

May 1979

Department of the Navy Weapons System Explosives Safety Review Program (NAVSEAINST 8020.6E) (See http://quicksearch.dla.mil/)

11 March 2008

Federal Acquisition Regulation (FAR) (See https://acquisition.gov/far/) Available Online Defense Federal Acquisition Regulation Supplement (DFARS) (See http://farsite.hill.af.mil/vfdfara.htm)

Available Online

GIDEP Operations Manual, S0300-BT-PRO-010 (See http://www.gidep.org) Available Online

3.2.4 NON-GOVERNMENT DOCUMENTS

Document Number Title Date and/or Revision

ASME Y14.2 Line Conventions and Lettering (See https://www.asme.org/shop)

ASME Y14.24 Types and Applications of Engineering Drawings (See https://www.asme.org/shop)

ANSI/EIA 649B Configuration Management Standard (See http://webstore.ansi.org/)

ANSI/ISO/ASQ

Q9001

Quality Management Systems – Requirements (See http://webstore.ansi.org/)

November 2008

ASTM-D3951-10 Standard Practice for Commercial Packaging (See http://www.astm.org/Standard/standards-and-publications.html)

ASTM-D4169-09 Standard Practice for Performance Testing of Shipping Containers and Systems (See http://www.astm.org/Standard/standards-and-publications.html)

GEIA-HB-0005-2 Technical Guidelines for Aerospace and High

Performance Electronic Systems Containing Lead- Free Solder and Finishes (See https://global.ihs.com/)

November 2007

GEIA-STD-0005-1 Performance Standard for Aerospace and High Performance Electronic Systems Containing Lead-free Solder (See https://global.ihs.com/)

March 2012

GEIA-STD-0005-2 Standard for Mitigating the Effects of Tin Whiskers in Aerospace and High performance Electronic Systems (See https://global.ihs.com/)

May 2012

IPC-2220 series 2221B: Generic Standard on Printed Board Design 2222A: Sectional Design Standard for Rigid Organic Printed Boards 2223C: Sectional Design Standard for Flexible Printed Boards 2224: Sectional Standard of Design of PWBs for PC Cards 2225: Sectional Design Standard for Organic Multichip Modules (MCM-L) and MCM-L Assemblies 2226: Sectional Design Standard for High Density Interconnect (HDI) Boards (See https://portal.ipc.org/ipc-store.htm)

2221B: November

2222A: December

2223C: November

2224: January 1998

2225: May 1998

2226: April 2003

IPC-4101 Specification for Base Materials for Rigid and Multilayer Printed Boards (See https://portal.ipc.org/ipc-store.htm)

April 2014 Rev D

IPC-6010 series 6011: Generic Performance Specification for Printed Boards 6012C: Qualification and Performance Specification for Rigid Printed Boards 6013C: Qualification and Performance Specification for Flexible Printed Boards 6015: Qualification & Performance Specification for Organic Multichip Module (MCM-L) Mounting & Interconnecting Structures 6016: Qualification & Performance Specification for High Density Interconnect (HDI) Layers or Board 6017: Qualification and Performance Specification for Printed Boards Containing Embedded Passive Devices 6018B: Qualification and Performance Specification for High Frequency (Microwave) Printed Boards (See https://portal.ipc.org/ipc-store.htm)

6011: July 1996

6012C: April 2010

6013C: December

6015: February

6016: May 1999

6017: March 2009

6018B: November

IPC-A-600 Acceptability of Printed Boards (See https://portal.ipc.org/ipc-store.htm) April 2010

IPC-A-610 Acceptability of Electronic Assemblies (See https://portal.ipc.org/ipc-store.htm)

April 2010 Rev E

IPC-CC-830 Qualification and Performance of Electrical Insulating Compound for Printed Wiring Assemblies (See https://portal.ipc.org/ipc-store.htm)

October 2008 Rev B Amd 1

IPC J-STD-001 Requirements for Soldered Electrical and Electronic Assemblies (See https://portal.ipc.org/ipc-store.htm)

April 2010 Rev E

IPC-MI-660 Incoming Inspection of Raw Materials Manual (See https://portal.ipc.org/ipc-store.htm)

February 1984

IPC-QL-653 Certification of Facilities that Inspect/Test Printed Boards, Components and Materials (See https://portal.ipc.org/ipc-store.htm)

November 1997 Rev A

IPC-TM-650 Test Methods Manual (See https://portal.ipc.org/ipc-store.htm)

January 2007

IPC/WHMA-A-620 Requirements and Acceptance for Cable and Wire Harness Assemblies (See https://portal.ipc.org/ipc-store.htm)

August 2013 Rev B Amd 1

SAE/EIA-649 Configuration Management Standard (See http://store.sae.org/)

April 2011 Rev B

SAE/EIA-748 Earned Value Management Systems (See http://store.sae.org/)

March 2013 Rev C

3.3 REQUIREMENTS

3.3.1 PROGRAM MANAGEMENT

The Contractor shall organize, coordinate and control all program activities to ensure the correct and timely performance of work required by the SOW is accomplished. The Contractor shall develop and provide a Program Management Plan (PMP) in accordance with CDRL A008. The PMP shall contain sufficient detail to allow the Government insight into the Contractor's management and scheduling of all efforts necessary to meet the contract requirements. The Contractor shall include a description of their process of identifying and tracking risks and opportunities in the PMP. Where these efforts are event as opposed to calendar driven, schedule estimates shall be provided. The Contractor shall designate a Contractor's program manager who shall have responsibility for all aspects of the MK 54 LWT Common Parts Kits procurement, and shall be responsible for providing a Contractor’s Progress, Status and Management Report in accordance with CDRL A009.

3.3.1.1 SECURITY REQUIREMENTS

The Contractor shall establish and maintain a facility clearance with a minimum of SECRET classification as issued by the Defense Investigative Service. Specific Contractor security access requirements are outlined in the DD Form 254 Contract Security Classification Specification (Attachment 6).

The Contractor shall issue the proper classification markings and maintain security for all classified items, including documentation, hardware, firmware and software produced during this procurement in accordance with the Office of the Chief of Naval Operations Instruction (OPNAVINST) S5513.5C, dated 26 April 2010. The Contractor’s facility clearance must support the ability to view classified information across all mediums (hard copy, electronic, CD/DVD, etc.).

The Contractor shall have the necessary clearances and processes necessary to ship and receive classified shipments.

The Contractor shall either establish the procedures and processes necessary to declassify all potentially classified hardware being delivered under this contract or contain all of their necessary Factory Test Set (both Contractor developed and Government Furnished) in classified areas. All declassification processes and procedures shall be approved by the Defense Security Service (DSS), prior to delivery.

3.3.1.2 PARTS MANAGEMENT

The Contractor shall establish and maintain a Parts Management Program in accordance with the requirements of CDRL A010 – Parts Management Plan, for all MK 54 LWT Common Parts Kits, MK 54 MOD 0 LWT PGAs and W4 Cables, exercise fuel tank(s) and modifications to GFE. The Contractor shall verify that the use of parts meet the contractual requirements, reduce proliferation of parts within and across Department of Defense (DoD) weapons systems and equipment through standardization, enhance reliability and supportability to meet material readiness objectives, and reduce total life-cycle costs. Also, the Contractor shall describe how the parts management process is validated, how process improvements are incorporated, and how process variation is controlled.

The Contractor shall actively participate in the Government Industry Data Exchange Program in accordance with contract clause 5252.227-9113 Government –Industry Exchange Program (APR 2015).

The Contractor shall submit information concerning critical or major non-conformances, as defined in FAR 46.407/DFARS 246.407, to the GIDEP information system. All GIDEP alerts or notifications impacting this contract shall be included as part of CDRL A009 – Contractor’s Progress, Status and Management Report.

3.3.1.2.1 ENGINEERING ANALYSIS

The Contractor shall conduct engineering analysis of the contract baseline (Attachment 1), build-to-print TDP, and provided GFI in an effort to identify any changes that are required to resolve obsolescence issues including the modification of any affected hardware and validation of the modified hardware to reflect current best practices and update supplier information to ensure a producible design. The Contractor shall recommend design changes to ensure continuous manufacturing and/or repairing capabilities in accordance with the configuration management requirements of this contract.

3.3.1.2.2 PARTS MANAGEMENT ELEMENTS

The Contractor shall address the following parts management elements in the Parts Management Plan submitted in accordance with CDRL A010:

a. Parts selection baseline.

b. Parts selection and authorization process.

c. Obsolescence management.

(1) The Parts Management Plan shall define the Contractor's process(es) that mitigate the risks associated with technology obsolescence; proprietary technologies; the loss or impending loss of manufacturers or suppliers of components, assemblies, or materials used in the system; and provide rationale for reliance on a single source of supply over the life of the system.

(2) The Parts Management Plan shall contain provisions to minimize the impact of obsolescence during contract execution, effectively manage obsolescence through planned modernization, and avoid additional costs from being incurred by the Government due to obsolescence.

(3) The Parts Management Plan shall address means and approach for providing the Government with information regarding obsolescence and DMSMS issues, access and insight into the Contractor's DMSMS forecasting tool, part list screening, part list monitoring, processing of Government Industry Data Exchange Program (GIDEP) DMSMS alerts, processing of DLA DMSMS alerts, communication with and availability of information to the Government, a means and approach for establishing obsolescence and DMSMS solutions, and a plan for managing commercial off-the-shelf (COTS) items.

(4) The Contractor shall ensure all known and forecasted DMSMS issues are identified and have a mitigation plan, so that the Government is not left with an unsupportable system due to DMSMS. The Contractor shall provide prompt notification to the Government for any DMSMS/obsolescence issues in accordance with Section C, paragraph 3.3.2. Approved changes shall be made in accordance with the configuration management requirements of this contract.

d. Parts list or Bill of Materials (BOM).

e. Subcontractor management.

f. Part and supplier quality.

g. Part level documentation procedures.

h. Substitute and alternative part procedures.

i. Customer-Contractor teaming.

j. Counterfeit parts.

k. Lead-free electronic parts.

l. Long lead material.

3.3.1.2.3 OBSOLESCENCE ANALYSIS AND REPORTING

The Contractor is responsible for the identification of all DMSMS/obsolescence/producibility issues associated with production and delivery of MK 54 LWT Common Parts Kits, MK 54 MOD 0 PGAs and W4 Cables, and exercise fuel tank(s) under this contract in accordance with the TDP and Section C, paragraph 2.4. The Contractor shall submit forecasting DMSMS source data in accordance with CDRL A011 – Source Data for Forecasting Diminishing Manufacturing Sources and Material Shortages

(DMSMS).

For purposes of this contract, producibility is defined as the ability to procure, fabricate, assemble, and test an item using available production technology while still meeting the necessary quality and performance requirements. This definition shall apply to all technical data supplied as a part of any change issued under this contract if the additional DMSMS/obsolescence/producibility effort is required by reason of a Government-issued change. In which case, this provision entitles the Contractor to an equitable adjustment for which the amount shall be included in the settlement of the change order for the Government-issued change.

3.3.1.2.4 OBSOLESCENCE TASKING UPDATES

The Contractor shall provide obsolescence tasking updates as part of the CDRL A009 – Contractor’s Progress, Status and Management Report. The obsolescence tasking updates shall address the results of the ongoing review and identification of actual and potential issues within Contractor and their vendors

BOM. The Contractor shall use the DoD DMSMS Center of Excellence Shared Data Warehouse for the purpose of exchanging obsolescence information across the DoD enterprise.

3.3.1.2.5 COMMUNICATION OF DMSMS REQUIREMENTS

The Contractor shall develop and flow down to all of its subcontractors and vendors DMSMS requirements sufficient to ensure that the end items and services provided meet all requirements of this contract.

3.3.1.2.6 COUNTERFEIT ELECTRONIC PARTS

The Contractor shall establish a written Contractor Counterfeit Electronic Part Detection and Avoidance System in accordance with DFARS 252.246-7007. This requirement shall flow down to all subcontractors and vendors.

3.3.1.3 RISK MANAGEMENT PROCESS

The Contractor shall implement a comprehensive risk management process that focuses on program risk areas and the program's critical path to systematically identify and mitigate cost, schedule, and technical risks. The Contractor shall use the "Undersea Weapons Program Office Risk Process Description" as provided in Section 3.2.2 – Program Unique Documents as the basis for the risk management process.

The Contractor shall provide risk item reports, including the identification and adjudication of risk items in accordance with CDRL A009 – Contractor’s Progress, Status and Management Report, and shall submit risk management process information during scheduled program reviews.

3.3.2 PROGRAM REPORTING

The Contractor's program manager shall provide CDRL A009 – Contractor’s Progress, Status and Management Report, covering all efforts under this contract including subcontractor/supplier performance against the schedule baseline established in the PMP, TIs/engineering services, obsolescence tasking updates and reviews, parts management, risk management, failure analysis, returned goods, and other work performed under the contract during the month of the report, in addition to design, development, manufacture, test, and production efforts on deliverable hardware and factory test equipment. The obsolescence tasking updates shall address the results of the ongoing review and identification of actual and potential issues within Contractor and their vendors BOM. The Contractor shall use the DoD DMSMS Center of Excellence Shared Data Warehouse for the purpose of exchanging obsolescence information across the DoD enterprise.

3.3.2.1 REVIEWS AND MEETINGS

The Contractor shall be responsible for hosting all reviews and meetings in Sections 3.3.2.1.3 through 3.3.2.1.7, unless otherwise noted. Each review/meeting specified in Sections 3.3.2.1.3 through 3.3.2.1.7 shall include providing for meeting location with all necessary administrative support as well as development, coordination and distribution of the agenda and program review and IPT presentation packets in accordance with CDRL A012 – Presentation Material, for each review. At PMS 404 discretion, Government-arranged facilities and administrative support may be used to support the meeting.

3.3.2.1.1 MEETING MINUTES

The Contractor shall record, generate, and process submittal of the review minutes from the participants of reviews and track all action items after the reviews. The Contractor shall report these minutes and action item tracking data as CDRL A013 – Meeting Minutes/Action Logs. Progress and updated status on action items shall also be included in CDRL A009 – Contractor’s Progress, Status and Management Report.

3.3.2.1.2 REMOTE MEETING PARTICIPATION

Unless otherwise noted by the Government for the individual review or meeting events, the Contractor shall provide unclassified electronic and video or audio teleconference capability allowing remote participation of conference room presentation screen by, and verbal participation of, Government personnel located in internet-connected Government offices, including NUWC Division, Newport and NUWC Division, Keyport locations. The Contractor shall provide internet-based ability to access or download unclassified program review documentation, models, and data to Government personnel located in internet connected Government offices.

3.3.2.1.3 INTER-ORGANIZATIONAL CONTRACT PROCESSES FAMILIARIZATION

WORKSHOP

Within sixty (60) days after contract award, the Contractor shall host, support the Government, and attend an Inter-Organizational Contract Processes Familiarization Workshop. The workshop will be facilitated by the Defense Acquisition University (DAU). The Contractor shall support the Government in preparing for and attending the workshop which shall be no longer than four (4) working days and accommodate at a minimum twenty (20) personnel: ten (10) Government and five (5) each from the Contractor and DAU and shall include participation of any major subcontractors supplying non-commercial items. As risk mitigation to miscommunications and other inter-organizational performance delays, this workshop allows Government and Contractor personnel to become familiarized with the organizational structures and processes under the new contract effort.

3.3.2.1.3.1 WORKSHOP PRESENTATION MATERIAL

On the dates of the workshop, the Contractor shall participate on-site and provide presentations as required. The Contractor shall review the agenda of the workshop and prepare presentation material to support Contractor briefing topics which shall be submitted in accordance with CDRL A012 – Presentation Material, prior to the workshop. In addition to agenda topics, the Contractor shall also provide the following data (CDRL A019):

a. Introduction to Contractor personnel, internal processes, and tools

b. Contractor cost monitoring techniques

c. Contractor organization chart with roles, names, email addresses and phone numbers

The Government will provide slide packages to the Contractor two (2) days in advance of the workshop.

The Contractor shall provide hard copies of all presentation material to all participants in the workshop.

3.3.2.1.4 INTEGRATED BASELINE REVIEW (IBR)

The Contractor shall host a post-award Integrated Baseline Review (IBR) no sooner than one-hundred-twenty (120) days and no later than one-hundred-eighty (180) days after contract award. During the post-award IBR, the Contractor shall present its PMP to the Government. The IBR shall detail the Contractor's planning to ensure complete coverage of the work effort required by the contract, the Contractor's logical scheduling of work activities, the Contractor's adequate resourcing, the Contractor understanding of technical requirements, and the Contractor's identification of inherent risks. Completion of the post-award IBR will result in establishment of a baseline for all elements of the production schedules provided in the PMP. Additional IBRs are required for major changes to the baseline or changes to any Government approved Contractor plans. Contractor shall update CDRL A008 according to results of IBR action items and resubmit for Government approval.

3.3.2.1.4.1 IBR DOCUMENTATION

The Contractor shall submit for Government review and approval an IBR agenda, IBR meeting minutes, IBR action logs, and all data required by entrance and exit criteria detailed above in accordance with

CDRL A013.

3.3.2.1.4.2 IBR ENTRANCE CRITERIA

The Contractor shall meet all IBR entrance criteria identified herein prior to hosting the IBR

a. Baseline is established by the Contractor reflecting the entire scope of work for the performance of the contract.

b. Project schedule key milestones are identified and documented.

c. Submittal of CDRL A008 – Program Management Plan.

d. Program risks and opportunities are identified.

e. Technical scope of work is consistent with performance specifications.

f. Resources such as budget, facilities and personnel are planned for the program and measured for variances.

g. Tasks are planned and can be measured objectively relative to the technical progress.

h. Program schedule is executable and updated.

i. Program has an executable budget plan established and is being measured for variances.

j. Management processes are documented for execution of the project.

k. Earned Value Management System (EVMS) is in place, including a plan for earned value collection and periodic status.

3.3.2.1.4.3 IBR EXIT CRITERIA

The Contractor shall meet all exit criteria identified herein to complete the IBR.

a. Technical scope of work is fully included and is consistent with authorizing contract documents.

b. Formal integrated and resource loaded Work Breakdown Structure (WBS) with cost and schedule baselines established and approved.

c. Approval of PMP provided under CDRL A008.

d. IBR action items completed and approved.

3.3.2.1.5 SYSTEMS ENGINEERING TECHNICAL REVIEW (SETR)

The Contractor shall host the SETRs listed below throughout the performance of this contract to demonstrate readiness to proceed in its hardware and software development efforts under the approving authority of the Undersea Weapons Program Manager. These SETRs shall be captured as program milestones in the Contractor's Systems Engineering Management Plan (SEMP) provided under CDRL A014 and PMP provided under CDRL A008. The SEMP shall describe the plan to complete necessary SETR tasking. The Contractor shall present all of the information detailed in CDRL A015 – Design Review Information Package (DRIP), at the applicable SETRs and deliver to the Government the DRIP for review and approval. The Contractor shall include any necessary Objective Quality Evidence (OQE) (e.g. test procedures, test reports, specification documents, design documents, interface documents, user manuals, configurations item data bases, schedules, etc.) referenced or needed to support the information presented in the DRIP with the CDRL A015 delivery. Systems engineering technical reviews shall be conducted for CLIN 0002 items and include:

a. System Requirements Review (SRR)

b. System Functional Review (SFR)

c. Software Specification Review (SSR)

d. Hardware Preliminary Design Review (HPDR)

e. Software Preliminary Design Review (SPDR)

f. Hardware Critical Design Review (HCDR)

g. Software Critical Design Review (SCDR)

h. Test Readiness Review (TRR)

i. Physical Configuration Audit (PCA)

j. Functional Configuration Audit (FCA)

The Contractor may combine multiple SETRs into a single meeting, should the Contractor be able to present all of the necessary information and the Contracting Officer's Representative (COR) approves the combination of the SETRs. In order to receive COR approval, the Contractor shall send a formal request to combine multiple SETRs into a single meeting at least thirty (30) days prior the planned meeting date.

3.3.2.1.5.1 FIRMWARE DESIGN

The Contractor shall include firmware design discussions as part of the HPDR and HCDR.

3.3.2.1.5.2 GOVERNMENT REVIEW AND APPROVAL

In accordance with CDRL A015 – Design Review Information Package (DRIP), the Contractor initiated SRR, SFR, SSR, and SPDR reviews will not be subject to Government approval. The Contractor shall provide the Government with a minimum of thirty (30) days-notice before conducting Contractor-initiated SETRs providing physical and remote access to allow the Government to attend the reviews. The Government reserves the right to provide comments for Contractor reviews. Government review and approval shall be required for the HPDR, HCDR, SCDR, TRR, PCA, and FCA in accordance with CDRL A015.

3.3.2.1.5.3 TEST READINESS REVIEW (TRR)

The Contractor shall host a TRR to demonstrate readiness to proceed in testing efforts under the approving authority of the Undersea Weapons Program Manager. In addition to the CDRL A015 requirements for the TRR, the Contractor shall present for Government review and approval test plans and procedures, test assets, facilities, risks in the upcoming test periods, and other related items. The Contracting Officer's Representative will provide authorization for the Contractor to proceed with the TRR once the following have been completed:

a. Approved test plan and procedures (CDRLs A001 and A034).

b. Approved First Article Test Plans and Procedures (CDRL A001) and Factory Acceptance

Test (FAT) Plan and Procedures (CDRL A034).

c. Approved Factory Test Equipment Certification Plans (CDRL A033).

d. Approved and Completed Test Equipment TDP and Software (CDRLs B002 and B004).

e. Updated and approved SEMP (CDRL A014).

f. Approved Test Equipment Validation Report (CDRL A036)

The TRR shall comply with all requirements in accordance with CDRL A014 – Systems Engineering Management Plan, and all action items generated during the TRR shall require resolution and closure.

Once all requirements are met, the Contracting Officer's Representative will issue a TRR closure letter authorizing the Contractor to proceed into formal qualification testing. Post TRR, any issues found during POD, Highly Accelerated Stress Screen (HASS), Proof Of Screen (POS), Margin Testing, or First Article Testing that necessitate revision of previously approved Contractor submitted CDRLs shall be addressed and the CDRLs revised and resubmitted for Government approval prior to PRR.

3.3.2.1.6 PRODUCTION READINESS REVIEW (PRR)

The purpose of PRR is for the Contractor to demonstrate to the Government that it has accomplished adequate production planning without incurring unacceptable risks that could breach schedule, performance, cost, technical, contractual requirements, or other established criteria and gain concurrence from the Government to produce production units. The Contractor shall submit a PRR agenda and PRR presentations in accordance with CDRL A012 – Presentation Material.

3.3.2.1.6.1 PRR REQUIREMENTS

PRR shall comply with all requirements in accordance with CDRL A014 – Systems Engineering Management Plan, and all action items generated during the PRR shall require resolution and closure.

Once all PRR requirements are met, the Program Manager will issue a closure letter. The Contracting Officer will issue a letter authorizing the Contractor to begin factory production deliveries. Upon completion of PRR, all TDPs and factory processes shall be baselined. The Government will determine when all entrance and exit criteria for the PRR have been satisfied and the Contracting Officer's Representative will notify the Contractor at least fourteen (14) working days prior to the milestone event to schedule PRR.

3.3.2.1.6.2 PRODUCTION READINESS REVIEW (PRR) ENTRANCE CRITERIA

The Contractor shall meet all entrance criteria identified herein prior to PRR.

a. Actions from Functional Configuration Audit (FCA) completed and approved.

b. Actions from Physical Configuration Audit (PCA) completed and approved.

c. Completion of Government first article and POM testing.

d. Approval of First Article Test Report (CDRL A002).

e. Supply sources and vendors are in place.

f. Approved Quality Program Plan addressing QASP elements (CDRL A016).

g. Approved Test Plan and Procedures (CDRL A001).

h. Approved Test Equipment TDP (CDRL B002).

i. Approved SEMP (CDRL A014).

j. Program risks have been evaluated by a joint Contractor/Government (including the Technical

Warrant Holder, Technical Design Authority, and Program Manager) review and ascertained to be acceptable at this phase of the program.

k. System product baseline has been established and documented for the system, subsystem, equipment, and software including establishing nomenclature in accordance with MIL-STD-196F

– Joint Electronics Type Designation Automated System, and to enable hardware fabrication and software coding to proceed with proper configuration management.

l. Technical performance measures are in place and being regularly monitored.

m. Program schedule is executable and updated.

3.3.2.1.6.3 PRODUCTION READINESS REVIEW (PRR) EXIT CRITERIA

The Contractor shall meet all exit criteria identified herein to complete PRR.

a. PRR action items completed and approved by the Program Manager, PMS 404.

3.3.2.1.7 PROGRAM MANAGEMENT REVIEWS

The Contractor shall conduct quarterly Program Management Reviews (PMRs).

3.3.2.1.7.1 PMR REQUIREMENTS

PMRs shall include, at a minimum:

a. Schedule performance covering all completed and planned efforts.

b. Risk management activities.

c. A review of all program, contractual, and obsolescence issues.

d. A review of all test efforts.

e. A review of all TIs including cost, technical and schedule performance.

f. A cost data review and performance to price.

g. A review of production through-put calculations.

3.3.2.1.7.2 PMR HOSTING

The Contractor shall propose dates and location no less than forty-five (45) days prior to the PMR. The Government will confirm the dates and location no less than thirty (30) days prior to the PMR. The Contractor shall be responsible for hosting all PMRs. Hosting shall include provision of meeting location at or within twenty (20) miles of the Contractor's facility or at a mutually agreed to location with the Government. A minimum of one PMR each year shall be conducted in the Washington D.C. area, within fifty (50) driving miles of the Washington Navy Yard. At PMS 404 discretion, Government arranged facilities and administrative support may be used to support the program review(s). Contractor hosting shall include all necessary administrative support as well as meeting location access, development, coordination, and distribution of the agenda in accordance with CDRL A012 – Presentation Material, for each review.

3.3.2.1.7.3 PMR DOCUMENTATION

The Contractor shall record, generate and process submittal of the review minutes from the participants of program reviews, and track all action items for completion. The Contractor shall report meeting minutes, action item tracking data, progress and updated status on action items in accordance with CDRL A013 following each PMR.

3.3.2.2 INTEGRATED PRODUCT TEAMS

The Contractor shall coordinate and host Government/Contractor Integrated Product Teams (IPT) at the leadership and working group levels to achieve program goals. At a minimum, IPTs shall be established for the following:

a. Monthly leadership meetings to review program status and determine go forward actions as needed. CDRL A009 – Contractor’s Progress, Status and Management Report will serve as the information package for this meeting.

b. Weekly Systems Engineering meetings to support execution of the Government approved System Engineering Management Plan (CDRL A014).

c. Weekly working level production meetings to resolve and discuss ongoing progress, status, condition of GFE, failure analysis, quality metrics, and program issues.

d. Twice monthly (minimum) meetings to review status and critical paths of Contractor and Government Integrated Master Schedules (IMSs) related to the execution of this contract until MK 54 LWT Common Parts Kits are delivered. Key drivers between Contractor and Government tasking shall be identified to establish programmatic critical paths.

The Contractor shall coordinate all IPT meetings and shall establish the IPT schedule and commencement of IPT meetings not later than one month after the Inter-Organizational Contract Processes Familiarization Workshop (Section C, paragraph 3.3.2.1.3). The Contractor shall develop and distribute the agenda and IPT Presentation Packets prior to all IPT meetings in accordance with CDRL A012 – Presentation Material, adjust the agenda in response to Government feedback, and shall submit meeting minutes and action logs in accordance with CDRL A013 following each meeting. IPT meetings may be held via telephone.

3.3.2.2.1 CONTRACTOR IPT PARTICIPATION

The Contractor shall ensure appropriate Contractor personnel are in attendance or on telephone conferences with Government personnel to resolve and discuss ongoing progress, status, condition of GFE, and program issues. The Contractor shall adopt improved processes developed by these IPTs in a timely manner, react quickly to mitigate risk, increase efficiency through appropriate use of IPT products, and streamline management oversight.

3.3.2.3 FAULT ISOLATION TEAM (FIT)

In addition to the Contractor coordinated meetings identified in Section C, paragraph 3.3.2.2, the Contractor shall support the Government's Fault Isolation Team (FIT) weekly meetings to review failures or non-conformances on Contractor deliveries, score the non-conformances as either Contractor or Government responsibility, and provide disposition of previously submitted Contractor Failure Reporting, Analysis and Corrective Action (FRACA) reports and corrective action plans (CDRLs A003, A004, and A005) in accordance with Attachment 11 – Fault Isolation Process (Fault Isolation of Non-conformances). The Government will provide the information packages for this meeting. The FIT weekly meetings will be established after the successful completion of the TRR.

3.3.2.4 OTHER REPORTS

3.3.2.4.1 MINIMUM SUSTAINING QUANTITIES

The Contractor shall submit a Minimum Sustaining Rate (MSR) and Economic Order Quantity (EOQ) report in accordance with CDRL A017. The MSR and EOQ shall be prepared for the production of MK 54 LWT Common Parts Kits, exercise fuel tanks, MK 54 MOD 0 PGAs and W4 Cables. The MSR and EOQ reports provide the Government with vital information to be used for production and budget purposes to help manage procurements. The Contractor shall provide the MSR and EOQ report, which at a minimum, includes the following information:

a. Minimum Sustaining Rate - The production rate for each budget year that is necessary to keep production lines open while maintaining a base of responsive vendors and suppliers.

b. Economic Order Quantity - The maximum rate for each budget year at which the weapon system can be produced with existing or planned plant capacity and tooling, with one shift a day running for eight hours a day and five days a week.

c. Rationale as to how the numbers were calculated.

Submission of this information does not obligate the Government to order IAW rate or quantities submitted.

3.3.2.4.2 COST REPORTING

For the full value of firm fixed-price CLINs 0003, 0004, 0103, 0104, 0203, 0204, 0303, 0304, 0403, and 0404, the Contractor shall provide a CLIN cost report documenting the composition of costs associated with the performance within the scope of this contract in accordance with CDRL A006. Under CDRL A006, the Contractor shall segregate the cost report by CLIN and then by WBS elements. The WBS elements shall be mapped to show costs at the level of program management, system engineering, material, inspections, assembly (in-house), quality assurance (separate by major assemblies), and acceptance testing.

3.3.2.4.3 FUNCTIONAL COST HOUR REPORT

The Contractor shall submit Functional Cost Hour Report in accordance with CDRL A007 to report Contractor costs on CLINs 0003, 0004, 0103, 0104, 0203, 0204, 0303, 0304, 0403, and 0404.

3.3.2.4.4 PROGRESS CURVE REPORT

The Contractor shall submit Progress Curve Report in accordance with CDRL A007 for CLINs 0003, 0004, 0103, 0104, 0203, 0204, 0303, 0304, 0403, and 0404. Under CDRL A007, the Contractor shall further separate the units of CLINs 0003, 0004, 0103, 0104, 0203, 0204, 0303, 0304, 0403, and 0404 into the following groups: first ten (10) units, second ten (10) units, then lots of fourty (40) units, and planned attritions.

3.3.3 DATA MANAGEMENT

The Contractor shall submit a Data Accession List (DAL) in accordance with CDRL A019. The DAL shall identify all Contractor data that is not otherwise listed in the CDRLs, but has been generated by the Contractor in compliance with the work efforts prescribed in this contract. All data listed under the DAL shall be subject to Section I clauses 252.227-7026, "DEFERRED DELIVERY OF TECHNICAL DATA OR COMPUTER SOFTWARE," and 252.227-7027, "DEFERRED ORDERING OF TECHNICAL DATA OR COMPUTER SOFTWARE." If available, the Contractor shall maximize the development, storage and delivery of unclassified data products (including CDRLs) electronically, using the Government provided CMPro database. When CDRL item electronic delivery is not possible, the Contractor shall deliver the CDRL item using a Government created and controlled website.

3.3.3.1 DAL DOCUMENTATION

The Government will provide the Contractor access to a Government-created and controlled website and the Contractor shall upload electronic data to the website to enable Government personnel connected to the internet through NMCI network computers the ability to upload, download, read, copy, comment, and print the unclassified program documentation, models, and data. If necessary, the Contractor will be authorized Common Access Cards (CAC) for up to ten (10) personnel to allow for access to the required Government web based data systems.

3.3.3.2 DAL DELIVERY

All data obtained or created for the performance of this contract shall become and remain the property of the Government with the rights defined herein, and shall be returned or disposed of in accordance with the Contracting Officer's Representative's (COR) instructions at the conclusion of this contract.

3.3.3.3 FULL DISCLOSURE OF DESIGN

The Contractor shall provide full disclosure of design of the deliverable hardware procurement in accordance with DFARS 252.227-7013, 252.227-7014, and 252.227-7015. This disclosure shall be all-inclusive and the Government shall be authorized for distribution to other Contractors and/or vendors to support the MK 54 LWT system.

3.3.3.4 TECHNICAL DATA PACKAGE

The Contractor shall submit Technical Data Packages (TDP) in accordance with CDRL B001, CDRL B002, CDRL B003 or B004, as applicable. The Contractor shall submit the TDP for Government review and approval. The TDP shall consist of the product drawings, software and associated lists necessary for the design, engineering, manufacturing, inspection, packaging, quality assurance, in-service engineering, and logistics support of the MK 54 LWT Common Parts Kits as well as the MK 54 MOD 0 PGAs and W4 Cables (CLINs 0003, 0004, and associated options). The TDP shall conform to the requirements in the TDP Option Selection Worksheet in MIL-STD-31000A.

3.3.3.4.1 TDP PRODUCT DRAWINGS AND LISTS

TDP product drawings and associated lists shall include, but are not limited to, engineering drawings, related data and lists, and descriptive specifications. The information contained within the TDP shall describe the product design established at the Integrated Baseline Review (IBR) and include subsequent changes and revisions up to the time of the last submittal.

3.3.3.4.2 SOFTWARE/FIRMWARE DOCUMENTATION

The Contractor shall submit software/firmware documentation required to support software products imbedded in the components defined in the TDP for Government review and approval in accordance with the Exhibit B.

The Contractor shall submit, at a minimum, the following software documentation in accordance with CDRLs B001 and B002. Software includes the software portion of firmware.

a. Software Product Specifications (SPS)

b. Software Version Descriptions (SVD)

c. Software Requirement Specifications (SRS)

d. Critical Item Development Specifications (CIDS)

The Contractor shall submit, at a minimum, the following software in accordance with CDRLs B003 and B004. Software includes the software portion of firmware.

a. Board Support Packages (BSP)

b. Operating System (OS)

c. Source Code

d. Executable Files

e. Build Procedures

3.3.3.4.3 UPDATED TDP

For the base production year and each exercised option year production items (CLINs 0003, 0004, and associated options), the Contractor shall submit all new, newly revised, or revised data with all ECPs and NORs incorporated, in accordance with CDRL B001, CDRL B002, CDRL B003 or B004, as applicable.

Prior to the commencement of any base contract or option production year, the Contractor shall submit the updated baseline of hardware, firmware and software that is common to production deliverables for Government review and approval.

3.3.3.4.4 CHANGES TO TDP

Upon Production Readiness Review approval, the production…