How WJCT integrated Sundance Digital’s BXF Gateway
Jun 25, 2008 8:00 AM
Day 3
On the third day, we began generating message examples from the traffic system, stepping through all the appropriate types. This is when we discovered our first snag in the implementation: The satellite record orders were not processing correctly.
WJCT had a specific requirement relating to a legacy practice in naming their receivers and satellite transponders. Up to this point, we had used only the XML fields that are available in the standard BXF code. Debate ensued about whether to use the private data function to solve this particular problem. Various solutions were considered throughout the day without resolution.
Day 4
The fourth day was test day for messaging from automation to traffic and the sensitive routines for automated processing of traffic logs. Here we found another snag — a problem with the Sundance functionality. The Media Prep software version that we installed was configured to only process traffic logs manually instead of the automated routines enabled by BXF. We conducted a conference call with the Sundance development group to discuss setting adjustments, only to find that they were omitted from the current build. Together, we created a timetable to work within and correct this feature.
Meanwhile, we tested the remaining messages, running all tasks through the WJCT Protrack and Sundance Digital systems. Everything else worked as designed. We also tested some alternative configuration options in the gateway to fine-tune them for faster XML file delivery and improved security.
Our developer trained the WJCT engineering staff on configuration and log interpretation. He covered normal operation, how to read error codes and where to find the transaction logs and archived files.
Back in Dallas, the Sundance development team continued working on the missing feature and testing the results.
The developer from Myers headed home with a full notebook and some ideas regarding the satellite messaging issue.
Day 5
With all other issues covered, we installed a fresh version of Media Prep from our developers in Dallas. Only one application required modification. We tested the implementation, and it worked fine.
Finally, we turned the system over to the WJCT staff and covered all remaining operational issues. We demonstrated all the automated messages on the system and pointed out the resultant effects. Everyone watched full runs of the log processing routines.
One of the most interesting and valuable consequences of conducting a beta installation is to learn “what you don’t know”. We were pleased that the process went so smoothly and the technology worked as designed. Discovering a couple of snags is par for the course, but a good working relationship with the staff at the site and careful planning makes those issues more useful and less fatal. We resolved the satellite issue remotely in the week following the installation. We will continue our regular communication with WJCT to uncover new issues and ways to improve our product. Work continues on the SMPTE committees (for recommended practices and version 2 development). These advantageous solutions will certainly find their way into general industry practice.
For more information, visit www.sundancedigital.com and www.smpte.org.
blog comments powered by Disqus
| Want to use this article? Click here for options! |  |
