Infrastructure responsibilities
Agree which organisation is responsible for servers, storage, operating environment and connected services.
- Infrastructure
- Database requirements
- Network access
- Backups
- Updates
- Support access
When self-hosting may be considered
Self-hosting may be relevant where an authority has internal hosting policies, existing infrastructure standards, data governance requirements, integration constraints or IT operational preferences that make customer-managed infrastructure the right deployment model.
The decision should be made with the products, modules, users, data volumes, integration requirements and support responsibilities in mind.
What needs to be agreed
Server and database requirements
Confirm technical requirements for the product, modules, users, data and expected usage.
Network and access arrangements
Plan connectivity, administrator access, support access and any customer-side access controls.
Backups and monitoring
Agree monitoring, backup and recovery responsibilities under the service model.
Updates and maintenance
Define how updates, patches, maintenance windows and configuration changes will be handled.
Integration responsibilities
Clarify responsibilities for third-party systems, data feeds, extracts and internal dependencies.
Support access
Agree how StatMap can investigate incidents and support the application where customer infrastructure is involved.
Migration and test environments
Plan data migration, test environments, acceptance activity and go-live responsibilities.
Support and maintenance
The support model for self-hosted services should be agreed before implementation, including responsibilities for infrastructure, application support, updates, access and incident investigation.
Self-hosting can work well when the authority and supplier responsibilities are clear. Issues may involve application behaviour, customer infrastructure, network access, data, integrations or local configuration, so the agreed investigation route matters.
Support Model
Define support arrangements, roles and escalation routes.
Support Desk
Understand how customers raise issues and provide investigation detail.
Service Level Agreement
Confirm service-level and support commitments for the agreed deployment model.
Technical requirements
Technical requirements should be confirmed for the product, modules, users, data volumes and integration requirements involved. Old server specifications should not be relied on without review.
Discuss self-hosting requirements
Talk to StatMap about self-hosting requirements for GIS, gazetteer, case-management, public portal and spatial data services.