Tenders Are Invited For Software-Related Services – It Service For Workload Automation

Software-Related Services – It Service For Workload Automation. Continuation Of The Description According To 2.1: In The Event Of A Disaster, It Can Be Assumed That The License Of The Production System Will Not Be Used. In Addition, The Contractor Provides The Client With The Software Updates/Versions (E.G. Sw Extensions, Bug Fixes) Required For Use And Operation, Including The Technical Documentation For Both Locations, Without Request, In A Timely Manner So That The Client Can Keep The Wla Software Solution Technically Up To Date. Performance Part C - Implementation Of An Interface Between Iws And Wla Software Solution In Order Not To Endanger Ongoing Data Center Operations At The Clients Location, Parallel Operation Of Both Software Products Is Required Until All Iws Tasks Have Been Completely Transferred To The Wla Software Solution To Be Procured. The Iws And The Wla Software Solution Must Be Operated Together By The Client During The Contract Term. To Do This, It Is Necessary That Both Software Products Interact With Each Other Via An Interface And Exchange Data (E.G. Events) In Real Time. The Wla Software Solution Is The Leading System (Meta Instance) And Determines The Job Flow. For Smooth Parallel Operation And The Migration From The Existing Iws Software To The Wla Software Solution, A Mutually Controlling Technical Interface Between Both Software Solutions Is Required, Which Ensures Smooth Productive Operation. Mutual Control Requires Functions In Both Directions: The Wla Software Solution Controls Iws The Wla Software Solution Must Start Iws Jobs, Pass Dependencies, Receive Status Information And Detect Possible Errors. Iws Controls The Wla Software Solution As Long As Jobs Are Still Running In The Iws, The Iws Must Start The Subsequent Processes In The Wla Software Solution Or Wait For Their Completion. Service Part D - Migration Iws To The Wla Software Solution - Cologne Location All Services And Tasks Of The Existing Scheduler (Iws) Across All Instances Must Be Taken Over By The New Wla Software Solution As Part Of The Migration. The Client Provides The Required Servers. The Contractor Has To Migrate Around 6,000 Iws Jobs To The Wla Software Solution According To Business And Technical Rules. The Iws Jobs Are Currently Carried Out An Average Of 110,000 Times Per Month. The Contractor Must Implement The Migration Of The Iws Jobs To The Wla Software Solution In Packages (Migration Package By Migration Package). The Contractor Ensures The Complete Implementation And Provides All Necessary Support Services Until The Wla Solution Is Fully Operational. Job Networks That In The Future Will Be Outside The Z/Os Environment Must Be Completely Operated By The Wla Software Solution. Job Streams That Are Still Required In The Z/Os Environment Must Continue To Be Executed, Controlled And Operated By The Iws Until They Are No Longer Required. Both Schedulers Must Be Shared Until All Iws Jobs Have Been Completely Migrated