CN112711412B - Universal business plan compiling method and platform - Google Patents
Universal business plan compiling method and platform Download PDFInfo
- Publication number
- CN112711412B CN112711412B CN202011600689.3A CN202011600689A CN112711412B CN 112711412 B CN112711412 B CN 112711412B CN 202011600689 A CN202011600689 A CN 202011600689A CN 112711412 B CN112711412 B CN 112711412B
- Authority
- CN
- China
- Prior art keywords
- plan
- business
- data
- compiling
- service
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 40
- 238000013499 data model Methods 0.000 claims abstract description 55
- 238000004364 calculation method Methods 0.000 claims abstract description 11
- 238000013439 planning Methods 0.000 claims description 14
- 238000013075 data extraction Methods 0.000 claims 1
- 238000011161 development Methods 0.000 abstract description 7
- 230000008569 process Effects 0.000 abstract description 7
- 230000008520 organization Effects 0.000 description 8
- 230000018109 developmental process Effects 0.000 description 6
- 238000010586 diagram Methods 0.000 description 6
- 238000012545 processing Methods 0.000 description 5
- 230000002776 aggregation Effects 0.000 description 3
- 238000004220 aggregation Methods 0.000 description 3
- 238000004458 analytical method Methods 0.000 description 3
- 238000013500 data storage Methods 0.000 description 3
- 230000000694 effects Effects 0.000 description 3
- 238000010276 construction Methods 0.000 description 2
- 238000007405 data analysis Methods 0.000 description 2
- 230000007547 defect Effects 0.000 description 2
- 238000000605 extraction Methods 0.000 description 2
- 238000007726 management method Methods 0.000 description 2
- 238000013507 mapping Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004883 computer application Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 239000000284 extract Substances 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000005192 partition Methods 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 238000000926 separation method Methods 0.000 description 1
- 230000033772 system development Effects 0.000 description 1
- 238000012384 transportation and delivery Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/35—Creation or generation of source code model driven
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/36—Software reuse
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The application discloses a general business plan compiling method and a general business plan compiling platform, which are used for solving the technical problems that an enterprise needs to adapt to application scenes of different systems or modules when different business plans are compiled, and a developer has high work overlapping rate in a developing process. The method comprises the following steps: determining corresponding service models which are respectively pre-constructed aiming at different service plans and corresponding basic plan forms; the business model and the basic plan form comprise fields for describing business plans; extracting a characteristic field and a value field of the service model, and constructing a data model; compiling the basic plan form to obtain an actual plan form comprising fields describing the service plan and corresponding field values, and synchronizing the field values into a data model; and performing data calculation and summarization on the data model. By the method, the universal compilation of the service plan and the reuse of the modules are realized, the enterprise development cost can be reduced, and the application experience of a user is enhanced.
Description
Technical Field
The application relates to the technical field of computer application, in particular to a general business plan compiling method and platform.
Background
When an enterprise compiles different business plans, software systems of different manufacturers may be used, or the same software system is used, but business design partitions belong to different modules and are completed by different developers.
Therefore, when a business person compiles a business plan, the business person needs to adapt to different application scenes of each business plan, different application experiences exist, and a lot of time and energy are consumed. In addition, for developers, different systems or different modules are independent from each other, and information cannot be shared, so that the developers have a work overlapping condition in work, the efficiency is low, the per-capita capacity is low, and the development cost of enterprises is increased.
Disclosure of Invention
The embodiment of the application provides a general business plan compiling method and a general business plan compiling platform, which are used for solving the technical problems that an enterprise needs to spend time to adapt to different application scenes when compiling different business plans, and developers have high work overlapping rate in the system development process.
In one aspect, an embodiment of the present application provides a method for universal compilation of a service plan, including: determining corresponding service models which are respectively pre-constructed aiming at different service plans and corresponding basic plan forms; the business model and the basic plan form comprise fields for describing business plans; extracting a characteristic field and a value field of the service model, and constructing a data model; compiling the basic plan form to obtain an actual plan form comprising fields describing the service plan and corresponding field values, and synchronizing the field values into a data model; and carrying out data calculation and summarization on the data model.
In an implementation manner of the present application, determining corresponding service models that are respectively pre-constructed for different service plans specifically includes: and referencing a default field describing the service plan, adding a specified field according to the service plan, and constructing a service model.
In an implementation manner of the present application, extracting a feature field and a value field of a service model, and constructing a data model specifically includes: taking a non-numerical field in the service model as a characteristic field and taking a numerical field as a value field; and extracting the characteristic field and the value field to construct a data model.
In an implementation manner of the present application, before the basic plan form is compiled, the method further includes: setting a compiling scheme according to a compiling period of the service plan, and forming a compiling task according to the compiling scheme; the method comprises the following steps of compiling a task, wherein the compiling task comprises a compiling main body and a basic plan form; and determining the programming task as an un-programmed state.
In an implementation manner of the present application, compiling the basic plan form to obtain an actual plan form including a field describing a service plan and a corresponding field value specifically includes: determining a plurality of detailed plans contained in the business plan; the detail plans correspond to the same basic plan form; and compiling the basic plan forms respectively according to the content of each detail plan to obtain actual plan forms corresponding to the detail plans respectively.
In an implementation manner of the present application, compiling the basic plan form to obtain an actual plan form including a field describing a service plan and a corresponding field value specifically includes: judging whether the type of the detail plan is a expenditure type; if yes, determining that the expenditure statistical data in the corresponding actual plan form does not exceed a preset expenditure threshold value.
In an implementation manner of the present application, the data calculation and summarization of the data model specifically includes: respectively extracting data in the data models corresponding to the actual plan forms; and according to the hierarchical relation among the actual plan forms, carrying out data summarization on the extracted data of the corresponding fields from the last stage to the previous stage in sequence.
In one implementation of the present application, the method further comprises: judging whether the ratio between the actual payment to be paid in the detail plan and the planned payment is excessive according to a preset floating ratio; if not, the payment operation is executed through the approval of the detail plan.
In one implementation manner of the present application, the receiving and payment conditions of the detail plan corresponding to each actual plan form are shown through a chart.
On the other hand, the embodiment of the present application further provides a service plan general compilation platform, where the platform includes: the business model building module is used for determining corresponding business models which are respectively pre-built aiming at different business plans and corresponding basic plan forms; the business model and the basic plan form comprise fields for describing business plans; the data model building module is used for extracting the characteristic field and the value field of the service model and building a data model; the compiling module is used for compiling the basic plan form to obtain an actual plan form comprising fields describing the service plan and corresponding field values, and synchronizing the field values into the data model; and the calculation and summary module is used for calculating and summarizing data of the data model.
The business plan universal compilation method and the business plan universal compilation platform provided by the embodiment of the application at least have the following beneficial effects: corresponding business models are respectively built according to different business plans, the templates for building the business models can be reused, and the structure of the business models can be customized according to the actual requirements of users, so that the users do not need to adapt to the application scenes of a plurality of compiling systems or modules when compiling different business plans, the product usability is improved, and a large amount of time and energy can be saved; meanwhile, in the development process of the planning system, the general planning of the service plan is realized by constructing the service model, independent development is not needed for different service plans, the overlapping rate of development work is reduced, the development efficiency is effectively improved, and the enterprise cost is reduced. In addition, a data model is built according to the business model, data storage, calculation and summarization are achieved through the data model, data and business separation is achieved, and application complexity is reduced.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:
fig. 1 is a flowchart of a general business plan compiling method according to an embodiment of the present disclosure;
FIG. 2 is a schematic diagram of a formula definition provided in an embodiment of the present application;
FIG. 3 is a schematic diagram of model extraction provided by an embodiment of the present application;
fig. 4 is a schematic structural diagram of a service plan general compilation platform provided in the embodiment of the present application.
Detailed Description
To make the objects, technical solutions and advantages of the present application more clear, the technical solutions of the present application will be clearly and completely described below with reference to specific embodiments of the present application and the accompanying drawings. It should be apparent that the described embodiments are only a few embodiments of the present application, and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The embodiment of the application provides a general business plan compiling method and a general business plan compiling platform, corresponding business models are constructed for different business plans, and data models are extracted from the business models, so that data storage and summarization are completed, and the technical problems that an enterprise needs to adapt to application scenes of different systems or modules when making different business plans, and working overlapping rate of developers is high in a developing process are solved.
The technical solutions proposed in the embodiments of the present application are described in detail below with reference to the accompanying drawings.
Fig. 1 is a flowchart of a general business plan compiling method provided in an embodiment of the present application. As shown in fig. 1, the general business plan compiling method provided in the embodiment of the present application mainly includes the following steps:
s101, determining corresponding service models and corresponding basic plan forms which are respectively constructed in advance aiming at different service plans.
The server constructs a corresponding service model according to the field describing the current service plan and forms a corresponding basic plan form aiming at different service plans; wherein the business model and the base plan form both include fields describing the business plan.
In particular, a business plan refers to a broad class of plans, such as a funding plan, a procurement plan, a sales plan, and so forth. A business plan corresponds to a business model, and the business model consists of a set of fields describing the business plan, without including specific field values. Under each business plan, a plurality of detail plans are subdivided, and each detail plan corresponds to the business model of the business plan and is provided with fields contained in the business model. In addition, the server constructs a business model according to the fields describing the business plan, and simultaneously forms a basic plan form, wherein the basic plan form is the basis for compiling the detailed plan and bears the relevant business model, and only contains the fields but not the field values.
According to project requirements, the basic plan form mainly comprises a form body and a form head, and main field elements comprise a balance project, a date, an amount and the like. The header part comprises an organization unit, a plan scheme, a plan period, a plan form, income aggregate, expense aggregate and the like, wherein the organization unit represents the name of the current organization unit, namely the name of a specific department and a company; the plan scheme represents a currently compiled plan scheme; the planning period represents the compilation period of the current detailed plan; the planning period represents the activity period of the current detailed plan; the plan form displays a basic plan form compiled currently; the income total and the expenditure total respectively represent the statistical values of the income and the expenditure of the currently compiled detail plan. The table body part comprises items, plan numbers, plan types, plan dates, balance types, plan currencies, plan bills, currency, counter units and the like, and the item fields are selected from the item dictionary for item entry; the plan number represents the number of the current detail plan and is automatically generated; the plan type is used for customizing the plan type so as to classify the detailed plan; the income and expenditure type is that the current detail plan is displayed to be the attribute of expenditure or income; planning a cash-out represents an amount of money planned to be paid using the cash-out; the planned ticket represents an amount for which payment is planned using the ticket; currency type is used to select the currency type of payment; the opposite side unit is selected to be recorded in the opposite side unit information dictionary.
In an embodiment of the application, the user has different requirements for different business plans, and when a business model is constructed, the server supports extension of a basic plan form, namely, on the basis of default fields, the fields are customized according to different requirements and are added to the business model. The default field is a field defined by developers and commonly used, and the custom field is a field defined by business personnel. Therefore, the defect that only one compiling format is used in traditional planning is overcome, different business models can be built for different businesses, the operation is more flexible, and the application experience of a user is improved.
In a possible implementation mode, the server can select required default fields according to the current business plan through a modeling tool template, and if the fields are lacked, the fields expanded by self definition are added into the modeling tool template, so that the construction of the business model and the flexible compilation of the basic plan form are realized.
S102, extracting a characteristic field and a value field of the service model, and constructing a data model.
And the server extracts the characteristic field and the value field in the service model to form a data model for finishing background logic processing of the data.
In one embodiment of the application, the server classifies the fields according to their properties in the business model, with non-numeric fields (items, planning dates, etc.) as feature fields and numeric fields (planning remissions, planning tickets, etc.) as value fields. After the construction of the business model is completed, the server automatically classifies all fields of the business model, identifies the characteristic field and the value field and constructs a corresponding data model.
Specifically, the data model structure is shown in table 1:
TABLE 1
| Number of | Name(s) | Attribute |
| PROJECTID | Item ID | Feature(s) |
| ID | ID | Value field |
Wherein the first column of table 1 represents the name of each field in the data model, the second column represents the actual name of each field, and the third column represents that the field belongs to a feature field or a value field.
The data model is formed by extracting the fields of the service model, so that the data can be quantized and operated, the data can be conveniently stored, calculated and summarized, and background logic processing of the data is realized. Meanwhile, on the basis of calculating and summarizing data in the data model, the data analysis and decision making work is facilitated.
S103, compiling the basic plan form to obtain an actual plan form comprising fields describing the service plan and corresponding field values, and synchronizing the field values into the data model.
And the server adds data to the basic plan form according to the compiling operation of the basic plan form to obtain an actual plan form, and synchronizes the data to the corresponding data model according to the model mapping relation. Wherein the actual plan form includes fields describing the current business plan and corresponding field values. Further, the basic plan form is compiled based on a plurality of detail plans included in the business plan, and an actual plan form corresponding to each detail plan can be obtained.
In an embodiment of the application, the server performs scheme management on main elements such as an actual plan form, a compilation main body and a compilation period to form a compilation task, so that task driving of service planning is realized. Before the server determines to compile the basic plan form, a compilation task needs to be preset, and detailed plans still needing to be compiled at present are checked according to the state of the compilation task. Firstly, setting a compiling scheme according to a compiling period, for example, setting the compiling period to be one month, and then using the scheme to compile a detailed plan of a certain month; secondly, determining a compiling range according to the compiling main body and the basic plan form, for example, the department 1 can compile a monthly expenditure table, so that a detailed plan range which can be compiled by the compiling main body is formed, and different compiling schemes can reuse the same compiling range; then, determining a compilation task according to the compilation scheme, wherein the compilation task corresponds to a corresponding compilation main body and a basic plan form to be compiled, for example, a department 1 needs to compile a 5-month expenditure table; and finally, determining the state of the compiling task, and compiling the corresponding basic plan form if the compiling task is not compiled. The above parameters are only selected by way of example, and the present application is not limited thereto.
Specifically, the compilation task is composed of an organization number, an organization name, a form number, a form name, a status, and the like. The organization number and the organization name correspond to the number of the compiling main body and the name of the compiling main body respectively, in addition, each basic plan form can number and name the organization number and the name of the form, the form number and the name of the form are used for limiting a specific detailed plan, the state column displays the state of the current task, such as states of non-compiling, examining and approving and the like, business personnel can reasonably distribute work according to the state of the task when planning and compiling, the usability is improved, and the working efficiency is ensured.
In an embodiment of the present application, a plurality of detail plans are subdivided under one business plan, each detail plan corresponds to a basic plan form of the business plan, and the server performs data filling on the basic plan form according to the content of each detail plan, so as to obtain an actual plan form corresponding to each basic plan form.
In an embodiment of the application, when the server compiles the basic plan form, it is first determined whether the currently compiled detailed plan is a payout plan according to the type of the detailed plan, and if the currently compiled detailed plan is a payout plan, it is determined whether payout statistical data in an actual plan form exceeds a preset payout threshold. If the current plan exceeds the preset expenditure threshold, prompting that the current plan exceeds the preset expenditure threshold, and assisting to modify the detailed plan according to the size of the preset threshold; if not, the basic plan form can be continuously compiled until the compilation is finished, and an actual plan form is obtained.
In an embodiment of the application, after obtaining the actual planning form, the server automatically maps the field value in the form to the corresponding field in the data model according to the model mapping relationship, so as to realize data storage.
In an embodiment of the application, after obtaining the actual plan forms, the server graphically analyzes the balance of the detail plan corresponding to each actual plan form, for example, the balance amounts on different dates are displayed through a bar chart.
And S104, calculating and summarizing data of the data model.
The server performs grading summarization on the data stored in the data model, and further achieves summarization of the data from the bottom unit to the upper unit, so as to achieve data analysis and decision.
In an embodiment of the application, the actual plan form includes a plurality of project data, and upper and lower level relationships exist among the projects, after the server synchronizes field values of the actual plan form to the data model, data can be extracted from the data model according to set data dimensions, and data summarization is performed on the data of the data fields sequentially from a last level to an upper level through a hierarchical relationship among the actual plan forms corresponding to the data model based on a defined formula, and finally, the aggregation of the project data is completed, and the obtained summarized data is automatically generated into a corresponding summarization plan table. The specific formula is shown in fig. 2.
Fig. 2 is a schematic diagram of formula definition provided in the embodiment of the present application. As shown in fig. 2, the formula represents that numerical values of all dimensions, that is, all field values, are extracted from the data model according to the default period number, and then the total summary of the numerical dimensions of the items is completed according to the upper-lower level relation of the corresponding items through the hierarchical summary function. Wherein the dimension value column is not filled in to indicate that the default value is taken from all the dimensions.
In an embodiment of the application, after the server obtains the summarized data, the server performs index calculation according to the summarized data, and further performs graphical analysis on each index. The graphic analysis type includes, but is not limited to, a bar chart, a line chart, and a pie chart. Therefore, the analysis result is displayed through the graph, so that the display effect is better, and the usability is improved.
In an embodiment of the present application, after the server completes the aggregation of the project data based on the formula, the aggregation relationship, that is, the secondary structure of the local data — the clique data, may also be set according to the system of the clique. The server can gradually gather the summary schedules generated by the subordinate companies to the group, so that the longitudinal summary of the data is realized, and the group can analyze and decide the summarized data.
In an embodiment of the present application, the server may also set a formula to realize summarizing detailed plans by date, for example, summarizing monthly actual plan forms to generate annual data.
In one embodiment of the present application, after a detailed plan is in effect, the server may control the implementation of the plan by setting a floating ratio for a certain type of plan. The server may determine whether the ratio between the actual payment due for the itemized plan and the planned payment is excessive based on a preset float ratio. If not, the actual payment of the detail plan is within the allowable range, the approval of the detail plan is passed, and the payment operation is executed.
For example, the payment floating rate of the detail plan of which the type is an expense plan is set to 120%, and if the expense amount of the planned payment is 100 ten thousand yuan, the detail plan of which the actual payment does not exceed 120 ten thousand yuan can be approved to make the payment. When a plurality of detail plans meet the payment condition, the detail plans can be sequentially validated through manual distribution, and can also be automatically distributed. The above parameters are only selected by way of example, and the application is not limited thereto.
Fig. 3 is a schematic diagram of model extraction according to an embodiment of the present disclosure. As shown in fig. 3, the bottom layer includes a data model or BE (business entity) for describing data structures, wherein the BE is a service entity for describing service characteristics. A data model structure supports multiple business models. The business model is used to describe the business plan, and the fields are divided into two categories, namely, a feature field and a value field. The business model also has a corresponding data interface, and data can be transferred to the data model for storage. In addition, the business model provides a basis for defining a basic schedule form for business personnel or delivery implementation personnel, the corresponding basic schedule form can be formed according to the business model, the characteristic field of the form forms an information area, and the value field forms a data area. When data are summarized, developers can directly perform background logic processing on the data through the data model, and processing results are directly displayed in the summary schedule.
According to the general compilation method for the business plans, the corresponding business models are respectively constructed for different business plans, the basic plan form is constructed according to the business models, and the structures of the business models and the basic plan form can be flexibly configured according to actual requirements, so that the defect that only one compilation format is available in the past is overcome, and the method is easy to use; different service plan service personnel do not need to adapt to various application scenes any more, universal compilation of different service plans can be realized through a service model, compilation efficiency is improved, development work is not independent for developers, and work overlapping rate is reduced; the data processing is automatic, and the collection level plan number of the collection items and units can be automatically collected and calculated and displayed; and the data model is extracted according to the business model and is used for storing and summarizing the data, so that the data and the business are separated, and the calculation performance is effectively improved.
The above is a method embodiment proposed in the present application. Based on the same inventive concept, the embodiment of the present application further provides a service plan general compilation platform, as shown in fig. 4.
Fig. 4 is a schematic structural diagram of a service plan general compilation platform provided in the embodiment of the present application. As shown in fig. 4, the platform includes a business model building module 401, a data model building module 402, a compiling module 403, and a calculation summary module 404.
In an embodiment of the present application, the business model building module 401 is configured to determine corresponding business models and corresponding basic plan forms, which are respectively pre-built for different business plans; the business model and the basic plan form comprise fields for describing the business plan; the data model building module 402 is configured to extract a feature field and a value field of a service model, and build a data model; the compiling module 403 is configured to compile a basic plan form to obtain an actual plan form including fields describing a service plan and corresponding field values, and synchronize the field values to the data model; the calculation summary module 404 is used for calculating and summarizing data of the data model. The universal compilation of the service plan is completed through the platform, the product platformization is realized, the requirements of modern society on informatization are met, the realization of full-level and full-service plan management is facilitated, and various service requirements are met.
The embodiments in the present application are described in a progressive manner, and the same and similar parts among the embodiments can be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the platform embodiment, since it is substantially similar to the method embodiment, the description is simple, and reference may be made to the partial description of the method embodiment for relevant points.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrases "comprising one of 8230; \8230;" 8230; "does not exclude the presence of additional like elements in a process, method, article, or apparatus that comprises that element.
The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art to which the present application pertains. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.
Claims (7)
1. A method for universal compilation of business plans, the method comprising:
determining corresponding service models which are respectively pre-constructed aiming at different service plans and corresponding basic plan forms; wherein the business model, base plan form include fields describing the business plan;
extracting a characteristic field and a value field of the service model to construct a data model;
compiling the basic plan form to obtain an actual plan form including fields describing the service plan and corresponding field values, and synchronizing the field values into the data model;
performing data calculation and summarization on the data model;
before the base plan form is compiled, the method further includes:
setting a compilation scheme according to the compilation period of the service plan, and forming a compilation task according to the compilation scheme; the compiling task comprises a compiling main body and the basic plan form;
determining that the programming task is in an unprogrammed state;
compiling the basic plan form to obtain an actual plan form including fields describing the service plan and corresponding field values, specifically including:
determining a plurality of detailed plans contained in the business plan; the plurality of detailed plans correspond to the same basic plan form;
according to the content of each detail plan, compiling the basic plan forms respectively to obtain actual plan forms corresponding to the detail plans respectively;
and calculating and summarizing the data of the data model, specifically comprising the following steps:
respectively extracting data in the data model corresponding to each actual plan form;
and according to the hierarchical relation among the actual plan forms, carrying out data summarization on the extracted data of the corresponding fields from the last stage to the previous stage in sequence, and automatically generating the obtained summarized data into the corresponding summarization plan table.
2. The method for universal compilation of business plans according to claim 1, wherein determining the corresponding business models that are respectively pre-constructed for different business plans specifically comprises:
and referencing a default field describing the service plan, adding a specified field according to the service plan, and constructing the service model.
3. The method of claim 1, wherein extracting a feature field and a value field of the business model to construct a data model specifically comprises:
taking a non-numerical field in the service model as a characteristic field, and taking a numerical field as a value field;
and extracting the characteristic field and the value field, and constructing the data model.
4. The method of claim 1, wherein compiling the basic plan form to obtain an actual plan form including fields describing the service plan and corresponding field values comprises:
judging whether the type of the detail plan is an expenditure type;
if yes, determining that the expenditure statistical data in the corresponding actual plan form does not exceed a preset expenditure threshold value.
5. The method for universal compilation of business plans according to claim 1, further comprising:
judging whether the ratio between the actual payment to be paid by the detailed plan and the planned payment is excessive or not according to a preset floating ratio;
and if not, the payment operation is executed through the approval of the detail plan.
6. The method for universal compilation of business plans according to claim 1, further comprising:
and displaying the income and expenditure conditions of the detailed plan corresponding to each actual plan form through a chart.
7. A service planning general compilation platform, to which the service planning general compilation method of any one of claims 1 to 6 is applied, the platform comprising:
the business model building module is used for determining corresponding business models which are respectively pre-built aiming at different business plans and corresponding basic plan forms; wherein the business model, base plan form include fields describing the business plan;
the data model building module is used for extracting the characteristic field and the value field of the business model and building a data model;
the compiling module is used for compiling the basic plan form to obtain an actual plan form which comprises fields describing the service plan and corresponding field values, and synchronizing the field values into the data model;
the system is also used for determining a plurality of detail plans contained in the business plan; the detail plans correspond to the same basic plan form; according to the content of each detail plan, compiling the basic plan forms respectively to obtain actual plan forms corresponding to the detail plans respectively;
the system is also used for setting a compiling scheme according to the compiling period of the service plan and forming a compiling task according to the compiling scheme; the compiling task comprises a compiling main body and the basic plan form; determining that the programming task is in an unprogrammed state;
the calculation and summary module is used for calculating and summarizing data of the data model;
the data extraction module is also used for respectively extracting data in the data model corresponding to each actual plan form; and according to the hierarchical relation among the actual plan forms, summarizing the extracted data of the corresponding fields from the last stage to the last stage in sequence, and automatically generating the obtained summarized data into the corresponding summarizing plan form.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011600689.3A CN112711412B (en) | 2020-12-29 | 2020-12-29 | Universal business plan compiling method and platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011600689.3A CN112711412B (en) | 2020-12-29 | 2020-12-29 | Universal business plan compiling method and platform |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112711412A CN112711412A (en) | 2021-04-27 |
| CN112711412B true CN112711412B (en) | 2023-01-24 |
Family
ID=75546811
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011600689.3A Active CN112711412B (en) | 2020-12-29 | 2020-12-29 | Universal business plan compiling method and platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112711412B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2008065426A2 (en) * | 2006-11-30 | 2008-06-05 | Duncan Bayne | Programming methods for improving browser-based electronic forms |
| CN103258014A (en) * | 2013-04-23 | 2013-08-21 | 浪潮集团山东通用软件有限公司 | Method for working out production plan through network diagram |
| CN110942204A (en) * | 2019-12-04 | 2020-03-31 | 国网安徽省电力有限公司合肥供电公司 | New power grid capital construction project annual planning model construction method and system |
| CN111291939A (en) * | 2020-02-27 | 2020-06-16 | 中国电力科学研究院有限公司 | Method and system for planning links |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090271240A1 (en) * | 2008-04-28 | 2009-10-29 | International Business Machines Corporation | Method and system for strategic headcount planning with operational transition management of workforce |
| CN110457288B (en) * | 2019-07-04 | 2023-06-20 | 平安科技（深圳）有限公司 | Data model construction method, device, equipment and computer readable storage medium |
| CN110825718B (en) * | 2019-10-22 | 2024-02-20 | 天津云景科技股份有限公司 | Information system data architecture model and construction method thereof |
| CN111427971B (en) * | 2020-03-25 | 2024-04-05 | 中国工商银行股份有限公司 | Business modeling method, device, system and medium for computer system |
| CN111913962B (en) * | 2020-07-30 | 2024-03-08 | 浪潮通用软件有限公司 | Multi-dimensional annual detail fund planning system and method |
-
2020
- 2020-12-29 CN CN202011600689.3A patent/CN112711412B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2008065426A2 (en) * | 2006-11-30 | 2008-06-05 | Duncan Bayne | Programming methods for improving browser-based electronic forms |
| CN103258014A (en) * | 2013-04-23 | 2013-08-21 | 浪潮集团山东通用软件有限公司 | Method for working out production plan through network diagram |
| CN110942204A (en) * | 2019-12-04 | 2020-03-31 | 国网安徽省电力有限公司合肥供电公司 | New power grid capital construction project annual planning model construction method and system |
| CN111291939A (en) * | 2020-02-27 | 2020-06-16 | 中国电力科学研究院有限公司 | Method and system for planning links |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112711412A (en) | 2021-04-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Bisschop | AIMMS optimization modeling | |
| CN100568237C (en) | Report form template in the multidimensional enterprise software system generates method and system | |
| CN101111835B (en) | Automated default dimension selection method within a multidimensional enterprise software system | |
| US20160048785A1 (en) | A computer implemented system and method for project controls | |
| CN101111838A (en) | Automated relational schema generation within a multidimensional enterprise software system | |
| KR20080019581A (en) | Cost element managing system | |
| CN110046337B (en) | Financial data acquisition method and system | |
| JP2007011990A (en) | Business portfolio simulation system | |
| US20040078309A1 (en) | Systems and methods for evaluating business cases | |
| Hegazy et al. | Simplified spreadsheet solutions. I: Subcontractor information system | |
| Foster | Cost factors in software maintenance. | |
| Gargiulo et al. | Documentation for the TIMES model part IV | |
| CN112711412B (en) | Universal business plan compiling method and platform | |
| CN114610801A (en) | Generation method of line and column report template | |
| US20040073466A1 (en) | Systems and methods for evaluating telecommunications projects | |
| Goldstein et al. | Documentation for the TIMES model. PART IV: VEDA 2.0 | |
| Firmansyah | Shariah Stock Emitent Efficiency Strategy in Digital Era: Application of DEA Super-Efficiency and Interpretive Structural Modeling | |
| Gay et al. | Automation of Life Cycle Assessment through Configurators | |
| WO2002001393A2 (en) | Dynamic enterprise resource planning chart of accounts and methods for implementing the same | |
| Bellin | Information commodities and the production process: how the introduction of case tools affects the software development life cycle | |
| Ghandforoush et al. | Developing a decision support system for evaluating an investment in fare collection systems in transit | |
| Li et al. | Case-based reasoning approach for decision-making in building retrofit: A review | |
| Densham | Decision support for settlement reorganization | |
| Nguyen et al. | A Review of Life Cycle Assessment Tools for Measuring the Environmental Impact of Building and a Decision Support Framework for Choosing Among Them | |
| Cusack | Time cost models: Their use in decision making in the construction industry with particular reference to the use of the microcomputer |
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 | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20230306 Address after: 250101 Inspur science and Technology Park, 1036 Inspur Road, hi tech Zone, Jinan City, Shandong Province Patentee after: Inspur Genersoft Co.,Ltd. Address before: 250101 Inspur science and Technology Park, 1036 Inspur Road, hi tech Zone, Jinan City, Shandong Province Patentee before: SHANDONG INSPUR GENESOFT INFORMATION TECHNOLOGY Co.,Ltd. |