DRAFT MPES 2025 Recompete PWS.pdf

FA7014‐XX-X-XXXX

PERFORMANCE WORK STATEMENT

FOR

MANPOWER PROGRAMING AND EXECUTION SYSTEM (MPES)

AT

JOINT BASE ANDREWS, MARYLAND

27 February 2025

DRAFT

Controlled by: AFDW/PK Categories: PROCURE Distribution/Dissemination Controls:

FEDCON AFTER AWARD

POC: Ms. Tiffany Young (240-612-XXXX)

Contents

Introduction

2. Scope

2.1 General Information

2.2 Current System

3. General Requirements

3.1 Overview

3.2 Design

3.3 Development

3.4 Integration

3.5 Testing

3.6 Deployment

3.7 Sustainment/Maintenance

4. Programmatic Requirements

4.1 Contract Progress, Status, and Management Report Preparation

4.2 Contractor Performance Assessment Reporting System (CPARS)

4.3. Project Management Plan

4.4 Configuration Management Plan

5. Technical Requirements

5.1 Software Development and Support

5.2 Software Maintenance

5.3 Quality Assurance and Testing

5.4 Code/Software Review Process

5.5 COTS Software Configuration

5.6 Software Licensing

5.7 Documentation

5.8 Database Administration

5.9 MPES Manpower Data Mart (Query, Reporting and Analysis)

5.10 Annual Disaster Recovery Plan (DRP)

5.11 System Interfaces

5.12 Applications Hosting Support

5.13 Manpower Instructional System Configuration and Support

5.14 Web Services

5.15 MPES Helpdesk Support

5.16 User Training and Training Materials

5.17 On-site Training

6. Cyber Security Requirements

6.1 Cyber Security Program Management

6.2 Cyber Security Practices

6.3 Contractor Cyber Security Workforce (CSWF) Management

6.4 Assess and Authorize

6.5 Clinger-Cohen

6.6 Contractor Cyber Security Workforce Roles

6.7 Computing Environment/Operating System Training Documentation

6.8 System Security Plan

6.9 Information Technology Asset Management

7. Transition In&Out Plan/Kickoff Meeting

7.1 Transition Support

7.2 Transition-In Plan

7.3 Transition-Out Plan

7.4 Project Kickoff Meeting

8. Contractor Personnel Support

8.1 Contract Program Manager

8.2 Duty Hours

8.3 Place of Performance

8.4 Telework

8.5 Emergency Operations/Mission Essential Personnel

8.6 Security Instructions

8.7 Travel Costs

8.8 Other Direct Costs

8.9 Employee Accountability and Turnover

8.10 Miscellaneous Paragraphs

APPENDIX A – DEFINITIONS, ABBREVIATIONS AND ACRONYMS

APPENDIX B – SERVICE SUMMARY

APPENDIX C – DELIVERABLES

APPENDIX D – WORKLOAD HISTORY AND HISTORICAL WORKFORCE

INTRODUCTION

The Air Force Directorate of Manpower, Organization and Resources (AF/A1M) is responsible to provide contracted services to support, develop, test, maintain and sustain the Manpower Programming and Execution System (MPES)-NIPR/SIPR web-based applications.

2. SCOPE. This Performance Work Statement (PWS) identifies the scope and general activities for the sustainment support the MPES system, applications and systems that may interface with the system. The portfolio includes custom Defense Business System software, also referred to as Government Off-the-Shelf (GOTS) software, Defense Business System Commercial Off-the-Shelf (COTS) software and mixed solutions that may include both types. The term “Defense Business System” means an information system, other than a national security system, operated by, for, or on behalf of the Department of Defense, including financial systems, mixed systems, financial data feeder systems, and information technology and information assurance infrastructure, used to support business activities, such as acquisition, financial management, logistics, strategic planning and budgeting, installations and environment, and human resource management. The scope of this PWS includes tasks associated with the sustainment and modernization of software. These tasks include:

• At the direction of the Government, development/modernization of existing and new IT software products

• Integration

• Testing and test support

• Implementation/deployment

• Sustainment, technology refresh and operations support

• Training: end use, administrator, knowledge management support for application

• Transition in/out support

The Contractor shall assume responsibility of the current, Government-owned system and end user environment, which shall include infrastructure and services. Requirements for supporting the current environment shall include management and maintenance of the existing infrastructure and ensure MPES interoperates and works seamlessly with Contractor-provided services. This will involve proactive monitoring, troubleshooting, timely resolution of system issues, security patching, performance optimization, and implementation of upgrades as directed by the Government, ensuring continuous system availability and functionality at established service levels.

The contractor shall provide all personnel, equipment, tools, materials, supervision and other items and services necessary for the ongoing help desk support, development, testing, production, maintenance, and sustainment services of the MPES web-based applications.

This contract also includes all the services and support associated with the above tasks such as: documentation, support for systems engineering activities and events, program management activities and reports, configuration management, and support for meetings and conferences associated with program activities.

Support is also included for other systems affected by services or support for the program office’s systems, such as addition or update of interfaces.

The Contractor shall comply with all applicable Department of Defense (DoD) and Air Force/Space Force directives and policies and program office processes and procedures, in the performance of activities and tasks identified in this

PWS.

2.1 General Information. The Air Force/Space Force Military Manpower program is the foundation of the MPES U/S application. One of the primary program objectives is to enhance and expand MPES functionality (to include new and emerging MPES requirements) and to support and translate evolving Congressional, Office of the Secretary of Defense (OSD), Secretary of the Air Force (SecAF) and Air Staff policy, procedure, and requirements in the execution of the Air Force/Space Force Manpower programs.

These new and emerging requirements create a high operational tempo for implementation that necessitates a fundamental understanding of Air Force/Space Force manpower programs as they relate to the MPES applications. Therefore, it is necessary that the development team understand key manpower functions to include, but not limited to: DoD Planning, Programming, Budgeting and Execution (PPBE); Air Force manpower programming and allocation process of Air Force/Space Force manpower resources at the Headquarters, MAJCOM and Base levels; designing and developing algorithms and conducting advanced modeling in support of an extremely large workforce; Air Force/Space Force Organizational Structure.

2.2 Current System—the current MPES capability includes an unclassified and classified environment (MPES-U/S and MPES Manpower Data Mart -U/S) composed of multiple web servers, applications, and SQL Server databases as the backend. These two environments are hosted in DISA JSP managed datacenters configured using virtual machines that run Windows Server platforms. The applications running on MPES are written using various software technologies and languages such as Smart Client, ColdFusion, Java, Java Script, .Net, C#, AJAX, ExtJS, Aspose.NET, CSS, JSON, XML, XSLT. In addition, COTS products such as Atlassian JIRA, Jenkins, Git, Gradle, Maven, and IntelliJ IDEA are used as part of the environment.

MPES-U is a web-based application that currently consists of six distinct modules designed to collect and disseminate Total force execution of programmed manpower end strength:

1) Unit Manpower Document (UMD) provides the capability to manage and produce Unit Manpower

Document (UMD) information for use at all levels with the Air Force, Space Force and DoD. The application depicts end strength and billet level detail for Active Duty, Civilians, Guard and Reserve forces.

2) Aircrew Requirements Review Module (ARRM), documents and monitors rated staff requirements including pilots, navigators, air battle managers, and career enlisted aviators.

3) Force Structure Book (FSB) Module—a data reference and resource that provides a snapshot of sustainment organizations by standard requirements code.

4) Manpower Grades Allocation Module (MGAM) Module—facilitates the grade factor determination process, document results and allows for relevant grade factors adjustments/review by Air Force Career Field Managers (AF CFMs).

5) Senior Grades Allocation Module (SGAM) Module—facilitates, the coordination, approval, documentation, and implementation of the Air Force Order of Merit.

6) United States Space Force (USSF) Module, mirrors MPES-U/MPES-S Air Force modules but captures unique and specific USSF requirements.

MPES-S application currently consists of two functional modules, Future Years Defense Program (FYDP) & Business Objects (BO) Data Mart. HQ USAF/A1M (Directorate of Manpower, Organization & Resources) uses the FYDP module to program and manage the Air Force and Space Force manpower future years budget. Following the Program Objective Memorandum (POM) & President’s Budget (PB), manpower FYDP (aka manpower end strength) is allocated to the Major Commands (MAJCOMs) to adjust their UMDs accordingly. MPES is the official system of record of all Air Force and Space Force manpower budget actions (manpower FYDP) and the authoritative data source for all Air Force and Space Force manpower actions (UMD). BO is the reporting module that supplements MPES FYDP to create custom reports.

MPES Manpower Data Mart (Query, Reporting and Analysis) There are two separate and distinct primary instances of the MPES Manpower Data Mart. One instance operates on a SIPR environment (FYDP Universe) and the other operates on the NIPR environment (UMD Universe and MGAM/SGAM Universes to include any new emerging requirement module universe). Each instance has different interfaces, multiple Universes, and its own design. Additionally, although both share a common set of data sources, each instance has specific data sources.

Each instance is updated throughout the year to support ever evolving manpower query, reporting and analysis requirements. For the purposes of this document, the term Data Mart refers to both the SIPR and NIPR instances.

3. GENERAL REQUIREMENTS

The Contractor shall work with Agency stakeholders and technology professionals to properly understand manpower and MPES business requirements and develop a current and relevant industry best practice approach to technology solutions. To maintain and enhance the application development the Contractor will employ Agile Sprint development cycles that require continuous collaboration and feedback between the Contractor development team/Contractor Program Manager and the Government team.

The Contractor shall perform system administration functions to support the web based MPES and applications. The

Contractor shall install, monitor, and configure the server software and database functions of the web application.

This includes user account maintenance, database administration, troubleshooting problems with the server, and installing and configuring new versions of the software.

3.1 Overview

General activities within the PWS include:

• Design

• Development

• Integration

• Testing

• Deployment

• Sustainment/maintenance

3.2 Design. When tasked to perform design activities to support sustainment, the Contractor shall use standard methodologies to develop designs for new solutions or baseline updates for maintenance upgrades to the current system. Design incorporates DoD/Commercial common standards, common architectures, and common parts into a comprehensive product or service implementation plan.

The Contractor shall use standard methodologies to develop designs and baseline estimates for maintenance updates to the current system. Design incorporates DoD and Commercial common standards, common architectures, and common parts into a comprehensive product. Design integrates and synchronizes products and services with existing product and service solutions and considers reuse or reconfiguration of existing software to the maximum extent possible. Design includes integration and synchronization of the resource input from a teaming partner(s) or subcontractor(s) into the final product. Design includes obsolescence screening to assess the supported useful life of proposed software components. Design also includes the incorporation of concepts relative to ease of sustainment and cost savings in the final product and addresses the life cycle requirements of the selected Course of Action

(COA).

The Contractor shall deliver all design and associated documentation appropriate for the effort, as well as recommendations for changes. The Contractor shall present the designs and recommendations to the Government for approval in conjunction with technical design reviews. The Contractor designs shall consider all internal and external interfaces.

When the objective is to provide a solution based on COTS, the primary focus of design efforts under this contract will be for the configuration, business process changes, databases, branding of presentation layer, interfaces, and afloat user capability as required. The objective when using COTS software is to minimize customization. When conducting fit/gap analysis, the Contractor will be provided as-is business processes, and high-level requirements.

During the fit/gap analysis, the Contractor shall use the out of the box capability or employ configuration of the software as much as possible and will document the fit of requirements and deliver as to-be processes for functional business owner use during investment certification processes. If customization (reports, interfaces, conversions, extensions (RICE)) is necessary, the Contractor shall provide a design recommendation for government approval, implementation cost, life-cycle support costs for the customization, analysis of risk to the COTS life-cycle support, and lead time estimate for all planned customizations. The Contractor shall also include an analysis of how proposed customization will impact implementation of COTS software product upgrades.

3.3 Development. The term development in this PWS is used to describe activities related to sustainment upgrades.

It includes database, reports, conversions, extensions, and interface development. Development in general includes the standardized processes and procedures by which a contractor transitions a design into a deliverable product or service. Development integrates products and services provided by a teaming partner, subcontractor, or COTS vendor. Development also includes unit, integration, and regression testing of teaming partner, subcontractor, or vendor provided products and services. Development includes ensuring all necessary components, interfaces, and data migration and exchanges satisfy functional and performance requirements. Development also includes all the associated documentation.

The Contractor shall support testing during development IAW the design approved by the Government. The Contractor shall configure, customize, and develop software components and interfaces using any proven software development methodology (e.g. rapid development, Agile, hybrid waterfall development); including close coordination with the appropriate Government personnel to identify and tailor specific technical review requirements for each iteration, increment, or release of software to be delivered. Development includes: adoption, reuse, or reconfiguration of existing components, configuration and implementation of COTS products, and new software code development. When a COTS product is the baseline, the Contractor shall leverage existing capabilities and COTS products for satisfaction of requirements to the maximum extent practicable.

The Contractor shall ensure delivered functionality operates within a secured information technology environment according to all Defense Information Systems Agency (DISA) prepared Security Technical Implementation Guides (STIGs), Security Requirements Guides, and other DoD mandated secure configuration guides during the development, test, deployment, and maintenance. At a minimum, the Application Security and Development, Operating System, Database, and Web Server STIGs are met.

3.4 Integration. The Contractor shall perform integration of software components and external interfacing applications and capabilities. The Contractor shall ensure that all internal and external integration is performed to satisfy all functional and specified performance requirements. External integration includes interfaces and data exchanges with external systems as well as integration with host facilities, platforms, and networks. The Contractor shall ensure that products are compatible and interoperable with all prior versions as necessary. Integration may include products and services provided by a teaming partner, subcontractor, vendor, or other Government activity.

Integration includes effort in: (a) the definition, collection and deployment of test data; (b) data management and migration; (c) deployment plans; (d) installation procedures; (e) system and database administration; (f) support for implementing applications and systems, (g) databases in development; (h) test; (i) production and failover environments; and (j) network connections.

The Contractor shall ensure delivered functionality operates within a secured information technology environment according to all Security Technical Implementation Guides (STIGs), Security Requirements Guides, and other DoD mandated secure configuration guides during the development, test, deployment, and maintenance. At a minimum, the Application Security and Development, Operating System, Database, and Web Server STIGs will be met.

When tasked, the Contractor shall migrate data and users from existing systems to the new system. Analysis and planning will be required to properly execute the data migration, including special handling for controlled information.

The Contractor shall provide ad hoc technical consultation or participate in an integrated team to solve problems or make improvements to MPES and implement those solutions.

3.5 Testing The goal of testing is to ensure that the functionality is delivered and that the integrated application(s) perform as expected with minimal defects. Testing throughout the project lifecycle will consist of both Contractor and Government testing events. The Contractor shall provide a Test Plan, including unit and system testing, interface and usability testing, interoperability testing, and data integrity testing to the Government for approval. Test all application releases and system modifications in the contractor test and quality assurance environment. The Contractors shall conduct all test planning, preparation, execution, and reporting for testing the application during iteration tests and demonstrations. This testing is the functional development testing phase that verifies that the developed application is free from defects, to include security vulnerabilities, and is a candidate for software release.

Testing shall adhere to the program office’s standard practices and procedures. Results will be included as verification of functional development testing in preparation for Test Readiness Review (TRR).

All incremental test events will be managed by the Government. The Contractor shall coordinate closely with the Government to provide technical support for these test events. This support includes:

• Test event planning

• Test scenario development

• Test environment design

• Test data development

• Test script development (to measure satisfaction of SRS functionality)

• Traceability matrix development (mapping test scripts to SRS requirement(s)

• Hot wash meetings

• Severity code adjudication

3.6 Deployment. The goal of deployment is to ensure that the tested and accepted product is smoothly transitioned into production, go-live status and that the impacted users and organizations are prepared to operate with the new system(s). Deployment may include products and services provided by a teaming partner, subcontractor, vendor, or other Government activity. Deployment includes effort in: (a) deployment, organizational change management, or training plans; (b) production installation and rollback conditions and procedures should the initial go-live fail; (c) operations procedures that enable end-users to acquire the skills and knowledge necessary to effectively use the product and/or service; and (d) ensuring Help Desk/user support is available during and after deployment.

3.7 Sustainment/Maintenance

• Sustainment, which includes processes, procedures, people, materiel, and information, are required to support, maintain, and operate MPES its core service level. Additionally, sustainment includes documentation, operations, deployment, security (including C&A support), configuration management, training (users and sustainment personnel as required), and Tier II help desk.

• Maintenance is the process of modifying MPES application software and database to correct faults (bug fixes, system breakage, and emergency fixes). Maintenance includes:

o resolving software problem reports and the resolution of outages o executing security updates in support of IAVM o ensuring products/components operate as required and satisfy performance requirements o keeping all production support documentation up to date including administrator and user documentation, training materials (as required), and other logistics documentation o testing and implementation of upgrades/new versions, including Service Packs o completing post-production checklists o providing technical support to the hosting facility as necessary

4. PROGRAMMATIC REQUIREMENTS

The Contractor shall use an integrated program management system to plan, direct, integrate, and control the administrative, management, technical, logistical, financial, production, and support functions of each specific task.

The Contractor shall manage work efforts to optimize total system performance, promote interoperability and common solutions, and minimize total ownership cost. The Contractor shall measure, monitor, and assess the progress of the work performed and costs incurred under the contract task. The Contractor shall adopt a total system and system of systems approach to product support and structure system by design, testing, support planning, resourcing, and post-fielding.

4.1 Contract Progress, Status, and Management Report Preparation. The Contractor shall submit a monthly status report IAW Contractor Progress, Status, and Management Report. The report shall identify and contain summary-level information on all on-going tasks, to include status of work completed, and identify any cost, schedule, and performance risks or issues. This CDRL shall identify the Contractor’s staffing approach and identify the method of managing and reporting cost and progress. Operational metrics, status, and other sustainment reports will be required as part of this report.

4.1.1 Monthly Status Report (MSR) Worksheet. The Contractor shall complete and submit the MSR Worksheet that is part of the Contractor’s Progress, Status, and Management Report. The MSR worksheet will enable the Government to monitor monthly schedule and technical performance progress. This report shall assess the status of each effort planned and performed in accordance with the PWS. This report shall include an explanation of the efforts that were completed, the efforts currently in progress, and the efforts planned for the next month. The report shall include descriptions of any barriers that the contractor is facing, as well as recommendations for overcoming such barriers.

4.2 Contractor Performance Assessment Reporting System (CPARS). The Contractor shall provide input to the CPARS system according to the contractual requirements of this solicitation.

4.3 Project Management Plan. The Contractor shall provide a plan describing the program management system IAW Project Management Plan. The Project Management Plan shall consist of the organizational structure, the assignment of functions, duties, and responsibilities, the procedures and policies and the reporting requirements that are established for the initiation, monitoring, control, completion, test, and verification, and reporting of contractual tasks, projects, and programs. The Contractor’s organizational structure, methods, personnel, and internal support functions shall be developed describing roles, responsibilities, names and types of personnel assigned, security, etc., required to successfully perform this contract. The Management Plan shall also include staffing and transition plan.

4.3.1 Personnel Certifications. The Contractor shall ensure that all Contractor personnel have completed all the training and certifications necessary to perform the tasks and activities identified within this contract. This includes SCRUM certifications, Cyber Security Workforce (CSWF) certifications, certifications for developers, and others specified. The Contractor shall identify the certifications as soon as new personnel are onboarded/hired.

4.3.2 Contract Transitions Support. The Contractor shall provide transition support as needed to ensure a smooth transition to a successor contractor prior to the termination of the existing contract. The Contractor shall identify their resources and activities associated with the overlap and transition to a follow-on contractor. The Contractor shall include a status of personnel resources and activities associated with the transition as part of the monthly status report. The Contractor shall provide additional status updates as needed and required by the Government.

The Contractor shall provide the Government with all the information and final documentation produced as part of the existing contract and assist in the transfer of information (including a general understanding of the products) to the successor contractor. Software products and manuals shall be delivered as end items IAW Computer Software Product End Items. Other documentation shall be a final delivery of products that were previously prepared IAW the PWS and the associated CDRLs for documentation.

4.4 Configuration Management Plan. The Contractor shall perform Configuration Management (CM) services consistent with the Program’s CM processes, tools, CM Standard Operating Procedure (SOP), and Configuration Control Board (CCB) processes. Configuration information includes requirements documents, Requirements Traceability Matrices, data dictionary, business rules, data mapping, and SE Documents associated with interfaces and data management. Upon approval by the Government, the contractor will follow the Configuration Management Plan for all CM actions.

5. TECHNICAL REQUIRMENTS

5.1 Software Development and Support. Contractor personnel performing Information Assurance tasks in this section shall attain and maintain a DoD Information Assurance System Architecture and Engineering (IASAE) Level 2 certification prior to gaining system access. The contractor shall provide all software development, software engineering, quality assurance, testing, and system maintenance and support for the MPES application.

Modifications and updates shall include testing performed by the Contractor including regression testing, performance testing and installation verification. Testing should represent a complete systems test performed by a Quality Assurance (QA) or Test team.

5.1.1 Contractor Furnished Equipment to Support Testing and Development. The Contractor shall provide its own hardware and software to support development and testing of MPES—UMD5, FYDP5, MGAM, SGAM, MPES Manpower Data Mart, ARRM, and FSB modules [as well as new/emerging MPES requirements module(s)]— at its facilities. The government will provide a list and configuration of equipment required. These Contractor development and test environments are separate from the Government production, testing and user acceptance environments, but shall mirror the production environments by having at a minimum development, testing, and user acceptance environments to ensure compatibility and consistency.

5.1.2 Software Task Types and Classification. Software efforts tasked under this paragraph shall be classified in accordance with the following categories:

• System Requirement: Includes how new or existing functionality in the application should perform; determine which solution within the existing application structure and environment needs to be produced and/or delivered.

• System Enhancement: Includes minor or major enhancements to MPES, depending on level of effort involved. Improves current software requirements or applications, when necessary, to meet current and future Air Force/Space Force Manpower program requirements.

• System Modification: Major changes to existing system functionality by the revision of existing program rules and/or deletion of existing requirements or functions, to meet current and future Air Force/Space Force Manpower program requirements.

5.1.3 System Development, Maintenance, and Enhancement. The Contractor shall provide personnel to both develop and maintain the current system and enhance the next generation version of MPES. The Contractor shall follow a change control board (common practice in the application/software development industry) software enhancement process to include requirements definition, design, documentation, testing, and release of bug fixes, enhancements, modifications and new MPES versions. The Contractor shall continue to enhance MPES and any associated MPES interfaces throughout the contract period. The Contractor shall complete MPES system bug fixes, enhancements and modifications at a time determined by the Government and with input from the Contractor. Upon release of MPES bug fixes, enhancements, and modifications, the Contractor shall send MPES mailer notifications to all users, notifying users of all new system updates and changes along with any guidance and instruction on the system updates/changes.

5.1.4 Software Enhancement and Modification. The Contractor shall initiate software enhancement and modification efforts according to the priority established by the Government. The Contractor shall implement a Configuration Management Plan to track program changes/modifications and to ensure Contract Officer Representative (COR) approval of proposed/submitted System Change Requests (SCRs) in MPES.

5.1.5 The contractor shall provide subject matter expertise for MPES U/S product suite including Oracle, Cold Fusion, SQL Server, Windows Server, Java and JavaScript, Microsoft .NET, AJAX controls, ExtJS, SmartClient, Yahoo Interface Library, Aspose.NET, CORE, C#, Source Code Management (SCM), Requirements Management (RM), Business Objects XI, F5 iRule Scripting, Business Objects Data Integrator, xSQL Schema Compare, CSS, XML, JSON, XSLT, IIS, Apache Tomcat, Maven, Final Builder, Eclipse, JRebel, and ModelGlue Framework.

5.1.6 Functional Knowledge/Experience. The Contractor team shall have demonstrated knowledge in supporting enterprise applications currently residing at the Pentagon. Included in this support are key operational support and system integrity for; COOP solutions; Risk Management Framework (RMF) Methodology; experience with Common Access Card (CAC) login capability; and managing development and technical support using Agile and DevSecOps best practices tailored to the AF environment and technical architecture. These best practices include participation in requirements development and all agile sprint ceremonies by representatives from development, cyber security, and operations teams. Additionally, the contractor shall provide training in DevSecOps practices to ensure continued alignment between contractor team activities and the government priorities.

For workload history and historical workforce, see APPENDIXES D and E.

The following is the required experience levels for technology used for the applications:

Software Development Tools Required Years of Experience

SQL Server 10 – 15

Cold Fusion 10 – 15

Smart Client 10 – 15

Java Script 10 - 15

Microsoft.Net 10 - 15

Business Objects 10 - 15

5.1.7 Technical Editing Services. The Contractor shall provide technical editing services to make all changes necessary to program documentation because of the software changes. The Contractor shall make updates to all documents that necessitate the change, within fifteen (15) days, following the Government signing off on the completion of the software change. The Contractor shall release changes to the documentation as a block release [patches/updates/builds] in accordance with scheduled software release cycles. Block releases of documentation shall occur every three (3) months. Out-of-cycle releases will be as agreed upon between the Contractor and the Government. The Contractor shall provide MPES system analysis/assessment of the application structure and environment during the contract lifecycle.

5.1.8 Use of COTS Tools and Software. The contractor shall seek to configure off-the-shelf aspects of the selected platform before recommending a customized coding approach for MPES- NIPR/SIPR applications software development and support based on needs of government.

5.1.9 MPES-NIPR/SIPR Development Cycle. To maintain mission success, MPES-NIPR/SIPR development shall adhere to an iterative development cycle that requires continuous collaboration and feedback between the Contractor development teams/Contractor Program Manager and the Government PM, and COR. These interactions include, but are not limited to, prototyping, demonstrations, white-boarding, technical design brainstorming conversations, and project reviews.

5.1.10 Cloud Migration. Upon government direction, contractor shall migrate MPES system to a government-approved cloud environment IAW most current DoD Cloud Computing Security Requirements Guide. The contractor shall provide a timeline, plan, and milestones for government approval. Migration shall not interrupt system access and shall not negatively impact mission. Any modifications to the contract will be implemented through a standard change order process, with agreed-upon cost and schedule adjustments.

5.1.11 Enhancements/Engineering Change Proposal. Upon request from the Government, the Contractor shall provide an Engineering Change Proposal to provide engineering and technical expertise to assist the Government in integrating components of other mission and technology areas into the system architecture.

The Government can initiate Engineering Change Proposals as needed for modifications to MPES. The Contractor shall provide a response to include anticipated schedule and funding required to meet the Government’s proposed changes. The proposed scope may include:

• Expanding or enhancing the functional architecture of hardware and software assets to support new technology and mission areas.

• Identify emerging technologies that enable MPES to meet business requirements more effectively and efficiently through relationships with team members, industry standards organizations, and vendor partners.

• When directed, the Contractor shall provide assessments to the Government which detail how MPES can be modified to support specific missions, architectures and/or environments.

5.2 Software Maintenance. Contractor personnel performing Information Assurance tasks in this section shall attain and maintain DoD IAT level 2 certification prior to gaining system access. The Contractor shall provide system support to maintain the functional processes within MPES. On a weekly basis, during normal operations, the Contractor shall ensure full functionality of the MPES software and databases are available for online use. The Contractor shall restore the maintained software to normal operation whenever the Contractor becomes aware of or is informed that the normal operation has been interrupted (i.e., due to system outage as result of server outage and/or network connectivity issues). Upon identification or notification of MPES software interruptions, the Contractor shall immediately prioritize return of MPES software to normal operations above all other contract task requirements.

5.2.1 MPES software availability. The Contractor shall maintain normal operations of MPES software ensuring availability of the system for online use. The Contractor shall not allow non-availability of the system to exceed 8-hours per month, except for scheduled maintenance or emergency downtimes (i.e., server crashes, virus attacks). The Contractor shall coordinate with the Government PM and COR on all scheduled maintenance or downtimes that impact availability of the software for online use. Weekly scheduled maintenance operations (to include day and time) shall be posted on the MPES web site.

5.2.2 Corrective Software Maintenance. The Contractor shall initiate software maintenance efforts to correct problems according to the priority established by the Government PM and COR. The Contractor shall include, on the next monthly status report statistics, the number of problems reported, nature of problems, problem status, and corrective actions. Also include number of system downtime occurrences, length of time system is down, and reason for downtime.

5.2.3 MPES mailer notifications. In addition, the Contractor shall send MPES mailer notifications to all MPES users, notifying users of all maintenance and emergency downtimes (scheduled and unscheduled) that will include expected timeframe to have MPES system back up and running. The Contractor shall provide notification, 24-hours in advance, for scheduled maintenance down times.

5.2.4 The Contractor shall make changes required to correct performance of functions described in existing system documentation as part of software maintenance. On a weekly basis, during normal operations, the Contractor shall evaluate any problems forwarded to MPES user feedback folder and/or designated email folder that is maintained within MPES. The evaluation shall include requirements analysis, clarification of the problem with the originator, determining if correcting the problem is feasible and cost effective, and the consequences of the proposed change. The Contractor will coordinate with the Government PM and COR on all problems.

5.3 Quality Assurance and Testing. The Contractor shall provide a plan that ensures the integrity of services provided under this contract, called a Quality Control Plan (QCP). The QCP is due within fifteen

(15) days after contract award. On a weekly basis in support of the QCP operations, the Contractor shall provide full analysis of hardware, software, and business rules to ensure quality of MPES products. The weekly QCP operations also include testing application code releases for both maintenance and feature releases, release notes for every application build, verifying business requirements, performing code reviews, validating data, test reports, release management, and creation of a test strategy, test plan, and test cases. In addition, in support of the weekly QCP operations, the Contractor shall perform unit and system integration testing on all software. The Contractor shall document integration test procedures and test results as necessary, and these test items will be maintained in the Software Enhancement Folder for Government review.

5.3.1 User Acceptance Testing. The Government will perform user acceptance testing of the software (on the testing stage) prior to release of any MPES update or change to the MPES production site, to demonstrate that the software is valid, and requirements are met. The Contractor shall not implement changes to the maintained software on the MPES production site until Government acceptance testing is completed and the Government has accepted the change as valid system update and/or change to MPES and the Government has instructed the Contractor to implement system update/change to the MPES production site.

5.4 Code/Software Review Process. Within three months of award of contract, the Contractor shall conduct and complete a formal/in-depth code review of the MPES web-based applications to include a systematic and line-by-line examination of the MPES code.

5.4.1 Application Development and Review. This should be adequate time to conduct/complete using two senior application developer/code and software review analysts full-time.

5.4.2 Senior Application Developer/Code and Software Review Analyst (Two Required). Contractor personnel performing tasks in this section shall attain and maintain DoD IASAE level 2 certification prior to gaining system access. Code review is intended to find and fix mistakes and flaws that were overlooked in the initial development of MPES. In addition, the code review is intended to check and validate the adherence of coding standards, the quality of the comments, and consistency of the overall design. This will directly improve the overall quality of the software. In the Option Years, formal/in-depth code review is not required, but the Contractor shall conduct a yearly quick code review to ensure coding standards, thus, to ensure system quality, reliability, and system security. Throughout the lifecycle of the contract, the Contractor shall conduct a software review of the MPES web-based application to check for end-of-life software and ensure record management of support agreements are in-place for major MPES software components.

5.5 COTS Software Configuration. Program efforts may include the implementation of COTS software products as the baseline solution for the new capability or technical refresh of an existing capability. The Contractor shall perform all tasks and activities necessary for the analysis, impact and implementation of COTS products including installation, configuration, customization, and integration with other software, hardware, and networks. The Contractor shall coordinate with COTS software vendors and support as necessary.

5.6 Software Licensing. The Contractor shall provide acquisition support for attaining software licenses and maintenance updates. Licenses are generally required for development and administrative support, but the Contractor shall support the acquisition of software enterprise and other operational licenses when necessary.

5.7 Documentation. The Contractor shall provide all changes necessary to system documentation as a result of system and software changes to the Government PM and COR. System documentation includes but is not limited to:

Technical Requirements Document, System Architecture Diagrams, Database Design Document, Data Dictionaries, Source Code, Training and Help materials for users, and other DoD Architecture Framework (DoDAF) elements as applicable and in accordance with DOD and DON issuances.

The Contractor shall maintain the following MPES documentation:

• Case Complete software to maintain all system documentation

• System Change Requests (SCRs); posted/updated on MPES site

• MPES User Guide; updated on MPES sites

• MPES Quick Reference Guide; updated on MPES site

• Any other applicable MPES training guides/instruction; posted/updated to MPES site

• Interface Control Agreements (ICAs) as required to document interfaces between MPES and other systems

• Video Tutorials

5.8 Database Administration. Database Administration includes maintaining the logical and physical data models for databases, implementing physical databases, maintaining reference tables and metadata, and providing support to all environments.

Contractor personnel performing system administration will be required to obtain and maintain a Security + Certification at task order award and through the duration of the task order. Additionally, contracting personnel performing Database admin shall maintain IAT level 2 certification prior to gaining system access.

All Contractor personnel must meet the terms of this PWS and must be a United States citizen. Applicable directives include DoD 5200.2, Procedures for the DoD Personnel and Security Program, and AFI 31-501.

Any costs associated with obtaining the certification shall be the responsibility of the contractor.

Additionally, a secret clearance may also be required while working in the A1M Sensitive Compartmented Information Facility (SCIF), Pentagon. Contractor personnel identified to work in one these facilities will be required to obtain and maintain a secret clearance while working in one of these facilities. Any costs associated with obtaining the security clearances shall be the responsibility of the contractor.

5.8.1 The Contractor will provide database administrator (DBA) support of the SQL Server (MPES-U/S) database application. Tasks shall include, but are not limited to the following:

• Maintain Data Dictionary and Entity Relationship documentation

• Manage the Production Database

• Update and Create Database Fields and Tables

• Monitor Database Growth and Performance

• Upgrade database tools as necessary and appropriate

• Perform Database Monitoring and Updates to Ensure Data Integrity

• Perform Database Backup and Recovery

5.8.2 Database Modification. Following approval by the Government PM or COR, the Contractor shall make all database changes/modifications identified by the Contractor or the COR according to the priority established by the Government PM and COR. This evaluation shall include requirements analysis, clarification of the problem with the originator, determining if correcting the problem is feasible and cost effective, and the consequences of the proposed change. The Contractor shall coordinate with the Government PM and COR on all problems.

5.8.3 End of Month Database Task Automation. The Contractor shall automate all End of Month (EOM) database tasks where possible. This will include database snapshots, backups, interface transmissions, expiring positions, report creation, and reference table dumps.

5.9 MPES Manpower Data Mart (Query, Reporting and Analysis). The Contractor shall provide all design, development, testing, maintenance, and support activities to support the Data Mart. The Contractor shall support and maintain the MPES Manpower Data Mart to ensure its ability to accurately extract, transform, load, process, store, and analyze data from MPES and other relevant databases as required.

5.9.1 Automated Data Quality Assurance. For systems of different security classifications, the capture, organization, and storage capabilities must consider all aspects of security as defined in current Air Force instructions and regulations. To the greatest extent possible, the contractor shall automate data extraction, transformation, and load (ETL) and data quality assurance procedures. The Contractor shall maintain error logs. The Contractor shall identify data quality errors existing in source data prior to data load. In these instances, an analysis of the data quality error must be performed to include coordination with source data ‘owner’ and a recommendation of how to resolve and/or highlight the data quality error within the Business Objects reporting environment.

5.9.2 The Contractor shall ensure that data refreshment occurs daily, at a minimum, but the contractor must ensure more frequent data loading in support of various manpower exercises as required.

5.9.3 The Contractor shall ensure that all MPES-NIPR/SIPR Data Mart hardware and software is maintained and updated as necessary. In addition, the Contractor shall work closely with appropriate Air Force personnel to ensure the Data Mart is able to operate on the Pentagon network as network configurations, operating systems, standard desktop configuration (SDC) images, and governing policies and procedures evolve over time.

5.9.4 The Contractor shall conduct MPES-NIPR/SIPR Data Mart requirements analysis meetings to identify additional requirements and capabilities. These additional requirements should include integration of data from other sources (databases, flat files, etc.). Based on these meetings and other requirement identification sources, the Contractor shall recommend or discuss the recommendations for system enhancements, provide a technical evaluation, and implement additional requirements and capabilities following Government PM and/or COR approval.

5.10 Annual Disaster Recovery Plan (DRP). Contractor personnel performing Information Assurance tasks in this section shall attain and maintain a DoD Information Assurance Technical (IAT) level 2 certification prior to gaining system access. The Contractor shall develop and test a DRP within the first three months of the contract, maintain up-to-date plans to ensure changes in the MPES environment are considered and addressed. Plans should be well-structured and easily understood to aid in the recovery of business operations as quickly and effectively as possible from an unforeseen disaster or event. The DRP shall include step-by-step recovery instructions for restoring MPES applications and services and be stored in a secure offsite location. The DRP shall be tested annually.

5.11 System Interfaces. Contractor personnel performing Information Assurance tasks in this section shall attain and maintain DoD IAT level 2 certification prior to gaining system access.

The Contractor shall design, develop, and maintain necessary MPES-NIPR/SIPR interfaces with other systems as required. The Contractor shall work closely with the COR and the external system POCs to:

• provide secure mechanisms to allow data exchange and interaction with external systems collect and analyze system interface requirements

• maintain and update data interchange documents

• attend system integration and other meetings as required

• provide system documentation, data schema, database, and meta data information as necessary

• provide data and database access as necessary

• design, develop and thoroughly document systems and/or data import/export processes

• accomplish data imports and exports as required

5.11.1…