Issue Customers and integrators require a clear understanding of the data collected during registration, how it is used, the ownership model, communication expectations, connection requirements, site information guidelines, and available training. Product Line EcoStruxure Building Operation, EcoStruxure Building Data Platform, EcoStruxure Building Advisor Environment EBO Enterprise Server and Automation Servers WorkStation and WebStation Cloud‑connected EBO systems Cause Registration and cloud connectivity introduce questions regarding privacy, data flow, communication policies, configuration steps, and troubleshooting expectations. Resolution Data Collected EBO collects only configuration and performance data required to identify equipment, evaluate system health, and support lifecycle management. Configuration data includes installed servers, controllers, firmware versions, and configuration details. Performance data includes CPU and memory utilization, server trace logs used for error investigation, and lifecycle event logs showing upgrade and configuration history. No personal or sensitive user information is collected. Data Ownership Personally Identifiable Information (PII) is owned by the individual and handled according to applicable privacy regulations. Technical System Data (Raw Data) is owned by the end user or site owner. Technical System Metadata (Calculated Data) is owned by the party that develops the algorithms that generate it. Data Storage Location Registration data is stored in secure Microsoft Azure cloud infrastructure located in Ireland. Use of Customer Data Customer data is never sold or shared with third parties for advertising or commercial purposes. Use of Email Addresses The provided email address receives the registration confirmation. After registration, Schneider Electric contacts the customer only if there is an urgent product issue requiring immediate attention and the system integrator cannot be reached. Marketing Communications Email addresses collected during registration are not used for marketing materials or newsletters. GDPR Compliance The product follows applicable privacy, data handling, and security regulations including GDPR. The terms governing this compliance are available within the product’s login interfaces. Site Naming and Registration Contact Details Site information should accurately reflect the deployed system. Installers must use the customer’s site name and customer contact information, not their own, unless they are the actual system custodian. Registration and Cloud Connectivity Steps Enable cloud communication Open WorkStation. Navigate to Control Panel → Security and Communication → Cloud Connectivity. Set Communication setting to Enable cloud communication. Register the installation At the WorkStation login screen, choose Register. Select I am the building’s owner, facility manager, or authorized custodian. Enter the site and contact details, then select Submit. Choose Exit and return to WorkStation. Update registration details From the login screen, select Edit registration, choose the custodian option, update information, and submit. When already logged in, go to Help → Registration → Edit information, update details, and submit. Cloud Endpoints and Ports EBO communicates outbound over TCP 443 to the following hostnames: app.schneider-electric.com cnmiothubappstna.blob.core.windows.net cnm-ih-na.azure-devices.net Cloud provider IP addresses may change dynamically; allow‑listing should be performed by hostname. Copying the System ID To copy the System ID, right‑click the value in the displayed dialog and select Copy. Partial Site Architecture Display (~ Indicator) A tilde (~) symbol indicates that initial communication has completed but the full system archive has not yet been uploaded. Allow time for the archive to finish transferring while maintaining connectivity. Training Availability Training for licensing, registration, and cloud connectivity is available through the corporate learning platform. The course provides guidance on enabling cloud services, completing registration, and maintaining site information.

Issue New user is unable to complete the BDP registration process Product Line EcoStruxure Building Data Platform Environment Building Data Platform Cause User clicks the registration button which has been mailed to them but get an “Opps! This page cannot be found.” error Resolution The user is already logged into BDP using another User account. This can occur if a SE user is using more than one email address to manage accounts with different business relationships. This can also occur if the user is a SE employee who is testing the system. The user should log out of BDP. Or use Incognito mode.   NOTE: If the user is logged into another SE app, this could also pose a problem. TBD

Issue New user with an external email account was created but never received an email invite Product Line EcoStruxture Building Data Platform Environment Building Data Platform Cause Incorrect email User registered for the wrong platform (UAT or Prod) IDMS issue Resolution Attempt to log in, this should kick off the registration process again Verify that the email is correct Verify which platform the user should be registered to

Issue Receive API error codes while trying to connect my API to BDP. Product Line EcoStruxture Building Data Platform Environment Building Data Platform Cause Receive the following Error codes: 400 Bad Request 401 Unauthorized 403 Forbidden 404 Not Found 500 Internal Server Error Resolution 400 Bad Request The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing) 401 Unauthorized Although the HTTP standard specifies "unauthorized", semantically this response means "unauthenticated". That is, the client must authenticate itself to get the requested response 403 Forbidden The client does not have access rights to the content; that is, it is unauthorized, so the server is refusing to give the requested resource. Unlike 401 Unauthorized, the client's identity is known to the server 404 Not Found The server cannot find the requested resource. In the browser, this means the URL is not recognized. In an API, this can also mean that the endpoint is valid but the resource itself does not exist. Servers may also send this response instead of 403 Forbidden to hide the existence of a resource from an unauthorized client. This response code is probably the most well known due to its frequent occurrence on the web 500 Internal Server Error The server has encountered a situation it does not know how to handle   Successful responses 200 OK The request succeeded. The result meaning of "success" depends on the HTTP method: GET: The resource has been fetched and transmitted in the message body HEAD: The representation headers are included in the response without any message body PUT or POST: The resource describing the result of the action is transmitted in the message body TRACE: The message body contains the request message as received by the server 201 Created The request succeeded, and a new resource was created as a result. This is typically the response sent after POST requests, or some PUT requests. 202 Accepted The request has been received but not yet acted upon. It is noncommittal, since there is no way in HTTP to later send an asynchronous response indicating the outcome of the request. It is intended for cases where another process or server handles the request, or for batch processing.