ASAALT RFI PWS.pdf

PERFORMANCE WORK STATEMENT

ASSISTANT SECRETARY OF THE ARMY FOR ACQUISITION, LOGISTICS, AND

TECHNOLOGY (ASA (ALT))

ACQUISITION DATA MANAGEMENT TOOL SUPPORT SERVICES

PSC Code: R499 PSC Name: Support – Professional – Other NAICS: 541511 Custom Computer Programming Services

1. BACKGROUND

The Army is implementing an Acquisition Domain Data System and centralized repository that is reforming the way it conducts Acquisition business. As part of this reformation, the Army is standardizing key metrics and collecting them within the acquisition domain. Collecting the data for these key metrics has highlighted the need for a centralized data repository. Army Leaders decided to leverage the Project Management Resource Tool (PMRT) to achieve this goal. PMRT, a tool developed by the Air Force, integrates infrastructure, hardware, software, and applications to provide the Air Force and DoD life cycle acquisition organizations with an integrated tool set to manage their programs. PMRT will allow users at the Program Offices to conduct daily financial business activities, while capturing that data at the point of creation so that it can be properly governed. PMRT is comprised of Monthly Acquisition Reports (MAR/Program Data Alignment Application (PDAA), Data Access Program Reporting (DAPR) (PDAA replaced MAR and DAPR but historical files remain), and the Comprehensive Cost and Requirements (CCaR™) tool. PMRT will allow the Army to focus on collecting the programmatic and financial information while providing data visualization tools to support senior Army Leader decision making.

2. OBJECTIVE

ASA (ALT) has a requirement to implement an Acquisition enterprise programmatic and financial management system that automates working-level processes within program management offices that allows for real-time access to key information for executive decision makers and action officers. PMRT will provide a simple, intuitive, comprehensive interface that allows users to define and coordinate Army program requirements, create budgets, forecast program execution, maintain visibility of program execution, track contracts and reconcile execution data. Additionally, PMRT must have the ability to generate automated reports and visualizations from the data that has been input into the system. PMRT must seamlessly interface with other Army and DoD external budget, execution and programmatic systems so that it can be utilized as the centralized tool and data repository to support the Army’s Acquisition program and financial management needs. PMRT must adhere to the Army’s Data Strategy.

3. PERFORMANCE REQUIREMENTS

3.1. Modernization, Enhancements, and Implementation of ASA (ALT) Acquisition

Data Management Database and Tools:

3.1.1. The contractor shall arrange a contract kick-off meeting with the Government through the Contracting Officer’s Representative (COR) to discuss and review the requirements of this Performance Work Statement no later than one (1) week after the start of the period of performance. The contractor shall submit a written report within 30 days of kick-off identifying applicable system architecture, existing servers, and capability to be leveraged for ASA (ALT) identified offices.

Attendance at this meeting will include key Government personnel working for

ASA (ALT).

3.1.1.1. The contractor shall provide the services listed in this document to the

ASA (ALT), MRDC, 12 J/PEOs, 85 program offices. The contractor must provide training through a web based training platform and/or in person training as requested for certification application hosted by the Government.

3.1.1.2. The Army reserves the option for other Army organizations to request optional above baseline contractor support necessary to assist during the PMRT future implementation and emerging initiatives that will require to share data with PMRT as described in sections 3.5-3.6.

3.1.1.3. The Army reserves the option to implement PMRT within other organizations within the Army to include, but not limited to: Army Futures Command HQs, Army Combat Capabilities Development Command (CCDC) HQs, Rapid Capabilities and Critical Technologies Office, additional HQDA commands and the following Development Centers at an additional cost to the government:

AFC Headquarters CCDC Headquarters CCDC Armaments Center CCDC Aviation & Missile Center CCDC Army Research Laboratory CCDC Chemical Biological Center CCDC C5ISR Center CCDC Data & Analysis Center CCDC Ground Vehicle Systems Center CCDC Soldier Center CCDC-Americas CCDC-Atlantic CCDC-Pacific

3.2. Regional Support

The contractor shall assign regional PMRT site leads to support the geographic location where PMRT is deployed. Note: MRDC is no longer an Army command but is under the Defense Health Agency.

In addition, several of their Army programs have gone to PEO-Soldier. However, they have expressed an interest in MRMC HQ using PMRT. MRDC will have an optional CLIN. PEO-CS&CSS will also have an optional CLIN.

3.2.1. The contractor shall provide regional support the following tasks:

3.2.1.1. Capturing, categorizing and reporting Tier 1-4 helpdesk tickets

3.2.1.1.1. PMRT Support Levels

Tier 1 Basic help desk resolution and service desk delivery Tier 2 Expert product and service support Tier 3 In-depth technical support Tier 4 Outside support for problems supported by external the organization

3.2.1.2. Resolve Tier 1 and Tier 2 issues and monitor the progress and closeout of Tier 3 and 4 issues

3.2.1.3. Coordinating onsite support to offices which require customer support

3.2.1.4. Provisioning new users in PMRT.

3.2.1.5. Capturing and supporting requests for training of new hires.

3.2.1.6. Capturing and reporting requests for additional enhancements.

3.2.1.7. Reporting all information captured to the government on a monthly basis.

3.2.1.8. Assisting with PEO and headquarters PMRT questions related to data management, MAR/DAPR/PDAA (replaced MAR and DAPR but historical files remain in PMRT)/CCaR™ functionality.

3.3. Central Support (HQ)

3.3.1. The contractor shall provide CCaR™ overall program management, training and support services throughout ASA (ALT) and HQDA, while coordinating support with the Regional Support Team and onsite personnel within the PEOs.

3.3.2. The contractor shall provide dedicated technical support to the ASA (ALT) HQs to include but not limited to the following areas: programmatic reporting to OSD; process automation and reengineering; and data architecture, governance, and analytics.

3.3.3. The contractor shall maintain the PMRT production site. This includes complying with Army and DoD cybersecurity requirements, conducting maintenance outages, reporting unscheduled outages, restoring service, managing and implementing software releases, performing system administration functions, and keeping the hosting provider/ Government team informed during any of these events.

3.3.4. The contractor shall sustain a training web based site which will provide the Government team with a training tool to improve their proficiency in functions within the financial management portion of the CCaR™ module. At a minimum the contractor shall provide courses for the functions listed below, with each course to include a thorough test which will demonstrate that trainees can fully perform the following functions: Program Manager, Budget Analyst, Program Analyst, General, Analyst and ASA(ALT) CCaR™ Administration.

3.3.5. The Contractor shall add lesson plans and assessments associated with new features and capabilities.

3.3.6. The Contractor shall develop electronic desk guides and training for each role identified in PMRT. Desk guides shall include an introduction, background, and general information with necessary screen shots required for an individual performing in the respective role to navigate through and use the dashboard. Initial revision of any modifications to the Training and Certification site shall be submitted to the Government for approval.

3.3.7. The contractor will maintain a certification program, in conjunction with required web-based training. The certification plan will detail a certification program to assess the system users’ knowledge, skills and abilities and certify that the system users can proficiently use the system. Multiple certifications will be offered based on the user roles and responsibilities.

3.3.8. The contractor shall use applications that run from one or more data sources and present data as though it all came from a single synchronized source. In the event that data sources are phased out and/or new sources are defined, the Contractor shall map or remap feeds into the integrated database/dashboard/visualizations.

3.4. Engineering & Development Support (Optional Above Baseline Development

Support)

3.4.1. Continued expansion of critical PMRT interfaces via the Acquisition Data Service

Broker (ADSB).

3.4.2. On-boarding of new capabilities, expansion of integrated IT operational environment to include acquisition program management automation, application and acquisition dashboard data visualizations development, and enhancement of PMRT to allow increased visibility to acquisition programmatic and financial information for all Army Acquisition programs.

3.4.3. The contractor shall adhere to the Government’s configuration control process for recording, defining, vetting and tracking changes within the systems at all levels of the organization (PM/PEO, etc.). Requested customizations, interfaces and/or issues will be recorded within established systems, with visible tracking statuses and worked through a configuration board and process that includes appropriate government representatives.

3.4.4. The contractor shall support SDLC activities to include requirements definition, systems integration, development, technical reviews, testing, deployment, and sustainment.

3.4.5. The Army reserves the option for the contractor to integrate and automate a connection to the DoD PIEE information sources into the system in order to associate contract performance information to Acquisition efforts within the visualization area at additional cost to the government.

3.4.6. The Army reserves the option for the contractor to facilitate and document the Program Objective Memorandum (POM) process and the President’s Budget (PB) submission.

The program must automatically compute a bottom-up out year budget request to support formal budget submissions. The program must be able to support what-if drills to allow organizations identify the impacts of budget cuts and plus ups at additional cost to the government.

3.4.7. The contractor shall support the migration of the PMRT production site from ALTESS to a cloud computing platform. This includes complying with Army and DoD cybersecurity requirements, conducting maintenance outages, reporting unscheduled outages, restoring service, managing, and implementing software releases, performing system administration functions, and keeping the cloud computing platform team and the Government team informed during any of these events. The contractor shall support the migration of the PMRT production site from hosting with ALTESS to a cloud computing platform estimated starting in calendar year 2026 without system interruption (other than the production cutover) or degradation of service.

3.4.8. Until 13 Sep 25, the Army falls under the AF Authority To Operate (ATO). As such, coding in the PMRT system and some developmental efforts are shared with AF PMRT developers. After the above date, the PMRT system for Army will be under the Army ATO. If development is still ongoing at that time, Army will require developers unless an agreement can be reached with the AF to share those assets. This should be done through a modification to the contract that is awarded for this PoP, however costs are required to be known up front prior to the award.

3.5. J/PEO Dedicated Customer Support. (Optional Above Baseline)

3.5.1. Organizations within ASA (ALT) will be able to request and fund additional onsite contractor support to meet internal emerging requirements. Their tasks will include, but are not limited to the following:

3.5.1.1. The contractor shall provide supplemental training to improve staff skills in using the system on an as required basis at the request of the Government.

3.5.1.2. The contractor shall assist the Government team during the execution of financial management tasks associated with PMRT to include defining requirements, create budgets, forecast program execution, maintain visibility of program execution, track contracts and reconcile execution data.

3.5.1.3. The contractor shall support development of PMRT interfaces with other business intelligence tools to include dashboard and data visualizations for analytical analysis in support of PMs and PEO leadership.

3.6. Engineering & Development Support (Optional Above Baseline Support)

TammiLambert Does the optional clins support this requirement.

3.6.1. The Army reserves the option for the contractor to provide a visualization capability that ingests MS Project schedules into the system for tracking program schedules at additional cost to the government.

3.6.2. The potential exists that the Government may require additional future support positions during the performance of this PWS related to any of the Tasks outlined above and defined within this section. The Contracting Officer may exercise an optional task by written notice to the Contractor within 30 days. Delivery of added optional labor shall continue at the same rate as like labor negotiated in the order, unless the parties otherwise agree.

3.6.3. The Army reserves the option for the contractor to integrate the PMRT baseline into an identified SIPR environment. The integration will ensure appropriate cross domain automation of information interfaces and data integrity between the NIPR and SIPR instances, ensuring that periodic updates from NIPR to SIPR do not overwrite SIPR instance only information. Further integration of the PMRT Enterprise Analytics into an identified SIPR environment may include pulling in SIPR only available interfaces and incorporating them into appropriate EA applications. These requirements will include support to the Army Rapid Capabilities and Critical Technologies Office

(RCCTO).

3.6.4 CCaR™ Licenses. ASA(ALT) shall procure and maintain a perpetual Enterprise

CCaR™ License per the terms and conditions contained within the ASA(ALT) CCaR™ Enterprise License Agreement.

3.7. PMRT System Requirements. Contractors shall be capable of providing the Government team with support in the following area:

System Requirements

Manage Acquisition Program Financial Requirements. (PM/PEO Level) Identify and document Financial Requirements.

Budget for the financial requirements across all years and types of funding needed for the requirement.

Coordinate financial requirements through electronic workflows.

Forecast funds execution for financial requirements.

Automated creation, coordination & approval of targets/controls.

Restrict Target/Control creation to authorized users.

Target creation supports appropriated, reimbursable, working capital and FMS funds.

Target creation will support providing target controls into financial systems Automated Target coordination will capture all information required to meet Guidance.

Automated Target coordination will automatically update the Budget Authorized amount when a Target is approved.

Account/Address listing that displays the current annual and quarterly amounts for all accounts/addresses.

Account/Address listing that displays all target load transactions for all accounts/addresses.

Account/Address listing that compares target load transactions for all accounts/addresses against the transactions in the accounting system.

Executes Acquisition Program Financial Requirements.

Automate regulatory and statutory compliance documentation for executing funds on a financial requirement.

Capture and track reimbursable and direct-cite funds from external organizations provided to fund the financial requirement.

Prepare the Commitment Document (aka Requisition). Army will accept L1 approved documents (GFEBS interface requirement) Automatically relate the Commitment Document (aka Requisition) to the financial requirement.

Check the available budget authority on the financial requirements prior to sending the funds commitment.

Coordinate and Certify Commitment Document (aka Requisition). Army will accept L1 approved documents (GFEBS interface requirement) Automatically relate commitment, obligation, expenditure and disbursement transactions to the financial requirement. (Army uses GFEBS) Receive transactional/summary execution and requisition data from the accounting system to report financial execution status and reconcile financial execution. (Army uses GFEBS) Receive daily commitment, obligation, expenditure, and disbursement transactional data from the accounting systems.

Receive daily commitment, obligation, expenditure, and disbursement summary data from the accounting systems.

Receive daily commitment document data from the accounting system Receive daily contract obligation and expenditure data from GFEBS and/or MOCAS.

Receive daily contractual award data from the contract writing system.

Automatically tie commitment, obligation, expenditure, and disbursement transactional data to the commitment document(s) and lines tied to the financial requirement.

Allow actual funds execution to be compared to execution forecasts.

Report commitment, obligation, expenditure and disbursement amounts for financial requirements.

Automatically report acquisition program status to Service Acquisition Organization, ASA(ALT) and OSD AT&L.

Interface with OSD’s DAVE/DAMIR bi-directionally Capture Acquisition Programs, Investment Activities, O&M Programs, O&S Programs and FMS Programs.

Provide System level Management Internal Controls for maintaining authoritative list of programs.

Publish program funding sources and execution for acquisition reporting.

Provide Interactive Acquisition views via visualization capability service that allows for ingest of additional data sources and user customization, along with enterprise analytics capability Publish program funding sources and execution to the Acquisition Dashboards Automatically generate program business reviews and program execution reviews using power point charts. The goal of these reviews is to focus on programs that are not executing according to plan. The Army must understand the reasons for under-executing programs since this places their funding “at risk” that may be swept for higher priorities by OSD or Army. These reviews will occur quarterly, at a minimum.

Provide Periodic Programmatic Assessment Reporting against APBs Capture assessments against APB or other recorded baseline measures Allow for multi-level views of assessment information to support lower level tracking and appropriate upper level reporting requirements (06, PEO, or ASA(ALT), OSD)

Capture Assessment approvals and periodicity Support data release based on approvals and established time frames Provide data access based on roles based provisioning at the organization and "Program" levels

4. MONTHLY STATUS REPORTS

4.1. The Contractor shall submit to the COR monthly status report of implementation operational status and staffing status reports.

4.2. Reports are due no later than five (5) business days after the end of the reported month.

4.3. Monthly Status Reports (MSR) shall contain detailed narrative information on significant tasks accomplished; challenges encountered or anticipated and plan to overcome or mitigate challenges; anticipated tasks for the next reporting period; and any other related information.

4.4. MSR’s Reports should emphasize tasks accomplished from the past two weeks month to present and anticipated tasks for the next month. These reports serve as a quick and concise overview of the current state of dashboard upgrade, enhancement, and maintenance and are designed to be a one (1) to two (2) page management tool.

4.5. These reports shall provide an overall outcome of goals and objectives met in support of this contract. Metrics may be included in the Monthly Status Report.

4.6. Monthly Staff Status (MSS) reports shall contain the name of each individual by location and assigned support task. MSS should include any anticipated additions or deletions of personnel.

See 12.5.3.3 for further detail.

4.7. J/PEO and other organizations are to be referenced by official name and be synchronized between the two reports.

4.8. Project Status Reports. Monday’s bi-weekly (except during federal holidays, then this report is due the next workday) the task coordinator contactor shall generate at a minimum a task report displaying all tasks open, closed, or past due.

5. PLACE OF PERFORMANCE

5.1. The Government reserves the unilateral right to change where work is performed or add additional sites under this task order as necessary to support the ASA (ALT) mission. Current locations include but are not limited to:

• Pentagon, Washington D.C.

• Fort Belvoir, VA

• Aberdeen Proving Ground, MD

• Warren, MI

• Huntsville, AL

• Austin, TX

• San Diego, CA

• Ft. Detrick, MD

• Orlando, FL

• Picatinny Arsenal, NJ

6. PERIOD OF PERFORMANCE

Period of performance is anticipated to be for 1 base period of twelve months and 4 option periods.

Provide a data service broker to allow for new interfaces to be identified and exposed appropriately to the visualization services area.

Base Period - 06/30/2025 – 06/29/2026 Option Period 1 - 06/30/2026 – 06/29/2027 Option Period 2 - 06/30/2027 – 06/29/2028 Option Period 3 - 06/30/2028 – 06/29/2029 Option Period 4 - 06/30/2029 – 06/29/2030

7. SYSTEM PERFORMANCE REQUIREMENTS

PWS

SECTION

ACCEPTABLE QUALITY LEVEL METHOD OF

SURVEILLANCE

5.1 Modernization, Enhancement, and Implementation of ASA(ALT) Acquisition Data Management Database and Tools

Performance occurs with no required re- performance or re-work at least 95% of the time. Problems that occur are minor and are resolved in a satisfactory manner.

Routine inspection of deliverable service.

5.2 Maintenance of Existing

System

Performance occurs with no required re- performance or re-work at least 95% of the time. Problems that occur are minor and are resolved in a satisfactory manner.

Routine inspection of deliverable service.

5.3 Monthly Status/Task Reports Deliverable is submitted with no required revision at least 95% of the time. Problems that occur are minor and are resolved in a satisfactory manner.

Routine inspection of deliverable.

5.3.4 System Availability

(Application Level). This does not apply to Army network problems.

System shall be available 95% of the time between the core hours 8:30 – 1700 hours Local

Routine inspection of deliverable.

PWS

SECTION

DESCRIPTION FORMAT DISTRIBUTION DUE DATE

3.3.5 Training Contractor Format Online/via

email/or in person as requested

According to release scheduled approved by the Government

3.3.7 Updated desk guides

when there are major updates

Contractor Format Send to COR via email

Submission – Within 30 working days of major update.

Monthly Status Report

/ Staffing Reports

Contractor Format in accordance with Preferred customer tool

Send to COR via email

No later than five (5) business days after end of reported month

5.2 Project

Status

Reports

Contractor Format Send to COR via email

First report due 30 days after contract award.

8. DELIVERABLES

8.1. All deliverables shall be submitted to the Government Contracting Office Representative via email and to the Contracting Officer, GSA Program Manager and Contracting Officer Representative (COR) through GSA Assisted Services Shared Information System (GSA ASSIST), Post Award Collaboration (PAC) Tool. Delivery format for reports, documentation presentations, briefings, and diagrams shall be via electronic media in the Microsoft Office 2016 software suite or later versions. Graphical formats of sufficient quality to render required readability detail, such as gif, jpg, bmp, tif, png, etc. are also acceptable for diagrams. All technical documentation and data exchanged between the Contractor and the Government shall be protected from public disclosure with marking contained therein (i.e., classified in accordance with appropriate DoD approved security classification directives and guides as applicable).

8.2. GSA ASSIST is an online, web-based purchase order system designed to facilitate the development of delivery and purchase orders within FAS programs. No classified information shall be uploaded in ASSIST.

8.3. Deliverables are subject to review and, if warranted, may be returned within ten (10) business days to the contractor for revision. Upon receipt of Government Comments, the contractor will provide the final revised deliverable according to a schedule provided by the Government.

9. QUALITY CONTROL

9.1. The Contractor shall ensure quality service is maintained to perform services throughout the life of the contract and methods for improving the overall quality are also employed. The Contractor shall prepare and submit a Quality Control Plan (QCP) within five (5) working days of contract award to the COR for Government review and approval. If revisions to the QCP are required, the Contractor shall re-submit the revised QCP within three (3) working days of written notification from the Government. The QCP shall discuss the Contractor’s overall approach and procedures for evaluating each of the major service areas contained in the PWS, communicating with the Government, resolving deficiencies, identifying potential improvements, and managing day-to-day operations. As part of the QCP, the Contractor may conduct internal QC inspections. Results of any contractor internal QC inspections and corrective actions taken shall be made available to the Government for review throughout the performance of this PWS. The Government may periodically require the Contractor to update/revise the QCP to ensure quality service is maintained throughout the life of the contract.

9.2. The contractor shall follow and apply industry best practices and standards to the maximum extent possible.

9.3. Contractor personnel shall have an understanding of these best practices and standards as appropriate for their specialized areas. The contractor is responsible for ensuring that their staff is well trained on current technologies and on industry best practices. The Contractor shall fill all the positions identified in the PWS NLT 30 days after contract award.

Vacancies shall be filled NLT 30 days from the time the position becomes vacant. The Contractor shall ensure no service degradation during and after any personnel changes to include providing bridge support through reach back to our central support resources, our Helpdesk support staff, and corporate SMEs to ensure that PWS requirements are met.

10. CONTRACTOR QUALIFICATIONS/REQUIREMENTS

10.1. Contractor personnel shall possess demonstrated expert experience in the contractor system, data mining, database development, and data selected item integration of financial and execution information and possess the capability to provide a visual display tool to access information. The Contractor is required to learn the Government’s requirement, seeing and anticipating what changes are on the horizon and proposing courses of action to address these changes. Changes may include identification of a new feeder system and/or feeder system evolvement and phase out. The Contractor must have the ability to understand the data and make the data understandable in not only a broad but also narrow context.

10.2. Contractor shall have knowledge of Department of Defense (DoD) financial systems, accounting processes execution processes and terminology, along with financial management terminology which is required to verify the information on the dashboard is accurate and convey to users the significance and importance of the dashboard outputs.

10.3. The Contractor shall understand DoD standard software interoperability and be able to utilize the existing licensed Microsoft Office software to update and enhance the existing acquisition analytical dashboard infrastructure. Minimum experience is shown in the table below:

Experience Type

Minimum Experience

Government/Military Accounting Ten (10) years of government/military accounting experience.

Government/Military Acquisition Ten (10) years of experience integrating program and financial data to support systems acquisition oversight and reporting with the contractor system.

DoD Budget, Accounting and Finance Data Integration

Ten (10) years of experience integrating DoD budget, accounting and finance data in support of Systems Acquisition oversight and reporting

DoD Systems Acquisition Data Integration Two (2) years of experience integrating Systems Acquisition data with the OSD DAVE/DAMIR systems

Data Analytics and Visualization Two (2) years of experience integrating Qlik Sense Enterprise with DoD GOTS systems and creating data visualizations to support systems acquisition oversight and reporting. Consideration will be given for experience with other Business Intelligence Tools (ie. Tableau, PowerBI). However, the government has invested in Qlik and so vendor must be able to support utilization of that tool.

10.4. Data Rights: All derived data, documents, and materials produced under this contract shall be Government owned and are the property of the Government with all rights and privilege of ownership/copyright belonging exclusively to the Government. All materials/data supplied to the Government shall be the sole property of the Government and may not be used for any other purpose. This right does not abrogate any other Government rights

10.5. The Contractor shall understand and have the ability to apply appropriate principles and technologies to safeguard data in Non-Secure Internet Protocol Router (NIPR) environments.

10.6. Contractor personnel shall possess at a minimum, the relevant certifications and education to support the requirements of the PWS. Relevant experience includes technical analysis, data modeling and management, data integration, dashboard design, creation and display.

11. PERSONNEL

11.1. This is a not a personal services contract. As such, the Government shall not exercise any supervision or control over Contractor personnel in performing services to satisfy the performance objective.

11.2. Contractor personnel performing services shall be U.S. citizens, unless exceptions apply and appropriate security authorization is obtained. In addition, Contractor personnel shall be fluent in the English language as exemplified in their written and verbal skills.

11.3. "Inherently Governmental function," as defined in Section 5 of the Federal Activities

Inventory Reform (FAIR) Act, Public Law 105‐270, means a function that is so intimately related to the public interest as to require performance by Federal Government employees.

11.4. The Contractor shall not perform inherently Government functions which include management of Government programs requiring value judgments, conduct of foreign relations, selection of program priorities, and the direction of intelligence and counter-intelligence operations. Inherently Governmental functions DO NOT include, (i) gathering information for or providing advice, opinions, recommendations, or ideas to Federal Government officials; or (ii) any function that is primarily ministerial and internal in nature.”

11.5. PERSONNEL CONDUCT: The selection, assignment, reassignment, transfer, supervision, management, and control of Contract personnel employed to perform tasks specific herein shall be the responsibility of the Contractor. The Contractor shall be responsible for the performance and conduct of contractor and subcontractor personnel at all times. Personnel employed by the Contractor in the performance of this contract, or any representative of the Contractor entering the installation shall abide by the security regulations listed in the contract and shall be subject to such checks by the Government as deemed necessary. The Contractor shall not employ for performance under this contract any personnel whose employment would result in a conflict of interest with the Government’s standards of conduct.

11.6. PERSONNEL COMPLIANCE: The Contractor shall ensure that Contractor personnel observe and comply with all local and higher authority policies, regulations, and procedures concerning fire, safety, environmental protection, sanitation, security, traffic, parking, energy conservation, flag courtesy, “off limits” areas, and possession of firearms or other lethal weapons. When two (2) or more directives or instructions apply, the Contractor shall comply with the more stringent of the directives or instructions.

11.7. PERSONNEL REMOVAL: Government rules, regulations, laws, directive, and requirements that are issued during the term of the performance period relating to law and order, installation administration, and security shall be applicable to all Contractor personnel and representatives who enter the installation. Violation of such rules, regulations, laws, directives, or requirements shall be grounds for removal (permanently or temporarily as the Government determines) from the work site or installation. Removal of Contractor personnel does not relieve the Contractor from the responsibility for the work defined in this PWS. The Contractor is expected to provide support services despite personnel removal or other unforeseen condition. The Contractor is responsible for training of replacement personnel due to extended leave or termination.

11.8. REMOVAL BY INSTALLATION COMMANDER: The Installation Commander may, at his discretion, bar an individual from the installation under the authority of 18 USC 1382

(1972), for conduct that is determined to be contrary to unfavorable determination, discipline, or installation security and safety.

11.9. REMOVAL BY MILITARY POLICE: Contractor personnel may be denied entry to or may be removed from the installation by Military Police if it is determined that the Contractor personnel’s presence on the installation may be contrary to discipline, or installation security and safety.

11.10. ENTERPRISE-WIDE CONTRACTOR MANPOWER REPORTING APPLICATION (ECMRA)

The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract ASA (ALT) via a secure data collection site. The contractor is required to completely fill in all required data fields using the following web address: http://www.ecmra.mil/, and then click on the “Department of the Army CMRA” or the icon of the DOD organization that is receiving or benefitting from the contract services.

12. SECURITY REQUIREMENTS

12.1. The work performed in this PWS will be performed in both classified and unclassified areas.

Therefore, U.S. citizenship and a SECRET security clearance for facility access will be required. Documentation will be at the UNCLASS/FOUO level and require an NDA.

Clearance shall remain valid for the entire period of performance.

12.2. The Contractor shall provide required information and documentation to the Government to facilitate the issuance of building badges, base passes, or to obtain Common Access Cards (CACs).

12.3. If the contractor is provided with Government Furnished Equipment (GFE), it is expected that personnel will use that equipment for official business. The Contractor shall be responsible for safeguarding all GFE issued as well as all information, and any additional property provided for contractor use. At the close of each workday, equipment and materials, whether in a government facility or while working remote, shall be secured. All GFE will be returned to the government if contractor employees leave the government or civilian organization for more than 30 days. All GFE will be hand-receipted by the government to the contractor.

12.4. The Contractor shall establish and implement methods to ensure that building badges, base passes, and CACs issued to contractor personnel by the Government are not lost or misplaced and are not used by unauthorized persons. No building badges, base passes, and CACs issued to the contractor by the Government shall be duplicated. The Contractor shall develop procedures addressing badge control and document it in the QCP. Such procedures shall include turn-in of any issued badges by personnel who no longer require access to work areas.

12.5. CONTRACTOR UNCLASSIFIED ACCESS TO FEDERALLY CONTROLLED FACILITIES,

SENSITIVE INFORMATION OR IT SYSTEMS

12.5.1. IA/IT Training Certification: All Contractor employees and subcontractor employees supporting IA/IT functions must be certified upon contract award as directed in DoDM 8140.03, Cyberspace Workforce Qualification and Management Program; DFARS 252.239.7001, Information Assurance Contractor Training and Certification; and AR 25-2, Information Management: Army Cybersecurity. Baseline certification as stipulated in DoDM 8140.03 must be completed upon contract award. Pursuant to DFARS 252.239– 7001 Information Assurance Contractor Training and Certification (JAN 2008).

12.5.2. The Contractor shall ensure that personnel accessing information systems have the proper and http://www.ecmra.mil/ current information assurance certification to perform information assurance functions in accordance with DoD In accordance with DoDD 8140.01, Cyberspace Workforce Management, Contractor personnel performing cyberspace duties/work roles must have their qualifications documented. Through their DoD Component contracting officials, apply updated qualification standards, according to Defense Federal Acquisition Regulation Supplement Subpart 239.71, for contractors performing cyberspace work roles.

12.5.3. In accordance with DoDM 8140.03, contractor must be fully qualified by commencement of work.

12.5.4. APPLICABILITY

12.5.4.1. This text applies to contractor employees requiring physical access to any area of a federally controlled base, facility or activity and/or requiring access to a Department of the Army (DA) or DoD computer/network/system to perform certain unclassified sensitive duties. This clause also applies to contractor employees who access Privacy Act and Protected Health Information (PHI), provide support associated with fiduciary duties, or perform duties that have been identified as National Security Position, as advised by the command security manager. It is the responsibility of the responsible security officer of the command/facility where the work is performed to ensure compliance.

12.5.4.2. Each contractor employee providing services at the Army command under this contract is required to obtain a DoD Common Access Card (CAC). Application and proof of completion of required training is necessary for issuance.

Additionally, depending on the level of computer/network access, the contract employee will require a successful investigation as detailed below.

12.5.4.3. The contractor must return CACs at the completion or termination of each individual’s support on a specific contract. Out processing shall be documented, and a completed copy sent to the COR within 5 business days of departure. Disposition of DOD CACs are to be coordinated in writing with the COR prior to departure.

12.5.4.4. All contractors are to follow existing DOD CAC use policies. Current policies can be found at: https://www.cac.mil/policies/

12.5.4.5. Per Title 18, Federally issued identification cards are not to be reproduced in any form.

12.5.5. ACCESS TO FEDERAL FACILITIES

12.5.5.1. Per HSPD-12, Homeland Security Presidential Directive 12 Policy for a

Common Identification Standard for Federal Employees and Contractors, and implementing guidance, all contractor employees working at a federally controlled base, facility or activity under this clause will require a DoD CAC. When access to a base, facility or activity is required contractor employees shall in-process with the Command's Security Manager (CSM) upon arrival to the command and shall out-process prior to their departure at the completion of the individual's performance under the contract.

12.5.5.2. Contractor shall not conduct work in authorized work areas without presence of Federal employee present.

12.5.5.3. The following documents shall be required prior to building access being granted and are required within 10 business days of CAC issuance.

• Access Acknowledgement

• NATO Security Brief

• NDA 312

• Security Awareness Brief

12.5.6. ACCESS TO DOD IT SYSTEM

12.5.6.1. Access to sensitive IT systems is contingent upon a favorably adjudicated background investigation. When access to IT systems is required for performance of the contractor employee's duties, such employees shall in-process with the Army Command's Security Manager (CSM) and IA manager upon arrival to the Army command and shall out-process prior to their departure at the completion of the individual's performance under the contract.

Completion and approval of a System Authorization Access Request (SAAR) form is required for all individuals accessing Army IT resources. The decision to authorize access to a government IT system/network is inherently governmental. The contractor supervisor is not authorized to sign the SAAR;

therefore, the government employee with knowledge of the system/network access required or the COR shall sign the SAAR as the supervisor.

12.5.6.2. When required to maintain access to required IT systems or networks, the contractor shall ensure that all employees requiring access complete the below mandatory training within 30 days of start date and complete recurring training annually thereafter. All training certificates will be presented to the COR.

• Anti-Terrorism (AT) Level I

• OPSEC Awareness

• Information Assurance

• Threat Awareness Reporting (TARP)

• Other mandatory training required by the Army/DoD

12.5.7. INTERIM ACCESS

12.5.7.1. The CSM may authorize issuance of a DoD CAC and interim access to a DA or DoD unclassified computer/network upon a favorable review of the investigative questionnaire and advance favorable fingerprint results. When the results of the investigation are received and a favorable determination is not made, the contractor employee working on the contract under interim access will be denied access to the computer network and this denial will not relieve the contractor of his/her responsibility to perform.

12.5.8. DENIAL OR TERMINATION OF ACCESS

12.5.8.1. The potential consequences of any requirement under this clause including denial or termination of physical or system access in no way relieves the contractor from the requirement to execute performance under the contract within the timeframes specified in the contract. Contractors shall plan ahead in processing their employees and subcontractor employees. The contractor shall insert this clause in all subcontracts when the subcontractor is permitted to have unclassified access to a federally controlled facility, federally controlled information system/network and/or to government information, meaning information not authorized for public release.

13. CONTRACTING OFFICER’S REPRESENTATIVE

13.1. A Contracting Officer’s Representative will be appointed at the time of award to provide technical oversight of this contract.

13.2. The contractor shall designate an employee to serve as the contractor's security representative. Within three workdays after contract award, the contractor shall provide to the requiring activity's Security Manager and the Contracting Officer (CO), in writing, the name, title, address and phone number for the contractor's security representative. The contractor's security representative shall be the primary point of contact on any security matter. The contractor's security representative shall not be replaced or removed without prior notice to the CO and CSM.

14. TRAVEL

Travel may be required in support of this contract. Travel required for tasks assigned under this contract shall be governed in accordance with rules set forth for temporary duty travel within FAR Part 31.205-46 Travel Costs and Joint Travel Regulations (JTR). The contractor shall obtain approval of the cost estimate from the Government COR prior to booking the travel via email and upload this approval to the GSA Assisted Services Shared Information System (ASSIST) Post-Award Collaboration Tool (PAC). The COR will verify funds availability on the applicable CLIN to cover the costs. The contractor will make every effort to make requests a minimum of 2-weeks prior to travel and will provide detailed estimated travel costs as part of the request. All travel must be approved in advance by the COR in writing via ASSIST detailing all anticipated travel costs. The number of trips and personnel traveling will be limited to the minimum required to accomplish work. Travel shall be scheduled during normal duty hours whenever possible.