Technical Approach
Learn how the FSS19 Phase 3 Modernization team is migrating the applications and the data to the cloud in order to eliminate the Mainframe dependency – while keeping the legacy systems running to avoid any disruptions to users.
High Level Approach
In order to understand the FSS19 Phase 3 Modernization effort, it is necessary to first understand the as-is state of the applications and their data.
- Applications: These legacy systems are currently located on-premises in the GSA EIO Data Center (FSSOnline, eFSSOnline, Contracting Services, and Mass Mods) or Clearpath Mainframe (Cobol programs).
- Tech Stack: Most systems are written in Java, a modern cloud-friendly coding language. However, FSSOnline (and Security) is a client-server desktop application written in PowerBuilder (not modern).
- Data: All systems still rely on data currently housed on the Unisys Clearpath Mainframe.
To achieve the goals of the FSS19 Phase 3 Modernization initiative, the cloud ready applications (Contracting Services and MassMods) will be “lifted-and-shifted” to the FCS MCaaS environment, and the other applications (FSSOnline, eFSSOnline, and Cobol programs) will be transformed and rewritten into a web-based cloud native application called Acquire, to remove the Mainframe dependency and allow the legacy applications to reap the benefits of the cloud.
The table below shows, for each system, a detailed description of the current state and the modernization approach proposed.
Description of Current State |
Summary of Proposed Approach |
|
Scope Area #1 - Contract Management Functions |
||
Contracting Services |
Java application housed in the on-prem GSA Data Center. Provides core back-end processes and web services to orchestrate contract and contract modification processes. |
Built in Java (i.e., cloud-ready), hence doing a lift-and-shift cloud migration. |
FSSOnline |
PowerBuilder Client-Server application. A procurement tool for the FAS workforce to track and manage contracts and mods from award date through contract lifecycle. |
A PowerBuilder application, requiring a code rewrite/cloud transformation into a new cloud-native application, Acquire |
eFSSOnline |
Web-based Java based application that is housed in the on-prem GSA Data Center and has limited functions from FSSOnline. |
The eFSSOnline is built in Java, but the functionality will be absorbed into the transformed Acquire application |
FSSOnline Security |
PowerBuilder hosted role-based registration service for several acquisition applications. |
A PowerBuilder application, requiring a code rewrite/cloud transformation into a new cloud-native application, Acquire |
Mass Mods |
A web-based Java application that is housed in the on-prem GSA Data Center and manages mass modifications to contracts. |
Built in Java (i.e., cloud-ready), hence doing a lift-and-shift cloud migration. |
FSSOnline Reporting |
The Acquisition workforce uses several reporting tools from Contracting Services and FSSOnline. |
Identify critical FSSOnline reports and rewrite as needed in the transformed Acquire. Contracting Services Reports will be part of the lift & shift. |
Note: These apps store data in the Mainframe DMSII Database and share data with other apps for other acquisition functions. Through modernization, the team will move the database and data as-is, continue to integrate with current interfacing applications (e.g., eOffer, eMod, ORS), maintain connectivity with interfacing utility apps (e.g., ECMS, API Exchange, SMTP), and support data needs of Falcon. |
||
Scope Area #2 - Mainframe Functions |
||
Acquisition-Related Cobol Programs |
The above apps depend on FSS-19 Cobol programs to manage some acquisitions functions and transmit data to downstream systems. |
The Cobol Programs will need to be transformed into cloud-friendly language. They will be refactored into Acquire or Contracting Services, as applicable. |
Cobol and URSA Reporting |
The Acquisition workforce uses several reporting tools and URSA. There are also backend Cobol processes that feed the Reports Portal. |
Build more robust Reporting capabilities. Remove dependency on URSA and Reports Portal. |
The FSS19 Phase 3 Modernization team is currently leveraging a scaled agile framework (SAFe) to perform the modernization work.The team is divided into five separate workstreams, which align directly to the project scope areas shown in the table above.
Ultimately, the goals of the FSS19 Phase 3 Modernization project are as follows: - Migrate legacy applications from on-prem GSA Data Center to FCS MCaaS using cloud-native tools and technologies to deliver changes faster - Accelerate migrating the data off the ClearPath Mainframe, providing significant cost savings - Achieve the enterprise solution that aligns with GSA’s long-term goal to build more modern, accessible, and streamlined acquisition systems - Promote a premier customer experience - Avoid disruptions to business line functions and maintain synchronization with downstream apps
This modernization project will carry GSA’s systems into the future, continue its commitment to Agile development practices, and facilitate low cost of maintenance, extensibility, and ease of use wherever possible.