© 2013 IBM Corporation IBM Predictive Maintenance & Quality Orchestration BA Technical Seller Training 1

© 2013 IBM Corporation 2 Agenda  Overview of orchestration  Deciding when to trigger scoring  Preparing the input  Intgegaion Flow  Perform Scoring  Decision Management  Calling Maximo

© 2013 IBM Corporation 3 Orchestration Overview  Orchestration is the process that ties recommendation activities in IBM PMQ together  Orchestration is achieved with message flows in Message Broker  Following activities are tied together in PMQ Preparing data for predictive models Running predictive models Feeding predictive results back to PMQ as events Calling external systems with recommendations

© 2013 IBM Corporation 4 Should Scoring and Recommending Occur?  At the end of event processing (after aggregation)  Determine if scoring and decision management should occur  For example:  This decision is made at the level of the event (not event observation)

© 2013 IBM Corporation 5 Property to Prevent Calling to SPSS  Can be set in the Message Broker Explorer

© 2013 IBM Corporation 6 Prepare Required Data  Generally the input required for predictive scoring will be available from profile variables  Some predictive modes may also require input from the event or from KPIs  Retrieving this data requires selecting it as required  The input data must be assembled into a message structure that will be processed to create a call to SPSS  For example:

© 2013 IBM Corporation 7 Prepare Required Data  The defined data structure includes an indication that a scoring model should be called, decision management should, or both 

© 2013 IBM Corporation 8 Data Preparation for SPSS  Health Score Model Aggregated data in RESOURCE_KPI acts as input for health score model SPSS needs data from RESOURCE_KPI for 3 profile calculations Measurement of Type Measurement Above Limit Measurement Below Limit  Life Span Model Aggregated data in RESOURCE_PROFILE acts as input for life span analysis model SPSS needs data from RESOURCE_PROFILE for Life Span Analysis profile calculation

© 2013 IBM Corporation 9 Pass Message to PMQ Integration Flow  Assembled data is placed on a queue for the next step of orchestration  The arrival of this message on the queue causes the integration flow to remove it from the queue and start processing

© 2013 IBM Corporation 10 Message Flow Required Input  The Build Request node receives the required input  The input is assembled into the format required to call the SPSS web service

© 2013 IBM Corporation 11 Message Flow to Call to SPSS Service  Call SPSS Scoring and Decision Management  Generate internal events to record results  Create a workorder in Maximo if recommended to do so

© 2013 IBM Corporation 12 Calling SPSS Scoring and Decision Management  The build request node emits multiple request messages  One message for each score and decision request  For the PMQ sample, this is two scoring and one decision request

© 2013 IBM Corporation 13 SPSS Scoring Service Location  The URL defining the name and location of the SPSS scoring service is set as a property of the web service request node

© 2013 IBM Corporation 14 Security  The security credentials for the SPSS service are included as part of the message supplied to the web service node  These credential are read from the file /restricted/credentials.properties

© 2013 IBM Corporation 15 Recording of Scores and Recommendations  Scores and Recommendations are recorded into the analytic data store  This is performed using the same mechanism as the recoding of event observation values  An internal event is created with scores and recommendations as observations that have an associated measurement type  Profile variables are defined to perform aggregation

© 2013 IBM Corporation 16 Internal Event Content Event observation with measurement type as HS, event type as RECOMMENDED, health score as the measurement value and recommendation as the observation text Event with measurement type as LSC, event type as RECOMMENDED, life span score as the measurement value and recommendation as the observation text

© 2013 IBM Corporation 17 Aggregation of Scores and Recommendations  Scores are Recommendations are recorded and aggregated in the same way as events  The aggregation of scores and recommendations using profile variables makes them available for reporting along with event data

© 2013 IBM Corporation 18 Internal Event Processing Flow – Scores and Recommendations  Processing of internally of events  Internal event processing is managed by measurement types and profile variables

© 2013 IBM Corporation 19 Metadata driven Event Aggregation – Measurement Types  Each observation is associated with a measurement type  This measurement type determines how the PMQ solution interprets the observation  The sample data includes a set of measurement types

© 2013 IBM Corporation 20 Metadata Driven Event Aggregation – Profile Variables  A profile variable specifies a specific calculation to perform on a measurement type  This calculation performs an aggregation  The sample data includes a set of profile variables

© 2013 IBM Corporation 21 Performing SPSS Scoring and Decision Management  Errors calling the SPSS web service  Errors saving the score and recommendation using an internal event  Errors preparing the data for work order creation  Error file is /error/IntegrationError.txt  Error queue is PMQ.INTEGRATION.ERROR

© 2013 IBM Corporation 22 Common Problems Calling SPSS  SPSS service not running  Incorrect username or password  Incorrect service name  Incorrect data input

© 2013 IBM Corporation 23 Example of an Error File From Calling SPSS  Web service URL should indicate the SPSS node

© 2013 IBM Corporation 24 Example of an Error File From Calling SPSS  Details from error queue PMQ.INTEGRATION.ERROR

© 2013 IBM Corporation 25 What caused this problem in PMQIntegration?  Unable to access the SPSS web service on the network

© 2013 IBM Corporation 26 SPSS Web Service Resources  Infocenter

© 2013 IBM Corporation 27