Cody Cobra

No recent searches

Cody Cobra

Created by Russ Hartle, Modified on Tue, 11 Nov, 2025 at 10:08 AM by Russ Hartle

COBRA.net Data Aggregation Platform

Wholistic, future-proofed foundation for data integration

COBRA.net is a wholistic, real-time data source integration, exchange and sharing platform that allows an organization, agency or group of agencies to harness their data sources and focus them for meeting today’s challenges involving big data.

Whether it is consortiums of law enforcement agencies with many isolated RMS databases, a fusion center needing to integrate data sources for one-stop search, or a state looking to mitigate social services fraud, COBRA.net forms the future-proofed foundation for an organization or consortium’s data integration infrastructure.

Benefit Highlights:

See your entire data picture with one search

Stop wasting valuable time searching each of your numerous data sources separately. COBRA.net provides ONE, single view of any number of data sources, with one single sign-on.

Aggregate, share and exchange cross-system data in real-time

Whether you search two sources or two hundred, COBRA.net’s powerful cross-system exchange allows any number of agencies to share and exchange information from any number of sources/systems in real-time.

Protect your data systems from obsolescence

Future-proof your data integration strategy by building an independent data foundation first. COBRA.net allows you to interchange the tools you use to access and query your data without disrupting the actual data foundation. Read more about this data foundation independence here.

Conform to prevailing national sharing standards (NIEM, LEX, etc.)

COBRA.net natively works with prevailing data standards, including NIEM and LEX to allow data systems to communicate, exchange and share data. Further, even if participating agencies have RMS or other data systems that are not compatible with such standards, COBRA.net still makes the data from all agencies interoperable with them.

Extend your foundation with best-of-breed tools: Inform analytics, dashboards, etc.

With COBRA.net’s tool-agnostic nature, you can BYOT (Bring Your Own Tools) to make the cross-system data work for you. Fuel any number of external systems and third party tools, including visual analysis, real-time intel and dashboards SIMULTANEOUSLY with one unified data picture. Also feed upstream databases such as N-DEx, NIBRS, etc.

Fluid Data Model adaptable for any mission

COBRA.net adapts to meet the needs of any type of agency or organization (or group of agencies). Whether your data involves criminals, medical patients, police incidents, information on government benefits, doctors, employees, healthcare providers, state licensing, intelligence or any other type of data, COBRA.net’s data model will adjust to work with your mission.

Total encryption: meeting FBI/CJIS requirements

Retain 100% integrity, fidelity and security for all data sources, with FIPS 140-2 encryption and CJIS compliance.

More information about Cody Cobra can be found here: Cody Website

Setup and Configuration

We provided Cody with a list of database views that they could query for the Cobra.net interface. These views will allow them to utilize the data output from the views or build their own SQL by joining the views. These views are maintained by our DBUpdate process and should be widely available.

Notes on Views :

There is no data dictionary per se. The clearest way to obtain information from the database is by selecting data from, singly or joined, the views that are provided in the database rather than the tables directly. Descriptions of the types of views follow. Please note that if different or extra information is required from the views, that they can easily be added to or extended on request, which would be our preference. However if necessary, the view source can instead be used as sample code to construct your own database SQL.

Hopefully, these views, which are intended to provide comprehensive access to the data, will help answer many of your questions. At a minimum, they should answer your questions on Person attributes, Organizations, and Property, either by using the views directly or by looking at the underlying SQL.

Main View Types

EFCS_* views show ARREST table records (arrest records where they exist, which are always linked to a contact (INC_CONTACT) within a case (INCIDENT). Contacts in a case can usually be either persons or organizations, but ARREST table records refer to persons only.
MAI_* views show Master Address Information
MI_* views show Case or Call Information
MNI_* views show Master Name Index (person) information
MOI_* views show Master Organization Index information
MPI_* views show Master Property Index information
MVI_* views show Master Vehicle Index information

EFCS_* views (ARREST)

All EFCS views contain arrest_number, which is unique among arrest records, and usually pertain to the arrestee the arrest record is for.

EFCS_ARRESTEE contains personal details (height, weight, race, name etc.)
EFCS_ALIAS contains aliases that have been used, if any
EFCS_BOOKINGPHOTO contains photos of arrestees
EFCS_CHARGE contains charge information
EFCS_COURT contains court date and charge description
EFCS_MARKING contains details on scars and other markings
EFCS_NUMBER contains agency-defined strings and/or numbers, type and value, for arrestees
EFCS_SSN contains SSNs

MAI_* views (ADDRESS)

Master Address Index views contain details of addresses alone, address/case combinations or address call combinations. I’ll call the latter “case addresses” and “call addresses” respectively. All these views contain ADDRESS_ID.

MAI_ADDRESS contains address information
MAI_CALL contains call_number, call notes, call type and date of call for call addresses
MAI_CRIME contains crime information for case addresses
MAI_MODUS_OPERANDI contains MO information for case addresses
MAI_NOTE contains notes made on addresses
MAI_PHOTO contains photos related to addresses
MAI_PRIOR contains related case information (and call type for the call the case was created from, if any) for addresses
MAI_RESIDING_ORGANIZATION contains ORGANIZATION_ID and details such as address_type for address/organization combinations
MAI_RESIDING_PERSON contains PERSON_ID and details such as address_type for address/person combinations

MI_* views (Case, Call, Citation, Miscellaneous)

These views display information that is generic, miscellaneous or pertaining to cases, calls or citations. They often contain key fields so you can join them to other queries.

MI_AFFILIATION contains PERSON_ID, ORGANIZATION_ID, and the person’s role within the organization
MI_ALARM_BILLING contains alarm billing information, including fines and payments, for contacts (BILL_ADDRESSEE_ID, can be either a PERSON_ID or ORGANIZATION_ID) and related address information
MI_CALL contains call contact information. It contains the id of the person or organization (ENTITY_ID, can join to PERSON_ID or ORGANIZATION_ID in other views), their role as contact within the call, call_number, date_reported and call_type
MI_CALL_VEHICLE contains PERSON_ID, VEHICLE_ID, call_number and other person/vehicle/call information
MI_CASE_VEHICLE contains PERSON_ID, VEHICLE_ID, case_number and other person/vehicle/case information
MI_CITATION_CRIME contains CITATION_ID and crime details for crimes in that citation
MI_ CRIME contains contact ENTITY_ID, which can be a PERSON_ID or ORGANIZATION_ID, and crime details and counts for crimes related to that contact
MI_CRIMINAL_CITATION contains CITATION_ID, DEFENDANT_ID (can be a PERSON_ID or ORGANIZATION_ID), citation_number and citation information for criminal citations
MI_PRIOR contains ENTITY_ID (can be a PERSON_ID or ORGANIZATION_ID), case_number, and related case information for case contacts
MI_TICKET contains VEHICLE_ID, OWNER_ID (can be a PERSON_ID or ORGANIZATION_ID), ticket_number and vehicle details for parking ticket/vehicle combinations
MI_TRAFFIC_CITATION contains CITATION_ID, DEFENDANT_ID (can be a PERSON_ID or ORGANIZATION_ID), citation_number and citation information for traffic citations

MNI_* views (PERSON)

All these views contain PERSON_ID.

MNI_ADDRESS contains ADDRESS_ID and person/address combinations
MNI_ASSOCIATION contains ASSOCIATION_ID, which is a PERSON_ID of an associate , and associate details
MNI_CONCEALED_WEAPON contains concealed weapon permit information
MNI_FIELD_INTERVIEW contains person/field interview combinations
MNI_LICENSE contains person/driver’s license combinations
MNI_MARKING contains person/marking (scars, tattoos etc.) combinations
MNI_MODUS_OPERANDI contains person/modus operandi combinations
MNI_NOTE contains person/note combinations
MNI_NUMBER contains person/agency-defined number combinations
MNI_OFFICER_SAFETY contains person/officer safety information
MNI_PERSON contains person details (height, race, name etc.)
MNI_PHONE contains person/phone number combinations
MNI_PHOTO contains person/photo combinations
MNI_PRISON_ALTERNATIVE contains person/prison alternative (parole, probation or incarceration) combinations
MNI_REGISTRATION contains person/offender registration (sex, arson, drug) combinations
MNI_SPECIAL_HANDLING contains person/special handling information combinations
MNI_WARNING contains person/warning information
MNI_WARRANT contains person/warrant information

MOI_* views (ORGANIZATION)

All these views contain ORGANIZATION_ID.

MOI_ADDRESS contains ADDRESS_ID and organization/address combinations
MOI_MODUS_OPERANDI contains organization /modus operandi combinations
MOI_NOTE contains organization/note combinations
MOI_ORGANIZATION contains organization details
MOI_PHONE contains organization/phone number combinations
MOI_WARNING contains organization/warning information
MOI_WARRANT contains organization/warrant information
MOI_* views show Master Organization Index information

MPI_* views (PROPERTY)

All these views contain PROPERTY_ID.

MPI_CALL contains property/call combinations.
MPI_CONCEALED_WEAPON_PERMIT contains person/concealed weapon permit combinations for property
MPI_CONTACT_PROPERTY contains property/ENTITY_ID (PERSON_ID or ORGANIZATION_ID) combinations
MPI_PHOTO contains property photos
MPI_PROPERTY contains property details, which may include weapon, jewelry, firearm, vehicle, drug or miscellaneous properties depending on what the property is (OBJECT_TYPE)
MPI_PROPERTY_ROLE contains property details in cases, eg. Stolen, Recovered or Evidence details

MVI_* views (VEHICLE)

All these views contain VEHICLE_ID.

MVI_ADDRESS contains ADDRESS_ID and vehicle owner/address combinations
MVI_CALL contains vehicle/call combinations
MVI_CRIME contains the cross product of crimes and vehicles in cases. The usefulness of this view escapes me, to be honest
MVI_OCCUPANT contains PERSON_ID and case number of occupant/vehicle combinations (for traffic incidents, eg. Driver, Passenger)
MVI_PERMIT contains vehicle/vehicle user permit combinations
MVI_PHONE contains vehicle owner/phone combinations
MVI_PHOTO contains photos of vehicles
MVI_PRIOR contains vehicle/case combinations
MVI_TRAFFIC_CITATION contains vehicle/citation combinations
MVI_VEHICLE contains vehicle details, including up to two owners, of which one may be an organization.
MVI_WARNING contains vehicle/warning combinations
To avoid complicating things, and expecting you to be able to examine the sql making up the views, I have left out the view definitions from this document. A very simple query might be: select * from MVI_VEHICLE where color_1 = ‘BLUE’;

An additional clarification: for most of the view “types” there is one particular view that shows the lion’s share of the data for that “class” of view. Specifically:

MAI_ADDRESS shows address fields
MNI_PERSON shows person fields
MOI_ORGANIZATION shows organization fields
MPI_PROPERTY shows property fields
MVI_VEHICLE shows vehicle fields

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article! *

Feedback sent

We appreciate your effort and will try to fix the article