Integrations / ERP / Senior ERP
Senior ERP Integration Guide for Production Scheduling with SkyPlanner APS
This Senior ERP integration guide shows partners and IT teams how to connect Senior ERP by Senior Sistemas (Gestão Empresarial | ERP XT with Senior X) to SkyPlanner APS. SkyPlanner integrates with Senior ERP in both directions, using Senior’s own interfaces:
- Production orders (OPs) with their stages, routings (roteiros), resources and resource centers, SKUs, product structures, stock and purchase orders flow in.
- Planned start and end per OP stage, and the resource chosen for each stage, go back to the OP.
- Operator timelogs post back as apontamentos de produção, if you choose.
- Senior X Events Hub tells SkyPlanner when an OP stage changes status, and SkyPlanner webhooks push schedule changes as they happen.
The SkyPlanner team configures the integration to your Senior ERP 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.
Senior ERP’s integration interfaces
ERP XT is a hybrid. Senior’s documentation says Gestão Empresarial XT “becomes a hybrid system: an on-premises (local) system with integration of cloud solutions” (Senior documentation, translated). A scheduler uses three Senior interfaces:
- G5 web services (SOAP). Services on your Senior server, named by module (com.senior.g5.co.<module>…). Each is published in three WSDL flavors: sapiens_Sync, sapiens_Async and sapiens_Scheduled. Production services include com.senior.g5.co.mpr.pcp.ordemproducao, which “calls the same production order generation routine” as the ERP screen (Senior documentation, translated), and services for products (com.senior.g5.co.ger.cad.produto) and production reporting.
- Senior X Platform REST APIs at api.senior.com.br, for the ERP domains Senior exposes on Senior X, such as products and sales orders (Senior documentation).
- Events Hub webhooks. Created in Senior X under Tecnologia > Customização > Events Hub > Webhooks. Manufacturing publishes the event erp_man/pcp_programacaocontrole/orderProductionStageChangeStatus when an OP stage changes status (Senior documentation).
Authentication and access
- Senior X Platform. The integration logs in with POST to platform.senior.com.br at /t/senior.com.br/bridge/1.0/rest/platform/authentication/actions/Login, with the user as user@tenant. The response holds a Bearer access token and a refresh token. Application keys can log in with loginWithKey (access key, secret, tenant). REST calls carry the authorization header and a client_id header that identifies the connecting application, registered in the Senior API portal and linked to a role in the ERP.
- G5 web services. Calls carry user, password and encryption parameters. With a Senior X token, the token replaces the password (Senior documentation).
- Permissions. Create a dedicated Senior user for the integration, with access to the PCP, engineering, stock and purchasing data it reads and writes.
On the SkyPlanner side, the REST API authenticates with an API token in the Authorization-Token header (SkyPlanner Settings > API) and is documented in Swagger/OpenAPI. The integration tutorial walks through the first calls.
Events and polling
Events Hub covers the shop-floor side: when an OP stage changes status, the webhook reaches SkyPlanner and the schedule updates. Other data is polled. Reads filtered to firm and released OPs and recent changes pick up new work. The frequency is set per plant, from every few minutes for OPs to hourly for stock.
SkyPlanner sends webhooks when state or the schedule changes, so the write-back side is event-driven.
Data mapping
| Senior ERP object (interface) | SkyPlanner object | Direction | Frequency |
|---|---|---|---|
| SKU: produto and derivação, units of measure (G5 web services or Senior X entities) | Products and materials | Senior → SkyPlanner | Initial load, then polling |
| Product structure (engenharia do SKU) | Product structure, subproducts, materials per product | Senior → SkyPlanner | Initial load, then on change |
| Roteiro with estágios: sequence, dependency on the previous stage | Process steps in order | Senior → SkyPlanner | Initial load, then on change |
| Recurso: Tempo processo, Tempo setup, Tempo carga e descarga, Tempo transferência, Fator de carga | Workstations, durations, setup and teardown times, efficiencies | Senior → SkyPlanner | Initial load, rarely after |
| Centro de recurso | Workstation groups | Senior → SkyPlanner | Initial load, rarely after |
| Calendário: Feriados, production calendar per shift | Shifts and non-working days | Senior → SkyPlanner | Daily, or own shifts in SkyPlanner |
| Ordens de produção (Firme, Liberada) with stages and materials | Orders and jobs with due dates and material needs | Senior → SkyPlanner | Polling every few minutes |
| OP stage status (Events Hub orderProductionStageChangeStatus) | Job progress | Senior → SkyPlanner | Real time via webhook |
| Estoque per SKU | Stock balances | Senior → SkyPlanner | Polling, hourly or on schedule run |
| Ordens de compra with delivery dates | Purchase orders, incoming material by delivery date | Senior → SkyPlanner | Polling, hourly or on schedule run |
| OP stage: planned start and end, resource | Planned start and end per job, assigned workstation | SkyPlanner → Senior | On schedule change, via SkyPlanner webhook |
| Apontamento de produção: numOrp, codEtg, seqRot, qtdRel, qtdRfg, start and end date and time | Timelogs and operator confirmations | SkyPlanner → Senior | Per confirmation or per shift, if chosen |
| Not in Senior ERP | Setting time matrix, tools as finite resources, multi-operator jobs, alternative machines and personnel | Maintained in SkyPlanner | Set up during onboarding |
Integration patterns
1. Initial master data load. Read SKUs, structures, roteiros, recursos, centros de recurso and the production calendar. Map resource centers deliberately: a centro de recurso with four machines becomes one workstation group or four workstations. Convert Fator de carga into SkyPlanner workstation efficiency or into shifts, not both.
2. OP sync. Read OPs in Firme and Liberada situations with their stages and materials, plus open purchase orders. Planejada OPs can still be changed or deleted by MRP, so schedule them only if you want a forward view. SkyPlanner treats ordered material as available on the PO delivery date and updates stock when the PO is marked Delivered.
3. Schedule write-back. When the engine places or moves a stage, a SkyPlanner webhook triggers the write-back. It sets the planned start and end of each OP stage and the resource chosen for it, the same fields the planner edits in Programação de produção. The SkyPlanner team agrees the exact web service with you and your Senior partner during 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 to Senior. If yes, each confirmation becomes an apontamento de produção on the OP stage, with quantity produced, scrap and start and end times. Senior accepts production reports only on OPs in situation Liberada or Andamento. If you report through Fábrica ao Vivo, SkyPlanner reads the progress through Events Hub instead.
5. Ownership and conflict rules. Write them down before go-live:
| Data | Owner |
|---|---|
| SKUs, structures, roteiros, OP quantities and situation | Senior ERP |
| Stage sequence, start and end times, resource assignment | SkyPlanner |
| Setting time matrix, tool and operator requirements, alternative resources | SkyPlanner |
| Production calendar and shifts | One system, chosen in scoping |
| Apontamentos, stock movements, costing | Senior ERP, entered there or posted from SkyPlanner timelogs |
Pick one writer of stage dates. If planners still sequence the same OPs in Programação de produção or the Gantt chart, agree which OPs SkyPlanner owns.
Typical project steps
Implementation is normally completed within weeks after onboarding starts. Before that, validate the schedule in the 30-day free trial with resources, roteiros and open OPs exported from Senior as CSV or Excel.
- Mapping. Fix the mapping table, ownership rules, sync frequencies and whether apontamentos post back.
- Senior access. Create the integration user, register the application in the Senior API portal, and enable the G5 web services and the Events Hub webhook. Test in a homologation base first.
- Initial load. SKUs, structures, roteiros, recursos, centros de recurso, calendar.
- OP and purchase order sync. Polling with filters and retries, plus the stage status webhook.
- Constraint setup in SkyPlanner. Setting time matrix, tools, operator counts per job and alternative machines or personnel.
- Schedule write-back. Stage dates and resources from SkyPlanner webhooks, plus apontamentos 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 Senior ERP integration
- Four resource times. Recurso holds process, setup, load and unload, and transfer time. Load and transfer time can be handling, not machine time. Decide per resource how each maps, or every duration is wrong.
- One setup per resource. Senior’s Tempo setup is a single value. Build the setting time matrix in SkyPlanner from your real changeovers during onboarding.
- Derivations. A SKU in Senior is a product plus a derivação, and roteiros can differ per derivation. Carry the derivation code into SkyPlanner product keys.
- OP situations. Only Liberada and Andamento OPs accept production reports. Keep situation changes in Senior and let SkyPlanner follow them through Events Hub.
- Hybrid deployment. G5 web services run on your Senior server and Events Hub runs in Senior X. Plan network access for both.
- Number format. Senior’s web services reject numbers with thousands separators and require a decimal comma. Send numbers in that format.
Who configures and supports the Senior ERP integration
- The SkyPlanner team configures it during onboarding and supports it after go-live, across the agreed web services, Senior X APIs and Events Hub webhooks. Every plant runs Senior ERP differently, and this is where that know-how goes.
- Your Senior partner can take part. The partner knows your setup, customizations and licensing, and can set up the integration user, API portal registration and web services 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, Senior ERP finite capacity scheduling, the Senior ERP 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.
1,000swork orders scheduled automatically
“Production is under control in a different way, and our understanding of capacity is on a completely different level.”
Hannu Ryynänen, CEO
Mamec · Industrial mixers, pumps and high-tech contract manufacturing
Thousands of work orders are scheduled automatically, with a real-time view of production for the whole organization.
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 Senior ERP have an API for production orders?
Yes. The G5 web service com.senior.g5.co.mpr.pcp.ordemproducao generates OPs with the same routine as the ERP screen, and other G5 services cover products and production reporting. Senior X Platform adds REST APIs with Bearer token login and Events Hub webhooks.
Does Senior ERP support webhooks?
Yes. Senior X Events Hub sends webhooks, including orderProductionStageChangeStatus when an OP stage changes status. SkyPlanner uses it to follow shop-floor progress in real time, and its own webhooks push schedule changes back.
How are planned dates written back to Senior ERP?
SkyPlanner sets the planned start and end of each OP stage and the resource chosen for it, the same fields the planner edits in Programação de produção. A SkyPlanner webhook triggers the write-back whenever the schedule changes, over the route the SkyPlanner team sets for your Senior installation during onboarding scoping.
Does the integration work with Senior X and ERP XT?
Yes. ERP XT runs on your server with cloud services on Senior X. The integration uses G5 web services on the server and Senior X APIs and Events Hub in the cloud.
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 Senior, no credit card needed. Start the trial, or talk to sales to scope the integration.
