Method for transporting physical objects, transportation system and transportation means

Information

  • Patent Application
  • 20080040182
  • Publication Number
    20080040182
  • Date Filed
    March 06, 2007
    18 years ago
  • Date Published
    February 14, 2008
    17 years ago
Abstract
The invention relates to a method for transporting physical objects, wherein at least one physical object is transported from a sending station to a receiving station, wherein the transport occurs through at least one physical router, wherein the physical router executes a decision about further parameters of transport to another physical router or to the receiving station.
Description

BRIEF DESCRIPTION OF THE DRAWINGS

In the following advantageous implementations of the invention will be further described by means of examples and by means of the figures:



FIG. 1 shows a system overview of a platform based implementation of the invention.



FIG. 2 shows a functional view of implementations according to a preferred embodiment of the invention.



FIG. 3 shows advantageous databases for carrying out the invention.



FIG. 4 shows a preferred import of files and tables in a system according to the invention.



FIG. 5 shows a schematic representation of a preferred embodiment of modules for performing calculation processes.



FIG. 6 shows a schematic overview of an operation process map with fore process groups for an advantageous implementation of the invention.



FIG. 7
a and FIG. 7b depict an Operation Process Map



FIG. 8 shows an example for the use of legs in the emission calculation.



FIG. 9 shows a formula for the calculation of carbon emissions for each leg.



FIG. 10 shows a schematic representation of data flows for emission calculating according to a preferred embodiment of the invention.



FIG. 11 shows a model of a transport process according to the invention.



FIG. 12 shows a schematic representation, how transactions from different operational systems are managed via a defined interface, where the transactions are verified before they are entered in to the database.



FIG. 13 shows a schematic representation, how the Air transactions from the production system are managed.



FIG. 14 shows an advantageous process chart for accounting carbon credits in the carbon supply ledger





DETAILED DESCRIPTION OF SPECIFIC EMBODIMENTS


FIG. 1 shows a preferred system overview 100.


The embodiment according to FIG. 1 contains four basic modules: a data-gathering module 102, an updating/calculating module 104, a storing module 106 and a retrieving/reporting module 108.


It is advantageous to perform a gathering of environmental data, especially of environmental performance data and—resulting—environmental impact data for different carriers.


The described example contains the names of several existing and operating transportation and logistic companies like DHL Express and DHL Danzas Air and Ocean. Examples of information technology production systems are: Rasti, NPS, +2000, Exact, LOGIS R and LOGIS C.


These names are only used to show, that the invention can be carried out with different carriers. The names of the carriers do not limit the scope of the invention. It is possible to carry out the invention in any transportation system, respectively any information technology production system.


The gathered data are transferred to module 104 for updating and/or calculating the environmental data.


A calculation is performed with regard to respective parameters.


The updated and/or calculated data are transferred to a storing module 106.


The storing module can be implemented in different configurations.


The depicted Implementation shows a preparation of an emission report 110 according to the stored data.


This implementation is especially advantageous to inform users of the transport system about the environmental impact of transport.


However it is also possible to use the stored data for one or more of the described routing and/or transportation processes.


Therefore, it is especially advantageous to implement at least a part of the stored environmental data in a logical node or a computer connected to a physical router.


It is even more preferred to use the stored data for the routing and/or transport as well as for the retrieving and/or report as it is described in the right part of FIG. 1.


The data retrieving and/or report allow reports for each transport process as well as periodic reports 112. The reports can be analyzed according to one or more of the following categories: Client, customer id, transportation (e.g. km, ton, tonkm), country, period of time, different emissions, energy use or shipment.


Especially advantageous is a flexible report out take with parameters chosen individually. Examples could be for specific relations, listing of euro classes of transportation means.


Within preferred embodiments the environmental data are incorporated into the routing mechanisms in order to make the corresponding routing decisions. Furthermore, a mechanism is advantageous to be able to track the packages.


A transport system like a mail delivery system can use the environmental data to internally sort and distribute letters and packages to the correct truck for delivery. The size, due date etc. of each letter and package are determined.


Furthermore, an appropriate truck is identified by comparison between ecological requirements of the transport and environmental performance data of the truck.


Alternatively another preferred embodiment of the invention includes flexible mechanisms meaning that we promise to some where in the transport system to transport the agreed transport volume. This might change if alternative fuels and trucks are capable of using them are easily available.


Information about the environmental requirement data is used to accompany the letter and package and to deliver the package to the correct destination. It is also possible to add environmental requirement data to each letter and package. However, in this case scanners are needed.


Externally the same mechanisms may apply. Whereas the letters and the packages are distributed via other networks, the environmental requirement data may accompany the letters and packages via any appropriate communication network as for example the Internet. This environmental requirement data is then used to make routing decisions.


A further implementation of the invention relates to a computer integrated manufacturing company. In a computer integrated manufacturing company the routing of construction parts and tools may be done with regard to environmental requirement data and/or environmental performance data.


Once the size, the due date/time, the environmental impact data and the destination are determined, a communication packet that takes care of the routing accompanies the construction parts and tools.


Weighted fair queuing may be used to speed up and delay at least one leg of transport process.


Through flow control mechanisms it is possible to adapt parameters, especially transport capacities of the transportation system to the need of the users.


If the goods can be separated, segmentation and from time to time a reassembly may be executed. The segmentation is for example performed at the sending station or at one or more of the mechanical routers.


The different packages which are transported have different sizes, masses and should meet different needs. The different needs are most preferably reflected in special Quality Of Services (QOS) mechanisms. QOS specifications are for example environmental performance data of the transport means, and/or a fast or a secure delivery. Most preferably the QOS specifications are categorised, for example according to special categories, which represent for example goods which have to be handled according to specific environmental requirement data.


The environmental requirement data are an example of especially advantageous quality of service specifications.


However it is possible that further aspects are used for the quality of service, for example a desired speed of transport.


Though the invention can be carried out without usage of protocols some implementations of the invention can be further improved by implementing protocol mechanisms.


The protocol mechanisms can be used to do traffic management. For example in case of congestion, a routing protocol could determine, especially in real-time, a different route and router the car by sending signals to the receiver in the car. An interface from the router to a traffic control system is used.


In the following the invention will be described by different concepts with different connections between actual machines and routing network.


The environmental data according to the invention especially the environmental impact data, the environmental requirement data and the environmental performance data can be implemented in various ways into the transportation procedure.


As described it is especially advantageous to implement environmental data into the routing of the objects. However it is as well possible to use the environmental data for planning the transport process and/or for calculating the environmental impact of a certain transport.


It is especially advantageous to include environmental data into the route planning tools is especially advantageous for a comparison between different modes of transports or linked to geographical restrictions/concerns e.g. in especially polluted areas.


For example it is possible to perform routing processes to guaranty that a certain environmental quality is maintained.


For example it is possible to perform the routing in a way that the transport processes fulfill certain criteria.


Such criteria can be derived from customer based directives and/or directives implemented by law and/or official actions.


For example the routing processes are fulfilled in a way that the following directives of the European Union are fulfilled:

    • 1. Framework Directive 96/62/EC on ambient air quality assessment and management.
    • 2. first Daughter Directive (1999/30/EC) relating to limit values for NOx, SO2, Pb and PM10 in ambient air.
    • 3. second Daughter Directive (2000/69/EC) relating to limit values for benzene and carbon monoxide in ambient air.
    • 4. third Daughter Directive relating to ozone.


If the route planning concerns one mode only e.g. truck transports, its' objective goes hand in hand with environmental concern. Higher efficiency means lower environmental impact per shipment.


It is possible to use more centralized implementations of the inventions.


More centralized versions of the invention include central planning and/or stearing of transport and/or calculation procedures.


However it is also advantageous to use decentralized implementations of the invention.


Such decentralized implementations of the invention can for example be carried out in the following way:


The invention especially covers the following embodiments:

    • separating the goods flow of ordinary shipments and environmentally friendly shipments. This requires an at least partly parallel system.
    • Implementing “green shipments” which build on flexibility that is the shipment itself may be transported using ordinary routines but somewhere in the transport system a corresponding volume is transported in a “green way”.


Environmental requirement data accompany the physical objects. This is for example possible by adding digital information to the physical objects, for example by printing codes and/or writing information to transponders.


The physical routers are connected to a database which contains environmental performance data of transport means which are accessible by the routers.


Examples for different transport means for one router are different trucks that operate from a cargo center.


Examples for accompanying the physical packages with logical packets are labels or transponders attached to the physical objects.


The labels and/or the transponders may contain a various data suitable for logistic processes.


Examples for these data are identification information about the physical object, a delivery address, a sender address and charging relevant information as for example digital franking marks.


Especially advantageous implementations of the current invention propose to add to this data environmental data, for example environmental impact data and/or environmental requirement data.


Whenever a physical object is received in a router, the router informs the machine on what to do and waits for a confirmation that the actions have been executed.


The embodiments described above can be combined with each other or with any of the embodiments described before.


The described examples of transportation systems that are designed and/or operated according to the invention show that the invention can easily be adapted to other transportation systems. Therefore the invention is not limited to a special transportation system.


The invention furthermore relates to methods for processing postal deliveries as letters, parcels and packets, transport pallets or transport containers.


A preferred embodiment of the invention involves a detection of information present on at least one surface of the physical object in such a way that, on the basis of the information present on the surface of the physical object, environmental data, for example environmental requirement data is used for the routing and/or for analysis and/or representation and/or for a compensation by transporting a corresponding volume in a “green way” that means with less impact on the environment.


An example of the implementation of the environmental data is a direct printing on the physical object. However, it is also possible to first print a medium, for example, a label, and to subsequently apply it onto the physical object.


This is advantageous to increase customer satisfaction and realization of the green shipment. It is possible but not necessary to use the environmental data for any sort of sorting or routing purposes.


The neutralization of the emission will in one advantageous implementation be done through compensation rather than reduction at the source. This is especially useful for air shipments where at the moment no alternative fuels are available.


The term “environmental data” is by no means to be understood in a limiting fashion and especially comprises all depictions of data in an optically recognizable and/or machine-readable form that can be used for sorting, transporting or delivering the physical object.


An especially advantageous embodiment of the method is characterized in that the physical objects are processed within the scope of a two-stage process, whereby the physical objects are already completely coded in the source region and undergo preliminary sorting according to target regions in a first sorting step.


In an advantageous embodiment the physical objects undergo fine sorting into smaller units in another sorting procedure.


Moreover, it is advantageous for the environmental data, for example the environmental requirement data, to be applied onto the physical object as a barcode.


In any case it is simultaneously appropriate to include the environmental data, for example the environmental requirement data in a transponder which is attached to the physical objects or a transport unit containing the physical objects.


The coding, or the labelling, is preceded by determination of the environmental requirements in which the environmental impact data are found on the basis of the recognizable environmental performance data by means of linked files from the data, including a conversion file.


The invention also comprises a device for processing physical objects.


Additional advantages, special features and practical refinements of the invention ensue from the sub claims and from the following presentation of preferred embodiments of the invention making reference to the drawings.


Afterwards an especially advantageous implementation of the invention is described as an ACCEPT-Implementation.


The preferred ACCEPT-Implementation includes an Automatic Customer Calculation of Environmental Performance Tool.


The idea of ACCEPT is to produce Emission reports for customers and operators. Those reports will describe the amount of Emissions a specific customer's shipment has produced for a specific period.


In order to facilitate the explanation of the ACCEPT-Implementation of the invention the following definitions are used:


Definitions
















Term
Explanation









ACCEPT
System used to calculate emission values,




especially a database which contains




Shipments, Transports, Emissions,




Customer information and Distances




for all source systems and all




periods.



FuelMixID
The definition of a specific usable




mix of ingredients used by a vehicle



ProductID
The ID for a Shipments Product. Ex




Stycke, Parti, Exact.



T-Web
Transporters-Web, external system for




handling operators and vehicles



Volume Weight
The weight for a shipment



City-to-city
City-to-city, postal code-to-postal




code, Air terminal-to-air terminal or




any combination



VehicleType
A type of vehicle used when we don't




know which in divide that was transporting




the shipment.



Operator
The organization or company that is




transporting the shipment.



Node
One point to calculate a distance




from.



Leg
A distance between two Nodes.



CoSP
One of the Shipment data providers




used for ACCEPT.



EmissionValue
The amount of an emission of a specific




type that is produced when a




specific amount of a specific FuelMix




is consumed.



Shipment
the total transportation service




bought by the customer, the transportation




of goods from location A to location B



Transport
the transport work done by a vehicle




used for one leg in the shipment.



Leg
the smallest part of the shipment in




the transport chain, the part where




the same vehicle has the transported




gods as its load, e.g. between two




terminals



Vehicle
the means of transportation used, e.g.




air plane, lorry, distribution van




etc.



Parcel
the smallest defined part of the total




shipment bought by the customer



Super user
An internal user with better access to




the functions within the system and




who should function as 1:st line support




for all users, within a country.



Internal User
DHL user who not is a Super user, limiting




the access rights in ACCEPT



External User
Any user who is not Super user or Internal




user, further limiting the access




rights in ACCEPT



Volume Weight
A calculation of the “cost” in the




transport chain for this shipment from




the customer. The value is a combination




of the weight and the volume and




is also used for setting the price to




the customer.



Max Load
The maximum weight carried by a vehicle,



Weight
used together with Volume Weight




to define the shipments part of the




available capacity.



Fill Factor
A value defining to what extent the




available capacity is used, also




called Utilization Factor. Given as a




percentage of the total capacity e.g.




74% fill factor declares that the vehicle




is 26% empty.



Fixed Emission
In some calculations e.g. calculation



Value
Air emissions, there is a fixed emission




value independent of the distance




e.g. take off and landing.



Variable
In all calculations, there is an emission



Emission
value totally depending of the



Value
distance.



Distance
The amount of kilometers the shipment




is transported.



Fuel Consumption
The amount of fuel used per distance




unit, normally liters per kilometer.




Used for calculating the base fuel




consumption for a shipment.



Utilization
see Fill Factor.



Factor










The ACCEPT system is for example useful to calculate emissions for shipments. The calculation is performed, in brief by multiplying the distance, weight and the emission values for a specific engine model. One instance of ACCEPT is meant to serve one country's all shipments, domestic, international, air and so on.


Distance Calculations

The system calculates the distance for a shipment in different ways:

    • 1. City-to-city distance.
    • 2. Terminal distance plus pickup and distribution distances.


The method to use is chosen by the ProductID term in the Shipment.


The fuel consumption, max load weight and fill factor for a vehicle and operator is imported from an external system, which is for example called T-Web, or set to a default value defined by ACCEPT. The fuel consumption for a specific shipment can be set in one of three values.













Quality level
Description







Vehicle-fuel consumption,
If we know which vehicle that transported


max load
the shipment and the vehicle is


weight, fill factor
registered in T-Web then use data from


and engine model
the vehicle


Operator-fuel consumption,
If we know which operator that transported


max load
the shipment and the vehicle is


weight, fill factor
registered in T-Web then use data from


and engine model
the operator


Vehicle type-fuel
If we do not know, vehicle nor operators


consumption, max load
then use data from a default vehicle


weight, fill factor
type. This type depends on which type of


and engine model
transport that is performed, e g city-



to-city, terminal, distribution or



pickup









Emission Calculations

This section describes the different ways to calculate emissions for shipments.


Exact




Factor=VolumeWeight/(MaxLoadWeight*FillFactor)





TransportEmission=FuelConsumption*LegDistance*EmissionValue*Factor





ShipmentEmission=TransportEmission+n1


Stycke, Parti, Air Express and International




Factor=VolumeWeight/(MaxLoadWeight*FillFactor)





TransportEmission=FuelConsumption*City-to-city-distance*EmissionValue*Factor





ShipmentEmission=TransportEmission


This embodiment relates in general to the field of transport routing system. More particularly, this aspect of the invention relates to an extensible model system architecture for integrated material and environmental data planning, and integrated transport and distribution planning.


Manufacturers and distributors commit to time critical transport and delivery of goods as a regular part of their operation. Often, the transport and distribution transport is complex, having many different material and environmental data constraints that simultaneously affect the implementation of the transport.


Due to the complexity of the transports, many different software tools have been developed to implement environmental data.


This preferred aspect of the invention provides an extensible model architecture for a transport routing system that allows an implementation of environmental data in the transport process.


More particularly, in one embodiment, the present invention provides a computer central control computer for modeling a transport capability on a computer. The central control computer is programmed with software and comprises an operation model type for defining a plurality of operation models. Each operation model represents activities that relate to the transport of the physical objects.


A resource model type is used for defining a plurality of resource models. Each resource model represents environmental data available for use in performing an activity and rules for allocating environmental data to the activity. An environmental data type is for defining a plurality of environmental data sets. Each environmental data represents rules for controlling a transport route of material between locations.


The operation model type, environmental data type, and resource model type each comprise a plurality of fields defining attributes. The plurality of fields includes a plurality of extension selector fields that each allows a user to specify one of a plurality of extensions that augment a model with additional fields and semantics. The model type specifies a base set of fields and semantics which includes fields that select extensions that specify additional fields and semantics that can be added to a particular model.


These measures allow handling different environmental data.


Examples for the environmental data are environmental requirement data, environmental performance data and environmental impact data.


The term environmental data is used for each of these types of data.


The environmental requirement data are data concerning and/or implementing desired or required economic standards.


The environmental requirement data are for example: Requirements concerning a desired level of emissions and/or another influence on the environment.


These data can be related to different aspects of transport.


For example it is possible to define that a single transport has to be emission neutral or that all transports of a customer together has to be emission neutral, or that a certain level of air or water quality is maintained in a place, a city, a region, a country or in total.


Environmental performance data describe the ability of a means to perform a task in relation to an environmental impact. An example for this is the capability of a truck to transport a certain amount of physical objects with specific parameters—especially weight and size—with a certain emission. For example the relation between ton, kilometers and carbon dioxide emissions. The invention further includes means with a positive effect of the environment, especially devices for reducing the content of hazards components in the air.


The invention proposes a complex database with knowledge information about interdependencies between different parameters and therefore allows to minimize an effect to the environment.


The invention allows to handle this with a multiparameter approach with detailed information about the ecological efficiency of transport means and parameters to influence this ecological influence, for example by using biofuel.


The presence of a field in a model is preferably dependent upon a value of another field in the model. Defined operation models, environmental data, and resource models are stored as nodes in an interrelated transport network model. The transport network model is formed by a plurality of operation models each specifying environmental data from which material is transported and environmental data to which a physical object is transported and specifying resource models having environmental data used in performing the activity specified by the operation model. In this manner, both transport and environmental data usage are simultaneously represented along with timing constraints between activities. According to the present invention, to model a plan for a transport, a plan network model is constructed upon the transport network model. An operation-plan model type is used to define a plurality of operation-plan models. Each operation-plan model represents a plan for performing an activity represented by an operation model. A resource-plan model type is used to define a plurality of resource-plan models. Each resource-plan model represents a planned usage of environmental data represented by a resource model.


In one preferred embodiment an operation-plan model type is used to define a plurality of operation-plan models. Each operation-plan model represents a planned transport route of a physical object represented by an environmental data element. A plan network model is formed by a plurality of operation-plan models each specifying resource-plan models planned to be used in performing the activity specified by the operation-plan. The nodes of the plan network model are built upon and refer to the nodes of the transport network model. According to the present invention, the transport network model represents possibilities of what can be done, and the plan network model represents that which is planned to be done. According to one aspect of the present invention, each model type has one or more extension points that may be used to extend the basic model type in order to support the information needed to create the user defined models. For each extension point, a user may select an appropriate extension to model a particular aspect of the user's system. According to another aspect of the present invention, several elements of a user's transport model may share data in a hierarchical fashion referred to as families.


One model inherits all of the data of the parent model unless it is specifically overridden by a designation in the model. A central control computer implementing the teachings of the present invention may provide for date affectivity of models using the families feature. It is a technical advantage of the present invention to use extensions to define the elements of the transport or system being modeled because it reduces the amount of data that needs to be stored in a memory device without reducing modeling power. According to the teachings of the present invention, data for each element of the modeled transport is stored at a node of a user model or transport network model. The data stored at a node comprises only the data for the fields corresponding to the extensions that are selected by the user. The system does not store a zero quantity for each 60 field not chosen by the user. Therefore, the use of extensions reduces the size requirement for a memory device in a system implementing the present invention. The central control computer of the present invention can be, but not necessarily, implemented using object oriented programming. Use of object oriented programming supports simultaneous use of multiple types of models for the different elements of the planning problem.


In one embodiment, the present invention provides a software based computer system for modeling various transports. For example, the computer system may model a transport means used to transport a particular physical object or product. The central control computer may also be used to model a product distribution channel, a supply chain, or an order fulfillment transport.


In a preferred embodiment a transport is modeled using three primary model types: an operation model type, an environmental data element type, and a resource model type. A plan for that transport is similarly modeled with three associated primary model types: the operation-plan, environmental data-plan, and resource-plan. A user uses a model type as a template to create a model. For example, an environmental data element type is used to create a model of environmental data. Each of these user defined models is stored as a node in a transport network model of a user's transport. The model types used by the system are extensible in that each model type may have one or more extension points that allow a user to customize the model to represent the user's transport. For each extension point, a user may choose from numerous extensions the one that is best suited to define a particular aspect of the user's system or transport. Each model type has a list of predefined extensions from which the user may choose. Each extension defines fields that extend the data and meaning associated with a model type. These extensions and fields define the way in which the model types interact. Each user defined model is defined by a model type, one extension for each extension point of the model type, and data for each field of the model type and extensions. Possible features of each of the model types are discussed in detail below.


The Operation Model Type may be used to create operation models which represent activities that can be performed. As used herein, “operation model type” means a general model for activities that may be modeled by the software. “Operation mode” and “operation model” are used interchangeably to represent a specific operation defined by a user using the operation model type. This convention is also used with respect to resources. An operation model type models a transport, activity, or action that transforms or moves physical objects resulting in a transport route.


Operations may require resources with specific skills. Those resources model may include transportation and/or storage.


An operation can use any number of resources, with different run times, and with staggered start and end dates. Thus, a single activity or a whole series of activities can be modeled with a single operation. This is important for having sufficient flexibility to model diverse activities. A preferred embodiment of the invention allows a routing to be modeled as simply a particular kind of operation that consists of other operations that are run in sequence. The relationships between those sub-operations can be different depending upon the chosen extension.


So, an operation can model a simple routing (a sequence of operations allowed to spread), a transport route routing (a sequence of operations which must transport route into one another), a set of operations that can be run at the same time, alternates (a set of alternate operations), and other combinations. Further, since routings are modeled as operations, they can be put in other operations.


For example, a simple routing operation may consist of different operations, called legs.


An operation can also model simply the environmental impact data for transporting a physical object (operations that just model the transform of physical objects, but do not model the environmental data required to do that).


Similarly, an operation can model simply the environmental impact data for transporting a physical object.


Other operations can then combine the environmental impact data with operations that properly consume environmental data.


For example, some transport software defines operations such that resources can be loaded just during portions of transport time. For ease of interfacing such packages or databases, transport extensions can be provided with the identical specification. That transport generates a routing-like operation containing auto-generated sub-operations that contain the different phased resource loadings.


An advantage of the operations model type design is simplicity and consistency. By providing a simple building block that is extensible and can be flexibly combined with others, a great deal of modeling capability is provided without complicating the common simple cases. In this way, the critical operations and resources can be modeled in adequate detail and time.


A user may select an extension from the operation model type to, for example, define a transportation model.


This model may contain a predetermined, constant time for loading material, followed by a run time which is a factor that is multiplied by the quantity of material that is being transported, followed by an unload run time which is constant. The load, run, and unload phases may each require use of different resources.


Operation models represent activities that consume supplies, transport physical objects, and/or utilize environmental data. Such operation models define the activities and precedence (timing) constraints in a transport. In transport, a sequence of operations is referred to as a routing. A routing is represented as an Operation model with a routing extension which defines the behavior of that operation to be a sequence of other operations. Similarly, the specification of alternate resources, alternate operations, and alternate routings can be done with an operation model and an extension which defines the behavior of that operation.


A resource model type may be used to create resource models which represent aspects of a transport that have predetermined environmental data. For example, a resource model may represent resources in a transport process. A resource model may represent a transport means such as an airplane, a ship or a truck, thus implementing the environmental impact data of a transport that has a predetermined environmental data limitation (such as carbon emission).


The resource model type may provide various extensions from which a user may choose to define an actual environmental data constraint on its transport. For example, a simple extension may only have a single field setting a maximum environmental data constraint. Such a resource model may, for example, represent a truck which has defined environmental impact data.


The environmental data type is used to create environmental data which manage physical objects transported in the modeled system. In other words, an environmental data element represents the management of a particular physical object.


Additionally, the environmental data type may have an extension that defines ordering policies.


A transport network model is a set of user defined models which may be stored in a computer memory. The stored nodes define, for example, the user's transport which is to be used to manage a particular. A user defines a level of desired environmental impact data by selecting model types and the appropriate extensions of these model types, as described above, to form models of the elements of the users' transport.


The nodes in transport network model may be connected together in many different ways to achieve different results. Transport network model represents all of the possible interconnections between starting place and destination of the transport of the physical objects.


A preferred transport network model represents the possible routes that material may be transported according to a route in a transport to be modeled. The central control computer of the present invention uses the information in a transport network model to create plans for implementing a particular material transport route path to model a transport. The interconnected nodes of the transport network model used to represent a particular plan may be referred to a as a plan network model or plan.


The central control computer according to the present invention may create a plan network model as a result of several different events. In general, a plan network model provides definitions as to quantities and timing for elements of the model. For example, the inventory level for a physical object managed by a particular environmental data may drop below an allowable level.


The central control computer may create a plan network model for replenishing the inventory of that environmental data. Alternatively, a plan may be created using the transport network model in response to customer orders. The central control computer of the present invention may create a plan network model as follows. For each activity in a user's transport, the central control computer creates an operation plan model from an operation-plan model type using extensions from the corresponding operation model. The system provides the operation plan model with the start and end dates, alternate selections, and other information needed to form a plan for a particular execution of that operation.


For each resource model that is used by an operation plan, the central control computer creates a resource plan model from a resource-plan model type and the extensions corresponding to the resource model. The system provides the resource plan model with all of the environmental data reservations placed on it by the operation plan models. For each environmental data according to which physical objects are transported or to which physical objects are transported by an operation plan, the central control computer creates an environmental data plan model from an environmental data-plan model type and the extensions of a corresponding environmental data. The system provides a plan model with inventory levels, ordering policies and any other information needed to plan the management of the transport route of physical objects in the transport.


Preferably the central control computer functions as system for modeling a transport capability for use in a transport routing system, the central control computer comprising: a plurality of operation models defined from an operation model type and stored by the computer system, each operation model representing an activity that can be performed by a transport; a plurality of environmental data defined from an environmental data element type and stored by the computer system, each environmental data element representing rules for controlling a transport route of material between activities, the activities represented operation models; the operation model type and environmental data type each having a plurality of fields defining attributes.


In an advantageous implementation the central control computer operates with a transport network model, stored by the computer and interrelating the operation models.


The transport network model can be formed by the plurality of operation models, each specifying environmental data according to which material is transported.


A material usage is preferably represented by the transport network model along with timing constraints between activities.


In a preferred embodiment the transportation system, especially the central control computer steering the system, further comprises: a plurality of resource models defined from a resource model type and stored by the central control computer, each resource model representing environmental data available for use in performing an activity and rules for allocating capacity to the activity, the activity represented by an operation model; the resource model type having a plurality of fields defining attributes; the transport network model further interrelating the resource models as logical nodes.


The transport network model may further be formed by a plurality of operation models each specifying resource models having environmental data used in performing the activity specified by the operation model; such that both material and environmental data usage are simultaneously represented by the transport network model, preferably but not necessary along with timing constraints between activities.


The central control computer is for example a computer with a database for storing environmental data and with interconnections to sensors and/or other computers capable of handling sensor data. Preferably the central control computer is coupled with means for implementing environmental data.


It is for example possible to connect the central control computer to at least one other computer which allows user to define values for environmental data.


It is advantageous to sign different user rights to different users and/or different types of users.


For example a customer is capable of define requested environmental data.


This allows for example a user to choose his own level of desired ecological quality of his transport, for example choosing zero-emission transport.


It is furthermore advantageous to assign other rights to other types of users.


It is for example possible to allow operators of the systems to implement a handling with regard to environmental data. This handling is for example bases upon ecological standards defined by competent authorities.


It is furthermore advantageous to implement an environmental data type wherein the environmental data type has an operation that defines how data managed by an environmental data element is stored. It is furthermore advantageous that the environmental data type has an operation that defines how material is received into an environmental data element.


It is further preferred that the central control computer comprises a plurality of resource models defined from a resource model type and stored by the computer system, wherein each resource model represents environmental data available for use in performing an activity and rules for allocating capacity to the activity, the activity represented by an operation model; wherein the environmental data type includes an operation that defines how material managed by an environmental data element is stored.


The specified operation model contains information about the operation that defines how physical objects are transported or supplies are handled.


Each operation model may specify another operation and each environmental data element may specify an environmental impact factor.


The usage of environmental data that may specify a range of dates during which the model is effective.


A preferred embodiment further comprises a computer for modeling transport capability.


Advantageously the central control computer comprises:

    • a data storage device operable to store data relating to a model of transport capability;
    • an execution memory operable to store data and coupled to the data storage device and
    • a plurality of operation models defined from an operation model type, each operation model representing an activity that can be performed by a transport
    • a plurality of environmental data defined from an environmental data element type, each environmental data representing rules for controlling a transport route of material between activities, wherein the operation model type and environmental data type each have a plurality of fields defining attributes;
    • a transport network model interrelating the operation models, the environmental data, and the resource models as nodes, wherein the transport network model is formed by a plurality of operation models each specifying environmental data according to which material is transported, such that material usage is simultaneously represented by the transport network model along with timing constraints between activities.


It is further advantageous to utilize a plurality of resource models defined from a resource model type, each resource model representing environmental data available for use in performing an activity and rules for allocating environmental data to the activity; the resource model type having a plurality of fields defining attributes; the transport network model further formed by the plurality of operation models each specifying resource models having environmental data used in performing the activity specified by the operation model; such that both material and environmental data usage are simultaneously represented by the transport network model along with timing constraints between activities.


A preferred embodiment of a method for modeling a transport further comprises an evaluation of capability for use in transport routing system on the computer system, the method comprising: defining a plurality of operation models from an operation model type, each operation model representing an activity that can be performed by a transport; defining a plurality of environmental data from an environmental data element type, each environmental data representing rules for controlling a transport route of material between activities, the activities represented operation models; and interrelating the operation models and the environmental data as nodes in a transport network model; the transport network model formed by the plurality of operation models each specifying environmental data from which material is transported and environmental data to which material is transported; such that material usage is represented by the transport routing system on the computer system.


The preferred embodiment of the method further comprises a plurality of operation models each specifying environmental data from which material is transported and environmental data to which material is transported; such that material usage is represented by the transport network model along with timing constraints between activities.


This preferred embodiment further comprises: defining a plurality of resource models from a resource model type, each resource model representing environmental data available for use in performing an activity and rules for allocating supplies to carry out transport processes.


Advantageously, the activity is represented by an operation model which interrelates the resource models as logical nodes in the transport network model.


The transport network model may further formed by the plurality of operation models each specifying resource models having environmental data used in performing the activity specified by the operation model; such that both material and environmental data usage are simultaneously represented by the transport network model along.


A functional view 200 of implementations according to the ACCEPT system is depicted in FIG. 2.


Functional View















Description

















Role



User
Abstract user that is interested in



an Emission Report


Operator
The operator of the ACCEPT system


CoSP
Provider of National shipments


T-Web
Provider of National road operators



and vehicles


DHL Air Express
Provider of air shipments


Rasti
Provider of city-to-city distances


Distance provider
Abstract distance provider


Use-Case


Show Emission
Abstract Emission report


DHL Air Express Report
Report for Air Express shipments


SE international report
Report for SE international shipments


SE domestic report
Report for SE domestic shipments


Import shipments
Imports shipments from CoSP


Import transports
Imports Transports from CoSP


Import postal code distances
Imports International postal code



distances (not impl.)


Import Airport distances
Imports Airport distances (not



impl.)


Import SE city-to-city
Imports SE city-to-city distance


distances
from Rasti


Import DHL Air express
Imports DHL Air express shipments


shipments


Import Operators
Imports SE road Operators from T-Web


Import Vehicles
Imports SE road Vehicles from T-Web









Advantageous databases for carrying out the invention are depicted in FIG. 3. The system shown in FIG. 3 is generally referred to by the reference number 300. The following table contains examples of these databases.













Database
Description







Distances
Different distance providers


Source
The Shipments and Transports provider (CoSP, DHL Air


system
Express)


OutArea
An inter-storage area where the Source system places



the exported Shipments and Transports for the period



to be calculated. From this area ACCEPT reads the



generic tables ACCEPT_Shipment and



ACCEPT_Transport.


DM_ACCEPT
The Data mart for ACCEPT. Contains the aggregated



rows on a Customer for a period, emission and



product type.









Execution Order to Create Reports

The table Parameters in ACCEPT contains run parameters for ACCEPT. The parameter Period is used to set the month for which a report will be created by the stored procedures.


Representation of how the data is imported from the production systems, calculated and moved to the reporting database by the use of stored procedures; is described afterwards in more detail.


The following table describes the execution order to create different reports.


















D
I
AE
SP Name
Description
DB
Tables







1


spOut-
Copies Shipments and Transports
DWH
xFile





Shipment
from DWH xFile and
OutArea
Transport





Transport
Transport to OutArea (Source

ACCEPT_Shipmeny






system ID = 1)

ACCEPT_Transport



1

spOut_SE_INT_Shipment-
Copies Shipments and Transports
DWH
xFile





Transport
from DWH xFile and
OutArea
Transport






Transport to OutArea (Source

ACCEPT_Shipmeny






system ID = 3)

ACCEPT_Transport




1
spOut_SE_AE_Shipment-
Creates Shipments and Transports
OutArea
SE_Inbound





Transport
from SE_Inbound and
OutArea
SE_Outbound






SE_Outbound. SE_Inbound and

ACCEPT_Shipment






SE_Outbound are currently

ACCEPT_Transport






loaded by a DTS package that






is loading an Access database,






se Imports section.


2

2
spLoad-
Copies Shipments from Out
OutArea
ACCEPT_Shipment





Shipment
Area to ACCEPT
ACCEPT
Shipment



2

spLoad_SE_INT_Shipment
Copies Shipments from Out
OutArea
ACCEPT_Shipment






Area to ACCEPT
ACCEPT
Shipment


3
3
3
spLoad-
Copies Transports from Out
OutArea
ACCEPT_Transport





Transport
Area to ACCEPT
ACCEPT
Transport


4
4
4
spDMPrepare
1. Creates tmpTransportDist
ACCEPT
Shipment,





Load
with distances for all
ACCEPT
Transport,





Shipment
transports

Emission






2. Creates tmpVehicleEm

tmpTransport






with emissions for all Vehicles,

Dist






VehicleTypes and Operators

tmpVehicle








Em


5
5
5
spDMLoad
Aggregates Shipments from
ACCEPT
Shipment,





Shipment
ACCEPT to DM_ACCEPT
DM_ACCEPT
Transport,








Emission








tmpTransport








Dist








tmpVehicle








Em








F_Shipment





D = Domestic,


I = International,


AE = Air Express,


Bold = target table or database






Stored Procedures for Loading of Code Tables















SP Name
Description
DB
Tables







spRun
Example used to execute Swedish
All
All



domestic for specific months


spLog
Sp that used to add a row to the
ACCEPT
xLog



xLog


spLoadOperator
Loads operators and vehicles from
OutArea
ACCEPT_Vehicle


Vehicle
the T-Web tables
ACCEPT
ACCEPT_Operator





Operator





Organisation





Vehicle


spLoad-
Loads Nodes and Legs from OutArea
OutArea
ACCEPT_Node


NodeLeg
to ACCEPT
ACCEPT
ACCEPT_Leg





Node





Leg


spLoadCustomer
Loads customers from OutArea
OutArea
ACCEPT_Customer




ACCEPT
Customer


spLoadCity-
Load city-to-city distances from
ACCEPT
ImpCityDistances


City
ImpCityDistances to Leg and
ACCEPT
Node



Nodes. ImpCityDistances is a distance

Leg



tabled loaded from Rasti.









Imports to ACCEPT


FIG. 4 shows a preferred import of files and tables in a system 400 according to the invention. FIG. 4 describes what files and tables are imported to ACCEPT from different source systems.


How to Add New Source Systems

Preferred steps to add a new Source system to ACCEPT are described below:

    • 1. Create a stored procedure that imports Shipments and Transports to the tables ACCEPT . . . Shipment and ACCEPT . . . Transport. Se spOutShipmentTransport as an example.
    • 2. Decide which type of distance calculation you need to perform. City-to-City or Terminal-pickup-distribution calculation.
    • 3. To add a new product type and assign it to a distance calculation type, it is advantageous adding a Transport stored procedure to spLoadTransport.sql that handles the added product type.


How to Add a New Country

A first preferred embodiment of the ACCEPT-system handles data for one country e.g. Sweden. To add a new country it is useful adding a completely new instance of ACCEPT database and DM ACCEPT database it is useful to add. ACCEPT database for Sweden growth approximately 2 gigabyte per month excluding distances, emissions, operators and vehicles.













Physical object
Description







Handling of historical
Historical data can be handled. It should


data
preferably be used to just remove rows for



current period and product id.


Automatic production
To maintenance and run the system, many



jobs, scripts, and ftp-connections must be



created.


Operational interfaces
Operational interfaces are created in advantageous



implementations of the invention.









Afterwards calculation methods for a transport emission report according to the invention are described in detail:


Transport Emission Report—Calculation Methods

The described calculation methods and general data allow different ways of calculating environmental performance of cargo forwarded.


General Description of the Calculations

The ACCEPT system calculates the environmental performance of each cargo shipment handled by a transport carrier, which is afterwards without limitation named DHL. A calculation is performed for each relocation carried out during the transport of a shipment through the DHL transport system. The result from each relocation is then summarised in order to answer different questions, e.g.

    • total emissions for a specific piece of cargo
    • total emissions for all transports for a customer during a selected time period


Definition of Cargo

Cargo data is obtained from the information systems of DHL. The data for the transported weight is used as the base for the calculations. This means that the environmental performance of each relocation is related to the weight of the investigated shipment/goods.


The weight is given as the volumetric, or dimensional, weight. This means that the physical weight of the shipment is used if the density of the shipment exceeds 250 kg/m3. Otherwise the volumetric weight is calculated as the volume of the shipment multiplied by the factor 250 kg/m3.


Environmental Parameters

The following parameters are evaluated:









TABLE 1







Environmental performance data included in the ACCEPT system.










Name
Abbreviation
Unit
Description





Carbon Dioxide -
CO2 fossil
[g]
Includes emissions from


Fossil


all non-renewable sources


Carbon Dioxide -
CO2 tot
[g]
Includes emissions from


total


both renewable and non-





renewable sources


Nitrogen
NOx
[g]
Measured as Nitrogen Dioxide,


Oxides


NO2.


Hydro Carbons
HC
[g]
Includes emission data of





all types of categorisations





of hydrocarbon compounds





(i.e. VOC, NMHC,





CH4) emitted from engines





and power plants.


Particular
PM
[g]
Includes emission data of


Matter


all types of definitions





of particles (i.e. PM10,





PM2.5 etc.)


Sulphur Oxides
SOx
[g]
Measured as sulphur dioxide,





SO2


Primary energy -

[MJ]
Denotes the energy content


Fossil


of the utilised non-





renewable energy carriers





(e.g. diesel, petrol,





natural gas, coal, peat





etc.)


Primary energy -

[MJ]
Denotes the total heat released


Nuclear


by fission processes





in nuclear reactors


Primary energy -

[MJ]
Denotes the energy content


Renewable


of the utilised renewable





energy carriers (e.g.





RME/bio-diesel, biogas,





biomass, etc.) and/or the





electricity produced by





solar-, wind- and hydro





power plants









System Boundaries
Time

The base for the calculation is continuously updated why the values are only valid for the ‘present’ system at any given time.


Geography

The emissions reported are emitted within the following geographic boundaries

  • ROAD—traffic within a certain area, e.g. Europe
  • RAIL non-electric—traffic within a certain area, e.g. Europe
  • RAIL electric—traffic using electricity generation within a certain area, e.g. Europe (UCPTE)
  • SEA—traffic within a certain area, e.g. Europe and surrounding waters
  • AIR—traffic within a certain area, e.g. Europe


Technical Systems

The calculation only covers emissions directly connected to the operation of the vehicle, train, vessel or aircraft. This includes engine exhaust emissions (road, rail non-electric, sea and air) and emissions from power plants engaged in the generation of consumed electricity (rail electric).


Emissions related to the following activities are implemented in more complex implementations of the invention:

    • 1. Construction, maintenance, service and scrapping/dismantling of:
      • vehicles and vessels
      • power plants
      • Traffic infrastructure (roads, bridges, petrol stations etc.)
      • Transport infrastructure (terminals, cargo handling systems, pallets etc.)
    • 2. Operations of
      • traffic infrastructure (illumination, cleaning, snow clearing, surveillance etc.)
      • transport infrastructure (terminal heating and illumination, personnel, cargo-handling systems etc.)
    • 3. Extraction, production and distribution of energy carriers
    • 4. Emissions from fuel systems and fuelling operations (evaporation)
    • 5. Emissions related to extraordinary events (i.e. due to accidents, conflicts, natural disasters or technical malfunctions)


ROAD Transport Calculation Methods
Truck Emission Calculations
Vehicle Types

The emission report is based on vehicle data supplied either from the vehicle operator or by application of standard default values relevant for the network of the transport carrier. The same calculation method is applied regardless of the data source. The following vehicle data is used in the calculation:









TABLE 2







Shows default vehicle types and parameters, with typical values.













Max
Capacity


Engine



load
utilisation

Fuel
type


Vehicle
capacity
[%-by
Fuel
Consumption
Emission


type
[tonne]
weight]
type
[l/vkm]
Standard















ry
1.5
50
Petrol
0.15



van


Delivery
1.5
50
Diesel
0.15


van


Distribution
8
50
Diesel
0.25
Euro 1-3


Lorry


Heavy
14
50
Diesel
0.3
Euro 1-3


Distribution


lorry


Heavy
14
50
Methane
0.3
Euro 1-3


Distribution


lorry


Tractor +
28
75
Diesel
0.38
Euro 1-3


Semi-trailer


Lorry +
40
75
Diesel
0.45
Euro 1-3


Semi-trailer









Emission Data Source and Quality

The ACCEPT-systems calculates the environmental performance of each relocation. The system uses the most specific information available. The following priority is used:

    • 1. The data for the specific vehicle that is used for the transport of the cargo
    • 2. The average value for all the vehicles (of the applied type) used by the specific operator
    • 3. The average value for all the vehicles (of the applied type) used in the network of the transport carrier in the region
    • 4. The default value from other external sources are applied (e.g. NTM).


Load Capacity and Utilisation

The emissions from the lorry are split between the cargos carried by the vehicle. The actual amount of cargo carried by each specific vehicle is usually not known. Instead, the following optional hierarchy is applied:

    • 1. The stated average value for the specific vehicle is used
    • 2. The average value for the specific operator is used
    • 3. The average value for the transport carrier network in Scandinavia/Europe is used
    • 4. The default values from other external sources are applied (eg. NTM).


The average values calculated in 1-3 are based on data for one calendar year.


Emission levels: Fuel-, Engine- and Exhaust cleaning combinations


The calculation is based on the emission level stated for different combinations of fuel and engine type (i.e. Euro classification).


HDV Emissions









TABLE 3







Shows exhaust gas emission data for Medium size


Diesel Vehicles (MDV) in URBAN traffic


MDV - Urban traffic


Vehicle gross weight 7–20 tonne, average speed 27 km/h.














HDV/

HDV/
HDV/



[g/l]
Euro0
HDV/Euro1
Euro2
Euro3

















HC
5.83
3.39
2.04
1.94



CO
13.2
8.47
6.15
7.31



NOx
35.6
26.3
33.3
25.1



PM
1.82
1.62
0.576
0.843



CO2
2642
2642
2642
2642



CH4
0.140
0.0813
0.0491
0.0466



SOx
0.0133
0.0133
0.0133
0.0133

















TABLE 4







Exhaust gas emission data for Medium size Diesel


Vehicles (MDV) in RURAL traffic


MDV - Rural traffic


Vehicle gross weight 7–20 tonne, average speed 71 km/h.














HDV/

HDV/
HDV/



[g/l]
Euro0
HDV/Euro1
Euro2
Euro3

















HC
3.20
1.88
1.17
1.13



CO
9.52
5.46
4.74
5.53



NOx
40.7
28.0
33.1
24.3



PM
1.35
0.932
0.536
0.599



CO2
2642
2642
2642
2642



CH4
0.0768
0.0450
0.0282
0.0271



SOx
0.0133
0.0133
0.0133
0.0133

















TABLE 5







Exhaust gas emission data for Heavy Diesel Vehicles


(HDV) in highway traffic


HDV - Highway traffic


Vehicle gross weight >20 tonne, average speed 82 km/h.














HDV/

HDV/
HDV/



[g/l]
Euro0
HDV/Euro1
Euro2
Euro3

















HC
1.42
1.72
1.07
1.01



CO
4.81
4.92
3.57
4.33



NOx
35.5
27.2
31.5
21.8



PM
1.06
0.902
0.451
0.488



CO2
2642
2642
2642
2642



CH4
0.0341
0.0412
0.0258
0.0242



SOx
0.0133
0.0133
0.0133
0.0133










The fuel-specific emission was found to vary somewhat with road type and vehicle type.


LDV Emissions

Emission data for light duty vehicles is only presented for the urban traffic since these vehicles are mostly used for distribution in urban areas.









TABLE 6







Exhaust gas emission data for Diesel Light Duty


Vehicles (LDV) in URBAN traffic.


LDV - Urban


traffic N1-III


Vehicle gross weight max 3.5 tonne, average speed 35 km/h.













[g/l]
vor 86
XXIII/EEA1
EURO1
EURO2
EURO3
EURO4
















HC
6.12
1.514
1.514
1.270
0.701
0.597


CO
15.5
7.00
7.00
3.50
1.93
1.66


NOx
9.7
9.27
9.27
8.0
6.04
3.40


PM
4.08
1.003
1.003
0.866
0.387
0.196


CO2
2642
2642
2642
2642
2642
2642


CH4
0.147
0.0363
0.0363
0.0305
0.0168
0.0143


SOx
0.0133
0.0133
0.0133
0.0133
0.0133
0.0133


FC [l/km]
0.115
0.101
0.101
0.101
0.101
0.101









Emission Data Sources

The applied diesel engine emission levels are adopted from the material presented by a competent source.


Emission Control Devices

The following emission control devices are applied with stated reduction of emissions.









TABLE 7







Shows diesel engine emission reductions with


abatement techniques.

















PM-

EGR + PM




Engine


filter
EGR
filter

SCR + PM


generation
Substance
Ox.kat.
(CRT)
(retrofit)
(retrofit)
SCR
filter





Euro I
CO2


 2%
 +2%





HC
−90%
−90%

−90%

−90%



NOx


−40%
−40%
−81%
−81%



PM
−20%
−90%

−90%

−90%


Euro II
CO2


 2%
 +2%



HC

−90%

−90%

−90%



NOx


−40%
−40%

−81%



PM
−15%
−90%

−90%

−90%


Euro III
CO2


  +2%**
 2%



HC
−90%
−90%

 −90%**

−90%



NOx


−40%
−40%
−81%
−81%



PM
−10%
−90%

−90%

−90%


Euro IV
CO2



HC

−90%



−90%



NOx




−81%
−81%



PM

−90%



−90%


Euro V*
CO2



HC

−90%



−90%



NOx




−81%
−81%



PM

−90%



−90%









Definition of Vehicle Capacity and Capacity Utilisation

Cargo capacity is defined as the physical weight carrying capacity of respective vehicle. The calculation of the cargo capacity utilisation uses data for the volumetric weight of the investigated cargo shipment. The capacity utilisation is defined as the loaded volumetric weight divided by the maximum allowed carrying capacity.






CCU
=




i



w

i
-
vol




W
max






Where:



  • CCU=cargo capacity utilisation

  • wi-vol=volumetric weight of shipment i

  • Wmax=Max allowed cargo weight

  • i=index number for all shipments loaded on the vehicle.



Allocation of Emissions to Transported Cargo
Full Truck Load

The environmental performance data for the vehicle is divided among the cargo shipments in proportion to their volumetric weight, using the following formula:







Share





to





shipment






(
i
)


=



w

i
-
vol





i



w

i
-
vol




=


w

i
-
vol



CCU
×

W
max








Integrated Cargo Transports via Terminals
Inter Terminal Transports

The transports between the terminals are handled in the same way as the full truckload.


Distribution and Pick Up

The environmental performance of the transport between the terminal and the customer (both pick up and delivery) is calculated as follows:


Some integration terminals are selected in order to represent different daily flow volumes, geographic coverage of operations, types of distribution vehicles etc. The total environmental performance for all delivery and pick-up traffic to and from each terminal is calculated. This amount is divided by the total amount of cargo handled in the terminal over the same period. The result is an average environmental performance per tonne cargo passing through the terminal. The rest of the terminals are categorised according to one of the investigated terminal types.


When information about the distance between the terminal and the origin/delivery address of a specific shipment is available the system will recognize it and use the specific characteristics of each truck. The environmental performance for the pick-up/distribution of a shipment is only depending upon the (volumetric) weight of the shipment.


Green Tonne

‘Green tonne’-trucks are only considered for the calculation of the environmental performance for the goods sent by customers buying this service. The environmental performance of these trucks, and the load carried by them, is therefore excluded in the calculation of the terminal average value.


RAIL Transport Calculation Methods

The ACCEPT system handles transports with cargo train in one ore more countries, as for example Sweden. In one advantageous implementation, only trains pulled by electrical engines are considered.


Cargo Units

Data for rail transport is given for the transport of the following cargo units:

    • 20 feet container
    • 40 feet container
    • semi-trailer (for road transport)


The emission calculations for trains are based on the weight of the cargo. The following default values are used for these units:









TABLE 8







Investigated cargo units for train transport.












Cargo
20 feet
40 feet
Semi-



unit
container
container
trailer















Max cargo carrying
[tonne]
28.25
28.8
26


capacity


of unit


Cargo capacity
[%-weight]
50%
50%
75%


utilisation of unit


Cargo weight
[tonne]
14
14
20


in unit


Cargo unit
[tonne]
2.23
3.7
7


tara









Train- and Wagon Types

The cargo types are transported on different wagon types, for example the following Swedish wagon types:


















Cargo
20 feet
40 feet




unit
container
container
Semi-trailer




















Wagon type

Container
Container
Semi-trailer




wagon
wagon
wagon




(Lgjs 741)
(Lgjs 741)
(Ldgs)









Emission Calculation

The emissions reported for the electrical train are those emitted from the power plants balancing the electricity use. The electricity need for pulling a typical cargo train is combined with the emission profile for the selected mix of power plants, this in order to find the emissions related to the transport. These emissions are then divided between the transported cargos in proportion to the net physical weight.


Electricity Demand

The electricity demand for pulling a typical cargo train is calculated by using the method suggested by the EcoTransIT project (also adopted by NTM), see EcoTransIT 2003. The calculation is made for a block train of 1000 tonnes gross. This weight is entered into the formula presented in Table 9 below.









TABLE 9







Electricity consumption for cargo trains.












Gross weight
Electricity




range (Wgr)
consumption (EC)


Traction
Topography
[tonne]
[Wh/gross tkm]





Electrical
Hilly terrain
500–1500
EC = 675 * Wgr−0.5









The electricity demand is thus found to be 0.021 [kWhel/ton-br×km], as measured at the engine.


Transmission Losses

There are losses in the transmission of the electricity from the power plant to the engine. The losses are moderate for the high voltage transmission to the connection to the rail network. The losses between the outtake from the grid to the engine are higher, due to frequency modulation and lower transmission voltage in the catenaries. The following values used by NTM are applied in the calculation:



















Electricity demand at engine
[kWhel/ton-
0.021




br × km]



Transmission losses between engine -
[%]
20%



power grid



Transmission losses between power
[%]
 4%



grid - power plant



Electricity demand at power plant
[kWhel/ton-
0.028




br * km]










Electricity Needed per Unit

Next step in the calculation is to find the gross weight of the wagons carrying the 3 different loaded cargo units. The following Tara weights and cargo capacity data are used in the calculations:









TABLE 10







Cargo and wagon data used in train calculations












Cargo
20 feet
40 feet




unit
container
container
Semi-trailer















Wagon type

Container
Container
Semi-trailer




wagon
wagon
wagon




(Lgjs 741)
(Lgjs 741)
(Ldgs)


Waggon tara
[tonne]
11.8
11.8
13.35


Cargo units

2
1
1


per wagon


Train
[ton-gross]
22.3
29.9
39.9


weight per


cargo unit










Tonne is a mass unit. It equals 1000 kg.


The wagon gross weight is connected to the carried unit(s). These data are then connected to the calculated emission per gross ton in order to find the environmental data connected to the transport of one unit 1 kilometre.


Electricity Production

A mix of the electricity production in the Nordic countries (Norway, Denmark, Sweden and Finland) was used in the calculation. The production volumes from each country were combined with the emission data for Swedish electricity generation. The following mix was applied:









TABLE 11







Applied mix of power plants.










Power
Nordic mix



plant
1998














Hydro
54.2%



power



Nuclear
24.2%



power



Wind power
0.8%



Coal condensing
7.1%



power



Oil condensing power
1.3%



CHP - Coal
2.8%



CHP - oil
1.2%



CHP - Natural gas
3.7%



CHP - Biomass (steam
4.7%



cycle)



CHP - peat
0.0%



Gas turbine
0.0%



Natural Gas - Combined
0.0%



cycle







CHP = Combined Heat Power generation






This kind of values (also e.g. table 14) is an example and will vary with time and between countries and need to be updated


The emission profile for this production mix as presented below was applied in the calculations.









TABLE 12







Environmental profile of selected mix of power plants.











Emissions/Primary energy


Substance
unit
Only from power plant












CO2 fossil
[g/kWhel]
130


CO2 total
[g/kWhel]
115


NOx
[g/kWhel]
0.26


HC
[g/kWhel]
0.002


PM
[g/kWhel]
0.014


SO2
[g/kWhel]
0.28


Primary energy - Fossil
[MJ/kWhel]
2.2


Primary energy - Nuclear
[MJ/kWhel]
1.4


Primary energy - Renewable
[MJ/kWhel]
2.91









Calculation Results

The following calculation result is used in the ACCEPT application.









TABLE 13





Environmental performance data for the transport


of 1 unit 1 kilometre.


















Container block




train
Container block train



LCI data for electricity
Only emissions from


20 feet container
generation
power plant













CO2 fossil
[g/km]
82
81


CO2 tot
[g/km]
73
71


NOx
[g/km]
0.2
0.2


HC
[g/km]
0.006
0.001


PM
[g/km]
0.011
0.009


SO2
[g/km]
0.2
0.17


Primary
[MJ/km]
1.37
1.37


energy


Fossil


Primary
[MJ/km]
1
0.9


energy -


Nuclear


Primary
[MJ/km]
2
1.80


energy -


Renewable













Container block




train
Container block train



LCI data for electricity
Only emissions from


40 feet container
generation
power plant













CO2 fossil
[g/km]
111
108


CO2 tot
[g/km]
98
95


NOx
[g/km]
0.2
0.22


HC
[g/km]
0.008
0.001


PM
[g/km]
0.01
0.01


SO2
[g/km]
0.2
0.2


Primary
[MJ/km]
1.8
1.8


energy -


Fossil


Primary
[MJ/km]
1
1


energy -


Nuclear


Primary
[MJ/km]
2
2


energy -


Renewable













Semi-trailer wagons
Semi-trailer wagons


Semi-trailer
LCI data for electricity
Only emissions from


Data per trailer
generation
power plant













CO2 fossil
[g/km]
148
144


CO2 tot
[g/km]
130
127


NOx
[g/km]
0.3
0.3


HC
[g/km]
0.011
0.002


PM
[g/km]
0.02
0.02


SO2
[g/km]
0.32
0.31


Primary
[MJ/km]
2.5
2.5


energy


Fossil


Primary
[MJ/km]
1.6
1.6


energy -


Nuclear


Primary
[MJ/km]
3
3


energy -


Renewable





SEA Transport calculation methods






Ship and Cargo Types

The following cargo types are applied in the calculation for sea transport: 20 feet container, 40 feet container, semi-trailer, articulated truck, rigid truck and trailer.


The ACCEPT systems calculates the environmental performance of cargo transported by ships by applying data for a number of representative vessels. The selected vessel types are presented in Table 13 below. Environmental data for two container sizes and 3 different road vehicles are calculated, see Table 13 for the selected combinations of cargo and vessel type.









TABLE 13







Cargo units and ship types included in the ACCEPT model.





















Large









containe









vessel


Vessel





Container
(ocean


type
RoPax
RoPax
RoRo
RoRo
RoRo
feeder
going)





Vessel name/
Mecklenburg
MS Deutschland
Older,
newer,
newer,
Older,
6 600 TE -


description
Vorpommern

slow (<18 kn.) -
faster
faster
slow (<18 kn.) -
no





no
(>20 kn.) -
(>20 kn.) -
no
abatemen





abatement
no
SCR
abatement






abatement
de-NOx


Route
Trelleborg
Rödby (DK) -
Short Sea
Short Sea
Short
Short Sea
Short Se



(SE) -
Puttgarden


Sea



Rostock
(DE)



(DE)


20 feet









container


40 feet









container


Semi-trailer







Articulated







truck


Rigid truck







and trailer









Emission Calculations—General Methodology

The emissions for the selected ships are calculated in the following steps:

    • 1. The fuel consumption per km for the vessel is adopted from published vessel information or calculated based on the engine type and size.
    • 2. An average emission profile for the most common engine types (for each vessel type) is selected
    • 3. The emission per km is found by combining the two above-mentioned steps.
    • 4. The total emission is allocated to one cargo unit by dividing the emission by the average number of cargo units carried.


The allocation procedure in step 4 differs between the vessel types, see below.


A Calculation Example

The calculation is illustrated by the example of an older and slow RoRo vessel (Older Danish vessel, DANA CIMBRIA).


Step 1. Fuel consumption (FC).

The fuel consumption is not stated in the vessel information. The consumption is calculated by assuming a specific fuel consumption of 200 g/kWh and a 85% power outtake at cruise speed, i.e. 17.5 knots. With an installed engine power of 6600 kW is the fuel consumption given as:






FC=0.85×6600×0.200=1122 [kg/h]


with a speed of 17.5 knots=32.4 km/h,






FC
=


1122

32


,


4


=

34


,



6




[


kg



/


km

]







Step 2 & 3. Vessel Emissions

The emission profiles are selected based on the combination of fuel type and engine speed. From known data-bases the following emission data are extracted for the use in the calculations for the ACCEPT system:









TABLE 13







Emissions from Main Engines at cruise speed.











Slow
Medium
Medium



Speed
Speed
Speed



Diesel
Diesel
Diesel



engine
engine
engine


Engine
(SSD)
(MSD)
(MSD)


type
Residual
Marine
Residual


Fuel type
Oil
Gas Oil
Oil














CO2 fossil
[kg/tonne]
3179
3177
3178


CO2 total
[kg/tonne]
3179
3177
3178


NOx
[kg/tonne]
93
65
66


HC
[kg/tonne]
3
2
2


PM
[kg/tonne]
4
1
3.8


SOx
[kg/tonne]
54
10
54


Primary energy -
[MJ/tonne]
41000
42600
41000


Fossil


Primary energy -
[MJ/tonne]
0
0
0


Nuclear


Primary energy -
[MJ/tonne]
0
0
0


Renewable


Reference

Whall et
Whall et
Whall et




al. (2002)
al. (2002)
al. (2002)









The RoRo vessel is typically powered by a medium speed diesel engine (MSD) burning residual oil. The emission per km is calculated by multiplying the fuel consumption by the emissions stated in Table 14, yielding the results presented below:









TABLE 15





Calculated emission for the selected RoRo ship.



















Fuel consumption
[ton/km]
0.0346



CO2 fossil
[g/km]
110 033



CO2 total
[g/km]
110 033



NOx
[g/km]
2275



HC
[g/km]
81



PM
[g/km]
130



SO2
[g/km]
1869



Primary energy -
[MJ/km]
1419



Fossil



Primary energy -
[MJ/km]
0



Nuclear



Primary energy -
[MJ/km]
0



Renewable










Step 4. Allocation to Transported Cargo

The total cargo capacity of the selected RoRo vessel was stated as 2 000 lane meters. The utilisation of the vessel is difficult to assess since this type of information (often) is considered as business sensitive information. A frequently stated CCU (lm) of 90% is used in these calculations. This value could be a bit on a high end and should probably be changed to 75-80% in a future up-date. The share of the ship emission to allocate to one lane metre is then calculated as 0.056%, see below.



















Lane meter capacity
[lm]
2000



Cargo Capacity Utilisation

  90%



Utilised lane meter
[lm]
1800



Share to one lane meter

0.056%










The following proportions then calculate the emission to each cargo unit:









TABLE 14







Share of ships emission to each cargo unit, calculation


example for RoRo vessel.












Vehicle length
Share of ships



Cargo unit
[lm]
emission















Semi-trailer
13.6
0.76%



Articulated
18
1.00%



truck



Rigid truck and
25.25
1.40%



trailer










The emission per cargo unit is then found by the combination of the ship emission and the share stated above. The result is presented in Table 17.









TABLE 17







Calculated emissions per cargo unit, calculation


example for RoRo vessel.















Rigid






truck




Semi-
Articulated
and


Substance
unit
trailer
truck
trailer














CO2 fossil
[g/km]
831
1 100
1 544


CO2 tot
[g/km]
831
1 100
1 544


NOx
[g/km]
17
23
32


HC
[g/km]
0.6
0.8
1.1


PM
[g/km]
1.0
1.3
1.8


SO2
[g/km]
14
19
26


Primary energy -
[MJ/km]
11
14
20


Fossil


Primary energy -
[MJ/km]
0
0
0


Nuclear


Primary energy -
[MJ/km]
0
0
0


Renewable









Vessel Type Specific Comments
RoRo Vessels

The following vessels are used in the calculations for transports with RoRo ships:









TABLE 15





Selected RoRo vessels.



















Vessel

DANA
DFDS Tor
DFDS Tor




CIMBRIA
Selandia
Selandia


Description

Older,
newer,
newer,




slow
faster
faster


Speed
[knop]
 17.5
 21
 21


Engine type

MSD
MSD
MSD


Fuel type

RO
RO
MGO


Sulphur
[%-
  2.7
  2.7
  0.5


content
weight]


Abatement



SCR


Lane meter
[lm]
2000
3000
3000


capacity


Capacity

90%
90%
90%


utilisation


Utilised
[lm]
1800
2700
2700


lane meter









RoPax Vessels

A RoPax vessel is carrying both passengers and vehicles. The RoPax ships usually offer substantial volumes for passenger purposes. The fact that they are carrying such different types of cargo makes the calculation modules for an allocation of environmental data different. One of the less complex ones, allocation by deck type, is selected for the calculations of data applied in the ACCEPT system. This method divides the ships emission in the following way:

    • 1. (the number of decks carrying vehicles)/(total number of ‘cargo’ decks)
    • 2. the share allocated to the vehicle decks are then divided by the number of utilised lane metres. (same as for the RoRo ships).


Like for the RoRo ships, high quality utilisation data is difficult to obtain from the ship operators.


The following vessels are used in the calculations for the ACCEPT system:









TABLE 16





Selected RoPax vessels.


Vessel description




















Vessel

Mecklenburg
MS Deutch-





Vorpommern
land



Route

Trelleborg
Rodby (DK) —





(SE) —
Puttgarden





Rostock (DE)
(DE)



Engine type

MSD
MSD



FC/crossing
[ton]
15.7
1.82



Distance
[km]
202
26



Fuel type
[%-
RO
RO




weight]



Sulphur
[%-
 2.7
2.7



content
weight]










The emissions used in the ACCEPT model are rather high since the selected ships are rather small and old. Newer ships are usually less polluting due to larger lane metre capacity as well as cleaner engines. Vessels exist with half the CO2 emission and only a fraction of the NOx emission (e.g. due to SCR de-NOx systems).


The ACCEPT system should be up-dated with more situation specific data supplied from the ship operators carrying out the transports of the investigated vehicles. Capacity utilisation and fuel consumption data should be averaged over a longer period of operations (e.g. one year).


Container Vessels
Cargo units

Data for transport with container vessel is given for the transport of the following cargo units:

    • 20 feet container
    • 40 feet container


The following two vessel types are included in the ACCEPT system, see









TABLE 17





Container ship types




















Vessel type

Small feeder
Ocean going





vessel



Category

Container
Container



Description

Older, more
Mid sized





slow



Speed
[knots]
13.7
20.2



Engine type

MSD
SSD



Fuel type

RO
RO



Sulphur content
[%-
 2.7
 2.7




weight]



Abatement













The vessel emission values were calculated in the same way as for RoRo vessels. Fuel consumption was given for a specified/normal route.


The calculated emissions were allocated to the number of utilised TEU positions. The following values were obtained:









TABLE 18







Allocation data for container ships.










Small




feeder



vessel
Ocean going
















TEU capacity
[TEU]
800
6600



CCU - Cargo Capacity

  80%
  100%



Utilisation



TEU
[TEU]
640
6600



positions



Share to

0.156%
0.015%



one TEU



position










The environmental data per cargo unit can now be calculated. The following results were obtained:




















Vessel

Small feeder vessel
Ocean going



Description

Older, more slow
Mid sized



Speed
[knots]
 14
 20



Capacity
[TEU]
800
6600



Abatement





















20 feet
40 feet
20 feet
40 feet


Substance
unit
container
container
container
container





CO2 fossil
[g/km]
122
244
64
129


CO2 tot
[g/km]
122
244
64
129


NOx
[g/km]
2.5
5.1
1.9
3.8


HC
[g/km]
0.090
0.180
0.062
0.125


PM
[g/km]
0.14
0.29
0.08
0.17


SO2
[g/km]
2.1
4.2
1.1
2.2


Primary
[MJ/km]
1.6
3.2
0.8
1.7


energy -


Fossil


Primary
[MJ/km]
0
0
0
0


energy -


Nuclear


Primary
[MJ/km]
0
0
0
0


energy -


Renewable









Summary of the Results



























Small


Inter





RoRo
RoRo
RoRo
feeder

Inter
modal



20 feet

Older,
newer,
newer,
vessel
Ocean
modal
train



container

slow
faster
faster
Older,
going
train-
with out



RoPax
RoPax
(<18 kn.) -
(>20 kn.) -
(>20 kn.) -
slow
6 600
LCI
LCI



Mecklenburg
MS
no
no
SCR
(<18 kn.) - no
TEU - no
1 000
1 000


20 feet container
Vorpommern
Deutschland
abatement
abatement
de-NOx
abatement
abatement
tonnes
tonnes

























CO2 fossil
[g/km]





122
64
82
81


CO2 tot
[g/km]





122
64
73
71


NOx
[g/km]





2.5
1.9
0.2
0.2


HC
[g/km]





0.090
0.062
0.006
0.001


PM
[g/km]





0.144
0.083
0.011
0.009


SO2
[g/km]





2.1
1.1
0.2
0.17


Primary
[MJ/km]





1.6
0.83
1.37
1.37


energy -


Fossil


Primary
[MJ/km]





0
0
1
0.9


energy -


Nuclear


Primary
[MJ/km]





0
0
2
1.80


energy -


Renewable









Afterwards standard operating procedures (SOP) for carrying out advantageous implementation of the invention are described in further detail.


The calculation processes are carried out with different data modules.


A preferred embodiment 500 depicted in FIG. 5.


The following sequences of activities are to be preferred; dependencies are shown for each step.

    • BACKUP OF WORLDMAIL.
    • WEEKLY BILLING.
    • BEFORE REPORTS. (SLIB REPORTS—BEFORE)
    • GBB EXT/LISTNING.(MENU IMB315)
    • CHANGE PARAMETERFILE. (MENU IBM520)
    • SAVE ALL IBS files. (MANUAL TAR BACKUP)
    • DAILY SAVE & REGULAR SHIPMENTS. (MENU IBM305)
    • ALLOCATE HANDLING FEE'S AND DISCOUNT'S. (MENU IBM330)
    • REGULAR INVOICE PROCESSING. (MENU IBM330)
    • If A.IB.CPH exists it should be renamed.
    • CREATE STATISTIC SUMMARY FILE. (MENU IBM335)
    • VARIOUS REPORTS. (MENU IBM335)
    • COPY OF A.IB.T99.
    • SET PERIOD END DATE. (MENU IBM340)
    • CHANGE PARAMETERFILE. (MENU IBM520)
    • VARIOUS REPORTS. (SLIB REPORTS—AFTER)
    • E-MAIL TO ANNIE.
    • Capella tapes.
    • Slet filer.
    • MONTH END FILE HOUSEKEEPING. (MENU IBM340)
    • MONTHEND FOR INBOUND.
    • COPY OF A.IB.T98
    • ISS MONTH-END.
    • RMS FILE TRANSFER.
    • T99 EXTRACT.


The scope is to give easy and potentially secure access to external users (Customer and Suppliers) and internal users (Sales representatives, Quality assurance, Analysts and maintaining of the system).


The access could be preferably done from a company web site, external and internal.


Operation Process Map

This chapter gives a high level overview on the operation processes of the GO GREEN implementation. There are core process groups that are visualized in a block diagram 600 shown in FIG. 6.


A computer which is equipped with software capable of handling Carbon Management represents a preferred hub of the system. Here the accounting of the credits takes place, the demand and supply of credits are matched and carbon credits are retired. This Carbon Management computer is afterwards called CM. The CM is preferably also responsible for the financial and contractual arrangements with the BU on both the demand and supply side.


On the demand side the participating BU sell GO GREEN products to their customers and, in most cases, collect additional revenue for this value added service. They are also responsible for the calculation of the emissions related to the shipments. They are to be compensated by CM according to a method agreed between the BU and CM and verified by an independent third party. The BU report their carbon emissions (and at the same time their carbon demand) to CM on a quarterly basis and pay a previously agreed price for each ton of carbon to CM.


Carbon credits are handled by internal and external abatement projects. Internal projects are represented by alternative vehicles using alternative or (partly biogenic) renewable—fuels. Energy efficiency projects or green energy transport such as solar panels on some of the hubs is also included in the internal carbon portfolio.


It is advantageous to purchase verified emission reductions from voluntary or Kyoto abatement projects.


The focus of this manual lies on those processes, that are relevant for carbon accounting. These processes and the data produced in these processes need to be verified by an independent third party.


The core operation processes related to carbon management are detailed further in the operation process map in FIG. 7. FIG. 7 comprises a first portion 700 (FIG. 7a) and a second portion 702 (FIG. 7b). The operation process map is further divided in four parts to represent the processes within the participating BU on the demand side (top part 704), the processes within CM (second part 706) and the processes for purchasing carbon credit from internal (third part 708) and external (bottom part 710) projects.


Certain processes and their data need to be verified. Examples of such processes and data include a calculate emissions footprint process 2 (FIG. 7a), an emission footprint methodology 2.1 (FIG. 7a), quarterly demand reports 6 (FIG. 7a), a carbon credit demand ledger 7 (FIG. 7a), a carbon credit supply ledger including retirement 8 (FIG. 7a), a purchase internal credits process 9, a purchase external credits process 10, an annual demand report for verification 20 (FIG. 7a), an annual report/diploma to customer 21, a comply with DPWN's quality criteria process 12 (FIG. 7b), quarterly supply reports 14 (FIG. 7b), a comply with DPWN's quality criteria process 16 (FIG. 7b) and a supply delivery note 18 (FIG. 7b) to name a few examples. Each of the highlighted processes is further detailed afterwards.


Operation Process Details

This chapter describes the individual operation processes that have been outlined in the previous chapter in greater detail.


The description distinguishes between those core processes that are relevant for the carbon accounting and those supplementary processes not relevant for the carbon accounting but necessary for the functioning of the system like the financial accounting processes.


Emissions Footprint Methodology (Process-2.1)

The BU that plans to offer GO GREEN products or services is responsible for specifying emission values for their products or services which should be done according to the steps and the two different methodologies specified in this chapter.


The following steps should be adhered to when introducing new GO GREEN products or services:

    • The BU describes the planned GO GREEN products or services at least including the following information:
      • name and type of product or services
      • expected emissions per product and service (emissions footprint)
      • choice of calculation method (bottom-up, top-down)
      • expected volume of services sold to customers
      • expected number of carbon credits needed for compensation
    • The BU reports to CM on a chosen methodology and encloses proper documentation according to this manual.
    • CM performs a plausibility check on the calculation and the documents and informs the BU of the results.
    • CM and the BU agree on the methodology to calculate the emissions footprint.
    • CM includes a description of the agreed methodology in this manual.
    • The relevant section of the manual as well as the calculation files and the documentation are referenced in the service level agreement (SLA) between the BU and the CM.


      CM uses two different methodologies for the calculation of direct carbon emissions from the product and services. Neither emissions of other greenhouse gases nor the life cycle assessment data is taken into consideration for the emission footprint of products and services. For both methodologies carbon is added to cover the carbon emissions from the facilities (hubs etc.).
    • 1. In the bottom-up approach specific carbon emissions per shipment are calculated ex-post based on the emissions of the vehicles used for transportation, the loading factors and allocated to the shipments transported using the NTM formula (see sub-section 0).
    • 2. In the top-down approach average carbon emissions per shipment are calculated ex-ante in case-studies based on more aggregated variables like for example the overall national fuel consumption (accountable for the shipments) of the BU divided by the total number of shipments (see sub-section 0).


The implementation (calculation, sources and values) of these methodologies is described in section 0.


Emissions Footprint Methodology (Process-2.1)—Bottom-up Approach
A) Purpose and Scope

This section describes the general methodology in the bottom-up approach. This methodology is used when systems within the operation (i.e. operational- and billing systems) and provides specific data required for emission calculations. Calculations are made on shipment level and take each movement into consideration.


If this Bottom-up approach is used, it is advantageous to perform a validation test report with the results from the calculation.


B) Description

The used methodology takes into account all direct emissions related to the transport of the shipments from the fuel combustion in the vehicles including those of the vehicles used by subcontractors. In a first step this relates to carbon emissions. For the carbon emissions from the facilities (hubs etc.) a fixed average value is added. The methodology does neither consider additional emissions in the life cycle of the fuels nor emissions of other greenhouse gases.


For the calculation of the transport emissions per shipment the method distinguishes between emission calculation and emission allocation. Emission calculation is defined as the calculation of the total vehicle emissions related to the use of the different modes of transport, whereas emission allocation relates to the allocation of these emissions to individual shipments. The distinction is necessary because typically a vehicle transports more than one shipment for the different distances and its emissions therefore need to be shared by the individual shipments.



FIG. 8 gives generic example 800 of typical legs of different shipments. The transport is divided into a (different) number of legs according to the different transport modes used on the way from its origin to its destination.


Taking into account the above outlined factors and the division of the shipments into different legs the carbon emissions related to each shipment can be calculated according to the following general principle:

    • 1. Calculate the distance for each leg
    • 2. Calculate the fuel consumption of the vehicle used for each leg
    • 3. Calculate the total emissions of the vehicle depending on vehicle type, engine type and fuel consumption for each leg
    • 4. Allocate the emissions to each shipment, based on volume weight of the shipment and the load capacity and fill factor of the vehicle used for each leg
    • 5. Add the emissions from the different legs of the shipment
    • 6. Add the emissions from all shipments per product and customer ID



FIG. 9 shows a formula 900 for the calculation of carbon emissions for each leg. Based on these general principles set forth above, the applied formula to calculate the carbon emissions for each leg from each shipment is shown in FIG. 9:


The factors used in this formula for the emission calculation are explained in Table 19.









TABLE 19







Factors for the calculation of carbon emissions


for an individual leg of a shipment









Factor
Explanation
Unit





Distance
Distance for each leg of the shipment.
km


Fuel consumption
(Average) fuel consumption of specific
l/km



vehicle type.


Variable
Specific emission factor for the vehicle
g/l


emission
and fuel used in the specific leg.


factor


Fixed emissions
(Average) value for specific air plane
g


value
types: only used for air transports to



account for the higher emissions during



take-off and landing.


Loading Capacity
Maximum payload of the vehicle used.
t


Loading Factor
(Average) share of loading capacity that
%



is actually used.


Volume
Measure to account for bulky (low density)
t


Weight
shipments.


Fixed emissions
Used to account for the average direct
g


value
carbon emissions of facilities like hubs


for facilities
etc.









For further explanation of some of these terms see the glossary.


Depending on information availability different it is possible, to either use generic values or specific values for some of the factors in the calculation formula (mentioned within brackets in the table above).


Emissions Footprint Methodology (Process-2.1)—Top-Down Approach
A) Purpose and Scope

This section describes the general methodology of the top-down approach. Using this methodology the total carbon emissions of a specific network and all its transports is calculated, based on available overall data. Carbon emissions per product (shipment) are calculated by allocating the relevant share of emissions to each product.


B) Description

This methodology is based on case-studies, which use different data depending on the data and the specific IT-systems available in the relevant BU and countries. The output of the calculation is an average value for the direct carbon emission per product or service. The emission value shall be calculated ex-ante and reviewed on an annual basis.


The performance of the case study follows the steps below. The most important is to document each step and sources to ensure transparency:

    • 1. Identify and specify network for relevant product and services (with GO GREEN offer).
    • 2. Gather needed data from network such as actual fuel consumption. If fuel consumption is not available a model of the network should be constructed by describing i.e. transport kilometres, vehicle types, loading factors,
    • 3. Gather data from product and services (with GO GREEN offer) such as volume and weight if relevant for allocation purposes.
    • 4. Add an estimated value to cover emission from facilities etc.


The minimum requirements for the documentation are as follows:

    • transparent and clearly structured Excel spreadsheet including a reference to the relevant data sources
    • a brief verbal description of the calculation and the data sources (could be included in the Excel spreadsheet)
    • a description on whether and how the calculated average emission values were checked for plausibility by alternative calculations or comparison to other available data
    • a printout of the data sources used or information on how it can be obtained by the CM and the verifier (e.g. hard copies or hyperlinks in case of published studies, name and contact data of the staff responsible in case of internal software systems)
    • a description on whether and how the internal data sources have been or can be checked for plausibility


Calculate Emissions Footprint (Process-2)
A) Purpose and Scope

This section and its sub-sections describe the implementation of the general emission calculation methodologies described in section 0 to be used by individual BU for their different products and services.


B) Implementation

An overview on the applied methodology per BU and respective GO GREEN products and services is shown in Table 23:









TABLE 20







Overview on the applied methodologies in the BU










Described in
Methodology










Operation unit
sub-section
Bottom-up
Top-down





DHL Express
0
TD International



Europe


DHL Express
0
TD International
TD Domestic


UK

(described
and DD International




in 0)
and





Domestic


Deutsche Post
0

Small Parcel


Germany


(Green





PlusPackchen)









Further products and further BU can be easily included as additional sub-sections.


Calculate Emissions Footprint (Process-2)—TD International Products
A) Purpose and Scope

This sub-section describes the implementation of the general methodology described in sub-section 0 to be used by DHL Express Europe for the TD International product line. For the following products GO GREEN can be chosen as a value added service: TDD, ECX, DOX and WPX.


B) Implementation


FIG. 10 shows a schematic representation 1000 of data flows for emission calculating according to a preferred embodiment of the invention. To automate the emission calculation, DHL Express uses the software ACCEPT (Automated Customer Calculation of Environmental Performance Tool). ACCEPT calculates the emissions ex post. Data from the relevant IT-systems are imported into ACCEPT. FIG. 10 outlines the data flows for emission calculation using ACCEPT.


Table 24 summarizes an explanation of the data types (individual or average) and the data sources (software system, case study etc.) for the variables used in the calculation formula (see also Table 22 and FIG. 9).









TABLE 21







Data sources for the different factors of the calculation


formula









Factor
Data Type
Data Source





Distance
Specific
Distance tables within the ACCEPT describe the




distances between frequented airports. The




source for distances is an internal application




plus a suitable web site e.g.:




http://www.bestflights.com.au/airportdist/calc.php


Fuel
Specific
Based on NTM values for fuel usage.


con-
for
NTM - ENVIRONMENTAL DATA FOR


sumption
different
INTERNATIONAL CARGO TRANSPORT



aircraft
Calculation methods - mode specific issue;



types and
AIR transport; VERSION 2005-04-15



their



load


Variable
As above
As above


emission


factor


Fixed
As above
As above


emissions


value


Loading
As above
As above


Capacity


Loading
Average
Calculated average based on most


Factor

frequently used aircraft types.


Volume
Specific
The weight of each shipment is derived from


Weight

the OPMS.


Fixed
Average
Based on case studies of energy utilization


emissions

of facilities and the number of shipments


value for

handled.


facilities









All default and average values used in the calculation are reviewed on an annual basis by the BU. The result of the review is reported to CM in a suitable format as described in this patent application.


Calculate Emissions Footprint (Process-2)—DHL Express UK, DD Domestic
A) Purpose and Scope

This sub-section describes the implementation of the general methodology described in sub-section 0 to be used by DHL Express UK. for TD domestic and DD international and domestic products. The products offering GO GREEN as a value added service are listed in Table 25 below.









TABLE 25







Example of Products with GO GREEN value added service


available










Area
Product







TD Domestic
Diamond




Omega 12




TDD (9 and 12)



DD
Europak



International
Europlus



DD Domestic
NextDay




DHL @home




DHL Network Express










It is possible to automatically create reports stating the direct carbon emissions compensated within the GO GREEN program for each single customer.


B) Implementation

The direct carbon emissions are preferably calculated in a top-down approach. An exemplary network/transport process 1100 used for the relevant products is described in FIG. 11.



FIG. 11 displays an advantageous network structure, which is especially useful for the handling of Express Parcels as a preferred example of the physical objects. It shows various transport legs from a pick-up of the physical object (especially an express parcel) at a first physical unit to a desired destination via several nodes. At each node a processing of the physical object occurs. Examples of the processing are sorting or routing. For each leg an appropriate means of transport will be selected following certain parameters, such as environmental parameters.


By way of example, the direct carbon emissions for the transport of a single transported physical object are shown for the different sub-processes, especially for the transport according to a leg.


The average emissions for the different products derived with the method described above are shown in Table 26:









TABLE 26







Average emissions per product











Average kg



Product
CO2/shipment







Diamond




Omega 12



TDD (9&12)



Europak



Europlus



NextDay



DHL@home



DHL Network



Express










All default and average values used in the calculation are reviewed, updated, reported and documented.


Preferably the central control computer performs the gathering and documenting of the relevant data based on data from sub-systems as local hosts. The central control computer performs the calculations to determine carbon emissions from shipments—especially from shipments relating to a certain BU—and ensures that the calculations and data sources are transparent and verifiable for an independent third party. The central control computer checks the plausibility of the results of the calculations in a vertical and horizontal approach.


Calculate Emissions Footprint (Process-2)—DHL Express Germany, Retail
A) Purpose and Scope

This sub-section describes the implementation of the general methodology described in section 0 to be used by DHL Express Germany Retail for parcels. This individual implementation of the methodology is valid for the calculation of direct carbon emissions for shipments performed for retail customers in its post offices and other outlets. It is possible to offer GO GREEN to all retail customers. Some of these products are small parcels, afterwards called GO GREEN PlusPackchen.


B) Implementation

The GO GREEN parcel will be sold to retail customers via the existing post offices in Germany. The number of GO GREEN PlusPackchen sold can be derived from the billing and accounting systems used.


The direct carbon emissions are calculated in a top-down approach.


The calculations behind each of the sub-processes are described and documented in a file. This file also documents the data sources and assumptions for the different sub-processes.


To account for any uncertainties in the data sources and the calculation the figure of 577 g CO2 per shipment is rounded to

    • 0.65 kg CO2 per shipment.


This value should be entered in the quarterly demand report by DHL Express Germany.

All default and average values used in the calculation are reviewed on an annual basis by the BU. The result of the review is reported to CM in a suitable format, stored and documented.


The central control computer is responsible for gathering and documenting the relevant data from the systems. The central control computer performs the necessary calculations to determine carbon emissions from the shipments and ensures that the calculations and data sources are transparent and verifiable for an independent third party. The central control computer furthermore checks the plausibility of the results of the calculations in a vertical and horizontal approach.


Quarterly Demand Reports (Process-6)
A) Purpose and Scope

This section describes the quarterly demand reports that are used by the BU to communicate their carbon credit demand for the past quarter to CM.


Details on which data fields are used are described in Table 27 below.


B) Implementation

The quarterly demand report consists of a protected Excel file. The structure and format is defined by CM. Changes can only be implemented by CM.


The quarterly report shall be stored by the central control computer on a net-drive


It is preferred to save the quarterly demand reports as read-only files to eliminate the risk of later unintended changes to the data.


Table 27 explains the data fields in the quarterly demand report and shows which BU uses the different data fields.









TABLE 27







Data fields in the quarterly demand report to be


filled by BU









Data Fields
Explanation
User





Operation
Unique name of the Operation Unit.
all BU


Unit Name
The name should be identical for



all reports of the specific BU.


Year
Year for which the report is
all BU



valid.



(Formatted as YYYY, e.g. 2006)


Quarter
Quarter of the year for which the
all BU



report is valid.



(Formatted as QQ, e.g. 03)


Customer
Name of the customer, who purchased
for customers,


Name
the value added service GO
that



GREEN for one or all of his products
receive a



used. Enter at least one line
diploma



per customer.
for SME



This information is also used to
customers



print the diploma for the customer.



Enter the full (legal) name



as it should appear on the diploma.



For SME customers “SME Customer”



is entered in this cell.


Volume of
Total number of shipments per customer.
all BU


Shipments
For BU without contract



customers this is the total number



of all shipments.


CO2 per
State the average carbon emissions
only for BU


Shipment
of an individual shipment.
with average



If actual values for each individual
carbon



shipment are calculated expost
emissions



by the BU this data field remains
per shipments



void.


Total CO2
For BU with average carbon emissions
all BU



per shipment this is automatically



calculated as product of



“Volume of shipments” and “CO2 per



Shipment”.



BU with contract customers over-



write the formula in the template



with the total emissions calculated



by their respective IT-



systems.


Price per t
Price per t CO2 as agreed in the
all BU


CO2
contract (Service Level Agreement -



SLA) between the BU and CM.


Total Costs
This is automatically calculated
all BU



as product of “Total CO2” and



“Price per t CO2


Preferred
Big corporate contract customers
only BU


method of
will in very special cases be allowed
with contract


com-
to choose a preferred method
customers


pensation
of compensation, e.g. solar or a



forestation. (Not to be marketed



actively and to be discouraged.)









Carbon Credit Demand Ledger (Process-7) and Demand Summary (Process-20)
A) Purpose and Scope

This section describes the carbon credit demand ledger that is used by CM to aggregate the quarterly demands from different BU. The carbon credit demand ledger is valid only for CM.


B) Implementation

The carbon credit demand ledger is a file with several spreadsheets, for example:

    • Carbon demand ledger
    • Carbon demand summary
    • Shipment volume summary
    • Plausibility check demand
    • Data for diploma
    • BU billing


The use of these spreadsheets is described in this patent application. The carbon credit demand ledger could for example be created as an Excel file.


Carbon Demand Ledger

The Carbon demand ledger contains preferably the same data fields as the quarterly demand reports by the BU (see Table 27). The additional data fields for use by CM are described in Table 22.









TABLE 22







Additional data fields in the carbon credit demand


Ledger











Data Fields
Explanation
User







Supply/Demand
Default value is “demand”.
CM



Reference ID
Unique serial number in the format
CM




D-“XXXX”,




e.g. D-0001 (D for demand)



Date
Date of the data transfer into
CM




the carbon credit demand ledger



By (Name)
Person transferring the data into
CM




the carbon credit demand ledger



Date payment
Date of the receipt of the payment
CM



received by
for the compensated carbon



BU
emissions










To transfer the data from the quarterly demand report to the carbon demand ledger the following steps are required:

    • On receiving the quarterly demand reports CM files them on a net-drive under a new name by adding “-CM” at the end of the filename.
    • CM checks that the data reported are plausible and consistent. This is especially important for the data fields operation unit name, customer name, product ID/code—and if applicable—CO2 per shipment, because the reporting is based on these data fields. CM corrects obvious typing errors and clarifies ambiguous cases with the relevant BU.
    • CM checks the serial number for the last entry in the carbon credit demand ledger.
    • CM adds in the newly filed quarterly demand reports the next reference ID, demand, the date of the data transfer to the carbon credit demand ledger and the name of the person transferring the data.
    • CM prints the quarterly demand reports and files a hard copy as part of the documentation. CM notes the reference ID in the carbon demand ledger on each print-out.
    • CM copies all data from the quarterly demand reports of all BU into the carbon credit demand ledger.
    • CM files at least a quarterly backup copy of the carbon credit demand ledger on a net-drive under a new name.


Based on the data in the spreadsheet carbon demand ledger the other spreadsheets provide demand reports, plausibility checks and the data for the certifications.


Carbon Demand Summary

The carbon demand summary automatically summarizes the demand per BU on a quarterly and annual basis. The summary is for example implemented in an Excel pivot table. The carbon demand summary is used as basis for the quarterly transfers of the aggregated demand into the carbon credit supply ledger for retirement as well as the annual report to the verifier.


After all quarterly bookings have been performed in the carbon demand ledger CM prints and files a hardcopy of the carbon demand summary.


Shipment Volume Summary

The shipment volume summary automatically summarizes the total volume of shipments per BU on a quarterly and annual basis. The summary is implemented in an Excel pivot table. The data are used for the plausibility check.


Plausibility Check Demand

The plausibility check demand automatically calculates the average CO2 emissions per shipment on a quarterly and annual basis. The calculation can be used for a plausibility check in a vertical and horizontal approach. The calculation only works properly, if both pivot tables Demand of Carbon (t) on the spreadsheet carbon demand summary and Number of Shipments on the spreadsheet shipment volume summary show the equivalent selections of Operation Unit Name, Preferred Compensation, Quarter and Year. After all quarterly bookings have been performed in the carbon demand ledger CM prints and files a hardcopy of the plausibility check demand.


Carbon Credit Supply Ledger Incl. Retirement (Process-8)


A) Purpose and Scope

This section describes the carbon credit supply ledger that is used by CM to aggregate the quarterly supply from different internal abatement projects and externally purchased credits as well as to retire carbon credits according to the quarterly demand. The carbon credit supply ledger is valid only for CM.


B) Implementation

The carbon credit demand ledger is an Excel file with several spreadsheets:

    • Carbon supply ledger
    • Project balance summary
    • Project portfolio
    • Auxiliary calculation
    • Project invoice


The use of these spreadsheets is described in the following paragraphs.
Carbon Supply Ledger

The carbon supply ledger contains the same data fields as the quarterly supply reports by the BU (see Table 31). The additional data fields for use by CM are described in Table 29.


In the carbon supply ledger both supply and aggregated demand are accounted. Supply is booked with positive values as credit entries. Demand is booked with negative values as debit entries.


Based on the data in the carbon supply ledger the other spreadsheets in this file provide an up-to-date balance for all abatement projects, an overview over the project portfolio and auxiliary calculation for accounting purposes.


Project Balance Summary

The project balance summary automatically summarizes the balances per abatement project on a quarterly and annual basis. The summary is implemented in an Excel pivot table with an additional calculation of the cumulative quarterly balances. The project balance summary is used as basis for the annual report to the verifier. For the second year of operation the balance of the previous year is entered in the project balance summary by hand.


Project Portfolio

The project portfolio automatically calculates the share of the individual abatement projects in the project portfolio on a quarterly and annual basis. The summary is implemented in an Excel pivot table with an additional calculation of the cumulative quarterly balances.









TABLE 23







Additional data fields in the carbon credit supply


ledger









Data Fields
Explanation
User





Supply/Demand
Default value is “supply”.
CM


Reference ID
Unique serial number in the format
CM



S-“XXXX”,



e.g. S-0001 (S for supply) in



case of data from quarterly supply



reports.



Reference ID taken from carbon



credit demand ledger in case of



data from quarterly demand reports



for customers with a preferred



method of compensation.



Unique number in the format QD-



“QQ”-“YYYY”,



e.g. QD-0001 (QD for aggregated



quarterly demand, with “QQ” for



number of the quarter, “YYYY” for



year) in case of quarterly demand



without preferred method of compensation.


Date
Date of the data transfer into
CM



the carbon credit supply ledger


By (Name)
Person transferring the data into
CM



the carbon credit supply ledger


Date value
Date of the payment for the delivered
CM


paid to BU
carbon credits to BU









Auxiliary Calculation

The auxiliary calculation automatically calculates the share of the total quarterly demand (without preferred method of compensation) that has to be booked on each of the abatement projects in the portfolio. It therefore automatically takes off the quarterly demand data from the demand ledger.


Accounting Processes

The processes for accounting carbon credits in the carbon credit supply ledger are illustrated and further explained in Table 30









TABLE 24







Explanation of processes for accounting carbon


credits in the carbon supply ledger









Step
Explanation
Files/tables





14
Quarterly supply report:
Excel files from every abatement



Quarterly supply reports
project:



as described in sub-
QSR-“Project-Name”-“YYYY”-



section 0
“QQ”.xls


18
Supply delivery note:
Document with delivery details



Supply delivery notes as
depending on contractual



described in sub-section
arrangements



Error! Reference source



not found.


 7
Carbon credit demand
Excel file:



ledger:
Carbon_demand_ledger_V1.0.xls



Carbon credit demand



ledger as described in



sub-section 0 including



the carbon credit demand



entries for the relevant



(past) quarter.


8-1
Check supply data
Excel files from every abatement



quality:
project:



On receiving the
QSR-“Project-Name”-“YYYY”-“QQ”-



quarterly supply reports
CM.xls



CM files them on a net-



drive under a new name by



adding “CM” at the end of



the filename.



CM checks that the data



reported are plausible



and consistent. This is



especially important for



the data fields operation



unit name and project



ID/name because the



reporting is based on



these data fields. CM



corrects obvious typing



errors and clarifies



ambiguous cases with the



relevant BU.



CM prints the quarterly



supply reports and files



a hard copy as part of



the documentation. CM



notes the reference ID in



the carbon supply ledger



on each print-out.


8-2
Copy supply data in
Data copied from:



supply ledger:
Excel files from every abatement



CM checks the serial
project:



number for the last entry
QSR-“Project-Name”-“YYYY”-“QQ”-



in the carbon credit
CM.xls



supply ledger.
to:



CM adds in the newly
Excel file:



filed quarterly supply
Carbon_demand_ledger_V1.0.xls,



reports the next
table carbon supply ledger



reference ID, supply, the



date of the data transfer



to the carbon credit



demand ledger and the



name of the person



transferring the data.



After that the data are



copied for each abatement



project from the



quarterly demand reports



into the table carbon



supply ledger.


8-3
Check for preferred
Excel file:



compensation:
Carbon_demand_ledger_V1.0.xls,



Since it will be possible
table carbon demand summary



that a big corporate



contract customer will



opt for a preferred



method of compensation,



these customers have to



be identified and their



demand must be booked



before the remaining



demand is booked.



Wether there are



customers with preferred



compensation can most



easily be checked in the



table carbon demand



summary. Here preferred



compensation is shown as



an extra line for the



operation unit(s) with



the relevant customer(s).



If there is no preferred



compensation the next



step is 8-6. The steps



8-4, 8-5 and 8-7



are skipped.


8-4
Copy preferred compensation
Data copied from:



data in supply ledger:
Excel file:



If there is preferred
Carbon_demand_ledger_V1.0.xls,



compensation, the individual
table carbon demand ledger



entries have to be identified
to:



in the table carbon demand
Excel file:



ledger by filtering in the
Carbon_supply_ledger_V1.0.xls,



column preferred compensation.
table carbon supply ledger



For each demand entry with



preferred compensation in the



the carbon demand ledger for



that quarter the data field



project ID/name is filled with



relevant project ID/name in a



new line of the table carbon



supply ledger and the fields



year and quarter are filled



with the relevant information.



CM than copies the data on



Total CO2 and Reference ID from



the relevant dataset with the



preferred compensation in the



carbon demand ledger to the new



line in the table carbon supply



ledger. The data on Total CO2



have to be entered with a



negative algebraic sign as a



debit entry.



The remaining data fields date



and By (name) are filled with



the relevant information.



This is repeated for each



customer with preferred



compensation.


8-5
Exclude preferred
Excel file:



compensation from demand
Carbon_demand_ledger_V1.0.xls,



summary:
table carbon demand ledger



In order not to double-



count the entries with



preferred compensation



after they have been



booked individually they



have to be excluded from



the calculation in the



carbon demand summary.



This is done by



deselecting the relevant



preferred compensations



in the carbon demand



summary.


8-6
Copy auxiliary
Excel file:



calculation within supply
Carbon_supply_ledger_V1.0.xls,



ledger:
table auxiliary calculation



In order to “freeze” the



number of credits and



their shares to be booked



on each of the abatement



projects the complete



table auxiliary



calculation is copied



within the carbon supply



ledger after refreshing



the data in the pivot-



tables. Following that,



the formulas in the



copied table have to be



replaced by their results



(copy and paste as



values). The copied table



is renamed AC-“YYYY”-



“QQ”.



After renaming the table



it is printed and filed



as a hard copy as part of



the documentation. CM



notes the reference ID in



the carbon supply ledger



on each print-out.


8-7
Include preferred
Excel file:



compensation in demand
Carbon_demand_ledger_V1.0.xls,



summary:
table carbon demand ledger



After copying the table



auxiliary calculation the



preferred compensation



can be reincluded in the



demand summary.



This is done by selecting



the relevant preferred



compensations in the



table carbon demand



summary again.


8-8
Book demand from auxiliary
Excel file:



calculation in supply
Carbon_supply_ledger_V1.0.xls,



ledger:
table carbon supply ledger



From the print-out of the



table auxiliary



calculation the carbon



demand is booked in the



table carbon supply



ledger.



For each abatement project



in the portfolio the



fields project ID/name,



quarter and year is



entered in a new line of



the table carbon supply



ledger. Than the demand



per abatement project is



booked with a negative



algebraic sign as a debit



entry. In the data field



Supply/Demand “Demand” is



entered. The data field



Reference ID is filled



with QDS-“YYYY”-“QQ”.



The remaining data fields



Date and By (name) are



filled with the relevant



information.



This is repeated for each



abatement project.


8-9
Copy project balance
Excel file:



summary within supply
Carbon_supply_ledger_V1.0.xls,



ledger:
table project balance summary



In order to “freeze” the



project balance summary



the complete table



project balance summary



is copied within the



carbon supply ledger



supply ledger after



refreshing the data in



the pivot-tables.



Following that, the



formulas in the copied



table have to be replaced



by their results (copy



and paste as values). The



copied table is renamed



PBS-“YYYY”- “QQ”.



After renaming the table



the table is printed and



filed as a hard copy.


8-10
Backup carbon supply
Excel file:



ledger:
Carbon_supply_ledger_V1.0_YYYY-MM-DD.xls



After booking all



quarterly entries CM



files at a quarterly



backup copy of the carbon



credit supply ledger on a



net-drive under a new



name by adding the date



of the backup in the



format “-YYYY-MM-DD” at



the end of the filename.









If the carbon supply ledger contains CER (and VER managed in external registries) the relevant amount retired in the supply ledger for the relevant projects need to be retired in the official CDM registry (and the VER registry if applicable) as well. This should be done at least annually, better quarterly, after the internal carbon accounting for the quarter is terminated by CM.


CER refers to rights to emission carbon. VER refers to Verified Emission Reduction data.


The relevant documents for the retirement in the above mentioned registries are filed on net-drives or as hard copies as part of the carbon credit accounting documents.


Purchase Internal Credits (Process-9)
A) Purpose and Scope

This section describes the initiation of purchasing internal credits by CM or BU. The description focuses on the perspective of CM.


B) Implementation

The purchase of internal credits can be managed by the system according to the invention.


Based on the forecasted supply and demand the central control computer checks regularly (at least quarterly), whether there is a sufficient future supply of credits to balance the expected future demand.


Additionally the project portfolio should have a balanced mix between projects from different geographical areas and different types of technology used for abatement.


In most cases it is possible to avoid a purchase of external emission credits. However, if it is necessary to purchase external emission credits, the following procedure applies.


Purchase External Credits (Process-10)
A) Purpose and Scope

This section describes the initiation of purchasing external credits by CM.


B) Implementation

Whether and when to purchase external credits is decided by CM. In this case a credit purchase agreement between a logistics company and a seller of the external carbon credits is integrated in the carbon management process.


Project Proposal by Project Owner/Project Idea Note (Process-11/11.1)
A) Purpose and Scope

This section describes the documentation needed for internal abatement projects. The section is valid for all internal suppliers (BU) of carbon credits.


B) Implementation

It is preferred to check the compliance of the internal projects with the quality criteria for internal projects and to integrate and automate the supply of internal credits.


Comply with Quality Criteria for Internal Credits (Process-12)
A) Purpose and Scope

This section describes the quality criteria used by for internal abatement projects. The quality criteria are valid for the central control computer and all internal suppliers (BU) of carbon credits.


B) Implementation

The following quality criteria apply for internal projects:

    • Carbon emissions are truly reduced.
    • The project is additional.
    • The emissions are abated by using clearly defined approaches and technologies.
    • The approach and the technologies are described and documented.
    • The calculation of carbon credits is done according to clear and previously defined standards. A baseline scenario is defined and justified.
    • All information relevant for the project is documented in transparent and plausible form.
    • The purchase of credits is handled in a SLA between CM and the BU.


The relevant information is filed on a net-drive or as hardcopy.


Quarterly Supply Reports (Process-14)
A) Purpose and Scope

This section describes the quarterly supply reports that are used to communicate carbon credit supply from abatement projects for the past quarter.


B) Implementation

The quarterly demand report consists of a protected file. Table 31 explains the data fields in the quarterly demand report.


There are three further data fields in the report for accounting purposes.









TABLE 25







Data fields in the quarterly supply report to be


filled by BU










Data Fields
Explanation







Operation
Unique name of the Operation Unit. The name



Unit Name
should be identical for all reports of the




specific BU.



Project
Unique ID or name for the project. It is defined



ID/Name
by CM and uses the following schema:




“E/I”-“Project-Type”-“NN”




With:




“E/I = alternative use of “I”




for internal




and “E” for external projects




“Project-Type” = e.g. afforestation, biogas,




RME, solar etc.




“NN” = serial number per project




type



Year
Year for which the report is valid.




(Formatted as YYYY, e.g. 2006)



Quarter
Quarter of the year for which the report is




valid.




(Formatted as QQ, e.g. 03)



Total Activity
Sum of all activities in the project:



Rate
total of all kilometres driven by all alternative




vehicles of one technology in




km (in case of alternative vehicle projects)




total solar power transport in kWh (in




case of solar projects)



Specific
Specific emissions of the baseline technology:



emissions
measured in kg CO2/l (in case of other



baseline
vegetable oil vehicle projects)




measured in kg CO2/km (in case of other




alternative vehicle projects)




measured in kg CO2/kWh (in case of solar




projects)




The relevant information can be taken from the




project idea note as described in section 0.



Specific
Specific emissions of the project technology:



emissions
measured in kg CO2/l (in case of other



project
vegetable oil vehicle projects)




measured in kg CO2/km (in case of other




alternative vehicle projects)




measured in kg CO2/kWh (in case of solar




projects)




The relevant information can be taken from the




project idea note as described in section 0.



Total CO2
This is automatically calculated as product of




“Volume of shipments” and “CO2 per Shipment”.



Price per t
Price per t CO2 as agreed in the contract (SLA)



CO2
between the BU and CM.



Total Value
This is automatically calculated as product of




“Total CO2” and




“Price per t CO2










Negotiation to Purchase Carbon Credits/Project Description (Process-15/15.1) Comply with Quality Criteria for External Credits (Process-16)
A) Purpose and Scope

This section describes the quality criteria used during the negotiations to purchase external credits for choosing the qualifying projects. The quality criteria are valid for CM and all external suppliers of carbon credits.


B) Implementation

For both credibility and practical reasons the same strict standards of additionality as the Kyoto protocol stipulates apply for the credits bought from external projects.


With additionality is generally meant that the project would not have happened unless there was the additional incentive of an extra income stream from the value of the generated credits. The project should not represent operation-as-usual.


Baseline emissions would equal project emissions in this case. Hence a project needs to prove its additionality by showing that is not operation-as-usual.


The credits should at least strive for being VER (Verified Emission Reductions) by an independent third party. Possible standards to be used as the basis for the verification are for example the “GHG Protocol for Project Accounting” by WBCSD/WRI, the “Gold Standard” by a number of NGO (BASE), the “Voluntary Carbon Standard” by IETA and the JI and CDM-Project Cycle defined by the Kyoto Protocol.


From this framework the following quality criteria for external projects are used:

    • Carbon emissions are truly reduced.
    • The project is additional.
    • Leakage is accounted for.
    • The emissions are abated by using clearly defined approaches and technologies. CM allows the purchase from all project types that are acceptable under the Kyoto framework.
    • The approach and the technologies are described and documented.
    • The calculation of carbon credits is done according to clear and previously defined standards. A baseline scenario is defined and justified.
    • All information relevant for the project is documented in transparent and plausible form.
    • The compliance of the project with the chosen standards is documented and verified.
    • The verification report is provided by the project owner.
    • Carbon credits are traceable.
    • The purchase is handled in a credit purchase agreement.
    • CM is responsible to gather the relevant information during the negotiations with the seller in order to judge the compliance of projects from which credits potentially will be bought. The relevant information is filed on a net-drive or as hardcopy. Ideally the relevant information is documented in a comprehensive project description.


The results of the compliance check are documented.


Contract on Internal Carbon Supply Project (Service Level Agreement—SLA) (Process-13)
A) Purpose and Scope

This section describes the main contents of the SLA between BU owning internal carbon supply projects and CM.


B) Implementation

The following carbon management specific aspects should be covered by the SLA:

    • Define the reporting requirements by the operation unit with quarterly supply reports
    • Define the responsibilities of the parties
    • Name the persons responsible within the parties
    • Define the legal nature of credits
    • Determine the price per ton of carbon dioxide payable to the project owner
    • Define the modalities of payments


Quality Assurance
A) Purpose and Scope

This chapter describes the measures taken to assure the quality and safety of the data used.


B) Implementation

The systems used for gathering data to calculate carbon emissions in the BU underlie a quality assurance system on their own, since they are used for transport control, billing and accounting purposes.


The following measures are taken additionally to ensure the quality and safety of the data:

    • All data shall be checked for plausibility in a horizontal and vertical approach.
    • Data gathering and calculations shall be performed by one staff member of the BU and/or CM and checked by a second independent staff member. In this way a separation of functions and a double check of the data are achieved.
    • The results of the checks shall be documented in a suitable form in the files or on the hardcopies of the documents.
    • Files shall be stored on net-drive with regular backup.


List of Abbreviations

The following table explains the abbreviations used in this patent application.


Abbreviation Explanation



  • % Per Cent

  • BU Operation Unit

  • CM Computer equipped with software to carry out Carbon Management

  • CNG Compressed Natural Gas

  • D Demand

  • DD Day definite: shipments with a guaranteed day of arrival at the (international) destination

  • DD Day (two digit number) in a date

  • DDD Day definite: shipments with a guaranteed day of arrival at the domestic (national) destination

  • DOX Worldwide Document Express (outside EU)

  • ECX European Document and Parcel Express

  • g Gram

  • GNM Global Network Management

  • ID Identification Number

  • IETA International Emissions Trading Association

  • kg Kilogram

  • km Kilometre

  • kWh Kilowatt hours

  • l Litre

  • MM Month (two digit number) in a date

  • NN Serial number

  • NTM Network of Transport and Environment (Natverket for Transporter och Miljön)

  • OPMS Operations Performance Management System

  • QD Quarterly aggregated demand

  • QQ Quarter (two digit number)

  • PIN Project Idea Note

  • S Supply

  • SLA Service level agreement

  • SME Small and Medium Enterprises

  • t Metric ton

  • TD Time definite: shipments with a guaranteed (latest) time of arrival at the (international) destination

  • TDD Time definite: shipments with a guaranteed (latest) time of arrival at the domestic (national) destination

  • tonnekm product of weight in t and distance in km for a shipment

  • UK United Kingdom

  • YYYY Year (for digit number) in a date

  • WPX Worldwide Parcel Express (outside EU)

  • Term Explanation

  • Carbon Emissions Emissions of Carbon Dioxide (CO2)

  • Contract Customer Typically a big global corporate customer, who negotiated an individual contract with the BU

  • Distance The amount of kilometres the shipment is transported.

  • Fill Factor A value defining to what extent the available capacity is used, also called Utilization Factor. Given as a percentage of the total capacity e.g. 74% fill factor declares that the vehicle is 26% empty.

  • Fixed Emission Value In some calculations e.g. calculation of emissions from air transport, there is a fixed emission value independent of the distance e.g. take off and landing.

  • Fuel Consumption The amount of fuel used per distance unit, normally litres per kilometre. Used for calculating the base fuel consumption for a shipment.

  • Leg The smallest part of the shipment in the transport chain, the part where the same vehicle has the transported goods as its load, e.g. between two terminals.

  • Loading Capacity The maximum weight carried by a vehicle, used together with Volume Weight to define the shipments part of the available capacity.

  • Parcel The smallest defined part of the total shipment bought by the customer.

  • Term Explanation

  • Shipment The total transportation service bought by the customer, the transportation of goods from location A to location B.

  • Transport The transport work done by a vehicle used for one leg in the shipment.

  • Utilization Factor See Fill Factor.

  • Variable Emission Factor In all calculations, there is an emission value totally depending on the distance.

  • Vehicle The means of transportation used, e.g. air plane, lorry, distribution van etc.

  • Volume Weight A calculation of the “cost” in the transport chain for this shipment from the customer. The value is a combination of the weight and the volume and is also used for setting the price to the customer.



Examples for Quarterly Demend Reports

Examples for a quarterly demand report for contract customers












Quarterly Demand Report








To be filled by Business Units
For use by CM only



















Cus-

CO2/

Price/
Total
Preferred
Supply/
Reference

By



tomer
Volume of
Shipment
Total
t CO2
Costs
Com-
Demand
ID
Date
(Name)

















Business Unit Name
Quarter
Year
Name
Shipments
kg
CO2 t

/t




pensation
entered in demand ledger




















DHL Express Europe
03
2006
AAA
123.400

654
20.00
13.080




DHL Express Europe
03
2006
BBB
10.456

199
20.00
3.973


DHL Express Europe
03
2006
CCC
3.456

162
20.00
3.249


DHL Express Europe
03
2006
DDD
12.345

86
20.00
1.728


DHL Express Europe
03
2006
EEE
129.876

5.585
20.00
111.693


DHL Express Europe
03
2006
FFF
8.765

140
20.00
2.805
Solar









Example for a quarterly demand report by DHL Germany Retail for retail customers












Quarterly Demand Report








To be filled by Business Units
For use by CM only
























Cus-
Product

CO2/

Price/
Total
Preferred
Supply/
Reference

By


Business


tomer
ID/
Volume of
Shipment
Total
t CO2
Costs
Com-
Demand
ID
Date
(Name)


















Unit Name
Quarter
Year
Name
Code
Shipments
kg
CO2 t

/t




pensation
entered in demand ledger
























DHL
03
2006

Parcel
15.432.678
0.5
7.716
20.00
154.327







Germary


Retail









Example for a quarterly supply reports for internal abatement projects












Quarterly Supply Report








To be filled by Business Units














Total
Specific
Specific





activity
emissions
emissions

For use by CM only
























rate
baseline
project
Total
Price/
Total
Supply/
Reference

By


Business
Project ID/
Quarter
Year
km
kg CO2/km
kg CO2/km
CO2
t CO2
Value
Demand
ID
Date
(Name)
















Unit Name
Name
Vehicle: Solar:
kWh
kg CO2/kWh
kg CO2/kWh
t

/t




entered in supply ledger























DHL Express
I-RME-01
0003
2006
126.579
0.350
0.045
38.6
10.00
386






Switzerland









In a preferred embodiment of the invention the processing of physical objects takes place in a processing station. In this embodiment, address components that are present on the physical objects are transmitted to an internal data stock. The internal data stock supplies a result address on the basis of the transmitted address components.


Moreover, it is checked whether environmental data were detected. In this case, a selection is made from among the determined environmental data.


Further preferred process steps for the execution of the invention will be explained below. The process steps can be used individually as well as combined with each other, as a result of which the efficiency of the individual process steps is further increased to an especially surprising extent.


A process component that translates into increasing the efficiency of the method with relatively little effort is the implementation of specialized reading software.


A conversion file, which is incorporated into the so-called dictionary of the sorting installation, can implement environmental data. In this manner, if the reading quality is sufficient, then the environmental data are ascertained reliably enough so that the sorting machine is able to sort the physical objects on the basis of the input distribution information (street, optionally house number) and the environmental data.


The environmental data can be applied in different ways, for example, by means of various printing processes. Printing with a fluorescent dye is especially advantageous since this make it possible to especially easily and reliably carry out an optical detection of the target code during a subsequent sorting procedure.


The target code can assume various forms, for example, it can contain environmental data, especially environmental requirement data and other data as for example the complete address information, which is preferably achieved by using an 11-character to 13-character target code with an additional imprint of the postal code in plain text.


However, it is possible to use another code instead of this code, for example, instead of the fluorescent barcode, to use a label with a 4-state code that likewise contains the requisite target information that is in encrypted form and that is applied onto the physical object automatically, preferably in the form of a label. Preferably, the postal code is additionally written on the label in plain text.


In addition to the automated use of the method in processing machines, which are preferably integrated into the normal processing of the physical objects, individual physical objects can also be detected separately, for example, at special processing stations.


Preferably, the individual stations consist of a PC with a monitor and keyboard as well as a label printer as an additional output unit that is controlled by the program and that generates a plain text label or, as an alternative, a 4-state label.


The implementation of the process steps will be explained below with reference to the example of a two-part computer system. However, the invention is not restricted to the especially advantageous case of a two-part computer system presented here.


As a matter of principle, any computer is suitable for carrying out the invention.


The term “computer” is by no means to be understood in a limiting manner. This can be any unit that is suitable for performing computations, for example, a workstation, a personal computer, a microcomputer or circuitry suitable for performing computations and/or comparisons.


Within a preferred embodiment a database is used on a server that takes over the described functions for several processing stations.


The client part is realized in a platform-independent programming language. The use of another programming language is fundamentally possible. The recognizable parts of the data are entered via an input mask. Then a database query is sent by the client to the server.


The server is a powerful computer with several processors and a large main memory. This is necessary in order to achieve very rapid access times.


The data stock consists of the files from a suitable database application containing, at least some environmental data. The design of the database is also configured for rapid access. However, this also means that a great deal of data has to be stored redundantly.


The data accesses are provided by a suitable database application, for example, PL/SQL. Via a PL/SQL procedure, the client receives his result set from the server in the form of data records. The result set is sorted at the client and displayed in a selection list. It can be locally limited by additional entries.


A special feature of the program is that, in a separate list, all environmental data are automatically displayed with the appertaining data for the delivery (post office box, postal code).


A decision module or an operator decides which of the displayed data records (from the normal or, for example, from the special selection list) are applicable in each given case. The decision module or the operator selects this data record and actuates the printing button. Via the locally connected label printer, the appropriate label is printed with the correct address and glued onto the physical object. A decision module is a program module that can observe its environment and that can act largely autonomously. For this purpose, the decision module contains information about the parameters and action instructions that have to be taken into account regarding the procedures. Preferably, the decision module is capable of acting as autonomously as possible.


In a preferred embodiment environmental requirement information attached to the physical object is detected and transmitted to an interface computer. The interface computer contains memory locations for associating the detected images.


The interface computer is connected to a server. The server preferably has the previously presented structure and allows a matching of environmental requirement data with archive able environmental impact data.


The environmental requirement data is detected on the basis of the ascertained image data and by undertaking a database query, or else a data stock query. These queries are made in the form of automated process steps.


This allows obtaining ascertained environmental impact data. This ascertained data is subsequently transmitted to the interface computer.


The interface computer is connected directly or indirectly to the sorting installation.


In a preferred embodiment the interface computer transmits the result data to a result memory of the sorting installation.


The physical objects are preferably associated with the corrected address information by detecting an identification code that identifies them.


Preferably, the identification code was applied onto the physical object in order to allow an association of the new address with the correct physical object.


The identification code makes it possible to associate each of the physical objects with the appertaining environmental requirement data. In an especially preferred embodiment, this is done in that identification codes printed on the physical objects are detected.


It is especially advantageous to print the identification code and/or the environmental requirement data on the physical object.


The printing can be done directly onto the physical object or else by printing a label that is subsequently affixed onto the physical object.


The described implementations of the invention help to analyze environmental impact of transport procedures.


This allows to create a transport system for transporting physical objects, wherein at least one physical object is transported from a sending station to a receiving station, wherein the transport occurs through at least one physical router, wherein the physical router executes a decision about further parameters of transport to another physical router or to the receiving station, wherein environmental data of the transport is calculated and displayed.



FIG. 12 shows a schematic representation 1200 that explains how transactions from different operational systems are managed via a defined interface, where the transactions are verified before they are entered in to the database. FIG. 12 shows an example of output data (emission report) generated according to a preferred embodiment of the invention.


Advantageous Processing Rules for Emission calculations are described afterwards:


The basic principle in the calculations is that the emissions reported to the customer should be calculated down to each transport, considering utilization and capacity of the vehicle.


For international shipments the emissions are managed on country level, i.e. that when a border is passed, the emissions are split equally and allocated to each country.


In ACCEPT there is one fundamental calculation method, used for the highest level of accuracy, this model is defined as follows in a 4-step approach:


For each leg of the transport the following is calculated and then summarized in the reports:

    • 1. Calculate the distance
    • 2. Calculate the fuel consumption of the vehicle
    • 3. Calculate the emissions, depending of vehicle/engine type
    • 4. Allocate the emissions, based on load capacity and fill factor
    • 5. Calculate emissions resulting from facilities involved


The actual calculations can be managed in three different ways, depending on the available data in each country:

    • 1. Manually, using oarameters from ACCEPT
      • The distance is calculated for each transaction using external web products, and then the distance is multiplied with the weight giving the transport work in tonkm. Based on this an “average fleet” can be calculated and then used for the respective customers calculations.
    • 2. Automatically
      • a. Calculate based on average fleet values, “Level 3”
      • b. Calculating fleet average is done by finding out the different vehicle types and their relative part of the total transport work done in the country.
      • Based on this an “average fleet” can be calculated and then used for the respective customers calculations.
      • c. Calculate based on each vehicle, “Level 6”
      • These calculations give a detailed calculation according to NTM level 3 and are verifiable by a third part.


Transports

The calculations of transports are done as follows, the same model applies for Road and Air. When calculating Road there is today no Fixed Emission Value:





Emissions for customer=((Volume Weight/(Max Load Weight*Fill Factor))*(Fixed Emission Value+Variable Emission Value*Distance))*Fuel Consumption


Fuel Consumption

Fuel consumption is gathered, in this order, from the vehicle, vehicle type or more generic parameters


Customer Part of Vehicle Utilization

Calculated as the shipments part of the total available weight capacity and with reference to actual utilization of vehicle





Volume Weight/(Max Load Weight*Fill Factor)


Emission Factor

The emission factor is calculated as the sum of fixed emission values and variable values. The fixed values derive from calculating Air transactions and are set to zero for Road calculations. The variable value is depending of the distance, thus the multiplication





Fixed Emission Value+Variable Emission Value*Distance


Error Management

If data is missing or not correct, ACCEPT either stops the update of this transaction and creates an error message, or uses a less accurate value e.g. using generic Vehicle Type instead the actual vehicle.


Real Estate and Facilities

Emission from e.g. energy usage in facilities can contribute significantly to the emission footprint of a shipment.


The examples describe two levels for implementing;

    • Level 3, based on more generic data
    • Level 6, based on detailed vehicle data


Calculating Road Emissions
Level 3, Based on Generic Data

Using Level 3 the calculations are gathered from the production systems and the transport work is calculated. This transport work is then multiplied with a more generic emission factor which is set from calculating the emissions from the fleet used in the country.


As an example, figures as stated in the table below are used. The rows represent the different vehicle types used;

    • As an example, figures like these are used; where the columns represent the different vehicle types used;
    • For each vehicle type is shown the total transportation work done, in absolute tonkm and in %
    • The capacity, Net Load ton, is calculated by multiplying the Max Load with the Utilization factor. The NTM standard value is indicated in the table.
    • The fuel consumption is taken from NTM values.























Part of

Max load
Net Load
Utilization

Fuel
consumption



Vehicle type
k tonkm
total %
ton
ton
NTM
DHL
l/km
l/tonkm
























H/D
Delivery van
0
0%
1.5
0.75
50%
50%
0.15
0.2000



Distribution


H/D
lorry - Urban
0
0%
8
4
50%
50%
0.25
0.0625



Distribution


H/D
lorry - Rural
0
0%
8
4
50%
50%
0.25
0.0625


H/D
Heavy distribution
66.167
19%
14
7
50%
50%
0.3
0.0429



lorry -



Urban


H/D
Heavy distribution
0
0%
15
7.5
50%
50%
0.3
0.0400



lorry -



Rural


LTL
Lorry + semi-
231.985
66%
40
36.8
75%
92%
0.45
0.0122



trailer


LTL
Tractor + semi-
25.776
7%
28
21
75%
75%
0.38
0.0181



trailer


LTL
Train
30.058
8%


50%
50%



Total
353.987
100%









These are the basic data used for a first country, e.g. Sweden, where the total transport work is split by vehicle type (and performance) and their part of the total.


Level 6, Based on Detailed Vehicle Data

Using Level 6 the transactions/data are gathered from the productions systems and the transport work is calculated. This transport work is then multiplied with the specific vehicle used, considering Euro class, fuel consumption, utilization etc, giving a high quality calculation matching the demands from the more demanding customers. Level 6 calculation requires a subsystem that can feed ACCEPT with the relevant data on vehicles such as e.g. the environmental index used.


In advantageous implementations the calculations will vary from level 3 to 6, giving a result that is much better than level 3 but with less quality than a pure level 6. All this depending on the fact that the transactions from production not always meet the need for level 6 reporting, e.g. COSP does not always identify the vehicle.


For specific customers, depending on their routes, a genuine level 6 quality might be achieved if all transactions are detailed enough.


For specific customers, depending on their routes, a genuine level 6 quality might be achieved if all transactions are detailed enough.


Calculating Air Emissions

Calculating Air emissions are done by from the actual shipment transactions. These transactions include origin and destination, but not the transactions in between. Thus ACCEPT uses a table, CSD, that specifies the different legs in the shipment, as they are planned, deviations from this plan might happen and are not managed by ACCEPT. If there are more than 5 “legs” in a shipment (which is rare) then ACCEPT calculates the last “leg as from last known origin to destination.


Level 3, Based on Generic Data

Using Level 3 the calculations are gathered from the production systems and the transport work is calculated. This transport work is then multiplied with a more generic emission factor which is set from calculating the emissions from the fleet used in the country or globally.


Level 6, Based on Detailed Vehicle Data

Using Level 6 the transactions/data are gathered from the productions systems and the transport work is calculated. This transport work is then multiplied with the specific vehicle used, considering air plane type, fuel consumption, utilization etc, giving a high quality calculation matching the demands from the more demanding customers. Level 6 calculation requires a subsystem that can feed ACCEPT with the relevant data on vehicles such as e.g. the environmental index used in a certain region, especially a country, e.g. Sweden,


In real production environment the calculations will vary from level 3 to 6, giving a result that is much better than level 3 but with less quality than a pure level 6. All this depending on the fact that the transactions from production do not always meet the need for level 6 reporting.


Calculating Rail Emissions

Rail emissions are not within the scope for the first release of ACCEPT.


The calculations are though be calculated in a similar way as Road and Air, using NTM methodology and values.


Calculating Sea/Ocean Emissions

The calculations are calculated in a similar way as Road and Air, using appropriate methodology and values.


Emissions Managed

The values shown in ACCEPT reports are the following:


















CO
Carbon oOxide



CO2
Carbon dDioxide



HC
Hydrocarbons



NOx
Nitrogen Ooxides



PM
Particulate mMatter



SO2
Sulphur dDioxide



Energy
Total consumption usage in kWh




Can also be split into Nuclear, Fossil or




ecological



Tonkm
Transport work done



kKm
Total distance driven



Number
of shipments



kKg
Total weight handled










For each physical object the value shown can be scaled in order to be more relevant, e.g. it might be more relevant to show emissions in kg instead of gram. This is managed by setting parameters.


External Interfaces

Using ACCEPT can involve external interfaces to existing production systems.


Air Transactions

For air transports there is a global solution, which can deliver transactions facilitating the implementation of ACCEPT, when one country is up and running, all other countries are easily adhered.



FIG. 13 shows a schematic representation 1300 showing how the Air transactions from the production system are managed. FIG. 13 shows how the Air transactions from the production system are managed via a Transaction Extract. The transaction is split, using the information in the CSD, generating a number of individual “legs” for which the emissions are calculated. These emissions are stored in the Data Mart (the same as for Road) and form the base for ACCEPT Report Database.


Transactions not accepted in the update are stored in a log file and an error message is created. When the error is corrected they will be updated.



FIG. 14 shows an advantageous process chart 1400 for accounting carbon credits in the carbon supply ledger.


Road Transactions

For the road transportations the situation is more complex, most countries have their own system(s), probably requiring a unique interface for each of them. In order to define the interface and estimate the cost, an analysis is done in each country.


ACCEPT is constructed in order to be as flexible as possible; all interfaces are planned for accepting a multiple of input systems. There are different ways how to interface the local production system, whether the major part of interface should be done on the production side or on the ACCEPT side.


The administration of interfaces to several systems is depending of the interface as described above, the aim is that the different production systems automate their deliveries to ACCEPT with ACCEPT administration monitoring the deliveries and updating the system.


Preferred embodiments of the invention allow integrating transportation means, characterized in that they contain means for transmitting environmental performance data of the transportation means to a logical node.


A logical node is any device that can be integrated in a computer network. Nodes can be computers, personal digital assistants (PDAs), cell phones, or various other network appliances.


On an IP (Internet Protocol) network, a logical node is any device with an IP address.


Logical nodes are often times connected by hubs, logical routers, or by a network switch.


The examples are combinable with physical routers, capable of executing a decision about parameters of transport to another physical router or to a receiving station, characterised in that a logical node is assigned to the physical router, wherein the decision is taken according to environmental data.


To carry out these embodiments efficiently it is advantageous to implement at least one computer program, capable of controlling a message for transporting physical objects, wherein the transport occurs through at least one physical router, wherein the physical router executes a decision about further parameters of transport, characterised in that the computer program takes the decision according to environmental data.


For further increasing the efficiency and speed for involving the environmental data, an aspect of the invention concerns a computer program product, characterised in that it contains one of the described computer programs. Preferable the computer program product is loadable in the logical node.


The descriptions for representation of data are always combinable with the examples for routing and/or transporting the physical objects.


Therefore the invention includes information systems as well as routing and transporting systems.


It is absolutely understandable that parts of the invention can be used together or alternatively separately.


It is especially advantageous to use transportation means, the physical router, the computer program or the computer program product according to the invention independently or in combination with one or more of the other parts of the present invention.


This allows obtaining ascertained environmental impact data and using it for a transport optimized with regard to calculated environmental impact data.

Claims
  • 1-12. (canceled)
  • 13. A method for transporting physical objects, at least one physical object being transported from a sending station to a receiving station, the transport occurring through a first physical router, the method comprising: receiving at a central control computer information for handling and moving the at least one physical object;using required environmental data to compute at least one transport parameter relative to a movement of the at least one physical object to a second physical router or to a receiving station; andtransporting the at least one physical object to the second physical router or to the receiving station based on the at least one transport parameter.
  • 14. The method according to claim 13, wherein environmental impact data accompanies the at least one physical object.
  • 15. The method according to claim 13, wherein environmental requirements data accompanies the at least one physical object.
  • 16. The method according to claim 13, performing a steering function of the first physical router using environmental impact data stored on the central control computer.
  • 17. The method according to claim 13, wherein a computer connected to the first physical router is adapted to consider environmental impact data about a transportation type and at least one transportation-relevant parameter of the at least one physical object.
  • 18. The method according to claim 13, wherein measured environmental data are measured by sensors and transmitted to the central control computer.
  • 19. The method according to claim 13, wherein transport of the at least one physical object is calculated and planned, wherein an environmental effect of the transport is calculated with regard to environmental performance data of at least one transport type and wherein the at least one transport parameter is changed if the planned transport does not fulfill the required environmental data.
  • 20. The method according to claim 13, wherein the required environmental data comprises emission data.
  • 21. The method according to claim 13, wherein the transport parameter comprises a fuel type.
  • 22. The method according to claim 13, wherein the transport parameter comprises a transport type.
  • 23. The method according to claim 13, wherein the transport parameter comprises a transport time.
  • 24. The method according to claim 13, comprising using the required environmental data to compute at least one sustainability parameter relative to the movement of the at least one physical object to the second physical router or to the receiving station.
  • 25. A system for transporting physical objects, at least one physical object being transported from a sending station to a receiving station, the system comprising: a first physical router, transport of the at least one physical object occurring through the first physical router; anda central computer that is adapted to receive information for handling and moving the at least one physical object, the central computer being adapted to use required environmental data to compute at least one transport parameter relative to a movement of the at least one physical object to a second physical router or to the receiving station.
  • 26. The transportation system according to claim 25, wherein the central control computer contains at least one comparator for comparing measured environmental data with the required environmental data.
  • 27. The transportation system according to claim 25, comprising: a plurality of sensors that are adapted to measure environmental data; anda transmitter that is adapted to transmit measured environmental data to the central control computer.
  • 28. The transportation system according to claim 25, wherein the required environmental data comprises emission data.
  • 29. The transportation system according to claim 25, wherein the transport parameter comprises a fuel type.
  • 30. The transportation system according to claim 25, wherein the transport parameter comprises a transport type.
  • 31. The transportation system according to claim 25, wherein the central computer is adapted to use the required environmental data to compute at least one sustainability parameter relative to the movement of the at least one physical object to the second physical router or to the receiving station.
  • 32. A tangible machine-readable medium, comprising: code that is adapted to receive information for handling and moving at least one physical object; andcode that is adapted to use required environmental data to compute at least one transport parameter relative to a movement of the at least one physical object to a physical router or to a receiving station.
Priority Claims (1)
Number Date Country Kind
EP 06 016 417.5 Aug 2006 EP regional