The terms that govern using the service engine.

These terms cover use of the Bgabs service engine and the public website that markets it. They apply to every operator account, whether the operator is an appliance brand, an in-house service network, or a multi-brand service company. They also apply to the technicians and dispatchers who log in under an operator account.

Bgabs provides a live service engine that tracks warranty and AMC contracts per unit, predicts service needs based on usage patterns and model failure history, proposes proactive visits inside the customer window, and dispatches the right technician for the route.

The engine is provided as a working, decision-making system - not just a repository. Availability targets, response windows, and the specific commitments for a given account are set out in the account\'s order form.

Operators are responsible for the accuracy of the contract terms they load into the engine, the accuracy of technician roster information, and the honouring of visits that the engine schedules and dispatches. Human overrides on alerts, schedules, and assignments are always available; the responsibility for those overrides rests with the operator who makes them.

Where an operator amends contract terms outside the engine, those amendments become binding only once they are written back into the contract record. Bgabs cannot honour terms it has never been told about.

Predictive alerts are computed from unit-level usage patterns and model failure history. Each alert carries a confidence score and a reason string. Alerts are decision support - not a guarantee that a failure will or will not occur. Operators are expected to treat alerts as inputs to a scheduling decision, and to keep a human dispatcher in the loop for edge cases.

Bgabs must not be used to run service operations that mislead customers about coverage, misrepresent service outcomes, or bypass documented safety obligations for a product. Operators must not attempt to scrape, mirror, or resell the underlying engine, and must not use the technician app to track technicians outside working hours or beyond the scope of active dispatch.

Customer data, contract data, and service event data belong to the operator that loaded them. The predictive models, dispatch algorithms, routing logic, and product interfaces belong to Bgabs. Model improvements derived from aggregated, anonymised usage across accounts do not create ownership in the operator\'s underlying data.

The default term is annual, renewing unless cancelled before the end of the current term. Exit exports of contracts, service history, and predictive labels are provided as standard, in a format the operator can move into another system. There is no exit fee for taking your own data with you.

Bgabs may suspend an account for material breach of these terms, for non-payment beyond a documented grace period, or where continued operation would put customer data or technician safety at risk. Wherever possible, suspension is preceded by written notice and a chance to remedy.

Bgabs is provided as a working service engine, with commercially reasonable effort applied to accuracy, availability, and support. Except where required by applicable law, Bgabs does not warrant that predictive alerts will be error-free, or that a scheduled visit cannot be refused by a customer. Standard limitations of liability apply as set out in the account\'s order form.

These terms may change as the product grows. Material changes are communicated to operator accounts in writing, with a reasonable window to review before they take effect. Continued use of the engine after a material change constitutes acceptance of the updated terms.