IntelliVue Telemetry System Infrastructure Installation and Service

IntelliVue Telemetry System Infrastructure Installation and Service

MOSE225

IntelliVue Telemetry System Infrastructure

Installation and Service Guide

Access Point Controller

ICN Network Switch

Access Point Controller

Power over Ethernet Unit

Synchronization Unit

1.4 GHz Smart-hopping

Access Points

1.4 GHz

Core Access Point

1.4 GHz

Remote Antenna

1.4 GHz

Core Access Point

1.4 GHz Patient-worn

Transceivers

1.4 GHz Wireless

Bedside Monitors

1.4 GHz Patient-worn

Monitors

Part Number: 453564238181

Printed in the U.S.A.

June, 2011

Second Edition

*453564238181*

ii

MOSE225

Proprietary Information

This document contains proprietary information that is protected by copyright.

Copyright

Copyright © 2011 Koninklijke Philips Electronics N.V. All Rights Reserved.

Manufacturer

Philips Medical Systems

3000 Minuteman Road

Andover, MA 01810-1099

(+1) 978-687-1501

This document was printed in the United States of America.

Trademark Acknowledgements

Symbol is a trademark of Symbol Technologies, Inc.

HP is a registered trademark of Hewlett-Packard Company

Cisco is a registered trademark of Cisco Systems

SQL Server and Windows are registered trademark of Microsoft Corporation

All other trademarks, trade names, and company names referenced herein are used for identification purposes only and are the property of their respective owners.

Warranty

The information contained in this document is subject to change without notice. Philips Healthcare makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties or merchantability and fitness for a particular purpose. Philips Medical Systems shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.

Printing History

New editions of this document will incorporate all material updated since the previous edition. The documentation printing date and part number indicate its current edition. The printing date and edition number change when a new edition is printed. The document part number changes when extensive technical changes are incorporated.

Second Edition ...................................................................................................................................................................June, 2011

First Edition ........................................................................................................................................................................ April, 2011

MOSE225

Contents

About This Guide

Chapter 1: Overview

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

IntelliVue Telemetry System Infrastructure Components . . . . . . . . . . . . . . . . . . . 1-3

ITS Smart-hopping Access Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

1.4 GHz ITS Core Access Points. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

2.4 GHz ITS Access Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

Access Point Controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9

Synchronization Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11

Front-panel Connectors, Controls, and Indicators . . . . . . . . . . . . . . . . . . 1-12

Rear-panel Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12

Power over Ethernet Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12

Uninterruptible Power Supply. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13

General Intellivue Telemetry System Data Flow . . . . . . . . . . . . . . . . . . . . . . . . . 1-14

Defined ITS Bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14

1.4 GHz ITS Bandwidth. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14

Standard WMTS Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15

Carved-out Regions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15

Required FCC Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17

2.4 GHz ITS Bandwidth. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17

Supported Topologies and System Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19

Installing the ITS within a Non-routed Ring Topology . . . . . . . . . . . . . . . . . . 1-19

Installing the ITS on a Routed Ring Topology . . . . . . . . . . . . . . . . . . . . . . . . 1-23

Routed Star Network Topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-26

Non-routed Star Topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-28

Advantages of Star Topologies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-28

System Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-29

Deploying the ITS on a Customer-supplied Clinical Network . . . . . . . . . . . . 1-30

IntelliVue Telemetry System Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-30

Power Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-30

Safety Regulatory Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-32

Environmental Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-32

IntelliVue Telemetry System Infrastructure Product Numbers . . . . . . . . . . . . . . 1-34

Chapter 2: Planning Your ITS Deployment

Respecting Patient Care Boundaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

General ITS Infrastructure Site Planning Guidelines. . . . . . . . . . . . . . . . . . . . . . . 2-3

IntelliVue Telemetry System Infrastructure Installation and Service Guide iii

Contents

MOSE225

Performing a Physical Space Assessment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

Understanding the Radius of Coverage (RoC) Metric. . . . . . . . . . . . . . . . . . . 2-4

Determining the Number of Wireless Clients to be Supported . . . . . . . . . . . 2-6

Determining AP Installation Locations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

Traditional Hallway Patient Room Layout . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

Non-linear Patient Room Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

Placing RoC Cells on a Floorplan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

Core AP Placements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

Access Point Placement Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11

Determining the Required Number of APCs . . . . . . . . . . . . . . . . . . . . . . . . . 2-11

Locating Equipment Closets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12

Planning Cable Runs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13

Defining the UPS Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14

Planning the Sync Network Layout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15

Daisy-chained Sync Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15

Star Sync Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16

Hybrid Sync Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17

Cable Delay Rotary Switch Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17

Planning Your AP Groupings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18

Configuring AP Groups in the IntelliVue Telemetry System . . . . . . . . . . . . . 2-18

Assigning Equipment to Units in the Config Wizard (IIC) . . . . . . . . . . . . . . . 2-19

Sample AP Group Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19

Performing an RF Frequency Survey . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20

Understanding RF Coexistence Issues in the 2.4 GHz Spectrum . . . . . . . . 2-20

Transient Noise in the 2.4 GHz Spectrum. . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21

Microwave Ovens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21

Bluetooth Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21

Other Transient Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21

Continuous Noise in the 2.4 GHz Spectrum . . . . . . . . . . . . . . . . . . . . . . . . . 2-22

802.11/WiFi Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22

Cordless Phones and Headsets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22

Wireless Security Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22

ZigBee Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23

RF Site Survey Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23

Survey Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23

Using the Spectrum Analyzer Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23

Determining Measurement Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24

Assigning 2.4 GHz ITS Channels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24

Avoiding WiFi Interference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24

2.4 GHz ITS Frequency Plans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24

Frequency Plan 1,6,11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25

Frequency Plan 1,7,13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25

Using “Advanced” 2.4 GHz ITS Channel Configurations . . . . . . . . . . . . . . . 2-25

iv

MOSE225

Contents

Completing ITS Installation Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26

ITS Infrastructure Equipment Summary Table . . . . . . . . . . . . . . . . . . . . . . . 2-27

ITS Access Point Equipment Summary Table . . . . . . . . . . . . . . . . . . . . . . . . 2-27

APC Configuration Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30

Setting Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30

1.4 GHz Default AP Configuration Worksheet. . . . . . . . . . . . . . . . . . . . . . . . 2-33

Setting Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33

Blank Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33

2.4 GHz Default AP Configuration Worksheet. . . . . . . . . . . . . . . . . . . . . . . . 2-34

Setting Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-34

Blank Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35

AP Group Configuration Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36

Setting Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36

Blank Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36

Chapter 3: Installing and Configuring the ITS

High-level ITS Installation and Configuration Procedure . . . . . . . . . . . . . . . . . . . 3-2

Step 1. Complete the ITS Installation Worksheets.. . . . . . . . . . . . . . . . . . . . . . . . 3-4

Step 2. Install the ITS Infrastructure Components.. . . . . . . . . . . . . . . . . . . . . . . . 3-4

Step 3. Set Up Your Service PC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8

Configuring Your PC to Connect to the ITS Wireless Subnet . . . . . . . . . . . . . 3-8

Copying the Upgrade Wizard Files to Your PC. . . . . . . . . . . . . . . . . . . . . . . . 3-10

Step 4. Perform Initial Configuration of the APCs to be Installed. . . . . . . . . . . . 3-12

Step 5. Add the APCs to the Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14

Step 6. Run the Philips Upgrade Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16

Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16

Using the Upgrade Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17

Step 7. Verify and Configure Important ITS Settings via the APC Interface. . . . 3-22

Verifying the Filter Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23

Verifying the BOOTP/DHCP Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24

Configuring the Access Point Default Settings . . . . . . . . . . . . . . . . . . . . . . . 3-27

Configuring the 1.4 GHz Access Point Default Settings . . . . . . . . . . . . . . 3-27

Configuring the 2.4 GHz Access Point Default Settings . . . . . . . . . . . . . . 3-28

Configuring AP Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30

Step 8. Run the Philips Upgrade Wizard Again.. . . . . . . . . . . . . . . . . . . . . . . . . . 3-34

Step 9. Add APs to the Network.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38

Step 10. Rename Installed APs and Remote Antennas. . . . . . . . . . . . . . . . . . . 3-41

Step 11. Run the Philips Upgrade Wizard Again. . . . . . . . . . . . . . . . . . . . . . . . . 3-42

Step 12. Export the ITS Configuration to a Disk File. . . . . . . . . . . . . . . . . . . . . . 3-50

IntelliVue Telemetry System Infrastructure Installation and Service Guide v

Contents

MOSE225

Step 13. Restore your Service PC to its Original Settings. . . . . . . . . . . . . . . . . . 3-52

Step 14. Install ITS Bedside Monitors and Patient-worn Devices.. . . . . . . . . . . 3-52

Chapter 4: Expanding or Modifying an Installed ITS

Expanding an Installed IntelliVue Telemetry System . . . . . . . . . . . . . . . . . . . . . . 4-2

ITS Expansion Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

Archiving the ITS Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

Upgrading ITS APCs and APs Using the Philips Upgrade Wizard . . . . . . . . . . . . . 4-7

An Overview of the Upgrade Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7

Access Point Controller Upgrade Process Summary . . . . . . . . . . . . . . . . . . . 4-8

Access Point Upgrade Process Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9

Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9

ITS Upgrade Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11

ITS Upgrade Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11

Adding APCs to an Existing ITS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20

Adding APs to an Installed ITS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21

Adding an AP via Auto-Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22

Adding an AP via Manual MAC Address Input. . . . . . . . . . . . . . . . . . . . . . . . 4-26

Renaming Newly Installed APs and Remote Antennas . . . . . . . . . . . . . . . . 4-28

Adding New AP Groups to an Existing ITS Configuration . . . . . . . . . . . . . . . . . . 4-28

Add the New AP Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29

Configure the New AP Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29

Adding ITS Monitoring Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31

Replacing an AP, Remote Antenna, or APC in an Existing System. . . . . . . . . . . 4-32

Replacing an ITS Access Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-32

Replacing a Remote Antenna. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33

Replacing an ITS APC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33

Chapter 5: Troubleshooting and Testing

ITS Access Point Test and Inspection Procedures . . . . . . . . . . . . . . . . . . . . . . . . 5-2

ITS Access Point Controller Test and Inspection Procedures . . . . . . . . . . . . . . . . 5-3

ITS Sync Unit Test and Inspection Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

ITS Power over Ethernet Unit Test and Inspection Procedures . . . . . . . . . . . . . . 5-5

ITS Uninterruptible Power Supply Test and Inspection Procedures. . . . . . . . . . . 5-6

ITS Network Switch Test and Inspection Procedures . . . . . . . . . . . . . . . . . . . . . . 5-7

Using the PWD Coverage Assessment Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9

Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9

vi

MOSE225

Contents

PWD Received Signal Strength Indications. . . . . . . . . . . . . . . . . . . . . . . . . . 5-10

Troubleshooting Known Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10

Importing ITS Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13

Appendix A: Installing Multiple ITSs at a Single Hospital Site

General Requirements for Installing Multiple ITSs at a Site. . . . . . . . . . . . . . . . . A-2

Transceiver Installation Requirements for Multiple ITSs . . . . . . . . . . . . . . . . . . . A-3

Patient-worn Transceivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3

Extra MAC addresses in the Label Assignment Screen . . . . . . . . . . . . . . . . . A-3

Sync Network Requirements for Multiple ITSs . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4

Appendix B: Routed Topology Configuration Information

ICN and ITS Subnet Device IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2

Sample Routed Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3

Appendix C: Upgrade Wizard Warning and Error Messages

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2

Message Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-4

Index

IntelliVue Telemetry System Infrastructure Installation and Service Guide vii

Contents

MOSE225

viii

MOSE225

About This Guide

This

IntelliVue Telemetry System Infrastructure Installation and Service

Guide

provides complete instructions and procedures for installing, configuring, and servicing Philips 1.4/2.4 GHz IntelliVue Telemetry System infrastructure devices. This section describes the document and includes:

• Audience

• Document Organization

• Notational Conventions

• Related Documentation

• Terminology

IntelliVue Telemetry System Infrastructure Installation and Service Guide ix

x

MOSE225

About This Guide

Audience

The

IntelliVue Telemetry System Infrastructure Installation and Service

Guide

is written for qualified service personnel who will install, configure, and service the 1.4 or 2.4 GHz IntelliVue Telemetry System infrastructure as part of an overall IntelliVue Clinical Network (ICN) deployment.

Document Organization

The information in this guide is organized and presented as follows:

Chapter 1, Overview

, describes the IntelliVue Telemetry System and how it is used to provide a bi-directional data flow between the

IntelliVue Information Center and patient-worn transceivers and wireless bedside monitors.

Chapter 2, Planning Your ITS Deployment

, provides information and procedures that must be followed to ensure a successful IntelliVue

Telemetry System deployment.

Chapter 3, Installing and Configuring the ITS,

gives complete procedures to physically install the IntelliVue Telemetry System components and configure the ITS Access Point Controllers and

Access Points.

Chapter 4, Expanding or Modifying an Installed ITS,

lists procedures to expand or modify an existing, installed IntelliVue Telemetry System.

Chapter 5, Troubleshooting and Testing

, includes procedures to troubleshoot and test an IntelliVue Telemetry System installation.

Appendix A, Installing Multiple ITSs a Single Hospital Site

, lists configuration rules and guidelines to enable you to install up to 22 totally independent IntelliVue Telemetry Systems at a given installation site.

Appendix B

,

Routed Topology Configuration Information

, provides important information to help you configure a routed ITS topology.

Appendix C, Upgrade Wizard Warning and Error Messages

, lists and describes messages generated by the Philips Upgrade Wizard tool.

MOSE225

About This Guide

Notational Conventions

This guide uses the following notational conventions to convey information:

Note Notes call attention to important information.

Caution Cautionary statements call attention to a condition that could result in loss of data or damage to equipment.

Warning Warnings call attention to a condition that could result in physical injury.

Related Documentation

Please refer to these other documents for additional installation service information about the IntelliVue Telemetry System and IntelliVue Clinical

Network:

ITS Access Point Controller Installation Guide (453564238151)

- provides procedures to physically install and power the ITS Access

Point Controller at the clinical site.

• ITS 1.4 GHz Access Point Installation Guide (453564238171)

- gives procedures to install the model ITS4843B 1.4 GHz Core AP and remote Antennas at the clinical site to a wall, or above or below a ceiling tile.

• ITS 2.4 GHz Access Point Installation Guide (453564238161)

- gives procedures to install the model ITS4852A 2.4 GHz AP at the clinical site to a wall, or above or below a ceiling tile.

• ITS Sync Unit Installation Guide (453564238191)

- lists procedures to install the model M4844A Sync Unit at the clinical site.

• Upgrading ITS Access Point Controllers and Access Points

(453564238141)

- gives procedures to use the Philips ITS APC and AP

Upgrade Wizard tool to install and synchronize the firmware version on

ITS APCs and APs.

IntelliVue Telemetry System Transceiver Installation and Service

Manual

(453564124421)

Telemetry Service Tool Installation Note and Instructions for Use

(453564087971)

IntelliVue Telemetry System Infrastructure Installation and Service Guide xi

About This Guide

Terminology

MOSE225

Please note the following terms, acronyms, and abbreviations used throughout this document:

• IntelliVue Clinical Network (ICN) - This term refers to the entire Philips network. In a routed topology, the ICN includes the routers and all inter-connected Database Domain(s) and the IntelliVue Telemetry

System wireless subnet.

• Database Domain (DBSD) - This term is used to describe the

“network” that contains the Standalone IntelliVue Information Center, or the IntelliVue Database Server and its connected Information

Centers, Clients, bedsides, and infrastructure. This term applies to both routed and non-routed topologies.

• IntelliVue Telemetry System (ITS) - Cellular wireless architecture that provides two-way communications between patient-worn transceivers, wireless bedside patient monitors, and the IntelliVue Information

Center.

• IntelliVue Wireless Subnet - This term is used to describe the IntelliVue

Telemetry System (ITS) “network” that contains the infrastructure used in a routed topology to connect the IntelliVue Telemetry System devices.

• Access Point (AP) - A network device that provides bi-directional wireless access to the monitoring network for patient-worn transceivers and wireless bedside monitors.

• Access Point Controller (APC) - A network device used to manage the operation of the Access Points. One APC is elected the Master APC.

The Master APC supports the web interface to the system and manages the master configuration.

• Access Point Group/AP Group - A logical grouping of APs. AP members of the same AP Group will inherit common configuration settings

(defaults). AP groups will often map logically to the clinical units in which the ITS is being installed.

• Partnered APC - Configurable element within an AP Group used to determine which APC will manage the operation of the AP members of a particular AP Group.

• RF Access Code - Configurable element in the Smart-hopping AP defaults shared among APs and patient-worn transceivers to control wireless access to the monitoring network. Portable devices will only connect to access points with which they share access codes. The RF

Access Code allows a specific wireless client that is programmed with a matching Access Point RF Access Code to connect to that Access

Point.

xii

MOSE225

About This Guide

• Synchronization Unit - The Philips Sync Unit provides a necessary common clock signal to synchronize all the IntelliVue Access Points in the system. As patients ambulate around the hospital coverage area their transmitted data are handed over from one AP to another seamlessly without interruption or data loss.

• System ID - Configurable element in the APC Configuration to logically associate Access Points and Access Point Controllers operating within the same ITS.

IntelliVue Telemetry System Infrastructure Installation and Service Guide xiii

About This Guide

MOSE225

xiv

1

MOSE225

Overview

This chapter provides a high-level overview of the Philips IntelliVue

Telemetry System and includes:

• Introduction

• IntelliVue Telemetry System Infrastructure Components

• General Intellivue Telemetry System Data Flow

• Supported Topologies and System Limits

• IntelliVue Telemetry System Specifications

• IntelliVue Telemetry System Infrastructure Product Numbers

IntelliVue Telemetry System Infrastructure Installation and Service Guide 1 1

MOSE225

Chapter 1: Overview

Introduction

The Philips IntelliVue Telemetry System (ITS) uses a cellular wireless architecture to provide two-way communications between patient-worn transceivers and wireless bedside patient monitors, and the IntelliVue Information Center.

Using the “Smart-hopping” wireless protocol, the ITS provides monitoring capabilities for ambulatory patients within a wide coverage area. The ITS transceivers (portable patient-worn devices), patient-worn monitors, wireless bedside monitors, and infrastructure operate on the 1.4 GHz US Wireless Medical

Telemetry Service (WMTS) band or on the 2.4 GHz Industrial Scientific and Medical

(ISM) band.

The pocket-size patient-worn transceiver or monitor sends patient data, and sends and receives control and device information to and from the IntelliVue Information

Center (bi-directional communication) for subsequent monitoring, display, analysis, alarm detection, operator alerts, data storage and permanent recording. Displays, settings, recordings, and alarms are controlled from the IntelliVue Information

Center. Recordings can also be initiated from the patient worn-transceivers/ monitors.

Access Point Controller

ICN Network Switch

Access Point Controller

Power over Ethernet Unit

Synchronization Unit

1.4 GHz Smart-hopping

Access Points

1.4 GHz

Core Access Point

1.4 GHz

Remote Antenna

1.4 GHz

Core Access Point

1.4 GHz Patient-worn

Transceivers

1.4 GHz Wireless

Bedside Monitors

1.4 GHz Patient-worn

Monitors

Figure 1-1: 1.4 GHz IntelliVue Telemetry System

1-2

MOSE225

IntelliVue Telemetry System Infrastructure Components

You can configure the Access Point Controller to communicate with IntelliVue 1.4 or

2.4 GHz Smart-hopping Access Points (APs). IntelliVue 1.4 GHz APs can only communicate with 1.4 GHz transceivers and monitors. Likewise, 2.4 GHz APs can only communicate with 2.4 GHz transceivers and monitors. You cannot mix 1.4 GHz and 2.4 GHz transceivers or monitors at a given ITS installation site.

Philips Smart-hopping technology utilizes a cognitive radio that senses the RF environment and adapts to it. Dynamic wireless channel allocation ensures best use of available wireless spectrum. When configured to operate in the 2.4 GHz spectrum, the ITS is designed to co-exist with other 802.11 wireless deployments.

IntelliVue Telemetry System Infrastructure Components

The ITS infrastructure consists of an Ethernet LAN that can include LAN switches and routers, and is used to interconnect multiple IntelliVue Access Points to one or more Philips Access Point Controllers (APC).

The key function of the ITS infrastructure is to transport data from the transceivers and wireless bedside monitors over a wireless LAN-based infrastructure (part of the

IntelliVue Clinical Network) to/from the IntelliVue Information Center where the data can be recorded or used to alert clinical operators as to a change in monitored parameters.

Five major components comprise the Philips IntelliVue Telemetry System infrastructure:

• 1.4 GHz or 2.4 GHz IntelliVue Telemetry System Smart-hopping Access Points

• Access Point Controller

• Synchronization Unit

• Power over Ethernet Unit

• Uninterruptible Power Supply

1.4 GHz ITS

Core Access

Points

ITS Smart-hopping Access Points

The IntelliVue Telemetry System supports two types of Smart-hopping Access

Points:

• Model ITS4843B (P/N 989803171211) Core AP for 1.4 GHz ITS

• Model ITS4852A (P/N 989803171221) AP for 2.4 GHz ITS

The IntelliVue Telemetry System Core Smart-hopping Access Point (AP), Model

ITS4843B (P/N 989803171211), (Figure 1-2) provides an air-link to transmit and

receive data between ITS wireless clients and the Philips IntelliVue Information

Center via the ITS infrastructure.

The Core AP is a modular antenna infrastructure consisting of a Core AP (CAP) with up to two connected Model ITS4846A Remote Antennas (RAs). A 74-foot (22.6m) coaxial and unshielded twisted pair (UTP) cable bundle is used to connect a Remote

Antenna to a Core AP. Core APs are only available for the 1.4 GHz ITS.

The effective range of the Core AP and of each Remote Antenna is typically 32 feet.

The Core AP always supports a maximum of 18 wireless clients (i.e., patient-worn transceivers/monitors or bedside monitors) regardless of its component

IntelliVue Telemetry System Infrastructure Installation and Service Guide 1 3

MOSE225

Chapter 1: Overview

Core AP

Remote

Antenna

Remote

Antenna

74 ft. Coax and

UTP Cable Bundle

Figure 1-2: 1.4 GHz IntelliVue Telemetry System Core Access Point

configuration. A Core AP alone supports 18 wireless clients. When used with a single RA, the Core AP supports nine wireless clients and its connected RA supports nine wireless clients (9+9=18). When used with two RAs, the Core AP supports six wireless clients and its connected RAs each support six wireless clients

(6+6+6=18).

When monitored patients are ambulatory, data roaming is handled seamlessly between the other IntelliVue Access Points in the system. The Core AP and each RA are always used with their two supplied antennas installed. The Core AP and its attached Remote Antennas can be mounted out of the way on corridor walls, or above or below ceiling tiles.

Philips provides ITS Core Access Points for the 1.4 GHz US Wireless Medical

Telemetry Service (WMTS) band (P/N 862228). Remote Antennas are available separately (P/N 865052).

1.4 GHz ITS Core AP Connectors

Figure 1-3 shows the controls and connectors on the 1.4 GHz ITS Core AP and

Remote Antenna.

Note the following connectors on the ITS Core AP:

• Ethernet Interface - The AP provides a 100 Base-T Ethernet interface with an

RJ-45 connector to connect the Core AP to the ITS Sync Unit.

The AP Ethernet interface provides data communications to and from the

IntelliVue Information Center over the ITS LAN infrastructure. It also presents the 48Vdc power and synchronization signals required by the Core AP. The synchronization signal is superimposed on the power supply voltage. You should attach a ferrite block to the CAT 5 cabling (from the Sync Unit) no more than 20 inches (50 cm) from the RJ-45 connector to reduce electromagnetic (radiation)

interference. Table 1-1 lists the pin signals for the AP Ethernet interface.

1-4

MOSE225

IntelliVue Telemetry System Infrastructure Components

Link LED Activity LED ITS Core Access Point

RA 2

Ethernet Interface to

ITS Sync Unit

Connection LED

(Green)

Power/Sync, Radio, and Network

Serial Port

Status LEDs

ITS Remote Antenna

RA 1

Coaxial Cable Connectors to Remote Antennas (2 & 1)

RA 2 RA 1

UTP Cable Connectors to Remote Antennas (2 & 1) with RA Status LEDs

Power LED

(Yellow)

UTP Cable Connector to ITS Core AP

Coaxial Cable Connector to ITS Core Access Point

Figure 1-3: 1.4 GHz ITS Core AP and Remote Antenna Controls and Connectors

Table 1-1: Core AP Ethernet Interface Pin Signals

Pin

1

2

3

4

5

6

7

8

Signal Description

Transmit Pair TX + Conductor

Transmit Pair TX - Conductor

Receive Pair RX + Conductor

+ 48Vdc Power and Synchronization

+ 48Vdc Power and Synchronization

Receive Pair RX - Conductor

0V Power Return

0V Power Return

• Serial Port - The serial port is used only for manufacturing purposes.

• UTP Cable Connectors to Remote Antennas - Two standard RJ-45 connectors are provided for the UTP cables that connect the Core AP to its Remote

Antennas. Each UTP cable carries 5.5 VDC power, Transmit, Receive, and

Antenna Diversity Control signals to the Remote Antenna.

• Coaxial Cable Connectors to Remote Antennas - Two standard 75 Ohm connectors are provided for the coaxial cables that connect the Core AP to its

Remote Antennas. Each coaxial cable carries RF and DC sense signals from the

Remote Antenna.

IntelliVue Telemetry System Infrastructure Installation and Service Guide 1 5

MOSE225

Chapter 1: Overview

Note the following connectors on the Remote Antenna:

• UTP Cable Connector to Core AP - A standard RJ-45 connector is provided for the

UTP cable that connect the Remote Antenna to its Core AP. The UTP cable carries 5.5 VDC power, Transmit, Receive, and Antenna Diversity Control signals from the Core AP.

• Coaxial Cable Connector to Core AP - A standard 75 Ohm connector is provided for the coaxial cable that connects the Remote Antenna to its Core AP. The coaxial cable carries RF and DC sense signals from the Core AP.

Note If an installed, powered Remote Antenna becomes disconnected from its Core AP via its Coax/UTP cable bundle, you must reconnect the Coax/UTP cable bundle to the RA and Core AP, and then cycle power to the connected Core AP before the RA will re-establish communications with the Core AP.

1.4 GHz ITS Core AP Status LEDs

The ITS Core AP provides the following status LEDs.

• Wired/Ethernet Activity - The Core AP provides two LEDs to indicate wired/

Ethernet activity to the ITS infrastructure. During normal operation, these LEDs indicate the following information:

- Link LED - Link present/Ethernet connection. Lights GREEN (ON) when a pass-through link is present - OFF when not present.

- Act LED - Wired network activity. Flashes YELLOW (ON) when there is activity is over the wired network.

• Wireless/RF Activity - The Core AP provides three LEDs to indicate wireless/RF activity. During normal operation, these LEDs indicate the following information:

- Power/Sync LED - GREEN (ON) when power and synchronization signal is present.

- Radio LED - Normally OFF (not lit) - flashes green to indicate wireless network activity.

- Network LED - Normally OFF (not lit) - flashes green to indicate wired network activity.

At initial power on the AP runs a Power On Self-Test (POST). During the POST, the above LEDs indicators flicker and then all three will illuminate continuously

(AMBER) to indicate correct startup operation. Then, the Power ON LED will illuminate (GREEN) continuously to indicate that the 48Vdc power and sync signal are being supplied, and the other two (AMBER) LEDs turn off (not lit).

• Remote Antenna - The Core AP provides two LEDs on each RJ-45 UTP cable connector that provides status on a connected Remote Antenna:

- RA Connection - Lights GREEN to indicate a RA is connected to the Core AP.

- RA Power - Lights YELLOW to indicate connected RA is receiving power from the Core AP.

1-6

MOSE225

IntelliVue Telemetry System Infrastructure Components

The Remote Antenna provides the following status LEDs.

• Remote Antenna Status LEDs - The green and yellow LEDs above the

RJ-45 UTP cable connector to the Core AP provide status on the Remote

Antenna as summarized below.

Table 1-2: Remote Antenna Status LEDs

Green/Yellow LEDs

Off/Off

Flash Green/Yellow

Solid Green/Yellow

Remote Antenna Status

No connection to or power from Core AP/Self-test Failed.

Remote Antenna is running self-test/Power on.

Connection to Core AP is Successful/Power On.

This is the expected normal operational status.

2.4 GHz ITS

Access Points

1.4 GHz ITS Core AP Mounting Options

Wall-mounting hardware is standard. An optional above/below ceiling mount kit is available.

The IntelliVue Telemetry System Smart-hopping Access Point (AP), Model ITS4852A

(P/N 989803171221) (Figure 1-4), provides an air-link to transmit and receive data between ITS 2.4 GHz wireless clients and the Philips IntelliVue Information Center via the ITS infrastructure.

Figure 1-4: 2.4 GHz IntelliVue Telemetry System Access Point

The ITS 2.4 GHz AP is housed in a ventilated metal case (approximate size:

9.6” (24.3 cm) L x 8.0” (20.4 cm) W x 1.2” (3.0 cm) H) and includes dual-diversity antennas and printed circuit (PC) boards. The AP is equipped with a bi-directional cellular transceiver (radio module PC board) that receives and sends data to the wireless clients (2.4 GHz patient-worn transceivers/monitors and wireless bedsides) via a switched diversity arrangement using two antennas, and a main PC board containing the software and electronics to process this data.

A 100 Base-T Ethernet RJ-45 connector, three System Status LEDs, and two

Network LAN Activity LEDs are attached to the AP main PC board and are accessible from outside the AP case. The AP main PC board includes a radio module, and power and control circuits. Each Access Point supports up to 18 wireless clients and has a 32 ft. (9.8 m) Radius-of-Coverage (RoC).

IntelliVue Telemetry System Infrastructure Installation and Service Guide 1 7

MOSE225

Chapter 1: Overview

The data transport mechanism between the patient-worn transceivers and the

IntelliVue Access Points is a cellular wireless connection using a modified version of the Digital Enhanced Cordless Telecommunications (DECT) system. The data transport mechanism between the Access Points and the IntelliVue Information

Center is via standard 100 Base-T Ethernet LAN infrastructure to the IntelliVue

Information Center.

2.4 GHz ITS Enhanced AP Connectors

Figure 1-3 shows the connectors and status indicators on the ITS 2.4 GHz AP.

Link LED Activity LED

ITS 2.4 GHz Access Point

Ethernet Interface to

ITS Sync Unit

Power/Sync, Radio, and Network

Status LEDs

Serial Port

Figure 1-5: 2.4 GHz ITS 2.4 GHz AP Connectors and Status Indicators

Note the following connectors on the ITS 2.4 GHz AP:

• Ethernet Interface - The AP provides a 100 Base-T Ethernet interface with an

RJ-45 connector to connect the 2.4 GHz AP to the ITS Sync Unit.

The AP Ethernet interface provides data communications to and from the

IntelliVue Information Center over the ITS LAN infrastructure. It also presents the 48Vdc power and synchronization signals required by the 2.4 GHz AP. The synchronization signal is superimposed on the power supply voltage. You should attach a ferrite block to the CAT 5 cabling (from the Sync Unit) no more than 20 inches (50 cm) from the RJ-45 connector to reduce electromagnetic (radiation) interference. Table 1-3 lists the pin signals for the AP Ethernet interface.

Table 1-3: AP Ethernet Interface Pin Signals

Pin Signal Description

7

8

5

6

3

4

1

2

Transmit Pair TX + Conductor

Transmit Pair TX - Conductor

Receive Pair RX + Conductor

+ 48Vdc Power and Synchronization

+ 48Vdc Power and Synchronization

Receive Pair RX - Conductor

0V Power Return

0V Power Return

• Serial Port - The serial port is used only for manufacturing purposes.

1-8

MOSE225

IntelliVue Telemetry System Infrastructure Components

ITS 2.4 GHz Enhanced AP Status LEDs

The ITS 2.4 GHz Enhanced AP provides the following status LEDs.

• Wired/Ethernet Activity - The 2.4 GHz AP provides two LEDs to indicate wired/

Ethernet activity to the ITS infrastructure. During normal operation, these LEDs indicate the following information:

- Link LED - Link present/Ethernet connection. Lights GREEN (ON) when a pass-through link is present - OFF when not present.

- Activity LED - Wired network activity. Flashes YELLOW (ON) when there is activity is over the wired network.

• Wireless/RF Activity - The 2.4 GHz AP provides three LEDs to indicate wireless/

RF activity. During normal operation, these LEDs indicate the following information:

- Power/Sync LED - GREEN (ON) when power and synchronization signal is present.

- Radio LED - Normally OFF (not lit) - flashes green to indicate wireless network activity.

- Network LED - Normally OFF (not lit) - flashes green to indicate wired network activity.

At initial power on the AP runs a Power On Self-Test (POST). During the POST, the above LEDs indicators flicker and then all three will illuminate continuously

(AMBER) to indicate correct startup operation. Then, the Power ON LED will illuminate (GREEN) continuously to indicate that the 48Vdc power and sync signal are being supplied, and the other two (AMBER) LEDs turn off (not lit).

Access Point Controller

The Philips Access Point Controller (APC) centralizes the management and security features of the wireless LAN on which the ITS operates. Used with the Philips

IntelliVue Clinical Network, the APC provides a gateway between the ITS Access

Points (APs) and the Philips IntelliVue Information Center.

The ITS APC is compatible with and can be used to configure 1.4 GHz or 2.4 GHz ITS

APs supplied by Philips. Depending upon the number of APs installed on your ITS network, between one and nine APCs will be installed on the ITS network to support the data throughput from the connected ITS APs.

Figure 1-6 illustrates the APC ports and status indicators.

Serial Port

LAN Port

Network Utilization LEDs Master/Slave LED

Figure 1-6: APC Ports and Status Indicators

IntelliVue Telemetry System Infrastructure Installation and Service Guide 1 9

MOSE225

Chapter 1: Overview

Network Utilization LEDs

These LEDs indicate as a percentage the relative amount of network traffic that is occurring between the ITS APC and the ITS Access Points. When the LED on the far left is ON but the rest are OFF, the network utilization is low, less than 33%. As the amount of traffic increases, more LEDs will turn ON to indicate an increase in the percentage of network utilization. When all three LEDs are ON, the network utilization is greater than 90% of the Access Point Controller’s total throughput capacity. The utilization value is updated ten times per second.

The LEDs also indicate the peak utilization for the previous three seconds by illuminating the LED that corresponds to that peak utilization over that period. For example, if all three LEDs turn ON momentarily and then the first two LEDs turn OFF while the third LED remains ON, the third LED is ON to indicate that peak utilization reached 90% within the last three seconds.

Serial Port

The serial port is equipped with a standard 9-pin D-style connector that enables you to establish an RS-232 connection to the APC command line interface (CLI). Use the

APC CLI to perform initial configuration of the APC as described on page 3-12.

Master/Slave LED

After the APC has been initially configured using its command line interface and then connected to the ITS network, the Master/Slave LED lights to indicate the following APC Master/Slave status:

• Green - The APC is functioning as the Master APC (i.e., the primary APC) on the

ITS network.

• Amber - The APC is functioning as a Slave APC (i.e., a secondary APC) on the ITS network.

• Blinking Amber - The APC has encountered an internal problem. Recycle power to the APC to attempt to clear the error. If the Master/Slave LED continues to blink amber, then you will need to replace the APC, as it is not functioning properly.

LAN Port

The LAN port is equipped with an RJ-45-style connector that enables you to connect the ITS APC to the network on which the ITS Access Points have been installed. Use standard CAT-5 (or better) Ethernet cable when connecting the APC to the ITS network.

We recommend that you configure the network switch port to which you connect the

APC to support a 100 Mbps Full-duplex connection

The APC LAN Port is equipped with standard green and yellow link status LEDs located above the RJ-45 connector.

1-10

Green Status LED

MOSE225

IntelliVue Telemetry System Infrastructure Components

Yellow Status LED

Figure 1-7: ITS APC LAN Port Link Status LEDs

Table 1-4 describes the C-Port link status LEDs shown in Figure 1-7.

Table 1-4: APC LAN Port Link Status LEDs

Green LED

Solid Green

Blinking Green

Blinking Green

OFF

Yellow LED

OFF

OFF

Solid Yellow

OFF

Link Status Indicated

Solid Green - Link connection established.

Blinking Green - Link connection with Link activity.

Yellow Off - 10 Mbit Full or Half Duplex connection.

Blinking Green - Link connection with Link activity.

Solid Yellow - 100 Mbit Full or Half Duplex Connection

No Hospital LAN connection detected. EC 40/80 Hub is either physically disconnected from the Hospital LAN or

Hospital LAN is turned off.

Synchronization Unit

The Philips Synchronization Unit (Sync Unit) (Figure 1-8) provides a necessary

common clock signal to synchronize all the IntelliVue Access Points in the system.

Access Points need to be synchronized so that as the patients move around the hospital they are able to maintain and hand over connections between the Access

Points seamlessly without interruption.

Master/Slave Switch

TO MASTER SU

Cable Delay Switch

FROM POWER HUB (PoE Unit)

TO SLAVE SU

1 2 3 4 5 6 7 8 9 10 11 12

FROM

HUB

AP/SU

1 2 3 4 5 6 7 8 9 10 11 12

AP/SU (to APs or slave SUs)

Power LED

TO

SLAVE SU

TO

MASTER SU CABLE DELAY

POWER EXT REF SYNC. IN

MASTER

5

SLAVE

4

3

2

6

1

7

8

EXT. 10MHz REF.

10

9

EXT REF. LED SYNC IN LED

Power Receptacle

Figure 1-8: IntelliVue Telemetry System Sync Unit

The Sync Unit can be rack mounted (recommended) or placed freestanding on a flat surface.

IntelliVue Telemetry System Infrastructure Installation and Service Guide 1 11

MOSE225

Chapter 1: Overview

Front-panel

Connectors,

Controls, and

Indicators

Rear-panel

Connectors

Each Sync Unit provides synchronization for up to 12 Access Points (AP). Maximum cable length between a Switch/PoE Unit/Sync Unit/Access Point is 100m (328ft.)

(normal LAN Ethernet rules).

The Sync Unit provides the following front-panel connectors, controls, and indicators:

• FROM POWER HUB (PoE Unit) - Top row of connectors. 1 to 12 input RJ-45 connectors, power inputs (48VDC) from the PoE unit, as well as 100Base-T

Ethernet.

• AP/SU (to APs or slave SUs) - Bottom row of connectors. 1 -12 ‘main’ output RJ-

45 sockets, to APs carrying power (48VDC) and synchronization as well as 100base-TX Ethernet. These can feed APs or slave Sync Units.

• TO SLAVE SU - Output RJ-45 port carrying synchronization signal to a slave Sync

Unit. Category 5 (or greater) UTP cable length attached between this output and the input of the upstream Sync Unit can be up to 500m.

• TO MASTER SU - Input RJ-45 socket designed to connect to the output of another Sync Unit. This can be either the ‘to slave’ or a ‘main’ output of the upstream unit

• POWER LED - Lights green when AC power is present.

• EXT REF. LED - Always off as this LED is not used currently.

• SYNC IN LED - LED should be OFF if this Sync Unit is the Master. LED is lit

GREEN if unit is a Slave.

• MASTER/SLAVE Toggle Switch - MASTER/SLAVE toggle switch (set manually) to indicate the master SU of an installation. This MASTER switch disables the alarm that would be generated by the lack of an upstream unit to provide a reference signal to this unit. Slave units should receive a reference feed from a master SU, and should be switched to the SLAVE position (operation). If the reference feed fails, these units will free-run, and will also generate a technical alarm.

• CABLE DELAY Switch - 10 Position rotary step switch compensates for cable delay - lowest delay position 1 to highest delay position 10. Each switch increment represents 50 m cable length.

• EXT 10MHz REF - Not used currently.

The Sync Unit has a single rear-panel connector, its AC power cord receptacle.

Connect the Sync Unit to an AC power source that provides 100 - 240 VAC, 1.5A max, at 50/60Hz (autoranging).

Power over Ethernet Unit

The ITS Power over Ethernet (PoE) Unit is a 6- or 12-port Power-over-Ethernet device that provides 48 VDC power to IntelliVue Access Points (and also remote Sync Units if connected) via 100-Base-TX Ethernet LAN cabling.

The ITS PoE Unit can be rack mounted (recommended) or placed free standing on a desktop.

1-12

MOSE225

IntelliVue Telemetry System Infrastructure Components

Data and Power Ports (To APs/SUs)

Data Ports (To ICN Network Switch)

Figure 1-9: IntelliVue Telemetry System 12-port Power Over Ethernet Unit

Uninterruptible Power Supply

The ITS infrastructure has several components that must be powered from an

Uninterruptible Power Supply (UPS) including the APC, the PoE Unit, the Sync Unit, and network switches and routers. The UPS supplies backup power to protect against hospital generator changeover interruptions, and short power line transients.

Figure 1-10: Uninterruptible Power Supply

The UPS can be rack mounted (recommended) or placed free standing on a desktop.

Refer Table 1-5 to when connecting ITS infrastructure devices to the UPS to ensure that you do not exceed the UPS’ backup power capacity.

Table 1-5: ITS Infrastructure Device Power Draws

Product Number

862114

862152

862149

862161

862162

453564054671

453564054681

862084

862084

862163

862164

862247

Device

Sync Unit

POE – 12 Port

POE – 6 Port

Cisco 2950 Switch: Copper

Cisco 2950 Switch: Fiber

Cisco 2960 Switch: Copper

Cisco 2960 Switch: Fiber

HP 2524 Switch

HP 2510 Switch

Cisco 3550 Router: Copper

Cisco 3550 Router: Fiber

Cisco 3560-24TS Router: Copper

Power in Watts

10 Watts

165 Watts

90 Watts

30 Watts

30 Watts

30 Watts

30 Watts

36 Watts

20 Watts

65 Watts

85 Watts

45 Watts

IntelliVue Telemetry System Infrastructure Installation and Service Guide 1 13

MOSE225

Chapter 1: Overview

Table 1-5: ITS Infrastructure Device Power Draws

Product Number

862248

865346 or 862147

Device

Cisco 3750-24FS Router: Fiber

APC

Power in Watts

70 Watts

10 Watts

General Intellivue Telemetry System Data Flow

Data sent from the ITS transceiver to the IntelliVue Information Center traverses the network as follows:

1. The ITS transceiver/monitor sends its ECG data over the wireless link to an ITS

Access Point.

2. The AP then “wraps” the ECG data into another message packet, with its destination as the Access Point Controller that is assigned to handle the management activities for that AP.

3. The wired network then treats the packet like a message to the APC.

4. The APC receives the packet, “unwraps” it and determines that the message is for the IntelliVue Information Center.

5. The APC repackages the message and forwards it on with a destination address of the IntelliVue Information Center.

Data sent from the IntelliVue Information Center to an ITS transceiver/monitor traverses the network as follows:

1. The Information Center sends a message to the ITS transceiver/monitor’s IP address. The network “sees” the location of the transceiver/monitor’s IP address as the location of the APC, and sends the message there.

2. The APC then looks at the message, determines which ITS Access Point is currently connected to the transceiver/monitor it needs to send the message to,

“wraps” the message into a packet and forwards the packet on to the appropriate ITS Access Point.

3. The network handles the packet as a message for the ITS Access Point.

4. When the packet arrives at the ITS Access Point, the Access Point “unwraps” the message, determines which transceiver/monitor the message is intended for, and sends the message on to the transceiver over the wireless link.

Defined ITS Bandwidth

The ITS transceivers (portable patient-worn devices), wireless bedside monitors, and infrastructure operate on the 1.4 GHz US Wireless Medical Telemetry Service

(WMTS) band or on the 2.4 GHz band.

1.4 GHz ITS Bandwidth

In the United States, Federal Communications Commission (FCC) has established the Wireless Medical Telemetry Service (WMTS) to promote interference-free operation of medical telemetry systems. The FCC has reserved the following bands of frequencies for use by medical telemetry devices: 608 - 614 MHz, 1395 - 1400

MHz, and 1427 - 1432 MHz.

1-14

MOSE225

Defined ITS Bandwidth

Standard WMTS

Channels

The Philips IntelliVue Telemetry System can operate in the radio bands of 1395 –

1400 MHz and 1427 – 1432 MHz.

Generally, WMTS operations are accorded primary status over non-medical telemetry operations in 1395-1400 MHz and 1427-1429.5 MHz bands, but are treated as secondary to non-medical telemetry operations in the 1429.5-1432 MHz band.

Table 1-6 lists the standard primary and secondary 1.4GHz WMTS frequencies.

Table 1-6: Standard WMTS Frequencies

WMTS Channel Frequencies in the Band 1395 to 1400MHz

Channel 1

Channel 2

Channel 3

1395.9MHz

1397.5MHz

1399.1MHz

Primary WMTS Channel

Primary WMTS Channel

Primary WMTS Channel

WMTS Channel Frequencies in the Band 1427 to 1432MHz

Channel 4

Channel 5

Channel 6

1427.9MHz

1429.5MHz

1431.1MHz

Primary WMTS Channel

Secondary Channel, available only if not in use

Secondary Channel, available only if not in use

Carved-out

Regions

The FCC has carved the following metropolitan regions out of the standard WMTS spectrum to protect operation of critical RF devices (e.g., radar, military and government communications, etc.):

• Pittsburgh, PA

• Metro Washington D.C.

• Richmond/Norfolk, VA

• Austin/Georgetown, TX

• Battle Creek, MI

• Detroit, MI

• Spokane, WA

In these seven areas, in contrast to the rest of the US, the FCC has specified that for

WMTS and non-medical telemetry devices operating in the 1427 - 1432 MHz range the band be “flipped” as to which device type enjoys primary status.

Figure 1-11 illustrates the use of the 1427 - 1432 MHz band for the US and the

designated carved out regions.

IntelliVue Telemetry System Infrastructure Installation and Service Guide 1 15

Chapter 1: Overview

MOSE225

1-16

Figure 1-11: Designated Use of WMTS Frequencies in the 1427 - 1432 MHz Band

Table 1-7 lists the 1.4GHz WMTS channels available for use in “carved-out” regions.

Table 1-7: WMTS Frequencies in “Carved Out” Regions

WMTS Channel Frequencies in the Band 1395 to 1400MHz

Channel 1

Channel 2

Channel 3

1395.9MHz

1397.5MHz

1399.1MHz

Primary WMTS Channel

Primary WMTS Channel

Primary WMTS Channel

WMTS Channel Frequencies in the Band 1427 to 1432MHz

Channel 4

*

1427.9MHz

Secondary Channel, only available if not in use

Channel 4a 1430.24MHz

Primary WMTS Channel

* - Channel 4 is not available when special “Carved-out” geographic area is selected as part of the APC configuration.

MOSE225

Defined ITS Bandwidth

Required FCC

Registration

The FCC (Section 95.1111 of the FCC Rules) requires that all WMTS transmitters be registered with the American Society for Healthcare Engineering (ASHE). If a hospital doesn’t register, not only is it subject to being interfered with, but the FCC can also shut down its telemetry system.

Hospitals using the IntelliVue telemetry System must register all 1.4 GHz patientworn transceivers, wireless bedside monitors, and Access Points and Remote

Antennas.

Site registration with the frequency coordinator, American Society for Healthcare

Engineering (ASHE), is only required once and can be done online (www.ashe.org).

The frequencies and number of devices in use must be logged with the frequency coordinator.

2.4 GHz ITS Bandwidth

Both inside and outside the United States, the IntelliVue Telemetry System can use

RF energy in the 2.4 GHz frequency space across 48 radio channels assigned from

2401.066 MHz to 2482.272 MHz, with a channel spacing of 1.728 MHz.

Table 1-8 lists the 2.4 GHz ITS channels.

Table 1-8: 2.4 GHz ITS Channels

2.4 GHz ITS Channel

(for Advanced Selection)

11

12

13

14

9

10

7

8

15

16

5

6

3

4

0

1

2

Center Frequency

(MHz)

2401.056

2402.784

2404.512

2406.240

2407.968

2409.696

2411.424

2413.152

2414.880

2416.608

2418.336

2420.064

2421.792

2423.520

2425.248

2426.976

2428.704

IntelliVue Telemetry System Infrastructure Installation and Service Guide 1 17

Chapter 1: Overview

Table 1-8: 2.4 GHz ITS Channels

2.4 GHz ITS Channel

(for Advanced Selection)

45

46

47

41

42

43

44

37

38

39

40

33

34

35

36

29

30

31

32

25

26

27

28

21

22

23

24

17

18

19

20

Center Frequency

(MHz)

2458.080

2459.808

2461.536

2463.264

2464.992

2466.720

2468.448

2470.176

2471.904

2473.632

2475.360

2477.088

2478.816

2480.544

2482.272

2444.256

2445.984

2447.712

2449.440

2451.168

2452.896

2454.624

2456.352

2430.432

2432.160

2433.888

2435.616

2437.344

2439.072

2440.800

2442.528

MOSE225

1-18

MOSE225

Supported Topologies and System Limits

The 2.4 GHz ITS channels available at a given installation site vary by geographic

region as determined by the regulatory domain for that region. Table 1-9 lists the

available 2.4 GHz ITS channels and regulatory domain by geographic region.

Table 1-9: Available 2.4 GHz ITS Channels by Geographic Region

Country/Region

Regulatory

Rule

Europe ETSI

North America

South America

Japan

FCC, RS-210

ETSI

JAPAN, ARIB

Allowed ROW channels

1-46

0-47

1-46

1-47

Max Power EIRP from

Antenna, dBm

20 dBm

10 dBm

12.14 dBm, Max

Antenna gain is 2.14dB

20 dBm Taiwan, Singapore, Hong Kong FCC

Asia ETSI

Australia/New Zealand AUS/NZ

Africa ETSI

0-47

1-46

1-46

1-46

10 dBm

Supported Topologies and System Limits

The IntelliVue Telemetry System is installed as part of an overall Philips IntelliVue

Clinical Network installation. There are four basic IntelliVue Clinical Network topologies into which the IntelliVue Telemetry System can be installed:

• non-routed ring topology

• routed ring topology

• routed star topology

• non-routed star topology

Refer to the latest edition of

IntelliVue Clinical Network Installation Guidelines and

Topologies

(M3185-91931) for detailed information about all supported ICN topologies.

As an alternative to installing the Philips IntelliVue Telemetry System on a Philipssupplied clinical network (PSCN), you may install the Philips IntelliVue Telemetry

System on customer-supplied clinical network (CSCN) infrastructure as described in

“Deploying the ITS on a Customer-supplied Clinical Network” on page 1-30.

Installing the ITS within a Non-routed Ring Topology

In a non-routed ICN configuration, the ICN functions as an independent network with a single IntelliVue Database (DBS) Domain. Figure 1-12 represents an ITS installed in a non-routed ICN.

Note the following guidelines for installing the ITS within a non-routed ICN topology:

• All ITS wireless devices (transceivers/wireless bedside monitors) must reside on the ICN Database Domain on which the ITS infrastructure is installed.

IntelliVue Telemetry System Infrastructure Installation and Service Guide 1 19

Chapter 1: Overview

MOSE225

1-20

Figure 1-12: An ITS Installed within a Non-routed ICN Topology

• Up to 48 ITS Standard or Core Access Points may be installed on a non-routed

ICN topology.

• Multiple ITSs at a single hospital are supported only if the topology, configuration, and the Sync Network requirements listed in Appendix A are met.

Figure 1-13 illustrates supported and non-supported ITS installations within a nonrouted ICN topology.

Refer to Table 1-10 for a list of the device IP address assignments used in a non-

routed ICN configuration where the ITS infrastructure is installed on the ICN subnet.

Note the following regarding Table 1-10:

• “n” represents the network number and starts at 0 for single Database Domain

ICN systems. This variable increments by 8 from there for additional ICN

Database Domains. For example, for DBSD 2, “n” would equal 8, for DBSD 3,

“n” would equal 16, and so on.

MOSE225

Supported Topologies and System Limits

Supported:

(Multiple ITSs at a single location are supported only if the Topology,

Configuration, and Sync

Network requirements listed in Appendix A are met.)

Not Supported:

Figure 1-13: Supported and Non-Supported ITS Non-routed ICN Installations

IntelliVue Telemetry System Infrastructure Installation and Service Guide 1 21

Chapter 1: Overview

MOSE225

Table 1-10: IP Address Assignments for Non-routed ICN Subnet

Device Types

(with Non-routed Subnet)

Network Subnet Address

Reserved for Routed Solution

Reserved for Service PC

Network Switches and Remote

Client Infrastructure (i.e.,

Remote Client Router)

Reserved for Future Use

1.4/2.4 Ghz ITS APCs

IP Addresses

Subnet Mask:

255.255.248.0

172.31.n.0

172.31.n.1 - 3

172.31.n.4 - 9

172.31.n.10 - 102

172.31.n.103 - 255

172.31.(n+1).0 - 63

Default

Gateway

Left Blank (0.0.0.0)

IP Address of DBS or

M3150 Information Center

IP Address of DBS or

M3150 Information Center

IP Address of DBS or

M3150 Information Center

Reserved

Reserved

1.4GHz AP Static Range

172.31.(n+1).64 - 127

172.31.(n+1).128 - 255

172.31.(n+2).0 - 127

Bootp/DHCP Server Range 2 for

ITS APs (configured in APC)

Database server (NIC 1)

Application Server (NIC 1)

172.31.(n+2).128 - 255

172.31.(n+3).0

172.31.(n+3).16 - 31

IP Address of DBS or

M3150 Information Center

IP Address of DBS or

M3150 Information Center

Information Centers (NIC 1)

Information Center Clients

Printers (Set by BootP in DBS)

172.31.(n+3).32 - 63

172.31.(n+3).64 - 95

172.31.(n+3). 96 - 127

IP Address of DBS or

M3150 Information Center

IP Address of DBS or

M3150 Information Center

IP Address of DBS or

M3150 Information Center

IP Address of DBS or

M3150 Information Center

Reserved 172.31.(n+3).128 - 255

Bedside Monitors/Devices

(Wired & ISM 2.4 GHz Wireless)

172.31.(n+4).0 - 255

Reserved for Future Use 172.31.(n+5).0 - 255

172.31.(n+6).0 - 255 Bootp/DHCP Server Range 1 for

1.4/2.4 GHz ITS Transceivers/

Bedsides (config in APC)

Reserved for Future Use

Network broadcast address

172.31.(n+7).0 - 254

172.31.(n+7).255

IP Address of DBS or

M3150 Information Center

IP Address of DBS or

M3150 Information Center

1-22

MOSE225

Supported Topologies and System Limits

Installing the ITS on a Routed Ring Topology

In a routed ring configuration, the ITS infrastructure is installed as a separate subnet to which multiple ICN Database Domains have access via routers.

Figure 1-14 represents an ITS installed within a routed ring topology.

Figure 1-14: An ITS Installed within a Routed ICN Topology

IntelliVue Telemetry System Infrastructure Installation and Service Guide 1 23

MOSE225

Chapter 1: Overview

Note the following guidelines for installing the ITS within a routed ring topology:

• An ITS subnet can be connected up to 22 ICN Database Domains via routers.

• Up to 320 ITS Standard Access Points may be installed on a routed ICN topology.

• Up to 320 ITS Core Access Points and up to 640 Remote Antennas (i.e., two per

Core AP) may be installed on a routed ICN topology.

• ITS Standard and Core APs may exist together on a routed ICN topology so long as the maximum number of APs does not exceed 320.

• You may install the 1.4 GHz ITS or 2.4 GHz ITS within a routed ICN topology.

Refer to Table 1-11 for a list of the device IP address assignments used in a routed

ICN configuration where the ITS infrastructure is installed as a separate subnet to which up to 22 Database Domains have access via routers.

Note the following regarding Table 1-11:

• “n” represents the network number and starts at 0 for single ICN systems (i.e.,

Database Domains). This variable increments by 8 from there for additional

IntelliVue Clinical Networks. For example, for DBSD 2, “n” would equal 8, for

DBSD 3, “n” would equal 16, and so on.

• Route statements are generated (in instances with a Router) at the completion of the Config Wizard.

1-24

MOSE225

Table 1-11: Routed Ring DBSD Subnet and ITS Wireless Subnet Device IP Addresses

Device Types

(with Routed Subnet)

ICN DBSD Subnet IPs

Mask: 255.255.248.0

Network Subnet Address (Used in Config Wizard for Router)

Gateway Address

Router A – <used for ITS Wireless Subnet Router>

Router B – <used for ITS Wireless Subnet Router>

Reserved for Service PC

Network Switches and Remote Client Infrastructure

Reserved for Future Use

ITS APCs

IntelliVue 802.11 Devices

IntelliVue 802.11 Devices and legacy Proxim (RangeLAN2/Harmony) APs.

Note: Proxim devices are not supported on IIC Release J (or higher).

172.31.n.0

172.31.n.1

172.31.n.2

172.31.n.3

172.31.n.4 - 9

172.31.n.10 - 102

172.31.n.103 - 255

172.31.(n+1).0 - 63

172.31.(n+1).64 - 127

Reserved for Future Use

ITS AP Static Range (1.4/2.4 GHz)

172.31.(n+1).128 - 255

ITS APC Bootp/DHCP Server Range 2 for 1.4/2.4 GHz APs

Database Server (NIC 1)

Application Server (NIC 1)

Information Centers (NIC 1)

Information Center Clients

Printers (Set by BootP)

172.31.(n+3).0 - 15

172.31.(n+3).16 - 31

172.31.(n+3).32 - 63

172.31.(n+3).64 - 95

172.31.(n+3). 96 - 127

Reserved 172.31.(n+3).128 - 255

Bedside Monitors/Devices (Wired & ISM 2.4GHz) (Set By BootP)

Reserved for Future Use

ITS APC Bootp/DHCP Server Range 1 for Transceivers/Bedsides

Reserved for Future Use

Network Broadcast Address

172.31.(n+4).0 - 255

172.31.(n+5).0 - 255

172.31.(n+7).0 - 254

172.31.(n+7).255

DBSD Default

Gateway

172.31.n.1

172.31.n.1

172.31.n.1

172.31.n.1

Default blank

172.31.n.1

172.31.n.1

172.31.n.1

ITS Wireless Subnet IPs

Mask: 255.255.240.0

172.31.240.0

172.31.240.1

172.31.240.2

172.31.240.3

172.31.240.4-9

172.31.240.10 – 20

172.31.240.21 – 172.31.240. 255

172.31.241.0 – 127

172.31.241.128 - 255

172.31.242.0 – 172.31.244.127

172.31.244.128 - 172.31.246.255

172.31.247.0 - 255

172.31.248.0 – 172.31.253.255

172.31.254.0 – 172.31.255.254

172.31.255.255

ITS Default

Gateway

172.31.240.1

172.31.240.1

172.31.240.1

172.31.240.1

172.31.240.1

172.31.240.1

172.31.240.1

172.31.240.1

MOSE225

Chapter 1: Overview

Routed Star Network Topologies

In the simplest form of the routed star topology, the Access Switches are directly connected to the Routers, which act as both Core Switch and Router. Because the currently used Core Switches have only 24 ports, this star topology design is limited to a total of 24 Access switches. The total number of end devices (both DBSD and

ITS) that can be connected to this network is 576.

Figure 1-15 shows an example of a star network topology where the Access

Switches are directly connected to the Routers/Core Switches.

Router A

Core 1

Router B

Core 2

DBSD/ITS

Network

Access 1 Access 2 Access 3 Access 4 Access 24

Figure 1-15: Simple Star Topology with Directly Connected Access Switches

To support a greater number of Access Switches and end devices, you may use a second type of routed star network topology in which Access Switches are not directly connected to the Routers/Core Switches but are instead connected to

Distribution Switches. The Distribution Switches, which must be used in pairs, are directly connected to the Routers/Core Switches in the topology.

Figure 1-16 shows a star topology that uses a distribution layer with a single pair of

Distribution Switches.

Router A

Core 1

Router B

Core 2

DBSD/ITS

Network

Distribution 1A

Access 1 Access 2 Access 3

Distribution 1B

Access 4 Access 6

Figure 1-16: Star Topology with Distribution Layer

Up to 24 Distribution Switch pairs may be used per network. With six Access

Switches allowed per Distribution Switch pair, a maximum Distribution Switch deployment would allow 144 Access Switches to be connected to the network. Each

Distribution Switch may also use 18 ports for end devices, bringing the total number of end devices that can be connected to a Star Topology with a fully populated

Distribution Layer to 4320.

1-26

MOSE225

Supported Topologies and System Limits

Figure 1-17 represents a routed star network topology with a maximum Distribution

Switch build out. Note that for the sake of brevity, the figure does not show all

Distribution or Access Switches.

Router A

Core 1

Router B

Core 2

Distribution

1A

DBSD/ITS

Network

Distribution

1B

Distribution

2A

Distribution

2B

Distribution

24A

Distribution

24B

Access

1

Access

2

Access

3

Access

6

Access

139

Access

140

Access

141

Access

142

Access

144

Figure 1-17: Star Topology with Maximized Distribution Layer

You may also create a hybrid routed star topology design which uses some Access

Switches that are directly connected to a Router/Core Switch and other Access

Switches that are connected to a Distribution Switch pair. Such a hybrid star topology is represented in Figure 1-18.

Router A

Core 1

Router B

Core 2

Distribution

1A

DBSD/ITS

Network

Distribution

1B

Access

1

Access

2

Access

3

Access

6

Access

7

Access

8

Access

9

Access n

Figure 1-18: Access Switches Connected to Routers and Distribution Switches

You should factor in the total number of end devices that must be supported and the location of these devices within the installation site when deciding which star topology to use.

IntelliVue Telemetry System Infrastructure Installation and Service Guide 1 27

MOSE225

Chapter 1: Overview

Non-routed Star Topologies

Though most star network installations will use routers, a non-routed star network topology is supported. In the non-routed star topology, a single pair of Distribution

Switches is used to connect up to six Access Switches as shown in Figure 1-19.

Distribution 1A Distribution 1B

DBSD/ITS

Network

Access 1 Access 2 Access 3 Access 4

Figure 1-19: Non-routed Star Topology

Access 6

The non-routed star network topology supports connection of up to 180 end devices

(both DBSD and ITS). Note that the DBSD and ITS end device limits that apply to the non-routed ring topology also apply to the non-routed star topology.

Advantages of Star Topologies

By using a star topology, you may mix ITS and DBSD networks on one switch. This is done by configuring a separate VLAN for each network, as shown in Figure 1-20.

Router A Router B

Distribution 1

DBSD/ITS

Network

Distribution 2

Access 1

Access 2

Access 3

Figure 1-20: Star Topology with Distribution Layer

The links between the switches are trunks. VLAN 124 represents the ITS network,

VLAN 101 represents a DBSD, and VLAN 102 represents another DBSD.

A trunk is a point-to-point link that transmits and receives traffic between switches or between switches and routers. Trunks carry the traffic of multiple VLANs and can extend VLANs across an entire network. 100BaseT and Gigabit Ethernet trunks use

Cisco Inter-Switch Link (ISL) protocol or industry-standard IEEE 802.1Q to carry traffic for multiple VLANs over a single link.

It is important to note that there can only be one ITS subnet. It is not possible to have DBSD/ITS VLANs shared on a switch coexisting with a Ring Topology ITS network. In the case where a Ring Topology ITS network exists and a customer

1-28

MOSE225

Supported Topologies and System Limits

desires DBSD/ITS VLANs shared on a switch, the Ring Topology ITS network will need to be migrated to the star topology.

In the case of directly attached Access Layer Switches, the Router and Core layers are effectively combined into a single device (i.e., a Layer 3 Switch). This scenario is shown in Figure 1-21.

Router A

Core Switch 1

Router B

Core Switch 2

DBSD/ITS

Network

Access 1

Access 2

Figure 1-21: Star Topology without Distribution Layer

Access 3

System Limits

Note the following important ITS system limits.

Table 1-12: Maximum ITS Capacities

ITS Device

Access Point Controllers

1.4 GHz Standard Access Points

1.4 GHz Core Access Points

1.4 GHz Remote Antennas

1.4 GHz Smart-hopping Wireless Clients

(Transceivers and Wireless Bedside Monitors)

2.4 GHz Access Points

2.4 GHz Smart-hopping Wireless Clients

(Transceivers and Wireless Bedside Monitors)

Maximum Supported

9 (includes one for redundancy)

320 (routed ICN topology)

48 (non-routed ICN topology)

320 (routed ICN topology)

48 (non-routed ICN topology)

640 (routed ICN topology)

96 (non-routed ICN topology)

1024 (routed ICN topology)

128 (non-routed ICN topology)

320 (routed ICN topology)

48 (non-routed ICN topology)

1024 (routed ICN topology)

128 (non-routed ICN topology)

IntelliVue Telemetry System Infrastructure Installation and Service Guide 1 29

MOSE225

Chapter 1: Overview

Deploying the ITS on a Customer-supplied Clinical Network

If you will be deploying the Philips IntelliVue Telemetry System on customer-supplied network infrastructure, then you must follow all of the requirements and specifications listed in the latest revision of the Philips

Customer-supplied Clinical

Network Specification

document.

Additionally, you should be aware of the following requirements for assigning IP addresses to 1.4Ghz or 2.4 GHz ITS Access Points on a customer-supplied clinical network.

Caution The device location value within an ITS is based on an ITS AP IP address and is limited to ten bits in length. If an AP IP address is used whereby the 11th bit changes, unstable system behavior could occur. We recommend that you define the

ITS subnet to be 255.255.240.0 for a routed network.

IntelliVue Telemetry System Specifications

This section lists power, radio, and regulatory compliance specifications for the

IntelliVue Telemetry System.

Power Requirements

Table 1-13: ITS Component Power Requirements

Device/

Component

Standard or Core

Access Point

Input Voltage

Manual

Switching

Required?

No

Input

Frequency

(Hz)

DC

Dissipated

Power

(Max)

< 13.8W

SYNC Unit

POE with 1 AP

POE with 12 AP

Access Point

Controller

48 VDC Nominal

(44 - 52) VDC

287 mA

88-264 VAC

88-264 VAC

88-264 VAC

88-264 VAC

No

No

No

No

47-63

47-63

47-63

47-63

< 10W/18VA

< 20W/50VA

< 165W

< 10W/40VA

1-30

MOSE225

IntelliVue Telemetry System Specifications

Table 1-14: UPS Specifications

UPS

Requirements

Input Voltage

Parameter Specification

1.4 GHz ITS

120VAC +/-10%

60Hz +/-3Hz minimum

2.4 GHz ITS

100, 120, 127, 220, 240 VAC ± 10%

50, 60Hz +/-3Hz Input

Frequency

UPS AC

Input Port

100, 120VAC model: one NEMA 5-15P plug.

Number of UPS

AC output ports

Power delivery

Power Fail

Transition

Power Fail Alert

EMI Filtering

EMC

Safety

Mounting

230 VAC model: one IEC 320 C14 plug.

100, 120VAC model: 3 minimum (NEMA 5-15R output receptacles), desirable to have 5 ports or greater.

230V model: 3 minimum (IEC 320 C13 output receptacles), desirable to have 5 ports or greater.

UPS shall provide at least 225Watts for > 90 seconds to power

12 APs, 1 Sync Unit, 2 APC, 1 POE, & 1 Switch from one UPS unit with 5

UPS ports.

Or:

12 APs, 1 Sync Unit, 1 APC, 1 POE, from one UPS unit with 3 UPS ports.

Additional UPS would be needed to power redundant APC & Switch.

UPS must be responsive to power fail conditions such that ITS system does not experience reboot due to transition to temporary battery backup power.

UPS shall provide local auditory response to power fail conditions.

Provide AC line EMI filtering over 100KHz to 30MHz on UPS ports.

FCC part 15 class A or B certification, CE Mark: CISPR 22/ EN 55022, and CISPR 24 / EN 55024.

UL certification, EN 62040 (Low Voltage Directive).

Rack Mounting is desirable.

IntelliVue Telemetry System Infrastructure Installation and Service Guide 1 31

MOSE225

Chapter 1: Overview

Safety Regulatory Compliance

Table 1-15: ITS Infrastructure Safety Standard Compliance

Safety Specification

Information Technology Equipment - Safety

UL 60950-1

Fire Safety

Standard for Uninterruptible Power Supply

Equipment

UL 1778

Compliant ITS Device/Component

1.4 GHz Access Points, 2.4 GHz Access

Points, APC, and Sync Unit, PoE Unit,

Switches, Routers, UPS.

Model ITS4843B 1.4 GHz Core Access

Points, Model ITS4846A 1.4 GHz Remote

Antennas, and Model ITS4852A 2.4 Access

Points, are Listed for use within “Other

Spaces Used for Environmental Air

(Plenum)” per NFPA70: 2011, Article

300.22.

Note: The term “plenum” as used in Article

300.22 Section C correlates with the use of the term “plenum” in NFPA 90A-2009,

Standard for the Installation of Air-

Conditioning and Ventilating Systems, and other mechanical codes where the plenum is used for return air purposes, as well as some other air-handling spaces. The area above dropped ceilings is an example of plenum space.

UPS.

Environmental Specifications

For EMC purposes component parts of the system conform to the requirements of

EN60601-1-2.

In general, the ITS is designed for use in an indoor environment and operates over an ambient temperature range of 0

°

to 55

°

C, excluding the patient-worn transceiver.

The Access Point, Sync Unit, APC, and Power over Ethernet Unit, and switches are all classified as ITE devices.

1-32

MOSE225

IntelliVue Telemetry System Specifications

Table 1-16: ITS Environmental Specifications

Environmental Test for ITS

Operating Temperature

Test Type & Limits

0

°

to 55

°

C

Operating Humidity

Storage Temperature

Storage Humidity

Altitude (Operating and

Non-operating)

< 95% RH at 40 non-condensing

-40

°

C to 60

°

C

< 90% RH at 60

°

C (104

°

F)/

°

C

3,048 meters (10,000 ft)

Applicable System

Element

Standard and Core

APs, Remote

Antennas, Sync

Unit, APC

Standard and Core

APs, Remote

Antennas, Sync

Unit, APC

Standard and Core

APs, Remote

Antennas, Sync

Unit, APC

Standard and Core

APs, Remote

Antennas, Sync

Unit, APC

Standard and Core

APs, Remote

Antennas, Sync

Unit, APC

IntelliVue Telemetry System Infrastructure Installation and Service Guide 1 33

MOSE225

Chapter 1: Overview

IntelliVue Telemetry System Infrastructure Product Numbers

Table 1-17 lists key product numbers associated with the IntelliVue Telemetry

System infrastructure.

Table 1-17: ITS Infrastructure Product Numbers

Device/Option

Model ITS3171A Access Point Controller

ITS Synchronization Unit

6-port Power over Ethernet Unit

12-port Power over Ethernet Unit

Model ITS4843B IntelliVue 1.4 GHz Core Smart-Hopping Access Point

Model ITS4846A IntelliVue Remote Antenna

Model ITS4852A IntelliVue 2.4 GHz Smart-Hopping Access Point

IntelliVue 1.4 GHz Telemetry Patient-worn Transceiver

• ECG Option

• ECG/SpO2 Option

• ECG Upgradeable Option

IntelliVue 2.4 GHz Telemetry Patient-worn Transceiver

• ECG Option

• ECG/SpO2 Option

• ECG Upgradeable Option

IntelliVue MX40 1.4 GHz Telemetry Patient-worn Monitor

• ECG Only

• ECG + FAST SpO2

• SpO2 Ready (enable by software option)

• Full Arrhythmia Capability

• Trend History

• Short Range Radio for WTAAP or Saturn Connectivity,

Cableless Patient

IntelliVue MX40 2.4 GHz Telemetry Patient-worn Monitor

• ECG Only

• ECG + FAST SpO2

• SpO2 Ready (enable by software option)

• Full Arrhythmia Capability

• Trend History

• Short Range Radio for WTAAP or Saturn Connectivity,

Cableless Patient

IntelliVue Telemetry System Mounting Options

• Wall and Shallow Rack Mount for APC (865346) and

Sync Unit (862114)

• Above & Below Ceiling Tile-mount Option for 989803171211 or

989803171221

Product Number/

Option Number

862439

• S01

• S02

• S03

862231

• S01

• S02

• S03

865350

• S01

• S02

• S03

• C01

• C02

• J46

865346

862114

862149

862152

989803171211

865052

989803171221

865351

• S01

• S02

• S03

• C01

• C02

• J46

862415

• K04

• K05

1-34

2

MOSE225

Planning Your ITS Deployment

Locating the IntelliVue Telemetry System Access Points and supporting infrastructure to assure full coverage for all patient-worn transceivers and wireless bedside patient monitors requires careful site planning.

This chapter provides information and procedures that must be followed to ensure a successful IntelliVue 1.4 GHz or 2.4 GHz ITS deployment including:

• Respecting Patient Care Boundaries

• General ITS Infrastructure Site Planning Guidelines

• Performing a Physical Space Assessment

• Planning the Sync Network Layout

• Planning Your AP Groupings

• Performing an RF Frequency Survey

• Assigning 2.4 GHz ITS Channels

• Completing ITS Installation Worksheets

IntelliVue Telemetry System Infrastructure Installation and Service Guide 2 1

MOSE225

Chapter 2: Planning Your ITS Deployment

Respecting Patient Care Boundaries

When planning your IntelliVue Telemetry System deployment, you must take into consideration the boundaries of the patient care environment and the restrictions against installing network equipment within these boundaries. Use caution when installing network equipment. Typically, network equipment is not suitable for use within the patient environment.

1.5 m

(4.9 ft.)

1.5 m

(4.9 ft.)

1.5 m

(4.9 ft.)

2.5 m

(8.2 ft.)

2-2

1.5 m

(4.9 ft.)

1.5 m

(4.9 ft.)

Figure 2-1: Patient Environment Boundaries

Warning Network system components are not suitable for installation in the Patient Care

Vicinity (Patient Environment) -- any area within 1.5 meters (4.9 ft.) horizontally and

2.5 m (8.2 ft.) vertically above the floor from any patient care location in which medical diagnosis, monitoring, or treatment of the patient is carried out.

MOSE225

General ITS Infrastructure Site Planning Guidelines

Note also the general restriction concerning location of ITS Access Points.

Warning The ITS Access Point must be operated at least 15 cm (6 inches) from any person.

This is necessary to ensure that the product is operated in accordance with the

Radio Frequency (RF) Guidelines for Human Exposure.

General ITS Infrastructure Site Planning Guidelines

Patient bedside monitors and patient-worn transceivers with a wireless network connection have their advantages, however the flexibility the wireless link offers is not without its challenges. The reliability and quality of the wireless signal transmission through the air and hospital walls are governed by a number of variables that can be difficult to control. A wireless network connection from a patient monitor or patient-worn transceiver cannot be as dependable as a wired network connection.

The effect of low signal strength and interference on the display of the patient information from a wireless patient monitor at the Information Center can range from a momentary data loss to a lengthy period of data loss. Although data loss due to the wireless link may be occurring at the Information Center, monitoring and alarms continue at the patient monitor. Note however, if the wireless link to a patient-worn transceiver is lost, patient monitoring terminates.

Before installing the IntelliVue Telemetry System as part of an ICN deployment, you must complete the following site planning tasks:

• Perform a physical space assessment.

- Define the desired coverage area within the hospital.

- Determine how many patient-worn transceivers and wireless bedside monitors are required.

- Apply radius-of-coverage circles to the site floorplan to define optimal AP installation locations.

- Add additional APs to cover other high-density wireless client areas if needed.

- Determine the number of Access Point Controllers required to support the installation.

- Evaluate the availability and location of equipment rooms and possible locations for Switches, APCs, PoE Units and Sync Units.

- Specify the cable runs between ITS infrastructure devices.

• Define the number of Uninterruptible Power Supplies required to support the

ITS installation.

• Define the Sync Unit Network required to support the number of APs to be installed. If there are multiple ITS networks in the hospital, then they may need to synchronized together. See Appendix A for details.

• Plan your AP Groupings.

IntelliVue Telemetry System Infrastructure Installation and Service Guide 2 3

MOSE225

Chapter 2: Planning Your ITS Deployment

• If you are installing the 2.4 GHz ITS, perform an RF frequency survey.

- Understand RF co-existence issues in the hospital environment.

- Determine available channels. Use a spectrum analyzer tool to identify RF channels in use and possible interference. Capture and store the spectrum analysis data.

- Assign channels to APs to avoid interference.

Performing a Physical Space Assessment

Assessing the physical space at the ITS deployment site requires that you:

• understand the radius of coverage provided by 1.4 GHz and 2.4 GHz Access

Points

• determine the number of ITS patient-worn transceivers and wireless bedside monitors to be deployed

• determine optimal AP installation locations

• determine the number of APCs required to support the APs to be deployed

• locate IT equipment closets

• plan cable runs between ITS devices

• determine the number of UPSs required to support the ITS deployment

Understanding the Radius of Coverage (RoC) Metric

The radius of coverage (RoC) is the area for which a given access point can provide

RF coverage. Graphically, this is represented as a circle with the AP at its center. In reality, the actual area of acceptable coverage has been demonstrated to be an irregular shape, formed in large part by site structure such as walls, elevator shafts and other materials that affect RF coverage. However as a starting point, a simple circle can often be effectively used to represent coverage for a given AP.

The ITS design goal is to blanket the desired coverage area such that wireless patient devices might move and be used throughout this area without losing network connectivity. The actual usable radius of coverage value depends on the building layout and construction techniques. Table 2-1 lists the RoC values for ITS

Access Points and Remote Antennas.

2-4

MOSE225

Performing a Physical Space Assessment

Table 2-1: Radius of Coverage Values for ITS Access Points

Radius of Coverage Values to Use for

Site Planning and Design

Site

Layout Type

Example

Typical

Patient Room

Area

Dense, congested area/RF impermeable materials

Open air/LOS

Hospital wing area with concentrated patient rooms and newer building construction.

The RoC values listed at right are conservative values that apply to typical deployment sites.

Sites built with materials known to absorb RF energy require that a smaller RoC be used for design. Experience has found that older hospitals with more block, brick, metal lathe and plaster and/or tile construction do not allow RF signals to penetrate walls as well as those with newer drywall and metal stud construction. Also, sites in earthquake prone areas with more reinforced concrete wall construction also absorb more RF energy and need a smaller RoC used for design.

Large metal objects (LMOs) also degrade RF signal propagation. These could be in an area with elevator shafts or lead lined walls such as found in X-Ray imaging areas.

Open “line of sight” (LOS) environment such as a long hallway corridor or open ward with no walls.

Note that when installing Core APs, a Core AP alone (without connected Remote Antennas) will generally provide sufficient coverage for a

LOS area.

1.4 GHz

Standard AP, Core AP, or Remote Antenna, and

2.4 GHz AP (ETSI, ARIB, or AS/NZ Mode)

32 feet

(9.8 m)

30 feet

(9.1 m)

60 feet

(18.3 m)

2.4 GHz AP

(FCC or

RSS-210 Mode)

60 feet

(18.3 m)

50 feet

(15.2 m)

100 feet

(30.5 m)

IntelliVue Telemetry System Infrastructure Installation and Service Guide 2 5

MOSE225

Chapter 2: Planning Your ITS Deployment

Determining the Number of Wireless Clients to be Supported

The number of wireless clients (i.e., patient-worn transceivers and wireless bedside monitors) to be used in the desired coverage area will have an impact on the overall system design. Sites typically will use as many clients as there are beds in the coverage area, or some number fewer than that.

Note We recommend that you use a Core AP alone (without connected RAs) to provide coverage to a Radius-of-Coverage cell that has a high density of wireless clients.

Add additional Core APs to cover other high-density wireless client areas if needed.

Note these limits when determining the number of wireless clients to be supported.

Table 2-2: Maximum Numbers of Wireless Clients Supported

ITS Device

Total Number 1.4 GHz or

2.4 GHz ITS Wireless

Clients (Patient-worn transceivers or bedside monitors)

Device Density: Maximum

ITS Wireless Clients

(Patient-worn transceivers or bedside monitors) per

AP

Maximum Supported

128 (non-routed ICN topology)

1024 (routed ICN topology)

Each Standard 1.4/2.4 GHz AP supports up to 18 wireless clients.

A Core AP alone supports 18 wireless clients. When used with a single RA, the Core AP supports nine wireless clients and its connected RA supports nine wireless clients (9+9=18). When used with two RAs, the Core AP supports six wireless clients and its connected RAs each support six wireless clients (6+6+6=18).

Determining AP Installation Locations

The ITS design goal is to blanket the coverage area with overlapping coverage cells such that wireless patient devices might move and be used throughout this area without losing network connectivity.

When determining where the APs should be installed, preference should be given to the areas where patients spend the majority of their time.

In the ideal system, the number of walls that the RF signal must penetrate should be minimized. Since wall penetration is a requirement in most all covered areas, the

AP should be placed on the side of the wall where the patient (and patient-worn transceiver) spends the majority of the time. At the same time, the AP installation location should maximize the amount of covered area. These objectives are sometimes diametrically opposed. A rule of thumb to designing an optimal system is to limit the wall penetrations for any given AP-to-transceiver connection to one.

The following sections describe the best employment of this approach for two common types of patient room layouts.

2-6

MOSE225

Performing a Physical Space Assessment

Traditional

Hallway Patient

Room Layout

In Figure 2-2, patient rooms lie on either side of the hallway. With traditional corridor

widths of approximately 10 to 12 feet (3 to 3.6 m), and patient room depths of 12 to

18 feet (3.6 to 5.5 m), covering a wing side-to-side with APs placed along the hallway centerline appears feasible (for a 32-foot (9.8 m) RoC). In many cases, this method has been employed successfully, but in others not. Sites with dense wall construction (typically older hospitals, high rise hospitals and/or hospitals built to earthquake codes) often do not perform well using this method, especially if there are bathrooms located in the outside edges of the patient rooms. As RF penetration decreases at these types of sites, the typical method to achieve coverage is to reduce the AP spacing in the hallway and add more APs. This sometimes works, but is really concentrating APs in an area where the patient will not spend much time

(the hallway).

Figure 2-2: AP Placement for a Traditional Room Layout

Non-linear

Patient Room

Layout

The analysis of coverage for hallway-placed APs is quantized quite simply to how many pairs of rooms one AP can cover. Two to three pairs (4 to 6 rooms) is typical. In cases where only one pair can be covered, you may want to consider placing APs in every other room alternating side-to-side along the corridor.

More common in newer hospital designs, are layouts where the patient rooms are placed along the outside of the structure, and non-clinical, administrative areas are clustered in the central areas. This creates an asymmetry in the floor plan relative to the location of the hallways and the patient rooms. In these cases, placing the

APs in the hallway becomes far less desirable as there is no advantage of covering multiple patient rooms from an AP placed outside of the patient rooms. The “one wall” rule would dictate placing the APs in the patient rooms in this type of layout.

The “one wall” rule as applied to this layout would allow for AP coverage in hallways where the patients ambulate as well.

IntelliVue Telemetry System Infrastructure Installation and Service Guide 2 7

MOSE225

Chapter 2: Planning Your ITS Deployment

Placing RoC

Cells on a

Floorplan

Figure 2-3: AP Placement for a Non-linear Room Layout

Figure 2-4 shows an example of how 1.4 GHz ITS AP installation locations were

determined by placing Radius-of-Coverage circles and a Line-of-Sight circle on a floorplan to blanket the coverage area with overlapping coverage cells such that ITS patient-worn transceivers might roam throughout this area without losing network connectivity.

2-8

Figure 2-4: Placing RoC Coverage Circles on a Floorplan

Core AP

Placements

For the example shown in Figure 2-4, a 32 ft. RoC was used for the Access Points

that provided coverage to patient rooms, and a 60 ft. LoS was used for the AP providing coverage to the hallway.

ITS Core AP implementations differ minimally from standard AP implementations.

The primary difference is rather than an individual “home run” UTP cable from each standard AP, only one UTP run is made for each Core AP—from the Core AP to the supporting POE/Sync infrastructure. The Remote Antennas connect directly to the

Core AP via a 74-foot (22.6m) coaxial and unshielded twisted pair (UTP) cable bundle.

MOSE225

Performing a Physical Space Assessment

Spacing between the Core AP and Remote Antennas is limited to the length of the

UTP/coax cable bundle—74 feet (22.6m). The cable assembly, is pre-terminated when manufactured and cannot be shortened. The actual Core AP-to-Remote

Antenna spacing will vary depending on the dimensions of the area to be covered at a given installation site.

The Core AP can be deployed using two installation methods, linear or interleaved.

Regardless of which installation method you use, you must manage the Remote

Antenna port assignments on each Core AP such that RAs with the same Core AP port assignment are not installed adjacent to each other. This restriction must be considered in both two (i.e., Core APs installed on the same floor) and three (i.e.,

Core APs installed on adjacent floors) dimensions. This restriction exists to ensure proper time slot allocation. In the following figures, the port assignment for each RA is listed.

In linear deployments, the component Core AP devices are laid end to end while maintaining an even spacing between devices.

RA 1 RA 2 RA 1 RA 2

Core AP

Figure 2-5: A Linear Core AP Deployment

Core AP

In interleaved deployments, the RAs are located in between an adjacent Remote

Antenna and its Core AP, resulting in an “overlap” of the Core APs. An interleaved design builds in some fault tolerance/redundancy to the RF coverage area.

RA 1 RA 2 RA 1

RA 2

Core AP

RA 1 RA 2

Core AP

Figure 2-6: An Interleaved Core AP Deployment

The following figures represent various possible Core AP deployments.

Figure 2-7 shows a single Core AP deployment. This deployment may be made with

either none, one, or two remote Antennas.

IntelliVue Telemetry System Infrastructure Installation and Service Guide 2 9

MOSE225

Chapter 2: Planning Your ITS Deployment

Figure 2-7: A Single Core AP Deployment

Figure 2-8 shows a multiple, linear Core AP deployment.

Figure 2-8: Linear Multiple Core AP Deployment

Figure 2-9 shows a multiple, interleaved Core AP deployment.

Figure 2-9: Interleaved Multiple Core AP Deployment

Figure 2-10 shows 1.4 GHz ITS Standard APs and Core APs deployed together.

Figure 2-10: Mixed Standard and Core AP Deployment

2-10

MOSE225

Performing a Physical Space Assessment

Access Point

Placement

Guidelines

Note the following important guidelines when locating ITS Access Points:

• AP antennas must be more than four inches (10 cm) away from metal structures. If the antennas are too close to the structure, antenna performance can be degraded.

• Each ITS Standard Access Point can handle communication with up to 18 wireless clients (patient-worn transceivers or bedside monitors).

• A Core AP alone supports 18 wireless clients. When used with a single RA, the

Core AP supports nine wireless clients and its connected RA supports nine wireless clients (9+9=18). When used with two RAs, the Core AP supports six wireless clients and its connected RAs each support six wireless clients

(6+6+6=18).

• We recommend that you use a Core AP alone (without connected RAs) to provide coverage to a Radius-of-Coverage cell that has a high density of wireless clients. Add additional Core APs to cover other high-density wireless client areas if needed.

• APs or Remote Antennas shall not be placed closer than three feet (1 m) together to prevent signal overload conditions.

• Each ITS Access Point requires a 100Mbps/Full Duplex switch port connection.

• Try to avoid placing APs and RAs close to other electrical devices (exit lights, light fixtures, speakers, etc.). Things like florescent light ballasts can create a significant amount of interference that can impact system performance.

• Locate 2.4 GHz ITS Access Points a minimum of six feet (1.8m) from 802.11

APs.

• Locate 2.4 GHz APs at least 6 ft (1.8 m) from 2.4GHz phone base stations.

• Locate 2.4 GHz APs at least 20 ft (6 m) from microwave ovens.

• Orient the antennas on ITS APs so that they are perpendicular to the floor.

Determining the Required Number of APCs

Once the number of required Access Points is known, calculate the number of

Access Point Controllers needed and determine their location. When determining the number of APCs required, follow these guidelines:

• No more than 40 APs should be supported by a single APC.

• No more than 9 APCs should be installed in a system (i.e., 8 APCs fully loaded and 1 APC for redundancy) when installing the ITS.

• We REQUIRE redundancy (this applies to APC redundancy and network redundancy) if the IntelliVue Telemetry System:

- has greater than 32 wireless clients in operation, or

- has greater than 16 32 ft. (9.8m) cells of coverage, or

- has greater than eight 60 ft. (18.3m) cells of coverage.

If any of these three conditions exist, the IntelliVue Telemetry System should be designed such that a single point of failure will not result in more than 32 telemetry patients losing monitoring.

IntelliVue Telemetry System Infrastructure Installation and Service Guide 2 11

MOSE225

Chapter 2: Planning Your ITS Deployment

Refer to Table 2-3 and Table 2-4 for guidance in determining the number of

APCs required for your system.

Table 2-3: Required Number of APCs in Redundant System

With Redundancy:

REQUIRED if:

Total Number of Wireless Clients > 32

OR Number of 32 ft. (9.8m) Cells of Coverage > 16

OR Number of 60 ft. (18.3m) Cells of Coverage > 8

OR Using Routed Network Topology

Number of Access Points

1 to 40

41 to 80

81 to 120

121 to 160

161 to 200

201 to 240

241 to 280

281 to 320

Minimum Number of APCs

8

9

6

7

4

5

2

3

Maximum Number of APCs

9

9

9

9

9

9

9

9

Table 2-4: Non-redundant System Guidelines

NO Redundancy:

Allowed if:

Total Number of Wireless Clients <= 32

AND Number of 32 ft. (9.8m) Cells of Coverage <= 16

AND Number of 60 ft. (18.3m) Cells of Coverage < 8

AND Using Non-routed Topology

Cells of Coverage

1 to 16 (32ft. (9.8m)) Cells

1 to 8 (60 ft. (18.3m)) Cells

Minimum Number of APCs

1

1

Locating Equipment Closets

As part of the RF coverage assessment, you must locate the available IT equipment closets at the ITS installation site.

The location of equipment closets is a relevant consideration as these closets will be used to house the supporting AP and ICN infrastructure. For this reason, equipment closets must be located within 328 feet (100 meters) cable length of each IntelliVue ITS AP to be installed.

Equipment closets must house the ICN network switches, APCs, PoE Units, and

Sync Units. You should assess the needed or available rack space within each equipment closet at this time.

2-12

MOSE225

Performing a Physical Space Assessment

Planning Cable Runs

The ITS APs require an infrastructure to support their datapath, RF synchronization and power needs. Network switches, Power over Ethernet (PoE) Units, and Sync

Units are connected serially between the AP and the devices that receive its data.

The devices are connected as shown in Figure 2-11.

“Data, Power, & Sync” Ports

- data, 48VDC, & Sync Signal

74 ft. Cable

Bundle Carries

Power & Control and RF Signals

LAN Cable

Maximum

Total Distance from Switch to

Access Point =

100m (328 ft)

“Data & Power” Ports

- data & 48 VDC Power

“Data” Ports

- data only

Switch Port Settings

100 Mbps/Full Duplex

Figure 2-11: Maximum AP to Switch Cable Length

From a design perspective, careful analysis of the site's layout, wire run options and equipment closet locations will dictate the optimal ITS infrastructure layout. Ideally, each PoE/Sync Unit pair will support 12 APs, as each has 12 ports available on it.

For this to be the case, the APs must all be located within 328 ft (100m) of the network switch to which they are connected, as the Ethernet wire run limitation for data cables applies; and the PoE and Sync Units must be placed within this run, as they (PoE and Sync Units) do not buffer and re-drive the data signals like some other network devices do.

Thus, each Network Switch/PoE/Sync Unit must be co-located in an equipment closet within 300 feet of each AP they support. In instances where available wiring/ equipment closets are located more or less centrally within or near the coverage area, 12 APs may be within a 300 foot radius of the equipment closet.

Figure 2-12: Maximum AP to Switch Cable Length

However in an extreme case, if all 12 APs are linearly placed in a single corridor and separated by 40 feet (for example), the resulting coverage area would be nearly 500

IntelliVue Telemetry System Infrastructure Installation and Service Guide 2 13

MOSE225

Chapter 2: Planning Your ITS Deployment

feet long. This means that unless the available POE/Sync/Network Switch equipment closet was in the center of that coverage area, the POE/Sync/Network

Switch groupings may have to be placed in multiple locations along the length of the coverage area, and the POE/Sync Units may not be fully loaded with all 12 ports in use.

So the general AP supporting infrastructure methodology is the deployment of POE/

Sync/Network Switch “stacks” within the site's available equipment closet locations. Obviously, each Network Switch has to have a connection back to the main network infrastructure and other non-AP supported devices (central stations, bedsides, etc.) may be plugged into a Network Switch used to support the APs.

Sync Units are required for any installation of two or more APs.

Defining the UPS Deployment

Because a reset of any of the ITS infrastructure devices can result in the loss of patient waveforms for several minutes, we require that the following ITS devices be connected to an Uninterruptible Power Supply (UPS) and also be on emergency hospital power:

• Network Switches & Routers

• Power Over Ethernet Units

• Sync Units

• Access Point Controllers

When determining the number of UPSs required to support your planned ITS deployment, consider the ITS device power draws listed in Table 2-5.

Table 2-5: ITS Infrastructure Device Power Draws

Product Number

862114

862152

862149

862161

862162

453564054671

453564054681

862084

862084

862163

862164

862247

862248

865346 or 862147

Device

Sync Unit

POE – 12 Port

POE – 6 Port

Cisco 2950 Switch: Copper

Cisco 2950 Switch: Fiber

Cisco 2960 Switch: Copper

Cisco 2960 Switch: Fiber

HP 2524 Switch

HP 2510 Switch

Cisco 3550 Router: Copper

Cisco 3550 Router: Fiber

Cisco 3560-24TS Router: Copper

Cisco 3750-24FS Router: Fiber

APC

Power in Watts

10 Watts

165 Watts

90 Watts

30 Watts

30 Watts

30 Watts

30 Watts

36 Watts

20 Watts

65 Watts

85 Watts

45 Watts

70 Watts

10 Watts

2-14

MOSE225

Planning the Sync Network Layout

Planning the Sync Network Layout

Design of a “Sync Network” is required for any site using more than one Sync Unit. A site may need more than one Sync Unit if:

• more than 12 APs are needed

• the geographical dispersion and/or location of available equipment closets dictate this

• multiple ITS networks are installed at a hospital (See Appendix A for details)

The Sync Network is imperative to ensure that all RF channels are driven in

Synchronization and no “drifting” occurs. While these connections are made using

UTP/CAT5 (or greater) cabling like the other network connections, these are nondata connections that can be run up to 500 meters (1640 feet). Note that even ITSs that support non-contiguous RF coverage areas must be synchronized if they are located at the same hospital site.

A Sync Unit can support up to 12 APs and can be configured as a Master or a Slave using its front-panel. It is also possible for a Sync Unit to act as a Master to feed up to 13 Slave Sync Units.The Master Sync Unit is the unit at the head of the chain, or center of the topology and is used to generate the synchronization signal format to other (slave) Sync Units. Slave Units act as regenerators to further distribute the signal if needed.

Note that there must be only one Sync Unit designated as a Master, all others must be Slaves. Also, note that an Access Point cannot be operated from the ‘TO SLAVE

SU’ output on the Sync Unit. APs should only be connected to an “AP/SU” port that sources sync signal, power, and data.

The maximum number of Sync Units that may be linked in a single daisy-chain is 4

(including the Master Sync Unit). Larger installations requiring more than four Sync

Units will use a Star Sync Network that typically has the Master Sync Unit located in the middle. Arms of the Star may each have chains of up to four Sync Units total.

There are three main Sync network layouts:

• Daisy-chained Sync Network

• Star Sync Network

• Hybrid Sync Network

Daisy-chained Sync Network

Figure 2-13 below shows one example of how PoE/Sync Unit/Network Switch stacks might be deployed using the daisy-chain method. Each PoE/Sync Unit/Network

Switch “stack” could support up to 12 APs. The stack Sync Units are all connected by the Master/Slave Sync signal ports on their front panels, the uppermost stack containing the Master Sync Unit.

IntelliVue Telemetry System Infrastructure Installation and Service Guide 2 15

MOSE225

Chapter 2: Planning Your ITS Deployment

2-16

Max. Cable Length is < 500m (1640 ft.)

Figure 2-13: Daisy-chained Sync Network

Star Sync Network

In some cases, the daisy-chain topology of interconnecting AP infrastructures may not be desirable. If the best candidate for the Master Sync Unit is centrally located and the Slave Syncs are located radially around it, using a “star” topology approach to wiring Master/Slaves Sync Units may be preferable.

In this methodology, the Master Sync Unit supplies its signal out of its “AP/SU” ports to as many Slave Sync Units as needed. The total number of Sync Units that can be driven by one Sync Unit is 13. The Sync cable connects to the “AP/SU” port of the

Master, and to the “To Master SU” port on the front panel of the Slave Sync Unit.

Master

Sync Unit

Figure 2-14: Star Sync Network

This topology, however, decreases the number of available ports on the Master Sync

Unit that may be used for APs. ‘AP/SU’ ports used to drive Slave Sync Units may not be used for APs. Any combination of Slave Sync Unit and Access Point connections

MOSE225

Cable Delay Rotary Switch Settings

can be made to these ports, up to the maximum of 13 (i.e., 12 Sync Units connected to the AP/SU Ports and one connected to the “To Slave SU” port), from any one Sync Unit.

Note also that in this “star” topology, the 'AP/SU' ports on the Master Sync Unit must have their corresponding PoE ports connected to a PoE Unit, or the synchronization signal will not be propagated to the Slave Sync Unit. Also, the cable delay switch should be properly set for each Slave Sync Unit.

Hybrid Sync Network

If you need more than the 144 AP connections provided by the star topology, then

you can create a hybrid of the daisy-chain and star topologies (Figure 2-15).

Figure 2-15: Hybrid Sync Network Topology

Cable Delay Rotary Switch Settings

You must select a delay setting on the front panel of the Sync Unit using the Cable

Delay rotary switch. The switch setting must correspond to the length of the cable connected the Sync Unit’s To Master SU port (its Sync source may be the system

Master, or another Slave Sync Unit in a daisy-chain implementation.).

The delay switch setting on a Master Sync Unit does not affect ITS operation, but for consistency, always set it to 1. Set the Delay Switch on Slave Sync Units as listed in

Table 2-6.

IntelliVue Telemetry System Infrastructure Installation and Service Guide 2 17

MOSE225

Chapter 2: Planning Your ITS Deployment

Table 2-6: Sync Unit Cable Delay Rotary Switch Settings

Cable Length

0 to 50 meters (0 to 164 ft.)

>50 to 100 meters (164 to 328 ft.)

>100 to 150 meters (328 to 492 ft.)

>150 to 200 meters (492 to 656 ft.)

>200 to 250 meters (656 to 820 ft.)

>250 to 300 meters (821to 984 ft.)

>300 to 350 meters (984 to 1148 ft.)

>350 to 400 meters (1148 to 1312 ft.)

>400 to 450 meters (1312 to 1476 ft.)

>450 to 500 meters (1476 to 1640 ft.)

Sync Unit - Cable Delay

Rotary Switch Position

6

7

4

5

1

2

3

8

9

10

If the delay setting is not set correctly, the APs will not be synchronized properly resulting in an intermittent loss of connectivity.

Planning Your AP Groupings

“Groups” as defined for the IntelliVue Telemetry System have more than one meaning and must be carefully thought out prior to configuration. They are also defined in two places on the system and care must be taken to ensure that the definitions are not in conflict.

Configuring AP Groups in the IntelliVue Telemetry System

Groups are defined in the IntelliVue Telemetry System infrastructure configuration, and then APs are assigned to them. The reasons for creating AP groups are:

• Groups of APs can be individually targeted for upgrades without affecting the

APs in the other groups.

• Each defined group can have a different destination IP for its alerts. The destination IP is the IP of a database server on the system. The relevance of this destination IP is twofold:

- The DBS will accumulate all alerts for those APs and build an alert database from them.

- The DBS will send out alert system messages to all IICs on its DBSD.

• An APC can be “partnered” with an AP group. This is the APC that manages an

AP during normal operation. However, if the assigned APC fails, then the APs will

“partner” with any available APC.

For these reasons, care must be taken when defining the groups. APs which are not physically located within a care area must still be given a “home” group for equipment management purposes. This includes APs in transport areas as well as

AP in procedure areas (such as X-ray or Dialysis) that may be used by patients in more than one care group, such as ICU and CCU.

2-18

MOSE225

Planning Your AP Groupings

Assigning Equipment to Units in the Config Wizard (IIC)

Equipment is assigned to “units” in the IIC config wizard. This is a way to further segment the IntelliVue Clinical Network (ICN) Database Domain (DBSD) into smaller groups, as a single DBSD may, and often does, support more than one unit. All units on the DBSD are served by the same Database Server (DBS).

Bedside equipment is assigned to units and, network devices, although they shared by all devices on the DBSD, are assigned to units as well.

Refer to Table 2-7 for a sample configuration plan to consider when assigning ITS

equipment to units as part of the overall DBS configuration.

Table 2-7: Sample DBS Configuration Plan

In Config Wizard:

ITS AP Configured?

Assigned to Unit?

In APC:

AP Group Alert

Destination is

This DBS

In APC:

AP Group Alert

Destination is

Another DBS

Yes

Yes

Location

AP Stats

Alerts

Location

AP Stats

No Alerts

Yes

No

Location

No AP Stats

Alerts

Location

No AP Stats

No Alerts

No

Yes

Configuration

Not Possible

Configuration

Not Possible

No

No

No Location

No AP Stats

No Alerts

No Location

No AP Stats

No Alerts

Sample AP Group Configuration

For example, consider a hospital that has APs deployed in six main areas:

• ICU

• CCU

• X-Ray

• Dialysis

• Pulmonary

• Transport corridors in between these departments

In this hospital, the ICU and CCU are on two different ICN DBSDs, and there are no

IICs in any of the procedure areas (X-Ray, Pulmonary or Dialysis).

In planning the groups for this hospital, the service provider handling the installation must decide where the alerts destination should be for each AP group and also ensure that the group is also defined in Config Wizard and used similarly.

IntelliVue Telemetry System Infrastructure Installation and Service Guide 2 19

MOSE225

Chapter 2: Planning Your ITS Deployment

The service provider decides the groups should be set up as follows:

Table 2-8: Sample AP Groupings

AP Location

ICU

CCU

X-Ray

Dialysis

Pulmonary

Transport corridors

AP Group

Name on APC

ICU

CCU

X-Ray

Dialysis

Pulmonary

Transport

Config Wizard Devices

ICU

CCU

ICU

ICU

ICU

ICU

System Devices in the

Philips IntelliVue

Telemetry System

APs in ICU

APs in CCU

APs in X-Ray

APs in Dialysis

APs in Pulmonary

APs in transport corridors

In this case, the ICU DBS will accumulate the alerts logs for all APs except those in the CCU. All IICs in the ICU DBSD will display alert messages when they occur

(typically only on device failure).

Conversely, only the CCU IIC will display messages for APs in the CCU and its DBS will accumulate a database of alert data only for the CCU APs.

This means that if you don’t assign the groups the same way in Config Wizard and the APCs, it may make it difficult to correlate alert data when reviewing it.

It would be possible to make all of the APs belong to the same group and have the same destination, but this would mean that if they needed to be upgraded, the down time required to perform the upgrade may affect the whole system rather than one group at a time.

Performing an RF Frequency Survey

The IntelliVue Telemetry System operates on the 1.4 GHz US Wireless Medical

Telemetry Service (WMTS) band or on the 2.4 GHz band.

In the USA, you must have a minimum of three available channels to deploy the 1.4

GHz ITS successfully. In general, this should not be a problem as the WMTS band is reserved, protected spectrum in the USA.

You must have a minimum of three available channels (six available channels is recommended) to deploy the 2.4 GHz ITS successfully. As there are many devices

(especially 802.11 b/g devices) that use the 2.4 GHz spectrum, it is imperative that you perform an RF frequency survey before installing the 2.4 GHz ITS.

Understanding RF Coexistence Issues in the 2.4 GHz Spectrum

There are several devices that may be encountered in the hospital environment that radiate 2.4GHz RF energy and may be potential interferers. An understanding of their existence and power levels is key to a successful ITS deployment.

2-20

MOSE225

Performing an RF Frequency Survey

Microwave

Ovens

Transient Noise in the 2.4 GHz Spectrum

Transient noise is RF energy that is not constant, but rather spurious and intermittent. Transient noise may sometimes only be observed by analyzing RF spectra over a longer period of time, or it may not be seen at all of it occurs outside the time that the data is taken.

The pulse of most consumer grade microwave ovens (typically 700-1300 watts) generally falls in the middle of the 2.4 GHz band. The pulse is very broad and will often affect at least half of the usable 2.4 to 2.5 GHz spectra but may not always be in the same place. Most consumer grade microwaves are single magnetron tube devices and the RF radiation of these varies by manufacturer.

While microwave ovens are typically used only periodically, their location should be known and steps should be taken to minimize their potential interference.

To avoid interference, position ITS Access Points a minimum of 20 feet (6 m) from consumer-grade microwave ovens. Ensure that there is not a microwave oven located between an Access Point and wireless beside monitors or patient-worn transceivers.

20 feet (6 m) (Consumer-grade Oven)

Figure 2-16: Recommended Minimum AP Distance from Microwave Ovens

Bluetooth

Devices

Other Transient

Devices

Avoidance: Physical separation of at least 20 feet. Microwave level at 2.4 GHz ITS

AP shall be < -25dBm. Use insufficient spectrum alert on APC web interface to determine if microwave source will be a problem at selected AP location.

Microwaves that operate on ½ sine wave can be avoided by the 2.4 GHz ITS with its frequency agility & retry mechanism. If a patient-worn transceiver is in close proximity to a microwave source, then data loss > 90sec/day may be experienced.

Although originally designed and deployed for short distance, low power Personal

Area Network (PAN) deployments, full power (100mW) devices are now being produced and deployed.

A Bluetooth device may operate as a frequency hopper or as a device emitting energy on several narrow band channels. Fortunately, Bluetooth devices are usually very low powered and have interference avoidance algorithms built into them. When a Bluetooth device encounters a fixed channel system like the 2.4 GHz ITS, it should avoid conflict. Unfortunately, Bluetooth devices are typically non-hospital owned

“walk-in” devices and thus are difficult to control. For this reason, they are treated as transient noise sources.

Avoidance: Possibly none needed. Provide physical separation if possible. Refer to hospital policy on Bluetooth use in care areas. 2.4 GHz ITS can tolerate Bluetooth piconet systems with seven Bluetooth 2.0 devices communicating.

Increasingly, the 2.4GHz space is being used for other non-communication or noncomputer related devices. Various remote controls and children's toys are using

2.4GHz radios. Be sure to consider these as possible interference sources. If

IntelliVue Telemetry System Infrastructure Installation and Service Guide 2 21

MOSE225

Chapter 2: Planning Your ITS Deployment

persistent, a noise source like this would be discovered by a spectrum analysis, typically appearing as a narrow band, continuous emitter with nearly a 100% duty cycle.

Avoidance: Physical separation.

802.11/WiFi

Devices

Cordless

Phones and

Headsets

Wireless

Security Devices

Continuous Noise in the 2.4 GHz Spectrum

We refer to “Continuous” RF emitters as devices that emit energy constantly, although seldom at a 100% duty cycle.

Devices which “beacon” when in low use may not be thought of as continuous noise sources, but because they often appear in short-term (5 to 20 minute) spectra captures, they are treated as such.

Noise attributed to 802.11 devices will vary in duration/duty cycle. It can range from short, intermittent “beaconing” bursts to near steady state, broad spectrum energy from heavily loaded, systems. Fortunately, device keep-alive and beaconing schemes make them generally detectable anytime that they are turned on, and therefore are treated as steady state noise sources.

While many 802.11 systems are fixed channel, many newer systems are dynamic and may change channels as other RF spectra changes take place. Predictable, coexistence with 2.4 GHz ITS is possible only if both the ITS and the WiFi device are configured for static, fixed channelization.

The 2.4 GHz ITS has pre-set configurations that are designed to “fit” channels in

between commonly used 802.11b/g channels. See “Avoiding WiFi Interference” on page 2-24 for more details.

Avoidance: Collaboration with hospital IT administrators to achieve a fixed 802.11 channel configuration that avoids the 2.4GHz ITS channel configuration. Use 2.4

GHz ITS channel assignment to avoid these 802.11 b/g channels: 1, 6, 11 or

1, 7, 13. Locate 2.4 GHz ITS APs and Remote Antennas at least 6 ft (2 m) from

802.11 Wi-Fi APs.

2.4GHz cordless phones and wireless headsets are prevalent and have been shown to interfere with 2.4GHz systems when in very close proximity. These devices are generally DECT-based frequency hoppers and populate the spectrum with moving

RF “spikes.” When enough devices are present, they may fill the whole spectrum with narrow-band, spike activity. The duty cycle however is typically very low.

Note that many cordless phones/headsets will emit “beacon” pulses even when not being used. Do not assume that such devices can only interfere when in use. For this reason, they are being dealt with here as “Continuous” interferers. Some of the higher end versions of these devices are capable of detecting like-channel interferers and avoiding them. These systems may simply “stay away” from the 2.4

GHz ITS, with fixed channelization, however this cannot be assumed.

Avoidance: Typically, no avoidance measures are needed. Provide physical separation if required. The 2.4 GHz ITS can tolerate up to 12 (2.4GHz) phones.

X10 cameras, wireless baby monitors and other devices dominate bandwidth on a constant, streaming basis. Duty cycle is typically 100%, however the spectrum usage is narrow.

2-22

MOSE225

Performing an RF Frequency Survey

ZigBee Devices

Survey

Objectives

Using the

Spectrum

Analyzer Tool

Avoidance: Collaboration of configurations with system IT or administrators. Fixed channelization and 2.4 GHz avoidance configuration (channelization).

ZigBee is a published specification set of high level communication protocols designed to use small, low power digital radios based on the IEEE 802.15.4 standard for wireless personal area networks (WPANs). This essentially means that implementations (and therefore RF “footprints”) will vary widely, more so than with other technologies. ZigBee is aimed at applications with low data rates and low power consumption and the technology is designed to be simpler and cheaper than other WPANs such as Bluetooth.

Avoidance: Implement proper ZigBee channel management. Limit channels used by

ZigBee to ensure that at least three 2.4 GHz channels are available for the ITS.

RF Site Survey Guidelines

Site surveys are required for all sites to validate the viability of usable RF spectrum for the 2.4 GHz ITS. The result of the site survey will be a picture of the available spectra at the site into which the ITS may be configured.

Once the site survey is done, you should use the survey data as the basis for selecting the channels used by the 2.4 GHz ITS.

The premise of steady-state or continuous RF interference is that while its source may not be known, it is more or less continuously in the environment and taking a measurement of RF energy for a duration of as little as five minutes will capture it.

Short duration tests are intended to capture this type of interference.

It is also acknowledged that in many cases, interference will be experienced intermittently at a given location either because the source is an intermittent radiator (or intermittently used by hospital personnel), or that it is a moving radiator that is experienced in a given location only as it moves through that area.

Capturing and measuring intermittent interferers is difficult. Even if measurement tools are left on to “listen” for hours and even days, they may still miss an “event” that would cause interference with the 2.4GHz ITS. A monitoring/measurement system should be left on as long as time permits to have the best chance to capture all possible steady and intermittent interference sources.

The Spectrum Analyzer tool should be used to assess and capture the steady-state

RF profiles. The data capture feature of this tool will be used to capture and create

.ccf files for each test location. Note that data files for a five-minute capture are approximately 1.6Mb in size and those for a two-hour capture are approximately

37Mb.

The Spectrum Analyzer allows you to specify the duration of the capture in advance such that when the time limit is reached, recording automatically stops.

Note In most cases, screen shot captures of Spectrum Analyzer displays are most effective when the tool is not moved during the data gathering. “Roaming” type tests can be useful sometimes, but trying to annotate the captured data such that another person looking at it later will know exactly how the tool was moved during the capture is difficult, if not impossible. Taking separate captures at fixed locations and annotating on a floorplan where each capture was a taken usually achieves a better overall analysis of the environment.

IntelliVue Telemetry System Infrastructure Installation and Service Guide 2 23

MOSE225

Chapter 2: Planning Your ITS Deployment

Determining

Measurement

Locations

Floor plans should be procured for the test sites and patient care areas identified.

Survey locations can be identified in advance on the floor plans and given location designations.

Short term captures (to detect steady state RF energy) should be taken at several such locations in the patient care areas, as well as on floors above and below, and adjacent areas as time and access permit. The objective is to take measurements in patient care areas where wireless monitoring of any kind might be employed, and the surrounding areas.

In a typical hospital unit, short term (five-minute) measurements should be taken in rooms along one side of the building, but not in every room. It is expected that any unit-wide RF activity would be found in most all rooms that were geographically and architecturally similar. Preference should be given for patient care areas that have windows which face other buildings, parking lots or areas of significant activity.

Additionally, patient care areas which are adjacent to common public areas such as lobbies, main corridors or waiting areas should be considered as a test location.

Surveys should be taken at planned AP locations also.

Also, “long-term” site-surveys should be executed when possible (especially for

“critical” sites where implementation to a high degree of thoroughness is warranted). Long-term captures should be taken in at least one location in the patient care area for a minimum period of two hours. The test period should be during a time of maximum hospital activity (i.e., not overnight) to try and capture all intermittent RF sources. Generally, overnight testing is not recommended, as it does not present a realistic picture of spectra use.

Assigning 2.4 GHz ITS Channels

When installing the 2.4 GHz ITS, you must configure 3-6 channels for the system to use. To have a successful deployment, the channels must be located in RF spectra where they are least likely to be interfered with. Choosing appropriate channels after reviewing the Spectrum Analyzer data is critical.

Avoiding WiFi Interference

In hospitals, 802.11 systems are the most likely source of interference in the 2.4

GHz space. The following sections describe how to choose the appropriate channels to avoid interference from WiFi systems as well as from other sources of interference.

Figure 2-17 shows the relationship between available 2.4 GHz ITS channels and

802.11b/g channels.

2.4 GHz ITS Frequency Plans

The 2.4 GHz ITS provides for simple configuration amid common 802.11 deployments. Configured in this way, the system automatically configures itself for the channels in the “holes” left by the specified 802.11 configuration. Graphical examples are shown below.

2-24

MOSE225

Assigning 2.4 GHz ITS Channels

Figure 2-17: 2.4 GHz ITS Channels vs. 802.11b/g Channels

Frequency Plan

1,6,11

Where channels 1-11 are available for 802.11 deployments, channels 1,6,11 offer orthogonality in a three-channel design. When channels 1,6, and 11 are used for

WiFi, configure channels 14,28 and 44-47 for use by the 2.4 GHz ITS.

Frequency Plan

1,7,13

Figure 2-18: Free 2.4 GHz ITS Channels in a 1,6,11 WiFi Configuration

In Europe, where channels 1-13 are available for 802.11 deployments, channels

1,7,13 offer good orthogonality in a three-channel design. When channels 1,7,and

13 are used for WiFI, configure channels 14-16 and 31-33 for use by the 2.4 GHz

ITS.

Using “Advanced” 2.4 GHz ITS Channel Configurations

In cases where an 802.11 deployment with channels 1,6 and 11, or 1, 7 and 13 are not the predominant interferers to be avoided, specific, individual channel configuration is warranted. Site situations will vary, but the RF Spectrum Analysis should show visually where the best location to configure the 2.4 GHz ITS channels are.

IntelliVue Telemetry System Infrastructure Installation and Service Guide 2 25

MOSE225

Chapter 2: Planning Your ITS Deployment

Figure 2-19: Free 2.4 GHz ITS Channels in a 1,6,11 WiFi Configuration

For example, if DECT phones are present at the site and occupy only the upper ¾ of the available spectra, choosing channels on the low end (1-9) of the available range is best.

If the spectra is clean other than a nearby microwave that the spectrum analysis shows radiates in the low end of the spectrum, you should select channels in the upper end of the spectrum for the 2.4 GHz ITS.

Completing ITS Installation Worksheets

As part of the planning process for your ITS deployment and prior to installing any components, be sure to photocopy and complete the following ITS installation worksheets:

• ITS Infrastructure Equipment Summary Table (page 2-27)

• ITS Access Point Equipment Summary Table (page 2-27)

• APC Configuration Worksheet (page 2-30)

• 1.4 GHz Default AP Configuration Worksheet (page 2-33)

• 2.4 GHz Default AP Configuration Worksheet (page 2-34)

• AP Group Configuration Worksheet (page 2-36)

2-26

MOSE225

Completing ITS Installation Worksheets

ITS Infrastructure Equipment Summary Table

Note the location, IP address, etc. of ITS infrastructure devices (network switches,

PoE Units, APCs, etc.) before you physically install them using Table 2-9.

Table 2-9: ITS Infrastructure Equipment Summary

Device Type Device Name

Physical

Location

IP Address Subnet Mask

ITS Access Point Equipment Summary Table

Note the location, IP address, MAC, etc. of ITS Access Points before you physically

install them using Table 2-10 and Table 2-11.

IntelliVue Telemetry System Infrastructure Installation and Service Guide 2 27

AP Name RF ID

Table 2-10: ITS 1.4 GHz Access Point Equipment Summary

Group

Membership

IP Address

MAC

Address

Physical Location

Partnered

APC

Connected to

Switch

Connected to

Switch Port

UTP

Cable Run

ID

MOSE225

MOSE225

AP Name RF ID

Group

Membership

IP Address

Table 2-11: ITS 2.4 GHz Access Point Equipment Summary

MAC

Address

Physical

Location

Partnered

APC

Connected to Switch

Connected to

Switch Port

UTP

Cable Run

ID

2.4 GHz

Frequency

Plan

2.4 GHz

Radio

Regulations

MOSE225

Chapter 2: Planning Your ITS Deployment

Setting

Descriptions

APC Configuration Worksheet

Refer to the following setting descriptions when completing the Access Point

Controller Configuration Worksheet.

• APC Configurations - In the worksheet provided, fill in the following information for each APC to be added to the wireless subnet:

- APC Name - Name to be assigned to this APC within the system

- APC MAC - MAC Address documented on product label (physical address)

- APC IP Address - IP address for the APC within the wireless subnet

• Subnet Mask - Set to subnet mask of the ITS wireless subnet. This will be

255.255.240.0 for Routed systems, and 255.255.248.0 for Non-Routed systems.

• Default Gateway - Typically this will be 172.31.240.1 for Routed systems, and

172.31 (n + 3).0 for Non-Routed systems.

Separate blank templates for non-routed and routed ICN topologies are provided on the following pages.

2-30

MOSE225

Completing ITS Installation Worksheets

APC Configuration Worksheet for Non-routed ICN Topology

APC Static Address Configuration

APC Name MAC Address IP Address

Range:

172. 31.(n+1).0 -

172. 31.(n+1).63

Subnet Mask

255.255.248.0

255.255.248.0

255.255.248.0

255.255.248.0

255.255.248.0

255.255.248.0

255.255.248.0

255.255.248.0

255.255.248.0

255.255.248.0

Default Gateway

172.31.(n + 3).0

(DBS)

BOOTP/DHCP Server Configuration

NON-ROUTED: Range 1 - Transceivers and Wireless Bedsides

Setting

MAC Address Base

MAC Address Mask

IP Address Range (Minimum)

IP Address Range (Maximum)

Subnet Mask

Default Gateway

DNS Server IP Address

Rules

00:09:fb:06:00:00 ff:ff:ff:0f:00:00

172.31.(n + 6).0

172.31.(n + 6).255

255.255.248.0

172.31.(n + 3).0 (DBS)

0.0.0.0

Factory Default

00:09:fb:06:00:00 ff:ff:ff:0f:00:00

172.31.6.0

172.31.6.255

255.255.248.0

172.31.3.0

0.0.0.0

Site Modification

00:09:fb:06:00:00 ff:ff:ff:0f:00:00

255.255.248.0

0.0.0.0

Setting

MAC Address Base

MAC Address Mask

IP Address Range (Minimum)

IP Address Range (Maximum)

Subnet Mask

Default Gateway

DNS Server IP Address

NON-ROUTED: Range 2 - Access Points

Rules

00:09:fb:05:00:00 ff:ff:ff:0f:00:00

172.31.(n + 2).128

172.31.(n + 2).255

255.255.248.0

172.31.(n + 3).0 (DBS)

0.0.0.0

Factory Default

00:09:fb:05:00:00 ff:ff:ff:0f:00:00

172.31.2.128

172.31.2.255

255.255.248.0

172.31.3.0

0.0.0.0

Site Modification

00:09:fb:05:00:00 ff:ff:ff:0f:00:00

255.255.248.0

0.0.0.0

IntelliVue Telemetry System Infrastructure Installation and Service Guide 2 31

MOSE225

Chapter 2: Planning Your ITS Deployment

APC Configuration Worksheet for Routed ICN Topology

APC Static Address Configuration

APC Name MAC Address IP Address

Range:

172.31.241.0 -

172.31.241.247

Subnet Mask

255.255.240.0

255.255.240.0

255.255.240.0

255.255.240.0

255.255.240.0

255.255.240.0

255.255.240.0

255.255.240.0

255.255.240.0

255.255.240.0

Default Gateway

172.31.240.1

ROUTED: Range 1 - Transceivers and Wireless Bedsides

Site Modification Setting

MAC Address Base

MAC Address Mask

IP Address Range (Minimum)

IP Address Range (Maximum)

Subnet Mask

Default Gateway

DNS Server IP Address

Factory Default

00:09:fb:06:00:00 ff:ff:ff:0f:00:00

172.31.248.0

172.31.253.255

255.255.240.0

172.31.240.1

0.0.0.0

Setting

MAC Address Base

MAC Address Mask

IP Address Range (Minimum)

IP Address Range (Maximum)

Subnet Mask

Default Gateway

DNS Server IP Address

ROUTED: Range 2 - Access Points

Factory Default

00:09:fb:05:00:00 ff:ff:ff:0f:00:00

172.31.244.128

172.31.246.255

255.255.240.0

172.31.240.1

0.0.0.0

Site Modification

2-32

MOSE225

Completing ITS Installation Worksheets

Setting

Descriptions

1.4 GHz Default AP Configuration Worksheet

Refer to the following setting descriptions when completing the 1.4 GHz Access

Point Configuration Worksheet.

• Partnered APC - “Any”

• Default Group - Always Smart-hopping.

• WMTS Channels - Circle the WMTS Channel that will be used for this installation. Default range = 1 to 6. Note: Disable channels 4, 5 & 6 when

Special Geographic Area is selected - use channels 4a, 1, 2 and 3.

• RF Access Code - Enter number between 1 and 254 to be used as the Access

Code for the system (site specific). Do not use 0 or 255, these are reserved for special use. For use of multiple RF Access Codes, refer to Appendix A, “Installing

Multiple ITSs at a Single Hospital Site.”

• IP Addressing: Subnet Mask - Enter the Static Subnet Mask documented for the

APC Configuration.

• IP Addressing: Default Gateway - Enter the Static Default Gateway documented for the APC Configuration.

Blank Template

Settings

Partnered APC

Default Group

WMTS Channels

RF Access Code

Rules

Any

Smart-hopping

Value

Circle channels at right.

Enter any number from 1 to 254 at right. (not 0 and not 255)

Standard: 1 2 3 4 5 6

Special: 4a

1 (Site Specific)

IP Addressing: Subnet mask

IP Addressing: Default gateway

[Copy from APC Configuration]

[Copy from APC Configuration]

IntelliVue Telemetry System Infrastructure Installation and Service Guide 2 33

MOSE225

Chapter 2: Planning Your ITS Deployment

Setting

Descriptions

2.4 GHz Default AP Configuration Worksheet

Refer to the following setting descriptions when completing the 2.4 GHz Access

Point Configuration Worksheet. Use the information you record in this worksheet

with the procedure entitled “Step 9. Add APs to the Network.” on page 3-38.

• Partnered APC - “Any”

• Default Group - Always Smart-hopping

• Radio Regulations - Specify the radio regulations that apply to the country in which you are installing the 2.4 GHz ITS. Possible Radio Regulation choices are:

• ETSI - Europe, South America, Asia, Asia Pacific, and Africa

• FCC - United States, Taiwan, Singapore, and Hong Kong

• RSS-210 - Canada/North America

• AS/NZ - Australia/New Zealand

• ARIB - Japan

• Frequency Plan - Specify the 802.11 channel configuration with which the 2.4

GHz ITS will co-exist. Possible Frequency Plan choices are:

Frequency Plan

2.4 GHz ITS Channels Configured for Use

FCC,ARIB,RSS-210

14, 28, 44, 45, 46, 47

1

ETSI, AS/NZ

14, 28, 43, 44, 45, 46 Co-exist with 802.11

Channels 1, 6, 11

Co-exist with 802.11

Channels 1, 7, 13

Advanced

14, 15,16, 31, 32, 33

2

14, 15, 16, 31, 32, 33

2

Any set (min 3, max 6) of 2.4 GHz

ITS channels from 0 - 47, excluding any that have been disabled by the ZigBee selection.

Any set (min 3, max 6) of 2.4 GHz

ITS channels from 1 - 46, excluding any that have been disabled by the ZigBee selection

1

-

If any one of this set of six channels is disabled by the ZigBee channel selection, then channel

43 can be used instead.

2

-

If any one of this set of six channels is disabled by the ZigBee channel selection, then channel

34 can be used instead.

If you select Advanced, then you must specify a minimum of three and a maximum of six channels (six is recommended) for use by the 2.4 GHz ITS.

• ZigBee channel used for medical - Specify the ZigBee channel used for medical purposes at the installation site. Possible selections are channels 11 to 26.

Default: None.

• RF Access Code - Enter number between 1 and 254 to be used as the Access

Code for the system (site specific). Do not use 0 or 255, these are reserved for special use. For use of multiple RF Access Codes, refer to Appendix A, “Installing

Multiple ITSs at a Single Hospital Site.”

2-34

MOSE225

Completing ITS Installation Worksheets

Blank Template

• IP Addressing: Subnet Mask - Enter the Static Subnet Mask documented for the

APC Configuration.

• IP Addressing: Default Gateway - Enter the Static Default Gateway documented for the APC Configuration.

Settings

Partnered APC

Default Group

Rules

Any

Smart-hopping

Value

Radio Regulations

Frequency Plan

ZigBee channel used for medical

RF Access Code

Specify radio regulations that apply to country in which 2.4 GHz ITS is installed. Circle applicable regulations at right.

2.4 GHz Must Co-exist with Installed

2.4 GHz 802.11 b/g Systems

Circle 802.11 plan at right.

ETSI

FCC

RSS-210

AS/NZ

ARIB (Japan)

1, 6, 11

1, 7, 13

Advanced - Enter a min. of 3 and a max. of 6 channels for use by the ITS.

None (Site Specific) Specify the ZigBee channel used for medical purposes at the installation site. Possible selections are channels

11 to 26.

Enter any number from 1 to 254 at right. (not 0 and not 255)

1 (or other Site-specific Value)

IP Addressing: Subnet mask

IP Addressing: Default gateway

[Copy from APC Configuration]

[Copy from APC Configuration]

IntelliVue Telemetry System Infrastructure Installation and Service Guide 2 35

MOSE225

Chapter 2: Planning Your ITS Deployment

Setting

Descriptions

Blank Template

AP Group Configuration Worksheet

For each AP Group to be established, complete a separate worksheet. The template

for this form is provided on the Documentation CD-ROM. See “Planning Your AP

Groupings” on page 2-18 for information about AP groups and how you may want to

configure them. Use the information you record in this worksheet with the

procedure entitled “Configuring AP Groups” on page 3-30.

Group Level Settings:

Document the following settings for each AP group:

• AP Group Name - Name of the AP Group

• AP Group Type - Always Smart-hopping

• AP Group Description - Optional notes regarding this AP Group

• Partnered APC - Copy APC Name from APC Configuration Worksheet for the APC that will be associated with Access Points in this group.

• Alert Destination - IP Address of Database Server/IIC receiving alerts for this group of APs.

AP Group Members:

Document the following settings for each AP group:

• AP MAC Address - MAC Address as labeled on the Access Point

• AP Name - Name to be assigned to this AP within the system.

• AP Specific IP Address - Specific IP address to be assigned to this AP. This IP address needs to be the same as the IP address assigned in the Database

Server in order for statistics gathering to occur for this AP.

Group Level Parameters

Value Setting

AP Group Name

AP Group Type

AP Group Description/

Area Covered (optional)

Partnered APC

Rules

Enter APC Name from AP

Configuration Worksheet.

Alert Destination

(DBS IP Address)

Smart-hopping

2-36

MOSE225

Completing ITS Installation Worksheets

AP Group Members

AP Group Name:

AP MAC Address No.

12

13

14

15

10

11

8

9

16

17

18

19

20

6

7

4

5

1

2

3

AP Name AP Specific IP Address

IntelliVue Telemetry System Infrastructure Installation and Service Guide 2 37

Chapter 2: Planning Your ITS Deployment

MOSE225

2-38

3

MOSE225

Installing and Configuring the ITS

This chapter provides procedures to physically install the IntelliVue

Telemetry System components and configure the ITS operational settings for use at the installation site, and includes:

• High-level ITS Installation and Configuration Procedure

• Step 1. Complete the ITS Installation Worksheets.

• Step 2. Install the ITS Infrastructure Components.

• Step 3. Set Up Your Service PC.

• Step 4. Perform Initial Configuration of the APCs to be Installed.

• Step 5. Add the APCs to the Network.

• Step 6. Run the Philips Upgrade Wizard.

• Step 7. Verify and Configure Important ITS Settings via the APC

Interface.

• Step 8. Run the Philips Upgrade Wizard Again.

• Step 9. Add APs to the Network.

• Step 10. Rename Installed APs and Remote Antennas.

• Step 11. Run the Philips Upgrade Wizard Again.

• Step 12. Export the ITS Configuration to a Disk File.

• Step 13. Restore your Service PC to its Original Settings.

• Step 14. Install ITS Bedside Monitors and Patient-worn Devices.

IntelliVue Telemetry System Infrastructure Installation and Service Guide 3 1

MOSE225

Chapter 3: Installing and Configuring the ITS

High-level ITS Installation and Configuration Procedure

The following high-level procedure lists the steps you must follow to install and configure the IntelliVue Telemetry System. Detailed procedures for each of these steps is provided in the sections that follow.

To install and configure the ITS:

1. Photocopy and complete the ITS Installation Worksheets provided in Chapter 2.

(page 2-26)

Note the location, IP address, MAC, etc. of ITS infrastructure devices before you physically install them. Be sure to complete the APC and AP configuration worksheets prior to attempting to configure the ITS Access Point Controller.

2. Physically install, but do not power up, the ITS infrastructure components.

(

page 3-4

)

At this time complete all inter-component cabling connections with the exception of connecting the APs and APCs to the network. Do not connect the

APs and APCs to the network until you have configured the APCs.

3. Set up your Service PC so that it may be used to connect to the ITS Wireless

Subnet. (

page 3-8

)

4. Perform initial configuration of each APC. (

page 3-12

)

5. Add the APCs to the network. (

page 3-14

)

6. Run the Philips Upgrade Wizard to verify that the newly installed APCs have the same firmware revision. (

page 3-16

)

7. Using the APC web interface, verify and configure these settings: (

page 3-22

)

• Verify Filters

• Verify BootP Address Ranges

• Verify AP Defaults

• Configure AP Groups

• Configure Basic Settings for each Group

• Configure Alerts for each Group

8. Perform the configuration check and replication procedure using the Philips

Upgrade Wizard to verify that the APCs have the same firmware revision and

proper configuration settings. (

page 3-34

)

9. Add each Access Point to the ITS, wait for a period of 60 seconds, and then configure it via the APC web interface. Ensure that you have connected each

Core AP to its installed Remote Antennas before connecting the Core AP to the

ITS. (

page 3-38

)

For each Standard and Core AP you will need to: a) Configure the AP Name, IP Address and Group membership.

b) Verify the AP Subnet mask, and Default gateway settings.

c) Assign descriptive meaningful names to Core AP Remote Antennas.

d) Save the AP configuration settings.

3-2

MOSE225

High-level ITS Installation and Configuration Procedure

e) Verify that the AP moves to Registered APs list.

f) Disconnect and then reconnect the AP to the network.

g) Verify that the AP is associated to the correct APC and has its IP address set correctly.

10. Change the names of installed APs and Remote Antennas from their default

values to meaningful, user-friendly names. (

page 3-41

)

11. Run the Philips Upgrade Wizard again to verify that the APCs and APs have the

same firmware revision and proper configuration settings. (

page 3-42

)

12. Export the ITS configuration to a disk file for archive purposes. (

page 3-50

)

13. Restore your service PC to its original settings. (

page 3-52

)

14. Enter the ITS infrastructure devices into the Database Server/Standalone

IntelliVue Information Center configuration wizard, and then bring the ITS

bedside monitors and patient-worn transceivers online. (

page 3-52

)

IntelliVue Telemetry System Infrastructure Installation and Service Guide 3 3

MOSE225

Chapter 3: Installing and Configuring the ITS

Step 1. Complete the ITS Installation Worksheets.

Photocopy and complete the following ITS installation worksheets provided in

Chapter 2 prior to installing any components:

• “ITS Infrastructure Equipment Summary Table” on page 2-27

• “ITS Access Point Equipment Summary Table” on page 2-27

• “APC Configuration Worksheet” on page 2-30

• “1.4 GHz Default AP Configuration Worksheet” on page 2-33

• “2.4 GHz Default AP Configuration Worksheet” on page 2-34

• “AP Group Configuration Worksheet” on page 2-36

Step 2. Install the ITS Infrastructure Components.

Figure 3-1 shows the suggested order when rack-mounting ITS infrastructure components.

UPS

ITS APC

Network Switch

ITS Power over Ethernet Unit

ITS Sync Unit

Patch Panel

Figure 3-1: Rack-mounting the ITS Infrastructure Components

Note It is extremely important that you power and interconnect the ITS components only in the prescribed order. Do not power up an ITS component or connect it to the network until instructed to do so.

To install, power, and verify operation of the 1.4/2.4 GHz IntelliVue Telemetry

System Infrastructure components:

1. Referring to Figure 3-1, mount the ITS infrastructure components in a standard

19-inch equipment rack:

• Mount the ITS Access Point Controller above the ICN Network Switch.

• Mount the ITS Power over Ethernet unit beneath the ICN Network Switch.

• Mount the ITS Synchronization Unit beneath the ITS Power over Ethernet

Unit and above the UPS.

3-4

MOSE225

Step 2. Install the ITS Infrastructure Components.

2. Mount the 1.4/2.4 GHz ITS Smart-hopping Access Points and Remote Antennas within the clinic where they can communicate with patient-worn transceivers and wireless bedside monitors. Note these guidelines when installing the ITS access points:

• You may mount each ITS Access Point above or below a suspended ceiling, or to a wall. Refer to the

1.4 GHz Smart-hopping Access Point Installation

Guide, 2.4 GHz Smart-hopping Access Point Installation Guide

, or

1.4 GHz

Core Access Point/Remote Antenna Installation Guide

for detailed installation procedures.

• Use category 5 (or better) Unshielded Twisted Pair cable to connect each ITS

Access Point to the ITS.

• The total length of UTP cable from the ITS access point-to the ITS

Synchronization Unit-to the ITS Power over Ethernet Unit-to ICN Network

Switch cannot exceed 328 ft. (100 m).

• Install 2.4 GHz ITS APs a minimum of six feet (1.8 m) away from 802.11 APs.

3. If you have installed Core APs and Remote Antennas, connect the Core APs to their RAs now using the provided 74-ft. UTP-and-Coaxial cable bundles.

Caution Do not kink the RA Coax-and-UTP-cable-bundle during installation. You must maintain a minimum 2.5-inch (64-mm) bend radius for the RA Coax-and-UTP-cablebundle throughout the installation.

a) Connect the first Remote Antenna to the Core AP using the UTP and Coaxial cable connectors labeled RA 1 in Figure 3-2.

b) Connect the second Remote Antenna to the Core AP using the UTP and

Coaxial cable connectors labeled RA 2 in Figure 3-2.

c) Be sure to label the UTP cable bundles and the Remote Antennas themselves as RA 1 and RA 2 corresponding to the cable connections you made in steps a and b.

Link LED

Activity LED

ITS Core Access Point

Coaxial Cable Connectors to Remote Antennas (2 & 1)

RA 2 RA 1

RA 2

Ethernet Interface to

ITS Sync Unit

Connection LED

(Green)

Power/Sync, Radio,

Serial Port and Network

Status LEDs

ITS Remote Antenna

RA 1

UTP Cable Connectors to Remote Antennas (2 & 1) with RA Status LEDs

Power LED

(Yellow)

UTP Cable Connector to ITS Core AP

Coaxial Cable Connector to ITS Core Access Point

Figure 3-2: 1.4 GHz ITS Core AP and Remote Antenna Controls and Connectors

IntelliVue Telemetry System Infrastructure Installation and Service Guide 3 5

MOSE225

Chapter 3: Installing and Configuring the ITS

4. Route a Category 5 UTP cable between each ITS Access Point and the equipment closet in which the ITS infrastructure devices are installed. Be sure to install a ferrite block within 20 inches (50 cm) of the RJ-45 connector that connects to the Standard or Core Access Point as shown in Figure 3-3

.

ITS Access Point

Distance = less than

20 inches (50cm)

Figure 3-3: Installing a Ferrite Block on the ITS AP UTP Cable

Connect the routed Category 5 UTP cables to the Access Points, but do not connect these cables to the ITS network yet. The Access Points are the last devices to be connected to the ITS network.

For Standard APs, be sure the AP’s Ethernet DIP switch settings are set as shown in Figure 3-3.

5. Connect the Uninterruptible Power Supply (UPS) to an AC power source.

6. Connect and power the ITS Power over Ethernet Unit.

a) For each 1.4/2.4 GHz Access Point you have installed, connect a Category 5

UTP patch cable between a Data Port on the PoE Unit and an available port on the ICN Network Switch.

b) Connect the ITS PoE Unit power cord to an available power outlet on the back of the UPS.

c) Verify that ITS Power over Ethernet (PoE) Unit powers up properly and that its power indicator lights green.

Figure 3-4 shows cable connections between the ITS Power over Ethernet

(PoE) Unit and the ICN Network Switch to support connection of two 1.4/2.4

GHz Smart-hopping Access Points.

7. Connect and power the ITS Synchronization Unit.

a) Verify that for the Master ITS Synchronization Unit, the Master/Slave toggle switch is set to Master.

All other Sync Units in the network should have the Master/Slave toggle switch is set to Slave. All Slave Sync units should have their front-panel

Cable Delay Switch set as described in Table 2-6.

3-6

MOSE225

Step 2. Install the ITS Infrastructure Components.

ICN Network Switch

24 1 2

1 2 3 4 5 6

Data & Power Ports (To APs)

Data Ports (To ICN Network Switch)

ITS Power over Ethernet Unit

Figure 3-4: ITS PoE Unit to ICN Network Switch Cable Connections

b) For each 1.4/2.4 Access Point you have installed, connect a Category 5 UTP patch cable between a Data & Power Port on the PoE Unit and a From Hub

Port (i.e., top connectors) on the ITS Synchronization Unit.

c) Connect the ITS Synchronization Unit power cord to an available power outlet on the back of the UPS.

d) Verify that the ITS Synchronization Unit powers up properly and that its power indicator lights green.

Figure 3-5 shows cable connections between the ITS Power over Ethernet Unit and the ITS Synchronization Unit to support connection of two 1.4/2.4 GHz

Smart-hopping Access Points.

ICN Network Switch

1 2 24

1 2 3 4 5 6

1 2 3 4 5 6

Data & Power Ports (To APs)

Data Ports (To ICN Network Switch)

ITS Power over Ethernet Unit

1 2 3 4 5 6

1 2 3 4 5 6

- From Power Hub (PoE Unit)

- From Access Points

ITS Synchronization Unit

Master/Slave

Figure 3-5: ITS PoE Unit to ITS Synchronization Unit Cable Connections

IntelliVue Telemetry System Infrastructure Installation and Service Guide 3 7

MOSE225

Chapter 3: Installing and Configuring the ITS

Step 3. Set Up Your Service PC.

To prepare your service PC to configure the APCs, you must:

• Configure your PC to connect to the ITS Wireless Subnet.

• Copy the Philips Upgrade Wizard tool and the latest ITS APC and AP firmware files to your PC from the Philips Network Infrastructure Tools CD-ROM.

Configuring Your PC to Connect to the ITS Wireless Subnet

To configure your PC to connect to the ITS wireless subnet:

1. Configure your Service PC’s network adapter for 100 Mbs full duplex communications and assign a fixed IP address to your Service PC that falls within the ITS subnet address space: a) Disconnect all network connections from your PC.

b) Select Start/Settings/Network Connections/Local Area Connection from the Windows desktop.

The Local Area Connection Status dialog appears.

c) Click Properties.

The Local Area Connection Properties dialog appears.

d) Click Configure and then click the Advanced tab in the displayed Properties dialog.

3-8

MOSE225

Step 3. Set Up Your Service PC.

The advanced properties for your PC’s network adapter are displayed.

e) Select Speed and Duplex, record the current setting, change the setting to

100Mb Full, and then click OK.

You are returned to the Local Area Connection Properties dialog.

f) Select Internet Protocol (TCP/IP) and then click Properties.

The Internet Protocol Properties dialog appears.

g) Mark the Use the following IP Address radio button, enter the following

Routed or Non-Routed settings, and then click OK:

Non-routed Configuration, where “n” represents the ICN Database Domain

Number:

- IP address - 172.31.(n).4 (.4 to .9 are available for Service PCs)

- Subnet mask - 255.255.248.0

- Default gateway - 172.31.(n+3).0 (IP address of DBS or M3150 IIC)

Routed Configuration

- IP address - 172.31.240.4 (.4 to .9 are available for Service PCs)

- Subnet mask - 255.255.240.0

- Default gateway - 172.31.240.1

h) Click OK at each open dialog to close the dialogs and save the Local Area

Connection settings.

2. Connect the Service PC to the ITS wireless subnet.

IntelliVue Telemetry System Infrastructure Installation and Service Guide 3 9

MOSE225

Chapter 3: Installing and Configuring the ITS

Copying the Upgrade Wizard Files to Your PC

Note the following requirements for the PC on which you are running the Upgrade

Wizard:

• The Upgrade Wizard relies on proper network communications between the

Support PC on which the Upgrade Wizard is run and the ITS infrastructure. Verify that there are proper connections between the Upgraded host PC and the installed APCs by running the ping command to ping all installed APCs.

• Verify that non-essential network programs are not running on the Upgrade

Wizard host PC (e.g., network anti-virus, firewalls, etc.). The Upgrade Wizard uses TFTP which can be blocked by such non-essential network programs.

To install the Philips Upgrade Wizard, and ITS AP and APC firmware files on the service PC that will connect to the ITS subnet:

1. Place the Network Infrastructure Tools CD in the PC’s CD ROM drive.

2. Create a folder called

\Telemetry Upgrader

on a local drive on your service PC in which to store the Upgrade Wizard application, and APC and AP firmware files. For example, create the file:

C:\Telemetry Upgrader\

3. Copy the entire contents of the

D:\TOOLS\PHILIPS AP AND APC UPGRADER TOOL\ folder on the Network Infrastructure Tools CD to the

C:\Telemetry Upgrader\ folder on your service PC.

After you have copied over the Upgrade Wizard executable, and APC and AP firmware file folders, the directory structure for the

C:\Telemetry Upgrader

folder on your service PC will look similar to that shown in Figure 3-6.

3-10

Figure 3-6: Sample Service PC Directory Structure for the Philips Upgrade Wizard

Note the following firmware file naming conventions for files stored within the

AP & APC IMAGES

folders:

• Legacy 1.4 GHz Standard AP (P/N 862113) firmware files are named:

WMTS_AP.IMG

.

• Legacy 1.4 GHz Core AP (P/N 862228) firmware files are named:

WMTS_CLAP.IMG

.

MOSE225

Step 3. Set Up Your Service PC.

• New 1.4 GHz Core AP (P/N 989803171211) firmware files are named:

WMTS_AP_RH.IMG

• Legacy 2.4 GHz AP (P/N 862232) firmware files are named:

ROW_AP.IMG

.

• New 2.4 GHz AP (P/N 989803171221) firmware files are named:

ROW_AP_RH.IMG

.

• Legacy APC (P/N 862147) firmware files are named:

WMTS_APC.IMG

.

• New APC (P/N 865346) firmware files are named:

WMTS_APC_RH.IMG

.

Note that the AP and APC firmware files contained within the individual APC and

AP firmware file folders on the Network Infrastructure Tools CD-ROM have been verified as compatible with each other. For this reason, copy only over firmware folders to your service PC. Do not copy over individual firmware files.

4. Disable the proxy settings in the Internet Explorer prior to running and using the

Upgrade Wizard: a) Run Internet Explorer on the service PC connected to the ITS subnet.

b) Select Tools>Internet Options>Connections and then click LAN settings.

The Local Area Network Settings dialog (Figure 3-7) appears.

Figure 3-7: Disabling the Internet Explorer Proxy Settings

c) Uncheck all options listed on the dialog screen.

IntelliVue Telemetry System Infrastructure Installation and Service Guide 3 11

MOSE225

Chapter 3: Installing and Configuring the ITS

Step 4. Perform Initial Configuration of the APCs to be Installed.

The Access Point Controllers are shipped from Philips in a factory default state. Prior to operation on a network, each APC must have the following parameters configured via its serial port interface:

• Static IP address

• Static Subnet Mask

• Static Default Gateway

• Set APC to control 1.4 GHz or 2.4 GHz Access Points

This initial configuration procedure is detailed below. All other configuration settings of the IntelliVue Telemetry System are configured via the APC web-accessed management screens.

The default configuration for an APC is:

• IP Address - 172.31.1.0

• Subnet Mask - 255.255.248.0

• Gateway - 172.31.3.0

• AP Type - 1.4GHz Smart Hopping

Refer to your completed APC configuration worksheet (page 2-30) for your planned

and documented APC configurations. Repeat this initial configuration procedure for each APC to be installed and connected to the ITS wireless subnet.

Note All Static IP address assignments for Access Point Controllers must be unique within the system. If two or more Access Point Controllers are configured with the same IP address, system behavior is unpredictable and unspecified.

To perform initial configuration of an Access Point Controller:

1. Connect a serial cable between COM1: on your service PC and the APC serial interface port.

2. Connect a power cable to the APC and power up the APC.

3. Select Start/Programs/Accessories/Communications/Hyperterminal to open a

HyperTerminal session on your computer.

4. Set up HyperTerminal: a) Enter a name for the New Connection.

b) Select COM1 from the Connect Using drop-down menu, and then click OK.

c) Set the serial port settings as follows:

- Bits per second: 115200

- Data bits: 8

- Parity: None

- Stop bits: 1

- Flow Control: None d) Click OK.

5. Press Enter twice on the PC.

3-12

MOSE225

Step 4. Perform Initial Configuration of the APCs to be Installed.

The APC serial interface Main Menu (Figure 3-8) appears:

Check Firmware

Version

Figure 3-8: APC Serial Interface Main Menu

6. Check the APC firmware version displayed on the APC serial interface Main

Menu and verify that the APC is running the correct firmware.

If the APC is not running the correct version firmware, then: a) Enter 1 at the main menu to change the Static TCP/IP Settings.

Enter the APC IP Address, Static Subnet Mask, and Default Gateway settings, and then press Esc to return to the main menu.

b) End the HyperTerminal session and disconnect the serial cable from the PC and APC.

c) Verify that you have configured your service PC with an IP address (see

page 3-8) that will enable it to communicate directly with the APC.

d) Connect a CAT-5 crossover cable from your service PC directly to the

Ethernet In port on the back of the APC.

e) Run the Philips Upgrade Wizard (see page 3-16) on your service PC to load

the correct version firmware onto the APC.

f) Close the Upgrade Wizard and disconnect the CAT-5 crossover cable from your service PC and the APC.

g) Repeat “Step 4. Perform Initial Configuration of the APCs to be Installed.” on page 3-12 from the beginning.

7. Enter 8 to reset the APC to its factory default settings.

You are prompted to confirm the APC reset.

Press 1 to confirm the rest of the APC to its default values.

The APC will reboot after its factory defaults have been set. During the reboot, the APC LED will change from amber to green.

The main menu displayed after the APC reboot completes should have nine selections. If only eight are listed, then press Esc on your PC until you see nine selections.

8. Enter 1 at the main menu to change the Static TCP/IP Settings.

IntelliVue Telemetry System Infrastructure Installation and Service Guide 3 13

MOSE225

Chapter 3: Installing and Configuring the ITS

Enter the APC IP Address, Static Subnet Mask, and Default Gateway settings, and then press Esc to return to the main menu.

9. Enter 4 at the main menu to access the advanced configuration settings.

a) Enter 4 at the displayed submenu to set the System Type.

b) Enter 1 to set the System Type to 1.4 GHz Smart-hopping, or enter 2 to set the System Type to 2.4 GHz Smart-Hopping.

c) Press Esc twice to return to the main menu.

10. End the HyperTerminal session and disconnect the serial cable from the PC and

APC.

11. Power off the APC.

We suggest labeling each APC that has been configured with its configured IP address and the name you will configure for it via the APC web interface.

Repeat this initial configuration procedure for each APC to be installed and connected to the ITS wireless subnet.

Step 5. Add the APCs to the Network.

Once you have performed the initial configuration procedure on all of the Access

Point Controllers to configure their static IP address and system type (1.4 GHz or

2.4 GHz) settings, it is now time to add the first APC to the network.

At this point, we assume that you have already configured the network switches and have identified each port on each switch to which the Access Point Controllers will be connected.

Note All switch ports to which the APCs are connected must be configured for 100 Mbps

Full Duplex communications.

Initially, only one APC is added to the network, and then this APC is configured. Do not add additional Access Point Controllers to the network until instructed to do so.

You should power off all APCs before beginning the procedure below.

Note Follow the procedure given below only when adding APCs to a new ITS installation. If

you are adding an APC to an existing ITS then refer to “Adding APCs to an Existing

ITS” on page 4-20. If you are replacing an APC in an existing ITS then refer to

“Replacing an ITS APC” on page 4-33.

To add Access Point Controllers to the wireless subnet:

1. Identify the port on the network switch to which you will connect the first APC to be added to the network.

Again, the switch port must be configured for 100 Mbps Full Duplex communications.

2. Connect a Category 5 network cable between the switch port and the APC.

3. Power on the APC.

3-14

MOSE225

Step 5. Add the APCs to the Network.

Verify that the APC power LED turns Green after its self-test (during which the

LED is amber). This APC (i.e., the first installed APC) will become the Master APC within the system.

4. Connect to the APC web-based management interface.

a) Connect your service PC to a network switch on the ITS wireless subnet.

b) Open a web browser on the PC.

c) Enter the static IP address of the APC in the URL field of the browser.

The APC web interface appears.

Not Used

Newly Added

APC

Figure 3-9: APC Web Interface

In the View Devices navigational tree, under System\AP Controllers, observe that the APC you just added to the network is listed and identified with the nomenclature APC-<mac address>.

Note that the UPGRADE button that appears in APC management screens is not used.

Note The APCs will appear in the APC web interface with the System ID of Philips. Do not modify this setting.

5. Select the APC in the View Device tree (selected device is displayed green) and then select the Configure tab.

In the AP Controller Network Configuration screen, configure the following parameters as necessary:

• System ID - Verify setting is Philips. If not, change it to Philips.

• AP Controller Name - Enter APC Name from APC worksheet (page 2-30).

IntelliVue Telemetry System Infrastructure Installation and Service Guide 3 15

MOSE225

Chapter 3: Installing and Configuring the ITS

• IP Addressing - Verify that the Specify IP radio button is marked and that the

IP Address, Subnet Mask and Default Gateway settings are as expected per

APC worksheet (page 2-30). If not, change the settings to match the

worksheet.

6. Click SAVE, and then verify the settings by selecting the Status tab.

7. At this time, add all other APCs to the network by repeating steps 1, 2, 3, 5, and

6 for each APC.

Step 6. Run the Philips Upgrade Wizard.

Run the Philips Upgrade Wizard to check and verify the APCs you added to the network are running the same version firmware. If any configuration modifications are made, run the Philips Upgrade Wizard again.

The Philips Upgrade Wizard has been designed to automate and simplify the upgrade process for ITS APC and APs. In addition to upgrading the firmware on these ITS components, you can use the wizard to:

• verify that APCs on your network are configured correctly

• display warning and error messages that you may use to troubleshoot any configuration errors that may exist on your ITS network

Compatibility

The Philips Upgrade Wizard requires supported, and compatible AP and APC firmware. Note the compatibility requirements listed in Table 3-1.

Caution Use of Versions A.00.19 and older of the Upgrade Wizard must be discontinued.

Upgrade

Wizard Version

(A.00.21)

(A.00.20)

(A.00.19)

(A.00.16)

(A.00.08)

(A.00.07)

(A.00.0X)

APC (C.00.04)

Compatible

Compatible

Not Compatible

Not Compatible

Not Compatible

Warning: May

Cause AP Fault

Not Compatible

Warning: May

Cause AP Fault

Not Compatible

Warning: May

Cause AP Fault

Table 3-1: Upgrade Wizard and APC Compatibility

APC (B.00.19)

Compatible

Compatible

Compatible

Not Compatible

Not Compatible

Warning: May

Cause AP Fault

Not Compatible

Warning: May

Cause AP Fault

Not Compatible

Warning: May

Cause AP Fault

APC (B.00.15) APC (A.00.34) APC (A.00.32) APC (A.00.29)

Compatible

Compatible

Compatible

Compatible

Not Compatible

Warning: May

Cause AP Fault

Not Compatible

Warning: May

Cause AP Fault

Not Compatible

Warning: May

Cause AP Fault

Compatible

Compatible

Compatible

Compatible

Compatible

Not Compatible

Not Compatible

Compatible

Compatible

Compatible

Compatible

Compatible

Compatible

Compatible

Compatible

Compatible

Compatible

Compatible

Compatible

Not Compatible Compatible

3-16

MOSE225

Step 6. Run the Philips Upgrade Wizard.

Also note the compatibility between versions of AP and APC firmware listed in

Table 3-2.

Table 3-2: AP and APC Firmware Compatibility

ITS APC Firmware Version

ITS AP Firmware

Version

2.4 GHz AP (C.00.04)

Legacy 2.4 GHz AP

(B.00.12)

Legacy 2.4 GHz AP

(B.00.07)

1.4 GHz Core AP (C.00.03)

Legacy 1.4 GHz Core AP

(A.00.26)

Legacy 1.4 GHz Core AP

(A.00.27)

Legacy 1.4 GHz Core AP

(A.00.23)

Legacy 1.4 GHz Std. AP

(A.00.66)

Legacy 1.4 GHz Std. AP

(A.00.54)

Legacy 1.4 GHz Std. AP

(A.00.52)

Legacy 1.4 GHz Std. AP

(A.00.50)

C.00.04

Compatible

Compatible

Not Compatible

Compatible

Compatible

Compatible

Not Compatible

Compatible

Not Compatible

Not Compatible

Not Compatible

B.00.19

Compatible

Compatible

Not Compatible

Compatible

Compatible

Compatible

Not Compatible

Compatible

Not Compatible

Not Compatible

Not Compatible

B.00.15

Not Compatible

Not Compatible

Compatible

Compatible

Compatible

Compatible

Compatible

Not Compatible

Compatible

Not Compatible

Not Compatible

A.00.34

Not Compatible

Not Compatible

Not Compatible

Compatible

Compatible

Compatible

Compatible

Not Compatible

Compatible

Not Compatible

Not Compatible

A.00.32

Not Compatible

Not Compatible

Not Compatible

Not Compatible

Not Compatible

Not Compatible

Not Compatible

Not Compatible

Not Compatible

Compatible

Not Compatible

Using the Upgrade Wizard

Caution Close the APC web interface before running the Philips Upgrade Wizard. Do not add components to or remove components from the IntelliVue Telemetry System while the wizard is running.

Do not run the Philips Upgrade Wizard on a computer with a browser open.

Follow these steps to upgrade ITS Access Point Controllers and Access Points using the Philips Upgrade Wizard:

Philips Upgrade Wizard:

1. Run the Philips Upgrade Wizard by double-clicking the file:

C:\Telemetry Upgrader\upgrader.exe

The Upgrade Wizard splash screen (Figure 3-10) appears.

2. Click Next> to continue.

The APC/AP firmware selection screen (Figure 3-11) appears.

3. Complete the settings on the APC/AP firmware selection screen:

IntelliVue Telemetry System Infrastructure Installation and Service Guide 3 17

MOSE225

Chapter 3: Installing and Configuring the ITS

Figure 3-10: Upgrade Wizard Splash Screen

a) Click ... and then browse to the directory (e.g.,

C:\Telemetry Upgrader\AP and APC Images\

) in which you have installed the APC and AP image files.

b) Specify what type of APs you have installed by marking the appropriate radio button, 1.4 GHz Smart Hopping or 2.4 GHz Smart Hopping.

c) Verify that the correct firmware versions are displayed in the APC Version,

AP Version (Standard), and AP Version (Cluster) fields.

3-18

Figure 3-11: APC/AP Firmware Selection Screen

Note that the firmware files listed in the Version fields correspond to the files stored within the directory listed in the Folder field. If valid device firmware files are not found within the specified directory, you cannot proceed.

d) Select the ICN IP address (e.g., 172.31.240.4) you have configured for the support PC on which you are running the wizard from the Use IP Address

MOSE225

Step 6. Run the Philips Upgrade Wizard.

drop-down menu. The menu lists the IP addresses of all Ethernet NICs configured on the PC.

e) Select Upgrade if necessary from the APC drop-down menu to allow each

APC to be upgraded. By default, an APC will not be upgraded if it is already at the selected firmware version.

f) Select Ignore Configuration from the unlabeled drop-down menu to ignore the APC configuration the first time you run the Upgrade Wizard.

g) Select Do Not Upgrade from the AP drop-down as you have only installed

APCs on the ITS at this point.

h) Do not mark the Export Configuration? checkbox.

You will not export the ITS configuration until later in this procedure.

4. Click Next> to continue.

The wizard automatically scans the IntelliVue Telemetry System for all connected APCs. When the scan is completed (Figure 3-13), the following message appears:

System [Philips] – Master APC [e.g., APC-02*] Complete (Config Key = C000532B)

* Note that the displayed APC name will be different for each clinical site.

IntelliVue Telemetry System Infrastructure Installation and Service Guide 3 19

MOSE225

Chapter 3: Installing and Configuring the ITS

Note After scanning the ITS for connected APCs, the Upgrade Wizard will list any APCs that have an incompatible configuration key (Figure 3-12). If such an APC is found, you cannot continue the upgrade process. Locate the incompatible APC, disconnect it from the ITS, reset it to its factory defaults, and then reconnect it to the ITS before retrying the upgrade process.

For APC firmware Revision B.00.15 (or lower) the displayed Configuration Key must be in the range 00 00 0000 to FF 00 0000 (hex). If the displayed Configuration Key value exceeds FF 00 0000, then you must discontinue the installation/upgrade procedure, and upgrade the APC to Revision B.00.19 (or higher) firmware.

Figure 3-12: Incompatible APC Configuration Key Screen

3-20

Figure 3-13: APC Scan Completion Screen

MOSE225

Step 6. Run the Philips Upgrade Wizard.

5. Highlight/select the displayed message, e.g., System [Philips] – Master APC

[APC3E] Complete and then click Next> to continue.

The wizard scans the IntelliVue Telemetry System for all connected APs.

The scan may take several minutes to complete. When the scan is completed, the message Finished System scan appears and the Next button becomes active.

6. Click Next> to continue.

The APCs are queried, and a full navigational tree of the ITS is built and displayed.

The tree lists the current firmware revision installed on each APC found in the

ITS.

Items needing an upgrade are shown in bold. If an AP needs an upgrade, the

APC it is connected to will also be shown in bold, even if that APC itself does not require upgrading.

7. Select one APC (i.e., top level APC structure) at a time to upgrade. For example, select APC [APC-C3] Version [A.00.29] and then select Next>.

The selected APC is taken offline, and the message Taking APC Offline is displayed.

8. Click Next> to continue.

The APC upgrade process begins. The upgrade process may take several

minutes to complete. Status messages are displayed (Figure 3-14) as the

process runs.

Figure 3-14: APC Upgrade Process Status Messages

The message Finished Upgrading APC appears when the upgrade process is complete.

9. Click Next> to continue.

IntelliVue Telemetry System Infrastructure Installation and Service Guide 3 21

MOSE225

Chapter 3: Installing and Configuring the ITS

10. After all APCs have been upgraded, the Upgrade Wizard Report (Figure 3-15) is

displayed.

The report provides a summary of all devices upgraded along with any errors that may have been generated during the upgrade process.

Figure 3-15: Upgrade Wizard Report

Click Save to save the report to a disk file (recommended).

Click Print to print the report without saving it.

Click Finish to close the Upgrade Wizard program.

Note that the Upgrade Wizard automatically creates a log file, logfile.txt, in the directory from which it was run. Rename this log file and save it together with the

Upgrade Wizard Report disk file in another directory.

After saving the Upgrade Wizard Report to a disk file, you should the open the text file in Notepad and execute a find for the strings “error” and “warning.” All errors must be corrected and all warnings be reviewed. See Appendix C for descriptions of possible error and warning messages.

Step 7. Verify and Configure Important ITS Settings via the APC Interface.

After adding the remaining Access Point Controllers to the wireless subnet, several important ITS settings must be verified and configured via the APC web interface to ensure proper operation of the system. These include:

• Verify Filter Settings

• Verify BootP Address Ranges

• Configure the AP Defaults (for 1.4 GHz or 2.4 GHz APs)

• Configure AP Groups

• Configure Basic Settings for each Group

• Configure Alerts for each Group

3-22

MOSE225

Step 7. Verify and Configure Important ITS Settings via the APC Interface.

Verifying the Filter Settings

To verify the network filter settings:

1. In View Device tree, select System and then select the Filters tab.

The Filter Configuration screen (Figure 3-16) appears.

Figure 3-16: APC Filter Configuration Screen

2. Verify that the following network filter settings are configured as follows:

Protocol Type Filters:

• IP/ARP - UNCHECKED

• All others - CHECKED

Multicast Address Filter:

• Enable Multicast Filter - CHECKED

• Multicast Address - 01:00:5E:00:00:00

• Multicast Mask - ff:ff:ff:ff:ff:ff

IntelliVue Telemetry System Infrastructure Installation and Service Guide 3 23

MOSE225

Chapter 3: Installing and Configuring the ITS

ARP Filter:

• Enable ARP Filter - UNCHECKED

• Network IP Address - 0.0.0.0 (N/A)

- Network Subnet Mask - 0.0.0.0 (N/A)

IPX Broadcast Filters:

• All filters - CHECKED

• Broadcast Bandwidth Allocation - 20%

3. If you made any changes to the Network filter settings, click SAVE and then verify the results.

Verifying the BOOTP/DHCP Settings

Warning If you have upgraded the firmware on an APC from version A.00.NN to B.00.NN, the

BOOTP/DHCP settings previously configured using version A.00.NN may be displayed/configured improperly under version B.00.NN. For example, routed table entries may be displayed in the non-routed table, and vice-versa. After upgrading an

APC from firmware version A.00.NN to B.00.NN, be sure to verify and if necessary, correct the BOOTP/DHCP table entries listed in the APC web interface.

To verify the BOOTP/DHCP server settings:

1. In View Device tree, select System and then select the BOOTP/DHCP tab.

The BOOTP/DHCP Server Configuration screen (Figure 3-17) appears.

2. Verify the settings for Range 1 and Range 2 are as follows for IP address ranges for routed and for non-routed systems. Set as documented in your APC

Configuration Worksheet (page 2-30). Typically, any changes to the IP address

scheme are made to the following fields:

• IP address range minimum

• IP address range maximum

• Subnet mask

• Default gateway

Non-Routed Range 1 - Transceivers and Wireless Bedsides

• Enabled - CHECKED for non-routed ITS, UNCHECKED for routed ITS

• MAC address Base - 00:09:fb:06:00:00

• MAC address Mask - ff:ff:ff:0f:00:00

• IP address range minimum - 172.31.(n + 6).0

• IP address range maximum - 172.31.(n + 6).255

• Subnet mask - 255.255.248.0

• Default gateway - 172.31. (n + 3).0

• DNS server IP address - 0.0.0.0

3-24

MOSE225

Step 7. Verify and Configure Important ITS Settings via the APC Interface.

Figure 3-17: BOOTP/DHCP Server Configuration Screen

IntelliVue Telemetry System Infrastructure Installation and Service Guide 3 25

MOSE225

Chapter 3: Installing and Configuring the ITS

Non-Routed Range 2 - Access Points

• Enabled - CHECKED for non-routed ITS, UNCHECKED for routed ITS

• MAC address Base - 00:09:fb:05:00:00

• MAC address Mask - ff:ff:ff:0f:00:00

• IP address range minimum - 172.31.(n + 2).128

• IP address range maximum - 172.31.(n + 2).255

• Subnet mask - 255.255.248.0

• Default gateway - 172.31. (n + 3).0

• DNS server IP address - 0.0.0.0

Routed Range 1 - Transceivers and Wireless Bedsides

• Enabled - CHECKED for routed ITS, UNCHECKED for non-routed ITS

• MAC address Base - 00:09:fb:06:00:00

• MAC address Mask - ff:ff:ff:0f:00:00

• IP address range minimum - 172.31.248.0

• IP address range maximum - 172.31.253.255

• Subnet mask - 255.255.240.0

• Default gateway - 172.31.240.1

• DNS server IP address - 0.0.0.0

Routed Range 2 - Access Points

• Enabled - CHECKED for routed ITS, UNCHECKED for non-routed ITS

• MAC address Base - 00:09:fb:05:00:00

• MAC address Mask - ff:ff:ff:0f:00:00

• IP address range minimum - 172.31.244.128

• IP address range maximum - 172.31.246.255

• Subnet mask - 255.255.240.0

• Default gateway - 172.31.240.1

• DNS server IP address - 0.0.0.0

Range 5

• Enabled - UNCHECKED (always)

3. If you made any changes to the settings, click SAVE and then verify the results.

3-26

MOSE225

Step 7. Verify and Configure Important ITS Settings via the APC Interface.

Configuring the

1.4 GHz Access

Point Default

Settings

Configuring the Access Point Default Settings

You must configure the default Access Point settings for the APs installed at your site, either:

• 1.4 GHz Access Points

• 2.4 GHz Access Points

The next step is to configure the 1.4 GHz Access Point default settings for this installation. Refer to the information you documented on the 1.4 GHz Access Point

Default Configuration Worksheet (page 2-33) during this step.

The default AP settings you configure here are global settings that will become the base configuration for all 1.4 GHz AP Groups you establish in the next step (refer to

“Configuring AP Groups” on page 3-30).

To configure the 1.4 GHz Smart Hopping Access Point default settings:

1. From within View Device tree, browse to the AP Basic Defaults screen under

System/Access Point Defaults/1.4 GHz Smart Hopping AP Defaults.

Verify that You are

Configuring the AP Defaults

Figure 3-18: 1.4 GHz Smart Hopping AP Defaults Configuration Screen

2. Set the Partnered AP Controller drop down list to “ANY.”

3. Set the Default Group drop-down list to Smart-hopping.

4. Set the WMTS Channels as appropriate for your geography and as documented in the 1.4 GHz Access Point Default Configuration Worksheet.

The FCC requires that all WMTS transmitters be registered with the American

Society for Healthcare Engineering (ASHE). Therefore, to be in compliance with

FCC regulations, you must register your intended WMTS channel usage with

IntelliVue Telemetry System Infrastructure Installation and Service Guide 3 27

MOSE225

Chapter 3: Installing and Configuring the ITS

ASHE prior to ITS deployment. See “Required FCC Registration” on page 1-17 for

details.

Caution If you mark the Special Geographic Area radio button when installing the 1.4 GHz

ITS in a “carved-out area,” then you must leave channels 4, 5, and 6 unchecked.

Checking channels 4, 5, or 6 with the Special Geographic Area radio button marked results in an invalid configuration that may cause APs to continually reboot.

Configuring the

2.4 GHz Access

Point Default

Settings

5. Set the RF Access Code field as documented in the 1.4 GHz Access Point

Default Configuration Worksheet, and set the Enable checkbox to CHECKED.

6. Set the Subnet Mask and Default Gateway fields as documented in the 1.4 GHz

Access Point Default Configuration Worksheet.

7. Click SAVE, and then verify the results to your expected settings.

The next step is to configure the 2.4 GHz Access Point default settings for this installation. Refer to the information you documented on the 2.4 GHz Access Point

Default Configuration Worksheet (page 2-34) during this step.

The default AP settings you configure here are global settings that will become the base configuration for all 2.4 GHz AP Groups you establish in the next step (refer to

“Configuring AP Groups” on page 3-30).

To configure the 2.4 GHz Smart Hopping Access Point default settings:

1. From within View Device tree, browse to the AP Basic Defaults screen under

System/Access Point Defaults/2.4 GHz Smart Hopping AP Defaults.

Verify that You are

Configuring the AP Defaults

3-28

Figure 3-19: 2.4 GHz Smart Hopping AP Defaults Configuration Screen

2. Set the Partnered AP Controller drop-down list to “ANY.”

MOSE225

Step 7. Verify and Configure Important ITS Settings via the APC Interface.

3. Set the Default Group drop-down list to Smart-hopping.

4. Select the Radio Regulations from the drop-down list that apply to the country in which you are installing the 2.4 GHz ITS. Possible Radio Regulation choices are:

• ETSI - Europe, South America, Asia, Asia Pacific, and Africa

• FCC - United States, Taiwan, Singapore, and Hong Kong

• AS/NZ - Australia/New Zealand

• RSS-210 - Canada/North America

• ARIB - Japan

5. Select the Frequency Plan from the drop-down list to specify the 802.11b/g channel configuration with which the 2.4 GHz ITS will co-exist. Possible

Frequency Plan choices are:

Table 3-3: 2.4 GHz ITS Frequency Plan Settings

2.4 GHz ITS Channels Configured for Use

Frequency Plan

FCC,ARIB,RSS-210

14, 28, 44, 45, 46, 47

1

ETSI, AS/NZ

14, 28, 43, 44, 45, 46 Co-exist with 802.11

Channels 1, 6, 11

Co-exist with 802.11

Channels 1, 7, 13

Advanced

14, 15,16, 31, 32, 33

2

14, 15, 16, 31, 32, 33

2

Any set (min 3, max 6) of 2.4 GHz

ITS channels from 0 - 47, excluding any that have been disabled by the ZigBee selection.

Any set (min 3, max 6) of 2.4 GHz

ITS channels from 1 - 46, excluding any that have been disabled by the ZigBee selection

1

-

If any one of this set of six channels is disabled by the ZigBee channel selection, then channel

43 can be used instead.

2

-

If any one of this set of six channels is disabled by the ZigBee channel selection, then channel

34 can be used instead.

If you select Advanced, then you must click the Click Here link at the bottom of the page to specify a minimum of three and a maximum of six channels for use by the 2.4 GHz ITS.

6. Select the ZigBee channel used for medical purposes at the installation site from the drop-down list. Possible selections are channels 11 to 26.

Default: None.

7. Set the RF Access Code field as documented in the 2.4 GHz Access Point

Default Configuration Worksheet, and set the Enable checkbox to CHECKED.

8. Set the Subnet Mask and Default Gateway fields as documented in the 2.4 GHz

Access Point Default Configuration Worksheet.

9. Click SAVE and then verify the results to your expected settings.

IntelliVue Telemetry System Infrastructure Installation and Service Guide 3 29

MOSE225

Chapter 3: Installing and Configuring the ITS

Configuring AP Groups

The next step in the process involves establishing the AP Groups for your

installation. As described in “Planning Your AP Groupings” on page 2-18, an AP

Group allows for logically associated Access Points within a clinical unit to be given a common set of configurations. These configurations govern everything from AP-to-

APC partnership rules, RF Channel and Access Code usage, and Alert Settings.

The AP Groups within the system should logically map to the Clinical Units that have been established for the monitoring network and databases.

Note Any changes you may later make to the Access Point Group settings on an installed

ITS will cause a momentary pause in monitoring for all patient-worn transceivers and wireless bedside monitors (and some AP Group setting changes may cause a longer break in monitoring).

Refer to the AP Group Configurations Worksheet on page 2-36 when configuring AP

Groups.

Complete the following steps for each AP Group to be created and configured:

1. Select the Groups View in the web interface drop-down menu and then click

GO!.

2. Click ADD GROUP at the bottom left of the screen.

3. In the Add New Group screen (Figure 3-20), configure the following settings:

• Group Name - Set as documented in AP Group Configurations Worksheet

(no spaces in name)

• Group Type - (should be set to Smart-hopping)

• Group Description - Optional. Enter a description for this AP Group. Typically, you may want to enter the name of the clinic, unit, or department in which the APS are installed.

3-30

Figure 3-20: Adding New AP Group

4. Click the ADD GROUP button. Repeat Step 3 for each AP Group being added on this system. When all AP Groups have been added, click the NETWORK button to return to the View Groups tree screen.

MOSE225

Step 7. Verify and Configure Important ITS Settings via the APC Interface.

1.4 GHz AP

Group

Configuration

Basic Settings

2.4 GHz AP

Group

Configuration

Basic Settings

For each AP Group that has been added, complete the follow steps:

5. In the View Groups tree, select an AP Group that was created and select the

BASIC SETTINGS tab.

In the 1.4 GHz AP Group Configuration Basic Settings screen, set the following configuration for this AP Group:

• Select the appropriate APC for this AP group from the Partnered AP

Controller drop-down list. Refer to your completed AP Group Configuration

Worksheet.

In the 1.4 GHz AP Group Configuration Basic Settings screen, verify the following configurations for this AP Group. If they are not correct, delete the AP

group and then edit the AP default settings (see page 3-27):

• Set the WMTS Channels as appropriate for your geography and as documented in the 1.4 GHz Access Point Default Configuration Worksheet.

• Set the RF Access Code field as documented in the 1.4 GHz Access Point

Default Configuration Worksheet, and set the Enable Box to CHECKED.

• Set the Subnet Mask and Default Gateway fields as documented in the 1.4

GHz Access Point Default Configuration Worksheet.

In the 2.4 GHz AP Group Configuration Basic Settings screen, set the following configurations for this AP Group:

• Select the appropriate APC for this AP group from the Partnered AP

Controller drop-down list. Refer to your completed AP Group Configuration

Worksheet.

In the 2.4 GHz AP Group Configuration Basic Settings screen, verify the following configurations for this AP Group. If they are not correct, delete the AP

group and then edit the AP default settings (see page 3-27):

• Select the Radio Regulations from the drop-down list that apply to the country in which you are installing the 2.4 GHz ITS as documented in the

2.4 GHz AP Default Configuration Worksheet.

• Select the Frequency Plan from the drop-down list to specify the 802.11 channel configuration with which the 2.4 GHz ITS will co-exist.

• Select the ZigBee channel used for medical purposes at the installation site from the drop-down list as documented in the 2.4 GHz AP Default

Configuration Worksheet.

• Set the RF Access Code field as documented in the 2.4 GHz Access Point

Default Configuration Worksheet, and set the Enable Box to CHECKED.

• Set the Subnet Mask and Default Gateway fields as documented in the 2.4

GHz Access Point Default Configuration Worksheet.

6. Click SAVE and then verify that the AP Group Basic Configuration settings are correct.

7. Select the ALERTS SETTINGS tab.

In the AP Group Configuration Alerts Settings screen, set the following configurations for this AP Group:

IntelliVue Telemetry System Infrastructure Installation and Service Guide 3 31

Chapter 3: Installing and Configuring the ITS

MOSE225

Figure 3-21: AP Group Configuration Alert Settings

• Alert Destination - Set as documented in the AP Group Configuration

Worksheet.

• Sync Loss Alert - Verify all boxes are CHECKED.

8. Click SAVE and then verify the AP Group Alerts Configuration settings are correct.

9. Select the ALERTS SETTINGS tab again. In the AP Group Configuration Alerts

Settings screen, click on the Click Here link at the bottom of the screen to display the AP Group Configuration Advanced Alerts Settings screen

(Figure 3-22).

The settings in the Advanced Alerts Settings screen will be populated as part of the factory defaults. Verify the correct settings against Figure 3-22.

10. Click SAVE and then verify the AP Group Configuration Advanced Alerts Results page.

11. Repeat Steps 5 - 10 until you have configured every AP group that you have added to the system.

3-32

MOSE225

Step 7. Verify and Configure Important ITS Settings via the APC Interface.

1732

5

Checked

2

Checked

24

Checked

Checked

300

Checked

10

Unchecked

0

Unchecked

Checked

Checked

Checked

Checked

Unchecked

Checked

Checked

Checked

Checked

15

27

30

40

Note that Insufficient Spectrum Alert

Settings are Only Displayed for and Apply to

2.4 GHz Access Points

Figure 3-22: AP Group Configuration Advanced Alert Settings

IntelliVue Telemetry System Infrastructure Installation and Service Guide 3 33

MOSE225

Chapter 3: Installing and Configuring the ITS

Step 8. Run the Philips Upgrade Wizard Again.

Run the Philips Upgrade Wizard to check and verify the APC configurations, and fix any errors as needed. If any configuration modifications are made, run the Philips

Upgrade Wizard again.

The Philips Upgrade Wizard has been designed to automate and simplify the upgrade process for ITS APC and APs. In addition to upgrading the firmware on these ITS components, you can use the wizard to:

• verify that APCs on your network are configured correctly

• display warning and error messages that you may use to troubleshoot any configuration errors that may exist on your ITS network

Follow these steps to upgrade ITS Access Point Controllers and Access Points using the Philips Upgrade Wizard:

Philips Upgrade Wizard:

1. Run the Philips Upgrade Wizard by double-clicking the file:

C:\Telemetry Upgrader\upgrader.exe

The Upgrade Wizard splash screen (Figure 3-23) appears.

3-34

Figure 3-23: Upgrade Wizard Splash Screen

2. Click Next> to continue.

The APC/AP firmware selection screen (Figure 3-24) appears.

3. Complete the settings on the APC/AP firmware selection screen: a) Click ... and then browse to the directory (e.g.,

C:\Telemetry Upgrader\AP and APC Images\) in which you have installed the APC and AP firmware files.

b) Specify what type of APs you have installed by marking the appropriate radio button, 1.4 GHz Smart Hopping or 2.4 GHz Smart Hopping.

Additionally, if you have installed Core APs, then be sure to mark the System includes Cluster APs (with or without Remote Antennas) checkbox.

MOSE225

Step 8. Run the Philips Upgrade Wizard Again.

c) Verify that the correct firmware versions are displayed in the APC Version,

AP Version (Standard), and AP Version (Cluster) fields.

Figure 3-24: APC/AP Firmware Selection Screen

d) Select the ICN IP address (e.g., 172.31.240.4) you have configured for the support PC on which you are running the wizard from the Use IP Address drop-down menu. The menu lists the IP addresses of all Ethernet NICs configured on the PC.

e) Select Upgrade if necessary from the APC drop-down menu to allow each

APC to be upgraded. By default, an APC will not be upgraded if it is already at the selected firmware version.

f) Select Smart Hopping-only Check and Update Configuration from the unlabeled drop-down menu to verify and update the APC configuration.

g) Select Do Not Upgrade from the AP drop-down as you have only installed

APCs on the ITS at this point.

h) Do not mark the Export Configuration? checkbox.

You will not export the ITS configuration until later in this procedure.

4. Click Next> to continue.

The wizard automatically scans the IntelliVue Telemetry System for all

connected APCs. When the scan is completed (Figure 3-25), the following

message appears:

System [Philips] – Master APC [e.g., APC-02*] Complete (Config Key = C000532B)

* Note that the displayed APC value will be different for each clinical site.

IntelliVue Telemetry System Infrastructure Installation and Service Guide 3 35

Chapter 3: Installing and Configuring the ITS

MOSE225

3-36

Figure 3-25: APC Scan Completion Screen

5. Highlight/select the displayed message, e.g., System [Philips] – Master APC

[APC3E] Complete and then click Next> to continue.

The wizard scans the IntelliVue Telemetry System for all connected APs.

When the scan is completed, the following message appears:

Finished System scan

6. Click Next> to continue.

The APCs are queried, and a full navigational tree of the ITS is built and displayed.

The tree lists the current firmware revision installed on each APC found in the

ITS.

Items needing an upgrade are shown in bold. If an AP needs an upgrade, the

APC it is connected to will also be shown in bold, even if that APC itself does not require upgrading.

7. Select one APC (i.e., top level APC structure) at a time to upgrade. For example, select APC [APC-C3] Version [C.00.01] and then select Next>.

The selected APC is taken offline, and the message Taking APC Offline is displayed.

8. Click Next> to continue.

MOSE225

Step 8. Run the Philips Upgrade Wizard Again.

The APC upgrade process begins. The upgrade process may take several minutes to complete. Status messages are displayed (Figure 3-26) as the process runs.

Figure 3-26: APC Upgrade Process Status Messages

The message Finished Upgrading APC appears when the upgrade process is complete.

9. Click Next> to continue.

10. After all APCs have been upgraded, the Upgrade Wizard Report (Figure 3-27) is displayed.

The report provides a summary of all devices upgraded along with any errors that may have been generated during the upgrade process.

Figure 3-27: Upgrade Wizard Report

Click Save to save the report to a disk file (recommended).

IntelliVue Telemetry System Infrastructure Installation and Service Guide 3 37

MOSE225

Chapter 3: Installing and Configuring the ITS

Click Print to print the report without saving it.

Click Finish to close the Upgrade Wizard program.

Note that the Upgrade Wizard automatically creates a log file, logfile.txt, in the directory from which it was run. Rename this log file and save it together with the

Upgrade Wizard Report disk file in another directory.

After saving the Upgrade Wizard Report to a disk file, you should the open the text file in Notepad and execute a find for the strings “error” and “warning.” All errors must be corrected and all warnings be reviewed. See Appendix C for descriptions of possible error and warning messages.

Step 9. Add APs to the Network.

Note We recommend that you add your installed APs to the ITS network in groups of up to

25 APs at a time by following the procedure given in this section. After adding the

APs as described here, complete “Step 10. Rename Installed APs and Remote

Antennas.” on page 3-41 and “Step 11. Run the Philips Upgrade Wizard Again.” on page 3-42 for the newly added APs. Continue to add APs and complete Steps 10

and 11 for the newly added APs until you have added all installed APs to your ITS network.

After you have run the Philips Upgrade Wizard to verify the APC configurations, it is time to add the Access Points to the network. At this point, it is assumed that you have already installed and configured the wired components of the ITS, and you have identified each port on each network switch to which the Access Points will be connected (via the Sync Unit and PoE Unit cable connections to the switch

described starting on page 3-4).

All ports on the network switch to which APs are connected must be configured to

100 Mbps Full Duplex.

Ensure that Core APs are connected to their Remote Antennas when the Core APs are initially added to the ITS.

Upon connection to the network switch and Power over Ethernet Unit, Access Points

(and connected Remote Antennas) will be automatically added to the View Devices tree of the network in the APC management screens. Each Access Point must then be individually configured for proper operation in the system.

Complete the following procedure for each AP to be added to the ITS.

To add an Access Point to the ITS:

1. Re-launch your web browser and reconnect to the APC web interface.

2. Route and connect a network patch cable between the Access Point and the

Sync Unit. (See page 3-4 for illustrations of and instructions for making these

cable connections.)

Wait 60 seconds before proceeding.

3-38

MOSE225

Step 9. Add APs to the Network.

1.4 GHz AP

Configuration

Once power is applied, the Access Point (and Remote Antennas) will take approximately 60 seconds to fully boot and will automatically appear in the View

Devices tree of the APC web interface under any AP Controller.

By default, the Remote Antennas are labeled as AP-1-ID#### (AP-port 1-remote antenna ID) or AP-2-ID#### (AP-port 2-remote antenna ID) where ID#### matches the ID number printed on the Remote Antenna’s device label.

Press F5 to refresh the APC web interface if the AP is not displayed.

If the AP is still not displayed, click System in the View device tree, click

Configure and then select the Advanced tab. Verify that the Allow new APs to be added automatically option is set to True.

3. Find the Access Point and select it in the View Devices tree. It should be named

AP-mac_address and be listed under an APC in the list.

4. In the AP Configuration screen for this Access Point, select the Basic Settings tab and then configure the following settings:

1.4 GHz Smart-Hopping AP Configuration Screen:

Note: You may use the RESET AP button to reboot/ reset a Core AP and its connected

RAs. The RESET AP button does not function with a

Standard 1.4 GHz

AP.

Figure 3-28: 1.4 GHz Smart Hopping AP Configuration Screen

• Set the AP Name as appropriate for this AP.

• Set the Enable AP checkbox to CHECKED.

• Verify that the Partnered AP Controller is set to “ANY.” The Partnered APC will get set correctly based upon the AP’s Group membership setting.

• Set the Group Membership as appropriate for this AP.

• Verify that the WMTS Channels are set as appropriate for your geography.

The WMTS Channels are set in the AP default settings.

• Verify that the RF Access Code is set correctly. The RF Access Code is set in the AP default settings.

IntelliVue Telemetry System Infrastructure Installation and Service Guide 3 39

MOSE225

Chapter 3: Installing and Configuring the ITS

2.4 GHz AP

Configuration

• Set the RF Access Code Enable Box to CHECKED.

• Mark the Use DHCP or Specify IP radio button as appropriate for your network. When specifying the IP address, note that the Subnet Mask and

Default Gateway fields are populated with the default values set in the AP default settings.

2.4 GHz Smart-Hopping AP Configuration Screen:

3-40

Note: You may use the RESET AP button to reboot/ reset a 2.4 GHz

Standard AP.

Figure 3-29: 2.4 GHz Smart Hopping AP Configuration Screen

• Set the AP Name as appropriate for this AP.

• Set the Enable AP checkbox to CHECKED.

• Set the Partnered AP Controller drop-down list to “ANY.” The Partnered APC will get set correctly based upon the AP’s Group membership setting.

• Set the Group Membership as appropriate for this AP.

• Select the Radio Regulations as specified in the 2.4 GHz Default AP

Configuration Worksheet.

• Verify that the Frequency Plan is set correctly for this AP. The Frequency Plan is set as part of the AP default settings.

• Verify that the ZigBee channel used for medical is set correctly for this AP.

The Zigbee Channel is set as part of the AP default settings.

• Verify that the RF Access Code is set correctly. The RF Access Code is set in the AP default settings.

• Set the RF Access Code Enable Box to CHECKED.

• Mark the Use DHCP or Specify IP radio button as appropriate for your network. When specifying the IP address, note that the Subnet Mask and

MOSE225

Step 10. Rename Installed APs and Remote Antennas.

Default Gateway fields are populated with the default values set in the AP default settings.

5. Click SAVE and then verify the AP Configuration settings.

6. Refresh Internet Explorer (by pressing F5), and in the View Devices tree, verify that the AP appears under the correct Access Point Controller.

This may take several minutes and in the process; the Access Point may appear

(for a moment) in the Unregistered List of the View Devices tree. If after five minutes the Access Point remains in the Unregistered List of View Devices tree, select the Access Point in the Unregistered List and click the Delete AP button at the bottom of the page. Remove power to the Access Point and repeat this procedure beginning from Step 1.

7. Disconnect the AP from the Sync Unit, and then reconnect it.

This will recycle power to the AP and enable the AP to load its configuration properly.

8. Click on the STATUS tab for the newly added AP and verify that the IP shown for that AP is correct. If not, remove power to the AP and then check and verify the status again.

9. Repeat the above steps for all other APs to be added to the ITS.

Step 10. Rename Installed APs and Remote Antennas.

You can change the names of installed Standard APs, Core APs, and Remote

Antennas from their default values to more user-friendly names by following these steps:

1. Click on the APC in the APC web interface that is associated with the APs you wish to rename.

2. Click the NAMES tab.

The AP and Remote Antenna Friendly Name Management screen appears as shown in Figure 3-30.

3. Enter meaningful, user-friendly names for the installed Standard APs, Core APs, and Remote Antennas in the AP Name and RA Name fields.

You may enter a string of up to 32 characters for the name values.

Standard APs will list Remote Antennas as Not Present. Core APs will provide general status of connected Remote Antennas.

4. Click SAVE and then verify the AP Configuration settings.

IntelliVue Telemetry System Infrastructure Installation and Service Guide 3 41

Chapter 3: Installing and Configuring the ITS

MOSE225

Figure 3-30: Renaming APs and RAs

Step 11. Run the Philips Upgrade Wizard Again.

Run the Philips Upgrade Wizard again to check and verify final APC and AP configurations, and fix any errors as needed. If any configuration modifications are made, run the Philips Upgrade Wizard again.

Caution Close the APC web interface before running the Philips Upgrade Wizard. Do not add components to or remove components from the IntelliVue Telemetry System while the wizard is running.

Follow these steps to upgrade ITS Access Point Controllers and Access Points using the Philips Upgrade Wizard:

Philips Upgrade Wizard:

1. Run the Philips Upgrade Wizard by double-clicking the file:

C:\Telemetry Upgrader\upgrader.exe

The Upgrade Wizard splash screen (Figure 3-31) appears.

2. Click Next> to continue.

The APC/AP firmware selection screen (Figure 3-32) appears.

3. Complete the settings on the APC/AP firmware selection screen: a) Click ... and then browse to the directory (e.g.,

C:\Telemetry Upgrader\AP and APC Images\) in which you have installed the APC and AP firmware files.

b) Specify what type of APs you have installed by marking the appropriate radio button, 1.4 GHz Smart Hopping or 2.4 GHz Smart Hopping.

3-42

MOSE225

Step 11. Run the Philips Upgrade Wizard Again.

Figure 3-31: Upgrade Wizard Splash Screen

Additionally, if you have installed Core APs, then be sure to mark the System includes Cluster APs (with or without Remote Antennas) checkbox.

c) Verify that the correct firmware versions are displayed in the APC Version,

AP Version (Standard), and AP Version (Core) fields.

Figure 3-32: APC/AP Firmware Selection Screen

d) Select the ICN IP address (e.g., 172.31.240.4) you have configured for the support PC on which you are running the wizard from the Use IP Address drop-down menu. The menu lists the IP addresses of all Ethernet NICs configured on the PC.

e) Select Upgrade if necessary from the APC drop-down menu. By default, an

APC will not be upgraded if it is already at the selected firmware version.

f) Select Smart Hopping-only Check and Update Configuration from the unlabeled drop-down menu to verify and update the APC configuration.

IntelliVue Telemetry System Infrastructure Installation and Service Guide 3 43

MOSE225

Chapter 3: Installing and Configuring the ITS

g) Select Upgrade if necessary from the AP drop-down menu to allow APs to be upgraded even if they are already at the newest firmware revision.

h) Do not mark the Export Configuration? checkbox.

You will not export the ITS configuration until later in this procedure.

4. Click Next> to continue.

The wizard automatically scans the IntelliVue Telemetry System for all

connected APCs. When the scan is completed (Figure 3-33), the following

message appears:

System [Philips] – Master APC [e.g., APC-02*] Complete (Config Key = C000532B)

* Note that the displayed APC value will be different for each clinical site.

Figure 3-33: APC Scan Completion Screen

5. Highlight/select the displayed message, e.g., System [Philips] – Master APC

[APC3E] Complete and then click Next> to continue.

The wizard scans the IntelliVue Telemetry System for all connected APs

(Figure 3-34).

The scan may take several minutes to complete. When the scan is completed, the following message appears:

Finished System scan

3-44

MOSE225

Step 11. Run the Philips Upgrade Wizard Again.

Figure 3-34: AP Scan Completion Screen

6. Click Next> to continue.

The APCs and APs are queried, and a full navigational tree of the ITS is built and

displayed (Figure 3-35), including APCs, APs (and the Group to which they

belong), and PWDs/PWMs.

Figure 3-35: ITS Navigational Tree Screen

The tree lists the current firmware revision installed on each APC and AP found in the ITS.

Items needing an upgrade are shown in bold. If an AP needs an upgrade, the

APC it is connected to will also be shown in bold, even if that APC itself does not require upgrading.

7. Select one APC (i.e., top level APC structure) at a time to upgrade. For example, select APC [APC-C3] Version [A.00.29] and then select Next>.

IntelliVue Telemetry System Infrastructure Installation and Service Guide 3 45

MOSE225

Chapter 3: Installing and Configuring the ITS

We recommend that you upgrade the APC with the lightest load (i.e., the fewest number of APs and patient-worn transceivers) first. We recommend that you upgrade the Master APC last.

The selected APC is taken offline, and the message Taking APC Offline is displayed.

8. Click Next> to continue.

The Select AP Group to Roam screen appears (Figure 3-36).

3-46

Figure 3-36: Selecting the AP Group to Roam

Select the clinical unit/group containing the APs to roam away from the APC, for example Group [CCU North].

As the APs are roamed to another APC, the message Roaming APs from Group

[Group Name] is displayed.

When all APs in the group have been roamed to another APC, the message All

APs successfully roamed is displayed.

Note If you are upgrading only a single APC system, the message WARNING: Couldn't

Roam all APs. Continue anyway?? is displayed. Continue the upgrade process if you see this message.

9. Select Next> to continue.

If there are more AP groups that must be roamed away from the APC, then you

are returned to the Select AP Group to Roam screen (Figure 3-36). Roam the

remaining AP groups away from the APC, one group at a time.

Otherwise, the APC upgrade process begins. The upgrade process may take

several minutes to complete. Status messages are displayed (Figure 3-37) as

the process runs.

The message Finished Upgrading APC appears when the upgrade process is complete.

MOSE225

Step 11. Run the Philips Upgrade Wizard Again.

Figure 3-37: APC Upgrade Process Status Messages

10. Click Next> to continue.

The AP Roam Back screen (Figure 3-38) appears.

Figure 3-38: AP Roam Back Screen

Select the clinical unit/group containing the APs to roam back to the upgraded

APC.

Note If no APs need to be upgraded, and no PWDs/PWMs are on the system, the ITS navigational tree will appear but no devices will be displayed in bold. Click Next to continue the process, and advance to the next screen (Restoring System State).

11. Click Next> to continue.

Before an AP is upgraded, the wizard roams its PWDs/PWMs to another AP.

IntelliVue Telemetry System Infrastructure Installation and Service Guide 3 47

MOSE225

Chapter 3: Installing and Configuring the ITS

Status messages are displayed as the PWDs/PWMs are roamed to another AP

(Figure 3-39).

3-48

Figure 3-39: PWD Roaming Status Messages

The message Finished Roaming PWDs is displayed when the PWD/PWM roaming process is complete.

12. Click Next> to continue.

If patient-worn transceivers cannot be roamed to another AP, then a dialog appears reminding you that patient-worn devices connected to the AP will lose data while the AP is being upgraded.

Figure 3-40: Patient Worn Device Data Loss Warning

13. Click Continue to continue the upgrade process.

The wizard upgrades the APs two at a time and displays status messages about

the AP upgrade process (Figure 3-41).

The message Finished upgrading AP [AP-##] is displayed when the AP upgrade process is complete.

MOSE225

Step 11. Run the Philips Upgrade Wizard Again.

Figure 3-41: AP Upgrade Process Status Messages

Note If an error is encountered during the AP upgrade process, the following dialog is displayed. Click Retry to reattempt the AP upgrade.

Figure 3-42: AP Upgrade Error Message

If the error dialog reappears repeatedly each time you click Retry, then click Skip to bypass this AP in the upgrade process. After the upgrade process completes, you must then run the Upgrade Wizard again to upgrade the AP that was bypassed.

14. Click Next> to continue.

The wizard returns to the PWD Roaming Status Messages screen (Figure 3-39)

if there are more APs in the Group.

The wizard returns to the Select AP Group to Roam screen (Figure 3-36) if there

are more AP Groups to upgrade.

The wizard returns to the ITS Navigational Tree screen (Figure 3-35) if there are

more APCs to upgrade.

Repeat the steps in this procedure until you have successfully upgraded all of the APC and APs in your ITS.

15. After all APCs and APs have been upgraded, the Upgrade Wizard Report

(Figure 3-43) is displayed.

IntelliVue Telemetry System Infrastructure Installation and Service Guide 3 49

MOSE225

Chapter 3: Installing and Configuring the ITS

The report provides a summary of all devices upgraded along with any errors that may have been generated during the upgrade process.

Figure 3-43: Upgrade Wizard Report

Click Save to save the report to a disk file (recommended).

Click Print to print the report without saving it.

Click Finish to close the Upgrade Wizard program.

Note that the Upgrade Wizard automatically creates a log file, logfile.txt, in the directory from which it was run. Rename this log file and save it together with the

Upgrade Wizard Report disk file in another directory.

Step 12. Export the ITS Configuration to a Disk File.

You can export a system configuration from an Access Point Controller to a disk file and import a previously exported configuration file to an Access Point Controller by running the Philips Upgrade Wizard.

Note Before exporting any configuration files, you must run through the Upgrade Wizard’s configuration checking process and correct any errors that are found. If you do not correct errors prior to exporting the configuration, the exported archive will contain errors.

To export the ITS configuration to a file in both human- and machine-readable formats:

1. Run the Philips Upgrade Wizard by double-clicking the file:

C:\Telemetry Upgrader\upgrader.exe

The Upgrade Wizard splash screen appears.

2. Click Next> to continue.

The APC/AP firmware selection screen (Figure 3-44) appears.

3-50

MOSE225

Step 12. Export the ITS Configuration to a Disk File.

Figure 3-44: Exporting an ITS Configuration

a) Specify what type of APs you have installed by marking the appropriate radio button, 1.4 GHz Smart Hopping or 2.4 GHz Smart Hopping.

b) Mark the Export Configuration? checkbox.

The APC fields are set to Do not upgrade and Only check configuration.

The AP field is set to Do not upgrade.

c) Enter the full path and file name of the configuration file to create in the

Export Filename field.

3. Click Next to create the specified ITS configuration file.

The exported file containing the configuration archive is stored on the service

PC from which you run the Philips Upgrade Wizard. All configuration items on the APC are archived to the specified file.

4. After the Upgrade Wizard has verified the configuration on all APCs and APs,

review the Upgrade Wizard Report screen (Figure 3-43) to verify that there are

no ITS configuration errors present.

If there are any configuration errors present, you must correct the errors before expanding the ITS.

5. Click Save to save the Upgrade Wizard report to a disk file on your service PC.

After saving the Upgrade Wizard Report to a disk file, you should the open the text file in Notepad and execute a find for the strings “error” and “warning.” All errors must be corrected and all warnings be reviewed. See Appendix C for descriptions of possible error and warning messages.

IntelliVue Telemetry System Infrastructure Installation and Service Guide 3 51

Chapter 3: Installing and Configuring the ITS

MOSE225

Figure 3-45: Upgrade Wizard Report

6. Click Finish to close the Upgrade Wizard.

Note that the Upgrade Wizard automatically creates a log file, logfile.txt, in the directory from which it was run.

7. Locate the ITS configuration file (

<filename.txt>

), the Upgrade Wizard report, and the Upgrade Wizard log file (logfile.txt) in the directory from which the

Upgrade Wizard was run (

C:\Telemetry Upgrader

), and move these files to an archive folder on your service PC for safekeeping.

Step 13. Restore your Service PC to its Original Settings.

Return your Service PC to its original setup, otherwise you will have problems connecting to your normal network.

Step 14. Install ITS Bedside Monitors and Patient-worn Devices.

Once you have completed steps 1 to 12 to install the ITS, you can now add ITS infrastructure and wireless clients into the Configuration Wizard. You can then configure the wireless clients for use by using the Label Assignment function from the DBS or IIC.

Note that if the IIC and DBS are running System J or greater, you can enter the ITS infrastructure devices into the Configuration Wizard by running the network Scan function on the Database Server/Standalone IntelliVue Information Center.

Turn on patient-worn transceivers and wireless bedside monitors that have been configured for use (i.e., equipment labels have been assigned in DBS, and equipment labels and domain have been set in the transceivers/bedsides). The transceivers and monitors should associate with APs in the system and begin to pass data to the central station displays.

3-52

4

MOSE225

Expanding or Modifying an Installed ITS

This chapter provides procedures to expand or modify an existing, installed ITS, and includes:

• Expanding an Installed IntelliVue Telemetry System

• ITS Expansion Prerequisites

• Archiving the ITS Configuration Files

• Upgrading ITS APCs and APs Using the Philips Upgrade Wizard

• Adding APCs to an Existing ITS

• Adding APs to an Installed ITS

• Adding ITS Monitoring Devices

• Replacing an AP, Remote Antenna, or APC in an Existing System

IntelliVue Telemetry System Infrastructure Installation and Service Guide 4 1

MOSE225

Chapter 4: Expanding or Modifying an Installed ITS

Expanding an Installed IntelliVue Telemetry System

This section describes the IntelliVue Telemetry System expansion scenarios and procedures. We assume that you will execute these procedures only on an installed and fully functional ITS.

Expanding an installed ITS has three facets:

• Adding APs to the ITS - The presumption is that all system expansion scenarios will include AP additions. Given the current design rules, APCs would not be added to an installed ITS if the system AP count were not increasing.

• Adding APCs to the ITS - APCs will need to be added to the system if APs are added beyond the current supported APC capacity. Given the current design rules, APCs would not be added to an installed ITS if the system AP count were not increasing.

• Adding AP Groups to an ITS Configuration - While this isn’t a hardware expansion, adding additional AP Groups to the system configuration might be common in a system where APs were being added. AP Group additions to the configuration without the addition of APs is considered a re-configuration exercise and is not covered in this document.

The scope of the system expansion needs to be analyzed to determine the proper sequence of events. The flow chart below identifies and facilitates the approach to system expansion and the order the tasks that must be completed.

Prior to expanding an installed ITS, be sure you have properly documented the expansion by modifying the ITS Installation Worksheets for the site.

The general flow of tasks associated with an ITS expansion is shown in Figure 4-1.

4-2

MOSE225

Expanding an Installed IntelliVue Telemetry System

Run Upgrade

Wizard with

-export option to capture current configuration.

page 4-4

Is APC at

Version

A.00.XX?

N

Y

Adding New

APCs to

System?

Y

N

Adding New

AP Groups to

Config?

Y

N

Perform configuration check and replication procedure

(Using Upgrade Wizard Tool)

Add APs

(choose method)

Auto-registration &

BootP Server

page 4-22

Manual MAC

Address Input

page 4-26

Upgrade APC to

Version B.00.19

page 4-7

Add APCs

Procedure

page 4-20

Add Groups

Procedure

page 4-28

Run Upgrade

Wizard with

-export option to archive new configuration.

page 4-4

Perform configuration check and replication procedure

(Using Upgrade Wizard Tool)

Figure 4-1: ITS Expansion Tasks

IntelliVue Telemetry System Infrastructure Installation and Service Guide 4 3

MOSE225

Chapter 4: Expanding or Modifying an Installed ITS

ITS Expansion Prerequisites

Note Implementing and executing any of the expansion procedures listed in this Chapter will cause interruptions to monitoring if the system is “live”—i.e., if the ITS is up and running and monitoring patients. Changing APC mastership relationships or

AP/APC partnering will cause monitoring interruptions. You must notify the hospital staff of all planned service events to the IntelliVue Telemetry System prior to implementing these service events.

Note the following requirements you must complete prior to expanding or modifying an ITS:

• Define the expanded RF coverage area. You may need to conduct an additional

RF survey to ensure proper coverage for the additional area. See Chapter 2 for details.

• Install additional network switching infrastructure as required for new coverage area. See Chapter 2 for details.

• Expand the Sync network as required to support additional APs. See Chapter 2 for details

• Run only Version A.00.20 (or greater) of the Philips Upgrade Wizard when expanding/upgrading an ITS.

• Upgrade the existing system APC software to B.00.19 or greater prior to expanding an ITS.

• Export the current ITS configuration to a service PC before expanding the ITS.

See the next section for details.

Archiving the ITS Configuration Files

Prior to expanding or modifying an ITS, upgrading ITS APC or AP software, and upon completion of the ITS expansion, you must save the following files to disk on your service PC:

• ITS configuration file

• Upgrade Wizard report

• logfile.txt file automatically generated by the Upgrade Wizard

Note Do not run the Philips Upgrade Wizard on a computer with a browser open.

To save the ITS configuration files:

To export the ITS configuration to a file in both human- and machine-readable formats:

1. Run the Philips Upgrade Wizard by double-clicking the file:

C:\Telemetry Upgrader\upgrader.exe

The Upgrade Wizard splash screen appears.

4-4

MOSE225

Archiving the ITS Configuration Files

2. Click Next> to continue.

The APC/AP firmware selection screen (Figure 4-2) appears.

Figure 4-2: Exporting an ITS Configuration

a) Specify what type of APs you have installed by marking the appropriate radio button, 1.4 GHz Smart Hopping or 2.4 GHz Smart Hopping.

b) Mark the Export Configuration? checkbox.

The APC fields are set to Do not upgrade and Only check configuration.

The AP field is set to Do not upgrade.

c) Enter the full path and file name of the configuration file to create in the

Export Filename field.

3. Click Next to create the specified ITS APC configuration file.

The exported file containing the configuration archive is stored on the service

PC from which you run the Philips Upgrade Wizard. All configuration items on the APC are archived to the specified file.

A sample exported ITS APC configuration file is shown in Figure 4-3.

IntelliVue Telemetry System Infrastructure Installation and Service Guide 4 5

MOSE225

Chapter 4: Expanding or Modifying an Installed ITS

###########################################

# SMART HOPPING SYSTEM EXPORT FILE #

###########################################

System {

APC MAC 00:09:FB:F7:F6:84 {

File String "BOOTROM.NVP" {

MAC 00:09:FB:F7:F6:84

Word 0000

IP 172.31.241.2

IP 255.255.240.0

IP 172.31.240.1

Byte 00

} # End file BOOTROM.NVP

File String "PASSWORD.TLV" {

Tag Word 1700

{

Bytes { 00 00 00 00 }

}

} # End of file PASSWORD.TLV

File String "PARAM/SYSTEM.TLV" {

Tag Word 1310

#Possible tag names:

#SYS_WEB_USERNAME_TAG

{

}

Tag Word 1300

#Possible tag names:

#SYS_WEB_PASSWORD_TAG

Figure 4-3: Sample Exported ITS APC Configuration File

4. After the Upgrade Wizard has verified the configuration on all APCs and APs, review the Upgrade Wizard Report screen (Figure 4-4) to verify that there are no

ITS configuration errors present.

4-6

Figure 4-4: Upgrade Wizard Report

If there are any configuration errors present, you must correct the errors before expanding the ITS.

5. Click Save to save the Upgrade Wizard report to a disk file on your service PC.

MOSE225

Upgrading ITS APCs and APs Using the Philips Upgrade Wizard

After saving the Upgrade Wizard Report to a disk file, you should the open the text file in Notepad and execute a find for the strings “error” and “warning.” All errors must be corrected and all warnings be reviewed. See Appendix C for descriptions of possible error and warning messages.

6. Click Finish to close the Upgrade Wizard.

Note that the Upgrade Wizard automatically creates a log file, logfile.txt, in the directory from which it was run.

7. Locate the ITS configuration file (

<filename.txt>

), the Upgrade Wizard report, and the Upgrade Wizard log file (logfile.txt) in the directory from which the

Upgrade Wizard was run (

C:\Telemetry Upgrader

), and move these files to an archive folder on your service PC for safekeeping.

Upgrading ITS APCs and APs Using the Philips Upgrade Wizard

This section describes use of the Philips Upgrade Wizard tool to upgrade devices on an installed ITS and includes:

• An Overview of the Upgrade Wizard

• Access Point Controller Upgrade Process Summary

• Access Point Upgrade Process Summary

• Compatibility

• ITS Upgrade Prerequisites

• ITS Upgrade Procedure

An Overview of the Upgrade Wizard

The Philips Upgrade Wizard is a PC-based utility that:

• upgrades the firmware on IntelliVue Telemetry System Access Point Controllers

(APCs) and 1.4 GHz. and 2.4 GHz Smart-hopping Access Points (APs)

• verifies that APCs on your network are configured correctly

• displays warning and error messages that you may use to troubleshoot any configuration errors that may exist on your ITS network

The Philips Upgrade Wizard runs on a Windows 2000 or Windows XP PC connected to an ITS network. The wizard scans the network for APCs, and connected APs

Patient Worn Devices (PWDs), and Patient Worn Monitors (PWMs). It then guides you through the upgrade process, one APC and two APs at a time. Before upgrading an AP, the Philips Upgrade Wizard roams any active PWDs/PWMs connected to the

AP to alternate APs so that minimal patient data is lost.

The wizard will export the APC system configuration and check that it conforms to the system requirements and installation rules, and verifies that the slave APC configuration matches the master APC configuration.

The Philips Upgrade Wizard updates the APC configuration using normal APC update processing, so the APC does not need to be rebooted and data flow is not interrupted during the configuration update process.

IntelliVue Telemetry System Infrastructure Installation and Service Guide 4 7

MOSE225

Chapter 4: Expanding or Modifying an Installed ITS

If the Philips Upgrade Wizard detects that an APC installation or configuration rule is broken, it generates a warning message after the upgrade process is complete. If the Philips Upgrade Wizard detects that a system requirement is broken, it generates an error and stops the upgrade process. If the APC Master and Slave configurations are mismatched, then the wizard attempts to force the Slave to upload a copy of the Master configuration.

Access Point Controller Upgrade Process Summary

Upgrading ITS Access Point Controllers using the Philips Upgrade Wizard proceeds as follows:

• The Upgrade Wizard will automatically retrieve the Master Configuration file from the Master APC to allow the process to maintain system configuration and return the system to original configuration.

• Select the AP group to be upgraded. If the Master APC manages this AP group, then the Upgrade Wizard will act as the Master to allow upgrade of the Master

APC.

• Before an APC can be upgraded, any attached APs will be dispersed to other

APCs in the system. During the dispersion of APs there will be loss of monitoring from the affected APs for 10 to 20 seconds.

• The Upgrade Wizard will verify configuration of APC against the Master

Configuration file, and notify the service user if differences exist and assist in corrective action if necessary.

• At this point the Upgrade Wizard notifies the APC being serviced to start the upgrade, a new software image is downloaded to the APC via TFTP and then verified. The service user will be prompted for input and notified of upgrade progress and status. The download of APC image takes approximately 3 minutes, and at the end of the process the APC will reboot.

• On completion of the APC upgrade, the APs from that AP group are re-partnered with the upgraded APC. There will be loss of monitoring while APs are repartnered.

• After you have upgraded all the APCs on an ITS, the current Master APC may function as a Slave APC to a new Master APC.

• If you will upgrading the software on ITS APs, then proceed to the next section

“Access Point Upgrade Process Summary” below. Otherwise, run the Philips

Upgrade Wizard again to verify the APC and AP configurations system wide, and archive the ITS configuration files as described on page 4-4.

Warning When upgrading the firmware on an APC from version A.00.NN to B.00.NN, the ITS

BOOTP/DHCP settings previously configured using version A.00.NN may be displayed/configured improperly under version B.00.NN. Routed table entries may be displayed in the non-routed table, and vice-versa. After upgrading an APC from firmware version A.00.NN to B.00.NN, be sure to verify and if necessary, correct the

BOOTP/DHCP table entries listed in the APC web interface.

4-8

MOSE225

Upgrading ITS APCs and APs Using the Philips Upgrade Wizard

Access Point Upgrade Process Summary

Upgrading ITS Access Points using the Philips Upgrade Wizard proceeds as follows:

• If both APs and APCs need to be upgraded, then the APCs will be upgraded first.

• Attach the service PC/laptop to the ITS subnet.

The PC must be connected to the subnet that the wireless infrastructure equipment is connected to. The Philips Upgrade Wizard will passively discover all active network components and display the active equipment labels for

Patient Worn Devices (PWDs), Patient Worn Monitors (PWMs), APs, and APCs to allow for easy identification.

• You are provided with equipment label information to provide adequate notification to clinical staff of any effected equipment.

• For the AP group, perform AP upgrade on all APs currently with no mobile clients connected to them. You are prompted for input and notified of the upgrade progress, status, and outcome.

• For each AP in an AP group with active PWDs/PWMs forced roaming will be attempted. You are prompted to move active PWDs/PWMs if the roam fails.

Once the active PWDs/PWMs are off the AP, the AP upgrade is user-initiated, and you are prompted for input and notified of progress, status, and outcome.

• Repeat for each AP group.

• APs will reboot when their partnered APC is power cycled.

• Run the Philips Upgrade Wizard again to verify the APC and AP configurations system wide, and archive the ITS configuration files as described on page 4-4.

Compatibility

The Philips Upgrade Wizard requires supported, and compatible AP and APC firmware. Note the compatibility requirements listed in Table 4-1.

Caution Use of Versions A.00.19 and older of the Upgrade Wizard must be discontinued.

Upgrade

Wizard Version

(A.00.21)

(A.00.20)

(A.00.19)

(A.00.16)

(A.00.08)

(A.00.07)

APC (C.00.02)

Compatible

Compatible

Not Compatible

Not Compatible

Not Compatible

Warning: May

Cause AP Fault

Not Compatible

Warning: May

Cause AP Fault

Table 4-1: Upgrade Wizard and APC Compatibility

APC (B.00.19)

Compatible

Compatible

Compatible

Not Compatible

Not Compatible

Warning: May

Cause AP Fault

Not Compatible

Warning: May

Cause AP Fault

APC (B.00.15) APC (A.00.34) APC (A.00.32)

Compatible

Compatible

Compatible

Compatible

Not Compatible

Warning: May

Cause AP Fault

Not Compatible

Warning: May

Cause AP Fault

Compatible

Compatible

Compatible

Compatible

Compatible

Not Compatible

Compatible

Compatible

Compatible

Compatible

Compatible

Compatible

APC (A.00.29)

Compatible

Compatible

Compatible

Compatible

Compatible

Compatible

IntelliVue Telemetry System Infrastructure Installation and Service Guide 4 9

MOSE225

Chapter 4: Expanding or Modifying an Installed ITS

Table 4-1: Upgrade Wizard and APC Compatibility

Upgrade

Wizard Version

(A.00.0X)

APC (C.00.02) APC (B.00.19) APC (B.00.15) APC (A.00.34) APC (A.00.32) APC (A.00.29)

Not Compatible

Warning: May

Cause AP Fault

Not Compatible

Warning: May

Cause AP Fault

Not Compatible

Warning: May

Cause AP Fault

Not Compatible Not Compatible Compatible

Note the compatibility between versions of AP and APC firmware listed in Table 4-2.

Table 4-2: AP and APC Firmware Compatibility

ITS AP Firmware

Version

2.4 GHz AP (C.00.04)

Legacy 2.4 GHz AP (B.00.12)

Legacy 2.4 GHz AP (B.00.07)

1.4 GHz Core AP (C.00.01)

Legacy 1.4 GHz Core AP

(A.00.26)

Legacy 1.4 GHz Core AP

(A.00.27)

Legacy 1.4 GHz Core AP

(A.00.23)

Legacy 1.4 GHz Std. AP

(A.00.66)

Legacy 1.4 GHz Std. AP

(A.00.54)

Legacy 1.4 GHz Std. AP

(A.00.52)

Legacy 1.4 GHz Std. AP

(A.00.50)

C.00.02

Compatible

Compatible

Not Compatible

Compatible

Compatible

Compatible

Not Compatible

Compatible

Not Compatible

Not Compatible

Not Compatible

ITS APC Firmware Version

B.00.19

Compatible

Compatible

Not Compatible

Compatible

Compatible

B.00.15

Not Compatible

Not Compatible

Compatible

Compatible

Compatible

A.00.34

Not Compatible

Not Compatible

Not Compatible

Compatible

Compatible

Compatible

Not Compatible

Compatible

Not Compatible

Not Compatible

Not Compatible

Compatible

Compatible

Not Compatible

Compatible

Not Compatible

Not Compatible

Compatible

Compatible

Not Compatible

Compatible

Not Compatible

Not Compatible

A.00.32

Not Compatible

Not Compatible

Not Compatible

Not Compatible

Not Compatible

Not Compatible

Not Compatible

Not Compatible

Not Compatible

Compatible

Not Compatible

4-10

MOSE225

Upgrading ITS APCs and APs Using the Philips Upgrade Wizard

ITS Upgrade Prerequisites

Note the following requirements you must complete prior to upgrading an ITS using the Philips Upgrade Wizard:

• Install the Upgrade Wizard Tool on your service PC as described on page 3-10.

• Connect your service PC to the ITS wireless subnet as described on page 3-8.

• Export the current ITS configuration to a service PC before upgrading the ITS.

See for details page 4-4.

• Run only Version A.00.19 (or greater) of the Philips Upgrade Wizard when expanding/upgrading an ITS.

• Upgrade the existing system APC software to B.00.19 or greater prior to expanding an ITS.

• Close all browser windows on the Service PC prior to running the Upgrade

Wizard.

ITS Upgrade Procedure

Follow these steps to upgrade ITS Access Point Controllers and Access Points using the Philips Upgrade Wizard:

Philips Upgrade Wizard:

1. Run the Philips Upgrade Wizard by double-clicking the file:

C:\Telemetry Upgrader\upgrader.exe

The Upgrade Wizard splash screen (Figure 4-5) appears.

Figure 4-5: Upgrade Wizard Splash Screen

2. Click Next> to continue.

The APC/AP firmware selection screen (Figure 4-6) appears.

3. Complete the settings on the APC/AP firmware selection screen: a) Click ... and then browse to the directory (e.g.,

C:\Telemetry Upgrader\AP and APC Images\

) in which you have installed the APC and AP image files.

IntelliVue Telemetry System Infrastructure Installation and Service Guide 4 11

MOSE225

Chapter 4: Expanding or Modifying an Installed ITS

b) Specify what type of APs you have installed by marking the appropriate radio button, 1.4 GHz Smart Hopping or 2.4 GHz Smart Hopping.

Additionally, if you have installed Core APs, then be sure to mark the System includes Cluster APs (with or without Remote Antennas) checkbox.

c) Verify that the correct firmware versions are displayed in the APC Version,

AP Version (Standard), and AP Version (Cluster) fields.

4-12

Figure 4-6: APC/AP Firmware Selection Screen

Note that the firmware files listed in the Version fields correspond to the files stored within the directory listed in the Folder field. If valid device firmware files are not found within the specified directory, you cannot proceed.

d) Select the ICN IP address (e.g., 172.31.240.4) you have configured for the support PC on which you are running the wizard from the Use IP Address drop-down menu. The menu lists the IP addresses of all Ethernet NICs configured on the PC.

e) Select Upgrade if necessary from the APC drop-down menu to allow each

APC to be upgraded. By default, an APC will not be upgraded if it is already at the selected firmware version.

f) Select Ignore Configuration from the unlabeled drop-down menu to ignore the APC configuration the first time you run the Upgrade Wizard.

g) Select Do Not Upgrade from the AP drop-down as you have only installed

APCs on the ITS at this point.

h) Do not mark the Export Configuration? checkbox.

You will not export the ITS configuration until later in this procedure.

4. Click Next> to continue.

The wizard automatically scans the IntelliVue Telemetry System for all connected APCs. When the scan is completed (Figure 4-7), the following message appears:

MOSE225

Upgrading ITS APCs and APs Using the Philips Upgrade Wizard

System [Philips] – Master APC [e.g., APC-02*] Complete (Config Key = C000532B)

* Note that the displayed APC name will be different for each clinical site.

After scanning the ITS for connected APCs, the Upgrade Wizard will list any APCs that have an incompatible configuration key. If such an APC is found, you cannot continue the upgrade process. Locate the incompatible APC, disconnect it from the ITS, reset it to its factory defaults, and then reconnect it to the ITS before retrying the upgrade process.

Figure 4-7: APC Scan Completion Screen

5. Highlight/select the displayed message, e.g., System [Philips] – Master APC

[APC3E] Complete and then click Next> to continue.

The wizard scans the IntelliVue Telemetry System for all connected APs.

The scan may take several minutes to complete. When the scan is completed, the message Finished System scan appears and the Next button becomes active.

6. Highlight/select the displayed message, e.g., System [Philips] – Master APC

[APC3E] Complete (Config Key = C000532B) and then click Next> to continue.

The wizard scans the IntelliVue Telemetry System for all connected APs

(Figure 4-8).

The scan may take several minutes to complete. When the scan is completed, the message Finished System scan appears and the Next button becomes active.

IntelliVue Telemetry System Infrastructure Installation and Service Guide 4 13

Chapter 4: Expanding or Modifying an Installed ITS

MOSE225

Figure 4-8: AP Scan Completion Screen

7. Click Next> to continue.

The APCs and APs are queried, and a full navigational tree of the ITS is built and displayed (Figure 4-9), including APCs, APs (and the Group to which they belong), and PWDs/PWMs.

4-14

Figure 4-9: ITS Navigational Tree Screen

The tree lists the current firmware revision installed on each APC and AP found in the ITS.

Items needing an upgrade are shown in bold. If an AP needs an upgrade, the

APC it is connected to will also be shown in bold, even if that APC itself does not require upgrading.

8. Select one APC (i.e., top level APC structure) at a time to upgrade. For example, select APC [APC3N] Version [A.00.29] and then select Next>.

MOSE225

Upgrading ITS APCs and APs Using the Philips Upgrade Wizard

We recommend that you upgrade the APC with the lightest load (i.e., the fewest number of APs and patient-worn transceivers) first. We recommend that you upgrade the Master APC last.

The selected APC is taken offline, and the message Taking APC Offline is displayed.

9. Click Next> to continue.

The Select AP Group to Roam screen appears (Figure 4-10).

Figure 4-10: Selecting the AP Group to Roam

Select the AP group containing the APs to roam away from the APC, for example

Group [CCU North].

As the APs are roamed to another APC, the message Roaming APs from Group

[Group Name] is displayed.

When all APs in the group have been roamed to another APC, the message All

APs successfully roamed is displayed.

Note If you are upgrading only a single APC system, the message WARNING: Couldn't

Roam all APs. Continue anyway?? is displayed. Continue the upgrade process if you see this message. if you have only a single APC on your system, you will lose all monitoring capabilities while the upgrade is in progress.

10. Select Next> to continue.

If there are more AP groups that must be roamed away from the APC, then you are returned to the Select AP Group to Roam screen (Figure 4-10). Roam the remaining AP groups away from the APC, one group at a time.

Otherwise, the APC upgrade process begins. The upgrade process will take several minutes to complete. Status messages are displayed (Figure 4-11) as the process runs.

IntelliVue Telemetry System Infrastructure Installation and Service Guide 4 15

Chapter 4: Expanding or Modifying an Installed ITS

MOSE225

Figure 4-11: APC Upgrade Process Status Messages

The message Finished Upgrading APC appears when the upgrade process is complete.

11. Click Next> to continue.

The AP Roam Back screen (Figure 4-12) appears.

4-16

Figure 4-12: AP Roam Back Screen

Select the AP group containing the APs to roam back to the upgraded APC.

Note If no APs need to be upgraded, and no PWDs/PWMs are on the system, the ITS navigational tree will appear but no devices will be displayed in bold. Advance to the next screen (Restoring System State).

12. Click Next> to continue.

MOSE225

Upgrading ITS APCs and APs Using the Philips Upgrade Wizard

Before an AP is upgraded, the wizard roams its PWDs/PWMs to another AP.

Status messages are displayed as the PWDs/PWMs are roamed to another AP

(Figure 4-13).

Figure 4-13: PWD Roaming Status Messages

The message Finished Roaming PWDs is displayed when the PWD/PWM roaming process is complete.

13. Click Next> to continue.

A dialog appears reminding you that patient-worn devices connected to the AP will lose data while the AP is being upgraded.

Figure 4-14: Patient Worn Device Data Loss Warning

14. Click Continue to continue the upgrade process.

The wizard upgrades the APs two at a time and displays status messages about the AP upgrade process (Figure 4-15).

The message Finished upgrading AP [AP-##] is displayed when the AP upgrade process is complete.

IntelliVue Telemetry System Infrastructure Installation and Service Guide 4 17

Chapter 4: Expanding or Modifying an Installed ITS

MOSE225

4-18

Note

Figure 4-15: AP Upgrade Process Status Messages

If an error is encountered during the AP upgrade process, the following dialog is displayed. Click Retry to reattempt the AP upgrade.

Figure 4-16: AP Upgrade Error Message

If the above error dialog reappears repeatedly each time you click Retry, then click

Skip to bypass this AP in the upgrade process. After the upgrade process completes, you must then run the Upgrade Wizard again to upgrade the AP that was bypassed.

If an AP was never rebooted after having its IP address changed, you would see the above error dialog reappear each time you click Retry. In such a case, the Upgrade

Wizard tool will actually upgrade the AP successfully even though the tool reports otherwise.

15. Click Next> to continue.

The wizard returns to the PWD Roaming Status Messages screen (Figure 4-13) if there are more APs in the Group.

The wizard returns to the Select AP Group to Roam screen (Figure 4-10) if there are more AP Groups to upgrade.

The wizard returns to the ITS Navigational Tree screen (Figure 4-9) if there are more APCs to upgrade.

MOSE225

Upgrading ITS APCs and APs Using the Philips Upgrade Wizard

Repeat the steps in this procedure until you have successfully upgraded all of the APC and APs in your ITS.

16. After all APCs and APs have been upgraded, the Upgrade Wizard Report

(Figure 4-17) is displayed.

The report provides a summary of all devices upgraded along with any errors that may have been generated during the upgrade process.

Refer to Appendix C for a description of possible Upgrade Wizard warning and error messages.

Figure 4-17: Upgrade Wizard Report

If there are any configuration errors present, you must correct the errors before upgrading the ITS.

17. Click Save to save the Upgrade Wizard report to a disk file on your service PC.

18. Click Finish to close the Upgrade Wizard.

Note that the Upgrade Wizard automatically creates a log file, logfile.txt, in the directory from which it was run.

Locate the Upgrade Wizard report, and the Upgrade Wizard log file (logfile.txt) in the directory from which the Upgrade Wizard was run (

C:\Telemetry Upgrader

), and move these files to an archive folder on your service PC for safekeeping.

19. Run the Philips Upgrade Wizard again to verify the APC and AP configurations system wide, and archive the ITS configuration files as described on page 4-4.

Warning When upgrading the firmware on an APC from version A.00.NN to B.00.NN, the ITS

BOOTP/DHCP settings previously configured using version A.00.NN may be displayed/configured improperly under version B.00.NN. Routed table entries may be displayed in the non-routed table, and vice-versa. After upgrading an APC from firmware version A.00.NN to B.00.NN, be sure to verify and if necessary, correct the

BOOTP/DHCP table entries listed in the APC web interface.

IntelliVue Telemetry System Infrastructure Installation and Service Guide 4 19

MOSE225

Chapter 4: Expanding or Modifying an Installed ITS

Adding APCs to an Existing ITS

Adding an APC to an existing IntelliVue Telemetry System may be required as a preliminary step to adding APs.

Before adding an APC to an ITS, ensure that you have verified the following:

• Before a new APC is added to an ITS, it must be in its factory default state. If the

APC has not been received directly from the factory, then connect the service PC to the APC serial port and reset the APC to its factory default settings.

If you properly reset an APC to its factory defaults before adding it to an existing

ITS, the new APC becomes a Slave, and it will determine that the Master configuration key is larger than its own, and properly request an update from the Master.

Caution Ensure that the subnet mask of the APC to be added is configured to match the network type. If the subnet mask is set incorrectly, it can cause system-wide failure on the ITS, as this APC will not be able to communicate effectively with other APCs on the ITS.

• Before you begin this procedure, ensure that the APC is not connected to the ITS network.

To add an APC to an installed ITS, complete the following steps:

1. Perform the APC initial configuration procedure described starting on

page 3-12.

This APC initial configuration procedure will:

• Verify the firmware revision of the replacement APC matches that of the

APCs already on the ITS.

• Reset the APC to its factory default settings. This will zero the APC’s configuration key and ensure that no configuration can be copied from the

APC (since the original configuration is removed).

• Set the APC’s IP address.

• Configure the APC for the desired system type (1.4 GHz Smart Hopping or

2.4 GHz Smart Hopping).

2. End the HyperTerminal session and disconnect the serial cable from the PC and

APC.

3. Power off the APC.

Caution Connect the APC network cable first, then connect its the power cable. Otherwise, the result could be a loss of monitoring and/or a loss of system configuration.

Implementing and executing any of the expansion procedures listed below will cause interruptions to monitoring if the system is “live” - i.e., system is up and running and monitoring patients. You must notify the hospital staff of all service events to the Philips IntelliVue Wireless Network prior to doing/implementing the service events.

4-20

MOSE225

Adding APs to an Installed ITS

4. Connect the new APC to the network, ensuring it is on the same subnet as the other APCs on the system: a) Connect a Category 5 network cable between the switch port and the APC. b) Power up the APC.

Verify that the APC power LED turns Green after its self-test (during which the

LED is amber).

5. Connect to the APC web-based management interface by opening a browser on

the service PC on the ITS subnet. Refer to page 3-8 if you need to configure your

service PC to connect to the ITS wireless subnet.

6. Select the APC in the View Device tree (selected device is displayed green) and then select the Configure tab.

In the AP Controller Network Configuration screen, configure the following parameters as necessary:

• System ID - Verify setting is Philips. If not, change it to Philips.

• AP Controller Name - Enter APC Name from APC worksheet (page 2-30).

• IP Addressing - Verify that the Specify IP radio button is marked and that the

IP Address, Subnet Mask and Default Gateway settings are as expected per

APC worksheet (page 2-30). If not, change the settings to match the

worksheet.

7. Click SAVE, and then verify the settings by selecting the Status tab.

8. Shutdown the APC web interface browser session, and then run the Philips

Upgrade Wizard to verify the APC and AP configurations system wide, and save

the ITS configuration files as described on page 4-4.

9. At this time, add all other APCs to the network by repeating Steps 1 to 12 for each APC to be added.

Adding APs to an Installed ITS

There are two procedures you can use to add APs to an existing IntelliVue Telemetry

System:

• The first procedure involves allowing the AP to automatically register on the system via the APC BootP server.

• The second procedure allows pre-configuration of the AP in the system so that when you do connect it to the ITS infrastructure, the AP will come up with the correct settings.

After you have added APs and Remote Antennas to your ITS, be sure to rename the newly added APs and Remote Antennas from their default values to more

meaningful, user-friendly names as described on page 4-28.

Before beginning the procedures given in this section, ensure that the ITS infrastructure (Switches, PoE Units, Sync Units) has sufficient capacity to connect the additional APs.

When adding new APs to an ITS, be sure to:

IntelliVue Telemetry System Infrastructure Installation and Service Guide 4 21

MOSE225

Chapter 4: Expanding or Modifying an Installed ITS

• Add only one AP at a time, wait for it to boot up, and then install the next AP only after waiting for a period of 60 seconds.

• Do not add multiple APs simultaneously on an ITS to prevent excess system stress due to high data traffic.

• Refrain from accessing the APC web interface during for 60 second waiting period after you have added an AP to the system.

• Always allow two-to-three minutes after making changes/additions to an ITS before accessing the web interface to check the status of the changes/ additions.

• Run the Upgrade Wizard periodically as APs are added to the system (e.g., every

12 newly added APs). Running the Upgrade Wizard periodically during the a system expansion provides these benefits:

- Provides error checking/warning for newly added APs; This ensures that any errors/warnings are detected early.

- Using the Upgrade Wizard will phase in the system changes and slow down the system expansion to a pace manageable by the active APCs.

When replacing an AP (see page 4-32) on an installed ITS, be sure to assign the

new replacement AP’s IP address as a static address. Assign the replacement AP the same IP address that was previously assigned to the old defective AP.

Adding an AP via Auto-Registration

To add an Access Point to an already up and running ITS using the auto-registration method:

1. Prior to adding the AP to the ITS, complete the 1.4 GHz Default AP Configuration

Worksheet (page 2-33) or the 2.4 GHz Default AP Configuration Worksheet

(page 2-34).

Caution Record the MAC address of the new AP prior to installing it. The MAC address is printed on the label found on the bottom of the AP. Also, to simplify the AP addition/ configuration procedure, you may find it helpful to connect the AP directly to a Sync

Unit in an equipment closet using a patch cable until the AP configuration is complete, and then disconnect and move the AP to its permanent mounting location. This may be desirable if you are connecting your service PC to a network switch to manage an AP in the same equipment closet.

2. Route a Category 5 UTP cable between each ITS Standard or Core Access Point and the equipment closet in which the ITS infrastructure devices are installed.

Be sure to install a ferrite block within 20 inches (50 cm) of the RJ-45 connector that connects to the Standard or Core Access Point as shown in Figure 4-18.

3. If you have installed a Core AP with Remote Antennas, connect the Core AP to its

RAs now using the provided 74-ft. UTP-and-Coaxial cable bundles.

4-22

MOSE225

Adding APs to an Installed ITS

ITS Access Point

Distance = less than

20 inches (50cm)

Figure 4-18: Installing a Ferrite Block on the ITS AP UTP Cable

Caution Do not kink the RA Coax-and-UTP-cable-bundle during installation. You must maintain a minimum 2.5-inch (64-mm) bend radius for the RA Coax-and-UTP-cablebundle throughout the installation.

a) Connect the first Remote Antenna to the Core AP using the UTP and Coaxial cable connectors labeled RA 1 in Figure 4-19.

b) Connect the second Remote Antenna to the Core AP using the UTP and

Coaxial cable connectors labeled RA 2 in Figure 4-19.

c) Be sure to label the UTP cable bundles and the Remote Antennas themselves as RA 1 and RA 2 corresponding to the cable connections you made in steps a and b.

Link LED

Activity LED

ITS Core Access Point

Coaxial Cable Connectors to Remote Antennas (2 & 1)

RA 2 RA 1

RA 2

Ethernet Interface to

ITS Sync Unit

Connection LED

(Green)

Power/Sync, Radio, and Network

Serial Port

Status LEDs

ITS Remote Antenna

RA 1

UTP Cable Connectors to Remote Antennas (2 & 1) with RA Status LEDs

Power LED

(Yellow)

UTP Cable Connector to ITS Core AP

Coaxial Cable Connector to ITS Core Access Point

Figure 4-19: 1.4 GHz ITS Core AP and Remote Antenna Controls and Connectors

4. Route and attach a network patch cable between the Access Point and the Sync

Unit, Power over Ethernet Unit, and appropriate network switch port. (See

IntelliVue Telemetry System Infrastructure Installation and Service Guide 4 23

MOSE225

Chapter 4: Expanding or Modifying an Installed ITS

1.4 GHz AP

Configuration

2.4 GHz AP

Configuration

page 3-4 for illustrations of and instructions for making these cable

connections.)

Once power is applied, the Access Point (and Remote Antennas) will take approximately 60 seconds to fully boot and will automatically appear in the View

Devices tree of the APC web interface under any AP Controller.

By default, the Remote Antennas are labeled as AP-1-ID#### (AP-port 1-remote antenna ID) or AP-2-ID#### (AP-port 2-remote antenna ID) where ID#### matches the ID number printed on the Remote Antenna’s device label.

Press F5 to refresh the APC web interface if the AP is not displayed.

If the AP is still not displayed, click System in the View Device tree, click

Configure and then select the Advanced tab. Verify that the Allow new APs to be added automatically option is set to True.

5. Click on the new AP and its configuration screen will appear. Note that although the AP was given an IP address by the BootP server, the IP address is not listed in the configuration screen. It appears as though the AP does not have an IP address (0.0.0.0).

6. In the AP Configuration screen for this Access Point, select the Basic Settings tab and then configure the following settings:

1.4 GHz Smart-Hopping AP Configuration Screen:

• Set the AP Name as appropriate for this AP.

• The Enable AP checkbox should be CHECKED.

• Leave the Partnered AP Controller drop-down list set to “ANY.” In this screen, the Partnered APC will get set correctly based upon the AP’s Group membership setting specified below.

• Set the Group Membership as appropriate for this AP.

• The WMTS Channels should match the existing ITS configuration.

• The RF Access Code should match the existing ITS configuration. Set the

Enable Box to CHECKED.

If you need to modify the WMTS or RF Access Code settings, then the 1.4 GHz.

AP defaults may not be set correctly. See page 3-27 for details.

• Mark the Use DHCP or Specify IP radio button as appropriate for your network. When specifying the IP address, you must set the Subnet Mask and Default Gateway fields to match the existing ITS configuration. When replacing an AP, be sure to assign the replacement AP’s IP address as a static address.

2.4 GHz Smart-Hopping AP Configuration Screen:

• Set the AP Name as appropriate for this AP.

• The Enable AP checkbox should be CHECKED.

• Leave the Partnered AP Controller drop-down list set to “ANY.” In this screen, the Partnered APC will get set correctly based upon the AP’s Group membership setting specified below.

• Set the Group Membership as appropriate for this AP.

4-24

MOSE225

Adding APs to an Installed ITS

• The Radio Regulations should match existing ITS configuration.

• The Frequency Plan should match existing ITS configuration.

• The ZigBee channel used for medical should match existing ITS configuration.

• The RF Access Code should match existing ITS configuration. Set the Enable

Box to CHECKED.

If you need to modify the Radio Regulations, Frequency Plan, Zigbee channel, or

RF Access Code settings, then the 2.4 GHz. AP defaults may not be set correctly.

See page 3-27 for details.

• Mark the Use DHCP or Specify IP radio button as appropriate for your network. When specifying the IP address, you must set the Subnet Mask and Default Gateway fields to match the existing ITS configuration. When replacing an AP, be sure to assign the replacement AP’s IP address as a static address.

7. Click SAVE and then verify the AP Configuration settings.

You should see the Partnered APC value change to match the AP group to which you assigned the AP.

8. Refresh Internet Explorer (by pressing F5), and in the View Devices tree, verify that the AP appears under the correct Access Point Controller.

This may take several minutes and in the process; the Access Point may appear

(for a moment) in the Unregistered List of the View Devices tree. If after five minutes the Access Point remains in the Unregistered List of View Devices tree, select the Access Point in the Unregistered List and click the Delete AP button at the bottom of the page. Remove power to the Access Point and repeat this procedure beginning from Step 1.

9. Disconnect the AP from the Sync Unit, and then reconnect it.

This will recycle power to the AP and forces the AP to apply the configuration changes.

10. Click on the STATUS tab for the newly added AP and verify that the IP shown for that AP is correct. If not, recycle power to the AP and then check and verify the status again.

Note If you encounter a Duplicate IP address system-level alert after adding an Access

Point to an ITS, then reconfigure the AP with a unique IP address, and then reset the

AP.

11. Repeat Steps 1 to 10 for each AP to be added to the installed ITS.

Run the Upgrade Wizard periodically as APs are added to the system (e.g., every

12 newly added APs).

12. Shutdown the APC web interface browser session, and then run the Philips

Upgrade Wizard to verify the APC and AP configurations system wide, and save

the ITS configuration files as described on page 4-4.

13. Add the new ITS devices to the Configuration Wizard.

IntelliVue Telemetry System Infrastructure Installation and Service Guide 4 25

MOSE225

Chapter 4: Expanding or Modifying an Installed ITS

Adding an AP via Manual MAC Address Input

By using an AP’s MAC address, you can fully pre-configure the AP before connecting it to the ITS.

Complete the following steps to manually add an Access Point to the system. This method allows you to pre-configure the AP off-line so that when you do connect it to the ITS, it will come up with the correct settings.

1. Before beginning this procedure, record the AP’s MAC address (found on the label on bottom of the AP), and complete the 1.4 GHz Default AP Configuration

Worksheet (page 2-33) or the 2.4 GHz Default AP Configuration Worksheet

(page 2-34).

2. Ensure the AP you want to add is disconnected from the network. In the APC management interface Device view, click the Add AP button.

The Add New Access Point (Figure 4-20) screen appears.

4-26

Figure 4-20: Add New Access Point Screen

3. Configure the following settings:

• AP Name - Enter the AP Name

• Physical Address - Enter the AP MAC Address

• AP Type - Select Smart-hopping from the drop-down menu.

4. Click the Add AP button, and then click the Network button to return to the

Device view. The newly added AP should appear in the unregistered APs list.

5. In the Unregistered List, select the AP just added and press the Basic Settings tab. Set the following AP-specific configuration parameters:

• Group Membership - Set as documented on the AP Configuration

Worksheet.

• IP Address - Set the IP address, Subnet Mask, and Default Gateway as documented on the AP Configuration Worksheet.

6. Click the SAVE button and verify the results. If the AP configurations settings are incorrect, repeat Step 5.

7. Add all other APs to the system configuration by completing Steps 1 to 6 for each AP.

8. Power on the AP. Each AP will take approximately one minute to become operational.

MOSE225

Adding APs to an Installed ITS

For Core APs, complete the following additional steps: a) Connect the first Remote Antenna to the Core AP using the UTP and Coaxial cable connectors labeled RA 1 in Figure 4-19.

b) Connect the second Remote Antenna to the Core AP using the UTP and

Coaxial cable connectors labeled RA 2 in Figure 4-19.

c) Be sure to label the UTP cable bundles and the Remote Antennas themselves as RA 1 and RA 2 corresponding to the cable connections you made in steps a and b d) Reboot the Core AP by disconnecting its cable.

e) Observe the Remote Antenna’s status LEDs to verify that the Remote

Antenna is powered and operational.

9. In the Device view, verify that the AP appears associated under the appropriate

APC and in the appropriate AP group.

10. Select each newly added AP, and then click on the Status tab for that AP and verify that the IP address shown for the AP is correct.

Note If you encounter a Duplicate IP address system-level alert after adding an Access

Point to an ITS, then reconfigure the AP with a unique IP address, and then reset the

AP.

Run the Upgrade Wizard periodically as APs are added to the system (e.g., every

12 newly added APs).

11. Shutdown the APC web interface browser session, and then run the Philips

Upgrade Wizard to verify the APC and AP configurations system wide, and save

the ITS configuration files as described on page 4-4.

12. Add new ITS devices to the Configuration Wizard.

IntelliVue Telemetry System Infrastructure Installation and Service Guide 4 27

MOSE225

Chapter 4: Expanding or Modifying an Installed ITS

Renaming Newly Installed APs and Remote Antennas

You can change the names of installed Standard APs, Core APs, and Remote

Antennas from their default values to more user-friendly names by following these steps:

1. Click on the APC in the APC web interface that is associated with the newly added APs and Remote Antennas you wish to rename.

2. Click the NAMES tab.

The AP and Remote Antenna Friendly Name Management screen appears as shown in Figure 4-21.

Figure 4-21: Renaming APs and RAs

3. Enter meaningful, user-friendly names for the installed Standard APs, Core APs, and Remote Antennas in the AP Name and RA Name fields.

You may enter a string of up to 32 characters for the name values.

Standard APs will list Remote Antennas as Not Present. Core APs will provide general status of connected Remote Antennas.

4. Click SAVE and then verify the AP Configuration settings.

5. Shutdown the APC web interface browser session, and then run the Philips

Upgrade Wizard to verify the APC and AP configurations system wide, and save

the ITS configuration files as described on page 4-4.

Adding New AP Groups to an Existing ITS Configuration

As described in “Planning Your AP Groupings” on page 2-18, an AP Group allows for

logically associated Access Points within a clinical unit to be given a common set of configurations. These configurations govern everything from AP to APC partnership rules, RF Channel and Access Code usage and Alert Settings.

4-28

MOSE225

Adding New AP Groups to an Existing ITS Configuration

Add the New AP

Groups

The AP Groups within the system should logically map to the Clinical Units that have been established for the monitoring network and databases.

If additional APCs are being added to the ITS infrastructure, then make sure that they have already been added to the system prior to adding the new AP groups.

Prior to beginning this procedure, ensure that you have the following information for each new AP group to be added:

• AP Group Name

• AP Group type (Smart-hopping)

• Partnered APC

• Alert Destination

To add a new AP group to an existing ITS configuration:

1. Connect to the APC web-based management interface.

2. Select the Groups View in the APC web interface drop-down menu and then click the GO! button.

3. Click ADD GROUP at the bottom left of the screen.

Configure the

New AP Groups

Figure 4-22: Adding New AP Group

4. In the Add New Group screen (Figure 4-22), configure the following settings:

• Group Name - Set as documented in AP Group Configurations Worksheet

(no spaces in name)

• Group Type - Set to Smart-hopping

• Group Description - Optional. Enter a description for this AP Group. Typically, you may want tenter the name of the clinic, unit, or department in which the

APS are installed.

5. Click the ADD GROUP button. Repeat Steps 3 to 5 for each AP Group being added on this system. When all AP Groups have been added, click the

NETWORK button to return to the View Groups tree screen.

For each AP Group that has been added, complete the follow steps:

1. In the View Groups tree, select an AP Group that was created and select the

BASIC SETTINGS tab.

IntelliVue Telemetry System Infrastructure Installation and Service Guide 4 29

MOSE225

Chapter 4: Expanding or Modifying an Installed ITS

1.4 GHz AP

Configuration

2.4 GHz AP

Configuration

In the 1.4 GHz AP Group Configuration Basic Settings screen, set the following configuration for this AP Group:

• Select the appropriate APC for this AP group from the Partnered AP

Controller drop-down list. Refer to your completed AP Group Configuration

Worksheet.

In the 1.4 GHz AP Group Configuration Basic Settings screen, verify the following configurations for this AP Group. If they are not correct, delete the AP

group and then edit the AP default settings (see page 3-27):

• Set the WMTS Channels as appropriate for your geography and as documented in the 1.4 GHz Access Point Default Configuration Worksheet.

• Set the RF Access Code field as documented in the 1.4 GHz Access Point

Default Configuration Worksheet, and set the Enable Box to CHECKED.

• Set the Subnet Mask and Default Gateway fields as documented in the 1.4

GHz Access Point Default Configuration Worksheet.

In the 2.4 GHz AP Group Configuration Basic Settings screen, set the following configurations for this AP Group:

• Select the appropriate APC for this AP group from the Partnered AP

Controller drop-down list. Refer to your completed AP Group Configuration

Worksheet.

In the 2.4 GHz AP Group Configuration Basic Settings screen, verify the following configurations for this AP Group. If they are not correct, delete the AP

group and then edit the AP default settings (see page 3-28):

• Select the Radio Regulations from the drop-down list that apply to the country in which you are installing the 2.4 GHz ITS as documented in the

2.4 GHz AP Default Configuration Worksheet.

• Select the Frequency Plan from the drop-down list to specify the 802.11 channel configuration with which the 2.4 GHz ITS will co-exist.

• Select the ZigBee channel used for medical purposes at the installation site from the drop-down list as documented in the 2.4 GHz AP Default

Configuration Worksheet.

• Set the RF Access Code field as documented in the 2.4 GHz Access Point

Default Configuration Worksheet, and set the Enable Box to CHECKED.

• Set the Subnet Mask and Default Gateway fields as documented in the 2.4

GHz Access Point Default Configuration Worksheet.

2. Click SAVE and then verify that the AP Group Basic Configuration settings are correct.

3. Select the ALERTS SETTINGS tab.

In the AP Group Configuration Alerts Settings screen, set the following configurations for this AP Group:

• Alert Destination - Set as documented in the AP Group Configuration

Worksheet.

• Sync Loss Alert - Verify all boxes are CHECKED.

4-30

MOSE225

Adding ITS Monitoring Devices

Figure 4-23: AP Group Configuration Alert Settings

4. Click SAVE and then verify the AP Group Alerts Configuration settings are correct.

5. Select the ALERTS SETTINGS tab again. In the AP Group Configuration Alerts

Settings screen, click on the Click Here link at the bottom of the screen to display the AP Group Configuration Advanced Alerts Settings screen

(See Figure 3-22 on page 3-33.)

The settings in the Advanced Alerts Settings screen will be populated as part of

the factory defaults. Verify the correct settings against Figure 3-22 on page 3-33.

6. Click SAVE and then verify the AP Group Configuration Advanced Alerts Results page.

7. Repeat Steps 1 to 6 until you have configured every AP group that you have added to the system.

8. Shutdown the APC web interface browser session, and then run the Philips

Upgrade Wizard to verify the APC and AP configurations.

Adding ITS Monitoring Devices

Before adding ITS patient-worn devices or bedside monitors, you must configure new equipment labels into the DBS. This may need to be done manually for live, active systems.

Adding new patient-worn devices to the system generates new DCHP entries that forces automatic system replication of the configuration file from the Master APC to all Slave APCs. For this reason, we recommend that you run the Philips Upgrade

Wizard to verify the APC and AP configurations system wide, and save the ITS

configuration files as described on page 4-4 after adding any monitoring devices to

the ITS.

IntelliVue Telemetry System Infrastructure Installation and Service Guide 4 31

MOSE225

Chapter 4: Expanding or Modifying an Installed ITS

Replacing an AP, Remote Antenna, or APC in an Existing System

At some point during the life of your Philips Wireless Infrastructure, it may be necessary to replace a defective Access Point, Remote Antenna, or Access Point

Controller within an installed ITS. Follow the replacement procedures listed below.

Note The Test and Inspection procedures provided in Chapter 4 must be followed by

Philips Service Providers when the Philips IntelliVue Telemetry System is installed, and after any service event, upgrade, or repair.

Replacing an ITS Access Point

In the event of a failed AP, the following steps should be taken to replace it with a new one. Make note of the following settings for the AP that is to be replaced (write this information down and have it readily available):

• AP Name

• IP Address

• Subnet Mask

• Default Gateway

• Group Membership

Note You must assign the new replacement AP’s IP address as a static address. Assign the replacement AP the same IP address that was previously assigned to the old defective AP.

To replace an Access Point within an installed ITS:

1. Physically disconnect the defective AP from the system and remove it from its installation location.

2. Access the APC management interface and verify that the AP was removed and has moved to the Unregistered list. This may take several minutes to occur.

If the AP continues to stay in the registered list, uncheck the Enable AP button in its Configuration screen and then click the SAVE button at the bottom of the screen. This will force the AP to move to the Unregistered list. Before disabling the AP, ensure that you have selected the correct AP, especially on a “live” system that is monitoring patients.

Note One way to verify that an AP that has been disconnected but has not yet fallen to the

Unregistered list, is to click on the Status tab for that AP after it has been disconnected but still remains in the registered list. Such an AP will report an error message if its status is requested.

3. Once the AP is in the Unregistered list, select it (so that it highlights), and then click on the Delete AP button at the bottom of the screen (on the left side).

4-32

MOSE225

Replacing an AP, Remote Antenna, or APC in an Existing System

4. After the above steps have been completed, continue with the procedure,

“Adding APs to an Installed ITS” on page 4-21.

5. Shutdown the APC web interface browser session, and then run the Philips

Upgrade Wizard to verify the APC and AP configurations.

Replacing a Remote Antenna

To replace a Remote Antenna (RA) connected to a Core AP:

1. Disconnect the UTP and Coax cables from the failed Remote Antenna and physically remove the RA from its mounting location.

2. Mount the replacement RA and note its ID number.

3. Reconnect the UTP and Coax cables from the Core AP.

4. Reboot the Core AP to detect the presence of the new RA. You can reset the

Core AP from the APC web interface.

5. Verify that the RA is powered and connected properly by observing the RA’s two status LEDs.

The Core AP and its connected Remote Antenna(s) will be auto-detected by the

APC after the Core AP has been rebooted/reset.

Although the RA’s ID number has changed, its friendly name mapping has not, so the RA will continue to work as normal at its installed location.

Replacing an ITS APC

Prior to removing an APC from the system, note the following information:

• APC IP Address

• APC Name

• APC Firmware Revision

• AP Groups and APs that are/were partnered with the APC

To replace a Slave APC on an existing system, perform the following steps:

1. Disconnect the Slave APC from the system.

Note Note that Step 1 may cause some system dropouts as “orphaned” APs are picked up by the existing APCs. If this is being done on a “live” system, ensure that all appropriate clinical personnel have been notified of its potential impact.

2. Access the APC management interface and verify that all of the orphaned APs have been picked up by the other APC using the APC management screens.

Ensure that the system is stable and that all configuration parameters are correct. It will be “normal” for APs “orphaned” by the missing APC to have been picked up by the remaining APC(s).

3. Power up the replacement APC but do not connect it to the network.

IntelliVue Telemetry System Infrastructure Installation and Service Guide 4 33

MOSE225

Chapter 4: Expanding or Modifying an Installed ITS

4. Perform the procedure “Step 4. Perform Initial Configuration of the APCs to be

Installed.” on page 3-12.

5. With the replacement APC’s power cord disconnected, connect the replacement

APC to the network where the old APC was connected ensuring it is on the same subnet as the other APCs on the system.

6. Power up the replacement APC.

7. Access the APC management interface and verify that the replacement APC shows up on the device list. It will show up with its MAC address as its name. Set the APC name to the value of the APC it replaced and click the SAVE button.

8. Reconfigure the AP Groups that were partnered with the replaced “bad” APC.

Point the Groups to the new APC (Partnered APC). If configuration was done properly all APs associated with the group should now be partnered with the replacement APC.

Reconfigure each AP group from the ‘old’ APC to the new ‘APC’ as follows: a) Select the existing AP Group that was assigned to the old, failed APC, and then click on the Group Membership tab.

b) Selected all APs that were assigned to the existing AP Group, and then click the right arrow button to un-assign all APs from the group.

The APs are assigned to the default group ‘WMTS.’ c) Create a new AP Group for the new, replacement APC.

d) Select the new AP Group, and then click on the Group Membership tab.

Selecting a maximum of five APs at a time that were unassigned from the old AP Group, click the left arrow button to assign the APs to the new AP

Group associated with the new, replacement APC.

Repeat Step d until you have moved all APs that were unassigned from the old AP Group to the new AP Group.

Note Reassign no more than five APs at a time to reduce the configuration load on the

APC.

9. Shutdown the APC web interface browser session, and then run the Philips

Upgrade Wizard (see page 3-34) to verify the APC and AP configurations.

4-34

MOSE225

5

Note

Troubleshooting and Testing

This chapter provides procedures you should follow to inspect and verify your IntelliVue Telemetry System, and includes:

• ITS Access Point Test and Inspection Procedures

• ITS Access Point Controller Test and Inspection Procedures

• ITS Sync Unit Test and Inspection Procedures

• ITS Power over Ethernet Unit Test and Inspection Procedures

• ITS Uninterruptible Power Supply Test and Inspection Procedures

• Using the PWD Coverage Assessment Mode

• Troubleshooting Known Issues

• Importing ITS Configuration Files

You must follow the tests and inspections provided in this chapter after you initially install the IntelliVue Telemetry System and also after you perform any service event on the ITS.

IntelliVue Telemetry System Infrastructure Installation and Service Guide 5 1

MOSE225

Chapter 5: Troubleshooting and Testing

ITS Access Point Test and Inspection Procedures

Table 5-1 lists which tests you must perform when performing service events on

IntelliVue Telemetry System Access Points.

Table 5-1: ITS Access Point Test and Inspection Requirements

When Performing this Service Event...

Installation

Preventive Maintenance

Any component repair or replacement

Hardware Upgrade

Software Upgrade

All other Service Events

Complete These Required Test(s)

Visual, Power On, Performance

N/A

Power On, Performance

N/A

Power On, Performance, Revision Check

Visual, Power On, Performance

Test Block

Name

AP Visual

AP Power On

AP Performance

AP Revision

Check

AP Safety

Table 5-2: ITS Access Point Test and Inspection Matrix

Test or Inspection to Perform

Inspect all system components for obvious damage.

Visually inspect all system components, Remote

Antennas, cables, and connectors. Check for signs of abrasion, wear, or other damage. Check the fixed antennas for secure connection, proper orientation and direction.

With power connected to each active Network device, observe that all lights visible on the front panel are in proper status and that no error conditions are shown.

Verify that Link and Power/Sync LEDs on Core AP are lit

GREEN. Verify that GREEN and YELLOW status LEDS on

Remote Antennas are lit solid. See Cluster AP LED

descriptions on page 1-6.

Note that for 1.4 GHz Core APs and 2.4 GHz Standard

APs, you can view the Power, Network, and Radio LEDs from the AP Status page in the APC web interface.

Remote Antenna status can be checked from the

Names tab in the APC web interface.

Does the AP appear in the AP web browser management screens? Does data from a wireless device appear at the Information Center?

Does the revision reported in the APC web browser screen match the revision loaded? Run the Philips

Upgrade Wizard to check and verify final configurations.

No safety test is required

Expected Results

No visible damage

Devices power up into expected status; no error indications are shown.

Expected answers are “Yes”. If so,

Performance test passed.

Expected answer is

“Yes”. If so, Revision

Check test passed.

Information to

Record on

Service Record

V:P or V:F where:

P = Pass

F = Fail

PO:P or PO:F where:

P = Pass

F = Fail

P:P or P:F where:

P = Pass

F = Fail

RC:P or RC:F where:

P = Pass

F = Fail

S:NA where:

NA=Not

Applicable

5-2

MOSE225

ITS Access Point Controller Test and Inspection Procedures

ITS Access Point Controller Test and Inspection Procedures

Table 5-3 lists which tests you must perform when performing service events on

IntelliVue Telemetry System Access Point Controllers.

Table 5-3: ITS Access Point Controller Test and Inspection Requirements

When Performing this Service Event...

Installation

Preventive Maintenance

Any component repair or replacement

Hardware Upgrade

Software Upgrade

All other Service Events

Complete These Required Test(s)

Visual, Power On, Performance

N/A

Power On, Performance

N/A

Power On, Performance, Revision Check

Visual, Power On, Performance

Test Block

Name

APC Visual

APC Power On

APC Performance

APC

Revision Check

APC Safety

Table 5-4: ITS Access Point Controller Test and Inspection Matrix

Test or Inspection to Perform Expected Results

Inspect all system components for obvious damage. Visually inspect all system components, cables, and connectors. Check for signs of abrasion, wear, or other damage.

With power connected to each active Network device, observe that all lights visible on the front panel are in proper status and that no error conditions are shown. The following are normal conditions:

• Power LED - On Green (862147 only)

• Network Utilization LEDs - See page 1-10

• 100 BaseT LED - On solid Green

• Master/Slave LED - On solid Green: Master, On solid Amber: Slave

• Link/Act (862147 only) - On primarily Amber, flashes when network activity is present

• Link/Act (865346 only) - On primarily Green, flashes when network activity is present

Does the APC appear in the APC web browser management screens? Does data from a wireless device associated with this APC appear at the

Information Center?

Does the revision reported in the APC web browser screen match the revision loaded? Run the Philips

Upgrade Wizard to check and verify final configurations.

No safety test is required

No visible damage

Devices power up into expected status; no error indications are shown.

Expected answers are

“Yes”. If so, Performance test passed.

Expected answer is “Yes”. If so, Revision Check test passed.

Information to

Record on

Service Record

V:P or V:F where:

P = Pass

F = Fail

PO:P or PO:F where:

P = Pass

F = Fail

P:P or P:F where:

P = Pass

F = Fail

RC:P or RC:F where:

P = Pass

F = Fail

S:NA where:

NA=Not

Applicable

IntelliVue Telemetry System Infrastructure Installation and Service Guide 5 3

MOSE225

Chapter 5: Troubleshooting and Testing

ITS Sync Unit Test and Inspection Procedures

Table 5-5 lists which tests you must perform when performing service events on

IntelliVue Telemetry System Sync Unit.

Table 5-5: ITS Sync Unit Test and Inspection Requirements

When Performing this

Service Event...

Installation

Preventive Maintenance

Any component repair or replacement

Hardware Upgrade

Software Upgrade

All other Service Events

Complete These Required Test(s)

Visual, Power On, Performance

N/A

Power On, Performance

N/A

N/A

Visual, Power On, Performance

Test Block

Name

Sync Unit Visual

Sync Unit

Power On

Sync Unit

Performance

Sync Unit

Revision Check

Sync Unit

Safety

Table 5-6: ITS Sync Unit Test and Inspection Matrix

Test or Inspection to Perform

No safety test is required

Expected Results

Inspect all system components for obvious damage. Visually inspect all system components, cables, and connectors. Check for signs of abrasion, wear, or other damage.

With power connected to each active Network device, observe that all lights visible on the front panel are in proper status and that no error conditions are shown.

Following are normal conditions for each LED:

- Power LED - On GREEN

- Ext Ref LED - Off

- Sync In LED - if Sync is Master - Off

- if Sync is Slave - On

Are there active Sync Unit alerts in Wireless

Status Log?

Do all associated APs appear as registered in the APC web browser management screens?

No visible damage

Devices power up into expected status; no error indications are shown.

Expected answer is

“No.”

Expected answer is

“Yes”. If so,

Performance test passed.

No Revision Check is required.

Information to

Record on

Service Record

V:P or V:F where:

P = Pass

F = Fail

PO:P or PO:F where:

P = Pass

F = Fail

P:P or P:F where:

P = Pass

F = Fail

RC:NA where:

NA=Not

Applicable

S:NA where:

NA=Not

Applicable

5-4

MOSE225

ITS Power over Ethernet Unit Test and Inspection Procedures

ITS Power over Ethernet Unit Test and Inspection Procedures

Table 5-7 lists which tests you must perform when performing service events on

IntelliVue Telemetry System PoE Unit.

Table 5-7: ITS PoE Unit Test and Inspection Requirements

When Performing this

Service Event...

Installation

Preventive Maintenance

Any component repair or replacement

Hardware Upgrade

Software Upgrade

All other Service Events

Complete These Required Test(s)

Visual, Power On

N/A

Power On

N/A

N/A

Visual, Power On

Test Block

Name

PoE Unit Visual

PoE Unit

Power On

PoE Unit

Performance

PoE Unit

Revision Check

Sync Unit

Safety

Table 5-8: ITS PoE Unit Test and Inspection Matrix

Test or Inspection to Perform

Inspect all system components for obvious damage. Visually inspect all system components, cables, and connectors. Check for signs of abrasion, wear, or other damage.

With power connected to each active

Network device, observe that all lights visible on the front panel are in proper status and that no error conditions are shown.

Verify that the AC LED on front panel is solid GREEN. Verify that the Link LED is lit GREEN for each connected cable.

No performance check is required.

Expected Results

No visible damage

Devices power up into expected status; no error indications are shown.

Information to

Record on

Service Record

V:P or V:F where:

P = Pass

F = Fail

PO:P or PO:F where:

P = Pass

F = Fail

No revision check is required.

No safety test is required

P:NA where:

NA=Not

Applicable

RC:NA where:

NA=Not

Applicable

S:NA where:

NA=Not

Applicable

IntelliVue Telemetry System Infrastructure Installation and Service Guide 5 5

MOSE225

Chapter 5: Troubleshooting and Testing

ITS Uninterruptible Power Supply Test and Inspection Procedures

Table 5-9 lists which tests you must perform when performing service events on

IntelliVue Telemetry System UPS.

Table 5-9: ITS UPS Test and Inspection Requirements

When Performing this

Service Event...

Installation

Preventive Maintenance

Any component repair or replacement

Hardware Upgrade

Software Upgrade

All other Service Events

Complete These Required Test(s)

Visual, Power On

N/A

Power On

N/A

N/A

Visual, Power On

Test Block

Name

UPS Visual

UPS

Power On

UPS

Performance

UPS

Revision Check

UPS

Safety

Table 5-10: ITS UPS Test and Inspection Matrix

Test or Inspection to Perform

Inspect all system components for obvious damage. Visually inspect all system components, cables, and connectors. Check for signs of abrasion, wear, or other damage.

With power connected to each active

Network device, observe that all lights visible on the front panel are in proper status and that no error conditions are shown.

No performance check is required.

Expected Results

No visible damage

Devices power up into expected status; no error indications are shown.

Information to

Record on

Service Record

V:P or V:F where:

P = Pass

F = Fail

PO:P or PO:F where:

P = Pass

F = Fail

No revision check is required.

No safety test is required

P:NA where:

NA=Not

Applicable

RC:NA where:

NA=Not

Applicable

S:NA where:

NA=Not

Applicable

5-6

MOSE225

ITS Network Switch Test and Inspection Procedures

ITS Network Switch Test and Inspection Procedures

Table 5-9 lists which tests you must perform when performing service events on

IntelliVue Telemetry System network switches.

Table 5-11: ITS UPS Test and Inspection Requirements

When Performing this

Service Event...

Installation

Preventive Maintenance

Any component repair or replacement

Hardware Upgrade

Software Upgrade

All other Service Events

Complete These Required Test(s)

Visual, Power On

N/A

Power On

N/A

N/A

Visual, Power On

Test Block

Name

Network Switch

Visual

Network Switch

Power On

Network Switch

Performance

Network Switch

Revision Check

Network Switch

Safety

Table 5-12: ITS Network Switch Test and Inspection Matrix

Test or Inspection to Perform

Inspect all system components for obvious damage. Visually inspect all system components, cables, and connectors. Check for signs of abrasion, wear, or other damage.

With power connected to each active

Network device, observe that all lights visible on the front panel are in proper status and that no error conditions are shown.

Verify the Power LED is solid green and that the LINK LED for each port with a cable connected is green.

If present, check port speed and duplex

LEDs.

No performance check is required.

Expected Results

No visible damage

Devices power up into expected status; no error indications are shown.

Information to

Record on

Service Record

V:P or V:F where:

P = Pass

F = Fail

PO:P or PO:F where:

P = Pass

F = Fail

No revision check is required.

No safety test is required

P:NA where:

NA=Not

Applicable

RC:NA where:

NA=Not

Applicable

S:NA where:

NA=Not

Applicable

IntelliVue Telemetry System Infrastructure Installation and Service Guide 5 7

MOSE225

Chapter 5: Troubleshooting and Testing

In addition to completing the procedures listed in the previous sections to validate the network switch installations, you must perform and document completion of the detailed site-specific T&I procedure provided to you by your Philips network design engineer.

For each ITS installation site, Philips FSEs will receive a detailed customized T&I procedure that will require completion of the following tasks at the clinical installation site:

• Verify that the running configuration on each network switch matches the configuration defined in the switch’s configuration file.

• Verify the interconnection between switches. Inspect the status trunk interfaces, and verify that the trunk VLAN information is correct and that no

VLAN pruning is occurring.

• Verify that each switch can communicate with other switches on the network by verifying the CDP neighbor information for the switches.

• Verify that the Spanning Tree Protocol (STP) has been implemented correctly.

• Verify that each switch can communicate with other switches on the network by pinging each switch’s CDP neighbors.

• Connect the Philips patient monitoring devices to the network switches and conduct a “pre-go live” test that includes:

- Execute a show interfaces command on each switch to verify its VLAN settings and device port status.

- Execute a show logging command on each switch to verify that the proper logging settings have been enabled for the switch.

- Execute a show vlans command on each switch to verify that the proper

VLAN settings have been enabled for the switch.

- For each switch, attempt to ping each locally connected patient monitoring device.

5-8

MOSE225

Using the PWD Coverage Assessment Mode

Using the PWD Coverage Assessment Mode

To facilitate ITS installations, you can configure the Philips TRx/TRx+ Transceivers

(i.e., patient-worn devices (PWDs)) to operate in Coverage Assessment Mode.

Operating a PWD in Coverage Assessment Mode will assist you in making a gross assessment of RF coverage within the ITS network.

Prerequisites

Note the following prerequisites to operating the PWD in Coverage Assessment

Mode:

• You must have a Philips Model TRx4841A/4851A Transceiver to use Coverage

Assessment Mode. Coverage Assessment Mode is not available on the M2601B

Transmitter.

• You must install and be familiar with use of the Philips Telemetry Service Tool

(TeleCfg.exe) to use Coverage Assessment Mode.

Use of the Philips Telemetry Service Tool is fully described in the

Telemetry Service

Tool Installation Note and Instructions for Use

(P/N 453564087971).

Procedure

To set a transceiver to operate in coverage assessment mode, perform the following steps:

1. Connect the Telemetry Service Tool to the transceiver as described in the

Telemetry Service Tool Installation Note and Instructions for Use

document.

2. To enable the device to be used as a non-monitoring meter, click on the Edit

Form button in the Device Type display screen.

3. Enter the desired RF Access Code to enable the Transceiver to connect to your

ITS.

4. Disable the RF Auto Shutoff feature by unmarking the checkbox.

5. Enable the Coverage Assessment Mode field by marking the checkbox.

6. Click the Update Device Configuration button.

7. Click OK to set the coverage mode configuration for the connected device.

8. Select the Actions --> Read Device menu, and verify that the Coverage

Assessment Mode checkbox is marked. If so, the transceiver is ready to use as a standalone RF assessment tool.

If the checkbox is unmarked, the transceiver is still set in monitoring mode.

9. Disconnect the cable from the device, and from the PC.

10. Reboot the device.

11. When finished, close the TeleCfg.exe program or go to another feature of the tool.

IntelliVue Telemetry System Infrastructure Installation and Service Guide 5 9

MOSE225

Chapter 5: Troubleshooting and Testing

Note You must disable Coverage Assessment Mode before using the Transceiver as a patient monitoring device. To disable Coverage Assessment Mode, repeat the above steps and unmark the Coverage Assessment Mode checkbox.

PWD Received Signal Strength Indications

When configured as an RF Coverage Assessment Tool, the Transceiver battery

gauge LED indicators signify the received signal strength. Refer to Table 5-13 for an

explanation of these indicators.

Table 5-13: PWD Received Signal Strength Indications

Gauge

4 Green LEDs

3 Green LEDs

2 Green LEDs

1Green LED

1 Red LED

1 Red LED

Signal Strength

> - 49dBM

- 50 to - 59dBm

- 60 to - 69dBm

-70 to -75dBm

< -75dBM

Status

Good Signal Strength

Good Signal Strength

Good Signal Strength

Marginal Signal Strength

Weak Signal Condition

No Access Point

Connection

Audio Feedback

None

None

None

None

None

Out of Range

Troubleshooting Known Issues

Please note the following known issues associated with the Upgrade Wizard.

• Issue: The Upgrade Wizard may generate errors when roaming back APs to an

APC; especially when that APC failed to be upgraded (e.g., due to an MAPC response timeout).

When first started, the Upgrade Wizard will scan the overall ITS and build its system configuration. From that point on, the Upgrade Wizard does not scan the

ITS again. It is possible that the actual ITS configuration may change (e.g., APC-

AP-PWD partnerships may change) in the interim. Such a change would make the Upgrade Wizard configuration different from that of the actual ITS.

• Workaround: The Upgrade Wizard can be terminated safely at any time. We recommend that you do not run the Upgrade Wizard for a very long time (in a single activation). It is best to run the Upgrade Wizard to complete a specific set of tasks and then re-run it again to complete the next set of tasks. Periodically, restarting the Upgrade Wizard allows it to re-scan and update its overall ITS configuration and allow its configuration to remain in sync with that of the actual ITS.

• Issue: Version A.00.16 of the Upgrade Wizard may falsely report the completion of an APC upgrade when in fact the APC has not been upgraded.

When upgrading an ITS system with the Force upgrade of APC option selected, a message indicating “APC upgraded” appears almost immediately after the upgrade process for the selected APC begins. The power LED on the selected

5-10

MOSE225

Troubleshooting Known Issues

APC does not change to amber from green, indicating a reboot, nor is there an

Upgrade Wizard message indicating a reboot of the APC.

• Workaround: If you suspect that an APC was not upgraded properly, then re-run the Upgrade Wizard with the Only Check Configuration option selected to confirm the completion of the upgrade process.

• Issue: After an APC has been upgraded, any roamed APs need to be roamed back to the upgraded APC. Although it seems that the roamed APs have been roamed back successfully, Version A.00.16 of the Upgrade Wizard may show the screen to roam back APs and not let a user to advance to the next screen to upgrade other APCs.

• Workaround: If you encounter this situation where you cannot advance beyond the “AP Roam Back” screen, click Cancel to exit the Upgrade Wizard, and then re-run the Upgrade Wizard with the Only Check Configuration option selected to confirm that the patient-worn transceivers have been roamed back correctly.

Be sure to refer to the following list of known issues when troubleshooting operation of an installed ITS:

• Issue: After an installed, powered Remote Antenna was disconnected from and then reconnected to its Core AP via its Coax/UTP cable bundle, the Remote

Antenna failed to start communicating with the Core AP.

Solution: You must power cycle the Core AP to re-establish communications with its connected Remote Antenna.

• Issue: An ITS Access Point fails “System Validation.” The IP address in the APC

AP configuration screen does not match the IP address in the AP status screen.

The Bootp address is displayed in the AP status screen.

Solution: The AP never received the configured IP address change. Simply power cycle the AP so that it loads its configuration properly.

• Issue: On a routed topology, the first message to transceiver doesn’t make it all the way through the network and the label assignment for each transceiver must be done twice.

Solution: Perform the label assignment twice, or upgrade the IIC to Release G or

F.00.43 (FCO86200523). In these IIC releases, the message is sent twice automatically.

• Issue: The UPS connected to ITS infrastructure devices overloads.

Solution: During ITS design process, ensure that the power rating of the UPS is

not exceeded by the connected devices. Refer to Table 1-13 on page 1-30 for a

list of ITS infrastructure device power draws.

• Issue: “Local Sync Loss” alerts reported by fourth-tier Sync Unit in Sync

Network.

Solution: Install latest released version of the Sync Unit to correct this known issue. Refer to Service Bulletin SB86200365 – “New Part Number and Change to Repair Strategy for Philips Sync Unit.”

• Issue: Some ITS Access Points were shipped with an incorrect MAC address range. Such APs will not appear automatically in the APC web-based management interface.

IntelliVue Telemetry System Infrastructure Installation and Service Guide 5 11

MOSE225

Chapter 5: Troubleshooting and Testing

Solution: Refer to Service Bulletin SB86200390 – 862113 for details. Manually

add the AP to the ITS by following the procedure “Adding an AP via Manual MAC

Address Input” on page 4-26.

• Issue: On an IIC with the Device Location application installed, “No Location” is displayed.

Solution: The Access Point being reported by the transceiver is not known to the

IIC. Enter all Access Points into Config Wizard in the DBS or standalone IIC to correct this problem.

• Issue: The clinical user is unable to take a patient out of Standby from the IIC.

The IIC must be able to send a message to an APC for a clinician to be able to take a patient out of Standby from the IIC. If the IIC cannot contact an APC, then the clinician will not be able to take a patient out of Standby from the IIC. Note, however, the clinician could alternatively take the patient out of Standby at the transceiver by pressing the transceiver’s Check button.

Solution: Enter all All APCs into Config Wizard in the DBS or standalone IIC to correct this problem.

• Issue: You encounter a Duplicate IP address system-level alert after adding an

Access Point to an ITS.

Solution: Reconfigure the AP with a unique IP address, and then reset the AP.

• Issue: Running the Philips Upgrade Wizard fails to upgrade an APC on the ITS.

Solution: You must disconnect the APC from the ITS, recycle power to the APC, reconnect the APC to the ITS, and then run the Philips Upgrade Wizard again.

• Issue: The error dialog shown below reappears repeatedly each time you click

Retry.

Solution: Click Skip to bypass this AP in the upgrade process. After the upgrade process completes, you must then run the Upgrade Wizard again to upgrade the

AP that was bypassed.

• Issue: A newly AP is not listed in the APC web interface.

Solution: In the APC web interface, click System in the View Device tree, click

Configure and then select the Advanced tab. Verify that the Allow new APs to be added automatically option is set to True.

• Issue: An APC disappears from the APC web interface after being upgraded.

Solution: Recycle power to the APC. Note, do not disconnect the APC from the

ITS before cycling its power.

5-12

MOSE225

Importing ITS Configuration Files

Importing ITS Configuration Files

The Philips Upgrade Wizard can import an APC/AP configuration file (for the purposes of restoring a configuration) by running the Philips Upgrade Wizard from the command line.

Note The configuration file import process should only be done by a Phillips-trained service person who is familiar with the ITS installation and only in the case of system disaster recovery (i.e., the IntelliVue Telemetry System monitoring is completely not working).

An APC configuration file is MAC address-specific and can only be imported back into the system from which it was originally exported.

This import process must not be done on active clinical systems.

Use Revision A.00.16 (or later) of the Philips Upgrade Wizard to compete the configuration file import.

To ensure that the configuration import works properly, you must follow these steps:

1. Ensure that all APCs that were online when the export file was created are online before the file import is initiated.

2. Remove all APs from the network by powering down the appropriate PoE Units.

3. To import a configuration to the master APC, execute the following command and options from the Windows command line:

C:\Telemetry Upgrader\Upgrader.exe -writemasterconfig -importDelay 20 -import <filename> where:

<filename> is a previously exported configuration file.

-importDelay 20 is the typical delay setting. You may set the delay from

10

to

100

milliseconds as appropriate for your network.

4. After the Upgrade Wizard is started from the command line, make the following settings as appropriate for your network:

• Select the appropriate AP type, 1.4 GHz, 2.4 GHz, Core APs when the wizard starts.

• Select the Do not upgrade and Only check configuration options for the APC when the wizard starts.

• Select the Do not upgrade option for the APs when the wizard starts.

5. When the Upgrade Wizard prompts you to select the APC to upgrade

(Figure 5-1), select the Master APC first.

IntelliVue Telemetry System Infrastructure Installation and Service Guide 5 13

Chapter 5: Troubleshooting and Testing

MOSE225

Figure 5-1: Select the APC to Upgrade

6. Note the messages displayed by the Upgrade Wizard summarizing the status of the configuration file import.

Figure 5-2 shows the status messages displayed for a successful configuration file import.

5-14

Figure 5-2: Status Messages for a Successful Configuration File Import

7. Select the next APC to upgrade (Figure 5-1) when prompted.

8. Repeat step 7 until you have upgraded each of the APCs on the ITS.

MOSE225

Importing ITS Configuration Files

After the import process is complete, you must:

1. Run the Philips Upgrade Wizard configuration check to verify the ITS configuration.

2. Add the APs back onto the network: a) Add multiple APs back onto the network by powering up a PoE Unit.

b) Verify that newly added APs appear in the APC web interface and then run

the Philips Upgrade Wizard. See page 3-42 for details.

Note Do NOT keep refreshing your web browser while waiting for the newly added APs to appear in the APC web interface. Refreshing the APC web interface too frequently will only slow down communications on the entire ITS.

c) Repeat Steps a and b until all APs have been added back to the network.

Note that all configuration files are imported in full except for the following:

• SYSTEM.TLV - This file is imported tag by tag, except for the following data which is ignored: APC Name, System Name, Configuration Key info, Web username/ password/config info, AP_CFG_PRESIDE.

• BOOTROM NVP - This file contains the APC MAC address and static IP address/ subnet mask/default gateway. These settings should only be edited using the bootloader serial menu on the APC.

IntelliVue Telemetry System Infrastructure Installation and Service Guide 5 15

Chapter 5: Troubleshooting and Testing

MOSE225

5-16

MOSE225

A

Installing Multiple ITSs at a Single Hospital Site

You can install up to 22 totally independent IntelliVue Telemetry Systems at a given installation site if you follow the configuration rules and guidelines given in this appendix. This appendix includes:

• General Requirements for Installing Multiple ITSs at a Site

• Transceiver Installation Requirements for Multiple ITSs

• Sync Network Requirements for Multiple ITSs

IntelliVue Telemetry System Infrastructure Installation and Service Guide A 1

MOSE225

Chapter A: Installing Multiple ITSs at a Single Hospital Site

General Requirements for Installing Multiple ITSs at a Site

Up to 22 totally independent IntelliVue Telemetry Systems can be installed per hospital.

The basic design rules for using multiple ITSs at a single installation site are:

• Each ITS must use a different RF Access Code (1 - 254) to ensure that the wireless clients (bedside monitors or patient-worn transceivers) connect to the correct APs. Each ICN Database Domain can support only a single unique RF

Access Code.

• Each Database Domain can have a single isolated ITS or be connected to a routed ITS subnet.

• Access Points on an isolated ITS cannot communicate with any other Database

Domains.

• Every wireless client in the hospital needs a unique Equipment Label (no duplication of labels).

• A common Sync Network is required if the ITSs are on adjacent floors, or if the linear distance between access points on the same floor is less than 300 feet.

• The ITSs do not have to be synchronized to each other if they are separated by two or more floors, or if the linear distance between access points on the same floor is greater than 300 feet.

Figure A-1 shows multiple ITSs installed at a single installation site.

A-2

Figure A-1: Multiple ITSs at a Single Installation Site

In the topology represented in Figure A-1, note that there is no connection to the

routers for ICN DBS #2 or DBS #22 and that is why an ITS can be added to those

Database Domains.

MOSE225

Transceiver Installation Requirements for Multiple ITSs

Transceiver Installation Requirements for Multiple ITSs

New installations or replacement of 1.4/2.4 GHz patient-worn transceivers require an association process to establish connection with the ITS infrastructure and the

ICN Central Station to get an equipment label assigned. Normal monitoring cannot proceed without the transceivers being assigned an equipment label.

Patient-worn Transceivers

When transceivers are shipped from the factory, they are shipped with an

Equipment Label of “New Device” and an RF Access Code of “0”. This allows them to connect to any access point (AP). However, a new transceiver will connect to the first access point it detects—not necessarily the AP that is closest.

If you do not see the MAC address appear in the Label Assignment screen (), then it is possible that the transceiver is connected to an access point associated with a different network. You will need to reboot the transceiver and then click the

“Refresh” key until you see the MAC address appear in the Label Assignment

Screen.

Extra MAC addresses in the Label Assignment Screen

if the systems are so close that it is likely that transceivers will connect to another system during the installation process, then it is likely that you will see extra MAC addresses in the Label Assignment screen. These would be transceivers from the other system that connected, but were not assigned a label because they connected to the wrong system.

Figure A-2: Assigning Labels to Patient-worn Transceivers

If a user wants to move an assigned portable device to a new area with a different

RF Access Code, then the portable device must be re-configured as a ‘new device’ with no equipment label assigned, And, at this stage the normal process to assign the portable device to the new AP group and Clinical care unit can take place as defined above.

IntelliVue Telemetry System Infrastructure Installation and Service Guide A 3

MOSE225

Chapter A: Installing Multiple ITSs at a Single Hospital Site

Sync Network Requirements for Multiple ITSs

Note the design rules for synchronization of multiple IntelliVue Telemetry Systems:

• A common Sync Network is required if the ITSs are on adjacent floors, or if the linear distance between system access points on the same floor is less than

300 feet.

Figure A-3: Common Sync Network Required

• The ITSs do not have to be synchronized to each other if they are not on adjacent floors, or if the linear distance between system access points on the same floor is greater than 300 feet.

A-4

Figure A-4: Common Sync Network Not Required

MOSE225

Sync Network Requirements for Multiple ITSs

Consider an example (Figure A-5) where a hospital wants three different ITSs to

provide wireless coverage to three units located on different floors.

Figure A-5: Sample Multiple ITS Coverage Requirements

In this example, because the PCU and CCU are on adjacent floors, but the ER is further away, the ITSs in PCU and CCU must be synchronized to each other, but the

ED system does not need to be synchronized to them.

Master Sync

Cable Delay Switch Set to 1

200 Ft. Sync Cable Length

Slave Sync

Cable Delay Switch Set to 2

Master Sync

Cable Delay Switch Set to 1

Figure A-6: Sample Multiple ITS Sync Network and Equipment Label Requirements

Note that all three ITSs must have different RF Access Codes configured and unique

Equipment Labels assigned.

IntelliVue Telemetry System Infrastructure Installation and Service Guide A 5

Chapter A: Installing Multiple ITSs at a Single Hospital Site

MOSE225

A-6

MOSE225

B

Routed Topology Configuration Information

This appendix provides important information to help you configure a routed ring ITS topology including:

• ICN and ITS Subnet Device IP Addresses

• Sample Routed Topology

IntelliVue Telemetry System Infrastructure Installation and Service Guide B 1

MOSE225

ICN and ITS Subnet Device IP Addresses

Table B-1: Routed DBSD Subnet and ITS Wireless Subnet Device IP Addresses

Device Types

(with Routed Subnet)

ICN DBSD Subnet IPs

Mask: 255.255.248.0

Network Subnet Address (Used in Config Wizard for Router)

Gateway Address

Router A – <used for ITS Wireless Subnet Router>

Router B – <used for ITS Wireless Subnet Router>

Reserved for Service PC

Network Switches and Remote Client Infrastructure

Reserved for Future Use

ITS APCs

IntelliVue 802.11 Devices

IntelliVue 802.11 Devices and legacy Proxim (RangeLAN2/Harmony) APs.

Note: Proxim devices are not supported on IIC Release J (or higher).

172.31.n.0

172.31.n.1

172.31.n.2

172.31.n.3

172.31.n.4 - 9

172.31.n.10 - 102

172.31.n.103 - 255

172.31.(n+1).0 - 63

172.31.(n+1).64 - 127

Reserved for Future Use

ITS AP Static Range (1.4/2.4 GHz)

172.31.(n+1).128 - 255

ITS APC Bootp/DHCP Server Range 2 for 1.4/2.4 GHz APs

Database Server (NIC 1)

Application Server (NIC 1)

Information Centers (NIC 1)

Information Center Clients

Printers (Set by BootP)

172.31.(n+3).0 - 15

172.31.(n+3).16 - 31

172.31.(n+3).32 - 63

172.31.(n+3).64 - 95

172.31.(n+3). 96 - 127

Reserved 172.31.(n+3).128 - 255

Bedside Monitors/Devices (Wired & ISM 2.4GHz) (Set By BootP)

Reserved for Future Use

ITS APC Bootp/DHCP Server Range 1 for Transceivers/Bedsides

Reserved for Future Use

Network Broadcast Address

172.31.(n+4).0 - 255

172.31.(n+5).0 - 255

172.31.(n+7).0 - 254

172.31.(n+7).255

DBSD Default

Gateway

172.31.n.1

172.31.n.1

172.31.n.1

172.31.n.1

Default blank

172.31.n.1

172.31.n.1

172.31.n.1

ITS Wireless Subnet IPs

Mask: 255.255.240.0

172.31.240.0

172.31.240.1

172.31.240.2

172.31.240.3

172.31.240.4-9

172.31.240.10 – 20

172.31.240.21 – 172.31.240. 255

172.31.241.0 – 127

172.31.241.128 - 255

172.31.242.0 – 172.31.244.127

172.31.244.128 - 172.31.246.255

172.31.247.0 - 255

172.31.248.0 – 172.31.253.255

172.31.254.0 – 172.31.255.254

172.31.255.255

ITS Default

Gateway

172.31.240.1

172.31.240.1

172.31.240.1

172.31.240.1

172.31.240.1

172.31.240.1

172.31.240.1

MOSE225

Sample Routed Topology

Refer to Table B-1 for a list of the device IP address assignments used in a routed

ICN configuration where the ITS infrastructure is installed as a separate subnet to which up to 22 Database Domains have access via routers.

Note the following regarding Table B-1:

• “n” represents the network number and starts at 0 for single ICN Database

Domains. This variable increments by 8 from there for additional ICN database

Domains. For example, for DBS 2, “n” would equal 8, for DBS 3, “n” would equal

16, and so on.

• Route statements are generated (in instances with a Router and without) at the completion of the Config Wizard.

Sample Routed Topology

Figure B-1 shows a sample routed ring topology.

Figure B-1: Sample Routed ITS Topology

In a routed ring ICN configuration, the ITS infrastructure is installed as a separate subnet to which multiple ICN Database Domains have access via routers. Note the following general guidelines for installing the ITS within a routed ICN topology:

• An ITS subnet can be connected up to 22 ICN Database Domains via routers.

• Up to 320 ITS Access Points may be installed on a routed ICN topology.

• The 1.4 GHz ITS or 2.4 GHz ITS may be installed within a routed ICN topology.

Note the following possible port connections and device IP address assignments for this sample topology shown in Figure B-1:

IntelliVue Telemetry System Infrastructure Installation and Service Guide B 3

MOSE225

Chapter B: Routed Topology Configuration Information

ITS Wireless Subnet

The ITS infrastructure devices reside on the ITS wireless subnet which has a subnet address of 172.31.240.0.

Router A is configured with an IP address of 172.31.240.2.

Router B is configured with an IP address of 172.31.240.3.

ITS_CORE_1 is configured with an IP address of 172.31.240.10 and connects to port 24 on Router A from port 24.

ITS_CORE_2 is configured with an IP address of 172.31.240.11 and connects to port 24 on Router B from port 24.

ITS_CORE_1 and ITS_CORE_2 have redundant connections to each other using their uplink ports.

APC_1 is configured with an IP address of 172.31.241.0.

APC_2 is configured with an IP address of 172.31.241.1.

Since there is only one Sync Unit on the ITS, it is considered to be the Master Sync

Unit and its front-panel Cable Delay Switch is set to 1.

There are eight 1.4 GHz Access Points on the ITS. They are named AP_1 to AP_8.

The Access Points are assigned IP addresses ranging from 172.31.242.0 (AP_1) to

172.31.242.7 (AP_8).

DBSD 1

ICN_1_CORE is configured with an IP address of 172.31.0.10 and connects to

Port 1 on Router A from Port 23 and to Port 1 on Router B from Port 24. The standalone IIC on ICN Database Domain 1 is configured with an IP address of

172.3.1.3.32.

DBSD 2

ICN_2_CORE is configured with an IP address of 172.31.8.10 and connects to

Port 2 on Router A from Port 23 and to Port 2 on Router B from Port 24. The standalone IIC on ICN Database Domain 2 is configured with an IP address of

172.3.1.11.32.

DBSD 3

ICN_3_CORE is configured with an IP address of 172.31.16.10 and connects to

Port 3 on Router A from Port 23 and to Port 3 on Router B from Port 24. The standalone IIC on ICN Database Domain 3 is configured with an IP address of

172.3.1.19.32.

B-4

MOSE225

C

Upgrade Wizard Warning and Error Messages

This appendix describes the warning and error messages generated by the

Philips Upgrade Wizard tool and includes:

• Overview

• Message Descriptions

IntelliVue Telemetry System Infrastructure Installation and Service Guide C 1

MOSE225

Chapter C: Upgrade Wizard Warning and Error Messages

Overview

The Upgrade Wizard will upload the APC system configuration and check that it conforms to the system requirements and installation rules, and verify that the

Slave APC configuration matches the Master APC configuration.

Configuration update is done by normal APC update processing, so the APC does not need to be rebooted, and data flow is not interrupted, while configuration update is performed.

If an installation rule is broken, a Warning Message is generated and written to the summary report. If a system requirement is broken, an Error Message is generated and written to the summary report, and the upgrade is aborted. If the Master and

Slave configuration are mismatched, the wizard attempts to force the Slave APC to upload a copy of the Master APC configuration.

You should take the appropriate response to a warning or error message as follows:

• Warning Message - A warning allows you to continue with the APC upgrade.

• Error Message - An error must be corrected before the upgrade can be completed. To correct an error, it may be necessary to take the APC down.

Appropriate notification will be given under these circumstances.

If the appropriate option has been chosen in the wizard, then errors in the Slave

APC configuration will be corrected automatically when possible by either copying the Master APC configuration to the Slave APC, or (with APC version

A.00.32 and higher) forcing the Slave APC to synchronize with the Master APC.

The Upgrade Wizard generates warning and error messages based on the presence of and content of a number of configuration files resident on the APC.

Note If the Upgrade Wizard displays an error message stating that a file is missing on a particular APC, then you can ignore any other warning or error messages related to that missing file on that APC.

This section lists and describes the possible warning and error messages generated by the Upgrade Wizard in the context of their associated configuration file.

The following tables document APC configuration files and their associated warning and error messages. The following information is provided for each configuration file:

• file name

• file content

• whether the file is required to be present (some files are optional), and whether it will be checked if the Smart hopping-only option is selected

• what general rules are applied to both Master and Slave APCs for this file

• what rules are applied to the Master APC only for this file

• what rules are applied to the slave APCs for this file

• whether a failure results in a warning or an error for each rule

C-2

The APC configuration rules are applied in the following order:

• Master APC

- File 1 general rules

- File 1 master-specific rules

- File 2 general rules

- File 2 master-specific rules

- [… etc., for each file, in the order given in the table below]

• Slave APC 1

- File 1 general rules

- File 1 slave-specific rules

- File 2 general rules

- File 2 slave-specific rules

- [… etc., for each file, in the order given in the table below]

- [… etc., for each slave APC]

MOSE225

Overview

IntelliVue Telemetry System Infrastructure Installation and Service Guide C 3

MOSE225

Chapter C: Upgrade Wizard Warning and Error Messages

Message Descriptions

Item/Rule

Comments

General Rules

Master-specific

Slave-specific

Table C-1: BOOTROM.NVP Warnings and Errors

Description

• APC specific information such as MAC address and IP address settings.

• This file must be present.

• This file will be checked if the Smart Hopping only option is selected.

• To fix errors or warnings in this file, use the APC serial menu to correct the settings.

• Check that the file itself is not corrupt (correct length, all fields given below are present).

Error: APC boot file length is incorrect

Error: [Data item] not found in boot file

• Check that last 3 bytes of MAC address are non-zero.

Warning: APC MAC address is default

• Check that the MAC address is either Philips (00:09:FB:xx:xx:xx) or Proxim

(00:20:A6:xx:xx:xx).

Error: MAC address is corrupt

• Check that the APC has a static IP address.

Warning: DHCP flag set

• Check that the static IP address is not class D or E.

Error: Class D/E IP addresses are illegal

• Check that the subnet mask is non-zero.

Error: Subnet mask must not be zero

• Check that the default gateway is either zero or on the same subnet as the

APC.

Error: Gateway and IP address are on different subnets

No checks

Check that the slave APC is on the same subnet as the master APC.

Error: Slave and master are not on same subnet

Item/Rule

Comments

General Rules

Master-specific

Slave-specific

Table C-2: PASSWORD.TLV Warnings and Errors

Description

• User and password info for logging in to the APC web interface.

• This file must be present.

• This file will be checked if the Smart Hopping only option is selected.

• Errors in this file can be corrected automatically.

No checks.

No checks.

• The file must contain the same set of TLVs on the master and the slave

(not necessarily in the same order, though).

Error: Slave and master files have differing contents [details…]

C-4

MOSE225

Message Descriptions

Item/Rule

Comments

General Rules

Master-specific

Slave-specific

Table C-3: PARAM/SYSTEM.TLV Warnings and Errors

Description

• System specific information.

• This file must be present.

• This file will be checked if the Smart Hopping only option is selected.

• Errors on the slave file can be corrected automatically; errors on the master can be fixed through the web interface, on the System config screens (“BOOTP/DHCP” and “SUBNET TABLE” tabs). System type on the

APC can be configured through the APC serial menu.

No checks.

• Check that the System Type (1.4 GHz or 2.4 GHz) stored in the APC matches the selection made on the Upgrader UI.

Error: System type on APC is [type], tool has been configured to verify a

[type] system

• Check that the DHCP configuration matches the default.

Warning: Non-default System DHCP Table configuration

• Check that the subnet table configuration matches the default.

Warning: Non-default subnet table configuration

• Check that any ranges in the DHCP configuration that would match AP

MAC addresses would not allow two APs to have duplicate ten low bits of IP address.

Error: Range n in DHCP table is invalid: duplicate FMIDs could result. Low ten bits of AP IP addresses must be guaranteed unique

• The file must contain the same set of TLVs on the master and the slave

(not necessarily in the same order, though); except the APC name TLV.

Error: Slave and master files have differing contents [details…]

Item/Rule

Comments

General Rules

Master-specific

Slave-specific

Table C-4: PARAM/FILTER.TLV Warnings and Errors

Description

• Filter configuration information.

• This file must be present.

• This file will be checked if the Smart Hopping only option is selected.

• Errors on the slave file can be corrected automatically; errors on the master can be fixed through the web interface, on the System config screens (“FILTERS” tab).

No checks.

• Check that each filter setting matches the default.

Warning: Non-default [filter] configuration

• The file must contain the same set of TLVs on the master and the slave

(not necessarily in the same order, though).

Error: Slave and master files have differing contents [details…]

IntelliVue Telemetry System Infrastructure Installation and Service Guide C 5

MOSE225

Chapter C: Upgrade Wizard Warning and Error Messages

Item/Rule

Comments

General Rules

Master-specific

Slave-specific

Table C-5: PARAM/AUTHTBL.TLV Warnings and Errors

Description

• Authorization details for specific PWDs.

• This file must be present.

• This file will be checked if the Smart Hopping only option is selected.

• Errors on the slave can be corrected automatically; errors on the master can be fixed through the web interface System config screens

(“AUTHORIZATION TABLE” tab).

No checks.

• Check that the authorization table is unused and has no entries

Error: Authorization table is in use.

• The file must contain the same set of TLVs on the master and the slave

(not necessarily in the same order, though)

Error: Slave and master files have differing contents [details…]

Item/Rule

Comments

General Rules

Master-specific

Slave-specific

Table C-6: CONFIG/DHCP.TLV Warnings and Errors

Description

• DHCP Server IP address assignment information.

• This file may not be present if no DHCP assignments have been made.

• This file will be checked if the Smart Hopping only option is selected.

• Errors on the slave can be corrected automatically; errors on the master can be fixed through the web interface System config screens (“BOOTP/

DHCP” tab, click to view allocations, “Purge allocations”).

No checks.

• Check that the file header is correct.

Error: Master DHCP file header incorrect

• Check that all entries have Philips or Proxim MAC addresses

Warning: unrecognized MAC address in DHCP table

• Check that all entries for AP MAC addresses have unique ten low bits of IP address (cross checked against manually configured APs in the WTMS.TLV file)

Error: AP x:x:x:x:x:x and AP x:x:x:x:x:x have duplicate low ten bits of IP address

• The file headers on the master and slave files must match.

Error: DHCP File headers do not match

• The file must contain the same set of DHCP entries on the master and the slave (not necessarily in the same order, though).

Error: Slave and master files have differing contents [details…]

C-6

MOSE225

Message Descriptions

Table C-7: CONFIG/TABLE/GRPSWMTS.TLV Warnings and Errors

Item/Rule

Comments

General Rules

Master-specific

Slave-specific

Description

• Group configuration information for Smart Hopping AP groups

• This file must be present.

• This file will be checked if the Smart Hopping only option is selected.

• Errors on the slave file can be corrected automatically; errors on the master can be fixed through the web interface, Group config screens.

No checks.

• APs have default group basic configuration.

Warning: APs have non-default group basic [specific item] configuration

• APs have default group alert configuration.

Warning: APs have non-default group alert [specific item] configuration

• APs have default group radio configuration.

Warning: APs have non-default group radio [specific item] configuration

• APs have default advanced group configuration.

Warning: APs have non-default advanced [specific item] group configuration.

• Group configuration has default check boxes checked for enabling items on configuration screen.

Warning: Non-default configuration: [specific item] on [specific group config screen], enable checkbox should be [set / unset]

• The file must contain the same set of Groups on the master and the slave

(not necessarily in the same order, though).

Error: Slave and master files have differing contents [details…]

• Each Group must contain the same set of Group TLVs on the master and the slave (not necessarily in the same order, though).

Error: Slave and master files have different group configurations [details…]

• Each Group must contain the same set of AP TLVs on the master and the slave (not necessarily in the same order, though).

Error: Slave and master files have different AP configurations [details…]

Item/Rule

Comments

General Rules

Table C-8: CONFIG/TABLE/WMTS.TLV Warnings and Errors

Description

• AP configuration information for Smart Hopping APs

• This file may not be present if no Smart Hopping APs are configured on the system.

• This file will be checked if the Smart Hopping only option is selected.

• Errors on the slave file can be corrected automatically; errors on the master can be fixed through the web interface, individual AP configuration screens.

No checks.

IntelliVue Telemetry System Infrastructure Installation and Service Guide C 7

MOSE225

Chapter C: Upgrade Wizard Warning and Error Messages

Item/Rule

Master-specific

Table C-8: CONFIG/TABLE/WMTS.TLV Warnings and Errors

Description

• All APs on same subnet.

Error: APs are not all on same subnet

• All entries for AP MAC addresses have unique ten low bits of IP address

(cross checked against manually configured APs in the DHCP.TLV file).

Error: AP x:x:x:x:x:x and AP x:x:x:x:x:x have duplicate low ten bits of IP address

• WMTS systems only: All APs have same WMTS channel configuration.

Error: APs do not all have same WMTS channel configuration

• ROW Z.nn.nn systems only: All APs have same ISM area configuration.

Error: APs do not all have same ISM area configuration

• ROW B.00.03 and onwards systems only: All APs have same ISM Radio

Regulation Code configuration.

Error: APs do not all have same ISM Radio Regulation Code configuration

• ROW B.00.03 and onwards systems only: All APs have same ISM

Frequency Plan configuration.

Error: APs do not all have same ISM Frequency Plan configuration

• ROW B.00.03 and onwards systems only: All APs have same ISM Zigbee

Channel configuration.

Error: APs do not all have same ISM Zigbee Channel configuration

• ROW B.00.03 and onwards systems only: All APs have same ISM

Advanced Channel configuration

• Error: APs do not all have same ISM Advanced Channel configuration

• APs have been set up with a preferred partner.

Warning: APs have been configured with no preferred partner

• APs are not disabled.

Warning: AP has been disabled

• APs have default RF Access code configuration - cross-check each entry in

AP file against AP template defaults (warning), default Smart Hopping

Group settings (warning), and AP's own group settings (error).

Warning/Error: RF Access Code enable: AP is [set / unset], [AP Default /

Default Smart Hopping Group / AP's Group] is [unset / set]APs have default WMTS Channels configuration - cross-check each entry in AP file against AP template defaults (warning), default Smart Hopping Group settings (warning), and AP's own group settings (error).

Warning/Error: WMTS Channels: AP has [channels] enabled, [AP Default /

Default Smart Hopping Group / AP's Group] has [channels] enabled

• ROW Z.nn.nn systems only: APs have default ISM area code configuration - cross-check each entry in AP file against AP template defaults (warning), default Smart Hopping Group settings (warning), and AP's own group settings (error)

Warning/Error: ISM area code: AP is [area], [AP Default / Default Smart

Hopping Group / AP's Group] is [area]

• ROW B.00.03 and onwards systems only: APs have default ISM Radio

Regulation Code configuration - cross-check each entry in AP file against

AP template defaults (warning), default Smart Hopping Group settings

(warning), and AP's own group settings (error).

Warning/Error: ISM Radio Regulation Code: AP has [code],

[AP Default / Default Smart Hopping Group / AP's Group] has [code]

• ROW B.00.03 and onwards systems only: APs have default ISM Advanced

Channels configuration - cross-check each entry in AP file against AP template defaults (warning), default Smart Hopping Group settings

(warning), and AP's own group settings (error).

Warning/Error: ISM Advanced Channels: AP has [channels] enabled, [AP

Default / Default Smart Hopping Group / AP's Group] has [channels] enabled

C-8

MOSE225

Message Descriptions

Item/Rule

Slave-specific

Table C-8: CONFIG/TABLE/WMTS.TLV Warnings and Errors

Description

• The file must contain the same set of APs on the master and the slave (not necessarily in the same order, though).

Error: Slave and master files have differing contents [details…]

• Each AP must contain the same set of TLVs on the master and the slave

(not necessarily in the same order, though).

Error: Slave and master files have differing contents [details…]

General Rules

Master-specific

Slave-specific

Table C-9: CONFIG/TEMPLATE/WMTS.TLV Warnings and Errors

Item/Rule

Comments

Description

• Default AP configuration for Smart Hopping APs

• This file may not be present if no changes have been made to the default template settings.

• This file will be checked if the Smart Hopping only option is selected.

• Errors on the slave can be fixed automatically; errors on the master can be fixed through the web interface, Access Point Default settings.

No checks.

• APs have default basic configuration.

Warning: APs have non-default basic [specific item] configuration

• APs have default alert configuration.

Warning: APs have non-default alert [specific item] configuration

• APs have default radio configuration.

Warning: APs have non-default radio [specific item] configuration

• The file must contain the same set of TLVs on the master and the slave

(not necessarily in the same order, though).

Error: Slave and master files have differing contents [details…]

IntelliVue Telemetry System Infrastructure Installation and Service Guide C 9

Chapter C: Upgrade Wizard Warning and Error Messages

MOSE225

C-10

MOSE225

Index

Numerics

1, 6, 11 frequency plan 2-25

1, 7, 13 frequency plan 2-25

1.4 GHz ITS bandwidth 1-15

2.4 GHz APs, description of 1-7

2.4 GHz ITS bandwidth 1-17

2.4 GHz spectrum, understanding interference in 2-20

802.11 devices within the 2.4 GHz spectrum 2-22

A

Access Point Controller (APC)

adding to an existing ITS 4-20

adding to the network 3-14 default configuration 3-14

determining required number 2-11

initial configuration of 3-12

overview of 1-9

replacing 4-33

testing 5-3

Access points

2.4 GHz AP descriptions 1-7

adding to the network 3-38

cluster AP descriptions 1-3

configuring groups 3-30

core AP placement guidelines 2-8

determining installation locations 2-6

Ethernet interface on 2.4 GHz APs 1-8

Ethernet interface on cluster APs 1-4

illustration of 2.4 GHz AP 1-7

illustration of cluster AP 1-4

location restriction 2-3

mounting options for cluster AP 1-7 overview of 2.4 GHz APs 1-7

overview of Cluster APs 1-3

placement guidelines 2-11

planning groups for 2-18

radius of coverage values 2-4

IntelliVue Telemetry System Infrastructure Installation and Service Guide Index 1

Index

rebooting after configuration 3-41

serial port 1-5, 1-8

status LEDs 1-6, 1-9

summary table worksheet 2-27

testing and inspecting 5-2

Act LED 1-6

Activity LED 1-9

Add AP button 4-26

Adding an AP via Auto-Registration 4-22

Adding an AP via Manual MAC Address Input 4-26

Adding APCs to an Existing ITS 4-20

Adding APs to an Installed ITS 4-21

Adding New AP Groups to an Existing ITS Configuration 4-28

Advanced 2.4 GHz channel configuration 2-25, 2-34, 3-29

Alert Destination 2-36, 3-32

ALERTS SETTINGS tab 3-31

American Society for Healthcare Engineering (ASHE), registering with 1-17

AP Controller Name 3-15

AP group configuration worksheet 2-36

AP group name 2-36

AP groups

configuring 3-30

planning 2-19

AP Name 3-39, 3-40, 4-26

AP Type 4-26

AP/SU connectors on Sync Unit 1-12

APC configuration file, exporting 4-5

APC fails to upgrade 5-12

APC serial interface main menu 3-13

APC web-based management interface, connecting to 3-15

ARIB 2-34, 3-29

AS/NZ 2-34, 3-29

Audience for this guide x

B

BASIC SETTINGS tab 3-31

Bluetooth device, as 2.4 GHz interference source 2-21

BOOTP/DHCP Settings 3-24

C

Cable delay switch 2-17

CABLE DELAY Switch on Sync Unit 1-12

Cable runs, planning 2-13

Carved-out areas in WMTS spectrum 1-15

Channels, 2.4 GHz ITS 1-17

Channels, assigning 2.4 GHz ITS 2-24

Coaxial Cable Connectors on Core AP 1-5

Coaxial Cable Connectors on remote antenna 1-6

MOSE225

Index-2

MOSE225

Index

Command line interface (CLI), connecting to the APC 1-10

Components, ITS 1-3

Configuration key, displaying 3-20

Copyright information

ii

Cordless phones, as 2.4 GHz interference source 2-22

Core AP description 1-3

Core APs

description of 1-3

placement guidelines 2-8

Coverage assessment mode, using the PWD 5-9

Customer-supplied Clinical Network (CSCN), deploying the ITS on a 1-30

D

Daisy-chained topology for Sync Units 2-15

Data flow, within the ITS 1-14

Default Group 3-29

Default WMTS Group 2-33, 2-34

Document organization

x

Document printing history ii

Duplicate IP address system-level alert 4-25, 4-27, 5-12

E

Emergency hospital power, devices that must be on 2-14

Enable AP 3-39, 3-40

Environmental specifications 1-32

Equipment closets, considering locations of 2-12

Ethernet interface, on 2.4 GHz APs 1-8

Ethernet interface, on cluster APs 1-4

ETSI 2-34, 3-29

Exporting an ITS APC configuration to a disk file 4-5

EXT 10MHz REF input on Sync Unit 1-12

F

FCC 2-34, 3-29

FCC registration, required for WMTS 1-17, 3-27

Ferrite block, installing on AP cable 3-6, 4-22

Filter Settings 3-23

Frequency Plan 2-34, 3-29, 3-31, 3-40, 4-30

Frequency plan

1, 6, 11 2-25

1, 7, 13 2-25

FROM POWER HUB connectors on Sync Unit 1-12

G

Group Description 3-30

Group Membership 3-39, 3-40

Group Name 3-30

IntelliVue Telemetry System Infrastructure Installation and Service Guide Index 3

Index

Group Type 3-30

H

Hybrid topology for Sync Units 2-17

Hyperterminal settings for APC serial connection 3-12

I

Initial configuration of APCs 3-12

Installation locations, determining optimal AP 2-6

IntelliVue Telemetry System (ITS)

components of 1-3

data flow 1-14 defined bandwidth 1-14

deployment planning 2-1

expanding 4-2

installing and configuring 3-2

overview of 1-2

part numbers 1-34

specifications 1-30

topologies and system limits 1-19

troubleshooting and testing 5-1

IP address assignment

for non-routed ICN topology 1-22

IP Addressing

Default Gateway 2-33, 2-35

Subnet Mask 2-33, 2-35

ITS infrastructure components, interconnecting 3-4

K

Known issues, troubleshooting 5-10

L

LAN port 1-10

LEDs

access point 1-6

Remote Active Antenna 1-7

LEDs, access point 1-9

Link LED 1-6, 1-9

Link status LEDs 1-10, 1-11

Locating cluster APs properly 2-8

M

Main menu, APC serial interface 3-13

Manufacturer contact information

ii

Master/Slave LED 1-10

MASTER/SLAVE toggle switch on Sync Unit 1-12

Index-4

MOSE225

MOSE225

Index

Maximum AP to switch cable length 2-13

Microwave ovens, as 2.4 GHz interference source 2-21

Mounting options 3-2

Mounting options, access point 1-7

N

Network LED 1-6, 1-9

Network utilization LEDs 1-10

Non-linear patient room layout, providing RF coverage for 2-7

Non-routed ICN topology 1-19

Non-routed ICN topology, assigning device IP addresses on 1-22

Notational conventions

xi

O

Organization of content in this document x

Overview of the ITS 1-2

P

Part numbers 1-34

Partnered AP Controller 3-27, 3-28, 3-31, 3-39, 3-40, 4-30

Partnered APC 2-33, 2-34

Patient environment, boundaries of 2-2

Philips Smart-hopping technology 1-3

Philips Telemetry Service Tool 5-9

Physical Address 4-26

Physical space assessment, performing 2-4

Power draw ratings for ITS devices 1-13

Power over Ethernet (PoE) Unit

description of 1-12

illustration of 1-13

testing 5-5

Power requirements for ITS devices 1-30

Power/Sync LED 1-6, 1-9

R

Rack-mounting ITS infrastructure components 3-4

Radio LED 1-6, 1-9

Radio Regulations 2-34, 3-29, 3-31, 3-40, 4-30

Radius of coverage cells, placing on a floorplan 2-8

Radius of coverage for APs 2-4

Range 5, settings for 3-26

Related documentation xi

Remote Antenna description 1-3

Remote Antenna, replacing 4-33

Replacing an ITS Access Point 4-32

Replacing an ITS APC 4-33

Retry, Skip, Abort error dialog 3-49, 5-12

IntelliVue Telemetry System Infrastructure Installation and Service Guide Index 5

Index

Index-6

RF Access Code 2-34, 3-28, 3-29, 3-31, 3-39, 3-40, 4-30

RF frequency survey, performing 2-20

Routed ICN, topology 1-23

RSS-210 2-34, 3-29

S

Safety regulatory compliance 1-32

Serial port 1-10

Serial port, on AP 1-5, 1-8

Service PC, connecting to ITS wireless subnet 3-8

Site planning guidelines 2-3

Site survey, guidelines for performing 2-23

Specifications 1-30

Spectrum analyzer, using 2-23

Speed-duplex settings 1-10

Star Topology

advantages of 1-28

Star topology for Sync Units 2-16

STATUS tab 3-41

Switch port settings 1-10

Sync Loss Alert 3-32

Sync network, planning layout of 2-15

Sync Unit

cable delay switch 1-12

LEDs 1-12

Master/Slave toggle switch 1-12

testing 5-4

Synchronization Unit

illustration of 1-11 overview of 1-11

System ID 3-15

System limits 1-29

T

Terminology xii

TO MASTER SU port on Sync Unit 1-12

TO SLAVE SU port on Sync Unit 1-12

Topologies and system limits, ITS 1-19

Trademark acknowledgements

ii

Traditional patient room layout, providing RF coverage for 2-7

Transceivers, determining number to be supported 2-6

Troubleshooting information 5-11

U

UL 2043 compliance 1-32

Uninterruptible Power Supply (UPS)

illustration of 1-13

ITS device power draws 1-13

MOSE225

overview of 1-13

planning deployment of 2-14

specifications for 1-31

testing 5-6

UPGRADE button, on APC configuration screens 3-15

Upgrade Wizard

installing 3-10

running 3-16, 3-34

troubleshooting known issues 5-10

UTP Cable Connectors on Core AP 1-5

UTP Cable Connectors on remote antenna 1-6

V

VLANs, configuring for a star topology 1-28

W

WiFi interference, avoiding 2-24

Wireless clients, determining number to be supported 2-6

Wireless headsets, as 2.4 GHz interference source 2-22

Wireless Medical Telemetry Service (WMTS) band 1-2

WMTS Channels 2-33, 3-27, 3-31, 3-39, 4-30

WMTS RF Access Code 2-33

Worksheets, ITS installation 2-26, 3-4

WWW.ASHE.ORG 1-17

Z

ZigBee channel used for medical 2-34, 3-29, 3-31, 3-40, 4-30

ZigBee devices, as 2.4 GHz interference source 2-23

MOSE225

Index

IntelliVue Telemetry System Infrastructure Installation and Service Guide Index 7

Index

MOSE225

Index-8

Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project