Using HTML (Hyper-text Marked Linked) documents to structure and tie together all your Electronic Information in an easily navigateable way.
Share all data including CAD Drawings, Bills of Materials, Specifications and other Mechanical Equipment Documentation Using your Microsoft Windows® Internet Explorer on every PC connected to your local network. A vehicle that makes a paperless manufacturing system possible.
Engineering Applications
This example represents documentation infrastructure and the flow of CAD Drawings and related Electronic Documentation within a Drawing Package.
   HTML based technical data structure can incorporate and document all kinds of data accessible using the Internet Explorer browser. If there is a platform that is best suited to utilize all the different types of data, it is Microsoft Windows® Internet Explorer. The function of Documentation Hyper Structure (DHS) is to provide this HTML capability to meet the manufacturer's specific needs.

   Retrieving data or information such as drawings, bills of materials, purchased part or component information as well as other associated data can be cumbersome. From an engineering standpoint, compiling all the paperwork to manufacture a product can be an enormous task for a piece of packaging machinery. There can be hundreds of sources of information that need to be tapped, and documented somehow. In the case of purchased part and components, photo-copied pages out of catalogues, printed pages of .pdf files and so forth, mostly documented in paper form to be stored in boxes, binders or file cabinets.

   Almost all if not all component manufacturers provide .pdf files and in a lot of cases the CAD geometry is available in both 2D and 3D to download in various formats. A machine designer can download this geometry onto his/her computer and insert it into a layout. At the same time, he/she can create the paperwork or documentation and enter information into a database of some sort to associate it with an internal or company part number and in some cases create a paper document to complete the documentation process. The machine designer makes note of the part to specify it on it's respective assembly and bill of materials.

   In the case of purchased components, usually when the manufacturer's part number builds the component, such as air cylinders and valves, gearboxes, servo drives, ect., it may become necessary later to refer back to what that manufacturer's part number means. When machine designers choose parts for their design, common parts are a focus because the documentation for these parts are already done. When it is quick and easy to get the right parts into their layouts, the process is smooth and efficient. Every engineer has his/her own way of doing this usually within a common infrastructure of resources utilizing the company's inventory of documented parts when possible.

   As a machine designer, browsing through CAD files for geometry and .pdf files for documentation purposes can be time consuming. A library of files in the form of "local .html documents" that have categories of types of components with links to CAD and .pdf files, the ones already downloaded and stored locally would eliminate the agony of browsing through those files manually. Not only that, but it is easy to navigate and available to all the designers.