CBV Ontology
type: Ontology
created: 2021-06-01
creator: GS1
modified: 2021-09-30
preferred namespace prefix: cbv
publisher: GS1
comment: The Comprehensive Business Vocabulary defines various enumerations used by EPCIS.
version info: 2.0

GS1
type: Organization
description: GS1 is an international organization that sets the global standards in transport and logistics

Business Transaction Type
type: Class
comment: These identifiers may be used to populate the type attribute of a bizTransaction element in an EPCIS event.
subclass of: TypeCode
term status: stable

Bill of Lading
type: Business Transaction Type
comment: A document issued by a carrier to a shipper, listing and acknowledging receipt of goods for transport and specifying terms of delivery.
term status: stable

Certificate
type: Business Transaction Type
comment: A document confirming certain characteristics of an object (e.g. product), person, or organisation, typically issued by a third party.
term status: stable

Despatch Advice
type: Business Transaction Type
comment: A document/message by means of which the seller or consignor informs the consignee about the despatch of goods. Also called an 'Advanced Shipment Notice', but the value `desadv` is always used regardless of local nomenclature.
term status: stable

Invoice
type: Business Transaction Type
comment: A document/message claiming payment for goods or services supplied under conditions agreed by the seller and buyer.
term status: stable

Pedigree
type: Business Transaction Type
comment: A record that traces the ownership or custody and transactions of a product as it moves among various trading partners.
term status: stable

Purchase Order
type: Business Transaction Type
comment: A document/message that specifies details for goods and services ordered under conditions agreed by the seller and buyer.
term status: stable

Purchase Order Confirmation
type: Business Transaction Type
comment: A document that provides confirmation from an external supplier to the request of a purchaser to deliver a specified quantity of material, or perform a specified service, at a specified price within a specified time. (Sometimes internally referred to as a 'Sales Order'.)
term status: stable

Production Order
type: Business Transaction Type
comment: An organisation-internal document or message issued by a producer that initiates a manufacturing process of goods.
term status: stable

Receiving Advice
type: Business Transaction Type
comment: A document/message that provides the receiver of the shipment the capability to inform the shipper of actual goods received, compared to what was advised as being sent.
term status: stable

Return Merchandise Authorisation
type: Business Transaction Type
comment: A document issued by the seller that authorises a buyer to return merchandise for credit determination.
term status: stable

Test Procedure
type: Business Transaction Type
comment: A document that provides a formal specification of a sequence of instructions for the purpose of verifying one or several criteria.
term status: stable

Test Result
type: Business Transaction Type
comment: A document that includes the outcome of the execution of a given test procedure.
term status: stable

Upstream EPCIS Event
type: Business Transaction Type
comment: Event ID URI(s) of event(s) provided by an upstream supplier, such as packing and shipping events (e.g., as the basis for the inferred completeness of inbound aggregations).
term status: stable

Business Step ID
type: Class
comment: These identifiers populate the bizStep field in an EPCIS event.
subclass of: TypeCode
term status: stable

accepting
type: Business Step ID
comment: Denotes a specific activity within a business process where an object changes possession and/or ownership.
example: Retailer X unloads a pallet on to the receiving dock. The numbers of cases on the pallet are counted. The pallets are disaggregated from the shipping conveyance. The quantity is verified against the delivery document (Freight Bill or Bill of Lading), notating any over, short or damaged product at the time of delivery. Typically this process releases freight payment and completes the contractual agreement with the carrier of delivering the product/assets to a specified location. A parcel carrier drops off five boxes at Distributor Y's DC. A person on the Receiving Dock signs that they accept the five boxes from the parcel carrier. A wholesaler is assigned a lot of fish at a fish auction, verifies the quantity and acknowledges receipt. A manufacturer's fork lift driver scans the IDs of components which have been removed from a consignment warehouse. In doing so, the components are added to the manufacturer's inventory.
term status: stable

arriving
type: Business Step ID
comment: Denotes a specific activity within a business process where an object arrives at a location.
example: Truckload of a shipment arrives into a yard. Shipment has not yet been received or accepted.
term status: stable

assembling
type: Business Step ID
comment: Denotes an activity within a business process whereby one or more objects are combined to create a new finished product. In contrast to transformation, in the output of `assembling` the original objects are still recognisable and/or the process is reversible; hence, `assembling` would be used preferably in an Association Event or, alternatively, an Aggregation Event, but not a Transformation Event.
example: Computer parts (hard drive, battery, RAM) assembled into a consumer ready computer Maintenance, repair and overhaul processes involving components added to an assembly comprised of multiple parts. Healthcare kitting: a surgical kit including drug, syringe, and gauze are combined to create a new 'product': a *kit*.
term status: stable

collecting
type: Business Step ID
comment: Denotes a specific activity within a business process where an object is picked up and collected for future disposal, recycling or re-used.
example: An organisation picks up disposed consumer electronics in an end of life state from various different organisations. After the goods are picked up, they typically are brought back and received into a Collection Centre Rented or leased pallets are picked up and brought to a collection centre.
term status: stable

commissioning
type: Business Step ID
comment: Process of associating an instance-level identifier (such as an EPC) with a specific object, or the process of associating a class-level identifier, not previously used, with one or more objects. A tag may have been encoded and applied in this step, or may have been previously encoded. `commissioning` is applied to this association of object and serialised identifier, regardless of industry/sector; it encompasses sector-specific process steps including, but not limited to: - catching (of fish), - harvesting (of fruit/vegetable), - picking (of fruit/vegetables), - producing (on an automated line), - slaughtering (of livestock). In the case of a class-level identifier, `commissioning` differs from `creating_class_instance` in that `commissioning` always indicates that this is the first use of the class-level identifier, whereas `creating_class_instance` does not specify whether the class-level identifier has been used before.
example: On a packaging line, an encoded EPC is applied to a case and associated to the product. An individual virtual document (e.g. digital coupon, digital voucher, etc.) is assigned an EPC. One hundred bottles of a particular batch of pharmaceutical product are produced, those being the first bottles of that batch to be produced. Sides of beef are transformed into individual packaged steaks. This may be an EPCIS 1.2 TransformationEvent if the input sides of beef are also tracked.
term status: stable

consigning
type: Business Step ID
comment: Indicates the overall process of `staging_outbound`, `loading`, `departing`, and `accepting`. It may be used when more granular process step information is unknown or inaccessible. The use of `consigning` is mutually exclusive from the use of `staging_outbound`, `loading`, `departing`, and `accepting`. Note: This business step is similar to `shipping`, but includes a change of possession and/or ownership at the outbound side.
example: A wholesaler comes aboard a fishing vessel, selects and buys boxes of fish, and brings them to his premises. A manufacturer retrieves components from a consignment warehouse for use in its assembly line. In the logical second of leaving the consignment warehouse, the components pass into the ownership of the manufacturer. A manufacturer stages products for loading, loads them into a container, the container is sealed, and the container departs. Ownership transfers to the receiver sometime during this overall process. If this is done in a single step, then business step `consigning` is used.
term status: stable

creating class instance
type: Business Step ID
comment: Denotes a step in a business process where an instance or increased quantity of a class-level identifier is produced. Unlike `commissioning`, this business step may be repeated for the same class-level identifier.
example: Water, sugar, and other ingredients are combined to produce a single batch of soda over a single shift on a single production line. This may be an EPCIS 1.2 `TransformationEvent` if the input ingredients are tracked. Potatoes are sorted by size and quality, washed, and packed into cases of a single lot in a single packaging facility on a single date.
term status: stable

cycle counting
type: Business Step ID
comment: Process of counting objects within a location in order to obtain an accurate inventory for business needs other than accounting purposes (e.g., replenishment and allocation).
example: A preselected subset of objects (for instance, all products belonging to a certain brand owner or a specific object class) within a retail store, are counted by a handheld reader. All objects of a specific sub-location (sales floor or a shelf on the sales floor, e.g.) are counted by a handheld reader.
term status: stable

decommissioning
type: Business Step ID
comment: Process of disassociating an instance-level identifier (such as an EPC) with an object. The object may be re-commissioned at some point in the future - however only with a new instance-level identifier.
example: An eSeal on a reusable container is broken when the container is opened, so that the container is no longer identified by the instance-level identifier that was in the eSeal. A digital coupon or an empties refund voucher is redeemed at retail point-of-sale.
term status: stable

departing
type: Business Step ID
comment: Denotes a specific activity within a business process where an object leaves a location on its way to a destination.
example: Truckload of a shipment departs a yard, typically through a gate and begins transit to another location.
term status: stable

destroying
type: Business Step ID
comment: Process of terminating an object. For an instance-level identifier, the object should not be the subject of subsequent events; subsequent events are likely indicative 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 not destroyed).
example: Distributor or Retailer puts empty case in the incinerator or box crusher.
term status: stable

disassembling
type: Business Step ID
comment: Denotes a specific activity within a business process where an object is broken down into separate, uniquely identified component parts.
example: Before feeding a consumer electronics end of life item (a computer) 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. A surgical kit (e.g. 2- 50 count bottles of medication and 1 syringe gauze) is broken down into its separate component parts.
term status: stable

dispensing
type: Business Step ID
comment: Denotes a specific activity within a business process where a product is made available in full or part to a consumer.
example: A pharmacist dispenses a pharmaceutical to fill a specific prescription written by a physician, to a consumer or patient. A deli manager slices a 5 pound package of turkey for sale.
term status: stable

encoding
type: Business Step ID
comment: Process of writing an instance-level identifier (typically an EPC) to a barcode or RFID tag, where the identifier is not yet associated with an object at this step in the process. Encoding SHOULD only be used in a `TransactionEvent`.
example: 3rd Party writes tags and returns spool of case tags to Manufacturer.
term status: stable

entering / exiting
type: Business Step ID
comment: Denotes a specific activity at the Entrance/Exit door of a facility where customers are either leaving with purchased product or entering with product to be returned to the facility.
example: Customer leaves the facility of Retailer X with their purchased items through a customer entrance/exit door.
term status: stable

holding
type: Business Step ID
comment: Denotes a specific activity within a business process where an object is segregated for further review.
example: Retailer X unloads a second pallet on to their receiving dock, and, finding no purchase order for the pallet, moves the pallet to a holding area on the dock. Distributor Y obtains a shipment of pharmaceutical product. Distributor Y finds that their supplier cannot provide a complete pedigree. Distributor Y moves the shipment to a quarantine area on their dock. Shipper Z is told by Customs to move a container to a special area until Customs can inspect and clear the container.
term status: stable

inspecting
type: Business Step ID
comment: Process of reviewing objects to address potential physical or documentation defects. In contrast to *sampled* objects, *inspected* objects **remain viable** in the supply chain. `inspecting` is non-destructive and typically only checks the plausibility of the product packaging, security devices (e.g. holograms, watermarks, etc.) and integrity of any tamper-evident seals, whereas `sampling` is always destructive, i.e., makes the sampled product instance no longer viable for sale or onward distribution in the retail/dispensing supply chain).
example: Manufacturer A pulls 10 bottles from every batch to ensure that the product and pill count in the bottles match expectations. Distributor Y checks all returned products to designate them either as saleable or as damaged. Regulator R pulls 3 bottles from a shelf to determine if the bottles have a correct pedigree. Customs Agent C uses a machine to scan the contents of a shipping container. Pallet pool operator Z checks if certain pallets comply with quality standards.
term status: stable

installing
type: Business Step ID
comment: Denotes a specific activity within a business process where an object is put into a composite object (not merely a container). In `installing` the composite object exists prior to this step, whereas in `assembling` the composite object is created during the step.
example: Additional memory chips and a rechargeable battery are installed within a computer A duplexing unit is installed on a laser printer Additional safety equipment is installed within the cabin of an aircraft or vehicle (e.g. fire extinguishers)
term status: stable

killing
type: Business Step ID
comment: Process of terminating an RFID tag previously associated with an object. The object and its instance-level identifier may continue to exist and be the subject of subsequent events (via a barcode, manual data entry, replacement tag, etc.).
example: Kill Command is issued to the tag to prevent any further reading of the tag or the information on the tag.
term status: stable

loading
type: Business Step ID
comment: Denotes a specific activity within a business process where an object is loaded into shipping conveyance.
example: Manufacturer A loads pallets into a container. The pallets are aggregated to the container. Distributor Y loads racks full of totes on to a truck.
term status: stable

other
type: Business Step ID
comment: A business step not identified by any of the values listed in the CBV.
example: `other` may be used for terms that have yet to be added to the CBV from an industry or a user.
term status: stable

packing
type: Business Step ID
comment: Denotes a specific activity within a business process that includes putting objects into a larger container - usually for shipping. Aggregation of one unit to another typically occurs at this point.
example: 12 packs of soda are placed into a case. Loose potatoes are placed into a tote.
term status: stable

picking
type: Business Step ID
comment: Denotes a specific activity within a business process that includes the selecting of objects to fill an order.
example: Distributor Y places three units into a tote to meet the requirements of a purchase order. Manufacturer A pulls three pallets from its racks to fulfil a purchase order.
term status: stable

receiving
type: Business Step ID
comment: Denotes a specific activity within a business process that indicates that an object is being received at a location and is added to the receiver's inventory. The use of `receiving` is mutually exclusive from the use of `arriving` and `accepting`.
example: Retailer X confirms that the count of cases on the pallet equals the expected count in a purchase order. Retailer X takes the cases into inventory. Typically, this process matches the product to the purchase order for payment to the supplier. A shipment from a manufacturer factory site to manufacturer distribution centre, is matched against the transaction record then added to local inventory.
term status: stable

removing
type: Business Step ID
comment: Denotes a specific activity within a business process where an object is taken out of a composite object. Opposite of `installing`.
example: A defective airplane part is taken out of the engine.
term status: stable

repackaging
type: Business Step ID
comment: Denotes a specific activity within a business process where an object's packaging configuration is changed.
example: Distributor Y receives one box full of batteries and another box full of laptops without batteries. Distributor Y ships out new boxes containing one laptop and one battery.
term status: stable

repairing
type: Business Step ID
comment: Denotes a specific activity within a business process where a malfunctioning product is repaired (typically by a post-sales service), without replacing it by a new one.
example: A computer is brought to a repair centre to fix a problem. An airplane part is in maintenance centre to diagnose an issue.
term status: stable

replacing
type: Business Step ID
comment: Denotes a specific activity within a business process where an object is substituted or exchanged for another object.
example: A defective airplane part is replaced by a new part.
term status: stable

reserving
type: Business Step ID
comment: Process in which a set of instance-level identifiers, not yet commissioned, are provided for use by another party.
example: Manufacturer provides set of case EPC numbers to a 3rd Party labeller.
term status: stable

retail selling
type: Business Step ID
comment: Denotes a specific activity within a business process at a point-of-sale for the purpose of transferring ownership to a customer in exchange for something of value (currency, credit, etc.).
example: Retailer X sells a screwdriver to a customer by checking it out through a point-of-sale system.
term status: stable

sampling
type: Business Step ID
comment: Denotes a testing activity within a business process where one or more portions of an object are examined for quality testing, quality inspection, or customs clearance purposes. In contrast to *inspected* objects, *sampled* objects are **no longer viable** in the supply chain. `inspecting` is non-destructive and typically only checks the plausibility of the product packaging, security devices (e.g. holograms, watermarks, etc.) and integrity of any tamper-evident seals, whereas `sampling` is always destructive, i.e., makes the sampled product instance no longer viable for sale or onward distribution in the retail/dispensing supply chain). When a serialised instance undergoes `sampling`, the subsequent business step SHALL be an end-of-life event (i.e., with action DELETE), to prevent the return of the sampled object (or its identifier) into the supply chain.
example: Customs authority X removes a pharmaceutical product from a case for quality testing at a customs office. Food laboratory Y pulls a random product sample and checks it for authenticity.
term status: stable

sensor reporting
type: Business Step ID
comment: Denotes a specific activity within a business process where sensor data, pertaining to the physical properties and condition of an object or location, is returned. If an EPCIS event accommodates sensor data in conjunction with specific business process steps (e.g. sensor observations in the context of a `commissioning`, `packing`, or `sampling`), the business step value describing the process step SHOULD be used. `sensor_reporting` SHOULD only be used when no other business step is in progress.
example: Several packages of frozen food are kept in cold storage, with temperature monitoring. An EPCIS event is triggered once a specific, pre-set temperature threshold is reached. A dust-free room is continuously checked for the presence of contaminants. An EPCIS event is captured at regular intervals for documentation purposes. A wine/cheese cellar is continuously checked for absolute humidity and temperature. Each time the door is opened or closed, an EPCIS event is captured, including the range of temperature and absolute humidity values within the period of time since the previously captured `commissioning` EPCIS event.
term status: stable

shipping
type: Business Step ID
comment: Indicates the overall process of `staging_outbound`, `loading` and `departing`. It may be used when more granular process step information is unknown or inaccessible. It may indicate a final event from a shipping point. The use of `shipping` is mutually exclusive from the use of `staging_outbound`, `departing`, or `loading`.
example: Manufacturer A loads and reads product into the shipping container and closes the door. The product has been read out of the shipping facility. The shipment is immediately picked up and a BOL is associated at this point. (The shipment has left the yard) At Distributor Y, the truck containing racks full of totes pulls away from the shipping dock or staging area. Manufacturer A completes loading product into trailer and seals door. The trailer is ready for pickup. The generation of a Despatch Advice / ASN triggers a `shipping` event. A 3PL picks and tags the product. The product is loaded into a trailer and signed over to a transportation carrier. The 3PL notifies the manufacturer who generates a `shipping` event. NOTE: This would be the case if there were NO departing step at a read point at the gate. Typical Process flow: - `staging_outbound` - `loading` - `departing` The above steps assume an organisation's ability and desire to share all steps in the process. If those process steps are not captured, the single business step of `shipping` would be used.
term status: stable

staging outbound
type: Business Step ID
comment: Denotes a specific activity within a business process in which an object moves from a facility to an area where it will await transport pick-up.
example: Container is being closed and will be subsequently loaded onto a vehicle in the yard. Container is being closed and seal is applied, and will be subsequently loaded onto a vehicle in the yard. Product has been picked and is now in a staging lane waiting for loading into a container.
term status: stable

stock taking
type: Business Step ID
comment: Process of counting objects within a location following established rules and/or standards to serve as a basis for accounting purposes.
example: All EPCs in a retail store are read by a handheld reader following a procedure accepted by the organisation’s accounting firm.
term status: stable

stocking
type: Business Step ID
comment: Denotes a specific activity within a business process within a location to make an object available to the customer or for order fulfilment within a DC.
example: Retailer X places cans from a case on to a shelf on the sales floor. Distributor X moves goods from a storage area to a picking area.
term status: stable

storing
type: Business Step ID
comment: Denotes a specific activity within a business process where an object is moved into and out of storage within a location.
example: Manufacturer A moves a pallet from the receiving area to a rack Retailer X moves a case from the receiving dock to a shelf in the backroom.
term status: stable

transporting
type: Business Step ID
comment: Process of moving an object from one location to another using a vehicle (e.g., a ship, a train, a lorry, an aircraft).
example: Carrier X conveys 150 sea containers from Hong Kong seaport to Hamburg seaport with a container vessel. A train with 20 goods wagons goes from one train station to another. A lorry moves a swap trailer from a depot to a distribution centre.
term status: stable

unloading
type: Business Step ID
comment: Denotes a specific activity within a business process where an object is unloaded from a shipping conveyance.
example: Manufacturer A unloads pallets from a shipping conveyance. The pallets are disaggregated from the shipping conveyance. Distributor Y unloads racks full of totes from a truck.
term status: stable

unpacking
type: Business Step ID
comment: 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.
example: 12 packs of soda are removed from a case. Loose potatoes are taken off from a tote.
term status: stable

void shipping
type: Business Step ID
comment: Denotes a process of declaring that one or more objects in a prior outbound process (captured in an EPCIS event having business step `shipping`, `departing`, or `consigning`) were not shipped (or departed or consigned) as previously indicated.
example: A sender cancels a shipment after a prior shipping event. A sender discovers, either by notification from a recipient or on their own, that a shipment they believed occurred and created a shipping event for, did not actually occur. The record is updated to reflect this. A sender discovers that three out of ten items, previously believed as having been shipped, were not included in the shipment. The `voidShipping` event indicates that those three items were not shipped.
term status: stable

Disposition ID
type: Class
comment: These identifiers populate the disposition field of an EPCIS event or the set / unset fields within the persistentDisposition field of an EPCIS event.
subclass of: TypeCode
term status: stable

active
type: Disposition ID
comment: A commissioned object has just been introduced into the supply chain.
example: Manufacturer A commissions tags for 10 cases of product. A virtual document has been assigned an EPC Business step: - `commissioning`
term status: stable

available
type: Disposition ID
comment: Object has been returned to service or to the supply chain (e.g., following a successfully completed `repairing` step).
example: A mechanical component has been serviced and made available for use.
term status: stable

completeness inferred
type: Disposition ID
comment: Applied as `persistentDisposition` of an `AggregationEvent` or `ObjectEvent` with action `OBSERVE` to indicate the **inferred** integrity of that aggregation (without unpacking the aggregated children from the parent) on the basis of aggregation information (e.g., earlier EPCIS packing event data and/or ASN/DESADV) provided by an upstream supplier. Inferred children SHALL be explicitly listed when captured in an `AggregationEvent`, but SHALL NOT be listed when captured in an `ObjectEvent`.
example: A downstream recipient *infers* that the contents of a shipment below the outer packing layer are complete, as indicated in EPCIS packing and shipping events provided by the upstream supplier.
term status: stable

completeness verified
type: Disposition ID
comment: Applied as `disposition` of an `AggregationEvent` with action `DELETE` and business step `unpacking` to explicitly indicate the verified integrity of that aggregation when the aggregated children are unpacked from their parent. Applied as `persistentDisposition` of an `ObjectEvent` with business step `inspecting`, if the inspection has verified the presence of each of the aggregated children.
example: A downstream recipient *verifies* that the contents of a shipment below the outer packing layer are complete, by means of unpacking and scanning the barcodes or EPC/RFID tags of the contents.
term status: stable

conformant
type: Disposition ID
comment: Outcome of a successful/passed inspection in an `inspecting` or `repairing` step.
example: A mechanical component has been successfully tested for conformity to safety or performance requirements.
term status: stable

container closed
type: Disposition ID
comment: Object has been loaded onto a container, the doors have been closed and the shipment sealed.
example: Container is being closed and will be awaiting pickup in the yard. Container is being closed and electronic seal is applied. Business step (non-exclusive example): - `staging_outbound`
term status: stable

container open
type: Disposition ID
comment: A container's doors have been opened; or a seal of a shipment has been broken. This disposition makes no indication as to whether the act of opening was authorised.
example: Container has been opened in the normal process of unloading. Container has been opened unexpectedly, with no apparent reason.
term status: stable

damaged
type: Disposition ID
comment: Object is impaired in its usefulness and/or reduced in value due to a defect.
example: Pallet pool operator P notices that a plank of a pallet is broken and records this incident by scanning the EPC of the pallet. Retailer R receives a shipment where the product packages on the pallet have been dented. Business steps: - `accepting` - `inspecting` - `receiving` - `removing` - `repairing` - `replacing` Note: `damaged` can also apply to non-apparent (physical) damage determined by means of sensor data. For example, product pH has dropped beyond a minimum acceptable threshold for viability.
term status: stable

destroyed
type: Disposition ID
comment: Object has been fully rendered non-usable.
example: Incinerator Operator B indicates that product and packaging have been incinerated. Business step: - `destroying`
term status: stable

dispensed
type: Disposition ID
comment: A full quantity of product is distributed to a consumer.
example: A pharmacist dispenses a pharmaceutical in a container’s totality to fill a specific prescription written by a physician, to a consumer or patient. A deli manager slices the complete contents of a 5 pound package of turkey for sale. NOTE: this disposition reflects the disposition of the original object, not what was dispensed.
term status: stable

disposed
type: Disposition ID
comment: Object has been returned for disposal.
example: A package of pharmaceuticals has been picked up by a distributor and will be subsequently destroyed.
term status: stable

encoded
type: Disposition ID
comment: An instance-level identifier has been written to a barcode or RFID tag, but not yet commissioned.
example: 3rd Party has written EPCs to tags and returns spool of case tags to Manufacturer. Business step: - `encoding`
term status: stable

expired
type: Disposition ID
comment: Object's expiration date is in the past.
example: Distributor Y indicates that a product is past its expiration date Business step (examples): - `holding` - `staging_outbound` - `storing`
term status: stable

in progress
type: Disposition ID
comment: Optional disposition for object proceeding through points in the supply chain.
example: Note: *Omission* of disposition is generally recommended instead of `in_progress`, which adds little value to event data.
term status: stable

in transit
type: Disposition ID
comment: Object being shipped between two trading partners.
example: Shipper Z pulled a container/product out of a manufacturer’s yard on to a road. Business step: - `shipping` - `departing`
term status: stable

inactive
type: Disposition ID
comment: Decommissioned object that may be reintroduced to the supply chain.
example: A reusable tag is removed from a reusable transport item. A digital coupon or an empties refund voucher has been redeemed at retail point-of-sale. Business step: - `decommissioning`
term status: stable

mismatch class
type: Disposition ID
comment: Class-level identifiers do not correspond to the identifiers that were expected.
example: Recipient unpacks 10 of expected 10, but GTINs do not match data communicated via the EPCIS Packing event provided by the supplier. Note: It is recommended to capture all `mismatch_` dispositions as persistentDisposition.
term status: stable

mismatch instance
type: Disposition ID
comment: Instance-level identifiers do not correspond to the identifiers that were expected.
example: Recipient unpacks 10 of expected 10, but SGTINs do not match data communicated via the EPCIS Packing event provided by the supplier. Note: It is recommended to capture all `mismatch_` dispositions as persistentDisposition.
term status: stable

mismatch quantity
type: Disposition ID
comment: Quantity do not correspond to the quantity that was expected.
example: Recipient unpacks 9 of expected 10 (an 'underage'), or 11 of expected 10 (an 'overage'). Note: It is recommended to capture all `mismatch_` dispositions as persistentDisposition.
term status: stable

needs replacement
type: Disposition ID
comment: Component(s) or other asset(s) must be replaced to ensure fulfilment of functional requirements.
example: An assembly component's service duration has exceeded its (theoretical, e.g., per EN 50126) mean time to failure, and is marked as needing replacement.
term status: stable

no pedigree match
type: Disposition ID
comment: In validating the pedigree for the object, no match was found, causing the product to be quarantined for further investigation and disposition.
example: Distributor Y could not obtain a valid pedigree for a product from its Manufacturer A Business step: - `holding` - `staging_outbound` - `storing`
term status: stable

non conformant
type: Disposition ID
comment: Outcome of an unsuccessful/failed inspection in an `inspecting` or `repairing` step. (`non_conformant` is the opposite of `available`).
example: A mechanical component has been failed conformity testing against safety or performance requirements. If disposition is `non_conformant``, follow up steps may be used to capture subsequent and/or final disposition. For example, if the `non_conformant` object is not usable, it might be moved to a separate location for storage. If the object is still installed in an assembly but not function-critical, the assembly might be allowed to continue running until the next repair cycle; alternatively, a disassembly event might follow.
term status: stable

non sellable other
type: Disposition ID
comment: Object cannot be sold to a customer.
example: A product is not sellable pending further evaluation. A product is not sellable, and one of the other dispositions (`expired`, `recalled`, `damaged`, `no_pedigree_match`) does not apply. Product has been sold and is awaiting customer pick-up. Business step: - `holding` - `inspecting` - `staging_outbound` - `storing`
term status: stable

partially dispensed
type: Disposition ID
comment: A portion of a product is distributed to a customer, while additional product is retained for subsequent distribution.
example: A pharmacist dispenses 10 pills from a 100-count bottle to fill a customer prescription. A deli manager slides and packages one pound of a 10 pound ham for customer purchase. NOTE: This disposition reflects the disposition of the original object, not what was dispensed.
term status: stable

recalled
type: Disposition ID
comment: Object is non-sellable because of public safety reasons.
example: Manufacturer A requested that all Retailers and Distributors return its batteries that could overheat and explode. Business step: - `holding` - `staging_outbound` - `storing`
term status: stable

reserved
type: Disposition ID
comment: Instance-level identifier has been allocated for a third party.
example: Distributor receives EPC numbers and can encode tag with the numbers. Business step: - `reserving`
term status: stable

retail sold
type: Disposition ID
comment: Product has been purchased by a customer.
example: A customer at Retailer X purchased a screwdriver by checking it out through the point of sale system. Business step: - `retail_selling`
term status: stable

returned
type: Disposition ID
comment: Object has been sent or brought back for various reasons. It may or may not be sellable.
example: Product is received at a returns centre from a customer because of an over-shipment, recall, expired product, etc. Product is returned to retail POS by a customer, who no longer wants the product. Business step: - `receiving` - `holding` - `shipping`
term status: stable

sellable accessible
type: Disposition ID
comment: Product can be sold as is and customer can access product for purchase.
example: Retailer X puts a case of screwdrivers on to a shelf or display within customer reach. Business step: - `stocking` - `receiving`
term status: stable

sellable not accessible
type: Disposition ID
comment: Product can be sold as is, but customer cannot access product for purchase.
example: Retailer X puts a case of screwdrivers on to a shelf in a store backroom. Business step: - `receiving` - `storing` - `loading` - `holding` - `inspecting`
term status: stable

stolen
type: Disposition ID
comment: An object has been taken without permission or right.
example: A pharmaceutical manufacturer completes an investigation of serial numbers that are missing from inventory, and concludes that they have been stolen.
term status: stable

unavailable
type: Disposition ID
comment: Object has been removed from service or from the supply chain (e.g., pending repair).
example: A mechanical component in need of maintenance is taken out of service.
term status: stable

unknown
type: Disposition ID
comment: An object's condition is not known.
term status: stable

Error Reason
type: Class
comment: These identifiers may be used to populate the reason attribute of an errorDeclaration element in an EPCIS event.
subclass of: TypeCode
term status: stable

did not occur
type: Error Reason
comment: The prior event is considered erroneous because it did not actually occur. There are no corrective events. (In a CBV-Compliant Document, this error reason SHALL NOT be used in an error declaration that contains one or more corrective event IDs.)
term status: stable

incorrect data
type: Error Reason
comment: The prior event is considered erroneous because some or all of the data in the event are incorrect. Subsequent events may provide a correct indication of what actually occurred when the prior event was captured. These events may be linked using the corrective event IDs in the error declaration.
term status: stable

Source/Destination Type
type: Class
comment: These identifiers may be used to populate the type attribute of a source or destination element in an EPCIS event.
subclass of: TypeCode
term status: stable

location
type: Source/Destination Type
comment: The source or destination identifier denotes the physical location of the originating endpoint or terminating endpoint (respectively) of the business transfer of which this EPCIS event is a part. When a source of this type is specified on an EPCIS event at the originating endpoint of a business transfer, the source identifier SHOULD be consistent with the Read Point specified in that event. When a destination of this type is specified on an EPCIS event at the terminating endpoint of a business transfer, the destination identifier SHOULD be consistent with the Read Point specified in that event.
term status: stable

owning party
type: Source/Destination Type
comment: The source or destination identifier denotes the party who owns (or is intended to own) the objects at the originating endpoint or terminating endpoint (respectively) of the business transfer of which this EPCIS event is a part.
term status: stable

possessing party
type: Source/Destination Type
comment: The source or destination identifier denotes the party who has (or is intended to have) physical possession of the objects at the originating endpoint or terminating endpoint (respectively) of the business transfer of which this EPCIS event is a part.
term status: stable

Component
type: Class
comment: These identifiers may be used to populate the type attribute of a component element in the SensorReport of an EPCIS event.
subclass of: TypeCode
term status: stable

x coordinate
type: Component
comment: Component or projection along the x axis in Cartesian coordinates (X,Y,Z)
term status: stable

y coordinate
type: Component
comment: Component or projection along the y axis in Cartesian coordinates (X,Y,Z)
term status: stable

z coordinate
type: Component
comment: Component or projection along the z axis in Cartesian coordinates (X,Y,Z)
term status: stable

axial distance
type: Component
comment: Radial distance from the cylindrical axis in a cylindrical polar coordinate system; the magnitude of the projection of the vector in the plane perpendicular to the cylindrical axis
term status: stable

azimuth
type: Component
comment: Angle measured in the XY plane, anticlockwise from the X axis (in cylindrical or spherical polar coordinate systems) to the plane containing the vector and the Z axis
term status: stable

height
type: Component
comment: Height parallel to the cylindrical axis in a cylindrical polar coordinate system, above a defined reference origin plane (typically the XY plane)
term status: stable

spherical radius
type: Component
comment: Radial distance from the centre of a sphere in a spherical polar coordinate system; the magnitude of the vector
term status: stable

polar angle
type: Component
comment: Angle measured from the Z axis to the vector in a spherical polar coordinate system
term status: stable

elevation angle
type: Component
comment: Angle measured from the XY plane to the vector in a spherical polar coordinate system
term status: stable

easting
type: Component
comment: A component or projection along an east-pointing axis in a geographic Cartesian coordinate system
term status: stable

northing
type: Component
comment: A component or projection along a north-pointing axis in a geographic Cartesian coordinate system
term status: stable

latitude
type: Component
comment: The angle of elevation from the equatorial plane in a geographic coordinate system
term status: stable

longitude
type: Component
comment: The angle (measured within the equatorial plane) to the east of the prime meridian in a geographic coordinate system
term status: stable

altitude
type: Component
comment: The height above a defined surface (such as mean sea level) in a geographic coordinate system
term status: stable