<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://mdotwikiqa.state.mi.us/aashtoware/index.php?action=history&amp;feed=atom&amp;title=Work_Zone_-_Appendix_F</id>
	<title>Work Zone - Appendix F - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://mdotwikiqa.state.mi.us/aashtoware/index.php?action=history&amp;feed=atom&amp;title=Work_Zone_-_Appendix_F"/>
	<link rel="alternate" type="text/html" href="https://mdotwikiqa.state.mi.us/aashtoware/index.php?title=Work_Zone_-_Appendix_F&amp;action=history"/>
	<updated>2026-10-17T14:30:00Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.35.2</generator>
	<entry>
		<id>https://mdotwikiqa.state.mi.us/aashtoware/index.php?title=Work_Zone_-_Appendix_F&amp;diff=392&amp;oldid=prev</id>
		<title>WZcrew: Added content</title>
		<link rel="alternate" type="text/html" href="https://mdotwikiqa.state.mi.us/aashtoware/index.php?title=Work_Zone_-_Appendix_F&amp;diff=392&amp;oldid=prev"/>
		<updated>2022-09-29T17:57:04Z</updated>

		<summary type="html">&lt;p&gt;Added content&lt;/p&gt;
&lt;a href=&quot;https://mdotwikiqa.state.mi.us/aashtoware/index.php?title=Work_Zone_-_Appendix_F&amp;amp;diff=392&amp;amp;oldid=391&quot;&gt;Show changes&lt;/a&gt;</summary>
		<author><name>WZcrew</name></author>
	</entry>
	<entry>
		<id>https://mdotwikiqa.state.mi.us/aashtoware/index.php?title=Work_Zone_-_Appendix_F&amp;diff=391&amp;oldid=prev</id>
		<title>WZcrew: /* Standard Abbreviations */ added content</title>
		<link rel="alternate" type="text/html" href="https://mdotwikiqa.state.mi.us/aashtoware/index.php?title=Work_Zone_-_Appendix_F&amp;diff=391&amp;oldid=prev"/>
		<updated>2022-09-29T17:29:11Z</updated>

		<summary type="html">&lt;p&gt;&lt;span dir=&quot;auto&quot;&gt;&lt;span class=&quot;autocomment&quot;&gt;Standard Abbreviations: &lt;/span&gt; added content&lt;/span&gt;&lt;/p&gt;
&lt;a href=&quot;https://mdotwikiqa.state.mi.us/aashtoware/index.php?title=Work_Zone_-_Appendix_F&amp;amp;diff=391&amp;amp;oldid=390&quot;&gt;Show changes&lt;/a&gt;</summary>
		<author><name>WZcrew</name></author>
	</entry>
	<entry>
		<id>https://mdotwikiqa.state.mi.us/aashtoware/index.php?title=Work_Zone_-_Appendix_F&amp;diff=390&amp;oldid=prev</id>
		<title>WZcrew: added content</title>
		<link rel="alternate" type="text/html" href="https://mdotwikiqa.state.mi.us/aashtoware/index.php?title=Work_Zone_-_Appendix_F&amp;diff=390&amp;oldid=prev"/>
		<updated>2022-09-29T17:08:46Z</updated>

		<summary type="html">&lt;p&gt;added content&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;=Appendix F: Portable Changeable Message Sign Guidelines=&lt;br /&gt;
Portable Changeable Message Signs (PCMS) are used to provide motorists real-time traffic safety and advance guidance information that allows motorists to make an informed decision when approaching a work zone.  This includes scheduled and unscheduled events that significantly impact traffic on the roadways.   &lt;br /&gt;
&lt;br /&gt;
==Application Guidelines for PCMS==&lt;br /&gt;
PCMS provide a variety of functions including: &lt;br /&gt;
* Ramp, lane, and road closures &lt;br /&gt;
* Traffic pattern changes (i.e. temporary crossovers &amp;amp; width restrictions) &lt;br /&gt;
* Moving Work Crews &lt;br /&gt;
* Roadwork Scheduling Advisories  &lt;br /&gt;
* Traffic Management and alternate routing &lt;br /&gt;
* Warning of Adverse Road Conditions &lt;br /&gt;
* Traffic Operations Control &lt;br /&gt;
* Real-time Travel Time Messages &lt;br /&gt;
* Incident Management &lt;br /&gt;
* Safety Messages &lt;br /&gt;
&lt;br /&gt;
==PCMS Applications (ranked in order of importance):==&lt;br /&gt;
===Advance Time Notification===&lt;br /&gt;
* Roadway Closures:  Advance notice message, displayed 7-14 days prior to closure, addresses the temporary closure (short duration) of roadways for planned work i.e. truss or bridge beam installations.   &lt;br /&gt;
* Ramp Closures:  Displaying the message 3-7 days prior to the closure is recommended.  For freeway to freeway or weekend closures on freeways with high recreational/tourist travel, the message should be displayed longer (up to 14 days), and should include two Thursdays prior to closures.  The message should include the start date/time as well as opening of the closure. &lt;br /&gt;
** Lane Closures: Same as Ramp Closures. &lt;br /&gt;
** Planned Maintenance Work:  it is recommended that the message is displayed 714 days prior to the planned work and include the start date/time and estimated completion date. &lt;br /&gt;
&amp;lt;/br&amp;gt;&lt;br /&gt;
The message(s) displayed during the closure/work will differ from those displayed prior to the event. &lt;br /&gt;
&lt;br /&gt;
===Existing Events===&lt;br /&gt;
* Detour/Alternate Routes:  The message should recommend detours/alternate routes during ramp/lane/roadway closures.   &lt;br /&gt;
* Notice of Operations:  Within unusual roadway geometrics, PCMS devices may be used as an advanced warning device in conjunction with static signing for stationary or moving operations.  Hills, curves, and other unusual geometrics obstruct the view of motorists; a PCMS provides an additional notice/warning.  Cancelation and completion of roadwork should also be messaged when applicable.  &lt;br /&gt;
* Work Zone Traffic Backups:  Involves monitoring congestion and backups (real- time).  This is an ideal use for PCMS and requires a stopped traffic advisory system to be added to the project.  Generic traffic backup messages should be avoided as theyis decreases the effectiveness of the stopped traffic advisory system.  Programing a message during peak traffic time frames is allowed, but this message should not remain in place during off peak hours.  &lt;br /&gt;
* Special Event Traffic Conditions:  Unusual vehicle and/or non-motorized traffic patterns generated by sporting or charity events are examples for PCMS use.  PCMS boards shall not be used under ANY circumstances to advertise special events. Messages for special events should be designed such that advertising is not embedded in the message.  The message shall identify traffic conditions and a suggested remedy for those attending the special event and those using the same roadway to pass by the special event location. &lt;br /&gt;
* Real-Time, Travel Time Messages:  Real-time, travel time messages are recommended to be displayed when other, higher priority messages are not available/needed.  This provides useful information on current roadway conditions, providing the motorist with real-time information for informed decision making. &lt;br /&gt;
* Incident Management:  Post roadway or lane closures due to crashes or incidents which cannot be addressed with static signing only. &lt;br /&gt;
* Safety Messages:  If used, messages must be pre-approved by the Work Zone Business Team or a common National Work Zone approved message.  Safety message should rarely be used on PCMS boards for work zones. &lt;br /&gt;
* Traffic Calming:   LIMITED USE of messages to inform motorists of closures are permitted.  Traffic calming messages indicate the reason a lane is closed (if not obvious) or when a lane will be re-opened.  For example, messages notifying of an estimated opening may be displayed during the life of the closure. &lt;br /&gt;
&lt;br /&gt;
===Prohibited Use of PCMS===&lt;br /&gt;
* Replacement of Michigan Manual of Uniform Traffic Control Devices (MMUTCD) required static signing or pavement markings. &lt;br /&gt;
* Advertising of any kind. &lt;br /&gt;
* No animation or rapid flashing symbols, pictures, or text. &lt;br /&gt;
* Lighted arrow replacement. (Exception: May allow static chevrons or a static arrow to provide additional direction on a detour route). &lt;br /&gt;
&lt;br /&gt;
==Message Objective==&lt;br /&gt;
PCMS boards should clearly identify what is happening within the work zone area.  It should provide useful, actionable information to the motorist.  Vague or generic messaging should not be used.   &lt;br /&gt;
&lt;br /&gt;
PCMS boards should clearly state the objective of the message by considering the following: &lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+ &lt;br /&gt;
|-&lt;br /&gt;
! Question !! Example Message&lt;br /&gt;
|-&lt;br /&gt;
| What is ahead? || (LEFT/RIGHT LANE CLOSED AHEAD)&lt;br /&gt;
|-&lt;br /&gt;
| How far away? || (XX MILES AHEAD)&lt;br /&gt;
|-&lt;br /&gt;
| Where? || (WOODWARD TO MOUND)&lt;br /&gt;
|-&lt;br /&gt;
| When? || (STARTS FRIDAY 8AM-9PM)&lt;br /&gt;
|-&lt;br /&gt;
| Directions advised? || (FOLLOW DETOUR)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The message should be designed to display the most important information, in as condensed a manner as possible, to meet the requirements of message timing. &lt;br /&gt;
&lt;br /&gt;
===PCMS Messaging Guidance===&lt;br /&gt;
Drivers must be able to see, read, and comprehend the message on a PCMS.  It is essential that messages are clear, concise, and easily comprehended by the general public.  &lt;br /&gt;
&lt;br /&gt;
It is also important to properly describe the roadwork or incident location based on the expected audience.  The public should believe that PCMS boards contain important, useful, and accurate information, so they read every message, every time.  Providing inaccurate, confusing, non-priority messages reduces motorist interest, increasing risk factors, and ultimately leading to a loss of credibility. &lt;br /&gt;
&lt;br /&gt;
PCMS must provide an 18-inch character height, with a maximum eight characters per line and three lines of text.  Commuters are typically familiar with street names; however, tourists are not.  Route Numbers should be used whenever possible. (Ex.  M-24, US-23, I-696).  When providing dates, use words for numbers whenever possible, because they are easier to read and comprehend.  For example, use the format “NOV 24” instead of “11/24/11”.  Also, when possible, use days instead of dates for upcoming construction.  “SAT-SUN” is easier to understand than “4/13 – 4/14.” &lt;br /&gt;
&lt;br /&gt;
===Full Matrix LED PCMS BOARDS===&lt;br /&gt;
NTCIP-Compliant, Full-Matrix Portable Changeable Message Boards may be used on projects as approved by each Region. Projects that may warrant the use of these pay items include locations where messages may require more than eight characters per line (with a 10-character maximum), on projects utilizing real-time travel time messages and unique messaging situations as determined appropriate. &lt;br /&gt;
&lt;br /&gt;
===Prohibited Messaging===&lt;br /&gt;
The below messages do not provide the public with any guidance as it relates to an upcoming work zone and should not be used unless they meet the exceptions. &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+ &lt;br /&gt;
|-&lt;br /&gt;
! Prohibited Messaging !! Exceptions&lt;br /&gt;
|-&lt;br /&gt;
| ONGOING ROAD WORK || None&lt;br /&gt;
|-&lt;br /&gt;
| DRIVE WITH CAUTION&amp;lt;/br&amp;gt;or&amp;lt;/br&amp;gt;EXPECT DELAYS || Crash, Incident, or Emergency&lt;br /&gt;
|-&lt;br /&gt;
| WATCH FOR BACKUPS || Stop Traffic Advisory and Temporary Portable Rumble Strip Projects&lt;br /&gt;
|-&lt;br /&gt;
| WORKZONE SPEED LIMIT STRICTLY ENFORCED|| Project is patrolled 24/7&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===PCMS Not in Use &amp;amp; Storage===&lt;br /&gt;
When PCMS is not needed for a message as contained in these guidelines, it must be turned off and removed from the road side, as indicated in the Standard Specifications for Construction.  PCMS boards must never be turned sideways and stored on the shoulder or edge of roadway. &lt;br /&gt;
&lt;br /&gt;
If during construction the message board is in an area that has limited access or may be used at a later date in the same location, 4 stars (*) may be placed in a flashing mode, with the first screen having the upper right and lower left stars (*) and the second screen having the lower right upper left stars (*).  This notifies the public that the board is working, but no message is being conveyed to them. &lt;br /&gt;
&lt;br /&gt;
==PCMS Location==&lt;br /&gt;
PCMS should be visible from at least 1/2 mile under both daytime and nighttime conditions.  Placement in advance of the work zone or incident should take into account the following factors: &lt;br /&gt;
* Where used for route diversion, PCMS should be placed far enough in advance to allow traffic ample opportunity to exit the affected roadway. &lt;br /&gt;
* PCMS are normally placed on a level shoulder of the roadway, perpendicular to traffic.  If practical, placement further from the traveled lane is suggested. &lt;br /&gt;
* PCMS boards are typically located in remote locations, not easily accessed and far from a contractor's office.   NTCIP PCMS boards are highly recommended for these areas. &lt;br /&gt;
* Delineate PCMS as described in the standard specifications. &lt;br /&gt;
* PCMS Boards must be locked at all times. &lt;br /&gt;
* PCMS Boards should not be located within 1000 ft. of an existing Digital Message Sign Board (DMS). &lt;br /&gt;
* PCMS Board locations should be detailed in construction plan sheets.  When no plan sheets exist, the boards should be located by TSC staff prior to project startup. &lt;br /&gt;
* PCMS boards must be maintained at all times.  This includes areas of dirt and dust and during the winter months, ensuring the dimming lens is free of debris, snow, and salt spray. &lt;br /&gt;
&lt;br /&gt;
===Temporary Rumble Strip PCMS Placement===&lt;br /&gt;
PCMS boards may be used in conjunction with temporary rumble strips on a project.  The boards should be placed a minimum of 500 ft. after a set of rumble strips to allow the driver time to read and comprehend the message. &lt;br /&gt;
&lt;br /&gt;
===Stop Traffic Advisory PCMS Placement===&lt;br /&gt;
PCMS boards should be placed on both sides of the roadway.  Boards should be staggered approximately 1000 ft. apart to ensure the flash rate is not distracting to motorists.  Depending upon the determined length of backup and the amount of PCMS boards placed on the project, boards should be placed every 0.5-1.0 mile apart in advance of the lane closure taper.  &lt;br /&gt;
&lt;br /&gt;
==Message Timing==&lt;br /&gt;
Sequencing messages are typically used when situations dictate the need for more messages than what can be displayed at one time on a PCMS.  The cycle time and duration of the message is related to the operating speed of the highway.  All message sequences should consist of a maximum of two messages and with a two-second minimum display time for each message.  If additional sequences are needed, a second PCMS should be placed on the same side of the roadway, separated by at least 1000 ft. &lt;br /&gt;
&lt;br /&gt;
==Incident Management==&lt;br /&gt;
Incident management messaging should reference the MDOT Dynamic Message Sign Guidelines.  Questions / examples of incident messaging provided below. &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+ &lt;br /&gt;
|-&lt;br /&gt;
! Questions !! Example Message&lt;br /&gt;
|-&lt;br /&gt;
| What Happened? || (CRASH)&lt;br /&gt;
|-&lt;br /&gt;
| Where? || (AT LIVERNOIS)&lt;br /&gt;
|-&lt;br /&gt;
| What is the effect? || (LEFT LANE BLOCKED)&lt;br /&gt;
|-&lt;br /&gt;
| Who is affected? || (THRU TRAFFIC)&lt;br /&gt;
|-&lt;br /&gt;
| What is advised? || (EXPECT DELAYS)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Abbreviations==&lt;br /&gt;
Due to limitations of PCMS size or the message length, it is sometimes necessary to abbreviate words.   The use of abbreviations however, should be minimized.   The following are nationally recognized abbreviations for frequently used words: &lt;br /&gt;
&lt;br /&gt;
===Standard Abbreviations===&lt;br /&gt;
&amp;lt;center&amp;gt;&lt;br /&gt;
&amp;lt;div style=display:inline-table&amp;gt;&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&amp;lt;!-- style=&amp;quot;display: inline-table; margin-right: 50px;&amp;quot; --&amp;gt;&lt;br /&gt;
|+ Table 1&lt;br /&gt;
|-&lt;br /&gt;
! Header text !! Header text&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;div style=display:inline-table&amp;gt;&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; &amp;lt;!-- style=&amp;quot;display: inline-table; margin-left: 50px;&amp;quot; --&amp;gt;&lt;br /&gt;
|+ Caption text&lt;br /&gt;
|-&lt;br /&gt;
! Header text !! Header text&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|-&lt;br /&gt;
| Example || Example&lt;br /&gt;
|}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/center&amp;gt;&lt;/div&gt;</summary>
		<author><name>WZcrew</name></author>
	</entry>
</feed>