Integrations / ERP / Divalto infinity
Does Divalto Have Finite Capacity Scheduling? Jalonnement, Opcenter APS and SkyPlanner APS
Partly. Divalto infinity plans manufacturing orders (OF) with jalonnement, and Divalto’s own documentation calls it infinite capacity. Finite scheduling comes through Ordonnancement Opcenter APS, the Siemens scheduler that the planner runs from the Production menu with a file export and import. Plants that want every machine, person, tool and material scheduled finitely, and a plan that keeps itself current, run SkyPlanner APS beside Divalto.
This article follows Divalto’s user documentation for Divalto infinity production (GPAO) and its Opcenter APS setup pages.
How Divalto schedules, step by step
1. Master data: centres de charge, postes and calendars
Capacity starts with ateliers, centres de charge and postes de travail. Each poste has a calendar. Ressources, opérateurs with their habilitations, and outillages are kept in master data and are exported to the scheduler when Opcenter APS is used.
2. Gammes and nomenclatures
The nomenclature lists components. The gamme lists séquences, each on a centre de charge or poste, with its times, ressources and outillages. Divalto handles chevauchement (overlapping séquences) and fractionnement (splitting a séquence).
3. OF launch
OF are created manually, from the customer order, by validating the CBN (net requirements calculation) or per affaire. Divalto’s page puts it this way: “lancez vos OF manuellement, à la commande ou par validation du calcul des besoins nets ou à l’affaire” (Divalto OF).
4. Jalonnement: infinite by design
Jalonnement places each séquence of an OF on the poste calendar. There are four types: backward from the requested end date (used by the CBN and by OF generated from orders), forward from an end date, forward from a start date (manual entry only) and backward from a start date.
Divalto is explicit about capacity. The run calculates a poste’s theoretical capacity “sans tenir compte des autres charges induites par d’autres OF à la même date et sur le même poste ou centre. Il s’agit d’un jalonnement à CAPACITE INFINIE, raisonnement logiquement appliqué par les ERP.” (Divalto docs) In plain English: other OF on the same poste on the same day are not counted.
Dates are revised after time entries, and only a principal OF can be rejalonné.
5. Plan de charge and Gantt
The plan de charge “illustre la charge induite par le portefeuille des OF sur les différents centres de charge et postes de travail,” by day, week or month, sorted by centre or poste (Divalto planification). OF administration shows a Gantt of the jalonnement. The planner sees overloads and moves work by hand.
6. Ordonnancement Opcenter APS: the finite part
For finite scheduling, Divalto connects Siemens Opcenter APS (formerly Preactor). Its goal, in Divalto’s words: “Planifier automatiquement en prenant en compte de la capacité finie de chacun des moyens de production et pas uniquement sur le poste de travail ‘goulot d’étranglement’.” Opcenter APS handles change matrices for tools and material and static material control.
The cycle runs in four steps:
- OF are created in Divalto.
- The planner exports production data from Production / O.F. / Mises en production / Ordonnancement.
- The plan is built and saved in Opcenter APS.
- Import ordonnancement brings the planned dates back from an exchange folder.
Setup ticks “ordonnancement” in the Production fiche, which starts a scrutateur, and sets a DIVALTO_ORDO path: “un chemin Windows qui pointe vers le dossier contenant les fichiers .PRCDF”. Data reaches Opcenter APS “par le biais de scripts d’importation”. Divalto states that “Opcenter APS est donc déclenché par l’utilisateur.” Grouping rules such as color or material set the Ultimate planning range apart from Standard. (Divalto docs)
What stays with the planner
- Infinite core planning. Jalonnement does not count other OF on the same poste (quoted above).
- Load, not sequence. The plan de charge shows load per centre and poste by period. The planner decides which OF runs first.
- Manual rejalonnement. After a change, the planner rejalonne the principal OF.
- A planner-run scheduling cycle. With Opcenter APS, the planner exports, plans and imports. Between runs, Divalto holds the last imported dates.
- Range-dependent rules. Grouping by color or material is tied to the Ultimate range.
When Divalto scheduling is enough
Divalto’s core planning does the job when:
- One or two bottleneck postes set the pace, and the rest have spare capacity.
- Weekly load per centre de charge is accurate enough for your delivery promises.
- Changeovers are short or do not depend on the product that ran before.
- Operators, shared tools and material arrival do not decide the order of work.
- One planner can level the load by hand each week.
If that fits, keep gamme times and poste calendars realistic, and review the plan de charge after each CBN.
When you need a finite capacity scheduler
You have outgrown jalonnement when several of these are true:
- Delivery dates slip although the plan de charge looks fine by week.
- The planner resequences OF by hand after every rush order or breakdown.
- Setup time depends on the product that ran before.
- Operators, shifts and absences limit output as much as machines do.
- Molds, dies or fixtures move between postes.
- Late components decide which OF can start.
What to look for
- Every resource finite at once: machines, people and tools, not load per period.
- Séquence-level sequencing by priorities and due dates.
- A setting time matrix with sequence-dependent, asymmetric setup times.
- Tools as finite shared resources and multi-operator jobs.
- Material-aware scheduling that checks stock and incoming supplier orders.
- Automatic rescheduling when production progress or orders change.
- A clean Divalto data path. Reads and writes over Divalto’s REST services, with planned dates returned per OF and séquence. Ask every vendor how dates reach your OF and who supports it after go-live.
The options fall into three groups:
- Divalto core planning: jalonnement, plan de charge and Gantt inside Divalto.
- Enterprise APS connected to Divalto, such as Opcenter APS through its export and import cycle, run by a planner.
- Cloud APS with shop-floor execution, where SkyPlanner sits. It schedules every resource automatically beside Divalto and puts the plan in operators’ hands.
For the wider picture, see advanced planning and scheduling and finite capacity scheduling.
Where SkyPlanner fits
SkyPlanner APS closes each gap listed above. Every workstation, person and tool is finite. The Arcturus AI engine builds a séquence-level schedule in seconds, sequenced by job priority, completion date, customer priority, Fast Track and Dynamic Priorities.
Its setting time matrix holds the setup time between each pair of products in both directions, and the engine picks the order with the least setup. “Allow similarity” groups jobs by a property such as a tool. Tools are finite shared resources, several people can work the same job at once, and work moves to alternative postes or personnel when the primary one is unavailable.
Material-driven scheduling simulates future inventory from stock and incoming supplier orders, so an OF is planned when its components are there. Autopilot reschedules automatically when production changes, and Running Time Lock freezes the next hours of work so the floor is not disrupted. Operators log work on phone or tablet with Mobile Confirmations, Production Timer and Quick Log Mode.
Choose SkyPlanner over Opcenter APS when:
- The plan must keep itself current. Divalto states that Opcenter APS is started by the user, then dates are imported (Divalto docs). Autopilot replans automatically on every meaningful change.
- You want cloud software, not an exchange folder. Opcenter APS exchanges files through a Windows path and import scripts. SkyPlanner works over Divalto’s REST services and runs live within weeks after onboarding starts.
- Changeovers decide your output. Divalto ties grouping rules by color or material to the Ultimate range. SkyPlanner’s setting time matrix and “Allow similarity” plan setups on every schedule.
- Every operator should see the plan. Users are unlimited, and Mobile Confirmations put the queue on every phone or tablet.
Start with an Excel export of open Divalto OF in the 30-day free trial (up to 20 workstations, all Basic features, no credit card). After that, pricing is 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.
SkyPlanner integrates with Divalto in both directions: it reads OF through RecordSql and writes planned OF and séquence dates back with GG_DATES_ORDO through the create_dataxml web service. The SkyPlanner team configures it during onboarding, and your partner or developers can work on the documented REST API. See the SkyPlanner for Divalto page, the Divalto integration guide or all ERP integrations.
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.
98%delivery reliability, up from about 50%
“SkyPlanner plays a decisive role in maintaining our delivery reliability.”
Hannu Lahtinen, Managing Director
KJH-Comp · Sheet-metal mechanics and contract manufacturing
Delivery reliability rose from around 50% to as high as 98%, and scheduling now needs one supervisor instead of two.
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.
FAQ
Is Divalto jalonnement finite or infinite capacity?
Infinite. Divalto’s documentation states that jalonnement calculates a poste’s theoretical capacity without counting other OF on the same poste and date. The plan de charge then shows the resulting load per centre and poste.
What is Ordonnancement Opcenter APS in Divalto?
It is Divalto’s connection to Siemens Opcenter APS, formerly Preactor. Divalto exports production data, the planner builds the finite plan in Opcenter APS, and the planned dates are imported back from an exchange folder.
Does Divalto handle sequence-dependent setup times?
Not in jalonnement, where each séquence carries its own times from the gamme. Opcenter APS adds change matrices. SkyPlanner’s setting time matrix stores setup times between product pairs in both directions and sequences jobs to minimize them on every replan.
Can SkyPlanner write planned dates back to Divalto?
Yes. SkyPlanner sends a GG_DATES_ORDO file through the create_dataxml web service with planned start and end dates per OF and per séquence, and a new centre or poste when work moves.
Can I test SkyPlanner before integrating it with Divalto?
Yes. Import open OF, gammes and postes from Divalto as Excel or CSV during the 30-day trial and compare the schedule with your current plan. See pricing, start the trial or talk to sales.
