M9549425MR0011_DRAFT PWS 20250305.pdf

Performance Work Statement (PWS) United States Marine Corps (USMC) Pacific Posture Enterprise (PPE)

1.0 Background

Over the past few years within the USMC Portfolio, PLP (Pacific Branch) has transformed into the enterprise office for overseeing the entire Pacific posture, monitoring compliance of established international agreements, and supporting operational forces requirements in the Pacific. In support of this transformation, PLP has established an information management / knowledge management (IM/KM) framework utilizing Microsoft 365 capabilities to establish processes for managing content and a repository called the Command Library. The Command Library requires maintenance, enhancement, and further integration into the day-to-day operations of PLP and in support of the Pacific Posture Enterprise (PPE). In further support of the PPE, the program office has leveraged the data available from multiple sources to create and maintain the Enterprise Decision Support Tool (eDST), which has become the program of record for data calls and requests for information across multiple stakeholders. eDST is in a constant state of change with new data added, new visualizations required, and ever-changing requirements submitted for analysis. eDST will continue to be the go-to system for all PPE inquiries as it expands to all locations in the Pacific in alignment with Force Design, the Service’s posture in support of USINDOPACOM, and changes to international agreements. PLP’s oversight for the Enterprise also includes financial management. In support of Headquarters Marine Corps, Deputy Commandant, Programs and Resources (HQMC, DC, P&R) Planning, Programming, Budget, Execution, and Assessment (PPBEA) process; PLP submits, justifies, and defends the Program Objective Memorandum (POM) for program requirements, provides program specific guidance to Enterprise stakeholder organizations. In addition, PLP tracks and analyzes the budgeting and execution of enterprise appropriated funds supporting Okinawa, Guam, Commonwealth of Northern Marianas Islands (CNMI), Australia, and other Pacific related interests.

2.0 Scope/Objectives

The scope of this requirement is to acquire technical, analytical, and financial program analysis services, in support of Pacific Branch (PLP), PP&O. The Contractor shall assist government in the planning, design, and implementation of a framework for knowledge management, decision support tool, financial management, and programming requirements to enable enterprise governance, risk assessment/management, and integration of program objectives with HQMC processes, policies, and directives.

The Contractor shall assist the Government in the planning, design, and implementation of updates to the IM/KM framework, Enterprise Decision Support Tool (eDST), financial management, programming activities and tools that enable governance, risk assessment and management, and integration of program objectives with HQMC processes, policies, and directives.

3.0 Tasks

The contractor must provide qualified personnel to complete each of the following tasks:

3.1 Task Area 1: Information/Knowledge/Records Management and Microsoft 365 Applications

3.1.1 The Contractor shall maintain and expand on the existing Knowledge Management (KM) system that aligns PLP Enterprise practices to overall Marine Corps Knowledge Management Strategy.

3.1.2 The Contractor shall maintain and improve upon the PLP Command Library and associated Microsoft 365 integrated applications.

3.1.3 The Contractor shall create a content management plan for the Command Library to include at the minimum quarterly reviews of the content, validation of all workflows established to move content, and update of published best practices within PLP.

3.1.4 The Contractor shall provide Microsoft 365 applications support to include working with stakeholders to identify capability requirements, user group and permissions management, developing content management and business rules, creating specifications, developing business workflows and site creation.

3.1.5 The Contractor shall work with leadership to develop and implement IM/KM and Records Management policy, procedures, and tools.

3.1.6 The Contractor shall assess and report on the use and effectiveness of the KM framework tools.

3.1.7 The Contractor shall document business processes within PLP, identify the process owners, create Business Process Modeling Notation (BPMN) process flows, Supplier, Inputs, Process, Outputs, and Consumer (SIPOC) documents, and identify a Microsoft 365 solution for storing, maintaining, and providing access to all the processes.

3.1.8 The Contractor shall generate a process management process by which all processes will be identified, documented, and maintained.

3.1.9 The Contractor shall analyze internal and external information and provide recommendations for process improvement.

3.1.10 The Contractor shall assist the Government in the organizing and archiving of institutional knowledge.

3.2 Task Area 2: Enterprise Program Management Support

3.2.1 The Contractor shall develop a Project Management Plan (PMP) for the maintenance and expansion of the Enterprise Decision Support Tool (eDST). The PMP shall reflect best practices, per Government Accounting Office (GAO) standards, Defense Acquisition University (DAU), and industry standards established by Program Management Institute (PMI).

3.2.2 The Contractor shall analyze and integrate enterprise data from multiple sources, to include stakeholder Integrated Master Schedules (IMSs), to design and build a Data Management Plan to align with the Enterprise Information Management Plan.

3.2.3 As required, the Contractor shall review and analyze Congressional appropriations, Pacific related interests, and Congressional materials supporting the execution of funds received from Government of Japan (GoJ) via Exchange of Notes (EON).

3.2.4 The Contractor shall identify required data and recommend and establish data calls and procedures to facilitate inputs from stakeholders.

3.2.5 The Contractor shall plan, design, develop, and deliver updated versions of eDST as required via discussions with the stakeholders, PLP staff, and changing data sources. The Contractor shall sustain, monitor, maintain, and report on eDST status. The Contractor shall employ iterative development approaches to the planning, design, and build of eDST.

3.2.6 The eDST shall expand to capture all PLP business lines and the Contractor shall work with the various components of PLP to capture requirements and support mission needs as coordinated with the PLP program manager.

3.2.7 The eDST will continue to provide and enable client capabilities to do the following, at minimum:

3.2.7.1. Identify and asses actual progress vs. planned progress for construction projects as reported by stakeholders.

3.2.7.2. Monitor the program Critical Path and help identify problem areas.

3.2.7.3. Assess the status of risk management activities based on the inclusion of program Risk Mitigation events aligned to Force Design and international agreement requirements.

3.2.7.4. Assess the progress on selected metrics, milestones, performance indicators, and performance measures.

3.2.7.5. Develop and support “what-ifs” exercises and to identify and assess candidate problems and workarounds.

3.2.8 The Contractor shall assist in development of eDST training materials, information guides, and newsletters.

3.2.9 The Contractor shall support program integration efforts by performing gap analysis.

3.2.10 The Contractor shall provide risk and change management analysis using information gathered in support of the eDST.

3.2.11 The Contractor shall lead or support meetings, conferences and workshops, including but not limited to Scenario Development Workshops, Technical Working Groups (TWG), Interim Progress Reviews (IPR), Integrated Product Team (IPT) and Operational Planning Team (OPT).

3.2.12 The Contractor shall provide virtual or onsite training support to stakeholders, as determined by the appropriate Government representatives. This may involve overseas travel.

3.3 Task Area 3: Financial Management and Analysis Support

3.3.1 The Contractor shall assist the client to support and inform the USMC and/or DON planning, programming, budgeting, and execution cycle associated with the DPRI program and Pacific posture related fiscal interests. This includes scenario development and analysis.

3.3.2 The Contractor shall provide financial analysis using information gathered from fiscal databases to include, but not lineated to, Defense Agencies Initiative (DAI), Programming, Budget, Information, System (PBIS), Marine Corps Program Review Information Management Enterprise (MCPRIME), eDST, Cerberus, USMC MCFAD, Navy STARS, Navy Enterprise Resource Planning (Navy ERP), and other financial databases and tools utilized by PLP and Enterprise stakeholders.

3.3.3 The Contractor shall crosscheck the accuracy of programming, budget, execution, and program data in related budgetary forms, fiscal and programming databases, documents, schedules, and reports.

3.3.4 The Contractor shall coordinate with stakeholders to analyze budgetary submission and funds execution information in support of the client.

3.3.5 As required, the Contractor shall review financial documents to verify budgetary account codes, data elements, and dollar amounts.

4.0 General Requirements.

4.1 Within one week after award, the contractor will schedule, and conduct as later scheduled, an initial orientation meeting. The orientation meeting will be held at a location or virtually, date and time mutually agreed upon by both parties. At the meeting the contractor will address its approach to meeting performance requirements to ensure a common understanding of contract requirements.

4.2 The Contractor shall produce Monthly Status Reports (MSRs) to the COR. Reports shall include at a minimum, an executive summary, identify schedule tracking, any issues, and recommendations. The MSR shall provide information on all work completed, all work in progress, all work outstanding, as well as highlighting problems encountered and anticipated.

The MSR shall be submitted five (5) working days following the beginning of each month. The Government shall respond within 5 working days with comments. The Contractor shall incorporate the comments within 5 working days. For final deliverables, the Government shall either accept or reject them within 5 working days of submission.

In the event of rejection, the Government shall notify the Contractor in writing of the reasons for such rejection. Absence of notification will be construed as an acceptance.

4.3 Thirty (30) days before completion of this contract, the contractor shall provide a transition out plan to an incoming contractor/Government personnel. This includes formal coordination with the COR and successor contractor staff or Government personnel to transfer knowledge regarding the following:

• Status of ongoing activities and initiatives

• Location of project documentation, procedures, files, and points of contact.

5.0 Deliverables

Deliverable Frequency Medium/Format Submit To Acceptance Criteria

PWS 3.1

KM POA&M

30 business days following kickoff and will update as necessary

Email, Word document or PowerPoint

COR and Programmatic Alignment Lead

No more than 3 errors per report or product and delivered by the required due date

PWS 3.1.3

Content Management Plan

During the first option year, updated as needed

Email, Word document or PowerPoint

COR and Programmatic Alignment Lead

No more than 3 errors per report or product and delivered by the required due date

PWS 3.1

SharePoint and Power Bi Utilization Report

30 business days following kickoff, quarterly thereafter

Email, Word document or PowerPoint

COR and Programmatic Alignment Lead

No more than 3 errors per report or product and delivered by the required due date

PWS 3.2.1

eDST Project Management Plan

During the first six months, updated as needed

Email, Word document

COR and Programmatic Alignment Lead

No more than 3 errors per report or product and delivered by the required due date

PWS 3.2.8

eDST new version release Newsletter

After each major functionality release or as requested by Government

Email, PDF COR and Programmatic Alignment Lead

No more than 3 errors per report or product and delivered by the required due date

PWS 3.3

Finance Monthly Execution Status Report

Monthly Email, Excel, PowerPoint

Financial Management Lead

No more than 3 errors per report or product and delivered by the required due date

PWS 3.3

Execution Updates to Exchange of Notes

Monthly Email, Excel, PowerPoint

Financial Management Lead

No more than 3 errors per report or product and delivered by the required due date

Deliverable Frequency Medium/Format Submit To Acceptance Criteria

PWS 3.3.1

Analysis of Programming Submissions

Annually or as required by DC, P&R, to include potential revisions

Database, Email, PowerPoint, Excel, Microsoft Teams

Financial Management Lead

No more than 3 errors per report or product and delivered by the required due date

PWS 3.3.2

Fiscal Database Analysis

Monthly Fiscal Databases, Excel, Email, Microsoft Teams, PowerPoint

Financial Management Lead

No more than 3 errors per report or product and delivered by the required due date

PWS 4.2

Monthly Status report

Monthly Email, PowerPoint COR and Contracting Officer

No more than 3 errors per report or product and delivered by the required due date

PWS 4.3

Transition Plan

30 days prior to completion of the contract

Email, Word Document

COR No more than 3 errors per report or product and delivered by the required due date

6.0 Place of Performance and Hours of Operation:

6.1 Place of Performance: The majority of work to be performed under this contract will be performed at the Contractor facilities and pre-approved ad hoc workspaces. Personnel will be required to work at the Government site (HQMC Pentagon located in Arlington, VA), as required by this PWS or as requested by the COR. Travel to/from the Contractors facility and the Pentagon and/or facilities within the NCR is not reimbursable. On occasion, specific personnel may be required to travel to Marine Corps bases within the Indo-Pacific to include locations in Hawaii, Guam, Japan, and Australia.

6.2 Hours of Operation. The contractor is responsible for conducting business Monday thru Friday except Federal holidays, unless otherwise directed by the Contracting Officer’s Representative or when the Government facility is closed due to weather conditions, and local or national emergencies. For purposes of scheduling personnel, the Contractor is advised that the Government installation will observe the following holidays and access to the Government installation may be restricted on these holidays:

HOLIDAY OBSERVANCE

New Year’s Day 1 January Martin Luther King Jr. Birthday 3rd Monday in January President’s Day 3rd Monday in February Memorial Day Last Monday in May

Juneteenth Federal Holiday 19th of June Independence Day 4 July

Labor Day 1st Monday in September Columbus Day 2nd Monday in October Veteran's Day 11 November Thanksgiving Day 4th Thursday in November Christmas Day 25 December

Core hours are between 0800–1700. The Contractor must at all times maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS when the Government facility is not closed for the above reasons.

7.0 Period of Performance:

The period of performance will include a one (1) year Base Period and four (4), one year Option Periods.

Period of Performance Date of Commencement Date of Completion Base Period 4 September 2025 3 September 2026

Option Period One 4 September 2026 3 September 2027 Option Period Two 4 September 2027 3 September 2028

Option Period Three 4 September 2028 3 September 2029 Option Period Four 4 September 2029 3 September 2030

8.0 Non-classified Internet Protocol Network (NIPRNet) Compliant Laptops

8.1. The Government will not furnish NIPRNET Compliant laptops/computers. Unless otherwise approved by the COR, the Contractor must deliver the NIPRNet compliant laptop(s) within 2 business days of the start of the contract’s period of performance or within 14 days of the contract’s award date, whichever is later, to the MCSC, G-6, Information Technology Asset Management (ITAM) department for imaging. The Government will notify the Contractor once imaging is complete. The Contractor shall pick up imaged laptops and distribute them to its personnel within 7 days of being notified by the Government. NIPRNet compliant laptops procured and operated for this contract shall only be used by personnel supporting this contract. No more than one laptop/computer will be imaged per Contractor employee.

8.2. The current list of approved laptops eligible for imaging shall be provided upon task order award. During task order performance, the Contractor shall contact the COR or their designee for an updated list if additional laptops are required for task order performance.

8.3. Upon completion of the contract or at such time as the Contractor reclaims the asset from the Marine Corps effort; non-Government owned internal\external hard drives and data associated with the laptop shall become the property of the US Government and turned over to the COR upon request. The laptops purchased will not be considered Government property and will not transfer to the Government at the end of the task order (except the aforementioned hard drives and data).

9.0 On-Site Performance

Contractor personnel working on-site shall follow procedures established at each site for ensuring the security of the building, equipment, materials and personnel who are working in and around facilities. During duty hours, Contractor personnel shall keep doors to the outside of facilities secured. When securing facilities at the end of the duty day or after hours, Contractor personnel shall follow established procedures. The Contractor and its employees shall be subject to all traffic, security, and registration regulations for personnel and vehicles.

10.0 Contractor Identification

Contractor employees must be clearly identifiable while on Government property by wearing appropriate badges.

Badges must be clearly visible at all times while on Government property and presented for examination upon request from the Contracting Officer, COR, Military Police, or any other Government Official with a need to see the badge. Contractor personnel and their subcontractors must identify themselves as Contractors or subcontractors during meetings, telephone conversations, in electronic messages, or correspondence related to this Contract. In email correspondence with the Government, is should be clear that the employee is a Contractor employee (i.e., annotate in signature block). Contractor-occupied facilities (on Department of the Navy or other Government installations) such as offices, separate rooms, or cubicles must be clearly identified with Contractor supplied signs, name plates or other identification, showing that these are work areas for Contractor or subcontractor personnel.

11.0 Security Requirements

Security requirements applicable to this contract are described in the Department of Defense Contract Security Classification Specification DD254 form. Access to classified data/information up to and including SECRET will be required in the performance of this work. The Contractor must hold an active SECRET Facility Clearance. All personnel directly supporting this Contract shall have a minimum SECRET security clearance and be ready to perform at contract award.

Common Access Cards (CAC): All personnel performing tasks under this contract must be eligible for, and obtain, a DoD Common Access Card (CAC) and associated DoD Public Key Infrastructure (PKI) certificates for identity verification and encryption of transmitted correspondence.

Requirements for Issuance of a CAC. The following conditions must be met prior to issuance of a CAC to any contractor employees for limited privilege/non-privileged access:

1) The Contractor shall be registered in the Contractor Verification System (CVS) with a valid record of security clearance (background check) on Joint Personnel Adjudication System

(JPAS).

2) All Contractor Employees will have an active current Secret clearance prior to commencing support.

3) The Contractor shall obtain proof of security clearance (background check) on JPAS.

4) When applying for a CAC, the Contractor shall show two original forms of Identification and submit 1) contract document, 2) letter of employment, 3) letter of authorization from the Contracting Officer [as applicable], and 4) a valid record of JPAS (proof of background check).

Note: Prior to applying for CVS, the Contractor’s personnel must initiate a background check on JPAS at the Security Management Office and a record of JPAS enrollment verification (e-mail) must be submitted to a Trusted Agent (TA).

12.0 Travel Reimbursement

Travel reimbursement is limited to travel DURING performance of the contract. Travel reimbursement does NOT include relocation expenses for Contractor employees prior to their start of performance on this contract/task orders.

Local travel (50 miles radius from assigned place of performance) will not be covered under this contract as a travel cost transaction.

The Contractor may be required to travel in the performance of this contract and shall be responsible for making all necessary arrangements for its personnel. These include but are not limited to medical examinations, immunizations, passports/visas/etc., and security clearances.

Contractor Request and Approval of Travel:

The Contractor will coordinate travel arrangements with the Contracting Officer's Representative (COR). Any travel under this contract must be specifically requested in writing by the Contractor and approved by the Contracting Officer’s Representative (COR), prior to incurring any travel expense. The Contractor shall submit the written request to the COR at least five (5) days in advance. The travel request shall include at a minimum, the following:

• Contract number

• Date, time, and place of proposed travel

• Purpose of travel and how it relates to the contract

• Contractor’s estimated cost of travel with a breakdown of the estimated costs of transportation, lodging, meals, and incidentals; and

• Name(s) of individual(s) traveling.

If the contractor is proposing to purchase re-fundable airfare, a justification must be included in the contractor request for travel and the COR must approve it prior to purchase.

The COR shall review and approve/disapprove (as appropriate) all travel requests submitted giving written notice of such approval or disapproval to the Contractor.

Travel Reimbursement: Travel will be paid on a cost reimbursable basis. The Contractor shall adhere to the following travel regulations (see FAR 31.205-46):

• Federal Travel Regulations (FTR) – Prescribed by the General Services Administration, for travel in the contiguous United States.

• Joint Travel Regulations (JTR), Volume 2, DoD Civilian Personnel, Appendix A. Prescribed by the Department of Defense for travel in Alaska, Hawaii, and outlying areas of the United States.

• Department of State Standardized Regulations (DSSR) (Government Civilians, Foreign Areas), Section 925, "Maximum Travel Per Diem Allowances for Foreign Areas," prescribed by the Department of State for travel in areas not covered in the FTR or JTR.

The Contractor will not be reimbursed for travel expenses unless audited records for transportation contain evidence, such as original receipts, substantiating actual expenses incurred for travel. The Contractor shall be reimbursed for the reasonable actual cost of transportation, lodging, meals and incidental expenses. However, actual costs shall be considered reasonable, allowable, and reimbursable only to the extent they do not exceed on a daily basis the maximum per diem rate in effect at the time of travel as set forth in the DOD Joint Travel Regulations located at http://www.defensetravel.dod.mil/. Actual cost does not include handling charges, general and administrative cost, overhead, profit or any other indirect cost.

Labor costs/wages of personnel on travel will not be covered under the reimbursable travel CLIN.

The contract includes a not-to-exceed funding limitation for travel costs. When the Contractor expects total funding expended for reimbursable travel to reach 85 percent of the total funds available on the travel CLIN, the Contractor shall notify the Contracting Officer and the COR and any other Government official identified by the Contracting Officer. The notice shall state the estimated amount of additional funds required to continue performance for the period specified in the task order. The Contractor shall not exceed or incur costs that exceed the amount of funding stated on the reimbursable travel CLIN. The Government is not obligated to reimburse the Contractor for otherwise reimbursable travel in excess of the funded amount stated on the reimbursable travel CLIN.

The Contractor is not obligated to continue performance of any reimbursable work under this Contract or otherwise incur costs for reimbursable travel in excess of the funded amount stated on the reimbursable travel CLIN unless the Contracting Officer notifies the Contractor in writing that the funded amount stated under the applicable reimbursable travel CLIN has been increased. In the event notification is made orally, such notification shall be followed up in writing within two working days.

No notice, communication, or representation from any person other than the Contracting Officer shall affect the Government’s obligation to reimburse the Contractor.

Change orders shall not be considered an authorization to exceed the funded amount stated under the reimbursable travel CLIN unless they contain a statement expressly increasing the funded amount of that reimbursable CLIN by a sufficient amount to cover the change order.

13.0 Data, Software And Intellectual Property Rights

All data, regardless of format, created, generated, produced or provided under, or as a result of, this contract shall become the property of the U.S. Government/Marine Corps, not the contractor, subcontractor, or individual author or researcher. This data includes reports, materials, data, information, and all electronic/digital files and other

PWS related items. The items described herein, and any other items, are hereinafter referred to individually or collectively as the work or works. The Marine Corps shall have the irrevocable, worldwide, royalty-free right to use, modify, reproduce, perform, display, release, or disclose such research, reports, materials and information, and associated intellectual property, in whole or in part, in any manner, and for any purpose whatsoever, and to have or authorize others to do so. The U.S. Government/Marine Corps shall be the owner of all of these works and all intellectual property rights in or to these works. Therefore, any restricted data rights, information, software, materials and/or other items, including the contractor’s or a third-party’s proprietary data, information, software, materials and/or items must not be used under this contract without the specific written approval by the Contracting Officer prior to start of any work.

14.0 Use of Works

Without the prior written permission of the Contracting Officer, no data, materials, information, or other items (hereinafter singularly or collectively “Items”) created or provided expressly for this contract/PWS shall be used by the contractor for any purpose other than those that are in support of, or for performance under, this PWS. The contractor (including its employees and subcontractors) is obligated to protect from unauthorized use or disclosure all Government confidential or classified material and/or Government-owned proprietary, and/or Personally Identifiable Information or Personal Privacy Items obtained in the course of performance under the Government contract, as long as such data remains proprietary, confidential, sensitive, or classified. Any information obtained in the course of duties, or the performance of services, under this contract including, but not limited to, information that may be made available for use that relates to the technical data, trade secrets, processes, operations, style of work, or apparatus, or to the technical data, statistical data, amount or source of any income, profits, losses, or expenditures of any person, firm, partnership, corporation, or association is included in this clause (and with “Items”). Contract personnel shall not publish, divulge, disclose, or make known Items in any manner, or to any extent not authorized by the Contracting Officer. When the contractor’s need for such Items ends, the Items shall be returned promptly (within ten (10) business days) to the appropriate government program personnel. However, the obligation not to discuss, disclose, release, reproduce or otherwise provide or make available such Items, or any portion thereof, shall continue, even after completion of this contract/order. Any actual or suspected unauthorized use, disclosure, release, or reproduction of any Items or violation of this agreement, of which the company or any employee is or may become aware, will be reported promptly (within one business day) to the contractor’s program manager, who will inform the Contracting Officer within five (5) business days of receiving such report.

15.0 Performance Requirements Summary (PRS):

Performance Objective

PWS

Reference

Performance Standard

Acceptable Quality Level

Method of Surveillance

Incentive

PRS #1

Timeliness of Deliverables required by the Contract

3.0 & 5.0

Deliverables shall be submitted in accordance with the delivery requirements required by the

PWS.*

95% of the deliverables / reports are submitted on time each month or as directed by Government supervisor.

COR

Tracking, 100% inspection

CPARS

ratings

PRS #2

Accuracy of Deliverables required by the Contract

3.0 & 5.0

Reports and Other Deliverables are complete and correct when submitted.

95% of deliverables should have no more than three (3) errors each month.

Customer input / random sampling / COR review, 100% inspection

CPARS

ratings

PRS #3

Responsiveness 3.0 & 4.0

Provide effective responses to requirements and effective balancing of resources to

Meets all requirements.

Problems encountered are minor, not substantive, and resolved in a

Customer input/ random sampling/

COR

review ratings;

Option Exercise

*Note: Deliverables are not counted as late when, on a case by case basis, the COR approves later deliverable submission. The COR’s approval of a late deliverable submission or failure to strictly enforce delivery requirements will not be deemed a waiver of the applicable delivery requirements for future deliverables.

accomplish work requirements without sacrificing priorities, or creating unstable performance.

satisfactory, timely manner to be determined with Government supervisor

PRS #4

Overall

Management of Tasks

3.0 & 5.0

Coordinate task activities and provide overall expertise for successful integration, management and completion of master plan.

Meets all requirements.

Any errors or issues identified submitted to the Government supervisor within 1 business day.

Problems encountered are minor, not substantive, and resolved in a satisfactory, timely manner within 5 days or otherwise determined with Government supervisor

Customer input / random sampling / COR review ratings

PRS #5

Staffing 3.0

Maintain adequate staffing in order to avoid a gap in service/ lapse of personnel supporting the required task areas.

100% of personnel positions should have no more than a 3 week vacancy gap annually.

COR tracking, 100% inspection

CPARS

ratings / Invoice reductions for missing personnel