Full comparison matrix
Values are categorical: Yes, Partial, Verify with vendor or Not primary focus. There are no scores. "Verify with vendor" means current public documentation did not confirm the capability either way.
| Attribute | JobBOSS² | PlanetTogether | Asprova | Skody AI |
|---|---|---|---|---|
| Primary product category | Job-shop ERP | APS platform | APS platform | Production scheduling / decision layer |
| Best fit | Shops needing shop-management ERP | Planner-owned APS over an ERP | Detailed sequencing at scale | High-mix shops keeping their ERP |
| ERP included | Yes | Not primary focus | Not primary focus | Not primary focus |
| Designed to complement ERP | Not primary focus | Yes | Yes | Yes |
| Finite capacity | Partial — verify depth with vendor | Yes | Yes | Yes |
| Machine constraints | Partial — verify with vendor | Yes | Yes | Yes |
| Labour capacity | Verify with vendor | Verify with vendor | Verify with vendor | Yes |
| Operator skills | Verify with vendor | Verify with vendor | Verify with vendor | Yes |
| Material constraints | Yes — via MRP/inventory | Yes | Yes | Yes |
| Setup sequencing | Verify with vendor | Yes | Yes | Yes — setup families and clustering |
| Outside processing | Yes — as purchased service; verify scheduling treatment | Verify with vendor | Verify with vendor | Yes |
| Dynamic rescheduling | Not primary focus | Planner-triggered; verify event triggers | Fast re-sequencing; verify event triggers | Primary focus — recomputes from current ERP and floor state |
| Multi-pallet / lights-out manufacturing | Verify with vendor | Verify with vendor | Verify with vendor | Yes |
| Visualisation | ERP dashboards and job views | Gantt and planning views | Gantt and sequencing views | Gantt, worker schedule, bottleneck map, late-job and capacity views |
| Enterprise planning depth | Not primary focus | Yes | Yes | Partial — focused on the shop, not network planning |
| Implementation complexity | Low to moderate — but it is an ERP change | Moderate to high | High | Low to moderate |
| High-mix suitability | Suitable as an ERP | Strong | Strong | Primary focus |
Compiled from public vendor documentation, September 2026. No vendor paid for placement. Verify critical requirements directly.
Choose JobBOSS² if…
…the gap is the system of record. JobBOSS² is a shop-management ERP built for job shops, covering estimating and quoting, job management, purchasing, inventory and the accounting ecosystem around them, with scheduling included. If quoting lives in spreadsheets, job costs are reconstructed after the fact, or the current ERP is being replaced anyway, buying a scheduling layer first solves a symptom. Verify the current feature set and scheduling depth with ECI before purchase.
Choose PlanetTogether if…
…you want an established APS engine layered on an ERP, owned by a production planner who wants direct control of scenarios and optimisation rules. It is a common choice in mid-market and larger plants running a mix of repetitive and make-to-order work, and it has a mature partner and integration ecosystem. Verify connector coverage for your ERP and how rescheduling is triggered.
Choose Asprova if…
…the scheduling problem is detailed and large: many operations, sequence-dependent setups, and a requirement for a deeply configured model. Asprova has a long track record in detailed production scheduling and suits organisations with the internal or partner expertise to build and maintain the configuration. Verify current deployment options and labour-modelling depth.
Choose Skody if…
…the existing ERP is staying, but the manufacturer wants a schedule that continuously adapts to machine, labour, material and priority changes. Skody reads current production information from the ERP and recomputes the finite-capacity schedule against machines, operators and skills, shifts and calendars, material readiness, outside processing, setups, pallets and unattended running, and today's priorities. It is not an ERP and does not attempt enterprise network planning.
The architectural difference
ERP: orders → routings → inventory → transactions
APS: ERP data → constrained optimisation → production plan
Decision layer: ERP / current state → finite-capacity schedule → actual changes → recompute → updated decisions
This is a simplification. Real products blur the boundaries: some ERPs include finite-capacity scheduling, and some APS platforms support frequent re-optimisation. The diagram is useful for deciding which layer you are missing, not for judging any individual product.
Example: a Tuesday morning disruption
Consider a hypothetical job shop: 50 work centres, 20 operators with different skill qualifications, 300 active jobs. On Tuesday morning a customer expedites an urgent order, machine #17 goes down, and two operations run long.
What to ask each vendor about this scenario
Rather than assuming how each product behaves, put the scenario in front of the vendor and ask: what changes on the screen, who has to act, and how long does it take?
- Does the system recalculate the remaining sequence, or does it show the original plan with the disruption noted?
- Are the operators qualified for the displaced work identified automatically, or does the planner check a skills matrix by hand?
- When machine #17 is marked down, does downstream capacity and every affected due date update?
- Does inserting the expedite show which existing promises are now at risk, before the decision is committed?
- How long does a full recalculation take at 300 active jobs across 50 work centres?
- Who performs the recalculation — a planner running a job, or the system on an event?
We deliberately do not state how JobBOSS², PlanetTogether or Asprova respond to this scenario. Their behaviour depends on configuration and version, and asserting it without verification would be exactly the sort of claim this page exists to avoid.
Which one should I choose?
| Buyer profile | Where to start |
|---|---|
| Existing ERP is staying, and schedule volatility is the problem | Investigate Skody — a decision layer over the ERP |
| Need a new job-shop ERP: quoting, jobs, purchasing, costing | Investigate JobBOSS² |
| Want an established traditional APS owned by a planner | Investigate PlanetTogether and Asprova together |
| Standardising planning across multiple plants | Investigate enterprise APS/MOM suites such as Siemens Opcenter APS |
The distinction matters more than any feature list. An ERP purchase replaces your record of truth and touches every department. An APS purchase adds a planning engine and a planner's workflow. A decision layer leaves both in place and changes how often the schedule is right. Buying the wrong layer produces an expensive project that does not fix the complaint.
Frequently asked questions
Is Skody an ERP?
No. Skody is a production scheduling and decision layer that connects to an existing ERP. It does not provide order entry, purchasing, inventory, MRP or accounting; it reads production information from the ERP and computes a finite-capacity schedule against current shop conditions.
Is JobBOSS an APS system?
JobBOSS² is fundamentally an ERP for job shops — quoting, jobs, purchasing, inventory and costing — with scheduling included as part of the system. Buyers should evaluate its scheduling depth on their own routings rather than assuming parity with a dedicated APS engine.
What is the difference between Asprova and PlanetTogether?
Both are established APS platforms that layer finite-capacity scheduling over an ERP. They differ in configuration style, deployment model and ecosystem rather than in category. Compare them on labour modelling, sequence-dependent setups, recalculation speed at your operation count and connector coverage for your ERP.
Which is best for high-mix manufacturing?
For high-mix, low-volume work all four can be shortlisted, but for different reasons: JobBOSS² if the ERP itself is the gap, Asprova or PlanetTogether if you want a planner-owned APS engine, and Skody if the ERP stays and the problem is that the schedule stops matching the floor during the day.
Which works with an existing ERP?
PlanetTogether, Asprova and Skody are all designed to work alongside an ERP rather than replace it. JobBOSS² is the ERP, so it is the alternative to your current system of record rather than a layer on top of it.
Which can account for labour constraints?
Skody schedules operator availability and skills as constraints alongside machines. For PlanetTogether, Asprova and JobBOSS², verify labour and skills modelling directly with the vendor — several systems represent labour as a shift calendar rather than as named skills.
Do I need APS if my ERP already has scheduling?
Not necessarily. If the ERP scheduler produces a plan operators actually follow, you do not have a scheduling software problem. Dedicated scheduling earns its place when routings vary, resources are shared, labour skills constrain capacity, and the plan is invalid within hours.
Can any scheduler automatically recover from disruptions?
No system removes the disruption. What a scheduler can do is recompute a feasible sequence quickly enough that the planner decides with current information instead of guessing. Ask each vendor what triggers a recalculation, how long it takes and which constraints are included.
Sources and verification
Statements on this page are drawn from each vendor's own public product information. Where documentation did not confirm a capability, the page says "verify with vendor" rather than guessing. Product functionality changes; confirm anything critical directly with the vendor.
- JobBOSS² (ECI Software Solutions)Product category as a job-shop ERP with scheduling included. Checked 6 September 2026.
- PlanetTogetherProduct category, APS positioning and ERP-integration approach. Checked 6 September 2026.
- AsprovaProduct category, finite-capacity scheduling scope and deployment model. Checked 6 September 2026.
- Siemens Opcenter APSEnterprise APS positioning and planning/scheduling scope. Checked 6 September 2026.
- Skody AISkody's own product scope, constraints modelled and ERP-integration approach. Checked 6 September 2026.
Editorial methodology
- Products were selected for their relevance to discrete production scheduling, not for commercial relationships.
- Comparisons use publicly available vendor documentation and product information current as of September 2026.
- Skody AI is included because Skody publishes this page. We say so plainly rather than presenting the comparison as third-party research.
- No vendor paid for placement, ranking or inclusion. There are no editorial scores and no reviews on this page.
- Product functionality changes. Buyers should verify every critical requirement directly with each vendor before purchase.
Last reviewed: September 2026
See how Skody schedules a real high-mix shop
Two published customer accounts show what finite-capacity rescheduling looks like against a live floor: a machine shop and a precision contract manufacturer, both keeping the ERP they already had.