This document describes how NLP customers can report Europ Pallet movements electronically.

Transcription

1 1 of 11 1 INTRODUCTION This document describes how NLP customers can report Europ Pallet movements electronically. 2 DEFINITIONS Navn GLN EPC Epcis GRAI active tag AS1 AS2 AS3 Asset Type EPC tag HF tags RFID read-only tags read-write Beskrivelse The GLN (Global Location Number) provides a standard means to identify legal entities, trading parties and locations to support the requirements of electronic commerce. The GLN is designed to improve the efficiency of integrated logistics while contributing added value to the partners involved, as well as to customers. Examples of parties and locations that can be identified with GLNs are: Functional entities - e.g., a purchasing department within a legal entity, an accounting department, a returns department, a nursing station, a ward, a customer number within a legal entity, etc. Physical entities - e.g., a particular room in a building, warehouse, warehouse gate, loading dock, delivery point, cabinet, cabinet shelf housing circuit boards, room within a building, hospital wing, etc. Legal entities/trading Partner e.g., buyers, sellers, whole companies, subsidiaries or divisions such as suppliers, customers, financial services companies, freight forwarders, etc. An identification scheme for universally identifying physical objects via RFID tags and Code other means. The standardized EPC data consists of an EPC (or EPC Identifier) that uniquely identifies an individual object, as well as an optional Filter Value when judged to be necessary to enable effective and efficient reading of the EPC tags. EPC Information Services (EPCIS) is a new breakthrough for trading partners to share information. A standard-based approach to securely share product movement information that will provide visibility and improve businesses processes in an unprecedented manner Global Returnable Asset Identifier: The globally unique EAN.UCC System identification number for a reusable package or Asset Identifier transport equipment of a certain value, such as a beer keg, gas cylinder, pallet, or crate. The Global Returnable Asset identifier comprises a mandatory part: the Asset Identification Number (EAN.UCC Company Prefix, Asset Type, and Check Digit) and an optional part: the Serial Number. A class of RFID tag that contains a power source, such as a battery, to power the microchip s circuitry. Active tags transmit a signal to a reader and can be read from 100 feet (35 meters) or more. Applicability Statement 1: The draft specification standard by which vendor applications communicate Electronic Data Interchange (EDI) data over Simple Mail Transport Protocol (SMTP). When implemented, AS1 will enable users to connect, deliver and reply to data securely and reliably over SMTP. Applicability AS2: The draft specification standard by which vendor applications communicate Electronic Statement 2 Data Interchange (EDI) or Extensible Markup Language (XML) data over the Internet using Hypertext Transfer Protocol (HTTP). When implemented, AS2 will enable users to connect, deliver and reply to data securely and reliably over HTTP. Applicability Statement 3: The draft specification standard by which vendor applications communicate Electronic Data Interchange (EDI) data over the Internet via File Transfer Protocol (FTP). When implemented, AS3 will enable users to connect, deliver, and reply to data securely and reliably over FTP. A number assigned by the owner of an asset to uniquely identify a type of returnable asset within a Global Returnable Asset Identifier (GRAI). RFID tag that complies with the EPCglobal standard and contains an Electronic Product Code (EPC). RFID tags that operate at 13.56MHz. Radio Frequency Identification: A data carrier technology that transmits information via signals in the radio frequency portion of the electromagnetic spectrum. A Radio Frequency Identification system consists of an antenna and a transceiver, which read the radio frequency and transfer the information to a processing device, and a transponder, or tag, which is an integrated circuit containing the radio frequency circuitry and information to be transmitted. RFID tags containing data that cannot be changed unless the chip is electronically reprogrammed. RFID tags with the capability to record and update data multiple times

2 2 of 11 tags returnable asset rti RFID reader RFID tag SSCC smart label UCC Company Prefix UHF tags A reusable entity owned by a company, which is used for transport and storage of goods. Reusable Transport Items: see returnable asset. An RFID reader communicates via radio waves with RFID tags and delivers the information in a digital format to a computer system. Also known as an Interrogator or a reader. A microchip attached to an antenna that sends data to an RFID reader. The RFID tag contains a unique serial number, and can also contain additional data. RFID tags can be active, passive, or semi-passive tags. Serial Shipping Container Code: The globally unique EAN.UCC System identification number for logistic units. The SSCC is an 18-digit number comprising (from left to right) an Extension digit, EAN.UCC Company Prefix, Serial Reference, and Check Digit. A label, containing an RFID tag, which can store information such as a unique serial number, and communicate with a reader. A globally unique number assigned to companies by GS1 to create Prefix identification numbers of the EAN.UCC System. RFID tags that operate between 866MHz and 930MHz. These tags are able to send and receive data faster and at greater distances than other tags. Ultra-high frequency tags are typically more expensive than other tags because they use more power. In addition, these tags are limited by the fact that radio waves at these frequencies do not pass through items with high water content, such as fruit. 3 REFERENCES Dokumenter Lokasjon Beskrivelser EPCIS Homepage for EPCIS standards EPCIS Standard Follow link from the EPCIS Homepage The EPCIS standard EPCIS Artifacts (XSD, WSDL Follow link from the EPCIS Homepage EPCIS schemas Schemas) EPCglobal Tag Data Standards Version a_stanard_1_3.pdf Standard defining how tags are encoded and stored on RFID tags. 4 ARCHITECTURE AND PROCESS The architecture for electronic reporting to NLP is illustrated below:

3 3 of 11 Key principles for the architecture: - All returnable asset movements are reported to the NLP EPCIS server. The EPCIS server will store all transactions reported, without any logical evaluation of the transaction beeing reported - According to the EPCIS standard, capture can be reported using xml over http or message queue. NLP supports xml over http. - The NLP logistics server will be updated based on information reported to the EPCIS server. - The NLP logistics server will evalutate messages reported and handle the information accordingly. All messages are stored in a transaction log enabling the ability to trace the result of each message. EDI managers will be alerted when errors occurs. The message log is available from the NLP web and is available for EDI managers. 4.1 BUSINESSLOGIC AND RULES Reusable Transport Item (RTI) Movements Messages shall be implemented according to the following principles: - Item movements shall be identified by the deliverynotenumber ( pakkseddelnummer as defined by GS1 Norway) - The customer order number should be present if the number is available. This will simplify routines at the receiving party. - Consignmentid ( sendingsnummer ) should be present if available. This will simplify routines at the receiving party. There may be more than one consigment id for each transaction. - All messages shall contain a reference to an accountid that identifies an NLP EDU user. NLP will issue account id s. - The following rules apply if a reusable transport item is reported from different channels: o A transaction will not be accepted if a transaction with an identical deliverynotenumber is already committed. Two transactions are identified as identical if the deliverynotenumber of both messages are identical. o The following rules apply if the transaction is not commited by the receiver (and the transaction is not auto-committed): Changes entered manually are always accepted

4 4 of 11 Electronic messages are accepted if the deliverynotenumber of the two messages are identical. - Business rules will be applied to the transaction by the NLP logistics system. The EPCIS server will contain all messages received, regardless of the message status in the NLP logistics server. - The EPCIS server will store all messages regardless of the sender and receiver GLN. The NLP logistics system will only accept messages with valid sender and receiver GLN. - The NLP logistics system will offer a transaction log displaying the status of messages received, including status code if the message is rejected. - It is not possible to delete transactions that are sent to the EPCIS server. The only possability is to send an identical message with quantity 0. This message will not be accepted by the NLP logistics server if the transaction is already committed Electronic Committ message from RTI receiver Receiving parties wishing to send electronic messages need to contact their vendors to ensure that their vendor send correct information: - Deliverynotenumber must be transferred from the vendor. - The vendor must enter and send date immediately to ensure that the receiving party has the information available when goods are received and controlled- - The sender must send the exact deliverynotenumber with no errors. 5 HOW TO BECOME NLP EDI PARTNER You can contact NLP using the following addresses: integrasjon@nlpool.no for account initiation and for other issues regarding integration datasupport@nlpool.no for operational issues 5.1 HOW TO GET STARTED Pallet movements shall be reported according to the EPCIS standard. To start sending electronic Pallet movement messages you have to go through the following phases: - Establish a test account to test your integration - Acceptance testing before going alive - Going live 5.2 INITIAL TESTING The addresses to be used for testing are: Service address Description Status

5 5 of 11 Address to be ues for testing (EPCIS capture). Test server is operational Contact NLP if you need access to the test server. 6 NLP DATAFORMAT The current version of EDI integration supports reporing of Pallets sent and Pallets received 6.1 XML SCMEMAS FOR RTI (PALLET) MOVEMENT MESSAGES EPCIS will be used as the standard and format for reporting of RTI (pallet) movements. EPCIS is a standard made for tracking RFID tags. This standard will be used when NLP introduces new RTI units with RFID tags. NLP has chosen to use EPCIS even for Euro Pallets to simplify the transfer to RFID reporting. Initially, before RFID tags are introduces, a subset of the EPCIS standard will be used. NLP will not support all features defined by the EPCIS standard. The EPCIS defines different event types: - Object Event, to report individual RFID tags - Aggregation Event, to report hierarchical tag structures - Quantity Event, to report the number of a specific type - Transaction Event, to assosiate RFID tages with business transactions Initially NLP will only use QuantityEvent to report the number of Euro Pallets sent or received. Euro Pallets will not have unique id s and will not have a tag attached. NLP will utilize the full set of features of the EPCIS standard when new pallets and crates with build-in RFID tags are introduced. It is possible to report more than one RTI (pallet) movements in one xml message. Different types of transfers may be implemented based on this guide: - RTI s used for delivery from vendor to wholesaler - Return RTI s from wholesaler to vendor - Internal transfer of RTI s o Between wholesalers o Between wholesaler and shop, both directions o Between vendors - Transfer from customer to NLP - From NLP to customer This transaction will normally be registered directly in the logistics system Next we will describe the message used for the reporting of RTI s (pallets) sent and RTI s (pallets) received.

6 6 of Sending Returnable Transport Items (RTI) All RTI movement reporting to NLP is implemented according to the EPCIS standard standard (EPC Capture). The xml message to report pallets sendt is described below. Reporting of RTI movements shall be made using the Capture interface as defined in the EPCIS standard. An example xml message is displayed below: <?xml version="1.0" encoding="utf-8" standalone="no"?> <epcis:epcisdocument xmlns:epcis="urn:epcglobal:epcis:xsd:1" xmlns:xsi=" creationdate="-03-10t21:30: :00" schemaversion="1.0"> <EPCISBody> <EventList> <QuantityEvent> <eventtime> t12:00:00</eventtime> <eventtimezoneoffset>+01:00</eventtimezoneoffset> <epcclass>urn:epc:id:grai: </epcclass> <quantity>24</quantity> <bizstep>urn:epcglobal:epcis:bizstep:fmcg:shipped</bizstep> <readpoint> <id>urn:epc:id:sgln: </id> </readpoint> <bizlocation> <id>urn:epc:id:sgln: </id> </bizlocation> <biztransactionlist> <biztransaction type="urn:nlpool:deliverynotenumber"> dpoint= &year=&transactionid= <biztransaction type="urn:nlpool:consignmentid"> t= &year=&transactionid= <biztransaction type="urn:nlpool:ordernumber"> &year=&transactionid= <biztransaction type="urn:nlpool:vendorordernumber"> point= &year=&transactionid= <biztransaction type="urn:nlpool:accountid"> &year=&transactionid=1234 </biztransactionlist> </QuantityEvent> </EventList> </EPCISBody> </epcis:epcisdocument> It is possible to include more than one quantityevent message in each xml transfer. Feltnavn QuantityEvent Beskrivelse Only QuantityEvent messages can be used for reporting of Euro Pallets. Messages with other event types will be stored in the EPCIS repository, but they will not be transferred to the NLP logistics server.

7 7 of 11 eventtime og eventtimezoneoffset epcclass eventtime is UTC time, eventtimezoneoffset is UTC offset. The date format is xsd:datetime, see xml schema for more information. The epcclass for Euro Pallets (wood) will always be: urn:epc:id:grai: quantity bizstep readpoint Other epcclass id s will be used for future RTI s. The GRAI structure is: urn:epc:id:grai:companyprefix.assettype.serialnumber is the CompanyPrefix for Norsk Lastbære Pool AS is the Euro Pallet type id 0 means that there is no serial number for Euro Pallets This id structure is important for future RTI s with RFID tags. This is the number of Euro Pallets being reported in this message. When reporting RTI s sent, use the following value: urn:epcglobal:epcis:bizstep:fmcg:shipped readpoint identifes the place where the Tag is being read, normally using a RFID reader. For Euro Pallets this will be the GLN of the sending party. The GLN shall be defined using the following format: urn:epc:id:sgln:companyprefix.locationreference.serialnumber GS1 Norway has desided to issue 12 digit location codes directly to individual locations. This 12 digit location code shall be inserted as the CompanyPrefix as defined in the standard. LocationReference and SerialNumber is set to 0. An example of a correct readpoint is: urn:epc:id:sgln: bizlocation Be aware that the location code shall only containt 12 digits. The last digit is a control digit, and shall not be part of the code. See EPCglobal Tag Data Standard for more information regarding urn:epc:id:sgln: namespace. bizlocation identifies the location where the RTI is heading after being read at the readpoint. For Euro Pallet reporting this identifies the receiving location (GLN). The bizlocation format is the same as for readpoint. An example of a correct bizlocation is: urn:epc:id:sgln: biztransactionlist Be aware that the location code shall only contain 12 digits. The last digit is a control digit, and shall not be part of the code. See EPCglobal Tag Data Standard for more information regarding urn:epc:id:sgln: namespace. For each QuantityEvent there can be zero or more biztransactions attached to the message. NLP utilizes this to identify the business context in which the RTI movement is happening. NLP has identified the following biztransactions: - Consigmentid ( Sendingsnummer ) - Deliverynotenumber ( Pakkseddelnummer ) - Ordernumber - Vendorordernmber - Accountid Usage of these identifiers is described in section 4.1 BUSINESSLOGIC AND RULES. For each transaction on the transactionlist a transactiontype is identified. The transactiontype will be used by NLP to identify what identificator to be used. The transactiontype must be present. All businesstransations (biztransactions) shall point to a url that includes information related to the transaction. If the provider of the transaction does not have its own service, the NLP url may be used. NLP will offer a trace for transactionidentifiers at the following address: The following parameters are used:

8 8 of 11 transactiontype This identifies the type of transaction. Readpoint Readpoint identifies the gln where the Euro Pallet is sent from. year= The year parameter is added to ensure the transactionid is unique. transactionid This is the id itself. If the NLP trace server is to be used for tracing, all of the parameters has to be included. If the customer offers its own trace service, at least the transactiontype and transactionid has to be present. If the customer offers its own trace server, other parameters may be added. o Receiving Returnable Transport Items (RTI) All pallet movement reporting to NLP is implemented according to the EPCIS standard (EPC Capture). An example of a Euro Pallet Received message is show below: <?xml version="1.0" encoding="utf-8" standalone="no"?> <epcis:epcisdocument xmlns:epcis="urn:epcglobal:epcis:xsd:1" xmlns:xsi=" creationdate="-03-10t21:30: :00" schemaversion="1.0"> <EPCISBody> <EventList> <QuantityEvent> <eventtime> t14:00:00</eventtime> <eventtimezoneoffset>+01:00</eventtimezoneoffset> <epcclass>urn:epc:id:grai: </epcclass> <quantity>24</quantity> <bizstep>urn:epcglobal:epcis:bizstep:fmcg:received</bizstep> <readpoint> <id>urn:epc:id:sgln: </id> </readpoint> <biztransactionlist> <biztransaction type="urn:nlpool:deliverynotenumber"> ;readpoint= &amp;year=&transactionid= <biztransaction type="urn:nlpool:consignmentid"> t= &year=&transactionid= <biztransaction type="urn:nlpool:ordernumber"> &year=&transactionid=

9 9 of 11 <biztransaction type="urn:nlpool:vendorordernumber"> point= &year=&transactionid= <biztransaction type="urn:nlpool:accountid"> &year=&transactionid=4321 </biztransactionlist> </QuantityEvent> </EventList> </EPCISBody> </epcis:epcisdocument> Feltnavn Beskrivelse QuantityEvent Se section eventtime og Se section eventtimezoneoffset epcclass Se section quantity Number of Euro Pallets received bizstep The bizstep value for Euro Pallets received shall be: readpoint biztransactionlist urn:epcglobal:epcis:bizstep:fmcg:received readpoint identifes the place where the Tag is being read, normally using a RFID reader. For Euro Pallets this will be the GLN of the receiving party. Se section for format description. Se section for format description. The message sent by the receiver must have exactly the same deliverynotenumber as the message sent by the sender. 7 SECURITY Authentication and authorization is defined in the EPCIS standard in the following sections: EPCIS Authentication and Authorization EPCIS Authentication EPCIS Authorization For the initial phase of the pilot there is no authentication. Software modules implemented for production should be prepared to use basic http authentication. There might also be other security mechanisms added before the production phase. 8 DATA EXCHANGE Epcis capture messages are transferred using xml over http as defined in the EPCIS standard. NLP supports xml over http as defined in the EPCIS standard, chapter 10 (Bindings for Core Capture Operations Module), section 10.2 (http Bindings). Section 10.2 from version 1_0_1 is quoted below:

10 10 of 11 START QUOTE: This section defines a binding of the Core Capture Operations Module to HTTP [RFC2616]. An EPCIS implementation MAY provide an HTTP binding of the Core Capture Operations Module in the following manner. For the purposes of this binding, a capture client is an EPCIS Capture Application that wishes to deliver an EPCIS event through the EPCIS Capture Interface, and a capture server is an EPCIS Repository or EPCIS Accessing Application that receives an event from a capture client. A capture server SHALL provide an HTTP URL through which a capture client may deliver one or more EPCIS events. A capture client SHALL exercise the capture operation defined in Section by invoking an HTTP POST operation on the URL provided by the capture server. The message payload SHALL be one of the following: an XML document whose root element conforms to the EPCISDocument element 2880 as defined by the schema of Section 9.5; or an XML document whose root element conforms to the EPCISQueryDocument 2882 element as defined by the schema of Section 11.1, where the element immediately nested within the EPCISBody element is a QueryResults element, and where the resultsbody element within the QueryResults element contains an EventList element. An implementation of the capture interface SHALL accept the EPCISDocument form and SHOULD accept the EPCISQueryDocument form. An implementation of the capture interface SHALL NOT accept documents that are not valid as defined above. Successful acceptance of this message by the server SHALL constitute capture of all EPCIS events included in the message. Status codes returned by the capture server SHALL conform to [RFC2616], Section 10. In particular, the capture server SHALL return status code 200 to indicate successful completion of the capture operation, and any status code 3xx, 4xx, or 5xx SHALL indicate that the capture operation was not successfully completed. END OF QUOTE The following address is used for capture messages: (use for testing). The capture interface returns an http status code. Status code 200 means that the message is received, and according to the latest version of the standard, status code 200 also implies that the schema is validated ok. This only means that the message is received by the NLP Epcis server. The messages will then be forwarded to the NLP logistics system wich will either accept the message as a transfer message, or discard the message with a failure code. 9 RESOURCES Here you will find tools and resources to start implementing your interface towards NLP.

11 11 of 11 Resource Location Description Accada EPCIS Capture Here you will find a java based epcis client that you can use to test EPCIS Client messages to the server. Accada EPCIS also has other RFID modules that Sending av EPCIS melding fra egen applikasjon ved bruk av open source kode fra ACCADA EPCIS you can test if you wish. You may use java code from Accada EPCIS to send Accada EPCIS messages from your own application as an alternative to developing your own code.