Server Software EULA
Please read this end user licence agreement ('EULA') carefully. The 'Licensor' under this EULA is EKM Global Limited, a company incorporated in England (registration number 04165970) having its registered office at Redland House, 157 Redland Road, Bristol BS6 6YE. By accepting the terms of this EULA, downloading the software made available under this EULA, installing that software or using that software, you consent to be bound by the terms of this EULA. If you do not agree to all the terms of this EULA, you must not download, install or use that software.
1. Definitions
1.1 In this EULA:
'Affiliate' means an entity that Controls, is Controlled by, or is under common Control with the relevant entity;
'Authorised Users' means the officers, employees, sub-contractors, agents, representatives and service providers of:
(a) the Licensee; and
(b) any Affiliate of the Licensee;
'Business Day' means any weekday, other than a bank or public holiday in England;
'Control' means the legal power to control (directly or indirectly) the management of a corporate entity (and 'Controlled' will be construed accordingly);
'Customer' means a legal or natural person that has purchased access to the System from either EKM or a Service Provider for the purpose of managing its and/or its Affiliates' print systems;
'Customer Equipment' means those elements of the Customer System that interface with the Software, including printer hardware;
'Customer System' means a Customer's computer systems, networks, hardware and software;
'Database' means any database of printing and related hardware and software information, printing consumables information and print services information provided with the Software and/or accessible using the Software, including both the structure of that database and the content of that database;
'Documentation' means any documentation made available by the Licensor to the Licensee with the Software;
'EKM' means EKM Global Limited, a company incorporated in England (registration number 04165970) having its registered office at Redland House, 157 Redland Road, Bristol BS6 6YE;
'Hosting Environment' means the hosting infrastructure service that will be used to host the Platform;
'Intellectual Property Infringement' has the meaning given to it in Clause 10.1;
'Intellectual Property Rights' means all intellectual property rights wherever in the world, whether registered or unregistered, including any application or right of application for such rights (and these 'intellectual property rights' include copyright and related rights, database rights, confidential information, trade secrets, know-how, business names, trade names, trade marks, service marks, passing off rights, unfair competition rights, patents, petty patents, utility models, semi-conductor topography rights and rights in designs);
'Licensed Materials' means the Software, any Documentation and any Database;
'Licensee' means the person or entity granted a right to use the Software under this EULA, being either a Service Provider or a Customer;
'Maintenance Services' means:
(a) the reconfiguration of the Platform from time to time; and
(b) the provision and application of Updates and Upgrades;
'Master Agreement' means:
(a) an agreement between the Licensor and the Licensee governing the provision of the System to the Licensee as a Customer; or
(b) an agreement between EKM as Licensor and the Licensee governing the provision of the System to the Licensee as a Service Provider;
'Permitted Purpose' means:
(a) if the Licensee is a Customer, the purpose of using the System in accordance with the Documentation to manage the Licensee's print systems, and the print systems of such of the Licensee's Affiliates as may be authorised in the relevant Master Agreement; and
(b) if the Licensee is a Service Provider, the purpose of providing the System to Customers in accordance with the relevant Master Agreement;
'Platform' means the platform used to host the Software, including server hardware and operating system software installed on that hardware, together with the Software itself;
'Service Provider' means a legal or natural person that has entered into an agreement with EKM under which that person is entitled to provide the System and sub-license elements of the System to Customers;
'Software' means EKM's Insight Messaging Server, Insight AdminPortal Server, Insight Database Server/Cluster, InsightReporting Server and Insight License Server;
'Support Services' means those support services relating to the Software that the Licensor agrees to provide to the Licensee under the Master Agreement;
'System' means the Licensor's print service management and reporting system, of which the Software forms a part;
'Updates' means minor version updates to the Software, whether for the purpose of fixing errors or otherwise;
'Upgrades' means major version upgrades of the Software, for the purpose of enhancing or altering the functionality of the System;
'Usage Data' means all data uploaded to, stored on, or processed or transmitted using the Software by or on behalf of a Customer or by any person or application or automated system; and
'User' means any natural person using the Software from time to time.
2. Grant of rights
2.1 The Licensor grants to the Licensee a worldwide, non-exclusive and non-transferable right to:
(a) install and use the Software in accordance with the Documentation;
(b) store, view, copy and print the Documentation; and
(c) access and use any Database through the Software,
in each case subject to any restrictions set out in the Master Agreement, solely for the Permitted Purpose and strictly in accordance with this EULA.
2.2 The licence granted under Clause 2.1 is subject to the following limitations:
(a) the Licensed Materials may only be used by Authorised Users;
(b) the Licensee must comply at all times with the terms of this EULA, and must ensure that all Users comply with the terms of this EULA.
2.3 Except to the extent mandated by applicable law or expressly permitted in this EULA or the Master Agreement, the licence granted under Clause 2.1 is subject to the following prohibitions:
(a) the Licensee must not sub-license its rights in relation to the Licensed Materials (providing that, if the Licensee is a Service Provider, the Licensee may sub-license the right to install and use the Software to Customers);
(b) the Licensee must not allow any unauthorised person to access or use the Licensed Materials;
(c) the Licensee must not sell, resell, rent, lease, loan, supply, distribute or redistribute the Licensed Materials or provide a bureau service using Licensed Materials (providing that, if the Licensee is a Service Provider, the Licensee may provide a service using the Software);
(d) the Licensee must not publish or re-publish the Licensed Materials;
(e) the Licensee must not copy or reproduce the Licensed Materials except where that copying is incidental to normal use of the Licensed Materials or where it is necessary for the purpose of back-up or operational security in accordance with the licence granted in this Clause 2;
(f) the Licensee must not modify, alter, adapt, translate or edit, or create derivative works of, the Licensed Materials;
Hp Smart Device Services On Pc
(g) the Licensee must not reverse engineer, decompile or disassemble the Licensed Materials;
(h) the Licensee must not circumvent or remove or attempt to circumvent or remove the technological measures applied to the Licensed Materials for the purpose of preventing unauthorised use; and
(i) the Licensee must not use the Licensed Materials to create, or in connection with the creation of, any software which is substantially similar to any software licensed or provided by EKM from time to time.
2.4 All Intellectual Property Rights in the Licensed Materials shall be the exclusive property of the Licensor and its licensors; and the only rights the Licensee has in relation to the Licensed Materials shall be those expressly set out in this EULA.
2.5 Save to the extent expressly provided otherwise in this EULA, the Licensee has no right to access the source code of the Software.
2.6 The Licensee shall be responsible for the security of the Licensee's copies of the Licensed Materials, and will use all reasonable endeavours to ensure that access to the Licensed Materials is restricted to persons authorised to use them.
2.7 The Licensee must not remove or obscure any copyright notice, EKM branding or EKM hyperlink incorporated into the Licensed Materials.
3. Database
3.1 The Licensee acknowledges that:
(a) Database information may be inaccurate;
(b) Database information may be, or become, out of date; and
(c) information may not be available in the Database in relation to obsolete or new products, and the Database information for any product may be absent or incomplete,
and, accordingly, the Licensee must not rely upon the Database information in any situation where the inaccuracy of that information may cause the Licensee to suffer any material loss or damage.
3.2 The Licensee acknowledges that the sources for the Database information, and the contents of the Database, may be changed at any time by EKM with or without notice to the Licensee.
4. Acceptable use
4.1 The Licensee must not:
(a) use the Software in any way that causes, or may cause: (i) damage to EKM's or any EKM subcontractor's business, systems or services; or (ii) impairment of the availability or accessibility of EKM's or any EKM subcontractor's systems or services;
(b) use the Software in any way that is unlawful, illegal, fraudulent, misleading or harmful, or in connection with any unlawful, illegal, fraudulent, misleading or harmful purpose or activity;
(c) use the Software to store, host, copy, process, distribute, display, publish, transmit or send works or materials that are illegal or unlawful, will or may infringe any person's Intellectual Property Rights or other legal rights, or could give rise to legal proceedings, whether against the Licensor, EKM or another person, in each case in any jurisdiction and under any applicable law; or
(d) upload or transmit, or permit the uploading or transmission of, any computer virus or other malicious software program to or by the Software.
5. Maintenance Services
5.1 During the Term, the Licensor shall provide the Maintenance Services to the Licensee in accordance with the provisions of this Clause 5.
5.2 The Licensor shall use reasonable endeavours to:
(a) give to the Licensee advance written notice of any intention to carry out scheduled Maintenance Services; and
(b) arrange that any scheduled Maintenance Services that are liable to affect the availability of the System be performed outside the hours of 09:00 to 17:00 on a Business Day.
5.3 From time to time the Licensor may provide and apply:
(a) Updates to the Platform; and
(b) Upgrades to the Software.
5.4 The Licensee acknowledges that the provision and application of Upgrades may be subject to additional charges, in which case the Licensee shall have the opportunity to refuse the application of the relevant Upgrade.
5.5 The Licensee acknowledges that the Software may be unavailable during the provision of scheduled and emergency Maintenance Services.
5.6 The Licensee acknowledges that the Licensor may remotely access the Software for the purpose of providing the Maintenance Services and for the purpose of calculating charges.
6. Licensee obligations
6.1 The Licensee will provide to the Licensor:
(a) such remote access to Customer Equipment and Customer Systems; and
(b) if the Hosting Environment is in the control of the Licensee, such remote administrative access to the Hosting Environment,
as is reasonably requested by the Licensor to enable the Licensor to provide the Support Services, Maintenance Services and/or any other services to be provided to the Licensee under the Master Agreement.
6.2 The Licensee shall:
(a) provide to the Licensor, and procure from each Customer and all relevant third party suppliers of the Licensee and each Customer, all necessary co-operation and information as may be reasonably required by the Licensor to enable the provision of the Support Services, Maintenance Services and/or any other services to be provided to the Licensee under the Master Agreement;
(b) ensure that each Customer System (and, if the Hosting Environment is in the control of the Licensee, the Hosting Environment) complies with the minimum system requirements reasonably stipulated by the Licensor from time to time;
(c) ensure that each Customer System (and, if the Hosting Environment is in the control of the Licensee, the Hosting Environment) is properly maintained, supported and updated, and notify the Licensor of any updates or other changes to any element of any Customer System (or Hosting Environment) which will or may affect the Software, Support Services or Maintenance Services;
(d) ensure that it has all rights necessary to allow the Licensor to interface with each Customer System as necessary for the performance of its obligations under this EULA and the Master Agreement;
(e) be solely responsible for procuring and maintaining its network connections and telecommunications links from its systems to the Licensor's data centres, and for all problems, conditions, delays, delivery failures and other loss or damage arising from or relating to the Licensee's network connections or telecommunications links or caused by the internet; and
(f) carry out all other Licensee responsibilities set out in this EULA in a timely and efficient manner,
and in the event of any delays in the Licensee's performance of its obligations under this EULA, the Licensor may adjust any timetable or delivery schedule set out in this EULA as reasonably necessary.
6.3 The Licensee acknowledges and agrees that the Licensor shall not be responsible for, or liable in respect of:
(a) any use of the System contrary to this EULA, the Documentation or the Licensor's instructions;
(b) the incorrect installation of the Software or any Platform software by any person other than the Licensor;
(c) any modification or alteration of the System by any person other than the Licensor or the Licensor's duly authorised contractors or agents;
(d) any issues affecting the internet, third party communications links which are outside of the Licensor's control, or the Licensee's network, firewall or anti-virus systems;
(e) any denial of service attacks affecting the Hosting Environment;
(f) any failure by the Licensee to meet any minimum system requirements in respect of a Customer System or Usage Data as stipulated by the Licensor on reasonable notice from time to time;
(g) any inaccuracies or omissions in Usage Data;
(h) bad or limited data from printers;
(i) any failure by the Licensee to comply with the requirements of this EULA; or
(j) Customer Equipment, Customer Systems or any other software or equipment not supplied by the Licensor operating in conjunction with the Software or used by the Licensee.
6.4 The Licensee shall obtain or shall procure:
(a) any Customer Equipment required for the installation or use of the Software; and
(b) if the Hosting Environment is in the control of the Licensee, the Customer Equipment, operating system software and other software required for the installation or use of the Software.
6.5 The Licensee grants to the Licensor a non-exclusive, royalty-free, irrevocable licence for the Term to use the Licensee's branding to the extent necessary for incorporation into the graphical user interfaces of the Software.
6.6 It is the Licensee's responsibility to ensure that the System is fit for the Licensee's and (if the Licensee is a Service Provider) each relevant Customer's purposes.
6.7 The Licensor shall be entitled to charge the Licensee at the Licensor's standard time and materials rates if the Licensor is delayed or put to extra cost as a result of the Licensee failing to comply with its obligations under this EULA.
7. Usage Data
7.1 All Intellectual Property Rights in Usage Data will remain, as between the parties, the property of the Licensee.
7.2 As between the parties, the Licensee shall have sole responsibility for the reliability, integrity, accuracy and quality of Usage Data.
7.3 The Licensee grants to EKM a non-exclusive licence during and after the Term to store, copy and otherwise use Usage Data on and in relation to the System for the purposes of:
(a) operating the System and providing the Support Services and Maintenance Services;
(b) enabling the Licensor to fulfil its obligations and exercise its rights under this EULA; and
(c) analysing the use of the System and other research and analysis.
7.4 If the Hosting Environment is in the control of the Licensor, then the Licensor shall make back-ups of all Usage Data stored on the Platform.
8. Records and audit
8.1 The Licensee shall maintain accurate and up-to-date records of the computers upon which the Software is installed, and shall provide such records to the Licensor promptly following receipt of a written request to do so from the Licensor.
8.2 The Licensee must permit the Licensor and its representatives, at all reasonable times and on reasonable advance notice, to inspect and have access to any premises at which the Licensed Materials are being kept or used, to the computer equipment located there, and to any records kept under this EULA, for the purpose of ensuring that the Licensee is complying with the terms of this EULA and the Master Agreement.
9. Warranty limitations
9.1 All of the parties' liabilities and obligations in respect of the subject matter of this EULA are expressly set out herein. To the maximum extent permitted by applicable law and subject to Clause 11.1, no other terms concerning the subject matter of this EULA will be implied into this EULA or any related contract.
9.2 Without prejudice to the generality of Clause 9.1 and subject to Clause 11.1:
Fl studio plugins reddit. (a) the Software has not been developed to meet the specific requirements of the Licensee, and accordingly the Licensee will be responsible for ensuring that the Software is suitable to meet the Licensee's requirements;
(b) it is the Licensee's responsibility to ensure that the System is suitable for the Licensee's and (if the Licensee is a Service Provider) each relevant Customer's purposes, and the Licensor does not warrant that the Licensed Materials will be suitable for any particular purpose;
(c) the Licensor does not warrant that the Licensed Materials will meet the Licensee's requirements, that the operation of the Software will be uninterrupted or error-free, or that defects in the Licensed Materials will be corrected;
(d) no oral or written information or advice given by the Licensor shall create any additional warranties or in any way increase the scope of the Licensor's obligations under this EULA;
(e) the Licensee acknowledges that complex software is never wholly free from errors and bugs, and that the Licensor gives no warranty or representation that the System will be wholly free from such errors and bugs; and
(f) the Licensor does not warrant or represent that the System will be compatible with any application, program or software not specifically identified as compatible by the Licensor.
10. Intellectual Property Infringement
10.1 The Licensor warrants to the Licensee that the use of the Software by the Licensee or any Authorised User in accordance with the terms of this EULA will not infringe the Intellectual Property Rights of any third party (an 'Intellectual Property Infringement').
10.2 If the Licensor reasonably determines, or any third party alleges, that there is or may be an Intellectual Property Infringement, the Licensor may at its own cost and expense:
(a) modify the Software in such a way that it no longer infringes the relevant Intellectual Property Rights; or
(b) procure for the Licensee the right to use the Software in accordance with this EULA.
10.3 Subject to the Licensee's compliance with Clause 10.4, the Licensor will indemnify and will keep indemnified the Licensee against all liabilities, damages, losses, costs and expenses (including legal expenses and amounts paid in settlement of any disputes) suffered or incurred by the Licensee and arising as a result of any Intellectual Property Infringement.
10.4 The Licensee must:
(a) upon becoming aware of an actual or potential Intellectual Property Infringement, notify the Licensor;
(b) provide to the Licensor all reasonable assistance in relation to the Intellectual Property Infringement;
(c) allow the Licensor the exclusive conduct of all disputes, proceedings, negotiations and settlements relating to the Intellectual Property Infringement; and
(d) not admit liability in connection with the Intellectual Property Infringement or settle the Intellectual Property Infringement without the prior written consent of the Licensor.
11. Limitations and exclusions of liability
11.1 Nothing in this EULA will:
(a) limit or exclude the liability of a party for death or personal injury resulting from negligence;
(b) limit or exclude the liability of a party for fraud or fraudulent misrepresentation by that party;
(c) limit any liability of a party in any way that is not permitted under applicable law; or
(d) exclude any liability of a party that may not be excluded under applicable law.
11.2 The limitations and exclusions of liability set out in this Clause 11 and elsewhere in this EULA:
(a) are subject to Clause 11.1; and
(b) govern all liabilities arising under this EULA or in relation to the subject matter of this EULA, including liabilities arising in contract, in tort (including negligence) and for breach of statutory duty.
11.3 Neither party will be liable to the other party in respect of any loss of profits, income, revenue, use, production or anticipated savings.
11.4 Neither party will be liable to the other party for any loss of business, contracts or commercial opportunities.
11.5 Neither party will be liable to the other party for any loss of or damage to goodwill or reputation.
11.6 Neither party will be liable to the other party in respect of any loss or corruption of any data, database or software.
11.7 Neither party will be liable to the other party in respect of any special, indirect or consequential loss or damage.
11.8 Neither party will be liable to the other party for any losses arising out of any event beyond the relevant party's reasonable control.
11.9 The Licensor shall not be liable to the Licensee in respect of any loss or damage arising out of the failure of or any defect in the Customer System or any Customer Equipment.
11.10 The limitations and exclusions of liability set out in this EULA are supplemental to those limitations and exclusions of liability set out in the Master Agreement.
12. Termination
12.1 This EULA shall automatically terminate upon the termination of the Master Agreement.
12.2 Within 7 days following the termination of this EULA, the Licensee must irrevocably remove and delete all copies of the Licensed Materials from its computer systems and storage media.
12.3 At any time following the expiry of the period referred to in Clause 12.2, the Licensee must, if the Licensor so requests, send to the Licensor a written confirmation of its compliance with Clause 12.2, signed by an officer of the Licensee.
12.4 The Licensee acknowledges that EKM may retain and use Usage Data following the termination of this EULA and use that Usage Data for the purpose specified in Clause 7.3(c).
12.5 Upon the termination of this EULA, all the provisions of this EULA will cease to have effect, save that the following provisions will survive and continue to have effect (in accordance with their terms or otherwise indefinitely): Clauses 1, 2.6, 10.3, 10.4, 11, 12, 14 and 15.
13. Export laws
13.1 The Licensee acknowledges that Software may be subject to the laws restricting and/or regulating: (i) the inter-jurisdictional import, export, supply, disclosure, transfer or transmission of goods, services, software, technology, technical know-how, data and/or information; and/or (ii) the import, export, supply, disclosure, transfer or transmission of goods, services, software, technology, technical know-how, data and/or information to designated entities or persons, or to designated classes of entities or persons; the Licensee must comply with all such laws insofar as they affect the Software.
14. Third party rights
14.1 If the Licensor is not EKM, then EKM shall have the right to enforce the provisions of this EULA against the Licensee and shall benefit from the limitations and exclusions of liability set out in this EULA as if it were the Licensor; and the parties may not agree any amendment, waiver, variation or settlement under this EULA without the prior written consent of EKM.
14.2 Subject to Clause 14.1:
(a) this EULA is made for the benefit of the Licensor and Licensee, and is not intended to benefit any third party or be enforceable by any third party; and
(b) the rights of the parties to terminate, rescind, or agree any amendment, waiver, variation or settlement under or relating to this EULA are not subject to the consent of any third party.
15. General
15.1 No breach of any provision of this EULA will be waived except with the express written consent of the party not in breach.
15.2 If a Clause of this EULA is determined by any court or other competent authority to be unlawful and/or unenforceable, the other Clauses of this EULA will continue in effect. If any unlawful and/or unenforceable Clause would be lawful or enforceable if part of it were deleted, that part will be deemed to be deleted, and the rest of the Clause will continue in effect (unless that would contradict the clear intention of the parties, in which case the entirety of the relevant Clause will be deemed to be deleted).
15.3 The Licensee agrees that the Licensor may subcontract any of its obligations under or relating to this EULA, providing that the Licensor shall remain responsible to the Licensee for the performance of the subcontracted obligations.
15.4 This EULA may not be varied except by a written document duly signed by or on behalf of each of the parties or in accordance with its express terms.
15.5 Each party hereby agrees that the other party may freely assign all of its contractual rights and obligations under this EULA to any successor to all or a substantial part of the business of that other party from time to time. Subject to this, neither party may without the prior written consent of the other party assign, transfer, charge, license or otherwise dispose of or deal in this EULA or any contractual rights or obligations under this EULA.
15.6 Except to the extent that the parties have expressly agreed otherwise in writing, time shall not be of the essence in relation to the performance of the parties' obligations under this EULA.
15.7 This EULA, together with the Master Agreement, constitutes the entire agreement between the parties in relation to the subject matter of this EULA, and supersedes all previous agreements, arrangements and understandings between the parties in respect of that subject matter; and, subject to Clause 11.1, neither party will have any remedy in respect of any misrepresentation (whether written or oral) made to it upon which it relied in entering into this EULA.
15.8 This EULA shall be governed by and construed in accordance with English law.
15.9 The Licensor may issue and pursue legal proceedings against the Licensee in any jurisdiction in which the Licensee is situated, incorporated, established or resident from time to time; subject to this, the courts of England shall have exclusive jurisdiction to adjudicate any dispute arising under or in connection with this EULA.
16. Interpretation
16.1 In this EULA, a reference to a statute or statutory provision includes a reference to:
(a) that statute or statutory provision as modified, consolidated and/or re-enacted from time to time; and
(b) any subordinate legislation made under that statute or statutory provision.
16.2 In this EULA, general words shall not be given a restrictive interpretation by reason of being preceded or followed by words indicating a particular class of acts, matters or things.
Skip to end of metadataGo to start of metadata
Please note that this page is best viewed with the Chrome browser.
The Advanced Meter Infrastructure ES bundle uses enterprise services to communicate between SAP backend systems and a metering system platform that is connected to smart meters, allowing information to flow back and forth between the call center, customer service department or backend office of a utility, and a customer's electric meter. This ES bundle provides enterprise services that allow utilities to automate time-consuming and expensive manual tasks such as disconnecting/reconnecting a meter, uploading profile data from a meter, and uploading discrete meter readings.
For a long time, utilities employed unsophisticated meters to track their customer's usage. These meters were read by a meter reader or by the customers themselves. Today greater strains on the power grid, environmental concerns, liberalization of utility markets, and new government-mandated billing systems mean that power suppliers must upgrade their metering systems.
Meters that had to be read manually then gave way to Automated Meter Reading (AMR) systems. These 'smarter' meters would transmit data to the utility company. However, this communication moved data in only one direction: from the meter to the utility. AMR was certainly an improvement, but unidirectional communications meant that some types of common transactions, such as disconnection and reconnection, could not be performed automatically.
An Advanced Meter Infrastructure (AMI), on the other hand, provides two-way communication between meters at the customer site and the utility company. The communication is frequent as well. Utilipoint International, Inc. defines an AMI as 'a communication network and meters providing interval usage (at least hourly) and collected at least daily.'
SAP for Utilities now provides a way to communicate with an AMI through the Advanced Meter Infrastructure ES bundle. This ES bundle provides enterprise services that allow information to flow back and forth between the meters, the metering system platform (also known as the AMI), and SAP back-end systems. Using these enterprise services, utility companies can disconnect and reconnect customers, as well as uploading profile data from the AMI into SAP ERP 6.0.
The SAP backend systems communicate with SAP NetWeaver Process Integration (SAP NetWeaver PI, formerly called XI, using the enterprise services in this ES bundle. Depending on the metering system platform in question, SAP NetWeaver Process Integration formats the XML message to transfer the data from the SAP backend systems to the metering system platform and back again. In the case of a regulated electricity market (as in most U.S. states except Texas), a single utility would own the entire system landscape, including both the technical processes and the commercial processes shown in Figure 1. In a deregulated market (as in most of Europe), this infrastructure would be run by multiple businesses such as a power supplier, distributor, and meter reading company (see the Market Communication ES bundle for details on market role based approach to handling the complexity of deregulated utilities). This ES bundle's enterprise services are the link between the technical and the commercial processes. What the Advanced Metering Infrastructure ES Bundle Does
The Advanced Meter Infrastructure ES bundle enterprise services handles tasks in the following areas:
Technical Master Data Exchange
When a smart meter is installed, several steps are involved. First, the device must be created in SAP for Utilities and the meter must be initialized. Next the meter must be physically installed, followed by technically installing the meter and setting various parameters, such as how usage data will be collected. All of this master data exchange involves communications between SAP for Utilities and the meter data unification and synchronization system (MDUS). The MDUS then in turn communicates with the meters.
Meter Reading Processes
This ES bundle supports reading meters on a given date, either in bulk or singly (on-demand read). It also supports gathering time series data, which is critical for creating accurate pictures of usage for billing and reporting.
Disconnection and Reconnection
Services in this ES bundle allow a call center or backend office to remotely disconnect/reconnect a customer's meter. This means utilities won't have to take the time-consuming and expensive step of sending a technician to a customer's house to disconnect or reconnect a meter. For customers, it means their power will be reconnected more quickly after they pay a delinquent bill.
Further, the enterprise services offered in this ES bundle help companies meet emerging regulatory requirements. For example, in Sweden, regulatory policy mandates that all customers must receive a monthly bill based on actual consumption and not on estimates. In the US, the Energy Policy Act of 2005 mandates that all retail customers must be provided with an Advanced Metering Infrastructure and that they must have the option of taking service under time-based rates. In Germany, process efficiency includes a requirement that utilities must be able to remotely connect and disconnect customers who exhibit delinquent payment behavior.
The AMI ES bundle leverages enterprise SOA by sending web service messages from SAP for Utilities to SAP NetWeaver Process Integration. PI messages are then mapped to the XML required for a particular third-party metering system and this metering system in turn communicates with the customer's meter. Figure 1. SAP AMI Integration for Utilities - Deregulated Market (click to enlarge) Figure 2. SAP AMI Integration for Utilities - Regulated Market (click to enlarge) For details on Service Operations, Business Objects and Process Components, see the ES Workplace.How To Use This ES Bundle
This section will explore use cases for the Advanced Meter Infrastructure ES bundle. Each use case will show how different outcomes can be achieved by using the enterprise services in different combinations. While these examples illustrate a few of the ways that this ES bundle could be used, the intention is to show the flexibility and reusability of these business objects and enterprise services operations so that you will have a clearer understanding of how to best deploy them in your own environment. This wiki is also a space for you to share knowledge and collaborate with others who are implementing the Advanced Meter Infrastructure ES bundle.
Use Case 1: Device Initialization Process
Before a smart meter can be used, it must be initialized to set up a bidirectional communication between the smart meter, the MDUS, and SAP for Utilities.
The process starts when a clerk enters a goods receipt for the smart meter in SAP for Utilities, which also creates the device's master data. At this point, SAP for Utilities sends a request to the MDUS system asking it to create a representation for the device in its system. This request is sent using the Request Utilities Device Smart Meter Creation enterprise service, whose business object is Utilities Device. The MDUS sends back a confirmation message, using the Change Based on Utilities Device Smart Meter Creation Confirmation enterprise service operation.
Later, when the smart meter is physically installed at the customer site, the MDUS system sends a notification back to SAP for Utilities using the Change Based on Utilities Device Smart Meter Registered Notification, telling SAP for Utilities that this meter has been registered within a specific AMI system and that it can now be used for subsequent processes.
Next, in SAP for Utilities, a clerk technically installs the smart meter. This process, with which users of SAP for Utilities will be familiar, involves assigning a measurement task to a device. A Utilities Measurement Task indicates why types of measurements should be taken using this device (for example, measuring consumption, energy, volume, or power periodically as indicated). It associates the physical meter with this measurement task, which can also be regarded as a logical representation of the meter's function. Technical installation also includes configuring the meter in SAP for Utilities, specifying how many registers there are, for example, for measuring energy use during different time blocks, such as daytime and night time usage. Performing this task in SAP for Utilities invokes a request to the MDUS, which is executed by the Request Utilities Device Smart Meter Register Creation enterprise service operation. The MDUS then sends back a confirmation, using the Change Based on Utilities Device Smart Meter Register Creation Confirmation service operation.
If discrete meter readings are collected instead of interval data, SAP for Utilities sends out a request to the MDUS to collect meter readings. Alternatively it is possible to enter meter readings manually (the prerequisite for doing so is the activation of a BAdI) and provide them to MDUS. (For more information, see use case 3).
The device has now been both physically and technically installed; the final step is to install it from a billing perspective. At this point, the customer has a contract with you and the point of delivery has been assigned to this customer. SAP for Utilities informs the MDUS that the point of delivery (the customer premises) has been associated with this particular meter. SAP for Utilities communicates this information by invoking the Notify of Smart Meter Utilities Measurement Task Point Of Delivery Assigned enterprise service operation.
Note: If multiple devices or measurement tasks are involved, this triggers the corresponding bulk services.
The following table summarizes the steps in this use case and the associated Enterprise Services:
Use Case 2: Change Technical Master Data
In use case 1, we set up the smart meter so that it is functioning, reading consumption information for billing the customer. But even after a meter is installed, a company may decide that they want to change how they measure their customers' consumption. For example, it may be that initially, total consumption by day was being measured. Now, however, they want to measure usage in two segments: daytime usage and nighttime usage. These segments are called registers and the registers are an attribute of the business object Utilities Device.
To change the number of registers, first the change is made in SAP for Utilities, which invokes the enterprise service Request Utilities Device Smart Meter Register Change is invoked. The MDUS makes the corresponding change in its metering infrastructure and then sends back a confirmation message: Change Based on Utilities Device Smart Meter Register Change Confirmation.
Please note: If multiple devices or measurement tasks are involved, this triggers the corresponding bulk services.
The following table summarizes the steps in this use case and the associated enterprise services:
Use Case 3: Discrete Meter Reading Process
To bill customers for consumption, you have to find out how much energy they have used. Discrete meter readings are required at specific points in time, for example business-related points in time such as the billing cycle or tariff changes, and technical points in time, such as device installation, device removal, and so on.
The discrete meter reading process can be executed in one of two ways:
Use Case 3a: SAP Requests Meter Readings from MDUS
In this use case, the utility company sends out a bulk request to read all the meters in a particular group (defined according to your setup) as of a given date, which can be a past or future date.
SAP for Utilities sends out this request to the MDUS by invoking the enterprise service Request Smart Meter Meter Reading Document Creation as Bulk. MDUS then acknowledges the request (perhaps the next day) by invoking Change Based on Smart Meter Meter Reading Document Creation Confirmation as Bulk enterprise service operation. However, this confirmation message is not simply an acknowledgment of the request; it also includes application level details, such as the fact that a particular point of delivery is not known to the MDUS. In other words, the MDUS is saying, I will read all the meters except for this one and the one for which I have no information. (In the optimum case, all meters are known to the MDUS and no such exceptions occur.)
The MDUS then reads the meters according to the date the read was requested: either as soon as possible (for a present or past date) or on the specified date (in the case of a future date). The MDUS sends the meter readings to SAP for Utilities by invoking the Create Meter Reading Document Result as Bulk enterprise service operation, which uses the Meter Reading Document business object. After SAP for Utilities has uploaded the meter reading documents, it sends a confirmation message back to the MDUS, invoking the Confirm Meter Reading Document Result Creation as Bulk enterprise service operation.
The following table summarizes the steps in this use case and the associated enterprise services:
If the request for meter reading (âMeter Reading Orderâ in SAPâs terminology) is cancelled in SAP, a meter reading is no longer required. SAP informs MDUS about this cancellation:
Use Case 3b: Sending Meter Reading Results from SAP to MDUS
Supported for SAP ERP 6.0 EhP5 SP09, SAP ERP 6.0 EhP6 SP05 and all higher releases and support packages.
Generally smart meters are read remotely following the process steps in use case 3. There are some situations where AMI head end systems are not able to capture discrete meter reading results and forward them to MDUS. These are:
⢠Installation of smart meters
⢠Replacement of smart meters ⢠Removal of smart meters
In such cases, meter reading results manually taken by the service technician are entered in IS-U and then sent to MDUS. As soon as a meter reading result is communicated to MDUS, changes or cancellations of the meter reading result also have to be communicated to MDUS to keep data consistent between SAP and MDUS.
The main reason for providing these meter reading results to MDUS is that VEE processing takes place in MDUS. The meter reading result for device installation in particular is quite important for validation of subsequent meter reading results by MDUS. As a prerequisite for this use case, BAdIs ISU_AMI_ATTR_MR and ISU_AMI_SEND_MR have to be activated. In the first steps, a meter reading result is entered in SAP and communicated to MDUS:
To keep the data in SAP for Utilities and MDUS synchronized, changes of meter reading results in SAP for Utilities have to be communicated if they have previously been sent to the MDUS.
The installation / removal / replacement of a device can also be cancelled in SAP for Utilities. In this case, the previously sent meter reading results related to the device transaction are obsolete and cancelled in SAP for Utilities. To ensure that data remains consistent, SAP for Utilities sends a cancellation request to MDUS:
Use Case 4: Reading One Customer's Meter: On Demand Read
A utilities customer is moving out (or changing suppliers), so this transition requires reading that customer's meter on a certain date. This use case is very similar to use case 3, but it simply handles one customer versus a larger number.
SAP for Utilities sends out a request to read the customer's meter on a given date to the MDUS by invoking the enterprise service Request Smart Meter Meter Reading Document Creation. MDUS then acknowledges the request by invoking Change based on Smart Meter Meter Reading Document Creation Confirmation enterprise service operation, either confirming that it will read the meter as scheduled or that it can't read the meter in question because it doesn't have POD data.
The MDUS then reads the meter on the date the read was requested: either as soon as possible (for a present or past date, since it is presumed that the MDUS has readings for past dates already stored) or on the specified date (in the case of a future date). The MDUS sends the meter reading to SAP for Utilities by invoking the Create Meter Reading Document Result enterprise service operation, which uses the Meter Reading Document business object. After SAP for Utilities has uploaded the meter reading document, it sends a confirmation message back to the MDUS, invoking the Confirm Meter Reading Document Result Creation enterprise service operation
The following table summarizes the steps in this use case and the associated enterprise services:
Use Case 5: Uploading Usage Data to SAP EDM
The services provided in this use case offer an updated set of enterprise services and improved underlying functionality, capable of processing interval usage data in a run-time-optimized way.
To create a bill in SAP ERP 6.0, information about utilities usage must be uploaded from the meter into SAP ERP 6.0. Live meters are able to collect usage data at regular intervals, for example every 15 minutes. This data is then uploaded to the AMI system usually once per day. Since bills are typically created monthly, the profile data is uploaded to SAP ERP 6.0 at least once a month. In the past, uploading profile data from the metering system platform into SAP for Utilities required a labor-intensive custom integration. Now, using enterprise services, the process is eased considerably. Furthermore, the uploading process can be monitored allowing navigation into the corresponding XML messages.
Profile data uploads are triggered on a regular schedule in order to produce a bill. The AMI system sends profle data as bulks to the SAP NetWeaver Process Integration, which then sends it to SAP backend systems by invoking the enterprise service Create Utilities Time Series Item As Bulk. All the profile data is then uploaded into SAP ERP 6.0, where it can be used to create the customer's bill. As confirmation that the data was received, SAP ERP 6.0 in turn triggers the Confirm Utilities Time Series Item Creation As Bulk service operation, which is sent to SAP NetWeaver PI. PI then formats an XML message that sends a confirmation to the AMI system.
Related enterprise services can be used on an as-needed basis.
The following table summarizes the steps for performing an initial upload of prifile data and the associated enterprise services:
The following table summarizes the steps for performing a follow-up upload of profile data and the associated enterprise services.
Use Case 6a: Remotely Disconnecting and Reconnecting a Meter
This use case explains how a utility could use the AMI ES bundle to remotely disconnect a customer who has not paid his or her bill. It also explains how the services in this bundle can be used to remotely reconnect a customer once the bill has been paid.
A utility would employ the enterprise services in the Advanced Meter Infrastructure ES bundle to disconnect a meter only after following a defined process of trying to get the customer to pay the delinquent bill. The process begins when a utility sends a customer a regular monthly bill. If the customer does not pay the bill in a timely fashion, he or she will end up on a list of delinquent customers. As a result, the following process steps could be performed: escalating the bill to dunning level 1, which entails sending mail to the sales manager and a reminder to the customer. If the customer still does not pay the bill, the process moves to dunning level 2, which requires calling the customer and perhaps taking other measures such as load reduction.
Table 1. Sample Collection Strategy and Related Activities
If the customer still does not pay, the collection strategy escalates to dunning level 3 and the call center begins the disconnection process.
A call center employee logs onto SAP for Utilities. The employee then fills out and submits a disconnection document (see Figure 2) that details the ID of the meter to be disconnected and the date when service will end. This triggers the enterprise service Request Utilities Connection Status Change Request. The request is sent from SAP for Utilities to SAP NetWeaver PI. PI then formats an XML message with these details and sends it to the MDUS system. The MDUS system then transmits a message to the meter to switch itself off, using a communications technique such as GSM, GPRS, or broadband over power lines. The AMI system then sends an XML message back to SAP NetWeaver PI, which triggers the Change Utilities Connection Status Change Request based on Confirmation enterprise service operation, which confirms to SAP for Utilities that the meter has in fact been disconnected.
Figure 3. Disconnection screen (click to enlarge) Reconnection
To reconnect service, the customer contacts the utility and pays the bill. The agent then fills out a reconnection form in SAP for Utilities (see Figure 3), which also triggers the Request Utilities Connection Status Change Request enterprise service operation, this time with a parameter that states that the meter should be reconnected. Power is remotely restored to the customer, and the meter sends back a message that triggers the Change Utilities Connection Status Change Request based on Confirmation enterprise service operation, which confirms the processing of the reconnection to the SAP backend system.
The following table summarizes the steps involved in disconnecting or reconnecting a customer and the associated enterprise services:
Figure 4. Reconnection screen (click to enlarge) Use Case 6b: Manually Disconnecting and Reconnecting a Smart Meter
Communication of the disconnection status for manual disconnection and reconnection is supported for SAP ERP 6.0 EhP5 SP09, SAP ERP 6.0 EhP6 SP05 and all higher releases and support packages.
In contrast to Use Case 6a, the smart meter is not disconnected or reconnected remotely. Instead, a service technician disconnects and reconnects the smart meter manually. The change of disconnection status is sent to the external MDUS system so that MDUS can observe the disconnection status in VEE processing. If the disconnection status is not connected to MDUS, MDUS does not know the correct status and is not able to perform VEE processing.
Use Case 6b works similarly to 6a, and involves the following process steps:
Use Case 7: External Profile Calculation
To create a bill in SAP ERP 6.0, information about utilities usage must be uploaded from the meter to SAP ERP 6.0. For live meters registered in an AMI system, usage data is collected every 15 minutes. This data is then uploaded - usually once per day - to the AMI system. Since bills are typically created monthly, this profile data is then uploaded to SAP ERP 6.0 at least once a month. This profile data is used to bill customers on the basis of accurate and flexible time-of-use rates. A time-of-use rate allows you to record different price blocks per day (for example on, off, and critical peak times). SAP for Utilities supports two approaches for the time-of-use-based billing process. One approach uploads all profile data to the SAP for Utilities Energy Data Repository. The billing process accesses the profile data in the repository and performs actions such as the aggregation of profile values to retrieve the total consumption within a time-of-use block. The necessary services required for this process are listed in use case 8: Event Management. The second approach does not upload the profile data to SAP for Utilities. In this case, the data is kept in the external meter data repository and is accessed using an enterprise service. This service performs the requested action, such as an aggregation, directly in the external meter data repository and only returns the results to SAP for Utilities. The subsequent billing process catches the data and prepares a billing document.
The following table summarizes the steps in this use case and in the associated enterprise services.
Use Case 8: Event Management
Smart meters are able to communicate with an AMI Head End system and share information about their current status, as well as inform the head end system about events that have occurred (such as an outage or a meter malfunction). Selected events are forwarded from the head end to SAP for Utilities, where the event data is analyzed and follow-up actions are created. For example, in the case of a meter malfunction, SAP for Utilities can create a workforce order to repair the meter.
The following table summarizes the steps in this use case and in the associated enterprise services.
Use Case 9: Text Messaging to AMI Device
Modern smart meter devices are capable of receiving and displaying text messages sent out by SAP for Utilities. This feature allows the Utility to communicate in a new way for customers. For example, the Utility is able to inform the customer about the progress of inquiries or send out a dunning notice.
The following table summarizes the steps in this use case and in the associated enterprise services.
Certified Partner Applications implementing this ES BundleCertified Partner Applications for AMI
Connectivity
This bundle achieves connectivity between backend processes in SAP for Public Utilities and the metering system platform using SAP NetWeaver PI or Peer-to-Peer communication via WS-RM (KW documentation: http://help.sap.com/saphelp_nw73/helpdata/en/2c/84258a70e940d8972bf5f3b01e6012/frameset.htm).
The AMI system communicates with a customer's meter via GSM, GPRS or perhaps eventually broadband over power lines.
System Requirements
Related ES BundlesLinksSDN and SAP Links and related documents
Page:Advanced Meter Infrastructure Business ObjectsPage:Advanced Meter Infrastructure Enterprise ServicesPage:Advanced Meter Infrastructure Process ComponentsPage:Advanced Meter Infrastructure Use Case -- Remotely Disconnecting and Reconnecting a MeterPage:Advanced Meter Infrastructure Use Case -- Uploading Usage Data
2,127,830
The HP Print Service Plugin is the only print driver that you'll need to easily print documents, emails and pictures from print-supported applications to a variety of HP Printers, including HP OfficeJet, HP LaserJet, HP DesignJet, HP Photosmart, HP DeskJet and HP Envy.
You can discover and print to HP printers that are: ⢠Connected to the same network as your mobile device ⢠Broadcasting a Wi-Fi Direct network ⢠Connected to the mobile device via a USB On-the-Go cable You won't see the app on your device, but it's there! Just select Print or Share to PSP when you need to print. Just tap the menu button to reveal the print option. Location of menu button may vary depending on your model of Android⢠device. The HP Print Service Plugin simplifies printing on your Android⢠Kitkat⢠(v4.4) and newer devices. If you use Android 6 (Marshmallow) or earlier, you might need to enable the HP Print Service Plugin in your device's settings For more information on using the HP Print Service Plugin or details on supported HP Printers, go to: https://support.hp.com/us-en/document/c04024231/?openCLC=true For more information on Mobile Printing in general, go to: https://www.hp.com/go/mobileprinting
Collapse
2,127,830 total
4
2
Read more
You will get access to a lot of amazing remote functionalities â see them all here.
Get your free trial now!Raise the bar â do it remotely with HP SDSRemote printer management â save resources with HP SDSSelected benefits of HP SDSRead moreâ¦
How to get started JetAdvice takes printer fleet management to a new level of efficiency and ease of use.Our advanced MPS solutions give you full control of the printer fleets of your customers.Contact usCases
Preventive Maintenance Remote Configuration Optimize Supply Use Know Your Printer Fleet CookiesThis site uses cookies: Find out more.Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |