TITAN Turnaround Integration in Trajectory And Network. TITAN Model Software Design Document

Transcription

1 TITAN Turnarund Integratin in Trajectry And Netwrk Prject Number: TITAN Mdel Sftware Design Dcument CLASSIFICATION: PU ISSUE: 1.0 DATE: 13/07/2012 DOCUMENT REFERENCE Prject Wrk Package Partner Nature Number TITAN 02 CRI DEL 05 Prject c-funded by the Eurpean Cmmissin and TITAN cnsrtium.

2 TITAN Mdel Sftware Design Dcument DOCUMENT CONTROL Respnsible Organisatin Name Date Authr CRI Andrea Villa/ Irene Navarr 16/04/2012 Partners invlved ISA Tarja Kettunen 24/04/2012 Reviewer CRI Niclás Suarez 24/04/2012 Apprver INE Laura Serran 29/05/2012 Issue Date Authr DOCUMENT CHANGE LOG Affected Sectins / Cmments /04/2012 Andrea Villa / Irene Navarr All / New dcument /04/2012 Tarja Kettunen All / New sectins included /05/2012 Andrea Villa / Irene Navarr All / Integrate ISA cmments /05/2012 Andrea Villa / Irene Navarr/ Eva Punter /07/2012 Ana Sáez All / Integrate WP2 partners cmments Final versin after EC Apprval TITAN: Turnarund Integratin in Trajectry And Netwrk Page 2 f 19

3 TITAN Mdel Sftware Design Dcument DOCUMENT DISTRIBUTION T/Cc Organisatin Name T EC Remy Dens T INECO Laura Serran T T T T T BLUSKY SERVICES CRIDA CRIDA CRIDA CRIDA Steve Zerkwitz Niclas Suarez Eva Punter María Ruiz Irene Navarr T INECO Ana C. Sáez T INECO Jse Luis Martin T ISA SW Ian Crk T ISA SW Matthew Bray T ISA SW Zak Tibichte T ISA SW Tarja Kettunen T JEPPENSEN Alicia Grech T JEPPENSEN Jhn Butcher T T T T RWTH Aachen University RWTH Aachen University SLOT CONSULTING SLOT CONSULTING Sebastian Kellner Athanasis Katsars Rland Gurály Némi Král Cc SESAR JU Paul Adamsn Cc AENA/SESAR JU Alejandr Egid Cc AENA/SESAR JU Francisc Javier Fernández de Liger TITAN: Turnarund Integratin in Trajectry And Netwrk Page 3 f 19

4 TITAN Mdel Sftware Design Dcument TABLE OF CONTENTS EXECUTIVE SUMMARY INTRODUCTION PURPOSE DOCUMENT STRUCTURE INTENDED AUDIENCE ASSOCIATED DOCUMENTATION ABBREVIATIONS AND ACRONYMS SOFTWARE DESIGN DESIGN GOALS DATA S TRUCTURE CLAS S DIAGRAM TITAN MODEL INTERACTIONS Start f sub-prcesses Triggers Sub-Prcesses start time Resurces availability Interactin Pints End f sub-prcesses Defined clsing time Time extensin in a decisin pint Interactin Pints TITAN MODEL INFORMATION S ERVICES Passenger Flw Infrmatin Service (PFIS) Baggage Flw Infrmatin Service (BFIS) Resurce utilisatin infrmatin Milestne status infrmatin ANNEX 1: MODEL INTERACTION POINTS TITAN: Turnarund Integratin in Trajectry And Netwrk Page 4 f 19

5 TITAN Mdel Sftware Design Dcument LIST OF FIGURES Figure 1: TITAN Glbal Class Diagram Figure 2: PFIS Diagram Figure 3: PFIS Interface Figure 4: BFIS Diagram Figure 5: BFIS Interface Figure 6: Resurce infrmatin Figure 7: Milestnes infrmatin LIST OF TABLES Table 1: TITAN Interactin Pints TITAN: Turnarund Integratin in Trajectry And Netwrk Page 5 f 19

6 TITAN Mdel Sftware Design Dcument EXECUTIVE SUMMARY The present dcument cntains infrmatin abut hw the TITAN Mdel Sftware was designed based n the Single Aircraft Turnarund Mdel. It cntains a descriptin abut hw multiple flights are managed by the mdel and hw they interact with each ther. It als includes a descriptin f the implementatin f TITAN features int the mdel. Within this Sftware Design Dcument, narrative and graphical infrmatin f the glbal sftware design can be fund cmprising the class diagram and TITAN mdel interactins. TITAN: Turnarund Integratin in Trajectry And Netwrk Page 6 f 19

7 TITAN Mdel Sftware Design Dcument 1. INTRODUCTION 1.1 Purpse Purpse f this dcument is t prvide a descriptin f the TITAN mdel sftware design. It is based n and aligned with the Single Aircraft Turnarund Mdel. Fr this particular Sftware Design Dcument the fcus is placed n the interactins between mdel elements, TITAN interactins and infrmatin flw systems. 1.2 Dcument Structure This dcument is divided int tw sectins: - The first sectin is this intrductin which presents the purpse, structure, audience, references and abbreviatins and acrnyms f the dcument. - The secnd sectin describes the sftware design f the TITAN mdel. - Annex 1 lists the mdel interactin pints that allws the user t interact with the mdel. 1.3 Intended Audience This dcument may be distributed freely within the TITAN cnsrtium, bth t thse wh are invlved in the use f the mdel as well as stakehlders t check the cnsistency f the mdel. 1.4 Assciated Dcumentatin [1] TITAN D2.2 Single Aircraft Turnarund Mdel SW Design Dc, v0.4, March 2012 [2] TITAN_WP2_Interactin pints fr the Mdel, v0.3, March 2012 [3] TITAN D1.4 TITAN Operatinal Cncept Dcument Issue 1, v1.0, Octber 2010 [4] TITAN D2.1 Technical Requirements Dcument, v1.0, July Abbreviatins and Acrnyms ATC AS BFIS EIBT EOBT LS PFIS SW TITAN Air Traffic Cntrl/Cntrller Airside Baggage Flw Infrmatin Service Estimated In Blck Time Estimated Off Blck Time Landside Passenger Flw Infrmatin Service Sftware Turnarund Integratin in Trajectry and Netwrk TITAN: Turnarund Integratin in Trajectry And Netwrk Page 7 f 19

8 TITAN Mdel Sftware Design Dcument 2. SOFTWARE DESIGN 2.1 Design Gals The main bjective f the TITAN Mdel is t prvide a flexible sftware mdel which culd be used t emulate the multiple turnarunds that ccur every day at any airprt. This sftware is an extensin t the Single Aircraft Mdel sftware, where nly ne aircraft turnarund is simulated. This ability t replicate is ne f the Single Aircraft Mdel sftware design bjectives. The secnd bjective fcuses n including int the Single Aircraft Mdel additinal mdelling features t reprduce TITAN interactins and infrmatin flw systems. This bjective is achieved by including milestnes and their mnitring as user decisin pints as well as infrmatin systems f passenger and baggage flws. In shrt, the definitin f a single aircraft turnarund is the sequence f peratins that are required frm the time pint when an aircraft is statinary at the airprt with the wheel chcks in place, t the time pint when the chcks are remved and the aircraft receives ATC clearance t leave the stand. All these peratins prvide a service t the aircraft. Each service is cmpsed f several sub-prcesses as detailed in TITAN D2.2 Single Aircraft Turnarund Mdel SW Design Dc [1]. In reality, the turnarund prcess is made up f a cmplex set f ften interdependent subprcesses, many f which require the use f a limited set f shared resurces, and which can vary widely in the time and the way the prcesses are carried ut. A turnarund starts when the first f the sub-prcesses previusly defined fr that turnarund starts and it ends when the last prcess is cmpleted r clsed. The architecture lgic f the TITAN Mdel sftware is exactly the same as the ne f the Single Aircraft Mdel and data inputs and utputs wrk in a similar way. 2.2 Data structure The data structure fr the TITAN Mdel Sftware is basically the same as the ne described fr the Single Aircraft mdel. Fr a detailed descriptin see [1]. In summary, the glbal data mdel structure fr bth the Single Aircraft mdel and the TITAN mdel is divided int tw grups: data inputs and data utputs. The first data grup is related t traffic data, prcesses descriptin, turnarund mdelling, airprt resurces and simulatin parameters. They are used by the simulatin t mdel a cntext f turnarund peratins at an airprt. Output data are prvided autmatically by the mdel and they allw analyzing the mdel perfrmance. There are three types f input data which are used fr bth mdels. Data related t schedule: Schedule data are similar t thse f the Single Aircraft mdel. Schedule, arrival and departure manifest files cntain a cmplete traffic sample fr the perid t be simulated (e.g. ne day). Additinally in the multiple aircraft mdel, cnnecting passengers can als be included by detailing arrival and departure flight cdes and the number f passengers in cnnectin. Turnarund data: As in the Single Aircraft mdel, services prvided t the aircraft can be defined in a highly flexible way by the user via sub-prcesses definitin (e.g. cleaning r baggage unlading) and intercnnectins between sub-prcesses can be implemented. TITAN: Turnarund Integratin in Trajectry And Netwrk Page 8 f 19

9 TITAN Mdel Sftware Design Dcument Data related t the time cnsumptin f entities 1 : Entities cnsume time by mving frm ne pint t anther at the airprt (e.g. passengers walk frm check-in desk t security cntrl), by waiting in a queue (e.g. barding gate queue) r by using resurces (e.g. time at a passprt desk). Resurces include bth fixed resurces which are part f the airprt infrastructure, such as baggage drps, check in desks, passprt desks r gates and mbile resurces that can be mved arund the airprt t supprt a turnarund, such as baggage lad belts, catering trucks, buses etc. The latter als allws the user t define specific parameters fr each resurce such as quantity, capacity, time t aircraft, time at aircraft, etc. Mrever, new simulatin parameters and data inputs were intrduced int the mdel as part f the multiple turnarund extensin: The mdel includes a delay functinality which allws simulating flights arriving late. The user can chse between a fixed delay value and a delay distributin (e.g. nrmal distributin) as well as the percentage f delayed flights. Fr the TITAN mdel simulatins, there are additinal input data elements which aim at prviding additinal infrmatin t the user when the simulatin is running (e.g. milestnes) r defining special airprt resurces which are t be used under certain circumstances that are presented t the user in the curse f the simulatin (e.g. emergency Desk Pls fr check-in, baggage drp, security cntrl r passprt cntrl). If a prcess is delayed TITAN mdel allws the ptinal use f these special airprt resurces t help mitigate any related prblems. Additinal scenari settings als allw fixing parameters like gate availability perid which is the time perid needed fr a new gate t be reallcated t an arriving flight if the initially allcated gate is being used by anther delayed flight. Grund handling waiting perid fr a delayed prcess can als be defined. There is als an input data file t define which user interactin dialgs are presented t the user and hw they are presented t him. Output data are prvided by means f text files where the different events are registered in chrnlgical rder. Data utputs prvided fr the single turnarund are nw replicated fr each aircraft turnarund. 2.3 Class diagram A glbal class diagram abut TITAN mdel is shwn in Figure 1. A glbal mdel class diagram was presented in full detail in [1]. It shwed hw turnarund subprcesses are defined by using ndes depending n the turnarund type. Different turnarund types may be defined accrding t flight and airline characteristics and each ne can cntain different sub-prcesses, thrugh which entities flw during the simulatin. During the simulatin, interactins between defined elements ccur. This allws simulating real airprt peratins where multiple aircraft turnarund sub-prcesses are carried ut in parallel. Firstly, each airprt has different resurces defined. Accrding t their prperties and characteristics resurces can be shared amng all aircraft. This establishes a relatinship between 1 TITAN mdel cnsiders fllwing entities: passengers, baggage and peratins. TITAN: Turnarund Integratin in Trajectry And Netwrk Page 9 f 19

10 TITAN Mdel Sftware Design Dcument different aircraft turnarund sub-prcesses (e.g. if all baggage lad belts are ccupied at a certain time pint, the baggage unlading prcess f a new flight cannt start.) Secndly, sme sub-prcesses may be carried ut in parallel but sme may be dependent n the cmpletin f ther sub-prcesses. This situatin is mdelled by using triggers 2 after having established the relatinships between the varius sub-prcesses. *In the class diagram the element prcess refers t tw TITAN peratinal cncept terms [3]: prcess and sub-prcess. Accrding t the Technical requirements dcument, the cnceptual definitin f the element prcess is the serie f actins twards a particular result, as an example, t lad mail/carg [4]. Data mdels f bth TITAN mdels (single and multiple) are based n this definitin and refers t prcess and sub-prcess peratinal cncept terms using the same data mdel element: prcess. Figure 1: TITAN Glbal Class Diagram Finally, TITAN services are implemented by using milestnes 3. The mdel uses a default set f milestnes, based n the list and definitins given in the internal dcument [2]. This list includes TITAN peratinal cncept milestnes and sme thers that were cnsidered needed fr the prper mdelling perfrmance. The mdel s default milestnes can be mdified by the user t a certain degree. It has been prved necessary t define specific cnditins fr milestne accmplishment/cmpletin in certain prcesses. When a milestne is missed r is ging t be 2 Triggers can be the start/end f ther sub-prcesses that launch the start f a sub-prcess. They are used t define the turnarund sequence f sub-prcesses [1]. MilestneTriggers can be the start/end f a sub-prcess that determines the milestne achievement. 3 Milestnes are ntificatins displayed when a prcess starts r has been cmpleted [1] TITAN: Turnarund Integratin in Trajectry And Netwrk Page 10 f 19

11 TITAN Mdel Sftware Design Dcument missed a user interactin dialg appears where a set f pssible decisins 4 defined t be applicable are presented t the user. The decisin made by the user aims at minimising delay and can affect the prcess, the entity flw r a resurce utilisatin. The user can decide by using TITAN Mdel Infrmatin Services. 2.4 TITAN Mdel interactins Bth Single Aircraft Turnarund Mdel and TITAN mdel are designed t mdel the service prvisin t aircraft. Accrding t different aircraft characteristics and airline peratinal cncepts, different sub-prcesses can be defined fr each turnarund. As detailed befre, a turnarund starts when the first f the sub-prcesses defined fr that turnarund starts and it ends when the last sub-prcess is cmpleted r clsed. It is imprtant t ntice that the start f a turnarund prcess may nt cincide with in blck time but with sme landside sub-prcesses such as check-in r security prcess Start f sub-prcesses The start f a sub-prcess is related t ne r mre f the fllwing features: Triggers TITAN mdel implements tw types f triggers; prcess_start r prcess_cmplete. When a trigger is defined it is necessary t chse what type f trigger is being implemented and which the surce sub-prcess is. Fr example, barding culd have a prcess_cmplete trigger related t refueling. In this case, refueling is the surce prcess. That means that barding is nt allwed t start befre refueling is cmpleted Sub-Prcesses start time The start time f a sub-prcess can be defined as a sub-prcess parameter. TITAN mdel allws defining the start time f a sub-prcess as an ffset frm an updated r initial event. Fr example, check-in prcess start time can be defined as an ffset f tw hurs frm the initial EOBT Resurces availability Each sub-prcess requires several resurces fr carrying ut its actins. If the resurce is available, the sub-prcess acquires it and entities can flw thrugh the sub-prcess. If the resurce is nt available, the sub-prcess waits until the resurce is made available. This results in an increase in the sub-prcess executin time. As detailed in [1] there are tw different resurce types: fixed resurces and mbile resurces. Fixed resurces are related t a fixed lcatin at the airprt (check-in desks, baggage drps, etc) while mbile resurces mve frm ne lcatin t anther and time parameters such as time t aircraft r time at aircraft can be defined fr them. The resurce utilisatin time impacts sub-prcess duratin. 4 Decisin pints r interactin pints assciated t milestnes are cntrl pints that display a user interactin dialg when the milestne cannt be achieved at the planned time. They allw interacting with the mdel in rder t decide which sub-prcesses will cntinue and hw by chsing ne actin f a predefined list f actins that the mdel prvides t the user [1]. TITAN: Turnarund Integratin in Trajectry And Netwrk Page 11 f 19

12 TITAN Mdel Sftware Design Dcument Mst f the resurces are shared between all aircraft but sme f them can be allcated t a specific airline such as baggage drps. Resurces are gathered in a pl and the mdel chses ne randmly frm the suitable pl each time it is required. Sub-prcesses can use resurces in different ways: One time resurce strategy means that the sub-prcess uses and reserves the resurce fr the whle sub-prcess duratin. This is, fr example, used t mdel a barding agent. The barding agent stands at the barding gate frm the time the barding gate is pen up t its clsing time even if there are ccasinally n passengers barding. Shared resurce strategy. Resurces have an assciated utilisatin time and nce an entity has finished using a resurce it is made available fr use by anther entity in the same r anther sub-prcess. Fr example, a PRM passenger may use an ambulift fr barding but, nce the passenger reaches the aircraft, the ambulift is free fr use by anther subprcess. Acquire and Release resurce strategy. Resurces can be acquired at ne time pint f a sub-prcess and be released later n in anther sub-prcess. Fr example, a PRM passenger may need an assistant frm check-in desk t barding gate. Interactins between aircrafts nly invlve the availability f resurces, especially the availability f the allcated gate Interactin Pints The TITAN mdel has been designed t use a set f predefined interactin pints t issue a user interactin dialg when the turnarund prcess f the flight is nt prceeding accrding t initial planning. Interactin pints are input data fr the mdel where the user has certain flexibility as t which interactin pints are active and which are the pssible slutins presented t him fr decisin-making. When the interactin dialg appears the simulatin is paused until the user chses ne slutin t the particular critical situatin. The user has access t backgrund infrmatin t justify his/her decisin-making, namely the Passenger Flw Infrmatin Service (PFIS) and the Baggage Flw Infrmatin Service (BFIS). The decisin made can mdify the curse f the simulatin but it may als have n impact. Implemented interactin pints int TITAN mdel can be classified as: Sub-prcess is late t start: This interactin pint will be displayed if a given subprcess is nt starting n time. It can appear due t lack f resurces r because there is a trigger t a previus unfinished sub-prcess. Several ptins can be presented t the user in the interactin windw: Priritize the use f resurces. Start the sub-prcess immediately. Wait fr a maximum f x minutes after which the dialg is shwn again. D nthing (wait fr sub-prcess t start) Grund handling is late t start: If grund handling cannt start as scheduled due t delay in the first grund handling sub-prcess attributed t lack f resurces, the TITAN interactin windw will be presented with the fllwing chices: Priritize the use f resurces Start a different grund handling sub-prcess TITAN: Turnarund Integratin in Trajectry And Netwrk Page 12 f 19

13 TITAN Mdel Sftware Design Dcument Cancel sub-prcess Wait fr a maximum f x minutes after which the dialg is shwn again D nthing A table shwing all default interactin pints f the mdel is prvided in Annex End f sub-prcesses The end f a sub-prcess can be determined thrugh different features Defined clsing time Sub-prcess definitin ffers several ptins fr clsing the sub-prcess. Each sub-prcess may have a pre-defined duratin after which the sub-prcess is clsed. Clsing time can als be defined as an ffset frm a specific event (e.g. check in prcess can be clsed an ffset f 30 minutes frm EOBT). If the last entity passes successfully thrugh the sub-prcess befre the estimated clsing time the user may als chse t clse the sub-prcess in advance. If cmpletin time is clse and nt all entities have gne thrugh the sub-prcess ndes, the subprcess can either be clsed immediately r the user can chse t wait fr a maximum f x minutes Time extensin in a decisin pint Decisins made at TITAN interactin pints can affect sub-prcess clsing time. An unfinished sub-prcess can be clsed r extended by the user at a particular interactin pint. Priritizing resurce allcatin r mdifying entity flw can result in an ptimizatin f the glbal prcess duratin Interactin Pints Implemented interactin pints related t end f sub-prcesses can be classified as: Sub-prcess is late t finish: If a sub-prcess is nt cmpleted by its defined clsing time an interactin dialg will appear shwing this infrmatin. At this interactin pint the user can: Clse the sub-prcess immediately Wait fr a maximum f x minutes Wait fr the sub-prcess t be cmpleted D nthing (wait r nt accrding t default sub-prcess settings) Open a new desk (t remain pen fr x at mst) Search fr entities (passengers) t mve (e.g. t the frnt f the queue) EIBT is ging t be missed: The gate allcated t an arriving aircraft may nt always be available due t a delay f the previus aircraft turnarund prcess at the given gate. In this case an interactin dialg appears and it is pssible t chse ne f the fllwing ptins: Wait fr the gate t be made available TITAN: Turnarund Integratin in Trajectry And Netwrk Page 13 f 19

14 TITAN Mdel Sftware Design Dcument Chse a randm gate * Chse an alternate gate manually * (* frm a subset f gates estimated t be available fr the next x minutes) EOBT is ging t be missed: When the scheduled EOBT is ging t be missed due t sub-prcesses still running, an alert is issued t the user in the frm f an interactin dialg with the fllwing ptins: D nthing (wait fr the sub-prcesses t be cmpleted) Priritize the use f resurces Leave immediately (all sub-prcesses are clsed) Clse sub-prcess(es) frm list A table shwing all default interactin pints f the mdel is prvided in Annex TITAN Mdel Infrmatin Services Passenger Flw Infrmatin Service (PFIS) Figure 2 shws a glbal structure f the PFIS. PFIS MILESTONES MILESTONE TRIGGER* DECISION POINT CHECK-IN SECURITY PASSPORT BOARDING Pax nt checked-in yet Missed check-in At check-in desk/queue Pass security desk Pass passprt desk At barding gate/queue Pass barding gate *Milestne Trigger can be the start/end f a sub-prcess that determines the milestne achievement. TITAN mdel uses tw different trigger methds: running fr the start f the sub-prcess and cmpleted fr the end f sub-prcess (see sectin 2.5.4) Figure 2: PFIS Diagram PFIS has several mnitring pints where the mdel btain infrmatin abut the turnarund perfrmance at different sub-prcesses (check-in, security, passprt and barding) based n defined milestnes accrding t TITAN Operatinal cncept [3]. Each Milestne is assciated t a milestne trigger that determines hw it is achieved r missed. In case the milestne is missed, an interactin dialg may appear setting up the crrespnding decisin pint. PFIS infrmatin is available at any mment during the simulatin bth during TITAN and Nn-TITAN simulatins 5 and als when an interactin dialg appears. Figure 3 Errr! N se encuentra el rigen de la referencia.shws an example f the infrmatin prvided by PFIS at an interactin pint. In this example an interactin windw appears as 5 PFIS infrmatin is available but has nt impact in the turnarund peratin as user can nt d anything with it TITAN: Turnarund Integratin in Trajectry And Netwrk Page 14 f 19

15 TITAN Mdel Sftware Design Dcument barding prcess is ging t finish late because at the estimated clsing time 10 passengers have nt checked-in yet. PFIS can be used t identify the lcatin f all missing passengers. In this case, five passengers are lcated at the check-in desk r queue. PFIS als shws which check-in desks are being used. Figure 3: PFIS Interface Baggage Flw Infrmatin Service (BFIS) Figure 4 shws a glbal structure f the BFIS. BFIS MILESTONES MILESTONE TRIGGER* DECISION POINT CHECK-IN Pass check-in desk BAGGAGE LOADING AIRSIDE Pass check-in desk Arrived at end BAGGAGE LOADING LANDSIDE Pass check-in desk Arrived at end Figure 4: BFIS Diagram TITAN: Turnarund Integratin in Trajectry And Netwrk Page 15 f 19

16 TITAN Mdel Sftware Design Dcument BFIS is als available t the user as a separate windw in the user interface and n interactin dialg bxes. BFIS definitin is similar t PFIS and prvides infrmatin n check-in prcess and baggage lading and unlading. Figure 5 shws the infrmatin prvided by BFIS when an interactin dialg during a lading prcess appears. In this case, baggage lading airside is ging t start late. BFIS windw allws the user t knw where all baggage fr that flight is. Figure 5: BFIS Interface Resurce utilisatin infrmatin Resurce utilisatin infrmatin int TITAN Mdel is always available in a separate windw in the user interface and can als be shwn n interactin dialg bxes. This way, the user can search fr resurce usage and status infrmatin befre taking a decisin t cntinue the simulatin. The resurce infrmatin windw appears and the simulatin is paused until the user clses it. Infrmatin shwn fr each resurce, bth airprt mbile and fix resurces, includes the number f sub-prcesses r entities using it, the current queue size, the maximum queue size, minimum and maximum waiting time and average waiting time (average weight). Figure 6 shws infrmatin related t check-in desks. TITAN: Turnarund Integratin in Trajectry And Netwrk Page 16 f 19

17 TITAN Mdel Sftware Design Dcument Figure 6: Resurce infrmatin Milestne status infrmatin Milestne infrmatin is always available while the simulatin is running in the mdel interface. The user can pre-define the milestnes that will be shwn as an input file by detailing the turnarund prcess, the sub-prcesses, the milestne names and the trigger methd. Figure 7Figure 7: Milestnes infrmatin shws milestne infrmatin during a simulatin. The first tw clumns shw simulatin time and peratin. Fr each sub-prcess several milestnes can be defined (e.g. ne fr the start f a sub-prcess and ne fr the end). Milestne Name, Target, and Trigger Methd clumns include relevant infrmatin abut the milestne definitin: The name f the milestne The turnarund sub-prcess linked t the milestne. The trigger methd that shws hw the milestne is defined. It may be cmpleted when the milestne refers t the end f a sub-prcess (it indicates that the milestne will be achieved when the target sub-prcess is cmpleted) r running when the milestne refers t the start f the target sub-prcess. State clumn shws if the milestne was cmpleted n time (in this case the rw is shwn in green), if there is a risk f missing the milestne (in yellw) r if the milestne was missed which means that the sub-prcess did nt start r finish n time (red lines). TITAN: Turnarund Integratin in Trajectry And Netwrk Page 17 f 19

18 TITAN Mdel Sftware Design Dcument Figure 7: Milestnes infrmatin TITAN: Turnarund Integratin in Trajectry And Netwrk Page 18 f 19

19 TITAN Mdel Sftware Design Dcument ANNEX 1: MODEL INTERACTION POINTS Milestne ID Sub-prcess Type f Interactin Pint Descriptin Interactin Pint Trigger M7 In blck Prcess late t start EIBT is ging t be missed Original gate nt available M8 Baggage Unlading Baggage Lading Catering Cleaning De-icing Pwer Supply Refuelling Prcess late t start Start f Grund Handling is ging t be missed Grund handling cannt start due t lack f resurces fr 1st prcess M11A Barding Prcess late t start Start f Barding is ging t be missed Prcess cannt start due t lack f resurces M11B Barding Prcess late t cmplete End f Barding is ging t be missed Prcess nt cmpleted at scheduled time M15 Off blck Prcess late t cmplete EOBT is ging t be missed Prcesses nt cmplete at scheduled time M17 Check-In Prcess late t cmplete End f Check-In is ging t be missed Prcess nt cmplete at scheduled time M18 Security Prcess late t cmplete End f Security Cntrl is ging t be missed Prcess nt cmplete at scheduled time M19 Passprt Prcess late t cmplete End f Passprt Cntrl is ging t be missed Prcess nt cmplete at scheduled time M20 De-barding Prcess late t start Start f De-barding is ging t be missed Prcess cannt start due t lack f resurces M21 Baggage lading LS Prcess late t cmplete End f Baggage Lading is ging t be missed Prcess nt cmplete at scheduled time M22 Baggage Unlading Prcess late t start Start f Baggage Unlading is ging t be missed Prcess cannt start due t lack f resurces M23 Baggage lading AS Prcess late t start Start f Baggage Lading AS is ging t be missed Prcess cannt start due t lack f resurces M24 Refuelling Prcess late t start Start f Refuelling is ging t be missed Prcess cannt start due t lack f resurces M25 Pushback Prcess late t start Start f Pushback is ging t be missed Prcess cannt start due t lack f resurces M26 De-icing Prcess late t start Start f De-icing is ging t be missed Prcess cannt start due t lack f resurces * TITAN Operatinal cncept [3] cnsiders the sub-prcess Baggage Lading; hwever the mdel has divided it int tw sub-prcesses (Baggage Lading LS and Baggage Lading AS) fr mdelling purpses. Table 1: TITAN Interactin Pints TITAN: Turnarund Integratin in Trajectry And Netwrk Page 19 f 19