Assetize

Workbench 2.0 · Engineering Studio

One project for your upgrade work, with every tool a click away.

Workbench 2.0 is the Engineering Studio: MXH finds a problem, you open it in the Studio with its versions and evidence already loaded, fix it in the right editor, and send the evidence back. Use any Assetize tool on its own, or connect the work here. Operations Studio, the command centres with maps and incident replay, is a separate catalogue.

Open the Studio · Start from an MXH finding · Read the Studio docs

What it connects

  • MXH findings: "Open in Workbench 2.0" carries the versions, object, attribute, owner, required action, closure test and evidence. Returning evidence never closes a finding. Sample assessment.
  • Workflow: the Workflow Designer opens inside the project; a saved revision runs structure checks, offline route scenarios and the version lookup.
  • Reports: build a BIRT report or import a .rptdesign and see what changes at the target version; export a .rptdesign or a Power BI handoff. BIRT Report Designer.
  • Scripts: a script pack travels with its tests to the Script Test Harness or a simulated Automation Scripts screen.
  • Data: add the sheet open in the Grid Editor to the project. Data Workbench.
  • Validate: look up any object and attribute at the target version and see which proof each artifact has. Relationship Explorer.

Use one tool, or connect the work

Choose a task, open the tool, review the proof, continue the project. Every tool launches directly from the directory; the Studio keeps the project context around them.

Three levels of proof, never merged

  • Static: the artifact is structurally compatible with retained evidence. Built for reports and workflows.
  • Simulated: the browser engine exercised our model of the artifact. Built for workflow offline routes. Not Maximo runtime execution.
  • Target execution: the artifact ran on that Maximo/MAS build. Not yet: NOT RUN until a connected, authorised environment has run it.

Ship

Download the project file or a developer pack for Eclipse BIRT. Every revision is kept: compare, restore, duplicate, export. Return remediation evidence to MXH with the proof levels it passed.

Not built in the Studio yet

UI and Integrations editors (the modules link to the UI Playground and the Integration Flow Explorer), a target execution runner, and projects stored on the server. A project lives in your browser; export the project file to keep or share it.