Beginning in January 2019, I worked with a small R&D team to integrate ShotGrid into our pipeline as seamlessly as possible. At the time, we were in the middle of a production, so it wasn’t practical or possible to fully disconnect our entire system and transition directly to ShotGrid. Instead, we developed a custom solution that would sync information from our in-house system to ShotGrid in real-time.
In order to figure out how we could integrate everything into ShotGrid at roughly the same time, we started by mapping out our current pipeline and detailing how each piece of data was being tracked. Our proprietary system was managing shot and asset creation, edit publishing, and almost anything else that generated files in the pipeline; to integrate ShotGrid, we developed a robust communication script that would sync the two platforms whenever a new version was checked in and rendered. In our updated workflow, all new versions are input into the proprietary system first, and then simultaneously uploaded into ShotGrid. We currently still rely on our proprietary platform for file management, while ShotGrid drives production management, including scheduling, tasks, review, versioning, and data analysis.
We started our first project based out of ShotGrid in August 2019, so integration took about eight months. Our pipeline is built around taking processes out of artist hands and putting them onto machines wherever possible and introducing ShotGrid was integral to managing the influx of data generated by complex productions. We currently are working on projects in Sydney and Vancouver and have upwards of 350 ShotGrid users, but at peak production we will be approaching 500+ user accounts.