HELIOS Integration Guide for Production Scheduling with SkyPlanner APS

Helios Inuvio Server (Inuvio REST API). Asseco describes it as a separate part of HELIOS iNuvio that gives REST API access to HELIOS iNuvio agendas (Helios Inuvio Server help). It ships with the iNuvio distribution, and the OpenAPI specification is published in Rapidoc and Redoc form. The API works on HELIOS overviews (browses), each with its own ID and rights:

• GET /browses/list and GET /browses/meta list the available overviews and their columns.
• /browses/data reads rows of an overview, and writes rows where the overview allows create, update and delete.
• /api/v1/actions/meta and /api/v1/actions/execute/{dbName}/{browseIdent}/{actionIdent} run external actions on an overview. Today these are external actions of type Procedure, Browse and Plugin.

The production overviews a scheduler uses include the production plan (výrobní plán), production orders (výrobní příkazy), production order parts, materials and semi-finished goods for production, professions, personnel resources, routing operation presets and operation records. Stock, receipts, issues and issued purchase orders (vydané objednávky) are available the same way.

HELIOS Nephrite REST API. The Nephrite roadmap lists REST API development (HELIOS Nephrite roadmap). The SkyPlanner team confirms the Nephrite endpoints for your installation with you and your HELIOS partner during scoping, and the data flows below stay the same.

Excel and CSV. Every HELIOS overview exports to Microsoft Office, which is enough for the trial load.

SkyPlanner reads HELIOS on a schedule. Calls to /browses/data, filtered to open production orders and recent changes, pick up new work. The frequency is set per plant, from every few minutes for production orders to hourly for stock.

SkyPlanner sends webhooks when state or the schedule changes, so the write-back side is event-driven.

1. Initial master data load. Read manufactured parts, BOMs, routings, workplaces, machines, professions, personnel resources and calendars from TPV overviews. Each HELIOS resource carries a flag to include it in capacity planning, so decide per resource what SkyPlanner schedules. A workplace with four machines becomes one workstation group or four workstations.

2. Order sync. Read production orders with their parts, operations and materials, plus issued purchase orders. SkyPlanner treats ordered material as available on the PO delivery date and updates stock when the PO is marked Delivered. Schedule released production orders. Planned quantities in the production plan stay in HELIOS until they become production orders.

3. Schedule write-back. When the engine places or moves a job, a SkyPlanner webhook triggers an external action on the production order overview through /api/v1/actions/execute. The action is a HELIOS procedure, agreed in scoping, that sets the planned start and finish of the order operation. HELIOS validates the change inside its own logic.

4. Shop-floor confirmations. Operators log work with SkyPlanner Mobile Confirmations or the Production Timer, and the timelogs keep the schedule current. You choose whether actual times post back to HELIOS. If yes, an external action records them as operation records per order operation. If no, operators keep reporting on HELIOS terminals and SkyPlanner reads those records.

5. Ownership and conflict rules. Write them down before go-live:

Pick one writer of order dates. If HELIOS capacity planning or Nephrite APS still writes dates, switch that off for orders SkyPlanner schedules, or keep the HELIOS plan as a test plan only.

• Planning flags. Only resources flagged for capacity planning have reliable capacity data. Check the flags on workplaces, machines, professions and subcontracts before the first load.
• Time units. Preparation, unit and finishing times can be entered in hours, minutes or seconds. Convert on import or every duration is wrong.
• Inter-operation time. The constant inter-operation time is waiting between operations, not machine time. Model it as a wait, not as capacity.
• Subcontract operations (kooperace). Transport time applies on the way out and back. Model subcontracts as time-only steps.
• Writable overviews. Every overview supports reads, but only some support create, update and delete. GET /browses/list with the filter browseCreateImplemented=1 shows which ones. Production orders are read-only overviews, so planned dates go back through the agreed external action.