Attachment J1 DD254.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

BIDDING 010-22

CONTINUATION – DD FORM 254 ITEM 13

ADDITIONAL SECURITY GUIDELINES FOR COMSEC

Contractor Generated COMSEC Material: Any material generated by the contractor (including but not limited to: correspondence, drawings, models, mockups, photograph, schematics, status programs and special inspection reports, engineering notes, computation and training aids) will be classified according to its own content. Classification guidance will be taken from other elements of this Contract Security Classification Specification, DD Form 254, Government furnished equipment or data, or special instructions issued by the Contracting Officer, or his/her duly appointed representative.

REQUIREMENTS

1. Contractor employees or cleared commercial carriers shall not carry classified COMSEC material on commercial passenger aircraft anywhere in the world without the approval of the procuring contracting officer.

2. No contractor generated or government furnished material may be provided to the Defense Technical Information Center (DTIC).

Contractor generated technical reports will bear the statement “Not Releasable to the Defense Technical Information Center per DOD Directive 5100-38.”

3. Classified paper COMSEC material may be destroyed by burning, pulping or pulverizing. When a method other than burning is used, all residues must be reduced to pieces 5 mm or smaller in any dimension. When classified COMSEC material other than paper is to be destroyed, specific guidance must be obtained from the User Agency.

4. The following Downgrading and Declassification notation applies to all classified COMSEC information provided to and generated by the contractor:

DERIVED FROM: NSA/CSS Classification Guide, dated 30 Sep 2013, revised 23 May 2014 DECLASSIFY ON: (calculate declassification date that is 25 years from the date of the source) DATE OF SOURCE: (Date of document from which information is derived)

5. All contractor personnel to be granted access to classified COMSEC information must be U.S. citizens granted FINAL clearance by the government prior to being given access. Immigrant aliens, interim cleared personnel, or personnel holding a contractor granted CONFIDENTIAL clearance are not eligible for access to classified COMSEC information released or generated under this contract without the express permission of the Director, NSA.

6. Unclassified COMSEC information released or generated under this contract shall be restricted in its dissemination to personnel involved in the contract. Release in open literature or exhibition of such information without the express written permission of the Director, NSA, is strictly prohibited.

7. Recipients of COMSEC information under this contract may not release information to subcontractors without permission of the User Agency.

8. The requirements of NSA/CSS Policy Manual 3-16, dated 23 January 2015 are applicable to this effort.

9. Additional notices to be affixed to the cover and title or first page of contractor generated COMSEC documents:

a. “COMSEC MATERIAL – ACCESS BY CONTRACTOR PERSONNEL RESTRICTED TO U.S. CITIZENS HOLDING A FINAL

GOVERNMENT CLEARANCE.”

b. “THIS PUBLICATION OR INFORMATION IT CONTAINS MAY NOT BE RELEASED TO FOREIGN NATIONALS WITHOUT PRIOR SPECIFIC APPROVAL FROM THE DIRECTOR, NSA. ALL APPROVALS WILL IDENTIFY THE SPECIFIC INFORMATION AND COPIES OF THIS PUBLICATION AUTHORIZED FOR RELEASE TO SPECIFIC FOREIGN HOLDERS. ALL REQUESTS FOR ADDITIONAL

ISSUANCES MUST RECEIVE PRIOR SPECIFIC APPROVAL FROM THE DIRECTOR, NSA.”

CONTINUATION – DD FORM 254 BLOCK 13

BLOCK 13 CONTINUATION STATEMENTS:

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

CLASSIFIED SYMPOSIUM MUST BE APPROVED BY THE NSWCDD 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 CANNOT 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 NSWCDD 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.

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 contract will comply with the crawl, walk, run CUI implementation stages as determined by DUSN (I&S). NSWCDD 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, 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, 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

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;

C.1 INTRODUCTION

The Naval Surface Warfare Center, Dahlgren Division (NSWCDD), Unmanned & Expeditionary Weapon Systems

Division (H40), actively supports the U.S. Navy, United States Special Operations Command (USSOCOM), Department of Defense (DOD), Department of Homeland Security (DHS), and Department of Justice (DOJ) agencies by providing design and fabrication, rapid prototyping, and rapid technology insertion. This is accomplished through rigorous systems engineering research, design, development, and analysis applied to Joint

Fires and Land Attack Command, Control, Communications, Computers, Intelligence, Surveillance and

Reconnaissance (C4ISR), time critical targeting, space technology, satellite tracking systems and global positioning systems applications.

Recent support activities applicable to this SOW include the Battle Management Systems (BMS), Assault

Amphibious Vehicle (AAV) projects, manned and unmanned platform integration and robotic systems, weapon control systems development, and all future states of these programs and technologies. Required tasking shall be provided in further detail with specific individual Delivery Orders. Delivery Orders will consist of Firm Fixed Price

(FFP) and Cost-Plus-Fixed-Fee (CPFF) type orders. CPFF orders will be for level of effort and completion type tasks.

C.2 APPLICABLE DOCUMENTS AND STANDARDS

Open Architecture (OA) - The Contractor shall develop and maintain an architecture that incorporates appropriate considerations for re-configurability, portability, maintainability, technology insertion, vendor independence, reusability, scalability, interoperability, upgradeability, and long-term supportability as defined in the OA Contract

Guidebook (https://acc.dau.mil/NOAGuidebook).

Other applicable standards, practices and procedures related to the design, construction and material selection for deliverable prototypes include the following:

AFSC DH 1-6 System Safety

SAE-AS50881 Aerospace Standards, Wiring Aerospace Vehicle

IPC J-STD-001 Space and Military Applications Electronic Hardware Addendum to IPC J-STD-001H, Requirements for Soldered Electrical and Electronic Assemblies

IPC-A-610E Acceptability of Electronic Assemblies

IPC/WHMA-A-620A Requirements & Acceptance for Cable & Wire Harness Assemblies

MIL-HDBK-454 General Guidelines for Electronic Equipment

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

MIL-STD-188-220 (series) Interface Standard for Digital Message Transfer Device (DMDT Subsystems)

MIL-STD-461 Requirements for the Control of Electromagnetic Interference Characteristics of Subsystems and

Equipment

MIL-STD-464 Electromagnetic Environmental Effects Requirements for Systems

MIL-STD-704 Department of Defense Interface Standard, Aircraft Electric Power Characteristics

MIL-STD-810 Department of Defense (DoD) Test Method Standard for Environmental Engineering

Considerations and Laboratory Tests

MIL-STD-882 System Safety Program Requirements

MIL-STD-1553 Digital Time Division Command/Response Multiplex Data Bus

MIL-STD-1587 Material and Process Requirements for Aerospace Weapons Systems

MIL-STD-1760 Department of Defense Interface Standards for Aircraft/Store Electrical Interconnection System

MIL-STD-1791 Designing for Internal Aerial Delivery in Fixed Wing Aircraft

Circuit cards shall be fully populated and built to IPC 610 Class 2 level and inspected to IPC A-600 Class 2.

Printed Circuit Board (PCB) surface shall be Hot Air Surface Leveled (HASL), as called out in Gerber files.

For cabling, IPC 620 shall include AS50881, MIL-STD-1310, 461, 464, 704.

Specific versions of standards, handbooks, and applicable interface documentation will be articulated in individual

Delivery Orders for the respective prototype deliverables.

Drawings shall be in accordance with ANSI/ASME applicable standards and practices with specific tailoring provided in individual Delivery Orders.

Technical Data Packages (TDP) shall be of sufficient quality to enable prototype reproduction by qualified vendors.

As a minimum, per MIL-STD-31000, TDP quality shall be Level II (Developmental) with Level III (Production) aspects as specified in individual Delivery Orders.

Copies of Government specifications, standards, handbooks and guidance data listed above may be obtained from:

http://assist.daps.dla.mil/online/start/

C.3 SCOPE

The primary focus of this contract shall be delivery of tactical systems to the warfighter. The purpose of this requirement is to provide prototype development, hardware fabrication, hardware and software for hardware prototype or prototype higher volume units and kits, and project management. Specifically, the Contractor shall provide engineering design, development, and testing. Additionally, the Contractor shall provide drawing development, bill of material development, fabrication, design analysis, and manufacturability analysis.

C.4 REQUIREMENTS

C.4.1 PROTOTYPE DEVELOPMENT

C.4.1.1 The Contractor shall provide prototype development, which includes all or any portion of the hardware and software development cycle, up to and including the development of a complete prototype system. Prior to commencement of prototype development, the Government will provide the detailed specifications for each required prototype. Components of the prototype development cycle include concept development, requirements collection, system design, systems engineering, material specification development, material acquisition, environmental resiliency design, prototype development, prototype testing, systems integration, systems testing, and systems functional demonstration based on performance requirements as documented in individual Delivery Orders.

The desired prototypes consist of both hardware and software components including weapons controls system software, command and fire control software, control box assemblies, training panel assemblies, cables, printed wiring assemblies, antennas, customized testing equipment, enclosures, and electronic racks that physically support the hardware which will be mounted in a variety of aircraft, ships, and vehicles.

C.4.1.2 Each prototype system developed, tested, and maintained shall be part of a comprehensive package, including all associated software source files, software libraries, hardware design tool outputs (e.g., 3D hardware models, assemblies, parts, drawings, bills of materials, etc.), circuit board design tool outputs (e.g., Altium Designer project, Gerber files, bills of materials, etc.) along with related test procedures and user/maintainer documentation.

Prototype development, enhancements, testing, and maintenance deliverables will be identified in individual

Delivery Orders. (CDRL A007)

C.4.1.3 The Contractor shall provide deliverable documentation such as technical specifications and Requirement

Traceability Matrixes (RTM), which list and describe all requirements for the prototype system, status on whether the current version meets those requirements, and the assigned priority for each requirement. The RTM shall document requirements currently met, those expected to be met in the current version, and any deferred requirements to facilitate project completion tracking. Specific deliverable documentation will be defined in individual Delivery Orders. Additional requirements may be solicited after each subsequent version of the prototype and documented via revisions to technical specifications as directed by individual Delivery Orders and change requests as approved by the Government.

The intent of the production drawings is to convey sufficient information and detail to move the prototype assembly into subsequent initial outfitting. The Contractor shall initially release the data package to the Government with the delivery of the first article system with incremental baseline updated releases to be delivered throughout the development and prototype pre-production effort based on Government approved change requests and Engineering

Change Notices (ECN). Once a prototype stabilizes and can move into full production, the prototype will be competitively procured under a separate Firm Fixed Price (FFP) Delivery Order.

C.4.1.4 The Contractor shall conduct testing. Delivery Orders will define all testing requirements to be conducted for the qualification of fabricated assemblies. The Delivery Orders will define responsibility (Contractor, Government or joint) for development and execution of Acceptance Test Procedures (ATP) and Hardware

Certification Test (HCT). In more mature designs, the Government will be able to provide these types of tests to the

Contractor. In earlier stages of TDP development, the Contractor will not be given these types of tests.

C.4.1.5 It is the Government’s intention that all prototypes and associated intellectual property developed under this contract be delivered with a minimum of Government Purpose Rights; no Contractor proprietary hardware or software may be used without the advance concurrence of the Contracting Officer’s Representative (COR) and

Contracting Officer. The Contractor shall identify and document proprietary hardware and software components used in the prototype pre-production of the hardware and software systems prior to integration.

C.4.1.6 The Contractor shall attend meetings with other Contractors and Government agencies but in no way shall represent the Government.

C.4.1.7 The Contractor shall conduct pre-development and development efforts by scheduling, coordinating, and participating in team meetings, recommending process improvements, assisting in managing agendas, and facilitating topic closures, and recording Government decisions/actions. The Contractor shall attend briefings and meetings, draft detailed notes and action items, and compose and distribute minutes documenting action items, discussions, and decisions reached. The Contractor shall in no way represent the Government in these meetings.

(CDRL A002, A003)

C.4.1.8 The Contractor shall identify long lead time parts or parts that appear to becoming end-of-life (obsolete) during the rapid prototyping phases. The purpose of this is so that the Government can order these parts sooner than the production Delivery Orders or do lifetime buys, and provide them as Government Furnished Material (GFM) for future Delivery Orders. After the issuance of a Delivery Order, the Contractor shall procure long lead time part hardware and kits for specified systems. (CDRL A009)

C.4.1.9 The Contractor shall provide organizational development, performance improvement, strategic planning, and risk assessment. The Contractor shall maintain a risk tracking database and provide risk status reporting with the

Monthly Progress Report. The Contractor shall identify cost saving measures for each Delivery Order and shall document the cost savings plan in the Monthly Progress Report. (CDRL A001, A009)

C.4.1.10 At the Government’s discretion, onsite hardware efforts may be required of Contractor personnel with specific skill sets. Onsite locations are considered to be at NSWCDD. For on-site support, the Contractor shall design and integrate hardware and software systems, integrate configuration management and workflow tools, trouble shoot hardware and software systems, disassemble and assemble hardware and hardware kits, add new components to hardware or hardware kits, customize equipment, machine equipment, package and ship items, develop drawings and specification, conduct other activities associated with successfully deploying hardware prototype or prototype pre- production units and kits, and perform joint ATPs and other quality control measures.

(CDRL A007, A009, A00A)

C.4.1.11 The Contractor shall conduct hardware and software efforts at the Contractor’s facilities including engineering design and integration of hardware and software systems, integration and support of configuration management and workflow tools, trouble shooting of hardware, disassembly and assembly of hardware and hardware kits, adding new components to hardware or hardware kits, customizing equipment, machining equipment, packaging, shipping, drawing and specification development, and other activities associated with successfully deploying hardware prototype or prototype pre-production units and kits. This support shall include fabrication and machining of replacement parts or equipment for fielded systems or platforms. (CDRL A007, A009, A00A)

C.4.2 HARDWARE FABRICATION

C.4.2.1 The Contractor shall provide hardware fabrication, which includes any portion of the hardware cycle, up to and including fabrication of complete systems or series of complete pre-production systems. The fabricated systems will be used for extensive testing in laboratories, at test sites, and as deployed units in theater. The delivery schedule and quantity of systems to be produced will be specified in individual Delivery Orders. The Delivery Orders may be revised by the Government to update the delivery schedule and quantities to meet emergent Government objectives, to include quick reaction operational requirements.

The hardware fabrication cycle includes material specification development, hardware component identification and selection, material acquisition, material staging, material tracking, fabrication, machining, assembly, quality control, testing, certification, packaging and shipping. Hardware components or hardware systems fabricated shall consist of a complete package, which includes all associated documentation.

C.4.2.2 The Contractor shall utilize complete set of prototype production models and drawings approved by the

Government for each fabrication run.

C.4.2.3 Changes during fabrication may be initiated by either the Government or the Contractor. Changes initiated by the Contractor must be approved, in writing, by the Government prior to implementation. The Contractor shall document all changes during fabrication as revisions on all the impacted drawings and associated documentation, and all changes shall be accompanied by a formal Change Request. The Change Request shall detail any changes, including the initiator and approver of the change, the reason for the change, the resulting impact of the change, and the change date. For hardware design changes, the Contractor shall document the changes to the hardware data package via Engineering Change Notices (ECN). The ECN package shall include full red-line markups of the affected drawings for formal review and approval by the Government prior to implementation in to the baseline.

(CDRL A004, A007, A008, A00B, A00D)

C.4.2.4 The Contractor shall manufacture and deliver test tools used for Acceptance Testing. A Government owned

TDP will be developed and sent to the Contractor for the fabrication of their own test tools. The Contractor shall use these tools for testing at their facilities to ensure that the Government and Contractor are using the same test procedures. These tools shall be tracked in the Government Furnished Property Reports (CDRL A00E).

C.4.2.5 The Contractor shall apply an item unique identifier (IUID) based on MIL-STD-130 (construct 2) latest version, to all units. The IUID shall include the cage code of the design activity, the cage code of the manufacturer, the part number and the serial number and additional written information, as may be designated by the Government.

C.5 ACCEPTANCE CRITERIA

C.5.1 The Contractor shall conduct a Government approved Factory Acceptance Test (FAT) for all first article prototype deliverables. The Contractor shall document in the FAT all electrical, mechanical and visual inspections and all system functional test and demonstrations necessary to verify that each prototype meets the requirements of the SOW for the respective Delivery Order. The Contractor shall provide the FAT procedure to the Government for review (CDRL A005). After approval by the Government, the FAT shall be placed under Contractor configuration control. Any revision to the FAT shall require Government approval. The FAT shall:

Identify how each functional and performance characteristics shall be demonstrated or tested;

Identify measurable parameters by acceptable operating limits and use measured results to record performance metrics; and

Identify special tools and test equipment required for performing the FAT.

C.5.2 The Contractor shall generate and submit a FAT report for each first article prototype deliverable (CDRL

A006). The FAT report shall include, as appended material, any lower level test, vendor tests or vendor certifications. The FAT report shall include an indentured As-Built Configuration List (ABCL) down to the Lowest

Replaceable Unit (LRU) level. The indentured ABCL shall identify drawing numbers, revision levels, serial numbers, and any applicable Engineering Change Proposals (ECP) or configuration variances.

C.5.3 Subsequent prototype deliverables shall pass a Government developed and conducted Acceptance Test

Plan/Procedure (ATP) or Test Procedure (TPROC) prior to official acceptance.

C.6 NON-RECURRING ENGINEERING AND REPAIRS

C.6.1 The Contractor shall make upgrades and enhancements to systems test and tactical equipment. During rapid fielding of systems, the Contractor shall make specific last minute, Government approved, changes to systems. In this case, the Government will submit over to the Contractor a revised TDP for upgraded systems.

C.6.2 The Contractor shall make repairs to products produced under this requirement. Repair items shall include tactical and testing equipment. This process includes the Government sending the repairable units back to the

Contractor, along with a Work Order with the Government’s findings. These units either come back from the field or rigorous testing events. The Contractor shall make the necessary repairs, deliver the unit back to the Government, and submit analysis reports and repair reports (CDRL A009, A00C). Specific reports for each requirement will be called out in the Delivery Orders.

C.7 GOVERNMENT FURNISHED EQUIPMENT (GFE) AND GOVERNMENT FURNISHED

INFORMATION (GFI)

C.7.1 The Government will provide incidental items as required by the Contractor for integration and testing of prototype deliverables. These deliverables shall successfully pass the FAT before delivery to the Government.

Specific GFE will be identified in individual Delivery Orders for the respective prototype deliverables.

C.7.2 The Government may provide drawings and interface documentation based upon the level of platform integration. If required, this information will be provided in individual Delivery Orders.

C.8 PROGRESS REPORTING, DELIVERABLES, AND OTHER CONTRACT MANAGEMENT

C.8.1 Monthly Progress Report

The Contractor shall provide Monthly Progress Reports (CDRL A001).

C.8.2 Task Prioritization Meeting

The Contractor shall participate in periodic Task Prioritization Meetings with the COR and project/work area/Delivery Order points-of-contact. The purpose of these meetings is to convey the Government’s technical program schedules and priorities, and to identify corresponding project priorities. It is anticipated that these meetings shall occur on a weekly basis (CDRL A002). The Contractor shall provide a Weekly Status Report to convey the status of current activities, and the results of these meetings shall also be reported in the Weekly Status

Report (CDRL A004). If necessary, schedule adjustments will be made via Delivery Order modifications.

C.8.3 Technical Interchange Meeting (TIM)

The Contractor shall participate in TIMs as required to support kicking off new requirements, or to support more complex emerging rapid prototyping requirements. All TIMs shall be approved by the COR. (CDRL A002, A003)

C.8.4 Location of Meetings and Reviews

Meetings and reviews may be held at Government or Contractor sites, as coordinated and approved by the COR. In addition, the Contractor shall have the ability to host web enabled and teleconference meetings to reduce travel cost and improve the effectiveness of Government/Contractor meetings.

C.9 MANDATORY REQUIREMENTS

The following mandatory requirements shall be maintained throughout the life of this contract.

Requirement 1: Facility location:

The Offeror’s primary facility providing support under this contract must be located within 200 miles of NSWCDD, Dahlgren, VA.

Requirement 2: Facility Security Clearance:

The contractor’s primary facility for supporting this contract is required to have a facility clearance of SECRET and must be cleared at the SECRET level for both information processing and storage at the time of proposal submission.

Requirement 3: Personnel Security Clearances:

All personnel providing support under this requirement must possess clearances at the SECRET level or higher with the exception of manufacturing and administrative personnel. Interim clearances are acceptable for all clearance levels.

Requirement 4: Certifications

The Offeror’s manufacturing facilities must be ISO 9001:2015 and AS9100D certified. These certifications must be for the following process areas: Configuration Management, Project Planning, Project Management and Control, Supplier Agreement Management, Product and Process Quality Assurance, Requirement Management &

Development, Risk Management, Verification, and Validation.

C.10 DIGITAL DELIVERY OF DATA

(a) Delivery by the Contractor to the Government of certain technical data and other information is now frequently required to be made in digital form rather than in hardcopy form. The method of delivery of such data and/or other information (i.e., in electronic, digital, paper hardcopy, or other form) shall not be deemed to affect in any way either the identity of the information (i.e., as “technical data” or “computer software”) or the Government’s and the

Contractor’s respective rights therein.

(b) Whenever technical data and/or computer software deliverables required by this contract are to be delivered in digital form, any authorized, required, or permitted markings relating to the Government’s rights in and to such technical data and/or computer software must also be digitally included as part of the deliverable and on or in the same medium used to deliver the technical data and/or software. Such markings must be clearly associated with the corresponding technical data and/or computer software to which the markings relate and must be included in such a way that the marking(s) appear in human-readable form when the technical data and/or software is accessed and/or used. Such markings must also be applied in conspicuous human-readable form on a visible portion of any physical medium used to effect delivery of the technical data and/or computer software. Nothing in this paragraph shall replace or relieve the Contractor’s obligations with respect to requirements for marking technical data and/or computer software that are imposed by other applicable clauses such as, where applicable and without limitation, DFARS 252.227-7013 and/or DFARS 252.227-7014.

(c) Digital delivery means (such as but not limited to Internet tools, websites, shared networks, and the like) sometimes require, as a condition for access to and/or use of the means, an agreement by a user to certain terms, agreements, or other restrictions such as but not limited to “Terms of Use,” licenses, or other restrictions intended to be applicable to the information being delivered via the digital delivery means. The Contractor expressly acknowledges that, with respect to deliverables made according to this contract, no such terms, agreements, or other restrictions shall be applicable to or enforceable with respect to such deliverables unless such terms, agreements, or other restrictions expressly have been accepted in writing by the Contracting Officer; otherwise, the Government’s rights in and to such deliverables shall be governed exclusively by the terms of the contract.

C.11 SECURITY

C.11.1 All personnel providing support under this requirement must possess clearances at the SECRET level or higher with the exception of manufacturing and administrative personnel. Interim clearances are acceptable for all clearance levels. The Contractor will have access to information and compartments with a SECRET classification.

All deliverables associated with this contract are unclassified unless otherwise specified. Access to classified spaces and material and generation of classified material shall be in accordance with the attached DD Form 254. The

Department of Defense Contract Security Classification Specification (DD Form 254) provides the security classification requirements for this contract. The Contractor shall obtain facility and personnel security clearances as required by the Department of Industrial Security Program prior to starting to work on tasks requiring clearances.

Access to classified spaces and material and generation of classified material shall be in accordance with 32 Code of

Federal Regulation (CRF) Part 117and the NSWCDD Command Security Manual. All data generated under this contract shall be classified in accordance with the guidance in the 32 CFR Part 117 and the NSWCDD Command

Security Manual. The Contractor must comply with guidelines specified on the DD254.

C.11.2 Controlled Unclassified Information (CUI) to include For Official Use Only (FOUO) and Personally

Identifiable Information (PII) generated and/or provided under this contract shall be safeguarded and marked as specified in DoD 5400.7-R Chapters 3 and 4. The Contractor will receive and generate classified material in accordance with the Security Classification Guidance specified on the DD-254. The Contractor will fabricate, modify or store classified hardware (circuit boards with firmware, laptop computers, etc…) but will not exceed the two cubic feet storage limit as specified in NISS. The Contractor shall require access to Communications Security

(COMSEC) in order to use crypto keying material. A COMSEC account is required in order to receive COMSEC material to include equipment and keying material.

C.11.3 Facility Clearance: The Contractor shall possess and maintain a SECRET (s) facility clearance as verified within the National Industrial Security System (NISS).

C.11.4 Physical Security: The Contractor shall be responsible for safeguarding all Government information or property provided for Contractor use. At the end of each work period, Government information, facilities, equipment and materials shall be secured as specified by the NISPOM and the NSWCDD Command Security

Manual. SECRET storage is required at the Contractor’s facility in order to meet requirements of receiving and generating classified material in accordance with this contract.

C.11.5 Electronic Spillages (ES) are unacceptable and pose a risk to national security. An electronic spillage is defined as classified data placed on an information system (IS), media or hardcopy document possessing insufficient security controls to protect the data at the required classification level, thus posing a risk to national security (e.g., sensitive compartmented information (SCI) onto collateral, Secret onto Unclassified, etc). The Contractor’s performance as it relates to ES will be evaluated by the Government. ES reflects on the overall security posture of

NSWCDD and a lack of attention to detail with regard to the handling of classified information of IS security discipline and will be reflected in the Contractor's performance rating. In the event that a Contractor is determined to be responsible for an ES, all direct and indirect costs incurred by the Government for ES remediation will be charged to the Contractor.

C.11.6 NSWCDD Security will continue to be responsible for the corrective action plan in accordance with the security guidance reflected on the DOD Contract Security Classification Specification - DD254. NSWCDD

Security will identify the Contractor facility and contract number associated with all electronic spillages during the investigation that involve Contractor support. NSWCDD Security will notify the Contracts Division with the

Contractor facility name and contract number, incident specifics and associated costs for cleanup. The Contracting

Officer will be responsible to work with the Contractor Facility to capture the costs incurred during the spillage clean up. The Contractor is also responsible for taking Information Security Awareness training annually, via their

Facility Security Officer (FSO), as part of the mandatory training requirements. If a spillage occurs additional training will be required to prevent recurrence.

C.11.7 Portable Electronic Devices (PEDs)

C.11.7.1 Non-government and/or personally owned portable electronic devices (PEDs) are prohibited in all

NSWCDD buildings with the exception of personally owned cell phones which are authorized for use in spaces up to and including Controlled Access Areas. The Contractor shall ensure the onsite personnel remain compliant with this PED policy. NSWCDD instruction defines PEDs as the following: any electronic device designed to be easily transported, with the capability to store, record, receive or transmit text, images, video, or audio data in any format via any transmission medium. PED’s include, but are not limited to, pagers, laptops, radios, compact discs and cassette players/recorders.