E N D
1. Bye-Bye NOLA Michael Hunt
VP, Enterprise Applications
PBS
2. NOLA Network Operations Logging Application
PBS homegrown application
Supports the distribution of schedule information
Supports flow of information to automation
Current generation in operation since 1992
3. Orion v1.0 Web-based application
Supports the collection of program info
Replaced former PDB program database
In operation since 2001
4. NOLA needs to be replaced > Built to support processes in place since the 70s
Its broken!
Cannot support
File-based contribution and distribution
Frame accurate timings
The growing number of versions
BroadView was selected to replace NOLA
Implementation design began in early 2004
Needed time to consider systems supporting stations
Significant effort to future-proof plans
5. Orion v1.0 needs to be upgraded Current version of Orion cannot support
Association between program information and media
Not built to allow for the submission of spots
Not built to allow for the submission of media files
Completing Orion v2.0 development
Will be compatible with BroadView
6. Operational Impacts of Change Guiding Principles
High-level Information Flow
Key Impacts
Program Information Hierarchy
PODS v4 and Reporting
Timeline
7. Guiding Principles In support of external and internal deployment
Reduce duplicative tasks (ie: re-keying, re-creation of reports, etc.)
Automate to minimize the number of hand-offs
Promote clear ownership and accountability for tasks
8. Guiding Principles In support of external and internal deployment
Communicate key concepts and solicit feedback from key stakeholders
Do No Harm
Minimize the initial impacts on producers, distributors, and station operations
9. High-level Information Flow
10. Key Impacts of the Change Positioned to manage the submission of spots
Processes and systems to support ingest
Streamline repacks
Timings will no longer be estimated
Approximate
Technically Evaluated
Timing information will be frame accurate
More detailed rights information
Usage Dates will govern program availability
11. Key Impacts of the Change NOLA subscripts are going away
In their place: Package Types
Other characteristics tracked separately:
Revision Number
CC
SAP
DVI
Aspect Ratio
NOLA Codes will continue to be generated
i.e. Episode-level NOVA 001601
Stations highly dependent
Distributed via PODS v4
Will continue to appear on reports
12. Program Information Hierarchy Mapping What was formerly
13. Hierarchy Example - Clifford
14. Hierarchy Example - Nova
15. Package Types Base
Unedited
Stacked
Stacked Unedited
Embedded Promo
Reinvented Breaks
Pledge
Pledge Event
Short
Spot
16. Packages not Versions
17. PODSv4 and Reporting Stay in your seats!
Detailed Session today at 10:45am
18. Reporting All current NOLA reports will come from BroadView in some form
Program Offers
Schedule Listings Advance Schedule, Alpha List, OPSLOG, Program Lineup and Timings (PLT), and corresponding revisions
Reports will be available from PBS Connect
Key data elements will be indexed and fully searchable
19. PBS Connect PBS Connects program search pages will be reformatted
Data will be more easily found
Streamlined process for publishing pages
20. Timeline Training has started
Extensive testing May and into June
BroadViews current go live is slated for late June 2005
PODS v4 will start producing files at the same time
PODS v2 will continue to produce files in parallel for one week containing day-of-air changes only
21. Questions?