Abstract: A computing system including a cooperative system architecture for cataloging, informing, sharing, and managing engineering assets within an organization includes a user management subsystem for creating a registered user profile associated with a specific user of the computing system. The registered user profile includes user metadata that provides identifying characteristics of the specific user. The computing system includes an asset management subsystem including an asset repository for recording one or more engineering assets. The asset management subsystem modifies the user metadata of the registered user profile in response to the specific user recording an engineering asset in the asset repository. The computing system includes a test management subsystem including a test repository for recording one or more test bill of materials.

Abstract: A resource sharing marketplace platform includes a back-office server including a controller adapted to run a plurality of integrated systems and a wireless communication module in communication with the controller, wherein, the resource sharing marketplace platform is adapted to receive a request from a user, collect data from a plurality of acceptable service providers, and provide a response to the user.

Abstract: Methods and systems are provided for automatically comparing, combining and fusing vehicle data. First data is obtained pertaining to a first plurality of vehicles. Second data is obtained pertaining to a second plurality of vehicles. One or both of the first data and the second data include abbreviated terms. The abbreviated terms are disambiguating at least in part by identifying, from a domain ontology stored in a memory, respective basewords that are associated with each of the abbreviated terms, filtering the basewords, performing a set intersection of the basewords, and calculating posterior probabilities for the basewords based at least in part on the filtering and the set intersection. The first data and the second data are combined, via a processor, based on semantic and syntactic similarity between respective data elements of the first data and the second data and the disambiguating of the abbreviated terms.

Abstract: A method of generating ontology models from requirement documents and software and performing consistency checks among requirement documents and software code utilizing ontology models. Terms in the plurality of requirement documents obtained from a database are identified. A processor assigns a part-of-speech tag to each term. The part-of-speech tag indicates a grammatical use of each term in the requirement documents. The processor classifies each term based on the part-of-speech tags. The classification identifies whether the each term is a part, symptom, action, event, or failure mode to constitute an ontology. The processor constructs an ontology-based consistency engine as a function of the ontologies. A consistency check is performed by applying the ontology-based consistency engine between ontologies extracted from two context documents. Inconsistent terms are identified between the context documents. At least one of the context documents having inconsistent terms is corrected.

Abstract: A method of automatic identifying linking relationships of requirements in a plurality of requirement documents. Terms in the plurality of requirement documents are identified. A part-of-speech tag is assigned to each term. Each identified term is selected as a focal term. Co-occurring terms within a predetermined distance of the selected focal term are determined. A linking relationship probability is calculated for each co-occurring term associated with the selected focal term. The selected focal terms and associated co-occurring terms between the plurality of requirement documents are compared. A degree of linking relationship is identified between two requirements as a function of a comparison between selected focal terms and the associated co-occurring terms between the plurality of requirement documents. An analysis report identifying the degree of linking relationships between two respective requirements is output.

Abstract: A method of automatically developing an ontology for product function and failure mode documentation for an apparatus. The apparatus is identified. A function-flow model is generated for the identified apparatus for identifying a composite structure of the apparatus. Functions and failure modes associated with the identified apparatus are enumerated. Failure data is obtained from a plurality of heterogeneous data sources. A semantic similarity module is applied to the enumerated failures by comparing a plurality of documents between the data sources. The semantic similarity module bridges a variety of terms used in the heterogeneous data to describe a respective failure. Failures associated with the enumerated apparatus functions are extracted from the plurality of documents between heterogeneous data sources. A composite of related terminology is generated for each identified failure mode.

Abstract: A method of automatically developing an ontology for product function and failure mode documentation for an apparatus. The apparatus is identified. A function-flow model is generated for the identified apparatus for identifying a composite structure of the apparatus. Functions and failure modes associated with the identified apparatus are enumerated. Failure data is obtained from a plurality of heterogeneous data sources. A semantic similarity module is applied to the enumerated failures by comparing a plurality of documents between the data sources. The semantic similarity module bridges a variety of terms used in the heterogeneous data to describe a respective failure. Failures associated with the enumerated apparatus functions are extracted from the plurality of documents between heterogeneous data sources. A composite of related terminology is generated for each identified failure mode.

Abstract: A method of automatic identifying linking relationships of requirements in a plurality of requirement documents. Terms in the plurality of requirement documents are identified. A part-of-speech tag is assigned to each term. Each identified term is selected as a focal term. Co-occurring terms within a predetermined distance of the selected focal term are determined. A linking relationship probability is calculated for each co-occurring term associated with the selected focal term. The selected focal terms and associated co-occurring terms between the plurality of requirement documents are compared. A degree of linking relationship is identified between two requirements as a function of a comparison between selected focal terms and the associated co-occurring terms between the plurality of requirement documents. An analysis report identifying the degree of linking relationships between two respective requirements is output.