We are a Scandinavian consulting engineering company and have a small IT project that is outside our primary competencies.
Our customer is located in Denmark and produces products in natural rubber. The products are approved for “food use” and therefore our customer has a need to be able to register the flow of raw material from shipment from the supplier and through the production process at our customer to the finished product.
We have got a couple of data engineering students to make a "quick and dirty" solution consisting of 2 apps for android. Its working fine, but not optimal from a user view.
App 1 scans 2 QR codes via mobile phone.
One of the QR´s is a batch number that identifies the production batch from which the raw rubber originates. This number is assigned by the supplier and mounted as a QR code on a label that follows the rubber throughout the process.
The other QR code that is scanned is Location QR codes which are located in relevant places at the factory. Eg. a label at the supplier, a label at our customer's goods receipt and labels around our customer's production halls on the various machines and processes.
The data logged via the app can see e.g. be:
Date (timestamp) Batch number Location Notes.
01-01-2021 18:25 B424432 SupplyExit “Please check lid”
03-01-2021 14:22 B424432 Port1 “Packaging ok”
03-01-2021 14:33 B424432 Lager 1, reol 2 “”
15-01-2021 11:30 B423332 Stirring “”
15-01-2021 13:30 B423332 Dipping 1 “”
The data is stored in a "transaction table" hosted on AZURE. (SQL)
The second ap (laboratory ap) is used to record data from samples taken from the raw material.
The user scans the batch number as with ap 1 - the location code is locked as "Laboratory"
The data is Date (timestamp); Batch number; Location (laboratory), measurement data 1..10, note.
The batch number is scanned - the rest is entered on the phone.
The data is stored in another table hosted on AZURE (SQL) - there are thus 2 tables in the small solution, which is not necessary and really inappropriate – we think one will do it.
The customer enters to AZURE control panel himself and extracts data in an Excel sheet. It is not very user friendly and the customer is very afraid to delete data. THEY MUST NOT HAPPEN.
It is important that the user can not delete data that is logged - the user must have an option to hide an entry by clicking on a "hide" check box - but the entry must not be deleted, as everything must be able to be used as production documentation to the Danish Food Agency.
[login to view URL]
We imagine a 4 page web based webapplication and keep the track ap. This web application can be hosted at [login to view URL] and via API update data in AZURE or you can choose to place the entire small application on AZURE. Up to you!
The solution shown in the draft on FIGMA (see the link above) consists of:
1. Only a table (SQL) with track data and data from the laboratory.
2. 4 web pages: login page (A), supplier page (B); search page (C), and laboratory page (D).
3. The old laboratory app should not be used anymore - the customer are going to uses the web page instead.
A: User control / password is required for only 2 levels. The customer must know everything/ se all pages. A vendor user should only have access to the vendor page. Keep it simple.
B: Supplier side.
See FIGMA to see the required fields.
There should be a simple search option for the vendor. He must not be able to correct in a post after submit, but he must be able to hide it by a check box (forgot to draw it on FIGMA). The he will have to enter a new one.
C: This page should only be used for queries. D....
Please see [login to view URL] for full dokumentation.
Please tell how you will design the solutions.