CENTRE ICCS CONTROL ROOM SOLUTION

(1)

CENTRE ICCS CONTROL ROOM SOLUTION

(2)



Page: 2

More than 65 years of innovation & expertise in mission

critical applications

We develop and market high reliable communication and information systems for mission critical applications in the fields of Air Traffic Management and Public Safety & Transport.

Worldwide Control Centres develop towards the same standards.

ATM

Air Traffic Management

PST

Public Safety & Transport

ATM Civil

(3)



FREQUENTIS and Nødnett

All Agencies Ph0+Ph1 fully live!



FREQUENTIS Norway AS



From 1

st

April 2014



Oslo based office



Nødnett focussed



Approx. 325 Control Rooms (ICCS

3020)



Police – Touch GUI



Fire – Touch GUI, Vision C&C



Health - MAK GUI & Resource

Management

(4)



Page: 4

Pasienten ringer 113, har vondt i brystet. Opprinnelses-markering sendes automatisk til AMK. AMK registrer henvendelsen i AMK OHS (AMK OHS har oppslag i sykehus EPJ for folkeregister opplysninger). Varsler alle ressurser (Ambulanse, legevakt lege mv) over Helseradio/AMK GVB. Amb og lege mottar opplysninger om oppdraget over Amb og lege GBV. Ambulanse registrerer fortløpende i elektronisk ambu-lansejournal Lege dokumenterer i Lege EPJ. EKG avdeling mottar EKG fra ambulanse (overføres via mobildata). EKG blir forelagt vakthavende kardiolog for vurdering. EKG opplysninger oppdateres automatisk i Sykehus EPJ. Ambulanse gir medisinsk tilbakemelding om pasient til AMK og akuttmottak via over helseradio. Lege oppdaterer dokumentasjon i Lege EPJ som oppdaterer automatisk kjernejournal basert på pasientens tidligere avklarte samtykke. AMK registrerer data i AMK OHS. AMK melder disse data til akutt mottak over telefon. Kjernejournal oppdateres med ”AMK og ambulanse data”. Mottar pasient, alle relevante opplysninger er overført fra AMK OHS til sykehusets EPJ. Relevante opplysninger oppdateres i kjernejournal etter pasienten er ferdigbehandlet. Kommunikasjonsvei AMK Sykehus LV-sentral Lege i vakt Sykehus EPJ

Scenario 9 Scenario år 2010, pasient har kjernejournal med avtale om deling av opplysninger Alle systemer kan importere data fra kjernejournal.

Lege journal kan importere data fra AMK OHS via AMK GBV _{©KoKom 2008}

Ambulanse

Pasient AMK AMB/Lege EKG avdeling AMB AMK Akuttmottak

Oppr. markering

EKG

LV EPJ

Sykehus EPJ Sykehus EPJ

Kjernejournal Kjernejournal Kjernejournal Kjernejournal Kjernejournal Kjernejournal Kjernejournal Amb. journal

Lege journal Lege journal Amb. journal Amb GBV Lege GBV Amb GBV AMK OHS AMK GBV

AMK OHS AMK GBV

4

(5)



Background – Health AED/GPoC Evolution

2009: “Compact Gate-X” solution for AED and GPoC

• Connected via air interface to TETRA network

• Limited TETRA voice services, shared data services • Considers space constraints in technical room

Operational Experience from Phase 0: Need to…

• Minimize space requirements for AED and GPoC sites further • Remove TETRA functionality limitations

• More flexibility to support geographical Health business distribution

2013: Adaption to “Centre-ICCS” Solution

• Addressing refined Health needs

• Deployed for Health from Phase 2 onwards

(6)



Page: 6

Nødnett Centre-ICCS Features at a Glance

Geographical

Disentanglement

• Central system and actual operator working positions can be fully geographically separated

Central Core

System

• Full availability of TETRA voice and data services • Shared use of hardware, interfaces and services • Central management

Remote Working

Positions

• Minimized hardware and installation requirements

• Either Touch or MAK GUI supported • Connected via IP to central system – extended distance

Control Room

Virtualization

• Discretionary grouping of working positions to several “logical units” constituting a virtual Control Room • Unchanged ICCS user experience!

(7)

(8)



Page: 8

General Benefits



Control Room operators, supporting staff and system itself can reside

at different locations



Working positions at different physical locations can be grouped into

one «virtual» Control Room



Operator personnel can assist at any virtual Control Room on demand

- without changing location



Task or event based grouping of working positions in order to separate

communication (work-)flows on ICCS



Centralized technical support and maintenance service will reduce

operation costs and lead to higher support quality



System can be hosted in existing data centre / shared central system

– reduced costs per (virtual) control room site



Remote work position equipment fits in typical office environments –

no technical room required

(9)



Considerations for Disparate Organizations



Centre-ICCS ideal to host multiple organizations with a

typically

lower

number of working positions – shared ICCS system



Solution ideal for organizations operating in similar business

environment or with existing business relation



Disparate organization do not require own solution support

environment but receive a service by hosting organization:

– shared central network and management services

– technical resources and system know-how

– hardware and software maintenance



Disparate organization and hosting organization («managed service

provider») would need to get into a service / support agreement



All remote working positions must use the same GUI type (Touch or

MAK)

(10)



Page: 10

ICCS Solution Portfolio in Comparison (1/3)

Compact Gate-X Centre-ICCS Standard-ICCS

Planned Agency Deployment

Police, Fire NA NA All

Health AED, GPoC phase

0 and phase 1

AED, GPoC phase 2-5

AMK all phases Connectivity and Interfaces

TETRA Air interface Line interface Line interface

Local telephone switch / PABX (Optional)

Locally connected Via leased line to

C-ICCS

Locally connected Local IT network

(Optional)

Locally connected Locally and/or via

C-ICCS connected

Locally connected E2E Voice Encryption

(Optional) Supported (requires hardware) Supported (requires hardware) * Supported (requires hardware)

* IP-PVN Encryption between C-ICCS and remote positions recommended. Customer specific solution.

(11)



ICCS Solution Portfolio in Comparison (2/3)

Compact Gate-X Centre-ICCS Standard-ICCS

Services

TETRA Voice Limited Full Full

TETRA Data Full (via associated

Standard ICCS) Full Full Resource Management (Health Option) via associated Standard ICCS via associated Standard ICCS Local

Management (PE) Per AED/GPOC Centrally for all

connected sites

Per AMK Scalability and Range

Distance WP-System Up to 100m Dependent on IT

network capability

Up to 100m

System Location Control Room site Any* - e.g. data

centre

(12)



Page: 12

ICCS Solution Portfolio in Comparison (3/3)

Compact Gate-X Centre-ICCS Standard-ICCS

Control Room Site Requirements

Technical room Operator room

Operator room Technical room

Operator room System Capacity With Resource Management Option Typically up to 4 working positions Up to ~100 nodes* Up to ~50 positions Up to ~100 nodes* Up to ~50 positions Service fall-back

On line interface outage NA Via Nødnett central

fixed telephony lines Via Nødnett central telephony lines and TETRA air interface On technical room outage (disaster)

none Connect to

fall-back C-ICCS

none

A node is a ICCS core switch connection e.g. working position or interface. Maximum number of working positions depends on the number of required interfaces and operational requirements.

(13)



Remote Working Position Setup

Position Equipment



1x slim client PC



1x Touch screen or 19”

TFT screen with Mouse

and Keyboard (“MAK”)



1x headset (USB) and 1x

loudspeaker pair (USB)



1x USB footswitch

Connectivity Equipment



2x IP Switch *



2x Transmission Modem *

Example: Connectivity deployment setup

(14)



Page: 14

Centre-ICCS Feature Roadmap

Less Footprint

• Less physical space of centre position

Statistics &

Reporting

• Reports per virtual Control Room

“Transfer of

Operation”

• All operational communication and controls can be transferred between virtual Control Rooms

(15)



Possible Future Solution Scenarios



Support of mobile Devices

– Mobile working positions

– Notebooks

– Tablets

– Smartphones

– …

These scenarios require further dialog with you to

specify needs and specific solution design!



System Interconnectivity

– Connecting multiple C-ICCS systems

– Increased resilience

– Distributed system capacity

(16)



Page: 16

Summarized Centre-ICCS Benefits

Full geographical

deployment

Flexibility

Centralized

(“Managed”)

Services

Reduced Costs

per (virtual)

Control Room

(17)