PAC-ID Resolver

Seamless user navigation across system borders.

Great user experience

  • Send users to tools they already know
  • Go straight to the correct detail page
  • Easy to keep evolving (avoid obsolete dead-ends)

Low TCO

  • Easy to get up and running
  • Avoids costly integrations
  • Reduces vendor lock
  • Allows changes without touching everything

Introduction

In laboratory workflows, the utilization of multiple software applications is commonplace. A seamless exchange of contextual data between these applications is essential to provide users with a state-of-the-art experience.

The conventional approach involves interfacing applications with each other. Unfortunately, due to the lack of standards, such interfaces typically require bespoke software development or customization projects, demanding substantial effort to create and maintain.

resolver_without

In contrast, the PAC-ID Resolver architecture offers an alternative and lightweight solution for connecting applications in a loosely coupled manner. Implemented as a neutral contract between systems, it eliminates inter-dependencies and therefore facilitates adding additional or replacing existing systems. Its workflow context awareness allows seamless interactions that result in an exceptional user experience.

resolver-with

Example

Mettorius maintains a file, which describes, what services (information, actions) they have available related to their products.
This so-called coupling information table (CIT) is publicly available online:

When the PAC-ID of a Mettorius instrument is scanned the information from the CIT is used to show links to the available services.

Context Aware Information

The PAC-ID resolver makes it possible to provide just the services which makes sense to the user in the current context.

Taylor by Type

Mettorius offers different services for Devices and Substances.

The user in the lab in both cases does exatly the same; they scan a PAC-ID.

 

 

For Cleaning Products Mettorius provides CoA, MSDS and a WebShop

HTTPS://PAC.METTORIUS.COM/-MS/BAL-CLEAN/56985

 

For Devices Mettorius provides Operation Manuals, Technical Datasheets and a WebShop:

HTTPS://PAC.METTORIUS.COM/-MD/BAL500/210263

Taylor by Intent

In some situations a particular service might be of higher importance than others. Consider Chem Inventory, a chemicals inventory system, which is used to track chemicals in a laboratory.

It has - among others - these two features:

Feature 1: Show information about a chemical on an infopage
Beside information the inventory system has about the chemical (e.g. current stock) it is convenient for the user to have access to services of Mettorius. The inventory system - which contains a PAC-ID resolver - displays all the services Mettorius has to offer: Links to MSDS, CoA and Shop

Feature 2: Notify the administrator when the stock runs low
The inventory system sends a notification to the administrator, when the penultimate BAL-CLEAN is used up. Now the Shop service is important, while MSDS and CoA are not. The inventory makes use of the Application Intent column and only shows entries for shop.

2025-02-28 15_55_21-Untitled – Figma and 1 more page - Work 2 - Microsoft​ Edge

Location Dependent

2025-02-28 16_39_29-Untitled – Figma and 1 more page - Work 2 - Microsoft​ Edge

We have seen, that Mettorius offers their shop as a service. In larger companies there might be a requirement to order through their internal order platform.
This can easily be achieved by adding an internal coupling information table (CIT), which provides a link to this system as a service.
PAC-ID resolvers consider both tables.
In fact, there can be even more CITs, for example a personal one.

Minimized Technical Burden

A powerful feature of the PAC-ID resolver is that additional services can easily be added or existing services can be moved. The only thing which needs to change is CIT, which a simple edit in a text file. The PAC-IDs which the CIT resolves can remain the same. This is important, as they might be on hard to reach entities, such as laboratory devices.

dynamically_link_services

Specifications

For the specification and technical details, refer to GitHub.