RFI_140A1625R0018_AM1_Q_A_2.pdf

Question Answer The RFI expresses interest in a COTS solution but also states the need for full source code, unlimited licenses, and government ownership of the system. This seems to contradict the intent. Could the government clarify whether it expects full source code access and ownership from a COTS vendor, or whether this applies primarily to a custom developed solution (via low-code/no-code) as another possible option?

CotS Solutions would not include data rights for ownership. Only solutions developed at the governments expence.

Can the government provide more detail on the format, volume, and accessibility of legacy TAAMS data for planning migration timelines and costs?

Format is Oracle Databasing, Volume of Current Data is 21T, and all data will need to be fully migrated and incorporated into the new system. Durring migration, both systems would be run simultaneously to facilitate data migration untill complete, wherein the legaszy syste would be shut down.

Can the government confirm whether the new system must integrate with the current versions of TFAS, BTFA, and LockBox systems via existing APIs?

Bureau of Trust Fund Administration(BTFA) is an office outside of Office of Trust Services (OTS).

They administer TFAS and Lockboxs. Our office cannot change those solutions, so any new (proposed) system would need to integrate with the current versions of these systems via API.

The SOW references “1,000 concurrent users.” Could the government confirm expected total users for licenses ROM, peak concurrent sessions, and whether this is expected to grow during the contract period?

The answer to this question is found at 3.1.1 of the "1.1 TAAMS Enterprise License SOW". 1500 total users, and 800 concurent (peak) users. Number of users could possibly go up or down over the years based on govt need, however, this would always be represented by an appropriate change in the contract to reflect costs.

Given the urgency to move off the on-premise environment, does the government have a targeted go-live timeframe or phased migration milestone plan in mind?

There is no current migration plan. The answers to this RFI are meant to inform any potential plans going forward. The answer to this question is the information the Government is seeking from industry.

Where is the current database for TAAMS located or co-located and what is the size/scope of the system itself?

The system and the data are currently hosted on site by the incumbent in Phoenix, AZ. The goal is to transfer to a cloud based hosting system. The size of the current data is 21T.

Is the database going to be accessed only within the U.S. and if not, is there a list of countries that officials will be accessing it from?

Only in the US, but this explicitly includes Alaska, so it is not OCONUS.

Will the Government consider extending the page count limit for responses to 20 pages? Additional pages will allow vendors to address all questions/requirements in more detail, which will help with your analysis of alternatives (AoA) effort.

Yes. We will accept responses up to 20 pages.

Could the government please confirm that the cover page and the table of contents are excluded from the page limit?

Confirmed. The Cover page and table of contents are not in cluded in the 20 page limit.

To ensure we provide the most relevant information, could the government please share its definition of 'developmental solutions'?

Any solution that is not turnkey. If there is conficuration time, setup time, any low/no code setup, etc. Basically, if your solution doesn’t exist untill you receive a contract to make it, it is developmental.

Based on the referenced text, we assume CGI Federal's propriatary Enterprise Resource Planning (ERP) tool, Momentum, provides core ERP functionality for TAAMS. Could you please confirm this assumption?

Momentum is the accounting system for Other federal agencies. TAAMS is not a product of Momentum. TAAMS is a land management system, not an accounting system. TAAMS "accounting" functions are limited to Billing and remittance functions for Land transactions.

the "accounting" for these funds are completed by TFAS.

Could the government please share what other software products are part of the current TAAMS solution?

All products, including third party products, are listed within the functionality map document.

Qlik, KLFX, and Filenet. Proposed solutions may inlude other ways to meet these requirements as the proposer sees fit.

Could the government please provide a Technical/ Application Architecture diagram for TAAMS? Yes. Please find attached.

RFI 140A1625R0018 Amendment 1 Q&A

Could the government please provide a list of internal and external systems that TAAMS integrates with?

The two portals listed in the functionality map, Bureau of Trust Fund Administration(BTFA) Trust Funds Accounting System (TFAS), and Office of Natural Resources Revinue (ONRR) Minnerals Revinue Management Support Systems.

Could the government please provide details on which modules utilize out of the box functionality and which modules are custom built?

Over the 25+ years that the government has utilized TAAMS, it has requested/required customizations on all mondules. Further, the government owned modules require the base system's functionality. The two are functionally inseperable at this time.

Sheet1