Logged In, Locked Out: When IT Systems Stand in the Way of Our Work
Michael Steffens, Helen Conefrey
USHU is increasingly concerned that the IT systems introduced across EU Delegations are undermining, rather than supporting, the day-to-day management of projects. A fragmented architecture, persistent bugs, permission problems and poorly managed migrations such as the recent move to HIVE place a heavy and avoidable burden on colleagues. Systems are too often designed in and for Headquarters, without enough regard for the realities of Delegations, where connections are slower and IT support is stretched. The result is high transaction costs, long delays and growing stress in an environment where burnout is already a serious concern. USHU calls for user-centred design, proper consultation and clear communication before any new system or migration is rolled out.
Managing EU-funded projects in a Delegation is demanding work. Colleagues prepare, contract, monitor and close interventions, often in difficult security environments, under time pressure, and with limited staff. In such conditions, IT systems should make the work easier. Too often, they do the opposite.
OPSYS: a system that still struggles to support the job
OPSYS, the operational system for launching and managing projects, was meant to modernise and simplify project management. In practice, many colleagues find its user interface unintuitive and its logic difficult to follow. The system has been affected by recurring bugs, and finding the right document can be time-consuming. The “My Workplace” environment shows every project a user has managed over several years, frequently across several Delegations and including closed contracts. Instead of an overview of current work, colleagues face a cluttered list that has to be searched manually.
In addition, OPSYS shows various processes and tasks for each file instead of providing a coherent overview per contract. At the same time, a few years after the introduction of OPSYS, the previous project management platform CRIS is still used for certain types of contracts.
For many routine tasks, completing the work in OPSYS requires one or more tickets to the IT support desk. Colleagues do eventually learn to work with the system, but at considerable cost in time, effort and patience.
A fragmented architecture with no single entry point
The difficulties are compounded by the dispersed nature of the IT architecture. There is no single environment for launching contracts. Service contracts under framework contracts are launched in OPSYS, while open tenders go through PPMT, a corporate Commission platform that follows an entirely different logic. Each system has its own permissions, its own bugs and its own support channels. Colleagues must constantly switch between applications that do not speak to each other.
These problems are amplified in Delegations where internet connections are slow or unstable. Applications that function adequately on Headquarters networks can become extremely slow, or unusable, in the field. Remote access tools that may be convenient in Brussels can be a daily obstacle in a Delegation with limited bandwidth.
HIVE: how not to manage a migration
The recent introduction of HIVE, and the decision to move all files from shared drives to the new platform, illustrates these concerns clearly. One colleague described their experience as follows:
“First there was no message about the introduction of HIVE and the relocation of files. […] Files started being transferred during working hours. My documents on the shared drive disappeared. I could not save the file I was working in, and this all in the middle of our workday. […] Then the files suddenly reappeared as read only on the shared drive.”
Colleagues also report that the training offered was of limited practical value. According to IT staff in Delegations, Regional IT Officers (RITOs) and local IT staff were not involved in the migration, yet they are expected to support users. It is difficult to see how effective support can be provided for a process in which those who provide support were not included.
USHU recognises that IT security is essential. However, security requirements cannot justify decisions taken without understanding how systems operate in Delegations, or without consulting the colleagues who will use and support them. Overall, HIVE does not seem to run smoothly in the Delegation environment – it is slow and reduces the speed of our work significantly.
The human cost: stress, delays and burnout
These issues are not simply technical. Burnout remains a serious problem in EU Delegations, and the daily friction of working with poorly adapted systems adds to it. When a single task requires several helpdesk tickets, when files disappear in the middle of the working day, and when deadlines are missed because a system does not work, the pressure falls on individual colleagues and their teams. Such pressure can also strain working relationships and contribute to tensions in already demanding environments.
The transaction costs of the current IT architecture are high, and the resulting delays are often long and unacceptable. Every hour spent working around a system is an hour not spent on the substance of EU cooperation.
What USHU calls for
USHU calls on the EEAS and the Commission to involve Delegation users, RITOs and local IT staff in the design, testing and roll-out of all new systems and migrations.
USHU requests that migrations be announced clearly and in advance, and scheduled outside working hours, with a tested fallback in case of problems.
USHU calls for a simpler and more coherent contracting environment, and for practical improvements to OPSYS, including a “My Workplace” view limited to current and relevant projects.
USHU asks that systems be tested under the bandwidth conditions of Delegations before deployment.
USHU calls for practical, task-based training and a feedback mechanism through which users can report problems and see them addressed.
USHU requests that the impact of IT systems on workload and well-being be considered as part of the institution’s approach to psychosocial risks.
IT systems should serve the people who use them. They ought to make work easier, rather than the opposite—which is all too often the case. USHU invites all colleagues to share their experiences so that we can continue to address these issues with headquarters, with the goal of improving our working conditions and becoming more "agile" in our day-to-day tasks.




Comments