How to Configure the BLK_Jump Attribute and OS Additional Text for Faceplate Navigation in PCS 7

In SIMATIC PCS 7 SCL and CFC engineering, the block parameter attribute 'BLK_Jump' enables seamless faceplate-to-faceplate navigation buttons in WinCC. When 'BLK_Jump' is declared on an input parameter of data type ANY or Struct, the AS-OS compiler automatically generates two internal WinCC tags upon compilation: '.#Jump' (which stores the tag name of the target interconnected block) and '.#OS_Text' (which stores the descriptive text used to label the navigation button in the faceplate). This built-in system mechanism eliminates manual WinCC VBScripting for faceplate jumps and ensures 100% automated synchronization across multi-project compilations.

Architecture of BLK_Jump and Faceplate Interconnection in PCS 7

In complex chemical reactors and distillation columns, technological blocks work in tightly coordinated groups (e.g., a dosing valve VlvL, a flow transmitter MonAnL, and a PID controller PIDConL):
* The Operational Requirement: When an operator opens the valve faceplate in WinCC, they need one-click access to the upstream flow meter and downstream controller without searching through plant hierarchy screens.
* The PCS 7 Solution: The system provides the BLK_Jump system attribute.
* How It Operates:
* In the AS block interface, an input pin is designated with BLK_Jump := 'true'.
* In CFC, that pin is interconnected to any output pin of the companion block.
* During OS compilation, the compiler inspects the interconnection and automatically configures the WinCC faceplate button with the partner's tag name and a human-readable button label.

SCL Block Declaration: Applying the BLK_Jump Attribute

To integrate faceplate jump capabilities into custom SCL blocks:

FUNCTION_BLOCK FB_CustomUnitControl
TITLE = 'Unit Controller with Companion Faceplate Jumps'
VERSION : '1.0'
AUTHOR : 'Cielo'
FAMILY : 'USER_APL'

VAR_INPUT
    // Standard jump parameter to companion valve block
    JumpValve { 
        S7_m_c := 'true'; 
        BLK_Jump := 'true'; 
        S7_string_0 := 'Inlet Valve' 
    } : ANY;

    // Standard jump parameter to companion PID block
    JumpPID { 
        S7_m_c := 'true'; 
        BLK_Jump := 'true'; 
        S7_string_0 := 'Temp Controller' 
    } : ANY;
END_VAR

Declaration Rules:
The parameter must have the operator control attribute: S7_m_c := 'true'.
The parameter must have: BLK_Jump := 'true'.
The parameter type should be ANY (or a matching structured signal type) to allow CFC interconnections to any external block output.

Automated OS Compilation Tag Generation (#Jump and #OS_Text)

When the engineer executes Compile OS in SIMATIC Manager, the AS-OS engineering compiler creates two distinct tag elements in WinCC Tag Management:

The #Jump Tag:
* Tag Name: <Chart>\<BlockName>.<ParameterName>#Jump (Data Type: Text tag 8-bit).
* Value: Automatically populated with the fully qualified WinCC tag name of the interconnected block (e.g., Plant1/Area2/FCV101).
* When an operator clicks the button in the faceplate, the APL faceplate open script reads #Jump and opens the target faceplate instantly.
The #OS_Text Tag:
* Tag Name: <Chart>\<BlockName>.<ParameterName>#OS_Text (Data Type: Text tag 8-bit).
* Value: Populated with the text configured under 'OS additional text' in the CFC block properties. This text appears as the visible label on the faceplate button (e.g., 'Inlet Valve').

Configuring OS Additional Text in CFC Object Properties

To define or override the button label in CFC:

Open the CFC chart containing the block instance.
Double-click the block (or right-click and select Object Properties).
Select the Inputs/Outputs tab.
Locate the jump parameter (e.g., JumpValve).
In the OS additional text column, type the desired button label (e.g., Feed Valve FCV-101).
Click OK.
Execute a delta compile of the OS (Compile OS > Changes Only). The #OS_Text tag in WinCC updates immediately with the new label.

Comparison of Faceplate Navigation and Jump Mechanisms

The table below compares faceplate navigation techniques across SIMATIC PCS 7.

Navigation TechniqueConfiguration LocationAutomated Tag GenerationMaintenance OverheadMigration DurabilityBLK_Jump AttributeSCL / CFC InterfaceYes (#Jump, #OS_Text)Zero (Compiler managed)100% Migration-ProofAPL SelFp1 / SelFp2 PinsStandard APL Block PinsYes (Standard APL tags)Zero (Native pins)100% Migration-ProofCustom WinCC C/VBScriptGraphics Designer PDLNo (Hardcoded script)High (Manual tag edits)Poor (Breaks on tag rename)Picture Window Open ButtonGraphics Designer PDLNo (Static screen link)ModerateModerate

Verification

To confirm that the BLK_Jump navigation functions properly:
1. In CFC, interconnect FB_CustomUnitControl.JumpValve to VlvL.FbkOpenOut.
2. In block properties, set OS additional text to Main Steam Valve.
3. Perform an OS delta compilation (Compile OS).
4. In WinCC Tag Management, verify that tags JumpValve#Jump (value: Plant/Area/VlvL) and JumpValve#OS_Text (value: Main Steam Valve) exist.
5. In WinCC Runtime, open the custom block faceplate: confirm that the navigation button displays the label Main Steam Valve.
6. Click the button: verify that the VlvL steam valve faceplate opens immediately adjacent to the caller window.

Limitations and Operational Precautions

If a jump parameter is left completely unconnected in CFC, the #Jump tag will be empty, and the corresponding button in the WinCC faceplate will be disabled or hidden.
Avoid declaring dozens of BLK_Jump parameters on a single block; faceplate toolbars have finite horizontal button space (typically 2 to 4 jump buttons per view).
Never hardcode WinCC tag names in SCL code; always utilize dynamic interconnections in CFC to maintain tag integrity across plant hierarchy changes.
Always validate final software licensing and system documentation against the applicable Siemens catalog and authorized distributor quotation.

Engineer FAQ

Why did the navigation button in my faceplate not appear?

The button will not render if the parameter has no active CFC interconnection, if the #Jump tag is blank, or if the parameter is missing the S7_m_c := 'true' attribute.

Can BLK_Jump navigate to a WinCC picture instead of a block faceplate?

No. BLK_Jump is designed specifically for block-to-block faceplate navigation. To navigate to a picture, use standard WinCC picture change scripts or the APL PictureName property on block icons.

What data type should be used for the BLK_Jump input pin?

Use the ANY pointer data type or an APL structured signal type (Struct). ANY is the most versatile because it accepts connections from any data type (BOOL, REAL, Struct) in CFC.