WO2010022758A1

WO2010022758A1 - Method and device for processing data and system comprising the device

Info

Publication number: WO2010022758A1
Application number: PCT/EP2008/007208
Authority: WO
Inventors: Sonja Auer; Hans-Joachim Diehl; Werner HÖFLER; Juliane Rettner; Earl Roethke; Rainer RÜDIGER
Original assignee: Siemens Aktiengesellschaft
Priority date: 2008-08-27
Filing date: 2008-08-27
Publication date: 2010-03-04

Abstract

A method for processing data is provided in which a user is provided with a context-based entry possibility for processing a task and in which with the selection of the task the task is started or loaded in a current processing state. Furthermore, an associated device and a system with such a device are specified.

Description

description

Method and device for data processing and system comprising the device

The invention relates to a method and a device for data processing as well as a system comprising the device.

Complex work tasks within a comprehensive system for modeling in particular an energy network are preferably to be structured or structured. The aim of this structuring is to identify work packages (so-called "jobs") that can be processed individually.

In existing systems and applications, it is disadvantageous that the user is offered no information about the content of a job or about work steps to be performed. In addition, the jobs are detached from the actual task processing. Thus, the user loses a lot of time to navigate to a relevant work area and to find needed data.

Existing applications or entry portals have the disadvantage that the user does not find the relevant information for him. Rather, such entry portals allow only universal access for general tasks.

The object of the invention is to avoid the abovementioned disadvantages and in particular to create a user-efficient option for processing tasks, work packages or jobs.

This object is achieved according to the features of the independent claims. Further developments of the invention will become apparent from the dependent claims. To solve the problem, a method for data processing is created,

- offering a user a context-based entry opportunity for processing a task;

- in which the task is started or loaded with a selection of the task in a current processing state.

In particular, the context-based embargo may take into account a context of the user or a group of users. For example, a profile may be associated with the user or with the group that allows certain actions and possibly prohibits (partially) administrative actions. The context-based emigration possibility is linked in particular to at least one such profile, so that, for example, a flexibly configurable individualization is made possible for the user or the group of users.

The task can be selected and with the selection, the processing of the task starts in particular such that the task is started or loaded in the current state of processing. Thus, the user can call up a task that is already in the process of being processed, depending on its processing status, and continue at this point. It is also possible to start processing a task that has not yet started.

Accordingly, a multiplicity of tasks can be offered via the context-based accessibility and at least partially selected by the user.

Thus, comprehensive and complex tasks can be mastered, in particular it is possible to efficiently coordinate users working simultaneously. A development is that parameters and / or data are loaded, which are linked to the processing state of the task.

Advantageously, the user (corresponding to the group of users) can be offered context-dependent data for processing the task. As a result, a cumbersome and time-consuming navigation for the user is avoided. Ideally, the user will find all (or at least part of) the information needed for processing in the form of data and parameters when processing the task. For example, this information may be linked or provided via submenus or pop-up windows.

Another development is that a comprehensive task management is carried out for several tasks based on several processing states.

Thus, advantageously, a user or an administrator can be offered and / or presented with an efficient overview of the status of one or more tasks.

Preferably, such tasks include several steps, e.g. a data entry, a validation of the data entries as well as an activation of the data entries.

In particular, it is advantageous that interruptions in the execution of the task cause no additional effort for the users. Each user is preferably provided with the scope of his work or a next task to be completed by means of the approach presented here.

Thus, the present approach allows the user a direct entry into his work, ie access to an area of the application in which he can carry out his work as well as the user an indication or access to information required for the task ( Data and / or parameters). Furthermore, it is advantageous that the user, in addition to the mentioned access to the area of the application, also has flexible access (for example, without an assigned work package) to available work areas and can thus process queries or tasks spontaneously.

A development is that a state information for the task is determined and / or displayed.

In particular, a degree of fulfillment of the task can be determined and displayed as state information. Advantageously, a plurality of status information can be evaluated cumulatively over a plurality of tasks (including across multiple users or groups of users). Thus, it is possible to determine and represent a degree of completion for a project comprising a variety of tasks. This information can be generated automatically at any time, so that e.g. For the job management (quasi) it is continuously known to what extent the entire project (or parts thereof) is within a given timeframe.

Another development is that several tasks are summarized in a work package.

In particular, it is a development that recurring tasks or recurring types of tasks are organized as templates.

Preferably, the context-based entry-level facility may have a workspace or a selection facility for the administration of the templates. Hereby the templates can be edited or new tasks corresponding to a template can be created.

It is also a development that the context-based entry possibility is offered by means of a homepage or by means of a portal. In particular, the context-based entry possibility may be via a browser platform (eg a web application or via an Internet or an intranet) provided and / or addressed.

Furthermore, it is a further development that the user stands out.

In particular, the user can authenticate himself before accessing the homepage. On the one hand, this represents a secure access to the user's individualized data, on the other hand, the application recognizes the user and can display relevant data, in particular tasks. Depending on the authorization of the user, certain parts of an application can be shown or hidden.

It should be noted that the user can also be a group of users. In particular, the group of users may comprise a plurality of users, the group having certain common features (e.g., processing a (sub) project comprising certain tasks). Optionally, nevertheless, each user of the group can be individually recognized by the application and it can be offered in this regard, at least partially, an individual context-based interface or homepage.

As part of an additional training, the context-based entry opportunity has at least one of the following work areas:

- A work area comprising currently pending and / or completed tasks; - a work area comprising a management of templates;

- a work area containing general information;

- A work area comprising a management of tasks and / or work packages.

A next development is that the work areas are flexible to each other can be arranged. In particular, the method described herein may be implemented as a program executable on a computer. Preferably, such a program can be executed on several computers of a network. In particular, several computers of the network can access the program. Advantageously, the program is designed so that a multiplicity of users can use the program or the method described here via several computers of a network. Said network may preferably comprise the Internet and / or a LAN.

The above object is also achieved by a device for processing a data unit comprising a processor unit and / or an at least partially hardwired circuit arrangement, which is set up such that the method can be carried out as described herein.

Said processor unit can be or comprise any type of processor or computer or computer with correspondingly necessary peripherals (memory, input / output interfaces, input / output devices, etc.). Such a processor unit can be provided, in particular, in a communication device, which in particular has a receiver or a transceiver.

Furthermore, a hardwired circuit unit, e.g. an FPGA or ASIC or other integrated circuit may be provided.

The device can be used in power engineering. It is also possible that the device is used for example in the field of industrial automation or medical technology.

Furthermore, to solve the problem, a system is provided comprising a device as described herein. Ausfülängsbeispiele of the invention are illustrated and explained below with reference to the drawings.

Show it :

1 shows a schematic representation of an entry page as a portal (preferably after an authentication of a user);

FIG. 2 shows a schematic illustration comprising work areas for the administration of templates; FIG.

A schematic representation of the display of work package specific information.

The approach presented here makes it possible for one or more users (an application) to carry out a comprehensive job management, comprising in particular at least one of the following tasks:

(a) Work packages (jobs) are logically divided into individual tasks.

(b) Optionally, recurring types of work package can be systematically managed using templates.

(c) Work packages or tasks are assigned to individual users. Here, a large number of work packages or tasks can also be assigned to a user.

(d) A processing status for tasks and work packages is logged.

(e) Based on the logged processing status, the status of the work package or each task can be provided eg via a user interface. In particular, processing status information about several work packages can be cumulatively evaluated and / or Thus, we are presented with status information, eg a degree of fulfillment (in percent) for an overall project comprising several work packages.

For example, the generated or compiled information can be offered and / or displayed via a user interface.

An example of such a user interface is an entry page or a portal. Here, the user can be presented with current work packages that are specifically relevant for the user and / or tasks assigned to this user. Preferably, the user previously identifies himself in the portal by means of a suitable login (authentication). For example, the user can log in using a password. Accordingly, different forms of logon or identification (e.g., by biometric and / or smart card) may be used.

The portal preferably provides the user with a current processing status for his tasks and / or work packages. The tasks and / or work packages are preferably linked to relevant or required parameters and / or data. By way of example, when a work package is selected, a processing mask can be selected and displayed which has context-related parameters or data or links to it. This allows easy and efficient navigation for the user to handle his tasks or work packages.

Another example of the user interface relates to the task areas comprising, e.g.

a user interface for defining and managing recurring work package types, in particular suitable for administrative use and / or for administrative users;

- an administrative user interface for assigning work packages to individual (or more) Users as well as (preferably this function for administrative users translated) for monitoring and / or processing status Tracking the users of the work packages and Aufga ^¬ ben for each user or for each user or for a specified group of users;

a user interface for displaying specific information for a work package (or task) and a way to modify the work package (or task).

As soon as you get started with the application, the user will be offered or displayed the selected or relevant work packages with the corresponding tasks. From this results for the user clearly and clearly, which

Tasks have already been partially or completely completed and which tasks still need to be processed. By selection, e.g. By means of a mouse click, the user can start or continue directly with the processing of the desired work package or the desired task.

In addition, all user-accessible workspaces of the application can be displayed on the entry page, eg. concerning a data maintenance or a user administration. Workspaces to which the user should not have access (i.e., for which the user has no rights) are not mapped. As a result, the presentation is not unnecessarily complicated and the user preferably deals only with information that is also relevant to him.

The user thus receives an overview of all work areas available to him via the user interface and can thus react flexibly to short-term tasks that are different, in particular, from the work packages or their tasks. Preferably, a work area is provided comprising work package-specific information for the user, another work area concerns, for example, a management of templates (in particular suitable for an administrative user).

Fig.l shows an example of a schematic representation of an entry page as a portal (preferably after an authentication of the user).

There are three workspaces:

A workspace 101 concerns access to further workspaces;

a workspace 102 concerns current work (work packages and related tasks);

a work area 103 relates to general information, e.g. a username, product name or project name.

Preferably, the arrangement of the work areas 101, 102 and 103 (horizontal and vertical) is made variable. For example, in favor of an intuitive operation, the presentation of the general information 103 can take place at the upper edge of the screen. The current work 102 can be shown in the left or in the lower area.

An interaction on the portal can include the following steps:

- A mouse click on a work area 101, 102, 103 opens a further representation of this work area; while the portal can be hidden or covered.

A mouse click on a work package 104 opens a display of information regarding this work package 104.

- A mouse click on an arrow 105 left of the work package is the associated tasks and ih ^¬ ren respective status. - A mouse click on a task 106 opens the corresponding work area and displays the data and / or parameters required to complete the task. - A mouse click on a down arrow

107 hides the tasks associated with the work package again.

The user interface for defining and managing recurring work package types is preferably provided to users with administrative tasks or authority. It serves for systematic work package structuring. New work packages can be created or existing work packages can be changed.

Preferably, the work area 103 is reserved for application-overlapping actions and information.

2 shows a schematic representation for the management of templates.

In a workspace 201, the existing templates are displayed grouped. Details of a selected template may be displayed in the workspace 202. In the working area 202, the corresponding tools for adapting the template can also be displayed.

An interaction can include the following steps:

- The work packages of a group can be displayed by a mouse click on an arrow 203 in front of the group name or hidden by a mouse click on a rotated arrow 204.

- A mouse click on a work package 205 updates the workspace 202 with the details of this selected work package.

- A processing of the work package can be done within the work area 202. For example a task can be added to or removed from the work package.

The work package-specific information display user interface provides the user with information about work packages (e.g., a due date or a work history) and the tasks contained in the work package (e.g., a description of the task and a workspace where this task is to be done). Optionally, the user can modify work packages and related tasks.

Preferably, the user is provided with a filtered list that includes work packages that are relevant for him and that the user directly displays. By means of a selection box, the user can also display work packages of other users. It is also possible to create a new work package. This option allows the user to flexibly edit work packages that as such are not yet included in the system or that are only needed for test purposes.

3 shows a schematic representation for the display of work package-specific information. Current work packets are displayed, for example, in a work area 301, and associated detailed information in a work area 302.

An interaction may include the following steps: - A mouse click on a work package 303 updates the workspace 302 with the details of the selected work package.

- A mouse click on a task 304 opens a workspace as well as data that the user needs to complete the selected task 304. Here, the open work area may be at least partially overlap the previous working ^¬ area. In the work area 302, information of the selected work package 303 is displayed, eg a comment or a due date. Possibly. The displayed information can be edited (changed, created and / or deleted) or changed according to its processing order.

- Changing a filter criterion via a selection box 305 updates a list 307 of the work packages according to the changed filter criterion. A switch "New" 306 adds a new work package to the list 307. In workspace 302, information about the new work package is entered.

Preferably, the portal includes job management that informs the user of pending and completed tasks. In this case, the user can, for example, only inform himself about his own or about all or about jobs of certain (other) users. Advantageously, the user is presented with a cumulative processing status, so that the user can quickly obtain an overview of a project comprising a large number of work packages and tasks.

The portal allows the user fast and direct access to required work areas as well as required data and / or parameters.

The present approach efficiently enables configuration through job management functionality. Thus, work packages can be assigned to different users and the processing status of the work packages can be monitored.

Preferably, work areas are further provided, which allow management, creation, modification and / or assignment of the work packages.

The approach presented herein further allows the following advantages: (1) Job management allows coordination of complex configurations for a variety of users. Systematically, additional work can be reduced by template-based work packages. Also, overlapping activities can be easily identified and distributed to users.

(2) Pending work packages and tasks are clearly and transparently defined and distributed. As a result, incorrect entries and misunderstandings can be avoided efficiently.

(3) A high level of quality of work can be achieved through a systematic approach and reusable templates.

(4) A status of completed and ongoing work packages and tasks can be determined at any time. Thus, e.g. An administrative user always has an overview of the processing status of the sum of the work packages or individual work packages and tasks.

(5) The presentation of the tasks to be processed gives a quick overview of tasks to be completed. This makes efficient work possible, and erroneous to-do lists can be omitted.

(6) The direct entry into the workspaces shortens the task processing. There is no need to switch between texts, the user will find all the necessary data where he needs them to do his work. This leads to significant time savings through efficient context-based navigation.

Examples: For the approach presented here, there are a variety of applications.

For example, a portal with an entry page with several workspaces can be provided for a data engineer

- an administrative workspace with the sub-fields "Templates for Jobs", "User Administration", "System Installation" and "Domain Data Administration";

- a general work and information area with the subfields "Domains Data Report", "Display", "Reports" and "Job Administration";

- A job report regarding own jobs, where the jobs are grouped under the lists "New

Substation for Toronto "and" New Substation for Ottawa ".

As soon as all the jobs in a list have been completed, this is marked with a checkmark on the left-hand side of the list (and with a checkmark for each task or work package in the list). Open jobs or open tasks, for example, are marked with a construction worker icon.

Another example concerns the definition and management of templates for recurring work packages. In a first workspace, the user receives a thematically structured overview of existing templates for work packages. The currently selected work package can be marked. In a second workspace, adjustments can be made to the selected work package, e.g. Remove tasks, sort tasks, add new tasks, describe tasks or work package.

Another example relates to a display of work package specific information. In a first workspace, the user sees the currently assigned work packages. By means of a button "Create New Job" the user can define a new work package. A selection box "Filter" allows the user to access work packages of other users. In a second work area, information is presented that describes the chosen work package in more detail, for example, based on a status, by means of a responsible user and / or on the basis of a due date. Also, a list of assigned tasks is shown in the second workspace with a direct entry (link) to a completion or processing of the task.

Another example concerns a user interface for a "data maintenance" task area. Accordingly, a graphical user interface can be provided which displays to the user the workspace needed to complete the selected task together with the data and / or parameters required for the execution. The user does not have to worry about further elaborate navigation, but can immediately start to complete his tasks in the environment of the required data and / or parameters. For each workspace, a specific interface may be provided.

Claims

claims

1. Method for data processing,

- offering a user a context-based entry opportunity for processing a task;

- in which the task is started with a selection of the task in a current processing state.

2. The method of claim 1, are loaded in the parameters and / or data associated with the processing state of the task.

3. The method according to any one of the preceding claims, in which a comprehensive task management is performed based on several processing conditions for multiple tasks.

4. The method according to any one of the preceding claims, in which a status information for the task is determined and / or displayed.

5. The method according to any one of the preceding claims, in which several tasks are summarized in a work package.

A method according to any one of the preceding claims, wherein recurring tasks or recurring types of tasks are organized as templates.

7. The method according to any one of the preceding claims, wherein the context-based entry opportunity is offered by means of an entry page or by means of a portal.

8. The method according to any one of the preceding claims, wherein the context-based entry opportunity is addressed via a browser platform.

9. The method according to any one of the preceding claims, wherein the user authenticates.

10. The method according to any one of the preceding claims, wherein the context-based Ausstiegsmoglichkeit has at least one of the following work areas:

- A work area comprising currently pending and / or completed tasks;

- a work area comprising a management of templates;

- a work area containing general information;

- A work area comprising a management of tasks and / or work packages.

11. The method of claim 10, wherein the work areas are flexibly arranged to each other bar.

12. A data processing apparatus comprising a processor unit and / or an at least partially hardwired circuit arrangement, which is set up such that the method according to one of the preceding claims durchfuhrbar.

13. System comprising a device according to claim 12.