DMAC 3 RFI PWS.pdf

Depot Maintenance Applications Consolidation (DMAC) 3 Performance Work Statement (PWS)

(FA877026RB008)

Version 1.00

EXECUTIVE SUMMARY

The Air Force Materiel Command (AFMC), Air Force Life Cycle Management Center (AFLCMC), Business and Enterprise Systems (BES), Enterprise Logistics Systems Division (GB4), Maintenance and Installation Portfolio (GBM), Wright-Patterson Air Force Base (AFB), has a requirement to consolidate two existing service contracts into a singular effort to improve coordination and management of Information Technology (IT) service delivery. This Performance Work Statement (PWS) describes sustainment and surveillance services in support of the following systems: Depot Maintenance Consolidated Operational Database (DMCODB), Depot Maintenance Systems Integration (DMSI), and Depot Maintenance Legacy Systems (DMLS).

Table of Contents

EXECUTIVE SUMMARY

1. INTRODUCTION/PURPOSE

2. SCOPE

3. BACKGROUND

3.1. Depot Maintenance Systems Integration (DMSI)

3.1.1. DMSI Client/Server Applications

3.1.2. Depot Maintenance Consolidated Operational Database (DMCODB)

3.2. Depot Maintenance Legacy Systems (DMLS)

4. REQUIREMENTS/DESCRIPTION OF SERVICES

4.1. Skills and Knowledge

4.1.1. General Skills and Knowledge

4.1.2. DMSI Support Skills and Knowledge

4.1.3. DMCODB Support Skills and Knowledge

4.1.4. DMLS Support Skills and Knowledge

4.2. Program Management Plan

4.3. Contractor Responsibilities and Support

4.4. Contractor Transition Support

4.4.1. Initial Kickoff Meeting

4.4.2. Contract Start

4.4.3. Contractor Transition and Decommissioning Plans

4.4.4. Transition at Contract Conclusion

4.4.5. Transition Working Group (TWG)

4.5. Data Analysis

4.6. Enterprise Management Support

4.7. Systems Support

4.8. Development, Test, Training and Production Servers

4.9. Agile / Incremental Delivery Methodology

4.9.1. Current Sustainment and Maintenance

4.9.2. Surge Requirements

4.10. Specific Task Descriptions

4.10.1. Database Integration and Design

4.10.2. Data Conversion

4.10.3. Interface Software Design and Maintenance

4.10.4. Interface Software Maintenance

4.10.5. Interface Software Surveillance

4.10.6. Database Cybersecurity

4.10.7. Database Administration

4.10.8. Unix/Linux System Administration

4.10.9. Continuity of Operations (COOP) / Information System Contingency Plan (ISCP)

4.10.10. Dependencies

5. PROGRAM/LIFECYCLE MANAGEMENT

5.1. Agile Transition and Support

5.2. Requirements/Software Configuration Management Process

5.2.1. Information Systems Management Tool (ISMT)

5.2.2. Information Support Request (ISR)

5.2.3. Historical Workload

5.3. Schedules

5.3.1. Schedule Management

5.3.2. Planning Release Roadmap

5.3.3. User Story Management

5.3.4. Product Backlog Management

5.4. Interface Control Documents

5.5. Software and Documentation Control and Release Procedures

5.5.1. Software License Management

5.6. Enterprise Software Initiative

5.7. Technical Interchange Meetings (TIM) and Technical Reviews

5.8. Monthly Status Report

5.9. Deficiency Reports (DRs)

5.10. Software Deployment Planning

5.10.1. DMSI and DMCODB Release Support

5.10.2. DMLS Release Support

5.11. Maintenance Changes

5.12. Software User’s Manual (SUM)

5.13. Test Support

5.13.1. Test and Evaluation

5.13.2. Test Readiness Review

5.13.3. User Evaluation Testing

6. ENGINEERING REQUIREMENTS

6.1. Life-Cycle Systems Engineering

6.2. Air Force Acquisition Process Model (APM)

6.3. Department of Defense Architectural Framework (DoDAF)

6.4. Standard Desktop Configuration (SDC)

6.5. Cybersecurity Support Personnel

7. CONTRACTUAL REQUIREMENTS

7.1. Place of Performance

7.2. Normal Hours of Operation

7.3. Government Furnished Property

7.4. Non-Personal Services

7.5. Contractor Identification

7.6. Performance Reporting

7.7. Program/Project Management

7.8. Services Delivery Summary

7.9. Task Management

7.10. Documentation and Data Management

7.11. Records, Files, and Documents

7.12. Hardware and Maintenance

7.13. Section 508 of the Rehabilitation Act

7.14. Voluntary Protection Program (VPP) Elements for Requirements Documents

7.14.1. Installation-specific Safety and Health Standards

7.14.2. Applicable Contractors

7.14.3. Applicable Contractor’s Safety and Health Plan

7.14.4. Mishap Reporting

7.15. Travel

7.16. Training

7.16.1. Mission-Unique Training

8. SECURITY

8.1. Personnel Security Investigation Requirements

8.1.1. Security Background Investigation and Clearance

8.1.2. Unclassified Contracts

8.2. Common Access Card (CAC) Issuance and Eligibility

8.2.1. CAC Eligibility

8.2.2. CAC Requests Submission

8.2.3. Interim Issuance of CAC

8.2.4. Final CAC Determination

8.2.5. Minimum Requirements for Justification

8.2.6. Termination, Separation, and Expiration of Contract

8.3. Protection of Information

8.3.1. Controlled Unclassified Information

8.3.1.1. Executive Order 13526

8.3.1.2. Atomic Energy Act of 1954

8.3.1.3. Specific Program or Project Security Classification Guide

8.3.2. National Archives and Records Administration CUI Registry

8.3.3. CUI Guidance

8.3.4. Aggregation of Information

8.3.5. DoDM 5400.07/AFM 33-302

8.3.6. DoDI 8582.01

8.3.7. NIST Special Publication 800-171

8.3.8. DFARS 252.204-7012

8.4. Operations Security

8.5. Information Technology (IT) Level Rating

8.5.1. Critical-Sensitive, Information Technology (IT) Level I positions

8.5.2. Non-critical Sensitive, Information Technology (IT) Level II Positions

8.5.3. Non-sensitive, Information Technology (IT) Level III positions

8.5.4. Application & Information System Access Requests

8.6. Required Security-Related Training

8.6.1. Cyber Awareness Challenge Training

8.6.2. Force Protection and Anti-Terrorism Training

8.6.3. Controlled Unclassified Information Training

8.7. In Processing

8.7.1. In-Processing Checklist

8.7.2. Visit Requests for Classified Contracts

8.7.2.1. Contractors Not Requiring Access to Classified Information

8.7.2.2. WP Security Office Address

8.7.3. Visit Requests for Unclassified Contracts

8.8. Out Processing

8.8.1. Out Processing with AFLCMC/GBC

8.8.2. Trusted Associate Sponsorship System (TASS)

8.8.3. Contractors Ending Association with Air Force/CAC Surrender

FA877026RB008

Attachment 1 – DMAC 3 PWS

1. INTRODUCTION/PURPOSE

The overall purpose and objective of this effort is to provide maintenance, operations and surveillance support to sustain Depot Maintenance Information Technology (IT) systems by providing software systems analysis, design, sustainment, and maintenance expertise for the system identified within this Performance Work Statement (PWS).

2. SCOPE

This effort is to provide support for the software maintenance, sustainment and surveillance of the Depot Maintenance Systems Integration (DMSI), Depot Maintenance Consolidated Operational Database (DMCODB) and Depot Maintenance Legacy Systems (DMLS). The scope of this effort shall include planning, developing, testing, deploying, and sustaining depot maintenance IT systems to include new development, modifications, enhancements, and upgrades.

3. BACKGROUND

3.1. Depot Maintenance Systems Integration (DMSI)

DMSI is comprised of six (6) applications: AFMC Labor Standards Data System (ALSDS), Depot Maintenance Materiel Support System (DMMSS), Exchangeables Production System (EPS), Inventory Tracking System (ITS), Job Order Production Master System (JOPMS), and Programmed Depot Maintenance Scheduling System (PDMSS). DMSI applications were modernized, technically refreshed, or re-hosted into a consolidated system framework. All DMSI application data were migrated into the Depot Maintenance Consolidated Operational Database (DMCODB), which provides the consolidated database for the production management of the depot repair and maintenance process for the Air Force (AF) Enterprise. DMSI supports approximately 8,000 Headquarters Air Force Materiel Command (HQ AFMC) users at the three

(3) Air Logistics Complexes (ALCs) and Kadena Air Base (AB), including inventory management specialists, maintenance specialists, equipment specialists, funds monitors, and quality assurance specialists.

3.1.1. DMSI Client/Server Applications

Only five (5) DMSI client/server applications are within the scope of this PWS:

1. AFMC Labor Standards Data System (ALSDS): Establishes and maintains labor standards for maintenance planning and production costing. It provides information on data used for capacity planning reports that shall evaluate workload and personnel in terms of skills, and a simulation capability in order to determine the impact on skill capabilities and requirements in relation to workload changes.

2. Job Order Production Master System (JOPMS): Provides a repository for storing the production number master records. It also provides the user ability to track customer work requests, record work authorizations, maintain temporary work plans, record end item production, and document standard labor hours earned during depot level maintenance.

3. Depot Maintenance Materiel Support System (DMMSS): Acts as a repository for material standards and production/issue history, which supports increased productivity of the Depot Maintenance Work Centers. It provides part number to stock number cross-reference, history of National Stock Number changes, and retrieves, stores and updates Bill of Material (BOM) standard data.

4. Exchangeables Production System (EPS): Provides access to workload requirements data, end item availability data, job order number data, production count data, end item production data, on-line information used to manage Depot Maintenance Supply Centers (DMSC) and bench stocks.

5. Inventory Tracking System (ITS): Tracks repairable end items through the maintenance overhaul line. It assigns item-tracking numbers to all parts as they are inducted and subsequently tracks them through disassembly, repair, and assembly. The system provides management information to all levels of management as well as inventory control.

3.1.2. Depot Maintenance Consolidated Operational Database (DMCODB)

DMCODB is an integrated, consolidated shared Oracle database that provides data for production management of the Depot repair and maintenance process for the AF Enterprise. It is an operational-level data environment, serving on-line transaction processing applications for managing day-to-day operations in the AF aircraft maintenance depots.

As the depot maintenance applications were modernized, their data was loaded into the DMCODB.

DMCODB became a common source of data, receiving their data updates, and sending their data interfaces. It performs application data retrieval and updates, interfaces, and scripts needed to support all system interfaces. Through the DMSI operational applications, the DMCODB supports HQ AFMC users worldwide, including inventory management specialists, maintenance specialists, equipment specialists, funds monitors, and quality assurance specialists. DMCODB also provides corporate-level data to support AFMC tactical and strategic planning activities.

As operational applications are technically refreshed, they are enhanced with new user capabilities for reporting and on-line analytical processing (OLAP). Drawing upon the DMCODB’s consolidated data, these systems enable users to extract information, perform analyses, create reports, and respond to information requests from AFMC command-level staff, HQ AF staff, and Department of Defense (DoD) elements. The DMCODB also provides data for Data Services (DS), data marts/warehouses, and Enterprise Integration projects.

3.2. Depot Maintenance Legacy Systems (DMLS)

DMLS consists of two (2) applications used by all three (3) ALCs to perform management, workload forecasting, planning, parts support and tracking and requirements, configuration and workload management. DMLS includes the following systems:

1. Depot Maintenance Workload Planning and Control System (DMWPCS): Provides the Depot Maintenance a method to document and track the results of workload and manpower planning actions, provide a planned and historical labor application, interface data to other systems and provide a master listing of all Resource Control Centers (RCC) and their associated accepted workloads factor. The system also provides for multiple

Planned Labor Application (PLA) capability. This system is designed to process in both batch and database environments.

2. Information System Management Tool (ISMT): ISMT is the mandated application directed by AFMC/A4 to be used for managing the lifecycle of all application requirements. A portfolio management, requirements management and workload management tracking/reporting tool that supports the entire software lifecycle for Logistics Business IT (LogIT) programs/systems. ISMT is also used to manage the program backlog of tasks that need to be worked within a program release or sustainment cycle.

4. REQUIREMENTS/DESCRIPTION OF SERVICES

4.1. Skills and Knowledge

The Contractor shall have the skills and knowledge necessary to perform requirements and business process analysis, configuration and requirements management, quality assurance, design and construction (coding), software systems engineering, web-based development, documentation development, and testing, implementation and training.

4.1.1. General Skills and Knowledge

The Contractor shall:

• Have proficiency with project management software (e.g., MicroSoft Project, Jira) to create/ deliver integrated schedules

• Have critical technical skills required include using sound program management techniques and processes, expertise in mainframe, cloud, and Web-based environments

• Systematically evaluate, design, and standardize database tables for databases of systems to be subsumed or incorporated into the DMSI or DMLS databases

• Provide software engineering support and technical expertise for defining and analyzing system requirements, developing design specifications, translating specifications into programming logic, coding, completing developmental testing, and additional testing, as required

• Provide support that may include, but is not restricted to, technical leadership to develop solutions for software engineering studies and mainframe, client/server or

Internet/intranet applications, systems engineering, architectural design, structured analysis, and object-oriented principles and tool suites

• Provide software engineering and system analysis to design, develop, test, deploy, document, system restart/recovery, and integrate of new and/or modified information systems

• Provide software engineering evaluation of Commercial-Off-the-Shelf (COTS) software packages for potential integration and use in current/future AFLCMC/GBM depot maintenance software applications

• As required, support subsumption (or consolidation) of application components and capabilities into any future depot maintenance enterprise solution requirements

4.1.2. DMSI Support Skills and Knowledge

The Contractor shall provide the following support skills and knowledge areas:

• ALSDS, DMMSS, EPS, ITS, and JOPMS applications are using client/server architecture with software being deployed by local communication squadrons to the users’ workstation.

• DMSI shall be programmed in Oracle Programming Language/Structured Query Language (PL/SQL) and also using Appeon PowerBuilder application development.

Procedures to retrieve data and package the business object data calls use SQL Scripts.

DMSI implements configuration management using Subversion. InstallShield is used to package the client/server applications for deployment. RoboHelp is used to create the Help files.

4.1.3. DMCODB Support Skills and Knowledge

• Knowledge of Oracle 12.x database administration and performance tuning

• Oracle SQL Script

• Oracle PL/SQL

• Oracle GoldenGate, DataGuard, Materialized Views

• Programming Languages: C, Perl, and Extensible Markup Language (XML)

• SubVersion Version Manager

• Information System Management Tool (ISMT)

• IBM Websphere MQ 7.x

• SQL/Net

• FTP/SFTP

• Data Modeling

• UNIX/Linux shell scripting and system administration

• MS Windows Sever Administration

• SmartSVN

• VisualSVN

• Data Modeling and Data Management Tools o ERwin v7.x PL/SQL Developer v 8

• Java and JavaScript

4.1.4. DMLS Support Skills and Knowledge

• Software maintenance and sustainment support performing mainframe, client/server, internet/intranet and cloud applications; translation of specifications into programming logic, coding, completing developmental and additional testing operations in a Defense Information Systems Agency (DISA) environment. Each DMLS application has its own unique software/ hardware requirement.

• DMWPCS is programmed Azure Cloud Hosted MaaS o Mainframe: Microsoft Azure C1 o OS - Windows Servers 2016 o DB - Azure SQL Server o C# o Lines of code: 142,530

• ISMT is a Cloud-based configuration and requirements management application.

o Cloud Azure PaaS o BitBucket o Artifactory o DB: SQL Server 2018 o Visual Studio 2019 o Oracle PL/SQL o ASP.net o Code repository – Atlassian BitBucket o Approx. 855,000 lines of code

4.2. Program Management Plan

The Contractor shall prepare a Program Management Plan describing the approach for conducting and providing analysis, maintenance, testing and surveillance support for this PWS. The Program Management Plan, at a minimum, shall address:

• Staffing Plan, Roles and Responsibilities

• Knowledge Transfer approaches and Internal Training

• Performance Measurement and Critical Success Factors

• Risk Management approach

• Workload Management

• Quality Assurance

• Use of ISMT for Software Configuration Management, including use of other government approved software code management tools

• Software maintenance processes, including documentation update and processing, and management and oversight

• Tools used for monitoring, controlling, and reporting

• Testing as covered in the Integrated Test Plan

• Development and update of project schedules and performance reporting

• Approach and processes for execution of program surveillance activities

• Outbound Transition Plan to Government or future contract resources, including:

• Approach to be used to train resources

• Transition of surveillance tasks and responsibilities

• Transition of maintenance tasks and responsibilities

• Transition of all source code, documentation, equipment, and support files and plans

4.3. Contractor Responsibilities and Support

The Contractor shall provide sustainment, operations and surveillance support for DMSI client/server applications, DMLS applications, and DMCODB. All systems identified within this PWS have a service level objective of at least 98% availability (i.e., uptime) to the customer.

The 98% uptime objective assumes a requirement of continuous uptime (i.e. 24/7 all year long) with allowances for planned maintenance windows. The Contractor shall schedule and coordinate all planned maintenance with the designated Capability Delivery Teams (CDT) and affected stakeholders (i.e. end users, ALCs, DISA, etc.).

The Contractor shall, in cooperation with other DMSI applications and Spectrum System Development Architecture (SSDA) framework, develop DMCODB changes required to meet customer change requests.

The Contractor shall develop and/or modify schedules, coordinate with interfacing systems, and serve as the surveillance Point of Contact (POC). The Contractor shall coordinate special runs and planned system outages with the Office Primary Responsibility (OPR) on schedules, block changes of releases, and special events for both DMLS and DMSI systems. The Contractor shall setup and/or modify site unique system Job Control Language to enhance performance, recovery procedures, and output distribution. The Contractor shall verify successful processing/ completion and/or file status.

The Contractor shall notify the appropriate Program Management Office (PMO) for non-conforming errors, and required restarts/reruns. The Contractor shall detect, analyze, and resolve program or data problems, security violations, process problems and/or conflicts with other system schedules and events. The Contractor shall utilize and update surveillance online documentation to include application help files, as applicable.

The Contractor shall provide the PMO with detailed information concerning program problems.

The Contractor shall detect poor and degraded program performance and report this to the PMO.

Upon PMO request, the Contractor shall provide Information Support Requests (ISRs), which can be (ad-hoc/out-of-cycle) reports, interrogations, requests and other specified information concerning any aspect of their system. DMSI batch jobs will be addressed, initiated, monitored, coordinated, and implemented through the DMSI PMO.

The Contractor shall provide sustainment and surveillance services to include, at a minimum:

software infrastructure, software engineering, technical support, and resolution of priority 1-5 Deficiency Reports (DRs), Software Problem Reports (SPRs), Change Requests (CR), Baseline Change Request (BCRs), Technical Change Requests (TCRs), Software Maintenance (S/W Mx), Code Quality Request (CQR), and Information Support Requests (ISRs) documented in ISMT.

Note:

Refer to Appendix A for DR Severity Code Definitions.

Refer to Appendix B for System Context and Historical Workload Data.

The Contractor shall provide technical editing and writing services in the preparation and maintenance of system lifecycle documents. The Contractor shall establish documentation guidelines, configuration and version control, procedures and templates, word processing and coordinate final production of deliverables. Development and maintenance of the on-line users’ manual shall meet customer standards and requirements.

The Contractor shall execute all phases of software maintenance (as appropriate) using the Department of the Air Force (DAF) Acquisition Process Model (APM).

Additionally, the Contractor shall comply with applicable regulations and standards identified in APPENDIX C. The Contractor shall prepare and submit Technical Solution/Rough Order of Magnitude (TS/ROM) data on all change request types (i.e., S/W Mx, CQR BCR, DR, and TCR) into ISMT, or government designated tracking system.

4.4. Contractor Transition Support

The Contractor shall address their plan to execute the training, transition and turnover of the DMSI client/server applications, DMLS applications, and DMCODB as part of an overall Transition Plan. During the Contract Start-up/Transition, the Contractor shall perform the tasks required for transferring maintenance, sustainment, surveillance and program management support from the incumbent contractor to the new contractor in a collaborative and supportive manner.

4.4.1. Initial Kickoff Meeting

The Contractor shall initiate work on this contract by meeting with AFLCMC/GBM personnel to ensure that a common understanding of requirements, expectations, documentation, and ultimate end products exist between all parties. The Contractor shall then prepare and deliver a Report, Record of Meeting/Minutes.

4.4.2. Contract Start

The Contractor shall submit a non-proprietary Transition Plan covering a 60 day period to include assisting the follow-on contractor in learning all capability support activities (development, surveillance and operations) to ensure minimal downtime. This Transition Plan shall provide for the orderly start-up of maintenance and transfer of all items related to the maintenance of supported systems (i.e., DMSI applications, DMLS applications, and DMCODB), to include, at a minimum:

source code, make files and/or other build files, build instructions, use of government approved configuration management tools, application data, application documentation, government furnish property (GFP), and status of work in-process. The Transition Plan shall include a comprehensive description of the activities and schedule required to transition the databases maintenance, sustainment, and technical support functions from the outgoing contractor to the follow-on contractor.

The plan shall include:

• Movement of GFP/Government Furnished Information (GFI), if required

• Resourcing and staffing

• Program Management startup activities

• DMCODB surveillance and operational activities

• Acquiring knowledge and familiarization

• Risk assessment approach/methodology

• 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

• 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 staffing no later than 30 calendar days after contract award

Deliverable: Software Transition Plan (STrP), (CDRL A011)

4.4.3. Contractor Transition and Decommissioning Plans

The Contractor shall create transition and decommissioning plans that accommodate all of the non-authoritative data sources (non-ADS) interfaces and ensure that necessary capabilities are delivered using approved ADSs.

Deliverable: Software Transition Plan (STrP), (CDRL A011)

4.4.4. Transition at Contract Conclusion

The Contractor shall develop a non-proprietary plan for the transition of sustainment, maintenance, operations, and modification responsibilities to the follow-on contractor. The Transition Plan shall provide a plan for the orderly transfer of all items related to the maintenance the DMSI client/server applications, DMLS applications, and DMCODB, to include source code, files and/or other build files, build instructions, configuration management tools and data, database models, documentation, status and documentation of work-in-process, and GFI/GFP, if required, to the follow-on contractor.

The Contractor shall be required to answer functional and technical questions to enable the follow-on contractor to maintain and sustain all applications 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 during the transition period. The Contractor’s transition plan shall include a comprehensive description of the activities and schedule required to transition the maintenance, sustainment, and technical support functions from the outgoing contractor to the follow-on contractor.

The plan shall include transition support for DMSI client/server applications, DMLS applications, and DMCODB:

• Resourcing and staffing

• Program management shut down activities

• DMCODB 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, production, 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

4.4.5. Transition Working Group (TWG)

A TWG shall be established to plan, monitor, and manage the transition of maintenance support from the Contractor. A Government representative will chair the TWG. It will include representatives of the Government Program Management Office (AFLCMC/GBM Depot Maintenance), out-going contractor, functional user, and gaining contractor and/or support contractors. The TWG shall define and coordinate all agreements, actions, events, schedules, training and other requirements needed for an orderly and timely transfer of maintenance and sustainment responsibility from the out-going contractor. The Contractor shall provide status on action items, events, and schedules in minutes from TWG meetings.

The Contractor shall also be required to meet the Performance Requirements identified in Appendix F: Services Summary.

4.5. Data Analysis

The Contractor shall perform proactive data analysis, recommend corrective actions as a result of analysis, and participate in work groups in support of DMSI client/server applications, DMLS applications, and DMCODB. The Contractor shall perform data analysis and maintain data analysis tools required to research legacy system data for comparison to data in the Data Depot Corporate Model. The Contractor shall provide analysis support for the migration of DMSI, DMLS, and DMCODB data to other Enterprise Integration efforts.

4.6. Enterprise Management Support

The Contractor shall be required to provide support to other AFMC Enterprise initiatives (e.g.

MROi, PLMi, etc.) that may materialize as they relate to integration with DMSI, DMLS, and DMCODB. The scope of these efforts may include functional requirements support and analysis, data analysis/integration/support, data modeling, design, development, and interface development/modifications for DMSI client/server applications, DMLS applications, and

DMCODB.

4.7. Systems Support

The Contractor shall design, develop, test and package systems and software changes as well as provide problem resolutions for the existing system. The Contractor shall maintain the current baseline of the system and provide software change and problem fixes to these baselines as required. The Contractor shall provide to the Government all developed, modified, or converted programs, scripts, operating instructions documentation, test scripts used to develop each approved systems change request.

Specific tasks may include the following:

• Maintain existing systems and environments in accordance with (IAW) disciplined engineering practices and sustain databases and interfaces in compliance with applicable AF/DoD standards

• Conduct software and data model development, data conversion and data lifecycle management

• Utilize Government-Off-the-Shelf (GOTS) or approved COTS tools for systems design and development

4.8. Development, Test, Training and Production Servers

The Contractor shall also be responsible for performing the following database administration activities specific to DMSI, DMLS, DMCODB development, and test, training, and production servers:

• The Contractor shall set up database structures

• The Contractor shall perform initial database environment configuration for the physical layout of the database environment and storage allocation

• The Contractor shall create or modify database instances; install, upgrade and patch the database software; and adjust authorizations and permissions of users and groups

• The Contractor shall ensure compliance with Security Technical Implementation Guides

(STIGs) and Information Assurance Vulnerability Alerts (IAVAs) and perform, maintain and validate Vulnerability Management System (VMS) data entry for all systems and applications identified within the PWS

• The Contractor shall conduct automated Source Code Analysis (SCA) using government approved tools (e.g., such as Checkmarx, Fortify, etc.) on every release/patch that includes new or modified source code

• The Contractor shall provide access to vulnerability assessments within the online tools for each release/patch that includes new or modified source code

• The Contractor also shall conduct cyber security-focused testing (validate on any affected controls/STIGs) and document any flaws found

• The Contractor shall produce/provide results of all security testing and work with the PMO Cybersecurity Team to assess all findings and flaws reported

• The Government cybersecurity team member shall be responsible for confirming the Contractor’s assessment of findings that the Contractor determines to be invalid or non-issues. All valid findings identified in the release shall be addressed prior to the code being released into the production environment or at a Government defined date. Valid findings can be addressed through remediation (fix/update code) or through other risk management processes, such the Plan Of Action & Milestones (POA&M) process (STIGs). Furthermore, any remediation decisions shall be documented.

• If Cyber Security incidents are identified in production, the Contractor shall work with the PMO cybersecurity team and other Government personnel from the PMO to prioritize the correction of these incidents. If the vulnerabilities identified are found to be introduced with a release/patch, the Contractor shall be responsible for remediation.

• The Contractor shall schedule and monitor database backups

• The Contractor shall validate the integrity of the database backup process and recovery images annually

• The Contractor shall conduct performance tuning

• The Contractor shall be responsible for release deployment when required

4.9. Agile / Incremental Delivery Methodology

4.9.1. Current Sustainment and Maintenance

The Contractor shall collaborate with the Government to facilitate an Agile-based approach to sustainment support. The prioritization of requirements is subject to change based on Mission Business Area demands during the period of the contract. Planned and forecasted features may be accelerated, changed, or interchanged within the scope as determined in program increment or sprint planning.

The designated Product Owner(s) will specify high-level requirements/capabilities to the Agile Development Team. As in typical Scrum-based agile processes, the Contractor and Product Owner will work together with project stakeholders to develop and estimate user stories and establish acceptance criteria. These acceptance criteria will specify expected functionality for a user story, as well as any non-functional requirements that must be met in the development of the story. The Agency Product Owner, supported by subject matter experts and business analysts, will determine whether or not acceptance criteria have been satisfied.

4.9.2. Surge Requirements

Future surge requirements may be identified throughout the Period of Performance (PoP), such as major technical refresh efforts, which would warrant a contract modification to define surge requirements and exercise the surge CLINs.

As part of this approach, the Contractor shall provide six (6) six-month agile team options that may be exercised per contract year to support increased requirements by the user community (Surge CLINs). These teams shall consist of two developers and one tester. These teams shall be additional to the staffing required to maintain the current requirements in the PWS and shall not be utilized to perform work to be completed under the basic labor CLINs. These increased in-scope requirements such as new AF or DOD initiatives may include unplanned tasks above/beyond current sustainment and/or maintenance efforts. Examples may include but are not limited to:

• Code refactoring

• Addressing technical debt

• Identity Credentialing Access Management (ICAM) implementation

• Standard Financial Information Structure (SFIS) compliance

• Standard Line of Accounting (SLOA) compliance

• Defense Logistics Management Standards (DMLS) compliance

The Government CO will provide the potential surge requirement to the contractor. The contractor shall then notify the appropriate CDM/PM of the number of surge teams required within 15 business days upon receipt of the requirement. Upon exercise of surge option(s), the surge requirement will be defined within the PWS. When these requirements are exercised utilizing surge labor CLINs, the requirement will be placed into the Contractor’s overall product backlog, integrated into the product increment plan, and worked within the programmed release cadence for the agreed period.

4.10. Specific Task Descriptions

4.10.1. Database Integration and Design

The Contractor shall review new and modified database requirements to determine any additions/modifications/clarifications necessary to update the Software Requirements Specifications (SRS) and Database Design Description (DBDD) for each application or database.

The Contractor shall develop and integrate data requirements into the data model. The Contractor shall work with the Government PMO, application development teams, SSDA framework and enterprise integration efforts to ensure a satisfactory understanding of the requirements before proceeding with the database design change. The Contractor shall take all actions necessary to resolve any data requirement conflicts with existing data model or proposed changes to the environment. The Contractor shall follow system engineering standards and/or best practices in the development of the logical and physical data models. The Contractor shall review and provide analysis on change requests submitted by developers or Program Office that impact logical and/or physical models. The Contractor shall provide updates to the existing SRS document or United States Government (USG) designated tool.

The Contractor shall monitor development, test, training, and operational environments in coordination with PMO and DISA staff. The Contractor shall perform required activities within the operational environment needed to support database and interface processes. The Contractor shall support the Government in investigating, developing and implementing data or database changes needed to support Air Force Enterprise initiatives.

The Contractor shall evaluate, design, and standardize database tables to be subsumed or incorporated into DMSI, DMLS, or DMCODB. This includes developing and integrating data requirements into the environment.

Deliverable: Database Design Description (DBDD), (CDRL A010) Deliverable: System Requirements Specification (SRS), (CDRL A005)

4.10.2. Data Conversion

The Contractor shall define data conversion mappings and designs to migrate data from a legacy system environment to support enterprise integration initiatives. The Contractor shall verify data integrity is not compromised and other DMSI, DMLS, and DMCODB are not adversely impacted.

Prior to the start of software testing, the Contractor shall execute data conversion tests using the most current legacy production data. The Contractor shall review the data conversion logs and review the results of the conversion with functional subject matter experts. The Contractor shall identify data that does not conform to the business rules defined in the database design. This dirty data shall be provided to the functional users who shall correct it in the legacy system. The data conversion shall be re-executed to verify the database is ready for testing. During testing, the data conversion shall be performed as required to support the retesting of interface and application software.

4.10.3. Interface Software Design and Maintenance

The Contractor shall implement interface change requests as required by the functional community. The Contractor shall monitor/surveil all interface jobs and batch processes to ensure proper execution. All system interfaces for this PWS are shown in APPENDIX D.

The Contractor shall analyze interface requirements, design interface methods and associated software, and shall demonstrate the current capabilities and status of the design at technical review.

The Contractor shall conduct TIMs with software developers and PMO as frequently as necessary to resolve requirements issues, to ensure that the design accurately represent the approved requirements, and are proceeding in accordance with the approved schedule. The Contractor shall verify and maintain the design of interface software with the Interface Control Document (ICD) associated with each interface in the Corporate Data Repository System (CDRS). At the conclusion of the detailed design, the Contractor shall update the Software Design Description (SDD) or Interface Design Description (IDD) artifacts.

The Contractor shall provide an Application Daily Operations Manual (ADOM) to document complete instructions for operating the interface software. This shall include administration functions required for execution and error recovery for the interface.

Deliverable: Software Design Description (SDD), (CDRL A006) Deliverable: Application Daily Operations Manual (ADOM), (CDRL A012)

4.10.4. Interface Software Maintenance

The Contractor shall provide software maintenance for all interfaces. This software maintenance shall include: attending development team scrum meetings, AF designated governance meetings, and providing analysis on proposed changes/ enhancements/ technical infrastructure changes to the interface software. Changes may be to existing data exchange mechanisms, transformation algorithms, record layouts, or other software modification caused by changes to external systems, database design, and preventative maintenance. Meetings with external systems might be necessary to provide a technical solution. Also, testing with external systems is necessary to ensure the technical solution is correct.

4.10.5. Interface Software Surveillance

The Contractor shall monitor incoming/outgoing interfaces and batch processes to ensure proper execution of all interface software processes. The Contractor is responsible to perform surveillance activities for all DMSI, DMLS, and DMCODB batch jobs. On a daily basis, the nightly batch process logs shall be reviewed to confirm the status of each scheduled interface. The Contractor shall respond 24 x 7 x 365 to interruptions in execution of critical batch processes as identified by the DISA help desk. The Contractor shall coordinate with DISA and cloud support personnel and software developers (DMSI, DMLS, and DMCODB) to implement corrective actions.

The Contractor shall support special job executions and/or other tasks in support of fiscal end-of-year processing. This is a special process that occurs on the night of 30 September through 1 October. These special job executions are coordinated with the site OPRs.

4.10.6. Database Cybersecurity

The Contractor shall perform a cybersecurity review of changes or modifications prior to execution in the production environment. The Contractor shall adhere to applicable DISA Security Technical Implementation Guides (STIGs), Air Force Cybersecurity Program Management, and NIST Cybersecurity Framework and supporting NIST Special Publications. See Appendix C for a list of Technical Standards.

The Contractor shall ensure deliverables comply with, or mitigate risk in cybersecurity control checklists and DISA Application Security & Development STIG.

The Contractor shall perform a cybersecurity review of all changes and follow a software release process for each release. The Contractor shall create default cybersecurity checklists consisting of cybersecurity controls to be answered per release. The Contractor shall complete cybersecurity checklists comprised of cybersecurity controls for each release and shall submit these results as part of the Software Test Report.

Deliverable: Software Test Report (STR), (CDRL A009)

4.10.7. Database Administration

The Contractor shall perform the following database administration activities for the database and application development, test, Software Validation Test (SVT), DMSI Integration Test (DIT), failover, production, and training database instances as specified in the DMCODB Database Instance Listing, APPENDIX E:

• Work with application developers to explain how to interact with the physical database, and how to construct stored procedures and other database objects as necessary

• Create and maintain additional Relational Database Management System (RDBMS) objects, System Select Transactions (SST), System Utility Transactions (SUT) and any required triggers to provide data replication

• Prepare sizing estimates for the physical database and recommend the optimal number and placement of Oracle instances

• Provide support, tool analysis, setup and administration as required in performing the necessary daily administration activities

• Provide on-site training and instruction and design tools as required by the AFLCMC/GBM depot maintenance development personnel. This instruction shall include techniques in integration of various COTS products and the standards and procedures necessary to construct a multiple-site data resource catalog

• Design and implement a physical database from the physical model

• Maintain the logical and physical data model

• Provide database support to other requesting external system for purposes of interface testing

• Perform user account management

• Provide database design, creation, implementation and maintenance support of development and test databases for all application systems

4.10.8. Unix/Linux System Administration

The Contractor shall be responsible for performing Unix/Linux system administration activities via the Service Level Agreement (SLA) with DISA:

• Optimize performance and ensure high availability of Unix/Linux servers

• Proactively monitor system performance and capacity

• Proactively maintain Unix/Linux infrastructure technology to maintain high availability

• Manage, coordinate, test and implement operating system software upgrades, operating system patches and operating system hot fixes on Unix/Linux servers

• Perform fault finding analysis of logged information for reporting of performance exceptions

• Create and maintain scripts to automate system administration tasks

• Perform routine audits of the Unix/Linux operating system and software

• Perform and maintain Unix/Linux operating system software backups

• Install and configure virtualized machines

• Install and configure Unix/Linux operating systems software

• Maintain user account information for the Unix/Linux servers

• Coordinate hardware maintenance activities with DISA representatives

• Identify problems/issues to the appropriate DISA management level to ensure resolution

• Identify risks and appropriate mitigations for Unix/Linux support tasks

• Ensure the Unix/Linux servers comply with Government STIGs and security regulations where appropriate

4.10.9. Continuity of Operations (COOP) / Information System

Contingency Plan (ISCP)

• The Contractor shall collaborate with AFLCMC/GBM personnel to establish an ISCP describing coordination and procedures to recover production, development, and training systems quickly and effectively following a service disruption.

• The Contractor shall identify the activities, resources, and procedures to carry out production, development, and training servers processing requirements during prolonged interruptions to normal operations.

• The Contractor shall ensure coordination with personnel responsible for AFLCMC/GBM contingency planning strategies.

• The Contractor shall ensure coordination with DMSI stakeholders and external points of contact (including vendors) associated with execution of ISCP.

4.10.10. Dependencies

DMSI is dependent upon DISA to maintain and operate the hardware and software infrastructure that supports DMSI’s web application and database servers. The Contractor shall coordinate with DISA to jointly administer the DMSI failover databases. The database (production), development and test environments are as follows:

• DMSI and DMCODB – 15103 DISA Data Center OKC, Tinker AFB, OK

• DMWPCS – Cloud One Azure MaaS

• ISMT – Cloud One Azure PaaS

DISA DECC Ogden hosts a second DMSI test site and DISA San Antonio (DISA SA) hosts the DMSI failover databases.

• DMWPCS is dependent on C1 Azure

• ISMT is dependent upon Cloud One Azure that supports its application and database.

The Contractor shall coordinate with DISA to jointly administer the development, test, and training databases. The Contractor shall be responsible of coordinating and/or setting up and maintaining the environments for application testing as well as testing external interfaces. The Contractor shall be responsible for supporting and coordinating schedule and/or out-of-cycle maintenance outages as applicable with DISA, Cloud One, site users, and other impacted teams (DMSI, DMLS, etc.).

Technical refreshes of the environments are part of the DISA or Cloud One Service Level Agreements (SLAs). The Contractor shall provide test and integration support to DISA for the DMSI systems and databases.

5. PROGRAM/LIFECYCLE MANAGEMENT

5.1. Agile Transition and Support

AFLCMC/GB4 has identified implementation and maturity of Agile processes and practices across all product lines as critical to achieving its organizational objective for system-wide modernization. As this is an ongoing organizational objective, the Contractor shall support and participate in the implementation of Agile processes in the execution of sustainment and surveillance services. The Contractor shall use the government designated tools in the electronic delivery and reporting of information.

5.2. Requirements/Software Configuration Management Process

The Contractor shall comply with configuration management policy, for all development and sustainment program/projects. The Contractor shall participate in all Functional Review Boards (FRBs) activities as scheduled and provide support to all Software Configuration Control Board (CCB) and Sprint Planning activities.

The Contractor shall use tools approved by AFLCMC/GBM Depot Maintenance for all applicable software configuration, data management, and requirements traceability. The Contractor shall provide configuration identification and change control tasks associated with the receipt, processing, approval and filing of system requirements, design and test documents; in conjunction with the applicable CR method. The Contractor shall capture Functional Description Data (FDD), where the FDD specifies the functional decomposition, and associated requirements, to translate stakeholder user stories to use-cases (functional and non-functional). These requirements shall not be acted upon/accepted by the Contractor until the Government officially approves them.

5.2.1. Information Systems Management Tool (ISMT)

The Contractor shall use ISMT to manage and…