Programme Manager

Programme purpose:Observability is defined as our ability to determine and measure a system''s current state based on the data that it generates through monitoring, logs, metrics, and traces. The point of observability is to be able to perceive and understand what''s happening across all Client''s environments so that we can proactively detect and correct issues before there is any impact on our employees, customers or other stakeholders.At Client, today much of our observability environment is fragmented with multiple bespoke solutions being used across the enterprise and with little to no end-to-end visibility. This in turn reduces our ability to monitor and respond proactively to unforeseen events. By introducing Enterprise Observability as a Service (OaaS), we intend to provide the business with the enterprise tools, processes, guidelines and understanding required to be able to implement full stack monitoring and machine-learning or Artificial Intelligence to automate root cause analysis and resolve issues rapidly and efficiently. Enterprise OaaS provides an End-to-End (E2E) enterprise market-standard tooling landscape with standardized processes, controls and service, reducing costs and eliminating risks. Programme scope/focus areas: - Communication: Its important to let the IT community know the Point C, goals, and objectives of OaaS. Also, we''ll need to provide contact details for questions relating to OaaS and continued communications as tools become available.- Proof of Concept: Point C tools not yet onboarded will require a Proof of Concept. The team will follow standard procedures of Non-Disclosures Agreements, IRM controls and Architectural engagement, etc.- Contracting: Tools that will be onboarded will require contract and procurement involvement. Existing tools need to be vetted to ensure there are enough licenses available for wider use.- Tool Uptake: ServiceNow will require updating to provide a catalogue of tools available to the IT community along with a description including features, functionality and purpose. Exception processes if not adhering to Point C. Create business process which acts as a control, ensuring checkpoints like TOE, PIRA, ITM community - catch points to avoid deviations.- Training: Need to determine which tools have training readily available (i.e. self directed) and which may require some hand-holding. - Administration: Given tools will be used by a wider IT community, it''s important to establish processes such as MACD, levels of access, attestation, etc. This will also help in license management.- Support & Maintenance: With so many tools being managed, it''s important to establish necessities such as version control, patch management, points of contact for cyber-related activities, etc.- Transform existing Client landscapes: Client landscape - track the monitoring tools and move to Point C. Manage the river & lake. Tools which suppliers use. - provided by Dice

Created: 2026-03-07