Attachment 1 - IPPS-A Army Military Payroll Performance Work Statement (PWS)_AMD 0002.pdf

CUI

Integrated Personnel and Pay System – Army

(IPPS-A)

Army Military Payroll

Performance Work Statement (PWS)

W91CRB-24-R-0003

January 2024

Prepared by:

IPPS-A Product Manager (PdM) Future Capabilities Office ii

THIS PAGE INTENTIONALLY LEFT BLANK

iii

Table of Contents

1.0 Introduction

1.1 Description of Product

1.2 IPPS-A Description

1.2.1 Background

1.2.2 IPPS-A Overarching Objectives

1.2.3 Army Military Payroll Description

1.3 Scope

1.4 Period of Performance

1.5 Contract Type

1.5.1 Expedited Delivery and Enhanced Performance

1.6 General Information Requirements

1.6.1 Quality Control and Assurance

1.6.2 Recognized Federal Holidays

1.6.3 Hours of Operation

1.6.4 Place of Performance

1.6.5 Security Requirements

1.6.6 Contracting Officer’s Representative (COR)

1.6.7 Agile Qualifications

1.6.8 Key Personnel

1.6.9 Contractor Key Personnel Replacement

1.6.10 Identification of Contractor Employees

1.6.11 Contractor Travel

1.6.12 Other Direct Costs (ODCs)

1.6.13 Organizational Conflict of Interest (OCI)

2.0 Reference Materials

3.0 Government Furnished Property (GFP) / Contractor Acquired Property (CAP), Services, and Materials

3.1 GFP / CAP (Equipment (GFE), Facilities, 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

iv

5.0 Performance Requirements – Specific Tasks

5.1 Task 1: Program Management

5.1.1 Transition In

5.2 Task 2: Solution Configuration, Development, and Test

5.3 Task 3: Solution Integration

5.4 Task 4: Release and Deployment

5.5 Task 5: Government Software Reuse Integration

5.6 Task 6: Training Material Development

5.7 Task 7: Production Operations Transition

5.8 Task 8: Training Delivery [OPTIONAL]

6.0 Deliverables

6.1 Deliverable Procedures

6.2 Data and Data Rights

6.3 Deliverables Schedule

Appendix A: Reference Materials

Appendix B: List of References

List of Figures

Figure 1. AMP Notional Capability Groupings by Category

Figure 2. AMP Notional Capability Groupings by Component Population

Figure 3. Notional 12-week PI

Figure 4. Business Process Mapping to Capabilities

List of Tables

Table 1. Deliverables List

Table 2. PWS References

Table 3. Solicitation PWS References

1.0 Introduction

This is a contract to develop an Army Military Payroll (AMP) total solution using the Oracle PeopleSoft Global Payroll application. The Army launched the Integrated Personnel and Pay System – Army (IPPS-A) Increment II (Inc II) production baseline for Human Resources (HR) processing in December 2022 utilizing PeopleSoft Human Capital Management (HCM). The new AMP capability will be integrated with the IPPS-A production baseline.

The development will consider (1) Agile execution combined with Development, Security, and Operations (DevSecOps) for all activities / tasks to allow for Continuous Integration / Continuous Delivery (CI/CD) and compliance with the Continuous Risk Management Framework (cRMF), (2) task automation to reduce / eliminate manual effort, and (3) innovation and creativity in problem-solving.

For this 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 through collaboration between cross-functional teams. These teams include the Government and Contractor communities working across parallel environments where capabilities are implemented, and production system product operations (previously known as capability support) is ongoing.

Contractors will apply and perform Agile execution in varying degrees to all aspects of the program life cycle across and within key activities. This includes applying agile methodologies where applicable within the agile processes to perform the following activities: requirements analysis, elicitation, elaboration, and decomposition;

architecture; design; development, implementation; test; integration; training material development; and deployment, in addition to support functions such as program management (planning, reporting), configuration management, change control, release management, quality assurance, and cybersecurity.

The Government will not exercise any supervision or control over the Contractor personnel developing the resulting AMP total solution. Such Contractor personnel shall be accountable solely to the Contractor who, in turn, is responsible to the Government.

1.1 Description of Product

The Contractor will provide all personnel, supervision, and other items (except for those specified as Government Furnished in Section 3 of this document) to develop and deliver the IPPS-A AMP total solution, as defined in this Performance Work Statement

(PWS).

Agile and DevSecOps methodologies will apply for incremental and value-added delivery from requirements analysis / elaboration and business process reengineering (BPR), through architecture, design, development, implementation, and testing, to integration with the IPPS-A production baseline with minimum cybersecurity vulnerabilities.

Integration with the IPPS-A production baseline will be performed with the IPPS-A Product Operations Team. The IPPS-A Product Operations Team is responsible for the integration, baseline testing, cybersecurity compliance, release, and deployment of functionality into the IPPS-A production baseline for operational use. The Contractor will be required to synchronize tasks and associated activities with the IPPS-A Product Operations Team and participate in agile teams, where applicable, to ensure smooth integration of AMP functionality into the IPPS-A production baseline.

The Government will provide the development environment(s) to support Contractor development activities. Each environment will contain the IPPS-A baseline and associated software applications and tools (see Solicitation PWS Reference 001 - IPPS- A Software Baseline Applications and Tools.xls). The Government will not restrict the Contractor to only using these applications and tools. The Contractor may implement additional applications and tools, with justification and Government approval, within the Government environments. Additional applications and tools that the Contractor implements must align with the IPPS-A applications and tools so when the AMP software is promoted to the IPPS-A integration environment, the IPPS-A tools will function properly with the AMP software. The Government will give the Contractor access as to the IPPS-A applications and tools at the level necessary to perform the required work. The Contractor will give the Government access to all applications and tools within the environments used by the Contractor to allow Government visibility into all components.

The IPPS-A Project Management Office (PMO) has yet to establish a DevSecOps pipeline. The Contractor is required to align with the IPPS-A environments and processes in place, to include security policies within the IPPS-A production baseline, and as they progress to a DevSecOps pipeline.

The Government will provide the Integration environment and associated tools to support the integration and test of the AMP functionality into the IPPS-A production baseline for release. The IPPS-A Product Operations Team will administer and maintain the Integration environment, will ensure the currency of the IPPS-A baseline, tools, and test data in that environment based on an agreed upon cadence, and will support the Contractor activities in that environment, such as incremental testing and cybersecurity scans. Likewise, the Contractor will support the IPPS-A Product Operations Team baseline activities in that environment to ensure readiness of the AMP functionality for release.

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

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

1.2 IPPS-A Description

1.2.1 Background

IPPS-A Inc II is both a Defense Business System and a National Security System (categorized as "Sensitive Activities") based on operational requirements on the Non-secure Internet Protocol Router Network (NIPRNet) and Secure Internet Protocol Router Network (SIPRNet). IPPS-A is under the Milestone Decision Authority (MDA) of the Army Acquisition Executive (AAE). It is managed by the Army Program Executive Office Enterprise Information Systems (PEO EIS), Project Manager (PM) IPPS-A, located in Arlington, VA. PEO EIS develops, acquires, and deploys tactical and management Information Technology (IT) systems and products and is a Systems Acquisition, Development, and Integration Center of Excellence.

The IPPS-A Inc II mission is to develop and deliver a single, integrated, multi-component HR and Army Military Payroll system that streamlines Army HR and military pay, enhances the efficiency and accuracy of Army Personnel and Pay procedures, and supports Soldiers and their families.

IPPS-A Inc II is being developed and deployed incrementally in a series of software releases to the Total U.S. Army Force (Active Army, Army National Guard, and Army Reserves). A major software release was completed in January 2023, providing Military HR capabilities, and bringing the Total U.S. Army Force into a single authoritative system. This software release serves as the IPPS-A production baseline and is in the Capability Support phase.

The IPPS-A production baseline primarily uses Oracle PeopleSoft Enterprise Resource Planning (ERP) Commercial-Off-The-Shelf (COTS) software to deliver the functionality, consisting of the following applications:

PeopleSoft HCM 9.2

PeopleSoft HCM 9.2 Peoplesoft Update Manager (PUM) Image 47 (or higher)

PeopleSoft Customer Relationship Management (CRM) 9.2 PUM Image 16 (or higher)

PeopleSoft Enterprise Learning Management (ELM) 9.2 PUM Image 17 (or higher)

PeopleSoft Tools version 8.60 (or higher)

Oracle database 19c version 12.2.0.3 (or higher)

Additional Oracle products, along with Ab Initio, OBIEE Stonebranch, Apache Kafka Confluent, and Cameo software products comprise the baseline. See Solicitation PWS Reference 001 (Solicitation PWS Reference 001 - IPPS-A Software Baseline Applications and Tools.xlsx) for a complete list of IPPS-A software products.

The IPPS-A solution and all its environments are currently hosted on-premises with the Defense Information Systems Agency (DISA). See Solicitation PWS Reference 002 (Solicitation PWS Reference 002 - IPPS-A Technical Environment Designs.pdf) for a description of the IPPS-A hardware.

1.2.2 IPPS-A Overarching Objectives

Overall IPPS-A program objectives include:

Provide incremental delivery using automated CI/CD pipelines, aligned with the IPPS-A production baseline architecture and processes

Integrate unit, regression, and security testing with each build / deploy cycle

Use DevSecOps structure, where functional, security, and technical staff members are embedded with each team and collaborate daily

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

Provide complete visibility of the Total Force in one system for over 1 million Soldiers

Enable the Army to better manage the talents of the Total Force based on their Knowledge, Skills, and Behaviors (KSBs) to optimize Soldiers’ contributions to Army Readiness

Deliver full audit compliance for pay, benefits, and HCM transactions per the Federal Information Systems Control Audit Manual (FISCAM) and National Institute of Standards and Technology (NIST) guidelines.

Improve Soldiers’ lives by reducing pay and personnel errors and providing full transparency of actions

Subsume applicable legacy systems and eliminate interfaces

Reduce point-to-point interfaces

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

Execute HR Transformation, Army Military Payroll Transition and Business Process Reengineering in conjunction with fielding IPPS-A to create a 21st century Talent Management system and a HR data-rich environment

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

Allow for future Machine Learning and Artificial Intelligence utilization

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

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

Apply Human Centered Design techniques to improve the user experience

Improve Return on Investment and lower total cost of ownership

The objective of this contract is to develop an AMP solution using the Oracle PeopleSoft Global Payroll application, which will be integrated with the IPPS-A production baseline.

1.2.3 Army Military Payroll Description

For planning purposes, Army Military Payroll capabilities have been notionally grouped in two ways as follows; however, these are not deemed to be the only means to achieve an AMP solution:

Five (5) main development and release categories as depicted in Figure 1 Three (3) incremental releases based on population by component as depicted in

Figure 2

Figure 1. AMP Notional Capability Groupings by Category

Figure 2. AMP Notional Capability Groupings by Component Population

In addition, the Government has developed a notional Planning Interval (PI) Model to for each notional grouping that depicts the sequencing and evolution of functionality across a series of 12-week PIs (see Solicitation PWS Reference 003 (Solicitation PWS Reference 003 - IPPS-A AMP PI Notional Plan and PI 1-3.pdf). Figure 3 provides a depiction of a notional 12-week PI.

Figure 3. Notional 12-week PI

As part of the IPPS-A baseline development effort, the following potential payroll capabilities have been identified and may be included in the future production baseline:

22 pay triggers for items such as absences, jobs, benefits, and special pay requests

4500+ Pay business rules

178 Pay elements defined in PeopleSoft Global Pay

369 total Pay elements defined

90 Pay scenarios

Figure 4 depicts the alignment of capabilities to business process maps. The accounting integration capabilities listed below are linked to maps and requirements that reflect IPPS-A operating as a financial feeder system rather than serving as a subledger. The Army is reviewing this approach and may shift to a subledger approach.

Figure 4. Business Process Mapping to Capabilities

For a complete list of the AMP Requirements, see PWS Reference 001 (PWS Reference 001 - IPPS-A AMP Functional Requirements List.xls).

For a description of the AMP Business Process Maps, Format Identifiers (FID) Transaction Identification Numbers (TINs), Interfaces, and Pay Elements, see Solicitation PWS Reference 004 (Solicitation PWS Reference 004 - IPPS-A AMP Business Process Maps - Interfaces - Pay Data.zip).

1.3 Scope

The Army requires the following to deliver an AMP total solution as follows: (1) manage,

(2) design, configure, build, and test, (3) integrate and test the AMP solution with the IPPS-A production baseline in the integration environment, (4) support AMP release and deployment activities, (5) assess Government software for reusability, (6) develop AMP training material, and (7) transition AMP functionality to production operations.

The AMP total solution will encompass the following tasks:

Task 1: Program Management / Transition In

Task 2: Solution Configuration, Development, and Test

Task 3: Solution Integration

Task 4: Release and Deployment Support

Task 5: Government Software Reuse Integration

Task 6: Training Material Development

Task 7: Production Operations Transition / Transition Out

Task 8: Training Delivery [OPTIONAL]

1.4 Period of Performance

The period of performance for this contract is up to seven (7) years. The performance will primarily consist of Program Management Contract Line Item Numbers (CLINs) and a series of 12-week Planning Intervals (PIs) for agile software development under an overarching CLIN. The Program Management CLIN will have an initial duration of twelve (12) months with continued performance every six (6) months thereafter as Option Periods through contract duration.

The Base Period begins on the designated date defined at contract award. PI Periods begin when exercised by the Government in concert with the Product 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 a PI Period.

1.5 Contract Type

This is a Hybrid Single Award Indefinite Delivery / Indefinite Quantity (IDIQ) contract that include Firm Fixed Price (FFP), Cost Plus Fixed Fee (CPFF) Level of Effort (LOE), CPFF Completion, and Cost Reimbursable (no fee) line items for Travel and Other Direct Costs (ODCs).

1.5.1 Expedited Delivery and Enhanced Performance

The Government may utilize a FFP Expedited Delivery and Enhanced Performance CLIN on a delivery order (DO) to encourage delivery of the AMP total solution. The Government anticipates ordering this CLIN, when determined applicable and appropriate, and in conjunction with a single PI. The total ceiling value of the FFP CLIN is based upon a capped FFP amount. No more than one (1) FFP CLIN will be issued per one (1) PI ordered.

This FFP CLIN is associated with individual PIs and is payable to the Contractor after the completion of a PI. The Contractor shall meet or exceed the “Very Good” performance standard(s) for all performance metrics selected for the associated PI. The Government reserves the right to unilaterally cancel the FFP CLIN and de-obligate all funding under this CLIN if the Contractor does not meet all performance metrics. The

Contractor shall not be entitled to payment if the quality level of the selected metrics does not at least meet the minimum threshold of “Very Good”. Cancellation of this CLIN will not negatively impact the Contractor’s CPARS rating.

Metrics may include all or a combination of the below performance metrics, which are outlined in the Performance Requirement Summary of the Quality Assurance Surveillance Plan (QASP) (Contract Attachment 2).

Story Point Completion Rate (Predictability)

Story Point Velocity

Delivered Value (Business Value Delivered)

Software Quality - Defect Density

Cost Performance

The Government reserves the right to add or revise the above performance metrics throughout contract performance.

1.6 General Information Requirements

1.6.1 Quality Control and Assurance

The Contractor will maintain an effective quality control program to ensure development is performed as agreed to in the contract. This will include the following:

Updating and implementing procedures to identify, prevent, and ensure the non-recurrence of non-conformance, to include products and software

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

The Government will evaluate the Contractor’s performance in accordance with the IPPS-A AMP QASP (Contract Attachment 2). The QASP describes the performance levels the Contractor must achieve to satisfy the contract performance requirements.

The Contractor shall meet the threshold requirements outlined in the QASP Performance Requirements Summary (PRS) to receive a Satisfactory rating in the monthly Contracting Officer’s Representative (COR) report and annual Contractor Performance Assessment Report (CPAR). The Contractor shall report performance against the measures / metrics outlined in the QASP during program reviews per the cadence established between the Government and Contractor. The report must show the current and previous two months. If the Contractor fails to meet any QASP measure/metric, the Government will notify the Contractor through the Contracting Officer and will require a response within five (5) business days of receipt of the official notice by the Contracting Officer describing their corrective action plan to meet the QASP measure/metric. If the Contractor is unable to meet the threshold requirement, the Government may decide to not award subsequent options to the Contractor.

The Government will perform random After Action Reviews (AARs) at the PI and/or sprint level for up to 100% of the PIs exercised. This surveillance method is appropriate for a deliverable or performed service which will capture best practices, bottlenecks, and future PI/sprint development processes for implementation.

1.6.2 Recognized Federal Holidays

New Year’s Day

Martin Luther King Jr.’s Birthday

Presidents Day

Memorial Day

Juneteenth National Independence Day

Independence Day

Labor Day

Columbus Day

Veteran’s Day

Thanksgiving Day

Christmas Day

1.6.3 Hours of Operation

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

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

1.6.4 Place of Performance

The primary place of performance for unclassified activities will be at Contractor-designated and reported locations. All activities requiring Government participation (e.g., planning, demonstrations, reviews) will take place at the IPPS-A PMO facility, currently located at the Polk Building, 2521 South Clark Street, Arlington, VA 22202, unless otherwise determined based on the specific activity. For activities conducted at the IPPS-A PMO facility, the Government will provide hotel-type space for Contractor use. The Contractor facility may also be used for key events. Key events will be coordinated in advance to include associated logistics.

All work related to Sensitive Activities (SA) will be performed at the designated IPPS-A PMO secure area approved for classified discussion and work. The IPPS-A PMO secure area is currently located at the Polk Building, 2521 South Clark Street, Arlington, VA 22202.

In accordance with FAR 7.108, the Government does not discourage the Contractor from allowing its employees to telecommute/remote work/telework in performance of this contract. The listed sites are primary duty locations, however, the support required under this contract may be performed through remote and telework as mission allows.

The Contractor shall submit all requests for remote work and telework flexibilities to the COR for approval prior to implementation.

Contractor travel costs to and from their normal duty location, whether at the contractor's facilities or at the Government’s facilities, are not authorized and are unallowable costs. Travel between the Contractor facilities and Government facilities will not be reimbursed as a travel expense. For performance of this contract, outside the local area is defined as greater than 50 miles from the IPPS-A PMO facility.

1.6.5 Security Requirements

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

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

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

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

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

The Contractor will review DoD, DA, and PEO EIS specific instructions, security policies, procedures, training, and other requirements stipulated in the National Industrial Security Program (NISP) and National Industrial Security Program Operating Manual (NISPOM), and any supplements thereto are applicable, to include, the Federal Acquisition Regulation (FAR), Defense Federal Acquisition Regulation Supplement (DFARS), data usage agreements and memoranda of agreement, and security provisions and/or clauses.

1.6.5.1 Authorities and Scope

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

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

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

1.6.5.2 Security Requirements for Overseas Travel

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

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

1.6.5.3 Physical Security

The Contractor will be responsible for safeguarding all Government equipment, information and property provided for Contractor use. At the close of each work period, Government facilities, equipment, and materials shall be secured.

1.6.5.4 Disclosure of Information

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

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

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

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

1.6.5.5 Visiting Facilities

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

1.6.5.6 Key Control

The Contractor will establish and implement methods of making sure all keys / key cards issued to the Contractor by the Government are not lost or misplaced and are not used by unauthorized persons. NOTE: All references to keys include key cards. No keys issued to the Contractor by the Government will be duplicated. The Contractor will develop procedures covering key control that will be included in the Quality Control Plan (QCP). Such procedures will include turn-in of any issued keys by personnel who no longer require access to locked areas. The Contractor will immediately report any occurrences of lost or duplicate keys/key cards to the COR.

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

however, the Government, at its option, may replace the affected lock or locks or perform re-keying. When the replacement of locks or re-keying is performed by the Government, the total cost of re-keying or the replacement of the lock or locks will be deducted by the Government from the monthly payment due the Contractor. In the event a master key is lost or duplicated, all locks and keys for that system will be replaced by the Government and the total cost will be deducted by the Government from the monthly payment due the Contractor.

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

1.6.5.7 Lock Combinations

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

1.6.5.8 Security Education Training and Awareness (SETA)

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

1.6.5.9 Special Qualifications

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

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

The Contractor will ensure the following:

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

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

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

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

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

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

Full name, with middle name, as applicable, with social security number

Citizenship status with date and place of birth Proof of the individual’s favorable adjudicated background investigation or NACI, consisting of identification of the type of investigation performed, date of the favorable adjudication, and name of the agency the performed the investigation

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

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

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

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

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

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

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

1.6.6 Contracting Officer’s Representative (COR)

The COR will be identified by separate letter. The COR monitors all technical aspects of the contract and assists in administration. The COR is authorized to perform the following functions: assure that the Contractor performs the technical requirements of the contract; perform inspections necessary in connection with performance; maintain written and oral communications with the Contractor concerning technical aspects of the contract; issue written interpretations of technical requirements, including Government drawings, designs, specifications; monitor Contractor's performance and notify both the Contracting Officer and Contractor of any deficiencies; coordinate availability of Government Furnished Property (GFP); and provide site entry of Contractor personnel.

A letter of designation issued to the COR, a copy of which is sent to the Contractor, states the responsibilities and limitations of the COR, especially regarding changes in cost or price, and estimates or changes in delivery dates. The COR is not authorized to change any of the terms and conditions of the resulting contract.

1.6.7 Agile Qualifications

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

1.6.8 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 shall provide key personnel that are commensurate with leading large-scale and complex programs.

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

1.6.8.1 Program Manager (PM)

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

This individual will have a strong understanding of program and project management principles and methodologies. 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.6.3 Monday through Friday except Federal holidays or when the Government facility is closed for administrative reasons.

The PM will have the following experience and qualifications:

a. Knowledge in planning, directing, and managing projects/operations in an organization similar in size to this acquisition with at least managing two major software development implementations, to include agile development

b. Knowledge and supervision of employees of various labor categories and skills in efforts similar in size and scope as this acquisition

c. Knowledge of industry accepted standards and best practices related to Project Management

d. Proven track record on delivering on time and within budget for large/complex projects

e. Experience with managing the entire agile software development lifecycle, including frequent production delivery

f. Experience with researching and fielding new and innovative technology

g. Experience with software procurement

h. Experience with program management in either commercial, Federal, DoD, Army, Intelligence Community (IC), or State programs of similar scope and complexity to AMP;

Federal, DoD, or Army experience preferred

i. IT experience in in either commercial, Federal, DoD, Army, IC, or State programs of similar scope and complexity to AMP; Federal, DoD, or Army experience preferred

j. Project Management Professional (PMP) Certification (e.g., Program Management Institute (PMI)-PMP) required

k. Leading SAFe® Certification required

l. Agile Project Manager Certification desired (e.g., PMI Agile Certified Practitioner (ACP),

m. Agile Product Owner Certification desired

n. Bachelor’s degree in an IT, Business Administration or Program Management related field, or equivalent experience (minimum 12 years) with similar type of program

Key Responsibilities include:

a. Program Planning and Coordination: Develop program strategies and plans that align with the Government objectives; Coordinate various projects and teams within the program, ensuring that they complement and do not conflict with each other

b. Team Leadership and Development: Lead and mentor project managers and teams within the program; Foster a collaborative environment and encourage high performance and professionalism

c. Stakeholder Management: Serve as the primary point of contact for program stakeholders; Communicate program goals, objectives, and progress effectively to all stakeholders, including senior management, project teams, and external partners

d. Resource Management: Oversee the allocation and utilization of resources across projects to maximize efficiency and effectiveness

e. Risk Management and Problem Solving: Identify potential risks and issues within the program. Develop and implement strategies for mitigating risks and resolving issues

f. Performance Monitoring: Monitor and evaluate program performance using appropriate tools and techniques; Adjust program strategies as necessary to ensure successful outcomes; Ensure proficient or can quickly gain proficiency in project management software and tools utilized by the Government

g. Budget Management: Develop and manage program budgets; Ensure that program spending is in line with financial objectives and constraints

h. Quality Assurance: Ensure that program outputs meet quality standards and stakeholder expectations

1.6.8.2 PeopleSoft Global Payroll Solution Engineer

The Contractor shall assign an individual with the technical expertise and customer-facing skills to understand the Government needs, design and present technical solutions, and drive successful implementation. This individual will collaborate closely with various teams to ensure that the architecture aligns with business needs and IT strategy.

The PeopleSoft Global Payroll Solution Engineer will have the following experience and qualifications:

a. Proven experience of at least one full implementation with PeopleSoft Global Payroll and an understanding of PeopleSoft Global Payroll Business Processes, business rules (HR/Payroll) and how it integrates with HR, Time & Labor, PeopleSoft Financial Supply Chain Management (FSCM), and external general ledger systems.

b. Experience working with multiple teams composed of technical and functional analysts

c. Experience configuring business rules, and performing Configuration, Design and Development of PeopleSoft HR and Global Payroll

d. Development experience with PeopleTools (e.g., Application Designer, Component Interface, Application Engine, Integration Broker), and SQL

e. Experience translating Functional and Technical Requirements for implementation in a business system; experience in a defense system is desired

f. Experience interacting and presenting work to senior leadership

g. Experience working with Federal, or DoD/Military HR/Pay rules and requirements (e.g., Title 10, 32, etc.) is desired; Army relevant experience is preferred

h. Experience with General Fund Enterprise Business System (GFEBS) accounting and U.S. Treasury disbursement is desired

i. Experience with Enterprise Architecture Frameworks, such as The Open Group Architecture Framework (TOGAF) and the DoD Architecture Framework (DoDAF);

DoDAF experience is desired to ensure Army Business Enterprise Architecture (ABEA) compliance

j. Experience with data modeling tools such as IBM System Architect, CAMEO, ARIS, and MagicDraw to assist architects with DoDAF is desired

k. Experience with modern software development tools such as: GITLAB, SonarQube, HP ALM suite, and the Atlassian Suite is desired

l. Experience in commercial, Federal, DoD, Army, IC, or State programs of similar scope and complexity to AMP; Federal, DoD, or Army experience preferred

m. Bachelor of Science degree in Computer Science, Information Technology, or a related technical degree plus 10 years’ relevant experience in a technical solutions role, ideally with PeopleSoft HCM 9.0 or higher implementation experience and PeopleSoft 9.0 or higher Global Payroll technical analysis, design, configuration, implementation, and ERP integration experience; in place of the standard Bachelor of Science degree requirements in Computer Science, Information Technology, or a related field, candidates shall have at least twenty (20) years of direct, hands-on experience with PeopleSoft HCM and Global Payroll, including recent and relevant experience with version 9.0 or higher on both products; this experience should encompass comprehensive technical roles, including analysis, design, and configuration, supporting at least two (2) implementations and training in relevant PeopleSoft technologies; while possessing Oracle PeopleSoft certifications and academic degrees is beneficial, they are optional prerequisites for this role; Contractor must showcase substantial expertise in PeopleSoft solutions, evidenced by their professional experience

Key Responsibilities include:

a. Consultation and Needs Analysis: Engage with the Government to understand their business needs and technical challenges. Analyze requirements to develop effective solutions.

b. Solution Design and Presentation: Design solutions that align with Government needs and covers configuration, design and development of PeopleSoft Payroll rules engine and processing Framework; Effectively analyze and demonstrate business processing reengineering of legacy Business Processes in favor of PeopleSoft delivered capability;

Be able to engage with senior leaders and clearly articulate functional and technical requirements and the value and functionality of the AMP solution in presentations and demonstrations to the Government

c. Technical Support and Implementation Guidance: Provide ongoing support and guidance during the implementation of solutions; Address any technical challenges and ensure a smooth release and deployment process

d. Cross-functional Collaboration: Work closely with architecture team and engineering teams to ensure solution feasibility and to align on Government expectations

e. Feedback and Improvement: Collect Government feedback on solutions and work with internal teams to refine and enhance product offerings

f. Stay Informed on Industry Trends: Maintain up-to-date knowledge of industry trends, emerging technologies, and competitive landscape to enhance solution offerings

1.6.8.3 Release Train Engineer

The Contractor shall assign a Release Train Engineer (RTE) who will facilitate and guide the Agile Release Trains (ART). The RTE's primary responsibility is to ensure that the ART operates effectively and delivers value to the organization. This role requires a blend of Agile coaching, program management, and strong leadership skills. This individual must possess strong facilitation skills, must promote continual improvement, and must have the ability to coach and motivate teams, and address and resolve conflict.

The Release Train Engineer will have the following experience and qualifications:

a. Knowledge applying agile processes and tools on multiple large-scale IT-related development programs

b. Knowledge with at least two of the following Agile tools: JIRA, Confluence, Gitlab, Nexus, SonarQube, HP ALM suite

c. Strong understanding of software development lifecycle models

d. Knowledge of both Agile and traditional project management principles

e. Experience coaching and mentoring Agile Scrum teams

f. Experience in planning, managing, and implementing the entire agile software development lifecycle

g. Minimum of two IT development programs as RTE

h. Experience applying Agile processes and tools in commercial, Federal, DoD, Army, IC, or State programs of similar scope and complexity to AMP; Federal, DoD, or Army experience preferred

i. Agile Leader Certification preferred

j. SAFe® Release Train Engineer Certification or equivalent required

k. Experience with supporting an ERP program such as PeopleSoft HCM by applying Agile processes is desired

l. Bachelor’s degree in Business or a non-technical related field, or a Bachelor of Science degree in Computer Science, Engineering, or Information Technology plus 4 years’ relevant experience in technical…