NRT how to prepare by acox

IS YOUR STATION READY FOR NON-REAL-TIME PROGRAM DELIVERY? How to conduct assessments of workflow and storage systems to prepare for the delivery of the NGIS-NRT System.

As PBS begins a nationwide rollout of digital program distribution via the NRT system, stations will need to evaluate their internal processes and infrastructure to be ready.

The transition to Non-Real-Time may mean revising certain processes in the management of program files at your station. !

If your station is using a file-based system: • There will be minor changes to your workflow in the areas of Traffic and Master Control. • There may be changes to your file storage systems used for Broadcast Playout and Archiving.

If your station is NOT YET using servers, digital archives or automation systems, this is the opportunity to make significant changes in your local workflow and operations configuration to move toward adopting a file-based system.

This guide will help you assess the storage needs at your station, based on the expanded volume of program files that will be distributed using NRT program delivery and will review changes to your program preparation and file distribution workflow that may be needed to make the best use of NRT program delivery.

ELEMENTS TO REVIEW IN YOUR STATION’S OPERATIONS Workflow Changes for NRT

Storage Changes for NRT

Assessing any changes needed in your broadcast workflow will require input from all the departments who plan, schedule and operate your broadcast services.

In terms of storage, the decision-making for NRT file transfers must begin as soon as possible, but there can be a flexible timeline for implementation. You can move toward a file-based system by using NRT as a first step.

In terms of workflow, the decision-making for NRT file transfers must begin as soon as possible, but there can be a flexible timeline for implementation. You can move toward a file-based system by using NRT as a first step.

Assessing any changes needed in your server and storage configuration should be based in large part on: • The size of the files you save — SD program files, HD files, or both • The workflow you adopt for capturing and playing out NRT programs, • Where the program files will be stored, • And for how long.

Based on your own program schedule, you will have to decide which programs will be used from the NRT schedule, and which will continue to be recorded from the Real Time (RT) satellite Interconnection System.

For an extended period, both Real Time (RT) and Non-Real-Time (NRT) will be in place simultaneously.

Basic File Management Operations

There is much greater reliability and higher quality with program files delivered in non-real time, so it is logical that this will become your major source of programming.

Servers and Storage

The basic operations for non-real-time program delivery are similar to satellite distribution, but there are a few important differences. Because of the changes expected with NRT, it is likely you will have to adjust some of your daily operations. For example, do you currently play a lot of programs directly to air, such as a children’s block? These programs will now arrive as files two days before the scheduled airdate on the PBS schedule. They cannot be played directly to air from the NRT File Store, so you, and your Operations staff, must plan a new workflow to manage them appropriately.

Server configuration and storage capacity is critical. How many program files you keep over time and in which formats, will inform your plans for storage and access devices. [More details about storage requirements are available on the NGIS Website.]

For programs you want to archive for future airplay, what workflow do you need to make them available for air and also route them to the archive?

Some questions you might want to consider: • Will they go to the air server or nearline storage from NRT first and then be saved to the archive after the program airs? • Will they be copied from NRT for both the air server and archive at the same time?

Major Considerations for Planning !

Programs will be delivered via satellite as digital files.

Programs will be made available 2 days before the air-date or the release date and they will be available for a total of 10 days.

Like many file transfer operations, program files will have to be downloaded into an appropriate system to store and manage them.

Each file will need a completely unique file name. Using the PBS Package ID is one way to assure there is no confusion. House numbers can also be used, but must be unique for each file.

Through system monitoring, PBS will receive confirmation that programs have been properly delivered to each station.

Each station will manage its own program selections for broadcast, and maintain the interfaces with its own servers, traffic and broadcast systems.

Based on your own use patterns, you will need to determine your own program file storage needs and routing paths.

• Do you want to send them to nearline storage or the archive directly, and then pull them two days later when they are scheduled for air? !

And once the basic NRT workflow is in place, will you be using programs in HD, SD or both? How much storage will you need to keep them available for air or near-line access?

You get the picture. The workflow assessment described here can help you determine how to capture the program files from PBS, and then how to route them for air and other destinations at your station.

Step by Step Planning

Your Broadcast Operations, Engineering and Traffic Departments all need to be involved in planning. !

It is important for everyone involved with program scheduling and traffic to understand the changes in how programs will arrive at your station and any new requirements for getting them to air. Together, the staff should review how decisions are made about which programs will be saved, how the programs will be stored, how much storage will be needed, and who needs to be involved. Once everyone understands the changes, they can assess the impact on your current workflow and outline steps necessary to respond to the needs of NRT program delivery.

Your Traffic System is the main interface. !

The SSP (Station Services Platform) was developed to closely integrate NRT distribution with your local traffic system and existing air servers.

Because of this, the process to select and schedule programs will seem familiar.

You will have to plan file storage and management based on your own current systems.

Are you using files today? Then you already have a digital workflow in place. !

If so, NRT will integrate with your current filemanagement workflow.

Your local workflow might become simplified because of the close integration of NRT with existing station traffic systems.

If not, the NRT team will work with you.

You control how the system is used in your own local operations.

The amount of NRT programming you use can be phased-in over time.

Which programs will you use from NRT, and which from RT? !

Will there be multiple replays? Short term and long term playback? Kids programs that go directly to air?

You now have to decide which programs will come from which source, and how they will be played out.

NRT programs will have to be routed to the appropriate device(s) for airplay and/or storage.

Do you want the HD or the SD version of a program? !

Both an HD version and an SD version are presented through the SSP for a station to use.

You will need to decide which version(s) you are going to use.

One or both versions will have to be copied for playout and/or archiving, with storage requirements determined accordingly.

How many programs do you currently play direct-to-air from the satellite feed, without any station recording? !

Nothing coming through NRT can be played directly to air.

Except for live and near-live programs, file copying will replace recordings. Default operation of NRT is that the file will be copied to the stationâ&#x20AC;&#x2122;s playout server.

Take this into account when you plan your program usage.

What changes in your workflow will assure that the files copied to the playout server will be ready for air? !

Multiple quality checks will be performed before the files are sent, and you should not need a step for QC. However, the decision to QC is yours so a local QC review can be incorporated into your own station workflow.

If you will be editing the file to remove “post logo filler,” you will want to allow for that operation.

Any regular server maintenance done by your Engineering department could affect the timing of when some files are copied out of the NRT System

In the first months of the NRT operation, the system may not run steadily at full capacity, so stations will be able to determine if there is a window of nationwide system downtime available for local server maintenance.

As the NRT operations ramp-up at PBS, files will be delivered almost 24 hours per day. Your Engineering group may need to work with your Traffic department on when to schedule routine maintenance operations in order to be sure you do not miss any files scheduled for transfer. The Traffic systems can designate times when your files arrive, so it is critical that your Traffic staff coordinate with your Engineering group on when maintenance windows can be scheduled.

Where do NRT program files need to be routed? !

Given how you store programs today and the need to store the files that you will use from NRT, will the workflow change the size or type of storage you need?

Will programs be copied to local storage (archive, tapes on shelves, etc.) during the two-day window before air, or will you store them after they air?

Will NRT programs stay on the air server for playout multiple times during the initial rights period, or will you move them to another storage location, such as nearline or off-line? SSP can be set up to copy the file to an archive or nearline storage destination.

The storage capacity you need is based in large part on the volume of files stored ready for playout vs. those that will go into off-line or another storage environment for future use.

You will need to design the most appropriate local systems for making sure files land at their proper inhouse destinations.

Once staff members have reviewed your current workflow and the related changes required by NRT program delivery, you should be able to plan and implement alterations appropriate to your local needs. Final adjustments can be made when the basic NRT operations are in place and have been tested.