M67854-20-R-2025.docx

M6785420R2025

Section B - Supplies or Services and Prices

Portable SATCOM Terminal (PST)

FFP

In accordance with (IAW) Statement of Work (SOW) Section 3.1 and Attachment 1 - Performance Specifications (P-Spec). Ordering Period 1.

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: D304

MAX

NET AMT

Initial Issue Provisioning (IIP) Kit

IAW SOW Section 3.2 and P-Spec. Ordering Period 1.

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.

MAX

See Exhibit K

IAW Exhibit K - Spare Parts Pricing Matrix. Ordering Period 1.

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.

MAX

Technical Data

Exhibits A, C, E and F and SOW Section 3.3. Not Separately Priced. Ordering Period 1.

PSC CD: R699

MAX

Portable SATCOM Terminal

IAW SOW Section 3.1 and Attachment 1 - P-Spec. Ordering Period 2.

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.

MAX

Initial Issue Provisioning Kit

IAW SOW Section 3.2 and P-Spec. Ordering Period 2.

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.

MAX

See Exhibit K

IAW Exhibit K - Spare Parts Pricing Matrix. Ordering Period 2.

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.

MAX

Technical Data

Exhibits A, C, E and F and SOW Section 3.3. Not Separately Priced. Ordering Period 2.

MAX

Portable SATCOM Terminal

IAW SOW Section 3.1 and Attachment 1 - P-Spec. Ordering Period 3.

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.

MAX

Initial Issue Provisioning Kit

IAW SOW Section 3.2 and P-Spec. Ordering Period 3.

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.

MAX

See Exhibit K

IAW Exhibit K - Spare Parts Pricing Matrix. Ordering Period 3.

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.

MAX

Technical Data

Exhibits A, C, E and F and SOW Section 3.3. Not Separately Priced. Ordering Period 3.

MAX

Portable SATCOM Terminal

IAW SOW Section 3.1 and Attachment 1 - P-Spec. Ordering Period 4.

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.

MAX

Initial Issue Provisioning Kit

IAW SOW Section 3.2 and P-Spec. Ordering Period 4.

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.

MAX

See Exhibit K

IAW Exhibit K - Spare Parts Pricing Matrix. Ordering Period 4.

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.

MAX

Technical Data

Exhibits A, C, E and F and SOW Section 3.3. Not Separately Priced. Ordering Period 4.

MAX

Portable SATCOM Terminal

IAW SOW Section 3.1 and Attachment 1 - P-Spec. Ordering Period 5.

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.

MAX

Initial Issue Provisioning Kit

IAW SOW Section 3.2 and P-Spec. Ordering Period 5.

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.

MAX

See Exhibit K

IAW Exhibit K - Spare Parts Pricing Matrix. Ordering Period 5.

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.

MAX

Technical Data

Exhibits A, C, E and F and SOW Section 3.3. Not Separately Priced. Ordering Period 5.

MAX

CONTRACT MINIMUM/MAXIMUM QUANTITY AND CONTRACT VALUE

The minimum quantity and contract value for all orders issued against this contract shall not be less than the minimum quantity and contract value stated in the following table. The maximum quantity and contract value for all orders issued against this contract shall not exceed the maximum quantity and contract value stated in the following table.

MINIMUM

QUANTITY

MINIMUM

AMOUNT

MAXIMUM

QUANTITY

MAXIMUM

AMOUNT

$10,000,000.00

$87,712,000.00

CLIN DELIVERY/TASK ORDER MINIMUM/MAXIMUM QUANTITY AND CLIN ORDER VALUE

The minimum quantity and order value for the given Delivery/Task Order issued for this CLIN shall not be less than the minimum quantity and order value stated in the following table. The maximum quantity and order value for the given Delivery/Task Order issued for this CLIN shall not exceed the maximum quantity and order value stated in the following table.

CLIN

MINIMUM

QUANTITY

MINIMUM

AMOUNT

MAXIMUM

QUANTITY

MAXIMUM

AMOUNT

Section C - Descriptions and Specifications

STATEMENT OF WORK

STATEMENT OF WORK

1. SCOPE OF WORK

This Statement of Work (SOW) defines the efforts required for the delivery of the Marine Corps Wideband Satellite – Expeditionary (MCWS-X) satellite terminals, spare parts, provisioning data, commercial technical manual(s), and training materials.

1.1. Background

MCWS-X is a man-packable, multiband (X, Ku, Ka) Super High Frequency (SHF), multi-waveform satellite communications (SATCOM) terminal capable of being transported by one Marine, and being set-up by that Marine in under 15 minutes. The MCWS-X provides throughput rates up to at least 2 Megabits per second (Mbps) and, objectively, up to 10 Mbps, and utilizes waveforms that are backward compatible with legacy Marine Corps Satellite Communications (SATCOM) systems and Department of Defense (DoD) Enterprise SATCOM Gateways, and forward compatible with future upgrades planned to implement the Protected Tactical Waveform (PTW).

2. APPLICABLE DOCUMENTS

The following documents specified form a part of this SOW to the extent specified herein. The most recent revision 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.

2.1 Government Documents

The following specifications, standards, and handbooks form a part of this document to the extent specified herein and are contained in the table below. Copies of the documents should be obtained from the ASSIST database at http://quicksearch.dla.mil/. ASSIST is the official source for all Defense Standardization Program documents and contains the most current information. An ASSIST Update (a bi-monthly summary of changes to the ASSIST document database) may be viewed or downloaded at Uniform Resource Locator (URL): https://quicksearch.dla.mil/qsSearch.aspx.

Requests for copies of Occupational Safety and Health Agency (OSHA) references should be addressed to the Department of Labor, OSHA, Washington, DC 20210. Requests for copies of National Security Agency (NSA) references should be addressed to National Security Telecommunications and Information Systems Security Committee (NSTISSC) Secretariat (V503), NSA, 9800 Savage Road STE 6716, Fort Meade, MD 20755-6716. Request for copies of MCWS-X documentation should be addressed to Marine Corps Systems Command, 2200 Lester St., Quantico, VA 22134, ATTN: PM Communications Systems.

*NOTE: If a newer version exists at the time of contract award, that version will apply instead.

2.2 Non-Government Documents – Information

3. REQUIREMENTS

The contractor shall perform all tasks required by, and delineated in, this SOW to manufacture and deliver the MCWS-X systems as well as to prepare associated documentation. The contractor shall deliver all materials, equipment, hard tooling, personnel, and facilities necessary to perform the tasks listed in this SOW, and to deliver the types and quantities of deliverables specified by the contract.

The contractor shall deliver all Contract Data Requirements Lists (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.

3.1 MCWS-X System

The contractor shall deliver complete integrated MCWS-X systems in accordance with the performance specifications at Attachment 1.

3.2 MCWS-X Spares

3.2.1 MCWS-X Initial Issue Provisioning

The contractor shall deliver spare Lowest Replaceable Units (LRUs), expendables, and consumables to form Initial Issue Provisioning (IIP) Kits sufficient to support each system for 2 years.

3.2.2 MCWS-X Spares List

The contractor shall deliver spare LRUs, expendables, and consumables in accordance with Exhibit K.

3.3 Program and Data Management

3.3.1 Travel

The contractor shall be responsible for all travel costs for its own personnel for all travel associated with the execution of this SOW. Travel costs will not be reimbursed by the Government.

3.3.2 Security Requirements

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

3.3.3 System Security Plan and Plans of Action and Milestones (SSP/POAM) Reviews Within 30 days of contract award, the contractor shall deliver its System Security Plan(s) (SSP(s)) for its covered contractor information system(s) for review by the Government in electronic format. The SSP(s) shall implement the security requirements in Department of Defense (DoD) 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.

If the Government determines that the SSP(s) does not adequately implement the requirements of DFARS clause 252.204-7012, the Government shall notify the contractor of each identified deficiency. The contractor shall correct any identified deficiencies within 30 days of notification by the Government. The contracting officer may provide for a correction period longer than 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.

Upon the conclusion of the correction period, the Government may conduct a follow-on review of the SSP(s), remotely or 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).

The Government may, at 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 3 years (measured from the date of contract award) and may conduct such reviews at any time upon 30 days’ notice to the contractor.

(CDRL A001 – System Security Plan (SSP) and Associated Plans of Action for a Contractor’s Internal Unclassified Information System)

3.3.4 Compliance to National Institute of Standards and Technology (NIST) SP 800-171 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), and establish a SSP(s) indicating compliance with associated POAMs 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.

Notwithstanding the allowance for such variation, the contractor shall identify, in the SSP and POAM, their plans to implement the following, at a minimum:

· 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;

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

· 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.

· Privilege Auditing. Audit user privileges on at least an annual basis;

· 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,

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

· 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.

· 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.

3.3.5 Cyber Incident Response:

The contractor shall, within 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.

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_Media.docx. In delivery of the incident data, the contractor shall, to the extent practical, remove contractor-owned information from Government covered defense information.

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 10 days of identification. In such a case, the contractor may request a delivery date later than 10 days after identification. The contracting officer will approve or disapprove the request after coordination with DC3.

(CDRL A002 – Cyber Incident Reporting for a Contractor’s Internal Unclassified Information System)

3.3.6 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 Department of the Navy (DON) programs and technologies.

3.3.7 NCIS/Industry Monitoring

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.

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.

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.

3.3.8 Contractor’s Record of Tier 1 Level Suppliers who Receive or Develop Covered Defense Information The contractor shall supply record of Tier 1 Level Suppliers who receive or develop Covered Defense Information. The contractor shall deliver its plan to track flow down of covered defense information and to assess DFARS Clause 252.204-7012 compliance of known Tier 1 Level suppliers.

(CDRL A003 – Contractor's Record of Tier 1 Level Suppliers Receiving/Developing Covered Defense Information)

3.3.9 Radio Frequency Spectrum Compatibility

Per the Equipment Location – Certification Information Database (EL-CID) process, the contractor shall complete and deliver the EL-CID Cut Sheet Template provided for obtaining an approved frequency for the MCWS-X system.

(CDRL A004, Technical Report – Study/Services (Applications for Equipment Frequency Allocation)

3.3.10 Logistics Product Data

The contractor shall develop and deliver a Provisioning Parts List (PPL). The contractor shall ensure that the PPL contains the end item; components or assemblies; and all support items that can be disassembled, reassembled, or replaced. The PPL shall include all support items which, when combined, constitute the end item, component, or assembly. The PPL 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 indicate the range and depth of support items required to maintain the end item. The PPL shall include all repairable and non-repairable Commercial Off-the-Shelf (COTS) 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, Logistics Product Data)

3.3.11 Commercial Technical Manuals

The contractor shall deliver commercial manuals sufficient to provide Marines with a thorough knowledge and understanding of MCWS-X system set up and tear down, storage, operation, preventive maintenance, corrective maintenance (if possible), troubleshooting, and safety information. Note the requirements of DFARS 252.227-7013(d), regarding requirements for third party copyrighted works provided as part of the deliverables.

(CDRL E001, Commercial Technical Manual)

3.3.12 Training Instruction

The contractor shall deliver commercial training materials sufficient to provide Marines with a thorough knowledge and understanding of MCWS-X system set up and tear down, storage, operation, preventive maintenance, corrective maintenance (if possible), troubleshooting procedures, and safety information.

(CDRL F001, Training Data Products)

3.3.14 Commercial 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. The contractor shall ensure that subcontractor and/or contractor warranties provide the same coverage for all end items.

Section D - Packaging and Marking

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:

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

TBD

(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

TBD

(If items are identified in the Schedule, insert ``See Schedule'' in this table.)

(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 unique item identifier is used).**

(11) Description.

** Once per item.

(f) The Contractor shall submit the information required by paragraphs (d) and (e) of this clause as follows:

(1) End items shall be reported using the receiving report capability in Wide Area WorkFlow (WAWF) in accordance with the clause at 252.232-7003. If WAWF is not required by this contract, and the contractor is not using WAWF, follow the procedures at http://dodprocurementtoolbox.com/site/uidregistry/.

(2) Embedded items shall be reported by one of the following methods--

(i) Use of the embedded items capability in WAWF;

(ii) Direct data submission to the IUID Registry following the procedures and formats at http://dodprocurementtoolbox.com/site/uidregistry/; or

(iii) Via WAWF as a deliverable attachment for exhibit line item number (fill in) ----, Unique Item Identifier Report for Embedded Items, Contract Data Requirements List, DD Form 1423.

(g) Subcontracts. If the Contractor acquires by subcontract any items for which item unique identification is required in accordance with paragraph (c)(1) of this clause, the Contractor shall include this clause, including this paragraph (g), in the applicable subcontract(s), including subcontracts for commercial items.

(End of clause)

Section E - Inspection and Acceptance

INSPECTION AND ACCEPTANCE TERMS

Supplies/services will be inspected/accepted at:

CLAUSES INCORPORATED BY REFERENCE

Section F - Deliveries or Performance

DELIVERY INFORMATION

Section G - Contract Administration Data

CONTRACT ADMINISTRATION

Contract Specialist:

Lisa J. Bennett Marine Corps Systems Command (MCSC) 2200 Lester Street Quantico, VA 22134 Telephone: (703) 432-8722 Email: lisa.bennett@usmc.mil

Project Officer:

Hannah G. Rowlette Marine Corps Systems Command (MCSC) 2200 Lester Street Quantico, VA 22134 Telephone: (703) 432-9953 Email: hannah.rowlette1@usmc.mil

All Contract Data Requirements List (CDRL) deliverables shall be delivered to the Project Officer (PO) indicated above. The PO is responsible for tracking and acceptance.

INDENTIFICATION OF CONTRACTOR EMPLOYEES

Contractor employees shall identify themselves as contractor personnel by introducing themselves or being introduced as contractor personnel and displaying distinguishing badges or other visible identification for meetings with Government personnel. In addition contractor personnel shall appropriately identify themselves as contractor employees in telephone conversations and in formal and informal written correspondence.

Section I - Contract Clauses

52.204-21 BASIC SAFEGUARDING OF COVERED CONTRACTOR INFORMATION SYSTEMS (JUN 2016)

(a) Definitions. As used in this clause--

Covered contractor information system means an information system that is owned or operated by a contractor that processes, stores, or transmits Federal contract information.

Federal contract information means information, not intended for public release, that is provided by or generated for the Government under a contract to develop or deliver a product or service to the Government, but not including information provided by the Government to the public (such as on public Web sites) or simple transactional information, such as necessary to process payments.

Information means any communication or representation of knowledge such as facts, data, or opinions, in any medium or form, including textual, numerical, graphic, cartographic, narrative, or audiovisual (Committee on National Security Systems Instruction (CNSSI) 4009).

Information system means a discrete set of information resources organized for the collection, processing, maintenance, use, sharing, dissemination, or disposition of information (44 U.S.C. 3502).

Safeguarding means measures or controls that are prescribed to protect information systems.

(b) Safeguarding requirements and procedures.

(1) The Contractor shall apply the following basic safeguarding requirements and procedures to protect covered contractor information systems. Requirements and procedures for basic safeguarding of covered contractor information systems shall include, at a minimum, the following security controls:

(i) Limit information system access to authorized users, processes acting on behalf of authorized users, or devices (including other information systems).

(ii) Limit information system access to the types of transactions and functions that authorized users are permitted to execute.

(iii) Verify and control/limit connections to and use of external information systems.

(iv) Control information posted or processed on…