Read the inventory platform
The Vysix Integration Engine reads Arcturus cloud data using TLS 1.2 encryption over outbound port 443.
Verified source platform
Arcturus & AutoCrib Data Integration
Integrate Arcturus, the AutoCrib inventory management platform, with your ERP and the Vysix-hosted data platform so inventory activity reaches the workflows and reports that need it.
Inventory platform
Arcturus (AutoCrib) or another scoped platform
Vysix Integration Engine
Reads, validates, maps, and moves operational records
ERP workflows scoped
Direction and frequency defined per ERP interface
Vysix-hosted data platform
Managed, secured, and maintained by Vysix. Your data stays yours.
Vysix BI
Dashboards, exceptions, and operational reporting
How it works
A focused path from inventory activity to ERP and reporting
Vysix complements Arcturus rather than replacing it. The inventory platform keeps running the floor while Vysix moves the records downstream.
Map operational records
Inventory, usage, employee, job, and item records are mapped to a dependable target structure and to ERP fields in scope.
Land and report
Mapped records load into the Vysix-hosted data platform, where Vysix BI reports on them.
Operational fit
Built around the systems and decisions you already own
The scoped path
How Arcturus data reaches your ERP and reporting
Arcturus, the AutoCrib inventory management platform, is the verified inventory source for Vysix. The records available on this path are inventory, usage, employee, job, and item records. The Vysix Integration Engine reads those records, maps the fields you agree on during implementation, and communicates outbound using TLS 1.2 encryption over port 443, so no inbound internet listener is required.
From there, mapped records can go two places: to the ERP workflow in scope, and to the Vysix-hosted data platform, where Vysix BI reports on them. Not every record, interface, or direction is available in every environment, and Vysix does not offer prebuilt connectors for every ERP. The ERP side of each integration is confirmed during technical discovery. For how this fits alongside other platforms, see our inventory and ERP integration services.
Discovery
What we confirm before defining your integration
A useful scope connects the business workflow to the interfaces and people responsible for it. We confirm five things before build.
Question 1
Arcturus environment and access
Which Arcturus tenant and sites are in scope, and what access your team can make available for the integration.
Question 2
ERP, version, and supported interface
Your ERP product and version, and which interface it actually supports for the records you want to exchange.
Question 3
Workflow and record ownership
The business workflow being connected, and which system owns each item, job, employee, and location identifier.
Question 4
Direction and timing
Which records need to move, in which direction, and how often. Direction and frequency are agreed per project, not assumed.
Question 5
Validation and error ownership
Who reviews unmatched or rejected records, how exceptions are reported, and who is responsible for resolving them.
For a fuller list of planning decisions, use the inventory-to-ERP integration planning checklist.
Planning example
Reconciling a usage record to ERP identifiers
Illustrative mapping example
In this hypothetical case, suppose an operator issues a box of inserts from an AutoCrib machine against a job. Arcturus records a usage event with an item, a quantity, an employee, and a job. Before that event can be useful in an ERP, both sides need to agree on what it means.
- Identifiers: which Arcturus item maps to which ERP part number, and which job reference matches the ERP job or work order.
- Units: whether the machine issues each, box, or pack, and how that converts to the ERP unit of measure. For example, if one issued box contains 10 inserts and the ERP records each insert, the agreed conversion is 1 box = 10 each; confirm the actual pack size in your item master.
- Sample output: a sanitized example of the record the ERP should receive, reviewed by both teams before build.
- Unmatched and repeated records: what should happen when an item or job has no mapping, and how a repeated delivery is told apart from a new transaction.
Agree these acceptance requirements with your inventory and ERP owners before implementation.
The first call
Start with your ERP and workflow
Bring your ERP and version, the workflow you want to connect, and your site and machine context. We use that to assess feasibility, field mapping, timing, and responsibilities, and to tell you plainly what is verified, what needs discovery, and what is not a fit yet.
Frequently asked questions
- Does this replace AutoCrib?
- No. Arcturus and your AutoCrib machines keep running the floor. Vysix reads agreed records from Arcturus and moves them to the ERP workflow in scope and to the Vysix-hosted data platform for reporting.
- Is my ERP supported?
- Arcturus, the AutoCrib inventory platform, is the verified source. The ERP side is assessed case by case: we confirm your ERP version, its supported interface, and the fields involved during technical discovery. We do not claim prebuilt connectors for every ERP.
- Is the transfer real time or bidirectional?
- Direction and timing are agreed per project. They depend on what Arcturus and your ERP interface support and on the workflow involved, so neither real-time nor bidirectional transfer is assumed in advance.
- What information should I bring?
- A short description of your ERP and version, the workflow you want to connect, the records involved, and your sites.
- What does discovery establish?
- Discovery defines the proposed source and target fields, direction, timing, validation checks and responsible owners. Feasibility and implementation estimates depend on the interfaces and requirements confirmed.