Title:

Project leader Solaris 10 in the financial sector

Location:

Brussels

Description:

• Background & Current Situation
  • 99% of our SUN-Solaris infrastructure is installed with the version 8 of the Operating System.
  • This Solaris 8 version was created by SUN in 2000.
  • There is a Solaris 10 that we have now to rollout on all SUN servers.
  • Based on the previous OS upgrade experience (Upgrade from Solaris 2.6 to Solaris 8), this is a 20 months project.
• Objectives
  • The objective is to rollout the solaris10 build on all SUN-Solaris servers within the bank (+or- 700 servers), taking into account business requirements (work only after business hours, during week-end, …).
  • This will permit us to keep an up to date infrastructure with the highest security/performance update.
• Scope
  • All SUN-Solaris servers are in scope and must be upgraded. In this case, upgrading is not applying the new version on the old one. The old version has to be scratched, so that the application will run on a clean Solaris10 install.
  • Two principles must be used:
  • The best way of doing it, if the application is on a legacy infrastructure, is to use spare and consolidated infrastructure.
  • An application will have an upgrade infrastructure at disposal to install a "to be qualified" version of its sources.
  • A second way of doing it, if the application is not on a legacy infrastructure, is to Backup -> Scratch the OS -> Restore on the same server. This has to be used as the generic principle.
  • Unfortunately, due to the application configuration, this is not always possible.
  • If the application is not on a legacy infrastructure but the service can't be interrupted too long enough, a new infrastructure as to be available to migrate the application.
  • The upgrade will first occurs in a development environment (called Alpha), then the test environment (called Beta) will be upgraded and finally in the production environment (Gamma).
  • Upgrades will be done per application (e.g.:Alpha GSP -> Beta GSP -> Gamma GSP) not per environment (All Alpha servers -> all Beta servers -> all Gamma servers).
  • The project leader has to obtain the Business commitment before upgrading an application.
  • Some mandays have to be foreseen per application in different teams (Storage, Business development, Network). The project leader has to analyze this during the PID phase.
  • Applications will be migrated as is no application upgrades will be performed during the Solaris migration.

Knowledge:

• Required
  • Project leader (as described in the standard contracts)
  • Support changes in the primary and secondary business processes by performing project management for (multi-disciplinary) IT projects.
  • Is responsible for setting up and managing the project team;
  • Is responsible for the project realization within the constraints imposed;
  • Translates policy documents into project plans for IT projects;
  • Ensures the acceptance and implementation of the project plan in consultation with future users;
  • Draws up a plan of approach, makes cost estimates and draws up time schedules for realizing (complex) projects including specifying the personnel and material consequences;
  • Monitors, evaluates and reports on the management aspects of (multi-disciplinary) projects;
  • Harmonizes the (status of) the execution and implementation of ongoing projects with the customers.
  • Relevant training in the area of IT and project management;
  • Management, verbal and written communication skills;
  • Practical knowledge of the primary and secondary business processes;
  • Knowledge and experience in the domains of IT projects and project management;
  • Knowledge of change management;
  • Experience in IT project organizations, structured work and documentation.
• Desired
  • PRINCE II

Experience:

3-5 years

Language:

N or F and English

Duration:

6 months

Offer:

Freelance

Type:

Contract

Rate:

Market rate

Reference:

Interteam.org - I0218002