Update: The prototyping work for the first procurement is complete and the associated procurement has been awarded. The prototyping findings are available for review.
For our first procurement we are dealing with updating a new legacy code base (ARIES) that is very complex and difficult to understand, a deployment process that is opaque — and on top of that, we want to create new connections between legacy systems ARIES and EIS. The unknowns involved with this work are risky enough that we can’t be confident that vendors will be able to deliver anything without more guidance.
As this is our first prototype, we will be testing out some of the more foundational things, like a vendor development environment and deploy process, that will apply to all buys, as well as setting up the lines of communication with internal technical staff that will be necessary throughout the project.
Before we write this first RFP, we want to spend time prototyping so we can mitigate the following identified risks:
| Description | Criticality (1 - 5)* | Status |
|---|---|---|
| Creating a development and deployment pipeline that will allow vendors to deliver code that can be automatically evaluated and pushed to a staging environment | 2 | In progress. See DevSecOps Strategy. |
| Creating a process to get the delivered code into a production environment on a continuous basis | 5 | In progress. See DevSecOps Strategy. |
| Verifying that the existing identity service can be used for user authentication/authorization | 1 | Completed. |
| Accessing data from the legacy EIS system to show in search results | 3 | In progress. |
| Accessing data from the ARIES system and staging table to show in search results | 2 | In progress. |
| Validating that the data coming from multiple systems is potentially reconcilable | 3 | In progress. |
| Deploying existing ARIES code to production | 4 | In progress. |
* 1 = low criticality; 5 = high criticality
Prototype documentation: