System Information
App

Server IBM WebSphere Application Server 9.0.0.7
Version

• Tivoli's process automation engine 7.6.1.1-IFIX20200324-1612 Build 20190514-1348 DB Build V7611-365 HFDB Build HF7611-06
• IBM Maximo Asset Management Scheduler 7.6.7.3 Build 20190514-1348 DB Build V7673-78 HFDB Build HF7673-11
• IBM Maximo Asset Management 7.6.1.1 Build 20190514-1348 DB Build V7611-01
• Server OS Windows Server 2016 10.0
• Server DB Microsoft SQL Server 13.0 (13.00.5820)

ODME

• 3.9 FixPack 2

------------------------------------------------------------------

So I need any guidance as we're getting issues or more precisely inconsistencies when we sent a Graphical Scheduler one of my scenarios to sent to be optimized and we're getting Failed to Solve, yet I have another one the solves.  This is so variable and we're not getting enough info from the WAS logs.

I'm looking for advice on what can I turn on, look it or hit with a hammer to get why it fails to solves for one, but not another.

Message BTW in the Optimizer console for the failed one is CIVOO2477E: Unrecoverable Solve Failure in during the solve java.lang.RuntimeException: CIVOO0040E: Task execution reported a failure at ilog.odm.processingsvc.impl.I.....

Hi Craig, hope you are fine.

So, my first advice on the version you are would be if possible move to the latest IFIX of TPAE 7.6.1.1, IFIX 12 version is planned to be released end of this week. On the Scheduler 7.6.7 with Decision Optimization Server product as you are 90% of the problems are related to the Data like Calendar (Shift and Work Period), Duration (Work Order and Task duration), Dates (Scheduler dates or Constraints outside of the range), missing resources (Craft are not associate with Labor/Crew) and some other facts that we advise you to collect the Data file that can be found inside of the WebSphere.

Example: C:\ibm\WebSphere\AppServer\profiles\ctgAppSrv01\temp\ctgNode01\MXServer\MAXIMO\maximouiweb.war\optimization\debug inside that folder all the data you send to optimization per scenario will be located and we can understand what is happening. This file contains all the Work that you are sending, Calendar information, Resource information, and Constraints. Based on what you describe I understand that in this scenario something is conflicting on those data.

At the New Scheduler 7.6.8 with Scheduler Optimization 7.6.8 we are able to expose those issues at the Maximo UI and save the time of debugging. And at the Scheduler Optimization console the data file, debug, and the Logs are already available on the UI.

Please, open a Case so we will be able to analyze the data and back to you with a resolution, when a problem happens at the Model side, 10%, then the ODME logs (Systemout) will be important to analyze what happened during a solution process. if possible to include those will be nice to save time.

Thanks and I wish you an Happy New Year.

System Information
App

Server IBM WebSphere Application Server 9.0.0.7
Version

• Tivoli's process automation engine 7.6.1.1-IFIX20200324-1612 Build 20190514-1348 DB Build V7611-365 HFDB Build HF7611-06
• IBM Maximo Asset Management Scheduler 7.6.7.3 Build 20190514-1348 DB Build V7673-78 HFDB Build HF7673-11
• IBM Maximo Asset Management 7.6.1.1 Build 20190514-1348 DB Build V7611-01
• Server OS Windows Server 2016 10.0
• Server DB Microsoft SQL Server 13.0 (13.00.5820)

ODME

• 3.9 FixPack 2

------------------------------------------------------------------

So I need any guidance as we're getting issues or more precisely inconsistencies when we sent a Graphical Scheduler one of my scenarios to sent to be optimized and we're getting Failed to Solve, yet I have another one the solves.  This is so variable and we're not getting enough info from the WAS logs.

I'm looking for advice on what can I turn on, look it or hit with a hammer to get why it fails to solves for one, but not another.

Message BTW in the Optimizer console for the failed one is CIVOO2477E: Unrecoverable Solve Failure in during the solve java.lang.RuntimeException: CIVOO0040E: Task execution reported a failure at ilog.odm.processingsvc.impl.I.....

Hi Pedro

We've done the review of the logs and on the whole they do appear consistent and full.  I've attached one successful and one failed.  More will be on the Case TS004725894.

The Maximo and Scheduler have only just been upgraded, so it'll be a while before upgrading again due to the need to be on Maximo 7.6.1.2 to take advantage of Maximo Scheduler 7.6.8 and the new optimizer.

Hi Craig, hope you are fine.

So, my first advice on the version you are would be if possible move to the latest IFIX of TPAE 7.6.1.1, IFIX 12 version is planned to be released end of this week. On the Scheduler 7.6.7 with Decision Optimization Server product as you are 90% of the problems are related to the Data like Calendar (Shift and Work Period), Duration (Work Order and Task duration), Dates (Scheduler dates or Constraints outside of the range), missing resources (Craft are not associate with Labor/Crew) and some other facts that we advise you to collect the Data file that can be found inside of the WebSphere.

Example: C:\ibm\WebSphere\AppServer\profiles\ctgAppSrv01\temp\ctgNode01\MXServer\MAXIMO\maximouiweb.war\optimization\debug inside that folder all the data you send to optimization per scenario will be located and we can understand what is happening. This file contains all the Work that you are sending, Calendar information, Resource information, and Constraints. Based on what you describe I understand that in this scenario something is conflicting on those data.

At the New Scheduler 7.6.8 with Scheduler Optimization 7.6.8 we are able to expose those issues at the Maximo UI and save the time of debugging. And at the Scheduler Optimization console the data file, debug, and the Logs are already available on the UI.

Please, open a Case so we will be able to analyze the data and back to you with a resolution, when a problem happens at the Model side, 10%, then the ODME logs (Systemout) will be important to analyze what happened during a solution process. if possible to include those will be nice to save time.

Thanks and I wish you an Happy New Year.

System Information
App

Server IBM WebSphere Application Server 9.0.0.7
Version

• Tivoli's process automation engine 7.6.1.1-IFIX20200324-1612 Build 20190514-1348 DB Build V7611-365 HFDB Build HF7611-06
• IBM Maximo Asset Management Scheduler 7.6.7.3 Build 20190514-1348 DB Build V7673-78 HFDB Build HF7673-11
• IBM Maximo Asset Management 7.6.1.1 Build 20190514-1348 DB Build V7611-01
• Server OS Windows Server 2016 10.0
• Server DB Microsoft SQL Server 13.0 (13.00.5820)

ODME

• 3.9 FixPack 2

------------------------------------------------------------------

So I need any guidance as we're getting issues or more precisely inconsistencies when we sent a Graphical Scheduler one of my scenarios to sent to be optimized and we're getting Failed to Solve, yet I have another one the solves.  This is so variable and we're not getting enough info from the WAS logs.

I'm looking for advice on what can I turn on, look it or hit with a hammer to get why it fails to solves for one, but not another.

Message BTW in the Optimizer console for the failed one is CIVOO2477E: Unrecoverable Solve Failure in during the solve java.lang.RuntimeException: CIVOO0040E: Task execution reported a failure at ilog.odm.processingsvc.impl.I.....