Ordinant

Make the decision part of your software.

Ordinant is software in which a decision happens. Your company says what an answer to each kind of question must satisfy before the company can rely on it. As the work is done, by people, agents or both, Ordinant checks what they contribute against those requirements and establishes the decision once the requirements are met. The work then goes ahead on the decision.

A decision is established when your requirements are met.

Each kind of question has its own requirements. They say which facts are needed and which sources count, which rules apply and whose judgment is needed. They can also call for an independent check, and they say how much uncertainty your company will accept. The requirements belong to the kind of question, not to any one workflow.

We make the requirements explicit from your policies, your procedures and the judgment your company relies on today. Your company approves them before the software applies them.

As the work is done, people, agents, rules and other systems contribute facts, rule results and judgments, and Ordinant checks each one against the requirements. When all of them are met, the decision exists. It is not a field that a person, an agent or a script can set.

The decision carries what it was based on.

A decision carries more than its answer. It carries the question, the requirements that applied, the facts and judgments that met them, who or what supplied each one, and the uncertainty and conditions that were accepted.

Each of these stays connected to where it came from. A fact is linked to its source. A judgment is linked to the requirement it met and to whoever made it. Where a decision relied on an earlier one, that link is there too. Your company can see how any answer was established, including which rules applied at the time.

A correction establishes a new decision for the same question, and the earlier decision stays as it was. Your company can still see what it decided at the time, and tell it apart from what it can rely on now.

Software can recognize the same question.

The same question often comes up in different pieces of work. For software to notice that, it needs a way to tell when two questions are the same. Ordinant uses your company’s own definitions of which differences matter: which supplier, which kind of work, which version of the rules.

With that, software can find the decisions already made about a question and apply the requirements that belong to it. It can also notice when a question is being decided twice without anyone knowing, decided differently in two places, or treated as settled when it was not. Ordinant calls this reference to a question a Decision Address.

Each decision is established apart from the work that raised it. So a piece of work can depend on several decisions, and some can be established while others are still open.

The same decision can be used again.

When later work raises the same question, an existing decision may already answer it. The later work does not simply read the earlier answer. Ordinant checks two things: whether the decision establishes enough for this particular use, and whether the conditions it depended on still hold. When both are true, the later work can rely on it. Any other decisions that work needs are still established on their own.

Changes can be traced to the work they affect.

What a decision was based on can change. A fact can turn out to be wrong, a policy can be revised, and a permission can expire or be withdrawn. When that happens, Ordinant finds the decisions affected and follows the links to the later work and acts that relied on them. What to do about them is your company’s call. Finding them is Ordinant’s.

Actions can proceed from established decisions.

Some decisions lead to an act, such as a payment, a release or a change in access. For that act, Ordinant issues an authorization based on every decision the act requires. It says what may be done and what must still be true when it is done. Ordinant calls it a Decision Warrant.

The system that carries out the act checks the warrant at the moment it acts, alongside its own identity and permission checks. It does not need to reopen the decisions, even if it acts later, somewhere else, and took no part in them. If a condition cannot be shown to hold, the act cannot go ahead under that warrant.

Afterward, the system reports what it did. Ordinant connects that report to the warrant and to the decisions behind it, so your company can see what was decided, what was authorized and what was actually done.

Ordinant sits beside the systems you already run.

It does not need to replace them. Your systems of record keep their records and events, and your workflow tools keep coordinating the work. Your rules engines keep evaluating rules, and each result becomes one contribution to a decision. Your people and agents keep doing the work and contribute to Ordinant as they go, and a person takes part wherever your requirements say one must. Ordinant’s part is the decision. Everything else stays where it is.