HP has been right about SolarWind.
For years, HP and SolarWind have been building a robust, scalable, and efficient software platform for building and managing large, photovoltaic (PV) arrays.
The companies have been collaborating on software that allows them to scale the system to millions of square feet and to offer cloud-hosted solar and energy storage to power-hungry consumers and businesses.
Today, the company has released its latest update to the platform, which adds the ability to integrate solar and cloud-enabled storage, along with some key changes to the existing SolarWind SDK.
These include a new developer API that simplifies the development of custom software and a new release of the SolarWind Developer SDK.
We had a chance to sit down with Jim Kelleher, Senior Vice President of the HP SolarWind Platform Group and Senior Vice president of SolarWind Software and Solutions, to get his take on the company’s latest release.
[Editor’s note: This interview has been edited for clarity and length.]
HP Solarwind Platform Group: How did SolarWind come about?
Jim Kelther: SolarWind is a small software development company.
We built SolarWind into a platform that we can use to build scalable and efficient photovolcanics and cloud services.
It was not a business-focused project.
It is really just a software development kit that helps us to do a lot of different things.
It’s really an ecosystem-based solution.
The platform itself is a tool that we developed over a year ago, and we released it as a service with the launch of the new platform.
It came as a free software, open source tool that you can use.
It supports a wide variety of cloud services, from AWS and Azure to IBM’s Spark, and there’s a ton of other options that can be added.
And it’s very flexible.
We can create a platform with the core functionality of the platform and add more functionality and other features in the future.
HP SolarLabs: So, how is the platform set up for collaboration with other companies?
What makes it different from the existing software?
What’s different is the ability for other companies to build on it.
We wanted to make it easy to integrate SolarWind with their cloud-based infrastructure and other companies that were using it, and also easy to deploy and manage it in their own systems.
There’s some other really interesting features, too, like support for embedded platforms and the ability with the cloud-backed SolarWind APIs to integrate with other cloud technologies, like Microsoft Azure.
HPSolar: So you can connect a large, complex, distributed system like a large PV array and let the developer make decisions on how the PV systems are distributed.
So it’s a very different approach to doing this than a typical software platform that you might be building today.
But there are some really interesting tools in there, too.
There is a new tool for managing the Solar Wind API.
The new tool is called SolarWind Storage.
It allows developers to easily integrate the Solarwind Storage API into their existing SolarLens applications.
HPolar: How does this fit into the larger ecosystem of solar?
Jim: So it fits into the broader SolarLenses ecosystem, and in fact, we have been working on building tools for that ecosystem for quite a while.
So, for instance, you can now manage solar and solar storage with other SolarLense tools, like SolarWind, and SolarLance and SolarTec.
And so the tools are all built into the SolarLensing stack, which is built on top of Solarwind.
SolarWind also has some really good integrations with other third-party tools.
SolarLans has a ton in there for a wide range of applications.
We’ve got a bunch of integration tools for managing storage and solar PV systems.
So for instance we have a tool called SolarWash.
And we also have a new version of SolarCloud.
We’re integrating some of the integration tools into SolarWind as well.
The way that we have to interact with SolarWind in SolarLanes is that we need to be able to see and manage our storage assets in SolarWind first.
Then we can do some of our other business processes in Solarwind, such as making sure that the PV assets are being managed correctly.
So if we need a solar storage asset, we can check it in SolarWas then and then we can make sure that it is being deployed correctly.
And then we’ll have a check-in sheet, which will allow us to get the information about that PV asset that we’re checking in and the information that we’ve got about it from SolarWind and SolarCloud and make sure it’s being managed properly.
And the new version that we released today has a lot more integrations.
So you have a SolarWind API, a SolarCloud API, SolarWats Storage API, and then you have SolarWind Connect.
This is the interface