Cyber_Fin_Mgmt_System_Questions_Response.xlsx

XLSX spreadsheet 18 KB Posted Jul 24, 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

Attached is answers to the RFI questions.

View the file

Other files

File	Type	Posted
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
CFMS_RFI_Technical_Characteristics_Capability_Worksheet.xlsx	XLSX spreadsheet	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

RFI: HB0001-19-R0021			Cyber Financial Management System
Question #	Section	Paragraph	Question	Response
1	1		Which organizations at USCYBERCOM will the 24 eventual users of CFMS reside (e.g., FM/J8, Acquisition, other J-staff)?	J8 and J9 initially, but all other J-Dirs will need access (users).
2	2		Would you please clarify the use of Portfolio Management as it will serve the purposes of USCYBERCOM? Does the inference to Portfolio Management under other requirements mean books of business, business partners or financial books, or combinations of all business entities government and non-government?	Respondent points to section 2 of the RFI here, but portfolio management is only mentioned in the Optional Requirements in Sec 10. The "inference to Portfolio Management under other requirements", again points to Sec 10. We were specifically referencing portfolio management within the J9; no other Government or non-Government entities. Portfolio Management as used within the RFI is referring to a portfolio of programs/projects within the Command.
3	3		How many current users are in CFMS ?	Technically 0 as this system does not currently exist. 24 users referenced in question 1; this was an initial SWAG, but will likely need to increase that number.
4	4		How many domains does the solution need to cross?	Three
5	5		How many users are in each domain?	All users need access to the three systems as they on-board and gain authorized access.
6			What is the current process for handling metadata? What is the current process for handling metadata across domains?	No existing cross-domain solution; currently use multiple systems across the domains which are not integrated
7			What is the current budgeting process?	Current process in a nutshell - requirement designed and validated; seek funding via UFR if emerging requirement; via an issue paper if for the next PBR cycle; or as a program of record via the Program Objective Memorandum (POM). Programming is completed via SIPR (ABIDES); budget execution is completed via DEAMS. Requirements built on JWICS. Once the requirement has funding aligned it will be executed via DEAMS (commited-obligated-expensed).
8			What is the current data integration process?	Non-existent due to CDS
9			How big is the database for the current budgeting solution? Metadata size? Data Warehouse?	The size of the needed database is unknown at this time. There is data stored in many different systems. It is a question that could be answered after the process mapping is completed.
10			What is the current BI Solution and what is the current reporting process?	The Command currently does not have a BI solution. The current reporting process is CCaRS.
11			Would you kindly confirm if this is an entirely new effort or is there an incumbent currently providing these services? If so, would you kindly provide the incumbent contract details (contractor name, contract number)?	New effort (Comprehensive Cost and Requirement System (CCaR) is the contracted portion of the Command's current system.)
12			Is the plan to integrate execution data into the budget formulation system?	Yes
13	4.B Technical Approach Recommendations	The RFI asks for “Rough Order of Magnitude (ROM) (presented in increments of twenty-four (24) licenses/users) cost/price and schedule for initial capability execution. This should include Operations and Maintenance (O&M) support.”

How does the government define initial capability execution? Is this a proof of concept (e.g. non-production) or is this an initial baseline implementation (production system)?

Initial baseline and fully operational system: how many users initially? 24
14	10.E Security Requirements	The government states, “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.”	Will the government specify what level of safeguarding is required and will this be at the contractor’s site or government’s site? Or is the government expecting the contractor to propose safeguarding requirements?	Will reside at Government site. Especially regarding sponsor network.
15	10.e. Security Requirements	The government states, “The contractor’s management system shall prevent unauthorized disclosure of classified and sensitive unclassified information.”	Will the government please clarify if the management system is the same as the CFMS, or is this referring to a contractor’s internal system for managing its contracts and personnel?

Guy, Kerry T: Guy, Kerry T:

Refers to the contractor's internal system for safeguarding Government information during planning, production and execution.
16	Row 26	Please explain what type of data you anticipate CFMS to exchange with KMDS.	Overlap with question 24
17	Row 27	Please explain what type of data you anticipate CFMS to exchange with DRDW.	Overlap with question 24
18	Row 29	Please explain what type of data you anticipate CFMS to exchange with CYBERVAULT.	Overlap with question 24
19	Row 30	Please explain what type of data you anticipate CFMS to exchange with JIRA.	Overlap with question 24
20	Row 31	Is this an existing system currently in use? Please explain what type of data you anticipate CFMS to exchange with RMS. Rows 57 to 77 also reference RMS requirements. Is the RMS referenced in Row 31 the same system as the RMS referenced in Rows 57 to 77 of the capability spreadsheet?	In reference to the Requirements Management System used by J81. So no, not the same. Might need to rename RMS to CFMS in lines 57-77.
21	Row 33	Please explain what type of data you anticipate CFMS to exchange with e915.	Overlap with question 24
22	Row 49	Can you please clarify this statement?	Line 49 (under "Support Requirements") reads: Implementation of a cross-domain system that will ultimately contain requirements and resource data used throughout USCYBERCOM.

Point to this question was to imply the system will need to grow after initial implementation. State, "throughout USCYBERCOM" to mean that other J-Dirs will eventually be able to use the system and include their own requirements. The system will need to be accessible to a larger group of users across all of USCYBERCOM.

23	Line 19: Operational Requirements	Run tailored data reports. Provide the ability to organize budget records in a graph and/or tree structure wherever and whenever applicable.	Need more requirements for reporting, possible use OBIEE/OAC, but out of the box Hyperion planning charts and graphs are simplistic and does not offer robust interaction with charts and graphs	Kind of reports the CFMS should be able to generate: dashboard views; trend charts; presentation slides (optional); graphs
24	Interface and Migration Requirements	Hyperion Planning uses ODI or FDMEE to integrate data from external systems to create the metadata and data for budget and planning requirements. Some of the systems listed such as JIRA, CYBERVAULT, and RMS, at first, may not seem to have relevant data to integrate with Hyperion Planning.	Need more details on what type of data is required from systems listed above.	DEAMS: Defense Enterprise Accounting and Management System is a Major Automated Information System that uses commercial off-the-shelf Enterprise Resource Planning software to provide accounting and management services for the Air Force and the Defense Finance and Accounting Service (DFAS). DEAMS is intended to improve financial accountability by providing a single, standard, automated financial management system. DEAMS performs the following core accounting functions: Core Financial System Management, General Ledger Management, Funds Management, Payment Management, Receivable Management, Cost Management, Reporting.
				PD2: Procurement Desktop-Defense (PD2) provides automated strategic, streamlined contract management support for the procurement professional within a complete workflow management solution. PD2 is an integral part of the DoD's Standard Procurement System (SPS) which is integrating acquisition, logistics and financial management within one end-to-end enterprise business system.
				WAWF: is a secure, Web-based system for electronic invoicing, receipt and acceptance. WAWF allows government vendors to submit and track invoices and receipt/acceptance documents over the Web, and allows government personnel to process those invoices in a real-time, paperless environment.
				KMDS: Knowledge Management and Decision Support - Knowledge is defined as, "intangible, complex, and created by people". This Knowledge management capability involves managing processes for acquiring, producing, and integrating knowledge. It can encompass all activities than an organization might take to get its critical knowledge flowing from the people who have it, to the people who might need it, in order to address the organization's business objectives and to produce the desired business results.
				DRDW (Defense Resource Data Warehouse): Data repository for unclassified and classified information.
				ABIDES: (Air Force's Automated Budget Interactive Data Environment System) provides database administration support, program and budget formulation support for ABIDES, to include its tables, data relationships, business rules, cost models, interfaces, automated processes, change logs, system documentation, and exposure as the authoritative data source for budget data.

				CYBERVAULT: Data repository for unclassified and classified information.
				JIRA: Jira is a proprietary issue tracking product that allows bug tracking and agile project management.
				RMS (Resource Management System): Currently used on a small scale for the efficient and effective development of USCYBERCOM resources/requirements. CMFS effort will need to be much larger and incorporate resources across additional organizations.
				e915: USCYBERCOM electronic replacement for the physical (paper) staff processing form.
				CCaRS: The Comprehensive Cost and Requirement System is an enterprise program and financial management system that delivers real-time program information to government decision makers. At the core of the CCaR System are automated reports and analysis tools which allow the program and financial managers to define program requirements, formulate program budgets, forecast program execution and track the execution of program funds.
25	Line 36	Provide authorized users the ability to create, read, update, and delete detailed records about an arbitrary number of budget record entries.	Current budgeting process and architecture would help us better explain how Hyperion Planning works. What budgeting method is utilized when creating POM/BES? Zero based, incremental, activity based, or Value Proposition? What level users can perform these actions in the current process? All users? Power users? Admins? Hyperion Planning allows users to create/delete dimension members that may correspond to a BLI.	Overlap with question 7
26	Line 39	Interface with external systems of record for budget management via API, to push and pull data as required.	Need more information, epm cloud and on-prem Hyperion Planning has rest api compatibility for specific functions and both have varying degrees of functionality.	If more information is needed on the external systems themselves, please see response to question 24.
27	Line 42	Provide users with the ability to process resource certification requests (MIPRs) and staff them through the respective certification process	Is the requirement to create MIPRs inside of the budgeting tool? This requirement seems more like a procurement/budget execution requirement which can be satisfied with procurement tools which can then interface that data back into Hyperion Planning.	Yes, the system should allow for the creation of MIPRs within the system - this would be done via DEAMS (or execution system of CCSA - should the CCSA change from AF) and interface into the CCMS.
28	Support Requirements	Technical configuration, administration and maintenance functions necessary to integrate with the existing USCYBERCOM Enterprise Cross Domain Solution.	Need a high level architecture of their current cross domain solution so that we can better describe Oracle’s proposed solution.	Overlap with question 6
29	Lin 92	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.	o Hyperion Planning and PBCS/EPBCS (cloud solutions) support planning and budgeting activities for projects and programs but it is not a PPM tool, would this possibly be integrated with a separate PPM tool the government is currently using? Line 95 seems to reference an existing portfolio management tool.	There is no current tool that does budgeting and planning. There are sytems that do budgeting and/or execution (DEAMS, CCaRS), and systems that do planning (WAWF, DRDW, ABIDES), but no system that does both.
30	Line 93	The system shall also provide project and program management capabilities that address performance management, manpower, and other critical aspects to successful execution.	Similar to the question for line 92, is there a desire to be able to conduct what-if analysis on these metrics due to integration with a separate portfolio management tool?	Yes, would like to be able to conduct "what-if" analyses.

File details come from the government source that posted it.