Maestro OS

Maestro OS · Business operating platform

Window construction calculations and revisions in Maestro OS

Maestro OS by MASTERPLAST connects window geometry, selected systems, hardware calculations and saved construction revisions. The useful outcome is a traceable construction record with explicit assumptions and diagnostics. This guide explains how to review that record, distinguish imported data and avoid confusing a current estimate with a previously saved order.

Define geometry and choices before calculating

A window calculation needs more than overall width and height. Establish the frame geometry, divisions, opening directions, leaf arrangement, selected system and relevant accessories. Maestro's calculation service passes frame points, selected options, reference data, separators, additional profiles, imposts and sash polygons to a configured calculation endpoint. The existence of that adapter does not establish that the endpoint is available in a particular installation. In the native constructor workflow, use the selected model and catalogue references consistently and resolve missing or ambiguous dimensions before saving. Imported supplier or WinCalc information should retain its provenance rather than silently becoming a new native construction. A faithful calculation preserves the intended geometry and opening behaviour; it does not replace an uncertain drawing with a convenient standard shape.

Read hardware results together with diagnostics

Hardware selection depends on a compatible combination of product type, system, dimensions, opening behaviour and accessory choices. The hardware calculator validates input, resolves a package version, checks compatibility and applies catalogue and range rules while building the material result. Its diagnostics and trace are therefore part of the review, not optional commentary beside a total. Blocking conditions should be resolved at their source before treating the calculation as usable. Production calculation is also controlled by a feature flag, and the general hardware engine explicitly distinguishes installation from approval for production use. Catalogue coverage must be checked for the selected configuration: code for a family of products is not a guarantee that every size, security option or opening combination is supported by the active package.

Save a revision that can be identified later

The construction revision service treats saved snapshots as the authoritative construction history, with order rows acting as projections of the current revision. A reviewer should be able to identify the saved project, its quantity and the revision being inspected. When editing, confirm the intended base revision and save through the revision workflow so that changes remain attributable. Reports and material views should refer to the same construction version rather than mixing an older drawing with a new calculation. Access is scoped to the order and user permissions, and some cost information is removed when the user lacks the relevant right. This separation helps different roles review the same construction without assuming that every person should see purchase costs or modify the authoritative record.

Distinguish historical values from a fresh estimate

A saved construction and an estimate using current prices answer different questions. The revision service supports stored report data as well as a working estimate built with current material pricing; its current pricing path warns that the saved order remains unchanged until a save. Decide which view is required before comparing totals or preparing a customer discussion. Check quantity, currency and pricing completeness rather than interpreting a missing amount as zero. For manufacturing review, reconcile geometry, materials and the chosen hardware result against the saved revision and resolve diagnostics before release. Before introducing the workflow, verify the active catalogue package, permissions, calculation endpoint and production feature settings in the target installation. This documentation describes source implemented revision and calculation controls; it does not certify structural performance, regulatory conformity or the live readiness of a particular product configuration.

Discuss your workflow

Explore related workflows