DRAFT Workload Model PWS_052522.pdf

CONTRACTING RESOURCING

PREDICTIVE RESOURCE STAFFING MODEL (PRSM)-CONTRACTING

PERFORMANCE WORK STATEMENT (PWS)

1. PURPOSE OF EFFORT: The intent of this effort to enhance the time to produce a model or design and deliver a similar model to facilitate forecasting and validating the Naval Supply Systems Command (NAVSUP) contracting resources/billets are aligned adequately to fulfill contracting workload. NAVSUP needs an objective, independent manpower forecasting tool that enables agile, well-informed, and real-time decision-making. Upon completion, the model shall be provided to NAVSUP contracting (SUP02). SUP 02 serves as the Head of the Contracting Activity (HCA) principal staff for contracting policy matters, operational review and specific approval actions; acts for the HCA in the management of contracting and purchasing matters under the purview of NAVSUP. The vision is to create an agile and efficient network of contracting professionals and resources that develops and leverages innovative acquisition solutions for the delivery of contracting services across the Navy Field Contracting System (NFCS). The focus of this requirement is on contracting functions.

2. LOCATION(S) OF EFFORT: Work will be conducted at the contractor’s facility, virtually over Microsoft Teams, approximately 3 to 5 meetings at NAVSUP headquarters and two site visits, one to the largest CONUS NAVSUP facility by dollars and the other the largest CONUS NAVSUP facility by actions.

3. DESCRIPTION OF DELIVERABLES: The contractor shall provide deliverables in accordance with the Services Summary (Table 12.) section and as defined by the standards outlined in this PWS. The PRSM deliverables shall be used to build and/or incrementally update the time to produce model for specified Acquisition functions. Functions being modeled are limited to Contracting functions. The model shall be in a platform or software that is approved by the Government prior to development.

The model shall provide capabilities listed below. All draft deliverables must be submitted no less than 7 calendar days in advance of the final deliverable deadline to allow for coordination and concurrence. The contractor shall provide the following:

Contracting Manpower Model Support. To help develop a successful model, segmented appropriately to account for variance across commodities/classes, the contractor shall provide assistance listed below:

3.1 Project Kick Off and Planning Deliverable:

3.1.1 Programmatic Support:

3.1.1.1. The contractor will be required to support integration level meetings and in-progress reviews (IPRs) prepared to discuss the technical aspects of the model. The contractor shall prepare presentation material to support these sessions as requested. In conjunction with any necessary technical clarifications, due to the dynamic nature of this work, these on-going technical discussions are intended to guide the work as it evolves.

3.1.1.2 Contractor team will need to participate in bi-weekly Integrated Product Team (IPT) meetings via MS Teams, teleconference, or in person. These sessions can range from 2 hours (VTC) to 3 days (working group session). The frequency of these meetings may increase based on project phase and require participation.

3.1.1.3 Contractor will meet with project lead on a weekly basis either by telephone or in person (NSA Mechanicsburg). These meetings will serve as synchronization points and/or preparation sessions for upcoming activities.

3.1.1.4 Periodic Progress Meetings. The Contracting Officer Representative (COR) and the Contractor shall periodically meet to discuss the Contractor’s performance. The following issues shall be discussed; opportunities to improve the contract, any potential modifications of the contract, unsatisfactory inspections and valid customer complaints against each performance objective observed and steps taken by the Contractor to prevent occurrences in the future.

3.1.1.5 The minutes of these meetings may be reduced to writing, signed by the Contracting Officer Representative and any other signatures as deemed appropriate, distributed to the functional area and the contractor. Should the contractor not concur with the minutes, the contractor shall provide a written notification to the Contracting Office identifying areas of non-concurrence for resolution.

3.1.2. The Contract Model Project Kickoff presentation will be the initial deliverable. This product shall be delivered in a PowerPoint slide deck and presented to the project integrator and functional leads.

The Contract Model kick-off will be to define and outline the following:

• Objectives and Deliverables

• Team Structure

• Modeling Approach

• High-Level Timeline

• Stakeholder Roles

• Data Requirements

• Topics for Discussion

3.1.3. Design Plan. Provide inclusive description of the proposed model to include:

• Detailed Project schedule

• Data to be used in model development (touch-hours, drivers, standards, assumptions, etc.)

• Description of how data will be segmented (organization, commodity, etc.)

• Description of statistical approach to be applied

• Software utilization

• Description of user input process

• Description of output format(s)

• Description of model flexibilities

• Competency Management Integration

3.1.4. Project Management Plan Update.

The Project Management Plan will be updated, as applicable, to define and outline the following:

• Outline the key activities, methodology and milestones associated with the specific study population

• Define key features of the study population – understand the context, complexity, diversity and geographical differences of the population

• Define survey questions/data collection investigation and development task list that incorporates feedback from, SME interviews, survey data, and other sources Perform analysis to include recommendations for alternative means of data discovery

• Build a tentative work breakdown structure

• Outline of programmatic risk/alternatives

3.2 Site Survey Deliverable:

3.2.1 Site Surveys

Anticipated MS Teams/travel to Navy Field Contracting System (NFCS) will establish the first body of knowledge through key interviews with subject matter experts (SMEs), key leadership and other members of the Contracting community. The data collected during this visit will be analyzed and presented to the Government for the purpose of validating the best means of accurately measuring this population across the NAVSUP enterprise.

Data to be collected will be to define and outline the following:

• Refine and validate key activities, methodology and milestones associated with the specific study population

• Further define and gather key features of the study population – understand the context, complexity, diversity and geographical differences of the population

• Gather data for survey questions/data collection investigation and development task list that incorporates feedback from, SME interviews, survey data, and other sources; Perform analysis to include recommendations for alternative means of data discovery

• Build, refine and validate workload driver list

• Build or refine draft driver questionnaire list

• Refine work breakdown structure and associated task list.

• Outline of programmatic risk/alternatives

The contractor shall obtain an approved plan by project lead prior to site surveys to keep project on schedule.

The site survey report shall be delivered to the government within 15 days of completing the site visit/VTC. The analysis should be in the form of a word document, with all data collected residing in expandable document formats that will allow additional data to be added upon the data points collected throughout the Contracting community.

3.3 Data Collection Deliverable:

3.3.1 Workload Driver List. Through data collection compile a list of key determinants to help further define and distinguish work attributes of the Contracting field. Following data collection, provide an assessment of which drivers were shown to be statistically relevant.

3.3.2 Workload Trends. Through data collection, analyze workload trends, community areas, performance trends, etc.

to help further define and distinguish workload of the Contracting field.

3.4 Model Deliverable:

3.4.1 Model Design Plan. Model description shall include the following data points at a minimum. The composition of The data to be used in model development selection criteria for their inclusion shall include:

• Touch-hours

• Drivers

• Standards

• Assumptions

• Description of how data will be segmented (e.g. organization, product, commodity, etc.)

• Description of statistical methodology/approach be applied

• Anticipated software requirements utilization

• Description of user input process

• Description of output format(s)

• Description of model flexibilities

• Course of Actions (COAs) for inclusion of competency management data

3.4.2 Predictive Resource Staffing Model-Contracting. Delivery of final functional Contracting PRSM will provide forecasts of workload requirements by Full-Time Equivalent (FTE), grade, workforce type, and tasks performed.

PRSM-Contracting model will consist of inputs (workload driver values), algorithms, and outputs (forecast recommendations for manpower requirements). PRSM will be developed with full intent of meeting NAVSUP validation criteria (repeatability/defendable analytics). Data must correspond to a Unique Identification Code (UIC).

Data outputs should be in consideration of the varied users and multiple projected uses. Each functional model shall identify tasks that are inherently governmental vs. tasks that are closely associated. The model must produce an audit sheet that contains all user entries (e.g. answers to model questions) and outputs (total and by labor class, etc.) for all output levels (e.g. low, mid, high range). The model must be able to report any output (total, labor class breakout, etc.)

by all output levels (e.g. low, mid, high range).

3.5 Fielding Support Deliverable:

3.5.1 Model User Manual. Develop a user manual to include step-by-step instructions (including screen shots) on how to run the Contracting model and a list at the beginning of the manual with sources of information a user will need to utilize to answer model questions. The user manual shall be worked with NAVSUP02, and any other organizations deemed necessary to relay accurate and pertinent information to the field.

3.5.2 Model Guidebook. Develop or update the main body of the model Guidebook to include changes or additions brought forward through the development of the contracting model. Provide information on the overall description of the model, rationale for why the model was developed, information into the model development and validation processes, and NAVSUP02 processes that will utilize model outputs. Include a contracting annex with information specific to the respective functional model. The guidebook shall be worked with NAVSUP02, and any other organizations deemed necessary to relay accurate and pertinent information to the field.

3.5.3 Model Demonstration and Training. Develop training materials that outlines background, data collection, and model development. Training tools should be developed for a variety of audiences to include leadership, model users, and potential trainers. Training should be developed for both interactive live demonstrations as well as training environments that are dependent on charts only. Additionally, contractor shall be available to facilitate and/or support a minimum of ten demonstration/training sessions.

3.6 Project Close Out Deliverable:

3.6.1 After Action Report. Sixty (60) days after receiving technical acceptance of the Contracting Predictive Resource Staffing Model (3.4.2) the vendor shall provide lessons learned regarding the execution of the total effort. Key areas of focus are:

• Identify challenges that arose and how they can be prevented or better managed on subsequent efforts

• Provide near- and long-term recommendations for model improvements, modifications, and updates

• Narrative will include recommendations for streamlining the processes and reducing required resources for similar modeling efforts in the future

3.6.2 Technical Data Package (TDP): 60 days from technical acceptance of the Contracting Predictive Resource Staffing Model (3.4.2) the contractor will be responsible for providing a technical data package (TDP). The government is not requiring this specific format be used, however Attachment A provides a sample template. The contractor may request a formal meeting for clarification of details required.

4. PERIOD OF PERFORMANCE (POP): 6 months upon contract award. The government requests the contractor to execute and deliver 3.1 no later than 10 days after contract award.

5. OPERATING CONSTRAINTS: The contractor shall sign a non-disclosure agreement.

6. DATA RIGHTS. The data collected, the analysis performed, the reports and materials supplied by the Contractor are the exclusive property of the Government. The Government will retain unlimited data rights to the deliverables provided under this contract.

Nothing in this PWS supersedes the terms and conditions of the data rights and intellectual property clauses incorporated in this task order or the base contract.

7. GOVERNMENT RESPONSIBILITIES: Assist contractor employees in gaining appropriate access to bases, facilities, systems, etc. as required to perform assigned functions, to include but not limited to:

• Upon contract award, conduct contractual and technical kickoff meeting with contractor

• Provide guidance and/or clarification for each deliverable as required

• Provide security badges for access to controlled areas

• Facilitate the issuance of Government CAC Cards for installation, network, and building access COMMON ACCESS

CARDS (CAC). The Government will provide special access badges as necessary for entrance to facilities. Specific Contractor personnel are required to acquire and maintain a Common Access Card (CAC). Contractor eligibility remains in force during employment under the contract for those employees who have a valid and recurring requirement for access to Army facilities or automation systems to perform those duties stipulated in the task order. The CACs shall be returned to the Contracting Officer's Representative (COR) when the Contractor employee's employment is terminated or upon expiration of the final task order under the contract. The CACs expire when Contractor eligibility terminates or the Period of Performance ends whichever occurs first.

8. GOVERNMENT FURNISHED/DATA: The contractor will submit a data request to the COR. The COR will work with system owners to provide data in a compliant format.

9. SERVICE SUMMARY: The contract service requirements are summarized in performance objectives that relate directly to mission essential items. The performance threshold briefly describes the minimally acceptable levels of service required for each requirement. The Service Summary (Table 12) provides information on contract requirements, the expected level of contractor performance and the expected method of government surveillance and confirmation of services provided. These thresholds are critical to mission success. Procedures as set forth in the FAR 52.212-4 (a), Contract Terms and Conditions - Commercial Items, Inspection/Acceptance, shall be used to remedy all deficiencies. During the first initial 30 days of the contract, two additional errors on each task shall be allowed in an effort to identify normal phase-in problem.

TABLE 1. SERVICE SUMMARY

Performance Objective

PWS

Para

Performance Threshold Remedy Method of Assessment

Type Delivery Timeframe

Project Kick Off & Planning Deliverable

3.1 Will be to define and outline the

following overview of the project;

Outline comprehensive report of key activities for model development

Upon notification of this deliverable not meeting specifications or delivery date, determine root cause of shortcomings. Implement plan of action to remedy deficiencies, and re-perform immediately.

Upon delivery Supporting 60 days after contract award

Site Survey Deliverable –

*OPTIONAL*

3.2 The contractor will incorporate the on-

site knowledge gained through key interviews with SMEs, key leadership and other members of the community by building on the on-site surveys

Upon notification of this deliverable not meeting specifications or delivery date, determine root cause of shortcomings. Implement plan of action to remedy deficiencies, and re-perform immediately.

Upon delivery Supporting 15 days after final site visit

Data Collection Deliverable

3.3 Develop an inter-organizational

Contracting task list that incorporates feedback from working group sessions, SME interviews, survey data, and other sources of published data; Develop a robust workload driver list that accounts for operational difference between the studied organizations; Develop focused interview guides and surveys tailored to address the differences across the studied organizations; Support development of data collection training materials.

Materials include but are not limited to business rules, FAQs, PowerPoint presentations, and user guides; Develop a comprehensive data report that presents narrative and illustrative information pertaining to the touch-time hour collection as well as the behavioral data gathered through other means.

Upon notification of this deliverable not meeting specifications or delivery date, determine root cause of shortcomings. Implement plan of action to remedy deficiencies, and re-perform immediately.

Upon delivery Supporting 5 business days following final pay period touch-hour collection

PRSM Development Deliverable

3.4 Provide inclusive description of the

proposed model; Delivery of final manpower model will provide forecasts of workload requirements by Full-Time Equivalent (FTE).

Upon notification of this deliverable not meeting specifications or delivery date, determine root cause of shortcomings. Implement plan of action to remedy deficiencies, and re-perform immediately.

Upon delivery Supporting 45 days after data collection deliverable

Fielding Support Deliverable

3.5 Develop a step-by-step instructional

manual on how to operate the PRSM contracting model; Develop a guidebook providing background and utilization of the model; Develop training materials that outline background, data collection, and model development.

Upon notification of this deliverable not meeting specifications or delivery date, determine root cause of shortcomings. Implement plan of action to remedy deficiencies, and re-perform immediately.

Upon delivery Supporting Concurrent with model delivery

Project Close Out Deliverable

3.6 Provide an objective description

regarding the execution of the total effort; The contractor will be responsible for providing a technical data package

(TDP)

Upon notification of this deliverable not meeting specifications or delivery date, determine root cause of shortcomings. Implement plan of action to remedy deficiencies, and re-perform immediately.

Upon delivery Supporting 60 days after model validation

10. GENERAL INFORMATION:

10.1 QUALITY CONTROL: The contractor employees shall utilize their own internal Quality Control processes in the performance of this contract.

10.2 DOCUMENTATION: The COR shall provide documentation to the Contracting Officer. The COR will maintain a complete project file. The project file shall contain copies of all deliverables, meeting minutes, reports, and any actions related to the performance of the effort. All materials shall remain intact to serve as a continuity book throughout the project such records shall be retained for the life of this contract.

Attachment A Technical Data Package for PRSM-Contracting

1. SCOPE. This attachment describes the Technical Data Package (TDP) requirements for the PRSM-Contracting.

2. APPLICABLE DOCUMENTS.

2.1 Documents. The following documents form a part of this attachment to the extent specified herein. The latest revision of the referenced documents as of the date of the contract award is applicable.

3. REQUIREMENTS.

3.1 Technical data package (TDP). The TDP shall consist of the product drawings and associated lists necessary for the re-engineering, in service engineering and support of PRSM-Contracting. These include, but are not limited to, related data and lists and descriptive specifications (see enclosure 1). The use of company standards within the TDP is acceptable, provided they are submitted without limited rights in technical data and provide necessary design disclosure as required by the contract. The information contained within the TDP shall describe the product design established at the initial Government approved product baseline and include subsequent changes and revisions up to the time of the last submittal.

3.1.1 Existing data products. Data products prepared or generated under any prior Government contracts, shall be provided if they meet the Technical Data Package Contract Requirement (TDPCR) content and quality requirements.

3.1.2 Language. All TDP elements shall use U.S. English language.

3.1.4 Supplemental requirements. The following are supplemental requirements for the TDP.

4. PREPARATION AND MANAGEMENT RESPONSIBILITY.

4.1 Drawing revisions. Revisions to the TDP shall comply with PRSM-Contracting. TDP elements or sub-elements, when found to be defective and/or rejected as unacceptable by the Government, shall not be permitted for use in formal Government technical audits, or technical final inspection.

4.2.1 TDP guidance conference. The Government will convene the TDP guidance conference ninety (90) days after contract award at the Contractor’s facility to discuss in detail the TDP requirements. The Contractor shall discuss their approach for the preparation and management of the TDP. The TDP guidance conference will, as a minimum, include the following discussion topics:

(a) Identification of contract end items, the TDP elements, and associated management data

b) Requirements for TDP elements contained in Statement of Work (SOW), Contract Data Requirements Lists (CDRLs), Data Item Descriptions (DIDs), TDPCR, and applicable specifications and standards

(c) Quality assurance procedures relating to TDP, including control of subcontractor and vendor TDP elements

(d) TDP review and inspection requirements and schedules

(e) TDP delivery requirements and schedules

(f) TDP configuration management system, including methods for releasing TDP elements, TDP validation requirements, approving TDP, and incorporating changes into the data package

(g) Organization for developing, releasing, and controlling TDP elements

(h) Review of corrective action procedures to arrive at corrected TDP submittal, as outlined in this TDPCR for documented discrepancies

(i) Establish most efficient media types and initial sample for in-process review and final submittals

(j) Review of design disclosure criteria and related interface with design compliance documents

4.2.2 In-process reviews. Periodic in-process reviews will be conducted during the development of the TDP as specified in the Contractors Master Schedule. These reviews are team meetings during which an evaluation of progress on TDP documentation is held. Reviews may be held at the Contractor’s facility or conducted off-site by the review activity.

4.2.3 Final technical review for digital deliveries. This review evaluates the final form TDP elements for contract compliance for digital deliveries. The following statements provide verification requirements.

4.2.3.1 When final delivery of the product definition data elements is to be in any other non-standard digital format, a sample (identify at guidance conference) shall be sent to the procuring activity along with a hard copy of the data files provided on digital media. These data should contain sample data and drawing files in the formats scheduled for delivery. The procuring activity and the Fleet Support Team (FST) will verify the sample digital delivery against the hardcopy to verify that the test media accurately depicts the original data files and that the delivery media will work successfully on Government equipment.

4.2.4 TDP discrepancy notification and correction. Written description and notification of TDP discrepancies uncovered and noted during, or as a result of, formal reviews and audits will be provided by the Government. Documented discrepancies shall be corrected and presented to the Government for comparison prior to the next TDP in-process review or audit.

4.2.5 Data and equipment. The following data and equipment shall be made available for inspection or select item builds to support each conference, review, or audit.

(a) Appropriate TDP elements

(b) Deviations

(c) Quality assurance data

(e) Outstanding discrepancies from previous reviews (action items)

(f) Applicable company standards, policies, procedures, and records

TABLE 1. SERVICE SUMMARY