Simple Cloud Based Proof of Concept

 

The eiPower Cloud Based Proof of Concept (POC) provides real results from production environments, giving an accurate estimation of your company’s potential savings

Get results using real data from your environment. 

Company Executives want to know the payback before investing in Cloud or On-Premise applications.
The eiPower Cloud Services POC can be conducted by Facilities, C-Level or any department measured by achieving sustainability goals and/or reducing the cost of doing business.

The eiPower application is as simple and safe as installing a smartphone application. Download and distribute the app, evaluate with sustainability, IT enhancement, and/or cost reduction criteria of success using our comprehensive POC report. (see below)

proof-img1
Report shows average costs, kWh, and carbon emission usage and savings.

Results are the same for cloud or on premise versions of eiPower.

POC can be run by Facilities or non-technical staff.

Does Not Change Desktop Settings

Specifically what was spent during the POC measuring period, and what the organization could have saved.

Gives management justification using data from their own environment.

1

Simply choose your POC candidates, email the client or email the link to the client from the secure Microsoft Azure Cloud

2

Tell us how much you pay for power we can handle any worldwide utility pricing scheme

3

EIP configures cloud server and provides comparison report

eiPower Cloud POC FAQs

How does this work?

Deploy the eiPower Agent by email, link, GPO or your PC management tool.  The eiPower Server is configured and maintained in the Microsoft Azure Cloud. The client measures the amount of time the computer could have gone into low power mode. At the end of the POC, the report prompts for low power schemes including standby, hibernate, and off, and the report shows Actual vs. Modeled usage – What was used and what the organization could have saved.  The report presents the data in average savings per day.  Those values are multiplied by the number of the computers in the organization, giving a very good estimate of kWh usage, cost and carbon emission savings. 

What about security?

More than half of the US Fortune 500 use Microsoft Azure.

Microsoft Azure Security and Compliance Overview

What are some POC best practices?

POC candidates should represent daily business use. IT computers are not good candidates as they do not have standard images, and are modified by users with administrator rights. Lab PCs are not good candidates as they do not represent daily use of the organizations business.

Install the client on a few users at first and confirm with EIP they are showing up in the cloud server. 20-30 computers will produce enough data for reports. When fully deployed, we will capture the data for 20 days, and run the report on the 21st day.

The agent does not change any desktop settings, it gathers data only. If your company draws power from multiple utilities at multiple locations, and you wish to have them included in the POC, you will need to deploy POC clients at those locations, and provide power pricing for those locations as well.

What data is sent to the cloud?

The computer and monitor model, a series of 1s and 0s coded for Window low power mode and on/off, and the duration of time the computer spent in those low power modes. Finally, the present power scheme is also sent. No sensitive information at all. This data is used to calculate kWh usage, cost, potential savings and carbon emissions.

What should i expect?

Before the eiPower Cloud POC begins, EIP or Partner will garner the Criteria of Success of the POC. Whether it be Tier 1 savings, or Tier 2 IT enhancement, the items will be documented and proven in the POC report. There is virtually no IT involvement and the user will see no impact in performance. We will also need the price your organization pays for power to calculate cost and savings. (peak, off peak, mid-peak, seasonal). Finally, if you are using multiple locations that draw power from different utilities, pricing from them, as well as a high and low IP address ranges of those locations. This will allow us to automatically put computers into those locations.

How is this different from an On-Premise eiPower POC?

An on premise POC requires the IT department to dedicate significant time and resources when evaluating new products. Tasks include time from an already busy IT schedule to:

  • Configure the test lab
  • Install and configure the application in their test lab
  • Run pre-arranged tests to determine if the application affects production systems
  • Schedule with company change control procedures
  • Install on the production server
  • Install and configure SQL Reporting Server in the production environment
  • Configure the application on the production server
  • Deploy the agent, monitor for exceptions
  • Enable policies
  • Attend weekly POC meetings
  • Interact with departments measured on reducing operating expenses
  • Run reports
  • Present findings

The Cloud POC task include:

  • Deploy the agent. Both the On-premise and Cloud agent do not change desktop settings and have no impact on user productivity.

The reports are the same, however the eiPower Cloud Services POC alleviates an already taxed IT department from these tasks, and allows departments and executives, who are traditionally measured on company savings, review reports and present to management.

Click here to see all production system features