How reliable are your technical systems in the Church? Before you laugh, consider the embarrassment your senior pastor would feel if everything went off during the middle of a sermon. (I’ve seen this happen, and at the early service, too!) Perhaps we need to think a bit about reliability after all.

In the commercial realm, reliability is measured by the number of Nines. That is, there will be a contract, say with a web hosting firm, that specifies the Service Level Availability in terms of percentage of guaranteed uptime. Here’s a table to help you better appreciate this:

So, if I am guaranteed that my system is up 99% of the time, that means it will be down at most 4 days over the course of a year. If I am guaranteed 99.999% of the time (5 Nines), that means that it will be down at most 5 minutes in a year. If I managed to get to 7 Nines – i.e. 99.99999% of the time – I am guaranteed that the system will at most be down 3 seconds in a year! Believe it or not, the technology is capable of that, but it gets very expensive!

Fortunately, the Church doesn’t need 7 Nines reliability, but your preacher probably expects 6 Nines, and your congregation will start getting anxious at anything less. So what do you do? Start by making an assessment of which systems are required for worship to proceed. For example, if the electricity totally fails, do you go on with no systems working, or jump to the closing prayer. If you had a UPS on everything in the tech closet, then you could continue without main power. Now think through scenarios where each of those systems goes down. What would you do? Is there an alternative that you could quickly deploy? How would you expect the staff to respond? Thinking ahead can go a long ways towards avoiding panic and dealing with the event effectively. And that ultimately will allow worship to go on. You may be wishing that the “rocks will sing out” in the closing song. Maybe they will!

With the emphasis these days on web 2.0, there are new opportunities for the Church. What if we used the web to create dialogue groups following worship? The congregation could join these groups and participate in a dialogue during the week after the worship service. These groups would focus on the sermon, discussing it together. A moderator would be needed to help keep the group on track. The preacher could participate if so inclined. The purpose of the group would be to reflect on and let the sermon sink in. It would not be an opportunity to put down the preacher or reject his message. The opportunity for people to deepen their faith is great. Would this work in your Church?

The technology for this already exists. It could be implemented as a blog or web log, whereby members could sign in and write their comments on each sermon. The main posting could be a summary of the sermon. By limiting comments to existing members and moderating the discussion, the spammers would be limited. It would also be helpful to come up with rules of etiquette for these discussion groups. The moderator could be a staff member if appropriate. The time frame for the comments would be the week after the sermon was preached. That would put a time box on the discussion, since a new sermon will come along after a week. The preacher could read these comments and gather feedback on the sermon that would take a 100 phone calls to elicit. So this becomes a win-win situation.

Many churches are now capturing the worship services for later playback on their web site. The technology to do this is readily available. People can even playback the service on their video enabled cell phone. Or they can play the service back on an iPod – i.e. in audio or video mode. Or they can play back the service on their computer over a broadband connection. Or they could receive a DVD of the service via mail or home delivery. Or they could just read the sermon online.

The technical demands of these processes are enormous. It takes a lot of hard disk space to record and process the service. And it takes a broadband connection to upload it to the web server. And the web server has to be capable of handling streaming media. A good rule of thumb is as follows for capturing video live:

For every 5 minutes of video (DV), you will be using up 1GB of hard drive space.

That implies that a one hour service will occupy 12 GB of hard disk space. If you just record the sermon, then you can cut that in half – i.e. 30 min or 6 GB. But this is still a huge load on system resources. Since you want to maintain quality, you will want to capture the service at the highest resolution possible – i.e. in these examples, standard resolution or DVD quality. High Definition would be even more. Then, to process and store the service, you will use up intermediate storage – i.e. rendering space for programs like Final Cut Pro. The overall load on hard disk space is enormous.

How do you plan for and manage this load? There are many approaches you can take. One would be to size the hard disks of your video editing system to handle a year’s worth of worship services, using the rule of thumb above. Another would be to use NAS (i.e. Network Attached Storage) technology to store everything except this week’s worship service. You also need to plan for having a web site with sufficient storage and bandwidth to support all of the services you want to have online at any given time. You will need to manage these spaces so that you do not exceed the limitations of the web host system, as that will incur high fees.