Show TOC

  XStep Locate this document in the navigation structure

Definition

A structure that you can use to describe the precise execution of production processes. Using XSteps you can control the data exchange with the process control level or generate interactive work instructions/PI sheets for process operators and production workers. An XStep can be assigned to a master recipe, process order, standard routing, or production order.

Structure

This graphic is explained in the accompanying text.

An XStep tree consists of one or more XSteps. It can also contain XStep process instructions and references to standard XSteps (SXS reference). An XStep in an XStep tree can also be made up of further XSteps, SXS references and XStep process instructions.

You can create the following components within an XStep tree.

  • XSteps

    An XStep can contain further subordinated XSteps. Properties of the higher-level XSteps, such as scope of generation, control instruction/control recipe destinations and application context are inherited by the subordinate XSteps, as long as they have not been explicitly assigned any of these values separately. If, for example, you have defined the application context Order in the superordinate XStep, this application context is valid for all subordinate XSteps until the next XStep for which a different context is defined.

  • SXS References

    An XStep or a standard XStep can be referenced to versions of a standard XStep, which are maintained in the SXS repository. When creating an SXS reference, the system firstly creates a loose connection to the referenced standard XStep. Once the references are exploded, the system creates a copy of the valid version of the standard XStep in your XStep tree for the key date.

    See also: Standard XSteps

  • XStep Process Instructions

    All functions that were available with the conventional process instructions are still available. When maintaining objects in the XStep editor, you no longer have to be familiar with the syntax of the process instruction characteristics. Instead, you can easily create output and input fields, as well as control functions such as function calls and process messages using the context menu.

    See also: XStep Process Instructions

XStep Properties

You can define specific properties for each XStep:

  • General Information

    In this dialog window, you find information about the status of the control instructions or the control recipe and administrative data about the last person to make a change and so on.

  • Parameters and Parameter Valuations

    In this dialog box you create the XStep parameters and their valuations for the XStep.

    See also: XStep Parameter

  • Scope of Generation

    In this dialog box you assign a scope of generation to the XStep.

    See also: XStep Generation

  • Receiver

    In this dialog box, you assign either a destination type (external system or PI sheet) or a concrete control instruction/recipe destination to the XStep.

    The destination is valid for the entire XStep tree until a new destination is found. The inheritance hierarchy then starts again from this position in the tree.

  • Application Context

    In this dialog box you specify whether the XStep should be valid for a particular phase, a certain operation, or for the entire order. The system requires the XStep context during the generation and the automatic valuation.

    As is the case with the destination, the context is valid for the entire XStep tree until a new context is found. The inheritance hierarchy then starts again from this position in the tree.

    Caution Caution

    Note that some scopes of generation also set the context. If, for example, you have defined the scope of generation For All Phases for an XStep, then the system creates a copy of this XStep for every phase. Every XStep copied is automatically assigned the context of the particular phase. For example, the XStep for phase 10 would be assigned the context for phase 10.

    End of the caution.