CFMS_RFI_Technical_Characteristics_Capability_Worksheet.xlsx

XLSX spreadsheet 18 KB Posted Jun 18, 2019

Attached to: Financial Management System
Solicitation number: HB0001-19-R-0021
Issued by: Department of Defense Cyber Command

About this file

From the source

Technical Characteristics Capability Summary Worksheet

View the file

Other files

File	Type	Posted
Cyber_Fin_Mgmt_System_Questions_Response.xlsx	XLSX spreadsheet	Jul 24, 2019
CFMS_RFI_GOLD_v2.0_Amendment.pdf	PDF	Jul 12, 2019
CFMS_RFI_GOLD_v1.0.docx	DOCX document	Jun 18, 2019
CFMS_Interface_Requirements_Diagram.pdf	PDF	Jun 18, 2019

On GovTribe

Work with this file

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

Try for free Login

Text version

The file's text, extracted by GovTribe without its formatting.

Sheet1

	Technical Characteristics Capability Sheet					May-19
	The following requirements for the Cyber Financial Management System (CFMS) are listed with more detail in the RFI.
•	Insert the name of the solution.
•	Indicate if your solution is an existing COTS/GOTS solution, an existing COTS/GOTS with additional modifications, or if a developmental solution is necessary, by placing an X in the appropriate column.
o	Please describe the degree of needed modifications to meet the Government requirement.
•	Place an X beside each requirement that your proposed COTS/GOTS solution can provide.
•	Provide a separate Capability Sheet for each solution.
	Requirement	COTS/GOTS Solution	Existing COTS/GOTS w/ Modification	Describe needed modifications	Developmental Solution	Prior Experience

(Customer name)

Name of COTS/GOTS Solution

Process Mapping and Workflow Identification

Conduct process mapping and workflow identification for processes relevant to the proposed system (As described in Appendix A).

Documented process maps and detailed Command workflows. The mapping shall identify inputs and outputs within the processes. The workflow identification shall include the “If, then” logic associated with the successful routing of requests

Identification of artifacts, handoffs, overlaps, and efficiencies, while also eliminating outdated processes.

Recommendation of standardized information fields to be used within the process which will create uniformity across multiple systems, and increase ease of use.

Technical Characteristics

Operational Requirements

A mechanism that will automate and facilitate the coordination of budgetary and financial management data across multiple domains utilizing the existing USCYBERCOM Enterprise Cross Domain Solution.

House all required functions and approvals within one system; it will work from a single form with a single workflow to process requests, which will reduce duplication of effort and potential confusion.

Accessible to users with the appropriate permissions, who will each have a unique account.

Users across the Command with specified permissions shall be able to:

Query a common database for current and planned requirements

Submit requests for new requirements and resources (both internal and external to the J8) for approval

Display status logs, with timestamps, of current notifications and approval requests

Run tailored data reports. Provide the ability to organize budget records in a graph and/or tree structure wherever and whenever applicable.

Interface and Migration Requirements - The proposed CFMS shall:

Be able to interface with multiple Air Force Accounting Systems, databases and other systems across multiple domains. Integration of data to and from the following currently supported systems, at a minimum:

Defense Enterprise Accounting and Management System (DEAMS)

DFAS (Defense Finance and Accounting Services)

Procurement Desktop-Defense (PD2)

Wide Area Work Flow (WAWF)

Knowledge Management and Decision Support (KMDS)

Defense Resource Data Warehouse (DRDW)

ABIDES

CYBERVAULT

JIRA

Requirements Management System (RMS)

Include migration of function and integration of data to and from the following currently supported systems, at a minimum:

e915

Comprehensive Cost and Requirement System (CCaRS)

Resource Management Data Requirements - The proposed solution shall:

Provide authorized users the ability to create, read, update, and delete detailed records about an arbitrary number of budget record entries.

Provide Command-specific standardized fields and attributes of a budget record.

Provide users the ability to associate budget line items with the projects, programs, tasks and requirements they are funding.

Interface with external systems of record for budget management via API, to push and pull data as required.

Provide budget record data as validated field/attribute to any of the other system modules that require the ability to reference the information.

Provide users with (Command approved) pre-defined forms/templates to support budget planning and funds execution (e.g., new record entry, funding acquisition form, MIPR, etc.).

Provide users with the ability to process resource certification requests (MIPRs) and staff them through the respective certification process.

Functional Process Requirements - The proposed solution shall:

List all of the budget records in a concise, filterable list view.

Allow authorized users to create, read, update and delete workflows related to budget records and their selectors.

Allow authorized users to create, read, update and delete a variety of dashboards based on budget records.

Support Requirements - The Contractor shall:

Technical configuration, administration and maintenance functions necessary to integrate with the existing USCYBERCOM Enterprise Cross Domain Solution.

Implementation of a cross-domain system that will ultimately contain requirements and resource data used throughout USCYBERCOM.

Application support (e.g., software maintenance) during the development of the Program Objective Memorandum (POM), and configuration changes when necessary.

Prepare end user training materials to support ER2MS users in transitioning to the system.

Build and document integration steps from the existing systems onto the sponsor’s internal system, NIPRNet, and SIPRNet.

Incorporate new technology into an integrated environment containing all historical financial data

Provide CFMS support during its deployment; once it is deployed and operational, the contractor shall provide operations, maintenance, system administration, and Help Desk support for the CFMS and its associated infrastructure

System Features

User Accounts, Permissions, and Responsibilities

The solution shall support the following classes of users:

RMS Administrator

RMS Approver

Regular User

Data Management

The RMS shall be configured to ensure that the following characteristics are maintained:

Consistency: The data shall be consistent across the database – contradictory records shall be flagged and brought to the owning user’s attention.

Up to date: The data shall include the most up to date information. The RMS database shall identify incomplete funding records that have been dormant for a specified amount of time, and shall be flagged and brought to the owning user’s attention for action.

Completeness: Criteria for data completeness shall be verified with the Government and enforced via data management rules.

Security: shall be secure, in the sense that unauthorized access shall be prevented, and also in the sense that the data shall be survivable and recoverable in the case of system and/or software failures.

Integrity: Provisions shall be made to protect the integrity of RMS data – data shall not be changed except by authorized users, with audit logs.

Data retention: retain historical resource data in accordance with DoD and Command records management policies.

Data Search

The RMS shall provide a search capability to all users to conduct data inquiries over the CFMS database. Searches shall be tailorable by combinations of relevant attributes, that include but are not limited to:

Owning organization

Requirement/contract name

Record IDs

Data tags

Fiscal year

Funding type/source

Other search parameters as negotiated

Data Sharing and Reporting

Data sharing functions that shall be included, not are not limited to:

Stakeholder Data Notifications: When certain types of data or information are entered (specific types to be determined by user groups during development), a notification or alert message shall be generated and sent to specified recipients (nominally the POC as listed within a specified data structure). (e.g., approvals, updates)

Collaboration Messages: Messages and/or modified Coordination Requests between the users.

Data Downloads/Transfers: Users (particularly Administrators) shall have the ability to transfer data to other systems.

Security Requirements

In an architecture to be defined, the RMS shall handle unclassified and classified data across multiple domains.

The contractor shall ensure requirements for safeguarding classified information and classified materials, for obtaining and verifying personnel security clearances, for controlling access to restricted information and Government property, and for the security of automated and non-automated management information.

Optional Requirements

Requirements Management

The solution shall be capable of tracking and reporting on requirements from needs identification through solution identification, resourcing, execution and deployment.

The enterprise solution shall be adaptable to the USCYBERCOM requirements workflow and approval process.

The system shall provide configurable reporting capability and shall be capable of migrating or integrating data and function from CFMS and requirements management.

Portfolio Management

The solution shall provide project and program (e.g., a portfolio of projects) management capabilities to track, aggregate, and integrate cost, schedule, performance, and risk.

The system shall also provide project and program management capabilities that address performance management, manpower, and other critical aspects to successful execution.

The system shall provide configurable reporting capability based on these various aspects of project and program management.

The system shall provide configurable reporting capability and shall be capable of migrating or integrating data and function from CFMS and portfolio management.

In the event that Army, rather than Air Force, becomes the Executive Agent for USCYBERCOM, the CFMS shall be able to interface with Army Accounting Systems, databases and other systems across multiple domain. What Army and accounting systems is your solution currently compatible with?

File details come from the government source that posted it.