














































NetFacilities is a cloud CMMS now offered by MRI Software, which counts more than 14,000 facilities on it in sectors such as education, property management, government, healthcare and hospitality. It covers work orders with customizable approval workflows, a login portal where users submit requests for review, preventive maintenance with automatic work order generation, assets tagged and linked to locations, inventory used on work orders, vendor management with insurance certificates and licensing, and key and lock management. Technicians use the MobileFacilities app with barcode scanning. A predictive maintenance product reads assets and locations through Makini's Unified API, so each monitored unit maps to the asset record facility teams already use. When it detects a developing fault, it can create a work order where the connection permits writes, so the job joins requests from the portal. Inventory optimization tools compare parts stock across sites with open purchase orders and vendors, where the connection exposes them, and energy or HVAC analytics products read completed work orders to see which equipment keeps failing. A NetFacilities 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 access, so agree on it with the customer's administrator. NetFacilities is built for multi-site portfolios, so check that the connecting user covers every site the product needs.
Have any questions? We’re here to help You
Yes, NetFacilities is the CMMS that MRI Software now markets as its own: MRI's product page at mrisoftware.com/products/netfacilities calls it MRI's CMMS, and users still log in at system.netfacilities.com. MRI counts more than 14,000 facilities on it and 6.8 million work orders processed. Customers may use either name, so search for both when they describe their system.
In NetFacilities a submitted request is reviewed, approved and then assigned to an individual, a group or a vendor, and status change notifications keep the requester informed. Each customer can customize approval workflows and priorities. A work order your product creates may therefore wait for approval, so read its status on later syncs rather than assuming it was dispatched.
NetFacilities assets carry a unique identifier, make, model, manufacturer serial number and an image, and are organized into groups of equipment types. Technicians scan asset barcodes in the MobileFacilities app for Android and iOS. Use that identifier together with the location as the join key when you map sensors to assets, since names often repeat across buildings.
NetFacilities has no API or integration documentation on MRI Software's product page, and Makini notes that some editions expose only limited or legacy APIs. Your product calls Makini's REST API, and Makini maintains the NetFacilities connector. Because MRI describes NetFacilities as a cloud CMMS, the firewall allowlisting or VPN used for on-premise systems is usually not needed.
Makini's NetFacilities page lists work orders, assets, purchase orders, stock, customers, vendors, accounts, locations, sites and organizations among its models. Time and cost tracking on work orders, key and lock records, and vendor certificates of insurance are specific to NetFacilities and may fall outside the unified models. Check which of these fields a given connection exposes before building cost or compliance reports.
NetFacilities writes are better added after a read-only phase, because its queues mix portal requests and preventive work, and unexpected new work orders would disrupt dispatchers. Ask the administrator for a dedicated user with access to every site your product needs. Then enable writes for a few agreed assets, keeping in mind Makini's note that permissions and workflow states can block changes.
