**Step 1 — Introduce the legacy customization challenge**

Explain that existing Maximo implementations may contain Java customizations created to satisfy specialized business requirements. Maintaining these customizations and migrating their logic into more maintainable implementations can require considerable developer effort.

**Step 2 — Open the Java conversion demo**

Introduce IBM Bob and the reusable **Maximo-java-conversion** building block. Select a representative legacy Java customization to demonstrate the conversion workflow.

**Step 3 — Review the original Java implementation**

Explain the purpose of the code, its key business rules, and its dependencies on Maximo APIs or application objects. Establish which behaviors must be preserved during conversion.

**Step 4 — Run the AI-assisted conversion**

Use the conversion building block to assist in generating a corresponding Maximo automation script. Explain how the solution helps translate the existing logic into the scripting model used by Maximo.

**Step 5 — Compare the source and generated code**

Review the original Java implementation alongside the generated automation script. Highlight how the main business logic is represented and identify any dependencies or constructs that require manual adjustment.

**Step 6 — Validate the converted implementation**

Explain that developers must review the generated script, confirm compatibility with the target Maximo environment, and test the business behavior in a non-production environment. AI-generated code should not be treated as production-ready without validation.

**Step 7 — Summarize the business value**

Close by highlighting reduced manual conversion effort, improved maintainability, and the potential to simplify legacy Maximo customizations. Explain how the reusable building block can be adapted to other conversion scenarios where the source code and target automation model are suitable.