Customer guide
ARC by Dynacore — Access. Reason. Change.
Your organization has chosen ServiceNow as a strategic platform. The starting point is to make good use of that investment.
ServiceNow already provides substantial capabilities for enterprise architecture, operational information, workflows, integration and external data. Workflow Data Fabric extends this further by connecting, contextualizing and governing information across enterprise sources.
ARC does not seek to replace those capabilities or create another universal platform.
ARC becomes relevant when a consequential change depends on architecture knowledge whose meaning, authority or lifecycle legitimately remains outside ServiceNow — for example in specialist architecture repositories, historical environments, interface definitions, documents or accountable expert knowledge.
The practical question is:
What additional knowledge does this decision require, and how can we use it without creating another competing version of the enterprise?
ARC is Dynacore’s offering platform. Our operations-first approach makes distributed architecture knowledge usable for controlled change. We start with the platforms and knowledge the organization already has and extend outward only where a real decision requires additional context.
ARC develops from capabilities Dynacore already delivers into a broader approach for connecting architecture knowledge to change.
| Delivery status | What this means for customers |
|---|---|
| Established delivery: Run | Dynacore operates and supports architecture environments. Our current operational experience is concentrated on Sparx Systems environments, including EA repositories, WebEA publishing and Prolaborate collaboration. |
| Established access services; preservation scoped per environment | Dynacore provides access services for architecture environments. Where a repository is being retired, preservation is scoped against the available source material, exports, structure, permissions and required user experience before the deliverable is agreed. |
| Scoped delivery: Connect and Insight | Selected architecture sources can be related and analysed for a defined question or change. Interfaces, mappings, permissions and deliverables are established for each engagement rather than assumed to be available through a universal connector catalogue. |
| Development direction: Automate and Transform | ARC is developing toward more reusable context across sources, evidence-linked reasoning and reviewed workflows that shorten the path from architecture knowledge to controlled action. These are progressively developing capabilities, not a promise of a complete autonomous architecture platform. |
A ServiceNow-related engagement therefore begins with an assessment of the environment that already exists. Available interfaces, information ownership, mappings, access conditions and maintenance responsibilities must be understood before a connection or integration is committed.
Your organization is moving away from an older EA platform. ServiceNow supports the current portfolio and operational environment, but the retiring repository contains design rationale, relationships, diagrams or historical models that still matter.
Keeping the old product running indefinitely is one option. Losing practical access to the knowledge is another.
Neither needs to be the default.
The first step is to identify what must remain intelligible after retirement and assess what can be preserved from the available source. The scope establishes which objects, relationships, diagrams and supporting information can be retained, how they will be accessed and any known losses or limitations.
Engagement scope today: a preservation and access engagement defined against the actual source environment.
Success means: authorized users can retrieve and interpret the agreed architecture knowledge after the original platform has been retired.
The preserved material remains identifiable as historical knowledge rather than silently becoming the asserted current state. If a later decision requires that knowledge alongside current ServiceNow information, such a connection is assessed and scoped separately.
A portfolio review identifies an application for retirement, replacement or consolidation. ServiceNow may already provide substantial information about the application, ownership, lifecycle, services and operational environment.
But the decision may also depend on architecture knowledge maintained elsewhere: a capability relationship, target architecture, interface contract, exception, design decision or accountable interpretation.
Start with what ServiceNow already knows.
Then identify the unanswered questions:
Engagement scope: an architecture assessment using agreed information supplied from ServiceNow and selected external sources. Data access, any integration and the assessment deliverables are confirmed during scoping.
Success means: reviewers can trace the assessment to its sources, understand unresolved gaps and judge whether the evidence is sufficient for the decision.
The established application owner, architecture governance and change processes retain responsibility for the decision.
Moving information between architecture tools is not only an export-and-import problem.
Relationship types, identifiers, lifecycle states, model semantics and historical context may differ between environments. A technically successful transfer can therefore preserve records while changing their meaning.
A bounded engagement starts with a representative set of architecture information. The teams establish mappings, identify what can transfer faithfully, make losses or transformations explicit and review the result before extending the scope.
Engagement scope today: source compatibility assessment and a tailored transfer or integration engagement.
Success means: the organization understands what has been preserved, transformed or lost before relying on the new representation.
Where ServiceNow is part of the target environment, it can retain its established role throughout the transition. Information does not need to become ServiceNow-owned merely because it needs to participate in ServiceNow-supported decisions or workflows.
Connecting information should not make its authority ambiguous.
For each important piece of architecture knowledge, establish:
These distinctions matter because a synchronized field, imported object or AI-generated relationship does not become authoritative merely because it appears in a strategic platform.
ARC should not reconstruct context that ServiceNow already provides well.
Where ServiceNow is authoritative, start there.
Where a decision requires additional architecture knowledge, connect only what the decision needs and preserve the identity and authority of the external source.
Start with the context ServiceNow already provides. Add the specialist, historical or externally authoritative architecture evidence the decision requires, with clear sources, responsibilities and review.
The objective is not to create a second portfolio repository, another universal data model or a replacement integration layer.
It is to establish enough trustworthy architecture context for the change at hand.
ARC is worth exploring when a concrete architecture problem crosses the boundaries of the environment you already have.
Typical signals include:
Where your existing ServiceNow capabilities and delivery arrangements already meet the need, extending them may be the better choice.
An ARC engagement should earn its place by demonstrating additional value against the effort and responsibility it introduces.
Do not begin by connecting the entire architecture landscape.
Bring one decision, one repository transition or one access problem.
Together, we can establish:
The goal is not another platform programme.
It is to make the architecture knowledge you already have more useful for the next controlled change.
Explore ARC at onarc.cloud
Contact contact@dynacore.se