Lios Admin

Siemens IT Solutionsand Services

the living company

s

07/04/23

LIOS 8.6 Administrator

1

LIOS V8.6

Administrator


the living company

s

07/04/23


2

LIOS administrator User administration NE administration EFD administration LEA administration


the living company

s

07/04/23


3

User administration

LIOS user roles: Operator External Operator Supervisor Administrator


the living company

s

07/04/23


4

LIOS operator Issuing, modifying and canceling observations (observation handling) Synchronization of LIOS and NE databases (observation management) LEA administration Alarm browser BMML console


the living company

s

07/04/23


5

LIOS supervisor Log browser Observation browser Ticket browser Alarm browser BMML console


the living company

s

07/04/23


6

LIOS administrator User administration NE and LIOS server administration EFD administration LEA administration Alarm browser BMML console


the living company

s

07/04/23


7

LIOS administrator interface


the living company

s

07/04/23


8

The LIOS main page

Work area

Navigationmenu

Applicationcommands

bar

Header


the living company

s

07/04/23


9

LIOS user administration Managing

LIOS users and LIOS operator groups


the living company

s

07/04/23


10

Creating a LIOS operator (I) Select ‘New user’ from the

application commands Under ‘user role’ select ‘internal

operator’


the living company

s

07/04/23


11

Creating a LIOS operator (II)

Select the operator rights for this operator

LEA administration: operator can administer LEAs

MML handling: operator can use BMML console

Observation handling: operator can create, modify and cancel observations

Observation Manager: operator can invoke DB synchronisation

Select operator group


the living company

s

07/04/23


12

Creating a LIOS administrator


the living company

s

07/04/23


13

Creating a LIOS supervisor


the living company

s

07/04/23


14

Operator groups Every operator has to belong to one or more operator groups. Apart from global alarms, an operator receives only alarms that concern his

group(s). An operator can only see the observations of operators of his group(s).


the living company

s

07/04/23


15

Select items from the ‘available operator groups’ list on the left and press the ‘>’ button. The items are shifted to the ‘selected operator groups’ list.

To shift all items press the ‘>>’ button.

Creating operator groups

the living company

S

Titel der PräsentationSiemens IT Solutionsand Services

07/04/23


16

Host Administration


the living company

s

07/04/23


17

Communication database in LIOS and on the NE IP configuration has to be performed both in the LIOS system and on the

NE (e.g. EWSD, S12, SR9, KCC, HUAWEI, . . .). For IP configuration in the LIOS system use Host Admininstration/NEs. The corresponding entries in the communicaton database of the NE are not

administered in the LIOS system. They have to be entered by an NE administrator on the NE.

the living company

S


07/04/23


18

LIOS-specific configuration of EWSD switches


the living company

s

07/04/23


19

/****************************************************************** /* * /* Administration of Exchange ID and USERIDs * /* * /****************************************************************** /* <ENTREXCHID:NAME=T8000,NSYT=0&2,IDNO=T8000; /* <CRUSERID:USERID=MFKONTES,AUT=1; *MFKON-0 *MFKON-0 <CRUSERID:USERID=DBPLIM12,AUT=1; *SYSTEM-2 *SYSTEM-2

Administration of Exchange ID and User IDs


the living company

s

07/04/23


20

/****************************************************************** /* * /* MMLCM Local (on CP) * /* * /****************************************************************** /* /* Local ipadr for efdad, mmlcm, efdli and fta /* <CRIPADR:ADRNAM=IPAOWN; already configured /* /* Local application for observation administration /* <CRAPPL:APPLID=MMLCM,PRONAM="T8000",ADRNAM=IPAOWN,TSEL= #005B,SSEL=000B,PSEL=000B,AET=0&2&262&1&1&8000&91; /* /****************************************************************** /* UserID for FTP on MP * /****************************************************************** /* CRFTINI:User identity="FELKEL",Password type=Simple PW, Password=********,Verify password=********,Ft type={ FTP }; /*

Local entries for LIOS: MMLCM / FTP Local IP address MMLCM application: for observation

handling and MML communication

For Powernode switches connected via IP FTP is used for file transfer. This is needed for Ticketbuffer management and exchanging security keys for EWSD <V17. Therefore only a User ID on the MP is necessary.


the living company

s

07/04/23


21

/****************************************************************** /* * /* Remote entries for LIOS * /* * /****************************************************************** /* /* Remote processors for LIOS (TS1 and TS2) <CRPRO:PRONAM="LIOS1",PROTYP=OSS,SYT=0&2&262&1&1&3001; <CRPRO:PRONAM="LIOS2",PROTYP=OSS,SYT=0&2&262&1&1&3002; /* <CRIPADR:ADRNAM=IPALIOS1,IPADR=10-119-146-85; <CRIPADR:ADRNAM=IPALIOS2,IPADR=10-119-146-86; /* /* Remote applications for observation administration (MMLCM) /* <CRAPPL:APPLID=MMLCM,PRONAM="LIOS1",ADRNAM=IPALIOS1,AUT=1, #TSEL=005B,SSEL=000B,PSEL=000B,AET=0&2&262&1&1&3001&91; <CRAPPL:APPLID=MMLCM,PRONAM="LIOS2",ADRNAM= IPALIOS2,AUT=1, #TSEL=005B,SSEL=000B,PSEL=000B,AET=0&2&262&1&1&3002&91; /*

Remote entries for LIOS: MMLCM Remote processor names for

LIOS servers Remote entries for MMLCM.

These entries are the values for the LIOS servers.


the living company

s

07/04/23


22

NET.CONFIG - Used for EFD and LID Admin

/******************************************************* /***** EFD Administration ***** /******************************************************* / LOSIADR: APT=0-2-262-1-1-8004-2020, PSEL=2020, SSEL=2020, TSEL=2020, # AC =2-9-0-0-2; ROSIADR: APT=0-2-262-1-1-2001-2020, PSEL=2020, SSEL=2020, TSEL=2020, # PORT =102, # IPADR=172-30-1-25; / /******************************************************* /***** LID Administration ***** /******************************************************* / LOSIADR: APT=0-2-262-1-1-8004-1010, PSEL=1010, SSEL=1010, TSEL=1010, # AC =2-9-0-0-2; ROSIADR: APT=0-2-262-1-1-2001-1010, PSEL=1010, SSEL=1010, TSEL=1010, # PORT =102, # IPADR=172-30-1-25; /

EFDAD application: for EFD administration

EFDLI application: for sending LI tickets and LI alarms from EWSD to LIOS


the living company

s

07/04/23


23

Host Administration The Host Administration is used for administering the IP and OSI

configuration data for the communication between NE (= EWSD, S12, SR9, ...) and LIOS server.

The corresponding entries in the IP database of the NE are not administered by a LIOS administrator. They have to be entered by an NE administrator.

The Host Administration contains data forLIOS serversall NEs connected to LIOSglobal LIOS configuration


the living company

s

07/04/23


24

Host Administration – NEs

the living company

S


07/04/23


25

Administering an EWSD switch (example)


the living company

s

07/04/23


26

Host Administration – General data EWSD (I) Provider. Abbreviated name of the

network provider; length: normally two characters

NE name. Name of the NE (has to be identical with the NE name used on the NE itself, specified by the ENTREXCHID command)

Long NE name. Any name which specifies the NE, e.g. name of location

NE type. Siemens fixed, Siemens mobile or Alcatel fixed

NE version. Software version of the switch (e.g. EWSD V15)

Time zone. If the time zone of the NE and LIOS differ, enter here the time zone of the NE.


the living company

s

07/04/23


27

Host Administration – General data EWSD (II) Values used for the ETSI HI2 and HI3 interfaces

Operator ID is used in HI2 and HI3

The NE ID can be entered in four different formats: E.164, X25, IP, DNS(this is only for HI2).


the living company

s

07/04/23


28

Host Administration – LI NE passwords (I) LI group command password. The LI

group command password is needed for controlling most LI functions on the NE (creating/modifying LEAs and observations). To be able to specify or modify the LI group command password, you must know the LI ID password.

LI ID password. It is needed for specifying or modifying the LI group command password and the audit password. The LI ID password replaces the hard-coded LI password. The LI ID password protects the EWSD command ‘MOD OBSID’.

LI audit password. It is needed for invoking LI audit functions (e.g. DISP LIMEAS). To be able to specify or modify the audit password, you must know the LI ID password.


the living company

s

07/04/23


29

Host Administration – Optional features (I) Realized as powernode. Optional.

If the switch is a powernode and replay-protect password is used for EFD administration and FT, then this must be ticked.

CUG indexing activated. Optional.If selected the CUG of the LEA can be addressed through a CUG index (this can only be used if on the EWSD the LEA is a member of a CUG, CUG indexing is administered, the responding flag is set in the LI option and in the LIOS LEA administration the corresponding indices have been defined).

NE directory number. Optional. Virtual directory number of the switch, which is displayed (CLIP) on the LEA equipment when the call to the LEA is established.

Ticket buffer management activated. Optional. If this feature is activated on the NE (EWSD stores tickets in a buffer after 24 hours of ticket transfer failure). LIOS retrieves tickets from this buffer automatically.

NE identification number. Optional. Freely chosen unique number for EWSD; included in tickets.

ETSI V2 allowed. Only for EWSD V17 / hiE9200 V3. Selection of the ETSI_V2 signaling schemes is allowed. The corresponding LI property must be set on the NE.

TR TKUE 40 active. Only for EWSD V17 / hiE9200 V3. The NE uses the German variant of ETSI_V2. If you select this check box, also ‘ETSI V2 signaling’ must be selected. The corresponding LI property must be set on the NE.


the living company

s

07/04/23


30

Host Administration – Transport system

For TCPI/IP: Enter IP Adress


the living company

s

07/04/23


31

Host Administration – adding an application

To set up an application for this NE press ‘New’.


the living company

s

07/04/23


32

Host Administration – Administering MMLCM for EWSD (I)

Application. Here MMLCM is being set up.

Primary LIOS server. Here you specify which LIOS server should send MML commands to the NE; the other LIOS server will work as a backup.

Port number. Specify which port of the Symicron card is used.


the living company

s

07/04/23


33

Host Administration – Administering MMLCM for EWSD (II)

Transport, Session, Presentation selector. Enter the selectors which are administered on the X.25/IP database on the NE

System title, APQ. Enter the corresponding values administered in the X.25/IP database on the NE

AEQ. If administered on the EWSD enter the appropriate values. (So far in no configuration has AEQ been administered.)


the living company

s

07/04/23


34

Host Administration – MMLCM authorization Enter the NE user ID(s) which

you want to use for MMLCM. The NE user ID(s) have to be

configured on the NE by the NE administrator.

For each operator group an NE user ID has to be assigned.

For LIOS-internal use, there has to be assigned an NE user ID to the group ‘none’ as well.


the living company

s

07/04/23


35

Host Administration – MMLCM authorizationEntering NE user ID(s) and passwords Replay-protected password

enabled. If selected, the password is encrypted to prevent replay. For the encryption, time information is used. ‘Replay-protected password’ only works if the time in the LIOS system and on the NE is precisely the same – this means synchronization through a radio clock or an NTP (Network Time Protocol) server is necessary. Only for EWSD V15 and higher and for hiQ V4 and higher.


the living company

s

07/04/23


36

Host Administration – MMLCM authorization Cyclic password change

enabled. If selected, LIOS handles the problem of expiring passwords. You have to enter an initial passwords and at least three more passwords. When LIOS receives a ‘password expired’ answer when accessing the NE, it automatically replaces the password with the next password in the list; when it has arrived at the last password in the list, it starts again with the first one (leaving out the initial password).


the living company

s

07/04/23


37

Host Administration – MMLCM authorization Here you relate LIOS

operator groups to the NE user IDs.

Press ‘New’. Select an operator

group and relate it to an NE user ID.

Do this for all LIOS groups and the internal LIOS group ‘none’.

You can use the same NE user ID for all groups or different NE user IDs.


the living company

s

07/04/23


38

Host Administration – EFD application for EWSD (I) The EFD application is

used for creating EFDs (= event-forwarding discriminators) on the EWSD through the LIOS EFD Administration.

Port number. Select which port of the Symicron card is used.


the living company

s

07/04/23


39

Host Administration – EFD application for EWSD (II)

Transport, Session, Presentation selector. Enter the selectors which are administered on the IP database on the NE.

System title, APQ. Enter the corresponding values administered in the IP database on the NE.

AEQ. If administered on the EWSD, enter the appropriate value. (So far in no configuration has AEQ been administered.)


the living company

s

07/04/23


40

Host Administration – Entering password

EFD NE password. Enter here the password for the NE user ID MFKONTES (or MFKON).This NE user ID has to be created on the NE by the NE administrator. The EFD Administration uses this NE user ID when connecting to EWSD.

Replay-protected password enabled . If selected, the password is encrypted to prevent replay. For the encryption, time information is used. ‘Replay-protected password’ only works if the time in the LIOS system and on the NE is precisely the same – this means synchronization through a radio clock or an NTP (Network Time Protocol) server is necessary. Only for EWSD V15 and higher and for hiQ V4 and higher.


the living company

s

07/04/23


41

Host Administration – Administering LID application for EWSD

The LID application is used for the ticket transfer from NEs to LIOS servers.

Transport, Session, Presentation selectors. Enter the selectors which are administered on the IP database on the NE.

System title, APQ. Enter the corresponding values administered in the IP database on the NE.

AEQ. If administered on the EWSD, enter the appropriate value. (So far in no configuration has AEQ been administered.)


the living company

s

07/04/23


42

Host Administration – LIOS servers Only needed for EWSD, Siemens MSC, Hi9200 The LIOS server configuration is analogue to the NE

administration. For LIOS servers, the application MMLCM, LID and EFD have to be

administered.


the living company

s

07/04/23


43

Host Administration – NE activation

After NE und LIOS server data has been administered in the Host Administration and in the the communication database of the NE, the NE can be switched to active.

During activation of an EWSD, an MMLCM connection to the EWSD is made for the first time, LIOS detects the ports on the NE and subtracts their number of the LIOS license.


the living company

s

07/04/23


44

Host Administration – NE activated


the living company

s

07/04/23


45

EFD Administration EFD = event-forwarding discriminator Necessary for defining the destination to which

tickets and LI NE alarms should be sent.(In most configurations the destinations are both LIOS servers.)

With the EFD Administration you can manage EFDs on EWSD switches (not necessary for Alcatel S12 and Siemens Mobile).


the living company

s

07/04/23


46

EFD Administration


the living company

s

07/04/23


47

Creating an EFD (I) NE name. Name of target NE.

Discriminator ID. It identifies the EFD on the individual NE; it must be unique only on the NE.Accepted values: 0 and positive and negative 32-bit integers (value range -2^31+1 to 2^31-1).

State. Read-only field. The state of an EFD can be ‘OK’, ‘Not in DB’, ‘Not on NE’, ‘DB != NE’; ‘Error’, ‘Undefined’, ‘Ignored’ and ‘Processing’.

Remark. You can add a remark here. 150 characters max.

Last validation. Read-only field. Date of last validation (Details form only).

Creation date. Read-only field. Date of creation of EFD (Details form only).

Error report. Read-only field. If an EFD Administration operation has failed, partially or as a whole, an error report is generated. The error report always refers to the last operation.


the living company

s

07/04/23


48

Creating a new EFD (IIa) Active destination. Read-only field. Currently valid

primary address to which events are sent by the NE.

Destination. (Primary) Target address to which events are forwarded. Input format: decimal numbers separated by dots (e.g. 0.2.262.1.1.4800.32.1).

Backup destination. Fall-back target address for events in case the destination cannot be reached. Input format: decimal numbers separated by dots.

Tickets (checkbox). If selected, LI tickets (LI records) are/will be forwarded through the EFD.

NE alarms (checkbox). If selected, NE alarms (LI infos) are/will be forwarded through the EFD.

Object class. Read-only field. Object IDs generated by the switch for EFDs.

Name binding. Read-only field. EFD attribute.

Package list. Read-only field. EFD attribute.


the living company

s

07/04/23


49

Creating a new EFD (IIb) Confirmed mode. If activated, user requests

are confirmed by the NE after execution. ‘Confirmed mode’ should always be activated.

Administrative state. Read-only field. The EFD can be in the following administrative states:Unlocked: processing of the information by the discriminator is permitted by a managing system.Locked: processing of the information by the discriminator is prohibited by a managing system.Shutdown: the EFD is not operational owing to a shutdown of the NE.

Operational state. Read-only field. The EFD can be in the following operational states:Disabled: the discriminator is not operational.Enabled: the discriminator is operational


the living company

s

07/04/23


50

Checking EFDs (1) Validation can be

performed - for a single EFD, - for a set of EWSDs- for all EWSDs

Depending on the filter settings in the EFD administration also EFDs not used by LIOS will be displayed

(e.g. EFDs used by NetManager).


the living company

s

07/04/23


51

Checking EFD (2)

After validation: If the EFD is not on the EWSD but an LI EFD,

the state of this EFD will be set to ‘Not on NE’. If you want to set this EFD on the NE, just select action ‘Align’.

If the EFD is on the EWSD but not in the LIOS DB,the state is set to ‘Not in DB‘.If you want to take over this EFD into the LIOS DB,select ‘take over‘.

If the data of a specific EFD differs between the LIOS and the EWSD databases, the state of this EFD will be set to ‘ NE != DB’. If you want to set the data in LIOS DB according to EWSD select ‘Synchronize‘.

If the EFD is not on the EWSD and not a LI EFD,it will be automatically removed from LIOS.


the living company

s

07/04/23


52

EFD manipulations

100

LIOS

Validate EWSD 1100

EFD

OK

200 EWSD 2Not on NE

200

Take over

EWSD 3300

Align

Not in DB300

400 EWSD 4400DB!=NE

400Synchronize

Align

Validation result:EFD state

400


the living company

s

07/04/23


53

Setting up a new EWSD switch (I)

Make sure that the communication hardware is installed (e.g. wiring, Symicron card [X.25], X.25 modem, ISDN router, IP router).

Preparation of the hardware connection from the NE to the X.25, ISDN or IP network.

Preparation of the LI functionality on the NE (LI patches, LI LTG, LI options, Q3 activated, ODAGEN, . . .)

Preparation of the communication database on the switch (local and remote parameters).

Make sure that the local communication parameters of LIOS have been entered: Host Administration/LIOS servers: transport systems, transfer protocols, LIOS addresses (X.25, IP)

If ISDN is used, configure a new WAN partner in the ISDN router (Bintec).

LIOS EWSD


the living company

s

07/04/23


54

Setting up a new EWSD switch (II) Host Administration/NEs: set up a new

NE; enter the remote parameters for the communication with the switch.

LI passwords are set.

EFDs are created to make the switch divert LI tickets and alarms to LIOS.

The LI options are modified.

Activate the NE: In the LIOS Host Administration, NEs subapplication, select ‘Activate NEs’. Activate the new NE.

BMML console: connect to the NE and set the LI passwords on the NE: enter the passwords as parameters of the MODOBSID command.

Open the EFD Administration and create an EFD. (In case of inband create an EFD only for NE alarms.)

From the BMML console adapt the LI options of the EWSD with the MODLIOPT command.

LIOS EWSD


the living company

s

07/04/23


55

LEA and CUG administration

Administration of the link to the LEA = law enforcement agency The LEA receives the call content directly from the NE through ISDN. The LEA configuration data is sent to an NE when the first observation for

a LEA is created on the NE. LI tickets are sent from the NE to LIOS

and then forwarded to the LEA through FTAM or FTP.


the living company

s

07/04/23


56

LEA Administration


the living company

s

07/04/23


57

LEA Administration – general LEA data LEA name. Name of LEA. Phone. Phone number for

contacting the LEA in case of problems.

Address. Physical addressof LEA.

Remark. Optional field forremarks.

Default LEA. The default LEA will receive all tickets that cannot be assigned to any LEA (stray tickets).


the living company

s

07/04/23


58

LEA Administration – observation data Different settings have to be

made for different switches. Press Next to make the settings.


the living company

s

07/04/23


59

LEA Administration – observation data EWSD (1) LEA ID on NEs. Read-only

field. Number (generated by LIOS) by which a LEA is known to NEs.

DN OF LEA. Nationally significant directory number (LAC and DN) of the LEA for the transmission of the call content

DN of ticket connection. Number used in LIOS for relating tickets to LIOS. Must be unique.

Overflow DN. Overflow destination for call content (optional).

Length of LAC. Number of LAC digits; only for charging purposes.

Version of LI tickets. Specifies the version of the LI tickets.

Version of signaling. Specifies the version of signaling information in the call content connection.

LI CUG name. Name of the closed user group to which the LEA belongs (optional).


the living company

s

07/04/23


60

Ticket output format. Ticket Conversion is an optional feature. Formats: ‘Native’, ‘ASCII’, ‘ETSI V2.1’ (i.e. ticket format according to ETSI Standard ES 201 671 V2.1), ‘ETSI V2.1 with national parameters’ or ‘Ticket Header V1’.

Transmission. Transmission of intercept-related information (IRI) to the LEA.

Q3. IRI as LI tickets through a Q3 interface sent to LIOS.

INB (in-band). IRI together with the call content directly sent to LEA.

ETSI HI3 encoding for EWSD V16. If the network provider has EWSD V16 switches and the call content is to be transmitted to the LEA in ETSI format, select this checkbox. HI3 encoding can only be activated in connection with Q3.

LEA Administration – observation data EWSD (2)


the living company

s

07/04/23


61

NE ID number. The NE ID number is part of the LI tickets (defined in the Host Administration).

COLP feature. The call content connection to the LEA uses the COLP feature (connected line presentation)

Single connection. Transmission of the call content of A and B through the same B channel, otherwise through two separate channels.

CLIP DN. A virtual number specifying the switch will be sent in the call content connection to the LEA – number must be defined in the Host Administration (NE directory number).

LEA Administration – observation data EWSD (3)


the living company

s

07/04/23


62

Creating LEA – Ticket transfer using FTP Configuration of the connection from

LIOS to LEA for transmitting LI tickets. Enter user ID and password. Ticket subdirectory (optional):

To this directory the tickets will be written. It is a subdirectory of the home directory of the FTP user.


the living company

s

07/04/23


63

Creating LEA – Transport system

TCP/IP:


the living company

s

07/04/23


64

LEA Administration – CUG for LEAs

CUG = closed user group Can be used for protecting the ISDN calls

from the NE to the LEA for transmitting the call content. To prevent LEA from being blocked by external

calls. CUGs have to be preconfigured on the NE.


the living company

s

07/04/23


65

LEA Administration – CUGs


the living company

s

07/04/23


66

LEA Administration – creating a CUG (I)Select CUG NE type. Mandatory parameter.

Select an NE type for the CUG. The CUG parameters vary depending on the NE type.

CUG name. Mandatory parameter. Name of LI closed user group. The CUG name must be unique in the LIOS system.EWSD, hiQ/E9200 and MSC SR9/SR10: 15 characters max., all characters incl. special characters accepted.Alcatel S12: 8 characters max.The LI CUG name must be unique in the LIOS system.

CUG index. EWSD, hiQ/E9200 and MSC SR9/SR10: Mandatory parameter. Closed user group index; 2 characters max., decimal numbers, range: 1 to 15. Whether an LI CUG index can be used, depends on the configuration of the NE.Alcatel S12: not used.


the living company

s

07/04/23


67

LEA Administration – creating a CUG (II)CUG interlock code. EWSD, hiQ/E9200 and

MSC SR9/SR10: Mandatory parameter. Closed user group interlock code for the call content connection between the intercepting NE and the LEA’s access. If no call content connection is established, this entry is without any effect. Decimal number. Range: 0 to 65535 (EWSD and hiQ/E9200); 1 to 65535 (Siemens Mobile).Alcatel S12: not used.

CUG data network ID. EWSD, hiQ/E9200 and MSC SR9/SR10: Optional parameter. Closed user group data network identification code for the call content connection between the intercepting NE and the LEA’s access; range: 0 to 4, decimal number.Alcatel S12: not used.

Remark. Optional parameter. Maximum length: 50 characters.


the living company

s

07/04/23


68

LEA data managed with LEA Administration

LEALIOS:

LEA AdministrationEWSD

LEA identification information(e.g. LEA name, postal address)

Observation parameters (e.g. DN for call content, EWSD ID to be included in

tickets, protection through COLP)*

Sent to switch with first

observation

Kept on switch as long as

obs. exist.

For tickets

Communication data for the ticket transfer from LIOS to the LEA (transport

system, file transfer protocol)

'Check LEA modification' applies only to LEA data on EWSD.

*) If this LEA data is modified ('Modify LEA' operation), also the corresponding LEA data on the EWSD is modified – if the LEA data exists on the EWSD, that is if observations for the LEA exist.


the living company

s

07/04/23


69

LEA data (I) LIOS administrator or operator creates

a LEA (LEA Administration).

The LEA is created on the EWSD.

Observation 1 is created on the EWSD.

Observation 2 is created on the EWSD.

LIOS operator issues observation 1 for the LEA.

At activation time LIOS sends CROBSGRP to the EWSD

and ENTROBSCALL.

LIOS operator issues observation 2 for the LEA.

At activation time LIOS sends ENTROBSCALL.

LIOS EWSD


the living company

s

07/04/23


70

LEA data (II) At deactivation time of observation 1

LIOS sends CANOBSCALL. Observation 1 is removed.

Observation 2 is removed

and the LEA is removed.

At deactivation time (observation 2) LIOS sends CANOBSCALL

and CANOBSGRP.

The LEA data is still kept in the LIOS system and can be used for future observations (until it is deleted by the LIOS administrator or operator).

LIOS

EWSD

'Check LEA modification' applies only to LEA data on EWSD.


the living company

s

07/04/23


71

'Modify LEA' and 'Check LEA modification' 'Modify LEA'

(observation parameters affected)

'Check LEA modification'

'Repair' (repetition of 'Modify LEA')

The result of the LEA modification on each EWSD is displayed on the LIOS GUI.

LIOSMODOBSGRP

MODOBSGRP

EWSD 1 observations for LEA

EWSD 3no obs. for LEA

LEA mod. OK



EWSD 4no obs. for LEA

LEA mod. OK


LEA mod. failed

LEA mod. failedOK

OK

Lios Admin

Documents

Transcript of Lios Admin