# Pascal Ontology

Source: https://www.trypascal.io/platform/ontology

A shared language for your business.

Connect records across systems into a shared model of your customers, shipments, assets, and relationships. Give people and agents the same business context.

## Capabilities

### Model the company in its own terms

Define object types, fields, relationships, and interfaces for customers, assets, orders, or anything else the business operates on.

### Resolve identity across systems

Bring different source records back to the same business object. A customer remains recognizable across finance, sales, and operations.

### Inspect the evidence behind a value

Follow important fields to their sources and change history. Understand where a value came from before relying on it.

### Explore the connected record

Move from a record to its related objects, documents, events, and available actions without reconstructing the context in another tool.

### Create reusable object sets

Define live collections such as at-risk orders or open cases. Reuse the same scoped business population in analysis, workflows, and applications.

### Attach actions to business objects

Make approved operations available where the work happens. Carry current permissions and review requirements into the action.

## Connected context

Connect source records with Integrations and Data Infrastructure. Use the same business objects in Atlas investigations, Compass processes, Workflows, applications, and agent Tasks.

- Customers, assets, orders, shipments, cases, and the relationships between them
- Business definitions, calculated knowledge, histories, lifecycles, and live collections
- Approved actions, operating rules, policies, and the evidence behind every change

## Controls and permissions

Your ERP, CRM, and other source systems keep control of their records. Ontology connects those records without losing their origins. Actions on a business object still require current permission and any necessary approval.

## Example

A carrier failure arrives as a notice in one system. The response depends on orders, delivery promises, containers, and compliance cases in several others. Ontology connects them around the shipment, so an operator can investigate the exception and see which actions are permitted from the same record.

## Workflow

### Start with a shared identity

- Open Shipment MDR-80421. The delivery promise, carrier, and compliance hold belong to the same business record, with the original observations still available.

### Follow the relationships and sources

- Move from the shipment to its carrier, container, order, and compliance case. Inspect the carrier field’s source and the earlier mapping it replaced.

### Find the work that needs attention

- Filter 42 active Horizon shipments to the 17 at highest risk. The lithium loads remain held; the available next step is to request Compliance review.

## Next steps

Bring the decision, the records behind it, and the systems that own them. Map the objects, relationships, and actions your team needs first.

- [Contact sales](https://www.trypascal.io/contact)
- [Logistics operating system](https://www.trypascal.io/solutions/logistics)