Learning Lab · Maximo SIM
Practise on the Maximo SIM.
DEV is dev.assetize.com.au and UAT is uat.assetize.com.au/maximo. Log in on the screen and use the applications: Work Order Tracking, Assets, Inventory and the rest.
Real practice on the Maximo SIM
- Knock on a real Maximo API without a key (DEV). The terminal sim showed a 401. Now see a Maximo-shaped server say the same thing, with a real BMXAA reason code.
- Ask the SIM who you are, with your API key (DEV). An API key proves who you are without a password. whoami answers with your own user record.
- Log in and read the work backlog (DEV). Every Maximo day starts on the list of work. Learn to find it on the screens before you ever query it in code.
- Find an operating asset and where it lives (DEV). Assets and locations are separate records. Seeing them side by side on the screen makes the difference stick.
- Raise a corrective work order and approve it (DEV). This is the most common thing anyone does in Maximo. Do it once by hand and the API version later will make sense.
- Read a storeroom balance (DEV). Planners check stock before they promise a job. Current balance and available balance are not the same number.
- Look inside the WORKORDER object (DEV). Database Configuration is where an object's attributes, their types and their domains live. Reading it is a daily developer habit.
- Open the object structure behind the API (DEV). The REST API reads object structures, not tables. See which objects MXAPIWODETAIL bundles.
- Query the backlog over the API (DEV). The same list you filtered on the screen, now from code: only the fields you need, filtered inside Maximo.
- Create a work order over the API (DEV). Integrations create records this way. The properties header asks Maximo to send back the new number.
- Make Maximo refuse you, then read the error (DEV). Errors are messages. Learn to read the reason code and the message word for word.
- Read the version from the box (DEV). Every answer belongs to a version. Prove which one you are talking to before you trust anything.
- Try the old login on a MAS-style API (DEV). The login change breaks more upgraded integrations than anything else. See it with your own eyes.
- Change DEV, prove UAT and PROD are untouched (DEV). Environments are separate copies. A change made in DEV exists nowhere else until it is moved on purpose.
- Read a screen in Application Designer (DEV). Most screen changes are configuration, not code. Learn where a field on a screen comes from.
- Write your first automation script (DEV). A completion gate is the classic first script: stop a work order being completed without a failure code.
- Find an integration message (DEV). When an integration breaks, Message Tracking is where you start. Know where it is before you need it.
- Promote your script from DEV to UAT, then check PROD (UAT). Promotion is the heart of delivery: the same change, moved the same way, checked at each step.
- Load five locations into the SIM with Workbench 3 (DEV). A real load end to end: connect, map, check, preview, load, read each row, reconcile.
- A small release, start to finish (UAT). Everything at once: a change built in DEV, tested, moved to UAT, data loaded, and proof written down.