Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Current »

Overview

A Runbook includes the scheduled, automated, and manual processes that facilitate daily processing of students in the Regent system. The level of automation versus manual processing varies by client, and processes include task assignment, communications, load ISIR files, load COD files, batch packaging, and disbursement sequence, among other processes.  

During a Regent implementation, a Runbook template is used by Regent’s Delivery Services and clients to shape a client-specific Runbook. Regent’s current Runbook template can be found here: (Any updates to this template will be highlighted in release documentation.) 

Specific details are documented in a client’s Runbook document. A portion of a sample Runbook is shown below:  

Order and Timing of Runbook Processes

The order and timing of Runbook processes are critical. As clients maintain and update their Regent Runbook, please keep the following in mind:

  •  In order to ensure current data is used for clearing disbursements, schedule large data imports (such as a full SBL or an NSLDS FAH file) after a day’s EST processes are complete and before Batch Packaging (BP) is run (focused or standard).

  • As part of Regent’s 6.2 Release, clients should plan to make any configuration changes after scheduled EST processes run and before BP runs, so the configuration changes that require repackaging will be included in the BP process.

  • The above two items will minimize the number of EST-0059 errors during the EST process due to changed data that requires repackaging. 

  • EST processes should closely follow BP in the runbook sequence.

  • Clients are encouraged not to run a full BP during the day while Users are processing in the Regent system and system usage is high.

  • Beginning with Regent’s 6.2 Release, students with SBL data changes imported during the day will need to be repackaged. If those students are not repackaged, they will not disburse and will receive an EST-0059 error. To resolve this error, clients can:

    • MAP the students separately, or

    • Recognize students will not disburse until they are repackaged.

Recommended Disbursement Sequence

Regent recommends the following disbursement sequence:

  1. Import FAH and other misc. files

  2. Complete any necessary configuration changes

  3. Import SBL

  4. Run BP

  5. Export COD for originations

  6. Import COD Originations response file

  7. Run EST for DRI=TRUE

  8. Export COD Disbursement Records (DRI=TRUE)

  9. Import COD Response file (DRI=TRUE)

  10. Run EST for AR

 

  • No labels