Method and system for monitoring vehicle components

Abstract

A method for monitoring a state of one or more components of a vehicle is provided. The method includes: retrieving one or more known identifiers associated with each of one or more components of the vehicle; retrieving one or more requirements regarding one or more physical conditions and / or one or more regulations associated with each of the identifiers; retrieving historical data regarding one or more physical conditions and / or one or more regulations associated with each of the identifiers; and aggregating the requirements and historical data by parts based on known identifiers to form one or more aggregated historical data sets, where each of the one or more aggregated historical data sets has historical data associated with one of the one or more parts of the vehicle; and determining whether each of the components satisfies a requirement associated with each of the components based on one or more aggregated historical data sets associated with each of the components. A corresponding system for performing the method is also provided.

Description

Technical Field

[0001] This invention relates to components of a monitoring vehicle, assemblies of a monitoring vehicle, and / or the vehicle itself. The invention particularly, but not exclusively, relates to monitoring components of an aircraft, assemblies of an aircraft, and / or the aircraft itself in relation to various requirements such as those concerning physical conditions and / or relevant regulations. Background Technology

[0002] Maintaining aircraft components in satisfactory physical condition is crucial for ensuring aircraft airworthiness and the safety of passengers and crew. However, despite the importance of aircraft component maintenance, it is prone to errors due to unreliable maintenance practices that have been used in the past.

[0003] In particular, given the ever-increasing number of aircraft operating globally, accurately monitoring whether aircraft components meet the requirements for safe aircraft operation is becoming increasingly challenging. This could lead to aircraft operators being unaware of their aircraft's lack of airworthiness, potentially resulting in catastrophic consequences. Furthermore, in some cases, aircraft operators may be forced to outsource unnecessary and repetitive maintenance work due to a lack of awareness of early maintenance procedures performed on the same aircraft components.

[0004] Therefore, methods and systems that enable aircraft operators to reliably monitor historical data associated with aircraft components are desirable. Summary of the Invention

[0005] This invention is defined by the independent claims, which are hereby referred to. Preferred features are set forth in the dependent claims.

[0006] In a first aspect of the invention, a method for monitoring the state of one or more components of a vehicle is provided. The method includes: retrieving one or more known identifiers associated with each of the one or more components of the vehicle; retrieving one or more requirements regarding one or more physical conditions and / or one or more regulations associated with each of the identifiers; retrieving historical data regarding one or more physical conditions and / or one or more regulations associated with each of the identifiers; and aggregating these requirements and historical data by component based on the known identifiers to form one or more aggregated historical datasets, wherein each of the one or more aggregated historical datasets has historical data associated with one of the one or more components of the vehicle; and determining whether each component meets the requirements associated with each component based on the one or more aggregated historical datasets associated with each component.

[0007] Optionally, the method may further include: if it is determined that at least one component in the components currently does not meet one or more requirements associated with at least one component in the components, generating a notification indicating that at least one component in the components does not meet one or more requirements.

[0008] Optionally, the method may further include: if it is determined that at least one of the components is expected to no longer meet one or more requirements associated with at least one of the components within a predetermined time period, generating a notification indicating that at least one of the components is expected to fail to meet one or more requirements.

[0009] Optionally, the notification may include one or more identifiers of at least one component in the components, wherein at least one component in the components does not meet or is expected to not meet one or more requirements associated with at least one component in the components.

[0010] Optionally, the requirements may include one or more certifications that one or more organizations performing the manufacture, distribution, inspection, maintenance and / or repair of the corresponding component must hold in the course of performing the manufacture, distribution, inspection, maintenance and / or repair.

[0011] Optionally, the requirements may include one or more parameters related to one or more physical conditions, lifespan, and / or predetermined cycles of inspection, maintenance, and / or repair of the corresponding component.

[0012] Optionally, the requirements may include one or more parameters related to one or more of the inspections, maintenance and / or repairs that need to be performed in response to one or more events affecting the physical condition of the corresponding component.

[0013] Optionally, one or more events affecting the physical condition may be one or more of the following: reported failures, defects and / or malfunctions of the corresponding component, and accidents that may cause failures, defects and / or malfunctions of the corresponding component.

[0014] Optionally, historical data may include data related to the time when one or more of the manufacturing, distribution, inspection, maintenance and / or repair of the corresponding component were performed.

[0015] Optionally, historical data may include data related to one or more certifications held by an organization that performs one or more of the manufacturing, distribution, inspection, maintenance and / or repair of the corresponding component.

[0016] Optionally, the data associated with each certification may include: the name of the organization that issued the corresponding certification, the name of the entity that issued the corresponding certification, the period during which the corresponding certification is valid, and details relating to one or more of the manufacturing, distribution, inspection, maintenance and / or repair that the organization is certified to perform on the corresponding component.

[0017] Optionally, historical data may include detailed information related to past transactions of the corresponding component.

[0018] Alternatively, a new unique identifier may be assigned to each group of aggregate identifiers, each group of aggregate identifiers consisting of identifiers associated with the same component.

[0019] Optionally, the one or more known identifiers may include identifiers issued and / or used by one or more of the following: manufacturers, operators, and organizations responsible for the manufacture, distribution, inspection, maintenance, and / or repair of the corresponding components.

[0020] Optionally, the method may further include sending the notification to one or more of the following: the owner of the vehicle, the operator of the vehicle, and / or one or more organizations responsible for the manufacture, distribution, inspection, maintenance and / or repair of the corresponding component.

[0021] Optionally, one or more certifications can be retrieved from a database. Optionally, the database can be configured to allow one or more organizations to upload, modify, and / or delete one of the multiple certifications held by those organizations.

[0022] Optionally, the method may further include: if it is determined that all requirements of all components of the assembly are currently met, issuing a certificate confirming that the assembly is suitable for operation, wherein the assembly is part of the vehicle and includes all components of the assembly.

[0023] Optionally, the method may further include: issuing a certificate confirming that the vehicle is suitable for operation if it is determined that all requirements for all components of the vehicle are currently met.

[0024] Alternatively, the vehicle may be an aircraft.

[0025] Optionally, the method may further include: issuing a certificate confirming the airworthiness of the aircraft if it is determined that all requirements for all components of the assembly are currently met, wherein the assembly is part of the aircraft and includes all components of the assembly.

[0026] Optionally, the method may further include issuing a certificate confirming the airworthiness of the aircraft if it is determined that all requirements for all components of the aircraft are currently met.

[0027] Optionally, the method may further include generating an alert indicating that the aircraft or assembly is unairworthy if it is determined that one or more basic components of the aircraft or the aircraft assembly does not meet or is expected to fail to meet one or more basic requirements associated with the basic components. The one or more basic components and the one or more basic requirements may be determined based on one or more inputs from one or more users associated with: the owner of the aircraft, the assembly, and / or the corresponding basic components; the operator of the aircraft; and / or one or more organizations responsible for the manufacture, distribution, inspection, maintenance, and / or repair of the aircraft, the assembly, and / or the corresponding basic components.

[0028] Optionally, the alarm may include one or more identifiers of one or more basic components that do not meet or are expected to fail to meet one or more basic requirements within a predetermined time.

[0029] In a second aspect of the invention, a system for monitoring the state of one or more components of a vehicle is provided. The system includes a data storage device and a processor, the data storage device including a computer program stored thereon. The processor is configured to run the computer program. The computer program is configured to perform a method for monitoring the state of one or more components according to a first aspect of the invention. Attached Figure Description

[0030] Embodiments of the invention will now be described by way of example only with reference to the accompanying drawings, in which: Figure 1 The illustration depicts an exemplary system for monitoring the status of one or more components of a vehicle, according to an embodiment. Figure 2 An exemplary authentication ledger according to an embodiment is illustrated; Figure 3 The illustration shows an exemplary front-end page of the authentication ledger website interface according to an embodiment; Figure 4 The illustration shows an exemplary use of the authentication ledger according to an embodiment; Figure 5 The illustration depicts an exemplary process for creating user accounts and approving company claims on an authentication ledger, according to an embodiment. Figure 6 The illustration depicts an exemplary process of adding certifications to a certification ledger according to an embodiment, wherein the user's organization has certifications mentioned by the organization's public website and listed in the certification ledger; Figure 7 The illustration depicts an exemplary process of adding an authentication to an authentication ledger according to an embodiment, wherein the user's organization does not have any authentications mentioned by the organization's public website and listed in the authentication ledger; Figure 8The illustration depicts an exemplary process for managing anomalies on the authentication ledger according to an embodiment; Figure 9 An exemplary UIN aggregation table according to an embodiment is illustrated; Figure 10 An exemplary UIN aggregation process according to an embodiment is illustrated; Figure 11 The illustration shows an exemplary reconciliation between the parts ledger and other modules of the system according to an embodiment; Figure 12 The illustration shows an exemplary process for synchronizing a parts ledger with other ledgers according to an embodiment; Figure 13 The illustration depicts an exemplary process for associating a maintenance organization's certification with a parts register according to an embodiment; Figure 14 An exemplary passport tree according to an embodiment is illustrated; and Figure 15 An exemplary process for a back-to-birth verifier scan according to an embodiment is illustrated. Detailed Implementation

[0031] The following exemplary description is based on systems and methods used in the aviation industry. However, it should be understood that the invention can be applied outside the aviation industry and in any industry (such as other tourism or logistics industries) where vehicle components need to comply with certain requirements set by relevant organizations (such as governments and regulatory agencies) in relation to physical conditions and / or regulations. Therefore, embodiments of the invention are generally applicable to the tourism and transportation industries, such as rail, bus, automobile, ship, and delivery and courier services.

[0032] As used herein, the term "vehicle" refers to equipment designed for the transport of people or goods. Therefore, vehicles include, but are not limited to: trucks, bicycles, motor vehicles (motorcycles, cars, trucks, buses, electric mobility scooters for the disabled), rail vehicles (trains, trams), water vehicles (ships, boats, underwater vehicles), amphibious vehicles (propeller-driven vehicles, hovercraft), aircraft (airplanes, helicopters, airships), and spacecraft.

[0033] For the purposes of the following discussion, the terms "component" and "part" may be used interchangeably.

[0034] The following text is about Figures 1 to 15Methods and systems for monitoring the status of one or more components of a vehicle, such as an aircraft, according to the present invention, and embodiments of systems for performing said methods are described. While the methods and systems described below include authentication ledgers, UIN aggregators, parts ledgers, and one or more applications associated with them, it should be understood that in other embodiments, the methods and systems may be implemented in other ways. For example, authentication ledgers, UIN aggregators, and parts ledgers may be implemented using integrated databases, and / or via one or more remote systems based on cloud and / or blockchain technologies. Similarly, one or more applications associated with authentication ledgers, UIN aggregators, and parts ledgers may run on any suitable form and number of processing devices.

[0035] Figure 1 An exemplary system for monitoring the status of one or more components of a vehicle is illustrated. Figure 1 The exemplary system shown includes interconnected software modules as illustrated. However, it should be understood that... Figure 1 The system described herein is provided as an example only, and in other embodiments, the system may be implemented in any other suitable form. This status may include airworthiness and / or regulatory compliance. To monitor the status of one or more components of a vehicle, the system may retrieve a list of multiple components of the vehicle. Such a list may be created by receiving one or more inputs from one or more users. For example, one or more of these components may be entered into the list based on one or more data inputs from the vehicle owner, the vehicle operator, and / or one or more organizations responsible for manufacturing, distributing, inspecting, maintaining, and / or repairing the vehicle. Alternatively, such a list may be imported from other sources such as third-party databases. Components entered into such a list may take the form of identifiers such as UINs, original part information, and / or other identifiers such as part numbers, serial numbers, and manufacturer numbers (e.g., cage codes), part numbers (PNRs), and serial numbers (SERs).

[0036] Regarding maintenance that can be performed on parts, assemblies, and / or vehicles, maintenance can be performed based on ratings and scopes of work. Ratings may define which parts and / or assemblies (e.g., engines, auxiliary power units, landing gear) a party is permitted to perform maintenance on. Scopes of work may define which vehicle types (e.g., A320, B787) a party is permitted to perform maintenance on. Scopes of work may optionally be defined using ATA sections (also known as “ATA 100 system codes”).

[0037] Similarly, one or more requirements regarding one or more physical conditions and / or one or more regulations associated with each of these components can also be retrieved by receiving one or more inputs from one or more users and / or by importing from other sources as described above. Such requirements may include requirements related to certifications and qualifications that one or more organizations are required to possess. For example, one or more of these requirements may specify that one or more organizations performing the manufacture, distribution, inspection, and / or maintenance of one or more of these components need to possess one or more certifications and / or qualifications that are valid when performing the manufacture, distribution, inspection, and / or maintenance of these corresponding components.

[0038] Alternatively, one or more of these requirements may specify one or more parameters relating to one or more physical conditions, lifespan, and / or predetermined cycles of inspection, maintenance, and / or repair of the corresponding parts. Additionally, such parameters may indicate whether the corresponding part is on a wing (i.e., mounted on a vehicle (e.g., an aircraft)) or on a shelf (i.e., in storage).

[0039] Alternatively, one or more of these requirements may specify one or more parameters relating to one or more of the inspections, maintenance, and / or repairs that need to be performed in response to one or more events affecting the physical condition of these corresponding components. One or more events affecting the physical condition may be one or more of the following: reported failures, defects, and / or malfunctions of the corresponding components, and accidents that may cause such failures, defects, and / or malfunctions of the corresponding components.

[0040] exist Figure 1 In the example shown, the system includes a certification ledger containing data related to such certifications and / or qualifications. This certification ledger can be a centralized database storing the certification and / or qualification history of one or more organizations responsible for the manufacture, distribution, inspection, and / or maintenance of the corresponding parts. The certification ledger can be accessed via an application with a website or application interface.

[0041] Figure 2 An exemplary authentication ledger according to an embodiment is illustrated. Figure 2As shown, organizations such as manufacturers (OEMs), airlines, maintenance organizations, repair shops, distributors, and / or suppliers can access the certification ledger via a website or application interface. Organizations can then browse data in the certification ledger and register to create and / or update their organizational profiles. They can also upload and / or update certification and / or scope of work details. The certification ledger can also allow organizations and / or other parties (e.g., vehicle operators and / or owners) to subscribe to it, enabling subscribers to perform searches within the ledger, retrieve statistics based on data stored on the ledger, and receive notifications from the ledger (e.g., notifications of new entries, deletions, expirations, and / or changes to all or specific organizations, parts, and / or vehicles). Figure 3 The illustration shows an example website interface front-end page for the authentication ledger.

[0042] Optionally, users of the authentication ledger can be granted different access levels to the authentication ledger. For example, such as Figure 1 As shown, unregistered users (free access) may only be allowed to browse and read basic information in the authentication ledger, and only registered company users can perform further tasks such as uploading authentications and work scopes.

[0043] Table 1. Examples of features provided to users with different access levels

[0044] Therefore, an authentication ledger can provide a means of collecting and verifying an organization’s historical authentication information based on input from one or more users, and reduce the risk of parts segregation.

[0045] Figure 4 The illustration depicts an exemplary use of the authentication ledger according to an embodiment. For example... Figure 4 As shown, the certification ledger allows anyone browsing the internet to access the ledger and read basic information without registration (free access 402). The certification ledger may have a website or application interface through which users can view visual basic information about the listed companies (e.g., company name, logo, basic business information, and a list of available certifications). The certification ledger interface may require users to register and / or pay to allow access to further features and information.

[0046] like Figure 4As shown, users can first register by creating an account on the authentication ledger interface 406. The account creation process can begin when the user submits a registration request 408. The account creation process may include automated email verification 410. If the user's email is verified, the user's registration request is approved, and the user completes registration 412. If the user's email is not verified or fails verification, an account may not be granted to the user 411.

[0047] Figure 5 The illustration depicts an exemplary process for user account creation and company claim approval on an authentication ledger application according to an embodiment. The authentication ledger application can access authentication ledgers associated with vehicle components, which may be stored in a data storage device. The authentication ledger application may run on one or more processors included in and / or communicatively connected to the system. Optionally, such processors may be shared with other parts of the system, such as the UIN aggregator and parts ledger application described below. Interaction between the application and the user may be performed via a website and / or application interface. After registration, the user can view further information available only to registered users. Furthermore, as... Figure 4 and Figure 5 As shown, registered users can search for and claim one or more organizations associated with them (414, 430) in the authentication ledger. Scenario 1 below describes an example process of a registered user claiming an organization already listed in the authentication ledger.

[0048] Scenario 1 - The user's organization is already listed on the authentication ledger application. 1. User searches for the organization to claim: The user searches for the organization to claim (if the organization is listed).

[0049] 2. User Submits Organization Claim: After registration, users initiate the process by submitting a claim (430) of an organization (e.g., a distributor / supplier, maintenance organization, and / or OEM / manufacturer) related to the business of vehicle (e.g., aircraft) parts and components. This claim indicates that the user wishes to manage the organization's information and upload relevant certifications.

[0050] 3. Verify User-Organization Association: The authentication ledger application has automated methods for initial verification to check if a user can be associated with a specific organization. This automated verification can be performed by any suitable application and / or computer program provided and / or operated by the administrator. Figure 4In the example shown, the administrator is SITA. However, in other embodiments, the administrator can be any party responsible for providing and / or operating the authentication ledger and / or one or more systems that include the authentication ledger. If the automated method cannot verify a user's affiliation, a request is forwarded to the administrator for manual verification of the user's affiliation with the claimed organization. This manual process may request additional documentation and / or directly contact the organization to confirm the user's affiliation and / or authorization to manage the organization's information.

[0051] 4. Approval or Rejection of Claim: If the initial verification conducted via automated methods is accepted, the user can manage company information. If the initial verification conducted via automated methods is not accepted, the claim is forwarded to the system administrator. Based on available information and / or additional information requests from the administrator, the administrator of the authentication ledger application can decide 440 to approve or reject the user's claim. If approved, the user is granted access to manage 460 the organization's information and upload relevant authentications. If rejected, the user is notified 450 of the decision. The notified decision may include an explanation of the rejection.

[0052] 5. Notify users: Regardless of the decision, notify users of the status of their claim via email or in the certification ledger application. If approved, the notification includes instructions on how to continue managing organizational information and uploading certifications. If rejected, the notification provides the reason for the rejection and any further steps that may be necessary.

[0053] 6. Continuous review and adjustment: such as Figure 5 As shown, the certification ledger application can continue to monitor and adjust the activities of claimed organizations and users on a regular basis. Other users can report erroneous information, and administrators can periodically review uploaded certification and organizational information to ensure accuracy and compliance with certification requirements. Furthermore, the certification ledger application can periodically verify whether the organization remains on the lists of relevant certification bodies such as the FAA, EASA, and ASA.

[0054] If one or more organizations associated with a user are not listed in the authentication ledger 420, the user can submit information about one or more organizations to register them in the authentication ledger 422. Scenario 2 below describes an example process for a registered user to claim an organization not listed in the authentication ledger.

[0055] Scenario 2 - The company is not listed on the authentication ledger application. 1. User reports to administrator (e.g., SITA): The user reports to SITA that the organization is missing from the repository that provides organization information.

[0056] 2. Administrator approval request: a. If approved, the SITA administrator will add the organization to the central database of the certification ledger application, and the user must follow the steps listed above in Scenario 1 in this section.

[0057] b. If not approved, the SITA administrator responds to the user's request (optionally providing a reason for rejection), and the user will be unable to claim the organization.

[0058] By following this user organization claiming and approval process, the certified ledger repository system can ensure that only authorized individuals can manage and update the information of certified organizations and maintain the integrity and reliability of the certified ledger repository data.

[0059] Figure 6 The illustration depicts an exemplary process for adding a certification to a certification ledger according to an embodiment. The process of adding a certification to a company profile may vary depending on whether the certification ledger has already identified the company as having one or more certifications mentioned and listed in the certification ledger by the public websites of one or more relevant organizations. Scenario 3 below describes an exemplary process for adding a certification to a certification ledger where the user's organization already has certifications mentioned and listed in the certification ledger by an organization's public website.

[0060] Scenario 3: The user's organization already has certifications mentioned on the organization's public website and listed in the certification ledger. 1. Access to Organization Profile: After account claim is approved and the user is granted permission to access their organization profile management interface, the user can navigate to the authentication-only section.

[0061] 2. Uploading Certification: In this scenario, since the organization has already been identified as having a specific certification (e.g., ASA-100, EASA, or FAA Part 145), users can provide additional details and upload a digital version of the certification. This can be done, for example, by selecting the "Add Certification" option on the specific certification and following the instructions to upload the digital certification file or entering the relevant information.

[0062] Scenario 4 below describes an exemplary process for adding certifications to the certification ledger, where the user's organization does not have any certifications mentioned by the organization's public website and listed in the certification ledger.

[0063] Scenario 4: The user's organization does not have certifications mentioned on the organization's public website and listed in the certification ledger. 1. Accessing the Organization Profile: Similar to Scenario 3, after account claiming is approved and the user is granted permission to access their organization profile management interface, the user can navigate to the authentication-only section.

[0064] 2. Upload Certification: In this case, the company does not have any certifications listed in the "Certifications" section. Therefore, users can use the "Upload New Certification" function and follow the instructions to upload the digital file of the certification or enter the relevant information.

[0065] 3. Review and Approval: After submitting an authentication request, the application may undergo a review and approval process. This may involve manual verification or validation by an administrator or relevant authority. Users can be notified of the status of their authentication request.

[0066] 4. Upload Authentication: After the authentication request is approved, the user will receive instructions on how to add authentication. The user can then upload the authentication to the company profile following the steps outlined in Scenario 3.

[0067] Figure 8 The illustration depicts an exemplary process for managing anomalies in an authentication ledger according to an embodiment. Detecting and managing anomalies and error messages in company profiles and their authentication within an application is crucial to ensuring user trust in the accuracy, reliability, and reliability of the authentication ledger. Scenario 5 below describes an exemplary process for detecting and managing anomalies.

[0068] Scenario 5: Anomaly Detection and Management 1. User Reporting: The user reporting mechanism allows users to flag any anomalies or incorrect information they encounter. This can be achieved by providing a dedicated report button or form within the authentication ledger interface. Users can be encouraged to provide specific details about the anomaly, such as errors in the company profile, the nature of the problem, and any supporting evidence or documentation.

[0069] 2. Application Monitoring and Auditing: Robust monitoring and auditing mechanisms can be employed to detect anomalies and identify potential errors. This may involve automated checks and algorithms for analyzing data consistency, cross-validating information, and identifying outliers or discrepancies. Regular system audits can help identify and correct any inaccuracies or anomalies that may have been missed.

[0070] 3. Verification and Validation Process: A comprehensive verification and validation process can be employed for the information displayed in the company profile and certifications. This may involve manual review by authorized personnel or agencies to ensure the accuracy and legality of the information provided. Regular checks and verifications can be conducted to address any potential errors or discrepancies.

[0071] 4. Organization Verification: Certifications can be verified through relevant organizations, regulatory bodies, or certification issuers to ensure the accuracy of information and the proper validation of the certification. Verification algorithms can be established to link these entities to a list of organizations, enabling timely reporting and correction of any inaccuracies. Regular updates from organizations help maintain the integrity of the data within the system.

[0072] 5. Timely Correction and Updates: Once abnormal or incorrect information is identified, swift action can be taken to correct and update the relevant data. This may involve removing or modifying inaccurate information, verifying and re-verifying authentication, and ensuring that the corrected data is accurately reflected in the system.

[0073] 6. Communication and Transparency: Maintaining open communication channels with users and stakeholders to address their concerns and providing updates on actions taken to correct anomalies or misinformation. Communicating any changes, fixes, or updates made to the system to enhance trust and confidence among users.

[0074] Therefore, certification ledgers and certification ledger applications make it easy to trace and verify the historical certifications and qualifications of organizations such as maintenance organizations, maintenance personnel, suppliers, and / or distributors. In other words, certification ledgers can serve as a trusted source to prove that, in past repairs, the organization responsible for handling the repairs (maintenance organization) was authorized, certified, and / or accredited to perform the repairs, and the personnel performing the repairs were authorized and / or certified to perform the repairs.

[0075] Furthermore, since the certification ledger can also contain information related to the certification of suppliers and / or distributors, it can also serve as a credible source for verifying that an organization selling and / or distributing parts is certified to sell and / or distribute them.

[0076] Given the regulations requiring such organizations to possess appropriate certifications and qualifications, and the fact that such certifications and qualifications may have set validity periods and expiration dates, the data in the certification ledger can thus be used not only to determine the condition of one or more components of a vehicle, but also to determine the condition of the vehicle as a whole. This can be particularly useful when the vehicle is an aircraft, because if the owner of an aircraft part cannot prove that the aforementioned regulatory requirements have been met, the aircraft part cannot be considered airworthy or sold.

[0077] As mentioned above, an authentication ledger enables the retrieval of information and / or authentication history from one or more organizations. However, different organizations may have their own preferred systems for identifying vehicle components, and therefore, the way relevant parties refer to vehicle components may differ. This can result in multiple identifiers being associated with the same component of the vehicle, which can be a problem for systems such as authentication ledgers.

[0078] To address this issue, a Unique Identifier (UIN) aggregator can be provided. It should be understood that although the term "unique identifier" is used, a UIN can consist of more than just a combination of numbers and can include other elements such as letters, characters, and / or symbols. Furthermore, while the following discussion provides examples using one or more UINs, it should be understood that the following teachings still apply even when using one or more other types of unique identifiers. Figure 9 As shown, the UIN aggregator can identify components as they flow across owners, service providers, applications, and platforms, and aggregate all existing UINs 904 and 906, assigning the aggregated UIN set to the corresponding component. For example, one or more UINs 904 and 906 of the same component can be aggregated into a table structure, such as... Figure 9 The exemplary UIN aggregation table shown includes one or more third-party 904, 906, and the resulting table can be assigned to parts. Existing UINs included in the aggregated UIN set can be one or more of the following: existing third-party UINs 906, original part information and / or identifiers 904, such as part number, serial number and manufacturer number (e.g., cage code), part number (PNR), serial number (SER). New UINs (e.g., Figure 9 The SITA UIN 902 shown can be created and assigned to the UIN set of an aggregate to facilitate identification of the aggregate's UIN set. In this case, the aggregate's UIN set can be referred to by using the new UIN 902. When the table structure is used for aggregation, this new UIN 902 can be added to the table structure.

[0079] Figure 10 An exemplary UIN aggregator process is shown. Figure 10 As shown, the UIN aggregator can first check if a UIN 902 already exists for a part created by the UIN aggregator or administrator. For the purposes of the following discussion, this UIN 902 will be referred to as "SITA UIN". If the part's SITA UIN 902 already exists, the UIN aggregator may not create a new UIN 902. If the part does not have an existing SITA UIN 902, the UIN aggregator may create a new SITA UIN 902.

[0080] After creating SITA UIN 902, the aggregator can assign all known existing part data points 904 and 906 to SITA UIN 1006. Part data points can include one or more of the following: existing UIN (e.g., third-party UIN) 906, original part information and / or identifiers 904, such as part number, serial number and manufacturer number (e.g., cage code), part number (PNR), serial number (SER).

[0081] SITA UIN 902 can be assigned to the parts register 1008, which is referenced below. Figure 11 and Figure 12 To elaborate further, the aggregated UIN set, including SITA UIN, is stored on the UIN aggregator. Therefore, the UIN aggregator can act as a centralized UIN repository for the components of a vehicle.

[0082] The parts ledger can monitor the UIN (User ID) throughout the entire lifecycle of a component, which may include multiple stages such as manufacturing, distribution, installation, maintenance, and decommissioning. The parts ledger can also monitor the existence of newly identified UINs and / or the emergence of any new UINs throughout the component's lifecycle.

[0083] Creating SITA UIN 902 to identify serialized vehicle components (e.g., aircraft parts) offers several advantages, such as: • Uniqueness: Each serialized part of the vehicle is assigned a unique UIN (“SITA UIN”) 902, ensuring that no two parts have the same identifier. This uniqueness helps eliminate cost and time losses caused by management chaos or errors related to identifying and tracking specific parts, especially in complex supply chains or maintenance operations.

[0084] • Traceability: SITA UIN allows for precise and accurate traceability of serialized parts throughout their entire lifecycle. It enables stakeholders to track parts from their manufacturing origin to installation, maintenance, repair, and decommissioning. This traceability is critical for quality control, regulatory compliance, and safety purposes.

[0085] • Improved Inventory Management: SITA UIN facilitates efficient inventory management by providing a unique identifier for each part. It enables organizations to track part quantity, location, and usage, aiding in inventory replenishment, inventory turnover, and maintenance or replacement planning.

[0086] • Enhanced Maintenance and Repair: SITA UIN enables comprehensive tracking of maintenance and repair activities for serialized parts. It helps maintenance teams and technicians quickly access relevant part information, such as repair history, service bulletins, or specific maintenance requirements, ensuring accurate and timely part repair. It also facilitates system integration for information exchange.

[0087] • Anti-counterfeiting: SITA UINs help combat the use of counterfeit or unauthorized parts. By verifying the authenticity of SITA UINs against certified ledgers or databases, organizations can verify that parts come from a trusted source and have not been tampered with or illegally copied.

[0088] • Data Analysis and Decision Making: SITA UIN generates a wealth of data that can be used for analysis and decision-making purposes. By analyzing UIN-related data, organizations can gain deep insights into part performance, maintenance trends, failure rates, and other key factors. This information helps optimize maintenance schedules, proactively identify potential problems, and improve operational efficiency.

[0089] Therefore, SITA UIN can bring improvements to parts identification, traceability, maintenance, and decision-making in relevant fields, such as the aviation industry. Particularly in the aviation industry, this will enhance airworthiness and safety.

[0090] Regarding the aforementioned certification ledger, the UIN aggregator allows the consolidation of requirements, historical transactions, and data associated with the same component but with different identifiers (e.g., data related to one or more physical conditions and / or one or more regulations). In other words, the UIN aggregator enables the aggregation of requirements, historical transactions, and data by component based on known identifiers.

[0091] The authentication ledger and UIN aggregator can be implemented in any suitable form, such as modules including a database and a processor for running the corresponding application. The authentication ledger and UIN aggregator can communicate with each other and with one or more other parts of the system. Figure 1 and Figure 11 In the example shown, the authentication ledger and the UIN aggregator are connected via the parts ledger.

[0092] The purpose of a parts ledger can be to provide a standardized way to continuously collect, store, and display an immutable history of information events related to basic vehicle components (e.g., aircraft parts) throughout their lifecycle. To this end, a parts ledger can act as a comprehensive information store, containing detailed information such as part number, serial number, manufacturer code, manufacturing date, and other relevant information. A parts ledger can also include data related to the installation of the component within a vehicle (e.g., an aircraft), as well as any parameters that may affect its lifecycle.

[0093] Figure 12 An exemplary process for synchronizing the parts ledger with other ledgers is shown. Figure 12 In the example shown, firstly, the parts authentication ledger application verifies whether 1202 has assigned a UIN to a part and whether its parts ledger exists. The parts ledger application can access the parts ledgers of vehicle components, which can be stored in a data storage device. The parts ledger application can run on one or more processors included in and / or communicatively connected to the system. Optionally, such processors can be shared with other parts of the system, such as the UIN aggregator and authentication ledger application described above. Interaction between the parts ledger application and the user can be performed via a website and / or application interface. Optionally, the same application can be used for user access to both parts ledger data and authentication ledger data.

[0094] If the part's UIN does not exist, a new UIN (SITA UIN) will be created (1210), as described above regarding the UIN aggregator. Correspondingly, part ledger number 1212 will also be created.

[0095] If UIN already exists, then the corresponding part's parts ledger likely also exists. This is because, as mentioned above... Figure 10 As discussed, at step 1008, SITA UIN 902 may have already been assigned to the parts register. In this case, the existing parts register 1220 can be used.

[0096] The parts ledger can be continuously updated based on events from various parties such as parts owners, MRO, and M&E.1214 Events for a given part can be retrieved, for example, from one or more MRO and / or M&E applications. These applications can then continuously update the parts ledger based on the events that occur and throughout the entire lifecycle of the corresponding part.

[0097] Similarly, the parts ledger can be continuously updated based on records from various parties, such as parts owners and DMS. Records and events can be added to the parts ledger by: creating links between the parts ledger and the location where the records are stored; and generating hashes to verify them. For example, when an event is added to the parts ledger, a link can be created to establish a reference between the event and the associated record. This link can serve as a connection point allowing easy access to documents within the parts ledger, and the record can be stored in an external storage location such as DMS or cloud storage. To ensure the integrity and authenticity of records added to the parts ledger, hashes can be generated by the application. This hash can be a unique alphanumeric string calculated using a cryptographic algorithm (e.g., SHA-256) applied to the content of the document or record. The hash value can be a fixed-length string that acts as a digital fingerprint of the record. This ensures that even minor changes to the content will result in different hash values.

[0098] In addition to continuous parts ledger updates, the reliability of the 1218 hash can be continuously checked. For example, when a record needs verification or re-verification, the hash can be recalculated based on the record's current content. The recalculated hash can then be compared with the original hash stored in the parts ledger. If the two hashes match, the application can confirm that the record has not been tampered with or modified since it was added to the parts ledger. If the hashes do not match, the application can indicate that the record has been altered or corrupted, and its integrity cannot be verified. By creating links and generating hashes, the parts ledger application ensures the traceability and integrity of added records. The link establishes connections between events and records, allowing for easy retrieval and referencing. The hash can act as a checksum, providing a means of verifying the content of any digital passport (e.g., by checking the integrity of the digital passport's content and detecting any unauthorized modifications), which can be generated based on data from the parts ledger, authentication ledger, and UIN aggregator.

[0099] Therefore, the method of adding documents or records using links and hashes, as described above, enhances the security and reliability of the parts ledger. This method allows stakeholders to trust the authenticity and unchanged status of the records, thereby promoting transparency and compliance throughout the entire lifecycle of aircraft parts.

[0100] This application can automatically reconcile the parts ledger with the certifications of the relevant organizations from the certification ledger. Adding event-related records to the parts ledger allows the system to check if the organization had valid certification at the time of the event; this record contains information about the organization listed in the certification ledger. When updates related to the UIN aggregator occur (e.g., changes to part numbers), the UIN aggregator can also be synchronized with and / or updated in the parts ledger.

[0101] This application allows part owners to mark all or part of the information to be issued in the digital passport as "public" or "private". As used herein, the term "public" indicates that the corresponding information in the part register can be viewed externally with the owner's permission and that the corresponding information can be exported. Conversely, the term "private" indicates that the corresponding information in the part register cannot be viewed externally.

[0102] To make selected information in the digital passport visible to third parties, the parts ledger application can employ access control mechanisms and define different roles with specific permissions. Each parts ledger can be associated with an owner who has certain permissions and control over the information in the digital passport and its modifications. The parts ledger owner can browse the user interface and select specific information they want to mark as public and / or prepare for export (e.g., general details such as part numbers and manufacturer codes; and / or more specific data such as maintenance records or repair information). The parts ledger application can provide various export options to meet the owner's needs. These options can include generating printable PDFs, creating structured XML files, and / or generating downloadable document packages containing the selected information.

[0103] By following the process described above, the parts ledger application allows owners to selectively export and share information with third parties while maintaining control over the privacy and security of their digital passports. Therefore, the parts ledger application ensures that only authorized information is shared and that any sensitive data is properly protected or edited, thus providing a secure and controlled mechanism for information sharing.

[0104] At any given time, the owner can export a "snapshot" of the parts register, limited to information marked "public," to a file. This snapshot can form a digital passport or be part of that digital passport, and the digital passport can be timestamped.

[0105] Therefore, a digital passport can provide a snapshot of the parts ledger at a given time. The parts owner can then choose to securely share the digital passport with one or more third parties via, for example, email, file transfer, and / or any other suitable means.

[0106] After the 1234 digital passport has been generated based on a snapshot of the parts ledger, one or more third parties can view the information exported by 1236. The exported information can be provided in various formats, such as PDF or structured data. Therefore, third parties can access specific information shared by the owner, while any sensitive data that has been edited or obscured (i.e., marked as private) remains protected.

[0107] To ensure the integrity and authenticity of exported digital passport information, digital passport applications can use digital signatures or hash verification. This allows third parties to verify the authenticity of the exported data against the original digital record.

[0108] The exported digital passport information can be ingested into a third party's own system by following the process outlined below: • Receiving Exported Digital Passports: Third parties can receive exported digital passport information from the part owner. The exported digital passport information can preferably be in a format compatible with the third party's system, requiring minimal or no conversion.

[0109] • Data Mapping: Third-party enterprise applications can directly map fields or entities from the exported digital passport to corresponding fields or entities in their own enterprise applications. This ensures seamless alignment and integration of data with third-party enterprise applications without requiring extensive data extraction or transformation.

[0110] • Data Validation: Third-party enterprise applications can perform necessary validation checks on data ingested from digital passports to ensure its integrity and reliability. This may involve verifying the data according to predefined rules, such as format validation, range checks, or consistency checks.

[0111] • Database Integration: The captured digital passport information can be integrated into a third-party enterprise database without significant modifications. This data can preferably be stored in a manner consistent with the existing data structures and specifications of the third-party enterprise application.

[0112] • Verification and Synchronization: Third-party enterprise applications can verify whether the ingested data matches their expectations and is synchronized with their existing data or processes. This helps maintain data consistency and accuracy and ensures that the integrated data is reliable for third-party use.

[0113] • Continuous data management: Third parties can integrate the digital passport information they ingest into their regular data management practices, such as backup, updates, and data lifecycle management, to ensure the continued availability and reliability of the integrated data.

[0114] By following the process outlined above, third parties can efficiently ingest the exported digital passport information into their own systems. It will be apparent to those skilled in the art that the data ingestion and integration may need to be tailored to the third party's system capabilities, data requirements, and integration mechanisms.

[0115] If a third party connects to the administrator's platform (e.g., ... Figure 12 If the “SITA platform” is shown and a parts ledger is used, then a third party can receive 1260 ledgers with publicly available content and / or continue to update the content.

[0116] Therefore, a parts ledger eliminates the need for manual verification of parts information and supplier verification information. A parts ledger can be used to mark missing certifications, which can be particularly beneficial before a change of ownership.

[0117] Regarding maintenance organizations, the parts ledger application verifies records issued by the maintenance organization, such as Authorized Release Certificates (ARC) (e.g., EASA Form 1, FAA 8130, etc.), against the certified maintenance organization's known repository in the certification ledger.

[0118] As mentioned above, the certification ledger stores relevant information, such as FAA Part 145 certifications issued to aircraft maintenance station operators, and other qualifications demonstrating that the maintenance organization is regulatory compliant during maintenance. This can include ratings and scope of work.

[0119] Parts ledger applications can have functionality for ARC verification to ensure that records issued by maintenance organizations are certified and verified against a certified ledger. The certified ledger can act as a repository of trusted and certified maintenance organizations and includes their certification, qualifications, and authorization details.

[0120] Figure 13 The diagram illustrates an exemplary process for linking a maintenance organization's certification with a parts inventory. For example... Figure 13 As shown, when ARC (e.g., EASA Form 1, FAA 8130, etc.) is included in the parts register, the application can automatically initiate the verification process. The application can link the maintenance organization to issued documentation (e.g., Part 145 certification or other relevant certifications). This information can be retrieved from the certification register.

[0121] The verification process may involve steps such as querying the certification ledger using the organization's unique identifier or other identifying information.

[0122] The parts ledger application can retrieve and cross-reference the maintenance organization that issued the documents, check their validity, and ensure that the organization is authorized during maintenance.

[0123] If the maintenance organization's ARC matches and is valid with an entry in the certification log, the ARC document can be marked as certified and accepted. The parts log can then be updated with relevant maintenance event details, including the ARC and a reference to the maintenance organization's certification (e.g., Part 145, rating, and scope of work).

[0124] If an organization's qualifications fail verification or do not match the information in the certification ledger, the parts ledger application can mark the ARC document as "unverified" and generate an alert.

[0125] This feature provides an additional layer of assurance and compliance by verifying the maintenance organization's authorization status during repairs. This, in turn, helps maintain a high level of trust in the parts register by verifying records against valid sources such as certification ledgers. The automated verification process described above can be particularly useful for handling parts data for multiple vehicles and / or vehicles with a large number of parts (e.g., aircraft).

[0126] In addition, the parts ledger application can generate a notification if the following conditions are determined based on data from one or more parts ledgers: - One or more components of the vehicle currently do not meet one or more requirements associated with at least one of these components; and / or - One or more components of the vehicle are expected to fail to meet one or more requirements associated with at least one of these corresponding components after a predetermined period of time (which may be set by the relevant parties (e.g., parts owners, aircraft owners, application administrators)).

[0127] This notification may indicate that the corresponding component currently does not meet the requirements and / or will not meet the requirements. Therefore, the notification may include one or more identifiers associated with the corresponding component. For example, the notification may include the SITA UIN associated with the corresponding component.

[0128] Such current or anticipated non-compliance with aircraft component requirements may indicate that the component is unairworthy. Furthermore, depending on the function and importance of the non-compliant part, the assembly or the entire aircraft including such non-compliant part may be deemed unairworthy.

[0129] The notification may further include one or more actions required to meet the requirements and / or the parties(s) responsible for performing those actions. The generated notification may be viewed on the application and / or sent to multiple users associated with the vehicle owner, the vehicle operator, and / or one or more organizations responsible for the manufacture, distribution, inspection, maintenance, and / or repair of these corresponding components. It should be understood that such notifications, and the notifications described below regarding the traceability verifier, may be sent via any suitable method, such as email, SMS, and push notifications.

[0130] Given that vehicles typically consist of multiple assemblies, and each assembly comprises multiple parts, scanning the digital passports associated with those parts can be advantageous. For example, scanning the digital passports of all parts of an assembly can be useful for assessing the condition of the assembly. For such scanning, a "source verifier" algorithm can be used. A source verifier is an algorithm that scans the entire digital passport tree of the assembly. Optionally, one or more alerts can be generated regarding potential non-compliance (e.g., airworthiness non-compliance of aircraft parts), missing documentation, and / or missing certifications for one or more parts within the assembly.

[0131] Figure 14 The illustration shows an exemplary passport tree for an engine, which includes a gas turbine, blades, an exhaust frame assembly, and other components as sub-parts. Figure 15 The illustration shows an exemplary process of a traceability verifier scan. For example... Figure 15 As shown, the traceability validator application can check whether all parts ledgers in the assembly have the required records. Part records that need to be traced from a traceability perspective can be user-defined and / or specified in relevant regulations. Optionally, one or more of the authentication ledger application, UIN aggregator, parts ledger application, and traceability validator application can be the same application. If at least one of the authentication ledger application, UIN aggregator, parts ledger application, and traceability validator application has its own application, these applications can communicatively connect to enable mutual access to one or more functions and / or data. A notification can be generated if not all records for a corresponding part are present in its parts ledger.

[0132] Similarly, the traceability validator application can check whether all parts in the assembly have the required events. Part events that need to be traced from a traceability perspective can be user-defined and / or specified in relevant regulations. If not all events for a corresponding part are present in its parts register, a notification can be generated.

[0133] The application can also check if all certification ledgers in the assembly contain the required certifications (i.e., all references to current and past distributors, manufacturers, and maintenance organizations). If not all certifications for the corresponding part are present in its certification ledger, a notification can be generated.

[0134] The application can also check whether the maintenance activities of the maintenance organization are being carried out in accordance with the relevant ratings and scope of work. If not, a notification can be generated.

[0135] For life-limited parts, cyclic information tracking is essential throughout their lifespan. As used herein, the term "life-limited part" refers to any part for which a mandatory replacement period is specified in the model design, continued airworthiness instructions, or maintenance manual. This cyclic information can be retrieved from, for example, the customer's MRO M&E, but also from different internal data sources (such as ACARS, ADSB, etc.) of an administrator (e.g., SITA). Therefore, the application can aggregate cyclic information from different sources. If inconsistencies are detected, a notification can be generated.

[0136] After all checks are completed, the application can generate an execution summary indicating the urgency of any missing traceability information and any inconsistencies detected.

[0137] One or more of the above notifications may optionally be sent to one or more of the following: the owner of the vehicle or corresponding component, the operator of the vehicle, and / or one or more organizations responsible for the manufacture, distribution, inspection, maintenance and / or repair of these corresponding components.

[0138] Therefore, traceability validator applications provide an automated method for assessing the state and / or condition of vehicle components (e.g., the airworthiness of aircraft components). This not only eliminates the need for manual verification but also reduces the risk of assembly isolation. Traceability validators can be particularly useful for validating aircraft component assemblies (e.g., engines, auxiliary power units, landing gear), as these assemblies can comprise thousands of sub-components, some of which are life-limited components subject to airworthiness regulations. Furthermore, in the aerospace industry, all sub-components of an assembly must individually be airworthy before the assembly can be traded or installed.

[0139] Furthermore, it should be understood that the traceability validator application can be used to identify any potential deficiencies and / or non-compliance requiring attention based on current data available from the ledger. Such potential deficiencies and / or non-compliance can also be communicated to relevant parties in the form of notifications. These notifications may include any actions required to avoid the deficiencies and / or non-compliance, and the date on which these actions need to be performed.

[0140] As used herein, the terms “processor” or “processing device” mean one or more processing devices, apparatuses, programs, circuits, components, systems, and subsystems, whether implemented in hardware, software, or both, and whether or not they are programmable. As used herein, the terms “processor” or “processing device” include, but are not limited to, one or more computers, hardwired circuits, signal modification devices and systems, devices and machines for controlling systems, central processing units, programmable devices and systems, field-programmable gate arrays, application-specific integrated circuits (ASICs), systems-on-a-chip (SoCs), systems composed of discrete components and / or circuits, state machines, virtual machines, data processors, processing facilities, and any combination thereof.

[0141] As used herein, the terms “storage,” “storage device,” “storage medium,” or “data storage device” mean one or more data storage devices, apparatuses, programs, circuits, components, systems, subsystems, and storage media used to retain and provide such retained data, whether temporarily or permanently.

[0142] One or more of the applications, interfaces, databases, modules, and / or services described herein can be built using any platform well known to those skilled in the art, such as Microsoft Azure, Amazon Web Services, cloud platforms, IBM cloud platforms, or Google cloud platforms. It should also be understood that one or more of the functionalities described herein can be implemented using any programming language, such as HTML5, C++™, Java™, and .xml, as well as other programming languages ​​well known to those skilled in the art.

Claims

1. A method for monitoring the state of one or more components of a vehicle, comprising: Retrieve one or more known identifiers associated with each of the one or more components of the vehicle; Retrieve one or more requirements relating to one or more physical conditions and / or one or more regulations associated with each of the identifiers; Retrieve historical data regarding one or more physical conditions and / or one or more regulations associated with each of the identifiers; The requirements and historical data are aggregated by component based on the known identifiers to form one or more aggregated historical datasets, wherein each of the one or more aggregated historical datasets has historical data associated with one of the one or more components of the vehicle; and It is determined whether each component meets the requirements associated with each component based on the one or more aggregated historical datasets associated with each component.

2. The method as described in claim 1, wherein, If it is determined that at least one of the components currently does not meet one or more of the requirements associated with the at least one of the components, a notification indicating that the at least one of the components does not meet one or more of the requirements is generated.

3. The method as described in claim 1 or 2, wherein, If it is determined that at least one of the components is expected to no longer meet one or more of the requirements associated with the at least one of the components within a predetermined time period, a notification indicating that the at least one of the components is expected to fail to meet one or more of the requirements is generated.

4. The method according to any one of claims 2 or 3, wherein, The notification includes one or more of the identifiers of the at least one component in the component, wherein the at least one component in the component does not meet or is expected to not meet one or more of the requirements associated with the at least one component in the component.

5. The method as described in any one of the preceding claims, wherein, The requirements include one or more certifications that one or more organizations performing the manufacture, distribution, inspection, maintenance and / or repair of the corresponding components must hold in the course of performing the manufacture, distribution, inspection, maintenance and / or repair.

6. The method as described in any of the preceding claims, wherein, The requirements include one or more parameters related to one or more physical conditions, lifespan, and / or predetermined cycles of inspection, maintenance, and / or repair of the corresponding component.

7. The method as described in any of the preceding claims, wherein, The requirements include one or more parameters related to one or more of the inspections, maintenance, and / or repairs that need to be performed in response to one or more events affecting the physical condition of the corresponding component.

8. The method of claim 7, wherein, The one or more events affecting the physical condition are one or more of the following: reported malfunctions, defects and / or malfunctions of the corresponding component, and accidents that may cause malfunctions, defects and / or malfunctions of the corresponding component.

9. The method as described in any of the preceding claims, wherein, The historical data includes data related to the time when one or more of the manufacturing, distribution, inspection, maintenance and / or repair were performed on the corresponding component.

10. The method as described in any of the preceding claims, wherein, The historical data includes data related to one or more certifications held by an organization that performs one or more of the manufacturing, distribution, inspection, maintenance and / or repair of the corresponding component.

11. The method of claim 10, wherein, The data associated with each of the certifications includes: the name of the organization that issued the corresponding certification, the name of the entity that issued the corresponding certification, the period during which the corresponding certification is valid, and detailed information relating to one or more of the manufacturing, distribution, inspection, maintenance, and / or repair that the organization is certified to perform on the corresponding component.

12. The method as described in any of the preceding claims, wherein, The historical data includes detailed information related to past transactions of the corresponding component.

13. The method as described in any of the preceding claims, wherein, A new unique identifier is assigned to each group of aggregate identifiers, each group of aggregate identifiers consisting of identifiers associated with the same component.

14. The method as described in any of the preceding claims, wherein, The one or more known identifiers include identifiers issued and / or used by one or more of the following: manufacturers, operators, and organizations responsible for the manufacture, distribution, inspection, maintenance, and / or repair of the corresponding components.

15. The method as described in any of the preceding claims, further comprising: The notification shall be sent to one or more of the following: the owner of the vehicle, the operator of the vehicle, and / or one or more organizations responsible for the manufacture, distribution, inspection, maintenance and / or repair of the corresponding component.

16. The method of claim 15, wherein, One or more of the certifications are retrieved from a database, wherein the database is configured to allow one or more of the organizations to upload, modify, and / or delete one of a plurality of certifications held by those organizations.

17. The method as described in any of the preceding claims, further comprising: If it is determined that all the stated requirements for all components of the assembly are currently met, a certificate confirming that the assembly is suitable for operation, the assembly being part of the vehicle and including all the stated components of the assembly.

18. The method of any one of claims 1 to 16, further comprising: If it is determined that all the requirements for all components of the vehicle are currently met, a certificate confirming that the vehicle is suitable for operation is issued.

19. The method as described in any of the preceding claims, wherein, The vehicle in question is an aircraft.

20. The method of claim 19, further comprising: If it is determined that all the aforementioned requirements for all components of the assembly are currently met, a certificate confirming the airworthiness of the aircraft, the assembly being part of the aircraft and including all the aforementioned components of the assembly, is issued.

21. The method of claim 19, further comprising: If it is determined that all the requirements for all components of the aircraft are currently met, a certificate confirming the airworthiness of the aircraft is issued.

22. The method of claim 19, wherein, If it is determined that one or more basic components of the aircraft or the assembly of the aircraft does not meet or is expected not to meet one or more basic requirements associated with the basic component, then Generate an alert indicating that the aircraft or assembly is unairworthy, wherein the one or more basic components and the one or more basic requirements are determined based on one or more inputs from one or more users associated with the following: The owner of the aircraft, the assembly, and / or the corresponding basic components, The operator of the aircraft, and / or One or more organizations responsible for the manufacture, distribution, inspection, maintenance and / or repair of the aircraft, the assembly and / or the corresponding basic components.

23. The method of claim 22, wherein, The alarm includes one or more of the identifiers of the one or more of the basic components, wherein the basic component does not meet or is expected to not meet the one or more of the basic requirements within a predetermined time.

24. A method for monitoring the state of one or more components of a vehicle, comprising: Retrieve one or more known identifiers associated with each of the one or more components of the vehicle; Retrieve one or more requirements relating to one or more physical conditions and / or one or more regulations associated with each of the identifiers; Retrieve historical data regarding one or more physical conditions and / or one or more regulations associated with each of the identifiers; The requirements and historical data are aggregated by component based on the known identifier to form one or more aggregated historical datasets, wherein each of the one or more aggregated historical datasets has historical data associated with one of the one or more components of the vehicle; Based on the one or more aggregated historical datasets associated with each of the components, determine whether each of the components meets the requirements associated with each of the components; and If it is determined that at least one of the components currently does not meet one or more of the requirements associated with at least one of the components, and / or at least one of the components is expected to no longer meet one or more of the requirements associated with at least one of the components within a predetermined time period, then a notification indicating that at least one of the components does not meet one or more of the requirements is generated. The notification includes one or more identifiers of at least one of the components, wherein the component does not meet or is expected to not meet one or more requirements associated with at least one of the components.

25. A system for monitoring the state of one or more components of a vehicle, the system comprising a data storage device and a processor, the data storage device including a computer program stored thereon, and the processor being configured to run the computer program, wherein, The computer program is configured to perform the method according to any one of claims 1 to 24.

Images