FORM 2
THE PATENTS ACT, 1970 (39 of 1970)
&
THE PATENS RULES, 2003 PROVISIONAL SPECIFICATION [See section 10, Rule 13]
METHOD AND SYSTEM FOR DELIVERING
PASSENGER RELATED DYNAMIC AND
REAL-TIME INFORMATION, IN GRAPHICAL
OR CHARACTER FORM, FOR MONITORING
PASSENGER RELATED SERVICES
ONBOARD A VEHICLE
THE GLOBAL TRAVEL SOLUTIONS, A COMPANY INCORPORATED UNDER THE COMPANIES ACT, 1956, WHOSE ADDRESS IS 3RD FLOOR, THE EAGLES FLIGHT, SUREN ROAD, ANDHERI (EAST), MUMBAI 400093
THE FOLLOWING SPECIFICATION
DESCRIBES THE NATURE OF THIS INVENTION.


FIELD OF THE INVENTION
The present invention relates to delivery of passenger information for monitoring passenger related services onboard a vehicle. More specifically, the invention relates to providing crew and other interested parties with dynamic and real-time passenger, travel and vehicle information onboard the vehicle.
BACKGROUND OF THE INVENTION
Currently, the passenger travel information is available on board the vehicle in a printed form. This leads to problems of timely delivery of printed information, problems in distribution of information to the crew and other interested parties, loss of information, if print out is torn, soiled, damaged or rendered unusable and difficulty in retrieval of specific information. Such information is often incomplete and not updated to reflect the latest up-to-the-minute information. This can lead to:
1. Inefficient service
2. Difficulties in handling emergencies
3. Inability to respond to special requirements of passengers
4. Impediments to priority service to special passengers
5. Non-availability of information on time
6. Loss of valuable information
7. Non- retrieval of information when needed and at the place and time needed
8. Only static one-time information being available as of the time of departure of the vehicle


9. Complex, cumbersome, unreliable and error-prone distribution of information to the various members of the crew and other interested parties
10. Information available being limited to the size of the print out that does not include various crucial passenger related data that can enhance passenger services and facilitate new services not even contemplated today. Such information could include, but is not limited to passenger profile, passenger requests, passenger meal preference, other passenger information, passenger value, passenger travel information, infant information, seat occupancy information for individual seats, rowwise, class-wise, zone-wise
11. Information not being available at the time and place most conducive for provision of efficient and personalized passenger services
In view of the foregoing, there is a current need in the art to automate the delivery and presentation of dynamic and real-time passenger travel information to crew and other interested parties, on board a vehicle in a manner which reduces passenger service time, and improves quality of service to passengers, facilitates introduction of new services not contemplated or available today and which allows crew and other interested parties more time to focus on other responsibilities.
SUMMARY OF THE INVENTION
The present invention solves the above problems by providing dynamic and realtime passenger travel information. This dynamic and real-time passenger travel


information can include passenger information, trip information, and vehicle timing information. Providing dynamic and real-time information in electronic form on a data system with a display monitor or other humanly perceivable system on board the vehicle is a radical change to the way information is presently given on paper and the way, crew and other interested parties can interact with and provide service to their passengers.
This would result in timely delivery of information, easy distribution of information to the crew and other interested parties, no loss of information and easy and retrieval of specific information. Such information is always complete and updated to reflect the latest up-to-the-minute information. This would lead to:
1. Efficient service
2. Easy in handling emergencies
3. Ability to respond to special requirements of passengers
4. Facilitate priority service to special passengers
5. Availability of information on time
6. Availability of valuable information
7. Easy retrieval of information when needed and at the place and time needed
8. Dynamic and real-time information being available as of the time of departure of the vehicle
9. Easy, efficient distribution of information, free from errors to the various members of the crew and other interested parties


10. Information available in electronic form and not limited in size that provide various crucial passenger related data that can enhance passenger services and facilitate new services not even contemplated today. Such information could include, but is not limited to passenger profile, passenger requests, passenger meal preference, other passenger information, passenger value, passenger travel information, infant information, seat occupancy information for individual seats, rowwise, class-wise, zone-wise
11. Information is available at the time and place most conducive for provision of efficient and personalized passenger services
The exemplary system can comprise a host Departure Control System (DCS), which is a trip and passenger acceptance, control system, a Passenger Information Delivery & Display System ("PIDDS"), comprising of a PIDDS server and PIDDS client and a communication network. The departure control system comprises a database of passenger records, vehicle configuration records and vehicle timing information records. The departure control system also contain as a part of the passenger record, information of seat allocation of each passenger and information of Passenger Requests, Passenger Meal Preference, Other Passenger information, Passenger Value. The PIDDS server comprise of a data system that communicates with the PIDDS client and DCS system to retrieve information from DCS and enable the PIDDS client to display information. The PIDDS client comprises a data system on board the vehicle for passenger information with a display monitor that can be used by the crew and other


interested parties to access and display the information to service the passengers. The communication network is connected to each of these systems and facilitates the exchange of information between the systems. Changes to passenger information, seat information or vehicle timing information, can be stored in DCS. The DCS system can forward passenger information, seat information and vehicle timing information to the PIDDS server through the communication network. The PIDDS client has an computer-implemented method for collecting, retrieving and displaying vehicle seat specific passenger occupancy information individually or collectively, that includes Passenger Profile, Passenger Requests, Passenger Meal Preference, Other Passenger information, Passenger Value, Passenger Travel Information, Infant information and the ability to retrieve seat occupancy information for individual seats, rowwise, class-wise, zone-wise to crew and other interested parties, onboard a vehicle comprising the steps of: continuously transmitting and updating the passenger-specific information from a host system to a processing system, wherein displaying the passenger-specific information on a display system coupled to the processing system, onboard the vehicle.
Various embodiments of the invention described herein are capable of the following:
• electronically compiling, processing and providing information related to
passengers, trip and vehicle related information to crew and other
interested parties on board the vehicle


» collecting, retrieving and displaying vehicle seat specific passenger occupancy information individually or collectively, that includes Passenger Profile, Passenger Requests, Passenger Meal Preference, Passenger Value, Passenger Travel Information, Infant information and Other Passenger information.
• retrieving seat occupancy information for individual seats, row-wise, class-wise, zone-wise to crew and other interested parties, onboard a vehicle
• continuously transmitting and updating the passenger-specific information from a host system to a processing system, wherein providing the passenger-specific information on a display monitor or other humanly perceivable system coupled to the processing system, onboard the vehicle.
• providing an initial screen, comprising general vehicle seat layout and information, onboard the vehicle, for a trip, on a display monitor or other humanly perceivable system prior to transmission of the passenger-specific information.
• displaying passenger-specific seat assignment information and associated passenger information to crew and other interested parties.
• continuously receiving and updating the passenger-specific information from a host data system at a processing system and providing information on display monitor or other humanly perceivable system coupled to the processing system, onboard the vehicle.


• receiving and updating the final and complete passenger-specific information and associated passenger information at the closure of passenger acceptance to the vehicle.
• displaying passenger-specific seat assignment information and associated passenger information as mentioned in claim 1, to crew and other interested parties comprising the steps of: continuously receiving and updating the passenger-specific information from a host data system at a processing system; providing information on a display monitor or other humanly perceivable system coupled to the processing system, and onboard the vehicle, in response to a signal from the crew or other interested parties.
• retrieving and displaying onboard the vehicle, the vehicle seat specific passenger occupancy information individually or collectively, that includes Passenger Profile, Passenger Requests, Passenger Meal Preference, Other Passenger information, Passenger Value, Passenger Travel Information, Infant information, seat occupancy information for individual seats, row-wise, class-wise, zone-wise onboard a vehicle based on specific criteria chosen by a member from the crew or other interested parties.
The aforementioned advantages of the invention, as well as additional advantages thereof, are more fully described by the detailed description of exemplary embodiments and the accompanying drawings.


BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a functional block diagram illustrating the components of an exemplary
system. This exemplary system comprises a Departure Control System (DCS), a
Passenger Information Delivery and Display System Server (PIDDS server), a
Passenger Information Delivery and Display System Client (PIDDS client), and a
communication network.
FIG. 2 is a block diagram illustrating an exemplary embodiment comprising of
PIDDS server, PIDDS client, clock and DCS.
FIG. 3 is a block diagram illustrating an exemplary embodiment comprising of
PIDDS client, Monitor, User and PIDDS Server.
FIG. 4 is a flow diagram illustrating the process of downloading information from
DCS to PIDDS server.
FIG. 5 is the flow diagram illustrating the process of downloading information
from PIDDS server to PIDDS client.
FIG. 6 is the flow diagram illustrating the process of actuating the PIDDS client to
display screens on the User's monitor.
FIG. 7 is a screen display illustrating an exemplary embodiment of the Summary
Report Screen that can display the flight number, flight date, aircraft type and
flight timing information. The Summary Report Screen can also display summary
information of Passengers, Meals, SSRs (Special Service Requests), Onward
Connections and Passenger Seating Information.
FIG. 8 is a screen display illustrating an exemplary embodiment of Meals
information.


FIG. 9 is a screen display illustrating an exemplary embodiment of Passenger
information.
FIG. 10 is a screen display illustrating an exemplary embodiment of SSR
information.
FIG. 11 is a screen display illustrating an exemplary embodiment of Onward
Connection information.
DESCRIPTION OF EXEMPLARY EMBODIMENTS OF THE INVENTION
The present invention provides a method and system for providing dynamic and
real-time passenger travel information. The passenger travel information typically
consists of passenger information, trip information and vehicle timing information.
Passenger travel Information is made available on display monitor or other
humanly perceivable system through a data storage and retrieval system
provided by a program on board the stationary or moving vehicle to the crew and
other interested parties. The present invention allows quick retrieval of relevant
information to provide faster and better service to the passengers and providing
additional time to the crew and other interested parties to discharge other
responsibilities on a stationary or moving vehicle.
The passenger travel information can be downloaded by the crew and other interested parties from the trip and passenger acceptance control system as soon as passenger acceptance for a specific journey of a vehicle commence. The information can be updated in dynamic and real-time mode periodically and


the final list is downloaded on completion of passenger acceptance process for
the specific trip of the vehicle.
Passenger information consists of number of passengers booked for the trip
(booked load, number of passengers accepted for the trip (actual load),
passenger profile, passenger requests, passenger meal preference, other
passenger information, passenger value, infant information and seat occupancy
information.
Seat information provides information on type and location of each seat in the
vehicle. The seat information is available for type of each seat, window, aisle or
middle and the nature of seat depending on the cabin the seat is located. Seat
information can be retrieved for the entire vehicle, cabin wise, zone wise, row
wise or for an individual seat.
Vehicle timing information consists of schedule departure time and schedule
arrival time for the trip of the vehicle as well as the estimated departure time and
estimated arrival time.
The crew and other interested parties can get specific information on passenger
travel typically consisting of passenger information, trip information and vehicle
timing information as required through different screens namely Summary Report
Screen, Meals View Screen, Passenger View Screen, SSR View Screen and
Onward Connection View Screen as described in Screen Display section.
An exemplary embodiment can comprise of air travel, where the vehicle is an
aircraft and the trip is a flight by a commercial airline. Within a predetermined
time after the passenger acceptance process for the trip has commenced the


program may be started on the PIDDS client system. The vehicle trip number which is airline code flight number and date for a commercial flight is provided as an input. The PIDDS client fetches the passenger travel information, seat information and vehicle timing information from the PIDDS server. The PIDDS server in turn fetches the information from the trip and passenger acceptance control system which is the Departure Control System (DCS). After the information is fetched by the PIDDS client the first screen of the Passenger Dashboard called Summary Report is displayed on the monitor attached to the PIDDS client system. Other screens displayed by the Passenger Dashboard are Meals View, Passenger View, SSR (Special Service Request) View and Onward Connection View through clickable icons on the dashboard. FIGS. 1, 2 and 3 are block diagrams illustrating components of an exemplary embodiment of the present system. FIGS. 4, 5 and 6 are flow diagrams illustrating exemplary methods for providing updated passenger information, trip information and vehicle timing information. FIGS. 7, 8, 9, 10 and 11 are screen displays illustrating an exemplary embodiment of the current invention. Those skilled in the art will recognize that the present invention may be implemented in a stand-alone or in a distributed computing environment. In a distributed computing environment, program modules may be physically located in different local and remote memory storage devices. Execution of the program modules may occur locally in a stand-alone manner or remotely in a client/server manner. Examples of such distributed computing environments include local area


networks of an office, enterprise-wide computer networks, and the global
Internet.
Referring now to the drawings, in which like numerals represent like elements
throughout the several figures, aspects of the present invention and an
exemplary operating environment will be described.
System Architecture
Turning now to FIG. 1, an exemplary embodiment of the present invention is described.
FIG. 1 is a functional block diagram illustrating the components of an exemplary system. This exemplary system 100 comprises a Departure Control System (DCS) 101, a Passenger Information Delivery and Display System Server (PIDDS server) 102, a Passenger Information Delivery and Display System Client (PIDDS client) 103, and a communication network 104. The DCS 101 is the host database of record. This DCS 101 holds all information about passengers, flight information, aircraft information that will be maintained, updated, and downloaded to the PIDDS server 102. This system operates by query and response, and provides updated information on passengers accepted to the PIDDS server 102. On completion of passenger acceptance process the final updated information is sent by the DCS 101 to the PIDDS server 102. The PIDDS server 102 is a transaction service system and a data repository of information retrieved from DCS 101 consisting of passenger information, flight information and aircraft information. The PIDDS server 102 stores real-time passenger information that is downloaded by the PIDDS client 103.


The PIDDS client 103 is also a data repository and a suite of computer programs to provide a dashboard to the crew and other interested parties with summary and detail information of passenger information, meal information, SSR information and onward connection information. The data repository is updated with data sent by the PIDDS server 102.
The communication network 104 is a network communications system that could be a Local Area Network, Wide Area Network, Wireless Network or Internet. The communication network 104 allows the DCS 101, the PIDDS server102, the PIDDS client 103 to communicate with each other.
All changes to flight, aircraft or passenger information are stored in the DCS 101. The DCS 101 forwards information to the PIDDS server 102. The information is transferred from DCS 101 to PIDDS server 102 by scheduled transactions or specific requests from the PIDDS server 102 using the communication network 104. The PIDDS client 103 also uses the communication network 104 to periodically and on request download information from PIDDS server 102 till passenger acceptance process is complete, when the final download is performed.
FIG. 2 is a block diagram illustrating an exemplary embodiment 200 comprising of PIDDS server 201, PIDDS client 202, clock 203 and DCS 207. The PIDDS server 201 comprises a data repository 206, a PIDDS server manager 205 and a PIDDS client manager 204. The data repository 206 comprises of passenger data, flight information data and aircraft information data downloaded from DCS 207 using a transaction interface.


The PIDDS server manager 205 has the programs for providing the transaction interface to DCS 207 and scheduling and executing transactions using the interface to receive updated information from DCS 207 on passenger information, flight information, aircraft information and updating the data repository 206. The transactions from PIDDS server 201 to DCS 207 can be triggered by a clock 203 or by a PIDDS client 202. The PIDDS client manager 204 authenticates PIDDS clients 202 accessing the server and controls the role based access procedure of PIDDS clients accessing the PIDDS server 201. FIG. 3 is a block diagram illustrating an exemplary embodiment 300 comprising of PIDDS client 301, Monitor 305, User 306 and PIDDS Server 307. The PIDDS client 301 comprises a data repository 304 a PIDDS Client Program Manager 303 and a User manager 302. The data repository 304 comprises of passenger data, flight information data and aircraft information data downloaded from PIDDS server 307 using a program interface, master tables, user tables, role based access rights tables and screen definitions.
The PIDDS Client Program Manager 303 has the programs for providing the Program interface to PIDDS server 307 and using the interface to receive updated information from PIDDS server 307 on passenger information, flight information, aircraft information and updating the data repository. The interface can be triggered by a User 306 using a Monitor 305. The PIDDS Client Program Manager 303 can be actuated by the User
306 using a Monitor 305 to display various screens from the Summary screen to detail screens on Passenger Information, Meal Information, SSR information and


Onward connection information. The User Manager 302 authenticates Users 306 accessing the PIDDS client 301 using Monitor 305 and controls the role based access procedure of User 306 accessing the PIDDS client 301.
The Flow Diagrams
FIG. 4 is a flow diagram 400 illustrating the process of downloading information from DCS to PIDDS server. The process starts with step 401 where a request to download information from DCS is generated by a trigger. The trigger is generated either by the expiry of a preset time driven clock or a user request. The request for download is validated in 402 for valid flight number, date and time for permissible flights. If the request is found to be valid step 403 is executed where the request is parsed and converted into a proper presentation format to retrieve passenger information, seat information and vehicle timing information from DCS. If the request in step 402 is found to be invalid, step 408 is executed. In step 408 the source of the request is identified, if it is due to expiry of clock no query to DCS is made and the process ends, if the request is initiated by a user no query to DCS is made, an error message is sent to the user and the process ends. Step 403 accepts valid queries from step 402 in proper format and uses the available query interface of step 404 to query the DCS for passenger information, seat information and vehicle timing information. Step 405 performs receipt and parsing of response received from DCS for the query. Step 406 validates the DCS response for any errors. If no errors are detected step 407 is executed where the PUDS server data repository is updated from the response


received from DCS. If any errors are detected in step 406, step 409 is performed where an error report is created and the process is terminated FIG. 5 is the flow diagram 500 illustrating the process of downloading information from PIDDS server to PIDDS client. The process starts at step 501 with a request from user or on expiry of a preset clock from PIDDS client to download passenger information, seat information and vehicle timing information from PIDDS server for a flight. Step 502 validates if data is available in PIDDS server for downloading for the requested flight. If data is available step 503 retrieves the data from PIDDS server and sends to PIDDS client. If no data is available in step 502 control is transferred by step 506 to step 402 in FIG 4. Step 507 checks for any errors returned by steps 408 or step 409 in FIG 4. If no errors step 507 passes control to step 503. If error is reported step 508 reports the error and the process is terminated. Step 504 parses and validates the PIDDS server response for errors. If errors are found step 509 reports the errors and the process is terminated. If no errors step 505 updates the PIDDS client data repository with response received from PIDDS server.
FIG. 6 is the flow diagram 600 illustrating the process of actuating the PIDDS client to display screens on the User's monitor. The process starts with step 601 with user login with user credentials. User credentials consist of user id password, flight number and date. Step 602 validates user credentials and if credentials found invalid terminates process with error message using step 613. If user credentials are correct step 603 checks if data for flight number and date is available in PIDDS client. If data is not available step 614 transfers control to


step 501 in FIG. 5. Step 615 checks for any errors returned by steps 508 or step 509 in FIG 5. If errors are reported step 616 reports error and terminates process. If no errors are reported step 604 is executed. If data is found available in step 603 control is transferred to step 604. Step 604 displays the application home page having the Summary information. Step 605 accepts user selection for detail information display. Step 606 checks for Meal view display. If correct Step 607 displays Meal view else step 608 is executed. Step 608 checks for Passenger view display. If correct Step 609 displays Passenger view else step 610 is executed. Step 610 checks for SSR view display. If correct Step 612 displays SSR view else step 612 displays Onward connection view.
The Screen Displays
FIG. 7 is a screen display illustrating the Summary Report Screen. The illustration given by 700 can display the flight number, flight date, aircraft type and book load as given in 701. Flight timing information is given in 702. The Summary Report Screen can also be divided into six boxes giving the following information:
• Total count of passengers accepted in each class is given in 703
• Total meal count and count of each meal type is given in 704
• Total seat count and count of each passenger type is given in 705
• Total special requests and count for types of special requests is given in 706
• Onward connection of passengers with same airline's flight or different airline's flight is given in 707


• Flight information provides static information of flight characteristics and
personnel required to handle the flight is given in 708 All screens displayed by the Passenger Dashboard has a Refresh button as given in 709 to download the updated information from the PIDDS server when passenger acceptance is in progress and the final updated information is downloaded on the PIDDS client when the passenger acceptance process is complete. After the final download is completed the PIDDS client has the complete data for the flight. The time-stamp of the last update is given at the bottom of the screen as shown in 710.
FIG. 8 is a screen display illustrating the Meals View Screen. The screen illustrated in 800 displays the seat map of the aircraft bearing seat numbers with demarcation for each class and zones with in each class as shown in 801. The proper seat map as shown in 801 is selected depending on the aircraft configuration for the flight. The type of meals to be served is color coded and reflected on each seat. By using clickable buttons 802 on the seat map the seat map display can be obtained for entire aircraft, class wise, zone wise or row wise. If the meal type is clicked 803 the particular meal type will be only displayed on the seats.
The bottom half of the screen is divided into three parts. The first part 804 bears the counts of the meal types of the portion of the seat map displayed. The second part 805 of the screen will list the seat number, passenger names and meal type based on the type of meal and portion of the seat map selected. Each seat is clickable on the seat map and can also be selected from the list and when


clicked or selected, detailed information of the passenger occupying the seat is displayed in the third part 806.
FIG. 9 is a screen display illustrating the Passenger View Screen. The screen illustrated in 900 displays the seat map of the aircraft bearing seat numbers with demarcation for each class and zones with in each class as shown in 901. The proper seat map as shown in 901 is selected depending on the aircraft configuration for the flight. The type of passenger occupying the seats is color coded and reflected on each seat. By using clickable buttons 902 on the seat map the seat map display can be obtained for entire aircraft, class wise, zone wise or row wise. If the passenger type is clicked 903 the particular passenger type will be only displayed on the seats.
The bottom half of the screen is divided into three parts. The first part 904 bears the counts of the passenger types of the portion of the seat map displayed. The second part 905 of the screen will list the seat number, passenger names and passenger type based on the type of passenger and portion of the seat map selected. Each seat is clickable on the seat map and can also be selected from the list and when clicked or selected, detailed information of the passenger occupying the seat is displayed in the third part 906.


FIG. 10 is a screen display illustrating the SSR View Screen. The screen illustrated in 1000 displays the seat map of the aircraft bearing seat numbers with demarcation for each class and zones with in each class as shown in 1001. The proper seat map as shown in 1001 is selected depending on the aircraft configuration for the flight. The type of Special service requested is color coded and reflected on each seat. By using clickable buttons 1002 on the seat map the seat map display can be obtained for entire aircraft, class wise, zone wise or row wise. If the SSR type is clicked 1003 the particular SSR type will be only displayed on the seats.
The bottom half of the screen is divided into three parts. The first part 1004 bears the counts of the SSR types of the portion of the seat map displayed. The second part 1005 of the screen will list the seat number, passenger names and SSR type based on the type of SSR and portion of the seat map selected. Each seat is clickable on the seat map and can also be selected from the list and when clicked or selected, detailed information of the passenger occupying the seat is displayed in the third part 1006.
FIG. 11 is a screen display illustrating the Onward Connection View Screen. The screen illustrated in 1100 displays the seat map of the aircraft bearing seat numbers with demarcation for each class and zones with in each class as shown in 1101. The proper seat map as shown in 1101 is selected depending on the aircraft configuration for the flight. The type of onward connection of the passenger is color coded and reflected on each seat. By using clickable buttons 1102 on the seat map the seat map display can be obtained for entire aircraft,


class wise, zone wise or row wise. If the onward connection type is clicked 1103 the particular onward connection type will be only displayed on the seats. The bottom half of the screen is divided into three parts. The first part 1104 bears the counts of the onward connection types of the portion of the seat map displayed. The second part 1105 of the screen will list the seat number, passenger names and onward connection type based on the type of onward connection and portion of the seat map selected. Each seat is clickable on the seat map and can also be selected from the list and when clicked or selected, detailed information of the passenger occupying the seat is displayed in the third part 1106.
The present invention has been described in relation to particular embodiments which are intended in all respects to be illustrative rather than restrictive. Alternative embodiments will become apparent to those skilled in the art to which the present invention pertains without departing from its spirit and scope. Accordingly, the scope of the present invention is defined by the appended claims rather than the foregoing description.





ABSTRACT
Providing crew and other interested parties with dynamic and real-time passenger, travel and vehicle information onboard the vehicle. This dynamic and real-time information is shown in various screens on a display monitor or other humanly perceivable system that could be a part of a Computer, Mobile phones, Personal Digital Assistants (PDA) or any other similar devices that have the capability to display a seat layout in graphical or character form, and includes travel information, passenger information and vehicle information. The information is presented to crew or other interested parties onboard the vehicle in a manner which enhances passenger service and allows crew and other interested parties to better service the passengers onboard the vehicle. Any or all of the information related to Passenger Profile, Passenger Requests, Passenger Meal Preference, Passenger Value, Passenger Travel Information, Infant information and Other Passenger information, the ability to retrieve seat occupancy information for individual seats, row-wise, class-wise, zone-wise is presented in a seat layout in graphical or character form on the device display monitor or other humanly perceivable system. The information is fetched from multiple information sources on real-time, or periodically updated or on update request made by the crew or other interested parties.