Who it helps, step by step

Consultant or Maximo owner deciding whether this is worth a pilot

1. Open /workbench/

   Open the Workbench. A guest workspace appears. No account, no approval.

   The Dashboard with a start button.

2. What are you loading?

   Pick Existing Maximo → Fix a messy asset sheet.

   The Grid Editor opens with a fictional export already mapped.

3. Grid Editor

   Read the red cells. Select one.

   Six planted mistakes, each with the reason and what is allowed.

4. Grid Editor

   Fix them, or use the suggested fix. Watch the status bar.

   Errors fall to 0.

5. Preview

   Open Preview.

   The exact request, masked headers, the hash. Nothing sent.

6. Run Console

   Send the rehearsal.

   Row-by-row results from the simulator, clearly labelled.

7. Run History

   Open the run.

   The record you would show a colleague. Retry and clone are one click away.

Data steward or analyst who owns the spreadsheet

1. Settings

   Choose the Data loader audience once.

   Plain words everywhere: Your sheet, Check before loading, Load and watch.

2. What are you loading?

   Drop in the file.

   The Workbench suggests Asset as the likely object and opens the sheet.

3. Version Setup

   Confirm the Maximo version. Choose Direct load.

   The top bar shows the target version.

4. Grid Editor

   Read the Match columns list. Map the ones it could not place.

   Every column mapped or knowingly left out.

5. Grid Editor

   Work down the red cells. Fix statuses against the allowed list, remove duplicate asset numbers, fill the missing locations.

   Each cell gives the reason in the formula bar. The status bar counts down.

6. Load Plan

   Put Locations before Assets. Add Assets before PMs if you are loading both.

   A parent that does not exist yet is flagged before it can fail a load.

7. Preview

   Check one row of the request.

   The values Maximo will see, not the values you typed.

8. Run Console

   Run the rehearsal. Watch the results.

   Passed rows and failed rows, by row number.

9. Run History

   Retry only the failures after correcting them.

   Rows that already passed are not sent again.

10. Grid Editor → Export

    Export the clean sheet or the MxLoader file for the real load.

    A file you can hand to whoever owns the live system.

Owns sites, organisations, security and what reaches production

1. Settings

   Choose the Maximo admin audience.

   Site, organisation, security and run settings appear.

2. Environments

   Create or pick the environment. Check the version and mode.

   A Demo environment, with Live shown as unavailable.

3. Schema Explorer

   Open the object. Look at required fields, keys and allowed values.

   Which attributes identify a record and which are domain-checked.

4. Grid Editor

   Check Site and Organisation columns on every row.

   Wrong or missing values flagged against the target rules.

5. Preview

   Read the target-rule findings beside the request.

   Anything that would fail on site, organisation or status before it is sent.

6. Run Console

   Run the rehearsal. Open the run.

   Who ran it, what was sent, what came back.

7. Run History

   Share the run with a Viewer.

   A reviewer can read it and cannot change it.

Integrator or automation-script author

1. Settings

   Choose the Maximo developer audience.

   Object structure names such as MXAPIWO, attribute names and API requests.

2. What are you loading?

   Start from the Work order backlog sample.

   MXAPIWO selected and mapped.

3. Schema Explorer

   Browse attributes, types and relationships.

   The structure for the version you chose, with the evidence behind it.

4. IBM 9.2 reference

   Check what IBM documents for a field you doubt.

   IBM's statement and source, kept separate from Assetize's interpretation.

5. Preview

   Read the URL, body and hash.

   A request you can paste into your own tooling.

6. Dev Tools

   Open the drawer from the command bar.

   Request, response, timings and audit trail for each call.

7. Run Console

   Run it. Compare the simulator's response to what your code expects.

   Deterministic result paths for success and failure.

Runs the move from 7.6.1.3 to MAS Manage 9.x

1. Version Setup

   Choose Migration. Source 7.6.1.3, target 9.2.x.

   The top bar shows the pair. Migration tools appear.

2. Schema Explorer

   Open the 7.6.1.3 vs 9.2.x tab.

   Removed, added and changed fields per object.

3. Migration Readiness

   Choose the object structures in scope. Include the grid mapping. Run the assessment.

   A score, and a list of what breaks with the evidence for each item.

4. Grid Editor

   Load an extract. Fix what the target rules flag.

   Migration-profile warnings beside normal errors.

5. Load Plan

   Order the loads. Foundation data first.

   Dependencies resolved before the first batch.

6. Run Console

   Rehearse each batch.

   Per-row outcomes for the target schema.

7. Run History

   Keep the runs as the evidence pack for the cutover review.

   A dated record per batch.

Delivers loads for several customers

1. Environments

   Create one environment per customer and version.

   Each customer's work is separate.

2. What are you loading?

   Start from New Maximo and replace the sample with the customer's data.

   The load order is already right: locations, assets, PMs, inspection form.

3. Grid Editor

   Map, fix and save as a load set.

   A reusable named set.

4. Load Plan

   Keep the plan with the set.

   Next time it opens in the same order.

5. Run Console

   Rehearse and run each load.

   A run per load, with its rows.

6. Run History

   Clone the run for the next customer.

   A new run with the same shape and none of the old rows.

7. Exports

   Export the sheets and requests for the customer's own team.

   Files that stand without the Workbench.

Change approver, auditor or manager

1. Sign in

   Open the one-time email link. Your account has Viewer access.

   Everything for the account, read-only.

2. Run History

   Open the run you were sent.

   What was sent, to which environment, by whom.

3. Run Console

   Read the row outcomes.

   How many passed, which failed and why.

4. Preview

   Read the request that was built.

   The payload and hash, with secrets masked.

5. Migration Readiness

   Read the score if the load is part of an upgrade.

   Findings with their evidence.

Works in Excel all day and will not leave it

1. /workbench/excel

   Download the Excel package and extract it. The .NET 8 x64 runtime must already be installed.

   Assetize Data Workbench.xll and Getting Started.xlsx.

2. Excel

   Open the .xll. An ASSETIZE WORKBENCH tab appears in the ribbon.

   Groups for Environment, Data, Prepare, Execute and Tools.

3. Home sheet

   Choose Explore offline demo, or add your environment.

   Fictional Bedford data, or your environment and its version.

4. Data

   Click Select Object, then paste or import your rows. Use Map for columns that do not match.

   A column per field, with status columns beside your data.

5. Validation

   Click Validate. Edit the flagged rows, then validate again.

   Severity, row, field, value, message and the suggested action.

6. Load Plan

   Check the order of loads and their dependencies.

   Ordered steps with dependency status.

7. Request

   Click Preview Request.

   Method, URL, masked headers, payload and hash. Not sent.

8. Execute

   Click Load. Click Retry Failed after you correct rejected rows.

   Row results, a Failed sheet with only the rows that failed, and the run in History.

IT or Maximo platform lead who must keep data inside the network

1. Repository

   Read products/workbench-enterprise/README.md. Copy .env.example to .env.

   A short list of settings: secret, public address, allowed Maximo hosts.

2. Terminal

   Set SESSION_SECRET (openssl rand -hex 32), PUBLIC_URL and MAXIMO_ALLOWED_HOSTS. Run docker compose up -d --build, or node server.mjs on Node 22.

   A line saying it is listening, and the migrations applied.

3. Reverse proxy

   Put your TLS proxy in front of port 8080. Keep TRUST_PROXY=true.

   The Workbench at your own address, over https.

4. Terminal

   Run node admin.mjs invite --email [email protected] --account "Finance" for each person.

   A one-time sign-in link per person.

5. Sign in

   Each person opens their link.

   Their own workspace. Nobody else's environments, sheets or runs.

6. Environments

   Add an environment.

   Only hosts on your allow-list are accepted. Credentials are sealed and never shown again.

7. Terminal

   Schedule node admin.mjs backup --to .... Keep SESSION_SECRET with the backup.

   A consistent copy of the database while the server runs.

Maximo developer fixing what an upgrade assessment found

1. MXH finding

   Select the finding and press Open in Workbench 2.0.

   Workbench 2.0 at 7.6.1.3 → 9.2 with the finding, owner, required action and closure test.

2. Finding

   Read the version evidence for the object and attribute.

   Found, changed, new or removed at the target, with the reference.

3. Reports

   Import the report's .rptdesign.

   A Report upgrade check: fields checked, compatible, changed, missing, unresolved.

4. Reports

   Fix the SQL and validate again. Export the .rptdesign.

   Static validation passes. Target execution says NOT RUN.

5. Workflow

   Open or build the approval that uses the field. Save a revision.

   Structure checks, the fields it names, offline routes: Simulated pass. Target execution NOT RUN.

6. Finding

   Press Return evidence to MXH.

   MXH shows Remediation prepared and the proof levels. The finding is still open.