














































Azzier is a CMMS built in-house by Tero, the company behind Web Work Azzier, with more than 40 years in maintenance management. It is a web-based system delivered as hosted SaaS, with iOS and Android apps for operators and technicians, and serves manufacturing, oil and gas, government, facilities, education, healthcare and power generation. Its modules cover work requests, work orders, preventive maintenance triggered by calendar intervals or meter readings, an equipment hierarchy with warranty details, spare parts inventory, purchasing and maintenance projects. A predictive maintenance product reads assets and locations through Makini's Unified API, so each monitored machine maps to the equipment record technicians already use. When it detects a developing fault, it can create a work order where the connection permits writes, so the job reaches the supervisor's queue. Inventory optimization tools compare spare parts stock with open purchase orders and vendors, and reliability analytics products read completed work orders to calculate failure intervals per asset. An Azzier user signs in through Makini Link, embedded in the vendor's product or sent as a magic link, so credentials never pass through the vendor's application. Data then syncs on an interval set by the Makini plan, not in real time. What a connection exposes depends on the connecting account's permissions, so agree on its access with the customer's Azzier administrator. Azzier implementations often configure screens, fields and statuses for each customer, so map work order statuses and custom fields per customer before writing data back.
Have any questions? We’re here to help You
Yes, Azzier is Tero Consulting's latest CMMS and the successor to Web Work, and Tero also markets it as Web Work Azzier. Textron Systems moved from legacy Web Work to Azzier 7.2, and Washington State Military, a Web Work customer since 1997, reported that no data was lost in its upgrade. Customer documents may use either name.
In Azzier anyone in the organization can submit a work request, and supervisors review, prioritize and convert approved requests into work orders. The work order then carries priority, assigned technician, required parts, procedures, drawings and time logs through to closure sign-off. Preventive maintenance work orders are generated separately, from calendar intervals or meter readings.
Yes, Azzier CMMS has an Integration API module, a no-code, web-based interface that exposes the entire application database. Tero also lists connectors for SAP, Oracle and Microsoft Dynamics, a Power BI link, and sensor and telematics feeds. A software vendor using Makini does not call the Azzier API itself: it reads one Unified API, and Makini maintains the Azzier connector.
Makini's Azzier page lists work orders, assets, purchase orders, stock, customers, vendors, accounts, locations, sites and organizations, each mapped to a unified model where the connection exposes it. Work requests, meter readings and maintenance projects exist in Azzier but are not on that list, so confirm with Makini before you build features around them.
An Azzier administrator should create a dedicated account for the integration, with permissions limited to the sites and modules the product needs, rather than reuse a technician's login. Azzier supports single sign-on through Azure Active Directory and LDAP, so confirm how that account will sign in through Makini Link. Record the custom fields and work order statuses configured for that customer.
A predictive maintenance product should write to Azzier only after reads work and the customer agrees. Azzier sites may sync asset and procurement data with SAP, Oracle or Microsoft Dynamics, and some supervisors want every alert to pass the work request review instead of arriving as a work order. Enable writes only where the connection permits them, agree which system owns each record, and test on one site.
