# US 2006/0156275 A1 · System and method for rule-based distributed engineering

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2006/0156275 A1
- Document ID: US20060156275A1
- Status: Published application
- Kind: A1
- Application number: 11/313,129
- Filed: 2005-12-20
- Published: 2006-07-13
- Earliest claimed: 2004-12-21
- Assignees: Siemens Aktiengesellschaft
- Inventors: Ronald Lange; Ralf Leins; Klaus Meusser; Jurgen Schmoll; Markus Weinlander
- Web page: https://patentgrep.com/patent/US20060156275A1

## CPC

- G05B 19/41865: {characterised by job scheduling, process planning, material flow}
- G06Q 10/10: Office automation; Time management
- Y02P 90/02: Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]
- G05B: CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS (systems for controlling or regulating non-electric variables G05D; systems for regulating electric or magnetic variables G05F; control devices or systems insofar as characterised by mechanical features only G05G)
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- Y02P: CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS

## Abstract

The invention relates to a system and a method for providing specifications for a project, in particular for an engineering project for creating an automation solution. The system comprises first means for creating a file containing the specifications and at least one project planning environment for creating a solution on the basis of the specifications, with the file containing the specifications being imported into the at least one project planning environment as meta knowledge. A simple provision of specifications to be used for a project is hereby enabled.

## Claims

### Claim at position 1

-18. (canceled)

### Claim 19

A system for providing specifications for a project, comprising:
a file generator for creating a file including specifications for the project; and
at least one project planning environment for creating a project solution based on the specifications, wherein the file is imported into the project planning environment in the form of meta knowledge data.

### Claim 20 (depends on 19)

The system according to claim 19, wherein the project is an engineering project for creating an automation solution.

### Claim 21 (depends on 19)

The system according to claim 19, wherein the project planning environment includes an evaluation unit for evaluating the file.

### Claim 22 (depends on 19)

The system according to claim 19, wherein the file generator is configured to generate different specifications for different subprojects.

### Claim 23 (depends on 19)

The system according to claim 19, wherein the specifications are rules or restrictions.

### Claim 24 (depends on 21)

The system according to claim 21, wherein the evaluation unit is configured to bar the input of non-admissible inputs into the project planning environment.

### Claim 25 (depends on 21)

The system according to claim 21, wherein the evaluation unit is configured to use the specifications as a test algorithm.

### Claim 26 (depends on 25)

The system according to claim 25, wherein the project planning environment is configured to generate a list of non-compliances relative to the specifications.

### Claim 27 (depends on 19)

The system according to claim 19, wherein the file is updated and the updated file is imported into the project planning environment.

### Claim 28 (depends on 19)

The system according to claim 19, wherein the specifications are used for supplementing library elements included in a library, the library assigned to a client demanding the specifications.

### Claim 29

A method of providing specifications for a project solution, comprising:
generating a file including the specifications;
importing the file into at least one project planning environment as meta knowledge; and
creating the project solution based on the specifications using the meta knowledge.

### Claim 30 (depends on 29)

The method according to claim 29, wherein the file is generated by a client ordering the project solution.

### Claim 31 (depends on 29)

The method according to claim 29, further comprising evaluating the file by the project planning en-vironment.

### Claim 32 (depends on 29)

The method according to claim 29, further comprising creating different specifications for different subprojects.

### Claim 33 (depends on 29)

The method according to claim 29, wherein the specifications are rules or restrictions.

### Claim 34 (depends on 29)

The method according to claim 29, further comprising rejecting inadmissible entries by the project planning environment.

### Claim 35 (depends on 29)

The method according to claim 29, further comprising using the specifications as a test algorithm.

### Claim 36 (depends on 35)

The method according to claim 35, further comprising generating a list of non-compliances relative to the specifications by the project planning environment.

### Claim 37 (depends on 29)

The method according to one of claims 29, further comprising updating the file and importing the updated file into the at least one project planning environment.

### Claim 38 (depends on 29)

The method according to claim 29, further comprising supplementing library elements by the specifications, the library elements included in a library assigned to a client demanding the specifications.
