Operations Architecture: The Foundation of ERP Success#
If you're responsible for ERP operations, you know that go-live is just the beginning. The operational architecture you build—the deployment patterns, monitoring strategy, scaling approach, and cost model—will determine whether your ERP enables business success or becomes a perpetual headache.
The uncomfortable truth: Most ERP implementations focus on features and functionality while treating operations as an afterthought. This creates technical debt that compounds over time. The organisation that planned for operational excellence from day one operates at a fraction of the cost and risk of one that didn't.
What's at stake: Poor operational architecture leads to downtime during critical periods, performance degradation as data grows, security vulnerabilities from unpatched systems, and costs that spiral beyond projections. The difference between well-architected and poorly-architected ERP operations can be 3-5x in total cost of ownership.
This guide covers the operations architecture patterns specifically relevant to New Zealand and Australian organisations running cloud or hybrid ERP systems.
---
Cloud Operations Models#
Fully Managed SaaS#
The vendor manages all infrastructure, platform, and application operations.
Examples: NetSuite, Workday, Oracle Fusion Cloud, SAP S/4HANA Cloud (public edition).
Your responsibilities: - User and access management - Configuration and customisation governance - Integration operations - Data governance - Business process management
Vendor responsibilities: - Infrastructure provisioning and maintenance - Platform updates and patches - Security at infrastructure and platform layers - Availability and disaster recovery - Performance management
Key considerations for ANZ: - Data residency: Verify where your data is stored - Support hours: Align with ANZ time zones - Integration latency: Consider distance from ANZ to data centres
Managed Cloud (Single-Tenant)#
Dedicated infrastructure managed by vendor or partner.
Examples: SAP S/4HANA Cloud (private edition), hosted ERP.
Your responsibilities: - Same as SaaS plus: - Custom code management - Update scheduling (with vendor support)
Vendor responsibilities: - Infrastructure provisioning and maintenance - Platform updates (with your scheduling input) - Security at infrastructure and platform layers - Availability and disaster recovery
Self-Managed Cloud#
You manage ERP on cloud infrastructure (AWS, Azure, GCP).
Examples: SAP S/4HANA on AWS, Dynamics 365 F&O on Azure.
Your responsibilities: - Infrastructure provisioning and management - Platform maintenance - Application management - Security across all layers - Availability and disaster recovery - Performance management
Key considerations for ANZ: - Cloud skills availability in ANZ market - Support from cloud providers in ANZ time zone - Data residency options
---
High Availability Architecture#
Availability Patterns#
Active-Passive: Primary system handles all traffic; passive standby ready for failover.
Active-Active: Multiple active instances share traffic; automatic load balancing.
Multi-Region: Systems deployed across multiple geographic regions for disaster recovery.
Recovery Objectives#
RTO (Recovery Time Objective): How quickly must the system be restored?
RPO (Recovery Point Objective): How much data can be lost?
Typical ERP requirements: - Tier 1 (mission-critical): RTO < 4 hours, RPO < 1 hour - Tier 2 (important): RTO < 24 hours, RPO < 24 hours - Tier 3 (standard): RTO < 72 hours, RPO < 24 hours
ANZ Considerations#
Geographic redundancy: - Australian data centres for primary - Consider NZ or secondary Australian region for DR - Factor in data replication costs
Time zone coverage: - Plan for APAC business hours - Consider follow-the-sun support for global operations
---
Performance Management#
Performance Baselines#
Establish baselines for: - Transaction response times - Batch job durations - Report generation times - Integration throughput - Concurrent user capacity
Monitoring Strategy#
Real-time monitoring: - System availability - Response time percentiles - Error rates - Resource utilisation
Trend analysis: - Performance over time - Growth patterns - Seasonal variations
ANZ Performance Factors#
Latency: - Distance from ANZ to data centres - Integration latency for cloud-to-cloud - Consider edge caching for static content
Peak periods: - End of financial year (June/July for AU, March/April for NZ) - Month-end processing - Payroll processing windows
---
Cost Management#
Cloud Cost Categories#
Compute: Virtual machines, containers, serverless.
Storage: Database storage, file storage, backup storage.
Network: Data transfer, CDN, direct connect.
Licensing: ERP subscription, database licensing, third-party tools.
Operations: Monitoring, security tools, management overhead.
Cost Optimisation Strategies#
Right-sizing: Match resources to actual utilisation.
Reserved capacity: Commit to long-term usage for discounts.
Spot/preemptible: Use lower-cost instances for non-critical workloads.
Storage tiering: Move cold data to cheaper storage.
ANZ Cost Considerations#
Currency risk: Most cloud providers price in USD.
Data transfer: Moving data out of cloud regions incurs costs.
Support costs: Premium support for ANZ coverage may be necessary.
---
Monday Morning Action Plan#
This week:
- Document Your Current Architecture: Map your ERP deployment, dependencies, and integration points.
- Establish Availability Requirements: Define RTO/RPO for your ERP system based on business impact.
- Create Performance Baselines: Measure current performance before making changes.
- Audit Your Costs: Review your cloud or hosting costs for optimisation opportunities.
- Check Support Coverage: Verify your support covers ANZ business hours.
---
Conclusion: Operations Architecture Determines ERP Success#
Operations architecture is not an afterthought—it's the foundation that determines whether your ERP enables business success or becomes a source of ongoing problems. For ANZ organisations, the additional considerations of geographic distance, time zone coverage, and data residency make thoughtful operations architecture even more critical.