System Architecture
The TAMS target architecture aligns well with the FAS IT Transactional Macro-pattern. The elements that are not present are “X’d” out and these include the Use of a Content Delivery Network (CDN) and the Use of an external analytics component
The architecture will provide:
- A thin web client
- Security integration
- Microservice architecture with discrete components
- An abstracted CRUD data layer
- Service orchestration (Camel)
- Reporting
- Event Driven architecture
The following diagram shows the helicopter’s view of how the FCS ecosystem enables TAMS system cloud transformation. FCS infrastructure, security/compliance planes provide backbone infrastructure, networking, security fabric supporting TAMS system and TAMS will benefit from inheriting all built-in security controls within the fabric.
The TARPS application was written in COBOL and incompatible with cloud environments. As COBOL ages out of use, requisite support is more difficult to find and expensive. The program is also inflexible to patch/change business rules. Users have observed internal control deficiencies through erroneous payments to contract auditors. As a result, TARPS was decommissioned and TAMS was developed as its replacement.
Regarding the TAMS business reference architecture, the system capabilities are:
- manage audits per 31 USC 3726 and
- improve compliance/collections in response to 2014 OIG Audit.
TAMS System Reference Architecture
TAMS Conceptual Architecture
TAMS is closely aligned with our Transactional Macro-pattern and therefore a three tier architecture on EBTA was appropriate.
