PMDS 2025

PMDS Dates

SMART Objectives

SMART Objective #1

Objective

Planned Output

End Year Comments

I resolved all requests assigned to me in a timely manner according to SLAs by carrying out the following activities:

- Routinely reviewed the monitoring reports and notifications, email inbox and ticket dashboards for incoming new tasks or inquiries, prioritising actions according to their urgency/impact categorisation.
- Supported customer requests/inquiries through chat and emails.
- Tracked the activities carried out in iNeed for accurate billing to customers.
- Maintained up to date ticket records in iNeed, following up when necessary with relevant parties for solving issues or completing requests.

I ensured that all services that I was responsible for had an availability of 99.9% or more by doing the following:
- Ensured that the correct monitoring and reporting was in place.
- Solved incoming issues in a timely manner according to their priority and SLAs.
- Coordinated with developers for deployments of new releases and for troubleshooting of ongoing issues, including the remediation of several critical WSO2 vulnerabilities through system analysis and escalation to developers for resolution.
- Maintained up to date related documentation and shared relevant information with the other team members by updating and improving the team's knowledge base.
- Took the necessary actions to avoid known issues and identify long-term solutions, for example by resolving firewall rule misconfigurations during the migration of the Open Street Map to Proxmox and coordinating corrective measures with relevant focal points to prevent similar issues in future deployments.
- Improved monitoring and reporting of the applications and its components to have a more proactive troubleshooting.
- Maintained up to date custom reports on relevant metrics to proactively detect possible issues.

During the period covered by this performance review, SLAs for tickets and applications availability were met.

Linked evidence:

**Migration of Open Street Map Server (ImpOSM) to Proxmox** Solved issues with fw rules by communicating quickly with relevant focal points Learn lesson about not preparing properly, assumed responsibility
Coordinated several critical vulnerabilities for WSO2, analyzing the systems to find the vulnerable files, escalating to developers and coordinating with them, and providing updates to security team.

SMART Objective #2

Objective

Planned Output

End Year Comments

SMART Objective #3

Objective

Planned Output

End Year Comments

- Collaborated with developers to support the migration of ESB services to Azure API Manager, focusing on testing activities and the controlled decommissioning of on-prem APIs.
- Worked on a proof of concept for an updated WSO2 version hosted in Azure Cloud servers to validate a possible upgrade path for the existing on-prem environment, including installing the ESB backend components and adjusting the approach after identifying database schema and compatibility constraints.
- Adapted the proof of concept execution to changing constraints by continuing development locally using containers after cloud resources were shut down for cost reasons, while documenting all steps to preserve learning and reusability.
- Wrote and refined automation scripts that simplified failover and data synchronization, reducing manual intervention and improving service continuity.
- Updated the ESB documentation to reflect new processes and troubleshooting steps, ensuring colleagues could work more independently when handling incidents or tickets.

Linked evidence:

**Create POC for new WSO2 version on Azure** Learnt to adapt to changing situation. Necessity to cut aggresively costs made the project stop because the cloud servers needed to be shutdown and deleted, but decided to continue on laptop with containers. Documented every step, so there was learning for the process, even if not finished.
Installed the backend part of the ESB POC.
Re-think of the PoC. We will install a simpler version (4.4?) and work on a MVP to test. I don't remember the details right now.
This week worked on creating a PoC for ESB to update to newest version of WSO2 (4.5 or 4.6). Realized most likely the original idea of just copying the data is not going to work because the schema is most likely changed and the software would be incompatible with the old DB, so I need to check either how to export and import the current data, or how to migrate sequentially to the new version.

Mandatory Team Objective

Competencies

Competency

Type

Order

End Year Comments

Learning and Development Plan

Area	Description	Status	Completion
Attending mandatory trainings as per HR recommendations	Prevention of Sexual Exploitation and Abuse (PSEA)	completed	—
Area Description Status Completion
Attending mandatory trainings as per HR recommendations	Information Security Awareness Training	completed	—
Area Description Status Completion
Attending trainings related to Linux, automation, and cloud technologies	AWS Data & AI Roadshow Workshop	completed	—
Area Description Status Completion
Attending trainings related to Linux, automation, and cloud technologies	AWS Certified Cloud Practitioner	in progress	—
Area Description Status Completion

Evidence Log

Description

Link To

Date

Description	Date	Linked
Create POC for new WSO2 version on Azure Learnt to adapt to changing situation. Necessity to cut aggresively costs made the project stop because the cloud servers needed to be shutdown and deleted, but decided to continue on laptop with containers. Documented every step, so there was learning for the process, even if not finished.	17 Dec 2025	objective
Description Create POC for new WSO2 version on Azure Learnt to adapt to changing situation. Necessity to cut aggresively costs made the project stop because the cloud servers needed to be shutdown and deleted, but decided to continue on laptop with containers. Documented every step, so there was learning for the process, even if not finished. Link To Date
Migration of Open Street Map Server (ImpOSM) to Proxmox Solved issues with fw rules by communicating quickly with relevant focal points Learn lesson about not preparing properly, assumed responsibility	17 Dec 2025	objective
Description Migration of Open Street Map Server (ImpOSM) to Proxmox Solved issues with fw rules by communicating quickly with relevant focal points Learn lesson about not preparing properly, assumed responsibility Link To Date
Installed the backend part of the ESB POC.	03 Dec 2025	objective
Description Installed the backend part of the ESB POC. Link To Date
Coordinated several critical vulnerabilities for WSO2, analyzing the systems to find the vulnerable files, escalating to developers and coordinating with them, and providing updates to security team.	26 Nov 2025	objective
Description Coordinated several critical vulnerabilities for WSO2, analyzing the systems to find the vulnerable files, escalating to developers and coordinating with them, and providing updates to security team. Link To Date
Re-think of the PoC. We will install a simpler version (4.4?) and work on a MVP to test. I don't remember the details right now.	12 Nov 2025	objective
Description Re-think of the PoC. We will install a simpler version (4.4?) and work on a MVP to test. I don't remember the details right now. Link To Date
This week worked on creating a PoC for ESB to update to newest version of WSO2 (4.5 or 4.6). Realized most likely the original idea of just copying the data is not going to work because the schema is most likely changed and the software would be incompatible with the old DB, so I need to check either how to export and import the current data, or how to migrate sequentially to the new version.	06 Nov 2025	objective
Description This week worked on creating a PoC for ESB to update to newest version of WSO2 (4.5 or 4.6). Realized most likely the original idea of just copying the data is not going to work because the schema is most likely changed and the software would be incompatible with the old DB, so I need to check either how to export and import the current data, or how to migrate sequentially to the new version. Link To Date

AI Assist: End Year Prompt

Copy or edit this prompt before pasting it into ChatGPT so you can convert your mid-year narrative into a past-tense end-year draft.

You are editing my PMDS draft.

Rules:

1. DO NOT change the text of “Objective” or “Planned output”. Only edit “comments” sections.
2. Preserve the existing structure exactly: keep the same headings, bullet points, ordering, spacing, and subdivisions. Do not add new sections like “Supporting evidence” or “Gaps”.
3. Convert all comment text from present/ongoing tense to past tense.
4. Incorporate evidence inline inside the most relevant existing bullet point by extending the sentence naturally (use “including…” / “for example…”). Do NOT add standalone “Evidence:” lines and do NOT mention dates.
5. If an evidence item does not fit any existing bullet, add ONE new bullet under the correct objective, and start it with “Also,” plus a one-sentence justification of why it supports that objective.
6. Keep the tone factual and professional. Prefer outcomes and actions. No extra commentary.
7. Before weaving an evidence entry into the comment, note which part of the comment it belongs to—reference that clause directly when you add the inline wording so the alignment is clear.

Output:

* Same PMDS text, same structure, with ONLY the updated end-year comments (past tense + evidence inline).
* If info is missing, append a short “Questions” section at the very end with only the minimum questions needed.

Input:
Below find the current mid-year PMDS and the linked evidences gathered during the year:

# Objectives:

## SMART Objective #1:
**Objective:**
Ensure all services are provided without interruption and degradation in service quality.

**Planned output:**
I will maintain SLAs and ensure 99.9% availability while monitoring KPIs and conducting regular reviews to prevent any interruption or degradation in service quality, ensuring consistent and reliable service delivery for stakeholders and end-users.

**Comments:**
(no comment provided yet)

## SMART Objective #2:
**Objective:**
Contribute to the consolidation of duty officer coverage across AOM into a single, shared DO model.

**Planned output:**
- Fix and enrich the Knowledge Base to standardize DO procedures and troubleshooting paths.
- Deliver knowledge-sharing/training sessions for AOM colleagues on the apps I manage.
- Design and publish a DO Incident Report form to simplify reporting, classification, and later consultation of troubleshooting and resolutions by duty officers.

**Comments:**
(no comment provided yet)

## SMART Objective #3:
**Objective:**
Support the modernization and migration of the ESB platform to Azure API Manager while improving its reliability, security, and operational efficiency.

**Planned output:**
- Support the migration of ESB services to Azure API Manager through testing and documentation updates.
- Develop a proof of concept to test an updated WSO2 version in Azure Cloud, addressing vulnerabilities and assessing feasibility for on-prem implementation.
- Improve system resilience by automating failover processes and enhancing operational documentation.

**Comments:**
(no comment provided yet)

## Team objective:
**Objective:**
Spending at least 40 hours of team learning on ilearn courses

**Comments:**
(not provided)

# Competencies:

**Technical Expertise**
**Comments:**
(no comment provided yet)

**Overall Attitude at Work**
**Comments:**
(no comment provided yet)

**Teamwork**
**Comments:**
(no comment provided yet)

**Respecting and Promoting Individual and Cultural Differences**
**Comments:**
(no comment provided yet)

**Communications**
**Comments:**
(no comment provided yet)

# Evidence log entries with “Linked to” objective number:

**Linked to: 
  
    
    
      SMART objective #3
    
  
**
**Create POC for new WSO2 version on Azure**
Learnt to adapt to changing situation. Necessity to cut aggresively costs made the project stop because the cloud servers needed to be shutdown and deleted, but decided to continue on laptop with containers.
Documented every step, so there was learning for the process, even if not finished.

**Linked to: 
  
    
    
      SMART objective #1
    
  
**
**Migration of Open Street Map Server (ImpOSM) to Proxmox**
Solved issues with fw rules by communicating quickly with relevant focal points
Learn lesson about not preparing properly, assumed responsibility

**Linked to: 
  
    
    
      SMART objective #3
    
  
**
Installed the backend part of the ESB POC.

**Linked to: 
  
    
    
      SMART objective #1
    
  
**
Coordinated several critical vulnerabilities for WSO2, analyzing the systems to find the vulnerable files, escalating to developers and coordinating with them, and providing updates to security team.

**Linked to: 
  
    
    
      SMART objective #3
    
  
**
Re-think of the PoC. We will install a simpler version (4.4?) and work on a MVP to test. I don't remember the details right now.

**Linked to: 
  
    
    
      SMART objective #3
    
  
**
This week worked on creating a PoC for ESB to update to newest version of WSO2 (4.5 or 4.6). Realized most likely the original idea of just copying the data is not going to work because the schema is most likely changed and the software would be incompatible with the old DB, so I need to check either how to export and import the current data, or how to migrate sequentially to the new version.

You can edit this before sending it to ChatGPT.