AIE PWS Task Order 1.pdf

Distribution Statement A: Approved for Public Release

Accessions Information Environment Task Order 1 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

AIE Task Order 1 PWS – CUI April 8, 2024 ii

THIS PAGE INTENTIONALLY LEFT BLANK

April 8, 2024 iii

Table of Contents

1. Introduction

1.1 Description of Services

1.2 AIE Description

1.2.1 Background

1.2.2 Program Objectives

1.3 Scope

1.4 Period of Performance

1.5 Contract Type

1.6 Contract Structure

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 Agile Qualifications

1.7.7 Key Personnel

1.7.8 Contractor Key Personnel Replacement

1.7.9 Identification of Contractor Employees

1.7.10 Contractor Travel

1.7.11 Other Direct Costs (ODCs)

1.7.12 Organizational Conflict of Interest (OCI)

1.7.13 Government Rights

2.0 Reference Materials

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

4.1 Contractor Furnished Property and Services

4.2 Personal / Contractor-Owned Property

5.0 Performance Requirements – Specific Tasks

5.1 Task 1 Category: Agile Program Management

April 8, 2024 iv

5.2 Task 2 Category: Salesforce Solution Design, Configuration, Development, and Test

6.0 Deliverables

6.1 Deliverable Procedures

6.2 Deliverables Schedule

Appendix A: Reference Materials

Appendix B: List of Attachments

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

Table. 2 Notional Personnel

Table. 3 Notional Labor Categories

Table. 4 Deliverable Schedule

April 8, 2024 1

1. Introduction This is a Task Order (TO) to obtain Contractor services for one (1) Agile team consisting of 9.5 Full Time Equivalent (FTEs) to continue development, configuration, testing and deployment of Accessions Information Environment (AIE). This Agile team shall operate within existing Salesforce platform, within the established requirement traceability matrix (RTM) and CI/CD pipeline.

The solution(s) developed in this task order will utilize Agile delivery and leverage the latest technology offerings. 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.

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

AIE is currently hosted in the Salesforce Government Cloud Plus as a Service environment utilizing the Public Sector Solutions. 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 (4) missions: (1) enlist Soldiers, (2) commission Officers, (3) fulfill In-Service requirements, and (4) support and sustain. See the parent IDIQ PWS for further background details.

1.2.2 Program Objectives

AIE’s overarching objective is to provide accessions and recruiting capabilities (see Attach01-AIE-RTM.pdf) 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.

April 8, 2024 2

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

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 configuration and development. The Contractor shall work closely with the Government Product Owner to ensure that the Product Backlog, stored in JIRA or other Agile tracking 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 aligned to Government priorities.

AIE’s 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.

The table below 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.3 Scope

The scope of this task order is obtaining one Agile team to continue AIE Salesforce development, configuration, testing and deployment with focus on achieving these following objectives:

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

April 8, 2024 3

• Maximize out-of-box Salesforce functionality.

• Continue to mature the data model.

• Work closely with users to adjust requirements – focus not only on requirements but user needs.

• Improve Human Center Design (HCD) through continual demonstration to users to gage user satisfaction.

• Execute hypothesis-driven approach based on testing assumption with demonstrations and real-world user validation.

• Rigorously track Agile metrics such as estimates vs. actual velocity; escape rate;

Salesforce out-of-box utilization percentages; user satisfaction; recruitment processing time improvements; recruiter record accuracy rate; and system performance.

• Employ “Flat” team with focus and authority given to technical team members who produce recruitment and accession capabilities for Army users.

• Utilize automation in testing, cybersecurity, and release management as much as feasible.

These Task Order services will be acquired across the following two tasks described in detail in section 5.

• Task 1: Agile Program Management

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

Solution Delivery The table below provides notional roles, descriptions, labor categories, and full-time equivalent allocation level. These roles will likely change over time based on requirements, thus the only as starting point. The contractor may propose a different team composition during task order performance. The asterisk (*) denotes key personnel.

Table. 2 Notional Personnel

Role Description LCAT FTE

*Solution Technical

Lead

• With deep Salesforce HR module expertise maps out-of-box Salesforce functionality to AIE requirements and Army/user needs

• Leads contractor technical team by providing design, coding, and architecture decisions

• Oversees end-to-end technical delivery of Salesforce capabilities to users in rapid and incremental manner

Technical Lead 1

April 8, 2024 4

• Configures Salesforce for AIE

2 Data Architect

• Oversees AIE platform data integrity by maturing the data model and accompanying data dictionary

• Designs data solutions that facilitate scalability, security, reusability

• Leverages Salesforce data best practices in all design and deployment activities

Developer Senior 1

Data

Interface Specialist

• Creates API-based interfaces using latest interface tools such MuleSoft

• Maps AIE Salesforce data-fields to inbound and outbound data

Developer Senior 1

Data

Migration Specialist

• Migrates all required data into AIE

• De-identifies data for testing purposes

• Performs data capacity design and configuration

Developer Mid 1

5 *Developer Lead

• Establishes design and coding best practices for customized solutions

• Perform regular code review to make sure all code meets best practices standards

• Provides coding activity estimate.

• Writes Apex code for customized solutions

• Configures Salesforce for AIE

Developer – Principle 1

6 Developer

• Write codes.

• Performs unit testing.

• Resolves defects.

• Configures Salesforce for AIE

Developer – Mid 1

7 *Test Lead • Leads all verification and validation activities to include

Tester 1

April 8, 2024 5 development, integration, system, and user testing

• Continues to automate regression and other testing activities

• Facilitates testing traceability to requirement and user stories

• Facilities identification, tracking and resolution of all defects

8 Test Engineer

• Write test scripts.

• Performs manual testing

• Review automated testing.

• Tracks and resolves bugs

Tester 1

Recruitment and

Accession Business Analyst

• With knowledge of Army recruiting and accession processes decomposes epics, features, and user stories to low level user stories and acceptance criteria that can be configured and developed in a Sprints

• Maintains product backlog with close coordination with government Product Owner

Product Owner .5

10 SCRUM

Master

• Facilitates Sprint Planning, daily standups, and other coordination activities

• Removes team impediments

• Tracks all activities in Agile tool such a JIRA, etc.

• Creates management related documentation and briefings

Product Analyst 1

1.4 Period of Performance

The period of performance is one (1) 12-month Base Period with four (4) 12-month option years.

1.5 Contract Type

This task order is Cost Plus Fixed Fee (CPFF) Term, with Cost Reimbursable (no fee) line items for Travel and Other Direct Costs (ODCs). Software deliverables or artifacts that will demonstrate successful sprint completion may be captured in Technical

April 8, 2024 6

Guidance Letters (TGLs) issued during task order performance. TGLs may be issued by the COR and will be within the scope of the task order. If the contractor believes a TGL is outside of the scope of the task order, the contractor shall notify the Contracting Officer upon receipt of the TGL and shall not perform in accordance with the TGL until the Contracting Officer has determined that the TGL is within scope.

1.6 Contract Structure

The draft contract structure is depicted in the table below.

Table. 3 Notional Labor Categories

Description Scope Period of Performance

Transition In (see Task 1)

Onboarding Activities Knowledge Transfer Account Provisioning

First 90 Days of Contract

Task 1: Agile Program Management

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

Task 2: Salesforce Solution Configuration, Development, and Test

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

SURGE OPTIONAL

CLIN

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

Contract Duration;

3-month periods

April 8, 2024 7

Description Scope Period of Performance Task 5: Cybersecurity

Authorization Authority To Operate (ATO) Risk Management Framework (RMF) Contract Duration

Task 6: Capability Support Post Deployment Support Contract Duration; initiated 60 days prior to first MVCR Task 7: Transition Out

[OPTIONAL]

Transition Out Planning Transition Out Implementation Last 120 Days of Contract

Licenses Additional Licenses Contract Duration Other Direct Costs (ODCs)Travel Actual ODCs, and actual travel Contract Duration

Contractor Manpower Reporting Manpower Reports Contract Duration

Contract Data Requirements List

(CDRL)

Required Documentation Contract Duration

1.7 General Information Requirements

1.7.1 Quality Control and Assurance

The Contractor shall 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 users through the CI/CD pipeline. This includes tracking key metrics. Monitoring and measuring help to identify areas for improvement and ensure that the implementation is meeting the goals. The Contractor shall meet the threshold requirements outlined in the government approved QASP, (see Attachment 001). This will include the following:

• Salesforce out-of-box utilization: Percentage of Salesforce capabilities deployed to users without customization

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

• User acceptance rate

• Escape Rate

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

1.7.2 Recognized Federal Holidays

• New Year’s Day

• Martin Luther King Jr.’s Birthday

• Presidents Day

April 8, 2024 8

• 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 8 AM to 5 PM Monday thru Friday, core hours being 9 AM to 3 PM 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 8 AM to 5 PM Monday thru Friday.

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

1.7.5 Security Requirements

The DD254 is provided.

April 8, 2024 9

The Contractor shall 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 shall 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 shall ensure the aforementioned information is properly safeguarded in accordance with the applicable requirements to protect adequately against unauthorized disclosure.

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

April 8, 2024 10

1.7.6 Agile Qualifications

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

1.7.7 Key Personnel

Key personnel are those people considered essential to successful Contractor performance. All key personnel must be on board at task order award. The Contractor shall 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 shall fill the following Key Personnel positions for the purposes of this task order.

1.7.7.1 Solution Technical Lead

The Salesforce Solution Technical Lead provides overarching Salesforce technical design and implementation guidance to meet AIE requirements in the most efficient manner. This entails rapid and incremental delivery to users, as well as minimizing downstream technical debt through scalable data and application architecture.

The Solution Technical Lead will have the following experience and qualifications:

a. 5 or more years of leading successful Salesforce implementation with minimum of 1,000 users

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

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

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

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

e. 1 or more years of experience working in Army or DoD environments

f. Bachelor’s degree in an IT related field

1.7.7.2 Developer Lead

The Apex Developer Lead institutes development quality standards, takes on the most challenging coding assignments, and performs code reviews.

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

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

b. Understanding of 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.

April 8, 2024 11

f. BS in Computer Science, information systems or a related technical degree plus and/or equivalent five (5) years' experience.

1.7.7.3 Test Lead

The Test Lead oversees all stages of testing from test script creation, to test execution, and defect resolution. The focus is on automating testing as much as feasible, performing frequent regression testing, and supporting all user testing activities.

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

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

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

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

April 8, 2024 12 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.

1.7.11 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.12 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 shall notify the Contracting Officer immediately whenever it becomes aware that such access or participation may result in any actual or potential OCI and shall promptly submit a plan to the Contracting Officer to avoid or mitigate any such OCI. The Contractor’s mitigation plan will be determined to be acceptable solely at the discretion of the Contracting Officer and in the event the Contracting Officer unilaterally determines that any such OCI cannot be satisfactorily avoided or mitigated, the Contracting Officer may affect other remedies as he or she deems necessary, including prohibiting the Contractor from participation in subsequent contracted requirements which may be affected by the OCI.

1.7.13 Government Rights

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

April 8, 2024 13 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.

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

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

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

2.0 Reference Materials

See Appendix A.

April 8, 2024 14

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.

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 shall develop and deliver a solution that meets the AIE requirements (see Attachment (TBD) or a complete 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.

4.1 Contractor Furnished Property and Services

The Contractor shall furnish all necessary supplies, software, data, parts, materials, tools, support equipment, labor, and vehicles required to perform all operations required

April 8, 2024 15 by this contract, except for those items or services specifically stated as Government-furnished.

Contractor-furnished equipment shall be maintained at all times in a safe and serviceable condition in accordance with the manufacturer recommendations.

Maintenance of Contractor-furnished equipment will not be performed on Government property or at Government expense. The COR or designated representative may inspect the Contractor’s equipment at any time and direct the removal of any unsafe or objectionable equipment from the installation / facility. All Contractor-furnished equipment shall be operable and shall meet all local, state, federal, and environmental requirements.

4.2 Personal / Contractor-Owned Property

The Contractor shall ensure that personal/Contractor-owned property brought on Government work sites is clearly marked as such to preclude misidentification as Government property.

The Contractor shall ensure that personal / Contractor-owned property meets safety specifications as set forth by Occupational Safety and Health Administration, Maryland Occupational Safety and Health, Virginia Occupational Safety and Health, or other state Occupational Safety and Health where contract work is being performed, and the U.S.

Army.

The Contractor shall ensure that all personal / Contractor-owned property is removed from the Government installations / facilities in which it resides at the end of the performance period. The Contractor shall not connect any personal / Contractor-owned computer equipment to any Government network.

5.0 Performance Requirements – Specific Tasks

The focus of the Agile Team shall be incremental and rapid delivery of Salesforce capabilities to users. Task 1: Agile Program Management focuses on planning and tracking of capability delivery, while Task 2, the more important task focuses on execution.

5.1 Task 1 Category: Agile Program Management

Agile Program Management activities will span all contract tasks. This includes managing and overseeing all activities performed by Contractor personnel, including subcontractors, to satisfy the requirements of the contract.

The Agile Program Management established at the program level by the government defines, manages, and executes processes and planned activities within cost, schedule, and performance parameters in rapid and incremental manner.

Agile Program Management includes:

a. Agile Program Planning and Reporting

1) Provide updates to the AIE Agile Program Management Plan (APMP)

• Agile measures as described in QASP

April 8, 2024 16

• Agile process and procedure(s) to deliver incremental and rapidly by reducing non-value-added steps and deliverables

2) DevSecOps delivery process that works in concert with the established AIE DevSecOps processes and tools

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

4) Contract funds management process and procedure(s)

5) Contractor QCP

6) Updates to Program Roadmap.

7) Cost and Software Data Reporting (CSDR): Establish a baseline, monitor, and perform CSDR in accordance with the APMP, 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

b. Contract Funds Management: Establish a baseline, monitor, and report contract funds status in accordance with the APMP.

c. License Management: Provide license management and renewal of any additional applications and tools procured, with justification and Government approval, for the development environment, 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. Note licenses for AIE Salesforce should be purchased by government, exceptions for discovery or special cases will need government approval.

d. Manage and maintain all program and technical products and documents delivered under the contract within the relevant AIE DevSecOps Tools or designated repository per the Information / Knowledge Management and Document Management process described in the APMP

e. Transition In: Develop and implement a Transition In Plan that details the activities and resources needed to perform the contract requirements, to include the on-boarding 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

f. Conduct Program Kick-off Meeting: Conduct within ten (10) business days of award

1) Provide an introduction between the Contractor personnel, to include all Key

Personnel) and Government personnel who will be involved with the contract

2) Address technical, management, and security issues, and travel authorization and reporting procedures

3) Discuss the Contractor’s CSDR process

4) Decide on initial report suspense dates and cadence for all recurring reporting and program reviews requirements

g. Strategic communication and Organizational Change Management: Provide recommendations support for strategic initiatives per government request.

April 8, 2024 17

h. Organizational Change Management (OCM): Assist and support the Government AIE PMO and FMD teams with content, recommendations, and subject matter expertise to ensure the alignment and readiness of all AIE receiving organizations. This includes, but is not limited to providing content, recommendations, and subject matter expertise in support of Government-led efforts to:

1) Develop organizational and team designs, roles, and responsibilities as needed to support AIE.

2) Design, develop, and implement stakeholder management efforts at all levels of the organization to build buy-in and acceptance of AIE releases and future capabilities.

3) Plan and implement best practice training, deployment, and organizational readiness plans to ensure receiving organization readiness.

4) Assess user readiness, using Government provided tools, to leverage current and future AIE capabilities and initiate corrective actions as needed.

Deliverable(s):

• CDRL A001: Updates to Agile Program Management Plan (APMP)

• CDRL A002: Updates to Program Roadmap

• CDRL A003: Materials, Reports, and Metrics

• CRDL A004: Cost-Hour Report (Flexfile)

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

• CDRL A006: Contractor Funds Status Report (CFSR)

• CDRL A007: Transition In Plan

• CDRL A008: Small Business Utilization Report

• CDRL A009 Government Property (GP) Inventory Report

• CDRL A010: OCM Support and Staffing Plan

5.2 Task 2 Category: Salesforce Solution Design, Configuration, Development, and Test The Agile team’s main focus will be on capability delivery which consists of Salesforce configuration, development, testing and deployment. These activities consist of:

a. Development Planning and Reporting

1) Develop and update the Agile Salesforce Configuration Development Plan

(ASDP) that describes the planned approach, detailed end-to-end processes and procedures, and development framework for: (1) continuous capability delivery; (2) requirements management and traceability; (3) how capability is prioritized, designed, developed, implemented, tested, integrated, and delivered incrementally (e.g., sprints, releases); (4) how defects are managed, tracked and resolved, to include recurring defects; (5) how cybersecurity security compliance is ensured; (6) how technical debt is identified, manages, tracked, reported, and remediated; (7) use of DevSecOps processes and procedures, to include aligning with the AIE processes within the Government-provided environments and AIE baseline, and complying with security policies within the AIE production baseline; (8)

April 8, 2024 18 use of automation and solution orchestration; (9) Agile Team structure, responsibilities, expertise composition, and synchronization; (10) agile processes and procedures to be implemented, to include alignment and interaction with Government PI Planning; (11) synchronization with the Government; and (12) metrics used to monitor progress aligned with the metrics used by the AIE baseline

2) Report status

a. Provide metrics utilizing the DevSecOps tools within the development environments when available, to include establishing dashboards and reports as described in the ASDP

b. Provide technical debt status

c. Provide activity-based reports and logs (e.g., test reports) per documented plans

d. Implementation / Agile Execution

3) Provide rapid delivery in small batches, increasing the frequency and pace of releases, by applying CI/CD practices; to include planning and supporting streamlined and efficient adoption of features and/or products across end users

4) Integrate security into the DevSecOps workflow in a collaborative way by employing a DevSecOps approach that maintains the security policies within the AIE production baseline, and delivering functionality with built-in security

5) Ensure all configuration and development tasks (e.g., design, BPR, sprint planning, sprint reviews) are identified in the Program Roadmap

6) Collaborate with the Government to agree upon PI and sprint ceremonies, to include cadence, Definition of Done, and products; it is expected that user stories will be complete during PIs

7) Collaborate with the Government to prioritize the program backlog and conduct continuous, iterative backlog grooming sessions to gather, elicit, understand, elaborate, and decompose the requirements; the backlog serves as the primary authoritative requirements source for all capabilities and solutions to be delivered

8) Ensure the backlog is accurately prioritized, populated, tracked, and reported to ensure accurate and useful data to include tracking agile metrics

9) Ensure that design assumptions are understood

10) Conduct reviews that, where applicable, demonstrate the work completed, identify design decisions, identify progress against the work planned, report metrics and team velocity, report blockers, address risks, issues, and corrective actions, and provides forecasts, address lessons learned, and identify improvements

11) Analyze requirements, identify epics and features, and create user stories for both business functionality and technical requirements; define definitively

April 8, 2024 19 testable acceptance criteria; estimate the size of user stories; and design, implement and test each user story

12) Perform unit testing to validate developed code / functionality and acceptance criteria

13) Prioritize epics and/or features into sprints / releases

14) Document epics, user stories, user story features, release trains and other agile artifacts

15) Create / update software design and interface documentation to ensure currency and completeness of the solution

16) Manage, update, and maintain technical artifacts within the development tools

17) Report, escalate, and resolve blockers, impediments and execute mitigation plans to remove dependencies and enable delivery of user stories

18) Identify and accurately map data sources for all the data needed to accomplish the business functionality being developed; ensure data coming from the correct source

19) Comply with Section 508 requirements

20) Provide Government visibility to the architecture, design, and development artifacts within the agile development tool(s)

21) Manage technical debt

a. Implement software in a manner that does not add new technical debt to a release and accounts for supportability in the architecture and design, including proactively raising Government awareness of technical debt based on BPR and evolving designs

b. Identify technical debt throughout development and testing, to include functional and technical impact and develop remediation actions

c. Perform assessments (e.g., code assessments) to ensure quality implementation and remediate technical debt associated with findings such as obsolete profiles, unused data fields / objects, and non-executable code

d. Interface Development Interface Development – Develop / configure interfaces with other systems to allow the AIE to send and receive data electronically over the Government network; maintain data integrity; ensure compliance with standards

e. Compliance

22) Meet the following compliance requirements: Clinger Cohen Act (CCA), Authority to Operate (ATO), Authority to Connect (ATC), Privacy Impact Assessment (PIA), Privacy Threshold Analysis (PTA), Security Impact Assessment, and ABEA

a. Requirements / Capability Management and Traceability

April 8, 2024 20

23) Adhere to the requirements management and traceability process, procedures, and tools as described in the ASDP

24) Prepare and provide Government visibility to capability completeness and traceability via a Requirements / Capability Traceability Matrix (RTM) within the agile development tool(s), for example: Value Stream à Epic à Feature Group à Feature à User Story à Test Case

25) Synchronize requirements traceability with the AIE Product Manager (PdM); the AIE PdM will update and maintain the AIE Master RTM within the AIE PdM tools

a. Configuration and Change Management

26) Develop and implement a Configuration and Change Management Plan (CCMP) that details the configuration management and change management processes, procedures, and tools to manage the AIE solution, and ensures system integrity while changes are made to the system; ensure alignment with the AIE baseline process used at the production level.

27) Maintain an AIE Configuration Management (CM) repository identifying the system configurations that identifies the state of the system, and all documentation related to the configuration and system baseline artifacts as they are updated over time; ensure alignment with the AIE baseline repository used at the production level

28) Support all necessary changes, to include changes to the Definition of Done, Acceptance Criteria, and any other items deemed necessary as well as coordinating and executing a Change Request Impact Assessment (to include estimated cost and schedule impact) for any Change Request and for processing and documenting all changes made as a result of a change proposal or system upgrade

29) Support the conduct of the Functional Configuration Audit (FCA) and Physical Configuration Audit (PCA), and participate in the resolution of discrepancies and successful completion of both FCA and PCA before establishing the solution baseline

30) Release and Deployment Management

a. Perform release and deployment management process aligned with the AIE release management process to release AIE functionality to the AIE PROD environment.

b. Maintain a continuous log of all releases and ensure all releases have the necessary packaged documentation

c. Post all release documentation to the AIE Baseline CM repository

d. Provide evidence that the functionality to be released has been tested through integration and the defects are dispositioned as acceptable for release

e. Establish a Definition of Ready and ensure compliance with the Definition of Ready for each release

April 8, 2024 21

31) Integration, Test and Evaluation

a. Develop and maintain a Capability and Integration and Test Plan that encompasses AIE integration and test and evaluation activities, to include clearly defined:

b. integration roles and responsibilities, process and procedures, activities to be performed, products and documentation, required resources, dependencies regarding the AIE production baseline, coordination actions, and integration metrics and associated reporting

c. test and evaluation roles and responsibilities, types of tests to be conducted and when, test events, required test resources, test dependencies, coordination actions, test metrics and associated reporting, and test reports

d. Perform testing at the levels necessary to ensure all AIE requirements have been met, and confirm that the functionality under test meets the acceptance criteria and performs the business processes as required by the user community

e. Ensure that the Definition of Done incudes conduct of testing and associated test results

f…