value focused. results driven.
Maximo Configurations vs. Customizations
Frank Vanderham March 24, 2011
Agenda • The business benefits of configurations and customizations • The differences between configurations and customizations • When have configurations gone too far? • Keeping Maximo upgradeable • Demonstration of configurations and customizations
Business Benefits of configuration / customization
Business Benefits of configuration / customization • Increase system adoption and readiness by adjusting Maximo to support your own, specific business processes • Save time by reducing data entry, extensive mouse clicks, etc. • Increase regulatory compliance by hiding or locking down information based on role • Increase total cost of ownership/ROI on Maximo by expanding its use into other business areas
The differences between configurations and customizations
The differences between configurations and customizations Configurations • Performed with standard Maximo tools, online • Requires no programming • Very likely to be upgradeable with new versions • Maintainable by Maximo “super-users” / administrators
Customizations • Modifies Maximo with “outside” tools • Requires Java programming • Will require investigation when considering upgrading Maximo • Maintained by Java developers
Types of Maximo Configurations
Types of Maximo Configurations • Adding new attributes to existing Maximo objects using Database Configuration and App Designer • Making fields required based on conditions • Adding a new Relationship to an object and using it to display Parent-Child records • Show / force a picklist of possible values on fields • “Cross-over” values from one record to another automatically • Create or Modify Start Centers to display data in an actionable way And many, many more….
Types of Maximo Customizations
Types of Maximo Customizations • Create a new Maximo object or application, with its own custom table • Create a “calculated” field • Enforce specific business logic on field validation (e.g. date ranges) • Change business logic or validation during status changes • Integration with 3rd party systems And many, many more….
When have configurations gone too far?
When have configurations gone too far? • Don’t cross the line on “core” Maximo business logic / fundamentals • When your workflow models become too complicated / large • Building views to perform calculations “Lightweight” Configurations • • •
Screen Changes Domain / value list changes Conditional UI
“Heavyweight” Configurations • • •
Workflow Custom Views “Cloned” Applications
When have customizations gone too far? • When your system cannot be upgraded • When they could be achieved with configurations • When they’ve crossed the line on “core” Maximo business logic / fundamentals “Lightweight” Customizations • • •
Java Field Validators / Listeners Custom Workflow Actions Integration “Exit” Classes
“Heavyweight” Customizations • •
Custom Maximo Objects Custom Application Objects
Keeping Maximo Upgradeable • Use configuration wherever possible and feasible • NEVER configure things outside of the Maximo toolset (database objects, custom JSPs, etc.) • Upgrade regularly – don’t fall behind too many versions • Document all changes; not just the “how” – the design, but also the “why” – the requirements • ALWAYS have your customization Java source code in your possession – preferably in a source control system
Demonstration • Configurations: – Add a value list to a field – Making a field required based on conditions
• Customizations: – Using a custom Java Field Validator / Listener
value focused. results driven.
Thank You!
