Data-type definition driven dynamic business component instantiation and execution framework and system and method for managing knowledge information

• US 9,667,468 B2
• Filed: 03/28/2012
• Issued: 05/30/2017
• Est. Priority Date: 04/12/2001
• Status: Expired due to Fees

• Current Assignee: Wellogix Technology Licensing LLC (Wellogix Incorporated)
• Original Assignee: Wellogix Technology Licensing LLC (Wellogix Incorporated)
• Inventors: Chikirivao, Bill S., Bodnar, Robert C., Hurst, Craig
• Primary Examiner(s): Ries, Laurie
• Application Number:
  US13/432,841
• Publication Number:
  US 20120246556A1
• Time in Patent Office: 1,889 Days
• CPC Class Codes: G06F 40/154 Tree transformation for tree-structured or markup documents, e.g. XSLT, XSL-FO or stylesheets
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 30/04 Billing or invoicing
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

In a complex workflow environment, a data-type-definition (DTD) schema drives a dynamic business component instantiation and execution framework that integrates documents with data and information created by various applications, potentially operating on several different platforms, enabling complex workflow and collaboration to occur over a communication network such as the Internet. The DTD execution language is preferably an industry specific XML-based tag set that defines business component instantiation, execution, input and output parameters, workflow, user profile, and collaboration specifications for a given task or data in a complex workflow process. Business and data processing components available on systems both within and outside the complex workflow system are called upon to provide the processing, interpretation, and transformation functions for the complex workflow system. The results of such processing are then returned to the complex workflow system for integration within the workflow process.

Claims

1. A method for processing an extensible markup language (XML) tagged document with a server, the method comprising:

inputting source data into the server;

converting the source data to an XML tagged document comprising an XML data subset, a document type identifier, a first data type, and a second data type;

determining the first data type and the second data type;

identifying at least one metafile associated with the first data type and the second data type determined by the determining operation, wherein the metafile comprises instructions to the server for manipulating data relating to one or more specified parameters present in the first data type determined by the determining operation and instructions to the server indicating that process results of the first data type be stored for use in subsequent processing of the second data type, wherein the server comprises a language execution broker that determines instructions for processing the XML tagged document based on the document type identifier, the document defining workflow and collaboration specifications for a given complex workflow system;

using the metafile to identify one or more data fields in the XML tagged document corresponding to the one or more specified parameters; and

generating an output file, wherein

the second data type is determined based on the process results obtained by the language execution broker from the processing of the first data type, and the language execution broker routes the output file to a plug-n-play engine that determines whether the document is to be processed within the complex workflow system or external to the complex workflow system.

2. The method of claim 1, wherein the first data type comprises information about wellbore operations, and the second data type comprises information about casing conditions.

3. The method of claim 1, wherein the source data comes from an operational data store.

4. The method of claim 1, wherein the metafile specifies one or more instructions for manipulating the first and second data types in the XML tagged document.

5. The method of claim 1, further comprising:

creating a plurality of metafiles wherein at least one metafile corresponds to at least one of the first data type and the second data type; and

wherein the operation of identifying at least one metafile further comprises accessing the plurality of metafiles to determine the at least one metafile.

6. The method of claim 1, further comprising:

validating the one or more data fields in the XML tagged document.

7. The method of claim 6, wherein the validating operation further comprises:

performing a form validation operation on said one or more data fields in the XML tagged document.

8. The method of claim 6, wherein the validating operation further comprises:

performing a type of validation operation on said one or more data fields in the XML tagged document.

9. The method of claim 6, wherein the validating operation further comprises:

performing a logic validation operation on said one or more data fields in the XML tagged document.

10. The method of claim 1, wherein the output file generated by the generating operation contains information about an oil well.

11. The method of claim 1, wherein the output file generated by the generating operation contains information about a gas well.

12. The method of claim 1, further comprising:

after the generating operation, creating an output document based on the output file.

13. The method of claim 1, further comprising:

after the generating operation, mining the output file for one or more patterns of the one or more data elements therein.

14. The method of claim 1, further comprising:

accessing a set of rules;

after the generating operation, determining whether at least one of the one or more data fields of the output file complies with at least one rule of the set of rules.

15. The method of claim 1, wherein the source data further comprises at least one of production data, drilling operations data, and combinations thereof.

16. The method of claim 1, further comprising:

storing the output file, wherein the storing operation stores the output file in a persistent memory associated with the server.

17. A system for processing an extensible markup language (XML) file, the system comprising:

one or more devices in communication with a network for receiving the XML file comprising one or more data elements accessible by a server,

wherein the server comprises a synchronization server configured to monitor the XML file in order to direct the XML file for further processing within the server, and a language execution broker configured to read the XML file in order to provide XML-based instructions for the further processing, and

wherein the one or more devices comprise;

computer instructions for determining a first type of data and a second type of data provided in the XML file representative of the one or more data elements;

data storage comprising at least one metafile associated with the type of data, wherein the metafile comprises instructions for manipulating data related to one or more specified parameters present in the type of data and instructions to the server indicating that process results of the first data type be stored for use in subsequent processing of the second data type;

computer instructions for identifying at least one metafile associated with the first type of data and the second type of data, wherein the language execution broker provides instructions to process the second data type based on the results obtained by processing of the first data type;

computer instructions for identifying the one or more data elements in the XML file corresponding to the one or more specified parameters of the metafile; and

computer instructions for generating an output file that includes the one or more data elements, wherein

the second data type is determined based on the process results obtained by the language execution broker from the processing of the first data type.

18. The system of claim 17, wherein the one or more devices further comprise:

computer instructions for converting, at an application server, at least one received data source file into the XML file.

19. The system of claim 18, wherein the one or more devices further comprise:

computer instructions for operating an instance of a web browser in the application server, wherein said instance of the web browser provides for entry of the at least one received data source file.

20. The system of claim 18, wherein the one or more devices further comprise data storage for storing the XML file, and wherein the XML file comprises a subset of XML tailored to a specific industry to provide an interfacing scheme for data structures used to facilitate the transfer of information associated with the specific industry.

21. The system of claim 17, wherein the first data type comprises information about wellbore operations, and the second data type comprises information about casing conditions.

22. The system of claim 17, wherein the metafile specifies one or more instructions for manipulating the one or more data elements in the XML file.

23. The system of claim 17, wherein the XML file further comprises an XML tagged document that identifies an industry-appropriate data subset, and wherein the one or more devices further comprise computer instructions for validating the one or more data elements in the XML tagged document.

24. The system of claim 23, wherein the computer instructions for validating further comprise computer instructions for performing a form validation operation on said one or more data elements in the XML tagged document.

25. The system of claim 23, wherein the computer instructions for validating further comprise computer instructions for performing a type validation operation on said one or more data elements in the XML tagged document.

26. The system of claim 23, wherein the computer instructions for validating further comprise computer instructions for performing a logic validation operation on said one or more data elements in the XML tagged document.

27. The system of claim 17, wherein the output file comprises information about an oil well.

28. The system of claim 17, wherein the output file comprises information about a gas well.

29. The system of claim 17, wherein the one or more devices further comprise computer instructions for mining the output file for one or more patterns of the one or more data elements therein.

30. The system of claim 17, wherein the one or more devices further comprise a set of rules and computer instructions for determining whether at least one of the one or more data elements of the output file complies with at least one rule of the set of rules.

31. The system of claim 17, wherein the server further comprises source data that comes from an operation data store.

32. The system of claim 17, wherein the output file is stored in a persistent memory associated with the server.

33. A system for processing source data into a data format suitable for processing by a web application server, comprising:

a server comprising a synchronization server, and a language execution broker, wherein the server receives the source data after it has been converted into an XML file comprising a first data type and a second data type, wherein the synchronization server monitors the XML file in order to direct the XML file for further processing within the server;

computer readable program code devices in communication with the server which effect identification of the first data type and the second data type;

a data server in which components of the XML file are saved in one or more files, the data server comprising at least one metafile associated with the first data type and the second data type, wherein the metafile comprises instructions for manipulating data related to one or more specified parameters present in the first data type and instructions to the server indicating that process results of the first data type be stored for use in subsequent processing of the second data type;

computer readable program code devices in communication with the server which effect application of the metafile to the XML file to determine one or more data fields that correspond to the one or more specified parameters, wherein the language execution broker provides instructions to process the second data type based on the results obtained by processing of the first data type; and

a web application server which accesses the at least one or more files from the data server and manipulates the data fields thereof to provide and output to a client system connected to the web application server, wherein the output comprises one or more data fields that correspond to the one or more specified parameters, wherein

the second data type is determined based on the process results obtained by the language execution broker from the processing of the first data type.

34. A computer program product comprising:

a computer usable medium and computer readable code embodied on said computer usable medium for converting an extensible markup language (XML) file to data elements accessible by a server, the computer readable code comprising;

computer readable program code devices configured to cause the computer to effect a receiving of an XML file comprising a data file configured for the oil and gas industry;

computer readable program code devices configured to cause the computer to effect a determining of a first data type and a second data type provided in the data file;

computer readable program code devices configured to cause the computer to effect an identifying of at least one metafile associated with either of the first data type or the second data type determined by the determining operation, wherein the metafile comprises instructions to the server for manipulating data relating to one or more specified parameters present in any of the types of data determined by the determining operation and instructions to the server indicating that process results of the first data type be stored for use in subsequent processing of the second data type, wherein the server comprises a language execution broker;

computer readable program code devices configured to cause the computer to effect use of the metafile to identify one or more data elements in the data file corresponding to the one or more parameters; and

computer readable program code devices configured to cause the computer to effect a generating of an output file which includes the one or more data elements, wherein

the second data type is determined based on the process results obtained by the language execution broker from the processing of the first data type.