Receiver Repair Dashboard Tool
The receiver return and repair tool is to manage receivers that are currently in the taggle office awaiting repairs. It is independent from dash2 to consolidate and partition from other undeployed or “returns” units.
This tool is specifically operating on Microsoft excel until additional tools can be made available to write the program as a web driven application.
Feature | Status of implementation |
|---|---|
Automatic Transfer Between Return List and QA | Implemented |
Add Returned Receiver Form which includes validation and quick access to dash2, also blocks duplicates from being added | Implemented |
Registry button hook in, user can click on any item and get dash2 information for that unit | Implemented |
Details button, expands details for any selected item including QA details | Implemented |
Commence and halt repair, users can quickly change repair status of a selected item, with limit of 2 units being repaired at once | Implemented |
QA Percentage and status, QA percentage based off 7 day period with check status on conclusion of that period | Implemented |
Ship receiver status, quickly change status of receivers shipped from inventory | Implemented |
Date completed QA for all receivers transitioned to inventory | Implemented |
QA to complete listview simple press of button, includes date of completion | Implemented |
Check to basestation API for QA pass - Now working as of 17/10/2023 | Implemented |
Repair Time Sheet with single button press start and stop | Implemented |
Include date returned column on all sheets/listview items for logging of receiver processing. | Implemented |
details form includes specific revision details, more accurate ID interpretation and date returned labels | Implemented |
Graph and review worksheet for KPI hook in | Not yet implemented |
Create target for repair metric (i.e 2 per week) | Not yet implemented |
Notification for receivers completing QA | Not yet implemented |
Receiver Repair Urgency Notifier | Not yet implemented |
QA/db testing Remote command initialisation to ansible including arguments as receiver id (requires SSH configuration on powershell or cmd) Requires API to function as intended. | Not yet implemented |
Repair start date when button is pressed and repair finish date (QA Start date) - To be QA driven, to enforce conclusion of repair | Not yet implemented |
Time of repair recorded per receiver in the Ready worksheet/listview, likely also needs a report for averages too. May require additional dashboard attachment or reporting mechanism (another workbook to detach? could include other KPI required details.) | Not yet implemented |
Component consumption and receiver modification checklist prior to QA - form added, needs more details | Not yet implemented |
API hook in for receiver transit status within completed/shipped receivers listview | Not yet implemented |
Additional 30 minutes of packaging and handling time for repair time sheet (0.5) | Not yet implemented |
Issues, fixes and bugs
Issue | Status |
|---|---|
Details form displays receiver ID’s as Taggle-<id> inclusive of adding a 0 before 2 digit ID. - enhancement | enhancement |
dash2 link can go to any receiver id from any selected item from any listview (initially could only select from listview1) - enhancement | enhancement |
Details can now display unknown receiver details - bug fix | fixed |
added confirmation dialog to commencement of QA - addition | enhancement |
Details form properly displays dates of returns - bug fix | fixed |
imported Json Conversion library | enhancement |
Start QA on receiver that has been repaired can result in type mismatch error - have not been able to recreate, possible data type difference causing issue. - Likely fixed, version differences didnt include error handling | fixed |
A space after Unknown IDs breaks the details form, tried basic, perhaps might resort to validation checks that change ID variable | bug |
Listviews display erroneous data from time to time, best current fix is refreshing the data load from the worksheets to clear it up - the worksheets are the source of truth! | bug |
QA start currently does not conclude a repair status and timestamp. This feature needs to be implemented/no blocks. | planned |
Halt Repair function does not do time dif hour calculation, only displays zero. | bug |
Screenshots