IT Project Manager.

Appendix 1: Project Description / Description of Services

Project / Scope of Services

Project: AS PRO Architecture 2030+
Project Type: IT Project

Billing Method:
☒ Independent professional services (billing based on effort / Time & Material)
☐ Independent contractual services (fixed price)

Client Contact: Tayfun Arisoy

Potential Customers of the Client:
N/A

Agreed Project Location:
Predominantly remote, onsite if required

Project Organization

Client / Project Team / Escalation Levels

• Tayfun Arisoy (AS-CDO-IT)

• Paul Siggenauer (AS-CDO-IT)

• Thomas Müller (Head of AS-CDO-IT)

• Franziska Köhler (CDO)

• Additional IT stakeholders

• Steering Committee participants

Project Duration

Planned Start: ASAP
Planned End: December 31, 2026

Capacity: 3 days per week / 24 hours per week

Overall Project Objective & Requirements

For the “AS PRO Architecture 2030+” project, we are looking for an experienced IT Project Manager.

By the end of 2026, the program is to be established in terms of both content and methodology. This includes, among other things:

• Defining the project organization

• Prioritizing the requirements that have already been defined

• Translating the requirements into implementation areas

• Structuring work packages

• Developing the overall program timeline, including milestones and dependencies

• Planning the budget for subsequent years

The tasks will be carried out in close coordination with the relevant IT and business stakeholders.

AS PRO is a business-critical core system of the Mobility Division and is to be specifically developed further as part of the “AS PRO Architecture 2030+” project to meet future business, regulatory, and technical requirements.

The basis for this work consists of the consolidated requirements for AS PRO “future” 2030+, as well as the findings from the external architecture review. The review particularly recommends the gradual verticalization of the system, decoupling of functional components, and opening up the system through clearly defined interfaces.

The objective is not a big-bang redevelopment, but rather a controlled modernization carried out alongside ongoing operations. This approach aims to preserve the value of the existing functional capabilities while simultaneously improving maintainability, scalability, integration capabilities, and release readiness.

Sub-Objectives and Deliverables



Potential Milestones

Milestones: TBD

Agreed Deadlines and Appointments / Cancellation Arrangements

To be defined as part of the project planning.

Description of Independent Services

Project Management in accordance with IT-PEX, including:

• Managing the responsible business-area stakeholders, IT development partners, and internal and external IT service providers

• Ensuring compliance with the TÜV SÜD IT project model, including defined roles and processes

• Preparing and continuously maintaining the project plan in coordination with the project team and service providers, including the project proposal/application

• Planning, managing, and monitoring timelines, costs, quality, and achievement of objectives

• Procuring suitable resources and requesting/obtaining resource commitments

• Coordinating, leading, and motivating the project team

• Cross-functional and cross-departmental cooperation with process partners from IT and Business across the entire Group

• Taking an end-to-end view of the customer journey and business process

• Independently preparing and conducting Steering Committee meetings

• Stakeholder management, including the involvement of business departments, IT development, application ownership, and internal/external service providers

• Ensuring clear, audience-appropriate communication and strong operational coordination among the key project participants

• Continuous implementation controlling, including tracking of actions, risks, dependencies, decisions, and escalations

• Active stakeholder management, including identification, involvement, and ongoing coordination with relevant contacts from the business, IT development, application ownership, and internal/external service providers

• Ensuring clear and target-group-oriented communication as well as strong operational coordination between development, business departments, application ownership, and the project organization

• Continuous implementation monitoring and controlling, including tracking of actions, progress, risks, dependencies, and outstanding decisions, as well as initiating appropriate management and escalation measures

Other Relevant Information

N/A

Agreed Acceptance Criteria

See “Description of Independent Services.”

Agreement on Documentation of Results

Project documentation in MS Teams, and where applicable, Azure DevOps.

Agreed Frequency of Coordination / Coordination with the Customer

At least once a week.

Appendices

Specifications, descriptions, plans, etc.