DRAFT J.1 - DD 254.pdf

Please wait...

If this message is not eventually replaced by the proper contents of the document, your PDF viewer may not be able to display this type of document.

You can upgrade to the latest version of Adobe Reader for Windows®, Mac, or Linux® by visiting http://www.adobe.com/go/reader_download.

For more assistance with Adobe Reader visit http://www.adobe.com/go/acrreader.

Windows is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries. Mac is a trademark of Apple Inc., registered in the United States and other countries. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

UNCLASSIFIED

CONTINUATION – DD FORM 254 BLOCK 13

BIDDING 036-21

BLOCK 13 CONTINUATION STATEMENTS:

1. CLASSIFIED OR UNCLASSIFIED TECHNICAL PAPERS TO BE PRESENTED AT A CLASSIFIED

SYMPOSIUM MUST BE APPROVED BY THE NSWCDN CONTRACTING OFFICER'S

REPRESENTATIVE PRIOR TO THE PRESENTATION.

2. SECURITY CLASSIFICATION GUIDES (SCG’s) AND UNCLASSIFIED LIMITED DOCUMENTS

(E.G., FOUO, DISTRIBUTION STATEMENT CONTROLLED) ARE NOT AUTHORIZED

FOR PUBLIC RELEASE; THEREFORE, THEY CAN NOT BE POSTED ON A PUBLICLY

ACCESSIBLE WEB SERVER OR TRANSMITTED OVER THE INTERNET UNLESS

APPROPRIATELY ENCRYPTED. REQUEST FOR PUBLIC RELEASE CAN NOT BE

TRANSMITTED VIA THE INTERNET UNTIL THE CONTRACTOR RECEIVES FINAL

APPROVAL FROM THE COR.

3. ALL CONTRACTOR REQUESTS FOR SHARING OF CLASSIFIED AND OTHER SENSITIVE

INFORMATION BETWEEN PRIME CONTRACTS MUST BE FORWARDED IN WRITING TO THE

NSWCDL SECURITY OFFICE POC IDENTIFIED IN BLOCK 17 OF THIS FORM FOR APPROVAL.

4. PERSONNEL DESIGNATED AS DERIVATIVE CLASSIFIERS SHALL RECEIVE DERIVATIVE

CLASSIFICATION TRAINING PRIOR TO ACCESS FROM THE CONTRACTOR'S FACILITY

SECURITY OFFICER (FSO). THE FSO SHALL ENSURE PERSONNEL RECEIVE INITIAL AND

BIENNIAL TRAINING DURING THE LIFE OF THIS CONTRACT. EVIDENCE OF COMPLETION,

TRAINING CERTIFICATES OR EQUIVALENT, SHALL BE PROVIDED TO THE INFORMATION

ASSURANCE MANAGER NO LATER THAN THE INDIVIDUAL'S DUE DATE.

5. ALL CLASSIFIED DOCUMENTS MUST BE DESTROYED USING A NATIONAL SECURITY

AGENCY (NSA) APPROVED HIGH SECURITY CROSSCUT SHREDDER LISTED ON THE

NSA/CSS EVALUATED PRODUCTS LIST(EPL) FOR HIGH SECURITY CROSSCUT PAPER

SHREDDERS, OR OTHER APPROVED METHOD FOR DESTROYING CLASSIFIED

INFORMATION.

6. ALL CLASSIFIED INFORMATION INVOLVED IN SECURITY INCIDENTS SHALL BE RETAINED

AND PROVIDED TO THE CERTIFYING OFFICIAL IN ITEM 17 OF THIS DD 254 FOR

CLASSIFICATION REVIEW.

7. ALL SECURITY RELATED ISSUES, INCIDENTS, OR REQUESTS PERTAINING TO THIS

CONTRACT SHALL BE PRESENTED IN WRITING BY THE CONTRACTOR'S FACILITY

SECURITY OFFICER (FSO) TO THE INDIVIDUAL IDENTIFIED IN BLOCK 16(A) OF THIS

DD254. THE CONTRACTOR SHALL ABIDE BY OTHER REPORTING REQUIREMENTS

OUTLINED IN THE 32 CFR PART 117.

8. FORWARD A COPY OF SUBCONTRACTOR DD 254S ISSUED UNDER THIS CONTRACT TO

THE OFFICIAL SHOWN IN ITEM 16 OF THIS DD254.

CONTINUATION – DD FORM 254 ITEM 13

DODI 5200.48

SEPT 2021

CONTROLLED UNCLASSIFIED INFORMATION (CUI)

1. DEFINITION. CUI is defined as information that Government creates or possesses, or that an entity creates or possesses for or on behalf of the Government, that a law, regulation, or Government-wide policy requires or permits an agency to handle using safeguarding or dissemination controls. CUI does not include classified information.

2. ORGANIZATIONAL INDEX GROUPINGS (OIG) and CUI CATEGORIES: CUI consists of OIGs and their categories with marking guidance. Categories have definitions and legal authorities to help determine if information meets the criteria to be marked as CUI. A complete list of OIGs and categories are located at the National Archives and Records Administration (NARA) website https://www.archives.gov/cui/registry/category-list.

3. GENERAL GUIDANCE: Security Classification Guides (SCG) and documents marked as Controlled Unclassified Information (CUI), legacy For Official Use Only (FOUO), or Distribution Statements B thru F are not authorized for public release and cannot be placed on a publicly accessible web site or web server.

a. All contractors supporting an NSWCDD DNA contract will comply with the crawl, walk, run CUI implementation stages as determined by DUSN (I&S). NSWCDD DNA is currently in the crawl phase of CUI implementation. The crawl phase consist of the following marking requirements:

Mark emails containing CUI with CUI banner at the TOP and BOTTOM of the email.

Use Designation Indicator Block along with signature block or in place of signature block.

CUI contains Non-technical Information

CUI attachments in emails must have CUI) the filename: Filename_CUI.

All emails containing CUI must be digitally signed and encrypted.

FOR OFFICIAL USE ONLY (FOUO) is no longer an authorized marking for new documents and materials in the DOD.

During the crawl phase, paragraph or portion markings are optional but highly encouraged.

Controlled by: Department of the Navy

Controlled by: NSWCDD DNA, Code, Branch, Dept

CUI Category: OPSEC (example category)

Limited Dissemination Control: FEDCON

POC: Name & office phone of CONTRACTOR who authored

CUI contains Technical Information

Controlled by: Department of the Navy

Controlled by: NSWCDD DNA, Code, Branch, Dept

CUI Category: CTI

Distribution Statement::D

POC: Name & office phone of CONTRACTOR who authored https://www.archives.gov/cui/registry/category-list

CONTINUATION – DD FORM 254 ITEM 13

b. Controlled Technical Information (CTI): Dissemination of CTI will be controlled with Distribution Statement (B-F) in the Distribution/Dissemination Control line with CTI as the CUI Category.

i. All controlled technical data provided to the contractor by the government will be protected from public disclosure in accordance with the markings contained therein.

ii. Follow guidance for marking CTI in accordance with DODI 5230.24, Distribution Statements for Technical Documents.

c. Marking guidance for deliverables shall be provided by the owning government office in the form of:

iii. Security Classification Guidance

iv. Properly marked source document in the form of a:

i. Memorandum,

ii. Plan,

iii. Message document (Any physical medium in or on which information is recorded or stored, to include written or printed matter, audiovisual materials, and electromagnetic storage material.)

iv. Letter, or

v. Publication.

4. TRANSMITTAL. All emails containing such information or attachments must be appropriately marked, and digitally signed and encrypted if being transmitted within Navy networks, or outside a Navy network to an approved contractor email address. All transmissions to personal email accounts (AOL, Yahoo, Hotmail, Comcast, etc.) are prohibited.

5. OFFSITE HANDLING. The contractor shall provide adequate physical protection to such information as to preclude access by any person or entity not authorized such access by the government.

6. DISCLOSURE POLICY: All other information relating to the items to be delivered or services to be performed under this contract may not be disclosed by any means without prior approval of the authorized representative of the contracting officer. Dissemination or public disclosure includes, but is not limited to, permitting access to such information by foreign nationals or by any other person or entity; publication of technical or scientific papers; advertising; or any other proposed public release. Due to the sensitivity of this program, no classified or CUI material received or generated under this contract will be transferred to any other contractor or agency without the approval of the Contracting Officer or Contracting Officer’s Representative (COR).

Additional guidance can be found at DODI 5200.48.

V DEPARTMENT

CODE 10 / COMMAND

H DEPARTMENT

M DEPARTMENT

PLACE THIS NEAR YOUR TELEPHONE

For assistance with OPSEC contact your

Department Security Coordinator/OPSEC

Coordinator or the OPSEC Program Manager

COMMAND OPSEC PROGRAM MANAGER:

LAUREN MAPLES 540-653-7614

DEPARTMENT OPSEC COORDINATORS:

M/R/00/01/02 540-653-7385

A 540-284-0520

B 540-653-0044

E 540-653-2083

H 540-653-8912

V 540-653-6595

Dam Neck 757-492-6757

CRITICAL INFORMATION

& INDICATORS LIST

Proprietary and business sensitive information;

Specific details about missions, threats, gaps, vulnerabilities, requirements, or urgent needs that

NSWCDD supports or mitigates;

Information about capabilities, vulnerabilities, and limitations or information revealing a security weakness;

New, projected, or expanded secure communications capabilities;

Specific details about current or future exercises/operations;

Key personnel or very important person schedules and itinerary;

Information system and network capabilities and vulnerabilities;

Security measures and countermeasures taken to protect a system;

Combat System and Warfare System specifications/design details for all Surface Ship Combat Systems including AEGIS, Aegis BMD (ABMD), Ship Self Defense System (SSDS), FFG(X), Large Unmanned Surface Vehicle (LUSV), DDG 1000, Littoral

Combat Ships (LCS), and U.S. Coast Guard (USCG), including tactical and virtualized environments;

Baseline Development, Cost Analysis, Testing, Installation and Delivery Schedules of Surface Navy Combat Systems including AEGIS, ABMD, SSDS, FFG(X), LUSV, DDG 1000, USCG and LCS;

Development of netted, flexible, automated and rapid capabilities for the integrated combat system that will be nodes in the distributed maritime operations;

Warfare and Combat System capabilities or limitations;

Interoperability and Combat Control systems capabilities or limitations including concept and design , Shipboard

Gridlock System/Automatic Correlation, System Track

Manager/Track Server, Cooperative Engagement

Capability, Cryptologic Technician Network, Navigation and Ground Based Air Defense;

Information system/network capabilities and vulnerabilities;

Laboratory/test site locations, capabilities, operational and access requirements for the Integrated Warfare Systems Lab

Complex, and other Combat System support laboratory/test sites;

Security measures/countermeasures taken to protect a system;

Identification of special access elements within a program;

Specific Program Protection Plan implementations;

Combat system virtualization efforts, virtualization experimentation, and virtualization prototypes;

Combat system development for unmanned surface vessel prototyping

Battle management aid/tactical aids and mission planning tools for surface Navy.

Unique applications of Artificial Intelligence or Machine

Learning to combat systems

Details of counter-improvised explosive device projects commissioned by combatant commands, services, and agencies;

Battle Management System concept of operations;

capabilities; performance, and limitations;

TOMAHAWK, AEGIS Ballistic Missile Defense (BMD), AEGIS Weapons Control System, AN/SQQ-89, Computer Aided Dead Reckoning Tracer, Vertical

Launch Systems capabilities, limitations, vulnerabilities, degradations, test results, errors, problems, actual performance, fleet exercises, tactical operations, threats, missions, data and algorithms;

Association of specific projects with non-Navy sponsors, information identifying our non-Navy sponsors and stakeholders;

Locations and schedules of Navy ships, personnel deployment and outdoor testing facilities and

Correlation of project titles with development spaces and laboratories.

Information concerning specific mission analysis;

Specific details about missions, threats, gaps, vulnerabilities, requirements or urgent needs that

NSWCDD supports or mitigates;

Digital threat characterizations and traceability of the threat products;

Digital threat models used to develop threat assessment products;

Adversaries threats / weapons effectiveness and

TTP’s;

Surface Warfare models and simulation products;

Force analysis and warfare studies examining force structures and architectures to be utilized for investment decisions;

Mission-level and force-level capabilities and limitations;

Counter threat strategies.

UPDATED: SEP 2021

Association of abbreviations, acronyms, nicknames or code words with projects or locations designated as CUI;

Security operating procedures and emergency plans;

Physical security pitfalls related to physical security maintenance and improvement;

Deployment schedules, dates, and locations.

USING THIS CIIL

Refer to your department CIIL when writing for public release or releasing outside the DOD. This includes awards, academic papers, presentation slides, etc.

Refer to the CIIL when conducting business phone calls to ensure you do not inadvertently disclose critical information.

B DEPARTMENT

E DEPARTMENT

DAM NECK ACTIVITY:

R DEPARTMENT

A DEPARTMENT

UNCLASSIFIED UNCLASSIFIED UNCLASSIFIED

Re-entry systems trajectory details;

Re-entry systems material properties and fabrication methods;

Reentry systems vulnerabilities, degradations, limitations, problems, or errors in the system that could be exploited;

Submarine Launched Ballistic Missile/Submersible, Ship Guided Missile, Nuclear (SLBM/SSGN) vulnerabilities, degradations, limitations, problems or errors in the system that could be exploited;

SLBM/SSGN systems capabilities;

SLBM targeting capabilities;

Ship, submersible, ballistic, submarine guided nuclear ship schedules, deployment dates, and locations;

Plans and schedules associated with strategic targeting changes;

SLBM/SSGN facilities and capabilities;

Mean time between failures and mean time to repair values for maintenance plan;

Public network internet protocol addresses associated with combat system elements;

Combat system capabilities and limitations;

Deployment of capabilities upgrades and schedules for rapidly prototyped systems;

Technical details of support efforts for Department of Defense (DoD) and non-DoD infrastructures and networks;

Information concerning specific mission analysis;

Near Real Time and surge operations in response to natural and man-made events;

Infrastructure site assessment locations, and;

Nuclear Command and Control Recapitalization.

• Analysis of system performance, target capabilities or vulnerabilities;

Current system technological, organizational, or operational vulnerabilities;

Counter technology efforts;

Specific biological capability gaps and/or limits of protection associated with fielded or developing biological defense equipment and/or system technical design details;

• Scientific and technical or test and evaluation data for biological defense related research

Details of plans, programs, operations, test events and exercises, contracts, designs and milestones before approved public release;

Specific explosive experimental area capabilities and limitations;

Specific information related to Railgun and

Hypervelocity Projectile and associated testing;

Specific information relating to hypersonic technology, programs, and associated testing;

Contents of magazines;

Targets of interest, analysis of target capabilities or vulnerabilities;

Weapon’s effects and lethality on targets; tactics, techniques and procedures (TTP’s);

Unmanned aerial vehicle capabilities and detailed results of testing;

Specific frequencies of operations;

Waveform specifics; e.g. frequency and pulse width;

Power on target;

References to transitioning existing systems and their applications as a weapon system;

Electromagnetic interference measurement and ratings;

Specific information relating to laser technology, testing and high power microwave technology and testing;

Current system technological, organizational, or operation vulnerabilities and;

Counter technology efforts.

“It is said that if you know your enemies and know yourself, you can win a thousand battles without a single loss. If you only know yourself, but not your opponent, you may win or you may lose. If you know neither yourself nor your enemy, you will always endanger yourself.” ~Sun Tzu, The Art of War

Installation and delivery schedules of ships and submarines;

Research & development technical information:

new, projected or expanded technical capabilities, performance data, vulnerabilities and limitations for ships, subs, missiles, littoral mine warfare systems and integrated warfare systems;

Details of plans, programs, operations, test events, exercises, contracts, designs, and milestones before approved public release. Specific exercises will provide separate OPSEC lists if required;

Travel details of any kind revealing information which could impact Causality Reports or ship status;

Procurement of sensitive items or higher technology;

Maintenance and material support that could reveal sensitive projects;

Special codes assigned to platforms in association with other platform-specific information.

Indicators are detectable actions which point to vulnerabilities or critical information. They may seem insignificant to you but to an adversary they are small pieces of a much larger puzzle.

Specific frequencies of operation;

Targets of interest;

Test data, specifically effects on a target, to include no effect;

Specific power on target;

References to transitioning existing systems and their applications as a weapon system;

General system parameters;

Radar cross sections;

Electromagnetic interference measurement data, analysis results, predictions, and risk ratings;

Advanced technology applications;

Specific knowledge of targets tactics, techniques, and procedures;

Section C - Descriptions and Specifications

LINE ITEM DESCRIPTIONS

1.0 SCOPE

This Statement of Work (SOW) defines the effort required for production, assembly, inspection, testing, delivery, and sustainment of the AN/SPQ-14(V) Advanced Sensor Distribution System (ASDS) and AN/SPQ-15(V) Data

Distribution System (DDS) including variants. This effort also includes production of the AN/SPQ-15(V) DDS systems in accordance with the Technical Data Package (TDP), provided as Government Furnished Information

(GFI) and as referenced in Section J. 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 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 9 JUL 2004

NAVSEAINST 5000.8 Naval SYSCOM Risk Management Policy 21 JUL 2008

2.2 MILITARY STANDARDS

MIL-STD-130 IUID Markings Latest edition

MIL-STD-882E Department of Defense Standard Practice: System Safety 11 MAY 2012

2.3 DoD/DON REGULATIONS, DIRECTIVES AND INSTRUCTIONS

DODM 4160.28 DoD Demilitarization Manual 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

2 MAY 2016

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

2.6 NON-GOVERNMENT DOCUMENTS

IEEE/EIA Std 12207 Software Life Cycle Processes Latest edition

ASME Y14.24-2012 Types and Applications of Engineering Drawings 05 APR 2013

2.7 AVAILABILITY OF DOCUMENTS

Copies of military handbooks, instructions, standards and specifications and DoD adopted non-Government standards may be obtained in accordance with Federal Acquisition Regulation (FAR) Subpart 52.211-2. Copies of specifications, standards and data item descriptions cited in this solicitation, if listed in the DoD Index of

Specifications and Standards (DoDISS) or the Acquisition Management Systems and Data Requirements Control

List, DoD 5010.12-L (Dec 2003) may be obtained from:

ASSIST database via the Internet at (https://assist.daps.dla.mil/);

DoD issuances (http://www.dtic.mil/whs/directives);

DoN issuances (https://secnav.navy.mil/doni/default.aspx)

NSWCDD DNA documents are included in the TDP (Section 3.1.2) as Government Furnished Information (GFI)

Attachment J-2.

By submitting a request to the:

Department of Defense Single Stock Point (DoDSSP)

Building 4, Section D

700 Robbins Avenue

Philadelphia, PA 19111-5094

Naval Systems Data Support Activity (NSDSA) website at: (https://nsdsa2.phdnswc.navy.mil/)

Copies of non-Government publications, not listed in the DoDISS, may be obtained from the respective Industry association.

2.8 PRECEDENCE

In the event of conflict between the referenced documents herein and the contents of this SOW, the contents of this

SOW and any provided Government information, including TDPs, shall be considered the superseding requirement.

See Section C Clause FAR 52.215-8 Order of Preference.

2.9 CONTRACTOR DEVELOPED DATA

PEO IWS INST 4731.1 Combat Systems Stress & Endurance Test requirements

Latest edition

NAVSEAINST 9410.2A Combat System Certification Policy Latest Edition https://assist.daps.dla.mil/ http://www.dtic.mil/whs/directives https://secnav.navy.mil/doni/default.aspx https://nsdsa2.phdnswc.navy.mil/

2.9.1 CONTRACT DATA REQUIREMENTS LIST/STATEMENT OF WORK CROSSWALK

CDRL NUMBER CDRL TITLE SECTION OF SOW

GENERAL

A001 Conference Agenda 3.1.1, 3.2.4, 3.2.5, 3.3.2.1 & 3.2.2.3

A002 Conference Report 4.0

A003 Contracting Officer’s Management

Report

3.1.2, 3.1.3, 3.2.2, & 3.2.4

A004 Presentation Material 3.1.4, 3.2.4, 3.2.5 & 3.3.2.1

A005 Reports of Receipts, Inventory, Adjustment, and Shipments of

Government Property

3.1.4 & 3.1.9

A006 Report, Record of Meeting/Minutes 3.1.1, 3.1.4, 3.2.4, 3.2.5 & 3.3.2.1

A007 Revisions to Existing Government

Documents

3.8

A008 Technical Report – Study/Services 3.1.2, 3.1.3, 3.1.5, 3.1.8, 3.2.9, 3.2.2.3, 3.4.1, 3.6.2 & 3.6.3

A009 Trip/Travel Report 3.1.12 & 3.4.2

A00A Manufacturing Plan 3.1.3, 3.1.4, 3.1.6 & 3.2.9

A00B Integrated Master Schedule 3.1.3, 3.2.3

LOGISTICS/CM

A00C Bill of Materials for Logistics and

Supply Chain Risk Management

3.1.6 & 3.3.2.3

A00D Configuration Status Accounting

Information

3.1.5

A00E Engineering Change Proposal 3.1.5 & 3.2.10

A00F Logistics Product Data Summaries 3.1.3

A00G Notice of Revision 3.1.5

A00H Planned Maintenance System

Maintenance Index Page

A00J Planned Maintenance System

Maintenance Requirement Card

A00K Request for Waivers 3.1.5

A00L Logistics Product Data 3.3.1.2

A00M Packaging Plan 3.1.10, 3.3.1.2 & 3.3.3.3

SOFTWARE

A00N Computer Software Product 3.3.3.3, 3.6.1 & 3.6.3

A00P Software Design Description 3.6.1

A00Q Software Development Plan 3.6.1

A00R Software Product Specification 3.6.1

A00S Software Requirements

Specification

3.6.1

A00T Software Test Description 3.6.3

A00U Software Test Plan 3.6.3

A00V Software Test Report 3.6.3

A00W Software User Manual 3.8

A00X Software Version Description 3.6.1

TEST SUPPORT

A00Y Qualification Test Report 3.1.7.1, 3.3.2 & 3.3.2.2

A00Z Test/Inspection Report 3.1.7.1, 3.3.2.2 & 3.3.3.2

A010 Test Plan 3.1.7.1. 3.3.2.2 & 3.3.2.3

A011 Test Procedure 3.1.7.1 & 3.3.2.2

TECHNICAL

A012 Certification/Data Report 3.1.7.1

A013 Installation Control Drawings 3.2.6 & 3.8

A014 Interface Requirements

Specification

3.2.6

A015 Product Drawings/Models and

Associated Lists

3.2.6 & 3.8

A016 Request for Variance 3.1.5

A017 Technical Data Package 3.1.2

A018 Technical Manual Validation

Certificate

3.1.11 & 3.8

A019 Technical Manual Schedule and

Status Report

3.1.11

TRAINING/CIRRICULUM

DEVELOPMENT

A01A Instructional Performance

Requirements Document

A01B List of Faults Inserted for Training

Purposes

A01C Specification Change Notice 3.1.5

A01D Training Conduct Support

Document

A01E Technical Manual Research and

Analysis Source Data

3.1.11 & 3.8

A01F Interactive Electronic Technical

Manual Content Plan

3.1.11

A01G Scientific and Technical Reports 3.1.11

3.0 REQUIREMENTS

3.1 GENERAL REQUIREMENTS

Material & production deliveries along with services to be performed will be IAW 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 Navies. These services include: Hardware testing; Hardware modifications;

Logistic support; training development and support; Installation Support; and other various services delineated in the

CDRLs.

3.1.1 POST AWARD CONFERENCE

A post award conference shall take place no later than 15 days after award of the contract. The purpose of this conference is to review the initial production plans. The Contractor shall deliver a conference agenda no later than one (1) week before the date of the post award conference (CDRL A001). The Contractor shall deliver meeting minutes/actions no later than one (1) week after completion of the post award conference (CDRL A006).

3.1.2 TECHNICAL DATA PACKAGE

The Contractor shall support the maintenance of the TDP (initial baseline provided as Attachment J-2) 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 and provide Life-Cycle support AN/SPQ-15(V) 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. No further costs of design changes are authorized. No Contractor responsible design corrections are chargeable to any Engineering Support CLINs.

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 Government Purpose Rights for all data delivered under the TDP (CDRL A017).

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 within this SOW. Additionally the Manufacturing Plan documents methods by which the design is to be built. The Manufacturing Plan contains 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 develop and maintain an Integrated Master Schedule (IMS) as an Appendix to the

Manufacturing Plan (CDRL A00B). The IMS will track all Material Production as well as all services requested by the Government in the support of Material Production and System Installation support.

The Contractor shall generate, maintain, and execute the Risk Management Plan (RMP) as part of the

Manufacturing Plan. The Contractor shall implement and maintain a risk management program in accordance with the approved RMP to identify and manage risks associated with achievement of the program’s technical (including performance), cost, and schedule requirements. Risks shall be reported to the Government during Integrated Product

Teams (IPTs)/Working Groups (WGs) meetings as well as In-Progress Reviews (IPRs). NAVSEAINST 5000.8

(Naval SYSCOM Risk Management Policy), and Risk Management Guide for DoD Acquisition, Version 1.0, dated

August 2006, are available as guidance.

When directed by the COR the Contractor shall form IPTs and WGs to support an integrated product development process. The Contractor shall generate the organizational structure and document it in a Critical Program

Information report (CDRL A008). The Government will assign representatives to participate in IPT/WG meetings as necessary. Government participation will be coordinated through the COR.

The Contractor shall generate, as part of the manufacturing plan, a Quality Assurance (QA) Plan that the Contractor will implement and maintain. It will be an appendix to the Manufacturing Plan, which is integral to the overall production process. The QA Plan shall be comprised of management, technical resources, plans, procedures, schedules and controls necessary to ensure conformance to contractual requirements. The QA Plan shall address the requirements of ASQC Q9001. The QA Plan shall also address the software and firmware quality provisions of

Institute of Electrical and Electronics Engineers (IEEE) 12207. The software and firmware design, documentation and review process shall be in accordance with current standard business practices that represent the approved processes for the Software Engineering Institute (SEI) level IV. For validation of 3D Model Data, MIL-DTL-

31000C, Appendix C, is available for guidance.

The Contractor shall develop and deliver a System Safety Program Plan (SSPP) as an appendix to the Manufacturing plan and develop, establish and implement a System Safety Program using MIL-STD-882E as guidance. Hazards associated with production, operation, maintenance, and handling of the AN/SPQ-15(V) and associated equipment hardware and software shall be identified, reported, and eliminated. Hazards that cannot be eliminated shall be dispositioned to the satisfaction of the Government.

The Contractor shall report actual and potential safety hazards associated with equipment hardware and software program using a System Safety Hazard Analysis (SSHA) report (CDRLs A003 and A008). The Contractor shall track system safety issues in the Environmental Safety and Occupational Health database, identify processes and methodologies to mitigate these hazards and implement them within the program. The Contractor shall resolve all safety issues reported by the Government.

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 IPRs to review progress of the subsystem, software, system builds, integration and testing efforts. IPRs shall be scheduled 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 option exercise through delivery of final unit (CDRL A005). The reports shall include the production metrics identified in the Manufacturing Plan

(CDRL A00A). 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 radar.

3.1.5 CONFIGURATION MANAGEMENT

The Contractor shall generate and execute an AN/SPQ-15(V) and associated equipment 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 identify all hardware, software, and documentation issues. In addition, the Government, other

HP&S 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 PDM 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.

The Contractor shall participate in LCCB as requested.

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 (CDRLs A00A and A00C).

3.1.7 FACTORY ACCEPTANCE TESTING

3.1.7.1 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 will provide a Certification and Data Report to show where their personnel are qualified to produce and test the equipment and software they will make for the Government (CDRL A012).

The Contractor shall document the results of Factory Acceptance Testing including the as run, redlined, and marked up procedures in a Test Report (CDRL A00Y). 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 A00Z). 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 generate and execute a Diminishing Manufacturing Sources and Material Shortages (DMSMS)

Plan using DoD DMSMS Guidebook: A Guidebook of Best Practices for Implementing a Robust DMSMS

Management Program (SD-22A) as guidance (CDRL A008).

The Contractor shall conduct DMSMS Forecasting and propose solutions in Trouble Reports (CDRL A008).

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

(CDRL A008). 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).

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. Travel is not included. The warranty does not include or cover misuse or physical damages caused by third parties (CDRL A005).

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-14(V) ASDS, and the AN/SPQ-15(V) DDS configuration specific variants (CDRL A01E and/or

A051). The reutilization of existing source documentation will be used to the maximum extent for developing new, changes, and revisions to hard copy technical manuals, Electronic Technical Manuals (ETMs), and Interactive

Electronic Technical Manuals (IETMs). IETMs developed for new System level designs will be developed in a

Government approved format.

Prior to beginning the TM development, the Contractor shall provide the Government with the Electronic Data

Development Plan, Content Flow Maps, and Technical Manual Schedule and Status Report for hard copy TMs and

ETMs/IETMs (CDRLs A019, A01F and A01G). The Contractor shall conduct In-Process Review meetings to ensure TMs are developed in accordance with approved baseline configuration (CDRLs A01E and A01F). Both the

Contractor and Government shall have a combined Validation and Verification Review meeting for validating and verifying the TMs development 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.

Before beginning the IETM development, the Contractor will provide the Government the Electronic Data

Development Plan and the Technical Manual Schedule and Status Report (CDRLs A019 and A01F).

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

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. The Contractor shall update source documentation as appropriate to reflect current shipboard configurations (CDRL A018).

3.1.12 TRAVEL

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 PROGRESS, STATUS, AND MANAGEMENT REPORT

The Contractor shall generate a monthly Contractor’s Progress, Status and Management Report (CDRL A003). The

Contractor’s Progress, Status and Management Report shall contain the following:

a. Planned and actual staffing by IPT/WG;

b. Planned and actual material purchases;

c. Planned and actual use of Non-Developmental Items (NDI)/Non-Developmental Software (NDS); and

d. CDRLs submitted v. CDRLs accepted during reporting period;

3.2.3 INTEGRATED MASTER SCHEDULE

As part of the Monthly Reports, the Contractor shall generate and maintain an Integrated Master Schedule (IMS)

(CDRL A00B). The IMS shall identify all tasks from option exercised to completion. The IMS shall use the

Contract Work Breakdown Structure (CWBS) for tracing all work to be performed. The IMS shall identify the critical path, all major program events, and program milestones. The IMS shall identify all discrete work and clearly align with work packages and planning packages within control accounts. The Contractor shall document its IMS 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 IMS 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.

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 to five 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 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.