AS-IS / TO-BE architecture for public platforms
Technical-functional survey and architecture definition as the starting point for evolving a platform already in institutional use.
Evolving a public platform does not start with a target stack. It starts with a technical-functional survey of what the institution actually runs — the AS-IS — and a definition of the architecture it needs to become — the TO-BE.
That sequence is deliberate. Without an honest AS-IS, the TO-BE is a slide. Without a TO-BE, the AS-IS is only documentation of the current constraint.
The work includes modular architecture, interoperability and the conditions for deployment and evolution: not only what to build, but the guidelines the institution will need after the consultancy ends.
This approach was the starting point of a consultancy for UNODC’s Global Programme on Cybercrime, on a technology platform for Uruguay’s National Cybercrime Unit. The same discipline applies wherever a public system has to change without pretending it is being invented from zero.