Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
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.
Maximo Asset
Maximo Spatial
Management
Asset Maximo Industry TRIRIGA Portfolio -
7.5.0.0
Management Solutions TBD
7.5.0.0 7.5.0.0
• Oil & Gas
IBM Real Time Maximo Asset Mgmt
Asset Locator Maximo Asset • Transportation IBM Real Time 7.5.x.0
for Healthcare Configuration • Utilities Asset Locator
7.5.0.0 Manager 7.5.0.0 • Industry Solutions
• Life Sciences 7.5.0.0
• Add-on’s
• Nuclear Power
• Government TRIRIGA Portfolio
Maximo Asset Maximo for Service Maximo Adapter - TBD
Mgmt. Essentials Providers 7.5.0.0 for Oracle Maximo DCIM 7.5.x.0
7.5.0.0 7.5.0.0
Maximo for
Maximo for Internal Maximo Archiving Safety, Risk & Intelligent Building
Maximo Mobile Service Providers with Optim Data Maximo Adapter Compliance management
Suite 7.5.0.0 7.5.0.0 Growth for SAP 7.5.0.0 7.5.0.0 Solution 1.x
Solution 7.5.0.0
Maximo
Maximo for Data Maximo Mobile
Scheduler
Center Fix-pack 6.2.8 Fix-pack 7.1.1.9 Fix-pack 7.5.0.1 7.5.x.0
7.5.0.0
Infrastructure
Mgmt 7.5.0.0
Maximo Everyplace
Maximo Adapter 7.5.x.0
for Primavera Intelligent Fix-pack 7.1.1.10
Maximo 7.5.0.0 Building
Everyplace Management
7.5.0.0 Solution 1.1.0.0 Fix-Packs
TAMIT 7.5.0.0
Maximo Adapter
for Microsoft 7.5.0.0
Project 7.5.0.0 TSRM 7.5.0.0 Releases
New Products
CCMDB 7.5.0.0
Maximo adapter
Planned
for ITM 7.5.0.0
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 !
• Expanded Capabilities
1. New & Enhanced Supply Chain • Customer Driven Requirements
Management •Satisfy Functional gaps
• PO/PR/RFQ/Invoicing •Improved Usability/Maintainability
– “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 © 2011 IBM Corporation
– “Better user interface. Better performance. Additional applications available.”
Maximo 7.5 Highlights
LDAP
– Tivoli Directory Server 6.3
– Windows Server AD 2008 R2
V7 Reporting
Created on Fly
Created in BIRT Report Designer
No Database/Java Skills Needed
Requires Database/Java Skills
Variable Content/Format
Fixed Content/Format
Leads to Tremendous Time + Cost Savings!
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
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.
Materials Management
– Consignment Inventory
Adds support for ‘vendor-owned’ inventory valuation. Allows for items to be paid for on use rather
than pay on receipt
Purchasing
PO Revisioning
– Benefit: Improves the process for creating PO revisions. Applies the 6.x revision capabilities to the
PO application.
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.
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.
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.
Accounting Enhancements
Chart of Accounts - Date ranges for account validity
– Benefit: Addresses customer-requested functional gap.
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.
KC
KC
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
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
Kansas
Colorado
Texas
Site 4
Repair Facility: Plano
Site 5
Site 6
Repair Facility Site: Texas
Plano Repair Facility Repair
Asset: KC Facility 3
USA Organization 2
Database/Enterprise
Repair Facilities
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.
New Calendar
New calendar
control offers faster
response to clicks
because it does not
make round trips to
the server.
Event Propagation
BIDI support
Application-based Importing/Exporting
Migration of WS Configuration
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.
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
– Provides improved/expanded support for authorization as it relates to an integration message.
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.
App Import/Export
Feature
– 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.
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
– Provides improved/expanded support for authorization as it relates to an integration message.
Export/Import toolbar
buttons
•Added through Object
structures
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).
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
Feature Benefit
“Pick and choose” configurations Packages can be assembled one configuration at a
to be migrated time without need for complex SQL or behind the
scenes change tracking
Enable auto-approved package Reduce time and effort needed to define packages
definitions
Add to collection
Collect directly in app
Collect based on
events
Validate
Preview
Define
/Generate
Create Distribute Deploy
Source product instance Target product instance
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)
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
Escalation
UI constructs
Field
Action Object Events Others..
Validations
Script Driver
Script Driver
Script Engine
Script Engine
Script Engine
Tpae Database
Script
68 © 2011 IBM Corporation
IBM Maximo Briefing
Launch Point
Binding
Bindings application/configuration
data to variables
Backup
Upgrade to 7.5
https://www-304.ibm.com/support/docview.wss?rs=3214&context=SSLKT6&uid=swg21266217