MRO Oracle and Agile SME Support PWS DRAFT.pdf

PERFORMANCE WORK STATEMENT (PWS)

for

MAINTENANCE, REPAIR AND OVERHAUL (MRO)

Oracle and Agile Subject Matter Expert (SME) Support

ORDER NUMBER:

7 NOVEMBER 2024

Version 1.0

Table of Contents

1. Organization

2. Scope of Work

2.1. Required Support

2.1.1 Agile Requirements Manager

2.1.2 Test SMEs (DevSecOps Automated Testing)

2.1.3 Application Teams Eng – Oracle EBS/ERP expertise highly desired

2.1.4 Cloud Architect OCI Expert

2.1.5 DevSecOps Configuration Manager

2.1.6 Environments/Performance Manager

2.1.7 Strategic Planner (Technical PM)

2.1.8 Release Train Engineer

2.1.9 Kick-Off Meeting

2.1.10 Transition Planning

2.1.11 Contractor Transition at Contract Start

2.1.12 Transition at Contract Conclusion

2.1.13 Collaboration and Technical Interchange Meetings

2.1.14 Monthly Status Reports

2.1.15 System Documentation

2.1.16 Practice, Process, Policy Analysis and Adoption

2.2. Services Delivery Summary

3. Contractor Personnel Requirements

3.1 Hiring, Staffing, and Vacancies

4. General Information

4.1 Security Requirements

4.1.1 Personnel Investigations, Clearances, and Computer and Network Access

4.1.2 Common Access Card

4.1.3 Local Security Requirements

4.1.4 Security and Protection Of Information

4.1.5 Operations Security

4.1.6 Required Security-Related Training

4.1.7 In-Processing

4.1.8 Out-Processing

4.2 Place of Performance

4.3 Hours of Work

4.4 Telecommuting/Telework

4.5 Vacancies and Turnover

4.6 Travel Requirements

4.7 Privacy Act

4.8 Performance of Services during Crisis Declared by National Command Authority or Overseas Combatant Commander

4.9 Performance of Services during Emergency Conditions Declared by Wright-Patterson AFB Authority

4.10 Voluntary Protection Program (VPP)

4.11 Contractor Performance Assessment Report (CPAR) Applicability

4.12 Contracting Officer Representative (COR)

4.13 Quality Assurance

4.14 Contractor Liability

4.15 Section 8108 of Public Law 112-10 of the Department of Defense and Full Year Continuing Appropriations Act of 2011 (Contractor Inventory/Manpower Reporting under the National Defense Authorization Act (NDAA) 2012)

5. Government Furnished Property and Services

5.1 Facilities, Supplies, and Services

5.2 Workspace

5.3 Computer Resources

5.4 Access

5.5 Information Sources

5.6 Access To Personnel

5.7 Documentation

6. Points of Contact

6.1 Government Points of Contact

6.2 Contractor Point of Contact

7. Contract Data Requirements List (CDRL)

8. Revision History

1. Organization

The Maintenance, Repair, and Overhaul initiative (MRO) is a Doctrine, Organization, Training, Materiel, Leadership and Education, Personnel, Facilities – Policy (DOTMLPF-P) transformation and standardization of both the business processes and enabling materiel solution which provides Air Force Sustainment Center (AFSC) with an integrated capability for planning, scheduling, and executing organic depot maintenance to support agile planning, optimized workload assignment, resource allocation, and integrated quality. The MRO materiel solution is a web-enabled system operating wholly within the .mil network. It implements a configured Oracle enterprise Business Suite (eBS) Commercial Off-The-Shelf (COTS) software product with 'complex MRO' being the core module for user interaction. This is supplemented with the integration of other necessary eBS suite modules plus Reports, Interfaces, Conversions and Extensions-Workflows (RICE-W) objects which are deemed necessary to provide the required functionality. MRO operates within a Government-approved environment, and interfaces with various legacy systems to support continuous operations within the depot maintenance environment.

2. Scope of Work

The Scope of the Performance Work Statement (PWS) covers the tasks necessary for the successful configuration, software development, fielding, deployment, operations support, and sustainment of the MRO system. The contractor shall provide senior-level subject matter experts to support the enterprise maintenance solution through requirements management, engineering (applications, test, and performance), architecture, technical analysis, and strategic planning.

Any lessons learned and best practices will be documented and shared for re-use in future enterprise solutions.

Agile Requirements Manager shall serve as the MRO Requirements Manager/Features Manager.

Test SME shall provide support for all phases of Testing and support the Government Chief Developmental Tester in DevSecOps automated testing. Application Teams Engineer shall provide SME leadership on new solutioning activities including assisting the MRO program in designing and implementing solutions leveraging Oracle EBS modules consistent with the development of a global maintenance, supply and financial management system, including Oracle cMRO, Supply and Financials, and other families of Oracle EBS modules as applicable to meet solution requirements. The Oracle Cloud Infrastructure Architect shall handle the design improvements to the Cloud Infrastructure MRO Oracle systems are using within the Oracle Cloud. The Cloud Architect SME shall also work with Enterprise Resource Planning Common Services (ERP-CS) to help leverage more infrastructure automation, Oracle Cloud native services, more self-service options, cloud and automation best practices, and technical integration. The DevSecOps Configuration Manager shall collaborate with DevSecOps teams to integrate configuration management processes into CI/CD pipelines, ensuring secure, efficient, and reliable software delivery. Advise on the adoption of automated configuration management tools and practices to enhance deployment speed and accuracy and ensure configuration management practices align with security requirements and best practices in DevSecOps. The Performance Manager shall utilize performance monitoring tools such as Oracle Enterprise Manager, and solutions tailored to MRO requirements to provide monitoring capabilities across the various components of MRO’s architecture. The Strategic Planner shall lead the development of comprehensive strategic plans that support MRO organizational goals by analyzing software development and internal capabilities. The Release Train Engineer (RTE) shall perform as RTE for assigned release train, champion Agile methodologies, ceremonies, processes, and practices and coach/mentor scrum teams in agile best practices.

The Contractor shall have the requisite knowledge of Agile methodology and take an active role in maturing system needs to modernize capabilities, increase efficiency, and productivity for the MRO community. The Contractor shall demonstrate an understanding of Agile development in delivering useful software leveraging self-organizing, cross-functional teams focusing on adaptive planning, early delivery, continuous improvement, and flexibility to respond to customer change. The Contractor shall use Agile software development methodologies and enabling tools, Development Security and Operations (DevSecOps) practices and provide recommendations for any additional tools, manpower and support required for successful execution of the contract. All work products produced by the Contractor shall become U.S. Air Force intellectual property.

2.1. Required Support

The Contractor shall provide) dedicated FTEs at time of contract award. Work described in this PWS and as outlined in section 2.1.1 is to begin upon contract award

2.1.1 Agile Requirements Manager

The contractor shall provide a resource with the capability to perform the following:

Understand SAFe and Scrum as a framework for Agile project management Serve as the MRO requirements manager aka Features, manager Proficiently track and manage requirements using Government provided tools, Octane

(primary), MS Teams, and MS SharePoint Facilitate Government meetings intended to prioritize Features or refine the capability roadmap Provide requirements status as needed, to include but not limited to, support the

Release Train Engineer (RTE), test planning/meetings, configuration audits, and implementation planning

Produce and report agile metrics related to requirements for stakeholders, e.g., velocity, burndown, status, progress, etc., Support MRO processes needed to ensure traceability of all functional and technical requirements

Assist the risk management process by highlighting Feature dependencies that threaten timely delivery of the capability

Build and refine MRO standards and best practices for Features (requirements) Support Feature refinement meetings as needed and assist Product Owners/ Product

Managers in building Features IAW with MRO standards Identify and report active Features without current status Assist MRO PMO with Feature related inquiries as needed

Assist in integrating requirements management with other processes such as the DevSecOps process that uses other tools like FlexDeploy and Config Snapshot

2.1.2 Test SMEs (DevSecOps Automated Testing)

The contractor shall provide a resource with the capability to perform the following:

Provide support for all phases of Testing in accordance with the MRO Test and Evaluation Master Plan (TEMP)

Support the Government Chief Developmental Tester to oversee testing and participate as a member of the MRO Integrated Test Team (ITT)

Support Test Integrated Product Team(s) created by the ITT to address specific test-related topics or issues

Employ test tools specified by the Government. The Government will provide the necessary licenses and the configured instances of these test tools. The Contractor shall create and maintain all test description and reporting data (to include complete and accurate test status, release coverage and requirement traceability) within these tools

Support the effort to create and maintain automated test scripts for supported testing to the maximum extent practical

Support management of Government tester access to the test environment by facilitating, granting and management of role-based permissions to the environment with the user accounts properly associated to the organization and workload data present in the environment

Support all aspects of MRO Government Integrated Test (GIT) including facilitating deployment of the capability into the GIT instance, checkout of the installation and assisting in resolution of any issues identified during that checkout

Support Test Automation by writing scripts to automatically test product functionality and identifying areas for automation. The contractor shall monitor the operational status and use of the Automated Test service provided to MRO. Report any issues seen to the Chief Developmental Tester and take action with the MRO SI or service provider as needed to address those issues. The contractor shall participate in identification of MRO Features/Capabilities which are suitable automated test candidates and creation/maintenance of those automated test scripts

Assist in troubleshooting and the identification and correction of issues that arise in the CI/CD pipeline

Collaboration and working with development and QA Scrum teams to ensure quality

Writing and maintaining documentation for quality assurance and compliance

2.1.3 Application Teams Eng – Oracle EBS/ERP expertise highly desired

The contractor shall provide a resource with the capability to perform the following:

Provide SME leadership recommendations on new solutioning activities Assist the MRO program in designing and implementing solutions leveraging Oracle

EBS modules consistent with the development of a global maintenance, supply and financial management system, including Oracle cMRO, Supply and Financials, and other families of Oracle EBS modules as applicable to meet solution requirements

Identify, design, document, and implement alternative integrated functional and technical product solutions across all End-to-End (E2E) business processes used by

MRO

Work in teams across organizations to help the MRO PMO quickly create COAs for leadership to identify, design, and implement solutions

Provide documented recommendations on how to maximize the use of the cMRO EBS COTS software by identifying and designing possible COTS configurations that lessen the need for customization

Provide senior leadership with recommendations on design, development, and configuration of software systems to meet MRO requirements. This can include analyzing data, and working with other professionals to achieve MRO requirements

2.1.4 Cloud Architect OCI Expert

The contractor shall provide a resource with the capability to perform the following:

Has a deep understanding of cloud computing technologies, applications, and trends.

Knowledge of Oracle EBS in a cloud environment Knowledge of cloud infrastructure, software application, and design Experience using OCI, Microsoft Azure, Amazon Web Services (AWS), Google

Cloud, or other major cloud computing services Experience with various types of Cloud automations tools such as Ansible, Chef, and Terraform Strong cloud skills with an emphasis on data privacy and security Excellent problem-solving capabilities and can thrive in a fast-paced work environment Strong communication skills with the willingness to collaborate with cross-functional organizations and teams including, but not limited to, MRO’s tools/infrastructure provider

Provide and advocate for best practice cloud reference architectures with our Tools provider, development teams, PMO, and other groups as needed

Provide and advocate for Cloud Automation Architencture best practices with our Tools provider, PMO, and development teams

Experience with DevSecOps processes in a cloud environment with tools such as FlexDeploy, Gitlab, Jenkins, or other CI/CD DevSecOps tools

2.1.5 DevSecOps Configuration Manager

The contractor shall provide a resource with the capability to perform the following:

Support Release Management, Environment Management, and participate in various boards such as the Configuration Control Board, Change Control Board, Functional Review Board, Requirements Review Board, and Program Review Board. Conduct Physical Configuration Audits (PCA) and Functional Configuration Audits (FCA), record and maintain audit findings, minutes, action items, and report on SI software and CDRL delivery status, as well as review and evaluate SI adherence to CDRL requirements

Support maintaining and implementing the MRO Configuration Management Plan (CMP) as a living document. Provide configuration management (CM) of relevant program artifacts, archive acquisition documentation, and review and analyze other contractors’ CM programs and data deliveries for accuracy, completeness, and compliance. Maintain CM files, including configuration identification, change control, and status accounting records

Receive and process change requests from stakeholders, lead process reengineering discussions to achieve consensus, and update associated process documentation to reflect agreed-upon changes. Track these tasked to closure in Jira. Document and maintain all subordinate process- and procedural-level documentation within the MRO CMP and developing training materials to facilitate adherence to documented CM processes and procedures

Collaborate with DevSecOps teams to integrate configuration management processes into CI/CD pipelines, ensuring secure, efficient, and reliable software delivery. Advise on the adoption of automated configuration management tools and practices to enhance deployment speed and accuracy, and ensure configuration management practices align with security requirements and best practices in DevSecOps. Develop strategies, standards, and guidelines for CI systems

2.1.6 Environments/Performance Manager

The contractor shall provide a resource with the capability to perform the following:

Utilize performance monitoring tools such as Oracle Enterprise Manager, and solutions tailored to MRO requirements to provide monitoring capabilities across the various components of MRO’s architecture

Utilize the product vendor support, as needed, for installation, test, and configuration expertise regarding performance monitoring solutions. The components of the MRO footprint include, but are not limited to, databases, middle tiers, applications, servers, load balancer, integration software, and storage systems

Define and identify performance issues, measure and quantify performance bottlenecks, and provide suggestions with guidance and instructions for implementing corrective solutions

Work with the infrastructure hosting provider (ERP Common Services and CloudOne) and Government PMO and DBA personnel by providing guidance and instruction to optimize overall system performance

Request, review and analyze applicable system documentation (e.g., log files, system files, system reports) to assist in root cause identification of system issues

Provide guidance and instructions to resolve performance issues across the various components of the MRO product footprint

Provide a predictive performance monitoring capability and provide suggestions with guidance and instructions for implementation of changes to configurations and tuning the overall system as needed to prevent performance issues

Provide Application Performance Management (versus network) to include UX.

Splunk exp desired

2.1.7 Strategic Planner (Technical PM)

The Strategic Planner shall lead the development of comprehensive strategic plans that support MRO organizational goals by analyzing software development and internal capabilities. This involves gathering and analyzing data from various sources to inform strategic decisions, utilizing both quantitative and qualitative data to identify opportunities, risks, reduce cost and trends as well as improve the overall efficiency of execution. The contractor shall maintain close collaboration with team leads, product owners, and other stakeholders to ensure alignment of strategic initiatives across the organization. Additionally, it involves establishing key performance indicators (KPIs) and other metrics to monitor the effectiveness of strategic initiatives, providing regular updates and recommendations for adjustments. The contractor shall provide functional/mission support expertise as inputs to program-developed programmatic/engineering documentation. The contractor shall assist in establishing, integrating, and institutionalizing common standards, repeatable processes, practices, tools and persistent functions leveraging industry and DoD practices. The contractor shall assist in the development of program road maps and metrics. The contractor shall also develop and evaluate potential scenarios to anticipate changes in the business environment and adjusting strategies accordingly. Effective communication is crucial, as it involves preparing and delivering briefings on strategic plans and initiatives to senior leadership and other key stakeholders.

2.1.8 Release Train Engineer

The contractor shall provide a resource with the capability to perform the following:

Perform as Release Train Engineer (RTE) for assigned release train (e.g.

Maintenance, Supply) o Champion Agile methodologies, ceremonies, processes, and practices

Refine established processes as necessary Establish processes where needed o Maintain established Agile cadence o Facilitate PI Planning sessions for assigned release train in conjunction with

SI RTE and in coordination with other release train(s) leads o Facilitate Inspect & Adapt sessions for assigned release train in conjunction with SI RTE and in coordination with other release train(s) leads o Facilitate scrum of scrum meetings, resolution of issues, and application of best practices thereof o Coach/mentor scrum teams in agile best practices (primary focus on assigned release train and can assist with other release train(s))

Work to resolve deficiencies in standard practices and communication gaps o Keep stakeholders aware of:

Program status and progress towards current commitment Dependencies and impediments requiring attention Changes affecting resources or plans o Advise program leadership of issues and risks associated with capability development and develops recommended solutions where appropriate.

o Coordinate with other Release Train(s) Facilitate program level processes and drive continuous improvement o Manage risk, deteriorate obstacles, and interacts with stakeholders to achieve at least 80% of PI Sprint goals. Measured by planned versus actual story completion o Prepare weekly release train report for leadership, progress towards commitments, impediments, etc. using metrics and information from provided tools. Brief release train status and issues to program and senior AF/DoD leadership as needed o Work with other teams to ensure SI and Government delivered code, configurations, and data are successfully migrated through the DevSecOps pipeline using the established process, undergo Government Integration Testing, moved to production, and implemented o Continuously look for areas of improvement and recommended policy/process changes are well researched, prepared, and present to decision makers o Provide inputs on contractor Agile performance at least quarterly to Government leadership

2.1.9 Kick-Off Meeting

The Contractor shall initiate work on this order by meeting with the PMO Program Manager and support team to ensure that a common understanding of requirements, expectations and ultimate end products exists between all parties. Initial familiarization/orientation will be provided by the PMO. The Contractor shall discuss the overall understanding of the project and review the background information and materials provided by the PMO. This meeting shall be held at a location agreed upon by the PMO and the Contractor.

2.1.10 Transition Planning

The Contractor shall follow their transition plan outlined below:

ID Milestone Schedule Objectives

1 Meet with Government Task Order Lead Functional Director, the Directorate Functional Director, their staff, and the COR

NLT 15 business days after contract award

Discuss specific task order requirements and critical issues

2 All incumbents that are targeted for transition are provided offer letters

NLT 30 calendar days after contract award

To determine how many legacy Contractor personnel will transition to new vehicle and identify what additional resources will be required for full performance

3 Additional/new hires identified and offer letters issued

NLT 15 business before start of contract performance

To determine how many personnel must be acquired to meet full performance

4 Incumbents and new hires accepted into Prime’s Defense Information System for Security (DISS)

NLT 10 calendar days before start of contract performance

To confirm/initiate the security clearance process

5 Incumbent and new hire information provided to Trusted Agent to begin Common Access Card (CAC) issuance/transfer process

NLT 10 calendar days before start of contract performance

To initiate the process of issuing new CAC and transferring existing CACs

6 All Contractor employees ready to begin performance

NLT the start of contract performance

Begin performance

The Contractor shall submit applications to obtain Contractor identification badges, vehicle passes, security clearances IAW DD Form 254, DoD Contract Security Classification Specification, passports and visas (as required), Internet, and e-mail connectivity.

The Contractor shall familiarize all Contractor personnel with equipment operation and organizational workflow to include work in progress, reporting, priorities, forms, documents, scheduling, storage, safety, security, and quality control procedures. The Contractor shall make arrangements with the COR(s) to access any Government facilities. The Contractor shall not interfere with the production efforts of current Contractor personnel and shall not schedule meetings with current Contractor personnel during core work hours.

The Transition Plan shall account for all Contractor personnel to complete initial host base training and briefing requirements. The Contractor shall identify and complete the development of all work plans and procedures.

A weekly meeting will be held with the EPASS CO, EPASS PM, and COR(s) to discuss the progress of the Transition Plan, report accomplishments, and address associated risks. The weekly telecoms will be held throughout the entire performance of the transition period from 30 days prior to the task order being subsumed in this contract.

Deliverable: CDRL A004 - Software Transition Plan (STRP)

2.1.11 Contractor Transition at Contract Start

Upon Government request, the contractor shall submit a non-proprietary transition plan. This Transition Plan shall provide for the orderly start-up of maintenance and transfer of all items related to the development and maintenance of MRO, to include source code, make files and/or other build files, build instructions, configuration management tools and data, documentation, status and documentation of work-in-process and Government Furnished Property (GFP), as required. The transition plan shall include a comprehensive description of the activities and schedule required to transition the MRO sustainment, and technical support functions from the outgoing contractor to the new incoming contractor. The plan shall include:

Movement of GFP/Government Furnished Information (GFI), if required Resourcing and staffing Program Management startup activities MRO development, surveillance and operational activities Acquiring knowledge and familiarization Other topics considered necessary for accomplishing a successful transition

The contractor shall execute their transition plan to:

Allow no disruption of service to business processes after conclusion of

Transition Period Accomplish a smooth transfer of daily operations, on-going projects, development and test environments, and other assets Ensure qualified personnel, with necessary skills, knowledge and clearances are available at contract award to accomplish a successful transition Collaborate and communicate with the Government and the current contractor during the transition period Identify and manage any risks associated with the transition—particularly risks associated with human resources and GFP environment transfer, if required

Complete transition of personnel shall be completed no later than 30 calendar days after contract transition period start date.

Deliverable: CDRL A003 - Technical Report-Study/Services – Incoming Phase In Plan

(IPIP)

2.1.12 Transition at Contract Conclusion

Upon Government request, the contractor shall be required to develop a non-proprietary plan for the transition of MRO sustainment, maintenance, operations, and development responsibilities to the follow-on contractor. The transition plan shall provide a plan for the orderly transfer of all items related to the maintenance of MRO, to include source code, make files and/or other build files, build instructions, configuration management tools and data, database models, documentation, status and documentation of work-in-process and GFP, if required, to the follow-on contractor. The Transition Plan shall cover a 30-day period to include assisting the follow-on contractor in learning the MRO surveillance and operations for minimal downtime to MRO.

The contractor shall be required to answer functional and technical questions to enable the follow-on contractor to maintain and sustain MRO and interfaces. The follow-on contractor shall have the responsibility to perform these activities, but the incumbent contractor shall continue to provide support to the follow-on contractor and to Government personnel during the transition period. The contractor’s transition plan shall include a comprehensive description of the activities and schedule required to transition MRO development, maintenance, sustainment, and technical support functions from the outgoing contractor to the selected contractor.

The plan shall include:

Resourcing and staffing Program Management shut down activities MRO development, surveillance and operational activities Knowledge sharing and orientation Movement of GFP/GFI, if required Other topics or activities necessary to accomplish a smooth transition

The contractor shall execute their transition plan to:

Allow no disruption of service to business processes Accomplish a smooth transfer of daily operations, on-going projects, development/test environments, and other assets Collaborate and communicate with the Government during the transition period Identify and manage any risks associated with the transition—particularly risks associated with human resources and GFP environment transfer, if required

Deliverable: CDRL A005 - Phase-Out Transition Plan (POTP)

2.1.13 Collaboration and Technical Interchange Meetings

The contractor shall participate in Technical Interchange Meetings, e.g., with source systems needed to support planning, data collection, and/or data loading. The contractor shall also participate in MRO Program Increment planning events as a technical interchange for discussing the data required for use during each MRO Program Increment.

2.1.14 Monthly Status Reports

The Contractor shall provide a monthly status report electronically during the period of performance. The report shall include the status of all functional areas addressed in this PWS and shall include status of work, schedules, deliverables, current and cumulative task funding status (direct labor and travel funding status to be reported separately as required), risks and risk mitigation techniques, outstanding issues, and proposed resolution approaches and actions to resolve any outstanding issues. The report shall identify milestones and deliverables completed and progress towards major milestones and deliverables (showing planned data deliveries down to the organizational unit level). The report shall identify activities and deliverables planned but not completed including the Government acknowledgement and approval of the incomplete work. The contractor shall include metrics that demonstrate remaining work is achievable within required timelines.

The monthly status report shall be submitted simultaneously with the monthly invoice. The Contractor shall ensure the accuracy of the monthly status report which must include:

Master task order schedule to identify status of all scheduled tasks, explanation of deviations from the baseline schedule, and forecast schedule impacts

Project metrics, analysis of trends, and corrective action plans Planned accomplishments for the next reporting period Resource levels and explanation of resource changes Issues requiring resolution Status of all assigned action items Current task order risks and risks mitigation plans and activities Short overview of data delivered during reporting period

Deliverable: CDRL A001 - Monthly Status Report (MSR)

2.1.15 System Documentation

The Contractor shall provide technical studies and updates to system documentation as required.

Existing Government word processing tools (MS Office Suite of tools) shall be used for documentation. This is a continuous effort, which shall be accomplished in concert with the efforts to update and enhance system operations. The Contractor shall update system documentation as necessary to reflect solutions used to satisfy the Change Requests (CRs), Discrepancy Reports (DRs) and Action Items (AIs). Results of these efforts shall be documented in the monthly status report CDRL A001.

Deliverable: CDRL A001 - Monthly Status Report (MSR)

The Contractor shall provide ad hoc Technical Report(s) or Studies as requested by the Government, at no additional charge, if the information requested is currently available or easily modified from existing data. The Contractor shall make every reasonable effort to provide additional or non-customary reports or data as requested by the Government, regarding its Operations and Infrastructure of MROi. The Government will provide one week notification for any ad hoc report and study requests, and will work with the contractor to agree on a delivery date of said report or study. Reports shall be provided in a Government defined format and within the Microsoft software suite where applicable or to an agreed upon format based on its intended use.

2.1.16 Practice, Process, Policy Analysis and Adoption

Best practice support shall include, but is not limited to, best practice research, benchmarking studies, COTS and enterprise system industry best practices, and recommendations to support all aspects of data management capability design, development and implementation. The Contractor shall evaluate, analyze, and document any proposed best practices to assess their impact on the mission area and the enterprise and recommend data management practices, processes, and policies to the Government.

2.2. Services Delivery Summary

Performance Objective

PWS

Para.

Performance Standard

Performanc e Threshold

Surveillance Method

Incentive/ Remedy

(SS-1)

Ensure documentation is delivered on-time in accordance with the applicable CDRL

2.1.10, 2.1.11, 2.1.12, 2.2.13, 2.1.14, 2.1.15, 4.5, 4.6

The contractor shall provide the applicable documents by the due date and time specified in Exhibit A.

100% compliance with no deviation from performance standard

100% Inspection and review upon receipt of report

Failure to meet 3 delivery dates will result in the remedies set forth in FAR clause 52.246-4, Inspection of Services – Fixed Price and a negative comment in

CPAR.

Re-performance and redelivery is required.

(SS-2)

Provide accurate Technical and Planning documentation and Execution results

2.1.10, 2.1.11, 2.1.12, 2.2.13, 2.1.14, 2.1.15, 4.5, 4.6

Deliverables shall meet the requirements of the content stated in the CDRL. Documents are written with clarity, accuracy, and without grammatical errors or misspellings. The technical documents must thoroughly capture results of the analysis to include background details, analytical methodology employed, summary, and any recommendations or suggestions.

100% compliance with no deviation from performance standard

100% Inspection and review upon receipt of report

Unacceptable performance will result in the remedies set forth in FAR clause 52.246-4, Inspection of Services – Fixed Price and a negative comment in CPAR.

Re-performance and redelivery is required.

(SS-3)

Hiring practices fill all vacancies

3.1 The Contractor shall

maintain the overall minimum team positions for program roles within 30 calendar days of the confirmed departure date.

Vacancies are not considered filled until the Contractor submits an updated VAR, adds personnel in DISS/NBIS, and submits an investigation request to the Government. If filled vacancies are not granted interim access (within 60 calendar days of submitting an investigation request to the Government) via the DoD's investigation process and are eligible for a CAC, then the filled vacancy will be considered unfilled.

Overall team minimum positions will be considered met if 95% of all resources are actively performing work on the contract.

100% compliance with no deviation from performance standard

100% surveillance

- Unacceptable performance will result in a PCOL

- Corrective Action Report (CAR)/Contract Discrepancy Report (CDR)

- Re-performance and redelivery

- Remedies set forth in FAR clause 52.246-4, Inspection of Services – Fixed Price

- Negative comment in

CPAR

(SS-4)

Quality:

Compliance with security requirements

Documents are written with clarity, accuracy, and without grammatical errors or misspellings. The documents must thoroughly capture results of the analysis to include background details, analytical methodology employed, summary, and any recommendations or suggestions.

Performance is considered satisfactory when there is 100% compliance with security requirements.

100% surveillance

COR and Project Lead Monthly Review

(SS-5)

Quality of Service Effective Communication:

Effective, professional contractor interaction with Government

PM,

Program Office, user personnel, and/or other contractors.

Performance is considered acceptable when no more than two (2) valid complaints are reported to the PM per Period of Performance (PoP).

Customer Compliant

Acceptable Quality Level (AQL): The Contracting Officer Representative (COR) or Program Manager (PM) will track customer complaints and give the contractor opportunity to apply corrective action or dispute the complaint.

The contractor shall respond to each complaint within five (5) business days and include a Corrective Action Plan (CAP). Such a CAP must be reviewed and approved in writing by the Contacting Officer (CO), or

COR.

If the contractor fails to provide an acceptable CAP or fails to perform in accordance with the approved CAP, the Government may request consideration on an ongoing basis until such a plan is provided, approved, and effectively enacted.

The results of the approved CAP shall be evaluated by the CO or the COR after a period of 10 business days.

If the CAP is determined to be successful, the matter shall be closed. If the CAP is determined to be unsuccessful, the CO or the COR may request a revised CAP or begin proceedings for Termination.

(SS-6)

Timeliness:

Contractor provides timely responses to technical and functional information requests.

Performance is considered acceptable when the contractor provides responses according to suspense dates 95% of the time per quarter, and the remaining 5% are delivered within two (2) business days.

100% Surveillance

AQL: Technical and Functional information requests are satisfactory when no more than 5% are late per quarter.

Performance is unsatisfactory when 6% or more of the Technical and Functional information requests are late per quarter.

At any time that 6% or more of any technical and/and or functional information requests are late during any deliver order period of performance, the CO or COR may request a CAP.

Such CAP shall be provided, in writing, within five (5) business days. The CAP must be reviewed and approved in writing by the CO, or COR.

If the contractor fails to provide an acceptable CAP or fails to perform in accordance with the approved CAP, the Government may request consideration on an ongoing basis until such a plan is provided, approved, and effectively enacted.

The results of the approved

CAP shall be evaluated by the CO or the COR after a period of 10 business days, or as it applies to the next three (3) deliveries. If the CAP is determined to be successful, the matter shall be closed. If the CAP is determined to be unsuccessful, the CO or the COR may request a revised CAP or begin proceedings for Termination.

(SS-7)

Quality:

Contractor provides complete and accurate responses to technical and functional information requests and completion of hands-on training requirements.

Performance is considered acceptable when 95% of the contractor responses received are delivered according to information request content requirements and instructions without rework required per quarter, and the remaining 5% of responses are complete and accurate within two (2) business days.

100% Surveillance

AQL: Deliverables are satisfactory when 5% or less are returned for rework. Performance is unsatisfactory when 6% or more of the deliverables require rework.

At any time that 6% or more of any deliverables require rework, the CO or COR may request a CAP.

Such CAP shall be provided, in writing, within five (5) business days. The CAP must be reviewed and approved in writing by the CO, or COR.

If the contractor fails to provide an acceptable CAP or fails to perform in accordance with the approved CAP, the Government may request consideration on an ongoing basis until such a plan is provided, approved, and effectively enacted.

The results of the approved CAP shall be evaluated by the CO or the COR after a period of 10 business days.

If the CAP is determined to be successful, the matter shall be closed. If the CAP is determined to be unsuccessful, the CO or the

COR may request a revised CAP or begin proceedings for Termination.

(SS-8)

Management of Personnel:

Contractor hires, retains, and/or replaces personnel as required.

Performance is considered acceptable when Contractor provides qualified personnel within thirty

(30) business days of Gov’t request 95% of the time. The remaining 5% are provided within 45 business days.

100% Surveillance

AQL: Contractor shall be notified of their “unacceptable” results in a PCOL from the contracting officer for this program. As part of the PCOL, the Contractor shall be required to present a corrective action plan to Government within 5 business days. If the Contractor continues :unacceptable” performance, it will be reflected in the CPARS rating, and the Government may further enforce all available remedies under the Contract.

3. Contractor Personnel Requirements

The Contractor shall provide continuous staffing with sufficient experience, training and expertise in the areas of MRO systems, including business analysts and report writing personnel.

The Contractor shall meet all requirements specified in DOD 8570.01-M for their designated category and specialty (e.g. IAT-II). DOD 8570.01-M requirements include and are not limited to:

Continuous Education Information Assurance (IA) Baseline Certification Initial On the Job Training (OJT) Evaluation Continuous Education Computing Environment/Operating System (CE/OS) Certificate Background Investigation Signed Privileged Access Statement

Personnel shall be capable of demonstrating the functionality of MRO systems from a tactical perspective as well as from a strategic perspective. The Contractor shall use proven engineering techniques to perform the tasks required by this delivery order and shall employ commercial best practices and innovative solutions where not in conflict with Government requirements. All Contractor personnel shall have experience using the suite of Microsoft Office products, including Word, Excel, PowerPoint and Access. The Task Leader shall provide other contractor personnel assigned to this task with required management direction and support to include required preparation and delivery of contract deliverables, and other actions as deemed necessary by the Task Leader. The Task Leader shall also assign and direct tasks to the various contractor personnel assigned to this contract, as required by the Government.

3.1 Hiring, Staffing, and Vacancies

The Contractor shall establish processes and assign appropriate resources to effectively administer the requirement. The Contractor shall provide for all management and support of Contractor personnel. The Contractor shall assign tasks and maintain proper and accurate time keeping records of personnel assigned to work on the task order. The Contractor shall maintain a stable workforce while minimizing the impact of any turnover and/or disruptions to the Government and/or mission.

The Contractor shall ensure continuation of services during personnel absences due to sickness, leave, and voluntary or involuntary termination from employment such that there is no negative impact to the Government mission.

Upon notification of a pending vacancy, the Contractor shall provide written documentation to the CO, COR and ACOR. This written notification shall include the date and time the position will be vacant, anticipated replacement date, and plan to ensure task mission (given the vacancy) is not impacted or degraded.

Additionally, the Contractor shall maintain the overall minimum team positions for program roles within 30 calendar days of the confirmed departure date. Vacancies are not considered filled until the Contractor submits an updated VAR, adds personnel in DISS/NBIS, and submits an investigation request to the Government. If filled vacancies are not granted interim access (within 30 calendar days of submitting an investigation request to the Government) via the DoD's investigation process and are eligible for a CAC, then the filled vacancy will be considered unfilled. If the vacancy cannot be filled within the required 30 calendar days, the Contractor shall provide written notification to the CO containing rationale for the unfilled vacancy, anticipated replacement date, and plan to ensure task mission (given the vacancy) is not impacted or degraded. When a vacancy is filled, an updated VAR shall be submitted to the Government. The CO may direct removal (permanent or temporary) of personnel for security, safety, or health reasons, upon discovery of fraudulent credentials/qualifications, or when Contractor personnel behave in an unprofessional manner that would be considered unacceptable by a reasonable person.

4. General Information

4.1 Security Requirements

Any information, records, or data the Contractor may have access to may be highly sensitive.

The Contractor shall not divulge any information about Government files, source selection activities and processes, or any other sensitive information to anyone not authorized access to such information. The Contractor may be required to sign a non-disclosure agreement (SF Form

312) to access sensitive or classified information. It shall be the Contractor's responsibility to ensure that their personnel have the proper authorities. The contractor shall ensure the MRO system complies with security regulations stated in this PWS.

The contractors shall comply with the Defense Acquisition Regulations (DFARS) 252.239-7001 and all cybersecurity requirements stipulated in the contract.

Contractors shall submit to the Contracting Office (CO) and Government Program Manager a list of personnel who require a Common Access Card (CAC) and Government-Furnished Equipment. The contractor shall identify each person by full legal name, their proposed assigned position, duty location, security clearance required by the contract, the company for which they work, full contract number (including task order, if applicable), and the contract end date. The prime contractor shall include the information for all subcontractors. If applicable, the personnel list shall also identify persons who need SIPRNET and/or Privileged Access. For privileged access, the list shall explicitly specify which Information Technology (IT) Level – I or II – is needed.

4.1.1 Personnel Investigations, Clearances, and Computer and Network Access

The Contractors performing work under this contract must comply with all applicable security requirements. Contractor personnel shall have the appropriate security background investigation or security clearance (i.e., eligibility) prior to the performance of duties in support of this contract. Contractor Personnel must have, at a minimum, a favorable Tier 3 Investigation prior to network access and issuance of a Common Access Card (CAC). Contractors necessary to perform DevSecOps and/or database/application work within all Government-approved environments to include, but not limited to: OCI, and CloudOne shall be required to have IT Level I access. IT Level I access requires a favorably adjudicated Tier 5 Investigation. See AFI 61-1405, Personnel Security Program Management, Wright-Patterson AFB Supplement 1 for more information regarding security investigation and clearance requirements.

4.1.2 Common Access Card

IAW DoDI 5200.46, DoD Investigative and Adjudicative Guidance for Issuing the Common Access Card, Enclosure 4, Paragraph 3, Application of the Standards; DoDI 5200.02, Personnel Security Program; Homeland Security Presidential Directive (HSPD)-12; and AFMC Guidance for the Credentialing of Un-cleared Contractors, 13 November 2018, Attachment, Paragraph 5a eligible contractor personnel requiring physical access to a DoD or AF facility or installation as their normal work location; the Air Force Network (AFNet); a DoD Automated Information System (AIS); Controlled Unclassified Information (CUI), or any equipment not involving access to classified information shall obtain Common Access Cards (CAC).

Interim issuance of a CAC to a contractor requires the completion of a Federal Bureau of Investigation (FBI) fingerprint check with favorable results and the successful submission of Tier l (equivalent or higher) background investigation to the Defense Counterintelligence and Security Agency (DCSA).

A final CAC determination requires a favorably adjudicated Tier 1 (equivalent or higher) investigation based on the basic and supplemental HSPD-12 credentialing standards as outlined in DODI 5200.46, Enclosures 3 and 4.

Once the request for a CAC has been approved, the employee shall go to Military to any local Defense Enrollment Eligibility Reporting System (DEERS) office to obtain their CAC.

Contractor badges shall be worn and displayed at all times. In addition, the Contractor employee shall identify themselves as Contractor employees in e-mails, telephone usage, correspondence, and meetings, etc.

Contractors must maintain the satisfactory minimum requirements for justification of the issuance of a CAC throughout the period of performance.

Contractor personnel shall, within seven calendar days, return all identification badges and/or CAC to the AFLCMC/HI (WP) Security Office upon termination, separation, or expiration of this contract.

4.1.3 Local Security Requirements

The Contractor shall be responsible for assuring that all employees comply with all security requirements imposed by the local commander at all times while their employees are on the installation and shall follow instructions of the local organizational commander pertaining to security. Local Security requirements can be found on Appendix A.

4.1.4 Security and Protection Of Information

Controlled Unclassified Information (CUI) o Controlled Unclassified Information is any information that law, regulation, or Government-wide policy requires to have safeguarding or disseminating controls. CUI excludes information classified by:

o Executive Order 13526, Classified National Security Information, December 29, 2009 o The Atomic Energy Act of 1954, as amended, or o A specific program or project Security Classification Guide

The National Archives and Records Administration (NARA) CUI Registry (http://www.archives.gov/cui/registry/category-list.html) identifies approved CUI categories and subcategories; provides general descriptions for each; identifies the basis…