~~~d{~eHt. The License Plate Recognition (LPR) program seeks to increase safety in Montgomery County while reducing the impact caused by homeland security threats, auto theft and other

DEPARTMENT OF POLICE

Isiah Leggett County Executive

INFORMATION SUPPORT AND ANALYSIS DIVISION

David Roach American Civil Liberties Union of Maryland Foundation

3600 Clipper Mill Road, Suite 350 Baltimore, Maryland 21211

Dear Mr. Roach:

September 7, 20 12

J. Thomas Manger Chief of Police

Your request addressed to Chief J. Thomas Manger on behalf of the American Civil Liberties Union of Maryland, was forwarded to me for response.

You have specifically requested to inspect and copy records in the Montgomery County Police Department's custody and control pertaining to automatic license plate readers (ALPRs). ALPRs are also sometimes referred to as Automatic Vehicle Identification, Car Plate Recognition or License Plate Recognition equipment and/or software, created since or in effect ii·mn January 1, 2006.

I have enclosed copies of all available records maintained by MCPD that are responsive to your request.

This letter is fully responsive to your request under the Maryland Public Information Act, Md. State Gov't Code Ann. §§ 10-611 et ~(the "MPIA"). Section 10-623 of the MPIA sets out the rights and remedies for a requester who believes that he or she has been denied of inspection of a public record. You should refer to that section of the State Code if you believe that you have been denied inspection of a public record.

~~~d{~ Custodian of Records

2350 Research Boulevard • Rockville, Maryland 20850 • 240-773-5000 • TTY 240-773-5336 www.montgome1ycountymd.gov

-~311· montgomerycountymd.gov /311 11 h ihi '¥'·"·"' 240-773-3556 TTY - 27558 -

LICENSE PLATE RECOGNITION SYSTEM

FC No.: 424 Date: draft 02-24-12

If a provision of a regulation, departmental directive, rule, or procedure conflicts with a provision of the contract, the contract prevails except where the contract provision conflicts with State law or the Police Collective Bargaining Law. (FOP Contract, Atticle 61)

Contents: I. Policy II. Training Requirements III. Procedures TV. Data and Record Keeping V. Dissemination and Retention of Data VI. CALEA Standards VII. Proponent Unit

I. Policy

A. The depmtment recognizes the importance of preserving Reed to ~reserve the delieate llalaaee lletweeR the constitutional rights of all persons. afforded to eaeh eitizea aad the legitimate needs of law enforeeH>eHt. The License Plate Recognition (LPR) program seeks to increase safety in Montgomery County while reducing the impact caused by homeland security threats, auto theft and other crimes. Furthermore, the system assists with the department's commitment to increasing the detection and solving of crime and other matters that impact the safety of citizens and visitors to the County.

B. It is the policy ofthis department that the LPR program will be used in accordance with the guidelines set forth in this directive. The use of the LPR system and data is restricted to matters relating to public safety only. Any other use of the LPR system or data is prohibited.

C. Eaeh day Routinely a "Hot List" database will be populated with information of specific concerns to the investigative, enforcement and pub! ic safety interests of law enforcement. This may include Terrorist Screening Center watch lists, stolen/wanted vehicles and license plates, wanted and missing persons, cautions, and license plates associated with Amber Alerts or watch lists provided for law enforcement purposes. In addition, the LPR system will act as an investigative and intelligence resource. LPR system information is available to authorized law enforcement personnel.

D. The depattment will assign the mobile LPR systems based on the needs ofthe department and may rotate the assignment of each LPR as it deems necessary.

II. Training Requirements

Only personnel who have successfully completed approved depmtmental training for the mobile LPR devises are allowed to operate the LPR equipment or system in LPR equipped vehicles. Operators will use the LPR equipment and system in accordance with their training and this policy.

III. Procedures

A LPR technology uses specialized cameras and computers to captme large numbers of license plate photographs. The LPR system records license plates it comes in contact with and records the location, date, and time of each license plate read. The system compares them to a list of plates of interest. The plates of interest are refetTed to as a "Hot List." At this time, the LPR system does not interface with real

- 27559 -

FCNo.: 424 Date: 00-00-00

time MY A, NLETS and NCIC data. It shall be the responsibility of the operator to ensure the most current "Hot List" available has been transferred into the LPR prior to its use but at a minimum, once per work day.

B. LPR equipped vehicles may be used in a routine patrol capacity or for special operations. These vehicles should not be intentionally used or deployed in a manner or location that will increase the risk of damage to the LPR equipment (such as civil disturbance situations) if at all possible.

C. Supervisors should make every effmt to deploy LPR equipped vehicles on a regular basis.

D. The LPR operator is responsible for inspecting the LPR equipment before its use and will notify their supervisor of any damage found.

E. Receipt of a LPR "hit" or alert is not sufficient probable cause to warrant an arrest without additional evidence of a violation. verification. Verification will be done following established depa1tment proceEiures. Upon receiving a "hit" from the LPR, the operator will determine the acctiracy of the "hit" The LPR operator will verify that the subject tag and the tag read by the LPR are actually the same. The operator will confirm the "hit" is still active by running the information through the proper system such as NCIC/METERS. The LPR operator will use established department procedures in taking enforcement action based on the seriousness of the offense. (This means if the vehicle is a felony vehicle used in a bank robbery, officers would make a felony stop versus and expired tag offense, it also means officers could issue a warning if appropriate (one day old expired tag versus expired for one year, write a citation, make an arrest etc).

F. Additional information may be entered into the LPR system at anytime. Broadcast information received following the initial download should be manually entered immediately upon receipt by the LPR operator. The reason for the ently shall be included in the "note" portion of the entry screen (e.g., stolen vehicle, missing person, abduction, Amber Ale11, robbery suspect). This entry is only available to the MDC on which it was entered and will expire when a new hot list is received from the system.

I. Additions to MCP/RCP hot list Tags entered into NCIC will automatically be included in the next regularly scheduled hot list received, but there can be a delay of 12 hours or more until that update is completed. Officers may immediately add a tag to the hot list of all LPR units connected to the Montgomery County Police LPR server by completing the appropriate Web Help Desk request. Officers may also add a tag to the hot list that will not be entered into NCIC. In that case, the requesting officer will provide details as to what action the LPR user should take if the tag is located. When an officer requests a tag be added to the hot list, the requestor must contact the LPR coordinator to have the tag removed when it is no longer needed for investigative purposes. Tags that are manually entered into the hot list by the LPR coordinator will automatically expire from the hot list after a set period oftime (initially set to 30 days but subject to change).

2. MCAC entries Officers may contact the Maryland Coordination and Analysis Center (MCAC) to request that a tag be forwarded to all LPR administrators in the region for inclusion in their system hot list for the same reasons as described in F.! above. Officers making such a request will provide all of the information required by MCAC.

G. Under no circumstances should an LPR operator attempt to modify the LPR equipment or software operating system.

H. Any time the LPR unit is disconnected, unmounted or removed from the vehicle, it shall be placed in the protective storage case and secured to prevent damage and theft.

2

- 27560 -

FCNo.: 424 Date: 00-00-00

I. The LPR coordinator shall be notified of any LPR equipment needing maintenance or repair. The coordinator will then coordinate all maintenance and repair.

IV. Data and Reconl Keeping

A. LPR equipment has the capability to store and/or cause to store data collected during deployments. LPR data may be stored in a central database. This database can be searched and information retrieved by department employees for official law enforcement purposes in accordance with this policy.

B. If an officer determines that LPR data could be valuable, the officer can query data from the LPR database. Data can be retrieved, copied and stored in a case file in order to enhance the initial or follow-up investigation.

V. Dissemination and Retention of Data

A. Use by Montgomery County Police employees and other law enforcement agencies is restricted to official law enforcement purposes. Montgomery County Police can share this data with other law enforcement agencies for official law enforcement purposes if those agencies have similar use, dissemination and restriction policies or procedures in effect. Sharing of data shall be based on the following procedures: I. All re~uests for ami dissemination ofLPR data outside Montgomery County Police will be recorded

in the dissemination log of the database. 2. No LPR data or information will be released to any non-law enforcement agency or individual. It is

the responsibility of the individual disseminating the data to ascertain that the request for the information is for legitimate law enforcement purposes. In the event it is determined that the request is for non-law enforcement activities, dissemination of the data is prohibited and the employee's supervisor will be immediately contacted.

3. All outside agency requests for data should be made in written form (electronic or paper) to the Director of CID. However, the Director of CID can honor oral requests as long as the receiving officer confirms !he authenticity of the requesteJ:. Immediate dissemination of data can be made without written requests in matters involving the immediate threat of terrorism, ilnminent harm to national security, death or serious bodily injury to a person and dissemination is necessary to respond to or prevent such a threat.

4. All disseminated information will be sent to the requestor with a cover letter outlining our department's policy concerning the dissemination and retention of MCPD data. The cover letter will he automated within the data system and generated by the disseminating employee. supervising!eoH'lltlaneiHg offieer, atteHtioH to the re~Bester.

5. No information will be disseminated to outside agencies without authorization from the disseminating officer's supervisor. Direetor sf g!D.

6 An outside agency can request that a specific tag be searched in the MCPD LPR database and that outside agency can be advised whether or not the data exists. The release of the specific data, including pictures, locations, dates and times will be handled according to this policy.

7. When a suspect has been identified based on information contained in the LPR database, the identification, any photographs, locations, dates and times of past locations of the vehicle may be shared with other law enforcement agencies in the same manner as other investigative information.

8. The disseminating officer Direetor of SID will ensure that the receiving agency knows, understands and agrees that this information cannot be duplicated or given to another agency or individual.

B. It is the policy of the department to audit the LPR files on a regular basis. All data will be initially stored for one year for investigative purposes. Any data older then one year will require approval of the Chief of Police or designee to access or disseminate by any employee. files. and is go\'ernee ana eovered ey department polieies aHd proeedures that eover these files.

3

- 27561 -

FCNo.: 424 Date: 00-00-00

Data is to be purged from the files when it has been determined that one or more of the following conditions exist: 1. The data is no longer relevant or necessary to the goals and objectives of this directive. 2. The data cannot be utilized for any present and/or future law enforcement purpose to assist in the

fUJtherance of criminal investigations. Data stored in case files are exempt from this requirement.

VI. Portable LPR Trailer

A. Use by Montgomery County Police I. Requests for deployment of the LPR trailer by MCPD personnel will be coordinated by the LPR

coordinator. 2. Simultaneous requests from multiple Districts/Divisions will be determined by the severity of the

offense for which the trailer is requested. Any conflicts will be settled by the District/Division commanders requesting the deployments.

3. Deployments will generally be limited to two weeks per location. Exceptions can be made on a case by case basis.

4. The trailer will be checked on once each day when deployed. 5. The District/Division requesting deployment will be made familiar with its use and functions by the

LPR coordinator. 6. Requests for deployment by MCPD take precedence over requests from outside agencies. Exceptions

can be made on a case by case basis. 7. All data from deployments of the p01table LPR trailer within Montgomery County will be stored in

accordance with Sections IV and V above.

B. Use by other police agencies The LPR trailer was received by MCPD thru a regional grant that requires it to be shared among the various law enforcement agencies in this region. When available, it can be deployed to other agencies as outlined below. I. Requests for deployment of the LPR trailer by outside law enforcement will be coordinated by the LPR

coordinator. 2. Simultaneous requests from multiple agencies will be determined by the severity of the offense for

which the trailer is requested. Any conflicts will be settled by the LPR coordinator or Traffic Division commander.

3. Deployments will be limited to two week periods per request. Exceptions can be made on a case by case basis.

4. The trailer will be checked on once each day when deployed. 5. The agency requesting deployment will be made familiar with its use and functions by the LPR

coordinator. 6. The requesting agency must provide appropriate means of towing the trailer to their location of

deployment. 7. All data from deployments of the p01table LPR trailer outside Montgomery County will be provided to

the requesting law enforcement agency and then purged from our department's data base and not retained by MCPD.

Vll. CALEA Standards: 41.3.7

VIII. Proponent Unit: Special Investigations Division

Please initial at this time J. Thomas Manger

Chief of Police

4

- 27562 -

MEMORANDUM OF UNDERSTANDING NATIONAL CAPITAL REGION'S (NCR) LICENSE PLATE READER (LPR)

INFORMATION SHARING PROGRAM

PURPOSE

1. This Memorandum of Understanding (MOU) is entered into by the participating federal, state, county, local and special jurisdiction law enforcement agencies collaborating in the NCR LPR information sharing initiative. The purpose of this MOU is to set forth the policy and procedures for the sharing of LPR data by the participating parties, including the ownership and control of the information within the system, which may be contributed by each party for the use by the participating agencies.

2. This initiative and MOU is to reduce crime and prevent terrorism in the NCR. This includes: identifying and locating criminals, terrorists and their supporters; identifying, assessing, and responding to crime and terrorist risks and threats; and otherwise preventing, detecting, and prosecuting criminal and terrorist activities. To achieve these ends, it is essential that all law enforcement agencies cooperate in efforts to share pertinent information. The NCR LPR data sharing program will establish a mechanism that will allow member agencies to search for LPR data collected and maintained by other member agencies via the NCRnet. NCRnet is a secure fiber optic network established by COG (Council of Governments) that is available for use by NCR member agenc1es.

3. Regional LPR data will be available for use by participating law enforcement agencies in furtherance of authorized law enforcement activities as well as the prevention and detection of terrorist risks and threats. Being able to access LPR data through NCRnet will significantly advance public safety and security, reduce crime, and will enhance the protection of this Nation's critical strategic resources in the National Capital Region which includes the aggregate areas of responsibility within the District of Columbia, State of Maryland, and Commonwealth of Virginia currently represented by the participating agencies.

PARTIES

1. The parties to this MOU shall be law enforcement agencies in the NCR.

2. The parties agree that maximum participation by all eligible law enforcement agencies will strengthen the purposes of this MOU. Accordingly, the parties anticipate and desire that other eligible agencies will join this project in the future.

3. Those eligible agencies, beyond the original signatories must request participation, and be approved by the COG Police Chief's Committee. Any law enforcement agency requesting to participate in NCR LPR Project must be given 30 days advance notice prior to a vote by the COG Police Chief's Committee. The LPR Sub-committee (an

This document was prepared under a grant fi·nm FEfv1A's Grants Programs Directorate. U.S. Department &Homeland Security. Points of view or opinions expressed in this document are those ofthe authors and do not necessarily represent the official position or policies of FEMA's Grants Programs Dircc!Oratc or the U.S. Department of Homeland Security.

- 27563 -

advisory board that reports to the COG Police Chief's Committee) shall make a recommendation to the COG Police Chief's Committee based on the following criteria: eligibility to join, security compliance, data accountability, technical capability, and operational history.

4. A joining state, county, local, and special jurisdiction law enforcement agency once approved to by the COG Police Chief's Committee shall be considered a party and shall have the same rights, privileges, obligations, and responsibilities as the original parties.

POINTS OF CONTACT

Each party shall designate an individual as the party's point of contact (POC) for representing that party in regard to the MOU. A party may change its POC at any time upon providing written notification to the LPR Program administrator. If the project has no program administer then the POCs of all other agencies will be notified.

MISSION/OBJECTIVES

This initiative seeks to establish a federated search capability of the cumulative LPR data from the region's law enforcement agencies in a systematic and ongoing manner to maximize the benefits of information gathering and analysis to prevent and respond to terrorist and criminal threats; to support preventive, investigative and enforcement activities; and to reduce crime, enhance public safety and protection of the Nation's critical infrastructure in the National Capital Region. The specific objectives of the NCR LPR data sharing program are to:

1. Provide the means for the participating agencies to use LPR data to support law enforcement, criminal investigation, force protection, and counter terrorism operational and investigative activities.

2. Provide access to cumulative LPR data held by individual, participating agencies.

3. Dramatically reduce the time spent by participating agency personnel in the search and retrieval of relevant LPR data.

CONCEPT

NCR LPR data sharing program is a cooperative partnership of federal, state, county, local and special jurisdiction law enforcement agencies, in which each agency is participating under its own individual legal status, jurisdiction, and authorities of the individual participants. The NCR LPR data sharing program is not intended to, and shall not, be deemed to have independent legal status.

License Plate Reader (LPR) is a computer-based system that utilizes special cameras to capture an image of the license plate of a passing vehicle. The image is converted into a text file utilizing Optical Character Recognition (OCR) technology. The text file is

This document was prepared under a gram t1·om 1:EMA's Grants Programs Directorate. U.S. Depmtment of Homeland Security. Points of view or opinions expressed in this document are those of the authors and do not necessarily represent the official position or policies or FEMA's Grant:; Programs Directorate or the U.S. Department of I lome[ and Security.

- 27564 -

automatically compared against an "informational data file", known as a "Hot List" and can contain information on stolen or wanted vehicles as well as vehicles associated with AMBER alerts, warrant subjects and agency-defined information.

1. Each participating agency will maintain its own in-house LPR server which will serve as the repository for that agency's LPR data. This data can then be accessed by other participating agencies via NCRnet. All participating agencies will have equal access to LPR data through NCRnet.

2. Agencies entering into this agreement hereinafter referred to as "Agency Parties", realizing the mutual benefits to be gained by sharing information, seek to share Plate Scan and Hot List information.

3. The purpose of this MOU is to outline conditions under which the Agency Parties will share and use Plate Scan and Hot List information. All Agency Parties will have equal access to Plate Scan and Hot List information in accordance with the contributing agency's data retention policy via a secure search performed via the NCRnet.

ACCESS TO AND USE OF LPR DATA

1. Each participating agency will make LPR data available to other participating agencies via NCRnet and agrees to permit the access, dissemination, and/or use of such information by every other agency under the provisions of this MOU (and any other applicable agreements that may be established for the NCR LPR data sharing program).

2. LPR servers shall be operated to maximize data sharing.

3. Only law enforcement agencies from federal, state, county, local, or special jurisdictions may become a party of the NCR LPR data sharing program.

4. All agencies are required to access LPR data from other participating agencies via a secure connection through the NCRnet. An agency without access to NCRnet must provide another secure alternative.

5. Agencies accessing the LPR data of another agency have the responsibility and accountability for ensuring that any access complies with any laws, regulations, policies, and procedures applicable to the accessing agency.

a. An agency party may access LPR data of another agency for official law enforcement use only.

b. Secondary dissemination of LPR data may not be done without first obtaining the permission of the contributing agency. However, immediate dissemination of LPR data can be made if the receiving agency determines:

1. There is a potential threat of terrorism, immediate danger of death or serious physical injury to any person, or imminent harm to

This documem was prepared under a grant from FFMA's Gnmts Programs Directorate, U.S. Department of Homeland Se~.;urity. Points of view or opinions expressed in this document me those of the authors and do not necessarily represent the official position or policies of FEMA's Grants Programs Directorate or the U.S. Department of I lome land Security.

- 27565 -

the national security; and

2. Requires dissemination without delay to any appropriate federal, state, local, or foreign government official for the purpose of preventing or responding to such a threat.

6. Any requests for LPR data from anyone other than a party to this MOU will be directed to the contributing agency.

7. Agencies that are not part of this MOU will not have direct access to LPR data via NCRnet. Requests by such agencies for copies of information contained in individual agency LPR servers must be referred to the individual agency that owns the information.

USER ACCESS

1. Each Agency's system administrator is responsible for management of user accounts at that agency. Agencies agree that authorized users shall be limited to employees who are legally authorized to review LPR data for crime prevention and detection purposes.

2. Each authorized user will be issued a user separate login and a password.

3. Each agency system administrator is responsible for maintaining the list of authorized users. Use by unauthorized users will result in the removal of the agency from the NCR LPR data sharing program.

OWNERSHIP, ENTRY, RELEASE AND MAINTENANCE OF INFORMATION

1. Each agency retains control of all information on its LPR server. Each agency is responsible for creating, updating, and deleting records according to its own policies. Each agency shall use reasonable efforts to insure the completeness and accuracy of its data.

2. An agency shall release or make available information accessed from an LPR Repository only to persons or entities authorized to receive LPR information pursuant to this MOU.

3. Any agency receiving a public records request, subpoena, or court order ("Legal Request") for information shall restrict their response to LPR information only on their LPR server.

4. No agency has any responsibility or accountability for ensuring that LPR information contributed by another party was done in compliance with all applicable laws, regulations, policies, and procedures applicable to the contributing party's entry and sharing of information via the NCRnet. Should inaccurate LPR data be located both the contributing agency and the LPR Project manager shall be notified.

This document was prepared under a grant from FEMA's Grants Programs Directorate. U.S. Department of Homeland Security. Points or view or opinions ~xpresscd in this document are those ofthe authors and do not necessarily represent the official position or policies of FEMA's Grants Programs Directorate or the U.S. Department or Homeland Security

- 27566 -

PROPERTY

1. Any equipment purchased by the Metropolitan Washington Council of Governments and Arlington County, Virginia, using UASI funds for the LPR Program will remain the property of the agency to which it was allocated. After expiration of any warranties the responsibility for the maintenance costs may be the responsibility of that agency should no funds be available.

2. LPR equipment located and used by multiple agencies shall remain the property of the Council of governments and under the control of the COG Police Chief's Committee.

RESTRICTIONS ON FUNDING

1. Unless otherwise provided each agency shall bear its own costs in relation to this MOU. Where an agency has agreed (or later does agree) to assume a particular financial responsibility, the agency's express written approval must be obtained before the incurring by another agency of any expense associated with that responsibility.

2. All obligations and expenditures by the agencies will be subject to their respective budgetary and fiscal processes and subject to availability of funds pursuant to all laws, regulations, and policies applicable thereto.

3. Agencies acknowledge that funding for the LPR Project may be limited or not available in future years.

2. This MOU shall not be used to obligate or commit funds, or serve as the basis for the transfer of funds.

LIABILITY

1. Each agency is solely responsible for any and all claims brought against it (including without limitation, claims for bodily injury, death or damage to property), demands, obligations, damages, actions, causes of action, suits, losses, judgments, fines, penalties, liabilities, costs and expenses (including, without limitation, attorney's fees, disbursements and court costs).

2. Unless specifically addressed by the terms of this MOU (or other written agreement), agencies acknowledge that no party shall have any responsibility for the negligent or wrongful acts or omissions of the officers or employees of other parties to this agreement.

3. Data inaccuracies can arise for multiple reasons (e.g., entry errors, misinterpretation, outdated data, etc.). It shall be the responsibility of the agency requesting or using the LPR data to confirm the accuracy of the information with the originating agency before taking any enforcement-related action.

4. Each Agency shall determine the frequency with which its hotlist data will be refreshed. Since changes or additions to hotlist data do not get updated on a real-time basis, agencies recognize that information may not always be timely. It shall be the

This document was prepared under a grant tl-om FI.:MA's Grants Progrmns Directorate. U.S. Department of Homeland s~curily. Poims of view or opinions expressed in this documem are those or Lhe authors and do not necessarily represent Ll11.: o!Ticial position or policie~ or Ff]\i[/\'s Grants Programs Directorate or tlte U.S. I kpartmcnt or Homeland Sccurit)

- 27567 -

responsibility of the requesting agency to confirm information with the originating agency.

5. To the extent permitted by law, each agency agrees to hold the other agency harmless for any information in an LPR Repository, or any action taken as a result of that data, regardless of whether the data is accurate or not, or any time delay associated with changes, additions, or deletions to the information contributed. This hold harmless provision shall not apply to the willful misconduct or gross negligence of originating agency.

GOVERNANCE

1. The success of this program requires close cooperation on the part of all agencies. To this end, the system will be operated under a shared management concept in which the participating agencies will be involved in formulating operating policies and procedures.

2. The COG Police Chief's Committee shall approve all provisions of the LPR Program.

Disagreements among agencies arising under or relating to this MOU shall be resolved between the affected parties and their sponsoring agencies. All unresolved matters would go before the COG Police Chief's Committee.

3. The COG Police Chief's Committee may establish additional procedures and rules for the governance of the NCR LPR program and in furtherance thereof may enter into one or more separate formal or informal agreements, provided that any such agreement does not conflict with the intent or provisions of this MOU. Such agreement(s) may address: organizational structure and control; executive management and administration; delegation of authority; operating policies, procedures rules; audits; and sanctions (including involuntary termination of a party's participation in this MOU).

EFFECTIVE DATE/DURATION

1. This MOU shall become effective when the duly authorized representatives of each agency have signed it. This shall include agencies that are subsequently approved for admittance by the COG Police Chief's Committee.

2. This MOU shall remain in effect indefinitely from the effective date, unless otherwise terminated.

MODIFICATIONS

1. This MOU may be modified upon the mutual written consent of the duly authorized representatives of all agencies. However, the agencies may, without the need of formal MOU modification, cooperatively address and resolve administrative, technical, and operational details relating to this MOU, provided that any such resolution does not conflict with the intent, or provisions of this MOU; could not reasonable be viewed as particularly sensitive, controversial, or objectionable by one or more parties.

This docum1:0nt was prepared under a gralll from FEtviA's Grants Programs Directorate. U.S. Depmtmcnl or 1-lomehmd Security. Points of vie"or opinions expressed in this document are those of the Huthors and do not necessarily represent the official position or policies orFEMA's Grants Programs Directorate or the U.S. Department or Homeland Security.

- 27568 -

TERMINATION

1. This MOU may be terminated at any time by the written notification by the representatives of the respective agency. Written notice to applicable parties shall be not less than 30 days. An agency's participation may also be terminated involuntarily for violation of policies in this MOU.

2. Should an agency leave the LPR data sharing program all obligations, responsibilities, limitations, and other understandings with respect to the disclosure and use of such information under this MOU shall survive any termination.

LEGAL REVIEW

It is the responsibility of each agency to review this MOU prior to executing it in order to ensure that it complies with all applicable laws, ordinances and policies specific to that agency.

Signature of Chief Executive Officer or Designee Agency

Printed Name/Title of Above Individual Date of Signature

This document was !)repared under a grant from FEMA's Cinmts Programs Directorate, U.S. Department of Homeland Security. Points of view or opinions expressed in this document arc those of the authors ~md do not necessarily represent the official position or policies ofFElvli\'s Grants Programs Dircctorato:: or the U.S. Department of Homeland Security.

- 27569 -

•

- 27570 -

' (B~ :-~:I (~~S

~\ '! ")\ < : -··-'~

~~ MCP has 22 ELSAG License Plate Readers ~ They are currently distributed as follows:

2 on fleet cars @ 1D, 2D, sD, 6D 3 on fleet cars@ 3D, 4D 3 at PCAT 3 at CATT 2 at 2D Traffic 1 speed trailer

' ~ LPR reads are checked against a local hot list that is updated 2x per day

Includes stolen, wanted persons, MD MV A flags

- 27571 -

_,....-'i, . ..-.,

•.: .. -·<->, ·''-

·- •· ----- . 0 @ LPR reads are uploaded in near real-time to a server

Each read has a color picture, a black & white picture, the text of the tag that was read, G PS coordinates, and any hit information that was present at the time of the read.

Most of our units are not running state recognition, so most reads will not specify a state

8 Use of the LPR data is restricted .-·_ .. The use of the LPR system and data is restricted to

matters relating to public safety purposes only. Any other use of the LPR system or data is prohibited.

-:·~ ,\'; . ·,_._

~-----------------· --·--·-·····---··" -·-----·-- -----------~-------~ . -- --'-·---------'--.--..__.,:__ ____ ·_. ----· ·-· .' ·-- --··------- . ·-----------------------·-_:_ ___ _

- 27572 -

r

-- ---- " "-~------

r"i: 1 ~ -1~-·'h 1j Q

,~.... "". f', ~.... r ?"::. :.. .. '. ~,, ~~ ~. "'Vi. '. "'.'~' ~- .,Jr Q ~ 1 ~~."·'~ ..,. -7"'""~' r!"'r-i r.· !:: .~\ - Pi i! ~ ·p ~, ;; ~~ ~ .i: · \V '-::¢,..... ...~,.)!... ..!· ... ""'~ \;;,...-\L • . J·. x.. J ... -r·'·~~ .~".. ...~-.... l.. r

r~~ '"Jt'

,,,._,. ·~~

€f, The policy on disseminating data to other law enforcement agencies is currently in draft form. ··. The currently proposed policy will allow dissemination of

data to other LE agencies with supervisory approval with appropriate logging and policy notifications.

~ Until a final policy is adopted DO NOT disseminate LPR data to other agencies.

-· -------··-· _ _;_ ___ :~..:..:._·_~--- ----------· ·-··_·_ .. _ .. -_~ -~----- -=----·-·-·---------~---~-~----"--:-.:.- --\.:~--~ ----~-·----· --·--· -· ~-·-' _._· __ _____:___, ___________ . ·- ·---· _·_. _. ---·----·-· ----- _____ ;;_ ~~-'

- 27573 -

~ c \-.... :J lQ g- r,....'~·- ,-; ,__...,

·-~ '""'·· - _ ·-:r ... ~ .L - .L i. (51 \C~ Jt

0 MCP' s server hosts Rockville City LPR data

(j,' All MCP reads, are also sent to MCAC . . MCAC is working on compiling LPR data for all agencies

in the state

MCAC data can only be accessed by a Request For Service form (or phone call in urgent situations).

~The National Capital Region is implementing a regional data sharing project. Eventually we will be able to search all of the region's LPR reads . from our web interface

---~----·--·---------~-.-~-~-------~~--·· -- ·-·--:------~--·--·- ''"'"'"-------·-·-_:___-~ .. _:_.~-~ ........ -------------·--·- ---·- ····-·------·------··-·----·-----------_; ____________ ______.,__._;

- 27574 -

"------------- -·---- - -·- ----.

" i("'\; (jf J, >~ .>·" .• ,.., ___ .....

.. r~'\\ '{ '>\ -~~ H '~0}

~ Your login name will be your Active Directory user name.

You will have to change the password the first time you log in

The password does expire but you can change it right back to the same password

~ A future version of the system is supposed to support active directory logon so you can use your county "single sign on" password for access.

-----------------~--~-·~~~--~------ ···----··---:.:.:.... __ . ~~---·-: ______________ _

- 27575 -

/,...... ..,. J.~ \,,_j/ ~"~ ~~ () J~-J~C~:-~ <.~- 1

:':Cli ~· ""' ''-<~..-'

ir.::~:~>,

H \:~~/

I 0 DO NOT SHARE YOUR PASSWORD ·. All use of the system is logged. You are responsible for queries

run under your login ID. ·· Who/why/when LPR data was accessed could become the

subject of internal, civil, or criminal investigations.

!

- 27576 -

-- - .. ------· - ----

~ t' ~-·-;:

(' . .-...,~

~" [;' ~:.A, ~ ..... .J .... ~-- 1}_ .:J--~'" ' ,:_1 ~~·; '': '

0 I• • ,,-, f]> "' r~ ., ,-, -. b· ~_.,.i' ";,j,_/ ~\.:,.,.'' lt ·~0' ~-'·

0 Demonstration of: Logon Java Alarm Application Query Basics

Wildcards: o % = general wildcard o @ = any single letter o # = any single number

Query Response Ambiguous reads Common read errors

Export Data

;;~ ; I \\ I' '!\ ·~; i[ ' /' ,~i

Cross Search and Convoy Search ......

.... -·---------.-----·- ··---·----------- ·-···-·---·----·--------~~-----· -------·-·---·--.. -- - ------· ........... ·----~---- ------------

- 27577 -

I

I r

-- ,_

~-r C

,_, (_~- --,- - - f;' ~ -·- ~ , . ~. _:·:.. A. _\\.

-- -"·

...-:::;·:~~

r?' '·:-; 1r 11 · ·- ·-I !• \: ' :;_"-.::.::::::1/

~ To get a tag related to an investigation added to all hot lists in Maryland contact MCAC.

® To get a tag related to an investigation added to MCP and RCP tag readers complete a Web Help Desk ticket.

For URGENT requests: Technology- LPR- Urgent Hot List Entry Request

An LPR Server Admin will be automatically paged.

For non-urgent request: Technology- LPR- Routine Hot List Entry Request

An LPR Server Admin will be emailed the request.

- 27578 -

LPR Units received by Montgomery County from Arlington County, VA

Date Serial# Serial# Serial II Received By:

Montgomery County PO PB21607 1600750 2500777 Jay VanGilder

Montgomery County PD PB20817 1600751 2500779 Jay VanGilder















Montgomery County 11-Feb-11 PB21218 1601999 2501046 Felsen

Montgomery County 21-Sep-11 PB21684 1601413 250484 Kane

Montgomery County 21-Sep-11 PB21689 2501494 1601437 Kane

- 27579 -

TRAFFIC SAFETY INITIATIVE Using the

LICENSE PLATE READER

Assistant Chief Russ Hamill Captain Tom Didone Montgomery County Police March 2012

- 27580 -

OVERVIEW o Our ~oal in utilizing the License Plate Reader

(LPRJ is to create a Traffic Safety Initiative that also Identifies stolen vehicles and provides a long-term investigative benefit.

o Our program will share data with Maryland Coordination & Analysis Center (MCAC).

o The 22 LPR units are deployed on both fleet and individually assigned vehicles, as well as, our central auto theft and police community action team.

o Department Policy was created to manage the access, dissemination and storage of the data collected.

- 27581 -

HISTORICAL o In 2004, the first 2 original units were received by the

Department and were assigned to the Central Auto Theft Unit.

o In November 2010, 20 additional units were received from National Capital Region Resources, however, software conflicts prevented actual operations to be delayed until March 2011.

o In March 2011, the NCR also provided the Department with a networking server.

o In June 2011, 2 additional units were received from State from the Governor's Office (Crime Control & Prevention - GOCCP) with specific reporting requirements.

o In September 2011, we received 1 from Arlington VA (built into mobile trailer) that must be shared with other agencies.

- 27582 -

ALLIED AGENCY LPR USAGE

o The other municipal agencies within Montgomery County also rece1ved and are deploying License Plate Readers.

Rockville City Gaithersburg City Chevy Chase Village Takoma Park Maryland National Capital Park & Planning Police

o The Maryland Transportation Authority currently operates LPR's on tile ICC.

o The State will also be deploying LPR's on IS 270 sometime this year.

- 27583 -

CURRANT OPERATION

We currently have 22 LPR's:

3 - PCAT SECTION

3 - Auto Theft

14 - Distributed to each of our 6 District Stations (2-3) per station

1 Mobile Trailer

··o· ·u··•.·R·h·· ' .'.·' --- , __ -" -·" -_:,

- 27584 -

- 27585 -

EXAMPLES OF SUCCESS o GENERAL TRAFFIC • •

•

53 Stolen vehicles recovered 9 Wanted subjects apprehended

One officer in 27 days, 96 hrs of LPR operation, scanned 48,101 tags resulting in 255 traffic citations, 4 stolen tags recovered, 3 arrests, 16 VEIP suspension violators, 26 suspended licenses, 1 expired tag

o INVESTIGATIVE TOOL • Used recently in capture of

husband who killed his wife in Kensington and was driving her car and took his life in Rockville. We were able to retrieve photo of subject and vehicle tag, as well as damage to car.

- 27586 -

POLICY o Used by Law Enforcement Investigations only

o Accessed only by trained users in its' Operation, Policy Requirements, and Guidelines

RETENTION - MCPD • 1 year on server, offline archival with limited access

for use for Cold Case support until case is closed or violator arrested. Cannot be used for any other dissemination other than its' original charge.

OUTSIDE RETENTION varies: • Takoma Park- 30 days • State of MD- 1 year • NY & DC keep it indefinitely.

- 27587 -

- 27588 -

• LPR Distribution By Unit

UNIT LPR Systems

FSB/10 2

FSB/20 · 1

FSB/20/TRAFFIC 1

FSB/30 3

FSB/40 3

FSB/50 2

FSB/60 2

FSB/500/ AIS 1

FSB/500/PCAT 3

ISB/CIO/AUTO 2

Page 1 of 1

Tuesday, November 08, 2011

2:24:20 PM

- 27589 -

.. LPR Distribution By Unit

UNIT LPR Systems

FSB/lD 2

FSB/2D 1

FSB/2D/TRAFFIC 1

FSB/3D 3

FSB/4D 3

FSB/SD 2

FSB/6D 2

FSB/SOD/ AIS 1

FSB/SOD/PCAT 3

ISB/CID/ AUTO 2

Page 1 of 1

Thursday, November 10, 2011

12:21:09 PM

- 27590 -


UNIT LPR Systems

FSB/10 2

FSB/20 1

FSB/20/TRAFFIC 1

FSB/30 3

FSB/40 3

FSB/50 2

FSB/60 2

FSB/500/ AIS 1

FSB/500/PCAT 3

ISB/CIO/ AUTO 2

Page 1 of 1

Wednesday, November 09, 2011

2:22:54 PM

- 27591 -


UNIT LPR Systems

1

FSB/10 2

FSB/20 2

FSB/20/TRAFFIC 2

FSB/30 3

FSB/40 3

FSB/50 1

FSB/50/TRAFFIC 1

FSB/60 1

FSB/500/ AIS 1

FSB/500/PCAT 2

ISB/CIO/ AUTO 2

N/A 1

Page 1 of 1

Thursday, April 26, 2012

11:56:34 AM

- 27592 -


UNIT LPR Systems

FSB/lD 2

FSB/20 3

FSB/20/TRAFFIC 1

FSB/30 3

FSB/40 3

FSB/SD 2

FSB/6D 2

FSB/SOD/ AIS 1

FSB/SOD/PCAT 3

ISB/CID/AUTO 2

Page 1 of 1

Wednesday, February 01, 2012

10:07:11 AM

- 27593 -


UNIT LPR Systems

FSB/10 2

FSB/20 3

FSB/20/TRAFFIC 1

FSB/30 3

FSB/40 3

FSB/50 2

FSB/60 2

FSB/500/ AIS 1

FSB/500/PCAT 3

ISB/CIO/AUTO 2

Page 1 of 1

Wednesday, January 25, 2012

2:01:19 PM

- 27594 -


UNIT LPR Systems

FSB/1D 2

FSB/2D 2

FSB/2D/TRAFFIC 2

FSB/3D 3

FSB/4D 4

FSB/SD 1

FSB/SD/TRAFFIC 1

FSB/6D/TRAFFIC 1

FSB/SOD/ AIS 1

FSB/SOD/PCAT 2

ISB/CID/AUTO 2

Page 1 of 1

Saturday, August 11, 2012

4:15:49 AM

- 27595 -

til LPR Distribution By Unit

UNIT LPR Systems

FSB/lD 2

FSB/20 2

FSB/20/TRAFFIC 2

FSB/30 3

FSB/40 4

FSB/50 1

FSB/50/TRAFFIC 1

FSB/60/TRAFFIC 1

FSB/500/ AIS 1

FSB/500/PCAT 2

ISB/CIO/AUTO 2

Page 1 of 1

Friday, August 10, 2012

4:15:49 AM

- 27596 -


UNIT LPR Systems

FSB/10 2

FSB/20 2

FSB/20/TRAFFIC 2

FSB/30 3

FSB/40 4

FSB/50 1

FSB/50/TRAFFIC 1

FSB/60/TRAFFIC 1

FSB/500/ AIS 1

FSB/500/PCAT 2

ISB/CIO/AUTO 2

Page 1 of 1

Thursday, August 09, 2012

4:15:53 AM

- 27597 -


UNIT LPR Systems

FSB/1D 2

FSB/2D 2

FSB/2D/TRAFFIC 2

FSB/3D 3

FSB/4D 4

FSB/SD 1

FSB/SD/TRAFFIC 1

FSB/6D/TRAFFIC 1

FSB/SOD/ AIS 1

FSB/SOD/PCAT 2

ISB/CID/ AUTO 2

Page 1 of 1

Wednesday, August 08, 2012

4:15:49 AM

- 27598 -


UNIT LPR Systems

FSB/10 2

FSB/20 2

FSB/20/TRAFFIC 2

FSB/30 3

FSB/40 4

FSB/50 1

FSB/50/TRAFFIC 1

FSB/60/TRAFFIC 1

FSB/500/ AIS 1

FSB/500/PCAT 2

ISB/CIO/AUTO 2

Page 1 of 1

Tuesday, August 07, 2012

4:15:49 AM

- 27599 -


UNIT LPR Systems

FSB/10 2

FSB/20 2

FSB/20/TRAFFIC 2

FSB/30 3

FSB/40 4

FSB/50 1

FSB/50/TRAFFIC 1

FSB/60/TRAFFIC 1

FSB/500/ AIS 1

FSB/500/PCAT 2

ISB/CIO/ AUTO 2

Page 1 of 1

Monday, August 06, 2012

4:15:46 AM

- 27600 -


UNIT LPR Systems

FSB/10 2

FSB/20 2

FSB/20/TRAFFIC 2

FSB/30 3

FSB/40 4

FSB/50 1

FSB/50/TRAFFIC 1

FSB/60/TRAFFIC 1

FSB/500/AIS 1

FSB/500/PCAT 2

158/CIO/ AUTO 2

Page 1 of 1

Sunday, August 05, 2012

4:16:00AM

- 27601 -


UNIT LPR Systems

FSB/1D 2

FSB/2D 2

FSB/2D/TRAFFIC 2

FSB/3D 3

FSB/4D 4

FSB/5D 1

FSB/5D/TRAFFIC 1

FSB/6D/TRAFFIC 1

FSB/SOD/ AIS 1

FSB/SOD/PCAT 2

ISB/CID/AUTO 2

Page 1 of 1

Saturday, August 04, 2012

4:15:47 AM

- 27602 -

0 LPR Distribution By Unit

UNIT LPR Systems

FSB/10 2

FSB/20 2

FSB/20/TRAFFIC 2

FSB/30 3

FSB/40 4

F5B/50 1

F5B/50/TRAFFIC 1

F5B/60/TRAFFIC 1

F5B/500/ Al5 1

F5B/50D/PCAT 2

15B/CIO/AUTO 2

Page 1 of 1

Friday, August 03, 2012

4:15:56 AM

- 27603 -


UNIT LPR Systems

FSB/1D 2

FSB/2D 2

FSB/2D/TRAFFIC 2

FSB/3D 3

FSB/4D 4

FSB/SD 1

FSB/SD/TRAFFIC 1

FSB/6D/TRAFFIC 1

FSB/SOD/ AIS 1

FSB/SOD/PCAT 2

158/CID/ AUTO 2

Page 1 of 1

Thursday, August 02, 2012

4:15:48 AM

- 27604 -


UNIT LPR Systems

FSB/10 2

FSB/20 2

FSB/20/TRAFFIC 2

FSB/30 3

FSB/40 4

FSB/50 1

FSB/SD/TRAFFIC 1

FSB/6D/TRAFFIC 1

FSB/SOD/AIS 1

FSB/SOD/PCAT 2

ISB/CID/AUTO 2

Page 1 of 1

Wednesday, August 01, 2012

4:15:48 AM

- 27605 -


UNIT LPR Systems

FSB/10 2

FSB/20 2

FSB/20/TRAFFIC 2

FSB/30 3

FSB/40 4

FSB/50 1

FSB/50/TRAFFIC 1

FSB/60/TRAFFIC 1

FSB/500/ AIS 1

FSB/500/PCAT 2

ISB/CIO/AUTO 2

Page 1 of 1

Thursday, July 26, 2012

4:16:06 AM

- 27606 -


UNIT LPR Systems

FSB/10 2

FSB/20 2

FSB/20/TRAFFIC 2

FSB/30 3

FSB/40 4

FSB/50 1

FSB/50/TRAFFIC 1

FSB/60/TRAFFIC 1

FSB/500/ AIS 1

FSB/500/PCAT 2

ISB/CIO/AUTO 2

Page 1 of 1

Tuesday, July 31, 2012

4:15:52 AM

- 27607 -


UNIT LPR Systems

FSB/10 2

FSB/20 2

FSB/20/TRAFFIC 2

FSB/30 3

FSB/40 4

FSB/50 1

FSB/50/TRAFFIC 1

FSB/60/TRAFFIC 1

FSB/500/ AIS 1

FSB/500/PCAT 2

ISB/CIO/AUTO 2

Page 1 of 1


4:16:17 AM

- 27608 -


UNIT LPR Systems

FSB/lD 2

FSB/2D 2

FSB/2D/TRAFFIC 2

FSB/3D 3

FSB/4D 4

FSB/SD 1

FSB/SD/TRAFFIC 1

FSB/6D/TRAFFIC 1

FSB/SOD/AIS 1

FSB/SOD/PCAT 2

ISB/CID/ AUTO 2

Page 1 of 1

Wednesday, July 25, 2012

4:16:06 AM

- 27609 -


UNIT LPR Systems

FSB/1D 2

FSB/2D 2

FSB/2D/TRAFFIC 2

FSB/3D 3

FSB/4D 4

FSB/SD 1

FSB/SD/TRAFFIC 1

FSB/6D/TRAFFIC 1

FSB/SOD/ AIS 1

FSB/SOD/PCAT 2

ISB/CID/AUTO 2

Page 1 of 1

Monday, July 23, 2012

4:16:06 AM

- 27610 -


UNIT LPR Systems

FSB/10 2

FSB/20 2

FSB/20/TRAFFIC 2

FSB/30 3

FSB/40 4

FSB/50 1

FSB/50/TRAFFIC 1

FSB/60/TRAFFIC 1

FSB/SOO/ AIS 1

FSB/SOO/PCAT 2

ISB/CIO/AUTO 2

Page 1 of 1

Sunday, July 22, 2012

4:16:07 AM

- 27611 -


UNIT LPR Systems

FSB/10 2

FSB/20 2

FSB/20/TRAFFIC 2

FSB/30 3

FSB/40 4

FSB/50 1

FSB/50/TRAFFIC 1

FSB/60/TRAFFIC 1

FSB/SOD/ AIS 1

FSB/SOD/PCAT 2

ISB/CIO/AUTO 2

Page 1 of 1

Saturday, July 21, 2012

4:17:05 AM

- 27612 -

A LPR Distribution By Unit

UNIT LPR Systems

FSB/lD 2

FSB/2D 2

FSB/2D/TRAFFIC 2

FSB/3D 3

FSB/4D 4

FSB/SD 1

FSB/SD/TRAFFIC 1

FSB/6D/TRAFFIC 1

FSB/SOD/AIS 1

FSB/SOD/PCAT 2

ISB/CID/ AUTO 2

Page 1 of 1

Friday, July 20, 2012

4:15:52 AM

- 27613 -


UNIT LPR Systems

FSB/1D 2

FSB/2D 2

FSB/2D/TRAFFIC 2

FSB/3D 3

FSB/4D 4

FSB/SD 1

FSB/SD/TRAFFIC 1

FSB/6D/TRAFFIC 1

FSB/SOD/AIS 1

FSB/SOD/PCAT 2

ISB/CID/AUTO 2

Page 1 of 1


4:15:55 AM

- 27614 -

.; LPR Distribution By Unit

UNIT LPR Systems

FSB/10 2

FSB/20 2

FSB/20/TRAFFIC 2

FSB/30 3

FSB/40 4

FSB/50 1

FSB/50/TRAFFIC 1

FSB/60/TRAFFIC 1

FSB/500/ AIS 1

FSB/500/PCAT 2

ISB/CIO/AUTO 2

Page 1 of 1


4:16:15 AM

- 27615 -

,.fl&! ~ LPR Distribution By Unit

UNIT LPR Systems

FSB/10 2

FSB/20 2

FSB/20/TRAFFIC 2

FSB/30 3

FSB/40 4

FSB/50 1

FSB/50/TRAFFIC 1

FSB/60/TRAFFIC 1

FSB/500/ AIS 1

FSB/500/PCAT 2

ISB/CIO/AUTO 2

Page 1 of 1


4:15:52 AM

- 27616 -


UNIT LPR Systems

FSB/1D 2

FSB/2D 2

FSB/2D/TRAFFIC 2

FSB/3D 3

FSB/4D 4

FSB/5D 1

FSB/5D/TRAFFIC 1

FSB/6D/TRAFFIC 1

FSB/SOD/ AIS 1

FSB/SOD/PCAT 2

ISB/CID/AUTO 2

Page 1 of 1


4:15:52 AM

- 27617 -


UNIT LPR Systems

FSB/10 2

FSB/20 2

FSB/20/TRAFFIC 2

FSB/30 3

FSB/40 4

FSB/50 1

FSB/50/TRAFFIC 1

FSB/60/TRAFFIC 1

FSB/500/ AIS 1

FSB/500/PCAT 2

ISB/CIO/AUTO 2

Page 1 of 1


4:16:14 AM

- 27618 -


UNIT LPR Systems

FSB/10 2

FSB/20 2

FSB/20/TRAFFIC 2

FSB/30 3

FSB/40 4

FSB/50 1

F5B/50/TRAFFIC 1

F5B/60/TRAFFIC 1

F5B/500/ AIS 1

F5B/500/PCAT 2

15B/CIO/AUTO 2

Page 1 of 1

Sunday, July 15, 2012

4:16:30 AM

- 27619 -


UNIT LPR Systems

FSB/10 2

FSB/2D 2

FSB/2D/TRAFFIC 2

FSB/3D 3

FSB/4D 4

FSB/SD 1

FSB/SD/TRAFFIC 1

FSB/6D/TRAFFIC 1

FSB/SOD/AIS 1

FSB/SOD/PCAT 2

ISB/CID/ AUTO 2

Page 1 of 1

Friday, July 13, 2012

4:16:01 AM

- 27620 -


UNIT LPR Systems

FSB/10 2

FSB/2D 2

FSB/2D/TRAFFIC 2

FSB/3D 3

FSB/4D 4

FSB/SD 1

FSB/SD/TRAFFIC 1

FSB/6D/TRAFFIC 1

FSB/SOD/ AIS 1

FSB/SOD/PCAT 2

ISB/CID/AUTO 2

Page 1 of 1


4:16:10 AM

- 27621 -


UNIT LPR Systems

FSB/10 2

FSB/20 2

FSB/20/TRAFFIC 2

FSB/30 3

FSB/40 4

FSB/50 1

FSB/50/TRAFFIC 1

FSB/60/TRAFFIC 1

FSB/SOO/ AIS 1

FSB/SOO/PCAT 2

ISB/CIO/AUTO 2

Page 1 of 1


4:16:09 AM

- 27622 -


UNIT LPR Systems

FSB/1D 2

FSB/2D 2

FSB/2D/TRAFFIC 2

FSB/3D 3

FSB/4D 4

FSB/SD 1

FSB/SD/TRAFFIC 1

FSB/6D/TRAFFIC 1

FSB/SOD/ AIS 1

FSB/SOD/PCAT 2

ISB/CID/AUTO 2

Page 1 of 1


4:16:26 AM

- 27623 -


UNIT LPR Systems

FSB/lD 2

FSB/20 2

FSB/20/TRAFFIC 2

FSB/30 3

FSB/40 4

FSB/50 1

FSB/50/TRAFFIC 1

FSB/60/TRAFFIC 1

FSB/500/ AIS 1

FSB/500/PCAT 2

ISB/CIO/AUTO 2

Page 1 of 1


4:16:16 AM

- 27624 -

,._, LPR Distribution By Unit

UNIT LPR Systems

FSB/10 2

FSB/20 2

FSB/20/TRAFFIC 2

FSB/30 3

FSB/40 4

FSB/50 1

FSB/50/TRAFFIC 1

FSB/60/TRAFFIC 1

FSB/500/ AIS 1

FSB/500/PCAT 2

ISB/CIO/ AUTO 2

Page 1 of 1


4:16:46 AM

- 27625 -


UNIT LPR Systems

FSB/10 2

FSB/20 2

FSB/20/TRAFFIC 2

FSB/30 3

FSB/40 4

FSB/50 1

FSB/50/TRAFFIC 1

FSB/60/TRAFFIC 1

FSB/500/ AIS 1

FSB/500/PCAT 2

ISB/CIO/ AUTO 2

Page 1 of 1


4:16:43 AM

- 27626 -


UNIT LPR Systems

FSB/lD 2

FSB/20 2

FSB/20/TRAFFIC 2

FSB/30 3

FSB/40 4

FSB/50 1

FSB/50/TRAFFIC 1

FSB/60/TRAFFIC 1

FSB/500/AIS 1

FSB/500/PCAT 2

ISB/CIO/ AUTO 2

Page 1 of 1


4:15:34 AM

- 27627 -

• ' "

LPR Distribution By Unit

UNIT LPR Systems

FSB/10 2

FSB/20 2

FSB/20/TRAFFIC 2

FSB/30 3

FSB/40 4

FSB/50 1

FSB/50/TRAFFIC 1

F5B/60/TRAFFIC 1

FSB/500/ AIS 1

FSB/500/PCAT 2

ISB/CIO/ AUTO 2

Page 1 of 1


4:15:53 AM

- 27628 -


UNIT LPR Systems

FSB/1D 2

FSB/2D 2

FSB/2D/TRAFFIC 2

FSB/3D 3

FSB/4D 4

FSB/SD 1

FSB/SD/TRAFFIC 1

FSB/6D/TRAFFIC 1

FSB/SOD/ AIS 1

FSB/SOD/PCAT 2

ISB/CID/AUTO 2

Page 1 of 1

Friday, June 29, 2012

4:15:37 AM

- 27629 -


UNIT LPR Systems

FSB/lD 2

FSB/20 2

FSB/20/TRAFFIC 2

FSB/30 3

FSB/40 4

FSB/50 1

FSB/50/TRAFFIC 1

FSB/60/TRAFFIC 1

FSB/500/AIS 1

FSB/500/PCAT 2

ISB/CIO/ AUTO 2

Page 1 of 1

Thursday, June 28, 2012

4:15:50 AM

- 27630 -


UNIT LPR Systems

FSB/10 2

FSB/20 2

FSB/20/TRAFFIC 2

FSB/30 3

FSB/40 4

FSB/50 1

FSB/50/TRAFFIC 1

FSB/60/TRAFFIC 1

FSB/500/ AIS 1

FSB/500/PCAT 2

ISB/CIO/ AUTO 2

Page 1 of 1

Wednesday, June 27, 2012

4:15:51 AM

- 27631 -


UNIT LPR Systems

FSB/lD 2

FSB/2D 2

FSB/2D/TRAFFIC 2

FSB/3D 3

FSB/4D 4

FSB/SD 1

FSB/SD/TRAFFIC 1

FSB/6D/TRAFFIC 1

FSB/SOD/AIS 1

FSB/SOD/PCAT 2

ISB/CID/ AUTO 2

Page 1 of 1

Tuesday, June 26, 2012

4:15:37 AM

- 27632 -


UNIT LPR Systems

FSB/lD 2

FSB/2D 2

FSB/2D/TRAFFIC 2

FSB/3D 3

FSB/4D 4

FSB/SD 1

FSB/5D/TRAFFIC 1

FSB/6D/TRAFFIC 1

FSB/SOD/ AIS 1

FSB/SOD/PCAT 2

ISB/CID/ AUTO 2

Page 1 of 1

Monday, June 25, 2012

4:15:37 AM

- 27633 -


UNIT LPR Systems

FSB/1D 2

FSB/2D 2

FSB/2D/TRAFFIC 2

FSB/3D 3

FSB/4D 4

FSB/SD 1

FSB/SD/TRAFFIC 1

FSB/6D/TRAFFIC 1

FSB/SOD/ AIS 1

FSB/SOD/PCAT 2

ISB/CID/AUTO 2

Page 1 of 1

Sunday, June 24, 2012

4:15:58 AM

- 27634 -


UNIT LPR Systems

FSB/10 2

FSB/20 2

FSB/20/TRAFFIC 2

FSB/30 3

FSB/40 4

FSB/50 1

FSB/50/TRAFFIC 1

FSB/60/TRAFFIC 1

FSB/500/ AIS 1

FSB/500/PCAT 2

ISB/CIO/AUTO 2

Page 1 of 1

Saturday, June 23, 2012

4:16:21 AM

- 27635 -

~~~d{~eHt. The License Plate Recognition (LPR) program seeks to increase safety in Montgomery County while reducing the impact caused by homeland security threats, auto theft and other

Documents