20141111_DSD - Offender Conduct

Detailed System Design
Total Offender Management System
(TOMS)
Offender Conduct
4000 Westerly Place, Suite 110
Newport Beach, California 9266

Prepared and Ow ned By - Capita Technologies
Confidential – Not to Be Reproduced or Emailed or Printed
i 12/4/2013
Table of Contents
2.13 Offender Conduct .............................................................................................4
2.13.1 Summary of Gaps That Are the Subject of the Design ......................4
2.13.2 Overall Design Diagram for the Functional Component ..................21
2.13.3 Description of the Design Diagram......................................................21
2.13.4 Menu Being Updated.............................................................................23
2.13.4.1 Menu Navigation.............................................................................23
2.13.4.2 Data Elements and Behavior........................................................24
2.13.4.3 Use Cases.......................................................................................25
2.13.4.4 Error Handing..................................................................................26
2.13.5 Incident Information ...............................................................................31
2.13.5.1 Incident Information Screen..........................................................31
2.13.5.3 Use Cases.......................................................................................42
2.13.5.3.1 Add New Incident......................................................................42
2.13.5.3.2 Edit Incident Report..................................................................43
2.13.5.4 Process Input(s) .............................................................................44
2.13.5.4.1 Incident Number Current Value ..............................................44
2.13.5.5 Processes........................................................................................44
2.13.5.5.1 Calculate Incident Number......................................................44
2.13.5.5.2 Send Supervisor Notification...................................................45
2.13.5.6 Error Handing..................................................................................46
2.13.6 Conduct Summary .................................................................................50
2.13.6.1 Conduct Summary Screen............................................................50
2.13.6.3 Use Cases.......................................................................................52
2.13.6.3.1 Edit Conduct Report .................................................................52
2.13.6.3.2 Dismiss Conduct Report..........................................................53
2.13.6.3.3 Add Hearing to Conduct Report .............................................54
2.13.6.3.4 Add Appeal ................................................................................55
2.13.6.3.5 Add Sanction .............................................................................56
2.13.6.3.6 Add Credit Class Review Hearing..........................................58
2.13.6.3.7 Add Petition to Restore Credit Time Hearing .......................59
2.13.6.4 Process Input(s) .............................................................................60
2.13.6.5 Processes........................................................................................60
2.13.6.5.1 Populate the Conduct Summary Grid....................................60
2.13.6.6 Error Handing..................................................................................61
2.13.7 Conduct Hearing Summary ..................................................................64

Page ii of 132 0731/2014
2.13.7.1 Conduct Hearing Summary Screen.............................................64
2.13.7.3 Use Cases.......................................................................................66
2.13.7.3.1 Add Hearing via Hearing Summary Screen .........................66
2.13.7.3.2 Add Appeal via Conduct Hearing Summary Screen ...........67
2.13.7.3.3 Add Sanction via Conduct Hearing Summary Screen........68
2.13.7.3.4 Add Credit Class Review Hearing via Conduct Hearing
Summary Screen............................................................................................69
2.13.7.3.5 Add Petition to Restore Credit Time Hearing via Conduct
Hearing Summary Screen.............................................................................71
2.13.7.4 Process Input(s) .............................................................................72
2.13.7.5 Processes........................................................................................72
2.13.7.5.1 Calculating the Description Text.............................................72
2.13.7.5.2 Calculating the values for the R, I, S, E grid columns. .......72
2.13.7.5.3 Populate the Conduct Hearing Summary Grid.....................72
2.13.7.6 Error Handing..................................................................................74
2.13.8 New Conduct Information .....................................................................77
2.13.8.1 Conduct Information Screen - New .............................................77
2.13.8.3 Use Cases.......................................................................................80
2.13.8.3.1 Create New Conduct Report...................................................80
2.13.8.4 Process Input(s) .............................................................................81
2.13.8.4.1 Case Number Current Value...................................................81
2.13.8.5 Processes........................................................................................81
2.13.8.5.1 Facility Dropdown Text ............................................................81
2.13.8.5.2 Populate Conduct Code Dropdown .......................................81
2.13.8.5.3 Calculate Case Number...........................................................81
2.13.8.5.4 Location Requirement..............................................................81
2.13.8.5.5 Schedule Hearing Notification ................................................81
2.13.8.6 Error Handing..................................................................................81
2.13.9 Conduct Information...............................................................................85
2.13.9.1 Conduct Information Screen.........................................................85
2.13.9.3 Use Cases.......................................................................................89
2.13.9.3.1 Edit Conduct Report .................................................................89
2.13.9.3.2 Dismiss Conduct Report..........................................................89
2.13.9.3.3 Add Hearing to Conduct Report .............................................91
2.13.9.3.4 Add Appeal ................................................................................92
2.13.9.3.5 Add Sanction .............................................................................93
2.13.9.3.6 Add Credit Class Review Hearing..........................................94
2.13.9.3.7 Add Petition to Restore Credit Time Hearing .......................96
2.13.9.4 Process Input(s) .............................................................................97
2.13.9.4.1 Current Credit Class.................................................................97

Page iii of 132 0731/2014
2.13.9.4.2 Current Earned Credit Time ....................................................97
2.13.9.5 Processes........................................................................................97
2.13.9.5.1 Process New Sanctions...........................................................97
2.13.9.5.2 Process Existing Sanctions.....................................................97
2.13.9.5.3 Sanction Notification Process Chart ......................................98
2.13.9.5.4 Allow Read Only......................................................................102
2.13.9.5.5 Populate Event Dropdown.....................................................102
2.13.9.6 Error Handing................................................................................103
2.13.10 Admin/Create LOV and Lookup .....................................................106
2.13.10.1 Create Lookup Event Type.........................................................106
2.13.10.2 Create Lookup Location..............................................................107
2.13.10.3 Create Lookup Results................................................................108
2.13.10.4 Create Lookup Actions................................................................108
2.13.10.5 Create Lookup Assaults..............................................................109
2.13.10.6 Create Lookup Suicidal Behavior ..............................................110
2.13.10.7 Create Lookup Property..............................................................111
2.13.10.8 Create Lookup Misconduct.........................................................112
2.13.10.9 Create Lookup Miscellaneous....................................................113
2.13.10.10 Create Lookup Restraint Type Used ......................................114
2.13.10.11 Create Lookup Injured Person.................................................114
2.13.10.12 Create Lookup Injury Source ...................................................115
2.13.10.13 Create LOV Conduct Code ......................................................116
2.13.10.14 Create Lookup Assault Victim..................................................117
2.13.10.15 Create Lookup Plea...................................................................118
2.13.10.16 Create Lookup Authorized By..................................................118
2.13.10.17 Create Lookup Confinement ....................................................119
2.13.10.18 Create Lookup Seen By Medical.............................................120
3 DATABASE STRUCTURE CHANGES......................................................................... 121
4 REVISION HISTORY.............................................. ERROR! BOOKMARK NOT DEFINED.
Table of Figures
Figure 1 – Overall Diagram of Functional Component.............................................21
Figure 2 – Conduct Menu .............................................................................................23
Figure 3 – Incident Information - Top.........................................................................31
Figure 4 – Incident Information - Bottom ...................................................................32
Figure 5 – Conduct Summary ......................................................................................50
Figure 6 – Conduct Hearing Summary.......................................................................64
Figure 7 – Conduct Information - New........................................................................77
Figure 8 – Conduct Information ...................................................................................85

Page 4 of 132 0731/2014
2.13 Offender Conduct
2.13.1 Summary of Gaps That Are the Subject of the Design
Req. # Requirement Desc.
Gap Exists?
(Yes, Partial)
Description of Gap Module Screen Proposed Gap Solution
CD.1
The software application
shall provide templates
for initiating conduct
reports
No None. Reports & Forms Framework None.
CD.2
shall allow inmate data to
be modified to reflect
conduct infractions and
associated matters such
as time credit
calculations, loss of
credits, visits, etc.
Yes
Addition of a new Conduct Information
Screen. This screen will allow the
addition of offender conduct infractions
and any related sanctions such as loss
of Earned Credit Time, change in Credit
Class or loss of visitation rights.
Conduct Information Screen
ADMIN – Lookup – Location
ADMIN – LOV – Offender Conduct
Code
ADMIN – Lookup- Assault Victim
ADMIN – Lookup- Plea
ADMIN – Lookup- Event Type
ADMIN – Lookup- Results
ADMIN – Lookup- Actions
ADMIN – Lookup- Authorized By
Create a new Conduct
Information Screen. The
screen will allow the user to
add or edit current offender
conduct details including
related sanction information
Data Elements:
1. Incident Date
2. Class
3. Date Report Received
4. Conduct
5. Case Number (Auto
generated)
6. Assault Victim
7. Facility
8. Thrown Substance
9. House
10. Reporting Person
11. Range
12. Plea
13. Shop/Other

Page 5 of 132 0731/2014
Gap Exists?
(Yes, Partial)
14. Prehearing Segregation
15. Event Type
16. Event Date
17. Effective Date
18. End Date
19. Facility
20. Results
21. Value
22. Actions
23. Authorized By
Create Lookup -
Offense Location
Data Elements:
1. Name
2. Abbreviation
3. Description
4. Effective Start Date
5. Effective End Date
Create LOV -
Conduct Code
Data Elements:
1. Class
2. Number
3. Abbreviation
4. Description
5. Classification

Page 6 of 132 0731/2014
Gap Exists?
(Yes, Partial)
Create Lookup -
Assault Victim
Data Elements:
1. Name
2. Abbreviation
3. Description
Create Lookup -
Plea
Data Elements:
1. Name
2. Abbreviation
3. Description
Create Lookup -
Event
Data Elements:
1. Name
2. Abbreviation
3. Description
Create Lookup -
Results
Data Elements:
1. Name

Page 7 of 132 0731/2014
Gap Exists?
(Yes, Partial)
2. Abbreviation
3. Description
Create Lookup -
Actions
Data Elements:
1. Name
2. Abbreviation
3. Description
Create Lookup -
Authorized By
Data Elements:
1. Name
2. Abbreviation
3. Description
Side Note:
Both “Housing” and
“Range” LOV Declarations
found within Offender
Movement Module.
CD.3
shall track rule violation
and the potential formal
Yes
addition of rule violations and any
Conduct Hearing Summary

Page 8 of 132 0731/2014
Gap Exists?
(Yes, Partial)
hearing process that may
result
formal hearings that may be held.
Addition of a new Conduct Hearing
Summary Screen. This screen will track
the hearing if one results from a rule
violation.
add or edit current rule
violations and formal
hearings related to
violations.
Data Elements:
Reference CD.2
Hearing Summary Screen.
This screen will show all
hearings during an
offender’s incarcerated
duration.
Data Elements:
1. Date
2. Class
3. Code
4. Description
5. Result
6. Recommend (R)
7. Impose (I)
8. Suspend (S)
9. Enforce (E)
20141111– PerIDOC
Feedbackdated,
10/08/2014, “Offender
CurrentCommitment

Page 9 of 132 0731/2014
Gap Exists?
(Yes, Partial)
PeriodsandPrevious
CommitmentPeriods,if
any,will beappropriately
displayedtoscreen by
leveragingthe SQL’s
DefaultDescendingSort
Pattern,by StartandEnd
Dates
CD.4
shall capture, store and
report an inmate’s
conduct history
Yes
Addition of the Conduct Summary
Screen. This screen will incorporate
both current and past Conduct
Information for the offender
Conduct Summary Screen
Summary Screen containing
both current and past
conduct information.
Data Elements:
1. Case Number
2. Class
3. Conduct Code
4. Description
5. Offense Date
6. Report Date
7. Hearing Date
CD.5
shall capture, store, and
report data to allow
searches of inmate
conduct data for easy
accessibility
Yes
Capability of searching and/or reporting
against an offenders conduct data
1. Types of Searches:
 Amount of offenses
 Type of Offenses
Conduct Summary Screen
Reports & Forms Framework
Create new Conduct
Summary Screen. The
screen will not display
records where the case was
dismissed or the offender
was found not guilty.

Page 10 of 132 0731/2014
Gap Exists?
(Yes, Partial)
 How many by
unitdormhousingbed
assignments(Location basically)
 What the results were, If they
Appealed it
 These searches will be capable
by either involving an IDOC
Database Administrator or via
the TOMS Application AdHoc
Reporting Mechanism through
the Reports and Form
Framework.
Data Elements:
Reference CD.4
Create new Conduct
sanction information related
to the current infraction and
resultant hearing.
Data Elements:
Reference CD.2
Reporting and AdHoc
Reporting will compensate
for Juvenile requirements.
CD.6
shall create, store, and
report on sanctions given
as a result of a conduct
hearing.
Yes
addition of sanctions pertaining to a
given infraction and formal hearing.
Addition of a new Hearing Summary
Screen. This screen will show all of the
sanctions received as the result of
conduct hearings.
Hearing Summary Screen
Create new Conduct
sanction information related
resultant hearing.
Data Elements:
Reference CD.2
Hearing Summary Screen.

Page 11 of 132 0731/2014
Gap Exists?
(Yes, Partial)
This screen will show all
sanctions given during an
duration..
Data Elements:
Reference CD.3
20141111– PerIDOC
Feedbackdated,
10/08/2014, “Offender
CurrentCommitment
PeriodsandPrevious
Dates
CD.7
report on conducts
dismissed as well as
appeals made and the
appeal results.
Yes
Any reports made to query the conduct
data should exclude the conducts
dismissed.
The report queries can include the
appeals made and appeal results.
addition of appeals pertaining to a given
infraction and formal hearing.
Create new Conduct
appeal information related
resultant hearing.
Data Elements:
Reference CD.2

Page 12 of 132 0731/2014
Gap Exists?
(Yes, Partial)
Screen.
The screen will be filtered such that it
will not show dismissed or not guilty
conduct records.
Create a new Hearing
Summary Screen. This
screen will show all of
conducts during an
duration.
Data Elements:
Reference CD.3
20141111– PerIDOC
Feedbackdated,
10/08/2014, “Offender
CurrentCommitment
PeriodsandPrevious
Dates
CD.8
shall track all petitions by
offenders for deprived
time to be restored.
Yes
Screen.
This screen will allow the tracking of
petition hearing for the restoration of
ECT.
Screen. This screen will show all of the
State Form, SF 6949,
Petition for Restoration of
Time will reside within
Forms.
Create new Conduct

Page 13 of 132 0731/2014
Gap Exists?
(Yes, Partial)
hearings for the restoration of ECT lost. petition hearings for the
restoration of ECT.
Data Elements:
Reference CD.2
Create a new Hearing
Summary Screen. This
screen will show all of
hearings for restoration of
ECT lost during an
duration.
Data Elements:
Reference CD.3
20141111– PerIDOC
Feedbackdated,
10/08/2014, “Offender
CurrentCommitment
PeriodsandPrevious
Dates
CD.9 Any conducts dismissed Yes Addition of a Conduct Summary Screen. Conduct Summary Screen Create new Conduct

Page 14 of 132 0731/2014
Gap Exists?
(Yes, Partial)
or resulting in a not guilty
determination need to be
maintained in the system,
but not reflected on the
offender's conduct
summary.
The screen will be filtered such that it
will not show dismissed or not guilty
conduct records.
Summary Screen. The
screen will not display
records where the case was
dismissed or the offender
was found not guilty.
Data Elements:
Reference CD.4
CD.10
report on all pertinent
data related to an
offender's conduct
incident and offense.
Partial
Adult Conduct
Court Docket Form - Formal/Conduct
Hearing:
1. Daily summary sent out to pertinent
personnel.
2. Forwarding notification on a need to
now basis.
3. Search by day
4. Provide the following report:
 Who they saw,
 What happened
 What has been scheduled,
 Where they are at
 Are they in transit
~Reference the Conduct Daily Docket
Report
Juvenile Conduct
~Reference CD.1
The Incident (PBS) Report contains all
key and pertinent data to not only drive
Incidents
ADMIN - Alerts & Notifications
ADMIN – Lookup – Assaults
ADMIN – Lookup - Suicidal Behavior
ADMIN – Lookup- Property
ADMIN – Lookup- Misconduct
ADMIN – Lookup- Miscellaneous
ADMIN – Lookup – Confinement
ADMIN – Lookup – Seen By Medical
ADMIN – Lookup- Restraint
ADMIN – Lookup- Injured Person
ADMIN – Lookup- Injury
Adult Conduct
Report to be created to
meet requirements.
Reference the Conduct
Daily Docket Report.
Juvenile Conduct
Modify the Incident
Information Screen to meet
the PBS Report Data
elements.
Data Elements:
1. PbS Incident No
2. Date Logged in PbS
Web Site
3. Notification of Officials
a. Officials
b. Date
c. Time
4. Youth Involved
a. Youth

Page 15 of 132 0731/2014
Gap Exists?
(Yes, Partial)
out the Incidents but to be leveraged to
determine functionality business flow.
Alert Configured for the Incident Report
– Should go to Shift Supervisors
b. Ethnicity(RACE)
c. Unit
d. Conduct Report
Issued
5. Assaults
6. Suicidal Behavior
7. Property
8. Misconduct
9. Miscellaneous
10. Confinement
11. Seen By Medical
12. Isolation
13. Segregation
14. Restraint
a. Youth
b. Type Used
15. Isolation Youth
a. Youth
b. Room
c. Date In
d. Date Out
e. Time In
f. Time Out
16. Medical
a. Youth
b. Date
c. Staff Name
d. Time Seen
e. Reason for Exam

Page 16 of 132 0731/2014
Gap Exists?
(Yes, Partial)
17. Injury Youth
a. Youth
b. Injured Person
c. Injury
Shift Supervisor Alert
Create alert to Shift
Supervisor once the
Incident Report has been
entered and completed in
the system.
Create Lookup -
Assaults
Data Elements:
1. Name
2. Abbreviation
3. Description
Create Lookup -
Suicidal Behavior
Data Elements:
1. Name
2. Abbreviation
3. Description
Create Lookup -
Property

Page 17 of 132 0731/2014
Gap Exists?
(Yes, Partial)
Data Elements:
1. Name
2. Abbreviation
3. Description
Create Lookup -
Misconduct
Data Elements:
1. Name
2. Abbreviation
3. Description
Create Lookup -
Miscellaneous
Data Elements:
1. Name
2. Abbreviation
3. Description
Create Lookup -
Confinement
Data Elements:
1. Name
2. Abbreviation
3. Description

Page 18 of 132 0731/2014
Gap Exists?
(Yes, Partial)
Create Lookup –
Seen By Medical
1. Name
2. Abbreviation
3. Description
Create Lookup -
Restraint
Data Elements:
1. Name
2. Abbreviation
3. Description
Create Lookup -
Injured Person
Data Elements:
1. Name
2. Abbreviation
3. Description
Create Lookup -
Injury

Page 19 of 132 0731/2014
Gap Exists?
(Yes, Partial)
Data Elements:
1. Name
2. Abbreviation
3. Description
CD.11
shall provide notifications
to appropriate staff of
conduct hearing and
results within a time
frame specified by DOC
policy.
Yes
Conduct alerts/notification
conditions:
1. Offender Conduct Entered into the
System:
a. This indicates that an Offender
Conduct Report has been
received.
b. Alert to notify Case Manager
and Hearing Officer that a
Conduct Hearing requires
scheduling.
2. Seven (7) days after Conduct
Report Received Date, if a Conduct
Hearing has not been scheduled
and held, trigger alert/notification to
Case Manager and Hearing Officer
to reschedule or dismiss.
ADMIN - Alerts & Notifications
Add 2 Offender Conduct
Alerts/Notifications
CD.12
shall provide a reference
table to support a
dictionary of charges in
the DOC conduct policy.
Yes
The creation and configuration of a
Lookup for the list of Conduct Codes
used by DOC for documenting offender
conduct.
ADMIN - LOV – Conduct Code
Create Lookup –
Conduct Code
Data Elements:
1. Class
2. Number
3. Abbreviation
4. Description
5. Classification

Page 20 of 132 0731/2014
Gap Exists?
(Yes, Partial)
6. Effective Date Start
7. Effective Date End

Page 21 of 132 0731/2014
2.13.2 Overall Design Diagram for the Functional Component
Component Menu
Incident Search
Information
Incident Search
Results Summary
Incident
Information
Use this flow to create a new
incident using Incident Search,
Incident Search Results Summary
and Incident Information
Incident Search
Information
Incident Search
Results Summary
Incident
Information
Use this flow to update an existing
incident using Incident Search,
Incident Search Results Summary
and Incident Information
Conduct
Summary
Use this flow to review the history of
Conduct Reports received by an offender
during the current commitment period
Conduct
Summary
Conduct
Summary
Conduct
Information
Use this flow to create a new Conduct
Report using Conduct Summary and
Conduct Information
Conduct
Information
Use this flow to update an existing Conduct
Report using Conduct Summary and
Conduct Information
Conduct Hearing
Summary
Use this flow to review the history of hearings
and sanctions received by an offender during
the current commitment period
Conduct Hearing
Summary
Conduct Hearing
Summary
Conduct
Information
Use this flow to create a new hearing or sanction
for the offender’s current Conduct Report using
Conduct Summary and Conduct Information
Conduct
Information
Use this flow to update an existing hearing
or sanction using Conduct Summary and
Conduct Information
Conduct
Information
Use this flow to review, edit and
add more hearings to the offender’s
most recent Conduct Report
Figure 1 – Overall Diagram of Functional Component
2.13.3 Description of the Design Diagram
The design diagram begins with the listing of the menu options available in TOMS. The
first menu item, Incidents opens up the Incident Search screen where the user can
search for incidents by entering the search criteria and clicking Search. The Incident
Search Summary screen displays all of the incidents that met the search criteria. By
clicking New, the system opens a new Incident Information screen for the user to a new
incident. If, the user clicks the Edit icon on a particular incident, the system displays the
selected incident and allows the user to modify it.
The Conduct Summary sub-menu item opens the Conduct Summary screen where the
user can view all of the conduct reports for an offender that occurred during an
offender’s incarcerated duration except those which were dismissed or the offender was

Page 22 of 132 0731/2014
found not guilty. By selecting the new button, the system opens a new Conduct
Information screen for the user to add a new conduct report. If the user selects the Edit
icon for a particular conduct report, the system displays the conduct report to the user in
an editable mode.
The Conduct Hearing Summary sub-menu item opens the Conduct Hearing Summary
screen where the user can view all of the hearings and related sanctions for an offender
that occurred during an offender’s incarcerated duration except those which were
dismissed or the offender was found not guilty. By selecting the new button, the system
opens the most recent Conduct Information screen for the user to add a new hearing,
appeal or sanction. If the user selects the Edit icon for a particular hearing, the system
displays the related conduct report to the user in an editable mode.
The Conduct Information sub-menu item opens the most recent Conduct Information
screen for the user to review, edit or add more hearings, appeals or sanctions.
20141110 – Per IDOC Feedback dated, 10/08/2014, “Offender Current Commitment Periods
and Previous Commitment Periods, if any, will be appropriately displayed to screen by
leveraging the SQL’s Default Descending Sort Pattern, by Start and End Dates”.

Page 23 of 132 0731/2014
2.13.4 Menu Being Updated
2.13.4.1 Menu Navigation
Figure 2 – Conduct Menu

Page 24 of 132 0731/2014
2.13.4.2 Data Elements and Behavior
Element Name
Element
Type
Description
Possible Values and
User Interaction
Req
Incidents & Grievances Menu item
The item in the menu bar that is the root for all
Grievance, Incident and Conduct Menu Items
Click to open the next
level menu items
N/A
Grievances Menu item
The menu item used to navigate to the
Grievances Search Information screen.
Click to open the
Grievances Search
Information screen
N/A
Incidents Menu item
The menu item used to open the Incident
Search Information screen
Click to open the
Incident Search
Information screen
N/A
Conduct Menu item
The menu item used to open the Conduct
submenu
Click to open the
Conduct sub-menu
N/A
Conduct Summary Sub-menu item
The sub-menu item used to open the Conduct
Summary screen
Click to open the
Conduct Summary
screen for the
selected user
N/A
Conduct Hearing Summary Sub-menu item
Hearing Summary screen
Click to open the
Conduct Hearing
Summary screen for
the selected user
N/A
Conduct Information Sub-menu item
Information screen
Click to open the
Conduct Information
screen for the
selected user’s most
current conduct
N/A

Page 25 of 132 0731/2014
2.13.4.3 Use Cases
The Offender Conduct Menu Navigation provides an end user the means to navigate
and utilize all aspects and functionality specific to this module. Use Cases have been
identified and described within each pertinent document section below. What follows is
a tabularized format that links to each section by:
1. Menu Element
2. Submenu Element
3. Screen
4. Use Case(s)
It has been provided in this fashion to provide clarity and avoid informational confusion.
Menu Element Submenu Element Screen Use Case(s)
Incidents Incident Information Use Cases
Conduct Conduct Summary Conduct Summary Use Cases
Conduct Hearing Summary Conduct Hearing Summary Use Cases
Conduct Information Conduct Information Use Cases
New Conduct Information Use Cases

Page 26 of 132 0731/2014
2.13.4.4 Error Handing
This section provides a detailed overview for the Offender Conduct Error Handling, catered towards future state. It will
depict Error Handling Specific to each Offender Conduct Screen, the condition or action taken, within the TOMS Offender
Management System Application, the Type of Error plausibly encountered, and the Application Expected Results.
Condition Type of Error Expected Results
1
End user navigates to the
Incident Information
Screen
Displays a Blank Screen
End user to not only be redirected to the Incident Information Screen but
painted to the screen as well., The following data should be painted to the
screen:
- Incident Date/Time
- Status
- Incident No
- PbS Incident No
- Date Logged in PbS Web Site
- Incident Location
- Work Location
- Incident Type
- Use of Force
- Notification of Officials
a. Officials
b. Date
c. Time
- Clients Involved
a. Client No.
b. Client Name
c. Client Location
d. Client Involvement
e. Mental Health Level
- Youth Involved
a. Name

Page 27 of 132 0731/2014
b. Number
c. Age
d. Ethnicity (RACE)
e. Conduct Report Issued
f. Unit
- Staff Involved
a. Employee No.
b. Employee Name
- Assaults
- Suicidal Behavior
- Property
- Misconduct
- Miscellaneous
- Confinement
- Seen by Medical
- Isolation
- Segregation
- Restraint
a. Youth
b. Restraint Type Used
- Isolation
a. Youth
b. Isolation Room
c. Date In
d. Date Out
e. Time In
f. Time Out
- Medical
a. Youth
b. Date

Page 28 of 132 0731/2014
c. Start Name
d. Time Seen
e. Reason for Exam
- Injury
a. Youth
b. Injured Person
c. Injury Source
- Incident Description
- Comments
2
Conduct Summary
Screen
End user to not only be redirected to the Conduct Summary Screen but painted
to the screen as well., The following data should be painted to the screen:
- Case Number
- Class (CLS)
- Code
- Description
- Offense Date
- Report Date
- Hearing Date
3
Conduct Hearing
Summary Screen
End user to not only be redirected to the Conduct Hearing Summary Screen
but painted to the screen as well The following Conduct Data should be painted
to the screen:
- Date
- Class
- Code
- Description
- Result
- Recommended (R)
- Imposed (I)
- Suspended (S)

Page 29 of 132 0731/2014
- Enforced (E)
5
Conduct Information
Screen
End user to not only be redirected to the Conduct Information Screen but
painted to the screen as well. The following Conduct Data should be painted to
the screen
- Incident Date
- Class
- Date Report Received
- Conduct
- Case Number
- Assault Victim
- Facility
- Thrown Substance
- Housing
- Reporting Person
- Range
- Plea
- Location
- Prehearing Segregation
- Event
- Date
- Effective Date
- End Date
- Facility
- Results
- Value
- Actions
- Authorized By
- Current Credit Class
- Current ECT

Page 30 of 132 0731/2014
6
Conduct Information
Screen – New
End user to not only be redirected to the Conduct Information Screen but
painted to the screen as well. The following Conduct Data should be painted to
the screen
- Incident Date
- Class
- Conduct
- Case Number
- Assault Victim
- Facility
- Thrown Substance
- Housing
- Reporting Person
- Range
- Plea
- Location
Prehearing Segregation

Page 31 of 132 0731/2014
2.13.5 Incident Information
2.13.5.1 Incident Information Screen
Figure 3 – Incident Information - Top

Page 32 of 132 0731/2014
Figure 4 – Incident Information - Bottom

Page 33 of 132 0731/2014
Element Name
Element
Type
Description
Possible Values and
User Interaction
Req
Incident Date Date field with Calendar icon Date of Incident occurrence
User – supplied
Can be entered
directly or selected
from Calendar icon.
Yes
Incident Time Time field with Clock icon Time of Incident occurrence
User – supplied
Can be entered
from Clock icon.
Yes
Status Dropdown Incident status either Active or Inactive
User-supplied or LOV
Loader
possible values are:
LOV
Yes
Incident No Text The IDOC Incident tracking number User – supplied No
Incident Type Dropdown The Type of Incident being reported
User-supplied or LOV
Loader
LOV
Yes
User of Force Radio Buttons Whether a use of force was evident or not User – supplied N/A
PbS Incident No Text
The tracking number supplied by the PbS web
site
User – supplied No
Date Logged in PbS Web Site Date field with Calendar icon
The date that the incident was reported to the
PbS web site
User – supplied
Can be entered
from Calendar icon.
No
Incident Location Dropdown
Where the incident occurred with regards to
the facility
User – supplied No
Work Location Dropdown
The work location or facility where the incident
occurred.
User – supplied Yes
Save Button Saves the current data set Click to save N/A

Page 34 of 132 0731/2014
Element Name
Element
Type
Description
Possible Values and
User Interaction
Req
Cancel Button
Cancel the current edits and return to the
previous screen
Click to cancel N/A
Notification of Officials
Grid Row Display only
Cell – Check Checkbox Used to select the current row
Click to select the
current row
N/A
Cell – Edit Edit icon
Used to edit the selected row of Notification of
Officials row
Click to edit the
selected row
N/A
Cell – Officials Text The official who was notified Display only N/A
Cell – Date Text The date that the official was notified Display only N/A
Cell – Time Text The time that the official was notified Display only N/A
Official(s) Textbox with finder icon Used to select the officials who were notified User - supplied N/A
Date Date field with Calendar icon The date that the official was notified
User – supplied
Can be entered
from Calendar icon.
N/A
Time Time field with clock icon The Time that the official was notified User - supplied N/A
Add Button
Add a row to the current grid based upon the
values contained in the controls.
Click to add grid row N/A
Remove Button Removes the row that is currently selected Click to remove N/A
Clients Involved
Click to select the
current row
N/A
Used to edit the selected row of Client
Involved data
Click to edit the
selected row
N/A
Cell – Client No. Text The Client Number Display only N/A
Cell – Client Name Text The Client Name Display only N/A

Page 35 of 132 0731/2014
Element Name
Element
Type
Description
Possible Values and
User Interaction
Req
Cell – Client Location Text The Client Location Display only N/A
Cell – Client Involvement Text Text Client Involvement Display only N/A
Cell – Mental Health Level Text The Client Mental Health Level Display only N/A
Client No. Dropdown The client that was involved in the incident
User – supplied
Possible values are
Client Lookup
No
Add Button
Youth Involved
Click to select the
current row
N/A
Used to edit the selected row of PBS Youth
Involved data
Click to edit the
selected row
N/A
Cell – Name Text The name of the youth involved in the incident Display only N/A
Cell – Number Text
The IDOC Number of the youth involved in the
incident
Display only N/A
Cell – Age Text The age of the youth involved in the incident Display only N/A
Cell – Ethnicity Text Text box that holds the selected ethnicity Display only N/A
Cell – Conduct Report Issued Text
Displays whether or not a Conduct Report
was issued
Display only N/A
Cell – Unit Text
Displays the unit where the incident took
place if entered by the user
Display only N/A
Youth Textbox with finder icon The youth that was involved in the incident User - supplied No
Ethnicity Dropdown The ethnicity of the youth involved.
User – supplied
Possible values are
RACE Lookup
No
Unit Textbox The unit location where the incident occurred User- supplied No

Page 36 of 132 0731/2014
Element Name
Element
Type
Description
Possible Values and
User Interaction
Req
Conduct Report Issued - Yes Radio Button
Indicates that there was a conduct report
issued for the incident
User - supplied No
Conduct Report Issued - No Radio Button
Indicates that there was not a conduct report
issued for the incident
User – supplied
Can be entered
from Clock icon
No
Add Button
Staff Involved
Click to select the
current row
N/A
Involved data
Click to edit the
selected row
N/A
Cell – Employee Number Text The Staff Number Display only N/A
Cell – Employee Name Text The Staff Name Display only N/A
Employee Name Dropdown The staff that was involved in the incident
User – supplied
Possible values are
Staff Lookup
No
Add Button
Assaults Multi-select list box
The types of assaults that the youth may have
committed
User-supplied
Lookup
No
Suicidal Behavior Multi-select list box Lists whether the youth was suicidal
User-supplied
Lookup – Suicidal,
Suicidal Behavior
No

Page 37 of 132 0731/2014
Element Name
Element
Type
Description
Possible Values and
User Interaction
Req
Property Multi-select list box
The types of property actions the youth may
have taken
User-supplied
Lookup
No
Misconduct Multi-select list box
The types of misconduct that the youth may
have committed
User-supplied
Lookup
No
Miscellaneous Multi-select list box
The types of miscellaneous acts the youth
may have committed
User-supplied
Lookup
No
Confinement Multi-select list box
Lists the type of confinement used on a youth
if any.
User-supplied
Lookup
No
Seen By Medical Multi-select list box
List the type of individual that needed medical
care if any
User-supplied
Lookup
No
Isolation - Yes Radio button
Indicates that someone was placed in
isolation
User-supplied No
Isolation - No Radio button Indicates that no one was placed in isolation User-supplied No
Restraint
Click to select the
current row
N/A
Involved data
Click to edit the
selected row
N/A
Cell – Name Text The name of the youth who was restrained Display only N/A
The IDOC Number of the youth that was
restrained
Display only N/A
Cell – Restraint Type Used Text
The type of restraint that was used to restrain
the youth
Display only N/A
Youth Textbox with finder icon The youth that was restrained User - supplied No

Page 38 of 132 0731/2014
Element Name
Element
Type
Description
Possible Values and
User Interaction
Req
Restraint Type Used Dropdown
The type of restraint that was used on the
youth
User – supplied
Possible values are
lookup
No
Add Button
Isolation
Click to select the
current row
N/A
Involved data
Click to edit the
selected row
N/A
Cell – Name Text The name of the youth placed in isolation Display only N/A
The IDOC Number of the youth placed in
isolation
Display only N/A
Cell – Isolation Room Text
The room where the youth was placed in
isolation
Display only N/A
Cell – Date In Text The date the youth was placed in isolation Display only N/A
Cell – Time In Text The time that the youth was placed in isolation Display only N/A
Cell – Date Out Text
The date that the youth was removed from
isolation
Display only N/A
Cell – Time Out Text
The time that the youth was removed from
isolation
Display only N/A
Youth Textbox with finder icon The youth that was placed in isolation User - supplied No
Isolation Room Textbox The room where the youth was isolated User - supplied No
Date In Date field with Calendar icon
The date that the youth was placed in
isolation
User – supplied
Can be entered
from Calendar icon.
No

Page 39 of 132 0731/2014
Element Name
Element
Type
Description
Possible Values and
User Interaction
Req
Time In Time field with clock icon The time that the youth was placed in isolation
User – supplied
Can be entered
from Clock icon
No
Date Out Date field with Calendar icon
The date that the youth was removed from
isolation
User – supplied
Can be entered
from Calendar icon.
No
Time Out Time field with clock icon
The time that the youth was removed from
isolation
User – supplied
Can be entered
from Clock icon
No
Add Button
Medical
Click to select the
current row
N/A
Involved data
Click to edit the
selected row
N/A
Cell – Name Text
The name of the youth that needed medical
attention
Display only N/A
The IDOC Number of the youth that required
medical attention
Display only N/A
Cell – Date Text
The date that the youth was seen by medical
personnel
Display only N/A
Cell – Staff Name Text
The name of the medical staff person that
attended to the youth
Display only N/A
Cell – Time Seen Text
The time that the youth was seen by medical
personnel
Display only N/A

Page 40 of 132 0731/2014
Element Name
Element
Type
Description
Possible Values and
User Interaction
Req
Cell - Reason For Exam Text
The reason that the youth was seen by
medical, personnel
Display only N/A
Youth Textbox with finder icon The youth that needed medical attention User - supplied No
Date Date field with Calendar icon
The date that the youth was seen by medical
personnel
User – supplied
Can be entered
from Calendar icon.
No
Staff Name Textbox
The name of the medical staff person that
attended to the youth
User - supplied No
Time Seen Time field with clock icon
The time that the youth was seen by medical
personnel
User – supplied
Can be entered
from Clock icon
No
Reason for Exam Textbox
The reason that the youth was seen by
medical, personnel
User - supplied No
Add Button
Injury
Click to select the
current row
N/A
Involved data
Click to edit the
selected row
N/A
Cell - Name Text The name of the youth that injured someone Display only N/A
Cell - Number Text
The IDOC Number of the youth that injured
someone
Display only N/A
Cell – Injured Person Text The type of person that the youth injured Display only N/A
Cell – Injury Source Text The source of the injury caused by the youth Display only N/A

Page 41 of 132 0731/2014
Element Name
Element
Type
Description
Possible Values and
User Interaction
Req
Youth Textbox with finder icon The youth caused an injury to another person User - supplied No
Injured Person Dropdown
The type of person that was injured by the
youth
User – supplied
Possible values are
lookup
No
Injury Source Dropdown The source of the injury inflicted by the youth
User – supplied
Possible values are
lookup
No
Add Button
Incident Description Textarea
Free form text area to enter other specifics to
the Incident Occurrence
User - supplied No
Comments Textarea
Free form text area to enter other specifics to
the Incident Occurrence
User - supplied No
Save Button Saves the current data set Click to save N/A
Cancel Button
Cancel the current edits and return to the
previous screen
Click to cancel N/A

Page 42 of 132 0731/2014
2.13.5.3 Use Cases
2.13.5.3.1 Add New Incident
Users: Custody Staff, Case Manager, Supervisor
Preconditions: The user is logged into the system, and can be on any screen.
Post Conditions: A new Incident Report record has been created.
Trigger: One of more youths participated in an incident that needs to be recorded in the
system.
Normal Flow:
1. The user selects Incident from the INCIDENTS & GRIEVANCES menu.
2. The system displays the Incident Search Information screen to the user.
3. The user enters the search criteria, such as Last Name, first Name, and IDOC
Number into the screen and clicks Search.
4. The system displays the Incident Search Results Summary screen to the user
with any results populating the grid.
5. The user selects New.
6. The system displays a new Incident Information screen to the user.
7. The user adds the minimum required fields to the record, which are Incident
Date/Time, Duty Supervisor Notification Date/Time, Work Location, Status, and
Incident Type. The user then adds any data that is not required such as:
a. Assaults
b. Suicidal Behavior
c. Property
d. Misconduct
e. Miscellaneous
f. Confinement
g. Seen By Medical
h. Isolation (Yes/No)
i. Segregation
j. PbS Youth Involved Record
i. The user adds a PbS Youth Involved record by looking up the youth
with a finder control, selecting the Ethnicity from a dropdown, typing
the unit into a textbox, and selecting the Add button.
k. Restraint Record
i. The user adds a Restraint Record by looking up the youth with a
finder control, selecting the Restraint Type Used from the
dropdown, and selecting the Add button.

Page 43 of 132 0731/2014
l. Isolation Record
i. The user adds an Isolation record by looking up the youth with a
finder control, typing in the Isolation room, selecting the Date In,
selecting the Time In, and selecting the Add button.
m. Medical Record
i. The user add a Medical record, by looking up the youth with a
finder control, entering the Date, entering the Staff Name in a
textbox, entering the Time Seen, entering the Reason for Exam in a
textbox, and selecting the Add button.
n. Injury Record
i. The user adds an Injury record by looking up the youth in a finder
control, selecting the Injured Person from a dropdown, selecting the
injury Source from a dropdown, and selecting the Add button.
o. Notifications
i. PbS Incident Tracking #
ii. Date Logged in PbS Web Site.
The user clicks Save to record all of the data.
8. The system calculates the Incident Number, saves all entered data, and displays
the Incident Search Information screen to the user.
9. The use case ends
Alternate Flow
A1. At step 7 of the normal flow, the user selects cancel instead of Save.
A2. The system prompts the user to verify that he or she would like to cancel.
A3. The user selects OK.
A4. The system discards all changes and returns the user to the Incident Search
Information Screen.
B1. If at step A3 of Alternate Flow A, the user selects Cancel, the system will return to
step 6 of the Normal Flow and show all changes made by the user at step 7 of the
Normal Flow.
2.13.5.3.2 Edit Incident Report
Users: Custody Staff, Case Manager, Supervisor
Preconditions: The user is logged into the system, and can be on any screen.
Post Conditions: A previous Incident Report record is updated to show the changes
entered by the user.
Trigger: The user needs to edit an Incident Report previously added to the system.

Page 44 of 132 0731/2014
Normal Flow:
1. The user selects Incident from the INCIDENTS & GRIEVANCES menu.
2. The system displays the Incident Search Information screen to the user.
3. The user enters the search criteria, such as Last Name, first Name, and IDOC
Number into the screen and clicks Search.
4. The system displays the Incident Search Results Summary screen to the user
with any results populating the grid.
5. The user selects the edit icon for the Incident Report he or she would like to edit.
6. The system displays the Incident Information screen to the user in a format
where every item is editable except the incident number.
7. The user edits, adds or removes items from the Incident Information screen, and
selects save.
8. The system saves the changes that the user made to the Incident record, and
displays the Incident Search Information screen to the user.
9. The use case ends
A4. The system discards all changes and returns the user to the Incident Search
Information Screen.
Normal Flow.
2.13.5.4 Process Input(s)
2.13.5.4.1 Incident Number Current Value
The current incident number provides the base for the next incident number
2.13.5.5 Processes
2.13.5.5.1 Calculate Incident Number
The first time an Incident Report is saved, the system calculates and stores the Incident
Number. The Incident Number starts with the three (3) letter abbreviation for the facility.
Next comes two (2) digits for the current year. Two (2) digits for the current month come
next. The number is completed by counting the number of incidents at the facility in the
current month by starting at 0001 and adding one (1) for each new incident, so the next
value would be 0002. The whole number would be IYC 14 07 0015 for the fifteenth
incident at IYC during July 2014.

Page 45 of 132 0731/2014
2.13.5.5.2 Send Supervisor Notification
The system will send a notification to the supervisor notifying him/her that an incident
has occurred and an incident report has been created.

Page 46 of 132 0731/2014
This section provides a detailed overview for the Incident Information Error Handling, catered towards future state. It will
depict Error Handling Specific to each Incident Information Screen, the condition or action taken, within the TOMS
Offender Management System Application, the Type of Error plausibly encountered, and the Application Expected
Results.
1
Incidents Information
Screen by selecting the
INCIDENTS &
GRIEVANCES Menu and
Incident Menu Item.
The end user is
redirected to the Incidents
content of the screen
paints successfully to the
monitor.
The end user is redirected to the Incidents
Information Screen.
The contents of the screen paints successfully to
the monitor however one of the following data
elements have not been successfully populated:
Dependent upon the missing Incidents Information
Screen Data Element(s), this may result in one of
the following Error(s):
1. “Officials Not Found“
2. “Client Number Not Found”
3. “Youth Not Found”
4. “Ethnicity Not Found”
5. “Employee Name Not Found”
6. “Assaults Not Found”
7. “Suicidal Behavior Not Found”
8. “Property Not Found”
9. “Misconduct Not Found”
10. “Miscellaneous Not Found”
11. “Confinement Not Found”
12. “Seen by Medical Not Found”
14. “Restraint Type Used Not Found”
17. “Injured Person Not Found”
18. “Injury Not Found”
In regards to Data Not Found – These are the Expected
Results. In this event please have your administrator
create the necessary LOV/LookUps within the ADMIN
Module beneath LOV & LookUp Admin Summary.
The contents of the screen paint successfully to the
monitor. The following data elements have been
successfully populated:
1. Officials
2. Client No.
3. Youth
4. Ethnicity
5. Employee
6. Assaults
7. Suicidal Behavior
8. Property
9. Misconduct
10. Miscellaneous
11. Confinement
12. Seen by Medical
13. Youth
14. Restraint Type Used
15. Youth
16. Youth
17. Injured Person
18. Injury

Page 47 of 132 0731/2014
Dependent upon the missing Information Screen
Data Element(s) Grid Row(s), this may result in
the following Errors:
1. “The following data elements were not found
for the Notifications of Officials: Official, Date,
and Time.”
for the Clients Involved: Client Number, Client
Name, Client Location, Client Involvement,
and Mental Health Level.”
for the Youth Involved: Name, Number, Age,
Ethnicity, Conduct Report Issued, and Unit.”
for the Staff Involved: Employee Number,
Employee Name.”
for the Restraint: Name, Number, and
Restraint Type Used.”
for the Isolation: Name, Number, Isolation
Room, Date In, Time In, Date Out, and Time
Out.”
for the Medical: Name, Number, Date, Staff
Name, Time Seen, and Reason for Exam.”

Page 48 of 132 0731/2014
for the Injury: Name, Number, Injured Person,
and Injury Source.”
2
INCIDENTS &
GRIEVANCES Menu and
Incident Menu Item.
End user alters one or all
of the data elements
found within the Incidents
Information Screen.
End user proceeds to
click the Save Command
Button
Database Integrity Error andor Database Submit
Error is thrown.
“Data Saved” should display in a Blue-Font in the upper
left-hand corner of the screen.
3
INCIDENTS &
GRIEVANCES Menu and
Incident Menu Item.
Information Screen;
however forgets to enter
one of the required fields
and proceeds to Save the
Incident.
The end user is redirected to the Incidents
Information Screen The contents of the screen
paints successfully to the monitor.
Dependent upon the missing Incidents Information
Data Element(s), this may result in one of the
following Error(s):
1. “Incident Date and Time are Required”
2. “Status is Required”
3. “Incident Type is Required”
4. “Work Location is Required”
5. “Client and/or Youth is Required”
6. “Incident Number is Required”
In regards to Data Elements Required – These are the
Expected Results. In this event please the end user will
be expected to enter all required information prior Saving
and Submitting the Offender Incident to the Database
Resource.

Page 49 of 132 0731/2014
4
INCIDENTS &
GRIEVANCES Menu and
Incident Menu Item.
Information Screen.
click the Cancel/Back
Command Button
End user altered Data Element Values are
retained in the Browser Session History.
Session History is not maintained and does not
proceed back to the previously visited end user
screen.
End user altered Data Element Values are flushed from
Browser Session History.
Session History is maintained and proceeds to redirect to
the previously visited end user screen.

Page 50 of 132 0731/2014
2.13.6 Conduct Summary
2.13.6.1 Conduct Summary Screen
Figure 5 – Conduct Summary

Page 51 of 132 0731/2014
Element Name
Element
Type
Description
Possible Values and
User Interaction
Req
(none) Edit icon
Hyperlink to the Conduct Information screen
for the selected entry
Click to go to the
conduct Information
screen for the
selected entry
N/A
Case Number Text The Case Number for the particular conduct Display only N/A
Class (CLS) Text The Class for the Offense Code Display Only N/A
Code Text The Code representing the Offense Display Only N/A
Description Text
The Description of the Offense related to the
Conduct
Display Only N/A
Offense Date Text The date that the Offence occurred Display only N/A
Report Date Text The date that the conduct Report was written Display only N/A
Hearing Date Text
The date that the Hearing took place for the
given Conduct Report
Display Only N/A
New Button
The button to navigate to a new Conduct
Information screen
Click to open a new
Conduct Information
screen
N/A

Page 52 of 132 0731/2014
2.13.6.3 Use Cases
View Conduct History
Users: Custody Staff, Case Manager, Supervisor, Hearing Officer, Screening Officer,
Facility Head
Preconditions: The user is on an offender specific screen.
Post Conditions: None.
Trigger: The user wants to review the offender’s conduct history.
Normal Flow:
1. The user selects Conduct Summary from the Conduct menu.
2. The system displays the Conduct Summary screen to the user populated with all
of the Conducts from the offender’s during an offender’s incarcerated duration.
3. The user views the conduct history.
4. The use case ends.
2.13.6.3.1 Edit Conduct Report
Users: Custody Staff, Case Manager, Supervisor, Hearing Officer, Facility Head
Post Conditions: A current Conduct Report record has been modified.
Trigger: The user needs to update the information on a Conduct Report.
Normal Flow:
7. The user selects the edit icon for the Conduct report to be edited.
8. The system displays the Conduct Information screen to the user with the
selected Conduct Report populated.
9. The user performs any edits desired and the user then selects SAVE.
10.The system saves the Conduct Report including changes made by the user.
11.The system displays the Conduct Summary screen to the user.
12.The use case ends.

Page 53 of 132 0731/2014
A4. The system discards all changes and returns the user to the Conduct Summary
Screen.
Normal Flow.
2.13.6.3.2 Dismiss Conduct Report
Users: Supervisor, Hearing Officer, Screening Officer
Post Conditions: A DISMISSED Event is added to the current Conduct Report.
Trigger: The current Conduct Report has been dismissed.
Normal Flow:
3. The user selects the edit icon for the Conduct report to be dismissed.
5. The user selects DIMISSED from the Event dropdown. The user enters the date
the Conduct Report was dismissed in the Date field. The user selects the Facility
where the offender is currently. The user selects either the Screening Officer or
Facility Head from the Authorized by dropdown, and then selects Add.
6. The system adds the DISMISSED Event to the Events grid and redisplays the
Conduct Information screen to the user.
7. The user selects SAVE.
8. The system saves the Conduct Report including the new DISMISSED Event
record.
9. The system displays the Conduct Summary screen to the user, but the conduct
should no longer appear on the screen because it was dismissed.
A1. At step 5 of the normal flow, the user selects cancel instead of Add.

Page 54 of 132 0731/2014
Screen.
Normal Flow.
C1. At step 7 of the normal flow, the user selects cancel instead of Save.
C2. The system prompts the user to verify that he or she would like to cancel.
C3. The user selects OK.
C4. The system discards all changes and returns the user to the Conduct Summary
Screen.
D1. If at step C3 of Alternate Flow C, the user selects Cancel, the system will return to
Normal Flow.
2.13.6.3.3 Add Hearing to Conduct Report
Users: Supervisor, Hearing Officer, CAB, UTDC
Post Conditions: A HEARING Event is added to the current Conduct Report.
Trigger: The current Conduct Report has been dismissed.
Normal Flow:
3. The user selects the edit icon for the Conduct Report to which to add the hearing.
5. The user selects HEARING 1 or HEARING 2 from the Event dropdown. The user
enters the date of the hearing in the Date field. The user selects the Facility
where the hearing took place. The user selects GUILTY or NOT GUILTY from
the Results Dropdown. The user selects the Screening Officer, UTDC, CAB or
HEARING OFFICER from the Authorized by dropdown, and then selects Add.
6. The system adds the HEARING Event to the Events grid and redisplays the

Page 55 of 132 0731/2014
8. The system saves the Conduct Report including the new HEARING Event
record.
9. The system displays the Conduct Summary screen to the user.
Screen.
Normal Flow.
Screen.
Normal Flow.
2.13.6.3.4 Add Appeal
Users: Supervisor, Hearing Officer, Assistant Superintendent
Post Conditions: An APPEAL Event is added to the current Conduct Report.
Trigger: The offender appealed a Conduct Report, and the user is recording the results
of that appeal.
Normal Flow:
3. The user selects the edit icon for the Conduct report to which to add an appeal

Page 56 of 132 0731/2014
5. The user selects APPEAL 1 or APPEAL 2 from the Event dropdown. The user
enters the date of the appeal in the Date field. The user selects the Facility where
the appeal took place. The user selects the result of the appeal, DENY,
SUSTAIN, or REHEAR. The user selects the appeal actions from the Action
Dropdown, Not Guilty, SANCTION OR OFFENSE, NONE, and then selects Add.
6. The system adds the APPEAL 1 or APPEAL 2 Event to the Events grid and
redisplays the Conduct Information screen to the user.
8. The system saves the Conduct Report including the new APPEAL Event record.
Screen.
Normal Flow.
Screen.
Normal Flow.
2.13.6.3.5 Add Sanction
Users: Hearing Officer, Assistant Superintendent
Post Conditions: A SANCTION(s) Event is added to the current Conduct Report.
Trigger: The offender was found guilty during a hearing or the offender pleaded guilty to
the Conduct.
Normal Flow:

Page 57 of 132 0731/2014
3. The user selects the edit icon for the Conduct report to which to add the sanction.
5. The user selects SANCTION from the Event dropdown. The user enters the date
the sanction was given. The user selects the Effective Date of the Sanction. The
user selects the End Date of the Sanction if appropriate. The user selects the
Facility where the offender is currently. The user selects the desired sanction
from the Results dropdown. The user enters a number or text in the Value
textbox based on the sanction selected. The user selects an action from the
Actions dropdown to determine if the sanction is one of the following:
a. S = Suspend
b. SR = Suspend/Recommend
c. E = Enforce
d. ER = Enforce/Recommend
e. R = Recommend
f. I= Imposed
Once all values are selected, the user selects Add.
6. The system adds the SANCTION Event to the Events grid and redisplays the
7. The user repeats steps 5 and 6 until all sanctions are added.
9. The system saves the Conduct Report including the new SANCTIONS Event
record(s). The system sends a notification based on section 2.13.9.5.3.
10.The system displays the Conduct Summary screen to the user.
Screen.
Normal Flow.

Page 58 of 132 0731/2014
Screen.
Normal Flow.
2.13.6.3.6 Add Credit Class Review Hearing
Users: Hearing Officer, CAB Member, Unit Team Member
Post Conditions: A CREDIT CLASS REVIEW Event is added to the current Conduct
Report.
Trigger: The offender previously had a reduction in Credit Class due to a Conduct
Report. After ninety (90) days a Credit Class Review occurs.
Normal Flow:
3. The user selects the edit icon for the Conduct report to which to add the Credit
Class Review.
5. The user selects CREDIT CLASS REVIEW from the Event dropdown. The user
adds the date that the review took place in the Date field. The user enters the
date the results become effective in the Effective Date field. The user selects the
facility where the offender is currently housed. The user selects the Results of
the Credit Class Review. The user selects an Action from the Actions Dropdown,
I =Imposed or R =Recommend. The user selects Add
6. The system adds the CREDIT CLASS REVIEW Event to the Events grid and
8. The system saves the Conduct Report including the new CREDIT CLASS
REVIEW Event record.

Page 59 of 132 0731/2014
Screen.
Normal Flow.
Screen.
Normal Flow.
2.13.6.3.7 Add Petition to Restore Credit Time Hearing
Users: Hearing Officer, CAB Member, Unit Team Member
Post Conditions: A PETITION TO RESTORE Event is added to the current Conduct
Report.
Trigger: The offender previously lost Earned Credit Time due to a Conduct Report. After
six (6) months the offender can petition to have twenty-five percent (25%) of deprived
time restored up to three times.
Normal Flow:
3. The user selects the edit icon for the Conduct report to which to add the Petition
to Restore Time hearing.
5. The user selects PETITION TO RESTORE from the Event dropdown. The user
adds the date that the offender filed the petition in the Date field. The user enters
the date the results become effective in the Effective Date field. The user selects

Page 60 of 132 0731/2014
the facility where the offender is currently housed. The user enters the number of
days to restore in the Value textbox. The user enters the date that the facility
approved the petition in the End Date field, and the user selects Add
6. The system adds the PETITION TO RESTORE Event to the Events grid and
8. The system saves the Conduct Report including the new PETITION TO
RESTORE Event record.
Screen.
Normal Flow.
Screen.
Normal Flow.
2.13.6.4 Process Input(s)
None.
2.13.6.5 Processes
2.13.6.5.1 Populate the Conduct Summary Grid
The grid contains the Conduct Reports for a specific offender for the during an
offender’s incarcerated duration in reverse chronological order. The grid will not show
Conduct Reports where the Conduct Report was dismissed or the offender was found
not guilty during the hearing or appeal process.

Page 61 of 132 0731/2014
This section provides a detailed overview for the Conduct Summary Error Handling, catered towards future state. It will
depict Error Handling Specific to each Offender Conduct Screen, the condition or action taken, within the TOMS Offender
Management System Application, the Type of Error plausibly encountered, and the Application Expected Results.
1
Incidents Conduct
Summary Screen by
selecting the INCIDENTS
& GRIEVANCES Menu,
the Conduct Menu Item,
and its Conduct Summary
Submenu Item.
The end user is
redirected to the Conduct
Summary Screen. The
monitor.
The end user is redirected to the Conduct
Summary Screen.
The contents of the screen paints
successfully to the monitor however one of
the following data elements have not been
successfully populated:
Dependent upon the missing Information
Screen Data Element(s) Grid Row(s), this
may result in the following Errors:
1. “The following data elements were not
found for Conduct Summary: Case
Number, Class, Code, Description,
Offense Date, Report Date, Hearing
Date”.
End user to not only be redirected to the Conduct Summary
Screen but painted to the screen as well., The following data
should be painted to the screen:
- Case Number
- Class (CLS)
- Code
- Description
- Offense Date
- Report Date
- Hearing Date
2
Incidents Conduct
Summary Screen by
& GRIEVANCES Menu,
Submenu Item.
The end user is
End user to not only be redirected to the Conduct Information
Screen but painted to the screen as well. The following Conduct
Data should be painted to the screen
- Incident Date
- Class
- Conduct
- Case Number

Page 62 of 132 0731/2014
Summary Screen. The
monitor.
Conduct Summary
Screen Grid Row Edit
Icon.
- Assault Victim
- Facility
- Thrown Substance
- Housing
- Reporting Person
- Range
- Plea
- Location
- Event
- Date
- Effective Date
- End Date
- Facility
- Results
- Value
- Actions
- Authorized By
- Current ECT
3
Incidents Conduct
Summary Screen by
& GRIEVANCES Menu,
Submenu Item.
The end user is
Summary Screen. The
monitor.
End user to not only be redirected to the Conduct Information
Screen but painted to the screen as well. The following Conduct
Data should be painted to the screen
- Incident Date
- Class
- Conduct
- Case Number
- Assault Victim
- Facility
- Thrown Substance
- Housing
- Reporting Person

Page 63 of 132 0731/2014
Conduct Summary
Screen New Command
Button.
- Range
- Plea
- Location
- Event
- Date
- Effective Date
- End Date
- Facility
- Results
- Value
- Actions
- Authorized By
- Current ECT
4
Conduct Summary
INCIDENTS &
GRIEVANCES Menu, the
Conduct Menu Item, and
its Conduct Summary
Submenu Item.
The end user is
Summary Screen. The
monitor.
click the Cancel/Back
Command Button
End user altered Data Element Values are
retained in the Browser Session History.
Session History is not maintained and does
not proceed back to the previously visited
end user screen.
End user altered Data Element Values are flushed from
Browser Session History.
Session History is maintained and proceeds to redirect to the
previously visited end user screen.

Page 64 of 132 0731/2014
2.13.7 Conduct Hearing Summary
2.13.7.1 Conduct Hearing Summary Screen
Figure 6 – Conduct Hearing Summary

Page 65 of 132 0731/2014
Element Name Element Type Description
Possible Values and User
Interaction
Req
(none) Edit icon
Hyperlink to the Conduct Information screen for the
selected entry
Click to go to the conduct Information
screen for the selected entry
N/A
Date Text The date that the event took place Display only N/A
Class Text The Class for the Offense Code for a Sanction Display Only N/A
Code Text The Code representing the Offense for a Sanction Display Only N/A
Description Text
1 The description of the offense for a Sanction
2. The text should be “CC Review Effective Date: ”
and the date of the Credit Class Review hearing
event.
3. The text should be “ECT Petition Effective
Date:” and the date of the Petition to Restore Time
Hearing event.
4. The text should be “Appeal 1 Effective Date”
and the date of the first appeal
5 The text should be “Appeal 2 Effective Date:”
and the date of the second appeal.
Display Only N/A
Result Text The result of the Hearing, Appeal, or Sanction, Display only N/A
Recommended (R) Check Box
This item will be checked if the code for the Event
Actions contains an “R”
Display only N/A
Imposed (I) Check Box
Actions contains an “I”
Display only N/A
Suspended (S) Check Box
Actions contains an “S”
Display only N/A
Enforced (E) Check Box
Actions contains an “E”
Display only N/A
New Button
The button navigates to the offender’s current
Conduct Information screen, so that the user can
enter a new Event.
Click to open the offender’s current
Conduct Report
N/A
Back Button
Button to navigate to the last screen the user was
on
Click to navigate to the last screen the
user was on
N/A

Page 66 of 132 0731/2014
2.13.7.3 Use Cases
2.13.7.3.1 Add Hearing via Hearing Summary Screen
Users: Supervisor, Hearing Officer, CAB, UTDC
Post Conditions: A Hearing Event is added to the current Conduct Report.
Trigger: A new hearing was held for the current Conduct Report.
Normal Flow:
1. The user selects Conduct Hearing Summary from the Conduct menu.
2. The system displays the Conduct Hearing Summary screen to the user
populated with all of the Events from the offender’s during an offender’s
incarcerated duration.
4. The system displays the offender’s current Conduct Information screen to the
user with the Conduct Report populated.
5. The user selects HEARING 1 or HEARING 2 from the Event dropdown. The user
enters the date of the hearing in the Date field. The user selects the Facility
where the hearing took place. The user selects GUILTY or NOT GUILTY from
the Results Dropdown. The user selects the Screening Officer, UTDC, CAB or
HEARING OFFICER from the Authorized by dropdown, and then selects Add.
6. The system adds the HEARING Event to the Events grid and redisplays the
8. The system saves the Conduct Report including the new HEARING Event
record.
9. The system displays the Conduct Hearing Summary screen to the user.
Screen.
Normal Flow.

Page 67 of 132 0731/2014
Screen.
Normal Flow.
2.13.7.3.2 Add Appeal via Conduct Hearing Summary Screen
Users: Supervisor, Hearing Officer, Assistant Superintendent
Post Conditions: An APPEAL Event is added to the current Conduct Report.
Trigger: The offender appealed a Conduct Report, and the user is recording the results
of that appeal.
Normal Flow:
1. The user selects Conduct Hearing Summary from the Conduct menu.
2. The system displays the Conduct Hearing Summary screen to the user
populated with all of the Events from the offender’s during an offender’s
incarcerated duration.
4. The system displays the offender’s current Conduct Information screen to the
user with the Conduct Report populated.
5. The user selects APPEAL 1 or APPEAL 2 from the Event dropdown. The user
enters the date of the appeal in the Date field. The user selects the Facility where
the appeal took place. The user selects the result of the appeal, DENY,
SUSTAIN, or REHEAR. The user selects the appeal actions from the Action
Dropdown, Not Guilty, SANCTION OR OFFENSE, NONE, and then selects Add.
6. The system adds the APPEAL 1 or APPEAL 2 Event to the Events grid and
8. The system saves the Conduct Report including the new APPEAL Event record.

20141111_DSD - Offender Conduct

20141111_DSD - Offender Conduct

Recommended

Recommended

More Related Content

What's hot

What's hot (17)

Viewers also liked

Viewers also liked (18)

Similar to 20141111_DSD - Offender Conduct

Similar to 20141111_DSD - Offender Conduct (20)

20141111_DSD - Offender Conduct