Here it comes!Here it comes!
The time series database of GE Home Cloud,Historian for Cloud,has come.At present,GE Digital’s first native time series database built on a third-party cloud has officially been put on the AWS Marketplace.It looks like this!
Profile Historian for Cloud
Yes,this is the first industrial time series database to be launched in the cloud provider application market.It’s so simple that we don’t need to care about its architecture at all.It’s just as easy as shopping on shopping websites.At the same time,it also solves the problem of high initial investment in industrial software.You can pay by usage just like using mobile traffic.
Of course,facing the cloud,we can’t escape a soul question-how to ensure the privacy of data.When the cloud infrastructure provider is trusted,GE Historian for Cloud has no data access rights.Historian is completely attached to the user’s virtual machine instance,storage and network resources.GE only provides a complete one-click deployment solution,and the user-generated instance permissions are completely controlled by the user.
Advantages of Proficiency Historian for Cloud:
The Profile Historian for Cloud,which has been launched in AWS Marketplace,fully utilizes the following integration advantages of AWS in cloud infrastructure solutions:
-AWS Marketplace:In addition to the Professional Historian for AWS,the AWS Marketplace market also provides one-click generation of Web management console and REST query services.
-Load balancing:use Amazon Network Load Balancer(NLB)to achieve load balancing.
-Integration with CloudWatch and CloudTrail:With CloudWatch,you can access the Historian log to quickly locate and solve system problems.With CloudTrail,you can access events and monitor system performance when reading or writing data.
-Amazon Elastic File System(EFS)storage:archive and log files are stored in EFS.We can easily access the archive and log files created by Historian,and realize rapid expansion of the system and ensure security.
-Security and high availability:The Profile Historian for AWS is deployed on the virtual private cloud(VPC).It uses private subnet and TLS encryption to make it secure.In addition,the Profile Historian for AWS is deployed in multiple zones.If the data archive fails,it can be recreated within 10 seconds,with higher continuous availability.
Deployment of Proficiency Historian for Cloud
Next,follow my operation step by step to experience the magic journey of the Professional Historian for Cloud.
First of all,we need to have an account that can access the AWS management console.In particular,the availability zone deployed by the Profile Historian for AWS does not include Ningxia and Beijing,China.
Access address https://aws.amazon.com/marketplace Open the AWS Marketplace homepage,filter Vendors as”GE Digital”in the search box,and the following three application deployment scenarios will appear:
Including:
The first option is WebAdmin and Rest API for Profile Historian,which is the REST API service of Profile Historian for Cloud.Historian for AWS needs to match this service to provide REST API interface to third parties;
The second option,Profile Historian for AWS(Consumption Pricing),is a service configuration that charges according to the event count of Historian.This option is used for users who do not have licenses and do not plan to purchase licenses;
The third option,Profile Historian for AWS(Term License),is to charge the service according to the service life,provided that you have the license of Historian or are ready to purchase a new license.
Take Term License as an example,we select the third option to connect and enter the subscription interface.Here we can get a detailed description of subscription,and then select”Continue to Subscribe”to continue subscription.This process takes a little time.
Next,select the implementation option as Cloud Formation Template,select the Historian version as 2022.1,and click”Continue to Launch”to continue deployment.
In the next deployment,we will find three deployment templates.Here we can deploy the service to the existing AWS VPC,or create a new VPC through the template.The other template is used to apply the existing or newly purchased licenses.
Enter the name of your stack.This name needs to be remembered.It will be used in the subsequent application license and configuration of REST API interface services.At the same time,we will configure the CIDR of the stack as required.It will deploy VPC and set routing aggregation in two availability zones of a region.
Enter your EKS cluster name,set the interface address of Kubernetes,and the instance type.Most importantly,we need to set the UAA password.The UAA password and the UAA user admin will be the only basis for us to obtain data and obtain tokens through the REST API.We must keep in mind.
Finally,accept the terms and click”Create stack”.The system will take about 40 minutes to deploy automatically.We can view the creation process and status through the stack events monitoring.After the task is completed,we will be able to see the”CREATE_COMPLETE”status.
Connect the Profile Historian for Cloud with the Historian Manager
After deployment,we can use the Historian Manager installed on the local Windows to connect to the Profile Historian for Cloud.
Open the AWS management console,find the Load Balancers load balancer option at the EC2 entry,open the details page of the load balancer automatically created in the previous deployment process,find the DNS Name entry,and copy this address.

Then add a server in the local Historian Manager.The server information is filled in as follows:
-Server Name:DNS name copied from load balancer details
-Username:ihCloudHistAdmin(default user name)
-Password:UAA password set during deployment
After adding,click Connect to connect to the Historian in the AWS cloud.At this time,we can’t see any collectors and data archives.
Installing and setting up collectors for Historian for cloud
We can find the cloud collector installation file in the official help document of the Profile Historian for Cloud.
https://www.ge.com/digital/documentation/cloud-historian/version2022.1/t_install_collectors_using_installer.html
Download and install the cloud collector,and on the Historian server configuration page of the installation process,set the Historian server as the DNS name previously copied from Load Balancers,the user name is the default user name of Historian for Cloud ihCloudHistAdmin,and the password is the UAA password set during deployment.
Next,we find the installation directory of the cloud collector.The default is”Drive:Program Files GE Digital Historian Cloud Config.Open the”CloudHistorian ConfigurationUtility.exe”program with administrator privileges,and a command line window will pop up automatically.
Enter the operation sequence number as required.For example,we enter 1 to create a collector instance,and then enter the DNS name previously copied from Load Balancers,as well as the default user name and UAA password to connect to the Historian for Cloud server.
Then select a collector type,for example,we enter 1 to install a simulation collector,and then enter a collector instance name and press Enter to confirm to start deploying the collector.
Finally,we can see the collector status and add variables in the Historian Manager in local Windows.At this time,a complete data collection and storage process is established.
Add a license for the Profile Historian for Cloud
Term service needs to import the Historian authorization.It needs to add the existing authorization or newly purchased authorization to the network storage first,and then import it in Historian for Cloud.To purchase the Historian authorization,you can contact the sales or authorized agent of GE Digital.
The Historian for Cloud import authorization in AWS can be operated according to the following steps:
1.Search S3 on the AWS console to open the S3 bucket service of AWS.
2.Create a bucket,name and select an area for the bucket.
3.Open the bucket,upload the authorization file to the bucket,and copy the URL address of the authorization file.
4.In AWS Marketplace,open the list of GE Ditital services again,and select Profile Historian for AWS(Term License).
5.As in the previous steps,choose to continue subscription,accept the terms,and then choose to continue configuration.In the configuration interface,select the fulfillment option and software version by default,and then click Continue to start.
6.After waiting for a while,select Profile Historian License-BYOL under the deployment template.
7.The Quick Create Stack page appears,enter a new stack name,find the name of the EKS cluster created in the list of EKS clusters created previously,and fill in the EKS Cluster Name parameter,and then fill in the S3 URL of License object parameter with the URL address of the previously copied authorization file in the S3 bucket.
8.Click Next to create the stack.At this time,the license has been applied.You can view the authorization information on the local Windows Historian management client.
summary
The Profile Historian for Cloud can provide users or OEM equipment manufacturers with an autonomous,controllable,rapid deployment,plug-and-play sequential data archiving environment.At the same time,with the help of the powerful industrial data collection capabilities and product solutions of the GE Profile product family,you can quickly transfer various types of automation,instrumentation,files,and third-party system data to the enterprise-level sequential data storage center.In addition,we can also easily use data lakes and other products of cloud providers such as AWS to build operational data centers for rapid analysis,data mining and data decision-making.
At present,GE Digital’s Profile Historian for Cloud is only available in the AWS application market.At the beginning of next year,we plan to release Profile Historian for Cloud in Microsoft Azure,and other cloud platforms will also be promoted.Before the official release,you can also contact GE Digital at any time.We can support you to quickly build similar industrial sequential data storage cloud platforms on other cloud platforms one-on-one according to your needs,We look forward to your patronage.