Hi,
We have Parts/Products in the PLM, that require additional testing until the product is ready for production. We currently evaluate, what´s the best way to organize these tests. The Aras Project Management feature might be a suitable solution, as it can easily be used to schedule and define certain Activities.
In our case, some of the Activities require additional resources to be completed. These can be special measurement equipment or personal to handle the tests.
Some of these resources are limited and can not be used more than once at the same time (e.g. heat chamber).
I have to admit, that resource planning may not be something, that is typically done by a PLM system. But in our case it would be a helpful feature, as people don´t have to leave the PLM environment for creating and planning new products. Managing tests in the PLM would also help to insure the traceability back to the requirements that are used as basis for the test plans.
Is it currently possible to do some basic resource planning in the current Project Management release? Or are there any other options in Aras available that can be used for this task?
Thanks again!
Angela
Hi Primož,
here some very basic overview about my first draft:
https://github.com/AngelaIp/aras-pm-resource-mgmt (Import package not included at the moment.)
Features:
- Adds additional ItemType for Resource Items
- Multible Resource Items can be linked to Project Activities
- The date range Plan Start – Plan Finish of the Activity is compared with the Used In booking date ranges of the resource (this is probably the best working part of my first draft).
- If Resource is available, an additional booking time is added
- If Resource is not available, an error message is returned
Pitfalls:
- Many various date properties are used in Activities. Which dates shall be used for date range check?
- Current concept requires many additional Methods (e.g. when Activity date changes, when Activity is deleted, …)
- When you open an Activity from a Project, there is no save button. So you have to save the project to do the Resource booking.
- Resource booking times can be changed outside the activity. My current concept of using an own ItemType for Booking times is maybe not the best solution. It requires much additional Methods and Permission settings. Maybe there is a better way to store the values.
- No visualization. Booking time should be visualized by some kind of basic calendar in the Resource.
- …
So, there are a LOT of things to consider. But if we never try, we will never know.
I've definitely learned something already. In English, resource is written with only one s. I consistently ignored that in my sample.
Angela
Hi Primož,
here some very basic overview about my first draft:
https://github.com/AngelaIp/aras-pm-resource-mgmt (Import package not included at the moment.)
Features:
- Adds additional ItemType for Resource Items
- Multible Resource Items can be linked to Project Activities
- The date range Plan Start – Plan Finish of the Activity is compared with the Used In booking date ranges of the resource (this is probably the best working part of my first draft).
- If Resource is available, an additional booking time is added
- If Resource is not available, an error message is returned
Pitfalls:
- Many various date properties are used in Activities. Which dates shall be used for date range check?
- Current concept requires many additional Methods (e.g. when Activity date changes, when Activity is deleted, …)
- When you open an Activity from a Project, there is no save button. So you have to save the project to do the Resource booking.
- Resource booking times can be changed outside the activity. My current concept of using an own ItemType for Booking times is maybe not the best solution. It requires much additional Methods and Permission settings. Maybe there is a better way to store the values.
- No visualization. Booking time should be visualized by some kind of basic calendar in the Resource.
- …
So, there are a LOT of things to consider. But if we never try, we will never know.
I've definitely learned something already. In English, resource is written with only one s. I consistently ignored that in my sample.
Angela
