MABSM PWS SS April 2025.pdf

PERFORMANCE-BASED WORK STATEMENT (PWS)

MAINTENANCE BUSINESS SYSTEM MODERNIZATION (MABSM)

IMPLEMENTATION & SUSTAINMENT SUPPORT FOLLOW-ON

U.S AIR FORCE OO-ALC

Updated:

3/5/2025

DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited.

MAINTENANCE BUSINESS SYSTEM MODERNIZATION (MABSM) IMPLEMENTATION &

SUSTAINMENT SUPPORT FOLLOW-ON

i

TABLE OF CONTENTS

1 DESCRIPTION OF SERVICES

2 BASIC SERVICES

2.1 BASIC REQUIREMENTS

2.2 SUSTAINMENT

2.3 IMPLEMENTATION

2.4 SPECIAL PROJECTS

2.5 KNOWLEDGE TRANSFER

3 SERVICES SUMMARY

4 CONTRACT DATA REQUIREMENTS LIST (CDRL) SUMMARY

5 GOVERNMENT FURNISHED PROPERTY AND FACILITIES

5.1 WORKSPACE

5.2 GFE / GFP

6 GENERAL INFORMATION

6.1 INSTALLATION SPECIFIC SAFETY & HEALTH STANDARDS

6.2 CERTIFICATIONS AND TRAINING REQUIREMENTS FOR CONTRACTOR

6.3 SECURITY REQUIREMENTS

6.4 CONFLICTS OF INTEREST

6.5 QUALITY CONTROL PLAN

6.6 HOURS OF OPERATION

6.7 TRAVEL REQUIREMENTS

6.8 CONTINUATION OF ESSENTIAL DOD CONTRACTOR SERVICES DURING

CRISIS

6.9 REPORTING OF CONTRACT LABOR HOURS/MANPOWER REPORTING

6.10 CONSERVATION OF UTILITIES

6.11 INTELLECTUAL PROPERTY

6.12 INHERENTLY GOVERNMENTAL FUNCTIONS/PERSONAL SERVICES

6.13 GOVERNMENT PROGRAM MANAGEMENT

6.14 GOVERNMENT CONTRACT MANAGEMENT

6.15 RECORDS, FILES, AND DOCUMENTS

6.16 PHASE IN/OUT PERIOD

6.17 APPENDICES

Appendix A – ACRONYMS & ABBREVIATIONS Appendix B .................................................................................... Error! Bookmark not defined.

MAINTENANCE BUSINESS SYSTEM MODERNIZATION (MABSM) IMPLEMENTATION &

SUSTAINMENT SUPPORT FOLLOW-ON

ii

Appendix C – SAFETY Appendix D – GROUP NUMBERS .............................................. Error! Bookmark not defined.

Appendix E – APPLICATION & SYSTEM TRAINING ............. Error! Bookmark not defined.

Appendix F – TRAVEL ................................................................. Error! Bookmark not defined.

Appendix G – PUBLICATIONS / INSTRUCTIONS ................... Error! Bookmark not defined.

Appendix H – USER GUIDES & TRAINING MANUALS ......... Error! Bookmark not defined.

1 DESCRIPTION OF SERVICES

The purpose of this PWS is to provide implementation, sustainment, special project, and training services for the Maintenance and Business System Modernization (MABSM) system, the Maintenance Repair Overhaul (MRO) system of record for Ogden Air Logistics Complex (OO- ALC), for continued support at OO-ALC, as well as Warner-Robins Air Logistics Complex (WR-ALC), Oklahoma City Air Logistics Complex (OC-ALC), including all internal groups and geographically separated units (GSUs).

MABSM is the government owned, based on a currently outmoded version of the commercially available, Impresa software that has been heavily modified to incorporate the business logic that allows it to function successfully as the MRO system for OO-ALC. This functionality allows the system to work within the organizational structure of an Air Force (AF) depot and follow key processes down to the individual Resource Control Center (RCC) level. For this reason, the contractor shall possess and apply specific knowledge of the business logic that corresponds to the organizational structure and processes unique to AF depot operations to implement MABSM.

The contractor shall provide on-site project management, technical analysis and services, and training of Government personnel. These services shall include all business management oversight, data configuration management, process standardization, and user/configuration functional training services required to fully implement and sustain MABSM. The contractor shall plan, manage, organize, direct, schedule and control all resources, processes, activities, and tasks to accomplish the requirements of this PWS through specific task orders provided by the Government in a PWS or Statement of Objective (SOO).

2 BASIC SERVICES

2.1 BASIC REQUIREMENTS

2.1.1 System Manager

2.1.1.1 The contractor shall identify to the Government and maintain a single point of contact (Program Manager or equivalent) with sufficient corporate authority to direct, execute and control all elements of this contract (see Appendix I for historical data). The point of contact shall possess an America Production and Inventory Control Society (APICS) credential. The APICS certificate shall be provided at the time of proposal, 15 days after any certificate renewal, and 15 days after any option period is exercised. The contractor shall be responsible for implementing and maintaining work standards and processes, delegating contractor/subcontractor assignments, supervising contractor personnel, and communicating policies, purposes, and goals to subordinates. The contractor shall be accountable for overall surveillance of contract employees, contract compliance, contract performance, the operational success of assigned tasks, and customer satisfaction.

2.1.1.2 The contractor System Manager shall oversee daily MABSM operations; provide programming and troubleshooting for application improvements, requirements, and software life-cycle management IAW industry best practices, applicable AF/DoD standards and IAW established processes. (Appendix G)

2.1.1.3 The System Manager shall ensure Government directed IT Service Management Tools (ISMT) and Change Management Processes are used to address customer issues and vet new requirements for approval prior to initiating solutions implementation.

2.1.2 MABSM Certification and Accreditation

2.1.2.1 The contractor shall provide support services to obtain Information System Certification & Accreditation IAW AFI17- 101; Risk Management Framework for Air Force Information Technology, and DoDI 8510.01; Risk Management Framework (RMF) for DoD IT Services to include, but not limited to:

2.1.2.1.1 Designing and documenting the Information Assurance (IA) plan as well as testing and validating IA controls, including the functions of the IA controls.

2.1.2.1.2 Gathering documentation, as requested, to support RMF Certification and Accreditation processes.

2.1.2.1.3 Implementing and executing the IA plan to include

validation testing and review results.

2.1.2.1.4 Working with Air Force Accrediting Authority to obtain Certification & Accreditation (C&A).

2.1.2.1.5 Performing continuous monitoring of system IA posture and IA control practices.

2.1.3 Meeting Support

2.1.3.1 The contractor shall attend or support specific meetings as requested by Government PM and/or COR. Examples of these meetings include staff meetings, production meetings, configuration review boards, product focus team meetings, and other scheduling, planning, and material management meetings.

The contractor shall also support and/or attend meetings with organizations outside the ALCs regarding MRO applications and methods. The contractor will be notified of regularly recurring scheduled meetings and 24 hours advanced notice of other meetings they will be required to attend.

2.1.3.1.1 The contractor shall attend unplanned meetings as

circumstances arise in which critical project or task updates are required by the Government. These meetings may have little or no previous notification times.

2.1.3.1.2 The contractor shall provide capabilities presentations and/or demonstrations as requested by the Government.

2.1.4 Monthly Summary/Reporting

2.1.4.1 The contractor shall capture all issues and document all new requirements identified by the customer, in the Monthly Status Report. (CDRL A001)

2.1.5 Quality Control Plan

2.1.5.1 The contractor shall comply with all requirements identified in section 6.5 Quality Control Plan.

2.1.6 Contractor Employees: Contractor employee(s) tasked with programming or application maintenance shall have at minimum ten (10) years of experience with programming Oracle and Java in use of an MRO application in supporting depot maintenance environment/operations.

Requirements include a minimum ten (10) years of experience in the development and support of MRO applications to perform lifecycle sustainment to include design, development, and implementation of application modifications.

2.1.7 Business Logic: MABSM is a government owned MRO system which incorporates extensive customizations and business logic which allows it to function successfully within the organizational structure of the Air Force (AF) and follows key processes down to the individual Resource Control Center (RCC) level. For this reason, the contractor shall possess and apply specific knowledge of the business logic that corresponds to the organizational structure and processes unique to AF depot operations.

2.1.7.1 The contractor shall provide personnel who have experience working with an MRO application in a Department of Defense (DoD) environment and shall have experience working with Air Force Legacy. The contractor shall know the differences between overhaul, repair, new manufacturing, modification, test/evaluation, and demilitarization efforts and how they affect AF supply chain management disciplines, policies, and procedures.

2.1.7.2 The contractor shall provide personnel who have expertise and experience in development of wireless technologies for use with MRO applications. This environment is currently not being utilized; however, it is anticipated that wireless technology may be required in the future. The contractor shall comply with DoD Directive 8100.02.

2.1.7.3 The contractor shall provide business process improvement recommendations to improve customer data systems through business process redesign, including modifying program design, and aligning information technology with business missions, goals, and objectives using industry best practices (i.e. gated processes and electronic work control documents).

2.1.7.4 The contractor shall evaluate suitability of business process improvement tools and methodologies.

2.1.7.5 The contractor shall acquire, install, and utilize new tools and methodologies in conducting business process improvement tasks.

2.1.8 User Guides

2.1.8.1 The contractor shall create and implement a system for creating or expanding upon existing user guides (CDRL A010 – User Guides). The contractor shall include an overview, summary and conclusion to each topic presented in a user guide. User guides shall include, but are not limited to, documented user guides and any of the reports within MRO Applications. User Guides shall be written from an understanding of the basic user to that of an expert.

2.1.8.2 The contractor shall ensure that the user guides provide detailed, step by step, comprehensive instructions and explanations of all MABSM functions. User guides shall explain how the MABSM data input affects legacy systems and all areas within MABSM.

2.1.8.3 Upon release of any software updates, the contractor shall review existing guides within the MRO Applications Reporting system to determine if updates are required.

2.1.8.3.1 For new features, the applicable user or process guide (CDRL A010 – User Guides) shall be delivered to the Government within sixty (60) calendar days.

2.1.8.3.2 When an RFC requiring modification to MABSM is

completed, the existing guide shall be updated within thirty

(30) calendar days.

2.1.8.3.3 The contractor shall create and update the master guide list to be included in the monthly status report (CDRL AXXX -

MSR).

2.1.9 Architecture and Application Design

2.1.9.1 The contractor shall support the customization and modification of MABSM to match the existing, overarching enterprise architecture. All changes must be approved through the Configuration Control Board (CCB) process (see paragraph 2.3.4.2) prior to start.

2.1.9.2 The contractor shall provide all documentation associated with supporting architecture for any frameworks including but not limited to, line routing, kitting, back shop support, and material procurement (CDRL A007 – Supporting Architecture). This documentation shall be delivered within three (3) business days following release of the feature. Corrections requested by the Government shall be delivered within five (5) business days of request.

2.1.9.3 The contractor shall produce high quality code and provide the source code as requested by the government for internal or external quality scans. The Government will assess code quality via third party codebase scan or other available means following completion of MABSM implementation or at any other time as appropriate, specified at the task order level. Code shall meet the following quality parameters:

Table XXX-1: Code Quality

Code Attributes Threshold

Duplication < 15%

Modularity > 85%

Cyclicality > 85%

2.1.10 Application Functionality Testing

2.1.10.1 The contractor shall perform application functionality user acceptance testing to verify software and external interface functionality. The contractor shall ensure customer verification, validation and approval of any system changes prior to any changes being implemented into the production environment.

2.1.10.1.1 The contractor shall ensure that the function, supportability, and performance of the MABSM application are not degraded by any approved changes.

Approved application design change enhancements or upgrades to the MABSM application shall be updated in the applicable user guides (CDRL A010 – User Guides) within 30 calendar days of release.

2.1.10.2 A Software Version Description (SVD) (CDRL A008 - SVD) document shall be delivered five (5) business days prior to each formal release to identify all changes that are incorporated into the release.

2.1.11 Lifecycle Management

2.1.11.1 The contractor shall provide data records management and configuration management. The contractor shall review, audit, validate, amend, and perform corrections to application data input in MABSM daily.

2.1.11.2 The contractor shall manage the document control process that includes research, document development, test, release and archive using industry standards for records management. This shall be included in the technical reports/white paper reports as required (CDRL A009 – Technical/White Paper Reports).

2.1.11.3 The contractor shall manage the lifecycle process for application and process development, improvements, upgrades, implementations, refreshes, sustainment and maintain Capability Maturity Model Integration (CMMI) Level II certification.

2.1.11.4 The contractor shall maintain accurate lifecycle status for all tasks and projects in work in MABSM. The contractor shall maintain a digital status tracker for all tasks and projects in work in a location (SharePoint, Shared Drive, etc.) that is always accessible to the Government. The tracker shall identify project tasks, start dates, estimated and actual completion dates, assigned resources and update with status daily.

2.1.11.4.1 Contractor shall attend and report scheduled regular progress meetings to ensure accurate project and lifecycle information, as well as identify tasks requiring escalation or reassessment.

2.1.11.5 The contractor shall create and sustain optimal structure and content for items, bills of material, shop routings, and other data critical to Material Requirements Planning (MRP) processing and material supportability.

2.1.11.6 The Contractor shall use 75 ABW/SC directed ITSM tools or practices to receive, track, and implement application lifecycle activities.

2.1.12 Security Patching

2.1.12.1 The contractor shall ensure information systems are made available to the government for continuous updates with the latest software and security patches to minimize security vulnerabilities. Patches and updates shall not impact system availability IAW paragraph 2.3.1.1.

Information systems, desktops, and supported peripherals shall be certified and accredited to comply with the DoD system security policies before they can be added to the network IAW DoDI 8510.01;

RMF for DoD IT Services.

2.1.12.1.1 The contractor shall protect system information and resources according to established security policies and procedures and ensure application code is updated with the latest security patches to minimize security vulnerabilities.

2.1.12.1.2 Notify the Host and Functional Management Office

(FMO) of any planned or emergency security patching.

2.1.12.1.2.1 The contractor shall provide a minimum of 10

business days of notice to the Host and FMO prior to planned security patching.

2.1.12.1.2.2 The contractor shall notify the Host and FMO

immediately upon identification of emergency security patching requirement(s).

2.1.12.1.3 The contractor shall code per FMO approval and

direction.

2.1.12.1 The contractor shall resolve all Security Technical Implementation Guide (STIG) findings within the following time frames, exempting any government-imposed delays.

Table 2-2

Threat Level Response Time

Critical 10 Calendar Days

High 15 Calendar Days

Medium 30 Calendar Days

Low 45 Calendar Days

2.1.12.2 All open STIG findings shall be reported in CDRL A002 - MSR including date of finding, scheduled and actual dates of resolution (for all STIGs resolved within the previous 30 calendar days).

2.1.13 End-User Training

The contractor shall provide training for all levels of MABSM users. The contractor shall provide formal classroom training, On-the-Job Training (OJT), and ad-hoc training as appropriate to the learning content. Specific training requirements may be defined at the task order level.

2.1.13.1 Master Training Plan: The contractor shall provide a comprehensive MTP (CDRL A006 – MTP) with each task order proposal. The plan shall provide a detailed schedule to include all planned training tasks associated with MABSM end-user training. The plan shall encompass implementation tasks and the minimum required training for new users as outlined in Appendix E. The plan shall identify which content will be instructed in the formal classroom setting, outline the contractor’s approach to OJT or other methods not conducive to classroom instruction, as well as a method for complying with ad-hoc training requests from the Government PM.

2.1.13.2 Training Reporting: The contractor shall document each training session conducted, reporting attendees, times, dates, and overview of what was trained, each month in CDRL A002 - MSR. The contractor shall provide any required documentation to the appropriate Production Acceptance Certification (PAC)/Training Schedule System (TSS) representative for tracking/verification of training completion within two (2) business days of training completion (CDRL A011 – Training Records).

2.1.13.3 Formal Classroom Training: The contractor shall provide formal classroom training to designated personnel using Government facilities. All training shall contain the “how to” performance functions in area such as queries, reports, asset visibility, job routing procedures, application reporting, scheduling and planning procedures, material ordering. The contractor shall utilize the most up-to-date course material consistent with the most recent system updates.

2.1.13.3.1 The contractor shall develop course material that

incorporates existing government training material where applicable. Course material (CDRL A012 – Training Courseware) shall be provided to the Government training office within 15 calendar days of any updates to existing course content or 45 calendar days for new courses.

2.1.13.4 On the Job Training: The contractor shall conduct OJT as outlined in their proposed MTP. This training shall provide one-on-one and small group training to target specific system task proficiencies within the MABSM system.

2.1.13.5 Ad-Hoc Training: Ad-hoc training shall be provided on an as needed basis as requested by the government PM. Ad-hoc training may be formalized classroom training or OJT and may cover unscheduled, existing training topics and objectives or specific MABSM training topics and objectives that are not covered by the contractor’s MTP. The Government does not anticipate the ad-hoc training burden to exceed 20 hours per month. The contractor shall address Government requests for ad-hoc training requests by providing a response to the Government PM within two (2) business days of request. The training shall be accomplished within five (5) business days of request or as outlined in the contractor’s MTP unless an exception is granted by the Government PM.

2.2 SUSTAINMENT

2.2.1 MABSM Availability

2.2.1.1 Contractor shall not disrupt MABSM availability during business hours.

Business hours include all regularly scheduled shifts and scheduled overtime. The Contractor shall notify and seek approval from the Government PM of all planned system outages to ensure every effort is made to schedule any planned outages outside of business hours.

Additional system availability requirements may be defined at the task order level.

2.2.1.2 Un-planned system disruptions caused by the contractor shall not exceed two (2) business hours each calendar month.

2.2.1.3 The contractor shall report application outages anticipated to last 1 hour or more to 75 ABW/SC Communications Focal Point (DSN: 586-8888, Commercial 801-586-8888). During regular business hours contractor shall notify Government PM of any outages within 15 minutes.

2.2.1.4 The contractor shall provide status updates and the actions the contractor intends to take to resolve the stated problem(s) via email or phone.

2.2.1.5 The contractor shall notify MABSM users of any data integrity issues or discrepancies within 24 hours and upon resolution.

2.2.2 Interface Management

2.2.2.1 The contractor shall maintain operation of all required system and application interfaces.

2.2.2.2 The contractor shall provide technical and/or specialized guidance in the operation and application of the MABSM software interfacing with other systems, both automated and manual.

2.2.2.3 The contractor shall document all existing and new interfaces in an Interface Control Document (ICD) and keep them up to date in the Corporate Data Repository System (CDRS).

2.2.3 User Access Management

2.2.3.1 answer technical queries/reports; be responsible for documenting the system configuration; sustain application, troubleshoot, and resolve any reported problems; provide application performance tuning; ensures use of DoD 2875 policy, provide functional assistance; and provide any reporting or query requirements summaries in the Monthly Status Report. (CDRL XXX1)

2.2.3.2 The contractor shall provision user accounts such as adding, deleting, and modifying user account information, roles, passwords, and privileges.

2.2.3.2.1 Contractor shall resolve new user adds/changes within one

(1) business day of request with exception of implementation provisioning of an RCC (see paragraph 2.1.6).

2.2.3.2.2 All user account changes shall be reported in the CDRL –

A002 – MSR.

2.2.4 Database Management

2.2.4.1 Engineering Change Requests (ECRs): The contractor shall ensure all ECRs are resolved, upon receipt of notification, based on the timelines outlined in Table 2-3 unless another time frame is approved by the Government. ECRs may include, but are not limited to, working with the appropriate party to correct or amend errors in existing documents or data. The contractor shall provide a monthly report of ECRs to include ECR activity/status to the COR as part of CDRL A002 – MSR.

Table 2-3

ECR TYPE REQUIRED RESOLUTION TIME

NWRM NTE 3 business hours Work Stoppage NTE 8 business hours Urgent NTE 12 business hours Standard NTE 27 business hours

2.2.4.1.1 The contractor shall provide direct support to Government personnel for minor changes and workarounds not requiring ECRs.

2.2.4.1.2 Contractor shall report all ECRs in CDRL A002 – MSR to include type and timeline.

2.2.4.2 Request for Change (RFC)

2.2.4.2.1 RFCs will be submitted in MABSM by the government to request changes for potential application design changes, enhancements or process changes to the MABSM application. This applies to both hardware and software.

The contractor shall assess the complexity, required resources (hours to complete, viability, etc.) and potential impact to MABSM and submit reply on RFC form within five (5) business days.

2.2.4.2.2 The government will release approved RFCs for

implementation by the contractor with priority level on the RFC Form within MABSM in MRO Apps for contractor action. The contractor shall track and document within each RFC, the estimated and actual times (new work, break-fix) for RFCs execution.

2.2.4.2.3 Upon Government request, the contractor shall participate in the CCB process as a technical advisor and shall attend CCB meetings. The contractor shall ensure that no RFCs are implemented without the approval of the CCB.

2.2.4.2.4 Completed RFCs shall be included in the next release cycle unless the Government request certain RFCs to be released together. User support RFCs are any request that assists an individual MABSM user. User support RFCs will not go into priority list and will not be counted towards the 270 quarterly RFCs. The RFC process is outlined in the MABSM Business Rules (attached). The contractor shall complete 270 RFCs, to include WIP managed RFCs, per quarter. If the contractor delivers more than 270 RFCs including 30 WIP managed RFCs, it will be annotated in

CDRL A002 – MSR.

Table 2-4 RFC Type Required Resolution Time

CCB Routed Help Request Non-CCB Routed New RFC Unassigned

2.2.4.2.5 The contractor shall comply with AF directed change and release management policies and processes.

2.2.4.2.6 The contractor shall obtain AF approval for all CCB configuration changes to the MABSM application prior to proceeding with implementation of application changes IAW all applicable Air Force, and 75 ABW/SC polices and/or processes.

2.2.5 Application Sustainment

2.2.5.1 The contractor shall design, develop, test, and package application and software changes, as well as provide problem resolutions for the MABSM application.

2.2.5.2 The contractor shall maintain the current baseline of the MABSM application and provide software change(s) and problem fixes to MABSM baselines as required.

2.2.5.3 The contractor shall provide to the Government all developed, modified, or converted source code, modules, processes, programs, scripts, operating instructions, databases, application files, documentation, test files, and test conditions used to develop or maintain each approved application change request.

(CDRL XX12) Specific tasks may include the following:

2.2.5.3.1 The contractor shall maintain existing application and environments IAW disciplined engineering practices and sustain applications, databases, and interfaces in compliance with applicable AF/DoD standards.

2.2.5.3.2 The contractor shall interact with current and proposed interface system points of contact to determine the best data sources, transmission methods, and to resolve interface related issues.

2.2.5.3.3 The contractor shall report application status changes and application enhancements in a Monthly Status Report. (CDRL A001)

2.2.6 Application Development

2.2.6.1 The contractor shall conduct software development, software development testing, software security, web services development, web services testing, security layer integration, database clean-up, data wrapping, and data conversion.

2.2.6.2 The contractor shall develop, operate, and maintain prototype applications, models, and databases to determine optimal solutions for integration concepts and problems integral to the integration process. The contractor shall develop schedules and implementation plans, including parallel operations, identification of technical approaches, and a description of anticipated prototype results.

2.2.7 Application Services

2.2.7.1 The contractor shall provide technical and/or specialized guidance in the operation and application of the MABSM software interfacing with other systems, both automated and manual.

2.2.7.2 The contractor shall provide personnel who possess the technical knowledge regarding data models to include table relationships, source application forms and integrated legacy system tables. The contractor shall possess technical knowledge of the Oracle PL/SQL language and skill in developing database queries, packages, procedures and triggers for integration with Oracle Forms and performing data analysis.

2.2.7.3 The Government or contractor shall identify potential application design changes, enhancements, or upgrades for the MABSM application. This applies to both hardware and software.

2.2.7.4 The contractor shall compile and analyze data, provide options to validate concept reviews and improvements to the CCB that facilitate life cycle management of the MABSM software. The coordination and concurrence of the CCB shall be required before the contractor begins design changes, enhancements, or upgrades. Any design change, enhancement, or upgrade shall be compatible with other systems and components. The contractor shall verify functionality of any potential design change, enhancement, or upgrade through testing. The contractor shall also perform in-depth security testing of any potential design change, enhancement, or upgrade, and report any findings to the Government PM.

2.2.7.5 The contractor shall be required to assist the Government in providing information for the Control System Requirements Document (CSRD) process through the Information Systems Management Tool (ISMT).

2.2.7.6 The contractor shall be responsible for the Impresa or other chosen COTS MRO processes and must be intimately familiar with the inner workings of the MABSM software. The contractor shall use Air Force Legacy IT systems knowledge to establish and maintain many interfaces between the COTS MRO solution and the Legacy system environment. The contractor is responsible to provide management reports integrating the data from Legacy systems. The contractor shall be responsible to provide automated queries and processes to support the induction and sales process to eliminate duplication between the MRO solution and the Legacy environment. This includes the required updates and maintenance to support the interface.

2.2.8 System Operations

2.2.8.1 System Engineering

2.2.8.1.1 System Migration and/or Integration

2.2.8.1.1.1 The contractor shall perform system performance

tuning, system re-hosting and integration services.

2.2.8.1.1.2 The contractor shall move or migrate MABSM

systems data at the Government’s request to a subsuming or alternate system, designated standard infrastructure such as the Global Combat Support System (GCSS), or alternative hosting environment such as the DoD Enterprise Computing Center (DECC) or alternative commercial cloud services IAW AFI 63-101 Integrated Lifecycle Management, 63-1201 Life Cycle Systems Engineering, and AFI- 17-100 Air Force Information Technology (IT) Service Management.

2.2.8.2 The Contractor shall employ systems engineering processes IAW AFI 63-1201, Lifecycle Systems Engineering. The contractor shall provide operational support services IAW AFI 17-100, DoD 8570.01-M Information Assurance Workforce Improvement Program, and AFMAN 17-1303 Cybersecurity Workforce Improvement Program.

2.2.8.3 The contractor shall ensure creation of test backups of data, provide data cleansing services, verify data integrity, and implement access controls.

2.2.8.3.1 Source Code Management

2.2.8.3.1.1 Computer software is defined as source code, source code listings, object code listings, design details, algorithms, processes, flow charts, formulate and any related material that will enable the software to be reproduced, recreated or recompiled. The contractor shall maintain a current copy of all within the 75 ABW/SC source code repository.

2.2.8.3.1.1.1 Complete copy of the application shall be

delivered to the Government through XXXXXX process/system. To include all source code, scripts, updates, and libraries.

(CDRL XXXX)

2.2.8.4 Interface Management

2.2.8.4.1 The contractor shall maintain links/interfaces to all legacy systems and enable data to be pushed/pulled through MABSM.

2.2.8.4.1.1 Contractor shall provide interface updates in the Monthly Status Report to include source connect, source data, destination data, method, frequency, function, and purpose. (CDRL XXX1)

2.2.8.5 ATO

2.2.8.5.1 The contractor shall ensure all activities performed in the execution of this PWS complies with the Authority to Operate (ATO) governed by AFI 17-101, Risk Management Framework (RMF) for AF IT.

2.2.8.6 Data Stores

2.2.8.6.1 Data Dictionary

2.2.8.6.1.1 The contractor shall develop and maintain a data

dictionary and Entity Relationship Diagram (ERD) (CDRL AXXX – ERD) for the MABSM application database within six (6) months of contract award and as requested by the Government PM.

2.2.8.7 Configuration Control & Change Management

2.2.8.7.1.1 The contractor shall create and sustain optimal

structure and content for items, bills of material (BOM), shop routings, and other data critical to Material Requirements Planning (MRP) processing and material supportability.

2.2.8.8 NWRM / Serialized Items

2.2.8.8.1 The contractor shall have knowledge of, and maintain, the Nuclear Weapons-Related Materiel (NWRM) asset accountability and tracking in accordance with (IAW) Air Force Instruction (AFI) 20-110 and any subsequent versions or supplements to include but not limited to modification, repair, test/evaluation, and demilitarization efforts. (CDRL XXX3)

2.2.8.8.2 The contractor shall manage MABSM to audit all

NWRM serially controlled items and related attributes against the official published NWRM list. When official NWRM master listings are updated and distributed (at a minimum semi-annually), the contractor shall update MABSM within 24-hours, to maintain item attribute and data accuracy (e.g. part number, National Stock Number (NSN), and descriptions). When notified of required changes, the contractor shall complete updates to MABSM and report completion to the Government PM.

(CDRL XXX3)

2.2.8.8.3 The contractor shall collect Maintenance Data for

repaired serialized/NWRM assets and upload to Reliability and Maintainability Information System (REMIS), IAW Technical Order (T.O.) 00-20-2, and as further defined at task order level.

2.2.8.8.4 The contractor shall work with Planners as they

maintain BOM accuracy relative to NWRM and serialized items to include maintaining the integrity of parent-child relationship and assigning Standard Reporting Designators (SRD) and Work Unit Codes

(WUC).

2.2.8.8.5 The contractor shall report deviations (errors) for serialized NWRM items to the Government PM when inconsistencies exist between Technical Data or official NWRM lists and Legacy systems (e.g. D043).

Deviations must be reported to the Nuclear Weapon Related Material Accountable Officer (NWRMAO) upon finding and then reported in the monthly status report. (CDRL XXX1)

2.2.8.9 Web/Cloud Services

2.2.8.9.1 TBD

2.2.8.9.2 Ensure any changes to web services is supported

2.2.8.9.3 Sustaining Web/Cloud Services

2.2.8.9.4 ATO requirements specific to Web/Cloud Services??

2.2.8.9.5 Establishing methods to access data through the

Web/Cloud Services (S3 Bucket)

2.2.8.9.6 Contractor shall ensure all activities with Cloud

Servicing Entity (BROKER?) are executed fully and maintained. (Reword as needed)

2.2.9 Analytical Support

2.2.9.1 The contractor shall provide analytical services and support to track assets using MABSM for all system interfaces throughout the maintenance process. These assets include end items, subassemblies, components, and subcomponents of Government equipment and weapons systems.

2.2.9.2 The contractor shall develop and deliver technical reports, studies, white papers, and presentations to support Air Force systems and processes. The completion date will be determined by the Government in coordination with the contractor. (CDRL

XXX3)

2.2.9.3 The contractor shall provide analytical and Information Technology (IT) customer support for the MABSM application.

2.2.9.4 The contractor shall provide analytical services to support daily maintenance operations Analytical services include collecting, analyzing (i.e. statistical methods, comparative analysis, timeline analysis, cross-functional analysis, and cause and effect diagrams), and reporting data to include, but not limited to, manpower, material, scheduling, inventory, financial, and production.

2.2.9.4.1 The contractor shall analyze problems, identify

causative factors, and identify appropriate corrective action(s) to minimize application impact. The contractor shall coordinate all corrective actions through the Government PM.

2.2.9.4.2 The contractor shall conduct surveys, document reviews, and consultations.

2.3 IMPLEMENTATION

2.3.1 The contractor shall implement MABSM within groups as defined at the task order level according to scheduled timelines.

2.3.1.1 The contractor shall develop and propose a Master Project Plan (MPP) with each task order detailing the overall schedule and approach to implementation for the organization specified in the task order. The MPP shall indicate where each Integrated Master Schedule (IMS) fits within the MPP and include all major milestones including off-ramping as described in section 2.7. The MPP shall be delivered within 10 business days of task order award. Subsequent changes required throughout the task order period of performance (PoP) shall be approved by the Government prior to the change being made. Corrections or changes requested by the Government, either upon initial submission or throughout the POP, shall be made and delivered within three (3) business days of request (CDRL A001 –

MPP/IMS).

2.3.1.2 The contractor shall develop and propose an IMS with each task order specific to each weapon system that shall incorporate the asset induction schedule IAW established asset availability. IMS shall be delivered with the MPP – within 10 business days of task order award. Subsequent contractor recommended changes required throughout the task order period of performance (PoP) shall be accompanied by rationale and approved by the Government prior to the change being made. Corrections or changes requested by the Government, either upon initial submission or throughout the POP, shall be made and delivered within three (3) business days of request (CDRL A001 –

MPP/IMS).

2.3.1.3 The contractor shall adhere to the approved MPP and IMS. The contractor shall meet all monthly milestones with no more than one (1) unapproved deviation per month. The contractor shall seek approval from the Government PM for any deviations prior to the scheduled milestone due date. Monthly Status Report (MSR) (CDRL A002 - MSR) shall indicate both approved and unapproved MPP or IMS deviations.

2.3.2 Interface Set-Ups: The contractor shall use Air Force Legacy IT systems knowledge to establish and maintain interfaces between MABSM and the Legacy system environment. The contractor shall perform interface setup and configuration to include ports, protocols and services (PPS) to local instances of apps including but not limited to TAA, TSS and DDS. The contractor shall create an interface control document (ICD) (CDRL A003 - ICD) for each interface IAW DAFI 17-1203. The contractor shall deliver ICD within 10 business days following implementation of the interface as scheduled on the IMS.

2.3.3 Capability Set-Ups: The contractor shall accomplish capability setups working with local subject-matter-experts (SME) on relevant systems.

Contractor shall accomplish validation and verification of system capabilities and perform functionality adjustments as needed.

2.3.4 System Configuration: The contractor shall accomplish system configuration in accordance with AF depot organizational structure and aircraft networks. The contractor shall apply specific knowledge of AF depot operations and business logic. Contractor shall add, delete, and modify user accounts as required throughout the implementation phase.

2.3.5 Data Extract Transform Load (ETL)

2.3.5.1 Data Mapping: The contractor shall evaluate and map existing processes to include any new interfaces with Air Force Legacy systems that are to be incorporated into MABSM. Contractor shall create Data Migration Scripts from existing legacy MRO to MABSM database schema. This shall include new and old field and cell names listing all field dependencies, interfaces, or unique attributes. Applicable changes shall be updated in the corresponding user guides (See paragraph 2.5).

2.3.5.2 Data Validation: The contractor shall work with Government planners, schedulers and other SMEs to validate data and avoid system down-time during data loads. The contractor shall work with planners as they maintain the accuracy of bill of materials (BOM) relative to serialized items to include maintaining the integrity of parent-child relationship and assigning Standard Reporting Designators (SRD) and Work Unit Codes (WUC).

Data integrity shall be revisited if errors are found during side-by-side induction.

2.3.5.3 Data Load: Within 10 business days following the completion of the ETL process, the contractor shall provide Data Migration Scripts (CDRL A004 – Data Migration Scripts). The Government does not intend to issue any task orders where full completion of the ETL process is not the stated goal. However, if for any reason the ETL process is not completed on schedule within the task order PoP, all planning data and setup migration scripts shall be delivered, whether they are complete or not, within five (5) business days after the PoP end date.

2.3.5.4 Historical Data: The contractor shall obtain legacy MRO historical data and configure it to MABSM in a persisting database identified by the Government PM (CDRL A005 – Historical Data). The contractor shall validate with the

Government SME that the data is intact and accessible for Government acceptance. Initial delivery of shall be within 10 business days of completion of step in IMS. Government-requested changes shall be made within five (5) business days of request.

2.3.6 Implementation User Provisioning: The contractor shall provision new users at least 10 business days prior to Initial Operating Capability (IOC), whichever occurs first.

2.3.7 Side-by-Side: The contractor shall accomplish side-by-side induction of aircraft or other assets into MABSM and legacy systems simultaneously.

The contractor shall utilize this method to further validate data and train users on how to accomplish tasks utilizing new capabilities in reference to analogous legacy functions. The contractor shall coordinate with the government PM to identify users for participation in side-by-side induction at least 10 business days prior to this task and ensure they are properly trained for it. This training requirement shall be incorporated in the contractor’s Master Training Plan (MTP) (CDRL A006 - MTP).

2.3.8 Additional implementation details will be defined further at the task order level.

2.4 SPECIAL PROJECTS

2.4.1 Special projects may be specifically requested by the Government or identified by the Contractor and approved by the Government. A special project is any task within the scope of this PWS that is estimated to take longer than 400 working hours and was not anticipated within the original task order IMS. The special project may be defined specifically by the Government, or the Government may issue a Statement of Objective (SOO) for the project to which the contractor will respond with a solution.

In either case, a special project shall be executed by issuance of a standalone Task Order and defined by a PWS. Special projects may include, but are not limited to application enhancements, interface management, Art of the Possible (AoP) management required changes, implementation of wireless capabilities, implementation of MABSM’s financial and timekeeping modules as required at each ALC.

2.4.1.1 Site Assessments: The contractor shall participate in site assessments either locally or at a temporary duty station (TDY) to assist the government in identifying capability gaps between MABSM at its current state and the new business processes.

2.4.1.1.1.1 Completion of a white paper (CDRL A009 –

Technical/White Paper Reports) will be required after any site assessment. Delivery timeframe to be identified at the task order level.

2.4.1.2 Rough Order of Magnitude (ROM): ROM estimates may be

requested through the CO for budgeting and planning purposes.

The Government may request ROM estimates for services or equipment unrelated to developed SOOs.

2.5 KNOWLEDGE TRANSFER

2.5.1 The contractor shall incorporate the training and mentorship of Government personnel into their approach to MABSM implementation and sustainment tasks. The contractor’s MPP and IMS (CDRL A001), as applicable, shall reflect the contractor’s intent to facilitate the training and mentorship of Government personnel on how to implement and sustain the MABSM system. This shall be done to the greatest practical extent so as not to interfere with the contractor’s MPP or IMS milestone objectives.

2.5.1.1 Training on Implementation: Throughout the implementation process described in section 2.1, the contractor shall provide training for Government personnel on the specific implementation sub-processes.

Training shall be in a format appropriate to the task such as over the shoulder, OJT, ad-hoc, or classroom. Implementation training shall encompass all implementation tasks including interface set-up, capability set-up, system configuration, data ETL, and side-by-side induction. Specific training requirements may be further detailed at the task order level.

2.5.1.2 Training on Sustainment: The Contractor shall provide specific training on sustainment tasks as described at the task order level. Tasks may include but are not limited to configuration management, software release process, ECR process, cyber security, backlog management, and development processes. The Contractor, through this training, shall facilitate a complete transfer of knowledge to enable the Government to perform the defined task for future sustainment. Specific training requirements may be further detailed at the task order level.

3 SERVICES SUMMARY

SS Performance Objective PWS Paragraph Performance Threshold 1 IMS(s) / Master Plans

Contractor shall deliver Master Project Plan and revised plans within 15 business days. Acceptable quality level is 100%.

(CDRL A002)

2 Resolve all STIG Findings 3 RFC and ECR Reporting The contractor shall deliver the ECR report on or before the 5th business day of each month. No more than one late delivery in a 12-month period. (CDRL A001)

4 Execute minor changes and workarounds not requiring

RFC/ECR

The contractor shall maintain a 95% compliance rate with timeframes specified in Table 1, with the exception of NWRM which shall maintain a 100% compliance rate. (CDRL A001)

5 Official NWRM master listings are updated and distributed the contractor shall update MABSM within 24 hours.

NWRM items shall be updated within 24 hours with a 100% compliance rate.

(CDRL A003)

6 Report training IAW the approved Training Plan and provide the status in the Monthly Status Report.

(CDRL A001)

The contractor shall deliver this report on or before the 5th business day of each month. No more than one late delivery in a 12-month period. (CDRL A001)

7 Provide User Guides update the master user guide list.

Report on monthly status report.

Provide a new user guide within 60 calendar days of a newly created application and 30 days for an update to a current application. (CDRL A001)

(CDRL A011)

8 Provide comprehensive Training Plan that at a minimum will cover required training for new users as outlined in the topics listed in Appendix E.

The contractor shall deliver the Training Plan not later than 15 days after notification of contract award. (CDRL A004)

9 System Availability

Contractor shall maintain at least 95% MABSM availability during business hours. Performance is Satisfactory when system is availability is 95 percent or greater. Performance objective is 100 percent.

10 Code Quality

A deviation is defined as one instance of not complying with written Air Force, AFMC, or ALC policies/guidance or an instance of submitting applicable deliverables after the identified due date IAW with the applicable CDRL.

4 CONTRACT DATA REQUIREMENTS LIST (CDRL) SUMMARY

CDRL requirements: Contract information data shall be delivered, as assigned by the Ordering Activity, electronically IAW the corresponding requirement for each Data Item listed in Table 4- 1 (below). The contractor shall have no more than one (1) error per quarter for all CDRL submittals. The contractor shall submit CDRLs according to the due date indicated and have no more than one (1) CDRL per quarter submitted after the identified due date. Grammatical errors do not count as an error. Substantive mistakes shall be corrected within two (2) working days and corrective action taken to prevent recurrence of inaccurate late CDRLs.

Reporting: All reporting requirements listed below are applicable, unless omitted at the TO level and shall include current site-specific information.

Table 4-1

Exhibit Title PWS Paragraph

Delivery

A001 Status Report As Required IAW CDRL A002 Master Project Plan As Required A003 Technical Report/White Paper As Required

A004 Comprehensive Training Plan 15 days after notification of contract award

A005 TCIR/DART Annually A006 Software Version Description (SVD) As Required

A007 Contract Labor Hours No later than 31 October of each calendar year

A008 Accident/Mishap Report As Required A009

A010 Quality Control Plan 10 days after notification of contract award

A011 Training Guide(s) As Required A012 MABSM Application Sustainment As Required A013 GFE / GFP Report XXXX

5 GOVERNMENT FURNISHED PROPERTY AND FACILITIES

5.1 WORKSPACE

5.1.1 The Government will provide workspace, basic working supplies, seating, and access to telephones and desktop computers. Network connectivity, computer systems, and facilities are for business purposes only.

5.2 GFE / GFP

5.2.1 Government Furnished Equipment (GFE) and Government Furnished Property (GFP) necessary to complete the requirements of this PWS will be issued utilizing DD Form 610 Government Furnished Equipment Requirement Schedule.

5.2.1.1 If Government deems it necessary to issue laptops to complete the requirements of this contract, they will have capability to access the…