Specific, documented technical insights from IBM Maximo and MAS engagements. No opinion pieces. No platform overviews. Problems, causes, and solutions.
Oracle's DATE type stores time at second precision. SQL Server's datetime2 behaves differently for implicit casts. Without explicit handling, migrated DATE values lose their time component — breaking any query that relies on time-sensitive filtering. This post documents the pattern and the remediation approach used across multiple migrations.
Ad-hoc automation scripts accumulate inconsistencies that make debugging incidents painful. This post outlines the standard template used across 30+ scripts: configuration in MAXVARS, structured exception handling, audit logging, and version-controlled deployment — and why each decision was made.
Entra ID sends group members as a flat value array. MAS expects $ref URIs per member. The mismatch causes silent group sync failures — users are provisioned but group memberships are dropped. This post documents the exact payload difference and the Entra ID attribute expression that resolves it.
Not all ARO configuration choices are equal when you are running MAS. Worker node sizing, storage class selection, egress routing, and DNS resolution each have MAS-specific requirements that generic ARO documentation does not cover. This post summarises the decisions that affect production reliability.
MAS uses a managed Key Store for encrypted database fields. Upgrading from Maximo 7.6 without migrating encryption keys first results in decryption failures on encrypted columns — often discovered only after the database migration is complete. This post documents the migration sequence that avoids the failure.
Of het nu gaat om een platformupgrade, een defecte integratie of automatiseringsexpertise — laten we bespreken wat Magiq Minds kan leveren.