Method, system and computer program product for creating customer layout configuration

Abstract

Methods, systems, and computer program products for creating a customer layout configuration are provided. The method includes pulling, from a customer database, a plurality of text documents specifying a customer's preference for the layout configuration. Technical requirements are determined from a requirement database tool based on customer preferences. Functional data and logical data are determined from a system architecture modeling tool based on customer preferences. A physical layout model of the vehicle is generated according to customer preferences in the text document within constraints of technical requirements, functional data, and logical data.

Description

Technical Field

[0001] The present disclosure relates generally to manufacturing and, more particularly, to computer-aided modeling systems for manufacturing. Background Art

[0002] Computer-aided modeling or computer-aided design (CAD) creates a virtual model of an object or system, which allows engineers and designers to visualize and simulate structures or processes. The configuration layout of a vehicle (such as an aircraft) can be customized according to specific customer needs. For the approved customer configuration, each commodity 3D space reservation model is also manually created in CAD. Summary of the invention

[0003] An exemplary embodiment provides a computer-implemented method for creating a customer layout configuration of a vehicle. The method includes pulling a plurality of text documents specifying customer preferences for the layout configuration from a customer database. Based on the customer preferences, determining technical requirements according to a requirements database tool. Based on the customer preferences, determining functional data and logical data according to a system architecture modeling tool. Based on the customer preferences in the text documents, generating a physical layout model of the vehicle within the constraints of the technical requirements, functional data, and logical data.

[0004] Another exemplary embodiment provides a system for creating a customer layout configuration of a vehicle. The system includes a storage device storing program instructions and a storage device operably connected to the storage device and configured to execute the program instructions so that the system: pulls a plurality of text documents specifying customer preferences for the layout configuration from a customer database; based on the customer preferences, determines technical requirements according to a requirements database tool; based on the customer preferences, determines functional data and logical data according to a system architecture modeling tool; and generates a physical layout model of the vehicle within the constraints of the technical requirements, functional data, and logical data according to the customer preferences in the text documents.

[0005] Another exemplary embodiment provides a computer program product for creating a customer layout configuration of a vehicle. The computer program product includes a computer-readable storage medium having program instructions embodied thereon to perform the following operations: pull a plurality of text documents specifying customer preferences for the layout configuration from a customer database; determine technical requirements based on the customer preferences according to a requirements database tool; determine functional data and logical data based on the customer preferences according to a system architecture modeling tool; and generate a physical layout model of the vehicle within the constraints of the technical requirements, functional data, and logical data based on the customer preferences in the text documents.

[0006] The features and functions can be achieved independently in various embodiments of the present disclosure or may be combined in yet other embodiments in which further details can be seen with reference to the following description and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] The novel features believed characteristic of the exemplary embodiments are set forth in the appended claims. However, the exemplary embodiments together with the preferred modes of use, further objects and features thereof will be best understood by reference to the following detailed description of exemplary embodiments of the disclosure when read in conjunction with the accompanying drawings, in which:

[0008] Figure 1 is a pictorial representation of a network of data processing systems in which illustrative embodiments may be implemented;

[0009] Figure 2 is a block diagram of a configuration layout system according to an exemplary embodiment;

[0010] Figure 3 shows an exemplary technology requirements matrix according to an exemplary embodiment;

[0011] Figure 4 depicts an exemplary functional diagram according to an exemplary embodiment;

[0012] Figure 5 depicts a logic diagram according to an exemplary embodiment;

[0013] Figure 6 depicts a 2D layout model according to an exemplary embodiment;

[0014] Figure 7 depicts a 3D physical model according to an exemplary embodiment;

[0015] Figure 8 depicts an illustration of a customer dashboard according to an exemplary embodiment;

[0016] Fig. 9 A flowchart depicting a process for creating a custom layout configuration for a vehicle according to an exemplary embodiment; and

[0017] Fig.10 is an illustration of a block diagram of a data processing system in accordance with an illustrative embodiment. DETAILED DESCRIPTION

[0018] The exemplary embodiments recognize and take into account that an automated CAD system cannot automatically create a three-dimensional (3D) model based on a custom configuration tool because the systems are not linked. Therefore, the 3D layout model must be created manually.

[0019] The exemplary embodiments provide a method for creating a customer layout configuration of a vehicle by linking the customer configuration with automatic CAD using model-based systems engineering that pulls together the requirements, functional data, and logical data associated with the customer configuration selections. Thus, the exemplary embodiments allow for the automatic generation of 2D and 3D physical models based on a text document provided by the customer regarding configuration layout preferences.

[0020] See also Figure 1 , depicts a pictorial representation of a network of data processing systems in which the exemplary embodiments may be implemented. Network data processing system 100 is a network of computers in which the exemplary embodiments may be implemented. Network data processing system 100 contains network 102, which is a medium for providing communication links between different devices and computers connected together within network data processing system 100. Network 102 may include connections such as wired, wireless communication links, or fiber optic cables.

[0021] In the depicted embodiment, server computer 104 and server computer 106 are connected to network 102 along with storage unit 108. In addition, client device 110 is connected to network 102. In the depicted embodiment, server computer 104 provides information, such as boot files, operating system images, and applications to client device 110. Client device 110 can be, for example, a computer, a workstation, or a network computer. As depicted, client device 110 includes client computers 112, 114, and 116. Client device 110 can also include other types of client devices, such as mobile phone 118, tablet computer 120, and smart glasses 122.

[0022] In this exemplary embodiment, server computer 104, server computer 106, storage unit 108, and client device 110 are network devices connected to network 102, where network 102 is a communication medium for these network devices. Some or all of client devices 110 may form an Internet of Things (IoT), where these physical devices may be connected to network 102 and exchange information with each other through network 102.

[0023] In this embodiment, client device 110 is a client to server computer 104. Network data processing system 100 may include additional server computers, client computers, and other devices not shown. Client device 110 connects to network 102 using at least one of a wired connection, a fiber optic connection, or a wireless connection.

[0024] Program code located in network data processing system 100 may be stored on a computer recordable storage medium and downloaded to the data processing system or other device for use. For example, program code may be stored on a computer recordable storage medium on server computer 104 and downloaded to client device 110 via network 102 for use on client device 110.

[0025] In the depicted embodiment, network data processing system 100 is the Internet, where network 102 represents a global collection of networks and gateways that use the Transmission Control Protocol / Internet Protocol (TCP / IP) protocol suite to communicate with each other. At the heart of the Internet is a backbone of high-speed data communication lines between major nodes or host computers, which consist of thousands of commercial, government, educational, and other computer systems that route data and messages. Of course, network data processing system 100 may also be implemented using many different types of networks. For example, network 102 may include at least one of the Internet, an intranet, a local area network (LAN), a metropolitan area network (MAN), and a wide area network (WAN). Figure 1 It is intended as an example, and not as an architectural limitation for the different exemplary embodiments.

[0026] See now Figure 2 , depicts a block diagram of a configuration layout system according to an exemplary embodiment. In this exemplary embodiment, the configuration layout system 200 includes a hardware (such as Figure 1 Components implemented in hardware (shown in FIG. 1 ) in network data processing system 100.

[0027] The configuration layout system 200 is capable of automatically creating requirements, functional, logical, and physical models using approved customer configuration option input data.

[0028] The configuration layout system 200 includes a database 202 for an aircraft customer configuration interior layout modeling tool (such as Pacelab), which contains customer options 204 for a vehicle (such as an aircraft) and a two-dimensional (2D) layout 206 provided by the customer. The customer options 204 can be selected by the customer from a list of options using a customer configuration tool 210. The customer can create a customer 2D layout 206 through a passenger cabin layout (LOPA) tool 208. The configuration layout system 200 automatically creates a physical 3D space reservation using approved customer options 204 and commodity design rules in a design rule database 244. Commodity refers to features that can be customized and arranged within a cabin layout according to customer preferences. Examples of commodities include seats, lavatories, galleys, toilets, and entertainment systems.

[0029] The customer may also use an internal configuration options (ICO) tool 226 to input selections into a color and material database 228 .

[0030] These selections and inputs from the customer take the form of a text document that is pulled into a Systems Modeling Language (SysML) tool 230, such as, for example, Magic Systems of Systems Architecture. The SysML tool 230 provides requirements, functions, and logic (RFL) capabilities associated with configuring the merchandise within the layout. The SysML 230 interacts with a requirements database tool 242 to determine technical requirements 232 for the customer 2D layout 206 and customer options 204 stored in the requirements database 240. An example of the requirements database tool 242 is DOORS provides the ability to capture, track, analyze and manage changes to information related to technical needs 232. Each commodity in the configuration layout (e.g., seating, kitchen, bathroom, etc.) has multiple technical needs 232 associated with its installation, which can be conveyed and tracked in a needs matrix and table (see Figure 3 ).

[0031] The requirements database tool 242 can provide technical requirements 232 related to several categories, such as airline repair and overall (AR&O), design requirements and objectives (DR&O), aircraft-level functional hazard assessment (AFHA), system functional hazard assessment (SFHA), Food and Drug Administration (FDA) requirements, customer needs, etc.

[0032] The SysML tool 230 helps determine the functional data 234 associated with the merchandise of the configuration layout. The functional data refers to the accompanying elements that must accompany the installation of the merchandise in the layout. For example, installing a galley in an aircraft also requires the provision of electricity and water. The functional data 234 can be presented in an activity diagram (see Figure 4 ). Configuration layout system 200 may use approved customer options 204 and commodity design rules in design rule database 244 to automatically create functional interface nodes (inputs and outputs).

[0033] Logic data 236 describes the operational interaction of components in a configuration layout that may exist in a block diagram (see Figure 5 ). Given standard components and structural constraints within a vehicle (such as an aircraft) and the characteristics of the commodity itself, the logical data 236 considers how the commodity needs to be installed, how its installation interacts with and affects other commodities and systems, and how other commodities and systems interact with and affect the installation of the commodity. The configuration layout system 200 can automatically connect the logical interface to the logical data 236 using the approved customer options 204 and the commodity design rules in the design rules database 244.

[0034] SysML Tool 230 also provides access to Team Work Cloud (TWC) and Connection to database 246. is a business and innovation platform that provides organizations with a holistic, real-time vision of SysML tools 230 business activities and ecosystem components.

[0035] The SysML tool 230 pushes customer technical requirements 232, functional data 234, and logical data 236 to a computer-aided design (CAD) tool 248. The CAD tool 248 also receives design rule data from a design rule database 244. Based on this data, the CAD tool 248 can automatically create a physical 2D layout model 250 (see Figure 6 ). The CAD tool 248 can then automatically create a 3D physical model 252 of the configuration layout from the 2D layout model 250 (see Figure 7 ).

[0036] Configuration layout system 200 may automatically connect all data from technical requirements 232 , functional data 234 , and logical data 236 to 3D physical model 252 based on the space reservation model tree in approved customer options 204 .

[0037] The 2D layout model 250 and 3D physical model 252 can be pushed to the Pacelab database 202 for customer verification or modification. The validation and verification dashboard 212 provides customers with a front-end tool to input their needs and preferences for the configuration layout, and to evaluate the configuration layout generated by the CAD tool 248 (see Figure 8 ) generated by the 2D layout model 250 and 3D physical model 252. The validation and verification dashboard 212 is a web-based model-based requirements engineering (MBRE) tool that utilizes a true single source database from SysML. The validation and verification dashboard 212 interacts with the TWC and 3DX database 246 through a structured query language (SQL) database 238. The validation and verification dashboard 212 provides a technical advantage of allowing a user to interact with and use the SysML tool 230 without having to learn and know SysML.

[0038] The Validation and Verification Dashboard 212 automates and provides traceability of design milestone requirements throughout the design process and enables automatic creation of new customer projects. These milestones include Assignment 214, Validation 216, Verification 218, Requirements 220, Design 222, and Integration 224. The Validation and Verification Dashboard 212 provides technical requirement traceability, design requirement traceability, color and material specification traceability, specification control drawings, and interface control drawings traceability.

[0039] SysML tools 230 are specifically concerned with the configuration layout of merchandise such as seating, galleys, and lavatories. Ceiling, galley, and sidewall layout tools 256 provide the remaining elements of the vehicle that form the context in which the merchandise must fit (see Figure 8 ). The ceiling, kitchen, and sidewall layout tool 256 interacts with the design rules database 244 and the SQL database 238 to provide input to the Pacelab database 202.

[0040] The configuration layout system 200 automatically pulls all requirements 220 from the requirements database 240 according to the customer options 204 and assigns the requirements using the validation and verification dashboard 212. Depending on the model generated by the CAD tool 248 (which incorporates the RFL constraints from SysML 230), the customer can use the validation and verification dashboard 212 to modify the layout design and resubmit it to the configuration layout system 200 for redesign.

[0041] Upon customer approval, CAD tool 248 may create specific part design 254 based on 3D physical model 252 .

[0042] The configuration layout system 200 may be implemented in software, hardware, firmware, or a combination thereof. When software is used, the operations performed by the configuration layout system 200 may be implemented in program code configured to run on hardware such as a processor unit. When firmware is used, the operations performed by the configuration layout system 200 may be implemented in program code and data and stored in a permanent memory to run on a processor unit. When hardware is used, the hardware may include circuits that operate to perform the operations in the configuration layout system 200.

[0043] In an exemplary embodiment, the hardware may take the form of at least one selected from the following: a circuit system, an integrated circuit, an application specific integrated circuit (ASIC), a programmable logic device, or some other suitable type of hardware configured to perform multiple operations. Using a programmable logic device, the device can be configured to perform multiple operations. The device can be reconfigured later or can be permanently configured to perform multiple operations. Programmable logic devices include, for example, programmable logic arrays, programmable array logic, field programmable logic arrays, field programmable gate arrays, and other suitable hardware devices. In addition, the process can be implemented in organic components integrated with inorganic components, and can be composed entirely of organic components other than humans. For example, these methods can be implemented as circuits in organic semiconductors.

[0044] Computer system 260 is a physical hardware system and includes one or more data processing systems. When more than one data processing system is present in computer system 260, those data processing systems communicate with each other using a communication medium. The communication medium may be a network. The data processing system may be selected from at least one of a computer, a server computer, a tablet computer, or some other suitable data processing system.

[0045] As described, computer system 260 includes multiple processor units 262 that can execute program code 264 that realizes the process in exemplary embodiment. As used herein, the processor unit in multiple processor units 262 is a hardware device, and includes those hardware circuits such as the response and processing instructions and program code of the operation computer on the integrated circuit. When multiple processor units 262 execute the program code 264 of the process, multiple processor units 262 are one or more processor units that can be on the same computer or on different computers. In other words, the process can be distributed between processor units on the same or different computers in the computer system. In addition, multiple processor units 262 can be processor units of the same type or different types. For example, multiple processor units can be selected from at least one of a single-core processor, a dual-core processor, a multi-processor core, a general-purpose central processing unit (CPU), a graphics processing unit (GPU), a digital signal processor (DSP) or a processor unit of some other type.

[0046] Figure 3 An example technical requirement matrix according to an exemplary embodiment is shown. The requirement matrix 300 displays the corresponding technical requirements of each design element in the configuration. In this embodiment, the row range 302 covers the internal configuration elements, and the column range 304 lists the associated technical requirements. The interface toolbar 306 allows the user to change the display details as needed.

[0047] The requirements matrix 300 organizes the technical requirements across different requirement levels from the aircraft level down to the subsystem level.

[0048] Figure 4 An exemplary functional diagram according to an exemplary embodiment is depicted. In this embodiment, the functional diagram 400 shows the Figure 2 404, a filling / drain valve 406, a pump 408, a pump relay 410, an internal line heater 412, and a pressure switch 414. These additional elements impose constraints on the installation of the water tank 402 in the layout.

[0049] Figure 5Depicted is a logic diagram according to an exemplary embodiment. In this embodiment, the logic diagram 500 shows a logic diagram according to logic data (such as Figure 2 500 illustrates the operational interactions between the elements of a service waste bin (e.g., logic data 236 in FIG. 500 ). Logic diagram 500 illustrates the sequence in which pressurized flushing fluid moves through filter 504, waste bin 506, drain line heater 508, and ball valve 510. Logic diagram 500 also represents the functionality provided by each element in the logic sequence.

[0050] Functional and logical data, such as provided by functional diagram 400 and logical diagram 500, identify how and where the components of the commodity are connected before continuing to build 2D and 3D models. The functional and logical data presents connectivity in SysML and works within the constraints of the components in the vehicle design that do not vary with customer preferences.

[0051] Using the above example of a drinking water and vacuum waste system, the functional and logical data takes into account the locations of given elements (such as, for example, water tanks, water pumps, waste tanks, vacuum blowers, and service panels) for a specific model of aircraft and is not affected by customer preferences. The functional and logical data generated by the SysML tool takes these constraints into account before modeling the physical layout.

[0052] Figure 6 A 2D layout model according to an exemplary embodiment is depicted. 2D layout model 600 is an example of 2D layout model 250 generated by CAD tool 248 according to input from SysML, tool 230 , and design rules database 244 .

[0053] Figure 7 A 3D physical model is depicted in accordance with an exemplary embodiment. 3D physical model 700 is an example of 3D physical model 252 generated by CAD tool 248 from 2D layout model 250 .

[0054] Figure 8 Depicted is an illustration of a customer dashboard according to an exemplary embodiment. Dashboard 800 is Figure 2 800. Toolbar 802 in dashboard 800 allows the customer to select and customize configuration elements according to the model of vehicle / aircraft. As the customer adds and adjusts elements for the configuration, the layout is shown in display area 804. Also shown in display area 804 are the components from Figure 2 Additional features of the aircraft (eg, galley P48) are provided by input from the ceiling, galley, and sidewall layout tool 256 in FIG.

[0055] Fig. 9A flow chart depicts a process for creating a custom layout configuration for a vehicle according to an exemplary embodiment. Process 900 may be implemented in hardware, software, or both. When implemented in software, the process may take the form of program code executed by one or more processor units in one or more hardware devices in one or more computer systems. For example, process 900 may be implemented in Figure 2 The configuration layout system 200 is implemented in the computer system 260 in the system.

[0056] Process 900 begins by pulling a plurality of text documents specifying customer preferences for layout configurations from a customer database (operation 902). The customer preferences may include at least one of a two-dimensional interior arrangement, a list of customer configuration options, and colors and materials.

[0057] Process 900 determines technical requirements from a requirements database tool based on customer preferences (operation 904). Process 900 also determines functional data and logical data from a system architecture modeling tool based on customer preferences (operation 906). Technical requirements, functional data, and logical data may be determined via customer configuration options.

[0058] Process 900 then generates a physical layout model of the vehicle based on the customer preferences in the text document within the constraints of the technical requirements, functional data, and logical data (operation 908). The physical layout model may include a two-dimensional layout model.

[0059] Process 900 may generate a three-dimensional model from a two-dimensional layout model (operation 910 ).

[0060] Process 900 may add technical requirements, functional data, and logical data to the customer model configuration tree (operation 912).

[0061] Process 900 provides the physical layout model to the customer via the dashboard interface for verification or modification of the customer's preferences (operation 914 ).

[0062] In response to a modification of the customer preferences (operation 914), process 900 returns to operation 902. If there are no modifications from the customer, the physical layout model is validated (operation 916). Process 900 then ends.

[0063] The flow charts and block diagrams in the different depicted embodiments show the architecture, function and operation of some possible implementations of the device and method in the exemplary embodiments. In this regard, each box in the flow chart or block diagram can represent at least one of a part of a module, a section, a function or an operation or a step. For example, one or more boxes can be implemented as a combination of program code, hardware, or program code and hardware. When implemented in hardware, the hardware can, for example, take the form of an integrated circuit that is manufactured or configured to perform one or more operations in the flow chart or block diagram. When implemented in a combination of program code and hardware, the implementation can take the form of firmware. Each box in the flow chart or block diagram can be implemented using a combination of a dedicated hardware system or dedicated hardware that performs different operations and a program code run by dedicated hardware.

[0064] In some alternative implementations of the exemplary embodiments, one or more functions indicated in the blocks may not occur in the order indicated in the figure. For example, in some cases, two blocks shown in succession may be performed substantially simultaneously, or the blocks may sometimes be performed in reverse order, depending on the functions involved. In addition, other blocks may be added in addition to the blocks shown in the flow chart or block diagram.

[0065] Now turn to Fig.10 , depicts an illustration of a block diagram of a data processing system according to an exemplary embodiment. Data processing system 1000 may be used to implement Figure 1 The server computers 104 and 106 and the client device 110 and Figure 2 1000. In the exemplary embodiment, data processing system 1000 includes communications framework 1002, which provides communications between processor unit 1004, memory 1006, persistent storage 1008, communications unit 1010, input / output (I / O) unit 1012, and display 1014. In this embodiment, communications framework 1002 takes the form of a bus system.

[0066] Processor unit 1004 is used to execute instructions of software that may be loaded into memory 1006. Processor unit 1004 may be multiple processors, multiple processor cores, or some other type of processor, depending on the specific implementation. In an implementation, processor unit 1004 includes one or more conventional general-purpose central processing units (CPUs). In an alternative implementation, processor unit 1004 includes one or more graphics processing units (GPUs).

[0067] Memory 1006 and permanent storage 1008 are embodiments of storage 1016. A storage device is any hardware capable of storing information such as, for example but not limited to, data, program code in the form of a function, or at least one of other suitable information on a temporary basis, on a permanent basis, or on both a temporary basis and a permanent basis. In these exemplary embodiments, storage 1016 may also be referred to as a computer-readable storage device. In these embodiments, memory 1006 may be, for example, a random access memory or any other suitable volatile or non-volatile storage device. Persistent storage 1008 may take various forms, depending on the particular implementation.

[0068] For example, permanent storage 1008 may include one or more components or devices. For example, permanent storage 1008 may be a hard drive, a flash memory, a rewritable optical disk, a rewritable magnetic tape, or some combination thereof. The media used by permanent storage 1008 may also be removable. For example, a removable hard drive may be used for permanent storage 1008. In these exemplary embodiments, communication unit 1010 provides for communication with other data processing systems or devices. In these exemplary embodiments, communication unit 1010 is a network interface card.

[0069] Input / output unit 1012 allows for input and output of data with other devices that may be connected to data processing system 1000. For example, input / output unit 1012 may provide a connection for user input through at least one of a keyboard, a mouse, or some other suitable input device. In addition, input / output unit 1012 may send output to a printer. Display 1014 provides a mechanism for displaying information to a user.

[0070] Instructions for at least one of an operating system, applications, or programs may be located in storage devices 1016 that are in communication with processor unit 1004 through communications framework 1002. The processes of the different embodiments may be performed by processor unit 1004 using computer-implemented instructions, which may be located in a memory, such as memory 1006.

[0071] These instructions are referred to as program code, computer usable program code, or computer readable program code that can be read and executed by a processor in processor unit 1004. The program code in different embodiments may be implemented on different physical or computer readable storage media, such as memory 1006 or persistent storage 1008.

[0072] Program code 1018 is located in functional form on computer readable medium 1020, which is selectively removable and can be loaded or transferred to data processing system 1000 for execution by processor unit 1004. In these exemplary embodiments, program code 1018 and computer readable medium 1020 form a computer program product 1022. In one embodiment, computer readable medium 1020 may be computer readable storage medium 1024 or computer readable signal medium 1026.

[0073] In these exemplary embodiments, computer-readable storage media 1024 is a physical or tangible storage device for storing program code 1018, rather than a medium for propagating or transmitting program code 1018. As used herein, computer-readable storage media 1024 should not be interpreted as being a transient signal per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through waveguides or other transmission media (e.g., light pulses through fiber optic cables), or, as used herein, electrical signals transmitted by linear transmission, and should not be interpreted as being a transient signal per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through waveguides or other transmission media (e.g., light pulses through fiber optic cables), or electrical signals transmitted by wires.

[0074] Alternatively, program code 1018 may be transferred to data processing system 1000 using computer readable signal media 1026. Computer readable signal media 1026 may be, for example, a propagated data signal containing program code 1018. For example, computer readable signal media 1026 may be at least one of an electromagnetic signal, an optical signal, or any other suitable type of signal. These signals may be transmitted via at least one communication link, such as a wireless communication link, a fiber optic cable, a coaxial cable, an electrical wire, or any other suitable type of communication link.

[0075] The different components shown for data processing system 1000 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 shown for data processing system 1000. Fig.10 Other components shown in the example embodiments may be different from those shown. The different embodiments may be implemented using any hardware device or system capable of running program code 1018.

[0076] As used herein, when used with a list of items, the phrase "at least one of" means that different combinations of one or more of the listed items may be used, and only one of each item in the list may be required. In other words, "at least one of" means that any combination of items and numbers of items in the list may be used, but not all of the items in the list are required. An item may be a specific object, thing, or category.

[0077] For example, but not limited to, "at least one of item A, item B, or item C" may include item A, item A and item B, or item B. This embodiment may also include item A, item B, and item C, or item B and item C. Of course, there may be any combination of these items. In some exemplary embodiments, "at least one" may be, for example, but not limited to, two items A; one item B; and ten items C; four items B and seven items C; or other suitable combinations.

[0078] As used herein, when "a plurality" is used with reference to an item, it refers to one or more items. For example, "a plurality of networks of different types" is one or more networks of different types. In an exemplary embodiment, "a set" as used with reference to an item refers to one or more items. For example, a set of metrics is one or more of the metrics.

[0079] Descriptions of different exemplary embodiments have been presented for purposes of illustration and description, and are not intended to be exhaustive or limited to the embodiments of the disclosed forms. Different exemplary embodiments describe components that perform actions or operations. In exemplary embodiments, components may be configured to perform the described actions or operations. For example, components may have a configuration or design of a structure that provides the components with the ability to perform the actions or operations described as being performed by the components in the exemplary embodiments. In addition, in the context of using the terms "comprises," "comprising," "having," "containing," and variations thereof in this article, these terms are intended to be inclusive in a manner similar to the term "comprises" as an open transition word, without excluding any additional or other elements.

[0080] Many modifications and variations will be apparent to those of ordinary skill in the art. In addition, different exemplary embodiments may provide different features than other desired embodiments. The selected one or more embodiments are selected and described to best explain the principles of the embodiments, the practical application, and to enable others of ordinary skill in the art to understand the disclosure of various embodiments with various modifications suitable for the particular use contemplated.

Claims

1. A computer-implemented method for creating a custom layout configuration of a vehicle, the method comprising: Using multiple processors (262), the following operations are performed: pulling ( 902 ) from a customer database ( 202 ) a plurality of text documents specifying customer preferences for layout configurations ( 206 ); determining (904) technical requirements (232) based on the customer preferences according to a requirements database tool (242); determining (906) functional data (234) and logical data (236) according to a system architecture modeling tool (230) based on the customer preferences; as well as Based on the customer preferences in the text document, a physical layout model (250) of the vehicle is generated (908) within the constraints of the technical requirements, the functional data, and the logical data.

2. The method according to claim 1, wherein: The physical layout model includes a two-dimensional layout model.

3. The method according to claim 2, further comprising: A three-dimensional model (252) is generated (910) from the two-dimensional layout model.

4. The method according to claim 1, further comprising: The technical requirements, the functional data, and the logical data are added (912) to a customer model configuration tree.

5. The method according to claim 1, further comprising: The physical layout model is provided (914) to the customer via a dashboard interface (212) for verification or modification of the customer preferences.

6. The method according to claim 1, wherein: The customer preferences include at least one of the following: 2D interior layout; A list of customer configuration options; and Color and material.

7. The method according to claim 1, wherein: The technical requirements, the functional data and the logical data are determined by customer configuration options (204).

8. A system for creating a custom layout configuration of a vehicle, the system comprising: A storage device (1016) storing program instructions; One or more processors (1004) operably connected to the storage device and configured to execute the program instructions so that the system: pulling ( 902 ) from a customer database ( 202 ) a plurality of text documents specifying customer preferences for layout configurations ( 206 ); determining (904) technical requirements (232) based on the customer preferences according to a requirements database tool (242); determining (906) functional data (234) and logical data (236) according to a system architecture modeling tool (230) based on the customer preferences; as well as Based on the customer preferences in the text document, a physical layout model (250) of the vehicle is generated (908) within the constraints of the technical requirements, the functional data, and the logical data.

9. The system according to claim 8, wherein: The physical layout model includes a two-dimensional layout model.

10. The system of claim 9, further comprising generating (910) a three-dimensional model (252) from the two-dimensional layout model.

11. The system of claim 8, further comprising adding (912) the technical requirements, the functional data, and the logical data to a customer model configuration tree.

12. The system of claim 8, further comprising providing (914) the physical layout model to the customer via a dashboard interface (212) for verification or modification of the customer preferences.

13. The system according to claim 8, wherein: The customer preferences include at least one of the following: 2D interior layout; A list of customer configuration options; and Color and material.

14. The system according to claim 8, wherein: The technical requirements, the functional data and the logical data are determined by customer configuration options (204).

15. A computer program product for creating a custom layout configuration of a vehicle, the computer program product comprising: A computer readable storage medium (1024) having program instructions embodied thereon to: pulling ( 902 ) from a customer database ( 202 ) a plurality of text documents specifying customer preferences for layout configurations ( 206 ); determining (904) technical requirements (232) based on the customer preferences according to a requirements database tool (242); determining (906) functional data (234) and logical data (236) according to a system architecture modeling tool (230) based on the customer preferences; as well as Based on the customer preferences in the text document, a physical layout model (250) of the vehicle is generated (908) within the constraints of the technical requirements, the functional data, and the logical data.

16. The computer program product of claim 15, further comprising: A three-dimensional model (252) is generated (910) from the physical layout model.

17. The computer program product of claim 15, further comprising: The technical requirements, the functional data, and the logical data are added (912) to a customer model configuration tree.

18. The computer program product of claim 15, further comprising: The physical layout model is provided (914) to the customer via a dashboard interface (212) for verification or modification of the customer preferences.

19. The computer program product of claim 15, wherein: The customer preferences include at least one of the following: 2D interior layout; A list of customer configuration options; and Color and material.

20. The computer program product of claim 15, wherein: The technical requirements, the functional data and the logical data are determined by customer configuration options (204).

Images