CN107766521A - A kind of method of Electric Power Network Planning versions of data control - Google Patents
A kind of method of Electric Power Network Planning versions of data control Download PDFInfo
- Publication number
- CN107766521A CN107766521A CN201711006395.6A CN201711006395A CN107766521A CN 107766521 A CN107766521 A CN 107766521A CN 201711006395 A CN201711006395 A CN 201711006395A CN 107766521 A CN107766521 A CN 107766521A
- Authority
- CN
- China
- Prior art keywords
- data
- data warehouse
- versions
- record
- electric power
- 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 46
- 238000012217 deletion Methods 0.000 claims description 11
- 230000037430 deletion Effects 0.000 claims description 11
- 238000012986 modification Methods 0.000 claims description 11
- 230000004048 modification Effects 0.000 claims description 11
- 239000000284 extract Substances 0.000 claims description 6
- 238000000605 extraction Methods 0.000 claims description 6
- 230000001360 synchronised effect Effects 0.000 claims description 6
- 230000004075 alteration Effects 0.000 abstract description 2
- 238000013461 design Methods 0.000 description 20
- 238000006243 chemical reaction Methods 0.000 description 3
- 238000010586 diagram Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 238000007726 management method Methods 0.000 description 3
- 230000015572 biosynthetic process Effects 0.000 description 2
- 238000013499 data model Methods 0.000 description 2
- 239000000203 mixture Substances 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 238000007596 consolidation process Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 235000013399 edible fruits Nutrition 0.000 description 1
- 230000002688 persistence Effects 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 230000000630 rising effect Effects 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
Classifications
-
- 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/22—Indexing; Data structures therefor; Storage structures
-
- 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/21—Design, administration or maintenance of databases
- G06F16/219—Managing data history or versioning
-
- 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/23—Updating
-
- 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/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- 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/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/283—Multi-dimensional databases or data warehouses, e.g. MOLAP or ROLAP
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- General Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Health & Medical Sciences (AREA)
- Economics (AREA)
- Human Resources & Organizations (AREA)
- Computing Systems (AREA)
- Public Health (AREA)
- Water Supply & Treatment (AREA)
- General Health & Medical Sciences (AREA)
- Software Systems (AREA)
- Marketing (AREA)
- Primary Health Care (AREA)
- Strategic Management (AREA)
- Tourism & Hospitality (AREA)
- General Business, Economics & Management (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The present invention relates to Electric Power Network Planning informatization, discloses a kind of method of Electric Power Network Planning versions of data control.Including procedure below：Step 1, the Database Modeling of Electric Power Network Planning data is carried out；Step 2, database access interface is kidnapped, records all data change daily records；Step 3, data changed content agreement step 4 is carried out, agreement content is submitted into local data warehouse forms version；Step 5, carry out version with central data warehouse to compare, determine synchronizing content；Step 6, central data warehouse and the difference section of data in local data warehouse are merged, solving conflict if any data collision forms redaction, is back to step 6, enters in next step if without data collision；Step 7, the difference section of local data warehouse and central data warehouse is submitted, completes the shared of versions of data.This programme is able to record all alterations of Electric Power Network Planning data, and traces back in any old version, additionally it is possible to realizes that the versions of data between more people merges.
Description
Technical field
The present invention relates to Electric Power Network Planning informationization technology field, particularly a kind of side of Electric Power Network Planning versions of data control
Method.
Background technology
Among the factor for restricting Electric Power Network Planning efficiency, the data collaborative problem between different planning personnels, also in very great Cheng
The efficiency of planning is have impact on degree.In conventional data collaborative business, generally require to convene the planning people of multiple units
Member is brought together, and compares design data line by line, carries out a large amount of careful patient work, can just obtain a achievement merged
Thing data.A kind of method of new layout data Version Control how is invented, realizes that the version management version collaboration of automation takes
For traditional artificial data Version Control mode, the efficiency of planning can be obviously lifted, while is also power network rule
Draw the hot issue of informatization.
Rational layout data edition control method, it should can either meet the needs of local version management, can also prop up
Support the data collaborative between more people.Submission and backtracking can be realized：Result of design and engineering document are stored as one and gone through by support
History version, user can be according to needing which data between checking different editions are changed, and can also be traced back to a certain
In individual indicated release.Also push can be realized with merging：Support to compare the data difference between the machine and other designers,
Native data is pushed to other people, his personal data is merged into the machine, Conflicts management strategy is supported in the place for data collision occur.
It is final to realize, simple push is only needed between planning personnel and downloads two operations, it becomes possible to accurate data collaborative is realized,
This workload that will fundamentally save data collaborative and bring.
So the method for research Electric Power Network Planning versions of data control, the development for Electric Power Network Planning technology have important meaning
Justice.
The content of the invention
The technical problems to be solved by the invention are：For above-mentioned problem, there is provided a kind of Electric Power Network Planning data version
The method of this control.
The technical solution adopted by the present invention is as follows：A kind of method of Electric Power Network Planning versions of data control, is specifically included following
Process：
Step 1, the Database Modeling of Electric Power Network Planning data is carried out；
Step 2, database access interface is kidnapped, records all data change daily records；
Step 3, data changed content agreement is carried out；
Step 4, agreement content is submitted to local data warehouse and forms version；
Step 5, carry out version with central data warehouse to compare, determine synchronizing content；
Step 6, merge central data warehouse and the difference section of data in local data warehouse, solved if any data collision
Conflict forms redaction, is back to step 6, enters in next step if without data collision；
Step 7, the difference section of local data warehouse and central data warehouse is submitted, completes the shared of versions of data.
Further, in the step 2, all data change daily records are recorded, data change type includes：
A. table addition daily record；
B. table Update log；
C. table deletes daily record；
D. field addition daily record；
E. field Update log；
F. field deletes daily record；
G. record addition daily record；
H. Update log is recorded；
I. record deletion daily record.
Further, in order to ensure the record of addition occurs without double sign, compiled in record addition daily record in the g of the step 2
System creates 16 unique No. Id algorithms, and described No. Id includes：Time, sequence second, sequence millisecond, random sequence.
Further, the data changed content agreement in the step 3, specifically records number using a character string
According to change, data change sequence is supported to turn to character string；Also character string is supported to be deserialized as data change, data change and word
The basis of lossless bi-directional conversion composition data versioned and data exchange between symbol string.
Further, the data changed content agreement of the step 3, the data field type bag that agreementization can act on
Contain：Boolean type；Character type；Numeric type；Time type, not comprising byte types and multimedia type.
Further, the step 4 specifically includes procedure below：
Step 41. checks the data of this time modification；
Step 42. is abandoned modification and restored to the original state；
Step 43. is submitted to local data warehouse and generates redaction.
Further, the step 43 includes procedure below：
Step 431. increases the data for being submitted to local data warehouse newly version number；
Step 432. addition version is detailed；
Step 433. deletes change daily record；
Step 434. changes version present situation.
Further, the step 5 specifically includes procedure below：
Step 51. extraction local data warehouse edition tree；
Step 52. extracts central data warehouse edition tree；
The single table of step 53. performs version alignment operation；
After step 54. alignment, be more than local data warehouse if there is central data warehouse version, then it is exactly to be synchronized
Content.
Further, the step 6 specifically includes procedure below：
Step 61. central data warehouse carries out version contrast with local data warehouse, only synchronous central data warehouse change
Partial data；
Step 62. data to be changed beat packet, if a record occurs repeatedly becoming more versions, can only take here
Newest one；
Step 63. compares with existing record one by one, judges whether data conflict；
Step 64. under conflict situations, the data in modification local data warehouse, does not form redaction, merged successfully；
Step 65. has under conflict situations, first solves conflict, merges failure.
Further, the conflict type in the step 63 includes：
(1) deletion table runs into any table data change；
(2) table is all with the addition of, but field is inconsistent；
(3) different type field of the same name is added；
(4) modification field runs into deletion field；
(5) addition records with id；
(6) addition record while identical id are recorded existing；
(7) the same attribute of same record is changed；
(8) deletion record runs into reference record.
Further, the step 7 specifically includes procedure below：
Step 71. performs data and merged successfully, it is determined that without the data that can more merge from central data warehouse；
Step 72. extraction local data warehouse edition tree, extracts central data warehouse edition tree, performs version alignment behaviour
Make, find out the difference section of local data warehouse and central data warehouse, that is, find out the incremental data bag for needing to submit；
Step 73. promotes incremental data bag to central data warehouse；
Step 74. forms new versions of data in central data warehouse, and versions of data is shared a success and terminated.
In summary, by adopting the above-described technical solution, the beneficial effects of the invention are as follows：It is able to record that power network is advised first
All trickle alterations of data are drawn, the increment of individual can be carried out by submitting redaction or abandoning current change
The design work of formula；Secondly can rollback trace back among any one old version, it is ensured that all previous submission can be effective
Record；It can finally realize that the versions of data between more people merges, complete data exchange, clash handle, be finally reached
The target of team's collaborative design.
Brief description of the drawings
Examples of the present invention will be described by way of reference to the accompanying drawings, wherein：
The schematic flow sheet of the method for Fig. 1 Electric Power Network Planning versions of data controls of the present invention.
Fig. 2 electric network database data model schematic diagrames of the present invention.
Embodiment
All features disclosed in this specification, or disclosed all methods or during the step of, except mutually exclusive
Feature and/or step beyond, can combine in any way.
Any feature disclosed in this specification, unless specifically stated otherwise, can be equivalent by other or with similar purpose
Alternative features are replaced.I.e., unless specifically stated otherwise, each feature is an example in a series of equivalent or similar characteristics
.
As shown in figure 1, a kind of method of Electric Power Network Planning versions of data control, specifically includes procedure below：Step 1, carry out
The Database Modeling of Electric Power Network Planning data；Step 2, database access interface is kidnapped, records all data change daily records；Step 3,
Carry out data changed content agreement；Step 4, agreement content is submitted to local data warehouse and forms version；Step 5, with
Central data warehouse carries out version comparison, determines synchronizing content；Step 6, merge in central data warehouse and local data warehouse
The difference section of data, solve conflict if any data collision and form redaction, step 6 is back to, if without data collision
Into in next step；Step 7, the difference section of local data warehouse and central data warehouse is submitted, completes the shared of versions of data.
In the modeling process of database, data storage is divided into following 3 parts：(1) personal work catalogue, if realizing
The storage of the data base system of dry Electric Power Network Planning data, i.e., most conventional data persistence mode；(2) personal data warehouse, realize
The storage of all versions of data of the machine and change detail, the program results data editted is submitted in local data warehouse,
Local data warehouse is able to record the detailed history situation submitted every time, and designer can perform submission in off-line case
Power planning result of design, revocation last time power planning result of design, abandon the operation such as this editor；C. central data warehouse,
The storage of whole team versions of data and change detail is realized, power planning result of design newest in local data warehouse is existed
Uploaded under ray mode in central data warehouse, and download and merge the power planning that other people are uploaded in central data warehouse and set
Achievement is counted, realizes multi-person synergy editor.
It is illustrated in figure 2 electric network database data model schematic diagram, the key element that the Electric Power Network Planning equipment of database includes
There are power station, circuit, current conversion station, transformer station, switchyard, string to mend station.Electric Power Network Planning data are all realized that database is built first
Mould, model establish after database in include following data content：(1) geographical wiring diagram；(2) line chart component card
Piece；(3) conceptual design result.If table 1 below is electric network database, conceptual design database, the mark of BPA databases and main
Content.
Table 1
Preferably, in the step 2, all data change daily records are recorded, data change type includes：A. table addition day
Will；B. table Update log；C. table deletes daily record；D. field addition daily record；E. field Update log；F. field deletes daily record；g.
Record addition daily record；H. Update log is recorded；I. record deletion daily record.All Electric Power Network Planning data are assigned on the basis of daily record
Following cognizable state is given, it is as shown in table 2 below.
Table 2
Preferably, in the g of the step 2 in record addition daily record, in order to ensure the record of addition occurs without double sign, establishment
The algorithm in 16 unique No. Id of the whole world is created, described No. Id includes：In the time, 2 are accounted for, take latter two in thousand, such as 2017
Take 17；The sequence second, account for 8, current time is which in 1 year second；Sequence millisecond, 4 are accounted for, current time is in one second
Which millisecond；Random sequence, 2 are accounted for, is randomly generated.According to the algorithm of above-mentioned No. Id, caused concrete instance is such as
“1718710533744796”.If all Data Elements use this unique Id algorithm, it can be ensured that more people's multi versions
In the case of, occur without Id conflicts.
Preferably, the data changed content agreement in the step 3, specifically using a character string come record data
Change.Support data change sequence to turn to character string, also support character string to be deserialized as data change, data change and character
The basis of lossless bi-directional conversion composition data versioned and data exchange between string.The coded system of serial protocol includes：a.
" 86HF_ " forces head；B. table name；C. unique Id；D. follow-up field, such as such as one record of table 3 below：
Table 3
| NO. | Field name | Value |
| 1 | id | 1718995745881200 |
| 2 | parent_domain_id | 1 |
| 3 | field0 | 2 |
| 4 | field1 | 3 |
| 5 | field2 | 0.4 |
| 6 | … | … |
Final agreement is：
86HF_git_demo_table,id,id,1718995745881200,parent_domain_id,1,field0,
2,field1,3,field2,0.4,field3,2.5,field4,StringField,field5,2015-01-01,
field6,&true,field7,7&comma7,field8,&false,field9,1,field10,2,field11,3,
field12,4,field13,5,field14,2015-01-01 00:00:00#。
Preferably, the data changed content agreement of the step 3, the data field type that agreementization can act on include：
Boolean type；Character type；Numeric type；Time type, not comprising byte types and multimedia type.
Preferably, agreement content is submitted to the process of local data warehouse formation version by the step 4, specifically includes
Following steps：Step 41. checks the data of this time modification；Step 42. is abandoned modification and restored to the original state；Step 43. is submitted to local
Data warehouse simultaneously generates redaction.Such as：Need to increase the 220KV feeder lines in new province, result version is kept in after addition
In local data warehouse；Or mistake delete Stall transformer station, it is necessary to which lossless from local data warehouse give for change.
Preferably, local data warehouse is submitted in the step 43 and generates the process of redaction and is comprised the following steps：
Step 431. increases the data for being submitted to local data warehouse newly version number；Step 432. addition version is detailed；Step 433. is deleted
Except change daily record；Step 434. changes version present situation.Wherein version number belongs to set membership with version detail, some version pair
Some version details are answered, for example with the addition of 2 transformer stations and 1 circuit, submit one version of generation.Wherein version is detailed
Structure is as follows：
| Name | Type | Length | Decimal point |
| detail_id | bigint | 20 | 0 |
| parent_log_id | bigint | 20 | 0 |
| table_name | varchar | 80 | 0 |
| opr_type | smallint | 6 | 0 |
| row_id | bigint | 20 | 0 |
| old_row_data | longtext | 0 | 0 |
| new_row_data | longtext | 0 | 0 |
Wherein record and stored inside the front and rear field " old_row_data " of wall scroll record change and " new_row_data "
Be exactly before data object after the agreement stated.
Preferably, the step 5 specifically includes procedure below：Step 51. extraction local data warehouse edition tree；Step
52. extract central data warehouse edition tree；The single table of step 53. performs version alignment operation；After step 54. alignment, if there is
Central data warehouse version is more than local data warehouse, then is exactly content to be synchronized.
Preferably, the step 6 specifically includes procedure below：Step 61. central data warehouse is entered with local data warehouse
Row version contrasts, only the partial data of synchronous central data warehouse change；Step 62. data to be changed beat packet, if one
Bar record occurs repeatedly becoming more versions, only can take newest one here；Step 63. compares with existing record one by one, sentences
Whether disconnected data conflict；Step 64. under conflict situations, the data in modification local data warehouse, does not form redaction, is merged into
Work(；Step 65. has under conflict situations, first solves conflict, merges failure.As in actual implement, the most frequently used two operate it
One, from central data warehouse downloading data, and it is automatically incorporated into local data warehouse and design personal work catalogue, comprising such as
Lower algorithmic rule：(1) if certain factor kind is not edited locally, it is consistent automatically with central data warehouse；(2) if certain
Factor kind is local compiled, then carries out the contrast of single pel, and the pel locally edited retains, what other designers edited
Pel is automatically incorporated into the machine；(3) if certain single pel is local and other designers edited, system is provided and carried automatically
Show, be to retain local or retain other designers；(4), will be in local formation after all merging and Conflict solving
New versions of data, automatic covering design working directory；(5) if accidental damage occurs in local data, this behaviour can be utilized
Make, the partial data of accidental damage is given for change and repaired；(6) under the support of pull orders, power planning result of design will not
Because the accidental causes such as hardware fault are lost, in any case, designer can give the rule of oneself for change by pull orders
Draw performance data.
Preferably, such as occurs the conflict type of following situation in the step 63, it is believed that be data collision：(1) table is deleted
Run into any table data change；(2) table is all with the addition of, but field is inconsistent；(3) different type field of the same name is added；(4) change
Field runs into deletion field；(5) addition records with id；(6) addition record while identical id are recorded existing；(7) change same
The same attribute of bar record；(8) deletion record runs into reference record.
Preferably, the step 7 specifically includes procedure below：Step 71. performs data and merged successfully, it is determined that without more
The data that can merge from central data warehouse；Step 72. extraction local data warehouse edition tree, extracts central data warehouse version
This tree, version alignment operation is performed, finds out the difference section of local data warehouse and central data warehouse, that is, finding out needs to submit
Incremental data bag；Step 73. promotes incremental data bag to central data warehouse；Step 74. is formed newly in central data warehouse
Versions of data, versions of data shares a success and terminates.As in actual implement, one of the most frequently used two operations, the machine
The power planning result of design editted, keeps in local data warehouse, by contrast, after merging, uploads to middle calculation
According in warehouse, shared for all designers, include following algorithmic rule：(1) before uploading, pull operations can be carried out automatically,
Ensure push establish with the data comparison of central data warehouse latest edition on；(2), can be in local data storehouse before uploading
In storehouse, the automatic test merged with Conflict solving is first carried out, central server is just submitted to after confirmation is errorless, it is ensured that data merge
Risk be isolated in local data warehouse, central data warehouse will not be spread to, the machine is not interfered with yet and set
The data of meter；(3) designer can frequently by the interim power planning result of design of oneself, (1 is small by push orders
When, half a day) central data warehouse is uploaded to, it can either ensure that power planning result of design is shared, and can ensures certainly well
Oneself power planning result of design is backed up in central data warehouse.
One of embodiment：
The Electric Power Network Planning carried out next 5 years is saved for southwest A, it is special according to one, each prefecture-level city region of the province
The configuration of duty planning personnel carrys out dispensing work.Controlled always using traditional file-type versions of data over the years because A is saved, it is different
Province, can not respectively there are a set of independent data under time, Feng great, withered big, rich small, withered small mode.Failing to realize automation
Versions of data control, each region be respectively completed planning after, it is necessary to devote a tremendous amount of time to handle trans-regional be formulated for
Fruit data consolidation problem, once hand mistake, the data that have modified other region of mistake occurs in someone, whole team needs to expend huge
Big energy goes to compare line by line, finds out the part of these planning conflicts.It is clear that failing to realize the versions of data automated
Under conditions of control, the number increase of collaborative design, the cost of data collaborative is in the rising of geometric progression, this Cooperation Cost
Increase is to restrict Electric Power Network Planning industry not carrying out the main the very crux of large-scale cooperative design.
The method controlled using Electric Power Network Planning versions of data, realize the data collaborative of automation, any one power network rule
The personnel of drawing can be divided into whole process several stages, and each stage submits a versions of data, and version is with the side of increment
Formula is stored in local data warehouse.Electric Power Network Planning personnel can carry out daily design work under the support of version, can be with
Version is formed, abandon edit segment according to needing selection to be submitted to local data warehouse and return to a nearest version, check
Or roll back on the old version specified.
Under the support in native data warehouse, the data merging and data sharing of automation can be realized between more people.Close
And centre data and the difference section of the machine.All planning personnels can be operated by simple pull and push is operated, branch
The renewal of frequently data, merging, submission and the Conflict solving of team's property are held, the online data for completing whole team is synchronously assisted
Together, finally technical foundation is established for the large-scale team's collaborative design of Electric Power Network Planning industry.
The invention is not limited in foregoing embodiment.The present invention, which expands to, any in this manual to be disclosed
New feature or any new combination, and disclose any new method or process the step of or any new combination.
Claims (10)
- A kind of 1. method of Electric Power Network Planning versions of data control, it is characterised in that including procedure below：Step 1, the Database Modeling of Electric Power Network Planning data is carried out；Step 2, database access interface is kidnapped, records all data change daily records；Step 3, data changed content agreement is carried out；Step 4, agreement content is submitted to local data warehouse and forms version；Step 5, carry out version with central data warehouse to compare, determine synchronizing content；Step 6, merge central data warehouse and the difference section of data in local data warehouse, solve to conflict if any data collision Redaction is formed, is back to step 6, is entered in next step if without data collision；Step 7, the difference section of local data warehouse and central data warehouse is submitted, completes the shared of versions of data.
- 2. the method for Electric Power Network Planning versions of data control as claimed in claim 1, it is characterised in that in the step 2, record All data change daily record, and data change type includes：A. table addition daily record；B. table Update log；C. table deletes daily record；D. field addition daily record；E. field Update log；F. field deletes daily record；G. record addition daily record；H. Update log is recorded；I. record deletion daily record.
- 3. the method for Electric Power Network Planning versions of data control as claimed in claim 2, it is characterised in that remember in the g of the step 2 In record addition daily record, in order to ensure the record of addition occurs without double sign, work out and create 16 unique No. Id algorithms, described No. Id Including：Time, sequence second, sequence millisecond, random sequence.
- 4. the method for Electric Power Network Planning versions of data control as claimed in claim 1, it is characterised in that the number in the step 3 According to changed content agreement, specifically changed using a character string come record data, support data change sequence to turn to character String；The data field type that agreementization can act on includes：Boolean type；Character type；Numeric type；Time type, not comprising byte types and Multimedia type.
- 5. the method for Electric Power Network Planning versions of data control as claimed in claim 1, it is characterised in that the step 4 is specifically wrapped Include procedure below：Step 41. checks the data of this time modification；Step 42. is abandoned modification and restored to the original state；Step 43. is submitted to local data warehouse and generates redaction.
- 6. the method for Electric Power Network Planning versions of data control as claimed in claim 5, it is characterised in that the step 43 includes Procedure below：Step 431. increases the data for being submitted to local data warehouse newly version number；Step 432. addition version is detailed；Step 433. deletes change daily record；Step 434. changes version present situation.
- 7. the method for Electric Power Network Planning versions of data control as claimed in claim 1, it is characterised in that the step 5 is specifically wrapped Include procedure below：Step 51. extraction local data warehouse edition tree；Step 52. extracts central data warehouse edition tree；The single table of step 53. performs version alignment operation；After step 54. alignment, it is more than local data warehouse if there is central data warehouse version, then is exactly to be synchronized interior Hold.
- 8. the method for Electric Power Network Planning versions of data control as claimed in claim 1, it is characterised in that the step 6 is specifically wrapped Include procedure below：Step 61. central data warehouse carries out version contrast with local data warehouse, only the portion of synchronous central data warehouse change Divided data；Step 62. data to be changed beat packet, if a record occurs repeatedly becoming more versions, can only take here newest One；Step 63. compares with existing record one by one, judges whether data conflict；Step 64. under conflict situations, the data in modification local data warehouse, does not form redaction, merged successfully；Step 65. has under conflict situations, first solves conflict, merges failure.
- 9. the method for Electric Power Network Planning versions of data control as claimed in claim 8, it is characterised in that rushing in the step 63 Prominent type includes：(1) deletion table runs into any table data change；(2) table is all with the addition of, but field is inconsistent；(3) different type field of the same name is added；(4) modification field runs into deletion field；(5) addition records with id；(6) addition record while identical id are recorded existing；(7) the same attribute of same record is changed；(8) deletion record runs into reference record.
- 10. the method for Electric Power Network Planning versions of data control as claimed in claim 1, it is characterised in that the step 7 is specifically wrapped Include procedure below：Step 71. performs data and merged successfully, it is determined that without the data that can more merge from central data warehouse；Step 72. extraction local data warehouse edition tree, extracts central data warehouse edition tree, performs version alignment operation, look for Go out the difference section of local data warehouse and central data warehouse, that is, find out the incremental data bag for needing to submit；Step 73. promotes incremental data bag to central data warehouse；Step 74. forms new versions of data in central data warehouse, and versions of data is shared a success and terminated.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711006395.6A CN107766521B (en) | 2017-10-25 | 2017-10-25 | Power grid planning data version control method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711006395.6A CN107766521B (en) | 2017-10-25 | 2017-10-25 | Power grid planning data version control method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107766521A true CN107766521A (en) | 2018-03-06 |
| CN107766521B CN107766521B (en) | 2021-12-14 |
Family
ID=61271498
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711006395.6A Active CN107766521B (en) | 2017-10-25 | 2017-10-25 | Power grid planning data version control method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107766521B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108647268A (en) * | 2018-04-28 | 2018-10-12 | 国网湖南省电力有限公司 | Increment updating method for distribution network planning data integration |
| CN111143315A (en) * | 2019-12-27 | 2020-05-12 | 贵州电网有限责任公司 | Version management method of transformer substation secondary circuit information model based on Git |
| CN112162970A (en) * | 2020-09-04 | 2021-01-01 | 华南理工大学 | Basic data maintenance method, enterprise side client, client side client and cloud server |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102917020A (en) * | 2011-09-24 | 2013-02-06 | 国网电力科学研究院 | Mobile terminal based on data packet and method for synchronizing business system data |
| CN103823797A (en) * | 2012-11-16 | 2014-05-28 | 镇江诺尼基智能技术有限公司 | FTP (file transfer protocol) based real-time industry database data synchronization system |
| US20140149369A1 (en) * | 2011-07-12 | 2014-05-29 | General Electric Company | Version control methodology for network model |
| US20150149371A1 (en) * | 2013-11-27 | 2015-05-28 | Red Ball Express, LLC | System And Method For Generating And Formatting Formally Correct Case Documents From Rendered Semantic Content |
| CN104834700A (en) * | 2015-04-27 | 2015-08-12 | 南京邮电大学 | Method for capturing movement data increment based on track change |
| CN105790441A (en) * | 2016-05-02 | 2016-07-20 | 国家电网公司 | Intelligent transformer substation relay protection inspection system |
| CN105930439A (en) * | 2016-04-20 | 2016-09-07 | 国电南瑞科技股份有限公司 | System and method for managing multiple versions of power grid model |
| CN105976262A (en) * | 2016-05-09 | 2016-09-28 | 国电南瑞科技股份有限公司 | Power plant granularity based power grid model version sharing method |
| CN106372301A (en) * | 2016-08-29 | 2017-02-01 | 西电通用电气自动化有限公司 | Method and system for detecting visualization and configuration consistency of configuration file of intelligent substation |
| CN106780157A (en) * | 2017-03-13 | 2017-05-31 | 国电南瑞科技股份有限公司 | Power network multi-time Scales model storage and management system and method based on Ceph |
| CN107292759A (en) * | 2016-04-10 | 2017-10-24 | 国网山东省电力公司经济技术研究院 | Distribution network planning based on power supply reliability calculates analysis system |
-
2017
- 2017-10-25 CN CN201711006395.6A patent/CN107766521B/en active Active
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140149369A1 (en) * | 2011-07-12 | 2014-05-29 | General Electric Company | Version control methodology for network model |
| CN102917020A (en) * | 2011-09-24 | 2013-02-06 | 国网电力科学研究院 | Mobile terminal based on data packet and method for synchronizing business system data |
| CN103823797A (en) * | 2012-11-16 | 2014-05-28 | 镇江诺尼基智能技术有限公司 | FTP (file transfer protocol) based real-time industry database data synchronization system |
| US20150149371A1 (en) * | 2013-11-27 | 2015-05-28 | Red Ball Express, LLC | System And Method For Generating And Formatting Formally Correct Case Documents From Rendered Semantic Content |
| CN104834700A (en) * | 2015-04-27 | 2015-08-12 | 南京邮电大学 | Method for capturing movement data increment based on track change |
| CN107292759A (en) * | 2016-04-10 | 2017-10-24 | 国网山东省电力公司经济技术研究院 | Distribution network planning based on power supply reliability calculates analysis system |
| CN105930439A (en) * | 2016-04-20 | 2016-09-07 | 国电南瑞科技股份有限公司 | System and method for managing multiple versions of power grid model |
| CN105790441A (en) * | 2016-05-02 | 2016-07-20 | 国家电网公司 | Intelligent transformer substation relay protection inspection system |
| CN105976262A (en) * | 2016-05-09 | 2016-09-28 | 国电南瑞科技股份有限公司 | Power plant granularity based power grid model version sharing method |
| CN106372301A (en) * | 2016-08-29 | 2017-02-01 | 西电通用电气自动化有限公司 | Method and system for detecting visualization and configuration consistency of configuration file of intelligent substation |
| CN106780157A (en) * | 2017-03-13 | 2017-05-31 | 国电南瑞科技股份有限公司 | Power network multi-time Scales model storage and management system and method based on Ceph |
Non-Patent Citations (1)
| Title |
|---|
| 陈荣权等: "基于版本化模型的配电网辅助设计系统的实现", 《电力信息化》 * |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108647268A (en) * | 2018-04-28 | 2018-10-12 | 国网湖南省电力有限公司 | Increment updating method for distribution network planning data integration |
| CN111143315A (en) * | 2019-12-27 | 2020-05-12 | 贵州电网有限责任公司 | Version management method of transformer substation secondary circuit information model based on Git |
| CN112162970A (en) * | 2020-09-04 | 2021-01-01 | 华南理工大学 | Basic data maintenance method, enterprise side client, client side client and cloud server |
| CN112162970B (en) * | 2020-09-04 | 2022-03-29 | 华南理工大学 | Basic data maintenance method, enterprise side client, client side client and cloud server |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107766521B (en) | 2021-12-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Weiss et al. | Logoot: A scalable optimistic replication algorithm for collaborative editing on p2p networks | |
| CN107766521A (en) | A kind of method of Electric Power Network Planning versions of data control | |
| CN101136783B (en) | Backup, recovery method and apparatus for network management system to configure data | |
| US20210216678A1 (en) | Cad collaborative design system | |
| CN104731596A (en) | Classification editing method for supporting multiple people to edit XBRL on line | |
| CN106649378A (en) | Data synchronizing method and device | |
| CN106777270A (en) | A kind of Heterogeneous Database Replication parallel execution system and method based on submission point time line locking | |
| CN106383876A (en) | Intelligent project matching system | |
| CN101556663A (en) | Project design process management system | |
| CN102402600B (en) | Asynchronous collecting method for maintaining consistency of database replicas | |
| CN102103642A (en) | OLTP-based data deletion method, system and graphic database sever | |
| CN109947741B (en) | Method for modeling and storing attribute parameters of items | |
| CN102193991A (en) | OLTP(on-line transaction processing)-based data modifying method and system as well as graphic database server | |
| CN103606032B (en) | A kind of method in two dimension power grid GIS data set | |
| CN108228762B (en) | Method and system for configuring master database universal templates | |
| CN105718572B (en) | A kind of transaction consistency of isomeric data composite object reaches method and system | |
| CN106802928B (en) | Power grid historical data management method and system | |
| CN109559085A (en) | The measures and procedures for the examination and approval and terminal device based on BIM light weighed model | |
| CN103544338A (en) | Method for technique information modeling for issuing three-dimensional assembling instruction | |
| CN113407230B (en) | Intelligent main model management system based on data driving | |
| CN110069516A (en) | A kind of service content intelligent management Implementation Technology based on normative document | |
| CN110232047B (en) | Time line management system, method, computer readable storage medium and computer terminal for CAD file | |
| CN107533559A (en) | Data structure, the model for filling data structure and the method being programmed using data structure to processing unit | |
| CN102193981B (en) | Method for realizing transaction expiration mechanism in online transaction of graphic database | |
| CN101216910B (en) | Isomorphic model merging method in the modeling of distributed enterprises |
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 |