Attachment 0002 - Performance Work Statement 4.16.2026.pdf
PDF 745 KB Posted
- Attached to
- Intelligence and Automation Operations Federal contract opportunity
- Solicitation number
- W50NH9-26-R-A002
About this file
This is a Performance Work Statement (PWS) for the Data Capabilities Division (DCD) - Intelligence and Automation Operations (IAO) contract supporting the Army Intelligence Security Enterprise (AISE).
The contract requires comprehensive operational intelligence integration and data-centric support across five task areas: Cross Domain Solutions and Digital Content Management, Data/Messaging/Systems Integration and TREX Support, Operations Support, Access Management, and Information Technology Support. Core services include cross-domain intelligence dissemination across multiple classified networks (JWICS, SIPRNET, CENTRIXS-KOREA, USBICES, and others), metadata tagging and content management via SharePoint platforms, data governance and architecture support, training delivery via the GEN 302 Foundry course, bilateral/multilateral intelligence sharing coordination, and IT infrastructure management supporting approximately 20 databases and IIS websites across five networks. The contract period is 12 months with four 12-month option periods. Primary places of performance include INSCOM Nolan Building Fort Belvoir, VA; Ft. Liberty, NC; Joint Base Lewis-McChord, WA; and Ft. Huachuca, AZ. Personnel must maintain Top Secret/SCI clearance with ability to obtain SI-G, TK, KLM-R, HCS, and NATO SECRET access. Contractor personnel must achieve Data Transfer Agent certification within 30 days and comply with DoD 8140.01 Information Assurance Technical (IAT) Level II certification requirements for applicable roles. Work hours are 8-hour days Monday-Friday with core hours 0900-1500; Task Area 1 requires minimum 2-person manning shifts with DTA training. The Performance Requirements Summary specifies 90% quality levels for dissemination tasks (6-hour turnaround for intelligence products, 30-minute turnaround for high-priority cross-domain transfers), tearline processing (2 hours), system availability (99%), and database daily checks (100% critical checks by 0700 hours daily). Contract deliverables include monthly financial status reports, quality control plans, SOPs, training curricula, trip reports, and IT systems matrices. Government furnishes workspace, utilities, computers, and standard operating procedures; contractor provides program management, personnel, and telework equipment when authorized.
View the file
Other files for this federal contract opportunity
Show all 14
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Data Capabilities Division (DCD) - Intelligence and Automation Operations (IAO)
1 | P a g e
PERFORMANCE WORK STATEMENT (PWS)
Data Capabilities Division (DCD) - Intelligence and Automation Operations (IAO) https://armyeitaas.sharepoint-mil.us/sites/INSCOM-DAIIS
2 | P a g e
1 PART 1. GENERAL.
1.1 ADMINISTRATIVE OVERVIEW.
1.1.1 Background: The Data Capabilities Division (DCD), under the Army G-2, DAMI-IT located within INSCOM Headquarters, leads the development and management of software solutions that strengthen all-source intelligence analysis and production across the Army Intelligence Security Enterprise (AISE). DCD collaborates closely with operational stakeholders and the acquisition community, including PEO IEW&S, to incorporate feedback and deliver agile updates to platforms, software, data, and analytics. The division supports mission requirements across multiple theaters of operation, enabling commanders to establish and sustain a Common Intelligence Picture (CIP). As the Information System Owner of the Army Intelligence Data Platform (AIDP), INSCOM provides governance to prioritize system changes in alignment with the Army Intelligence Modernization Strategy. DCD ensures systems are enriched with authoritative data sources and protected through rigorous cybersecurity and risk management practices.
1.1.2 Objective: To provide comprehensive operational intelligence integration and data-centric support to the DCD and its diverse customer base. Beneficiaries include tactical units, joint forces, interagency partners, allied and coalition entities, Army Service Component Commands (ASCCs), Joint Task Force J-2s, and Combatant Commands. This effort enables intelligence consumers to discover, access, and share relevant Intelligence Community (IC) reporting—both all-source and single-source—across the networks they operate. Core services include cross-domain solutions, secure network access, data management, systems integration, and access to intelligence reporting across U.S. and multinational platforms. Support extends to the Army’s intelligence program of record and the designated intelligence application within the Next Generation Command and Control (NGC2) framework. The Army Intelligence Data Platform (AIDP) supports all echelons—battalion, brigade, division, corps, and ASCC—and directly contributes to the tactical-to-operational targeting process. Additionally, the contract establishes data protocols for NGC2 through a range of services, including artificial intelligence integration, Mobile Training Teams (MTTs), data governance, exercise systems integration, cybersecurity, cloud engineering, help desk operations, and overall mission support.
1.1.3 SCOPE: Outlined within five (5) specific task areas identified below, as outlined in Part four (4) of the PWS:
• Task Area 1: DCD Cross Domain Solutions and Digital Content Management
• Task Area 2: DCD Data, Messaging, Systems Integration and Trex Support
• Task Area 3: DCD Operations Support
• Task Area 4: DCD Access Management
3 | P a g e
• Task Area 5: Information Technology Support
1.1.4 Reference Materials:
• Part 5: Regulations and Policies
• Part 6: Technical Exhibit Listings
• Attachment 0003 - List of CDRLs
1.1.5 Period and Place of Performance.
1.1.5.1 Period of Performance. The Contract period of performance is for a 12-month based period from the time of award with four 12-month option periods.
1.1.5.2 Places of Performance. Unless otherwise stated, the primary places of performance for all Task Areas are INSCOM Nolan Building, Fort Belvoir, VA, Ft. Liberty, NC, Joint Base Lewis-McChord, WA, and Ft. Huachuca, AZ.
1.1.5.3 Continuity of Operations (COOP): In response to catastrophic events, DCD will execute a COOP plan; some contractor personnel shall be required to relocate to an approved COOP location. COOP operational hours are likely 24 X 7/365. DCD government personnel will provide additional guidance for COOP planning. In the event of an emergency or unanticipated impact to operations (such as a pandemic, natural disaster, etc.), telework or alternate worksites may be authorized for up to 90 days. After 90 days, the government will be required to reauthorize after a revaluation by the operations director. Costs of relocating employees, purchasing hardware, sustaining operations, or establishing new workstations at the cost of the government is authorized when approved by the government.
1.1.6 Hours of Operations and Personnel Manning.
1.1.6.1 Task Area 1. Contractors should provide services during core hours. The contractor shall ensure the following:
1.1.6.1.1 Minimum manning of 2 contractor personnel on shift at all times, two (2) of whom are trained and available to perform Data Transfer Agent (DTA) operations. The two-person minimum DTA manning requirement is mandated by Army and DoD policies for Two Person Reliable Human Review of all files prior to conducting a cross-domain data transfer. In the event the DCD-designated automated screening toolset is degraded, 3-person manual review is mandatory to ensure Unauthorized Disclosure of Classification Information (UDCI) risks are mitigated.
4 | P a g e
1.1.6.2 All Task Areas. Contractors provide services covering an 8-hour workday, Monday through Friday, and must incorporate the established organizational core hours of 0900 through 1500 unless otherwise directed. Contractor personnel must be available to the Government for the conduct of their contracted efforts during core hours unless coordinated and approved (in advance and in writing) by the Contracting Officer Representative (COR) except during Recognized Federal holidays or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings. The Contractor will not be reimbursed when the government facility is closed for the above reasons.
The Contractor must at all times maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS when the Government facility is not closed for the above reasons. When hiring personnel, the Contractor should keep in mind that the stability and continuity of the workforce are essential.
1.1.7 Administrative and Management of Personnel Requirements.
1.1.7.1 Tactical Timeliness. Due to the highly adaptable nature of the enemy and the need to take advantage of short windows of opportunity, equipment and services are frequently required on short notice. The Contractor’s ability to provide services, and support within short time constraints 24 to 48 hours is critical.
1.1.7.2 The contractor shall provide a contract manager and alternate at no direct labor cost to the Government. The name of this person and an alternate who shall act for the contractor when the manager is absent shall be designated in writing to the contracting officer.
The contract manager or alternate shall have full authority to act for the contractor on all contract matters relating to the daily operation of this contract. All contractor personnel shall be knowledgeable in the conduct of intelligence operations and must demonstrate knowledge of battalion, brigade, and division level intelligence operations and production cycles.
1.1.7.3 Reserved
1.1.7.3.1 Reserved
1.1.8 Extended Work Week, Backfill, and Vacancies
1.1.8.1 Reserved
5 | P a g e
1.1.8.2 Extended Work Week: The contractor shall provide enough fully trained and qualified employees to meet all reporting requirements and deliverables. The contractor must maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS when the Government facility is not closed. When hiring personnel, the contractor should keep in mind that the stability and continuity of the workforce are essential. If an Extended Work Week (EWW) is required, all hours must be approved by the COR in advance. An EWW is defined as any hours worked in addition to a normal 40-hour work week. The projected EWW hours must be within budget and will not exceed the contract’s limitation of funds. Justification shall be provided for all EWW requested per labor category/contractor name as reflected in the contractor’s invoice backup detail. Approved EWW hours shall apply only to the contractor(s) named in the request and are not transferable to others. If request is approved, all EWW hours worked shall be billed at the normal labor category billing rate. Without approval, EWW hours shall not be included in the contractor's invoice.
1.1.8.3 Vacancies: When the Contractor becomes aware that an employee will be leaving the contract, the Contractor shall immediately notify the COR and backfill the position with personnel of equal or superior qualifications no later than the eleventh working day and permanently fill the position within 30 calendar days. The Contractor shall notify the COR of their plan to fill the position prior to employee assignment.
1.1.8.4 Identification and Conduct of Contractor Employees. All contract personnel attending meetings, answering Government telephones, and working in other situations where their contractor status is not obvious to third parties are required to identify themselves as such to avoid creating an impression in the minds of members of the public that they are Government officials. Contractor personnel should also ensure that all documents or reports they produce are suitably marked as contractor products or that contractor participation is appropriately disclosed.
Contractor personnel shall wear the appropriate security/identification badges when required.
The Contractor shall be responsible for ensuring that employees assigned to this contract comply with the applicable laws and regulations of the host country and any political subdivisions thereof. The Contractor shall be responsible for ensuring that such employees comply with military rules and regulations when employed in areas under the jurisdiction of the applicable U.S. Forces Commander.
6 | P a g e
1.1.8.5 The Contractor shall be responsible for ensuring that employees assigned to this contract comply with the applicable laws and regulations of the host country and any political subdivisions thereof. The Contractor is also responsible for ensuring that such employees comply with military rules and regulations when employed in areas under the jurisdiction of the applicable U.S. Army Commander. The Government reserves the right to direct any Contractor employee to be removed from performance, directly or indirectly, whenever there is probable cause to believe, based on all facts available, that such action is warranted in the interest of national security. This action shall be made whether the cause is deemed of sufficient severity to warrant action to terminate the Contractors or individuals Security clearance. The Government also reserves the right to remove any Contractor for the purpose of conducting any investigation of alleged misconduct that may, in the opinion of the Contracting Officer, jeopardize the security of the project. Loss or suspension of required facility security clearance as set forth on the DD Form 254, “Contract Security Classification Specifications,” would result in the Contractor’s inability to perform per the terms and conditions of this contract. As a direct result, the Contractor is subject to termination under the appropriate termination clause herein.
1.1.8.6 If a Contractor's employee is barred from continuing to perform under the contract for failure to comply with the laws, rules, and regulations, the costs incurred by the Contractor because of the removal of the employee, or the substitution of a replacement employee shall not be reimbursable under this contract. The disallowed costs would include relocation costs incurred by the Contractor to furnish a suitable substitute employee for the overseas assignment.
1.1.8.7 Contractor Travel. Travel to other Government facilities or other contractor facilities may be required. All travel requirements (including plans, agenda, itinerary, estimated reimbursable costs, or dates) will be pre-approved by the COR prior to travel by the contractor.
All contractor travel cost invoices will include backups (miscellaneous receipts, mileage, gas, lodging, flight, rental car, etc.) A valid U.S. unrestricted passport is required for personnel traveling for OCONUS site support. The cost of travel is provided for in the Other Direct Costs
(ODC).
1.1.8.8 Local travel is considered to travel within a 50-mile radius from the home station to perform official duties. Travel outside the 50-mile radius, as tasked by the Government, will be reimbursed at the applicable Joint Travel Regulations (JTR) rate.
7 | P a g e
1.1.8.9 Travel outside the 50-mile radius requires Government-issued Letters of Authorization (LOAs) for OCONUS travel and Letters of Instruction (LOI) for official travel and shall comply with the JTR. A trip report shall be submitted to the COR no later than 10 working days following completion of any Contractor travel. Air travel will be reimbursed IAW the Government JTR. All other travel costs will be reimbursed IAW the JTR.
1.1.8.10 The Contractor shall ensure their employees comply with National Industrial Security Program Operations Manual, DOD 5220.22-M requirements for notification and obtaining authorization prior to travel to areas listed by the State Department or other U.S. Government Agencies as “denied or restricted” travel areas. Intermittent travel to countries other than those listed in Table 1-2 may be required for short periods of time and other locations as directed by the COR. Travel to these locations may require country clearances prior to travel and shall comply with the JTR.
1.1.8.10.1 Deliverable: CDRL A001 - Travel Trip Report
1.1.8.11 Training. The Contractor is required to ensure that all employees comply with the HQ INSCOM mandatory training requirements for Contractor personnel in accordance with Army Regulation (AR) 381-10. The Contractor must provide documentation to the COR to confirm that training has been completed for each employee. Training will be completed during the transition period or as available via the Government. After the initial Transfer-In period, the Contractor must ensure that all CMEs comply with annual/periodic training requirements so that they are never in “overdue” status.
1.1.8.12 Online Training. The mandatory online training includes 1) DoD Cyber Awareness Challenge/Information Assurance, 2) Intelligence Oversight and Civil Liberties 3) Information Security Program, 4) DoD Controlled Unclassified Information Awareness, and 5) OPSEC Awareness. Additional training may be mandated by the government as necessary. Contractors shall complete all initial online training within 5 business days of indoctrination at HQ
INSCOM.
1.1.8.13 Classroom Training. Mandatory classroom training includes 1) Classification Marking and 2) Threat Awareness and Reporting Program (TARP). Additional training may be mandated by the government as necessary. Contractors shall attend the earliest available scheduled online training upon indoctrination at HQ INSCOM.
1.1.8.14 Data Transfer Agent Training. Personnel assigned to Task Area 1 require training and authorization as Data Transfer Agents (DTA). DTA training will be conducted at HQ INSCOM in coordination with the designated Government Lead, as required. Personnel must attend DTA training and pass DTA examination within 30 calendar days of indoctrination at HQ INSCOM.
1.1.9 Program Management Requirements:
1.1.9.1 Program Management. The contractor shall provide comprehensive program management across all subtask areas, including but not limited to:
8 | P a g e
• Program Oversight and Engagement
• Financial Reporting and Dashboard Delivery
• Administrative and Operational Support
• Production Metrics and CDRL Reporting and Compliance
• Other Direct Costs Tracking and Approvals
1.1.9.2 Program Oversight and Engagement: The contractor’s Program Manager shall actively participate in a range of professional engagements, including meetings, briefings, conferences, seminars, progress reviews, and other relevant events as directed by the Government. These activities may involve providing management oversight, offering technical expertise, and contributing to cost analysis discussions. The Program Manager shall also provide real-time contract and financial information to the KO and COR upon request or as needed to support program oversight. If assigned tasks or projects fall behind schedule, the Program Manager shall submit a report detailing the issue, identifying root causes, and outlining a mitigation plan with a timeline for resolution. Additionally, the contractor shall maintain a formal risk management and lessons learned program to support continuous process improvement, with results shared with the Government as changes occur and upon request by the COR.
1.1.9.3 Financial Reporting and Dashboard Delivery: The Program Manager is responsible for delivering an initial Monthly Financial Status Report (MFSR) to the designated COR and KO 30-days following the contract award date and by the 5th calendar day of each month thereafter, in accordance with CDRL 002. This report serves as a key financial and technical status tracking tool to ensure transparency and accountability throughout the performance period.
1.1.9.3.1 Within 30 days of contract award, the Program Manager shall also deliver a live, web-based Financial and Resource Management (FRM) - Dashboard to COR and KO, in accordance with CDRL A002 at no additional cost to the Government. . The FRM-D shall leverage a government-owned and controlled platform with an existing Authority to Operate (ATO) and provide secure, real-time access to integrated financial, personnel, and scheduling data relevant to contract execution, as approved by the Government. It shall feature interactive visualizations for Key Performance Indicators (KPIs), burn rate status (e.g., estimated funds remaining and estimated funds required, estimated funding run-out date, etc.), invoice status (e.g., costs invoices to date, outstanding invoices/lagging costs), expenditure trends, forecast modeling, CLIN/SLIN details, Estimate At Completion (EAC)/Estimate to Completion (ETC) metrics, contract modifications, task-level resource allocation, and personnel status including vacancies, paid time off, onboarding/offboarding, and TDY / Training schedules. The dashboard must support real-time data filtering without downtime, operate 24/7, and be accessible via standard web browsers without requiring additional software. Access shall be partitioned and secured exclusively for the Program Manager, COR, and KO. The FRM-D shall include export capabilities, automated report generation, and comprehensive audit logging to support compliance.
9 | P a g e
1.1.9.3.1.1 The contractor shall provide ongoing technical support, periodic enhancements, and training to designated Government personnel upon request to ensure effective use. The FRM-D complements the MFSR and serves as a centralized, dynamic tool for real-time program oversight and decision-making.
1.1.9.4 Administrative and Operational Support: The Program Manager shall perform all necessary administrative support functions to ensure effective contract execution. These responsibilities include contract financial management, accounting, reporting, precision scheduling, and oversight of mission support operations. The Program Manager shall also manage tasks, coordinate efficient logistics support, and maintain control mechanisms to ensure operational continuity. The contractor is responsible for ensuring timely updates and accuracy across all task activities, personnel travel and leave, facility readiness, financial reporting, contract modifications, and procurement actions.
1.1.9.5 Production Metrics and CDRL Reporting Compliance: The Program Manager shall maintain a live dashboard, integrated into the FRM-D, that is securely partitioned from financial data and accessible to all DCD Government personnel. This dashboard shall display daily production metrics, operational requirements, and CDRL reporting, enabling real-time review and verification that contract activities are executed in accordance with defined SOPs. All reports and data shall be submitted in alignment with applicable CDRLs. When formats are not specified, the contractor shall use standardized templates approved by the COR and apply them consistently throughout the performance period. Submissions must be posted in accordance with established CDRL protocols and reflected within the FRM-D interface. In support of the Quality Control Plan (QCP), the contractor shall implement a formal process for reviewing and submitting all contract deliverables. Draft submissions shall be provided by CDRL timelines, with corrections made as directed by the customer. If no comments or revisions are received within the specified timeframe, the submitted report shall be considered final. The FRMD shall serve as the central platform for tracking, exporting, and auditing these reports, ensuring transparency, compliance, and continuous process improvement.
1.1.9.6 Other Direct Costs Tracking and Approval: The Program Manager shall be responsible for tracking all Other Direct Costs (ODCs) incurred by contract personnel and ensuring they are displayed in real time on the FRM-D, along with associated documentation, in accordance with CDRL 002. ODCs will primarily include travel, training, materials, software licenses, and equipment necessary to support DCD service requirements. Only materials essential to the performance of this order shall be acquired. Authorized travel may include Mobile Training Team (MTT) deployments, conference attendance, and participation in required training activities. All ODCs must be approved in writing by the KO or COR prior to expenditure.
1.1.9.6.1 Deliverable: CDRL A002 Monthly Financial Status Report (MFSR) and Live Web-Based Financial and Resource Management Dashboard
10 | P a g e
1.1.10 Quality Assurance. The COR will evaluate the contractor’s performance under this contract in accordance with the Quality Assurance Surveillance Plan (QASP). This plan is primarily focused on what the Government must do to ensure that the contractor has performed in accordance with the performance standards. The Performance Requirements Summary (PRS) defines how the performance standards will be applied, the frequency of surveillance, and the minimum acceptable defect rate(s).
1.1.10.1 The contractor shall ensure 100% of its services and products go through a comprehensive contractor-led quality assurance and quality control process that when presented to the Government results in products that meet the requirements in the Performance Requirements Summary at PWS 6.1.
1.1.10.2 Quality Control Plan (QCP). The contractor shall develop and maintain an effective quality control program to ensure services are performed in accordance with the PRS in paragraph 6.1 (attachment 1) of this PWS. The contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services. The contractor’s quality control program is how they assure that work complies with the requirement of the contract.
1.1.10.3 The contractor’s initial draft QCP is to be submitted electronically to the KO and COR within 5 business days of the contract award and within 3 business days when changes are made thereafter. After Government approval/acceptance of the QCP, the contractor shall receive contracting officer’s acceptance in writing of any proposed change to its QC system.
1.1.10.3.1 Deliverable: CDRL A003 – Quality Control Plan
1.1.11 Facility Clearance. The Contractor and Subcontractor, performing work in support of this contract, shall have been granted a TOP SECRET security clearance from the Defense Industrial Security Clearance Office at the time of contract award. Overarching security requirements and Contractor access to classified information will be as specified in the basic DD Form 254.
1.1.11.1 Contractor personnel shall have and maintain a TOP SECRET/SCI clearance with Special Background Investigation (SBI) and be able to attain Special Intelligence with sub-compartment G (SI-G), Talent Keyhole (TK), KLM-R, HUMINT Control System (HCS), and North Atlantic Treaty Organization SECRET (NATO SECRET) access. Personnel shall sign a Non-Disclosure Statement.
11 | P a g e
1.1.11.2 Personnel supporting all Task Areas must be eligible to obtain a Counterintelligence (CI) polygraph examination. At the Government’s discretion, select personnel shall obtain the CI polygraph based on project and daily tasks following government nomination and approval. The CI polygraph will be provided by the government at government expense. Personnel shall perform within the security limitations of AR 381-10, USSID 1800, and other appropriate security regulations according to their intelligence disciplines. The Contractor will submit personnel for polygraph examinations within 10 business days of indoctrination at INSCOM if required by the mission and directed by the Government. Failure to pass the polygraph examination will result in loss of access to the Sensitive Compartmented Information Facility
(SCIF).
1.1.11.3 All individuals requiring access to information technology (IT) systems will have the appropriate security clearance and will be granted access according to their security clearance, need-to-know, and their IT position/category. Additional position category and investigation guidance is available in DOD5200.2-R. As referenced from AR 25-2, personnel requiring access to information systems processing classified information to fulfill their duties will possess the required favorable security investigation, security clearance, formal access approval (DoD Directive 8140.01, Cyberspace Workforce Management), and need to know. The Contractor will ensure individuals performing Task Area 2 and 3 will comply with DOD Directive 8140.01 (ADP-II / IT-II) upon onboarding.
1.1.11.4 Physical Security. The contractor shall be responsible for safeguarding at the government facility all government equipment, information, and property provided for contractor use. At the close of each work period, government facilities, equipment, and materials shall be secured. The contractor shall safeguard any Government equipment, information, and property at the contractor’s facility.
1.1.11.5 Key Control. The Contractor shall establish and implement methods of making sure all keys/key cards issued to the Contractor by the Government are not lost or misplaced and are not used by unauthorized persons. NOTE: All references to keys include key cards. No keys issued to the Contractor by the Government shall be duplicated. The Contractor shall develop procedures covering key control that shall be included in the QCP. Such procedures shall include turn-in of any issued keys by personnel who no longer require access to locked areas. The Contractor shall immediately report any occurrences of lost or duplicate keys/key cards to the Contracting Officer. The government also requires a Security Plan within the QCP since key control procedures are required in the QCP.
https://armyeitaas.sharepoint-mil.us/sites/INSCOM-DAIIS http://www.dtic.mil/whs/directives/corres/pdf/520002r.pdf http://www.dtic.mil/whs/directives/corres/pdf/520002r.pdf http://www.army.mil/USAPA/epubs/25_Series_Collection_1.html
12 | P a g e
1.1.11.6 In the event keys, other than master keys, are lost or duplicated, the Contractor shall, upon the direction of the Contracting Officer, re-key or replace the affected lock or locks;
however, the Government, in its option, may replace the affected lock or locks or perform re-keying. When the replacement of locks or re-keying is performed by the Government, the total cost of re-keying or the replacement of the lock or locks shall be deducted from the monthly payment due to the Contractor. In the event a master key is lost or duplicated, all locks and keys for that system shall be replaced by the Government, and the total cost is deducted from the monthly payment due to the Contractor.
1.1.11.7 The Contractor shall prohibit the use of Government-issued keys/key cards by any persons other than the Contractor’s employees assigned to support this requirement. The Contractor shall prohibit the opening of locked areas by Contractor employees to permit the entrance of persons other than Contractor employees engaged in the performance of assigned work in those areas, or personnel authorized entrance by the KO.
1.1.11.8 Lock Combinations. The Contractor shall establish and implement methods of ensuring that all lock combinations are not revealed to unauthorized persons. The Contractor shall ensure that lock combinations are changed when personnel having access to the combinations no longer need to know such combinations. These procedures shall be included in the Contractor’s QCP. The government also requires a Security Plan within the QCP since key control procedures are required in the QCP.
1.1.12 Antiterrorism Considerations. In accordance with DFARS, 27 January 2011, 207.105(b) (20) (D), and DOD Instruction 2000.16, DoD Antiterrorism Standards, the contractor is hereby advised that it shall comply with the policies and procedures of the U.S. Antiterrorism Officer (ATO) at each installation where work is being performed. DoD Instruction 2000.16 is available at the Washington Headquarters Services website at http://www.dtic.mil/whs/directives/. Information about the INSCOM procedures and policies will be provided later. A modification to the contract will be the instrument of notification for this action. The contractor may submit a request for an equitable adjustment for any directly incurred costs for compliance with these policies and procedures, following the modification incorporating the policy and procedures guidance. Equitable adjustment requests shall comply with clauses.
1.1.12.1 Antiterrorism and Force Protection (AT/FP). AR 350-1, 4 August 2011, Army Training and Leadership Development, Section II, G-7, Antiterrorism and Force Protection.
Specific Army standards for AT/FP training are listed in chapter 5, AR 525-13, 11 September 2008. Individual AT/FP training is mandatory for all Soldiers, Department of the Army civilians, and DOD contractors and is strongly recommended for family members prior to traveling outside the 50 United States and its territories and possessions for any reason, including mobilization, temporary duty, permanent change of station, and leave. There is also an AT/FP training requirement for personnel stationed outside the United States. Individual AT/FP training is valid for one (1) year and must be documented.
http://www.dtic.mil/whs/directives/
13 | P a g e
1.1.12.2 AT Level I Training. All contractor employees, including subcontractor employees, requiring access to Army installations, facilities, and controlled access areas shall complete AT Level 1 awareness training within 30 calendar days after the contract start date or the effective date of incorporation of this requirement into the contract, whichever is applicable. The contractor shall submit certificates of completion for each affected contractor employee and subcontractor employee to the COR/ACOR or to the contracting officer, if a COR/ACOR is not assigned, within 15 calendar days after completion of training by all employees and subcontractor personnel. AT Level 1 awareness training is available at the following website:
https://atlevel1.dtic.mil/at.
1.1.12.3 AT Awareness Training for Contractor Personnel Traveling Overseas. This requires U.S. based contractor employees and associated sub-contractor employees to make available and to receive government provided area of responsibility (AOR) specific AT awareness training as directed by AR 525-13. Specific AOR training content is directed by the combatant commander with the unit ATO being the local point of contact.
1.1.13 Access and General Protection/Security Policy and Procedures. Contractor and all associated subcontractor's employees shall comply with applicable installation, facility and area commander installation/facility access, and local security policies and procedures (provided by government representative). The contractor should also provide all information required for background checks to meet installation access requirements to be accomplished by the installation Provost Marshal Office, Director of Emergency Services, or Security Office. The contractor workforce must comply with all personal identity verification requirements as directed by DOD, HQDA, and 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.
1.1.14 iWATCH Training. The contractor and all associated sub-contractors shall brief all employees on the local iWATCH program (training standards provided by the requiring activity ATO. This locally developed training will be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity to the COR/ACOR. This training shall be completed within 30 calendar days of the contract award and within 30 calendar days of the new employee’s commencing performance. iWATCH training results shall be reported to the COR/ACOR not later than 45 calendar days after contract award.
https://atlevel1.dtic.mil/at
14 | P a g e
1.1.15 OPSEC Standing Operating Procedure/Plan. The contractor shall develop an OPSEC Standing Operating Procedure (SOP)/Plan within 90 calendar days of contract award, to be reviewed and approved by the responsible Government OPSEC officer, per AR 530-1, Operations Security. This SOP/Plan will include the government's critical information, why it needs to be protected, where it is located, who is responsible for it, and how to protect it. In addition, the contractor shall identify an individual who will be an OPSEC Coordinator. The contractor will ensure this individual becomes OPSEC Level II certified per AR 530-1.
1.1.16 Operations Security (OPSEC). AR 530-1, 26 Sep 2014, Training Programs. The Contractor shall provide OPSEC training to all employees regarding the safeguarding of sensitive information prior to employees being allowed access to such information. Chapter 4 of AR 530-1, Training, requires that newly arrived personnel receive an OPSEC orientation briefing within the first 30 days of arrival at the organization. The AR requires that all personnel receive an annual OPSEC briefing. Contractor personnel may utilize the OPSEC briefings presented by the INSCOM OPSEC Program Manager/Coordinator. The Contractor will submit certificates of completion or sign in rosters all initial and annual OPSEC training to the COR. The above requirements will flow down to all subcontractors working on or providing support to the contract. The Contractor shall not release sensitive information to the public without prior written approval from the Contracting Officer. All contractor requests to release sensitive information shall be in writing and clearly explain the necessity for the release of the information and consequences if approval is not granted.
1.1.17 All material produced by the contractor which will be released to the public will be subject to OPSEC and Security reviews from INSCOM OPSEC Officer, Security Officer, and INSCOM Public Affairs Office prior to release.
1.1.18 The Contractor shall destroy all sensitive program material at the completion of the contract to ensure the information cannot be accessed or utilized for any purpose. The Contractor will also notify the Contracting Officer in writing of its destruction. These same requirements will flow down to all subcontractors working on or providing any sensitive information related to the contract.
1.1.19 DoD Cyber Awareness Challenge / Information Assurance (IA) Training. All contractor employees and associated sub-contractor employees must complete the DoD IA awareness training before issuance of network access and annually thereafter. All contractor employees working in IA/IT functions must comply with DoD and Army training requirements in DoDD 8140.01 (formerly DoDD 8570.01-M), and AR 25- 2 within 30 calendar days of employment.
1.1.20 Information assurance (IA)/Information technology (IT) Certification. Per DoDD
8140.01 (formerly DoDD 8570.01-M), and AR 25-2, the contractor employees supporting IA/IT functions shall be appropriately certified upon contract award. The baseline certification as stipulated in DoDD 8140.01 (formerly 8570.01-M) must be completed upon contract award.
15 | P a g e
1.1.20.1.1 Deliverable: CDRL A004 – OPSEC Standing Operating Plan/Training Certificates
1.1.21 For Contractors Authorized to Accompany the Force. DFARS Clause 252.225-7040, Contractor Personnel Authorized to Accompany U.S. Armed Forces Deployed Outside the United States. The clause shall be used in solicitations and contracts that authorize contractor personnel to accompany US Armed Forces deployed outside the US in contingency operations;
humanitarian or peacekeeping operations; or other military operations or exercises when designated by the combatant commander. The clause discusses the following AT/OPSEC related topics: required compliance with laws and regulations, pre-deployment requirements, required training (per combatant command guidance), and personnel data required. DFARS Clause 252.225-7043, Antiterrorism/Force Protection for Defense Contractors Outside the US. The clause shall be used in solicitations and contracts that require performance or delivery in a foreign country. This clause applies to both contingencies and non-contingency support. The key AT requirement is for non-local national contractor personnel to comply with theater clearance requirements and allows the combatant commander to exercise oversight to ensure the contractor's compliance with combatant commander and subordinate task force commander policies and directives.
1.1.22 Handling or Access to Classified Information. 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.
1.1.23 Courier Responsibility. Contactor personnel who are authorized to transport classified information between facilities must be in compliance with DoD 5220-22.M. The contractor shall ensure the following: Couriers are properly briefed and documented by company FSO on courier responsibilities. Couriers are issued a courier identification card that contains the contract employee's name and photograph. The courier will always retain classified information in his/her personal possession. Classified information is inventoried prior to departure. Information will be placed in two opaque envelopes (inner/outer). The inner envelope shall be sealed and marked top and bottom, front and back with the highest classification of the information, complete address of the sender and receiver. A receipt for the information will be placed inside the outer sealed envelope. No classification markings shall be placed on the outer envelope and addressed.
16 | P a g e
1.1.24 Post Award Conference/Quarterly Progress Meetings. The Contractor shall attend any post-award conference convened by the contracting activity or contract administration office in accordance with Federal Acquisition Regulation Subpart 42.5. The KO, Contracting Officers Representative (COR), and other Government personnel, as appropriate, may meet quarterly with the contractor to review the contractor's performance. At these meetings, the contracting officer will inform the contractor of how the government views the contractor's performance and the contractor will inform the Government of problems, if any, being experienced. Appropriate action should be taken to resolve outstanding issues. These meetings shall be at no additional cost to the government.
1.1.25 COR/Alternate COR (ACOR). The COR/ACOR will be designated by a formal letter.
The COR/ACOR monitors all technical aspects of the contract and assists in contract administration. The COR is authorized to perform the functions identified in the appointment letter. The COR/ACORs formal designation letter, a copy of which is forwarded to the Contractor, states the responsibilities and limitations of the COR/ACOR, especially regarding changes in cost or price, estimates, or changes in delivery dates. The COR/ACOR is not authorized to change any of the terms and conditions of the resulting contract.
1.1.26 Organizational Conflict of Interest. Contractor and subcontractor personnel performing work under this contract may receive, have access to or participate in the development of proprietary or source selection information (e.g., cost or pricing information, budget information or analyses, specifications or work statements, etc.) or perform evaluation services which may create a current or subsequent Organizational Conflict of Interests (OCI) as defined in FAR Subpart 9.5. The Contractor shall notify the Contracting Officer immediately whenever it becomes aware that such access or participation may result in any actual or potential OCI and shall promptly submit a plan to the Contracting Officer to avoid or mitigate any such OCI. The Contractor’s mitigation plan will be determined to be acceptable solely at the discretion of the Contracting Officer and in the event, the Contracting Officer unilaterally determines that any such OCI cannot be satisfactorily avoided or mitigated, the Contracting Officer may affect other remedies as he or she deems necessary, including prohibiting the Contractor from participation in subsequently contracted requirements which may be affected by the OCI.
1.1.27 Transition. The transition period is 30 calendar days.
1.1.27.1 Transition In: The Contractor shall complete transition from the incumbent in accordance with a Transition In Plan due with their proposal submission at award. The Contractor shall complete transition from the incumbent in accordance with their proposed transition plan. The contractor shall ensure that all positions are filled to ensure there will be minimal service disruption to vital Government business and no service degradation during and after transition.
17 | P a g e
1.1.27.2 The Contractor shall meet or exceed minimum incoming staffing levels as it relates to Transition In Period. In this context, staffing is defined as personnel who are qualified, available, and approved for indoctrination at HQ INSCOM. Minimum staffing levels shall be as follows:
30% within 7 calendar days, 50% within 14 calendar days,75% within 21 calendar days, 90% within 30 calendar days. The staffing level shall be at 100% by 45 calendar days post contact award.
1.1.27.2.1 Deliverable: CDRL A005 – Transition in Plan
1.1.28 The Contractor shall identify how it will coordinate with the incoming/outgoing Contractors and Government personnel to transfer regarding the following:
• Project management processes
• Points of Contact
• Location of technical and project management documentation
• Status of ongoing technical initiatives
• Appropriate Contractor-to-Contractor coordination to ensure a seamless transition.
• Transition of personnel
• Identify schedules and milestones
• Identify actions required of the Government
• Establish and maintain effective communication with the incoming
Contractor/Government personnel for the period of the transition via weekly status meetings.
1.1.29 Transition Out: The Contractor shall cooperate with the Government to transition these efforts at the conclusion of the contract. The Contractor shall include a Transition-Out Plan and provide it to the Government NLT 120 calendar days prior to the expiration of the contract for approval by the Government within 5 business days of receipt. If unacceptable, the contractor will have 5 calendar days to revise. The transition period shall not exceed 90 calendar days. The Transition-Out plan shall facilitate the accomplishment of a seamless transition from the incumbent to an incoming Contractor / Government personnel member at the expiration of the contract.
1.1.29.1 The contractor should maintain a sufficient staffing level to continue executing all tasks during the Transition Out period. The Contractor shall identify how it will coordinate with the incoming/outgoing Contractor and Government personnel to transfer knowledge regarding the following:
1.1.29.2 Project management processes.
• Location of technical and project management documentation
• Status of ongoing technical initiatives
• Appropriate Contractor-to-Contractor coordination to ensure a seamless transition.
• Transition of personnel
18 | P a g e
• Identify schedules and milestones
• Identify actions required of the Government
1.1.29.3 Establish and maintain effective communication with the incoming Contractor / Government personnel for the period of the transition via weekly status meetings
1.1.29.4 The contractor shall establish and maintain effective communication with the incoming contractor/Government representative for the period of the transition via weekly status meetings.
This may include audio/video-teleconferences or physical meetings with both contractor vendors and Government personnel.
1.1.29.5 Ensure all services and performance objectives required by PWS requirements are met throughout the phase-out period. Establish procedures with the successor to ensure transition of provided services without a degradation of service. Provide copies of all instructions, records, databases, performance metric data, vendor points of contact, and all other procedures developed by the contractor in the performance of this requirement to the successor.
1.1.29.5.1 Deliverable: CDRL A006 – Transition Out Plan
1.1.29.6 In/Out Processing: The Facility Security Officer (FSO) must provide to COR, the following information on all Contractor Manpower Equivalents (CMEs) performing HQ INSCOM missions and are direct labor, for input into the INSCOM In/Out Processing Portal.
1.1.29.7 Contractor personnel shall complete DoD Cyber Awareness Challenge/Information Assurance (IA) Training (required for Government systems access), and obtain a completion certificate, prior to Entry on Duty (EOD). The completion Certificate shall be sent to the responsible COR to confirm compliance prior to EOD.
1.1.29.8 Contractor personnel shall also obtain a CAC prior to EOD during the transition period.
1.1.29.9 Unauthorized Disclosure of Classified Information (UDCI). Dissemination of classified information must be conducted in strict accordance with established security regulations and procedures. Improper or unauthorized disclosure, either willful or inadvertent, presents a serious risk to national security. Upon validation that a UDCI has occurred, the COR and contractor will review the incident to determine what measures are required to prevent future UDCI occurrences. Should multiple UDCIs occur, the Contracting Officer may direct the removal of any contractor employee incurring multiple UDCIs, assess an appropriate annual performance rating reflecting that multiple UDCIs have occurred, or any other appropriate action to prevent future UDCIs from occurring.
1.1.30 Data Rights
1.1.30.1 Per DFARS 252.227-7020 the Government shall have unlimited rights to all works (including but not limited to all reports, documents, data, summaries, Standing Operating Procedures, computer databases, computer software (including source code), or computer software documentation) first produced, created, or generated under this contract. With respect to data rights and delivery, the contractor developing and storing software on Government
19 | P a g e resources and computers shall be considered delivery of the computer software from the contractor to the Government.
20 | P a g e
2 PART 2. GOVERNMENT FURNISHED EQUIPMENT, PROPERTY AND
SERVICES
2.1 GOVERNMENT PROPERTY
2.1.1 The contractor shall be responsible and liable for Government property in their possession pursuant to FAR 52.245-1.
2.1.1.1 At time of award no Government Furnished Property (GFP) is expected to be provided to the contractor. However, there is a possibility for Contractor Acquired Property (CAP). In the event that the contractor acquires property or is furnished property the following applies.
2.1.1.2 As defined in FAR Part 45.1, GFP is “property in the possession of, or directly acquired by, the Government and subsequently furnished to the contractor for performance of a contract.
Government-furnished property includes, but is not limited to, spares and property furnished for repair, maintenance, overhaul, or modification. Government-furnished property also includes Contractor-acquired property (CAP) if the CAP is a deliverable under a cost contract when accepted by the Government for continued use under the contract.”
2.1.1.3 GFE and CAP Accountability: When the contractor is to acquire property on a reimbursable basis, that property - as CAP for the basis of this Contract -- shall be deemed GFE.
The contractor is required to track all GFE in an electronic data-base and maintain a valid hand receipt from the designated Government site-lead or property book owner. The contractor shall account for 100 percent of all GFP and provide the report to the COR.
2.1.1.4 If GFE or CAP is added to this contract the contractor shall develop a GFE and CAP report for Government approval on a monthly basis.
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .