IPPS-A Army Military Payroll PWS - DRAFT - 3 JAN 2024.pdf

CUI

Integrated Personnel and Pay System – Army

(IPPS-A)

Army Military Payroll

Performance Work Statement (PWS)

DRAFT

W91CRB-24-R-0003

January 2024

Prepared by:

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

THIS PAGE INTENTIONALLY LEFT BLANK 14

iii

Table of Contents 17

1.0 Introduction ......................................................................................................... 1 18

1.1 Description of Services ...................................................................................... 1 19

1.2 IPPS-A Description ............................................................................................. 3 20

1.2.1 Background .............................................................................................. 3 21

1.2.2 IPPS-A Overarching Objectives ............................................................... 4 22

1.2.3 Army Military Payroll Description .............................................................. 5 23

1.3 Scope ................................................................................................................... 7 24

1.4 Period of Performance ....................................................................................... 8 25

1.5 Contract Type ..................................................................................................... 8 26

1.6 General Information Requirements ................................................................... 9 27

1.6.1 Quality Control and Assurance ................................................................. 9 28

1.6.2 Recognized Federal Holidays ................................................................. 10 29

1.6.3 Hours of Operation ................................................................................. 10 30

1.6.4 Place of Performance ............................................................................. 10 31

1.6.5 Security Requirements ........................................................................... 11 32

1.6.6 Contracting Officer’s Representative (COR) .......................................... 15 33

1.6.7 Agile Qualifications ................................................................................. 16 34

1.6.8 Key Personnel ........................................................................................ 16 35

1.6.9 Contractor Key Personnel Replacement ................................................ 23 36

1.6.10 Identification of Contractor Employees ................................................... 24 37

1.6.11 Contractor Travel .................................................................................... 24 38

1.6.12 Other Direct Costs (ODCs) ..................................................................... 24 39

1.6.13 Organizational Conflict of Interest (OCI) ................................................. 24 40

1.6.14 Government Rights ................................................................................ 25 41

1.6.15 Contractor Manpower Reporting ............................................................ 25 42

2.0 Reference Materials .......................................................................................... 25 43

3.0 Government Furnished Property (GFP), Items, and Services ...................... 26 44

3.1 Equipment (GFE), Facilities, and Supplies ..................................................... 26 45

3.2 Hardware, Software, and Technology Services and Materials ..................... 26 46

4.0 Contractor Furnished Items ............................................................................. 27 47

5.0 Performance Requirements – Specific Tasks ................................................ 27 48

5.1 Task 1: Program Management ........................................................................ 27 49 iv

5.1.1 Transition In ............................................................................................ 31 50

5.2 Task 2: Solution Configuration, Development, and Test ............................. 32 51

5.3 Task 3: Solution Integration ........................................................................... 40 52

5.4 Task 4: Release and Deployment .................................................................... 43 53

5.5 Task 5: Government Software Reuse Integration .......................................... 44 54

5.6 Task 6: Training Material Development .......................................................... 44 55

5.7 Task 7: Production Operations Transition ..................................................... 45 56

5.8 Task 8: Training Delivery [OPTIONAL] ........................................................... 47 57

6.0 Deliverables ...................................................................................................... 47 58

6.1 Deliverable Procedures .................................................................................... 47 59

6.2 Data and Data Rights ....................................................................................... 49 60

6.3 Deliverables Schedule ..................................................................................... 49 61

Appendix A: Reference Materials .......................................................................... 53 62

Appendix B: List of References ............................................................................. 61 63

List of Figures 66

Figure 1. AMP Notional Capability Groupings by Category ............................................. 5 67

Figure 2. AMP Notional Capability Groupings by Component Population ....................... 6 68

Figure 3. Notional 12-week PI ......................................................................................... 6 69

Figure 4. Business Process Mapping to Capabilities ...................................................... 7 70

List of Tables 73

Table 1. Deliverables List .............................................................................................. 49 74

Table 2. PWS References ............................................................................................. 61 75

1.0 Introduction 78

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

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

For this contract, Agile execution is defined as a group of software methods (e.g., 90 Scrum, Kanban, SAFe®) based on iterative and incremental development and 91 deployment of software capabilities for end users, where requirements and solutions 92 evolve through collaboration between cross-functional teams. These teams include the 93 Government and Contractor communities working across parallel environments where 94 capabilities are implemented, and production system product operations (previously 95 known as capability support) is ongoing. 96

Contractors will apply and perform Agile execution in varying degrees to all aspects of 97 the program life cycle across and within key activities. This includes applying agile 98 methodologies where applicable within the agile processes to perform the following 99 activities: requirements analysis, elicitation, elaboration, and decomposition; 100 architecture; design; development, implementation; test; integration; training material 101 development; and deployment, in addition to support functions such as program 102 management (planning, reporting), configuration management, change control, release 103 management, quality assurance, and cybersecurity. 104

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

1.1 Description of Services 108

The Contractor will provide all personnel, supervision, and other items and non-personal 109 services necessary (except for those specified as Government Furnished in Section 3 of 110 this document) to perform the IPPS-A AMP services, as defined in this Performance 111 Work Statement (PWS). 112

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

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

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

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

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

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

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

1.2 IPPS-A Description 166

1.2.1 Background 167

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

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

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

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

PeopleSoft HCM 9.2 190

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

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

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

PeopleSoft Tools version 8.60 (or higher) 196

Oracle database 19c version 12.2.0.3 (or higher) 197

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

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

1.2.2 IPPS-A Overarching Objectives 205

Overall IPPS-A program objectives include: 206

Provide incremental releases based on Agile execution and DevSecOps using 207 automated CI/CD pipelines, aligned with the IPPS-A production baseline 208 architecture and processes 209

Use Agile development methods, where functional and technical development 210 team members and the Army collaborate daily 211

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

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

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

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

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

Subsume applicable legacy systems and eliminate interfaces 225

Reduce point-to-point interfaces 226

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

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

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

Allow for future Machine Language and Artificial Intelligence utilization 236

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

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

Apply Human Centered Design techniques to improve the user experience 240

Improve Return on Investment and lower total cost of ownership 241

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

1.2.3 Army Military Payroll Description 244

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

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

Figure 2 250

Figure 1. AMP Notional Capability Groupings by Category 252

Figure 2. AMP Notional Capability Groupings by Component Population 255

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

Figure 3. Notional 12-week PI 262

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

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

4500+ Pay business rules 267

178 Pay elements defined in PeopleSoft Global Pay 268

369 total Pay elements defined 269

90 Pay scenarios 270

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

Figure 4. Business Process Mapping to Capabilities 276

For a complete of the AMP Requirements, see Reference 004 (Reference 004 - 277 IPPS-A AMP Functional Requirements List.xls). 278

For a description of the AMP Business Process Maps, Format Identifiers (FID) 279 Transaction Identification Numbers (TINs), Interfaces, and Pay Elements, see 280 Reference 005 (Reference 005 - IPPS-A AMP Business Process Maps - Interfaces - 281 Pay Data.zip). 282

1.3 Scope 283

The Army requires the following services to deliver an AMP solution as follows: (1) 284 manage, (2) design, configure, build, and test, (3) integrate and test the AMP solution 285 with the IPPS-A production baseline in the integration environment, (4) support AMP 286 release and deployment activities, (5) assess Government software for reusability, (6) 287 develop AMP training material, and (7) transition AMP functionality to production 288 operations. 289

These services will be acquired across the following tasks: 290

Task 1: Program Management 291

Task 2: Solution Configuration, Development, and Test 292

Task 3: Solution Integration 293

Task 4: Release and Deployment Support 294

Task 5: Government Software Reuse Integration 295

Task 6: Training Material Development 296

Task 7: Production Operations Transition / Transition Out 297

Task 8: Training Delivery [OPTIONAL] 298

1.4 Period of Performance 299

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

The Base Period begins on the designated date defined at contract award. PI Periods 306 begin when exercised by the Government in concert with the Program Roadmap 307 maintained by the Contractor and concurred with by the Government. Contractor 308 performance will be monitored, and results will be reviewed when deciding to exercise a 309 PI Period. 310

1.5 Contract Type 311

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

1.5.1 Expedited Delivery and Enhanced Performance 315

The Government may utilize a Firm-Fixed Price (FFP) Expedited Delivery and 317 Enhanced Performance CLIN on a delivery order to encourage delivery of the AMP total 318 solution. The Government anticipates ordering this CLIN, when determined applicable 319 and appropriate, and in conjunction with a single PI. The total ceiling value of the FFP 320 CLIN is based upon a capped FFP amount. No more than one (1) FFP CLIN will be 321 issued per one (1) PI ordered. 322 This FFP CLIN is associated with individual Planning Intervals (PI) and is payable to the 324 contractor after the completion of a PI. The contractor shall meet or exceed the “Very 325 Good” performance standard(s) for all performance metrics selected for the associated 326 PI. The Government reserves the right to unilaterally cancel the FFP CLIN and de-327 obligate all funding under this CLIN, if the contractor does not meet all performance 328 metrics. The Contractor shall not be entitled to payment if the metrics do not meet the 329 minimum threshold of “Very Good”. Cancellation of this CLIN will not negatively impact 330 the contractor’s CPARs rating. 331 Metrics may include all or a combination of the below performance metrics, which are 333 outlined in the Performance Requirement Summary of the QASP. 334

Story Point Completion Rate (Predictability) 336

Story Point Velocity 337

Delivered Value (Business Value Delivered) 338

Software Quality - Defect Density 339

Cost Performance 340

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

1.6 General Information Requirements 344

1.6.1 Quality Control and Assurance 345

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

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

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

The Government will evaluate the Contractor’s performance in accordance with the 353 IPPS-A AMP Quality Assurance Surveillance Plan (QASP) (see Attachment 1). The 354 QASP describes the performance levels the Contractor must achieve to satisfy the 355 contract performance requirements. The Contractor shall meet the threshold 356 requirements outlined in the QASP Performance Requirements Summary (PRS) to 357 receive a Satisfactory rating in the monthly Contracting Officer’s Representative (COR) 358 report and annual Contractor Performance Assessment Report (CPAR). The 359 Contractor shall report performance against the measures / metrics outlined in the 360 QASP during program reviews per the cadence established between the Government 361 and Contractor. The report must show the current and previous two months. If the 362 Contractor fails to meet any QASP measure/metric, the Government will notify the 363 Contractor through the Contracting Officer and will require a response within five (5) 364 business days of receipt of the official notice by the Contracting Officer describing their 365 corrective action plan to meet the QASP measure/metric. If the Contractor is unable to 366 meet the threshold requirement, the Government may decide to not award subsequent 367 options to the Contractor. 368

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

1.6.2 Recognized Federal Holidays 373

New Year’s Day 374

Martin Luther King Jr.’s Birthday 375

Presidents Day 376

Memorial Day 377

Juneteenth National Independence Day 378

Independence Day 379

Labor Day 380

Columbus Day 381

Veteran’s Day 382

Thanksgiving Day 383

Christmas Day 384

1.6.3 Hours of Operation 385

The Contractor shall be responsible for conducting normal operations between the 386 hours of 8am to 5pm Monday thru Friday, core hours being 9am to 3pm Monday 387 through Friday except for Federal Holidays, Government closure due to local or national 388 emergencies, administrative closings, or similar Government directed facility closings. 389 Contractor personnel identified as key personnel and/or leads shall be available 390 between the hours of 8am to 5pm Monday thru Friday. 391

1.6.4 Place of Performance 392

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

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

VA 22202. 404

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

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

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

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

1.6.5 Security Requirements 418

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

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

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

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

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

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

1.6.5.1 Authorities and Scope 439

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

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

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

1.6.5.2 Security Requirements for Overseas Travel 463

For travel requirements/restrictions to any foreign country, see the Foreign Clearance 464 Guide (FCG) at the following website for applicable information: 465 https://www.fcg.pentagon.mil/fcg.cfm 466

1.6.5.3 Physical Security 467

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

1.6.5.4 Disclosure of Information 471

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

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

Request for approval will identify the specific information to be released, the medium to 484 be used, and the purpose for the release. The Contractor will submit its request to the 485

COR at least forty-five (45) days before the proposed date for the release. The 486 Contractor shall include a similar requirement in each subcontract under this contract. 487 Subcontractors will submit requests for authorization to release through the prime 488 Contractor to the COR. The Contractor's procedures for protecting against unauthorized 489 disclosure of information shall not require DoD employees or Armed Forces (AF) 490 members to relinquish control of their work product, whether classified or not, to the 491 Contractor. 492

1.6.5.5 Visiting Facilities 493

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

1.6.5.6 Key Control 503

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

a. In the event keys, other than master keys, are lost or duplicated, the Contractor 512 will, upon the direction of the COR, re-key or replace the affected lock or locks; 513 however, the Government, at its option, may replace the affected lock or locks or 514 perform re-keying. When the replacement of locks or re-keying is performed by 515 the Government, the total cost of re-keying or the replacement of the lock or 516 locks will be deducted by the Government from the monthly payment due the 517 Contractor. In the event a master key is lost or duplicated, all locks and keys for 518 that system will be replaced by the Government and the total cost will be 519 deducted by the Government from the monthly payment due the Contractor. 520

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

1.6.5.7 Lock Combinations 526

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

1.6.5.8 Security Education Training and Awareness (SETA) 530

All DA SETA requirements identified in this PWS are applicable to all of DoD and Army 531 (military, civilian and Contractor) personnel performing services on the IPPS-A contract 532 and IPPS-A integrated portfolio efforts in accordance with DoDM 5220.22, DoDM 533

5200.01 Volume 1-3, DoDI 5200.48, Army Regulation (AR) 350-1, AR 380-12, AR 25-2, 534 and DA Pamphlet (PAM) 25-2-6. 535

1.6.5.9 Special Qualifications 536

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

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

The Contractor will ensure the following: 545

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

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

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

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

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

4) Previously completed security investigations may be accepted by the 562 Government in lieu of new investigations if determined by the PEO EIS 563 security office to be essentially equivalent in scope to the PWS 564 requirements. The length of time elapsed since the previous investigation 565 will also be considered in determining whether a new investigation is 566 warranted. To assist the Government in making this determination, the 567 Contractor must provide the following information to the respective PEO 568 EIS security office. This information must be provided for each Contractor 569 employee who will perform work on a PEO EIS system and will require 570 access to Federally-controlled information systems: 571 Full name, with middle name, as applicable, with social security 572 number 573 Citizenship status with date and place of birth 574 Proof of the individual’s favorable adjudicated background 575 investigation or NACI, consisting of identification of the type of 576 investigation performed, date of the favorable adjudication, and 577 name of the agency the performed the investigation 578

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

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

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

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

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

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

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

1.6.6 Contracting Officer’s Representative (COR) 602

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

1.6.7 Agile Qualifications 616

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

1.6.8 Key Personnel 621

Key personnel are those people considered essential to successful Contractor 622 performance. All key personnel must be on board at contract award. The Contractor will 623 not replace any personnel designated as key personnel without providing written notice 624 to the Contracting Officer and COR at least 48 hours upon Contractor receipt of a 625 voluntary notice or Contractor decision to replace personnel. The notice will provide a 626 detailed explanation of the circumstances necessitating the substitution. Qualifications 627 of substitute key personnel shall be equal to, or greater than, those of the person(s) 628 being replaced. 629

The Contractor shall provide key personnel that are commensurate with leading large-630 scale and complex programs. 631

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

1.6.8.1 Program Manager (PM) 634

The Contractor shall assign an individual to serve as a Program Manager (PM) for this effort. 635 This individual will have a strong understanding of program and project management principles 636 and methodologies. This individual will be the single point of contact for the Government Task 637 Monitor (GTM) and COR. The PM will be responsible for the performance of the work. The 638 name of this person and an alternate, who will act for the Contractor when the PM is absent, 639 will be designated in writing to the Contracting Officer. The Contractor PM and alternate will 640 have full authority to act for the Contractor on all matters relating to daily operation of this 641 contract. The Contractor PM or alternate will be available in accordance with paragraph 1.6.3 642 Monday through Friday except Federal holidays or when the Government facility is closed for 643 administrative reasons. 644

The PM will have the following experience and qualifications: 645

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

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

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

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

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

f. Experience with researching and fielding new and innovative technology 656

g. Experience with software procurement 657

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

i. IT experience in the Federal, DoD, Army, or IC 661

j. Project Management Professional Certification required 662

k. Agile Project Manager Certification required 663

l. Agile Product Owner Certification preferred 664

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

Key Responsibilities include: 668

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

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

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

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

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

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

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

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

1.6.8.2 PeopleSoft Global Payroll Solution Engineer 690

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

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

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

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

c. Experience configuring…