We’re moving to East Nashville, and we wanted to make it simple for visitors to download our new contact information. Since most of our visitors are App-savvy mobile phone users, we decided to add a mobile tag to the FireSign digital signage displays in our lobby.

What is a Mobile Tag? Mobile tags, also called QR barcodes, use your camera phone (or other mobile device) to capture and decode data embedded in two-dimensional barcodes. The data in these barcodes may instruct your phone to launch a web site, place a phone call, or in our case, download contact information.

Here is a snapshot of the message we created for the FireSign digital signage in our current lobby:

Use this close-up of our mobile tag to see how the technology works. Just download the mobile app by visiting http://gettag.mobi, snap a picture of the barcode and voila! You now have complete contact information for our new location.

In a future blog post, we will share more information on how to create your own mobile tags. But for now… we should get back to packing.

Adding new images to your digital signage is a great way to keep your messages fresh and relevant. Several online sources make it easy to update images, icons and even video elements with royalty-free stock at very affordable prices (many between $1 and $20). However, there are a couple of points to consider before purchasing your first image.

1. Make sure the graphic image is consistent with your overall brand image and messaging. This is a very subjective process, and you will have to rely on your own judgment as to which visual elements work together. One suggestion is to look for an artist with a portfolio of related images.

2. Remember that pixels count. Purchase the correct file size to make certain your brand message stays in focus. Start by determining the resolution of your monitor. The quickest way to do this is to check your “Player Format” from within FireSign Studio. From the home screen, click the “Where” circle. This selection will give you a list of your active Players and their formats. A typical format is 1360 x 768 which denotes the pixel dimensions of your screen. (This dimension should also be reflected in the format of the segments you have been creating.) With this information, you can now calculate the minimum pixel dimensions based on the the screen area you want to cover. Here is a simple example:

Independent schools continue to find innovative ways to communicate their brand image and value. As a WhippleHill Ecosystem partner, FireSign strengthens a school’s overall brand strategy by bringing online and offline communications into the hallways of the school. Download FireSign’s breakout presentation from the 2009 WhippleHill User Conference for an overview of FireSign applications and installations in the educational environment.

FireSign WhippleHill UC Presentation

The Segment Workflow feature in FireSign 3.3 facilitates the creation and approval of digital signage messaging prior to public display.

The basic workflow process follows these steps:
• A content author creates a new message segment then requests approval.
• An editor reviews the segment and either requests revisions or marks the segment as approved.
• Once the segment is approved, it can no longer be changed and it may be scheduled to play by either the author or the editor.

Setting up Projects and Users

A user with FireSign Server access must first enable the Workflow process for each project.

Workflow Enabled

Next, the server administrator must define the creation and approval hierarchy by configuring the user rights on the User Detail Screen. An author has permission to “Alter Segments,” while an editor has the ability to “Approve Segments.” In scenarios where you may have more than one user with approval authority, segments will only need to be approved by one such user.

Admin Rights

Using the Workflow Feature

With your permissions in place, a content author is now able to create a new message segment in FireSign Studio. The status of the segment is shown as “In Production.” Once the author believes the segment to be complete, he or she may “Request Approval.” A dialog box appears with the title “Submit Request for Approval.” Any editors for this project are listed below the comments field with the option to include them in the approval process.

Approval Request

The editors chosen in the dialog will receive an email requesting approval for the segment. At this stage, the segment can no longer be edited using FireSign Layout, and the segment status is changed to “Pending Approval.”

Next, an editor must now log into FireSign Studio, and find the Segment Detail screen for the target segment. The editor has two choices at this point. They can (1) approve the segment or (2) send it back to the author for further revisions.

By clicking “Needs Revision,” the status of the segment reverts back to “In Production,” and the segment may be edited once again. A notification email is sent to the author along with any comments from the editor.

When the editor clicks “Mark As Approved,” the status of the segment changes to “Approved.” A confirmation email is sent to the author, and the segment can now be used in a schedule.

Pending Approval

By enabling the Workflow feature, you add a powerful tool for keeping your messaging and branding consistent while allowing multiple users to create content for your FireSign digital signage system.

FireSign.net Showcases the First Step Towards the Company’s Next Generation of Digital Signage Software

NASHVILLE, TN. June 4, 2009 – Anode Inc. has unveiled a newly redesigned web site for the company’s FireSign digital signage software product. FireSign.net features expanded content for both technical and marketing professionals who want to deliver the right message to the right audience at the right time.  A key feature of the new site is a streaming media micro site (FireSignApplications.com) focusing on the system’s interactive capabilities.

“One of the key requirements of the new site was to provide updated information on how FireSign can be used to transform passive signage into interactive experiences,” noted Chris Lee, Vice President of Technology.  “The future of digital signage is about more than just hanging flat-panel displays on walls, and we feel this new site better communicates how FireSign can enhance the visitor experience and integrate with the overall communication strategy of our clients.”

First introduced in 2000, FireSign is the company’s proprietary digital signage platform for communicating and interacting with audiences in public spaces.  From its first installation at Colonial Williamsburg, FireSign has established a national presence.  FireSign is found in schools, libraries, transportation centers, corporations and museums.

“As a creative communications studio, we are in a unique position to offer FireSign as a digital messaging platform for our clients,” commented Richard Bess, Vice President of Sales and Marketing.  “We know how to apply technology, and we know how to create messages that educate, motivate and entertain visitors in a variety of industries.”

The updated FireSign web site gives the company a new platform for sharing examples of how FireSign is being used to attract new customers, drive revenue and reduce costs. Meanwhile, Anode continues to explore new screen-based technologies while preparing the next version of FireSign for release in 2010.  Access new the FireSign Web site at FireSign.net.

About Anode
Located in Nashville, Tennessee, Anode Inc. is a visual communications studio where brand experiences are engineered in print and interactive media. For more than 18 years, Anode has been creating award-winning designs for corporations and cultural institutions. Anode developed its proprietary FireSign™ digital signage platform to deliver meaningful communications in public spaces.  From concept and installation to custom content and ongoing management, Anode’s FireSign software and services offer end-to-end solutions for enhancing the physical visitor experience.  More information is available at Anode.com and FireSign.net.

Step 1: Create an HTML file that will call the Twitter widget.
Using a text editor, MS Word, Adobe Dreamweaver, Notepad, or other editor of your choice, create a basic HTML skeleton file with these lines:

<!DOCTYPE html PUBLIC “-//W3C//DTD XHTML 1.0 Transitional//EN” “http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd”>

<html xmlns=”http://www.w3.org/1999/xhtml”>

<head>

<meta http-equiv=”Content-Type” content=”text/html; charset=UTF-8″ />

<title>twitter display page</title>

</head>

<body>

</body>

</html>

Step 2: Obtain the code snippet for the Twitter widget.
The code snippet for the widget is obtained from Twitter using your account settings.
Sign in to your twitter account, then go to: http://twitter.com/widgets.

Select “Other” and click “Continue”

Select “Flash Widget” and click “Continue”

Select “Interactive Widget” and click “Continue”

Select a style using the pop-up menu. There are three options.  (Don’t worry about the size option right now. We will adjust that in the next step to fit your FireSign Player screen’s format and pixel dimensions.)

Select and copy the HTML from the box in the web browser.

Go to the HTML page you created in Step 1, and paste this code between the <body> and
</body> tags.

Step 3: Customize the widget code to fit your FireSign Player

Edit the width and height parameters in the widget code to match the width and height of the pixel dimensions for your FireSign Player. See the red text in the code block below. For instance, your Player format might be “1360×768 16:9H”. The width is the number before the “x” (1360) and the height is the number after it (768). Do not change anything else.

<object classid=”clsid:d27cdb6e-ae6d-11cf-96b8-444553540000″ codebase=”http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=9,0,124,0″ width=”458″ height=”822″ id=”TwitterWidget” align=”middle”>
<param name=”allowScriptAccess” value=”always” />
<param name=”allowFullScreen” value=”true” />
<param name=”movie” value=”http://static.twitter.com/flash/widgets/profile/TwitterWidget.swf” />
<param name=”quality” value=”high” />
<param name=”bgcolor” value=”#FF6600″ />
<param name=”FlashVars” value=”userID=16436568&styleURL=http://static.twitter.com/flash/widgets/profile/velvetica.xml”>
<embed src=”http://static.twitter.com/flash/widgets/profile/TwitterWidget.swf” quality=”high” bgcolor=”#FF6600″ width=”1360″ height=”768″ name=”TwitterWidget” align=”middle” allowScriptAccess=”sameDomain” allowFullScreen=”true” type=”application/x-shockwave-flash” pluginspage=”http://www.macromedia.com/go/getflashplayer” FlashVars=”userID=16436568&styleURL=http://static.twitter.com/flash/widgets/profile/velvetica.xml”/>
</object>

Save your HTML file, making sure it has the proper .html file extension.

Step 4: Import your HTML file into your Media Library in FireSign Studio
You may want to also create a separate Media group for HTML files, just to keep them organized.

Step 5: Place the HTML file into a Segment
Create and edit a new Segment (or use an existing one) in FireSign Layout.

Place the HTML file into a Scene. Adjust the Scene duration to be 15 seconds or longer – long enough for someone to be able to read all the tweets on the page.

Resize the HTML file in the Scene so that it covers the entire display area.

Save your work, exit Layout, and go back to Studio.

Step 6: Set the Segment to play
Either add the Segment to a Schedule, or assign it as an override to your Player for a quick check.

Now step back and admire your work!