Plan Element Components

Plan element components allow entering information for plan elements defined under the "‘Hierarchy".  Note that you can have a number of plan element components, carrying a title of your choice and ordered in a way that is most relevant to your organisation.

You will be able to link a selected plan element entry to an existing element in interplan^® during the data entry process. This linking process is governed by a set of rules as explained in the following section.

Linking the element between Shuttle Plans and interplan^®

Element linking creates a link between a plan element in Shuttle Plans and an element in interplan^®. In order to create a relationship between the two, for a given plan in the Shuttle Plans module, only one element can be linked to the same element in interplan^®.

Please refer the example below:

However, different plans within Shuttle Plans may have elements that link to the same element in interplan^®.

Please refer the example below:

Types of Element Linking

Two types of linking can be done between elements in Shuttle Plans and interplan^®.

• Top level linking refers to the linking of any Shuttle Plans element (with the exception of the lowest level element) to any interplan^® element. This lowest level element depends on the configuration of your setup, since it is possible to edit the default Hierarchy of elements within any given plan. Please refer "Hierarchy" for more information about defining and editing elements and their Hierarchies.

• Bottom level linking refers to the linking of the lowest level element in Shuttle Plans to an interplan^® Action or Task. The lowest level element in Shuttle Plans that is being linked to an Action or Task in interplan^® (bottom level linking), must have the same Responsible Officer. In essence, this lowest level Shuttle Plans element and the interplan^® Action or Task is the same thing, expressed in different ways. This means that there is only one Responsible Officer, and the Comments, Status and % complete are always the same (e.g. if it is updated in Shuttle Plans, the changes will be reflected in interplan^®, and vice versa).

In practice, the Responsible Officer is likely to utilise interplan^® to update Actions/Tasks, which in turn will update all comments for the related plans.

For example if the Responsible Officer updated the Youth Plan Strategy 1 in the above example through Shuttle Plans, all Action/Task related information (e.g. the progress comments, status and % complete) would flow through to Infrastructure Plan Strategy 1 and interplan^® Action 1.1.1.1.

Copyright © 2014-2015 CAMMS Online Help. All rights reserved.

Last revised: September 23, 2018