Commentary

Thomas Claburn
 

If AT&T Ran The Highway System...

If AT&T ran the highway system, things would be different. Only AT&T-approved cars would be allowed on the roads, all of which would be toll roads. Drivers would have to prepay their tolls, based on the estimated number of miles they expected to drive. Those who drove fewer miles than estimated would get no refund; those who drove more would be charged for the overage at a higher rate.

If AT&T ran the highway system, things would be different. Only AT&T-approved cars would be allowed on the roads, all of which would be toll roads.

Drivers would have to prepay their tolls, based on the estimated number of miles they expected to drive. Those who drove fewer miles than estimated would get no refund; those who drove more would be charged for the overage at a higher rate.The AT&T-approved Apple iCar would be limited to a top speed of 30 mph. Sales people in AT&T car showrooms would have no idea how the iCar operated.


More Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Buyers of the iCar would be required to use it for a period of two years or to pay a penalty. In addition to the purchase price of the iCar, buyers would have to pay a one-time activation fee to get the engine to start, not to mention the taxes.

AT&T's roads would feature fluctuating speed limits. In some cases, speed limit reductions would correspond to the traffic on the road; in others, the speed limit would just drop for no apparent reason. Posted speed limits would not correspond with actual ones.

The engines powering AT&T cars would sometimes just stop, depending on the driver's location. No warning about these "dead spots" would be provided.

Many of AT&T's roads would be made of dirt, despite tax credits AT&T received to pave its roads.

AT&T-approved cars would not rely on risky user-operated windows or doors. Entering or exiting the vehicle and raising or lowering the windows would be authorized upon request by a remote AT&T operator.

For the sake of safety, passengers would not be allowed to load unauthorized food content into the vehicle. Adding and removing authorized cargo to and from the vehicle would be allowed, for a fee.

AT&T-approved cars would come equipped with an integrated digital jukebox, complete with a coin slot for easy listening. Input and output connectors would be disabled, for passenger protection.

AT&T would make horn tones available for $3.99. No transfer of music from the car's jukebox to its horn tone storage chip would be allowed.

AT&T's Terms of Operation would specify the kinds of driving allowed on the AT&T highway system. Ride sharing, trailers, off-road driving, picking up hitchhikers, and cruising would all be grounds for license suspension.

Car customization would be allowed only using AT&T-approved colors and accessories.

Driving beyond the coverage of AT&T's highway network would incur roaming charges.

AT&T's road system would report the start point and end point of all trips to the National Security Agency. This information would be used for your protection.

If none of this sounds particularly appealing, don't worry. This is just one possible future of many. AT&T knows enough to stick to its core competency: innovation in telecommunications.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links