Verizel
🇬🇧🇳🇴
← Back to user guide

Integrations

Integrations and API

Connect external technical data to controlled report workflows, analytics and finished documentation.

ProfessionalEnterprise
IntegrationsAdministrationReporting

Summary

  • Integrations are used when external data should become part of a controlled reporting workflow instead of remaining disconnected in spreadsheets, machine logs, vendor exports or separate databases.
  • The reusable integration model is: source data, mapping, validation, structured record, report link and controlled output.
  • Welding is the first reference implementation. The same pattern can later support NDT, heat treatment, inspection data and material traceability workflows.

Visual overview

Integration concept

External systems can import, export or synchronize structured data with the portal.

External systems

ERP, customer database, inventory system, certificate archive or BI platform.

Verizel

Customers, Projects, Work Orders, Inventory, Reports, Attachments and status data.

Outputs

Approved metadata, report status, analytics exports or customer portal updates.

portal.solemnenterprise.com / integrations

External systems

ERP
Inventory DB
Certificate archive
BI platform

API mapping

WorkOrderNo → Work Order number
HeatNo → Inventory heat number
CertRef → Attachment reference

Portal output

Customers
Projects
Work Orders
Inventory
Reports

What you can do

  • Register or prepare external data sources.
  • Map external fields to controlled portal fields and report context.
  • Preview and validate imported rows before they become controlled records.
  • Create structured records such as Welding Runs, measurements or result records with provenance.
  • Link relevant integration data to the correct report revision.
  • Snapshot selected data into finished reports and controlled PDF documentation.
  • Plan import, export or synchronization logic for ERP, DMS, inventory, analytics or customer portal workflows.

When to use this

  • A machine log, vendor export, CSV file, API or gateway contains technical data that should support a report.
  • Users currently retype source data manually into technical reports.
  • Welding, NDT, heat treatment, inspection or material traceability data needs stronger provenance.
  • Customers, projects or work orders already exist in an ERP system.
  • Material certificates or inventory records are managed in another database.
  • Approved report status should be pushed to a customer portal.
  • A company wants to analyze registered report data in an external BI tool.

Before you start

  • Identify the source system and owner of the data.
  • Decide whether data should be imported manually, imported from files, received through an API or connected through a gateway.
  • Prepare example records, field definitions and expected units.
  • Clarify whether the integration is read-only or should also write data back to the external system.
  • Confirm how imported data should be linked to Customer, Project, Work Order, report type and report revision.

Plan note

Integrations are normally Professional or Enterprise capabilities. Simple data export may be available earlier, while API, gateway, machine or database integrations usually require a scoped solution.

Task help

Common tasks in this area

Open the task that matches what you are trying to do. The full article continues below.

Integrations

Turn source data into report evidence

Use this when external technical data should support a controlled finished report.

Open
  1. Identify the source data, for example a welding machine log, vendor export, CSV/API file or gateway input.
  2. Map external fields to controlled portal fields, units and report context.
  3. Preview imported rows and check missing values, warnings, duplicates and technical validation issues.
  4. Create structured records such as Welding Runs, NDT results, heat treatment measurements or material traceability entries.
  5. Link the relevant structured record to the correct Work Order and report revision.
  6. Submit the report so selected source data can be preserved in the report snapshot.
  7. Export the approved revision as controlled PDF when documentation is complete.

Welding is the first reference implementation. The same model can later support NDT, heat treatment, inspection and material traceability workflows.

Integrations

Request an integration solution

Use this when a customer needs Verizel to exchange data with another system.

Open
  1. Identify the external system, machine, database or vendor export.
  2. Describe the business purpose of the integration.
  3. Decide whether data should be imported, exported or synchronized both ways.
  4. List the portal objects involved, for example Customers, Projects, Work Orders, Inventory, Reports or structured measurement data.
  5. Prepare example records, field names and units.
  6. Define frequency, security requirements and desired timeline.

A public Request solution form should later collect this information directly from potential customers.

Integrations

Prepare data mapping

Use this before estimating or implementing a database/API integration.

Open
  1. List fields from the external system.
  2. Map each field to the relevant portal object, field, unit and report context.
  3. Identify required fields and optional fields.
  4. Clarify unique identifiers and duplicate handling.
  5. Define error handling for missing, invalid or out-of-range data.
  6. Confirm how imported records should be linked to reports and controlled PDF output.

Good field mapping reduces integration risk and makes later testing much easier.

Reusable integration flow

The recommended integration flow is source data, mapping, validation, structured record, report link and controlled output.

This makes integrations useful for controlled reporting, not only for data transfer. Imported data should keep enough provenance to show where it came from, how it was mapped, when it was imported and which report revision used it.

  1. Source data: collect a machine log, vendor export, CSV/API file, gateway input or external database record.
  2. Mapping: map external fields to controlled portal fields, units and report context.
  3. Validation: preview rows, missing values, warnings, duplicate candidates and technical checks before ingest.
  4. Structured record: create controlled records such as Welding Runs, NDT results, heat treatment measurements or material traceability entries.
  5. Report link: connect the relevant structured record to the correct Work Order and report revision.
  6. Controlled output: snapshot the selected data into the finished report and controlled PDF.

Welding as first reference implementation

The welding integration is the first reference implementation of this model. It can prepare welding data sources, map imported vendor fields, validate rows, create structured Welding Runs and link the relevant run to a report revision.

Live equipment connection depends on vendor/API credentials, gateway setup or an agreed export/import format. Manual import and pilot validation can be used before live machine connection.

Other workflows that can use the same model

NDT workflows can use the same pattern for result tables, technique details, acceptance status and report evidence.

Heat treatment workflows can use the same pattern for oven logs, temperature/time curves, batch context and finished heat treatment reports.

Inspection workflows can use the same pattern for measurement data, dimensional results, visual inspection observations and approval status.

Material traceability workflows can use the same pattern for certificates, heat numbers, batch records, inventory lots and usage evidence.

Common integration examples

ERP integration can be used to import customers, projects, work orders or purchase order references.

Document system integration can be used to link material certificates, procedures or approved supporting documents.

Inventory integration can be used to synchronize stock, batches, heat numbers and material availability.

BI or analytics integration can be used to export report status, measured values, review status and production data for further analysis.

Request solution

Some integrations will be standard and repeatable. Others will require a scoped solution because each company stores data differently.

A Request solution form should collect the external system name, integration purpose, data direction, objects involved, sample fields, expected frequency, security requirements and contact person.

Typical request form fields

  1. Company name.
  2. Contact person.
  3. External system, machine, vendor export or database name.
  4. Integration purpose.
  5. Import, export or two-way synchronization.
  6. Objects involved, for example Customers, Projects, Work Orders, Inventory, Reports, Attachments or structured measurement data.
  7. Sample fields, units and example records.
  8. Expected frequency, for example manual, daily, hourly, event-based or live connection.
  9. Security and access requirements.
  10. Business priority and desired timeline.