# T-NEX PPM: project portfolio and resource management

Brief version: 1.1 · 12 September 2026  
Documented functional state: 30 August 2026 · Frontend 0.8.5 / server 15.23.0

T-NEX PPM connects a portfolio overview with individual project planning and line-based resource management. It serves companies and financial institutions that need to coordinate projects using shared capacity, agreed priorities and traceable planning records.

The core distinction is between **requested demand, an approved allowance and a named commitment**. This makes clear whether a plan has people assigned to it or still requires a decision from the line manager.

## Documented functionality

| Area | Supported work |
|---|---|
| Portfolio | Overview, prioritisation and a shared view of costs, dates and resources |
| Project planning | Work breakdown structures, Gantt charts, dependencies, milestones and baselines |
| Resources | Demand by organisational unit, skill and period; requests, allowance approval and named commitments |
| Costs | Non-staff cost planning and staff costs derived from resource planning |
| Collaboration | Tasks, RACI assignments, time recording and role-specific work areas |
| Project control | Planned, committed and actual values; status reports, risks, actions and change requests |
| AI assistance | Drafting or modifying a work breakdown structure with a preview and selective acceptance |

Programme functionality is disabled by default and not yet fully developed in the documented state dated 30 August 2026. A usable programme scope must be demonstrated and agreed separately before commissioning.

## Inputs and outputs

Implementation requires the organisational structure, skills, user assignments, capacity, cost categories and rates. Each project adds objectives, scope, work packages, dates and resource demand. Existing operational work needs to be included in capacity planning so that projects are not planned against the entire theoretical availability of staff.

Outputs include coordinated project plans, visible resource gaps, traceable cost comparisons and status reports. Exporting a status report freezes that reporting state and creates the snapshot used for milestone trend analysis. An unexported draft does not create this snapshot.

## Example: requesting resources

1. The project manager plans internal demand by work package, organisational unit, skill and period.
2. The manager checks the recipients in the preview and submits the request.
3. The line manager checks capacity and competing commitments, then approves an allowance or gives a reason for rejection.
4. Committing named people binds specific capacity to the project.
5. The project manager compares planned demand, commitments and subsequently recorded actual time.

This is a schematic workflow from the functional documentation, not a measured customer outcome. External team members are planned separately and do not trigger internal line approval.

## Roles and professional oversight

The documented roles are administrator, portfolio manager, programme manager, project manager, organisational-unit manager, employee and external user. Available functions depend on the user’s permission profile and the project configuration. A programme role alone does not enable programme functionality. Roles should therefore be checked against actual responsibilities before users are invited.

The work breakdown assistant proposes changes. The project manager reviews the preview, corrects individual elements and accepts selected suggestions. The feature requires a configured AI backend and can be disabled. This does not establish a particular model provider, training exclusion or data-retention period.

## Migration and integration

The documentation covers project-handbook XML, including a separate master-data file, MS Project XML for schedules, and the application’s own export format. For project-handbook imports, the target project, replacement scope and conflicts are reviewed before data is written. Empty source values and deletions can be authoritative within selected areas, so implementation should include a trial with representative data.

Further interfaces are agreed against the actual source system and required data direction. Supporting an import format does not imply continuous synchronisation with every project-management or ERP system.

## Implementation, operation and commercial scope

On-premises deployment is the standard model described in the documentation. The handbook also describes SaaS operating functions. Neither description establishes a specific hosting provider or location.

| To be agreed in the proposal | Specific decisions |
|---|---|
| Functional scope | User groups, project classes, roles, enabled functions and required adaptations |
| Migration | Formats, volume, conflict rules, trial migration and acceptance |
| Installation | Single- or multi-tenant operation, system environment and access model |
| AI | Required functions, provider, data flows and the option to disable features |
| Operation | Responsibility for updates, backups, restoration and monitoring |
| Service and contract | Licence scope, implementation, training, support hours, response commitments and handover |

A complete run from project planning through resource requests to the status report provides a useful acceptance scenario, using professionally reviewed example data.

## Evidence and scope limits

This brief is based on the functional PPM documentation dated 30 August 2026. It describes functionality and workflows. It is not independent certification and does not establish a general availability figure, price commitment or automatic fulfilment of regulatory requirements. The software versions identify the documented state, not a guaranteed current customer release.

T-NEX PPM is the product offering for project portfolio management. The original views shown on the product pages come from the separately presented A5Hub project reference and illustrate documented planning workflows. The offered scope is defined separately for your project.

[PPM for financial institutions](https://t-nex.de/en/institutions/products/ai-project-management/) · [PPM for companies](https://t-nex.de/en/companies/products/project-portfolio-management/)  
Contact: [info@t-nex.de](mailto:info@t-nex.de)