1
Resolve before cutover1 underlying observationsMAXIMO UPGRADE ASSESSMENT
Your upgrade. A clear way forward.
7.6.1.3→Manage 9.2Kestrel Energy
RECOMMENDED NEXT MOVE
Proceed with upgrade planning; resolve the named incompatible dependencies before retaining those functions at cutover.
6
Validation required12 underlying observations1
Product and environment decisions8 underlying observations22 observations organised into 8 work packages. A work package groups related decisions and tests; it is not an effort estimate.
Decisions that move the programme forward
Resolve before cutover1 observations
Class removed
Replace the reference. The type does not exist at the target, so the customisation will not compile; find the supported equivalent or remove the dependency.
Owner · Customisation developer
Validation required3 observations
Validate changed datatypes against actual usage
Validate existing values and every cited consumer against the new type, including case, rounding, range and truth semantics. A metadata difference alone does not establish a failing operation.
Owner · Customisation developer
Validation required3 observations
Method removed
Check each cited site. The class survives but this member does not, so a call compiles today and fails at the target.
Owner · Customisation developer
Validation required2 observations
Attribute removed
Change every cited site before cutover. The column is gone at the target: a read throws and a write fails.
Owner · Customisation developer
Assessment scope4 objects3 source files3 supplied surfaces
FROM FINDINGS TO DELIVERY
Clear ownership. A test for every decision.
Agree retained business functions, target products and the named compatibility decisions.
Run the data checks, complete technical work packages and exercise the affected journeys.
Reassess the upgraded export and record target-runtime and business acceptance.
Where the work goes
| Workstream | Packages | Purpose |
|---|---|---|
| Resolve before cutover | 1 | A demonstrated incompatible dependency or unmet prerequisite. Resolve or retire the affected function before cutover. |
| Validation required | 6 | A named data, binding, provider or behaviour check settles the consequence. A failure has not been established. |
| Product and environment decisions | 1 | Confirm products, extensions and installation-specific definitions against the intended target. |
| Information appendix | 0 | Release context and uncited inventory differences, retained for traceability. |
The programme view contains the complete work list. The assurance view contains coverage, provenance and remaining evidence requests. Budgets and dates are agreed against the work packages.
Coverage boundary: 1 presentation-binding occurrences remain unresolved by static analysis. These are coverage gaps, tracked separately from the finding counts.
MXH is not produced, endorsed, certified or supported by IBM. Counts of findings, not of days.