CN112068909A - Nuclear power operation rule mobile execution card generation system and method - Google Patents
Nuclear power operation rule mobile execution card generation system and method Download PDFInfo
- Publication number
- CN112068909A CN112068909A CN202010757081.5A CN202010757081A CN112068909A CN 112068909 A CN112068909 A CN 112068909A CN 202010757081 A CN202010757081 A CN 202010757081A CN 112068909 A CN112068909 A CN 112068909A
- Authority
- CN
- China
- Prior art keywords
- procedure
- attribute
- action
- module
- interface
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 125
- 230000009471 action Effects 0.000 claims abstract description 101
- 238000009877 rendering Methods 0.000 claims abstract description 28
- 238000000354 decomposition reaction Methods 0.000 claims abstract description 24
- 230000003993 interaction Effects 0.000 claims abstract description 7
- 230000002457 bidirectional effect Effects 0.000 claims description 3
- 230000007246 mechanism Effects 0.000 claims description 3
- 238000011161 development Methods 0.000 abstract description 6
- 238000012423 maintenance Methods 0.000 abstract description 3
- 238000004519 manufacturing process Methods 0.000 abstract description 2
- 238000010586 diagram Methods 0.000 description 8
- 238000012360 testing method Methods 0.000 description 6
- 206010063385 Intellectualisation Diseases 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 238000012795 verification Methods 0.000 description 2
- 238000006243 chemical reaction Methods 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000008569 process Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/451—Execution arrangements for user interfaces
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45504—Abstract machines for programme code execution, e.g. Java virtual machine [JVM], interpreters, emulators
- G06F9/45529—Embedded in an application, e.g. JavaScript in a Web browser
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
- G06Q50/06—Energy or water supply
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/54—Indexing scheme relating to G06F9/54
- G06F2209/545—Gui
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/54—Indexing scheme relating to G06F9/54
- G06F2209/549—Remote execution
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Health & Medical Sciences (AREA)
- Economics (AREA)
- Databases & Information Systems (AREA)
- General Health & Medical Sciences (AREA)
- Human Computer Interaction (AREA)
- Public Health (AREA)
- Water Supply & Treatment (AREA)
- Data Mining & Analysis (AREA)
- Human Resources & Organizations (AREA)
- Marketing (AREA)
- Primary Health Care (AREA)
- Strategic Management (AREA)
- Tourism & Hospitality (AREA)
- General Business, Economics & Management (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention relates to the field of nuclear power plant operation regulations, in particular to a system and a method for generating a nuclear power operation regulation mobile execution card. The existing paper regulations can not well apply production operation data, the data can not be deeply mined, the regulations are various and complex, and the maintenance difficulty is high in classified development. The invention comprises a rule action data format defining module, a server side attribute defining and decomposing module and an APP side interface dynamic rendering control module. The method comprises the steps of defining procedure actions, decomposing the attributes of the procedure actions, decomposing the attribute operations, traversing the procedure actions, traversing the attributes of the procedure actions, obtaining the attribute operations of the single procedure actions, performing quadratic weighted decomposition, rendering a VUE interface and performing UI interaction on the rendered interface. The invention completely strips and decouples the data definition on the interface and has higher expandability.
Description
Technical Field
The invention relates to the field of nuclear power plant operation regulations, in particular to a system and a method for generating a nuclear power operation regulation mobile execution card.
Background
With the development of nuclear power digitization and intellectualization, the digitization and intellectualization requirements for nuclear power operation regulations are gradually improved. At present, in the nuclear power industry, a great number of paper edition regulations exist. And carrying out on-site execution by an on-site operator with the paper version document, and finally signing and uploading the executed paper version document. In such a way, precious production operation data cannot be well applied, and data cannot be deeply mined, so that more and more nuclear power plant units expect to electronize regulations. The user can execute the procedure by moving the APP, and when the user can connect to the network, the data is transmitted back.
At present, some projects use mobile APPs, but the content of the projects is not structured, a word file is opened in the APP, procedure content is used as the content of the word file to be edited, and finally an unstructured procedure result is delivered.
If the content of each of the procedures is to be extracted and structured individually and can be presented in a user-friendly manner in the interface, the procedures are classified in a common development manner, and the procedures are developed according to the classification result (each type of procedure develops a set of interfaces). However, the nuclear power station has many types of regulations, and the regulations are complex and not standardized, so that the maintenance difficulty is very high, and the nuclear power station is difficult to implement in the nuclear power industry.
Disclosure of Invention
1. The purpose is as follows:
the invention provides a method for dynamically generating a rule card interface on an APP, which can effectively classify and abstract different and similar rule actions of nuclear power and realize generation of an electronic rule card in a UI interface dynamic rendering mode.
2. The technical scheme is as follows:
a nuclear power operation rule mobile execution card generation system is divided into three modules:
a first module: a rule action data format defining module;
and a second module: a server attribute definition and decomposition module;
and a third module: and the APP terminal interface dynamic rendering control module.
Data sequentially flows between the first module and the third module.
The first module is as follows: and the protocol action data format definition module performs data definition in the system and analyzes each type of action by second power.
The second module: the server attribute definition and decomposition module specifically comprises: defining procedure actions, decomposing the attributes of the procedure actions and decomposing the attribute operations; and the module II is used for decomposing and structuring the actual structure layer by the procedure according to procedures, chapters, actions, attributes and operation modes at the server side.
The third module: the APP terminal interface dynamic rendering control module is responsible for data receiving, deserializes the json character string according to a receiving result, and traverses and analyzes rule actions, action attributes and attribute operations; and according to different types of attribute operations, dynamically rendering the form and the UI layout of the interface on the attributes.
A nuclear power operation procedure mobile execution card generation method specifically comprises the following steps:
the method comprises the following steps: defining a procedure action; step two: decomposing the attribute of the procedure action; step three: attribute operation decomposition; APP end: step four: traversing the procedure action; step five: traversing the procedure action attribute; step six: obtaining the action attribute operation of a single procedure; step seven: quadratic weighted decomposition; step eight: rendering a VUE interface; step nine: rendering the interface UI interaction.
The method comprises the following steps: the protocol action definition specifically comprises the following steps: in a background database, decomposing the actions in the procedures, wherein the action in each procedure corresponds to one card; each protocol action defines its unique identification code and an action title.
Step two: the procedure action attribute decomposition specifically comprises the following steps: defining and storing action attributes owned by each procedure action in a background database; the procedure action attribute only records the content of the interface presentation, but does not define the corresponding operation type of the attribute.
Step three: attribute operation decomposition specifically includes: the action attribute of each procedure has different attribute operations according to the type of the procedure; in the background database, the values of the power-of-2 sum of the attribute operations are recorded, respectively.
Step four: and traversing the procedure action, specifically comprising: the mobile APP end sends a request to webapi to obtain all actions of a certain procedure, and in the client, a plurality of procedure operation cards are generated on the current layout in a mode of loading according to needs through a rendering mechanism of the front end vue.
Step five: the traversal procedure action attribute specifically comprises: the title of each procedure operation card is fixed, but the attribute content is dynamically displayed according to the control type through the procedure content defined by the server; and additionally arranging each control according to two columns in a streaming layout mode, and limiting the width value of each rule attribute to be 50% of the total width in the arrangement mode, so that the interface layout can be neater and more uniform.
Step six: acquiring the action attribute of a single procedure, specifically comprising: and performing operation on the action attributes of the procedure through js operation to obtain an action set of a specific attribute in the procedure attributes.
Step seven: a quadratic weighted decomposition.
Step eight: the VUE interface rendering specifically comprises the following steps: the system dynamically renders the interface data according to the sequence of the logic size by the result of weighted decomposition, and realizes bidirectional data binding.
Step nine: rendering the interface UI interaction.
3. The effect is as follows:
by the method, the data is defined on the interface to be completely stripped and decoupled, and the method has high expandability.
Drawings
FIG. 1 is a schematic diagram of an execution side card mode
FIG. 2 data input schematic
FIG. 3 is a diagram of original input file fragment-operation steps
FIG. 4 is a schematic diagram of a raw input file fragment-trial report
FIG. 5 is a schematic diagram of multiple data inputs
FIG. 6 is a flow chart of a nuclear power operation procedure mobile execution card generation
FIG. 7 is a diagram of relationships between modules
FIG. 8 is a schematic diagram of a digital input
FIG. 9 device authentication diagram
FIG. 10 is a schematic diagram of date type input
Detailed Description
In a nuclear power project, the operation procedures are various, and each type of procedure has various types of actions, such as anti-human tools (including scanning two-dimensional codes, three-way communication, guardianship and the like), signatures, circles (being executed), bars (being completed), numerical values, selection time, selection date, character string contents and the like.
Meanwhile, the number of attribute fields required by the action of each procedure is different, and some procedures have 5 fields, some 7 fields and some 1 field.
This therefore presents great difficulties for the structured development of applications for the protocol.
As in fig. 1, each protocol action contains 6 attribute fields (operation/check, flag, location, expected result, yes, no, description), while in fig. 2 of the same protocol, only 4 fields (test equipment, safety-related system regularly supervises the test outline standard, test record, test result satisfaction).
While the fields and types of all actions may be completely different in the same procedure.
As shown in fig. 1, the flag column 1SAP037VA requires that a code scan verification be performed, whether the column contains "[ ]" requires a check, and the column 009 LP- ___ Mpa requires a padding value. In addition to this, there are various types of anti-human tools. And cross-overlaps between corresponding operations may occur. For example, it is necessary to fill in both time and character string content, or to fill in both signature, value and signature. As shown in FIG. two, one action simultaneously comprises different interactions of text input, whether or not, verification equipment and the like.
In other regulations, the number of corresponding fields and the operations corresponding to the fields are different, so it is necessary to design a regulation card that can generate different action types in the interface according to different rules.
The traditional development mode is as follows: and configuring a set of interfaces according to each type of procedure, and writing corresponding service codes according to the corresponding interfaces.
The regulations of nuclear power projects are large in number, and the codes of each regulation are independently compiled, so that the overall development amount is huge, and the maintenance is difficult.
As shown in FIG. 7, the method is divided into several functional modules according to their functions
1. Rule action data format definition module
2. Server attribute definition and decomposition module
APP end interface dynamic rendering control module
In the technology, the specific technical scheme is as follows:
and a rule action data format definition module is responsible for making data definition in the system, and decomposing each type of action by a power of 2, such as 1, 2, 4, 8, 16 and the like, and decomposing the action by a power of 2, so that a function of combinational logic judgment can be realized by using a smaller storage space in one field. The principle of the attribute combination mode of the power of 2 is as follows:
assume that each bin represents 1 logical control function. We denote 1 as having this function and 0 as not having this function.
The first logical function is 1
The second logical function is 10
The third logic function is 100
The fourth logical function is 1000
…
If each is considered as binary, bits 1-4 are converted to 10 and become 1, 2, 4, and 8, respectively.
If the logic function superposition is performed, the decimal number is 101 if an operation has the 1 st and 3 rd logic functions. In decimal addition, 1+4 is equal to 5. And the conversion of 101 to decimal is also 5 for 2.
In this way, the attribute operation type of the protocol can be defined in an overlapping way, and the method has the capability of being expanded in a horizontal direction (adding new operation definitions) and a vertical direction (one operation defines a plurality of types).
The server attribute definition and decomposition module is responsible for data definition, and the data definition comprises 3 parts: the method comprises the steps of procedure action definition, procedure action attribute decomposition and attribute operation decomposition.
The part is all data bases, and the rules are decomposed according to the actual structure in the server side, and are decomposed and structured layer by layer according to the operation mode of the rules- > chapter- > action- > attribute- > and the operation mode.
And the APP end interface dynamic rendering control module is responsible for receiving data, performing deserialization on the json character string according to a receiving result, and traversing and analyzing rule actions, action attributes and attribute operations. And according to different types of attribute operations, dynamically rendering the form and the interface UI layout for the attributes.
As shown in fig. 6, a method for generating a nuclear power operation procedure mobile execution card includes:
(1) protocol action definition
And decomposing the actions in the procedures in a background database, wherein the actions in each procedure correspond to one card. Each procedure action defines its unique identification code (GUID) and an action title.
(2) Procedure action attribute decomposition
In the background database, the action attribute owned by each procedure action is defined and stored, and each procedure action can have a plurality of action attributes, such as operation, check, identification, whether, test record, test result and the like. The procedure action attribute only records the content of the interface presentation, but does not define the corresponding operation type of the attribute. Such as defining a "if" attribute, but a "if" attribute does not necessarily require a corresponding "if" operation
(3) Attribute operation decomposition
As shown in fig. 6, the action attribute of each procedure may have different attribute operations (possibly one or more) according to its type. In the background database, the values of the power-of-2 sum of the attribute operations are recorded, respectively. If an action attribute operation contains a set of 3 types of operations, sign on, scan on, and if, the system records its attribute value 138 raised to the power of 2. 128, code scan 8, 2, 128+8+2, 138. By the storage mode, the storage complexity can be effectively reduced, and one more data association table is not needed.
(4) Traversal of protocol actions
As shown in fig. 6, the mobile APP side obtains all actions of a certain procedure by sending a request to webapi, and in the client side, a plurality of procedure operation cards are generated in the current layout in an on-demand loading manner through a rendering mechanism of the front end vue.
(5) Traversal procedure action attributes
The title of each procedure operation card is fixed, but the attribute content is dynamically displayed according to the control type through the procedure content defined by the server. Each control is additionally arranged according to 2 columns in a streaming layout mode, and the width value of each rule attribute is limited to 50% of the total width in the arrangement mode, so that the interface layout can be neatly and uniformly arranged.
(6) Obtaining single procedure action attributes
And performing operation on the action attributes of the procedure through js operation to obtain an action set of a specific attribute in the procedure attributes.
(7) Power 2 weighted decomposition
If the attribute operation set value 138 of a certain action attribute is obtained in the previous step, it can be decomposed into 128+8+ 2. It means that the attribute operation for the action attribute is "sign on" (128), "sweep code"
(8) And "No" (2).
(8) Vue interface rendering
The system dynamically renders the interface data according to the sequence of the logic size by the result obtained by weighted decomposition, and realizes bidirectional data binding, and if the attribute operation is 'signed', the system renders the interface data into a canvas.
Aiming at the attribute operation of code scanning, the system renders a button icon of a two-dimensional code scanning;
aiming at the ' whether ' attribute, the interface is rendered into a ' switch component, and the component is defaulted as not selected;
aiming at the read-only attribute operation, the interface does not carry out any operation and only carries out rendering according to the text character string;
aiming at the attribute operation of the Date, the interface is rendered into a Date type control, and the user is required to input the year, month and day;
the user does the process according to the Time attribute, the interface is rendered into a Time type control, and the user is required to input Time;
aiming at the 'digital' attribute operation, rendering the interface into a text box;
and aiming at the attribute operation of the character string, rendering the interface into a text box.
(9) Rendering interface UI interactions according to attribute operations
As shown in fig. 8, 9, 10, different UI interactions are required for different types of operations.
If the attribute operation is 'sign on', the system renders a canvas, and when the user clicks the canvas, the canvas can be popped up, and the mobile terminal tablet signature is performed on the canvas content. And the online signature effect is realized, and when the user repeatedly clicks the canvas, the signature can be supplemented in the signature.
Aiming at the attribute operation of code scanning, the system renders a button icon of a two-dimensional code scanning, a user starts a code scanning function when clicking the code scanning icon, and after the code scanning method is finished, a code scanning result is filled in a current action attribute field.
And aiming at the ' no ' attribute, the interface is rendered into a ' switch component, and the component is defaulted to be not selected. Whether the attributes must be filled, the user must select one of yes or no.
And aiming at the read-only attribute operation, the interface does not carry out any operation and is only rendered according to the text character string.
For the "Date" attribute operation, the interface is rendered as a Date type control, requiring the user to enter the year, month and day, the system uses the time control of year, month and day, and is spaced by a "-" separator.
The "Time" property is only done, the interface is rendered as a Time type control, requiring the user to enter Time and be spaced by a "-" separator.
For the "numeric" attribute operation, the interface is rendered as a text box and a mask layer pops up, the numeric operation of the "keypad" pops up, and the app-side keyboard event is disabled.
And aiming at the attribute operation of the character string, rendering the interface into a text box, and using a standard mobile terminal keyboard event.
Claims (10)
1. A nuclear power operation rule mobile execution card generation system is characterized in that: the method is divided into three modules: a first module: a rule action data format defining module; and a second module: a server attribute definition and decomposition module; and a third module: an APP terminal interface dynamic rendering control module; data sequentially flows between the first module and the third module.
2. The nuclear power operation procedure mobile execution card generation system of claim 1, characterized in that: the first module is as follows: and the protocol action data format definition module performs data definition in the system and analyzes each type of action by second power.
3. The nuclear power operation procedure mobile execution card generation system of claim 1, characterized in that: the second module: the server attribute definition and decomposition module specifically comprises: defining procedure actions, decomposing the attributes of the procedure actions and decomposing the attribute operations; and the module II is used for decomposing and structuring the actual structure layer by the procedure according to procedures, chapters, actions, attributes and operation modes at the server side.
4. The nuclear power operation procedure mobile execution card generation system of claim 1, characterized in that: the third module: the APP terminal interface dynamic rendering control module is responsible for data receiving, deserializes the json character string according to a receiving result, and traverses and analyzes rule actions, action attributes and attribute operations; and according to different types of attribute operations, dynamically rendering the form and the UI layout of the interface on the attributes.
5. A nuclear power operation rule mobile execution card generation method is characterized by comprising the following steps: the method comprises the following steps: the server side: the method comprises the following steps: defining a procedure action; step two: decomposing the attribute of the procedure action; step three: attribute operation decomposition; APP end: step four: traversing the procedure action; step five: traversing the procedure action attribute; step six: obtaining the action attribute operation of a single procedure; step seven: quadratic weighted decomposition; step eight: rendering a VUE interface; step nine: rendering the interface UI interaction.
6. The nuclear power operation procedure mobile execution card generation method according to claim 5, characterized in that: the method comprises the following steps: the protocol action definition specifically comprises the following steps: in a background database, decomposing the actions in the procedures, wherein the action in each procedure corresponds to one card; each procedure action defines its unique identification code and action title;
step two: the procedure action attribute decomposition specifically comprises the following steps: defining and storing action attributes owned by each procedure action in a background database; the procedure action attribute only records the content presented by the interface, but does not define the corresponding operation type of the attribute;
step three: attribute operation decomposition specifically includes: the action attribute of each procedure has different attribute operations according to the type of the procedure; in the background database, the values of the power-of-2 sum of the attribute operations are recorded, respectively.
7. The nuclear power operation procedure mobile execution card generation method according to claim 5, characterized in that: step four: and traversing the procedure action, specifically comprising: the mobile APP end sends a request to webapi to obtain all actions of a certain procedure, and in the client, a plurality of procedure operation cards are generated on the current layout in a mode of loading according to needs through a rendering mechanism of the front end vue.
8. The nuclear power operation procedure mobile execution card generation method according to claim 5, characterized in that: step five: the traversal procedure action attribute specifically comprises: the title of each procedure operation card is fixed, but the attribute content is dynamically displayed according to the control type through the procedure content defined by the server; and additionally arranging each control according to two columns in a streaming layout mode, and limiting the width value of each rule attribute to be 50% of the total width in the arrangement mode, so that the interface layout can be neater and more uniform.
9. The nuclear power operation procedure mobile execution card generation method according to claim 5, characterized in that: step six: acquiring the action attribute of a single procedure, specifically comprising: and performing operation on the action attributes of the procedure through js operation to obtain an action set of a specific attribute in the procedure attributes.
10. The nuclear power operation procedure mobile execution card generation method according to claim 5, characterized in that: step eight: the VUE interface rendering specifically comprises the following steps: the system dynamically renders the interface data according to the sequence of the logic size by the result of weighted decomposition, and realizes bidirectional data binding.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010757081.5A CN112068909B (en) | 2020-07-31 | 2020-07-31 | Nuclear power operation rule mobile execution card generation system and method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010757081.5A CN112068909B (en) | 2020-07-31 | 2020-07-31 | Nuclear power operation rule mobile execution card generation system and method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112068909A true CN112068909A (en) | 2020-12-11 |
| CN112068909B CN112068909B (en) | 2023-10-20 |
Family
ID=73657200
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010757081.5A Active CN112068909B (en) | 2020-07-31 | 2020-07-31 | Nuclear power operation rule mobile execution card generation system and method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112068909B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2004030055A (en) * | 2002-06-24 | 2004-01-29 | Nippon Telegr & Teleph Corp <Ntt> | Ic card control application |
| KR20120020859A (en) * | 2010-08-31 | 2012-03-08 | 주식회사 포스코아이씨티 | Apparatus for controlling nuclear power generation and method for updating data of that apparatus |
| CN102929598A (en) * | 2012-09-25 | 2013-02-13 | 中国核电工程有限公司 | Man-machine interface design method for improving safety of nuclear power station |
| CN103810090A (en) * | 2012-11-12 | 2014-05-21 | 中国广东核电集团有限公司 | Nuclear power station digital regulation installing, debugging and verifying method and nuclear power station digital regulation version upgrading method and platform |
| US20150012905A1 (en) * | 2013-07-02 | 2015-01-08 | Andrew T. Emmons | System and method for streamlining user interface development |
-
2020
- 2020-07-31 CN CN202010757081.5A patent/CN112068909B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2004030055A (en) * | 2002-06-24 | 2004-01-29 | Nippon Telegr & Teleph Corp <Ntt> | Ic card control application |
| KR20120020859A (en) * | 2010-08-31 | 2012-03-08 | 주식회사 포스코아이씨티 | Apparatus for controlling nuclear power generation and method for updating data of that apparatus |
| CN102929598A (en) * | 2012-09-25 | 2013-02-13 | 中国核电工程有限公司 | Man-machine interface design method for improving safety of nuclear power station |
| CN103810090A (en) * | 2012-11-12 | 2014-05-21 | 中国广东核电集团有限公司 | Nuclear power station digital regulation installing, debugging and verifying method and nuclear power station digital regulation version upgrading method and platform |
| US20150012905A1 (en) * | 2013-07-02 | 2015-01-08 | Andrew T. Emmons | System and method for streamlining user interface development |
Non-Patent Citations (1)
| Title |
|---|
| 尹继超;张轶婷;向俊瑛;: "核电站数字化规程导入方式和方法研究", 科技传播, no. 07 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112068909B (en) | 2023-10-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111625226B (en) | Prototype-based man-machine interaction design implementation method and system | |
| CN112835560A (en) | WEB multi-terminal low-code intelligent software development platform | |
| KR102038092B1 (en) | Apparatus and Method for automatic generation of Electric Design Drawings | |
| CN105204860B (en) | A kind of method and device for quickly generating self-defined static Web pages | |
| CN110543303B (en) | Visual service platform | |
| CN102209963A (en) | Automatic designation of footnotes to fact data | |
| CN102870108A (en) | Method of generating electronic report | |
| CN103455338A (en) | Method and device for acquiring data | |
| US9501462B2 (en) | Form object having form representation and grid representation of form | |
| CN111859053B (en) | Data definition method of visual chart and chart library system | |
| CN107577460A (en) | A kind of method from unstructured data extraction structural data | |
| CN115495069A (en) | Model-driven coal industry software flow implementation method, device and equipment | |
| CN112068909A (en) | Nuclear power operation rule mobile execution card generation system and method | |
| JP2016173721A (en) | Information processing device, control method of information processing device, and program | |
| CN106527840A (en) | Method and device for controlling distributed server | |
| CN111368387B (en) | Electric power system simulation data textualization method | |
| CN114281797A (en) | Method for quickly creating basic level data aggregation warehouse based on agile low-code platform | |
| CN109597845B (en) | Report configuration method, report configuration device, computer equipment and storage medium | |
| CN111324646A (en) | Policy information importing and analyzing method based on dynamic mapping | |
| CN113703638A (en) | Data management page processing method and device, electronic equipment and storage medium | |
| CN113626029A (en) | Data processing method and system for dynamically generating page | |
| CN103577560A (en) | Method and device for inputting data base operating instructions | |
| CN114780084B (en) | Configuration system for collaborative multi-type interactive interface design | |
| CN106570114A (en) | Production method and system for rapidly customizing editable web form | |
| CN115357502A (en) | Server interface testing method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |