DIGITAL PRODUCT MANAGER

DIGITAL PRODUCT MANAGER

As asubject matter expert in BMC Control-M, you will play a pivotal role intransitioning our workload automation from legacy frameworks to ahigh-performing, hybrid cloud architecture, ensuring regulatory compliance acrossdesign, build and run phases.

Roles& Responsibilities:

·      Producea high‑level solution design for Control‑M and WCM, including:

o   Overallarchitecture topology (Control‑M/EM, EM Add-Ons like WCM, WA, MFTe, BIM,Self-service, Control‑M/Server, agents, plugins, APIs).

o   Integrationlandscape (ServiceNow, observability, log aggregation, monitoring tools, AzureDevOps, APIs).

o   HA and DR approach,including RTO 2 hours and RPO 0.

·      Producea low‑level design (LLD) detailing:

o   Infrastructurelayout (servers/VMs, clusters, storage, network zones, firewall flows).

o   OS, DB, Control-Mcomponent versions and configuration baselines.

o   Sizing model (CPU,memory, storage, IOPS, network bandwidth) for current and projected workloads.

o   Data architecture(Control‑M database schema usage, growth, retention, archiving).​

·      Preparematerial and artefacts required for Bank’s domain architect and solution designboards.

·      Presentand obtain approvals from:

o   Domainarchitecture, security, network, infrastructure, and application governanceforums.

·      Updatedesign artefacts per review feedback until formal approval and sign‑off.

·      Implementthe agreed Control‑M architecture across required environments (Dev, SIT, UAT,Pre‑Prod, Prod, DR).

·      Installand configure:

o   Control‑M/EnterpriseManager and associated Add-Ons Self-service, BIM

o   Package and RolloutControl-M/EM GUI clients on SCCM/XenDesktop/VDIs

o   Control‑M/Server.

o   Control‑M Agents(including Advanced File Transfer and application plugins as required).

o   Control-M/EMAdd-ons: Workload Change Manager (WCM), Workload Archiving

·      Designand implement:

o   Control‑M/EMtopology, including logical servers, domains, and security zones.

o   Agent deploymentstrategy and locations (on‑prem, cloud, containers, DMZ if required).

o   Networkconnectivity, firewall rules, load balancers, DNS, and certificates.

·      Designand implement highly available Control‑M components using supported HA patternsand database replication mechanisms.

·      ImplementDR setup at secondary site, including:

o   Asynchronous orsynchronous replication as appropriate.

o   Full failoverenvironment for Control‑M and database.

·      Validatethat solution achieves:

o   RTO: 2 hours.

o   RPO: 0 (no dataloss).

·      ConductDR drills and document:

o   Failover andfailback procedures.

o   Test results,issues, and remediation.

·      Implement role‑based access control (RBAC) for Control‑M,WCM, and associated tools.

·      Implement SSL/TLS for:

o   Control‑M/EMcommunication.

o   Control‑M/Serverand agents where supported.

·      Ensure alignment with Bank security standards andregulatory requirements (UK SOX, ISO, US, UK, Japan, MAS, and internaltechnology compliance).

·      Define and document:

o   Access controlmodel.

o   Privileged accessflows.

o   Segregation ofduties.

o   CI/CD withapprovals/audits.

·      IntegrateControl M alerts with ServiceNow (or equivalent ITSM) for:

o   Automatic incidentcreation.

o   Incident updatesand closure triggers based on batch events.

·      Configure:

o   Alert rules inControl M.

o   Mappings toServiceNow queues, priorities, assignment groups.

·      IntegrateControl‑M metrics and events into the Bank’s observability platform (e.g.,APM/metrics/logs stack).

·      Provide:

o   Metric definitions(e.g., job success/failure rates, queue depth, throughput).

o   JVM metrics (heapusage, GC pauses, thread count)

o   Databaseperformance (query time, connection pool usage)

o   Custom metrics (jobexecution time, queue depth, success rate)

o   API response timeand error rate

o   Infrastructuremetrics (CPU, memory, disk, network)

o   Dashboards andvisualisations for platform health and batch SLAs.

·      ForwardControl M logs and audit data to the Bank’s central log aggregation platform.

·      Define:

o   Log formats,fields, and parsing rules.

o   Retention andsearch use cases (e.g., audit, troubleshooting).

o   Log Retentionpolicy standards

·      IntegrateControl M infrastructure and application health into the Bank’s enterprisemonitoring tool.

·      Configure:

o   Health checks forall Control M components.

o   Thresholds, alerts,and escalation rules to L1 monitoring team.

·      Designand implement Control M API usage for:

o   Automated jobonboarding and changes.

o   Integration withCI/CD pipelines and external systems.

·      IntegrateControl M deployments with Azure DevOps (ADO) pipelines for:

o   Version control ofjob definitions and site standards.

o   Automated promotionacross environments (Dev → SIT → UAT → Prod).

·      Ensure:

o   Jobs, calendars,variables, resources, and site standards are stored in ADO repositories.

o   Deployments areexecuted via CI/CD, with approvals and audit trails.

·      Integratewith LDAP/Active Directory (AD) for user authentication and Azure AD (Entra ID)for SSO/MFA.

o   Set up LDAPSbinding in Control-M Configuration Manager:

o   Enable SSL/TLS: UseLDAPS (port 636); import AD cert chain to Control-M truststore.

o   Map LDAP/AD groupsto Control-M roles/users (e.g., AD group "CTM_Admins" → Control-MAdmin role).

o   Support usersynchronization: Automatic lookup on login; optional group-based provisioning.

·      ConfigureSAML in Control-M System Parameters:

o   Enable SAMLprovider; download Azure metadata XML (Federation Metadata URL).

o   Set Entity ID,Reply URL (ACS), Sign-on URL from Control-M.

o   Map SAML attributes(e.g., NameID to username, groups to roles).

·      AzureAD Setup:

o   Create EnterpriseApp for Control-M; configure SAML SSO.

o   Assignusers/groups; enable MFA policy (conditional access).

o   SupportIdP-initiated/ SP-initiated flows.

·      ClientCoverage: Control-M Web, Desktop (via proxy if needed), APIs (JWT validation).

·      Fallback:LDAP for non-SSO access; session timeout aligned to policy.
·      24x7production support using:

o   Business hoursL2/L3 support.

o   Out of hoursstandby/on call model for critical incidents.

·      Supportscope:

o   Control M BatchScheduling support (like job failures, SLA breaches, change windows).

o   Control MAdministration (user management, configurations, upgrades, core platformmaintenance,).

o   Control MEngineering (enhancements, integrations, performance tuning).

·      Performregular:

o   OS, DB, andapplication patching and upgrades for Control M and supporting components,ensuring no platform obsolescence.

o   Capacity reviewsand planning, with recommendations.

o   Backup and restoreof all platform components (configurations, databases, repositories).

·      Validatebackups regularly through recovery drills and document:

o   Backup schedules.

o   Recovery proceduresand outcomes.

·      Auditand compliance documents:

o   Evidence mappingfor UK SOX, ISO, US/UK/Japan/MAS regulatory requirements as applicable.

o   Audit logs, RFIresponses, and participation in audit briefings.

·      Conductstructured user and administrator trainings for:

o   Application teams(job modelling, monitoring, WCM usage).

o   Operations teams(L1/L2 support, dashboards, incident handling).

o   PlatformEngineering teams (advanced configuration and integrations).

·      Provide:

o   Training material,recordings (if permitted), and reference guides.

o   Formal knowledgetransfer from project implementation team to run/BAU team.

·      Providefull project management for the implementation phase, including:

o   End to end projectplanning and coordination, including:

§  Scope, schedule,budget, and resource management.

o   Risk and issuemanagement:

§  Maintenance of RAIDlogs.

§  Mitigation plansand escalations.

o   Stakeholdercommunication and reporting:

§  Regular statusreports.

§  Steering committeeand technical governance presentations.

o   Management of:

§  Dependencies withinfrastructure, security, application teams.

§  Vendor subcontractors (if any).

·      Proposeservice levels for:

o   Platformavailability (considering HA/DR and RTO/RPO targets).

o   Incident andrequest response/resolution times.

o   Change success rateand defect leakage.

·      Definequality measures for:

o   Documentationcompleteness and accuracy.

o   Testing coverageand defect metrics.

RequiredSkills:

·      10+ years of experience in IT delivery management,preferably in banking or financial services

·      Excellent stakeholder management, communication, andleadership skills

·      Expert-level experience with BMC Control-M (includingControl-M Automation API).

·      Proven track record in Azure Cloud migrations andAzure DevOps CI/CD implementation.

·      Deep understanding of Financial Services compliance(MAS, SOX, etc.).

·      Strong leadership skills with the ability to manage servicescross-functional delivery teams