EFiMS_Vendor_Question_Responses_-_FBO_Posting_-_7.2.19-v2.pdf

Vendor Questions & Responses EFiMS- Enterprise Financial Management Systems RFI 70RTAC18RFI000004EFiMS

# Question/Reference DHS Response 4 SOW - 10.1.2 Complex Event Planning

“The system shall have the capability to perform complex event planning”

Was this requirement intended to be for "complex event processing" instead of "complex event planning"? Also, elaboration on the desired capabilities or use cases supported would be helpful.

Yes, this should be complex event processing. The following has been added to the SOW, "The system shall have the capability to perform complex event processing. This includes activities associated with combining information from multiple data sources that analyze cause-and-effect relationships to infer events or patterns that suggest more complicated circumstances with integrated financial, asset and procurement data (e.g. identifying risks/opportunities, discovering trends, etc.)"

5 Is EFiMS intended to replace or supplement the current TRIO program? The “Trio” as it is known today, consists of an enterprise resource planning (ERP) software solution (financial, procurement, and asset management) in support of the following elements of the U.S. Department of Homeland Security: Transportation Security Administration (TSA), Coast Guard (CG), and the Domestic Nuclear Detection Office (which is now known as the Countering Weapons of Mass Destruction Office). The “Trio” runs on the Oracle platform.

The “Trio” solution was migrated by DHS from the U.S. Department of the Interior. The underlying software is Oracle. The “Trio” implementation is supported by IBM, which was awarded a System Deployment Agent (SDA) task order under the Department’s Enterprise Acquisition Gateway for Leading Solutions (EAGLE) II contract in 2017. The SDA task order ends in 2021. The “Trio” in its present form may collectively or on an individual component basis leverage the EFiMS software contract in the future. Or, the “Trio” may continue with the “Trio” solution outside of the EFIMS software multi-award vehicle.

The Enterprise Financial Management Software (EFiMS) requirement is being solicited to satisfy the requirements outlined in the EFiMS Software statement of work. The information provided above in response to this question is not intended to indicate a preference by the government for the “Trio” solution, or the underlying software under this procurement.

6 Does DHS envision 1 contract to configure, implement and support EFiMS? Or does DHS envision 1 contract to support EFiMS (This one) and a separate contract to configure and implement the EFiMS Solution?

The companion contract to EFiMS software is Enterprise Financial System Integration (EFSI). DHS has updated Section 1 of the SOW to address this question.

7 Does DHS intend to provide components with the ability to select differing solutions?

This would seem to make it a challenge to achieve some of DHS overarching goals.

Yes, Components will conduct a fair opportunity competition and selection under the EFiMS software multi-award vehicle when they need to modernize.

9 Is DHS going to provide a definition of the requirements for level 1 and 2 support? DHS has removed prior references to level 3 support from the SOW. The updated SOW includes a definition for the Tier 4 OEM vendor support services requirements.

# Question/Reference DHS Response 11 SOW - 7.1.2.The second paragraph of Sec on 4 indicates that a selec on of a so ware product to the IDIQ, only enables a vendor to further compete for Task Orders at the HQ or component level of DHS. This procurement structure could result in multiple protests to get on the IDIQ, with the potential for additional protests at the Task Order level. This could make it difficult for DHS to reach its modernization objective of 2025.

We suggest that DHS use an “analysis of alternatives” method for components to select their preferred software off of the IDIQ; then be able to place sole source task orders for that software.

Enterprise Financial Management Systems software (EFiMS SW) is a multi-award vehicle designed to support the DHS Chief Financial Officer (CFO) Joint Program Management Office (JPMO) Financial Systems Modernization Program. The vehicle supports all DHS Components. EFiMS will be leveraged by Components to modernize/ replace their financial, procurement, and asset management system(s) using a fair opportunity competition and selection methodology when the DHS Directorate and/or Component determines the need to modernize. A separate Enterprise Financial System Integration (EFSI) multi-award vehicle will be used to configure and implement the EFiMS software solution. System integration /configuration/implementation is not part of this multi-award vehicle.

18 SOW, Page 3, Section 2 : Background - Considering the ongoing TRIO project is already implementing Oracle Financials for TSA and USCG, has DHS made a decision to select Oracle Financials for the EFiMS procurement?

Please see the response to Question Number 5. No, DHS has not made a decision to select a particular software. All software types are welcome to bid on this procurement.

19 SOW, Page 3, Section 2 : Background - Is the TRIO solution integrated with the PRISM procurement solution?

No, the Trio solution is not currently integrated with PRISM. Please see the response to Question Number 5. The proposed software must meet the DHS requirements as described in the SOW.

20 SOW, Page 3, Section 2 : Background - Has DHS already completed a separate competition to move PRISM procurement users to a different procurement solution? If so, what is the procurement solution selected for TRIO?

No, DHS has not already completed a separate competition. Please see the response to Question Number 5. The proposed software must meet the DHS requirements as described in the SOW.

27 SOW, Page 3, Paragraph 3 - Is IBM also providing Consulting and Advisory Assistance (CMS) services to the JPMO, under this SDA task order award?

No. The SDA vendor is not providing Consulting and Advisory Assistant services to the JPMO.

28 SOW, Page 3, Paragraph 3 - Has a conflict of interest been evaluated? Please see the response to Question Number 27.

29 SOW, Page 3, Paragraph 3 - Is there a proposed mitigation plan? Please see the response to Question Number 27.

38 SOW, Page 5, Capability Gap #1 - What kind of "compensation controls" is DHS currently using? Please provide the cross reference to the related requirements for this capability in the attachments provided.

The gap capability list has been removed from the SOW. The EFiMS SW requirements are outlined in the SOW.

39 SOW, Page 5, Capability Gap #3 - Is the Government seeking to replace all currently fielded systems at the identified target components, even when targeted incremental updates would close this capability gap for a fraction of the cost of replacing these systems altogether? Please clarify.

Please see response to Question Number 38.

40 SOW, Page 5, Capability Gap #3 - Is the Government currently using "cuff systems" to reconcile data between non-integrated systems? If so, please identify any such existing tools.

Please see response to Question Number 38.

41 SOW, Page 5, Capability Gap #3 - Are any of these tools targeted for elimination under this modernization program? Please provide the cross reference to the requirements related to any existing functionalities in these tools that the new solution needs to support.

Please see response to Question Number 38.

# Question/Reference DHS Response 42 SOW, Page 5, Capability Gap #4 - What kind of "non-standard methods" are DHS customers currently utilizing?

Please see response to Question Number 38.

43 SOW, Page 5, Capability Gap #4 - What are the specific financial information requests DHS needs to support for Congress? Are these included in the attachments provided?

Please provide a cross reference.

Please see response to Question Number 38.

44 SOW, Page 5, Capability Gap #5 - The Draft SOW states "DHS lacks the ability to streamline financial data collection and sharing across the enterprise. The Department relies on manual labor-intensive data calls to generate Department- level financial reports. The department lacks the capability to share information across organizational boundaries and from disparate systems.·

Is this referencing Departmental financial reporting/consolidation capabilities, currently supported by the DHS TIER system?

Please see response to Question Number 38.

45 SOW, Page 5, Capability Gap #5 - Is the TIER system within the scope of this procurement? Please provide a cross reference to the related requirements in the attachments provided.

Please see response to Question Number 38.

46 SOW, Page 5, Capability Gap #6 - Does Capability Gap #6 describe the current need to have to customized systems for emerging requirements?

Please see response to Question Number 38.

47 SOW, Page 5, Capability Gap #6 - How can any software vendor claim to meet future/emerging requirements without system changes if those requirements do not even exist yet?

Please see response to Question Number 38.

48 SOW, Page 5, Capability Gap #7 - Can the Government elaborate on the term "limited web services?" Please provide cross

Please see response to Question Number 38.

49 SOW, Page 6, Capability Gap #7 - Is it not a fact that all current Federal financial, procurement, and asset COTS systems available in the Federal market today are considered proprietary and subject to vendor's software licensing terms?

Please see response to Question Number 38.

50 SOW, Page 6, Capability Gap #7 - What specific proprietary constraints is the Government referring to?

Please see response to Question Number 38.

51 SOW, Page 6, Capability Gap #7 - How are proprietary constraints "limiting resources available," given that all COTS products have proprietary constraints?

Please see response to Question Number 38.

52 SOW, Page 6, Capability Gap #10 - Similar to Capability Gap #5, Capability Gap #10 also seems to be referencing Departmental financial reporting/consolidation capabilities currently supported by the DHS TIER system. Is the Tl ER system within the scope of this procurement? Please clarify and provide a cross reference to the related requirements in the attachments provided.

Please see response to Question Number 38.

# Question/Reference DHS Response 53 SOW, Page 6, Capability Gap #10 - In order for the Department to share information across organizational boundaries, the existing systems must have common key identifiers to provide reporting. Has DHS undertaken, or is it planning to undertake, a data-centric approach to address this gap?

Please see response to Question Number 38.

60 SOW, Page 7, Bullet 3 - Is the Government looking for specific data export and import capabilities? Please provide the cross reference to related requirements in the attachments provided.

The Government is looking for the ability to generate ad-hoc, or as-needed, reports from the software. The proposed software should not include any restrictions on the government's ability to retrieve data from the software.

The SOW has been updated to provide additional details on the Government's ad-hoc reporting requirements.

61 SOW, Page 7, Section 4, second paragraph - How does the Government plan to provide fair opportunity, competition, and selection of the final COTS software product at USCG and TSA, given that DHS is already in the middle of its TRIO financial management modernization project at those components and implementing Oracle Financials there?

Please see the responses to Question Numbers 5 and 7. The Trio, as it is known today, may leverage the EFiMS software vehicle for future modernization requirements.

62 SOW, Page 7, Section 4, second paragraph - Given this requirement, why is the procurement based on the Treasury FIT requirements (in Attachment A) upon which the TRIO solution was already evaluated against before moving the Oracle Solution at

DOI?

Please see the response to Question Number 5. The SOW encompasses all DHS Components. The software proposed should be based upon the SOW requirements. The SOW is not solely based upon FIT, but all federal agencies have to align to these requirements.

64 SOW, Page 7, Bullet 7 - Since there are no component level requirements at this stage, how does the Government plan to avoid customizations if capability gaps are identified in the future?

The broad-based SOW for EFiMS software identifies the requirements needed across the DHS enterprise. However, during the task order fair opportunity process, Component unique requirements may be identified.

76 SOW, Page 13, Section 5.8, Bullet 2, #15 - Is the Government referring to "Oracle Fusion Middleware"? If not please provide details on what the Government means by "core fusion middleware."

The SOW has been revised. The license management section was completely updated to more clearly define what the Government was expecting. Tables were added to provide a list of elements with descriptions of the information the vendor shall provide in their proposals for license agreements, maintenance agreements, and software related services.

77 SOW, Page 13, Section 5.8, Bullet 2, #15 - If the Government is referencing "Oracle Fusion Middleware" please cross reference the requirements in Attachment A to the intended use of the "Oracle Fusion Middleware."

The SOW has been revised. The license management section was completely updated to more clearly define what the Government was expecting. Tables were added to provide a list of elements with descriptions of the information the vendor shall provide in their proposals for license agreements, maintenance agreements, and software related services.

83 SOW, Page 14, Section 5.8.1 - What current licenses among those listed in Section 5.8 does DHS currently hold for the components that fall within the scope of this procurement?

The Component licenses identified in this section are within the scope of the EFiMS software multi-award vehicle. Also, please see the response to Question Number 5.

# Question/Reference DHS Response 84 SOW, Page 14, Section 5.8.1 - What is DHS's expected number of license-provided testers at each DHS component?

The COTS software vendor/SaaS provider shall support the following transfer requirements at no additional cost to the Government:

•The ability to transfer licenses between users •Unlimited user license agreements •Allow perpetual per current user licenses •Upgrade current licenses to the latest version •Allow usage of licenses for so ware tes ng and development •Transfer of purchased licenses toward a subscrip on-based model •Licenses purchased by any DHS Component shall be transferable to DHS HQ and other DHS Components •Flexibility to transfer so ware between data centers at no addi onal cost to support disaster recovery and other activities •Flexibility to transfer licenses from DHS to a cloud environment •Flexibility to transfer licenses from DHS to the Quality Service Management

Office (QSMO) for financial management.

86 SOW, Page 14, Section 5.8.2 - Does this table represent the volume of licenses DHS plans to purchase through this procurement?

Please see the response to Question Number 83. This table provides estimated current user levels for existing systems. Subsequent task orders issued under the IDIQ will include specific Component license requirements.

87 SOW, Page 14, Section 5.8.2 - If the statistics in the table are correct, why does USSS require 6,500 financial system users, given USSS has approximately 7,300 FTEs in total?

Please see the response to Question Number 86.

88 SOW, Page 15, Section 5.9.1 - Is DHS currently using a specific web-based tool for license management? If so, which one is it?

No, DHS does not currently use a specific web-based tool for license management. After further review, DHS determined that this should not be included in the SOW. This section has been removed.

89 SOW, Page 15, Section 5.9.1 - Are the bullets listed in Section 5.9.1 to be considered requirements for this tool, or are there separate or additional requirements in the attachments provided?

Please see the response to Question Number 88.

90 SOW, Page 15, Section 5.9.1 - Why is there is no reference to licensing costs for this tool in the pricing tables?

Please see the response to Question Number 88.

# Question/Reference DHS Response 94 SOW - Page 16, Section 5.11 –

In order to price data migration services, we will need the following for the existing systems:

•Data architecture •Data logical model •Data physical model

Does the Government plan to provide these documents with the Final SOW?

The SOW has been updated to include additional details on the professional services covered under this SOW. The EFiMS software SOW has been updated to more clearly define the scope of services that will be included under the EFiMS software multi-award vehicle.

98 SOW Attachment A, Page 20, first paragraph - The draft SOW states “The use cases are reviewed and updated annually by FIT, refer to the Treasury FIT website for the latest version https://www.fiscal.treasury.gov/fsservices/gov/fit/fit_usecase.htm.” The hyperlink for Treasury FIT use cases provided above is inactive and no such webpage exists. Please update.

The hyperlink for Treasury FIT has been updated.

https://www.fiscal.treasury.gov/fit/financial-management-standards.html There are sub-links for use cases, system requirements, functions/activities, etc.

99 SOW Attachment A, Page 20 - The first use case is titled “Budget Formulation to Execution”, but does not include any budget formulation activities.

Budget formulation is traditionally not considered part of a core financial system. Is the government planning to add this as a separate line item in the Pricing schedules?

There are aspects of budget formulation that are within the scope of the EFiMS software SOW. A separate line item in the Pricing schedules is not necessary for the budget formulation requirements in the EFiMS SOW.

Attachment A is based on the Treasury Office of Financial Innovation and Transformation (FIT) business use cases. These use cases include some aspects of budget formulation. Vendors should propose software that meets the scope of formulation requirements included in the SOW.

100 SOW Attachment A, Page 20 - Are there any existing budget formulation tools or systems DHS plans to retire and replace with a new system purchased through this procurement? Please identify any such systems.

Section 2.2 of the EFiMS SOW includes the DHS current state of systems that may be modernized under this multi-award contract vehicle. Please see the response to Question Number 99. Vendors should propose software that meets this requirement in their proposals.

101 SOW Attachment A, Page 20 - Does DHS have a preferred Budget Formulation system or vendor, that should be part of the new EFiMS solution?

No, DHS does not have any preferred system or vendor. Please see the response to Question Number 99. Vendors should propose software that meets this requirement in their proposals.

102 SOW Attachment A, Page 20 - Will the government be updating the first use case to include Budget Formulation activities?

Please see the response to Question Number 99. Attachment A is based on the Treasury Office of Financial Innovation and Transformation (FIT) business use cases. These use cases include some aspects of budget formulation.

Vendors should propose software solutions that meet the scope of formulation requirements included in the SOW.

103 SOW, Attachment A, Page 21 - Acquire to Dispose use case 020.FFM.L1.01 Property, Plan, and Equipment (PP&E) Assets - This use case is very high level. Will DHS be providing additional details, such as business rules, on how to capture and classify different types of assets, to meet DHS requirements?

See Attachment D to the SOW for level 4 DHS standard process requirements.

# Question/Reference DHS Response 110 SOW, Attachment B - Page 26, Section 2, Constraints #3 –

The Draft SOW states "Financial audit requirements. Process, performance, regulatory, administrative, and statutory requirements necessary to achieve "clean" financials without reliance on manual processes to maintain auditability must be met.

DHS obtains a clean audit opinion at the Departmental level. Most components do not get separate opinions. How is the Government defining "clean" financials? Are "clean" financials the absence of material weaknesses related to internal controls?

Vendors should propose software that meet this requirement in their proposals. The term “clean audit opinion” means that the financials allow DHS to receive an audit opinion with no material weaknesses.

120 SOW, Attachment C, Page 51, #10 - Is the government planning to add a separate line item in the Pricing schedules for a Business Intelligence and Decision Support Reporting tool?

The Business Intelligence and Decision Support Reporting capability will be part of the Component specific requirements. However, the capability to provide reporting from the software is required. Vendors should propose software that meets this requirement. A separate contract line item number will not be added to the price schedule for reporting.

121 SOW, Attachment C, Page 51, #10 - Are there any existing Business Intelligence and Decision Support Reporting tools or systems DHS plans to retire and replace with a new system purchased through this procurement? If so, please identify any such systems. If not, will DHS be providing the tool to be used and if they currently have licenses or if licenses should be prices as part of this solution?

Please see the response to Question Number 120.

122 SOW, Attachment C, Page 51, #10 - Does DHS have a preferred Business Intelligence and Decision Support Reporting system or vendor that should be part of the new EFiMS solution?

No, DHS does not have a preferred system or vendor.

124 SOW, Attachment D, Page 53-54, BF2E Requirement 1.1.2.1 Conduct internal base budget review - Is the government planning to add Budget Formulation as a separate line item in the Pricing schedules?

Please see the response to Question Number 99.

126 SOW, Attachment D, Page 53-54, BF2E Requirement 1.1.2.1 Conduct internal base budget review - If the government is planning to procure a new Budget Formulation system, please identify if DHS has a preferred Budget Formulation system or vendor, that should be part of the new EFiMS solution?

Please see the response to Question Number 99.

127 SOW, Attachment D, Page 67, 2.1.32 Approve general ledger entries - The requirement states “The solution shall provide the capability to upload and view back-up documentation in various formats for journal vouchers.” Such capabilities are usually provided by Enterprise Content Management (ECM) systems.

Is ECM part of the scope of this procurement?

There is no explicit requirement for a separate document management solution under the EFiMS SOW. The EFiMS software proposed must satisfy the requirements outlined in the SOW.

129 SOW, Attachment D, Page 67, 2.1.32 Approve general ledger entries - If the government is planning to procure an ECM system, please identify if DHS has a preferred ECM system or vendor that should be part of the new EFiMS solution.

Please see the response to Question Number 127.

# Question/Reference DHS Response 130 SOW, Attachment D, Page 67, 2.1.32 Approve general ledger entries - If there is an existing system the government intends to use, please provide license details and specify those that need to be priced as part of this solicitation.

No, the Government does not have an existing system that will be used by Components.

131 SOW, Attachment D, Page 69-70, 2.3.1 Trading Partner Reconciliation and Elimination,

2.3.1.1 Reconcile cdifference(s) with a trading partner Page 94, 4.4.3.1 – This requirement relates a trading partner reconciliation/ discrepancy resolution process.

1. Is DHS planning to

a) use this reconciliation mechanism within the core financial system;

b) use G-invoicing, or;

c) is there already a third party tool in place to support this function?

DHS does plan to use this reconciliation mechanism within the core financial system. In addition, DHS will use G-invoicing, which is a federal mandate.

Lastly, there is no third-party tool to support this function.

132 SOW, Attachment D, Page 69-70, 2.3.1 Trading Partner Reconciliation and Elimination,

2.3.1.1 Reconcile cdifference(s) with a trading partner Page 94, 4.4.3.1 - If a third party tool is in place, please clarify whether DHS plans to continue using it or whether it will be replaced. Please provide details about existing licenses already available to DHS, and/or any that need to be priced.

Please see the response to Question Number 131.

135 SOW, Attachment D, Page 69-70, 2.3.1 Trading Partner Reconciliation and Elimination,

2.3.1.1 Reconcile cdifference(s) with a trading partner Page 94, 4.4.3.1 - Is the requirement in 2.3.1.1 only for reconciling trading partner differences internal to DHS, or for differences with any Government entity?

Includes activities associated with the reconciliation of inter/intra-governmental and intra-entity trading partner transactions.

136 SOW, Attachment D, Page 69-70, 2.3.1 Trading Partner Reconciliation and Elimination,

2.3.1.1 Reconcile cdifference(s) with a trading partner Page 94, 4.4.3.1 - Is DHS looking to operate a separate intragovernmental reconciliation tool for addressing DHS-only discrepancies, in addition to an interface to G-invoicing to address governmentwide discrepancies?

No, DHS is not looking for a separate reconciliation tool.

137 SOW, Attachment D, Page 90, 4.3.1 Invoice Entry, 4.3.1.2.b Match and validate mixed Invoice - The requirement states “The solution shall provide the capability to perform both positive and negative matching to purchase orders and to other invoices. For example, enter an invoice for -$100 with invoice Type as "Mixed" and match to an invoice for -$200 and to a purchase order for $100.” What is the purpose of “mixed” invoices, and why match an invoice to another invoice? Please also provide the references to the applicable use cases.

DHS requires EFiMS software that recognizes and allows for credits. Under the current process, a vendor would have to send a new invoice that credits charges from a previous invoice. Requirement 4.3.1.2.b will be combined with 4.3.1.2.c and re-worded.

138 SOW, Attachment D, Page 95, 4.4.6, Advance Payments, 4.4.6.2, Process advance payment - The requirement states “The solution shall provide the capability to liquid Permanent Change of Station (PCS) advances once the traveler files an approved claim.

The system determines the gross-up and tax withholding amount, offsets the proposed disbursements by the advance and withholding amounts, liquidates the advance, and processes the PCS voucher for disbursement.” Is an employee relocation system part of the scope of this procurement?

No. This is the accounting portion of the PCS function. Liquidating the obligation and recording the transactions in the financial system.

# Question/Reference DHS Response 139 SOW, Attachment D, Page 95, 4.4.6, Advance Payments, 4.4.6.2, Process advance payment - Is the government planning to add an employee relocation system as a separate line item in the Pricing schedules?

No. This is the accounting portion of the advanced payment function.

Liquidating the obligation and recording the transactions in the financial system.

140 SOW, Attachment D, Page 95, 4.4.6, Advance Payments, 4.4.6.2, Process advance payment - Is the government planning to sunset, retire, and replace the mLINQS employee relocation system currently in use at DHS, with a new system purchased through this procurement? If not, is DHS expecting pricing of license for mLINQs are part of this solution? Please provide details related to available licenses or the number of licenses that need to be priced.

HR/Travel type systems are not in scope for the solution. However, there may be financial impacts that would be captured in the solution, so an interface may be needed. We are focused on transactions from external systems that would provide financial transactions to the solution.

142 SOW, Attachment D, Page 95, 4.4.6, Advance Payments, 4.4.6.2, Process advance payment - If the government is planning to procure a new employee relocation system, please identify if DHS has a preferred system or vendor that should be part of the new EFiMS solution?

HR/Travel type systems are not in scope for the solution. However, there may be financial impacts that would be captured in the solution, so an interface may be needed. We are focused on transactions from external systems that would provide financial transactions to the solution.

144 SOW, Attachment D, Page 100 - 101, 5.1.2.4, 5.5.1.3 and 5.5.2.1 - These requirements are designated as "duplicate." However, the requirements referenced do not seem to be referring to the same capabilities. Please clarify.

Requirements were re-worded to capture the level 4 process title.

145 SOW, Attachment D, Page 101, 5.5.4.1, Validate and receive royalty reports - This requirement refers to the "capability to Validate and receive royalty reports." Please provide additional clarifications - what kind of royalty reports? What kind of validations? Are there use cases that relate to this requirement?

A royalty report is a basic obligation and disbursement report that shows that an obligation and disbursement has taken place in accordance to how the royalties were established (i.e. monthly, quarterly, yearly, semi-yearly) and that funding is available as required. A use case may be made available during a fair opportunity process.

146 SOW, Attachment D, Page 101, 5.5.5.1, 5.5.5.2, 5.5.5.3 and 5.5.5.4 - These requirements state, "Process is not performed - see NEW process requirement below."

Please clarify - are these no longer applicable, and are these not requirements?

Requirements were re-worded to capture the level 4 process title.

147 SOW, Attachment D, Page 106, 6.1.1.3 through 6.2.1.1, Page 107, 6.2.1.3 to 6.3.1.4,

6.3.2.2 to 6.3.3.4 - These requirements all state “N/A”, and that they are covered elsewhere. No specific requirements are cited or cross-walked. Please clarify. Are these no longer applicable, and are these not requirements?

Requirements were re-worded to capture the level 4 process title. 6.2.1.3 was deleted.

148 SOW, Attachment D, Page 107, 6.3.2.1 - This requirement references the "capability to modify reimbursable agreements as the buyer." Please provide additional details - how would this functionality work, without compromising internal controls over agency data?

Modifications to reimbursable agreements will be on a bilateral agreement basis with the servicing agency, and not conducted in a unilateral state. This will ensure there is no compromise to IC of data.

# Question/Reference DHS Response

163 SOW,

•The License Name •The License Descrip on •What the License supports (func ons/technology) •Licensing Metrics – Applica on User, Unlimited License, Perpetual, Server, Processor, etc.

Enterprise Financial Management Solution (EFiMS) SOW

– Draft 14 •Technology/Business Solu on •Func onality – Full, Read Only, Limited, unlimited license agreement (ULA), etc.

•License cost structure – Ini al cost per license, yearly maintenance cost, etc.

Suggest changing “license” to “license/subscription.”

Please see the response to Question Number 76.

164 SOW, The software suite vendor shall provide Tier 3 level support the following services requirements:

●Installa on of So ware suite ●Configura on of So ware suite ●Data Migra on ●Ini al Setup & Training ●Planning Support to Configure and

Install the Software suite These services are typically offered by an integrator as opposed to the software vendor.

Suggest the procurement include awards for both software vendors and implementers of such software.

Please see the response to Question Number 94.

167 SOW, Attachment C - FMSS Taxonomies and Requirements A comprehensive listing – no suggestions

Thank you for your feedback.

175 SOW: Installation of Software Suite: We recommend DHS provides details such as:

Operating System (Solaris, SuperCluster)?

Installation of software has been removed from the professional services requirements. Please see the response to Question Number 94.

176 SOW: Installation of Software Suite: We recommend DHS provides details such as: In how many environments (Dev, Test, Stage, Pre-Prod, Prod)?

Installation of software has been removed from the professional services requirements. Please see the response to Question Number 94.

177 SOW: Installation of Software Suite: We recommend DHS provides details such as:

What are the security requirements for this installation (4300-A, Impact level 3)?

Installation of software has been removed from the professional services requirements. Please see the response to Question Number 94.

178 SOW: Installation of Software Suite: We recommend DHS provides details such as: Will the staff need to be onsite (At DC1, DC2, NDC, all, none)?

Installation of software has been removed from the professional services requirements. Please see the response to Question Number 94.

179 SOW: Installation of Software Suite: We recommend DHS provides details such as:

Operating System (Solaris, SuperCluster)?

Installation of software has been removed from the professional services requirements. Please see the response to Question Number 94.

180 SOW: Installation of Software Suite: We recommend DHS provides details such as:

In how many environments (Dev, Test, Stage, Pre-Prod, Prod)?

Installation of software has been removed from the professional services requirements. Please see the response to Question Number 94.

# Question/Reference DHS Response 181 SOW: Installation of Software Suite: We recommend DHS provides details such as:

What are the security requirements for this installation (4300-A, Impact level 3)?

Installation of software has been removed from the professional services requirements. Please see the response to Question Number 94.

182 SOW: Configuration of Software Suite: We recommend DHS provides details such as:

How much configuration will be required?

Configuration of software has been removed from the professional services requirements. Please see the response to Question Number 94.

183 SOW: Configuration of Software Suite: We recommend DHS provides details such as:

Will CEMLI files be provided from legacy systems?

Configuration of software has been removed from the professional services requirements. Please see the response to Question Number 94.

185 SOW: Data Migration: We recommend DHS provides details such as: From which systems, how large are the data sets?

Data migration has been removed from the professional services requirements. Please see the response to Question Number 94.

186 SOW: Data Migration: We recommend DHS provides details such as: How much historical detail?

Data migration has been removed from the professional services requirements. Please see the response to Question Number 94.

187 SOW: Data Migration: We recommend DHS provides details such as: What are the data formats?

Data migration has been removed from the professional services requirements. Please see the response to Question Number 94.

188 SOW: Data Migration: Will there be the need to scrub data and will enterprise data quality tools employed?

Data migration has been removed from the professional services requirements. Please see the response to Question Number 94.

189 SOW: Initial Setup and Training: How does this task differ from Installation? Initial setup and training has been removed from the professional services requirements. Please see the response to Question Number 94.

195 SOW:

On section 3.3.1 on page 30, DHS requires a system response time of 15 seconds. There are many factors that affect system response times, including factors that are completely outside of the control of the software’s design and performance, such as network bandwidth and other external factors. We suggest that this requirement be revised to limit it to factors that are within the control of the software application.

The SOW has been updated to address this comment and to eliminate factors that are outside of the software application.

201 SOW: On page 3 of the draft SOW, DHS lists several components that it plans to modernize financial systems. Specifically, CWMD, USSS, TSA, USCG, FEMA, ICE, NPPD, DHS HQ, S&T, USCIS. Notably, CBP is not listed. Why not? Conversely, why are the Trio

– CWMD, TSA and USCG listed? The Trio FSMS is in progress.

The SOW has been revised to clarify that CBP is within the scope of the EFiMS software.

Also, please see the response to Question Number 5.

# Question/Reference DHS Response 202 SOW: The RFI mentions a planned services solicitation later in the fiscal year. If a vendor is selected for this software solicitation, does it preclude that same vendor from competing for the services work?

This procurement, EFiMS software, is anticipated to be a multi- vendor, multi-award vehicle to be used by all Components to purchase software with a fair opportunity competition and selection methodology when the Component has the need to modernize. A separate Enterprise Financial System Integration (EFSI) multi- award contract vehicle will be utilized to support the EFiMS software licenses selected from contract vehicle. Anticipated services on EFSI that can be used to support EFiMS SW, include, but are not limited to:

program management, training, system lifecycle management (service strategy, service design, service operations, service transition, and continuous service improvement), configuration/implementation, technical support, and help desk.

A vendor that receives an EFiMS software contract award is not precluded competing for the EFSI contract award.

231 General Comment: Procurement Vehicle We would like to suggest DHS could obtain the most flexible and competitive solutions by not limiting this procurement to existing agency vehicles. The ability to attract and evaluate the best Federal and commercial solutions and services via the use of broad GWAC vehicles (e.g. GSA IT 70 etc.) will provide DHS the most complete and robust offerings. For example, DHS could utilize the GSA IT-70 schedule to acquire solutions and services, as well as allow for vendors to include open-market items (e.g. ODCs) to provide the best offering and capabilities for DHS.

This procurement will be solicited as an open market competition Federal Acquisition Regulation Part 15. In addition, DHS will leverage other in-house or agency-wide contracts for products and services not supported under this multi-award vehicle.

232 What is the expected term of the resulting IDIQ (i.e. 1 Year Base and 4 Option Years)? The expected period of performance will be the following a base period and four option periods totaling 20 years.

233 Is there a planned implementation or project schedule detailing a timeline for consolidating each component's core financial system? Understanding this timeline will ensure DHS receives the most advantageous license pricing structure.

Please see the response to Question Number 194.