> For the complete documentation index, see [llms.txt](https://interfacing.gitbook.io/interfacing-help-files/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://interfacing.gitbook.io/interfacing-help-files/getting-started/glossary-and-key-concepts.md).

# Glossary & Key Concepts

Learn key terminology and core concepts to help you use the platform effectively.

This section defines key terms, frameworks, and methodologies used in IMS. Understanding these concepts will help you navigate the system more effectively and take full advantage of its capabilities.

***

### Audit

An **audit** is a systematic process used to review and verify actions, changes, and compliance across processes and documentation, ensuring adherence to standards.&#x20;

In IMS, all modifications, approvals, and user interactions are automatically logged. This creates a complete, traceable history that enables teams to review changes, ensure compliance, and meet internal or external audit requirements.

> **Learn More**:&#x20;
>
> * Explore the [Audit App](broken://pages/FcEBLZqWX6Q6Ad33pev5)
> * Review how [Versioning](/interfacing-help-files/end-users/library/exploring-the-details-panel/versioning.md) works
> * Download the <mark style="color:red;">Audit Trail</mark>

***

### BPMN&#x20;

#### ➔  Business Process Model and Notation

**BPMN** is an industry-standard visual notation used to model business processes. It illustrates the flow of tasks, events, decisions, and interactions between participants.

{% columns %}
{% column %}
**For End-Users:**&#x20;

Understanding BPMN helps users follow process flows, see how their tasks fit within the larger workflow, and recognize how processes impact their work.
{% endcolumn %}

{% column %}
**For Process Analysts:**&#x20;

Proficiency in BPMN allows analysts to create detailed, accurate diagrams that reflect real business activities. This ensures processes are clearly represented, easy to analyze, and ready for optimization or automation.
{% endcolumn %}
{% endcolumns %}

> **Learn More**:
>
> For additional details on BPMN 2.0 logic and functionality, visit: [www.omg.org/](http://www.omg.org/).

***

### BPMN Properties

BPMN elements—such as tasks, events, and gateways—have **properties** that define their behavior and interactions within a process.&#x20;

These properties specify whether activities repeat, how paths are chosen, and how events affect the process flow. They ensure that process diagrams accurately reflect real work, thereby making diagrams easier to follow for users and more reliable for analysts to design and improve.

> **Learn More**:&#x20;
>
> See the [**Detailed Guide to BPMN Properties**](/interfacing-help-files/process-analysts/business-process-management/creating-and-editing-process-diagrams/mapping-a-process/editing-bpmn-properties-for-objects-and-flows.md) to explore advanced properties and learn how they enhance your process models.

***

### Collaboration is Now Posts

In IMS, the **Collaboration** feature from EPC is now called **Posts**. Posts provide a more interactive and organized way to share ideas, ask questions, and suggest improvements to documentation.&#x20;

They help teams communicate more effectively, reduce information silos, and encourage collaboration across the organization, fostering a culture of continuous improvement and shared knowledge.

> **Learn More**:&#x20;
>
> See the new **Posts** in action in the [**Release Notes**.](/interfacing-help-files/release-notes-16.0/posts.md)

***

### CRUD

#### ➔ Create, Read, Update, Delete

**CRUD** is a method for managing **Master Data** (<img src="https://1488562728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTx7AmE0d2Q4ja20EYjF5%2Fuploads%2FdKoI0O0opffoEzxTxyqF%2FIMS-V16-NAV-Library-Icons-7.png?alt=media&amp;token=0ac84ae5-d535-426f-8f60-9d42fa1dca2e" alt="" data-size="line">) documentation items, such as **entities** and **attributes**. It also helps track how information flows through processes.&#x20;

With CRUD, users can assign data objects directly to processes and flow objects, making it easy to see who or what is responsible for creating, accessing, updating, or deleting information.&#x20;

***

### Governance

**Governance** is a structured framework for managing documentation, ensuring compliance, accountability, and accuracy across the organization.

A key component of governance in IMS is the **Documentation Lifecycle**, which defines how documentation is created, reviewed, approved, published, and maintained. Each stage is traceable and designed to promote collaboration, transparency, and continuous improvement.

> **Learn More**:&#x20;
>
> Refer to the [**Documentation Lifecycle Guide**](/interfacing-help-files/document-control/managing-documentation-lifecycle.md) to see how governance is managed.

***

### **KPIs, KRIs, and KCIs**

These are all **Performance** (<img src="https://1488562728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTx7AmE0d2Q4ja20EYjF5%2Fuploads%2FwgybSfXchzFbCLOuTMAx%2FIMS-V16-NAV-Library-Icons-2.png?alt=media&amp;token=f82fb772-d067-4edf-bf7f-d5d48d4c80ff" alt="" data-size="line">) documentation items used to monitor and improve processes:

* **KPI (Key Performance Indicator):**\
  Measures performance against objectives (efficiency, effectiveness, goal achievement).
* **KRI (Key Risk Indicator):**\
  Monitors potential risks and provides early warning signals.
* **KCI (Key Control Indicator):**\
  Measures the effectiveness of controls or safeguards within processes.

These indicators allow you to track performance, risks, and controls at every level, from individual tasks to entire processes.&#x20;

The system provides real-time feedback through color-coded indicators and historical trends, making it easy to spot issues, monitor progress, and take proactive action.

***

### Process Mapping vs. Process Modeling

{% columns %}
{% column %}

#### Process Mapping

* Provides a high-level view of a process, showing the sequence of steps, inputs, and outputs.&#x20;
* Helps teams quickly understand the workflow, participants, and the movement of information or materials.
  {% endcolumn %}

{% column %}

#### Process Modeling

* Offers a more detailed, structured representation, including rules, decision points, roles, and system interactions.&#x20;
* Supports analysis, optimization, and compliance.
  {% endcolumn %}
  {% endcolumns %}

{% hint style="info" %}
**Summary**: Mapping gives an overview; modeling provides the blueprint for improvement, automation, and informed decision-making.
{% endhint %}

***

### Process Mining

**Process Mining** is a data-driven method for visualizing, analyzing, and improving business processes using real event log data.&#x20;

In IMS, the **Process Mining App** automatically generates interactive process maps and highlights key insights, such as case flows, activity durations, and performance bottlenecks. This helps teams identify inefficiencies, monitor performance, and make faster, evidence-based decisions.

> **Learn More**:&#x20;
>
> See your processes in action and begin your process optimization journey with the [**Process Mining App Guide**](/interfacing-help-files/process-analysts/process-analysis-and-simulation/process-mining.md).

***

### Process Simulation

**Process Simulation** allows you to model and test changes or scenarios in a virtual environment before implementing them in reality.&#x20;

Using IMS’ **Process Mining App**, you can simulate changes to activity timing, routing, or volume, compare scenarios with the current process, and evaluate their impact on performance. This supports smarter planning, reduces risk, and helps optimize processes across the organization.

***

### RASCI-VS

#### ➔ Responsible, Accountable, Support, Consulted, Informed, Verifier, Signatory

**RASCI-VS** is a responsibility assignment matrix that clarifies who is involved in each task or deliverable.&#x20;

Each documentation item or activity is linked to the appropriate role, making accountability and collaboration clear across the organization.

<table><thead><tr><th width="118.888916015625">Value</th><th width="215">Responsibility </th><th>Role</th></tr></thead><tbody><tr><td>R </td><td>Responsible</td><td>Completes the work or task</td></tr><tr><td>A</td><td>Accountable</td><td>Owns the task or item and makes final decisions</td></tr><tr><td>SU</td><td>Support</td><td>Provides assistance or resources</td></tr><tr><td>C</td><td>Consulted</td><td>Gives input or advice; two-way communication</td></tr><tr><td>I </td><td>Informed</td><td>Kept updated; one-way communication</td></tr><tr><td>V</td><td>Verifier</td><td>Checks quality, compliance or accuracy of content</td></tr><tr><td>SI</td><td>Signatory</td><td>Approves or signs off content before completion</td></tr></tbody></table>

***

### SIPOC&#x20;

#### ➔ Suppliers, Inputs, Process, Outputs, Customers

**SIPOC** provides a high-level view of a process, showing the relationships between the process, its suppliers, and its customers.&#x20;

<table><thead><tr><th width="140.2000732421875">Component</th><th>Description</th></tr></thead><tbody><tr><td><strong>S</strong>upplier</td><td>The entity providing inputs to the process</td></tr><tr><td><strong>I</strong>nputs</td><td>The items or resources consumed by the process to produce outputs.</td></tr><tr><td><strong>P</strong>rocesses</td><td>The workflow or procedure itself.</td></tr><tr><td><strong>O</strong>utputs</td><td>The results or deliverables produced by the process.</td></tr><tr><td><strong>C</strong>ustomers</td><td>The entity receiving the outputs from the process.</td></tr></tbody></table>

You can view a process' SIPOC in its [**Details** panel](/interfacing-help-files/drafts/searching-for-objects-in-the-library/library/exploring-the-details-panel.md), helping you understand your role, your impact on others, and opportunities for for process improvement and alignment with objectives.

> **Learn More**:&#x20;
>
> See the <mark style="color:red;">**SIPOC Guide**</mark> to start creating your own.&#x20;

***

### Workflow

A **workflow** is the defined sequence of tasks in a process, including decision points, showing how work moves from start to finish.

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://interfacing.gitbook.io/interfacing-help-files/getting-started/glossary-and-key-concepts.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
