Daily planning reports

Figure 1. Daily planning reports - General information

ABCD COMPANY                                                 PAGE 0001
 REPORTS FOR SUBSYS EIDA                                     06 MAY 08
                                                                 12:33

               P R I N T O U T   O F   D A I L Y   P L A N
               = = = = = = = = = = = = = = = = = = = = = =

                                    GENERAL INFORMATION

REQUESTED PLANNING PERIOD                : 08/05/06 09.06 - 08/05/06 24.00
PLAN COVERS                              : 08/05/06 09.06 - 08/05/13 24.00
TYPE OF PLANNING                         : PLAN NEXT PERIOD

LONG TERM PLAN USED                      : 08/05/04
OLD CURRENT PLAN USED                    : NO
NEW CURRENT PLAN CREATED                 : YES

WORKSTATION SUMMARY                      : YES
DAILY OPERATING PLAN                     : YES
WORKSTATION PLANS                        : YES
INPUT ARRIVAL LISTS                      : YES
NON-REPORTING WORKSTATION PLANS ONLY     : YES
CURRENT PERIOD RESULTS                   : NO
PREVIOUS PERIOD RESULTS                  : NO
MISSED FEEDBACK REPORT                   : YES
PLANNED RESOURCE UTILIZATION             : YES
ACTUAL RESOURCE UTILIZATION              : YES
CRITICAL PATH                            : NO

NUMBER OF PLANNED APPLICATIONS           :     3
NUMBER OF PLANNED OPERATIONS             :     6

NUMBER OF MESSAGES - ERROR               :     0
                   - WARNING             :     0
                   - INFORMATION         :     0

The following data appears on the general information page:

Data: Explanation
Requested planning period: Start and end times as specified in panel.
Plan covers: Start time is the time the latest backup of the current plan was taken; end time is the end of the tail-end period. If no current plan exists, start time is the earliest input arrival time.
Type of planning: Name of daily planning function used to produce this set of plans.
Long-term plan used: Time the long-term plan was last updated; appears only if the long-term plan was used as input to this daily planning run.
Old current plan used: Time the last current plan backup was taken; appears only if the current plan was used in this planning run.
New current plan created: YES if new current plan created; NO if no plan was created.
Workstation summary: Report produced, YES or NO.
Daily operating plan: Report produced, YES or NO.
Workstation plans: Report produced, YES or NO.
Input arrival lists: Report produced, YES or NO.
Nonreporting workstation plans only: Report produced, YES or NO.
Current period results: Start and end time for period covered; NO if no report produced.
Previous period results: Start and end time for period covered; NO if no report produced.
Missed feedback report: Report produced, YES or NO.
Planned resource utilization: Report produced, YES or NO.
Actual resource utilization: Report produced, YES or NO.
Critical path: Report produced, YES or NO.
Number of planned applications: Number of occurrences in daily plan.
Number of planned operations: Number of operations in daily plan.
Number of messages: Number of error, warning, and information messages.

Figure 2. Daily planning reports - Daily operating plan

                 DAILY OPERATING PLAN  (080530   08.44 - 080531   08.44)
                 ========================================================
------------------------------------------------------------------------------------------
APPLICATION ID         |                      |                 |                       |    |    |
 APPLICATION OWNER     |INP ARRIVAL   DEFINED |APPLICATION TEXT |  PREDECESSORS    SPEC |EXT |
 OP ID    JOBNAME  P  S|   START  DUR DEADLINE| OPERATION  TEXT |APPL   ID OP ID INP ARR|RES |MON |COND
 -------- -------- - --|-- ---------- --------|-----------------|--------- ------ ------|----|----
                       |                      |                 |                       |    |    |    
PAYBACKP           5  W|   12.00      09 06.00|Backup payroll DB|                       |    |    |    
 SAMPLE                |                       |                |                       |    |    |    
 CPU1_015 PAYBACKP     |   12.09 00.05        |Daily payr backup|PAYDAILY  CPU1_020     |*   |    |N   
 WTO1_030 PAYDAILY     |   12.14 00.0109 06.00|PAYX OPEN DATASET|          CPU1_015     |    |    |N   
 FTW1_001 MASSI1       |29 15.00 00.0229 17.00|                 |                       |    |Y   |N   
 ---------------------------------------------------------------------------------------------------
 PAYBACKP          5  W|   12.00      09 06.00|Backup payroll db|                       |    |    |    
   SAMPLE              |                      |                 |                       |    |    |    
   CPU1_015 PAYBACKP   |   12.09 00.05        | Daily payr bckup|PAYDAILY CPU1_020 12.00|    |    |N   
   WTO1_030 PAYBACKP   |   12.14 00.0109 06.00| PAYX OPEN DATAS |         CPU1_015      |    |    |N   
----------------------------------------------------------------------------------------------------
                       |                      |                 |                       |    |    |    
  PAYDAILY         5  W|   12.00         16.00| Daily payr jobs |                       |    |    |    
   SAMPLE              |                      |                 |                       |    |    |    
   WTO1_005 PAYDAILY   |   12.00 00.01        | PAYX CLOSE DS   |                       |*   |    |N   
   SETP_010 PAYDAILY   |   12.01 00.03        | Job setup pay   |           WTO1_005    |*   |    |N   
   CPU1_020 PAYDAILY   |   12.04 00.05   16.00| Runs pay04,pay06|           SETP_010    |*   |    |N   
----------------------------------------------------------------------------------------------
                                  >>>>>>>  END OF DAILY OPERATING PLAN REPORT <<<<<<<

The daily operating plan shows all work to be done during the period covered by the plan. It is a printed copy of the current plan. All applications are listed in alphanumeric order. Where there are several occurrences of the same application, these are listed in order of their input arrival times.

The following data appears in the daily operating plan:

Data: Explanation
Application ID: Application name
Application owner: Owner ID of the application
Operation ID: Operation number and workstation name
P: Application priority
S: Application status
Input arrival: Application input time
Start: Operation planned start time; for status C, actual start time
Dur: Estimated duration of the operation; blank if operation is complete
Defined deadline: Application or operation deadline
Application text: Application descriptive text
Operation text: Operation text
Predecessors: Internal and external predecessors
Application ID Op ID: Predecessor application ID: blank if internal predecessor; operation ID: blank if the predecessor occurrence starts after the period covered by this plan
Special resources: * indicates that this operation specifies special resources
External monitor: Specifies if this operation is to be monitored by an external product, Y or N
Conditional dependency: Specifies if there is any conditional dependency defined for this operation, Y or N

Figure 3. Daily planning reports - Plan for workstation

ABCD COMPANY                                                     PAGE 0003
 REPORTS FOR SUBSYS EIDA                                         06 MAY 03
                                                                     12:33

                         PLAN FOR WORKSTATION CPU1  (03/05/06 09.06 - 03/05/06 24.00)
                         ============================================================
-------------------------------------------------------------------------------------
APPLICATION ID       |    |RESOURCES| PLANNED  PLANNED  LATEST  |OPERATION TEXT  | PRED APPL ID
 OP¶ JOBNAME  FORM  C|P  S| PS R1 R2| START      END     OUT    |                |OP ID JOBNAME  INP
 --- -------- ----- -|- --| -- -- --| -------- -------- --------|----------------|----- -------- ---
---------------------------------------------------------------------------------------------
             >>> WORKSTATION OPEN   03/05/06 00.00 - 24.00 WITH 99 PARALLEL SERVER(S) <<<
---------------------------------------------------------------------------------------------
CP                   |    |         |                           |                |
 050 XRAYNERC        |7  A|  1  0  0|    12.00    15.00    16.00|                |
PAYDAILY             |    |         |                           |                |
 020 PAYDAILY        |5  W|  1  0  0|    12.04    12.09    16.00|Runs pay04,pay06|SETP_010 PAYDAILY
PAYBACKP             |    |         |                           |                |PAYDAILY
 015 PAYBACKP        |5  W|  1  0  0|    12.09    12.14 09 05.59|Daily payr bkp  |CPU1_020 PAYDAILY
------------------------------------------------------------------------------------------
             >>> WORKSTATION OPEN   03/05/07 00.00 - 24.00 WITH 99 PARALLEL SERVER(S) <<< 
------------------------------------------------------------------------------------------
⋮

          INPUT ARRIVAL LIST FOR WORKSTATION CPU1  (03/05/06 09.06 - 03/05/06 24.00)
          ==========================================================================
-----------------------------------------------------------------------------------------
APPLICATION ID         | INPUT   PLANNED   REM  |OPERATION TEXT          |OWNER ID
 OP¶ JOBNAME  FORM  C P|ARRIVAL   START    DUR  |                        |
 --- -------- ----- - -|-------- -------- ----- |------------------------|---------------
CP                     |                        |                        |
 050 XRAYNERC         7|   12.00    12.00 03.00 |                        |SAMPLE3

The report in Daily planning reports - Plan for workstation lists the work to be done at the workstation in order of planned operation start times. You can request this report either for all workstations or only for nonreporting workstations.

On the PLAN FOR WORKSTATION report, HCL Workload Automation for Z leaves the input arrival day for the predecessor application blank if it is the same day as the start of the planning interval (shown in the report title).

On the INPUT ARRIVAL LIST report, HCL Workload Automation for Z leaves the input arrival day blank if it is the same day as the start of the planning interval (shown in the report title).

Figure 4. Daily planning reports - Workstation usage (parallel operations)

ABCD COMPANY                                      PAGE 0006
 REPORTS FOR SUBSYS EIDA                                  06 MAY 19                                                              12:33

       PLANNED UTILIZATION FOR WORKSTATION CPU1  ( 03/05/19 09.06 - 03/05/19 24.00)
       ============================================================================
  * PARALLEL OPERATIONS PLANNED
  _ PARALLEL SERVERS AVAILABLE
    175 |
        |
        |
        |
        |
    150 |
        |
        |
        |
        |
    125 |
        |
        |
        |
        |___________________________________________________________________________________________
    100 |
        |
        |
        |
        |
     75 |
        |
        |
        |
        |
     50 |
        |
        |
        |
        |
     25 |
        |
        |
        |
        |                                            ************
         ----------------------------------------------------------------------------------->  TIME
         01.00 | 03.00 | 05.00 | 07.00 | 09.00 | 11.00 | 13.00 | 15.00 | 17.00 | 19.00| 21.00
  DATE  03/05/19                      PLANNING REQUESTED : YES
                         >>>>>>>  END OF CPU1 WORKSTATION REPORT  <<<<<<<

Daily planning produces workstation usage histograms, which show how many operations are processed by the workstation.

The level of resource available during the interval; that is, the number of parallel servers as shown by the horizontal line. The histogram shows the number of operations planned concurrently during each 15-minute interval. A histogram is produced for each 24-hour interval included in the daily planning period.

Figure 5. Daily planning reports - Workstation usage (resource 1)

ABC COMPANY                       PAGE 0195
DATA PROCESSING DEPARTMENT                              17 APR 03
OPC/ESA                                                     10:12

                     PLANNED UTILIZATION FOR WORKSTATION CPU1  (                - 03/04/16 24.00)
                     ============================================================================
  * UTILIZATION OF RESOURCE 1  ( TA )
  _ LIMIT FOR RESOURCE
     35 |
        |
        |
        |
        |
     30 |
        |
        |
        |____________________________________________________________________________
        |
     25 |
        |
        |
        |
        |
     20 |
        |
        |
        |
        |
     15 |
        |
        |
        |                 *
        |                 *                        *
     10 |                 *                        *
        |                 *                        *
        |                 *               *        *
        |                 **              **       *
        |                 **         *    **       ***
      5 |                 **         *    **       ***    *
        |                 ***       **    **     * ***    *
        |                 ****      ****  ***    *****  * *
        |                *******  * **** ****   ******* *
        |                **********************************
         ---------------------------------------------------------------------------TIME
         06.00 | 08.00 | 10.00 | 12.00 | 14.00 | 16.00 | 18.00 | 20.00 | 22.00 | 24.00| 02.00
  DATE  03/04/17                      PLANNING REQUESTED : YES

If R1 and R2 resources are specified to be planned for on the workstation; histograms are produced showing usage of these resources. These have a similar layout to the workstation usage histograms described above. The number of operations using the special resource is shown for every 15-minute interval.

Figure 6. Daily planning reports - Planned resource usage

ABCD COMPANY                             PAGE 0034
 REPORTS FOR SUBSYS EIDA                             06 AUG 18                                                         06:03
                  PLANNED RESOURCE UTILIZATION  (03/08/18 08.00 - 03/08/19 08.00)
                  ===============================================================
RESOURCE NAME    : PAYROLL.DATABASE               DESCRIPTION: Serializes access to Paymore database
DYNAMICALLY ADDED: NO
INTERVAL START | INTERVAL   END |           |             |     PLANNED |  ALLOCATION FAILURES BY   
| NUMBER OF
DATE      TIME | DATE      TIME | AVAILABLE |    QUANTITY | UTILIZATION |     CONNECT |    QUANTITY 
| CONTENTIONS
====================================================================================================
03/08/18  8.00 | 03/08/18 10.00 |     YES   |           1 |           1 |           1 |           0 
|           2
03/08/18 10.00 | 03/08/18 12.30 |     YES   |           1 |           1 |           0 |           0 
|           0
03/08/18 12.30 | 03/08/18 20.00 |     YES   |           1 |           1 |           0 |           0 
|           1
03/08/18 20.00 | 03/08/19 08.00 |     YES   |           1 |           1 |           0 |           0 
|           0

You see this data on the planned resource usage report:

Data: Explanation
Dynamically added: If this is YES, the resource was dynamically added during daily planning (it is not present in the database and was added because an operation needs it, and the DYNAMICADD keyword of the BATCHOPT statement is set to YES).
Available: This is the planned availability, taken from the resource database interval values or the default availability. It does not show the overriding (global) availability, because daily planning does not use this for planning purposes.
Quantity: This is the planned quantity, taken from the resource database interval values or the default quantity. It does not show the overriding (global) quantity, because daily planning does not use this for planning purposes.
Planned utilization: This is the maximum number of the resource that is planned to be in use in the interval.
Allocation connect failures: This is the number of times that the planning program could not allocate this resource to an operation because the required workstation was not connected to the resource.
Allocation quantity failures: This is the number of times that the planning program could not allocate this resource to an operation because there was not enough quantity. It does not include cases where the allocation was delayed (because of contention) but was successful later in the interval.
Contentions: This is the number of times that the planning program could not allocate this resource to an operation, so that the operation missed its latest start time. This is counted only once for each operation, in the interval containing the latest start time of the operation.