System for using task tables and technical data from a relational database to produce a parsed file of format instruction and a standardized document

• US 5,457,792 A
• Filed: 11/07/1991
• Issued: 10/10/1995
• Est. Priority Date: 11/07/1991
• Status: Expired due to Fees

• Current Assignee: Hughes Aircraft Company (Rtx Corporation)
• Original Assignee: Hughes Aircraft Company (Rtx Corporation)
• Inventors: Virgil, Kenneth W., June, Philip J., Baron, Albert D.
• Primary Examiner(s): Black, Thomas G.
• Assistant Examiner(s): AMSBURY, WAYNE P
• Application Number:
  US07/788,906
• Time in Patent Office: 1,433 Days
• Field of Search: 364/419, 364/419.03, 364/419.1, 364/419.17, 364/419.14, 395/600, 395/650
• US Class Current: 1/1
• CPC Class Codes: G06F 40/174 Form filling; Merging

Abstract

A process for extracting data from a MIL-STD relational database, parsing and automatically processing the resultant output into a MIL-STD technical publication. The data extracted from the database is tagged, sorted and passed to a Parser program which produces several outputs. One output is a disk file which has encoded tags and control characters. The disk file is then processed into word processing syntax used in MIL-STD publications. Another output is a formatted pseudo technical publication which contains all relevant data in a style which resembles a technical manual. This pseudo technical publication allows the data to be reviewed and approved prior to processing the disk file data into a technical publication. A third output is a Task checklist.

Claims

1. A method for automatically generating a technical publication descriptive of a work task or series of work tasks involving the operation or maintenance of particular hardware, and complying with a predetermined standardized document format wherein a set of instructions and pertinent information necessary for performing said task or series of tasks is included in the technical publication, the method further comprising a sequence of the following steps:

providing access to a relational database which does not include, define or have residing or embedded therein document structure data defining a document structure of the technical publication, said database having stored therein for each said task one or more data sets, each said data set being identified with a predetermined unique identification name and specifying content information required in the performance of said task while not having any document format data embedded therein;

constructing externally to said database a task table which contains a list of data sets, said task table for identifying the data to be extracted from said database for a particular chapter of said document, said task table comprising a listing of the identification names of the data sets to be extracted from said database;

using said task table externally to said database to extract said data sets from said database, and for each data set, defining an input file including a parser header record identifying the particular type of data comprising said data set;

parsing said input files external to said database to create a parser output file containing the content data necessary to publish said technical publication, said parsing step comprising reading each input file, setting program logic flags when an input file parser header record is encountered, said logic flags identifying particular report headings to be printed in said technical publication, and encoding within said parser output file symbols representing document format instructions for said predetermined standardized document format; and

processing said parser output file externally to said database to convert said encoding symbols into said document format instructions and publish said technical publication with said report headings and in accordance with said document format instructions to comply with said predetermined standardized document format, said publication setting forth information extracted from said relational

database which is necessary to the performance of said task.

2. The method of claim 1 wherein said task table comprises a chapter header record which defines the chapter number and name, a process header record-which assigns beginning paragraph numbers within a chapter, and at least one task identifier record which identifies which data sets are to be extracted from said database.

3. The method of claim 2 wherein said chapter header record comprises a record having a predetermined number of columns, wherein a first data field at a first set of said columns designates a first predetermined keyword, a second data field at a second set of said columns designates the chapter number to be assigned to the chapter to be generated, and a third data field at a third set of said columns designates the name of the chapter as it is to be published in said publication.

4. The method of claim 2 wherein said process header record comprises a record having a predetermined number of columns, wherein a first data field at a first set of said columns designates a second predetermined keyword, and a second data field at a second set of said columns designates the starting paragraph number for the tasks in said task table.

5. The method of claim 2 wherein said task identifier record comprises a record having a predetermined number of columns, wherein a first data field at a first set of columns designates a first task code, and a second data field at a second set of columns designates a second task code, said first and second task codes comprising said identification names.

6. The method of claim 1 wherein said task table comprises a plurality of task identifier records, and wherein said task identifier records are processed in the order in which they appear in said task identifier record in said processing step.

7. The method of claim 1 wherein said database is a relational database which complies with MIL-STD 1388-2A.

8. The method of claim 1 wherein said technical publication complies with a predetermined military publication standard.

9. The method of claim 1 wherein said data sets extracted from said database comprise a data set defining a list of consumables required for said task.

10. The method of claim 1 wherein said data sets extracted from said database comprise a data set defining a list of special tools required for said task.

11. The method of claim 1 wherein said data sets extracted from said database comprise a data set defining special handling equipment required for said task.

12. The method of claim 1 wherein said data sets extracted from said database comprise a data set defining task narrative describing said task.

13. The method of claim 1 wherein said data sets extracted from said database comprise a data set defining illustrated parts involved in said task.

14. The method of claim 1 wherein said parsing step further includes the step of providing a pseudo technical publication report file which comprises data from said parser input files representing said content information but which does not rigidly comply with said standardized document format, said report file for use as a preliminary review manuscript of said technical publication.

15. The method of claim 1 wherein said steps of providing access to said database, using said task table to extract data sets, and parsing said input files are conducted within a mainframe computer environment, and said step of using said parser output file to publish said technical publication is conducted on a computer workstation comprising a personal computer.

16. A method for automatically generating a technical publication descriptive of a work task or series-of work tasks involving the operation or maintenance of particular hardware, and complying with a predetermined standardized document format, wherein a set of instructions and pertinent information necessary for performing said task or series of tasks is included in the technical publication in accordance with the standardized document format, the method comprising a sequence of the following steps:

providing access to a relational database, which database does not include, define or have residing or embedded therein document structure data defining a document structure of the technical publication, said database having stored therein for each said task one or more data sets in rows and columns of one or more tables comprising said database, each said data set being identified with a predetermined unique identification name and specifying content information required in the performance of said task while not having any document format data embedded therein;

constructing externally to said database a task table which contains a list of data sets, said task table for identifying the data to be extracted from said database for a particular chapter of said document, said task table comprising a listing of the identification names of the data sets to be extracted from said database, said task table defining the particular data to be incorporated into said technical publication from said database, including a list of consumables required for said task, a list of special tools required for said task, a list of special handling equipment required for said task, and a list defining task narrative data, and illustrated parts breakdown data;

using said task table externally to said database to extract said data sets from said database and provide parser input files corresponding to said data sets, each input file comprising header records specifying the file identity;

parsing said data sets externally to said database to create a machine readable technical manual file containing the content data specific to said task necessary to publish said technical publication, said parsing step comprising setting informational messages in said technical manual file identifying particular report headings to appear in the technical publication and format symbols representing document format instructions for said predetermined standardized document format; and

processing said technical manual file externally to said database to convert said encoding symbols into said document format instructions and publish said technical publication with said report headings in accordance with said document format instructions to comply with a rigid format specified by said standardized document format.

17. The method of claim 16 wherein said task table comprises a chapter header record which defines the chapter number and name, a process header record which assigns beginning paragraph numbers within a chapter, and at least one task identifier record which identifies which data sets are to be extracted from said database.

18. The method of claim 17 wherein said chapter header record comprises a record having a predetermined number of columns, wherein a first data field at a first set of said columns designates a first predetermined keyword, a second data field at a second set of said columns designates the chapter number to be assigned to the chapter to be generated, and a third data field at a third set of said columns designates the name of the chapter as it is to be published in said publication.

19. The method of claim 17 wherein said process header record comprises a record having a predetermined number of columns, wherein a first data field at a first set of said columns designates a second predetermined keyword, and a second data field at a second set of said columns designates the starting paragraph number for the tasks in said task table.

20. The method of claim 17 wherein said task identifier record comprises a record having a predetermined number of columns, wherein a first data field at a first set of columns designates a first task code, and a second data field at a second set of columns designates a second task code, said first and second task codes comprising said identification names.

21. The method of claim 16 wherein said task table comprises a plurality of task identifier records, and wherein said task identifier records are processed in the order in which they appear in said task identifier record in said processing step.

22. The method of claim 16 wherein said database is a relational database which complies with MIL-STD 1388-2A.

23. The method of claim 16 wherein said technical publication complies with a predetermined military publication standard.

24. The method of claim 16 wherein said parsing step further includes creating a task checklist report file, using only said task narrative list data.

25. The method of claim 16 wherein said parsing step further includes the step of providing a pseudo technical publication report file which comprises data from said parser input files but which does not rigidly comply with said standardized document format, said report file for use as a preliminary review manuscript of said technical publication.

26. The method of claim 16 wherein said steps of providing access to said database, using said task table to extract data sets, and parsing said input files is conducted within a mainframe computer environment, and said step of using said parser output file to publish said technical publication is conducted on a computer workstation comprising a personal computer.