Talk to us

Connecting data across partners, sites and systems

Axio Lattice connects data across companies and makes it ready for AI. Each company controls what it shares.

See how it works Talk to us

How Lattice works

Each company keeps its raw records in its own Node. An approved view contains only the information the owner agrees to share.

  1. Connectors read records from your source systems or exported files.

  2. The Node is software that runs where you choose to store your records. Raw records stay there.

  3. Rosetta is the translation layer. It combines a shared vocabulary with each company's own mappings. A mapping links a local field to a shared concept and its unit rule.

  4. Lineage records where a result came from. It links the result to its source file, connector run, mapping version and approvals.

  5. Axio runs the Coordination layer. It manages sign-in, identity, permissions and each company's sharing policies. Each company's gate applies those policies before a view leaves its Node. The Coordination layer holds the audit log and the views each team has permission to see. The audit log records access, changes and approvals.

  6. Blueprints

    Blueprints define a workflow's inputs, checks and results.

Follow a tech transfer

Tech transfer gives a Manufacturing Partner the process information it needs to make a Pharma Sponsor's medicine. This example follows the process handoff and the return of a direct measurement.

Viable cell density measures the number of living cells in a volume of liquid.

In a 2019 survey, transfers between companies took an average of 5.8 months longer than transfers within one company. The survey covered complete transfers of sterile products.

Illustrative example. The sample values, fields, codes, versions and approval records show how Lattice handles a tech transfer.

The Pharma Sponsor hands over the process

  1. Define the process

    The Pharma Sponsor defines the cell culture step, the day-10 viable cell density target and the counting method under vcd. The field uses cells/mL. The process record stays in the sponsor's Node.

    Today: Teams assemble process steps, targets and methods in separate documents.

  2. Translate through Rosetta

    Rosetta maps vcd to VCD.01, then to the partner's Viable Cells (E6/mL). The unit rule links cells/mL with million cells/mL. If a term has no approved mapping, Rosetta flags a gap at its source line.

    Efficiency: Approved mappings remove retyping and repeated term-by-term reading of documents.

    Today: Teams read documents term by term and retype fields into local templates.

  3. Approve the process handoff

    The sponsor approves the process package for the partner. Lattice records the approver, approval time and package version. The approved view passes through the sponsor's gate to the partner.

    Efficiency: The approval record replaces requests for signed PDFs.

    Today: Teams exchange signed PDFs and ask which version has approval.

The Manufacturing Partner returns the result

  1. Read the measurement

    During the batch run, the Manufacturing Partner's lab system records a day-10 viable cell density of 24.6 ×10⁶ cells/mL. The connector reads the record into the partner's Node. Rosetta applies mapping v14 to link the result to VCD.01 and its source history.

    Today: Teams copy the lab result into a results table.

  2. Approve the return

    The partner approves the result and its supporting details for the sponsor. The approved view passes through the partner's gate. The raw file stays in the partner's Node.

    Efficiency: Teams share the approved view without a separate export or a retyped certificate.

    Today: Teams export results and retype them into a certificate of analysis.

The Pharma Sponsor checks the result

  1. Compare with the target

    The sponsor sees the result under its own vcd, beside the day-10 target from its process package. The meaning, unit and sample day match the process definition.

    Today: Teams compare result names, units and sampling days in spreadsheets.

  2. Trace the result to its source

    The sponsor traces the result through mapping v14 and the connector run to 2044R2_D10_CC.csv. The sponsor needs separate permission to open the raw file.

    Efficiency: The sponsor can trace the result without asking the partner to send source data.

    Today: The sponsor emails the partner for the source record and its history.

Illustrative example. The sample values, fields, codes, versions and approval records show how Lattice handles a tech transfer.

Your next transfer starts with these connections and mappings

Keep the connection

For each later partner, you can use the same connection to a source system. The connector reads records into the company's Node. Each new partner receives only the views the company approves.

Keep the meaning through Rosetta

Rosetta's shared vocabulary defines process steps, measurements and their relationships. For a result, those relationships include the sample, unit, test method and batch. Each company keeps its local field names.

Axio maintains the shared vocabulary. The Pharma Sponsor controls its mappings to that vocabulary. The Manufacturing Partner controls its own mappings. A subject expert at each company approves its mapping rules.

Teams can use an approved mapping for later records and other partners that use the same shared concept. Teams review the meaning, units and source version for each new use.

Review a changed field

The partner renames Viable Cells (E6/mL) to Viable cell density (E6/mL). Rosetta holds the affected result for review because the new field has no approved mapping. The partner's subject expert reviews the meaning and unit before approving mapping v15.

The new mapping links the renamed field to VCD.01. The sponsor keeps its vcd mapping. The result from the transfer example keeps mapping v14 in its Lineage.

Each approved mapping change creates a new version. If a team processes a source record again, Lattice creates a new result with the selected mapping version. Lattice keeps the earlier result and its Lineage.

Illustrative field change. The renamed field and mapping v15 apply to a later record.

Reuse the workflow

A Blueprint defines a workflow's inputs, checks and results. The tech transfer Blueprint uses existing connections and Rosetta mappings to assemble process information and identify gaps. Teams adapt its checks and sharing rules for the next transfer.

Questions about working with Lattice

Find answers about fit, data control, quality and setup.

The basics

Who is Lattice for?

Lattice connects a Pharma Sponsor with a Manufacturing Partner working on the same drug program. The sponsor develops the medicine. The partner makes or tests it. Their teams use approved views to exchange process information and review results.

Does it replace our existing software?

Your existing systems stay the official sources of your records. Connectors read records from those systems or their exported files. Rosetta applies mappings for the views your teams use.

What happens to our existing documents?

Process documents, batch records and certificates of analysis are part of your quality process. Lattice links the information for the agreed workflow to its source through Lineage. Your teams still review and approve the required documents.

How does Lattice use AI?

AI can draft mapping proposals that a person at the company that owns the mapping must approve before use. Approved Rosetta mappings then apply the same rules every time. Lattice flags uncertain items for a person to review. Axio agrees the AI services and hosting with you in advance. Axio does not send raw sample values to hosted AI services.

Data and control

What leaves our boundary?

Only approved views cross your Node boundary. Your sharing policy defines the fields, supporting details and recipients for each view. Raw records stay in your Node.

What does Axio hold?

Axio's Coordination layer holds the shared vocabulary, approved views, source references and audit records. If Axio hosts your Node, that Node also holds raw records within your company's chosen boundary. The hosting agreement defines the locations and responsibilities.

Who controls access to our records?

Your company decides what to share and who can receive it. The Coordination layer applies permissions by company, program and role. Permission to see a result or its source reference gives no automatic access to the raw file.

Do you train models on our data?

Axio does not use your data to train or fine-tune models. Axio does not let third-party model providers train on it. Your records and results reach only the recipients you approve. Other customers can benefit from improvements to the shared vocabulary and connectors that contain none of your records or results.

Security and quality

Who hosts the Node?

The Node runs at your facilities, in your cloud environment or with Axio. Your company chooses the boundary that holds its raw records. Axio runs the Coordination layer in each arrangement. The hosting agreement assigns the operating and security responsibilities.

How is the connection protected?

The Node starts an encrypted connection to the Coordination layer. Each end verifies the other's identity. Security review also covers stored data, administrator access and connections to outside services.

How does Lattice support data integrity?

Data integrity means that records stay complete, accurate and traceable throughout their life. The Node keeps the original files. Lineage links results to their source files, connector runs, mapping versions and approvals. Lattice records corrections as new entries in the audit log. Earlier entries stay in the log.

Is Lattice validated for regulated work?

Lattice includes controls that support validation for a defined use. Validation needs documented evidence that the installed system works for that use. Your quality team and Axio must establish the required evidence and procedures for your deployment.

Who remains responsible for quality decisions?

The sponsor and partner keep their quality responsibilities. Their quality agreement defines how they divide and oversee the work. Lattice provides approved views and Lineage for their review. Authorized people approve investigations, process changes and product release.

Getting started

What do we need to start?

Select a workflow, its source systems and the people who understand those records. Your technology and quality teams define Node hosting, connector access, mapping approval and sharing policies. Source access and data quality determine the setup work.

Can our own agents use Lattice?

Lattice includes interfaces for authorized software agents. The Coordination layer applies the company's permissions to their actions. Your team reviews which interfaces, agent actions and human approvals the workflow needs.

What happens if a connection drops?

The Node keeps records locally during an interruption. When the connection returns, the Node sends only approved updates. Your deployment plan must define storage limits, recovery and warnings for results that are out of date.

What happens to our data if we leave?

Raw records stay in your Node. Axio holds approved views, source references and audit records in the Coordination layer. After the work ends, Axio deletes the data it holds and confirms the deletion in writing. Axio agrees any retained records with you in advance.

Apply to become a Lattice partner

Tell us about your organization and how you want to work with Axio on Lattice.