TRS ANNEX eDEP SSP Demonstrator v1.0...TRS ANNEX eDEP SSP Demonstrator_v1.0.doc Date : DD/MM/YYYY...

TRS ANNEX eDEP SSP Demonstrator_v1.0.doc

Date : DD/MM/YYYY

Page : i EUROCONTROL

STATUS TITLE Company Ref. Template : tec01.dot

EUROCONTROL EXPERIMENTAL CENTRE Brétigny-sur-Orge, FRANCE

eDEP

Technical Document

TRS eDEP SSP Demonstrator

Issue date:14 November 2003

<Preface>

The information contained in this document is the property of the EUROCONTROL Agency and no part should be reproduced in any form without the Agency’s permission.

The views expressed herein do not necessarily reflect the official views or policy of the Agency.


Date : DD/MM/YYYY

Page : ii EUROCONTROL


Document Change Log Release Author Date of the

release Description of the

release Modifications (sections affected

and relevant information) 0.1 D.Smith Draft for comments 0.2 D.Smith 11/11/03 Comments integrated

WP5 expanded upon

1.0 D.Smith 14/11/03 Official Release Dates shifted 2 weeks (start 19/01) Updated reference section

Acceptance andReviewing Procedures Name (s) Date of acceptance/ review Date of approval

Document distribution to/cc Name Role

Table of contents

1. INTRODUCTION........................................................................................................................................ 1

1.1 PURPOSE................................................................................................................................................. 1 1.2 INTENDED AUDIENCE................................................................................................................................. 1 1.3 ASSOCIATED DOCUMENTATION.................................................................................................................. 1

1.3.1 TRS Input Documentation.............................................................................................................. 1 1.3.2 Existing Project Documentation ..................................................................................................... 2

1.4 GLOSSARY ............................................................................................................................................... 2 1.5 TERMINOLOGY.......................................................................................................................................... 3

2. PROJECT OVERVIEWS ........................................................................................................................... 4

2.1 EDEP PROJECT ....................................................................................................................................... 4 2.1.1 Objectives....................................................................................................................................... 4 2.1.2 Platform Functionality..................................................................................................................... 4 2.1.3 Software Size ................................................................................................................................. 5 2.1.4 Documentation ............................................................................................................................... 5

2.2 E-COCKPIT PROJECT................................................................................................................................ 5 2.2.1 Objectives....................................................................................................................................... 5


Date : DD/MM/YYYY

Page : iii EUROCONTROL


2.2.2 Functionality ................................................................................................................................... 5 2.2.3 Software Size ................................................................................................................................. 5 2.2.4 Documentation ............................................................................................................................... 6

3. TRS MANAGEMENT ISSUES .................................................................................................................. 6

3.1 PHASED TASKING ..................................................................................................................................... 6 3.1.1 Background Information ................................................................................................................. 6 3.1.2 Future Work packages ................................................................................................................... 6

3.2 GENERAL ISSUES ..................................................................................................................................... 6 3.3 LOCATION ................................................................................................................................................ 7 3.4 MONTHLY REPORTING............................................................................................................................... 7 3.5 ROLES AND RESPONSIBILITIES .................................................................................................................. 7

4. TRS OVERVIEW........................................................................................................................................ 8

4.1 OBJECTIVES............................................................................................................................................. 8 4.2 OVERALL SCOPE ...................................................................................................................................... 8 4.3 SCHEDULE ............................................................................................................................................... 8 4.4 MILESTONES ............................................................................................................................................ 9 4.5 TRS RESPONSE..................................................................................................................................... 10

5. TRS TECHNICAL MANAGEMENT......................................................................................................... 11

5.1 DESIGN PROCESS .................................................................................................................................. 11 5.2 TOOLS / COTS ...................................................................................................................................... 12 5.3 CODING STANDARDS .............................................................................................................................. 12 5.4 SOFTWARE ............................................................................................................................................ 12 5.5 DOCUMENTATION ................................................................................................................................... 12

6. WORK PACKAGES ................................................................................................................................ 13

6.1 WP 0 : MANAGEMENT............................................................................................................................. 13 6.2 WP1 INITIATION ..................................................................................................................................... 13

6.2.1 WP1.1 eCockpit & eDEP Software Management ........................................................................ 13 6.2.2 WP1.2 Technical Studies & Costing for WP2 .............................................................................. 14 6.2.3 WP1.3 Technical Studies & Costing for WP5 [Future Task]........................................................ 15 6.2.4 WP1.4 Technical Studies & Costing for WP3 [Future Task]....................................................... 15 6.2.5 WP1.5 Technical Studies & Costing for WP4 [Future Task]....................................................... 16

6.3 WP2 AVT DEMONSTRATOR.................................................................................................................... 16 6.3.1 Overview ...................................................................................................................................... 16 6.3.2 WP2.1 eDEP / eCockpit Technical Integration ............................................................................ 17 6.3.3 WP2.2 : (Live AIR) eCockpit / ARTAS Integration ...................................................................... 18 6.3.4 WP2.3 : (Simulated AIR/GRD) eCockpit / eDEP AIR+GRD Integration ...................................... 20 6.3.5 WP2.4 : (Pseudo Live AIR / GRD) eCockpit/eDEP GRD/ ARTAS Integration ............................ 21 6.3.6 WP2.5 : CDTI Upgrades for AVT ................................................................................................. 21

6.4 WP3 : A320/340 COCKPIT ..................................................................................................................... 21 6.5 WP4 : CDTI FOR MCS/COSPACE .......................................................................................................... 22 6.6 WP5: SECTOR PACKAGE 1 DEMONSTRATOR ........................................................................................... 22

Index of figures

Index of tables


Date : DD/MM/YYYY

Page : 1 EUROCONTROL


1. INTRODUCTION

1.1 Purpose

This document provides supplementary information for eDEP SSP Demonstrator TRS 2004 which should assist framework members in preparing their responses.

The information provided herein includes

• Background information (e.g. eDEP platform technical overview, eDEP project aims)

• top-level software requirements

• references to detailed software requirements

1.2 Intended audience

All companies responding to the TRS offer.

1.3 Associated documentation

Note: Due to the size of the associated documentation (14MB zipped), it shall not be sent via e-mail with the TRS notification.

The documentation has been placed at the following location

http://www.eurocontrol.fr/projects/edep/trs/eDEP_SSP_2004_DocumentPack.zip

1.3.1 TRS Input Documentation

Title Reference Version Date

[Ref 1] URD for Airbus A340 ?? ?? ??

[Ref 2] ASTERIX Part 1 SUR.ET1.ST05.2000-STD-01-01

http://www.eurocontrol.int/asterix/documents/pt1ed128.pdf

V1.28 Dec 01

[Ref 3] ASTERIX for SMART3-SDG (Asterix 244) DIS/SUR/SASS-C/DOC/00303.0.3 V0.3 Sept 02

[Ref 4] ASTERIX Surveillance Data Exchange Part 12 : category 021

SUR.ET1.ST05.2000-STD-12-01

http://www.eurocontrol.int/asterix/documents/p12ed020.pdf

V0.20 Dec 02

[Ref 5] ASTERIX Surveillance Data Exchange Part 09 : category 062

SUR.ET1.ST05.2000-STD-09-01

http://www.eurocontrol.int/asterix/documents/p9ed029.pdf

V0.29 Sept 03

[Ref 6] AVT Requirements on CDTI function of MCS Avt_cdti_reqs_v01.doc V0.1 ??

[Ref 7] Appendix AD :Expected CDTI MOPS Requirements

ASA MASPS CDTI section – for WG1 review 5-27-03.doc

?? ??

[Ref 8] ASAS Spacing cockpit interface User Requirement Document

Asas_Spacing_URD_1.1.pdf V1.1 09/09/03


Date : DD/MM/YYYY




[Ref 9] Software Specification Document of Delegation markings

Y02-M07 SDD DEL-5.doc V5 09/04/03

[Ref 10] Software Integration Tests for Delegation Markings

Y02-M08 SITD DEL-2.doc V1 29/07/02

[Ref 11]

Note: the latest ASTERIX documentation is available at http://www.eurocontrol.int/asterix/

1.3.2 Existing Project Documentation


[Ref 12] ECockpit Web site http://www.eurocontrol.fr/projects/freer/e-Cockpitversions/

[Ref 13] EDEP Architecture Design Document http://www.eurocontrol.fr/projects/edep

V1.4

[Ref 14] E-Cockpit Software Specification Document DSL-3-1 (Evol CDTI) 27 janv V3.1 27/01/00

[Ref 15] E-Cockpit User Requirements Document Urd.doc V1.4 19/10/98

[Ref 16] E-cockpit validation document Cv Evol 26 janv V1.0 27/01/00

[Ref 17] E-Cockpit Software Design Document DC-2.0 Evol CDTI V2.0 19/01/00

The eDEP project web-site is at http://www.eurocontrol.fr/projects/edep which includes,

• functionality overviews

• downloadable demonstrations

• full documentation set including Architecture, Design, Test and User Documentation.

The eCockpit website is at http://www.eurocontrol.fr/projects/freer/e-Cockpitversions/ which includes

• eCockpit applet

• eCockpit User Guides (http://www.eurocontrol.fr/projects/freer/e-Cockpitversions/Manual.html)

1.4 Glossary ACL ATC Clearances (via Datalink) ACM ATC Communication Management ACR Aircraft Server ACS ATM Concepts and Studies BA ADS-B Automatic Dependent Surveillance Broadcast AMAN Arrival Manager ASA Automated Support to ATC ASAS Airborne Separation Assurance System ASP Airspace Server ATC Air Traffic Control ATG Air Traffic Generator ATM Air Traffic Management BA Business Area CAP Controller Access Parameters


Date : DD/MM/YYYY



CFMU Central Flow Management Unit COORD Co-ordination Server CORA Conflict Resolution Assistant CWP Controller Working Position DIS Directorate Infrastructure, ATC Systems & Support DIS/ATD Air Traffic Control & Data Processing DIS/HUM Human Factors and Manpower DMAN Departure Manager DOVE Datalink Operational Validation Experiments DSA/AMN Airspace Management & Navigation EACAC European Civil Aviation Conference EATCHIP European ATC Harmonisation and Integration Programme EATMP European Air Traffic Management Programme EC European Commission EDEP Eurocontrol Early Demonstration and Evaluation Platform EEC EUROCONTROL Experimental Centre EMAN En-route Manager ERIS EATMP Reference Industry Based Simulation Platform FM Flight Manager FPM Flight Plan Monitor GRD Ground HMI Human Machine Interface IAS Integrated Air Surveillance IFPL Initial Flight Plan INO Innovation BA LoA Letters of Agreement MSP Multi-Sector Planner MTCD Medium Term Conflict Detection PFE Performance, Flow Management, Economics and Efficiency PM Pilot Manager PPD Pilot Preference Downlink PWP Pilot Working Position SAF Safety BA STCA Short Term Conflict Alert TLS Tactical Load Smoother TME Time Server TP Trajectory Predictor VAW Vertical Assistance Window WBS Work Breakdown Structure XFL eXit Flight Level

1.5 Terminology

In order to ensure clarity and readability, the following conventions are applied in this document:

"shall": The word "shall" is used whenever a mandatory requirement is expressed.

"should": The word "should" is used in order to express a recommendation.

"bidder": The word "bidder" designates an organisation responding to this Call for Tender.

"supplier": The word "supplier" designates the organisation selected by EUROCONTROL to carry out the work defined in this Specification.

"he": The word "he" stands for "he/she".


Date : DD/MM/YYYY



2. PROJECT OVERVIEWS

2.1 eDEP Project

2.1.1 Objectives

The aim of the eDEP project is to produce a low-cost, lightweight, web-enabled ATM simulator platform, offering an ideal environment for research and advanced concept projects to rapidly prototype applications.

The platform is written in Java, enabling it to be run across the web on various platforms (Windows, Linux, Unix). For simple demonstration purposes the platform can be run on a single PC, or can equally be distributed across the network for the needs of small-scale simulation.

2.1.2 Platform Functionality

The platform offers broad yet simplified ATM functionality, covering the AIR, GRD and CWP subsystems.

The eDEP platform will offer the following functionality at end-2003

• GRD subsystem

• Environment components – Airspace, Flight Plan, Time, Aircraft Performance

• RDPS - IAS (Integrated Air Surveillance component)

• FDPS – Flight Manager (FM), 4D Trajectory Predictor (TP), Co-ordination (COORD)

• Tools – MTCD, STCA, FPM, HIPS, AMAN

• AIR subsystem

• PM (Pilot Manager)

• PWPs (Pilot Working Positions)

• CWP subsystem

• Minimum EATMP HMI subset (ACC Labels, SIL, MiW, MoW, PPD, VAW)

• Inter-CWP communication component (PC/TC comms)

• Experimentation support tools

• Simple traffic editor / profile validation tool

• IPAS data reader (via STORIA XML)

• Data recording and CWP replay facility

Equally, the eDEP platform has the following characteristics

• Lightweight – the complete system can run on a single PC (1 Ghz, 512MB RAM)

• Web-enabled – the complete system may be downloaded and run via the internet

• Support for distribution

Refer to the eDEP Architecture Design Document ([Ref 13]) for more information.


Date : DD/MM/YYYY



2.1.3 Software Size

The eDEP platform has been under development since April 2001. The current platform consists of approximately 150 000 lines of code,1 and concentrates on the GRD / CWP functionality.

2.1.4 Documentation

The following eDEP project documentation exists (in MS-Word 97 format),

• Architecture Document

• Toolkit Design Document

• Platform User Guide / Admin Guide

• Developer’s Tutorial Guide

• Comprehensive HMTL javadoc documentation

• Test Plan Procedure Documentation (Component Test Scripts)

2.2 E-Cockpit Project

2.2.1 Objectives

The objective of the eCockpit project was to produce a light-weight cockpit demonstrator, implementing a number of ASAS applications .

2.2.2 Functionality

The e-Cockpit application includes,

• B777 Cockpit with

• detailed graphical cockpit layout

• ASAS applications

• Simple a/c performance model

• Simple Controller Working Position (CWP)

• Simple simulation capabilities

• scenario launcher mechanism

• simple airspace definitions

• simple ‘other traffic’ simulation

2.2.3 Software Size

The software project represented 3-4 man years effort, and consists of approximately 40 000 lines (i.e. lines and not lines of code).

The eCockpit software is built upon ILOG Jviews.

Note: the software was developed in 1999, upon an old version of Jviews. 1 Using the LOC tool from http://csdl.ics.hawaii.edu/Tools/LOCC/


Date : DD/MM/YYYY



2.2.4 Documentation

The following eCockpit documentation exists:

• User Requirements Document (specific for the B777 HMI)

• Software Specification Document

• Software Design Document

• Validation (Test) Document

• Various User guides

The following document will equally be proved

• User Requirements Document (specific for an Airbus HMI)

3. TRS MANAGEMENT ISSUES

3.1 Phased Tasking

3.1.1 Background Information

This TRS is a phased tasking contract, which includes a number of initial tasks (which are mandatory), and a number of future tasks (which shall be activated by the EEC at the appropriate moment if required).

The TRS has been designed in this manner for the following reasons:

• Flexibility: the ability for Eurocontrol to modify and launch work packages upon demand.

• Time-scales: ability for Eurocontrol to further analysis Requirements before work package activation

• Budget constraints: ability for Eurocontrol to launch or delay work packages dependent upon the supplier costing versus the Eurocontrol yearly budget constraints.

In responding to this TRS the bidder is expected to confirm his ability to produce the overall deliverable (initial & future tasks) within the defined financial envelope.

The bidder is invited to read the “General Terms and Conditions for Phased Tasking Contracts”.

3.1.2 Future Work packages

Future work packages shall be activated following a formal process.

• The EEC shall review current progress

• The EEC shall review the expected deliverables, scope and objectives of the future work package with the supplier

• The EEC and supplier shall agree on the required inputs before the future work package may be activated

• The EEC shall review the planning dates with the supplier

• The supplier shall provide a detailed costing for the work package (refer to general conditions).

• Following EEC approval the work package shall be activated.

3.2 General Issues

In the context of the TRS all exchanges (written or oral) shall be in English.


Date : DD/MM/YYYY



3.3 Location

The TRS is expected to be executed as follows

• Off-site : all standard development & maintenance work

• On-site: requirement capture phases & acceptance test phases

• off-site : 2nd level support activities

3.4 Monthly reporting

Reporting shall be monthly, and shall include the following:

• Progress / Activity report progress with respect to the agreed plan impact on milestone dates significant changes if any

• Action List List of all new, ongoing, and recently closed2 actions

• Risk List List of identified risks and their associated probability / impact values, and their mitigation strategy

• Issue List longer term issues which have not yet been upgraded to the risk or action lists.

• Decision Register all decisions (following supplier/EEC discussions) will be reported here. This is to ensure that EEC management may monitor decisions taken which may impact (a) delivery dates and/or (b) delivery content.

3.5 Roles and Responsibilities

The responsibilities shall be as follows:

• The Supplier: Shall be responsible for the organisation of all activities previously described which are necessary for him to produce the deliverables. Shall manage all meetings and aspects of the contract, in co-ordination with the eDEP Manager (or his delegate). The Contractor shall provide, in co-operation with the eDEP Manager, agendas for meetings and shall produce the minutes thereof.

• The eDEP Manager (or his delegate) shall be responsible for the overall control and organisation of the whole project (delegated to the contractor) and shall assist in meetings.

• Decisions shall be prepared by the supplier, co-ordinated and agreed with the eDEP Manager, and made by the eDEP Manager (or his delegate).

• Reviews and Acceptance shall be as follows: Internal Supplier review followed by sign off by the eDEP Manager.

• In case of conflict, the eDEP Manager shall be the ultimate authority

2 Actions that have been closed for more than 1 reporting period shall be removed.


Date : DD/MM/YYYY



4. TRS OVERVIEW

4.1 Objectives

The SSP Business Area intends to build a portable and lightweight concept demonstrator, covering both the controller and pilot roles.

This shall be achieved by building upon the eDEP platform, and reusing/integrating parts of the eCockpit demonstrator.

4.2 Overall Scope

This phased TRS has the following parts:

• Initial Tasks (Work Packages)

• WP1.1

• WP1.2

• Future Tasks (Work Packages)

• WP1.3-5

• WP2

• WP3

• WP4

• WP5

The EEC intends to activate the WP2 task.

The EEC estimates the overall effort for this contract (covering Initial & Future tasks) at 5 man years.

4.3 Schedule

The following is a proposed EEC schedule (note : no holiday time has been planned).

This schedule is intended to demonstrate a possible development plan. The bidder is expected to produce his/her own schedule based on bidder effort estimates.


Date : DD/MM/YYYY



ID Task Name Duration Start Finish

1 WP0 : Management 500 days Mon 19/01/04 Fri 16/12/05

2

3 WP1 : Initiation 290 days Mon 19/01/04 Fri 25/02/05

4 WP1.1 : Softw are Mgt 40 days Mon 19/01/04 Fri 12/03/04

5 WP1.2 : Tech Study & Costing for WP220 days Mon 15/03/04 Fri 09/04/04




9

10

11 WP2 : AVT Demonstrator 190 days Mon 12/04/04 Fri 31/12/04

12 WP2.1 : eDEP/eCockpit Technical Integration40 days Mon 12/04/04 Fri 04/06/04

13 WP2.2 : (Live AIR) eCockpit/ARTAS Integration80 days Mon 07/06/04 Fri 24/09/04

14 WP2.3 : (Sim AIR/GRD) eCockpit/eDEP Integration80 days Mon 07/06/04 Fri 24/09/04

15 WP2.4 (Pseudo Live) eCockpit/eDEP/ARTAS Integration70 days Mon 27/09/04 Fri 31/12/04

16 WP2.5 : CDTI Upgrades for AVT 70 days Mon 27/09/04 Fri 31/12/04

17

18 WP3 : A320/340 Cockpit 160 days Mon 28/02/05 Fri 07/10/05

19 Development 160 days Mon 28/02/05 Fri 07/10/05

20

21 WP4 : CDTI COSPACE 160 days Mon 28/02/05 Fri 07/10/05

22 Development 160 days Mon 28/02/05 Fri 07/10/05

23

24 WP5 : Sector Package 1 Demonstrator320 days Mon 26/07/04 Fri 14/10/05

25 Iteration 1 90 days Mon 26/07/04 Fri 26/11/04



Dev1;Dev2

Dev1;Dev2

Dev3

Dev1;Dev2

Dev1;Dev2

Dev1;Dev2

Dev1

Dev2

Dev1

Dev2

Dev1

Dev2

Dev3

Dev3

Qtr 1 Qtr 2 Qtr 3 Qtr 4 Qtr 1 Qtr 2 Qtr 3 Qtr 42004 2005

4.4 Milestones

The following Eurocontrol milestones are specified:

(Initial, Future, Additional)

ID Date Work Package Deliverable

Initial Tasks

SSP1 12/03/04 WP1.1 eCockpit Status Document

SSP2 09/04/04 WP1.2 Commercial & Technical Proposition Updated URD Updated & Draft eCockpit SRD

Future Tasks (for which activation is decided)

SSP3 04/06/04 WP2.1 eDEP/eCockpit technical integration

SSP4 24/09/04 WP2.2 Live AIR delivery (acceptance tested) Software Test Plan

SSP5 24/09/04 WP2.3 Simulated AIR+GRD Delivery (acceptance tested) Software Test Plan


Date : DD/MM/YYYY



SSP6 20/12/04 WP2.4 Pseudo Live AIR + GRD Delivery (acceptance tested) Software Test Plan Full Document Set update (eCockpit & eDEP)

SSP7 20/12/04 WP2.5 AVT CDTI Upgrades (acceptance tested) Software Test Plan

Future Tasks (for which activation is not yet decided)




SSP11 07/10/05 WP3 A320/340 eCockpit Delivery Updated Software Test Plan

Full Document Set update (eCockpit & eDEP)

SSP12 07/10/05 WP4 eCockpit CDTI for MCS/CoSpace Delivery Updated Software Test Plan


SSP13 26/11/04 WP5 Sector Package 1 Demonstrator : Iteration1




4.5 TRS Response

Apart from classical contents appearing systematically in responses for ERC TRSs, the following items shall be addressed:

1. Work analysis

1. The bidder shall not re-write the contents of the TRS, but shall give an interpretation and analysis of the work to be performed, as well as a rough idea of the methods and tools to achieve the provision of the TRS deliverables.

2. The bidder shall provide a high level architecture (black-box) design of the components and its place within the eDEP server architecture. This shall enable the EEC to judge the bidder’s technical offer.

2. Contractual aspects


Date : DD/MM/YYYY



1. Declaration of the bidder’s agreement to provide the overall TRS deliverable (initial & future tasks) within the defined maximum financial envelope3

2. Licence agreements if necessary

3. Declaration if the TRS bid involves the use of sub-contractors

4. Information required under the terms and conditions of phased tasking (notably, daily rates for cost estimation, initial task effort estimations)

3. Project Management Plan (PMP)

This task consists in addressing the management issues of the TRS. This includes:

1. Effort estimates (reviewed by the bidder) for each work package.

2. CVs of the team involved in the TRS and their respective roles. The bidder shall give a justification on why the given profiles fit the TRS expertise requirements. If the bidder is not in the position to guarantee the actual designation of this team for the TRS, he shall precise so and guarantee equivalent expertise will be used.

3. Planning giving at least on which WP the team members are allocated and the nature of their contribution (sub-tasks).

4. Quality assurance measures applied to the TRS lifetime.

4. Company description

1. The bidder shall enumerate references, with contact names for Eurocontrol references, of experiences of a similar nature to the TRS in such aspects as off-site externalisation

2. The bidder shall describe the exact motivations to handle such a TRS and how it fits to its business strategy.

3. Finally, the bidder shall precise in which location and which technical environment its team will execute the TRS.

5. TRS TECHNICAL MANAGEMENT

5.1 Design Process

The eDEP project uses an iterative step-wise development process. For each identified work package iteration the following will occur –

• initial supplier / EEC discussion on the exact nature of the task

• Supplier conducts the initial design work

• Joint Supplier / EEC design review

• Supplier conducts the implementation phase

• Joint Supplier / EEC code review

3 The bidder shall indicate if the overall deliverable requires a financial envelope inferior to the maximum envelope declared in the TRS.


Date : DD/MM/YYYY



5.2 Tools / COTS

The supplier is responsible for the purchase of all relevant software tools.

• UML modelling tool4

• Eclipse IDE (www.eclipse.org) shall be used for software development.

• Sun Java J2SE 1.4.1+

• ILOG Jviews (latest version is 5.5)

• Software Configuration Management Tool

• Microsoft Word (XP Word 2002)

• Microsoft Project 2000

All software shall be developed on a PC Windows environment.

The EEC provides access to a Bug Reporting Tool via the web (Remedy). The supplier may choose to use this EEC tool, or supply their own.

5.3 Coding Standards

The supplier shall apply appropriate Java code and comment standards within the project (e.g. Sun recommendations).

The supplier is requested to apply modern software design practices (e.g. use of design patterns, use of Java2 design patterns).

5.4 Software

The code shall contain extensive javadoc comments.

All developed software shall be the intellectual property of Eurocontrol (within the limits of existing software licence agreements).

Full software source code shall be delivered to the EEC.

5.5 Documentation

All Microsoft Word documentation shall be delivered in Word-2002 format.

This TRS shall maintain the eDEP documentation outlined in section 2.1.4

This TRS shall update the following eCockpit documentation

• User Requirements Document (on the EEC’s behalf)

• Software Specification Document

• Software Design Document (the EEC suggests that the main document body concerning detailed class descriptions be deleted. Instead this document should provide an overview of the overall architecture & design structure, similar in detail to the eDEP DDD documentation).

• Validation Document (A test document shall be maintained. Its form and content is open to discussion)

4 The following UML tools are acceptable – Rationale Rose, or MagicDraw (http://www.magicdraw.com/ ).


Date : DD/MM/YYYY



• Javadoc Code comments (The current eCockpit software contains little or no java comments. It is recommended that the SDD class descriptions are moved into javadoc style comments within the code)

• User Guides (these documents shall be maintained and extended)

Note : the relevance & consistency of the eCockpit documentation is open to discussion. During the course of the TRS the supplier and EEC may agree to changes in the documentation strategy.

6. WORK PACKAGES

6.1 WP 0 : Management

The supplier shall be responsible for:

• Supplier team management

• Supplier team planning

• Monthly reporting with the following deliverables :

• Progress report

• Action list / Risk List / Decision Register

• Microsoft Project Plan

6.2 WP1 Initiation

6.2.1 WP1.1 eCockpit & eDEP Software Management

The software & documentation will be taken over by the supplier.

This work package allows the supplier to master the software code bases (eDEP & eCockpit) so that detailed cost estimations may be provided in WP1.2 for the future work packages.

The eDEP and eCockpit platforms combined constitute nearly 200 000 lines of code.

Therefore, all bidders should indicate the effort required before their proposed team can be considered ‘operational’ (i.e. fully familiar with the software). The EEC suggests the following:

Software Man Months

EDEP platform (150, 000 LOC) 18 man months

ECockpit platform (40, 000 lines) 4 man months

Therefore, for bidders unfamiliar with the platform, delivery dates & financial costing should be realistically calculated.

In particular, this work package should ensure that the eCockpit software is in full working order.

This will involve :

• Purchase of latest Jviews product


Date : DD/MM/YYYY



• Adapt eCockpit software to this version of Jviews5

• Verify its functioning state by re-running the Validation tests.

ID SSP1

Work Package Input eCockpit Software & Documentation eDEP Software & documentation

Work Package Output ECockpit Status Document – document describing the current software status, including the validation test results.

Effort Estimate 4 - 22 man months (dependent on supplier knowledge of eDEP/eCockpit software)

Delivery Date 12/03/04 (assuming supplier has eDEP knowledge)

6.2.2 WP1.2 Technical Studies & Costing for WP2

This work package will provide technical and commercial propositions for the work package 2 “AVT Demonstrator”.

Supplier will

- Interview EEC staff to determine detailed User Requirements

- Translate those User requirements into high level Software Requirements (knowing both the eDEP and eCockpit software code bases)

- Perform a number of technical feasibility studies (e.g. issues of removing Jviews)

- Provide Detailed schedule / cost estimates for work packages

ID SSP2

Work Package Input WP1.1 (or parts thereof) AVT related documents ([Ref 2] [Ref 3] [Ref 4] [Ref 5] [Ref 6] [Ref 7])

Work Package Output Updated eCockpit URD (mainly for HMI concerns)

Technical Proposition –

• Proposed Design solution detailing architecture issues, and top level detailed design.

• Work breakdown structure

Commercial Proposition – cost (including missions)

Effort Estimate 2 man months

Delivery Date 09/04/04 (FIRM)

5 ECockpit was developed in 1999 with an older version of JViews


Date : DD/MM/YYYY



6.2.3 WP1.3 Technical Studies & Costing for WP5 [Future Task]

This work package will provide technical and commercial propositions for the work package 5 “Sector Package 1 Demonstrator”.

Supplier will

• Interview EEC staff to determine detailed User Requirements

• Translate those User requirements into Software Requirements (knowing both the eDEP and eCockpit software code bases)

• Perform a number of technical feasibility studies (e.g. issues of removing Jviews)

• Provide Detailed schedule / cost estimates for work packages

ID SSP8

Work Package Input WP1.1 (or parts thereof) EUROCONTROL Concept documents (TBD)

Work Package Output Technical Proposition –





Delivery Date (Estimated) 23/07/04


This work package will provide technical and commercial propositions for the work package 3 “A320/340 Cockpit”

Supplier will





ID SSP9

Work Package Input WP1.1 (or parts thereof) Eurocontrol provided eCockpit URD for Airbus A320/A340 ([Ref 1])




Date : DD/MM/YYYY








This work package will provide technical and commercial propositions for the work package 4 “CDTI for MCS/COSPACE”

Supplier will





ID SSP10

Work Package Input WP1.1 (or parts thereof)

COSPACE Requirements ([Ref 8] [Ref 9] [Ref 10])







6.3 WP2 AVT Demonstrator

6.3.1 Overview

The AVT project is concerned with building an ADS-B Validation Testbed, based upon the ESCAPE/PROVE platform (including a number of live-trials capabilities).

The AVT project now wishes to build a light-weight demonstrator incorporating elements of eDEP and eCockpit.

The following diagram illustrates the overall expectations (note: architecture design decisions should not be inferred from this diagram):


Date : DD/MM/YYYY



ARTAS

eCockpit eCockpit

ASTERIX cat 62(tracks)

HMI = TIS-B

ASTERIX cat 21(ads reports)

ASTERIX cat 62(tracks)

eDep GRD

eDep AIR

We have the following configurations required:

• Live AIR mode (in YELLOW)

• Simulated AIR&GRD mode (in BLUE)

• Pseudo Live AIR&GRD mode (both BLUE and YELLOW)

The following sections detail the work package breakdown.

6.3.2 WP2.1 eDEP / eCockpit Technical Integration

This work package covers the initial technical work required to integrate the eDEP and eCockpit software bases.

This work package must be executed and terminated before following Wp2.x work packages.

Tasks include

Integration Task Description Comments

EDEP Component Framework Use of eDEP distribution, lifecycle and time services

Mandatory

EDEP Environment services Use of airspace, flight plan services. Equally use of eDEP Entity Models (TBD)

Mandatory

EDEP AIR Subsystem Basic integration of eCockpit into eDEP PM (i.e. remove eCockpit ‘other’ traffic generator)

Mandatory (although may be done in wp 2.3).

Depends if chosen architecture connects eCockpit directly to ARTAS, or via the eDEP PM.

Removal of eCockpit navigation component

ECockpit could depend upon eDEP’s own TP to generate its flight path

Optional. This is probably high risk. We should perhaps keep eCockpit’s own internal navigation


Date : DD/MM/YYYY



logic.

Removal of Jviews Replaced by the eDEP Graphics Engine (GSDK)

Optional. The merit of such a removal needs to be justified.

EDEP Recording & replay Client has expressed interest in replay

Optional.

The objective of this work package is to have a working eDEP/eCockpit solution, with the necessary data flows in place. This work package will not cover functional upgrades in either eCockpit or eDEP.

Other tasks (which may be long term tasks)

• code comments : the eCockpit software requires javadoc comments (taken from SDD?)

• use of packages : the current software is mono-package (i.e all in one directory) – the software requires structuring into sub-packages

ID SSP3

Work Package Input WP1.1, WP1.2

Work Package Output Integrated software


Delivery Date 04/06/04

6.3.3 WP2.2 : (Live AIR) eCockpit / ARTAS Integration

This work package shall produce the following configuration.

• eCockpit positions

• ARTAS connection (ARTAS provides the air situation)

• No eDEP GRD, CWP subsystems (note: if GRD/CWP subsystems are present, they will be based upon PROVE)

The business objectives here are (a) demonstrate eCockpit with real data, (b) use eCockpit at partner-sites for mixed-mode simulations i.e. cheaper alternative to MCS (the EEC’s high fidelity cockpit simulator)

This will require ASTERIX message support

• Cat 21 (ADS reports) : eCockpit -> ARTAS

• Cat 21 (ADS Reports) : ARTAS -> eCockpit

• Cat 244 (SMART) : eCockpit -> ARTAS (via SMART4)

• Cat 62 (traffic) : ARTAS -> eCockpit


Date : DD/MM/YYYY



Concerning CAT21/244, eCockpit MUST provide the following fields

• 24 bit ICAO address

• Callsign

• 3D position

• Ground Speed vector

• NIC/NAC or NUC separately for position and ground velocity

• Vertical rate

• Mode/Status

• Next four TCP (3d position, TCP type, ETO)

• Top of Climb (as TCP)

• Top of descent (as TCP)

• Selected Altitude

• Selected Airspeed Vector

• Selected vertical rate

• Horizontal acceleration

• Vertical acceleration

• Datalink type (1090, UAT, VDL-4)

eCockpit shall generate this info at a configurable rate (maximum once per second).

Concering CAT 62, the eCockpit shall receive and process the following data:

• latitude, longitude

• altitude (baro)

• ground speed vector

• vertical rate

• position uncertainty, speed uncertainty

• Callsign/Track Id

• Mode/Status

For Information - ARTAS : should be available on Linux Dec 2003. This would be important if the supplier intends to have a local copy of ARTAS for integration testing purposes.

ID SSP4

Work Package Input WP2.1, ARTAS Software or sample test data

Work Package Output Tested Software Test Plan Document.



Date : DD/MM/YYYY




6.3.4 WP2.3 : (Simulated AIR/GRD) eCockpit / eDEP AIR+GRD Integration

This work package results in the following configuration:

• EDEP running with eCockpit.

• EDEP supplying Pseudo Pilots (to navigate non-eCockpit flights)

• EDEP supplying GRD & CWP logic

• No ARTAS connection

The objective here is to have a complete concept demonstrator including FDPS/CWP and cockpit elements.

Topics for discussion:

Topic Description Comments

EDEP AIR Subsystem integration The eCockpit will be managed by the eDEP Pilot Manager (PM).

eCockpit receives traffic information from PM, and sends position reports to PM

Mandatory

EDEP CWP Upgrades If the eDEP CWP replaces the eCockpit CWP then we need to offer the same functionality

- Tracker tool upgrades

- Opening ecockpit via CWP

Mandatory

Final packaging ECockpit contains a nice launcher HMI. I assume they will wish to maintain this (for mono-process demonstrations only)

Recommended.

ID SSP5

Work Package Input WP2.1





Date : DD/MM/YYYY



6.3.5 WP2.4 : (Pseudo Live AIR / GRD) eCockpit/eDEP GRD/ ARTAS Integration

This configuration covers

• EDEP running with integrated eCockpits (but no PWPs)

• EDEP Supplying GRD and CWP logic

• ARTAS running with pre-recorded data, feeding both GRD and AIR subsystems.

• EDEP running with prepared scenarios, including a hand crafted correlation table (trackID -> FlightID).

In other words eDEP WILL NOT implement life flight plan feeds / correlation functions.

ID SSP6

Work Package Input WP2.1, WP2.2, WP2.3


Full Document Set Update (for all WP2)



6.3.6 WP2.5 : CDTI Upgrades for AVT

The AVT project has a number of extra requirements for the CDTI. A subset of these requires implementation within the eCockpit display.

ID SSP7

Work Package Input WP2.1, WP2.2, WP2.3




6.4 WP3 : A320/340 Cockpit

This work package will result in a multi-layout eCockpit capable of supporting both B777 and A320/340 cockpit layouts.

This work package will receive as input the necessary eCockpit URD (similar to the current one defining the B777 layout).

ID SSP11



Effort Estimate (Estimated) 8 man months


Date : DD/MM/YYYY




6.5 WP4 : CDTI for MCS/CoSpace

The COSPACE project has extra requirements with respect to the cockpit HMI.

- Need to change the MCDU (data input area) pages

- Different data on CDTI

Equally, the eDEP platform will require the following updates

- ASAS orders added to AIR subsystem (e.g. merge)

- Some basic data link to the eCockpit

ID SSP12





6.6 WP5: Sector Package 1 Demonstrator

This work package shall bring together various concepts such as CORA1, MTCD, DataLink, AMAN, ASAS1, into a single coherent demonstrator.

The following steps have been identified:

• Iteration 1 : AMAN & MTCD

• Iteration 2 : Interation 1 & DataLink (DOVE 1) & ASAS

• Iteration 3 : Iteration 2 & CORA2

Note: an initial version is needed for Maastrict 2005.

ID SSP13


Work Package Output Iteration 1 Demonstrator Test Plan Document.



ID SSP14





Date : DD/MM/YYYY




ID SSP15





TRS ANNEX eDEP SSP Demonstrator v1.0...TRS ANNEX eDEP SSP Demonstrator_v1.0.doc Date : DD/MM/YYYY...

Documents

Transcript of TRS ANNEX eDEP SSP Demonstrator v1.0...TRS ANNEX eDEP SSP Demonstrator_v1.0.doc Date : DD/MM/YYYY...