lgs rostering system web viewimros rfp v10 ... warn the user in case if the manual change of the...

THE REQUIREMENTS & SPECIFICATIONSFor

IMplementation of the ROstering System

Identification NumberLGS 2013/33

June 2013

Prepared by

SJSC Latvijas gaisa satiksmeInternational Airport

”Riga”, LV-1053, Latvia

Request for proposal ImRoS ProjectThe Requirements & Specifications

1. INTRODUCTION................................................................................................51.1 LGS IN BRIEF....................................................................................................51.2 LGS PERSONNEL FACT SHEET...........................................................................5

1.2.1 General.....................................................................................................51.2.2 Operational Personnel..............................................................................61.2.3 Technical Personnel.................................................................................71.2.4 Support Personnel....................................................................................81.2.5 Sample Shift Patterns...............................................................................8

1.3 OVERVIEW........................................................................................................91.4 SCOPE OF WORK..............................................................................................91.5 ORGANISATION OF THE DOCUMENT..................................................................10

2. SYSTEM REQUIREMENTS.............................................................................112.1 GENERAL REQUIREMENTS...............................................................................112.2 FUNCTIONAL REQUIREMENTS...........................................................................122.3 SYSTEM INTERFACE.........................................................................................152.4 SYSTEM COMPOSITION....................................................................................152.5 SYSTEM ARCHITECTURE..................................................................................16

3. LGS SYSTEMS CONNECTED TO ROSTERING SYSTEM............................173.1 LGS FINANCE SYSTEM (OPTIONAL)..................................................................173.2 LGS DOCUMENT MANAGEMENT SYSTEM (OPTIONAL)........................................18

4. TECHNICAL REQUIREMENTS.......................................................................194.1 SYSTEM SPECIFICATION...................................................................................19

4.1.1 Technology.............................................................................................194.1.2 Software..................................................................................................194.1.3 Modularity...............................................................................................204.1.4 Time Synchronization.............................................................................204.1.5 Other Requirements................................................................................21

4.2 INSTALLATION AND CONSTRUCTION..................................................................224.2.1 General...................................................................................................224.2.2 Supply of removable parts and mating connectors.................................224.2.3 Installation...............................................................................................224.2.4 Materials.................................................................................................224.2.5 Cabinets and racks.................................................................................234.2.6 Labeling..................................................................................................23

4.3 ELECTRICAL DESIGN........................................................................................244.3.1 Power Supply Units.................................................................................244.3.2 Cable Identification.................................................................................244.3.3 External wiring and cabling.....................................................................24

4.4 EQUIPMENT COOLING......................................................................................254.5 ELECTROMAGNETIC INTERFERENCE..................................................................254.6 EARTHING.......................................................................................................25

5. DOCUMENTATION..........................................................................................265.1 INTRODUCTION................................................................................................265.2 GENERAL REQUIREMENTS...............................................................................265.3 PROVISION OF DOCUMENTATION.....................................................................26

5.3.1 General...................................................................................................265.3.2 System Design Document (SDD)...........................................................275.3.3 Sub System Design Document (SSDD).................................................27

document.docx of 68


5.3.4 Operational System Description.............................................................275.3.5 System Operator's Manual.....................................................................285.3.6 User’s Manual.........................................................................................285.3.7 Maintenance Manual...............................................................................285.3.8 Installation Manual..................................................................................285.3.9 Equipment Manual..................................................................................285.3.10 Subcontractor's Manuals.....................................................................29

6. QUALITY AND SAFETY ASSURANCE..........................................................296.1 GENERAL REQUIREMENTS...............................................................................29

6.1.1 Quality System Requirements................................................................296.1.2 Rights Reserved by LGS........................................................................296.1.3 Suppliers Response to Quality Requirements........................................30

6.2 QUALITY CONTROL AND VERIFICATION.............................................................306.2.1 Introduction.............................................................................................306.2.2 Design Reviews......................................................................................316.2.3 Quality Inspection...................................................................................316.2.4 Testing (General)....................................................................................316.2.5 Acceptance Tests, Definitions and Reference Points.............................326.2.6 Factory Acceptance Test (FAT)..............................................................326.2.3 Site Acceptance Test (SAT)....................................................................35

7. TRAINING........................................................................................................387.1 INTRODUCTION................................................................................................387.2 GENERAL........................................................................................................387.3 TRAINING DOCUMENTATION.............................................................................387.4 TRAINING FACILITIES AND EQUIPMENT..............................................................397.5 TRAINING OF TECHNICAL PERSONNEL..............................................................397.6 TRAINING AIMS OF THE COURSE FOR TECHNICAL PERSONNEL..........................397.7 TRAINING OF OPERATIONAL PERSONNEL..........................................................407.8 TRAINING AIMS OF THE COURSE FOR OPERATIONAL PERSONNEL......................407.9 PROPOSAL FROM THE SUPPLIER......................................................................40

8. STATEMENT OF COMPLIANCE.....................................................................418.1 GENERAL........................................................................................................418.2 STATEMENT TABLE..........................................................................................418.3 FORMAT..........................................................................................................41

9. PROJECT MANAGEMENT..............................................................................429.1 INTRODUCTION................................................................................................429.2 CONTRACTOR’S REPRESENTATIVE....................................................................429.3 SUPPLIER’S PROJECT ORGANIZATION...............................................................429.4 PROJECT MANAGEMENT PLANS.......................................................................429.5 PROGRESS MEETINGS.....................................................................................439.6 BUYER’S PROJECT ORGANIZATION...................................................................43

10. HARDWARE AND SOFTWARE REQUIREMENTS........................................4410.1 GENERAL.....................................................................................................4410.2 SOFTWARE REQUIREMENTS..........................................................................4410.3 HARDWARE REQUIREMENTS.........................................................................44

ANNEX 1. SHIFT PATTERNS...................................................................................47STANDARD PATTERN.............................................................................................47AMGKCS DIVISION...................................................................................................48

document.docx of 68


AIS DIVISION.............................................................................................................49BRIEFING DIVISION..................................................................................................50FMFDU DIVISION......................................................................................................53ATC CENTRE............................................................................................................57TOWER RIGA............................................................................................................61TOWER LIEPAJA......................................................................................................63

document.docx of 68


1. INTRODUCTION

1.1 LGS in Brief1.1.1 The main goal of the State Joint-Stock Company “Latvijas gaisa satiksme” (LGS) is to provide safe and optimal Air Navigation Services in Latvian airspace, namely Riga Flight Information Region (FIR).

1.1.2 LGS was founded on the October 21, 1991 as an Air Navigation Services Enterprise with 100% state ownership on the basis of the disintegrated “Aeroflot” structure. On June 12, 1997 the enterprise changed its legal status and became a State Joint-Stock Company keeping the same title.

1.1.3 The Air Navigation Services are provided in accordance with ICAO and EUROCONTROL standards and recommended practices. An operational differences are published in Latvian AIP.

1.1.4 As an enterprise operating in the field of civil aviation, LGS is subject to the Ministry of Transport of the Republic of Latvia and is under regulatory supervision of Latvian Civil Aviation Agency.

1.1.5 Operating in the market economy LGS is client-oriented and provides all the users with equal quality services as per international standards.

1.1.6 The main revenue source for LGS is the air navigation charges collected for the services rendered. There is no financing from the State budget. LGS is one of the largest taxpayers in Latvia.

1.2 LGS Personnel fact sheet

1.2.1 General1.2.1.1 Working week: 40hrs, max 56hrs but not more than 160hrs in 4 weeks;

1.2.1.2 Optional: 5 working days, 2 days free;

1.2.1.3 Min 12hrs between shifts;

1.2.1.4 Vacation: 28 calendar days + max. 11 additional;

1.2.1.5 Leave for children care: (min approximately 300 calendar days, max approximately 482 calendar days);

1.2.1.6 Paternity leave: 10 calendar days;

1.2.1.7 Leave for studies and examinations: 20 working days;

1.2.1.8 Collective agreement days off:

1.2.1.8.1 3 calendar days to the wedding,

1.2.1.8.2 3 calendar days to the funeral;

1.2.1.8.3 1day – 1 September for parents of primary school children;

1.2.1.8.4 1 day – graduates;

document.docx of 68


1.2.1.9 Vacation planning a year ahead (long, short) with possibility of splitting;

1.2.1.10 Working time accounting;

1.2.1.11 The work journey planning and accounting;

1.2.1.12 Business trips (workshops, exhibitions, exchanges of experience, projects,8 hours, etc.).

1.2.2 Operational Personnel1.2.2.1 Staff and WP:

1.2.2.1.1 ATCC – 59

1.2.2.1.2 OSUP – 5 (+5 part time)

1.2.2.1.3 Controllers: 54

1.2.2.1.4 APP – 27

1.2.2.1.5 ACC EAST – 44

1.2.2.1.6 ACC West/North – 39

1.2.2.1.7 Working Positions (WP):

1.2.2.1.8 OSUP 1WP – 24hrs

1.2.2.1.9 Sector EAST: EX WP – 24hrs; PL WP – 15hrs

1.2.2.1.10 Sector WEST: EX WP – 24hrs; PL WP – 15hrs

1.2.2.1.11 Sector NORTH: EX WP – 15hrs; PL WP – 8hrs

1.2.2.1.12 Sector APP1: EX WP – 24hrs; PL WP – 15hrs

1.2.2.1.13 Sector APP2: EX WP – 12hrs

1.2.2.1.14 Riga TWR - 26

1.2.2.1.15 OSUP – 5 (+1 part time)

1.2.2.1.16 Controllers: 20

1.2.2.1.17 OSUP 1WP – 24hrs

1.2.2.1.18 Riga TWR: EX WP – 24hrs

1.2.2.1.19 Riga Ground: EX WP – 24hrs

1.2.2.1.20 Liepaja TWR: Controllers: 4

Liepaja TWR(AFIS): EX WP

document.docx of 68


1.2.2.2 Training planning (refresh, seasonal training, rating prolongation (including business/training trips), TRM, UK, ELPAC;

1.2.2.3 Strategic and tactical planning (endorsements; renovations);

1.2.2.4 Schedule construction according to local legislation (work. hours per week/month, rest time after night shifts, etc.);

1.2.2.5 Use of preferred patterns (according to company rules);

1.2.2.6 Reservation (planning) of day-off’s;

1.2.2.7 Determination of necessary number of ATCO’s per shift (taking into account not the minimum possible number, but potential reserve);

1.2.2.8 ENG Test: 8 hours;

1.2.2.9 Medical checkup: 8 hours;

1.2.3 Technical Personnel1.2.3.1 Staff and units:

1.2.3.1.1 ATRACC unit - 19:

1.2.3.1.1.1 Business days (5 working days, 2 days free) – 5;

1.2.3.1.1.2 Shift (7 days a week/24 hours a day) – 14;

1.2.3.1.2 Building and Transport unit – 7:



1.2.3.1.3 Electrical power unit – 7:



1.2.3.1.4 IT unit – 9:


1.2.3.1.5 Meteorological unit – 12:

1.2.3.1.5.1 Business days (5 working days, 2 days free) - 6;


1.2.3.1.6 Radar unit – 10:



1.2.3.1.7 Navigation unit – 14:



1.2.3.1.8 Communication unit – 22:


document.docx of 68




1.2.3.1.9 Mintenance Management unit – 3:


1.2.3.1.10 Head of Department - 1:


1.2.3.2 Maintenance planning (required count of personnel, time to prepare for maintenance, etc.);

1.2.3.3 Technical training planning (monthly, including safety);

1.2.3.4 Qualification improvement courses in training centers (LGS, Luxembourg, equipment-manufactures, etc);

1.2.3.5 Other training (climbing, electrical safety, safe driving, the airport „Riga” courses);

1.2.3.6 Emergency works and others unforeseen work performance and personnel time accounting;

1.2.3.7 Execution of various works – related to equipment installation, reconfiguration (the order specified time – often at night – outside of normal working hours).

1.2.4 Support Personnel1.2.4.1 The ImROS system will be used by all of the LGS personnel. It means

the system shall be able to provide the rostering for Security, car drivers, cleaners, etc.

1.2.4.2 Their rostering partly correlates and duplicates with other rosterings. Additional information might by provided during the site survey by request.

1.2.5 Sample Shift Patterns1.2.5.1 Refer to Annex Nr 1.

document.docx of 68


1.3 Overview

1.3.1 This document provides operational, functional, technical and other specifications for procurement of Implementation of Rostering System (ImRoS) for LGS Project.

1.3.2 It is the intention of “Latvijas gaisa satiksme” (LGS) that the system procured will provide the maximum benefit/cost ratio with the minimum risk of time-scale overrun. As such, the procured system is expected to comprise a large proportion of existing capabilities, but with a degree of development and tailoring where required to meet the requirements of LGS. The organization and content of this document, and the instructions to Supplier detailed below, are designed to facilitate the evaluation of these factors.

1.3.3 Mandatory capabilities are denoted with the term “shall”; desired capabilities are denoted with the term “should”. Suppliers are encouraged to propose COTS systems that provide all the mandatory capabilities and as many desired capabilities that are available with a minimum amount of development.

1.4 Scope of Work

1.4.1 The Supplier shall undertake to:

1.4.1.1 Deliver hardware

1.4.1.2 Deliver software

1.4.1.3 Perform System adaptation to LGS environment

1.4.1.4 Perform integration with existing LGS Finance System and LGS Document Management and Electronic Document Management system (optional).

1.4.1.5 Perform installation of hardware and software

1.4.1.6 Deliver documentation

1.4.1.7 Provide training

1.4.1.8 Perform factory acceptance testing

1.4.1.9 Perform site acceptance testing

1.4.1.10 Provide warranty

1.4.1.11 Provide after-sales service

document.docx of 68


1.5 Organisation of the Document

1.5.1 Chapter 1 provides an introduction including information about the document structure and reference documents.

1.5.2 Chapter 2 provides the Functional Requirements of the ImRoS Project

1.5.3 Chapter 3 describes the LGS systems connected to Rostering System.

1.5.4 Chapter 4 describes the Technical Requirements of the ImRoS Project.

1.5.5 Chapter 5 describes the Documentation.

1.5.6 Chapter 6 describes the Quality and Safety Assurance.

1.5.7 Chapter 7 describes the Training.

1.5.8 Chapter 8 describes the Statement of Compliance.

1.5.9 Chapter 9 describes the Project Management.

1.5.10 Chapter 10 describes the Hardware and Software Requirements.

1.5.11 Annex 1 describes the samples of Shift Patterns

document.docx of 68


2. SYSTEM REQUIREMENTS2.1 General Requirements

2.1.1 This document describes the configuration, performance, and functionality of the Rostering System (ImRoS) to be delivered during the Project.

2.1.2 This section also describes the functionality required at end user application and not how this functionality is to be achieved technically, or the parameters within which the system will operate.

2.1.3 The system shall be operationally proven, have a high availability, shall be fully reconfigurable, and represent state of the art technology. It is anticipated that the majority of equipment supplied shall be commercial off the shelf, and that a minimal amount of customization will be necessary to achieve the required functionalities.

2.1.4 Clarity, integrity and correctness of the data: the system shall guarantee the clarity, integrity and correctness of the data it manages and shall ensure the centralized management of such data.

2.1.5 The system shall assign the role for each user. The role shall be configurable with the set of the parameters/permissions for each user.

2.1.6 The system shall enable traceability and data logging of all operations that are effected (both by the regular user and by the system administrators). Users can access the system through a personal system profile – User Role. This renders shall limit access to information and functions that the user is not entitled to.

2.1.7 The system shall enable the user, within the Role of his or her assigned profile, to manage any modifications, additions or substitutions of fields or other objects (e.g. insertion / cancellation, role / responsibility, new trade union agreements, new regulations, insertion of new class) in complete autonomy and with the maximum flexibility, and to disable or enable functions

2.1.8 The system shall include and manage HR “anagraphyc” data.

2.1.9 The system shall be integrated with the Customer Finance System and Customer Document Management and Electronic Document Management system.

2.1.10 The system shall provide and follow for a logical chain of action for the insertion of data.

2.1.11 The system shall be user-friendly and easily navigable, in other words the user shall be aided in identifying information presented by the various masks.

2.1.12 The system shall enable comprehensive searches through pre-defined keywords (e.g. identification number, first name, surname, assigned place of work, rating, etc.), so that specific information should be found quickly. It shall also enable the filtering, ordering and extrapolation of data for tactical management and for the production of reports.

2.1.13 The system shall allow for available functions to be activated over time according to the real organizational needs of the Customer, as well as allowing for an extension of its capabilities according to user numbers and work peaks.

document.docx of 68


2.1.14 The system shall be easy configurable by the set of parameters. The configuration process shall be documented with high details.

2.1.15 The utilization of the system should be so simple that it should be enough to have one person only from each Customers’ department, who will work with the Roster.

2.2 Functional Requirements2.2.1 The major function of the system is to manage the shifts, grant and record the changes, vacations (both planned and incidental), sick leaves, other situations according to the rules of the Customer.

2.2.2 System shall build the roster automatically.

2.2.3 System shall operate taking into account the preferences of each person like, for example, request to work in the morning shift only.

2.2.4 System shall take into account the European, National Regulations and Collective Labour agreement rules like rest time between shifts, max. working days, leave for children care, leave for studies, etc.

2.2.5 It shall be possible to reserve the special days in advance like to avoid the training days for the dates, when simulator is not available, etc.

2.2.6 System shall warn the user in case if the manual change of the roster will cause the further multiple changes and shall propose the resolution.

2.2.7 System shall produce alerts in advance the roster of the person in case if medical license expires, monthly work limits expires, more than 6 days’ work in a row, etc.

2.2.8 If alerts have not been taken into account system shall block the roster of the person in case if medical license expires, monthly work limits expires, more than 6 days’ work in a row, etc.

2.2.9 System shall propose the free standby persons to call in case of substitution (taking into account rating, endorsement, and previous calls, “black” and “white” lists, etc.).

2.2.10 System shall sends SMS or/and email to person with the goal for accept/refuse the change. The answer shall be done by phone, via SMS or/and e-mail.

2.2.11 The change request shall be issued from the person via Web-Application in advance. The period shall be set flexible (like one day in advance for ordinary change, 2 hours in advance for incidental sick leave, etc.).

2.2.12 Web-Application shall require the Authorization of the each person.

2.2.13 The system shall not allow two users to change simultaneously the same rostering data, or on the same shift tables for a category and a facility nor during the same time period. It shall avoid undesirable change of the same data.

2.2.14 For the operations with the Rostering system Authorized users shall have an access to the system from outside of the Customer network either via Web-Application or/and via special application.

2.2.15 System shall operate with virtual copy of real enterprise structure: ACC/APP/TWR, technical divisions, administration divisions.

document.docx of 68


2.2.16 The system shall support the planning in advance of shift workers.

2.2.17 The planning in advance shall be possible for any time period: days, weeks, months, quarters, years, etc.

2.2.18 The planning in advance shall be managed for each worker in compliance with scheduling rules, including those relating to the connection of shifts with any previous shift.

2.2.19 The planning in advance shall be adaptable to the environment for which it is proposed, giving the user the possibility of choice between more than one scenarios proposed by the system. This process shall be automatic for all the relevant personnel, on the basis of a pattern/template which is pre-defined by the user.

2.2.20 It shall be possible to simulate the changes in the structure (like re-structurization, new personnel, etc.). System shall do the cost-benefit analysis and should propose the optimal roster plus several options.

2.2.21 System shall be able to collect and present the statistical data about each person including how many hours worked a month/a year, extra calls, overtime, holidays/day-offs, sick leave, etc.

2.2.22 System shall have the detailed information/reports about all the changes with reporting and statistics, including such activities like, for example, number of change requests per month and a real number of changes.

2.2.23 Personal cards in the Electronic Document Management system shall be expanded (if necessary) with the goal to input all the personal data (like rating, unit endorsement, licenses, health certificates, etc.) and preferences in the one system only and to avoid the duplication of any possible inputs in the several systems.

2.2.24 The Data about the shifts shall be sent to Finance system on regular basis at least once a day (in the night for example).

2.2.25 The system shall have a log/journal of all the actions/activities made by every user. This log shall be accessible and provide a comprehensive and detailed report.

2.2.26 Log shall be stored for the time period defined as a parameter. The system shall perform the planning and control of work shifts on the basis of rules and constraints contained in a rule engine in order to provide solutions that are compatible with company constraints and practices.

2.2.27 The system shall manage the rules in two different ways:

2.2.27.1 Soft rules - the rule shall consider a goal to reach / maximize and may be waived;

2.2.27.2 Hard rules - the rule shall be a programmed constraint that may not be violated.

2.2.28 The system shall apply the shift rules to every stage of rostering:

2.2.28.1 strategic planning;

2.2.28.2 monthly or quarterly planning;

2.2.28.3 assignment of working positions;

2.2.28.4 management of daily operations;

2.2.28.5 manual changes to shifts.

document.docx of 68


2.2.29 The system shall have the ability to utilize different regulations that are diversified according to staff category, even within the same facility.

2.2.30 The system shall have a special web interface integrated within the company web portal, the system can accept requests for shift variations, absences and shift swap proposals submitted by shift workers for shifts which have already been planned. The system then proposes several solutions – allowing for the time necessary to make any changes – to the decision-maker. These will highlight the “cost” (not necessarily an economic statistic) of the various changes of shift necessary in order to accommodate the maximum number of requests. These shift changes will remain subject to approval by the user of the Integrated Rostering System.

2.2.31 The system shall communicate the shift change to the employee via email, illustrating the new shift calendar for the month in question. The number of manageable shift changes daily or for any other period shall be unlimited in number.

2.2.32 The system shall provide for the construction of a daily staff log assigned for duty at the working positions foreseen by the active configuration. It shall be possible for this assignation of personnel to take place automatically, or manually or part-manually / part-automatically.

2.2.33 The system shall check the rotation of employees at working positions based on current unit endorsements, with the aim of safeguarding the minimum thresholds required by the rules for the maintenance of unit endorsements.

2.2.34 The system shall enable the publication of assignments to working positions per daily shift and per facility.

2.2.35 The operational management of shifts is carried out locally by each site or facility and begins with the strategic planning of nominal shifts. The system shall allow shifts to be re-programmed on a monthly, weekly and daily basis, for example, by allowing the replacement of staff on duty, in order to allow adequate coverage of working positions in the event of unscheduled absences (illness, training, etc.).

2.2.36 The system shall produce a concise interface for use by the shift supervisor. This interface shall focus in turn on the resources covered by the supervisor’s hours, including a table view similar to the one in the log.

2.2.37 The system shall be able to provide the supervisor with information regarding on-call staff and a contact list for the various endorsements, with their respective addresses, ordered according to their ratings (it is best to begin the list with the on-call staff possessing lower ratings), and also according to the number of overtime hours already worked that year. The supervisor on duty may change only the work assignments for the shift for which he or she is responsible, and for the weekends and public holidays during which the staff office is closed.

2.2.38 The System shall be notified in real time of changes in staff absences and presences. The Supervisor shall be able to consult a screen showing the clock-on, clock-off details of the shift worker.

document.docx of 68


2.3 System Interface2.3.1 All the System Interface (including menus, windows, web-applications) shall be in English or Latvian.

2.3.2 All the System messages, logfiles, configuration parameters shall be in English or Latvian.

2.3.3 System reports shall be in English or/and Latvian.

2.3.3.1 Report sheets presented to Finance department shall be in English or/and Latvian.

2.3.4 All the other information presented by the System and not listed above shall be in English or/and Latvian

2.3.5 System shall support Unicode, i.e. data stored in the system shall be in English, Latvian or any other language supported by Unicode.

2.4 System Composition2.4.1 The ImRoS shall be delivered, installed and implemented on TURN-KEY basis.

2.4.2 The ImRoS shall be delivered fully equipped (including racks, interfaces, software capacity, power supply, network equipment, etc.) in order to fully meet the requirements stated in this document.

2.4.3 The Central Equipment shall be installed in the Equipment Rooms of the LGS ATS Centre Building.

2.4.4 The ImRoS itself and necessary Peripheral Equipment shall be installed in the locations defined by LGS.

2.4.5 The ImRoS shall consist of:

2.4.5.1 Central Rostering Server module, which shall have the reliable redundant configuration;

2.4.5.2 Rostering Application Module(s), which shall be installed and used as separate end user software applications or/and (depending on roles and functions) should be accessible via web-interface.

2.4.5.3 Rostering Integration Module, which shall provide the interaction with LGS Finance system and LGS Electronic Document Management system.

2.4.5.4 Rostering Transaction Server and Security Module, which shall provide secured and controlled access to the Rostering system via Internet.

document.docx of 68


2.5 System Architecture2.5.1 The Supplier shall demonstrate the Architecture of the system, which shall have the elements presented on the Drawing below

INTERNET

LGS LAN

Rostering Central Server

LGS FinanceSystem

RosteringRemote APP

RosteringWeb APP

LGS EDMSystem

Rostering Application

RosteringApplication

LGSFirewall

RosteringTransaction Server

Rostering SMSGateway

LGSFirewall

2.5.2 The components of ImRoS are marked with red.

2.5.3 The Supplier shall prove the fulfilment of the requirements in case if the proposed System’s architecture differs from the presented above.

document.docx of 68


3. LGS SYSTEMS CONNECTED TO ROSTERING SYSTEM

3.1 LGS Finance System (optional)3.1.1 Finance System is FinaWinSolis Alga3.1.2 It is a responsibility of the Bidder to contact the supplier of LGS Finance System and to develop and implement the Interface between the Finance System and Rostering System.

3.1.2.1 Contact Details are: Mr Aleksandrs Ozerskis, SolCraft, phone +371 29256451, [email protected].

3.1.3 The IMROS system shall be able to provide at least the following data to the LGS Finance System:

3.1.3.1 Employee info;

3.1.3.2 Actually worked shifts (according to the category of the shift);

3.1.3.3 Date/Time;

3.1.4 FinaWinSolis Alga is based on Firebird Sql server (ver.FB 2.5);

3.1.5 Data exchange with other programs (one of the following options is possible)

3.1.5.1 Supports data import from

a) xls (preferable option)b) txt,csv,c) xml,d) dbf files

3.1.5.2 data from external applications might be uploaded directly into Alga data base, with prior access rights and rules defined (for instance, through ODBC or directly) (preferable option)

3.1.6 Implementation of web service inteface is possible as well if the above said options are not available.

3.1.7 The expenses for the establishment should be a part of this project and shall be done as Supplier’s expenses.

3.1.8 More detailed information about this system might be obtained during site survey.

document.docx of 68

mailto:[email protected]


3.2 LGS Document Management System (optional)3.2.1 Electronic Document Management System (EDMS) is a modular system consisting of separate subsystems (databases with different templates) for storage and processing the specific information such as correspondence, agreements, information about human resource etc.

3.2.2 EDMS is a tailored product based on IBM Lotus Notes/Domino. The developer of the EDMS is Tieto Latvia ( http://www.tieto.lv ) and it has copyrights to make any modifications of software.

3.2.3 Detailed technical requirements are described in the IBM Corporation issued document "Detailed System Requirements for Lotus Notes, Lotus Domino, Lotus Domino Administrator, Lotus Domino Designer, and Lotus Notes Traveler" - http://www-01.ibm.com/support/docview.wss?rs=475&uid=swg27007909

3.2.4 Human Resource Management System is a database providing information about company’s hieararchical structure and maintenance of folowing information about employees:

3.2.4.1 Basic information about employee (name, gender, adress, contact information etc.);

3.2.4.2 employment contract, the contract amendment registration;

3.2.4.3 education and training,

3.2.4.4 cerificate of qualification;

3.2.4.5 health checks, medical certificates indicating,

3.2.4.6 vacations;

3.2.4.7 sick leaves;

3.2.4.8 business trips and other absenteism (f.e. educational leave, maternity leave etc).

3.2.5 The Bidder shall propose a solution that ensures that the data that has already been and will be entered (f.e. information about vacations, business trips of current employees, registering a new employee etc.) in EDMS is automatically synchronized with data in Rostering System.

3.2.6 The Bidder shall agree and coordinate with the Suplier of LGS EDMS the possible expansion/change of information about employees inside EDMS system with the goal to input all the necessary data in EDMS system only.

3.2.7 It is a responsibility of the Bidder to contact the supplier of LGS EDMS and to develop and implement the Interface between the EDMS and Rostering System.

3.2.8 Contact details are: Mr. Juris Kalinovskis, TIETO Latvija; phone +371 67510634, e-mail: [email protected]

3.2.9 The expenses for the establishment should be a part of this project and shall be done as Supplier’s expenses.

3.2.10 More detailed information about this system might be obtained during site survey.

document.docx of 68

mailto:[email protected]

http://www-01.ibm.com/support/docview.wss?rs=475&uid=swg27007909

http://www.tieto.lv/


4. TECHNICAL REQUIREMENTS4.1 System Specification 4.1.1 Technology4.1.1.1 The design shall be based upon the application and adaptation of proven

modern technology and architecture (hardware and software) with the objective of optimizing overall system performance and lifetime, minimizing technical risks and meeting the safety requirements of the user.

4.1.1.2 It is imperative that all hardware, software and firmware that is to be utilized shall be totally proven in an operational environment that has similar, if not more stringent requirements than those stated within this Specification.

4.1.1.3 In particular, the design of the system shall be such that failure of units shall never cause a complete outage of the total system. Only gradual degradation of performance is allowed.

4.1.1.4 Any data processor in the proposed configuration shall have sufficient spare capacity for subsequent extensions or modifications i.e. spare memory capacity, spare I/O facilities and reserve in processing time (duty cycle). This spare capacity shall be in the order of 40 %.

4.1.1.5 The application software shall preferably be developed under a standard operating system. Use should be made of a high level language. The software should be written in accordance with the principles of structured programming in order to allow for efficient software maintenance. Only well-proven software which is already used in a similar system shall be offered. References should be state.

4.1.2 Software4.1.2.1 The system software architecture shall be such that system functions are

assigned in four areas:

4.1.2.1.1 Operating system software

4.1.2.1.2 Applications software

4.1.2.1.3 System configuration and environment data

4.1.2.1.4 System maintenance software

4.1.2.2 The system shall be such, that new versions of all software types can be loaded and tested without detriment to the operational service.

4.1.2.3 The Operating System software shall provide the capability for real-time execution, file management, command procedures and various utilities.

4.1.2.4 The Operating System to be utilized may be of an industry standard type, and in any event, shall be totally proven in a similar environment.

4.1.2.5 The application software shall include software that is unique to a specific function

4.1.2.6 Unique application software shall be based on proven technology.

document.docx of 68


4.1.2.7 The system configuration data shall consist of all details of variables and configuration parameters of the system.

4.1.2.8 The system shall provide the operator with tool for display, input, back-up and restore/loading of all system variables and configuration parameters.

4.1.2.9 The system shall provide the operator with windows-like interface.

4.1.2.10 The system maintenance software shall be available when the system requires reports on diagnostics, testing etc. This software shall run in background and shall have no detrimental effect on any system processing.

4.1.2.11 The system maintenance software shall provide self-diagnostic capabilities, with the ability to detect failures, localization of defective module and with operator intervention isolate any defective modules and take out of service any defective part or unit.

4.1.2.12 The system maintenance software shall include facilities for activity and event logging. It shall be possible to extract this information from the system in a suitable industry standard format, for off line statistical analysis, without in any way effecting the operational service.

4.1.2.13 The software design shall be functionally and operationally modular to:

4.1.2.13.1 Facilitate system expansion, modification and configuration control;

4.1.2.13.2 Facilitate fault detection, diagnosis, containment, recovery and fault tolerance;

4.1.2.13.3 Facilitate changes to the lowest practical level without large scale program reassembles;

4.1.2.13.4 Allow all configuration data to be held in a separate data file.

4.1.2.14 Other requirements about the ImRoS system software will be found in chapter “Hardware and Software Requirements”.

4.1.3 Modularity4.1.3.1 The system design and construction shall be highly modular in order to

accommodate user site variations, change of Operational requirements and to limit possible failure to sub-assemblies.

4.1.3.2 Faults in one unit shall thus never influence the proper Operation of other units. The Interfaces between the central equipment and the working positions should be based on standard interfaces.

4.1.4 Time Synchronization4.1.4.1 The time synchronization shall be made by means of standard network

time protocol (NTP), connecting to the existing or internal timeserver within LAN.

4.1.4.2 The time synchronization shall be performed on regular basis, e.g. hourly. The frequency of time synchronizations should be a subject of system configuration.

document.docx of 68


4.1.5 Other Requirements4.1.5.1 As a general rule, so called "Off the Shelf" equipment are preferred.

Therefore no precise technical requirements for such equipment are implied herein.

4.1.5.2 If any custom-made components are used, their functions shall be broadly outlined.

4.1.5.3 The equipment must be, as far as possible, so constructed that, similar part, spares and replaceable units are interchangeable and easily fitted.

4.1.5.4 General provisions regarding construction are given below, however, as stated before, in case of so called "Off The Shelf" equipment, the Supplier shall just show the compliance/non-compliance between the equipment and requirement; the Supplier is not required to modify his "Off The Shelf" solutions according to these requirements.

4.1.5.5 The Supplier shall describe and define all related standards and rules, which his equipment design, solutions and production methods are based on.

4.1.5.6 Construction of the system equipment shall employ standardization of cabinets, modular packaging, parts, materials, processes and workmanship.

4.1.5.7 Installation and design shall be performed in such a way that a failure in one unit will not disturb the function of units on the same or higher level.

4.1.5.8 Initial approval respect to the technical design and conditions will be given by LGS after the Supplier has:

4.1.5.8.1 Shown an example of already existing equipment and provided with all necessary explanations concerning its design and operation; or

4.1.5.8.2 Supplied with a full description of the design, presentation, and access facilities and a provisional list of the components, which will be used.

4.1.5.8.3 Visits could be made to the Supplier's premises during the production period. The aim of these visits is to monitor the general advancement of the equipment production and can in no way be considered as a substitute for a "factory inspection" before shipment of goods. Any observations formulated by LGS will be notified to the Supplier who will take them into account for the production of the equipment.

4.1.5.8.4 Files containing all such observations shall be kept by the Supplier to help to form a technical record to be used during the factory inspection and during provisional and final acceptance.

document.docx of 68


4.2 Installation and Construction

4.2.1 General4.2.1.1 Installation of hardware and software shall be performed at LGS

premises at Riga International Airport.

4.2.1.2 Installation, setting up and commissioning of all equipment, including interfacing and interconnection of all units/subsystems and supply of all the necessary cables shall be the responsibility of the Supplier.

4.2.1.3 Site Preparation and Installation shall take into account the existing environment and technical features LGS has available.

4.2.2 Supply of removable parts and mating connectors4.2.2.1 All equipment furnished by the Supplier shall be complete e.g. with an

installed set of fuses, lamps, plug-in integrated circuits, plug-in relays, plug-in crystals, and all other parts which are used in the equipment and which are similarly designed for quick removal and replacement.

4.2.2.2 Where a cable connector is provided on a piece of equipment furnished under the contract, which will be connected to another piece of equipment not being furnished under the contract, the Supplier shall supply the mating connector for the equipment under contract.

4.2.2.3 When two or more pieces of equipment furnished under the contract require interconnection, the Supplier shall supply the necessary cables with mating connectors installed.

4.2.3 Installation4.2.3.1 The equipment shall be designed so that it can be easily installed,

removed, and reinstalled with a minimum of special tools and without extensive disassembly.

4.2.4 Materials4.2.4.1 All materials should be antistatic and they shall not be dangerous for

users.

4.2.4.2 Radioactive or poisonous vapor emitting materials, natural rubber, wood and wood products and flammable materials shall not be used.

document.docx of 68


4.2.5 Cabinets and racks4.2.5.1 The racks, cabinets, consoles and other furniture (if such exist) to be

installed in one particular room are to be of comparable dimensions and appearance.

4.2.5.2 All inscriptions and information shall be in English.

4.2.5.3 The cabinets shall be provided with doors. Cabinet’s type and model should be agreed with LGS.

4.2.5.4 The Supplier shall list the number, size, weight, power consumption and heat load (dissipated power) of each type of cabinet.

4.2.5.5 Special requirements for equipment configuration shall be stated.

4.2.5.6 The relative configuration of different units e.g. power supplies, memories etc. within a cabinet shall be stated together with information about central cabling entrances. The equipment shall be designed to facilitate quick access to all units within the cabinets. The Supplier shall specify the necessary means for mounting of cabinets.

4.2.6 Labeling 4.2.6.1 All labeling shall be unified. The Supplier shall determine the type of

labeling system to be used.

4.2.6.2 LGS reserves the right to change this system. In that case labeling system is defined in co-operation with LGS and the Supplier.

4.2.6.3 Labeling shall be made for the following items:

4.2.6.3.1 Cabling;

4.2.6.3.2 Cabinets and consoles;

4.2.6.3.3 Cable vaults and conduits;

4.2.6.3.4 Equipment.

4.2.6.4 Labeling shall include equipment labels, cable labels and cable addresses and color marking of cable vaults and conduits according to their disturbance group.

4.2.6.5 All markings shall be made in a permanent way to a lasting wear that can be mounted reliably.

4.2.6.6 Labels shall be fixed regularly and flexibly. If the label is hidden then it shall be doubled or there shall be a pointer for it.

4.2.6.7 All labeling and corresponding documents shall be compatible.

document.docx of 68


4.3 Electrical Design

4.3.1 Power Supply Units4.3.1.1 The System shall be able to be supplied by AC main 220 volt +/- 10%,

50 Hz +/- 2%.

4.3.1.2 The quantity of power supply units together with associated output voltage and maximum current shall be listed.

4.3.1.3 All power supplies shall have protection against both overcurrent and overvoltage in case of any occurring fault, e.g. short circuit of the voltage or short circuit in some component.

4.3.1.4 All the AC power plugs and sockets shall be Schuko (“CEE 7/4”).

4.3.2 Cable Identification4.3.2.1 Wires carrying given signals shall be easily identifiable. Covering of

different colors may be used to identify wires carrying different types of signals, e.g. supply, input, output signals, etc., and modifications to wiring. All connectors shall be identified with labels or tags.

4.3.3 External wiring and cabling4.3.3.1 Wiring between units shall be brought together to form a relatively small

number of uninterconnected multicore cables. These shall be identical. The cable connectors shall be capable of being connected and disconnected more than 5.000 times without any precautions being necessary.

4.3.3.2 All cables shall have identification at both ends according to cabling doc.

4.3.3.3 All cables and/or wiring shall be provided with at least 10% spare routings, with a minimum of two.

document.docx of 68


4.4 Equipment Cooling

4.4.1 In the equipment room it is preferred that the cooling is effected by convection.

4.4.2 A failure of the cooling system for up to 30 minutes shall not affect the performance of the equipment or shorter its expected life cycle.

4.5 Electromagnetic Interference4.5.1 The Supplier shall state the guaranteed maximum amount of external electromagnetic radiation on band 0 ... 3 GHz that does not cause harm for the equipment.

4.5.2 Any requirement for Faraday cage shall be stated in the Tender documents.

4.5.3 The equipment shall be designed in compliance with Standard EN 55 022 of European Committee for Electrotechnical Standardization (CENELEC):"Limits and methods of measurement of radio interference characteristics of information technology equipment".

4.6 Earthing4.6.1 All equipment shall be connected to the PE for safety reasons. Only exception is equipment with double insulation, which must be indicated with a sign on the equipment.

4.6.2 Testing of potential free level in PE grounding shall be done during start-up.

4.6.3 No loops in earthing circuits are allowed, but structure of circuits shall be of "tree" type.

document.docx of 68


5. DOCUMENTATION

5.1 Introduction5.1.1 This chapter gives detailed information of the documentation required for technical maintenance, technical system operation, and operational use of the system and sub systems.

5.1.2 Requirements for the documentation of software are included.

5.1.3 Documentation requirements for the various project phases will be found in chapter: PROJECT MANAGEMENT.

5.1.4 Documentation requirements associated with acceptance testing are in chapter: QUALITY AND SAFETY ASSURANCE.

5.1.5 Training documentation requirements are in chapter: TRAINING

5.2 General Requirements5.2.1 It is essential that documentation is of a high standard, and that text is presented in a clear and correct language. Where possible, diagrams, pictures etc. shall be used as supplement to the text. Refer also to the chapter: QUALITY AND SAFETY ASSURANCE.

5.2.2 The documentation shall:5.2.2.1 be written in the English or Latvian;

5.2.2.2 present information in a clear and logical manner;

5.2.2.3 provide cross-referencing between drawings, diagrams and text;

5.2.2.4 contain drawings using standard symbols;

5.2.2.5 contain indexes and glossaries.

5.2.3 All documentation shall be subject to LGS approval. LGS reserves the right to review and comment on all draft versions of documentation prior to printing.

5.2.4 All documentation shall be delivered both in printed form and as computer readable files (PDF). If the Supplier has used word processor for production of other documentation, is delivery of computer readable files also mandatory for this part.

5.2.5 It shall be provided not less than 3 copies of each manual

5.2.6 LGS reserves the right to copy and to use the delivered documentation in performing, for instance, training.

5.3 Provision Of Documentation

5.3.1 General5.3.1.1 The following documentation items shall be provided:

5.3.1.1.1 System Design Document;

5.3.1.1.2 Sub System Design Document;

5.3.1.1.3 Operational System Description;

5.3.1.1.4 System Operator's Manual;

document.docx of 68


5.3.1.1.5 User´s Manual;

5.3.1.1.6 Maintenance Manual;

5.3.1.1.7 Installation Manual;

5.3.1.1.8 Equipment Manual;

5.3.1.1.9 Item Manual;

5.3.1.1.10 Subcontractor's Manuals;

5.3.1.1.11 A list of binary files and configuration / parameter files;

5.3.2 System Design Document (SDD)5.3.2.1 In order to provide the maximum scope to Suppliers to propose the re-

use of existing capabilities, the requirements are often specified herein at a relatively high level. Therefore, the proposals must contain sufficient detail to allow a reliable evaluation of the systems.

5.3.2.2 SDD shall be worked out to give a full overview of the ImRoS and integration of the various sub-systems.

5.3.2.3 SDD shall give an outline of the complete system as delivered. It shall be adapted to the engineering staff and describe composition and functions of the system.

5.3.2.4 SDD shall give a general overview of the sub-systems and outline the structure of associated documentation.

5.3.2.5 Cross-reference to further documentation shall be included.

5.3.3 Sub System Design Document (SSDD)5.3.3.1 Separate sets of documentation shall be worked out for each of the main

sub systems nominated below. The documentation for each sub system shall follow the outline structure given below, to the extent considered relevant by the Supplier and accepted by the Buyer:

5.3.3.1.1 Monitoring and Control System;

5.3.3.1.2 Interfaces.

5.3.3.2 This manual shall give a broad outline of the complete relevant sub system. It shall be written for the engineer staff and describe composition and functions of the sub system.

5.3.3.3 It shall give an overview of hardware and software, give main technical data and interfaces and outline the structure of associated documentation.

5.3.3.4 Cross-reference to applicable Equipment Manuals shall be included.

5.3.4 Operational System Description 5.3.4.1 Content shall be an extract from above, adapted to software specialists.

document.docx of 68


5.3.5 System Operator's Manual5.3.5.1 This manual shall give a detailed description of all system operation

functions, including input actions and error responses.

5.3.6 User’s Manual5.3.6.1 This manual shall give a detailed description of all functions seen from

the user’s working position.

5.3.7 Maintenance Manual5.3.7.1 Full descriptions of how to maintain the system in a preventive and

corrective manner shall be included.

5.3.7.2 The preventive maintenance part shall include a preventive maintenance checklist and guidelines on how to verify performance.

5.3.7.3 The corrective maintenance part shall include full details on the following subjects:

5.3.7.3.1 evaluation of system error messages;

5.3.7.3.2 error messages and alarms, with reference to applicable test unit;

5.3.7.3.3 methods for trouble shooting to board level;

5.3.7.3.4 required tools and instruments referenced to applicable maintenance task;

5.3.7.3.5 operational and technical fault reporting system manuals.

5.3.7.4 The maintenance manual shall contain a functional description of implemented hardware functions for the support of maintenance.

5.3.7.5 The documentation shall include functional block diagrams and fault tracing trees.

5.3.7.6 Applicable cabling information shall exist.

5.3.8 Installation Manual5.3.8.1 The Installation Manual shall include full details on the physical

installation, including drawings and diagrams for external connections and system's internal interconnection..

5.3.9 Equipment Manual5.3.9.1 The Equipment Manual shall give full details of the sub system or unit on

the following subjects as a minimum:

5.3.9.1.1 general description;

5.3.9.1.2 complete block diagrams;

5.3.9.1.3 complete logical diagrams;

document.docx of 68


5.3.9.1.4 mechanical and electrical data;

5.3.9.1.5 interface data;

5.3.9.1.6 configurations and parameter/switch settings.

5.3.10 Subcontractor's Manuals5.3.10.1 The documentation for system peripherals, like disk drives, magnetic

recording equipment, visual display terminals, printers etc., shall be delivered in the English language.

6. QUALITY AND SAFETY ASSURANCE

6.1 General Requirements

6.1.1 Quality System Requirements6.1.1.1 To prevent nonconformity at all stages of the project, every supplier of

equipment for LGS systems shall have established a quality system in accordance with the requirements in the document: STANDARD ISO 9000 SERIES (the latest version available).

6.1.1.2 All paragraphs in STANDARD ISO 9000 series shall be considered relevant for the Contract situation resulting from this R&S.

6.1.1.3 If the Supplier uses a standard other than stated above compliance with it shall be stated in the compliance table and a correspondence with the ISO 9000 series latest standards shall be stated.

6.1.1.4 All of the offered equipment shall be produced in accordance with the European Union Directives to obtain the CE symbol (including the standards for electromagnetic compliance (EMC) as well as the safety regulations, which ensure the protection of personnel and equipment).

6.1.2 Rights Reserved by LGS6.1.2.1 The LGS reserves the following rights as a supplement to the

requirements of STANDARD ISO 9000 series:

6.1.2.1.1 Verification of Purchased Product. The Buyer right to verification shall be included in the Contract.

6.1.2.1.2 Nonconformity Review and Disposition. The Buyer right to determine the use of nonconformity products shall be included in the Contract.

document.docx of 68


6.1.3 Suppliers Response to Quality Requirements6.1.3.1 The Supplier shall state their conformity with the above quality system

requirements.

6.1.3.2 To enable the Buyer to evaluate the Suppliers quality assurance conformity, the following points shall be fully described:

6.1.3.2.1 inspection of Sub-Suppliers (hardware and software);

6.1.3.2.2 quality inspection reports;

6.1.3.2.3 handling of non-conforming equipment;

6.1.3.2.4 the structure and production methods of hardware and software documentation including updating and other relevant rules referred to in this matter.

6.1.3.3 The Supplier shall describe and document the internal Quality Assurance (QA) organization. Areas of responsibilities shall be given and relevant names of QA managers shall be mentioned.

6.1.3.4 The way of reporting in the QA organization shall be detailed and contents of QA reports shall be identified.

6.2 Quality Control and Verification

6.2.1 Introduction6.2.1.1 Although the objective of the prescribed quality system is to prevent

nonconformity to materialize, verification shall be an important activity.

6.2.1.2 The verification activities shall be an on-going process that extends from the conception of the system up to and including its acceptance by the Buyer.

6.2.1.3 The verification process shall include design reviews, inspections, and relevant tests. As the realization of the system progresses, tests shall be performed at increasingly higher levels of items. Test procedures shall be worked out for assemblies, units, sub-systems and the complete system under the Contract.

document.docx of 68


6.2.2 Design Reviews6.2.2.1 Design reviews shall be held at appropriate points in the design and

development phase in order to verify compliance with the requirements in the Product Specification.

6.2.2.2 Completion of the design reviews shall result in the release of preliminary acceptance test procedures.

6.2.2.3 Design reviews shall be performed by the Suppliers own organization.

6.2.2.4 Preliminary acceptance test procedures shall be made available to the Buyer.

6.2.3 Quality Inspection6.2.3.1 Suppliers Inspection

6.2.3.1.1 The Supplier shall have the full responsibility for a proper and thorough supervision of the manufacturing process.

6.2.3.2 Inspections by the LGS.

6.2.3.2.1 The Supplier shall have full responsibility for quality of the equipment under the Contract even if the Buyer has made use of his right to verify the manufacturing process through inspection activities.

6.2.3.2.2 The Buyer's representative shall be given complete insight in the Supplier's and any Sub-Supplier's manufacturing and QA activities.

6.2.3.2.3 Should the Buyer's representative so wish, he shall be entitled to carry out his own verification tests and reviews. In such cases he shall be given full assistance from the Supplier's staff.

6.2.3.2.4 All approvals shall be in written form and signed by the Buyer's Project Manager or his authorised representative.

6.2.4 Testing (General)6.2.4.1 Introduction

6.2.4.1.1 A description of the Buyer's testing requirements is given here. It contains the Buyer's test objectives, describes categories of tests to be conducted and sets out documentation requirements. A formal stability verification test before commissioning of the contracted equipment is part of the Buyer's requirements.

6.2.4.2 Objectives

6.2.4.2.1 The objective of the Buyer's testing requirements is a full verification that the system, when completed and installed on site, meets the contractual specifications, as laid down in the Specification.

6.2.4.3 Categories of Test

6.2.4.3.1 Tests are divided into two categories, namely production tests and acceptance tests. Production tests shall be performed by the Supplier in order to verify compliance to specifications of items at lower levels.

document.docx of 68


6.2.4.3.2 Acceptance tests shall be performed by the Supplier in order to verify compliance to specifications of items at lower levels.

6.2.4.3.3 Acceptance tests shall be performed on items at sub-system level and higher, in order to demonstrate that the item concerned meets the specified functional performance.

6.2.4.3.4 The Buyer shall be prepared to accept such tests being applied to units if the performance or capabilities of such units cannot be demonstrated properly under higher level tests, or if testing of units will give a better verification of compliance.

6.2.4.3.5 Acceptance tests are of vital significance for the Buyer. Every acceptance test shall be performed in the presence of the Buyer, who will sign the acceptance documentation upon successful completion of the tests.

6.2.4.3.6 Acceptance tests shall be further divided into Factory Acceptance Tests (FAT) and Site Acceptance Tests (SAT).

6.2.4.3.7 The major goal of FAT is to prove to the Buyer that System has the most of the functions required and those functions work according to Buyer’s requirements.

6.2.4.3.8 The major goal of SAT is to prove to the Buyer that System is adopted to specific Buyer’s requirements, is fitted into the Buyer’s infrastructure and is able to interact with other systems belonging to the Buyer.

6.2.5 Acceptance Tests, Definitions and Reference Points

6.2.5.1 Factory Acceptance Test (FAT)

6.2.5.1.1 Before the actual Factory Acceptance test a full-scale internal preliminary test shall be arranged according to the specification. The Buyer reserves the right to attend this test as an observer. The Supplier shall notice in due time the start of this preliminary test, however not later than one month in advance.

6.2.5.1.2 FAT is a test in the Supplier's facilities, which is conducted in accordance with the agreed FAT specification. The Buyer should be entitled to witness the test and shall be notified about the FAT in due time

6.2.5.2 Site Acceptance Test (SAT)

6.2.5.2.1 A test at the Buyer's premises which is conducted in accordance with the agreed SAT specification. The Buyer shall witness the test and will sign the test protocol upon successful completion of the test. The Buyer shall be notified in due time.

6.2.6 Factory Acceptance Test (FAT)6.2.6.1 FAT Documentation

6.2.6.1.1 A selection of the required documentation should be approved by the Buyer, as indicated below. Upon approval by the Buyer these documents shall be binding on both parties. The following documentation is relevant for the FAT:

document.docx of 68


6.2.6.1.1.1 TEST PLAN, which shall contain the general conditions and definitions, a test work flow which defines the test sequence and identifies the related test specifications and test procedures, and a general description of the tests.

6.2.6.1.1.1.1 The Test Plan shall be worked out by the Supplier and shall be made available for the Buyer for review and approval latest two months prior to the expected start of the FAT.

6.2.6.1.1.2 TEST SPECIFICATION, which shall include detailed descriptions of the various tests and also include criteria for acceptance/rejection, conditions and interfaces. In addition, requirements for test provisions such as test tools, test equipment and test software shall be included.

6.2.6.1.1.2.1 The Test Specification shall be worked out by the Supplier and sent, together with the Test Plan, to the Buyer for review latest two months prior to the expected start of the FAT.

6.2.6.1.1.2.2 The Buyer shall be allowed one month for his evaluation and supplemental proposals for a final version of the Test Plan and the Test Specification.

6.2.6.1.1.2.3 These documents shall mutually be agreed upon at the latest one month before the start of the FAT.

6.2.6.1.1.3 TEST PROCEDURE, which shall describe the tests step by step and include detailed instructions for the test set-up, the use of test tools and test equipment, execution of the tests, and the interpretation and recording of the tests results.

6.2.6.1.1.3.1 The complete test environment shall be described, including simulated interfaces, test software and predefined inputs.

6.2.6.1.1.3.2 The Test Procedure shall be worked out by the Supplier and sent to the Buyer for review three weeks prior to the expected start of the FAT.

6.2.6.1.1.3.3 The Buyer shall be allowed two weeks for his evaluation and supplemental proposals for a final version of the Test Procedure.

6.2.6.1.1.3.4 The Test Procedure shall mutually be approved at the latest 2 weeks before the actual start of the FAT.

6.2.6.1.1.4 PRELIMINARY TEST REPORT, which shall include complete results from the Supplier's internal factory installation and factory test report, as well as full details from the Supplier's own pre- FAT evaluation.

6.2.6.1.1.5 TEST RECORD, which shall be worked out for the recording of test results. The test record shall be in accordance with the agreed test procedure. The Test Record forms shall be agreed upon before commencing the FAT.

6.2.6.1.1.6 CERTIFICATION RECORD, which shall indicate the type of test, the items tested and test result, including possible remarks.

6.2.6.1.1.6.1 After completion of each acceptance test an equipment certification record shall be filled in.

6.2.6.1.1.6.2 Remarks may include agreed deviations from the test procedure. The Certification Record shall be the formal document for recording of approval of the relevant test. Both the Buyer and the Supplier shall sign the Certification Record.

document.docx of 68


6.2.6.1.1.7 LIST OF DELIVERY. The list of delivery shall contain information about the configuration of the equipment down to sub-assembly level.

6.2.6.2 Notifications to the LGS

6.2.1 Ten working days prior to the start of the FAT the Buyer shall be informed about the date of FAT. Should the Buyer decide that he does not wish to observe the FAT, The FAT shall be conducted normally and monitored by the Supplier's QA responsible.

6.2.2 The Supplier should assist The Buyer with travelling, accommodation, local transport for LGS representatives (6 persons) if the Buyer does wish to observe the FAT.

6.2.2.1 FAT Execution

6.2.2.1.1 The Supplier should accomplish the agreed Factory Acceptance Test (FAT) program in the presence of the Buyer's appointed representatives.

6.2.2.1.2 The FAT shall be run to verify whether the system, before delivery, satisfies the functional requirements and technical specifications defined in the Contract.

6.2.2.1.3 It is accepted that factory acceptance tests are performed under the environmental conditions that prevail in the Supplier's test department at the time of the test.

6.2.2.1.4 Before starting the formal FAT, the Supplier shall present for the Buyer the complete Preliminary test Report. The highlights of the Preliminary test Report shall be pinpointed by the Supplier's representative before the start of the FAT.

6.2.2.1.5 The FAT shall be performed following the Test Plan and the Test Procedure, successively checking the items for compliance with the Test Specification.

6.2.2.1.6 The Suppliers shall provide all instruments, equipment, materials, facilities and services required for an appropriate realisation of the FAT.

6.2.2.1.7 During the FAT the Test Record shall be completed. The configuration of the equipment during the FAT shall correspond to the one requested by the Buyer.

6.2.2.1.8 Should problems arise during the FAT or should the FAT test results be deemed unsatisfactory in any major way by the Buyer, the problems shall be corrected and the status shall be mutually verified and agreed. The Supplier shall take full economic responsibility for any required re-testing program.

6.2.2.2 FAT Verification

6.2.2.2.1 The following set of documentation should be handed over to the Buyer as evidence of a successfully completed FAT:

6.2.2.2.1.1 the Certification Record, signed by the Buyer or their representatives upon completion of the test,

6.2.2.2.1.2 the set of completed Test Records,

6.2.2.2.1.3 the List of Delivery

document.docx of 68


6.2.2.2.2 These Factory Acceptance Test documents, properly signed by the Supplier, shall imply that the equipment is accepted by the Buyer for delivery to the site.

document.docx of 68


6.2.3 Site Acceptance Test (SAT)6.2.3.1 SAT Documentation

6.2.3.1.1 A selection of the required documentation shall be approved by the Buyer, as indicated below. Upon approval by the Buyer these documents shall be binding on both parties. The following documentation is relevant for the SAT:

6.2.3.1.1.1 TEST PLAN, which shall contain the general conditions and definitions, a test work flow which defines the test sequence and identifies the related test specifications and test procedures, and a general description of the tests.

6.2.3.1.1.1.1 The Test Plan shall be worked out by the Supplier and shall be made available for the Buyer for review and approval latest one month prior to the expected start of the SAT or after completion of the FAT, whichever is the latest.

6.2.3.1.1.2 TEST SPECIFICATION, which shall include detailed descriptions of the various tests and also include criteria for acceptance/rejection, conditions and interfaces.In addition, requirements for test provisions such as test tools, test equipment and test software shall be included.

6.2.3.1.1.2.1 The Test Specification shall be worked out by the Supplier and sent, together with the Test Plan, to the Buyer for review latest three weeks prior to the expected start of the SAT or after completion of the FAT, whichever is the latest.

6.2.3.1.1.2.2 The Buyer shall be allowed two weeks for his evaluation and supplemental proposals for a final version of the Test Plan and the Test Specification.

6.2.3.1.1.2.3 These documents shall mutually be agreed upon not later than one week before the start of the SAT.

6.2.3.1.1.3 TEST PROCEDURE, which shall describe the tests step by step and include detailed instructions for the test set-up, the use of test tools and test equipment, execution of the tests, and the interpretation and recording of the tests results.

6.2.3.1.1.3.1 The complete test environment shall be described, including simulated interfaces, test software and predefined inputs/outputs.

6.2.3.1.1.3.2 The Test Procedure shall be worked out by the Supplier and sent to the Buyer for review not later than three weeks prior to the expected start of the SAT.

6.2.3.1.1.3.3 The Buyer shall be allowed two weeks for his evaluation and supplemental proposals for a final version of the Test Procedure.

6.2.3.1.1.3.4 The Test Procedure shall mutually be approved not later than one week before the actual start of the SAT.

6.2.3.1.1.3.5 As the SAT shall include a number of live trials, the Buyer is prepared to provide for the environment for such trials like live test targets and operational staff to perform specified actions.

6.2.3.1.1.4 PRELIMINARY TEST REPORT, which shall include complete results from the Supplier's testing activities during the Setting- Up phase and the conclusions from the Supplier's evaluation of this phase.

document.docx of 68


6.2.3.1.1.5 TEST RECORD, which shall be worked out for the recording of test results. The test record shall be in accordance with the agreed test procedure.

6.2.3.1.1.5.1 The Test Record forms shall be agreed upon before commencing the SAT.

6.2.3.1.1.6 CERTIFICATION RECORD, which shall indicate the type of test, the item tested and the test result, including possible remarks.

6.2.3.1.1.6.1 After completion of each acceptance test, an equipment certification record shall be filled in.

6.2.3.1.1.6.2 Remarks may include agreed deviations from the test procedure. The Certification Record shall be the formal document for recording the approval of the relevant test. Both the Buyer and the Supplier shall sign the Certification Record.

6.2.3.1.1.7 LIST OF DELIVERY. The list of delivery shall contain information about the configuration of the equipment down to sub-assembly level.

6.2.3.2 Agreement on the SAT Starting Date

6.2.3.2.1 One week prior to the expected start of the SAT the Buyer and the Supplier shall mutually agree upon a fixed starting date and duration of the SAT.

6.2.3.3 SAT Execution

6.2.3.3.1 The objective of the Site Acceptance Test is to confirm that the system, after installation on site, is compliant with all the specifications set out in the Contract and detailed in its Annexes.

6.2.3.3.2 A complete Site Acceptance Test shall include verification of all items delivered in accordance with the Supplier including training, documentation and quality of workmanship.

6.2.3.3.3 The Site Acceptance Tests will be performed under the environmental conditions that will exist under normal operation for the equipment contracted.

6.2.3.3.4 It shall be the responsibility of the Supplier to provide required documentation, test equipment, measuring instruments, tools etc. prior to the start of the SAT.

6.2.3.3.5 Before the start of the formal SAT the Supplier shall present his Preliminary test Report to the Buyer. This documentation shall contain full details of the Suppliers evaluation of the test results achieved during Setting Up.

6.2.3.3.6 The SAT shall be performed following the Test Plan and the Test Procedure, successively checking the items for compliance with the Test Specification.

6.2.3.3.7 Equipment under SAT shall consist of the complete system in accordance with the Contract.

6.2.3.3.8 The final phase of the SAT shall include a long term STABILITY TEST, lasting for minimum 3 days, during which the system shall run under continuous relevant operation without any signs of anomalous function. The procedures of the stability test and the criteria and conditions to be granted acceptance shall be mutually agreed.

6.2.3.3.9 During the SAT the Test Record shall be completed. Every recording, listing, print-out etc, created during the SAT shall be added to the test report as

document.docx of 68


evidence. The configuration of the equipment, as it is during the SAT shall be laid down in the List of Delivery.

6.2.3.3.10 Should problems arise during the SAT or should the SAT test results be deemed unsatisfactory in any major way by the Buyer, the problems shall be corrected and the status shall be mutually verified and agreed.

6.2.3.4 Verification

6.2.3.4.1 The following set of documentation shall be handed over to the Buyer as evidence of a successfully completed SAT:

6.2.3.4.1.1 the certification record, signed by the Buyer or their representative upon completion of the test,

6.2.3.4.1.2 the set of completed test records,

6.2.3.4.1.3 all recordings,

6.2.3.4.1.4 the list of delivery

document.docx of 68


7. TRAINING

7.1 Introduction7.1.1 This chapter covers the requirements for operational and technical training to enable correct use, operation and maintenance of the whole Contracted system.

7.1.2 Training documentation requirements are included here.

7.1.3 Detailed training programs for the operational and technical staff shall be negotiated

7.2 General7.2.1 To ensure efficient training, it is essential that a high standard of documentation is provided.

7.2.2 The documentation shall be in the English or Latvian language, provide all information required, and be presented in a clear, and concise format.

7.2.3 All training courses shall:7.2.3.1 be conducted in the English or Latvian language;

7.2.3.2 involve theoretical and practical training;

7.2.3.3 provide simulation of faults;

7.2.3.4 use documentation provided for the Contracted system.

7.2.4 After training course the Supplier shall give a document (Certificate) which confirms training completion.

7.2.5 The Certificate shall allow the Student to train other LGS personnel.

7.2.6 The Supplier shall be responsible for providing a suitable number of competent instructors fully capable of providing training to a standard acceptable to LGS.

7.3 Training Documentation7.3.1 In case final training documentation is not available at the beginning of the training, preliminary versions of both the information and instructional documents shall be provided.

7.3.2 Descriptions and detailed data included in the documentation shall comply with the characteristics of the delivered ImRoS as closely as possible. Any advertising or sales promoting material shall not be included in the training material.

7.3.3 The Supplier shall:7.3.3.1 deliver to the Buyer detailed course programs and documentation at least

2 weeks before the beginning of the course;

7.3.3.2 provide each participant with a complete set of course material at the beginning of the course;

7.3.3.3 at the end of the course deliver a complete set of instructor's training material (transparences, films, video tapes etc.) to the Buyer.

document.docx of 68


7.4 Training Facilities and Equipment7.4.1 When training takes place at the Supplier´s factory/training center suitable classrooms and laboratory facilities shall be provided.

7.4.2 All test equipment used under training shall be of the same kind as Contracted. Maintenance of training test equipment is the Supplier´s responsibility.

7.5 Training of Technical Personnel7.5.1 Under the Contract, system-related training shall be provided for technical personnel and system engineers.

7.5.2 The Supplier shall provide the training after the project has been defined and documented in the Product Specification and prior to, but as close as possible to the FAT starting date

7.5.3 The training course shall include:

7.5.3.1 detailed system hardware course;

7.5.3.2 system operating course;

7.5.3.3 installation, maintenance and technical parameter changes.

7.6 Training Aims of the Course for Technical Personnel 7.6.1 This course shall prepare the technical personnel to handle and maintain the ImRoS on technical matters.

7.6.2 At the completion of the course each participant shall have:

7.6.2.1 clear overview of the complete system;

7.6.2.2 a sound understanding of individual sub-systems;

7.6.2.3 knowledge of the functional design and operation of the system down to board level;

7.6.2.4 detailed knowledge of operational functions, input functions and their results, etc. enabling the operation of all sub-systems and work station equipment;

7.6.2.5 detailed knowledge of how to perform preventive and corrective maintenance.

7.6.3 This shall include to:

7.6.3.1 check performance parameters;

7.6.3.2 interpret fault conditions;

7.6.3.3 select and apply maintenance aids such as fault finding procedures, test programs, control and monitoring test equipment;

7.6.3.4 carry out adjustments allowable for maintenance personnel;

7.6.3.5 perform necessary restoration of service.

document.docx of 68


7.7 Training of Operational Personnel 7.7.1 Under the Contract, system-related training for operational personnel shall be provided.

7.7.2 The Supplier shall provide the training after the project has been defined and documented in the Product Specification and prior to, but as close as possible to the FAT starting date

7.7.3 The training course shall include:

7.7.3.1 general course on system hardware;

7.7.3.2 detailed course on rules of the system operating;

7.7.3.3 documentation on the system operation.

7.8 Training Aims of the Course for Operational Personnel 7.8.1 This course shall give users the operational knowledge about the system. The course shall prepare the participants to give operational courses for others.

7.8.2 At the completion of the course each participant shall have:

7.8.2.1 clear overview of the system;

7.8.2.2 knowledge of the functional design and operation of the system;

7.8.2.3 detailed knowledge of operational functions, input functions and their results, etc. enabling to operate the work station equipment in accordance with the designer's requirements.

7.8.3 This shall include to:

7.8.3.1 carry out all the functional operations envisaged by the specifications;

7.8.3.2 select any configuration of the system and to be able to accomplish reconfiguration of the system;

7.8.3.3 to operate the work station equipment in accordance with the designer's requirements.

7.9 Proposal from the Supplier7.9.1 The Supplier shall, based on the guidelines given above, compose an adapted technical training course program.

7.9.2 Each course shall have a description, duration, location and an allowed maximum number of participants.

7.9.3 The Supplier shall state the price for each of the courses in his proposal which shall also form a part of the Contract.

7.9.4 The Supplier should assist The Buyer with travelling, accommodation, local transport for LGS representatives (6 persons) during Training.

document.docx of 68


8. STATEMENT OF COMPLIANCE

8.1 General8.1.1 The Supplier shall state compliance in accordance with Statement of Compliance Tables. The Supplier shall prepare Statement of Compliance Tables for the complete specification.

8.2 Statement Table8.2.1 The Statement of Compliance Table shall contain a reference to each paragraph in the Chapters mentioned. In general, the reference is made to paragraphs as they occur in the specification.

8.2.2 Many of the paragraphs contain several requirements. The statement given shall cover all the requirements referred to in the actual paragraph, unless otherwise stated.

8.3 Format8.3.1 The Statement of Compliance Tables shall consist of five (5) fields. The first field (R&S) are used in defining the number of specification.

8.3.2 CS, Compliance Statement - the Supplier shall state his compliance using one of the following alternatives in the second field:

8.3.2.1 OC, Over Compliant - the item exceeds the specified requirement.

8.3.2.2 FC, Fully Compliant - complete compliance with the specified requirements.

8.3.2.3 PC, Partly Compliant - the item is functionally compliant. Deviations from the specifications are clearly shown in the Documents.

8.3.2.4 NC, Not Compliant - the item is not compliant with the specified requirement

8.3.3 In the third field, PS (Present State) the Supplier shall declare the status of the referred facility using one of the following alternatives:

8.3.3.1 SF, Standard Facility - the referred facility has already been developed and fulfils the requirement without any modification;

8.3.3.2 AR, Standard Facility but Adaptation Required - the referred facility has already been developed, but adaptation is needed to obtain complete compliance with the specified requirement;

8.3.3.3 DR, Development Required - the referred facility will be new design, not developed at the present time. A concept of the required development shall be enclosed.

8.3.4 RM, Remarks - the fourth field shall be used for remarks and clarifications to the referred paragraph.

8.3.5 The fifth field shall contain the reference number to the RFP.

document.docx of 68


9. PROJECT MANAGEMENT

9.1 Introduction9.1.1 The Supplier shall implement a formal project organization, which plans, organizes, conducts and manages the activities required by the Project.

9.1.2 The Supplier shall include a Project Management System Description, which details the Supplier's interpretation and approach to ImRoS management requirements.

9.2 Contractor’s representative9.2.1 The Supplier shall appoint a Contractor’s Representative who is responsible for the successful performance of all aspects of project management on ImRoS, including any subcontractor's activities.

9.2.2 The Supplier shall include a statement of the authority and assigned responsibility of the Contractor’s Representative.

9.2.3 The Supplier shall provide the name of the Contractor’s Representative and describe his/her qualifications, background and experience to show how he/she qualifies to be the manager for ImRoS project.

9.3 Supplier’s Project Organization9.3.1 The Supplier shall describe in detail in the Project Management System Description the internal organization related to ImRoS Project. Full functional and administrative project organization structure shall be presented, including relevant names of personnel.

9.4 Project Management Plans9.4.1 The Supplier shall control the project regarding activities covered or influenced by the Contract by means of project management plans.

9.4.2 The project management plans should be presented to the Buyer as tree charts, flow charts, network plans, bar charts and work breakdown structures as considered appropriate by the Supplier.

9.4.3 The following information shall be included in the Supplier's project management plans presented in the Documents:

9.4.3.1 main time schedule incorporating the entire ImRoS Project,

9.4.3.2 detailed time schedules of the progress of the Work of the sub-systems of ImRoS Project,

9.4.3.3 significant progress milestones of the Work,

9.4.3.4 dates of major actions and decisions to be taken both by the LGS and the Supplier.

document.docx of 68


9.5 Progress Meetings9.5.1 The Supplier shall be prepared to arrange progress meetings for general monitoring of the progress of the project activities. The progress meetings form a formal contact forum between the Supplier and the Buyer.

9.5.2 Progress meetings shall be held regularly from the date of Contract signing.

9.5.3 The following persons shall be present at the Project Meetings:

9.5.3.1 Contractor’s Representative,

9.5.3.2 Buyer's representatives,

9.5.3.3 other persons considered necessary either by the Supplier or the Buyer.

9.5.4 The following information shall be presented at the Project Meetings:

9.5.4.1 - work accomplished after the previous project meeting,

9.5.4.2 - progress planned to take place during the period before the next progress meeting,

9.5.4.3 - actions to be taken either by the Supplier or the Buyer before the next project meeting,

9.5.4.4 - possible time schedule adjustments,

9.5.4.5 - other items considered appropriate by the Supplier or the Buyer.

9.5.5 Updated reports of the progress of the Work shall be prepared by the Supplier and be available at the Buyer's organization at least five working days before each progress meeting. The progress report shall include an updated version of the Supplier's time schedule.

9.5.6 A proposal for the progress meeting agenda shall be prepared by the Supplier and be available at the Buyer's organization at least five working days before the progress meeting.

9.5.7 The Supplier shall prepare minutes from each progress meeting. Minutes of the meetings shall be mutually approved and a draft minute shall be forwarded to the representatives of the Buyer at the end of each meeting.

9.5.8 The official minutes of the progress meetings shall be available in the Buyer's organization five working days after each progress meeting at the latest.

9.5.9 Progress reports, agenda proposals and the minutes of the latest held progress meeting as well as other possible correspondence related to the activities described in this Chapter shall be addressed to the LGS Project Implementation Unit.

9.5.10 In addition to the documents mentioned above, the Supplier shall issue a monthly report describing the general progress of the Work.

document.docx of 68


9.6 Buyer’s Project Organization9.6.1 Buyer's project organization shall be arranged administratively as Projects Organization of the LGS.

9.6.2 The LGS Project Implementation Unit of the Projects Organization shall be the main contact towards the Buyer in all matters related to ImRoS Project.

document.docx of 68


10. HARDWARE AND SOFTWARE REQUIREMENTS

10.1 General 10.1.1 In case if it is not specially defined in the current document or its attachments, the Supplier should provide the hardware and software, which fulfils the following requirements:

10.2 Software Requirements10.2.1 System-level software for servers of ImRoS part shall be one of the commercially available multi-tasking, multi-user Operating System (OS). One of the OS UNIX™ versions or their clones (such as Linux), which supports Intel® hardware platform are preferred, however Microsoft® Windows™ Server 2008 or later version will be considered as a suitable OS

10.2.2 System-level software for Working Positions of ImRoS part shall be one of the commercially available multi-tasking, multi-user Operating System (OS). Microsoft® Windows™ 7 or later version is preferred, however OS UNIX™ versions or their clones (such as Linux), which supports Intel® hardware platform will be considered as a suitable OS.

10.2.3 In case of proposing the Web-Application it should be possible to run it on the devices supporting:

10.2.3.1 Microsoft Windows v7 or later;

10.2.3.2 Apple iOS v5 or later;

10.2.3.3 Google Android v4 or later;

10.2.4 Off-the-shelf (COTS) database software shall be provided for servers.

10.3 Hardware Requirements10.3.1 Off-the-shelf (COTS) equipment shall be provided for server and workstations equipment. Solutions, based on Intel® Pentium™ platform (Dell, HP) are preferred.

10.3.2 The server and communication equipment should reside in standard 19” rack (the dimension should be at least: 2000mm height, 600mm width, 1000mm depth). Rack shall be equipped with rack-mounted console including LCD monitor, keyboard and mouse.

10.3.3 All the server equipment, including computers, display, keyboard, etc., should be rack-mounted.

10.3.4 The server should have the configuration, not worse that:

10.3.4.1 Server Construction: shall be placed into Customer’s HP c7000 blade server chassis;

10.3.4.2 Processors: 2 (two) eight-core x86 64bit architectures processors with minimum 2.0 Ghz frequency, 16Mb cache memory, not more than 100W TDP;

10.3.4.3 RAM: 48GB RAM DDR3 12800 Registered, proposed system shall operates with 1600 Mhz speed;

document.docx of 68


10.3.4.4 HDD: 2 (two) 146GB 15k RPM 6G SAS Hot Plug disks RAID-1 configuration;

10.3.4.5 External interfaces: 2 (two) 10Gb Ethernet connections, with automated recognition of 10G/1G Ethernet for each port, and Virtual Connect Flex-10 functionality together with Customer’s Virtual Connect FlexFabric 10Gb/24-port modules;

10.3.4.6 Operational System compatibility and Vendor Support: Servers and their components shall be compatible with Microsoft Windows Server 2008, 2008 R2, 2012; VMware vSphere 4.x, 5.x, Bidder shall provide URL references to Vendor website;

10.3.4.7 Other requirements: Servers and components shall be new and not used before; server shall be fully configured at factory.

10.3.4.8 Hardware Warranty: 36 month warranty with 4 hours reaction time from the Vendor side in case of problems, 24 hours x 7 day a week, with technician’s availability.

10.3.4.9 Each Server shall be supplied with the following software licenses:

10.3.4.9.1 Veeam Backup & Replication Enterprise for VMware – 2 licenses;

10.3.4.9.2 VMware vSphere 5 Enterprise for 1 processor - 2 licenses;

10.3.4.9.3 Basic Support/Subscription for VMware vSphere 5 Enterprise for 1 processor for 2 years - 2 licenses.

10.3.5 Additional components, like multi-port serial interfaces, magneto optical or tape storage device for long-term data archiving or DVD/CD-writer, modems, etc., shall be provided.

10.3.6 In case of several servers and by request of the Buyer, it should be necessary to provide an Off-the-shelf (COTS) KVM switch with correspondent number of KVM ports.

10.3.7 The CWP should have the configuration, not worse that:

10.3.7.1 Processor: X86 architect with min. 2550 point benchmark by PassMark CPU test (http://www.cpubenchmark.net) with possibility extend for 2 processors;

10.3.7.2 Memory: At least 4 GB DDR3 expandable till 8 GB;

10.3.7.3 160 GB HDD (PATA/SATA or SCSI interface), SSD disks are preferable;

10.3.7.4 DVD drive (PATA/SATA or SCSI interface);

10.3.7.5 Network Interface Card(s), Ethernet 10/100/1000 Base-T with RJ-45 socket;

10.3.7.6 Video card, which supports resolution of 1920x1080 min

10.3.7.7 At least 24” LCD display. The other displays could have other parameters, but not worse than described above.

10.3.7.8 Additional components, like multi-port serial interfaces, magneto optical storage device for long-term data archiving or DVD/CD-writer, modems, etc., shall be provided as necessary.

document.docx of 68

http://www.cpubenchmark.net/


10.3.8 Every workstation shall be equipped with all necessary power cables, communication cables, input\output devices (mouse/trackball, keyboard, etc.).

10.3.9 Sufficient number of short-range modems shall be provided for the systems, which requires serial asynchronous connection.

10.3.10 The system should be equipped with one or more network packet switch to allow network communication between system components (servers, workstations) and external equipment.

10.3.11 Network switches should allow connection of the equipment by means of 1000BaseT Category 6 twisted pair cabling or higher.

document.docx of 68


Annex 1. SHIFT PATTERNS

Standard Pattern

Pattern A – Standard 8-hours shift Maximum number of persons Month dates / Shifts

1 2 3 4 5 6 7 8 9 10 11

12 13 14

15 16 17

18 19 20

21 22

23 24 25

26 27 28

29 30 31

Total

1 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 1842 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 1843 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 1844 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 1845 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 1846 A A A A A 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 1447 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 A A A A A A A A A A 1208 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 1849 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 18410

AK AK AK AK AK AK AK AK AK

AK AK AK AK AK AK AK AK AK AK AK AK AK AK AK AK AK AK AK AK AK AK 0

8 – day shift: from 08:30 till 17:00, duration 8 hours, lunch - 30 min (responsibility of the person)A – vacation:K – Business trip: SA – Sick Leave (Type A)SB – Sick Leave (Type B)BD – Day off (saving salary)AB – Day off (without salary)A – VacationAP – Additional Vacation (saving salary)AK – Maternity vacationAT – Paternity vacationAM – study vacationTR – Simulator trainingM - trainingE – language exam

document.docx of 68


AMGKCS Division

Pattern A – AMGKC controllers shifts

Maximum number of persons Month dates / Shifts1 2 3 4 5 6 7 8 9 10 11 1

213 1

415 16 1

718 1

920 2

122 23 2

425 2

627 28 2

930 3

1Total

1 D N D N D N D N D N D 1322 D N D N D N D N D N 1203 D N D N D N D N D N 1204 D N D N D N D N D N 1205 D N D N D N D N D N 1206 D N D N D N D N D N 120

Pattern B – AMGKC controllers shifts

Maximum number of persons Month dates / Shifts1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 Total

1 Dn Dn Dn Dn Dn Dn 1442 Dn Dn Dn Dn Dn 1203 Dn Dn Dn Dn Dn 1204 Dn Dn Dn Dn Dn 1205 Dn Dn Dn Dn Dn 1206 Dn Dn Dn Dn Dn 120

D – day shift: from 08:00 till 20:00, duration 12 hours, lunch - 30 min (included as working time) without leaving working position (responsibility of the person)N – night shift: from 20:00 till 08:00, duration 12 hours, break - 30 min (included as working time) without leaving working position (responsibility of the person)Dn – allday shift from 08:00 till 08:00, duration 24 hours, lunch - 30 min and breaks(included as working time) without leaving working position (responsibility of the person)

document.docx of 68


AIS Division

Pattern A – AIS NOTAM operators shifts

Month dates / Shifts1 2 3 4 5 6 7 8 9 10 1

112 1

314 1

516 17 1

819 2

021 2

223 24 2

526 2

728 2

930 3

1Total

1 D D D D D D D D D D D D D D D D 1762 D D D D D D D D D D D D D D D 165

D – day shift: from 08:30 till 19:30, duration 11 hours, lunch - 30 min (included as working time) without leaving working position (responsibility of the person)

document.docx of 68


BRIEFING Division

Pattern A – Briefing Officers shifts

Minimum number of persons Month dates / Shifts1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 Total

1 Dn R Dn R Dn R Dn R Dn R Dn 1782 R Dn R Dn R Dn R Dn R Dn R 1633 Dn R Dn R Dn R Dn R Dn R 1554 R Dn R Dn R Dn R Dn R Dn 1555 R Dn R Dn R Dn R Dn R Dn 1556 R Dn R Dn R Dn R Dn R Dn 1557 D D D D D D D D D D D D D D D D 1928 D D D D D D D D D D D D D D D 180

Pattern B – Briefing Officers shifts


1 Dn R Dn R Dn R Dn R Dn R Dn 1782 R Dn R Dn R Dn R Dn R Dn R 1633 Dn R Dn R Dn R Dn R Dn R 1554 R Dn R Dn R Dn R Dn R Dn 1555 R Dn R Dn R Dn R Dn R Dn 1556 R Dn R Dn R Dn R Dn R Dn 1557 D D D D D D D D D D D D D D D D 192

D – day shift: from 08:00 till 20:30, duration 12 hours, lunch - 30 min (responsibility of the person)R – day shift: from 08:30 till 17:00, duration 8 hours, break - 30 min (responsibility of the person)Dn – allday shift from 08:00 till 08:00, duration 23 hours, lunch - 30 min and break 30 min (responsibility of the person)

document.docx of 68


Pattern C – Briefing Officers shifts


1 Dn R Dn R Dn R Dn R Dn R Dn 1782 R Dn R Dn R Dn R Dn R Dn 1553 Dn R Dn R Dn R Dn R Dn R 1554 R Dn R Dn R Dn R Dn R Dn 1555 R Dn R Dn R Dn R Dn R Dn 1556 R Dn R Dn R Dn R Dn R Dn 155

Pattern D – Briefing Officers shifts


1 Dn R Dn R Dn R Dn R Dn R Dn R Dn 2092 R Dn R Dn R Dn R Dn R Dn R Dn R 1943 R Dn R Dn R Dn R Dn R Dn R Dn 1864 R Dn R Dn R Dn R Dn R Dn R Dn 1865 R Dn R Dn R Dn R Dn R Dn R Dn 186

D – day shift: from 08:00 till 20:30, duration 12 hours, lunch - 30 min (responsibility of the person)R – day shift: from 08:30 till 17:00, duration 8 hours, break - 30 min (responsibility of the person)Dn – allday shift from 08:00 till 08:00, duration 23 hours, lunch - 30 min and break 30 min (responsibility of the person)

document.docx of 68


Pattern E – Briefing Officers shifts

Major pattern Month dates / Shifts1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 1

819 20 21 22 23 24 25 26 2

728 29 30 31 Total

1 D N D N D N D N D N D N D 1562 D N D N D N D N D N D N D 1563 D N D N D N D N D N D N 1444 D N D N D N D N D N D N 1445 N D N D N D N D N D N D N 1566 N D N D N D N D N D N D N 1567 D N D N D N D N D N D N 1448 D N D N D N D N D N D N 1449 D N D N D N D N D N D N 144

10 D N D N D N D N D N D N 144

D – day shift: from 08:00 till 20:30, duration 12 hours, lunch - 30 min (responsibility of the person)N – night shift: from 20:30 till 08:00, duration 12 hours, break - 30 min (responsibility of the person)

document.docx of 68


FMFDU Division

Pattern A – FMFDU Officers shifts


1 D D D D D D D D D D D 1432 D D D D D D D D D D 1303 D D D D D D D D D D 130

Pattern B – FMFDU Officers shifts



D – day shift: from 07:20 till 20:20, duration 13 hours, break - 30 min (included as working time) without leaving working position (responsibility of the person)

document.docx of 68


Pattern C – FMP & FDA Officers shifts

Minimum number of persons Month dates / Shifts

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 1

8 19 20 21 22 23 24 25 2

6 27 28 29 30 31 Total

1 D N D N D N D N D N D N D 1562 D N D N D N D N D N D N 1443 D N D N D N D N D N D N 1444 D N D N D N D N D N D N 1445 N D N D N D N D N D N D N 156

Pattern D – FMP & FDA Officers shifts

Minimum number of persons Month dates / Shifts1 2 3 4 5 6 7 8 9 10 11 12 1

314 15 16 17 1

819 20 21 2

223 24 25 2

627 28 29 3

031 Total

1 D N D N D N D N D N D N D N D N 1922 D N D N D N D N D N D N D N D N 1923 D N D N D N D N D N D N D N D 1804 N D N D N D N D N D N D N D N 180

D – day shift: from 08:00 till 20:30, duration 12 hours, lunch - 30 min (responsibility of the person)N – night shift: from 20:00 till 08:30, duration 12 hours, break - 30 min (responsibility of the person)

document.docx of 68


Pattern E – FMP & FDA Officers shifts


1 Dn Dn Dn Dn Dn Dn Dn 1612 Dn Dn Dn Dn Dn Dn Dn 1613 Dn Dn Dn Dn Dn Dn 1384 Dn Dn Dn Dn Dn Dn 1385 Dn Dn Dn Dn Dn Dn 138

Pattern F – FMP & FDA Officers shifts


1 Dn Dn Dn Dn Dn Dn Dn Dn 1842 Dn Dn Dn Dn Dn Dn Dn Dn 1843 Dn Dn Dn Dn Dn Dn Dn Dn 1844 Dn Dn Dn Dn Dn Dn Dn 161

Dn – allday shift from 08:30 till 08:30, duration 23 hours, lunch - 30 min and break 30 min (responsibility of the person)

document.docx of 68


Pattern G – FMFDU Senior Officers shifts


1 D D D D D D D D D D D 1432 D D D D D D D D D D 1303 D D D D D D D D D D 130

Pattern H – FMFDU Senior Officers shifts



D – day shift: from 07:20 till 20:20, duration 13 hours, break - 30 min (included as working time) without leaving working position (responsibility of the person)

document.docx of 68


ATC Centre

Pattern A – ATC Operational Supervisors shifts

Minimum number of persons Month dates / Shifts1 2 3 4 5 6 7 8 9 10 11 1

213 1

415 1

617 1

819 2

021 2

223 2

425 2

627 2

829 3

031 Total

1 2 1 3 2 1 3 2 1 3 2 1 3 2 1 3 2 1 3 2 1542 2 1 3 2 1 3 2 1 3 2 1 3 2 1 3 2 1 3 1473 2 1 3 2 1 3 2 1 3 2 1 3 2 1 3 2 1 3 1474 3 2 1 3 2 1 3 2 1 3 2 1 3 2 1 3 2 1 3 157.55 1 3 2 1 3 2 1 3 2 1 3 2 1 3 2 1 3 2 1 154

2 – day shift: from 14:30 till 22:00, duration 7 hours, break - 30 min (responsibility of the person)1 – morning shift: from 07:30 till 15:00, duration 7 hours, break - 30 min (responsibility of the person)3 – night shift: from 21:30 till 08:00, duration 10 hours 30 min, break - 30 min (included as working time) (responsibility of the person)

Pattern B – ATC Operational Supervisors shifts


1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 1

8 19 20 21 22 23 24 25 2

6 27 28 29 30 31 Total

1 D N D N D N D N D N D N D N D N 1842 D N D N D N D N D N D N D N D N 1843 D N D N D N D N D N D N D N D 1724 N D N D N D N D N D N D N D N 173

D – day shift: from 08:00 till 20:00, duration 11 hours, lunch - 30 min, break – 30 min (responsibility of the person)N – night shift: from 20:00 till 08:00, duration 12 hours, break - 30 min (included as working time) (responsibility of the person)

document.docx of 68


Pattern C – ATC Controllers shifts (one controller per sector)


213 1

415 1

617 1

819 2

021 2

223 2

425 2

627 2

829 3

031 Total

1 2 1 3 2 1 3 2 1 3 2 1 3 2 1 3 2 1 3 2 1542 2 1 3 2 1 3 2 1 3 2 1 3 2 1 3 2 1 3 1473 2 1 3 2 1 3 2 1 3 2 1 3 2 1 3 2 1 3 1474 3 2 1 3 2 1 3 2 1 3 2 1 3 2 1 3 2 1 3 157.55 1 3 2 1 3 2 1 3 2 1 3 2 1 3 2 1 3 2 1 154


Pattern D – ATC Controllers shifts (two controllers per sector)


213 14 1

516 17 1

819 2

021 22 2

324 25 2

627 2

829 30 3

1Total

1 2 1 3 2 1 2 1 3 2 1 2 1 3 2 1 2 1 3 2 1 1542 2 1 3 2 1 2 1 3 2 1 2 1 3 2 1 2 1 3 2 1473 1 2 1 3 2 1 2 1 3 2 1 2 1 3 2 1 2 1 3 1474 2 1 2 1 3 2 1 2 1 3 2 1 2 1 3 2 1 2 1 3 1545 2 1 2 1 3 2 1 2 1 3 2 1 2 1 3 2 1 2 1 3 1546 2 1 2 1 3 2 1 2 1 3 2 1 2 1 3 2 1 2 1 1477 3 2 1 2 1 3 2 1 2 1 3 2 1 2 1 3 2 1 2 1478 1 3 2 1 2 1 3 2 1 2 1 3 2 1 2 1 3 2 1 147


document.docx of 68


Pattern E – ATC Controllers shifts (two controllers per sector)


1 2 1 3 2 1 3 D* D* 2 1 3 2 1 3 D* D* 2 1 3 156.52 2 1 3 D

*D* 2 1 3 2 1 3 D

*D* 2 1 3 2 1 146

3 2 1 3 2 1 3 D*

D* 2 1 3 2 1 3 D*

D* 2 139

4 3 2 1 3 D* D*

2 1 3 2 1 3 D* D*

2 1 3 142.5

5 D*

D* 2 1 3 2 1 3 D*

D* 2 1 3 2 1 3 D*

D* 149

6 D* D*

2 1 3 2 1 3 D* D*

2 1 3 2 1 3 D* 140.5

7 1 3 D* D* 2 1 3 2 1 3 D* D* 2 1 3 2 1 3 149


D* optional shifts:D1 – day shift: from 09:00 till 18:00, duration 8 hours 30 min, break - 30 min (responsibility of the person)D2 – day shift: from 10:00 till 19:00, duration 8 hours 30 min, break - 30 min (responsibility of the person)D3 – day shift: from 11:00 till 20:00, duration 8 hours 30 min, break - 30 min (responsibility of the person)

Pattern F – ATC Controllers shifts (one controller per sector without night shifts)


213 14 1

516 17 1

819 2

021 22 2

324 25 2

627 2

829 30 3

1Total

1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1472 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 1403 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 147

document.docx of 68


2 – day shift: from 14:30 till 22:00, duration 7 hours, break - 30 min (responsibility of the person)1 – morning shift: from 07:30 till 15:00, duration 7 hours, break - 30 min (responsibility of the person)

document.docx of 68


Pattern F – ATC Controllers shifts (one controller per sector without night shifts)


1 2 1 2 1 1 2 1 2 2 1 2 1 1 2 1 2 2 1 2 1 1 1472 1 2 1 2 2 1 2 1 1 2 1 2 2 1 2 1 1 2 1 2 1403 1 2 2 1 2 1 1 2 1 2 2 1 2 1 1 2 1 2 2 1 2 147


Pattern G – ATC Controllers shifts (one controller per sector without night shifts)

Minimum number of persons Month dates / Shifts1 2 3 4 5 6 7 8 9 10 1

112 1

314 1

516 17 1

819 2

021 2

223 24 2

526 2

728 2

930 3

1Total


D – day shift: from 08:00 till 20:00, duration 11 hours, lunch - 30 min, break – 30 min (responsibility of the person)

Pattern H – ATC Controllers shifts (one controller per sector without night shifts)

Minimum number of persons Month dates / Shifts1 2 3 4 5 6 7 8 9 10 1

112 13 14 15 1

617 18 19 2

021 22 23 24 2

526 27 28 29 3

031 Total

1 2 D 1 R 2 D 1 2 D 1 R 2 D 1 2 D 1 R 2 1562 R 2 D 1 2 D 1 R 2 D 1 2 D 1 R 2 D 1 1493 1 R 2 D 1 2 D 1 R 2 D 1 2 D 1 R 2 D 1 156


document.docx of 68


D – day shift: from 08:00 till 20:00, duration 11 hours, lunch - 30 min, break – 30 min (responsibility of the person)R – day shift: from 08:30 till 17:00, duration 8 hours, break - 30 min (responsibility of the person)

Tower Riga

Pattern A – Tower Controller shifts (one controller per sector)


Pattern B – Tower Controller shifts (two controllers per sector)


213 1

415 1

617 1

819 2

021 2

223 2

425 2

627 2

829 3

031 Total

1 2 1 3 2 1 2 1 3 2 1 2 1 3 2 1 2 1 3 2 1 1542 2 1 3 2 1 2 1 3 2 1 2 1 3 2 1 2 1 3 2 1473 1 2 1 3 2 1 2 1 3 2 1 2 1 3 2 1 2 1 3 1474 2 1 2 1 3 2 1 2 1 3 2 1 2 1 3 2 1 2 1 3 1545 2 1 2 1 3 2 1 2 1 3 2 1 2 1 3 2 1 2 1 3 1546 2 1 2 1 3 2 1 2 1 3 2 1 2 1 3 2 1 2 1 143.57 3 2 1 2 1 3 2 1 2 1 3 2 1 2 1 3 2 1 2 1478 1 3 2 1 2 1 3 2 1 2 1 3 2 1 2 1 3 2 1 147


document.docx of 68

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

13 14

15 16

17 18

19 20

21 22

23 24

25 26

27 28

29 30

31 Total

1 2 1 3 2 1 3 2 1 3 2 1 3 2 1 3 2 1 3 2 1542 2 1 3 2 1 3 2 1 3 2 1 3 2 1 3 2 1 3 1473 2 1 3 2 1 3 2 1 3 2 1 3 2 1 3 2 1 3 1474 3 2 1 3 2 1 3 2 1 3 2 1 3 2 1 3 2 1 3 157.55 1 3 2 1 3 2 1 3 2 1 3 2 1 3 2 1 3 2 1 154


document.docx of 68


Pattern C – Tower Controller shifts


1 2 1 3 2 1 3 D* D* 2 1 3 2 1 3 D* D* 2 1 3 156.52 2 1 3 D

*D* 2 1 3 2 1 3 D

*D* 2 1 3 2 1 146

3 2 1 3 2 1 3 D*

D* 2 1 3 2 1 3 D*

D* 2 139

4 3 2 1 3 D* D*

2 1 3 2 1 3 D* D*

2 1 3 142.5

5 D*

D* 2 1 3 2 1 3 D*

D* 2 1 3 2 1 3 D*

D* 149

6 D* D*

2 1 3 2 1 3 D* D*

2 1 3 2 1 3 D* 140.5

7 1 3 D* D* 2 1 3 2 1 3 D* D* 2 1 3 2 1 3 149.5


D* optional shifts:D1 – day shift: from 09:00 till 18:00, duration 8 hours 30 min, break - 30 min (responsibility of the person)D2 – day shift: from 10:00 till 19:00, duration 8 hours 30 min, break - 30 min (responsibility of the person)D3 – day shift: from 11:00 till 20:00, duration 8 hours 30 min, break - 30 min (responsibility of the person)D4** – day shift: from 07:00 till 17:00, duration 10 hours, break - 30 min (responsibility of the person)D5** – day shift: from 08:00 till 18:00, duration 10 hours, break - 30 min (responsibility of the person)

D** - those shifts are not only for Riga, but for regional aerodromes as well.

In certain cases shift can be prolonged for 1(one) hour.

document.docx of 68


Tower Liepaja

Pattern A – Tower Controller shifts (two controllers per sector)

Minimum number of persons Month dates / Shifts1 2 3 4 5 6 7 8 9 10 11 12 1

314 15 1

617 18 19 2

021 22 23 2

425 26 2

728 29 30 3

1Total

1 2 D 1 2 D 1 2 D 1 2 D 1 2 D 1 2 D 1 2 D 1 2 D 1 177.22 1 2 D 1 2 D 1 2 D 1 2 D 1 2 D 1 2 D 1 2 D 1 2 169.23 D 1 2 D 1 2 D 1 2 D 1 2 D 1 2 D 1 2 D 1 2 D 1 170.14 2 D 1 2 D 1 2 D 1 2 D 1 2 D 1 2 D 1 2 D 1 2 D 170.2

1 – morning shift: from 05:00 till 12:30, duration 7 hours, break - 30 min (responsibility of the person)2 – day shift: from 14:00 till 20:10 / from 22:30 till 24:00, duration 7 hours 10 min, break - 30 min (responsibility of the person)D – day shift: from 08:30 till 17:00, duration 8 hours, break - 30 min (responsibility of the person)

Pattern B – Tower Controller shifts (two controllers per sector)


213 14 1

516 17 1

819 2

021 22 2

324 25 2

627 2

829 30 3

1Total

1 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 1472 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1403 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 147

1 – morning shift: from 08:30 till 16:00, duration 7 hours, break - 30 min (responsibility of the person)2 – day shift: from 09:30 till 17:00, duration 7 hours, break - 30 min (responsibility of the person)

Pattern C – Tower Controller shifts (two controllers per sector)


213 14 1

516 17 1

819 2

021 22 2

324 25 2

627 2

829 30 3

1Total

1 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 1612 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 161

document.docx of 68


1 – morning shift: from 08:30 till 16:00, duration 7 hours, break - 30 min (responsibility of the person)2 – day shift: from 09:30 till 17:00, duration 7 hours, break - 30 min (responsibility of the person)Pattern D – Tower Controller shifts (two controllers per sector)


213 14 1

516 17 1

819 2

021 22 2

324 25 2

627 2

829 30 3

1Total

1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 1542 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 1 2 1 2 1333 1 2 2 1 1 2 2 1 1 2 2 1 1 2 2 1 2 2 1 1 2 147

1 – morning shift: from 08:30 till 16:00, duration 7 hours, break - 30 min (responsibility of the person)2 – day shift: from 11:30 till 19:00, duration 7 hours, break - 30 min (responsibility of the person)

document.docx of 68