Integration discovery

Connect OreLynx to the Systems Your Operation Relies On

Exchange operational records through defined files, APIs, webhooks and integrations—with clear ownership, validation, timing and failure handling.

Assess integration requirements

Integration Discovery Areas

Use these categories to identify the records and systems OreLynx should connect for your operating scope.

Identity and Access

Authentication source, account lifecycle, groups or roles, privileged administration, access reviews and emergency access.

Laboratory and Sample Data

Identifiers, custody state, dispatches, methods, results, qualifiers, corrections, QA/QC context and reconciliation ownership.

GIS and Spatial Data

Coordinate reference systems, geometry types, source metadata, transformations, validation, precision and update direction.

Documents and Evidence

File types, classification, versioning, approvals, retention, legal hold, malware handling and controlled retrieval.

Finance and Procurement

Reference data, approval boundaries, coding, currencies, tax context, reconciliation and segregation of duties.

Portability and Exit

Customer-owned records, export scope, structure, attachments, audit context, delivery method, verification and deletion boundary.

Contract element	Questions to resolve	Acceptance evidence
Scope and direction	Which objects and fields move, in which direction, and which system is authoritative?	Approved mapping, sample data and round-trip or reconciliation test
Identity and security	How is the connection authenticated, authorised, rotated, limited and audited?	Threat review, configuration proof, negative tests and owner sign-off
Timing and capacity	Is transfer interactive, scheduled or batch, and what limits and delays are acceptable?	Measured volume test, throttling behaviour and capacity assumptions
Failure and recovery	What happens on duplicate, partial, late, invalid or unavailable transfer?	Retry, idempotency, dead-letter, alert and reconciliation tests
Version and support	Which vendor versions are supported and who owns change, incident and deprecation work?	Compatibility matrix, monitoring plan and change-control terms

Bring a Real Exchange Sample

A useful assessment starts with a redacted sample, expected result, volume, timing and known failure case. Do not send production credentials, personal data, confidential geological records or unredacted customer information through the marketing form.

Describe the systems to connect

Integration operations

What Teams Configure and Monitor

Each connection is operated as a controlled exchange with named ownership, validation and recovery—not a logo on a catalogue.

Map systems and records

Identify authoritative sources, destinations, objects, identifiers, versions and responsible owners.

Protect sensitive fields

Define tenant scope, permitted use, authentication, field allowlists, retention and transfer controls.

Test failure paths

Exercise duplicates, partial transfers, rejected records, timeouts and safe retries with representative data.

Operate reconciliation

Monitor expected versus received records and assign every unresolved exception to a person.

Bring one real workflow. We’ll map these functions to your roles, records, systems and acceptance scenarios.

Assess your workflow