Sometimes, after testing an alcohol check procedure with pilot equipment and ordering the same model, people are caught off guard when the delivered equipment's screen layout or method of viewing results is different. Even if the measuring unit itself is the same, if the configuration of the PC program, power supply, printer, cables, or disposable accessories such as mouthpieces used for blowing differs, it is hard to reproduce the workflow confirmed during the pilot.
What to compare here is not a single model name, but the equipment combination and sequence of use actually tested during the pilot. If you base the decision on verifiable actions, such as who views the result on which screen, where the result is kept, and whether a printout is needed, you can judge whether the delivered items meet the purpose of the pilot.
First write down the actions that passed in the pilot
If you keep only how satisfied people were with the pilot, it becomes unclear what to compare at delivery. Rather than "it was easy to use," it is better to write the sequence from test to confirmation, such as "after the test, the result was shown on the device screen, and the person in charge viewed that result on the PC."
Pilot results may not come from the unit alone. If a PC or printer prepared by the supplier was used as well, you need to determine whether that equipment is included in the delivery list or was simply on loan. If you plan to switch to equipment the site already has, treat the connections confirmed in the pilot and the connections after delivery as separate conditions.
The reference configuration sheet is a tool for comparing delivered items
The reference configuration sheet is not a document for finding out every internal item of the pilot equipment or copying it exactly. It is a table for comparing the configuration confirmed in the pilot and the delivered configuration on the same basis. Rather than trying to change items managed by the manufacturer on your own, organize it so the supplier explains the differences between the pilot configuration and the delivered configuration within the scope they can confirm.
| What to compare | What to record during the pilot | What to look at on delivery |
|---|---|---|
| Measuring unit | Model name and information that distinguishes each unit | Whether the model and unit type match what was ordered |
| Testing and result confirmation | Settings used and results confirmed on screen | Whether you can test and view results in the same order |
| PC and printer | Program used, whether connected, sample printout | Whether results can be viewed or printed on site equipment |
| Peripherals and consumables | Mouthpieces, power supply, cables, printer | Whether the needed items are on the delivery list |
Write only facts actually confirmed in the table. Photos of the unit and cables help confirm the configuration, but photos alone do not prove the PC program's screens or the conditions for viewing results. Keeping screen captures and sample printouts as well makes it possible to specify what to look at again during acceptance.
Decide whether to adopt conditions changed during the pilot
Pilot equipment may be in a different state after site testing than when it was first installed. If the order for checking results or the screen display conditions were changed during testing and that change affected the evaluation, you need to decide whether to adopt it in the final delivered configuration. Conversely, separate conditions applied temporarily for testing convenience so they are not included in the delivery standard.
As a hypothetical case, suppose a workplace viewed test results on a PC prepared by the supplier during the pilot but wants to use an office PC after delivery. The observed fact is that results could be viewed on the pilot PC. This cannot be interpreted to mean that results can be viewed the same way on the site PC.
A possible action is to connect to the office PC before delivery or during acceptance and confirm the same viewing sequence as in the pilot. The completion criterion is not the fact that a cable was connected, but a state in which, after a test result is produced, the person in charge can confirm that result on the needed screen or printout. If that configuration cannot be reproduced, update the configuration sheet to reflect whether to include the pilot PC or adopt another confirmation method possible on the site PC.
If the applicable materials differ, look only at the affected stages
Being in the same model line does not mean the user manual or PC program applied to the pilot equipment and the delivered equipment is the same. The DATECH Downloads section posts "The New AF-50 / AF-50AD Korean manual" as a separate item. This is why you need to compare the title and applicable models of the materials referenced during the pilot with those provided with the delivered items.
If a difference is found, there is no need to repeat the entire pilot from the beginning. You can set a plan that divides which stage the change affects, among testing, result storage, result confirmation, and printing, and rechecks only the affected stages. For example, if only the printout format changed, it is appropriate to check whether the needed information is kept on the printout rather than the whole test procedure.
You can ask the supplier to explain not only the names of changed items but also which part of the flow confirmed in the pilot changes. If the explanation and recheck results meet the pilot standard, add that content to the configuration sheet. If not, decide on an alternative configuration and additional check items, and then judge whether to accept the delivery.
Record both the differences and the check results in the acceptance record
During acceptance, note next to the reference configuration sheet the items that differ from the pilot equipment, and distinguish whether each difference comes from a product change or a site request. Do not pass over items not yet confirmed as blanks either. Record what will be looked at again and in what environment, so the pilot evaluation and delivery inspection stay connected.
Before returning the pilot equipment, also decide how to handle the personal rosters and test records used in testing. What is needed is to keep the actions confirmed in the pilot and the inspection results, not to mix test data into the new equipment's normal operating records. Keeping the configuration sheet, change list, and recheck results together lets you narrow down differences based on actions actually confirmed, rather than guessing from the model name alone, even if questions arise after delivery.