Changing date format

Hi,

About second question – these attributes are editable but only by scripts.

 

BR, Alex

 

Hi,

As I’ve understood date/time format depends on system settings (Control panel > regional settings).

 

 

Alex,

I've changed system settings and found no dependency :( .

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

Ivo, if you use Architect 7.1, you are right about date :(

But there is no same problems in Toolset 7.1, sorry

 

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:

1. 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).

4. :) What do you exactly mean with working dependencies. You can create different predecessor relationships (again this is related to point 1)

Regards,

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

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