IBM Software Group | Tivoli software


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

IBM Software Group | Tivoli software

  1. 1. IBM Maximo Asset Management 7.1 Highlights Ron Wallace, Maximo Product Marketing Chuck Bandy, Maximo Sales Engineer Chris Norton, Maximo Sales Engineer
  2. 2. Maximo Asset Management 7.1 Highlights <ul><li>Enhanced User Interface and Security Capabilities </li></ul><ul><li>Migration Manager </li></ul><ul><li>Linear Assets </li></ul><ul><li>Other Asset Enhancements </li></ul><ul><li>Enhanced Process and Work Management </li></ul>*Linear Assets is an add-on available for Maximo Asset Management 7.1
  3. 3. 7.1 Highlights – Security and UI
  4. 4. Conditional, Dynamic Security <ul><li>Data Restrictions </li></ul><ul><ul><li>Control Access Characteristics to Objects and Attributes based on Data and/or User Group </li></ul></ul><ul><ul><li>Characteristics include “Read Only” and “Hidden” </li></ul></ul><ul><ul><li>Examples: </li></ul></ul><ul><ul><ul><li>Tradesmen User Group cannot view WOs in “Waiting Approval” Status </li></ul></ul></ul><ul><ul><ul><li>Hide pay rate field on the Labor record based on user group; e.g. Tradesman </li></ul></ul></ul><ul><ul><ul><li>Hide WO cost fields for Tradesmen, but visible for Supervisors </li></ul></ul></ul><ul><ul><ul><li>WOs in “Complete” Status are read-only for Tradesmen User Group, but not for Planners </li></ul></ul></ul><ul><ul><ul><li>Asset records are read-only if the status is “Salvage” </li></ul></ul></ul><ul><li>Application Access </li></ul><ul><ul><li>Conditional Access to Applications </li></ul></ul><ul><ul><ul><li>Read, Insert, Modify and Delete </li></ul></ul></ul><ul><ul><li>Conditional Access to Actions </li></ul></ul><ul><ul><ul><li>E.g., Change Status, Add to New Parent, View Total Costs, etc. </li></ul></ul></ul>
  5. 5. Conditional Expression Manager <ul><li>Persistent Definition and Re-use of Common Conditions </li></ul>
  6. 6. Conditional Access
  7. 7. Data Restrictions You can create a Data Restriction that applies to only one application Checking this box will set the system to re-evaluate the condition when a user tabs out of a field. If it is unchecked, the condition will be re-evaluated on save. Select a existing condition or use the ‘GOTO’ to create on in Conditional Expression Manager <ul><li>Object and Attribute Level Restrictions </li></ul><ul><li>Can be made Read Only, Required or Hidden </li></ul><ul><li>Can be Conditionally Applied </li></ul>
  8. 8. Conditional UI <ul><li>Control the UI based on Data and/or User Group </li></ul><ul><ul><li>Controls characteristics of UI Controls </li></ul></ul><ul><ul><ul><li>E.g., Fields, Table Windows, Tabs, Buttons, Actions, etc. </li></ul></ul></ul><ul><ul><li>Characteristics include “Required”, “Read Only”, “Hidden” </li></ul></ul><ul><li>Examples: </li></ul><ul><ul><li>Hide Asset Application Safety tab for IT Users </li></ul></ul><ul><ul><li>Different labels, colors, etc on the same field for different groups of users; e.g. “Labor” for US users and “Labour” for Canadian or UK users </li></ul></ul>
  9. 9. Associating a “Sig Option&quot; with a Control Specify the SIGOPTION in this field
  10. 10. Conditional UI Properties
  11. 11. 7.1 Highlights – Migration Manager
  12. 12. Migration Manager: Maximo Configuration Capabilities <ul><li>Maximo releases provide increasing configuration capabilities </li></ul><ul><ul><li>Fewer customizations (coding) </li></ul></ul><ul><li>Current migration process is cumbersome </li></ul><ul><ul><li>Manually executed database scripts, export/import </li></ul></ul><ul><ul><li>Prone to sequencing errors </li></ul></ul><ul><ul><li>Seeding often </li></ul></ul><ul><ul><li>incomplete (“I missed </li></ul></ul><ul><ul><li>that configuration!”) </li></ul></ul>Maximo 5.2 Maximo 6.2.1 Maximo 7.1 <ul><li>Security </li></ul><ul><li>Workflow </li></ul><ul><li>Screen Designer </li></ul><ul><li>Database Configuration </li></ul><ul><li>Reports </li></ul><ul><li>Application Designer </li></ul><ul><li>Domains </li></ul><ul><li>Sets </li></ul><ul><li>Cron Tasks </li></ul><ul><li>Communication Templates </li></ul><ul><li>Escalations </li></ul><ul><li>Enhanced Security </li></ul><ul><li>Enhanced Workflow </li></ul><ul><li>Database Configuration </li></ul><ul><li>Enhanced Reports </li></ul><ul><li>OMP Integration </li></ul><ul><li>Web Services Library </li></ul><ul><li>Launch In Context </li></ul><ul><li>Configuration Import/Export </li></ul><ul><li>Logging </li></ul><ul><li>Properties </li></ul><ul><li>Application Designer </li></ul><ul><li>Domains </li></ul><ul><li>Sets </li></ul><ul><li>Cron Tasks </li></ul><ul><li>Communication Templates </li></ul><ul><li>Escalations </li></ul><ul><li>Enhanced Security </li></ul><ul><li>Enhanced Workflow </li></ul><ul><li>Database Configuration </li></ul><ul><li>Reports </li></ul>Configuration applications in Maximo
  13. 13. Configuration Migration Process <ul><li>Migration of Configurations between Maximo environments </li></ul><ul><li>Supports standard rollout environments: </li></ul><ul><ul><li>DEV->TEST->PRODUCTION </li></ul></ul><ul><li>Purpose: </li></ul><ul><ul><li>Seed a new Maximo environment with all configurations and customizations </li></ul></ul>DEV DB Development Server TEST DB Test Server PROD DB Production Server 1 PROD DB Production Server 2 PROD DB Production Server 3
  14. 14. Migration Manager <ul><li>Manages Packages - containers for Maximo configuration information </li></ul><ul><li>Package has a life-cycle: </li></ul><ul><li>Package can be “Snapshot” or “Delta” </li></ul><ul><li>Configuration Import/Export also provides: </li></ul><ul><ul><li>Snapshot configuration/customization for support purposes (IBM support) </li></ul></ul><ul><ul><li>General purpose package-based export/import tool between Maximo environments </li></ul></ul><ul><ul><li>Packaged content delivery through OPAL </li></ul></ul>Define Create Distribute Deploy
  15. 15. Migration Groups <ul><li>Migration Groups define logical sets of Objects (and their relationships) </li></ul><ul><li>Also defined is the Order, which ensure that data being Migrated is appropriately sequenced </li></ul><ul><li>New Groups can be defined in addition to those delivered out of the box </li></ul>
  16. 16. Package Definition
  17. 17. Package Creation
  18. 18. Benefits <ul><li>Lower implementation costs </li></ul><ul><ul><li>Standardized process to promote product configurations </li></ul></ul><ul><ul><li>Reuse of existing Maximo technology </li></ul></ul><ul><ul><li>No separate tools or utilities </li></ul></ul><ul><ul><li>Automation of many manual tasks </li></ul></ul><ul><li>Adhere to IT policies and regulations </li></ul><ul><ul><li>Adapt the migration to client’s specific needs </li></ul></ul><ul><ul><li>Plan for and control migration tasks </li></ul></ul><ul><ul><li>Track and report on migration tasks </li></ul></ul>
  19. 19. 7.1 Highlights - Linear Assets
  20. 20. Linear Assets Non linear Assets Linear Assets Mobile (fleet, vehicles) Fixed Physical Assets (facilities) Component-based Assets (aircraft, ship) Roads Pipelines (sewers, oil pipelines) Railway tracks A non Linear Asset occupies a defined space and can be tracked by its location or modeled as part of a parent child hierarchy Linear Assets have linear properties and often connect with each other by their relationship with the linear infrastructure itself Installed, maintained, replaced as a whole Preserved and restored in place, and in segments
  21. 21. Linear Assets 0 50 Asset A Speed Limit 65 55 Lanes 4 3 Pavement Concrete Surface Exits 0 40 25 50 WO 127 WO 128
  22. 22. Linear Assets <ul><li>Extended Asset Definition </li></ul>
  23. 23. Linear Assets - Specifications <ul><li>Linear asset attributes apply to segments of an asset </li></ul>
  24. 24. Assets and Locations
  25. 25. Creating Work Orders, Tickets from Assets
  26. 26. Reporting Downtime in the Asset Application
  27. 27.
  28. 28. Modifying Downtime History
  29. 29. <ul><li>This dialog can also be accessed from the Work Order Application - you can modify only those entries that belong to the current work order </li></ul>
  30. 30. Counting Parts issued to an Asset
  31. 31.
  32. 32.
  33. 33. Asset Specification History
  34. 34. Asset Collections
  35. 35. 7.1 Highlights - Process and Work Management Enhancements
  36. 36. Multiple Assets and Locations on Work Orders <ul><li>Work Orders and Tickets will allow multiple assets, locations and CIs to be associated. </li></ul><ul><li>Does not support distributed costs (still just one GL Account) </li></ul><ul><li>New look-up actions to populate the ‘Multi’ table </li></ul><ul><ul><li>Multi-select for Assets/Locations/CIs </li></ul></ul><ul><ul><li>Multi-select from Routes and Collections </li></ul></ul><ul><ul><li>Multi-select from ‘Multi’ entries on other records (hierarchical or related records) </li></ul></ul><ul><li>Move/Swap/Modify Asset action enhanced to take advantage </li></ul>
  37. 37. Asset Move/Swap/Modify <ul><li>The action will now support the new Multi Asset/Loc/CI table </li></ul><ul><ul><li>No longer will the list of Assets/Locations be stored as child work orders </li></ul></ul><ul><li>A true ‘Swap’ option is now offered where an asset can be swapped out for a replacement </li></ul><ul><li>User and Custodianship can be modified via the action </li></ul>
  38. 38. Nested Job plans <ul><li>Nested Job Plans allow Work Order hierarchies to be created </li></ul><ul><li>If a Job Plan Task has a Nested Job Plan defined, it will create a child work order instead of a task </li></ul><ul><li>Nested Job Plans can have job plans nested underneath them as many levels deep as desired </li></ul><ul><li>The Create Job Plan from Work Plan action is enhanced to enable the creation of Nested Job Plans </li></ul><ul><li>The Remove Work Plan action is enhanced to support the removal of child work order records </li></ul>
  39. 39. Automated Process Flow for Work Orders <ul><li>Embedded work flow process in Job Plans and Work Orders </li></ul><ul><li>Automatically ‘start’ new records when all predecessors are completed </li></ul><ul><li>Automatically complete work orders when all tasks have been completed </li></ul><ul><li>Do not allow inheritance of start and complete status changes </li></ul><ul><li>Optionally turn on this feature or not </li></ul>
  40. 40. Automated Process Flow <ul><li>Control the status flow of a work order based on task sequencing. </li></ul>Precedence logic Flow Control processing WBS hierarchy <ul><li>Business rules start eligible children down the hierarchy </li></ul><ul><li>Business rules start eligible siblings in the network </li></ul><ul><li>Business rules complete parents when children are completed </li></ul><ul><li>New Work Order Task Application </li></ul>
  41. 41. New Activities & Tasks Application <ul><li>The existing Activities application will be replaced by a new ‘Activities & Tasks’ application </li></ul><ul><li>Designed to farm work out to laborers/technicians </li></ul><ul><li>Similar to Quick Reporting </li></ul><ul><li>Designed for executing single Tasks or Activities </li></ul><ul><ul><li>Not designed for hierarchies </li></ul></ul><ul><ul><li>Not designed for planning </li></ul></ul><ul><li>Screens have been pared down for ease of use </li></ul><ul><li>Cannot create new records </li></ul><ul><li>Standard use case is that this application launches based on a selection from a user’s inbox/workview. </li></ul>
  42. 42. Thank you