AIE PWS - DRAFT.pdf

Distribution Statement A: Approved for Public Release

Accessions Information Environment

Performance Work Statement (PWS)

DRAFT

W91CRB-24-X-XXXX

December 7, 2023

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

AIE PWS – DRAFT Distribution Statement A: Approved for Public Release December 7, 2023 ii

THIS PAGE INTENTIONALLY LEFT BLANK

December 7, 2023 iii

Table of Contents Introduction

1.1 Description of Services

1.2 AIE Description

1.2.1 Background

1.4 Scope .......................................................................... Error! Bookmark not defined.

1.5 Period of Performance

1.6 Contract Type

1.7 Contract Structure

1.8 General Information Requirements

Quality Control and Assurance

Recognized Federal Holidays

1.2.2 Hours of Operation

1.2.3 Place of Performance

1.2.4 Security Requirements

2.1. Key Personnel

Contractor Key Personnel Replacement

2.1.2 Identification of Contractor Employees

2.1.3 Contractor Travel

2.1.4 Other Direct Costs (ODCs)

2.1.5 Organizational Conflict of Interest (OCI)

2.1.6 Government Rights

2.1.7 Contractor Manpower Reporting

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

3.1 Equipment (GFE), Facilities, and Supplies

3.2 Hardware, Software, and Technology Services and Materials

4.0 Contractor Furnished Items

Task 1: Program Management

4.1 Task 2: Solution Analysis, Configuration, Development, Test, Integration, and Solution Delivery

4.2 Task 3: Training and Organization Change Management

4.3 Task 4: Deployment and Release

Task 5: Cybersecurity Authorization

December 7, 2023 iv

Task 6: Capability Support

4.4 Task 7: Transition Out [OPTIONAL]

4.5 Deliverable Procedures

Deliverables Schedule

Appendix A: Reference Materials

List of Tables Table 1. Notional Capabilities Across Core Mission Areas

Table 2. AIE Draft CLIN Structure

December 7, 2023 1

Introduction This is a Task Order (TO) to obtain contractor services to develop, configure, and deploy an Accessions Information Environment (AIE) solution that implements modern business practices and technology to support the Army’s Accessions Enterprise.

Program Executive Office Enterprise Information Systems (PEO EIS) is seeking the development, delivery, and deployment of AIE, a system that will support the Army’s global operations with over 28,000 core users. Mobility, reliability, secure connectivity, and data access are paramount AIE attributes. The enterprise workforce must be able to perform tasks using any device, anytime, anywhere, while maintaining secure connectivity with the AIE.

Development, configuration, and deployment will consider (1) Agile methodology combined with Development, Security, and Operations (DevSecOps) 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 contract, Agile execution is defined as a group of software methods (e.g., Scrum, Kanban, SAFe®) based on iterative and incremental development and deployment of software capabilities for end users, where requirements and solutions evolve.

Contractors shall apply and perform in an Agile manner across all aspects of work and within Army organizational constraints.

The Government will not supervise or control subcontractors performing the services herein. Such subcontractors shall be accountable solely to the prime contractor (Contractor) who, in turn, is responsible to the Government.

1.1 Description of Services

The contractor shall provide qualified personnel with relevant experience, domain knowledge, and other items and non-personal services necessary (except those specified as Government Furnished in Section 3 of this document) to perform the AIE services, as defined in this Performance Work Statement (PWS).

Agile and DevSecOps methodologies will apply for incremental and value-added delivery to users. The definition of done means functionality in the hand of the user in production which will entail not only development but all other steps such as testing, cybersecurity vulnerability mitigation, data migration and user acceptance.

For this PWS, “deploy” is defined as moving capability to the production environment;

and “release” is defined as users having access to the new capability in the production environment.

For this PWS, Minimal Viable Product (MVP) is defined as an early version of software that delivers functionality to users to evaluate and provide feedback; and Minimum Viable Capability Release (MVCR) is defined as a set of functionality / features suitable

December 7, 2023 2 to be fielded to a production environment that provides sufficient capability or performance to deploy into operations.

The AIE solution will be hosted in cArmy to the greatest extent possible, i.e. new development will utilize tools and standards offered within cARMY to allow for rapid and frequent releases through the automated DevSecOps pipeline. The hosting environment will comply with Federal Risk and Management Program (FedRAMP+) and DoD Cloud Computing Security Requirements Guide (SRG) cloud security information Impact Level 4 (IL4) security controls.

1.2 AIE Description

1.2.1 Background

The Army Accessions Enterprise is data-driven, analytics-enabled, Soldier workforce- centric, Mobile, and customer-focused system. It provides the Army’s strength through its four missions: (1) enlist Soldiers, (2) commission Officers, (3) fulfill In-Service requirements, and (4) support and sustain. The enterprise system serves the Army well, but requires modernization, and rejuvenation to meet emerging requirements and ensure continued success. Several factors contribute to the critical imperative to transform the enterprise. Some are societal phenomena such as the declining number of qualified men and women or diminishing interest in service. Others are attributable to the Army’s failure to invest in technology and research. Regardless, the need for modernization is urgent.

The AIE is a program of record established to confront the challenges facing the Accessions Enterprise. AIE will implement new business practices and modern technology. It will be a fully integrated enterprise level capability enabling transparency, efficiency, and effectiveness of the accessions workforce to acquire best-qualified talent to meet all Army manning requirements.

AIE has not been designated a National Security System (NSS). At a minimum, AIE will displace the following systems:

• Army Recruiting Information Support System (ARISS)

• Cadet Command Information Management Module (CCIMM)

• Integrated Knowledge Resources Online for Me (IKROME)

• Army Career Explorer (ACE) (partial)

• Future Soldier Program (FSP)

• Direct Commission Accession

• Reception Module

• Warrant Officer Application Processing

• Electronic Records Management

• Scholarship Processing

Data and analytics drive the Accessions Enterprise. Therefore, the AIE will be built on a foundation of data, information technology architectures and standards, infrastructure, and analytical tools to achieve a modern end-state that will reflect the 21st century Recruiting needs and engage users through multiple platforms. The envisioned end-state is a net-centric enterprise solution characterized by standardized architecture and

December 7, 2023 3 data formats; maximized authoritative data discovery and sharing; fully integrated capabilities; intuitive ability to access, visualize, assess, and understand data; integrated and automated business processes; and single source data entry.

The Accessions Enterprise is similar in many respects to a Fortune 100 enterprise. The enterprise can be characterized as a holding company with three (3) subsidiaries; U.S.

Army Recruiting Command (USAREC), U.S. Army Cadet Command (USACC), and U.S.

Army National Guard (ARNG). Like commercial enterprises, the Accessions Enterprise relies upon partners to accomplish numerous tasks. For example, the enterprise partners with the Military Entrance Processing Command (MEPCOM) for testing, and physical and medical examinations for enlisted Soldiers, and DoD Medical Examination Review Board (DoDMERB) for Officers; the Office of Personnel Management (OPM) for background investigations; and the Army Enterprise Marketing Office (AEMO) for marketing support. Its institutional clients are the TRADOC for initial military training, and the Army at large. The Nation, especially its young people who commit to serve, are the enterprise customers. The customer for AIE is primarily all the recruiters, Army leadership and Human Resource (HR) community.

The Accessions Enterprise performs several tasks familiar to commercial enterprises.

Two of them are marketing and sales. USAREC, USACC and the USARNG employ primary and secondary market research, and data science to plan campaigns, understand their markets, provide guidance to the workforce, and inform senior leadership by developing and testing strategy. The enterprise collects, maintains, secures, and analyzes terabytes of complex data on economics, demographics, workforce performance, market campaigns and events, and advertising effectiveness along with numerous ad hoc requirements and formal studies. The toolkit includes tools for reports, stochastic processes, simulation, and optimization, and they routinely employ descriptive, predictive, and prescriptive statistics to inform decisions.

The public facing workforce is analogous to a commercial enterprise system. Soldiers and Officers interface with the public daily to build relationships, tell the Army story, participate in educational and marketing events, and obtain commitments to serve. The mission for commitments is large and requires a diverse, highly skilled workforce of Soldiers. More than 100,000 enlisted Soldiers and Officers enter the Army (total for all three components) each year. USAREC and the USARNG enlists Soldiers, selects candidates for Officers’ Candidate School and Warrant Officer Flight Training (WOFT), commissions Army Medical Department (AMEDD) professionals, and fulfills in-service requirements for Army Special Operating Forces (ARSOF). USACC annually commissions over 5,000 Reserve Officer Training Corps (ROTC) graduates. The workforce also provides “service after the commitment.” In the case of ROTC cadets, this includes leadership development and training in classroom and field environments, stipends, tuition, or board while simultaneous pursuing a bachelor’s degree. The US Army Center for Initial Military Training (USACIMT) processes over 100,000 new Soldiers into the Army at reception battalions at the four primary training bases for entry on to active duty for training.

Like commercial enterprises, the Army has customers. The Army’s customers are the American public, especially those who volunteer to serve, along with their parents, friends, teachers, coaches, and other community influencers. Social phenomena such

December 7, 2023 4 as decreasing propensity to serve and declining number of youths qualified to serve contribute to an urgent need to know and understand the customer. These factors, combined with requirements to increase the Army’s ends-strength and enhance readiness place a premium on knowing and understanding the needs, interests, and characteristics of the target audience and presenting customized messages and options for service. This knowledge is the intersection of data science enabled research and Soldier knowledge of the market.

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

1.3 Program Objectives

The overarching AIE objective is to provide accessions and recruiting capabilities (see AIE RTM) to the end user in an incremental manner via MVPs and MVCRs while holistically addressing the foundations of the solution architecture, design, data, interfaces, and system security; and leveraging industry's agile best practices through continuous integration and continuous development (CI/CD) for software development and software delivery while meeting the highest standards of cybersecurity readiness in an environment of continuous and unpredictable change.

MVPs are utilized to assess the effectiveness of functionality, with the assumption that requirements and user needs are best understood through hands-on experimentation.

Each MVP should be deployed within three (3) months from the previous; and each MVCR should be released within twelve (12) months from the previous. It is the Army’s desire that development planning be aligned with the requirement prioritization per the AIE RTM and that the requirements associated with each MVP and MVCR be identified in the product roadmap. The Government recognizes that an MVP and/or MVCR definition may evolve within the product roadmap as user needs become better understood. The RTM serves as a starting point to create relevant epics, features, user stories, and acceptance criteria with enough detail for development. The Contractor shall work closely with the Government Product Owner to ensure that the Product Backlog, stored in [software/tool], is continually and regularly maintained in alignment with the Agile cadence so that the necessary Release and Sprint Backlog items (epics and user stories) are defined with acceptance criteria and prioritized by the Government Product Owner prior to the start of each release and sprint. The Contractor shall prioritize development in accordance with the Program Backlog.

The AIE primary technical objective is to employ modern technology that enables solutions for the recruiting and accessioning workforce and commanders at multiple echelons across the breadth and depth of the Accessions Enterprise. It will collect, store, secure, and allow role-based access to sensitive data, including Personally Identifiable Information (PII) and Protected Health Information (PHI). AIE will provide timely access for studies, analyses, reporting, and decision support.

Specifically, the Army seeks to acquire a secure, interoperable, configurable solution that will (1) maximize the adoption of standardized products and business processes,

(2) operate on a network in a cloud hosting environment, (3) perform operational

December 7, 2023 5 workflow data exchange with other standardized Government systems of record, (4) provide a common operating picture, (5) optimize knowledge management / information sharing, and (6) implement a single source record that enable single data entry. The AIE solution will have proven maturity to scale user and data growth, insert technology, perform continuous upgrades, and provide long-term sustainment.

AIE will deliver and maintain reliable, secure, and timely access to systems of record, enable task accomplishment irrespective of workforce location, and respond to emerging demands for support. The AIE will enhance workforce effectiveness and efficiency by achieving the following system objectives:

• Secure, Interoperable Solution: The ability to capture, store, and maintain data in accordance with cybersecurity requirements; ability to exchange and utilize data from other systems.

• Mobility: Users perform authorized roles anytime and anywhere, on or offline, with no degradation from buffering or other performance degradations.

• Connectivity, to include remote user: perform authorized roles with mobile devices while maintaining connection and full functionality with the enterprise

• Data Access, Accuracy, and Timeliness: ability to retrieve authoritative data, maintain its integrity in an urgent manner responsive to specific requirements for the data

• Data maintainability; management, processes, and data services to support standardization as well as rapid development of data-driven decision capability

• Device-agnostic, Real-time Access from Multiple Domains: regardless of OS, version, or device without buffering from multiple Army and Department of Defense (DoD) systems of record

• Interface to Systems of Record: enabling the secure exchange of data between and among systems while maintaining integrity and access for authorized users

• Common Operating Picture: ability to view authoritative data through multiple views defined by role and echelon

• Knowledge Management: collaborative management of information within the enterprise to achieve enterprise goals

• Leadership End-to-end Enterprise Visibility: ability for longitudinal and vertical analysis at echelon, aggregates and disaggregates data to meet requirements

• Single Source Record: one authoritative record for each individual candidate / recruit that captures each transaction during the individual’s record lifecycle

• Network Modernization: improving visibility, bandwidth, and management, analogous of providing roadways for high-speed traffic.

• Automated Business Processes: building automation into workflows to enhance effectiveness and efficiency.

December 7, 2023 6

These objectives shall result in a solution, hosted in cArmy to the greatest extent possible, authorized and provisioned in a FedRAMP+ compliant cloud environment (to include IL4 security and privacy controls per the AIE requirements), with mobile and offline capabilities for the Army to perform its mission.

Table 1 provides a description of the notional capabilities across mission areas. This table depicts which of the eight core capabilities are associated with each of the six major mission areas.

Table 1. Notional Capabilities Across Core Mission Areas

1.4 Scope

The Army requires the following services: (1) manage; (2) analyze, design, configure, build, test, secure, and integrate the solution that meets the requirements in the AIE RTM (see AIE RTM for a draft list of AIE requirements); (3) develop training materials and delivery training to end users, (4) release and deploy capability, (5) obtain and maintain cybersecurity posture; and (6) provide capability support to the production baseline.

These services will be acquired across the following tasks:

• Task 1: Program Management

• Task 2: Solution Analysis, Configuration, Development, Test, Integration, and Solution Delivery

• Task 3: Training and Organizational Change Management

• Task 4: Capability Deployment and Release

• Task 5: Cybersecurity Authorization

• Task 6: Capability Support

• Task 7: Transition Out

1.5 Period of Performance

The period of performance is as follows:

Capability Enlisted Mission

In-Service Direct Commission

ROTC

Campus

ROTC

Summer

Accessions Support

Lead Generation / Management x x x x x x

Prospecting x x x x x x Interviewing x x x x x x Processing x x x x x x Pay and Incentives x x x x Training/ Leader Dev x x x x x

Marketing x x x x x x Intelligence x x x x x x

December 7, 2023 7

• 12-month Base Period: begins on the designated date defined at contract award

• Four (4) 1 year Option Periods: begins when exercised by the Government in concert with the Program Roadmap maintained by the Contractor and concurred with by the Government. Contractor performance will be monitored, and results will be reviewed when deciding to exercise an Option Period.

The period of performance is not to exceed five (5) years.

1.6 Contract Type

This is a Hybrid contract including Firm Fixed Price (FFP), Cost Plus Fixed Fee (CPFF), CPFF Level of Effort (LOE), CPFF Completion, and Cost Reimbursable (no fee) line items for Travel and Other Direct Costs (ODCs).

1.7 Contract Structure

The draft contract structure is depicted in Table 2.

Table 2. Draft AIE CLIN Structure

Description Scope Period of Performance APPN

Transition In (see Task 1) Onboarding Activities Knowledge Transfer Account Provisioning

First 90 Days of Contract

RDTE

Task 1: Program Management

Program Planning and Reporting Program Management (Cost, Schedule, Performance, Quality)

Contract Duration

RDTE

Task 2: Solution Analysis, Configuration, Development, Test, Integration, and Solution Delivery

Task 3: Training and Organizational Change Management

Task 4: Capability Deployment and Release

Planning Interval (PI) Planning Sprint Execution Code Delivery Data Management, Migration, and

Conversion Baseline Integration Baseline Deployment and Release Planning Deployment Readiness Release Readiness Training Planning and Management Training Material Development Training Preparation Training Delivery to End Users

RDTE

SURGE OPTIONAL CLIN

Task 5: Solution Analysis, Configuration, Development, Test, Integration, and Solution Delivery

Task 6: Training and Organizational Change Management

Task 7: Capability Deployment and Release

Planning Interval (PI) Planning Sprint Execution Code Delivery Data Management, Migration, and

Conversion Baseline Integration Baseline Deployment and Release Planning Deployment Readiness Release Readiness Training Planning and Management Training Material Development Training Preparation Training Delivery to End Users

Contract Duration;

3-month periods

RDTE

Task 8: Cybersecurity Authorization

Authority To Operate (ATO) Risk Management Framework (RMF)

December 7, 2023 8

Description Scope Period of Performance APPN

Task 9: Capability Support Post Deployment Support Contract Duration;

initiated 60 days prior to first MVCR

RDTE

Task 10: Transition Out

[OPTIONAL]

Transition Out Planning Transition Out Implementation

Last 120 Days of Contract

RDTE

Licenses Additional Licenses Contract Duration RDTE

Travel Actual Travel Costs Contract Duration RDTE

Other Direct Costs (ODCs) Actual ODCs Contract Duration RDTE

Contractor Manpower Reporting

Manpower Reports Contract Duration

Contract Data Requirements List (CDRL)

Required Documentation Contract Duration

1.8 General Information Requirements

Quality Control and Assurance The Contractor will maintain an effective quality control program to ensure services are performed as agreed to in the contract. The AIE quality assurance will focus on continually improving the flow of value-added and secure functionality to user through the CI/CD pipeline. This will include the following:

• Percentage of each high-level capabilities completed – deployed to PROD and accepted by users.

• Number of user stories, prioritized and approved ready for development.

• Velocity - Amount of work the team completes during a given period.

• Sprint Burn Down - Pace of work completion over a given period.

• Sprint Burn Up - The amount of work completed for a feature compared to the amount of work required for the feature.

• User acceptance rate

• Escape Rate

• Average time for developed functionality to reach cybersecurity vulnerability approval for deployment.

• Recidivism Rate - Percent of work returned to the developer for various reasons within the CI/CD Workflow

• Delivered Features -Measures progress of backlog conversion and workflow process to product that is delivered

Recognized Federal Holidays

• New Year’s Day

December 7, 2023 9

• 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.2.2 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.2.3 Place of Performance

All activities requiring Government participation (e.g., planning, demonstrations, reviews) will take place virtually, at the AIE PMO Government facility at Fort Belvoir, VA, or at the Functional Lead Government facility at Fort Knox, KY unless otherwise determined based on the specific activity. The Contractor facility may also be used for these events and other key events. These events will be coordinated in advance to include associated logistics.

Local 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 PMO 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 Contracting Officer’s Representative (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.

December 7, 2023 10

1.2.4 Security Requirements

The DD254 is provided.

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.2.4.1 Authorities and Scope

This paragraph addresses contractor access to, or possession of, collateral (non-SCI) classified information, CUI, PII, PHI, 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 AHRS integrated portfolio efforts, other integrated 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

December 7, 2023 11 duties. This also includes all Executive Orders, policies, laws, statutes, as promulgated in DoD and DA Directives, Regulations, Instructions and Manuals as provided in the following references.

Agile Qualifications The Contractor shall have previous Agile development experience and demonstrate organizational culture and commitment to Agile principles.

2.1. Key Personnel

Key personnel are those people considered essential to successful Contractor performance. All key personnel must be on board at contract 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.

The Contractor will fill the following Key Personnel positions for the purposes of this contract.

Agile Program Manager (PM) The Contractor will assign an individual to serve as a Program Manager (PM) for this effort.

This individual will be the single point of contact for the Government Task Monitor (GTM) and COR. The PM will be responsible for the performance of the work. The name of this person and an alternate, who will act for the Contractor when the PM is absent, will be designated in writing to the Contracting Officer. The Contractor PM and alternate will have full authority to act for the Contractor on all matters relating to daily operation of this contract. The Contractor PM or alternate will be available in accordance with paragraph 1.2.2 Monday through Friday during business hours except Federal holidays or when the Government facility is closed for administrative reasons.

The PM will have the following experience and qualifications:

a. 5 or more years of leading successful Agile Development teams

b. 3 or more years of experience leading teams in delivering in DevSecOps environment

c. 5 or more years of acquired knowledge and supervision of employees of various labor categories and skills in efforts similar in size and scope as this acquisition

d. Agile certification such SCRUM Master, SAFE, etc.

e. 5 or more years of experience managing the entire agile software development lifecycle, including frequent production delivery

f. 5 or more years of experience with researching and fielding new and innovative technology

g. Bachelor’s degree in an IT related field, or equivalent experience)

December 7, 2023 12

System Architect/Technical Lead The System Architect/Technical Lead will have the following experience and qualifications:

a. Proven experience in implementing technical solutions as a whole: infrastructure, data, operating system, development, testing,

b. 5 years of experience in technical leadership providing a team with design, architecture, and development vision and guidance.

c. 5 years of experience communicating complicated data, architecture, and development topics clearly to decision-making bodies and senior leadership

d. Strong understanding of continuous Risk Management Framework (cRMF)

e. 3 or more years of experience with modern software development tools such as:

GITLAB, SonarQube, HP ALM suite, and the Atlassian Suite is desired

f. 3 years of experience in managing DevSecOps pipeline

g. BS in Computer Science, information systems or a related technical degree plus 10 years’ relevant experience with Customer Relationship Management (CRM) type implementation experience.

Lead Developer The Lead Developer will have the following experience and qualifications:

a. 10 or more years of experience developing applications using modern coding languages

b. Understanding latest development and data management techniques

c. Ability to establish development vision for the team.

d. 3 or more years of experience leading coding and technical reviews

e. 3 or more years of experience leading developers in DevSecOps environment.

f. BS in Computer Science, information systems or a related technical degree plus

10 years’ relevant experience with Customer Relationship Management (CRM) type implementation experience.

Lead Test Engineer The Lead Test Engineer will have the following experience and qualifications:

a. 5 or more years of experience applying Agile methodologies and tools on at least one IT related development program, to include defining and testing user story acceptance criteria

b. 5 or more years of experience converting user stories and acceptance criteria into test scripts.

c. Strong communication skills and ability to facilitate research and analysis with all team members to include Product Owners, Developers, and Senior Leaders.

d. 10 or more years of acquired knowledge in planning, directing, and managing interoperability testing (interfaces, data quality, etc.)

e. 5 or more years of experience as Test Lead on a CRM-type implementation is desired

December 7, 2023 13

f. Bachelor’s degree in Computer Engineering, Computer Science, Information Systems, Information Technology, or a related Engineering or IT discipline

Release Manager

a. Experience with developing software and review for software quality

b. Experience developing test scripts to meet user stories, user story features

c. Experience reviewing software decencies between features, and user stories to ensure

Enterprise Solutions will integrate prior to releasing

d. 10 or more years of experience as implementing software development and Software

Quality is desired

e. Bachelor’s degree in Computer Engineering, Computer Science, Information Systems, Information Technology, or a related Engineering or IT discipline

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. Government process time should not inhibit the Contractor from meeting the timelines expressed above.

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

2.1.3 Contractor Travel

Contractor personnel will be required to travel CONUS, 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 CENTCOM, PACOM AND 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.

December 7, 2023 14

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

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

2.1.6 Government Rights

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

2.1.6.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). Note that all licenses shall be purchased through PEO EIS CHESS vehicle, unless otherwise authorized by the government.

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

December 7, 2023 15 and software deliverables. These assertions shall comply with the following requirements:

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

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

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

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

2.1.7 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 Procurement Integrated Enterprise Environment (PIEE).

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.

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

3.1 Equipment (GFE), Facilities, and Supplies

The Government will provide Contractor personnel performing under the Contract in Government facilities 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.

Upon request and in support of task execution, the Government will provide computer equipment (e.g., laptops, tablets, and phones) with Local Area Network / Wide Area Network (LAN/WAN) interface, and NIPRNet (.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.

December 7, 2023 16

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:

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

2) Quantity received, issued, and on hand

3) Contract number or equivalent code designation

4) Location

5) Disposition

6) Posting reference and date of transaction

Upon completion of the contract, the Contractor shall return all non-expendable Government-issued items to the COR.

3.2 Hardware, Software, and Technology Services and Materials The Government will provide the most recent versions of available information requested by the Contractor for use in performing the tasks herein. The Government provided information shall not be shared with other Government or commercial agencies without the approval of the AOR or Product Manager.

The Government will provide Army data to the Contractor for use in performing the tasks identified herein. The terms and conditions of the Government Data Use Agreement will apply.

4.0 Contractor Furnished Items

The Contractor will develop and deliver a solution that meets the AIE requirements (see AIE RTM for a draft list of AIE requirements). The AIE solution will operate on the NIPRNet and will be hosted on the NIPRNet in cArmy to the greatest extent possible and will be IL4 compliant.

Task 1: Program Management Program Management activities will span all contract tasks. This includes the management and oversight of all activities performed by Contractor personnel, including subcontractors, to satisfy the requirements of the contract.

The Program Management objective is to define, manage, and execute processes and planned activities within cost, schedule, and performance parameters.

Program Management includes:

• Program Planning and Reporting ‒ Establish and perform an Agile Program Management Plan (PMP) that describes organizational Agile culture and support mechanism for continuous improvement defines the specific Agile and DevSecOps methodology and flavor to deliver incremental and rapid capabilities to users in Production describes delivery cadence identifies Agile and DevSecOps tracking tools

December 7, 2023 17 describes the personnel management process and procedure(s) to provide qualified staff with the requisite knowledge, skills, experience, and certifications necessary to perform in the position to which they have been assigned described the license management process and procedure(s) for all necessary commercial, Open Source, and third-party software agreements, to include licenses, warranties, and/or commercial maintenance agreements, procured for use in developing and delivering the AIE solution describes the cost and software data reporting (CSDR) process and procedure(s) that satisfies the guidelines contained in the DoD 5000.04-M-1, CSDR Manual, and the requirements in the Government-approved CSDR plan for contract (DD Form 2794). Note: In the “Remarks” tab of the CSDR plan, there is language stating “The Reporting Entity [(i.e., the Contractor)] is instructed to provide a Resource Distribution Table [RDT] upon contract award, which identifies the value and work assigned to the Reporting Entity and its subcontractors. The Reporting Entity [(i.e., the Contractor)] shall provide an updated RDT when additional quantities/scope are added to the contract to ensure that no major sub-contract(s) breach the direct CSDR reporting threshold specified in DoDI 5000.02 and DoDM 5000.04-M-1."

describes the contract funds management process and procedure(s) Establish and perform reporting forums aligned with processes to report on task status and ensure full disclosure of, and Government visibility into, program execution progress, reporting on applicable cost, schedule, and performance metrics, and Earned Value performance of cost-type CLIN outcomes, using the DevSecOps tools to the extent possible

• Quality Management: Perform quality assurance as a process, in accordance with the Agile approach, that monitors the overall plan, procedures, and controls that the Contractor will use to provide and maintain a satisfactory quality system for the duration of the contract

• Cost and Software Data Reporting (CSDR): Establish a baseline, monitor, and perform CSDR in accordance with the PMP, to include flowing down CSDR requirements to subcontractors as applicable, and maintaining the Resource Distribution Table (RDT) to ensure that no major subcontract(s) breach the direct CSDR reporting threshold specified in DoDI 5000.02 and DoDM 5000.04-M-1

• Contract Funds Management: Establish a baseline, monitor, and report contract funds status in accordance with the PMP

• License Management ‒ Provide license management, maintenance, and renewal of any applications and tools procured under this contract, with justification and Government

December 7, 2023 18 approval, to include documenting, tracking, and maintaining a log of all product licenses, and preparing a schedule to ensure licenses are assigned, unassigned, and renewed as needed such that there is not a gap in product usage

‒ Ensure the following is identified for all licenses License Type (e.g., enterprise) License Use (e.g., single computer) License Issue: Note: All licenses shall be issued in the name of the

U.S. Government) Perpetual Agreement Terms Available Documentation: Note: All Software documentation shall be identical to that provided to a customer in the general public in the course of a private sale; the Government’s right to software documentation shall be no less than the rights provided with the associated software

Applicability Terms Maintenance Terms

‒ Prepare a recurring report of all licenses in accordance with the PMP ‒ Transfer all necessary commercial, Open Source, and Third (3rd) Party software agreements used for AIE, to include licenses, warranties, and/or commercial maintenance agreements, as appropriate

• Information / Knowledge Management and Product Delivery ‒ Manage and maintain all program and technical products and documents delivered under the contract within the relevant repository per the Information ‒ Knowledge Management and Document Management process Post deliverables agreed to in the PMP to the AIE Knowledge Repository site within 24 hours of submission to the COR

• Property Management: Establish and conduct a property management process to manage and track Government-provided property, items, and services in accordance with paragraph 3.0

• Agile Program Kick-off Meeting: Conduct within five (5) business days of award ‒ Provide an introduction between the Contractor personnel, to include all Key

Personnel) and Government personnel who will be involved with the contract ‒ Address technical, management, and security issues, and travel authorization and reporting procedures ‒ Discuss the Contractor’s CSDR process ‒ Decide on initial report suspense dates and cadence for all recurring reporting and program reviews requirements ‒ Introduce Agile and DevSecOps teams ‒ Provide delivery Agile and DevSecOps delivery cadence

December 7, 2023 19

‒ Provide initial impediments and issues to rapid and incremental delivery to users

‒ Provide Approach on grooming the backlog

• Transition In ‒ Develop and implement a Transition In Plan that details the activities and resources needed to perform the contract requirements, to include the onboarding staffing plan (% onboard within x days), key personnel by name and qualifications, a schedule for all Transition In activities, data / information deemed necessary to be provided by the Government in the forms of knowledge transfer, and Transition metrics. The purpose of this transition in plan to minimize technical debt, facilitate efficient data migration, and account transfers.

‒ Conduct Transition In for no more than 6 months Deliverable(s):

• CDRL A001: Agile Artifacts

• CDRL A002: Program Roadmap

• CDRL A003: Reporting Materials and Metrics

• CRDL A004: Cost-Hour Report (Flexfile)

• CDRL A005: Contractor Business Data Report (DD Form 1921-3)

• CDRL A006: Software Resources Data Reporting (SRDR)

• CDRL A007: Contractor Funds Status Report (CFSR)

• CDRL A008: Kick-off Meeting Materials

• CDRL A009: Transition In Plan

• CDRL A010: Transition In Status Report

4.1 Task 2: Solution Analysis, Configuration, Development, Test, Integration, and Solution Delivery The Solution Analysis, Configuration, Development, Test, Integration, and Solution Delivery objective is to delivery value-added AIE capabilities to users…