CN114493488A

CN114493488A - Sharing service center system facing power grid field

Info

Publication number: CN114493488A
Application number: CN202111609874.3A
Authority: CN
Inventors: 张凌志; 敖知琪; 姜唯; 杨漾; 康旖; 刘竹青
Original assignee: Southern Power Grid Digital Grid Research Institute Co Ltd
Current assignee: Southern Power Grid Digital Grid Research Institute Co Ltd
Priority date: 2021-12-25
Filing date: 2021-12-25
Publication date: 2022-05-13

Abstract

The invention relates to a power grid field-oriented shared service center system in the technical field of power grid service management systems, which comprises a multi-dimensional service model unit, a shared service modeling unit and a shared service meta-model unit, wherein the multi-dimensional service model unit classifies services based on service types and constructs a multi-dimensional service model, the shared service modeling unit is used for modeling services based on service scenes, the shared service meta-model unit constructs a shared service meta-model based on the shared service modeling unit to structurally manage related assets, and the basic forms of shared services and services are agreed to form standard and clear definitions of elements related to the shared services and services. The method has the advantages that the service change is used as traction, the process drive is changed into the scene drive, the definition commonality and the personalized service requirements are effectively identified, new service requirements are continuously mined and the service implementation process is optimized through data, the flexible configuration of the service scene is enabled, and the realization of the service asset is facilitated.

Description

Sharing service center system facing power grid field

Technical Field

The invention relates to the technical field of power grid service management systems, in particular to a sharing service center system facing to the field of power grids.

Background

In recent years, the fourth industrial revolution of the integration of digital technologies such as cloud computing, big data, internet of things, artificial intelligence and the like and industry is emerging, and the social and economic big environment and the traditional operation mode of enterprises are deeply impacted.

The aim of company digital transformation is to mine a digital transformation adaptability scene, achieve 'double driving' of technical driving and business demand driving, enable the numbers and data to really become production elements, promote service innovation and business model innovation, and enable digital economy to become a new benefit growth point of companies. On one hand, for traditional business of a company, the 'rotation to the utmost extent' is required, and business process reconstruction and scene service transformation are promoted from the company perspective; on the other hand, for a new business developed by a company, "do not go around," should be newly constructed in a "digitized" manner directly based on a new technology platform.

Therefore, a scientific, consistent and reasonable service modeling system needs to be established to change service into traction, change from 'process drive' to 'scene drive', effectively identify and define commonalities and personalized service requirements, continuously excavate new service requirements and optimize a service implementation process through data, enable flexible configuration of service scenes, help to realize service assets, promote continuous deepening of company digital transformation and digital power grid construction, and promote accelerated implementation of a strategy goal of company 'three-business' transformation.

Based on the above, the invention designs a sharing service center system facing to the power grid field, so as to solve the above problems.

Disclosure of Invention

The invention aims to provide a shared service center system facing the field of power grids, so as to solve the problems in the background technology.

In order to achieve the purpose, the invention provides the following technical scheme: a sharing service center system facing the power grid field comprises a multidimensional service model unit, a sharing service modeling unit and a sharing service meta-model unit, wherein the multidimensional service model unit classifies services based on service types and constructs a multidimensional service model, the sharing service modeling unit is used for modeling and processing the services based on service scenes, and the sharing service meta-model unit constructs a sharing service meta-model based on the sharing service modeling unit, so that personnel participating in sharing service combing and service construction can describe the services and services by using a uniform language and perform structured management on related assets, and appoint the basic forms of the sharing services and services to form standard and clear definitions of various elements related to the sharing services and services.

In the above power grid field-oriented shared service center system, the multidimensional service model unit includes a service scenario component, a service capability component, and a service identity component, where the service scenario component is used to distinguish service flows, the service capability component is used to identify a service target and provide a method and means required for completing the service target, and the service identity component defines an identity type of a service activity.

In the above power grid field-oriented shared service center system, the service identity component defines the identity type of the service activity based on the difference between the steps and the rules and the personalized requirements.

In the above power grid domain-oriented shared service center system, the shared service modeling unit includes a service model combing component, an individualized requirement combing component, and a shared service design component, where the service model combing component is used to define a service scene, a service capability, a service activity, and a service object, the individualized requirement combing component is used to define a service identity, identify a service difference, and define a service extensible point definition, and the shared service design component is used to design a service sharing service and a data sharing service.

In the above power grid domain-oriented shared service center system, the shared service meta-model unit includes a design-state architecture component, an operation-state architecture component, and a management-state architecture component, where the design-state architecture component includes a service scene, a service capability, a service activity, a service identity, a service object, a domain model, a logic model, and a physical model. And identifying architecture elements from the business model and the data model, wherein the operation state architecture component comprises a business sharing service and a data sharing service. The business sharing service and the data sharing service have a mapping relation, and the management-state architecture component comprises a center, a service library, a first-level service classification and a second-level service classification. And performing four-level grading according to a design method of top-down and layer-by-layer decomposition for service classification and collection management.

Compared with the prior art, the invention has the beneficial effects that: the service change is used as traction, the process drive is changed into the scene drive, the definition commonality and the personalized service requirement are effectively identified, the new service requirement is continuously mined and the service implementation process is optimized through data, the flexible configuration of the service scene is enabled, and the realization of the service asset is facilitated.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without creative efforts.

FIG. 1 is a schematic view of the frame structure of the present invention;

FIG. 2 is a schematic diagram of a framework structure of a multi-dimensional business model unit in the present invention;

FIG. 3 is a schematic diagram of a framework structure of a shared business modeling unit according to the present invention;

FIG. 4 is a diagram of a framework structure of a shared service meta-model unit according to the present invention.

In the drawings, the components represented by the respective reference numerals are listed below:

1-a multi-dimensional business model unit, 11-a business scene component, 12-a business capability component, 13-a business identity component, 2-a shared business modeling unit, 21-a business model combing component, 22-an individual requirement combing component, 23-a shared service design component, 3-a shared service meta model unit, 31-a design state framework component, 32-an operation state framework component and 33-a management state framework component.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the 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 invention.

Referring to fig. 1-4, the present invention provides a technical solution: a sharing service center system facing to the power grid field comprises a multi-dimensional service model unit 1, a sharing service modeling unit 2 and a sharing service meta model unit 3, wherein the multi-dimensional service model unit 1 classifies services based on service types and constructs a multi-dimensional service model, the multi-dimensional service model unit 1 comprises a service scene component 11, a service capacity component 12 and a service identity component 13, the service scene component 11 is used for distinguishing service processes, the service capacity component 12 is used for identifying service targets and providing methods and means required by service target completion, the service identity component 13 defines the identity type of service activities based on the difference in steps and rules and personalized requirements, for example, organization is used as the service identity type, the service identities are defined as an A power supply bureau, a B power supply bureau and the like, the sharing service modeling unit 2 is used for modeling services based on service scenes, the sharing service meta-model unit 3 constructs a sharing service meta-model based on the sharing service modeling unit 2, so that personnel participating in sharing service combing and service construction can describe services and services by using a uniform language, related assets are structurally managed, basic forms of the sharing services and services are agreed, and standard and clear definitions of all elements related to the sharing services and services are formed.

The shared business modeling unit 2 comprises a business model combing component 21, an individualized requirement combing component 22 and a shared service design component 23, wherein the business model combing component 21 is used for defining business scenes, business capabilities, business activities and business objects, and combing company-level core business around company core business directions of asset life-expectancy, client omnibearing, energy overall process, core resource intensification and the like according to a company strategic development schema. The method comprises the steps of defining a core service scene, such as a 'patrol inspection scene' and a 'customer electricity access' scene, by taking a company-level core service as a framework and taking an event-type service flow in a service architecture as input. And adjusting and perfecting the scene according to the requirement by combining the actual service condition. On one hand, the service scenes with higher homogenization degree can be merged into the same service scene; on the other hand, if there is a definite connection relationship between the processes, the processes can be connected in series to form a complete service scene. For example, in consideration of the similarity degree of the process and the management mode, scenes such as "large-customer business expansion installation", "low-voltage resident business expansion installation" and "low-voltage non-resident business expansion installation" are merged to form a "customer electricity access" scene, and a business capability system is formed by combing the input of function business processes in the business architecture. And screening functional business processes in the business architecture, identifying and adjusting corresponding business items into business capabilities, and defining specific connotation of the business capabilities according to the contained business processes. For example, the 'charging management' capability refers to the service model specification based on the service scenario, and according to the service activity definition, the end-to-end process is disassembled to the process node granularity, and is refined to form the service activity. Based on the identified service capability, the core service activities are correspondingly collected with the existing service capability one by one, and service objects, such as 'operation plan' and 'equipment', are identified and extracted according to the steps, service forms, service rules and the like of each common service activity. And (4) detailing the business object description, and defining and containing the attribute clearly. The personalized requirement combing component 22 is used for defining business identities, identifying business differences and defining business extensible point definitions, the shared service design component 23 is used for designing business shared services and data shared services, the business identities are formed by combining a plurality of business attributes and used for identifying different steps and rules of business activities, different business identities are defined for each business for supporting quick iterative innovation of the businesses, and differential customization among the businesses is allowed. For example, the definition category is "organization", the combing business identity is "A power supply office" and "B power supply office", and step differences in the same business activity and business rule differences in the same step are identified based on the business identity. For example, different power supply offices have differences in the specific steps of the activity of "generating a job plan", and the rules of the same steps may also be different, so that the support service extends own specific activity steps and service logic on the basis of the public service activity, and the places where the extension can be performed are called service extension points. Based on the differences in steps and rules, business extensible points are defined, allowing implementation of different steps and rules, thereby completing the service design. The extension points can be configured through rule configuration or code extension, and shared service design can be developed based on the shared business model carding result. And based on the extracted business activities, preliminarily defining and forming business sharing services by referring to business objects related to the activities. In principle, one core business activity corresponds to one business sharing service. And developing a business sharing service design, realizing business logic in the service, and definitely performing the data sharing service required to be called by data reading and writing. The method is characterized in that services multiplexed in two or more functions are called shared services, a unified data model is used as a basis, data access requirements of service shared services and data access requirements of application functions are used as input, the data access requirements are collected and sorted, and interface types required by the data shared services are defined, such as single newly added, single modified, single deleted, newly added in batches, modified in batches, deleted in batches, inquired and the like data shared services. On the basis, input and output of the service are determined. The shared service meta-model unit 3 includes a design-state architecture component 31, a run-state architecture component 32, and a management-state architecture component 33, where the design-state architecture component 31 includes a business scenario, a business capability, a business activity, a business identity, a business object, a domain model, a logic model, and a physical model. From the business model and the data model, the architectural elements are identified, and the runtime architectural component 32 includes a business sharing service and a data sharing service. The business sharing service and the data sharing service have a mapping relationship, and the management-state architecture component 33 includes a center, a service library, a primary service classification, and a secondary service classification. According to a design method of top-down and layer-by-layer decomposition, four-layer grading is carried out for service classification and collection management, and design state architecture elements comprise a service scene, service capability, service activity, service identity, a service object, a domain model, a logic model and a physical model. From the business model and the data model, architectural elements are identified.

(1) Business scenario

The service scene is a service flow of events which are developed by completing a certain service target, have definite event start and termination and independently occur, such as a patrol inspection scene and a customer electricity access scene. A business scenario is composed of multiple business activities.

(2) Business capability

The business capability refers to a functional unit formed by abstracting and refining a working method and a means required by an enterprise to achieve a certain business goal. Such as job plan management capabilities. A single business capability may be decoupled to multiple business activities.

(3) Business activity

The business activity represents a process node, is completed by a single organization unit or role, and has definite input and output, such as generating a patrol operation plan. In principle, one business activity corresponds to one business sharing service; the input and output of business activity relate to one or more business objects; the execution steps or rules of the same business activity may be different for different business identities.

(4) Service identity

The business identity is composed of a plurality of business attributes, which generally refer to organization, channel, object type, etc., and is used for distinguishing the difference of business activities in steps and rules. The service identity is used for realizing personalized customization of the service sharing service, and different service identities are allowed to expand own special activity steps or realization rules in the service sharing service.

(5) Business object

Refers to a process object or an event object in a business activity, such as a device, a job plan, etc. The business objects, attributes, and their relationships constitute the inputs to the logic model design.

(6) Domain model

A domain model is a visual representation of concept classes within a domain or objects in the real world. The structured representation of the objects and their relationships by the domain model can be used as input to the design of the data model.

(7) Logical model

The logic model is composed of a group of entities and relations thereof, the entities have attributes, and the attributes are composed of standard data elements and information classification codes. The logical model describes the logical structure of the data and guides the physical implementation of the data.

(8) Physical model

The physical model is based on the logical data model, and considers various specific technical realization factors to design the database architecture, thereby really realizing the storage of data in the database. Based on the physical table, a data sharing service corresponding to the table entity can be generated.

The operation state architecture elements comprise business sharing services and data sharing services. The business sharing service and the data sharing service have a mapping relation.

(1) Business sharing service

The service sharing service provides operations with service meanings, such as dispatching, payment, credit rating evaluation and the like, for service application, and takes the role of service instruction allocation and scheduling. According to the business object, one business sharing service corresponds to one or more data sharing services; generally, if a business application needs to write data, the business application needs to process the data through the business sharing service and then call the data sharing service to write the data.

(2) Data sharing service

The data sharing service provides access operations to data without business logic, including adding, deleting, modifying, querying and the like, such as adding a single production plan and assuming a data interaction role. The business sharing service has to invoke the data sharing service if data access is needed.

The management-state architecture element comprises a center, a service library, a primary service classification and a secondary service classification. And performing four-level grading according to a design method of top-down and layer-by-layer decomposition for service classification and collection management.

(1) Center of a ship

The center is a service management module formed according to the division of the current company functions, and comprises an equipment center, a contract center, a project center, a client center, a financial center, a personnel center and the like. A single center contains multiple service libraries, primary service classes, secondary service classes, and services.

(2) Service library

The service libraries are large service capacity classes facing the center and are divided according to company-level core business management objects, such as an equipment service library, a contract service library and the like. A single service library may be subdivided into a plurality of primary service classes.

(3) Class one service classification

The primary service classification is a collection of a certain class of services in a service library, and is generally divided according to the management process state of an object. Such as a job plan management service. A single primary service library may be split into one or more secondary service classes as needed.

(4) Secondary service classification

The secondary service classification is a further refinement of the primary service classification, and is generally divided according to object types or business classifications and the like. Such as a job planning management service. The secondary service class is the minimum unit of the service class and comprises a plurality of business sharing services and data sharing services.

In the description herein, references to the description of "one embodiment," "an example," "a specific example" or the like are intended to mean that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the invention. In this specification, the schematic representations of the terms used above do not necessarily refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. The preferred embodiments of the invention disclosed above are intended to be illustrative only. The preferred embodiments are not intended to be exhaustive or to limit the invention to the precise embodiments disclosed. Obviously, many modifications and variations are possible in light of the above teaching. The embodiments were chosen and described in order to best explain the principles of the invention and the practical application, to thereby enable others skilled in the art to best utilize the invention. The invention is limited only by the claims and their full scope and equivalents.

Claims

1. A sharing service center system facing the power grid field is characterized by comprising a multidimensional service model unit (1), a sharing service modeling unit (2) and a sharing service meta-model unit (3), wherein the multidimensional service model unit (1) classifies services based on service types, and construct a multi-dimensional business model, the shared business modeling unit (2) is used for modeling the business based on the business scene, the sharing service meta-model unit (3) constructs a sharing service meta-model based on the sharing service modeling unit (2), so that personnel participating in sharing service combing and service construction can describe services and services by using a uniform language, and the related assets are managed in a structuralized mode, the basic forms of the sharing service and the service are agreed, and the standard and clear definition of all elements related to the sharing service and the service is formed.

2. The grid-domain-oriented shared service center system according to claim 1, wherein the multidimensional business model unit (1) comprises a business scenario component (11), a business capability component (12), and a business identity component (13), the business scenario component (11) is used for distinguishing business processes, the business capability component (12) is used for identifying business targets and providing methods and means required for completing the business targets, and the business identity component (13) defines identity types of business activities.

3. The grid-domain-oriented shared service center system according to claim 2, wherein the business identity component (13) defines the identity type of the business activity based on the difference in steps and rules, personalized requirements.

4. The grid-domain-oriented shared service center system according to claim 1, wherein the shared service modeling unit (2) comprises a business model combing component (21), a personalized requirement combing component (22), and a shared service design component (23), the business model combing component (21) is used for defining business scenes, business capabilities, business activities, and business objects, the personalized requirement combing component (22) is used for defining business identities, identifying business differences, and defining business extensible point definitions, and the shared service design component (23) is used for designing business shared services and designing data shared services.

5. The grid-domain-oriented shared service center system according to claim 1, wherein the shared service meta-model unit (3) comprises a design-state architecture component (31), a run-state architecture component (32), and a management-state architecture component (33), and the design-state architecture component (31) comprises a business scenario, a business capability, a business activity, a business identity, a business object, a domain model, a logical model, and a physical model. From the business model and the data model, architectural elements are identified, and the runtime architectural component (32) comprises a business sharing service and a data sharing service. The business sharing service and the data sharing service have a mapping relation, and the management state framework component (33) comprises a center, a service library, a primary service classification and a secondary service classification. And performing four-level grading according to a design method of top-down and layer-by-layer decomposition for service classification and collection management.