Specifications automation system and method

Abstract

A method of leveraging XML (eXtensible Markup Language) Technology, or similar modeling languages such as ontology definition languages, to provide attribution and multi-node data modeling, object orientation, classes, and linkage capabilities of such languages and technologies, specifically for authoring new and translating existing technical specifications in such a way that the base text content is augmented with additional information such as metadata, in such a way that other sub-specifications, data sheets, inspection and quality assurance documents, etc., do not need to be written separately, but instead become logical sub-components of the governing specifications themselves.

Description

BACKGROUND

Technical specifications or engineering specifications used in various industries are static documents, typically produced using a word processor. These documents contain numerous references to codes, standards and other specifications. They also contain references to other kinds of documents that are intimately related, such as equipment datasheets, inspection and test requirements, bills of material, and other engineering, procurement, and project management documents. In many cases the main engineering specifications are the governing documents, while the information on other closely related specifications and other intimately related documents becomes out-of-spec because they are treated as separate documents.

It would be desirable if related, similar, and repeated information shared among several documents be electronically tied to the governing specifications. More particularly, it would be desirable if the information was not duplicated at all-that duplicated or related information reside only in the master specifications. More particularly yet, it would be desirable if the various related documents were not additional standalone documents at all, but instead, were alternative views and printouts from metadata contained in the master specifications themselves.

SUMMARY

The invention relates to a method of leveraging XML (eXtensible Markup Language) technology, and/or similar modeling languages such as ontology definition languages, OWL, RDL, HTML, and others, and more particularly, the attribution and multi-node data modeling, object orientation, classes, and linkage capabilities of such languages and technologies, specifically for the purpose authoring new, and translating existing specifications in such a way that the base textual content is augmented with additional information (aka metadata) in such a way that other sub-specifications, datasheets, inspection and quality assurance documents, etc. do not need to be written separately, but instead become logical sub-components of the governing specifications themselves.

Furthermore, this invention relates to the design and development of computer software and user interface, and configuration files that enable the application of said method.

For the above cited reasons it is an object of the invention to provide both a data model and computer software to enable engineers and other professionals and responsibilities to “multi task”, that is, create several documents for various purposes and workflows and business requirements from a single editing session.

For the data model, for each specification paragraph, in addition to the main textual component, the appropriate attributes and/or elements are created and defined by schema to support said multitasking and the storing of related information for related purposes.

For the computer program and user interface, the ability for the user to write the main textual components of the specification while having simultaneously in view the content of the various metadata, as necessary, and being able to edit all at the same time.

Applicable to both data model and user interface, is the automatic linking and electronic management of the relationships of each paragraph and its metadata, as well as the ability to publish the main spec and it's related sub-specifications and/or documents automatically.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A and 1B together show an application window;

FIGS. 2 and 3 show sample XML (or other data modeling language) that stores text and related metadata, manages links, and provides for the programmatic extraction and automatic generation of the various views and documents.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

The invention provides a system for automation of specifications that allows for the uniform creation and/or loading of information used in forming technical specifications into an automated and indexed data model, preferably using an XML spec schema and XML conventions or other similar modeling technologies such as ontology definition language(s), OWL, RDL, etc. This enables the technical specifications, specifications, codes and/or standards being utilized to be converted into electronic data that is in a standardized form based on the schema provided. The model allows specific information to be tagged and/or coded into specific fields so that they can be easily drawn from the Specification, referenced or updated in a uniform manner. Additionally, specific information and/or requirements can be tagged in or on spec paragraphs allowing these items to be separately drawn from and/or indexed in the technical specifications. For example, all inspection and test criteria requirements, codes, standards, etc. can be tagged so that they can be easily accessed, drawn from the technical specification and/or indexed separately.

FIGS. 1A and 1B together show an application window 100 that in the top-left pane 110 shows a set Vendor Information Requirements Forms (VIRF) that is part of a refrigeration system specification.

The specification itself, in browse-able tree view is shown in the bottom left pane 120.

The top center pane 130 shows an individual vendor information requirement item. It has a field for the main text, but also shows user input fields for the various metadata, such as “PkgNo” (Package Number), “Status”, “CtrlNo” (Control Number), “Date/Time”, “Keyword”, “Reminder”, and so on. This information, collectively for all similar items in the subject XML files, is sufficient to generate a full Vendor Information Requirements package.

The top right pane 140 shows other items and main specification paragraphs that are electronically linked to the VIRF item. These relationships are managed automatically and all changes to any interrelated item propagates through all of them.

The bottom center pane 150 shows one of the main specification paragraphs including it's various metadata. Specifically, note checkboxes named “Data”, “VIRF”, “Bid Tab” (Bid Tabulation), and “Insp” (Inspection). These checkboxes mark (or un-mark) the paragraph as a provider (or non-provider) of some or all of this additional data. When the user hovers over these checkboxes she can add additional information for each requirement. In this example, the user can specify “Exchanger Arrangement”, while simultaneously specifying which drawings this shall be shown on, and simultaneously generating an inspection checklist that will allow a quality assurance engineer to access the appropriate drawing, automatically with the appropriate specification paragraph, to verify these “Exchanger Arrangement” at a supplier's works after manufacture. The invention relates to a method of accomplishing all of this directly from the main paragraphs' interfaces, and not sequentially created multiple documents that can later become dis-synchronized, as it is done today.

FIGS. 2 and 3 show sample XML 200 (or other data modeling language) that stores text and related metadata, manages links, and provides for the programmatic extraction and automatic generation of the various views and documents, which are internally just one electronic document, therefore everything that is related is automatically maintained together and never becomes dis-synchronized.

The system is implemented utilizing a PC or other computer processor programmed with the specific method according to the invention.

The system is implemented such that various documents and concepts that are derivative of the main specification, called “Child Documents”, live as flags or attributes on main specification paragraph objects, so that they are not stand alone documents and never become dis-synchronized from the main specification. These Child Documents are therefore not separately created, and can be generated while working on the main technical specification. The Child Documents can be attachments, subsidiaries, lists and various other documents and concepts that this environment considers as sub-sets of technical codes and standards. This list includes, but is not limited to, datasheets, inspection and test plans, and requirements, information requirements (e.g., vendor information requirements), etc. Child Documents can be generated from content in the main specification. Content in the main specification may be marked and/or tagged in the computer application either directly (i.e., in the main body text), or indirectly, i.e. tags and/or additional information are associated with specific paragraphs of the main specification.

The system further provides for “Item Level Granularity” for revision and history control. This can be implemented by a GUID (Globally Unique Identifier) or a URI (Universal Resource Identifier) or URL (Universal Resource Locator). This enables objects to be uniquely identified in the system and disassociate the objects from the paragraph number and other user attributes, so that if the main specification is renumbered in the future, paragraph-level revision and history are not lost. Item Level granularity can be implemented by maintaining an archive xml document backing each main xml document that maintains all ‘stale’ objects.

Further, the system provides discipline-specific views, functionalities and workflows. These are externally configurable by a configuration file, and thus do not require the recompilation of the product.

The system also has the functionality of providing reminders. That is, there is the ability of any object or entity in the main specification to record a reminder. These reminders have due dates as well as the ability to “snooze.”

Claims

1. A method of automatically generating specification data models, said method comprising the steps of: parsing, by a hardware-based computer processor, existing documents or beginning a new blank document in lieu of an existing document;creating, by the hardware-based computer processor, a main specification that includes a plurality of main specification paragraphs, wherein the main specification is maintained by main specification paragraph objects that are uniquely identified with item level granularity, and the main specification paragraph objects are disassociated from any paragraph numbers of the main specification paragraphs;allowing a user to edit a main specification paragraph and metadata in simultaneous views;allowing the user to select relationships between the main specification paragraph and at least some of the metadata, and set notifications;allowing the user to configure output document types and publishing requirements;creating, by the hardware-based computer processor, Child Documents with the metadata related to the main specification paragraph, the Child Documents existing as logical sub-components of the main specification that reside internal to the main specification, and are indicated by flags or attributes on main specification paragraphs; andpublishing the main specification and one or more of the Child Documents simultaneously.

2. The method of claim 1, wherein the item level granularity is implemented by a GUID (Globally Unique Identifier) or a URI (Universal Resource Identifier) or a URL (Universal Resource Locator).

3. The method of claim 1, wherein the item level granularity is implemented by maintaining an archive eXtensible Markup Language (XML) document backing the main specification that maintains all stale objects.

4. The method of claim 1, further comprising allowing a user to set reminders associated with any object or entity in the main specification.

5. The method of claim 4, further comprising recording a due date for a reminder and providing a snooze capability for the reminder.

6. A system comprising: a hardware-based computer processor;computer software executable by the hardware-based computer processor, the computer software configured to: create a main specification that includes a plurality of main specification paragraphs, wherein the main specification is maintained by objects that are uniquely identified with item level granularity and the objects are disassociated from any paragraph number of paragraphs in the main specification;show a main specification paragraph and metadata in simultaneous views to a user;receive a selection from the user of relationships between the main specification paragraph and at least some of the metadata;create Child Documents with the metadata related to the main specification paragraph, the Child Documents existing as logical sub-components of the main specification that reside internal to the main specification in association with the main specification paragraph; andpublish the main specification and one or more of the Child Documents.

7. The system of claim 6, wherein the computer software is further configured to: mark the main specification paragraph to indicate that the main specification paragraph is a provider of the at least some of the metadata and a non-provider of other metadata.

8. The system of claim 6, wherein the Child Documents include sub-specifications, datasheets or inspection and quality assurance documents.

9. The system of claim 6, wherein the item level granularity is implemented by a GUID (Globally Unique Identifier) or a URI (Universal Resource Identifier) or a URL (Universal Resource Locator).

10. The system of claim 6, wherein the item level granularity is implemented using an archive eXtensible Markup Language (XML) document backing the main specification.

11. A method comprising: creating, by a hardware-based computer processor, a main specification that includes a plurality of main specification paragraphs;maintaining the main specification with main specification paragraph objects that are uniquely identified with item level granularity, wherein the main specification paragraph objects are disassociated from any paragraph numbers of the main specification paragraphs, such that information is preserved through any paragraph renumbering;showing a main specification paragraph and metadata in simultaneous views to a user;receiving a selection from the user of relationships between the main specification paragraph and at least some of the metadata, the selection to include marking the main specification paragraph to indicate the main specification paragraph is a provider of the at least some of the metadata and a non-provider of other metadata;creating, by the hardware-based computer processor, Child Documents with the metadata associated with the main specification paragraph, the Child Documents existing as logical sub-components of the main specification that reside internal to the main specification in association with the main specification paragraph; andpublishing the main specification and one or more of the Child Documents.