Patent Publication Number: US-2023153064-A1

Title: Method for automatically matching chart names

Description:
CROSS-REFERENCE TO RELATED APPLICATIONS 
     The present application is related to and claims the benefit of the earliest available effective filing dates from the following listed applications (the “Related applications”) (e.g., claims earliest available priority dates for other than provisional patent applications (e.g., under 35 USC § 120 as a continuation in part) or claims benefits under 35 USC § 119(e) for provisional patent applications, for any and all parent, grandparent, great-grandparent, etc. applications of the Related applications). 
     RELATED APPLICATIONS 
     U.S. Provisional Patent Application Ser. No. 63/278,576 entitled SYSTEMS AND METHODS FOR GENERATION, SELECTION, AND DISPLAY OF MAP-BASED CHART DATABASES FOR USE WITH CERTIFIED AVIONICS SYSTEMS and filed Nov. 12, 2021; 
     Concurrently filed U.S. patent application Ser. No. ______ entitled TOOL TO FACILITATE CUSTOMER GENERATED CHART DATABASES FOR USE WITH A CERTIFIED AVIONICS SYSTEM and having docket number 131418US01; and 
     Concurrently filed U.S. patent application Ser. No. ______ entitled ELECTRONIC CHART APPLICATION WITH ENHANCED ELEMENT SEARCHING AND HIGHLIGHTING USING GENERIC THIRD-PARTY DATA and having docket number 131318US01. 
    
    
     BACKGROUND 
     Aircraft pilots undergo periods of high workload at specific time points in flight. Flight procedures, particularly flight procedures relating to navigation, can be particularly cognitively taxing. These procedures initially require the pilot to upload a navigation chart upon a display, such as a display on a flight management system (FMS), that is specific for the procedure. 
     Uploading and displaying aircraft navigation charts based upon specific navigation procedures can be particularly troublesome and time-consuming. Navigation charts are available from several vendors, with some vendors offering tens of thousands of different navigation charts, which must be matched to thousands of procedural names. Navigation chart names may be short/abbreviated descriptions of the chart or chart characteristics, or may have many (e.g., ˜90) characters, and it is often not obvious to a pilot whether a specific navigation chart is relevant to the navigation procedure. Similarly, procedure names are often short/abbreviated descriptions of the of the procedure or a characteristic of the procedure. For example, a procedure name may include the designation of a specific runway of an airport for landing. These abbreviated procedure names and associated chart names often do not match in an immediately meaningful manner. To illustrate this, a chart  90  comparing a sampling of FMS procedure names with corresponding navigation chart names is shown in  FIG.  1 A . 
     Although some vendors insert a match code into a navigation chart that matches the procedure to the correct navigation chart, there are vendors that do not offer matching services, and physically matching large numbers of navigation charts to navigation procedures is labor and cost intensive. Accordingly, it would be advantageous to provide a system and method that overcomes the shortcomings described above. 
     SUMMARY 
     A method for correlating a first item to a second item is disclosed. In one or more embodiments, the method includes detecting a first identifier associated with the first item. In one or more embodiments, the method further includes detecting a second identifier associated with the second item. In one or more embodiments, the method further includes executing a matching procedure configured to match the first simplified identifier to the second identifier and generate a match value. In one or more embodiments, the method further includes comparing the first simplified identifier to the second identifier. In one or more embodiments, the method further includes generating the match value between the first simplified identifier and the second identifier. In one or more embodiments, the method further includes reporting a correlation between the first item and the second item based on the match value. 
     In some embodiments, simplifying the first identifier, includes generating a codex string configured as character string based on the first identifier. In some embodiments, simplifying the first identifier includes generating a codex value configured as a bit field based on the first identifier. In some embodiments, simplifying the first identifier includes removing nonessential letters. In some embodiments, simplifying the first identifier includes setting one or more bits of the codex value based on the first identifier. In some embodiments, simplifying the first identifier i includes adding one or more sub-strings of the first identifier to the codex string. 
     In some embodiments, executing a matching procedure configured to match the first identifier to the second identifier and generate a match value further includes determining a second identifier type of the second identifier. In some embodiments, executing a matching procedure configured to match the first identifier to the second identifier and generate a match value further includes comparing bits in the codex value and values in the codex string to the second identifier. In some embodiments, executing a matching procedure configured to match the first identifier to the second identifier and generate a match value further includes generating a match value based on the comparison between the first identifier and the second identifier. 
     In some embodiments of the method, the first item and the second item are configured as electronic files. 
     In some embodiments of the method the first item is configured as a chart, and the second item is configured as a procedure. 
     In some embodiments of the method, the codex string includes at least one of a moniker name, a procedure name, or a geographic location. 
     In some embodiments of the method, the geographical location includes a runway number. 
     In some embodiments of the method, simplifying the first identifier is performed in a non-mobile computing environment, wherein executing the matching procedure is performed in a mobile computing environment. 
     In some embodiments of the method, the codex value includes a least one of an equipment type or document characteristic. 
     In some embodiments of the method, the second identifier is configured as a second simplified identifier. 
     A system is disclosed. In one or more embodiments, the system includes a controller configured to correlating a first item to a second item. In one or more embodiments, the controller includes one or more processors. In one or more embodiments, the controller further includes a memory configured to store data and instructions executable by the one or more processors. In one or more embodiments, the instructions include detecting a first identifier associated with the first item. In one or more embodiments, the instructions further include detecting a second identifier associated with the second item. In one or more embodiments, the instructions further include executing a matching procedure configured to match the first identifier to the second identifier and generating a match value. In one or more embodiments, executing a matching procedure includes comparing the first identifier to the second identifier. In one or more embodiments, executing a matching procedure further includes generating the match value between the first identifier and the second identifier. In one or more embodiments, the instructions further include reporting a correlation between the first item and the second item based on the match value. 
     In some embodiments of the system, the instructions further include simplifying the first identifier In some embodiments of the system, simplifying the first identifier includes generating a codex string configured as character string based on the first identifier. In some embodiments of the system, simplifying the first identifier includes generating a codex value based on the first identifier. In some embodiments of the system, simplifying the first identifier includes removing nonessential letters. In some embodiments of the system simplifying the first identifier includes setting one or more bits of the codex value based on the first identifier. In some embodiments of the system, simplifying the first identifier includes adding one or more sub-strings of the first identifier to the codex string. 
     In some embodiments of the system, executing a matching procedure includes determining a second identifier type of the second identifier. In some embodiments of the system, executing a matching procedure further includes comparing bits in the codex value and values in the codex string to the second identifier. In some embodiments of the system, executing a matching procedure further includes generating a match value based on the comparison between the first simplified identifier and the second identifier. 
     In some embodiments of the system, wherein the first item and the second item are configured as electronic files. 
     In some embodiments of the system, the first item is configured as a chart, and the second item is configured as a procedure. 
     In some embodiments of the system, the second identifier is simplified. 
     This Summary is provided solely as an introduction to subject matter that is fully described in the Detailed Description and Drawings. The Summary should not be considered to describe essential features nor be used to determine the scope of the Claims. Moreover, it is to be understood that both the foregoing Summary and the following Detailed Description are example and explanatory only and are not necessarily restrictive of the subject matter claimed. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
       The detailed description is described with reference to the accompanying figures. The use of the same reference numbers in different instances in the description and the figures may indicate similar or identical items. Various embodiments or examples (“examples”) of the present disclosure are disclosed in the following detailed description and the accompanying drawings. The drawings are not necessarily to scale. In general, operations of disclosed processes may be performed in an arbitrary order, unless otherwise provided in the claims. In the drawings: 
         FIG.  1 A  is a chart comparing FMS procedure names with corresponding chart names; 
         FIG.  1 B  is a block diagram of a system  100  within a computing environment  102  configured to facilitate the matching of a first item to a second item, in accordance with one or more embodiments of the disclosure; 
         FIG.  2    is a drawing diagram illustrating a computing environment for a system comprising an aircraft and an air traffic control tower in accordance with one or more embodiments of the disclosure; 
         FIG.  3    is a flow diagram illustrating a method for correlating a first item to a second item, in accordance with one or more embodiments of the disclosure; 
         FIG.  4    is a block diagram of a flow chart illustrating a method for converting a first identifier into a first simplified identifier, in accordance with one or more embodiments of the disclosure; 
         FIG.  5    is a chart illustrating an example of a codex value, in accordance with one or more embodiments of the disclosure; 
         FIG.  6    is a chart illustrating a list of letters and words that may be removed from the first identifier, in accordance with one or more embodiments of the disclosure; 
         FIG.  7    is a block diagram of a flow chart illustrating a method for executing a matching procedure configured to match the first simplified identifier to the second simplified identifier, in accordance with one or more embodiments of the disclosure; and 
         FIG.  8    is a chart illustrating a list of codex value bits and corresponding 1 st  letter of a procedure name, in accordance with one or more embodiments of the disclosure. 
     
    
    
     DETAILED DESCRIPTION 
     Before explaining one or more embodiments of the disclosure in detail, it is to be understood that the embodiments are not limited in their application to the details of construction and the arrangement of the components or steps or methodologies set forth in the following description or illustrated in the drawings. In the following detailed description of embodiments, numerous specific details may be set forth in order to provide a more thorough understanding of the disclosure. However, it will be apparent to one of ordinary skill in the art having the benefit of the instant disclosure that the embodiments disclosed herein may be practiced without some of these specific details. In other instances, well-known features may not be described in detail to avoid unnecessarily complicating the instant disclosure. 
     As used herein a letter following a reference numeral is intended to reference an embodiment of the feature or element that may be similar, but not necessarily identical, to a previously described element or feature bearing the same reference numeral (e.g.,  1 ,  1   a ,  1   b ). Such shorthand notations are used for purposes of convenience only and should not be construed to limit the disclosure in any way unless expressly stated to the contrary. 
     Further, unless expressly stated to the contrary, “or” refers to an inclusive or and not to an exclusive or. For example, a condition A or B is satisfied by anyone of the following: A is true (or present) and B is false (or not present), A is false (or not present) and B is true (or present), and both A and B are true (or present). 
     In addition, use of “a” or “an” may be employed to describe elements and components of embodiments disclosed herein. This is done merely for convenience and “a” and “an” are intended to include “one” or “at least one,” and the singular also includes the plural unless it is obvious that it is meant otherwise. 
     Finally, as used herein any reference to “one embodiment” or “some embodiments” means that a particular element, feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment disclosed herein. The appearances of the phrase “in some embodiments” in various places in the specification are not necessarily all referring to the same embodiment, and embodiments may include one or more of the features expressly described or inherently present herein, or any combination of sub-combination of two or more such features, along with any other features which may not necessarily be expressly described or inherently present in the instant disclosure. 
     A system and method for matching procedure names with associated chart names are presented. The method includes simplifying the chart name, then performing a name-matching procedure. The method reports to a user, such as a pilot, a chart name, or a list of chart names, that most likely matches the chart associated with a procedure. The method greatly simplifies the arduous process of matching a chart name with a FMS procedure, as the digital representation of paper charts used in navigation come from different sources with differing or no standards (e.g., Federal Aviation Administration (FAA) Department of Defense (DOD), foreign governments, independent contractors). FMS procedure names are also difficult to predict, as FMS procedure names follow a general pattern, but do not follow a precise standard. The method to associate these names is innovative. Off-line, the chart names are parsed and certain data is stored. At run time, this data is used in a series of comparisons against the procedure name, airport identifier, procedure type, and other information to find match candidates. Additional comparisons increase the likelihood that those candidates are valid matches. A high-probability match or set of matches is presented to the pilot, reducing the time needed to select a chart. 
       FIG.  1 B  is a block diagram of a system  100  within a computing environment  102  configured to facilitate the matching of a first item to a second item, in accordance with one or more embodiments of the disclosure. The first item and the second item may each include any type of file, document, list, chart, procedure, or any named entity wherein the name or identifier of the first item is to be associated with a name or identifier of the second item. For example, the first item may be configured as a chart with a first identifier (e.g., an FMS navigation chart configured with a chart name), and the second item may be configured as procedure with a second identifier (e.g., a specifically-named landing procedure). In another example, the first item may be configured as a text file that includes a first identifier configured as a short filename (e.g., SFN or 8.3 filename) and the second item may be configured as a spreadsheet file configured with a list of second identifiers (e.g., a column of named entries), one of which is the second identifier that is associated with the first item. In another example, the first item and second item may be configured as associated text files (e.g., user manuals for a vacuum cleaner) with the text and identifiers of the first item and the second item each written in different languages. 
     The system  102  may be configured as a stand-alone monolithic processing device, or as a component or module within a larger computing framework. For example, one or more components of the system  102  may be configured as a component or tool within a toolkit for displaying graphics. For instance, in some embodiments, the system  102  is incorporated within the Electronic Charts Application Tool Suite (ECATS) toolkit as described in U.S. Provisional Patent Application Ser. No. 63/278,576 entitled SYSTEMS AND METHODS FOR GENERATION, SELECTION, AND DISPLAY OF MAP-BASED CHART DATABASES FOR USE WITH CERTIFIED AVIONICS SYSTEMS and filed Nov. 12, 2021, which is incorporated by referenced in its entirety. The system  100  may also be configured as a multi-component system, as shown in  FIG.  2   . For example, the initial processing of the first identifier and/or the second identifier may be accomplished off-line in a separate system  100  or system component than the matching of the first identifier and second identifier. For instance, the system  100  may perform initial processing may in a non-mobile computing environment  204  (e.g., in an air traffic control tower  206  or other building), whereas the matching may be performed on a mobile computing environment  208  on-board an aircraft  212  (e.g., a mobile computing environment). Data from the initial processing may be physically inputted onto the aircraft  212  via a technician while the aircraft  212  is in service, or may be sent directly via a wireless signal  216 . Performing initial processing off-line and performing matching at run-time saves computing space at run-time and allows quicker response to the pilot when compared to performing both initial processing and matching at run-time. Referring back to  FIG.  1 B , the system  100  and/or the computing environment  102  may include an input device  104 , an output device  108 . The system  100  further includes a controller  112  configured to facilitate the functions of the system  100 . The controller may also be coupled to the input device  104  and the output device  108 , as well as to a network  114 . 
     In embodiments, the input device  104  inputs first item data, including first identifier data, and second item data, including second identifier data, into the system  100 . The input device  104  may be configured as any type of input device including but not limited to a keyboard, a scanner, a camera, or data port. For example, the input device  104  may be configured as a scanner configured to scan a graphic or list (e.g., a graphic or list of a physical avionics chart) into the system. In another example, the input device  104  may be configured as a USB port configured to receive a USB memory device having avionics charts (e.g., a digital navigation chart of a flight management system (FMS)) or avionic chart names loaded onto it (e.g., as a pdf. file, jpg. file, text file, or other type of file). In another example, the input device  104  may include a data port configured to receive data from the network  114 . 
     In embodiments, the output device  108  may be configured to report matching data and/or output candidate first items from the system  100  to a user and may be configured as any type of output device  108  including but not limited to a display, a printer, or any type of data port. For example, the output device  108  may be configured as a computer screen. In another example, the output device  108  may be configured as a data port connected to the network  114 . 
     In embodiments, the controller  112  includes one or more processors  116 , a memory  120 , and a communication interface  124 . The one or more processors  116  may include any processor or processing element known in the art. For the purposes of the present disclosure, the term “processor” or “processing element” may be broadly defined to encompass any device having one or more processing or logic elements (e.g., one or more micro-processor devices, one or more application specific integrated circuit (ASIC) devices, one or more field programmable gate arrays (FPGAs), or one or more digital signal processors (DSPs)). In this sense, the one or more processors may include any device configured to execute algorithms and/or instructions (e.g., program instructions stored in memory). In one embodiment, the one or more processors may be embodied as a desktop computer, mainframe computer system, workstation, image computer, parallel processor, networked computer, or any other computer system configured to execute a program configured to operate or operate in conjunction with the system  100 , as described throughout the present disclosure. Moreover, different subsystems of the system  100  may include a processor or logic elements suitable for carrying out at least a portion of the steps described in the present disclosure. Therefore, the above description should not be interpreted as a limitation on the embodiments of the present disclosure but merely as an illustration. 
     The memory  120  can be an example of tangible, computer-readable storage medium that provides storage functionality to store various data and/or program code associated with operation of the controller  112  and/or other components of the system  100 , such as software programs and/or code segments, or other data to instruct the controller and/or other components to perform the functionality described herein. Thus, the memory can store data, such as a program of instructions for operating the system  100  or other components. It should be noted that while a single memory  120  is described, a wide variety of types and combinations of memory  120  (e.g., tangible, non-transitory memory) can be employed. The memory can be integral with the controller, can comprise stand-alone memory, or can be a combination of both. Some examples of the memory  120  can include removable and non-removable memory components, such as random-access memory (RAM), read-only memory (ROM), flash memory (e.g., a secure digital (SD) memory card, a mini-SD memory card, and/or a micro-SD memory card), solid-state drive (SSD) memory, magnetic memory, optical memory, universal serial bus (USB) memory devices, hard disk memory, external memory, and so forth. 
     The communication interface  124  can be operatively configured to communicate with components of the controller  112  and other components of the system  100 . For example, the communication interface  124  can be configured to retrieve data from the controller  112  or other components, transmit data for storage in the memory  120 , retrieve data from storage in the memory  120 , and so forth. The communication interface  124  can also be communicatively coupled with controller  112  and/or system elements to facilitate data transfer between system components. 
       FIG.  3    is a flow diagram illustrating a method  300  for correlating a first item to a second item, in accordance with one or more embodiments of the disclosure. The first item and the second item may include the navigation chart and the FMS procedure, respectively, or may include any other first item or second item as detailed above. 
     In embodiments, the method  300  includes a step  310  of detecting the first identifier associated with the first item. For example, the first identifier may be configured as the name of a file. In another example, the first identifier may be configured as a title of a document, a digital object identifier (DOI), data from the citation of a document (e.g., issue number, volume number and/or page number), or any text within the document. (For instance, the first identifier may be one entry of a list of entries in a spreadsheet. A first item may be configured with two or more data pieces within the first identifier. For example, a digitized document may have two or more identifiers (e.g., a file name, and a title name) that together comprise the first identifier 
     In embodiments, the method  300  includes a step  320  of detecting a second identifier associated with the second item. The second identifier of the second item may include any data type as indicated for the first identifier of the first item, and vice versa. For example, the second identifier may be configured as a name that identifies a procedure file or the procedure itself. For instance, the second identifier may be configured to identify an FMS procedure. A second item may be configured with two or more data pieces within the second identifier. For example, a digitized document may have two or more identifiers (e.g., a file name, and a title name) that together comprise the second identifier 
     In some embodiments, the method  300  includes a step  330  of converting the first identifier into a first simplified identifier. Converting the first identifier into a first simplified identifier facilitates downstream matching with the second identifier. First identifier simplification may be performed off-line through software tools (e.g., as indicated in  FIG.  2   ), via one or more processors  116 , and involves the conversion of the first identifier into one or more data and/or data field types. For example, first identifier simplification may include detecting first identifier data and converting that the detected first identifier data into a Codex Value, configured as a bit field, and a Codex String, configured as a character string. Other data relating to the item type and item description/name may also be stored in memory  120 . Details for converting the first identifier into the first simplified identifier are detailed below. In some embodiments, step  330  is optional, or performed to a modest extent. For example, a system  100  (e.g., such as on-board an aircraft  212 ) may perform the matching process between the first identifier and the second identifier with no simplification. For instance, the first identifier may be simplified to begin with to a point where the system  100  can perform the matching process without requiring further simplification. Therefore, a first identifier may be configured as a first simplified identifier, and a first simplified identifier may be configured as a first identifier. 
     In some embodiments, the method  300  includes a step  340  of executing a matching procedure configured to match the first simplified identifier to the second identifier, in accordance with one or more embodiments of the disclosure. The matching procedure may be performed on the aircraft  212  at run-time, as shown in  FIG.  2   . For example, the one or more processors  116  of the system  100  located on the aircraft  212  may compare the first simplified identifier to the second identifier, and then generate a match value between the first identifier and the second identifier. The match value is an indicator of the amount of match between the first simplified identifier and the second simplifier, and is indicative of a probability that the second item is correlative to the first item. Details of the matching procedure are detailed below. 
     In some embodiments, the method  300  includes a step  350  of reporting the correlation of the first item to the second item based on the match value. Based on the number of potential or probable matches and the level of matching between the first simplified identifier and the second identifier, a determination is made on whether the most likely match is identified and reported, a list (e.g., a minimized list) of matches is identified and reported, or that an indication of no matching (e.g., no matching beyond a match threshold) is reported. For example, a pilot attempting to select a navigation chart a based on an FMS procedure may be presented via the output device  108  three navigation charts with match values that suggest a moderate to high probability that one of the three navigation charts is the correct chart. 
       FIG.  4    is a block diagram of a flow chart illustrating a method  400  for converting a first identifier into a first simplified identifier, in accordance with one or more embodiments of the disclosure. The method  400  may include the parsing of the first identifier into one or more data forms, or within one of more data fields. As described herein, a first identifier may already be simplified, or partially simplified, and may not require one or more steps of the method  400 . 
     In some embodiments, the method  400  includes a step  410  of generating a codex string configured as character string based on the first identifier. The codex string may contain moniker names, procedure names, geographical locations, runway numbers, or any other identifying information. The coded string may be configured as any type of data string. For example, the codex string may be defined with a form {N,N,LLL;M;M}, where “N” is defined as zero or more numbers separated by commas, “L” is defined as zero or more letters without separation, and “M” defined as a moniker string of up to four characters preceded by a semicolon. In this form, “N” may indicate specific runway numbers, “L” may indicate procedure variants, and “M” may indicate the names of the monikers represented by the chart. There may be more than one Moniker defined within a chart name. 
     In some embodiments, the method includes a step  420  of generating a codex value based on the first identifier. The codex value may be configured as a bit field comprising any number or range of bits. For example, the codex value may comprise bits in a range of 16 to 128 bits. In another example, the codex value may comprise bits in a range of 32 to 64 bits. For instance, the codex value may comprise approximately 32 bits. The codex value may include any type of information relating to the first item including but not limited to: type of equipment being used (e.g., Global Positioning System (GPS) equipment, or Instrument Landing System (ILS) equipment), runway positions (e.g., left, center, or right), page number of the chart, and whether the chart name is a “Guidance” type (e.g., such as a GPS chart), or a “Moniker” type (e.g., such as a BENKE7). A codex value chart  500  illustrating an example of a codex value is shown in  FIG.  5   , in accordance with one or more embodiments of the disclosure. 
     In embodiments, the method  400  includes a step  430  of removing nonessential letters. Nonessential letters may include any letters that are either not needed or redundant for correlating the first item for the second item. For example, a list of letters and words may be generated that may be removed from the first identifier. An example list  600  of letters and words to be removed from the first identifier is shown in  FIG.  6   . 
     In some embodiments, the method  400  includes at step  440  of setting one or more bits of the codex value based on the first identifier. For example, if the FMS chart is a ‘Guidance” chart type (e.g., the chart comprises approach chart, departure chart, arrival chart, or airport chart types, and at least one of the following key strings exist as either a word or a substring: ILS, LOC, GPS, TACAN, NDB, DME, VOR, RNP, GNSS, LDA, SDF), then the appropriate bit (e.g., bit zero in  FIG.  5   ) will be set along with the guidance type (e.g., bit  6  in  FIG.  5   ). In another example, bits for SID and STAR will be set (e.g., bit  28 - 29  in  FIG.  5   ) upon detection of the strings SID/SIDS and STAR, respectively. In another example, bits for X, Y, Z, R (right), C (center), and L (left) (e.g., bits  20 - 25  in  FIG.  5   , respectively) will be set depending if the first identifier contains number with letters immediately preceding the number. For instance, the designation  17 L in a first identifier will result in the setting of bit  25  in  FIG.  5   ). In another example, for strings within the first identifier that denote paging (e.g., PGn or CONTn, where n is a number) and set the continued bits as appropriate (e.g., bits  30 - 31  in  FIG.  5   ). In another example, detection of the words “high” or “Hi” in the first identifier will result in the setting of a bit for high airway (e.g., bit three in  FIG.  5   ). 
     In some embodiments, the method  400  includes a step  450  of adding one or more sub-strings of the first identifier to the codex string. For example, a first identifier than contains a number either written as a numeral (e.g., 7) or spelled out (e.g., seven) will be added to the codex string in a numeral form. In another example, non-codex value-relevant sub-strings are processed and added to the codex string. For instance, when parsing left to right, and a 2-letter sub-string is detected, the sub-string is a moniker if the string itself has not yet been determined to be a moniker (e.g., no un-reserved sub-string of more than two letter has been found to the left of the two-letter sub-string). If the string has already been determined to be a moniker, the 2-letter substring is a modifier for the moniker and is treated as the individual letters in the codex string. In a particular illustration, “BAYES_AB” indicates the “BAYES” moniker with procedures “A” and “B” while “SL_403_621_DEP” would be treated as a moniker since the two letters, “SL”, were processed before finding a moniker. This catches moniker place names that start with “EL”, “LA”, or “ST”. Any remaining moniker strings are added to the codex string, and if are remaining unprocessed strings, the moniker bit will be set in the codex value (e.g., bit  1  in  FIG.  5   ). A codex string may have both guidance and moniker characteristics. 
       FIG.  7    is a block diagram of a flow chart illustrating a method  700  for executing a matching procedure configured to match the first simplified identifier to the second identifier, in accordance with one or more embodiments of the disclosure. Once generated, the first simplified identifier provides a more straightforward approach for correlating the first item to the second than the non-simplified first identifier. 
     In some embodiments, the method  700  includes a step  710  of determining a second identifier type of the second identifier. For example, one or more characteristics of the second identifier may be used to determine the second identifier type, which then determines whether to perform a matching procedure, or which specific matching procedure is appropriate. For instance, if the second identifier is identified as a guidance procedure, then a procedure specific for matching a guidance procedure to the first simplified identifier will be performed. In another instance, if the second identifier is identified as a moniker, then a procedure specific for matching a moniker to the first simplified identifier will be performed. In a particular illustration, an FMS procedure (e.g., the second identifier) will be identified as a guidance procedure if the second procedure contains any of the following: a letter followed by two numbers, and/or a combination of numbers that includes “TTAC”, “EVOR”, “SVOR: “FNDB”, and/or “GGPS”. If a procedure is not a guidance procedure, then it is a moniker. 
     In embodiments, the method  700  includes a step  720  of comparing bits in the codex value and values in the codex string to the second identifier. For example, utilizing the one or more processors  110 , the system  100  may compare an FMS procedure (e.g., or an FMS International Civil Aviation (ICAO) procedure, or an FMS procedure type, and match it to a chart name (e.g., the first simplified identifier). For instance, a procedure will only match to a chart if both the procedure and the chart are of the same type (e.g., guidance or moniker) and include the same airport. 
     In embodiments, the method includes a step  730  of generating a match value based on the comparison between the first simplified identifier and the second identifier. The match value may be any parametric or nonparametric value system that facilitates the grading or placement of a comparison between the first simplified identifier and the second identifier. Once generated, the match value may be used to determine which comparisons, and therefore which first item may be reported as a potential match. The values or levels within the match value may include known value systems. For example, the match values may include and exact match, a close match, a possible match, and no match. 
     The following description details an example set of rules for generating match values between a first simplified identifier (e.g., a processed chart name) and a second identifier (e.g., a procedure name, such as an FMS procedure name). The rules differ slightly between guidance-related matching and moniker-related matching. In general, guidance matching follows a set of rules which takes the first letter of the FMS procedure name (or possibly a specific embedded string within the FMS procedure name) and matches it to a guidance type bit in the codex value. Additional matching is done against positional type information (left right, center, and others), runway IDs, version of chart (X, Y, Z for FAA charts but random other letters for some foreign charts), and other information. Moniker matching is performed as a comparison between the procedure string (e.g., the FMS procedure name) and the moniker sub-strings stored in the codex string. Additional matching is done with version numbers, version of procedure letters, and other information. 
     For example, an exact match between a chart name and a guidance procedure name is determined when 1) the guidance bit in the codex value is set, 2) an FMS embedded runway identification (ID) number matches a runway ID in the codex string, 3) there is a match on the first letter of the procedure name to the associated codex value bit (e.g., see  FIG.  8   ), and 4) no additional letters are found in the procedure name or additional procedure name letters are found in the codex string or there is a match between additional letter in the FMS procedure name and the codex value bit (e.g., see chart  800  in  FIG.  8   ). 
     In another example, a close match between a chart name and a guidance procedure name is determined when the first three conditions of the exact match criteria are met, but not the fourth criteria, or 1) the guidance bit in the codex value is set, 2) the FMS embedded runway ID number matches a runway ID in the codex string, and 3) there is a match on the first letter of the procedure name associated codex values “G” and “R” (e.g., codex bits for GPS and required navigation performance (RNP)) as shown in  FIG.  8   . 
     In another example, a possible match between a chart name and a guidance procedure name is determined when 1) there is a single chart at the ICAO that matches the FMS procedure name (e.g., guidance chart type), 2) the FMS procedure type is “departure” and the SID bit is set in the codex value and the FMS runway ID is found in the codex string, or 3) the FMS procedure type is “arrival” and the STAR bit is set in the codex value, and the FMS runway ID is found in the codex string. 
     In another example, an exact match between a chart name and a moniker procedure name is determined when 1), the moniker bit in the codex string is set, 2) the first characters of the FMS procedure name match the first characters of a moniker sub-string in the codex string, 3) either a) no numbers exist in the FMS procedure name or b) a number in the FMS procedure name matches a number in the codex string, or c) a number exists in the FMS procedure name and no numbers exist in the codex string, and 4) either if the FMS procedure name has an additional associated letter, the codex string also has the same additional associated letter or an equivalent bit set in the codex value if the letter is “X”, “Y”, or “Z”. 
     In another example, a close match between a chart name and a moniker procedure name is determined when the moniker bit in the codex value is set and 1) the first characters of the FMS procedure name match the first characters of a moniker in the codex string, 2) two characters in the FMS procedure name match two characters in a moniker in the codex string and there is a number in the FMS procedure name that matches an associated number in the codex string, 3) the FMS procedure type is “departure” and the FMS runway ID exists in the codex string and the SID bit is set in the codex value, or 4) the FMS procedure type is “arrival” and the FMS runway ID exists in the codex string and the STAR bit is set in the codex value. 
     In another example, a possible match between a chart name and a moniker procedure name is determined when 1) the FMS procedure type is “departure” and the FMS runway ID does not exist in the codex string and the SID bit is set in the codex value, 2) the FMS procedure type is “arrival” and the FMS runway ID does not exist in the codex string and the STAR bit is set in the codex value, 3) a number exists in the FMS procedure name, no numbers in the codex string, and at least two letter can be matched, in order, between the FMS procedure name and a moniker sub-string in the codex string, or 4) there is a single chart of the FMS procedure type for the ICAO. 
     In some embodiments, the second identifier is configured as a second simplified identifier. For example, the second identifier may be converted similarly to that of the first identifier such that the converted, or simplified, second identifier is configured with a second codex value and a second codex string. Once converted, the second identifier, now simplified, may be matched with the first simplified identifier, and a match value calculated. 
     It is to be understood that embodiments of the methods disclosed herein may include one or more of the steps described herein. Further, such steps may be carried out in any desired order and two or more of the steps may be carried out simultaneously with one another. Two or more of the steps disclosed herein may be combined in a single step, and in some embodiments, one or more of the steps may be carried out as two or more sub-steps. Further, other steps or sub-steps may be carried in addition to, or as substitutes to one or more of the steps disclosed herein. 
     Although inventive concepts have been described with reference to the embodiments illustrated in the attached drawing figures, equivalents may be employed and substitutions made herein without departing from the scope of the claims. Components illustrated and described herein are merely examples of a system/device and components that may be used to implement embodiments of the inventive concepts and may be replaced with other devices and components without departing from the scope of the claims. Furthermore, any dimensions, degrees, and/or numerical ranges provided herein are to be understood as non-limiting examples unless otherwise specified in the claims.