This deliverable provides a comprehensive report of the method and results of the requirements engineering of the RAASCEMAN software system. First, we describe the requirements engineering methodology we followed. This process involved all RAASCEMAN project partners, with on the one hand system architects, who will be responsible for creating (parts of) the RAASCEMAN system and are represented by DFKI, FLM, RPTU, CTU, INTRA, LMS, CEA, and on the other hand users of the RAASCEMAN system represented by pilot case owners CONTI, ASKA, DFKI, RPTU, CTU, FLM. Next, the results of the different phases of the methodology are reported in the following sections, namely the overall needs from the point of view of the RAASCEMAN system users, a translation to use cases and user stories that describe the functionality of the RAASCEMAN system from a high level, followed by requirements of the system. The result of the methodology is a living document of requirement artefacts (use cases, user stories, requirements) that are available throughout the project, and are meant to be tracked, updated, and extended in the remainder of the project.