Introduction of automated mechanisms for ticket registration and categorization for monitoring levels within IBM structures.

The project involved adapting automated units (software) that were implemented on the client's servers and automatically monitored the console (Tivoli) for alerts. Upon detecting such an alert, it automatically generated a ticket and assigned it to the so-called second-level support, where the tickets were resolved. This required integrating the client's systems with IBM devices, ensuring the proper flow of network data, and defining security protocols.

Responsibility:

•  Monitoring the schedule and reacting in case of a potential time overrun.
• Establishing communication within the team and among collaborators in the project and beyond.
• Updating documentation.
• Preparing and overseeing changes along with the Change Manager.
• Risk management - preparing contingency plans to eliminate or mitigate the occurrence of risks.

Methodology: WaterFall

Communication:

• Meetings with the Program Manager - DAILY
• Weekly reporting of progress and discussion of current issues
• Monthly meetings and presentation of project progress

Tools:

MS Office, Lotus Notes, Free Mind

Team:

The team is distributed across different departments, not assigned to a single project but to various ones. Requests were made by submitting forms through the team leaders of the respective teams. They were administrators, network specialists, and developers.

piotr@palmowskipm.pl

You can find me here.