Attach-8_SOW.Template_REV_07.25.2023.docx

This document must be completed as specified below as part of the proposal submission. Do not delete any portion of this document.

All pages shall be formatted for printing on 8-1/2 by 11-inch paper with 1-inch margins and font size not smaller than 11 point. Font sizes not smaller than 8 point may be used for figures, tables, and charts.

The document must be in .docx format. Submissions must be written in English. No page limit has been specified for the Draft Statement of Work document; however, brevity is preferred. The draft document must be editable by the Government in support of negotiations if the offer is considered as an award candidate.

Remove these instructions prior to saving and sending the document.

Guidance for use in completing the document:

The Government intends to incorporate the proposed Draft Statement of Work (SOW), potential revisions through negotiations, into the resulting project award; therefore, the offeror shall propose it as a separate and distinct volume in the submission. The proposed SOW shall NOT contain any cost or pricing information. The offeror shall only submit cost or pricing information in the cost proposal – separate from the technical proposal or the SOW. In addition, the offeror shall not include any proprietary data or classified information in the SOW.

The intended approach for developing SOW content is to address the requested information ensuring the intent for work activity is adequately represented, but not so detailed as to limit performance to a restrictively defined approach and/or deliverable(s).

The offeror shall define tasks in the SOW per the intended approach, and the offeror may use as many pages as necessary to adequately describe the tasks. However, the offeror must not define the tasks in so much detail that the SOW encumbers flexibility in execution of in-scope research. The ability to achieve the results from a task should not be unduly constrained by the verbiage of the task description.

When describing the work to be performed, the offeror should construct statements in the SOW in “active voice”. The offeror shall format the SOW using the same font size, margins, etc. as the technical proposal and adhere to the following guidance for the nomenclature in the SOW:

Contractor/Performer: Use “contractor” whenever referring to any action to be performed by an industry or academia offeror or subcontractor to the offeror for a contract award. If the offeror is a Government entity or an OTA agreement vs. contract is used, use the term “performer” in lieu of “contractor.”

Government: Use “Government” whenever referring to any action to be performed by the Government, including the TRMC, the T&E/S&T Program Office, the Army Contracting Command, the Executing Agent, or any Government transition partner. “Government” should not refer to any offeror submitting from a Government entity.

Shall/Must: Use “shall” whenever the work statement expresses a binding provision or contractual requirement, e.g., “The contractor shall design an on-board sensor array capable of operating in a high-powered microwave environment.”

Should: Use “should” to indicate a preferred or recommended course of action but not necessarily required course of action, e.g., “The contractor should consider various candidate materials to develop shielding techniques for the on-board sensor array.”

May: Use “may” to indicate a course of action is permissible within the limits of the SOW, e.g., “The contractor may test candidate materials in their laboratory to determine which is most ideal for shielding.”

Will: Use “will” whenever no contractor requirement is involved, to make an explanatory statement or to indicate an obligation on the part of the Government, e. g., “The Government will supply electrical power to the on-board sensor array.”

Regarding SOW template content, where instructions are provided using the following convention, [Insert contract/agreement number], replace the bracketed content with the identified information. The replaced content is not italicized.

Note that two header sections are included in the SOW, A. Technical Elements, and B. Administrative Elements. The offeror will update the specified Technical Elements sections based upon the proposed solution.

The provided structure is a template format for Offeror use to add and expand needed content as required with additional subsections, if needed.

Pay particular attention to information requirements for the following:

The offeror shall segregate the work effort into the phases proposed and indicate each anticipated end-of-phase TRL. The offeror shall outline each major task in a separately numbered subparagraph that also delineates, by subtask, the work to be performed and the deliverable items. The offeror shall clearly write the tasks to be definite and realistic. The offeror shall propose exit criteria for each phase, defining goals or milestones to be achieved before the Government authorizes proceeding to the next phase. The offeror shall ensure that the proposed exit criteria for each phase match that defined in the Technology Maturity Approach section of the Technical Proposal.

For completing content for A.3.0 TASKS AND EXIT CRITERIA:

At the beginning of each phase sections for task descriptions, the offeror shall provide a very brief overview summary of the work performed (i.e., goals to be achieved) during this phase to create context for separately listed tasks and subtasks or elements below. If the technical proposal offered a primary approach with risk-mitigated alternatives as required, a high level overview of the ‘priced’ approach(es) should be briefly identified in this paragraph.

The offeror shall describe tasks aligned with incremental goals and results required for progression. After negotiation, these tasks will become binding upon project award. Therefore, the offeror should organize the task progression with succinct content to establish the feasibility of accomplishing the overall project goals.

Task/subtask descriptions should be a brief discussion of the activity to be accomplished focused on the outcome vs. approach of each. For each defined task/subtask provide:

· Identification of any tasks/subtasks that will be performed on campus at a university.

· Identification (by name) of the primary organization (prime contractor, sub-awardee(s), consultant(s)) responsible for task/subtask execution.

· Identification of the proposed classification for each task/subtask.

· For all tasks and subtasks proposed to be unclassified, identify if the task/subtask is proposed as controlled unclassified information (CUI).

· Where applicable, a measurable milestone (e.g., a design review, deliverable, demonstration, or other event/activity that marks task completion).

Phase (or major milestone) exit criteria shall identify specific measurable metrics as basis for phase completion and readiness to continue to the next phase.

For completing content for A.4.0 DELIVERABLES:

SOW section 4.1 Deliverables Hardware/Software/Data is intended to capture items that occur ONLY in a particular phase. Note that interim hardware and software deliverables (as proof of concept, breadboard, and brassboard creations) should be identified in this section as well as reports, presentations, and documents associated with phase activities. Also note guidance in the template document. Reports required through the duration of the contract should be listed in section 4.3 Reporting Requirements and Related Deliverables. Section 4.4 provides directions to provide a tabular summary of specified content from sections 4.1 and 4.3.

SOW section 4.2 Documentation Markings and Transmittals show required language, some with YELLOW highlighted text. If the award is via other transaction authority, this language will need to be modified. If via a FAR-based award, remove the yellow highlights and use text as is. This is also applicable to text in section 4.3.

For all B ADMINISTRATIVE ELEMENTS and the Appendix: This is required content. Except for the item discussed in the next paragraph, the offeror makes NO changes to these sections, which is the currently used language for the component administrative SOW sections. This is provided for the Offeror’s understanding of SOW administrative requirements for contract award.

Find section B 2.0 regarding “Program Security” and look for the BLUE highlighted text. The Offeror shall update each of the affected sentence with the correct terms as applicable to the project’s technology development requirements.

If the Offeror goes into negotiations with the Government, the Administrative Elements sections may be updated with more recent content revisions during the process of refining the document for award.

Note that language in section B 4.0 references contracts and FAR-based paradigms. Section B 4.0 will be modified accordingly for OTA agreements made vs. FAR-based contracts.

END OF INSTRUCTIONS

ATTACHMENT 8: W900KK-22-R-0012

INSTRUCTIONS: DRAFT STATEMENT OF WORK TEMPLATE

i TRMC T&E/S&T BAA Attachment 8 Instructions: 3

TEST & EVALUATION/SCIENCE & TECHNOLOGY (T&E/S&T)

[Insert TTA Name and (acronym)]

[Insert Project Name and (Acronym)]

[Insert contract/agreement number]

STATEMENT OF WORK

[dd MONTH yyyy]

Controlled By: OSD TRMC T&E/S&T Program CUI Category: SP-PROCURE Limited Dissemination Control: FEDCON POC: [Insert Executing Agent Name, phone number]

CUI//SP-PROCURE//FEDCON

Revision History

Proposal Volume 2 Initial Draft

[Insert contract/agreement number] Statement of Work [Insert dd Month yyyy]

W900KK-19-C-0033

Statement of Work 22 February 2019 i

TABLE OF CONTENTS

[Insert contract/agreement number] Statement of Work [Insert dd Month yyyy] ii

CUI//SP-PROCURE//FEDCON

TECHNICAL ELEMENTS

OVERVIEW

Objective [The offeror shall provide a brief overview of the technology development effort, including why it is being pursued, what is intended to be accomplished, and what aspect of the test technology need is being addressed.] Scope [The offeror shall outline the general bounds of the technology development effort, including the goals, anticipated Technology Readiness Level advancements, major milestones, key characteristics, and other project descriptors. The scope shall be defined in general terms to allow for effective ‘in-scope’ change management actions.] Background [The offeror shall reference this BAA, the proposed domain and research topic, and the T&E Need and the S&T Challenge of the proposed effort. The offeror shall include any information, explanations, or constraints necessary to understand the technical requirements presented in the remaining technical sections of the SOW. The offeror may include techniques previously tried and found ineffective. The offeror shall identify appropriate specifications, standards, and other documents applicable to the effort.] DPAS Rating In accordance with DODM 4400.1 and 15 CFR 700, the requirement associated with this SOW has a Defense Priorities and Allocations System (DPAS) priority rating of: [Select appropriate rating: None; DO, critical to National Defense; DX, Highest National Defense Urgency.]

TECHNICAL PERFORMANCE GOALS

[Use the following language as boilerplate for addressing project performance goals development and resolution.] The submitted contract technical proposal identifies technical performance goals associated with the primary intended technology development approach. These goals are based upon both meeting topic expectations for a demonstration prototype assuming trade-space allowances across multiple performance parameters, and projecting performance for each assessed parameter for its prioritized optimization. These goals will be reviewed with the transition partners at the project kick-off meeting, further investigated during concept development, refined at the system requirements review (SRR), and finalized as development requirements at the final design review (FDR).

TASKS/EXIT CRITERIA BY PHASE

Phase 1 Phase 1 Tasks [The offeror shall provide a very brief overview summary of the work performed during this phase to create context for separately listed tasks and subtasks or elements below. If the technical proposal offered a primary approach with risk-mitigated alternatives as required, a high level overview of the ‘priced’ approach(es) should be briefly identified in the paragraph.]

(1) [Identify/briefly describe task 1]

(a) [Identify/briefly describe subtask 1]

(b) [Identify/briefly describe subtask 2]

(2) [Identify/briefly describe task 2]

(a) [Identify/briefly describe subtask 1]

(b) [Identify/briefly describe subtask 2] Phase 1 Exit Criteria

· [Identify required activity/event/demonstration/milestone and related measurable TRL metric(s) as a defined goal needed to indicate readiness to proceed to the next contractual milestone or phase/option]

· [Identify required activity/event/demonstration/milestone and related measurable TRL metric(s) as a defined goal needed to indicate readiness to proceed to the next contractual milestone or phase/option] Phase 2 Phase 2 Tasks [The offeror shall provide a brief overview summary of the work performed during this phase to create context for separately listed tasks and subtasks or elements below. If the technical proposal offered a primary approach with risk-mitigated alternatives as required, a high-level overview of the ‘priced’ approach(es) should be briefly identified in the paragraph.]

(1) [Identify/briefly describe task 1]

(a) [Identify/briefly describe subtask 1]

(b) [Identify/briefly describe subtask 2]

(2) [Identify/briefly describe task 2]

(a) [Identify/briefly describe subtask 1]

(b) [Identify/briefly describe subtask 2] Phase 2 Exit Criteria

· [Identify required activity/event/demonstration/milestone as a defined goal needed to indicate readiness to proceed to the next contractual milestone or phase/option]

· [Identify required activity/event/demonstration/milestone as a defined goal needed to indicate readiness to proceed to the next contractual milestone or phase/option] Phase 3 Phase 3 Tasks [The offeror shall provide a brief overview summary of the work performed during this phase to create context for separately listed tasks and subtasks or elements below. If the technical proposal offered a primary approach with risk-mitigated alternatives as required, a high-level overview of the ‘priced’ approach(es) should be briefly identified in the paragraph.]

(1) [Identify/briefly describe task 1]

(a) [Identify/briefly describe subtask 1]

(b) [Identify/briefly describe subtask 2]

(2) [Identify/briefly describe task 2]

(a) [Identify/briefly describe subtask 1]

(b) [Identify/briefly describe subtask 2] Phase 3 Exit Criteria

· [Identify required activity/event/demonstration/milestone as a defined goal needed to indicate readiness to proceed to the next contractual milestone or phase/option]

· [Identify required activity/event/demonstration/milestone as a defined goal needed to indicate readiness to proceed to the next contractual milestone or phase/option]

DELIVERABLES

Hardware/Software/Data/Documentation Phase 1

· [List the hardware/software/data/documentation (including analysis, plans, presentations, reviews, and reports) based on technology development activities during this phase. Ensure the list of deliverables matches that in the Deliverables section of the Technical and Cost Proposals. Indicate any deliverable for which data rights are being asserted.]

· [List the hardware/software/data (including analysis, plans, presentations, and reports) based on technology development activities during this phase. Ensure the list of deliverables matches that in the Deliverables section of the Technical and Cost Proposals. Indicate any deliverable for which data rights are being asserted.] Phase 2

· [List the hardware/software/data/documentation (including analysis, plans, presentations, reviews, and reports) based on technology development activities during this phase. Ensure the list of deliverables matches that in the Deliverables section of the Technical and Cost Proposals. Indicate any deliverable for which data rights are being asserted.]

· [List the hardware/software/data (including analysis, plans, presentations, reviews, and reports) based on technology development activities during this phase. Ensure the list of deliverables matches that in the Deliverables section of the Technical and Cost Proposals. Indicate any deliverable for which data rights are being asserted.] Phase 3

· [List the hardware/software/data/documentation (including analysis, plans, presentations, reviews, and reports) based on technology development activities during this phase. Ensure the list of deliverables matches that in the Deliverables section of the Technical and Cost Proposals. Indicate any deliverable for which data rights are being asserted.]

· [List the hardware/software/data/documentation (including analysis, plans, presentations, reviews, and reports) based on technology development activities during this phase. Ensure the list of deliverables matches that in the Deliverables section of the Technical and Cost Proposals. Indicate any deliverable for which data rights are being asserted.] Documentation Markings and Transmittals [Include the following standard statement for FAR awarded contracts or equivalent language for OT award compliance where highlighted in yellow below.] The contractor shall mark all technical documentation deliverables as indicated in Block 9 of the Contract Data Requirements Lists (CDRLs). For all documentation, the contractor shall propose the appropriate controlled unclassified information (CUI) category and limited dissemination controls per guidance found at CUI Categories | National Archives with Distribution Statements in accordance with Department of Defense Directive 5230.24. Note: CUI categories, limited dissemination, and CTI distribution statements may be altered by the Contracting Officer’s Representative (COR). [At minimum applicable documents shall be designated as CUI-Controlled Technical Information (CTI) with ‘FEDCON’ Limited Dissemination and initially as Distribution Statement C unless Offeror recommends more restrictive limited dissemination and CTI distribution statements. Other CUI categories may also apply, such as Export Controlled Research (EXPTR) or Unclassified Controlled Nuclear Information-Defense (DCNI)].

At the completion of the contract, the contractor shall submit a transmittal letter for each separately transferred deliverable specifically stating the data rights are held by the Government. The Government holds unlimited data rights, unless specified otherwise in the items enumerated under phase deliverables.

Project Reporting Requirements and Related Deliverables [Below items are the minimal reporting requirements; others may apply.] Monthly Status Reports (MSR) The contractor shall deliver a Monthly Status Reports (MSR) to the EA in accordance with the CDRL. The MSR shall detail the accomplishments and expenditures of the project over the reporting period, upcoming major events, timely issue identification, and voucher submissions (amount and date) for payment with payment status for the project in accordance with the Data Item Description (DI-MGMT-81928) and per the Government format template provided upon award.

Quarterly Material/Property Disposition Report (QMPR) The contractor shall deliver Quarterly Material/Property Disposition Reports (QMPR) to the Contracting Officer in accordance with the CDRL. The QMPR shall detail the disposition of all purchased and acquired Contractor Acquired Property (CAP) as either stored, in use during development, consumed, destroyed, or subsumed as a component into an end item for project testing or as in interim or end item hardware deliverable (as a minimum). The report shall also report on status of any accepted Government Furnished Property (GFP) with an emphasis on condition, location, and whether intact as received or if modified or integrated into project hardware deliverables. This report correlates to requirements in accordance with the Data Item Description (DI-MGMT-80411) and per the Government format template provided upon award.

Software Product Deliverable Submissions (SPDS) This applies to all software products produced within the project and listed within section 4.2. This includes products that are classified within the terms “Computer Databases,” “Computer Software” and “Computer Software Documentation,” and “Technical Data” as defined within the associated BAA documents. The contractor shall deliver SPDs as specified within SOW phase deliverables in accordance with the CDRL. Each SPD submission shall include a transmittal letter for each separately transferred deliverable specifically stating the data rights are held by the Government. The Government holds unlimited data rights, unless specified otherwise in the items enumerated under phase deliverables. These CDRL submissions correlate to requirements in accordance with the Data Item Description (DI-IPSC-81441A) and per any provided Government format templates provided, if identified, prior to the software product development tasks.

Phase and Final Technical Reports The contractor shall deliver a draft report prior to the end of each phase in accordance with the CDRL detailing the work performed and results of each phase. A final version of the report shall be delivered prior to close of the last awarded phase of the contract, defined in this case as either the original intended final phase or end of current phase when EA makes the determination to not exercise subsequent phases. The report shall be drafted in accordance with the Data Item Description (DI-MISC-80711A) and per the Government format template provided upon award.

Final Report Delivery The contractor shall deliver a final DD Form 250 for the program concurrent with final submission of the final report. The final DD Form 250 shall be signed by the EA to close the project after all testing, deliveries and closeout activities are completed to the satisfaction of the Government.

Summary Schedule of Deliverables [This section should address intended deliverables previously discussed in one single tabular summary for convenience of completeness reviews.

This section shall also include all project high-level reporting requirement deliverables as defined in template section 4.3. It may also include other high-level reporting deliverables that may be deemed necessary by the Government based on review of the offeror submission.

This section should also include from section A 4.1 any ‘finalized’ hardware/software/data/documentation for Government acceptance and use intended as an ‘end-item’ beyond project execution (and that requires submission of DD250(s)). It may include items submitted for Government acceptance and use prior to completion of the contract/agreement. This should not include hardware/software/data/documentation that is identified in section 4.1 but is used as interim project submissions focused on developmental, incremental milestone achievement within execution of the project.

An example tabular format shown below should be used to aggregate the above listed deliverable requirements]

CDRL xxxx

(if applicable) CDRL xxxx

ADMINISTRATIVE ELEMENTS

REIMBURSEMENT OF TRAVEL, PER DIEM, AND SPECIAL MATERIAL COSTS

Area of Travel. Performance under this contract may require travel by contractor personnel. If travel, domestic or overseas, is required, the contractor is responsible for making all necessary arrangements for its personnel. These include but are not limited to medical examinations, immunizations, passports/visas/etc., and security clearances.

Travel Policy. The Government will reimburse the contractor for allowable travel costs incurred by the contractor in performance of the contract in accordance with FAR Subpart 31.205-46. Travel required by tasks assigned under this contract shall be governed in accordance with: Federal Travel Regulations (FTR), prescribed by the General Services Administration, for travel in the contiguous United States; Joint Travel Regulation (JTR), Volume 2, DoD Civilian Personnel, Appendix A, prescribed by the Department of Defense, for travel in Alaska, Hawaii, and other outlying areas of the United States; and Standardized Regulations (SR) (Government Civilians, Foreign Areas), Section 925, “Maximum Travel Per Diem Allowances for Foreign Areas,” prescribed by the Department of State, for travel in areas not covered by FTR and JTR.

Travel. Travel and subsistence are authorized for travel beyond a fifty-mile radius of the contractor’s office whenever a task assignment requires work to be accomplished at a temporary alternate worksite. No travel or subsistence shall be charged for work performed within a fifty-mile radius of the contractor’s office. The contractor shall not be paid for travel or subsistence for contractor personnel who reside in the metropolitan area in which the tasks are being performed. Travel performed for personal convenience, in conjunction with personal recreation, or daily travel to and from work at the contractor’s facility will not be reimbursed.

(1) For travel costs other than described in paragraph (c) above, the contractor shall be paid on the basis of actual amount paid to the extent that such travel is necessary for the performance of services under the contract and is authorized by the COR in writing.

(2) When transportation by privately owned conveyance is authorized, the contractor shall be paid on a mileage basis not to exceed the applicable Government transportation rate as contained in the JTR or SR. Authorization for the use of privately owned conveyance shall be indicated in the basic contract. Distances traveled between points shall be shown on invoices as listed in standard highway mileage guides. Reimbursement will not exceed the mileage shown in the standard highway mileage guides.

(3) The contractor agrees, in the performance of necessary travel, to use the lowest cost mode commensurate with the requirements of the mission as set forth in the basic. When it is necessary to use air or rail travel, the contractor agrees to use coach, tourist class, or similar accommodations to the extent consistent with the successful and economical accomplishment of the mission for which the travel is being performed.

(4) The contractor’s invoices shall include receipts or other evidence substantiating actual costs incurred for authorized travel. In no event will such payments exceed the rates of common carriers.

Vehicle and/or Truck Rentals. The contractor shall be reimbursed for actual rental/lease of special vehicles and/or trucks (i.e., of a type not normally used by the contractor in the conduct of its business) only if authorized in the basic contract or upon approval by the COR. Reimbursement of such rental shall be made based on actual amounts paid by the contractor. Use of rental/lease costs of vehicles and/or trucks that are of a type normally used by the contractor in the conduct of its business are not subject to reimbursement.

Car Rental. The contractor shall be reimbursed for car rental, exclusive of mileage charges, as authorized in the basic contract or upon approval by the COR, when the services are required to be performed beyond the normal commuting distance from the contractor’s facilities. Car rental for a team on temporary duty (TDY) at one site will be allowed for a minimum of four (4) persons per car, provided that such number or greater comprise the TDY team.

Per Diem. The contractor shall not be paid for per diem for contractor personnel who reside in the metropolitan areas in which the tasks are being performed. Per diem shall not be paid on services performed within a 50-mile radius of the contractor’s home office or the contractor’s local office. Per diem is authorized for contractor personnel beyond a 50-mile radius of the contractor’s home or local offices whenever a task assigned requires work to be done at a temporary alternate worksite. Per diem shall be paid to the contractor only to the extent that overnight stay is necessary and authorized under this contract. The authorized per diem rate shall be the same as the prevailing per diem in the worksite locality. These rates will be based on rates contained in the JTR or SR. The applicable rate is authorized at a flat seventy-five (75%) percent on the day of departure from contractor’s home or local office, and on the day of return. Reimbursement to the contractor for per diem shall be limited to actual payments to per diem defined herein. The contractor shall provide actual payments of per diem defined herein. The contractor shall provide supporting documentation for per diem expenses as evidence of actual payment.

Shipboard Stays. Whenever work assignments require temporary duty aboard a Government ship, the contractor will be reimbursed in accordance with the Joint Travel Regulations, Paragraph C4558, Per Diem for Travel by Ship.

Special Material. “Special material” includes only the costs of material, supplies, or services which is peculiar to the ordered data, and which is not suitable for use in the course of the contractor’s normal business. It shall be furnished pursuant to specific authorization approved by the COR. The contractor will be required to support all material costs claimed by its costs less any applicable discounts. “Special materials” include, but are not limited to, graphic reproduction expenses, or technical illustrative or design requirements needing special processing.

PROJECT SECURITY AND ANTITERRORISM

1. Project Security. The contractor shall comply with FAR 52.204-2, Security Requirements. This clause involves access to information classified “Confidential,” “Secret,” or “Top Secret” and requires contractors to comply with— (1) The Security Agreement (DD Form 441), including the National Industrial Security Program Operating Manual (DoD 5220.22-M); any revisions to DOD 5220.22-M, notice of which has been furnished to the contractor.

The contractor shall ensure that project security requirements are integrated into all task areas as required by Department of Defense (DOD) Directive 5200.39. The contractor shall establish, implement, and maintain these requirements in accordance with (IAW) the provisions of 32 CFR, part 117 NISPOM. The contractor shall have a (INSERT CLEARANCE LEVEL) Facility (Security) Clearance (FCL) with (indicate “a storage” or “no storage”) requirement. The contractor shall ensure that all classified and sensitive unclassified program information, data, materials, and end items are properly marked and controlled as required in accordance with the DD Form 254, Contract Security Classification Specification, and any subsequent revisions. Contractor visits to other DOD or DOD contractor facilities in the performance of this task shall be coordinated through the COR or Procurement Contracting Officer (PCO).

Antiterrorism (AT) and Operations Security (OPSEC). Contractor employees and associated subcontractor employees shall comply with Antiterrorism (AT) and Operations Security (OPSEC) while maintaining access to CONUS/OCONUS military installations. As directed by AR 525-13 and AR 530-1, the contractor shall complete the AT Level I Awareness Training and shall submit certificates of completion to the COR, Contract Specialist (CS), or Contracting Officer (KO) within 10 calendar days after completion.

Note: Antiterrorism Level Training - https://jko.jten.mil/courses/AT-level1/launch.html, (AT Level I is a yearly requirement).

[Clearance level-contingent training follows. If the contract requires clearance, utilize the TARP section and omit the iWATCH section. If it does not, utilize the iWATCH section and omit the TARP section.] iWATCH. The contractor shall require all employees to review the Army iWATCH information prior to reporting to or having access to military installations. The iWATCH program requires all personnel to report any suspicious activity to the emergency hotline number, Military Police number or local law enforcement number.

Threat Awareness Reporting Program. For all contractors with security clearances. Per AR 381-12 Threat Awareness and Reporting Program (TARP), contractor employees must receive annual TARP training by a counterintelligence (CI) agent or other trainer as specified in 2-4b of AR 381-12.

Common Access Card (CAC). For contractors requiring CAC. Before CAC issuance, the contractor employee requires, at a minimum, a favorably adjudicated National Agency Check with Inquiries (NACI) or an equivalent or higher investigation in accordance with Army Directive 2014-05. The contractor employee will be NACI or an equivalent or higher investigation in accordance with Army Directive 2014-05. The contractor employee will be issued a CAC only if duties involve one of the following: (1) Both physical access to a DoD facility and access, via logon, to DoD networks on-site or remotely; (2) Remote access, via logon, to a DoD network using DoD-approved remote access procedures; or (3) Physical access to multiple DoD facilities or multiple non-DoD federally controlled facilities on behalf of the DoD on a recurring basis for a period of 6 months or more. At the discretion of the sponsoring activity, an initial CAC may be issued based on a favorable review of the FBI fingerprint check and a successfully scheduled NACI at the Office of Personnel Management.

Access and General Protection/Security Policy Procedures. Contractor and all associated subcontractor employees shall comply with applicable installation, facility, and area commander installation/facility access and local security policies and procedures provided by the Government. The contractor shall also provide all information required for background checks to meet installation access requirements to be accomplished by installation Provost Marshal Office, Director of Emergency Services, or Security Office. Contractor workforce must comply with all personal identity verification requirements as directed by DOD, Headquarters Department of the Army (HQDA), and/or local policy. In addition to the changes otherwise authorized by the changes clause of this contract, should the Force Protection Condition (FPCON) at any individual facility or installation change, the Government may require changes in contractor security matters or processes.

DISCLOSURE, USE AND PROTECTION OF PROPRIETARY INFORMATION

1. During the performance of this contract, the Government may use an independent services contractor (ISC), who is neither an agent nor employee of the Government. The ISC may be used to conduct reviews, evaluations, or independent verification and validations of technical documents submitted to the Government during performance.

The use of an ISC is solely for the convenience of the Government. The ISC has no obligation to the prime contractor. The prime contractor is required to provide full cooperation, working facilities, and access to the ISC for the purposes stated in paragraph (a) above.

Since the ISC is neither an employee nor agent of the Government, any findings, recommendations, analyses, or conclusions of such a contractor are not those of the Government.

The prime contractor acknowledges that the Government has the right to use ISCs as stated in paragraph (a) above. It is possible that under such an arrangement the ISC may require access to or the use of information (other than restricted cost or pricing data), which is proprietary to the prime contractor.

To protect any such proprietary information from disclosure or use, and to establish the respective rights and duties of both the ISC and prime contractor, the prime contractor agrees to enter into a direct agreement with any ISC as the Government requires. A properly executed copy (per FAR 9.505-4) of the agreement will be provided to the Procuring Contracting Officer.

GOVERNMENT PROPERTY

(Government Furnished Property + Contractor Acquired Property) The term Government Property (GP) refers to any Government Furnished Property (GFP) or Contractor Acquired Property (CAP) that will pass to the Government at the conclusion of this effort.

*** NOTE: At the time of contract award the Government may determine there may be a process/processes that is not applicable to this contract. However, if it is later determined that they are applicable, the PCO will enact this/these requirement(s).

Property Management – The contractor shall have a system of internal controls to manage (control, use, preserve, protect, repair, and maintain) Government property in its possession. The contractor shall maintain a Property Management System (PMS) for Government Property in accordance with FAR 52.245-1. The system shall be adequate to satisfy the requirements of this clause. In doing so, the contractor shall initiate and maintain the processes, systems, procedures, records, and methodologies necessary for effective and efficient control of Government property in accordance with sound business practices and applicable provisions and other contractually imposed requirements. The contractor shall disclose any significant changes to its property management system to the Property Administrator prior to implementation of the changes. The contractor may employ customary commercial practices, voluntary consensus standards, or industry-leading practices and standards that provide effective and efficient Government property management that are necessary and appropriate for the performance of this contract (except where inconsistent with law or regulation). The contractor may employ customary commercial practices, Voluntary Consensus Standards, or Industry-Leading Practices and standards that provide effective and efficient Government property management that are necessary and appropriate for the performance of this contract.

The contractor shall establish and maintain procedures necessary to assess its Property Management System effectiveness and shall perform periodic internal reviews, surveillances, self-assessments, or audits. Significant findings or results of such reviews and audits pertaining to Government property shall be made available to the KO/Property administrator.

The contractor shall keep a database or electronic spreadsheet of all requisitioned GFP and CAP during the life of the contract.

Property Management Systems Analysis Evaluation (PMSA) – The Property Management Systems Analysis (PMSA) will be used to evaluate the contractor’s Property Management System (PMS). The contractor’s PMS shall provide all property records and related correspondence to the appropriate COR/KO/Government Property Administrator (GPA) for audit. The contractor shall be prepared to present any GFP and GFP records for inspection upon request.

Item Unique Identification – IAW DoDI 8320.04 Enclosure 3 Figure 1, the contractor will collaboratively assess with the KO and COR during contract execution if any deliverables are subject to Item Unique Identification (IUID) assignment. If IUID assignment is required, the contractor shall follow AR 700-145 and ensure all equipment that meet the criteria of serialized, $5,000 dollars or more items have a valid Unique Item Identification (UII) marking. If IUID assignment is applicable, the contractor shall also register for a IUID account in order to enter, view, and edit all records within the IUID database that are associated with in accordance with https://dodprocurementtoolbox.com.

Records of Government Property – Accountability records of Government property shall be maintained using the FAR, part 52.245-1(f) (1) (iii). The contractor shall create and maintain records of all Government property accountable to the contract, including Government-furnished and contractor-acquired property. Property records shall enable a complete, current, auditable record of all transactions and shall contain the following: The name, part number, description, National Stock Number, quantity received, fabricated, issued, balance-on-hand, unit acquisition cost, unique-item identifier, unit of measure, accountable contract number, location, posting reference, date of transaction, and date placed in service unless otherwise approved by the KO/GPA.

Utilization of Government Property – The contractor shall utilize, consume, move, and store Government Property only as authorized under this contract. The contractor shall promptly disclose and report Government property in its possession that is excess to contract performance. The contractor shall use Government property only for its authorized purposes and will have a system to determine usage. Usage data will be recorded and provided to the appropriate COR as requested. Usage data will be used to determine if property is excess to contract and/or to justify replacement or additional GFP. (Reference FAR 52-245-1).

Storage of Government Property – The contractor shall provide proper protection of Government property. This includes but is not limited to security from pilferage and protection from the elements: i.e., adequate prevention of handling damage; protection against water flow, insects, and rodents; or deterioration by dust, temperature, and humidity. Unless otherwise authorized by the appropriate COR, the contractor shall not commingle Government property (GFP and CAP) with property not owned by the Government IAW FAR 52.245-1(f) (1)(viii)(b). Storage of Government Property requires establishing controls that permit ready location and identification. Special controls shall be provided for shelf life items.

Reports – The contractor shall have a process to create and provide reports of discrepancies, loss of Government property, physical inventory results, consumption reports, audits self-assessments, corrective actions, and other property related reports as directed by the Contracting Officer. This report shall be drafted in accordance with the Data Item Description (DI-MGMT 81947B).

Subcontractor Control – The contractor shall award subcontracts that clearly identify items to be provided and the extent of any restrictions or limitations on their use. The contractor shall ensure appropriate flow down of contract terms and conditions (e.g., extent of liability for loss of Government property). The contractor shall assure its subcontracts are properly administered and reviews are periodically performed to determine the adequacy of the subcontractor's Property Management System.

Relief of Stewardship Responsibility and Liability (Loss) – The contractor shall have a process to enable the prompt recognition, investigation, disclosure, and reporting of loss of Government property, including losses that occur at subcontractor or alternate site locations. The contractor shall investigate and provide initial report of loss, theft, damage, or destruction of Government Property to the appropriate COR/KO/PA within 24 hours. This includes reporting all incidents or accidents involving government property. IAW Class Deviation 2020-O0004 - Reporting Loss of Government Property, the contractor shall use the Procurement Integrated Enterprise Environment (PIEE) Property Loss Application in the GFP to report any property loss. Reporting value shall be at unit acquisition cost.

Disposition of Government Property – The contractor shall report all Government Property that is determined to be in excess of contract requirements or may require disposal instructions from the appropriate COR/KO/GPA. The contractor shall dispose of excess Government property IAW DFARS. Condition codes shall be annotated as appropriate. All disposition actions and disposal records will be maintained as required by the FAR52.245-1(j). The contractor may use local Defense Logistics Agency (DLA) Disposition Services.

Scrap procedures – The contractor shall ensure their scrap disposal processes, methods, and practices allow for effective, efficient, and proper disposition and are properly documented in the contractor’s Property Management System.

The contractor shall have a process for disposal of Government-owned scrap on Government contracts if any of the following items are produced:

· Sensitive items

· Hazardous materials or wastes

· Classified or otherwise controlled items

· Precious or strategic metals

· Characteristics or components dangerous to public health or safety The contractor shall physically segregate unique disposal processing or separate plant clearance reporting. The contractor procedures shall address the following if applicable:

· Unserviceable end-items beyond economical repair (meeting the DFARS 252.245- 7004(a) (2) definition of scrap) or scrap parts removed from end-items as a result of the repair, maintenance, overhaul, or modification process.

· Scrap remaining from production operations, i.e., production (shavings and trimmings), engineering, research, and development.

· Production scrap does not warrant physical segregation and may be commingled and disposed of with contractor owned scrap.

· Other types of scrap: e.g., serviceable property downgraded to scrap, may be disposed of for its basic material content by direction of the PLCO.

Property Closeout – The contractor shall promptly perform and report to the COR/KO/Property Administrator, contract property closeout, to include reporting, investigating, and securing closure of all loss of Government property cases; physically inventorying all property upon termination or completion of this contract; and disposing of items at the time they are determined to be excess to contractual needs.

Contractor Acquired Property (CAP) The contractor shall maintain a list of all CAP. All CAP and associated records will remain the property of the Government and shall be returned to the Government upon request or at the end of the contract/task order/delivery order period of performance or as directed by the Contracting Officer. All CAP shall be used in support of the contracted function and operated in the prescribed manner intended. CAP must be cataloged, and the contractor shall use an automated property system for the purpose of tracking and accounting for CAP. The contractor shall keep a database or electronic spreadsheet of all requisitioned CAP during the life of the contract. The contractor shall request access to the respective Service’s automated system(s) for cataloging CAP prior to delivery to the Government.

Government Furnished Property (GFP) The contractor shall maintain a list of all GFP issued for use. GFP materials and records will remain the property of the Government and shall be returned to the Government upon request or at the end of the period of performance or as directed by the Contracting Officer. All GFP shall be used in support of the contracted function and operated in the prescribed manner intended.

The contractor’s PMS will be provided by contractor’s management, reviewed by the Property Administrator, and approved by the Contracting Officer (in writing) prior to and during the life of this contract. The contractor shall disclose any significant changes to its Property Management System to the COR/KO/Property Administrator prior to implementation of the changes. All changes to the PMS must be approved by the Contracting Officer in writing, prior to implementation.

Acquisition – The contractor shall furnish a written statement to the COR/KO/Property Administrator containing all relevant facts, such as cause or condition and a recommended course(s) of action, if overages, shortages, or damages and/or other discrepancies are discovered upon receipt of Government-Furnished Property.

Receiving – The contractor shall receive, document the receipt, and record the necessary record requirements of paragraph (f)(1)(iii)(A)(1), (2), (3), (4), (5), (6), (7), (8), (9) & (10) as specified in FAR 52.245-1. The contractor shall take all actions necessary to adjust for overages, shortages, damage, and/or other discrepancies discovered upon receipt, in shipment of Contractor-Acquired Property from a vendor or supplier, so as to ensure the proper items are reasonable, allowable, and allocable, with associated costs.

The contractor shall use an automated property system for the purpose of tracking and accounting for GFP.

The contractor shall only acquire initial and additional GFP for use on this contract when given prior written approval. Requests for additional GFP shall include justification and will be routed through the appropriate COR for review and endorsement prior to sending the Contracting Officer for approval and contract modification.

Identification of Government Property – Government-owned property shall be identified, marked, and recorded during the contractor’s receiving process.