Hi!
Answers to question:
1. If there are thousands of identical sub-equipment items, how do you decide which sub-equipment to connect to which main equipment?
When it comes to sub-equipment and “loose gear”, same type and with same ID’s we have following scenarios.
Were talking mainly about loose gear such as shackles of different types of eyebolts that has been manufactured with no unique ID’s.
- Brand new items ready to be mounted/attached (picked physically from shelves)
- Used items that has been used together with another parental item previously and I.ex later detached (physically been placed in a quarantine pallet with tags where it came from or unit it previously connected to)
- “New” old/used items transferred from another system to Onix (i.e New customer who previously used another system, then switched to Onix whereas all of the documentation is uploaded into new profiles established)
I can start with saying that having a standardized profile description on each and every item type has been a good practice for better looking and more compressed controlcard. Making it easier for the field operators to identify and control sub equipment on main unit for better overview.
Me personally does the whole process, as Field operator, ordering, documentation and backoffice related to process.
- Connecting new items
a) Example. I have ordered 50 new psc. of item X. The supplier or provider issues a certificate from this X batch on X-date.
Case: I need 4 psc. of X out of 50 psc, attached to a main unit.
In item look-up, I select 3 out of 50 of item X, making them “inactive” and changing the profile description on the fourth to 4 psc. Example below.
To ensure its from the right batch I need to confirm issued date and certificate number is correct. Making them inactive will also lead to having the correct remaining amount of item X in list next look-up.
Previously last step was to go through this profile I edited and connect it directly to the main. But now I have 10X plus more clicks finding main and then look it up item I made and then connect it.
The challenge here is when you have more of same item X mixed with scenario 2.
![example 1](https://europe1.discourse-cdn.com/business20/uploads/onix/original/2X/0/0606c2b0bcfc39fc30fd72f6990822f2cbbfe067.jpeg)
b) Example. One of the workshops need 4 psc. of item X for an operation. I perform annual inspection physically (applying color coding) and then update the control card. Additionally In the description add the Workshop code for where its located.
These items will also appear in item look-up in the process of connecting item X from a main.
- Used Items
a). Example. When item returns offshore, workshops no longer need excess items, or a unit has been stripped for its sub equipment due to maintenance – it gets returned to my department. Marked with tags in pairs i.e two’s , four’s or singles etc., with info where it came from and what unit it was connected to. The item then is placed in a quarantine pallet/shelf.
This pallet can i.e contain item X,Y,Z of batches A and B with different certificate no., and how I verify that is to check the label tags where/which unit it originated from, and then look it up in Onix.
Case:I want to re-use 2 psc of item Y of batch B and attach them to a new main.
I locate them in Onix, but cannot connect them directly, but instead give them a “fictional temporary Unique ID” and then look them up by connecting them through main. I then need to enter the chosen 2 pcs. item Y and delete the temporary ID and then head back to main to continue task.
- “New to onix” used items
a) As a representative of a third party inspection company, the customer I work with now used another system from another third party. There is still many items and units that haven’t been “converted” yet, which also contains items X, Y, Z from another batch i.e C, D and E.
Case: I receive notice that a certain main unit need to be inspected. Since a I have full access to customer account to old third party system, I can easily download documentation, inspection history and its sub items connected.
These main’s have i.e item Y with batch E certificates issued by another supplier, and when initially converting this item to Onix its imperative to establish one profile for “new-used item Y” and the amount in this actual batch, in item details and keeping track of how many remaining in this actual item’s description. (text)
At the same time there’s already existing item Y of scenario 1, 2 and 3 with batch A, B and C etc.
Summarise:
Not having the ability to immediately connect item to main is a big issue in these scenarios.
This function was working quite well, and as I have expressed through several mails earlier, the focus on less clicks and efficiency for the operators should be considered more.
All of these extra clicks and additional time-consuming tasks related to inconvenient changes your developers implement adds up. At the end, who pays for it? Also for the operators and back-office it creates more pressure in already short timeline.
I really hope you guys either revert this change or find a solution which involves less clicks not having to move back and forth between items.
Answer for question 2 is, No. We could keep track of different items of batch A, B , C in excel, but item description in Onix works quite well for that.