Europe has now entered the full exploitation phase of its contribution to the International Space Sta-
tion. The implementation of the operations tasks for the ISS Operations Program has been delegated by
ESA to the Integrated Operations Team (IOT) which, through a single End-to-End Contract, provides
the services necessary to maintain, support and operate the European Elements of the ISS. A continuous
process has been put in place for the collection of lessons-learnt, the denition of the necessary recovery
actions and the control of their implementation, in close-cooperation among the various parties, ESA,
COL-CC, USOCs and the Industrial consortium. After this initial three years cycle, the lessons-learnt
assessment has enabled to highlight the change of attitude embedded in transitioning from Design and
Development to the actual real Operations on-orbit: this leap is particularly evident in the shorter re-
action times, in the
exibility obtained by re-interpreting system performances beyond the design and
qualication boundaries to meet extra-operational needs andso forth. The paper brie
y describes the
IOT organization and relationships with ESA, recalls the TAS-I role in general and in particular for
Columbus operations, gives some hints on the established Lessons Learnt Process, analyzes the challenges
for engineering and operations integration to keep up with on-board activity
ow, focusing in detail on
some notable cases as examples of anomaly management. Moreover, some specic cases will be addressed
as peculiar examples of the change of pace imposed by the on-orbit operations: the WOOV8 blockage
(Columbus TCS internal issue), DMS vital layer failure (Columbus system-wide issue), ETCS loop A
Pump stop (station-wide issue).