Project Management
TINF21C, SWE I Praxisprojekt 2022
Project Handbook (PM)
Project: AAS-Management
Customer: Rentschler & Holder Rotebühlplatz 41 70178 Stuttgart
Supplier: Team 2 (Selvana Dwi Ayunda, Paul Brenner, Jonas Alexander Graubner, Mohaddeseh Tibashi, Luka Dominik Pavic) Rotebühlplatz 41 70178 Stuttgart
Version 0.1
| Version | Date | Author | Comment |
|---|---|---|---|
| 0.1 | 30.10.2022 | Selvana Ayunda | Document created and edited |
| 0.2 | 09.10.2022 | Selvana Ayunda | Gantt Charts update |
CONTENTS
1.Project Order 3
2.Project Kontext 4
3.Project Organization 5
4.Project Structure Plan (PSP) 6
_5._Risks 7
6.Gantt-Charts 8
7.Milestone 9
8.Activities and Responsibilities 10
Goal:
The goal of this project is to develop a web application that acts as a management system for the "Asset Administration Shell" (AAS). This specific web application shall have an identity and access management as well as a user administration with persistent data storage in MongoDB. The user administration enables a role distribution of the users in the user groups "Admin", "Advanced" and "Basic", whereby the role distribution is carried out manually via the Admin. Each role is equipped with different access rights and read permissions ("Advanced" gets full read access to all AAS and their submodels and "Basic" gets read access only to the basic submodels to all AAS), with the admin also having functions for managing AAS content and user management. This uses the specification of the concept as a REST API in openapi.
Product Environtment:
The AAS is a concept of the Industrie 4.0 platform for the standardized implementation of "Industrie 4.0 components", consisting of the digital twin in the form of the AAS and the associated physical object (the asset). This makes it possible in industry to provide digital twins that can be shared and combined across manufacturers and accessed via standardized interfaces.
Initial situation and problem description
A web application for managing the digital twins of the respective Industry 4.0 devices. The administration should be made available via user management with the user groups "Admin", "Advanced" and "Basic" mentioned there.
The web application should communicate with the backend of the AASX server using the REST API to be created. The interface can be designed in such a way that the information of the digital twins can be saved, changed and read out. Depending on the role of the logged in user. This means the application communicates with the backend and presents this information via the web application (a classic MVC application).
The web application is to be created with the REST API. In addition, you should implement a connection to a MongoDB in the backend of the server, in which the digital twins are stored, with all properties (can be implemented relatively "easily" using a REST API to use the web application to manage the digital twins). In addition, the user administration is also placed in the MongoDB. Everything is in one central place.
• _ Financial risk _: It is possible that the project planning is misestimated and the actual number of hours per person is higher than actually planned.
_ Measure: _ The risk is minimized through precise planning of the project. Work packages and time expenditure must be defined.
• _ Planning risk: _ Fixed deadlines cannot be met, which delays the entire process, especially if there are dependencies between the work packages.
_ Measure: _ The project plan must contain sufficient time buffers to absorb delays.
• _ Communication risk _: Lack of or incorrect communication between individual team members.
_ Measure: _ Regular exchange in the team, in the form of calls and proactive communication in the event of uncertainties or problems of individual members
• _ Personal risk: _ Members could leave the company during the project period, or be lost due to limitations such as illness, accidents, etc
_ Measure: _ Sufficient buffer and distribution of tasks among several members. It is not possible to replace the member in the project!
|
