Creating a Schedule Library

The schedule facilities used in ADP are based on the standard Draft automatic tagging functionality, and you should be familiar with this before reading any further.

The ADP PGA defaults file contains an entry to allow the administrator to define what tag rule set element will be available to the user during use of the ADP system. The supplied system refers to a TRLB called

DRA/PRJ/ADP/SCHE/PGA

that contains the TRSTs that the user accesses on the schedule creation form. Each TRST is represented by a toggle and modify button gadget group on the user’s form.

In order to create your own TRLB for schedules and any number of TRSTs below this, each of which represents an available schedule for use by the user. The TRSTs and their constituent TAGRs have to be built with the following naming conventions:

TAGR /LOCAL can reference any STYM or TXTM as required. This tag rule is responsible for generating the tags local to the design graphics.

TAGR /ENTRY has to reference a special SYTM which in turn has references to other SYTMs and is responsible for generating the tabular format entries generated as part of the schedule. In order to generate a matching set of local and table tags it is important that both TAGRs have the same criteria.

The SYTM referenced by the TAGR /ENTRY has an associated set of SYTMs as shown below, where prefix can be any prefix name for the SYTMs, but the same prefix is used to identify all three SYTMs required to construct the schedules table.

Example

The following example is based on the Project Libraries supplied in the Sample Project, under DRA/PRJ/ADP/SCHED:

Each of the functions of the three schedule table SYTMs is explained below:

The SYTM prefix/OFFSET contains a single TEXP whose BTEX determines how each table entry is positioned with respect to the previous. The BTEX simple states the OFFSET for each table entry in the standard X and Y format. For example:

This means that each table entry is offset by -10 in the Y direction, therefore producing a vertical table that grows down the sheet from the origin position.

The origin and extent positions for any schedules created are initially taken from a special note created in the BACK by the administrator. See the next section for further information of how to implement this.