Roche RIS Feedback Portal

Please submit any feature requests and vote on ideas that have already been submitted to indicate your interest in seeing them developed

 

Merged idea

This idea has been merged into another idea. To comment or vote on this idea, please visit NMON-I-93 Pending samples (as SWL widget) per analyzer (Old title-Sample Throughput Widget based on device).

Assessing capacity through real time data Merged

  • Guest
  • Oct 2 2024
  • Promoted
navify Monitoring
Idea detail description

There is a need to understand current levels of capacity in both automation, instruments and pre-analytic systems so that the lab staff can make decisions on whether to load more samples to their setup or wait not to cause blockages or unfavorable conditions on their automation setup.

Attachments Open full size
  • Admin
    Qilei Ge commented
    31 Mar 08:35

    @Daniel Swahn As discussed on 28.Mar, this topic will be elaborated with the customer during the june visit.

    Attachments Open full size
  • Guest commented
    November 21, 2024 08:39

    Hi @Daniel Swahn , we discussed with the team and some questions came up we hope you can help us answer so we get a better image:

    • Which pre-analytics are the customers using?

    • Do they have a standby buffer? (module)

    • Which Monitoring version is the customer on?

    Thank you and best!

    Attachments Open full size
  • Guest commented
    November 08, 2024 10:02

    @Daniel Swahn @Andre Maansson
    Thank you for the feedback session earlier! I was able to found the idea and added the summary of our previous session. Please feel free to expand on my notes where you see needed. Thanks!

    Session with affiliate, 08.11.2024:

    Pain point:

    • There is no real time update on how many samples oin total are on the track to help the users know when to load more racks onto the automation.

      • Example current use: Users are loading 20 tubes every 10 minutes to not overload the automation.

    • Current SWL and ITW does not help in this case because tubes that have been pipetted are sent to post-analytics for storage while the test is being run. The sample is marked as "Processed" even thought it is still being run in Analytics.


    Techn. restrictions:

    • To achieve the exact count, it would require data from the instruments on how many tests are currently being run on an analyzer, which Monitoring is not able to get through IGW.

      • Affiliate and customer are ok with the count being not fully exact. A range indicator would be great to see when the automation has capacity and when to not load any more tubes onto it.


    Customers: Nordics have 25 with automation that have Monitoring where this would be relevant

    Attachments Open full size

Related ideas