~190K Year
Across the metropolitan administration
10K+ Year
Governed through formal institutional processes
92
Within the metropolitan institutional ecosystem
One
Connecting operations with legacy systems and institutional history
1. The Enterprise Challenge
A major metropolitan public authority in Southern Europe governs a territory of 92 municipalities, approximately 1,170 km² and close to 3 million residents. Its responsibilities span strategic planning, mobility and roads, public infrastructure, metropolitan schools, procurement, territorial development, environment, administrative governance and digital transformation. Over time, those responsibilities had produced an equally complex information landscape.
Enterprise applications, internally developed solutions, workflow platforms, departmental archives, correspondence systems, administrative-resolution applications and custom integrations had been introduced at different moments to solve specific organizational needs. Some had become technologically obsolete. Others still contained years of institutional information and history that could not simply disappear. And several apparently configurable workflow environments depended in practice on substantial custom software for forms, rules, integrations, document generation, exceptions and user interaction.
The authority therefore chose not to modernize by rebuilding every application independently. The objective was to establish a shared enterprise information and operational layer capable of progressively taking responsibility for reusable capabilities such as content, business objects, cases, processes, institutional communications, digital trust, search, integration and evidence. Legacy systems could then be replaced where appropriate — or remain connected where their history or specialist responsibility still mattered.
Modernization became an ongoing architectural capability rather than a sequence of application replacement projects.
2. Why it was complex
The challenge was not simply moving old software to newer technology. It was preserving business meaning and institutional continuity while the systems underneath them changed.
Modernizing every legacy application would preserve fragmentation
Many existing applications duplicated capabilities that could instead become shared enterprise services. Rebuilding each one individually would have modernized the technology while retaining the same architectural silos.
Historical depth makes some systems temporarily irreplaceable
An application may contain years of documents, metadata, relationships and institutional history. Replacing its interface may be easy. Reconstructing everything behind it may not be. The architecture therefore had to support coexistence rather than forcing a high-risk big-bang migration.
A workflow diagram is not the complete operation
Existing process platforms often contained only part of the real business behavior. The production application also depended on: Forms · Rules · Validation · Data · Documents · Integrations · Exceptions · Specialized Actions. Migration therefore required recovering what actually makes the administrative operation work, not simply reproducing its process diagram.
Correspondence can initiate much larger operations
The administration handles approximately 190,000 correspondence registrations every year. A communication can be registered and archived — but it can also initiate an administrative issue, activate a procedure, involve a responsible organizational structure and generate subsequent work. Registration is therefore often only the first event.
Institutional decisions require governed execution
More than 10,000 formal administrative resolutions every year can involve proposals, supporting content, organizational review, approvals, digital signatures, registration, publication and resulting evidence. The final document must remain connected to how the institutional decision became legitimate.
3. How Coopera Holds the Operation Together
Coopera provides a common operational foundation across administrative domains rather than becoming another vertical application. Content, persistent business context, lifecycle, communication, processes, integration and evidence can therefore be shared while different public-sector realities retain their own rules and responsibilities.
The Living Business Objects
The environment can maintain different persistent administrative realities, including: Administrative Resolution · Correspondence-to-Resolution Case · Administrative Case. The last category can represent domain-specific operations such as: Procurement · Contract · Authorization · Concession · Public Works · Funding Procedure · Administrative Request. These objects are different. They do not need one common lifecycle or one universal workflow. But each can maintain the context that must survive while people, documents, systems and processes change around it: Identity · State · Content · Relationships · Responsibilities · Approvals · History · Evidence · What can happen next.
- A workflow can start and finish.
- An application can eventually be replaced.
- A document can be generated.
- A legacy system can continue contributing historical information.
The administrative business object remains the persistent point of continuity. This is what allows modernization to proceed without forcing the administration to redefine its operations around every generation of software.
4. What This Looks Like in Practice
Administrative Resolutions
The document records the decision, the business object preserves how it became legitimate. An Administrative Resolution begins before the final institutional document exists. Its operational context can include: Proposing Structure · Subject · Supporting Content · Budget or Procurement References · Review · Approvals · Digital Signatures · Final Document · Registration · Publication · Evidence. Document composition therefore becomes part of execution around the Resolution. Different families of resolutions and determinations can preserve their own responsibilities and approval requirements while using the same underlying operational foundation.
The final document is critically important. But it is not the complete operation.
The Resolution preserves the context, responsibility and evidence through which the institutional decision became legitimate.
Correspondence-to-Resolution
Registration can become the beginning of the operation. Institutional communications can enter through email, certified channels, portals and other intake mechanisms. A communication can be: Received → Registered → Connected to a Case → Routed to Responsibility → Used to Start Work → Resolved. The correspondence record still provides formal evidence that the communication entered or left the administration. But the business issue created by that communication may persist much longer.
Coopera allows the correspondence to become part of the appropriate persistent administrative context rather than ending its operational life at registration.
Registration records the communication. The business object carries its consequences forward.
Administrative Cases
Complex public procedures can outlive individual workflows. Procurement, contracts, authorizations, concessions, public works, funding procedures and administrative requests can involve many documents, participants, decisions and external systems over extended periods. Representing the entire reality through one permanent workflow makes change increasingly difficult. Instead, the Administrative Case can preserve the persistent business context while different processes perform bounded work around it.
- A review process can begin and end.
- An approval process can follow.
- Another procedure can be introduced later.
The Case survives them. The work can change without requiring the administrative reality itself to be rebuilt.
Replacing Legacy Applications
The application can disappear without taking the operation with it. Some legacy applications provide capabilities that are now available horizontally through the shared platform: document storage, workflows, forms, tasks, search, simple case management or integration. Where those systems no longer provide unique value, their responsibilities can progressively move into the common environment. The legacy application can then be retired. Where a system still owns historical information or specialist functionality that cannot yet be replaced economically, it can remain connected.
This creates a pragmatic modernization rule: Replace where possible. Integrate where history or specialization still matters.
The administration can therefore modernize different areas at different speeds without forcing every operational domain into the same migration timetable.
5. Preserving Institutional Information Through Change
A central consequence of this architecture is that enterprise content becomes less dependent on the application that originally created it.
Historically, the relationship was often: Application → owns its documents.
The new model moves toward: Enterprise → owns its information and evidence
Applications → participate in their lifecycle. Documents, metadata, relationships, provenance and historical evidence can therefore remain accessible even when the originating application changes.
This is particularly important in government, where contracts, resolutions, concessions, procurement procedures, public works and correspondence may remain institutionally relevant for years after their original process has completed. Standardized interoperability applies the same principle to systems. A specialist application can participate today without becoming the architecture the administration must preserve tomorrow.
Information and operations become more durable than the technology currently executing them.
6. Continuous Modernization
The shared operational layer allows modernization to happen progressively.
- A legacy document application can be retired while its information remains.
- A workflow-heavy application can be rebuilt around persistent business objects and configurable execution instead of recreating its old custom architecture.
- A specialist system can remain connected until its replacement becomes justified.
- A new administrative service can consume the same content, process, search and integration capabilities without creating another independent technological stack.
The platform has also moved onto modern cloud infrastructure as part of the wider transformation. But cloud is not the central story.
Moving the existing application landscape to different infrastructure would have preserved the underlying fragmentation. The important change is architectural: Shared Information · Persistent Business Objects · Reusable Execution · Standardized Integration · Progressive Legacy Replacement.
Modern infrastructure supports the transformation. The shared operating model makes it possible.
6. The Outcome
The metropolitan authority is progressively replacing a fragmented landscape of legacy applications and custom solutions with a shared enterprise operational foundation. Approximately 190,000 correspondence records every year can participate in the same environment used to govern administrative information and processes. More than 10,000 Administrative Resolutions annually can retain their content, responsibilities, approvals and resulting evidence within persistent operational contexts. But transaction volume is not the most important result.
The deeper change is that responsibilities previously rebuilt repeatedly inside individual applications can become shared enterprise capabilities. Administrative operations can outlive the workflow technology or application originally used to execute them. Systems whose unique value has disappeared can progressively be retired. Systems whose historical depth or specialist responsibility still matters can remain connected while modernization continues around them. Institutional content does not need to disappear with the software that originally created it. The authority can therefore:
- replace one application without losing its information;
- redesign one process without losing its business meaning;
- retain one legacy system without making it the future architecture.
The result is not simply a new document-management or workflow platform. It is a continuous modernization layer that allows public-sector operations and institutional history to remain coherent while applications, workflows, integrations and infrastructure evolve around them.
5. What This Case Proves
Enterprise modernization does not require big-bang replacement
Different systems can evolve at different speeds while persistent administrative context provides continuity across the transformation.
The application is not the business operation
Administrative Resolutions, Cases and public procedures can survive multiple generations of software because their identity and operational history remain separate from the application currently performing part of the work.
Institutional history can survive application replacement
Documents, metadata, relationships and evidentiary context do not have to disappear when the system that originally created them is retired.
Interoperability can create modernization freedom
A legacy or specialist system can participate today without becoming the architecture the organization must preserve tomorrow.
