Prepare Maximo data with confidence

Get Maximo data right before Maximo sees it. Bring a spreadsheet, fix it in a grid that knows Maximo, check the request, rehearse the load, retry only what failed.

From an open browser to a rehearsed load in six steps. No sign-in needed for the free web pilot.

1. Open the Workbench at /workbench/. A guest workspace is created for you.
2. Go to What are you loading? and pick a journey: New Maximo, Existing Maximo or Regular loads. Or drop in your own file.
3. Confirm the Maximo version in Version Setup. Choose Direct load, or Migration if you are moving between versions.
4. Fix the sheet in the Grid Editor until the status bar says 0 errors.
5. Open Preview to read the request. Nothing has been sent.
6. Use Run Console to send the rehearsal. Read the results by row. Retry only failures from Run History.

Nine kinds of people get value. Each has a full end to end journey on the journeys page.

Home shows your projects and recent runs. The left rail has four places: Home, Project, Environments, History. Settings and Help sit below.

An environment is a Maximo target: a name, a version and a mode. Demo environments answer from the simulator.

Pick a journey, or bring your own file. The Workbench opens the sheet already mapped.

Inventory usage: drop the flat MXINVUSE sheet Maximo exports (INVUSENUM, FROMSTORELOC, USETYPE, then line columns ITEMNUM, QUANTITY, REFWO). It opens as the structure the file is named after (MXINVUSE), or MXAPIINVUSE when the name does not say, with the line columns mapped to INVUSELINE, one row per line.

New numbers: put NEW (or NEW-1, NEW-2 to tell several apart) or leave INVUSENUM blank. Rows with the same placeholder become one usage, the placeholder is not sent, and your Maximo gives each usage its next INVUSENUM. A real number such as I_30002 is sent as typed. The same works for WONUM and ASSETNUM on parent and child sheets.

Issue the stock: put COMPLETE in STATUS. Maximo creates a usage at ENTERED and only issues it to the work order at COMPLETE, so Execute does both: it creates each usage (one request per usage, so Maximo returns the number it gave), then changes its status to COMPLETE. Rows left at ENTERED are created and stay there. Request and response lists every usage with its number and final status. Preview checks the whole sheet in one call and does not complete anything.

Accepted input: delimited text (comma, tab, semicolon, pipe, quoted values), pasted cells, JSON and XML. Practice data is one fictional water plant, site BEDFORD, so a run in order leaves a coherent site. The simulator accepts any site code, so your own sheets preview with your own sites.

Samples for assets, PMs and work orders carry a Golden check link. It opens that screen's golden script on assetize.com.au/ui/golden: drag the bookmark once, open the screen in your Maximo, click it, and see whether the title and controls match the MAS 9.2 screen harvest. Read-only. The free journeys kit runs every golden script at once (npm run golden).

Say which Maximo you are loading into. Checks use that version's rules, not a generic set.

Switch any time. The choice is stored with the project, saved load sets, runs and exports.

Browse the fields of the object you are loading: type, length, which are required, which identify the record, allowed values.

In Migration, a second tab compares source with target: removed, added and changed fields. Data loaders see this as Browse fields.

What IBM documents for the object and field you have selected, with the source named.

Reached from Help or the grid. Reference, observation and demo data are labelled separately. IBM statements are never mixed with Assetize interpretation.

The sheet is the hero. Type, paste from Excel, fix red cells. The status bar keeps the error count.

Pick the job and the Workbench sets itself up for it. Use the Layout menu in the top bar, or Alt+1 to Alt+5. The Workbench remembers your last layout.

A layout is a shortcut for three choices: the page it opens, your audience, and whether the sheet hides optional columns. You can still change each one yourself afterwards in Settings or on the grid.

The grid works like a spreadsheet. Press ? anywhere, or use More → Keyboard shortcuts, to see the list in the app. On Mac use ⌘ for Ctrl.

Sets the order of loads and what each depends on, so children never arrive before their parents.

Batches are listed in order with their row counts. A failed batch can be retried without resending rows that already succeeded.

Read the exact request before it is sent: URL, headers with secrets masked, body and a hash.

Target-rule findings sit beside the payload. Data loaders see this as Check before loading. Nothing is sent from this page.

Pick object structures, run the assessment, get a score and the list of what breaks between source and target.

Optionally includes your grid's mapping. Data loaders see this as Upgrade check. Findings carry the evidence behind them, not just a colour.

Send the rehearsal and watch it. Per-row outcomes, the request and the response, and the option to load in the background.

Data loaders see this as Load and watch. A run exercises the simulator's result paths: success, failure and retry.

Every run for your account: what was sent, what came back, by row. Retry failures only, or clone a run into a new one.

Runs, rows, audits and batches are stored per account. Viewers can read them but not change them.

Choose your audience, reset local state, find short explanations beside each page.

Reset clears the current project, grid and Dev Tools state in this browser. Server data is untouched.

A drawer for developers: the request and response, timings and the audit trail. Open it from the command bar.

The command bar (jump to any page or Dev Tools tab) is the quick way around the app.

Ten curated templates from observed lab object structures, with fictional records. No real Maximo, no network send.

Use them to learn the flow, to train a team or to show a customer, without touching real data.

Take your work with you: export the sheet, the request or an MxLoader file. Or work in Excel with the add-in.

The Excel edition is a separate Windows product: an add-in (.xll) with a Getting Started workbook, sharing the same JSON contracts. It has its own ribbon for validate, preview, load, retry and history, and keeps customer data on your PC. It is free and needs no licence key. The shortcuts below are the web grid's. In Excel you have Excel's own. See /workbench/excel, and /workbench/compare for the web, Excel and self-hosted editions side by side.

Free web pilot with a guest workspace. Sign in with a one-time email link to keep your work. Each account sees only its own data.

Run the Workbench inside your own network. One Node 22 process and one SQLite file. Your data and saved credentials stay on a disk you own.

Start with products/workbench-enterprise/README.md in the repository: Docker compose, plain Node, every setting and the admin commands.

One project for upgrade work. MXH finds a problem, you open it here with its versions and evidence already loaded, fix it in the right editor, and send the evidence back.

Open it from the rail, or from an MXH finding with Open in Workbench 2.0. The project lives in this browser. The Evidence Graph is asked for facts and is never copied.

The finding arrives with everything MXH knew. The evidence goes back with what actually ran. The finding stays open until its own closure test passes.

1. In an MXH assessment, select a finding and press Open in Workbench 2.0. The source and target versions, object, attribute, owner, required action, closure test and evidence arrive with it.
2. The Studio shows the context and looks the object and attribute up at the target version, with the evidence it rests on.
3. Open Workflow or Reports on the object. The artifact is linked to the finding.
4. Save and validate. Each artifact records its proof levels.
5. On the finding, press Return evidence to MXH. MXH shows what was prepared and which proof levels passed.

Every result says what it is. The levels are never merged.

The Workflow Designer opens inside the project. It checks the fields your conditions name against the target version.

Create an approval, import designer JSON, or open the WOSTATUS lab example. Save a revision to run the designer's structure checks, your offline route scenarios and the version lookup. The process stays inactive.

Conditions that run on a related object are listed as not checked, because the related object is not resolved here.

Build a BIRT report from a Maximo object, or import the .rptdesign you already have and see what changes at the target version.

Choose an object and columns, add parameters, filters, sort and grouping, preview on synthetic rows, validate against the target, and export a .rptdesign or a Power BI handoff.

Power BI: the Export tab downloads a zip with one Power Query (M) script per data set, a TMDL semantic model with typed columns, parameters and simple calculated columns, a report plan (page, tables, slicers) and a README listing what needs a person (event scripts, scripted expressions, libraries). BIRT layout and charts are not converted. The files are generated text; they have not been opened in Power BI Desktop here.

Import reads data sources, data sets and SQL, parameters, bound fields, scripts, libraries and layout counts. Every table and column is looked up at the target. Scripts that use Java or BIRT APIs are flagged for review.

For pixel-level BIRT layout, native libraries and Java work. The pack carries the same project file.

Download it under Packages. Open the reports in the native BIRT Designer, edit, and bring the .rptdesign back with Import. There is no second Workbench in Eclipse.

These are named here so nobody has to guess.