jsnosal - Monday, January 7, 2013 3:19 PM:
I saw in the code for the Impact Matrix that it looks for the Item Type Documents. How do I get the ECO Impact Matrix to search for Documents? I also saw it mentioned in this presentation from 2010. Thanks for your help.
www.aras.com/.../11-ACE-2010-Aras-Configuration-and-Change-Management.pdf
Josh
RobMcAveney - Tuesday, January 29, 2013 3:00 PM:
Aras is working on adding standard support for Documents in the Impact Matrix. There's a bit more to it than just allowing for search. You have to account for Documents in the other part of the Express ECO change process as well. Documents also tend to have their own review cycles, as opposed to Part/BOM changes, which can be reviewed directly in the Impact Matrix UI. You'll start to see some of these changes in upcoming releases, but if you're comfortable with the code you're welcome to give it a try in advance of the release.
Rob
jsnosal - Tuesday, January 29, 2013 4:12 PM:
Rob,
Thank you for your reply. Your just the guy I was looking for. In your presentation from 2010 for the ARAS community event. On slide 14 you have a picture of an ECN. Are those only documents that you have in the impact matrix or is that a mix of parts and documents?
I understand that documents and parts/BOMs have different review cycles. At the same time it would be nice to be able to show any documents that might be affected by the change to the part or BOM. The Impact Matrix is a powerful tool and I look forward to next release.
www.aras.com/.../11-ACE-2010-Aras-Configuration-and-Change-Management.pdf
Josh
RobMcAveney - Tuesday, January 29, 2013 7:24 PM:
Josh -
You are correct that those are Documents on the screenshot you referenced. That was an early prototype of the Impact Matrix that had support for Documents, but lacked some other features (and stability/performance). We hope to add Documents and other items to the released version soon. The intent is to eventually be able to spawn a DCO with its own workflow for each Document on the Impact Matrix (grouping of multiple docs on one DCO is an option as well). The ECO would not close until all DCOs made it through their cycles.
Does this approach fit with what you're trying to do? If so, do you have any interest in helping us develop the requirements and/or sponsoring the project? We can get things done a lot faster when there is subscriber momentum pushing us.
Rob
dennis - Wednesday, January 30, 2013 7:47 AM:
Hi Rob,
I'm just curious if you are also considering an approach where the documents do not get approved on a DCO but instead get approved on the ECO with the part?
Dennis
RobMcAveney - Wednesday, January 30, 2013 4:13 PM:
Hi Dennis -
That is an option as well, and we certainly plan to be flexible. The downside to approving documents on the ECO is that they either all have to have the same reviewer list or we have to do some dynamic assignment magic to get the right docs to the right reviewers. Spawning DCOs in an automated fashion solves that problem and a couple others. We do plan to keep the overhead of using DCOs to a minimum.
Rob
