PWS - OPNAV N2N6 RAPS.pdf

PDF 199 KB Posted

Attached to
Resource Allocation Planning System (RAPS) Financial Database Management Support Services
Solicitation number
N0018924R662
Issued by

About this file

This document is a Performance Work Statement (PWS) for the Resource Allocation Planning System (RAPS) Financial Database Management Support Services contract. The objective is to obtain Information Technology (IT) services to assist the Deputy Chief of Naval Operations for Information Warfare (OPNAV N2N6) with planning, programming, funding, and monitoring programs, systems, and services. Key tasks include maintaining and supporting the RAPS financial database, developing and customizing RAPS accounting and financial queries and reports, providing user administration and database access, and assisting with the N2N6 Program Objective Memorandum (POM) submission process. The contract requires specific labor categories including Senior Systems Engineer, Database Engineer, and Senior Programmer Analyst, with defined minimum qualifications. The period of performance is four months from September 2024 to January 2025, and all work will be performed on-site at OPNAV N2N6 in the Pentagon, except for the Senior Programmer Analyst who can work remotely. No travel is required.

View the file

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Performance Work Statement (PWS) The Deputy Chief of Naval Operations for Information Warfare (OPNAV N2N6)

Resource Allocation Planning System (RAPS)

1.0 INTRODUCTION

The Deputy Chief of Naval Operations (OPNAV N2N6) for Information Warfare optimizes information warfare investments through centralized coordination of Navy warfighting and warfighting support analysis/assessments, Navy network capability development and integration, Joint and Navy requirements development, and resource programming. This is accomplished by delivering affordable, relevant capabilities to the Fleet in a timely manner.

N2N6 acts as principal advisor to Chief of Naval Operations for communications and network matters, Cyber, Battlespace Awareness, Electronic Warfare, and Assured Command and Control; and serves as Navy's top level advocate for information management/information technology resources throughout the Navy and the Joint environment.

2.0 BACKGROUND

The Resource Allocation Planning System (RAPS) provides a web-enabled, Secure Sockets Layer (SSL) and Public Key Infrastructure (PKI) protected, centralized, interactive, and searchable financial database data warehousing system that is integrated with other internal and external government financial systems. RAPS is a budget/financial allocation tracking system that provides and maintains planning and programming data, status of funds allocations, transaction histories and descriptions, and data extracts from the Program Budget Information System (PBIS). It includes the capability to keep an audit trail of data input and the identification of individuals responsible for data input into the system. It also provides administrative and financial management system data and provides the N2N6 Program Objective Memorandum (POM) submission load into PBIS each year. RAPS is the mission critical database and web-based application utilized by N2N6 to develop, staff and deliver a 100% accurate, fully balanced POM submission to the Chief of Naval Operations (CNO) (via PBIS) each year in accordance with PBIS database standards, the DoD Financial Management Regulation (FMR), and N80 and FMB guidance.

3.0 SCOPE

The objective of this task order is to obtain Information Technology (IT) services to assist N2N6 with carrying out duties and responsibilities to plan, program, fund, and monitor the planning programming, and execution of programs, systems, and services to their customers.

N2N6 requires assistance in the following RAPS Financial Database Management areas:

• Maintain and support the RAPS financial database usage and access to N2N6 staff members.

• Maintain, develop and customize RAPS accounting and financial queries, reports and data within PBIS database standards, structures and protocols and compliant with OPNAV N8 guidance and directives and the DoD Financial Management Regulation (FMR).

• Create ad-hoc accounting and financial queries and reports within the time constraints to assist the N2N6 financial staff in meeting all existing and emergent organizational requirements without new system development.

• Develop reports and queries to display and reconcile programming / budget and execution data for OPNAV N2N6 staff.

• Display archived and historical information within specified time constraints and ensure continuity of financial processes and information over the Future Years Defense Plan and associated out years, as needed by the N2N6 staff and RAPS database users.

• Develop Oracle database objects and reports for a wide range of customers in DoD. Serve as a data transfer conduit between other DoD financial systems as required, using the most efficient database to database and / or file connections as possible. Update and synchronize RAPS data within 24 hours of receipt of external database files.

• Establish and maintain secure connections to external database servers as needed. Requires effective working relationships with network administration personnel and IT administrators throughout OPNAV to rapidly respond to requirements for new connections to support emerging and short-fused requirements.

• Provide user administration and database access in accordance with all DoD security mandates.

4.0 TASKS

To accomplish this objective N2N6 requires the following task support:

• 4.1 Senior Systems Engineer tasks:

o Create and administer RAPS user accounts. Manage and assign database privileges, as appropriate, as determined by each user’s role in the community. Ensure accounts are activated and disabled in accordance with DoD security mandates.

o Create Oracle database objects necessary to incorporate the Navy and N2N6 Information Warfare business logic and emergent organizational requirements into RAPS forms and reports to streamline data processing and reduce data entry errors. Write data validation routines to ensure 100% veracity of the N2N6 financial data and data migration modules to seamlessly transfer data to and from various Navy financial databases.

o Provide timely and accurate ad hoc data extractions and reports to senior N2N6 leadership.

Provide technical support and data analysis to N2N6 staff. Develop training materials and conduct training as necessary. Coordinate program level data synchronization between N2N6 and Budget Submitting Offices (BSOs) to ensure accuracy and consistency of the financial data.

o Monitor system performance to ensure maximum availability and performance. Rapidly incorporate emergent N2N6 reporting requirements into database structure and reports.

o Archive legacy data to maintain accurate corporate financial historical auditing of programs by fiscal cycle.

o Assist N2N6 staff with all phases of the N2N6 POM development and submission process via data input, budget calculations, “what-if” drills, and the formulation of required budget exhibit documents. Ensure that any modifications to the PBIS database structure (physical or virtual) that affect the submission are incorporated in the RAPS database structure. Provide technical assistance, accuracy assurance, error resolution, and coordination between N2N6 and N80 on all matters that involve the electronic transfer of funding between Navy IT systems as directed by OPNAV N80 and the Navy Office of Financial Management and Budget (FMB) guidance and directives. Assist N2N6 POM development by writing and maintaining N2N6 POM submission, administration, and reporting modules. Package the N2N6 POM data, in compliance with PBIS database standards and in the native PBIS data format, to successfully transfer to the N80 PBIS database while meeting Navy fiscal guidance and with 100% accuracy and within all assigned deadlines.

o Write and maintain automated Program Dualie generator and the automated POM Issue Dualie generator. Maintain POM submission history track by archiving all submission data and documents for future referral.

• 4.2 Database Planner/Designer tasks o Create and administer RAPS user accounts. Manage and assign database privileges, as appropriate, determined by each user’s role in the community. Ensure accounts are activated and disabled in accordance with DoD security mandates.

o Create any Oracle database objects necessary to incorporate Navy and N2N6 Information Warfare business logic and emergent organizational requirements into RAPS forms and reports that will streamline data processing and reduce data entry errors by Navy users. Develop and implement backup strategies. Establish and maintain secure connections to external Navy database systems as required. Support the setup and implementation of data warehousing and archiving routines.

Write data validation routines to ensure 100% veracity of the N2N6 financial data and data migration modules to seamlessly transfer data to and from various Navy financial databases.

o Provide timely and accurate ad hoc data extractions and reports to senior N2N6 leadership.

Provide technical support and data analysis to N2N6 staff. Develop training materials as necessary.

o Coordinate program level data synchronization between N2N6, Budget Submitting Offices (BSOs), OPNAV N80 and FMB to ensure accuracy and consistency of the financial data as reflected in Navy budget exhibits, such as, P-Sheets and R-Docs. Monitor system performance to ensure maximum availability and responsiveness of the system. Rapidly incorporate emergent N2N6 and PBIS reporting requirements and data elements into the RAPS into database structure and reports.

o Archive legacy data to maintain accurate corporate financial historical auditing of programs by fiscal cycle.

o Assist N2N6 staff with all phases of the N2N6 POM development and submission process via data input, budget calculations, “what-if” drills, and the formulation of required budget exhibit documents. Ensure that any modifications to the PBIS database structure (physical or virtual) that affect the submission are incorporated in the RAPS database structure. Provide technical assistance, accuracy assurance, error resolution, and coordination between N2N6 and N80 on all matters that involve the electronic transfer of funding between Navy IT systems as directed by OPNAV N80 and the Navy Office of Financial Management and Budget (FMB) guidance and directives. Assist N2N6 POM development by writing and maintaining N2N6 POM submission, administration, and reporting modules. Package the N2N6 POM data, in compliance with PBIS database standards and in the native PBIS data format, to successfully transfer to the N80 PBIS database while meeting Navy fiscal guidance and with 100% accuracy and within all assigned deadlines.

o Write and maintain automated Program Dualie generator and the automated POM Issue Dualie generator. Maintain POM submission history track by archiving all submission data and documents for future referral.

• 4.3 Senior Programmer Analyst tasks o Rapidly develop front-end web interface and financial reports used by N2N6 personnel based upon OPNAV requirements. Current RAPS application production environment includes pages and reports written in HTML, XML, ColdFusion, PL/SQL, Oracle Portal, and Oracle Reports.

Ensure RAPS is compliant with NMCI standards and DoD Information Assurance Vulnerability Alerts (IAVAs) as necessary to maintain applications NMCI Authority to Operate (ATO) and in accordance PBIS database standards, structures and protocols and compliant with OPNAV N8 guidance and directives and the DoD Financial Management Regulation (FMR).

o Ensure the front end connectivity to the back-end Oracle database is maintained. Include automatic filtering of data based upon assigned user and group permissions to ensure that each user can read and update only those records to which they have explicitly been grated rights to access.

o Rapidly incorporate emergent N2N6 design changes, reporting requirements into web interface, reporting tools, and download interfaces.

o Manage secure SSL encrypted, PKI authorization and CAC log-in capability. Document remedies taken for DITSCAP (SSAA) application procedures. Follow all current security protocols, STIG requirements, business rules, and best practices when developing, deploying, modifying, administering, and providing access to RAPS. Meet with supervisory personnel, Configuration Control Boards (CCB), and other ad hoc groups as necessary.

o Assist N2N6 POM development by using ColdFusion to create and update web based forms and reports used within the N2N6 POM submission and reporting module, the automated web Program Dualie generator, the automated web POM Issue Dualie generator, and the web based POM Build Issue record and funding record data entry system in accordance PBIS database standards, structures and protocols and compliant with OPNAV N8 programming guidance and directives and the DoD Financial Management Regulation (FMR).

5.0 LABOR CATEGORY MINIMUM QUALIFICATIONS

Senior Systems Engineer

General Experience: Minimum ten (10) years of technical and professional experience that applies to systems engineering techniques, concepts, and methods. Must have a working knowledge of the DoD Financial Management Regulations (FMR) along with technical experience working with DoD financial programming and budgeting data structures and systems. Must have an extensive knowledge and understanding of the Navy’s Planning, Programming, Budget, and Execution (PPBE) cycle and strong knowledge of the PBIS database environment.

Functional Responsibility: Acts as a lead in defining and executing systems engineering activities within a project.

These activities may consist of systems planning, performance management, capacity planning, testing and validation, benchmarking, information engineering, and development and staffing of a systems engineering management plan.

Minimum Education: Bachelor's Degree in Systems Engineering or a Related Field.

Database Engineer

General Experience: Minimum six (6) years of relational database design and development experience that applies to complex software systems. Must have a strong knowledge of a variety of database systems – primarily Oracle 11g. Must have a working knowledge of the DoD Financial Management Regulations (FMR) along with the technical experience working with DoD financial programming and budgeting data structures and systems. Must have an extensive knowledge and understanding of the Navy’s Planning, Programming, Budget, and Execution (PPBE) cycle and strong knowledge of the PBIS database environment.

Functional Responsibility: Works independently, with management review of end results. Has prime accountability for the design, development, maintenance and operating efficiency of a major database system.

Minimum Education: Bachelor's Degree in Computer Science or a Related Field.

Senior Programmer Analyst

General Experience: Six (6) years of programming experience which applies to complex software systems with at least two (2) years as a team leader. Must be competent in a variety of current computer languages and skilled at supervising a programming team. Must have a working knowledge of the DoD Financial Management Regulations and technical experience working with DoD financial programming and budgeting data structures and systems.

Functional Responsibility: Works independently, with management review of end results. Has prime accountability for the maintenance and operating efficiency of a major subsystem, such as database management systems, etc.

Minimum Education: Bachelor's Degree in Computer Science or a Related Field

6.0 APPLICABLE DIRECTIVES AND DOCUMENTS

The Contractor shall adhere to the following documentation:

Document Type No./Version Title Date

U.S. Code 2002 Federal Information Security Management Act (FISMA), TITLE X of The Homeland Security Act of 2002

27 Nov 02

U.S. Code 1987 Public Law 100-235, Computer Security Act of

8 Jan 88

Document Type No./Version Title Date OMB Guidance A-130 OMB Circular A-130, Management of Federal

Information Resources 8 Feb 96

DoD Instruction 8500.01 Cybersecurity 14 Mar 14 DoD Instruction 8510.01 Risk Management Framework (RMF) for DoD

Information Technology (IT) 28 Jul 2017

DoD Manual 8510.1 DITSCAP Application Manual July 2002 SECNAV Instruction 5239.3A DoN Information System Security (INFOSEC)

Program 20 Dec 04

5721.1 Electronic and Information Technology (EIT)

Section 508 Accessibility Standards

21 Dec 00

OPNAV Instruction 5239.1B Navy Information Assurance Program 9 Nov 99 Navy-Marine Corps Unclassified Trusted Network

Protection (UTNProtect) Policy 31 Oct 02

SSC-PAC Policy 1.40 Network Security Policy 1 May 04 DoD Instruction 8520.02 Public Key Infrastructure (PKI) and Public Key

(PK) Enabling 24 May 11

NSTISSP Policy 11 National Information Assurance Acquisition Policy Jan 2000 NSTISSIP Policy 4009 National Information Assurance Glossary, revised May 03 DoD Instruction 7000.14-R Financial Management Regulation (FMR), Volumes

2A and 2B

OMB Guidance A-11 Preparation, Submission, and Execution of the Budget

Business Management Modernization Program Memoranda, Instructions, and Products

7.0 DELIVERABLES

The Contractor shall provide the following deliverables within the timeframe specified:

Products Due Date Monthly Status Report Due the 15th of each month RAPS Technical Change and Tasking Report As requested, or required

8.0 SECURITY

The nature of this task requires access to classified, for official use only, and business sensitive information. The work performed by the contractor will include access to classified and unclassified data, information, and spaces.

The contractor will be required to attend meetings classified at SECRET, CONFIDENTIAL, and unclassified levels.

All workers must obtain and maintain SECRET level clearances and be United States citizens.

All workers must sign a Certificate of Non-Disclosure Agreement not to divulge Defense financial information to anyone without specific authorization from the Contracting Officer or duly appointed representative.

9.0 COMMON ACCESS CARDS

The Government will provide Common Access Cards (CAC). The contractor is responsible for notifying the government when an employee who has been issued a CAC leaves the company or transfers to another program/project. In the case of an employee who no longer works for the company, the company must collect the CAC and turn it over to the government within two (2) working days of the employee’s departure.

10.0 CONTRACTING OFFICER’S REPRESENTATIVE (COR)

TBD

11.0 TRAVEL

There is no travel required for the completion of the deliverables for this task order.

12.0 PLACE OF PERFORMANCE

One Senior Systems Engineer and one Database Engineer will perform all duties at OPNAV N2N6 in the Pentagon.

N2N6 will provide desk area, computer equipment, and NMCI connectivity. One Senior Programmer Analyst will perform application development work remotely. N2N6 can provide an NMCI connected laptop to the Senior Programmer Analyst upon approval of the COTR and the N2N6 Staff Operations Department.

13.0 PERIOD OF PERFORMANCE

The four month based period of performance begins on 19 September 2024 through 18 January 2025.

File details come from the government source that posted it. Updated .