M67854-21-R-2053 SF33.pdf

CODE

(Hour)

PAGE(S)

until 02:00 PM local time 16 Nov 2020

X

A

X B

X C X D

EX

X

G

F 45 - 58

59 - 67

H 68 - 70 catherine.Opsahl@usmc.mil

RATING PAGE OF PAGES

7. ISSUED BY

(Date)

IMPORTANT - Award will be made on this Form, or on Standard Form 26, or by other authorized official written notice.

Previous Edition is Unusable 33-134 STANDARD FORM 33 (REV. 9-97)

Prescribed by GSA

FAR (48 CFR) 53.214(c)

1 70

(If other than Item 7)

15A. NAME 16. NAME AND TITLE OF PERSON AUTHORIZED TO

AND

ADDRESS

SIGN OFFER (Type or print)

OF

OFFEROR

AMENDMENT NO. DATE

15B. TELEPHONE NO (Include area code) 17. SIGNATURE15C. CHECK IF REMITTANCE ADDRESS

IS DIFFERENT FROM ABOVE - ENTER

SUCH ADDRESS IN SCHEDULE.

18. OFFER DATE

1. THIS CONTRACT IS A RATED ORDER

UNDER DPAS (15 CFR 700)

2. CONTRACT NO.

M67854 8. ADDRESS OFFER TO

See Item 7

9. Sealed offers in original and 1 copies for furnishing the supplies or services in the Schedule will be received at the place specified in Item 8, or if handcarried, in the depository located in

CAUTION - LATE Submissions, Modifications, and Withdrawals: See Section L, Provision No. 52.214-7 or 52.215-1. All offers are subject to all terms and

See Section L conditions contained in this solicitation.

10. FOR INFORMATION

CALL:

A. NAME (NO COLLECT CALLS)

CATHERINE G. OPSAHL 703-432-8728

11. TABLE OF CONTENTS

SOLICITATION/ CONTRACT FORM

SUPPLIES OR SERVICES AND PRICES/ COSTS

2 - 4

X I CONTRACT CLAUSES

DESCRIPTION/ SPECS./ WORK STATEMENT X

PACKAGING AND MARKING

5 - 15

16 - 22

J LIST OF ATTACHMENTS

INSPECTION AND ACCEPTANCE

DELIVERIES OR PERFORMANCE

24 - 25 X K

REPRESENTATIONS, CERTIFICATIONS AND

OTHER STATEMENTS OF OFFERORS

CONTRACT ADMINISTRATION DATA 26 - 28 X

SPECIAL CONTRACT REQUIREMENTS

OFFER (Must be fully completed by offeror)

X M

L INSTRS., CONDS., AND NOTICES TO OFFERORS

EVALUATION FACTORS FOR AWARD

NOTE: Item 12 does not apply if the solicitation includes the provisions at 52.214-16, Minimum Bid Acceptance Period.

is inserted by the offeror) from the date for receipt of offers specified above, to furnish any or all items upon which prices are offered at the price set opposite each item, delivered at the designated point(s), within the time specified in the schedule.

13. DISCOUNT FOR PROMPT PAYMENT

(See Section I, Clause No. 52.232-8)

14. ACKNOWLEDGMENT OF AMENDMENTS

(The offeror acknowledges receipt of amendments

AMENDMENT NO. DATE

to the SOLICITATION for offerors and related documents numbered and dated):

FACILITY

12. In compliance with the above, the undersigned agrees, if this offer is accepted within calendar days (60 calendar days unless a different period

SOLICITATION, OFFER AND AWARD

X

(X) SEC. DESCRIPTION (X) SEC. DESCRIPTION PAGE(S)

PART I - THE SCHEDULE

26. NAME OF CONTRACTING OFFICER (Type or print) 27. UNITED STATES OF AMERICA 28. AWARD DATE

EMAIL:TEL: (Signature of Contracting Officer)

CODE CODE

B. TELEPHONE (Include area code) C. E-MAIL ADDRESS

AWARD (To be completed by Government)

19. ACCEPTED AS TO ITEMS NUMBERED 20. AMOUNT 21. ACCOUNTING AND APPROPRIATION

22. AUTHORITY FOR USING OTHER THAN FULL AND OPEN COMPETITION:

10 U.S.C. 2304(c)( ) 41 U.S.C. 253(c)( ) (4 copies unless otherwise specified)

23. SUBMIT INVOICES TO ADDRESS SHOWN IN ITEM

24. ADMINISTERED BY (If other than Item 7) CODE 25. PAYMENT WILL BE MADE BY CODE

PART IV - REPRESENTATIO NS AND INSTRUCTIO NS

PART III - LIST O F DO CUMENTS, EXHIBITS AND O THER ATTACHMENTS

29 - 43

PART II - CO NTRACT CLAUSES

COMMANDER, MARCORSYSCOM

ATTN: CATHIE OPSAHL

2200 LESTER STREET

QUANTICO VA 22134 (703) 432-8728

FAX:

TEL:

FAX:

TEL:

NOTE: In sealed bid solicitations "offer" and "offeror" mean "bid" and "bidder".

SOLICITATION

6. REQUISITION/PURCHASE NO.5. DATE ISSUED

08 Oct 2020

4. TYPE OF SOLICITATION

SEALED BID (IFB)

NEGOTIATED (RFP)

[ X ]

3. SOLICITATION NO.

M6785421R2053

Section B - Supplies or Services and Prices

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

0001 80 Each Marine Analog Tactical Telephone System

FFP

Test Assets IAW SOW 4.1. and Attachment 2: PSPEC

NOTE: The requirements in DFARS 252.211-7003, Item Identification and

Valuation, are applicable for this line item. The contractor shall provide DoD unique identification or a DoD recognized unique identification equivalent.

FOB: Destination

PSC CD: 5805

NET AMT

0002 2,000 Each OPTION Marine Analog Tactical Telephone System

IAW SOW 4.1. and Attachment 2: PSPEC unique identification or a DoD recognized unique identification equivalent.

0003 7,920 Each OPTION Marine Analog Tactical Telephone System

IAW SOW 4.1. and Attachment 2: PSPEC unique identification or a DoD recognized unique identification equivalent.

0004 1 Each Operator's Manual

Test Assets IAW SOW 4.4.4 and Exhibit D002

0005 12 Each Technical Data (CDRLs)

Exhibits A, B, C and D Not Seperately Priced (NSP)

Section C - Descriptions and Specifications

STATEMENT OF WORK

1. Scope of Work

This Statement of Work (SOW) defines the efforts required for the manufacture and delivery of the Wired in the Defense (WID) Marine Analog Tactical Telephone (MATT) system, as well as logistics information, manuals, and engineering drawings.

2. Background

The WID MATT will provide a wired command and control (C2) communication capability. It will be able to operate in a point to point or point to multi-point configuration. It will be able to provide redundant C2 capability that can operate in an environment where radio frequency (RF) is denied or degraded and separate from all data/internet protocol (IP) networks.

3. Documents

The following documents form a part of this SOW to the extent specified herein (i.e., “Mandatory Compliance” or “Guidance Only”). The most recent version of the referenced document at the time of contract award shall be used unless otherwise specified. In the event of conflict between the applicable documents and this SOW, the SOW shall take precedence.

Nothing in this document, however, supersedes applicable laws and regulations unless a specific exemption has been obtained.

3.1. Military Standards (MIL-STD) and Specifications - Mandatory Compliance

These latest versions of MIL-STDs and Specifications can be found online at the Acquisition

Streamlining and Standardization Information System website at https://quicksearch.dla.mil/qsSearch.aspx or at –Every Spec http://www.everyspec.com/. If not available there, contact the Program Office.

MIL-STD-461 Radio Frequency (RF) Emissions and Susceptibility and

Electromagnetic Interference Susceptibility

MIL-STD-810 Standard Practice for System Safety

MIL-STD-882 Standard Practice for System Safety

MIL-STD-1366 DoD Interface Standard for Transportability Criteria

MIL-STD-1388-1 Logistics Support Analysis

MIL-STD-40051-2 Preparation of Digital Technical Information for Page – Based

Technical Manuals

MIL-STD-40051-5 Parts Information (PI) and Repair Parts and Special Tools List

(RPSTL)

MIL-STD-3018 Parts Management

MIL-STD-31000 Technical Data Packages

MIL-STD-129 Military Marking for Shipment and Storage

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

MIL-STD-12 Abbreviations for use on Drawings and in Specifications, Standards and Technical Documents

3.2. Federal Standard (FED-STD) – Mandatory Compliance

FED-STD-313E Safety Data for Hazardous Material

NIST SP 800-171 Rev. 1 Protecting Controlled Unclassified Information in Nonfederal

Systems and Organizations

GEIA-STD-0007 Logistics Product Data Handbook

3.3. Government Handbooks (HDBK) – Guidance Only

MIL-HDBK-61 Configuration Management Guidance

MIL-HDBK-470 Designing and Developing Maintainable Products and Systems

MIL-HDBK-502 Acquisition Logistics

SIAT-HDBK-001 Marine Corps Systems Command Systems Engineering Technical

Review Handbook

GEIA-HB-0007 Logistics Product Data Handbook

3.4. Other Government Documents – Guidance Only

Unless otherwise stated, the following documents may be obtained from the Document

Automation and Production Service, Building 4/D, 700 Robbins Avenue, Philadelphia, PA

19111-5094 or visit http://dodssp.daps.mil:

DI-SESS-81000 Product Drawings/Models and Associated Lists

3.5. Non-Government Documents – Guidance Only

ISO 10303 Standard for Exchange Product Model Data STEP Format

ASME Y14.100 Engineering Drawing Practices with Append. B, C, D, & E

ASME Y14.24 Types and Applications of Engineering

ASME Y14.34 Associated Lists

GEIA-HB-649 Implementation Guide for Configuration Management

(Copies of ASTM documents are available from www.astm.org or American Society for Testing and Materials International, 100 Barr Harbor Drive, West Conshohocken, PA 19428-2959.)

3.6. Additional References:

DFARS 211.274 Item Identification and Valuation Requirements

DFARS 252.211-7003 Item Identification and Valuation

DFARS 252.246-7006 Warranty Tracking of Serialized Items

DFARS 252.246-7008 Use of Government-Assigned Serial Numbers

DODI 4161.02 Accountability and Management of Government Contract Property

DODI 8320.04 IUID Standards for Tangible Personal Property

SECNAVINST 4440.34 Implementation of IUID within the Department of the Navy

MCO 4410.28 IUID of Ground Equipment

OUSD (AT&L) IUID Implementation Planning Guide

AMS-STD-595 Standard Color Chart

4. REQUIREMENTS

The contractor shall deliver all items identified in Contract Data Requirements List (CDRLs) in accordance with each DD Form 1423 and the CDRL Submission Instructions. Deliverables are referenced by name and reference number after the paragraph containing the requirement for that deliverable.

The contractor shall perform all tasks required and delineated in this SOW to manufacture and test the WID MATT, prepare associated documentation, and deliver both to the Government.

The contractor shall provide all materials, equipment, hard tooling, and personnel necessary to perform the tasks in this SOW and deliver the types and quantities of deliverables specified by the contract.

4.1. Marine Analog Tactical Telephone

The contractor shall deliver WID MATTs that meet the specifications listed in the Performance

Specification (P-SPEC).

The WID MATT system shall include:

Handset

Quick Reference Guide (QRG)

Special tools, if required

4.2. Program and Data Management

4.2.1. Status Report

The contractor will deliver a monthly status report that identifies the agreed to production and delivery schedule and will track deliveries to date and highlight any deviations. This monthly report will be due on the last day of each month starting with the first full month after award.

(CDRL B001, Monthly Status Reports)

4.2.2. Post Award Conference (PAC)

The contractor shall host a Post Award Conference (PAC) at the contractor's facility or virtually within 30 days of Contract Award. The purpose of the PAC is for the contractor to review, and demonstrate to the Government, the management procedures it uses, deliver a progress assessment, review the status of technical and other specialty areas, and establish schedule dates for near term critical meetings/actions. The contractor shall present management, key personnel, and program implementation processes. As part of the PAC presentation materials, the contractor shall provide the production schedule and delivery timeline.

(CDRL B002, Presentation Material)

(CDRL B003, Conference Minutes)

4.2.3. Security Requirements

The information provided to the contractor will be unclassified and/or Controlled Unclassified

Information (CUI). The contractor is not required, nor expected, to have a Facility Clearance and contractor personnel supporting this effort are not required to possess Personnel Clearance

Levels. However, any contractor personnel requiring access to U.S. Government CUI shall possess a completed background investigation (minimum of a T-1/NACI) for this Public Trust

Position.

4.3. Systems Engineering

4.3.1. Systems Engineering Technical Review (SETR)

The contractor shall participate telephonically in the Government-led SETR events, to provide answers to specific questions from the SETR team, including a System Functional Review (SFR)

/ Non-developmental Item Integration Review (NIR) for the Marine Analog Tactical Telephone, to set the system’s initial Product Baseline. The NIR is a review that provides the Government with the confidence the device’s initial Product Baseline (iPBL) is known and documented. The

Government will conduct a Test Readiness Review (TRR) to determine whether the device can proceed to demonstration and testing. The Government Technical Review Board will conduct a

Functional Configuration Audit (FCA), to audit the results of the previously mentioned testing, and a System Verification Review (SVR), to assess the system’s functionality and determine if it meets the functional requirements. Lastly, a Physical Configuration Audit (PCA) will be conducted to set the system’s final Product Baseline (PBL).

4.3.2. Safety Assessment Report (SAR)

The contractor shall conduct a safety assessment in accordance with MIL-STD-882E and deliver a Safety Assessment Report (SAR) for the WID MATT. The SAR shall have a statement signed by the contractor Program Manager stating that all hazards have been identified, eliminated, or controlled.

(CDRL A001, Safety Assessment Report)

4.4. Integrated Logistics Support

4.4.1. Provisioning Guidance Conference (PGC)

The contractor shall attend a Provisioning Guidance Conference. The Marine Corps Systems

Command (MCSC) Equipment Specialist shall chair this conference. The purpose of the meeting is to define requirements for Logistics Management Information Data Products including format and medium of delivery, addressing unique Government requirements, and discussing/resolving unclear provisioning/cataloging related areas. Other topics to be addressed may include the Reliability, Availability, and Maintainability of the material solution, Operator’s

Manual and Quick Reference Guide, and safety efforts to be executed.

(CDRL B002, Presentation Material)

(CDRL B003, Meeting Minutes)

4.4.2. Provisioning Conference

The contractor shall attend a Provisioning Conference. The contractor shall provide a minimum of one production grade system for use at the conference. Disassembly of system, by the contractor, may be required during the conference to verify all provisioning documentation, parts and assemblies are accurate. The Provisioning Conference shall be conducted concurrently with the PCA.

(CDRL B003, Meeting Minutes)

4.4.3. Logistics Product Data

The contractor must deliver Engineering Drawings sufficient for the Government’s use in conducting Logistics Provisioning. The required Logistics Product Data includes, at a minimum, Provisioning Technical Data, Provisioning Parts List and Index, Long Lead Time Item List, Common Bulk Item List, Design Change Notice, Support Equipment Recommendation Data and

Indentured Bill of Materials.

The contractor shall deliver all necessary data for the Government to update or add National

Stock Numbers (NSNs), and shall assign Source, Maintenance, and Recoverability (SM&R) codes to the WID MATT in accordance with the USMC two levels of maintenance concept

(GEIA-STD-0007 Logistics Product Data Handbook).

(CDRL D001, Logistics Product Data)

(CDRL D003, Engineering Data for Provisioning)

4.4.3.1. Provisioning Parts List (PPL)

The contractor shall develop and deliver a Provisioning Parts List (PPL) in LSA-36 format IAW

GEIA-STD-0007. The contractor shall ensure that the PPL contains the end item, components or assemblies and all support items which can be disassembled, reassembled, or replaced, and which, when combined, constitute the end item, component or assembly, and shall include items such as parts, materials, consumables, connecting cabling, mounting, and fittings required for the operation and maintenance of the end item, component, or assembly. The PPL shall be used to determine the range and depth of support items required to maintain the end item. This includes all repairable and non-repairable NDI items. The PPL shall be structured in a Top-Down

Breakdown sequence. Indenture Codes shall be in Alpha Character format. Provisioning List

Item Sequence Number (PLISN) sequencing of the PPL shall begin with Alphanumeric Codes of

A001 as the first “B” indenture PLISN, continue through A999, then B00l, and continue through

B999. All repairable items will be identified by the contractor. The PPL shall contain repair kits and repair part sets required to maintain the end item, component, or assembly.

(CDRL C001, Provisioning Parts List)

4.4.4. Technical Manual Requirements

The contractor shall develop and deliver an Operator’s Manual in electronic form that includes

Operator’s Maintenance Procedures with a Special Tools List (RPSTL) (-24P). The Government shall have unlimited rights in the Operator’s Manual.

(CDRL D002, Operator’s Manual (Manual Supplement) – User Guide)

The contractor shall also deliver a Quick Reference Guide (QRG), one overpacked as part of each WID MATT system. The QRG is intended to be a compressed operator’s manual that a

Marine can put in his or her pocket to take to the field and have quick reference instructions on how to operate and maintain the system. The Government shall have unlimited rights in the

QRG.

(CDRL D002, Quick Reference Guide (Operator’s Manual Supplement)

4.4.4.1. Technical Manual Reviews

The contractor shall support four separate reviews of the Operator’s Manual at the following stages of its development: 30% review, 60% review, 90% review, and 100% review, as defined in the text below.

30% Review - The purpose of the 30% review is to ensure the contractor is developing the publication document to USMC requirements. It is an opportunity for the Government to review the contractor/editor’s approach to the publication development and to offer guidance and direction at an early stage.

Definition of 30% - A publication shall be at the 30 % completion stage when the following items are completed. Publication Control Number (PCN) has been obtained. The structure/outline and proper format of the publication have been defined. The hyper linking approach has been established. Front matter (including warnings and cautions), most introductory and equipment descriptions have been written and placed in the appropriate chapters. Known tables and figures are complete and placed in the appropriate chapters. At a minimum, all placeholders are defined and awaiting technical content to be written.

60% Review - The purpose of the 60% review is to ensure that the manual is meeting USMC format, and all warnings and cautions are in place. At this time, Government subject matter experts review the publication for any discrepancies or inconsistencies.

Definition of 60% - A publication shall be considered at 60% when the following is completed.

All front matter (cover, title page, table of contents, warnings and cautions) is complete and placed in the appropriate places. The content of each chapter is written, including descriptions;

step-by-step procedures; tables; figures; and warnings, cautions and notes. A minimal amount of technical data may still be missing, but placeholders have been created for that data. The content in the chapters must flow in a clear and logical sequence and be written in the proper format. A table of contents is complete and correctly links to the appropriate chapter, paragraph, table or figure, etc.

90% Review - The purpose of the 90% review is to ensure that the manual is nearly complete.

At this time, Government subject matter experts review the publication for any discrepancies or inconsistencies in preparation for Validation and Verification

Definition of 90% - A publication shall be considered at 90% when the following is completed.

All front matter (cover, title page, table of contents, and warnings and cautions) is complete and placed in the appropriate places. The content of each chapter, including descriptions; step-by-step procedures; tables; figures; and warnings, cautions and notes, is written, with a minimal amount of error. Placeholders should have sufficient data in logical sequence and need only minimum corrections to be complete. The content in the chapters must flow in a clear and logical sequence and be written in the proper format. A table of contents is complete when it correctly links to the appropriate chapter, paragraph, table or figure, etc.

100% Review - The purpose of the 100% review is to ensure that the manual is complete. At this time, Government subject matter experts review the publication for any discrepancies or inconsistencies during 100% Verification.

Definition of 100% - A publication shall be considered at 100% when the following is completed. All front matter (cover, title page, table of contents, and warnings and cautions) is complete and placed in the appropriate places. The content of each chapter, including descriptions; step-by-step procedures; tables; figures; and warnings, cautions and notes, is written. The content in the chapters must flow in a clear and logical sequence and be written in the proper format. A table of contents is complete and correctly links to the appropriate chapter, paragraph, table or figure, etc. All chapter data is finalized and in place. Marines and the program office will conduct the Verification and those findings will be adjudicated and the

Operator’s Manual in electronic form will be finalized and submitted for Government Program

Office approval.

4.4.4.2. Validation and Verification (Val/Ver) Review

The purpose of the Val/Ver review is to ensure that the manual is complete. At this time, Government subject matter experts review the publication for any discrepancies or inconsistencies.

4.4.4.3. Definition of Val/Ver

A publication shall be considered validated and verified when the following is completed. All front matter (cover, title page, table of contents, and warnings and cautions) is complete and placed in the appropriate places. The content of each chapter, including descriptions; step-by-step procedures; tables; figures; and warnings, cautions and notes, is written, with a minimal amount of error.

The content in the chapters must flow in a clear and logical sequence and be written in the proper format. A table of contents is complete and correctly links to the appropriate chapter, paragraph, table or figure, etc. RPSTL (parts breakdown) data is finalized and in place. The Val/Ver review will consist of a paper review and the Operator’s Manual in electronic form on CD, to verify the linking. The contractor/editor will have received all the copyright releases at this time.

Marines will conduct the Val/Ver and those findings will be adjudicated and the Operator’s

Manual in electronic form finalized and submitted for Government Program Office approval.

4.4.5. Warranty

The contractor shall provide the standard warranty. Warranty coverage will clearly identify limitations, exclusions, and restrictions upon the intended military application, use and environmental stress that may be imposed by the tactical employment of the equipment, systems or items being acquired. Warranty shall be tracked per DFARS 252.246-7006 Warranty

Tracking of Serialized Items.

4.4.6. Copyright Release

Per DFARS 252.227-7013(d), the contractor shall provide copyright release specifically for the

QRG and the Operator’s Manual and shall identify any third party copyrighted material that will be included in any deliverable technical data or software, if applicable, and provide the required license(s) for Government use, reproduction and distribution.

4.4.7. IUID Marking and Registration

The contractor shall develop and affix Unique Item Identifier labels in accordance with the provided references and the Item Unique Identification (IUID) Implementation Plan (IP) for

WID MATT.

5. Shipping Instructions

The initial 2,080 WID MATTs that are procured will be shipped to the Artillery units at each

MEF. These assets will be shipped directly to the Initial Issue Point (IIPs) for distribution and must be fully operational with IUID tagging completed. Any delivery address updates that are required will be provided to the contractor prior to delivery. The list below provides the distribution for deliveries, by location and priority (ordered from highest to lowest):

Location IIP Address Contact DODAAC

III MEF Okinawa

Quantity - 100

MMRFFA - Distribution Management Office

MF MFORCE FED ACCT IIP MMRFFA

Bldg 401 Bay 4 Camp Kinser JA 6374

Okinawa JP 901 2100

Christine Blanchard christine.blanchard@usmc.mil

011-81-315-637-2425

MMRFFA

III MEF Hawaii

Quantity - 170

MMK105 - Distribution Management Office

Blgd 209 MCBH Kaneohe Bay

MCBH Kaneohe Bay, HI 96863-3032

Sgt Emmanuel Alexisdumas emmanuel.alexis@usmc.mil

808-257-2939

M00318

I MEF Camp Pendleton

Quantity - 760

MMC246 - Traffic Management Officer

Bldg 2262 MCB

Camp Pendleton, CA 92055-5001

MF IIP 1st Supply BN 1st MLG MMC246

Victor Martinez victor.j.martinez.ctr@usmc.mil

760-763-8588

MMC246

II MEF Camp Lejeune

Quantity - 500

MML151 - Traffic Management Officer

MF INITIAL ISSUE PROV ACCT - ERD

MML 151 Marine Corps Base

Camp Lejeune, NC 28542-5000

Richard (Rick) McElroy richard.mcelroy.ctr@usmc.mil

910-450-5540

MML151

MARFORRES New Orleans

Quantity - 470

US Marine Corps Reserve

2000 Opelousas Ave

New Orleans, LA 70114-1500

CWO3 Brian Duvall brian.duvall@usmc.mil

(504) 697-8666

M20016

Fort Sill, OK

Quantity - 40

Marine Detachment FT Sill

Bldg 741, Macomb Road

Fort Sill, OK 73503

SSgt Yazzie latisha.yazzie@usmc.mil

(580) 442-8559/6585

M54066

TBS Quantico, VA

Quantity - 40

The Basic School

24006 Montezuma Ave

Quantico, VA 22135

GySgt Mireles jose.a.mireles@usmc.mil

(703) 784-6429

M30300

6. Security Requirement

The information provided to the contractor will be unclassified and/or Controlled Unclassified

Information (CUI). The contractor is not required or expected to have a Facility Clearance and contractor personnel supporting this effort are not required to possess Personnel Clearance

Levels. Any contractor personnel requiring access to U.S. Government CUI shall possess a completed background investigation (minimum of a T-1/NACI) for this Public Trust Position.

The Company must notify the MCSC AC/S G-2 Personnel Security Office (PERSEC Office) via encrypted e-mail to MCSC_Security@usmc.mil or 703-432-3374/3952, within 24 hours, of any adverse/derogatory information associated with the 13 Adjudicative Guidelines concerning any contractor performing on this contract, if they have been issued a CAC and/or a MCSC Building

Badge.

6.1. Cyber Security

6.1.1 System Security Plan And Plans Of Action And Milestones (Ssp/Poam) Reviews

a) Within thirty (30) days of contract award, the Contractor shall make its System Security

Plan(s) (SSP(s)) for its covered contractor information system(s) available for review by the

Government at the contractor’s facility. The SSP(s) shall implement the security requirements in

Defense Federal Acquisition Regulation Supplement (DFARS) clause 252.204-7012, which is included in this contract. The Contractor shall fully cooperate in the Government s review of the

SSPs at the Contractor’s facility.

b) If the Government determines that the SSP(s) does not adequately implement the requirements of DFARS clause 252.204-7012 then the Government shall notify the Contractor of each identified deficiency. The Contractor shall correct any identified deficiencies within thirty (30) days of notification by the Government. The contracting officer may provide for a correction period longer than thirty (30) days and, in such a case, may require the Contractor to submit a plan of action and milestones (POAM) for the correction of the identified deficiencies. The

Contractor shall immediately notify the contracting officer of any failure or anticipated failure to meet a milestone in such a POAM.

c) Upon the conclusion of the correction period, the Government may conduct a follow-on review of the SSP(s) at the Contractor s facilities. The Government may continue to conduct follow-on reviews until the Government determines that the Contractor has corrected all identified deficiencies in the SSP(s).

d) The Government may, in its sole discretion, conduct subsequent reviews at the Contractor’s site to verify the information in the SSP(s). The Government will conduct such reviews at least every three (3) years (measured from the date of contract award) and may conduct such reviews at any time upon thirty (30) day’s notice to the Contractor.

(CDRL A002, SSP with POAM)

6.1.2 Compliance To Nist 800-171

a) The Contractor shall fully implement the CUI Security Requirements (Requirements) and associated Relevant Security Controls (Controls) in NIST Special Publication 800-171 (Rev. 1)

(NIST SP 800-171), or establish a SSP(s) and POA&Ms that varies from NIST 800-171 only in accordance with DFARS clause 252.204-7012(b)(2), for all covered contractor information systems affecting this contract.

b) Notwithstanding the allowance for such variation, the contractor shall identify in any SSP and

POA&M their plans to implement the following, at a minimum:

(1) Implement Control 3.5.3 (Multi-factor authentication). This means that multi-factor authentication is required for all users, privileged and unprivileged accounts that log into a network. In other words, any system that is not standalone should be required to utilize acceptable multi-factor authentication. For legacy systems and systems that cannot support this requirement, such as CNC equipment, etc., a combination of physical and logical protections acceptable to the Government may be substituted;

(2) Implement Control 3.1.5 (least privilege) and associated Controls, and identify practices that the contractor implements to restrict the unnecessary sharing with, or flow of, covered defense information to its subcontractors, suppliers, or vendors based on need-to-know principles;

(3) Implement Control 3.1.12 (monitoring and control remote access sessions) - Require monitoring and controlling of remote access sessions and include mechanisms to audit the sessions and methods.

(4) Audit user privileges on at least an annual basis;

(5) Implement:

i. Control 3.13.11 (FIPS 140-2 validated cryptology or implementation of NSA or NIST approved algorithms (i.e. FIPS 140-2 Annex A: AES or Triple DES) or compensating controls as documented in a SSP and POAM); and,

ii. NIST Cryptographic Algorithm Validation Program (CAVP) (see https://csrc.nist.gov/projects/cryptographic-algorithm-validation-program);

(6) Implement Control 3.13.16 (Protect the confidentiality of CUI at rest) or provide a POAM for implementation which shall be evaluated by the Navy for risk acceptance.

(7) Implement Control 3.1.19 (encrypt CUI on mobile devices) or provide a plan of action for implementation which can be evaluated by the Government Program Manager for risk to the program.

(CDRL A003, Record of Tier 1 Level Suppliers Receiving/Developing Covered Defense

Information)

6.1.3 Cyber Incident Response:

a) The Contractor shall, within fifteen (15) days of discovering the cyber incident (inclusive of the 72-hour reporting period), deliver all data used in performance of the contract that the

Contractor determines is impacted by the incident and begin assessment of potential warfighter/program impact.

b) Incident data shall be delivered in accordance with the Department of Defense Cyber Crimes

Center (DC3) Instructions for Submitting Media available at http://www.acq.osd.mil/dpap/dars/pgi/docs/Instructions_for_Submitting_Me.... In delivery of the incident data, the Contractor shall, to the extent practical, remove contractor-owned information from Government covered defense information.

c) If the Contractor subsequently identifies any such data not previously delivered to DC3, then the Contractor shall immediately notify the contracting officer in writing and shall deliver the incident data within ten (10) days of identification. In such a case, the Contractor may request a delivery date later than ten (10) days after identification. The contracting officer will approve or disapprove the request after coordination with DC3.

(CDRL A004, Cyber Incident Reporting)

6.1.4 Naval Criminal Investigative Service (Ncis) Outreach

The Contractor shall engage with NCIS industry outreach efforts and consider recommendations for hardening of covered contractor information systems affecting DON programs and technologies.

6.1.5 Ncis/Industry Monitoring

a) In the event of a cyber incident or at any time the Government has indication of a vulnerability or potential vulnerability, the Contractor shall cooperate with the Naval Criminal Investigative

Service (NCIS), which may include cooperation related to: threat indicators; pre-determined incident information derived from the Contractor's infrastructure systems; and the continuous provision of all Contractor, subcontractor or vendor logs that show network activity, including any additional logs the contractor, subcontractor or vendor agrees to initiate as a result of the cyber incident or notice of actual or potential vulnerability.

b) If the Government determines that the collection of all logs does not adequately protect its interests, the Contractor and NCIS will work together to implement additional measures, which may include allowing the installation of an appropriate network device that is owned and maintained by NCIS, on the Contractor's information systems or information technology assets.

The specific details (e.g., type of device, type of data gathered, monitoring period) regarding the installation of an NCIS network device shall be the subject of a separate agreement negotiated between NCIS and the Contractor. In the alternative, the Contractor may install network sensor capabilities or a network monitoring service, either of which must be reviewed for acceptability by NCIS. Use of this alternative approach shall also be the subject of a separate agreement negotiated between NCIS and the Contractor.

c) In all cases, the collection or provision of data and any activities associated with this statement of work shall be in accordance with federal, state, and non-US law.

Section D - Packaging and Marking

MARKING INSTRUCTIONS

MIL-STD-129R Military Marking for Shipment and Storage

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

MIL-STD-2073/1E Chg 1 Department of Defense (DoD) Standard Practice for Military Packaging

ASTM D3951-98 Standard Practice for Commercial Packaging

(Copies of ASTM documents are available from www.astm.org or American Society for Testing and Materials

International, 100 Barr Harbor Drive, West Conshohocken, PA 19428-2959.)

D.1 Packaging and Marking of Data

The Contractor shall be prepare data and documents for shipment in accordance with best commercial practice.

Note: All correspondence submitted to the Government must reference the Contract number and the name(s) of the

Contract Specialist and/or Contracting Officer (KO) as appropriate. A copy of all correspondence sent to the PM, COR or COTR) shall be provided to the Contracting Officer.

Deliverables provided in electronic format shall comply with the accepted standards (e.g., applications, platforms, database formats, and engineering tools) in use by MARCORSYSCOM or appropriate agency at the time of performance, unless otherwise directed by the KO. The contractor shall ensure that all deliverables and products are identified with the compliance standards prior to the start of work.

The Contractor shall be responsible for the preservation and packaging of all items to be delivered under the terms of the contract in accordance with and MIL-STD-2073/1 and guidance within ASTM D3951-98.

The Contractor shall use the fastest traceable means of transportation available for urgent shipments. For routine shipments, the Contractor shall use the most economical traceable means of transportation for routine shipments.

D.2 Item Unique Identification

The identification marking of individual parts shall be performed on modules, systems, equipment, assemblies, subassemblies, components, groups, sets or kits, and of spare and repair parts utilizing Item Unique Identification

(IUID) in accordance with DFARS 252.211-7003. All IUID marked items shall have their IUID data submitted electronically to the IUID Registry per DFARS 252.211-7007.

D.3 Marking Requirements

When hardware is required, the Contractor shall implement specific Item Unique Identification (IUID) markings, as defined in MIL-STD-130N and Defense Federal Acquisition Regulation Supplement clause 252.211-7003. IUID markings shall be applied to all qualifying items manufactured, modified or procured by the Contractor during the period of performance of this contract. The IUID marking shall be incorporated into existing data plates when possible. Bar Coding and the two-dimensional IUID data matrix shall be machine-readable with common optical scanning devices and be accompanied by the corresponding human readable markings when practical. Whenever practical, the location of the marking on the item shall ensure its readability during normal operational use.

CLAUSES INCORPORATED BY REFERENCE

252.211-7008 Use of Government-Assigned Serial Numbers SEP 2010

CLAUSES INCORPORATED BY FULL TEXT

252.211-7003 ITEM UNIQUE IDENTIFICATION AND VALUATION (MAR 2016)

(a) Definitions. As used in this clause-

Automatic identification device means a device, such as a reader or interrogator, used to retrieve data encoded on machine-readable media.

Concatenated unique item identifier means--

(1) For items that are serialized within the enterprise identifier, the linking together of the unique identifier data elements in order of the issuing agency code, enterprise identifier, and unique serial number within the enterprise identifier; or

(2) For items that are serialized within the original part, lot, or batch number, the linking together of the unique identifier data elements in order of the issuing agency code; enterprise identifier; original part, lot, or batch number;

and serial number within the original part, lot, or batch number.

Data Matrix means a two-dimensional matrix symbology, which is made up of square or, in some cases, round modules arranged within a perimeter finder pattern and uses the Error Checking and Correction 200

(ECC200) specification found within International Standards Organization (ISO)/International Electrotechnical

Commission (IEC) 16022.

Data qualifier means a specified character (or string of characters) that immediately precedes a data field that defines the general category or intended use of the data that follows.

DoD recognized unique identification equivalent means a unique identification method that is in commercial use and has been recognized by DoD. All DoD recognized unique identification equivalents are listed at http://www.acq.osd.mil/dpap/pdi/uid/iuid_equivalents.html.

DoD item unique identification means a system of marking items delivered to DoD with unique item identifiers that have machine-readable data elements to distinguish an item from all other like and unlike items. For items that are serialized within the enterprise identifier, the unique item identifier shall include the data elements of the enterprise identifier and a unique serial number. For items that are serialized within the part, lot, or batch number within the enterprise identifier, the unique item identifier shall include the data elements of the enterprise identifier; the original part, lot, or batch number; and the serial number.

Enterprise means the entity (e.g., a manufacturer or vendor) responsible for assigning unique item identifiers to items.

Enterprise identifier means a code that is uniquely assigned to an enterprise by an issuing agency.

Government's unit acquisition cost means--

(1) For fixed-price type line, subline, or exhibit line items, the unit price identified in the contract at the time of delivery;

(2) For cost-type or undefinitized line, subline, or exhibit line items, the Contractor's estimated fully burdened unit cost to the Government at the time of delivery; and

(3) For items produced under a time-and-materials contract, the Contractor's estimated fully burdened unit cost to the Government at the time of delivery.

Issuing agency means an organization responsible for assigning a globally unique identifier to an enterprise, as indicated in the Register of Issuing Agency Codes for ISO/IEC 15459, located at http://www.aimglobal.org/?Reg_Authority15459.

Issuing agency code means a code that designates the registration (or controlling) authority for the enterprise identifier.

Item means a single hardware article or a single unit formed by a grouping of subassemblies, components, or constituent parts.

Lot or batch number means an identifying number assigned by the enterprise to a designated group of items, usually referred to as either a lot or a batch, all of which were manufactured under identical conditions.

Machine-readable means an automatic identification technology media, such as bar codes, contact memory buttons, radio frequency identification, or optical memory cards.

Original part number means a combination of numbers or letters assigned by the enterprise at item creation to a class of items with the same form, fit, function, and interface.

Parent item means the item assembly, intermediate component, or subassembly that has an embedded item with a unique item identifier or DoD recognized unique identification equivalent.

Serial number within the enterprise identifier means a combination of numbers, letters, or symbols assigned by the enterprise to an item that provides for the differentiation of that item from any other like and unlike item and is never used again within the enterprise.

Serial number within the part, lot, or batch number means a combination of numbers or letters assigned by the enterprise to an item that provides for the differentiation of that item from any other like item within a part, lot, or batch number assignment.

Serialization within the enterprise identifier means each item produced is assigned a serial number that is unique among all the tangible items produced by the enterprise and is never used again. The enterprise is responsible for ensuring unique serialization within the enterprise identifier.

Serialization within the part, lot, or batch number means each item of a particular part, lot, or batch number is assigned a unique serial number within that part, lot, or batch number assignment. The enterprise is responsible for ensuring unique serialization within the part, lot, or batch number within the enterprise identifier.

Type designation means a combination of letters and numerals assigned by the Government to a major end item, assembly or subassembly, as appropriate, to provide a convenient means of differentiating between items having the same basic name and to indicate modifications and changes thereto.

Unique item identifier means a set of data elements marked on items that is globally unique and unambiguous. The term includes a concatenated unique item identifier or a DoD recognized unique identification equivalent.

Unique item identifier type means a designator to indicate which method of uniquely identifying a part has been used. The current list of accepted unique item identifier types is maintained at http://www.acq.osd.mil/dpap/pdi/uid/uii_types.html.

(b) The Contractor shall deliver all items under a contract line, subline, or exhibit line item.

(c) Unique item identifier. (1) The Contractor shall provide a unique item identifier for the following:

(i) Delivered items for which the Government's unit acquisition cost is $5,000 or more, except for the following line items:

http://www.aimglobal.org/?Reg_Authority15459

Contract line, subline, or exhibit line item No. Item description

(ii) Items for which the Government's unit acquisition cost is less than $5,000 that are identified in the Schedule or the following table:

Contract line, subline, or exhibit line item No. Item description

CLIN 0001 MATT System Test Assets

CLIN 0002 MATT System

CLIN 0003 MATT System

(iii) Subassemblies, components, and parts embedded within delivered items, items with warranty requirements, DoD serially managed reparables and DoD serially managed nonreparables as specified in Attachment Number ----.

(iv) Any item of special tooling or special test equipment as defined in FAR 2.101 that have been designated for preservation and storage for a Major Defense Acquisition Program as specified in Attachment Number ----.

(v) Any item not included in paragraphs (c)(1)(i), (ii), (iii), or

(iv) of this clause for which the contractor creates and marks a unique item identifier for traceability.

(2) The unique item identifier assignment and its component data element combination shall not be duplicated on any other item marked or registered in the DoD Item Unique Identification Registry by the contractor.

(3) The unique item identifier component data elements shall be marked on an item using two dimensional data matrix symbology that complies with ISO/IEC International Standard 16022, Information technology--International symbology specification--Data matrix; ECC200 data matrix specification.

(4) Data syntax and semantics of unique item identifiers. The Contractor shall ensure that--

(i) The data elements (except issuing agency code) of the unique item identifier are encoded within the data matrix symbol that is marked on the item using one of the following three types of data qualifiers, as determined by the

Contractor:

(A) Application Identifiers (AIs) (Format Indicator 05 of ISO/IEC International Standard 15434), in accordance with

ISO/IEC International Standard 15418, Information Technology--EAN/UCC Application Identifiers and Fact Data

Identifiers and Maintenance and ANSI MH 10.8.2 Data Identifier and Application Identifier Standard.

(B) Data Identifiers (DIs) (Format Indicator 06 of ISO/IEC International Standard 15434), in accordance with

ISO/IEC International Standard 15418, Information Technology--EAN/UCC Application Identifiers and Fact Data Identifiers and Maintenance and ANSI MH 10.8.2 Data Identifier and Application Identifier Standard.

(C) Text Element Identifiers (TEIs) (Format Indicator 12 of ISO/IEC International Standard 15434), in accordance with the Air Transport Association Common Support Data Dictionary; and

(ii) The encoded data elements of the unique item identifier conform to the transfer structure, syntax, and coding of messages and data formats specified for Format Indicators 05, 06, and 12 in ISO/IEC International Standard 15434, Information Technology-Transfer Syntax for High Capacity Automatic Data Capture Media.

(5) Unique item identifier.

(i) The Contractor shall--

(A) Determine whether to--

(1) Serialize within the enterprise identifier;

(2) Serialize within the part, lot, or batch number; or

(3) Use a DoD recognized unique identification equivalent (e.g. Vehicle Identification Number); and

(B) Place the data elements of the unique item identifier (enterprise identifier; serial number; DoD recognized unique identification equivalent; and for serialization within the part, lot, or batch number only: Original part, lot, or batch number) on items requiring marking by paragraph (c)(1) of this clause, based on the criteria provided in MIL-STD-

130, Identification Marking of U.S. Military Property, latest version;

(C) Label shipments, storage containers and packages that contain uniquely identified items in accordance with the requirements of MIL-STD-129, Military Marking for Shipment and Storage, latest version; and

(D) Verify that the marks on items and labels on shipments, storage containers, and packages are machine readable and conform to the applicable standards. The contractor shall use an automatic identification technology device for this verification that has been programmed to the requirements of Appendix A, MIL-STD-130, latest version.

(ii) The issuing agency code--

(A) Shall not be placed on the item; and

(B) Shall be derived from the data qualifier for the enterprise identifier.

(d) For each item that requires item unique identification under paragraph (c)(1)(i), (ii), or (iv) of this clause or when item unique identification is provided under paragraph (c)(1)(v), in addition to the information provided as part of the Material Inspection and Receiving Report specified elsewhere in this contract, the Contractor shall report at the time of delivery, as part of the Material Inspection and Receiving Report, the following information:

(1) Unique item identifier.

(2) Unique item identifier type.

(3) Issuing agency code (if concatenated unique item identifier is used).

(4) Enterprise identifier (if concatenated unique item identifier is used).

(5) Original part number (if there is serialization within the original part number).

(6) Lot or batch number (if there is serialization within the lot or batch number).

(7) Current part number (optional and only if not the same as the original part number).

(8) Current part number effective date (optional and only if current part number is used).

(9) Serial number (if concatenated unique item identifier is used).

(10) Government's unit acquisition cost.

(11) Unit of measure.

(12) Type designation of the item as specified in the contract schedule, if any.

(13) Whether the item is an item of Special Tooling or Special Test Equipment.

(14) Whether the item is covered by a warranty.

(e) For embedded subassemblies, components, and parts that require DoD unique item identification under paragraph (c)(1)(iii) of this clause, the Contractor shall report as part of, or associated with, the Material Inspection and Receiving Report specified elsewhere in this contract, the following information:

(1) Unique item identifier of the parent item under paragraph (c)(1) of this clause that contains the embedded subassembly, component, or part.

(2) Unique item identifier of the embedded subassembly, component, or part.

(3) Unique item identifier type.**

(4) Issuing agency code (if concatenated unique item identifier is used).**

(5) Enterprise identifier (if concatenated unique item identifier is used).**

(6) Original part number (if there is serialization within the original part number).**

(7) Lot or batch number (if there is serialization within the lot or batch number).**

(8) Current part number (optional and only if not the same as the original part number).**

(9) Current part number effective date (optional and only if current part number is used).**

(10) Serial number (if concatenated…