Attach-8_Draft.SOW.Template _ FINAL.docx

DOCX document 134 KB Posted

Attached to
Broad Agency Announcement _ TRMC _ TE-ST _ W900KK-22-R-0012
Solicitation number
W900KK-22-R-0012
Issued by

About this file

This Broad Agency Announcement solicits proposals for research and technology development projects related to test and evaluation of future warfighting capabilities. The Test & Evaluation/Science & Technology Program seeks to advance test technologies from Technology Readiness Levels 3 to 6 to produce higher quality, more cost-effective, and timelier test and evaluation for the Department of Defense acquisition lifecycle. Prospective offerors should review the individual Opportunity Notices described in the BAA for specific areas of interest, which include developmental test and evaluation, operational test and evaluation, and live-fire test and evaluation. The BAA encourages novel, higher-risk solutions and will accept a degree of technical risk commensurate with potential high payoffs.

View the file

Other files

File Type Posted
ATTACHMENT-8_SOW.Template_REV_5.18.2026_clean.docx DOCX document
Attach-9_CHESS_Letter_Signed.pdf PDF
Attach-8_SOW.Template_REV_5.18.2026_clean.docx DOCX document
ATTACHMENT-8_SOW.Template_REV_5.07.2026.docx DOCX document
Encl-1.4 _ In-Cycle _ Opportunity Notice 1.4 _ Rev 1 _ 4.15.2026.docx DOCX document
Encl-1.4 _ In-Cycle _ Opportunity Notice 1.4 _ 2.11.2026.docx DOCX document
TE-ST.BAA_W900KK-22-R-0012_Revised 2.4.2026.docx DOCX document
Encl-1.2_+In-Cycle.Opportunities_REV_26 Nov 2024.pdf PDF
Attach-8_SOW.Template_REV_07.25.2023.docx DOCX document
Attach-13_Abstract.Template_REV_02.08.2023.docx DOCX document
Encl-4_Proposal.Submission.Instr_REV_02.08.2023.docx DOCX document
Attach-8_Draft.SOW.Template_REV_02.06.2023.docx DOCX document
Encl-1.3_Out-of-Cycle Opportunity_3 Nov 2022.pdf PDF
Encl-1.2., Rev 1_Out-of-Cycle_Other.Test.Technologies_3 Nov 2022.pdf PDF
Encl-1.2_Out-of-Cycle_Other Test Technologies_DET-EWT_FINAL.pdf PDF
Attach-1_White.Paper.Data.Sheet.v1.1p_25 APR 2022.xlsx XLSX spreadsheet
ON 1.1 _ Industry Day Qestions and Response_25 APR 2022.xlsx XLSX spreadsheet
Encl-3_White.Paper.Submission.Instr.REV_4.19.2022.docx DOCX document
Encl-1.1_ In-Cycle.Opportunities_REV_4.19.2022.docx DOCX document
NOTICE OF INDUSTRY-ACADEMIA DAYS_FINAL with Link.docx DOCX document
NOTICE OF INDUSTRY-ACADEMIA DAYS_FINAL.docx DOCX document
0.NOTICE OF INDUSTRY-ACADEMIA FORUM_23MAR2022_Final.docx DOCX document
0.TE-ST_BAA_Industry_One-on-One_Registration.xlsx XLSX spreadsheet
Attach-1_White.Paper.Data.Sheet.v1.0p_FINAL.xlsx XLSX spreadsheet
Attach-9_CHESS_Letter_ Signed.pdf PDF
Encl-2_Project.Structure.Guidelines_ FINAL.docx DOCX document
Encl-3_White.Paper.Submission.Instr_ FINAL.docx DOCX document
Attach-2_Related.Work.History-Experience.v1.0p_FINAL.xlsx XLSX spreadsheet
Attach-3_Govt.Data.Rights.Acknowledgement_ FINAL.docx DOCX document
Attach-6_Proposal.Data.Sheet.v1.0p _ FINAL.xlsx XLSX spreadsheet
Attach-10_Cost.Volume.Template_FINAL.docx DOCX document
Attach-13_Abstract.Template_v1.0_FINAL.docx DOCX document
Encl-1.1_ In-Cycle.Opportunities_final.draft-11MAR.docx DOCX document
Encl-5_Admin and Natl.Policy.Reqts_ FINAL.docx DOCX document
Attach-7_Project_Quad_Chart_Template.v1.0_FINAL.pptx PPTX presentation
Attach-11_Cost.Prop.Workbook_v1.0p_FINAL.xlsx XLSX spreadsheet
Attach-12_Basis.of.Estimate.Desk.Guide_FINAL.docx DOCX document
Encl-1_Research.Opportunity.Guidance_ FINAL.docx DOCX document
Encl-4_Proposal.Submission.Instr_ FINAL.docx DOCX document
TE-ST.BAA_W900KK-22-R-0012_ FINAL.docx DOCX document
Annex_TTA.Descriptions.v1_FINAL.docx DOCX document
Attach-4_IP and Data.Rights.Assertions_ FINAL.docx DOCX document
Attach-5_Admin and Natl.Policy.Reqts._ FINAL.docx DOCX document
Show all 43

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

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 .pdf, .odx, .doc, or .docx formats. Submissions must be written in English. No page limit has been specified for the Draft Statement of Work document.

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 offeror shall define all tasks in the SOW, 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. 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. If the offeror is a Government entity, 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:

The offeror shall describe the tasks that represent the work to be performed. After negotiation these tasks will become binding upon project award. Therefore, the offeror should organize the task progression and provide enough detail to establish the feasibility of accomplishing the overall project goals.

Task/sub-task descriptions should include a detailed description of the approach to be taken to accomplish for each defined task/subtask and should 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).

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

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

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.

The Administrative Elements section is required content, which is the currently used language for the component administrative SOW sections at BAA release. The offeror makes NO changes to these sections. This is provided for the Offeror’s understanding of these administrative SOW requirements for contract award, if pursued.

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.

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)]

STATEMENT OF WORK

[dd MONTH yyyy]

Revision History

REV
DATE
BY
CHANGE
0.1
[dd MMM yyyy]

Proposal Volume 2 Initial Draft

W900KK-19-C-0033

Statement of Work 22 February 2019 i

TABLE OF CONTENTS

A.TECHNICAL ELEMENTS1
1.0OVERVIEW1
1.1Objective1
1.2Scope1
1.3Background1
2.0TECHNICAL PERFORMANCE TARGETS/GOALS1
2.1Tabular Summary1
3.0TASKS/EXIT CRITERIA BY PHASE1
3.1Phase 11
3.2Phase 22
3.3Phase 32
4.0DELIVERABLES3
4.1Hardware/Software/Data3
4.2Documentation Markings and Transmittals4
4.3Reporting Requirements and Related Deliverables4
B.ADMINISTRATIVE ELEMENTS7
1.0REIMBURSEMENT OF TRAVEL, PER DIEM, AND SPECIAL MATERIAL COSTS7
2.0PROGRAM SECURITY AND ANTI-TERRORISM9
3.0DISCLOSURE, USE AND PROTECTION OF PROPRIETARY INFORMATION10
4.0GOVERNMENT FURNISHED PROPERTY10
APPENDIX A: SOW ADDENDUM FOR GOVERNMENT FURNISHED PROPERTY12

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

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

TECHNICAL PERFORMANCE TARGETS/GOALS

Tabular Summary [Provide either statements or a tabular summary that represents all the intended technology advancement areas or elements addressed to meet the topic objective. Indicate the planned priority for each when addressing any trade-space considerations across all areas/elements for each advancement area (or parameter), the primary goal for performance, and the desired ultimate goal if unconstrained from trade-space requirements or funding availability.] [Provide any amplification commentary to advancement areas/elements, if needed.]

TASKS/EXIT CRITERIA BY PHASE

Phase 1 Phase 1 Tasks [Identify/describe task 1] [Identify/describe subtask 1] [Identify/describe subtask 2] [Identify/describe task 2] [Identify/describe subtask 1] [Identify/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 [Identify/describe task 1] [Identify/describe subtask 1] [Identify/describe subtask 2] [Identify/describe task 2] [Identify/describe subtask 1] [Identify/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 [Identify/describe task 1] [Identify/describe subtask 1] [Identify/describe subtask 2] [Identify/describe task 2] [Identify/describe subtask 1] [Identify/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 Phase 1

· [List the deliverables that result from each phase, ensuring 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 deliverables that result from each phase, ensuring 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 deliverables that result from each phase, ensuring 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 deliverables that result from each phase, ensuring 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 deliverables that result from each phase, ensuring 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 deliverables that result from each phase, ensuring 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 distribution statement by marking in accordance with Department of Defense Directive 5230.24, Distribution Statements on Technical Documents (as revised). Note, distribution statements may be altered by the COR.

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

Reporting Requirements and Related Deliverables [Below items are the minimal reporting requirements; others may apply, which may include but not be limited to TRMC presentations, in-progress status reports, and test event performance data/reporting.] 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 and issues on the project in accordance with the Data Item Description (DI-MGMT-80227) and Government format template provided upon award.

Phase/Final Report 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).

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.

ADMINISTRATIVE ELEMENTS

REIMBURSEMENT OF TRAVEL, PER DIEM, AND SPECIAL MATERIAL COSTS

(a) 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.

(b) 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 (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.

(c) 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.

(d) 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.

(e) 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 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.

(f) 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 fifty-mile radius of the Contractor’s home office or the Contractor’s local office. Per Diem is authorized for Contractor personnel beyond a fifty-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.

(g) 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.

(h) 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.

PROGRAM SECURITY AND ANTI-TERRORISM

(a) Program Security. 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 program 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 IAW the provisions of DOD Manual 5200.1. 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 PCO.

(b) Antiterrorism (AT) and Operations Security (OPSEC), and iWATCH. Contractor employees and associated sub-contractor 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 Contracting Officer Representative (COR), Contract Specialist (CS) or Contracting Officer (CO) within 10 calendar days after completion. Additionally, 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.

Note: Anti-Terrorism Level Training - https://atlevell.dtic.mil/at/, (AT Level I is a yearly requirement).

(c) Access and General Protection/ Security Policy Procedures. Contractor and all associated sub-contractor 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, 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

(a) 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.

(b) 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.

(c) 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.

(d) 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.

(e) 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 FURNISHED 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. 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 shall maintain a Property Management System (PMS) for GFP in accordance with FAR 52.245-1. The Contractor shall develop the PMS that will address all aspects of this document in detail. The approved PMS shall contain procedures for acquisition, receiving, identification, records, reports, storage, movement, audits, physical inventories, consumption, utilization, maintenance, subcontractor control, disposition, and contract closeout of GFP in accordance with sound business practices and applicable provisions and other contractually imposed requirements. This PMS will be provided by Contractor’s management and reviewed by the Property Administrator and approved by the Contracting Officer (in writing) prior to and during the life of this contract. Any and all changes to the PMS must be approved by the Contracting Officer in writing, prior to implementation.

The Contractor shall only acquire 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.

APPENDIX A: SOW ADDENDUM FOR GOVERNMENT FURNISHED 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. The Contractor shall maintain a list of all GFP issued for use.

Government Furnished Property, 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 task order 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 shall not acquire additional GFP/CAP for use on this contract without 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 to the Contracting Officer for approval and contract modification.

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 initiate and maintain the processes, systems, procedures, records, and methodologies necessary for effective and efficient control of Government property. The Contractor shall disclose any significant changes to its Property Management System to the COR/KO/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.

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.

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 request access to Automated Enterprise System Integration Program (AESIP) to catalog CAP prior to delivery to Government. The Contractor shall use an automated property system for the purpose of tracking and accounting for GFP. The Contractor shall keep a database or electronic spreadsheet of all requisitioned GFP and CAP during the life of the contract.

Identification of Government Property - Government-owned property shall be identified, marked, and recorded during the Contractor’s receiving process. All GFP shall be stamped, tagged, marked and recorded using automated procedures IAW FAR 52.245-1(f) (1) (ii).

Item Unique Identification -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. The Contractor shall 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 http://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/Property Administrator.

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

Consumption – The Contractor shall consume Government Material only as authorized under this contract. The Contractor shall analyze and track the consumption of material and have processes for monitoring of this action. The Contractor shall issue materials in reasonable and proper quantities for work being performed. The Contractor shall return unused portions of materials to stock and annotate reestablishment to records. It may include the attachment or incorporation of material into a Government Property item.

Movement of Government Property - The Contractor shall control Government Furnished Property through documentation, tracking, and location systems that facilitate changes in quantities and location. Examples of proper documentation are receiving reports, issue documents, turn-in documents, and shipping documents. The PMS shall address all movement and transfer of Government property.

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

Physical Inventories of Government Property - The Contractor shall perform physical inventories of GFP within 30 days of contract award. An initial inventory of GFP shall be performed jointly between the COR/USG Representative and the incoming Contractor at the beginning of the contract period. This inspection will verify the quantities, condition and availability of the equipment offered to the Contractor by the Government. Inspection results will be recorded and signed by the Contractor and the appropriate USG representative. This inventory should be completed prior to the end of the Phase In period. The process to complete this inventory should be addressed in the Transition Agreement between the incumbent and new Contractor. The Contractor shall periodically perform, record, and disclose physical inventory results. A final physical inventory shall be performed upon contract completion or termination.

The Contractor will schedule additional inventories as needed and submit this schedule to the appropriate COR for review. The Contractor shall use a 10% monthly cyclic method of inventory for this contract. The Contractor shall designate by memorandum what line items are to be inventoried during this cycle and how the inventory will be conducted. These monthly inventory records, results of the inventory and a written report of all discrepancies and corrective actions noted during cyclic inventories shall be provided to the COR NLT 25th of each month.

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

Maintenance - The Contractor's Maintenance Program shall enable the identification, disclosure, and performance of normal and routine preventative maintenance and repair. The Contractor shall disclose and report to the COR/KO the need for replacement and/or capital rehabilitation. The Contractor’s maintenance program shall be structured to efficiently initiate, control, perform and document required maintenance for GFP provided under the terms of the contract. This maintenance plan will include a preventive and general maintenance plan and provide for scheduled and unscheduled services. All GFP requiring maintenance services shall be included in the GFP Maintenance Plan. New equipment shall be inducted into the plan upon receipt. The Government may require a particular maintenance procedure or system be used for the maintenance of GFP. The Contractor shall not modify, alter or cannibalize any GFP without USG permission.

Sub-Contractor 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 GFP to the appropriate COR /KO/PA within 24 hours. This includes reporting all incidents or accidents involving government property. IAW DFR 252.245-7002 the Contractor shall use the Defense Contract Management Agency (DCMA) eTools software application for reporting loss of Government property. Reporting value shall be at unit acquisition cost. The eTools “LTDD of Government Property” toolset can be accessed from the DCMA home page External Web Access Management (EWAM) application at http://www.dcma.mil/WBT/propertyloss.

Disposition of Government Property - The Contractor shall report any and all GFP that is determined to be in excess of contract requirements or may require disposal instructions from the appropriate COR/KO/PA. The Contractor shall dispose of excess GFP IAW FAR 45.6 02-1 and DFARS 245.6 as may be appropriate. 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 DRMS as long as it is stated in the PWS/SOW. The Contractor shall use the Defense Contract Management Agency (DCMA) eTools software application Plant Clearance Automated Reutilization Screening System (PCARSS) for disposition of GFP. The eTools “PCARSS toolset can be accessed from the DCMA home page External Web Access Management (EWAM) application at http://www.dcma.mil/WBT/pcarss.

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 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/GPA/ for audit. The Contractor shall be prepared to present any GFP and GFP records for inspection upon request.

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.

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

image1.png

File details come from the government source that posted it. Updated .