[ARIS 7.1]
Is there a way to change date format in ARIS? Or it is dependent on the method language?
The default is YY-MM-DD which I would like to change for some date attributes type or if not possible, for all. Not having this makes Project Schedule model not very user friendly. And speaking of this, is there a way to modify schedule grid labels?
Another question which is not related to format is how to maintain actual date? In the actual data attribute group there are some attributes but there a not editable. Some of them a related to interface with MS Project which is no longer available. But anyway is there a standard way to maintain actual dates for a task/project or we should create new user attribute types? In case the latter is the solution then I think attribute based modeling cannot be used as it works only with standard attributes.
Regards
Ivo
Hi Ivo,
nice to see that someone is evaluating the project and program management capabilities in ARIS!
Basically all attributes having the following types can be used:
Position:
- Date
- Point in Time
Dimension:
- Time
- Duration
This includes user defined attributes! They are then shown at the end of the list.
But basically I think the attribute group "Project management attributes" is a good starting point.
Cheers,
Jens
Thank you, Jens! It's good that user attributes can be used.
Yes, ARIS capabilities for project/program management are nice. There are a few things that are either missing or I could find how to go about:
1. Calculated time attributes
It's quite natural to know that is the planned end date of a task. Maintaining for example fixed date + task duration and attribute based modeling for position and dimension based on those attributes would place a task OK how to get the value of the end date?
Of course having the possibility to enter start and end and have duration calculated would be even nicer but I think that's not quite in line with the implemented concept.
2. Implicit connections enabled in rows
As with other similar models I expected to have implicit connection created and objects belonging to a row to move when the row is moved e.g. to when changing the order of row or adding/deleting.
3. Working dependencies
I understand that the intention is not to compete with PM systems but...
4. Ability to change date format and grid labels.
Regards
Ivo
Hi Ivo,
first of all thanks for the comments about what you think is missing or a nice to have!
But I can only comment some of your issues:
- I think if you have a standalone task it would be pretty easy to determine for instance the real end date. But if you also have relationships to other tasks that have an impact on the actual start date and therefore probably also on the end date of this task it's a little bit harder. So you see this issue is related to point 4 (at least if I understand point 4 right).
- :) What do you exactly mean with working dependencies. You can create different predecessor relationships (again this is related to point 1)
Regards,
Jens
Jens,
The use case [p. 1] is quite common I believe:
1. Create a task
2. Maintain start date = "fixed date"
3. Maintain duration = "task duration"
4. Choose work/calendar day for duration = maintain "weekends off"
5. Place calculated end date. And here is the problem - no such attribute or capability to create one. Well, may be by running a macro but that would hardly be a lean solution.
The other use case [p.3 is]
1. Position attribute = earliest start date
2. Create Task 1 and Task to
3. Crate dependency Task 1 "is predecessor of" task 2
4. Maintain "dependacy type" = "At the earliest"
5. Expected result: start date of Task 2 = End date of Task 1 + 1 and position of Task 2 changed accordingly
Another common expectation is position attribute to be related to object, no to model. This way for some tasks it could be fixed date, for others - earliest start date as this is quite often the case.
Regards
Ivo