Overview

The purpose of theLogix API is to enable data exchange between LogixApplications andbusiness systems, such as ERP, APS, or CMMS.

...

• Repository of materials and BOM’s

• Scheduling production activities

• Registering events related to lifecycle of an activity (start/stop/complete)

• Exposing selected raw data and aggregated KPIs and other data by Logixapplications(including OEE metrics, downtimes, reported labor time)

Goals

• Decoupling:

  • Logix internal data model, of which semantics is known across Logixcomponents, from external data models.

  • Logix cloud services from implementation of custom integration components, supporting various interfaces, different orchestrations, ETL batch exchanges, and data formats.

• Common core message bus and data structure

• Security:

  • Authorizations

  • DDoS - Request Flood prevention

  • Events/errors logging

• Out-of-the-box observability:

  • Monitoring

  • Logging for auditing and debugging

  • Tracing in case there is a need for deeper problem analysis.

...

Updating via an external system is not allowed only if a specific activity is blocked as Managed by LogiX (it is done by setting a special internal flag in LogiX). Such blocking occurs automatically when an activity is added or modified through an app that belongs to the LogiX Suite (PackOS or KeepUp).

3. Registering events

Changing the statuses of activities that are in the LogiX scheduler can be initiated from outside by invoking dedicated methods on the resources related to specific activities (start/complete).

...