ISO IEC 19988-2015 Information technology - GS1 Core Business Vocabulary (CBV)《信息技术 GS1核心业务词汇 (CBV)》.pdf

《ISO IEC 19988-2015 Information technology - GS1 Core Business Vocabulary (CBV)《信息技术 GS1核心业务词汇 (CBV)》.pdf》由会员分享，可在线阅读，更多相关《ISO IEC 19988-2015 Information technology - GS1 Core Business Vocabulary (CBV)《信息技术 GS1核心业务词汇 (CBV)》.pdf（68页珍藏版）》请在麦多课文档分享上搜索。

1、Information technology GS1 Core business vocabulary (CBV)Technologies de linformation Vocabulaire relatif aux activits de base GS1INTERNATIONAL STANDARDISO/IEC19988Reference numberISO/IEC 19988:2015(E)First edition2015-rsw ISO/IEC 2015 ii ISO/IEC 2015 All rights reservedCOPYRIGHT PROTECTED DOCUMENT

2、ISO/IEC 2015, Published in Switzerland the requester. zvrs stsv vsttyvrsss vsttyvrvy 7www.iso.orgISO/IEC 19988:2015(E)ISO/IEC 19988:2015(E) ISO/IEC 2015 All rights reserved iiiForeword s s t 5 The committee responsible for this document is ISO/IEC JTC 1, Information technology.Core Business Vocabula

3、ryVersion 1.1, May-2014 All contents 20102014 GS1 Page 1 of 62GDSN Package Measurement Rules GS1 Standards DocumentVersion 1 13 2 Dec 2013Core Business Vocabulary (CBV) GS1 StandardVersion 1.1, May 20141 Core Business VocabularyVersion 1.1, May-2014 All contents 20102014 GS1 Page 2 of 62 20102014 GS

4、1 AISBLAll rights reserved. GS1 Global OfficeAvenue Louise 326, bte 10B-1050 Brussels, BelgiumDisclaimerGS1 AISBL (GS1) is providing this document as a free service to interested industries. This document was developed through a consensus process of interested parties in developing the Standard. Alt

5、hough efforts have been made to assure that the document is correct, reliable, and technically accurate, GS1 makes NO WARRANTY, EXPRESS OR IMPLIED, THAT THIS DOCUMENT IS CORRECT, WILL NOT REQUIRE MODIFICATION AS EXPERIENCE AND TECHNOLOGY DICTATE, OR WILL BE SUITABLE FOR ANY PURPOSE OR WORKABLE IN AN

6、Y APPLICATION, OR OTHERWISE. Use of this document is with the understanding that GS1 DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY IMPLIED WARRANTY OF NON-INFRINGEMENT OF PATENTS OR COPYRIGHTS, MERCHANTABILITY AND/OR FITNESS FOR A PARTICULAR PURPOSE, THAT THE INFORMA

7、TION IS ERROR FREE, NOR SHALL GS1 BE LIABLE FOR DAMAGES OF ANY KIND, INCLUDING DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR EXEMPLARY DAMAGES, ARISING OUT OF USE OR THE INABILITY TO USE INFORMATION CONTAINED HEREIN OR FROM ERRORS CONTAINED HEREIN.,62,( when these words appear in ordinary

8、typeface they are intended to have 335their ordinary English meaning.336All sections of this document, with the exception of Sections 1, 2, and 3, are normative, except 337where explicitly noted as non-normative. 338,62,( hence, assembling would be used in an Aggregation Event, not a Transformation

9、Event.xComputer parts (hard drive, battery, RAM) assembled into a consumer ready computerxHealthcare kitting: a surgical kit including drug, syringe, and gauze are combined to create a new product: a kit2Cnt2CntSyringeGauze2Cnt2CntSyringeGauzeBefore Kit with Serial Number (New Finished Good)Kit Seri

10、al Nbr: 1234566789,62,( subsequent events are likelyindicative of error (such as a stray read of a tag inside an incinerator). For a class level identifier, quantities are reduced; however, the class-level identifier may still be used in subsequent events (referring to different instances that were

11、not destroyed).xDistributor or Retailer puts empty case in the incinerator or box crusher.disassembling Denotes a specific activity within a business process where an object is broken down into separate, uniquely identified component parts.xBefore feeding a consumer electronics end of life item (a c

12、omputer) into recycling operation line, it is necessary to disassemble the parts for the purpose of being recycled or disposed of in an environmentally sound manner.xA surgical kit (e.g. 2- 50 count bottles of medication and 1 syringe gauze) is broken down into its separate component partsencoding P

13、rocess of writing an instance-level identifier (typically an EPC) to a bar code or RFID tag,where the identifier is not yet associated with an object at this step in the process.x3rd Party writes tags and returns spool of case tags to Manufacturerentering_exitingDenotes a specific activity at the En

14、trance/Exit door of a facilitywhere customers are either leaving with purchased product or entering with product to bereturned to the facility.xCustomer leaves the facility of Retailer X with their purchased items through a customer entrance/exit door.,62,( the output has a new identity and characte

15、ristics.This business step is deprecatedfor use with EPCIS 1.1. The EPCIS 1.1 standard has an event type, TransformationEvent,dedicated to transformations. The business steps commissioning,new_class_instance, or other business steps may be used with TransformationEvent. xMeat packer X cuts a whole c

16、ow into two sides of beef (1 to many)xFood processor Y combines water, vegetables, and meat to create a unit of soup (many to one)xButcher Z combines meat from multiple carcasses, grinds them together, and creates individual packages of ground beef (many to many)transporting Process of moving an obj

17、ect from one location to another using a vehicle (e.g., a ship, a train, a lorry, an aircraft). xCarrier X conveys 150 sea containers from Hong Kong seaport to Hamburg seaport with a container vessel.xA train with 20 goods wagons goes from one train station to another. xA lorry moves a swap trailer

18、from a depot to a distribution center.unloading Denotes a specific activity within a business process where an object is unloaded from a shipping conveyance.xManufacturer A unloads pallets from a shipping conveyance. The pallets are disaggregated from the shipping conveyance.xDistributor Y unloads r

19、acks full of totes from a truckunpacking Denotes a specific activity within a business process that includes removing products (individuals, inners, cases, pallets) from a larger container usually after receiving or accepting. Disaggregation of one unit from another typically occurs at this point. x

20、12 packs of soda are removed from a casexLoose potatoes are taken off from a tote.581 7.2 Dispositions582This section specifies standard identifier values for the EPCIS DispositionID vocabulary. 583These identifiers populate the disposition field in an EPCIS event, as specified below. 5847.2.1 URI S

21、tructure585All disposition values specified in this section have the following form:586urn:epcglobal:cbv:disp:payload587,62,(& ( ,62,(&$OOULJKWVUHVHUYHGCore Business VocabularyVersion 1.1, May-2014 All contents 20102014 GS1 Page 25 of 62where the payload part is a string as specified in the next sec

22、tion. Every payload string 588defined herein contains only lower case letters and the underscore character.5897.2.2 Element Values and Definitions Dispositions590Each EPCIS event in a CBV-Compliant Document MAY include a disposition field. If the 591disposition field is present, the value of the dis

23、position field SHALL be a URI 592consisting of the prefix urn:epcglobal:cbv:disp: followed by the string specified in the 593first column of some row of the table below. The portion following the prefix SHALL be written 594exactly as specified in the table below, in all lowercase letters (possibly i

24、ncluding underscores, as 595indicated).596Example (non-normative): the following shows an excerpt of a CBV-Compliant EPCIS 597document in XML format containing a single event, where the disposition of that event is the 598Core Business Vocabulary “in progress” value:599600601602603.604urn:epcglobal:

25、cbv:disp:in_progress 605.606607608609610The following example is NOT CBV-Compliant, because it does not use the full URI string in the 611disposition field. It is also not CBV-Compatible, because the value of the disposition field is not 612a URI with an owning authority, as required by Section 6.4

26、of EPCIS1.1. 613614615616617.618in_progress WRONG619.620621622623624Additional examples may found in Section 10.1.625Each EPCIS event in a CBV-Compatible Document MAY include a disposition field, and 626the value of the disposition field MAY be a URI as specified above for a CBV-Compliant 627documen

27、t, and MAY be any other URI that meets the general requirements specified in 628EPCIS1.1, Section 6.4, except for those URIs which in this standard are forbidden or 629designated for a different purpose. 630,62,(& ( ,62,(&$OOULJKWVUHVHUYHGCore Business VocabularyVersion 1.1, May-2014 All contents 20

28、102014 GS1 Page 26 of 62DispositionsValue Definition Examplesactive A commissioned object has just been introduced into the supply chain. xManufacturer A commissions tags for 10 cases of product. xA virtual document has been assigned an EPCBusiness step:commissioningcontainer_closedObject has been l

29、oaded onto a container, the doors have been closed and the shipment sealed.xContainer is being closed and will be awaiting pickup in the yard. xContainer is being closed and electronic seal is applied.Business step:staging_outbounddestroyed Object has been fully rendered non-usable. xIncinerator Ope

30、rator B indicates that product and packaging have been incineratedBusiness step:destroyingencoded An instance-level identifier hasbeen written to a bar code or RFID tag, but not yet commissioned. x3rd Party has written EPCs to tags and returns spool of case tags to ManufacturerBusiness step:encoding

31、inactive Decommissioned object that may be reintroduced to the supply chain. xA reusable tag is removed from a reusable transport item. xA digital coupon or an empties refund voucher has been redeemed at retail point-of-saleBusiness step:decommissioningin_progress Default disposition for object proc

32、eeding through points in the supply chain. xProduct arrives at a location and is being accepted and verified.xProduct is being prepared for shipment.Business step:receivingpickingloadingacceptingstaging_outboundarrivingin_transit Object being shipped between two trading partners. xShipper Z pulled a container/product out of a manufacturers yard on to a roadBusiness step:shippingdeparting,62,(& ( ,62,(&$OOULJKWVUHVHUYHG