Introducing Maximo Calibration on Maximo Anywhere. Sandra Gannon & Marcelo Esperandio

Transcription

1 Introducing Maximo Calibration on Maximo Anywhere Sandra Gannon & Marcelo Esperandio

2 Please Note: IBM s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM s sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion. Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user s job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here. 2

3 What is calibration? A technique that compares instrument performance to a standard of known accuracy. Improper calibration of tools, equipment or standards can lead to errors that diminish efficiency, compromise product quality, damage plant assets, increase operational costs and reduce profits. Calibration on Work Execution enables technicians to perform mobile calibration using tablets to streamline work tasks.

4 Benefits of Maximo Calibration on Maximo Anywhere Simplifies and expedites calibration work execution Designed for the tablet user Extension to the Work Execution application; not a stand alone application Validation is done on the device: suitable for disconnected work

5 Scenarios covered 1. Completing data sheets for analog or discrete devices 2. Completing data sheets with function checks 3. Completing data sheets with dynamic checks 4. Inserting calibration points, function checks, and dynamic checks 5. Completing a looped calibration work order 6. Copying valid 'as found' readings to 'as left' fields 7. Validating tools

6 Overview Calibration work orders are downloaded to tablet devices and calibration technicians can scroll through all the Calibration work orders. Calibration-specific fields are displayed to provide calibration-specific information to the technician.

7

8

9

10

11

12 Scenario 1 A c a libra tion tec hnic ia n c a n c omplete a da ta s he et for a n a na log or a dis c rete devic e

13

14

15

16

17

18

19

20

21

22

23

24 Analog device An analog device is an instrument that provides continuous results, such as a pressure gauge. It includes non-linear instruments. In the Work Order details view on calibration work orders, the data sheets associated with the work order are available. From the data sheets, the users can enter in the As Found and As Left values for the instruments The Data Sheet functionality displays the information in the same UI flow as the Work Execution application. The validation is performed on the device which is much more responsive than Maximo. The following types of tolerance calculations are possible: EU %Reading %Span %URV Summed tolerances Opposite single and summed Square root single and summed Reverse flow single and summed

25 Discrete device A discrete device is an instrument that only has two settings. For example: A switch that is either on or off A valve that is either open or closed The same tolerance calculations that are done in Maximo are possible: EU %Reading

26 Scenario 2 A c a libra tion tec hnic ia n c a n c omplete a da ta s he et w ith a func tion c hec k

27

28

29

30

31

32

33

34 Function check A function check is an additional check point that is required to calibrate an instrument. The options for a functional check are either pass or fail. For example, a functional check can record a temperature setting that contributes to either a pass or fail. There is a simple check box to indicate pass or fail.

35 Scenario 3 A c a libra tion tec hnic ia n c a n c omplete a da ta s he et w ith a dyna mic c he c k

36

37

38

39

40

41

42

43 Dynamic check A dynamic check is additional data about the instrument being calibrated. A dynamic check point does not affect the calibration of an instrument, but is relevant to the calibration of an instrument. For example, a dynamic check can record the reading of gear settings or controller tuning of an instrument. The user has the ability to enter values and select measurement units from a list.

44 Scenario 4 A c a libra tion tec hnic ia n c a n ins e rt a c a libra tion point, func tion c he c k, a nd dyna mic c he c k

45

46

47

48

49

50

51

52

53 Inserting points and checks A technician may discover that the data sheet does not cover enough of a range to enable a comprehensive calibration reading and so might enter extra calibration points. This follows the same logic as the Calibration application in Maximo. This functionality is only enabled the Technician Can Insert Points option is allowed for the specific asset function. If the asset function is analog, the Nominal Input and the Desired Output values are editable. Units are read-only and are determined from the asset function. If the asset function is discrete, then only the Set Point and the Switch Action values are editable. The unit is determined from the asset function. The calibration point can be added from the As Found view The Input/Output and Set Point values are editable based on whether the asset function type is analog or discrete. The validation is the same as for the Work Order Tracking application.

54 Scenario 5 A c a libra tion tec hnic ia n c a n perform a looped c a libra tion

55

56

57

58

59

60

61

62 Looped calibration A loop is a set of instruments that are grouped and calibrated together. The input and output of the entire group determines whether the calibration is successful. This follows the same logic as the Calibration application in Maximo. If a data sheet, which is part of a loop calibration, is marked as required, then all data on that data sheet is required. This data includes all asset functions for calibration points, function checks, or dynamic checks.

63 Scenario 6 A c a libra tion tec hnic ia n c a n c opy va lid As F ound readings to As L eft fie lds

64

65

66

67

68

69

70

71 Copying As Found values to As Left fields Data entry, particularly when there are many calibration points, can become tedious due to the need to capture both 'as found' and 'as left' readings. If the organization permits, when the 'as found' readings pass, the user can copy as found points and statues to the 'as left' fields. If the 'as found' readings pass, the user can select the No Adjustment Made check box to copy the status and readings over to the 'as left' fields.

72 Scenario 7 A c a libra tion tec hnic ia n c a n only c omplete a c a libra tion w ork orde r w ith a va lid tool

73

74

75

76

77

78

79

80

81

82

83

84

85 Completing calibration work orders with valid tools You can ensure that a calibration work order is only completed when a validated tool is entered and that the technician is qualified to use the tool. Calibration fields were added to the Actual Tools view. You can include date/time picker for fields, as required. We implemented the MAXVAR PLUSCPASTDUEVAL logic. This MAXVAR determines if the tool is past due. Depending on the maxvar setting, when you select a tool that is past due, the application prevents a past due tool from being entered or allows you to add the tool without any warning message. We implemented the MAXVAR PLUSQUALTECH logic. This MAXVAR determines if the technician is qualified to use the tool. Depending on the setting, an unqualified technician can be specified but a warning message is displayed, you are prevented from specifying an unqualified technician, or no validation is performed between the technician and the tool. We implemented the MAXVAR.PLISCVALTOOL logic. This MAXVAR determines whether you can set the status of a Work Order Tracking to CLOSED or COMP without specifying an actual tool. Depending on the settings, there is no validation between the tool and the status of the work order, validation occurs but a warning message is displayed, or validation occurs and the relationship between a tool being added and setting the status the work order to CLOSED or COMP is enforced. If it's a buffer solution logic, certain fields become required.

86 Notices and Disclaimers Copyright 2016 by International Business Machines Corporation (IBM). No part of this document may be reproduced or transmitted in any form without written permission from IBM. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM. Information in these presentations (including information relating to products that have not yet been announced by IBM) has been reviewed for accuracy as of the date of initial publication and could include unintentional technical or typographical errors. IBM shall have no responsibility to update this information. THIS DOCUMENT IS DISTRIBUTED "AS IS" WITHOUT ANY WARRANTY, EITHER EXPRESS OR IMPLIED. IN NO EVENT SHALL IBM BE LIABLE FOR ANY DAMAGE ARISING FROM THE USE OF THIS INFORMATION, INCLUDING BUT NOT LIMITED TO, LOSS OF DATA, BUSINESS INTERRUPTION, LOSS OF PROFIT OR LOSS OF OPPORTUNITY. IBM products and services are warranted according to the terms and conditions of the agreements under which they are provided. Any statements regarding IBM's future direction, intent or product plans are subject to change or withdrawal without notice. Performance data contained herein was generally obtained in a controlled, isolated environments. Customer examples are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual performance, cost, savings or other results in other operating environments may vary. References in this document to IBM products, programs, or services does not imply that IBM intends to make such products, programs or services available in all countries in which IBM operates or does business. Workshops, sessions and associated materials may have been prepared by independent session speakers, and do not necessarily reflect the views of IBM. All materials and discussions are provided for informational purposes only, and are neither intended to, nor shall constitute legal or other guidance or advice to any individual participant or their specific situation. It is the customer s responsibility to insure its own compliance with legal requirements and to obtain advice of competent legal counsel as to the identification and interpretation of any relevant laws and regulatory requirements that may affect the customer s business and any actions the customer may need to take to comply with such laws. IBM does not provide legal advice or represent or warrant that its services or products will ensure that the customer is in compliance with any law 86

87 Notices and Disclaimers Con t. Information concerning non-ibm products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products in connection with this publication and cannot confirm the accuracy of performance, compatibility or any other claims related to non-ibm products. Questions on the capabilities of non-ibm products should be addressed to the suppliers of those products. IBM does not warrant the quality of any third-party products, or the ability of any such third-party products to interoperate with IBM s products. IBM EXPRESSLY DISCLAIMS ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. The provision of the information contained h erein is not intended to, and does not, grant any right or license under any IBM patents, copyrights, trademarks or other intellectual property right. IBM, the IBM logo, ibm.com, Aspera, Bluemix, Blueworks Live, CICS, Clearcase, Cognos, DOORS, Emptoris, Enterprise Document Management System, FASP, FileNet, Global Business Services, Global Technology Services, IBM ExperienceOne, IBM SmartCloud, IBM Social Business, Information on Demand, ILOG, Maximo, MQIntegrator, MQSeries, Netcool, OMEGAMON, OpenPower, PureAnalytics, PureApplication, purecluster, PureCoverage, PureData, PureExperience, PureFlex, purequery, purescale, PureSystems, QRadar, Rational, Rhapsody, Smarter Commerce, SoDA, SPSS, Sterling Commerce, StoredIQ, Tealeaf, Tivoli, Trusteer, Unica, urban{code}, Watson, WebSphere, Worklight, X-Force and System z Z/OS, are trademarks of International Business Machines Corporation, registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at: 87

88 Thank You Your Feedback is Important! Access the InterConnect 2016 Conference Attendee Portal to complete your session surveys from your smartphone, laptop or conference kiosk.