Skip to Main Content
IBM Sustainability Software - Ideas Portal


This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Is a defect
Created by Guest
Created on Jul 16, 2020

Inspection form creates 2 forms per Work Order

I have this screen of 26 inspections, this is just me testing and on those 26, 13 are absolutely useless to the end user as they are a double occurrence of another.

Now here is what happen in the real life of a train maintenance site; for Eglinton site only, I have 75 vehicle that need a daily inspection, so it mean each day I will end up with 150 inspections for and each day 75 will just be a useless copy of another. Technically it does not change anything as results are the same on both, but in the daily reality of a site, it is a bloody mess when you look for the inspection sheet you need to use, even more when you have twice what you should have.

And don't get me wrong, I know we are IT guy's and it seem obvious to use the search and find what we look for, but if you put yourself in the boots of a train mechanic which computer is not the daily bread then it is a very different perspective.

So this being said, if you confirm this is as designed and not a bug , I will say it is badly designed and ask you if there is any options to report this with IBM support

Idea priority Medium
  • Guest
    Reply
    |
    Mar 27, 2023

    The extra InspectionResult exists by design. I agree it was not a great design and the developers realized it and have improved upon it to some extent.


    The extra InspectionResult record which has ReferenceObject = PARENTWO (vs. WORKORDER or WOACTIVITY) was intended to support "Batch" Inspections. The concept of "Batch" Inspections is very useful when you're associating Inspection Forms with the rows in the "Multiple Assets, Locations, and CIs" table and allows the user to select the PARENTWO record for the "Batch" Inspection and have it bring up all the individual Inspections by Sequence #.


    If you don't plan to use the "Batch" feature, you can turn off the creation of the PARENTWO records changing the value of the mxe.app.workorder.InspectionBatchRecord System Property to "0".


    If you do want to use the "Batch" feature, you can modify the OSLC Queries used by the "Conduct an Inspection" app to ignore InspectionResult records where "Parent IS NOT NULL".


    Word of warning, since the 7.6.1.2 Ifix that introduced that System Property, the code that creates the PARENTWO record has been broken and is not always created for the appropriate WO. This is due to a related design change dealing with the WO Hierarchy. The original design generated the PARENTWO for the top-level WO in the WO Hierarchy and made the top-level WO the Parent on all related records. That was a really bad design and caused a number of performance issues. The design was changed to have the Parent be at the lowest level of the WO Hierarchy meaning that the PARENTWO record only makes sense when MultiAssetLocCI records have Inspection Forms. The code has not quite caught up to the design changes and I have had various cases to fix the issue. It is fixed in certain scenarios but not all.


  • Admin
    Kim Woodbury
    Reply
    |
    Mar 27, 2023

    Please report this as a case through support.

  • Guest
    Reply
    |
    Jul 20, 2020

    This sure sounds like a bug rather than an enhancement.

  • Guest
    Reply
    |
    Jul 16, 2020

    Sorry but my brain is hurting. Please explain the set-up of the forms/PM/JP/WO that produces the doubling. Other than that I believe you're asking that IBM fix it. Have you raised a Case first? This is the request enhancements especially where IBM Support says it's working as per design, but we know that it should work correctly.

  • Guest
    Reply
    |
    Jul 16, 2020

    Attachment (Description)