Attachment 1 PWS W912HQ22R0007 - CEFMS Maintenance and Modernization SATOC - 06SEP2022.docx

PERFORMANCE WORK STATEMENT (PWS)

Maintenance and Modernization Services for the US Army Corps of Engineers Financial Management System (CEFMS II) for

USACE Finance Center (UFC) 06 September 2022

Table of Contents

1.0 Introduction

1.1 Background

The U.S. Army Corps of Engineers Finance Center has a requirement to support, maintain, , and modernize (including development and migrating the system to the cloud) the Corps of Engineers Financial Management System (CEFMS II) which is an enterprise financial management system supporting the business processes and mission of U.S. Army Corps of Engineers (USACE) worldwide. CEFMS II provides integrated, end-to-end automated financial management services enabling full transparency of funds execution for USACE projects. CEFMS II provides functionality for receipt and end-to-end execution of appropriated Civil Works and Military direct funding and reimbursable funding. CEFMS II provides automated pro-forma transactions and general ledger updates in compliance with U.S. Treasury Standard General Ledger (USSGL) proprietary and budgetary general ledgers policies. CEFMS II enables USACE to produce auditable financial statements and sustain audit readiness in accordance with guidance found in OMB Circular A-136, General Accepted Accounting Principles (GAAP) and Federal Accounting Standards Advisory Board(FASAB) CEFMS II data must be recorded, executed and reported in accordance with Standard Financial Information Structure(SFIS) and Standard Line of Accounting Formats(SLOA). CEFMS II has been designated as major AIS DBS for USACE and vitally critical to the day-to-day operations and carrying out the overall missions of USACE. The CEFMS II system requires continuous availability to prevent USACE mission failure.

1.2 Scope

CEFMS II is the premier financial management system in the Department of Defense and the US Army Corps of Engineers enterprise system for executing all financial management business processes and transactions within USACE. CEFMS II has over 72 areas of functionality and consists of approximately 62 Field Operating Activity (FOA) production databases and supporting development/testing environments. Each database has approximately 5525 tables and 329 views each. CEFMS II has a Corporate Reporting database consisting of approximately 700 tables and 100 views. CEFMS II has one Data Manager Database. CEFMS II application code is managed using PVCS and a custom developed problem reporting system. PVCS is the repository for all code changes, deployment, and configuration management for CEFMS II. PVCS functionality is paramount to deployment of new code in the following zones: Development, Test, QA, Production, and Disaster Recovery. This links the Problem Reporting system with configuration for tracking.

The CEFMS II proprietary application software to be supported includes:

· Oracle APEX: 24

· Oracle Forms: 2581

· Oracle BI Reports: 313

· Oracle Reports: 462

· Oracle SQR Reports: 743

· Database Functions: 172 (standalone)

· Database Packages: 1405 (actual package count, each contains multiple functions and/or procedures, estimate 10,000 additional packages and functions)

· Database Procedures: 1013 (standalone)

· Database Tables: 5525

· Database Views: 329

· Database Triggers: 1162

· CEFMS II system architecture currently consists of the following:

· Operating System: Solaris, Windows, Linux

· Oracle Database

· Multitenant for Oracle Database

· Real Application Cluster

· Partitioning

· Advance Security

· Database in Memory

· Golden Gate

· Data Integrator

· Directory Service

· WebLogic Server

· Enterprise Data Quality Profile and Audit

· Enterprise Data Quality Standardization and Match

· Oracle Analytics Server

· PVCS

· DBSIGN

· Hyperion

· SQR

· Oracle Forms

· Oracle Reports

· Oracle Access Manger

· Oracle HTTP Server

· Oracle APEX

· Oracle Real Applications Testing

1.3 Purpose

The purpose of this contract is to provide for CEFMS II system support, maintenance, and modernization (including development and migrating the system to the cloud) to meet the requirements of public laws, regulations, standards, stakeholders, and best business practices. The Contractor shall be responsible for maintaining/enhancing the CEFMS II system to ensure continuous system availability of the application. Services may include research, analysis, design, development, testing, and implementation of enhancements. Requirements may entail migrating selected CEFMS II functionality and Oracle forms to an HTML web application framework using current technology and products; providing enhanced reporting capabilities; and modifying CEFMS II architecture and application software to operate in USACE Cloud Environment.

2.0 General Requirements

2.1 Contract Management

The Contractor shall establish clear organizational lines of authority and responsibility to ensure effective management of the resources assigned to the requirement. The Contractor must maintain continuity between the support operations at UFC and the Contractor's corporate offices.

2.2 Contract Administration

The Contractor shall provide all necessary personnel and supervision to deliver technical services in response to the CEFMS II maintenance support and enhancement requirements. The Contractor shall establish processes and assign appropriate resources to effectively administer the Contract. The Contractor shall have a single point of contact between the Government and Contractor personnel assigned to support contract administration.

2.3 Non-Personal Services

The Government shall neither supervise Contractor employees nor control the method by which the Contractor performs the required tasks. Under no circumstances shall the Government assign tasks to, or prepare work schedules for, individual Contractor employees. It shall be the responsibility of the Contractor to manage its employees and to guard against any actions that are of the nature of personal services. If the Contractor believes that any actions constitute, or are perceived to constitute personal services, it shall be the Contractor's responsibility to notify the Procuring Contracting Officer (PCO) immediately.

2.4 Hours of Operation

Work performed at a Federal facility shall be in accordance with UFC core operating hours from 0900 to 1500 Monday through Friday, except U.S. Federal Holidays. The Contractor shall provide CEFMS II maintenance support during core hours. The Contractor shall provide non-core hours support as described in Section 2.5.

2.5 Non-Standard Operations

2.5.1 Upon determination by the Government that an emergency exists, the Contractor shall be notified of the need for priority response by the most appropriate method including, but not limited to, telephone or “in person" (if possible). Notification shall be followed up with an email. Contractor acknowledgement of the response shall be within 30 minutes of notification receipt.

2.5.2 The Contractor shall maintain an on-call service capable of responding to system failures within a one-hour period after normal business hours and on weekends.

2.5.3 The Contractor shall be available to work extended hours on an ad hoc basis to support CEFMS II maintenance and develop software solutions necessary to satisfy emergent needs due to changes in public law, policy, or data requirements.

2.5.4 Recognized Holidays: The Contractor is not required to perform services on the holidays listed below unless there is an extenuating circumstance as described in section 2.5 above:

Recognized Holidays

Memorial Day Juneteenth Thanksgiving Day Christmas Day

Independence Day

2.6 Travel

2.6.1 Infrequent Travel may be required. All travel will be within the Continental United States (CONUS) in accordance with the Joint-Travel Regulations (JTR).

The COR will be identified by separate letter with a copy to the Contractor. The COR monitors all technical aspects of the contract and assists in contract administration. The letter of designation issued to the COR states the responsibilities and limitations of the COR regarding this contract. The COR is not authorized to change any of the terms and conditions of the resulting contract. A warranted Contracting Officer is the only entity with authorization to negotiate and make changes to this contract.

2.8 Key Personnel

The key personnel positions are critical to the successful performance of this contract and are identified in Table 1 below. These key personnel must be assigned for the duration of the Contract. The Contractor shall always maintain a list of all Key Personnel. The Project Manager shall be responsible for managing the performance of the work. The identity of the Project Manager, and an alternate Project Manager shall be designated in writing to the Contracting Officer. The Contractor shall obtain the Contracting Officer’s written consent before making any substitution for designated key personnel. In the event of such substitution, the key personnel proposed to fill the specified role must have equivalent qualifications to the original individual.

The Project Manager (or the alternate) shall have the authority to act for the Contractor on all matters relating to the daily operation under this contract.

Table 1 – Key Personnel

Project Manager

Provides day-to-day management of all project activities under the task order. Manages and reports project schedule and performance. Manages personnel staffing and other administrative functions to meet established performance objectives.

Years of Relevant Experience: 10+ Education: Master’s or bachelor’s degree Certifications: No minimum required. Certification in Project Management (e.g., PMP) desired.

Skills/Experience: Project Management experience managing day-to-day operations across the project life cycle.

Senior Oracle DBA

Education: Bachelor's Degree Certifications: CISSP, Security+, or equivalent certification Skills/Experience: Experience as an Oracle DBA managing large Oracle databases and depth knowledge of Oracle performance and tuning.

System Engineer/ Architect

Defines and develops systems architecture from customer requirements. Possesses understanding of system requirements and Federal and DoD architecture standards. Capable of analyzing moderate to complex solutions and interpreting requirements into architectural artifacts.

Years of Relevant Experience: 10+ Education: Bachelor's Degree Certifications: No minimum required.

Skills/Experience: Experience leading design and systems architecture development using Federal/DoD architecture standards.

Senior Forms Developer

Maintains and compiles Oracle Forms, Libraries, and Menus in UNIX environment. Interprets software design specifications and translates them into Oracle Forms. Develops and unit tests Oracle Forms. Develops and maintains Oracle queries, stored procedures, functions, and packages using SQL Developer. Integrates modules with other modules and external systems. Mentors and transfers technical knowledge to employee staff as necessary.

Years of Relevant Experience: 7+ Education: Bachelor's Degree Certifications: No minimum Skills/Experience: Experience with developing Oracle forms using Oracle SQL language skills in the current version of Oracle (12c).

Senior APEX or Java Developer

Design, develop, implement, and maintain user-facing interfaces code and internet applications. Integrates applications by designing database architecture and server scripting, studying, and establishing connectivity with network systems, search engines, and information servers. Determine design methodologies and tools sets. Drive best practices, quality and consistency within design and development phases and coordinates efforts with fellow teammates. Identify production and non-production application features, limitations, and issues. Identify opportunities to fine-tune and optimize applications of java developed projects. Provide technical support and consultation for java application and infrastructure questions. Establish, refine, and integrate development and test environment tools and software as needed. Supports continuous improvement by investigating alternatives and new technologies and presenting these for architectural review. Develop and execute unit test plans to ensure compliance with specifications. Support formal testing and resolve test defects.

Years of Relevant Experience: 5+ Education: Bachelor's Degree Certifications: No minimum Skills/Experience: Proven working experience with Java development (HTML, CCS and Java scripting) and a strong understanding of Java and Java web applications. Working knowledge and experience with JDBC, SQL and database-stored procedures. Expert Knowledge and Experience with Oracle Application Express (APEX).

Education: Bachelor's Degree Certifications: No Minimum Skills/Experience: A strong knowledge of a comprehensive, modern accounting systems.

Skilled proficiency using Microsoft Office Suite (Word, Excel, Outlook, etc.).

Advanced English level.

2.9 Quality Control

The Contractor shall develop, maintain, and execute an approved Quality Control Plan (QCP) to ensure services are satisfactorily performed under this contract. The QCP plan shall define the processes to monitor Contractor performance and ensure compliance with the requirements of this contract and applicable regulations. The Contractor’s QCP shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services. The Contractor shall electronically submit a comprehensive, written QCP to the COR and the Contracting Officer within 30 calendar days of contract award. The QCP shall be reviewed by the Government before acceptance. After review of the quality control plan, the KO will provide the Contractor with written acceptance or rejection of the QCP along with any proposed changes.

2.10 Quality Assurance

The Government will evaluate the Contractor’s performance under this contract in accordance with the Quality Assurance Surveillance Plan (QASP). The QASP is the method by which the Government will measure Contractor performance in accordance with the performance standards. It defines how the performance standards will be applied, the frequency of surveillance, and the minimum acceptable defect rate(s).

2.11 Government Furnished Equipment

The Government will provide equipment, as necessary and workspace, as required, to Contractor personnel assigned to this requirement. The Government will provide workspace for Contractor personnel when working on-site at the Government’s facility.

2.12 Data Rights

The Government has unlimited rights to all documents/material produced under this contract. All documents and materials, to include the source code of any software, produced under this contract shall be Government owned and are the property of the Government with all rights and privileges of ownership/copyright belonging exclusively to the Government. These documents and materials may not be used, sold, or published by the Contractor without written permission from the Contracting Officer. All materials supplied to the Government shall be the sole property of the Government and may not be used for any other purpose. This right does not abrogate any other Government rights. The Government has unlimited rights in accordance with FAR Clause 52.227.14.

2.13 Copyright

The CEFMS II source code, technical data, and user manuals are copyrighted materials owned by the Government. Any information provided under this contract pertaining to the CEFMS II application is restricted to Government use only and not available for redistribution. The Contractor agrees to assign all copyrights to the Government for any new materials or modifications to existing materials that are produced by the Contractor during the term and in the scope of this contract.

3.0 Special Qualifications

The Contractor is responsible for ensuring their staff have the following qualifications.

3.1 The Contractor personnel assigned to the project shall be:

· The Contractor personnel assigned to the project shall be:

· Knowledgeable of DoD and Civil Works financial management laws, regulations, policies, and generally accepted accounting standards.

· Familiar with pertinent Office of Management and Budget (OMB) policies and federal financial management systems requirements.

· Knowledgeable of US Treasury USSGL pro-forma logic for federal accounting transactions and rules for both proprietary and budgetary general ledgers.

· Knowledgeable of DoD Standard Financial Information Structure(SFIS) data elements and the interworking related to accounting events.

· Expert knowledge/understanding of Oracle products and the ability to draw upon additional resources and maintain a “reach-back” knowledge base capability that can be utilized as needed.

· Expert knowledge of DoD End-to End (E2E) Integration framework and business processes including, but not limited to, procure-to-pay, acquire-to-retire, order-to- cash, budget-to-report, plant-to-stock, environmental liability, service-to satisfaction, proposal to reward, and cost management.

4.0 Specific Tasks

4.1 CEFMS II Maintenance, Modernization (Development) and Support Services

4.1.1 The Contractor shall provide Iterative Customer Driven Software Management and Development, IT Oracle Database Administration, Design, and System Engineering Services for the CEFMS II application. These services will be made available to the Government personnel of the USACE Finance Center. This work is variable in nature. It can be completed on a daily, weekly, or monthly basis depending upon changes in business processes and regulatory requirements. Work frequently entails aggressive mandatory deadlines, a high degree of complexity, and a high degree of uniqueness.

4.1.2 The Contractor shall possess experience and knowledge of the best business processes as described in Section 3.0.

4.1.3 The Contractor shall respond to and complete work requests timely. All specific work assignments associated with the contract tasks will be managed by work requests utilizing the CEFMS II Problem reporting system and will serve as the delivery accountability tool for these tasks.

Work requests will be categorized by the government using the following categories:

1. Stops user from performing functions in system as currently deployed

2. Corrections of update/recon/report (code and/or scripts)

3. Modifications required due to regulatory changes or at direction of UFC or higher headquarters

4. System performance issues to include tuning, referenced procedures, database integrity, and redesign of existing procedures

5. Maintaining and developing user documentation

6. Minor screen changes and screen modifications not critical to operation

7. Approved Configuration Control Board (CCB) system enhancements and reports

8. Data Calls

Work classification codes consist of the following and shall be assigned by the Contractor:

· AC Application Correction

· AE Application Enhancement/New Functionality (may require ECP)

· DA Detailed Analysis Prior to Application PR Development

· DC Data Correction Script Development

· DOC System Documentation Composition

· QA Quality Assurance

· SYS System, Database, Audit Support Activities

· Explicitly addresses security requirements

· Identifies the standards and tools used in the development process

· Documents the specific tool options and tool configurations used in the development process

· Documents, manages, and ensures the integrity of changes to the process and/or tools used in development; and

· Reviews the development process, standards, tools, and tool options/configurations yearly to determine if the process, standards, tools, and tool options/configurations continue to meet all security requirements.

4.2 Agile Development Process

The Contractor shall incorporate software development processes under this PWS using Agile Development Methodologies. Agile Development involves a series of short- duration, iterative projects that deliver incremental capabilities in shortened timeframes. It is intended to deliver working software quickly and evolves quickly to meet changing requirements.

The twelve principles of agile development include:

1. Customer satisfaction through early and continuous software delivery – Customers are happier when they receive working software at regular intervals, rather than waiting extended periods of time between releases.

2. Accommodate changing requirements throughout the development process – The ability to avoid delays when a requirement or feature request changes.

3. Frequent delivery of working software – Scrum accommodates this principle since the team operates in software sprints or iterations that ensure regular delivery of working software.

4. Collaboration between the business stakeholders and developers throughout the project – Better decisions are made when the business and technical team are aligned.

5. Support, trust, and motivate the people involved – Motivated teams are more likely to deliver their best work than unhappy teams.

6. Enable face-to-face interactions – Communication is more successful when development teams are co-located.

7. Working software is the primary measure of progress – Delivering functional software to the customer is the ultimate factor that measures progress.

8. Agile processes to support a consistent development pace – Teams establish a repeatable and maintainable speed at which they can deliver working software, and they repeat it with each release.

9. Attention to technical detail and design enhances agility – The right skills and good design ensures the team can maintain the pace, constantly improve the product, and sustain change.

10. Simplicity – Develop just enough to get the job done for right now.

11. Self-organizing teams encourage great architectures, requirements, and designs – Skilled and motivated team members who have decision-making power, take ownership, communicate regularly with other team members, and share ideas that deliver quality products.

12. Regular reflections on how to become more effective – Self-improvement, process improvement, advancing skills, and techniques help team members work more efficiently.

4.2.1 Requirements Definition

Requirement’s definition shall use agile development methodologies to capture capability needs through User Cases. This phase of agile development involves the users and process owners with participation by developers as needed.

4.2.2 Software Development Iterations and Integration

Software development shall follow agile development methodologies using short duration development cycles or “sprints” that produce demonstrable “interim deliveries” of software. These deliveries of capability may or may not be fielded to the operational community. The time required to create a delivery iteration is dependent on planning, complexity of features, or other influences. Iterations may also be based on a fixed time cycle, with variances in the number of features developed. The Contractor is expected to use continuous integration best practices in developing software solutions.

4.2.3 Product Testing

Product testing in the agile development process requires frequent engagement of the customer and/or designated representative testers. Agile development shall include use of automated regression testing techniques and utilities included part of a continuous software integration process. The Contractor shall ensure all products are thoroughly tested prior to delivery to the government. The Contractor shall support the Government to identify and correct product testing issues identified throughout the agile development process, but especially during integration testing of a releasable set of software features.

4.2.4 Software Releases

Based on a plan for each agile project, software releases shall be completed, delivered, and fielded. Most agile projects will require several iterations culminating in a release to the field. Every project will be tailored to the scope of the project, driving longer or shorter iteration and release schedules as required and directed by the Government. The Contractor shall participate in the release planning team and its process, including feature selection, with other Government directed representatives. Release planning is the responsibility of the Government, but the Contractor shall provide knowledge and input that is deemed critical by the Government to the planning process.

4.3 Application Maintenance, Development and Support

4.3.1 Overview

4.3.1.1 Utilizing the current Oracle product releases, the Contractor shall assist in the maintenance, system requirements analysis, design, coding, testing, and implementation of changes and enhancements of the software required for the operations of CEFMS II.

4.3.1.2 The Contractor shall possess experience and knowledge of the best business processes for Federal financial accounting transactions to include proprietary and budgetary general ledgers as described in Section 3.0 and shall have a knowledge of the applicable regulations referenced in section 5.0 to assist the Government personnel in the analysis of requirements.

4.3.1.3 The Contractor shall maintain the existing Oracle Forms, Oracle Reports, Oracle Analytics Server, Oracle Application Express (APEX) and Repository applications while making enhancements using new and innovative features provided by technology updates to include the CEFMS II repository.

4.3.1.4 The Contractor shall provide design of software that supports a service-oriented architecture to ensure seamless integration between applications.

4.3.1.5 The Contractor shall provide analysis, design, and development in integrating modern HTML web application development frameworks as a user interface to existing CEFMS II business process applications.

4.3.1.6 The Contractor shall provide continuous assistance in identification and correction of programming deficiencies, programming modifications based on regulatory requirements and/or modifications, data elements needed to enhance and produce forms and reports, and/or changes to improve functional operations of screens.

4.3.2 CEFMS II Modules

The Contractor shall provide maintenance, support, modification, and leverage new technology features to update areas of functionality that include but is not limited to the list below:

Contract Number to be Determined

· 2101 Schedule of Obligations and Expenditures

· Access Request Management System (ARMS) Module

· Accounts Payable Module

· Accounts Receivable Module

· Accrual Module

· Appropriation Expenditure Authority

· Appropriation Refund

· Army Contract Writing System

· Asset Life Cycle Management Module

· Asset/Facilities Management Module

· Audit Universe of Transactions

· Billing and Collections Module

· Budget Module

· Building & Structures Module

· Capital Property Recon Reporting Module

· Civil Automated Budget Module

· Corps of Engineers Manpower Requirements Module (CEMRS)

· Civil Works Infrastructure Financing Program (CWIFP) Module

· Civil Work Allowance Module

· Collections & Deposits

· Common Access Card (CAC) Authentication

· Consolidated Departmental Overhead Module

· Construction in Progress

· Corporate Reporting Module

· Cost of Doing Business Module

· Cost Share Module

· Cost Transfer Module

· Credit Card Module

· Cross Charge Distributable Billings

· Customer Order Advance Accounts Module

· Customer Order-Government Order Module

· Data Management

· Depreciation, Plant Increment, and Insurance Accounting Module

· Distributions Module

· Expend and Disburse Module

· Facility Management

· Foreign Currency Module

· Foreign Military Sales

· Funding Module

· Funds Distribution Module (FDM)

· General Journals

· General Ledger Chart of Accounts

· Government Order / Customer Order (GO/CO) Integration

· Homeowners Assistance Program (HAP)

· Inventory Management Module

· Integrated Manning Document

· Intra-Government Payment and Collection (IPAC)

· IRS Form 1099 Miscellaneous Module

· Long-Term Receivables Module

· Manpower Module

· Multipurpose Power Module

· Obligations Module

· Oracle Toolset Support

· Payroll Module

· Personal Property Management Module

· Problem Reporting Module

· Purchase Request Module

· Reconciliations/Data Integrity

· Real Estate Property Maintenance Module

· Reoccurring Payments Module

· Reorganization Module

· Reporting Module

· Revenue Generating Agreements Module

· Revolving Fund

· Small Purchases Module

· Specific Expenditure Authority

· Standard Resource Code Module

· Standard Revolving Fund Work Item Module

· Supervision and Administration (S&A) Module for Flat Rate Military Construction

· System Print Programming and Support

· Time and Attendance Module

· Training Module

· Transfers Module

· Travel Module – PCS/TDY

· Treasury Offset Program

· Unliquidated Obligations Review Module

· Multiple Interfaces with both internal and external systems

· Warehouse and Inventory Module

· Work Management Module

· Workload, Workforce Planning Module (WWP)

· Year-End Closeout Processing Module

4.3.3 Requirements and Analysis

4.3.3.1 The Contractor shall use teamwork and close customer collaboration in evaluating and analyzing system requirements.

4.3.3.2 The Contractor shall provide as requested analysis and recommendations for modifications or enhancements of coding.

4.3.3.3 The Contractor shall perform impact analysis and provide possible solutions for refinement and improvements of existing coding and processes.

4.3.4 Code Modifications and Development

4.3.4.1 The Contractor shall incorporate agile software methodologies and practices into development.

4.3.4.2 The Contractor shall participate in agile teams to provide technical guidance and assist with the refinement of previously developed functionality and create enhancement to functionality as directed by the Government.

4.3.4.3 The Contractor shall make changes to fielded software to meet new security requirements, correct errors in coding and meet new regulatory requirements.

4.3.4.4 The Contractor shall provide frequent deliveries of software development.

4.3.4.5 The Contractor shall respond quickly to changing demands and requirements.

4.3.4.6 The Contractor shall assist with the refinement/tuning of previous code development to improve performance or system functionality.

4.3.4.7 The Contractor shall provide system design for proposed system modifications that are revised as changes are made in the agile development process.

4.3.5 Error Corrections – Scripts

The Contractor shall diagnose system and data problems as reported by system accountants and end users. Data correction scripts will be created as needed to maintain system integrity and user functionality. All scripts will follow standard policy to ensure all audit requirements are met.

4.3.6 Testing

4.3.6.1 The Contractor shall conduct tests (e.g., unit, functional, system, interoperability, regression, security, and performance) of software throughout the development lifecycle using industry best practices of continuous integration methods and automated regression testing utilities. Testing materials (scripts, configurations, utilities, tools, plans, and results) shall be maintained under configuration control.

4.3.6.2 The Contractor shall develop and deliver testing materials in a format that allows the Government to reproduce the testing procedures and results within their own development environment.

4.3.6.3 The Contractor shall conduct testing related to non-functional requirements, including load, performance, and installation testing.

4.3.6.4 The Contractor shall correct and repair software defects throughout the agile software development process identified through all testing (including unit, system, functional, security, performance, and load testing) procedures.

4.3.6.5 The Contractor shall conduct inspections and provide analysis of testing results as directed.

4.3.6.6 The Contractor shall include the user/customer as part of the iteration tests/demonstrations as required.

4.3.6.7 The Contractor shall collect systems and application performance and load data as part of testing process.

4.3.6.8 Testing scripts, utilities, test execution, and testing results shall be historically maintained under configuration control for comparison and analysis.

4.3.6.9 The Contractor shall support the Government’s efforts to conduct integration testing of software deliverables within the Government’s Testing and Integration Environment.

4.3.7 Releases

4.3.7.1 The Contractor shall create detailed software deployment and fielding instructions.

4.3.7.2 The Contractor shall deliver as part of a software application the installation kits, all related source code, script and instructions for software builds, and associated design, development, and testing artifacts.

4.3.7.3 The Contractor shall release approved changes to production according to prescribed weekly schedules and as required outside of prescribed schedule.

4.3.8 Yearend Support

Yearend closeout is a critical process for the CEFMS II. The process includes various programs that support the financial closing process and opening business for the new Fiscal Year.

4.3.9.1 The Contractor shall provide support for data calls from Headquarters, auditors, and other external agencies.

4.3.9.2 The Contractor shall monitor routine system processes: System reconciliations, General Ledger posting, report stacks and CRON execution.

4.3.9.3 The Contractor shall provide project management plans in support of system modifications, upgrades, and enhancements.

4.3.9.4 The Contractor shall create presentations and technical analysis reports as directed by the Government to support discussions.

4.3.9.5 The Contractor shall support meetings with government/contractor teams defining artifacts, data models, services, system specifications, and architectures

4.3.9.6 The Contractor shall provide technical guidance to systems accountants in supporting the system.

4.3.9.7 The Contractor shall participate in committees and review groups as assigned.

4.3.10 Audit Support

The Chief Financial Officer’s Act requires that agency accounting systems produce Financial Statements that shall be audited in accordance with generally accepted government auditing standards and provide a report on the internal controls over financial reporting and compliance with laws and regulations. USACE consistently maintains an unmodified audit opinion on the Financial Statements. System changes must be in compliance with Federal Financial Management Improvement Act (FFMIA) and internal controls as specified by OMB circular A-123.

4.3.10.1 The Contractor shall provide audit support by maintaining and producing monthly universe of transactions and producing data requests and supporting other inquiries when requested.

4.4 Oracle Database and Application Design and Administration

4.4.1 The Contractor shall assist in continued support of the USACE Oracle Database and Application Server Administration, Design, and System Engineering Services required for the operations of the CEFMS II.

4.4.2 The Contractor shall leverage latest technology capabilities to meet customer needs with timely and seamless access to the cloud-based infrastructure, business applications, and data. This includes staying abreast of new feature offerings and new and innovative ways to provide technology value to USACE customers. Contractor shall keep management informed on incorporating all latest features and technology advances in CEFMS II to improve user interfaces, effectiveness, efficiency, and performance of the system.

4.4.3 The Contractor shall take advantage of features of the USACE Oracle licensed products listed below to meet the requirements of the CEFMS II system architecture plans with real-time failover and high availability solutions:

· Install, configure, and test the following point products in Development, Test, Quality Assurance, Production, and Disaster Recovery Environments and support CEFMS II in migration to new platforms in a Government or Commercial Cloud Facility.

· Oracle Database

· Multitenant for Oracle Database

· Real Application Cluster

· Partitioning

· Oracle Advance Security

· Oracle Database in Memory

· Oracle Golden Gate

· Oracle Data Integrator

· Directory Service

· WebLogic Server

· Enterprise Data Quality Profile and Audit

· Enterprise Data Quality Standardization and Match

· Oracle Analytics Server

· PVCS

· DBSIGN

· Hyperion

· SQR

· Oracle Forms

· Oracle Reports

· Oracle Access Manger

· Oracle HTTP Server

· Oracle APEX

· Oracle Real Applications Testing

4.4.4 The Contractor shall assist with configuring and tuning the CEFMS II Oracle database and application servers.

4.4.5 The Contractor shall maintain the CEFMS II Oracle databases and application in the development and test environments, including configuration modifications based on regulatory requirements, system certification and accreditation policies, upgrades, and overall design and operations of the architecture.

4.4.6 The Contractor shall provide continuous assistance for identification, correction, and configuration of all Oracle Databases to include the development and test environments, configuration modifications based on regulatory requirements, database and system certification and accreditation policies, upgrades, and overall design and operations of the architecture.

4.4.7 The Contractor shall monitor development and test database health.

4.4.8 The Contractor shall assist with Enterprise DBA to diagnose and correct database problems for all environments.

4.4.9 The Contractor shall maintain the CEFMS II Oracle software, including Security Technical Information Guidance (STIG) and Information Assurance Vulnerability Management (IAVM) compliance.

4.4.10 The Contractor shall keep the CEFMS II Oracle application and database software on current technology using upgrades and patches.

4.4.11 The Contractor shall create new databases, as needed, including training, development, and test environments.

4.4.12 The Contractor shall provide 24x7 Oracle on-call Certified DBA Support.

4.4.13 Oracle Database and Application Design and Administration.

4.5 UNIX and System Administration

4.5.1 The Contractor shall assist with the administration of the CEFMS II development and test environments, to include knowledge of UNIX, Solaris, Windows, Red Hat Linux, and Oracle SQL/PL*SQL software tuning techniques. To achieve CEFMS II user support objectives, assistance will include optimization of platform specific hardware and software tuning considerations to maximize the performance of the CEFMS II activity across the CIO/G-6 architecture.

4.5.2 The Contractor shall assist CIO/G-6 with configuring and tuning the CEFMS II Oracle database and application servers in the development and test operating environment.

4.5.3 The Contractor shall work closely with CIO/G-6 to resolve issues in the development and test environments prior to CIO/G6 making the changes on the production server issues and migrate the application and databases to supported platforms, including hardware and operating system.

4.5.4 The Contractor shall maintain, configure, and tune the CEFMS II Oracle database and application servers in the development and test environments. The Contractor shall develop and administer a development and test server backup plan.

4.5.5 The Contractor shall maintain the development and test environments, including configuration modifications based on regulatory requirements, information assurance and system certification and accreditation policies, upgrades, and overall design and operations of the architecture.

4.6 Electronic Signature Software – CAC/PKI

4.6.1 The Contractor shall assist in continued support of all electronic signature software required for the operations of CEFMS II and shall provide maintenance, troubleshooting, and new developments in both the development and testing environments. This includes, but is not limited to, the following:

· Windows-based software (i.e. WinEFT, WinChecks, WinStubs)

· Foreign Currency and European Electronic File Transfers

· Unix-based PKI electronic signature libraries

· Oracle database interface for electronic signatures

· DBSign server-based signature software

4.7 Interface Support

4.7.1 The Contractor shall assist in the continued support of the hardware and software architecture of interface support between CEFMS II and other Corps automated information systems (AIS), as well as external agency systems, including DoD and U.S. Treasury systems. CEFMS II currently has 31 system interfaces using various connection methods.

4.7.2 The Contractor shall develop processes for new interfaces in the future as new agency requirements, directives, policy, and procedures are implemented requiring interchange of data with CEFMS II. Contractor shall have skills to support XML interfaces, webservices, flat file transfers and database links.

4.8 Configuration Management

4.8.1 As part of a software assurance process, the Contractor shall maintain and follow the CEFMS II Configuration Management Plan (CMP) and establish and maintain a strict change control process.

4.8.2 The Contractor shall manage strict version control on all software source code and related artifacts either acquired or developed per the government approved CMP. The Contractor shall maintain source code in the PVCS Version Manager system.

4.8.3 The Contractor shall coordinate with Government personnel on changes to the environment through the change control process outlined in the Contractor CMP and in accordance with the Government’s configuration management guidance.

4.8.4 The Contractor shall maintain the Configuration Management software and utilities.

4.8.5 The Contractor shall assist developers in resolving source code configuration issues, apply approved changes to development environment, and coordinate with CIO/G6 to release the approved changes to production environment.

4.8.6 The Contractor shall ensure that, if necessary, code changes can be rolled back to the previous release versions.

4.9 Cybersecurity

Cybersecurity is defined as prevention of damage to, protection of, and restoration of computers, electronic communications systems, electronic communications services, wire communication, and electronic communication, including information contained therein, to ensure its availability, integrity, authentication, confidentiality, and nonrepudiation.