Philips IntelliSpace Event Management Computer ... · he Computer Specifications provide the...
Transcript of Philips IntelliSpace Event Management Computer ... · he Computer Specifications provide the...
Philips IntelliSpace Event Management
Computer Specifications
Version 11.00
Document Number: 866030-90015
Document Release: C
WARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Computer Specifications
Page 2 866030-90015 Document Release CWARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANYRELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Computer Specifications Version 11.00 Notices
Notices
© 2001-2012 Koninklijke Philips Electronics N.V. All Rights Reserved.
This document and the information contained in it is proprietary and confidential information of Philips Healthcare ("Philips") and may not be reproduced, copied in whole or in part, adapted, modified, disclosed to others, or disseminated without the prior written permission of the Philips Legal Department. Use of this document and the information contained in it is strictly reserved for current Philips personnel and Philips customers who have a current and valid license from Philips for use by the customer's designated in-house service employee on equipment located at the customer's designated site. Use of this document by unauthorized persons is strictly prohibited. Report any violations of these requirements to the Philips Legal Department. This document must be returned to Philips when the user is no longer licensed and in any event upon Philips' first written request.
Philips provides this DOCUMENT without warranty of any kind, implied or expressed, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose.
Philips has taken care to ensure the accuracy of this document. However, Philips assumes no liability for errors or omissions and reserves the right to make changes without further notice to any products herein to improve reliability, function, or design. Philips may make improvements or changes in the product(s) or program(s) described in this document at any time.
Installation and operation of Philips IntelliSpace Event Management software with some devices may require certification of the Philips IntelliSpace Event Management software by the device vendor.
For additional information on certification applicability please contact Philips IntelliSpace Event Management Technical Support as described in the Support Information section of this document.
Intended Use Statement
IntelliSpace Event Management provides healthcare professionals with supplemental information about patient alarms, technical alarms, nurse call alarms and system information messages (events). The system can route all or subsets of this information to selective remote devices such as pagers, phones, or marquees. Receipt of alarm messages or events by the external device, is not confirmed and delivery to the end device is not guaranteed. The primary alarm notification is the device producing the alarm or event. This product line is not intended to provide real-time information, nor is it a source of patient alarms, nor is it a replacement for alarming devices.
Regulation and Safety Notices
Trademark Attributions
Philips IntelliSpace Event Management and all related logos and branding are trademarks of Philips.
All other product, service, and company names are trademarks or registered trademarks of their respective owners.
Philips3000 Minuteman RdAndover, MA, 01810United States of America
www.philips.com/IntelliSpaceEventManagement
Declaration IntelliSpace Event Management conforms to the provisions of Council Directive: 93/42/EEC (Medical Devices Directive) as amended by 2007/47/EC concerning medical devices. It carries CE-marking to the European Medical Device Directive.This product is not intended for home use. Rx only. Philips IntelliSpace Event Management system components are not suitable for installation in the Patient Care Vicinity (Patient Environment).
0123
866030-90015 Document Release C Page 3WARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Contents
Chapter 1 Introduction
Terminology ..........................................................................................................................................14
System Requirements ..........................................................................................................................15
System Security and Maintenance .......................................................................................................15
Anti-Virus Software ...............................................................................................................................16
Excluded Files .................................................................................................................................16
Compliances .........................................................................................................................................17
Regulatory Information .........................................................................................................................17
Prerequisites ........................................................................................................................................17
Preinstallation Information ....................................................................................................................17
System Implementation ...................................................................................................................18Network Installation .........................................................................................................................18Stand-Alone Installation ..................................................................................................................18Installation Privileges ......................................................................................................................18Firewall Ports ..................................................................................................................................19System Time Synchronization .........................................................................................................22Implementation Design Requirements for Microsoft SQL Server ...................................................22Philips Event Integration Service ....................................................................................................23
Modems .....................................................................................................................................23Legacy Cisco CallManager .............................................................................................................24
Automatic Update Requirements .........................................................................................................24
Qualified Platforms and Microsoft Security Updates ............................................................................24
Chapter 2 Product and Configuration Overview
Introduction ...........................................................................................................................................26
Event Notification ............................................................................................................................26
System Software Architecture ..............................................................................................................26
Patient Monitoring Gateway ............................................................................................................26IntelliSpace Event Management Nurse Call Gateway ....................................................................28Event Service Bus (ESB) ................................................................................................................29IntelliSpace Event Management Platforms .....................................................................................30Philips Integration Adapters ............................................................................................................31
Input Adapters ............................................................................................................................31Output Adapters .........................................................................................................................31Administrative Adapters .............................................................................................................31
Orchestrator Client ..........................................................................................................................32Adapter Rules .................................................................................................................................33
Component Installation Requirements .................................................................................................34
Chapter 3 Hardware Product Specifications
Non-Virtual Environment Specifications ...............................................................................................38
Gateway Server ..............................................................................................................................38Philips Event Adapter Server (EAS) ................................................................................................39
866030-90015 Document Release C Page 5WARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Contents Computer Specifications Version 11.00
EIS Server .......................................................................................................................................40EIS Server when connected to HDB ..........................................................................................41HDB SQL Server ........................................................................................................................42
IIS Server ........................................................................................................................................43Blade Servers ..................................................................................................................................43Cisco Remote Telephony Server ....................................................................................................44
Client Machine Specifications .............................................................................................................45
Virtual Environment Specifications .......................................................................................................46
Deployment Best Practices ..................................................................................................................46
Deployment Requirements ...................................................................................................................46
Resource Management Requirements ...........................................................................................47Option A .....................................................................................................................................47Option B .....................................................................................................................................47
Event Service Bus/Adapter Servers (ESB) .....................................................................................47Gateway Servers (MS SQL server installed on another VM) ..........................................................47Gateway Servers (co-installed MS SQL server) .............................................................................47Database Servers ...........................................................................................................................47Cisco Remote Telephony Server ....................................................................................................48vMotion ............................................................................................................................................48DRS .................................................................................................................................................48
Option A .....................................................................................................................................48Option B .....................................................................................................................................48
High Availability (HA) ......................................................................................................................48IEM Services Configuration for use with HA ..............................................................................48
Gateway Server Virtual Machine .....................................................................................................49Adapter Server Virtual Machine ......................................................................................................50Event Management Server Virtual Machine ....................................................................................51IntelliSpace Event Management SQL Server Virtual Machines ......................................................52Database Storage Considerations ..................................................................................................53IIS Server Virtual Machine ..............................................................................................................56Cisco Remote Telephony Server Virtual Machine ..........................................................................57
HA and non-HA System Layout ...........................................................................................................58
Cisco Remote Telephony Server Layout ..............................................................................................59
System Layout For Microsoft Clustered Environments ........................................................................59
Storage .................................................................................................................................................61
Storage Area Network .....................................................................................................................61Dedicated SAN ..........................................................................................................................61Managed Multisystem SAN ........................................................................................................61Unmanaged Multisystem SAN ...................................................................................................61
Networked Attached Storage ..........................................................................................................61
Optional Computer Cards .....................................................................................................................61
Chapter 4 Software Product Specifications
Installation Prerequisites ......................................................................................................................64
Philips Event Integration Service ..........................................................................................................67
Philips Event Integration Service Software Operating Environment ...............................................67Additional Notes and Considerations for the Philips Event Integration Service ..............................68Philips Event Integration Service Features and Limits ....................................................................68
Philips Event Personalization Service ..................................................................................................70
Event Personalization Service Software Operating Environment ...................................................71Additional Notes for the Event Personalization Service Specifications ...........................................71
E-mail Messenger ................................................................................................................................72
Page 6 866030-90015 Document Release CWARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Computer Specifications Version 11.00 Contents
Additional Notes for the E-mail Messenger Specifications ..............................................................72E-mail Messenger Features and Limits ...........................................................................................72
Web Messenger Server ........................................................................................................................72
Web Messenger Client .........................................................................................................................73
Web Messenger Client Software Operating Environment ...............................................................73Additional Notes for the Web Messenger Client Specifications ......................................................73Web Messenger Client Features and Limits ...................................................................................73
File Messenger .....................................................................................................................................74
File Messenger Software Operating Environment .........................................................................74Additional Notes for the File Messenger .........................................................................................74File Messenger Features and Limits ...............................................................................................74
Command Messenger ..........................................................................................................................75
Command Messenger Software Operating Environment ................................................................75Additional Notes for the Command Messenger Specifications .......................................................75Command Messenger Features and Limits ....................................................................................76
Orchestrator .........................................................................................................................................76
Orchestrator Software Operating Environment ...............................................................................76Additional Notes for the Orchestrator Specifications .......................................................................77
Whiteboard ...........................................................................................................................................77
Whiteboard Software Operating Environment .................................................................................77Additional Notes for the Whiteboard Specifications ........................................................................77
Messenger ............................................................................................................................................78
Messenger Software Operating Environment .................................................................................78Additional Notes for the Messenger Specifications .........................................................................78Messenger Features and Limits ......................................................................................................79
Alarm Messenger .................................................................................................................................80
Additional Notes for the Alarm Messenger Specifications ..............................................................80Alarm Messenger Features and Limits ...........................................................................................81
Philips Event Notification Exporter .......................................................................................................82
Philips SOAP SDK ...............................................................................................................................83
Philips Event Syndication Service ........................................................................................................83
Philips Socket SDK ..............................................................................................................................83
Unified Counters Viewer .......................................................................................................................84
Philips Historical Database ...................................................................................................................84
Historical Database Reporting ..............................................................................................................85
Software prerequisites ....................................................................................................................85HDB Reporting Service ...................................................................................................................85HDB Reporting Client/Browser ........................................................................................................85
Personal Assignments ..........................................................................................................................86
Personal Assignments Features and Limits ....................................................................................86Personal Assignments Server .........................................................................................................86Personal Assignments Devices .......................................................................................................86
Contact Information .................................................................................................................................87
866030-90015 Document Release C Page 7WARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Figures
Figure 1. Patient Monitoring Gateway ....................................................................................................... 27Figure 2. Nurse Call Gateway ................................................................................................................... 28Figure 3. IntelliSpace Event Management System Software Architecture Diagram.................................. 29Figure 4. Philips Adapters - Typical Configuration with Six Input and Administrative Adapters. ............... 32
866030-90015 Document Release C Page 9WARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Tables
Table 1: Acronym Definitions .....................................................................................................................14Table 2: Term Definitions ..........................................................................................................................15Table 3: Files and Locations Excluded from Anti-virus Scans ...................................................................16Table 4: IntelliSpace Event Management Firewall Ports Requirements ....................................................19Table 5: Basic Requirements for Wireless Data Protocols ........................................................................23Table 6: IntelliSpace Event Management Configuration Rules .................................................................30Table 7: Configuration Rules for Philips Adapters .....................................................................................33Table 8: Component Installation Requirements and Options ....................................................................34Table 9: Storage Requirement in KB per Alert (if waveform images are sent with alerts ..........................54Table 10: Storage Requirement in KB per Alert (if no waveform images are sent with alerts ...................54Table 11: Storage Requirement for Alerts with Waveform Images Over Time - Total Storage .................54Table 12: Storage Requirement for Alerts without Waveform Images Over Time - Total Storage ............55Table 13: Optional Computer Cards ..........................................................................................................61Table 14: IIS and Required Role Services ................................................................................................65Table 15: Philips Event Integration Service Software Operating Environment ..........................................67Table 16: Philips Event Integration Service Features, Feature Limits, and Notes ....................................68Table 17: Event Personalization Service Software Operating Environment ..............................................71Table 18: E-mail Messenger Features, Feature Limits, and Notes ...........................................................72Table 19: Web Messenger Client Software Operating Environment .........................................................73Table 20: Web Messenger Client Features, Feature Limits, and Notes ....................................................73Table 21: File Messenger Software Operating Environment .....................................................................74Table 22: File Messenger Features, Feature Limits, and Notes ................................................................74Table 23: Command Messenger Software Operating Environment ..........................................................75Table 24: Command Messenger Features, Feature Limits, and Notes .....................................................76Table 25: Orchestrator Software Operating Environment .........................................................................76Table 26: Whiteboard Software Operating Environment ...........................................................................77Table 27: Messenger Software Operating Environment ............................................................................78Table 28: Messenger Features, Feature Limits, and Notes ......................................................................79Table 29: Messenger Desktop Mode Features, Feature Limits, and Notes ..............................................79Table 30: Alarm Messenger Software Operating Environment .................................................................80Table 31: Alarm Messenger Features, Feature Limits, and Notes ............................................................81Table 32: Philips Event Notification Exporter Software Operating Environment .......................................82Table 33: Philips SOAP SDK Software Operating Environment ...............................................................83Table 34: Event Syndication Service Software Operating Environment ....................................................83Table 35: Philips Socket SDK Software Operating Environment ..............................................................83Table 36: Unified Counters Viewer Software Operating Environment .......................................................84Table 37: Historical Database Software Operating Environment ..............................................................84Table 38: HDB Reporting Service Software Operating Environment ........................................................85Table 39: Historical Database Software Operating Environment ..............................................................85Table 40: Personal Assignments Software Operating Environment ..........................................................86
866030-90015 Document Release C Page 11WARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Chapter 1 Introduction
he Computer Specifications provide the requirements and specifications for the Philips IntelliSpace Event Management that comprises core services, adapters, and clients.
This chapter contains overview information that can be useful in understanding the Philips IntelliSpace Event Management computer specifications.
T
In this chapter:
Terminology on page 14
System Requirements on page 15
System Security and Maintenance on page 15
Anti-Virus Software on page 16
Compliances on page 17
Regulatory Information on page 17
Prerequisites on page 17
Preinstallation Information on page 17
Automatic Update Requirements on page 24
Qualified Platforms and Microsoft Security Updates on page 24
866030-90015 Document Release C Introduction Page 13WARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Terminology Computer Specifications Version 11.00
TerminologyThis section provides definitions for acronyms and terms used within this guide. Table 1 lists the acronym definitions and Table 2 lists the term definitions.
Table 1: Acronym Definitions
Acronym Definition
ADT Admit, Discharge, and Transfer
CAL Client Access License
CIPS Cisco IP Phone Service
DST Daylight Savings Time
EAS Event Adapter Server
EIS Event Integration Service
EPS Event Personalization Service
ESB Event Service Bus
GUI Graphical User Interface
HA High Availability
HBA Host Bus Adapter
HL7 Health Level 7
HTTPS Hypertext Transfer Protocol Secure
IIS Internet Information Server
iSCSI Internet Small Computer System Interface
LAN Local Area Network
LUN Logical Unit Number
NCG Nurse Call Gateway
NIC Network Interface Card
OS Operating System
PAB Personal Address Book
PMG Patient Monitoring Gateway
SAN Storage Area Network
SCSI Small Computer System Interface
TAPI Microsoft Telephony Application Programming Interface
TCP/IP Transmission Control Protocol/Internet Protocol
TSP TAPI Service Provider
URL Uniform Resource Locator
VM Virtual Machine
WAN Wide Area Network
WCTP Wireless Communications Transfer Protocol
XML Extensible Markup Language
Page 14 Introduction 866030-90015 Document Release CWARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Computer Specifications Version 11.00 System Requirements
System RequirementsPhilips products require specific hardware and software to function properly. Make sure you have sufficient hardware and software to support your environment and configuration before proceeding with the installation process. Refer to Chapter 3 Hardware Product Specifications on page 37 for hardware information about the requirements for each Philips IntelliSpace Event Management component and refer to Chapter 4 Software Product Specifications on page 63 for software requirements.
System Security and MaintenanceThe site’s IT department best practices should be followed to avoid such things as compromising data integrity, service disruption, or denial of service attack. This includes protecting the server from physical damage and unsecured access to the server.
The operating system password protection feature and a strong password for service user access must be in place and enforced by the site’s IT department. Secure password must be enabled to avoid compromising the server data. Refer the Philips IntelliSpace Event Management Orchestrator Service Guide for information about configuring a password.
To ensure that a hospital’s IT security procedures are followed, a redundant network path is recommended.
Note: Operating systems that support User Access Control must have it enabled before running the installation package.
Table 2: Term Definitions
Term Definition
Adapter An adapter is an interface to a specific third-party vendor, application, or service component.
Architecture The collection of software components that comprises the structure of a system.
Client A client is a service component that requests information from the service bus.
Event Adapter Server (EAS)
An instance of a Windows® server/PC that can run one or more input adapters. The EAS does not include services or warranty. For example, in this pricing model, the PMG is now called an Philips Event Adapter Server (EAS). The Patient Monitoring EAS runs an input adapter for a specific patient monitoring vendor. Functionally, the EAS is equivalent to a PMG -- however the Philips Event Adapter Server is not a turnkey bundle.
Event Service Bus (ESB)
The ESB is the central architectural component and core engine of the Philips IntelliSpace Event Management platform. The ESB runs the Philips Event Integration Service (EIS) – which is often referred to as the “EIS server”. A key component of the EIS is the alert dispatch function. The dispatch function works through the output adapter that must run on the same server/box as the ESB.
Gateway In the Gateway packaging model, the package consists of one input adapter, optionally administrative adapters for ADT or LDAP and one or more output adapters. The equivalent of an Philips Gateway (again without Philips software, services, hardware, and 1st year warranty) in the built-to-order model is an Philips Event Adapter Server (EAS).
Recipient A recipient is a user, group or device. A group counts as only one recipient, regardless of the number of members.
866030-90015 Document Release C Introduction Page 15WARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Anti-Virus Software Computer Specifications Version 11.00
Anti-Virus SoftwareA variety of network equipment comprise IntelliSpace Event Management including Windows-based computers (e.g., Clients, Database Servers, and Application Servers). Due to the prevalence of Windows-based computers on the network and the large number of hacks and exploits made to Windows-based computers, we recommend that you run anti-virus software on all Windows-based computers used with IntelliSpace Event Management.
Philips does not recommend any specific anti-virus tool. Because of the critical nature of the data in IntelliSpace Event Management, regardless of which anti-virus software tool you choose (e.g., Symantec/Norton Anti-Virus or McAfee Virus Scan), you should, but do not have to, disable the tool's live virus scan and live virus signature file update capabilities, as live scans/updates may degrade system performance. You should perform virus scans and update the tool's virus signature file manually when the Windows computer is offline. Refer to Excluded Files on page 16 for information about files and file locations that must be excluded from any virus scan. Refer to Qualified Platforms and Microsoft Security Updates on page 24 for more information about Microsoft Windows Automatic Updates.
You should backup your systems on a regular basis so that if the system is compromised it can be restored.
In the event of a virus infection or suspected infection, we recommend that you take the suspect system offline, run a virus scan, and if a virus is detected, rebuild the computer completely.
Excluded Files
Certain files and file locations must to be excluded from any virus scan. Figure 3 lists the files and locations.
Table 3: Files and Locations Excluded from Anti-virus Scans
Exclusions File Names and Locations
Files and Locations \Windows\debug
\Windows\Logs
\Windows\Security\logs
\Windows\SysWOW64\filemsgr.exe
\Windows\System32\msgr.dll
Microsoft Cluster Specific:
• Q: (Quorum disk)
• Windows\Cluster
The directory that holds the SQL Server data, temp files and backup files. Refer to http://support.microsoft.com/kb/309422 for additional information.
<Emergin Integration Suite Program Folder>
File Types .mdb
.ldb
.mdf
.ldf
.ndf
SQL Backup files - typically
• .bak
• .trn
Page 16 Introduction 866030-90015 Document Release CWARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Computer Specifications Version 11.00 Compliances
Refer to http://support.microsoft.com/kb/309422 for additional information related to co-installed SQL and Clustering.
CompliancesThe Philips IntelliSpace Event Management is in compliance with the Energy Policy Act of 2005 which changes the dates of the start and end of Daylight Savings Time (DST).
Regulatory InformationInstallation and operation of Philips IntelliSpace Event Management software with some devices may require certification of Philips IntelliSpace Event Management software by the device vendor.
For additional information on certification applicability please contact Philips IntelliSpace Event Management Technical Support.
PrerequisitesPhilips products require specific prerequisite software. Refer to Chapter 4 Software Product Specifications on page 63 for prerequisite requirements for each Philips IntelliSpace Event Management component. Additionally, review the Preinstallation Information section for important preinstallation considerations and requirements.
Preinstallation InformationThis section provides the following preinstallation information, considerations and requirements for IntelliSpace Event Management and specific components. If you are planning a virtual environment, a clustered environment, or both, refer to the Philips IntelliSpace Event Management Virtualization Service Guide and the Philips IntelliSpace Event Management Clustering Service Guide before you begin your installation. Lastly, it is recommended that an uninterruptible power supply (UPS) be used with your system and that the battery is regularly tested.
• System Implementation on page 18
• Network Installation on page 18
• Stand-Alone Installation on page 18
• Installation Privileges on page 18
• Firewall Ports on page 19
• System Time Synchronization on page 22
• Implementation Design Requirements for Microsoft SQL Server on page 22
• Philips Event Integration Service on page 23
• Legacy Cisco CallManager on page 24
It is recommended that you review these considerations prior to beginning your installation.
866030-90015 Document Release C Introduction Page 17WARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Preinstallation Information Computer Specifications Version 11.00
System Implementation
When planning your IntelliSpace Event Management implementation, you need to consider the following:
• Users – A user is defined as a person with login rights, who will be setup in the EIS to receive messages and has at least one device setup in their profile.
• A Microsoft SQL Server 2008 SP3 or 2008 R2 SP1, Standard, Enterprise or Datacenter or Express edition (with Advanced Tools) database is required for the EIS. Refer to the Philips IntelliSpace Event Management Database Administrator Guide for more information about database requirements and guidelines.
• Orchestrator and Messenger do not run as stand-alone clients. They depend on connecting to the EIS either on the same machine or over a TCP/IP network.
• An Uninterruptible Power Supply (UPS) should always be used with the Philips system. The UPS should be tested regularly to ensure the batteries are functioning properly.
Remember, if you are planning a virtual environment, a clustered environment, or both, refer to the Philips IntelliSpace Event Management Virtualization Service Guide and the Philips IntelliSpace Event Management Clustering Services Guide before you begin your installation.
Network Installation
IntelliSpace Event Management requires a network adapter card for networked systems. If your system is networked, TCP/IP must be installed. You must know the IP address or the name of the computer(s) where IntelliSpace Event Management is installed. It is recommended that you record the IP address(es) or computer name(s) for future use, if needed. You must be able to ping the IntelliSpace Event Management IP address(es) or computer name(s).
To ensure that network availability, a redundant network path is recommended.
Stand-Alone Installation
When the EIS and Orchestrator, Messenger and/or Alarm Messenger are installed on a stand-alone system TCP/IP must be installed to allow communication between applications. However, a network adapter card is not required to run TCP/IP. Instead you can install the Microsoft Loopback Adapter to simulate the network adapter card. Refer to the help files included with the Philips IntelliSpace Event Management Product Installer for information about installing the Microsoft Loopback Adapter.
Installation Privileges
You must log on with Windows local administrative privileges to install the software. To ensure a successful installation of the software, review the product specifications in the Chapter 3 Hardware Product Specifications on page 37.
Page 18 Introduction 866030-90015 Document Release CWARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Computer Specifications Version 11.00 Preinstallation Information
Firewall Ports
IntelliSpace Event Management requires certain firewall ports to be opened depending on which software products are connecting over the network. Table 4 lists the firewall ports that are required to be opened.
Table 4: IntelliSpace Event Management Firewall Ports Requirements
ProductInbound
Port Number
Outbound Port
NumberDescription
E-mail Messenger 25 The SMTP port is used for the E-mail Messenger to receive e-mail from the Internet.
Philips Event Integration Service (EIS)
25 The SMTP port is used to send e-mail to the Internet. It is also used for some Dispatcher to CIPS Message Manager communications.
Philips Event Integration Service (EIS)
80 The HTTP port is used to make outbound requests to a service provider using the WCTP protocol.
Philips Event Integration Service (EIS) – OAI protocol
5456 The OAI port is used to send messages to Spectralink Netlink Systems.
Philips Event Integration Service (EIS) – OAP protocol
1321 The OAP port is used to send messages to Ascom phones.
Philips Event Integration Service (EIS) – NEMA protocol
5680 The NEMA port is used to send messages.
Philips Event Integration Service (EIS) – SMPP protocol
Carrier defined 8010 (default)
The SMPP port is used to send messages and is defined by the carrier. The default is 8010 and sometimes port 8011 may need to be opened for inbound traffic, depending on the carrier.
Philips Event Integration Service (EIS) – VMI protocol
Vendor defined - typical 5005
The VMI port is used to send messages to Vocera badges. The dispatcher communicates locally with a Vocera provided DLL. The DLL communicates with the Vocera server on an unknown port.
866030-90015 Document Release C Introduction Page 19WARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Preinstallation Information Computer Specifications Version 11.00
Philips Event Integration Service (EIS)
135 This port is used for RPC endpoint mapping. Port 135 must be left open (not firewalled) on the EIS Server for any deployment with an EIS client. EIS clients include:
• Client Applications
• Orchestrator (Orchestrator allows for a port to be specified so it can bypass the endpoint mapper, but other considerations prevent this from being used in practice.)
• Messenger
• Whiteboard
• Command Messenger
• Web Services
• Web Messenger Application Server (the Web service itself)
• CIPS Login
• CIPS Message Manager
• SOAP
• WCTP Push (wowctp.dll)
• Services/Applications
• Alarm Messenger
• Email Messenger
• ENE
• EPS
• ESS
• File Messenger
• Socket Service
• APIs
• COM SDK (as used by Hill-Rom and West Call)
Philips Event Integration Service (EIS)
444 This port is used to make outbound requests to a service provider using the Simple Network Paging Protocol (SNPP).
Philips Event Integration Service (EIS)
1024 - 65535 By default, these ports are dynamically assigned for client to server connections. If needed, you can configure a static connection using a free port in the range shown in the Port Number column. Refer to the Philips IntelliSpace Event Management Orchestrator Service Guide, Server Configuration Connect Tab for information about configuring the endpoint port.
Messenger 12396 This port is used to listen for status updates from the EIS.
Table 4: IntelliSpace Event Management Firewall Ports Requirements (Continued)
ProductInbound
Port Number
Outbound Port
NumberDescription
Page 20 Introduction 866030-90015 Document Release CWARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Computer Specifications Version 11.00 Preinstallation Information
Orchestrator 12397 This port is used to listen for status updates from the EIS.
Alarm Messenger 12398 This port is used to listen for status updates from the EIS.
Web Messenger 135 This port is used for RPC endpoint mapping. Refer to Philips Event Integration Service Port 135 description for more information.
CIPS 135 This port is used for RPC endpoint mapping. Refer to Philips Event Integration Service Port 135 description for more information.
Web Server 80 (default) This port is used to listen for HTTP requests.
• Web Services:
• CIPS Login
• CIPS Message Manager
• Web Messenger
• woWCTP.dll.
Philips Socket Service 5260 (default) 8000 (default)
These ports are configurable in the socketservice.exe.conf file.
SOAP 80 (default) This port is used to listen for HTTP requests. This port is configured to the same port number as the Web Server is configured.
Philips Event Syndication Service (ESS)
3125 This port is used to listen to the SOAP interface.
Philips Event Personalization Service (EPS) – HL7
Configurable This port listens for HL7 messages. Port configuration is done in the Control Panel/Registry.
Philips Event Personalization Service (EPS) – LDAP
389 (default)
This port send requests to the LDAP/Active Directory server. It is configurable in the Orchestrator Server Configuration window Database tab.
Dispatcher/Cisco TSP 2748 TCP port used for the CTI application server. (CallManager)
CIPS Message Manager 80 TCP port used for the CIPS Message Manager Web Service.
CIPS Message Manager 80 TCP port used to send commands to the IP Phone's Web service.
CIPS Login 80 TCP port used for the Web Service.
Table 4: IntelliSpace Event Management Firewall Ports Requirements (Continued)
ProductInbound
Port Number
Outbound Port
NumberDescription
866030-90015 Document Release C Introduction Page 21WARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Preinstallation Information Computer Specifications Version 11.00
System Time Synchronization
To ensure accurate functioning of the IntelliSpace Event Management system, you must synchronize the clocks of all the servers and clients that are part of the Philips solution, including remote SQL Servers. Best practices should be used for system time synchronization. Refer to http://technet2.microsoft.com/WindowsServer/en/library/63de1316-5e25-4ab3-b84b-6f4c7d6358c31033.mspx?mfr=true for information about system time synchronization.
Implementation Design Requirements for Microsoft SQL Server
The EIS database is a real-time component of the EIS. The performance and availability of the database directly impacts performance and operation of the EIS. A Microsoft SQL Server 2008 SP3 or 2008 R2 SP1, Standard, Enterprise or Datacenter or Express edition (with Advanced Tools) database is required.
Either of the following configurations must be implemented:
• The Microsoft SQL Server co-installed with the EIS.
• A remote SQL Server with network latency < 1ms between the IntelliSpace systems the SQL Server. Performance must be equivalent to a co-installed SQL server.
For installations across a network, the Windows user must have administrative access to both systems. This can be a domain user or this can be the same local user created on both systems.
SQL Client Tools and the SQL Management Tools must be installed on the system where EIS is installed and on the system where the SQL Server is installed.
If EIS SQL is co-installed with EIS then a 64-bit version of SQL is required. If EIS SQL is not co-installed with EIS then either a 32-bit or 64-bit version of SQL is supported.
Any other configuration requires contacting an Philips IntelliSpace Event Management representative for analysis and approval before installation.
Philips Event Notification Exporter (ENE)
7777 80 ENE requires outbound port 80 to send Web service subscription request to ESS and by default requires inbound port 7777 to listen for responses. The inbound port can be changed by modifying CallbackListenPort in the ExportService.exe.config file.
Table 4: IntelliSpace Event Management Firewall Ports Requirements (Continued)
ProductInbound
Port Number
Outbound Port
NumberDescription
Page 22 Introduction 866030-90015 Document Release CWARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Computer Specifications Version 11.00 Preinstallation Information
Philips Event Integration Service
The EIS runs as a Windows® service and communicates with in-building wireless systems and wireless operators, various outputs, LED signs, and others. Contact the Philips Sales team for a complete review of the product suite. The Orchestrator is used to configure the EIS. Table 5 lists the basic requirements for wireless data protocols.
Modems
If your configuration requires a modem, for example a fax, you must install the modems with the correct Windows driver. Refer to the modem manufacturer’s documentation for information about using the correct Windows driver. After configuring the modem, you must test it using HyperTerminal®, or a similar dialer, before trying to dial through EIS. If you cannot dial out through the modem using HyperTerminal, or a similar dialer, you will not be able to use the modem in the EIS.
Philips recommends using a dedicated modem line for dialing the carriers. Using a number, such as 9, to reach an outbound line through an internal phone system can cause problems.
The carrier phone number must be a TAP data dial-up number in order to work in the EIS. The carrier phone number cannot be a voice number. You must have all modem communication properties for each carrier before you begin setting up a carrier in EIS. When configuring a new carrier, it is recommended that you contact each carrier’s customer service department and confirm the following information.
• Modem connection information
• Modem access phone number
• Parity
• Stop Bits
• Flow Control on or Flow Control off?
• Maximum messages allowed per a connection
• Largest block size allowed (message length)
• Volume of messages allowed per minute
• Baud rate
• Modem specific user information
• PIN
• Maximum message length allowed for a user, if it is different than the carrier default.
Table 5: Basic Requirements for Wireless Data Protocols
Communication Link
Requirements
Modems TAPI-compliant modems.
RS-232 Serial port and cable, or a serial to IP converter with virtual COM port.
Network (TCP/IP) NIC connected to LAN and WAN services.
866030-90015 Document Release C Introduction Page 23WARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Automatic Update Requirements Computer Specifications Version 11.00
Legacy Cisco CallManager
The Telephony Service Provider (TSP) that Cisco provides for communication with CallManager versions 8.0 and earlier only runs on a 32-bit operating system. IntelliSpace Event Management software 11.00 is only qualified for use on a 64-bit operating system. Integration of IntelliSpace Event Management with Cisco CallManager versions older than 8.5(1)su1 require a 32-bit remote telephony server. Refer to Cisco Remote Telephony Server on page 44 or Cisco Remote Telephony Server Virtual Machine on page 57 for the specific hardware specifications when using a Cisco CallManager 8.0 and earlier. Refer to the IntelliSpace Event Management help files included with the installer for specific configuration instruction.
Automatic Update RequirementsMicrosoft® Windows Automatic Updates must be disabled for all EIS server and gateway installations. Updates must be applied manually during a scheduled maintenance window. Refer to Qualified Platforms and Microsoft Security Updates on page 24 for important information about Microsoft updates.
One of the following settings is recommend to disable Microsoft Windows Automatic Updates:
• Check for updates but let me choose whether to download and install them.
• Never check for updates.
Qualified Platforms and Microsoft Security UpdatesPhilips qualifies Microsoft Security updates for the Philips IntelliSpace Event Management server, adapter and gateway platforms every two months. The Microsoft Security Updates qualification is performed using the Security Release ISO Image releases (available on Microsoft© Download Center).
IMPORTANT: Microsoft Service Packs are not included in the Microsoft Security updates unless specifically noted.
Current Software Updates Qualification Service Bulletin can be accessed from http://www.healthcare.philips.com/us_en/products/hi_pm/products/intellispace/event_management/index.wpd and select the Support Quick Link.
Page 24 Introduction 866030-90015 Document Release CWARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Chapter 2 Product and Configuration Overview
his chapter provides information about the Philips IntelliSpace Event Management system software architecture, standard and enterprise class platforms, adapter types and configuration rules, and system hardware.T
In this chapter:
Introduction on page 26
System Software Architecture on page 26
Component Installation Requirements on page 34
866030-90015 Document Release C Product and Configuration Overview Page 25WARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Introduction Computer Specifications Version 11.00
IntroductionPhilips is the market leader in event notification and alarm management solutions for healthcare organizations. The flagship product, Philips Event Integration Service (EIS), is a client/server software application that provides wireless messaging capabilities to both one-way and two-way pagers, mobile phones, hand-held devices, email, and LED display signs.
Philips IntelliSpace Event Management components are connected to the EIS through a Local Area Network (LAN) or Wide Area Network (WAN) using the TCP/IP protocol. The EIS connects to wireless infrastructures through direct connection, modem connection, LAN or the Internet.
Philips IntelliSpace Event Management components are installed using the Philips IntelliSpace Event Management, Web Assignments and Historical Database (HDB) installation programs. Refer to the specific component Product Installation Help Files for installation instructions.
Event Notification
IntelliSpace Event Management has the capability to integrate and manage a wide variety of clinical and non-clinical events, and alarms.
• Clinical events are location events generated from people and equipment.
• Non-clinical events are events such as fire, security, life safety, and building services/control events.
These events and alarms can be managed using the following integration models:
• Machine-to-Human: Events generated by a medical device, system or application for the purposes of real-time notification to an assigned caregiver or designated individual or group.
An example is when a patient monitoring or nurse call event is distributed to an assigned caregiver.
• Machine-to-Machine: Events generated by a medical device, system, or application for the purposes of real-time notification to a designated machine such as a medical device, system, application, apparatus, and others.
An example is when Philips IntelliSpace Event Management sends a “bed needs cleaning” request from a nurse call system to a bed management system.
System Software ArchitecturePhilips offers two types of software configurations — the IntelliSpace Event Management Gateway, which is a bundled solution and the IntelliSpace Event Management Service Bus, which is an unbundled solution.
• The IntelliSpace Event Management Gateway comprises one input adapter, one or more output or administration adapters, and Philips IntelliSpace Event Management software and hardware.
• The IntelliSpace Event Management Event Service Bus is the central architectural component and core engine of the Philips IntelliSpace Event Management platform. Using the IntelliSpace Event Management Event Service Bus solution allows you to have a built-to-order system that best suits your environment.
Page 26 Product and Configuration Overview 866030-90015 Document Release CWARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Computer Specifications Version 11.00 System Software Architecture
Patient Monitoring Gateway
The IntelliSpace Event Management Patient Monitoring Gateway (PMG) extends the function of the existing patient monitoring and telemetry systems to deliver automated secondary event notification to numerous devices. Figure 1 illustrates how the PMG is used.
Figure 1. Patient Monitoring Gateway
Patient Monitoring
System
WTS
AccessPoint
AccessPoint
AccessPoint
PagingTransmitter
Wireless Phone
Alphanumeric Pager
Wireless Phone
Application Layer Integration Layer Communication Layer
Patient Monitoring Gateway
Patient Monitoring Gateway
866030-90015 Document Release C Product and Configuration Overview Page 27WARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
System Software Architecture Computer Specifications Version 11.00
IntelliSpace Event Management Nurse Call Gateway
The IntelliSpace Event Management Nurse Call Gateway (NCG) extends the function of the existing nurse call systems to deliver automated event notification to all types of devices. Figure 2 illustrates how the NCG is used.
Figure 2. Nurse Call Gateway
Nurse CallGateway
Nurse CallSystem
WTS
AccessPoint
AccessPoint
AccessPoint
TAP/RS-232
Telephony Dial BackLines
PagingTransmitter
Hospital’s PBX
Wireless Phone
Alphanumeric Pager
Patient CallButton
Patient CallButton
Patient CallButton
Wireless Phone
Protocol/Transport
Protocol/Transport
Application Layer Integration Layer Communication Layer
Nurse Call Gateway
Page 28 Product and Configuration Overview 866030-90015 Document Release CWARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Computer Specifications Version 11.00 System Software Architecture
Event Service Bus (ESB)
IntelliSpace Event Management Event Service Bus is the core engine of the Philips integration architecture. Event Service Bus includes various services that automate the Philips platform. These include services that enable the importing of hospital Admit, Discharge, and Transfer (ADT), optional location services, and directory information such as staff/user directories.
The Philips IntelliSpace Event Management Event Service Bus architecture is scalable and flexible. The IntelliSpace Event Management ESB architecture consists of three main components, which include Event Integration Service ESB, third-party integration adapters, and the user interface (Orchestrator). These components are illustrated in Figure 3.
Figure 3. IntelliSpace Event Management System Software Architecture Diagram
Location Services
Staff Directory
Patient Directory
Nurse Call System
Patient Monitoring
System
Ventilator Mgmt
System
Dispatching System
Building Automation
System
Bed Mgmt
System
NC Adapter
PM Adapter
Bed Mgmt
System
IS Adapter
IS Adapter
Facilities Adapter
Event Integration Service
UserInterface
(Orchestrator)
Time & Attendance
Adm
inis
tra
tive
Ad
apte
rs
Communication (Output) Adapters
Paging System
PBX/Wireless Telephone
System
Voice Recognition
System
Cellular Service
Providers
Applications, Devices, or
Systems
Event (Input) Adapters
866030-90015 Document Release C Product and Configuration Overview Page 29WARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
System Software Architecture Computer Specifications Version 11.00
IntelliSpace Event Management Platforms
IntelliSpace Event Management is configured on a IntelliSpace Event Management platform. The customer should select the platform best suited for their environment based on system size and performance requirements.
Table 6 on page 30 lists the configuration rules and limitations for both the IntelliSpace Event Management gateway and IntelliSpace Event Management Service Bus Class platforms.
Table 6 describes what each IntelliSpace Event Management server can support and provides a summary of the IntelliSpace Event Management configuration rules.
In the case of limits being exceeded for an IntelliSpace Event Management system, the customer is required to install another instance of an IntelliSpace Event Management server. If a second IntelliSpace Event Management system is required to meet scalability requirements, then a separate/additional server and a second instance of Philips IntelliSpace Event Management software are required.
Table 6: IntelliSpace Event Management Configuration Rules
Platform LimitationsIntelliSpace Event
Management Gateways IntelliSpace Event Management (ESB)
Hardware Platform Requirements Refer to Chapter 3 Hardware Product Specifications on page 37
Refer to Chapter 3 Hardware Product Specifications on page 37
Maximum Adapters (Input or Administrative)
1 Input adapter, LDAP and ADT adapters can also be used.
16
Concurrent Orchestrator Clients 15 50
Concurrent Web Messenger Clients 25 200
Concurrent Whiteboard Clients with a minimum refresh delay of 30 seconds
15 30
Beds 512 1000
Users 5000 <20000
Groups Up to 1000 Up to 5000
Message Storage (the last 200,000 messages processed by the system). Message logs can be archived for long term event management and reporting.
Up to 200,000 Up to 200,000
Minimum Server Requirements Gateway Server IntelliSpace Event Management Event Service Bus Class Server
Database Requirement SQL 2008 with SP3, SQL Server 2008 R2 SP1 – Express with Advanced Tools, Standard, Enterprise, or Datacenter editions
SQL 2008 with SP3, SQL Server 2008 R2 SP1 Standard, Enterprise, or Datacenter editions. SQL Express is supported, if HDB is not required. However, it is not recommended
Page 30 Product and Configuration Overview 866030-90015 Document Release CWARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Computer Specifications Version 11.00 System Software Architecture
Philips Integration Adapters
Philips integration adapters are used to establish input and output connections of third party systems to IntelliSpace Event Management. Philips has several types of integration adapters for establishing connection to the IntelliSpace Event Management.
Adapters are available for a wide variety of systems, applications, and medical devices. There are three types of adapters:
• Input
• Output
• Administrative
Input and administrative adapters reside on IntelliSpace Event Management Server which can run one or more adapters. Refer to IntelliSpace Event Management System Software Architecture Diagram on page 29.
Because the alert dispatch function is a component of the Philips Event Integration Service (EIS), which is a part of IntelliSpace Event Management, output adapters must reside on the same server box as IntelliSpace Event Management.
Input Adapters
Input adapters connect various systems that generate events and alarms to IntelliSpace Event Management. Input adapters include patient monitoring, nurse call, IV pumps, building automation (fire, security, life safety), clinical applications (EMR), manufacturing, and so forth.
It is recommended that a co-installed SQL server be used for Adapter Servers for the message persistence queue to reduce load on the EIS production SQL server.
Other examples of input adapters that Philips can support are connections such as e-mail or file transfers (FTP).
Output Adapters
Output adapters connect IntelliSpace Event Management to various communication systems that are typically the interface to the managed end-points, such as a caregiver’s portable or wireless communication device.
Other examples of output adapters include e-mail or fax output. Output adapters can also be used for machine-to-machine communications. In this case, the output adapter can be another machine that processes the event information integrated through the IntelliSpace Event Management such as a medical device or server/application.
Administrative Adapters
Administrative adapter connection types include: staff directory, patient directory, and location services.
The Philips Event Personalization Service (EPS) is the Philips software adapter component that facilitates the importing of information/data, also referred to as meta data, that can be used to automate the Philips IntelliSpace Event Management platform, as well as user and system administration tasks.
Meta data is defined as patient directory or ADT (Admit, Discharge, and Transfer), staff directory information, location /proximity information such as location services, or time & attendance data.
For example: ADT meta data contains data about the patient, such as age, sex, race, height, weight, and so forth. Meta data can be imported using a variety of protocols including LDAP for staff directory and HL7 for ADT.
866030-90015 Document Release C Product and Configuration Overview Page 31WARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
System Software Architecture Computer Specifications Version 11.00
The Philips Event Personalization Service (EPS) can be installed on a dedicated system or co-installed on the IntelliSpace Event Management server. EPS for LDAP is required to be co-installed with EIS.
Orchestrator Client
The Philips Orchestrator client application is the user interface to IntelliSpace Event Management. The Orchestrator client includes modules for message dispatching, staff/device assignments, command center, white board, and reporting. Figure 4 illustrates a typical configuration with six Input and Administrative Adapters.
Figure 4. Philips Adapters - Typical Configuration with Six Input and Administrative Adapters.
Page 32 Product and Configuration Overview 866030-90015 Document Release CWARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Computer Specifications Version 11.00 System Software Architecture
Adapter Rules
The Philips platform and architecture offers flexibility in structuring so various adapters can run on different servers or the same server. However, due to regulatory and/or performance considerations, certain rules apply for determining what adapters should be installed on an IntelliSpace Event Management Server/EAS.
For example, a patient monitoring adapter and nurse call adapter should not be installed on the same IntelliSpace Event Management Server/EAS, while other servers can run multiple adapters, such as the ADT and LDAP administrative adapters.
Refer to Table 8 on page 34 which lists the Philips components, adapters, and where they should be installed. Table 7 lists the configuration rules that apply to the Philips Adapters.
Note: Regarding the output system, the EIS can process a large number of events per hour (depending on the database used). In practice, all output/communication systems have limitations and often this is the determining factor for overall end-to-end system throughput. Often the end-to-end throughput limitation is determined by the bandwidth of the output/communication system. A Philips representative can consult with sites to make specific recommendations for communication system sizing.
Table 7: Configuration Rules for Philips Adapters
Configuration Rules for Philips Adapters
• Never mix regulated medical devices (vendor/product) on the same IntelliSpace Event Management Adapter Server (EAS). For Example; A patient Monitoring Adaptor for Philips PIIC can only be used to connect Philips PIIC devices.
• Never mix regulated medical devices and non-regulated input devices on the same IntelliSpace Event Management Adapter Server (EAS).
• Multiple vendors of the same type of non-regulated input devices cannot be mixed on the same IntelliSpace Event Management Adapter Server (EAS).
• Multiple dissimilar non-regulated input device types may be mixed on the same IntelliSpace Event Management Adapter Server (EAS).
• Output adapters always run on the same server as IntelliSpace Event Management/Philips Event Integration Service.
• Up to eight Administrative Adapters can be combined onto a single IntelliSpace Event Management Standard Class Server/EAS. Check with your Philips representative for any exceptions to this rule. The Philips Event Personalization Service (EPS) can be installed on a dedicated system or co-installed on the IntelliSpace Event Management server.
• Up to eight Nurse Call systems from the same vendor can connect to the one nurse call adapter that connects to the IntelliSpace Event Management Standard Class Server/EAS.
• Up to eight Patient Monitors systems from the same vendor can connect to the one patient monitor adapter that connects to the IntelliSpace Event Management Standard Class Server/EAS.
• Rules for total end user destinations or endpoints that will receive events processed by IntelliSpace Event Management must always be adhered. Refer to Table 6 on page 30.
• All servers that run a Philips adapter must be sized appropriately according to recommended published guidelines. Refer to Chapter 3 Hardware Product Specifications on page 37.
• System throughput limitation is often based on the capacity or ability of the output communication system to process output messages.
866030-90015 Document Release C Product and Configuration Overview Page 33WARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Component Installation Requirements Computer Specifications Version 11.00
Component Installation RequirementsTable 8 lists the component installation requirements and options.
Table 8: Component Installation Requirements and Options
Component Typical Installation LocationOptional Installation
Location
Alarm Messenger IntelliSpace Event Management, Philips Adapter Server,IntelliSpace Event Management GW
CIPS Applications IntelliSpace Event Management, IntelliSpace Event Management GW
Command Messenger Clients IntelliSpace Event Management, IntelliSpace Event Management GW
Philips Event Integration Service
IntelliSpace Event Management, IntelliSpace Event Management GW
Note: EPS for LDAP is required to be co-installed with EIS.
E-mail Messenger IntelliSpace Event Management, IntelliSpace Event Management GW
File Messenger IntelliSpace Event Management, IntelliSpace Event Management GW
Philips Event Messenger Clients IntelliSpace Event Management, IntelliSpace Event Management GW
Philips Event Orchestrator Clients, IntelliSpace Event Management, IntelliSpace Event Management GW
Philips Adapter Server
Philips Web Messenger IntelliSpace Event Management, IntelliSpace Event Management GW
Input Adapter IntelliSpace Event Management GW, Philips Adapter Server
Output Adapters IntelliSpace Event Management, IntelliSpace Event Management GW
Administrative Adapters IntelliSpace Event Management, IntelliSpace Event Management GW, Philips Adapter Server
IntelliSpace Event Management
Legacy Cisco CallManager TSP
Remote Telephony Server
Note: Legacy Cisco CallManager TSP is not an IntelliSpace Event Management component. However, it must be installed if CallManager 8.0 or earlier is installed.
Philips Adapter Server – Philips Adapter Server – Input and Administrative Adapters.
IntelliSpace Event Management GW – Gateway – All components on one machine.
IntelliSpace Event Management – The central architectural component and core engine of the Philips platform. The IntelliSpace Event Management runs the Philips Event Integration Service (EIS).
Clients - a client PC meeting Philips requirements.
Page 34 Product and Configuration Overview 866030-90015 Document Release CWARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Computer Specifications Version 11.00 Component Installation Requirements
866030-90015 Document Release C Product and Configuration Overview Page 35WARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Chapter 3 Hardware Product Specifications
his chapter provides the hardware specifications for the Philips IntelliSpace Event Management system. The information in this chapter contains the minimum and recommended hardware requirements as related to processor class, memory and storage
requirements, the supported operating system, and SQL requirements for non-virtual environments, virtual environments, and clustered environments. Software requirements for specific components can be found in Chapter 4 Software Product Specifications on page 63. Additionally, this chapter provides information regarding the location or the co-location of various components and, information about storage and optional cards.
T
In this chapter:
Non-Virtual Environment Specifications on page 38
Client Machine Specifications on page 45
Virtual Environment Specifications on page 46
Deployment Best Practices on page 46
Deployment Requirements on page 46
HA and non-HA System Layout on page 58
System Layout For Microsoft Clustered Environments on page 59
Storage on page 61
Optional Computer Cards on page 61
866030-90015 Document Release C Hardware Product Specifications Page 37WARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Non-Virtual Environment Specifications Computer Specifications Version 11.00
Non-Virtual Environment SpecificationsThis section contains the following information and specifications for a non-virtual environment:
• Gateway Server on page 38
• Philips Event Adapter Server (EAS) on page 39
• EIS Server on page 40
• Blade Servers on page 43
• Cisco Remote Telephony Server on page 44
• IIS Server Virtual Machine on page 56
Note: For non-virtualized environments, serial ports and/or expander cards are required for serial connections.
Gateway Server
For Gateway solution (Nurse Call Gateway, Patient Monitoring Gateway, Philips Communications Gateway).
Gateway Server
Operating System 64-bit Microsoft Windows Server 2008 R2 SP1 Standard, Enterprise, and Datacenter versions. The operating system must be English language.
Database Microsoft Windows SQL 2008 SP3, or SQL Server 2008 R2 SP1 (service pack is required) Standard, Enterprise (recommended), or Datacenter editions.
Components Required Recommended
Processor 1.8-2.2 GHz Core 2 Duo 6300 series
1.8 GHz Xeon 5200 series
2.0 GHz Xeon 5500 or 5600 series
Single socket Intel CPU
Xeon 2.0 GHz or faster 5500 or 5600 series (5520 or higher)
Memory (Remote SQL) 4 GB memory 6 GB memory
Memory (Local SQL) 4 GB memory 6 GB memory
Note: 6GB Memory is strongly recommended for co-installed SQL Server configuration
Hard Disk 72GB Single SATA or SAS disk drive RAID1, 5 or 10 72GB or larger total storage space with Hot Plug SAS 10,000 rpm or faster Hard Drives
Disk controller upgrade Disk Controller Cache of sufficient size and speed for the RAID capacity with battery backup.
CD/DVD DVD-ROM DVD-ROM
USB 2.0 Port USB 2.0 Port USB 2.0 Port
Power Supply Single power supply Redundant Power Supplies
Page 38 Hardware Product Specifications 866030-90015 Document Release CWARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Computer Specifications Version 11.00 Non-Virtual Environment Specifications
Philips Event Adapter Server (EAS)
Philips Event Adapter Server (EAS)
Operating System 64-bit Microsoft Windows Server 2008 R2 SP1 Standard, Enterprise, and Datacenter versions. The operating system must be English language.
Database Microsoft Windows SQL 2008 SP3, or SQL Server 2008 R2 SP1 (service pack is required) Standard, Enterprise (recommended), or Datacenter editions.
Components Required Recommended
Processor 1.8 GHz Xeon 5200 series
2.0 GHz Xeon 5500 or 5600 series
Single socket Intel CPU
Xeon 2.0 GHz or faster 5500 or 5600 series (5520 or higher)
Memory (Remote SQL) 4 GB memory 6 GB memory
Memory (Local SQL) 4 GB memory 6 GB memory
Hard Disk 72GB 7,200 rpm Hard Drives RAID1, 5 or 10 72GB or larger total storage space with Hot Plug SAS 10,000 rpm or faster Hard Drives
Disk controller upgrade Disk Controller Cache of sufficient size and speed for the RAID capacity with Battery backup.
CD/DVD DVD-ROM DVD-ROM
USB 2.0 Port USB 2.0 Port USB 2.0 Port
Power Supply Single power supply Redundant Power Supplies
866030-90015 Document Release C Hardware Product Specifications Page 39 WARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Non-Virtual Environment Specifications Computer Specifications Version 11.00
EIS Server
For use as an EIS (Event Integration Service) server.
EIS Server
Operating System64-bit Microsoft Windows Server 2008 R2 SP1 Standard, Enterprise, and Datacenter versions. The operating system must be English language.
DatabaseMicrosoft Windows SQL 2008 SP3, or SQL Server 2008 R2 SP1 (service pack is required) Standard, Enterprise (recommended), or Datacenter editions.
Components Required Recommended
Processor 1.8 GHz Xeon 5200 series
2.0 GHz Xeon 5500 or 5600 series
Single socket Intel CPU
Xeon 2.0 GHz or faster 5500 or 5600 series (5520 or higher)
Memory (Remote SQL) 4 GB memory 6 GB memory
Memory (Local SQL) 4 GB memory 6 GB memory
Note: 6GB Memory is strongly recommended for co-installed SQL Server configuration
Hard Disk 72GB 7,200 rpm Hard Drives RAID1, 5 or 10 72GB or larger total storage space with Hot Plug SAS 10,000 rpm or faster Hard Drives
Disk controller upgrade Disk Controller Cache of sufficient size and speed for the RAID capacity with Battery backup
CD/DVD DVD-ROM DVD-ROM
USB 2.0 Port USB 2.0 Port USB 2.0 Port
Power Supply Single power supply Redundant power supply
Page 40 Hardware Product Specifications 866030-90015 Document Release CWARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Computer Specifications Version 11.00 Non-Virtual Environment Specifications
EIS Server when connected to HDB
For use as an EIS (Event Integration Service) server solution when connected to HDB.
EIS Server when connected to HDB
Operating System 64-bit Microsoft Windows Server 2008 R2 SP1 Standard, Enterprise, and Datacenter versions. The operating system must be English language.
Database Microsoft Windows SQL 2008 SP3, or SQL Server 2008 R2 SP1 (service pack is required) Standard, Enterprise (recommended), or Datacenter editions. SQL Native Client is required.
Components Required Recommended
Processor 1.8 GHz Xeon 5200 series
2.0 GHz Xeon 5500 series
Single socket Intel CPU
Xeon 2.0 GHz or faster 5500 or 5600 series (5520 or higher)
Memory (Remote SQL) 4 GB memory 6 GB memory
Memory (Local SQL) 4 GB memory 6 GB memory
Note: 6GB Memory is strongly recommended for co-installed SQL Server configuration
Hard Disk RAID1with 500GB or larger total storage space with Hot Plug SAS 10,000 rpm or faster Hard Drives
RAID1, 5 or 10 500GB or larger total storage space with Hot Plug SAS 10,000 rpm or faster Hard Drives
Note: The 500GB disk requirement is for the primary SQL server when the EIS SQL database is co-installed with EIS. Otherwise, the 500GB disk needs to be located on the SQL server.
Disk controller upgrade Disk Controller Cache of sufficient size and speed for the RAID capacity with Battery backup.
CD/DVD DVD-ROM DVD-ROM
USB 2.0 Port USB 2.0 Port USB 2.0 Port
Power Supply Single power supply Redundant Power Supplies
866030-90015 Document Release C Hardware Product Specifications Page 41 WARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Non-Virtual Environment Specifications Computer Specifications Version 11.00
HDB SQL Server
For use with the Historical Database (HDB).
IntelliSpace Event Management HDB SQL Server
Operating System 64-bit Microsoft Windows Server 2008 R2 SP1 Standard, Enterprise, and Datacenter versions. The operating system must be English language.
Database Microsoft Windows SQL 2008 SP3, or SQL Server 2008 R2 SP1 (service pack is required) Standard, Enterprise (recommended), or Datacenter editions. SQL Native Client is required..
Components Required Recommended
Processor 1.8 GHz Xeon 5200 series
2.0 GHz Xeon 5500 series
Single socket Intel CPU
Xeon 2.0 GHz or faster 5500 or 5600 series (5520 or higher)
Memory Allocation 6GB 8GB
Note: An additional 4GB beyond the required value should be allocated if Reporting Services is coinstalled on the HDB SQL Server
An additional 4GB beyond the required value should be allocated iMicrosoft Windows SQL 2008 SP3, or SQL Server 2008 R2 SP1 (service pack is required) Standard, Enterprise (recommended), or Datacenter editions. SQL Native Client is required.If IIS is coinstalled on the HDB SQL Server for Reporting Services.
16GB is strongly recommended If both Reporting Services and IIS are coinstalled on the HDB SQL server.
Hard Disk (Datastore) with HDB Refer to Database Storage Considerations on page 53.
Note: Database Best Practice disk configurations should be used for SQL Server configurations. Database Best Practice includes that operating systems and programs, databases, and logs reside on different disks.
Disk controller upgrade Disk Controller Cache of sufficient size and speed for the RAID capacity with battery backup.
USB 2.0 Port USB 2.0 Port USB 2.0 Port
Power Supply Single power supply Redundant power supply
Page 42 Hardware Product Specifications 866030-90015 Document Release CWARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Computer Specifications Version 11.00 Non-Virtual Environment Specifications
IIS Server
The specifications for the IIS Server apply to the Philips IntelliSpace Event Management components requiring IIS. This includes Personal Assignments servers, stand-alone Web Messenger servers.
Blade Servers
Blade servers should follow the preceding solution guidelines and use the following for the Modular Enclosure.
IIS Server
Operating System 64-bit Microsoft Windows Server 2008 R2 SP1 Standard, Enterprise, and Datacenter versions. The operating system must be English language.
Components Required Recommended
Processor 1.8 GHz Xeon 5200 series
2.0 GHz Xeon 5500 or 5600 series
Single socket Intel CPU
Xeon 2.0 GHz or faster 5500 or 5600 series (5520 or higher)
Memory 4 GB memory 6 GB memory
Hard Disk 72GB 7,200 rpm Hard Drives RAID1, 5 or 10 72GB or larger total storage space with Hot Plug SAS 10,000 rpm or faster Hard Drives
Disk controller upgrade Disk Controller Cache of sufficient size and speed for the RAID capacity with Battery backup.
CD/DVD DVD-ROM DVD-ROM
USB 2.0 Port USB 2.0 Port USB 2.0 Port
Power Supply Single power supply Redundant Power Supplies
Components Required Recommended
Power Supply Redundant power supply
Cooling Fans Redundant Cooling Fans
Network Pass Through Ethernet
CD/DVD DVD-ROM DVD-ROM
USB 2.0 Port USB 2.0 Port USB 2.0 Port
KVM Integrated KVM
866030-90015 Document Release C Hardware Product Specifications Page 43 WARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Non-Virtual Environment Specifications Computer Specifications Version 11.00
Cisco Remote Telephony Server
The Cisco Remote Telephony server is used when configuring a Cisco CallManager 8.0 or earlier for an IEM 11.00 system.
Cisco Remote Telephony Server for CallManager 8.0 and earlier
Operating System 32-bit Microsoft Windows Server 2008 SP2 Standard, Enterprise, and Datacenter versions. The operating system must be English language.
Components Required Recommended
Processor 1.8 GHz Xeon 5200 series
2.0 GHz Xeon 5500 or 5600 series
Single socket Intel CPU
Xeon 2.0 GHz or faster 5500 or 5600 series (5520 or higher)
Memory 2 GB memory 3 GB memory
Hard Disk 72GB 7,200 rpm Hard Drives RAID1, 5 or 10 72GB or larger total storage space with Hot Plug SAS 10,000 rpm or faster Hard Drives
Disk controller upgrade Disk Controller Cache of sufficient size and speed for the RAID capacity with Battery backup.
CD/DVD DVD-ROM DVD-ROM
USB 2.0 Port USB 2.0 Port USB 2.0 Port
Power Supply Single power supply Redundant Power Supplies
Page 44 Hardware Product Specifications 866030-90015 Document Release CWARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Computer Specifications Version 11.00 Client Machine Specifications
Client Machine SpecificationsThe specifications listed in this section apply to the Orchestrator, Messenger, Whiteboard, and Command Messenger.
Client System
Resource Required Recommended
Operating System One of the following:
• Microsoft Windows XP Professional (x86) SP3• Microsoft Vista Professional, Ultimate, or Enterprise (x86) SP1• Microsoft Server 2003 (x86) SP1, SP2, R2• Microsoft Windows 2008 R2 no SP or SP1• Windows 7 Professional, Enterprise and Ultimate x86 or x64
Windows 7 Professional, Enterprise, or Ultimate x86 or x64
Note: The operating system must be English language.
CPU Cores 1.6GHz Dual Core 2GHz Dual core or better
Memory • Microsoft Windows XP Professional (x86) SP3 - 512MB
• Microsoft Vista Professional, Enterprise, or Ultimate (x86) SP1 - 2GB
• Microsoft Server 2003 (x86) SP1, SP2, R2 - 1GB
• Microsoft Server 2008 R2 - 2GB
• Microsoft Windows 7 - 2GB
• Microsoft Windows XP Professional (x86) SP3 - 1GB
• Microsoft Vista Professional, Enterprise, or Ultimate (x86) SP1 - 3GB
• Microsoft Server 2003 (x86) SP1, SP2, R2 - 2GB
• Microsoft Server 2008 R2 - 4GB
• Microsoft Windows 7 - 4GB
Hard Disk 100GB 250GB
CD/DVD CD-ROM DVD-ROM
USB 2.0 Port USB 2.0 Port USB 2.0 Port
Network Adapter 100Mbps 1Gbps
Display SXGA - 1024x768 SXGA 1280x1024
866030-90015 Document Release C Hardware Product Specifications Page 45 WARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Virtual Environment Specifications Computer Specifications Version 11.00
Virtual Environment SpecificationsThis section contains the following information and specifications for a virtual environment:
• Deployment Best Practices on page 46
• Deployment Requirements on page 46
• HA and non-HA System Layout on page 58
• System Layout For Microsoft Clustered Environments on page 59
• Storage on page 61
• Optional Computer Cards on page 61
Refer to VMware product documentation for more information about virtual machines.
Deployment Best PracticesThe following are recommended best practices derived from configuration and testing of Philips IntelliSpace Event Management (IEM) running on VMware virtual infrastructure.
• It is recommended that you use Intel-based Nehalem or AMD-based Shanghai processors which have the Hardware-Assist capabilities that help in performing memory management operations.
• While using Intel-based systems, ensure that the BIOS settings enable Hyperthreading, VT, and EPT options on all ESX hosts.
• Use Eager zeroed disks for better I/O performance. This can be done using the following VMware vmkfstools command:
vmkfstools –w abc.vmdk• To decrease disk latency, it is recommended that you use Fibre Channel Adapters and
configure proper RAID configuration with sufficient Spindles.
• Install VMware tools on the virtual machines. The VMware Tools package provides support required for shared folders and for drag and drop operations. Other tools in the package support synchronization of time in the guest operating system with time on the host, automatic grabbing and releasing of the mouse cursor, copy and paste operations between guest and host, and improved mouse performance in some guest operating systems.
• Consider using server-class network interface cards (NICs) for the best performance and configure paravirtualized vmxnet3 adapters for better network throughput.
• Ensure that the Service Console / VMkernel and virtual machines are configured on separate NICs.
• If possible, configure all the virtual machines for the IntelliSpace Event Management product suite on the same virtual switch. Having virtual machines on separate switches will cause transmission of traffic over different wires, resulting in additional CPU and network overhead.
• Disconnect or disable unused or unnecessary physical hardware devices, such as:
• COM ports
• LPT ports
• Floppy drives
Deployment RequirementsThe following are requirements for deploying Philips IntelliSpace Event Management (IEM) on VMware virtual infrastructure.
Page 46 Hardware Product Specifications 866030-90015 Document Release CWARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Computer Specifications Version 11.00 Deployment Requirements
Resource Management Requirements
Philips IEM is a near real-time notification system that requires resources to be available with low latency to provide acceptable response times in clinical environments. Therefore one or both of the following are required to be configured:
Option A
• Set resource allocations based on the Virtual Machine specifications for the server type.
• Virtual host utilization must be monitored and alert notifications implemented to assure that resources are always sufficient to support average and peak loads on Philips IEM virtual machines. We advise setting up the following alerts (vCenter console and SMTP or SNMP):
• CPU utilization exceeding 66% for more than 30 seconds
• Memory utilization exceeding 66% for more than 30 seconds
See http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_admin_guide.pdf for instructions.
Option B
• Set resource allocations based on the Virtual Machine specifications for the server type.
• The following reservations set for IntelliSpace Event Management virtual servers:
Event Service Bus/Adapter Servers (ESB)• 2.8 GHz CPU
• 512 MB Memory
Note: Refer to Adapter Server Virtual Machine on page 50 and Event Management Server Virtual Machine on page 51 specifications for additional details.
Gateway Servers (MS SQL server installed on another VM)• 2.8 GHz CPU
• 512 MB Memory
Note: Refer to Gateway Server Virtual Machine on page 49 specifications for additional details.
Gateway Servers (co-installed MS SQL server)• 5.6 GHz CPU
• 1 GB Memory
Note: Refer to Gateway Servers (co-installed MS SQL server) on page 47 specifications for additional details.
Database Servers• 5.6 GHz CPU
• 2 GBs Memory
Note: See IntelliSpace Event Management SQL Server Virtual Machines specifications for additional details, especially when co-installing Reporting Services and IIS
An additional 1GB should be reserved if Reporting Services are co-installed
An additional 1GB should be reserved if IIS is co-installed
866030-90015 Document Release C Hardware Product Specifications Page 47 WARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Deployment Requirements Computer Specifications Version 11.00
Note: The reservation specifications are not the same as the allocation specifications for the VMs. For instance, though the 2.8GHz CPU reservation is an approximation of the cycles per second for one core, our requirements for VM configurations specify at least two cores.
Cisco Remote Telephony Server• 2.8 GHz CPU
• 512 MB Memory
Note: Refer to Cisco Remote Telephony Server Virtual Machine on page 57 and Event Management Server Virtual Machine on page 51 specifications for additional details.
vMotion
Given that movements with vMotion may take between 1 and 2 minutes, do not perform movements during production unless absolutely required for the health of the machine (clinical notification is strongly recommended). Though vMotion may not produce actual downtime for the virtual machine, it can cause slowness that may impact IEM’s near real-time messaging.
DRS
Philips IEM is a near real time notification system that requires resources to be available with low latency to provide acceptable response times in clinical environments. The process of moving a VM introduces noticeable delay into message delivery, therefore one or both of the following configurations are required:
Option A
• Configure DRS Automation Level to “Disabled” for IEM VMs and move non-IEM VMs to balance the hosts instead on Virtual Hosts using Fully Automated DRS.
Option B
• Do not configure DRS for “Fully Automated” migration mode on hosts for the Philips IEM virtual machines. Use the “Partially Automated” setting where DRS automated movements are limited to startup. Use DRS recommendations to move IEM virtual machine.
High Availability (HA)
High Availability protects against hardware failures on the virtual host that can cause failure or degradation of performance of the virtual machines. When using HA, we require VMware tools be installed on all IEM virtual machines so that High Availability can also be configured to monitor that our virtual machines are still running. HA will not detect service-level failure on IEM virtual machines, but can be configured to detect if the virtual machine has stopped responding to the heartbeat request.
IEM Services Configuration for use with HA
All IEM services except EPS (Event Personalization Service) are required to have the Service Control Manager recovery options configured to Restart the Service on First failure, Restart the Service on Second failure and Restart the Computer on Subsequent failures.
The EPS (Event Personalization Service) is required to configure the Service Control Manager recovery options configured to Restart the Service on First failure, Restart the Service on Second failure and Restart the Service on Subsequent failures. Alternately, the Subsequent failures setting could be set to Run a Program to send a notification to IT to take action.
Page 48 Hardware Product Specifications 866030-90015 Document Release CWARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Computer Specifications Version 11.00 Deployment Requirements
Gateway Server Virtual Machine
The specifications for the Gateway Server Virtual Machine apply to the Philips IntelliSpace Event Management.
Gateway Server Virtual Machine
Virtual Machine Platforms VMware ESX/ESXi 4.1, VMware ESX/ESXi 5.0
Operating System Microsoft Windows Server 2008 R2 SP1 Standard, Enterprise and Datacenter Versions. The operating system must be English language.
Database Microsoft SQL Server 2008 SP3, or SQL Server 2008 R2 SP1(service pack is required) Standard, Enterprise, Datacenter or Express with Advanced Tools Editions
Resource Required Recommended
CPU Cores 2
CPU MHz (total) Allocate 5.6 GHz
CPU Shares/Reservation/Unlimited
Refer to Resource Management Requirements Option A and Option B on page 47
Memory Allocation 4GB 6GB
Note: 6GB Memory is strongly recommended for a co-installed SQL Server configuration
Memory Shares/Reservation/Unlimited
Refer to Resource Management Requirements Option A and Option B on page 47
Hard Disk (Datastore) 72GB 72GB
Disk Shares/Reservation/Unlimited
Unlimited
Network Adapter 100Mbps 1Gbps
COM Ports As required for input and output systems
As required for input and output systems
Note: Virtual COM port software connecting to an input/output device local serial/IP converter is recommended over use of direct allocation of VM host local COM ports. The Yield CPU on Poll option should be left enabled (default).
Display N/A, client workstation with remote access software (vSphere) must meet OS or Philips client requirements
N/A, client workstation with remote access software (vSphere) must meet OS or Philips client requirements
866030-90015 Document Release C Hardware Product Specifications Page 49 WARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Deployment Requirements Computer Specifications Version 11.00
Adapter Server Virtual Machine
The specifications for the Adapter Server Virtual Machine apply to the Philips IntelliSpace Event Management input adapters (Alarm Messenger, Socket Service, SOAP SDK) and the Philips Event Personalization Service (EPS).
Adapter Server Virtual Machine
Virtual Machine Platforms VMware ESX/ESXi 4.1, VMware ESX/ESXi 5.0
Operating System Microsoft Windows Server 2008 R2 SP1 Standard, Enterprise Versions and Datacenter. The operating system must be English language.
Database Microsoft SQL Server 2008 SP3, or SQL Server 2008 R2 SP1(service pack is required) Standard, Enterprise, Datacenter or Express with Advanced Tools Editions
Note: It is recommended that a co-installed SQL server be used for Adapter Servers for the message persistence queue to reduce load on the EIS production SQL server.
Resource Required Recommended
CPU Cores Allocation 2
CPU MHz (total allocation) Allocate 5.6 GHz
CPU Shares/Reservation/Unlimited
Refer to Resource Management Requirements Option A and Option B on page 47
Memory Allocation 4GB 4GB
Memory Shares/Reservation/Unlimited
Refer to Resource Management Requirements Option A and Option B on page 47
Hard Disk (Datastore) 72GB 72GB
Disk Shares/Reservation/Unlimited
Unlimited
Network Adapter 100Mbps 1Gbps
COM Ports As required for input and output systems
As required for input and output systems
Note: Virtual COM port software connecting to an input/output device local serial/IP converter is recommended over use of direct allocation of VM host local COM ports. The Yield CPU on Poll option should be left enabled (default).
Display N/A, client workstation with remote access software (vSphere) must meet OS or Philips client requirements
N/A, client workstation with remote access software (vSphere) must meet OS or Philips client requirements
Page 50 Hardware Product Specifications 866030-90015 Document Release CWARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Computer Specifications Version 11.00 Deployment Requirements
Event Management Server Virtual Machine
The specifications for the Event Management Server Virtual Machine apply to the Philips IntelliSpace Event Management.
Event Management Server Virtual Machine
Virtual Machine Platforms VMware ESX/ESXi 4.1, VMware ESX/ESXi 5.0
Operating System Microsoft Windows Server 2008 R2 SP1 Standard, Enterprise and Datacenter Versions. The operating system must be English language.
Database Microsoft SQL Server 2008 SP3, or SQL Server 2008 R2 SP1(service pack is required) Standard, Enterprise, Datacenter or Express with Advanced Tools Editions
Note: It is recommended that the SQL server reside on a separate machine.
Resource Required Recommended
CPU Cores Allocation 2
CPU MHz (total allocation) Allocate 5.6 GHz
Note: If Web Messenger is deployed with 100 users or more, 3 CPU Cores must be allocated.
CPU Shares/Reservation/Unlimited
Refer to Resource Management Requirements Option A and Option B on page 47
Memory Allocation 4GB 6GB
Note: 6GB Memory is strongly recommended for a co-installed SQL Server configuration
Memory Shares/Reservation/Unlimited
Refer to Resource Management Requirements Option A and Option B on page 47
Hard Disk (Datastore) 72GB 146GB
Note: If HDB is installed, the Required disk is 500GB.
Disk Shares/Reservation/Unlimited
Unlimited
Network Adapter 100Mbps 1Gbps
COM Ports As required for input and output systems
As required for input and output systems
Note: Virtual COM port software connecting to an input/output device local serial/IP converter is recommended over use of direct allocation of VM host local COM ports. The Yield CPU on Poll option should be left enabled (default).
Display N/A, client workstation with remote access software (vSphere) must meet OS or Philips client requirements
N/A, client workstation with remote access software (vSphere) must meet OS or Philips client requirements
866030-90015 Document Release C Hardware Product Specifications Page 51 WARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Deployment Requirements Computer Specifications Version 11.00
IntelliSpace Event Management SQL Server Virtual Machines
The specifications for the SQL Server apply to the Philips IntelliSpace Event Management.
IntelliSpace Event Management SQL Server Virtual Machine
Virtual Machine Platforms VMware ESX/ESXi 4.1, VMware ESX/ESXi 5.0
Database Microsoft SQL Server 2008 SP3, or SQL Server 2008 R2 SP1(service pack is required) Standard, Enterprise or Datacenter Editions
Resource Required Recommended
CPU Cores Allocation 2 4
Note: An additional CPU core beyond the required value should be allocated if Reporting Services is co-installed on the HDB SQL Server
Note: An additional CPU core beyond the required value should be allocated if IIS is co-installed on the HDB SQL Server for Reporting Services
CPU MHz (total allocation) 5.6GHz 11.2GHZ
CPU Shares/Reservation/Unlimited
Refer to Resource Management Requirements Option A and Option B on page 47
Memory Allocation 6GB 8GB
Note: An additional 4GB beyond the required value should be allocated if Reporting Services is co-installed on the HDB SQL Server
Note: An additional 4GB beyond the required value should be allocated if IIS is co-installed on the HDB SQL Server for Reporting Services
Note: 16GB is strongly recommended If both Reporting Services and IIS are co-installed on the HDB SQL server.
Memory Shares/Reservation/Unlimited
Refer to Resource Management Requirements Option A and Option B on page 47
Hard Disk (Datastore) - no HDB 146GB 300GB
Hard Disk (Datastore) with HDB 500GB 500GB
Note: Database Best Practice disk configurations should be used for SQL Server configurations. Database Best Practice includes that operating systems and programs, databases, and logs reside on different disks.
Network Adapter 1Gbps 1Gbps
Display N/A, client workstation with remote access software (vSphere) must meet OS or Philips client requirements
N/A, client workstation with remote access software (vSphere) must meet OS or Philips client requirements
Page 52 Hardware Product Specifications 866030-90015 Document Release CWARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Computer Specifications Version 11.00 Deployment Requirements
Database Storage Considerations
The HDB product was developed and designed to provide customers with the ability to store long term data outside of the production environment. The data is extracted from the production environment using SQL Server transactional replication. This historical data can be used for alert generation analysis, custom reports and custom queries.
HDB storage requirements will be different for each site depending on the volume of alerts processed and the amount of data retained. The staging database is set to purge data older than 60 days. The 10.0 release of the historical database added a feature that will allow you to configure the amount of historical data to retain as well. Refer to Philips IntelliSpace Event Management Historical Database and reporting Administrator Guide, Chapter 4 Database Maintenance for more information about data retention. Growth projections for historical data over time are shown below.
IntelliSpace Event Management HDB SQL Server Virtual Machine
Virtual Machine Platforms VMware ESX/ESXi 4.1, VMware ESX/ESXi 5.0
Database Microsoft SQL 2008 SP3, or SQL Server 2008 R2 SP1(service pack is required) Standard, Enterprise or Datacenter Editions
Resource Required Recommended
CPU Cores Allocation 2 4
CPU MHz (total allocation) 5.6GHz 11.2GHz
CPU Shares/Reservation/Unlim-ited
Refer to Resource Management Requirements Option A and Option B on page 47
Memory Allocation 6GB 8GB
Memory Shares/Reservation/Unlimited
Refer to Resource Management Requirements Option A and Option B on page 47
Hard Disk (Datastore) with HDB Refer to Database Storage Considerations on page 53
Note: Database Best Practice disk configurations should be used for SQL Server configurations. Database Best Practice includes that operating systems and programs, databases, and logs reside on different disks.
Network Adapter 1Gbps 1Gbps
Display N/A, client workstation with remote access software (vSphere) must meet OS or Philips client requirements
N/A, client workstation with remote access software (vSphere) must meet OS or Philips client requirements
866030-90015 Document Release C Hardware Product Specifications Page 53 WARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Deployment Requirements Computer Specifications Version 11.00
Storage Calculations
The tables below provide storage guidelines for HDB based on alert volume. Table 9 and Table 10 project maximum storage requirements in kilobytes (KB) per alert based on IntelliSpace Event Management Internal Testing.
The following two tables project the amount of storage required over time for the two scenarios presented in Table 11 and Table 12.
Table 9: Storage Requirement in KB per Alert (if waveform images are sent with alerts
File Type Storage Size
SQL Data Files 240 KBs per Alert
SQL Log Files 48 KBs per Alert
Database Backup Files 223 KBs per Alert
Transaction Log Backup Files 433 KBs per Alert
Distribution Data and Log 112 KBs per Alert
TOTAL KBs per Alert 1056 KBs per Alert
Table 10: Storage Requirement in KB per Alert (if no waveform images are sent with alerts
File Type Storage Size
SQL Data Files 20 KBs per Alert
SQL Log Files 15 KBs per Alert
Database Backup Files 47 KBs per Alert
Transaction Log Backup Files 54 KBs per Alert
Distribution Data and Log 43 KBs per Alert
TOTAL KBs per Alert 179 KBs per Alert
Table 11: Storage Requirement for Alerts with Waveform Images Over Time - Total Storage
Total Storage (1,056 KBs/Alert)
Alert Rate
Alerts Per
Second
Alerts Per
Hour
Alerts Per Day
Per Day Storage
KBs
Alerts Per
Month
Per Month Storage
KBs
Alerts Per Year
Per Year Storage
KBs
1 every 5 seconds
0.2 720 17,280 18,247,680 518,400 547,430,400 6,307,200 6,660,403,200
1 every 2 seconds
0.5 1800 43,200 45,619,200 1,296,000 1,368,576,000 15,768,000 16,651,008,000
1 every 1 second
1 3600 86,400 91,238,400 2,592,000 2,737,152,000 31,536,000 33,302,016,000
2 every 1 second
2 7200 172,800 182,476,800 5,184,000 5,474,304,000 63,072,000 66,604,032,000
3 every 1 second
3 10800 259,200 273,715,200 7,776,000 8,211,456,000 94,608,000 99,906,048,000
Page 54 Hardware Product Specifications 866030-90015 Document Release CWARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Computer Specifications Version 11.00 Deployment Requirements
Table 12: Storage Requirement for Alerts without Waveform Images Over Time - Total Storage
Total Storage (179 KBs/Alert)
Alert Rate
Alerts Per
Second
Alerts Per
Hour
Alerts Per Day
Per Day Storage
KBs
Alerts Per
Month
Per Month Storage
KBs
Alerts Per Year
Per Year Storage
KBs
1 every 5 seconds
0.2 720 17,280 3,093,120 518,400 92,793,600 6,307,200 1,128,988,800
1 every 2 seconds
0.5 1800 43,200 7,732,800 1,296,000 231,984,000 15,768,000 2,822,472,000
1 every 1 second
1 3600 86,400 15,465,600 2,592,00 463,968,000 31,536,000 5,644,944,000
2 every 1 second
2 7200 172,800 30,931,200 5,184,000 927,936,000 63,072,000 11,289,888,000
3 every 1 second
3 10800 259,200 46,396,800 7,776,000 1,391,904,000 94,608,000 16,934,832,000
866030-90015 Document Release C Hardware Product Specifications Page 55 WARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Deployment Requirements Computer Specifications Version 11.00
IIS Server Virtual Machine
The specifications for the IIS Server Virtual Machine apply to the Philips IntelliSpace Event Management components requiring IIS. This includes Personal Assignments servers, stand-alone Web Messenger servers, IIS server for HDB Reports, and IIS components in Microsoft Cluster configurations.
IIS Server Virtual Machine
Virtual Machine Platforms VMware ESX/ESXi 4.1, VMware ESX/ESXi 5.0
Operating System 64-bit Microsoft Windows Server 2008 R2 SP1 Standard, Enterprise, and Datacenter versions. The operating system must be English language.
Resource Required Recommended
CPU Cores Allocation 2 2
CPU MHz (total allocation) Allocate 5.6 GHz
CPU Shares/Reservation/Unlimited
Refer to Resource Management Requirements Option A and Option B on page 47
Memory Allocation 4GB 4GB
Memory Shares/Reservation/Unlimited
Refer to Resource Management Requirements Option A and Option B on page 47
Hard Disk (Datastore) 72GB 72GB
Disk Shares/Reservation/Unlimited
Unlimited
Network Adapter 100Mbps 1Gbps
Display N/A, client workstation with remote access software (vSphere) must meet OS or Philips client requirements
N/A, client workstation with remote access software (vSphere) must meet OS or Philips client requirements
Page 56 Hardware Product Specifications 866030-90015 Document Release CWARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Computer Specifications Version 11.00 Deployment Requirements
Cisco Remote Telephony Server Virtual Machine
The Cisco Remote Telephony virtual server is used when configuring a Cisco CallManager 8.0 or earlier for an IEM 11.00.
Cisco Remote Telephony Server Virtual Machine
Virtual Machine Platforms VMware ESX/ESXi 4.1, VMware ESX/ESXi 5.0
Operating System 32-bit Microsoft Windows Server 2008 SP2 Standard, Enterprise, and Datacenter versions. The operating system must be English language.
Resource Required Recommended
CPU Cores Allocation 2 2
CPU MHz (total allocation) Allocate 5.6 GHz
CPU Shares/Reservation/Unlimited
Refer to Resource Management Requirements Option A and Option B on page 47
Memory Allocation 2GB 3GB
Memory Shares/Reservation/Unlimited
Refer to Resource Management Requirements Option A and Option B on page 47
Hard Disk (Datastore) 72GB 72GB
Disk Shares/Reservation/Unlimited
Unlimited
Network Adapter 100Mbps 1Gbps
Display N/A, client workstation with remote access software (vSphere) must meet OS or Philips client requirements
N/A, client workstation with remote access software (vSphere) must meet OS or Philips client requirements
866030-90015 Document Release C Hardware Product Specifications Page 57 WARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
HA and non-HA System Layout Computer Specifications Version 11.00
HA and non-HA System Layout For Physical and Virtual Environments
The system layout for physical servers also applies to virtual servers in a VMware environment including HA (High Availability) deployments.
IntelliSpace Event Management (EIS)
File Messenger
IIS/Web Services:
CIPS Login
CIPS Message Manager
WCTP Push – wowctp.dll
Web Messenger
Email Messenger
ENE SOAP instance
ENE
ENE ESS instance
EPS for LDAP - required to be installed with EIS
EPS for ADT optionally co-installed
ESB Server (physical or virtual)
Server (physical or virtual) IIS for Personal Assignments
IIS for HDB Reporting
IIS for stand-alone Web Messenger
Web Services
Server (physical or virtual) IIS for HDB Reporting
SQL Server
SQL Server configured for HDB
Reporting Service
HDB and Reporting
Input Adapter Servers
Server (physical or virtual) EPS Only Co-located with EIS - optional configuration
Server (physical or virtual) Philips/Socket
Socket Service Alarm Messenger
Patient Monitoring Adapters
Server (physical or virtual) Any Philips SOAP
SOAP IIS
ESS (optional) Alarm Messenger
EPS Adapter
Server (physical or virtual) Any Philips SOAP
SOAP IIS
ESS (optional) Alarm Messenger
Nurse Call Adapter Server (physical or virtual) Any Philips SOAP
SOAP IIS
ESS (optional)
Alarm Messenger
Server (physical or virtual)
All other protocols1
Alarm Messenger
Server (physical or virtual)
All other protocols1
Alarm Messenger
Note: COM based inputs (e.g. WestCall or Hill-Rom NCM/ NNC COM) do not use an adapter and connect directly to
Server (physical or virtual)
All other protocols1
Alarm Messenger
Location Tracking Adapters
Location Tracking Adapters
Server (physical or virtual) Any Philips SOAP
SOAP IIS
ESS (optional) Alarm Messenger
Facility Adapters
Server (physical or virtual)
All other protocols1
Alarm Messenger 1 Other protocols can include TAP, TNPP, and so forth.
Page 58 Hardware Product Specifications 866030-90015 Document Release CWARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Computer Specifications Version 11.00 Cisco Remote Telephony Server Layout
Cisco Remote Telephony Server LayoutThe Cisco Remote Telephony server must be set up when using Cisco CallManager 8.0 or earlier.
System Layout For Microsoft Clustered Environments• The system layout for clustered environments applies to VM host machines and virtual
machines.
• It is recommended that a host machine have no more than 10 virtual machines.
• IIS servers are not clustered.
• Each SOAP instance in a cluster requires a separate IIS server virtual machine.
• When a configuration calls for more than one IIS server, the IIS servers need to be distributed across the physical hosts.
• Multiple ESBs in a single cluster are not qualified at this time.
• If cluster virtual machines and/or the host machine use iSCSI SAN, then an additional SAN NIC is required. If either uses fiber channel SAN, then a Host Bus Adapter (HBA) is required.
• Rocket Port Modem Card is not supported in a cluster. Instead, use virtual COM port(s) to external modems or modem bank.
• Microsoft Windows Server 2008 R2 SP1 Enterprise or Datacenter are required for clustered servers.
IntelliSpace Event Management (EIS)
File Messenger
IIS/Web Services:
CIPS Login
CIPS Message Manager
WCTP Push – wowctp.dll
Web Messenger
Email Messenger
ENE SOAP instance
ENE
ENE ESS instance
EPS for LDAP - required to be installed with EIS
EPS for ADT optionally co-installed
ESB Server (physical or virtual)
Server (physical or virtual) Remote Telephony Service Cisco TSP (TAPI Service Provider)
Telephony Services
866030-90015 Document Release C Hardware Product Specifications Page 59 WARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
System Layout For Microsoft Clustered Environments Computer Specifications Version 11.00
Clustered Node Pair
VM Host Machine 2
EIS
File Messenger
(Points to the EIS cluster IP)
EPS
(Points to the EIS cluster IP)
EIS
File Messenger
(Points to the EIS cluster IP)
EPS
(Points to the EIS cluster IP)
Alarm Messenger for SOAP
(One per SOAP instance. This points to the EIS cluster IP)
Alarm Messenger for SOAP
(One per SOAP instance. This points to the EIS cluster IP)
Socket Service and Alarm Messenger
• Socket service points to this Alarm Messenger cluster IP and to the EIS cluster IP
• Alarm Messenger points to EIS cluster IP
Socket Service and Alarm Messenger
• Socket service points to this Alarm Messenger cluster IP and to the EIS cluster IP
• Alarm Messenger points to EIS cluster IP
Primary IIS Server• CIPS Login (Points to the EIS
Cluster IP)
• CIPS Message Manager (Points to the EIS Cluster IP)
• WCTP Push - wowctp.dll (Points to the EIS Cluster IP)
• Web Messenger (Points to the EIS Cluster IP)
• Email Messenger (Points to the EIS Cluster IP)
• ENE (Points to the EIS Cluster IP)
• ENE SOAP adapter (install SOAP only)
• SOAP points to the EIS cluster IP
• ESS points to the EIS cluster IP
Additional IIS servers installed on separate virtual machines for each additional SOAP adapter (SOAP only)
• Each SOAP points to its Alarm Messenger cluster IP and the EIS cluster IP
• Each ESS points to EIS cluster IP
VirtualMachine
VM Host Machine 1
VirtualMachine
VirtualMachine
Cluster Service
Cluster Service
Cluster Service
VirtualMachine
Page 60 Hardware Product Specifications 866030-90015 Document Release CWARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Computer Specifications Version 11.00 Storage
StorageThis section provides the following storage information for the EIS and all adapters:
• Storage Area Network on page 61
• Networked Attached Storage on page 61
Storage Area Network
If you are using a Storage Area Network (SAN), review the following information for:
• Dedicated SAN
• Managed Multisystem SAN
• Unmanaged Multisystem SAN
Dedicated SAN
A dedicated SAN is connected directly to the EIS and used exclusively by the EIS and adapters. A dedicated SAN is presented as a normal disk to Windows with comparable data rates. A dedicated SAN can be used in the same manner as a normal attached storage with no impact on the Philips software operation.
Managed Multisystem SAN
A managed multisystem SAN is not used exclusively for EIS and adapters. A managed multisystem SAN is presented as a normal disk to Windows. This configuration can only be used if the site guarantees that SAN data rates comparable to locally attached storage can be maintained.
Unmanaged Multisystem SAN
An unmanaged multisystem SAN is not supported because bandwidth and access cannot be guaranteed.
Note: Connection failures from the server to the SAN display in the Windows System event log as delayed write errors. The delayed write errors begin to display at the time of connection loss.
Networked Attached Storage
Networked Attached Storage (NAS) is not supported because bandwidth and access cannot be guaranteed.
Optional Computer CardsPhilips has approved computer cards to support optional system functionality or expand standard system functionality. Table 13 describes the optional cards including their system requirements.
Additionally, a TAPI-compliant modem is required for dial-up connections.
Note: Winmodems are not supported.
Table 13: Optional Computer Cards
Card Description Connector Type Form Factor
Comtrol/RocketPort 8 Port Serial 32 Bit PCI/64 Bit PCI-X Full Height. 1/2 Depth
RocketModem III 4 Port 32 Bit PCI/64 Bit PCI-X Full Height. 1/2 Depth
RocketModem III 8 Port 32 Bit PCI/64 Bit PCI-X Full Height, Full Depth
U.S. Robotics V.92 Modem 1 Port 32 Bit PCI/64 Bit PCI-X 1/2 Height, 1/2 Depth
866030-90015 Document Release C Hardware Product Specifications Page 61 WARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Optional Computer Cards Computer Specifications Version 11.00
Page 62 Hardware Product Specifications 866030-90015 Document Release CWARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Chapter 4 Software Product Specifications
his chapter provides the software specifications for the Philip IntelliSpace Event Management. The information in this chapter contains the minimum and recommended software requirements.T
In this chapter:
Installation Prerequisites on page 64
Philips Event Integration Service on page 67
Philips Event Personalization Service on page 70
E-mail Messenger on page 72
Web Messenger Server on page 72
Web Messenger Client on page 73
File Messenger on page 74
Command Messenger on page 75
Orchestrator on page 76
Whiteboard on page 77
Messenger on page 78
Alarm Messenger on page 80
Philips Event Notification Exporter on page 82
Philips SOAP SDK on page 83
Philips Event Syndication Service on page 83
Philips Socket SDK on page 83
Unified Counters Viewer on page 84
Philips Historical Database on page 84
Historical Database Reporting on page 85
Personal Assignments on page 86
866030-90015 Document Release C Software Product Specifications Page 63WARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Installation Prerequisites Computer Specifications Version 11.00
Installation PrerequisitesIn addition to the software specifications listed in this chapter the following items must be configured:
• All installers; Philips IntelliSpace Event Management, Personal Assignments on Mobile Device, Historical Database and Documentation must have Microsoft Windows Installer 4.5 or later and .Net 4.0 full profile installed.
Note: Although .Net 4.0 framework with Full Profile is required for the HDB and Personal Assignments installers, the application software only requires .Net 3.5 framework.
• The IntelliSpace Event Management Event Integration Service installations requires the following:
• The Fax Server role must be enabled. To enable the fax server, on the task bar select Server Manager | Roles | Add Roles | Fax Server.
• Microsoft Data Access Components (MDAC) - version 2.81.1117.6
• Microsoft SQL Server 2008 SP3, or SQL Server 2008 R2 SP1(service pack is required) Standard, Enterprise, Datacenter or Express with Advanced Tools Editions, Native Client Driver
• Microsoft XML - 6.10.1200
• If you are installing Orchestrator on a Windows Server 2008 R2 SP1, you must install Windows Media Player. To install Windows Media Player:
1.On the taskbar, click Start | Computer | Manage. The Server Manager displays.
2.In the left pane click Features. The Features pane displays on the right.
3.Scroll down and select Desktop Experience and click Install. The Windows Media Player is now installed.
• Alarm Messenger requires the following:
• Microsoft Data Access Components (MDAC) - version 2.81.1117.6
• Microsoft XML - version - 6.10.1200
• Microsoft SQL Server 2008 SP3, or SQL Server 2008 R2 SP1(service pack is required) Standard, Enterprise, Datacenter or Express with Advanced Tools Editions, Native Client Drive
• IIS for Web Service Applications
Web service applications require Internet Information Services (IIS) 7.5 to be installed and configured before using the service. By default, IIS is not installed on the Windows Server 2008 R2 SP1. Before IIS can be installed, Microsoft.NET Framework 4.0 must be installed. Refer to the documentation provided with Windows Server 2008 R2 SP1 for information about installing Microsoft .NET Framework 4.0.
Table 14 on page 65 lists the IIS and role services and features required by each Web application installed using the Philips IntelliSpace Event Management installation program. To add roles, on the task bar select Server Manager | Roles | Add Roles and to add features Server Manager | Roles | Add Features.
Page 64 Software Product Specifications 866030-90015 Document Release CWARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Computer Specifications Version 11.00 Installation Prerequisites
Table 14: IIS and Required Role Services
Application Requirements
CIPS Applications • Web Server (IIS)
Philips E-mail Messenger • IIS
• SMTP Server feature
SOAP Toolkit • Microsoft Internet Information Server (IIS)
• Microsoft Windows 2008 R2 Role Services
• ASP.NET
Socket SDK • Microsoft Internet Information Server (IIS)
Event Syndication Service • Microsoft Internet Information Server (IIS)
Philips Web Messenger • Microsoft Data Access Components (MDAC)
• Microsoft Internet Information Server (IIS)
• Microsoft Windows 2008 R2 Role Services
• ASP.NET
• IIS Management Console
• IIS Management Scripts and Tools
• IIS 6 Metabase Compatibility
• IIS 6 WMI Compatibility
• IIS 6 Scripting Tools
• IIS 6 Management Console
• Static Content
• Default Document
• Basic Authentication
• Windows Authentication
HDB Reporting • Microsoft Internet Information Server (IIS)
• Microsoft Windows 2008 R2 Role Services
• ASP.NET
• IIS Management Console
• IIS Management Scripts and Tools
• Static Content
• Default Document
• Basic Authentication
• Windows Authentication
866030-90015 Document Release C Software Product Specifications Page 65 WARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Installation Prerequisites Computer Specifications Version 11.00
• The following components have no software installation prerequisites:
• Command Messenger
• Messenger
• Whiteboard
Personal Assignments • Microsoft Data Access Components (MDAC)
• Microsoft Internet Information Server (IIS)
• Microsoft Windows 2008 R2 Role Services
• ASP.NET
• IIS Management Console
• IIS Management Scripts and Tools
• Static Content
• Default Document
• Basic Authentication
• Windows Authentication
Table 14: IIS and Required Role Services (Continued)
Application Requirements
Page 66 Software Product Specifications 866030-90015 Document Release CWARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Computer Specifications Version 11.00 Philips Event Integration Service
Philips Event Integration Service The Philips Event Integration Service (EIS) specifications are described in the sections listed below.
• Philips Event Integration Service Software Operating Environment on page 67
• Additional Notes and Considerations for the Philips Event Integration Service on page 68
• Philips Event Integration Service Features and Limits on page 68
Philips Event Integration Service Software Operating Environment
Table 15lists the Philips Event Integration Service (EIS) software operating environment requirements.
Table 15: Philips Event Integration Service Software Operating Environment
Validated Software
Philips Event Integration Service
Basic Requirements
With CIPS Installed
With Web Services Installed (Philips Web Messenger
Service and E-mail Messenger)
64-bit Microsoft Windows Server 2008 R2 SP1 Standard, Enterprise, and Datacenter versions. The operating system must be English language.
Yes Yes Yes
Microsoft .NET 3.5 Yes Yes Yes
Microsoft Windows Installer 4.5 or later Yes Yes Yes
Microsoft XML Parser (MSXML) Version 6 SP1
Yes Yes Yes
TCP/IP (IPv4) - non clustered and clustered environments
TCP/IP (IPv6) - clustered environment
Yes Yes Yes
Microsoft MDAC 6.1 or later Yes
Microsoft IIS 7.5 Yes Yes, additionally Web Messenger needs IIS 6 compatibility configured.
Microsoft Windows SQL 2008 SP3, or SQL Server 2008 R2 SP1 Express with Advanced Tools, Standard, Enterprise (Recommended) or Datacenter editions. SQL Native Client is required.
All Web services, except Philips Web Messenger
Note: If EIS SQL is co-installed with EIS then a 64-bit version of SQL is required. If EIS SQL is not co-installed with EIS then either a 32-bit or 64-bit version of SQL is supported.
866030-90015 Document Release C Software Product Specifications Page 67 WARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Philips Event Integration Service Computer Specifications Version 11.00
Additional Notes and Considerations for the Philips Event Integration Service
The following list contains additional information about the EIS software specifications and additional requirements that may apply depending on the configuration.
• If your server is a domain controller or Active Directory server, only Orchestrator, Command Messenger, and Messenger can be installed on the system.
• Dedicated Internet access is required for SMTP, SNPP or WCTP protocol support.
• One E-mail address with relay capabilities is required.
• Microsoft Internet Information Server (IIS) 7.5 is required for CIPS applications and WCTP. Web Messenger requires IIS 6.0 compatibility mode to be configured. Refer to Table 14 on page 65 for a complete list of IIS requirements.
Philips Event Integration Service Features and Limits
Table 16 lists the EIS features and feature limits.
Table 16: Philips Event Integration Service Features, Feature Limits, and Notes
Feature Limit Notes
User profiles 100,000 Based on Authorization Code
Devices per use 10
Devices in a sequence 10 Number of devices in a user’s list used for device sequencing
Devices in escalation 10 Number of devices in a user’s list used for device escalation
Groups No limit 5000 maximum recommended
Group members 1000
Carriers No limit 500 maximum recommended
Connected clients No limit Based on Authorization Code
Activity Log size 5000 messages
Message Log size 200,000 messages or 999 days
Use of reporting functions during normal messaging operation with a Message log size greater than 1500 messages causes message delivery delays during the report processing.
Message length 40 – 16384 characters
Message priority levels 15
Recipients per message No limit Limit to output system capabilities
Scheduled messages No limit 500 maximum recommended
Recipients per scheduled message No limit 100 maximum recommended
Escalated messages No limit 100 maximum recommended
Recipients per escalated level No limit 100 maximum recommended
Alarm Sensitivity Level 256
Page 68 Software Product Specifications 866030-90015 Document Release CWARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Computer Specifications Version 11.00 Philips Event Integration Service
Alarm Categories 512
Canned Messages 50
Staff Assignment Escalation levels 3
Escalation levels 5
Escalation Group levels 5
Escalation Group members 25 Per level. The output system must be able to support the total number of recipients within a level.
Escalation minimum level interval 30 seconds
Modems1 No limit 50 maximum recommended
Direct connect ports No limit 50 maximum recommended
TTS/IVR ports 96 Based on Authorization Code. Currently 24 ports are validated.
Failed messages before alerting 2 Two or more messages to the carrier must fail before a failed messages server alert is issued.
Queued messages before alerting 500 Configure the number of messages queued to a carrier before a queued messages alert is issued.
Performance is impacted when the messages also contain images.
Duplicate message filters 5 Number of message filters that can be configured in the Sever Configuration Message tab.
SNPP: poll rate 60 second minimum / One hour maximum
WCTP: poll rate2 60 second minimum Carrier may enforce a 5 minute minimum.
WCTP: response per poll 500
Polling duration 1 hour minimum / 7 day maximum
OAI phone directory size No limit 500 records recommended
WOPro Log file size 256 KB each 200 files
Dispatch Log file size 256 KB each 200 files
TAP: messages per connection 1 - 300 20 messages default
TAP: block size 10 - 4072 bytes 256 bytes default
TAP: maximum message length Block size less 16 bytes 240 bytes default
Table 16: Philips Event Integration Service Features, Feature Limits, and Notes (Continued)
Feature Limit Notes
866030-90015 Document Release C Software Product Specifications Page 69 WARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Philips Event Personalization Service Computer Specifications Version 11.00
Philips Event Personalization Service In the Philips Event Personalization Service (EPS) the Admit, Discharge, and Transfer (ADT) interface accepts and processes related Health Level 7 (HL7) messages to provide the following functions:
• Create new user accounts and monitor the Patient Identifier List and any values used as an alternative ID to ensure unique patient identification
• Create new locations
• Create association between patient and location
• Create association between locations and profiles
• Change patient’s location
• Change association between patient and location
• Remove patient
• Combine patient’s records
Users can create nurse station profile definitions in the Orchestrator GUI. The user can define Keys and definitions for each station at the site. The information is stored in the EIS database and collected by the EPS upon initialization. This information is used to create new user profiles and to associate the EIS patient record with the location and zone. Up to 200 zones are supported.
In EPS, records can be imported from the LDAP directory server to the EIS database. However, only fields needed to create user accounts in the EIS database are imported from LDAP directory.
Note: If you have Philips Event Personalization Service (EPS) configured and if it is available at the time EIS is started, EIS attempts to initialize communication with EPS. If EIS successfully initializes communication, EPS is responsible for importing records from the Active Directory/LDAP server. If EPS is available at startup, but is not available when an import is scheduled, the import fails until the EPS becomes available again.
The EPS can only connect to or interoperate with a single system or over a single port number.
The EPS specifications are described in the following sections:
• Event Personalization Service Software Operating Environment on page 71
• Additional Notes for the Event Personalization Service Specifications on page 71
SMTP, SNPP: maximum message
length2, 34096 bytes
SMPP, WCTP: maximum message
length24096 bytes
LDAP Filter Size 4096 characters
1Winmodems are not supported
2Dedicated Internet access is required for SMTP, SNPP, and WCTP output.
3An Open Relay e-mail server is required for SMTP.
Table 16: Philips Event Integration Service Features, Feature Limits, and Notes (Continued)
Feature Limit Notes
Page 70 Software Product Specifications 866030-90015 Document Release CWARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Computer Specifications Version 11.00 Philips Event Personalization Service
Event Personalization Service Software Operating Environment
Table 17 lists the Event Personalization Service software operating environment requirements.
Additional Notes for the Event Personalization Service Specifications
The following list contains additional information about the Event Personalization Service specifications.
• If your server is a domain controller or an Active Directory server, only Orchestrator and Messenger can be installed on the server.
• The Microsoft Windows operating system may have higher system requirements than listed. If so, use the minimum system requirements published by Microsoft.
Table 17: Event Personalization Service Software Operating Environment
Event Personalization Service Software Operating Environment
Software Basic Requirements
64-bit Microsoft Windows Server 2008 R2 SP1 Standard, Enterprise, and Datacenter versions. The operating system must be English language.
Yes
Microsoft Windows Installer 4.5 or later Yes
Microsoft XML Parser (MSXML) Version 6 SP1 Yes
TCP/IP (IPv4) - non clustered and clustered environments
TCP/IP (IPv6) - clustered environment
Yes
Microsoft Windows SQL 2008 SP3, or SQL Server 2008 R2 SP1 Express with Advanced Tools, Standard, Enterprise (Recommended) or Datacenter editions. SQL Native Client is required..
Yes
Note: If EPS SQL is co-installed with EPS then a 64-bit version of SQL is required. If EPS SQL is not co-installed with EPS then either a 32-bit or 64-bit version of SQL is supported.
866030-90015 Document Release C Software Product Specifications Page 71 WARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
E-mail Messenger Computer Specifications Version 11.00
E-mail MessengerThe E-mail Messenger is installed on the same server as EIS. Refer to Philips Event Integration Service on page 67 for more information about the software specifications and to Chapter 3 Hardware Product Specifications on page 37 for hardware specifications. Additional information about the E-mail Messenger is described in the sections below.
• Additional Notes for the E-mail Messenger Specifications on page 72
• E-mail Messenger Features and Limits on page 72
Additional Notes for the E-mail Messenger Specifications
The following list contains additional information about the E-mail Messenger specifications.
• Microsoft Windows operating system may have higher system requirements than listed. If so, use the minimum system requirements published by Microsoft.
E-mail Messenger Features and Limits
Table 18 lists the E-mail Messenger features and feature limits.
Web Messenger ServerThe Web Messenger is installed on the same server as EIS. Refer to Philips Event Integration Service on page 67 for software specifications and to Chapter 3 Hardware Product Specifications on page 37 for hardware specifications. Refer to Table 14 on page 65 for a complete list of IIS requirements.
Microsoft Windows operating system may have higher system requirements than listed. If so, use the minimum system requirements published by Microsoft.
Table 18: E-mail Messenger Features, Feature Limits, and Notes
Feature Limit Notes
Recipients per message 1 User, group or PIN/carrier
Log File size 512 KB
Page 72 Software Product Specifications 866030-90015 Document Release CWARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Computer Specifications Version 11.00 Web Messenger Client
Web Messenger ClientThe Web Messenger Client specifications are described in the following sections:
Web Messenger Client Software Operating Environment on page 73
Additional Notes for the Web Messenger Client Specifications on page 73
Web Messenger Client Features and Limits on page 73
Web Messenger Client Software Operating Environment
Table 19 lists the Web Messenger Client software operating environment requirements.
Additional Notes for the Web Messenger Client Specifications
The following list contains additional information about the Web Messenger Client specifications.
• Web Messenger Client must be added to the allowed Pop-up sites list for the browser.
• The Web Messenger Client does not function on Microsoft Windows Server 2003 or Microsoft Windows Server 2008 R2 if the Internet Explorer Enhanced Security Configuration is enabled.
• The Microsoft Windows operating system may have higher system requirements than listed. If so, use the minimum system requirements published by Microsoft.
Web Messenger Client Features and Limits
Table 20 lists the Web Messenger Client features and feature limits.
Table 19: Web Messenger Client Software Operating Environment
Web Messenger Client Software Operating Environment
Software Recommended Mandatory Validated
TCP/IP (IPv4) Yes Yes
Microsoft Internet Explorer 6, 7, or 8 Yes Yes
Firefox 3 Yes
Table 20: Web Messenger Client Features, Feature Limits, and Notes
Feature Limit Notes
PAB user devices 1 Device per recipient
PAB users 25
PAB groups 25
PAB group members 10 Includes server users
Recipients per message No limit
Edit devices N/A Must own device
MCR lists 10
866030-90015 Document Release C Software Product Specifications Page 73 WARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
File Messenger Computer Specifications Version 11.00
File Messenger The File Messenger specifications are described in the following sections:
• File Messenger Software Operating Environment on page 74
• Additional Notes for the File Messenger on page 74
• File Messenger Features and Limits on page 74
File Messenger Software Operating Environment
Table 21 lists the File Messenger software operating environment requirements.
Additional Notes for the File Messenger
Microsoft Windows operating system may have higher system requirements than listed. If so, use the minimum system requirements published by Microsoft.
File Messenger Features and Limits
Table 22 lists the File Messenger features and feature limits.
Table 21: File Messenger Software Operating Environment
File Messenger Software Operating Environment
Software Recommended Mandatory Validated
64-bit Microsoft Windows Server 2008 R2 SP1 Standard, Enterprise, and Datacenter versions. The operating system must be English language.
Yes Yes Yes
Microsoft Windows Installer 4.5 or later Yes Yes
TCP/IP (IPv4) – non-clustered environment
TCP/IP (IPv6) – clustered environment
Yes Yes
Table 22: File Messenger Features, Feature Limits, and Notes
Feature Limit Notes
Directories to scan 5
Messages per file 1
Recipients per message 1 Recipient type can be a user, group or PIN/carrier
Escalation levels 5
Recipients per escalated level 1 Recipient type can be a user, group or PIN/carrier
MCRs per message 10
Log File size 512 KB
Page 74 Software Product Specifications 866030-90015 Document Release CWARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Computer Specifications Version 11.00 Command Messenger
Command Messenger The Command Messenger specifications are described in the following sections:
• Command Messenger Software Operating Environment on page 75
• Additional Notes for the Command Messenger Specifications on page 75
• Command Messenger Features and Limits on page 76
Command Messenger Software Operating Environment
Table 23 lists the Command Messenger software operating environment requirements.
Additional Notes for the Command Messenger Specifications
Microsoft Windows operating system may have higher system requirements than listed. If so, use the minimum system requirements published by Microsoft.
Table 23: Command Messenger Software Operating Environment
Command Messenger Software Operating Environment
Software Recommended Mandatory Validated
• 32-bit version Windows XP Professional SP2 or SP332-bit version Windows Server 2003 no SP, SP1, or SP2• 32-bit version Windows 2003 R2 no SP or SP2 Standard and Enterprise editions• Windows Vista SP1 or SP2 Business and Ultimate editions• 32-bit or 64-bit version Windows 7 Professional, Enterprise and Ultimate editions• 64-bit version Windows Server 2008 R2 no SP or SP1 Standard, Enterprise, and Datacenter editions
• 32-bit version Windows XP Professional SP2 or SP3
• 32-bit version Windows Server 2003 no SP, SP1, or SP2
• 32-bit version Windows 2003 R2 no SP or SP2 Standard and Enterprise editions
• Windows Vista SP1 or SP2 Business and Ultimate editions
• 32-bit or 64-bit version Windows 7 Professional, Enterprise and Ultimate editions
• 64-bit version Windows Server 2008 R2 no SP or SP1 Standard, Enterprise, and Datacenter editions
Yes
Note: The operating system must be English language.
Microsoft Windows Installer 4.5 or later Yes Yes
TCP/IP (IPv4) Yes Yes
866030-90015 Document Release C Software Product Specifications Page 75 WARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Orchestrator Computer Specifications Version 11.00
Command Messenger Features and Limits
Table 24 lists the Command Messenger features and feature limits.
OrchestratorThe Orchestrator specifications are described in the following sections:
• Orchestrator Software Operating Environment on page 76
• Additional Notes for the Orchestrator Specifications on page 776
Orchestrator Software Operating Environment
Table 25 lists the Orchestrator Client Desktop Version software operating environment requirements.
Table 24: Command Messenger Features, Feature Limits, and Notes
Feature Limit Notes
Recipients per message 1 Recipient type can be a user, group or PIN/carrier.
Staff Assignment escalation levels 3
Escalation levels 5
Recipients per escalated level 1 Recipient type can be a user, group or PIN/carrier.
MCRs per message 10
Table 25: Orchestrator Software Operating Environment
Orchestrator Software Operating Environment
Software Recommended Mandatory Validated
• 32-bit version Windows XP Professional SP2 or SP332-bit version Windows Server 2003 no SP, SP1, or SP2• 32-bit version Windows 2003 R2 no SP or SP2 Standard and Enterprise editions• Windows Vista SP1 or SP2 Business and Ultimate editions• 32-bit or 64-bit version Windows 7 Professional, Enterprise and Ultimate editions• 64-bit version Windows Server 2008 R2 no SP or SP1 Standard, Enterprise, and Datacenter editions
• 32-bit version Windows XP Professional SP2 or SP3
• 32-bit or 64-bit version Windows 7 Professional, Enterprise, or Ultimate edition
Yes
Note: The operating system must be English language.
Microsoft Windows Installer 4.5 or later Yes Yes
Microsoft XML Parser (MSXML) Version 6 SP1 Yes
TCP/IP (IPv4) Yes Yes
Page 76 Software Product Specifications 866030-90015 Document Release CWARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Computer Specifications Version 11.00 Whiteboard
Additional Notes for the Orchestrator Specifications
Microsoft Windows operating system may have higher system requirements than listed. If so, use the minimum system requirements published by Microsoft.
WhiteboardThe Whiteboard specifications are described in the following sections:
Whiteboard Software Operating Environment on page 77
Additional Notes for the Whiteboard Specifications on page 77
Whiteboard Software Operating Environment
Table 26 lists the Whiteboard software operating environment requirements.
Additional Notes for the Whiteboard Specifications
Microsoft Windows operating system may have higher system requirements than listed in Table 26. If so, use the minimum system requirements published by Microsoft.
Table 26: Whiteboard Software Operating Environment
Whiteboard Software Operating Environment
Software Recommended Mandatory Validated
• 32-bit version Windows XP Professional SP2 or SP332-bit version Windows Server 2003 no SP, SP1, or SP2• 32-bit version Windows 2003 R2 no SP or SP2 Standard and Enterprise editions• Windows Vista SP1 or SP2 Business and Ultimate editions• 32-bit or 64-bit version Windows 7 Professional, Enterprise and Ultimate editions• 64-bit version Windows Server 2008 R2 no SP or SP1 Standard, Enterprise, and Datacenter editions
• 32-bit version Windows XP Professional SP2 or SP3
• 32-bit or 64-bit version Windows 7 Professional, Enterprise, or Ultimate edition
Yes
Note: The operating system must be English language.
Microsoft Windows Installer 4.5 or later Yes Yes
TCP/IP (IPv4) Yes Yes
866030-90015 Document Release C Software Product Specifications Page 77 WARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Messenger Computer Specifications Version 11.00
MessengerThe Messenger specifications are described in the following sections:
Messenger Software Operating Environment on page 78
Additional Notes for the Messenger Specifications on page 78
Messenger Features and Limits on page 79
Messenger Software Operating Environment
Table 27 lists the Philips Event Messenger software operating environment requirements.
Additional Notes for the Messenger Specifications
The following list contains additional information about the Messenger specifications.
• Under Desktop Mode, serial COM ports for Paging Terminal or TAPI compliant modem are required.
• Microsoft Windows operating system may have higher system requirements than listed. If so, use the minimum system requirements published by Microsoft.
Table 27: Messenger Software Operating Environment
Messenger Software Operating Environment
Software Recommended Mandatory Validated
• 32-bit version Windows XP Professional SP2 or SP332-bit version Windows Server 2003 no SP, SP1, or SP2• 32-bit version Windows 2003 R2 no SP or SP2 Standard and Enterprise editions• Windows Vista SP1 or SP2 Business and Ultimate editions• 32-bit or 64-bit version Windows 7 Professional, Enterprise and Ultimate editions• 64-bit version Windows Server 2008 R2 no SP or SP1 Standard, Enterprise, and Datacenter editions
• 32-bit version Windows XP Professional SP2 or SP3
• 32-bit or 64-bit version Windows 7 Professional, Enterprise, or Ultimate edition
Yes
Note: The operating system must be English language.
Microsoft Windows Installer 4.5 or later Yes Yes
TCP/IP (IPv4) Yes Yes
Page 78 Software Product Specifications 866030-90015 Document Release CWARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Computer Specifications Version 11.00 Messenger
Messenger Features and Limits
Table 28 lists the Messenger features and feature limits.
Table 29 lists the Event Messenger Desktop Mode features and feature limits.
Table 28: Messenger Features, Feature Limits, and Notes
Feature Limit Notes
PAB total size No limit Resource considerations apply
PAB users 25
PAB groups 10
PAB group members 25
PAB server users No limit Resource considerations apply
Recipients per message 500
Escalation levels 5
MCR lists No limit Resource considerations apply
MCRs per list 10
Change password Yes
Edit devices Yes
Table 29: Messenger Desktop Mode Features, Feature Limits, and Notes
Feature Limit Notes
PAB total size No limit Resource considerations apply
PAB users No limit Resource considerations apply
PAB groups No limit Resource considerations apply
PAB group members 10
PAB server users No limit Resource considerations apply
Recipients per message 500
Escalation levels 5
MCR lists No limit Resource considerations apply
MCRs per list 10
Change password Yes
Edit devices Yes
866030-90015 Document Release C Software Product Specifications Page 79 WARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Alarm Messenger Computer Specifications Version 11.00
Alarm Messenger The Alarm Messenger specifications are described in the following sections:
Alarm Messenger Software Operating Environment on page 80
Additional Notes for the Alarm Messenger Specifications on page 80
Alarm Messenger Features and Limits on page 81
Alarm Messenger Software Operating Environment
Table 30 lists the Alarm Messenger software operating environment requirements.
Additional Notes for the Alarm Messenger Specifications
Microsoft Windows operating system may have higher system requirements than listed. If so, use the minimum system requirements published by Microsoft.
Table 30: Alarm Messenger Software Operating Environment
Alarm Messenger Software Operating Environment
Software Recommended Mandatory Validated
64-bit Microsoft Windows Server 2008 R2 SP1 Standard, Enterprise, and Datacenter versions. The operating system must be English language.
Yes Yes Yes
Microsoft Windows Installer 4.5 or later Yes Yes
Microsoft Windows SQL 2008 SP3, or SQL Server 2008 R2 SP1 (service pack is required) Standard, Enterprise (recommended), or Datacenter editions.
Yes Yes
Note: If Alarm Messenger SQL is co-installed with Alarm Messenger then a 64-bit version of SQL is required. If Alarm Message SQL is not co-installed with Alarm Message then either a 32-bit or 64-bit version of SQL is supported.
Microsoft MDAC Version 6.1 or later Yes
Microsoft XML Parser (MSXML) Version 6 SP1 Yes Yes
TCP/IP (IPv4) - non clustered and clustered environments
TCP/IP (IPv6) - clustered environment
Yes Yes
Page 80 Software Product Specifications 866030-90015 Document Release CWARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Computer Specifications Version 11.00 Alarm Messenger
Alarm Messenger Features and Limits
Table 31 lists the Alarm Messenger features and feature limits.
Table 31: Alarm Messenger Features, Feature Limits, and Notes
Feature Limit Notes
Instances 16 Based on Authorization Code. The EIS supports up to 16 instances of Alarm Messenger, however, each Alarm Messenger must reside on its own machine.
RS-232 ports 100 Maximum total ports. This limit is based on the number of available PCI/PCI-X slots using 8 port cards.
RS-232 maximum baud rate 9600
OPC ports 0 Obsolete
TCP/IP ports 100 Maximum total ports
Total ports monitored at once 8
Port Log size 50 MB
Port timeout (RS-232) 3 seconds
TCP/IP connection timeout 2 seconds – 5 minutes Inactivity timeout
Connections per TCP/IP port 32
Alerts (RS-232) 2500
Alerts (TCP/IP) 2500
Messages per alert 20
Recipients per message 25
Staff Assignment escalation levels 3
Escalation levels 5
Recipients per escalated level 25
Keys per alert 50
Keys 2500
Time shifts 20
Input monitor size 500 entries
Input length (RS-232) 65535 bytes Final message content is limited by Philips Event Integration Service length setting or output device, whichever is lower.
866030-90015 Document Release C Software Product Specifications Page 81 WARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Philips Event Notification Exporter Computer Specifications Version 11.00
Philips Event Notification ExporterTable 32 lists the software operating environment requirements for the Philips Event Notification Exporter (ENE).
Input length (TCP/IP) 65535 bytes Final message content is limited by Philips Event Integration Service length setting or output device, whichever is lower.
Activity Log size 5 MB
Rules Log size 5 MB
Custom message length 16369 bytes
Canned message length 16369 bytes
Data queue size 25000 entries
Duplicate filtering 5 seconds – 90 minutes
Filtering Log size 50 MB
Burst filtering alert range 5 seconds – 90 minutes
Character filtering 0X00 – 0XFF All can be filtered at once
PIN Prefix (maximum length) 16 characters
Field extraction 1 – 100 characters
Field extract delimiter 16 characters
Maximum repeated segment allowed for field extraction
50
Table 32: Philips Event Notification Exporter Software Operating Environment
Philips Event Notification Exporter Software Operating Environment
Software Recommended Mandatory Validated
64-bit Microsoft Windows Server 2008 R2 SP1 Standard, Enterprise, and Datacenter versions. The operating system must be English language.
Yes Yes
Microsoft .NET Framework 3.5 Yes
Microsoft IIS 6.0 or higher Yes
Table 31: Alarm Messenger Features, Feature Limits, and Notes (Continued)
Feature Limit Notes
Page 82 Software Product Specifications 866030-90015 Document Release CWARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Computer Specifications Version 11.00 Philips SOAP SDK
Philips SOAP SDKTable 33 lists the software operating environment requirements for the Philips SOAP SDK.
Note: SOAP must reside on the same system as the adapter (Alarm Messenger) and SOAP is limited to the one port.
Philips Event Syndication ServiceTable 34 lists the software operating environment requirements for the Philips Event Syndication Service (ESS).
Note: ESS must reside on the same system as the SOAP SDK.
Philips Socket SDKPhilips Socket SDK must be installed on the same system as the Alarm Messenger.
Table 35 lists the software operating environment requirements for the Philips Socket SDK.
Table 33: Philips SOAP SDK Software Operating Environment
Philips SOAP SDK Software Operating Environment
Software Recommended Mandatory Validated
64-bit Microsoft Windows Server 2008 R2 SP1 Standard, Enterprise, and Datacenter versions. The operating system must be English language.
Yes Yes
Microsoft .NET 3.5 Yes Yes
Microsoft IIS 7.5 Yes Yes
Table 34: Event Syndication Service Software Operating Environment
Event Syndication Service Software Operating Environment
Software Recommended Mandatory Validated
64-bit Microsoft Windows Server 2008 R2 SP1 Standard, Enterprise, and Datacenter versions. The operating system must be English language.
Yes Yes
Microsoft .NET 3.5 Yes Yes
Microsoft IIS 7.5 Yes Yes
Table 35: Philips Socket SDK Software Operating Environment
Philips Socket SDK Software Operating Environment
Software Recommended Mandatory Validated
64-bit Microsoft Windows Server 2008 R2 SP1 Standard, Enterprise, and Datacenter versions. The operating system must be English language.
Yes Yes
Microsoft .NET 3.5 Yes Yes
866030-90015 Document Release C Software Product Specifications Page 83 WARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Unified Counters Viewer Computer Specifications Version 11.00
Unified Counters ViewerUnified Counters Viewer must be installed on the same system as the SOAP SDK.
Table 36 lists the software operating environment requirements for the Unified Counters Viewer.
Philips Historical DatabaseThe Philips Historical Database (HDB) Software Operating Environment specifications are described in Table 37
Table 36: Unified Counters Viewer Software Operating Environment
United Counters Viewer Software Operating Environment
Software Recommended Mandatory Validated
64-bit Microsoft Windows Server 2008 R2 SP1 Standard, Enterprise, and Datacenter versions. The operating system must be English language.
Yes Yes
Microsoft .NET 3.5 Yes Yes
Table 37: Historical Database Software Operating Environment
Historical Database Software Operating Environment
Software Recommended Mandatory Validated
Microsoft .NET 3.5 Yes Yes
Microsoft XML Parser (MSXML) Version 6 SP1 Yes Yes
TCP/IP (IPv4) Yes Yes
Microsoft Windows SQL 2008 SP3, or SQL Server 2008 R2 SP1 (service pack is required) Standard, Enterprise (recommended), or Datacenter editions.
Yes Yes
Microsoft IIS 7.5 Yes Yes
HDB only requires Microsoft SQL Server 2008 SP3 or SQL Server 2008 R2 SP1 (Standard or Enterprise). It does not require, but, optionally, you may want to install SQL Server 2008 Reporting Services.
Note: Either a 32-bit or 64-bit of SQL is supported.
Page 84 Software Product Specifications 866030-90015 Document Release CWARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Computer Specifications Version 11.00 Historical Database Reporting
Historical Database ReportingThe HDB reporting package leverages Microsoft Reporting Services, to produce individual reports to display required data.This functionality includes:
• built-in security capability that can be configured at the Reporting Server and Active Directory levels
• built-in exporting capability (to .pdf and .xls) and built-in printing capability
• built-in charting capability
• built-in parameter creation
Software prerequisites• Microsoft SQL Server 2008 Reporting Services, if Reports are installed.
• Microsoft SQL Server 2008 Browser
• Microsoft SQL Server 2008 SQL Agent
• NET Framework 4.0 full profile
HDB Reporting Service
Table 38 lists the requirements for the HDB Reporting Software Operating Environment.
HDB Reporting Client/Browser
Refer to Table 14 on page 65 for a complete list of client roles and requirements.
Table 38: HDB Reporting Service Software Operating Environment
HDB Reporting Software Operating Environment
Software Recommended Mandatory Validated
Microsoft Windows Installer 4.5 or later Yes Yes
TCP/IP (IPv4) Yes Yes
Microsoft SQL Server 2008 SP3 or SQL Server 2008 R2 SP1, Reporting Services, Standard, Data Center, or Enterprise edition (Recommended).
Yes Yes
Microsoft® Windows Server® 2008 R2 SP1, 64-bit version Enterprise edition. The operating system must be English language.
Yes Yes Yes
Note: HDB Reports by end device is optimized for use with Microsoft Internet Explorer 9. Use of earlier versions may result in non-optimal display.
Table 39: Historical Database Software Operating Environment
Historical Database Client/Browser Software Operating Environment
Software Recommended Mandatory Validated
Microsoft Internet Explorer 9 in standard mode Yes Yes Yes
Note: HDB Reports by end device is optimized for use with Microsoft Internet Explorer 9. Use of earlier versions may result in non-optimal display.
866030-90015 Document Release C Software Product Specifications Page 85 WARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Personal Assignments Computer Specifications Version 11.00
Personal AssignmentsThe Personal Assignments GUI is a web-based application requiring IIS v7.0 or later. The GUI is accessed by the URL provided at installation. The application uses IIS functionality as necessary, including SSL over HTTPS and logging.
As a Web-based application IIS 7.5 with specific roles and features must be installed and configured. Refer to Table 14 on page 65 for a complete list of IIS requirements.
Personal Assignments Features and Limits
Personal Assignments provide the follow key features:
• Web-based application, accessible to mobile devices
• Users may perform their own assignment and duty status changes from a mobile device
• This is a supplement, not a replacement, for the Orchestrator client
• Compatibility with 10.0 and 11.0 installations
Note: Installed on an IIS server.
Personal Assignments Server
Personal Assignments is installed on its own IIS server or installed on another web server with adequate capacity. Network connectivity to the Event Integration Service. Refer to Philips Event Integration Service on page 67 for software specifications and to Chapter 3 Hardware Product Specifications on page 37 for hardware specifications. Refer to Table 14 on page 65 for a complete list of IIS requirements.
The Personal Assignments Client specifications are described in the following sections:
Personal Assignments Devices
Personal Assignments are qualified by operating system (with native browser) and clinical usability review. Contact your Philips representative for the currently qualified devices.
Table 40: Personal Assignments Software Operating Environment
Personal Assignments Software Operating Environment
Software Recommended Mandatory Validated
Microsoft IIS 7.5 Yes Yes
Microsoft .NET 3.5 Yes Yes
64-bit Microsoft Windows Server 2008 R2 SP1 Standard, Enterprise, and Datacenter versions. The operating system must be English language.
Yes Yes
TCP/IP (IPv4) Yes Yes
Page 86 Software Product Specifications 866030-90015 Document Release CWARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Contact InformationVisit the Philips Web site (www.philips.com/IntelliSpaceEventManagement) for product information, technical support, or to provide your comments about Philips products.
Contact the following groups directly for specific information or assistance.
Sales Information
E-mail address: [email protected] number: 1-561-361-6991Telephone number: 1-866-363-7446
Technical Support for Products and Solutions
E-mail address: [email protected] Number: 1-561-886-3181 Telephone number: 1-800-722-9377 (Option 2, then Option 3)
Reader’s Comments
Send comments about this document to [email protected]. Helpful comments include feedback on the overall usefulness of this document; possible additions, deletions, and clarifications; or specific errors and omissions. Include the following information in your note:
• Document title• Document number and document version• Software version• Page number and comment
Your comments will be forwarded to a developer for review and action, if deemed appropriate. You understand that Philips may use or distribute whatever information you supply in any way it believes appropriate without incurring any obligation to you.
WARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Philips 3000 Minuteman Rd.Andover, MA 01810
United States of America1-866-363-74461-561-361-6990
www.philips.com/IntelliSpaceEventManagement
WARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL, WITHOUT PERMISSION, IS A VIOLATION OF LAW.