Avennorth
Avennorth/Architect
06Solution Architecture

Architect

Design validated against what your environment actually is.

Architect applies CSDM compliance validation, tech debt roadmap generation, and solution design impact simulation directly against the live GPS data fabric. Every indicator is automated from live discovery — no assessments, no surveys, no spreadsheets. Enterprise architecture grounded in what your environment actually is right now.

ARCHITECT — CSDM COMPLIANCE ENGINELIVE
CSDM SCAN
847 CIs evaluated
0%
compliant
checkout.service
Application Service
31%
web-server-01
Server
67%
orders.application
Application
88%
orders.database
Database
94%
core-switch.net
Network Gear
58%
2 PASS2 GAP1 CRITICAL
TECH DEBT ROADMAP
Bearing-ranked · risk-ordered
01 checkout-svc relationships staleCRITICAL
Effort: 2dScore: 31
02 web-01 undocumented attrsMEDIUM
Effort: 4dScore: 67
03 core-sw CSDM class gapsMEDIUM
Effort: 1dScore: 58
1 design pending simulation
checkout-v2 → 3 services affected
CSDM
Compliance scored continuously
Alignment validated against live discovery data — not a point-in-time assessment that ages immediately
Auto
Dependency maps generated
Application-to-infrastructure bindings built from Pathfinder relationships — no manual architecture survey
Measured
Tech debt roadmaps
Roadmap priorities are ranked by Bearing health scores and remediation cost — not by who argues loudest
0
Manual architecture surveys
Architect derives structure from the fabric — environment state is discovered, not declared
The Problem

Enterprise architecture fails when the maps it's built on are wrong.

EA programmes develop reference architectures, run CSDM alignment projects, and build roadmaps — all from data that's months or years out of date. CSDM gaps go undetected until audit. Roadmaps are built from opinions about tech debt, not measured scores. When a solution design is proposed, its impact is estimated by the team that wants to build it. Architect changes the foundation: every EA deliverable is generated from and validated against a live, discovered environment.

CSDM Compliance

Every CI scored. Every relationship validated. Continuously.

Architect evaluates your live CMDB topology against CSDM alignment requirements — not from a point-in-time export, but from the same discovered data fabric that updates with every Pathfinder cycle. Gaps open? You'll know immediately.

Compliance scored per CI

Not per application or per environment — every Configuration Item gets its own score.

Relationship class gaps

Missing CSDM relationship classes are detected at the relationship level, not inferred from CI state.

Drift detected on change

When Pathfinder discovery updates a CI, Architect re-scores immediately — no scheduled scan.

Audit-ready evidence chain

Every score is traceable to a discovered attribute via the GPS bitemporal fabric.

CSDM COMPLIANCE MAP — 847 CIs
● PASS● GAP● CRITICAL
Solid line = PASS relationship · Dashed = GAP or CRITICAL67.6% compliant — 2 remediation items active
How It Works

Four steps, end to end.

01

Ingest topology and health from the fabric

Architect draws continuously from Pathfinder's discovered relationships and Bearing's health scores. No manual data collection, no architecture survey — the environment describes itself.

02

Score CSDM compliance per CI and relationship

Every CI and relationship is evaluated against CSDM alignment requirements. Gaps are identified and ranked. Compliance posture is tracked over time — drift is detected as it happens, not at the next audit.

03

Generate tech debt roadmap from health data

Bearing health scores are converted into a prioritised remediation roadmap — ranked by business risk, remediation cost, and dependency sequence. The roadmap updates automatically as the environment changes.

04

Validate proposed designs against live topology

Before a solution design is approved, Architect simulates its impact against the current topology. Blast radius, dependency conflicts, and CSDM alignment gaps in the proposed state are surfaced before the first line of configuration.

DESIGN SIMULATION — checkout-v2SIMULATING
CURRENT TOPOLOGY
checkout-service
Application Service
CRITICAL
web-server-01
Server
GAP
orders.app
Application
PASS
orders.database
Database
PASS
PROPOSED CHANGEScheckout-v2
checkout-v2
Proposed replacement
NEW
checkout-service
To be decommissioned
REMOVED
web-server-01
Direct dependency
BLAST
orders.app
Transitive dependency
BLAST
orders.database
Not affected
PASS
SIMULATION FINDINGS
CSDM GAP
checkout-v2 → web-server-01 missing rel_class_depends_on
BLAST RADIUS
3 services affected · 2 direct · 1 transitive dependency
DESIGN VERDICT
Blocked — resolve CSDM gap before raising implementation ticket
Design Simulation

Validate your design before a single ticket is raised.

Architect simulates proposed solution designs against the current live topology. Before the change hits the CAB, you know the blast radius, the CSDM alignment gaps in the proposed state, and any dependency conflicts that would surface at implementation.

Topology-aware blast radius

Impact is calculated from the live Pathfinder relationship graph — not from architecture diagrams that haven't been updated since the last major release.

CSDM alignment pre-check

Proposed relationship classes are validated against CSDM requirements before implementation. Gaps are surfaced at design time, not at post-implementation review.

Design blocked until resolved

Simulations that produce critical CSDM gaps or unacceptable blast radius are flagged before they reach the implementation team — enforcement built into the design process.

Who It's For

Built for the people who own this problem.

01

Enterprise Architect

Architecture deliverables grounded in the actual environment — not a snapshot that's outdated before it's published.

02

IT Strategy & Planning

A tech debt roadmap ranked by measured risk and cost — not by internal politics or loudest voice.

03

CIO

Continuous CSDM compliance scoring so they know the organisation's alignment posture without waiting for an annual assessment.

04

ServiceNow Architect / Implementation Lead

Design validation against live topology before committing to implementation scope.

Why Architect

Built different.

Four capabilities you won't find assembled anywhere else.

01

Live CSDM compliance validation

Continuous, not point-in-time.

CSDM compliance is scored against the live GPS data fabric, not a snapshot taken at the last assessment. As the environment changes, the compliance posture changes with it — gaps are detected and surfaced as they open, not six months later.

02

Discovery-grounded dependency maps

No manual architecture survey.

Application-to-infrastructure bindings are derived from Pathfinder's observed relationships — not from architecture diagrams that haven't been updated since the last migration. If a dependency exists, Architect sees it.

03

Bearing-ranked tech debt roadmap

Measured risk. Not opinions.

Tech debt remediation priorities are derived from Bearing's five health dimensions — not from who has the most seniority in the architecture meeting. Every priority is traceable to a scored CI and a cost estimate.

04

Pre-approval design simulation

Validate before you build.

Proposed solution designs are simulated against the current topology before they reach the CAB or implementation team. CSDM alignment gaps, blast radius implications, and dependency conflicts are surfaced at design time — not at rollout.

POWERED BY INTELLIGENCE

Indicators and intelligence,
grounded in this product.

HOW INTELLIGENCE REASONS HERE

Every indicator below is automated from live Pathfinder discovery — not produced by an assessment, a survey, or a consultant workshop. There is no questionnaire. There is no scoring spreadsheet. The environment describes itself, and Architect reads that description continuously. Intelligence then evaluates competing design outcomes against those live indicators — simulating blast radius, class coverage gaps, and pattern violations — and surfaces only the designs that survive all falsification checks.

CSDM COMPLIANCE
  • CSDM compliance score by CI class
  • Relationship class coverage
  • Discovery-grounded compliance %
  • Real-time gap detection
EA CAPABILITY INDICATORS
  • Application rationalization priority
  • Architecture pattern score
  • Integration architecture health
  • Information model completeness
DESIGN INTELLIGENCE
  • Pre-approval simulation confidence
  • Blast radius of proposed change
  • Design verdict (pass / gap / critical)
  • CSDM delta from current state
STAKEHOLDER ALIGNMENT
  • EA governance score
  • Decision approval velocity
  • Architecture debt by stakeholder domain
  • Rationalization alignment index
STAKEHOLDER SIGNALS
Enterprise Architect
CSDM compliance score, design verdict, blast radius per proposal
EA Governance Board
Pattern violations, rationalization alignment, approval readiness
CIO
Portfolio health, EA capability maturity, debt by domain
Solution Architect
Pre-approval simulation results and CSDM delta
Competitive Comparison

How Architect stacks up.

29 capabilities across CSDM governance, architecture intelligence, business & application intelligence, portfolio & cost, and delivery model.

CAPABILITY
ARCHITECT
by Avennorth
ServiceNow EA (APM)
SAP LeanIX
Ardoq
CSDM Compliance & Governance
Continuous CSDM compliance scoring
CI alignment evaluated on every discovery cycle — not on demand, and not on a scheduled batch job that lags by the run cadence
Rescored on every Pathfinder cycle automatically
CMDB BATCH
NOT NATIVE
NOT NATIVE
Architecture pattern enforcement
Proposed designs validated against approved CSDM structural patterns before they reach CAB — not just documented as standards
CSDM patterns auto-validated in every design simulation run
TEMPLATES
MANUAL
MANUAL
Relationship-level class validation
CSDM rel_class attribute checked on every discovered relationship, not just on CI records themselves
Validates rel_class on every discovered relationship
SCRIPTED
NOT NATIVE
NOT NATIVE
Real-time CSDM gap detection
Gaps surface the moment a CI changes — ServiceNow's own CMDB health scoring runs on scheduled batch jobs, so its gaps lag by the job cadence
Gap detected on CI change, zero lag
BATCH JOBS
NOT NATIVE
NOT NATIVE
Discovery-grounded compliance data
Compliance scored against live observed topology from Pathfinder — not declared CMDB entries (default 60-day staleness) or hand-maintained fact sheets
Sourced from live Pathfinder topology — not stale declarations
60-DAY STALE
FACT SHEETS
IMPORTED
Information model governance
CI attribute completeness scored against the CSDM data model per CI class — gaps surfaced and prioritized automatically
Attribute gaps scored per CI against CSDM class definitions
CMDB HEALTH
MANUAL
MANUAL
Architecture Intelligence & Design
Pre-approval design simulation against live topology
Proposed designs validated against the live environment before CAB. ServiceNow only analyzes impact on CIs that already exist; LeanIX and Ardoq simulate against a hand-modeled inventory
Simulates the proposed design against the live Pathfinder graph
EXISTING CIs ONLY
MODEL ONLY
MODELED
Change impact analysis on live dependencies
Downstream blast radius scoped from the same live topology used by Contour and Vantage — competitors traverse an imported or hand-built model, not observed reality
Traverses the full live dependency graph for every proposed change
CMDB IMPACT
MODELED
MODELED
Service continuity dependency mapping
BC/DR dependency chains mapped from live behavioral topology. ServiceNow needs Service Mapping (ITOM Visibility); the EA tools need a manual DR-questionnaire campaign
BC/DR chains mapped from live Pathfinder data — zero surveys
ITOM SVC MAP
MANUAL INPUT
MANUAL INPUT
Health-ranked tech debt roadmap
Remediation order derived from measured Bearing health across security, stability, age, and config debt — competitors rank from manual indicators or self-assessed scores
Ranked by Bearing's five measured health dimensions — not opinion
APM SCORING
SELF-ASSESSED
SURVEY
Reference architecture & standards validation
Approved standards validated against what is actually running — non-standard tech flagged from live discovery. Competitors document standards and govern them by hand; ServiceNow's TRM check is advisory, not enforced
Standards validated against live discovered tech, not just documented
TRM ADVISORY
MANUAL GOV
MANUAL GOV
Zero-survey environment understanding
Environment structure derived entirely from Pathfinder's behavioral discovery — no architecture questionnaires, no CI-owner interviews, no fact-sheet subscriptions
Fully derived from Pathfinder data — no questionnaires
REQUIRED
SURVEYS
SURVEYS
Business & Application Intelligence
Business capability mapping
Capability-to-application relationships derived from live behavioral discovery — which applications actually deliver which capabilities. ServiceNow ingests a reference framework (e.g. APQC) and links apps by hand; LeanIX and Ardoq model the map manually on fact sheets
Capability map grounded in observed app-to-service relationships — not hand-modeled
APQC IMPORT
MANUAL MODEL
MANUAL MODEL
Business capability intelligence
Each capability scored for health, risk, and redundancy from measured Bearing health and live usage — not a heat map rolled up from manually entered or 1–5 self-assessed inputs
Capability health measured from Bearing + live usage, continuously
MANUAL ROLLUP
SURVEY-BASED
SURVEY-BASED
Application usage intelligence
Real usage observed by Pathfinder for every application — actual connection frequency, active consumers, idle detection. ServiceNow's EA usage is a self-reported banded dropdown (e.g. 100–250 users); observed SaaS usage needs the separate SAM product. LeanIX and Ardoq have no runtime usage at all
Actual usage observed via eBPF — not a self-reported band
MANUAL FIELD
NOT AVAILABLE
NOT AVAILABLE
Application performance & stability signals
Proactive behavioral performance and stability telemetry feed rationalization and roadmap decisions. ServiceNow only infers this reactively from linked ITSM incidents unless you also license ITOM Health / AIOps; the EA repositories have no runtime signal at all
Proactive performance/stability from live telemetry — not reactive tickets
REACTIVE ITSM
NOT AVAILABLE
NOT AVAILABLE
Business criticality intelligence
Criticality derived from observed dependency centrality and real usage — not a rated field or a business-impact questionnaire answered once and left to age
Criticality from observed dependency load and real usage
RATED FIELD
SURVEY
SURVEY
Organization & ownership intelligence
Team, owner, and consumer relationships inferred from observed activity — who actually operates and uses each application, not a declared org chart or a directory import that drifts
Ownership inferred from observed activity — not declared org charts
MANUAL
MANUAL
DIRECTORY
Portfolio, Cost & Rationalization
Service portfolio management
Full GPS service graph used as live source of truth for portfolio governance — not a manually maintained catalogue or an imported fact-sheet inventory
GPS service graph as live source for portfolio governance
NATIVE (SPM)
MANUAL DATA
MANUAL DATA
Application rationalization
Redundant, overlapping, or low-health apps ranked as rationalization candidates from measured health and observed usage. Competitors run the same TIME model, but on self-reported functional/technical fit scores
Ranked by measured Bearing health and live usage — not self-reported fit
MANUAL FIT
SELF-REPORTED
SURVEYED FIT
Technology lifecycle & obsolescence risk
EOL/EOS matched against discovered CIs continuously — coverage isn't limited to a vendor catalogue, and custom or unrecognized tech doesn't silently fall through. ServiceNow's enrichment needs the SAM product and only covers recognized products
EOL/EOS matched to discovered CIs — not catalogue-limited
SAM CATALOG
TRC CATALOG
MANUAL DATES
Application cost & TCO intelligence
Cost per application built from discovered assets and observed usage via the Assets fabric — not allocated GL buckets keyed in by hand or imported from a finance sheet
TCO from discovered assets and observed usage — not allocated buckets
ALLOCATED
MANUAL / IMPORT
MANUAL / IMPORT
Cloud & SaaS spend visibility
SaaS and cloud footprint surfaced from observed behavior via the Assets fabric — including shadow IT no expense feed sees. ServiceNow automates this across Cloud Cost Management + SAM (two more products); Ardoq only imports it
SaaS surfaced from behavior, including shadow IT — not just expense feeds
CCM + SAM
SMP
IMPORTED
Integration architecture mapping
API and middleware dependency relationships captured automatically by Pathfinder. ServiceNow discovers connections via Service Mapping (ITOM); the EA tools import an integration inventory or model interfaces by hand
Integration points discovered by Pathfinder — zero manual mapping
ITOM SVC MAP
CONNECTORS
IMPORTED
Capability-based transformation roadmapping
Transformation roadmaps sequenced by measured health and live dependencies — competitors plan roadmaps natively too, but over a manually maintained current-state model
Roadmap sequenced by measured health and live dependencies
MANUAL BASE
MANUAL BASE
MANUAL BASE
Platform, Audit & Delivery Model
Single-fabric delivery — one product, not a suite
Architect delivers every capability above as one product on the unified GPS fabric. Matching it in ServiceNow means licensing and integrating ITSM, EA (APM), SPM, ITOM Visibility, ITOM Health, AIOps, BCM, SAM and HAM — nine products, plus the CSDM data-quality and integration tax between them. LeanIX and Ardoq each need their core platform plus SaaS-management and integration add-ons
One product on one fabric — no module stitching, no integration tax
9+ PRODUCTS
3+ PRODUCTS
2+ PRODUCTS
Native ServiceNow CI population
Discovered CIs and relationships written directly into ServiceNow HAM / SAM / CMDB tables via the patent-protected integration layer — LeanIX syncs via integration, Ardoq only imports one-way
GPS fabric writes to native SN tables — patent-protected
NATIVE
CMDB SYNC
IMPORT ONLY
Bitemporal audit trail
Every CI state immutably recorded — architecture posture verifiable at any past timestamp for compliance, audits, or post-incident review. No EA tool in this class offers it
Hash-chained, cryptographically verifiable at any past timestamp
NONE
NONE
NONE
Cross-product intelligence chain
CSDM posture and architecture state flow automatically into executive reporting and compliance products downstream — standalone EA tools are islands
Feeds Compass and Trust natively via GPS fabric
WITHIN SPM
STANDALONE
STANDALONE
COVERAGE (FULL OR PARTIAL)
29 / 29
23 / 29
18 / 29
20 / 29
Full native support
Partial / manual / integration required
Not available

All third-party product names and logos are trademarks of their respective owners and are used for identification and comparison purposes only. Comparisons are based on publicly available product documentation as of 2025–26 and reflect Avennorth's good-faith assessment; they do not imply affiliation, sponsorship, or endorsement.

Intelligence Chain

Where Architect fits in the platform.

Architect is the EA layer of the platform. Its outputs are only as good as the discovery and health data underneath — which is why it's most powerful in a full Pathfinder + Bearing + Contour deployment.

Get started

See Architect in action.

Thirty minutes. A live environment. Real findings from your own data.

Book a Demo