Upstream
FAQs
For general questions regarding the GS1 standards or membership please contact GS1 Australia
FAQs - Answers
Question 1. How do GS1 standards support the model?
Answer: GS1 standards for identification (GTIN, GLN, SSCC, GS1 Logistic Label) support the UIM model. From the eCom Standards only the XML syntax is supported in the exchange of information between the trading partners in support of these supply chain processes. To cover all upstream transactions, fifteen messages have been selected from the GS1 XML standards (see figure right).
To help implementation of the standards, supporting guidelines are available:
- GTIN allocation rules including specific rules for ingredients, raw materials and packaging,
- UIM implementation guidelines per building block including Message Implementation Guides (MIG's).
Question 2. Who do I contact for further information?
Answer: To find out more information about Upstream, please contact the GS1 Australia Industry Engagement Team on 1300 366 033 or email
Question 3. Companies all have different project priorities; how can Upstream Integration not suffer from a lack of momentum in Australia?
Answer: The important achievement of global GUSI and its Australian counterpart is that as companies become ready to implement upstream integration, there is a common, standard way of doing so, making it scalable, easier and cost effective to bring on new partners. This removes barriers to implementation. Also, companies not ready to integrate IT systems, are meanwhile proceeding to align business processes to get ready for systems integration when the time is right.
Question 4. Why doesn’t the GUSI UIM use GDSN for data synchronisation?
Answer: GUSI UIM uses bilateral messaging for data alignment rather than GDSN (Global Data Synchronisation Network) accredited data pools used by downstream business. Some of the reasons appear to be:
- there are many more items and prices changes downstream making data alignment more volatile and therefore needing more disciplines which GDSN provides
- there are more suppliers to downstream customer and so a single interface via data pool works well for downstream but can be "overkill" for upstream
- GDSN is designed more for alignment of data for finished goods rather than raw materials, although this can be developed as needed
- downstream data alignment is also about timeliness (synchronisation) as the rate of change demands timely updates to keep partner systems in line
Question 5. Is transport and 3rd party logistics covered in the GUSI model?
Answer: Version 3.0 of the Despatch, Receipt and Consumption Implementation Guide will include transport and 3PL.
Question 6. What about small suppliers who have unsophisticated IT?
Answer: The GUSI model is not dependent on having sophisticated IT solutions. It is as much process-based as IT reliant. Much of the process standardisation that can be achieved in your interfaces with larger, IT-enabled partners can also be achieved with smaller partners. You may choose to look at community IT / portal type options that can deliver IT enablement to smaller partners also.
Question 7. Some items are customised for one manufacturer; why are Barcodes (GTINs) necessary for those?
Answer: Customer-specific items will carry a Barcode (GTIN) allocated from the customer’s number range, not the supplier's. Barcodes (GTINs) are unique, standard and secure. They are the numbering structure and format used in standard GS1 barcode symbologies.
Question 8. Why does Purchase Conditions follow Master Data Alignment in the GUSI UIM?
Answer: The GUSI UIM tends to treat these as separate building blocks; with Master Data Alignment being the sharing of item master data about the products agreed to be traded. Purchase Conditions is the sharing of data to update purchasing and other systems about agreed prices, terms and other trading partner specific deals.
This can sometimes be confusing as presented in the GUSI UIM, with MDA preceding PC; the argument being that prices and terms are agreed first and then the master data about items and their prices is aligned.
This is still the case, where businesses will always negotiate the business relationship and what is to be bought and sold in what quantities and at what costs; the GUSI UIM is not attempting to redefine this.
Rather it suggests that, particularly for raw materials items bought from upstream suppliers, the item data is not very volatile, in that once the customer has agreed to buy say three different grades of sugar in either liquid or granular form, this item data does not change much. However the price may fluctuate and so it may be that the pricing information needs to be more regularly aligned between buyer and supplier systems, hence the Purchase Conditions block is separated out and shown as occurring after item data alignment.
Question 9. Is the scanability of barcodes reliable?
Answer: The GS1 barcoding guidelines ensures that barcode size, contrast, position etc. is adhered to so that barcodes can be relied upon to scan correctly first time.
Question 10. The GUSI UIM v2.2 does not contain all Implementation Guides
Answer: Later versions of GUSI will add Implementation Guides for the remaining building blocks, starting with Financial Settlement.
Question 11. Does GUSI cater for International Transport and container delays?
Answer: The current GUSI model does not have functionality covering this. Today, such a situation would be managed manually by exception. The functionality is under development: It will be part of the future 'Transport' module (in UIM 3.0) with the third party LSP involved.
Question 12. Does GUSI cover customer giving supplier "authority to purchase" its own raw materials?
Answer: Thus "authority to purchase raw materials" is managed in the "Integration agreement". Defining a target stock coverage profile (in days) for raws that the supplier can purchase, based on mid long term forecast.
Authority to make: Some companies are currently testing the "Purchase conditions" message to manage "authority to make". The next steps will be discussed in the GUSI PMO and Working Group. So currently, authority to purchase is linked to the forecast horizons e.g. if the total horizon is three months, the first month may be commitment to manufacturer purchase (i.e. equivalent of PO), 2nd month may be authority to purchase inputs and 3rd month is purely forecast estimates.
Question 13. Is GUSI just another way suppliers will have to do business with manufacturers?
Answer: The Australian industry initiative aims to ensure that GUSI is THE way that upstream supply chain integration will occur. Those with existing connections may choose a migration plan.
Question 14. What KPIs can be used to gauge the success of an upstream implementation?
Answer: If you have developed a well defined Integration Agreement, specifying things like e-message compliance, response times, process adherence, then you should be measuring each other against these requirements.
Question 15. Bulk items – shipped versus discharged quantity, does GUSI cater for this?
Answer: In this scenario, typically a tanker cannot discharge the full shipped quantity due to residue, and the customer will pay for discharged quantity.
This scenario can be catered for in the model by the supplier sending a GUSI Despatch Notification with the shipped quantity, then sending an updated Despatch Notification with the discharge quantity. If the discharge quantity is calculated by the customer, the supplier may chose to be advised of the discharged quantity using the current process, or may receive electronic receipt Notification from customer. Using the latter would have to ensure message is timely so does not delay invoicing.
Question 16. How will scanning work on bulk (e.g. tanker) deliveries?
Answer: The SSCC label can be applied to the shipment documentation and scanned as part of the receiving process as per palletised goods.
Question 17. To what levels does GUSI support pricing?
Answer: For standard groupings of base units e.g. a reel of 1000 labels, a case of 24 glass bottles, a barcode (GTIN) is assigned to the standard grouping and the price is expressed against that barcode (GTIN). For example: a reel of 1000 labels = GTINX, price $Y per one reel (not $0.0000X per label).
If individual base units are the sale unit, then GUSI supports pricing at this level as needed.
Question 18. How should batch track and trace work?
Answer: GUSI is an enabler for capturing traceability data from upstream suppliers. The implementation of full track and track relies on each party in the supply chain linking captured traceability data to their internal processes so that the continuity of data about an item’s lifecycle is not broken. GUSI provides the process and data capture standards to electronically capture traceability data. The GS1 Traceability Model then shows how to utilise that data to provide full supply chain track and trace.
The batch number is an important piece of traceability data. The working group provides a guideline to the creation of batch numbers. The batch number supplied by the bulk supplier will be made up of the supplier source site identifier + shipment date. This can then be traced back by the raw materials supplier to the internal batches contained within that source site location on the shipment date. The batch number is to have a minimum granularity of being unique per day. For example the shipment date cannot simply nominate the last day of the week if there were multiple shipments in a week.
