Issue
Users and customers often confuse the terms hotfix and upgrade when discussing updates to the EBO platform. This article clarifies the distinction to help with proper planning and communication.
Product Line
EcoStruxure Building Operation
Environment
- Building Operation Enterprise Server
- Building Operation Automation Server
- Building Operation Central Server
- Building operation MP, RP and other upgradable field controllers.
Cause
The confusion typically arises due to:
- Similar version naming conventions (e.g., 4.0.1 vs. 4.0.1 CP1).
- Lack of awareness about the scope and impact of each type of update.
- Misunderstanding of the validation requirements for regulated environments.
- Assumption that all updates require the same level of planning and downtime.
Resolution
EBO Hotfix or Consolidation Point (CP)
- Purpose: Targeted fix for specific bugs or issues.
- Scope: Minimal — typically affects only a few files or modules.
- Impact: Low risk; does not change the database schema.
- Versioning: Minor version change (e.g., 4.0.1 → 4.0.1 CP3).
- Use Case: Applied when an issue needs resolution without waiting for a full release.
- Installation: Quick and simple; may not require full system downtime.
EBO Upgrade
- Purpose: Introduces new features, performance improvements, and broader fixes.
- Scope: Comprehensive — affects multiple components and may include database schema changes.
- Impact: Higher risk and complexity; requires planning and validation.
- Versioning: Major or minor version change (e.g., 4.0.1 → 5.0.1).
- Use Case: Planned system enhancement, often requiring customer approval or validation.
- Installation: More involved; typically requires backups, downtime, and post-upgrade testing.
