EAFLOW · CASE · PREVISIONAL
Process and operational-documentation corpus connected to the graph
A social-security contributions financial-services organization, with an operation in Chile, reused with Process Knowledge the process knowledge it already had —including a legacy repository such as ARIS— as a structured knowledge base: narrative, hierarchies, activities, owners, applications and documents are preserved as reusable context, connected to risks, controls and continuity over the same Operational Graph and queryable with Max. The goal was not to migrate legacy diagrams, but to leave that knowledge navigable and queryable to accelerate future process redesign and documentation.
EAFlow lets you reuse the process knowledge you already have as a navigable knowledge base: the corpus is ordered and connected to the Operational Graph, with the narrative and the legacy structure as an anchor, the processes linked to the compliance and continuity model, and querying with Max — useful as input to redesign, document and model processes when the team decides to.
The challenge
Social-security contributions financial-services organizations that keep their process practice on a legacy enterprise BPA tool face the same pattern. The problem is not the quality of the models: it is that the corpus lives trapped in the original modeler, isolated from the rest of the operation.
- The existing process repository is a valuable asset: years of curated models represent investment and the team's operational knowledge, but they stay locked in the original modeler.
- The decomposition hierarchy, the narrative and the legacy codes are the language the organization knows. That knowledge should be kept as a base, not discarded when redesigning.
- The repository lives isolated from the rest of the operational model: the processes are not connected to the risks, controls nor to continuity, even though they share the same universe.
- When redesigning processes from scratch, the risk is starting with no context: losing the narrative, the relationships and the documentation that already exist and that speed up the work.
- There is no way to reuse what exists as navigable, queryable knowledge —without assuming an automatic conversion of diagrams— that reduces the perceived risk before committing the full repository.
Process knowledge is not sustained with an isolated modeler. It is sustained with a corpus reusable, navigable, connected to the graph and queryable alongside its compliance and continuity context.
The EAFlow solution
Process Knowledge is a cross-cutting solution of the Process and Architecture Modernization area, built on the shared Operational Graph layer of EAFlow Platform. It reuses the enterprise BPA tool corpus —including legacy repositories such as ARIS— as a structured knowledge base, portable beyond the original modeler. The walkthrough covered, over a representative scenario to validate traceability and reportability, the reuse of the BPA corpus:
- Reuse of the process corpus as a knowledge base. A scoped set of the existing corpus —including a legacy repository such as ARIS— is brought into EAFlow keeping the decomposition hierarchy, the narrative and the legacy codes as a navigable anchor.
- Reusable context, not automatic conversion. Narrative, activities, owners, applications and documents become available as knowledge input. Where applicable, that knowledge serves to model new processes in portable BPMN 2.0, without assuming an automatic conversion of legacy diagrams.
- Processes connected to the compliance model. The reused processes are connected to risks and controls in the graph, showing the value of the shared context over the same base.
- Processes connected to the continuity model. The critical processes of the scenario are linked to the continuity model, connecting process, risk, control and dependency.
- Operational Graph as the unified destination. Processes, tasks, roles, applications, documents, risks, controls, critical continuity processes and relationships become connected as first-class entities, with source citation and event-level traceability.
- Deterministic analytical support and querying with Max. Navigation, structural querying and reporting over the reused corpus operate deterministically over the graph, queryable with Max in natural language.
The value is in reusing what already exists as knowledge: the corpus becomes navigable and queryable, and serves as input to redesign and document processes. When the team decides to model in portable BPMN 2.0, the equivalence rules are documented by notation family, in an assisted and governed way, without assuming an automatic conversion of diagrams. The level of integration with each modeler is refined by maturity and technical validation in Discovery.
What was tested
The walkthrough was run over a representative scenario to validate traceability and reportability of the social-security domain, leaving the real load for Discovery. The team walked the complete capability: reading the existing corpus (EPC, extended BPMN, including legacy repositories such as ARIS), reuse of the narrative, the decomposition hierarchy and the legacy codes as a navigable anchor, connection of the processes to risks, controls and critical continuity processes over the shared graph, queryable with Max, and —where applicable— assisted modeling in portable BPMN 2.0 with documented equivalence rules. Navigation, structural querying and reporting over the structure of the corpus worked deterministically.
Demonstrated capabilities
- Operational Graph as the shared context base.
- Reuse of the process corpus —including a legacy repository such as ARIS— as a structured knowledge base.
- Narrative, hierarchies, activities, owners, applications and documents preserved as reusable context.
- Portable BPMN 2.0 as input to model and document processes when the team decides to — without assuming an automatic conversion of legacy diagrams.
- Processes connected to risks and controls in the compliance model.
- Critical processes connected to the continuity model.
- Deterministic graph navigation, structural querying, reporting and querying with Max over the reused corpus.
Observed result
The corpus went from "living trapped in the original modeler" to being available as a navigable knowledge base connected to the graph, with the narrative, the decomposition hierarchy and the legacy codes preserved as an anchor, and the processes linked to risks, controls and continuity over the same base, queryable with Max — ready as input to redesign and document processes in BPMN 2.0 when the team decides to.
The walkthrough showed that reusing the existing corpus —including legacy repositories such as ARIS— is applicable to the social-security domain over a representative scenario, leaving the evolutionary path —reuse the full repository in Discovery, complete the connection to the inventory and the risk-control universe, model new processes in BPMN where applicable, or extend natural-language querying— in the team's hands, with the tested capability as evidence.
Why it matters for other organizations
The pattern repeats in social-security contributions financial-services organizations with years of investment in their process practice, including legacy repositories such as ARIS: the corpus is valuable and the narrative, the hierarchy and the legacy codes are the team's language. Reusing that existing knowledge as a structured base —preserving it as navigable context, connecting it to the compliance and continuity model, queryable with Max, and leaving it as input to model in BPMN where applicable— accelerates process redesign, documentation and navigation without starting from scratch, and opens an evidence-informed evolutionary path.
Starting with process knowledge is also a low-risk entry point: the same Operational Graph that sustains the processes later sustains architecture, inventory, documents, risk and operation.
How it scales — related solutions
The reused process corpus is connected over the same Operational Graph:
- Toward the full repository Process Knowledge
At-scale reuse of the existing process corpus as a knowledge base, full connection to the graph and —if the client decides— natural-language querying over the corpus.
- Toward risk and control Risk & Control Assurance
The reused processes connect to the risk-control universe, with evidence and process-control-evidence traceability.
- Toward continuity Operational Continuity & Resilience
The reused critical processes feed the impact analysis and the critical dependencies.
- Toward the application inventory Live IT Inventory
The applications that support the processes connect to the IT portfolio with owners, criticality, dependencies and integrations.
- Toward architecture governance Enterprise Architecture Governance
The process corpus becomes the base of the living architecture repository, with metamodel, traceability and governance by domain.
- Toward changes and roadmap Change Impact
When a change touches a process in the corpus, the graph allows estimating the impact over applications, integrations, data and documents before deciding.