No. This is a build-to-order module that ECOSIRE designs, builds, installs and supports specifically for your assets and instruments. There is nothing to download at purchase. After you buy, we confirm scope, then develop and deploy the module to your Odoo instance. This lets us match the data model, trigger rules, tolerance bands and certificate layout to your equipment and quality procedures rather than shipping a generic template.

Typical delivery is one working week from a signed scope. A straightforward meter-and-calibration setup on a clean Odoo 17/18/19 instance lands toward the shorter end; heavier requirements — bulk data migration, IoT/SCADA reading feeds, accredited-lab certificate formats or multi-company rollout — sit at the longer end. We share a milestone plan up front (scope, build, UAT on staging, training, production go-live) so you always know where the project stands.

Every engagement includes a post-go-live support window covering bug fixes and adjustments, with defined response terms. Because the module is written to standard Odoo conventions (proper __manifest__.py, models, security and views), it upgrades cleanly with your platform. When you move between Odoo 17, 18 and 19, we provide a compatibility check and any needed migration of the module as part of an agreed maintenance arrangement — you own the source code either way, so you are never locked to us.

Both. The module targets Odoo 17, 18 and 19 on Community or Enterprise. Core functionality — meters, usage-based triggers, calibration scheduling, certificates and quarantine — is built on standard framework features (models/ORM, automated actions, ir.model.access.csv, record rules and QWeb) that exist in Community. If your workflow relies on Enterprise-only apps such as Quality or advanced Field Service, we integrate with them where present; we confirm the exact edition dependencies during scoping.

Yes. Every new model — including the meter and reading records — is exposed over Odoo's XML-RPC and JSON-RPC API, so your IoT gateway, SCADA historian, telematics provider or PLC middleware can create readings programmatically. When a pushed reading crosses a configured threshold, the automated action raises the maintenance request without any manual step. We can also build a scheduled import if your source is a file or database export rather than a live API.

Each instrument carries a calibration due date and a tolerance verdict. An automated action combined with a record rule flips any overdue or failed instrument into a 'quarantined' state, and that state removes it from the selectable instruments on quality checks and sign-offs. So a technician physically cannot pick an out-of-cal gauge to pass an inspection. You also get advance alerts before the due date and a traceability link from a failed instrument back to the checks it signed off, which is what auditors ask for under ISO 9001, IATF 16949 and ISO 17025.

You receive the full module source, the configuration mapped to your assets and instruments, a branded calibration-certificate template, the security/access matrix, an initial data load, deployment to staging and production, documentation and a training session — plus the support window. You own the delivered source code and can host, modify or extend it yourself. We document the models and extension points so your own developers, or another partner, can continue the work if you ever choose to.