N0017822R2501-0001.pdf

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

To update Solicitation, based on Questions received from industry.

1. CONTRACT ID CODE PAGE OF PAGES

J 1 57

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

16C. DATE SIGNED

BY 12-Oct-2022

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 N0017822R2501

X 9B. DATED (SEE ITEM 11)

30-Aug-2022

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 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

07-Oct-2022

CODE

NSWCDD 3

ATTN: KIMBERLY CARTER/CODE 0252

KIM.CARTER@NAVY.MIL

17632 DAHLGREN ROAD STE 157

DAHLGREN VA 22448-5110

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N0017822R2501

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 30 - BLOCK 14 CONTINUATION PAGE

The following have been added by full text:

Amendment 1 reflects the following changes:

Section C:

FROM:

3.1.5 CONFIGURATION MANAGEMENT

The Contractor shall identify all hardware, software, and documentation issues. In addition, the Government, other Hardware Production & Sustainment Contractor, and Design Agent Contractor may identify and submit issues to the Contractor. For each issue identified, the Contractor shall generate a Technical Report and submit to the AN/SPQ- 15(V) LCCB via the Government’s Product Data Management system (CDRL A008). The Contractor shall categorize each Trouble Report using the following criteria.

TO:

3.1.5 CONFIGURATION MANAGEMENT

The Contractor shall identify all hardware, software, and documentation issues. For each issue identified, the Contractor shall generate a Technical Report and submit to the AN/SPQ-15(V) LCCB via the Government’s Product Data Management system (CDRL A008). The Contractor shall categorize each Trouble Report using the following criteria.

FROM:

3.1.7 FACTORY ACCEPTANCE TESTING

The Contractor shall provide all Test Data, evaluation tools (including simulations) and results to the Government for independent evaluation of performance (CDRL A00Z).

TO:

3.1.7 FACTORY ACCEPTANCE TESTING

The Contractor shall provide all Test Data, evaluation tools (including simulations) and results to the Government for independent evaluation of performance (CDRL A012).

Section J:

FROM:

Attachment J.2 – Government Furnished Information (GFI) List

04/05/2022 1

TO:

Attachment J.2 – Government Furnished Information (GFI) List Rev 1

10/05/2022 1

Section L:

FROM:

2.2 PROPOSAL FORMAT

(10) Minimum font size for both text and graphics shall be 10 point and font type shall be Times New Roman.

TO:

2.2 PROPOSAL FORMAT

(10) Minimum font size for text, not within excel, shall be 10 point and font type shall be Times New Roman.

FROM:

2.9 PAST PERFORMANCE (VOLUME IV)

The Offeror shall provide up to three (3) past performance references on contracts that were awarded and performance began within the past five (5) years from the closing date of solicitation that reflect relevant experience using the information requested below. The contracts identified should be relevant in that they are of similar scope and complexity to the effort in this solicitation and provide the most context and ability to measure whether the Offeror will successfully satisfy the current requirement. Common aspects for determining relevancy includes similarity of service/support (having performed most of the types of support efforts identified in the SOW), complexity (length of contract, extent of travel), dollar value, contract type, and extent of subcontracting. The identified contracts can be with Federal, commercial, or other customers. The Government reserves the right to limit or expand the number of references it decides to contact and to contact other references than those provided by the Offeror. Offerors are encouraged to supply past performance references information for which they are the Prime contract holder or provide detailed clarification to the extent of which they contributed as a Sub-contractor to the referenced contract.

TO:

2.9 PAST PERFORMANCE (VOLUME IV)

The Offeror shall provide up to three (3) past performance references on contracts that were awarded and performed within the past five (5) years from the closing date of solicitation that reflect relevant experience using the information requested below. The contracts identified should be relevant in that they are of similar scope and complexity to the effort in this solicitation and provide the most context and ability to measure whether the Offeror will successfully satisfy the current requirement. Common aspects for determining relevancy includes similarity of service/support (having performed most of the types of support efforts identified in the SOW), complexity (length of contract, extent of travel), dollar value, contract type, and extent of subcontracting. The identified contracts can be with Federal, commercial, or other customers. The Government reserves the right to limit or expand the number of references it decides to contact and to contact other references than those provided by the Offeror. Offerors are encouraged to supply past performance references information for which they are the Prime contract holder or provide detailed clarification to the extent of which they contributed as a Sub-contractor to the referenced contract.

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

STATEMENT OF WORK (SOW)

1.0 SCOPE

This Statement of Work (SOW) addresses the need for the procurement of hardware in support of the AN/SPQ- 15(V) Data Distribution System (DDS) programs. This hardware procurement will provide standard data and distribution systems from radar sensors to navigational and tactical displays, as well as durable and reliable state-of the-art equipment in accordance with the Technical Data Package (TDP), provided as Government Furnished Information (GFI) and as referenced in Section J. It also includes upgrades for existing AN/SPQ-14(V) Advanced Sensor Distribution System (ASDS) and DDS installations. The efforts defined by this SOW are in support of Hardware and Software production and sustainment.

The Contractor’s obligation to perform this contract is in no way conditioned upon the Government provision of any facilities, material, property, equipment, services, or information, except as may otherwise be explicitly provided herein.

1.1 BACKGROUND

Naval Surface Warfare Center Dahlgren Division Dam Neck Activity (NSWCDD DNA) is tasked by Naval Sea Systems Command (NAVSEA) Program Executive Office, Integrated Warfare Systems (PEO IWS 1.0) to provide supplies, engineering, technical, and logistical services associated with delivery, software design, development, improvement, enhancement, and technical support for the ASDS and DDS systems.

ASDS is the technology upgrade and Follow-on to AN/SPQ-12(V) Radar Display and Distribution System (RADDS) and is an evolutionary program for radar displays and switchboards dating back to World War II. The pre-RADDS equipment was first developed in the 1950-1960 period and has since been modified over time to include and incorporate technology advances.

The ASDS system was developed to fulfill the needs of the U.S. Coast Guard for a small radar video switchboard and Red-Green-Blue (RGB) switchboard combination. Although this upgrade was effective in meeting the needs of the U.S. Coast Guard, it required further enhancements to meet the U.S. Navy requirements of the Naval Amphibious Program for a common track picture between the Advanced Combat Direction System (ACDS) and installed radars. ASDS was enhanced to meet the high capacity distribution requirements of U.S. Navy Destroyers, Cruisers, Aircraft Carriers and Large Deck Amphibious platforms. Most recently, radar display and distribution has fully migrated into Open Architecture (OA) initiatives by using Local Area Network (LAN) technology. DDS is the OA evolution of ASDS.

2.0 APPLICABLE DOCUMENTS (Applicable to all CLINs)

The following documents, or the must current versions of these documents, are applicable to the tasks herein, and are for use by the Contractor as general guidance in the fulfillment of the SOW, as required.

2.1 MILITARY HANDBOOKS AND DoD GUIDANCE

MIL-DTL-31000C Technical Data Packages, Detail Specification Latest Edition MIL-HDBK-61B Configuration Management Guidance Latest Edition NAVSEAINST 5000.8 Naval SYSCOM Risk Management Policy Latest Edition

2.2 MILITARY STANDARDS

MIL-STD-130 Identification Marking of U.S Military Property Latest Edition MIL-STD-882E Department of Defense Standard Practice: System Safety Latest Edition

MIL-STD-167-1A Mechanical Vibrations of Shipboard Equipment (Type I - Environmental and Type II - Internally Excited) Latest Edition

MIL-STD-461G Requirements for the Control of Electromagnetic Interference Characteristics of Subsystems and Equipment Latest Edition

MIL-STD-464D Electromagnetic Environmental Effects Requirements for Systems Latest Edition

MIL-STD-810H(1) Environmental Engineering Considerations and Laboratory Tests Latest Edition

MIL-DTL-901E Shock Tests, H.I. (High-Impact) Shipboard Machinery, Equipment, and Systems, Requirements for Latest Edition

MIL-STD-1399-300-1 Department of Defense Interface Standard Section 300, Part 1 Low Voltage Electric Power, Alternating Current Latest Edition

MIL-STD-1399-300-2 Department of Defense Interface Standard Section 300, Part 2 Medium Voltage Electric Power, Alternating Current Latest Edition

MIL-STD-38784B General Style and Format Requirements for Technical Manuals Latest Edition

2.3 DoD/DON REGULATIONS, DIRECTIVES AND INSTRUCTIONS

DODM 4160.28 DoD Demilitarization Manual Latest Edition DoD Instruction 4140.67 DoD Counterfeit Prevention Policy Latest Edition DODD 8140.01 Cyberspace Workforce Management Latest Edition

2.4 SECNAV AND OPNAV INSTRUCTIONS AND MEMORANDA

SECNAVINST 5210.8D Records Management Latest Edition SECNAVINST 5239.3C Department of the Navy (DON) Cybersecurity Policy Latest Edition

COMUSFLTFORCOM/C

OMPACFLT

INSTRUCTION 6320.3A

Medical Screening for Personnel Prior to Embarking Fleet Vessels Latest Edition

NAVSUP P-409 NAVSUP Publication 409-MILSTRIP/MILSTRAP Desk Guide Latest Edition

2.5 NAVSEA AND PEO IWS, NSWCDD REGULATIONS, DIRECTIVES, AND INSTRUCTIONS

2.6 NON-GOVERNMENT DOCUMENTS

PEO IWS INST 4731.1 Combat Systems Stress & Endurance Test requirements Latest Edition NAVSEAINST 9410.2A Combat System Certification Policy Latest Edition

NAVSEA S0420-AA-

RAD-010 Radiological Affairs Support Program Manual Latest Edition

PEO IWS SEA 05 TRM

PEO IWS Naval Sea Systems Command Research & System Engineering Warfare Systems (SEA 05) Technical Review Manual

(TRM)

Latest Edition

TMCR NDMS-030057-

000 Interactive Electronic Technical Manual (IETM) for PEO 2RI 30 APR 2009

TMCR NDMS-090044-

000 Technical Manual Update Revision to IETMs for PEO IWS 2RI 30 APR 2009

N/A Electronic Technical Manual Operation Plan (ETMOP) for 2RI IETM Process (2RIIP) IETMs - Version 1.8 01 MAR 2011

IEEE/EIA Std. 12207 Software Life Cycle Processes Latest Edition ASME Y14.24-2012 Types and Applications of Engineering Drawings Latest Edition 455187E Marking Plan 29 JAN 2018

S1000D International Specification for Technical Publications Using a Common Source Database Latest Edition

ISO 9001:2015 Quality management systems — Requirements Latest Edition ISO/IEC 12207:2008 Systems and Software Engineering - Software Life Cycle Processes Latest Edition

2.7 RESERVED

2.8 DATA DELIVERABLES

CDRL NUMBER CDRL TITLE SUBTITLE SECTION OF SOW

A001 Conference Agenda N/A 3.1.1, 3.2.4, 3.2.5, 3.3.2.1 &

3.3.2.3 A002 Conference Report N/A 4.0 A003 Contracting Officer’s

Management Report N/A 3.1.2, 3.1.4, 3.2.2 & 3.2.4

A004 Presentation Material N/A 3.1.4, 3.2.4, 3.2.5 & 3.3.2.1 A005 Reports of Receipts, Inventory, Adjustment, and Shipments of Government Property

Government Property Report

4.4

A006 Report, Record of Meeting/Minutes

N/A 3.1.1, 3.1.4, 3.2.4, 3.2.5 & 3.3.2.1

A007 Revisions to Existing Government Documents

N/A 3.8

A008 Technical Report – Study/Services

Critical Program Report & DMSMS & Logistics Material Safety Data Sheets

3.1.2, 3.1.5, 3.3.2.3, 3.4.1,

3.6.2 & 3.6.3

A009 Trip/Travel Report N/A 3.1.12 & 3.4.2 A00A Manufacturing Plan Production Plan 3.1.3, 3.1.4, 3.2.3 & 3.2.9 A00B Manufacturing Plan Production Master

Schedule 3.1.3, 3.1.4, 3.2.3 & 3.2.9

A00C Bill of Materials for Logistics and Supply Chain Risk Management

N/A 3.1.6 & 3.3.2.3

A00D Configuration Status Accounting (CSA) Information

N/A 3.1.5

A00E Engineering Change Proposal (ECP)

N/A 3.1.5

A00F Logistics Product Data Summaries

Engineering Data for Provisioning

3.1.3

A00G Notice of Revision (NOR) N/A 3.1.5 A00H Planned Maintenance

System (PMS) Maintenance Index Page (MIP)

N/A 3.8

A00J Planned Maintenance System (PMS) Maintenance Requirement Card (MRC)

N/A 3.8

A00K Request for Waivers (RFW) N/A 3.1.5 A00L Logistics Product Data Provisioning Parts List 3.3.1.2

A00M Packaging Plan N/A 3.1.10, 3.3.1.2 & 3.3.3.3 A00N Computer Software Product N/A 3.3.3.3, 3.6.1 & 3.6.3 A00P Software Design Description

(SDD)

N/A 3.6.1

A00Q Software Development Plan

(SDP)

N/A 3.6.1

A00R Software Development Plan

(SDP)

Software Development Master Schedule

3.6.1

A00S Product Roadmap N/A 3.2.3 & 3.6.1 A00T Product Backlog N/A 3.2.3 & 3.6.1 A00U Software Product

Specification (SPS) N/A 3.6.1

A00V Software Requirements Specification (SRS)

N/A 3.6.1 & 3.6.3

A00W Software Test Description

(STD)

N/A 3.6.3

A00X Software Test Plan (STP) N/A 3.6.1 & 3.6.3 A00Y Software Test Report (STR) N/A 3.6.3 A00Z Software User Manual

(SUM)

N/A 3.1.7, 3.3.2.2 & 3.8

A010 Test Plan N/A 3.1.7, 3.3.2.2 & 3.3.2.3 A011 Test Procedure N/A 3.1.7 & 3.3.2.2 A012 Test/Inspection Report N/A 3.1.7, 3.3.2, 3.3.2.2 &

3.3.3.2 A013 Installation Control

Drawings (ICD) N/A 3.2.6 & 3.8

A014 Interface Requirement Specification (IRS)

N/A 3.2.6

A015 Product Drawings/Models and Associated Lists

N/A 3.1.11, 3.2.6 & 3.8

A016 Request for Variance (RFV) N/A 3.1.5 A017 Technical Data Package

(TDP)

TDP Maintenance 3.1.2

A018 Technical Manual Validation Certificate

Validation Certificate 3.1.11 & 3.8

A019 Technical Manual Schedule and Status Report

N/A 3.1.11

A01A Instructional Performance Requirements Document

N/A 3.8

A01B List of Faults Inserted for Training Purposes

N/A 3.8

A01C Specification Change Notice

(SCN)

Covers Overall System Support for All Changes

3.1.5

A01D Training Conduct Support Document

N/A 3.8

A01E Interactive Electronic Technical Manual (IETM) – New IETM

Source Data 3.1.11 & 3.8

A01F Interactive Electronic Technical Manual (IETM) Content Plan

Electronic Data Development Plan

3.1.11

A01G Scientific and Technical Reports

Content Flow Map 3.1.11

A01H Item Unique Identification

(IUID) Marking and Validation Report

N/A 3.2.10

A01J Item Unique Identification (IUID) Marking Plan

N/A 3.2.10

A01K Configuration Audit Plan N/A 3.3.2.3 A01L Interactive Electronic

Technical Manual (IETM) – Update Revision IETM

Source Data 3.1.11 &3.8

A01M Software Version Description (SVD)

N/A 3.6.1

A01N Qualification Test Report

(QTR)

N/A 3.1.7, 3.3.2 & 3.3.2.2

A01P Diminishing Manufacturing Sources and Material Shortages (DMSMS) Management Plan

N/A 3.1.8

A01Q Configuration Audit Summary Report and Certification

N/A 3.3.2.3

3.0 REQUIREMENTS

3.1 GENERAL REQUIREMENTS

Work to be performed and required deliverables shall be specifically described in individual Task Orders or Delivery Orders issued by the Contracting Officer and shall be within the parameters of one or more of the requirements described below.

Material and production deliveries along with services to be performed will be in accordance with the specifics of this contract. All production materials will be built/produced in accordance with the Technical Data Package and/or as directed by the Contracting Officer. Hardware to be furnished hereunder may consist of any individual item or group of individual items listed in Section B. The Contractor shall perform and successfully complete all necessary testing, including Factory Acceptance Testing (FAT), and evaluation of the system and equipment at the systems level, equipment level, and component level on contract production items to demonstrate that the procured items fulfill the requirements and specification of the contract.

Engineering and other services to be furnished hereunder will be for both the US Navy and Foreign Military Navy’s (International Program Support). These services include: hardware testing; hardware modifications; logistic support; training development and support; installation support; in-service software support/maintenance; and software development for future upgrades and future capabilities to the AN/SPQ-15(V).

3.1.1 POST AWARD CONFERENCE

A post award conference shall take place in accordance with C-242-H002 Post Award Meeting. The purpose of this conference is to review the initial production plans. The Contractor shall deliver a conference agenda before the date of the post award conference (CDRL A001). The Contractor shall deliver meeting minutes/actions after completion of the post award conference (CDRL A006).

3.1.2 TECHNICAL DATA PACKAGE

The Contractor shall support the maintenance of the Technical Data Package (TDP) in accordance with the configuration management processes in Section 3.1.5. The TDP will be maintained in the Integrated Data Environment (IDE). The TDP shall contain all data and information sufficient for a third party to manufacture

AN/SPQ-15(V), provide Life-Cycle support and associated equipment developed, qualified and maintained under this contract. The Contractor, as necessary, shall prepare and deliver an updated TDP describing in detail the as-built product baseline at a production level (Level 3) in accordance with MIL-DTL-31000C and ASME Y14.24.100- 2017. The TDP shall describe any and all subsequent changes to the baseline product including revisions up to the time of Government acceptance to reflect the final as-built configuration. Any required updates to the TDP for producibility and obsolescence shall be accounted for underneath the AN/SPQ-15(V) DDS and associated equipment production and sustainment CLINs. Changes to the TDP shall be processed in accordance with MIL- HDBK-61B. The Contractor shall not make any changes to the TDP without being directed by the Contracting Officer’s Representative.

The TDP shall include any software products, including source code necessary for diagnostic and troubleshooting purposes and source code for any other software and firmware developed for the DDS. Unless otherwise noted, the Government shall have at a minimum Government Purpose Rights (as defined in DFARS 252.227-7013 and DFARS 252.227-7014) for all data delivered under the TDP (CDRL A017). Rights in Technical Data and Computer Software shall be consistent with the applicable clauses of this contract.

When needed, new drawings and new associated lists shall be developed and structured in accordance with ASME Y14.24-2012. The TDP shall contain digital photographic images of assembly procedures and cable dressing techniques provided coincident with the development of configurations supported, interface control information for hardware and software changes. When updates to the TDP are necessary, the Contractor shall incrementally deliver each completed TDP element to the Government via the Contracting Officer’s Representative (COR) (CDRLs A003, A008, and A017).

The Contractor shall verify the TDP at least 30 days prior to any required Physical Configuration Audit (PCA).

3.1.3 PLAN EXECUTION

The Contractor shall generate, maintain, and execute the Manufacturing Plan (CDRL A00A). The Manufacturing Plan shall address manufacturing efforts to include the Production Master Schedule (CDRL A00B) within this SOW. Additionally the Manufacturing Plan documents methods by which the design is to be built. The Manufacturing Plan contains the sequence and schedule of events at Contractor and Sub-contractor levels that define use of materials, fabrications flow, test equipment, tools, facilities, and personnel. It reflects consideration and incorporation of manufacturing requirements in the design process and includes identification and assessment of design facilities. For systems and components that are designed to higher Evaluated Assurance Levels (EALs), the Manufacturing Plan identifies the physical and personnel controls needed in the manufacturing process to meet Cyber requirements.

The Contractor shall form IPTs and WGs to support an integrated product development process. The Contractor shall generate the organizational structure of these IPTs and WGs and make the documentation available to the Government upon request. The Government will assign representatives to participate in IPT/WG meetings as necessary. Government participation will be coordinated through the COR.

The Contractor will provide Engineering Data that is used for provisioning to the Government (CDRL A00F).

3.1.4 PRODUCTION PROGRESS

The Contractor shall conduct In-Process Reviews (IPRs) to review progress of the subsystem, software, system builds, integration and testing efforts. IPRs shall be scheduled no less than quarterly. The first IPR shall address readiness of manufacturing processes, quality systems, and production planning. The Contractor shall host the IPRs, and coordinate meetings with the Government. The Contractor shall coordinate and deliver Meeting Agendas (CDRL A006). The Contractor shall deliver Presentation Materials and Minutes/Action Items to the Government (CDRLs A004 and A006).

The Contractor shall generate a Production Status Report for the period from contract award through delivery of final unit (CDRL A003). The reports shall include the production metrics identified in the Manufacturing Plan

(CDRLs A00A and A00B). The reports shall address production metrics, including components procured, assembled and tested. The reports shall address labor efforts and facility utilization. The reports shall address material efforts, including procurement, inventory, expenditures, and quality control data. The Contractor shall provide a consistent format for the reporting of metrics for the IPR.

3.1.5 CONFIGURATION MANAGEMENT

The Contractor shall generate and execute an AN/SPQ-15(V) and associated equipment configuration management plan and give monthly accounting of the material manufactured, delivered and planned in the form of a Configuration Status Accounting report (CDRL A00D).

The Government will provide the Contractor its Configuration Management Plan, which the Contractor will use for all of the Hardware, Software, and documentation it will produce. The Government will conduct the AN/SPQ- 15(V) Local Configuration Control Board (LCCB), PEO IWS 1.0 LCCB, and Integrated Combat System (ICS) Change Control Board (CCB). The Contractor shall participate as a non-voting member in the LCCB as requested.

The Contractor shall identify all hardware, software, and documentation issues. For each issue identified, the Contractor shall generate a Technical Report and submit to the AN/SPQ-15(V) LCCB via the Government’s Product Data Management system (CDRL A008). The Contractor shall categorize each Trouble Report using the following criteria.

Priority Definition 1 Prevents the accomplishment of an essential capability, jeopardize safety, security or other requirement designated critical.

2 Adversely affects accomplishment of an essential capability and no workaround exists; adversely affects technical, cost, or schedule risks to the project or to Life-Cycle support of the system and no work around solution is known.

3 Adversely affects accomplishment of an essential capability, but reasonable workaround solution is known; adversely impacts functions supporting an essential capability; adversely affects effectiveness, technical, cost, or schedule risks to the project or to Life-Cycle support of the system, but a reasonable workaround solution is known.

4 Results in user/operator inconvenience or annoyance but does not affect a required operational or mission-essential capability; results in inconvenience or annoyance for operational or maintenance personnel but does not prevent the accomplishment of the responsibilities of those personnel.

5 Any other effect

The Government will have approval authority over all Trouble Report (TR) categorizations.

The Contractor shall correct all issues associated with Trouble Reports. The Contractor shall conduct sufficient regression testing to ensure that any changes made appropriately correct the issues without introducing additional issues.

The Contractor shall update and submit Trouble Reports with the proposed corrective actions, proposed schedule, and associated cost estimates to the AN/SPQ-15(V) LCCB for approval and determination of required change documentation. The Contractor shall generate the approved change documentation. Change documentation includes, but is not limited to Engineering Change Proposals (ECPs), Requests for Variances (RFVs), Request for Waiver (RFWs), Notice of Revisions (NORs) and/or Specification Change Notices (SCNs) (CDRLs A00E, A00G, A00K, A016, and A01C).

The above change documentation shall be submitted to the Government. In addition, all updated TDP materials shall be submitted to the Government in accordance with the LCCB approved change documentation. At all times, the Government shall manage the official product baseline for production and sustainment.

The AN/SPQ-15(V) LCCB will have approval authority of Class II ECPs, Minor (Request for Deviations (RFDs), Request for Waivers (RFWs), Notice of Revisions (NORs), and Specification Change Notice. The AN/SPQ-15(V)

LCCB will review and recommend approval/disapproval of Class I ECPs and Major/Critical RFD/RFWs to the PEO IWS 1.0 LCCB. The PEO IWS 1.0 LCCB will have approval authority of Class I ECPs and Major/Critical RFD/RFWs. Approval of formal Class I ECPs, if any, will be accomplished via the changes clause of the Contract.

3.1.5.1 TRADE STUDIES AND ANALYSIS

Prior to submission of a Class I ECP, the Contractor, if directed by the COR, shall perform trade studies and analysis. These efforts will include cost estimates, scope estimates, technical investigations, Industry surveys, and technical trade-off studies. All results of such trade studies and analysis shall be delivered as detailed in the Configuration Management Plan.

3.1.6 AS-BUILT CONFIGURATION BILL OF MATERIAL LIST

The Contractor shall generate an As-Built Configuration (ABC) Bill of Material (BOM) List in accordance with the manufacturing plan annex for each the AN/SPQ-15(V) production unit, subsystems, and parts reflecting the delivered AN/SPQ-15(V) production unit hardware, software, and parts (CDRL A00C).

3.1.7 FACTORY ACCEPTANCE TESTING

The Contractor shall generate the Factory Acceptance Test Plan and Procedures (CDRLs A010, and A011). The Original Equipment Manufacturer (OEM) Plan and Procedures and the TDP are available as guidance. The Contractor shall conduct Factory Acceptance Testing on each AN/SPQ-15(V) Unit in accordance with Contractor-developed, Government-approved Acceptance Test Plan and Procedures.

The Contractor shall document the results of Factory Acceptance Testing including the as run, redlined, and marked up procedures in a Qualification Test Report (CDRL A01N, CDRL A012 and CDRL A010). Any marked up procedures shall be reflected in updated Acceptance Test Procedures.

The Contractor shall provide all Test Data, evaluation tools (including simulations) and results to the Government for independent evaluation of performance (CDRL A012). The Contractor shall notify the Government of planned test events no later than 21 calendar days prior to testing to support Government participation. The Contractor shall notify the Government of any changes to planned test events no later than seven (7) calendar days before the test. In the event that the Government is not able to witness a test that requires Government attendance and/or approval, the test shall be rescheduled as soon as possible. The Contractor shall conduct meetings to review test results with the Government.

3.1.8 DIMINISHING MANUFACTURING SOURCES AND MATERIAL SHORTAGES

The Contractor shall support and resolve all Lowest Replaceable Unit (LRU), subassembly, or piece part Diminishing Manufacturing Sources/Material Shortages (obsolescence) issues necessary to execute the requirements of this contract.

The Contractor shall conduct DMSMS Forecasting and propose solutions in Trouble Reports. Proposed solutions shall include analysis of alternatives and impacts to both production and sustainment. In addition, the Contractor shall generate DMSMS Forecast Source Data and Report as part of the trouble report. Summaries of DMSMS Trouble Reports, data and reports shall be reported at IPRs. The Source Data for Forecasting DMSMS shall reference parts, part numbers, and drawing numbers based upon the TDP (as defined in Section 3.1.2). The Contractor shall deliver a DMSMS Management Plan to document their DMSMS Management approach (CDRL A01N).

3.1.9 WARRANTIES AND LICENSES

All equipment and material delivered under this contract shall be warranted for 18 months with the warranty period starting from the date of equipment/material Government acceptance at no additional cost to the Government. The warranty will cover labor and replacement parts for assemblies that have experienced failures due to parts or workmanship. Repairs will be performed at the Contractor’s facility. Shipping charges will be covered by the

Contractor. The warranty does not include or cover misuse or physical damages caused by third parties.

3.1.10 PACKAGING, HANDLING, STORAGE AND TRANSPORTATION

The Contractor shall establish a Packaging, Handling, Storage and Transportation (PHS&T) program for the AN/SPQ-15(V) system equipment, subsystems and parts developed under this contract. This PHS&T program shall be planned, developed, and maintained to deliver the AN/SPQ-15(V) systems equipment free-from-damage. The PHS&T program shall be consistent with the AN/SPQ-15(V) equipment principal component marking, reliability, maintainability, safety, and human factors. This plan will be submitted to the Government for approval before first product production.

The Contractor shall generate the AN/SPQ-15(V) principal component PHS&T procedures and elements that conform to MIL-STD-2073/1E and meet the requirements of Section D (Packaging and Marking) and be in accordance with best commercial practices. Unique or special packaging, handling, storage or transportation requirements shall be identified and reported in a PHS&T impact analysis report.

Applicable PHS&T requirements, PHS&T equipment designs, and procedures shall be documented in the hard copy TM and ETM/IETM source data, TDP and provisioning data.

The Contractor shall update the PHS&T impact analysis report as required to support changes to the AN/SPQ-15(V) equipment implemented during production (CDRL A00M).

3.1.11 TECHNICAL MANUALS

The Contractor shall develop and maintain new and existing operation and maintenance technical manuals (TMs) for the AN/SPQ-15(V) DDS configuration specific variants in accordance with CDRLs A01E and A01L. The reutilization of existing source documentation will be used to the maximum extent for developing new and revisions to AN/SPQ-15(V) Interactive Electronic Technical Manuals (IETMs). TMs developed for new System level designs will be developed in accordance with new Technical Manual Contract Requirements (TMCR), S1000D, or other approved specifications.

Prior to beginning the TM development, the Contractor shall provide the Government with the Electronic Data Development Plan (CDRL A01F), Content Flow Map (CDRL A01G), and Technical Manual Schedule and Status Report (CDRL A019) for TMs/IETMs. The Contractor shall conduct In-Process Review meetings in accordance with CDRLs A01E and A01L to ensure TMs are developed in accordance with approved baseline configurations.

Both the Contractor and Government shall have a combined Validation and Verification Review meeting for validating and verifying the TM maintenance procedural data, troubleshooting fault logic diagrams, parts, and engineering drawing data against the hardware system. The Contractor will maintain the Comment Sheet Master Copy for recording discrepancies found during the Validation and Verification review and for taking corrective action.

The Contractor shall certify the TM is adequate, accurate, and complete. The Contractor shall provide the Government with a Technical Manual Validation Certificate (CDRL A018) for final TM delivery.

The Contractor shall update source documentation as appropriate to reflect current shipboard configurations. The Contractor shall provide CDRL A018 certifying the adequacy, accuracy, and completeness of the TM revision.

Tasks shall be initiated as a result of Fleet feedback, Technical Manual Deficiency Evaluation Report, failure analyses, engineered process improvements, system installation activities, software updates, or Government direction.

3.1.12 TRAVEL (CLIN 0200)

All travel under this contract must be authorized by the COR in writing prior to travel and must show the number of people traveling, the number of days for the trip, and the reason for the travel. The Contractor is not authorized to perform any travel that is not in conjunction with this effort. Travel costs shall be in accordance with FAR 31.205-

46. The Contractor shall submit trip reports following any travel under this effort (CDRL A009).

Planned travel is provided in the following chart.

Number of Trips Number of People Duration (Days) Destination 8 3 5 San Diego, CA 7 3 10 Norfolk, VA 5 3 5 Moorestown, NJ 7 3 5 Wallops Island, VA 5 3 5 Pascagoula, MS 3 3 5 Clearwater, FL 3 3 14 Yokosuka, Japan 3 3 14 Okpo, South Korea 2 3 14 Gaeta, Italy 5 3 5 Washington, DC 3 3 5 Norway 3 3 5 Rota, Spain

If applicable, Status of Forces Agreement (SOFA) will be incorporated.

3.2 PROGRAM MANAGEMENT

3.2.1 PROGRAM MANAGEMENT SUPPORT

The Contractor shall assign a Program Manager (PM) who shall have complete responsibility for the planning, execution, control and reporting of all aspects of the program, and for directing in-house and Sub-contractor efforts.

The PM shall ensure that all requirements are applicable to the components/parts as specified herein for all items procured. The PM shall ensure that Sub-contractors, suppliers or vendors procedures are compliant with all SOW requirements. The PM shall be an employee of the Prime Contractor.

3.2.2 CONTRACTING OFFICER’S MANAGEMENT REPORT

The Contractor shall generate a Contracting Officer’s Management Report (CDRL A003). The Contracting Officer’s Management Report shall contain the following:

(a) Planned and Actual Staffing

(b) Planned and Actual Material Purchases

(c) Planned and Actual use of Non-developmental Items (NDI) and Non-developmental software, and

(d) CDRLs submitted/accepted

3.2.3 INTEGRATED MASTER SCHEDULE

The Contractor shall generate and maintain a Manufacturing Plan to include a Production Plan (CDRL A00A) and as part of the Monthly Reports, a Production Master Schedule (CDRL A00B), which is to be tailored to reflect the items section 3.6.1 of the data item description. The Production Master Schedule shall identify all tasks from contract award to completion. The Production Master Schedule shall use the Contract Work Breakdown Structure (CWBS) for tracing all work to be performed. The production schedule shall identify the critical path, all major program events, and program milestones. It shall also identify all discrete work and clearly align with work packages and planning packages within control accounts. The Contractor shall document its Production Master Schedule at the lowest level of the CWBS. The Contractor shall quantify risk in hours, days, or weeks of delay and provide optimistic, pessimistic, and most likely durations for each Production Master Schedule activity and event that meets the following criteria: (1) critical path tasks/activities, (2) near-critical path tasks/activities, (3) high risk tasks/activities in the program’s risk management plan. For software development efforts, the Product Roadmap (CDRL A00S) shall describe the planned, iterative software releases and the software planning schedule, and the Product Backlog (CDRL A00T) shall describe the requirements baseline for software development.

3.2.4 INTEGRATED BASELINE REVIEW

The Contractor shall conduct an Integrated Baseline Review (IBR) to demonstrate the Contractor’s plan to achieve program requirements within cost and schedule constraints. The Contractor shall propose the review (scheduling, location, security requirements, Agenda ((CDRL A001) and content), subject to Government approval. The IBR shall be conducted once a fiscal year for the duration of this contract. The review will be two (2) to five (5) work days in length. The Contractor shall send read ahead material and Presentation Material, to the Government preceding each review (CDRL A004). The IBR Presentation Material shall include some or all of the following:

Process Documentation; Contract Award and Modifications; Subcontract SOWs & CDRLs List; Basis of Estimates (BOE); Work Authorization Documents; Organizational Breakdown Structure; Responsibility Assignment Matrix;

Monthly Report (CDRL A003) (at least two (2) Periods); Bill Of Materials (BOM); and Current Risk Management Database Listing. The Contractor shall place final Presentation Materials on the Government IDE following the reviews. The Contractor shall prepare Minutes/Actions to include a database to capture and manage all Government and Contractor Action Items (CDRL A006). The database shall reside on the Government IDE. The Contractor shall update Action Item status including closure plans weekly. At the IBR, the Contractor shall present the phased work schedule and planned resources, and approaches for conducting the work on this contract. IBR(s) shall also be conducted on Subcontracts that meet or exceed $20 million. The prime Contractor shall lead the Sub-contractor IBRs with active participation by the Government. Following the IBR(s), the Contractor shall baseline the Monthly Report. The Government may hold additional IBRs at the program’s discretion.

3.2.5 PROGRAM MANAGEMENT REVIEWS

The Contractor shall conduct Program Management Reviews (PMRs) quarterly in-person and/or virtually to provide Government insight into program cost, schedule, technical, and outstanding issues.

The Contractor shall propose all reviews (scheduling, location, security requirements, Agenda (CDRL A001) and content), subject to Government approval. The Contractor shall send read ahead material and presentations to the Government preceding the PMRs (CDRL A004). The Contractor shall send final Presentation Materials to the Government following the PMRs. The Contractor shall maintain a database to capture all Government and Contractor Minutes/Action Items from the PMRs (CDRL A006). The Contractor shall update Action Item status including closure plans monthly or as requested.

3.2.6 DATA MANAGEMENT

The routine use and generation of classified information is not anticipated in this contract. The Contractor shall implement data management procedures to ensure complete and timely flow of data deliverables and track document versions, clearly identifying document changes/additions. Specific data deliverables formats and distributions are listed in the CDRLs. Proper export control and distribution statements shall be clearly stated in the data deliverables and adhered to by the Contractor and any Sub-contractors.

When changes to the baseline are made, the Contractor shall provide those changes via the following CDRLs.

Changes to the baseline Material and Software of the system, the Contractor shall provide updated Installation Control Drawings (CDRL A013). Changes to the Hardware and Software Configuration Items as well as system components and operating procedures. The Contractor shall provide those Interface Requirement Changes (CDRL A014).

When any new equipment, parts or components are designed in support of the system, the Contractor shall provide the Product Drawing/Models and associated lists that provide detail on that new equipment and part components

(CDRL A015).

Deliverables shall be clearly marked as to any restrictions on the Government’s use/dissemination with supporting rationale for restrictions. Restrictions on data shall also be identified and reported at all meetings. When data, software, or software documentation contains data with less than unlimited rights to the Government, only the cover and the specific portions of the document shall be marked with appropriate markings and tied directly to items on the lists required by DFARS 252.227-7017 and/or 252.227-7028 within the contract. The Contractor shall not mark an entire document (e.g., presentation materials, trade studies, etc.) as restricted unless every page of the document contains restricted data.

3.2.7 INTEGRATED DIGITAL ENVIRONMENT

The Government will maintain all data via its own Configuration Management (CM) Plan. The Government will ensure that the Contractor is provided all of the material/data that it requires.

3.2.8 INTERNATIONAL TRAFFIC IN ARMS REGULATIONS AND EXPORT ADMINISTRATION

REGULATIONS

The Contractor shall be solely responsible for obtaining any State Department approvals, licenses, Technical Assistance Agreements (TAA), etc. required by the International Traffic in Arms Regulations (ITAR) and Export Administration Regulations (EAR) and must obtain specific written authorization from the Procuring Contracting Officer (PCO), COR, or NSWCDD Security Manager before exercising those approvals or licenses.

3.2.9 COUNTERFEIT PARTS AND MATERIALS MANAGEMENT

The Contractor shall provide a Counterfeit Prevention Plan as a part of its Manufacturing Plan (CDRLs A00A and A00B) that documents procedures to minimize the risk of procuring and/or using counterfeit parts and materials.

This plan shall be in accordance with DFARS 252.246-7007 Contractor Counterfeit Electronic Part Detection and Avoidance System.

Society of Automotive Engineering (SAE AS5553) contains information regarding the detection, avoidance, and mitigation of counterfeit electronic components, and may be used as a reference document for CDRL submission.

DoD Instruction 4140.67, DoD Counterfeit Prevention Policy, latest edition, contains information regarding the detection, avoidance, and mitigation of counterfeit electronic components, and may be used as a reference document for meeting the above steps.

3.2.10 ITEM UNIQUE IDENTIFICATION MARKING

The Contractor shall implement an Item Unique Identification (IUID) Marking Plan (CDRL A01J) utilizing the existing Marking Plan for the AN/SPQ-15(V) Data Distribution System. The Contractor shall apply the IUID marking on each AN/SPQ-15(V) assembly in accordance with DFARS 252.211-7003. Internal parts and subassemblies, unless designated as a LRU, are not required to have IUID marking. IUID pedigree data for LRUs embedded in Unit level assemblies shall be entered into the IUID Registry as children to the parent Unit. LRU’s procured as spares shall not have a parent-child relationship. The Contractor shall:

• Utilize MIL-STD-130 Series for IUID marking.

• Deliver preliminary UID Marking Plan (CDRLA01J) and IUID Marking and Verification Report (CDRL

A01H).

• Deliver final IUID Plan (CDRL A01J).

• Deliver final IUID Marking and Verification Report (CDRL A01H). Report shall provide the data resulting from IUID marking activities for all qualifying items manufactured on this contract. Data shall be available for inspection by the PCO or other Government representative at any time during the life of this contract.

The markings shall contain data qualifier, data syntax, construct and semantics, as outlined in MIL-STD-130 Series, and utilizing the IUID as the common data point for the marking of LRUs and enclosures.

3.3 PRODUCTION REQUIREMENTS

3.3.1 FIRST ARTICLE AN/SPQ-15(V) PRODUCTION UNITS (CLINs 1001-1014)

3.3.1.1 PRODUCTION

The Contractor shall build the AN/SPQ-15(V) Production Units that meet all requirements of the TDP (as defined in Section 3.1.2).

3.3.1.2 DELIVERY

The Contractor shall deliver the AN/SPQ-15(V) Production Units in accordance with Section F. In support of delivery, the Contractor shall use Special Packaging Instructions (CDRL A00M). The Contractor shall update the Special Packaging Instructions using the Logistics Product Data (CDRL A00L).

3.3.2 FIRST ARTICLE TESTING

First Article Qualification Testing (FAQT) is conducted to verify specification compliance and validate the factory acceptance testing. FAQT shall be conducted on the first production units that are changed from the original build to print configuration due to a configuration change. The Contractor shall submit the First Article Test report using the test report (CDRL A01N and CDRL A012).

The Contractor may request a waiver for performing the First Article Testing.

3.3.2.1 TEST READINESS REVIEW

The Contractor shall conduct a Test Readiness Review (TRR) prior to execution of FAQT. Within FAQT, multiple test periods may be conducted. The TRR shall also cover both FAQT and Factory Acceptance Testing. Prior to each test period, the Contractor shall conduct a Test Event Review (TER). The TRR is conducted to ensure that the component/subsystem/system under review is mature enough to proceed into the major test cycle (i.e., FAQT). The TER is conducted to focus on the subset of tests identified for an individual test period. At the TRR and TERs, the Contractor shall review planned test objectives, methods, procedures and statistical analyses and examine lower-level test results, test plans, test objectives, test methods and procedures to verify the traceability of planned tests to program requirements and ensure that required test resources have been properly identified and coordinated.

The Contractor shall propose all reviews (scheduling, location, security requirements, Agenda (CDRL A001) and content), subject to Government approval. The content of the TRRs is defined in the PEO IWS Naval Sea Systems Command Research & System Engineering Warfare Systems (SEA 05) Technical Review Manual (TRM). The entry and exit criteria for TRRs is defined in the TRM. The Contractor shall host the TRR and TERs, and coordinate with the Government. The Contractor shall coordinate and send the Meeting Agenda to the Government prior to the TRR. The Contractor shall send Presentation Materials and Minutes/Actions to the Government (CDRL A004 and A006). The Contractor shall capture all Government and Contractor Action Items from the TRRs (CDRL A006).

The Contractor shall update Action Item status, including closure plans, at least monthly and as requested.

3.3.2.2 TESTING

The Contractor shall generate the FAQT Plan and Procedures (CDRL A010). The OEM Plan and Procedures and the TDP are available as guidance. The Contractor shall conduct FAQT on the First Article in accordance with Contractor-developed, Government approved FAQT Plan and Procedures. The Contractor shall document the results of FAQT including the as run, redlined, and marked up procedures in a Test Report (CDRL A01N, A012)). Any marked up procedures shall be reflected in updated FAQT Procedures.

The Contractor shall provide all Test Data, evaluation tools (including simulations) and results to the Government for independent evaluation of performance. The Contractor shall notify the Government of planned test events no later than 15 calendar days prior to testing to support Government participation.