CN109614143B

CN109614143B - Development method for automatically generating fault flow chart in IETM browser

Info

Publication number: CN109614143B
Application number: CN201811506174.XA
Authority: CN
Inventors: 陈继勋; 龚丹丹; 蒋坚鸿; 王南松
Original assignee: SHANGHAI INSTITUTE OF AEROSPACE INFORMATION; SHANGHAI PRECISION METROLOGY AND TEST RESEARCH INSTITUTE
Current assignee: SHANGHAI INSTITUTE OF AEROSPACE INFORMATION; SHANGHAI PRECISION METROLOGY AND TEST RESEARCH INSTITUTE
Priority date: 2018-12-10
Filing date: 2018-12-10
Publication date: 2022-06-21
Anticipated expiration: 2038-12-10
Also published as: CN109614143A

Abstract

The development method for automatically generating the fault flow chart in the IETM browser comprises the steps of automatically generating the fault flow chart, and dynamically generating the fault flow chart by utilizing preset fault isolation logic and a gfx technology of Dojo; the method comprises the steps of browsing and interacting a fault flow chart, wherein the browsing and interacting of the fault flow chart are realized by using a JS technology; the method comprises fault browsing interaction records and statistical display, wherein the browsing interaction records and the statistical display utilize a database to store browsing interaction records; statistics of browsing interactions are shown using gfx and charting of Dojo.

Description

Development method for automatically generating fault flow chart in IETM browser

Technical Field

The invention relates to the technical field of Interactive Electronic Technical Manuals (IETM), in particular to a development method for automatically generating a fault flow chart in an IETM browser.

Background

The U.S. department of defense at 9 months 1985 proposed a CALS (computer aided logistics support) strategic plan. The meaning of CALS means that the weapon equipment is subjected to life-cycle management and information support, namely, advanced information technologies such as computer network, database, multimedia and digital simulation are comprehensively utilized by all links and relevant units in the life-cycle process of purchasing, dealing, developing, designing, producing, checking, delivering, training and maintaining of a weapon system, information data of the weapon equipment and engineering technology are subjected to digitization, standardization and network integration, and the sharing and reutilization of the information data are improved.

The IETM (interactive electronic technical manual), as an important component of the CALS, is a standardization for digitizing and information exchange of engineering data generated in the works of weapon design, production, use training, maintenance and guarantee, etc.

The IETM currently compiles data modules using standards such as S1000D and GJB6600 and stores the data modules in XML format. And when the fault data module is displayed, providing a guide mode browsing method to gradually display the content of the data module and guide to finish fault isolation.

The existing IETM reading system generally adopts CGM map and other ways to realize the interaction between the fault flow chart and the fault isolation logic. The mode needs to draw the CGM map according to the preset fault isolation logic and then add the CGM map into the data module.

XML (extensible Markup language) extensible Markup language provides a set of rules for converting XML data described by one set of elements into a document described by another set of elements, or even converting the data into a custom text format. XSLT is typically used to transform XML documents into HTML for display in a web browser.

Dojo is an open source DHTML toolkit realized by javascript language, supports internationalization and has four themes: claro, nihilo, soria, tundra. Dojo has high conceptual integrity, can obtain the source code free of charge, and is open source.

The OSWorkflow is an open-source workflow engine completely written by java language, and has the characteristics of remarkable flexibility and complete user facing to the technical background. The present invention utilizes only xml formatted files of OSWorkflow.

Disclosure of Invention

The invention aims to provide a development method for automatically generating a fault flow chart in an IETM browser, which can automatically generate the fault flow chart based on preset fault isolation logic.

In order to achieve the above object, the present invention provides a development method for automatically generating a fault flow chart in an IETM browser, which includes automatically generating a fault flow chart, wherein the fault flow chart automatically generates a fault flow chart dynamically by using preset fault isolation logic and the gfx technology of Dojo.

The above development method for automatically generating a fault flowchart in an IETM browser, wherein the automatically generating of the fault flowchart includes: utilizing an IETM manufacturing platform to manufacture a fault data module and generating a DDN data packet; converting XML data into HTML data by using an XSLT technology, converting a fault step part into XML data in an OSWorkflow form, and corresponding a label of a fault data module to an XML label in the OSWorkflow; and (5) combining the gfx and JS technologies of Dojo, and drawing the xml data into a fault flow chart.

The development method for automatically generating the fault flow chart in the IETM browser further comprises fault flow chart browsing interaction, wherein the fault flow chart browsing interaction is realized by using a JS technology; the fault flow diagram browsing interaction comprises: setting a single-click event for each step when drawing a fault flow chart; the click events include: when clicking the step on the fault flow chart, firstly judging whether the previous step of the step is executed, if so, highlighting the step, restoring other steps to be not executed except the ancestor step of the step, and simultaneously displaying the details of the step through characters in the character step; if not, no action is triggered.

The above development method for automatically generating a fault flow chart in an IETM browser, wherein the single-click event further includes: clicking the link of the text step triggers the same event when clicking the step on the fault flow chart.

The development method for automatically generating the fault flow chart in the IETM browser further comprises fault browsing interaction records and statistical display, wherein the browsing interaction records and the statistical display utilize a database to store the browsing interaction records; and displaying the statistics of browsing interaction by using gfx and charting of Dojo.

The above development method for automatically generating a fault flow chart in an IETM browser, wherein the fault browsing interaction record and statistical presentation include: when the final step of the fault flow is executed, displaying a storage link in the text step, clicking for storage, and storing the browsing interaction record into a database; the IETM browser background counts various browsing interaction records; and displaying the browsing interaction records and the statistical results of various browsing interaction records by using gfx and charting of Dojo.

The method for developing the automatic fault flow chart generation in the IETM browser includes storing the contents in the database, including the converted xml data, the step set after browsing interaction, the data module code and the data module name.

Compared with the prior art, the invention has the beneficial technical effects that:

according to the development method for automatically generating the fault flow chart in the IETM browser, the fault flow chart is automatically generated and can be automatically generated according to the preset fault isolation logic, and if the fault isolation logic is modified, the fault flow chart is automatically regenerated again, so that CGM (computer graphic message) modification can be omitted, and corresponding workload can be reduced; browsing interaction is realized, a user can conveniently check and execute a certain step and check details of the step, and the method is more intuitive; the browsing interaction record is saved, so that the operation trace of a user can be saved and the trace can be traced; the statistical result of browsing the interactive records is displayed by using the histogram, so that the occurrence frequency of certain interactive records can be visually observed, certain interactive operation interaction is less, and the histogram has certain guiding significance for subsequent troubleshooting.

Drawings

The development method for automatically generating the fault flow chart in the IETM browser of the invention is provided by the following embodiments and the attached drawings.

FIG. 1 is a flow chart of automatic generation of a fault flow chart according to a preferred embodiment of the present invention.

FIG. 2 is a flow chart of a fault generated in the preferred embodiment of the present invention.

FIG. 3 is a flow chart of interaction for browsing a fault in a preferred embodiment of the present invention.

FIG. 4 is a diagram illustrating a statistical presentation of trouble shooting interactions in accordance with a preferred embodiment of the present invention.

Detailed Description

The following describes the developing method for automatically generating a fault flow chart in an IETM browser according to the present invention in further detail with reference to fig. 1 to 4.

The development method for automatically generating the fault flow chart in the IETM browser comprises the step of automatically generating the fault flow chart. And the fault flow chart is automatically generated, and the fault flow chart is dynamically generated by utilizing preset fault isolation logic and the gfx technology of Dojo.

FIG. 1 is a flow chart illustrating automatic generation of a fault flow chart according to a preferred embodiment of the present invention.

Referring to fig. 1, the automatic generation of the fault flow diagram includes: utilizing an IETM manufacturing platform to manufacture a fault data module and generating a DDN data packet (the data in the DDN data packet is XML data); converting XML data into HTML data by using an XSLT technology, converting a fault step part into XML data in an OSWorkflow form, and corresponding the label of a fault data module to the XML label in the OSWorkflow; in conjunction with the gfx and JS techniques of Dojo (i.e., JS code written with gfx of Dojo), xml data is plotted as a fault flow chart, as in fig. 2.

And manufacturing a fault data module, namely presetting fault isolation logic.

And issuing the generated DDN data packet by using an IETM issuer, wherein XML data is converted into HTML data in the issuing process, and the fault step part is converted into XML data in the form of OSWorkflow.

The correspondence before and after the conversion of the failure step portion is shown in table 1.

Table 1: correspondence table before and after partial conversion of fault step

And automatically generating a fault flow chart according to preset fault isolation logic, and if the fault isolation logic is modified, automatically modifying the fault flow chart correspondingly.

The development method for automatically generating the fault flow chart in the IETM browser further comprises fault flow chart browsing interaction. And the browsing interaction of the fault flow chart is realized by using a JS technology, and the interactive steps are highlighted.

FIG. 3 is a flow chart of interaction for browsing a fault in a preferred embodiment of the invention.

Referring to fig. 3, the fault flow diagram browsing interaction includes: when drawing the fault flow chart, a single-click event is set for each step. The click events include: when clicking the step on the fault flow chart, firstly judging whether the previous step of the step is executed, if so, highlighting the step, restoring other steps to be not executed except the ancestor step of the step, and simultaneously displaying the details of the step through characters in the character step; if not, no action is triggered. The link to the text step can also be clicked, triggering the same event when clicking the step on the fault flow chart. That is, the single click event can be implemented by clicking on a step on the fault flow chart or clicking on a link of a text step.

The development method for automatically generating the fault flow chart in the IETM browser further comprises fault browsing interaction record and statistical display. The browsing interaction records and the statistical display are realized, and the browsing interaction records are stored by utilizing a database; and displaying the statistics of browsing interaction by using gfx and charting of Dojo.

The fault browsing interaction record and the statistical display comprise: when the final step of the fault flow is executed, a storage link is displayed in the text step, the storage is clicked, the browsing interaction record of the time is stored in a database, and the content stored in the database comprises the converted xml data, the step set after the browsing interaction, the data module code and the data module name; the IETM browser background counts various browsing interaction records; and displaying the browsing interaction records and the statistical results of various browsing interaction records by using gfx and charting of Dojo, as shown in FIG. 4.

By using the development method for automatically generating the fault flow chart in the IETM browser, when a fault data module is read, the equipment can be effectively guided to use and be learned and mastered by maintenance personnel for maintenance and fault diagnosis through the display guidance and interaction of the fault flow chart and corresponding troubleshooting information description (text steps).

Claims

The development method for automatically generating the fault flow chart in the IETM browser is characterized by comprising the steps of automatically generating the fault flow chart, wherein the fault flow chart is automatically generated by utilizing preset fault isolation logic and a gfx technology of Dojo;

the automatic generation of the fault flow diagram comprises: utilizing an IETM manufacturing platform to manufacture a fault data module and generating a DDN data packet, wherein data in the DDN data packet is XML data; converting XML data into HTML data by using an XSLT technology, converting a fault step part into XML data in an OSWorkflow form, and corresponding the label of a fault data module to the XML label in the OSWorkflow; and (5) combining the gfx and JS technologies of Dojo, and drawing the xml data into a fault flow chart.
2. The development method for automatically generating a fault flow graph in an IETM browser according to claim 1, wherein the development method further comprises a fault flow graph browsing interaction, the fault flow graph browsing interaction being implemented with a JS technique;

the fault flow diagram browsing interaction comprises: setting a single-click event for each step when drawing a fault flow chart;

the click events include: when clicking the step on the fault flow chart, firstly judging whether the previous step of the step is executed, if so, highlighting the step, restoring other steps to be not executed except the ancestor step of the step, and simultaneously displaying the details of the step through characters in the character step; if not, no action is triggered.
3. The development method for automatically generating a fault flow graph in an IETM browser of claim 2, wherein the single click event further comprises: clicking the link of the text step triggers the same event when clicking the step on the fault flow chart.
4. The development method for automatically generating fault flow charts in IETM browsers according to claim 2 or 3, wherein the development method further comprises fault browsing interaction records and statistical presentation, said browsing interaction records and statistical presentation utilizing a database to maintain records of browsing interactions; and displaying the statistics of browsing interaction by using gfx and charting of Dojo.
5. The development method for automatically generating fault flow charts in an IETM browser according to claim 4, wherein said fault browsing interaction logging and statistical presentation comprises: when the final step of the fault flow is executed, displaying a storage link in the text step, clicking for storage, and storing the browsing interaction record into a database; the IETM browser background counts various browsing interaction records; and displaying the browsing interaction records and the statistical results of various browsing interaction records by using gfx and charting of Dojo.
6. The development method for automatically generating fault flow charts in IETM browsers according to claim 5, wherein the contents saved to the database include converted xml data, browsing interacted step set, data module code and data module name.