Minnesota Data Practices Act

Local cell phone spying KingFish stonewall: Minnesota law enforcement at BCA & Hennepin County refuse to disclose SIGINT cell phone snooping capabilities from NSA contractor Harris

kingfish.jpg

It's been dawning on Americans this year that their everyday electronic devices are used by law enforcement for investigations. However the lawmen and the county attorneys are withholding the policy information about the Harris Corporation Kingfish system which is a device that can alter the electronic behavior in a cell phone, also known as a CDMA Interrogator or cell phone interceptor.

The MN Bureau of Criminal Apprehension (BCA) has declined to share any policy information about Kingfish. I have also heard that Hennepin County Sheriffs Office and their legal counsel are putting up rather high barriers to disclosing anything at all about Kingfish. The whole case is weirdly parallel to the 1978 Rockford Files episode House on Willis Avenue, which ended with this unprecedented title card:

rockford-files-willis-ave.pngWe still have "no legal right" to know about who in Minnesota is building dossiers and how. The main question: what is Hennepin County and the BCA hiding in their versions of the House on Willis Avenue?

At the Hennepin County level in the 2010 they earlier promised to come up with sensible and clear policies about if and when law enforcement uses these devices to interfere with cell phones. Now they are claiming that stuff is non-public data - which of course precludes informed public debate at the Legislature in 2014 about electronic law enforcement interference in technical devices.

Several people including Rich Neumeister are looking into this nasty Signals Intelligence (SIGINT) mess. Follow @RichNeumeister - he is helpful answering about the details on this via Twitter.

In a shocking surprise Harris Corporation is a major contractor with the National Security Agency and KingFish is part of the domestic-grade apparatus for local but still unchecked NSA-style electronic snooping. The NSA didn't seem like a big deal when KingFish was approved, but now everyone has finally started noticing the tremendous power of unchecked electronic data collection. It's a much Hotter Potato than in 2012!

See: Sept 2009: Harris Corporation and National Security Agency Announce Certification of First Tactical Radio with Type-1 Suite B Information Security

July 2012: Harris Corporation Receives National Security Agency Certification for Soldier Radio Waveform in Falcon III AN/PRC-117G Multiband Manpack Radio

April 2007: National Security Agency Certifies Harris Corporation's SecNet 54 Top-Secret Capable Secure Wireless LAN Product

September 2004: Harris Corporation Receives NSA Certification for Programmable Cryptographic Module

Wikispaces notes: PIRT - Harris Corporation etc. More Harris links at end.

rockford3.pngAnother angle here: Hundreds of thousands of dollars have gone into KingFish in Minnesota and they are not willing to share the expense information. Ars Technica reports the boxes cost $25K so where the hell is the rest of the money? Meet the machines that steal your phone’s data | Ars Technica:

The Kingfish is a surveillance transceiver that allows authorities to track and mine information from mobile phones over a targeted area. The device does not appear to enable interception of communications; instead, it can covertly gather unique identity codes and show connections between phones and numbers being dialed. It is smaller than the Stingray, black and gray in color, and can be controlled wirelessly by a conventional notebook PC using Bluetooth. You can even conceal it in a discreet-looking briefcase, according to marketing brochures.

First used: Trademark records show that a registration for the Kingfish was filed in August 2001. Its “first use anywhere” is listed in records as December 2003.

Cost: $25,349.

Agencies: Government agencies have spent about $13 million on Kingfish technology since 2006, sometimes as part of what is described in procurement documents as a “vehicular package” deal that includes a Stingray. The US Marshals Service; Secret Service; Bureau of Alcohol, Tobacco, Firearms, and Explosives; Army; Air Force; state cops in Florida; county cops in Maricopa, Arizona; and Special Operations Command have all purchased a Kingfish in recent years.

[…]The code of silence shrouding the above tools, however, is highly contentious. Their use by law enforcement agencies is in a legal gray zone, particularly because interference with communications signals is supposed to be prohibited under the federal Communications Act. In May, an Arizona court ruled that the FBI's use of a Stingray was lawful in a case involving conspiracy, wire fraud, and identity theft. But according to the American Civil Liberties Union (ACLU), when seeking authorization for the use of the Stingray tool, the feds have sometimes unlawfully withheld information from judges about the full scope of its capabilities. This means that judges across the country are potentially authorizing the use of the technology without even knowing what it actually does. [But in MN who needs judges?? LOL]

That's not all. There is another significant issue raised by the Harris spy devices: security. According to Christopher Soghoian, chief technologist at the ACLU, similar covert surveillance technology is being manufactured by a host of companies in other countries like China and Russia. He believes the US government’s “state secrecy” on the subject is putting Americans at risk.

"Our government is sitting on a security flaw that impacts every phone in the country," Soghoian says. "If we don't talk about Stingray-style tools and the flaws that they exploit, we can't defend ourselves against foreign governments and criminals using this equipment, too."

rockford-files.png

Soghoian makes an excellent point - the vulnerabilities exploited by KingFish are in some ways a major public safety threat, and the security establishment is accruing power by hiding the flaws as usual instead of forcing society to deal with the overall crappiness of today's telecom technology.

"Security by obscurity" is the dominant principle of political accountability here, and of course it is doomed to fail. Responsible disclosure of the flaws exploited by KingFish and their granular legal circumstances are what we need, not moar domestic SIGINT fog and mystification.

All of these cell phone attack avenues should be known because similar tech to KingFish would be more widely available soon. The disruption under the federal Communications Act is also relevant.

Some time back I pointed out the problems with MN statutes about these kind of cell interceptor technology at a Senate committee and former Sen. Mee Moua suggested that if I wanted to go fishing for KingFish I might need to find some alternate way. At least these days more people care about this stuff!! [It should be recalled Moua - a Hmong war refugee - was hounded by law enforcement at the tail end of her service. See MPR clip below]

/////

Earlier: March 3 2010: Sheriff Stanek landing Fed cash for KingFish military cellphone tracker in Hennepin County; National Guard intelligence analysts fuse to metro police departments; Lobby for warrantless wiretaps in St. Paul | Twin Cities Indymedia -- March 15 2010: Surprise bill for interstate fusion center data sharing pops up Tuesday; Specs found for Harris StingRay & KingFish cellphone tracking devices | Twin Cities Indymedia

via Rich Neumeister: Open Secrets: An indefensible and odious practice with (Foia-Data Practice) data requests (Oct 15th)

////

Office of the Commissioner

445 Minnesota Street - Suite 1000 - Saint Paul, Minnesota 55101

Phone: 651.201.7160 - Fax: 651.297.5728 - TTY: 651.282.6555

Website: dps.mn.gov

October 3, 2013

Rich Neumeister VIA Electronic Mail

Re: Cell Phone Tracking Data Request

Dear Mr. Neumeister:

Thank you for your data request. You ask "to inspect and review all government data about the cell phone location tool known as the (Kingfish) including, but not limited to, such items as protocols, procedures, legal thresholds, Attorney opinions, evaluations, correspondence, and results of use."

The BCA does possess cellular exploitation equipment; however, we cannot provide details about the equipment because it would compromise ongoing and future criminal investigations including AMBER Alerts, kidnapping cases, fugitive searches and homicides.

In addition, any disclosure regarding the manufacturer, model, capabilities, functionality or other specifics about the equipment could be used by criminals and fugitives to defeat the technology and render the system useless.

As a result, any data regarding this equipment is confidential or protected non-public under Statutes 13.82 Subd. 25 and 13.37 Subd. l (a).

Portions of the data are also trade secret data not subject to dissemination. The contracting company has taken efforts to protect the data from disclosure. As you are aware, a corporation supplying trade secret data to a government entity may claim portions are trade secret. The contractor in this case has appropriately made such a claim as it relates to portions of the data, pursuant to Minn. Statute 13.37 Subd. 1(b).

Again, thank you for your data request. Should you care to discuss it further please contact me.

Sincerely,

E. Joseph Newton

General Counsel

/////

Lol "any disclosure regarding the manufacturer, model, capabilities, functionality or other specifics about the equipment could be used by criminals and fugitives to defeat the technology" - so they are counting on ignorance to succeed in controlling society. A perfectly sound way to invest public Debt-Dollars, counting on perpetual confusion over some metal box's legal & technical specifications. Perhaps this kind of clever spending theory contributed to the federal government shut down - it's not like millions haven't vanished on deficient & wasteful Homeland Security gear :-/

Well then let us take a look at MN Statutes 13.82 Subdivision 25. 13.82, 2013 Minnesota Statutes

"Subd. 25.Deliberative processes. Data that reflect deliberative processes or investigative techniques of law enforcement agencies are confidential data on individuals or protected nonpublic data; provided that information, reports, or memoranda that have been adopted as the final opinion or justification for a decision of a law enforcement agency are public data."

Justification for a decision of a law enforcement agency are public data and that would really seem to include the legal memos about the process for when to fire up Kingfish to poke at cell phones.

here is the 13.37 Subdivision 1 a: 13.37, 2013 Minnesota Statutes

Subdivision 1.Definitions. As used in this section, the following terms have the meanings given them.

(a) "Security information" means government data the disclosure of which the responsible authority determines would be likely to substantially jeopardize the security of information, possessions, individuals or property against theft, tampering, improper use, attempted escape, illegal disclosure, trespass, or physical injury. "Security information" includes crime prevention block maps and lists of volunteers who participate in community crime prevention programs and their home and mailing addresses, telephone numbers, e-mail or other digital addresses, Internet communication services accounts information or similar accounts information, and global positioning system locations.

/////

It seems like this is worded to mean that the "information" would be subjected to "theft, tampering, improper use, attempted escape, illegal disclosure, trespass, or physical injury". "Defeat the technology" is not on that list, and indeed the question of who the technology has been used on remains decidedly open.

Here is Rich's list of questions which is a good starting point: What's behind the secrecy wall of Hennepin Co Sheriff and BCA?

Some of the few questions I am trying to get answered are as follows: In what situations are the cellular exploitation devices used?

Are the BCA/Hennepin Co Sheriff invading people's privacy and liberty at a low legal threshold or no threshold rather than get a search warrant?

Who oversees and approves the use of the equipment? Where is the accountability?

How many innocent people have been within sights of the Kingfish or similar device, the data collected and those subjects of the surveillance who may not even know about it,? How many arrests have happened with the use of this device?

Kip Carver, an official in the Hennepin County Sheriff's office stated to the county's commissioners three years ago that the cellular exploitation device may be used hundreds of times a year.

How frequently are the cellular exploitation devices used and the number of subjects?

Depending if the cops are using a low threshold or none at all in using this device are they doing so to avoid an appearance before a judge where a search warrant (top standard to protect our privacy & liberty) needs to be issued and where questions can be asked?

What is the role of the prosecutors in situations when this equipment is used?

In my data request I asked for the legal thresholds that the agencies must go by in order to use the Kingfish? What is so secret about that?

At this time, the attitude that both agencies have taken with my data requests give the Minnesota Legislature and most important the public no idea how this tool has been used, is being used, how an individual or individuals get chosen to be pursued, and who is accountable.

As some people may currently know I have been working to possibly update our state laws so that the rule of law applies to whats happening now in 2013 not in 1988-1989 when 626A had its last major update.

Even though the Department of Public Safety and the Hennepin County Sheriff do not want to tell me or the public their protocols, policies, procedures of accountability, legal thresholds, and other appropriate public data I will still push on and I hope others will. I am not interested to live in a state where law enforcement rules and not the people.

/////

Story from Feb 9 2010 Star Tribune. You Can LOL about how Kip Carver claims that the device would only track cell phone numbers obtained through a search warrant: via Sheriff Stanek landing Fed cash for KingFish military cellphone tracker in Hennepin County; National Guard intelligence analysts fuse to metro police departments; Lobby for warrantless wiretaps in St. Paul | Twin Cities Indymedia | Movement Media for Minneapolis-St. Paul

The Minnesota Bureau of Criminal Apprehension in St. Paul has a KingFish device and makes it available to local agencies, said Jill Oliveira, a BCA spokeswoman. Only a few people know how to use it because the training is expensive, she said.

Stanek couldn't be reached for comment Tuesday. Kip Carver, a Sheriff's Office inspector who heads the investigations bureau, told commissioners that the device would track only cell phone numbers obtained through a search warrant, and couldn't be used without a court order.

The KingFish can't eavesdrop on phone conversations, Carver said. Instead, it locates cell phones that might be in the possession of an abduction victim, he said, or a robber making a getaway.

"I truly believe [we] would be very busy using that," Carver said. Asked how many times a year the device might be used, he said it could be in the hundreds.

Commissioner Jan Callison agreed to table the request to get more information, but added she was not as troubled by the device as some of her colleagues. "It seems to me that there are certainly ways to make sure this technology is deployed legally. ... It's really the sort of law enforcement that we want," she said.

/////

rockford-files2.pngHere is something handy, a contract surely similar to the ones being currently hoarded by BCA and Hennepin County Sheriffs Office, a 2012 Harris Government Communications Systems Division June 25 2012 from the city of Tempe Arizona: Harris Corporation Wireless Surveillance Products Standard Terms and Conditions of Sale | Public Intelligence - 11 pages.

Harris Corporation’s “StingRay” Used by FBI for Warrantless Mobile Phone Tracking

Harris Corporation AmberJack, StingRay, StingRay II, KingFish Wireless Surveillance Products Price List. Thanks to PublicIntelligence.net as always for stacking the key infos nicely!

/////

December 2008: Harris Corporation Receives National Security Agency Certification for Type 1 Ethernet Module for SecNet 54

June 2013: Harris Corporation Receives NSA Type 1 Certification for Cryptographic Component of Anti-Scintillation/Anti-Jam Modem

July 2011: Harris Corporation's Small Secure Data Link Receives National Security Agency Certification - aka drone radios

January 2008: Harris Corporation Receives National Security Agency Certification for Falcon III Multiband Manpack Radio

Photo source: Ars Technica: Meet the machines that steal your phone’s data | Ars Technica

/////

Sen Mee Moua hounded by law enforcement: Mee Moua leaves state Senate, legacy | Minnesota Public Radio News - Laura Yuen June 29 2010

Yet Moua made waves with some law-enforcement officials this year when she proposed legislation that would ban police departments from sharing secret files on gang members and activities. Moua said she had concerns about racial profiling, especially of young African-Americans who she says could be entered into the database simply for being photographed with a known gang member. The proposal came after a series of scandals involving the now-defunct Metro Gang Strike Force.

"So she saw abuse in law enforcement, and I think that's why she wrote the bills she did," Limmer said. "Was it an overreach? Hmm. Some people might say so, but you could understand where she was coming from."

Some law-enforcement officials, though, painted Moua as a gang sympathizer. And Ramsey County Sheriff Bob Fletcher said at the time that Moua was overreacting to isolated problems with the strike force.

"I think that overreaction has caused her to introduce reckless legislation that will jeopardize the safety of citizens, officers and case prosecutions," Fletcher said.

Moua said she was taken aback by the reaction from law enforcement.

"They wanted to make this about cops vs. dangerous criminals," she said. "But the actuality is it's about cops vs. people in the community who haven't done anything [wrong] and who were being profiled in these databases."

Chaska Police Chief Scott Knight said Moua has been known to question police practices -- which may have irked some law enforcement officials.

"While sometimes some of my peers had some frustrations, I thought she was very healthy for the global approach to law enforcement, and the balance with community and citizens' rights and fairness," Knight said.

/////

To paraphrase Rockford Files Jim says: "You can stomp someone into the ground using computer technology as a club"… Evil CEO guy: "To my knowledge none of this is illegal." Jim: "It should be!" The House on Willis Avenue is easily the most applicable episode to this scenario, with its combination of unregulated electronic spying and shady local government operations:

See also: Rockford files data surveillance didactic ending — Critical Commons

/////

Finally I would add there are several candidates for Pirate Party in Minneapolis in November - if you want to send the signal that these issues matter, consider voting for them. The two parties are almost certainly not going to help you and the other minor parties are all over the map.

How to check cops checking your driver's license! Plus full texts of Anne Marie Rasmusson lawsuit settlements for cop ID checks

Yet another nasty branch on the poisonous tree of data abuse in Minnesota is bearing its digital fruit. Anne Marie Rasmusson, a former law enforcement officer, got 'checked out' by an absurdly sprawling array of Minnesota law enforcement officers illegally abusing their driver's license lookup systems. Three major legal documents from the settlements are included below, I believe for the first time on the web (I might be wrong but didn't spot anything on Google).

For the backstory of the weird law enforcement gangstalking of Rassmusson & subsequent litigation, see Nov 2 2012: Anne Marie Rasmusson's settlement haul now over $1 million - Aaron Rupar / CityPages.

From a clever data-fishing colleague, here is one proven method for promptly obtaining your own DVS data:

E-mail kim.jacobson@state.mn.us with "Hi Kim! This is a request to inspect public data under the Minnesota Government Data Practices Act using my own equipment, in electronic form. I would like to inspect all records and logs of when my driver's license and motor vehicle information on file with DVS was accessed, along with date, time, request detail and requesting agency. My driver's license number and license plates are: X. Thanks!"

100% Lulz virtually guaranteed. Not a horrible time lag either, from what I am hearing from people.

Better Know An Acronym: Mpls PD's ALPR & MnDOT's MBUF, the Parallel DataSchemes: Better get yr DVS records while they're hot: the government has a habit of clamping down on these kinds of data flows, legislative authorization be damned!

On another critical but separate mass surveillance & data control issue, IPAD | Information Policy Analysis Division, Minnesota Department of Administration is taking public comment until January 30, 2013 on the issue of the automated license plate reader system which Minneapolis has semi-extralegally shifted from public to non-public data classification. The PDF is here: www.ipad.state.mn.us/docs/mplsappalpr.pdf. One idea: let IPAD know that this tech is dangerous for data regardless of who is supposed to have access. As the burgeoning DVS omnishambles indicates, 'sensitive' data should be minimized in government, and even 'authorized' personnel actually shouldn't be trusted to operate these systems without granular and public systems of accountability.

Again it is worth pointing out that the City of Minneapolis itself argued in the PDF above that the data generated by the Minneapolis Police Department's Automated License Plate Reader (ALPR) system is dangerous and must be made non-public for the same reasons that MnDOT's Mileage Based User Fee (MBUF, aka Intellidrive) data is dangerous.

MBUF is a story I have been following for several years - it would send extremely frequent location/direction/velocity info to the government & its military-industrial contractor, Battelle, for every user in order to generate a dollar figure for taxing the vehicle - only nuking all your remaining privacy in the process. After many months, much MnDOT MBUF data was released via a Mn Data Practices Act Request, though it is difficult to work with. See Nov 30 2012: EXCLUSIVE MnDOT info cake: 2.97gb emails/docs on the Mileage Based User Fee (MBUF)- Minnesota's GPS vehicle taxing regime in the works

Previously: Jan 9 2013: MPD Tracking OccupyMN Facebook BBQs: Minneapolis "secret" Strategic Information Center / Emergency Operations and Training Facility 25 37th Ave NE in Fridley // MPD Homeland Security Unit at Cruz House: Minneapolis Police Department data request on Occupy Minnesota finally released; sketchy anti-Occupy fusion-style police material from Nevada // Dec 14 2012: Mordor Mayor Rybak makes moves to hide Minneapolis panopticon: Total Minneapolis Awareness Automatic License Plate Reader records form 'retroactive surveillance' empire. Ye Gods we keep catching substantial fish!

The issue of abusive operations in the MN Department of Public Safety-controlled DVS database is becoming a major issue recently, with the decidedly unlikely duo of Republican-aligned Hennepin County Sheriff Rich Stanek and indefatigable Star Tribune reporter Randy Furst both finding highly indefensible query activity on their records. Minn. driver’s license data snoopers are difficult to track | StarTribune.com:

Despite widespread misuse of driver's license records in Minnesota, determining just who is peeking into your files can prove nearly impossible.

The Minnesota Department of Public Safety, which oversees the driver's license database, refuses to tell people the names of users -- generally public employees -- who have looked up their information. Perhaps the most high-profile citizen getting stonewalled by the state is Hennepin County Sheriff Rich Stanek, who is sparring with the department over what he believes were inappropriate queries into his driver's license records.

The Driver and Vehicle Services (DVS) database, which contains addresses, photographs and driving records on nearly every Minnesotan, is protected under state and federal law. State records show that public employees frequently have misused the database by running people's names without a business purpose. That is the subject of a major lawsuit that recently ensnared police officers across Minnesota, as well as a criminal case pending against two Minneapolis employees.

Stanek learned in June that employees at 21 agencies, including his own office, had accessed his records over several years. Some of the queries came from as far away as Wells, Minn., a small town 117 miles south of Minneapolis that he has never visited. The Department of Public Safety would not provide him with the names of the users.

"I believe that some or all of these requests may have been without a legitimate government purpose," Stanek wrote in a December letter to the Department of Administration, asking for an advisory opinion on the matter. The Department of Public Safety "and DVS appear to have purposely created obstacles to deny me an opportunity to track illegitimate access."

Stanek had made two previous requests for his lookups out of curiosity, and was surprised by how many agencies had queried his name.

This time, he says, a security concern prompted his request for the lookups.

He believes the state has an obligation to show that the lookups had a legitimate purpose, even if they do not hand over the names.

Anyhow, a source provided a great deal of the Rasmusson legal paperwork obtained via the Minnesota Data Practices Act. I don't think it's around elsewhere on the Internet, so here it is. I haven't looked over too many settlements myself, so this is overall just funny stuff about a serious topic -- nothing like a government formally conceding abuse and paying out hard-collected taxpayer cash to cover for some ridiculous abuse of officially "necessary" authority.

I wonder what kind of world we'd live in if our government units were actually run by people who never screw up like this, wasting all these resources and being generally abusive. There will surely be more inquiries along these lines...

Three parts:

Rassmusson Lawsuit 1 1110 001 (44pgs) - direct download 1.8MB: rassmusson_lawsuit-1-1110_001.pdf

Rassmusson Lawsuit 1 1110 001 by Dan Feidt

Rassmusson Lawsuit 2 1109 001 (5 pgs) - direct download 205KB: rassmusson_lawsuit-2-1109_001.pdf

Rassmusson Lawsuit 2 1109 001 by Dan Feidt

Rassmusson Lawsuit 3 1102 001 (39 pgs) - Direct download 1.9MB: rassmusson_lawsuit-3-1102_001.pdf

Rassmusson Lawsuit 3 1102 001 by Dan Feidt

Leaving it there for now, but hell, something will probably turn up yet again before I even have time to deal with it!!

MPD Tracking OccupyMN Facebook BBQs: Minneapolis "secret" Strategic Information Center / Emergency Operations and Training Facility 25 37th Ave NE in Fridley

Dateline: Pseudo-Secret Minneapolis (aka Fridley): What WCCO called the "secret" "City of Eyes" Strategic Information Center has been located on the Google! Your Federal Stimulus Money & FY2010 Homeland Security Appropriations At Work - A Facility for Spying on Facebook Occupy Barbecues

strategic-center-mpls.png

It's nice when data releases tie together a larger system, and we've sure got that here. It's not really "secret" but it's quite shiny & new, not well-known at all, and it is certainly has been used as a site for spying on Occupy activists without criminal predicates by the Minneapolis Police Department. [emails a bit farther down]

///// UPDATE Jan 10 2013: See How to check cops checking your driver's license, Rassmusson lawsuit settlement docs /////

The Minneapolis Police Department files about Occupy Minnesota released by a data request on Monday afternoon are turning up interesting wastes of taxpayer money -- and even the so-called "secret" Strategic Information Center & Emergency Operations and Training Facility at 25 37th Ave Northeast in Fridley, north of the city line by the river & railroad tracks.

Also known as the EOTF/SIC, let's wrangle up everything we can find. Start with architects, via Wold Architects/Engineers: City of Minneapolis EOTF | Wold Architects and Engineers

Wold Architects and Engineers designed a site and facility for the City of Minneapolis Fire Department Training Campus to include a Fire Department’s Training Division; training classrooms multi-used as an Emergency Operations Center for the City’s Emergency Preparedness; a Strategic Information Sensor Monitoring Center for the Minneapolis Police Department; and vehicle storage garages for the Fire Department’s regional asset equipment.

The design exceeds the City of Minneapolis requirement for design to meet LEED Silver.

strategic-4.png

strategic-5.pngThis state-of-the-art federally funded facility allows police to determine... the location of barbecues on Facebook, including even the number of "YES" and "MAYBE" invitees.

This facility also encompasses "Shotspotter" directional microphones all over the city - I wonder if those are ever activated besides the gunshot decibel threshold "trigger" - they are in fact pretty high-fidelity microphones, it has been disclosed (May 28 2012 NYT article) but the manufacturer denies the mics are triggered by conversations.

I for one, am glad that we spent both municipal and borrowed federal tax dollars on training the Minneapolis police to believe a Facebook "YES" invite is real. The simulacrum of today's clicks has become the strategic information of tomorrow!

The old EOC center, used in the 2007 35W bridge collapse, can be seen here via MPR and clearly lacks expensive-enough videoconferencing gear.

Here is the press release from Nov 4 2010: Minneapolis opens Emergency Operations Training Facility - City of Minneapolis

Minneapolis opens Emergency Operations Training Facility

The City of Minneapolis has opened its new Emergency Operations Training Facility, which will help emergency responders and other City staff better prepare for and respond to emergencies. The multi-purpose building helps meet the training and response needs of the Minneapolis Fire Department, the Minneapolis Police Department, and the City's Emergency Management Division, along with other regional partners.

The Emergency Operations Training Facility is a multi-purpose building that includes training classrooms for Minneapolis firefighters and metro emergency managers, a strategic information center for the Minneapolis police, the main training site for the State of Minnesota Structural Collapse Team, and an emergency operations center that will be used during significant emergencies or disasters.

The new facility is built on a 12-acre site in Fridley that the City purchased in 1990, and since that time, the site has been built out as a training facility for Minneapolis Firefighters. Over the years, a fire training tower and propane burn building have been constructed, and special equipment has been purchased to help train emergency responders for incidents involving hazardous materials and collapsed structures. The construction of the new Emergency Operations Training Facility on the site is a major step toward completing this training and response site.

The Emergency Operations Training Facility is built to a LEED Silver Quality Standard for sustainability, and it includes facilities for a wide range of emergency responders from Minneapolis and the region:

Emergency Operations Center

One of the lessons learned from the City's response to the Interstate 35W Bridge collapse in 2007 was that the City's Emergency Operations Center, located in the basement of City Hall, was too small to serve as a center for large-scale emergencies. The new facility fixes that, with 2,800 more square feet of floor space. It will also be used as a back-up Emergency Operations Center for the State, Hennepin County and the City of St. Paul.

Strategic Information Center

The Strategic Information Center is a new space where the Minneapolis Police Department will analyze data to determine long-range trends that pose potential risks to the city. It can provide emergency managers with important information during a major event, incident or disaster.

State of Minnesota Structural Collapse Team

This team serves the entire state with specialized equipment and trained personnel for urban search and rescue and structural collapse incidents. This facility will include apparatus bays for storage of emergency response vehicles and specialty equipment for the Coast Guard, State, City and Metro West region of Homeland Security. In addition, this facility will house training and classroom space, staff offices, support spaces and common spaces.

Coast Guard monitoring.

The U.S. Coast Guard will also use the facility as a monitoring location for cameras placed along the Mississippi River from St. Louis to the metro area.

Published Nov. 4, 2010

Moar casual Google Mapping:

google-streetview-mpls.png

Apparently they dropped a cool $50K on the fence in early 2012. here is the bid page "To furnish all labor, materials, equipment and incidentals necessary to accomplish the complete construction of Emergency Operations Training Facility Perimeter Fence Project, located at 25 37th Ave NE, Fridley, MN." SRC: Minneapolis, City of - Projects. [A little more on the fence industrial complex below]

google-streetview-mpls2.png

Of course, once Erin Brockovich samples those weird adjacent holding pond things, I'm sure the infamous Fridley Cancer Cluster case will be solved. Perhaps Sgt. Garcia can go out and take some samples!

google-map-mpls1.png google-map-mpls2.png

I believe at least two of structures are firefighter training buildings - later pics below seem to bear this out.

eoc-marketing-swag1.pngHere is some marketing swag about the video conferencing gear. AVI-SPL Integrates Government Emergency Operation Centers. See the PDF and video too.

eoc-marketing-swag2.pngLet's check out the $330,704 in electronically-created yet borrowed-at-interest-from-private-Fed-cartel recently invested in this barbecue monitoring center. Official less-than-informative stimulus info page: Minneapolis Recovery - City of Minneapolis Minneapolis Police Strategic Information Center.

[Naturally it is funded by the electronically created debt-digits from the Department of Justice Bureau of Justice Assistance (BJA), the same endless police pork hub that brought us all those "you might be a terrorist if you pay in cash" type intel flyers for everything from hotels to hobby stores - many of those flyers were financed by Grant Number 2007-MU-BX-K002, which I included ironically on my own site's banner art. Google it for lulz!] Here's that official page:

The City of Minneapolis is not a primary recipient on this project. No Federal Report XML is submitted for this project.

Dollars Awarded

$330,704

Project Status

Fully completed

Project Description

To establish integrated crime analysis in cooperation with the St. Paul Police Department. Staff will be located in a joint Strategic Information Center (SIC).

Funding Program

MN Department of Public Safety: Byrne Justice Assistance Grant

Responsibility for Implementation

Police Department

Funding Agency

US Department of Justice [BJA/Recovery Act]

Dollars Leveraged

Data not yet available.

Dollars Leveraged Description

Data not yet available.

Dollars Requested

$330,704

Projected Jobs Created

2

Award Type

Grant

Sub-recipient Names

Minneapolis, City of

Vendor Names

No vendors have been contracted to date.

Recovery Funds Spent to Date

$330,704

Perhaps this is even the 'secret' location Tippy spycams are constructed: a while ago prankster MPD Spokester & PIO Jesse Garcia shared pics of a camera construction room & with all the other video rigs this seems a likely spot.

Anyway finally here is the email chain which prompted this line of research. There are surely other gems, we are just barely getting started. Circa page 109 of Part 1:

strategic-center-targets-barbecue.png

The public servant on some of these emails is one Minneapolis Police Department officer Steven Otteson, who has a decidedly low Internet profile.

Poking for traces of intrepid Strategic Facebooker Otteson turns up very little - even though the email is dated June 2012, he has no listed salary on this MPD salary list: My Docstoc. Crossposted the index here: 2011 Minneapolis Police Dept Gross Salary index for Web.

A news story indicated the supervisor of the Strategic Information Center is MPD Lt. Jeff Rugel at 612-673-3428. Page 112:

rugel-bbq.png

"Why are we not getting this stuff from the SIC?" Here is stuff about why they should not have to "spend time looking it up" and it should be run through the SIC... This could kind of be the crux of the whole issue here on Page 114:

sic-track-occupy

Alright, that covers some of the new data on this SIC thing vis-a-vis obsessing on Occupy events, so let's turn to the news coverage of this facility.

Carefully shaped news coverage: Mid-2012 saw a series of mainstream media items intended to shape public perceptions this center is designed to neutralize the threats from the surveilled populace. WCCO went so far as to call it a "secret location". That is some quality Fourth Estate right there.

Coverage for this "City of Eyes" facility on WCCO March 19 2012 (video) City Of Eyes: Your Camera May Help Mpls Police Fight Crime « CBS:

MINNEAPOLIS (WCCO) – Minneapolis police are the first in the country to merge two technologies to help officers fight crime.

The Minneapolis Police Department has combined shot spotter technology and a system of cameras to help catch criminals in the act.

Authorities allowed WCCO-TV’s Reg Chapman into a secret location in Minneapolis, where a strategic information center is housed.

Minneapolis Police Deputy Chief Rob Allen said the room is where police gather intelligence.

“This is the room where we try and fuse the technology we have to monitor video cameras, to monitor the sounds of possible gunshots, and it’s where we have our officers who are trained in intelligence gathering,” he said.

The system in the room is like CBS’ Thursday night show “Person of Interest,” in which cameras are used to help save people from becoming victims of crime.

“If you can anticipate where crimes might happen, you got a far better chance of preventing them from occurring,” Allen said.

According to Allen, when a gunshot goes off, a camera turns toward the source of the sound. Strategic Information Center Commander Lt. Jeff Rugel said the technology helped solve a case where a man was shot, killed and pushed out of a moving car. The sound of the gunfire activated the cameras, which gave police their first clue.

[......]City Of Eyes

The number of cameras connected to the intelligence system is growing and helping police catch more criminals. But not all the cameras are owed by the city.

“The city owns roughly 250 cameras,” Allen said. “We can access right now … an infinite number of cameras.”

According to Allen, any camera that has an IP address, is connected to the Internet, and that police have permission to use can give information to authorities.

So whenever you are in a public space, know that you’re likely on camera. Police are using portable cameras more now than ever. They can put them where they are needed and have one up and running within an hour of the order.

Invasion Of Privacy?

But what about your right to privacy? Police say they are careful not to infringe on anyone’s rights.

“Every time we installed a camera system, we went to the neighborhood and said, ‘You know, this is what we’ve thought about doing? Do you want it or not,’” Allen said.

He says police can’t look into a place where someone has the expectation of privacy. [magic filters eh?] But police still have a wide reach, which gives criminals a greater chance of getting caught on camera.

Crime patterns are currently moving and Minneapolis police hope to add more portable cameras. Police believe if criminals know they are being watched they are more likely not to commit crimes.

Star Tribune writes about this center using Facebook to watch what the state defines as "gang members" (mysteriously, shady rich Caucasian financial operatives never seem to meet this race/age/wealth-biased deviance category schema).

Of course, this week's data release shows this has bloated out to canvassing political movements without even the semblance of illegal activity... there is no "barbecue predicate" but there are of course hourly wages to be paid by Minneapolis taxpayers for monitoring the barbecue Facebook Event. Perhaps even overtime!

Gangs sometimes fire first shots online | StarTribune by Matt McKinney July 14 2012:

Facebook has become a virtual street corner where members trade threats, mourn the dead.

"It's probably no different than any other kids, right?" said Minneapolis police Lt. Jeff Rugel. "They're sharing stuff that they used to do face-to-face or over the phone. But there's criminal stuff." [.....]

Rugel runs the police department's Strategic Information Center, where officers use technology to track crime. One of the jobs in his office amounts to monitoring Facebook full-time. They understand the teen slang and filter through thousands of innocuous and inane comments to look for the few that could solve a crime or stop one before it happens. They try to draw connections out of the Facebook networks to help document the shifting alliances on the street.

Police were aware of Facebook threats between rival gangs weeks before the shooting that killed Nizzel, but the threats weren't specific. When Rugel and his staff sees something that looks like trouble -- a known gang member says he's going to hurt someone -- they pass the information along to officers on the street.

It's a poorly kept secret that the police watch Facebook, said Rugel.

"You see comments every once in a while. 'Don't put that on Facebook. You know who's looking at it,' " he said.

Despite some users' occasional concern, many of the Facebook users monitored by police flaunt their illegal behavior online, showing themselves smoking marijuana, posing with stolen merchandise, the security tags still attached, and making gang signs. [.....]

There was also some bidding information online about the estimated $50,000 fence around the facility. Emergency Operations Training Facility Perimeter Fence Project (eBidDoc #1810882) contact: David Schlueter phone: 612-673-2834 e-mail: david.schlueter@ci.minneapolis.mn.us bid date: 01/25/2012 10:00:00 AM

Try http://io.questcdn.com/questio/projects/planholder/planholder_list.html?jobPK=1810882&userPK=&modifiable=FALSE&isQCPI=TRUE

strategic-center-fence-bidding.png

//////

garcia-yatedo.pngSome other stuff: for what it's worth, this lists PIO Jesse Garcia as being based at the Strategic Information Center.Minneapolis Police Department Employees - Professional Experience,Email,Phone numbers..Everything!: Digging deeper to: Jesse Garcia III - Strategic Information Center, Minneapolis Police Department:

It was scraped off his LinkedIn - no surprise there. But no one put it together... Jesse Garcia III | LinkedIn. I think it would be great if state law were changed so that Garcia could be cross-examined by taxpayers about the flow of drug money through the Federal Reserve Bank of Minneapolis and its member banks, let's say once a month on live community access TV. Looks like he ought to be tapped into that gigaflow of data on bankster crime intel!

Strategic Information Center

Minneapolis Police Department

September 2010 – Present (2 years 5 months)

I am a supervisor in our new intel center that focuses on:

-gang intel

-crime intel

-real time officer assist

-safety camera analysis

-Emergency Operations Center readiness

jesse.garcia@ci.minneapolis.mn.us

Public Information Officer / Media Relations

Minneapolis Police Department

October 2007 – September 2010 (3 years)

More media: Vehicle data, email access among Minneapolis legislative issues | MinnPost - Karen Boros, Nov 2, 2012. Automated License Plate Reader (ALPR) including of course the "secret" camera on nearby Plymouth Ave. N. bridge is controlled from this "Strategic Information unit" according to the article - I would assume this is the same spot it's based, unless it is somehow split:

Currently, the Minneapolis Police Department uses cameras to record the license plates, time and location of vehicles. That data is now public information that can be obtained by anyone requesting the information.

“Our concern is that if it stays public data that people can use it for inappropriate purposes,” said Deputy Chief Robert Allen. The system now doesn’t allow police to inquire how it might be used. “We’re not allowed to make a judgment,” he said.

Access to the data is controlled by about a dozen people working in the department’s Strategic Information unit.

Alright this is taking more than long enough. This thing says it is 22,178 sq ft and it is on parcel 34-30-24-43-0009.

Minneapolis, City of - Projects: An estimated $1.5 million were bid on this beast for just a small chunk of the building, closed Feb 2012.

directions to site: 25 37th Ave NE Fridley, MN 55421

bids close: 02/23/2012, 10:00:00 AM

bids received by: City of Minneapolis Purchasing Department CONSTRUCTION OF THE EOTF APPARAUS BAY ADDITION 330 Second Avenue South Suite 552 Minneapolis, MN 55401

estimated value: $1,500,000.00

project completion date: 08/15/2011

pre-bid meeting information: A Pre-Bid Meeting and site tour will be held on February 15th, at 11:00 AM, Local Time in Room 128 at the Emergency Operations Training Facility located at 25 37th Ave NE, Fridley MN. All interested bidders should attend this meeting.

addenda: 1

project description: Scope of Work Includes: Complete construction of the Apparatus Bay Addition at the City of Minneapolis Emergency Operations Training Facility. This work shall include all labor, equipment, materials, installation, handling, delivery at site, necessary insurance and permits, erection and other required items for general, civil, landscaping, demolition, structural, architectural, mechanical and electrical construction and stability as shown on the plans and specifications.

additional description: This Contract contemplates the complete construction of the Emergency Operations Training Facility Apparatus Bay Addition for the Minneapolis Fire Department located at 25 37th Avenue NE., in Fridley, all in accordance with the Contract Documents. This Project has been designed to comply with the requirements of the State of Minnesota Sustainability Building Guidelines B3 (MSBG B3) Version 2.1 and also the U.S. Green Building Council’s Leadership in Energy and Design ( USGBC LEED®) Rating System. It is the intent of this Contract that the Project shall become MSBG B3 Version 2.1 Certified and LEED® SILVER level of quality building under the LEED®-NC Rating System. Work to be performed consists of the furnishing of all materials, machinery, equipment, labor, supplies, tools, transportation, and other incidentals necessary or convenient to complete the work as shown in the Contract Documents on file in the Minneapolis Finance Department, Property Services Division and with the Purchasing Agent of the City of Minneapolis.

owner: City of Minneapolis

350 South 5th Street, Room 223

Minneapolis , MN 55415

ph: 612-673-3774

contact: Chris Backes e-mail: chris.backes@ci.minneapolis.mn.us

Soliciting Agent: Soliciting agent

Minneapolis, City of

330 2nd Ave. S. Suite 552

Minneapolis, MN 55415

ph: 612-673-2834

fax: 612-673-3565

contact: David Schlueter e-mail: david.schlueter@ci.minneapolis.mn.us

It was used to host a session of the 10,000 Lakes Chapter of the International Code Council. [pdf]

The site's address is place on things like preparedness for your pet: Emergency Preparedness - City of Minneapolis && stuff about exercises (again on the sidebar) City Preparation - City of Minneapolis - the 'meh' front page: Emergency Preparedness - City of Minneapolis. Really need to improve page titles at the city. Perhaps after the election?

Awards - City of Minneapolis:

Minneapolis wins its second Tekne Award

Minneapolis Emergency Operations Training Facility

November 2011: The Minnesota High Tech Association recognized the City of Minneapolis and its Emergency Operations Training Facility with an award at the 2011 Tekne Awards, held Nov. 3 at the Minneapolis Convention Center. The Tekne Awards recognize Minnesota companies and individuals who have shown superior technology innovation and leadership.

The City of Minneapolis took home the award in the “Technology Excellence in a Nonprofit Organization” category that recognized the City’s Emergency Operations Training Facility/Strategic Information Center (EOTF/SIC) for bringing technology and information together to make Minneapolis a safer place. At the facility, technology, digital data, streaming video and highly interactive interfaces come together in one highly efficient communication center for the city.

The Minneapolis Fire Department, Police Department, and Emergency Management division opened the EOTF/SIC in August 2010 as a place where they and other emergency responders could coordinate more closely than had ever been possible before. The facility recently demonstrated its effectiveness during the response to the May 22 tornado that struck north Minneapolis.The multi-purpose building also provides training space for emergency responders.

Here it was, the first one: Minneapolis Emergency Operations Training Facility wins Tekne award - City of Minneapolis: The City of Minneapolis took home the award in the “Technology Excellence in a Nonprofit Organization” category that recognized the City’s Emergency Operations Training Facility/Strategic Information Center (EOTF/SIC) for bringing technology and information together to make Minneapolis a safer place. At the facility, technology, digital data, streaming video and highly interactive interfaces come together in one highly efficient communication center for the city.... and earlier: Oct 18, 2011: Minneapolis Emergency Operations Training Facility a finalist for Tekne award - City of Minneapolis

Mpls. Unveils New Emergency Operations Center | Crime | Downtown News - Nov 4 2010, KSTP Gail Brown: Congressman Keith Ellison secured $750,000 for the project in a 2010 appropriations bill, and he will be attending a ribbon cutting ceremony at 2:30 p.m. along with Minneapolis Mayor R.T. Rybak, City Council President Barb Johnson and other city leaders.

Ellison Secures $750,000 for Minneapolis Emergency Operations Center - Ellison.House.gov Oct 15 2009:

Washington, D.C. – Congressman Keith Ellison (D-Minneapolis) secured a $750,000 appropriation for the City of Minneapolis to build a new Emergency Operations Center in a bill approved by the House today. The funds were included in H.R. 2892, the Homeland Security Appropriations Bill for FY 2010.

Roughly the same stuff in this Council Prez Barb Johnson doc.

It's on Pinterest - see Government & Military for tons of funny stuff including everything from the avispl swag people above. And also: AV Products We Love / Minneapolis Emergency Operations Training Facility

There is a blog post about training there on the Mpls Dept of Civil Rights by Anthony Johnson - Civil Rights Urban Scholars with a helpful slideshow. Tony’s Voice: Our Day As Fire Fighters! | Minneapolis Department of Civil Rights.

strategic-center-3.png strategic-center-2.png strategic-center-1.png

I think you can see this fire training structure (or maybe a similar one) on Google Maps though I have not swung by to check out the Facility myself. Another one:

Minneapolis Emergency Services Employ projectiondesign - AVNetwork.com (undated? A couple pix included)

Fredrikstad, Norway--The City of Minneapolis has deployed 12 projectiondesign F32 DLP projectors as the main display source in the Analyst Room and F22 series projectors in the Incident Command Room of its Emergency Operations Training Facility (EOTF).

Located just outside Minneapolis, the EOTF boasts an extensive surveillance, audiovisual and network infrastructure specified and installed by systems integrator AVI-SPL.

“In a facility like this, even the slightest compromise in performance can result in tragic consequences,” said Fred Primoli, regional VP Sales for AVI-SPL. Primoli and his colleagues worked with the city for nearly two years on the concept, planning and final implementation of the EOTF, with the primary challenge being an interesting one: the creation of a state-of-the-art communications facility that may get activated no more than once in a decade.

“We needed systems that were capable of totally robust operation 24 hours per day, seven days per week – but which also were capable of performing at their best after extended periods of inactivity.

“From the outset we were delighted with the performance of the F32 projectors. The Analyst Room has three rear-projection screens, each measuring 160 inches wide by 120 inches tall, with four projectors driving each screen so that four separate windows can be shown on each one.

“The projectors have been superbly colour-matched to ensure consistency across each screen, while their excellent resolution, contrast and brightness mean they are equally at home showing video or data sources – which is important in an installation such as this where the staff need to a view a combination of both.”

Deputy Chief Robert Allen, a veteran of the Minneapolis Police Department, said: “The new display system allows us to look at a video feed and understand a situation almost instantly. Through video, we can get information to our officers much faster – especially when time is critical. We can zoom in with our cameras and really examine a situation and relay it back to our officers, allowing them to be prepared even before they get there. With this new technology, we can see something happen faster than a police offer 50 feet away.”

F22 series projectors from projectiondesign can also be found in the EOTF’s Incident Command Room that’s used for emergency training and an actual declared emergency.

“There is a large number of emergency monitoring projects in the U.S., and we are delighted that our technology has been used to display high-resolution security-camera images in so many of them," said Anders Løkke, marketing director, projectiondesign. "The Minneapolis EOTF already demonstrated its effectiveness during the tornado that swept through the area last May and, although we would prefer it if our systems never had to be used in similar situations again, the reality is that the city is better-protected now that its providers of emergency services have such easy, immediate and accurate access to security-camera imaging from so many locations.”

“The EOTF was conceived as a place where the various Departments responsible for emergency response and management in Minneapolis could co-ordinate their efforts more closely than had previous been possible,” said Primroli.

Same stuff as May 11, 2012: Minneapolis Emergency Services Goes with Projectiondesign - Fire Apparatus

On May 20 2011 CItyPages reported on Rocco Forte, former Minneapolis fire chief, departing, and Forte talked about being pleased to help finish the complex: "After the 35W bridge collapse, the Republican National Convention, and the tornado that went through South Minneapolis, it is clear that we have one of the finest emergency management teams in the country. It was also a long time goal of mine to complete the Emergency Operations Training Facility that includes an Emergency Operations Center, Strategic Information Center as well as a training facility which seats up to 250 people per day."

Reed Construction Data estimates its cost at $3,988,400 (a more accurate cost estimate is available from RSMeans Online), they say.

There are a couple autogenerated links at Facility Management Minneapolis Product From Industrial Manufacturers, Distributers, Suppliers And OEMs.

There is some PR speak about AVI-SPL getting an award. Press Release/ InfoComm, Sound & Video Contractor Honor AVI-SPL with Two PRO AV Spotlight Awards - Audio/Video Equip./Surveillance - AVI-SPL, Inc. | PRZOOM

On March 11, 2009, the overall cost of the project was pegged by House Research as $27,403,000. SRC: www.house.leg.state.mn.us/hrd/bs/86/hf0554.pdf

This bill would grant $8,000,000 in bond proceeds to the City of Minneapolis to design, construct, furnish, and equip an emergency operations center housed in the City’s current training center and to make other improvements to the training center.

According to the 2008 budget request, the overall cost of the project is $27,403,000 with the City and Hennepin County funding the non-state funded portions of the project. The Joint Emergency Operations Center (EOC) for Hennepin County and the City of Minneapolis will be located at the Minneapolis Fire Training Campus on city owned land. The City contends the current facility is inadequate and limits the effectiveness of the command structure. The City further contends that the Minneapolis Fire Training Campus is an ideal location for the EOC as it would provide a secure operations center with enough room to respond to a major incident affecting the county. Finally, the City believes this request would provide much needed training classrooms at the Minneapolis Training Facility which is the main site for training the State Structural Collapse Team.

HF 554 Status in the House for the 86th Legislature (2009 - 2010) - this is the bill number - I suspect it probably got rolled into the omnibus bill but I will leave that to a Deep Wonk to suss out. // H.F. No. 554, as introduced - 86th Legislative Session (2009-2010).

With a pretty severe shortage of funds for both state and municipal operations, is an open-ended SIC mandate to track protest activity on Facebook really the most prudent use of funds? And doesn't this operational configuration create a chilling effect on political expression in Minneapolis? The research continues....

MPD Homeland Security Unit at Cruz House: Minneapolis Police Department data request on Occupy Minnesota finally released; sketchy anti-Occupy fusion-style police material from Nevada

///// UPDATE 2:30AM Jan 9: Diggings lead to a truly under-appreciated and basically new police strategic intelligence outfit in Fridley complete with documentation about why they ought to be tracing protesters on state-of-the-art gear - WCCO stated this place is "secret"! LOTS MOAR: MPD Tracking OccupyMN Facebook BBQs: Minneapolis "secret" Strategic Information Center / Emergency Operations and Training Facility 25 37th Ave NE in Fridley /////

After some months, the Minneapolis Police Department released dozens of pages about Occupy Minnesota / Occupy Minneapolis and several high-profile operations, particularly the eviction of protesters from 4044 Cedar Ave. This data was released from the Department late yesterday afternoon.

Interestingly the suppression of the civil disobedience at 4044 Cedar fell under the rubric of the MPD Special Operations Division / Homeland Security Unit. Further data requests to this unit could be interesting, including federal grants applied for similar suppression activities in the name of "Homeland Security."

occupy-mpls-mpd-net7.png occupy-mpls-mpd-net6.png

This email related to the "Emerging Issues" PDF from Nevada below (see the attachments field).

occupy-mpls-mpd-net1.png

One interesting feature: the coordination between the MPD and the Downtown Improvement District (DiD) which is aligned & serves the purposes of the downtown property owners (as opposed to homeless, indigent people downtown etc). DiD, while seen as a semi-public entity, is privately directed and is not an openly participatory structure. DiD has a central office that coordinates over a digital radio system with the downtown First Precinct and corporate building security officers including during protests.

The other major item of wider interest is a sketchy Nevada operation partially merged with the Los Vegas Police Department. It was use as "a lot going on" from Darrel Stephens@carolina.rr.com whoever that is...

"Emerging Issues in the Occupy Movement" from the Major Cities Intelligence Commanders Group (MCC ICG Sub-Committee)and the Southern Nevada Counterterrorism Center (SNCTC) is really a classic chestnut. The email addresses to LVMPD.com seem to be an official domain of Las Vegas law enforcement, not a private organization. I don't recall seeing this Occupy-related writing from this organization circulate elsewhere. If so, we have a new taxpayer-supported 'node' generating more hype in the "counterterror" national political activist monitoring network.

occupy-mpls-mpd-net2.png occupy-mpls-mpd-net3.png occupy-mpls-mpd-net4.png occupy-mpls-mpd-net5.png

Fortunately the "LAW ENFORCEMENT ONLY - DO NOT DISSEMINATE" pseudo-classification does not really have much if any actionable meaning under the Minnesota Data Practices Act, though we can surely expect proposals to create tons of secret data piles under loosey-goosey unnecessary pseudo-secrecy at the Minnesota Legislature this session. Follow @richneumeister for sharp updates on that whole front for sure!

I want to also point out a couple other good recent releases posted on Scribd about Minneapolis. The ALPR reader system ongoing story - see Dec 2012: Mordor Mayor Rybak makes moves to hide Minneapolis panopticon: Total Minneapolis Awareness Automatic License Plate Reader records form 'retroactive surveillance' empire | HongPong.com && also Nov 30 2012: EXCLUSIVE MnDOT info cake: 2.97gb emails/docs on the Mileage Based User Fee (MBUF)- Minnesota's GPS vehicle taxing regime in the works. The City of Minneapolis itself neatly ties both these stories together in the next link by arguing that these surveillance data programs are both dangerous! Thanks!

City of Minneapolis Application to IPAD requesting classification of all ALPR data as not public. It's worth an entirely separate post, but basically here the City of Mpls argues that the ALPR license plate reader should be classified by the State of Minnesota Dept of Administration's "IPAD" division as confidential, because IPAD classified data from an entirely different tracking project, the MnDOT IntelliDrive / Mileage Based User Fee (MBUF) system, is also dangerously specific data which easily indicates when homes are vacant due to daily traffic patterns, etc. So the argument from the city is that the data is dangerous: ALPR is dangerous, MBUF is dangerous, therefore should be classified -- but still collected of course!

Page 7 of this one: http://www.scribd.com/doc/117555926/Metro-Transit-Police-Report-on-Chalk-and-Silly-String talks about using Trespass notices specifically because of OccupyMN. For more docs like these see SmileyRevolt & twitter.com/smilyus.

There does not seem to be very much other personal data of regular people, besides one page of mugshots of arrestees with their birthdays. However I do not have the time to parse more carefully & if this acts as an intrusion to anyone in the public I apologize in advance. IN theory, what the state defines as private personal data should not be released on this kind of material. Lacking a handy secure redaction tool for PDFs, I deleted page 99 from part 1 in this release..

Here is the Data Practices Act official response email which accompanied this. If the requestor wishes to have their name added back onto this I will do that, just took it off by default.

----- Forwarded Message -----

From: "Meyers, Linda" <Linda.Meyers@minneapolismn.gov>

To: [....]

Date: Mon, 7 Jan 2013 19:43:48

Subject: DP 1229 - Occupy MN data

Mr. [....],

We received your check today and I’ve attached the data you requested regarding Occupy MN. There are 259 pages. Again, we apologize for the delay in getting this to you.

Linda Meyers

Police Support Technician I

MPD Records Information Unit

350 S. 5th St.

Minneapolis, MN 55415

612-673-2961

linda.meyers@minneapolismn.gov

Non-public and/or Privileged and/or Confidential and/or Private Information:

This electronic message may contain investigative data which is non-public pursuant to Minnesota Statutes section 13.82 subdivision 7, or personnel data which is non-public pursuant to Minnesota Statutes section 13.43 subdivision 4. If you are not the intended recipient of this e-mail: (1) do not read the content of the message; (2) immediately notify the sender that you incorrectly received the message; and (3) do not disseminate, distribute, or copy this e-mail.

//////////

134 pages (135 before the removed page) - Part1 originally 4242Kb. With the edit, the md5 sum is aef289624969402680255a15dea1aec3 MPD_OccupyMN_Data_part1b.pdf - Posted also at http://www.scribd.com/doc/119531853/MPD-OccupyMN-Data-Part1b

Direct download: MPD_OccupyMN_Data_part1b.pdf 6.7MB

MPD OccupyMN Data Part1b


Part2 3183Kb.

1d58ba5700273ede7b3dd5ad0595fa5c MPD_OccupyMN_Data_part2.pdf - Posted also at

http://www.scribd.com/doc/119527079

Direct download 3.3MB MPD_OccupyMN_Data_part2.pdf

MPD OccupyMN Data Part2

Federal Homeland Security TSA VIPR Team & #VikingsDrone: Suspicious drone & Feds spotted at Vikings/Packers game

Things are a little strange at the Vikings/Packers Game today. A drone has been photographed hovering around the Metrodome fan plaza on the west side, and a Homeland Security / TSA "VIPR" team has been hanging around as well, indicating the federal government is shifting into "protecting" the major Spectacles at taxpayer expense.

My friend Nathan Hansen noticed the #VikingsDrone and the VIPR team, documenting & posting them on twitter @nathanmhansen. [Note: awhile back I did a 'lil client design work for Hansen.]

//// UPDATE 12:15PM Monday: According to @TCRover, a branch of the Pioneer Press, the drone was NOT operated by the government but rather some production company. The pic they say is from the crew flying it earlier: See https://twitter.com/TCRover/status/285560684245315585/photo/1 . Nonetheless we still need to deal with the impending prospect of government & contractor drones filling our airspace - and indeed this story has prompted others to discuss other sightings near government sites. //// 2:20PM update: It's annoying that they tried to tweet @ me last night but it never turned up in my timeline so I didn't find out until today. I would have much preferred to straighten it out immediately! Also, here's what's going on with drones in Oklahoma... Follow my friend @axxiom for more. ////

PHOTO sources: yfrog Fullsize - http://twitter.yfrog.com/h41hxevhj // yfrog Fullsize - http://twitter.yfrog.com/o0mkqkobj // yfrog Fullsize - http://twitter.yfrog.com/oemubbyj // VIPR Team: yfrog Fullsize - http://twitter.yfrog.com/odjd2ybj

odjd2ybj.jpeg h41hxevhj.jpeg

You can see the four rotors pretty well on these pics. It is comparable to the sports photography drone linked below as well - I figured it might just be a civilian hobbyist drone or some weird sports media project drone until the VIPR team was found by Hansen.

mkqkob.jpg mubby.jpeg

I am just delighted that the national government had to borrow more money at interest from the Federal Reserve System in order to send out these guys and their fancy flying spy robot to the Vikings/Packers game. We get the twin benefits of national debt slavery AND a surveillance state with nothing useful to do!

Our friends at WTFNews cranked out a quick post on this already: Unidentified Drone Spotted at @Packers-@VikingsFootball @NFL Game » WTF RLY REPORT

Let's Ban This Drone Operation in Minneapolis: Already Minneapolis activist Kurtis Hanna has suggested a petition to get drones banned on the city charter. (come to think of it, wouldn't it be good to get something like the White House petition site for the Mpls Charter Commission?) I will include some info below on this.

The Department of Homeland Security and the National Football League have a burgeoning relationship. Previously when I wrote up a post on the relatively new and totally off-the-radar Homeland Security Investigations division (basically their own militant version of the FBI, intended to reach BATF-level org status) they did a drill black helicopter landing on the Super Bowl field. [yes really - HSI is so new I must have been the first person to satirize its absurdities on the whole interweb!] See April 12 2012: Meet the new Boss in Town: ICE spawns... HSI Homeland Security Investigations, for great justice & cocaine cowboys | HongPong.com

The Super Bowl and World Series are also both declared National Special Security Events, which activates a fat block of overtime for many federal police agencies, much like the Republican & Democratic National Conventions. (However, since rioting at sports events is closer to the booze-soaked Id of the American public than more 'political' street upheavals, it doesn't meet the same heavy hand from federal & local police agencies) NSSEs generally feature Homeland Security, FEMA and the Secret Service operating at a high tempo, another thing that HSI & TSA are getting involved with as a 'filler force' if you will.

For Super Bowl NSSE info see: Super Bowl XLVI, NSSE & Big Sis - YouTube // www.secretservice.gov/press/pub0202.pdf on Bowl XXXVI // this crazy PDF: rnc08report.org/engine/uploads/1/Day-2-Breakout-2-NSSE-Carillo-Lowry-Lumley.pdf // Infowars » Indy Super Bowl: National Security State Protects Sports Fans from Prostitutes // National Special Security Events: 8. NSSE Fill-in Fact Sheet // Article Detail - Domestic Preparedness via LLIS.gov // etc

Federal VIPR teams: been popping up in all sorts of places. Here's the Wiki page. Wiki notes GAO attributes their existence to a Reaction to the shady Madrid train bombings. VIPR is trying to get at pro sports & local transportation (the Hiawatha light rail has a station close to where they were photographed) and wherever else they can normalize their presence. In this case the VIPR deployment apparently includes at least a half-dozen uniformed officers and at least one drone.

Additionally there was strange audio interference right before a commercial break in the first half, kind of like the sound a cell phone makes when its microwave signal induces noise in a speaker or electronics. However, I don't think game-day satellite transmissions go straight over-the-air from the Metrodome, as there aren't really satellite dishes around there I've noticed. Thus it seems unlikely to me that the one spotted drone would have glitched the transmission. Perhaps unrelated but also something you don't usually see. I blame Wisconsin FalseFlag types for this noise, whoever that might be :-P

SEE ALSO:

The drone does look similar to the one in this story. New use for drones: Sports photography - CBS News

Oh this is great. Perhaps the best link I've found in this. "PUT [VIPR] TEAMS TO WORK FOR YOU" VIPR teams and pipelines!! A "no cost resources for expanding and enhancing your security". Free oil goon security? Screw that: www.dleg.state.mi.us/mpsc/gas/download/2011SS-2-4-VIPR_Handout.pdf

May 2012: TSA VIPR Team Spotted at… Detroit Music Festival?? « TSA Out of Our Pants!

CNN Jan 28 2012: TSA rail, subway spot-checks raise privacy issues - CNN.com

VIDEO Blackburn Questions TSA Officials on VIPR Teams - YouTube

VIDEO TSA VIPR Teams in Greyhound Bus Station Tampa FL 02/16/2010

TSA deploys 'VIPR' teams throughout Tennessee to set up illegal security checkpoints on interstates - NaturalNews with a bunch of other links including: TSA-style full body pat-downs coming to an NFL stadium near you (Sept 2011) etc

6 USC § 1112 - Authorization of Visible Intermodal Prevention and Response teams | LII / Legal Information Institute. So they are doing this about the Hiawatha light rail officially I would guess. This would also signify that Metro Transit would have some record of the situation if "consult" in Sec.4 has occurred

(a) In general

The Secretary, acting through the Administrator of the Transportation Security Administration, may develop Visible Intermodal Prevention and Response (referred to in this section as “VIPR”) teams to augment the security of any mode of transportation at any location within the United States. In forming a VIPR team, the Secretary—

(1) may use any asset of the Department, including Federal air marshals, surface transportation security inspectors, canine detection teams, and advanced screening technology;

(2) may determine when a VIPR team shall be deployed, as well as the duration of the deployment;

(3) shall, prior to and during the deployment, consult with local security and law enforcement officials in the jurisdiction where the VIPR team is or will be deployed, to develop and agree upon the appropriate operational protocols and provide relevant information about the mission of the VIPR team, as appropriate; and

(4) shall, prior to and during the deployment, consult with all transportation entities directly affected by the deployment of a VIPR team, as appropriate, including railroad carriers, air carriers, airport owners, over-the-road bus operators and terminal owners and operators, motor carriers, public transportation agencies, owners or operators of highways, port operators and facility owners, vessel owners and operators and pipeline operators.

(b) Authorization of appropriations

There are authorized to be appropriated to the Secretary to carry out this section such sums as necessary for fiscal years 2007 through 2011.

Process for City Charter Amendment for banning these drones: Sent along by Kurt Hanna who thinks that "10,791 valid signatures of Minneapolis residents who are registered voters in order to qualify for the ballot" based on the figure of 215,806 voters voting last time. Citizen petition timeframe link. BUT: How much time do we have to gather these signatures?

Some more info: Via Minneapolis City Charter: http://library.municode.com/HTML/11490/level2/SUHITA_CH.html

(1) The methods available for amending a home rule city charter are contained in Minnesota Statutes, Section 410.12 et seq., which provides as follows:

(1) 410.12 AMENDMENTS. Subdivision 1. Proposals. The charter commission may propose amendments to such charter and SHALL DO SO upon the petition of voters equal in number to five percent of the total votes cast at the last previous state general election in the city.Proposed charter amendments must be submitted at least 12 weeks before the general election. Only registered voters are eligible to sign the petition. All petitions circulated with respect to a charter amendment shall be uniform in character and shall have attached thereto the text of the proposed amendment in full; except that in the case of a proposed amendment containing more than 1,000 words, a true and correct copy of the same may be filed with the city clerk, and the petition shall then contain a summary of not less than 50 nor more than 300 words setting forth in substance the nature of the proposed amendment. Such summary shall contain a statement of the objects and purposes of the amendment proposed and an outline of any proposed new scheme or frame work of government and shall be sufficient to inform the signers of the petition as to what change in government is sought to be accomplished by the amendment.The summary, together with a copy of the proposed amendment, shall first be submitted to the charter commission for its approval as to form and substance. The commission shall within ten days after such submission to it, return the same to the proposers of the amendment with such modifications in statement as it may deem necessary in order that the summary may fairly comply with the requirements above set forth.

Subd. 2. Petitions. The signatures to such petition need not all be appended to one paper, but to each separate petition there shall be attached an affidavit of the circulator thereof as provided by this section. A petition must contain each petitioner's signature in ink or indelible pencil and must indicate after the signature the place of residence by street and number, or their description sufficient to identify the place. There shall appear on each petition the names and addresses of five electors of the city, and on each paper the names and addresses of the same five electors, who, as a committee of the petitioners, shall be regarded as responsible for the circulation and filing of the petition. [........]

(1) Subd. 3. May be assembled as one petition. All petition papers for a proposed amendment shall be assembled and filed with the charter commission as one instrument. Within ten days after such petition is transmitted to the city council, the city clerk shall determine whether each paper of the petition is properly attested and whether the petition is signed by a sufficient number of voters. The city clerk shall declare any petition paper entirely invalid which is not attested by the circulator thereof as required in this section. Upon completing an examination of the petition, the city clerk shall certify the result of the examination to the council. If the city clerk shall certify that the petition is insufficient the city clerk shall set forth in a certificate the particulars in which it is defective and shall at once notify the committee of the petitioners of the findings. A petition may be amended at any time within ten days after the making of a certificate of insufficiency by the city clerk, by filing a supplementary petition upon additional papers signed and filed as provided in case of an original petition. The city clerk shall within five days after such amendment is filed, make examination of the amended petition, and if the certificate shall show the petition still to be insufficient, the city clerk shall file it in the city clerk's office and notify the committee of the petitioners of the findings and no further action shall be had on such insufficient petition. The finding of the insufficiency of a petition shall not prejudice the filing of a new petition for the same purpose. (Back)

(1) Subd. 4. Election. Amendments shall be submitted to the qualified voters at a general or special election and published as in the case of the original charter. The form of the ballot shall be fixed by the governing body. The statement of the question on the ballot shall be sufficient to identify the amendment clearly and to distinguish the question from every other question on the ballot at the same time. If 51 percent of the votes cast on any amendment are in favor of its adoption, copies of the amendment and certificates shall be filed, as in the case of the original charter and the amendment shall take effect in 30 days from the date of the election or at such other time as is fixed in the amendment.

An amusing side question: is this "magick" security theater? Security Theater of course works most "effectively" at materializing psychological phantoms with an audience at a Spectacle. This is the perhaps the principle Stimulus Effect intended by Homeland Security & its general orientation around 'visuals' which is not that different than Ceremonial Magick, which is [arguably] anything that generates a certain sense-impression in the mind of Observers.

metrodome-national-guard.jpeg

Another old backstory: In 2010 some people noticed they were using government photos of MN National Guard riot control gear from the deployment at the 2008 Republican National Convention under the NSSE system for recruitment propaganda on the Metrodome. RNC '08 Report: Our News: National Guard advert on Metrodome, proposed site of 2012 DNC, depicts soldiers deployed against protesters during 2008 RNC. Your tax dollas at work!

Mordor Mayor Rybak makes moves to hide Minneapolis panopticon: Total Minneapolis Awareness Automatic License Plate Reader records form 'retroactive surveillance' empire

rybak-licenseplate-mordor-panopticon.jpg

"It is poor civic hygiene to install technologies that could someday facilitate a police state." ~ Cryptographer/security guy Bruce Schneier (src)

We all know the old motif - Feds staking out parking lots, reporting the license plates back to Hoover. Nowadays things are a little different - computers can trivially hoover up all the unique features like license plates and faces from video signals, 24/7. These are technical capabilities that Hitler and Stalin only dreamed of. The former National Security Agency employee William Binney described the system locking into place as a "turnkey totalitarian state" is arriving one system at a time. One of those turnkeys just turned up in Minneapolis.

The word is out now that more than 2 million license plate records have been obtained through a data request, since the surveillance material consists of mostly public record fields. Minneapolis developer Tony Webster (@webster) wrote up the info on what happened here - and quite correctly calls for the government to quit holding this kind of data for a number of serious reasons. See TonyWebster.com: Minneapolis Police release 2.1 million license plate records.

Rybak wants quick action on license plate data | StarTribune.com:

A day after the city released a database containing more than two million license plate scans, Mayor R.T. Rybak wants expedited state action to make the data non-public.

The Legislature is already expected to take action this session to reclassify license plate tracking data, which is derived from cameras mounted on local police squad cars across the state. But after complying with a request for Minneapolis' entire public database -- featuring dates, times and locations of all plates scanned in a 90 day period -- Rybak wants more immediate action.

He said the request was "already in the works" before Tuesday's data release, but "it does concern me." His request to temporarily reclassify the data would, if approved by the Commissioner of Administration, prevent the city from releasing the tracking data to members of the public.

See also latest on MPR: Lawmakers mull bill to regulate automatic license plate readers Minnesota Today. I think MPR is inaccurate as MPD said they'd shortened this to 90 days from the original year, as Strib indicated. (otherwise they would have violated MN Data Practices Act by failing to release earlier public records upon request)

Minneapolis' DFL Mayor RT Rybak (@mayorRTrybak) has sprung into action to demand the records generated by Minneapolis Police Department's Automated License Plate Reader (ALPR) system become classified as "private data", which means only the government, cops, various lawyers under different circumstances, etc, could trivially get ahold of incredibly detailed data & patterns about your vehicle's movements without a warrant.

Rybak's thoughtful plan is to make sure that no one else can get that data, only that bloated galaxy of whom John Young @ Cryptome.org calls the 'authoritatives' lording the new panopticon over us.

This is our window - our snapshot of the beta test - into the hellish future of total 'retroactive surveillance' awaiting us, when all our actions are constantly recorded to be 'played backwards' whenever some bureaucratic enforcer wants to increment his career through hassling us, demanding civil fines for infractions etc.

As recent posts on this site have documented, the Minnesota Department of Transportation (which just got a new chief) is spending state taxpayer money funnelled to military-industrial contractors in order to build a local version of a GPS tracking system called Intellidrive, which would transmit every damn move, including velocity, of every tagged car.

Additionally, exposure of abusive & immoral practices in the Drug Recognition Evaluator training program (& main BCA file) resulted not in a candid cleanup by law enforcement, but stonewalling. When individual law enforcement officers invariably abuse these massive data mining deployments, as some do, is there really adequate oversight let alone punishment for turning these 'necessary' technologies into avenues of abuse?

Plus of course, what are the implications of the chilling effects of these ALPR systems? What is the price paid by society when the chilling effect of avoiding ALPRs by staying put kicks in? How many people refuse to fly because of the intrusive & abusive security measures? And what happens when municipal cameras collect data even more granular and intrusive than the federal TSA?

For more on this stuff I recommend following @webster, and @RichNeumeister, a citizen activist on nearly all data & privacy matters at the Mn State Capitol. It seems like Webster triggered the Rybak blocking him on Twitter. Classy - especially since Webster posted in this recent context he's a lifelong DFL supporter.

To quote a bit from Rich Neumeister's blog which is VERY helpful for Minnesota issues: Two meetings: prescription records and license plate scans

Now to the Criminal Justice and Juvenile Information Policy Group meeting which was to make a decision about the collection and retention of millions of records of where you and I travel if we happen to be owners of cars collected secretly by the cops.

Per Eric Roper's Star Tribune Blog post  the Policy Group made up of Commissioners, judges, and others decided to make the license scan data private, but deleted the retention of 180 days for the data if there were no hits for law enforcement investigation.

Now I have to scratch my head on this one. By deleting the retention of 180 days, is the Policy Group saying with all intents and purposes, DO NOT KEEP OR COLLECT LICENSE SCANS ON INNOCENT AND LAW ABIDING PEOPLE, or are they saying the COPS CAN COLLECT ALL THE LICENSE SCAN DATA THEY WANT ON INNOCENT AND LAW ABIDING PEOPLE AND KEEP IT AS LONG AS THEY WANT.

I am perplexed.

& also earlier: Email to Minnesota Criminal Justice Policy Group on License Plate Cameras. For what it's worth Webster tweeted this afternoon (Tues Dec 13th) that the division of the state govt that implements/sets the rules, IPAD, has NOT yet received anything new from Minneapolis about ALPR data.

The reality is that politicians are not that responsible about these data issues. Instead you get ignored, blocked on Twitter etc. I am writing another post about yet another newly relevant old case - the Norm Coleman credit card database leak which I covered at Politics In Minnesota circa January 2009, eerily similar to the new charges against alternative journalist Barrett Brown. (Posting links to data like the Coleman leak is a form of journalism & research that feds are trying to redefine [unconstitutionally] as a felony! NOT GOOD). But that is definitely a whole 'nother story....

/////

MORE ON RETROACTIVE SURVEILLANCE LIKE MINNEAPOLIS POLICE DEPARTMENT ALPR SYSTEM: (not to be confused with the practice of retroactively legalizing the earlier illegal surveillance performed by telecoms during the Bush administration). 'Retroactive surveillance' is basically a timestamped panopticon.

Retroactive surveillance is a class of technology which can easily destroy certain dimensions of 'free will' and therefore should be considered extremely carefully as a keystone type of social control system. It's my personal opinion it will take at least a century for this type of tech to be possible to be used ethically (if ever), as the ethical structures do not currently exist – a major reason we are all descending into a kind of neo-feudal technocratic authoritarianism worldwide.

cryptogon.com » NYPD and Microsoft Team Up to Peddle Retroactive Surveillance System [WSJ] - same type of camera data inputs

NYPD, Microsoft Hope to Make a Mint off New Surveillance System - National - The Atlantic Wire

Coming soon: Ubiquitous surveillance from Big Brother's wayback machine (the archive.org wayback machine snapshots many websites over time, invaluable!)

NetworkWorld, 2011: Coming soon: Ubiquitous surveillance from Big Brother's wayback machine

cryptogon.com » New Video Surveillance System Tags, Tracks and Follows

a commenter puts it well at cryptogon.com » Coming Soon: Retroactive Surveillance on Anyone: "A present anxiety of future trouble from the unforgotten past; black to the future."

A change in tune: law enforcement now aggressively promoting retroactive surveillance capabilities of license plate readers | Privacy SOS

Is there any science (social science) of retroactive surveillance?

House Passes Surveillance Bill without Retroactive Immunity | TPMMuckraker

Drug war provides cover for retroactive surveillance without probable cause | Privacy SOS

.. That's all for now - this post is licensed Creative Commons remix/reuse with attribution to Dan Feidt/Hongpong.com non-commercially, including the "sheeple style" remix image I slapped together.

EXCLUSIVE MnDOT info cake: 2.97gb emails/docs on the Mileage Based User Fee (MBUF)- Minnesota's GPS vehicle taxing regime in the works

After a long wait, on Nov 28 2012, the Minnesota Department of Transportation (MnDOT) released ~2.97 gigabytes of data from inside the development of a GPS-based vehicle tracking system intended to introduce a vehicle tax - which would entail a great deal of data constantly collected by the government on the whereabouts and everyday patterns of the taxed vehicles. The source URL posted yesterday is ftp://ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/ .

My friend Nathan Hansen made the request, pursuing a long-running story of the buildout of these taxation-tracking highway techs. (Disclosure: I did some design work for Hansen previously) The 2008 story I did: Now Searchable: The MnDOT NASCO NAFTA Superhighway Document Stash && Index of /June 2008 MN DOT Request/NASCO - Hansen Request && Index of /June 2008 MN DOT Request/June 2008 Request && Index of /DOT. A lot of these plans fell by the wayside - and a special Minnesota Intellidrive project and MBUF is the new plan. Related: Melissa Hill's new blog allows you to "Track the Police" using public data && Private company hoarding license-plate data on US drivers. In May 2011 I did this story: Contracts for IntelliDrive MnDOT Military-Industrial/U of M plan to GPS-track all cars. This data dump continues the story.

There are a few important angles: comprehensive vehicle tracking data would be great for law enforcement, lawyers and big corporations to investigate everything in one's life, including 'retroactive surveillance' of previous activities. However, the "fees" that would be imposed on rural Minnesotans who have to drive around a lot would be quite burdensome.

From a quick look at the PDFs we find internal discussion points about such impending scams as 'carbon credit' trading (a greenwashing Goldman Sachs sponsored futures bubble, as Matt Taibbi reported). Additionally Raytheon and SAIC have both been involved in this "Intellidrive" national-scale super-project. Also, just because the user data is processed behind Battelle's firewall in no way signifies any level of security of personal information.

The main block of data posted is in huge Acrobat Reader X sized PDF files (1.1 and 1.6GB) . We have mirrored around the files and checked with md5hash in case the govt pulls any later. Acrobat Reader X is kinda bogging on these giant files -- it loads all the emails in a slow email reader-like interface). Plenty of items like "concept of operations" or "MBUF CONOPS" is in there, a lot of stuff about consultants. We are just starting to peer at it, but Adobe is difficult to work with (a svelte 400MB app yay).

To get this batch of files yourself, if you have UNIX wget for mirroring:

$ wget -mb ftp://ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/

I definitely recommend installing wget for things like this, where the files are listed in a directory for quick scraping.

//////////////

DATA EXTRACTION BONUS CHALLENGE: To open the attachments on these emails, for OSX you have to use a program such as the free MailRaider: Download MailRaider for Mac - Read Outlook .msg files on your Mac. This is what you gotta do - in Acrobat, hit the paperclip on the side:

acrobatreader.png

After first picking out the individual PDF attachments in Acrobat (the paperclip icon) you can get it to open in MailRaider. Hit the 'Open' button in that side panel. Hopefully this will launch MailRaider. In MailRaider, flip open the sidebar you can get it to work like so:

mailraider.png

Here is the first PDF I was able to extract - Intell~1.pdf (2MB) - it is a "business sensitive" presentation by military-industrial contractor Battelle to MnDOT. Let's have some choice excerpts including particularly how they use taxing people driving around rural-ish places like Wright County as a target for the mileage tax.

mndotcake000.png mndotcake001.png mndotcake002.png mndotcake003.png mndotcake004.png mndotcake005.png mndotcake006.png mndotcake007.png mndotcake008.png mndotcake009.png mndotcake010.png mndotcake011.png mndotcake012.png mndotcake013.png mndotcake014.png mndotcake015.png mndotcake016.png mndotcake017.png mndotcake018.png mndotcake019.png mndotcake020.png

What could possibly go wrong?!

mndotcake021.png

It is always sad to see fine open source techs like GnuPG used to encrypt tracking data. Damn you Technocratic Capitalism!

mndotcake022.png mndotcake023.png

This is pretty alarming. Sterns, Wright, etc are counties full of peopl that can't afford to pay more.

mndotcake025.png mndotcake026.png

LOOKS LEGIT:

mndotcake027.png mndotcake028.png

So this is just one extracted PDF from a single email. If Battelle was actually a front for malicious space aliens who want all the inhabitants of this planet tagged and tracked, I would not be surprised!

///////////////

MIRROR ADDRESSES: Here is the first mirror of it. These files are big enough to crash your browser - maybe rightclick & Save As link so the PDF plugin doesn't keel over... I don't think we'll need tons of mirrors for this, but it's good to have a couple around.

the big ones are at:

http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun... & also:

http://hongpong.com/files/mndotcake/Public%20QAM.pdf
http://hongpong.com/files/mndotcake/Public%20CommVault.pdf

dfc0fd1d4d6bdbcaf0498a50ee0f5fec Public CommVault.pdf 1.22 GB on disk (1,216,990,533 bytes)

cec386cc20000b7fe10297fc3ca0cdab Public QAM.pdf 1.7 GB on disk (1,698,431,132 bytes)

If you find gems tweet em with hashtag #mndotcake. If you find an open source way to work with files this big let us know. It will take some people to work on this. We invite people to occupythecomms.cc group infocake for looking at PDFs - this has group writing pads available (very easy, much like googledocs). Info on occupythecomms: https://occupythecomms.cc/pages/view/90009/activism-and-collaborative-media-methods

On the indymedia mirror the directoryIndex isn't cooperating yet (no folders list) but the files are here. The big ones are in bold, not too much in the others so far found.

You can generate a list of your wget mirror like this with:

$ find -name \*

http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/Public%20QAM.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/Public%20CommVault.pdf

http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes16.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes27.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes26.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes3.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes9.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes13.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes8.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes29.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes10.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes5.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes11.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes12.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes19.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/r_phone%20for%2027th%20and%2028th....and%20a%20TIP!%20_).pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes17.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes22.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes6.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/6_5_07%20Commissioner's%20Staff%20Meeting%20Minutes.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/RE_%20Dieringer%20Pre-Award---IMPORTANT!!!!.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes15.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/RE_%20Dieringer%20Pre-Award---IMPORTANT!!!!3.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Ray's%20requests.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/r_RE_%20Dieringer%20Pre-Award---IMPORTANT!!!!2.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes30.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes28.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/r_Re_%20MNDOT_MBUF%20Discussion%20guide%20v2.DOC%20(Lucy's%20out%20of%20the%20office%20).pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes18.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Attachments/r_6%205%2007%20Commissioner's%20Staff%20Meeting%20Minutes.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes2.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes20.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/r_This%20should%20do%20it!.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes%20-%20No%20major%20issues%20FYI.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes25.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes7.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/r_This%20should%20do%20it!2.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/r_RE_%20Help_!_.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes14.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/r_headin'%20home%20with%20MBUF%20as%20my%20bedmate....pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes24.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/r_Selection%20Committee%20%20(Just%20In%20Case)%20.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...).pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes21.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes4.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes23.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/6_5_07%20Commissioner's%20Staff%20Meeting%20Minutes2.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes31.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/CommVault%20Redactions/RECEIVED!!%20%20_)%20%20%20%20MBUF%20Presentation%20Draft_11_16_2009_415pm.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/CommVault%20Redactions/RE_%20Temp%20classification%20is%20here!_02_09_2011_128pm.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/CommVault%20Redactions/RE_%20Temp%20classification%20is%20here!_02_09_2011_136pm.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/CommVault%20Redactions/RE_%20Temp%20classification%20is%20here!_02_09_2011_133pm.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/CommVault%20Redactions/RE_%20Temp%20classification%20is%20here!_02_08_2011_1141am.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/CommVault%20Redactions/RE_%20CONSULTANT%20CONTRACTs_last%20night!_12_02_2009_1127am.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/CommVault%20Redactions/RE_%20Temp%20classification%20is%20here!_02_08_2011_1130am.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/CommVault%20Redactions/RE_%20CONSULTANT%20CONTRACTs_last%20night!_12_02_2009_1132am.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/CommVault%20Redactions/RE_%20News%20from%20Mileage%20Based%20User%20Fee%20Alliance%20(MBUFA)_04_11_2011_309pm.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...

/////////////////

Here is the MD5 hashes for all these files. (for fingerprinting/verification of file uniqueness, accept no substitutes). There are a bunch of apparently empty emails in "redactions" directories - or going to try another PDF reader to see if something is hiding.

a1541603442a1f0a6c2c7487c947e35b Hansen, Nathan 4_20_2011.xlsx

dfc0fd1d4d6bdbcaf0498a50ee0f5fec Public CommVault.pdf 1.22 GB on disk (1,216,990,533 bytes)

cec386cc20000b7fe10297fc3ca0cdab Public QAM.pdf 1.7 GB on disk (1,698,431,132 bytes)

$ cd QAM\ Redactions/

$ md5sum *

2bd53b4d4cfdf5735c6acb3d78dcac68 6_5_07 Commissioner's Staff Meeting Minutes.pdf

ac02fb8d2d000af38df63e9d6804a5bd 6_5_07 Commissioner's Staff Meeting Minutes2.pdf

bb562e176106b9436968ec57312fd74c Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes - No major issues FYI.pdf

cbbb2e9d9d81892a865d6539216d768c Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes.pdf

5294e1ef211a8a2de42749ab525b53ff Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes10.pdf

dba29ffb9fc67b3a389dbfc7e67ea8f7 Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes11.pdf

e77272f7a0b33506dbf7e284f553bc58 Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes12.pdf

8b0f53991f8b62fc2d1c92407839a4cc Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes13.pdf

a6b449f524250717b8fcdbac45abe537 Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes14.pdf

c0b806598d33db35b25a167558e61dca Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes15.pdf

3243ea3f27b71c5da5d8aa146033fd45 Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes16.pdf

091a17b9fd52dcb52f8ee9f2e1087426 Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes17.pdf

61f4122e7d61e84099bcd39479c389a0 Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes18.pdf

f8537cda72dc63a7dd3e6fd5bdf96f80 Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes19.pdf

1dc010c5ff89962ae132c242d99cdd4e Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes2.pdf

d005b7b9edf6acf4046e57f0f157b098 Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes20.pdf

0b9c231b2a572b29bc0b26e533b49416 Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes21.pdf

9234a884059b1667134a3a60438da49d Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes22.pdf

16095da57ce2c90ab73ea3acb470231a Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes23.pdf

e834fc715abed962a5926db379b7d47b Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes24.pdf

44bc416f5ed69a62dbc3284bddf45be4 Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes25.pdf

93db674814645af1a9b2e3b86e0cedbb Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes26.pdf

7dfb0294d4e9916117d48f87399396b4 Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes27.pdf

0d1e549ec6911fb272c273cc9cdb85d2 Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes28.pdf

af0b4c77b40a92f007f6de0937689666 Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes29.pdf

14ad0e9eaf2a1ec784a7f64a4677d1fd Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes3.pdf

eb3c3a2ab081cd011cb8dc3cc4220c17 Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes30.pdf

babb6166d521b7bd5e3da38e549101b9 Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes31.pdf

faa33837481a7ea9ce5389301005d276 Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes4.pdf

ec283884cf4eb57c1902f554c6daf88a Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes5.pdf

fd3955363a06c5e4f073b9a0eb685dce Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes6.pdf

9bb8bb439de8ebd31245d9e5c8039ba1 Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes7.pdf

7e8d8bf30cb1979c98d26b68f74b4354 Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes8.pdf

5e691539c7ab6721cd39e1739a63c977 Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes9.pdf

eaf5422b97c8ada9bc1a2e2eebfef0bf Fwd_ MNDOT_DOCS-#573688-v3-MBUF_EXEC_SUMM.DOC.pdf

17f5832daf02053ece137906874516a2 Fwd_ Re_ CANCELED TONIGHT.pdf

4324e83ef735d5e77d99dfd22044224f Fwd_ Re_ Contract 90815 with The Dieringer Research Group; Mileage Based User Fee et al.pdf

3b7488cce7ecd2166663f08279cfc3dd Fwd_ Russian exchange program.pdf

fdd5552a9a0a29ea87998d4836e80e96 RE_ Dieringer Pre-Award---IMPORTANT!!!!.pdf

d0658a06b65516fca4053fc9b36ecb8c RE_ Dieringer Pre-Award---IMPORTANT!!!!3.pdf

0dbcad4857d9b6403a2e853cd78c6972 RE_ Dieringer Pre-Award.pdf

a1d456e7e7b594fe400f3848aa11e98c RE_ Dieringer Pre-Award3.pdf

6fd5adfd694451487ccdf26373eeab55 Ray's requests.pdf

39468301435c56e3ec93fc588c92819a Re_ Fwd_ Fox 9 follow up.pdf

58e487d24be75a7d253941dde63b08fc Re_ Fwd_ UPA.pdf

f01b3471912eedfdba901c0c593de83a Re_ Fwd_ UPA2.pdf

d3b3a8c4347947539ca68b1e9c1d6e51 Re_ MBUF_ Invoice Questions.pdf

b063347fb895a472d4dbfd830646ddad r_Final payment on MBUF.pdf

d215cb89c3fd54140daf25b9ef8284ce r_MBUF Session at Research Conference.pdf

5b355449e4377a26817cd4c6811596bf r_MBUF_EXEC_SUMM.DOC.pdf

62531bda63cf387a9af54c603c485f05 r_MNDOT_DOCS-#573688-v3-MBUF_EXEC_SUMM.DOC.pdf

9d58ff05a42d717ab21fb16b025ae57a r_One-pager on MBUF.pdf

00498befc398512b83fd12a504885117 r_RE_ Couple quick thoughts for the morning....pdf

f7f56814799552a8c7623a05651abf6a r_RE_ Dieringer Pre-Award---IMPORTANT!!!!2.pdf

21f3cd6184330313fd4c968a7f028cbd r_RE_ Dieringer Pre-Award2.pdf

44b00634488d6c0a4047f001d0458fe0 r_RE_ EGADS___.pdf

ab4a3171454d293faf05282fd2d83eec r_RE_ Help_!_.pdf

0fd3fb1e29875e32749ea7c14c04c3f4 r_RE_ RE_ MBUF 3 Informational Materials.doc.pdf

326fc5ab634d7bfedb4c1bb5f301f2c0 r_RE_ Revised Proposal.pdf

4653657972f849fd9a1c7054079d000c r_RE_ Weighting issue_ new thought_.pdf

c61c3d6a1ef1be417f9d00c7be8b77cb r_RE_ dang, did it again.....pdf

91179ab7d3629f5762bd8e18ab4afca5 r_RE_ tomorrow_ or... in the meantime....pdf

08d3bea45066ef0c5d509828947797d8 r_RFI Responses.pdf

e507c028247157bf0860a7ed793f429a r_RFI Responses2.pdf

9cb9fe08acb375b3ddfbedfb27c640fe r_RFI Responses3.pdf

3d9ee0668e57b78f837885a77e7afe80 r_Re_ WANT INPUT FROM RW_KM- Re_ Notes from the second pretest.pdf

477daab48437d06bbc3d48763f849c09 r_Re_ Any MBUF updates_.pdf

5db8f9421c5edf2810be6964febc0d4c r_Re_ Budget review.pdf

4606fdd159fd22f59b610edfddd6e8ca r_Re_ Checking in.....pdf

51f6f0c7e5b327a6378b96dc2d0ba936 r_Re_ Contract 90815 with The Dieringer Research Group; Mileage Based User Fee et al.pdf

4ab4226505ba43336ca2ddfb864de016 r_Re_ Contract 90815 with The Dieringer Research Group; Mileage Based User Fee et al2.pdf

c980c15aa1358178a1766ce97f04f090 r_Re_ Contract 90815 with The Dieringer Research Group; Mileage Based User Fee et al3.pdf

37258df0b414af50f8c64d51e0bcf500 r_Re_ Contract 93707.pdf

63c77560c995c1f95af81637e25a0cbf r_Re_ Div. Directors.pdf

fb76beed27f4086fc713c6d6bc59159c r_Re_ Final payment on MBUF.pdf

0c045b993642661cfc57e47d2998f539 r_Re_ Focus Groups_ MBUF.pdf

13369f6c2c7d1f15947be9f5451ecf3e r_Re_ MBUF FAQ.pdf

c0f66f0d95a6bb505dfe5a152f4a6d04 r_Re_ MBUF FAQ2.pdf

6768b6bb46892736ca405151827dc3e1 r_Re_ MBUF FAQ3.pdf

5548eb744fdefe5edc438d777aee0e7b r_Re_ MBUF Posting.pdf

f452cc41fb449ac5a532fe69e36f9aae r_Re_ MBUF TRB Paper.pdf

fdc671465cca77c1ac28c624c66eec60 r_Re_ MBUF TRB Paper2.pdf

15fdbfc26e9c1d7d1d75bebf19bd3d4b r_Re_ MBUF TRB Paper3.pdf

f9064a7d54b55dbdfee12201f5a6d6fb r_Re_ MBUF TRB Paper4.pdf

1ea6c324c4810a187fbb466f090e9dc8 r_Re_ MBUF TRB Paper5.pdf

ee2bf6d95d1dde47efad543d7fcd72f7 r_Re_ MNDOT_MBUF Discussion guide v2.DOC (Lucy's out of the office ).pdf

908d43977c57905893b1876c3743680b r_Re_ MNDOT_MBUF Discussion guide v2.DOC.pdf

c953af1a4399e1c7186b760163d22cf4 r_Re_ PAYD Market Research.pdf

2c3ff87a050058633837b932e27ffdf3 r_Re_ Presentation of MBUF Public Perceptions Study.pdf

ab603f4bed9c05693a38a2fbbbfab8dd r_Re_ RFP Questions - 3.pdf

971fa164a5f7b261c89828bf7abc9396 r_Re_ What time do you think you will go to lunch__.pdf

1322615f623d2ad114f056d96ac22800 r_Re_ What time do you think you will go to lunch__2.pdf

2e4cac2496e0ae647c75c03336ea1365 r_Re_ What time do you think you will go to lunch__3.pdf

d1cc38d07c46de1d9603c9d0e34c9e46 r_Re_ checking on your status.pdf

b0ee689930c73f8f899ef89dc65996b0 r_Re_ project status.pdf

d98803d63a7121d7475fa402037bde55 r_Re_ project status2.pdf

75339d3c33fa450cde6aeb9f61d4cf46 r_Revised Proposal.pdf

2b719b5df5c7e94cb4c254a923a77029 r_Selection Committee (Just In Case) .pdf

9b858373c2c295719101426381877004 r_This should do it!.pdf

3e0a41234df919fc5748fb0f3733f5a0 r_This should do it!2.pdf

3c0202bf34f06fca292a363ded23d808 r_Travel Authorization Signatures.pdf

4ff5b016ecab1a8194ba82d1f3166166 r_What time do you think you will go to lunch__4.pdf

f9b137390f0e4be87d0eacc412e55cbf r_headin' home with MBUF as my bedmate....pdf

74da3639cfd3c5cad57a802cfb571df6 r_last Friday....pdf

8a720e445fbd86bae91c273b7ee94bec r_meeting today.pdf

01517f469063f9f88b231abbf3c60fe0 r_phone for 27th and 28th....and a TIP! _).pdf

1893859cb7ef79f3e8edeaa57e6d40bc r_to hear the second pretest interviews_.pdf

ec21dda39b263e35e15ffa1a7106e3d7 r_up and taking nourishment _).pdf

$ cd ../CommVault\ Redactions/

$ md5sum *

4526805e569ac612e8b47e0baa0f18c5 Bernie Lieder Update_04_12_2011_316pm.pdf

965a35632c7ee3c5b4a77953c819b6e7 Email address_04_19_2011_152pm.pdf

ea00a30ddde74758dfb632444ee17554 FW_ MBUF Online Community_02_14_2011_122pm.pdf

c30785e48c44ab468535c835ea8808ca FW_ MBUF Symposium & PAYD Insurance_03_23_2010_1002am.pdf

ae3f69040f670c509ed143bf937abeb6 FW_ MBUF_12_10_2010_1006am.pdf

1f217b45f730ab22fa987aec48ec1797 FW_ MnDOT Snapshot - Reaching Older Generations_02_23_2011_1143am.pdf

6c04c8b976f6c6615aaf1f3e553eef4a FW_ Mn_DOT MBUF RFP_08_10_2010_1032pm.pdf

be0486bbafba485cf73e797cf57cce1d FW_ TRB_01_06_2011_1148am.pdf

5dd29c7fdc005ea0d1872b7b50db4f9c FW_ Temp classification Ready for your review_11_17_2010_330pm.pdf

da1c6529e24b3aeb622e465810d2493d FW_ Terminology for legislation_12_02_2010_832am.pdf

60526ffba0b83ed3ca2de4b1d0ee4d93 FW_ US-2 Alternative Risk Analysis_12_02_2009_126pm.pdf

356efd4378b9f723631510c6da3ab9ec FW_ my schedule_06_02_2010_339pm.pdf

8134913b6cb4291df781450444fad923 Fw_ MBUF project name_03_18_2011_405pm.pdf

4806c46d5527908e4f5d6d69ecc3fb9e Fw_ MnDOT Snapshot - Reaching Older Generations_02_23_2011_358pm.pdf

03a2a1ca03c16fb5b1cbec671111a729 Fw_ TRB_01_06_2011_937am.pdf

14db70ba2b1af71c30c850b9a6470dd5 Hansen, Nathan 4_20_2011.xlsx

abb315692a9475591a3f3ebebb2ca0df I-394_05_20_2010_848am.pdf

484c3fad46b8460e8cc8e024d44b2eda Letter to Administration and IPAD_02_21_2011_221PM.pdf

30f936b3baf79c8a3f4adf0c37b9cd17 MBUF Exec Summ in one pager template.docx_02_24_2010_139pm.pdf

54447e231cc5e7d1d12d52cfcb2cb51e MBUF Online Community_02_11_2011_1223pm.pdf

8144d33f994c47817ec2ea44e06ec98a MBUF Project_02_08_2011_143pm.pdf

b27c2fdf06cd476d21c4e66b772d3fb1 MBUF_10_22_2010_839am.pdf

be348e1362ac6ccece5756bcf754d3f1 MBUF_11_30_2009_1013am.pdf

c4b6a0285baa57dfd06cc49e19228773 Mbuf name_02_23_2011_1141am.pdf

274c29d8c6e94608478aa42efaad281e MnDOT & Communispace weekly call agenda_02_25_2011_919am1.pdf

71d3478d4d6332dc22e6c575ef2e0512 MnDOT & Communispace weekly call agenda_02_25_2011_919am2.pdf

39d76453ecd31324635d95e3891e9d13 MnDOT Snapshot - Reaching Older Generations_02_22_2011_943am.pdf

671fe8c19a2f81667a52fe78075655b1 MnDOT Snapshot - Reaching Older Generations_02_22_2011_944am.pdf

b135755acaa77b327ddd2f8339179b0c RECEIVED!! _) MBUF Presentation Draft_11_16_2009_415pm.pdf

886befdaa2332b043dc63e9800f8f6f6 RE_ CONSULTANT CONTRACT EXPIRATION ALERT_12_01_2009_1035am.pdf

d63301b6ab7408fd335ecd01c22bfba9 RE_ CONSULTANT CONTRACT EXPIRATION ALERT_12_01_2009_1059am.pdf

c3c35a0da620de7e9fabf3e281b33cd1 RE_ CONSULTANT CONTRACTs_last night!_12_02_2009_1127am.pdf

66c4c8e5721a887186ef32c29e24ff93 RE_ CONSULTANT CONTRACTs_last night!_12_02_2009_1132am.pdf

78d6d6ef56ecfc67fcaf61e5a332127a RE_ I-394_05_20_2010_902am.pdf

05df7eaf8b317c80f13820f1e1cee14b RE_ IntelliDrive MBUF Project_12_16_2009_333pm.pdf

2b7f16e797a7a0c6ad62c7ed1333b8f5 RE_ IntelliDrive MBUF Project_12_16_2009_810am.pdf

9a0cec08313abcf1c9ca70c658f80e14 RE_ Letter to Administration and IPAD_02_22_2011_927AM.pdf

e30e6e048ba92ef1a599a2600bd6498f RE_ MBUF Exec Summ in one pager template.docx_02_24_2010_154pm.pdf

70c7b32debe5a55e2f8f2d67bebb76b8 RE_ MBUF Focus Group_01_17_2011_511pm.pdf

50e47e4450bab89d5500f5eb35a036a4 RE_ MBUF Online Community_02_11_2011_1225pm.pdf

92fcfc9630992a333dc3b46bd48732c4 RE_ MBUF Online Community_02_11_2011_1231pm.pdf

f027c45acab6e57b1d36e24d0ee93772 RE_ MBUF Online Community_02_15_2011_1100am.pdf

a1b6ce5cde68ea77a9c23c95ea8dcb9a RE_ MBUF Online Community_02_15_2011_1129am.pdf

deb5838863a641688c6e7c85ece7b5db RE_ MBUF Policy Kick-Off Meeting_12_01_2010_1236pm.pdf

7899b2e46e7bbc1d7d3dab6b67204ef8 RE_ MBUF Policy Study Draft Online Survey Approach_02_03_2011_1206pm.pdf

04a3bd71953c8a3116c6d5302d71b583 RE_ MBUF news release going out today_04_18_2011_419pm.pdf

0f97d747bd627273951ae52d9f47af52 RE_ MBUF news release going out today_04_18_2011_506pm.pdf

5d7c9d7b938d012327ad74e8adc1c6ef RE_ MBUF news release going out today_04_18_2011_603pm.pdf

1108a01bc5647242129db848b1968ad0 RE_ MBUF project name_03_18_2011_424pm.pdf

9d04bdc4f3d47bd9aa6a42cc86e8111c RE_ MBUF project name_03_18_2011_425pm.pdf

e1b29a363a67381a2bf62b520b81c54b RE_ MBUFF meeting today; cancelling_04_15_2011_215pm.pdf

2b62cff8e2356af2367a533757fecd3c RE_ MBUFF meeting today; cancelling_04_18_2011_830am.pdf

8c6f28f8bfad5e6269be821d90a38ef3 RE_ MBUF_11_30_2009_1149am.pdf

e44110f22e541bd4e66165e507305409 RE_ MBUF_12_10_2010_1103am.pdf

999925ec95ed3a13e110e798bf1555c1 RE_ MBUF_12_10_2010_1111am.pdf

27a82743582cefc14bb61353f8551a06 RE_ MBUF_12_10_2010_950am.pdf

27956fe15cf55ca0c7f0287b03148ea6 RE_ MBUF_12_10_2010_953am.pdf

81af256a23a3809ff8bb8d622b70d4a0 RE_ MBUF_12_10_2010_954am.pdf

3e13a81758d56493a83f5c7428ed370b RE_ MBUF_12_10_2010_955am.pdf

19d4fb79563af9ee4d8fdd44b9ee2508 RE_ MBUF_12_10_2010_957am.pdf

f9f6f496419b156db9f74f4f7683f83b RE_ MNDOT & Communispace weekly call - 2_15_02_17_2011_236pm.pdf

5b8361f64e68eab5c8a8342fbcfda50d RE_ Mbuf name_02_23_2011_1144am.pdf

006f09322d12e50fb6f0f819bea23fbe RE_ Media contact-mileage based user fee_04_19_2011_319pm.pdf

f1ee5606964818951a6c908260505a4a RE_ MnDOT & Communispace weekly call agenda - NOTES_02_28_2011_957am1.pdf

cb9614632da4c99f2b63cab39767a502 RE_ MnDOT & Communispace weekly call agenda - NOTES_02_28_2011_957am2.pdf

dc0c94c5bda4f38f9b50e5bbee1adeb1 RE_ MnDOT Snapshot - Reaching Older Generations_02_22_2011_504pm.pdf

4700a7736adc778ff83d49f14c6ab184 RE_ MnDOT Snapshot - Reaching Older Generations_02_23_2011_1153am.pdf

7ab57aca29541ad59aa8cb4aa735396d RE_ MnDOT Snapshot - Reaching Older Generations_02_23_2011_12483.pdf

e8021d8f7e3afdd8629541fd1a9b0cc3 RE_ MnDOT Snapshot - Reaching Older Generations_02_23_2011_1248pm.pdf

fa54ec8e94bf5fb5cdbe3fa6e1c4db9f RE_ MnDOT Snapshot - Reaching Older Generations_02_23_2011_1248pm2.pdf

3218af37335c0e06c3f3b9a011b19e39 RE_ MnDOT Snapshot - Reaching Older Generations_02_23_2011_328pm.pdf

eb696b4ffeee4e306e2eb7e484bba2d6 RE_ MnDOT Snapshot - Reaching Older Generations_02_23_2011_331pm.pdf

2dd4f45c1331c9db6bc6ad13cad669e7 RE_ MnDOT Snapshot - Reaching Older Generations_02_23_2011_331pm2.pdf

6dcab9c1d50ee4793d1c2f50ac5c1aac RE_ Mn_DOT MBUF RFP_08_11_2010_1031am.pdf

8d4ac4b9986a2dee1ebdf640cc241aa4 RE_ News from Mileage Based User Fee Alliance (MBUFA)_04_11_2011_309pm.pdf

e210a430bee280107a58c426d63a4bdd RE_ Next steps_Action Planning_12_03_2009_124pm.pdf

dd51eb0f42aea93f113ff5753b23f7f5 RE_ TRB Presentation_01_28_2011_125pm.pdf

4dc9010d0d7df27e8d5dd8689beebd0b RE_ TRB Presentation_01_28_2011_133pm.pdf

f910d3770ae1253cb5a096f9fc89be26 RE_ TRB_01_05_2011_543pm.pdf

3559e8bf7034bd767690c270c54aa1d8 RE_ TRB_01_06_2011_1111am.pdf

be8de9d4e1d3f82ab1a7567cbbbd0db2 RE_ TRB_01_06_2011_1116am.pdf

276086ae4495d14e7cbb077238747743 RE_ TRB_01_06_2011_1136am.pdf

de5827e592a282eea1853abaf717bc0d RE_ TRB_01_07_2011_840am.pdf

1e20ee8d269538d3c51f1e4a394813a9 RE_ TRB_01_07_2011_848am.pdf

29bbb01ead3b247be765ae31ccc4af0b RE_ TRB_01_24_2011_450pm.pdf

b44878a8ba14e90d657e411ad8d6f3f8 RE_ TRB_01_26_2011_620am.pdf

0c08f27a10d2e6df4d0562d7a6f1c0ff RE_ TRB_01_26_2011_801am.pdf

76495b1ee7bf01d8cd82d00f844a3df4 RE_ Temp class_02_17_2011_412pm.pdf

2f0318acfd3b1dcb960d5ea3a58a3264 RE_ Temp classification Ready for your review_11_17_2010_636pm.pdf

920a5c9704de481feb63d517712c1bbc RE_ Temp classification Ready for your review_11_18_2010_1105am.pdf

91d9a6e0ecaccd8038d737fb9e018548 RE_ Temp classification is here!_02_08_2011_1130am.pdf

f00a78733245cdb151b70161e8b0c6c6 RE_ Temp classification is here!_02_08_2011_1141am.pdf

88084dd4767ce27fb1c98cab13fe86c8 RE_ Temp classification is here!_02_09_2011_128pm.pdf

325966f645ec703d7da2d357249d6678 RE_ Temp classification is here!_02_09_2011_133pm.pdf

5c900f9cadf4e5037c0cd14da33e283c RE_ Temp classification is here!_02_09_2011_136pm.pdf

eb559b717547c18aa1ce5de7f4a334fb RE_ This AM_06_11_2010_934am.pdf

1d52160c492897b3bca16ee9df7ffa8b RE_ VM yesterday_12_05_2009_1131am.pdf

6be20bbfc07fe87eaecab816bc64e9dc RE_ another version of the policy study overview_01_07_2011_835am.pdf

3eebed34ca6fdfd6224366da55a0364e RE_ another version of the policy study overview_01_07_2011_932am.pdf

221e425208d0c9dea2da17e21cedaf78 Re_ 2010 MBUF Symposium Call March 12, 3 p.m. Central time_02_27_2010_1006am.pdf

4a7ad39b42e8063a51090e4dfc4c9ac3 Re_ Jon H.2_01_05_2011_759am.pdf

bf84169642681c0393244cbdb2661a3e Re_ Jon H._01_05_2011_838am.pdfbf84169642681c0393244cbdb2661a3e Re_ Jon H._01_05_2011_838am.pdf

ec3787db74d4c1110113c0b45f0a355e Re_ Letter to Administration and IPAD_02_22_2011_155PM.pdf

7cb7973b2280ba2688b13512ebcb7625 Re_ MBUF Policy Meeting_03_02_2011_215pm.pdf

739ed2f8cadb31733edb0fdfd97f04e7 Re_ MBUF_03_31_2011_714pm.pdf

5cabfd708b4c7a48068bcb609c853d79 Re_ MBUF_03_31_2011_824pm.pdf

4ee94529b2e9ec85f9f64693e0dff2cf Re_ MBUF_12_09_2010_911pm.pdf

2ea238fe33918e7b7eebc5ac7ec96c1e Re_ MBUF_12_10_2010_1047am.pdf

5baa528dfaecef9cd4ed408f2d94a650 Re_ MBUF_12_13_2010_746am.pdf

f7adb768801ba9af6150f1cbc9053a97 Re_ MnDOT Snapshot - Reaching Older Generations_02_23_2011_155pm.pdf

8bc02ad9e7444b670486bc1fc4f1fb2c Re_ MnDOT Snapshot - Reaching Older Generations_02_23_2011_323pm.pdf

36fdd9e21207b2267c0d13fbb8baad70 Re_ TRB_01_25_2011_148pm.pdf

7c3a94657f2afb64691f52ede7db19cb Shortened Presentation draft_11_18_2009_104pm.pdf

e82b4a99ead5133167d892c292950a64 Temp classification citations and final Attachment _11_18_2010_146pm.pdf

e3a1eb76c041f03400532d26a93c01b7 Temp classification_11_09_2010_420pm.pdf

f35b892dcd07cae5ef763765ec8e8989 VM yesterday_12_05_2009_718am.pdf

ad284dd91760b55caa43d94947bcb309 my notes from focus group_07_15_2010_1042pm.pdf

5ec009dc1d2b30fd7180043d71e431d2 my schedule_06_01_2010_306pm.pdf

df2c566cec38e930b2fc0b89c5467048 note changes per my vm on your cell...._07_22_2010_1142am.pdf

adcbf8b475c7158e8800c223e06b1783 r_VPPP Grant Apps_02_03_2011_905am.pdf

2bc792828e021379bd6508c0a8e5e808 your 3905 and 3924_ classifying data_12_21_2010_403pm.pdf

$ cd ../QAM\ Redactions/Attachments/

$ md5sum *

3fd8f0f9226e7b23383fb4e9820800ef r_0584_001.pdf

5fe5e205e8c9673a577d2acb389fbbd7 r_09xxx Dieringer 2009 FHR Cost Detail.pdf

8b56f9fb39fa8b7a6d58e2b2da23776c r_09xxx Dieringer 2009 FHR Cost Detail_for revi.pdf

e22812037eada83aecf6311eb08a7b4a r_1.30.07 Commissioners Staff Meeting Minutes.pdf

f713229f7f300f227589bd89aaad2002 r_2.06.07 Commissioners Staff Meeting Minutes.pdf

f3375414fc619ee175b5dc224a5e07a1 r_2.13.07 Commissioners Staff Meeting Minutes.pdf

22f6f34e84981638ffa263c1f5a434fd r_6 5 07 Commissioner's Staff Meeting Minutes.pdf

52a28aea5fffa90a906a41dd04d6ea5c r_Addresses_2009.pdf

8c31824d4de7622ffcffaf8d4a44fcd4 r_Fwd_ Re_ CANCELED TONIGHT.pdf

d52b1e9786833b3d758a0e642afd0507 r_Grants-dot-gov-20070522131848652_1.pdf

cf02b8b051229580d130fadce52e7a67 r_MNDOT_DOCS-#573688-v3-MBUF_EXEC_SUMM.DOC.pdf

0298e9beac45b9d02e9c3c5f3e4fae96 r_Re_ Contract 90815 with The Dieringer Research Group; Mileage Based User Fee et al.pdf

///////////////////

More on this as stuff develops. Happy tracker hunting!

MK Occupy Minnesota: The Drug Recognition Evaluator BCA Investigation files

By Dan Feidt -- hongpong.com -- MINNEAPOLIS -- NOV 12 2012 -- Law enforcement officers under a state training program called Drug Recognition Evaluators encouraged people in downtown Minneapolis, including Occupy Minnesota protesters at Peavey Plaza and other vulnerable and houseless people to participate in alcohol and drug intoxication evaluations. After a 35-minute video "MK Occupy Minnesota" [produced by Occupy Minneapolis, Communities United Against Police Brutality, Rogue Media & Twin Cities Indymedia] was released documenting claims of several DRE participants they'd been given drugs and encouraged to take drugs, an officer from Hutchinson, MN, stepped forward to corroborate part of that story.

UPDATE Nov 28: For a DRE training manual & a few other docs see the update. Thanks to CityPages for doing a whole series of posts including an interview.

Mn Bureau of Criminal Apprehension under the Department of Public Safety, generated a 513-page investigative report described in Minnesota Public Radio & Star Tribune stories, but not available publicly in full until now, adding another chunk to this incomplete story from one of the many gray areas in the war on drugs & the suppression of Occupy protesters.

New BCA Report URL: http://hongpong.com/files/dre/DRE-investigation-BCA.pdf (78MB)

May 3: http://www.hongpong.com/archives/2012/05/03/mk-occupy-minnesota-drugs-dre-program-peavey-plaza


Original video: http://www.youtube.com/watch?v=vTgN17FZGKE MK Occupy Minnesota: Drugs & the DRE Program at Peavey Plaza - May 2 2012 - 155,777 views @ Nov 12 2012

SCRIBD URL: http://www.scribd.com/doc/112922193/DRE-Investigation-BCA

DRE Investigation BCA

This BCA report, a compilation of interviews, correspondence & law enforcement & their lawyers refusing to answer the BCA's questions about DRE, raises many questions. Besides the claims of the Occupy protesters, many unethical practices including cash for participation, discussing gaining "leverage" over "volunteers" by threatening to arrest them (pg 76), not having an ambulance near where people were encouraged to take drugs at the gravel pit in Richfield near the MnDOT garage, no waivers, the explicit suspending of state drug laws for a privately organized certification program (pg 91, 99), etc.

Many of the officers discuss a general sense of unease across their entire class, of trespassing certain obvious moral or ethical boundaries ('your morals are gone', pg 428). As Minneapolis considers dissolving the Civilian Review Authority oversight board, many connections to the Minneapolis Police Department including the 5th Precinct have not been reviewed.

Other items include: a BCA AT&T phone subpoena to trace phone/SMS activity by one of the officers involved, and more on the International Association of Chiefs of Police (IACP) role in the program (pg 223, 231) -- as an officer discusses, they're called "evaluators" rather than "experts" because the courts don't really recognize it (pg 202). IACP receives large donations from major defense contractors to promote local police policies expanding biometrics & surveillance, war-on-terror tech deployed at home, mass incarceration and intensifying the war on drugs. The IACP has managed to impose this pseudo-legal yet scientifically unproven framework, the DRE, with its morally abhorrent training program, on many states besides Minnesota.

In the end of this phase, the Hennepin County Attorney's office ruled out filing charges after so many officers stonewalled (pg 54-57) [as the Strib noted, some of the same same legal operations used by the disgraced Metro Gang Strike Force officers]. Pages significant to documenting the way illegal government operations in Minnesota get papered over, the 'coverup machine' network of lawyered up law enforcement, listed below ('get everyone quiet', pg 367)-- and really, Hennepin concluded, unless an officer handed out a generous 42 grams in one sitting, it wouldn't be a felony crime.

While everything in this strange report should be taken critically, disturbing themes of emerge of relatively young rural police officers being sent around Minneapolis to find the chemically dependent & mentally ill, turn them loose again after they're intoxicated, without any help like medical or social support, and connections to further gray areas like developing informants in the drug world(pg 381), and a methamphetamine-addicted informant handled into performing an evaluation by a Ramsey County deputy.

Another key subject is the Donald Steven Turner interview (pg 485-492) wherein he describes not only his certainty that Occupiers were lying, he seemingly brags about giving a Minneapolis police officer he knows one person's name and then scaring them into jumping a train out of town, talking up his ability to develop 'profiles' on OccupyMN members, etc. While the authorities describe Turner as a credible OccupyMN member, he had a reputation for scuffling with people and being tossed from Occupy meetings, taking at least one bike, and other serious issues stretching back long before Occupy started in New York. This are some of the most jaded & disturbing statements I've ever seen documented, seemingly bragging about informing to spread fear. More interviews with others he affected are really needed to tell this particular story. Whether or not his statements have any validity, the damage to privacy of third parties he named has already been done in his statement to law enforcement -- unfortunately, redacting the first names Don put out there would do no good.

Voters showed last week they're becoming increasingly weary of the war on drugs, which has generated huge profits for lawyers, corporations, banks and Wall Street through laundered money. All this shadiness isn't a bug, it's a feature. Will Minnesota recognize the failure of the war on drugs and cancel abusive, unscientific programs like the DRE? Can Minnesota shift from punishment, coercion & incarceration to harm-reduction chemical dependency policies that treat everyone humanely?

[birthday/phone/contact info of people targeted by DRE was removed with black rectangles. This document did not arrive via government/data practices channels, and some other details, likely police personal details like cell phone & home addresses were apparently removed with marker probably by the BCA.]

For more information & work on similar issues please see the websites of groups involved in producing the initial MK Occupy Minnesota video:

Communities United Against Police Brutality - CUAPB.org - @CUAPB

roguemedia.org @roguemedia_org

OccupyMinneapolis.mn - @occupyMN

tc.indymedia.org @TCIMC

hongpong.com @hongpong

globalrevolution.tv @globalrevlive

---- This story and the original video MK Occupy Minnesota are licensed Creative Commons with Attribution --

--------

Here is shorthand for some interesting pages to check out further. Particular interesting pages marked with asterisks:

22 coverup

36 Hutchinson drug kit?

90 Munoz

42 coverup

49 Holiday parking lot lol

54-57 coverup

66 LDF coverup

76 using statutes for leverage to gain 'volunteers'

79 coverup

83 * "I just gave them marijuana it's not like I hurt anybody"

91 WTF instruction on illegal drugs?

99 WTF little to no instruction on street subjects

102 incentives "could offer them money"

105 "wink wink nod nod"

106 - why blank?

109 "I just gave them marijuana"

112 warnings about occupy minnesota / Munoz instruction after video

116 WTF

125 Telephone subpoena

129 Don Turner says occupiers lied about DRE

136 possible missing marijuana from Nobles Co evidence room?

140 Hennepin County Attorney CASE CLOSED summary

141 Hutchinson starts inquiry

142 Roster of police participants

148 players in International Association of Chiefs of Police (IACP)

152-153 *** the case - interview

154 **** disposing of the case

157 no independent medical personnel or ambulance nearby (even though drugs are being taken in area)

162 phone subpoena

163 drugs with volunteers

190-191 coverup

198 getting leverage on volunteers- threaten to arrest

202 definitions of 'expert' vs 'evaluator' - they aren't real 'experts' but IACP labels it

206 Munoz instructs not to hand out drugs after video is posted

208 Michelle Ness: "we kinda looked over to Peavey and we're like whoa concentration of potential clients"

217 Hutchinson PD evidence sheet

223-224 IACP control log & material

226 instructors watch all evaluations?

227-228 training schedule

231 IACP

232 "kidnapping" & volunteers

233 probation & volunteers, illegal/warrant issues

235 sketchiness 'it was odd'

239 offering cheeseburgers

241 occupy & video questions

244 national players in IACP / DRE

245 coverup lawyer

249 5th Precinct MPD connection

259 seizure

261 MPD 5th Pct

268 MPD 5th Pct

273 MPD & incentives advice

275 coverup lawyer

278 * Certificates & IACP

279 uneasy feeling for all students

286 Otterson - no instruction

287 "shitty areas"

288 occupy video day we took final exam / weed

289 call to MPD about beat-up guy

291 * direct supervisor for years

295 no independent medical presence or ambulance at MnDOT

297 IACP

305 specs for program change from 12 to 15 evals

309 MPD 5th Pct

310 No waivers for drug participants

311 Munoz says don't provide drugs after occupy video

315 "target area"

323 story about prostitute

325 MPD

335 blackmail "volunteers" via Minneapolis statutes: " get us copies of Minneapolis codes, um in case we saw people you know breaking any city ordinances and kinda use that as a way to get them to see that, you know you can come with us or you know Minneapolis"

340 certification goes via the IACP DRE national website (NOT 'real' state authority)

343 coverup

347 *** Willers narrative - confusion over brothers

348 MPD

354 MPD

357 fear of being recorded at Peavey Plaza

360 ok to buy cigarettes, cash, overlook state drug law etc

361 giving $$$

367-8 *** coverup Legal Defense Fund "get everyone quiet"

381 developing informants "a lot of times we never charged 'em. We said you know give us some info on who your source is"

385-386 Pete's box getting low

387-88 ** informants high on meth

389 smoking in the gravel pit

390 letting off warrant suspect, more suspension of law

391 officer had weed "a bag the officer had the marijuana in" ??

402 incentives

405 MPD

406 coercion of "volunteers"

412-413 woman who was "nuts" = no mental health support

414 using traffic stops & $ for "volunteers"

415 giving out beer

421 snitching: "We did a UA and ah they actually um they apparently he was gonna snitch out some people for drugs and guns"

426 getting desperate, offering a buffet

427 threat of jail

428 ** "your morals are gone"

429 "you can either go to jail for possession of the drugs or if you want to cooperate with us we'll give you a pass."

434 morals/instruction

439 giving out shooter glasses

443-445 getting high

447 odd redaction may be house address?

460 crimes at discretion

468-469 crack, pimp, Popeye's

470 a pimp / the jacket incident

471"it is weird. It is a weird class to go out and try to find someone high"

479 AT&T cell phone subpoena

485-492 *** Don Steven Turner interview

487-492 *** Don talks to MPD Mercil (Sp?) a lot

495 it's like a joint task force re expanded geographic arrest powers

496-497 smoking in Richfield

499 goodie bag MJ

501-513 final Hennepin County report

--
To reach the publisher of this file contact Dan Feidt at hongpong@hongpong.com or at twitter.com/hongpong.

EXCLUSIVE: Cointelpro Gothic II: Midwestern Police State Paranoia Continues! Winona & Des Moines hubs of spurious "terrorism" & great statistical accomplishments!

Iowa-American-Gothic-500.jpeg EARLIER: October 13, 2010: Cointelpro Gothic: Docs prove Iowa FBI's Wild Rose Rebellion a pretend RNC "Terrorism Enterprise" for great "statistical accomplishment"

BY DAN FEIDT -- Another level of the seemingly endless, unregulated Midwestern law enforcement campaign against political activists has been revealed in 525 pages obtained from the Department of Justice by Freedom of Information Act requests filed by David Goodner of Des Moines. (FULL PDF 62MB / Scribd.com)

Two related stories emerge: in 2004-2006, federal agents spurred to achieve career-advancing "statistical accomplishments" spied on people the G-Men linked with the CrimeThinc Anarchist publishing label -- in Des Moines and Winona, MN anyone linked to anything CrimeThinc is deemed a great target for further snooping.

Of course, in this file, the FBI deems CrimeThinc as a terrorist organization, a designation which they never have to account for to anyone. They never found any evidence of terrorism to charge anyone with any crimes, terrorism or otherwise, but this lack of 'real terrorism' only creates a gentle opportunity for career advancement without the risk of hassling any powerful people.

In 2006, FBI agents conducted a sweeping surveillance stakeout of a CrimeThinc meetup at the Winona, MN visitor's center, which has not been reported in detail until now. Since they've already labeled CrimeThinc a terrorist organization, they collect tons of precious "statistical accomplishments" merely for rationalizing their conclusions and defaming random people to local police officers.

Goodner previously obtained the 2008 Republican National Convention documents around the "WILD ROSE REBELLION" FBI investigation.

Separately, an addition batch of documents obtained by a member of Twin Cities Indymedia (via the MN Data Practices Act) about the East Metro WMD Task Force (available for viewing & download @ Scribd.com), which started shortly after September 11, 2001, reveals another layer of paranoid, baseless police activity targeting everyone from Somali immigrants to 2008 RNC protesters. Among many interesting documents, former Ramsey County Sheriff Bob Fletcher planned a strange wargame during the election, a kind of exercise designed to ascertain what they would do if terrorists gained control of elected officials.

-- Sorry no time for a more detailed writeup right now - please repost as you will. Creative Commons with Attribution! - hongpong@hongpong.com

TCIMC Exclusive: Contracts for IntelliDrive MnDOT Military-Industrial/U of M plan to GPS-track all cars

SAIC.png

Minnesota taxpayers give intelligence contractor SAIC a cost-plus contract to evaluate MnDOT's GPS tracking program!

By Dan Feidt for Twin Cities Indymedia – Key info about Minnesota's elusive "GPS Mileage Tax" test program has finally turned up. It's actually part of a federal program called "IntelliDrive", as shown by new documents obtained on Wednesday. The Minnesota Department of Transportation has entered into a pilot program called the "Mileage Based User Fee Policy Examination" which includes a contract with the huge low-profile military-industrial intelligence contractor SAIC of McLean Virginia, a system intended to pass all GPS data from everyday travel into centralized vehicle databases. The University of Minnesota has a main leading role, along with the Battelle Institute, URS Corporation, Mixon-Hill in Kansas and the local Pierce Pini & Associates. The MnDOT data practices "handler" at headquarters in St Paul didn't like it when these documents were photographed, and they denied a request to simply copy the mileage tax project contracts onto a USB flash drive, which is the only reason we don't have the complete material at hand right now.

With these incomplete documents, it's still perfectly clear that this plan is intended to make Minnesota's roads into a mere part of a national IntelliDrive road monitoring grid - broadcasting tracking devices would be intended for all vehicles.

Some legislators already made an attempt this week to cancel funding for this mileage tax pilot project, as the Star Tribune reported, and they don't seem to want more information to reach the public before the end of Minnesota's regular legislative session this weekend. After all, you could just tax mileage by having drivers report odometer readings every year. Tracking every vehicle's location at every moment is obviously not necessary unless the goal is about controlling the vehicles and collecting real-time information on everyone's activities. Will the Democratic Dayton Administration and legislators continue to support spending more cash they don't have on this totally unnecessary total vehicle tracking 'trial balloon' program?

Below the Fold: Behavior modification as "consumer satisfaction" contract deliverables; Contact info for Military-Industrial SAIC contractors building Minnesot'a branch of the IntelliDrive vehicle tracking system; University of Minnesota and SAIC contract info. The latest version of the big tracking system is all here. SAIC: All your 10,000 Lakes Plates GPS Coordinates are belong to us :-D

So what is the point of all this?saic-project-header.jpg Basically the program is obviously intended to convert Minnesota roadways into spaces managed by something called "IntelliDrive". It looks like SAIC and the rest of them are cashing in on these programs. The official agenda of IntelliDrive is provided below: implementing trackers on cars and fixed points to make a complete grid of everywhere you go. None of this is really about "mileage" measurement, which again is available via the good ol Odometer.

Overall the program is intended to convert our roads into "IntelliDrive" managed spaces, which means radio transmitters and/or GPS chips in cars, and many receivers tracking your location at all times. SAIC's role seems kind of "meta": the intelligence contractors control whether the project is evaluated positively or not. The SAIC contract's criteria for "satisfaction" are quite strange.

Another detail: Preliminary rules for government personal data handling under the Minnesota Data Practices Act have been created for this pilot program.

An 2007 study on public opinion about the mileage tax was conducted by the Dieringer Research Group on behalf of MnDOT's Value Pricing Program was done (PDF here). Negative citizen impressions included (p39):

Sounds a little bit sketchy with a “Big Brother” impression. – Metro High Efficiency participant

Big Brother is really watching. – Duluth General Public participant I disbelieve that it would be tamper proof. There are websites devoted to cracking/

hacking anything – Metro Peak Commuter participant

I do not support any implementation of equipment by the government on my privately owned vehicles. I can not support this type of system based on this type of subversive invasion. – Mankato High Miles participant

All of these are perfectly obvious concerns, especially since the DOJ Solicitor General has recently declared the federal government should always be able to plant law enforcement GPS systems on anyone's cars at any time without a warrant. With the IntelliDrive tracking apparatus, law enforcement would merely have to tap into remote databases run by SAIC or whoever. No more bulky special GPS trackers for Internet gadget geeks to pick apart.

**************

U of M MnDOT Contract No. 89261 Work Order No. 235: "Mileage Based User Fee Policy Examination"

MnDOT and the Regents of the University of Minnesota (via the Office of Sponsored Projects Administration at 450 McNamara Alumni Center) agree to furnish the Mileage Based User Fee Policy Examination project as a whole. They seem to be the masters of the project as a whole.

u-m-contract.jpg

Also the University of Minnesota apparently provided some electronic device in order to ensure the programs were not overlapping – could that be the car transmitter element? The U of M's ITS Institute would seemingly be involved - see the advocacy of MnDOT Commissioner Tom Sorel on ITS at a conference in April. Here is TechPlan, the policy program with the Humphrey School.

********

SAIC MnDOT Contract No. 92809 - also listed as CFMS Contract B230(unknown): "VII for Safety, Mobility and User Fee Evaluation"

saic-1.jpg

The major intelligence contractor SAIC – Science Applications International Corporation of McLean VA, is the "Evaluation Team" for the project. It has the title "VII for Safety, Mobility and User Fee Evaluation". It describes a main "Concept of Operations" (a military planning term) to be developed by a separate Technical Program Management Team contract. The Evaluation Team, SAIC, then determines how well the program is evaluated. VII seems to have meant "Vehicle Infrastructure Integration" and a fact sheet at this page recently vanished. The google cache is at the end of the article,

The contacts in the SAIC contract are:

saic-contacts.jpg

SAIC Team:

Mark R. Carter - Principal Investigator - mark.r.carter@saic.com

Vaughan Inman - Human Factors Lead

Jennifer A Rephlo - Customer Satisfaction Evaluation Lead - Jennifer.a.rephlo@saic.com

CH2M Hill Team:

Howard Preston, PE - Local Coordinator, Safety Evaluation Support - Howard.preston@ch2mhill.com - 651-365-8614

Tom Maze, PE, PhD - Safety Evaluation Lead - tmaze@iastate.edu - 515-294-9523

E-Squared Engineering Team:

Richard Easley - Technical Advisor on Electronic Revenue Collection and ITS Standards (unknown..) - 703-858-5588

The SAIC Evaluation Plan includes the following impressive recategorizations of behavior manipulation as what else, Customer Satisfaction!

saic-satisfaction.jpg

Customer Satisfaction:

System Awareness

Expectation of system benefits

System use

Response-decision-making and/or behavior change

Realization of benefits

Assessment of value

********

There is reference to the "RITA ITS Evaluation Resource Guide" (probably this) including "quantitiative change" in what appears to be driver behavior. Also it includes "implications of conforming to the National ITS Architecture" and the "National VII initiative" and "National ITS standards".

It appears a later Amendment to to the executed contract with SAIC, says the system called VII changed its name to "IntelliDrive" - a servicemarked name. MnDot "is currently developing their Intellidrive (formerly VII) for Safety Mobility and User Fee system in conjunction with the larger IntelliDrive national effort. As of June 30th 2009, Phase I was completed which included a concpet of operations, preliminary requrirements, a Phase II implementation scope of work and the preliminary evaluation plan. Mn/DOT expects The Contractor [SAIC] to conduct a final evaluation in Phase II to begin in 2010."

saic-amend.jpg

********

Mixon Hill contract: MnDOT Contract 92808: VII for Safety, Mobility and User Fee Technical Program Agreement with Mixon Hill, Incorporated.

mixon-hall-amended.jpg

"The Technical Program Management team was tasked with overall project management of Minnesota's VII (now IntelliDrive) initiative which includes project oversight, document review, technical support and coordination with the separately contracted Evaluation team. The Technical Project Mangement team had major deliverables for Phase I of the VII for Safety, Mobility and User Fee Project. A Concpet of Operations (ConOps), preliminary requirements and scope of work for the Phase II implementation.

The contract is being amended due to necessary revisions to Phase I tasks that fall within the original scope of the work. The University of Minnesota is currently planning a VMT [Vehicle Mileage Tax] project through Federal funds that will directly effect the development of IntelliDrive's eventual implementation. The State has reviewed the University's plan and has decided to incorporate a piece of hardware supplied by the University into their IntelliDrive project. The purpose of this hardware inclusion is to assure both projects are not competing with each other and to further the development of a sate-wide [SIC] IntelliDrive initiative.

********

Battelle Institute Contract - number not available.

battelle-contacts.jpg

Only the photograph of the contact information is available now, due to MnDOT's reluctance to share this file on Flash drive.

Battelle Team:

Bennett K. Pierce - Project/Program Manager - Office - 614-424-3905 - Fax - 614-458-3095 - pierceb@battelle.org

Matthew Burns - Principal Research Scientist

Robert Zimmer, CSEP - Senior Systems Engineer

URS Team:

Daryl Taavola, PE - Vice President - ITS and Traffic Engineering - Office - 612-373-6889 daryl_taavola@urscorp.org

Pierce Pini & Associates Team:

Peter Muehlbach - Safety Evaluation Lead - 763-537-1311 peter@piercepini.com

********

MnDOT tracking from NAFTRACS to IntelliDrive: Sadly this is all the hard MnDOT info we have right now, because of MnDOT's rather defensive on-site data handling practices. However all the remaining elements of the program fall under the Data Practices Act request that has been slowly going through the system.

Attorney Nathan Hansen says that four different main contracts were involved, as his photo shots show SAIC, University of Minnesota and Mixon Hill folders. The laptop he was presented with had no power supply, he said, and while the documents have been "produced" the agency representative asserted to Hansen that more fees would be required to get copies of these documents. Simply copying them onto a USB flash drive was not acceptable to the MnDOT person, Hansen said. He had no time to photograph proof of it Wednesday, but he said SAIC has a cost-plus contract with MnDOT.

This new IntelliDrive/SAIC turn has actually been a long time in the works. For years MnDOT has already been trying to implement corridor tracking systems with vendor help from the military-industrial complex. Hansen got spme access the new documents in a partial response to his data request posted on his website, along with material from years prior.

Hansen heard former Gov. Tim Pawlenty talking about vehicle tracking taxes years back, which spurred him to send data requests to MnDOT about tracking systems. Four years ago, when I was at Politics in Minnesota, Hansen brought me similar documents from MnDOT about a program called NAFTRACS run by the North American Super Corridor Coaliton, which turned out to be heavily funded by Lockheed Martin. Lockheed was spearheading a program to build an RFID tag-based tracking system based on their existing "Global Information Grid" (GIG) Pentagon tracking system.

Since then, apparently MnDOT's participation in NASCO and NAFTRACS pretty much ground to a halt – and more than a year ago a GOP senator told me that RFID readers were too obnoxious to set up. He chuckled that he'd been socially engineered into buying a hybrid car which gets better gas mileage, but now the state plan was to put in GPS tracking systems to tax his cars' mileage instead. Problem, reaction, solution.

Really, if the State of Minnesota is going to enter into contracts, the Attorney General should just post all contracts on the official websites. Hansen and I got to be good friends after working years ago on this strange highway tracking agenda – as well as the other ways military-industrial contractors are reshaping Minnesota through homeland security programs. If Hansen or people like him who are actually concerned about the direction of these authoritarian programs were in positions like attorney general or judges, county attorneys etc., maybe this stuff wouldn't be so aggressive, profitable and handled in secrecy. On the whole, these issues are more about authoritarianism vs freedom than left vs right.

The issues need to be raised in the formal election process as well as at every step, including the critical last days of the legislature, entirely out of money. Both parties aren't too concerned with the drift towards spending more on greater tracking, less privacy, and more ease for law enforcement and intelligence contractors to watch our every move. From Pawlenty to Dayton, the expensive surveillance policy complex continues to unfold without pause. Do Minnesotans really need to pay SAIC right now??

*******

What is ITS?? The system called "ITS" heralded in the contracts is "Intelligent Transportation Systems" according to US Department of Transportation's Research and Innovative Technology Administration. ITS is described as: Research and Innovative Technology Administration (RITA) - United States Department of Transportation (USDOT, US DOT or DOT):

The U.S. Department of Transportation's (USDOT) ITS research program focuses on intelligent vehicles, intelligent infrastructure and the creation of an intelligent transportation system through integration with and between these two components. The Federal ITS program supports the overall advancement of ITS through investments in major research initiatives, exploratory studies and a deployment support program. Increasingly, the Federal investments are directed at targets of opportunity – major initiatives – that have the potential for significant payoff in improving safety, mobility and productivity.

ITS Strategic Research Plan, 2010-2014

On December 8, 2009, the United States Department of Transportation (USDOT) released the Intelligent Transportation Systems (ITS) Strategic Research Plan, 2010-2014. This plan defines the strategic direction for the USDOT's ITS research program for the next five years and is designed to achieve a vision of a national, multi-modal surface transportation system that features a connected transportation environment among vehicles, the infrastructure and passengers’ portable devices. This connected environment will leverage technology to maximize safety, mobility and environmental performance.

Federal ITS Research Initiatives

At the core of Federal ITS research is connected vehicle research – a multimodal initiative that aims to enable safe, interoperable networked wireless communications among vehicles, the infrastructure, and passengers’ personal communications devices. This research leverages the potentially transformative capabilities of wireless technology to make surface transportation safer, smarter and greener. USDOT research supports the development and testing of connected vehicle technologies and applications to determine their potential benefits and costs. If successfully deployed, this smart communications between vehicles, and between vehicles and infrastructure, will ultimately enhance the safety, mobility and quality of life of all Americans, while helping to reduce the environmental impact of surface transportation.

More information about the USDOT IPS office is at: Research and Innovative Technology Administration (RITA) page. Also see press releases.

More about Mixon Hill: Not much info is on their site but there is a page about building tracking systems on I-95. As a contractor in Kansas they are probably in a good position to join these plans for Interstate GPS-based tracking systems. mixonhill.com/services/information_technology.html

More about Battellebattelle-front.jpg : This organization has a ton of military-industrial projects going. Their website has a huge list of things they are involved with just in National Security alone! See http://battelle.org/index.aspx // http://battelle.org/commercialization/index.aspx // and the index at: http://www.battelle.org/solutions/?Nav_Area=Solution&Nav_SectionID=4. Their stuff includes:

Adaptive Systems and Controls Armor & Protective Systems Assay Development Avionics CBRNE Response / Preparedness Chem Demil Plant Support Critical Infrastructure Protection Demilitarization Processes Electronics Environmental Technology Explosives / Energetics Fatigue / Life Prediction Fitness for Service Food Security Government Business Consulting Individual Equipment Information / Knowledge Management Infrastructure Protection Integrated Manufacturing Simulation Logistics Management Material Development / Selection Probabilistic Mechanics Residual Stress / Distortion Ruggedized Packaging Sensors Strategy & Organization Consulting Technical Manuals / Publications Technology Insertion Threat Assessment & Characterization Transit Safety & Security Transportation Safety and Security Undersea Technology

And total freeway tracking for MnDOT. Huzzah!
More about E-Squared Engineering: of Ashburn Virginia, dedicated to providing quality services in the Intelligent Transportation Systems" with similar contracts on news page. Interesting staff support services: Currently, E-Squared Engineering has Staff Support Services contracts with the following organizations: the Intelligent Transportation Society of America, the International Parking Institute (IPI), the Commercial Vehicle Safety Alliance(CVSA), the National Private Truck Council (NPTC), NACHA The Electronic Payments Association, and the Institute of Transportation Engineers (ITE).
More about Pierce Pini & Associates: A MN-based general civil engineering firm: ppa@piercepini.com 763.537.1311 10600 University Avenue NW, Suite 3B Coon Rapids MN. 100% Woman Owned Business established in 2003 and certified as such in the state. Pierce Pini & Associates, Inc.
poar01_spyagency0703.jpgMore about "Stealth Company" SAIC: More than half the 44,000 employees have security clearances. This is a really pretty important contractor with an impressive aura of national security weirdness, & deliberately low public profile. Here's their official history. They actually had a Remote Viewing (ie Staring at Goats style telepathy program) sent to them in 1991 called the StarGate Project. In 2002 they launched a huge important NSA program called Trailblazer and also failed to build a new FBI case file system in 2003. See also 2007 PBS report on failed projects and corruption .
See also SAIC's expansive role as intelligence contractors in legally dubious roles in Iraq: Washington's $8 Billion Shadow | Vanity Fair. SAIC is frequently found working with Booz Allen Hamilton in weird intelligence affairs. (Vanity Fair pic of McLean VA HQ by Coral von Zumwalt) Lead: "....the dark and ruthless corporation whose power extends into every cranny around the globe, whose technological expertise is without peer, whose secrets are unfathomable, whose riches defy calculation, and whose network of allies, in and out of government, is held together by webs of money, ambition, and fear.... If there were such a company—and, mind you, there isn't—it might look a lot like the largest government contractor you've never heard of:"
CH2MHill is a major global construction company based in Colorado. Tom Maze from Iowa State is part of their group on Safety issues evidently.
URS Corp: major contractor.
*******Let's Go Out with IntelliDrive and VII: The White Papers!
The final death of the great anonymous American drive is prescribed in the following white papers. For now we'll leave this article with most of the Intellidrive white paper text, and hope for a more properly informed public debate about spending money on having SAIC evaluate a Minnesota version of IntelliDrive when potholes, bridges, and many other concerns demand major funds.
Here is the 2010 IntelliDrive Roadmap via a supporting organization IntelliDrive Task Force - ITS America's Connected Vehicle Task Force Wikispace.
IntellidriveRoadmapofRoadmaps7-10_Page_1.jpg
DOT.GOV RITA | ITS | From VII to IntelliDrive White paper: [The images are broken]

Purpose of the White Paper

This white Paper traces the strategic evolution of the U.S. Department of Transportation’s (DOT’s) plans for IntelliDriveSM research. As this White Paper was being written, in Spring 2010, DOT was embarking on the ITS Strategic Research Plan, 2010-2014 - IntelliDrive research comprises a major portion of the research program. DOT recognizes the need to provide stakeholders with an explanation of the major strategic issues that drove the development of its current plans for IntelliDrive research, and an explanation of how, and when, the research results will enable decisions regarding the future development of IntelliDrive capabilities.

The VII Vision

Launched in the mid 1990s, with roots stemming back to earlier DOT research in the 1960s, the U.S. DOT ITS Program adapts emerging technology innovations to the needs of the surface transportation community. The ITS Program initially focused on applying processes and technologies that had been developed by the defense community - such as surveillance technologies and systems engineering - to transportation systems.

In the early 2000s, it became apparent to the DOT ITS Program and its partners that the interaction between vehicles (Vehicle to Vehicle or V2V) and between vehicles and the roadway (Vehicle to Infrastructure or V2I) held tremendous potential to address the highway safety problem and other difficult transportation challenges. Building from earlier ITS research, DOT launched the Vehicle-Infrastructure-Integration (VII) Program in 2003. The VII vision was to use wireless communication with and between vehicles to achieve dramatic safety and mobility improvements.

The VII program was rebranded as IntelliDriveSM in January 2009 - largely for communications purposes. The VII name was not readily understood outside of research circles and was easily confused with the Roman numeral for seven. However, the program has also undergone changes in concept from the original vision, due to initial research findings.

The VII Approach

Fundamentally, VII was an engineering research program. As the VII Program was originally conceived, V2V was recognized as a potentially powerful technology that could address many safety issues. While V2V promised dramatic safety gains, it was assumed at the time that achievement of maximum safety benefits would require all vehicles (cars, trucks and buses) to have radio devices installed to provide the necessary V2V communications capabilities. Unfortunately, it would take 15 to 20 years for the vehicle fleet to turn over so that a sufficient number of vehicles would be equipped with the V2V technology and start to yield tangible benefits.

Because of this fleet-turnover-timeline problem with V2V implementation, the VII Program planners concluded that an alternative approach was needed. In-vehicle devices talking with roadside infrastructure (V2I) was seen as a way to achieve safety benefits more quickly and address safety issues that V2V could not. The VII research program was based on the premise that infrastructure-based radios would achieve benefits – particularly safety benefits – sooner. The program was grounded in the need for a nationwide deployment of roadside infrastructure to support the communication with and between vehicles, while radios became prevalent in the new vehicle fleet.

In addition, in the VII approach, both V2V and V2I required a dedicated short-range communications (DSRC) radio tuned to the 5.9 GHz frequency in the vehicle and in the infrastructure. The Federal Communications Commission allocated, at the behest of the transportation community, 5.9GHz for transportation safety applications. This allocation gave the VII program the key technical requirement that would be needed for ultimate deployment. The spectrum was allocated for safety purposes, but it allowed unused bandwidth to be available for other applications, such as mobility or convenience. Preliminary indications were that safety messages would use only part of the communications bandwidth. As a result, non-safety applications, such as mobility and convenience applications, could also be accommodated through the same DSRC radio.

These assumptions - to start with V2I while V2V capabilities migrated gradually, and use of one DSRC radio at 5.9GHz for all applications - were a good starting point, but many questions remained. Would V2V and V2I work technically? Could these technologies be implemented practically?

Proof-of-Concept Test

First, DOT conducted a proof-of-concept (POC) test to address the basic technical feasibility questions. The POC, conducted in 2008 and 2009 in specially designed "test beds" located in Oakland County, Michigan and Palo Alto, California, was designed to validate the technical feasibility of key components of VII. For example, the first DSRC multi-channel radios were built for the test vehicles, and the first instrumented roadside equipment was placed at the test beds. The researchers conducted basic tests to assess the communication capabilities and characteristics of the DSRC radios and the 5.9GHz band. The POC testing proved that the basic technical concept would work. However, the POC test was never conceived as the answer to all technical questions. There were practical limitations regarding the scope of the tests. POC testing included less than 30 vehicles, and they represented only one vehicle type - light passenger vehicles. The testing focused on evaluation of message exchange between partially developed “stub” applications, using draft DSRC standards.

The POC testing accomplished much of the initial work necessary to determine that the concept was technically sound and feasible. But the question of whether it could be practically implemented remained.

The Chicken and Egg Dilemma

The VII approach had a classic "chicken and egg" problem. Why should vehicle manufacturers invest in developing and paying to install in-vehicle devices (DSRC radios) with no guarantee that there would be any infrastructure-based devices with which to communicate? Conversely, why should State and local agencies invest in the installation of infrastructure-based technology with no guarantee that there would be any in-vehicle devices for their infrastructure-based devices to talk to?

In particular, there were many uncertainties about infrastructure deployment. Early estimates indicated that approximately 300,000 roadside equipment (RSE) units were needed to support initial applications at a nationwide scale. An infrastructure installation of that magnitude had obvious problems. How quickly could those units be installed? Would infrastructure installation be faster than fleet turnover for V2V? Who would pay to install, operate and maintain RSE units? These 300,000 units needed to be installed alongside roads controlled by thousands of State and local jurisdictions. How could that many agencies all be convinced that installation of roadside radios at key locations was a worthwhile investment?

Figure 1: The Three Big Dilemmas to Achieving the VII and IntelliDrive Vision - U.S. DOT Image

VII and IntelliDrive share the same vision: safety and mobility through wireless technology. Three dilemmas exist to achieving that vision.

The VII infrastructure conundrum gave rise to three big dilemmas (Figure 1):

  • Which is installed first: vehicles or infrastructure?
  • How can the vehicle fleet be equipped with DSRC radios quickly enough to realize early benefits from the technology? In other words, how can market penetration be accelerated?
  • How can the financial and logistical challenges be overcome to achieve sufficient infrastructure deployment?

New Technologies

In the meantime, wireless technology exploded in the consumer marketplace, and consumer mobile communications devices, including smartphones and mobile internet devices, proliferated. These technologies had significant implications for the future of VII. To support high-speed transmission of text, voice and video data, telecommunications providers greatly expanded the bandwidths available for cellular phone technology, providing 3rd Generation (3G) networks. To make the wireless mobile devices more appealing to the customer, new applications were developed, including some capable of providing location-specific information - for example, applications that locate the closest store selling a hard-to-find item, or that forecast the weather for your location during the next 60 minutes. These applications use global positioning systems (GPS) or cellular positioning technology to pinpoint the device's location. As the wireless revolution exploded, other recent information technology innovations, including cloud computing and real-time search capabilities, showed potential for application to transportation.

As the VII Program progressed from the research laboratory stage into commercial testing and marketing, it became apparent that the DOT ITS Program needed to expand the scope of the VII Program to explore the potential applications of the newer wireless and computing technologies. To better reflect the expanded spectrum of the research, in 2009 DOT rebranded the VII Program to IntelliDrive. V2V and V2I communications remain critical components of the expanded program. While DSRC remains a primary focus for safety, the IntelliDrive research program also is exploring how other communications capabilities can be used to support non-safety applications - particularly for mobility applications.

The IntelliDrive Approach

The implementation dilemmas associated with the original VII approach and the new technologies emerging in the market indicated that it was time to adapt the research program based on new information. But, significantly, the original vision remained the same; it was only the approach to achieving the vision that needed to be revised to take advantage of new opportunities.

Safety

Results of a recent high-level NHTSA analysis of the potential of V2V and/or V2I to address crash types indicate that V2V has the potential to address a large proportion of crashes involving unimpaired drivers. Specifically, up to 82 percent of all crashes by unimpaired drivers could potentially be addressed by V2V technology. If V2V were in place, another 16 percent of crashes could potentially be address by V2I technology. In imminent crash situations, V2V is uniquely capable of addressing forward collisions and lane change/merge collisions. At very high market penetration levels V2V can also address intersection collisions. V2I has the potential to address road departure and intersections crashes at lower market penetration levels. The actual effectiveness of V2V and V2I in addressing these crash types still remains to be tested.

Implementation considerations quickly emerged as key hurdles for the original VII approach based on massive infrastructure installation up front. This fact prompted the USDOT to explore alternative approaches to achieving the safety vision.

Dilemma #1: Which is Installed First: Vehicles or Infrastructure?

The information from the NHTSA report provides a compelling reason to aggressively pursue V2V technology and applications while continuing to pursue V2I. In fact, the potential is so great, that NHTSA has embraced V2V as a priority for its rulemaking research plan, and has identified this technology for possible future regulation or other action to encourage its implementation. Action by NHTSA would dramatically change the pathways to implementation and would “crack” the chicken and egg problem by firmly establishing vehicles as the path to early implementation (Figure 2).

Figure 2: The Vehicles or Infrastructure First Dilemma - U.S. DOT Image

Answering the dilemma of which comes first – vehicles or infrastructure – could hinge on a
NTHSA regulatory decision in 2013 about whether to require technology on new vehicles.

However, regulation or other government action in private markets is not something that NHTSA or any other Federal agency takes lightly. Much research, data collection and analysis is needed to support a regulatory decision. The V2V research program outlined in the ITS Strategic Research Plan is structured to develop applications, test their effectiveness and validate the results to support a regulatory decision in 2013. If the research results indicate that IntelliDriveSM is beneficial, practicable and can be tested objectively, then NHTSA will proceed with rulemaking for light and heavy vehicles. If the results are sufficiently positive but do not justify a rulemaking, then the agency may advise drivers to purchase vehicles with this technology through its consumer information program.

If NHTSA chooses to issue a regulation requiring installation of V2V communications equipment in all new vehicles, then the "Which comes first?" question will be answered definitively. If NHTSA chooses not to regulate, then other implementation approaches to achievement of the safety goal will need to be considered.

Dilemma #2: How Can Market Penetration be Accelerated?

While the potential of V2V technology was recognized in the VII Program, benefits would be delivered only when a sufficient number of equipped vehicles were on roadways to interact. Early in the VII program, it was difficult to envision a feasible way out of this dilemma. But now, a plethora of consumer electronics devices are available in vehicles. The exponential growth of the use of these devices by travelers may open up a new avenue to accelerate DSRC into the vehicle fleet.

The concept is to embed DSRC communications in aftermarket devices, such as navigation systems, so that they emit a simple "Here I Am" message (Figure 3). The “Here I Am” message would be a subset of the full V2V message. Portable navigation systems are prevalent, and many smaller consumer devices also have navigation applications. "Here I Am" messages are continually emitted when these devices are turned on, and do not require any driver interface. Safety could be significantly increased by notifying other vehicles of the location of a vehicle that contains a "Hear I Am" device.

Figure 3 – Vehicle Emitting a “Here I Am Message” - U.S. DOT Image

Aftermarket devices have access to power, communication (typically cell) and location via GPS. This basic data, plus a little more, constitutes the “Here I Am” message. The V2V message includes all of this information, plus more robust data that is available directly from vehicle systems. The differences in message content will determine the type of applications that can be supported. “Here I Am” messages will probably have limitations in their capabilities; they will likely not have access to data from internal vehicle electronic systems. On the other hand, there is much that could potentially be accomplished with these simple messages. In addition, the presence of “Here I Am”- equipped devices would provide increased early benefit to fully equipped V2V vehicles, which could sense the location of an emitting device.

The V2V research program includes testing and validation of aftermarket DSRC devices and their potential benefit for owners of both vehicles and devices. If the research shows that these devices are effective, the market penetration dilemma may be diminished. If not, then other options need to be pursued (Figure 4).

Figure 4: The Fleet Penetration Dilemma - U.S. DOT Image

DOT supports a two pronged approach to the dilemma of accelerating market penetration: test the potential of DSRC-enabled aftermarket devices and continue to advance research on technology embedded in vehicles.

Dilemma #3: How Can Financial and Logistical Challenges Be Overcome to Achieve Sufficient Infrastructure Deployment?

Again, new research results provide new opportunities. As V2V research progresses, one of the key questions under investigation is the need for infrastructure to support V2V applications.

V2V applications are inherently about communication between vehicles. Does that require any infrastructure? Initial indications from the research indicate that some infrastructure is needed to support data security. Communications security is essential for critical safety applications - but what type of communications is needed, and what is the density of infrastructure required? These questions are still subject to study and refinement. Preliminary results are beginning to emerge that seem to indicate that communications for data security will not require DSRC; other communication technologies might be used. Further research is ongoing, but if this proves out, then it may be possible to achieve a large portion of the safety vision without requiring new DSRC infrastructure (Figure 5). It is too early to know with certainty, but the results of this research may lead to new opportunities, without some of the difficulties that greater infrastructure needs would imply.

Figure 5: Vehicle to Infrastructure Communication May Not Require DSRC for Basic Functionality (Security) - U.S. DOT Image

What would that mean for V2I applications? Clearly V2I technologies have the potential to address crash types that cannot be addressed otherwise. As mentioned earlier, V2I is uniquely suited to address intersection and road departure crashes around sharp curves. If research shows that pervasive infrastructure is not needed for V2V, then V2I applications potentially could be pursued for high-crash locations, such as signalized intersections and sharp curves. In this scenario, with infrastructure deployment limited to "spot safety" applications, far fewer than 300,000 roadside equipment units using DSRC would be needed (Figure 6).

Figure 6: The Infrastructure Deployment Dilemma - U.S. DOT Image

The infrastructure deployment challenge is lessened if DSRC is not needed for basic functionality (security) of the system, but can be applied for spot safety applications – enable gradual deployment over time.

Further research is required to explore V2I application development, testing, and validation of effectiveness, and is included in the ITS Strategic Research Plan, 2010-2014. Stakeholders are particularly interested in the potential to equip traffic signals with DSRC communications to emit a frequent message about signal status - which is termed “SPaT” (signal phase and timing) - the equivalent of a traffic signal “Here I Am” message (Figure 7).

Intuitively, SPaT data appears to provide the basis for several applications that would support safety and mobility. Additionally, it may provide early benefits for infrastructure-based technologies and spur their implementation. As more traffic signals with DSRC communications capability are deployed, this data can be captured for mobility applications as a supplement to other wireless and conventional transportation data.

Figure 7: Vehicle to Infrastructure Communication with Traffic Signals Using DSRC May be Valuable for some Safety and Mobility Applications - U.S. DOT Image

Mobility

In the early stages of VII, it was understood that mobility applications that used vehicle-based communications did not need the same communications requirements as safety applications. In fact, only the most rigorous safety applications needed DSRC at 5.9GHz. Mobility applications had been a part of the original VII Program only because the spectrum could support BOTH safety and mobility simultaneously. If the DSRC radio was required for safety applications, the reasoning went, it could also be used for mobility. This was a rational approach for the initial program; however, technology innovations provided new opportunities.

Driven by the consumer marketplace, entrepreneurs have been using signals from cell phones to capture location data that could be converted into useful information for transportation applications. Other innovators are leveraging wireless equipment in vehicle fleets to capture traffic data. This data, already available, approximates the mobility data that could potentially be captured through V2I.

It now appears that the original mobility goals can be substantially realized using data from non-DSRC sources, while accommodating future DSRC data. Data from wireless sources is already being combined with data being collected by public sector agencies. Today these public sector data are collected by conventional equipment, such as loop detectors, traffic cameras, ramp meters and traffic signals. The challenge for the future is to increase the amount of data available and integrated for multiple uses. For instance, it remains a challenge to integrate data from multiple agencies to provide information across various modes or various jurisdictions within a connected region. Enhancing the quantity and quality of available data and the ability to combine data is likely to fuel new applications that could lead to revolutionary mobility improvements. Considerable research is required to understand user data requirements; to explore data quality issues related to new data sources; to understand how to integrate newer data with conventional data; and, finally, to develop applications for public sector use (Figure 8).

Figure 8: Achieving the IntelliDrive Vision for Mobility Applications - U.S. DOT Image

Achieving the IntelliDrive vision for mobility depends on the ability to combine data from multiple existing and new sources and use it in revolutionary new ways

The ITS Strategic Research Plan, 2010-2014 includes two new programs to address these research questions: the Real-Time Data Capture and Management research program, and the Dynamic Mobility Applications research program.

The objective of the Real-Time Data Capture and Management research program is to enable the development of environments that support the collection, management, integration, and application of real-time transportation data. Some of the data types that can be captured and managed include: situational safety; environmental conditions; congestion data; and cost information (derived from both traditional sources - traffic management centers, Automated Vehicle Location systems; and non-traditional sources - mobile devices, IntelliDrive applications). Data also can be collected from toll facilities, parking facilities, and transit stations. The results of the Real-Time Data Capture and Management research program will reveal opportunities for achieving greater efficiencies within our transportation systems.

Dynamic Mobility Applications is a closely related research program. This program will seek to answer the question, “What do we do with all this data if we have it?” Key objectives include development of multi-modal applications targeted to public sector managers, leveraging the abundance of new data that is possible from wireless technology. DOT will work with stakeholders to identify a few high-value applications and test them in real-world environments to assess their effectiveness. The intent is to focus on applications that are of specific value to public agencies across all modes. Consumer applications will be left to private companies.

IntelliDrive also will create the capability for location-specific messages to be relayed back to individual vehicles - for instance, traffic, weather, school zone, speed limit, or road closure information. This would make other forms of message delivery, such as variable message signs, 511 systems, highway advisory radio, etc. less critical in the future - saving local agencies money. Ensuring safe, non-distracting, message delivery methods is a critical part of the ITS Strategic Research Plan, 2010-2014.

Other Vexing Issues

In addition to the challenges described above, other vexing issues must be addressed. The POC test accomplished a great deal by developing and testing the technical foundation needed to support IntelliDrive. However, many technical issues will need to be addressed to achieve a system that can be effectively implemented and is financially feasible. Discussed below are some of the particularly difficult remaining technical issues. Research to address these issues is under way. The ITS Strategic Research Plan, 2010-2014 describes how the results of the technical research will be used to systematically resolve the issues into implementable solutions.

  • Data security: For IntelliDrive to be successful, data being transmitted wirelessly needs to be secure. Many questions remain around data security: What level of security is needed? What are the communications requirements? How much of what type of infrastructure is needed for secure data transmission? What are the tradeoffs between data security requirements and privacy principles?
  • Positioning: Positioning, or the precision and accuracy of locating a wireless device, is another challenging issue. V2V technologies require relative positioning ("Where is the other vehicle relative to me?"), whereas V2I communications require absolute positioning ("Where is the vehicle? On which road? In which lane? Where in the lane?"). Initial research indicates that relative positioning using equipment from a single GPS manufacturer may be reasonable; however, relative positioning using equipment from different GPS manufacturers may be more problematic. For V2V to work, relative positioning must be uniform and fully addressed to support safety applications.
  • Scalability: Another uncertainty of the IntelliDrive approach is whether these technologies, assuming they perform well in limited pilot and field operational tests, will be able to accommodate all 250+ million vehicles in the United States. The VII POC test involved only a small number of vehicles with prototype equipment. More extensive tests are needed to identify any issues for the communication network at full scale.

In addition to these and other technical issues, policy issues also remain. Many of these issues must be addressed iteratively, as technical research results inform policy options. Among the most complex policy issues are these:

  • Balancing technical data security requirements with privacy principles: The handling of security “certificates,” the frequency of certificate renewal, the use of multiple certificates, and the handling of fraudulent messages all require careful consideration and balancing of security requirements with privacy concerns. The VII Privacy Principles have served as a basis for technical design. As the design, particularly for security, is further developed, the implications for privacy will need to be fully considered.
  • Certification and enforcement: The IntelliDrive concept depends on interoperability of components developed by various manufacturers based on open standards. Purchasers must be able to trust that equipment does indeed work within the system as intended. A transparent process must be in place to instill this trust – whether it is based on self certification by manufacturers or some level of testing and oversight by outside entities. This issue is especially significant for active safety applications that are intended to safeguard against a crash. There may also be some authority or operating entity involved in issuing security certificates to system users. An approach for these oversight and authority issues needs to be developed.
  • Funding: At present, there are many unanswered questions about the ultimate structure that an IntelliDrive system would take, and whether it would be built and operated by the public or private sectors or through a partnership. Multiple developers and operators is another possibility. Regardless, there will be a cost for building and operating the system. Funding requirements and potential sources will need to be identified and assessed to determine feasibility.

These are just a few of the particularly difficult policy issues. Narrowing policy and technical options will require an iterative process that will include discussion and balancing of benefits, costs and societal acceptance.

[......]

Achieving the Vision

Much has changed with the metamorphosis of DOT’s VII Program into IntelliDrive. But what has not changed is the vision that these programs seek to achieve: dramatic improvements in safety and the potential for revolutionary improvements in mobility. A third major goal was added most recently - decreasing transportation’s impact on the environment.

While the vision remains the same, new opportunities have emerged to address the three major shortcomings of the VII approach. IntelliDrive embraces a multi-pathway approach that uses DSRC capabilities for safety; and explores aftermarket DSRC devices for their ability to more quickly provide benefits through faster penetration into the vehicle fleet. IntelliDrive also takes advantage of data collected by non-DSRC devices for mobility applications.

The broader IntelliDrive approach is designed to address the three dilemmas of the “chicken and egg” impasse between vehicle and infrastructure deployment; market penetration in vehicles; and the institutional and policy issues associated with infrastructure deployment. Many additional technical and policy issues remain to be addressed, but work is under way (Figure 9).

Figure 9: Achieving the IntelliDrive Vision ― the Full Concept - U.S. DOT Image

Safety, mobility, weather and environmental applications take different paths to achieving the IntelliDrive vision, but may ultimately converge in the use of DSRC over time.

The ITS Strategic Research Plan, 2010-2014 is designed to take advantage of the new opportunities provided by advancing technology, and to do so in a way that specifically addresses the remaining research questions that need to be answered to ensure implementation of the full suite of applications that comprise IntelliDrive.

IntelliDrive is new next evolution of VII. It opens the research scope to new opportunities, while continuing to pursue the original goal of materializing the safety, mobility and environmental benefits that captivate our imaginations and motivate our work.

For more information about the ITS Strategic Research Plan, 2010-2014, please visit:http://www.its.dot.gov/strat_plan/index.htm

For more information about IntelliDrive, please visit: http://www.its.dot.gov/intellidrive/index.htm

*********
Recently Deleted page - Google cache from May 6th 2011 RITA | ITS | Vehicle Infrastructure Integration

http://www.its.dot.gov/images/title_bckgnd.jpg); background-attachment: initial; background-origin: initial; background-clip: initial; background-color: initial; font-family: arial, helvetica, sans-serif;">Vehicle Infrastructure Integration (VII)

What It Is

The VII Initiative is a cooperative effort among USDOT, state governments, and the automobile industry to support development of an information infrastructure for ongoing real-time data communications with and among vehicles to enable a number of safety, mobility, and commercial applications. An implemented VII network will enable travelers to access traffic condition and routing information for multiple modes of travel, receive warnings about imminent hazards, and conduct commercial transactions within their vehicles. Transportationagencies will have access to data needed to better manage traffic operations, support planning, and more efficiently manage maintenance services. The goals of the VII initiative are to (1) assess the value; (2) determine the technical feasibility, economic viability, and social acceptance; and (3) conduct research needed to support development of a VII network.

America ’s roadways have a safety and congestion problem. Vehicle crashes account for more than 42,000 deaths per year. Urban surface transportation congestion is estimated at $80 billion per year. Fifteen years of ITS research have indicated that traffic condition and roadway information can have a tangible and significant positive impact on these statistics. Furthermore, new technology, enabling active safety applications, such as advanced warnings to drivers approaching a patch of ice or merging into another car, have the potential to provide whole new levels of safety benefits.

Current Status

USDOT’s VII program is divided into three phases:

  • Phase I - Operational testing and demonstration (SafeTrip-21)
  • Phase II - Research in the areas of enabling technology, institutional issues, and applications to support deployment
  • Phase III - Technology scanning to determine potential new technology horizons for VII

In December 2007, USDOT announced SafeTrip-21—Safe and Efficient Travel through Innovation and Partnerships in the 21 st Century. This multi-application field test of safety and congestion-reducing technologies will be launched at the Intelligent Transportation Systems World Congress in New York City from November 16-18, 2008 and then integrated into other test locations. SafeTrip-21 builds upon research into the use of information, navigation, and communications technologies to prevent accidents and alleviate congestion by providing drivers with real-time safety warnings, traffic and transit information, and advanced navigational tools. SafeTrip-21 will accelerate testing and deployment of these capabilities.

Phase II continues the foundational research necessary to determine the viability of a nationwide VII deployment decision. Significant work has been done in partnership with automakers, equipment suppliers, and State and local governments in assessing potential technology and applications. Concept testing is being conducted in Michigan, California, Virginia, Arizona, Florida, Minnesota, and New York. Privacy principles and related technical requirements have been developed. Study of other legal and institutional issues is underway, and work has begun to explore potential deployment scenarios and business models. Phase III will be an ongoing scanning activity to make sure that the vehicle infrastructure integration initiative continues to plan for and use the best available technology over time.

FHWA-JPO-08-016 ITS EDL 14086

For more information go to: http://www.its.dot.gov/vii/index.htm or http://www.vehicle-infrastructure.org/

Syndicate content