Integrations / ERP / PSIpenta
PSIpenta Integration Guide for Production Scheduling with SkyPlanner APS
This PSIpenta integration guide shows PSI partners and IT teams how to connect PSIpenta/ERP to SkyPlanner APS. SkyPlanner integrates with PSIpenta in both directions, using PSI’s own interfaces:
- Production orders (Fertigungsaufträge) with their operations (Arbeitsgänge), routings (Arbeitspläne), BOMs (Stücklisten), work centers, machines, tools (Betriebsmittel), stock and purchase orders flow in.
- Planned start, end and work center per operation go back to the production order.
- Operator timelogs can post back as BDE confirmations (Rückmeldungen), if you choose.
- SkyPlanner webhooks push schedule changes as they happen.
The SkyPlanner team configures the integration to your PSIpenta setup during onboarding and supports it after go-live. This guide is for partners and developers who want to take part, or to build on SkyPlanner’s documented REST API (API reference) themselves.
PSIpenta’s integration interfaces
PSI gives an external scheduler three routes (PSI brochure):
- PSIpenta/ERP REST API. PSI names a REST and SOAP API for PSIpenta/ERP and states that all PSIpenta components can be integrated into existing architectures through RESTful web services. This is the main route for reading production data and writing planned dates.
- PSIpenta/BDE REST and SOAP API. The shop-floor data collection module has its own API. It is the route for posting operator confirmations.
- PSIintegration. PSI’s standard integration layer across PSIpenta modules. It works hub and spoke, maps messages graphically in adapters and archives every message in a database. Use it when your installation already routes outside systems through it.
PSIpenta/ERP 10 adds BPMN 2.0 workflows, built in a web-based Workflow Developer, to integrate external systems (PSI). A workflow can react to a change in PSIpenta and call SkyPlanner.
Authentication and access
- PSIpenta side. The integration runs as a dedicated technical user, with rights limited to the objects it reads and writes. Your PSI partner sets up the user and the API access in your installation.
- Network. PSIpenta usually runs on premises. The integration reaches it through the route your IT team allows, for example a published API endpoint or a small connector inside your network.
- SkyPlanner side. The REST API authenticates with an API token in the
Authorization-Tokenheader, created under Settings > API. The API is documented in Swagger/OpenAPI, and the integration tutorial walks through the first calls.
Events and polling
On the PSIpenta side, the integration polls the REST API for open production orders and recent changes, or a BPMN workflow or PSIintegration message pushes a change to SkyPlanner. The frequency is set per plant, from every few minutes for orders to hourly for stock.
SkyPlanner sends webhooks when state or the schedule changes, so the write-back side is event-driven.
Data mapping
| PSIpenta object | SkyPlanner object | Direction | Frequency |
|---|---|---|---|
| Parts (Artikel), units | Products and materials | PSIpenta → SkyPlanner | Initial load, then polling |
| BOMs (Stücklisten), multi-level | Product structure, subproducts, materials per product | PSIpenta → SkyPlanner | Initial load, then on change |
| Routings (Arbeitspläne) with operations, setup and run times | Process steps with durations, setup and teardown times | PSIpenta → SkyPlanner | Initial load, then on change |
| Work centers (Arbeitsplätze) and machines | Workstations, workstation groups, efficiencies | PSIpenta → SkyPlanner | Initial load, rarely after |
| Tools and fixtures (Betriebsmittel) | Tools as finite shared resources | PSIpenta → SkyPlanner | Initial load, then on change |
| Shift calendars | Shifts and non-working days | PSIpenta → SkyPlanner | Daily, or own shifts in SkyPlanner |
| Production orders (Fertigungsaufträge) with operations and material | Orders and jobs with due dates and material needs | PSIpenta → SkyPlanner | Polling every few minutes |
| Stock on hand | Stock balances | PSIpenta → SkyPlanner | Polling, hourly or on schedule run |
| Purchase orders (Bestellungen) with delivery dates | Purchase orders, incoming material by delivery date | PSIpenta → SkyPlanner | Polling, hourly or on schedule run |
| Planned start, end and work center per operation of the production order | Scheduled start and end per job | SkyPlanner → PSIpenta | On schedule change, via SkyPlanner webhook |
| BDE confirmations (Rückmeldungen): time and quantity per operation, employee | Timelogs and operator confirmations | SkyPlanner → PSIpenta | Per confirmation or per shift, if chosen |
| SkyPlanner scheduling rules | Setting time matrix, operator counts per job, alternative machines and personnel | Maintained in SkyPlanner | Set up during onboarding |
Integration patterns
1. Initial master data load. Read parts, BOMs, routings, work centers, machines, Betriebsmittel and calendars through the PSIpenta/ERP REST API. Map work centers deliberately: a work center with four machines becomes one workstation group or four workstations.
2. Order sync. Read released production orders with their operations and material, plus open purchase orders. SkyPlanner treats ordered material as available on the PO delivery date and updates stock when the PO is marked Delivered. Purchase proposals stay in PSIpenta until they become orders.
3. Schedule write-back. When the engine places or moves an operation, a SkyPlanner webhook triggers a call to the PSIpenta/ERP REST API. It updates the planned start, planned end and work center of that operation on the production order. The order’s dates follow from its operations. The resources and fields for your installation are set during onboarding scoping.
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. If yes, time and quantity post per operation as BDE confirmations through the PSIpenta/BDE API. If BDE terminals stay in use, SkyPlanner reads the confirmations from PSIpenta instead.
5. Ownership and conflict rules. Write them down before go-live:
| Data | Owner |
|---|---|
| Parts, BOMs, routings, quantities, order status | PSIpenta |
| Operation sequence, start and end times, machine assignment | SkyPlanner |
| Setting time matrix, operator counts, alternative resources | SkyPlanner |
| Betriebsmittel master data | PSIpenta; availability over time planned in SkyPlanner |
| Shifts and non-working days | One system, chosen in scoping |
| Confirmations, material issues and receipts | PSIpenta, entered there or posted from SkyPlanner timelogs |
Pick one writer of operation dates. If the Leitstand, Adaptive Planung or MES Scheduling also sets planned dates, switch that off for the orders SkyPlanner schedules.
Typical project steps
Implementation is normally completed within weeks after onboarding starts. Before that, validate the schedule in the 30-day free trial with work centers, routings and open production orders exported from PSIpenta as CSV or Excel.
- Mapping. Fix the mapping table, ownership rules, sync frequencies and whether confirmations post back.
- PSIpenta access. Create the technical user, enable the API routes with your PSI partner and test in a test installation first.
- Initial load. Parts, BOMs, routings, work centers, machines, Betriebsmittel, calendars.
- Order and purchase order sync. Polling with filters, paging and retries, or workflow-triggered messages.
- Constraint setup in SkyPlanner. Setting time matrix, tools, operator counts per job and alternative machines or personnel.
- Schedule write-back. Operation dates from SkyPlanner webhooks, plus BDE confirmations if chosen.
- Parallel testing. Run SkyPlanner beside the current plan, compare dates, fix master data.
- Go-live. Switch on write-back once the data matches.
What to plan for in a PSIpenta integration
- Module mix. Check which PSI planning modules are licensed and live. Each one that writes dates needs a clear rule.
- Work center or machine. Decide whether SkyPlanner schedules on the work center or on the machine level, and keep it the same in both directions.
- Betriebsmittel. Fixtures and tools from the Betriebsmittel list become finite tools in SkyPlanner, so an operation books its tool too.
- Setup and run time units. Convert setup and run times with the right unit and basis on import, or every duration is wrong.
- External operations. Subcontracted operations are elapsed time, not your capacity. Model them as time-only steps.
- Started operations. Read progress from confirmations before each run, so the schedule starts from work already done. Running Time Lock then freezes the next hours of work.
Who configures and supports the PSIpenta integration
- The SkyPlanner team configures it during onboarding and supports it after go-live, across the agreed API calls and messages. Every plant runs PSIpenta differently, and this is where that know-how goes.
- Your PSI partner can take part. The partner knows your modules, custom fields and PSIintegration setup, and can open the API access alongside the SkyPlanner team.
- Your own developers can build on it against SkyPlanner’s REST API with an API token. An API token is enough to start, and the SkyPlanner team assists when needed. Integration documentation is at SkyPlanner integration docs.
SkyPlanner starts from 199 € per month with 5 workstations included, billed monthly. The integration is quoted up front for your process and needs, together with your plan. See pricing, PSIpenta finite capacity scheduling, the PSIpenta page and the ERP integrations hub.
SkyPlanner reviews from manufacturers
2 hsaved every week
“SkyPlanner has taken our production planning from Excel spreadsheets to real-time production optimization.”
Kalle Kalliomäki, Supply Chain Specialist
UTU · Electrical switchboards and switchgear
Production planning saves 2 hours of working time every week, and a new work queue reaches the line in seconds.
+90%production efficiency
“Efficiency has gone up 90% in production.”
Abdul Rucyinga, Head of IT
Laboratory & Allied · Pharmaceutical manufacturing
Production efficiency is up 90%, and a three-month optimized plan across all workstations takes under 30 minutes.
100%delivery reliability since 2021
“SkyPlanner gives us visibility into capacity and makes planning predictable.”
Dan Berglund, COO/CFO
Opes Corporation · Chemical and food manufacturing
Delivery reliability has been 100% for the entire time SkyPlanner has been in use, since 2021.
Fewerstoppages from material shortages
“The value SkyPlanner brings us is that it is a tool that works in daily use, especially for setting delivery dates.”
Tommi Männistö, Production Planning Manager
Eskomatic · Contract machining
Automatic load scheduling gives more accurate delivery dates, and production stoppages caused by material shortages have fallen sharply.
FAQ
Does PSIpenta have an API for production orders?
Yes. PSI names a REST and SOAP API for PSIpenta/ERP and PSIpenta/BDE, and says all PSIpenta components can be integrated through RESTful web services. PSIintegration adds a message-based integration layer across modules.
How are planned dates written back to PSIpenta?
Through the PSIpenta/ERP REST API. On every schedule change, a SkyPlanner webhook triggers the update of planned start, planned end and work center for each operation of the production order.
Can SkyPlanner post confirmations to PSIpenta BDE?
Yes, if you choose. Operator timelogs from SkyPlanner post as BDE confirmations with time and quantity per operation through the PSIpenta/BDE API. Plants that keep BDE terminals let SkyPlanner read the confirmations instead.
Should a PSI partner propose the PSIpenta Leitstand or SkyPlanner?
SkyPlanner, when the customer wants a working finite schedule in weeks. The Leitstand, Adaptive Planung and MES Scheduling are separate modules of PSI’s modular product (PSI). SkyPlanner connects through the PSIpenta/ERP and BDE APIs, reschedules automatically when production changes, plans changeovers, tools, crews and material, and has unlimited users, from 199 € per month.
Does the integration need PSIpenta/MES?
No. SkyPlanner connects to PSIpenta/ERP and, for confirmations, PSIpenta/BDE. Operators can log work in SkyPlanner on phone or tablet.
Can we test SkyPlanner before building the integration?
Yes. The 30-day free trial supports up to 20 workstations with CSV or Excel imports from PSIpenta, all Basic features and no credit card. Start the trial, or talk to sales to scope the integration.
