H40 Rapid Prototyping SOW.pdf

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

AS50881 SAE Aerospace Standards, Wiring Aerospace Vehicle

IPC J-STD-001 Soldering Certification

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-HDBK-1568 Military Handbook Materials and Processes for Corrosion Prevention and Control in

Aerospace Weapon Systems

MIL-HDBK-1587 Department of Defense Handbook Material and Process requirement for Air Force Weapon

Systems

MIL-HDBK-1791 (USAF) Military Handbook Designing for Internal Aerial Delivery in Fixed Wing Aircraft

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 Emissions and Susceptibility

MIL-STD-462 Test Method Standard for Measurement of Electromagnetic Interference Characteristics

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-1760 Department of Defense Interface Standards for Aircraft/Store Electrical Interconnection System

MIL-STD-2401 DoD World Geodetic System 1984 (WGS-84)

MIL-STD-2525 Common Warfighting Symbology

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, 901, 1274.

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, A010, A011)

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 development 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 of hardware and software systems, integrate configuration management and workflow tools, trouble shoot of hardware and software systems, disassemble and assemble of 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, A010, A011, A012)

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, A010, A011, A012)

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, A015)

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 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 A013).

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, A014). 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. Results of these meetings shall be reported in the Weekly Status Report. If necessary, schedule adjustments will be made via Delivery Order modifications. (CDRL A002)

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 Contractor’s primary facility providing support under this contract must be located within 100 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 at proposal submission. The Contractor’s primary facility must be cleared at the SECRET level for both information processing and storage at contract award.

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 Management and Support personnel. Interim clearances are acceptable.

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 Management and Support personnel. Interim clearances are acceptable. 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.

C.11.2 Controlled Unclassified Information (CUI) (formerly 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 DODI 5200.48, Controlled Unclassified Information (CUI), March 6, 2020. The Contractor will receive and generate classified material in accordance with the Security Classification Guidance specified on the DD Form

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 the ISFD.

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 32 CFR 117 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. In addition, this includes removable storage media such as flash memory, memory sticks, multimedia cards and secure digital cards, micro-drive modules, ZIP drives, ZIP disks, CD-RWs, DVD-RWs, MP3 players, iPADs, digital picture frames, electronic book readers, kindle, nook, cameras, external hard dish drives, and floppy diskettes.

C.11.7.2 Personal Wearable Fitness Devices (PWFDs) marketed primarily as fitness or sleep devices are allowed in all Navy spaces where collateral non-Sensitive Compartmented Information (SCI), classified information is processed, stored, or discussed up to and including secret. User must ensure PWFD is compliant with all requirements in NAVADMIN 216/15, Cyber Hygiene Authorization to use Personal Wearable Fitness Devices (e.g., FitBit, Jawbone UP, etc.) in Navy Spaces, dated 14 September 2015 and register PWFD in the NSWCDD Fitness

Device Tracker.

C.11.7.3 PED’s belonging to an external organization shall not be connected to NSWCDD networks or infrastructure without prior approval from the NSWCDD Information Assurance and Compliance Branch. This approval will be granted using the TARIS form and action tracker process.

C.11.7.4 Personally owned hardware or software shall not be connected or introduced to any NSWCDD hardware, network or information system infrastructure.

C.11.8 Operations Security (OPSEC)

C.11.8.1 Contractor personnel shall follow OPSEC concepts and principles in the conduct of this requirement to protect critical information, personnel, facilities, equipment, and operations from compromise. All Contractors

(including Subcontractors) shall supplement their current security practices by requiring any personnel involved in executing this contract to complete Government-sponsored and administered Operations Security (OPSEC) training.

In addition, all Contractors should be aware of the Critical Information and Indicators List (CIIL) for the organization they are supporting as well as the OPSEC plan for NSWCDD. These OPSEC requirements will be in effect throughout the life of the procurement from award through the conclusion of services at the end of the period of performance (PoP) or other procurement termination. The Contractor must immediately notify the Government upon the discovery of any nonconformance with the OPSEC Plan.

C.11.9 Privacy Program Training

C.11.9.1 Privacy Program Training. Privacy training is mandatory for all NSWCDD personnel (military, civilian, and Contractor) and must be completed annually. The Total Workforce Management System (TWMS) is the official database for workforce training and is the preferred tool for taking and recording privacy act training. All

NSWCDD personnel are responsible for ensuring individual annual privacy training requirements are met.

C.12 ON-SITE SAFETY REQUIREMENTS

C.12.1 The Contractor shall strictly adhere to Federal Occupational Safety and Health Agency (OSHA)

Regulations, Environmental Protection Agency (EPA) Regulations, and all applicable state and local requirements.

C.12.2 The Contractor shall ensure that each Contractor employee reads the document entitled, "Occupational

Safety and Health (OSH) Policy Statement" within 30 days of commencing performance at NSWCDD. This document is available at:

https://wwwdd.nmci.navy.mil/program/Safety_and_Environmental_Office/Safety/Safety.html

C.12.3 The Contractor shall provide each Contractor employee with the training required to do his/her job safely and in compliance with applicable regulations. The contractor shall document and provide, upon request, qualifications, certifications, and licenses as required.

C.12.4 The Contractor shall provide each Contractor employee with the personal protective equipment required to do their job safely and in compliance with all applicable regulations.

C.12.5 Contractors working with ionizing radiation (radioactive material or machine sources) must comply with

NAVSEA S0420-AA-RAD-010 (latest revision) [provided upon request]. Prior to bringing radioactive materials or machine sources on base, the Contractor must notify the Command Radiation Safety Officer in the Safety &

Environmental Office.

C.12.6 The Contractor shall ensure that all hazardous materials (hazmat) procured for NSWCDD are procured through or approved through the hazmat procurement process. Hazmat brought into NSWCDD work spaces shall be reviewed and approved by the Safety & Environmental Office prior to use by submitting an Authorized Use List addition form and Safety Data Sheet that shall be routed through the Government supervisor responsible for the specific work area. The Authorized Use List addition form can be found at https://wwwdd.nmci.navy.mil/program/Safety_and_Environmental_Office/.

C.12.7 Upon request, the Contractor shall submit their OSHA 300 Logs (injury/illness rates) for review by the

Safety Office. If a Contractor's injury/illness rates are above the Bureau of Labor & Statistics industry standards, a safety assessment will be performed by the Safety Office to determine if any administrative or engineering controls can be utilized to prevent further injuries/illnesses, or if any additional PPE or training will be required.

C.12.8 Applicable contractors shall submit Total Case Incident Rate (TCIR) and Days Away, Restricted and

Transfer (DART) rates for the past three years upon request by the Safety Office. A Contractor meets the definition of applicable if its employees worked 1,000 hours or more in any calendar quarter on site and where oversight is not directly provided in day to day activities by the command.

C.12.9 The Contractor shall report all work-related injuries/illnesses that occurred while working at NSWCDD to the Safety Office.

C.12.10 The Contractor shall ensure that all on-site Contractor work at NSWCDD is in accordance with the

NSWCDDINST 5100.1D Occupational Safety and Health Instruction, available at: