The Global Carbon Market Model provides a framework for integration of data from global carbon markets into a web portal.
The model comprises carbon emissions and energy efficiency monitoring as well as enterprise planning and business process automation elements.
It encompasses a customer domain as well as the data elements common to technology services, components and deployment.
It is the basis for building carbon market databases in common SQL database products such as MySQL, DB2, Oracle, SQL Server, Postgres etc..
The Enterprise Planning Model describes the processes involved in the interaction around the organization centric planning capability, including the services that provide customer, products, asset management services.
The Customer Domain Model represents the customer.
The system collects customer profile information that enables identification. Customer identity is a key aspect.
The customer profile attributes are modelled as classes, as their may be a one-to-many relationship between the customer and the attribute. For example, the customer may have more than one address, drivers licence. This domain includes the capability to make charges for products and services, and to aggregate invoices to a customer account.
The Customer model includes information and functions entailed in the processing of customer requests for products through different channels - web, telephone etc.
The capability to parse the incoming requests to a queue structure, and to assign operators to those queues through workflow role definition.
The request processing begins with a customer contact from three main channels
- Web requests
- Email/fax/post requests
- Telephone requests
The Products Domain Model models the capability to allow marketing personnel to update prices for products and product bundles on a campaign basis.
It provides the basis for marketing products and services is an offer to customers. The products capability is to provide self-service for marketing.
The Organisation Domain Model describes the physical locations for a business, and the people and the organisation of roles involved in the enterprise, including people, job and business roles, and workgroups.
It also describes the contact details for organisation personnel.
The Asset Domain Model describes the management and maintenance of physical assets, such as plant and equipment, asset identification by means of asset tags, and recording information about the state of the assets.
Routine and ad hoc maintenance of equipment is managed by maintenance schedules for maintenance crews, linked to specific work requests.
The Geospatial Domain Model describes the mapping of objects related to a particular theme. A theme, e.g. electricity substations, is represented by a layer that may contain a number of features that are represented graphically on a map at a particular latitude and longitude.
The Vehicles Domain Model describes the management of information from telematics collected from vehicles, profiles, drivers, depots, and the recording of vehicle journeys.
The Carbon Market Model describes the calculation and registration of greenhouse gas emissions reductions to any of the global carbon trading markets, connecting buyers and sellers of carbon offsets at a price per tonne of CO2e (Carbon Dioxide equivalent, a standardized measurement that covers the whole suite of greenhouse gases).
Replacement of Renewable Energy supply can provide the basis for carbon trading with near real-time metrics from power transmissions by generators replacing fossil fuel power plants.
Click on to expand model
Click on to view diagrams
Click on any element in any diagram to view it's composition
An architecture model provides the basis for communication and stakeholder engagement. Business and technology people are increasingly speaking very different languages, from both a geolocation and a technical perspective.
A UML model provides a focus for architecture, business process management, technology development, testing and implementation either in a data centre or the cloud.
The Global Carbon Market Model is a data and services model for carbon emissions pricing and energy efficiency calculations cloud applications and enterprise data integration.
If you'd like more information about using the model, please contact us. We are happy to discuss your requirements for deployment of the model as the basis for your enterprise solution architecture.
The Business Process Automation Model provides an ICT architecture framework for a head start on delivery of integration of applications, connected with existing technology.
The API Management and Application Workflow Domain Model describes the workflow for a business process. As workflows generally involve user interaction, user access to a web interface, and the content displayed to the users is included in this package.
The Web Navigation and Search Models provide for interaction by mobile and desktop users to published information relating to carbon emissions and energy and efficiency.
Identity and Access Management
The Identity Domain Model provides the Identity of a Party. A Party is generally identified once, and for subsequent verifications, authentication mechanisms can be applied, e.g. security tokens, userid and password.
Identity can beapplied to all stakeholders accessing internal or external systems. The parties may be customers, authorities, staff and consultants.
Data Distribution Model
The Data Distribution Model describes a data centric message capability, that supports the OMG DDS (Object Management Group Data Distribution Service) standard.
It provides for message topics by business domain. Participants in the data distribution services can either be publishers of or subscribers to messages or both.
Domain data sources are described by topic fields and topic values, accessible by key fields.
Application Services Model
The Application Services Model describes the applications, services and messages amongst different application systems.
Services are described in terms of the source and target applications, and whether the interface is provided or required. Messaging is independent of data and content, so messages can be interpreted at each node of the communications paths.
Event Handling Model
The Event Handling Domain Model describes triggered and scheduled events that cause automated actions in a technology system. Workflows are often triggered by events.
The Reporting Domain Model describes the data sources that provide input into the report, and the parameter name value pairs engaged in the filtering of reporting data and content.