PI Cloud Connect. Customer Onboarding Checklist

Transcription

1 PI Cloud Connect Onboarding Checklist PI Cloud Connect Customer Onboarding Checklist Version 1.0.4

2 Content Introduction...3 Business requirements...3 Framing the context of the data exchange... 3 Onboarding Process...3 Signing Up information... 4 Account Activation... 5 Technical requirements...5 PI Cloud Connect nodes... 5 Users Accounts... 6 Check List...7 O S I s o f t P a g e 2 7

3 Introduction This document is aimed at facilitating the onboarding process of a new customer who wants to use PI Cloud Connect. Even though the philosophy and the design behind the product is to make customer as self-sufficient as possible through the entire process of using this service, our experience tells us that some preparation work helps making the process more effective. Business requirements PI Cloud Connect allows customers to share data between PI Systems. It is therefore expected that a customer who signs up for the service already has one or several PI Systems deployed in his (her) organization. If the data is to be exchanged with another company, it is also expected that a business relationship already exists with that company. PI Cloud Connect will not explicitly expose information about others companies or users having signed up for the service. Framing the context of the data exchange Here are a list of questions that each customer interested in signing up for PI Cloud Connect might want to answer before engaging in the sign up process: What is the business goal for sharing data? What value does it bring to you and the other party? Do you want to send or to receive data or both? Do you have a sense for the criticality/sensitivity of the data you are planning to share? 1 As a Publisher Who will receive your data? Have you validated that the company receiving the data has signed up for the service? Have you already defined what data you want to share? As a Subscriber Who is sharing data with you? What data are you looking for? Onboarding Process The picture below shows the information required for a user to sign up for PI Cloud Connect. This picture is a screen capture of the sign up page available at Even though PI Cloud Connect is the only 1 Some guidelines about defining the sensitivity and criticality of the data can be found in the ISA document as well as the FIPS 199 publication. O S I s o f t P a g e 3 7

4 service available at this time, users sign up only once under the PI Cloud Services umbrella and can then access and use any of the services available. Signing Up information First name: Last name: Windows Live ID: Subdomain: First name of the customer signing up for the service. The first name is use to identify the user in the PI Cloud Connect Customer Portal. Last name of the customer signing up for the service. The first name is use to identify the user in the PI Cloud Connect Customer Portal. A valid Windows Live ID account (a.k.a. Microsoft Account) is required to authenticate users who want to sign in the PI Cloud Connect Customer Portal. The account has to exist before sign up for PI Cloud Services. Go to Live.com if you don t have an account yet and create one. This field will be used to identify the organization, third party or affiliate that the customer is signed up for. The full domain name (i.e. CompanyA.picloudservices.com ) will be used to sign in the PI Cloud Connect Customer Portal. It uniquely defines a tenant in the PI Cloud Services offering. Therefore, this name has to be unique among all the tenants who have signed up for the services. O S I s o f t P a g e 4 7

5 Phone number: Sign Up: This field is optional. By clicking on the Sign Up button, the customer acknowledges that they have read AND agreed to the OSIsoft Terms of Services and Privacy Statement referenced in the Sign Up page. Account Activation After completing the sign up process, the user will receive an at the address provided (the Windows Live Id account). This contains a hyperlink required to activate the account. Since the process of provisioning a new tenant may take several days, users should not expect to receive the activation instantaneously. We strongly recommend that users verify that their configuration in Windows Live doesn t block or filter the activation . The hyperlink provided to activate the account is valid for 48hours after receipt of the . The PI Cloud Connect Customer Portal should be accessible from any modern browser running on any device; it is built using HTML5 technology and Java Script. You might need to adjust the security settings of your browser to enable Java Script. For customers using Windows, we recommend using Internet Explorer version 8 and higher. Technical requirements Since PI Cloud Connect is transferring data from a PI AF structure to another, it is expected that customer will have configured PI AF both at the source and the destination. The PI Cloud Connect Customer Portal doesn t provide functionalities to create or organize structures in PI AF. The data has to be prepared using standard tools such as the PI System Explorer before it can be used by PI Cloud Connect. PI Cloud Connect nodes PI Connect, the On-Prem components of PI Cloud Connect, has the following requirements: Operating System (OS) versions: 32 or 64 versions of Windows Vista SP2, Windows 7 or Windows 8 32 or 64 versions of Windows Server 2008 SP2 64 versions of Windows Server 2008 R2 or Server 2012 Software: Microsoft.Net Framework 4.5 or higher AF Client 2012 SP2 (version 2.5.2) or higher Others: Direct access to Internet is required O S I s o f t P a g e 5 7

6 Internet Access If access to Internet is managed through a proxy server or if your corporate firewall is controlling the access to public resources, you might need to contact your IT department to make sure that the PI Connect node can access resources hosted in Windows Azure. During the platform validation check performed by the PI Connect node setup kit, any connectivity issue between the Pi Connect node and the Azure components will be reported to the user so that corrective action can be taken before further deployment. Users Accounts When deploying the PI Connect components on the computer used to access PI AF, several sets of credentials are required by the installation kit. Windows Service account The PI Connect Windows Service requires a Windows Identity with the following: Log as Service privileges Must have been used once to log on the computer Must have access to both PI AF and the PI Archive o To read the data targeted for a publication o To write the data targeted for a subscription When using a proxy server, that account should be able to communicate with the Internet via the proxy server. Windows Live ID (Microsoft Account) The PI Connect Windows Service requires a Windows Live account associated with the tenant it is connecting to. This account can be the same as the one used during the sign up process. O S I s o f t P a g e 6 7

7 Check List The table below is a summary of the information provided so far. Business Contact collaborating party Validate that the collaborating party uses PI Cloud Connect Define the scope for data sharing Assess the sensitivity/criticality of the data to be shared PI Cloud Services Onboarding Define the tenant name Define/create the Windows Live ID used for administrating the tenant Read and agree with Terms of Use and Privacy Statement PI Cloud Connect Customer Portal Validate that an activation has been received Activate the account/tenant within 48hrs Sign in the Customer Portal is successful Navigation within the Customer Portal is successful Data Preparation Data to be shared is organized in PI AF Security around access the data is defined/known PI Connect Node Pre-requisites 32 or 64 versions of Windows Vista SP2, Windows 7 or Windows 8 32 or 64 versions of Windows Server 2008 SP2 64 versions of Windows Server 2008 R2 or Server 2012 Microsoft.Net Framework 4.5 or higher AF Client 2012 SP2 (version 2.5.2) or higher Access to Internet User Accounts and Credentials User Account for the PI Connect node Windows Service Windows Live account to connect to the Customer Portal Yes/No O S I s o f t P a g e 7 7