Attachment_0013_DD_254_with_attachments_No_Distribution_Statement.pdf

DEPARTMENT OF DEFENSE 1. CLEARANCE AND SAFEGUARDING

CONTRACT SECURITY CLASSIFICATION SPECIFICATION a. FACILITY CLEARANCE REQUIRED

SECRET (PEO-AMMO-17-004-S)

(The requirements of the DoD Industrial Security Manual apply to all aspects of this effort)

b. LEVEL OF SAFEGUARDING REQUIRED

SECRET

2. THIS SPECIFICATION IS FOR: (X and complete as applicable) 3. THIS SPECIFICATION IS: (X and complete as applicable)

a. PRIME CONTRACT NUMBER

a. ORIGINAL (Complete date in all cases)

Date (YYYYMMDD)

THIS DD254 IS FOR SOLICITATION PURPOSES ONLY.

A PRIME CONTRACT DD254 WILL BE PROVIDED

UPON CONTRACT AWARD.

X 20170601

b. SUBCONTRACT NUMBER b. REVISED REVISION NO. DATE (YYYYMMDD)

X (Supersedes all previous specs)

c. SOLICITATION OR OTHER NUMBER DUE DATE (YYMMDD) c. FINAL (Complete Item 5 in all cases) DATE (YYYYMMDD)

X W15QKN-17-R-0140

4. IS THIS A FOLLOW-ON CONTRACT? YES X NO. If Yes complete the following

Classified material received or generated under (Preceding Contract Number) is transferred to this follow-on contract

5. IS THIS A FINAL DD FORM 254? YES X NO. If Yes complete the following

In response to the contractor's request dated ____________ , retention of the identified classified material is authorized for the period of __________

6. CONTRACTOR (Include Commercial and Government Entity ( CAGE) Code)

a. NAME, ADDRESS, AND ZIP CODE b. CAGE CODE c. COGNIZANT SECURITY OFFICE (Name, Address, and Zip Code) This DD Form 254 is for Solicitation purposes only. A Prime Contract DD254 will be provided upon contract award.

N/A N/A

7. SUBCONTRACTOR

a. NAME, ADDRESS, AND ZIP CODE b. CAGE CODE c. COGNIZANT SECURITY OFFICES ( Name, Address, and Zip Code)

N/A

8. ACTUAL PERFORMANCE

a. LOCATION b. CAGE CODE c. COGNIZANT SECURITY OFFICE (Name, Address, and Zip Code)

TBD- CONTRACTOR LOCATIONS

9. GENERAL IDENTIFICATION OF THIS PROCUREMENT

Solicitation for the production and services in support of the following programs: RAMS (M152, MK152)

10. THIS CONTRACT WILL REQUIRE ACCESS TO: YES NO 11. IN PERFORMING THIS CONTRACT, THE CONTRACTOR WILL: YES NO

a. COMMUNICATIONS SECURITY (COMSEC) INFORMATION X a. HAVE ACCESS TO CLASSIFIED INFORMATION ONLY AT ANOTHER

CONTRACTOR’S FACILITY OR A GOVERNMENT ACTIVITY X

b. RESTRICTED DATA X b. RECEIVE CLASSIFIED DOCUMENTS ONLY X

c. CRITICAL NUCLEAR WEAPON DESIGN INFORMATION X c. RECEIVE AND GENERATE CLASSIFIED MATERIAL X

d. FORMERLY RESTRICTED DATA: X d. FABRICATE, MODIFY, OR STORE CLASSIFIED HARDWARE X

e. INTELLIGENCE INFORMATION: e. PERFORM SERVICES ONLY X

(1) Sensitive Compartmented Information (SCI) X f. HAVE ACCESS TO U.S. CLASSIFIED INFORMATION OUTSIDE THE U.S., PUERTO

RICO, U.S. POSSESSIONS AND TRUST TERRITORIES X

(2) Non-SCI X g. BE AUTHORIZED TO USE THE SERVICES OF DEFENSE TECHNICAL

INFORMATION CENTER (DTIC) OR OTHER SECONDARY DISTRIBUTION CENTER X

f. SPECIAL ACCESS INFORMATION X h. REQUIRE A COMSEC ACCOUNT X

g. NATO INFORMATION X i. HAVE A TEMPEST REQUIREMENT X

h. FOREIGN GOVERNMENT INFORMATION X j. HAVE OPERATIONS SECURITY (OPSEC) REQUIREMENTS X

i. LIMITED DISSEMINATION INFORMATION X k. BE AUTHORIZED TO USE THE DEFENSE COURIER SERVICE X

j. FOR OFFICIAL USE ONLY INFORMATION X l. OTHER (Specify) X

k. OTHER Specify) Controlled Unclassified Information (CUI)

X

DD Form 254, DEC 1999 Previous editions are obsolete

12. PUBLIC RELEASE. Any information (classified or unclassified) pertaining to this contract shall not be released for public dissemination except as provided by the industrial Security Manual or unless it has been approved for public release by appropriate U.S. Government authority. Proposed public release shall be submitted for approval prior to release

Direct X

Through (Specify):

Request for release of material requires approval through Program Manager, Office of the Project Manager, Close Combat Systems, (Andre Edwin, andre.c.edwin.civ@mail.mil) SFAE-AMO-CCS, Bldg. 183, Picatinny NJ 07806-5000 to the Picatinny Public Affairs Office.

to the Directorate for Freedom of Information and Security Review, Office of the Assistant Secretary of Defense (Public Affairs)* for review.

*In the case of non-DoD User Agencies, requests for disclosure shall be submitted to that agency.

13. SECURITY GUIDANCE. The security classification guidance needed for this effort is identified below. If any difficulty is encountered in applying this guidance or if any other contributing factor indicates a need for changes in this guidance, the contractor is authorized and encouraged to provide recommended changes: to challenge the guidance or classification assigned to any information or material furnished or generated under this contract; and to submit any questions for interpretation of this guidance to the official identified below. Pending final decision, the information involved shall be handled and protected at the highest level of classification assigned or recommended. (Fill in as appropriate for the classified effort. Attach, or forward under separate correspondence, any document/guides/extracts referenced herein. Add additional pages as needed to provide complete guidance.)

Classified material must be handled in accordance with the current National Industrial Security Program Operating Manual (NISPOM DoD 5220.22M) requirements, and source documents. No classified information/materials will be provided to contractor prior to verification of company’s facility clearance and storage capability.

Applicable Security Classification Guides are: REMOTE ACTIVATION MUNITION SYSTEM (RAMS) FAMILY, which will be provided under separate cover.

Contractor personnel shall comply with AR 381-12, Threat Awareness and Reporting Program (October 2010) and reporting requirements prescribed therein.

SEE DD254, BLOCK 13, CONTINUATION SHEETS FOR LIST OF SECURITY CLASSIFICATION GUIDES AND ADDITIONAL

SECURITY GUIDANCE.

Ref 13a: Army regulations available at: www.apd.army.mil.

Ref 13b: Classified information transmitted under this agreement is authorized to be submitted directly to/from: COMMANDING GENERAL, US ARMY Program Executive Officer AMMUNITION, ATTN: SFAE-AMO, Bldg. 1 Buffington Rd., Picatinny Arsenal, NJ 07806-5000.

Ref 13c: TECHNICAL LEAD ACKNOWLEDGEMENT AND SIGNATURE: The undersigned has reviewed this Security Specification, understands the security provisions outlined therein, and will ensure that the prime contractor complies with them as best possible within the limits of his/her responsibility, and that any violations are brought to the attention of the PCO and certifying security official identified in block 16.

Heather Gandy, Contracting Officer heather.a.gandy.civ@mail.mil (973) 724-3638

Nicolas Gyma, Technical Lead Government Representative nicolas.d.gyma.civ@mail.mil (973) 724-6038

14. ADDITIONAL SECURITY REQUIREMENTS. Requirements, in addition to ISM requirements, are established for this contract. (If Yes, identify the pertinent contractual clauses in the contract document itself, or provide an appropriate statement which identifies the additional requirements. Provide a copy of the requirements to the cognizant security office. Use Item 13 if additional space is needed.)

X Yes No

OPSEC Requirements; See Block 13 Continuation Sheet

NO CLASSIFIED INFORMATION WILL BE PROVIDED DURING THE SOLICITATION PHASE.

15. INSPECTIONS. Elements of this contract are outside the inspection responsibility of the cognizant security office. (If Yes, explain and identify specific areas or elements carved out and the activity responsible for inspections. Use Item 13 if additional space is needed.

Yes X No

16. CERTIFICATION AND SIGNATURE. Security requirements stated herein are complete and adequate for safeguarding the classified information to be released or generated under this classified effort. All questions shall be referred to the official named below.

a. TYPED NAME OF CERTIFYING OFFICIAL

b. TITLE Security Specialist Program Executive Office Ammunition c.TELEPHONE (Include Area Code)

(973) 724-9877/9775

d. ADDRESS (Include ZIP Code) 17. REQUIRED DISTRIBUTION

Program Executive Office – Ammunition X a. CONTRACTOR

Buffington Road, Building 1 b. SUBCONTRACTOR

Picatinny Arsenal, NJ 07806-5000 X c. COGNIZANT SECURITY OFFICE FOR PRIME AND SUBCONTRACTOR

e. SIGNATURE d. U.S. ACTIVITY RESPONSIBLE FOR OVERSEAS SECURITY

ADMINISTRATION

X e. ADMINISTRATIVE CONTRACTING OFFICER

X f. OTHERS AS NECESSARY

DD Form 254 (Back), DEC 1999 mailto:heather.a.gandy.civ@mail.mil mailto:nicolas.d.gyma.civ@mail.mil jason.hayman Typewritten Text Jason Hayman

PEO Ammunition Attachment (PEO-AMMO-17-004-S)

SOLICITATION NUMBER: W15QKN-17-R-0140

Attachment DD254, Block 13 Continuation Sheet :

SECURITY GUIDANCE

Ref 10j and Ref 10k: SEE DD254, BLOCK 13, CONTINUATION SHEET FOR

FOUO/CUI GUIDANCE.

Ref 11c: Contractor will follow the guidelines of Chapters 4 and 5 of the NISPOM for the proper handling of classified information. Contractor will also follow guidance set forth within Security Classification Guide (SCG), The contractor requires access to classified source data up to and including SECRET in support of the work effort. Any extracts or use of such data requires the contractor to apply derivative classifications and markings consistent with the source documents.

Use of “Multiple Sources” on the “Derived From” line necessitates compliance with the NISPOM, paragraph 4-208a, and the use of a bibliography.

Ref 11d: Contractor must provide adequate storage at their facility for classified material and/or hardware to the level of SECRET.

Ref 11j: The contractor shall develop an OPSEC Standing Operating Procedure (SOP)/Plan within 60 calendar days of contract award, to be reviewed and approved by the responsible Government OPSEC officer, per AR 530-1, Operations Security. This SOP/Plan will specify the government’s critical information, why it needs to be protected, where it is located, who is responsible for it, and how to protect it. In addition, the contractor shall identify an individual who will be an OPSEC Coordinator. The contractor will ensure that this individual becomes OPSEC Level II certified per AR 530-1. Training can be received from either the Army OPSEC Support Element (OSE) or the Interagency OPSEC Support Staff (IOSS). Per AR 530-1, Operations Security, new contractor employees must complete Level I OPSEC training within 30 calendar days of their reporting for duty. All contractor employees must complete annual OPSEC awareness training. Enclosure 1 of this Attachment provides guidance regarding the format of the OPSEC plan.

Enclosure 1 Page 2 of 9

SOLICITATION NUMBER: W15QKN-17-R-0140

Attachment DD254, Block 13 Continuation Sheet :

SECURITY GUIDANCE

Enclosure 1 – OPSEC Plan Format

I. COVER PAGE

The cover page for an OPSEC Plan shall clearly present, at a minimum, the following information:

1. Title of the Acquisition Program

2. Title of the Document (i.e. “Operations Security Plan”)

3. Reference to the government contract number

4. Date of latest revision

5. Name, signature and title of the preparer of the OPSEC Plan

6. Name, signature and title of the approver of the OPSEC Plan

7. Reference for whom the document was prepared (Contracting activity)

8. Reference by whom the document was prepared (Corporation)

9. All appropriate distribution or classification statements

II. TABLE OF CONTENTS PAGE

The Table of Contents for an OPSEC Plan shall outline each section contained in the OPSEC Plan.

III. PREFACE PAGE

The purpose of the Preface is to provide a brief, unclassified, overview of the program and the need for OPSEC measures. The specific objectives of the contracted effort shall be introduced with reference to all strategic participants and partnerships required to make the program a success. The anticipated development of any innovative concepts or technologies shall also be introduced in the Preface.

The Preface shall reference all links between the OPSEC Plan and any corporate OPSEC Program(s).

The Preface may conclude by referencing requirement documents such as the contract number, Contract Security Classification Specification (DD254), Contract Data Requirements List (DD1423) and any other pertinent guidance provided by the contracting activity. It shall also provide an OPSEC point of contact, with contact information, for additional guidance or assistance such as the OPSEC program manager or contractor program manager.

IV. OPSEC PLAN INTRODUCTION

Purpose and Scope: The purpose of the OPSEC Plan shall be effectively communicated in this section and include a description of the scope of the OPSEC Plan (unique physical locations, subcontractors, suppliers, period of performance, etc.).

Authorities: The requirement to protect critical information shall be documented within this section.

Documenting the requirement can be achieved by referencing the Corporate OPSEC Program (Policy) and Plan, DODM 5205.-2M, specific contract documents including the DD254 for contracts involving classified data, or other contracting activity specific guidance.

Enclosure 1 Page 3 of 9

OPSEC Plan Major Activity Timeline: This section shall include a list of all major OPSEC Plan activities such as quarterly OPSEC Working Group Meetings, Annual Assessments, scheduled OPSEC awareness training, Sub-contractor OPSEC Assessments and Surveys, Threat and Vulnerability Reviews, etc. This section shall also include scheduled OPSEC Plan reviews.

Responsibilities: The OPSEC Plan shall identify who is responsible for the major activities described in the Plan. For example (not intended as an inclusive The OPSEC Officer shall be identified by name and include a list of duties that may include:

1. Coordinate all OPSEC policy responsibilities/ procedures within the program

2. Revise the Program OPSEC Plan as necessary

3. Convene and coordinate the annual Program OPSEC Assessment

4. Disseminate updated threat information to program personnel

5. Assist in the review of contract requirements for OPSEC considerations

6. Conduct OPSEC Training IAW AR 530-1, Chapter 4.

7. Achieve OPSEC Level II certification

8. Develop/Disseminate Program Critical Information List (CIL)

9. Promote OPSEC awareness within the program

A short description of the expectations and responsibilities of all program personnel (including subcontractors and suppliers) shall be provided and may typically include:

1. Remain compliant with all applicable OPSEC Plans

2. Maintain an awareness of all applicable CIL

3. Attend all OPSEC program briefings

4. Timely reporting of any OPSEC concerns to the Contractor Program Manager and/or the

Program OPSEC Manager

5. Generation of OPSEC Plans (sub-contractors or suppliers only)

Organizational OPSEC Communications and Interfaces: A description as to how the OPSEC Plan will be communicated to all personnel supporting the program (hardcopy, via a webpage, briefings, etc.)

Marking, Handling and Distribution of Documents: This section shall provide a description of marking, handling, storage, access and transmission authorizations and procedures for any critical information provided to, or generated by, the contractor. Reference to the program classification guide, Freedom of Information Act and any additional guidance provided by the contracting activity may be cited as applicable.

V. CRITICAL INFORMATION

General: Critical information shall be identified within this section of the plan and a comprehensive program Critical Information List (CIL) shall be included.

Critical Information List: Guidance on the creation of a CIL is contained within “Applying OPSEC to Government Acquisitions and Contracts,” available at www.ioss.gov, AR 530-1, DODM 5205.02M, or may be provided by the contracting activity. Ideally the CIL shall remain unclassified to facilitate wide internal distribution, but may provide reference to classified information as applicable

VI. THREAT

General Threat: This section shall identify and demonstrate an understanding of the http://www.ioss.gov/

Enclosure 1 Page 4 of 9 overall threat to program critical information throughout the anticipated duration of the contract/program. The section shall conclude with a brief description of all identified intelligence/information collection methods that may be expected to be used by an adversary or competitor to acquire Critical Information. Note: For current information see, “Targeting US Technologies: A Trend Analysis of Cleared Industry Reporting.” You can also contact your local FBI field office for relevant information.

Program Detailed Threat: This section shall be similar to section above referencing any known direct threats to acquisition specific elements of critical information within the program/contract. As complete a description of each threat as possible shall be provided while maintaining the overall plan classification at the unclassified level.

Threat Analysis: Each threat identified in above sections shall be analyzed to determine the level of threat to the corresponding critical information. The results of this analysis shall be presented in this section. A description of the specific threat analysis method used by the contractor to quantify each threat shall be included in this section. Note: For additional guidance and a sample threat analysis methodology see, “Applying OPSEC to Government Acquisitions and Contracts” at www.ioss.gov and DODM 5205.02.

VII. VULNERABILITIES

General: The Vulnerability section of the OPSEC Plan shall describe the analysis of activities (indicators) that point to OPSEC vulnerabilities an adversary can exploit to acquire critical information. This section shall contain a list of all identified OPSEC vulnerabilities.

List of OPSEC Vulnerabilities: All vulnerabilities shall be described in sufficient detail as to communicate to the contracting activity the extent of the vulnerability. The Vulnerability List shall remain unclassified. Note: A list of typical OPSEC vulnerabilities which may require OPSEC measures may be found within “Applying OPSEC to Government Acquisitions and Contracts”, available at www.ioss.gov. These sample vulnerabilities are not all inclusive and the submitted vulnerability list shall be tailored to the specific acquisition or contract.

Vulnerability Analysis: Once potential program vulnerabilities have been identified, the magnitude of each vulnerability shall be determined using a consistent methodology identified and documented in this section of the OPSEC Plan. The results of this analysis shall also be described in this section.

Note: For additional guidance and a sample vulnerability methodology see, “Applying OPSEC to Government Acquisitions and Contracts” at www.ioss.gov, AR 530-1 and DODM 5205.0-2M.

VIII. RISK ASSESSMENT

General: The OPSEC risk of a program represents the probability of compromise of critical information and the impact to the program/contract taking into account the threat and vulnerabilities.

The acceptable level of OPSEC risk (as determined by senior leadership, or the contracting activity) shall be described in this section in terms consistent with the selected OPSEC methodology.

Risk Assessment: The specific OPSEC risk shall be described in terms consistent with the OPSEC methodology selected for determining OPSEC threat and vulnerability. The method, and the results of the assessment, shall be presented in this section. The conclusion of the risk assessment shall result in an ordinal ranking of OPSEC risk (highest to lowest). Note: Additional guidance and a sample risk methodology are available in “Applying OPSEC to Government Acquisitions and Contracts” at www.ioss.gov, AR 530-1 and DODM 5205.0-2M.

http://www.dss.mil/documents/ci/2013%20Unclass%20Targeting%20US%20Technologies_FINAL.pdf http://www.dss.mil/documents/ci/2013%20Unclass%20Targeting%20US%20Technologies_FINAL.pdf http://www.ioss.gov/ http://www.ioss.gov/

Enclosure 1 Page 5 of 9

IX. OPSEC MEASURES

General: This section of the OPSEC Plan shall identify specific OPSEC Measures proposed for mitigating OPSEC risk to acceptable levels including the cost to implement each measure. A sampling of common OPSEC measures is available in “Applying OPSEC to Government Acquisitions and Contracts” at www.ioss.gov. This list is not to be considered exhaustive and is provided as guidance for the development of the program/contract specific list of potential OPSEC measures.

Residual Risk: This section shall contain an analysis of residual OPSEC risk, in terms consistent with the OPSEC methodology selected, as a result of implementation of each OPSEC measure presented. This section shall identify which OPSEC measures will be implemented and the rationale for those that will not.

X. OPSEC PROGRAM CHRONOLOGY:

This section shall document significant program OSPEC events throughout the lifecycle of the program. Significant events may include changes to the CIL, changes in program leadership or results of program assessments and surveys (including subcontractors). At a minimum, this section shall include a brief description of the event, date of occurrence, actions taken by the contractor and final disposition. A known compromise of critical information need only be referenced in keeping with the intended classification of this document. Note: The history contained herein may be used by the government as a part of an OPSEC or security audit conducted by the contracting activity, DSS or other authorized agency.

XI. ACRONYMS:

This section shall include a complete list of acronyms used in the Program OPSEC Plan.

XII. REFERENCES:

This section shall include a complete list of all references cited in the Program OPSEC Plan.

SOLICITATION NUMBER: W15QKN-17-R-0140

DD254, Block 13, Section 10j and 10k Continuation Sheet:

For Official Use Only (FOUO) and Controlled Unclassified Information (CUI)

10j. FOR OFFICIAL USE ONLY (FOUO)

1. The “FOR OFFICIAL USE ONLY” marking is assigned to information at the time of its creation in a DOD User Agency. It is not authorized as a substitute for a security classification marking but it is used on official government information that may be withheld from the public under exemptions 2 through 9 IAW Army Regulation 25-55, The Department of the Army Freedom of Information Act Program.

2. Control, marking, and protection of FOUO information will be in accordance with this document and DoD Manual 5200.01, Vol. 4.

3. Specific Handling Instructions: All emails containing (FOUO) will be digitally encrypted in accordance with AR 25-1, para. 4-1 f.(1)(b), dated 25 June 2013. There are several encryption tools available for use to accomplish this requirement: The AMRDEC Safe Access File Exchange (SAFE) website (https://safe.amrdec.army.mil/SAFE/) and/or the Encryption Wizard (http://spi.dod.mil/).

4. FOR OFFICIAL USE ONLY is restricted to personnel with a valid need to know unless public release authorization has been obtained. Information marked as FOUO, in any media format, may only be disseminated to those individuals or organizations with direct affiliation with the given program or project. Further dissemination of such information will be at the discretion of the Contracting Officer (PCO) or Contracting Officer’s Representative (COR).

Personnel no longer requiring access to FOUO must destroy or surrender any materials in their possession and terminate future access to it. The contractor may disseminate “FOR OFFICIAL USE ONLY” (FOUO) information to their employees who have a need to know for the information in connection with this contract.

5. When no longer needed, all FOUO material will be destroyed by shredding. Electronic media will be purged with approved software or destroyed through a physical process.

6. Use of the above marking does not mean that the information cannot be released to the public, only that it must be reviewed by the Government prior to its release to determine whether a significant and legitimate government purpose is served by withholding the information, or portions of it, from the public.

7. An unclassified document containing FOUO information will be marked IAW with DoD Manual 5200.01, Vol. 4, Enclosure 3, paragraph 2c.

https://safe.amrdec.army.mil/SAFE/

8. Within a classified document, an individual page that contains both FOUO and classified information will be marked at the top and bottom with the highest security classification of the information appearing on the page, as outlined in the NISPOM, AR 380-5, and DoD Manual 5200.01.

9. Removal of the “For Official Use Only” marking can only be accomplished by the originator or other competent authority. When the “For Official Use Only” status is terminated, all known holders will be notified to the extent practical.

10. During working hours, “For Official Use Only” information shall be placed in an out-of-sight location if the work area is accessible to persons who do not have a need for the information. During non-working hours, the information shall be stored to preclude unauthorized access. Filing such material with other unclassified records in unlocked files or desks is adequate when internal building security is provided during non-working hours. When such internal security is not exercised, locked buildings or rooms will provide adequate after-hours protection or the material can be stored in locked receptacles such as file cabinets, desks, or bookcases. “For Official Use Only” information may be sent via First Class US Mail or by parcel post. Bulky shipments may be set by Fourth Class US Mail.

11. Unauthorized disclosure of “For Official Use Only” information does not constitute a security violation but the Government Customer should be informed of any unauthorized disclosure. The unauthorized disclosure for FOUO information protected by the Privacy Act may result in criminal sanctions and disciplinary action may be taken against those responsible.

10k. CONTROLLED UNCLASSIFIED INFORMATION (CUI)

1. The definition of CUI is unclassified information that requires safeguarding or dissemination controls pursuant to and consistent with law, regulations, and Government-wide policies. It does not include information that is classified pursuant to Executive Order 13526, dated December 29, 2009, or the Atomic Energy Act, as amended (References (m) and (n)). Within the Department of Defense, examples of CUI include materials marked as “For Official Use Only (FOUO)”, “Law Enforcement Sensitive (LES),” or any unclassified technical documents with a Distribution Statement B-F.

2. When CUI is to be provided to or generated by DoD contractors, the controls and protective measures to be applied shall be described in the pertinent contract documents (e.g., contract clause; statement of work; or DD Form 254, “Department of Defense Contract Security Classification Specification”). Solicitations and contracts shall use a non-disclosure of information clause that prohibits release of unclassified information to the public without approval of the contracting activity.

3. The Contractor shall not release to anyone outside the Contractor's organization any unclassified information, regardless of medium (e.g., film, tape, document), pertaining to any part of this contract or any program related to this contract without prior approval from the government.

4. Technical Data is any recorded information related to experimental, developmental, or engineering works that can be used to define an engineering or manufacturing process or to design, procure, produce, support, maintain, operate, repair, or overhaul program material. The data may be graphic or pictoral delineations in media, such as computer software, drawings, or photographs, text in specifications, or related performance or design documents, or computer printouts. Examples of technical data include research and engineering data, engineering drawings, and associated lists, specifications, standards, process sheets, manuals, technical reports, catalog-item identifications, and related information, and computer software documentation.

5. GOVERNMENT DISTRIBUTION STATEMENTS: Will be added to all technical data generated during the execution of this contract, in accordance with DoD Directive 5230.24.

6. The contractor shall protect CUI from unauthorized disclosure by appropriately marking, safeguarding, disseminating, and destroying such information.

7. CUI may be identified in security classification guides to ensure the information receives appropriate protection.

8. For unauthorized disclosures of CUI, no formal security inquiry or investigation is required.

However, appropriate management action shall be taken to fix responsibility for unauthorized disclosure of CUI whenever feasible or required by other guidance, and appropriate disciplinary action shall be taken against those responsible. The DoD Component that originated the CUI shall be informed of its unauthorized disclosure.

SOLICITATION NUMBER: W15QKN-17-R-0140

DD254, Block 17, Required Distribution

PLEASE ENSURE ALL PARTIES LISTED ON THIS DISTRIBUTION RECEIVE A

COPY OF THE DD254 WITH ALL ATTACHMENTS

SECTION 17: REQUIRED DISTRIBUTION:

a. CONTRACTOR (all locations listed in Block 8a):

TBD

c. COGNIZANT SECURITY OFFICE FOR PRIME CONTRACTOR:

**In the event of a possible compromise of classified information under the control of the contractor, the contractor will immediately notify:

Defense Security Service Insert Appropriate Field Office Information

TBD

e. CONTRACTING OFFICER:

Heather Gandy Army Contracting Command - NJ ACC-NJ-CC, Bldg. 10 Picatinny Arsenal, NJ 07806-5000 Phone: 973-724-3638 Email: heather.a.gandy.civ@mail.mil

GOVERNMENT TECHNICAL LEAD:

Nicolas D Gyma US Army Armament Research, Development & Engineering Center (ARDEC) RDAR-MEM-G, Bldg. 64S Picatinny Arsenal, NJ 07806-5000 Email: nicolas.d.gyma.civ@mail.mil

f. OTHERS AS NECESSARY:

Naomi Griggs or Jason Hayman Industrial Security Specialist PEO Ammunition, SFAE-AMO Picatinny Arsenal, NJ 07806-5000 (973)724-9877 or (973) 724-9775 naomi.j.griggs.civ@mail.mil and/or jason.j.hayman.civ@mail.mil mailto:heather.a.gandy.civ@mail.mil mailto:nicolas.d.gyma.civ@mail.mil mailto:naomi.j.griggs.civ@mail.mil mailto:jason.j.hayman.civ@mail.mil