Deployment model
Agree whether cloud hosting is appropriate for the products, modules, users and operational model involved.
- Deployment model
- Data requirements
- Access controls
- Resilience planning
- Support arrangements
- Implementation
Hosting planned around the service
Cloud hosting may be considered for StatMap GIS and web mapping, gazetteer management, case-management systems, public portals, spatial data services, integrations, reporting and operational access.
The right hosting approach depends on the agreed deployment model, customer requirements, data responsibilities, integration needs and support arrangements. Specific hosting, security, resilience and service commitments should be confirmed for the project rather than assumed from old public material.
What hosting discussions should cover
Data and integration requirements
Review datasets, interfaces, extracts, public services and third-party systems that need to be connected.
User access
Plan how authorised users, administrators and support contacts will access the service.
Resilience and backup expectations
Agree backup, resilience, recovery and monitoring expectations for the project and service agreement.
Security and access controls
Confirm security, access-control and data-handling arrangements during implementation.
Support arrangements
Define support routes, responsibilities, escalation routes and change processes under the agreed support model.
Maintenance and updates
Agree how product updates, configuration changes and maintenance windows should be handled.
Customer responsibilities
Clarify customer-side responsibilities such as contacts, data ownership, testing and connected systems.
Implementation planning
Plan migration, configuration, integration, training and acceptance activity before go-live.
Cloud hosting and StatMap services
Hosting decisions should be considered alongside the products and services being implemented. A GIS-only project may have different needs from a case-management or public portal implementation, and data services or integrations can add additional responsibilities.
eVO Software Platform
Understand the shared platform behind StatMap GIS, case-management, portal and workflow products.
Corporate GIS
Plan hosting around web mapping, spatial layers, editing and internal access.
HorizoNext
Consider case-management records, documents, workflows and public-facing options.
Data Services
Review mapping, address data, migration, extracts and integration requirements.
Support Model
Agree support responsibilities, routes and escalation processes.
Procurement information
Confirm current procurement routes before relying on framework references.
Security, resilience and service commitments
Security, resilience, backup and support arrangements should be agreed for the project and reflected in the relevant service agreement. Current provider, region, certification, uptime, backup and disaster-recovery details should be confirmed with StatMap for the specific service.
Discuss hosting for your StatMap services
Talk to StatMap about hosting options for GIS, gazetteer, case-management, public portal and spatial data services.