Query your operating model in plain language
When something breaks or a regulator asks, most teams lose days assembling the answer, chasing owners by email, cross-checking Visio against SOPs, reconstructing dependencies from memory. IGX360 answers ownership, dependency and impact questions in plain language, in seconds, with the source behind every answer.
See Iggy answer a live questionThe cost of not having a fast answer
Every week without a fast answer is a week of manual audits, email chains and "let me check and get back to you." By the time the answer is assembled, the decision it was meant to inform has often already been made without it, and the next system change lands with a dependency nobody flagged in time to stop it.
How to map process ownership and dependencies
Answering "who owns this and what breaks if it fails" reliably comes down to three things most repositories can't do at once:
- A single model, not four systems. Ownership lives in a SharePoint list, the process in Visio, the control in a SOP, the dependency in someone's head. Until those are reconciled into one model with typed relationships, every question is a manual hunt.
- Typed relationships, not documents. Knowing that a document mentions a system isn't the same as knowing the payments gateway feeds settlement which is owned by Treasury. Dependency answers need relationships modelled as objects, not buried in prose.
- Provenance on every answer. An answer you can't trace is one you can't defend to a regulator or act on with confidence. Every claim should carry its source object, relationship path and confidence score.
IGX360 reconciles iGrafx, Visio, SOPs and BPMN/XML into one canonical model, so these questions resolve against structured relationships instead of a document search.
A worked example
- Question:
- If the payments gateway goes down, what stops?
- Answer:
- Settlement, supplier payment run, and month-end reconciliation. Gateway integration owner: IT Service Delivery. Downstream process owner: Finance Operations. Confidence: high, traced from the gateway object through three "depends-on" relationships to the affected processes. Every part of that answer links back to the object and path it came from. No black box.
Questions worth asking before you commit
Is this just a chatbot over documents?
No. Iggy queries a canonical model with typed objects and relationships, and returns provenance for every answer, not a keyword match over PDFs.
Can it be wrong?
Answers include a confidence score and their source path, so you can verify, not just trust.
What can it read?
iGrafx, Visio, SOPs and BPMN/XML, reconciled into one model.
Query your operating model in plain language
Ask your first question.