2.3: Project Phases

Following the establishment of core principles and the modernisation approach detailed in Chapter 2, this chapter outlines the proposed phased implementation plan for the project. This plan is designed to deliver ArcGIS Enterprise 11.4 on Microsoft Azure through a sequence of manageable stages, ensuring iterative value delivery, risk mitigation and the progressive build-out of a resilient, enterprise-grade GIS platform.

2.3.1. Overview of Phased Implementation¶

It is recommended that the new eMap platform be implemented through a series of defined phases and stages. This iterative approach is fundamental to managing complexity, mitigating risks and incorporating learnings at each step of the deployment. The sequence prioritises establishing foundational governance and automation before scaling the platform and introducing advanced resilience features. This methodology ensures that each stage delivers tangible business value and operational insights, systematically building towards the complete, modernised GIS platform.

The implementation philosophy guiding this phased approach is based on the following key tenets:

• Foundation First: The initial phase focuses on establishing a robust data governance framework. This is critical as it informs all subsequent technical implementations and ensures sustainable, quality-focused data management from the project's inception.
• Iterative Value Delivery: Each phase and stage is designed to deliver specific, measurable capabilities, allowing stakeholders to see progress and realise benefits incrementally.
• Risk Management: By addressing simpler components and foundational elements before more complex ones, risks are identified and mitigated early. Core capabilities are validated before advanced features such as High Availability (HA) and Disaster Recovery (DR) are introduced.
• Cost-Controlled Progression: Resource deployment is aligned with the requirements of each phase, starting with essential components at an appropriate scale and progressively adding capacity and resilience as justified by business needs and usage.
• Automation as a Cornerstone: Infrastructure as Code (IaC) using OpenTofu and Configuration Management are embedded from the outset, ensuring consistency, repeatability and operational efficiency throughout all phases.
• Continuous Validation and Testing: Rigorous testing, including functional, load, HA, DR and security testing, is integrated into each phase to ensure quality and operational readiness.

The implementation is structured into three primary phases:

Phase I: Data Governance Framework¶

The initial phase establishes the principles, policies and strategic decisions for data management, storage allocation and workflow development. It ensures that robust governance practices underpin all subsequent technical work, defining how data is classified, stored and managed throughout its lifecycle.

Phase II: Technical Implementation¶

This phase focuses on the iterative build, testing and enhancement of the new eMap platform's technical infrastructure and ArcGIS Enterprise software capabilities. It progresses through distinct stages, each delivering an increasing level of functionality, scalability and resilience:

• MVP Stage (Minimum Viable Product): Deploys core ArcGIS Enterprise functionality (Portal, Server, Data Store, Web Adaptors on Azure App Service) in Development (DEV), User Acceptance Testing (UAT) and a single-region Production (PROD) environment (Melbourne). This stage validates basic user access, service publishing and foundational automation scripts.
• Bronze Stage (Automatic Scaling): Implements and validates automatic scaling for ArcGIS Server (via VM Scale Sets) and Web Adaptor App Services within the PROD environment to optimise resource utilisation and performance under varying loads.
• Silver Stage (Optional, High Availability): Enhances the PROD environment by implementing high availability for all critical components to mitigate hardware failures and ensure resilience against single points of failure.
• Gold Stage (Optional, Disaster Recovery): Establishes disaster recovery capabilities for the PROD environment, enabling failover from Melbourne (primary) to Sydney (DR region, utilising a pilot light model). This stage involves inter-region data replication and global traffic management.
• Platinum Stage (Optional, Specialised Roles): Provides a framework for incrementally adding specialised ArcGIS Server roles (e.g., GeoEvent Server, Image Server) based on validated business needs, ensuring their integration into the existing HA/DR frameworks.

Phase III: Transition & Legacy Decommissioning¶

The final phase concentrates on the systematic migration of users, data and services from the existing eMap system to the new eMap platform. Following successful migration and validation, the legacy eMap environment will be formally decommissioned.

Each phase and stage within this implementation plan is designed to ensure a controlled and logical progression, building upon previous accomplishments. This approach facilitates continuous learning, adaptation and stakeholder engagement.

2.3.2. Governance Gates and Phase-based Deliverables¶

To ensure successful implementation, review and approval checkpoints, known as governance gates, are recommended to be established at the conclusion of each major phase and stage of the project. These gates serve to validate that deliverables meet the required standards, objectives are achieved and stakeholders are in agreement before the project progresses to subsequent activities.

Phase I: Data Governance Framework Deliverables¶

Progression from Phase I requires approval based on the satisfactory completion and acceptance of foundational governance documents.

The key sign-off criteria include:

Data Storage Strategy¶

Endorsement of the Data Storage Strategy, which includes the finalised decision framework for allocating data between user-managed Enterprise Geodatabase and the Esri-managed ArcGIS Data Store, as well as the Azure PaaS resource allocation plan for different data categories.

Workflow Patterns¶

Validation and approval of the standard Workflow Development Patterns, including guidelines for VertiGIS Studio Workflow integration, ensuring alignment with data governance and architectural principles.

Monitoring Framework¶

Sign-off on the Monitoring and Observability Framework definition, including Key Performance Indicators (KPIs), health metrics and the strategy for integration with Azure Monitor and Application Insights.

Minimum Viable Product Stage (MVP) Deliverables¶

Advancement from MVP Stage should be contingent upon the successful deployment and validation of the new eMap platform.

Successful User Acceptance Testing¶

Confirmation from designated business users and stakeholders that the core platform functionality deployed in the UAT environment meets the agreed-upon requirements for the MVP. This includes validating user access, service publishing from user-managed Azure PostgreSQL and the functionality of hosted services via the ArcGIS Data Store.

Validated Infrastructure as Code (IaC) and Configuration Management (CM) Scripts¶

Verification that the OpenTofu scripts for infrastructure provisioning and the Configuration Management scripts for VM and software setup are functional, repeatable and have successfully deployed the DEV, UAT and PROD (Melbourne) environments for the MVP.

Operational Readiness Documentation¶

Approval of initial operational handover documentation, including basic support procedures and monitoring guidelines for the MVP.

Bronze Stage (Automatic Scaling) Deliverables¶

To complete Bronze Stage, the successful implementation and validation of automatic scaling capabilities within the Production environment are required.

Demonstrated Automatic Scaling Behaviour¶

Successful demonstration of the automatic scaling capabilities of Production components, specifically the ArcGIS Server Virtual Machine Scale Sets (VMSS) and the Web Adaptor Azure App Services, under simulated load test conditions. This includes verifying that resources scale out and scale in according to defined rules.

Validated Monitoring of Scaling Events¶

Confirmation that monitoring systems are accurately capturing and reporting scaling events and that alerts related to scaling thresholds or issues are functioning correctly.

Silver Stage (Intra-Region High Availability - Optional) Deliverables¶

Progression beyond Silver Stage should validate the high availability (HA) features implemented within the Production environment in Melbourne.

Successful Component-Level HA Failover Tests¶

Documented evidence of successful failover tests for all critical components configured for HA within the PROD environment. These tests must demonstrate minimal or no data loss and meet predefined recovery time objectives for intra-region failover.

Verification of Resilience against Simulated Outages¶

Confirmation that the platform remains operational and services remain accessible during simulated outages, validating the effectiveness of the deployment strategy.

Gold Stage (Inter-Region Disaster Recovery - Optional) Deliverables¶

To conclude Gold Stage, the disaster recovery (DR) capabilities should be tested.

Successful End-to-End DR Failover and Failback Drill¶

Execution of a successful end-to-end DR drill, simulating a full failure of the Melbourne (primary) region and failover to the Sydney (DR) region, followed by a successful failback to Melbourne. This includes testing the Global Server Load Balancer (GSLB) redirection, data replication and restoration processes and application functionality in the DR site.

Validation of Recovery Point Objective (RPO) and Recovery Time Objective (RTO) Targets¶

Confirmation that the DR drill meets the pre-defined RPO and RTO targets for critical services and data, ensuring business continuity requirements are satisfied.

Platinum Stage: (Specialised Roles - Business Dependent) Deliverables¶

For each specialised ArcGIS Server role (e.g., GeoEvent Server, Image Server) implemented in Platinum Stage, specific deliverables should be defined:

Validated Business Value Delivery¶

Confirmation from business stakeholders that the deployed specialised component delivers the anticipated business value and meets the functional requirements for which it was intended.

Successful Integration into HA/DR Framework¶

Verification that the new specialised component is successfully integrated into the existing High Availability (HA) and Disaster Recovery (DR) frameworks and that it meets the platform's overall resilience and recovery objectives through specific HA/DR testing for that component.

Phase III: Transition & Legacy Decommissioning Sign-off¶

The final phase of the project requires sign-off indicating the successful transition to the new eMap and the complete retirement of the legacy eMap system. Sign-off criteria include:

Sign-off on Successful Migration of All Critical Data and Services¶

Formal acceptance from business owners and data stewards that all critical data, services and associated functionalities have been successfully migrated from the legacy eMap system to the new eMap platform, with data quality and functional parity validated.

Verified Decommissioning of legacy eMap System¶

Confirmation that all components of the legacy eMap system have been securely and completely decommissioned, with resources reclaimed and no remaining dependencies. This includes verification that all users have transitioned to the new eMap platform.

These governance gates and their associated deliverables provide a structured framework for managing the project, ensuring that each stage is completed to a high standard and that the project remains aligned with its strategic objectives.