Answer to Questions DAAS RFI.pdf
PDF 163 KB Posted
- Solicitation number
- 20241203
- Issued by
-
Defense Logistics Agency
About this file
This document contains questions and answers related to a Request for Information (RFI) for the Defense Logistics Agency's (DLA) Defense Automatic Addressing System (DAAS) Modernization effort. The Q&A addresses technical requirements and specifications for the modernization project, including clarification that the "To-Be" environment requires high availability architecture solutions supporting warm or hot COOP in multi-availability zones and/or multi-region cloud environments.
Key details include that while MuleSoft Anypoint is DLA's current enterprise API Gateway solution, the government is open to other technology options that meet DAAS requirements. The modernization is described as a multi-year, multi-phase effort with schedule TBD based on chosen solution. All DAAS components (DDATA, DGATE, EBUS) and processes are in scope for modernization. Transaction processing details indicate an even split between individual and bundled transactions, with bundles ranging from a few to tens of thousands of transactions. Batch ETL processes currently run at frequencies from minutes to annual, with minimal resource utilization and typical run times of minutes to hours, though future state requirements may differ.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| DAAS Questions and Answers.xlsx | XLSX spreadsheet | |
| DAAS DBX RFI v2.docx | DOCX document | |
| DAAS DBX RFI.docx | DOCX document |
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
• For the ‘Full Continuity of Operations Plan (COOP)/Disaster Recovery (DR) Capabilities’, would that requirement be Hot, Warm or Cold COOP?
For the “To-Be” environment, the Government is looking for high availability architecture solutions which can operate in multi availability zones and/or multi-region cloud environments to support warm or hot COOP solutions.
• How tied is DLA to the MuleSoft Anypoint Platform? Would you be open to other technology options for the API Gateway?
Mulesoft Anypoint platform is the DLA enterprise API Gateway solution. While it is managed by the DAAS Program Office, the DLA enterprise API Gateway modernization is currently not within the scope of this effort. The Government is interested in any technology option which is best suited to meet DAAS requirements.
• What is your anticipated timeline/schedule for completion of DAAS modernization? Have phases or milestones been defined?
DAAS Modernization is currently a multi-year, multi-phase effort which includes the implementation of the “To-Be” environment and a seamless transition from the existing environment without impacting operations. The actual schedule including phases and milestones is TBD at this time and depends on the solution chosen.
• Has DLA prioritized which programs or processes within the four DAAS profiles (DDATA, DGATE, EBUS) or the API Gateway are in scope for modernization vs. which existing components should be maintained in their current state?
o All DAAS components and their associated processes are within the scope for modernization.
• What proportion of transactions are received individually vs bundled?
The bundling of transactions is customer driven. Proportion wise, it is estimated that they are evenly split.
• On average, how many transactions will be bundled together?
The transaction bundling is customer driven and could range from few to tens of thousands depending on the connection. Some of the processes require the entire bundle to be treated as a single entity processing wise to ensure data integrity.
• For batch ETL processes, what is the frequency for batch jobs?
Currently, DAAS operates batch jobs with frequencies ranging every few minutes up to a year for annual jobs. Please note that the ETL batch jobs align with the existing solution which may or may not be necessary in the future state depending on the solution chosen.
• How much compute is currently allocated to a batch job and how long do the jobs run?
Currently, DAAS ETL processes do not involve significant resource utilization and typically last between minutes to few hours. The existing cloud architecture supports auto-scaling of infrastructure to support additional resource requirements, as necessary. The RFI is focused on a future state which may involve different batch jobs with their own resource requirements based on the solution chosen.
The solution and the supporting infrastructure shall be scalable to support those.
File details come from the government source that posted it. Updated .