CN103679395A - Enterprise planning management and analysis method based on temporal data operation - Google Patents
Enterprise planning management and analysis method based on temporal data operation Download PDFInfo
- Publication number
- CN103679395A CN103679395A CN201310748690.4A CN201310748690A CN103679395A CN 103679395 A CN103679395 A CN 103679395A CN 201310748690 A CN201310748690 A CN 201310748690A CN 103679395 A CN103679395 A CN 103679395A
- Authority
- CN
- China
- Prior art keywords
- plan
- mark
- enterprise
- time
- attribute
- 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.)
- Pending
Links
Images
Landscapes
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The invention discloses an enterprise planning management and analysis method based on temporal data operation. The enterprise planning management and analysis method based on the temporal data operation is characterized by comprising the following steps of (A) establishing a tense marker document; (B) establishing an enterprise planning temporal data index and leading the tense marker document into a binary data file through a data conversion engine, wherein the tense marker document includes binary planning temporal attribute records and planning temporal index; (C) inquiring and analyzing the enterprise planning temporal data, utilizing a temporal processing module to inquire the enterprise planning temporal data and performing quantitative calculation on the execution degree of enterprise plans according to the consistent degree of actual execution process and preset execution process of plans when the executable degree of the plans is analyzed. By adopting the enterprise planning management and analysis method based on the temporal data operation, an effective plan execution time management engine is provided for enterprises, the time management efficiency of an enterprise information management system is improved, analysis on plan execution time information in the system is achieved, and decision support is provided for the top.
Description
Technical field
The present invention relates to a kind of enterprise plan management and analytical approach, specifically a kind of enterprise plan management and analytical approach based on temporal data operation.
Background technology
The demand of temporal information and technology are accompanied by the development of database technology in fact always and produce and develop.Temporal database is to record the database of time dependent information, has the characteristic of following several aspects:
1) dynamic.Traditional Database Systems are carried out static state or accurate dynamic data base administration to data.When database update, out-of-date data will be deleted from database, and this just can not reflect the dynamic process of real world.In traditional database, can only preserve the last data; And in temporal database, out-of-date data are no longer deleted from database, to historical data, also can upgrade, make system and real world keep omnibearing dynamic exchange always.
2) comprehensive.Because temporal database is the aggregate of all data, the data of any moment and time period can be provided, make database become database truly, this is that traditional database is incomparable.
Enterprise plan management is the important component part of business administration, is in fact to the planning of business operation and management.Enterprise wants to improve constantly effectiveness of operation and efficiency, first will guarantee improving constantly of planning management level.Because the business activities of enterprise are complicated, the formulation of every plan and planning need the abundant linking on the retention time, to corporate decision maker, are very large challenges.In addition, execution and the time of plan are closely related, and each of plan exists the relations such as synchronous, mutual exclusion or cause and effect in stage, and these are all huge challenges concerning plan operational staff.Therefore, an efficient planning management platform is vital to enterprise.
In traditional enterprise information management system, mostly the management of information is that the relational database management system based on static carries out, and this is not also suitable for and tight relevant plans management of time.Planning management is the important content of business administration, and the execution of plan is with obvious tense attribute.Therefore in the enterprise information management system, particularly in planning management, add tense administrative skill, can make planning management more effectively and directly.
Summary of the invention
The object of the present invention is to provide a kind of enterprise plan management and analytical approach based on temporal data operation, the present invention has adopted the description means of temporal data to the plan implementation in business administration, and by Structural Indexing of Organized, plan the reorganization in each stage, to improve the validity of modern enterprise to the management of plan implementation.
Technical scheme of the present invention is as follows: enterprise plan management and analytical approach based on temporal data operation, it is characterized in that, and comprise the following steps:
A, establishment tense marking document: utilize text mark editing machine to carry out temporal data description to enterprise plan, in time describing framework, the time attribute in the timeline of enterprise plan and implementation thereof is changed and is described, text mark editing machine generates marking document the marking document of PTDM description script automatically; Create in tense marking document, utilize text mark editing machine to define following label as planning tense descriptive markup:
<plan> mark: represent a plan, describe the base attribute of plan with <plan> mark, comprise plan title, plan responsible official, plan fund and plan importance degree;
Length attribute: the time span that represents plan expectation;
<timeline> mark: be the sub-mark of <plan>, mark the timeline of plan, wherein each stage identifies with the sub-mark of <step>;
Expect attribute: represent whether this <timeline> is default timeline, when Expect attribute is true, be expressed as default planned time line, when Expect attribute is false, represent that this is an actual timeline of carrying out of plan;
Concurrent attribute: represent this <timeline> be whether need to be represented with other <plan> mark plan synchronize;
Exclusive attribute: represent this <timeline> be whether need to be represented with other <plan> mark plan mutual exclusion;
<User_Time> mark: represent user's Self defined time, with respect to the real time, the user-defined time can be take any reference point as starting point;
The attribute of <User_Time> comprises ReferencePoint, represents the start time of reference;
B, set up enterprise plan temporal data index: marking document imports in a binary data file by data transformation engine, wherein comprise binary plan tense attribute record, and the tense index of plan: key step is as follows: (1) is used the document markup function storehouse passing marker document of increasing income, be converted to a mark syntax tree, and carry out prefix code, be converted into binary representation; (2) set up tense index, the timeline that the database of take comprises is time shaft, and each stage of difference plan is marked on time shaft, and tense index-group is made into the mode of bivariate table, wherein classify time shaft as, each stage of the plan that behavior is associated with time point on time shaft;
The inquiry and analysis of C, enterprise plan temporal data: utilize the inquiry of Temporal dispose module to enterprise plan temporal data, when can level of enforcement the carrying out of plan of analysis, by the practical implementation of plan and the consistent degree of default implementation, with this, quantize to calculate the execution degree of enterprise plan, concrete analysis is: analyze the resonable degree of making a plan, when the quota of formulating in section at one time or the programming phase of simultaneously carrying out are too much, system automatically to and prompting; Between the stage <step> of some plan, there is precedence relationship/cause-effect relationship, must complete in certain sequence, this relation is defined within the sub-mark of sub-label L EssT.LTssT.LTprecondition> of <step>; Analyzing the sub-mark of <precondition> there will not be due to the dissatisfied and inexecutable problem of pilot condition while carrying out by predefined sequential to guarantee each stage of plan; The analysis of the sub-mark of <precondition> is adopted the topological sorting method of plan execution graph is completed;
To each <step expect=false> mark plan execute phase pointed, analyze the consistent degree of itself and <step expect=true>, whether the actual execution of determining plan is consistent with default execution time line, adopts the poor method of each part-time of calculating to measure; For the <step> with concurrent attribute, by the size of its overlapping part, to measure, lap shows that more greatly the concurrent execution degree of plan is higher; For the <step> with Exclusive attribute, by the tightness degree of the linking in its each stage, measure, free time more, plan execution degree is lower.
Further, in drawing the inquiry and analysis of temporal data, utilize Temporal dispose module mutual by programming interactive interface and enterprise information system, and adopt loose coupling method to carry out alternately, enterprise information system sends to Temporal dispose module by the TSQL statement of standard inquiry and analysis request, and Temporal dispose module is returned to the result that tense record set form represents.
Further, programming interactive interface, adopts the database connected mode that meets ODBC standard.
Further, inquiry and analysis at enterprise plan temporal data, also comprise collaborative issued transaction module: in order to plan tense affairs are defined as to the plan sub with <step> mark that must work in coordination with, affairs are with Concurrent and Exclusive attribute definition, the <step> with Exclusive does not allow in same affairs processed, the <step> with Concurrent attribute does not permit meter processed in different affairs, request encapsulates with mark pattern.
Beneficial effect of the present invention: enterprise plan management and analytical approach based on temporal data operation, Neng Wei enterprise provides an effectively plan execution time management engine, the efficiency of time management in enterprise information management system, for the plan execution time information in system is analyzed, for high level provides decision support.
Accompanying drawing explanation
Below in conjunction with accompanying drawing, the present invention is described in further detail.
Fig. 1 is process flow diagram of the present invention.
Embodiment
As shown in Figure 1, enterprise plan management and analytical approach based on temporal data operation, comprise the following steps:
Create tense marking document: enterprise plan, with obvious time attribute, proposes in time describing framework, the time attribute in the timeline of enterprise plan and implementation thereof to be changed and is described.Use temporal data describing method to describe enterprise plan, the text mark language of usining is described means as the tense of plan, defines following label as planning tense descriptive markup (Plan Time Description Markup, PTDM):
<plan> mark: represent a plan
Length attribute: expression plan expectation time be span
<timeline> mark: be the sub-mark of <plan>, mark the timeline of plan, wherein each stage identifies with the sub-mark of <step>.
<step> mark: represent a plan execute phase of timeline, have two attributes of starttime and endtime.
Expect attribute: represent whether this <timeline> is default timeline
Concurrent attribute: represent this <timeline> be whether need to be represented with other <plan> mark plan synchronize
Exclusive attribute: represent this <timeline> be whether need to be represented with other <plan> mark plan mutual exclusion
<User_Time> mark: represent user's Self defined time, with respect to the real time, the user-defined time can be take any reference point as starting point.The attribute of <User_Time> comprises ReferencePoint, represents the start time of reference.
On the basis of these marks, provide the temporal data describing method of a plan.Enterprise plan is defined as an event with some time node,
.According to following steps to plan
carry out tense description:
(1) with <plan> mark, describe the base attribute of plan, comprise the time span Length attribute of plan title, plan responsible official, plan fund, plan importance degree, plan.
(2) two sub-marks of <timeline> of definition, the Expect attribute of one of them is true, is expressed as default planned time line, the predetermined implementation schedule of also planning.Each execute phase marks with <step> mark.Between each <step>, can overlap, the synchronism of representative plan execute phase; The Expect attribute of another <timeline> mark is that false represents that this is an actual timeline of carrying out of plan, and the content of this <timeline> mark constantly increases each execute phase representing with <step> mark along with the execution of plan.
(3) the stage definitions Concurrent and the Exclusive attribute that for each <step> mark, represent.
(4), for each <step> increases the sub-mark of <precondition>, mark precedence relationship and cause-effect relationship between different each stages of planning.
(5) the sub-mark of definition <User_Time>, set the relative time between plan, the reference start time of the sub-mark of Different L EssT.LTssT.LTUser_Time> can be not identical, but be necessary for the length of a game of enterprise management system.
Through above step, a plan is described as to a marking document, a plurality of <plan> marks can be placed in same marking document, can carry out various tense query manipulations.
Set up enterprise plan temporal data index: the plan temporal data marking document to the 1st description with claim manages and analyzes.Management function realizes by increase temporal data database management module in enterprise management system, and marking document imports in a binary data file by data transformation engine, wherein comprises binary plan tense attribute record, and the tense index of plan.Key step is as follows:
(1). use the document markup function storehouse passing marker document of increasing income, be converted to a mark syntax tree, and carry out prefix code, be converted into binary representation.
(2). set up tense index, the timeline that the database of take comprises is time shaft, and each stage of difference plan is marked on time shaft, and tense index-group is made into the mode of bivariate table, wherein classify time shaft as, each stage of the plan that behavior is associated with time point on time shaft.
The analysis of temporal data, mainly realizes two evaluating objects, one, plan can level of enforcement, its two, the practical implementation of plan and the consistent degree of default implementation, quantize to calculate the execution degree of enterprise plan with this.
The inquiry and analysis of enterprise plan temporal data:
(1). plan can level of enforcement: analyze the resonable degree of making a plan, when the quota of formulating in section at one time or the programming phase of simultaneously carrying out are too much, system automatically to and prompting.Between the stage <step> of some plan, there is precedence relationship/cause-effect relationship, must complete in certain sequence, this relation is defined within the sub-mark of sub-label L EssT.LTssT.LTprecondition> of <step>.Analyzing the sub-mark of <precondition> there will not be due to the dissatisfied and inexecutable problem of pilot condition while carrying out by predefined sequential to guarantee each stage of plan.The analysis of the sub-mark of <precondition> is adopted the topological sorting method of plan execution graph is completed.
(2). the quantification of plan execution degree is calculated
To each <step expect=false> mark plan execute phase pointed, analyze the consistent degree of itself and <step expect=true>, whether the actual execution of determining plan is consistent with default execution time line, and this part adopts the poor method of each part-time of calculating to measure.For the <step> with Concurrent attribute, by the size of its overlapping part, to measure, lap shows that more greatly the concurrent execution degree of plan is higher.For the <step> with Exclusive attribute, by the tightness degree of the linking in its each stage, measure, free time more, plan execution degree is lower.
The Framework for enterprise information system integration of plan temporal data: the interactive interface of Temporal dispose module and enterprise information system and collaborative transaction processing facility.
Temporal dispose module and enterprise information system interactive interface: adopt loose coupling method to carry out alternately, programming interactive interface adopts the database connected mode that meets ODBC standard, enterprise information system sends to Temporal dispose module by the TSQL statement of standard inquiry and analysis request, and Temporal dispose module is returned to the result that tense record set form represents.Service interactive interface adopts Web Service form, and with the form submit Query request of marking document, the mode with marking document returns results equally.
Synergetic affairs treatment mechanism: plan tense affairs are defined as the plan sub with <step> mark that must work in coordination with.The issued transaction of plan tense transaction management and enterprise management system is separate, adopt the mechanism of request feedback, affairs are with Concurrent and Exclusive attribute definition, the <step> with Exclusive does not allow in same affairs processed, and the <step> with Concurrent attribute does not permit meter processed in different affairs.Request encapsulates with mark pattern:
<request>
<transaction>
<term> plan name: phase name </term>
<term> plan name: phase name </term>
<term> plan name: phase name </term>
</transaction>
</request>
Feedback encapsulates with mark pattern:
<response>
<term> plan name: transaction status </term>
<term> plan name: transaction status </term>
<term> plan name: transaction status </term>
</response>
Plan <plan> tag definitions by name, stage, the sub-mark of <step> by name defined, the transaction status of <response> can be following three value: processing, commit, rollback, representative " in processing ", " submission " and " rollback " respectively.
Claims (4)
1. enterprise plan management and the analytical approach based on temporal data operation, is characterized in that, comprises the following steps:
A, establishment tense marking document: utilize text mark editing machine to carry out temporal data description to enterprise plan, in time describing framework, the time attribute in the timeline of enterprise plan and implementation thereof is changed and is described, text mark editing machine generates marking document the marking document of PTDM description script automatically; Create in tense marking document, utilize text mark editing machine to define following label as planning tense descriptive markup:
<plan> mark: represent a plan, describe the base attribute of plan with <plan> mark, comprise plan title, plan responsible official, plan fund and plan importance degree;
Length attribute: the time span that represents plan expectation;
<timeline> mark: be the sub-mark of <plan>, mark the timeline of plan, wherein each stage identifies with the sub-mark of <step>;
Expect attribute: represent whether this <timeline> is default timeline, when Expect attribute is true, be expressed as default planned time line, when Expect attribute is false, represent that this is an actual timeline of carrying out of plan;
Concurrent attribute: represent this <timeline> be whether need to be represented with other <plan> mark plan synchronize;
Exclusive attribute: represent this <timeline> be whether need to be represented with other <plan> mark plan mutual exclusion;
<User_Time> mark: represent user's Self defined time, with respect to the real time, the user-defined time can be take any reference point as starting point;
The attribute of <User_Time> comprises ReferencePoint, represents the start time of reference;
B, set up enterprise plan temporal data index: marking document imports in a binary data file by data transformation engine, wherein comprise binary plan tense attribute record, and the tense index of plan: key step is as follows: (1) is used the document markup function storehouse passing marker document of increasing income, be converted to a mark syntax tree, and carry out prefix code, be converted into binary representation; (2) set up tense index, the timeline that the database of take comprises is time shaft, and each stage of difference plan is marked on time shaft, and tense index-group is made into the mode of bivariate table, wherein classify time shaft as, each stage of the plan that behavior is associated with time point on time shaft;
The inquiry and analysis of C, enterprise plan temporal data: utilize the inquiry of Temporal dispose module to enterprise plan temporal data, when can level of enforcement the carrying out of plan of analysis, by the practical implementation of plan and the consistent degree of default implementation, with this, quantize to calculate the execution degree of enterprise plan, concrete analysis is: analyze the resonable degree of making a plan, when the quota of formulating in section at one time or the programming phase of simultaneously carrying out are too much, system automatically to and prompting; Between the stage <step> of some plan, there is precedence relationship/cause-effect relationship, must complete in certain sequence, this relation is defined within the sub-mark of sub-label L EssT.LTssT.LTprecondition> of <step>; Analyzing the sub-mark of <precondition> there will not be due to the dissatisfied and inexecutable problem of pilot condition while carrying out by predefined sequential to guarantee each stage of plan; The analysis of the sub-mark of <precondition> is adopted the topological sorting method of plan execution graph is completed;
To each <step expect=false> mark plan execute phase pointed, analyze the consistent degree of itself and <step expect=true>, whether the actual execution of determining plan is consistent with default execution time line, adopts the poor method of each part-time of calculating to measure; For the <step> with concurrent attribute, by the size of its overlapping part, to measure, lap shows that more greatly the concurrent execution degree of plan is higher; For the <step> with Exclusive attribute, by the tightness degree of the linking in its each stage, measure, free time more, plan execution degree is lower.
2. enterprise plan management and the analytical approach based on temporal data operation according to claim 1, it is characterized in that: in drawing the inquiry and analysis of temporal data, utilize Temporal dispose module mutual by programming interactive interface and enterprise information system, and adopt loose coupling method to carry out alternately, enterprise information system sends to Temporal dispose module by the TSQL statement of standard inquiry and analysis request, and Temporal dispose module is returned to the result that tense record set form represents.
3. enterprise plan management and the analytical approach based on temporal data operation according to claim 1, is characterized in that: programming interactive interface, adopts the database connected mode that meets ODBC standard.
4. enterprise plan management and the analytical approach based on temporal data operation according to claim 1, it is characterized in that: at the inquiry and analysis of enterprise plan temporal data, also comprise collaborative issued transaction module: in order to plan tense affairs are defined as to the plan sub with <step> mark that must work in coordination with, affairs are with Concurrent and Exclusive attribute definition, the <step> with Exclusive does not allow in same affairs processed, the <step> with Concurrent attribute does not permit meter processed in different affairs, request encapsulates with mark pattern.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310748690.4A CN103679395A (en) | 2013-12-31 | 2013-12-31 | Enterprise planning management and analysis method based on temporal data operation |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310748690.4A CN103679395A (en) | 2013-12-31 | 2013-12-31 | Enterprise planning management and analysis method based on temporal data operation |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN103679395A true CN103679395A (en) | 2014-03-26 |
Family
ID=50316872
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201310748690.4A Pending CN103679395A (en) | 2013-12-31 | 2013-12-31 | Enterprise planning management and analysis method based on temporal data operation |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103679395A (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6898475B1 (en) * | 2004-05-27 | 2005-05-24 | Palo Alto Research Center Inc. | System and method utilizing temporal constraints to coordinate multiple planning sessions |
| JP2006185220A (en) * | 2004-12-28 | 2006-07-13 | Internatl Business Mach Corp <Ibm> | Data processing apparatus, data management apparatus, data processing method, data management method, data processing program, data management program and information system |
| CN103077215A (en) * | 2012-12-28 | 2013-05-01 | 深圳先进技术研究院 | Method for dynamically updating three-dimensional urban model database in event driving way |
| CN103426061A (en) * | 2013-08-19 | 2013-12-04 | 周晓光 | Emergency maintenance and update integrated system and method based on target tracking |
-
2013
- 2013-12-31 CN CN201310748690.4A patent/CN103679395A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6898475B1 (en) * | 2004-05-27 | 2005-05-24 | Palo Alto Research Center Inc. | System and method utilizing temporal constraints to coordinate multiple planning sessions |
| JP2006185220A (en) * | 2004-12-28 | 2006-07-13 | Internatl Business Mach Corp <Ibm> | Data processing apparatus, data management apparatus, data processing method, data management method, data processing program, data management program and information system |
| CN103077215A (en) * | 2012-12-28 | 2013-05-01 | 深圳先进技术研究院 | Method for dynamically updating three-dimensional urban model database in event driving way |
| CN103426061A (en) * | 2013-08-19 | 2013-12-04 | 周晓光 | Emergency maintenance and update integrated system and method based on target tracking |
Non-Patent Citations (2)
| Title |
|---|
| 刘云生等: "一种可行的时态数据库索引技术", 《计算机应用研究》, no. 10, 1 October 2006 (2006-10-01), pages 63 - 65 * |
| 李楠等: "基于UML和关系模型的时态数据库设计方法研究", 《中国优秀硕士学位论文全文数据库信息科技辑》, no. 12, 15 December 2010 (2010-12-15) * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Azeroual et al. | The effects of using business intelligence systems on an excellence management and decision-making process by start-up companies: A case study | |
| US8671084B2 (en) | Updating a data warehouse schema based on changes in an observation model | |
| CN108874919B (en) | Automatic checking method for planned land, electronic equipment, storage medium and system | |
| CN109101652A (en) | A kind of creation of label and management system | |
| CN105224631B (en) | The method built the system of the open cloud of industry and work out XBRL financial statement | |
| CN110750650A (en) | Construction method and device of enterprise knowledge graph | |
| CN106611246A (en) | Integrated management system of land and resources | |
| CN104216948A (en) | Difference control method of data model | |
| CN202948475U (en) | Information management system of construction material | |
| CN109299074B (en) | Data verification method and system based on templated database view | |
| CN102646224A (en) | Management integrating system of enterprise standardization | |
| CN102708466A (en) | Project management system | |
| CN112651218A (en) | Automatic generation method and management method of bidding document, medium and computer | |
| CN105069556A (en) | User behavior analysis method and system of ERP management system | |
| CN103606032B (en) | A kind of method in two dimension power grid GIS data set | |
| Gupta et al. | Process cube for software defect resolution | |
| CN109636303A (en) | A kind of storage method and system of semi-automatic extraction and structured document information | |
| CN103593228A (en) | Practical test instrument program control command emulator and application method thereof | |
| CN113342921A (en) | Resource cataloging method and device | |
| KR100798577B1 (en) | Analyzing system and analyzing method for data quality problem | |
| CN108132802B (en) | Application method of configuration model in system development | |
| CN103309888A (en) | Method and device for verifying data of electronic map | |
| CN103679395A (en) | Enterprise planning management and analysis method based on temporal data operation | |
| CN105243490B (en) | A kind of statistical system and method based on git software | |
| CN103092841A (en) | Method and device for processing data |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20140326 |