However, customers are always well aware of known and potential impacts of product upgrades and fixpack installations so it is important to understand and justify time and effort needed for such projects.
A very high-level comparison of features available in Maximo 6.2, 7.1 and 7.5 is represented in this table.
| Features | Maximo 6.2 | Maximo 7.1 | Maximo 7.5 |
| Work and Asset Management | X | X | X |
| Configuration applications | X | X | X |
| Enhanced Reporting | X | X | X |
| Materials Management | X | X | X |
| Workflow | X | X | X |
| Web Services | X | X | |
| Launch in Context | X | X | |
| Migration Manager | X | X | |
| Conditional Expression Manager | X | X | |
| Attached Documents at task level | X | X | |
| Full Supply Chain Capability | X | ||
| Standard technology platform | X | ||
| Application-based data Import/Export | X | ||
| Asset Templates | X | ||
| PM Forecasting | X | ||
| Automation Scripts | X |
However, this list is not complete. IBM has published tons of great documentation but sometimes can be difficult to understand when a feature has been introduced and if it is available in a specific version of Maximo. That's why I have spent some time today to merge the new features introduced in Maximo 7.1 and 7.5 in a single list. This list also includes smaller features introduced in fixpacks.
I have tried as much as possible to summarize the features description so if you want more details you can refer to the official documentation.
Maximo 7.1
| Feature | Description |
| Multiple Assets and Locations on Work Orders | Work orders can be linked to multiple assets, locations, and CIs. |
| Enhanced Swap capabilities | Plan asset swaps in Work Order Tracking application. Upon completion of the work order, the Asset move transactions are automatically recorded. |
| Configuration Item functionality | |
| Automated Flow Control | Define precedence connections between work orders and tasks. This then initiates the resulting network of records automatically having a finish-to-start action applied to them, thus automating the flow of status changes between them. |
| Activities and Tasks Application | A new Task application is available that is a subset of Work Order Tracking functionality to support the single task specific use case. |
| Attached Documents at task level | The standard functional capability to attach documents is available on work order tasks and job plan tasks. |
| Nested Job Plans | This functionality will allow Job Plans to be nested within a hierarchical relationship. |
| Classification-based attributes | Work Order Classifications supports the Attributes and all of the standard functionality that comes with this feature (the same as Assets, Locations and Items). |
| Classification Enhancements | Several enhancements to the Classifications application. |
| Job Plan Template | Job Plan application includes a the Job Plan Template field that allows to categorize job plans: Maintenance, Activity, Process. |
| Task and Work Order Ownership | Ownership concept is extended to work order tasks and job plan tasks. |
| Future dates tolerance | Configurable tolerance for closing work orders with labor reported in the future. |
| Route Enhancements | Improved Route application to support |
| Assets application enhancements | Directly report asset downtime. Edit asset downtime history. Assets Collections. Issue items directly to an asset. |
| Item status | Items are stateful to track and manage the lifecycle of items from creation to obsolescence.. |
| Item images | The Item Master, Tools and Service Items applications all support the ability to associate images with their main records. |
| Work management status change flow control | An embedded status change workflow has been added to the work order applications. Precedence relationships can be defined between work orders, activities and tasks. Flow control can then be optionally set in either the job plan or work order applications to govern the status change rules in a hierarchy and/or network of records. |
| Extended attributes with Service Requests | Use of extended attributes with the Self Service Applications. |
| Quick Insert | Quick Insert functionality enables the rapid creation of SRs, Incidents and Problems by referencing a ticket template along with the quick insert action. |
| Bulletin Board enhancements | Hide viewed messages. Send Email from a Bulletin Board message. |
| New Create Ticket and Work Order actions | Create Ticket and Work Order Actions added to Assets, Locations, and Configuration Item Applications |
| Communications Log enhancement | Communications Log enhancement to allow for the capture of escalation and workflow driven communications |
| Enhanced assign ownership actions | Enhanced filtering capabilities to make it easier to select the appropriate owner for a ticket or work order. |
| Enhanced Related Record functionality | Added ability to create related records from additional dialogs. |
| Global Ticket Management enhancements | |
| Classification description field lookup | Classification description field is now a lookup to return all classifications that contain the description entered in the field. |
| Ticket enhancement | The list page within all of the ticket applications now includes the ability to change status or ownership for a group of selected records. |
| Solution Exposure in the View Service Request Application | |
| System Properties | System Properties application to manage system-wide properties. |
| Logging | This is a dedicated application to manage system logging and tracing. |
| Migration Manager | Migration Manager is a dedicated tool to promote Maximo configurations from pre-production to production environments. |
| Enhanced User Interface | Accessibility and efficiency enhancements. |
| Conditional Expression Manager | Conditional Expression Manager application allows to define conditions, either as expressions or as custom class files that can be used to drive application behavior. Conditions within the library can be used for conditional option access, data restrictions and conditional UI. |
| Conditional Option Access | It is possible to tie a condition to a security groups̢۪ access to an application option. Conditional access is granted in the security groups application. |
| Data Restrictions | An object or an attribute can be made hidden or read-only either conditionally or unconditionally for the entire system or for a security group. |
| Conditional User Interface | Possibility to bind UI controls to a Sig Option and thereby grant or revoke it to groups of users. Also properties of a control (label, color, value list, etc.) can be tailored for specified groups of users either conditionally or unconditionally. |
| Integration Framework | |
| LDAP | Predefined LDAP integrations to both Microsoft Active Directory and IBM Directory Server. Security groups and user/group management can be performed in Maximo rather than in the directory. |
| Reporting | BIRT is now the embedded technology for reporting. Other reporting options are: Cognos, Business Objects/Crystal, External Report Integration, Open Database Integration. |
| Upgrade Utility | The 7.1 upgrade utility has streamlined upgrade workflow by integrating the database and screen upgrade functions into a single utility. |
| Application Designer | Several improvements to the Application Designer application. |
| Email Listener | Email Listener can process both formatted and non-formatted emails. |
| Manage Sessions | Enhancements to tracking user session information and login history information. |
| Data Import | Data loading functionality within the External Systems application, using theImport Data action. |
Maximo 7.1 fixpacks
| Release | Feature | Description |
| 7.1.1.5 | BIRT Reporting | BIRT reporting is upgraded from BIRT 2.1.2 to 2.3.2. |
| 7.1.1.5 | Monitoring Agent for Maximo feature pack | Allows to monitor Maximo infrastructure and applications using IBM Tivoli Monitoring. |
| 7.1.1.5 | Query-based reporting | Query-based, or ad hoc, reporting is expanded to include the creation of detail reports, user-defined parameters, public security access, and multiple report object structures. |
| 7.1.1.6 | Cognos Business Intelligence reporting | To support the open reporting architecture, a new integration to the Cognos Business Intelligence reporting products is included. |
| 7.1.1.7 | Support added for Internet Explorer 8 | "Runs on" support has been added for Windows Internet Explorer 8 on Windows 7. |
| 7.1.1.7 | Support added for DB2 9.7 | "Runs on" support has been added for DB2 9.7. |
| 7.1.1.7 | Turkish translations | |
| 7.1.1.9 | Upgrade checkpoint restart | The updatedb utility was enhanced to restart from the point of failure rather than completely restarting from the beginning. |
| 7.1.1.9 | Office 2010 certification | New Microsoft Office (docx, xlsx, etc.) formats are officially supported. |
| 7.1.1.10 | Upgrade checkpoint restart | The updatedb keeps track of the last database update statement successfully performed. |
Maximo 7.5
| Feature | Description |
| Upgrade checkpoint restart | The UPDATEDB tool completes database tasks during the upgrade process and tracks the last database update statement that succeeds. |
| Installation | Multiple Maximo environments can be installed on one administrative machine with the Maximo 7.5 installer (TechNote) . |
| Taxes | You can configure the system for work orders, job plans, and to enable a tax-exempt status at vendor or organization level. |
| Autofill | Configure autofill properties so that fields are automatically filled with cached data. |
| Application design | Merge the data in three columns that show classification attributes and their values. |
| Application restrictions | You add a query to an application to restrict the records that a user can see. |
| Security | You can manage failed logins, forgotten password attempts, and self-registration attempts. |
| Automation scripting | Scripting allows to extend and customize business logic without need to develop Java code. Rhino, Jython and other JSR223 compliant languages can be used. |
| Migration Manager | Migration collections. Compare source and target databases. Deployment preview. More flexible version compatibility checking. Many others. |
| Accessibility | |
| Usability | Rich text editing for long descriptions. Asynchronous field validation. The new calendar control. The filter that you set for records on the List tab of an application is maintained when you view multiple tabs during the same user session. Different text styles indicate whether a record was changed since the filter was applied. |
| Reporting | Several improvements to reporting infrastructure. |
| Consignment invoices | Consignment payment invoices can be generated, either manually or automatically, for financial transactions that occur when consignment items are used. |
| Purchase order revisions | |
| Receipt and invoice processing | |
| Contract revisions | |
| Tax code calculations | |
| Related records | |
| Commodity association | |
| Inventory Usage application | The new Inventory Usage application streamlines the issue and transfer process. Costing methods are also improved. |
| Item issues and transfers | Create inventory usage records to track the issue, transfer, and return of inventory items within and across organizations. Monitor the balances of inventory items and tools in storerooms and bins. Transfer inventory items or tools between storerooms within an organization by creating shipment records or purchase orders. Enter multiple shipping addresses and multiple billing addresses for the sites in an organization. |
| Inventory costing | Specify the issue cost type that is associated with an item when you add items to a storeroom, such as last-in first-out (LIFO) and first-in first-out (FIFO) cost types. Apply last-in first-out (LIFO) and first-in first-out (FIFO) costing methods to inventory records. Include selected items as part of the consignment inventory, so that they are paid for only when they are used. |
| Item ordering | Specify the percentage of items that can be received over the amount that is ordered in the initial agreement. Specify the stock category for an item to identify stocked items, non-stocked items, and special order items. |
| Soft reservations | Create hard reservations or soft reservations of inventory items and tools, based on the availability of the inventory requirement (see TechNote). |
| Asset templates | Use asset templates to create or update multiple assets. |
| Return rotating assets and direct issue items to vendors. | |
| Preventive maintenance forecast | Generate forecasts for preventive maintenance records on the Forecast tab. Forecasts are based on the frequency criteria that you specify and on seasonal information. |
| Track owner groups by specifying assigned owner groups in preventive maintenance records. Specify active dates and expiration dates for general ledger accounts. | |
| Work order tracking | View the internal and external labor costs that are associated with work orders and work packages. Monitor whether the actual costs for work orders and work packages exceeded the planned costs. Specify whether to ignore the availability of storeroom materials and direct issues for work orders. View the current direct issue material status and the current storeroom material status for a work order. Add multiple address tax codes to a work order record to facilitate tax calculation. |
| Job plan management | Track owner groups by specifying assigned owner groups in job plan records. Specify that nested job plans are processed in the background when job plans are applied to work order type records. |
| Escalations | Include calendars and shifts in the calculation of escalation points. |
| Service groups | Service groups for tickets, work orders, contracts, assets, locations. |
| Integration | REST APIs. Messages in text format. Enable exporting and importing of data from any application. Child objects event propagation. Processing of integration messages can follow the authorization configuration that is established for an application and user group. Deployment of web services is expanded to support the use of the application server container. Bidirectional languages. |
Maximo 7.5 fixpacks
| Release | Feature | Description |
| 7.5.0.1 | DB2 full text search | |
| 7.5.0.2 | Default Application | Default application for user profiles and Security Groups. |
| 7.5.0.2 | Support for WAS 8 | |
| 7.5.0.3 | High availability configuration | Configuration of the environment to provide high availability of your system and data. |
| 7.5.0.3 | Email interaction | |
| 7.5.0.3 | Object duplication configuration | You can now exclude user-defined attributes that should not be copied to the new object. |
| 7.5.0.3 | Flow control status inheritance | You can set a system property to allow status inheritance for work items that are under process flow control. |
| 7.5.0.3 | Job plan condition | You can create conditions and apply them to job plans to specify that work can begin only when certain conditions are satisfied. |
| 7.5.0.3 | OSLC integration | |
| 7.5.0.3 | Last memo in communication template | You can add the last memo from the most recent workflow assignment action to a communication template. |
| 7.5.0.3 | Data filters in application | You add the allowqualifiedrestriction property to the XML for an application to restrict the data that is returned from the database. |
| 7.5.0.3 | Support for BIRT 3.7.1 | |
| 7.5.0.3 | Support for Cognos 10.1.1 | |
| 7.5.0.5 | Cross-site scripting and SQL injection filter | You can enable a filter that protects the product from cross-site scripting and SQL injection attacks (link). |
| 7.5.0.5 | Runs On Support for WAS 8.5.5 | This fix pack supports WebSphere 8 servers. Once the installation completes successfully on WebSphere 7, you can upgrade to WebSphere 8. |
| 7.5.0.5 | OSLC | Enhancements to Open Services for Lifecycle Collaboration (OSLC) capabilities. |
| 7.5.0.7 | Result Set related records | A new enhancement was added to allow you to view information that is related to the main record of the result set. For example, you can now display the first and last name of the owner of an incident, instead of only the UserID. |
Source:http://maximodev.blogspot.com/2013/11/maximo-7.1-7.5-features-history-comparison.html
Tidak ada komentar:
Posting Komentar