Evidence atoms
Clickable claim/evidence index for the Max Connect V1 pack. Atoms are grouped by type and each card opens its atom detail.
Maximo community is event-led
The community notebook identifies MaximoWorld, MUWG, GOMaximo, CanMUG, IBM Community, MORE Maximo/community forums, Reddit, and partner content as active signal channels.
MaximoWorld is the flagship independent ecosystem event
The community notebook identifies MaximoWorld as the flagship independent Maximo ecosystem event, with 1,300+ attendees and a 2026 theme focused on unlocking more value through APM, RCM, and AI.
MUWG and CanMUG are specific user-group channels
The Maximo Utility Working Group and Canadian Maximo User Group are named community channels. MUWG serves over 200 global utilities, and CanMUG is seeking user/sponsor presentations around MAS, Maximo Mobile, supply chain, and cloud hosting.
Specialist partners shape the MAS migration route
The MAS migration ecosystem is partner-heavy. Named players include Cohesive, TRM, Interloc, Projetech, Pragma Edge, P2Insight, Naviam, and JFC & Associates.
Public Maximo knowledge base needed
Ant wants the first Discovery sweep to gather publicly available information about Maximo/MAS, the product itself, differences between legacy Maximo and MAS, competitor/support analysis, TAM or market-sizing signals, and broad public-domain context.
Maximo 7.6 end-of-support creates migration urgency
The community opportunity synthesis says Maximo 7.6.1.x reached end of support on Sept 30, 2025, with extended support temporary and expensive. This creates a time-based trigger for migration decisions.
Fifty to hundred thousand budget hypothesis
Ant's starting budget hypothesis is that each target company may have roughly £50k–£100k available for consultative guidance/support around Maximo/MAS.
AppPoints are a buying risk
The licensing corpus describes MAS AppPoints as a shared-pool model with authorized and concurrent usage, role tiers, reserved points, add-on/install points, SaaS overage exposure, and customer-managed activation/lockout constraints.
AppPoints are a shared enterprise pool
MAS licensing centers on AppPoints: a shared pool consumed across applications, role tiers, access types, and some application installations rather than a simple one-license-per-product model.
Concurrent and authorized AppPoints behave differently
Authorized users reserve AppPoints permanently, while concurrent users check out AppPoints only while active and return them after their session. This distinction matters for shift-heavy maintenance teams.
MAS role tiers create licensing design choices
Self-Service, Limited, Base, Premium, and Administrator access tiers each have different AppPoint implications. Correctly mapping legacy users into those tiers is a design exercise, not a clerical conversion.
MAS creates both overage and lockout risk
In MAS SaaS, depleted AppPoint pools may continue operating and create retrospective overage bills. In customer-managed environments or authorized-user assignment, insufficient unreserved AppPoints can block user activation.
Some MAS add-ons consume flat installation AppPoints
Some capabilities consume AppPoints at installation or by usage, not just by named user role. Examples in the NotebookLM synthesis include Optimizer, SAP/Oracle connectors, Civil Infrastructure, Visual Inspection, and AI service token usage.
Implementation cost is a barrier for smaller customers
The NotebookLM synthesis cites high upfront implementation costs, with a reported USD 150k–300k range for mid-sized businesses. That makes migration economics a likely barrier for smaller Maximo-dependent organizations.
Readiness audit and education wedge
Ant sees possible Max Connect offers including readiness audit, education/thought leadership, a useful information repository or website, self-serve survey, consultative audit, workshops, upgrade plan, execution support, ongoing partner relationship, and commu
Readiness assessment is a wedge
The strongest near-term Max Connect opportunity from the corpus is a readiness-assessment wedge: inventory existing Maximo version, modules, integrations, customizations, database health, auth model, AppPoints exposure, OpenShift/SaaS preference, and partner n
Education plus partner matching
The corpus supports several Max Connect value paths: plain-English MAS education, AppPoints explainers, migration readiness, partner/vendor matching, event/community content, and implementation navigation for smaller customers that may be underserved by enterp
Education is a plausible Max Connect wedge
Max Connect could create value by translating MAS architecture, OpenShift, AppPoints, API, and migration concepts into plain-language education for smaller legacy Maximo users.
Migration planning is a plausible Max Connect wedge
Max Connect could package migration planning around sequencing, prerequisites, customization rationalization, data prep, test cutovers, downtime measurement, integration rewrites, and SaaS versus self-managed choices.
AppPoints analysis is a plausible Max Connect wedge
Max Connect could help smaller users model AppPoints exposure: concurrent versus authorized users, role tiers, administrator reservations, non-production environments, add-on install points, service-account design, overage risk, and lockout risk.
Partner matching is a plausible Max Connect wedge
Because the ecosystem relies heavily on specialist integrators and service providers, Max Connect could match smaller customers to appropriate partners by need: hosting, zero-downtime migration, API modernization, mobile/offline, reliability training, or suppl
Community media is a plausible Max Connect wedge
Existing events and communities skew broad/enterprise. Max Connect could build a niche media/community surface for smaller Maximo users focused on survival-level migration questions, AppPoints, practical cutover, and partner selection.
Ongoing MAS support is a plausible Max Connect wedge
MAS administration creates ongoing needs around OpenShift, manual scaling, monitoring, backups, channel subscriptions, API permissions, and disaster recovery. Max Connect could explore recurring support or fractional admin offers.
Single Node OpenShift may make smaller MAS deployments viable
The community notebook suggests Single Node OpenShift on AWS as a potential lower-footprint path for organizations with under 70 concurrent users or satellite deployments.
Target-profile DD can shape wedge choice
The target-client profile source creates a useful due-diligence workstream for choosing Max Connect's first wedge. The four profile groups have different triggers:
Migration pain is multi-layered
NotebookLM answers cluster migration pain into several layers: database integrity checks, data quality, customization archives, Java recompilation, user/auth migration, testing/cutover sequencing, OpenShift operation, and integration rewrites.
Dirty legacy data is a central migration pain
Research and community notes converge on data readiness: run Integrity Checker, clean database errors, and treat migration as rationalization rather than copy-paste. Community language describes dirty legacy data that no one wants to own.
Maximo is perceived as over-engineered for smaller operations
Community synthesis says Maximo is described as over-engineered for small operations, with complaints such as many clicks to create a simple work order and fallback to spreadsheets.
End users report a training and usability gap
The community notebook reports end users asking for an easier way to use Maximo and complaining about insufficient training for laypersons just trying to open or close work orders.
Attachment and doclink migration is a specific SaaS pain
Community opportunity synthesis identifies SaaS attachment and file migrations as a practical pain, including movement from on-prem file servers to cloud storage, record ID changes during object structure migrations, and Azure Files/PVC configuration for docli
Legacy custom Java can fail in MAS deployment pods
Community synthesis says admins porting legacy 7.6 custom Java classes to MAS9 can encounter configdb and maxinst pod deployment failures. This ties to the broader customization archive migration burden.
Underserved smaller Maximo businesses
Ant's starting audience hypothesis is smaller Maximo-dependent businesses that do not get meaningful support from IBM.
Multiple buyers and blockers exist
The corpus indicates that MAS migration affects economic buyers, technical decision-makers, administrators, reliability/maintenance leaders, technicians, integration owners, and external partners.
Economic buyers care about ROI asset life and transformation
Likely economic buyers include C-level executives and enterprise leaders focused on ROI, asset lifecycle extension, loss minimization, and digital transformation in asset-intensive sectors.
Technical decision makers evaluate integration privacy and scalability
Likely technical decision-makers include CIOs, CTOs, IT teams, and operations/maintenance managers evaluating scalability, data privacy, edge-to-cloud patterns, and legacy integration complexity.
Daily users include technicians inventory clerks supervisors and reliability engineers
Daily Maximo/MAS users include field technicians executing work orders, inventory clerks, supervisors, maintenance managers, and reliability engineers using mobile execution, inventory, IoT sensor data, and predictive analytics.
Blockers are cost skills complexity and change resistance
Likely blockers include high upfront implementation cost, lack of skilled IT/asset-management professionals, Kubernetes/OpenShift complexity, and organizational resistance to moving from reactive to predictive maintenance.
Target client profiles split by asset sector
NotebookLM analysis of the `Target Client Profiles: EAM and IBM Maximo Consultancy Opportunities` source suggests four initial target-client profile groups for Max Connect:
MAS is a platform shift
MAS is not a normal Maximo 7.6 version upgrade. The product corpus describes legacy IBM Maximo Asset Management as becoming Maximo Manage inside the broader IBM Maximo Application Suite, with suite-level administration, centralized identity/user management, Ap
OpenShift drives migration complexity
The expanded corpus repeatedly points to Red Hat OpenShift, Kubernetes operators, embedded WebSphere Liberty, MongoDB/core services, persistent storage, relational database connections, API keys, and resource sizing as central MAS operating requirements.
Legacy integrations need rewrites
Migration evidence identifies integration discontinuities: RMI is no longer supported, legacy authentication patterns such as maxauth are displaced, REST/API-key usage becomes central, and older messaging patterns may need Kafka or supported JMS replacement.
MAS requires Red Hat OpenShift
MAS is built as a containerized suite on Red Hat OpenShift. For legacy Maximo 7.6 customers, this changes the operating base from traditional application-server administration to Kubernetes/OpenShift administration across on-prem, hybrid, managed, or SaaS depl
WebSphere deployment is replaced by Liberty in pods
Traditional IBM WebSphere Application Server is not installed or migrated as before. Maximo Manage uses WebSphere Liberty embedded in container images and runs workloads as OpenShift pods/server bundles such as UI, Cron, MEA, and Report.
MAS adds MongoDB Kafka and object storage dependencies
A MAS environment is not just Maximo plus a relational database. The NotebookLM architecture synthesis identifies MongoDB for MAS core metadata/user registry/OIDC data, Kafka or another JMS provider for messaging, persistent object/file storage, and in some ap
RMI integrations must be rewritten to REST APIs
Remote Method Invocation (RMI) is no longer supported in MAS. External applications or custom extensions that depend on RMI need to be rewritten around REST APIs before or during the migration.
Legacy maxauth API authentication is replaced by API keys
Machine-to-machine and REST API interactions in MAS do not use the legacy maxauth method. Administrators must generate API keys and bind them to appropriate user-management or system-configuration privileges.
Object structure security can break integrations by default
When object structure security is enabled, external applications cannot query or update data via REST/JSON/XML/OSLC unless the backing object structures are explicitly assigned to security groups with required permissions.
Customization archives replace old customization handling
Maximo Archiving is discontinued. Existing Java classes, XML files, database scripts, and third-party changes need to be extracted into customization archives that the Maximo Manage operator injects into images during deployment.
Some MAS core services require manual scaling
The NotebookLM synthesis says core MAS microservices such as MongoDB, coreidp, and coreapi do not autoscale. Administrators must monitor load and manually adjust CPU and memory limits as usage grows.
Non-production mode avoids AppPoints consumption
MAS allows administrators to mark environments as Non-production. Development, test, and staging environments in that mode do not consume purchased AppPoints, making test migrations and rehearsals commercially safer.
SAML user mismatches can cause data migration conflicts
If a legacy Maximo environment uses SAML and user IDs do not match usernames, the migration can hit a data conflict. The NotebookLM synthesis says a specific OpenShift ConfigMap may be needed to migrate data with the correct SAML ID field.
Cutover rehearsal is required to measure downtime
The migration guidance emphasizes backing up production, preparing a duplicate test database, and running full test upgrades to measure downtime before production cutover. Community language also points to multiple cutover rehearsals rather than a single lift-