Attachment 1 - Draft Performance Work Statement (PWS).pdf

UNISON ACQUISITION MAINTENANCE AND SYSTEM

SUPPORT SERVICES

PERFORMANCE WORK STATEMENT

AUGUST 30, 2024

1.0 BACKGROUND:

The Office of Naval Research (ONR) is an Echelon I headquarter organization within the Office of the Secretary of the Navy (SECNAV). Congress established ONR to command and manage all Science and Technology (S&T) – defined as basic research (budget category 6.1), applied research (6.2), and advanced technology development (6.3) – for the Department of the Navy (DON) and to foster the transition from science and technology to higher levels of research, development, test, and evaluation. ONR is a pioneer in the public support of science and technology research that benefits both the naval services and the nation. From investments in the earliest computers to spearheading seminal research in deep-sea exploration to cultivating groundbreaking efforts in solid-state electronics and countless other innovations.

The Chief of Naval Research (CNR) commands ONR and is responsible for encouraging, promoting, planning, initiating, coordinating, and conducting naval research. ONR awards over 80% of ONR-sponsored S&T funding to external performers in academia, industry, and the Naval Research Enterprise (NRE). Work funding is procurement (contracts) or assistance (grants and agreements) awards.

The UNISON ACQUISITION system allows procurement personnel to conduct acquisition activities for ONR. The UNISON ACQUISITION system manages the solicitation and contract administration functions of ONR, transforming a purchase request or need into a procurement action or contract award. UNISON ACQUISITION includes external interfaces to that supports the entire contracting lifecycle. UNISON ACQUISITION maintains technical or procedural interfaces with the other DOD and Federal Systems to support the posting of items related to contracting activities. UNISON ACQUISITION is a COTS product from Unison Global Inc that executes on a Microsoft Windows Platform using the Oracle DBMS on a Linux RHEL platform. Access to the application is PKI-enabled using Microsoft IIS.

ONR's operations heavily rely on the UNISON ACQUISITION system, making its maintenance and support crucial. This support involves not only keeping the system operational but also facilitating its decommissioning for historical purposes and records retention. The following sections will outline the specific goals and objectives of these support services, which aim to ensure the stability of ONR's current computing environment and prepare for the system's removal from the operational network.

2.0 PROJECT:

2.1 Project Location/Team

The project location is ONR Headquarters, 875 North Randolph Street, Arlington, Virginia 22203. The Contractor shall work with an integrated team consisting of ONR personnel from the Contracts, Grants, and Acquisition Department (Code 02), Office of the Command Information Office (Code 53), and other Navy representatives that will support the maintenance and future decommission.

2.2 Project Functional and Technical Requirements

As the designated expert, the Contractor is responsible for maintaining the latest version of the UNISON ACQUISITION system and staying abreast of all future software versions.

Their role also includes providing expert advice on configuration decisions, issue resolution, and operations and maintenance support to ensure compliance with all regulatory mandates. The Contractor is to provide a Quality Control Plan that will address how they manage quality control aspects and resolution of any issues identified.

3.0 SCOPE:

This task consists of providing operations and maintenance services for the UNISON ACQUISITION system at ONR.

3.1 Software Maintenance

The Contractor shall provide continued maintenance and support of ONR's existing software application and its interfaces to ensure that the system performs per the specifications and functionality detailed in the Commercial-Off-The-Shelf (COTS) documentation provided. The updates and maintenance shall include new software COTS versions developed and certified by the Contractor as ready for release (e.g., thoroughly tested by the Contractor) in the ONR cloud environment. Further the Contractor will support all decommission activities to preserve the system historical information for records retention.

Maintaining interface integrity is a top priority for the Contractor. Any updates to the software versions will be carefully coordinated with the COR and Code 53 (ONR Team), and the Contractor will document any changes to its software that could affect existing or future integrations. Interfaces with the Procurement Integrated Enterprise Environment (PIEE) suite and Integrated Award Environment (IAE) suite of applications and existing ONR additional features will remain operational, ensuring the system's functionality is preserved. The system will allow ingestion or interfacing of data from any ONR-designated system into UNISON ACQUISITION using a standard COTS Application Programming Interface (API).

The Contractor shall update and maintain the software with the underlying acquisition regulations, including the Federal Acquisition Regulations (FAR) and the DoD FAR Supplement (DFARS). For all software updates, the Contractor shall provide the required documentation to support configuration changes, including creating the initial ONR Request for Change (RFC) form. The configuration management documentation will consist of (at a minimum) the software release notes, installation procedures, and any other documentation identifying impacts to the network, operating system, database, or application.

3.2 System Testing Support

As part of their responsibilities, the Contractor is required to support the installation of software updates in the ONR development environment and actively participate in the system testing of the application. Should any system issues arise during testing, the Contractor is expected to lead the problem definition effort and be prepared to conduct any required remedial action for the UNISON ACQUISITION software.

If system issues arise during a test, the Contractor shall lead the problem definition effort and be prepared to conduct any required remedial action for the UNISON ACQUISITION software.

3.3 DBA Support

The Contractor is committed to providing comprehensive DBA Support. A dedicated Database Administrator (DBA) will be responsible for installing software hotfixes, patches, and new versions of the software and troubleshooting technical issues on-site or virtual. Planned downtime for maintenance or software upgrades to the production instance of UNISON ACQUISITION will be scheduled during regular business hours whenever possible. If the on-site support personnel cannot resolve an issue within the regular on-site visit hours, the problem will be resolved as quickly as possible. DBA Support is provided on a bi-weekly basis on Thursdays of each month, ensuring the system's maintenance is a continuous process.

The DBA will be required to coordinate any changes on the network with Code 53. DBA tasks include:

UNISON ACQUISITION Installs and Upgrades o Installs o Major releases, service packs, and hotfixes

Regulatory updates o Federal Acquisition Regulations (FAR) and Defense Federal

Acquisition Regulation Supplement (DFARS) o Product Service Codes (PSC) o North American Industry Classification System (NAICS) o Forms

Custom Clause Databases Oracle database tuning o Generate Automatic Workload Repository (AWR) report and review the report o Make System Global Area (SGA) sizing modifications based on usage and load testing o Tune Oracle initialization parameters based on customer feedback and usage o Create appropriate indexes to increase performance based on specific customer usage o Recommend steps to minimize Input/Output (I/O) bottlenecks o Implement table partitioning if required

Database and Application Server Event logs review o Review Windows Event logs and take appropriate actions o Review the UNISON ACQUISITION application log and take necessary measures o Review database log files (e.g., Alert log file, Listener log file) and take appropriate steps o Review database audit log

Troubleshooting UNISON ACQUISITION and database issues o Run database tracing to identify issues o Analyze and explain plans and make appropriate recommendations o Proactively implement database changes based on in-house recommendations o Provide support and interact with development to fix issues

Maintenance Tasks o Analyze backup jobs o Run jobs to clean UNISON ACQUISITION temporary tables as required o Analyze dbms_jobs used for ADHOC and fix any failures o Analyze database growth and add space to tablespaces when required

Before completion of an on-site visit, the DBA shall provide ONR with a summary of all actions taken, any open issues remaining, and a plan to address any outstanding issues

(CDRL A002).

INFORMATION ASSURANCE CONTRACTOR TRAINING AND CERTIFICATION.

All Contractor personnel performing work under the contract must have proper and current Information Assurance Workforce (IAWF) certifications before the commencement of the award and for the duration of the contract.

The Contractor shall notify the COR 90 days before the expiration of any IAWF certifications and provide the renewal status.

DoD-approved information assurance workforce certifications appropriate for each category and level as listed in the current version of DoD 8570.01-M.

Information related to Information Assurance (IA) Workforce Qualification Requirements resides at https://public.cyber.mil/cwmp/.

3.4 Audit Preparation

The Contractor shall provide support for Audit Readiness functions, including responding to inquiries about the required documentation and coordinating with the audit team. The audit requirements are on the following FISCAM/FIAR websites:

http://comptroller.defense.gov/fiar.aspx and http://www.gao.gov/special.pubs/fiscam.html.

3.5 Information Assurance (IA) Support

The Contractor shall assist ONR with information assurance compliance and accreditations for UNISON ACQUISITION, including maintaining the documentation required to maintain an active Authority to Operate (ATO) in accordance with Navy DAA.

3.6 Customer Support

The Contractor shall provide avenues for immediate customer support to resolve software issues and answer related questions in support of system usage. Additionally, provide resolution to tickets in less than a business day, unless otherwise escalated to another Tier for completion.

4.0 DELIVERABLE:

4.1 Monthly Reports

The Contractor shall provide monthly status reports to the COR (Exhibit A, CDRL Data Item No. A001). This report's monthly technical progress is acceptable in Contractor format (subject to COR approval). At a minimum, the report shall contain the following information:

1. Administrative Information Contract Number Contractor Name, PM name, and contact information Date of Award Period of Performance Dates of Reporting Period

2. O&M Support Summary Metrics on system downtime and performance Risks and issues that may influence performance. Resolution if applicable Any other business that may affect performance (e.g., personnel changes, staffing gains, losses with associated performance impacts, training).

Provide reference numbers and short descriptions (e.g., patch change) for any changes, software releases, updates, patches, hotfixes, and DBA maintenance summary.