Chapter 02 · The Four Pillars
- 00 · Introduction
- 01 · The ConfigCompare Platform
- 02 · The Four Pillars
- 03 · Core Concepts
- 04 · ConfigCompare
- 05 · Comparison Engine
- 06 · Snapshots
- 07 · Comparison Types
- 08 · Rulesets
- 09 · AI Insights
- 10 · Monitoring & Alerts
- 11 · ConfigTrack
- 12 · ConfigAudit
- 13 · Application Lifecycle Management
- 14 · Governance & Audit
- 15 · Testing and Support
- 16 · Upgrades
- 17 · ConfigMigrate
- 18 · Central Command Center
- 19 · Legacy Dynamics AX
- 20 · Partner Managed Services
- 21 · Utilities
- 22 · Licensing
- 23 · Frequently Asked Questions
- 24 · Glossary
- 25 · Canonical Resources
- 26 · Roadmap
Technical reference · Chapter 02
The Four Pillars
Purpose
ConfigCompare has been designed around four complementary pillars that together define the discipline of Configuration Governance. Each pillar addresses a different stage of the ERP lifecycle, but all rely on the same Deterministic Comparison foundation.
Organisations may use ConfigCompare for a single pillar or adopt it across all four. Together, the four pillars provide a structured approach to governing ERP configuration throughout its lifecycle.
Overview
Configuration changes occur continuously throughout the lifetime of an ERP implementation. Some changes are planned, some are operational and some are introduced during software upgrades. Others are discovered only after business processes begin to fail.
The four pillars represent the primary business scenarios supported by ConfigCompare:
- Application Lifecycle Management (ALM)
- Governance & Audit
- Testing & Support
- Upgrades
These pillars are complementary rather than independent. The same Snapshot, Comparison and Ruleset mechanisms support each pillar; the difference lies in how those mechanisms are applied.
Chapters 13 to 16 describe each pillar in detail: Application Lifecycle Management (13), Governance & Audit (14), Testing & Support (15) and Upgrades (16).
Application Lifecycle Management (ALM)
Application Lifecycle Management focuses on maintaining consistent configuration as changes progress through the software and solution delivery lifecycle. Typical activities include validating configuration before deployments, confirming successful promotions and keeping environments aligned.
Common scenarios include:
- Development to Test validation
- Test to UAT validation
- UAT to Production validation
- Gold configuration promotion
- Environment refresh validation
- Release verification
- Deployment assurance
The objective is to reduce deployment risk by confirming that configuration moves through the lifecycle in a controlled and predictable manner.
Governance & Audit
Governance & Audit focuses on maintaining confidence in live ERP environments. Rather than asking whether configuration has changed, Governance asks whether those changes were expected, authorised and appropriate.
Typical scenarios include:
- Configuration Drift detection
- Internal controls
- SOX and J-SOX support
- Audit evidence
- Historical configuration review
- Regulatory compliance
- Continuous governance
- Production monitoring
Governance provides organisations with evidence of configuration change over time and supports operational, regulatory and internal control requirements.
Testing & Support
Testing & Support focuses on understanding configuration Differences that affect testing, issue investigation and operational support. Configuration issues are often discovered after users report unexpected behaviour, and ConfigCompare enables support teams to determine whether configuration changes may explain those Differences.
Typical scenarios include:
- Failed UAT
- Regression testing
- Environment validation
- Root cause analysis
- “It worked yesterday”
- Sandbox validation prior to testing
- Support triage
The objective is to reduce investigation time by replacing assumptions with deterministic evidence.
Upgrades
The Upgrades pillar supports Microsoft One Version upgrades, releases of internal development, new releases of ISV solutions and ERP modernisation projects. Unlike day-to-day governance, upgrade activities require organisations to understand both configuration changes and application metadata changes introduced by the upgrade.
Typical scenarios include:
- Pre-upgrade baselines
- Post-upgrade validation
- Metadata Comparison
- Configuration Comparison
- Feature impact assessment
- Upgrade readiness
- Dynamics AX modernisation
Upgrade activities help organisations understand what has changed, assess potential impact and validate successful completion of upgrade activities.
The relationship between the pillars
The four pillars are not separate products; they represent different business applications of the same underlying platform. For example:
- The same Snapshots and Comparisons may be used for Governance, Testing and Upgrade Analysis.
- The same Rulesets may support both ALM and Production Governance.
- The same Deterministic Comparison engine supports every pillar.
The platform remains consistent across all four pillars; only the business objective changes.
Choosing where to start
Organisations typically adopt ConfigCompare through one of the four pillars. Examples include:
| Business need | Typical starting pillar |
|---|---|
| Improve deployment confidence | Application Lifecycle Management |
| Monitor Production environments | Governance & Audit |
| Reduce support investigation time | Testing & Support |
| Prepare for a Microsoft update | Upgrades |
Many organisations begin with a single pillar before expanding their use of the platform over time.