New Import/Export Features in Maximo 7.5

Transcription

1 value focused. results driven. New Import/Export Features in Maximo 7.5 By Paul Hoang Feb 15, 2013

2 Agenda New Features Overview Business Benefits Pros and Cons Application Import/Export Migration Collection Deployment Management Demonstration Questions

3 New Features Overview 1 Application Import / Export 2 Migration Collection 3 Deployment Management Value Replacement / Error Correction Compatibility 3 Usability

4 Business Benefits 1 Quicker data entry 2 More efficient assembly of components 3 More streamlined deployment

5 Pros and Cons Pros Cons Application Import / Export Quick for large # of data Security concern Operator knowledge Migration Collection / Comparison Faster, easier to gather components Need management for higher volume Simple way to identify changes Time and resource consuming Replacement / Error Correction Quick fix Additional traceability Need to turn off after use Limited to SET Usability Fewer steps More traceability Enhanced obj. structure

6 Application Import/Export Uses Integration Framework to directly import or export data from application (such as Assets, Job Plan, Work Order, etc.) Format: Flat File, XML Example: Source (multilingual) Target (unilingual)

7 Application Import/Export setup Object Structure (e.g. MXAssets) Check Support Flat Structure if use flat file Select Action > Add/Modify Application Export (or Import) Add application(s) Set XML or Flat File Set number of rows (high number decreases system performance) Security Group grant access to: Application Import and Export

8 Application Import/Export setup con t

9 Grant Access in Security Group

10 Application Usage Property Name Description Current Value mxe.dm.previewfreememorythreshold Memory threshold in percentage for preview operation to stop 20

11 Migration Collections Collection = configuration or group of configurations E.g. workflow processes, escalation, domain, pm Collection Application Similar to Application Import/Export Manually select records from the application instead of using Where Clause on the MM Group. Collection can be built within Collection Application or within the actual application itself.

12 Source Target Collection Process Migration Collection Migrated Collection Create Collect Compare Validate Define Create.zip file Replacement Rule Deploy Distribute Preview

13 Adding Collection Function to Application

14 Application Adds Collection icon Available on both List tab and inside the record If use on List tab then all display records will be added to the collection

15 Import collection objects

16 Find other related objects Property Name Description Current Value mxe.dm.collvalidlevels Maximum number of levels searched to find related records. 5

17 Select related objects for inclusion Need user intervention

18 Bring related objects into Collections

19 Use Collections MM for large sets Select Action > Create Page Definition Go to Migration Manager, then go through MM route Approve migration package, Create, Distribute, Download. Deploy on Target

20 Replacement Rule during import Limited rule available (currently SET) Apply to all import until turn off

21 Replacement Attribute/Condition

22 Edit error data on the fly

23 Compare Current Migration package

24 Import package from different source As long as same base level No longer need matching: DB (Oracle, SQL, DB2) Maximo Package (e.g. Oil & Gas, Linear Asset, etc.) Patch

25 Warning message when deploy

26 Usability Enhancement Can set status=appr at package creation Snapshot package no longer need activation New object structures: DMMaxObjectCfg support different target db DMQuery DMInteraction, DMWSRegistry to support web service migration DMScript and DMLaunchPoint

27 Maximo Properties Property Name Description Current Value mxe.dm.autoapprovepkgdef Migration Manager Auto Approval of Package 0 Definitions. mxe.dm.collvalidlevels Maximum number of levels searched to find 5 related records. mxe.dm.collvalidsrcexclude Specify source object, attribute and value combinations that should be not be traversed from. mxe.dm.collvalidtgtexclude Specify target object and attribute combinations that should not be traversed to during validation. mxe.dm.continueonerror Continue Migration Manager deploy 0 mxe.dm.importlimit Collection Import Limit 100 <MAXINTOBJCOLS> <MAXINTOBJALIAS> MAXINTOBJECT.USEWITH, MAXRELATIONSHIP.CARDINALITY, CRONTASKINSTANCE.SCHEDULE

28 Demo Let me show you

29 Question

30 Thank you for attending our webcast. If you have any questions regarding the content of this webcast, or for additional information contact the presenter, Paul Hoang at: Phone:

31 Thank You! value focused. results driven.