Monitor ERP Integration Guide for Production Scheduling with SkyPlanner APS

Monitor G5’s documented integration interface is the Monitor ERP API v1. It is a CQRS and REST hybrid with JSON over HTTPS. (Monitor ERP API)

• Queries read data with GET. They accept OData-style options: $filter, $select, $expand, $orderby, $top and $skip.
• Commands write data with POST, for example Manufacturing/ManufacturingOrderOperations/Update.
• Batch runs several commands in one all-or-nothing transaction through POST /api/v1/Batch. Append /Simulate or /Validate to test a batch and roll it back. That is the safe way to write a whole schedule. (Batch)

The base URL is https://{host}:8001/{languageCode}/{companyNumber}/api/v1/. The company number combines the database number and company id, for example 004.1.

On licensing, Monitor says: “It is free to query and extract information from the API for all our customers. However, in order to use commands and write data to the ERP system, you need to purchase Monitor ERP API.” Plan the write licence into the project from day one. (api.monitor.se)

The Monitor ERP API reference documents no webhooks or event subscriptions. Changes are picked up by polling:

• Common/EntityChangeLogs (from 2.33) returns ChangeType (Update, Create, Delete), EntityTypeId, EntityId and ModifiedTimestamp. Poll it every few minutes and fetch only the changed records. (EntityChangeLog)
• Filter manufacturing order queries to open orders and page with $top and $skip.

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

1. Initial master data load. Read work centers, operation rows, alternative operation rows, material rows, parts and schedules. Map each work center to a SkyPlanner workstation deliberately. A Pool work center becomes a workstation group, and its incorporated work centers become the workstations the engine chooses between.

2. Order sync. Read open manufacturing orders with their nodes, operations and materials, plus stock and open purchase orders. SkyPlanner treats ordered material as available on the PO delivery date and updates stock when the PO is marked Delivered. After the first load, Common/EntityChangeLogs drives the delta.

3. Schedule write-back. For every operation the engine placed or moved, SkyPlanner sends ManufacturingOrderOperations/Update with PlannedStartDate and PlannedFinishDate. When the engine moved an operation to another machine in a pool, SetWorkCenter comes first. The commands for one order go in one Batch, so Monitor accepts all of them or none. Run the batch through /Validate during testing.

On Monitor versions before 24.5, the planned dates are not writable through Update. Use ManufacturingOrders/ReplanOperation (from 2.40) with StartDate and FinishDate instead, and set RestrictToOrderBounds to match your rules.

4. Shop-floor confirmations. Keep one reporting channel:

• Monitor stays the channel. Operators report on the Recording terminal or through machine integration as today. SkyPlanner reads ManufacturingOrderOperationReportings as progress and replans.
• SkyPlanner becomes the channel. Operators log work with Mobile Confirmations or the Production Timer, and SkyPlanner posts ReportManufacturingOrderOperation to Monitor.

Reporting from both sides duplicates time and quantities.

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

The main conflict source is planners still working the priority plan. Rescheduling according to New finish and dragging rows in Priority planning overwrite the dates SkyPlanner wrote. Once SkyPlanner owns the sequence, Priority planning becomes a view. With Autopilot, SkyPlanner reschedules automatically when production changes.

• Availability factor. Monitor reduces gross capacity to net with the availability factor, 80 % by default on a new work center. Apply it once, as SkyPlanner efficiency or as shorter shifts, never both.
• Time precision. Work centers on Day planning carry capacity as basic time per day, with no shift times. Map real shifts in SkyPlanner from production schedules so jobs land inside working hours.
• Queue time and overlap. Operation rows carry queue time and overlap in %. Decide in scoping how each maps to SkyPlanner, or lead times change after go-live.
• Pools. Pool work centers are planned in Pool planning, not Priority planning. Read the incorporated work centers, not only the pool row.
• Version gates. Planned dates through Update need 24.5. Work center capacity fields in the API need 24.3, and OIDC needs 25.8. Check the build before scoping.
• Network and certificate. On-premises Monitor serves the API on port 8001 with a self-signed certificate. SkyPlanner runs in the cloud, so plan a firewall rule or a relay and trust the certificate explicitly.
• Licences. Each third-party application that writes needs its own API licence users. One read-only API user ships with every system.