Order scheduling. Simple. Efficient.

Apex schedules production orders across machines, people and shifts, taking material and your operating rules into account. An AI agent lets you request plans and compare alternatives in chat. The aim is less manual coordination and a clear basis for deciding which schedule to release.

Apex is designed for discrete manufacturing: individual parts and assemblies with defined operations, resources and dependencies. Examples include machinery, metalworking, automotive suppliers and electronics assembly. The planning model is configured for your shop floor, including alternative machines, lot sizes and shared resources.

You can keep your existing systems. ERP manages orders and master data, MES supports production execution, and Apex adds detailed scheduling and scenario analysis. It covers tasks associated with Advanced Planning and Scheduling (APS); whether it supplements or replaces an existing planning component depends on your processes and interfaces.

Yes. Connect a compatible AI platform to Apex through MCP or HTTP. Ask for a plan, change assumptions or compare scenarios in chat. Voice input is available if your chosen platform supports it. The agent works with the data and permissions you provide; Apex calculates the schedules.

Yes. Model machine availability, staff, tools, shifts, breaks, setup times and material availability in one scheduling problem. Apex assigns operations within those constraints instead of assuming unlimited capacity. Fixed operations and resource assignments can be retained when you replan.

Create a what-if scenario, change the affected orders or resource availability, and calculate an alternative schedule. Compare completion dates, delays and production times before changing the operational plan. This helps you assess a rush order, an extra shift or a machine outage using the same planning rules.

Yes. Flexible multiobjective optimization lets you weight goals such as delivery performance, completion time, flow time and setup effort. Compare alternatives when goals compete. Mandatory operating rules stay binding regardless of the priorities you choose.

Configure the rules Apex already supports for your production environment. If you need more, the public source code can be extended within your license. A coding agent can help implement and test a rule from your examples. Your team or an implementation partner reviews the change before using the extended version.

Start with orders and due dates, workplans, processing and setup times, machines and other resources, shift calendars and material availability. Add the rules that matter for your process, such as tools, staffing or fixed operations. Missing information and any assumptions should be made explicit before planning.

Yes. Start with an Excel workbook, CSV file or ERP export. An adapter maps the relevant fields to Apex's planning data and flags missing information. Once set up, reuse it for the next import. Sample data works immediately; your own exports need a mapping to your production model.

Yes, through a connector built for the exports or interfaces available in your SAP environment. Orders, workplans, resources and material are mapped with your SAP team. The connection depends on your system version, configuration and permissions; it is implemented and tested for your setup.

MES systems with suitable exports or interfaces can supply planning data. For example, a connector for Siemens Opcenter, SAP Digital Manufacturing or MPDV HYDRA X could read order progress and machine availability. These are integration options, not bundled connectors; the available fields and access rights must be checked for your installation.

Yes, this can be implemented with your own connector and approval workflow. Transfer agreed dates, sequences or resource assignments through the target system's interface: after manual approval, under defined approval rules or automatically at the level you choose. Field mapping, permissions, conflict handling and logging are set up and tested for your system. Write-back is a separate integration step.

Yes. All offers, including Custom, can run locally or in your own cloud. Free, Business, Business Plus and the perpetual license are self-service offers. Connect your own AI models through a compatible agent platform using MCP or HTTP; a cloud-based agent needs a reachable, secured endpoint. We can help with setup, integration and operation under a separate agreement. If you want Qunevo to host Apex, request a Custom license with the services you need.

The Apex scheduling engine can run inside your company. Whether data is sent to an external AI provider depends on the agent platform and its configuration. Define which production data the agent can access, where it is processed and which permissions apply. Hosting Apex locally does not by itself make an external AI service local.

The AI agent handles the conversation, prepares inputs and calls Apex. Apex's scheduling engine calculates and validates the plan. You can also use the engine through its API or command line without a language model. This separates conversational assistance from the scheduling calculation.

Apex and four established optimization methods solve the same benchmark problems. The comparison covers total completion time and total flow time. The published charts aggregate the shared datasets; the methodology explains how runs, configurations and reference values are selected. This is a comparison of algorithms, not commercial APS products.

That depends on your orders, capacity, data and current planning process. Benchmark averages are not a forecast for your factory. Compare Apex with your current plan using the same inputs and rules, then assess delivery dates, production times, setup effort and the time your team spends planning.

The Apex source code is public. The study is available on arXiv, and the benchmark page describes the results and methodology. Reproduction requires the same datasets, configuration, run budget and aggregation.

Download Apex and start with the sample data. Then map an existing export to one planning task and compare the results with your current schedule. The license permits up to 90 days of non-operational evaluation, including shadow tests whose results do not influence live production. Operational use needs the applicable Free or paid entitlement from the start.

The code is public under the APEX Source Available License 1.1. You can inspect it, adapt it and maintain your own version within the licensed scope. This is a source-available license, not an OSI open-source license. Free and commercial use depend on your revenue and use case.

Free use covers a manufacturing company's own production up to and including EUR 2 million annual revenue, and qualifying non-commercial academic research and teaching. Group companies use consolidated group revenue for eligibility. Multi-company operations, SaaS, OEM and white-label use need a separate scope. See the pricing page for the applicable terms.

Yes. The perpetual license is a self-service offer from EUR 8,000 plus taxes. You host Apex yourself and connect your own AI models; we can help with setup and integration under a separate agreement. The quote depends on company size and agreed scope. You may keep using and adapting the purchased version for that scope; later revenue growth does not add license fees. Future versions, additional companies, new uses and services need a separate agreement.

Free, Business, Business Plus and the perpetual license are self-service licenses for your own infrastructure and AI models. We can help with consulting, setup, integration and training for any offer; these services are quoted separately. Custom can also be operated locally. Hosting by Qunevo requires a Custom license, with hosting, AI provider costs and ongoing support agreed in your quote. There is no Apex fee per user or planning run within the licensed scope.

The main factors are data quality, interfaces and your production rules. A first scenario can use an export; regular updates and write-back need more setup and testing. Start with one planning task, identify missing data and agree the connector and approval workflow. This makes the effort concrete before expanding the rollout.

Yes. Qunevo supports production modelling, data connectors, agent setup, custom rules and training with your team's planning tasks. You can commission an assessment, selected implementation work or a complete introduction. Consulting is optional and quoted separately; you may also use your own team or another implementation partner.