Existing Xworks Plus (XWP) projects with PXC64/128 and PXC00..200 devices can be combined and extended with PXC4, PXC5, and PXC7 automation stations. Below, four different scenarios are described for such an extension. These scenarios are examples and have to be adjusted to the project and the customer needs.

  • Scenario A:
    Adding a single new PXC4/5/7 automation station and/or primary control unit.
  • Scenario B:
    Adding a new floor or building part with new room automation and a primary control unit.
  • Scenario C:
    Securing existing room automation from unsecure communication, adding a new hub.
  • Scenario D:
    Extending and securing an existing installation (combination of scenario B and C).

Each scenario starts with a high-level topology followed by a summary about the required adaptations in the runtime system as well as in engineering and commisioning.

Scenario A: Adding a single new PXC4/5/7 automation station and/or primary device

 

 

Runtime system

Engineering and commissioning

Automation

  • BACnet referencing (mixed BACnet revisions): Additional referencing from/to PXC4/5/7 devices.

Primary server in PXC64/128 and PXC00..200:

  • Time manager: Keep PXC64/128 and PXC00..200 configuration. Options are:
    • Keep Desigo CC as time manager (recommended).
    • Configure PXC5/7 as new time master (NTP), provide time to PXC64/128 and PXC00..200 primary server(s) (“manager of primary server manager”) (recommended).
    • Add PXC4/5/7 as new recipient (third-party BACnet-browser required).
  • Alarm routing: Keep PXC64/128 and PXC00..200 as is.
  • Global calendar: Keep PXC64/128 and PXC00..200 structure and add PXC4/5/7 calendar (use one of the option described on the right side).
  • Device supervision: PXC64/128 and PXC00..200: Primary server or other PXC device does "life check" of backup servers, separate life check on new PXC4/5/7 devices.
  • System test necessary.
  • XWP:
  • Network: Update BBMD, BDT, etc.
  • XWP-BOS: Stays as is.
  • ABT Site: Define new PXC4/5/7 device, BACnet referencing with PXC64/128 and PXC00..200.

Primary server in PXC64/128 and PXC00..200:

  • Time manager:
    • XWP: No upload/RTE online recipient list lost (not recommended).
    • Engineer time manager (NTP) in ABT Site and add primary server as recipient, no actions required in XWP.
    • Add PXC5/7 as time recipient in Desigo CC.
  • Alarm routing: Setup independent new alarming for PXC4/5/7 devices (same [NC] in ABT).
  • Global calendar: Two options are available:
    • Add calendar object from PXC4/5/7 to Desigo CC calendar management (recommended).
    • If no Desigo CC: PXC4/5/7 calendar needs to be engineered independently.
  • Note: New calendar solution in planning.
  • Device supervision: Define PXC5/7 as supervisor (not PXC4!) for PXC4/5/7 devices.

Room

Installed Desigo room automation is not impacted, still communicates with central functions (grouping) and PXC64/128 and PXC00..200 primary control units (BACnet referencing).

 

Operation and monitoring

  • Desigo Control Point can online discover and learn new PXC4/5/7 devices.
  • New PXC4/5/7 device with new alarming on Desigo Control Point.
  • PXM20 shows PXC4/5/7 devices as third-party devices.
  • Learn PXC4/5/7 devices into Desigo Control Point with existing functionality in ABT Site and reload Desigo Control Point.
  • Alarming

Mangement

  • Online learning as is for PXC64/128 and PXC00..200 and PXC4/5/7 devices.
    • New alarm routing for newly added PXC4/5/7 devices.
  • Operation and monitoring as is for existing devices, add new devices.
  • Offline import for newly added PXC4/5/7 devices.
  • Life check: add {PXC4/5/7 “supervisory” device} to Desigo CC.
  • Migrate Desigo Insight to Desigo CC.

Scenario B: Adding a new floor or building part with new room automation and a primary device

 

 

Runtime system

Engineering and commissioning

Automation

  • No change on installed system.
  • Add coordination between existing and new automation devices according to customer requests, using BACnet references.
  • Rest is the same as scenario A.
  • XWP: No change.
  • Rest is the same as scenario A.

Equipment

  • Existing PXC64/128 and PXC00..200 primary server stay as is. Coordination with existing room solution stays as is.
  • New PXC4/5 devices as NTP time manager for new Desigo room automation (independent of existing installation).
  • Rest is the same as scenario A.
  • ABT Site: Add new primary control unit, engineer grouping for new room solution.
  • XWP: No change (PXC4/5/7 devices not supported in network work manager).
  • XWP-BOS: PXC4/5/7 check-in/out supported.
  • Rest is the same as scenario A.

Room

  • Room automation, grouping.
  • Central functions: Add new room devices to existing central functions (or define new groups).
  • Rest is the same as scenario A.
  • ABT Site: Add new room automation devices.
  • Extend existing central functions with existing Desigo room automation.
  • XWP-BOS: Check in new Desigo room automation in existing BOS.
  • Rest is the same as scenario A.

Operation and monitoring

  • Desigo Control Point: Online learning of new devices.
  • Rest is the same as scenario A.
  • ABT Site: Offline learning of new device in Desigo Control Point.
  • Rest is the same as scenario A.

Mangement

  • Support alarm management for existing PXC64/128, PXC00..200, and new devices.
  • Rest is the same as scenario A.
  • Import new devices (reuse existing features).
  • Rest is the same as scenario A.

 

Scenario C. Securing existing room automation from unsecure communication, adding a new hub

 

 

Runtime system

Engineering and commissioning

Automation

  • Add new PXC5/7 devices:
    • BACnet/SC with hub.
    • BACnet routing, keep BACnet IPv4 port open.
  • Rest is the same as scenario A.
  • ABT Site:
    • Add hub, create and load certificates to PXC5/7 devices (hub).
    • Setup BACnet routing for Desigo room automation devices from BACnet Secure Connect to IPv4.
  • Rest is the same as scenario A.

Equipment

  • No change on PXC64/128 and PXC00..200.
  • BACnet referencing to Desigo room automation stays unchanged (communication via PXC5/7 router and hub).
  • XWP: No actions required.

Room

  • Load new firmware, upgrade device (large root-fs).
  • Configure DXR2/PXC3 device as BACnet Secure Connect node.
  • DXR2/PXC3 devices keep device name, number, IP address, etc.
  • ABT Site: Change from IPv4 to BACnet Secure Connect node, assign hub, create and load certificates to DXR2/PXC3.
  • XWP: DXR2 and PXC3 still visible in project and network manager, but no BACnet Secure Connect properties.
  • XWP-BOS: Check-in/-out stays as is.

Operation and monitoring

  • Same as scenario A.
  • Same as scenario A.

Mangement

  • Same as scenario A.
  • Same as scenario A.

 

Scenario D: Extending and securing an existing installation

 

 

Runtime system

Engineering and commissioning

Automation

  • Add new PXC5/7 devices:
    • BACnet/SC with hub.
    • BACnet routing, keep BACnet IPv4 port open.
  • ABT Site:
    • Add hub, create and load certificates to PXC5/7 devices (hub).
  • Setup BACnet routing for Desigo room automation devices from BACnet Secure Connect to IPv4.

Equipment

  • Same as scenarios B and C.
  • Same as scenarios B and C.

Room

  • Load new firmware, upgrade device (large root-fs).
  • ABT Site: Change from IPv4 to BACnet Secure Connect node, assign hub, create and load certificates to DXR2/PXC3.
  • XWP: PXC5/7 not visible in network manager.

Operation and monitoring

  • Same as scenarios B and C.
  • Same as scenarios B and C.

Mangement

  • Same as scenarios B and C.
  • Same as scenarios B and C.