IBM Maximo Asset Management 7.5
Release Highlights
May 5, 2011
© 2011 IBM Corporation
IBM Maximo Briefing
Disclaimer
The information on new products is intended to outline our
general product direction and it should not be relied on in
making a purchasing decision. The information on new
products is for informational purposes only and may not be
incorporated into any contract. The information on new
products is not a commitment, promise, or legal obligation
to deliver any material, code or functionality. The
development, release, and timing of any features or
functionality described for our products remains at our sole
discretion.
© 2011 IBM Corporation
2011 Asset Management
Product
Roadmap
IBM Maximo
Briefing
Maximo Asset
Management
7.5.0.0
IBM Real Time
Asset Locator
for Healthcare
7.5.0.0
Maximo Spatial
Asset
Management
7.5.0.0
Maximo Asset
Configuration
Manager 7.5.0.0
Maximo Asset
Mgmt. Essentials
7.5.0.0
Maximo for Service
Providers 7.5.0.0
Maximo Mobile
Suite 7.5.0.0
Maximo for Internal
Service Providers
7.5.0.0
Maximo Industry
Solutions
7.5.0.0
• Oil & Gas
• Transportation
• Utilities
• Life Sciences
• Nuclear Power
• Government
Maximo Archiving
with Optim Data
Growth
Solution 7.5.0.0
Q2 2011
Maximo for Data
Center
Infrastructure
Mgmt 7.5.0.0
Maximo
Everyplace
7.5.0.0
Maximo
Scheduler
7.5.0.0
Maximo Adapter
for Primavera
7.5.0.0
Maximo Adapter
for Microsoft
Project 7.5.0.0
Fix-pack 6.2.8
Intelligent
Building
Management
Solution 1.1.0.0
TRIRIGA Portfolio TBD
Maximo Asset Mgmt
7.5.x.0
• Industry Solutions
• Add-on’s
IBM Real Time
Asset Locator
7.5.0.0
Maximo Adapter
for Oracle
7.5.0.0
TRIRIGA Portfolio
- TBD
Maximo DCIM 7.5.x.0
Maximo Adapter
for SAP 7.5.0.0
Maximo for
Safety, Risk &
Compliance
7.5.0.0
Q3 2011
Q4 2011
2012
Fix-pack 7.1.1.9
Fix-pack 7.5.0.1
Maximo Mobile
7.5.x.0
Fix-pack 7.1.1.10
Intelligent Building
management
Solution 1.x
Maximo Everyplace
7.5.x.0
TAMIT 7.5.0.0
Fix-Packs
TSRM 7.5.0.0
7.5.0.0
Releases
New Products
Maximo adapter
for ITM 7.5.0.0
CCMDB 7.5.0.0
Planned
Releases
The information on the new product is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information on the new product is
for informational purposes only and may not be incorporated into any contract. The information on the new product is not a commitment, promise, or legal obligation to deliver any material,
2code or functionality. The development, release, and timing of any features or functionality described for our products remains at our sole discretion. .
© 2011 IBM Corporation
IBM Maximo Briefing
What’s Next?......
Maximo 7.5 !
Released on April 29, 2011
3
© 2011 IBM Corporation
IBM Maximo Briefing
Maximo 7.5 – 3 Major Areas of Focus
• Expanded Capabilities
1. New & Enhanced Supply Chain
Management
•Satisfy Functional gaps
•
PO/PR/RFQ/Invoicing
•Improved Usability/Maintainability
•
Inventory/Receiving
•Address Integration/ERP
2. Return on Investment
• Additional Configuration
•
Automation Scripts
• Lower Cost of Implementation
•
Application data Import/Export
•
• Lower Cost of Ownership
Enhanced Migration Manager
•
Usability & Performance
3. Continued Leadership and
Innovation in EAM
4
• Customer Driven Requirements
•
Enhanced Work & Asset Management
•
Linear Asset Visual Control
• Easier to configure & support
• Deep Vertical Functionality
• Improved End-User interaction
© 2011 IBM Corporation
IBM Maximo Briefing
Maximo 7.5– Expanded Footprint
Asset
Management
Work
Management
Materials
Management
Purchasing
Locations
Job Plans
Item Master
Request for Quotation
• Repair Facilities
• Revisioning
Storerooms
Asset
Work Order Tracking
Inventory
Asset Templates
•Assignment Tab
•Inventory Usage
Shipment Receiving
Failure Codes
•Hard/Soft Reservations
•LIFO/FIFO Costing
Purchase Requisitions
Linear Assets
•Repair Facilities
• Consignment
•Invoices
• Visual Control
Safety
• Transfer via
Condition Monitoring
Quick Reporting
Meters
Meter Groups
Contract
Management
Service
Management
Receiving
Purchase Contracts
Service Groups
Receiving Inspections
Master Contracts
SLA Management
Warranty Contracts
Change Management
Lease/Rental Contracts
•Incidents
• Invoice Reversals
Labor Rate Contracts
•Problems
Shipment
Purchase Orders
•Premium Pay Rates
•Changes
Labor/Crafts
• Default Costing
• Revisioning
Payment Schedules
•Releases
Tools
Condition Codes
• Receipt Tolerance
Preventive Maintenance
Stocked Tools
Desktop Requisitions
• PM Forecasting
Service Items
•Solutions
Master PM
Assignment Manager
Enhanced Workflow – Event Driven, Context-based / Escalation Manager
KPIs / Reporting/ Ad-hoc Reporting / Cognos Integration
Security/Administration/Configuration – Automation Scripts, Migration Manager
Integration/Web Services – Import & Export direct from applications
5
© 2011 IBM Corporation
IBM Maximo Briefing
Maximo 7.5 Beta program
 Maximo 7.5 Beta testing – started in December 2010
– Hosted in a cloud by the beta team in India
– Over 15 client companies & business partners
– Global coverage with cross-industry representation
North America, Asia, Middle East & Europe
Southern Company, Duke, KNPC, Hong Kong Jockey Club, Bluewater, others
– 50+ individuals as registered testers, additional companies/testers added weekly
– Excellent participation, customers actually testing
Over 75 unique postings of feedback, questions, comments, bugs
Focus on Supply Chain, but also hitting Work Management applications
6
© 2011 IBM Corporation
Maximo 7.5 Beta program
– Participant Quotes
IBM Maximo Briefing
– “Happy to see Supply Chain getting new functionality”.
– “Could see good amount of improvements, administration point of view, saves time/increases
accuracy in migrations and reduces number of outages for smaller changes.”
– “The Beta 7.5 was a great reference which desperately helped with insight into updates. For
the majority I was pleased with the site. Maximo 7.5 incorporates major changes which allow
more flexibility and less customization. “
– “Greatly Improved on the SCM side. Can see where the foundation is being laid for next
generation Maximo to be a complete Supply Chain and Work Management Solution.”
– “Some new features added on SCM that make it competitive to other ERP packages like
SAP” .
– “The Beta of Maximo 7.5 is impressive and superb! The new design, the speed and the
quality are incredible. Happy to see that some changes requested from us are now in the core
product.”
– “Upgrading to Maximo 7.5 will require the least change management compared to any other
Maximo upgrades we have applied.”
– “The Modules in Maximo I've tested have been working perfect so far. No Errors
encountered.”
7
– “Better user interface. Better performance. Additional applications available.”
© 2011 IBM Corporation
Maximo 7.5 Highlights
© 2011 IBM Corporation
Maximo Briefing
Maximo 7.5 TechnicalIBMPlatform
Developed on current R7.1 Architecture:
 J2EE based Enterprise Application
– Web Application Interface for users to access Maximo applications via
Browser
– Fully configurable from presentation content to the business logic
– Configurable Authentication (Database based or LDAP based)
– Integration mechanisms via Web Services, JMS, HTTP, EJB, XML files, Flat
files and Interface tables in database
– Built-in reporting using BIRT/Cognos/TCR and support for integration with
customer’s reporting systems
 Supported Application Servers
– IBM WebSphere Server
– Oracle WebLogic Server
 Supported Database Platforms
– DB2
– Oracle
– MS SQL Server
9
© 2011 IBM Corporation
IBM Maximo Briefing
Maximo 7.5 Planned Platform Updates
Updated:
 Operating Systems
– AIX 7.1
– RHEL 6
 Database
– DB2 9.7
– DB2 9.8
 Application Servers
– Websphere Server 7
– Weblogic Server 10.3
Deprecated:
 Operating Systems
–
–
–
–
–
AIX 5.3
RHEL 3
RHEL 4
SLES 9
All Linux 32 bits flavors
 Database
– DB2 8.2
– DB2 9.1
 Application Servers
– WebSphere 6.1
 LDAP
– Tivoli Directory Server 6.3
– Windows Server AD 2008 R2
10
© 2011 IBM Corporation
IBM Maximo Briefing
Maximo Open Report Architecture
V7 Reporting
Embedded
Integration
Integration
Integration
Externalized
BIRT
Cognos
Reporting 8
Tivoli
Common
Reporting
External
Report
Integration
Open
Database
Platform
(free)
(free)
DB2
11
© 2011 IBM Corporation
IBM Maximo Briefing
Types of Core BIRT Reports Available
Enterprise, Formatted Reports
for Heavy, Multi-User Access
Created in BIRT Report Designer
Requires Database/Java Skills
Fixed Content/Format
12
Ad Hoc, Dynamic Reports
for Individual Use
Created on Fly
No Database/Java Skills Needed
Variable Content/Format
Leads to Tremendous Time + Cost Savings!
© 2011 IBM Corporation
IBM Maximo Briefing
Enhancements Areas
 Supply Chain
–
–
–
–
–
Materials Management
Purchasing
Receiving
Invoicing
Misc
 Work and Asset Management
–
–
–
–
–
Work Order
Job Plan
Repair Facility
Assets
PMs
 Usability
– Improved Efficiency
– New Skin
 Maximo Integration Framework (MIF)
 Migration Manager
 Scripting
13
© 2011 IBM Corporation
IBM Maximo Briefing
Materials Management
 Item Master – Add ‘true’ stocked/non-stocked item support
– Resolves functional gap on usage of stocked/non-stock item terminology. Better alignment with
ERP systems.
 Inventory Usage Application – Add a ‘statusable’ document for issuing and transferring
items
– Provides for streamlining the issue and transfer process while increasing the breadth of
functionality: Support for workflow of issues and transfers, staged and shipped items, multiple
assets and source bins per line.
 Issues and Transfers – Transfer via Shipment
– Enhances and streamlines business process for items in transit. Serves as a foundation for
manifesting for Oil & Gas customers.
 Issues and Transfers – Hard/Soft material reservations
– Addresses functional gap in materials mgt by allowing requested items to be set as a hard or soft
reservation.
14
© 2011 IBM Corporation
IBM Maximo Briefing
Materials Management
 Inventory Costing Enhancements
– Default Costing Method (Avg, Std, LIFO, FIFO)
Allows the user to set the costing method for an item at the inventory level.
– LIFO/FIFO Inventory Costing
‘New’ costing method to allow for valuation at actual receipt costs on a LIFO or FIFO basis
– Consignment Inventory
Adds support for ‘vendor-owned’ inventory valuation. Allows for items to be paid for on use rather
than pay on receipt
15
© 2011 IBM Corporation
IBM Maximo Briefing
Purchasing
 PO Revisioning
– Benefit: Improves the process for creating PO revisions. Applies the 6.x revision capabilities to the
PO application.
 PR/PO/RFQ/RECEIPTS/INVOICE – View entire supply chain
– Will provide the user with the ability, from one screen, to view all upstream and downstream
processing of any line items currently in the supply chain.
 Item Master, PO – Tax exempt items
– Provides support for setting items as ‘tax-exempt.’ Tax exempt items will bypass the normal tax
code application process on purchasing lines.
 RFQ: Allow item comparison in base currency
– Currently, quotes may be submitted in various currencies and there is no valid way to compare the
line items in this case. The functionality will use the Exchange Rates app to display the line items in
the native and base currency.
16
© 2011 IBM Corporation
IBM Maximo Briefing
Receiving
 Receipt Tolerances
– Provides functionality to control against ‘over-receipt’ of lines against a PO. Establishes a tolerance
threshold at which the user can be either warned or stopped during an over-receipt situation.
 Add functionality for returning received services
– Brings service receipt return functionality in line with what is offered for material receiving.
 Support for voiding a receipt. (ie: cancelling a receipt line)
– Allows the reversal of a receipt line, similar to a return, and reverse balance updates, etc, but would
NOT allow the user to create a credit invoice for the voided line.
 Receiving application requires functionality to select an asset for return to a vendor
– Provides the functionality to select the asset being returned and business logic to disable the use of
the returned asset records.
17
© 2011 IBM Corporation
IBM Maximo Briefing
Invoicing
 Ability to create invoice reversals
– Allows the creation of reversal invoices against PO lines that have already been fully matched. Also
allows for the ability ‘back out’ an approved, but incorrect invoice.
 Cross Site Invoices
– Ability to create an Invoice containing POs from other sites in the same Org.
 Enhance ‘Copy PO Lines’ dialog box
– Enhances usability by allowing invoice users to filter on additional fields.
 Add functionality for setting the date to derive the financial period
– Benefit: A Posting Date will be added to the invoice header to be used to derive the financial period.
 Default Table Window
– A new Default Table Window added to the Invoice Lines tab
18
© 2011 IBM Corporation
IBM Maximo Briefing
Accounting Enhancements
 Chart of Accounts - Date ranges for account validity
– Benefit: Addresses customer-requested functional gap.
 Chart of Accounts – Different GL account structures per Organization
– Addresses customer-requested functional gap.
– Better alignment with ERPs.
19
© 2011 IBM Corporation
IBM Maximo Briefing
Miscellaneous Supply Chain enhancements
 Labor Contracts – Premium pay rates on labor contracts
– Allows that the same options that are available on the labor record would be available on the labor
contract record.
 Organizations – Support multiple addresses per site
– Allows for additional addresses to be registered against a site. This data will be used by the
purchasing applications in the scenario where multiple ship-to and bill-to addresses are possible
per site.
 Person – Associate multiple commodity codes with a person record
– Benefit: Satisfies the use case of a ‘buyer’ person record. Person records associated with these
commodity codes could then be used within workflow etc, for routing purchasing documents to the
appropriate individual.
20
© 2011 IBM Corporation
Work and Asset Management
© 2011 IBM Corporation
IBM Maximo Briefing
Work Management Enhancements
 Work Order Tracking – Additional Cost information displayed in the work order
– Adds additional visibility into related purchasing records from a work order.
 Work Order Tracking – Add visibility for storeroom materials on backorder
– Fills a functional gap in work orders by adding visibility of a ‘waiting material’ situation for storeroom
items in addition to direct issue items.
 Assignments tab added to Work Order app
– Enables labor assignments directly on the Work Order
 Job Plan Revisioning
– Optional system setting to enforce tracking of JP revisions/revision history
 PM Forecast tab added to app
– Ability to generate forecasted dates for Preventative Maintenance records
 Decoupling Owner and Owner Group
– Ability to assign both to a Work Order or Ticket based record
22
© 2011 IBM Corporation
IBM Maximo Briefing
WO Costs and Material Status
23
© 2011 IBM Corporation
IBM Maximo Briefing
Assignments tab – enables labor assignments directly on the
Work Order
24
© 2011 IBM Corporation
IBM Maximo Briefing
Job Plan Revisioning – optional system setting to enforce
tracking of JP revisions/revision history
25
© 2011 IBM Corporation
IBM Maximo Briefing
PM Forecast tab – ability to generate forecasted dates for
Preventative Maintenance records
26
© 2011 IBM Corporation
Repair Facility
© 2011 IBM Corporation
IBM Maximo Briefing
Requirement
 Some assets operate across the virtual geographical boundaries of Maximo sites
– Repair and maintenance work may need to be performed at a facility that is not in the same Maximo site as the asset
– “How can I EASILY insert a work order for an asset from a site other than my default insert site?”
 The Maximo work order defaults to a site and the asset must be in this site
– The work order is “owned” by the site and location of the asset
– Customers want the ability to have the location performing the work to “own” the work order and potentially be in a different site than
the asset.
28
© 2011 IBM Corporation
IBM Maximo Briefing
Fixed Assets vs Mobile Assets
KC
Work Order: 1234
Asset: HVAC
Asset Home Location: Denver
KC
Repair Location: Denver
KC
Work Order: 5678
Asset: KC
Asset Home Location: Kansas City
KC
Repair Location: Plano
29
© 2011 IBM Corporation
IBM Maximo Briefing
Solution
 Allow users to EASILY insert work orders for assets from any site
– New asset field validation allows valid assets from multiple sites
 Introduce the concept of a Repair Facility
– A location identified as a Repair Facility (check box)
 Work order based records can be assigned a repair facility
– Work orders, changes, releases
 The repair facility can be from a site other than current site
– Within the same organization
 New security groups feature for Repair Facility authorizations
– Works in concert with site authorizations to determine records user can work with
 Users can have a default repair facility
30
© 2011 IBM Corporation
IBM Maximo Briefing
User Scenarios
 The most common scenario is for clients with mobile assets with multiple sites defined in Maximo
– Assets that can travel across the virtual boundaries defined by Maximo sites
– For example an asset based in Atlanta in the Southeast US site travels to Boston in the Northeast US site. The repair facility in
Boston owns the work and the work order, but the asset is from another site
 Clients with fixed assets or with only one site may also find benefit to having the further control
over security for work order based records
– Limiting maintenance personnel to records only for their repair facility
31
© 2011 IBM Corporation
IBM Maximo Briefing
Multisite Architecture with Repair Facilities
Work Order: 5678
Site 6
USA
Site 5
Denver Repair Facility
Site 4
Texas
Kansas
Colorado
Plano Repair Facility
Repair Facility: Plano
Repair Facility Site: Texas
Repair
Facility 3
Asset:
KC
Repair Facility 4
Asset Site: Kansas
Organization 2
Database/Enterprise
32
© 2011 IBM Corporation
IBM Maximo Briefing
Repair Facilities
Site for the Work
Order and Asset
Site where the
work is done
33
© 2011 IBM Corporation
IBM Maximo Briefing
Asset Management Enhancements
 New Asset Template application
– Provides a quick way to add new Assets or update existing Assets based on defined template
 Asset list from Template
– list of assets created from Asset Template generation, all create at once
 Visual Control for Linear Assets
– Visual Control tab enables graphical display of linear assets, features, attributes and work orders
34
© 2011 IBM Corporation
IBM Maximo Briefing
New Asset Template application – quick way to add new
Assets or update existing Assets based on defined template
35
© 2011 IBM Corporation
IBM Maximo Briefing
Assets – list of assets created from Asset Template generation, all
create at once
36
© 2011 IBM Corporation
IBM Maximo Briefing
Linear tab in Assets – Visual Control enables graphical
display of linear assets, features, attributes and work orders
37
© 2011 IBM Corporation
Usability
© 2011 IBM Corporation
IBM Maximo Briefing
Improved Efficiency Enhancements
 Returning to List Tab maintains Record focus
– After editing an record going back to the list tab will return to the edited record
 Field Validation option
– Performed in background allowing the user to continue data entry
– Set as default at system level
 Rich Text Editor for Long Description and Com Templates
– Supported by BIRT reports
 Improved Date Entry
– Quicker and easier to select values
 Help moved to Info Center format
– Content based.
39
© 2011 IBM Corporation
List page
IBM Maximo Briefing
When I save a record and go back
to the List, the result set is still in
the state I left it until I hit refresh.
Records that have been touched
are Italicized to indicate they have
changed
40
© 2011 IBM Corporation
Table Window
IBM Maximo Briefing
When I save, focus remains
on the last table row that
was edited
41
© 2011 IBM Corporation
‘Heads down data entry’ IBM
(Asynchronous
Validation)
Maximo Briefing
I can enter data at my own
pace, and address errors and
warnings when I want to
42
© 2011 IBM Corporation
IBM Maximo Briefing
I can enter text in the format that I want on a Maximo screen. I don’t need to rely
on attachments for rich-text formatting.
• Long Descriptions, Communication Templates and Displays in BIRT reports
• Flexible Fonts
• Bold, Italics, Underline, etc.
• Character Sizes
• Bullets
• Colors and Highlighting
• URL links
• Supports copy/paste from
Word, etc.
43
© 2011 IBM Corporation
Displays in reports
IBM Maximo Briefing
Enabled Rich Text
Formats to display in
BIRT Reports
44
© 2011 IBM Corporation
IBM Maximo Briefing
New Calendar
New calendar
control offers faster
response to clicks
because it does not
make round trips to
the server.
45
© 2011 IBM Corporation
IBM Maximo Briefing
Help – Info Center, content based
46
© 2011 IBM Corporation
New Skin
© 2011 IBM Corporation
IBM Maximo Briefing
48
© 2011 IBM Corporation
IBM Maximo Briefing
49
© 2011 IBM Corporation
Maximo Integration Framework
© 2011 IBM Corporation
IBM Maximo Briefing
New Integration Framework Features in 7.5

Event Propagation

Support for application authorization

BIDI support

Application-based Importing/Exporting

JAX-WS – Web Service support via the application server container

Migration of WS Configuration
51
© 2011 IBM Corporation
IBM Maximo Briefing
Event Propagation

Feature
–

A new 7.5 feature for the Integration Framework is the ability to recognize events from child objects
within an object structure. In prior releases, this was only supported if the business objects had this
logic embedded within them. Now customers will be able to enable the events from child objects
when the business object does not provide this capability.
Planning
–

This new feature would be applicable in cases of ‘outbound’ integration using Publish Channels. For
use when an event from a child object within an object structure does not initiate an event through the
Publish Channel
Steps
–
How to configure
Using the Object Structure application, select the applicable object structure, choose Advanced
Configuration under the Select Action menu and check the Propagate Events checkbox for the
object where event behavior is desired.
–
Verifying successful configuration
Using the relevant application, update an attribute of that object and verify an outbound integration
messages is sent via the Publish Channel.

Benefits
Provides event-based integration messages to external applications where in previous releases this
behavior did not exist. Customers would often write custom code or do other configuration in order to
work around this limitation.
52
© 2011 IBM Corporation
IBM Maximo Briefing
App Authorization

Feature:
A new 7.5 feature for the Integration Framework is the ability to support the existing application authorization that is
configured for User Groups. In prior releases, integration support for authorization was limited to object restrictions.
This change will allow support for application configured authorization.

Planning
–

This new feature allows integration implementations to leverage the application-based configuration for authorization
for ‘inbound messages’ and Data Export. An object structure can be connected to an application which would, in turn,
point to an authorization configuration for a user group. The user on the inbound integration message would be used
in combination with the application on the object structure to obtain the appropriate authorization configuration.
Steps
–
How to configure
Using the main tab on the Object Structure application, select the applicable application name to associate to the object
structure.
–
Verifying successful configuration
Send an inbound message to Maximo where the action/operation of the message is in conflict with the users
authorization and confirm that a security-related error is generated.

Benefits
–
53
Provides improved/expanded support for authorization as it relates to an integration message.
© 2011 IBM Corporation
IBM Maximo Briefing
BIDI Support

Feature
A new 7.5 feature for the Integration Framework is the ability to support the conversion between the
Maximo BIDI format to an external BIDI format for both inbound and outbound messages

Planning
–

For a Maximo implementation in a BIDI language that requires integration to another application in a
different BIDI format, this new feature provide the capability to transform messages from one BIDI
format to another for both inbound and outbound messages.
Steps
–
How to configure
There is configuration at the object structure, standard service and external systems levels to enable
BIDI. See the Deep Dive section for more details.
–
Verifying successful configuration
Send/Receive messages using a different BIDI format than the one being used within Maximo and
verify proper conversion of data.

Benefits
For those customers operating with BIDI, this features allows them to integrate with another
application in a different BIDI format.
54
© 2011 IBM Corporation
IBM Maximo Briefing
App Import/Export

Feature
–

Planning
–

A new 7.5 feature for the Integration Framework is the ability to enable importing and exporting of
data directly from an application such as Assets or Work Orders.
This new feature allows integration implementations to leverage the application-based configuration
for authorization for ‘inbound messages’ and Data Export. An object structure can be connected to an
application which would, in turn, point to an authorization configuration for a user group. The user on
the inbound integration message would be used in combination with the application on the object
structure to obtain the appropriate authorization configuration.
Steps
– How to configure
Using the main tab on the Object Structure application, select the applicable application name to
associate to the object structure.
–
Verifying successful configuration
Send an inbound message to Maximo where the action/operation of the message is in conflict with the
users authorization and confirm that a security-related error is generated.

Benefits
–
55
Provides improved/expanded support for authorization as it relates to an integration message.
© 2011 IBM Corporation
IBM Maximo Briefing
Application Export/Import
Export/Import toolbar
buttons
•Added through Object
structures
•Controlled through Security
•Imported data is validated
through business logic
•Able to run in Preview mode
56
© 2011 IBM Corporation
IBM Maximo Briefing
JAX-WS compliant web services
 Description
– An important interoperability feature in IBM Tivoli Automation Engine (TPAE) is the deployment of Integration
Framework (I-F) services as web services enabling the interaction with external applications via web service calls.
– Starting in TPAE 7.1, the I-F supports web services interoperability by means of an AXIS2 based implementation:
Inbound - TPAE's web services are deployed to an AXIS2 container for external applications consumption.
Outbound - I-F provides a SOAP handler based on AXIS2 ServiceClient APIs designed to call external web
services.
 Features:
– Incorporate the deployment of web services to TPAE's Application Server Web Service Container by means of JAX-WS
standard.
– Enable use of WS-* standards (WS-Policy, WS-Security, etc).
Leverage application servers to support WS-*
– ITCAM support for TPAE Web Services
– Allows clients to move off Axis Web Service container
– Leverage application servers' support of WS standards (WS-Policy, WS-Security, etc).
57
© 2011 IBM Corporation
IBM Maximo Briefing
Migration of Web Services (WS) Configuration
 Features:
– It is the objective of this enhancement to
Enable the migration of web service configuration between TPAE instances.
Supported via Integration Framework or Migration Manager
 Planning Web Service Deployment
– This new feature would be applicable for customers working with Integration Framework services (Enterprise, Object
Structure, Standard)
– Customers need to identify which web service container is more appropriate for their integration scenarios
For web services created in previous TPAE versions, customers need to decide if a web service
container migration is needed
 Steps
– How to configure
Using the Systems Properties application, set
mxe.int.containerdeploy property value that corresponds to the web service container of
choice. In TPAE 7.5 installations this property value is being set to 1 by default.
Verifying successful configuration
Using the Web Services Library application, select and deploy a web service. Initiate a web service
call from external system.
58
© 2011 IBM Corporation
Migration Manager
© 2011 IBM Corporation
IBM Maximo Briefing
Migration Manager strategy for 7.5
 A set of features is being added to Migration Manager to:
– Enable clients better align Migration Manager with development
environments
– Enable clients and practitioners more easily create and distribute content
(time-to-value)
 Imperatives driving new features:
– Reduce lead times to plan, execute and complete migration
– Reduce overheads on tracking development configurations
 Clients driving new features:
– Key clients in service and asset management
 Product teams driving new features:
– SRM, CCMDB, Maximo, IBM Global Services, business partners
60
© 2011 IBM Corporation
IBM Maximo Briefing
Development support features
 These features are intended to better support development
environments
– Simpler, intuitive collection of configurations
– Facilitate check in/check out against source control system
61
Feature
Benefit
“Pick and choose” configurations
to be migrated
Packages can be assembled one configuration at a
time without need for complex SQL or behind the
scenes change tracking
Improve error processing and
recovery
Reduce cost to development teams to rebuild
packages; correct and re-process existing packages
Enable export/import of
configuration from the “Pick and
Choose” application
Facilitate a source control model – enable check
in/check out of a set of configuration data
© 2011 IBM Corporation
IBM Maximo Briefing
Content creation and distribution features
 These features are targeted towards more a flexible and quicker
content migration model
Feature
Benefit
Enable replacement of chosen
values in a package
Make it easier to distribute content where
site/org/date-time values need to be changed to suit
target environment
Automatically migrate ‘same
as’ objects
Avoid having to manually select and migrate ‘same
as’ objects
Enable migration of objects
across RDBMS
Make it easier to distribute object definitions to
multiple customers/targets with different RDBMS
Relax product compatibility
checks
Make it easier to distribute content across disparate
product installations
Enable auto-approved package Reduce time and effort needed to define packages
definitions
Enable comparison of sources
and targets
62
Differences can be identified pre- or post-migration
accelerating the migration effort
© 2011 IBM Corporation
IBM Maximo Briefing
Tpae 7.5 - Migration Collections and Comparison
Migration Collection
Migration Comparison
Add comparison results to
migration collection
Create
Collect
Validate
Define
/Generate
Go to app/Return
with value
Add to collection
directly in app
Collect based on
events
Preview
Create
Source product instance
63
Compare
Distribute
Deploy
Target product instance
© 2011 IBM Corporation
Scripting
© 2011 IBM Corporation
IBM Maximo Briefing
What is a script?
 Short pieces of code
 Simplified programming model
 Usually used to glue or extend applications
 Usually interpreted (vs compiled Java or C/C++)
 Example – add all asset spare part quantities together and set total into ASSET.SPAREQTY:
spPartSet = mbo.getMboSet('sparepart')
partCount = spPartSet.count()
totalQty = 0.0
for i in range(partCount):
partMbo = spPartSet.getMbo(i)
totalQty += partMbo.getDouble('quantity')
mbo.setValue('spareqty',totalQty)
65
© 2011 IBM Corporation
IBM Maximo Briefing
Why scripting?
 Java skills considered onerous
 Java customizations increase IT costs
– Java/JEE developers
– API knowledge/compatibility
– Performance/functionality issues
– Build process for WAR, EAR, JAR files
– Server shutdown / re-starts
 Scripting promotes simplified programming model
 Scripting is completely dynamic (no server re-starts)
66
© 2011 IBM Corporation
IBM Maximo Briefing
Scripting Strategy for 7.5
 Tpae 7.5 exploits scripting API that is part of JDK 6
– JSR 223 – standardized scripting API for Java
 Supports two script engines out of the box
– Rhino JavaScript (embedded with JDK 6, compliant with JSR 223)
– Jython 2.5.2 (newer version compliant with JSR 223)
 Other JSR-223 compliant script engines can be seamlessly plugged in
– Provides programming flexibility to clients and practitioners
– Example: Jacl, JRuby, Groovy, Jawk
– Place JARs in application server classpath and re-start server
 Tpae scripting can be enabled for many different configurations
– No longer limited to just actions
– Script creation and management remains the same
 Tpae scripting supports simple coding approach
– Launch points offer closer alignment with Tpae applications and configurations
– Script variables and bindings to pass in data and return results
– Detailed knowledge and experience of Maximo APIs not a pre-requisite
67
© 2011 IBM Corporation
IBM Maximo Briefing
Scripting architecture in 7.5
Design Time
Runtime
Workflow
Escalation
UI constructs
Action
Script
Launch Point
Action
Launch
Point
Object Events
Field
Validations
Others..
Object
Launch
Point
Attribute
Launch
Point
Other
Launch
Points
Script Driver
Script Driver
Script Engine
Script Engine
Script Engine
Tpae Database
Script
68
© 2011 IBM Corporation
IBM Maximo Briefing
Scripting constructs in 7.5
Objects
Attributes
Actions
Configuration or application
context for script
Launch Point
Bindings
69
Tpae native
configuration or
application
Binding
application/configuration
data to variables
Variables
Input and output variables
to script
Script
Script executed passing
inputs and returning
outputs
© 2011 IBM Corporation
IBM Maximo Briefing
Backup
70
© 2011 IBM Corporation
IBM Maximo Briefing
Upgrade to 7.5
https://www-304.ibm.com/support/docview.wss?rs=3214&context=SSLKT6&uid=swg21266217
71
© 2011 IBM Corporation
IBM Maximo Briefing
Upgrade to 7.5 (con’t)
72
© 2011 IBM Corporation