Appendix A - Requirements - Matrix for Scheduling Management Software Checklist (Req 377044).pdf

Page | 1 of 2

APPENDIX A – REQUIREMENTS - MATRIX FOR SCHEDULING MANAGEMENT

CHECKLIST- Req 377044

REQUIREMENT

NUMBER

DESCRIPTION Yes -

Proposed Software Meets or Exceeds Requirement

No – Proposed

Software does not meet

Requirement

1 Multiple calendars in a single job grouping (currently called job set) – each calendar controls specific jobs in the set.

2 Multiple calendars can be “active” at the same time in a specific job grouping – normal Wednesday, Final, Yearend, etc. Final and Yearend are “additional” calendars that control additional jobs when they are scheduled but the “normal” Wednesday is the same through them all.

3 Ability to run Perl Scripts to execute the various types of programs – SQR, PL- SQL, Cobol, App Engine, SQL (both Oracle and SQL Server versions), etc. (Note: This currently is controlled locally and is part of the Perl routines.)

4 Ability for holds to be added to a job or job grouping to allow processes to be held until released by an analyst.

5 Ability for holds to be added to a job or job grouping to allow processes to be held until released by an analyst.

6 Ability to produce a listing of the various jobs during set up and modifications.

7 Ability to send a daily report of what, by system, is in the queue for the next 24 hours – currently called “New Day”.

8 Ability to have “triggers” that will send emails to specific people based on the Job and its related trigger. (Note: Currently a combination of actions based on the arrival of a file along with actions that are coded for each specific situation.

The actions deal with the scheduling software console log while the actual email is sent using a local VB Script.)

9 Ability to print a report of the “triggers” set up for emails. (Note: Currently the report is created locally with a query of the scheduling software console messaging capabilities.)

10 Ability to send text messages to specific cell numbers. (Note: Currently a combination of actions based on the arrival of a console message along with actions that are coded for each specific situation. The actions deal with the scheduling software console log while the actual email is sent using a local VB S i )

11 Ability to cancel a job out of a grouping (after additional dependencies have been added) that will allow a specific job out of the group be “skipped” after it has “scanned” in for the day.

12 Ability to restart failed jobs in a specific step internal to a Perl script or to restart from the beginning of the script/step. (Note: This amounts to being able to change parameters being passed into the job after a failure. Controlling the steps is within the Perl routines written not the software.)

13 Ability to have a job grouping (set) start processing when a file is placed (dropped) in an identified file share/folder location

14 Ability to have a completed job grouping (set) purge out of the queue and come back in (reset) to process again when the “trigger” completes/is available.

(Note: Combination of software and local code within Event Management console log, which can process commands. We created commands within the actions portion of an identified Console message to perform these scheduling

Page | 2 of 2

REQUIREMENT

NUMBER

DESCRIPTION Yes - Proposed

Software Meets or Exceeds

No – Proposed

Software does not meet

15 Ability to run Perl scripts and, therefore, processes in command line mode.

16 Ability to have multiple jobs grouped into a single set to process with d d i

17 Ability to pass parameters to the scheduled jobs/steps.

18 Ability to send emails in case of failure or completion, etc.

19 Ability to pick up/drop off external files for processing – Perl does the work, but the system needs to be able to handle external interfaces.

20 Ability to read/decrypt an encrypted password file so the passwords aren’t hard coded in a clear text file/process.

21 Ability to process and track jobs on Windows and Red Hat Linux platforms.

22 Ability to store Job Groups/Job scheduling information in a single location while the actual scripts being executed are located on the application areas/servers

23 Ability to control the number of jobs that can run at one time independent of Job Groups (resource). I.E Single thread sets of jobs or only allow 5 jobs of a give resource to run concurrently.

24 A utility to be able to place messages in the console log from a batch job that can be reacted upon (actions) to Delete/stage for execution/Release groups of jobs or jobs for execution.

25 A utility or method to extract Job groups, jobs, calendars file triggers and console actions for backup or to be loaded on a different server for test or migration to new software versions on a future production server.

A utility to load extracted Job information, issue line mode commands from a console defined action, or from a batch job to process into the scheduling software product.

27 A routine to be able to place messages in the console log from a batch job that can be reacted upon (actions) to Delete/stage for execution/Release groups of jobs or jobs for on request. An example would be a Job Group or Job would be staged to process when a file is placed (dropped) in a predefined location. This could also be a method to schedule a predefined Job Group/Job set based upon

28 Ability (command) to stop jobs from starting when necessary. They would remain in a wait to start status until a command is issued to start processing jobs again

29 Ability to automatically schedule Job Groups for the current day based on date and time. Be able to request a Job Group (demand/request) for the current day.

30 Ability to forecast Job Groups/Jobs that will automatically be scheduled for future dates.

31 Screens to monitor a console log and manage Job Groups, Jobs, and other scheduling software features which could include calendars, resources, console actions and files that relate to job processing dependencies.

32 Ability to monitor/manage by multiple people.

Attesting to accuracy of Appendix A – Print & Signature of Official of Proposing Company Date