Frequently asked questions

OPLAN is web-based supply chain planning software for manufacturers. Four modules run on the OPLAN CORE: Demand Planning, S&OP (sales and operations planning), Finite Capacity Planning and Machine Scheduling. From the demand forecast to the machine sequence, the plan is chained through the same master data and the same rules.

Yes. OPLAN CORE is the mandatory foundation, installed with the first module; modules are licensed one by one. They connect through the core's plan data bus rather than directly: when a module is missing, integration, a file or manual entry fills the same table. So a single-module installation works fully, and adding a module later needs no data migration.

Five process flow types: discrete (work order → operation), batch / process (batch → recipe), continuous (campaign block), assembly line (takt, mixed-model sequence) and project (ETO). The flow type is chosen per production area, not per company; capacity unit, batching logic, setup model and scheduling behaviour follow from it.

The sales history is cleansed first: missing periods, unmet demand during stock-outs, promotion spikes and outliers (median + MAD) are corrected. The cleansed series is backtested across an 11-model pool (naive, moving averages, exponential smoothing, Holt, Holt-Winters, Croston, TSB …); the model with the lowest WMAPE is selected with its rationale. The final plan's contribution to accuracy is measured with FVA.

In finite mode, load above capacity is pulled forward, moved to an alternative machine, split if needed or pushed back; no work centre × week cell exceeds 100%, and work that does not fit is listed separately in the bottleneck report — this is the plan released to production. In infinite mode nothing moves; the output is not a plan but a measure of the raw capacity need, the basis for investment, shift and outsourcing decisions.

OPLAN's integration contract defines 29 data sets and 241 fields (ERP → OPLAN, OPLAN → ERP, MES → OPLAN, OPLAN → MES, between modules); it is shared as CSV with your ERP / MES team. Data arrives by CSV / Excel file, token-protected REST API, database view or manual entry; the field-mapping screen uses your ERP's column names. Generic CSV / Excel and REST API are included in the core; we define any system-specific connector together during implementation planning. A ready link exists with OPERRA, Grupas's production ERP.

The AI features explain the chosen forecasting model and its alternatives, interpret data-quality findings, review manual overrides through FVA, draft a management summary from scenario comparisons and an S&OP meeting summary, and answer natural-language questions with computed summaries. They see the data in summarized form and never decide: only a user's traceable intervention changes the plan. These features are enabled as part of the license and set-up.

Monthly subscription, annual subscription, purchase (perpetual license) and a project license for Grupas projects. A quote is made of OPLAN CORE, the modules you choose, any ERP / MES-specific connector and implementation services, sized to your sites and users — contact us through the demo / quote form.

OPLAN runs in the browser; Grupas prepares a separate environment and database for each customer. Implementation covers master data set-up and ERP mapping, a rule / constraint / preference workshop for your company, history cleansing and model calibration, role-based user training and parallel-run (pilot) support in the first cycles.

The OPLAN interface is in Turkish. This website is in four languages; let's discuss your need for another language in the demo call.

Fill in the demo / quote form; we will get back to you and schedule a live walkthrough on a sample plant that combines several flow types.