A smarter and more flexible Mainpac platform
Recent releases of the Mainpac platform introduce several important enhancements designed to give organisations greater flexibility in managing asset data, improve support for field teams, and simplify day-to-day system use.
Versions 3.20.10 to 3.20.12 bring together new capabilities across data configuration, mobility, AI-powered assistance, and security infrastructure.
These updates are designed to help organisations capture more relevant operational data, streamline workflows, and reduce the time users spend searching for support or navigating complex system processes.
Key highlights in this release
- AI-powered in-application assistance through MIA
- A rebuilt mobile platform experience called Mainpac Go
- Flexible data configuration through Dynamic Datasets
- Improved asset governance through Asset Classification Structures
- Enhanced security and infrastructure capabilities
Dynamic Datasets
Every organisation manages assets differently. Capturing the right operational data is essential to maintaining reliable reporting and maintenance processes.
Dynamic Datasets allow administrators to configure custom fields directly within Mainpac without requiring development work. Fields can include numeric values, text, or structured lookups and can be validated to ensure consistent data entry.
These fields appear natively within Mainpac screens, meaning organisations can extend the system data model while maintaining a consistent user experience.
Key benefit: Organisations can capture the data that matters most to their operations without waiting for development cycles.
Asset Classification Structures
Managing large asset portfolios requires consistent classification and governance.
The new Asset Classification Structure enables organisations to create configurable hierarchies for both operational and financial assets. Attributes such as criticality ratings, fault codes, and risk scores can be defined at classification levels and automatically inherited by related assets.
This significantly reduces manual configuration and improves consistency across asset portfolios.
Key benefit: Standardised asset governance across large and distributed asset bases.
MIA – Mainpac Intelligent Assistant
MIA introduces AI-powered assistance directly into the Mainpac interface.
Users can ask questions within the platform and receive contextual responses based on the documentation and the task they are performing. This reduces the need to leave the system to search for help.
MIA can also generate structured support emails that automatically include important system details such as the screen name, entity type, and record identifier.
Key benefit: Faster support resolution and improved user productivity.
Mainpac Go – the new mobility experience
The Mainpac mobility platform has been rebuilt to provide a faster and more reliable mobile experience for field teams.
Administrators now have greater control over how mobile screens are configured. Fields can be shown or hidden depending on the operational context, and layouts can be tailored to different user roles.
Organisations can also apply branding to the mobile application, creating a more consistent experience for field teams.
Key benefit: Faster workflows and improved usability for field operations.
Security and infrastructure improvements
The latest releases also introduce several security and infrastructure enhancements.
External Work Requests can now support Azure Active Directory authentication and reCAPTCHA validation, giving organisations more control over who can submit requests and helping prevent automated submissions.
MP Connect can now be deployed using IIS, aligning with standard enterprise infrastructure practices and simplifying deployment.
What this means for organisations
These updates are designed to help organisations manage assets more effectively while improving user experience across the platform.
- Administrators gain more control over configuration.
- Field teams benefit from improved mobility workflows.
- Users gain faster access to support and guidance directly within the system.
Together, these enhancements make Mainpac more adaptable to the operational realities of asset-intensive organisations.
To illustrate how these updates translate into real operational benefits, consider a hypothetical customer, Meridian Water, a mid-sized regional utility responsible for managing treatment plants, pump stations, and distribution infrastructure across several locations.
Before the updates
Sarah had been waiting six months for a system enhancement to allow her team to capture additional maintenance attributes specific to their regulatory reporting requirements. In the meantime, teams were maintaining a parallel spreadsheet. James was regularly frustrated by the mobile app’s slow load times on-site and the fact that he had to scroll past irrelevant fields to find the ones he actually needed during checks.
When a field technician needed help submitting a work request, they’d call the office. When a new team member needed to understand how to raise a fault in Mainpac, they’d have to wait for someone to walk them through it.
After the updates
Sarah spends a morning configuring a new Dynamic Dataset for pressure vessel maintenance. She creates a set of custom fields — maintenance date, pressure reading, seal condition — adds a lookup field using a Hierarchical Lookup tied to their asset location hierarchy, and marks the pressure reading as mandatory with a numeric validation range. She arranges the fields into a dedicated ‘Regulatory Maintenence ‘ panel. The whole process takes under two hours with no external support needed.
She also sets up an Asset Classification Structure for Meridian’s pump station assets. She defines criticality ratings and risk scores at the asset class level — now, when a new pump station asset is added, it inherits those attributes automatically. No one needs to configure it asset by asset.
James opens the updated Mainpac Mobility app on his tablet. The app loads quickly. On the pressure vessel maintenance screen, he sees only the fields relevant to his current task, in the order Sarah has configured for field maintenance. The mandatory pressure reading field is clearly marked. He completes the record in half the time it used to take.
Later that day, a new field technician, Maria, needs help understanding how to link a fault code to a work order. Instead of calling James, she opens MIA, types her question, and gets a clear, step-by-step answer within seconds — all without leaving the screen she’s working on.
At the end of the week, Maria encounters a system behaviour she can’t explain and needs to raise a support request. She uses MIA’s support email feature. The email is pre-populated with her current screen, the entity she’s working with, and the relevant record ID. She adds a short description of the issue and sends it. The Mainpac support team receives a complete, structured request and resolves it that same day.
The result: Meridian Water’s teams spend less time on configuration, less time navigating around irrelevant information, and less time waiting for support. The data they capture is more consistent, their reporting is more reliable, and new team members become productive faster.
Release Notes Summary
| Feature | Version | Area |
| Dynamic Datasets | 3.20.10 | Data Configuration |
| Hierarchical Lookups | 3.20.10 | Data Configuration |
| Asset Classification Structure | 3.20.10 | Asset Management |
| MP Connect – IIS Deployment | 3.20.11 | Infrastructure |
| Unified Work Order Step Structure | 3.20.11 | Work Management |
| External Work Request Enhancements | 3.20.11 | Security & Access |
| Condition Assessment Validation | 3.20.11 | Asset Management |
| MIA – Help Chatbot | 3.20.12 | AI & User Support |
| MIA – Support Email Generation | 3.20.12 | AI & User Support |
| Mainpac Mobility – .NET MAUI Upgrade | 3.20.12 | Mobile |
For assistance with any of these updates, contact your Mainpac customer success manager or visit the Mainpac support portal.
