AIE PWS IDIQ Multiple Award.pdf

CUI

Accessions Information Environment

Performance Work Statement (PWS)

DRAFT

W91CRB-24-X-XXXX

MONTH XX, 2024

Army Contracting Command – Aberdeen Proving Ground (ACC-APG) Attn: Megan A. Lamiotte Contracting Officer 6565 Surveillance Loop (CCAP-CCB), Building 6001 Aberdeen Proving Ground, MD 21005 megan.a.lamiotte.civ@army.mil mailto:megan.a.lamiotte.civ@army.mil

1.0 Introduction

1.1 Description of Services

1.2 AIE Description

1.2.1 Background

1.2.2 AIE Overarching Objectives

1.3 AIE Description

1.4 Scope

1.5 Period of Performance

1.6 Contract Type

1.7 General Information Requirements

1.7.1 Quality Control and Assurance

1.7.2 Recognized Federal Holidays

1.7.3 Hours of Operation

1.7.4 Place of Performance

1.7.5 Security Requirements

1.7.6 Contracting Officer’s Representative (COR)

1.7.7 Agile Qualifications

1.7.8 Key Personnel

1.7.9 Contractor Key Personnel Replacement

1.7.10 Identification of Contractor Employees

1.7.11 Contractor Travel

1.7.12 Other Direct Costs (ODCs)

1.7.13 Organizational Conflict of Interest (OCI)

1.7.14 Government Rights

2.0 Government Furnished Property (GFP), Items, and Services

2.1 Hardware, Software, and Technology Services and Materials

2.2 Government Property (GP)

3.0 Government Furnished Information (GFI)

3.1 Contractor Acquired Property (CAP)

3.2 Government Facilities

3.3 Government Facilities Access

3.4 Contractors Requiring Common Access Card (CAC)

3.5 Contractors Not Requiring CAC

3.6 Associate Contractor Agreements (ACA)

4.0 Overarching Performance Requirements – Task Areas

4.1 TA 1: Agile Program Management

4.2 TA 2: Salesforce Solution Design, Configuration, Development, and Test

4.3 TA 3: DevSecOps

4.4 TA 4: Architecture

4.5 TA 5: Training Material Development

4.6 TA 6: Production Operations Transition

5.0 Deliverables

5.1 Deliverable Procedures

5.2 Data and Data Rights

5.3 Deliverables List

6.0 Reference Materials

6.1 List of References

Table. 1 Sample Deliverables List Table. 2 PWS References

1.0 Introduction

The Program Executive Office Enterprise Information Systems (PEO EIS) Accession Information Environment (AIE) product office has a requirement for continual development, configuration, and operation of its Salesforce-based platform. AIE is a defense business system under DoDI 5000.87 Software Pathway, used by recruiters to enlist Soldiers in the Army.

This is a multiple-award indefinite delivery, indefinite quantity (IDIQ) contract utilizing a Capacity Team-Based Contracting (CTBC) agile acquisition approach. Task Orders will be issued to obtain Contractor services based on AIE requirements and capability needs.

The AIE solution is based on a Salesforce customer relationship management (CRM) Software as a Service (SaaS) platform hosted in a Government Cloud Plus environment and has continued to evolve. AIE development work will consist of (1) Agile execution combined with Development, Security, and Operations (DevSecOps) for all activities / tasks. This will allow for Continuous Integration / Continuous Delivery (CI/CD) and compliance with the Continuous Risk Management Framework (cRMF), (2) task automation to reduce/eliminate manual effort, and (3) innovation and creativity in problem-solving.

For this effort, Agile execution is defined as a group of software methods (e.g., Scrum, Kanban, SAFe®) based on iterative and incremental configuration and deployment of software capabilities for end users, where requirements and solutions evolve through collaboration between cross-functional teams. These teams include the Government and Contractor communities working across parallel environments where capabilities are implemented as part of continual operations (previously known as capability support).

Contractors will apply and perform Agile execution in varying degrees to all aspects of the program life cycle across and within key activities. This includes applying Agile to perform the following activities: requirements analysis to map existing Salesforce capabilities to user needs, elicitation, elaboration, and decomposition; architecture to minimize customization and continually improve data management; design;

development, implementation; test; integration; training material development;

deployment, and cybersecurity.

The Government will not exercise any supervision or control over the service providers performing the services herein. Such service providers shall be accountable solely to the Contractor who, in turn, is responsible to the Government.

1.1 Description of Services

The Contractor will provide all personnel, supervision, and other items necessary (except for those specified as Government Furnished in Section 3 of this document) to perform AIE services, as defined at high-level in this PWS. Specific work scope will be provided in future Task Order(s).

Agile and DevSecOps methodologies will apply for incremental and value-added delivery from requirements analysis / elaboration and business process reengineering

(BPR), through architecture, design, configuration, development, testing and implementation, to deploy to production with minimum cybersecurity vulnerabilities.

The Contractor will synchronize tasks and associated activities with other technical contracting teams already in place that established the AIE Salesforce platform, architecture, and CI/CD pipeline.

AIE resides on Salesforce Government Cloud Plus leveraging Salesforce’s Public Sector Solutions (PSS). The full list of AIE tools and applications are included in Reference 1 (AIE Components.xls). The Government will give the Contractor access to the AIE applications and tools at the level necessary to perform the required work including the established DevSecOps pipeline tools.

AIE has established a DevSecOps pipeline. The Contractor is required to utilize this existing DevSecOps pipeline to align with the AIE environments and processes in place, to include security policies within the AIE production baseline.

The Government will provide the Integration environment and associated tools to support the integration and test for AIE. The DevSecOps team will administer and maintain the Integration environment; ensure the currency of the AIE baseline, tools, and test data in that environment based on an agreed upon cadence; and will support the Contractor activities in that environment, such as incremental testing and cybersecurity scans. The Contractor, based on their task order requirement, will support the AIE DevSecOps team for baseline activities in that environment to ensure readiness of the AIE functionality for release.

PEO EIS uses the Scaled Agile Framework (SAFe®) for program office operations. The Contractor will integrate efforts (e.g., activities and tools) with the Government for Agile Release Train (ART) workflow to support agile planning and continuous product delivery. The Contractor will apply an agile development framework within their Agile Teams and will synchronize their effort with the Government ART workflow. The Contractor’s agile framework will define interactions between key roles such as Business Owners, Solution Architects, Release Train Engineers, Product Owners, Scrum Masters, and Team Coaches. These interaction definitions will clearly delineate roles and responsibilities to ensure continuous alignment of program roadmaps and transparency in execution activities and reporting.

For this PWS, where addressed as part of capability development and delivery, “release” is defined as moving capability to integration environment followed by the production environment. “Deploy” is defined as users having access to the new capability in the production environment.

1.2 AIE Description

1.2.1 Background

The U.S. Army Training and Doctrine Command (TRADOC), the senior responsible official (SRO) for Army Accessions, and senior Army Leadership require a modern solution to simplify and streamline the recruiting process for the entire Army Accessions Enterprise, including U.S. Army Recruiting Command (USAREC); U.S. Army Cadet Command (USACC); U.S. Army National Guard (ARNG); and the U.S. Army Center for Initial Military Training (C-IMT). The AIE will answer TRADOC’s modernization solution as a fully integrated enterprise system implementing new business practices and modernizing recruiting capabilities that meet all Army manning requirements. For the first time, this AIE will enable the Army to leverage a minimally configured Commercial Off-The-Shelf (COTS) solution hosted in a commercial Salesforce and Amazon Web Service (AWS) Cloud Impact Level 4 (IL4) environment for talent acquisition Army-wide.

In concert with systems modernization across the accessions enterprise, AIE will originate the Army record for management in systems downstream.

The AIE supports Army objectives to improve readiness; improve Return on Investment (ROI); reduce Total Cost of Ownership; use compliant, effective, and efficient processes;

provide timely, secure, protected, accurate, and available data; and improve user experience.

AIE will introduce form-less recruiting through a natural interview process supported by an applicant portal for communication with the ability to upload/complete application information. Validation rules span the solution to ensure accurate data entry. Recruiters gain Artificial Intelligence (AI) enabled intelligence, web-based and mobile application tools; internal system messaging for alerts and notifications; and the ability to track all touch points for each applicant across components and mission sets for ROI analysis.

The AIE supports tactical planning and decision making by recruiters and Recruiting Operations Officers (ROOs), and Planning, Programming, Budgeting, and Execution (PPBE) and strategic decisions at the Headquarters Department of the Army (HQDA).

Users at all levels gain dashboards and reports enabling data-driven decision-making.

Across the Accessions Enterprise, each level of command gains a Common Operating Picture (COP) to view timely, credible, and relevant data.

The AIE provides integrated training management for Future Soldier and Cadets, integrated social media, and marketing campaigns from recruiter to the national level, and an integrated content library for recruiting and Army marketing materials.

AIE will utilize Agile software development and human-centered design processes throughout the CI/CD DevSecOps pipeline to deliver iterative incremental minimum viable products (MVPs) with basic capabilities for users to provide feedback for future improvements to user stories and features. The Minimum Viable Capability Release (MVCR) will provide the set of recruiting features suitable for the operational production environment that will enhance recruiting mission outcomes with the first being the Enlisted Mission.

The AIE will support global operations with over 25,000 core users operating around the clock seven days a week. Mobility, reliability, secure connectivity, and data access are paramount AIE attributes. The following enterprise workforce must be able to perform tasks using any device, anytime, anywhere, while maintaining secure connectivity with the AIE system. Core users of the system include:

• USAREC;

• ARNG recruiting personnel;

• USACC;

• Accessions Support Personnel National Guard Bureau (NGB);

• CIMT;

• TRADOC staff; and

• HQDA analysts.

The AIE will leverage the similarity of missions across all accessions enterprise commands and provide a net capability supporting four (4) core capabilities: Lead Management; Prospecting; Interviewing; and Processing; and four (4) supporting capabilities: Intelligence; Training / Leader Development; Marketing; and Pay Incentives. AIE will use common architectures and standards while providing a fully integrated enterprise level capability enabling transparency, efficiency, and effectiveness of the accessions workforce and acquire the best-qualified talent to meet all Army manning requirements.

AIE conducted multiple Business Process Reengineering (BPR) assessments and a full BPR assessment in 2023 with satisfactory results. Since then, AIE consistently achieves both current and future integrated architecture requirements documented in the Army Enterprise Knowledge Repository (EKR) and is continually assessed in the Human Resource Management (HRM) domain architecture by Technology and Business Architecture Integration (TBAI). The J6 architecture interoperability certification and subsequent Joint Interoperability Test Command (JITC) testing will further evaluate AIE architecture at the application domain level.

Refer to the AIE Requirements Traceability Matrix (RTM) (Reference 2), and Capability Overview (Reference 3) for a complete list of AIE requirements to be met.

1.2.2 AIE Overarching Objectives

Overall AIE program objectives include:

a. Provide incremental releases based on Agile execution and DevSecOps using automated CI/CD pipelines, aligned with the AIE production baseline architecture and processes

b. Use Agile development methods, where functional and technical development team members and the Army collaborate daily

c. Provide preventive and corrective cybersecurity and information assurance to not only meet cRMF compliance requirements but to provide robust and innovative defense of soldier data

d. Subsume applicable legacy systems and eliminate interfaces

e. Reduce point-to-point interfaces

f. Simplify application integration and open application data to enable collaboration and innovation via techniques such as Application Programming Interfaces (APIs)

g. Use modern data architecture best practices to improve accessibility, increase high data velocity, increase data throughput for low latency and reduce reliance on any single technology or vendor

h. Allow for future Machine Language and Artificial Intelligence utilization

i. Comply with the seven data-centric Department of Defense (DoD) Data Strategy VAULTIS goals, i.e., making data (1) Visible, (2) Accessible, (3) Understandable,

(4) Linked, (5) Trustworthy, (6) Interoperable, and (7) Secure

j. Apply Human Centered Design techniques to improve the user experience

k. Improve Return on Investment and lower total cost of ownership

The objective of this contract is to continue to configure and mature AIE solution using the Salesforce application.

1.3 AIE Description

At a high-level AIE requirements can be grouped into the following six categories:

Foundation, CRM, Processing, On-Boarding, Intelligence, Marketing, Training and Leader Development, and Sustain and Support. See the AIE RTM (Reference 2) for requirements decomposition.

1.4 Scope

The Army requires the following services in the following Task Areas (TAs) to deliver an AIE solution. Task Orders may include as few as one (1) TA or as many as all. TAs are further described at PWS Section 5.0.

TA 1: Agile Program Management;

TA 2: Salesforce Solution Design, Configuration, Development, and Test;

TA 3: DevSecOps;

TA 4: Architecture;

TA 5: Training Material Development; and TA 6: Production Operations Transition.

1.5 Period of Performance

The period of performance for this multiple-award IDIQ is ten (10) years, consisting of a five (5) year Base Period from date of award and five (5) one year Option Periods(s).

Task orders will define the performance scope and base period start and end.

1.6 Contract Type

The task orders will be Hybrid including Firm Fixed Price (FFP), Cost Plus Fixed Fee (CPFF) Term, CPFF Completion, and Cost Reimbursable (no fee) line items for Travel and Other Direct Costs (ODCs).

1.7 General Information Requirements

1.7.1 Quality Control and Assurance

The Contractor will maintain an effective quality control program to ensure services are performed as agreed to in the contract task order. This will include the following:

a. Updating and implementing procedures to identify, prevent, and ensure the non-recurrence of defective services, to include products and software

b. Using programmatic and technical metrics as quality measures to assess performance, progress, speed, cybersecurity, and quality of the product team, leveraging automated tools to the maximum extent practicable

The Government will evaluate the Contractor’s performance in accordance with the AIE Quality Assurance Surveillance Plan (QASP) (see Attachment 1). The QASP describes the performance levels the Contractor must achieve to satisfy the contract performance requirements. The Contractor shall meet the threshold requirements outlined in the QASP Performance Requirements Summary (PRS) to receive a Satisfactory rating in the monthly Contracting Officer’s Representative (COR) report and annual Contractor Performance Assessment Report (CPAR). The Contractor shall report performance against the measures / metrics outlined in the QASP during program reviews per the cadence established between the Government and Contractor. The report must show the current and previous two months. If the Contractor fails to meet any QASP measure/metric, the Government will notify the Contractor through the Contracting Officer and will require a response within five (5) business days of receipt of the official notice by the Contracting Officer describing their corrective action plan to meet the QASP measure/metric.

The Government will perform random After-Action Reviews (AARs) as needed in Sprint Review or at other delivery points. This surveillance method is appropriate for a deliverable or performed service which will capture best practices, bottlenecks, and future PI/sprint development processes for implementation.

1.7.2 Recognized Federal Holidays

• New Year’s Day

• Martin Luther King Jr.’s Birthday

• Presidents Day

• Memorial Day

• Juneteenth National Independence Day

• Independence Day

• Labor Day

• Columbus Day

• Veteran’s Day

• Thanksgiving Day

• Christmas Day

1.7.3 Hours of Operation

The Contractor shall be responsible for conducting normal operations between the hours of 8am to 5pm Monday thru Friday, core hours being 9am to 3pm Monday through Friday except for Federal Holidays, Government closure due to local or national emergencies, administrative closings, or similar Government directed facility closings.

Contractor personnel identified as key personnel and/or leads shall be available between the hours of 8am to 5pm Monday thru Friday.

1.7.4 Place of Performance

The primary place of performance for unclassified activities will be at Contractor-designated and reported locations. All activities requiring Government participation (e.g., planning, demonstrations, reviews) will take place at the AIE facility, currently located at 9350 Hall Road. Fort Belvoir, VA 22060, unless otherwise determined based on the specific activity. For activities conducted at the AIE facility, the Government will provide hotel-type space for Contractor use. The Contractor facility may also be used for key events. Key events will be coordinated in advance to include associated logistics.

Travel between the Contractor facilities and Government facilities will not be reimbursed as a travel expense.

Temporary duty (TDY) travel to other designated locations will be required to attend meetings, demonstrations, and data centers.

The number of TDY trips is unknown. The Contractor will not be reimbursed for travel to and from their normal place of business within the Continental United States (CONUS) (Convenience Travel). For performance of this contract, outside the local area is defined as greater than 50 miles from the AIE facility. Travel will be reimbursed as actual costs incurred in accordance with Joint Travel Regulations (JTR). All necessary travel shall be approved in advance by the COR.

Contractor personnel will be subject to all travel regulations in effect at the time of the anticipated travel. Contractors are not authorized city pair (i.e., Government discount) air fares.

1.7.5 Security Requirements

The DD254 is provided as Attachment 3. The security classification guidance for classified information requirements is in accordance with the attached DD254.

The Contractor will possess and maintain a Facility Clearance Level of SECRET from the Defense Counterintelligence Security Agency (DCSA).

Contractor personnel performing work under this contract will have a valid active SECRET security level clearance.

The Contractor will ensure the protection of Classified Information, Controlled Unclassified Information (CUI), Personal Identifiable Information (PII) or Privacy Act Data, Controlled Technical Information (CTI) [as required], and Critical Program Information (CPI) [as required].

The Contractor will ensure the aforementioned information is properly safeguarded in accordance with the applicable requirements to protect adequately against unauthorized disclosure.

The Contractor will review DoD, DA, and PEO EIS specific instructions, security policies, procedures, training, and other requirements stipulated in the National Industrial Security Program (NISP) and National Industrial Security Program Operating Manual (NISPOM), and any supplements thereto are applicable, to include, the Federal

Acquisition Regulation (FAR), Defense Federal Acquisition Regulation Supplement (DFARS), data usage agreements and memoranda of agreement, and security provisions and/or clauses.

1.7.5.1 Authorities and Scope

This paragraph addresses Contractor access to, or possession of, collateral (non-SCI) classified information, CUI, PII, CTI or CPI in connection with the performance of this contract. However, it is also applicable to safeguarding the same information in connection with all aspects of pre-award activity, including preparation of bids and proposals and pre-award negotiations, and all aspects of post-award activity. Moreover, the requirements are equally applicable to the safeguarding of the same information not released or disclosed under a procurement contract, agreements or programs participated in by a firm, organization, or individual on a voluntary or grant basis.

For the purposes of this contract, unless otherwise specified, the term “access” will be used to denote any of the aforementioned categories of information released to industry. Additionally, the term Requiring Activity (RA) applies to any element requiring Contractor access.

All functional Security, Force Protection, Antiterrorism, Operations Security (OPSEC), Cybersecurity and Counterintelligence requirements, policies, and procedures identified in this PWS are applicable to all of DoD and Army (military, civilian and Contractor) personnel performing services on this contract. This includes AIE, other integrated ERP program efforts that support the implementation of the AIE solution or where the Army and / or PEO EIS, as the Cognizant Security Office (CSO), is required to implement security procedures, program protection planning, additional required training identified through updated policy, or exercise security and/or protection duties. This also includes all Executive Orders, policies, laws, statutes, as promulgated in DoD and Department of Army (DA) Directives, Regulations, Instructions and Manuals as provided in the following references.

1.7.5.2 Security Requirements for Overseas Travel

For travel requirements/restrictions to any foreign country, see the Foreign Clearance Guide (FCG) at the following website for applicable information:

https://www.fcg.pentagon.mil/fcg.cfm

1.7.5.3 Physical Security

The Contractor will be responsible for safeguarding 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.

1.7.5.4 Disclosure of Information

The Contractor will not release to anyone outside the Contractor's organization any classified information, regardless of medium (e.g., film, tape, document, etc.), pertaining to any part of this contract or any program related to this contract, unless: (1) The COR has given prior written approval by the cognizant classified information owner and (2) the cognizant classified information owner has approved its release as part of contract performance.

http://www.fcg.pentagon.mil/fcg.cfm

Classified information will not be authorized for release regardless of medium (e.g., film, tape, document), for any part of this contract or any program related to this contract. All unclassified information or CUI regardless of medium (e.g., film, tape, document), pertaining to any part of this contract or any program related to this contract, shall be reviewed and approved for release through standard Army processes before it is provided to the public, including via posting to publicly accessible websites.

Request for approval will identify the specific information to be released, the medium to be used, and the purpose for the release. The Contractor will submit its request to the COR at least forty-five (45) days before the proposed date for the release. The Contractor shall include a similar requirement in each subcontract under this contract.

SubContractors will submit requests for authorization to release through the prime Contractor to the COR. The Contractor's procedures for protecting against unauthorized disclosure of information shall not require DoD employees or Armed Forces (AF) members to relinquish control of their work product, whether classified or not, to the Contractor.

1.7.5.5 Visiting Facilities

Pursuant to Section 808 of Public Law (P.L.) 102-190 (DFARS 204.402), DoD employees or members of the Armed Forces (AF) who are assigned to or visiting a Contractor facility and are engaged in oversight of an acquisition program will retain control of their work product. Classified work products of DoD employees or members of the AF will be handled in accordance with DoD 5220.22-M. Contractor procedures for protecting against unauthorized disclosure of information will not require DoD employees or members of the AF to relinquish control of their work products, whether classified or not, to a Contractor. If a visit to a Contractor facility will require access to classified information, the visitors must give the Contractor advance written notice.

1.7.5.6 Key Control

The Contractor will 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 will be duplicated. The Contractor will develop procedures covering key control that will be included in the Quality Control Plan (QCP) at a task order level. QCP is not required at the IDIQ level. Such procedures will include turn-in of any issued keys by personnel who no longer require access to locked areas. The Contractor will immediately report any occurrences of lost or duplicate keys/key cards to the COR.

a. In the event keys, other than master keys, are lost or duplicated, the Contractor will, upon the direction of the COR, re-key or replace the affected lock or locks;

however, the Government, at 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 will be deducted by the Government from the monthly payment due the Contractor. In the event a master key is lost or duplicated, all locks and keys for that system will be replaced by the Government and the total cost will be deducted by the Government from the monthly payment due the Contractor.

b. The Contractor will prohibit Government issued keys by any persons other than the Contractor’s employees. The Contractor will prohibit the opening of locked areas by Contractor employees to permit entrance of persons other than Contractor employees engaged in the performance of assigned work in those areas, or personnel authorized entrance by the COR.

1.7.5.7 Lock Combinations

The Contractor will establish and implement methods of ensuring that all lock combinations are not revealed to unauthorized persons. These procedures shall be included in the Contractor’s QCP.

1.7.5.8 Security Education Training and Awareness (SETA)

All DA SETA requirements identified in this PWS are applicable to all of DoD and Army (military, civilian and Contractor) personnel performing services on the AIE contract in accordance with DoDM 5220.22, DoDM 5200.01 Volume 1-3, DoDI 5200.48, Army Regulation (AR) 350-1, AR 380-12, AR 25-2, and DA Pamphlet (PAM) 25-2-6.

1.7.5.9 Special Qualifications

Contractor personnel performing work under this contract will have the appropriate personnel security investigation (PSI) completed and favorably adjudicated by the DoD CAF; and granted eligibility for access to classified information.

The Contractor will be responsible for ensuring that employees providing cybersecurity services possess and maintain current Information Assurance Technician (IAT) Level I (COMPTIA A+ CE) or II (COMPTIA Security + CE) professional certification per Army and DoD regulation at the time of contract award, and during the execution of the contract.

The Contractor will ensure the following:

a. All employees complete Cybersecurity Awareness training annually, as outlined by the DA PAM 25-2-6, “Cybersecurity Training and Certification Program”, April 8, 2019. Employees will also complete additional relevant security trainings, i.e., Privacy Information Handling, as required by the Government.

b. All DA Contractor personnel who have access to Federally controlled information systems are assigned to an Automated Data Processing (ADP) Position Category which is designated at one of three ADP levels, positions which are designated at one of three information technology (IT) levels, each requiring a certain level of investigation and clearance, as follows (see A Release 3 80-5, Appendix K for position descriptions):

1) ADP-I for an IT position requiring a Single Scope Background Investigation (SSBI) or SSBI equivalent;

2) ADP-II for an IT position requiring a National Agency Check with Law and Credit (NACLC equivalent); and

3) ADP-III for an IT position requiring a National Agency Check with Inquiries (NACI) or equivalent.

4) Previously completed security investigations may be accepted by the Government in lieu of new investigations if determined by the PEO EIS security office to be essentially equivalent in scope to the PWS requirements. The length of time elapsed since the previous investigation will also be considered in determining whether a new investigation is warranted. To assist the Government in making this determination, the Contractor must provide the following information to the respective PEO EIS security office. This information must be provided for each Contractor employee who will perform work on a PEO EIS system and will require access to Federally controlled information systems:

Full name, with middle name, as applicable, with social security number Citizenship status with date and place of birth Proof of the individual’s favorable adjudicated background investigation or NACI, consisting of identification of the type of investigation performed, date of the favorable adjudication, and name of the agency the performed the investigation

Company name, address, phone, and fax numbers with email address

Location of on-site workstation or phone number if off-site; and Order or contract number and expiration date; and name of the

Contracting Officer. The Contracting Officer will ensure that the Contractor is notified as soon as a determination is made by the assigned or cognizant PEO EIS security office regarding acceptance of the previous investigation and clearance level.

5) If a new investigation is deemed necessary, the Contractor and Contracting Officer will be notified by the respective PEO EIS security office after appropriate checks in the DoD databases have been made.

6) If the Contractor employee requires access to classified information and currently does not have the appropriate clearance level and/or an active security clearance, the PEO EIS security office will relay this information to the Contractor and Contracting Officer for further action.

7) The Contracting Officer will ensure that the respective PEO EIS security office initiates the investigation for the required clearance level(s) of the Contractor personnel.

8) It is the Contractor’s responsibility to ensure that adequate information is provided, and that each Contractor employee completes the appropriate paperwork, as required either by the Contracting Officer and the PEO EIS security office, to begin the investigation process for the required clearance level.

1.7.6 Contracting Officer’s Representative (COR)

The COR will be identified by separate letter. The COR monitors all technical aspects of the contract and assists in administration. The COR is authorized to perform the following functions: assure that the Contractor performs the technical requirements of the contract; perform inspections necessary in connection with performance; maintain written and oral communications with the Contractor concerning technical aspects of the contract; issue written interpretations of technical requirements, including Government drawings, designs, specifications; monitor Contractor's performance and notify both the Contracting Officer and Contractor of any deficiencies; coordinate availability of Government furnished property; and provide site entry of Contractor personnel. A letter of designation issued to the COR, a copy of which is sent to the Contractor, states the responsibilities and limitations of the COR, especially regarding changes in cost or price, and estimates or changes in delivery dates. The COR is not authorized to change any of the terms and conditions of the resulting contract.

1.7.7 Agile Qualifications

The Contractor shall ensure personnel performing work under task orders within this multiple-award IDIQ contract have the necessary Agile certifications and/or experience to perform their assigned role to deliver functionality in compliance with the Contractor’s agile methodology, leveraging best practices of Agile software development.

1.7.8 Key Personnel

Task Orders under this multiple-award IDIQ may identify key personnel. Those key personnel are people considered essential to successful Contractor performance.

Where applicable, Task Orders will define Key Personnel qualifications. All key personnel must be on board at task order award. The Contractor will not replace any personnel designated as key personnel without providing written notice to the Contracting Officer and COR at least 48 hours upon Contractor receipt of a voluntary notice or Contractor decision to replace personnel. The notice will provide a detailed explanation of the circumstances necessitating the substitution. Qualifications of substitute key personnel shall be equal to, or greater than, those of the person(s) being replaced.

1.7.9 Contractor Key Personnel Replacement

Any key personnel vacancies by involuntary separation (e.g., termination) will be replaced within ten (10) business days, subject to Government acceptance. Any vacancies in the personnel through voluntary separation (e.g., voluntary separation from the company) shall be replaced within fifteen (15) business days, subject to Government acceptance. The Government reserves the right to review and accept or reject all key personnel resumes. The Government will provide input on all resumes within five (5) business days after receipt. Government process time should not inhibit the Contractor from meeting the timelines expressed above.

1.7.10 Identification of Contractor Employees

All Contractor personnel attending meetings, answering Government telephones, and working in other situations where their Contractor status is not apparent 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. They must also ensure that all documents or reports produced by Contractors are suitably marked as Contractor products or that Contractor participation is appropriately disclosed. Contractor personnel will be required to obtain and wear badges in the performance of this service.

1.7.11 Contractor Travel

Contractor personnel will be required to travel CONUS and may be required to travel Outside the Continental United States (OCONUS), and within the National Capitol Region during the performance of the contract to attend meetings, conferences, and training, including areas of operations in United States Central Command (CENTCOM), United States Indo-Pacific Command (PACOM), and United States European Command (EUCOM). All Contractor travel is subject to the limitations of FAR 31.205- 46, Travel Costs. The Contractor may be required to travel to off-site training locations and to ship training aids to these locations in support of the contract. Contractor personnel will be authorized travel expenses consistent with the substantive provisions of the JTR and the limitation of funds specified in the contract; and could include locations deemed hostile. All travel requires Government approval / authorization and notification to the COR.

1.7.12 Other Direct Costs (ODCs)

The Contractor shall acquire necessary ODC items associated with the services of the contract with written, advances, approval of the COR.

1.7.13 Organizational Conflict of Interest (OCI)

Contractor and subContractor personnel performing work under the 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 will 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 subsequent contracted requirements which may be affected by the OCI.

1.7.14 Government Rights

1.7.14.1 Intellectual Property Rights

The Government’s rights in non-commercial technical data and software deliverables shall be governed by DFARS 252.227-7013 and DFARS 252.227-7014, respectively.

The Government's rights in commercial technical data deliverables shall be governed by DFARS 252.227-7015. All non-commercial technical data and software deliverables shall be properly marked in accordance with the marking requirements set forth in DFARS 252.227-7013(f) and DFARS 252.227-7014(f), respectively. Technical data and software deliverables with non-conforming restrictive markings shall be rejected and corrected by the Contractor at the Contractor's expense, in accordance with DFARS 252.227-7013(h)(2) and DFARS 252.227-7014(h)(2), respectively.

1.7.14.2 Commercial Software Licenses

The Government's rights in commercial software are governed by the licensor's commercial software license agreements. However, the Government will not agree to commercial software license terms that are inconsistent with Federal procurement law or do not otherwise satisfy user needs, in accordance with DFARS 227.7202-1(a).

1.7.14.3 Data / Software Rights Assertions

Pursuant to the requirements set forth in DFARS 252.227-7017, Contractors are required to specifically identify Data/Software Rights Assertions related to technical data and software deliverables. These assertions shall comply with the following requirements:

a. The Contractor shall not assert license restrictions on items, component, or processes themselves. The asserted license restrictions shall pertain to software or technical data that relates to items, components, or processes.

b. The Contractor's Assertions shall not include technical data or software that will not be furnished to the Government under this Contract.

c. The Contractor shall provide a concise (but specific) description of the technical data and software deliverables that will be furnished to the Government with restrictions, rather than generically asserting license restrictions in "technical data" or "technology".

d. The Contractor is responsible for ensuring that Data and Software Rights Assertions from its subcontractors comply with the aforementioned content and formatting requirements (in accordance with DFARS 252.227-7017).

1.7.14.4 Contractor Manpower Reporting

The Contractor shall report ALL Contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the Army via a secure data collection site. The Contractor is required to completely fill in all required data fields through the following web address: www.sam.gov. Reporting inputs will be for the labor executed during the period of performance during each Government FY, which runs from October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year. Contractors may direct questions to the help desk by clicking “View Assistance for SAM.gov” which is located at the top of the SAM.gov website. From there, you can the select “Contact Our Service Desk” which will allow you to contact SAM.gov directly. If contract period of performance ends prior to September 30, the Contractor has twenty (20) days from end date of the contract to complete the SAM SCR requirement.

http://www.sam.gov/

2.0 Government Furnished Property (GFP), Items, and Services

The Government will provide any Contractor personnel designated to perform work under the Contract in Government facilities when required with the following incidental Property equipment: workspaces / work areas, desks, chairs, telephones, document file cabinets, and access to printers, facsimile machines, copy machines and conference rooms. Any requirement for work performed in a Government facility will be specified in the Task Order.

The Government will provide computer equipment (primarily laptops) with Local Area Network / Wide Area Network (LAN/WAN) interface, NIPRNet and SIPRNet (.mil) access. The computer equipment will be pre-loaded with the Government-standard desktop image that includes Microsoft Office365 applications, file shares, security tools, and print services.

The Contractor's property control records shall provide the following basic information for every item of Government property in the Contractor's possession, regardless of value:

a. The name, description, and National Stock Number (if furnished by the Government or available in the property control system)

b. Quantity received, issued, and on hand

c. Unit price (and unit of measure)

d. Contract number or equivalent code designation

e. Location

f. Disposition

g. Posting reference and date of transaction

h. Upon completion of the contract, the Contractor shall return all non-expendable

Government-issued items to the COR.

2.1 Hardware, Software, and Technology Services and Materials The Contractor will use the hardware, software, and IT Services (infrastructure) provided by Government to support the services required in this PWS. This includes networks provided by the United States Army, Army Reserve, and Army National Guard. Specific materials (products and tools) are identified in Reference 001 (Reference 001 – AIE Software Baseline Applications and Tools.xlsx).

As previously stated, the Contractor is not restricted to the use of the Government-provided software applications and tools, and, with justification and Government approval, may implement additional applications and tools, ensuring alignment with the AIE baseline.

The authoritative data source for Force Structure is the Army Organization Server (AOS). However, this source is expected to be replaced by the Global Force Information Management (GFIM).

2.2 Government Property (GP)

GP which includes Government Furnished Material (GFM), and Government Furnished Equipment (GFE) may be provided as defined in each individual TO.

The Government will provide all necessary equipment to perform support services as required by individual TOs. All equipment received as Government Property (GP) shall be accounted for IAW FAR 52.245-1 and by Government approved Contractor internal property controls. GP controls will be established and maintained to manage all property provided as GP, purchased, or otherwise acquired for use in supporting the mission of

PEO EIS.

The Property Management Plan provided at solicitation in accordance with FAR 45.201(c)(4) shall be a description of the property management system to be used in managing Government property. No later than 60 days after contract award, the Contractor shall submit the Property Management System procedures in accordance with FAR 52.245-1(f). Include Contracting Officer and Government Property Administrator in the submission. Changes thereafter to the Property Management System must be approved by the Property Administrator prior to implementation.

Both the requiring activity and Contractor shall utilize GFP Property Transfer to document shipment and receipt of GFP per DoDI 4161.02 and DFARS 252.211-7007.

Government property will be inventoried at least every 3 years at a minimum and classified or sensitive property must be inventoried at least annually.

The Contractor shall submit a Government Property Inventory report IAW A009 of the CDRL list. This report shall be initially submitted six (6) months post-award of the first task order and every six (6) months thereafter.

The Contractor shall use the property for performing work in support of only this MAC.

Modifications or alterations of property are prohibited. The Contractor shall not cannibalize property. In the event property is received by the Contractor in a condition not suitable for its intended use, the Contractor shall immediately notify the COR. The Contractor shall have a process to enable the prompt recognition, investigation, disclosure, and reporting of loss of incidental property (meaning unintended, unforeseen, or accidental loss, damage, or destruction of Government property that reduces the Government’s expected economic benefits of the property). Contractor shall include the control of incidental property in their Quality Control Plan.

All GFP provided will be returned to the customer unless notification in writing is provided by the customer to submit specific items in Plant Clearance function of the GFP Module in Procurement Integrated Enterprise Environment (PIEE). The Contractor is required to utilize CAP (Contractor-acquired property) Pre-Screening of the GFP Module in PIEE for any Contractor inventory (as defined in FAR 52.245-1) during the performance of the contract and for contract closeout. Any remaining Government property not reutilized, transferred, or otherwise disposed of at contract closeout, shall be submitted in the Plant Clearance function of the GFP Module in PIEE. If applicable, Contractor is responsible for demilitarization. If applicable, Contractor is responsible for transportation or shipping to Defense Logistics Agency Disposition Services (DLA DS).

The Contractor shall investigate and report loss of GP IAW DFARS 252.245-7002.

Contractor shall also report to the Government COR all incidents of property loss within 72 hours. This process shall include the corrective actions necessary to prevent recurrence.

3.0 Government Furnished Information (GFI)

Technical data or computer software provided to the Contractor as GFI under this contract shall be subject to restrictions on use, modification, reproduction, release, performance, display, or further disclosure. GFI data or software will be accessed and used for the purpose stated in this contract and shall not be used to compete for any Government or non-Government contract. The Contractor shall take all reasonable steps to protect the technical data or software against any unauthorized release or disclosure. The Contractor shall be required to sign a Non-Disclosure Agreement (NDA), which will restrict the Contractor use of GFI data or software provided under this contract.

3.1 Contractor Acquired Property (CAP)

Each TO will specify the CAP that the Contractor shall acquire as described in FAR 52.245-1. Any equipment, tools, materials, facilities, or software required to conduct required services that are not made available by the Government may be purchased by the Contractor with authorization from the COR prior to any purchase. Any tools or material purchased must be incidental to the service and must be acquired using Government rates when available and applicable.

Only material necessary to the service of this contract shall be acquired. There shall be no production or limited production buys under this contract. All necessary material meeting the above criteria shall be reviewed and approved in advance by the COR.

The Contractor shall obtain prior written authorization and approval from the KO or designee as applicable for any Contractor-acquired property purchased to support the performance of any detailed requirement under this contract.

3.2 Government Facilities

Government office or laboratory space may be made available for performance of specific orders. The Contractor may be required to establish operations and support facilities and warehouses within a Government provided facility that complies with DOD and/or Department of State certification and accreditation requirements. Such facilities will be specified in the individual orders.

3.3 Government Facilities Access

Contractor and all associated Subcontractor employees shall provide all information required for background checks to…