Search Results

In real-world situations, information from enterprise systems needs to be integrated with each other to support the desired way of working. AVIX CONNECTOR offers a standard way, and a toolbox to integrate/exchange AVIX information with other systems. The stan...

AVIX CONNECTOR aims to define a common neutral format to describe all types of information. In doing so we relay on some basic building blocks. Object Domains Objects Parent/Child references Relations   Logical structure Given a generic parent child...

Let’s say that we have a tiny factory structure that we want to import. One factory, with one line beneath it. Factory objects resides in the “locations” domain. AVIX understands location types “factory”, “building”, “line”, “workStation”, “humanResource” and...

Wood4.json is a bigger example and contains information from two object domains, “locations” and “processes”. One new concept that is introduced is relations. { "type": "humanResource", "id": "oid4004", "originId": "oid4004", "originSource": "EXCEL", ...

In AVIX, many text fields can contain more that one translation of a text. One example is the “name”-field. More than one translation can be imported at the same time using the “.” (dot) notation. "attributes": { "name": { "sv": "7 Stationer-Standar...

Known domains are “processes” Parent type Child list type Child type processLibrary childProcesses processTask processLibrary ownedDocuments externalUrl processLibrary ownedDocuments ...

In the main meny, select “File”, “Import…” Select “Upstream connector”, “Next>” For “Assigned host”, click the “ME” button. ROUTING AVIX uses Apache Camel internally and AVIX Connector let a skilled user create routes between AVIX and other external system...

OPC UA proxy definitions can be used to make AVIX SFV aware of external data provided by the factory.  This tags provided can be used to allow for triggering of Work instructions. Future functionality aim to record selected tags to the as built journal. exam...