Issue
- No standard test or performance validation procedure is available.
- Each EcoStruxure Building Operation system requires a site-specific approach based on its configuration.
- Guide on what to check after EBO / Windows updates
Product Line
EcoStruxure Building Operation
Environment
- EcoStruxure Building Operation
- Enterprise Central (EC)
- Enterprise Server (ES)
- Automation Server (AS)
- WebStation
- WorkStation
- PostgreSQL / Timescale Database (if used)
- SQL Server (if used)
- External databases (if used)
- Third-party interfaces (if used)
Cause
When validating system performance (for example, after an upgrade or Windows updates), a standard procedure may be expected; however, EcoStruxure Building Operation systems differ significantly in server roles, databases, and integrations, requiring a site-specific validation approach.
Resolution
Use the following structured approach to create and execute a site-specific performance validation procedure for EcoStruxure Building Operation systems.
1. Prepare Baseline (Before Changes)
Capture current system performance to enable comparison.
- Record CPU usage (Enterprise Central / Enterprise Server)
- Record memory usage (Enterprise Central / Enterprise Server)
- Measure network latency between Enterprise Central / Enterprise Server and Automation Servers
- Capture system load indicators:
- Active alarms
- Trend logs
- Connected users
- Measure user experience:
- WebStation load times
- WorkStation login times
- Graphics load performance
2. Perform Immediate Post-Change Validation
Confirm the system is operational after updates or changes.
- Confirm all servers are online
- Expected result: No offline or red cross states
- Verify licenses are valid
- Confirm all required services are running
- Validate communication between:
- Enterprise Central
- Enterprise Server
- Automation Servers
3. Inspect Logs and System Health
Identify early warnings or failures.
- Review Windows Event Viewer
- Review EcoStruxure Building Operation logs
- Check for:
- Service failures
- Certificate issues
- Database warnings
4. Verify Core Functionality
Ensure key features are operating correctly.
- Verify alarm generation and acknowledgment
- Confirm trend data is being recorded
- Validate graphics loading and bindings
- Test access via:
- WorkStation
- WebStation
- Mobile clients (if applicable)
5. Validate Performance
Assess system responsiveness and resource usage.
- Validate WebStation responsiveness
- Expected result: Acceptable page load and navigation times
- Monitor CPU usage trends
- Monitor memory usage trends
- Check database performance
- Trend retrieval speed
- Alarm list loading
- Verify network latency
- Confirm communication stability
- Expected result: No intermittent offline or red cross states
6. Perform Soak Testing (24–72 Hours)
Validate stability under normal operating conditions.
- Operate the system under typical load
- Monitor:
- CPU stability
- Memory trends
- Communication reliability
- Confirm no gradual performance degradation
7. Confirm Regression Checks
Ensure no functional or performance regression.
- All servers remain online
- No communication drops
- WebStation operates reliably
- Trends and alarms function correctly
- Reports generate successfully
8. Define Rollback Plan
Prepare recovery actions if issues are identified.
- Define rollback criteria:
- Persistent communication issues
- Sustained high resource usage
- Performance degradation
- Database latency issues
- Define rollback method:
- Restore from backup
- Revert to the virtual machine snapshot
9. Document and Sign Off
Capture results and confirm validation completion.
- Record system version and Windows update details
- Document test results and identified issues
- Obtain stakeholder or customer sign-off
Reference Materials
Use relevant documentation to support the validation approach:
