The workflow processes to develop content for a schematic diagram solution is critical and rarely discussed. This article will review a successful approach used by Atlas Dynamics. The link below is a complete detail of the workflow that will be discussed.
A wiring diagram project usually starts out with a vehicle and some source schematic diagrams. The source diagrams must be converted to at least a CGM level 4 or WebCGM to work as an interactive diagram with hotspots, links and indexed searchable data. Some CAD tools can articulate a set of diagrams in their native formats into circuits and links but need to be transformed into CGM file formats. Atlas does have a new tool called XAT Wires that can take in CAD wire lists and transform the information into CGM S1000D compliant diagrams.
A good IEWD solution has the ability to resolve a vehicle into a set of systems and subs-system. In such a articulated configuration diagrams can be associated and provide an intuitive ability to navigate a vehicle's set of diagrams, this proves very advantageous for projects where there are hundreds of diagrams.
The next set of processing phases are called Native Vector Data Processing, however, if the project is using diagrams that were transformed from a CAD tool's wire lists the Native Vector Data processing is unnecessary. On the other hand if the diagrams are from a raster to vector transforming tool or a simple CAD tool file format to CGM the vector, line point data must be analyzed and processed algorithmically.
The Native Vector processing involves many processing stages that include text pattern and line pattern algorithms. In addition wire typing algorithms are used to identify circuit types. Finally circuit building algorithms and along with hierarchical capturing algorithms are employed that create the indexed circuit data set. Meaning a data set is created that has captured the circuit component inter-connections and hierarchical component relationships as well as the circuit types.
Diagrams processed by the Native Vector processing stages or diagrams transformed from a CAD tool's wire list move onto the Post Circuit Building Process stages. These set of stages or phases use the data sets created from previous processes to link up circuits across diagrams. From the outputs of the Post Circuit Building Process S1000D wiring modules can be built.
In addition, a good IEWD solution should be capable of associating and managing media or auxiliary data for each circuit and component across all diagrams. Meaning a technician need only click on a hot spotted component label and can bring up images, PDF instructions, videos, etc. Atlas' tool suite provide such a capability.
Another good feature for an IEWD solution is the ability to communicate with other software such as IETMs, 3D simulators, etc. Atlas' P2pViewer can communicate with just about any IETM and 3D simulators on the market today! The tool suite provides management tools that are user friendly and have no need for programming, that will allow a user to set up a communications ability between both the P2pViewer and the external application, 3D simulator or IETM, etc.
Across all phases of the processing QA stages are implemented that insure each phase is correct and accurate. The Atlas tool suite can be configured where different parties are responsible for QA of the resultant diagram outputs from each stage.
Finally once all stages have been completed and passed QA the data sets of inter-linked diagrams, auxiliary media data, external application exchanges and the IEWD viewer can be complied and published for installation to any tablet or laptop with just a click of a button. This kind of user friendly processing removes any need for internal IT support or intuitive know how to any particular hardware or software platform.
From this brief description one can clearly see that the workflow is of a document management process and as such there are inherent advantages from such an approach.
Conclusion:
A repeatable workflow process is neccessary for any IEWD solution for the obivious reasons listed above. What may be of concern to many technical publication organizations is how to provide a competative IEWD solution that is sustainable and attractive to potential clients! Fears by potential clients of costly diagram maintenance because technical publication organizations will only solicit such business if customize software development is included in the contract is no longer warranted with COTS solutions. Effectively, without the need to engineer a solution, an organization wanting to deploy a sustainable wiring diagram solution to a client is possible with a COTS solution such as Atlas' tool suite.
Frank Lombard is the CEO of Atlas Dynamics Corp a leading provider of Interactive Electronic Wiring Diagram production tools.