Environmental & Risk Management / Compliance Management / Compliance Program Manager

Generating Scheduled Events for Requirements

When you enter information for a requirement, when you save the information, you can, optionally, generate events for the requirement. You also might periodically need to regenerate events. See About Generating Events.

To generate or regenerate scheduled events for a requirement

  1. From the Process Navigator, select one of the following tasks:
    TaskSteps
    Manage Compliance Requirements
    1. Select the task.
    2. Use the Filter console to locate the requirement.
    3. Click Select in the row for the requirement.

      The Define Requirement form appears.

    Manage Compliance Drill-Down
    1. Select the task.
    2. Use the Filter console to restrict the drill-down list to show the requirement you are looking for.
    3. Expand the drill-down list to locate and select the requirement.

      The Define Requirement form appears.

  2. To generate events for this requirement, in the Save and Generate Events pane of the Define Requirement form, enter the following information:

    Event Duration (Days)

    The number of days over which this event occurs. The application uses this field to generate the Date Scheduled Start for each event. See How Your Entries Determine Dates for Generated Events.

    Event Schedule Buffer (Days)

    The number of days before required completion to set the Date Scheduled End. See How Your Entries Determine Dates for Generated Events.

    Date Initial Scheduling

    The application starts scheduling events on or after this date, according to the recurrence pattern you select. For new requirement records, by default, this field is set to the current date. You can enter a different date if needed, but the date must be on or after the Date Requirement Start, if one is entered. If you clear the field, then the Date Requirement Start is automatically copied to the field when you Save the requirement or Save and Generate Events.

    Example: For a monitoring program that consists of collecting samples each month for five years, from 2011 to 2016, you would enter the date of the first sample collection, such as 1/12/11.

    Generate event occurrences until

    You can enter this date as an end point for event generation. For example, use this date when the requirement is ongoing and you have not entered a Date Requirement End. You can change this date each time you generate events to control the time frame for which events are generated.

    When you regenerate events, this field shows the date entered the last time events were generated.

    See Controlling the Number of Events.

    Note: The application does not generate events beyond five years for a daily, weekly, or monthly schedule, or beyond ten years for a yearly schedule. Use the Generate event occurrences until field to generate a smaller number of occurrences than the application limit would produce.

    Create Scheduled Events for Each location

    Select Yes to have the application generate a separate event for each location associated with the requirement.

    Select No to have the application generate events according to the recurring schedule you set, without generating separate events for each location.

    Replace Future Non-Recurring Events (Includes Do Not Reschedule Event)

    If you select this check box, all future events with the Status of Scheduled, even those that have the Do Not Reschedule field set to Yes, are removed and replaced with the newly generated events. This check box enables you to override the Do Not Reschedule setting for an event.

    If you do not select this check box, events that have the Do Not Reschedule flag set to Yes, are not removed when you generate events.

    See Determining if an Event Is Removed When Regenerating Events.

    Event TitleThe title that helps to identify the event. By default, the first time you generate events, this is set to the Requirement Code. After that it is set to the Event Title entered the last time you generated events for this requirement. You can change the Event Title as needed to help identify this set of generated events. For example, if you generate events annually, you could add the year to the Event Title.
    Activate Notifications?

    Set to Yes to begin automatic notifications for this requirement.

    Set to No to turn automatic notifications off for this requirement.

    This setting determines whether or not email notifications associated with the event's compliance program or requirement will be added for each generated event.

  3. Define the recurrence pattern for the event. The information you enter is used to determine the Date Completion Required for the event:

    Select one of the following option buttons:

    None This is selected by default, but no events are generated if you keep this selection.

    Once Occurs once on the Date Initial Scheduling entered when generating the event.

    Daily Select this option when events occur more frequently than weekly. You also enter the number of days between events. For example, keep the selection to the default of 1 to have the event occur every day. Or, enter 2 to have the event occur every other day. Daily events are scheduled a maximum of five years into the future, until the 'Generate event occurrences until' date, or the End After XX Occurrences, whichever comes sooner.

    Weekly Select this option for events that occur more frequently than monthly. Select the number of weeks between events, and the day of the week you want the event to occur on. Weekly events are scheduled a maximum of five years into the future, until the 'Generate event occurrences until' date, or the End After XX Occurrences, whichever comes sooner.

    Monthly Select the number of months between events. You can enter the day of the month for the event. For example, the event could start on the first of each month. Or, you can select a specific day of the week and then specify that the event should occur on the 1st, 2nd, 3rd, 4th, or last occurrence of that day for the month. For example, you can set an event to occur on the second Monday of each month, or the second Monday every other month. Monthly events are scheduled five years into the future, until the 'Generate event occurrences until' date, or the End After XX Occurrences, whichever comes sooner.

    Yearly. Select the number of years in between events and then select the date for the event. Yearly events are scheduled a maximum of ten years into the future, or until the 'Generate event occurrences until' date, or the End After XX Occurrences, whichever comes sooner.

    End After XX Occurrences: For any of these schedules, except Once, you can specify the maximum number of occurrences for the event by entering the number in the End After XX Occurrences field. This field is used only if that number of occurrences does not take scheduling beyond the Date Requirement End Date, or past the maximum number of years for the schedule type (five years for daily, weekly and monthly schedules, and ten years for yearly schedules.) The application schedules until the 'Generate occurrences until date' or the End After XX Occurrences, whichever comes sooner.

  4. To generate events for the requirement, click Save and Generate Events.

    You are asked to confirm that you want to save the information you entered and generate events.

  5. Click OK to continue.

    A message appears giving the number of events that were generated.

    You can view the events from the Events tab. Each event has a Date Completion Required, Date Scheduled Start, and Date Scheduled End calculated using the information you entered. See How Your Entries Determine Dates for Generated Events.