Main Menu

SIS 2000+ Special Programs Editor

Sec. 5, Define a 'Timeline'

This section only applies to special programs that have been designated as 'Special Education" (in the 'General' tab).

Special Education programs are implemented through a sequence of events called "Special Education Process" or "due process." This sequence is defined in the 'Timeline' screen of the Special Programs Editor. The sequence can rearranged, events can be designated as dependent on other events, and a variety of other requirements and attributes can be set in this procedure. Though the events in the due process are defined here, the fulfillment of this due process is tracked on a per recipient basis in a separate SIS 2000+ program named Special Education History.

5.1 View the Timeline list
The Special Education field in the 'General' screen must be checked in order to view the 'Timeline' screen of the current program being defined. Click on the 'Timeline' tab to bring the screen to the front. The default view is a list of events in the read-only mode; signified by the dark blue column headers (Fig. 15).

Fig. 15 - Timeline list

• Seq.(uence) -

A number designating the sequence of the event in the Special Education Procedure.
• Description -

The name of the event.
• Type of Date -

Completed events may be dated in a variety of ways when they appear in the Special Education History 'Compliance Timeline'. The type of date is defined here first, such as 'Effective Date', 'Expiration Date', 'Received' date, and so on.
• Req.(uired) -

A "Y" (Yes) will be displayed in this field if the event is required by the school district. A "N" (No) indicates the event is optional.
• Doc.(ument) -

A "Y" (Yes) will be displayed in this field if there is a document associated with this event. A "N" (No) indicates that there is no associated document.
• Days -

The number of days allowed to complete the event in the due process.
• from Seq.(uence) -

A number designating which event must be completed earlier in the sequence (the parent event) before this event (the child event) is implemented. Once set, this link will be maintained even if the overall order of sequence is changed.

5.2.1 Activate the first level edit mode



Click on the Edit command button at the bottom of the screen to go into the first level edit mode; indicated when the column headers and the small Add, Edit, and Delete buttons turn bright blue (Fig. 16).


Fig. 16 - First-level edit mode

5.2.2 Open new event attributes form



Click on the blue-colored Add command button below the events list to open a blank form for a new event (Fig. 17)


Fig. 17 - blank form

5.2.3 Define event attributes
Use the Tab key to move from field to field. Enter data as follows:


• Sequence num.(ber) -

A read-only field displaying a number designating the sequence of this event in the due process. This number is automatically generated at the time this event is first added. This number can be changed only by following the "Change the sequence of events" procedure (See Step 5.4).
• Description -

Enter a descriptive name for the event.
• Depends on Date -

This field will refer to another event (the parent) that has already been defined in the sequence. Make a selection of previously defined events from the drop-down list. If there are no previous events, the only selection will be '<Unset>'. The link set up in this action will be represented by a sequence number in the from Seq. field in the Timeline list view. For example, if the current event being defined is named "Event C" and "Event A" is selected in this field, then a parent/child relationship will be set up between the two events. Consequently, the from Seq. value will be equivalent to whatever the Seq.(uence) number is for "Event A", the parent. If the sequence number for "Event A" changes, the from Seq. value for "Event C" will automatically change accordingly to maintain the link. If Depends on Date field is left unset then a blank will appear in the from Seq. field in the list view.
• Num. of Days to add -

Enter the number of days allowed to complete the event in the due process. This value will be displayed in the Days field in the Timeline list. The Special Education History application will use this value to calculate actual calendar Due dates for each event in the the fulfillment of the program once the sequence of events starts.
• Count the Weekend -

Check this box to count weekends in the Number of days to add field.
• Count non School Days -

Check this box to count non-school days (such as holidays) in the Number of days to add field.
• Special Ed. Recalculate -

This field determines Timeline functions in the Special Education History application. Special Ed. Recalc determines how the due date of an entry is calculated from its parent event. If Special Ed. Recalc is not checked, then the Due date is calculated as so many days from the parent's Due date. If Special Ed. Recalc is checked on, then the Due date is calculated as so many days from the parent event's actual date.
• Auto recalculate -

This field determines Timeline functions in the Special Education History application. Auto Recalculate when set causes previously set Due dates to be recalculated when a Due date of an ancestor record is changed. When Auto Recalculate is not set a non-empty due date will never be changed by the program but can be changed manually. For example, if the due date of Event #2 is changed then the Due date of Event #3 will also be changed if either #3 has no Due date or has Auto Recalculate turned on.
• Is required -

Check this field if the completion of this event is required in by the school district before completing any subsequent child events. If it is left unchecked, the event is optional.
• Is documented -

Check this field if there is a document associated with this event.
• Type of Date -

Completed events may be dated in a variety of ways when they appear in SIS 2000+'s Special Education module. The type of date is defined here first, such as 'Effective Date', 'Expiration Date', 'Received date', and so on.
• Document Type -

Select the type of document associated with this event.
• Receiving entity type -

Select the type of person or institution that must receive the associated document.
• Originating doc -

Select the printed format that is required for the associated document.
• Method delivery -

Select the method of delivery required for the associated document.
• Comments -

A memo field for anecdotal comments.


Fig. 18 - sample data


5.2.4 Save data
Click on the Save Timeline command button to save the new event, or Undo Changes to clear all changes since the last save, or Previous Page to exit the form and return to the Timeline list if no changes were made.



5.2.5 View the new event in the Timeline
After saving an event's attributes, the view will automatically revert to the Timeline list, still in the first-level edit mode (Fig. 10). The new event will be visible as an entry in the list in its automatically assigned sequence.


Fig. 19

5.2.6 To add another event, repeat Steps 5.2.2 - 5.2.4

5.2.7 To exit the edit mode, click on the Done command button.

5.3.1 Activate the first level edit mode by clicking on the Edit command button at the bottom of the screen.

5.3.2 Select the event in the Timeline list until it is highlighted in dark gray.

5.3.3 Activate the second-level edit mode by clicking on the blue-colored Edit command button.

This action will open the event's attribute form (Fig. 18).

5.3.4 Use the Tab key to move from field to field. Modify data (See Step 5.2.3).

5.3.5 Save data by clicking on the Save Timeline command button, or click on Undo Changes to cancel all changes since the last save. If no changes were made, click on the Previous Page command to exit the form and return to the Timeline list.



5.3.6 After saving an event's attributes, the view will automatically revert to the Timeline list in the first-level edit mode (Fig. 19).

5.3.7 To exit the first level edit mode click on the Done command button.

5.4.1 In the Timeline information screen activate the first level edit mode by clicking on the Edit command button.

5.4.2 Select an event to move.
In the first level edit mode, each event in the timeline list will have a small mover barin the left hand Seq.(uence) column followed by a sequence number.


Fig. 20

Select an event to move by clicking on it until the line is highlighted in dark gray and the mover bar becomes activated with small, black up/down arrows (Fig. 20).

5.4.3 Drag and drop the activated mover bar up or down to change the entry's sequence in the list. In the example below, "Event C" has been moved from third in the list (a sequence position of 003) to first in the list (the position of 001) (Fig. 21).


Fig. 21

5.4.4 Exit first level edit mode by clicking on the Undo command button. The new sequence will be saved automatically.

5.5.1 Find the special program to edit using the List command button (See Sec. 1)

5.5.2 Click on the "Timeline" information screen

5.5.3 Activate the first level edit mode by clicking on the Edit command button

5.5.4 Select an event to delete by clicking on it until the line is highlighted in dark gray.

5.5.5 Click on the blue-colored Delete command button.

5.5.6 In the dialog box that appears, answer "Yes" to confirm or "No" to abort.


Fig. 22

5.5.7 Exit first level edit mode by clicking on the Undo command button.