BPA Author


  • About Emile
     
    About Ian
      

    About David
     
    About Stephanie
     

    About Krishnan

December 2014

Sun Mon Tue Wed Thu Fri Sat
  1 2 3 4 5 6
7 8 9 10 11 12 13
14 15 16 17 18 19 20
21 22 23 24 25 26 27
28 29 30 31      

« GBS release Green Button enhancements and EnergyPlus 7 support | Main | Green Building Studio API Part II »

Monday, January 14, 2013

Comments

Feed You can follow this conversation by subscribing to the comment feed for this post.

Tomislav Zigo

Workflow mapping, including value stream mapping is an exercise that requires significant investment in time and resources, especially for those organizations that are hesitant when it comes to committing to R&D. Providing a set of guidelines that can define a potential framework for a novice or even somewhat experienced user would have an enormous benefit from the adoption perspective as well as from the perspective of obtaining consistent simulation results. This is a really great way to start and the only word of caution is to be more process and less application biased.

Respectfully,

TZ

Adam Menter

Thanks for the feedback TZ! I agree with you - it has required a significant investment in time on Stantec's part for them to get as far as they have... and it will take more time to truly integrate it into their practice. I think we're all hoping that sharing this work will provide enough initial legwork for others to undertake similar processes with more confidence (and not have to "re-invent the wheel").

Regarding application vs. process based... I think, for Autodesk, it's a balance. The basic workflow maps described in the beginning of this post are application based, because they're focused on getting students to use our software more strategically. Stantec's map is very process based (doesn't mention applications/tools at all). Because we're a software company that makes the tools/applications, I think we're trying to be firmly grounded in both. We can't be so software-focused that we lose the bigger picture of customer needs/processes. But we have to pay attention to how the tools fit-in so we can: 1) help people use the tools better; 2) work to make the tools better.

The comments to this entry are closed.