DoD Manual 7730.47-M_vol1

773047m_vol1.pdf

Download Original Safe Download (PDF)

File Info Search Share Print Help Open in Adobe Viewer  

0/0

×

Information

×

Content scan completed. The original file can be downloaded by clicking the download button if permitted by your policy.

• Content scan completed

OK

×

Help

×

To enable safe viewing of documents and attachments, all active or risky content is executed away from the endpoint with a safe version rendered in the document viewer.

To download either the safe PDF version or original document, click on the download icon in the top right corner of the viewer. The download button may be greyed out, you will not be able to download the original version of a document if it has been found to contain malware or if your administrator has prevented it.

You may be able to download a Safe PDF version of the document.

File Info, Search, Share, and Print options can be accessed by clicking on the three dots in the top right hand corner of the document viewer.

File Info - File Info shows the properties of the document, including created date, modified date and author.

Search - Opens a search dialog bar. Upon entering a search term and clicking ‘Enter’ the UI reports the total number of hits and highlights the matching terms in the page. The user can navigate forward and backwards through the matching terms in the document. Pages are dynamically loaded in order to display the next matching search result.

Share - Displays a new dialog containing a link to the original URL of the document with a button to copy the URL. This option is not available for email attachments.

Print - selecting 'Print' opens the Print dialogue, showing a preview of the printed document, with the ability to scroll through all the pages of the document. Clicking the printer icon opens the printer settings for the selected printer.

OK

Please use the "Print" button to print the document.

Problems viewing this file?

×

You can open it using the Adobe Viewer by clicking the options menu.

Got It!

Department of Defense

MANUAL

NUMBER

7730.47-M, Volume 1

December 7, 2010

Incorporating Change 3, Effective September 18, 2020

USD(I&S)

SUBJECT: Defense Incident-Based Reporting System (DIBRS): Data Segments and Elements

References: See Enclosure 1

1. PURPOSE

a. Manual. This Manual is composed of several volumes, each containing its own purpose,

and reissues DoD 7730.47-M (Reference (a)). The purpose of the overall Manual, in accordance

with the authority in DoD Directive (DoDD) 5124.02 (Reference (b)), is to implement the policy

in DoD Instruction (DoDI) 7730.47 (Reference (c)) and to assign responsibilities and prescribe

procedures for managing the DIBRS.

b. Volume. This Volume:

(1) Prescribes the reporting data elements needed to comply with Federal criminal

incident reporting pursuant to the note to section 534 of title 28, United States Code (U.S.C.)

(also known and hereafter referred to as “The Uniform Federal Crime Reporting Act of 1988, as

amended” (Reference (d))) and the note to section 922 of title 18, U.S.C. (also known and

hereafter referred to as “The Brady Handgun Violence Prevention Act of 1993, as amended”

Reference (e))).

(2) Incorporates and cancels Under Secretary of Defense for Personnel and Readiness

(USD(P&R)) Memorandums (References (f) and (g)) and Deputy Under Secretary of Defense

for Program Integration Memorandum (Reference (h)).

(3) Continues to require maintenance of:

(a) A central database on incidents of domestic violence involving members of the

Military Services pursuant to section 1562 of title 10, U.S.C. (Reference (i)) and DoDI 6400.01

(Reference (j)).

(b) A central repository of criminal incident data to enhance DoD effectiveness in

responding to executive, legislative, and ad hoc requests for statistical information relating to

criminal and other high-interest incidents.

DoDM 7730.47-M-V1, December 7, 2010

2. APPLICABILITY. This Volume applies to OSD, the Military Departments, the Office of the

Chairman of the Joint Chiefs of Staff and the Joint Staff, the Combatant Commands, the Office

of the Inspector General of the Department of Defense (IG DoD), the Defense Agencies, the

DoD Field Activities, and all other organizational entities within the Department of Defense

(hereafter referred to collectively as the “DoD Components”).

3. POLICY. DIBRS policy is set forth in section 4 of Reference (c).

4. RESPONSIBILITIES. See Enclosure 2.

5. PROCEDURES. See Enclosures 3 through 5.

6. INFORMATION REQUIREMENTS. The information requirements of Enclosures 3 through

5 have been assigned Report Control Symbol DD-P&R(M)1973 in accordance with DoD Manual

8910.01 (Reference (k)).

7. RELEASABILITY.

Cleared for public release

. This Volume is available on the Directives

Division Website at https://www.esd.whs.mil/DD/.

8. SUMMARY OF CHANGE 3. This administrative change updates:

a. The title of the Under Secretary of Defense for Intelligence to the Under Secretary of

Defense for Intelligence and Security in accordance with Public Law 116-92 (Reference (l)).

b. Administrative changes in accordance with current standards of the Office of the Chief

Management Officer of the Department of Defense.

Change 3, 09/18/2020 2

DoDM 7730.47-M-V1, December 7, 2010

9. EFFECTIVE DATE. This Volume is effective December 7, 2010.

Clifford L. Stanley

Under Secretary of Defense for

Personnel and Readiness

Enclosures

1. References

2. Responsibilities

3. General Procedures

4. Segment Formats

5. Data Submission Procedures

Glossary

Change 3, 09/18/2020 2

DoDM 7730.47-M-V1, December 7, 2010

TABLE OF CONTENTS

ENCLOSURE 1. REFERENCES ...................................................................................................5

ENCLOSURE 2. RESPONSIBILITIES .........................................................................................7

USD(P&R) .................................................................................................................................7

IG DoD.......................................................................................................................................7

HEADS OF THE DoD COMPONENTS WITH LAW ENFORCEMENT

ORGANIZATIONS .............................................................................................................8

SECRETARIES OF THE MILITARY DEPARTMENTS ........................................................8

ENCLOSURE 3. GENERAL PROCEDURES ..............................................................................9

INTRODUCTION .....................................................................................................................9

REPORTING PROCESS OVERVIEW ..................................................................................12

ENCLOSURE 4. SEGMENT FORMATS ...................................................................................16

DISCIPLINARY INCIDENTS ................................................................................................16

DoD DATABASE OF DOMESTIC VIOLENCE INCIDENTS .............................................18

OTHER REPORTABLE INCIDENTS ...................................................................................19

ADMINISTRATIVE SEGMENT ...........................................................................................19

OFFENSE SEGMENT ............................................................................................................22

PROPERTY SEGMENT .........................................................................................................27

VICTIM SEGMENT ...............................................................................................................32

OFFENDER/ARRESTEE SEGMENT ....................................................................................38

COMMANDER’S REPORT OF ACTION TAKEN SEGMENT ...........................................46

RESULTS OF TRIAL SEGMENT..........................................................................................52

CORRECTIONS SEGMENT ..................................................................................................65

ENCLOSURE 5. DATA SUBMISSION PROCEDURES ...........................................................73

INFORMATION REQUIREMENTS ......................................................................................73

SUBMISSION INSTRUCTIONS ...........................................................................................74

CORRECTION OF RECORDS ..............................................................................................74

AUTHORIZED RELEASE OF INDIVIDUAL INFORMATION .........................................75

AUTHORIZED RELEASE OF STATISTICAL INFORMATION ........................................75

UNAUTHORIZED ACCESS ..................................................................................................76

DATABASE CHANGE MANAGEMENT .............................................................................76

TESTING PROCEDURES FOR UNMATCHED SEGMENTS ............................................76

DIBRS PII SHELF-LIFE .........................................................................................................76

Change 3, 09/18/2020 3 CONTENTS

DoDM 7730.47-M-V1, December 7, 2010

GLOSSARY ..................................................................................................................................78

ABBREVIATIONS AND ACRONYMS ................................................................................78

DEFINITIONS.........................................................................................................................78

TABLES

1. Administrative Segment ......................................................................................................21

2. Offense Segment .................................................................................................................23

3. Property Segment ................................................................................................................30

4. Victim Segment ..................................................................................................................34

5. Offender/Arrestee Segment ................................................................................................41

6. Commander’s Report of Action Taken Segment ................................................................48

7. Results of Trial Segment .....................................................................................................55

8. Corrections Segment ...........................................................................................................68

9. PII Shelf Life .......................................................................................................................77

Change 3, 09/18/2020 4 CONTENTS

DoDM 7730.47-M-V1, December 7, 2010

ENCLOSURE 1

REFERENCES

(a) DoD 7730.47-M, “Manual for Defense Incident-Based Reporting System,”

July 25, 2003 (hereby cancelled)

(b) DoD Directive 5124.02, “Under Secretary of Defense for Personnel and Readiness

(USD(P&R)),” June 23, 2008

(c) DoD Instruction 7730.47, “Defense Incident-Based Reporting System (DIBRS),”

January 23, 2014, as amended

(d) Note to section 534 of title 28, United States Code, as amended (also known as “The Uniform

Federal Crime Reporting Act of 1988, as amended”)

(e) Section 13

1

and note to section 922

2

of title 18, United States Code, as amended

(f) Under Secretary of Defense for Personnel and Readiness Memorandum, “Working

Agreement on Implementing the Defense Incident-Based Reporting System (DIBRS) for

Criminal and Related Offenses within the Department of Defense,” September 9, 1994

(hereby cancelled)

(g) Under Secretary of Defense for Personnel and Readiness Memorandum, “Establishment of

DoD Database on Domestic Violence and Procedures for Submitting Domestic Violence

Data,” June 8, 2000 (hereby cancelled)

(h) Deputy Under Secretary of Defense for Program Integration Memorandum, “DIBRS Personal

Identifier Data (PID) Shelf Life Recommendation,” March 15, 2001 (hereby cancelled)

(i) Chapter 47 and section 1562 of title 10, United States Code

(j) DoD Instruction 6400.01, “Family Advocacy Program (FAP),” May 1, 2019

(k) DoD Manual 8910.01, “DoD Information Collections Manual,” June 30, 2014, as amended

(l) Public Law 116-92, “National Defense Authorization Act for Fiscal Year 2020,”

December 20, 2019

(m) DoD 5400.11-R, “Department of Defense Privacy Program,” May 14, 2007

(n) Section 803 of Public Law 110-53, “Implementing Recommendations of the 9/11 Commission

Act of 2007,” August 3, 2007

(o) Section 10601 of title 42, United States Code (also known as “The Victims Rights and

Restitution Act of 1990, as amended”)

(p) Federal Bureau of Investigation, “Uniform Crime Reporting Handbook,” National Incident-

Based Reporting System Edition, August 2002

3

(q) DoD Instruction 1030.2, “Victim and Witness Assistance Procedures,” June 4, 2004

(r) DoD Manual 6025.18, “Implementation of the Health Insurance Portability and

Accountability Act (HIPAA) Privacy Rule in DOD Health Care Programs,” March 13, 2019

(s) Manual for Courts-Martial, United States, 2008 Edition

(t) DoD Directive 1325.04, “Confinement of Military Prisoners and Administration of Military

Correctional Programs and Facilities,” August 17, 2001

(u) Federal Information Processing Standard 10-4, “Countries, Dependencies, Areas of Special

Sovereignty, and Their Principal Administrative Divisions,” April 1995

(v) Section 14071 of title 42, United States Code

1

Also known as “The Assimilative Crimes Act of 1948, as amended.”

2

Also known as “The Brady Handgun Violence Prevention Act of 1993, as amended.”

3

Copies can be obtained by writing to the Communications Unit, Criminal Justice Information Services Division, FBI,

Module 3, 1000 Custer Hollow Road, Clarksburg, WV 26306-0154.

Change 3, 09/18/2020 5 ENCLOSURE 1

DoDM 7730.47-M-V1, December 7, 2010

(w) DoD Instruction 8910.01, “Information Collection and Reporting,” May 19, 2014, as amended

(x) DoD Instruction 8320.02, “Sharing Data, Information, and Technology (IT) Services in the

Department of Defense,” August 5, 2013, as amended

(y) Page 56062 of Volume 72, Federal Register, October 2, 2007

(z) DoD Directive 5400.07, “DoD Freedom of Information Act (FOIA) Program,”

April 5, 2019

Change 3, 09/18/2020 6 ENCLOSURE 1

DoDM 7730.47-M-V1, December 7, 2010

ENCLOSURE 2

RESPONSIBILITIES

1. USD(P&R). The USD(P&R) shall:

a. Develop overall DoD DIBRS policy and monitor DoD Component compliance with

Reference (c).

b. Provide functional guidance to the Heads of the DoD Components in the discharge of

their responsibilities pursuant to this Volume and Reference (c).

c. Oversee the functions of the Defense Manpower Data Center (DMDC) and ensure that

DMDC:

(1) Formulates a data collection mechanism to:

(a) Track and report DIBRS information through the life cycle of a criminal incident.

(b) Report National Incident-Based Reporting System (NIBRS) data to the Federal

Bureau of Investigation (FBI).

(2) Operates and maintains the DIBRS, to include providing computer support, software

development, quality control, inquiry capability, and administrative support.

(3) Provides technical assistance to the DoD Components in the development of software

necessary to implement this Volume and Reference (c).

(4) Maintains the DIBRS database in accordance with DoD 5400.11-R and section 803

of Public Law 110-53 (References (m) and (n)), subject to the provision that disclosure of

DIBRS information containing personal identifying information (PII) within the Department of

Defense is limited solely to DMDC use for official statistical analysis and record verification,

and outside the Department of Defense is limited solely to that necessary to comply with The

Brady Handgun Violence Prevention Act of 1993, as amended.

(5) Ensures that disseminations of DIBRS information within and outside the

Department of Defense containing PII receive equal consideration of the need for the disclosure

and any adverse impacts the release might have upon that individual’s privacy and civil liberties.

d. Establish and provide the Chair for the DIBRS Council, consisting of functional

representatives from each of the DoD Components.

2. IG DoD. The IG DoD shall develop investigative policy and perform appropriate oversight

reviews of the reporting of disciplinary incident data by the Defense Criminal Investigative

Change 3, 09/18/2020 7 ENCLOSURE 2

DoDM 7730.47-M-V1, December 7, 2010

Organizations (DCIOs). This shall not substitute for the routine managerial oversight of the

program provided by the DCIOs, the Office of the USD(P&R) (OUSD(P&R)), the Heads of the

DoD Components, or the Component responsible officials.

3. HEADS OF THE DoD COMPONENTS WITH LAW ENFORCEMENT

ORGANIZATIONS. The Heads of the DoD Components with law enforcement organizations

shall:

a. Ensure compliance with this Volume and Reference (c) and establish policies and

procedures to implement and maintain DIBRS reporting within their respective Components.

b. Designate a Component responsible official to coordinate, implement, and manage the

DIBRS within their respective Components, and to report monthly to DMDC as set forth in

paragraph 2.b. of Enclosure 3 of this Volume.

c. Designate a functional responsible official for each DIBRS functional area for which their

respective Components have reporting requirements to coordinate all reporting for their

Components in the designated functional area, and to provide representation to the DIBRS

Council.

d. Provide for the assignment of personnel in sufficient numbers to enable DIBRS programs

to be carried out effectively.

e. Train personnel to comply with this Volume and Reference (c).

f. Report, pursuant to Reference (c), on each person under their jurisdiction who is the

subject of a reportable incident.

g. Ensure that any database created pursuant to the requirements of Reference (c) is

maintained in accordance with Reference (c) and subject to the restrictions on disclosure set forth

in References (m) and (n).

4. SECRETARIES OF THE MILITARY DEPARTMENTS. The Secretaries of the Military

Departments, in addition to the responsibilities in section 3 of this enclosure, shall:

a. Designate specific reporting responsibilities for their respective Service members who are

assigned to the Combatant Commands.

b. Report cases concerning their respective Service members that are handled by a

Combatant Command.

Change 3, 09/18/2020 8 ENCLOSURE 2

DoDM 7730.47-M-V1, December 7, 2010

ENCLOSURE 3

GENERAL PROCEDURES

1. INTRODUCTION

a. DIBRS Overview

(1) The DIBRS is designed to meet the data repository needs involved in reporting on

overall law enforcement activities and statistics within the Department of Defense, as mandated

by Congress, including:

(a) NIBRS requirements mandated by The Uniform Federal Crime Reporting Act of

1988, as amended.

(b) Victim and witness notifications mandated by section 10601 of title 42, U.S.C.

(also known and hereafter referred to as “The Victim’s Rights and Restitution Act of 1990, as

amended” (Reference (o))).

(c) Case dispositions mandated by The Brady Handgun Violence Prevention Act of

1993, as amended.

(d) Establishment of a central database on domestic violence incidents mandated by

Reference (i).

(e) Recurring requests for overall DoD law enforcement data.

(2) The areas with reporting responsibility are:

(a) Law Enforcement. General police operations, such as those conducted by the

Service military police and civilian police and similar operations, as well as by Defense Agency

civilian police.

(b) Criminal Investigations. Investigations conducted by the Air Force Office of

Special Investigations, the Naval Criminal Investigative Service, the Army Criminal

Investigation Command, the Defense Criminal Investigative Service, or other criminal

investigative organizations within the Department of Defense.

(c) Command Actions. Case dispositions resulting from command authority or

referral for judicial action.

(d) Judicial Functions. Proceedings conducted through military legal offices and

courts responsible for prosecuting DoD offenders.

Change 3, 09/18/2020 9 ENCLOSURE 3

DoDM 7730.47-M-V1, December 7, 2010

(e) Corrections. Actions conducted at military correctional facilities and by persons

responsible for DoD employees convicted of a crime and sentenced to imprisonment.

b. NIBRS Overview. Since the inception of the Uniform Crime Reporting (UCR) Program

in 1930, the FBI has been collecting crime data dealing with offenses and arrests from

approximately 16,000 county, State, and Federal law enforcement agencies. The FBI uses the

data to develop a reliable set of criminal statistics for law enforcement agencies throughout the

country to use in their administration, operation, and management.

(1) During the late 1970s, the law enforcement community called for expanded use of

the UCR Program and developed new guidelines for reporting crime statistics. These guidelines

formed the basis of NIBRS, as mandated by The Uniform Federal Crime Reporting Act of 1988,

as amended. NIBRS requires law enforcement agencies, including those within the Department

of Defense, to report NIBRS data to the Department of Justice for inclusion in the FBI-

maintained system pursuant to FBI handbook (Reference (p)).

(2) The FBI assembles, publishes, and distributes the data to contributing agencies,

including the Department of Defense, State UCR programs, Government bodies, and others

interested in the Nation’s crime problem. Law enforcement agencies consider NIBRS data to be

an indispensable tool in the war against crime because it provides them with detailed, accurate,

and meaningful statistical data about when and where crime takes place, what form it takes, and

the characteristics of its victims and perpetrators. Law enforcement personnel and Government

agencies armed with this information can request and allocate resources, and inform interested

parties on the effort to combat crime.

c. Victim-Witness Act. Pursuant to The Victims Rights and Restitution Act of 1990, as

amended, victims and selected witnesses must be notified of their rights at certain phases of the

case, from the time of initial contact by law enforcement through the investigation phase,

prosecution phase, and, if the case results in confinement, the change in confinement status. The

confinement authority must advise the victim or witness of an inmate’s status, to include length

of sentence, anticipated earliest release date, place of confinement, the possibility of transfer, the

possibility of parole or clemency, release from confinement, escape, and death. DoDI 1030.2

(Reference (q)) requires the use of DD Form 2705, “Victim/Witness Notification of Inmate

Status,” for this purpose. (DD Form 2705 is available on the Internet at

http://www.dtic.mil/whs/directives/infomgt/forms/ddforms2500-2999.htm.) The DIBRS

requires that the number of victim-witness notifications be reported to DMDC in accordance

with The Victim’s Rights and Restitution Act of 1990, as amended.

d. Brady Act. The DIBRS shall be used to centralize the collection of information that is

reportable by the DoD Components pursuant to The Brady Handgun Violence Prevention Act of

1993, which requires the Department of Defense to report these eight categories to the FBI for

purposes of prohibiting firearm purchases:

(1) Persons who have been convicted in any court of a crime punishable by

imprisonment for a term exceeding 1 year.

Change 3, 09/18/2020 10 ENCLOSURE 3

DoDM 7730.47-M-V1, December 7, 2010

(2) Persons who are fugitives from justice.

(3) Persons who are unlawful users of, or addicted to, any controlled substance.

(4) Persons who have been adjudicated as mental defectives or who have been

committed to a mental institution.

(5) Persons who have been discharged from the U.S. Armed Forces under dishonorable

conditions.

(6) Persons who, having been citizens of the United States, have renounced their U.S.

citizenship.

(7) Persons convicted in any court of a misdemeanor crime of domestic violence.

(8) Persons who are under indictment or information for a crime punishable by

imprisonment for a term exceeding 1 year.

e. Database on Domestic Violence. Reference (i) requires the Department of Defense to

establish a central database of information on incidents of domestic violence involving members

of the Military Services. The Military Departments must maintain and report annually any

information received on:

(1) Each domestic violence incident reported to a commander, a law enforcement

authority of the Military Services, or a family advocacy program of the Department of Defense.

(2) The number of those incidents that involve evidence determined sufficient for

supporting disciplinary action and, for each such incident, a description of the allegations and the

action taken by command authorities in the incident.

(3) The number of those incidents that involve evidence determined insufficient for

supporting disciplinary action and, for each such case, a description of the allegation.

f. General Crime Reporting

(1) In addition to meeting the mandatory statutory requirements, the Department of

Defense must ensure a common interface between the functional areas that make up overall DoD

law enforcement. Specifically, the Military Services and OSD have been faced with increasing

requests from Congress, the Department of Justice, and other agencies for statistical data on

criminal offenses and other high-interest issues including suicide, fraternization, drug abuse,

homosexual misconduct, sexual assault, and sexual harassment. These requests necessitate

improvements in the ability of the Department of Defense to track a crime or incident through

the law enforcement, criminal investigation, command action, judicial, and corrections phases.

Change 3, 09/18/2020 11 ENCLOSURE 3

DoDM 7730.47-M-V1, December 7, 2010

(2) The DIBRS shall:

(a) Allow the Department of Defense to respond to requests based on a standard data

system that can track a criminal incident from initial allegation to final disposition.

(b) Allow the Department of Defense to account for cases that are processed

administratively through separation or other actions.

(c) Provide the flexibility to track non-criminal incidents or incidents that are hard to

identify from the name of the offense, which is often the case with sexual harassment.

(d) Ensure that overall law enforcement data compilations using inputs from the

various functional areas are based on consistent data definitions and data collection

requirements.

(e) Enable the DoD Components and organizations involved in law enforcement to

transfer information electronically between the functional areas.

(f) Ensure data is collected, maintained, used, and disseminated in accordance with

References (m) and (n).

2. REPORTING PROCESS OVERVIEW

a. To satisfy the requirements of this Volume, a DIBRS incident report shall be initiated for

each reportable incident, as defined in Reference (c), by the lead investigative agency or, in those

cases initiated without law enforcement or investigative involvement, by the commander of the

Service member involved. The DIBRS is primarily a reporting system covering active duty

military personnel; however, civilians fall within the reporting requirements of DoD law

enforcement organizations pursuant to the NIBRS reporting requirement.

(1) The nature of reportable incidents shall be captured and tabulated through the use of

the specific coding provided in Enclosure 2 to Volume 2 of this Manual. Reporting activities

shall:

(a) For incidents involving civilian offenders for which there is a NIBRS reporting

requirement, use the appropriate NIBRS code in Enclosure 2 to Volume 2.

(b) For incidents involving active duty military offenders pursuant to chapter 47 of

Reference (i) (also known and hereafter referred to as “The Uniform Code of Military Justice

(UCMJ)”), use the UCMJ codes in Enclosure 2 to Volume 2.

(c) For suicide incidents, use the special non-criminal fatality code assigned in

Enclosure 2 to Volume 2.

Change 3, 09/18/2020 12 ENCLOSURE 3

DoDM 7730.47-M-V1, December 7, 2010

(2) In addition to specific offense codes, each incident shall be assigned a unique number

to facilitate tracking incidents and cases across functional lines. The law enforcement agency or

command originally reporting the incident shall use its identification number (FBI Location

Number and Incident Number) from initiation of DIBRS reporting through final resolution.

b. Each month, each of the DoD Components shall report new and updated information to

the activity designated by their Component to act as the central collection point for the functional

reporting area (functional consolidating activity). The DoD Components may choose to set up

Component-wide repositories. Either the functional consolidating activity or the Component-

wide repository shall send monthly submissions to DMDC to build the DIBRS database. DMDC

shall provide a DoD response to the reporting requirements of NIBRS, as well as answer

recurring requests for criminal incident data. DMDC shall use DIBRS data to comply with the

requirements of NIBRS; References (m), (n), and (o); and general statistical reporting, including

judicial, non-judicial, and administrative dispositions of incidents.

c. No organization shall submit PII to DMDC that could jeopardize or compromise any

ongoing investigation. In addition, PII shall not be reported on any reportable incident without a

“probable cause” determination that there are reasonable grounds to believe that an offense has

been committed and that the person to be identified as the offender committed it. The

developments involving the offender that shall be construed as the equivalent of a probable

cause determination, and that shall trigger the requirement to report PII as Arrestee/Offender

data, are:

(1) Apprehension.

(2) Taking into custody.

(3) Ordering into pretrial confinement.

(4) Preferral of charges.

(5) Imposition of non-judicial punishment.

(6) Approval of separation from the Service.

(7) Conviction by civilian court.

d. Functional areas with DIBRS reporting responsibilities are:

(1) Law Enforcement. Military law enforcement agencies in most cases shall be

responsible for initiating the reporting process. The DIBRS reporting process shall be triggered

when law enforcement officials respond to a credible report of a criminal incident. Law

enforcement officials shall collect information necessary to fulfill reporting responsibilities,

including the data required by NIBRS. If the crime is determined to be outside the jurisdiction of

the law enforcement organization, the DIBRS reporting responsibility shall be passed to the

appropriate agency, such as the DCIO or other criminal investigative organizations within the

Change 3, 09/18/2020 13 ENCLOSURE 3

DoDM 7730.47-M-V1, December 7, 2010

Department of Defense, the FBI, or the local authority that has accepted investigative jurisdiction

of the case. The responsible DoD Component shall determine whether the case is reportable to

NIBRS based on guidance provided in this Volume. The functional responsible official shall

implement procedures to consolidate and forward monthly DoD Component-wide data to

DMDC.

(2) Criminal Investigations. Two areas involved in the DIBRS that fall within the

criminal investigations area of responsibility are NIBRS and the reporting requirements of

Reference (n). If the investigation is initiated by or referred to a criminal investigative

organization and that organization assumes the lead investigative role, it also assumes DIBRS

reporting responsibility. The investigative organization must coordinate with referring agencies

to ensure the NIBRS reporting responsibility is clearly understood. The functional responsible

official shall implement procedures to establish a functional consolidating activity and forward

monthly DoD Component-wide data to DMDC. A DIBRS incident report shall be considered

cleared for purposes of NIBRS reporting upon apprehension, arrest, or an equivalent stage in the

investigative process.

(3) Command Actions

(a) Investigative agencies shall normally refer cases involving military offenders to

the responsible commander for appropriate action. In these cases, a DIBRS entry for the incident

should be initiated by the law enforcement activity with the lead investigative responsibility.

The commander may refer the case to staff agencies, dispose of the case pursuant to

administrative or non-judicial authority, or refer the case to court-martial or to an appropriate

convening authority for ultimate disposition. Once the action is complete, the commander taking

final action on the case shall report the final disposition action to the functional consolidating

activity. If the case is forwarded to another convening authority for action, the commander

assuming jurisdiction over the case shall be responsible for forwarding appropriate DIBRS

identifying information.

(b) In some instances, commanders shall be required to initiate DIBRS reporting

when a military law enforcement activity is not involved. Commanders must ensure there are

reasonable grounds to believe an offense has been committed and that the person to be identified

as the offender committed it. Referral of charges, imposition of non-judicial punishment,

approval of separation from the Service, and conviction by a civilian court are all examples of

reasonable grounds. Commanders shall ensure that reporting responsibilities and requirements

as prescribed in this Volume are met in these cases.

(c) When PII is used in support of the DIBRS, appropriate safeguards should be

utilized to ensure compliance with References (m) and (n). It is appropriate to include

administrative, physical, and technical safeguards that ensure that PII is protected throughout all

stages of collection, maintenance, use, and dissemination.

(d) Whenever initiating, processing, submitting, or reviewing incidents for DIBRS

reporting, reporting officials must ensure that steps are taken to safeguard the civil liberties of the

alleged offender and other individuals whose PII is included in the report.

Change 3, 09/18/2020 14 ENCLOSURE 3

DoDM 7730.47-M-V1, December 7, 2010

(e) When DoD Military Treatment Facilities disclose protected health information

(PHI) in support of the DIBRS, such disclosures shall comply with the requirements of DoD

Manual 6025.18 (Reference (r)). When PHI is received by non-DoD Military Treatment

Facilities it is then considered to be PII and thereafter subject to the requirements of References

(m) and (n).

(4) Judicial Functions. The two areas involved in the DIBRS that fall in the judge

advocate area of responsibility are the reporting requirements of Reference (n) and the results of

the trial reporting required by Manual of Courts-Martial (Reference (s)), Rule of Court-Martial

1101. Judicial function officials shall report the results of the trial and the identifying

information for offenders qualifying pursuant to The Brady Handgun Violence Prevention Act of

1993, as amended. Legal organizations with DIBRS reporting responsibilities shall forward data

to the functional consolidating activity on a monthly basis. The functional consolidating activity

shall forward data to DMDC on a monthly basis.

(5) Corrections. Confinement facility officials are responsible for entering DIBRS data

on prisoners confined in the facility, regardless of the member’s branch of Service. The Army,

as the Executive Agent for Level III Corrections pursuant to DoDD 1325.04 (Reference (t)),

shall be responsible for updating DIBRS entries for those military prisoners transferred from

Army facilities to the Federal Bureau of Prisons. DIBRS reporting shall document significant

changes in the confinement status and release from confinement. Correctional facilities shall

also report data concerning victim and witness notifications and entries documenting that sex

offender registration processing has been completed if required by the appropriate officials

involved in the case. Confinement facilities shall submit DIBRS data reports to a DoD

Component central confinement repository on a monthly basis. Data gathered from the monthly

submission of these reports shall be consolidated to complete confinement and victim and

witness assistance reports currently prepared for the Department of Defense, the Congress, and

the Department of Justice.

Change 3, 09/18/2020 15 ENCLOSURE 3

DoDM 7730.47-M-V1, December 7, 2010

ENCLOSURE 4

SEGMENT FORMATS

1. DISIPLINARY INCIDENTS

a. General

(1) The DIBRS is primarily a reporting system covering military personnel on active

duty. Civilians may fall within the reporting requirements of law enforcement pursuant to

NIBRS. Determination that an incident is NIBRS reportable simply identifies those incidents

and the related data elements that must be forwarded by DMDC to the FBI to fulfill NIBRS

requirements. Except for cases involving civilians, these cases shall also require the submission

of additional DIBRS data.

(2) The NIBRS requirement is comprised of six segments (i.e., Administrative, Offense,

Property, Victim, Offender, and Arrestee) and 53 data elements. For military personnel on

ACTIVE DUTY ONLY, the DIBRS adds a Commander’s Action Segment, Results of Trial

Segment, and Corrections Segment. Data elements required for The Brady Handgun Violence

Prevention Act of 1993, as amended, and References (i) and (n) reporting requirements are

contained throughout all segments. Reporting requirements for civilian offenders are only those

required by NIBRS; therefore only the segments described in paragraph 1.b. of this enclosure

should be submitted for civilians.

(3) In most cases, an initial incident report shall contain the Administrative, Offense,

Property (if applicable), Victim, and Offender Segment(s). Arrestee Segments may also be

included if arrests were made by the time the initial report was submitted. However, in most

cases, arrests shall be made after the initial report and the Arrest Segments shall be submitted as

updates to the initial report. Likewise, the Commander’s Action Segment, Results of Trial

Segment, and Corrections Segment shall generally be submitted as updates.

b. NIBRS Reporting

(1) The FBI compiles detailed reports on two types of offenses, Group A and Group B.

(See Table 9 in Volume 2.) The two groups are based on the amount of reporting required to be

forwarded to the FBI for each group. Initial Group “A” Incident Reports will contain an

Administrative Segment, Offense Segment(s), Property Segment(s) (if applicable), Victim

Segment(s), and Offender Segment(s), to include “unknown” values in the Offender Segment if

information is unknown or unavailable. One or more Arrestee Segments may also be included if

arrests were made by the time the initial report was submitted. However, in most cases, arrests

will be made after the initial report, and the Arrestee Segments will be submitted as updates to

the initial report. Offenses listed as Group B should be reported on arrest and consist of the

Administrative Segment and an Arrestee Segment for each arrestee.

Change 3, 09/18/2020 16 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

(2) Required NIBRS segments and subsequent updates should be submitted for EACH

incident (as defined in the Glossary), even if in each incident the offender is the same and all

incidents would normally be disposed of as one case.

(3) If an arrest involving a Group A offense occurs for which no initial incident report

was previously submitted (e.g., an on-view arrest), a complete incident report must be created

and submitted that provides not only the Arrestee Segment, but also the Administrative, Offense,

Offender, and, as applicable, Property and Victim Segments.

(4) If a group of offenders is acting in concert at the same time and place (as defined in

the Glossary), all of the offenders in the incident are considered to have committed all of the

offenses in the incident. If one or more of the offenders did not act in concert, then there is more

than one incident involved. Normally, the offenses must have occurred during unbroken time

duration and at the same or adjoining locations(s). However, incidents can also be comprised of

offenses that, by their nature, involve continuing criminal activity by the same offender(s) at

different times and places, as long as the activity is deemed to constitute a single criminal

transaction.

(a) Example. Two offenders robbed a bar. The bartender was forced at gunpoint to

surrender money from the cash register. The robbers also took money and jewelry from three

customers. One of the robbers, in searching for more customers to rob, found a female customer

in the restroom and raped her there outside the view of the other offender. When the rapist

returned, both robbers left. There were two incidents, one involving robbery and the other

involving forcible rape, because the offenders were not acting in concert in both offenses. If,

however, the rape had occurred in the bar and the other offender told the rapist to stop and only

rob the victim, there was only one incident with two offenses. Although the other robber did not

consent to the rape, by displaying a gun he prevented someone coming to the victim’s assistance

and thereby assisted in the commission of the crime.

(b) Example. Over a period of 18 months, a computer programmer working for a

bank manipulated the bank’s computer and systematically embezzled $70,000. The continuing

criminal activity constituted a single incident involving the crime of embezzlement.

(5) To be certain that data are not reported more than once by overlapping jurisdictions,

these guidelines have been developed for NIBRS reporting:

(a) City law enforcement agencies report offenses that occur within their city

boundaries for offenses for which they are the investigative agency.

(b) County and State law enforcement agencies report offenses that take place in

their jurisdiction for which they are the investigative agency.

(c) Federal agencies report offenses within their investigative jurisdictions if they are

not being reported by a local or State law enforcement agency.

Change 3, 09/18/2020 17 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

(d) When two or more Federal, State, or local agencies are involved in the

investigation of the same offense and there is a written or oral agreement defining the roles of the

investigating agencies, the agreement should designate which agency shall report the offense.

(e) When two or more Federal agencies are involved in the investigation of the same

offense and there is no written or oral agreement defining their roles, the Federal agency having

“lead” or “primary” investigative jurisdiction shall report the incident. If there is uncertainty as

to which is the lead or primary agency, the agencies should agree on which agency shall report

the offense.

(f) Agencies report only those arrests made for offenses committed within their own

boundaries and jurisdictions.

(g) Likewise, the recovery of property is reported only by the agency that first

reported it missing and stolen, regardless of whom or what agency recovered it.

c. Non-NIBRS Reporting

(1) Some incidents may trigger DIBRS, but not NIBRS, reporting (e.g., the UCMJ

offenses listed in Enclosure 2 to Volume 2 that do not have NIBRS codes, or Category B

offenses when there is no arrest). In addition, reportable disciplinary incidents for which only

Category B reporting for NIBRS is triggered, AND active duty military members are the

offenders, have additional DIBRS reporting requirements. In all these instances, the

Administrative, Offense, Property, Victim, Offender, Arrestee, Commander’s Action, Results of

Trial, and Corrections Segments, as applicable, must still be submitted.

(2) When reporting the felony conviction of military personnel on active duty for civilian

criminal incidents, the Results of Trial and Corrections Segments need not be submitted.

2. DoD DATABASE OF DOMESTIC VIOLENCE INCIDENTS

a. Pursuant to Reference (i), each domestic violence incident reported to a commander, a law

enforcement authority of the Military Services, or a family advocacy program of the Department

of Defense shall be reported. Reporting requirements include the number of those incidents that

involve evidence determined sufficient for supporting disciplinary action and, for each such

incident:

(1) A description of the substantiated allegations and the action taken by command

authorities in the incident.

(2) The number of those incidents that involve evidence determined insufficient for

supporting disciplinary action and, for each such case, a description of the allegation.

b. The database required by Reference (i) shall be a DIBRS subset comprised of data

elements from seven segments (i.e., Administrative, Offense, Property, Victim,

Change 3, 09/18/2020 18 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

Offender/Arrestee, Commander’s Action, and Results of Trial Segments). DMDC shall match

Family Advocacy Program data, as defined in Reference (j), with DIBRS data submitted

according to this Volume to satisfy reportable information requirements.

c. Pursuant to References (m) and (n), all appropriate administrative, physical, and

technical safeguards will be used to prevent system access by unauthorized individuals.

3. OTHER REPORTABLE INCIDENTS

a. “Not a crime” offenses, incidences of non-criminal fatalities such as suicide of active duty

military members, and offenses pursuant to section 13 of Reference (e) (also known as “The

Assimilative Crimes Act of 1948, as amended”) require submission of the Administrative,

Offense Segment, Offender/Arrestee Segment, Victim Segment (if applicable), and Property

Segment (if applicable) .

b. Instances in which a person is adjudged a mental defective or committed to a mental

institution are reportable pursuant to The Brady Handgun Violence Prevention Act of 1993, as

amended.

4. ADMINISTRATIVE SEGMENT

a. The Administrative Segment contains administrative information that is applicable to the

entire incident report (e.g., the identifying number assigned to the incident and the date and hour

the incident occurred). A single Administrative Segment is to be submitted for each reported

incident. Specific information on each data element is included in the Data Element Dictionary,

Enclosure 3 to Volume 2. The Administrative Segment data layout is displayed in Table 1.

b. Data elements used in the Administrative Segment are:

(1) FBI Location Number. (The FBI calls this the “Originating Agency Identifier” (or

“ORI”) Number.)

(2) Incident Number.

(3) Segment Type.

(4) Report Type.

(5) Reportable to NIBRS.

(6) Incident/Report Occurred Date Category.

(7) Incident/Report Occurred Begin Date/Hour.

Change 3, 09/18/2020 19 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

(8) Incident/Report Occurred End Date/Hour.

(9) Incident Clearance Reason.

(10) Exceptional Clearance Date.

(11) Number of Victims Notified (DD Form 2701, “Initial Information for Victims and

Witnesses of Crime,” available at

http://www.dtic.mil/whs/directives/infomgt/forms/ddforms2500-2999.htm).

(12) Number of Witnesses Notified (DD Form 2701).

c. This segment is prepared by the lead agency and may be updated at any time within the

incident life cycle.

d. For purposes of making entries in Field 11 of the Administrative Segment, “Incident

Clearance Reason,” these developments shall be equivalent to an arrest (leading to block marked

“X”):

(1) Apprehending or taking the accused into custody.

(2) Ordering the accused into pretrial confinement.

(3) Preferring charges.

(4) Initiating non-judicial punishment proceedings.

(5) Initiating administrative separation based on commission of criminal offenses.

(6) Any other circumstances in which these three criteria are met:

(a) Investigation clearly and definitively establishes the identity of an offender.

(b) Probable cause exists to support prosecuting the offender.

(c) Location of the offender is known.

Change 3, 09/18/2020 20 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

Table 1. Administrative Segment

FIELD

NUMBER

FIELD NAME DOMAIN

RECORD

SIZE STANDARD NAME

POSITION

1 FBI Location Number TEXT 1 9 Derived:

Organization-

Designator Source

Assigned Identifier

2 Incident Number TEXT 10 12 Derived:

Organization-

Designator Source

Assigned Identifier;

Situation Identifier

3 Segment Type M 22 1 No Standard

4 Report Type A=ADD 23 1 No Standard

M=MODIFY

D=DELETE

5 Reportable to NIBRS Y=Yes 24 1 No Standard

N=No

6 Incident/Report I=Incident 25 1

Occurred Date R=Report

Category

7 Incident/Report YYYYMMDD 26 8 Situation-Schedule-

Occurred Begin Date Component Date

8 Incident/Report 9999 34 4 Situation-Schedule-

Occurred Begin Time Component Time

9 Incident/Report YYYYMMDD 38 8 Situation-Schedule-

Occurred End Date Component Date

10 Incident/Report 9999 46 4 Situation-Schedule-

Occurred End Time Component Time

11 Incident Clearance U=Unfounded 50 1 Examination-Closure-

Reason X=Arrest or Arrest Reason Code

Equivalent

A=Death of Offender

B=Prosecution Declined

C=Extradition Declined

D=Victim Refused to

Cooperate

E=Juvenile, No Custody

12

Exceptional Clearance

YYYYMMDD 51 8

Examination-Closure

Date Reason Effective Date

13

Number of Victims

999 59 3 Derived

Notified (DD Form

2701)

14 Number of Witnesses 999 62 3 Derived

Notified

Change 3, 09/18/2020 21 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

5. OFFENSE SEGMENT

a. The Offense Segment is used to identify and describe the types of offenses involved in the

incident (e.g., arson, prostitution).

(1) An offense segment is submitted for each of the (up to) 10 most serious (as

determined by the reporting agency) offenses in the incident. Only one offense segment is to be

submitted for each reported offense identifier even though there may have been more than one

victim of the crime. At least one offense segment must be submitted for each incident report.

Example: In the same incident, the offender assaulted two persons by threatening them with a

handgun.

(a) Only one Offense Segment should be submitted with “aggravated assault” entered

as the offense identifier.

(b) Two victim segments should also be submitted that are linked to this Offense

Segment by entering the appropriate offense code into “Victim Connected to Offense

Information.”

(2) The Offense Segment data layout is displayed in Table 2.

b. Data elements used in the Offense Segment are:

(1) Header Elements. While FBI Location Number, Incident Number, Segment Type,

and Report Type are part of the Administrative Segment, they are repeated in all other segments

for the purpose of linking those segments to the Administrative Segment.

(2) Offense Code Information (Offense Statutory Basis + Offense Result + Offense

Identifier).

(3) Offender(s) Suspected of Using Alcohol.

(4) Offender(s) Suspected of Using Drugs.

(5) Offender(s) Suspected of Using Computer Equipment.

(6) Location of Offense.

(7) On Military Service Installation.

(8) U.S. State or Possession.

(9) Offense Location Country Code.

(10) Number of Premises Entered.

Change 3, 09/18/2020 22 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

(11) Method of Entry.

(12) Type of Criminal Activity.

(13) Type Weapon/Force Used.

(14) Gun Category.

(15) Bias Motivation.

c. This segment is prepared by the lead agency. This agency shall retain the update

responsibility for quality control.

Table 2. Offense Segment

FIELD

NUMBER

FIELD NAME DOMAIN

RECORD

SIZE STANDARD NAME

POSITION

1 FBI Location Number 1 9

Derived:

Organization-

Designator Source

Assigned Identifier

2 Incident Number 10 12 Derived:

Organization-

Designator Source

Assigned Identifier;

Situation Identifier

3 Segment Type F 22 1 No Standard

4 Report Type A=ADD 23 1 No Standard

M=MODIFY

D=DELETE

15 Offense Statutory Basis A =UCMJ 24 1 Derived:

B=Non-Criminal Fatality Offense Statutory

(High Interest) Basis Code;

C=State Organization-

D=Local Guidance Reason Code

E=Foreign

F=Federal, Non-UCMJ

16 Offense Identifier See Enclosure 2 to Volume 2 25 6 Offense Identifier

17 Offense Result A=Attempted 31 1 Offense Name

C=Completed

19 Offender Suspected of Y=Yes 32 1 Person-Situation-

Using Alcohol N=No Material-Item

Reason Code

20 Offender Suspected of Y=Yes 33 1 Person-Situation-

Using Drugs N=No

Material-Item

Reason Code

21 Offender Suspected of Y=Yes 34 1 Person-Situation-

Using Computer N=No Material-Item

Equipment Reason Code

Change 3, 09/18/2020 23 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

Table 2. Offense Segment, Continued

FIELD

NUMBER

FIELD NAME DOMAIN

RECORD

SIZE STANDARD NAME

POSITION

22 Location of Offense 01=Air/Bus/Train Terminal 35 2 Derived:

02=Bank/Savings and Loan

Facility Category Code

(includes other financial

institutions, credit union)

03=Bar/Night Club/

Officer Club/NCO Club

04=Church/Synagogue/

Temple (includes other

religious buildings)

05=Commercial/Office

Building

06=Construction Site

07=Convenience Store,

Shoppette

08=Department/Discount

Store, Exchange

09=Drug Store/Doctor’s

Office/Hospital, Clinic

(includes medical supply

companies and buildings)

10=Field/Woods, Training

Area

11=Government/Public

Building

12=Grocery/Supermarket,

Commissary

13=Highway/Road/Alley/

Street/Sidewalk

14=Hotel/Motel/Etc. (includes

other civilian or military

temporary lodging)

15=Jail/Prison/Penitentiary/

Corrections Facility

16=Lake/Waterway/Beach/

Ocean

17=Liquor Store, Class VI

18=Parking Lot/Drop Lot/

Garage/Motor Pool

19=Rental Storage Facility

(includes any mini-

storage or self-storage

buildings)

20=Residence/Home/Quarter/

Barrack/BOQ/BEQ

(includes apartments,

condominiums,

and nursing homes,

residential driveways,

and/or residential yards)

Change 3, 09/18/2020 24 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

Table 2. Offense Segment, Continued

FIELD

NUMBER

FIELD NAME DOMAIN

RECORD

SIZE STANDARD NAME

POSITION

22, Location of Offense 21=Restaurant, Dining Facility 35 2 Derived:

Continued

(includes cafeteria)

Facility Category Code

22=School/College (includes

university)

23=Service/Gas Station

24=Concessionaire/Specialty

Store

25=Other/Unknown

26=Recreation Area/Park

27=Training Center/Service

School

28=On-Board Ship

37=Abandoned/Condemned

Structure

38=Amusement Park

39=Arena/Stadium/

Fairgrounds/Coliseum

40=ATM Machine Separate

from Bank (if located at a

banking facility, use

02=Bank/Savings and

Loan)

41=Auto Dealership

New/Used

42=Camp/Campground

43=Cargo Container

44=Daycare Facility (child or

adult care such as senior

center)

45=Dock/Wharf/Freight/

Modal Terminal

46=Farm Facility

47=Gambling Facility/Casino/

Race Track

48=Industrial Site

49=Military Installation

50=Park/Playground

51=Rest Area

52=School-College/University

(includes community

colleges and trade

schools)

53=School-Elementary/

Secondary

54=Shelter-Mission/Homeless

55=Shopping Mall (includes

strip malls)

56=Tribal Lands

23

On Military Service Y=Yes

37 1

Organization-

Installation N=No Facility-Usage Code

Change 3, 09/18/2020 25 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

Table 2. Offense Segment, Continued

FIELD

NUMBER

FIELD NAME DOMAIN

RECORD

SIZE STANDARD NAME

POSITION

24 U.S. State or Possessions See Table 12 in Volume 2 38 2 State Code

192 Offense Location See Federal Information 40 2 Country Code

Country Code Processing Standard 10-4

(Reference (u))

25 Number of 99 42 2 No Standard

Premises Entered

26 Method of Entry F=Forced 44 1 Offense Name

N=Not forced

“TYPE OF CRIMINAL ACTIVITY,” “TYPE OF WEAPON OR FORCE USED,” AND “GUN CATEGORY”

OCCUR THREE TIMES

27 Type of Criminal B=Buying/Receiving 45, 1 Offense Classification

Activity C=Cultivating/Manufacturing

49,

Code

1 of 3 D=Distributing/Selling

53

E=Exploiting Children

O=Operating/Promoting/

Assisting

T=Transporting/Importing

U=Using/Consuming

P=Possessing/Concealing

G=Gangs

J=Juvenile Gang

N=None/Unknown (no known

gang affiliation)

28 Type Weapon/Force 11=Firearm (type not stated) 46, 2 Person-Situation-

Used 12=Handgun

50,

Material Reason

1 of 3 13=Rifle

54

Code

14=Shotgun

15=Other Fire Arms

20=Knife/Cutting Instrument

30=Blunt Object

35=Motor Vehicle

40=Personal Weapons

50=Poison

60=Explosives

65=Fire/Incendiary

70=Narcotics/Drugs

85=Asphyxiation

90=Other

95=Unknown

99=None

29 Gun Category A=Fully Automatic 48, 1 Gun Category

1 of 3 M=Manual 52, Code

S=Semiautomatic 56

30 Bias Motivation AV=Anti-White 57 2 Legal-Event-Bias-

AH=Anti-Black Motivation Code

AD=Anti-Arab

AM=Anti-Hispanic DMDC shall translate

AC=Anti-American Indian

Standard Codes to FBI

AB=Anti-Alaskan coding specifications

AE=Anti-Asian

Change 3, 09/18/2020 26 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

Table 2. Offense Segment, Continued

FIELD

NUMBER

FIELD NAME DOMAIN

RECORD

SIZE STANDARD NAME

POSITION

30, Bias Motivation AT=Anti-Pacific Islander 57 2 Legal-Event-Bias-

Continued

AR=Anti-Multi-Racial Group Motivation Code

AO=Anti-Jewish

AI=Anti-Catholic DMDC shall translate

AN=Anti-Islamic (Moslem) Standard Codes to FBI

AU=Anti-Protestant coding specifications

AS=Anti-Multi-Religious

Group

AW=Anti-Homosexual

AA= Anti-Agnostic

AQ=Anti-Male Homosexual

AK=Anti-Female Homosexual

AL=Anti-Heterosexual

AG=Anti-Bisexual

AX=Unknown Bias

AY=Anti-Other Religions

AZ=Anti-Other Ethnicity

BA=Anti-Mental Disability

BB=Anti-Physical Disability

NB=None (no bias)

112 Sexual-Harassment Y=Yes 59 1 Derived:

Related N=No

Legal-Event Type

Code; Legal-Event

Offense Reason Code;

Offense Name; Offense

Type Code

6. PROPERTY SEGMENT

a. Property Segments are used to describe the type, value, and quantity of property involved

in the incident. The Property Segment data layout is displayed in Table 3.

b. The Property Segment is to be submitted for each type of property loss (e.g., burned,

stolen).

c. Property Segments are submitted ONLY IF a property loss occurs during the commission

of one or more of these offenses:

(1) Kidnapping/Abduction.

(2) Robbery.

(3) Arson.

(4) Extortion/Blackmail.

Change 3, 09/18/2020 27 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

(5) Burglary/Breaking and Entering.

(6) Pocket-Picking.

(7) Purse-Snatching.

(8) Shoplifting.

(9) Theft from Building.

(10) Theft from Coin-Operated Machine or Device.

(11) Theft from Motor Vehicle.

(12) Theft of Motor Vehicle Parts or Accessories.

(13) All Other Larceny.

(14) Motor Vehicle Theft.

(15) Counterfeiting/Forgery.

(16) False Pretenses/Swindle/Confidence Game.

(17) Credit Card/Automatic Teller Machine Fraud.

(18) Impersonation.

(19) Welfare Fraud.

(20) Wire Fraud.

(21) Embezzlement.

(22) Destruction/Damage/Vandalism of Property.

(23) Drug/Narcotic Violations.

(24) Betting/Wagering.

(25) Operating/Promoting/Assisting Gambling.

(26) Gambling Equipment Violations.

(27) Sports Tampering.

Change 3, 09/18/2020 28 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

(28) Bribery.

d. The data elements used in the Property Segment are:

(1) Header Elements.

(2) Property Loss By.

(3) Property Description.

(4) Date Recovered.

(5) Date Returned.

(6) Quantity.

(7) Value of Property.

(8) Ownership.

(9) Secured/Unsecured.

(10) Drug Code.

(11) Estimated Drug Quantity.

(12) Type Drug Measure.

e. Up to 10 types of property (e.g., Aircraft, Alcohol, Automobiles) can be reported to the

DIBRS for each type of property loss. If there was no property loss, no record need be

submitted.

f. This segment is prepared by the lead agency. This agency shall retain the update

responsibility for quality control.

Change 3, 09/18/2020 29 ENCLOSURE 4

FIELD

NUMBER

FIELD NAME

1 FBI Location Number

2 Incident Number

3 Segment Type

4 Report Type

31 Property Loss By

32 Property Description

1 of 10

33 Date Recovered

1 of 10

34 Date Returned

1 of 10

DoDM 7730.47-M-V1, December 7, 2010

Table 3. Property Segment

DOMAIN

P

A=ADD

M=MODIFY

D=DELETE

1=No Property Loss

2=Burned

3=Counterfeited/Forged

4=Damaged/Destroyed/

Vandalized

5=Recovered

6=Seized

7=Stolen

8=Unknown

See Table 13 in Volume 2

YYYYMMDD

YYYYMMDD

RECORD

SIZE

POSITION

1 9

10 12

22 1

23 1

STANDARD

NAME

Derived:

Organization-

Designator Source

Assigned Identifier

Derived:

Organization-

Designator Source

Assigned Identifier;

Situation Identifier

No Standard

No Standard

24 1 Derived: Situation-

Material Reason

Code; Situation-

Facility Reason

Code

25,

2

63,

101,

139,

177,

215,

253,

291,

329,

367

27, 8 Situation-Material

65, Reason Date

103, (Situation-Material

141,

Reason Code=

179, Recovered)

217,

255,

293,

331,

369

35, 8 Situation-Material

73, Reason Date

111,

(Situation-Material

149, Reason Code=

187, Returned)

225,

263,

301,

339,

377

Change 3, 09/18/2020 30 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

Table 3. Property Segment, Continued

FIELD

NUMBER

FIELD NAME DOMAIN

RECORD

SIZE

POSITION

STANDARD

NAME

35 Quantity 999999999 43, 9 No Standard

1 of 10

81,

119,

157,

195,

233,

271,

309,

347,

385

36 Value of Property 999999999 52, 9 No Standard

1 of 10

90,

128,

166,

204,

242,

280,

318,

356,

394

37 Ownership A=U.S. Federal Government 61, 1 Derived:

1 of 10 B=U.S. State Government

99,

Organization

C=U.S. City Government 137, Category Code;

D=U.S. County Government

175,

Local-Government-

E=Foreign Government 213, Organization Type

F=Private Sector 251, Code

289,

327,

365,

403

38 Secured/Unsecured S=Secured

1 of 10 U=Unsecured

62,

1

100,

138,

176,

214,

252,

290,

328,

366,

404

“DRUG CODE,” “ESTIMATED DRUG QUANTITY,” AND “TYPE DRUG MEASURE” OCCUR FOUR

TIMES

39 Drug Code A=‘Crack’ Cocaine 405, 1 Derived:

1 of 4 B=Cocaine

420,

Drug Code

C=Hashish 435, Drug Classification

D=Heroin 450 Code

E=Marijuana

F=Morphine

G=Opium

H=Other Narcotics

I=LSD

Change 3, 09/18/2020 31 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

Table 3. Property Segment, Continued

FIELD

NUMBER

FIELD NAME DOMAIN

RECORD

SIZE

POSITION

39,

Continued

J=PCP 405, 1

K=Other Hallucinogens 420,

L=Amphetamines/ 435,

Methamphetamines 450

M=Other Stimulants

N=Barbiturates

O=Other Depressants

P=Other Drugs

Q=Steroids

U=Unknown Type Drug

X=Greater Than 4

40 Estimated Drug Quantity 999999999.999 406, 12

1 of 4

421,

436,

451

41 Type Drug Measure GM=Gram 418, 2

1 of 4 KG=Kilogram 433,

OZ=Ounce 448,

LB=Pound 463

ML=Milliliter

LT=Liter

FO=Fluid Ounce

GL=Gallon

DU=Dosage Unit

NP=Number of Plants

XX=Not Reported

7. VICTIM SEGMENT

STANDARD

NAME

Derived:

Drug Code

Drug Classification

Code

Materiel Weight

No Standard

a. Victim Segments are used to describe the victims involved in the incident (e.g., their age,

sex, race). A separate Victim Segment is to be submitted for each of the (up to 999) victims

involved in the incident. There must be at least one Victim Segment in each incident report,

except when a Group B offense is being reported. (See Table 9 in Volume 2.) The Victim

Segment data layout is displayed in Table 4.

b. The data elements used in the Victim Segment are:

(1) Header Elements.

(2) Victim (Sequence) Identifier.

(3) Victim Connected to Offense Code Information (Offense Statutory Basis + Offense

Result + Offense Identifier + Involvement).

(4) Victim Type.

Change 3, 09/18/2020 32 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

(5) Pay plan.

(6) Grade.

(7) Service.

(8) Component.

(9) Age (of Victim).

(10) Sex.

(11) Federal Civil Servant.

(12) Military Service Retiree.

(13) Federal Contractor.

(14) Military Service Family Member.

(15) Race (of Victim).

(16) Ethnicity (of Victim).

(17) Aggravated Assault/Homicide Circumstances.

(18) Additional Justifiable Homicide Circumstances.

(19) Injury Type.

(20) Offender Identifier(s) Related to this Victim.

(21) Relationship(s) of Victim to Offender(s).

c. This segment is prepared by the lead agency. This agency shall retain the update

responsibility for quality control.

Change 3, 09/18/2020 33 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

Table 4. Victim Segment

FIELD

NUMBER

FIELD NAME DOMAIN

RECORD

SIZE

POSITION

STANDARD

NAME

1 FBI Location Number 1 9 Derived:

Organization-

Designator Source

Assigned Identifier

2 Incident Number 10 12 Derived:

Organization-

Designator Source

Assigned Identifier;

Situation Identifier

3 Segment Type V 22 1 No Standard

4 Report Type A=ADD 23 1 No Standard

M=MODIFY

D=DELETE

42 Victim Identifier 999 24 3 Person-Designator

Identifier

“VICTIM CONNECTED TO OFFENSE STATUTORY BASIS,” “OFFENSE IDENTIFIER,” “OFFENSE

RESULT,” AND “INVOLVEMENT” OCCUR 10 TIMES

43, 15 Victim Connected to A=UCMJ 27, 1 Derived: Offense

Offense Statutory

B=Non-Criminal Fatality 36,

Statutory Basis

Basis

(High Interest) 45,

Code;

1 of 10

C=State 54,

Organization-

D=Local

63,

Guidance Reason

E=Foreign 72, Code

F=Federal, Non-UCMJ 81,

90,

99,

108

43, 16 Victim Connected to See Enclosure 2 to Volume 2 28, 6 Offense Identifier

Offense Identifiers

37,

1 of 10

46,

55,

64,

73,

82,

91,

100,

109

43, 17 Victim Connected to A=Attempted 34, 1 Offense Name

Offense Result C=Completed

43,

1 of 10

52,

61,

70,

79,

88,

97,

106,

115

Change 3, 09/18/2020 34 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

Table 4. Victim Segment, Continued

FIELD

NUMBER

FIELD NAME DOMAIN

RECORD

SIZE

POSITION

STANDARD

NAME

43, 18 Victim Connected P=Principal 35, 1 Derived:

to Involvement A=Accessory

44, Person-Situation

1 of 10

C=Conspiracy 53, Role Category

S=Solicit 62, Code;

71, Offense Type Code

80,

89,

98,

107,

116

44 Victim Type I=Individual 117 1 Offense Victim

B=Business Type Code

F=Financial

G=Government

R=Religious Organization

S=Society/Public

45 118 9 Blank Field

46 Pay Plan EM=Enlisted 127 2 Pay-Plan Code

WM=Warrant Officer

OM=Commissioned Officer

CM=Cadet/Midshipman

GS/GM=General Schedule

ES=Senior Executive Service

WG=Wage Grade/Other

YA=Standard Professional/

Analytical

YB=Standard Technical/

Support

YC=Standard Supervisor/

Manager

YP=Standard Student

YD=Scientific and

Engineering –

Professional

YE=Scientific and

Engineering

Technical

/

Support

YF=Scientific and

Engineering

Supervisor/Manager

YG=Medical Physician/

Dentist

YH=Medical Professional

YI=Medical Technical/

Support

YJ=Medical Supervisor/

Manager

YK=Investigative and

Protective Service –

Investigative

Change 3, 09/18/2020 35 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

Table 4. Victim Segment, Continued

FIELD

NUMBER

FIELD NAME DOMAIN

RECORD

SIZE STANDARD NAME

POSITION

46, Pay Plan YL=Investigative and 127 2 Pay-Plan Code

Continued

Protective Service –

Fire Protection

YM=Investigative and

Protective Service –

Police/Security Guard

YN=Invest and Protective

Service – Supervisor/

Manager

47 Grade 01=Grade 1 129 2 Pay-Plan-Grade

through Ordinal Identifier

15=Grade 15

48 Service A=Army 131 1 Uniformed-Service

N=Navy Organization Code

F=Air Force

M=Marine Corps

C=Coast Guard

O=NOAA

H=Public Health

D=DoD

49 Component

R=Regular

132 1

Uniformed-Service-

V=Reserve Organization-

G=National Guard Component-Type

Code

50 A Age (*Low Range) NN=Under 24 Hours 133 2 Person-Situation

NB=1-6 Days Old Observation Age

BB=7-364 Days Old Code

01-98=Years Old

99=Over 98 Years Old

00=Unknown

50 B Age (High Range 01-98=Years Old 135 2

Only) 99=Over 98 Years Old

51 Sex M=Male 137 1 Sex-Category Code

F=Female

I=Indeterminate

U=Unknown

52 Federal Civil Servant C=Civil Service 138 1 Personnel Resource

Type Code

53

Military Service

G=Military Service Retiree 139 1

Separation

Retiree Category Code

54 Federal Contractor J=Contractor 140 1 Person Organization

Person Role Code

55 Military Services F=Family Member 141 1 Person-Association

Family Member Reason Code

56 Race (Victim) A=American Indian 142 1 Race Code

B=Asian/Pacific Islander

C=Black

D=White

M=Mixed

U=Unknown

Change 3, 09/18/2020 36 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

Table 4. Victim Segment, Continued

FIELD

NUMBER

FIELD NAME DOMAIN

RECORD

SIZE STANDARD NAME

POSITION

57 Ethnicity (Victim) H=Hispanic 143 1 Ethnicity Code

N=Not Hispanic

U=Unknown

“AGGRAVATED ASSAULT/HOMICIDE CIRCUMSTANCES” OCCURS TWO TIMES

58 Aggravated Assault/ 01=Argument 144, 2 Legal-Event

Homicide 02=Assault on Law 147 Context Code

Circumstances

Enforcement Officer

1 of 2 03=Drug Dealing

04=Gangland

05=Juvenile Gang

06=Domestic Quarrel

07=Mercy Killing

08=Other Felony Involved

09=Other

10=Unknown

20=Criminal Killed by

Private Citizen

21=Criminal Killed by Police

Officer

30=Child Playing with

Weapon

31=Gun-Cleaning Accident

32=Hunting Accident

33=Other Negligent

Weapon Handling

34=Other Negligent Killings

“ADDITIONAL JUSTIFIABLE/HOMICIDE CIRCUMSTANCES” OCCURS TWO TIMES

59

Additional Justifiable A=Criminal Attacked

146, 1

Derived: Legal-

Homicide Police Officer and that

149

Event Context

Circumstances Officer Killed Criminal Code; Legal-Event-

1 of 2 B=Criminal Attacked

Context Description

Police Officer and

Text

Criminal Killed by

Another Police Officer

C=Criminal Attacked a

Civilian

D=Criminal Attempted

Flight from a Crime

E=Criminal Killed in

Commission of a crime

F=Criminal Resisted Arrest

G=Unable to Determine

“INJURY TYPE” OCCURS FIVE TIMES

60 Injury Type B=Apparent Broken Bones 150, 1 Derived:

1 of 5 I=Possible Internal Injury

151,

Eyewitness-

L=Severe Laceration 152, Observation

M=Apparent Minor Injury 153, Description Text;

O=Other Major Injury 154 Eyewitness-

T=Loss of Teeth Observation Type

U=Unconsciousness Code; Person-

Change 3, 09/18/2020 37 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

Table 4. Victim Segment, Continued

FIELD

NUMBER

FIELD NAME DOMAIN

RECORD

SIZE STANDARD NAME

POSITION

Situation Role Code

“OFFENDER IDENTIFIER” AND “RELATIONSHIP OF VICTIM TO OFFENDER” OCCUR 10 TIMES

61 Offender Identifiers 99 155, 2 Person-Designator

Related to this Victim

159,

Identifier

1 of 10 163,

167,

171,

175,

179,

183,

187,

191

62 Relationship of Victim AA=Spouse 157, 2 Person-Association

to AB=Child 161, Reason Code;

Offender AC=Sibling

165,

Person-Situation-

1 of 10 AD=Parent

169,

Role Code

AE=Parent-in-Law

173,

AF=Stepchild

177,

AG=Grandparent 181,

AH=Stepparent 185,

AK=Grandchild

189,

AV=Stepsibling

193

AZ=Friend

BA=Neighbor

BB=Common-Law Spouse

BC=Acquaintance

BD=Baby-Sitter (the baby)

BE=Love Interest

BF=Child of Love Interest

BH=Former Spouse

BL=Homosexual

Relationship

BN=Extended Family

Member

BY=Employee

BZ=Employer

BX=Stranger

CA=Otherwise Known

CB=Relationship Unknown

VO=Offender

8. OFFENDER/ARRESTEE SEGMENT

a. The Offender/Arrestee Segment is used to describe the offenders in the incident (e.g., their

age, sex, race). An Offender/Arrestee Segment is to be submitted for each of the (up to 99)

offenders involved in the incident. There must be at least one offender in each incident report.

For non-criminal fatalities, supply information on the victim. There are several categories in the

Offender/Arrestee Segment. The Offender, Subject, and Suspect categories require a subset of

Change 3, 09/18/2020 38 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

the segment. The Arrestee category uses all the data elements. If NOTHING is known about the

offender(s) (i.e., no one saw the offender(s) and there were no suspects, so even the number of

offenders is unknown), then “00” is to be entered into Offender Identifier and all other elements

are to be left blank. PII shall be submitted only upon a probable-cause determination that there

are reasonable grounds to believe an offense has been committed and that the person to be

identified as the offender committed it. Subparagraphs 2.c.(1) through 2.c.(7) of this enclosure

list the developments involving the offender that shall be construed as the equivalent of a

probable cause determination, and that shall trigger the requirement to report PII as

Arrestee/Offender data. The Offender/Arrestee Segment data layout is displayed in Table 5.

(1) Category – Offender/Subject/Suspect. This category uses only some of the data

elements in the Offender/Arrestee Segment. They are:

(a) Header Elements.

(b) Category (Suspect, Subject, Offender).

(c) Offender/Arrestee (Sequence) Identifier. (This number remains with the offender

if he or she is arrested and continues THROUGHOUT administrative, non-judicial, or judicial

punishment reporting.)

(d) Name (Last, First, Middle Name, Alias (First, Last)).

(e) Grade.

(f) Service.

(g) Component.

(h) Social Security Number (SSN)/Alien Registration (Designator Type Code, SSN

or Alien Registration).

(i) Date of Birth.

(j) Place of Birth.

(k) Age/Age Range (of Offender/Arrestee).

(l) Drivers License Source and Number.

(m) Personnel Status (Federal Civil Servant, Military Service Retiree, Federal

Contractor, Military Service Family Member).

(n) Unit Identification Code (UIC).

(o) Race (of Offender/Arrestee).

Change 3, 09/18/2020 39 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

(p) Ethnicity (of Offender/Arrestee).

(q) Sex (of Offender/Arrestee).

(r) Identifying Marks (Type, Location, Description).

(s) Height.

(t) Weight.

(2) Category – Arrestee Segment. This category is used to report the apprehension of the

persons who committed the crimes reported. Even though Military Service personnel would not

use the term “arrestee” to refer to someone apprehended, the name of this segment was left

“Arrestee” in keeping with NIBRS terminology. An Arrestee Segment is to be submitted for

each of the (up to 99) arrestees who were involved in the incident. If there were no arrestees,

this segment should NOT be submitted. The Arrestee Segment describes the arrestee (e.g., his or

her age, sex, race) and the circumstances of the arrest. Many of the data elements used to

describe the suspect or offender are repeated for the arrestee. They are grouped in subparagraphs

8.a.(2)(a) through 8.a.(2)(o) as Suspect Offender Elements. It is essential that complete

information be provided in the Arrestee Segment (AA/AE) because the information in the

Arrestee Segment shall be used to update any existing Offender Segment (AC) for the same

Offender/Arrestee Identifier. The data elements used in the Arrestee Segment are:

(a) Header Elements.

(b) Category (Arrestee).

(c) Offender/Arrestee (Sequence). Identifier. (A new Offender Identifier may be

added if an additional arrestee is found, but it is essential that the ORIGINAL Offender Identifier

be used to associate the offender and the arrestee records.)

(d) Suspect Offender Elements. (Any field may be updated except the OFFENDER

IDENTIFIER).

(e) Armed With.

(f) Gun Category.

(g) Arrest or Citation Number.

(h) Arrest or Apprehension Date.

(i) Arrest Type.

(j) Arresting Organization UIC.

Change 3, 09/18/2020 40 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

(k) Multiple Incidents Cleared.

(l) Arrest Offense Code Information (Offense Statutory Basis + Offense Result +

Offense Identifier + Involvement).

(m) Detention Type.

(n) Disposition of Person Under 18.

b. If a Group B arrest results in the clearance of a previously submitted Group A incident

report, the reporting agency should submit an Arrestee Segment as an update to the previously

submitted Group A Incident Report rather than a Group B Arrest Report. The Group B Offense

Identifier is to be entered into the Arrest Offense Identifier of the Arrestee Segment. Example:

The subject was arrested for Driving Under the Influence (DUI), a Group B Offense. It was

determined that he was wanted for a previously reported robbery, a Group A Offense. Instead of

submitting a Group B Arrest Report, an Arrestee Segment should be submitted as an update to

the Group A Incident Report, with the Offense Identifier for DUI entered as the Arrest Offense

Identifier.

c. This segment is prepared by the lead agency. Care should be taken to ensure that the

correct offense identifier is used for the Arrest Segment to ensure data integrity.

Table 5. Offender/Arrestee Segment

FIELD

NUMBER

FIELD NAME DOMAIN

RECORD

SIZE STANDARD NAME

POSITION

1 FBI Location Number 1 9 Derived:

Organization-

Designator Source

Assigned Identifier

2 Incident Number 10 12 Derived:

Organization-

Designator Source

Assigned Identifier;

Situation Identifier

63 Category AC=Suspect/Offender 22 2 Person-Situation

AA=Arrestee Role Code

AJ=Subject/Suicide

AB=Business or Enterprise

AE=Arrest Equivalent

64 Offender Identifier 99 24 2 Person-Designator

Identifier

4 Report Type A=ADD 26 1 No Standard

M=MODIFY

D=DELETE

65 Name Last 27 21

Name (Person-Name

Category=s)

66 Name First 48 14 Name (Person-Name

Category=f)

Change 3, 09/18/2020 41 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

Table 5. Offender/Arrestee Segment, Continued

FIELD FIELD NAME DOMAIN RECORD SIZE STANDARD NAME

NUMBER POSITION

67 Name Middle Name 62 14 Name (Person-Name

Category=m)

68 Name Cadency (Jr., Sr., III) 76 4 Name (Person-Name

Category=c)

69 Name Alias (Last) 80 21 Name (Person-Name

Usage Code=a)

69 Name Alias (First) 101 14 Name (Person-Name

Usage Code=a)

46 Pay Plan EM=Enlisted 115 2 Pay-Plan Code

WM=Warrant Officer

OM=Commissioned Officer

CM=Cadet/Midshipman

GS/GM=General Schedule

ES=Senior Executive Service

WG=Wage Grade/Other

YA=Standard Professional/

Analytical

YB=Standard Technical/

Support

YC=Standard Supervisor/

Manager

YP=Standard Student

YD=Scientific and

Engineering –

Professional

YE=Scientific and

Engineering Technical/

Support

YF=Scientific and

Engineering Supervisor/

Manager

YG=Medical Physician/Dentist

YH=Medical Professional

YI=Medical Technical/Support

YJ=Medical Supervisor/

Manager

YK=Investigative and

Protective Service –

Investigative

YL=Investigative and

Protective Service –

Fire Protection

YM=Investigative and

Protective Service –

Police/Security Guard

YN=Investigative and

Protective Service –

Supervisor/Manager

47 Grade 01=Grade 1 through 117 2 Pay-Plan-Grade

15=Grade 15

Ordinal Identifier

Change 3, 09/18/2020 42 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

Table 5. Offender/Arrestee Segment, Continued

FIELD FIELD NAME DOMAIN RECORD SIZE

NUMBER POSITION

48 Service A=Army 119 1

N=Navy

F=Air Force

M=Marine Corps

C=Coast Guard

O=NOAA

H=Public Health

D=DoD

49 Component R=Regular 120 1

V=Reserve

G=National Guard

70 SSN/Alien Registration S=SSN 1

Designator

R=Alien Registration

I=Foreign Country

Identification Card Number

N=Non-Existent/Unknown

71 SSN/Alien Registration 999999999 122 9

72 Date of Birth YYYYMMDD 131 8

73 City of Birth TEXT 139 20

74 State of Birth See Table 12 in Volume 2 159 2

75 Country of Birth See Reference (s) 161 3

76 Age (*Low Range)

01-98=Years Old

164 2

99=Over 98 Years Old

00=Unknown

76 Age (High Range Only) 01-98=Years Old 166 2

99=Over 98 Years Old

45

77 Drivers License Number TEXT

168 9

177 15

78 Drivers License Source IT=International 192 2

FR=Foreign

See Table 12 in Volume 2

52 Federal Civil Servant C=Civil Service 194 1

53 Military Service Retiree G=Military Service Retiree 195 1

54 Federal Contractor J=Contractor 196 1

55 Military Service Family F=Family Member

Member

79 Offender’s UIC TEXT

197 1

198 8

STANDARD NAME

Uniformed-Service

Organization Code

Uniformed-Service-

Organization-

Component-Type

Code

Person-Designator

Type Code

Person-Designator

Identifier (Person-

Designator Type

Code=s/r)

Person Birth Date

City Code

State Code

Country Code

Eyewitness-

Observation

Description Text

Eyewitness-

Observation

Description Text

Blank Field

Person-Designator

Identifier (Person-

Designator Type

Code=D)

State Code

Personnel-Resource

Type Code

Separation Category

Code

Person Organization

Person Role Code

Person-Association

Reason Code

Organization-

Designator Source

Assigned Identifier

Change 3, 09/18/2020 43 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

Table 5. Offender/Arrestee Segment, Continued

FIELD FIELD NAME DOMAIN RECORD SIZE

NUMBER POSITION

56 Race (Offender) A=American Indian 206 1

B=Asian/Pacific Islander

C=Black

D=White

M=Mixed

U=Unknown

57 Ethnicity (Offender) H=Hispanic 207 1

N=Not Hispanic

U=Unknown

51 Sex M=Male 208 1

F=Female

I=Indeterminate

U=Unknown

80 Identifying Mark Type A=Tattoo 209 1

B=Scar

C=Mark

81 Identifying Mark AAA=Left Eye 210 3

Location AAB=Right Eye

AAC=Face

AAD=Scalp

AAE=Teeth Set

AAF=Left Hand

AAG=Right Hand

AAH=Left Foot

AAI=Right Foot

AAJ=Left Upper Leg

AAK=Right Upper Leg

AAL=Left Upper Arm

AAM=Right Upper Arm

AAN=Right Shoulder

AAO=Left Shoulder

AAP=Right Hip

AAQ=Left Hip

AAR=Abdomen

AAS=Chest

AAT=Back

AAU=Neck

AAV=Buttocks

AAW=Right Lower Leg

AAX=Left Lower Leg

AAY=Right Lower Arm

AAZ=Left Lower Arm

ABA=Right Wrist

ABB=Left Wrist

ABC=Right Ankle

ABD=Left Ankle

82 Identifying Mark TEXT 213 30

Description

83 Height 99 243 2

STANDARD NAME

Race Code

Ethnicity Code

Sex-Category Code

Body-Part-Marking-

Observation Type

Code

Body-Part

Observation Type

Code

Body-Part-Marking-

Observation Text

Eyewitness-

Observation

Description Text

Change 3, 09/18/2020 44 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

Table 5. Offender/Arrestee Segment, Continued

FIELD FIELD NAME DOMAIN RECORD SIZE

NUMBER POSITION

84 Weight 999 245 3

“ARMED WITH” AND “GUN CATEGORY” OCCUR TWO TIMES

85 Armed With 01=Unarmed 248, 2

1 of 2 11=Firearm (type not stated) 251

12=Handgun

13=Rifle

14=Shotgun

15=Other Firearm

16=Lethal Cutting Instrument

17=Club/Blackjack/Brass

Knuckles

86

Gun Category A=Fully Automatic

250, 1

1 of 2 M=Manual

253

S=Semiautomatic

87 Arrest/Citation Number 254 12

88 Arrest/Apprehension YYYYMMDD 266 8

Date

89 Arrest Type O=On-View Arrest 274 1

S=Summons

T=Taken into Custody

90 Arresting Organization

UIC

275 8

91 Multiple Incidents C=First Record of Multiple 283 1

Cleared M=Multiple

N=Not Applicable

92, 15 Arrest Offense Statutory A=UCMJ 284 1

Basis

B=Non-Criminal Fatality

(High Interest)

C=State

D=Local

E=Foreign

F=Federal, Non-UCMJ

92, 16 Arrest Offense Identifier See Enclosure 2 to Volume 2 285 6

92, 17 Arrest Offense Result

A=Attempted

291 1

C=Completed

92, 18 Arrest Involvement P=Principal 292 1

A=Accessory

C=Conspiracy

S=Solicit

93 Detention Type N=Non-Military Service 293 1

U=Military Service

94 Disposition of Person H=Handled within Department 294 1

Under 18 R=Referred to Other

STANDARD NAME

Eyewitness-

Observation

Description Text

Derived:

Durable-Materiel-

Item Type Code;

Gun Type Code;

Law-Enforcement-

Event Type Code;

Person-Situation-

Material-Reason

Code; Person-

Situation Role Code

Gun Category Code

Situation Identifier

Situation-Schedule-

Component Date

Derived:

Apprehension-Event

Basis Code;

Situation-Document

Reason Code

Organization-

Designator Source

Assigned Identifier

No Standard

Derived:

Offense Statutory

Basis Code;

Organization-

Guidance Reason

Code

Offense Identifier

(Offender Offense

Reason=Arrested)

Offense Name

Organization

Classification Code

Derived:

Evaluation-Result

Change 3, 09/18/2020 45 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

FIELD

NUMBER

Table 5. Offender/Arrestee Segment, Continued

FIELD NAME DOMAIN

Authorities

RECORD

POSITION

SIZE

9. COMMANDER’S REPORT OF ACTION TAKEN SEGMENT

STANDARD NAME

Text; Person Birth

Date

a. The Commander’s Action Segment records the actions of the commander as a result of the

incident. A separate segment is submitted for each person referred to the commander for action.

Cases initiated by the commander that have not triggered previous DIBRS reporting

requirements, such as positive drug tests, may be submitted as one incident. The DoD

Components shall develop procedures for submitting appropriate Administrative, Offense, and

Arrestee Segments to complete the incident report. The Commander’s Report of Action Taken

Segment data layout is displayed in Table 6.

b. Data elements used in the Commander’s Action Segment are:

(1) Header Elements.

(2) Offender (Sequence) Identifier.

(3) Offender Name (Last, First, Middle Name).

(4) SSN/Alien Registration.

(5) Referral Date.

(6) Referral Agency.

(7) Referral Agency Response Date.

(8) Action Taken Type.

(9) Non-Judicial Type.

(10) Action Initiation Date.

(11) Action Appealed Date.

(12) Action Completed Date.

(13) Sanction Type.

(14) On Record.

(15) Sanction Form.

Change 3, 09/18/2020 46 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

(16) Sanction Amount.

(17) Sanction Days.

(18) Grades Reduced.

(19) Sentence Suspended.

(20) Discharge Type.

(21) Offense Committed Information (Offense Statutory Basis + Offense Identifier +

Offense Result + Involvement).

(22) Sexual-Harassment Related.

(23) Judicial Action Type.

(24) Civilian Criminal Court Disposition.

(25) Civilian Criminal Offense Category.

(26) Civilian Court Location Zip Code.

(27) Civilian Court Location Country Code.

c. This segment shall be prepared as specified by the functional responsible official. The

notification sent to the commander shall include instructions on how to report the results.

Change 3, 09/18/2020 47 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

Table 6. Commander’s Report of Action Taken Segment

FIELD

NUMBER

FIELD NAME DOMAIN

RECORD

POSITION

SIZE STANDARD NAME

1 FBI Location Number 1 9 Derived:

Organization-

Designator Source

Assigned Identifier

2 Incident Number 10 12 Derived:

Organization-

Designator Source

Assigned Identifier;

Situation Identifier

3 Segment Type D 22 1 No Standard

4 Report Type A=ADD 23 1 No Standard

M=MODIFY

D=DELETE

64 Offender Identifier 99 24 2 Person Designator

Identifier

65 Name Last 26 21 Name (Person-Name

Category=s)

66 Name First 47 14 Name (Person-Name

Category=f)

67 Name Middle Name 61 14

Name (Person-Name

Category=m)

71 SSN/Alien 999999999 75 9 Person-Designator

Registration Identifier (Person-

Designator Type

Code=s)

“REFERRAL DATE,” “REFERRAL AGENCY,” AND “REFERRAL AGENCY RESPONSE DATE”

OCCUR SEVEN TIMES

95 Referral Date YYYYMMDD 84, 8 Evaluation-Result

1 of 7

101,

Date

118,

135,

152,

169,

186

96 Referral Agency F=Family Advocacy 92, 1 Organization-Name

1 of 7 E=Equal Opportunity

109,

Text

M=Mental Health

126,

D=Drug/Alcohol Abuse

143,

Office

160,

L=Legal Office

177,

R=Relief Agency

194

S=Special Referral

97 Referral Agency YYYYMMDD 93, 8 Administrative-Event

Response Date

110, Date

1 of 7

127,

144,

161,

178,

195

Change 3, 09/18/2020 48 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

Table 6. Commander’s Report of Action Taken Segment, Continued

FIELD

NUMBER

FIELD NAME DOMAIN

RECORD

SIZE

POSITION

STANDARD NAME

98 Action Taken Type A=No Action Taken 203 1 Proceeding Type Code

B=Administrative

C=Non-Judicial

D=Judicial

99 Non-Judicial Type F=Field Grade (O4 and 204 1 Evaluation-Result

Above) Text

C=Company Grade,

(O3 and Below)

S=Summarized

P=Principal Assistant

O=Officer Exercising

General

Court-Martial

Jurisdiction

G=Flag Officer

“SANCTION TYPE,” “ON RECORD,” “SANCTION FORM,” “SANCTION AMOUNT,” “SANCTION DAYS,”

“SUSPENDED,” AND “GRADES REDUCED” OCCUR 10 TIMES

100 Sanction Type AA=Withholding of 205, 2 Derived:

1 of 10 Privileges 249, Administrative-Event

AB=Adverse Performance

293, Category Code;

Evaluation

337,

Administrative-Event

AC=Mandatory

381,

Subject Code;

Reassignment

425,

Administrative-

AD=Transfer

469,

Event Type Code;

AE=Adverse Record Entries

513,

Administrative-

AF=Denial of Reenlistment

557, Event-Evaluation

or Continuation

601

Reason Code;

AG=Withholding of Administrative-

Promotion Sentence Type

AH=Delay of Promotion Code

AI=Reduction in Grade

AJ=Clearance Revocation

AK=Control Roster

AL=Promotion Revocation

AM=Resignation

AN=Retirement

AO=Transfer to Inactive

Reserve Status

AP=Administrative

Separation

AQ=Retirement at Lower

Grade

AR=Military Occupational

Specialty

Reclassification

AS=Counseling

AT=Non-Punitive

Admonition,

(Reprimand, Censure)

AU=Fines

AV=Extra Duty

Change 3, 09/18/2020 49 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

Table 6. Commander’s Report of Action Taken Segment, Continued

FIELD

NUMBER

FIELD NAME DOMAIN

RECORD

SIZE

POSITION

STANDARD NAME

AW=Restricted

AX=Correctional Custody

AY=Administrative

Separation in Lieu of

Trial

101 Action Initiation Date YYYYMMDD 207, 8 Examination-

1 of 10

251,

Schedule-Component

295,

Date

339,

383,

427,

471,

515,

559,

603

102 Action Appealed YYYYMMDD 215, 8 Examination-

Date 1 of 10 259, Schedule-Component

303, Date

347,

391,

435,

479,

523,

567,

611

103 Action Completion YYYYMMDD 223, 8 Examination-

Date 1 of 10

267,

Schedule-Component

311,

Date

355,

399,

443,

487,

531,

575,

619

104 On Record

1 of 10

Y=Yes

N=No

231, 1

275,

319,

363,

407,

451,

495,

539,

583,

627

105 Sanction Form O=Oral

1 of 10 W=Written

232, 1

276,

320,

364,

408,

452,

Change 3, 09/18/2020 50 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

Table 6. Commander’s Report of Action Taken Segment, Continued

FIELD

NUMBER

FIELD NAME DOMAIN

RECORD

SIZE

POSITION

STANDARD NAME

496,

540,

584,

628

106 Sanction Amount 999999999 233, 9 Monetary-

1 of 10 277, Remuneration-

321,

Sentence Amount

365,

409,

453,

497,

541,

585,

629

107 Sanction Days 99999 242, 5 Derived:

1 of 10

286,

Fixed-

330,

Term-Confinement-

374,

Sentence Duration

418,

Quantity; Community-

462,

Service-Sentence Duration

506,

Quantity

550,

594,

638

108 Grades Reduced 9 247, 1 Derived:

1 of 10 291, Evaluation-Result

335,

Text; Pay-Plan-

379,

Grade Ordinal

423,

Identifier; Sentence

467,

Type Code

511,

555,

599,

643

109 Sanction Suspended Y=Yes 248, 1 Confinement-

1 of 10 N=No

292,

Sanction Condition

V=Vacation of Suspended 336, Code

Sanction 380,

424,

468,

512,

556,

600,

644

110 Discharge Type HO=Honorable 645 2 Separation-

UH=Under Honorable Characterization

Conditions (General Code

Discharge)

UN=Uncharacterized

UO=Under Other than

Honorable Conditions

Change 3, 09/18/2020 51 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

Table 6. Commander’s Report of Action Taken Segment, Continued

FIELD

NUMBER

FIELD NAME DOMAIN

RECORD

SIZE

POSITION

STANDARD NAME

111, 15 Offense Statutory A=UCMJ 647 1 Derived:

Basis

B=Non-Criminal Fatality Offense Statutory Basis

(High Interest) Code; Organization-

C=State Guidance Reason

D=Local Code

E=Foreign

F=Federal, Non-UCMJ

111, 16 Offense Committed See Enclosure 2 to Volume 2 648 6 Offense Identifier

Code

111, 17 Offense Result A=Attempted 654 1 Offense Name

C=Completed

111, 18 Involvement P=Principal 655 1 Derived:

A=Accessory Person-Situation Role

C=Conspiracy Category Code; Offense

S=Solicit

Type

Code

112 Sexual-Harassment Y=Yes 656 1 Derived:

Related N=No

Legal-Event Type Code;

Legal-Event

Offense Reason

Code; Offense

Name; Offense

Type Code

113 Judicial Action Type A=Referred to Court- 657 1

Martial

B=Remanded to Civilian

Criminal Court

114 Civilian Criminal G=Guilty 658 1 Derived:

Court Disposition N=Not Guilty Examination-

D=Deferred Evaluation Reason

C=Nolo Contendere Code; Verdict Code

115 Civilian Criminal F=Felony 659 1 Offense Category

Offense Category M=Misdemeanor Code

116 Civilian Court 999999999 660 9 Postal-Region

Location Zip Code Code

117 Civilian Court See Reference (s) 669 2 Country Code

Location Country

Code

10. RESULTS OF TRIAL SEGMENT

a. The Results of Trial Segment records the actions of the court-martial as a result of the

incident. Several segments are submitted for each arrestee sent to trial. A separate segment is

sent by each Finding and Sentence Report/Review Authority level. A separate segment shall be

sent by the same Finding and Sentence Report/Review Authority level if the incident is handled

by the same authority on more than one occasion (e.g., the clemency and parole authority may

submit multiple reports). The Findings and Sentence Report/Review Date is used to distinguish

between the reports. The Results of Trial Segment data layout is displayed in Table 7.

Change 3, 09/18/2020 52 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

b. Data elements used in the Results of Trial Segment are:

(1) Header Elements.

(2) Offender (Sequence) Identifier.

(3) Findings and Sentence Report/Review Authority Code.

(4) Findings and Sentence Report/Review Date.

(5) Offender Name (Last, First, Middle Name).

(6) SSN/Alien Registration.

(7) Court Type.

(8) Location of Court-Martial UIC.

(9) Promulgating Order Number.

(10) Promulgating Order Date.

(11) Convening Authority UIC.

(12) Forum.

(13) Conditions of Pretrial Agreement.

(14) Exceptional Trial Clearance.

(15) Charge Number.

(16) Charge Offense Information.

(17) Offense Description.

(18) Specification Number.

(19) Plea.

(20) Lesser Included Offense Code (Plea).

(21) Findings.

(22) Lesser Included Offense Code (Finding).

Change 3, 09/18/2020 53 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

(23) Date Adjudged.

(24) Sentence Suspended.

(25) Sentence Amount.

(26) Sentence Days.

(27) Grades Reduced.

(28) Sentence Type.

(29) Discharge Type.

(30) Pretrial Confinement Days.

(31) Judiciary Ordered Credit Days.

(32) Confinement Deferred Date (Begin and End).

(33) Number of Pretrial Victims Notified.

(34) Number of Pretrial Witnesses Notified.

(35) Number of Post-Trial Victims Notified.

(36) Number of Post-Trial Witnesses Notified.

(37) Number of Victims Electing to be Notified.

(38) Number of Witnesses Electing to be Notified.

c. The Results of Trial Segment is prepared by each agency serving in the Findings and

Sentence Report/Review Authority life cycle. The DoD Component with court-martial

convening authority shall report all Results of Trial Segments. The Results of Trial Segment

should be submitted in all cases in which charges are referred to court-martial, regardless of

disposition. The only exception is in those cases in which an administrative separation in lieu of

trial is granted. In such cases, enter the information in the Commander’s Action Segment under

Sanction Type. If there is a pretrial agreement, two segments should be submitted. (Findings

and Sentence Report/Review Authority Code = “Pretrial Agreement” and “Court-Martial Report

Authority.”) Each appropriate Findings and Sentence Report/Review Authority level shall

ensure that the Incident Number, FBI Location Number, and the original offender number are

obtained from the lead agency, or previous Findings and Sentence Report/Review Authority

level, to ensure accurate tracking with each incident. The Findings and Sentence Report/Review

Authority agency shall assume final quality control responsibility for the incident.

Change 3, 09/18/2020 54 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

Table 7. Results of Trial Segment

FIELD

FIELD NAME DOMAIN

RECORD

SIZE STANDARD NAME

NUMBER POSITION

1 FBI Location Number 1 9 Derived:

Organization-

Designator Source

Assigned Identifier

2 Incident Number 10 12 Derived:

Organization-

Designator Source

Assigned Identifier;

Situation Identifier

3 Segment Type T 22 1 No Standard

4 Report Type A=ADD 23 1 No Standard

M=MODIFY

D=DELETE

64 Offender Identifier 99 24 2 No Standard

118 Findings and Sentence A=Service Secretary 26 1 Derived:

Report Review B=Court-Martial Report Administrative-

Authority Code

Authority

Proceeding Type

C=Convening Authority Code; Judicial-

D=Clemency and Parole Organization

E=Judge Advocate General

Jurisdictional

F=Service Court of Criminal

Level Code;

Appeal

Judicial-

G=Court of Appeals for the

Organization-

Military Services Authority Case

H=Supreme Court

Category Code;

I=Civil Court

Trial Type Code

J=Law Enforcement

119 Findings and Sentence YYYYMMDD 27 8 Document Date

Report/Review Date

65 Name Last 35 21 Name (Person-Name

Category=s)

66 Name First 56 14 Name (Person-Name

Category=f)

67 Name Middle Name 70 14

Name (Person-Name

Category=m)

71 SSN/Alien Registration 999999999 84 9 Person-Designator

Identifier (Person-

Designator Type

Code=s)

120 Court Type Code SCM=Summary Court-Martial 93 4 Court-Martial Type

SPCM=Bad Conduct Code

Discharge Special

Court-Martial

GCM=General Court-Martial

121 Location of Court-Martial TEXT 97 8 Organization-

UIC Designator Source

Assigned Identifier

122 Promulgating Order 105 10 Examination

Number Identifier

Change 3, 09/18/2020 55 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

Table 7. Results of Trial Segment, Continued

FIELD FIELD NAME DOMAIN RECORD SIZE STANDARD NAME

NUMBER POSITION

123 Promulgating Order Date YYYYMMDD 115 8 Examination

Schedule Component

Date

124 Convening Authority UIC TEXT 123 8 Organization-

Designator Source

Assigned Identifier

125 Forum J=Judge Alone 131 1 Court-Martial Forum

O=Officer Members Only

Type Code

E=Enlisted and Officer

Member

126 Conditions of Pretrial M=Military Judge Only 132, 1 Derived:

Agreement N=Non-Capital 133, Court-Martial Forum

1 of 9 R=Restitution 134, Type Code; Pretrial-

L=Referral to Lower Court

135, Agreement Type

T=Testimony

136, Code; Sentence-

C=Confinement Limitation

137, Pretrial-Agreement

F=Forfeiture Limitation

138, Type Code; Judicial-

G=Reduction in Grade

139,

Proceeding Type

Limitation

140 Code; Examination-

A=Allotment to Family

Agreement Reason

V=Allotment to Victim

Code

D=Deferment of Confinement

S=Special Terms

127 Exceptional Trial A=Charges Withdrawn 141 1

Clearance C=Victim/Witness Refused to

Cooperate

D=Other Legal Ban

B=Unfound

“CHARGE NUMBER,” “OFFENSE STATUTORY BASIS,” “OFFENSE IDENTIFIER,” “OFFENSE RESULT,”

“INVOLVEMENT OFFENSE DESCRIPTION SPECIFICATION NUMBER,” “PLEA,” “LESSER INCLUDED

OFFENSE CODE (PLEA),” “FINDINGS,” AND “LESSER INCLUDED OFFENSE (FINDINGS)” OCCUR 20

TIMES

128 Charge Number 99 142, 2 Offense Identifier

1 of 20 195,

248,

301,

354,

407,

460,

513,

566,

619,

672,

725,

778,

831,

884,

937,

990,

1043,

Change 3, 09/18/2020 56 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

Table 7. Results of Trial Segment, Continued

FIELD FIELD NAME DOMAIN RECORD SIZE STANDARD NAME

NUMBER POSITION

1096,

1149

129, 15 Offense Statutory Basis A=UCMJ 144, 1 Derived:

1 of 20 B=Non-Criminal Fatality 197, Offense Statutory

(High Interest) 250, Basis Code;

C=State 303, Organization-

D=Local 356, Guidance Reason

E=Foreign 409, Code

F=Federal, Non-UCMJ

462,

515,

568,

621,

674,

727,

780,

833,

886,

939,

992,

1045,

1098,

1151

129, 16 Charge Offense Identifier See Enclosure 2 to Volume 2 145, 6 Charge Offense

1 of 20 198, Identifier

251,

304,

357,

410,

463,

516,

569,

622,

675,

728,

781,

834,

887,

940,

993,

1046,

1099,

1152

129, 17 Offense Result A=Attempted 151, 1 Offense Name

1 of 20 C=Completed 204,

257,

310,

363,

416,

469,

522,

575,

Change 3, 09/18/2020 57 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

Table 7. Results of Trial Segment, Continued

FIELD FIELD NAME DOMAIN RECORD SIZE STANDARD NAME

NUMBER POSITION

628,

681,

129, 17, Offense Result A=Attempted 734, 1 Offense Name

Continued 1 of 20 C=Completed 787,

840,

893,

946,

999,

1052,

1105,

1158

129, 8 Involvement P=Principal 152, 1 Derived:

1 of 20 A=Accessory 205, Person-Situation Role

C=Conspiracy

258, Category Code;

S=Solicit

311, Offense Type Code

364,

417,

470,

523,

576,

629,

682,

735,

788,

841,

894,

947,

1000,

1053,

1106,

1159

130 Offense Description TEXT 153, 20 Offense Description

1 of 20

206,

Text

259,

312,

365,

418,

471,

524,

577,

630,

683,

736,

789,

842,

895,

948,

1001,

1054,

1107,

1160

Change 3, 09/18/2020 58 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

Table 7. Results of Trial Segment, Continued

FIELD FIELD NAME DOMAIN RECORD SIZE

NUMBER POSITION

131 Specification Number 99 173, 2

1 of 20

226,

279,

332,

385,

438,

491,

544,

597,

650,

703,

756,

809,

862,

915,

968,

1021,

1074,

1127,

1180

132 Plea G=Guilty 175, 1

1 of 20

N=Not Guilty

228,

L=Lesser Included Offense

281,

R=Not Guilty by Reason of

334,

Insanity

387,

440,

493,

546,

599,

652,

705,

758,

811,

864,

917,

970,

1023,

1076,

1129,

1182

133, 15 Lesser Included Offense A=UCMJ 176, 1

Offense Statutory Basis B=Non-Criminal Fatality 229,

(Plea) (High Interest) 282,

1 of 20

C=State 335,

D=Local 388,

E=Foreign 441,

F=Federal, Non-UCMJ 494,

547,

600,

653,

706,

STANDARD NAME

Document Identifier

Examination-

Situation-Offense

Specification Plea

Code

Derived:

Offense Statutory

Basis Code;

Organization-

Guidance Reason

Code

Change 3, 09/18/2020 59 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

Table 7. Results of Trial Segment, Continued

FIELD FIELD NAME DOMAIN RECORD SIZE

NUMBER POSITION

133, 15, Lesser Included Offense A=UCMJ 759, 1

Continued

Offense Statutory Basis

B=Non-Criminal Fatality 812,

(Plea) (High Interest) 865,

1 of 20

C=State 918,

D=Local 971,

E=Foreign 1024,

F=Federal, Non-UCMJ 1077,

1130,

1183

133, 16 Lesser Included Offense See Enclosure 2 to Volume 2 177, 6

Offense Code (Plea) 230,

1 of 20

283,

336,

389,

442,

495,

548,

601,

654,

707,

760,

813,

866,

919,

972,

1025,

1078,

1131,

1184

133, 17 Lesser Included Offense A=Attempted 183, 1

Offense Result (Plea) C=Completed 236,

1 of 20

289,

342,

395,

448,

501,

554,

607,

660,

713,

766,

819,

872,

925,

978,

1031,

1084,

1137,

1190

STANDARD NAME

Derived:

Offense Statutory

Basis Code;

Organization-

Guidance Reason

Code

Offense Identifier

Offense Name

Change 3, 09/18/2020 60 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

Table 7. Results of Trial Segment, Continued

FIELD FIELD NAME DOMAIN RECORD SIZE

NUMBER POSITION

133, 18 Lesser Included Offense P=Principal 184, 1

Involvement (Plea) A=Accessory

237,

1 of 20

C=Conspiracy 290,

S=Solicit 343,

396,

449,

502,

555,

608,

661,

714,

767,

820,

873,

926,

979,

1032,

1085,

1138,

1191

135 Findings G=Guilty 185, 1

1 of 20 N=Not Guilty

238,

L=Lesser Included Offense

291,

R=Not Guilty by Reason

344,

of Insanity

397,

450,

503,

556,

609,

662,

715,

768,

821,

874,

927,

980,

1033,

1086,

1139,

1192

136, 15 Lesser Included Offense A=UCMJ 186, 1

Offense Statutory Basis B=Non-Criminal Fatality 239,

(Finding) (High Interest) 292,

1 of 20

C=State 345,

D=Local 398,

E=Foreign 451,

F=Federal, Non-UCMJ 504,

557,

610,

663,

716,

STANDARD NAME

Derived:

Person-Situation Role

Category Code;

Offense Type Code

Derived:

Verdict Code; Person-

Examination-Role

Code; Offense-

Association Reason

Code

Derived:

Offense Statutory

Basis Code;

Organization-

Guidance Reason

Code

Change 3, 09/18/2020 61 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

Table 7. Results of Trial Segment, Continued

FIELD FIELD NAME DOMAIN RECORD SIZE

NUMBER POSITION

136, 15, Lesser Included Offense A=UCMJ 769, 1

Continued

Offense Statutory Basis

B=Non-Criminal Fatality 822,

(Finding) (High Interest) 875,

1 of 20

C=State 928,

D=Local 981,

E=Foreign 1034,

F=Federal, Non-UCMJ 1087,

1140,

1193

136, 16 Lesser Included Offense See Enclosure 2 to Volume 2 187, 6

Offense Code (Finding) 240,

1 of 20 293,

346,

399,

452,

505,

558,

611,

664,

717,

770,

823,

876,

929,

982,

1035,

1088,

1141,

1194

136, 17 Lesser Included Offense A=Attempted 193, 1

Offense Result (Finding) C=Completed 246,

1 of 20

299,

352,

405,

458,

511,

564,

617,

670,

723,

776,

829,

882,

935,

988,

1041,

1094,

1147,

1200

STANDARD NAME

Derived:

Offense Statutory

Basis Code;

Organization-

Guidance Reason

Code

Offense Identifier

Offense Name

Change 3, 09/18/2020 62 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

Table 7. Results of Trial Segment, Continued

FIELD FIELD NAME DOMAIN RECORD SIZE STANDARD NAME

NUMBER POSITION

136, 18 Lesser Included Offense P=Principal 194, 1 Derived:

Involvement (Finding) A=Accessory

247, Person-Situation Role

1 of 20 C=Conspiracy 300, Category Code;

S=Solicit 353, Offense Type Code

406,

459,

512,

565,

618,

671,

724,

777,

830,

883,

936,

989,

1042,

1095,

1148,

1201

138 Date Adjudged YYYYMMDD 1202 8 Evaluation-Schedule-

Component Date

“SENTENCE SUSPENDED,” “SENTENCE AMOUNT,” “SENTENCE DAYS,” “SENTENCE GRADES

REDUCED,” “SENTENCE TYPE,” AND “SENTENCE DAYS DEFERRED” OCCUR NINE TIMES

139 Sentence Suspended Y=Yes 1210, 1 Confinement-

1 of 9 N=No 1233, Sentence Condition

V=Vacation of Suspended

1256,

Code

Sentence

1279,

1302,

1325,

1348,

1371,

1394

140

Sentence Amount

9999999999 1211, 10

Monetary-

1 of 10

1234,

Remuneration-

1257,

Sentence Amount

1280,

1303,

1326,

1349,

1372,

1395

141 Sentence Days 99999 1221, 5 Derived:

1 of 9

1244,

Fixed-Term-

1267, Confinement-

1290,

Sentence Duration

1313,

Quantity;

1336,

Community-

1359,

Service-Sentence

1382,

Duration Amount

1405

Change 3, 09/18/2020 63 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

Table 7. Results of Trial Segment, Continued

FIELD FIELD NAME DOMAIN RECORD SIZE STANDARD NAME

NUMBER POSITION

142 Sentence Grades Reduced 9 1226, 1 Derived:

1 of 9

1249,

Sentence Type

1272, Code; Pay-Plan-

1295, Grade Ordinal

1318,

Identifier; Evaluation-

1341,

Result Text

1364,

1387,

1410

143 Sentence Type A=No Punishment 1227, 1 Derived:

1 of 9 B=Reprimand 1250, Sentence Type

C=Restriction 1273,

Code; Administrative-

D=Hard Labor Without

1296,

Event-Evaluation

Confinement

1319,

Reason Code;

E=Specified Confinement

1342,

Administrative-

F=Confinement for Life

1365,

Event Type Code

G=Specified Forfeitures

1388,

H=Total Forfeitures

1411

I=Fines

J=Reduction in Grade

L=Discharge/Dismissal

M=Death

193 Sentence Days Deferred 99999 1228, 5 Deferred-

1 of 9 1251, Confinement-

1274, Sentence Deferment

1297,

Quantity

1320,

1343,

1366,

1389,

1412

144 Discharge Type BC=Bad Conduct Discharge 1417 2 Separation-

1 of 9 DI=Dishonorable Discharge Characterization

DS=Dismissal Code

NA=Not Applicable

145 Pretrial Confinement 999 1419 3 Derived:

Days Person-Facility

Begin Date;

Person Facility

End Date; Person

Facility Reason Code

146 Judicially Ordered Credit 9999 1422 4 Reduced-Fixed-

Days Term-Confinement-

Sentence Duration

Reduction Quantity

147 Confinement Deferred YYYYMMDD 1426 8 Derived:

Begin Date Confinement-

Sentence Condition

Code; Evaluation-

Result Date

Change 3, 09/18/2020 64 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

Table 7. Results of Trial Segment, Continued

FIELD FIELD NAME DOMAIN RECORD SIZE

NUMBER POSITION

148 Confinement Deferred YYYYMMDD 1434 8

End Date

149 Number of Pretrial 999

Victims Notified

(DD Form 2702)

150

Number of Pretrial

999

Witnesses Notified

(DD Form 2702)

151 Number of Post-Trial 999

Victims Notified

(DD Form 2703)

152 Number of Post-Trial 999

Witnesses Notified

(DD Form 2703)

153 Number of Victims 999

Electing to be Notified

(DD Form 2704)

154 Number of Witnesses 999

Electing to be Notified

(DD Form 2704)

11. CORRECTIONS SEGMENT

1442 3

1445 3

1448 3

1451 3

1454 3

1457 3

STANDARD NAME

Derived:

Confinement-

Sentence Condition

Code; Confinement-

Sentence Deferment

Quantity

Derived:

Person-Situation-

Role Code; Person-

Document-

Representation-

Reason Code

Derived:

Person-Situation-

Role Code;

Person-Document-

Representation-

Reason Code

Derived:

Person-Situation-

Role Code;

Person-Document-

Representation-

Reason Code

Derived:

Person-Situation-

Role Code;

Person-Document-

Representation-

Reason Code

Derived:

Person-Situation-

Role Code;

Person-

Administrative-

Event Role Code

Derived:

Person-Situation-

Role Code;

Person-

Administrative-

Event Role Code

a. The Corrections Segment records the actions of the corrections facility as a result of the

incident. It also provides the information required for the Department of Defense to comply with

section 14071 of title 42, U.S.C. (Reference (v)). The Corrections Segment data layout is

displayed in Table 8.

Change 3, 09/18/2020 65 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

b. Data elements used in the Corrections Segment are:

(1) Header Elements.

(2) Report Date.

(3) Report Time.

(4) Offender (Sequence) Identifier.

(5) Offender Name (Last, First, Middle Name, Cadency, Maiden Name, Alias).

(6) SSN/Alien Registration.

(7) Service.

(8) Date of Birth.

(9) Confinement Facility UIC.

(10) Gang Name.

(11) Gang Location (City, State).

(12) Cult/Extremist Name.

(13) Cult/Extremist Location (City, State).

(14) Pretrial Confinement Begin Date.

(15) Pretrial Confinement End Date.

(16) Pretrial Controlling Offense Information (Offense Statutory Basis + Offense

Identifier + Offense Result + Involvement).

(17) Post-Trial Confinement Date.

(18) Confinement Reason Gained.

(19) Post-Trial Controlling Offense Information (Offense Statutory Basis + Offense

Identifier + Offense Result + Involvement).

(20) Losing Confinement Facility UIC.

(21) Date Adjudged.

Change 3, 09/18/2020 66 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

(22) Minimum Release Date.

(23) Full-Term Release Date.

(24) Clemency Eligibility Date.

(25) Parole Eligibility Date.

(26) Release Date.

(27) Release Reason.

(28) Release Agency Name.

(29) Release Location Zip Code.

(30) Fatality Reason.

(31) Fatality-Associated FBI Location Number.

(32) Fatality-Associated Incident Number.

(33) Escapee Returned to Custody Date.

(34) Federal Bureau of Prisons Transfer Facility Code.

(35) Military Transfer Facility UIC.

(36) Number of Victims Electing Notification.

(37) Number of Witnesses Electing Notification.

(38) Notification Begin Date.

(39) Notification Reason.

(40) Number of Victims Terminating Notification.

(41) Number of Witnesses Terminating Notification.

(42) Sex Offender Processing Required.

(43) Date Notification of Release Provided to State.

(44) Date Prisoner Notified of State Registration.

Change 3, 09/18/2020 67 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

c. This segment is prepared by the correctional facility gaining the prisoner. The FBI

Location Number, Incident Number, and the original offender number are obtained from the

convening authority or losing correctional facility. A record should be submitted for each

change of status (e.g., transfer, release, clemency hearing). Multiple records should be submitted

if more than one action occurs within the reporting period.

Table 8. Corrections Segment

FIELD

NUMBER

FIELD NAME DOMAIN

RECORD

SIZE

POSITION

STANDARD

1 FBI Location Number 1 9

Derived:

Organization-

Designator Source

Assigned Identifier

2 Incident Number 10 12 Derived:

Organization-

Designator Source

Assigned Identifier;

Situation Identifier

3 Segment Type R 22 1 No Standard

4 Report Type A=ADD 23 1 No Standard

M=MODIFY

D=DELETE

155 Report Date YYYYMMDD 24 8

156 Report Time 32 4 Document Time

64 Offender Identifier 99 36 2 Person Designator

Identifier

65 Name Last 38 21 Name (Person-Name

Category=s)

66 Name First 59 14 Name (Person-Name

Category=f)

67 Name Middle Name 73 14 Name (Person-Name

Category=m)

68 Name Cadency (Jr., Sr., III) 87 4 Name (Person-Name

Category=c)

157 Name Maiden 91 21

Name (Person-Name

Usage Code=m)

69 Name Alias (Last) 112 21 Name (Person-Name

Usage Code=a)

69 Name Alias (First) 133 14 Name (Person-Name

Usage Code=a)

71 SSN/Alien Registration 999999999 147 9 Person-Designator

Identifier (Person-

Designator Type

Code=s)

48 Service

A=Army

156 1

Uniformed-Service

N=Navy Organization Code

F=Air Force

M=Marine Corps

C=Coast Guard

D=DoD

Change 3, 09/18/2020 68 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

Table 8. Corrections Segment, Continued

FIELD

NUMBER

FIELD NAME DOMAIN

RECORD

SIZE

POSITION

STANDARD

72 Date of Birth YYYYMMDD 157 8 Person Birth Date

158 Confinement Facility 165 8 Organization-

UIC Designator Source

Assigned Identifier

159 Gang Name TEXT 173 20 Organization Name

Text

160 Gang Location City TEXT 193 20 City Name

161 Gang Location State TEXT See Table 12 in 213 2 State Code

Volume 2

162 Cult/Extremist Name TEXT 215 20 Organization Name

Text

163

Cult/Extremist Location

TEXT 235 20 City Name

City

164 Cult/Extremist Location TEXT See Table 12 in 255 2 State Code

State Volume 2

165 Pretrial Confinement YYYYMMDD 257 8 Person-Facility Begin

Begin Date Date

166 Pretrial Confinement YYYYMMDD 265 8 Person-Facility End

End Date Date

167, 15 Pretrial Controlling A=UCMJ 273 1 Derived:

Offense Statutory Basis B=Non-Criminal Fatality Offense Statutory

(High Interest) Basis Code;

C=State Organization-

D=Local Guidance Reason

E=Foreign Code

F=Federal, UCMJ

167, 16 Pretrial Controlling See Enclosure 2 to Volume 2 274 6 Offense Identifier

Offense Identifier

167, 17 Pretrial Controlling A=Attempted 280 1 Offense Name

Offense Offense Result C=Completed

167, 18 Pretrial Controlling P=Principal 281 1 Derived:

Offense Involvement A=Accessory

Person-Situation

C=Conspiracy

Role Category Code;

S=Solicit

Offense Type Code

168 Post-Trial Confinement YYYYMMDD 282 8 Person-Facility Begin

Date Date

169 Confinement Reason A=New Sentence 290 1 Confinement

Gained B=Parole Revocation Circumstance Code

C=Returned Escapee

D=Transfer

E=Vacated Suspension

F=Pretrial Confinement

170, 15 Post-Trial Controlling

A=UCMJ

291 1 Derived:

Offense Statutory Basis

B=Non-Criminal Fatality

Offense Statutory

(High Interest)

C=State

D=Local

E=Foreign

Basis Code;

Organization-

Guidance Reason

Code

F=Federal, UCMJ

170, 16 Post-Trial Controlling See Enclosure 2 to Volume 2 292 6 Offense Identifier

Offense Identifier

Change 3, 09/18/2020 69 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

Table 8. Corrections Segment, Continued

FIELD

NUMBER

FIELD NAME DOMAIN

RECORD

SIZE

POSITION

STANDARD

170, 17 Post-Trial Controlling A=Attempted 298 1 Offense Name

Offense Offense Result C=Completed

170, 18 Post-Trial Controlling P=Principal 299 1 Derived:

Offense Involvement A=Accessory Person-Situation

C=Conspiracy Role Category Code;

S=Solicit Offense Type Code

171 Losing Confinement 300 8 Organization-

Facility UIC Designator Source

Assigned Identifier

138 Date Adjudged YYYYMMDD 308 8 Evaluation-Schedule-

Component Date

172 Minimum Release Date YYYYMMDD 316 8 Derived:

Fixed-Term-

Confinement-Sentence

Duration Quantity;

Judicial-Proceeding

Type Code; Person-

Facility Begin Date

173 Full-Term Release Date YYYYMMDD 324 8 Derived:

Fixed-Term-

Confinement-Sentence

Duration Quantity;

Judicial-Proceeding

Type Code; Person-

Facility Begin Date:

Unconditional-Release-

Confinement

Type Code

174 Clemency Eligibility YYYYMMDD 332 8 Person-Examination-

Date Type-Reason Begin

Date

175 Parole Eligibility Date YYYYMMDD 340 8 Person-Examination-

Type-Reason Begin

Date

176 Release Date YYYYMMDD 348 8 Person-Facility End

Date

177 Release Reason A=Appellate 356 1 Derived:

D=Death Conditional-Release-

T=Transfer

Confinement Type

E=Escape

Code; Confinement

C=Clemency

Termination Type

O=Overturned

Code; Unconditional-

X=Expiration of Sentence

Release-Confinement

P=Parole

Type Code

R=Returned to Duty

I=Investigative Officer’s

Release

L=Emergency Leave

M=Magistrate’s Release

178 Release Agency Name TEXT 357 20 Organization Name

Text

Change 3, 09/18/2020 70 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

Table 8. Corrections Segment, Continued

FIELD

NUMBER

FIELD NAME DOMAIN

RECORD

SIZE

POSITION

STANDARD

179 Release Location Zip 999999999 377 9 Postal-Region Code

Code

180 Fatality Reason E=Execution 386 1 Derived:

N=Natural Causes/Illness Confinement

S=Suicide Termination Type

H=Homicide Code

A=Accident

181 Fatality-Associated FBI 387 9 Derived:

Location Number Organization-

Designator Source

Assigned Identifier;

Situation Identifier

182 Fatality-Associated 396 12 Derived:

Incident Number Organization-

Designator

Source Assigned

Identifier; Situation

Identifier

183 Escapee Returned to YYYYMMDD 408 8 Person-Facility

Custody Date Begin Date;

Confinement

Circumstance Code

184 Federal Bureau of See Table 14 in Volume 2 416 3 Derived:

PrisonsTransfer Facility Facility Name;

Code Organization-Name

Text

185 Military Transfer 419 8 Organization-

Facility UIC Designator Source

Assigned Identifier

186

Number of Victims

99 427 2

Derived:

Electing Notification Administrative-Event

Subject Code;

Administrative-Event

Type Code; Person-

Situation Role Code

187 Number of Witnesses 99 429 2 Derived:

Electing Notification Administrative-Event

Subject Code;

Administrative-Event

Type Code; Person-

Situation Role Code

188 Notification Begin Date YYYYMMDD 431 8 Person-Document-

Representation-

Reason Begin Date

Change 3, 09/18/2020 71 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

Table 8. Corrections Segment, Continued

FIELD

NUMBER

FIELD NAME DOMAIN

RECORD

SIZE

POSITION

STANDARD

189 Notification Reason A=Parole Eligibility Date 439 1 Derived:

B=Clemency Eligibility

Person-Examination-

Date

Type-Reason Code;

C=Parole Hearing

Confinement

D=Clemency Hearing

Termination Type

E=Transfer

Code; Confinement

F=Escape

Circumstance Code

G=Returned Escapee

H=Release

I=Initial Contact

190 Number of Victims 99 440 2 Derived:

Terminating Administrative-Event

Notification Category Code;

Administrative-Event

Subject Code

191 Number of Witnesses 99 442 2 Derived:

Terminating Administrative-Event

Notification Category Code;

Administrative-Event

Subject Code

194 Sex Offender Y=Yes 444 1 No Standard

Processing Required N=No

See Table 10 in Volume 2 for

allowable codes

195 Date Notification of YYYYMMDD 445 8

Release Provided to

State

196

Date Prisoner Notified

YYYYMMDD 453 8

of State Registration

Change 3, 09/18/2020 72 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

ENCLOSURE 5

DATA SUBMISSION PROCEDURES

1. INFORMATION REQUIREMENTS

a. DMDC shall collect data directly from each Service in an automated format using the

standard definitions and automated media submission formats specified in this Manual.

b. The Military Services and Defense Agencies with criminal incident record management

systems shall collect, prepare, store, and submit data to DMDC in accordance with References

(m) and (n) and DoDIs 8910.01 and 8320.02 (References (w) and (x)).

c. All DIBRS data submitters shall use DoD standard data elements and codes where

applicable. When source files contain codes different from the standard, conversion to the DoD

standard is the responsibility of the submitting organization.

d. All DIBRS data submitters shall report automated data through separate files, as specified

in section 2 of this enclosure, and formatted and coded as specified in Tables 1 through 8 of this

Volume.

(1) In cases in which the requested formats or coding structures do not correspond to

available data structures in current organizational systems, DMDC shall work with the affected

organization to develop a transition plan to implement the data requirement.

(2) All DIBRS data submitters shall prepare reports using the specified reporting

procedures and submit them 15 workdays after the end of each month.

(3) DMDC shall return submissions containing errors with appropriate error notification

to the submitting agency. The submitting agency shall make the appropriate corrections and

resubmit the report within 30 days. Data submitted to DMDC is edited in accordance with the

requirements specified in both volumes of this Manual. In addition, if data element 5,

REPORTABLE TO NIBRS, is “Y,” additional edit checks are performed in accordance with the

FBI requirements specified in Volumes 1 to 4 of Reference (o). All errors shall be returned to

the submitting agency with full explanations and descriptions. All data submission errors shall

be tracked to completion. Corrections for each type of error are varied; however, DMDC shall

provide these three general classes of messages to submitters with full explanation statements:

(a) Data Prevented Load. Errors are so profound that the segment is prevented from

being processed by the DIBRS system. Examples include segments submitted for which an

Administrative Segment does not exist, or a segment submitted without all key fields reported.

In all cases, “Data Prevented Load” errors mean the segment was rejected by the DIBRS system.

A new “add” record should be submitted to correct this type of error.

Change 3, 09/18/2020 73 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

(b) Data Not Reportable. Errors are generated when any of DIBRS or NIBRS (as

appropriate) edit checks indicate a code is not correct or a logical check is marked invalid in

accordance with the reporting instructions. The submitted data fields are ACCEPTED as

submitted; however, the incident may not be reported to NIBRS until the submitting agency

corrects all errors that make the transaction marked invalid for submission. To correct the data,

the submitting agency must resubmit segment information either as a “modify” or as a

“delete,” followed by an “add” if the segment was originally accepted. Numerous types of

actions required may be contained in the full explanation returned to the submitting agency.

DMDC shall submit any segments needed to correct or add the NIBRS incident.

(c) “Warning: Data Shall Be Re-Coded at Report Time.” DMDC shall provide this

warning to the submitting agencies whenever a code submitted in accordance with the DIBRS

must be re-coded to submit to NIBRS. No correction is required when this warning is received.

2. SUBMISSION INSTRUCTIONS. The DIBRS data submitting agencies shall:

a. Coordinate file-naming conventions and security of data with DMDC before the initial

transmission of data via the Defense Information Systems Network or a comparable data

network. Submitting organizations are responsible for the accuracy and completeness of each

electronic data transfer.

b. Right-justify numeric data with leading zeros; left-justify alpha data with trailing blanks.

c. For file transmission, use blanks for null, inapplicable, and unavailable data unless another

code is specified.

d. Provide a record count.

e. Mail to:

Defense Manpower Data Center

Office of the Assistant Secretary of Defense (P&R)

Project Officer, DIBRS File

DoD Center Monterey Bay

400 Gigling Road

Seaside, CA 93955-6771

3. CORRECTION OF RECORDS

a. Individual written requests for correction of DIBRS records may be addressed to the

address in paragraph 2.e. of this enclosure for action and response. DMDC shall be responsible

for providing all responses, both interim and final, as appropriate, to individuals requesting

corrections.

Change 3, 09/18/2020 74 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

b. Requests for correction of DIBRS records shall be handled according to these procedures:

(1) Upon receipt of the request, DMDC shall verify with the relevant Component

responsible official that the DIBRS record is consistent with the DoD Component records.

(2) If the DIBRS record is inconsistent with the DoD Component records, DMDC shall

forward the request for correction of records to the Component responsible official for

investigation and validation. The Component responsible official shall submit corrected records

to DMDC as soon as the investigation is complete. DMDC shall submit corrections as specified

by NIBRS reporting procedures or by the reporting procedures set forth in The Brady Handgun

Violence Prevention Act of 1993, as amended.

(3) At the request of the FBI, DMDC shall verify within 3 workdays whether a DIBRS

record is consistent with FBI records. If the DIBRS record is inconsistent with FBI records,

DMDC shall forward the matter to the Component responsible official for investigation and

validation.

4. AUTHORIZED RELEASE OF INDIVIDUAL INFORMATION

a. Pursuant to the DIBRS system of records notice at Page 56062 of Volume 72, Federal

Register (Reference (y)), requests from individuals for information about themselves shall be

forwarded to and processed by the Privacy Act Officer at:

Office of Freedom of Information

Washington Headquarters Services

1155 Defense Pentagon

Washington, DC 20301-1155

b. All other requests for information about individuals shall be forwarded for action to the

individual’s sponsoring DoD Component. Pursuant to Reference (c) and subparagraph 1.c.(4) of

Enclosure 2, disclosure of DIBRS information containing PII within the Department of Defense

is limited solely to DMDC use for official statistical analysis and record verification, and outside

the Department of Defense solely to the FBI to satisfy the reporting requirements of The Brady

Handgun Violence Prevention Act of 1993, as amended.

5. AUTHORIZED RELEASE OF STATISTICAL INFORMATION. DMDC shall extract a

quarterly compendium of statistical information and circulate it to the DoD Components for

review. PII shall not be released as a part of the extract nor shall any information that is

identifying by circumstance. Once the DoD Components have reviewed the extract without

objection, DMDC shall release the information in response to legitimate inquiries. In the case of

a request for statistical information not included in the quarterly compendium, DMDC shall

coordinate each new analysis with any concerned DoD Component prior to release.

Change 3, 09/18/2020 75 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

6. UNAUTHORIZED ACCESS. DMDC stores input data files in a controlled access area

located in the U.S. Naval Postgraduate School in Monterey, California. DMDC stores data files

in the secure DMDC facility at 400 Gigling Road in Seaside, California. Badge authorization is

required for entry into these facilities. Additionally, a limited number of users have access to the

Oracle database. At all times, the data are under the control of the DMDC DIBRS Database

Administrator. All DMDC personal computers are within the secure DMDC facility. Detailed

information on DMDC security procedures is available on request from the DIBRS Project

Officer at the address in paragraph 2.e. of this enclosure.

7. DATABASE CHANGE MANAGEMENT. Changes to this Manual should be submitted to

the DIBRS Council Configuration Management Subcommittee, which is managed by DMDC.

Change requests may be sent to DMDC at the address in paragraph 2.e. of this enclosure. This

committee meets at least once a year to consider the impact of suggested changes on each

submitting agency. Changes resulting from new legislation or additional requirements shall be

presented to this subcommittee for consideration. The subcommittee shall advise the

OUSD(P&R) on implementation schedules.

8. TESTING PROCEDURES FOR UNMATCHED SEGMENTS. During implementation

testing, if it is not possible to submit the adjudication segments of Commander’s Action, Results

of Trial, and Corrections as part of a complete incident (e.g., the reporting responsibility is split

across functional areas with different submission capabilities), records not corresponding to

existing incidents must be submitted as a separate file and designated with a file name containing

X (Commander’s Action), Y (Results of Trial), and Z (Corrections), respectively. These files

shall be processed and reported on as test data only. The data cannot and shall not remain part of

the DIBRS database and shall not be used for any external reporting outside DMDC.

9. DIBRS PII SHELF-LIFE

a. PII is reported to the DIBRS in accordance with paragraph 2.c. of Enclosure 3 of this

Volume. Offense categories govern the length of time PII remains in the DIBRS database (shelf-

life) for a given incident in order to:

(1) Provide DIBRS database managers the tools (PII) they need for quality control,

insuring that individuals and incidents are matched across DIBRS segments and time of

submission.

(2) Mitigate concerns related to the DoD Privacy Program in Reference (m) and the

DoD Freedom of Information Act Program in DoDD 5400.07 (Reference (z)) by limiting the

time PII resides in the database based on the class of crime, statutory reporting requirements,

and Service punishment policy.

(3) Match DIBRS procedures, as a criminal database, with those of the Services that do

not carry an individual’s criminal record forward.

Change 3, 09/18/2020 76 ENCLOSURE 4

DoDM 7730.47-M-V1, December 7, 2010

b. Offense categories and corresponding PII shelf life are displayed in Table 9.

Table 9. PII Shelf Life

OFFENSE CATEGORY PII SHELF LIFE

Offenses reportable pursuant to Brady

*

or involving sex offender

registration

99 years from entry into database

Class A offenses (other than those disposed of by UCMJ Article 15 5 years from entry into database

administrative sanction) not reportable by the Department of Defense or term of confinement,

pursuant to Brady

*

or involving sex offender registration whichever is longer

Military offenses (for which there is no NIBRS equivalent) not

reportable by the Department of Defense pursuant to Brady* and for

which confinement of more than 1 year or death is adjudged by a

court-martial

5 years from entry into database

or term of confinement,

whichever is longer

Class B offenses (other than those disposed of by UCMJ Article 15 3 years from entry into database

administrative sanction) not reportable by the Department of Defense

or term of confinement,

pursuant to Brady

*

or involving sex offender registration whichever is longer

Military offenses (other than those disposed of by UCMJ Article 15 3 years from entry into database

administrative sanction and for which there is no NIBRS equivalent)

not reportable by the Department of Defense pursuant to Brady

*

Offenses disposed of by UCMJ Article 15 or by administrative

sanctions and not reportable by the Department of Defense pursuant

to Brady

*

or involving sex offender registration

6 months from entry into database

Acquittals, set-aside actions, and unfounded allegations Immediate removal

*

The Brady Handgun Violence Prevention Act of 1993, as amended

Change 3, 09/18/2020 77 ENCLOSURE 4

DCIO

DIBRS

DMDC

DoDD

DoDI

DoDM 7730.47-M-V1, December 7, 2010

GLOSSARY

PART I. ABBREVIATIONS AND ACRONYMS

Defense Criminal Investigative Organization

Defense Incident-Based Reporting System

Defense Manpower Data Center

DoD directive

DoD instruction

FBI Federal Bureau of Investigation

IG DoD Inspector General of the Department of Defense

NIBRS National Incident-Based Reporting System

OUSD(P&R) Office of the Under Secretary of Defense for Personnel and Readiness

PHI protected health information

PII personal identifying information

SSN Social Security number

UCMJ

UCR

UIC

U.S.C.

USD(P&R)

Uniform Code of Military Justice

uniform crime reporting

unit identification code

United States Code

Under Secretary of Defense for Personnel and Readiness

PART II. DEFINITIONS

Unless otherwise noted, these terms and their definitions are for the purpose of this Volume.

acting in concert. Indicates that all of the offenders who actually commit or assist in the

commission of a crime(s) at the same time and place are aware of and consent to the commission

of the crime(s), or, if non-consenting, their actions assist in the commission of the offense(s).

bias. A preformed negative opinion or attitude toward a group of persons based on their race,

religion, ethnicity or national origin, sexual orientation, or disability.

bias crime. A criminal offense committed against a person or property that is motivated, in

whole or in part, by the offender’s bias against a race, religion, ethnic or national origin, sexual

orientation, or disability group. Also known as a “hate crime.” Even if the offender was

Change 3, 09/18/2020 78 GLOSSARY

DoDM 7730.47-M-V1, December 7, 2010

mistaken in his or her perception that the victim was a member of the group he or she was acting

against, the offense is still a bias crime because the offender was motivated by bias against the

group.

bisexual. Of or relating to persons who experience sexual attraction toward, and responsiveness

to, both males and females; a bisexual person.

case. All criminal charges brought against a particular accused for disposition at a single forum.

A case may include any number of offenses resulting from any number of incidents.

central repository. The DoD Component facility designated to receive Service inputs of incident

data from functional consolidating activities and to report this data to other Federal agencies.

DMDC is the DoD Central Repository.

Component responsible official. The person designated by the Head of each DoD Component

primarily responsible in the Component for coordinating, implementing, and managing the

reporting system established by Reference (c).

credible information. Information disclosed or obtained that, considering the source and nature

of the information and the totality of the circumstances, is sufficiently believable to indicate

criminal activity has occurred and would cause a reasonable person under similar circumstances

to pursue the facts of the case further.

criminal offense against a victim who is a minor. Any criminal offense that consists of, or that

consists of an attempt to commit:

Kidnapping of a minor, except by a parent.

False imprisonment of a minor, except by a parent.

Criminal sexual conduct toward a minor.

Solicitation of a minor to engage in sexual conduct.

Use of a minor in a sexual performance.

Solicitation of a minor to practice prostitution.

Carnal knowledge of a minor.

A conduct that by its nature is a sexual offense against a minor.

DIBRS. The incident-based system used to report criminal and specifically identified incidents

from initial law enforcement response to offender release from confinement. It includes

provisions to comply with The Brady Handgun Violence Prevention Act of 1993, as amended,

and References (b) and (f).

Change 3, 09/18/2020 79 GLOSSARY

Loading page...

Loading page...

Page /  84

-100%+

Safe Document Download

×

Safe Document Download:
773047m_vol1.pdf

Complete

OK

Document Properties

• Printed Page Count: 84
• Title: DoDM 7730.47-M, Volume 1, "Defense Incident-Based Reporting System (DIBRS): Data Segments and Elements," December 7, 2010; Incorporating Change 3 on September 18, 2020
• author: USD(I&S)
• Company: JSP
• Created: 2018/07/23
• Creation Date: 2020/09/17 13:13:35-04'00'
• Creator Tool: Acrobat PDFMaker 15 for Word
• keywords: Defense Incident-Based Reporting System; DIBRS; law enforcement; reporting
• LastSaved: 2018/12/03
• Modification Date: 2020/09/18 13:19:58-04'00'
• Producer: Adobe PDF Library 15.0
• SourceModified: 2020/09/17 17:10:35

Input value altered

×

The website Javascript has altered an input field value, please confirm accuracy.