| Task Name | The name of the item. Click to open the default page for that item. You can expand and collapse the structure to view the regulatory calendar phases in the template, and the regulatory milestones within the calendar phases. |
Type | The type of item. The calendar can include these item types:- Regulatory Calendar Template
- Regulatory Calendar
- Regulatory Milestone
- Interactive Review
|
Regulatory Calendar | Scope | Global or Local for rows that define a regulatory calendar. Blank for all other rows. You cannot define more than one regulatory calendar with the same combination of Scope and Esc. Level. In the schedule for the template, you add additional global or local calendars as children of the template (the first row of the schedule) regardless of when they would occur during the submission process. For a submission project that uses this regulatory calendar template, you would add the local calendar to a regulatory milestone with Yes for the Connection value. You would add an escalated global calendar to a regulatory milestone with Yes for the Pivot value. |
Esc. Level | The escalation level. For the global scope, all escalation values must start from 0, and increment by 1 without any gaps. The escalation for a global calendar might not have an equivalent escalation for the local calendar. |
Regulatory Milestone | Pivot | Yes or No to indicate if this milestone allows an escalation calendar to be added to it. If the schedule includes global calendars for any number of escalations, you need to include regulatory milestones for each escalation, not including the 0 escalation. For example, if your schedule includes these regulatory calendars: - Scope=Global and Esc. Level=0
- Scope=Global and Esc. Level=1
- Scope=Global and Esc. Level=2
You need at least two regulatory milestones with Yes for the Pivot value. These milestones define the places in the schedule where the escalated calendars can be attached in the schedule for a submission project. |
Connection | Yes or No to indicate if this milestone allows a local calendar to be connected to it. If the schedule includes local calendars for any number of escalations, you need to include regulatory milestones for each escalation. For example, if your schedule includes these regulatory calendars: - Scope=Local and Esc. Level=0
- Scope=Local and Esc. Level=1
- Scope=Local and Esc. Level=2
You need at least three regulatory milestones with Yes for the Connection value. These milestones define the places in the schedule where local calendars can be attached in the schedule for a submission project. |
Purpose | The regulatory purpose for this milestone. See Regulatory Milestones for information about the options. |
|  | For the Interactive Review phase only. If shows for the row, then the submission timer is in clock stop. |
Id | The schedule sequence for this regulatory calendar phase, interactive review phase, or regulatory milestone. |
Dependency | The dependency for this milestone. See Project Management
User's Guide: About Task Dependencies for information. |
Estimated | Duration | Duration in days or hours for the item on this row |
| WBS | The phase or milestone's order in the hierarchy. Integers represent the top level. Second level items have one decimal, third level tasks have two decimals, and so on. |
Description | Descriptive information about the activity. |