WinCC Unified - Calendar - Manual

Calendar - Defining schedules for production
Migrating V16 project 1
Basics 2
Configuring the time
3
SIMATIC HMI model.
Configuring a calendar 4
WinCC Unified
Calendar - Defining schedules for Configuring a calendar
5
production control
Compiling configuration
System Manual
data and loading it into 6
Runtime
Validation of the
configuration of plant 7
objects
Defining schedules during

runtime 8
Local reporting for calendar 9
Online documentation
06/2021
Legal information
Warning notice system
This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent
damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert
symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are
graded according to the degree of danger.
DANGER
indicates that death or severe personal injury will result if proper precautions are not taken.
WARNING
indicates that death or severe personal injury may result if proper precautions are not taken.
CAUTION
indicates that minor personal injury can result if proper precautions are not taken.
NOTICE
indicates that property damage can result if proper precautions are not taken.
If more than one degree of danger is present, the warning notice representing the highest degree of danger will
be used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to
property damage.
Qualified Personnel
The product/system described in this documentation may be operated only by personnel qualified for the specific
task in accordance with the relevant documentation, in particular its warning notices and safety instructions.
Qualified personnel are those who, based on their training and experience, are capable of identifying risks and
avoiding potential hazards when working with these products/systems.
Proper use of Siemens products
Note the following:
WARNING
Siemens products may only be used for the applications described in the catalog and in the relevant technical
documentation. If products and components from other manufacturers are used, these must be recommended
or approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and
maintenance are required to ensure that the products operate safely and without any problems. The permissible
ambient conditions must be complied with. The information in the relevant documentation must be observed.
Trademarks
All names identified by ® are registered trademarks of Siemens AG. The remaining trademarks in this publication
may be trademarks whose use by third parties for their own purposes could violate the rights of the owner.
Disclaimer of Liability
We have reviewed the contents of this publication to ensure consistency with the hardware and software
described. Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the
information in this publication is reviewed regularly and any necessary corrections are included in subsequent
editions.
Siemens AG Copyright © Siemens AG 2021.

Digital Industries Ⓟ 06/2021 Subject to change All rights reserved
Postfach 48 48
90026 NÜRNBERG
GERMANY
Table of contents
1 Migrating V16 project ............................................................................................................................ 5

2 Basics ..................................................................................................................................................... 7
2.1 Introduction ........................................................................................................................ 7
2.2 Requirements ...................................................................................................................... 9
2.3 Basics on scheduling in the WinCC Unified Calendar ........................................................... 10
2.4 Changes in multi-user projects ........................................................................................... 11
3 Configuring the time model. ............................................................................................................... 13
3.1 Creating time categories .................................................................................................... 13
3.2 Deleting time categories .................................................................................................... 14
3.3 Editing properties of a time category .................................................................................. 15
3.4 Editing the tree structure of the time model ....................................................................... 16
3.5 Exporting time categories .................................................................................................. 17
3.6 Importing time categories .................................................................................................. 18
4 Configuring a calendar ........................................................................................................................ 19
4.1 Creating a calendar ............................................................................................................ 19
4.2 Opening a calendar............................................................................................................ 20
4.3 Configuring the basic settings of the calendar .................................................................... 20
4.4 Defining tag access of the calendar .................................................................................... 22
4.5 Editing calendars ............................................................................................................... 23
4.6 Deleting a calendar ............................................................................................................ 23
5 Configuring a calendar control ............................................................................................................ 25
5.1 Inserting a calendar control into a screen ........................................................................... 25
5.2 Configuring a calendar control ........................................................................................... 25
5.3 Set up access control for calendar control........................................................................... 27
6 Compiling configuration data and loading it into Runtime ................................................................ 29
7 Validation of the configuration of plant objects ................................................................................. 31
8 Defining schedules during runtime ..................................................................................................... 33
8.1 Basics ................................................................................................................................ 33
8.1.1 Introduction ...................................................................................................................... 33
8.1.2 Requirements .................................................................................................................... 35
8.1.3 Basics on scheduling in the WinCC Unified Calendar ........................................................... 36
8.1.4 Inheritance of calendars..................................................................................................... 39
8.1.5 Context logging ................................................................................................................. 40

System Manual, 06/2021 3
Table of contents
8.1.6 Overall workflow ............................................................................................................... 41

8.2 User interface .................................................................................................................... 45
8.2.1 Overview of the user interface of the calender control ........................................................ 45
8.2.2 "Planning" and "Templates" tabs ......................................................................................... 47
8.3 Creating templates ............................................................................................................ 53
8.3.1 Creating and deleting shift templates ................................................................................. 53
8.3.2 Creating and deleting day templates .................................................................................. 55
8.3.3 Creating and deleting action templates .............................................................................. 57
8.3.4 Saving or discarding changes ............................................................................................. 58
8.3.5 Working with action elements in action templates.............................................................. 60
8.3.5.1 Adding or deleting action elements .................................................................................... 60
8.3.5.2 Editing action elements ..................................................................................................... 61
8.3.6 Working with actions ......................................................................................................... 62
8.3.6.1 Adding or deleting actions ................................................................................................. 62
8.3.6.2 Editing actions ................................................................................................................... 64
8.3.6.3 Edit action elements in shifts ............................................................................................. 66
8.3.7 Working with time periods ................................................................................................. 67
8.3.7.1 Adding and deleting time periods ...................................................................................... 67
8.3.7.2 Moving time periods .......................................................................................................... 69
8.3.7.3 Shortening or extending time periods ................................................................................ 71
8.3.8 Working with shifts ............................................................................................................ 72
8.3.8.1 Adding and deleting shifts ................................................................................................. 72
8.3.8.2 Moving shifts ..................................................................................................................... 75
8.3.8.3 Shortening or extending shifts ........................................................................................... 76
8.3.8.4 Shift properties .................................................................................................................. 78
8.3.9 Renaming a template ......................................................................................................... 78
8.3.10 Changing templates........................................................................................................... 79
8.4 Creating and adapting schedules ....................................................................................... 81
8.4.1 Adding and deleting days................................................................................................... 82
8.4.2 Editing days ....................................................................................................................... 84
8.4.3 Restoring days ................................................................................................................... 85
8.4.4 Flagging a day ................................................................................................................... 86
8.4.5 Creating a recurrence for a shift ......................................................................................... 86
8.4.6 Creating a recurrence for a day .......................................................................................... 87
8.4.7 Saving or discarding changes ............................................................................................. 89
8.4.8 Editing inherited shifts ....................................................................................................... 90
8.4.9 Clear planning data............................................................................................................ 91
8.5 Export and import .............................................................................................................. 92
8.5.1 Export data ........................................................................................................................ 92
8.5.2 Importing data................................................................................................................... 93
8.5.3 Structure of the CSV file ..................................................................................................... 94
9 Local reporting for calendar ................................................................................................................ 97
9.1 Basics ................................................................................................................................ 97
9.1.1 Introduction ...................................................................................................................... 97
9.1.2 Requirements .................................................................................................................... 98
9.2 Procedure .......................................................................................................................... 98
9.3 Defining a report template with hierarchical segment ........................................................ 99
9.4 Creating a report job and downloading a report ............................................................... 101

4 System Manual, 06/2021
Migrating V16 project 1
Introduction
When you open your V16 project with Calendar configuration in TIA Portal V17, you have the
option of upgrading the project to V17.
The configured Runtime version of the HMI device must be separately changed to V17. The
calendar control used in the screen must then be updated.
Upgrade project
1. Open your V16 project in TIA Portal V17.
The "Open project" dialog opens:
Note
When a product is used in the V16 project but is not installed, an upgrade is not possible.
Install the missing product and then perform the upgrade.
2. Click "Upgrade".
The upgrade will take a few minutes.
The project is opened.

Migrating V16 project
Result
• The contents of the V16 project are saved in a new project with the V17 project version.
• The original project is not overwritten and can still be edited with TIA Portal V16.
Changing the configured Runtime version of the HMI device

1. Right-click on the HMI device in the project tree.
2. Select "Change device / version".
The "Change device - SIMATIC WinCC Unified PC" dialog opens.
3. Navigate to "SIMATIC WinCC Unified PC" in the right tree.
The existing HMI device with version V17 is automatically displayed under "New device".
4. Confirm your change with "OK".
Updating calendar control

1. Open a screen in your project.
2. Click the "Update" button in the task card "Toolbox > My controls".

Basics 2
2.1 Introduction
Introduction
SIMATIC WinCC Unified Calendar is an option package of the Plant Intelligence options of TIA
Portal. With Calendar, you create schedules for the production lines and stations of your
plant.
You make preparations for the scheduling during the engineering in TIA Portal. You perform
the scheduling itself in runtime in the calendar control.
Functional scope
TIA Portal:
• You define a time model whose time categories are available in the option packages
Calendar and Performance Insight.
• You configure the calendar and the calendar control with which you define templates and
create schedules in runtime.
Runtime:
• You define and manage templates for typical shifts, days and actions that can be used as
often as desired in the schedules. You create the templates from different time categories
defined centrally in TIA Portal, e.g. break, work and maintenance.
• From the templates, you create production schedules for the future which implement the
requirements for production and work planning.
• You can adapt the schedules to changed requirements at any time during production.
Examples:
– Move a planned maintenance activity to achieve a new setpoint number.
– Respond to events in the production sequence, such as unplanned maintenance work
or a staff meeting called at short notice.
• You define actions that access member tags of the plant model during a shift (internal
tags or PLC tags). You define the starting point of the action relative to the starting point
of your shift.
In this way, you can control the production process already during scheduling. For
example, you can switch on the lights in the production hall via Calendar half an hour
before the first day shift begins.

Basics
2.1 Introduction
Benefits
• You plan based on the created plant view and the time categories centrally managed in
TIA Portal and thus guarantee data consistency.
• You speed up your scheduling by using centrally managed templates:
– With a few clicks, you define templates that you can adapt flexibly to the specific
production requirements.
– You can forward changes to the templates automatically to the schedules.
• You react during production to changed boundary conditions and adapt your schedules on
location.
• You collect basic data for additional evaluations and actions related to the shift, such as
quantity statistics and production overviews.

Basics
2.2 Requirements
2.2 Requirements
Introduction
You use SIMATIC WinCC Unified Calendar to configure schedules for the production lines. You
require a license to use this option. You can find information on licenses in the Plant
Intelligence Options Installation Guide, section "Licensing PI Options".
Software requirements
To use Calendar both in the engineering system and in runtime, you need the following
products:
• TIA Portal V17 or higher with STEP 7 Professional
• WinCC Unified Runtime/PC V17
• WinCC Unified Calendar option package
Requirements in the TIA Portal

Your TIA Portal project must meet the following requirements so that you can prepare the
scheduling for WinCC Unified Runtime in the engineering.
• The project is open.
• Devices and an HMI device are created in the "Devices" tab.
• The HMI device has a screen.
• A plant view is created in the "Plant objects" tab.
• The plant objects of the plant view have member tags (internal tags and tags for
communication with a controller).
• An HMI device is assigned to the plant view.
• A time model with at least one user-defined time category has been created.
See also
Configuring the time model. (Page 13)

Basics
2.3 Basics on scheduling in the WinCC Unified Calendar
2.3 Basics on scheduling in the WinCC Unified Calendar
Plant-based planning
The plant is the basis of the scheduling. In the engineering system, the plant model is
mapped in a tree in the plant view. The tree root represents the plant view, while the nodes
represent the plant objects.
Plant objects have internal tags and tags for communication with a controller. Each plant
object has access to its own tags as well as to the tags of its lower-level objects.
Plant objects also have different functional facets. These facets include the calendar object.
Plant Intelligence options for WinCC Unified work in a common plant view. It is defined with
Common Plant Model.
Note
Data losses in Runtime due to changes in engineering
• Deleting or moving a plant object with the calendar
Or
Deleting a calendar from the plant view:
The data that is created in runtime for the calendar is deleted. If the calendar was passed
on to lower-level plant objects and overwritten there, this data is also deleted.
• Inserting a new calendar at a plant object:
If the plant object has inherited and overwritten a calendar in runtime, this data is deleted.
If the calendar was passed on to lower-level plant objects and overwritten there, this data
is also deleted.
• Changes to tag access of the calendar
When a member tag that is used by an action element in runtime is disabled, its status is
set to "Undefined" in the calendar after the next compile and load. See also section
Defining tag access of the calendar (Page 22).
Calendar and inheritance of calendars

A calendar saves all data that is relevant for the schedules of a plant object and its lower-level
objects. You define during engineering which objects from the plant view have their own
calendar.
• When a plant object has a calendar, its lower-level objects inherit this calendar.
In runtime, the calendar is valid for the plant object and its lower-level objects. The lower-
level objects can amend and overwrite the schedules defined at the higher-level plant
object.
• Lower-level nodes can also have their own calendar. This means that they lose access to
the calendar of their higher-level node.
They pass on their own calendar to their own lower-level objects.
For each calendar object you define which calendar settings apply to this calendar, for
example, the pre-selected shift length and the beginning of the fiscal year.

Basics
2.4 Changes in multi-user projects
Calendar control
The calendar control is the HMI control with which schedules are created in runtime.
The calendar control must be linked to a plant object. The link allows the calendar control to
show the calendar of the linked plant object and to access the following tags in runtime:
• The member tags of the plant object
• The member tags of all plant objects subordinate to the plant object
You can limit the tag access in the engineering system via the calendar settings.
The link between the calendar control and plant object can be set as follows:
• Dynamic in runtime by selecting a plant object in the "Plant overview" control
Requirement: The plant overview is configured as companion control in the properties of
the calendar control.
• By a static entry in the properties of the calendar control
• By a script
See also section Defining tag access of the calendar (Page 22).
Common Time Model and time categories

The Plant Intelligence options of WinCC Unified Performance Insight and WinCC Unified
Calendar share a time model. The time model defines which time categories are available, the
options for which they are relevant, how they are visualized and whether or not they belong
to the working time.
In the calendar, time periods are combined into shifts from the time categories defined in the
time model during runtime.
With installed Performance Insight option, you also define the machine states that you are
using in KPIs in Performance Insight in the time model.
See also
Configuring a calendar control (Page 25)

Changes to the time model and calendars in multi-user projects always have to be executed
in the server project view.
Changes made in the local session are overwritten as soon as the local session is being
updated.

Basics

Configuring the time model. 3
3.1 Creating time categories
Time categories are structured in a tree. A root time category under which you create user-
defined time categories serves as the tree root.
You can create any number of time categories. You can change the tree structure
retrospectively.
Creating a root time category
Requirement
• No root time category is created in the time model editor.
Procedure
1. Select the "Plant objects" tab.
2. In the "Common data" folder, double-click the node "Time model".
3. In the time model editor, double click the "Add new" cell.
The root time category is created.
Creating a user-defined category
Requirement
• The root time category is created in the time model editor.
Procedure
2. You have the following options:
– Select the root time category.
– In the time model editor, expand the time model and select a time category.
The "Expand all" button extends the tree so that you can see all categories, "Collapse
all" reduces it.
3. Click the "Add time category" button or select "Add time category" from the shortcut menu.
4. Enter the name of the category.
5. Configure additional properties of the new time category, either directly in the editor or in
the Inspector window.

Configuring the time model.
3.2 Deleting time categories
Copying time category

1. Select "Copy" in the shortcut menu of a time category.
2. Select the desired owner.
3. In the shortcut menu, select "Paste".
See also
Editing properties of a time category (Page 15)
Editing the tree structure of the time model (Page 16)
Importing time categories (Page 18)
3.2 Deleting time categories
Requirement
• The time model editor is open.
• At least one time category has been created.
Procedure
1. Select the required time category.
2. Select "Delete" in the shortcut menu.
Result
After the next save, compile and load, the time category is no longer available to users in
Runtime for planning.
Note
Time categories used in Runtime
If the deleted time category is used in a calendar in Runtime, time intervals with this time
category are marked with an "*". Users using this category must replace the time intervals
that are in the future.

3.3 Editing properties of a time category
3.3 Editing properties of a time category
Requirement
• A time model is created on the "Plant objects" tab.
• The time model has user-defined time categories.
Procedure
2. In the time model editor, expand the time model and select a time category.
The "Expand all" button extends the tree so that you can see all categories, "Collapse all"
reduces it.
3. Click on a time category.
4. Configure its properties, either directly in the editor or in the Inspector window.
Properties of the time category
Property Description
Properties
Name Assign a unique name.
Language-neutral
Unsupported special characters:
: :: . #\ / % [ ] $ "
Display name Localizable
Description Localizable
Color Color for visualizing the category in the Plant Intelligence options.
Relevance
Calendar In the time model, select the check box of a category so that it can be
used in the calendar control.
When you activate a category, the hierarchically higher-level and low-
er-level categories are deactivated.
Default setting of new categories: Deactivated

3.4 Editing the tree structure of the time model
3.4 Editing the tree structure of the time model
Note
Data losses in runtime through changes to the time model
If the time model is changed in TIA Portal after templates and schedules have been created in
runtime, this can lead to data losses.
You can edit the tree structure of the time model as follows:
• Creating time categories
• Deleting time categories
• Moving time categories
You can move a lower-level node or a higher-level node including all its children.
• Sorting time categories
Requirement
• The time model has user-defined time categories.
Deleting time categories

Select one of the following procedures:
• Select "Delete" in the shortcut menu of the time category.
• Select the time category and press <Del>.
• Select the time category and click "Delete" in the toolbar.
The time category and its children are deleted.
Moving time categories

Select one of the following procedures:
• Select a time category and drag it to the new owner, keeping the left mouse button
pressed.
• Select "Cut" in the shortcut menu of the time category and "Paste" in the shortcut menu of
the new owner.
The time category and its children are moved.

3.5 Exporting time categories
Rearranging time categories

You rearrange the order of time categories on the same level:
1. Select a time category and drag it to the line header of a second category on the same level,
keeping the left mouse button pressed:
The time category and its children are sorted above the second category.
3.5 Exporting time categories

You have the option to export the time categories to Excel.
Requirements
• The time model has time categories.
Procedure
2. Click the "Export" button.
3. Define the export path and the file name.
4. Click "Export".
Result
An Excel file is created. The time categories are exported into the "TimeCategories"
worksheet.
Note
Do not rename the sheet if you are planning on a reimport.

3.6 Importing time categories
3.6 Importing time categories

You have the option to import time categories from Excel.
Requirements
• The Excel file has a "TimeCategories" worksheet. The worksheet has the required format.
Importing time categories

2. Click the "Import" button.
3. Select the import path and the Excel file.
4. Define what happens during the import if time categories in TIA Portal and in the import file
have the same name. Select one of the following options:
– The time category to be imported is renamed.
– The time category to be imported overwrites the time category from TIA Portal.
5. Click "Import".
Result
If a time model already exists, the time categories are imported from the Excel file into the
time model.
If no time model exists yet, a time model and the base time category are created. The time
categories are imported from the Excel file into the time model.

Configuring a calendar 4
4.1 Creating a calendar
Requirements
• A plant object has been created in the plant view.
• A plant object has no calendar.
Creating a new calendar

1. Double-click the plant object or select "Open" in its shortcut menu.
The editor for plant objects opens.
2. Select the "Calendar" tab.
3. Click the "Add calendar" button.
Copying an existing calendar

1. Copy a calendar in the detail view.
2. In the "Plant objects" tab, click a plant object without a calendar.
3. In the shortcut menu, select "Paste".
Alternative procedures:
• Keyboard commands <Ctrl+C> and <Ctrl+V>
• Using the shortcut menu of the calendar and the new owner or the menu bar
• Drag-and-drop in conjunction with keyboard command <Ctrl>
Result
A Calendar object is created and is loaded for editing into the "Calendar" tab in the work area.
If you select the plant object in the "Plant objects" tab, you see the calendar object in the
detail view.
With a complete download, the changes become immediately visible in Runtime. In the case
of a delta download, the changes become visible after a screen change or a browser refresh.
Unsaved changes to the calendar are lost on screen change and browser refresh.
See also
Basics on scheduling in the WinCC Unified Calendar (Page 10)

Configuring a calendar
4.2 Opening a calendar
4.2 Opening a calendar
Requirements
A plant object has a calendar.
Procedure
1. Select the plant object in the "Plant objects" tab.
2. Select "Open" in the detail view in the shortcut menu of the calendar
or double-click the calendar in the detail view.
Result
The calendar editor opens.
See also
Configuring the basic settings of the calendar (Page 20)
4.3 Configuring the basic settings of the calendar
Requirement
A plant object in the "Plant objects" tab has a calendar.
Procedure
1. Open the calendar.
3. Configure the general calendar properties under "Settings".
4. Under "Permitted interface tags", configure which of the member tags available in principle
can be accessed via the calendar.
5. Save your project.

4.3 Configuring the basic settings of the calendar
Overview of the general calendar settings
Settings
Under "Settings", you define the general calendar settings:
Name Description Default setting

"Time zone" The time zone used by the calendar. The time zone set in the local system.
The property is write-protected.
"Standard shift length." Determines the length of created new 8 hours
shifts.
Minimum value: 2 hours
Maximum value: 24 hours
"First day of week" Determines the day on which the work- Monday
ing week starts.
"First week of year" Determines the week in which the year First 4-day week
starts.
Possible values:
• "1 January"
• "First 4-day week"
• "First full week"
"Beginning of day offset" Determines the number of hours after 0
midnight until the working day starts.
"Fiscal year day" Determines the first day of the fiscal 1
year
"Fiscal year month" Determines the first month of the fiscal January
year
"Weekdays" Determines which days are part of the Monday to Friday
working week.
Permitted tags
Under "Permitted interface tags", use the "Permitted" check box to configure the tags to
which the calendar has access. See section Defining tag access of the calendar (Page 22).
Result
With a complete download, the changes become visible immediately in runtime. In the case
Unsaved changes to the calendar are lost on browser refresh.
Note
Deactivate weekdays of a calendar used in runtime
If you deactivate weekdays for a calendar used in runtime, shifts scheduled for those
weekdays are not displayed in the working week view. The days are still executed in runtime.
The planned shifts are not deleted.

4.4 Defining tag access of the calendar
See also
Opening a calendar (Page 20)
4.4 Defining tag access of the calendar
Requirement
A plant object has a calendar.
Procedure
Proceed as follows to determine which tags the calendar can access in runtime:
1. Open the calendar.
Under "Permitted interface tags", you can see all member tags that were defined for the
plant object and its lower-level objects in the "Interface" tab. The member tags have the
"permissible" check box.
3. Select or clear the check boxes as required.
Note
Deactivating tags used in runtime
When you disable a tag that is used by an action element in runtime, its status is set to
"Undefined" in the calendar after the next compile and load.
4. Save your project.
Result
Your settings for tag access are available in runtime as soon as you have compiled them and
loaded them into the device. All tags with selected check box can be assigned to action
elements in runtime.
With a complete download, the changes become visible immediately in runtime. In the case
See also
Opening a calendar (Page 20)

4.5 Editing calendars
4.5 Editing calendars
Editing a calendar used in Runtime

1. Edit the desired calendar settings.
2. Compile the project and load it into the device.
With a complete download, the changes become immediately visible in Runtime. In the case
See also
4.6 Deleting a calendar
Requirements
A plant object in the "Plant objects" tab has a calendar.
Procedure
1. Double-click the plant object or select "Open" in the shortcut menu.
The editor for plant objects opens.
3. Click "Remove calendar".
The calendar is deleted.
Deleting a calendar used in Runtime

1. Delete the calendar.
2. Compile the project and load it into the device.
With a complete download, the Calendar is no longer directly available in Runtime. In the
case of a delta download, the calendar is no longer available after a screen change or a
browser refresh.
See also

4.6 Deleting a calendar

Configuring a calendar control 5
5.1 Inserting a calendar control into a screen
Procedure
1. Select the HMI device on the "Devices" tab.
2. Open the "Screens" folder.
3. Open the screen.
4. In the "My Controls" pane, select the calendar control and place it on the screen.
5.2 Configuring a calendar control
Requirement
• A plant object from the plant hierarchy has a calendar.
• The screen of an HMI device has a calendar control.
• Optional: A plant overview is inserted in the screen.
Procedure
1. Open the screen.
2. Select the calendar control in the screen.
3. In the Inspector window, click on the "Properties" tab.
4. Open the "Properties" node.

Configuring a calendar control
5.2 Configuring a calendar control
5. In "Active view", select the view with which the control starts in runtime.
6. Set a link to the plant object whose calendar the control should display in runtime.
Select one of the following options:
Dynamically during 1. Leave the "Plant object" field empty.

runtime via the "Plant
overview" control 2. In the "Plant overview" control, configure the calendar control as a
companion control.
If a plant overview has been configured for the screen, the calendar
control always displays the calendar of the plant object selected in the
plant overview.
Link manually 1. Click the "Plant object" field and the "..." button.
2. In the left-hand area, select the owner of the plant object whose
calendar the control should display.
3. In the right-hand area, select the tag of the plant object.
The control always shows the calendar of this plant object.
Linking by script 1. Select "Script" as dynamization for the "Plant object" field.
2. Enter a script that sets the path to a plant object with calendar in
runtime:
Screen.Items('<CalendarControl-
Name>').Properties.PlantObject = "<The path to the
plant object>";
Example: Screen.Items('Calendar con-

trol_1').Properties.PlantObject =
"HMI_RT_1.hierarchy::Plant1/Subplant_A";
3. Select a tag or a timer as trigger.
The script determines dynamically the plant object to which the control
is linked, and which calendar it displays.
Note
Alternative for a link by script
Instead of adding the script to the "Plant object" property, you can also configure a button
and add the script to an event of the button.
Note
Transferring changes to Runtime
The changes to the calendar are only available in runtime after you have compiled them and
loaded them into the device.

5.3 Set up access control for calendar control
Introduction
You can set up access control for the calendar control. With this you determine which rights
the runtime user gets for the control. To do this, you can assign predefined or user-specific
runtime rights to the properties "Action edit", "Planning edit" or "Full access".
Action edit With this right, the Runtime user can edit actions in the "Planning" tab. Edit-
ing shifts and templates is not possible.
Planning edit With this right, the Runtime user can edit actions and shifts in the "Planning"
tab. Creating new plans and editing templates is not possible.
Full access With this right, the runtime user can fully operate the Control (change and
create actions, shifts, templates) and delete runtime data.
If no function right is assigned to a property, all runtime users have the right.
Function rights of the runtime user

If more than one function right is configured for a runtime user, the right with the highest
privilege is taken into account.
Action edit Planning Full access Function rights of the runtime user
edit
X X X User has only read rights. Operation is not possible.
✓ X X The user has the "Action edit" right.
X/✓ ✓ X The user has the "Planning edit" right.
X/✓ X/✓ ✓ The user has the "Full access" right.
Legend:
X = The runtime user does not have the function right that is set in the property.
✓ = The runtime user has the function right that is set in the property.
Or the property is empty.

Requirement
• In the security settings, you have configured "Users and roles" in accordance with your
needs.
You can find more information in the section "Configuring users and roles" in the WinCC
Unified help.
• The "Allow operator control" option is activated in the control properties under "Security".
• The "Authorization" option is empty in the control properties under "Security".
• In the control properties under "Properties > Miscellaneous > Interface", the "Require
explicit unlock" option is disabled under the property "Action edit", "Planning edit" and
"Full access".
This control property is for multipoint touch displays and is not supported in V17.
Procedure
1. Select the desired control in the screen.
2. Expand the property "Action edit", "Planning edit" or "Full access" under "Properties >
Miscellaneous > Interface".
3. Expand the drop-down list in the "Static value" column under "Authorization".
The function rights are displayed.
4. Select a function right.
5. If necessary, repeat steps 2-4 to configure the additional properties.

Compiling configuration data and loading it into
Runtime 6
Introduction
To receive configuration data in runtime, you have the option of performing a delta compile
and delta download.
You can find more information in the WinCC Unified help under "Visualize processes >
Compile and load".
Configuration changes to calendar data

Not all configuration changes can be compiled and downloaded in delta mode. The following
table shows you the changes to the calendar data for which a delta compile and delta
download are possible:
Element Delta download capability No delta download capability

Time model Time category: -
• Change the properties of a time category
• Add or delete new child time category
for an existing time category
• Import or export of time categories
Time model in PFI controls - General, if time categories are used in the
PFI controls:
• Create, rename or delete
• Copy and paste
• Move within the plant view
Calendar object Calendar object: -
• Change settings
• Create or move under another plant
object
• Delete
Plant object - General:
• Create, rename or delete
• Copy and paste
• Move within the plant view
Plant object types - In general, if an instance of the plant object
type exists:
• Rename or delete
Calendar control All custom control screen properties are
capable of a delta download.

Compiling configuration data and loading it into Runtime
Effects on the active RT project

Active Runtime is not terminated by delta download. The changes are immediately applied in
the active RT project and are visible in Runtime after a screen change or browser refresh.

Validation of the configuration of plant objects 7
Introduction
If validation errors in the plant view, missing or faulty properties of plant objects or plant
object types have arisen, these errors are displayed during compilation. With the "Go to"
function, you have the possibility to jump directly to the error location and eliminate the error
immediately.
Solve causes of errors during validation

1. Navigate in the Inspector window to "Info > Compile".
2. Set the filter so that error messages are displayed.
If a green arrow is displayed in the "Go to" column for a message, you can go directly
to the appropriate tab for correcting the cause of the alarm.
3. Select the green arrow .
The tab in which corrections are expected is displayed. The corresponding property is
selected.

Validation of the configuration of plant objects

Defining schedules during runtime 8
8.1 Basics
8.1.1 Introduction
Introduction
SIMATIC WinCC Unified Calendar is an option package of the Plant Intelligence options of TIA
Portal.
With Calendar, you create schedules for the production lines and stations of your plant.
Functional scope
• You define and manage templates for typical shifts, days and actions that can be used as
often as desired in the schedules. You create the templates from different time categories
defined centrally in TIA Portal, e.g. break, work and maintenance.
• From the templates, you create production schedules for the future which implement the
requirements for production and work planning.
• You can adapt the schedules to changed requirements at any time during production.
Examples:
– Move a planned maintenance activity to achieve a new setpoint number.
– Respond to events in the production sequence, such as unplanned maintenance work
or a staff meeting called at short notice.
• You define actions that access member tags of the plant model during a shift (internal
tags or PLC tags). You define the starting point of the action relative to the starting point
of your shift.
In this way, you can control the production process already during scheduling. For
example, you can switch on the lights in the production hall via Calendar half an hour
before the first day shift begins.

Defining schedules during runtime
8.1 Basics
Benefits
• You speed up your scheduling by using centrally managed templates:
– With a few clicks, you define templates that you can adapt flexibly to the specific
production requirements.
– You can forward changes to the templates automatically to the schedules.
• You react during production to changed boundary conditions and adapt your schedules on
location.
• You plan based on the created plant hierarchy and the time categories centrally managed
in TIA Portal and thus guarantee data consistency.
• You collect basic data for additional evaluations and actions related to the shift, such as
quantity statistics and production overviews.
Configuration and operation

You make preparations for the scheduling during the engineering in TIA Portal. You perform
the scheduling in runtime in the calendar control. Scheduling consists of template
management and shift planning.

8.1 Basics
8.1.2 Requirements
Preliminary work in TIA Portal

The following preparations in engineering are requirements for scheduling in WinCC Unified
Runtime:
• Mapping the plant model of your production line or station in a plant view
• Defining a time model (Common Time Model, CTM) and the time categories required for
the shift definition
See Configuring the time model. (Page 13).
• Inserting calendar objects at the plant objects of the plant hierarchy
See Creating a calendar (Page 19).
• Basic configuration of the calendar objects
See Configuring the basic settings of the calendar (Page 20).
• Assignment of an HMI device to the plant hierarchy
• Placing calendar controls on screens
See Inserting a calendar control into a screen (Page 25).
• If the calendar control is to represent calendars of various plant objects:
– Placing a plant overview on the same screen
– Configuring the calendar control as companion control of the plant overview
Otherwise: Manually linking of the calendar control with a plant object and thus with its
calendar object
See Configuring a calendar control (Page 25).

8.1 Basics
8.1.3 Basics on scheduling in the WinCC Unified Calendar
Calendar
A calendar saves all data that are relevant for the schedules of a plant object and its lower-
level plant objects. In engineering, a plant model defines which plant objects have a separate
calendar and which inherit their calendar from a higher-level plant object.
Changes to a calendar or the plant model are passed on to runtime by loading them into a
device. With a complete download, the changes become visible immediately in runtime. In
the case of a delta download, the changes become visible after a screen change or a browser
refresh.
Note
Loading changes to the plant model
Use complete download to load changes to the plant model into a device.
Note
Data losses in runtime due to changes in engineering
When a calendar or plant model is changed in engineering after schedules have been created
in runtime in the calendar, this can lead to data loss:
• Deleting or moving a plant object with the calendar
on to lower-level objects and overwritten there, this data is also deleted.
• Inserting a new calendar at a plant object
If the plant object has inherited and overwritten a calendar in runtime, this data is deleted.
If the calendar was passed on to lower-level objects and overwritten there, this data is also
deleted.
• Deleting a calendar from the plant model
on to lower-level objects and overwritten there, this data is also deleted.
• Changes to tag access of the calendar
When a member tag that is used by an action element in runtime is disabled, its status is
set to "Undefined" in the calendar after the next compile and load.
Calendar control
The calendar control is the HMI control with which you create schedules in runtime.
The calendar control has access to the time categories defined in engineering.
Each calendar control has a link to a plant object. The link allows the calendar control to
access the following in runtime:
• The calendar of the linked plant object
The calendar can be created or inherited at the plant object.
• The member tags of the plant object and its lower-level plant objects

8.1 Basics
Template types
Before you create schedules, you define templates. The following types of templates are
available:
Action templates
In action templates, you define access to the member tags of the plant objects using action
elements.
Shift templates
With shift templates, you define typical shifts, for example early shift and night shift.
You create shift templates by:
• Adding time intervals to the desired time categories.
• (Optional) Instantiating action templates in the shift template.
Day templates
With day templates, you define typical sequences of shifts.
You create day templates by:
• Instantiating shift templates
• (Optional) Instantiating action templates.
Templates and instances

Templates are defined in the template view. When you use a template, the template is
instantiated. Each template can have any number of instances.
You can use templates:
• For template planning in the template views
Templates can be nested.
Example: A day template uses a shift template, which in turn uses action templates. When
you instantiate the day template in the planning view, a day is created that contains shifts
with actions.
• For scheduling in the planning views
The following table provides you with an overview as to where you use which template types:
Template type Shift definition view Day definition view Planning views
Action templates X X X
Shift templates - X X
Day templates - - X
Edit templates
If you edit a template that already has instances, you decide whether the changes are
adopted by the instances.

8.1 Basics
Editing instances
You can edit instances so that they deviate from their templates. For example, you can
extend a time period in a shift or add another action element to an action.
Shifts are marked with the following note: "<Template name> (customized)"
Availability of templates
Templates are available only in the calendar in which they were defined and in the inheriting
calendars.
Shifts and time periods

A shift is composed of any number of time periods. The time categories of the time model
define which time periods are available, for example in operation, in maintenance and
shutdown. Time periods always belong to one shift. Their start time is relative to the start
time of their shift.
Shift instances belong to a day template or a working day. You define the duration of a shift
in the template view and its start time in the planning view. The end time of the shift
instance is calculated from the duration and start time.
Shifts can be linked to actions.
Actions
Actions are used to control the member tags of the plant objects to which the calendar has
access. Actions contain action elements at which you define which tag accesses the action
and which value you assign to it.
Actions are also instantiated in a shift. The system uses the anchor of the action and the
offset of the action element to calculate when the tag will be set in the shift in runtime.
Working days
In the properties of a calendar object, you define which days in this calendar are working
days. Working days can be business days and weekend days.
Past planning data

Data which is in the past is retained.
See also
Inheritance of calendars (Page 39)
Defining tag access of the calendar (Page 22)

8.1 Basics
8.1.4 Inheritance of calendars
Definition
A plant object that has a calendar passes the calendar on to its lower-level plant objects
recursively. The calendar is visible in runtime at the lower-level objects, but initially read-only.
Inherited shifts are shown hatched.
The lower-level objects can add to and overwrite the inherited calendar data. When you edit a
shift in an inherited calendar, for example by extending it, you overwrite the shift.
Overwriting interrupts the inheritance.
The shift is executed in runtime as it has been defined at the lower-level object.
Data inconsistencies due to overwriting

Inheritance can lead to inconsistencies between the data which are visible at a lower-level
planning object and its higher-level planning object in the calendar.
Examples of the formation of such inconsistencies:
• When an inherited shift is overwritten at a lower-level object and then changed again in
the higher-level calendar, this change is not visible at the lower-level object.
• A new shift is created at a lower-level object. The shift is not visible at the higher-level
object in the calendar.
Afterwards, a shift is created at the higher-level object in the calendar that overlaps with
this shift.
When a calendar is being saved the system therefore checks whether the shifts to be saved
have been overwritten by the inheriting calendars. If they have been overwritten, the system
notifies you that inconsistencies will arise from the saving. Check and rectify the
inconsistencies.
If an inherited shift and a shift that is newly created or edited in the inherited calendar
overlap, the overlap is visually highlighted at the inheriting calendar:
Note
No inheritance of actions
Actions cannot be inherited.

8.1 Basics
Example
1. A scheduler instantiates, in a calendar of a plant, a day template consisting of early shift,
midday shift and late shift. The unit of the plant inherits the calendar.
2. At the unit, the scheduler shortens by 30 minutes the midday shift inherited from the plant.
3. Another scheduler extends the early shift at the plant by one hour.
During saving, a prompt informs the scheduler that these changes will lead to
inconsistencies in inheriting calendars. A visual note about the shift overlap appears in the
calendar of the unit.
At the end of the early shift and the start of the midday shift, defined calendars are read out
during runtime from the calendars defined at the unit and entered accordingly in the context
log.
See also
Editing inherited shifts (Page 90)
8.1.5 Context logging

WinCC Unified Calendar supports context logging:
• Each shift is identified by a shift ID.
You can find the shift ID in the shift properties.
• When the shift starts, a new entry is created in the context logging.
See also
Shift properties (Page 78)

8.1 Basics
8.1.6 Overall workflow
Introduction
Users with the following roles participate in the creation of schedules with WinCC Unified
Calendar:
• Template designers
Template designers create action templates, shift templates and day templates in the
template views, or change existing templates.
• Schedulers
Schedulers instantiate the templates in the planning views. They thus create schedules for
the plant which implement specifications of the plant management.
If necessary, they change the instances so that they differ from their templates. For
example, they can extend or shorten time periods, move shifts or add an action.
• Operators
Operators inform you during the operation about the pending schedules and
requirements. The operators check during the operation whether changes to the
schedules are necessary and carry them out.
The following example illustrates which tasks these users carry out in runtime.
Example
An automotive supplier initially creates schedules for their plant with WinCC Unified Calendar.
• The plant manufactures side view and rearview mirrors. It is configured with the following
plant view in TIA Portal:
"Plant"
> "SideViewMirror"
> "Line_LeftMirror"
> "Line_RightMirror"
> "RearViewMirror
> "Line_RearViewMirror"
• "Plant" has a calendar which is passed on to the "SideViewMirror" and "RearViewMirror". It
can be overwritten at the plant objects below "Plant".
• The process pictures were configured in TIA Portal so that users select via the plant view
control which calendar is displayed in runtime in the calendar control.

8.1 Basics
Tasks of the template designer

The template designer creates the following templates in the "Plant" calendar on the basis of
operational regulations and according to the general specifications of the plant management:
1. Action templates
For example, three action templates that set the quantity, one template each for the right
side-view, the left side-view mirror and the rear-view mirror.
The template designer adds an action element to each action template. It determines
which member tag the action element sets.
2. Shift templates
For example, the templates "Early shift", "Late shift" and "Night shift"
3. Day templates
For example, the templates "2-shift day" (consisting of instances of "Early shift" and "Late
shift") and "3-shift day" (consisting of instances "Early shift", "Late shift" and "Night shift")
Once the introductory phase has been completed, the template designer can change existing
templates or create new templates.
Note
Edit templates and update instances
When the template designer changes a template that already has instances, the designer
decides during saving whether the changes are adopted or not by the instances.
Tasks of the scheduler
Tasks for "Plant"

The calendar created for "Plant" in TIA Portal is inherited by all plant objects under "Plant". At
the "Plant" calendar, the scheduler defines basic schedules that apply to all units of the plant.
The scheduler performs the following tasks:
1. Selects "Plant" in the plant overview control so that the "Plant" calendar is displayed.
2. Creates instances of the day template "2-shift day" for all working days of the next four
weeks.
3. Changes the "Early shift" or the last day in this time period.
A works council meeting is scheduled for this day. The scheduler shortens the shift in
order to create an empty time between early shift and late shift for the works council
meeting.
4. Saves the changes.
They are transferred to the server and the other clients are updated.

8.1 Basics
Note
Check for inconsistencies when a calendar is changed
During saving the system check whether the elements changed in the calendar were
overwritten by plant objects below them. If yes, the scheduler receives a prompt that
inconsistencies arise during saving. The scheduler must then check and eliminate these
inconsistencies.
Tasks for "Line_LeftMirror" and "Line_RightMirror"

For both product lines the scheduler defines changes to the inherited calendar. The scheduler
performs the following tasks:
1. Selects "Line_LeftMirror" in the plant overview control so that the calendar of this production
line is shown.
2. Instances the action template "Quantity" that was defined for the left side-view mirror at
each shift instance.
3. Enters the planned quantity for this shift at this action element.
4. Repeats these steps for "Line_RightMirror".
Note
Change instances and interrupt inheritance
Through the change the inherited shift instances are overwritten and the inheritance
interrupted.
If one of the shifts is changed later at a plant object above the production line, this change is
not displayed in the calendars of the production lines. Data inconsistencies arise. If the
planning view shows the calendar defined on "Line_LeftMirror" or "Line_RightMirror", visual
highlighting draws the scheduler's attention to the inconsistency.
The definition that was defined further down in the hierarchy continues to apply in runtime
as long as the inconsistency exists. In the example, this is the definition of the production
lines.
Tasks for "RearViewMirror"

For "RearViewMirror" the scheduler defines changes at the inherited calendar. The scheduler
performs the following tasks:
1. Selects "Line_RearViewMirror" in the plant overview control so that the calendar of this
production line is shown.
2. Instances the action template "Quantity", which was defined for the rear-view mirror at each
shift instance.

8.1 Basics
3. For the last week of the planning period the quantity is so high that it can only be reached
by means of a third shift.
– The scheduler deletes the "Early shift" and "Late shift" shifts for each working day in
this week.
The connection to the day template is lost as a result.
– Creates instances of the "3-shift day" day template.
4. For the entire planning period the scheduler enters the planned quantity for this shift in the
"Quantity" action at each shift instance.
Tasks of the operator:

Gets information on the schedules during operation and monitors whether these schedules
are being met. If inconsistencies arise because an overwritten calendar element was changed
at the inherited calendar, the operator checks the conflict and resolves it.
Tasks for "RearViewMirror"

On the day of the works council meeting the production of rear-view mirrors falls slightly
behind schedule after the start of the early shift. To ensure that the specified quantity will be
produced, the operator carries out the following tasks:
1. Changes the "Early shift" by reducing the time periods for both upcoming breaks by ten
minutes each and by extending the intervening working time by twenty minutes.
2. Saves the changes.
The changes are transferred to the server and the other clients are updated. The instances are
changed and the inheritance is interrupted.
See also
Creating and deleting shift templates (Page 53)
Creating and deleting action templates (Page 57)
Creating and deleting day templates (Page 55)
Changing templates (Page 79)
Renaming a template (Page 78)
Adding and deleting days (Page 82)
Editing days (Page 84)
Working with shifts (Page 72)
Working with time periods (Page 67)

8.2 User interface
8.2 User interface
8.2.1 Overview of the user interface of the calender control

The calendar control has the following structure:
① Toolbar
② Tab for scheduling and for template planning
Each tab has the following elements:
③ • Toolbar
④ • Work area
⑤ • Selection area
⑥ In the day view and the week views in the "Planning" tab: Input panel for action elements
⑦ Status bar

8.2 User interface
Buttons on the toolbar
Ico Button Description

n
"Save" Saves all changes from the current template view or from the
planning views.
"Discard" Undoes all changes from the current view.
"Clear" Clears configured Runtime data (planning, templates, inher-

itance).
"Expand" / "Collapse" The planning view is displayed in full-screen mode. / The full-
screen mode is closed.
The button is only available in the planning view.
Status bar
The status bar offers the following information:
• Connection information
• Button for displaying the calendar settings
• Date information
See also
"Planning" and "Templates" tabs (Page 47)

8.2 User interface
8.2.2 "Planning" and "Templates" tabs
Buttons
The following buttons are available in the "Planning" and "Templates" tabs:
Icon Button Description

"Shift definition" Opens the view for defining shift templates.
"Day definition" Opens the view for defining day templates.
"Action definition" Opens the view for defining action templates.
"Day" Opens the respective planning view in which you then plan
shifts.
"Working week"
"Week"
"Month"
"Zoom in" Zooms-in in the current view.

Maximum zoom factor:
• Month view: Not available
• Action definition view: 1 hour before and after the anchor
• Other views: 2 hours
"Zoom out" Zooms-out of the current view.
Maximum zoom factor:
• Month view: Not available
• Action definition view: 8 hours before and after the anchor
• Other views: 24 hours
"Today" The planning view jumps to the current day.
"Flagged day" The planning view jumps to the highlighted day.
"Select day" Opens the date window in which you switch to a specific day.
"Export" Exports planning data and templates to a CSV file.

8.2 User interface
Icon Button Description

"Import" Imports planning data and templates from a CSV file.
Views
There are template views and planning views in the calendar control:
• You can find the planning views in the "Planning" tab. You define your schedules using
templates in these schedules.
Day view
Working week view
Week view
Month view
• You can find the template views in the "Templates" tab. You define templates in the
template views.
Shift definition view
Day definition view
Action definition view
The contents of the work area and selection area depend on the selected view.
Selecting a view
Proceed as follows to select a view:
1. Select the "Planning" or "Template" tab in the calendar control.
2. In the toolbar of the tab, click on the view button.

8.2 User interface
Work area
In the template views, the work area contains the following:
• The templates already created
• An empty header for creating an additional template
In the planning views, the work area contains a calendar section:
• The selected view determines which calendar section you see (day, week, month).
• You scroll to earlier or later planning data using the and buttons or the mouse wheel.
Selection area
The following panes are visible in the views:
Panes Shift definition Day definition Action definition Planning

view view view views
Categories X X - X
Shift templates - X - X
Day templates - - - X
Action templates X X - X
Action elements - - X -
You show or hide the selection area using the following buttons:
You show or hide a pane using the following buttons:

8.2 User interface
Special displays in the work area
Unsaved data
Unsaved data is marked with an * and displayed transparently.
Example:
• Shift template with new time period before saving:
• Shift template after saving:
Shifts that deviate from the template

Shift instances that were edited and deviate from their template are marked with the
following note: "<Template name> (customized)"
Inherited shifts
In the planning view, shifts from inherited calendars are shown hatched.
You can edit the shift and thereby overwrite the inherited data. See section Editing inherited
shifts (Page 90).

8.2 User interface
Overlapping shifts
In the inherited calendars, shifts can overlap, for example when a shift is inserted that adjoins
an inherited shift and the inherited shift is then moved in the original calendar. In the
inherited calendar such overlaps are visually highlighted:
Selection
Selected time periods and shifts have a dashed border:
Deleted time categories

Time intervals whose time category has been deleted in the engineering system are marked
with an "*" after the change has been loaded into runtime.
Mouse-over behavior
If you hover with the cursor over a day in week views and in the month view, the day has a
light gray border:

8.2 User interface
If you hover with the cursor over one of the following elements, the following tooltips are
displayed above and next to the element:
Time period • View dependent:

– Month view: Duration, shift name, and name of the time period
– Day view and week views: Duration of the time slice
– Template views: Duration of the time slice
• Start time
• End time
Shift • View dependent:
– Month view: Duration and shift name
– Day view and week views: Duration
– Template views: Duration
• Start time
• End time
Action element • View dependent:
Day view, week views, shift definition and day definition: Time
• Offset in minutes
• Path to linked tag and the value to be set
Current time
The current time is displayed as follows in the planning view:
Current day
The current day is displayed as follows in the planning view:
Flagged day
The day flagged for tracking is marked as follows in the planning view:

8.3 Creating templates
Day instances
For day instances that have not been edited, the name of the day template is displayed in the
week views and day view in the right-hand margin next to the date.
8.3.1 Creating and deleting shift templates
Procedure
1. Select the "Templates" tab.
2. Click "Shift definition".
In the selection area, you see the available categories.
You can see the available shift templates in the working area. You see an empty header in
the row at the very bottom.
3. Add a time period to the empty header.
See also section Adding and deleting time periods (Page 67).
4. In the "Shift properties" dialog, enter the name of the shift.
5. Optional: Enter a display name and a description and change the shift duration.
6. Click "OK".
A new shift template with this time period is created.
7. Add additional time periods to the shift template.

8. Optional: Add one or more actions.
9. Click "Save".

Result
• The shift template is saved in the calendar and transferred to the server. It is automatically
available in the other clients.
• You can use the template in this calendar:
– Defining day templates
– In the planning view for the scheduling
• You can edit the template at any time.
Copy shift template

If a shift template is already available, you can create a new template based on this template:
2. Click "Shift definition".
3. Right-click the header of the shift template. Select "Copy" or press Ctrl+C.
4. Right-click the empty header in the bottom row. Select "Paste" or press Ctrl+V.
The template is copied. You can adapt it as you like.
Delete shift template

Select "Delete" in the shortcut menu of the template header.
Or select the template header and press Del.
See also
Adding or deleting actions (Page 62)
Creating and deleting day templates (Page 55)

8.3.2 Creating and deleting day templates
Requirement
• At least one shift template is available.
Procedure
2. Click "Day definition".
In the selection area, you see the available categories and shift templates.
You can see the available day templates in the working area. You see an empty header in
3. Add a shift to the empty header.
See also section Adding and deleting shifts (Page 72).
4. Enter the name of the template in the "Day properties" dialog.
5. Optional: Enter a display name and a description.
6. Click "OK".
A new day template with this shift is created.
When the shift template you are using has an action, the shift also has an action.
7. Add additional shifts to the day template.
8. Optional: Edit the shifts. You have the following options:
– Adding or deleting time periods
– Shortening or extending time periods
– Moving time periods
– Adding, deleting or moving shifts
– Shortening or extending a shift duration
– Moving shifts
– Adding, deleting or moving actions
9. Click "Save".

Result
The template is saved and transferred to the server. It is automatically available in the other
clients.
The template can be used in the planning view for the scheduling.
You can edit the template at any time.
Copy day template

If a day template is already available, you can create a new template based on this template:
2. Click "Day definition".
3. Right-click the header of the day template. Select "Copy" or press Ctrl+C.
4. Right-click the empty header in the bottom row. Select "Paste" or press Ctrl+V.
The template is copied. You can adapt it as you like.
Delete day template

See also
Adding and deleting time periods (Page 67)
Shortening or extending time periods (Page 71)
Moving time periods (Page 69)
Shortening or extending shifts (Page 76)
Moving shifts (Page 75)

8.3.3 Creating and deleting action templates
Procedure
2. Click "Action definition".
You can see the available action templates in the working area. You see an empty header in
3. In the selection area, click an action element and keep the left mouse button pressed.
Each action element represents a tag to which the calendar has access.
4. Move the mouse cursor to the empty header, to the left or right of the anchor of the action
and release the mouse cursor.
5. Enter the name of the template in the "Action properties" dialog.
6. Optional: Enter a display name and a description.
7. Click "OK".
The action template is created.
1 Action name
2 Anchor of the action
3 Action element
4 Offset of the action element
The distance to the anchor determines the duration of the offset.
8. Optional: Edit the action element.

You can change its offset, select a different action element or set the tag value.
9. Add additional action elements to the action template or delete an action element.
Note
Maximum of five action elements
An action template can have a maximum of five action elements.
10.Click "Save".

Result
• The template is saved and transferred to the server. It is automatically available in the
other clients.
• You can use the template for shift definition, for day definition as well as for scheduling in
the planning view.
• You can edit the template at any time.
Delete action template

See also
Adding or deleting action elements (Page 60)
Editing action elements (Page 61)
8.3.4 Saving or discarding changes

All changes in the calendar control are first made locally in your browser window.
You have two storage options:
• Save template and update instances
The instances in the planning view are updated automatically. Customized instances with
the note "customized" are not updated.
• Save template and do not update instances

Saving
To transfer your changes in the current template view to the server and save them, follow
these steps:
1. Click "Save" in the toolbar.
The "Unsaved changes" dialog opens.
2. Select your option and click "OK".
Result
The changes are transferred to the server and are automatically available at the clients.
When the calendar control is opened in other browser windows, it is automatically updated.
Your changes are available to other users.
Note
Overwriting of unsaved changes
If users work in different browser windows in the same view, unsaved changes can be lost.
The user who saves first overwrites the unsaved changes of the second browser window.
Note
Inconsistencies due to interrupted inheritance
If a shift changed by you has been overwritten in an inheriting calendar, the system notifies
you that inconsistencies will arise from the saving. Check and rectify the inconsistencies.
If an overwritten and an inherited shift overlap, an optical note is shown under the shift at
the inherited calendar.
Discarding
To discard changes, click "Discard" in the toolbar.

8.3.5 Working with action elements in action templates
8.3.5.1 Adding or deleting action elements

You can add up to five action elements to an action template.
Requirement
• An action template exists.
Adding an action element

3. In the selection area, click an action element and keep the left mouse button pressed.
4. Move the mouse cursor to an action template, to a position to the left or right of the anchor
of the action.
5. Release the cursor.
The action element is inserted with the offset defined by the mouse cursor.
Note
Maximum offset
The maximum offset of an action element is +/- eight hours in relation to its anchor.
6. Optional: Edit the action element.

You can change its offset, select a different action element or set the tag value.
Deleting the action element

Select "Delete" in the shortcut menu of the action element
Or select the action element in the work area and press Del.
See also
Editing action elements (Page 61)

8.3.5.2 Editing action elements
Introduction
You can change the following properties:
• Offset
Note
Maximum offset
The maximum offset of an action element is eight hours.
• Action element
• Tag value
Note
As soon as you make changes, the instance is decoupled from the template. Changes in the
template then no longer affect the instance.
Requirement
• An action template exists.
Procedure
1. Select an action.
The input panel is expanded in the lower area.
2. Change the properties.
Alternative procedure
3. Click "Select tag" in an action template in the shortcut menu of an action element.
The "Action properties" dialog opens.
5. Click "OK".
Move offset with mouse button

As additional alternative, keeping the left mouse button pressed, drag the action element to
the right or left until the tooltip displays the desired offset value.

8.3.6 Working with actions
8.3.6.1 Adding or deleting actions

You add or delete actions in the following cases:
• When creating or editing a shift template or a day template
• When creating schedules in the planning views
Note
No actions in the month view.
You cannot add or see actions in the month view.
Note
No inheritance of actions
Actions are not passed on to the underlying calendar.
Requirement
• At least one action template exists
• When you are working in a day template or in the planning views: A shift exists in the
view.
• To add an action to a day template or shift template: The respective template exists.
• When the shift is inherited, you must first select "Edit" in the shortcut menu of the shift.
The shift then overwrites the inherited shift and you can edit it.

Add action
1. Select the desired view in the calendar control.
2. In the selection area, click an action template and keep the left mouse button pressed.
3. Move the cursor to the header of the desired shift to the place where you want to anchor
the action in the shift.
Note
Time of value assignment in runtime
A tag is assigned to each action element of an action. In runtime, the system calculates
when the tag value will be set based on the start time of the shift, the offset between shift
start and anchor of the action, and the offset of the action element.

The action is added to the shift.
5. Optional: Move the anchor point of the action.

6. Optional: Edit the action elements of the action.
You have the following possibilities:
– Changing the offset of the action element
– Select other action element
– Set tag value
– Disable or enable the action element
Note
Maximum five actions
A shift can have a maximum of five actions.
Deleting an action
Select "Delete" in the shortcut menu of the action.

Displaying actions
Actions are only visible while their shift is selected. The month view show no actions.
1 Anchor point of the action

2 Deactivated action element
3 Offset of the action element
The distance from the anchor determines the duration of the offset.
4 Activated action element
See also
Adding and deleting shifts (Page 72)
Editing actions (Page 64)
Edit action elements in shifts (Page 66)
8.3.6.2 Editing actions

You edit actions in the following cases:
• In the planning views when editing a shift
Note
No actions in the month view.
You cannot see or modify actions in the month view.
Note

Requirement
• The desired view is open.
• A shift with action exists in the view.
Moving the anchor of the action

The anchor of an action is always defined in relation to the start time of its shift. When you
move the anchor, this affects the execution time of the action elements during runtime.
Proceed as follows to move the anchor:
1. Click on the shift whose action you want to edit.
The actions of this shift are displayed.
2. Move the cursor to the anchor point of the action displayed in the shift register.
3. Keeping the left mouse button pressed, move the anchor point to the left or right until the
desired position.
The anchor of the action is moved and with it its action elements.
Editing action elements

• Adding or deleting an action element
• Disable or enable the action element
• Switch action element or change tag value
• Changing the offset of an action element
See also
Adding or deleting action elements (Page 60)

8.3.6.3 Edit action elements in shifts

You edit action elements in shifts in the following cases:
• When creating schedules in the planning views
Note
Actions not visible in the month view
You cannot see or modify actions in the month view.
You can change the following properties:

• Offset
Note
Maximum offset
The maximum offset of an action element is +/- eight hours in relation to its anchor.
• Action element
• Tag value
Note
Requirement
• The desired view is open.
• A shift with action exists in the view.
Modify properties
1. Select an action.
The input panel is expanded in the lower area.

Alternative procedure
1. Click "Select tag" in an action in the shortcut menu of one of your action elements.
The "Action properties" dialog opens.
3. Click "OK".
Move offset with mouse button

As additional alternative, keeping the left mouse button pressed, drag the action element to
the right or left until the tooltip displays the desired offset value.
Disable or enable the action element

Deactivated action elements are not executed during runtime.
Follow these steps:
1. In the shortcut menu of the action element, select the command "Disable".
The display of the action element changes.
2. To activate the action element again, select the "Enable" command in the shortcut menu.
8.3.7 Working with time periods
8.3.7.1 Adding and deleting time periods

You add time periods in the following cases:
• When creating or changing a shift template or a day template.
• When working in the planning view to adapt a used template instance
Note
Not available in the month view
You cannot add time periods in the month view.

Requirement
• For the work in the planning views or the day definition view:
A shift exists in the work area.
• For the work in the planning views:
If the shift in which you want to add or delete time periods is inherited, you must first
select "Edit" in the shortcut menu of the shift. The shift then overwrites the inherited shift
and you can edit it.
Procedure
1. Select the desired view.
2. The shift must have an empty period that is long enough for the new time period. If
appropriate, shorten or delete a time period already included, extend the overall duration of
the shift or move the time periods to create space.
3. Select a calendar-relevant category in the selection area.
Note
Calendar-relevant categories
The selection area shows the entire category tree defined in engineering. Categories that
are not relevant for calendar are grayed out in runtime.
4. Move the cursor in the work area onto an empty period of the shift.
5. Keep the mouse button pressed and draw in the starting point and the end point of the time
period.
Note
Selecting the starting point and the end point
The new starting point or end point cannot overlap with other time periods or extend
beyond the shift limit.
The added time period has the name and color of the category.
Deleting time periods

Select "Delete" in the shortcut menu of the time period.
Or select the time period in the work area and press Del.
See also

8.3.7.2 Moving time periods

You move time periods in the following cases:
• When creating or editing a shift template or a day template.
• When working in the planning view to adapt a template instance.
Note
You cannot move time periods in the month view.
Requirement
• A shift that has time periods exists in the desired view.
• To move a time period whose shift is inherited, you must first select "Edit" in the shortcut
menu of the shift. The shift then overwrites the inherited shift and you can edit it.
• When placing in an empty period, the empty period has to be at least as long as the time
period.
With the mouse

2. Position the cursor on a time period.
3. Keep the left mouse button pressed and select one of the following options:
– Move the mouse to an empty time.
Tooltips show the new start time and end time of the time period.
– Move the mouse to a different time period.

Two arrows indicate the future position.
4. Now release the mouse button.

Result
• The time period is moved to the new position.
• When you have moved the time period to the last time period of the shift, the time period
is always positioned after the other time period; otherwise, it is positioned beforehand.
• If shifts lie to the right of the time period insertion point, they are moved to the back.
With keyboard shortcuts

Requirement: The time period is adjacent to an empty period.
2. Click the time period.
3. Use the following keyboard shortcuts:
Shortcut Description
Left arrow Shift left - by 10 minutes
Right arrow Shift right - by 10 minutes
Ctrl+Left arrow Shift left - by 1 minute
Ctrl+Right arrow Shift right - by 1 minute
Note
Limitation
You can move the time period at the most to the next adjacent time period. The time
periods cannot be swapped.
Engaging via shortcut menu

Requirement: The time period is adjacent to an empty period.
1. In the shortcut menu of the time period, select the entry "Snap left" or "Snap right".
The time period directly adjoins the right-hand or left-hand time period or the beginning or
end of the shift. Its duration does not change. The empty period is moved accordingly.

8.3.7.3 Shortening or extending time periods
Note
You cannot change time periods in the month view.
Requirement
• A shift that has time periods exists in the desired view.
• For the work in the planning views:
If the shift in which you want to add or delete time periods is inherited, you must first
select "Edit" in the shortcut menu of the shift. The shift then overwrites the inherited shift
and you can edit it.
• To extend a time period, the time period must adjoin an empty period that is sufficiently
long.
If required, create space by reducing, deleting or moving an adjacent time period.
With the mouse

2. Move the cursor to the right-hand or left-hand edge of the time period.
The pointer changes to a double-arrow. You see tooltips with the start time and end time
of the time period as well as its duration:
3. Hold down the left mouse button and drag the frame to the left or right until the tooltips
show the desired values.
Note
Limitation
The new starting point or end point cannot overlap with other time periods or extend
beyond the shift limit.


2. Click the time period.
Shift+Left arrow Extend by 10 minutes
Shift+Right arrow Shorten by 10 minutes
Ctrl+Shift+Left arrow Extend by 1 minute
Ctrl+Shift+Right arrow Shorten by 1 minute
Note
Restriction for extending
You can extend the time period at the most to the next adjacent time period.
See also
8.3.8 Working with shifts
8.3.8.1 Adding and deleting shifts
Introduction
Shifts are instances of shift templates. You add shifts in the following cases:
• When creating or editing a day template
Use a shift template.
• During shift planning in the planning view
Select one of the following options:
– Use shift templates
– Use day template that instantiates shifts
See section Adding and deleting days (Page 82).
– Copy the planned shift
– Make a recurrence from a planned shift
See section Creating a recurrence for a shift (Page 86).

Requirement
At least one shift template is available in the calendar displayed in the calendar control.
Use shift templates

1. Select the desired view in the calendar control.
2. In the selection area, click a shift template and keep the left mouse button pressed.
3. Move the cursor to a day template or to a day onto the position at which the shift is to start.
A tooltip shows whether insertion is permitted at this position:
Insertion permitted
Insertion not possible
Note
Extend empty time
You can only insert the shift if the empty time after the insertion position is at least as
long as the shift. If necessary, move or delete a shift that has already been added.
Copying shifts in the planning view

You can reuse shifts that have already been planned:
1. Select the "Planning" tab.
2. Select one of the week views or the day view.
3. Right-click on the header of a shift and select "Copy" or use the keyboard shortcut Ctrl+C.
4. Right-click elsewhere in the calendar and select "Paste" or use the keyboard shortcut Ctrl+V.
A view change is not possible.
The shift is copied and pasted.
Note
No shift overlaps
If the insertion location is selected so that the shift overlaps with the next shift, it will not be
inserted.
Result
The shift is inserted into the day template or the day. It receives the same name as its
template. When the shift template you are using has an action, the shift also has an action.

You can adapt the shift at any time:

• Add time periods
• Delete time periods
• Move time periods
• Shorten or extend time periods
• Shorten or extend a shift duration
• Move a shift
• Assign unique shift ID for context logging
• Add, delete or edit actions
• In the planning view: Plan the shift as a recurrence.
Deleting shifts
Select "Delete" in the shortcut menu of the shift header.
Or select the shift in the work area and press Del.
Note
Restoring an inherited shift
You can restore a deleted, inherited shift by resetting the day.
See also
Restoring days (Page 85)
Shift properties (Page 78)

8.3.8.2 Moving shifts

You have the possibility to change the start time of a shift by moving it in the day definition
view, in the day view and in the week views:
You can move a shift beyond day boundaries in the day view and in the week views.
Note
Limitation
You can move a shift at the most until the next adjacent shift.
Requirement
• A shift exists in the desired view.
• An inherited shift must first be released from its write protection by clicking "Edit" in the
shortcut menu of the shift.
The shift then overwrites the inherited shift and you can edit it.
With the mouse

2. Position the cursor on the shift.
3. Hold down the left mouse button and move the shift to the desired position, for example to
the beginning of the day.
Note
Moving a shift into an empty period
Make sure that the empty period is long enough.
Select the new start time so that the end of the shift does not overlap the adjacent shift or
extend beyond the day end.
The view is moved to the new position. If shifts lie to the right of the insertion point, they are
moved to the back.


Requirement: The shift is adjacent to an empty period.
2. Click on the shift header.
Left arrow Move 10 minutes earlier
Right arrow Move 10 minutes later
Ctrl+Left arrow Move 1 minute earlier
Ctrl+Right arrow Move 1 minute later
See also
8.3.8.3 Shortening or extending shifts

You can shorten or extend shifts in the shift definition view, the day definition view and in
the planning views.
Note
Restrictions
• You cannot change the shift duration in the month view.
• You can shorten the shift at the most until its first or last time period.
• In the day definition view and in the planning views, you can extend the shift at the most
until the next adjacent shift or until the end of the day.
• Shifts have a minimum duration of two hours.
Note

Requirement
• For the shift definition view: There is a shift template.
• For the day definition view: There is a day template with a shift.
• For the planning views:
– A shift that has time periods exists in the desired view.
– For an inherited shift, you must first select "Edit" in the shortcut menu of the shift. The
shift then overwrites the inherited shift and you can edit it.
• In order to extend a shift, the shift must adjoin an empty period that is sufficiently long.
If required, create space by shortening, deleting or moving an adjacent shift.
With the mouse

1. Open the desired view.
2. Move the left-hand or right-hand edge of the shift header to the right or left while keeping
the left mouse button pressed.
A tooltip shows the current duration of the shift.
3. Release the cursor when the shift has the desired duration.

You can also use keyboard shortcuts to shorten or extend the shift end:
2. Click on the shift header.
Shift+Left arrow Shorten by 10 minutes
Shift+Right arrow Extend by 10 minutes
Ctrl+Shift+Left arrow Shorten by 1 minute
Ctrl+Shift+Right arrow Extend by 1 minute
Via the properties

1. Double-click the shift header.
2. Enter the desired duration in minutes in "Duration (min)".
3. Click "OK".
See also

8.3.8.4 Shift properties

To check or set the properties of a shift, double-click the shift header.
For an inherited shift, you must first select "Edit" in the shortcut menu of the shift. The shift
then overwrites the inherited shift and you can edit it.
Properties
"Name" Name of the shift template
Read-only
"Duration (min.)" The duration is automatically updated when the
shift duration is edited in the work area.
"Comment" Comment field for the user
"Shift ID" Only in the planning views
For the unique identification of the shift in the
context logging.
Enter a number between 1 and 99.
Preset value: 1
8.3.9 Renaming a template

Proceed as follows to rename shift templates, day templates and action templates:
1. Double-click the header of the desired template in one of the template views.
A dialog box opens.
2. Enter the desired name.
If the template already has instances, the name of its instances is updated automatically. This
also applies if you specify, when saving the template or when exiting the template view, that
the instances should not be updated.

8.3.10 Changing templates

You can change the templates at any time. When you save, you transfer changes to the
server all the changes that you made to a template view. The changed templates are
automatically available at the clients.
If a template already has instances, the system prompts you to decide whether the changes
have been adopted by the instances.
If you exit a template view without saving, the system prompts you to decide what to do with
the changes made in this template view.
Note
Note
Automatic name application on name change
If you rename a template, the name is updated automatically in the instances. This also
applies if you specify, when saving the template or when exiting the template view, that the
instances should not be updated.
Overview of the change options
Changing shift templates

• Renaming a template
• Adding and deleting time periods
• Shortening and extending time periods
• Moving time periods
• Shortening and extending shifts
• Adding, updating and deleting action templates

Changing day templates

• Adding and deleting shifts
• Shortening and extending shifts
• Moving shifts
• Adding and deleting time periods
• Shortening and extending time periods
• Moving time periods
• Adding, updating and deleting action templates
Changing action templates

• Editing an action
• Adding and deleting action elements
• Editing action elements
See also

8.4 Creating and adapting schedules

You create the schedules for your production lines and stations in the planning views using
the available templates.
• Changing day templates
The days instantiated by means of day templates have pre-configured shifts. You can
adjust the days. Add actions, change the shifts instantiated with the day or instantiate
new shifts using shift templates.
• Using shift templates
Shift templates are used to adjust days that have been scheduled with day templates.
It is advisable to use day templates as they make scheduling clearer and faster. However,
their use is not mandatory. You can also create schedules by directly instantiating shift
templates in the planning view in a day. You then adjust the shift instances as usual to the
requirement.
Note
See also
Adding and deleting days (Page 82)
Working with shifts (Page 72)

8.4.1 Adding and deleting days

Days are instances of day templates. You use them in the planning view for the scheduling.
Requirement
At least one day template is available.
Procedure
2. Click on the button of a planning view.
3. In the selection area, click a day template and keep the left mouse button pressed.
4. Move the cursor in the work area onto an empty day.
A tooltip shows whether the day template may be inserted at this position:
Insertion is permitted.
Insertion is not permitted.
Result
• The day template is instantiated, and the day instance is placed at a pre-defined start of
the day.
For day instances that have not been edited, the name of the day template is displayed in
the week views and day view in the right-hand margin next to the date.
• When the day template you are using has an action, the day also has an action.
You can adapt the day at any time, for example, by moving shifts or adding actions.
Note
Update of customized day instances
Updates of day templates cannot be used for customized day instances.

Copying days
You can reuse days that have already been planned:
2. Select one of the week views.
3. In the work area, right-click on a date and select "Copy".
4. Right-click on another date and select "Paste".
A view change is not possible.
The day is copied and inserted.
If the copied day is based on a day template and does not deviate from it, the name of the
day template for the pasted day is also displayed in the week views in the right-hand margin
next to the date.
Deleting days
To delete a day instance, delete all shifts of the day.
To delete all shifts of a day at once, select "Delete day" in the shortcut menu of a day.
See also
Saving or discarding changes (Page 89)

8.4.2 Editing days
Note
Requirements
Planning data is present in the planning view.
In the week views or the day view

You can edit days as follows:
• Add actions to a shift or delete actions
• Edit actions of a shift, e.g. define new action elements or set tag values
• Add, delete or move shifts
• Shorten or extend a shift duration
• Add time periods to a shift, delete or move time periods
• Shorten or extend time periods
• Delete the day
In the month view

You can add or delete shifts.

See also
Creating a recurrence for a shift (Page 86)
Editing actions (Page 64)
8.4.3 Restoring days

If you have edited or deleted shifts in an inherited calendar, you can reset the shifts to their
original, inherited state.
Requirement
Shifts that were inherited and overwritten exist in the planning view.
Procedure
In the planning view, select "Reset day" in the shortcut menu of the day.
Result
All shifts of the day are reset to the inherited state.
See also

8.4.4 Flagging a day

Double-click on the desired day in a planning view in the working area.
The day flagged for tracking is marked as follows in the planning view:
Switching to the flagged day

Click the "Flagged Day" button in one of the planning views.
8.4.5 Creating a recurrence for a shift

In the planning view, you can create a recurrence for an existing shift.
Requirement
• A shift is planned in the planning view.
Procedure
3. Right-click on the header of a shift and select "Recurrence".
4. In the "Recurrence" dialog, specify the pattern and time period of the recurrence.
The following entry limitations apply:
– Start date / end date: Maximum difference of 1 year
– Monthly: 1 to 99
– Weekly: 1 to 99
– Daily: 1 to 999
5. Confirm your entries.
Result
In accordance with the pattern, shifts are inserted into the calendar in the time period
defined by you.
Note
Behavior in case of overlap
If the recurrence leads to overlaps with shifts already scheduled, the entire recurrence will
fail.

8.4.6 Creating a recurrence for a day

In the planning view, you can create a recurrence for an existing planned day.
Requirement
• One or more shifts are planned for this day in the planning view.
• All changes for this day have already been saved.
Procedure
3. Right-click on a date and select "Recurrence".
4. In the "Recurrence" dialog, specify the pattern and time period of the recurrence.
The following entry limitations apply:
– Start date / end date: Maximum difference of 1 year
– Monthly: 1 to 99
– Weekly: 1 to 99
– Daily: 1 to 999
5. To overwrite planned days, enable the "Overwrite" option.
6. Confirm your entries.
Result
The recurrence is added as defined to the calendar.
Note
Behavior in case of overlap and partial shifts
When the "Overwrite" option is not selected and there are overlaps with planned shifts, the
entire recurrence will fail.
When a shift extends over two days in which one day is included in the recurrence and the
other is not, the entire recurrence will fail. Overwriting is only possible when the existing
shifts are completely contained within the days of a recurrence.

Example
The following table is an example of the use cases for recurrences on planned days.
Use case User action Explanation Result

Recurrence with complete shift The recurrence is planned for 16 The existing planning for The recurrence is created
overwrite June 2020: The daily recurrence 20 June 2020 and 22 successfully.
starts on 19 June 2020 for the June 2020 is overwrit-
next 10 days. ten.
Recurrence with partial shift The recurrence is planned for 16 The existing planning for
overwrite June 2020: The daily recurrence 17 June 2020, 20 June
starts on 17 June 2020 for the 2020 and 22 June 2020
next 10 days. is overwritten.
Recurrence with partial shift The recurrence is planned for 16 The existing planning is The entire recurrence
overwrite June 2020: The daily recurrence not overwritten because fails.
starts on 18 June 2020 for the one of the shifts is not
next 10 days. within the recurrence
period.
Recurrence with partial shift The recurrence is planned for 16 The existing planning is
overwrite June 2020: Recurrence starts on not overwritten because
17 June 2020 for every second one of the shifts is not
day in the next 10 days. within the recurrence
period.
The figure illustrates the various use cases from the example.

8.4.7 Saving or discarding changes

All changes in the calendar control are first made locally in your browser window.
Saving
To transfer your changes in the current planning view to the server and save them, click
"Save" in the toolbar.
Result
The changes are transferred to the server and are automatically available at the clients.
When the calendar control is opened in other browser windows, it is automatically updated.
Your changes are available to other users.
Note
Note
Inconsistencies due to interrupted inheritance
If a shift changed by you has been overwritten in an inheriting calendar, the system notifies
you that inconsistencies will arise from the saving. Check and rectify the inconsistencies.
If an overwritten and an inherited shift overlap, an optical note is shown under the shift at
the inherited calendar.
Discarding
To discard changes, click "Discard" in the toolbar.

8.4.8 Editing inherited shifts

In the planning view, shifts from inherited calendars are shown hatched:
You can edit the shift and thereby overwrite the inherited data.
Requirement
• The calendar displayed in the control is inherited.
• The planning view contains an inherited shift.
Procedure
1. Right-click on the inherited shift.
2. In the shortcut menu, select "Shift edit".
3. Edit the shift, for example, by shortening it.
Result
The inherited shift is overwritten.
See also

8.4.9 Clear planning data
Introduction
You can clear the runtime data. The following deletion processes are possible:
• Clear entire planning data (with or without inherited calendar)
• Clear planning data (with or without inherited calendar) that is in a specific time period.
• Clear all (planning, templates, inheritance)
Note
Only runtime users with the "Full access" right are allowed to delete runtime data.
You can create a backup of the runtime data before you delete it. The backup is done by
exporting the runtime data to the client.
Note
Inherited calendars are not backed up. However, you can export (Page 92) the instances
before deleting them.
Procedure
1. Click "Clear" in the toolbar.
The "Runtime configuration" dialog opens.
2. Make your settings.

3. Click "OK".

8.5 Export and import

You can export planning data and templates of a calendar to a CSV file and import from a CSV
file.
This data exchange offers you the following options:
• Data migration between devices
• Bulk update of templates and planning data
• Offline update of data in third-party programs
• Data exchange between projects
• Creation of data backups
8.5.1 Export data
Requirement
Planning data or templates are available.
Procedure
1. Click "Export" in the toolbar of the Calendar control.
2. To export templates, follow the steps below:
– Select the "Template" check box.
– Select the check box of the template types you want to export.
3. To export planning data, follow the steps below:
– Select the "Planning" check box.
– Set a start date and an end date.
4. Enter the name of the export file.
5. Click "Export".
Result
The data is exported and saved as CSV file on the device. You can edit the file outside the
runtime environment with a third-party program.
Note
The following data is exported for inherited calendars:
• Data that overwrites the inherited information
• Data that has been newly added

8.5.2 Importing data

It is not possible to import to an inherited calendar.
Requirement
• A CSV file with planning data or templates is available. The file has the necessary format.
See section Structure of the CSV file (Page 94).
• Time intervals used in the file are available in the calendar.
• Tags linked to action elements used in the file are available in the calendar.
• To import planning data based on templates: The corresponding templates are already
available in the calendar or their template types are also selected for import in the import
dialog.
Procedure
1. Click "Import" in the toolbar of the calendar control.
2. To import templates, follow the steps below:
– Select the "Template" check box.
– Select the check box of the template types you want to import.
3. To import planning data, follow the steps below:
– Select the "Planning" check box.
4. Optional: To backup the existing planning data or templates before performing the import,
select the "Export" check box.
5. Select the import file.
6. Click "Import".
Result
• When the "Export" check box is selected, a CSV file with a complete backup of the
planning data or templates is created before the start of the import.
• The data is imported to the calendar.
Note
Restrictions
• If a complete import is not possible, the entire import is canceled.
• The same rules and restrictions apply to the imported data as for the data created in the
calendar in runtime. See section Structure of the CSV file (Page 94).
• Avoid major changes to the exported CSV file. If you use invalid values for action
elements, such as values outside of the range, mismatched data type values, etc., they are
not checked during import and this may cause undesired behavior in runtime.

8.5.3 Structure of the CSV file
Structure
You can edit the CSV file generated by the export. For a re-import of the file, observe the
editing restrictions listed below.
The file has a tree structure. It has the following setup:
Section for template data

If templates were exported into the file, the following nodes are created on the top tree level
for each exported template type:
• A node with the name of the template type
"DAY_TEMPLATE" , "SHIFT_TEMPLATE", "ACTION_TEMPLATE"
• A node with a legend of the values exported for this template type.
The legend also includes the data of the instances used by the templates.
• A node for each template of the template type.
If a template uses other template types, their data is imported into subnodes.
Example:
– A day template uses shift templates. One of these shift templates used an action
template.
– Extract from the CSV file:

Section for planning data

If planning data was exported into the file, the following nodes are created on the top tree
level:
• A node with the name "PLANNING_DATA"
• One node each with the start date and end date selected upon export
• A node with a legend of the values exported for the planning data
• For each day of the export period that contains planning data: A node with subnodes for
the planning data

Processing restrictions
• Offset of action elements: Maximum +/- 8 hours
• Shift duration: Between 2 and 24 hours
• Date information: In UTC
• Time information: In seconds
• The times of elements of the same type must not overlap, for example two time intervals
or two days.
If necessary, correct the start time or duration of the element.
Note
Editing the import file in MS Excel
Depending on your Excel settings, manually editing the import file can result in violations of
the date and time format. The import could fail.
When changing shift and day instances in the XML file manually, the "IsCustomized" flag must
be set. Otherwise, inconsistencies can occur after reimporting when you save or update
planning data that are based on a template.

Local reporting for calendar 9
9.1 Basics
9.1.1 Introduction
When the Calendar option package is installed, you can generate reports of shifts in Runtime
with WinCC Unified Reporting. You can then continue to edit the data in Excel or save the
report as PDF and distribute or archive it.

Local reporting for calendar
9.2 Procedure
9.1.2 Requirements
To create reports with Calendar, the Excel add-in must be installed. In addition, you must be
familiar with the basic operation of WinCC Unified Reporting. The documentation for this can
be found in the TIA Portal Help under "Creating production logs".
Basic information on report templates

Information on creating report templates is available in the TIA Portal help, in the "Creating
templates for production reports" section.
This information is also available in the Excel add-in. For this purpose, click the "?" icon in the
"WinCC Unified Reporting" tab.
Basic information on production reports in Runtime

Information on creating production logs in Runtime is available in the TIA Portal help in the
section "Working with production logs in Runtime".
9.2 Procedure
Requirement
• The Calendar option package is installed.
• Position the "Reports" control in a screen of a WinCC Unified device.
• The same requirements apply to the use of Reporting with the WinCC Unified basic
installation.
Run sequence
1. Define a report template for your jobs in the Excel add-in.
2. Define a trigger for the reports in the "Reports" control.

9.3 Defining a report template with hierarchical segment
Introduction
You can create a report template of the plant object on which a calendar is configured.
You define report templates with hierarchical view in the Excel add-in.
Requirement
• Microsoft Excel is open and the "WinCC Unified" tab is visible.
• The server on which an active runtime project with Calendar configuration is running is
selected in the "WinCC Unified" tab under "Connections".
• The list of options that is called from the server includes "Calendar".
Defining a hierarchical segment

1. In the "WinCC Unified" tab, click on "Segments".
The list of segments is loaded.
2. Select "New segment".
The selection menu opens.
3. Select "New hierarchical segment".
A new hierarchical segment is created.
4. Assign a name.
5. Specify the storage location, the table and the cell in which the hierarchical segment is to
start.
6. Specify a start time and an end time.
7. Confirm with "OK".
Adding a data source item

1. Click the created hierarchical segment.
2. Click the "+" icon.
The menu for selecting a data source item opens.
3. Select the "Calendar" option.
4. Select the "Plant view" context definition.

5. Under "Context definition", select the plant object for which the report is to be created.
Multiple selection is possible if you want to create a report on several plant objects.
6. Confirm your entries with "OK".

The template is generated.
7. Save the report template.
Adjusting columns
1. Select the "Edit" button of the data source item.
2. Select the desired columns.
3. Make your changes.
4. Confirm your entries with "OK".
The template is updated.

9.4 Creating a report job and downloading a report
Style of the report template

You can create the report template in different styles:
• Hierarchical display (default setting)
• Display in a row
Procedure
1. Click the "Edit" button next to the created hierarchical segment.
2. Under "Indent", select the "By level" option for hierarchical display or "By attribute" for display
in a row.
Testing the template

Test your template by clicking the button located next to the hierarchical segment.
Introduction
Before you create a report, create a report job in the "Reports" control and define a trigger. If
required, download the report as an XLSX file or PDF file.
Requirement
• A report template with a time series segment has been created in Excel.
• The "Reports" control is being used in Runtime.

Creating a report job and defining triggers

1. Select the "Job parameters" tab in the "Reports" control.
2. Under "Templates", select the "Add new" button.
A selection dialog opens.
3. Select the report template previously created in the Excel add-in.
4. Select "Open".
The report template is added.
5. Under "Trigger", select the "Add new" button.
6. Define a trigger.
7. Add a report job in the "Report jobs" area.
8. Define the template for the report job.
9. Define the trigger for the report job.
Note
Generating reports
The execution of a report job generates a report. Report jobs are executed automatically
when the trigger defined in their job parameters is initiated. You also have the option to
execute report jobs manually.
Downloading a report
1. A new entry has been created in the "Reports" control under "Reports".
2. Select the file format.
3. Click "Export".
The file is downloaded to the download directory of the browser.
4. To display the report, open the file.


WinCC Unified - Calendar - Manual

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

WinCC Unified - Calendar - Manual

Uploaded by

Copyright:

Available Formats

Calendar - Defining schedules for production

Migrating V16 project 1

Defining schedules during

Local reporting for calendar 9

Siemens AG Copyright © Siemens AG 2021.

1 Migrating V16 project ............................................................................................................................ 5

Calendar - Defining schedules for production

8.1.6 Overall workflow ............................................................................................................... 41

Calendar - Defining schedules for production

Calendar - Defining schedules for production

Changing the configured Runtime version of the HMI device

4. Confirm your change with "OK".

Updating calendar control

Calendar - Defining schedules for production

Calendar - Defining schedules for production

Calendar - Defining schedules for production

Requirements in the TIA Portal

Calendar - Defining schedules for production

2.3 Basics on scheduling in the WinCC Unified Calendar

Calendar and inheritance of calendars

Calendar - Defining schedules for production

Common Time Model and time categories

2.4 Changes in multi-user projects

Calendar - Defining schedules for production

Calendar - Defining schedules for production

Creating a root time category

Creating a user-defined category

Calendar - Defining schedules for production

Copying time category

3.2 Deleting time categories

Calendar - Defining schedules for production

3.3 Editing properties of a time category

Properties of the time category

Calendar - Defining schedules for production

3.4 Editing the tree structure of the time model

Deleting time categories

Moving time categories

Calendar - Defining schedules for production

Rearranging time categories

3.5 Exporting time categories

Calendar - Defining schedules for production

3.6 Importing time categories

Importing time categories

Calendar - Defining schedules for production

Creating a new calendar

Copying an existing calendar

Calendar - Defining schedules for production

4.2 Opening a calendar

4.3 Configuring the basic settings of the calendar

Calendar - Defining schedules for production

Overview of the general calendar settings

Name Description Default setting

Calendar - Defining schedules for production

4.4 Defining tag access of the calendar

4. Save your project.

Calendar - Defining schedules for production

4.5 Editing calendars

Editing a calendar used in Runtime

4.6 Deleting a calendar

Deleting a calendar used in Runtime

Calendar - Defining schedules for production

Calendar - Defining schedules for production

5.2 Configuring a calendar control