User story
As a Heron lab manager, I would like to be able to report on the number of labware that have passed through each stage in the pipeline each day, so that I can monitor the flow of work and identify throughput and bottlenecks.
Who are the primary contacts for this story
Sara, Katy
Acceptance criteria
[ ] The relevant timepoints map approximately to when each new plate is created in Limber.
[ ] It should be by labware rather than by sample.
[ ] It should be easy to map labware to a consistent identifier down the pipeline ('input plate barcode') - and this should ideally be the RT-Q plate barcode (see story sanger/limber#1035)
Additional context
This is currently being done using spreadsheets - a combination of manual entry and some automation involving pulling from Trello. Driving it from the LIMS should reduce human error and free up the time taken for the manual entry.
CoTrack currently provides some reporting of this kind, using the events from the warehouse. Development is stopping on CoTrack in favour of rebuilding it, after which they could extend their solution to help the Heron team further.
It was agreed that Avi and James W would get together to discuss Tableau reporting. The idea is that PSD would make sure events are fired at the right timepoints and in the right format, and the reporting would be done by someone else (probably Avi for Heron).
stevieing
commented
2 months ago
User story As a Heron lab manager, I would like to be able to report on the number of labware that have passed through each stage in the pipeline each day, so that I can monitor the flow of work and identify throughput and bottlenecks.
Who are the primary contacts for this story Sara, Katy
Acceptance criteria
Additional context This is currently being done using spreadsheets - a combination of manual entry and some automation involving pulling from Trello. Driving it from the LIMS should reduce human error and free up the time taken for the manual entry.
CoTrack currently provides some reporting of this kind, using the events from the warehouse. Development is stopping on CoTrack in favour of rebuilding it, after which they could extend their solution to help the Heron team further. It was agreed that Avi and James W would get together to discuss Tableau reporting. The idea is that PSD would make sure events are fired at the right timepoints and in the right format, and the reporting would be done by someone else (probably Avi for Heron).
Liz E has similar requirements in this story - https://github.com/sanger/General-Backlog-Items/issues/169 - although that is at a higher level, rather than focused on library prep.