0

Using Shotgun for asset allocation/tracking...

Norberto 'Beto' Meijome

September 23, 2009 00:50

None

Follow

Hi guys,
We are looking at the issue of tracking + managing assets ( software , hardware, people) over time across projects , and wondering whether this would be something that could be done under Shotgun.

AFAICT, I am able to say "Artist Bob, working on ShotX for ShotY between DateA and DateB, 100%" and have that shown in shotgun. I'd like to be able add to this "using SoftwareC (for all or part of the DateA-DateB period), on workstation9999".

Critical to this is also the ability to say , from DateB, ArtistBob will using this other software license. And from DateC, Workstation9999 actually goes to Jane.

Has anyone implemented this? any suggestions on how to go about it, if at all, within shotgun ?

Thanks in advance for any hints,
Beto

• Facebook
• Twitter
• LinkedIn

3 comments

• 0
  
  Mike Romey October 10, 2009 14:52

  Its totally reasonable to do this.  We do it.  So with SG 10.2 I think.  They introduced Custom Non Project Entities.  We use these non project entities for host machines, render pools, and software audits. Our custom tools use the render pools and host to manage render submissions.  We also we have a software audit tool that is deployed on all our workstation when users login to link a user to a workstation and audit the workstation for software.  Its not to difficult to set up. Keep in mind you will have some limitations.  If you follow the list people have requested custom entity fields to link one filed to many.  This is a pivital feature when dealing with non pproject entities.  I am constantly struggling to deploy our tools the way we think they should be built with this deficincy.  Regardless, its totally doable, and a great way to help the IT department and Scheduling department.  Our IT department likes it becuase they can monitor who haas what and make to-do-list quickly. And our scheduling department can use it when they have new artist coming on board and need to sit them at a specified desk.  I would say the hardest part about setting up a system like this is getting everyone on board and forcing them to give up those pesky excel files and host tables. 

   

  -Romey

• 0
  
  Norberto 'Beto' Meijome October 11, 2009 21:52

  Thanks for the insights, Romey - we are looking into doing something similar ...will probably send some feedback when we get around to trying it .

   

  cheers,

  B

• 0
  
  KP March 14, 2010 23:20

  With the addition of being able to add your own custom multi-entity fields on an entity, you can then also store information on the join fields so you can track information about the instance of something (we also call these connection entities). I don't know about how you have approached this but with this ability you should be able to get the information you need.