Patent Description:
The present disclosure relates generally to a customizable service space within a modular environment in a vehicle.

Historically, galley areas on airplanes are configured at purchase to meet specific customer requirements for an airline carrier. The configuration requirements at time of purchase are typically directed toward current market conditions at the time of purchase. Galley suppliers have standard designs and the customers may modify them to a limited extent during the initial configuration at the time of purchase. As the markets change, airlines modify the services and products that they offer during in-flight service. Airlines may seek to modify or decrease the in-flight service equipment on an airplane in order to reduce weight or cost, or change the food or beverage service offerings to increase revenues and lower costs. Modifications of the initial configuration implemented after the time of initial purchase are costly, time consuming, and in some cases because of mod-shop quality control may compromise the integrity of the galley area components due to work-arounds for modifications that were not planned for initially. Airplanes undergoing modifications, usually in concert with other modifications, may be out of service for extended periods of time in order to complete the modifications. This time out of service adds lost revenue to the already high costs of reconfiguring the at purchase design.

Therefore, it would be advantageous to have a method and apparatus that takes into account one or more of the issues discussed above, as well as possibly other issues.

<CIT> describes, in accordance with its abstract, an aircraft cabin module of an elongated rectangular shape and that includes two large walls connected by two small walls, a service module arranged along a wall separating the module from an aisle, a door mounted in an opening implemented in a small wall, and at least one seat having at least one configuration in which it is positioned longitudinally in relation to the direction of movement of the airplane. Each module includes elements configured to form a bedding surface for at least one passenger.

<CIT> describes, in accordance with its abstract, methods and systems for an automated safety device inspection system for a vehicle are provided. The system includes an RFID reader including a transmit portion and a receive portion wherein the reader is physically translatable along a predetermined path, a directional antenna communicatively coupled to the reader wherein the antenna is configured to transmit and receive radio frequency (RF) signals in a direction substantially normal to the path, a relative position indicator configured to determine a relative position of the reader from a starting point, and a controller communicatively coupled to the reader. The controller includes a user interface, a processor communicatively coupled to the user interface, and a database communicatively coupled to the processor wherein the database includes location data of a plurality of safety devices in a plurality of different types of vehicles, the processor is configured to control the transmitted RF signals based on the location data.

<CIT> describes, in accordance with its abstract, an interior cabin configuration determination system includes multiple objects, including two or more monuments or passenger service units, that are within an interior cabin. The objects include card readers. Object controllers are coupled to the card readers and determine the position of the objects in response to the position information on the cards. A remotely located controller determines the configuration of the objects in response to the position information.

<CIT> describes, in accordance with its abstract, A modular integrated galley used for food preparation and storage in a passenger vehicle includes a mounting rack defining a plurality of openings or spaces and having a plurality of structural mounting points disposed within the spaces for receiving a plurality of individual galley modules. Each of the galley modules including a generally box-like outer shell having top, bottom, front, rear, and side walls. At least two of the galley modules having a different functional component contained within the outer shell that is selected from the group consisting of a beverage maker, a water dispensing unit, an oven, a refrigerator and a storage compartment. The modular integrated galley further including means for interconnecting adjacent galley modules including an elongate connecting rail defining an outer perimeter having at least two slots formed along the outer perimeter for receiving complimentary ribs on adjacent galley modules.

<CIT> describes, in accordance with its abstract, a galley assembly includes a plurality of modules including adjacent panels mounted to a floor by a plurality of floor fittings and interconnected by a monolithic connector block. The panels are formed by a core disposed between a pair of spaced-apart skins. One of the modules includes a horizontal worktop formed by a substantially rigid bottom panel, a top skin and a perimeter frame disposed between the bottom panel and the top skin. Each floor fitting includes a floor fitting block attached to a bottom edge of the panel and a floor mount attached to the floor fitting block that carries a stud for engaging a floor track in the floor. The connector block includes a main body having a joint face and a peripheral flange, a work opening formed in the main body and a fastener hole formed through the joint face and in communication with the work opening.

<CIT> describes, in accordance with its abstract, a modular galley for an aircraft or train. The modular galley comprises a wall provided with a multiplicity of guides running in the vertical direction with undercuts as well as a multiplicity of essentially block-shaped modules with runners on the rear that can be accommodated in the undercut slots, the cross-sectional shape of which, viewed in the horizontal plane, corresponds to the cross-sectional shape of the undercut slots, viewed in the horizontal plane. The modular galley furthermore comprises lifting means for raising or lowering a said module, the runners of which have been accommodated in a said undercut slot, over the wall. It is preferable if the slots are widened in places such that a runner can be inserted here in the horizontal direction so as then to hook into the undercut slot after being moved vertically.

<CIT> describes, in accordance with its abstract, an aircraft cargo locating system that determines the location and weight of aircraft cargo placed in unit loading devices. A wireless tag, such as an Radio Frequency Identification (RFID) tag is affixed to each of the loading devices. The system receives information from the tags, and from this information calculates the location of the loading devices and the weight of the loading devices.

According to the invention to which this European patent relates, a vehicle as recited in claim <NUM> is provided.

Further details can be seen with reference to the following description and drawings.

The novel features believed characteristic of the advantageous embodiments are set forth in the appended claims. The advantageous embodiments, however, as well as a preferred mode of use, further objectives and advantages thereof, will best be understood by reference to the following detailed description of an advantageous embodiment of the present disclosure when read in conjunction with the accompanying drawings, wherein:.

Referring more particularly to the drawings, embodiments of the disclosure may be described in the context of the aircraft manufacturing and service method <NUM> as shown in <FIG> and aircraft <NUM> as shown in <FIG>. Turning first to <FIG>, an illustration of an aircraft manufacturing and service method is depicted in accordance with an advantageous embodiment. During pre-production, aircraft manufacturing and service method <NUM> may include specification and design <NUM> of aircraft <NUM> in <FIG> and material procurement <NUM>. Initial configuration of a customizable service space may take place during specification and design <NUM> of aircraft <NUM>, for example. A customizable service space may be an area in a vehicle that is configured to be modified or changed.

During production, component and subassembly manufacturing <NUM> and system integration <NUM> of aircraft <NUM> in <FIG> takes place. Thereafter, aircraft <NUM> in <FIG> may go through certification and delivery <NUM> in order to be placed in service <NUM>. While in service by a customer, aircraft <NUM> in <FIG> may be scheduled for routine maintenance and service <NUM>, which may include modification, reconfiguration, refurbishment, and other maintenance or service.

For the purposes of this description, a system integrator may include, without limitation, any number of aircraft manufacturers and major-system subcontractors; a third party may include, without limitation, any number of venders, subcontractors, and suppliers; and an operator may be an airline, leasing company, military entity, service organization, and so on.

With reference now to <FIG>, an illustration of an aircraft is depicted in which an advantageous embodiment may be implemented. In this example, aircraft <NUM> may be produced by aircraft manufacturing and service method <NUM> in <FIG> and may include airframe <NUM> with a plurality of systems <NUM> and interior <NUM>. Examples of systems <NUM> include one or more of propulsion system <NUM>, electrical system <NUM>, hydraulic system <NUM>, environmental system <NUM>, and service space control system <NUM>. Any number of other systems may be included. Although an aerospace example is shown, different advantageous embodiments may be applied to other industries, such as the automotive industry.

Apparatus and methods embodied herein may be employed during any one or more of the stages of aircraft manufacturing and service method <NUM> in <FIG>. For example, components or subassemblies produced in component and subassembly manufacturing <NUM> in <FIG> may be inspected while aircraft <NUM> is in maintenance and service <NUM> in <FIG>.

Also, one or more apparatus embodiments, method embodiments, or a combination thereof may be utilized during service stages, such as maintenance and service <NUM> and in service <NUM> in <FIG>, for example, without limitation, by substantially expediting the inspection and/or maintenance of aircraft <NUM>. As another example, some advantageous embodiments may be used during in service <NUM>. These advantageous embodiments may be used, for example, between flights without requiring maintenance and service <NUM> normally used to reconfigure or modify the interior service areas of an airplane.

The different advantageous embodiments take into account and recognize that currently used galley area configurations for airplanes are configured at purchase to accommodate current market conditions. Standard designs are used and may be modified slightly at initial configuration to meet specific airline customer requirements. However, the different advantageous embodiments recognize that as the market changes, airlines wish to modify the service and products they offer during in-flight service in order to reduce cost, increase revenue, or both. Modification from the initial at purchase configuration is both costly and time-consuming, and is often poorly executed because the modification desired was not originally anticipated by the initial configuration of the galley area.

The different advantageous embodiments take into account and recognize that current customers of transportation vehicles need a way to efficiently and economically customize the on-board service and product offerings to meet changing conditions. In some cases, current customers purchase standard galley equipment in order to make their airplane attractive for resale at a later date. The galley area configuration in this case is not designed for the current airline customer's in-flight service needs but rather strictly for resale considerations so that costly reconfigurations will not be necessary by the new purchaser at the time of resale.

The different advantageous embodiments also take into account and recognize that airline carriers currently offer in-flight services and products, such as food and beverage service for example. In order to supply drinking water to passengers, an airplane must be stocked with bottled drinking water. Bottled drinking water adds cost to the operations, weight considerations, and a large amount of excess trash. In addition, flight attendants may not have a dedicated hand washing station, and may rely on airplane lavatories, which must be shared with passengers.

Furthermore, the different advantageous embodiments also take into account and recognize that there is a lack of trash storage space on current airplanes. In part due to the bottled drinking water, and also due to the other beverages and food served and brought onto the plane by passengers, there is an increase in trash during in-flight service. Plastic bottles in particular may take up excessive space and airplane galleys have limited storage space in current configurations. Multiple small trash bags are often filled and hung on the front of galley units, stored in lavatories, or stashed elsewhere throughout the airplane, such as underneath a seat.

Thus, one or more of the different advantageous embodiments may provide an apparatus for customizing a service space comprising the service space and a number of modules. The service space is capable of being configured. The number of modules is capable of being removeably attached in a number of locations in the service space.

The different advantageous embodiments further provide a method for customizing a service space using a service space control system. User input is detected through a user interface. An identification screen is presented using the user interface. Identification information is received. A determination is made as to whether a user is authorized to use the service space control system using the identification information.

The different advantageous embodiments may provide a wireless communications system that may be capable of providing communications with the customizable service space and/or modules within the modular environment. The computer system may be capable of generating commands and processes for the customizable service space and/or number of modules in the modular environment and communicating the commands and processes to the customizable service space and/or number of modules to configure the customizable service space.

As a specific illustrative example, one or more of the different advantageous embodiments may be implemented, for example, without limitation, during at least one of component and subassembly manufacturing <NUM>, system integration <NUM>, certification and delivery <NUM>, in service <NUM>, and maintenance and service <NUM> in <FIG> to assemble a structure for aircraft <NUM>. As used herein, the phrase "at least one of", when used with a list of items, means that different combinations of one or more of the items may be used and only one of each item in the list may be needed. For example, "at least one of item A, item B, and item C" may include, for example, without limitation, item A or item A and item B.

With reference now to <FIG>, an illustration of a data processing system is depicted in accordance with an illustrative embodiment. Data processing system <NUM> may be used to implemented different computers and data processing systems within a modular environment, such as modular environment <NUM> in <FIG>.

In this illustrative example, data processing system <NUM> includes communications fabric <NUM>, which provides communications between processor unit <NUM>, memory <NUM>, persistent storage <NUM>, communications unit <NUM>, input/output (I/O) unit <NUM>, and display <NUM>. Depending on the particular implementation, different architectures and/or configurations of data processing system <NUM> may be used.

Processor unit <NUM> serves to execute instructions for software that may be loaded into memory <NUM>. Processor unit <NUM> may be a set of one or more processors or may be a multi-processor core, depending on the particular implementation. Further, processor unit <NUM> may be implemented using one or more heterogeneous processor systems in which a main processor is present with secondary processors on a single chip. As another illustrative example, processor unit <NUM> may be a symmetric multi-processor system containing multiple processors of the same type.

Memory <NUM> and persistent storage <NUM> are examples of storage devices <NUM>. A storage device may be any piece of hardware that may be capable of storing information, such as, for example without limitation, data, program code in functional form, and/or other suitable information either on a temporary basis and/or a permanent basis. Memory <NUM>, in these examples, may be, for example, a random access memory or any other suitable volatile or non-volatile storage device. Persistent storage <NUM> may take various forms depending on the particular implementation. For example, persistent storage <NUM> may contain one or more components or devices. For example, persistent storage <NUM> may be a hard drive, a flash memory, a rewritable optical disk, a rewritable magnetic tape, or some combination of the above. The media used by persistent storage <NUM> also may be removable.

Communications unit <NUM>, in these examples, provides for communications with other data processing systems or devices. In these examples, communications unit <NUM> may be a network interface card. Communications unit <NUM> may provide communications through the use of either or both physical and wireless communications links.

Input/output unit <NUM> allows for input and output of data with other devices that may be connected to data processing system <NUM>. For example, input/output unit <NUM> may provide a connection for user input through a keyboard, a mouse, and/or some other suitable input device. Further, input/output unit <NUM> may send output to a printer. Display <NUM> provides a mechanism to display information to a user.

Instructions for the operating system, applications and/or programs may be located in storage devices <NUM>, which are in communication with processor unit <NUM> through communications fabric <NUM>. In these illustrative examples the instruction are in a functional form on persistent storage <NUM>. These instructions may be loaded into memory <NUM> for execution by processor unit <NUM>. The processes of the different embodiments may be performed by processor unit <NUM> using computer implemented instructions, which may be located in a memory, such as memory <NUM>.

These instructions are referred to as program code, computer usable program code, or computer readable program code that may be read and executed by a processor in processor unit <NUM>. The program code in the different embodiments may be embodied on different physical or tangible computer readable media, such as memory <NUM> or persistent storage <NUM>.

Program code <NUM> may be located in a functional form on computer readable media <NUM> that may be selectively removable and may be loaded onto or transferred to data processing system <NUM> for execution by processor unit <NUM>. Program code <NUM> and computer readable media <NUM> form computer program product <NUM> in these examples. In one example, computer readable media <NUM> may be in a tangible form, such as, for example, an optical or magnetic disc that may be inserted or placed into a drive or other device that may be part of persistent storage <NUM> for transfer onto a storage device, such as a hard drive that may be part of persistent storage <NUM>. In a tangible form, computer readable media <NUM> also may take the form of a persistent storage, such as a hard drive, a thumb drive, or a flash memory that may be connected to data processing system <NUM>. The tangible form of computer readable media <NUM> may also be referred to as computer recordable storage media. In some instances, computer readable media <NUM> may not be removable.

Alternatively, program code <NUM> may be transferred to data processing system <NUM> from computer readable media <NUM> through a communications link to communications unit <NUM> and/or through a connection to input/output unit <NUM>. The communications link and/or the connection may be physical or wireless in the illustrative examples. The computer readable media also may take the form of non-tangible media, such as communications links or wireless transmissions containing the program code.

In some illustrative embodiments, program code <NUM> may be downloaded over a network to persistent storage <NUM> from another device or data processing system for use within data processing system <NUM>. For instance, program code stored in a computer readable storage medium in a server data processing system may be downloaded over a network from the server to data processing system <NUM>. The data processing system providing program code <NUM> may be a server computer, a client computer, or some other device capable of storing and transmitting program code <NUM>.

The different components illustrated for data processing system <NUM> are not meant to provide architectural limitations to the manner in which different embodiments may be implemented. The different illustrative embodiments may be implemented in a data processing system including components in addition to or in place of those illustrated for data processing system <NUM>. Other components shown in <FIG> can be varied from the illustrative examples shown. The different embodiments may be implemented using any hardware device or system capable of executing program code. As one example, the data processing system may include organic components integrated with inorganic components and/or may be comprised entirely of organic components excluding a human being. For example, a storage device may be comprised of an organic semiconductor.

As another example, a storage device in data processing system <NUM> may be any hardware apparatus that may store data. Memory <NUM>, persistent storage <NUM> and computer readable media <NUM> are examples of storage devices in a tangible form.

In another example, a bus system may be used to implement communications fabric <NUM> and may be comprised of one or more buses, such as a system bus or an input/output bus. Of course, the bus system may be implemented using any suitable type of architecture that provides for a transfer of data between different components or devices attached to the bus system. Additionally, a communications unit may include one or more devices used to transmit and receive data, such as a modem or a network adapter. Further, a memory may be, for example, memory <NUM> or a cache such as found in an interface and memory controller hub that may be present in communications fabric <NUM>.

With reference now to <FIG>, an illustration of a modular environment is depicted in accordance with an illustrative embodiment. In one illustrative example, modular environment <NUM> may be implemented in an aerospace environment. Although an aerospace example is shown, different advantageous embodiments may be applied to other industries, such as the automotive industry for example.

Modular environment <NUM> contains vehicle <NUM>. Vehicle <NUM> may be any type of vehicle such as, without limitation, an aircraft, train, ship, bus, spacecraft, submarine, and/or any other suitable transportation vehicle. Vehicle <NUM> contains service space <NUM> and service space control system <NUM>. Service space <NUM> is an area in vehicle <NUM> that is capable of being configured and/or reconfigured for different uses. In these examples, service space <NUM> may be referred to as customizable service space <NUM>. Modular environment <NUM> may also include number of modules <NUM>.

Customizable service space <NUM> may include arch framework <NUM>, utilities <NUM>, power supply source <NUM>, communications unit <NUM>, mounting system <NUM>, track system <NUM>, number of modules <NUM>, electronic latching system <NUM>, radio frequency identification system <NUM>, and access system <NUM>. Arch framework <NUM> may be a fixed basic unit that includes distinct spaces for modular components. Arch framework <NUM> is sized to fit within customizable service space <NUM> of vehicle <NUM>. In an illustrative example of an aircraft, customizable service space <NUM> may be an aircraft fuselage and arch framework <NUM> may be sized to the aircraft fuselage and adaptable to any number of different aircraft fuselage cross sections. For example, arch framework <NUM> may be implemented in the aft section of an aircraft fuselage, a mid-cabin section of an aircraft fuselage, and/or any other suitable location within an aircraft fuselage.

Utilities <NUM> may provide electricity, water, sewage disposal, and/or any other suitable utility. Utilities <NUM> may include, without limitation, electrical components and plumbing components. Utilities <NUM> may be pre-populated within customizable service space <NUM> to provide utility services to any number of different modules in any number of different configurations within customizable service space <NUM>. For example, utilities <NUM> may be distributed throughout customizable service space <NUM> in order to provide utility access to number of modules <NUM> at any location within customizable service space <NUM>. As used herein, a number refers to one or more modules and/or one or more configurations.

Power supply source <NUM> may be a master power supply that may provide power to a number of modules inserted into a modular space of a customizable service space, such as number of modules <NUM>. In an illustrative example, power supply source <NUM> may be routed from the back wall of customizable service space <NUM> to an Aeronautical Radio, Incorporated (ARINC) standard electrical connector. The opposite fitting for the electrical connector may be located on the back surface of a module. When a module is installed the connectors lock and power is then transferred to the systems in the module. Power supply source <NUM> may include, without limitation, a battery, a mobile battery recharger, a networked autonomous battery recharger, energy harvesting devices, photo cells, and/or other suitable power sources.

Communications unit <NUM>, in these examples, provides for communications with other data processing systems or devices. Communications unit <NUM> may be an example of one implementation of communications unit <NUM> in <FIG>, for example. Communications unit <NUM> may include, for example, without limitation, transmitters, receivers, transceivers, and/or other suitable types of communication devices.

Mounting system <NUM> includes track system <NUM>. Track system <NUM> may include a number of tracks disposed along the floor surface of customizable service space <NUM> for accepting number of modules <NUM>. For example, track <NUM> may be a track in track system <NUM>. Track <NUM> may have number of fittings <NUM>. Number of fittings <NUM> may be any type of fitting, including, without limitation, a latching fitting, pin, fastener, slider, and/or any other suitable fitting. Number of modules <NUM> may include module <NUM>. Module <NUM> may have number of rails <NUM> disposed along the bottom surface of module <NUM>. Number of rails <NUM> may be, without limitation, slotted rails. Number of rails <NUM> may engage track system <NUM>. In an illustrative example, module <NUM> may be inserted into customizable service space <NUM> using number of rails <NUM> and track system <NUM> to align module <NUM> into a distinct modular space of customizable service space <NUM>. In this example, number of fittings <NUM> of track <NUM> may engage number of rails <NUM> of module <NUM> in order to assist with the insertion of module <NUM> into customizable service space <NUM>.

In an illustrative example, number of fittings <NUM> may be teeth fittings that engage with a slotted rail, for example. In this illustrative example, the teeth fittings may be dispersed along the front and rear of a track on the floor of a customizable service space. This illustrative assembly has a connecting rod between the forward and aft fitting and a pull pin and latch that are connected to the forward fitting. Once the pin is pulled and the latch is unlatched the fitting assembly can be pulled forward, thus sliding the teeth fittings forward without tools and disconnecting the module from the H-section attachment rail.

Number of modules <NUM> may be any type of modular component suitable for customizable service space <NUM>. For example, number of modules <NUM> may include, without limitation, a lavatory, a self-service vending machine, a seating area, a retail space, a bar unit, a storage unit, a countertop unit, a business center, a desk unit, conventional galley units with industry standard inserts, and/or any other suitable module. Conventional galley units with industry standard inserts may include, without limitation, ovens, coffee makers, hot cups, galley carts, food storage units, beverage storage units, and/or any other suitable unit.

Number of modules <NUM> include number of radio frequency identification tags <NUM>. Radio frequency identification system <NUM> includes number of radio frequency identification readers <NUM>. Number of radio frequency identification tags <NUM> may provide information about the module, such as, without limitation, identification of module, type of module, content of module, status of module, health of module, and/or any other suitable information. Each module in number of modules <NUM> may have a unique radio frequency identification tag that identifies the module to customizable service space <NUM> using number of radio frequency identification readers <NUM>. For example, module <NUM> may include radio frequency identification tag <NUM>. A module may have a number of radio frequency identification tags located throughout the module. As used herein, a number refers to one or more radio frequency identification tags.

In one illustrative example, module <NUM> may be a galley module that contains meals for in-flight meal service. Each meal package or tray within module <NUM> may have its own radio frequency identification tag in order to track the number of meals in the galley module at any given time. When the meals are inserted into module <NUM> and module <NUM> is placed in customizable service space <NUM>, radio frequency identification reader <NUM> may scan module <NUM> and record all of the radio frequency identification tags in module <NUM>, including radio frequency identification tag <NUM>. The data collected from the scan may then be compared to a database that contains food information, for example, to determine whether the correct number of meals have been supplied by the food provider. In another example, the data may be used to monitor the number of meals remaining, or the number of a certain type of meal remaining. A type of meal may be, without limitation, a vegetarian meal, a beef meal, a chicken meal, a breakfast meal, a lunch meal, a dinner meal, and/or any other suitable type of meal. As the meals are depleted during meal service, radio frequency identification reader <NUM> in customizable service space <NUM> may provide real time information to service space control system <NUM> as to the amount and type of food remaining. This data may be accessed over user interface <NUM> and displayed on display device <NUM>. Radio frequency identification reader <NUM> is an example of a reader in number of radio frequency identification readers <NUM> that detects radio frequency identification tag <NUM> when module <NUM> is inserted into customizable service space <NUM>. Radio frequency identification reader <NUM> transmits the identification information detected from radio frequency identification tag <NUM> to service space control system <NUM> using communications unit <NUM>. The identification information is be stored in service space database <NUM> and may be processed by service space control process <NUM>.

Radio frequency identification system <NUM> may be located within customizable service space <NUM> in a location that provides number of radio frequency identification readers <NUM> access to number of radio frequency identification tags <NUM> on number of modules <NUM> when a module is inserted into customizable service space <NUM>. The location may be, for example, on the back wall of customizable service space <NUM>, or on the floor surface of customizable service space <NUM>. In an illustrative example, when module <NUM> is installed into customizable service space <NUM>, radio frequency identification reader <NUM> may read radio frequency identification tag <NUM>. Radio frequency identification reader <NUM> may then use service space database <NUM> to identify module <NUM> and record information about module <NUM>. Information recorded may include, for example, they type and/or quantity of contents within module <NUM>.

The service space control system <NUM> uses information detected by number of radio frequency identification readers <NUM> to identify the types of modules inserted into customizable service space <NUM> as well as other information about the modules. For example, service space control system <NUM> will know the difference between a galley module and a lavatory module and update the system with the information about the current modules in customizable service space <NUM>. The information is stored in service space database <NUM> and may be used for maintenance and certification purposes.

Radio frequency identification system <NUM> is used as an electronic means of recording configuration control instead of manually recording data. The description of radio frequency identification system <NUM> is provided for illustrative purposes and does not limit the methods by which information may be recorded in this invention. In an example that does not fall within the scope of the claims, any other suitable method for recording information may be used, such as, without limitation, bar codes to record information about the modules.

Electronic latching system <NUM> may be capable of electronically securing number of modules <NUM> after insertion into customizable service space <NUM>. Electronic latching system <NUM> may also be capable of electronically releasing number of modules <NUM> for removal from customizable service space <NUM>. In an illustrative example, electronic latching system <NUM> may use a radial fastener with the electronic component installed on the back wall of customizable service space <NUM> and the fitting installed on the back of the modules, such as number of modules <NUM>. When a module, such as module <NUM>, is slid into place, electronic latching system <NUM> locks and sends a signal to service space control system <NUM> indicating module <NUM> is locked into place. In order to unlock a module, a user may select a maintenance mode from a function selection of service space control process <NUM> over user interface <NUM>. In the maintenance mode, a user may select the module to unlock, and service space control system <NUM> may send a signal to electronic latching system <NUM> to release the module.

Access system <NUM> may be capable of allowing and/or restricting access to number of modules <NUM> based on the individual attempting access to one or more of number of modules <NUM>. For example, module <NUM> of number of modules <NUM> may be a restricted access module that allows access to authorized personnel only.

Service space control system <NUM> may provide for communication with and control of the different components of customizable service space <NUM>. Service space control system <NUM> may be an example of one implementation of data processing system <NUM> in <FIG>. Service space control system <NUM> may be an example of one implementation of service space control system <NUM> on aircraft <NUM> in <FIG>, for example. Service space control system <NUM> may include communications unit <NUM>, display device <NUM>, user interface <NUM>, service space control process <NUM>, and service space database <NUM>.

Communications unit <NUM> may be similar to communications unit <NUM>. Communications unit <NUM> may be an example of one implementation of communications unit <NUM> in <FIG>, for example. Communications unit <NUM>, in these examples, provides for communications with the different components of customizable service space <NUM>. Communications unit <NUM> may include, for example, without limitation, transmitters, receivers, transceivers, and/or other suitable types of communication devices.

Display device <NUM> may be an example of one implementation of display <NUM> in <FIG>. Display <NUM> may include user interface <NUM>. User interface <NUM> may enable interaction with service space control process <NUM> by a user, such as user <NUM>. User <NUM> may be, without limitation, a human operator, an external system, and/or any other suitable user of service space control process <NUM>. A human operator may include a number of personnel, such as, for example, without limitation, flight attendants, maintenance workers, service staff, and/or any other suitable personnel for vehicle <NUM>.

Service space control process <NUM> may interact with user interface <NUM> to receive input from a user and present information to the user. Service space control process <NUM> may analyze input from a user, generate a number of commands based on the input, and send the number of commands to one or more components of customizable service space <NUM>. For example, if a flight attendant attempts to access a specific module, such as module <NUM> in number of modules <NUM>, service space control process <NUM> may first analyze the input from the flight attendant, such as verification information, and determine whether the flight attendant is authorized to access module <NUM>. Service space control process <NUM> may determine that the flight attendant is an authorized person, and send a command to access system <NUM> to allow access to module <NUM>. In an illustrative example, access system <NUM> may allow access by releasing a lock mechanism of a door for module <NUM>, for example. In another illustrative example, a maintenance worker may input data into user interface <NUM> requesting release of module <NUM> for removal from customizable service space <NUM>. Service space control process <NUM> may first analyze the input to determine if the maintenance worker is an authorized person. Upon determining that the maintenance worker is an authorized person, service space control process <NUM> may then send a command to electronic latching system <NUM> to release module <NUM> from customizable service space <NUM>.

Service space database <NUM> may include information such as, without limitation authorized personnel identification information and access authorization, specification information for a number of different service spaces, specification information for a number of different modules, and/or any other suitable information.

In an illustrative example, customizable service space <NUM> may be initially configured with number of modules <NUM>. A new configuration request may be generated or received by service space control process <NUM>. The new configuration request may be, for example, a new customized service space configuration. In an illustrative example, new configuration requests may be generated by a user using service space control system <NUM>, for example, or may be generated by an external system and transmitted to service space control system <NUM>. Service space control process <NUM> may identify which of the existing modules in number of modules <NUM> meet the new requirements of the new configuration request, if any. For example, module <NUM> may be a storage unit currently inserted into a distinct space where the new configuration request has also required the same storage unit. In this illustrative example, service space control process <NUM> may identify module <NUM> as a module that may remain in the new configuration, and send a command to electronic latching system <NUM> to retain module <NUM> in the secure position, while releasing the other modules of number of modules <NUM>. Number of modules <NUM> may then be inserted in place of number of modules <NUM> that are removed, for example, in order to fulfill the new configuration request.

The illustration of modular environment <NUM> in <FIG> is not meant to imply physical or architectural limitations to the manner in which different advantageous embodiments may be implemented. Other components in addition and/or in place of the ones illustrated may be used. Some components may be unnecessary in some advantageous embodiments. Also, the blocks are presented to illustrate some functional components. One or more of these blocks may be combined and/or divided into different blocks when implemented in different advantageous embodiments.

For example, in some advantageous embodiments, the components of service space control system <NUM> may be distributed throughout modular environment <NUM> or across locations remote from modular environment <NUM>. Service space database <NUM> may be located in a remote location from service space control system <NUM> or may be integrated with service space control system <NUM>. Further, a particular module within number of modules <NUM> or number of modules <NUM> may be used for more than one purpose.

With reference now to <FIG>, an illustration of a service space control process is depicted in accordance with an illustrative embodiment. Service space control process <NUM> may be an example of one implementation of service space control process <NUM> in <FIG>. Service space control process <NUM> may include electronic latching process <NUM>, personnel authentication process <NUM>, access control process <NUM>, and modular configuration process <NUM>. Service space control process <NUM> may receive input <NUM> from a user interface, such as user interface <NUM> in <FIG>. Service space control process <NUM> may generate number of commands <NUM> in response to input <NUM> using electronic latching process <NUM>, personnel authentication process <NUM>, access control process <NUM>, and modular configuration process <NUM>.

Electronic latching process <NUM> may control an electronic latching system, such as electronic latching system <NUM> in <FIG>. Electronic latching process <NUM> may send commands to an electronic latching system to electronically secure a number of modules after insertion into a customizable service space. Electronic latching process <NUM> may send commands to an electronic latching system to electronically release a number of modules after insertion into a customizable service space. Personnel authentication process <NUM> may control access to the components of a customizable service space and/or the data processing system controlling the customizable service space, such as service space control system <NUM> in <FIG>, for example.

Access control process <NUM> may control an access system, such as access system <NUM> in <FIG>. Access control process <NUM> may analyze user input, such as, for example, user identification information, in order to determine whether a particular user is allowed access to a specific module.

Modular configuration process <NUM> may provide a number of different configuration options for a customizable service space. For example, modular configuration process <NUM> may present the number of different configuration options to a user over a user interface for selection by the user of a preferred configuration option.

Input <NUM> may be received from a user interface, such as user interface <NUM> in <FIG>. Input <NUM> may be processed by data analysis process <NUM> to generate number of commands <NUM>. Data <NUM> may be received from a customizable service space, such as customizable service space <NUM> in <FIG>. In one illustrative example, data <NUM> may be radio frequency identification tag information detected by radio frequency identification reader <NUM> in <FIG>, for example. In this illustrative example, data <NUM> may be processed by data analysis process <NUM> using module identification process <NUM> to identify a number of modules inserted into a customizable service space. Data analysis process <NUM> may then generate number of messages <NUM> with the module identification information, for example. The number of messages may be sent to a database, such as service space database <NUM>, for access by a user over user interface <NUM> in <FIG>, for example. In another example, the number of messages may be sent as alerts to a user interface, such as user interface <NUM> in <FIG>, for example.

The illustration of service space control process <NUM> in <FIG> is not meant to imply physical or architectural limitations to the manner in which different advantageous embodiments may be implemented. Other components in addition and/or in place of the ones illustrated may be used. Some components may be unnecessary in some advantageous embodiments. Also, the blocks are presented to illustrate some functional components. One or more of these blocks may be combined and/or divided into different blocks when implemented in different advantageous embodiments.

With reference now to <FIG>, an illustration of a service space database is depicted in accordance with an illustrative embodiment. Service space database <NUM> may be an example of one illustrative embodiment of service space database <NUM> in <FIG>.

Service space database <NUM> may include number of personnel identification information <NUM>, number of personnel access information <NUM>, number of service spaces specification information <NUM>, number of modules specification information <NUM>, number of modules identification information <NUM>, current module information <NUM>, and/or any other suitable information. Number of personnel identification information <NUM> may contain information about the personnel authorized to interact with a service space control system and/or a customizable service space. Information about authorized personnel may include identification information, such as, without limitation, biometric information, facial recognition information, voice recognition information, password and/or pass code associated with a specific individual, name, identifying characteristics, employee data, and/or any other information used to identify an authorized person attempting to access a service space control system. Information contained in number of personnel identification information <NUM> may be accessed by a process, such as personnel authentication process <NUM> in <FIG>, in order to identify and authenticate a person attempting to interact with a service space control system, such as service space control system <NUM> in <FIG>, for example.

Number of personnel access information <NUM> may contain information about the specific modules and/or compartments of a customizable service space that an individual person is authorized to access. Information pertaining to specific modules and/or compartments may be associated with identification information from number of personnel identification information <NUM>. Information contained in number of personnel access information <NUM> may be used to restrict access to certain modules to a select group of authorized personnel, for example. In an illustrative example, a module used for storage of emergency equipment may be restricted to allow access only to authorized emergency personnel and prohibit access to other personnel.

Number of service spaces specification information <NUM> may contain information about the technical specification of a number of service spaces. Technical specifications of a service space may include information such as, without limitation, size, width, length, height, weight restrictions, utility configurations, power configurations, and/or any other suitable information about a service space. Number of service spaces specification information <NUM> may be used by a process, such as modular configuration process <NUM> in <FIG>, to generate a number of configuration options for a number of modules in a given service space.

Number of modules specification information <NUM> may contain information about the technical specifications of a number of modules. Technical specifications of a module may include, without limitation, size, width, length, height, weight, materials, content, utility requirements, power requirements, and/or any other suitable information about a module. Number of modules specification information <NUM> may be used by a process, such as modular configuration process <NUM> in <FIG>, to generate a number of configuration options for a number of modules in a given service space.

Number of modules identification information <NUM> may contain information used to identify a type of module and/or a specific module. For example, the information may contain, without limitation, the name of a module, the type of module, the purpose of the module, the contents of the module, and/or any other suitable information for identifying a module. Current module information <NUM> may contain information received about the current status of a number of modules. Information about the current status of a module may include, without limitation, the location of a module, the age of a module, the time the module has been in its current location, the health of the module, the contents of the module, the last time the module was accessed, and/or any other suitable information about the current status of a module. In one illustrative example, the information about the current status of a module may be received from a service space control system, such as service space control system <NUM> in <FIG>, during monitoring of a customizable service space, for example. In another illustrative example, the information about the current status of a module may be received from a radio frequency identification reader, such as radio frequency identification reader <NUM> in <FIG>, for example. Information about the current status of a number of modules may be used by personnel interacting with a service space control system to make decisions about reconfiguring a service space, for example, or alert personnel to potential conflicts in a current configuration, in another example.

The illustration of service space database <NUM> in <FIG> is not meant to imply physical or architectural limitations to the manner in which different advantageous embodiments may be implemented. Other components in addition and/or in place of the ones illustrated may be used. Some components may be unnecessary in some advantageous embodiments. Also, the blocks are presented to illustrate some functional components. One or more of these blocks may be combined and/or divided into different blocks when implemented in different advantageous embodiments.

With reference now to <FIG>, <FIG>, an illustration of a module is depicted in accordance with an illustrative embodiment. Module <NUM> may be an example of one implementation of module <NUM> in <FIG>.

Module <NUM> is depicted within customizable service space <NUM>. Module <NUM> is depicted with area <NUM> and area <NUM> in an exploded view in <FIG> to illustrate the number of rails of module <NUM> interacting with a track system of a customizable service space, such as track system <NUM> in customizable service space <NUM> in <FIG>.

Area <NUM> depicts left module attachment rail <NUM> of module <NUM>. Left module attachment rail <NUM> is disposed along the bottom surface of module <NUM> and interacts with track <NUM>. Track <NUM> is disposed along the floor surface <NUM> of customizable service space <NUM>.

Similarly, area <NUM> depicts right module attachment rail <NUM> of module <NUM>. Right module attachment rail <NUM> is disposed along the bottom surface of module <NUM> and interacts with track <NUM>. Track <NUM> is disposed along the floor surface <NUM> of customizable service space <NUM>. Track <NUM> and track <NUM> may be an example of one implementation of track system <NUM> in <FIG>, for example. Track <NUM> and track <NUM> provide customizable service space <NUM> the capability to be configured with any number of different modules, such as module <NUM>.

Left module attachment rail <NUM> and right module attachment rail <NUM> may be any type of device capable of interacting with tracks <NUM> and <NUM>. In one illustrative example, left module attachment rail <NUM> and right module attachment rail <NUM> may be slotted rails, and tracks <NUM> and <NUM> may include a number of fittings/pins that interact with the rails to grip the rails and assist in secure insertion of module <NUM> into customizable service space <NUM>. Left guide rail <NUM> and right guide rail <NUM> may be any type of rail suitable for aligning module <NUM> with track <NUM> and track <NUM> as module <NUM> is inserted into customizable service space <NUM>. Left guide rail <NUM> and right guide rail <NUM> may be any type of rail suitable for aligning module <NUM> with track <NUM> and track <NUM> as module <NUM> is inserted into customizable service space <NUM>.

The illustration of module <NUM> in <FIG>, <FIG> is not meant to imply physical or architectural limitations to the manner in which different advantageous embodiments may be implemented. Other components in addition and/or in place of the ones illustrated may be used. Some components may be unnecessary in some advantageous embodiments. Also, the blocks are presented to illustrate some functional components. One or more of these blocks may be combined and/or divided into different blocks when implemented in different advantageous embodiments.

With reference now to <FIG>, an illustration of a customizable service space is depicted in accordance with an illustrative embodiment. Customizable service space <NUM> may be an example of one implementation of customizable service space <NUM> in <FIG>.

Customizable service space <NUM> may include arch <NUM>. Arch <NUM> may be an example of one implementation of arch framework <NUM> in <FIG>. Arch <NUM> may be a fixed basic unit that includes distinct spaces for modular components. Arch <NUM> may include module A <NUM>, module B <NUM>, and module C <NUM>. In one illustrative example, module A <NUM> and module B <NUM> may be fixed components of arch <NUM>, while module C <NUM> may be an optional, or configurable, component of arch <NUM>. Module C <NUM> may be configurable in size in order to accommodate the size of the vehicle, for example. In an illustrative example of an aircraft, module C <NUM> may be configured in length between module A <NUM> and module B <NUM> to fit the size of the fuselage for which customizable service space <NUM> has been designed. In another illustrative example, module C <NUM> may be optionally removed in order to accommodate the specific modules inserted into modular space <NUM>. In this example, modules selected for modular space <NUM> may have a height that requires the space optionally occupied by module C <NUM>, for example.

In an advantageous embodiment, module A <NUM> may be a water unit. A water unit may include, for example, a water dispensing component, a filtration system, a faucet, a sink, a container for collecting dispensed water, a drain, a water storage unit, an ice maker, a heating unit, a refrigeration unit, and/or any other suitable water unit component. Module A <NUM> is configured as a vertical stack. In an illustrative example, module A <NUM> may provide water for drinking and/or hygiene from the top portion of the vertical stack. Module A <NUM> may deliver hot and/or cold water to an in-flight station in an aircraft service area for hygiene, such as hand washing by flight attendants for example, from the bottom portion of the vertical stack. Module A <NUM> may provide filtered drinking water and ice from the same station that provides water for hygiene.

This type of module may reduce the weight and cost of providing bottled drinking water on a flight and reduce the bulk of waste from plastic bottles of water consumed in-flight, for example. A filtered water and ice dispensing system would provide more efficient service and ergonomically friendly preparation. In addition, in an illustrative example, a station for flight attendant hygiene may alleviate the need for flight attendants to share airplane lavatories with passengers. This provides ready access for hand washing to flight attendants at any time, enhancing the health and hygiene of the passengers in turn.

In an advantageous embodiment, module B <NUM> may be a waste unit. A waste unit may include, for example, a waste storage unit, an access point for inserting waste, an access point for removing waste, a removable bin, and/or any other suitable waste unit component. In an illustrative example, module B <NUM> may provide storage for trash during transport and operation of a vehicle, such as vehicle <NUM> in <FIG>. Module B <NUM> is configured as a vertical stack.

In an illustrative embodiment, module B <NUM> may provide high-capacity trash storage that can be accessed at airplane turn time from outside the airplane by the maintenance crew by sliding the trash unit forward into the aft door opening, for example. In another advantageous embodiment, module B <NUM> may be a storage unit.

In one advantageous embodiment, module C <NUM> may be overhead storage units. The overhead storage units may include access points, such as doors, for accessing the storage unit and securing the storage unit during transport, for example. Module C <NUM> may be an optional, or configurable, component of arch <NUM> that may be inserted or removed dependent upon the number of different modules inserted into modular space <NUM>.

Modular space <NUM> may be a customizable space within arch <NUM> of customizable service space <NUM>. In an illustrative example, modular space <NUM> may be an initial customizable space, although module C <NUM> may also be customized and/or configured to adapt to the number of modules inserted into modular space <NUM>. Modular space <NUM> may be implemented with a track system, such as track system <NUM> of <FIG> in order to accept a number of modules, such as number of modules <NUM> of <FIG>, into modular space <NUM>.

Door <NUM> represents an aft door of an aircraft cabin. In an illustrative example, module B <NUM> may be a waste unit, and may be capable of moving into alignment with door <NUM> during a service or maintenance process, such as maintenance and service <NUM> in <FIG>, for example. Module B <NUM> may move into alignment with door <NUM> in order to allow for the removal of waste without requiring maintenance or service personnel to enter the aircraft cabin, for example.

The illustration of customizable service space <NUM> in <FIG> is not meant to imply physical or architectural limitations to the manner in which different advantageous embodiments may be implemented. Other components in addition and/or in place of the ones illustrated may be used. Some components may be unnecessary in some advantageous embodiments. Also, the blocks are presented to illustrate some functional components. One or more of these blocks may be combined and/or divided into different blocks when implemented in different advantageous embodiments.

Customizable service space <NUM> may include arch <NUM>. Arch <NUM> may be an example of one implementation of arch framework <NUM> in <FIG>. Arch <NUM> may include module A <NUM>, module B <NUM>, and module C <NUM>.

In an advantageous embodiment, module A <NUM> may be a water unit. Module A <NUM> may include component <NUM> and component <NUM>. Component <NUM> may be, for example, a water storage unit and dispensing component. Component <NUM> may be, for example, a sink, a container for collecting dispensed water, a drain, and/or a water storage unit. In an illustrative example, module A <NUM> may provide water for drinking and/or hygiene.

In an advantageous embodiment, module B <NUM> may be a waste unit. Module B <NUM> may include component <NUM> and component <NUM>. Component <NUM> may be, for example, an access point for inserting waste. Component <NUM> may show an open access point, and may include a door or other suitable covering (not shown) for the open access point, for example. Component <NUM> may be, for example, a movable component of module B <NUM> that provides access to an interior waste storage unit, such as a trash bin for example. In an illustrative example, module B <NUM> may provide storage for trash and component <NUM> may be a hinged door assembly that may open to provide removal of collected or stored trash.

In one advantageous embodiment, module C <NUM> may be overhead storage units. The overhead storage units may include access points, such as doors, for accessing the storage unit and securing the storage unit during transport, for example.

Modular space <NUM> may be a customizable space within arch <NUM> of customizable service space <NUM>. In an illustrative example, modular space <NUM> may include module <NUM>, module <NUM>, module <NUM>, and module <NUM>. Modules <NUM>, <NUM>, and <NUM> may be any type of insertable modules, such as storage units, for example. Module <NUM> may be a space providing a module capable of providing counter space or flat surface space, for example.

Modular space <NUM> may be implemented with a track system, such as track system <NUM> of <FIG> in order to accept module <NUM>, module <NUM>, module <NUM>, and module <NUM> into modular space <NUM>.

Customizable service space <NUM> may include arch <NUM>. Arch <NUM> may be an example of one implementation of arch framework <NUM> in <FIG>. Arch <NUM> may include module A <NUM> and module B <NUM>. Arch <NUM> may provide an illustrative example of a customizable service space configured without module C <NUM> in <FIG>, for example.

In an advantageous embodiment, module A <NUM> may be a water unit. Module A <NUM> may include component <NUM>, which may be a water storage unit or drain system, in an illustrative example. Module A <NUM> may also include sink <NUM> and dispenser <NUM>. Component <NUM> may be provided in module A <NUM> to provide a view into a water storage unit or water dispensing unit of module A <NUM>, for example. Component <NUM> may be used to monitor a remaining water level, for example.

In an advantageous embodiment, module B <NUM> may be a waste unit. Module B <NUM> may illustrate a waste unit, such as module B <NUM> in <FIG>, with a closed access point, such as door <NUM>.

Modular space <NUM> may be a customizable space within arch <NUM> of customizable service space <NUM>. In an illustrative example, modular space <NUM> may include module <NUM> and module <NUM>. Modules <NUM> and <NUM> may be any type of insertable modules. Module <NUM> may be a lavatory module, with door <NUM> for access to the lavatory, for example. Module <NUM> may be a retail space that includes display case <NUM>, for example. A retail space may be used for additional revenue opportunities by a company providing transport. For example, a retail space could be leased out to different companies for a specific period of time. In another example, a retail space could be used by the company providing the transportation vehicle to display promotional items. The retail space may be a self-service retail unit and/or a display unit presenting items for purchase during in-flight service, for example.

Modular space <NUM> may be implemented with a track system, such as track system <NUM> of <FIG> in order to accept module <NUM> and module <NUM> into modular space <NUM>.

For example, modular space <NUM> may be configured with a fixed or mobile bar unit (not shown) to serve specialized drinks. The bar unit may be configured to serve specific drinks depending upon the culture of the primary transportation customer. For example, the bar unit may be configured as a tea service, as a full-service bar with alcoholic beverages, as a coffee bar, and/or any other customized drink service configuration. With reference now to <FIG>, an illustration of a customizable service space is depicted in accordance with an illustrative embodiment. Customizable service space <NUM> is an example of one implementation of customizable service space <NUM> in <FIG>.

Customizable service space <NUM> may include modular space <NUM>. Modular space <NUM> may be configured with module <NUM> and module <NUM>. Modules <NUM> and <NUM> may be, for example, lavatory modules. Modules <NUM> and <NUM> may be inserted between module A <NUM> and module B <NUM>. Module A <NUM> and module B <NUM> may be examples of module A <NUM> and module B <NUM> in <FIG>, for example.

Customizable service space <NUM> may include arch <NUM>. Arch <NUM> may be an example of one implementation of arch framework <NUM> in <FIG>. Arch <NUM> may include module A <NUM>, module B <NUM>, and module C <NUM>. Module A <NUM> is an example of one implementation of module A <NUM> in <FIG>. Module B <NUM> may be an example of one implementation of module B <NUM> in <FIG>. Module C <NUM> may be an example of one implementation of module C <NUM> in <FIG>.

Modular space <NUM> may be a customizable space within arch <NUM> of customizable service space <NUM>. In an illustrative example, modular space <NUM> may include seating <NUM>. Seating <NUM> may be provided as additional seating for a vehicle, such as vehicle <NUM> in <FIG>, for example. In an illustrative example, seating <NUM> may be additional seating for passengers, seating for flight attendants, seating for service crews, seating for transportation crews, specialized seating for persons with disabilities, premier seating, task specific seating, and/or any other suitable type of seating.

In one advantageous embodiment, modular space <NUM> may be configured with a person with disabilities module. A person with disabilities module may include additional securing mechanisms for specialized seating, such as a wheelchair or motorized chair for example. Securing mechanisms may include retractable lock down devices and drawer slides that support and guide either a one-piece seating module and/or a wheelchair mounting device to the module, for example. In an illustrative embodiment, an additional locking device may be disposed along the back of the person with disabilities module to hold the wheelchair in place until it is released by crew members on the ground.

Configuration of customizable service space <NUM> at the aft end of an aircraft with a person with disabilities module, for example, may provide specialized seating for a person in a wheelchair that enables the person to enter the aircraft through the aft door and move directly to the specialized seating without having to be carried down the aisle to a seat by a special service crew. Existing aircraft aisles can not accommodate a wheelchair and a person with a disability is usually required to sit in an aircraft seat while their wheelchair is stowed during flight. Modular space <NUM> may be configured to provide wheelchair seating, allowing persons with disabilities to remain in their own chairs and easily access their seating on the aircraft. The person with disabilities module may be quickly installed during aircraft turn time in response to a passenger need on an upcoming flight, for example. Likewise, the module may be easily removed and replaced with another module when there is no passenger necessity requiring the person with disabilities module.

In one advantageous embodiment, where seating <NUM> is inserted into modular space <NUM>, additional passenger service units may be added to the bottom of module C <NUM>, such as passenger service units <NUM>, <NUM>, <NUM>, and <NUM>. Passenger service units may refer to, for example, without limitation, oxygen masks, air vents, emergency lights, attendant call buttons, and/or any other suitable passenger service unit. If any type of seating is provided in modular space <NUM>, passenger service units may be dispersed along the underside of module C <NUM>. In an advantageous embodiment where a type of seating is provided and module C <NUM> is removed from the configuration, such as in the business center example of <FIG>, passenger service units may be dispersed along the underside of arch <NUM>.

With reference now to <FIG>, an illustration of a customizable service space is depicted in accordance with an illustrative embodiment. Customizable service space <NUM> is an example of one implementation of customizable service space <NUM> in <FIG>.

Customizable service space <NUM> may include module <NUM> and module <NUM>. Module <NUM> may be a business center or work place implemented within a vehicle, such as vehicle <NUM> in <FIG>. Module <NUM> may include seating <NUM> and desk <NUM>, for example. Module <NUM> and module <NUM> may be configured with any number of components to provide a mobile working environment, for example.

Customizable service space <NUM> may include module A <NUM>, module B <NUM>, and modular space <NUM>. Module A <NUM> may be an example of one implementation of module A <NUM> in <FIG>. Module B <NUM> may be an example of one implementation of module B <NUM> in <FIG>. Modular space <NUM> may be an example of one implementation of modular space <NUM> in <FIG>.

Modular space <NUM> may include module <NUM>, module <NUM>, and module <NUM>. Module <NUM>, module <NUM>, and module <NUM> may be an example of one implementation of number of modules <NUM> in <FIG>, for example. Module <NUM>, module <NUM>, and module <NUM> may include modules specific to a galley service space, for example. Module <NUM> may include cart <NUM> and cart <NUM>, oven <NUM>, coffee maker <NUM>, storage <NUM>, and storage <NUM>.

Module <NUM> may include cart <NUM>, cart <NUM>, counter space <NUM>, storage <NUM>, storage <NUM>, storage <NUM>, and storage <NUM>. Module <NUM> may include cart <NUM>, cart <NUM>, oven <NUM>, coffee maker <NUM>, storage <NUM>, and storage <NUM>.

With reference now to <FIG>, an illustration of a module in a customizable service space is depicted in accordance with an illustrative embodiment. Module B <NUM> is an example of one implementation of module B <NUM> in <FIG>.

Module B <NUM> may be an illustrative example of a movable waste unit. Module B <NUM> includes hinged compartment <NUM> and sliding compartment <NUM>. Hinged compartment <NUM> may be a movable portion of module B <NUM> that provides access to sliding compartment <NUM> and secures sliding compartment <NUM> during transport. In one advantageous embodiment, sliding compartment <NUM> may be a waste storage unit. Sliding compartment <NUM> may be composed of a water tight, durable material, such as blow molded or rotor-molded plastic, for example. Sliding compartment <NUM> may accommodate trash and recyclable material, or the storage of all purpose trash bags that can be separated for recycling off the vehicle, for example. Sliding compartment <NUM> may include handle <NUM> for pulling sliding compartment <NUM> into alignment with doorway <NUM>. Alignment of sliding compartment <NUM> with doorway <NUM> may provide for removal of stored waste, such as trash or recyclable materials, by personnel outside the vehicle without requiring entrance into the vehicle, for example. In an illustrative example, sliding compartment <NUM> may be completely removable from module B <NUM> for cleaning and sanitation during vehicle turn time.

Sliding compartment <NUM> may include retractable drawer slides on the bottom surface of sliding compartment <NUM>. The retractable drawer slides may support and guide sliding compartment <NUM> into and out of module B <NUM>. This sliding system may allow for quick and easy removal of waste collected on a vehicle during transport, for example.

The illustration of module B <NUM> in <FIG> is not meant to imply physical or architectural limitations to the manner in which different advantageous embodiments may be implemented. Other components in addition and/or in place of the ones illustrated may be used. Some components may be unnecessary in some advantageous embodiments. Also, the blocks are presented to illustrate some functional components. One or more of these blocks may be combined and/or divided into different blocks when implemented in different advantageous embodiments.

Module B <NUM> may be an illustrative example of a movable waste unit. Module B <NUM> depicts module B <NUM> in <FIG> partially aligned with doorway <NUM>. Module B <NUM> includes hinged compartment <NUM> and sliding compartment <NUM>. Sliding compartment <NUM> may be a waste storage unit. Sliding compartment <NUM> may include sliding compartment door <NUM> for accessing the interior of sliding compartment <NUM>. Alignment of sliding compartment <NUM> with doorway <NUM> may provide for access to sliding compartment <NUM> without requiring personnel entrance into the vehicle, for example.

Module B <NUM> depicts module B <NUM> in <FIG> fully aligned with doorway <NUM>. Sliding compartment <NUM> may include sliding compartment door <NUM> for accessing the interior of sliding compartment <NUM>. Alignment of sliding compartment <NUM> with doorway <NUM> may provide for access to sliding compartment <NUM> without requiring personnel entrance into the vehicle, for example.

Module B <NUM> depicts sliding compartment <NUM> fully aligned with doorway <NUM> and having sliding compartment door <NUM> in an open position, allowing access to accessible interior <NUM> of sliding compartment <NUM>.

Module B <NUM> depicts sliding compartment <NUM> as viewed from the interior of a vehicle, such as vehicle <NUM> in <FIG>. Sliding compartment <NUM> is depicted as fully aligned with doorway <NUM>. Hinged compartment <NUM> is in an open position, allowing for movement of sliding compartment <NUM>. Indicator light <NUM> may be included on module B <NUM>. Indicator light <NUM> may be, for example, without limitation, a light-emitting diode (LED) light. In an illustrative example, indicator light <NUM> may light up when sliding compartment <NUM> is not locked in place. When sliding compartment <NUM> is installed and locked in place, indicator light <NUM> may turn off. Indicator light <NUM> may serve as a visual indication to ensure that sliding compartment <NUM> is locked in place prior to vehicle movement, such as an airplane taking off for flight for example.

With reference now to <FIG>, an illustration of a hierarchy of screens is depicted in accordance with an illustrative embodiment. Hierarchy of screens <NUM> may be an example of different functionalities of service space control system <NUM> presented on user interface <NUM> in <FIG>.

Hierarchy of screens <NUM> may begin with timeline screensaver <NUM>. Timeline screensaver <NUM> may be, for example, an image displayed when the display device is idle. The display device may be a touch screen panel, a handheld device, a computer monitor with keyboard and mouse peripherals, and/or any other suitable display device.

The user interface may be activated by user input, such as detection of the presence and location of a touch within the display area for example. Upon activation, the user interface may display thumbprint scan <NUM>. Thumbprint scan <NUM> may be capable of biometric scanning for information and security. Upon identification using biometric information, the user interface will display the appropriate screen or screen selection options in mode selection <NUM> based on clearance and/or authorized access. For example, if a maintenance or service worker authorized to reconfigure and service a customizable service space activates the user interface, the next screen presented may be mode selection <NUM> showing options reconfiguration mode <NUM> and service mode <NUM>. The authorized maintenance or service worker may then select which mode will be employed for the current operation. In another illustrative example, if a flight attendant activates the user interface, the next screen presented may be flight attendant functions <NUM>. The options presented in hierarchy of screens <NUM> are provided for illustrative purposes. Any number of different mode selection options and screen options may be presented in a service space control system over a user interface.

Mode selection <NUM> may further direct a user to functional components of a user interface. For example, reconfiguration mode <NUM> may direct a user to screen <NUM> displaying an image of a galley to unlatch center modules, such as modules <NUM>, <NUM>, and <NUM> in modular space <NUM> of <FIG>, for example. Screen <NUM> may provide an image of a customizable service space complete with the current configuration of modules. The image of the current configuration may allow for selection of individual and/or specific modules for unlatching and removal during reconfiguration, for example.

In another illustrative example, service mode <NUM> may direct a user to screen <NUM> displaying an image of a galley to unlatch trash and/or stowage or open all modules. Screen <NUM> may provide an image of a customizable service space complete with the current configuration of modules, which allows for selection of individual and/or specific modules for providing access to those modules. For example, a user may select module B <NUM> to access the trash storage bin located within module B <NUM> in <FIG> in order to remove collected trash during airplane turn time.

Flight attendant functions <NUM> may direct a user to function selection <NUM>. Function selection <NUM> may provide a number of different functional capabilities of a service space control system for selection by the user. For example, function selection <NUM> may include, without limitation, equipment log <NUM>, food/beverage inventory <NUM>, passengers with special needs <NUM>, passenger connections <NUM>, passenger manifest <NUM>, and/or any other suitable function selection.

The illustration of hierarchy of screens <NUM> in <FIG> is not meant to imply physical or architectural limitations to the manner in which different advantageous embodiments may be implemented. Other components in addition and/or in place of the ones illustrated may be used. Some components may be unnecessary in some advantageous embodiments. Also, the blocks are presented to illustrate some functional components. One or more of these blocks may be combined and/or divided into different blocks when implemented in different advantageous embodiments.

With reference now to <FIG>, an illustration of a service space control system is depicted in accordance with an illustrative embodiment. Service space control system <NUM> may be an example of one implementation of service space control system <NUM> in <FIG>.

Service space control system <NUM> may include display device <NUM>. Display device <NUM> may present user interface <NUM>. User interface <NUM> allows a user to interact with service space control system <NUM>.

Service space control system <NUM> provides vehicle personnel access to information, access to modules, and control of a customizable service space. Vehicle personnel may include, for example, without limitation, transportation personnel, service personnel, maintenance personnel, and/or any other suitable personnel. Transportation personnel may be, for example, flight attendants of an aircraft vehicle. Other functionalities that may be provided by service space control system <NUM> may include, without limitation, security of storage areas, galley equipment report logs, cabin controls, inventory, revenue tracking connecting information, passenger manifest, information management, and/or any other suitable transportation carrier functionality.

Display device <NUM> may be provided as a touch screen panel, a computer monitor with peripheral components such as keyboard and mouse, a handheld computing device, and/or any other suitable display device for presenting user interface <NUM>. User interface <NUM> consolidates information into a single presentation format and provides specific information about the vehicle, customizable service space, modules, passengers, and/or any other suitable information. User interface <NUM> provides security and electronic control functions that enable the access and removal of modules in a customizable service space. Security and electronic control functions may be, for example, without limitation, electronic latching process <NUM>, personnel authentication process <NUM>, access control process <NUM>, and modular configuration process <NUM> of <FIG>. For example, maintenance personnel can electronically unlatch and release a number of modules from a modular space without the use of tools and/or heavy equipment to quickly and efficiently remove and/or replace individual modules.

The illustration of service space control system <NUM> in <FIG> is not meant to imply physical or architectural limitations to the manner in which different advantageous embodiments may be implemented. Other components in addition and/or in place of the ones illustrated may be used. Some components may be unnecessary in some advantageous embodiments. Also, the blocks are presented to illustrate some functional components. One or more of these blocks may be combined and/or divided into different blocks when implemented in different advantageous embodiments.

With reference now to <FIG>, an illustration of a user interface is depicted in accordance with an illustrative embodiment. User interface <NUM> may be an example of one implementation of user interface <NUM> in <FIG>. User interface <NUM> may depict an example of one implementation of timeline screensaver <NUM> in <FIG>.

With reference now to <FIG>, an illustration of a user interface is depicted in accordance with an illustrative embodiment. User interface <NUM> may be an example of one implementation of user interface <NUM> in <FIG>. User interface <NUM> may depict an example of one implementation of thumbprint scan <NUM> in <FIG>. In an illustrative example, thumbprint scan <NUM> may include authentication request <NUM> and biometric scanning component <NUM>. Biometric scanning component <NUM> may be any type of biometric scanning device, such as a fingerprint scan, retinal scan, and/or any other suitable type of biometric detection device.

The illustration of user interface <NUM> in <FIG> is not meant to imply physical or architectural limitations to the manner in which different advantageous embodiments may be implemented. Other components in addition and/or in place of the ones illustrated may be used. Some components may be unnecessary in some advantageous embodiments. Also, the blocks are presented to illustrate some functional components. One or more of these blocks may be combined and/or divided into different blocks when implemented in different advantageous embodiments.

For example, other forms of authentication and/or user verification may be used in place of or in addition to biometric scanning. In one example, a unique identification code may be used to securely sign on to the service space control system. In another example, an identification badge with a radio frequency identification tag may be detected by the service space control system.

With reference now to <FIG>, an illustration of a mode selection is depicted in accordance with an illustrative embodiment. Mode selection <NUM> may be an example of one implementation of mode selection <NUM> in <FIG> over a user interface, such as user interface <NUM> in <FIG>.

Mode selection <NUM> may include flight attendant mode <NUM>, service mode <NUM>, and reconfiguration mode <NUM>. Flight attendant mode <NUM> may direct a user to a number of different flight attendant functions or capabilities, such as passenger list management, food and beverage inventory, identification of passengers with special needs and/or request, identification of passenger connections, equipment logs, and/or any other suitable function. Service mode <NUM> may be used by service personnel during vehicle turn time to replenish module contents or empty waste, such as trash collected in module B <NUM> in <FIG>, for example. Service mode <NUM> may also be used to replace a module, for example an empty food cart module with a full food cart module for the next flight. Reconfiguration mode <NUM> may be used by maintenance personnel, for example, to reconfigure a customizable space with a number of new modules.

With reference now to <FIG>, an illustration of a passenger connections screen is depicted in accordance with an illustrative embodiment. Passenger connections screen <NUM> may be an example of a screen presented when passenger connections <NUM> in <FIG> is selected over a user interface, such as user interface <NUM> in <FIG>.

Passenger connections screen <NUM> may include information about the number of connecting passengers <NUM>, status of connecting flights <NUM>, and other information about connecting passengers and/or flights. With reference now to <FIG>, an illustration of a user interface is depicted in accordance with an illustrative embodiment. User interface <NUM> may be an example of one implementation of user interface <NUM> in <FIG>. User interface <NUM> may depict an illustrative example of screen <NUM> in <FIG>.

User interface <NUM> may include customizable service space depiction <NUM> which provides information about the status of different modules within a customizable service space. For example, the status information may be whether a module is secured for transportation or not, whether a module is accessible or restricted, and/or any other suitable information about a module in a customizable service space.

With reference now to <FIG>, an illustration of a passengers with special needs screen is depicted in accordance with an illustrative embodiment. Passengers with special needs screen <NUM> may be an example of a screen presented when passengers with special needs <NUM> in <FIG> is selected over a user interface, such as user interface <NUM> in <FIG>.

Passengers with special needs screen <NUM> may include vehicle depiction <NUM> having information about passengers, for example. The information about passengers may include, for example, the seating diagram of the vehicle including the specific seating of passengers with disabilities <NUM>, premier passengers <NUM>, sky marshals <NUM>, and other information about passengers on a vehicle.

With reference now to <FIG>, an illustration of a user interface is depicted in accordance with an illustrative embodiment. User interface <NUM> may be an example of one implementation of user interface <NUM> in <FIG>.

User interface <NUM> may depict food/beverage inventory screen <NUM>. Food/beverage inventory screen <NUM> may be an example of a screen that is presented when food/beverage inventory <NUM> function is selected in <FIG>. Food/beverage inventory screen <NUM> may depict remaining meals <NUM>, type of meals <NUM>, beverage information <NUM>, and/or any other type of information about food or beverage modules in a customizable service space of a vehicle.

With reference now to <FIG>, an illustration of a flowchart of a process for configuring a customizable service space is depicted in accordance with an advantageous embodiment. The process in <FIG> may be implemented by service space control system <NUM> of <FIG>.

The process begins by receiving customized service space requirements (operation <NUM>). The process selects a number of modules to fulfill the requirements (operation <NUM>). The process then configures the service space with the number of modules (operation <NUM>). The process activates an electronic latching system to secure the number of modules (operation <NUM>), with the process terminating thereafter.

With reference now to <FIG>, an illustration of a flowchart of a process for reconfiguring a customizable service space is depicted in accordance with an advantageous embodiment. The process in <FIG> may be implemented by service space control system <NUM> in <FIG>.

The process begins by receiving new customized service space requirements (operation <NUM>). The process determines whether any existing modules in the service space meet the new requirements (operation <NUM>). If any of the existing modules in the service space meet the new requirements, the process identifies existing modules in the service space that will remain in the new configuration (operation <NUM>). The process then activates an electronic latching system to release each existing module in the service space that will be removed (operation <NUM>). If none of the existing modules in the service space meet the new requirements, the process moves to operation <NUM>.

The process receives new modules that fulfill the new customized service space requirements (operation <NUM>). The process then activates the electronic latching system to secure the new modules (operation <NUM>), with the process terminating thereafter.

With reference now to <FIG>, an illustration of a flowchart of a process for providing user access to a service space control process is depicted in accordance with an advantageous embodiment. The process in <FIG> may be implemented by user interface <NUM> of service space control system <NUM> in <FIG>.

The process begins by detecting user input (operation <NUM>). User input may be detected from a touch or presence of a user on a touch screen in one example. In another example, user input may be detected from a peripheral device, such as a mouse or keyboard. In yet another example, user input may be detected over a voice detection system, or any other suitable means for detecting user input.

The process presents an identification screen (operation <NUM>), providing a user with an area to input identification information. Identification information may be, for example, without limitation, biometric information, a password, a unique identification code, and/or any other identification information capable of being detected by a data processing system. Biometric information may include, for example, a fingerprint, retinal image, and/or any other suitable biometric information. The process receives the identification information (operation <NUM>), and determines whether the user is authorized to use the system (operation <NUM>). This determination may be made using a database, such as service space database <NUM> in <FIG>, for example, to retrieve identification and/or authentication information of a number of users authorized to use the system, and comparing the stored information with the identification information received in operation <NUM>. If the user is not authorized to use the system, the process terminates.

If the user is authorized to use the system, the process then identifies the modes the user is authorized to access (operation <NUM>). For example, a user may be authorized to access one or more modes. The process presents the mode selection (operation <NUM>). The mode selection may be presented to the user with the specific mode or number of modes that the user is authorized to access, allowing the user to select the mode of the user's choice. If the user is only authorized to access one mode, the mode selection may still be presented with all available modes, but the user may only be able to select the mode the user is authorized to access.

The process receives the mode selection from the user (operation <NUM>) and then the process presents a function selection (operation <NUM>). A function selection may display a number of different functional capabilities to be selected by the user. For example, different functional capabilities may include reconfiguration of a customizable service space, electronically unlatching or re-latching a number of modules in a customizable service space, accessing information about passengers in a vehicle, accessing information about a number of modules in a customizable service space, and/or any other suitable functionality.

The process receives a function selection by the user (operation <NUM>), with the process terminating thereafter. The functional selection may lead to further interactive capabilities by the user with the service space control process, such as data management for example.

With reference now to <FIG>, an illustration of a flowchart of a process for reconfiguring a customizable service space is depicted in accordance with an advantageous embodiment. The process in <FIG> may be executed by a user, such as user <NUM> in <FIG>, for example.

The process begins releasing a number of first modules in a service space (operation <NUM>). The number of first modules may be, for example, a number of modules that were installed in an initial configuration at purchase. The number of first modules may be released by a user, such as user <NUM> in <FIG>, interacting with service space control process <NUM> using user interface <NUM> to electronically release, or unlatch, the number of first modules, such as number of modules <NUM> in <FIG>.

Next, the process removes the number of first modules from the service space (operation <NUM>). The modules may be physically removed from the service space once they are electronically released, or unlatched, by sliding each module out of the service space, for example. In an illustrative example, where a sliding rail and track system is implemented, each module may slide out of the service space once the module is unlatched and be physically removed from the vehicle.

The process then inserts a number of second modules into the service space (operation <NUM>). The number of second modules may be modules chosen during a reconfiguration process, such as in <FIG> for example. The number of second modules may be selected by a user, such as user <NUM> in <FIG>, interacting with service space control process <NUM> using user interface <NUM> to reconfigured a customizable service space, such as customizable service space <NUM> in <FIG>.

Then the process secures the number of second modules in the service space (operation <NUM>), with the process terminating thereafter. The number of second modules may be secured by a user, such as user <NUM> in <FIG>, interacting with service space control process <NUM> using user interface <NUM> to electronically secure, or latch, the number of second modules, such as number of modules <NUM> in <FIG>.

The flowcharts and block diagrams in the different depicted embodiments illustrate the architecture, functionality, and operation of some possible implementations of apparatus and methods in different advantageous embodiments. In this regard, each block in the flowchart or block diagrams may represent a module, segment, function, and/or a portion of an operation or step. In some alternative implementations, the function or functions noted in the block may occur out of the order noted in the figures. For example, in some cases, two blocks shown in succession may be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved.

The different advantageous embodiments take into account and recognize that currently used galley area configurations for airplanes are configured at purchase to accommodate current market conditions. Standard designs are used and may be modified slightly at initial configuration to meet specific airline customer requirements. However, the different advantageous embodiments recognize that as the markets changes, airlines wish to modify the service and products they offer during in-flight service in order to reduce cost, increase revenue, or both. Modification from the initial at purchase configuration is both costly and time-consuming, and is often poorly executed because the modification desired was not originally anticipated by the initial configuration of the galley area.

The different advantageous embodiments provide a system and method for configuration of customer specific modules in a timely and cost effective manner. The system is capable of quick changes and modifications by having a modular space that may be configured with a number of different modules in a number of different configurations. A low-cost carrier or leased aircraft carrier may simply be able to pull out existing modules and insert new modules customized to suit their specific in-flight service plan. The customized service space enables efficient and cost-effective change and customization by using computer generated latching and locking devices that allow for multiple ways to configure a service space without having to modify the vehicle structure. The change may be essentially tool-less, removing existing service modules and installing new modules without tools, and reconfiguring the service space with minimal resources and time. In addition, the service space may be reconfigured for a number of different purposes other than the original purpose of the space at time of purchase. A galley area may become a business center, for example, by simply switching out a number of modules.

The different advantageous embodiments can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment containing both hardware and software elements. Some embodiments are implemented in software, which includes but is not limited to forms, such as, for example, firmware, resident software, and microcode.

Furthermore, the different embodiments can take the form of a computer program product accessible from a computer usable or computer readable medium providing program code for use by or in connection with a computer or any device or system that executes instructions. For the purposes of this disclosure, a computer usable or computer readable medium can generally be any tangible apparatus that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.

The computer usable or computer readable medium can be, for example, without limitation an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, or a propagation medium. Non limiting examples of a computer readable medium include a semiconductor or solid state memory, magnetic tape, a removable computer diskette, a random access memory (RAM), a read-only memory (ROM), a rigid magnetic disk, and an optical disk. Optical disks may include compact disk - read only memory (CD-ROM), compact disk - read/write (CD-R/W) and DVD.

Further, a computer usable or computer readable medium may contain or store a computer readable or usable program code such that when the computer readable or usable program code is executed on a computer, the execution of this computer readable or usable program code causes the computer to transmit another computer readable or usable program code over a communications link. This communications link may use a medium that is, for example without limitation, physical or wireless.

A data processing system suitable for storing and/or executing computer readable or computer usable program code will include one or more processors coupled directly or indirectly to memory elements through a communications fabric, such as a system bus. The memory elements may include local memory employed during actual execution of the program code, bulk storage, and cache memories which provide temporary storage of at least some computer readable or computer usable program code to reduce the number of times code may be retrieved from bulk storage during execution of the code.

Input/output or I/O devices can be coupled to the system either directly or through intervening I/O controllers. These devices may include, for example, without limitation to keyboards, touch screen displays, and pointing devices. Different communications adapters may also be coupled to the system to enable the data processing system to become coupled to other data processing systems or remote printers or storage devices through intervening private or public networks. Non-limiting examples are modems and network adapters are just a few of the currently available types of communications adapters.

Claim 1:
A vehicle (<NUM>) comprising:
a service space (<NUM>) capable of being configured;
a service space control system (<NUM>);
a number of modules (<NUM>) capable of being removably attached in a number of locations in the service space, wherein the number of modules (<NUM>) includes a number of radio frequency identification tags (<NUM>), wherein each module includes a radio frequency identification tag (<NUM>) capable of identifying a module to a data processing system and one or more additional radio frequency identification tags; and
a radio frequency identification system (<NUM>) located within the service space and configured to detect the number of radio frequency identification tags (<NUM>) located on the number of modules to provide information to the service space control system (<NUM>),
wherein the radio frequency identification system (<NUM>) comprises a number of radio frequency identification readers (<NUM>),
wherein a radio frequency identification reader of the number of radio frequency identification readers (<NUM>) is configured to detect all radio frequency identification tags (<NUM>) of a module (<NUM>) when the module (<NUM>) is inserted into service space (<NUM>),
wherein the radio frequency identification reader (<NUM>) of the number of radio frequency identification readers (<NUM>) is configured to transmit identification information detected from the number of radio frequency identification tags (<NUM>) to the service space control system (<NUM>) using a communications unit (<NUM>),
wherein the identification information is stored in a service space database (<NUM>).