Digitalization and modernization for public institutions

We help public institutions in Romania turn manual processes into digital services, update existing software and migrate applications to the government cloud. We work on public websites, portals and internal applications, taking account of existing data, public archives, integrations and the team responsible for operating them.

Tell us what you need to develop or change.

Why digitalization and modernization matter

A project may start with a service that is still handled manually, an application that is difficult to maintain or a planned move to the government cloud. Each situation calls for a clear assessment and a defined piece of work.

• Manual processes and disconnected information. Repeated data entry and information spread across documents or applications make requests harder to process and track.
• Software that is difficult to maintain. Unsupported components, known vulnerabilities and missing documentation complicate updates and the handover to another team.
• Interruptions and uncertain recovery. An institution needs to know how its services will be monitored and restored, and how changes will be tested before launch.

The figures below describe the use of digital public services and cyber incidents targeting public administration. The ENISA figure is a share of recorded incidents, not a percentage of institutions breached.

Digital solutions for public institutions

We develop websites, portals and internal applications around the work the institution needs to carry out. We start with the people using the service, the information they need and the steps that can be handled digitally.

• Processes and requirements. Define the user journeys, information, roles and responsibilities before development.
• Application development. Build the agreed interfaces and workflows for the public, the institution’s staff or both.
• Data and integrations. Connect the solution to existing systems where access and interfaces are available, and prepare any agreed content or data import.

What you receive: A tested digital solution, source code and access arrangements defined in the contract, technical documentation and training for the responsible team.

Government cloud migration

We assess, adapt and migrate existing applications and their data to the government cloud. We clarify the applicable technical requirements and access arrangements at the start, then plan the work around the application’s dependencies and the institution’s operating needs.

• Assessment and preparation. Review source code, licences, databases and integrations. Identify the changes needed for deployment in the government cloud.
• Configuration and migration. Configure deployment, access, monitoring and backups within the agreed responsibilities. Transfer the application and the agreed data, content and public archives.
• Testing and transition. Check data and integrations, test restoration and agree the transition window and rollback procedure before launch.

What you receive: The application deployed in the government cloud, migration and test records, operating documentation and an agreed support plan.

We carry out the technical work for government cloud migration. Access and acceptance follow the responsible infrastructure administrator’s procedures, which are confirmed for each project.

Official information about the government cloud migration programme

Modernizing existing applications

We update applications that are difficult to maintain, no longer supported or unable to meet current requirements. The assessment determines which parts can be retained, improved or replaced; a complete rebuild is not the default.

• Updates and remediation. Update dependencies, address identified vulnerabilities and correct the agreed functional or stability problems.
• Functions and integrations. Improve workflows and interfaces, add the required functionality and update connections to other systems.
• Maintainability and handover. Document the application, introduce appropriate automated checks and clarify deployment, access and recovery procedures.

What you receive: Updated application components, verified data and integrations, documented changes and a prioritized plan for any remaining work.

From assessment to launch and support

We agree the work, deliverables, responsibilities and acceptance criteria before implementation. An initial assessment can be a separate engagement when the application or requirements need clarification.

1. Assess and define. For a new solution, review the process and user needs. For an existing application, review the available code, infrastructure, data and documentation.
2. Plan. Set priorities, technical choices, costs and milestones. Agree the institution’s involvement, required access and any maintenance windows.
3. Implement and test. Work in a test environment, verify functionality and integrations, and check the agreed data migration and recovery procedures.
4. Launch and hand over. Monitor the transition, provide documentation and train the responsible team. Record acceptance and any follow-up work.

Maintenance and support after launch

Support can cover application updates, monitoring, backup and restore testing, incident handling and reporting. We agree coverage, response times and responsibilities for the application and infrastructure in the support terms.

Proposals and procurement

We prepare a technical and financial proposal based on the institution’s requirements. It sets out what is included, what the institution needs to provide and how the delivered work will be checked.

• Description of the work and technical requirements
• Deliverables, acceptance criteria and responsibilities
• Cost, milestones and delivery schedule
• Handover, maintenance and support terms

Our services are available through the SEAP electronic catalogue. We clarify the relevant catalogue item and project scope during the proposal stage. The institution determines the procurement procedure that applies to its requirement.