Checklist to keep your system lean
To get and keep a clean system it is important that your system is clean, logical and recognizable. This checklist contains some important pointers for this purpose. If you need any help cleaning up your system, feel free to contact AlisQI support.
- Consistent use of language
In general users find it pleasant when they see the same words reappearing in the system. That’s why it is good that a certain type of field, which is being used at multiple places within AlisQI, has the same name (more or less).
- Menu bar groups
Do you have a lot of analysis sets? Then separate menu bar options could come in handy.
- Analysis-set groups
Are the analysis sets grouped in a way they are easy and logical to find?
- Consistent naming
Are the names you give analysis sets or fields within analysis sets consistent with other places which are similar
- Double input
Is the same data being put in in more analysis sets? Try to prevent this by for example connecting analysis sets with each other or by merging analysis sets
- Sorting of analysis sets fields
Do you use batch number, sample number and remarks within multiple analysis sets? Try to improve the recognizability by giving them the same order in all the analysis sets.
Are headers added to different parts of an analysis set? This can improve the recognizability and make it easier for users to find what they are looking for.
- Index fields
Index fields can be used to set up specifications, but are also handy for field visibility. Depending on a product for example, you might not need to see every field in every case.
Are you getting the same alarm in different ways (or via different alarm types)? Delete workflows or alarm types to stop this from happening.
- Unused fields
Are there fields within your analysis set which are never or almost never being filled in? Maybe you can remove them or include them somewhere else in AlisQI.
- Drafts & inactives
Have you got a lot of drafts or inactive analysis sets? Go through them and see what you can clean up.
- Serial numbers
On the background we can give more intelligence to serial numbers, for example a part of the serial number could change depending on a choice of a selection list.
- Unused options
Are certain options of a selection list never or almost never being used? Consider if you can deactivate these options, if these options are being used in past results they will continue to exist there.
- Few to no options
If a selection list contains few to no options, and is not being used for statistical analysis then you could consider to not adopt these options in a selection list. Maybe there is some other way, for example using a check box.
- Not assigned
Are there selection lists which aren’t assigned to an analysis set? Consider removing these selection lists.
- Similar options
Are there several selection lists containing the same or similar options? Maybe these can be combined in one selection list.
- Drafts & inactives
Have you got (a lot of) drafts or inactive selection lists? Go through these and see what you can remove.