Attachment 2 - IPPS-A AMP QASP - DRAFT - 25 OCT 2023.pdf

CUI

Integrated Personnel and Pay System – Army

(IPPS-A)

Army Military Payroll

Quality Assurance Surveillance Plan

(QASP)

DRAFT

W91CRB-24-R-0003

October 25, 2023

Prepared by:

IPPS-A Product Manager (PdM) Future Capabilities Office

IPPS-A AMP QASP - DRAFT CUI

October 25, 2023 ii

THIS PAGE INTENTIONALLY LEFT BLANK 14

October 25, 2023 iii

Table of Contents 18

1.0 Overview ............................................................................................................. 1 19

1.1 Purpose ............................................................................................................... 1 20

1.2 Intent .................................................................................................................... 1 21

2.0 Contract Description .......................................................................................... 1 22

2.1 Background ......................................................................................................... 1 23

2.2 Scope of Work .................................................................................................... 2 24

2.3 Type of Contract ................................................................................................. 2 25

3.0 Roles and Responsibilities ................................................................................ 2 26

3.1 Government ........................................................................................................ 2 27

3.1.1 Contracting Officer ................................................................................... 2 28

3.1.2 Contracting Officer’s Representative (COR) ............................................ 3 29

3.1.3 Product Manager and Associate PdM ...................................................... 3 30

3.1.4 Product Owner ......................................................................................... 4 31

3.2 Contractor ........................................................................................................... 4 32

3.2.1 Contract Manager ..................................................................................... 4 33

3.2.2 Program Manager .................................................................................... 4 34

3.2.3 Quality Manager ....................................................................................... 4 35

4.0 Contract Quality Requirements ......................................................................... 5 36

4.1 Contractor’s Quality Control Program .............................................................. 5 37

4.2 Government Quality Assurance ........................................................................ 5 38

5.0 Government Surveillance .................................................................................. 5 39

5.1 Customer Feedback ......................................................................................... 12 40

5.2 Surveillance Schedule ..................................................................................... 12 41

5.3 Surveillance Instructions/Checklists .............................................................. 13 42

5.4 Surveillance Documentation ........................................................................... 13 43

6.0 Nonconformance Reports (NCRs) .................................................................. 14 44

7.0 Deduct Plan ....................................................................................................... 14 45

8.0 Data Analysis .................................................................................................... 15 46

9.0 Acceptance of Services ................................................................................... 15 47

10.0 COR Status Report ........................................................................................... 15 48

October 25, 2023 iv

11.0 Contractor Manpower Reporting Initiative ..................................................... 15 49

12.0 Contractor Performance Assessment Reporting System (CPARS) ............. 16 50

13.0 Combating Trafficking In Persons (CTIP) ....................................................... 16 51

14.0 COR/Quality Assurance Surveillance Files .................................................... 16 52

15.0 QASP Changes ................................................................................................. 16 53

Attachment 1 - Corrective Action Report (CAR) ....................................................... 17 54

Attachment 2 - Customer Complaint Record ............................................................ 18 55

Attachment 3 - Performance Assessment Report (PAR) ......................................... 19 56

List of Tables 59

Table 1: Performance Objectives & Surveillance Methods .............................................. 6 60

Table 2: Evaluation Ratings Definitions ......................................................................... 11 61

October 25, 2023 1

1.0 Overview 64

1.1 Purpose 65

The purpose of this Quality Assurance Surveillance Plan (QASP) is to identify the 66 methods and procedures the Government will use to ensure it receives the services 67 under this contract as identified in the Performance Work Statement (PWS). 68

1.2 Intent 69

The intent of this QASP is to: 1) ensure Contractor performance meets or exceeds 70 contract terms, conditions, and specifications; 2) hold the Contractor accountable for 71 quality control; and 3) encourage the Contractor to take appropriate steps to control and 72 improve quality. Accordingly, the Government will perform surveillance on the contract 73 in accordance with this QASP; and reserves the right to monitor the contract in any 74 manner necessary, at any times necessary, and at all places necessary to ensure that 75 the rendered services conform to contract requirements. The Government also 76 reserves the right to perform quality assurance at the Subcontractor level and perform 77 quality assurance at the Contractor's place of business, if applicable. Resolution of non-78 conforming services discovered at the Subcontractor level will be addressed with the 79 prime Contractor. 80

2.0 Contract Description 81

2.1 Background 82

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

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

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

Contractors will apply and perform Agile execution in varying degrees to all aspects of 100 the program life cycle across and within key activities. These activities include 101

October 25, 2023 2 requirements analysis, elicitation, elaboration, and decomposition; architecture; design; 102 development, implementation; test; integration; training material development; and 103 deployment, in addition to support functions such as program management (planning, 104 reporting), configuration management, change control, release management, quality 105 assurance, and cybersecurity. 106

2.2 Scope of Work 107

The Army requires the following services, and the Contractor shall deliver an AMP 108 solution as follows: (1) design, configure, build, and test, (2) integrate and test the AMP 109 solution with the IPPS-A production baseline, (3) develop AMP training material, (4) 110 support AMP release and deployment activities, and (5) transition AMP functionality to 111 capability support. 112

These services will be acquired across the following tasks: 113

Task 1: Program Management 114 Task 2: Solution Configuration, Development, and Test 115 Task 3: Solution Integration 116 Task 4: Release and Deployment Support 117 Task 5: Government Software Reuse Integration 118 Task 6: Training Material Development 119 Task 7: Capability Support Transition 120 Task 8: Training Delivery [OPTIONAL} 121

2.3 Type of Contract 122

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

3.0 Roles and Responsibilities 126

3.1 Government 127

3.1.1 Contracting Officer 128

The Army Contracting Command-Aberdeen Proving Group (ACC-APG) will assign a 129 Contracting Officer (KO), duly appointed with the authority to enter into, administer, or 130 terminate contract actions such as basic awards or modifications, and make related 131 determinations and findings on behalf of the Government. The KO is the only individual 132 who can legally bind the Government. See Federal Acquisition Regulation (FAR) Part 133

1.602 for KO authority and responsibilities. 134

The KO is responsible for monitoring contract compliance, contract administration, and 135 cost control. The KO serves as the official Government agent with authority to modify 136 and interpret the contract with the Contractor. The KO is the only Government official 137 who can authorize contract actions that may result from review of Contractor 138 performance. The KO is responsible for resolving any differences between the 139

October 25, 2023 3 observations documented by the Government and the Contractor. The KO will also 140 ensure that the Contractor receives impartial, fair, and equitable treatment. 141

The KO will designate, at a minimum, one (1) KO Representative (COR) and/or one (1) 142 Alternate KO Representative (ACOR) as the Government authority for performance 143 management, based on the complexity of the services measured, as well as the 144 Contractor’s performance. 145

The KO relies on the COR to provide information and recommendations regarding 146 Contractor performance. While the KO may delegate many of the day-to-day contractual 147 administration duties to the COR, certain contractual actions are retained as the sole 148 purview of the KO, including: negotiation and issuance of contract modifications, 149 issuance of Contract Deficiency Reports, issuance of “show cause” letters, contract 150 termination, contract closeout, and Contractor claims and disputes resolution. 151

The KO is ultimately responsible for the final determination of adequacy of Contractor 152 performance. 153

3.1.2 Contracting Officer’s Representative (COR) 154

The COR will be identified by separate letter. The COR monitors all technical aspects 155 of the contract and assists in contract administration. The COR is responsible for 156 providing continuous technical oversight of Contractor performance. The COR is 157 authorized to perform the following functions: 1) assure that the Contractor performs the 158 technical requirements of the contract; 2) perform inspections necessary in connection 159 with contract performance; 3) maintain written and oral communications with the 160 Contractor concerning technical aspects of the contract; 4) issue written interpretations 161 of technical requirements, including Government drawings, designs, specifications; 5) 162 monitor Contractor's performance and notify both the KO and Contractor of any 163 deficiencies; 6) coordinate availability of Government furnished property, and 7) provide 164 site entry of Contractor personnel. The COR is not empowered to make any contractual 165 commitments or to authorize any contractual changes on behalf of the Government. For 166 any changes that may affect contract price, delivery dates, terms, or conditions, the 167 COR will alert the PO for potential resolution or action. 168

A letter of designation is issued by the KO to the COR, a copy of which is sent to the 169 Contractor, stating the responsibilities and limitations of the COR. This is the formal 170 source of authority for the COR. See FAR Part 2.101 for COR definition. 171

3.1.3 Product Manager and Associate PdM 172

The IPPS-A Product Manager (PdM) and AMP Associate PdM (APM) provide primary 173 program oversight. While the PdM and APM may serve as a direct conduit to provide 174 Government guidance and feedback to the Contractor on project matters, the PdM and 175 APM are not empowered to make any contractual commitments or any contract 176 changes on behalf of the Government. The PdM and APM will recommend a COR to 177 the KO, ensure the COR is trained before performing any delegated duties, and will 178 support COR performance assessment activities. 179

October 25, 2023 4

3.1.4 Product Owner 180

The AMP Product Owner(s) will work with the PdM and APM to provide oversight of the 181 work being performed to ensure business value and alignment with the AMP functional 182 requirements, (i.e., the right product is being developed for the user). While Product 183 Owners may serve as a direct conduit to provide Government guidance and feedback to 184 the Contractor on project matters, they are not empowered to provide any guidance to 185 the Contractor or make any contractual commitments or any contract changes on behalf 186 of the Government. 187

3.2 Contractor 188

3.2.1 Contract Manager 189

The Contract Manger manages the full range of acquisition activities. This individual will 190 be the primary point of contact for the KO and any designated CORs. Additionally, the 191 Contract Manger will 1) perform work related to Department of Defense (DoD) Contracts 192 Management, such as FAR, Defense Federal Acquisition Regulation Supplement 193 (DFARS), DoD Instructions (DoDI) 5000 series regulations and Clinger-Cohen Act 194 compliance; 2) track deadlines, deliverables, and other obligations; 3) plan, direct, and 195 manage projects/operations; 4) track and maintain a record of modifications; 4) record 196 and solve contract problems/issues; 5) report on contract deliverables and performance, 197 and 6) ensure product quality. In addition, the Contract Manager will be knowable of 198 different contract types; and will coordinate and interface with the Government 199 contracting office on contract-related action items and management activities. 200

3.2.2 Program Manager 201

The Contractor will assign an individual to serve as a Program Manager (PM) for this 202 effort. This individual will be the single point of contact for the Government Task Monitor 203 (GTM) and COR. The PM will be responsible for the performance of the work. The 204 name of this person and an alternate, who will act for the Contractor when the PM is 205 absent, will be designated in writing to the Contracting Officer. The Contractor PM and 206 alternate will have full authority to act for the Contractor on all matters relating to daily 207 operation of this contract. 208

3.2.3 Quality Manager 209

The Quality Manager will maintain an effective quality control program to ensure 210 services are performed as agreed to in the contract. This will include the following: 211

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

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

October 25, 2023 5

4.0 Contract Quality Requirements 217

4.1 Contractor’s Quality Control Program 218

The Contractor’s quality control program (IAW FAR Part 46 and applicable 52.246 219 Clause(s)) is the means by which the Contractor assures that work complies with the 220 requirement of the contract. The Contractor shall ensure services are performed in 221 accordance with the PWS. The Contractor shall identify, prevent, and ensure non-222 recurrence of defective services. 223

4.2 Government Quality Assurance 224

The Government shall evaluate the Contractor’s performance under this contract in 225 accordance with this QASP. This plan is primarily focused on what the Government 226 must do to ensure that the Contractor has performed in accordance with the 227 performance standards. It defines how the performance standards will be applied, the 228 frequency of surveillance and minimum acceptable defect rate(s). 229

5.0 Government Surveillance 230

The COR will evaluate the performance objectives through surveillance as reflected in 231 Error! Reference source not found. by reviews and acceptance of work products and 232 services. As indicated, the COR will assess progress towards the final delivered 233 products (e.g., source code, documentation). Note that the performance requirements 234 listed below are required for the final deliverable. However, the sprints and incremental 235 delivery of code will be assessed by the Government to ensure that the Contractor is on 236 a path to successful final delivery. 237

The Government ratings and narrative will reflect FAR Part 42.1503, Table 42-1 238 “Evaluation Ratings Definitions” as depicted in Table 2. These ratings include: 239 Exception, Very Good, Satisfactory, Marginal, and Marginal. The Objective and 240 Threshold values aligned to these ratings are noted in Table 1. 241

Error! Reference source not found. outlines the performance objectives, expected 242 standard of performance, the minimum accepted quality level, and method of 243 surveillance. If not otherwise referenced, the following definitions will be applied for the 244 method of surveillance: 245

100% Inspection: The Government will evaluate 100% of a deliverable or 246 required service. This surveillance method is appropriate where 100% inspection 247 is required and is practical. For example, all features will be inspected with a user 248 acceptance test prior to integration with the IPPS-A production baseline. 249

Random Sampling: The Government will evaluate less than 100% of a 250 designated a deliverable or required service on a random basis. This surveillance 251 method is appropriate for a deliverable or required service that occurs 252 infrequently and where 100% inspection is neither required nor practical. For 253 example, a subset of the completed work will randomly be inspected. 254

October 25, 2023 6

Periodic Inspection: The Government will evaluate less than 100% of a 255 designated a deliverable or required service on a selective basis. This 256 surveillance method is appropriate for a deliverable or required service that 257 occurs infrequently and where 100% inspection is neither required nor practical. 258 For example, completed user stories are inspected at the end of each sprint. 259

In addition, the Government will inspect user stories at the end of each Sprint to 260 evaluate the “Definition of Done” achieved during the Sprint. The target “Definition of 261 Done” for each Sprint will be defined at the beginning of the sprint. 262

Table 1: Performance Objectives & Surveillance Methods 263

Type Deliverable or Required

Services Description

Performance Standard(s)

Objective

Acceptable Quality Level

(AQL)

Threshold

Method of Surveillance

Program Management

Program Planning and Reporting

Quality Control and Management

Risk Management

Schedule Management

Personnel Management

Earned Value Management

Cost and Software Data Reporting

Contract Funds Management

License Management

Property Management

Knowledge Management

Periodic and ad hoc Meetings and Reporting

Program Management activities span all contract tasks. This includes the management and oversight of all activities performed by Contractor personnel, including Subcontractors, to satisfy the requirements identified in the PWS.

Accurate, complete. and timely support of tasks and functions as directed by the Government

Implementation of the schedule

Milestones met on time Requirements met within proposed cost Metric reports delivered on time in correct format/content

Meetings and Reporting provides the information needed

Task activities defined in PWS successfully completed

Very Good: meets the following at a minimum of 95%:

Meets milestones as scheduled Meets contract cost baseline Personnel required to perform tasks are qualified and present

Exceptional: meets the following at a minimum of 97%:

Meets milestones as scheduled Meets contract cost baseline Personnel required to perform tasks are qualified and present

100% compliant with all procedures and applicable regulations

90% of Contract Data Requirements List (CDRLs) delivered on time and in compliance with the DD FORM 1423-1

Satisfactory: meets the following at a minimum of 93%:

Meets milestones as scheduled

Meets contract cost baseline

Personnel required to perform tasks are qualified and present

100% Inspection

CDRLs Staffing Levels and Quality of Performance

Outcomes and performance of regularly scheduled and ad hoc meetings

Progress against Roadmap

Compares targeted versus delivered value to help determine if appropriate progress is being made. This informs future planning, Very Good: 95% of Delivered values

Exceptional: 97% of Delivered values

Satisfactory: 93% of Delivered values

100% Inspection

October 25, 2023 7

Type Deliverable or Required

Services Description

Performance Standard(s)

Objective

Acceptable Quality Level

(AQL)

Threshold

Method of Surveillance prioritization, and investment.

Contract Performance

Schedule Performance Index (SPI)

Measures how efficiently the project is progressing compared to the planned timeline (SPI = Earned Value / Planned Value)

Very Good: 95% SPI

Exceptional: 97% SPI

Satisfactory: 93%

SPI

100% Inspection

Cost Performance Index (CPI)

Evaluates the cost efficiency of the project by comparing earned value with actual costs (CPI = Earned Value / Actual Cost)

Very Good: 95% CPI

Exceptional: 97% CPI

Satisfactory: 93%

CPI

100% Inspection

Customer Satisfaction

Measures the level of satisfaction of stakeholders with the Contractor's performance

Customer satisfaction score = (total survey point score / total questions) x 100

Very Good: 95% Customer Satisfaction Score

Exceptional: 97% Customer Satisfaction Score

Satisfactory: 93% Customer Satisfaction Score

100% Inspection

% of Small business subcontracting value

Total value of small business contracting incurred on contract.

Total value of small business contracting = (Total value of small business contracting Total value of contracting)

Very Good: 23% Total value of business contracting

Exceptional: 25% Total value of business contracting SPI Customer Satisfaction Score

Satisfactory: 93% Total value of business contracting

100% Inspection

Agile Process Story Points Measure the complexity of a story and total amount of work to be completed in a sprint

% of Story Points completed versus planned

Very Good: 95%

Exceptional: 97%

% of Story Points completed versus planned

Satisfactory: 93%

100% Inspection

Velocity Actual amount of work completed in a sprint

Planned story points versus velocity (avg story point per sprint) each sprint

Very Good: 95%

Exceptional: 97%

Planned story points versus velocity (avg story point per sprint) each sprint

Satisfactory: 93%

Velocity Predictability

Average Velocity is a measurement of the average amount of story (or story points)

Used to calculate Velocity

Calculated at the end of Planning Intervals (PIs)

Used to calculate Velocity

October 25, 2023 8

Type Deliverable or Required

Services Description

Performance Standard(s)

Objective

Acceptable Quality Level

(AQL)

Threshold

Method of Surveillance delivered across a given time period.

Average Velocity = Total number of story (or story points) delivered / Total number of Sprints

Calculated at the end of PIs

Story Completion Rate

Number of stories completed in a sprint (and release)

% of Stories completed versus planned

Very Good: 95%

Exceptional: 97%

% of Stories completed versus planned

Satisfactory: 93%

100% Inspection

Release Burnup Amount of work completed for a release (Note: work should increase as sprints are completed until release)

% of release work completed versus planned

Very Good: 95%

Exceptional: 97%

% of release work completed versus planned

Satisfactory: 93%

100% Inspection

Recidivism Stories returned to the team (this is where the levels of “why” come in)

% of stories returned versus completed in a sprint

Very Good: 6%

Exceptional: 4%

% of stories returned versus completed in a sprint

Satisfactory: 8%

100% Inspection

Agile Quality First-time Pass Rate

Number of stories that pass the first time

% of stories passed (completed and accepted) in accordance with Definition of Done versus completed in a sprint

Very Good: 95%

Exceptional: 97%

% of stories passed (completed and accepted) in accordance with Definition of Done versus completed a sprint

Satisfactory: 93%

100% Inspection

Defect Count Number of defects per spring, PI, and release

% of defects per lines of code

Very Good: 6%

Exceptional: 4%

% of defects per lines of code

Satisfactory: 8%

100% Inspection

Test Coverage Level of testing performed in the value stream process

% of test coverage of capabilities, features, epics, and/or stories

Very Good: 95%

Exceptional: 97%

% of test coverage of capabilities, features, epics, and/or user stories

Satisfactory: 93%

Periodic Inspection

Number of Blockers

Number of events that prohibit completion of an activity or work item

Number of contract blockers currently open that prohibit the completion of an activity or work item in a sprint or release

Very Good: 6 blockers

Exceptional: 4 blockers

Number of contract blockers currently open that prohibit the completion of an activity or work item in a sprint or release

Satisfactory: 8 blockers

October 25, 2023 9

Type Deliverable or Required

Services Description

Performance Standard(s)

Objective

Acceptable Quality Level

(AQL)

Threshold

Method of Surveillance

Delivered Features (or Capabilities)

Delivery progress relative to outcome (Note: Features (or Capabilities) should increase as PIs are completed until release)

% of Delivered Features (or Capabilities) completed in accordance with Definition of Done versus planned

Very Good: 95%

Exceptional: 97%

% of Delivered Features (or Capabilities) completed in accordance with Definition of Done versus planned

Satisfactory: 93%

Capability Delivery

Delivered Value Points

Value points delivered to users for a release (Note: Is are completed until release)

% of Value delivered versus Value planned

Very Good: 95%

Exceptional: 97%

8% of Value delivered versus Value planned

Satisfactory: 93%

100% Inspection

Level of User Satisfaction

User satisfaction based on the value delivered in a release

% of User satisfaction based on the delivered value in a release

Very Good: 95%

Exceptional: 97%

% of User satisfaction based on the delivered value in a release

Satisfactory: 93%

100% Inspection of Releases with a random number of users surveyed

Cybersecurity RMF actions The Contractor shall follow DoD and Army RMF policies and regulations that govern the Department of Defense (DOD) RMF process (risk identification; risk measurement and assessment; risk mitigation; risk reporting and monitoring; and risk governance)

Conduct ongoing RMF actions to identify risk, risk measurement and assessment, risk mitigation risk reporting and monitoring (i.e., POAMs)

Very Good: Not Applicable

Exceptional: 100%

Satisfactory: 99.8% 100% Inspection

Training Material

Development

Training Material Effectiveness

Measure of the training materials’ effectiveness to convey the knowledge to users.

Accurate and complete Training Materials

Training proficiency levels identified in the agreed to Training Plan are met

Very Good: All training participants achieve a score of 80% or better and an average score of 82%

Exceptional: All training participants achieve a score of 80% or better and an average score of 85%

Accurate and complete Training Materials

Training proficiency levels identified in the agreed to Training Plan are met

Satisfactory: All training participants achieve a score of 80% or better and an average score of 80%

100% Inspection of user training scores

October 25, 2023 10

Type Deliverable or Required

Services Description

Performance Standard(s)

Objective

Acceptable Quality Level

(AQL)

Threshold

Method of Surveillance

Training Training experience satisfaction

Training metrics to measure and can usually be found in a post-training survey. It is used to gauge how satisfied learners are with the training they received.

Very Good: 87% Score from User Questionnaire

Exceptional: 90% Score from User Questionnaire

Satisfactory: 83% Score from User Questionnaire

100% Inspection

Transition Follow the Transition Plan accepted by the Government and keep the Government fully informed of status throughout the Transition period.

Transition Planning and Management

Transition Accountability

Transition Activity

Collaboration Asset Transfer

Transfer responsibility for project documentation, resources, assets, and performance to the designated party.

Ensure the implementation and readiness of capabilities necessary for all aspects of performance without disruption in schedule, increased costs, degradation to performance, need for increased Government oversight, or likelihood of unsuccessful

Accurate, complete. and timely support of tasks and functions as directed by the Government

Products delivered on time in correct format/content

Meetings and Reporting provides the information needed

Task activities defined in PWS successfully completed

Very Good: meets the following at a minimum:

100% compliant with all procedures and applicable regulations

100% of CDRLs delivered on time and in compliance with the DD

FORM 1423-1.

95% Personnel required to perform tasks are qualified and present

Exceptional: meets the following at a minimum:

100% compliant with all procedures and applicable regulations

100% of CDRLs delivered on time and in compliance with the DD

FORM 1423-1.

97% Personnel required to perform tasks are qualified and present

Satisfactory: meets the following at a minimum:

100% compliant with all procedures and applicable regulations

90% of CDRLs delivered on time and in compliance with the DD

FORM 1423-1.

93% Personnel required to perform tasks are qualified and present

100% Inspection:

CDRLs Outcomes and performance of regularly scheduled and ad hoc meetings

AMP

Performance

Standards

Accuracy Percentage of accurately processed payroll transactions

Identify errors in:

Soldier data payroll calculation tax calculations rations allotments garnishments Thrift Savings Plan Government liabilities others

Soldiers receives accurate pay, error free:

Very Good: Not Applicable

Exceptional: 100%

Soldiers receives accurate pay, error free:

Satisfactory: 99%

October 25, 2023 11

Type Deliverable or Required

Services Description

Performance Standard(s)

Objective

Acceptable Quality Level

(AQL)

Threshold

Method of Surveillance

Timeliness Measures the time it takes for the system to process payroll transactions for 1M+ payees

Very Good: 6 hours

Exceptional: 4 hours

Satisfactory: 8 hours 100% Inspection

Compliance Measures the percentage of payroll transactions that comply with:

relevant laws regulations policies

Compliance Score

Very Good: 95%

Exceptional: 97%

Compliance Score

Satisfactory: 93%

100% Inspection

Solider Satisfaction

Measures Soldier satisfaction with the payroll process; can be assessed through surveys, feedback forms, or focus groups.

A high level of satisfaction indicates that the system meets the needs of Soldiers and their families.

Soldier satisfaction score = (total survey point score / total questions) x 100

Very Good: 95%

Exceptional: 97%

Soldier satisfaction score = (total survey point score / total questions) x 100

Satisfactory: 93%

100% Inspection

The Government notifies the Contractor that it intends to adopt automated testing and 264 will establish metric(s) for automated testing at a later date under the terms of QASP 265 paragraph 15.0 266

Table 2: Evaluation Ratings Definitions 267

Rating Definition Note

Exceptional – Performance meets contractual requirements and exceeds many to the Government’s benefit. The contractual performance of the element or sub-element being evaluated was accomplished with few minor problems for which corrective actions taken by the Contractor were highly effective.

To justify an Exceptional rating, identify multiple significant events and state how they were of benefit to the Government. A singular benefit, however, could be of such magnitude that it alone constitutes an Exceptional rating. Also, there should not have been any significant weaknesses identified.

Very Good – Performance meets contractual requirements and exceeds some to the Government’s benefit. The contractual performance of the element or sub-element being evaluated was accomplished with some minor problems for which corrective actions taken by the Contractor were effective.

To justify a Very Good rating, identify a significant event and state how it was a benefit to the Government. There should not be any significant weaknesses identified.

Satisfactory – Performance meets contractual requirements. The contractual performance of the element or sub-element contains some minor problems for which corrective actions taken by the Contractor appear or were satisfactory.

To justify a Satisfactory rating, there should have been only minor problems, or major problems the Contractor recovered from without impact to the contract/order.

There should not have been significant weaknesses identified. A fundamental principle of assigning ratings is that Contractors will not be evaluated with a rating lower than Satisfactory solely for not performing beyond the requirements of the contract/order.

Marginal – Performance does not meet some contractual requirements. The contractual performance of the element or sub-element being evaluated reflects a serious problem for which the Contractor has not yet identified corrective actions. The Contractor proposed

To justify Marginal performance, identify a significant event in each category that the Contractor had trouble overcoming and state how it impacted the Government. A Marginal rating should be supported by referencing the management tool that notified the Contractor of

October 25, 2023 12

Rating Definition Note actions appear only marginally effective or were not fully implemented.

the contractual deficiency (e.g., management, quality, safety, or environmental deficiency report or letter).

Unsatisfactory – Performance does not meet most contractual requirements and recovery is not likely in a timely manner. The contractual performance of the element or sub-element contains a serious problem(s) for which Contractor corrective actions appear or were ineffective.

To justify an Unsatisfactory rating, identify multiple significant events in each category that the Contractor had trouble overcoming and state how it impacted the Government. A singular problem, however, could be of such serious magnitude that it alone constitutes an unsatisfactory rating. An Unsatisfactory rating should be supported by referencing the management tools used to notify the Contractor of the contractual deficiencies (e.g., management, quality, safety, or environmental deficiency reports, or letters).

The COR, along with the IPPS-A PdM, AMP APM, and designated Government Product 269 Owner, will inspect all tasks to ensure Contractor compliance with the requirements at 270 the conclusion of each Sprint. Delivery will occur by a data pull within the AMP agile 271 development tools repository. Inspection results will recorded and reported. The COR 272 may find the delivery satisfactory even though further work is required, provided that the 273 specific requirements of the sprint are met. 274

At the conclusion of each sprint, the COR, along with the IPPS-A PdM, AMP APM, and 275 designated Government Product Owner, will review the completed user stories and 276 related functionality. Incomplete or inadequate code and user stories will be noted in a 277 mutually agreed-upon issue tracker, such as Trello or GitHub Issues, and links to each 278 issue shared with the COR. The Contractor may respond in that tracker as appropriate, 279 addressing the accuracy and validity of the defect as well as any planned corrective 280 action (if not already noted). The Contractor team will discuss and document actions to 281 prevent recurrence in their sprint retrospectives. 282

At the conclusion of the period of performance, a similar procedure will be followed to 283 document discrepancies and to assess overall performance. 284

5.1 Customer Feedback 285

The following procedures will be followed when a complaint is received regarding the 286 Contractor/Contractor Employees. 287

The COR will investigate and determine the validity of the complaint. 288 If the complaint is determined to be invalid, the COR will inform the person who 289 submitted the complaint of the reason(s) as soon as practical. 290 For validated complaints that are true contractual non-conformances, the 291 procedures in paragraph 6 will be followed. 292

5.2 Surveillance Schedule 293

A Surveillance Schedule will be created for each month of Contractor performance and 294 filed in the Procurement Integrated Enterprise Environment (PIEE), Surveillance and 295 Performance Monitoring (SPM), Surveillance Documents Section of the Contract File 296 using the Add Smart Form function. The schedule is “Controlled Unclassified 297 Information (CUI)” and is not releasable to anyone other than those authorized by the 298 Government. 299

October 25, 2023 13

5.3 Surveillance Instructions/Checklists 300

Surveillance Checklists will be completed when surveillances are conducted and filed in 301 the PIEE, SPM, Surveillance Documents Section of the Contract File using the Add 302 Smart Form function. Supplementary data, such as end of sprint reports directly 303 extracted from the development tools that provide a snapshot of real-time progress will 304 be captured when possible. The objective is to take advantage of any tools and 305 streamlined processes available that capture results suitably to obtain the most 306 accurate results in an administrative-efficient manner. 307

5.4 Surveillance Documentation 308

No later than the 15th of each month surveillance documentation for the preceding 309 month will be filed in the PIEE, SPM, Surveillance Documents Section. Surveillance 310 documentation includes a COR Status Report, the Surveillance Schedule, all completed 311 Surveillance Checklist(s) for the period the COR Status Report covers, 312 Nonconformance Reports, if any, and Contractor Deliverables, if any. 313

The Government will document performance. A Performance Assessment Report (PAR) 314 template is attached (Attachment 3) or may be documented in the COR Monthly 315 Reports in PIEE. Any report may become a part of the supporting documentation for 316 fixed fee payments, or other actions. Government acceptance of services permits the 317 Contractor to invoice for the service fee. 318

Unacceptable Contractor performance can be identified by customer complaints 319 (Attachment 2) or upon schedule surveillance evaluations. When unacceptable 320 performance occurs, the COR shall inform the Contractor. This will normally be in 321 writing unless circumstances necessitate verbal communication. The COR will 322 document the discussion and place it in the COR file and provide a copy to the KO. 323

When the COR determines formal written communication is required, the COR will 324 prepare a Corrective Action Report (CAR) (Attachment 1). The CAR is forwarded to the 325 KO for dissemination to the Contractor. 326

The Contractor shall acknowledge receipt of the CAR in writing. The CAR will specify if 327 the Contractor is required to prepare a corrective action plan to document how the 328 Contractor shall correct the unacceptable performance and avoid a recurrence. The 329 CAR will also state how long after receipt the Contractor has to provide a corrective 330 action plan to the KO and COR. The Government may withhold payment for services 331 until corrective action is taken. The Government will review the Contractor's corrective 332 action plan to determine acceptability. Upon Government acceptance of the corrected 333 services the Contractor will be permitted to invoice for the service fee. 334

Any CAR may become a part of the supporting documentation for contract payment 335 deductions, fixed fee deductions, CPARS, or other actions deemed necessary by the 336

KO. 337

October 25, 2023 14

6.0 Nonconformance Reports (NCRs) 338

If any of the services do not conform to the task requirements, the COR may require the 339 Contractor to perform the services again in conformity with the task requirements. 340

Within a Planning Interval (PI), any user stories that are not accepted must be 341 completed in the next sprint, unless the Product Manager agrees for it to be moved to a 342 later sprint based on documented justification. The COR will not certify satisfactory 343 performance for a PI until all use stories dispositioned for the PI have been corrected. 344 The inherent real-time tracking and monitoring of user story progress and defects within 345 the development tools will be used as a data point for nonconformance monitoring. 346

7.0 Deduct Plan 347

The COR shall not certify satisfactory performance until all service / task defects have 348 been corrected. When the defects in services / task conduct cannot be corrected by re-349 performance, the Government may: 350

1. Require the Contractor to take necessary action to ensure that future 351 performance conforms to the task requirements; and, 352

2. Reduce the contract price to reflect the reduced value of the services performed. 353 The COR will, in addition to providing documentation to the CO, maintain a 354 complete quality assurance file. The file will contain copies of all reports, 355 evaluations, recommendations, and any actions relating to the Government’s 356 performance of the quality assurance function, including originals of all 357 surveillance activity checklists. All such records will be retained for the life of the 358 contract. The COR shall forward these records to the CO at completion or 359 termination of the contract. 360

The Government fully supports the Scaled Agile Framework (SAFe) and SAFe’s 361 concept to “Fail Fast”; however, the Government needs to ensure the Contractor 362 delivers a quality product in a timely manner. The Government will implement a Deduct 363 Plan that will support “Fast Fail” and aligns with the Government’s responsibility to 364 ensure the Contractor delivers a quality product in a timely manner. The Deduct Plan is 365 based on the following types of failures: 366

Contractor fails to complete a user story and meet Definition of Done 367 (Contractor’s Fault) 368

Government Roadblock prevents user story completion 369 User story not accepted by the user; user story did not adequately support the 370 user requirement and needs to be rewritten 371

If the Contractor fails to deliver a user story planned to be developed in a PI because of 372 Contractor’s Fault and the failure is a first occurrence for this user story, then the cost to 373 develop the user story a second time will be paid for by the Government as part of the 374 Contractor’s planned effort in a future PI. 375

If the Contractor fails to deliver a user story planned to be developed in a PI because of 376 the Contractor’s Fault and the failure is a second or more occurrence in a PI, then the 377

October 25, 2023 15 cost to complete will be deducted from the cost to complete the user story in a future PI 378 by the Contractor. 379

8.0 Data Analysis 380

Data Analysis will be performed to identify trends in cost, schedule and/or performance 381 risks. The results of Data Analysis will be documented in COR Status Reports and may 382 be used to make adjustments to surveillance schedules, and increase or decrease 383 surveillance, if deemed appropriate. Negative trends noted using Government 384 data/observations could result in issuing the Contractor a Nonconformance Report. 385 Trends noted using Contractor data will not result in a Nonconformance Report unless 386 the Contractor is not addressing the negative trend. 387

9.0 Acceptance of Services 388

Acceptance of services will be based upon compliance with performance standards 389 described in the PWS and surveillance procedures described in this QASP. Before 390 approving/certifying any Contractor invoices, the COR/ACOR will verify that all invoiced 391 services have been performed in compliance with contract requirements. The 392 COR/ACOR shall not certify satisfactory performance for the contract until all defects 393 have been corrected. 394

When all services have been deemed acceptable and there is documented objective 395 quality evidence to support acceptable performance, the COR will accept the services 396 provided and authorize payment to the Contractor. This is accomplished by approving 397 the Contractor’s Receiving Reports in PIEE, Wide Area Workflow (WAWF). 398

10.0 COR Status Report 399

COR Status Reports will be submitted on a monthly basis, no later than the 15th of each 400 month for the preceding frequency, to the Contracting Officer via PIEE, SPM, 401 Surveillance Documents Section using the Add Smart Form function. COR Status 402 Reports will provide a synopsis of the Contractors performance for the inclusive dates of 403 the report. The synopsis will contain a summary of: surveillances performed; Customer 404 Feedback, if any; Nonconformance Reports, if any; an analysis of the Contractors 405 performance; recommended adjustments to surveillance schedules; and any other 406 pertinent contract information. 407

11.0 Contractor Manpower Reporting Initiative 408

In accordance with Office of the Secretary of Defense Memorandum, Revised 409 Department of Defense Contractor Manpower Reporting Initiative, dated Oct 16, 2019, 410 the Contractor must report Contractor manpower to the System for Award Management 411 website at https://www.sam.gov NLT 31 October each year. All data shall be reported 412 in accordance with applicable FAR and supplements. The COR will verify that the 413

October 25, 2023 16

Contactor has complied with the required Contractor manpower reporting annually and 414 document the results in their October COR Status Report. 415

12.0 Contractor Performance Assessment Reporting System (CPARS) 416

Documented surveillance data (COR Status Reports, Completed Surveillance 417 Checklists, Customer Feedback, Deliverables, if any, and Nonconformance Reports, if 418 any) will be used to support CPARS ratings. CPARS will be completed in accordance 419 with Army Federal Acquisition Regulation Supplement (AFARS), Subpart 5142.15 – 420 Contractor Performance Information. The COR will document that CPARS, if required, 421 was completed in the COR Status Report for the month in which the CPARS was 422 completed. 423

13.0 Combating Trafficking In Persons (CTIP) 424

In accordance with PGI 222.17 and FAR 52.222-50, the KO will be notified immediately 425 of any information from any source that alleges a Contractor employee, Subcontractor 426 and/or Subcontractor employee has engaged in conduct that violates the United States 427 Government “zero” tolerance policy regarding trafficking in persons. 428

14.0 COR/Quality Assurance Surveillance Files 429

The official COR/Quality Assurance Surveillance File will be maintained in PIEE, SPM 430 IAW DoDI 5000.72, DoD Standard for COR Certification. 431

15.0 QASP Changes 432

This QASP is a living document and, as such, may be changed as needed based on 433 Data Analysis (trends), contract modifications, etc. The COR will send any 434 recommended changes to the KO for approval and the KO must approve all changes. 435

Ms. Kristin M. Height Ms. Robin M Delossantos 440 Contracting Officer Contracting Officer’s Representative 441 Army Contracting Command Army Contracting Command 442 Aberdeen Proving Ground, MD Aberdeen Proving Ground, MD 443

October 25, 2023 17

Attachment 1 - Corrective Action Report (CAR) 445

CORRECTIVE ACTION REPORT (CAR)

(If more space is needed, use reverse and identify by number)

1. CONTRACTOR 2. CONTRACT NUMBER 3. TYPE OF SERVICES

4. FUNCTIONAL AREA 5. SUSPENSE DATE 6.

CONTROL

NUMBER

7. DEFICIENCY MAJOR MINOR

FINDING:

FINDING IMPACT:

Please respond with a written corrective action plan that details the corrective action of the cited deficiency, the cause of the deficiency, and actions taken to prevent recurrence by Suspense Date in Block 5. If date was not entered in Block 5, the contractor is not required to provide a response.

8. QUALITY ASSURANCE PERSONNEL (COR)

TYPED NAME AND GRADE SIGNATURE AND DATE

9. ISSUING AUTHORITY

TYPED NAME AND GRADE SIGNATURE AND DATE

10. COR RESPONSE TO CONTRACTOR CORRECTIVE ACTION AND ACTION TAKEN TO PREVENT RECURRENCE

11. COR DETERMINATION

ACCEPTED REJECTED

12. CLOSE DATE

October 25, 2023 18

Attachment 2 - Customer Complaint Record 449

CUSTOMER COMPLAINT RECORD DATE/TIME OF

COMPLAINT

SOURCE OF COMPLAINT

ORGANIZATION BUILDING NUMBER INDIVIDUAL PHONE NUMBER

NATURE OF COMPLAINT

CONTRACT REFERENCE

VALIDATION

DATE/TIME CONTRACTOR INFORMED OF COMPLAINT

ACTION TAKEN BY CONTRACTOR

RECEIVED/VALIDATED BY

October 25, 2023 19

Attachment 3 - Performance Assessment Report (PAR) 454

PERFORMANCE ASSESSMENT REPORT (PAR)

(If more space is needed, use reverse and identify by number)

4. QUALITY ASSURANCE PERSONNEL (COR) SIGNATURE AND DATE 5. COR PHONE 6. SUSPENSE DATE

I. PERFORMANCE

7…