Term | Definition | ||
---|---|---|---|
Associated Data | Database object (based on a Non Periodic Channel) that holds data such as Floor Area, Occupancy, Population, etcAccount | The items that represent the granular Supply Point level at which you are billed. It is anticipated that there be only one Supply Point effective for an Account on any one specific day. An Account is also expected to be for a single commodity, so while it may be that a Supply Point is associated to an Account, and its configuration may change over time resulting in multiple Supply Point records, it is not expected that Supply Points for different commodities are associated to the same Account. Account configuration is needed if your intention is to use Sigma for bill validation purposes. As a rule of thumb, if wanting to estimate the number of Accounts you will need to configure, it would be the answer to the question “How many distinct supplies of different commodities, do I expect to receive bills for for my usage on any one specific day?”. Note, this is different to the number of bills, as one single bill from a supplier may include several your supplies (typically referred to as a bulk bill). | |
Account Number | A unique number for the utility being provided. This stays constant for the supply whereas the Meter Number and Account Number may change. Electricity is MPRN (Meter Point Reference Number), Gas is MPRN (Meter Point Reference Number) and Water is SPID (Supply Point Identifier). | ||
Associated Data | Used to record supplementary information to be used in validation or the calculation of data. Examples of the use of Associated Data include the definition of floor areas for sites to enable the calculation of usage per m2 rates, the definition of the Agreed Supply Capacities for Supplies to be used in the validation of charges or the definition of PPU rates for Accounts which are also used in the validation of charges. | ||
Channel | Reside under a meter or sub-meter database object. | ||
Contract | A referenceable agreement between you and the Provider. A Contract may be evergreen in which case the Permanent option is selected, or it may be timebound, having both a start date and an end date. A Contract is for a single commodity type and may cover one or more supply points and their meters. As a Contract is related to one and only one commodity this means that, if you were to have a dual fuel type agreement, this would be represented by one Provider with two Contracts. | ||
Contract Container | The intermediary object used to relate Contracts, Accounts, Supply Points and Meters. A Contract Container defines, for a period of time, the Contract that is applicable for the provision of a utility through the Meters on a Supply Point that is billed via an Account. Contract Containers are not displayed as a separate Item type via the Sigma UI and are effectively created and modified via Supply Points. A Supply Point may have one or more Contract Containers over time. A Contract Container can only be associated to one Supply Point (and one Contract, one Account and one or more Meters). | ||
Invoice Number | The Invoice Number is found on the Invoice (bill) and is unique. This will be entered into Sigma to identify the Invoice (Bill). | ||
Meter | The equipment that measures and records the flow of a utility through a Supply Point during a period of time. The provision of utilities is often measured based on recording the amount consumed directly or recording readings of how much has flowed through the Meter at two separate times and then inferring that the amount consumed is the difference between the readings. The creation of Meters is required if you wish to use Sigma for Monitoring and Targeting purposes. As Meters represent the technical physical reality there is no need for any decision making with regards to the level and number of these that need to be created. Distinct Meters need to be created for each Meter from which you anticipate receiving data which needs to be loaded into Sigma. | ||
Meter Number | The number given by the Provider and seen on the Invoice (Bill). Used to identify the Account to which we need to add bills to. | ||
Monitoring Point | Monitoring point needs to be created for each site, for each commodity under that site. Monitoring Points can hold various database objects including accounts, meters, channels, etc. A Monitoring Point stores information that has been created from various sources of data. For example, a calculation of the total gas consumed by a number of sites derived from gas consumption data at each individual site. The data in the Monitoring Point object would be generated by an equation (in this case a simple sum) combining all of the sources of data (in this example gas consumption at each site) | ||
Non Periodic Channel | Database object that saves data that is of a variable frequency and is often based on manual meter readings. | Periodic Channel | Database object that saves high frequency data, usually in 15 minutes or 30 minutes time intervals.Channels are the time series data holders that are used in Sigma to record and manage data. Similar to Meters, and their use of readings or consumption, Channels come in two types; Non-Periodic and Periodic. A Non-Periodic Channel is a channel for which consumption or reading data is entered along with the datetime for which they are applicable. A Non-Periodic Channel is required in order to be able to use Sigma to Enter Meter Readings. |
Organisation | The top-level entity with respect to the portfolio’s physical structure. An Organisation may be created for each legal entity that is billed and responsible for the consumption of utilities, or a single Organisation may be created for an entire group. In most cases a single Organisation is used to manage a customer’s portfolio. The decision with regards to the number of Organisations that you wish to create largely comes down to the need to differentiate the assets attributable to each. If there is a strong need to separate information then it would be sensible to have separate Organisations (for example if there is a need to attribute inbound and outbound costs to different legal entities), however, if the combined picture is more often of interest then a single Organisation is likely to achieve the desired results. | ||
Periodic Channel | Used to record data for cases where the measurement of consumption is performed on a routine recurring periodic basis | ||
PPU | Price Per Unit. | ||
Property Keys | Supply Point | Database object that links together all the details of the relevant contract, account and meters using the supplier number (MPAN/MPRN) Method by which it is possible to assign custom data to the entities in your Utility Portfolio. These custom properties can then be used to search for records in your portfolio. All Property Keys that are defined to be created need to be assigned a reference of the record that they are to be allocated to. For example, it may be desirable to use the “AMR” Property Key which has values of “True” or “False”. If this Property Key is to be used then the Meter or Meters to which we wish to assign it need to be defined. | |
Provider | The legal entity that supplies you with services or a utility for which you expect to be charged. A single Provider may supply you with more than one utility (e.g. Electricity and Gas). Within Sigma there are three main types of Provider which are; Supplier, Meter Operator or Data Collector and Aggregator. A single Provider may fulfil any one or more of these services. A Provider may be the party responsible for the provision of a utility to your meters but may not be a Supplier in the industry sense of the term. This is typically relevant to scenarios where your utility charges are passed through by another party, for example you have a rented property and your landlord recharges the utility costs. | ||
Supply Point | Represent the industries’ physical infrastructure required for the provision of a utility of a given commodity to your Site. In the case of utilities that aren’t supplied continuously (e.g. Oil Deliveries), the Supply Point represents the storage facility on-site. The Supply Point in Sigma is the Item that links the different parts of the story (physical, technical and supply) together. The provision of a utility through a Supply Point is normally technically measured using Meters, that may record readings/consumption based on differing frequencies. The quantity of the utility, or its availability for use if required, (the supply) is billed to the customer based on their contractual agreement with their Providers. Supply Points are the entities that provide visibility of the Contract Containers that link these different aspects together for defined periods of time. | ||
Site | The physical locations to which your utilities are supplied. These will typically be buildings and be referenceable by a postcode. Sites have specific properties and the contact details of someone that is responsible for them. Over time a Site may be Closed or become Non-Operational. The specification of Sites is typically easier than the selection of the number and level of Organisations and Site Groups to create as they are a one to one mapping with the physical distribution of your infrastructure. | ||
Site Group | Another level of hierarchical configuration in addition to Organisations. Site Groups are completely optional and may or may not be used. Site Groups can be used to structure your portfolio in a logical way. Site Groups might for example be used to mirror the geographic distribution (e.g. North, East, etc…), the cost centre that the Sites attributed to them belong to (e.g. Retail, Manufacturing, etc..) or some other frequently referenced grouping with your organisation. As Property Keys can be used to assign specific properties, the selection of the Site Group is not the only way in which Sites can be distinguished as you could for example configure with graphical site groups and then assign a cost centre based property and use that to select and work on Sites. | ||
Validator | |||
Page Comparison
General
Content
Integrations