{"id":6694,"date":"2022-08-16T20:13:14","date_gmt":"2022-08-16T20:13:14","guid":{"rendered":"https:\/\/bulletpc.pl\/?page_id=6694"},"modified":"2026-08-11T22:03:54","modified_gmt":"2026-08-11T22:03:54","slug":"projects-portfolio","status":"publish","type":"page","link":"https:\/\/bulletpc.pl\/?page_id=6694","title":{"rendered":"Case Study & Projects Portfolio"},"content":{"rendered":"

[vc_row][vc_column]

Case Studies & Projects Portfolio<\/span><\/h1>[\/vc_column][\/vc_row][vc_row][vc_column]
<\/div><\/div>[vc_column_text css=””]<\/p>\n

Complex systems. Clear requirements.
\nSolutions ready for delivery.<\/h2>\n

More than 20 years of working at the intersection of business and technology have taught me that technology itself is rarely the biggest challenge in complex projects.<\/p>\n

The real challenge is translating the needs of multiple stakeholders, existing systems, regulatory constraints and integration dependencies into a solution that can be clearly designed, implemented and tested.<\/p>\n

The following case studies present selected projects across enterprise integrations, CRM, pharmaceuticals, banking, access management and regulated systems. My experience covers requirements engineering, UML\/BPMN modelling, reverse engineering, impact assessment and collaboration with distributed EMEA\/APAC teams.<\/p>\n

[\/vc_column_text][vc_tta_tabs][vc_tta_section title=”CASE STUDY 01″ tab_id=”1784926386768-c690e7f9-d22a”][vc_column_text css=””]<\/p>\n

Global Integration Programme for the Pharmaceutical Industry<\/h2>\n

How do you maintain architectural and requirements consistency when a global programme spans multiple systems, countries, deployment waves and teams?<\/strong><\/p>\n

1. Context<\/h3>\n

A global pharmaceutical organisation was running a long-term programme involving numerous integrations, multiple deployment waves and several parallel sub-projects.<\/p>\n

The scope included integrations related to a global GTM platform and systems such as OCE, SailPoint, Reltio and PCS.<\/p>\n

The programme involved stakeholders and teams operating across several time zones, including EMEA and APAC.<\/p>\n

2. Challenge<\/h3>\n

In an environment involving multiple systems and teams, a local change rarely remains local.<\/p>\n

A new requirement could affect the data model, existing integrations, user lifecycle processes, downstream systems and the scope of future deployment waves.<\/p>\n

The challenge was therefore not simply to document individual functionalities, but to maintain a consistent view of the entire integration landscape and identify the impact of proposed changes before implementation.<\/strong><\/p>\n

3. Waldemar\u2019s Role<\/h3>\n

Waldemar worked as a Core Senior Business\u2013System Analyst<\/strong>, with responsibilities covering the analytical side of the integration programme, the canonical integration model and the Change Request process.<\/p>\n

His role connected business, system and integration perspectives while coordinating with business stakeholders, technical teams and solution owners.<\/p>\n

4. Scope of Analysis<\/h3>\n

The work included:<\/p>\n

    \n
  • business and system requirements analysis,<\/li>\n
  • system integration analysis,<\/li>\n
  • maintenance and evolution of the canonical integration model,<\/li>\n
  • Change Request analysis and impact assessment,<\/li>\n
  • dependency analysis across systems,<\/li>\n
  • analytical support for deployment waves and sub-projects,<\/li>\n
  • user lifecycle analysis,<\/li>\n
  • support for solution design prior to implementation and testing.<\/li>\n<\/ul>\n

    Selected assignments included OCE\u2013SailPoint integration and Reltio\u2013PCS integrations implemented across multiple countries.<\/p>\n

    5. Methods & Deliverables<\/h3>\n

    Depending on the project stage, deliverables included:<\/p>\n

      \n
    • integration models,<\/li>\n
    • High-Level Design documentation,<\/li>\n
    • Business Requirements Documents,<\/li>\n
    • SLAs,<\/li>\n
    • RFP materials,<\/li>\n
    • test plans,<\/li>\n
    • Change Request analysis,<\/li>\n
    • impact assessments,<\/li>\n
    • requirements and project documentation,<\/li>\n
    • backlog and requirements management in JIRA.<\/li>\n<\/ul>\n

      Discovery sessions, workshops, demonstrations and retrospectives were also an important part of the work.<\/p>\n

      6. Stakeholder Collaboration<\/h3>\n

      The programme required close cooperation with distributed teams and stakeholders from multiple regions.<\/p>\n

      The analyst\u2019s role went beyond collecting information. It involved bringing different perspectives together into a clear and consistent solution model<\/strong>, while ensuring that decisions made within one area reflected their impact on the wider ecosystem.<\/p>\n

      7. Outcome<\/h3>\n

      The work resulted in a consistent set of models, analyses and documentation supporting subsequent programme changes and deployment waves.<\/p>\n

      The canonical integration model provided a shared reference point for dependency analysis, while impact assessments supported informed decision-making before changes were implemented.<\/p>\n

      Business value:<\/strong> improved predictability of changes in a complex integration environment and clearer communication between business and technical teams.<\/p>\n

      8. Technologies & Tools<\/h3>\n

      OCE \u2022 SailPoint \u2022 Reltio \u2022 PCS \u2022 Enterprise Architect \u2022 JIRA \u2022 Enterprise Integrations \u2022 Canonical Models \u2022 UML\/BPMN<\/strong><\/p>\n

      9. Confidentiality<\/h3>\n

      This case study describes the scope of responsibilities and working approach without disclosing client-owned information, detailed architecture, data or confidential business rules.<\/p>\n

      CTA:<\/strong>
      Running a programme involving multiple integrations and systems? Let\u2019s discuss how to structure requirements and dependencies before implementation.<\/strong><\/p>\n

      [\/vc_column_text][vc_column_text css=””]<\/p>\n

      Project Portfolio<\/strong><\/h1>\n

      Selected Projects Across Enterprise IT, Integrations, CRM and Regulated Environments<\/h2>\n

      Over more than 20 years in IT, I have worked on projects ranging from global integration programmes and enterprise CRM platforms to access governance, regulatory transformation and mission-critical public-sector systems.<\/p>\n

      My role has typically been positioned between business and technology: clarifying requirements, modelling processes and solutions, analysing integrations, reconstructing legacy behaviour and preparing delivery teams to implement changes with a shared understanding of the target solution.<\/p>\n

      The portfolio below presents selected assignments across pharmaceuticals, banking, finance, telecommunications, energy and the public sector.<\/p>\n

      [\/vc_column_text]

      <\/div><\/div>[\/vc_tta_section][vc_tta_section title=”CASE STUDY 02″ tab_id=”1784926386774-69ead0b1-99f4″][vc_column_text css=””]<\/p>\n

      CRM & Customer Lifetime Value in Banking<\/h2>\n

      How do you develop a complex CRM environment, when part of the knowledge about the existing solution first needs to be reconstructed?<\/strong><\/p>\n

      1. Context<\/h3>\n

      The project involved a Customer Lifetime Value \/ CRM environment<\/strong> for a European bank and covered both ongoing development and maintenance of an existing solution.<\/p>\n

      Waldemar was responsible for maintaining the solution model in Enterprise Architect, analysing sprint scope, facilitating workshops and reverse-engineering existing CRM functionalities and integrations.<\/p>\n

      2. Challenge<\/h3>\n

      Systems developed over many years do not always have documentation that accurately reflects their current behaviour.<\/p>\n

      Before designing a new change, it was therefore necessary to establish:<\/p>\n

        \n
      • how an existing functionality actually worked,<\/li>\n
      • which components it depended on,<\/li>\n
      • where system responsibility boundaries were located,<\/li>\n
      • how a proposed change would affect the existing landscape,<\/li>\n
      • how to describe the change clearly for both business and development teams.<\/li>\n<\/ul>\n

        3. Waldemar\u2019s Role<\/h3>\n

        As a Senior Business\u2013System Analyst<\/strong>, Waldemar was responsible for end-to-end analysis of sprint scope and for maintaining consistency between business requirements, the existing solution model and planned changes.<\/p>\n

        4. Scope of Analysis<\/h3>\n

        The work included:<\/p>\n

          \n
        • analysis of upcoming sprint scope,<\/li>\n
        • reverse engineering of existing CRM functionalities,<\/li>\n
        • integration analysis,<\/li>\n
        • maintenance of the Enterprise Architect model,<\/li>\n
        • dependency identification,<\/li>\n
        • clarification of business requirements,<\/li>\n
        • preparation of changes for development teams.<\/li>\n<\/ul>\n

          5. Methods & Deliverables<\/h3>\n

          The work involved:<\/p>\n

            \n
          • Enterprise Architect models,<\/li>\n
          • use cases,<\/li>\n
          • user stories,<\/li>\n
          • change documentation,<\/li>\n
          • business and technical workshops,<\/li>\n
          • as-is analysis,<\/li>\n
          • reverse engineering,<\/li>\n
          • end-to-end analysis.<\/li>\n<\/ul>\n

            The CV specifically confirms responsibility for maintaining the EA model as well as delivering use cases, user stories and supporting documentation for changes.<\/p>\n

            6. Stakeholder Collaboration<\/h3>\n

            Workshops were conducted with both business stakeholders and development teams.<\/p>\n

            This made it possible to compare business expectations with the actual behaviour of the existing solution and identify gaps between the expected and technically feasible scope of a change.<\/p>\n

            7. Outcome<\/h3>\n

            Each change was supported by clear analytical documentation connecting the existing system, the business requirement and the work of the development team.<\/strong><\/p>\n

            Reverse engineering allowed new changes to be designed based on the actual behaviour of the solution rather than outdated assumptions or incomplete documentation.<\/p>\n

            8. Technologies & Tools<\/h3>\n

            CRM \u2022 Customer Lifetime Value \u2022 Enterprise Architect \u2022 UML \u2022 Requirements Engineering \u2022 Reverse Engineering<\/strong><\/p>\n

            9. Confidentiality<\/h3>\n

            The case study does not disclose the bank\u2019s internal processes, data models, solution architecture or commercially sensitive information.<\/p>\n

            CTA:<\/strong>
            Is your CRM documentation no longer aligned with the system itself? Let\u2019s start with an as-is analysis and reverse engineering.<\/strong><\/p>\n

            [\/vc_column_text][\/vc_tta_section][vc_tta_section title=”CASE STUDY 03″ tab_id=”1784926673870-f28ae5c2-057a”][vc_column_text css=””]<\/p>\n

            User Access Management for Finance & Budgeting<\/h2>\n

            How do you translate access policies and governance principles into processes that make sense to users, business stakeholders and IT teams?<\/strong><\/p>\n

            1. Context<\/h3>\n

            The project involved User Access Management for finance and budgeting systems<\/strong> within an international organisation.<\/p>\n

            The scope covered access processes, roles, permission models and governance principles.<\/p>\n

            Waldemar led the analysis, prepared business and technical documentation, facilitated workshops and supported end-user training.<\/p>\n

            2. Challenge<\/h3>\n

            Access management sits at the intersection of several areas:<\/p>\n

            user needs, organisational structure, security requirements, operational processes and system constraints.<\/strong><\/p>\n

            Defining who should have access is not enough.<\/p>\n

            A complete solution must also establish roles, approval paths, access provisioning and removal processes, responsibilities, exceptions and governance across the entire access lifecycle.<\/p>\n

            3. Waldemar\u2019s Role<\/h3>\n

            Waldemar worked as the Senior Business\u2013System Analyst responsible for UAM analysis<\/strong>, connecting process requirements with role and access models.<\/p>\n

            4. Scope of Analysis<\/h3>\n

            The scope included:<\/p>\n

              \n
            • access provisioning and modification processes,<\/li>\n
            • business and system roles,<\/li>\n
            • permission models,<\/li>\n
            • approval flows,<\/li>\n
            • governance,<\/li>\n
            • ownership and responsibilities,<\/li>\n
            • exception scenarios,<\/li>\n
            • the end-user perspective of new access management processes.<\/li>\n<\/ul>\n

              5. Methods & Deliverables<\/h3>\n

              Deliverables included:<\/p>\n

                \n
              • process models,<\/li>\n
              • role and access models,<\/li>\n
              • business documentation,<\/li>\n
              • technical documentation,<\/li>\n
              • training support materials,<\/li>\n
              • outputs from workshops and brainstorming sessions.<\/li>\n<\/ul>\n

                6. Stakeholder Collaboration<\/h3>\n

                The analysis was performed through collaborative workshops.<\/p>\n

                This ensured that access rules were not designed purely from a technical perspective, but also reflected how users and process owners actually worked with finance and budgeting systems.<\/p>\n

                7. Outcome<\/h3>\n

                The project resulted in a structured and documented UAM process model<\/strong>, covering roles, access and responsibilities as well as documentation supporting communication of the new processes to end users.<\/p>\n

                The engagement also included support for user training related to the new UAM processes.<\/p>\n

                8. Technologies & Tools<\/h3>\n

                User Access Management \u2022 Role & Access Models \u2022 Governance \u2022 Process Modelling \u2022 Requirements Engineering<\/strong><\/p>\n

                9. Confidentiality<\/h3>\n

                For security reasons, the case study does not describe detailed authorisation mechanisms, permission structures or the client\u2019s system architecture.<\/p>\n

                CTA:<\/strong>
                Designing UAM, RBAC or access governance processes? Let\u2019s translate security requirements into clear processes and access models.<\/strong><\/p>\n

                [\/vc_column_text][\/vc_tta_section][vc_tta_section title=”CASE STUDY 04″ tab_id=”1784926784580-91a2ff25-98e9″][vc_column_text css=””]<\/p>\n

                GDPR & Blockchain Platform for the Financial Sector<\/h2>\n

                How do you connect regulatory requirements, distributed architecture and integrations with multiple financial institutions?<\/strong><\/p>\n

                1. Context<\/h3>\n

                The engagement covered two significant areas within the financial sector: implementation of GDPR-related regulatory changes<\/strong> and development of a DLT\/blockchain platform designed to work with multiple banks.<\/p>\n

                The solution supported public and private document storage and had to address requirements associated with the \u201cright to be forgotten\u201d.<\/p>\n

                2. Challenge<\/h3>\n

                The project combined three complex areas:<\/p>\n

                regulation + inter-organisational integrations + emerging technology.<\/strong><\/p>\n

                In a solution involving multiple financial institutions, a legal requirement has to be translated into precise system behaviour, data considerations, integration requirements and test scenarios.<\/p>\n

                3. Waldemar\u2019s Role<\/h3>\n

                As a Senior Business Systems Analyst<\/strong>, Waldemar was responsible for business and systems analysis, project documentation and technical clarification for both GDPR and blockchain initiatives.<\/p>\n

                4. Scope of Analysis<\/h3>\n

                The work included:<\/p>\n

                  \n
                • analysis of GDPR-driven changes,<\/li>\n
                • requirements concerning document processing,<\/li>\n
                • integration of the platform with multiple banks,<\/li>\n
                • integration-level analysis,<\/li>\n
                • technical clarification of requirements,<\/li>\n
                • analytical support for testing activities.<\/li>\n<\/ul>\n

                  5. Methods & Deliverables<\/h3>\n

                  Activities included:<\/p>\n

                    \n
                  • project documentation,<\/li>\n
                  • business and system requirements,<\/li>\n
                  • integration analysis,<\/li>\n
                  • technical clarifications,<\/li>\n
                  • QA support,<\/li>\n
                  • User Acceptance Testing,<\/li>\n
                  • Business Acceptance Testing,<\/li>\n
                  • ad-hoc analysis.<\/li>\n<\/ul>\n

                    The CV directly confirms involvement in both integrating the blockchain platform with multiple banks and supporting QA, UAT and BAT.<\/p>\n

                    6. Stakeholder Collaboration<\/h3>\n

                    The project required alignment between regulatory, business and technology perspectives.<\/p>\n

                    A key part of the analyst\u2019s role was ensuring that expected system behaviour was described clearly enough to be consistently interpreted by integration and testing teams.<\/p>\n

                    7. Outcome<\/h3>\n

                    The work delivered the documentation and analysis required to support regulatory changes and integration of the DLT solution with financial institutions.<\/p>\n

                    Analytical support during QA, UAT and BAT also helped verify that the implemented solution remained aligned with agreed requirements.<\/p>\n

                    8. Technologies & Tools<\/h3>\n

                    GDPR \u2022 DLT \/ Blockchain \u2022 Banking Integrations \u2022 QA \u2022 UAT \u2022 BAT \u2022 Requirements Engineering<\/strong><\/p>\n

                    9. Confidentiality<\/h3>\n

                    The case study does not disclose solution topology, banking interfaces, processed data or detailed security mechanisms.<\/p>\n

                    CTA:<\/strong>
                    Does your project combine regulatory requirements with integrations across multiple organisations? Let\u2019s turn regulatory obligations into clear system requirements and verification scenarios.<\/strong><\/p>\n

                    [\/vc_column_text][\/vc_tta_section][vc_tta_section title=”CASE STUDY 05″ tab_id=”1784926922388-0a7ab167-50a7″][vc_column_text css=””]<\/p>\n

                    Mission-Critical System in a Regulated Environment<\/h2>\n

                    How do you conduct systems analysis when security and unambiguous documentation are integral parts of the solution itself?<\/strong><\/p>\n

                    1. Context<\/h3>\n

                    The project involved a web application designed for border guard services.<\/p>\n

                    It was developed in a regulated, security-focused environment and delivered iteratively using Agile practices.<\/p>\n

                    2. Challenge<\/h3>\n

                    In mission-critical systems, an ambiguous requirement is not merely a project management issue.<\/p>\n

                    It may affect system security, user behaviour, testing and the decisions made by implementation teams.<\/p>\n

                    Maintaining consistency between business documentation, the system model and the scope of subsequent sprints was therefore particularly important.<\/p>\n

                    3. Waldemar\u2019s Role<\/h3>\n

                    Waldemar was responsible for preparing business and technical documentation<\/strong>, maintaining the solution model in Enterprise Architect and providing analysis for subsequent Agile sprint scopes.<\/p>\n

                    4. Scope of Analysis<\/h3>\n

                    The work included:<\/p>\n

                      \n
                    • business requirements,<\/li>\n
                    • system requirements,<\/li>\n
                    • sprint scope analysis,<\/li>\n
                    • solution modelling,<\/li>\n
                    • analysis of dependencies between system components,<\/li>\n
                    • preparation of analytical information for delivery teams.<\/li>\n<\/ul>\n

                      5. Methods & Deliverables<\/h3>\n

                      Key deliverables included:<\/p>\n

                        \n
                      • business documentation,<\/li>\n
                      • technical documentation,<\/li>\n
                      • the solution model in Enterprise Architect,<\/li>\n
                      • analyses supporting successive Agile sprints.<\/li>\n<\/ul>\n

                        6. Stakeholder Collaboration<\/h3>\n

                        The engagement required close alignment between business and technical analysis.<\/p>\n

                        The analyst\u2019s role was to maintain a common language between operational requirements and their representation within the system solution.<\/p>\n

                        7. Outcome<\/h3>\n

                        The result was a set of documentation and a maintained solution model supporting iterative development of the application.<\/p>\n

                        In a security-sensitive environment, particular value came from providing a clear, structured and traceable description of the solution and its requirements.<\/strong><\/p>\n

                        8. Technologies & Tools<\/h3>\n

                        Enterprise Architect \u2022 Web Applications \u2022 Agile \u2022 Business & Systems Analysis \u2022 Technical Documentation<\/strong><\/p>\n

                        9. Confidentiality<\/h3>\n

                        Due to the nature of the project, publicly available information is limited to the type and scope of analytical work performed. Functional details, architecture and security mechanisms are not disclosed.<\/p>\n

                        CTA:<\/strong>
                        Working on a regulated or mission-critical system? Let\u2019s discuss how to structure requirements, models and documentation for reliable delivery.<\/strong><\/p>\n

                        [\/vc_column_text][\/vc_tta_section][\/vc_tta_tabs][vc_tta_tabs][vc_tta_section title=”01. Global GTM Platform for Pharmaceutical Affiliates” tab_id=”1660681055501-8d176c32-2bf3″]

                        Sep 2007 - Jun 2014 \u00b7 6 yrs 10 mos<\/span><\/h3>[vc_column_text css=””]Pharma \u2022 GTM Platform \u2022 Regional Delivery \u2022 Enterprise Analysis<\/strong><\/p>\n

                        Project Overview<\/h3>\n

                        Business and systems analysis for regional affiliates participating in a global Go-To-Market platform programme.<\/p>\n

                        The engagement required translating global platform capabilities into requirements and analytical packages that could support regional implementation and ongoing development.<\/p>\n

                        My Contribution<\/h3>\n

                        As a Lead Senior Business\u2013System Analyst<\/strong>, I was responsible for:<\/p>\n

                          \n
                        • maintaining and evolving the domain model in Enterprise Architect,<\/li>\n
                        • preparing analysis packages for individual sprints,<\/li>\n
                        • facilitating workshops with business and development teams,<\/li>\n
                        • reverse-engineering existing work items and implemented solutions,<\/li>\n
                        • preparing use cases and user stories,<\/li>\n
                        • producing business and technical documentation,<\/li>\n
                        • supporting ongoing BAU analysis.<\/li>\n<\/ul>\n

                          Business Perspective<\/h3>\n

                          The key analytical challenge was maintaining alignment between global platform standards and regional business requirements<\/strong> without losing visibility of existing dependencies and implemented functionality.<\/p>\n

                          Methods & Tools<\/h3>\n

                          Enterprise Architect \u2022 Requirements Engineering \u2022 Use Cases \u2022 User Stories \u2022 Reverse Engineering \u2022 Workshops \u2022 Agile<\/strong><\/p>\n

                          [\/vc_column_text][\/vc_tta_section][vc_tta_section title=”02. Enterprise CRM \/ ERP Landscape Development” tab_id=”1660681055510-02309f70-54d5″]

                          Jul 2014 - Apr 2015 \u00b7 10 mos<\/span><\/h3>[vc_column_text css=””]<\/p>\n

                          Pharma & Banking \u2022 CRM \u2022 ERP \u2022 Sprint Analysis<\/strong><\/p>\n

                          Project Overview<\/h3>\n

                          Analysis of a complex CRM\/ERP environment covering both ongoing system evolution and preparation of clearly defined scope for development teams.<\/p>\n

                          My Contribution<\/h3>\n

                          The work included:<\/p>\n

                            \n
                          • maintaining the Enterprise Architect model,<\/li>\n
                          • end-to-end analysis of sprint scope,<\/li>\n
                          • workshops with business and development teams,<\/li>\n
                          • reverse engineering of existing CRM capabilities,<\/li>\n
                          • integration analysis,<\/li>\n
                          • preparation of use cases and user stories,<\/li>\n
                          • supporting documentation for planned changes.<\/li>\n<\/ul>\n

                            Business Perspective<\/h3>\n

                            The objective was to reduce ambiguity between business expectations, existing system behaviour and implementation scope<\/strong>.<\/p>\n

                            Rather than treating individual requirements in isolation, the analysis considered the wider CRM and ERP landscape and the impact of proposed changes across connected functionality.<\/p>\n

                            Methods & Tools<\/h3>\n

                            CRM \u2022 ERP \u2022 Enterprise Architect \u2022 Requirements Engineering \u2022 Reverse Engineering \u2022 Agile<\/strong><\/p>\n

                            [\/vc_column_text][\/vc_tta_section][vc_tta_section title=”03. Customer Lifetime Value CRM” tab_id=”1660681106663-78cd1e86-d556″]

                            Nov 2014 - Apr 2015 \u00b7 6 mos<\/span><\/h3>[vc_column_text css=””]<\/p>\n

                            Banking \u2022 CRM \u2022 Customer Lifetime Value \u2022 R&D & Maintenance<\/strong><\/p>\n

                            Project Overview<\/h3>\n

                            Development and maintenance of a Customer Lifetime Value CRM environment for a European banking organisation.<\/p>\n

                            The project combined ongoing product development with analytical work required to understand and evolve an established CRM landscape.<\/p>\n

                            My Contribution<\/h3>\n

                            Responsibilities included:<\/p>\n

                              \n
                            • maintaining the CLV\/CRM model in Enterprise Architect,<\/li>\n
                            • analysing sprint scope end to end,<\/li>\n
                            • leading workshops,<\/li>\n
                            • reconstructing existing CRM functionality,<\/li>\n
                            • analysing integrations,<\/li>\n
                            • preparing use cases, user stories and supporting documentation.<\/li>\n<\/ul>\n

                              Business Perspective<\/h3>\n

                              A significant part of the work involved converting knowledge embedded in an existing system into structured analytical documentation that could support future changes<\/strong>.<\/p>\n

                              Methods & Tools<\/h3>\n

                              CRM \u2022 Customer Lifetime Value \u2022 Enterprise Architect \u2022 UML \u2022 Reverse Engineering \u2022 Workshops<\/strong><\/p>\n

                              [\/vc_column_text][\/vc_tta_section][vc_tta_section title=”04. Global Enterprise Integration Programme” tab_id=”1660681129682-e6dc157f-5c6b”]

                              May 2015 - Jun 2017 \u00b7 2 yrs 2 mos<\/span><\/h3>[vc_column_text css=””]<\/p>\n

                              Pharma \u2022 Global Integrations \u2022 Canonical Model \u2022 EMEA\/APAC<\/strong><\/p>\n

                              Project Overview<\/h3>\n

                              Long-term participation in a global pharmaceutical integration programme comprising multiple implementation waves, sub-projects and enterprise systems.<\/p>\n

                              My Contribution<\/h3>\n

                              As a Core Senior Business\u2013System Analyst<\/strong>, I was responsible for:<\/p>\n

                                \n
                              • the analytical perspective of the canonical integration model,<\/li>\n
                              • Change Request analysis,<\/li>\n
                              • impact assessments,<\/li>\n
                              • integration-level optimisation,<\/li>\n
                              • business and technical documentation,<\/li>\n
                              • workshops, discovery sessions and demonstrations,<\/li>\n
                              • JIRA requirements and backlog management,<\/li>\n
                              • coordination across EMEA and APAC time zones.<\/li>\n<\/ul>\n

                                Business Perspective<\/h3>\n

                                The central challenge was maintaining a reliable view of dependencies across a constantly evolving global integration landscape.<\/p>\n

                                The analytical model provided a common point of reference when assessing how new changes could affect existing systems and integrations.<\/p>\n

                                Selected Deliverables<\/h3>\n

                                HLD \u2022 BRD \u2022 SLA \u2022 RFP \u2022 Test Plans \u2022 Impact Assessments \u2022 Integration Models<\/strong><\/p>\n

                                [\/vc_column_text][\/vc_tta_section][vc_tta_section title=”05. Marketing Platform Integration” tab_id=”1660681191040-f938bc64-8be8″]

                                Mar 2018 - Jan 2019 \u00b7 11 mos<\/span><\/h3>[vc_column_text css=””]<\/p>\n

                                Pharma \u2022 Enterprise Integration \u2022 Marketing Technology<\/strong><\/p>\n

                                Project Overview<\/h3>\n

                                Integration of an enterprise pharmaceutical platform with OCE to support marketing-related business scenarios.<\/p>\n

                                My Contribution<\/h3>\n

                                The analytical work focused on understanding the business use cases, defining integration requirements and positioning the change within the wider enterprise integration landscape.<\/p>\n

                                Key Areas<\/h3>\n
                                  \n
                                • business use-case analysis,<\/li>\n
                                • integration requirements,<\/li>\n
                                • dependency identification,<\/li>\n
                                • impact assessment,<\/li>\n
                                • documentation supporting delivery and testing.<\/li>\n<\/ul>\n

                                  Business Perspective<\/h3>\n

                                  The project required translating marketing requirements into precise system interactions that could be implemented consistently within an existing enterprise architecture<\/strong>.<\/p>\n

                                  Methods & Tools<\/h3>\n

                                  OCE \u2022 Integration Analysis \u2022 Requirements Engineering \u2022 Enterprise Architecture<\/strong><\/p>\n

                                  The integration is listed among the selected sub-projects of the global pharmaceutical programme.<\/p>\n

                                  [\/vc_column_text][\/vc_tta_section][vc_tta_section title=”06. Identity Lifecycle Integration” tab_id=”1786308948932-05dbe126-cc27″]

                                  Mar 2018 - Jan 2019 \u00b7 11 mos<\/span><\/h3>[vc_column_text css=””]<\/p>\n

                                  Pharma \u2022 Identity Management \u2022 OCE \u2022 SailPoint<\/strong><\/p>\n

                                  Project Overview<\/h3>\n

                                  Integration between OCE and SailPoint supporting the complete user lifecycle.<\/p>\n

                                  The scope included lifecycle events such as:<\/p>\n

                                  create \u2022 activate \u2022 deactivate \u2022 delete<\/strong><\/p>\n

                                  My Contribution<\/h3>\n

                                  The work required analysing how user states and identity-management processes should be represented consistently across connected systems.<\/p>\n

                                  Key Areas<\/h3>\n
                                    \n
                                  • user lifecycle analysis,<\/li>\n
                                  • system interaction modelling,<\/li>\n
                                  • integration requirements,<\/li>\n
                                  • state and dependency analysis,<\/li>\n
                                  • Change Request and impact assessment support.<\/li>\n<\/ul>\n

                                    Business Perspective<\/h3>\n

                                    Identity integrations are highly dependent on consistent rules and system states. The analytical goal was to ensure that business lifecycle events translated into unambiguous behaviour across both systems<\/strong>.<\/p>\n

                                    Technologies<\/h3>\n

                                    OCE \u2022 SailPoint \u2022 Identity Lifecycle \u2022 Enterprise Integration<\/strong><\/p>\n

                                    [\/vc_column_text][\/vc_tta_section][vc_tta_section title=”07. Master Data Integration Across Multiple Countries” tab_id=”1786309169306-4d134d61-1e7a”]

                                    Mar 2018 - Jan 2019 \u00b7 11 mos<\/span><\/h3>[vc_column_text css=””]<\/p>\n

                                    Pharma \u2022 Master Data \u2022 Reltio \u2022 PCS \u2022 APAC<\/strong><\/p>\n

                                    Project Overview<\/h3>\n

                                    Integration between Reltio and PCS deployed across multiple national environments, including markets in Asia-Pacific.<\/p>\n

                                    My Contribution<\/h3>\n

                                    The work supported integration analysis across country-specific implementations while maintaining consistency with the wider enterprise integration model.<\/p>\n

                                    Key Areas<\/h3>\n
                                      \n
                                    • integration dependencies,<\/li>\n
                                    • data-flow analysis,<\/li>\n
                                    • regional implementation considerations,<\/li>\n
                                    • impact assessment,<\/li>\n
                                    • analytical documentation.<\/li>\n<\/ul>\n

                                      Business Perspective<\/h3>\n

                                      Multi-country deployments introduce additional complexity because a common integration model must coexist with local implementation requirements and regional dependencies<\/strong>.<\/p>\n

                                      Technologies<\/h3>\n

                                      Reltio \u2022 PCS \u2022 Master Data \u2022 Enterprise Integrations \u2022 APAC<\/strong><\/p>\n

                                      The CV explicitly identifies deployments in several countries, including Taiwan, the Philippines and China.<\/p>\n

                                      [\/vc_column_text][\/vc_tta_section][vc_tta_section title=”08. International Drug Pricing Information Solution” tab_id=”1786309244607-bd302e99-d336″]

                                      Mar 2018 - Jan 2019 \u00b7 11 mos<\/span><\/h3>[vc_column_text css=””]<\/p>\n

                                      Pharma \u2022 Global Data \u2022 Pricing \u2022 50+ Countries<\/strong><\/p>\n

                                      Project Overview<\/h3>\n

                                      A solution designed to inform pharmaceutical affiliates and global teams about changes in drug prices across more than 50 countries.<\/p>\n

                                      Project Context<\/h3>\n

                                      The solution operated in an international environment where pricing information had to remain understandable and usable across multiple markets.<\/p>\n

                                      Analytical Focus<\/h3>\n

                                      The project required attention to:<\/p>\n

                                        \n
                                      • information flows,<\/li>\n
                                      • data consistency,<\/li>\n
                                      • international business requirements,<\/li>\n
                                      • stakeholder communication,<\/li>\n
                                      • structured documentation.<\/li>\n<\/ul>\n

                                        Business Perspective<\/h3>\n

                                        The scale of the project made consistency and clarity of information across countries<\/strong> particularly important.<\/p>\n

                                        Domain<\/h3>\n

                                        Pharmaceutical Pricing \u2022 Global Information Management \u2022 International Operations<\/strong><\/p>\n

                                        The project is identified in the CV as SARA IRP and covered drug-price change information across 50+ countries.<\/p>\n

                                        [\/vc_column_text][\/vc_tta_section][\/vc_tta_tabs][\/vc_column][\/vc_row]<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"

                                        [vc_row][vc_column][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text css=””] Complex systems. Clear requirements. Solutions ready for delivery. More than 20 years of working at the intersection of business and technology have taught me that technology itself is rarely the biggest challenge in complex projects. The real challenge is translating the needs of multiple stakeholders, existing systems, regulatory constraints and integration dependencies into […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-6694","page","type-page","status-publish","hentry"],"yoast_head":"\nCase Study & Projects Portfolio - PROSKILLED<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/bulletpc.pl\/?page_id=6694\" \/>\n<meta property=\"og:locale\" content=\"pl_PL\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Case Study & Projects Portfolio - PROSKILLED\" \/>\n<meta property=\"og:description\" content=\"[vc_row][vc_column][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text css=””] Complex systems. Clear requirements. Solutions ready for delivery. More than 20 years of working at the intersection of business and technology have taught me that technology itself is rarely the biggest challenge in complex projects. The real challenge is translating the needs of multiple stakeholders, existing systems, regulatory constraints and integration dependencies into […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/bulletpc.pl\/?page_id=6694\" \/>\n<meta property=\"og:site_name\" content=\"PROSKILLED\" \/>\n<meta property=\"article:modified_time\" content=\"2026-08-11T22:03:54+00:00\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Szacowany czas czytania\" \/>\n\t<meta name=\"twitter:data1\" content=\"20 minut\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/bulletpc.pl\\\/?page_id=6694\",\"url\":\"https:\\\/\\\/bulletpc.pl\\\/?page_id=6694\",\"name\":\"Case Study & Projects Portfolio - PROSKILLED\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/bulletpc.pl\\\/#website\"},\"datePublished\":\"2022-08-16T20:13:14+00:00\",\"dateModified\":\"2026-08-11T22:03:54+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/bulletpc.pl\\\/?page_id=6694#breadcrumb\"},\"inLanguage\":\"pl-PL\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/bulletpc.pl\\\/?page_id=6694\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/bulletpc.pl\\\/?page_id=6694#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Strona g\u0142\u00f3wna\",\"item\":\"https:\\\/\\\/bulletpc.pl\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Case Study & Projects Portfolio\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/bulletpc.pl\\\/#website\",\"url\":\"https:\\\/\\\/bulletpc.pl\\\/\",\"name\":\"PROSKILLED\",\"description\":\"Senior Business System Analyst\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/bulletpc.pl\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"pl-PL\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Case Study & Projects Portfolio - PROSKILLED","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/bulletpc.pl\/?page_id=6694","og_locale":"pl_PL","og_type":"article","og_title":"Case Study & Projects Portfolio - PROSKILLED","og_description":"[vc_row][vc_column][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text css=””] Complex systems. Clear requirements. Solutions ready for delivery. More than 20 years of working at the intersection of business and technology have taught me that technology itself is rarely the biggest challenge in complex projects. The real challenge is translating the needs of multiple stakeholders, existing systems, regulatory constraints and integration dependencies into […]","og_url":"https:\/\/bulletpc.pl\/?page_id=6694","og_site_name":"PROSKILLED","article_modified_time":"2026-08-11T22:03:54+00:00","twitter_card":"summary_large_image","twitter_misc":{"Szacowany czas czytania":"20 minut"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/bulletpc.pl\/?page_id=6694","url":"https:\/\/bulletpc.pl\/?page_id=6694","name":"Case Study & Projects Portfolio - PROSKILLED","isPartOf":{"@id":"https:\/\/bulletpc.pl\/#website"},"datePublished":"2022-08-16T20:13:14+00:00","dateModified":"2026-08-11T22:03:54+00:00","breadcrumb":{"@id":"https:\/\/bulletpc.pl\/?page_id=6694#breadcrumb"},"inLanguage":"pl-PL","potentialAction":[{"@type":"ReadAction","target":["https:\/\/bulletpc.pl\/?page_id=6694"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/bulletpc.pl\/?page_id=6694#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Strona g\u0142\u00f3wna","item":"https:\/\/bulletpc.pl\/"},{"@type":"ListItem","position":2,"name":"Case Study & Projects Portfolio"}]},{"@type":"WebSite","@id":"https:\/\/bulletpc.pl\/#website","url":"https:\/\/bulletpc.pl\/","name":"PROSKILLED","description":"Senior Business System Analyst","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/bulletpc.pl\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"pl-PL"}]}},"_links":{"self":[{"href":"https:\/\/bulletpc.pl\/index.php?rest_route=\/wp\/v2\/pages\/6694","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/bulletpc.pl\/index.php?rest_route=\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/bulletpc.pl\/index.php?rest_route=\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/bulletpc.pl\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/bulletpc.pl\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=6694"}],"version-history":[{"count":53,"href":"https:\/\/bulletpc.pl\/index.php?rest_route=\/wp\/v2\/pages\/6694\/revisions"}],"predecessor-version":[{"id":6811,"href":"https:\/\/bulletpc.pl\/index.php?rest_route=\/wp\/v2\/pages\/6694\/revisions\/6811"}],"wp:attachment":[{"href":"https:\/\/bulletpc.pl\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=6694"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}