Docstoc

Filing for Sole Legal Custody Court

Document Sample
Filing for Sole Legal Custody Court Powered By Docstoc
					                                                             MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                                                              ATTACHMENT C
                                                               MARYLAND ELECTRONIC COURT PROCUREMENT                                                                      Page 1 of 249
                                                                      FUNCTIONAL REQUIREMENTS

                                                       INSTRUCTIONS TO COMPLETE ATTACHMENT - C - AMENDMENT #1


The MDEC functional requirements are presented in the tables that comprise this attachment. They have been grouped by CMS function. The table below provides an overview of
these major groups.
 Section ID      CMS Function                                                                           Functional Description
CII         Case Initiation and         The activities that initiate a case and maintain its index including acceptance and processing of the initial filing, securing case files from public
            Indexing                    view, associated record keeping and reporting, and creation and maintenance of an index for the case.
DRK         Docketing, Record           The activities associated with entering information in the docket, including:
            Keeping                     --That a document has been filed.
                                        --That in some instances, the filed document is the basis for placing a case on the court calendar for hearing or review.
                                        -- What occurred at the hearing or review.
                                        --Securing case data such as notes, documents, specific data fields
SCH           Scheduling                The activities associated with scheduling upcoming events, maintaining and displaying information on scheduled events, and monitoring
                                        adherence to schedules.
DIS           Disposition               The activities associated with disposing a case or defendant in a case, including any type of disposition resulting from a court decision after
                                        jury or nonjury trial, guilty plea, or dismissal.
CMN           Case Management           The activities associated with navigating the system‘s user interface.
              Navigation
CAL           Calendaring               The activities associated with the creation of calendared matters including the generation, maintenance, and, in some instances, distribution of
                                        court calendars for each type of hearing.
CCL           Case Close Function       The activities associated with final closure of a case.
COM           Compliance                The activities associated with the court's monitoring of adherence to sentence and supervision conditions
DGP           Document Generation       The activities associated with generating, distributing, and tracking documents that notify individuals of past and upcoming events and other
              and Processing            court actions.
EFI           Electronic Filing         The activities associated with filing a case or document with the court electronically, including the ability to provide service of filed documents
                                        to other case participants.
EXE           Execution Function        The activities associated with execution of a judgment.
FDP           File, Document, and       The activities associated with:
              Property Management


HAD           Hearings, Adjudication,   The activities associated with reaching a decision in calendared events, recording the results of these events, and notifying the appropriate
              Disposition               persons of court decisions.
INT           Integration               The activities associated with exchanging information with external or partner systems.
MSR           Management and            The reports that provide caseload, case flow, and workload statistics and management information on court operations, finances, and staffing.
              Statistical Reports
FOR           Forms                     The activities associated with building and managing electronic court forms.
BBO           Bail Bonds                The activities associated with tracking of bonds written and the bond writing statuses of bondsmen and sureties.
SCO           Specialty Courts          The activities associated with capturing case activities in support of the Problem Solving Courts programs such as: drug court, mental health
                                        court, family court, etc.
ACC           Accounting                The activities associated with satisfying the court‘s fiduciary responsibilities, including: posting receipt of funds, posting case-related funds to
                                        a case fee record, and posting non-case-related funds to other types of records; maintaining account records; disbursing funds; generating
                                        checks; billing; producing payment agreements; producing notices required for collection activities; reconciling bank accounts; and producing
                                        documents required to satisfy county, state, and federal auditing agencies.


      MDEC Procurement K11-0030-29                                                                                                                                     September 1, 2010
                                                               MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                                                                  ATTACHMENT C
                                                                 MARYLAND ELECTRONIC COURT PROCUREMENT                                                                          Page 2 of 249
                                                                        FUNCTIONAL REQUIREMENTS

                                                        INSTRUCTIONS TO COMPLETE ATTACHMENT - C - AMENDMENT #1


HEA           Hearings                   The activities associated with conducting courtroom proceedings using electronic means, including support for all activities of judicial officers
                                         and clerk personnel.
              Miscellaneous              The activities associated with development, configuration, implementation, documentation, and maintenance of a court CMS.
MIS           Security and Data          The activities associated with ensuring the security, privacy and integrity of the case processing system and it's data.
              Integrity

The Offeror must use the following tables in this attachment to respond to every requirement highlighted in Yellow. Each requirement includes a list of sub-requirements that provide
supporting detail. For each functional requirement highlighted in yellow, the Offeror must indicate one of the following 6 responses in the column labeled ―Response Code‖ for ALL
worksheets in this workbook. The worksheet will automatically fill the response column for the detailed sub-requirements with the response provided in the main requirement highlighted
in yellow. If necessary, the Offeror may amend the automated response code in a sub-requirement.

A – Can be Demonstrated                  Application support for the function can be demonstrated without configuration or customization. No customization or configuration of the
                                         application will be required to implement this function, using the proposed application. (Note that failure to demonstrate this capability when
                                         called upon to do so may be grounds for disqualification from the procurement). No explanation is required.

B – Requires Configuration               Application support for the function can be accomplished with configuration. (Note that failure to demonstrate this capability at the time of
                                         product acceptance testing may be grounds for contract cancellation and penalties). No explanation is required.

C – Future Release                       Application support for the function will be accomplished by a future release of the application. The respondent must identify the specific release and the
                                         date of that release in the comments field. (Note that failure to specify the release and release date would be considered non-responsive and may be
                                         grounds for disqualification from the procurement. Failure to provide the application with this capability on the date specified (and without customization)
                                         may be grounds for contract cancellation and penalties.

D – Requires Customization               Application support for the function can be accomplished with software customization. (Note that failure to demonstrate this capability at the
                                         time of product acceptance testing may be grounds for contract cancellation and penalties). The nature of the customization must be
                                         explained in the comments field. (Note that failure to explain the nature of the customization would be considered non-responsive and may be
                                         grounds for disqualification from the procurement.)

E – Alternative Proposed                 Respondent does not propose to meet this requirement. However, the respondent is proposing an alternative approach to meet the needs of
                                         the courts in Maryland. An explanation is required. and failure to provide that explanation in the comments field would be considered non-
                                         responsive and may be grounds for disqualification from the procurement.

F – Not Proposed                         Application support for the function is not proposed. An explanation is required and failure to provide that explanation in the comments field
                                         would be considered non-responsive and may be grounds for disqualification from the procurement.

In the event that ―Requirement Text‖ of any functional requirement is modified or deleted, the text for that requirement in this RFP (and any subsequent amendment) shall supersede
and replace the text for that requirement in the Offeror‘s proposal. Material modification of a ―Requirement Text‖ field would be considered non-responsive and may be grounds for
disqualification from the procurement.

High level requirements have been decomposed into sub requirements. The sub requirements utilitize a common language and structure.

User Roles
ADMIN USER                               Users responsible for backend system administration and configuration
USER                                     User interacting directly with the system in accomplishing business functions

      MDEC Procurement K11-0030-29                                                                                                                                           September 1, 2010
                                                        MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                                                             ATTACHMENT C
                                                          MARYLAND ELECTRONIC COURT PROCUREMENT                                                                     Page 3 of 249
                                                                 FUNCTIONAL REQUIREMENTS

                                                 INSTRUCTIONS TO COMPLETE ATTACHMENT - C - AMENDMENT #1


E-FILE USER                        User who creates an electronic submission using an electronic filing service provider
REVIEW CLERK                       User receiving electronic submissions for review prior to acceptance into the court record.


Requirement Semantics
AUTOMATICALLY                      Implies activities that occur without any user intervention. This activity could be associated with a business rule or other condition or it could
                                   represent relationships that should be created between entities without any user action.
MANUALLY                           Infers activities that occur at the explicit direction of the user.
ASSIGN                             Indicates any of the following:
                                   a) The ability to add, view, delete or modify fields based on access permissions and context
                                   c) A field that persists in the database and can be retrieved and updated.
                                   d) Updates to fields that are assigned will be historically logged.
                                   e) Field is associated with the appropriate entity as required
                                   f) Field association is stored in the database
                                   g) Field association/type is validated against data constructs and setup rules
ASSIGN FIELD                       Implies the need to capture a specific data element(s) as part of the requirements entity; all fields may not be specifically addressed.
ASSIGN INDICATOR                   Implies the capturing of specific conditions/state and maintaining a history of state changes over time.
ASSIGN UNIQUE IDENTIFER            Implies the need for an entity to be uniquely identified for referential integrity.
DEFINE                             Implies the establishment of configuration options. These options may be implemented globally across all court levels or locally across
                                   specific court types, court locations, case categories or case types
DEFINE CODES/DEFINE TYPE           Implies the creation of coded data constructs that may be used to form hierarchical relationships between data sets or be used to restrict
                                   selections for validation.
DEFINE CODES TO ASSOCIATE/         Implies the creation of codes in order to form a relationship between the entities noted in the context of the requirement.
DEFINE RULE                        Implies the creation of business rules governing conditional behavior
DEFINE WORKFLOW                    Implies the creation of a set of rules that represent an entire business process
DEFINE CENTRAL REPOSITORIES        Implies the creation of a centralized data set with unique idenfifiers that can be used globally in all cases.
DEFINE DISPLAY FIELDS              Implies the specification of fields that display on screen or on printed report with the assumption that anything that can be displayed can also
                                   be printed in the displayed format
DEFINE FIELDS FOR QUERYING         Implies the specification of the fields that will be used in creating a query.
PRODUCE                            Implies:
                                   a) creation of output that can be viewed on screen, printed in hardcopy, electronicially stored or exported for use in another application
                                   b) Output based on a defined layout or template
PRODUCE/CREATE DOCUMENT            Implies creation of a completed document. Documents can be further classified by various names such as: orders, notices and writs.
                                   Documents may also be generated based on pre-defined templates
PRODUCE REPORT                     Implies the presentation of an organized set of data generated based on a query that can be displayed on screen or printed. The completed
                                   report can be based on a pre-defined query and report layout or produced from a user defined ad hoc query and layout.
DISPLAY/VIEW                       Implies the presentation of an organized set of data inorder to provide a view of saved records and relationships
NAVIGATE                           Implies user interface functionality that allows the user to be taken to another functional area of the application automatically
OVERRIDE                           Implies the user's ability to make a selection that is contrary to an assigned default.
CHOOSE/SELECT                      Implies selection of one or many rows from a specific data set. The contents of the data set may be filtered based on the context of the
                                   selection
SEARCH/SORT/FILTER                 Implies the ability to execute a query and be presented with the resulting data set electronically. The results set should be able to be further
                                   sorted and filtered. Search results should consider the user's access control to the records selected by the query.


    MDEC Procurement K11-0030-29                                                                                                                                 September 1, 2010
                                                   MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                        ATTACHMENT C
                                                     MARYLAND ELECTRONIC COURT PROCUREMENT                               Page 4 of 249
                                                            FUNCTIONAL REQUIREMENTS

                                                                  CASE INITIATION AND INDEXING

      ID                                      Requirement Text                                       Response Code   Comments
CII-001      Establish relationships of courts and agencies noted above (e.g., other
             courts, corrections, law enforcement, domestic relations service providers)
             with parties.
CII-001.01        Provide USER with the ability to select relationship of PARTIES to             0
                  OTHER COURTS and AGENCIES.
CII-001.02        Provide ADMIN USER with the ability to define relationship of                  0
                  PARTIES to OTHER COURTS and AGENCIES.
CII-001.03        Provide USER with the ability to assign a relationship between a               0
                  PARTY and an AGENCY.
CII-002      Enter in docket or register of actions case initiation information including
             date and time of initial filing, information on initial filing noted above
             (including identity of filer), and basic case information (e.g., case number
             and other identifiers, case type, case category, court type and location,
             case status, case title or style, whether case is Title IV-D with IV-D
             identifier, parties, attorneys, date filed, judge or other judicial officer, last
             and next events, and other docket-related events) (see also Docketing and
             Related Recordkeeping Function)
CII-002.01        Provide ADMIN USER with the ability to define workflow for entering            0
                  CASE initiation information in docket.
CII-002.02        Provide ADMIN USER with the ability to define fields and Provide               0
                  validation rules for entering CASE initiation information in docket.
CII-002.03        Provide USER with the ability to initiate the CASE including case              0
                  Number , CASE TYPE , category , court type, location, status , title
                  (based on the rules setup by ADMIN USER) and Date and time of
                  filing.




CII-003      Provide the ability to define basic case information that must be entered in
             order to initiate a case, by CASE TYPE.
CII-003.01       Provide ADMIN USER with the ability to locally define rules for                 0
                 required fields for CASE initiation per CASE TYPE.
CII-004      Provide the ability to utilize either a statewide unified case numbering
             scheme or individual case numbering schemes by jurisdiction.
CII-004.01       Provide ADMIN USER with the ability to define CODES for CASE                    0
                 NUMBERING SCHEME.

      MDEC Procurement K11-0030-29                                                                                     September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                       ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                              Page 5 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                               CASE INITIATION AND INDEXING

      ID                                    Requirement Text                                      Response Code   Comments
CII-004.02         Provide ADMIN USER with the ability to assign jurisdiction to CASE         0
                   NUMBERING SCHEME.
CII-004.03         Provide USER with the ability to assign a CASE NUMBER based on             0
                   the rules.
CII-005      Provide the ability to relate different CASE TYPEs that arise from the same
             incident (e.g., incident leads to criminal, traffic, and DNR charges).
CII-005.01         Provide ADMIN USER with the ability to define a rule to relate different   0
                   CASE TYPEs that arise from the same incident.
CII-005.02         Provide USER with the ability to search by incident.                       0
CII-006      Provide the ability to distinguish between CINA shelter and non shelter on
             filing case.
CII-006.01         Provide ADMIN USER with the ability to define codes for CINA               0
                   SHELTER and NON SHELTER.
CII-006.02         Provide USER with the ability to assign CINA SHELTER OR NON                0
                   SHELTER To the CASE.
CII-007      Supplement docket or register of actions entries with additional information
             on children and parents (e.g., identifier, date of birth, social security
             number) (in accordance with Section 466(a)(13)(B) of the Social Security
             Act).
CII-007.01         Provide ADMIN USER with the ability to define rules to enter additional    0
                   information on children and parents.
CII-007.02         Provide USER with the ability to assign additional information to a        0
                   Person.
CII-007.03         Provide USER with the ability to assign date of birth to a                 0
                   Person[Juvenile].
CII-007.04         Provide USER with the ability to assign social security number to a        0
                   Person[Juvenile].
CII-008      Assign appropriate security to records, particularly those with data on
             children and other minors (e.g., for each PARTY with increased security for
             child and family records, or for warrants that have not been served). (see
             also Security Function)
CII-008.01         Provide ADMIN USER with the ability to define security access rules        0
                   for any field or combination of fields in system.
CII-008.02         Provide ADMIN USER with the ability to define security access rules        0
                   for any person/organization entity in system.
CII-008.03         Provide ADMIN USER with the ability to define security access rules        0
                   for any case in the system.

      MDEC Procurement K11-0030-29                                                                                  September 1, 2010
                                                MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                  MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 6 of 249
                                                         FUNCTIONAL REQUIREMENTS

                                                              CASE INITIATION AND INDEXING

      ID                                  Requirement Text                                      Response Code   Comments
CII-008.04       Provide ADMIN USER with the ability to define security access rules        0
                 for any Event object in the system.
CII-008.05       Provide ADMIN USER with the ability to define security access rules        0
                 for any Address to Entity relationship in the system.

CII-008.06        Provide ADMIN USER with the ability to define security access rules       0
                  for any Document Image in the system.
CII-009      Enter information in docket or register of actions for parties and
             participants as individuals (e.g., Ann Smith) or organizations (e.g.,
             investigative service) with primary contact person if organization (see also
             Docketing and Related Recordkeeping Function).
CII-009.01        Provide ADMIN USER with the ability to define PARTY TYPE CODE.            0
CII-009.02        Provide USER with the ability of a drill down option thru PARTY TYPE      0
                   Category Type when selecting PARTY TYPE CODE.
CII-009.03        Provide ADMIN USER with the ability to assign a PARTY TYPE CODE           0
                  to a single PARTY CODE Category type.
CII-009.04        Provide ADMIN USER with the ability to define ADDRESS TYPE                0
                  CODE.
CII-009.05        Provide ADMIN USER with the ability to assign a PARTY TYPE CODE           0
                  to multiple CASE TYPE.
CII-009.06        Provide USER with the ability to assign a PERSON to a CASE.               0
CII-009.07        Provide USER with the ability to assign an Organization to a CASE.        0
CII-009.08        Provide USER with the ability to assign many Primary Contacts to an       0
                  Organization.
CII-009.09        Provide USER with the ability to assign many PARTY Code Types to a        0
                  (Person to Case) Relationship.
CII-009.10        Provide USER with the ability to assign many PARTY Code Types to a        0
                  (Organization to Case) Relationship.
CII-009.11        Provide USER with the ability to have choices of PARTY TYPE Codes         0
                  that will validate against the Case Category type of the case.
CII-009.12        Provide USER with the ability to directly enter PARTY TYPE Code.          0
CII-009.13        AUTOMATICALLY validate PARTY TYPE Code against the Case                   0
                  Category type of the case.
CII-009.14        Provide USER with the ability to assign first-name, middle-name, last-    0
                  name, name-prefix, name-suffix and additional family or middle names
                  to a Person.


      MDEC Procurement K11-0030-29                                                                                September 1, 2010
                                                MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                     ATTACHMENT C
                                                  MARYLAND ELECTRONIC COURT PROCUREMENT                            Page 7 of 249
                                                         FUNCTIONAL REQUIREMENTS

                                                             CASE INITIATION AND INDEXING

      ID                                  Requirement Text                                     Response Code   Comments
CII-009.15       Provide USER with the ability to assign an organization name to an        0
                 Organization.
CII-009.16       Provide USER with the ability to assign a resident agent or service       0
                 party to an Organization
CII-009.17       Provide ADMIN USER with the ability to define ADDRESS TYPE                0
                 CODE.
CII-009.18       Provide USER with the ability to assign many addresses to an              0
                 Organization or Person.
CII-009.19       Provide USER with the ability to assign an address type to an Address.    0

CII-009.20        Provide USER with the ability to assign international address            0
                  information to an Address.
CII-009.21        Provide USER with the ability to assign an end date to a (PARTY to       0
                  Address) Relationship.
CII-010      Provide ability to establish relationships between parties and relationship
             between party and case (attorney/client, familial relationships, defendant,
             witness, victim, etc.).
CII-010.01        Provide ADMIN USER with the ability to define CODES for PARTIES.         0
CII-010.02        provide ADMIN USER with the ability to define relationships between      0
                  PARTIES on a CASE.
CII-010.03        Provide ADMIN USER with the ability to Maintain relationships            0
                  between PARTY and case. Allow the same PARTY to be associated
                  with many cases.
CII-010.04        Provide ADMIN USER with the ability to specify what these roles are or   0
                  make them USER defined per CASE TYPE per PARTY TYPE.
CII-010.05        Provide USER with the ability to assign a PARTY to one or more           0
                  Cases.
CII-010.06        Provide USER the ability to assign a Case to one or more Parties.        0
CII-011      Create alerts based upon approaching or passed deadlines, and record if
             time-sensitive filing that requires rapid action (e.g., schedule emergency
             domestic violence hearing even though only minimal data available, issue
             restraining order, process stay request).
CII-011.01        Provide ADMIN USER with the ability to define rule to create alerts.     0




      MDEC Procurement K11-0030-29                                                                               September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 8 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                CASE INITIATION AND INDEXING

      ID                                    Requirement Text                                      Response Code   Comments
CII-012      Prompt user when cases or parties already exist that relate to new case
             (e.g. parties filed other cases), followed by user-initiated search for
             duplicate parties and attorneys (including instances in which parties or
             attorneys have different roles in different cases such as party who is
             petitioner in one case and respondent in another case, or attorney who is
             counsel in one case or guardian ad litem in another case) that user can
             transfer into current case if appropriate to avoid redundant data entry (e.g.,
             using party names, addresses, and other identifiers noted above).
CII-012.01        Provide ADMIN USER with the ability to define rules for matching a          0
                  duplicate PARTY across multiple cases.
CII-012.02        Provide ADMIN USER with the ability to define rules for matching a          0
                  duplicate Attorney across multiple cases.
CII-012.03        Provide ADMIN USER with the ability to define rules for matching a          0
                  duplicate generic entity across multiple cases. ( This match ignores
                  entities role on case ).
CII-012.04        Provide USER a prompt when a match or match(s) are found.                   0
CII-012.05        Provide USER with the ability to do a subsequent Case and PARTY             0
                  detail lookup on each matching candidate.
CII-012.06        Provide USER with the ability to associate selected entity with initiated   0
                  PARTY to case's specified role.
CII-013      Capture demographic information for each PARTY in a case.

CII-013.01        Provide ADMIN USER with the ability to define fields for querying the       0
                  demographic information on each PARTY.
CII-013.02        Provide USER with the ability to search on demographic information          0
                  on each PARTY.
CII-014      Create and maintain locally defined index that (1) contains basic index
             information (e.g., each PARTY name, date of birth, role in case, and
             whether party has an attorney; case type; court type and location; case
             number and other identifiers; date filed; and cross reference to other
             parties in case [e.g., other party named in case title or style]); (2) permits
             database look-up by a choice of key fields (e.g., party name, party role,
             case filed date range) and, if record found; (3) permits retrieval and display
             of index information;, and (4) permits easy interfaces with other parts of
             case processing system as noted below.
CII-014.01        Provide ADMIN USER with the ability to define fields for searching the Case 0
                 and PARTY records.

      MDEC Procurement K11-0030-29                                                                                  September 1, 2010
                                                   MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                         ATTACHMENT C
                                                     MARYLAND ELECTRONIC COURT PROCUREMENT                                Page 9 of 249
                                                            FUNCTIONAL REQUIREMENTS

                                                                  CASE INITIATION AND INDEXING

      ID                                   Requirement Text                                           Response Code   Comments
CII-014.02       Provide ADMIN USER with the ability to define fields that are displayed in the   0
                 Case and PARTY Index search result screen.
CII-014.03       Provide ADMIN USER with the ability to define rules for screen navigation        0
                 based on field values in a selected row.
CII-014.04       Provide USER with the ability to search the CASE and PARTY Index with            0
                 specified fields.
CII-014.05       Provide USER with the ability to manually navigate directly from the search      0
                 result screen to any functional screen based on field value context of a
                 selected row.
CII-014.06       Provide USER with the ability to manually navigate directly from a search        0
                 result row to a pre-configured screen.
CII-014.07       Provide USER with the ability to sort on any column in the CASE and PARTY        0
                 search result screen.
CII-015      Handle look-up and retrieval subfunctions by identifying a specific party
             name, date of birth, party role, court type or location, case or party
             identifier, case filed date range—if necessary, after eliminating other cases
             or parties that satisfy original look-up—and then obtaining index
             information by selecting from list of matching cases or parties or by using
             key fields noted above (e.g., user requests list of parties named Smith,
             system returns list of Smiths, user selects desired Smith from list by
             clicking on proper line or entering proper keys (sometimes after several
             tries that yield another Smith), system returns index information on cases
             involving that Smith).
CII-015.01        Provide USER with the ability to search on CASE and PARTY Index by 0
                  narrowing a previous search ( ex. USER is able to select specific rows
                  (usually after a sort). System then AUTOMATICALLY repopulates the
                  search fields with new range values from selected.
CII-016      Allow users easy interface with other parts of the system such as
             docketing, scheduling, calendaring, and accounting for potentially all
             related case and financial information (i.e., on specific case, its parties, its
             participants, its attorneys and on cases related to specific case and to its
             parties, participants, and attorneys) and with the inquiry and report
             generation capabilities for more varied displays.
CII-016.01        Provide USER with the ability to manually navigate to any functional        0
                  screen when selecting a row after any interactive search or the
                  running of any interactive report. The resulting functional screen is to
                  be AUTOMATICALLY populated based on the context of selected
                  fields.

      MDEC Procurement K11-0030-29                                                                                      September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                        ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                               Page 10 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                 CASE INITIATION AND INDEXING

      ID                                     Requirement Text                                       Response Code   Comments
CII-017      Generate locally defined case title or style (i.e., short phrase that identifies
             case and include plaintiff/petitioner and defendant/respondent names) from
             PARTY names, CASE TYPEs, and other information. Allow for override of
             automated case title or style.
CII-017.01        Provide ADMIN USER with the ability to locally define rules for               0
                  formatting the case title.
CII-017.02        Provide USER with the ability to assign case title to a Case by               0
                  overriding the automatic default for case title format.
CII-017.03        provide ADMIN USER with the ability to locally define rules for               0
                  formatting the case style.
CII-018      Conduct locally used review processes to ensure case should be accepted
             by court and display results (e.g., attorney not suspended for failure to
             pay, bondsman or interpreter not suspended).
CII-018.01        Provide ADMIN USER with the ability to locally define rules for case          0
                  acceptance in the "review process".
CII-018.02        Provide ADMIN USER with the ability to locally define rules for case          0
                  acceptance.
CII-018.03        Provide USER with the ability to search display results.                      0
CII-019      Enter reason for initiation (e.g., new filing, transferred from another
             jurisdiction, reopened or remanded case, counter or cross claims, de
             novo appeal according to local procedures).
CII-019.01        Provide ADMIN USER with the ability to locally define Case initiation         0
                  Reasons (see Data Definitions).
CII-019.02        Provide the ADMIN USER with the ability to locally define types for           0
                  Case Initiation Rejection Reasons.
CII-020      Maintain history of CASE TYPE change when transferred from another
             jurisdiction allow intaking county to override case information.(CASE
             TYPE, parties, PARTY TYPEs, addresses, attorneys).
CII-020.01       AUTOMATICALLY maintain history of CASE TYPE change when transferred            0
                 from another jurisdiction.
CII-021      Issue back to proper jurisdiction on commitment. AUTOMATICALLY
             indicate on commitment that the defendant is to be transferred back to
             issuing county. Allow commissioners to set trial dates for ―out of county‖
             cases using an automated system.
CII-021.01        AUTOMATICALLY indicate on commitment that the defendant is to be 0
                  transferred back to issuing county.


      MDEC Procurement K11-0030-29                                                                                    September 1, 2010
                                                   MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                        ATTACHMENT C
                                                     MARYLAND ELECTRONIC COURT PROCUREMENT                               Page 11 of 249
                                                            FUNCTIONAL REQUIREMENTS

                                                                 CASE INITIATION AND INDEXING

      ID                                     Requirement Text                                        Response Code   Comments
CII-021.02       Provide USER with the ability to assign trial dates for" out of county"         0
                 cases using an automated system.
CII-022      Enter locally used court identifiers (e.g., district court) and court location
             identifiers (e.g., county or location number), including the ability to set local
             defaults.
CII-022.01       Provide ADMIN USER with the ability to define court identifiers(e.g.,           0
                 district court).
CII-022.02       Provide ADMIN USER with the ability to locally assign a USER to a               0
                 default Court Location Type.
CII-022.03       Provide the ADMIN USER with the ability to locally assign a USER to             0
                 many default Court Location Type(s).
CII-023      Support electronic filing (e.g., directly from attorneys‘ offices) and move
             designated data (e.g., tagged basic case information) from electronic
             document to case processing system.
CII-023.01       Be able to import a case to the review process with the ECF 4.0 XML             0
                 standard.
CII-024      Generate receipt for or notify appropriate parties that case filing received
             and accepted, and give them assigned case number (notice, including
             electronic acknowledgment, would apply primarily when case transferred
             from another jurisdiction or filed electronically) (see also Document
             Generation and Processing Function)
CII-024.01       AUTOMATICALLY generate Receipt when "case filing" was received.                 0
CII-024.02       AUTOMATICALLY generate Notification for appropriate Person(s)                   0
                 when Case is "reviewed and accepted".
CII-025      Support differential case management (i.e., different categories of cases
             are processed differently such as in time-sensitive filings, cases processed
             under different rules or time standards, specific judicial assignment for
             specific types of cases) and other case management methods (users enter
             local differential case management parameters and time standards into
             code translation tables; see List of Code Translation Tables). PLEASE
             NOTE: differential case management may entail highly complex computer
             programming because it may permit the user to define complete case
             processing profiles (e.g., containing processing rules and schedules for
             each event) for each case type and case category)

CII-025.01       Provide ADMIN USER with the ability to define different caseflow                0
                 TRACKS.

      MDEC Procurement K11-0030-29                                                                                     September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 12 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                               CASE INITIATION AND INDEXING

      ID                                   Requirement Text                                      Response Code   Comments
CII-025.02       Provide ADMIN USER with the ability to define case MILESTONES               0
                 associated for each TRACK
CII-025.03       Provide ADMIN USER with the ability to define milestone target dates        0
                 that may be calculated based on other milestone dates, calculated
                 using simple date mathematics, or calculated based on date elements
                 found in the case
CII-025.04       Provide ADMIN USER with the ability to define milestone target dates        0
                 as calendared events (e.g. Trial date) or as case deadlines (e.g.
                 discovery deadline)
CII-025.05       Provide ADMIN USER with the ability to define codes to associate a          0
                 track to a specific case type
CII-025.06       Provide USER with the ability to assign a case to a track                   0
CII-025.07       Provide USER with the ability to override track milestone target dates      0
CII-025.08       Provide USER with the ability to assign a new case flow track at any        0
                 time in case processing
CII-025.09       Provide USER with the ability to configure the case processing work         0
                 flowfor different case types.
CII-026      Display in case history the time standards for, and age of, a given case.
             Age must be calculated per business rules for initiation, suspension, and
             disposition.
CII-026.01       AUTOMATICALLY display the case age based on the time standards,             0
                 and the business rules for initiation, suspension, and disposition.

CII-027      Create groups of related cases (e.g., several tort cases filed against same
             defendant by different plaintiffs, several paternity cases filed against same
             respondent by same or different petitioners, multiple-plaintiff asbestos
             cases)
CII-027.01       Provide USER with the ability to assign many Cases to a Case Group.         0

CII-027.02       AUTOMATICALLY link/apply all initial entries to each Case in the Case 0
                 Group when assigning a Case to a Case Group.
CII-027.03       AUTOMATICALLY link/apply all subsequent entries to each Case in          0
                 the Case Group.
CII-028      Establish relationships (including type of relationship) between cases and
             case categories and court types (e.g., small claims, matrimonial),
             locations, and departments (e.g., for large courts with multiple locations).


      MDEC Procurement K11-0030-29                                                                                 September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                       ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                              Page 13 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                               CASE INITIATION AND INDEXING

      ID                                     Requirement Text                                     Response Code   Comments
CII-028.01         Provide ADMIN USER with the ability to define COURT TYPE CODES             0
                   [ex.CC District, Circuit, Appellate].
CII-028.02         Provide ADMIN USER with the ability to define                              0
                   Circuit/District/Appellate CODES [ CC County, District Number ].
CII-028.03         Provide ADMIN USER with the ability to define Court LOCATION               0
                   TYPE CODES [ex, Location within District ].
CII-028.04         Provide ADMIN USER with the ability to assign a COUNTY CODE type           0
                   to a LOCATION TYPE.
CII-028.05         Provide ADMIN USER with the ability to assign USERs to one or more         0
                   Court LOCATIONS types.
CII-028.06         Provide ADMIN USER with the ability to locally set default COURT           0
                   SUB LOCATION CODE.
CII-028.07         Provide USER with the ability to assign a CASE to a COURT                  0
                   LOCATION TYPE.
CII-029      Permit name search on various combinations of a person‘s or PARTY‘s
             name (e.g., full name, last name only, part of first or last name, aliases,
             maiden names, etc.)
CII-029.01         Provide ADMIN USER with the ability to define rule(s) to search            0
                   person's or PARTY's name with various combinations.
CII-029.02         Provide USER with the ability to search person or PARTY name with          0
                   various combinations.
CII-030      If attorneys included in index, allow multiple names and bar identifiers and
             relationship to law firm.
CII-030.01         Provide ADMIN USER with the ability to define rules to identify multiple   0
                   Attorney names and bar identifiers only if attorneys included on index.

CII-030.02        Provide the ADMIN with the ability to define relationship between           0
                  attorney and law firm.
CII-031      Include index information in index record or make this information easily
             accessible (e.g., in a manner that requires no additional USER actions).
CII-031.01        AUTOMATICALLY maintain index records.                                       0
CII-032      Permit updating of index based on occurrence of specific case events
             (e.g., motions filed, dispositions decided).
CII-032.01        Provide ADMIN USER with the ability to define rules that specify what       0
                  event types or records are tracked in the index.
CII-032.02        AUTOMATICALLY maintain Event index information.                             0


      MDEC Procurement K11-0030-29                                                                                  September 1, 2010
                                                MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                   ATTACHMENT C
                                                  MARYLAND ELECTRONIC COURT PROCUREMENT                          Page 14 of 249
                                                         FUNCTIONAL REQUIREMENTS

                                                             CASE INITIATION AND INDEXING

      ID                                    Requirement Text                                 Response Code   Comments
CII-033      Extract, print, or otherwise produce (e.g., microfiche, PDF) with appropriate
             security restrictions index information arranged according to various
             components of index (e.g., PARTY, case number, case status).
CII-033.01       Provide USER with the ability to request output of Case/PARTY index. 0

CII-033.02        Provide USER with the ability to set preferences on sort criteria on   0
                  Case and PARTY Index output.
CII-033.03        Provide USER with the ability to set preferences on fields to be       0
                  included in Case and PARTY Index output.
CII-034      Retrieve basic index information on all cases associated with specific
             participant.
CII-034.01        Provide ADMIN USER with the ability to define rules for Specific       0
                  participant on all cases.
CII-035      Accommodate aliases in conjunction with indexing and processing of
             PARTY names as appropriate.
CII-035.01        Provide USER with the ability to search Case and PARTY Index with      0
                  alias information.
CII-036      Capture or allow entry of other unique identifiers as needed (e.g., of
             prosecutor, defense attorney, corrections, law enforcement) and establish
             relationships with participants.
CII-036.01        Provide ADMIN USER with the ability to define Agency Group Type        0
                  codes.
CII-036.02        Provide USER with the ability to assign a Person to an Agency Group    0
                  Type.
CII-036.03        Provide USER with the ability to assign an end date to an (Entity to   0
                  Agency Group) Relationship.
CII-036.04        Provide ADMIN USER with the ability to define PARTY relationships      0
                  types.
CII-036.05        Provide ADMIN USER with the ability to assign valid PARTY              0
                  Relationship types for PARTY TYPE pairs.
CII-036.06        Provide USER with the ability to assign many (Person to Person)        0
                  Relationships between the same 2 Persons on the same case.
CII-036.07        Provide USER with the ability to assign an end date to a (PARTY to     0
                  PARTY) Relationship on a Case.
CII-037      Generate and assign case number for a defendant using locally-defined
             format and procedures (e.g., separate case number for each incident or
             offense, or for each incident or offense and each defendant).

      MDEC Procurement K11-0030-29                                                                             September 1, 2010
                                                MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                  MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 15 of 249
                                                         FUNCTIONAL REQUIREMENTS

                                                              CASE INITIATION AND INDEXING

      ID                                   Requirement Text                                     Response Code   Comments
CII-037.01        Provide ADMIN USER with the ability to define rules to relate different   0
                  CASE TYPEs that arise from the same incident.
CII-037.02        Provide ADMIN USER with the ability to define each CASE TYPE to           0
                  each incident.
CII-037.03        Provide ADMIN USER with the ability to define rules to establish          0
                  relationship between parties and cases.
CII-037.04        Provide USER with the ability to assign parties to cases.                 0
CII-037.05        Provide USER with the ability to assign relationship between parties.     0
CII-037.06        Provide ADMIN USER with the ability to locally define rules to generate   0
                  and format a local defendant case number.
CII-037.07        Provide USER with the ability to assign many local defendant case         0
                  numbers to a Person[Defendant] per incident or offense.
CII-038      Associate each defendant (or PARTY) with a case using locally-defined
             procedures.
CII-038.01        Provide ADMIN USER with the ability to define CODES for PARTIES.          0
CII-038.02        Provide ADMIN USER with the ability to define relationships between       0
                  PARTIES on a CASE.
CII-039      Enter each charge (or allegation) and count based on charging documents
             and alert USER if restriction (such as pretrial release or requirement for
             preliminary hearing) exists.
CII-039.01        Provide ADMIN USER with the ability to set restrictions when adding       0
                  on charging document.
CII-039.02        Provide USER an alert when a restriction exists when a charge is          0
                  added.
CII-040      Provide ability to place allegation or charge codes into groups (e.g.,
             murder, sexual abuse, rape, hate crime, DV Order Violations, DV
             Vulnerable Adult, DV Child Abuse, etc.) for statistical reporting purposes.
CII-040.01        Provide ADMIN USER with the ability to define charge codes to groups.     0

CII-040.02        Provide USER with the ability to assign charge codes to groups.           0
CII-041      Coordinate with Docketing and Related Record Keeping Function to enter
             all charges or relief/issues (initial and modified) filed by prosecutor or
             commissioner at case initiation and subsequently.
CII-041.01        Provide ADMIN USER with the ability to define workflow for CASE           0
                  initiation data entry.



      MDEC Procurement K11-0030-29                                                                                September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                       ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                              Page 16 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                CASE INITIATION AND INDEXING

      ID                                    Requirement Text                                       Response Code   Comments
CII-041.02        Provide ADMIN USER with the ability to define fields and provide             0
                  validation rules for entering Charges/ relief or issues at case initiation
                  and at modification.
CII-041.03        Provide ADMIN USER with the ability to define types of events that           0
                  create docket entries.
CII-041.04        Provide USER with the ability to assign charges/Relief or Issues to a        0
                  Case at case initiation and also at modification.
CII-042      Identify lead charge, if appropriate, among group of charges for a given
             defendant (e.g., the most serious of charges). In traffic cases allow the
             input of citations in any order, allow system to AUTOMATICALLY sort,
             organize and select lead citation base
CII-042.01        Provide ADMIN USER with the ability to define rules to identify lead         0
                  charge form group of charges.
CII-042.02        AUTOMATICALLY sort lead charge.                                              0
CII-043      Enter arrest, citation, custody, and bail information for each defendant or
             acquire this information from CJ agency (including bond and surety
             information).
CII-043.01        Provide automatic ability to import arrest, citation, custody and bail       0
                  information with Niem 2.0 XML and AUTOMATICALLY assign
                  imported information to case.
CII-044      Assign cases to court type, judge, location, department, and courtroom
             AND/OR other appropriate entities based on established relationships (see
             Scheduling Function) Statewide systems must have the ability to assign
             cases based on Circuit or Judicial district).
CII-044.01        AUTOMATICALLY and provide user with the ability to assign cases to           0
                  a judge, courtoom, department or location based on established case
                  data and relationships.
CII-045      Allow USER to designate the nature of the relationship between cases
             (e.g. codefendants, multiple cases against same defendant or respondent).

CII-045.01       Provide ADMIN USER with the ability to define CODES for PARTIES.              0
CII-045.02       Provide ADMIN USER with the ability to define relationships between           0
                 PARTIES on a CASE.
CII-045.03       Provide ADMIN USER with the ability to Maintain relationships                 0
                 between PARTY and case. Allow the same PARTY to be associated
                 with many cases.


      MDEC Procurement K11-0030-29                                                                                   September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 17 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                CASE INITIATION AND INDEXING

      ID                                Requirement Text                                          Response Code   Comments
CII-045.04       Provide ADMIN USER with the ability to specify what these roles are or 0
                 make them USER defined per CASE TYPE per PARTY TYPE.
CII-046      Assign referral numbers and person (e.g., juvenile and family) and other
             identifiers.
CII-046.01       Provide USER with the ability to assign referral numbers and person    0
                 and other identifier.
CII-047      Track or flag when a person refuses to testify against his or her spouse.

CII-047.01        Provide USER with the ability to assign an indicator to a Case when a       0
                  person refuses to testify against spouse.
CII-047.02        Provide ADMIN USER with the ability to define indicator to a case           0
                  when a person refuses to testify against spouse.
CII-048      Prompt USER when related information already exists for juvenile and
             family named in referral, and allow USER to output existing information.
CII-048.01        Provide ADMIN USER with the ability to set rules to prompt USER for         0
                  existing juvenile and family named in referral
CII-048.02        AUTOMATICALLY alert USER when a party already exists in the                 0
                  system.
CII-049      Allow USER to capture (i.e., enter, receive electronically, or transfer
             existing information into current referral entry to avoid data entry) referral
             information.
CII-049.01        INTERFACE from Department of Juvenile Services or Department of             0
                  Human Resources
CII-050      Establish relationships, including links to others in referral and others in
             family, within newly-entered information and between new and existing
             information.
CII-050.01        Provide ADMIN USER with the ability to define relationships between         0
                  others in the same referral and others in the same family within the
                  existing and new information.
CII-051      Merge multiple related referrals for single child into one course of action.

CII-051.01       Provide user with the ability to merge multiple related referrals for    0
                 single child into one course of action.
CII-051.02       Provide user with the ability to consolidate cases into a single case OR 0
                 to designate that multiple cases will be processed (e,g, hearings held,
                 document filings) together


      MDEC Procurement K11-0030-29                                                                                  September 1, 2010
                                                    MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                          ATTACHMENT C
                                                      MARYLAND ELECTRONIC COURT PROCUREMENT                                 Page 18 of 249
                                                             FUNCTIONAL REQUIREMENTS

                                                                   CASE INITIATION AND INDEXING

      ID                                   Requirement Text                                             Response Code   Comments
CII-052      Link multiple related referrals for a single child to a single family.

CII-051.01         Provide user with the ability to link multiple referrals for a single child to   0
                   a single family.
CII-053      Store all (i.e., new combined with existing, historical resulting from
             research) referral information in updated or new intake file; maintain intake
             file as case progresses (e.g., enter information pertaining to temporary
             actions noted below); and output.
CII-053.01         AUTOMATICALLY store referral information from new intake and                     0
                   update case files as case progresses.
CII-054      Enter, maintain, process, and store information pertaining to temporary
             actions (any actions of a temporary nature put in place at the beginning of
             the case; e.g., informal supervision, shelter care, or temporary protective
             custody) including recording events
CII-052.01         Provide ADMIN USER with the ability to define certain actions as                 0
                   temporary
CII-052.02         AUTOMATICALLY store case information for all temporary actions by                0
                   recording each event.
CII-055      Enter results of research on referral (e.g., verification of person and family
             information such as name; addresses; juvenile date of birth, race, ethnic
             group, sex; prior contact with court; service and justice agencies; alias(es);
             schools)
CII-055.01         Provide USER with the ability to enter results of referral.                      0
CII-056      Provide USER with assessment tools, risks, and probable results to assist
             with decision on referral.
CII-056.01         Provide USER with the assessment tools, referral risks and probable              0
                   results for a referral to assist in the outcome decision.
CII-057      Enter decision (outcome) on referral (e.g., file a petition in juvenile court,
             conduct informal adjustment or diversion program (in conjunction with
             Juvenile Court Support Functions), refer to medical or social evaluation,
             reject) in intake file and retain all information.
CII-057.01         Provide USER with the ability to enter decision outcome in intake file.          0

CII-058      Create pleadings within delinquency case categories by combining
             standard text (e.g., statutes for each allegation), variable data (e.g.,
             juvenile information), and other data (e.g., imaged if capability exists in
             system) information).

      MDEC Procurement K11-0030-29                                                                                        September 1, 2010
                                                           MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                          ATTACHMENT C
                                                             MARYLAND ELECTRONIC COURT PROCUREMENT                                 Page 19 of 249
                                                                    FUNCTIONAL REQUIREMENTS

                                                                           CASE INITIATION AND INDEXING

      ID                                      Requirement Text                                                 Response Code   Comments
CII-058.01           Provide USER with the ability to create pleadings within delinquency                  0
                     case categories by combining standard text, variable data and other
                     data.
CII-059          Convert one referral for family or multiple persons into separate petitions
                 and track separately through resolution for each juvenile.
CII-059.01           Provide USER with the ability to manually navigate to any functional                  0
                     screen when selecting a row from any interactive search or the
                     running of any interactive report. The resulting functional screen is to
                     be AUTOMATICALLY populated based on the context of the selected
                     data.
CII-059.02           Provide USER with the ability to accept one intake referral and create                0
                     separate cases that are maintained and tracked separately
CII-060          Transfer intake information and petition to initiate case if petition filed with court.

CII-060.01            AUTOMATICALLY receive intake information from external source.                       0
CII-060.02           Automatically assign electronic intake information to Case.                           0
CII-060.03           Provide USER with the ability to assign fields from Documents[intake,                 0
                     petition] to case.
CII-060.04           Provide USER with the ability to assign Documents[intake, petition] to                0
                     case.
CII-060.05           Provide ADMIN USER the ability to define rules for required fields for                0
                     electronic documents.
CII-061          Transfer intake and referral information to outside agencies. (see Juvenile
                 Court Support Functions).
CII-061.01           Provide ADMIN USER the ability to define rules for required fields for                0
                     electronic documents.
CII-062          Output information for transfer to another jurisdiction.

CII-062.01            Provide ADMIN USER the ability to define rules for required fields for               0
                      electronic documents.

CII-063          Enter, maintain, process, and store intermediate and final information
                 pertaining to outside agency program (e.g., diversion Administered by
                 probation) or internal program (e.g., informal adjustment Administered by
                 intake) including recording events.



          MDEC Procurement K11-0030-29                                                                                           September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                    ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                           Page 20 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                              CASE INITIATION AND INDEXING

      ID                                    Requirement Text                                   Response Code   Comments
CII-063.01        Provide USER the ability to enter and maintain intermediate and final    0
                  case information related to a referral to an internal or ouside agency
                  program.
CII-064      As case progresses, interact with juvenile services and justice and social
             services agencies to perform ongoing functions (e.g., Administer court-
             ordered supervision) and maintain intake file (e.g., track allegations) as
             established by local conventions.
CII-064.01        Provide ADMIN USER the ability to define rules for required fields for   0
                  electronic documents.
CII-065      Create notices and other documents (e.g., letters to victims and schools
             requesting more information). (see Document Generation and Processing
             Function)
CII-065.01        Provide USER with the ability to produce DOCUMENT[notices].              0
CII-066      Receive and send documents and information electronically including
             notices verifying receipt of electronic information.
CII-066.01        Provide ADMIN USER the ability to define rules for required fields for   0
                  electronic documents.
CII-067      Output all, part, or summaries of intake files for individual or groups of
             juveniles, family, or other parties as requested by USER.
CII-067.01        Provide USER with the ability to request output of intake information.   0
CII-068      Exchange information with external participants (e.g., public and private
             agencies charged with child protection, state and local government
             agencies, state and local government attorneys, law enforcement, public
             and private mental health agencies).
CII-068.01        Provide ADMIN USER the ability to define rules for required fields for   0
                  electronic documents.
CII-069      Ensure appropriate security and data integrity on intake information. (see
             Security and Data Integrity Function).
CII-069.01        Provide ADMIN USER with the ability to define rules for field level      0
                  security with privileges based on USER role and nature of the data in
                  the field.
CII-070      Receive intake information and petition to initiate case from intake.

CII-070.01       AUTOMATICALLY receive intake information from external source.            0
CII-070.02       Automatically assign electronic intake information to Case.               0
CII-070.03       Provide USER with the ability to assign fields from Documents[intake,     0
                 petition] to case.

      MDEC Procurement K11-0030-29                                                                               September 1, 2010
                                                    MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                       ATTACHMENT C
                                                      MARYLAND ELECTRONIC COURT PROCUREMENT                              Page 21 of 249
                                                             FUNCTIONAL REQUIREMENTS

                                                                    CASE INITIATION AND INDEXING

      ID                                     Requirement Text                                        Response Code   Comments
CII-070.04       Provide USER with the ability to assign Documents[intake, petition] to          0
                 case.
CII-070.05       Provide ADMIN USER the ability to define rules for required fields for          0
                 electronic documents.
CII-071      Accommodate different types of case initiation filings for juvenile case
             categories (e.g., types of filings for child abuse and neglect cases differ
             from those for delinquency and status cases, various informal processes
             can initiate cases).
CII-071.01       Provide ADMIN USER with the ability to define CASE TYPES/SUB-                   0
                 TYPE.
CII-071.02       Provide ADMIN USER with the ability to locally define workflow                  0
                 process for each CASE TYPE/sub-type.
CII-071.03       Provide USER with the ability to assign CASE TYPE/SUB-TYPE (pick                0
                 from lookup table).
CII-072      Establish link between each juvenile and his or her family.

CII-072.01      Provide ADMIN USER with the ability to define PARTY relationships                0
                types.
CII-072.02      Provide ADMIN USER with the ability to assign valid PARTY                        0
                Relationship types for PARTY TYPE pairs.
CII-072.03      Provide USER with the ability to assign many (Person to Person)                  0
                Relationships between the same 2 Persons on the same case.
CII-072.04      Provide USER with the ability to assign an end date to a (PARTY to               0
                PARTY) Relationship on a Case.
CII-073      Create identifier for family or familial unit.

CII-073.01       Provide USER with the ability to define Unique Family IDs.                      0
CII-074      Supplement information entered during intake with additional information
             on juveniles, families, and other parties.
CII-074.01       Provide USER with the ability to add supplemental to intake                     0
                 information for all parties.
CII-075      Identify most serious allegation among group of allegations for given juvenile in
             delinquency case categories and designate other allegations as of lesser
             seriousness.
CII-075.01       Provide USER with the ability to easily identify the most serious               0
                 allegation among group of allegations.


      MDEC Procurement K11-0030-29                                                                                     September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 22 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                CASE INITIATION AND INDEXING

      ID                                    Requirement Text                                      Response Code   Comments
CII-075.02        Provide USER with the ability to designate seriousness/weight age to        0
                  all allegations.
CII-076      Enter each count and its identifier and correlate with allegation(s) within
             group of allegations in delinquency case categories.
CII-076.01        Provide USER with the ability to correlate Counts and its identifier with   0
                  one or many allegations within a group of allegations.
CII-077      Inform USER when situations exist for persons in new case that USER
             should be aware of (e.g., criminal charges or restraining orders against a
             parent, attorney conflict of interest) and identify situation to extent
             information in system.
CII-077.01        Provide ADMIN USER with the ability to define rules regarding which         0
                  types of cases/charges are reported to USER upon case initiate.
CII-077.02        Provide ADMIN USER with the ability to define rules regarding which         0
                  types of cases are subject to USER alerts upon initiate.
CII-077.03        Provide ADMIN USER with the ability to define rules regarding               0
                  minimum search criteria for PARTY search, e.g. name and D.O.B.
CII-077.04        AUTOMATICALLY perform a search of database for existing cases               0
                  involving PARTY)ies to case in accordance with locally defined rules.
CII-077.05        Alert USER when existing case(s) exist for identified PARTY.                0
CII-077.06        Provide USER with the ability to search database for cases involving        0
                  PARTY(ies) to case from within case initiate module.
CII-077.07        Provide USER with the ability to choose which PARTY(ies) to case to         0
                  run search.
CII-077.08        Provide USER with the ability to import selected information regarding      0
                  existing cases, e.g. case header information, caseID, case type, etc.
                  into case being initiated.
CII-077.09        Provide USER with the ability to ignore any automatic alerts regarding      0
                  existing cases for identical PARTY(ies) to case being initiated.

CII-077.10       AUTOMATICALLY search database for attorney(ies) who might                    0
                 represent opposing parties.
CII-077.11       Alert USER when existing case(s) exist where attorney represents             0
                 opposing PARTY(ies).
CII-077.12       ALSO SEE SCHEDULING.                                                         0
CII-078      Assign judge to case on case initiation or per local business rules (e.g.,
             manual or random assignment).


      MDEC Procurement K11-0030-29                                                                                  September 1, 2010
                                                MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                  MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 23 of 249
                                                         FUNCTIONAL REQUIREMENTS

                                                              CASE INITIATION AND INDEXING

      ID                                    Requirement Text                                    Response Code   Comments
CII-078.01        Provide ADMIN USER with the ability to globally define types of Judge     0
                  assignment.
CII-078.02        Provide USER with the ability to assign a Judge or multiple Judges        0
                  (see en banc review) to a case or group of cases.
CII-078.03        Provide ADMIN USER with the ability to define local business rules        0
                  regarding manual or automatic assignment of judges, e.g. random
                  assignment, rotation, etc.
CII-078.04        Provide USER with the ability to select judge assignment in               0
                  accordance with locally defined rules.
CII-079      Alert specified USERs to verify case is filed in the proper jurisdiction or
             retains jurisdiction from an external source.
CII-079.01        Provide ADMIN USER with the ability to define rules regarding which       0
                  types of cases are subject to verification process.
CII-079.02        Provide USER with the ability to check location of offense against this   0
                  jurisdiction.
CII-079.03        Alert USER when location information conflicts with this jurisdiction.    0
CII-079.04        Allow USER to assign previous case origin information into case being     0
                  initiated.
CII-080      Assign separate identifier or receive identifier for each defendant from
             Criminal Justice (CJ) agency (e.g., driver‘s license number, biometric or
             SSN).
CII-080.01        Allow USER to enter unique identifiers for PARTY(ies) to case, e.g.       0
                  SS#, Driver's License, D.O.B., Inmate Number, etc.
CII-081      Constant data carried forward to subsequent screens (e.g., defendant,
             citation and/or case number).
CII-081.01        Allow ADMIN USER to define which information is displayed on each         0
                  data entry screen, I.e., selected information from case header.
CII-081.02        Allow ADMIN USER to define rules regarding which type of information      0
                  is displayed on screen depending upon CASE TYPE, nature of action,
                  etc.
CII-082      Enter or track all relevant Originating Agency Identifier (ORI) codes.

CII-082.01       Allow ADMIN USER to define codes for originating court or agency.          0
CII-082.02       Allow USER to assign originating court of agency codes to case upon        0
                 case initiate.
CII-082.03       Maintain record of all originating court or agencies for case.             0


      MDEC Procurement K11-0030-29                                                                                September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 24 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                CASE INITIATION AND INDEXING

      ID                                   Requirement Text                                       Response Code   Comments
CII-083      Ability to use the mandatory Federal Information Processing Standards
             (FIPS) for geographic location of offense.
CII-083.01        AUTOMATICALLY use FIPS for geographic locations.                           0
CII-084      Ability for user management team to define statute/ ordinance tables (e.g.,
             offense code, descriptive text, bail amount, model driver violation code,
             effective and expiration date, severities,) as well as NCIC (National Crime
             Information Center)
CII-084.01        Provide ADMIN USER with the ability to globally define codes for           0
                  statutes, including CJIS codes, statute codes, statute descriptions,
                  effective date, rescission date, charging language, penalty information
                  etc.
CII-084.02        Provide ADMIN USER with the ability define a central repository for        0
                  criminal statutes.
CII-084.03        Provide ADMIN USER with the ability to define codes for                    0
                  NCIC(National Crime Information Center) data sets (party
                  demographics)
CII-084.04        AUTOMATICALLY maintain record of changes to CJIS codes, statute            0
                  codes, statute descriptions, effective date, rescission date, etc.

CII-085      Provide the ability to define validation criteria for specific fields, events, and
             work flow processes at the local level.
CII-085.01       Provide ADMIN USER with the ability to locally define validation criteria. 0

CII-085.02        Provide ADMIN USER with the ability to locally define workflow             0
                  processes.
CII-086      Provide the use of ―pick lists‖ where data values may be chosen from a
             discrete list.
CII-086.01        Provide ADMIN USER with the ability to define lookup tables.               0
CII-086.02        Provide USER with the ability to search lookup tables based on             0
                  context.
CII-087      Ability to edit citations and track changes during case initiation when it is
             entered in error (with appropriate security).
CII-087.01        Provide ADMIN USER with the ability to define rules regarding USER's       0
                  ability to make edits to previously entered citations/charges and error
                  correction. (SECURITY).



      MDEC Procurement K11-0030-29                                                                                  September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                       ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                              Page 25 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                CASE INITIATION AND INDEXING

      ID                                      Requirement Text                                     Response Code   Comments
CII-087.02         Provide USER with the ability to edit citations/charges or make             0
                   correcting entry (error) based on security settings/rules as determined
                   by ADMIN USER.
CII-087.03         AUTOMATICALLY maintain record of all edits (previous                        0
                   citation/charge information, USER login, USER date).
CII-087.04         Provide ADMIN USER with the ability to define REPORT of edits/error         0
                   corrections.
CII-087.05         Provide USER with the ability to produce a REPORT of any                    0
                   edits/corrections to charges/citations.
CII-087.06         Provide a mechanism to report edits/corrections to appropriate              0
                   agency(ies), e.g. CJIS reporting.
CII-088      Provide the ability to have USER-defined types of cases (e.g., traffic,
             parking, criminal traffic, civil and other).
CII-088.01         Provide ADMIN USER with the ability to locally define codes for CASE        0
                   TYPEs (nature of action).
CII-088.02         Provide USER with the ability to select CASE TYPE code(s) upon case         0
                   initiate.
CII-089      Ability to enter all (up to an unlimited number) charges (initial and modified)
             filed at case initiation and subsequently.
CII-089.01         Provide USER with the ability to assign an unlimited number of              0
                   charges to case, both upon initiation and subsequently.
CII-090      Initiate case with minimal information to be updated later (e.g., allows
             cases initiated with cash bail, forfeiture information and bonds) and then
             flag these incomplete cases and track them.
CII-090.01         Provide ADMIN USER with the ability to define rules regarding               0
                   required fields when entering information such as bail bond
                   information, etc.; required PARTY TYPEs, required charges,
                   motion/document, etc.
CII-090.02         Provide USER with the ability to assign limited or incomplete               0
                   information on case initiate without undoing initiate process.
CII-090.03         Provide ADMIN USER to define REPORT of incomplete case                      0
                   initiations, bail bond information, etc.
CII-091      Provide the ability to produce text and bar code labels, RFID tags, or future
             technology for attachment to case folders, for documents to be served, and
             for subsequent manual filings.
CII-091.01         Provide for bar-coding, etc. for case folders.                              0


      MDEC Procurement K11-0030-29                                                                                   September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 26 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                               CASE INITIATION AND INDEXING

      ID                                       Requirement Text                                  Response Code   Comments
CII-091.02         Print bar code on case folders, notices, summons, etc. or other system-   0
                   generated documents.
CII-091.03         Print bar code on any cover sheets associated with manual filings.        0
CII-091.04         Associate/insert bar code on scanned document images.                     0
CII-092      Allow a USER to stop, exit or place the case on hold once the case
             initiation work flow has begun. This process must consider the case flow
             clock performance statistics are not distorted.
CII-092.01         Provide ADMIN USER with the ability to globally define rules for          0
                   starting/stopping/suspending the case initiation while maintaining the
                   proper case flow measurements.
CII-092.02         Provide USER with the ability to assign start, suspend, stop events to    0
                   case during case initiation
CII-093      Allow the Commissioner to set the date for temporary order based upon
             setting parameters, and initiate the case. The clerk would then finish case
             initiation, e-file to police for database, e-file service of process request.

CII-093.01        Provide USER with the ability to take filing fees for DV case.             0
CII-093.02        Provide USER with the ability to set hearing date for final order.         0
CII-093.03        Provide USER with the ability to assign parties to case (case initiate     0
                  process).
CII-093.04        Provide USER with the ability to electronically commit temporary           0
                  DV/Peace Order to database (DVCR process).
CII-093.05        Provide USER with the ability to electronically commit record of service   0
                  to database.
CII-094      Enable charging documents initiated by law enforcement agencies to be
             filed with the commissioner electronically.
CII-094.01        Provide USER with the ability to electronically commit charging            0
                  document(s) to database.
CII-094.02        Provide USER with the ability to view/print charging documents that        0
                  have been electronically filed.
CII-095      Provide automatic checking of previous judgments on the warrants or
             restitution to ensure that the appropriate number of prior judgments were
             received.
CII-095.01        AUTOMATICALLY check previous judgments for landlord and tenant             0
                  failure to pay claims when warrants of restitution are filed to ensure
                  that the appropriate number of prior judgements were received.


      MDEC Procurement K11-0030-29                                                                                 September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 27 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                CASE INITIATION AND INDEXING

      ID                                    Requirement Text                                      Response Code   Comments
CII-096      Provide the ability to link juvenile and criminal history data between the
             juvenile justice system and the courts.

CII-096.01       Provide USER with the ability to link cases between the juvenile justice 0
                 system and the courts.
CII-097      Provide ability to set parameters for pre-trial release.

CII-097.01        Provide ADMIN USER with the ability to define rules for parameters for      0
                  pre-trial release dates.
CII-098      Provide the ability to allow all victims associated with the same defendants
             or respondents to be linked, and all defendants or respondents with the
             same victim linked.
CII-098.01        Provide USER with the ability to link parties from among one to many        0
                  CASES.
CII-098.02        Provide USER with the ability to view associated parties, e.g.              0
                  defendant and all victims; victim and all defendants.
CII-099      Provide the ability to identify links between TPR and CINA cases for the
             same child, and track the case from TPR to adoption.
CII-099.01        Provide ADMIN USER with the ability to define relationships between         0
                  CASE TYPES.
CII-099.02        Provide ADMIN USER with the ability to define unique identifiers for        0
                  PARTY(ies).
CII-099.03        Provide USER with the ability to link related CASES.                        0
CII-099.04        Provide USER with the ability to view one to many related cases from        0
                  within each related CASE.
CII-099.05        Provide USER with the ability to view/print case histories for related      0
                  cases in a single document.
CII-100      Provide the ability to ensure that multiple citations/arrests of the defendant
             in the same case/case number with different tracking dates and/or tracking
             numbers are not allowed.
CII-100.01        Provide ADMIN USER with the ability to define RULES for data                0
                  validation when entering multiple cases for the same defendant
CII-101      The system must use the check digit to verify the arrest tracking number
             entered.
CII-101.01        AUTOMATICALLY perform checksum to validate arrest tracking                  0
                  number as assigned by USER.


      MDEC Procurement K11-0030-29                                                                                  September 1, 2010
                                                MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                   ATTACHMENT C
                                                  MARYLAND ELECTRONIC COURT PROCUREMENT                          Page 28 of 249
                                                         FUNCTIONAL REQUIREMENTS

                                                             CASE INITIATION AND INDEXING

      ID                                   Requirement Text                                  Response Code   Comments
CII-102      The system must support shielding done either by request or by motion or
             order.
CII-102.01       Provide ADMIN USER with the ability to define RULES regarding           0
                 shielding of certain information (See MD Rule 16-1009).
CII-102.02       Provide USER with the ability to shield information pursuant to Md      0
                 Rule 16-1009.
CII-102.03       AUTOMATICALLY prevent public access to shielded information.            0
CII-103      The system should utilize OCR or similar technology in order to utilize
             scanned images to populate data fields.
CII-103.01       Provide ADMIN USER with the ability to develop OCR forms, cover         0
                 sheets and separator sheets for the purpose of electronically
                 populating the database with meta-data.
CII-103.02       Provide USER with the ability to scan OCR documents                     0
CII-103.03       Provide USER with the ability to verify meta-data from scanned OCR      0
                 forms before committing to the database
CII-104      The system should provide notices to all parties as requested at
             milestones in case
CII-104.01       Provide ADMIN USER with the ability to locally define tracks for        0
                 differentiated case management, including deadlines for discovery,
                 pleading, and automatic scheduling of hearing/trial.
CII-104.02       Provide ADMIN USER with the ability to associate tracks for selected    0
                 CASE TYPEs.
CII-104.03       Provide USER with the ability to assign tracks to one to many cases.    0
CII-104.04       Provide USER with the ability to override track milestones for one to   0
                 many cases.
CII-104.05       Provide USER with the ability to update track milestones.               0
CII-104.06       Provide USER with the ability to modify track assignment for one to     0
                 many cases.
CII-104.07       Provide a mechanism for reporting compliance with track milestones      0
                 for one to many cases (statistical reporting).
CII-104.08       Provide USER with the ability to remove one to many cases from          0
                 previously assigned track.
CII-104.09       AUTOMATICALLY generate notices to parties for all scheduled event       0
                 milestones.
CII-105      The system must enable Domestic Violence Order Templates to be
             created and issued from system.


      MDEC Procurement K11-0030-29                                                                             September 1, 2010
                                                MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                     ATTACHMENT C
                                                  MARYLAND ELECTRONIC COURT PROCUREMENT                            Page 29 of 249
                                                         FUNCTIONAL REQUIREMENTS

                                                              CASE INITIATION AND INDEXING

      ID                                    Requirement Text                                   Response Code   Comments
CII-105.01        Provide USER with the ability to access domestic violence order          0
                  templates on demand.
CII-105.02        Provide USER with the ability to maintain copies of all previous         0
                  versions for domestic violence order templates
CII-105.03        Provide USER with the ability to access all previous completed           0
                  domestic violence orders
CII-105.04        INTERFACE to Domestic Violence Central Repository                        0
CII-106      The system must enable templates for Orders for CINA, TPR and adoption
             milestones to meet federal compliance.
CII-106.01        AUTOMATICALLY capture outcomes from hearings in CINA, TPR and            0
                  adoption cases , statistics etc.
CII-106.02        Provide ADMIN USER with the ability to define order templates .          0
CII-107      Exclude ―special‖ CASE TYPEs from the time standards with reason built
             into CMS. (e.g. domestic violence, emergency petitions consent
             judgments liens).
CII-107.01        Provide ADMIN USER with the ability to define rules regarding cases      0
                  to be included in CTS reporting.
CII-107.02        Provide ADMIN USER with the ability to define CASE TYPES/sub-            0
                  types subject to CTS process.
CII-107.03        Define Alias for Criminal – Rule Review not an AKA when just a data      0
                  entry error.
CII-108      Electronic exchange of data in regards to service of warrants and other
             service documents. (DV, Juvenile and other domestic cases).
                  Provide ADMIN USER with the ability to define which document             0
                  require service
CII-108.01        AUTOMATICALLY exchange data on service of warrants and other             0
                  documents across cases and juridictions.
CII-109      The system should provide the capability to receive Foreign DV Orders and
             capture them so they can be reported on.
CII-109.01        Provide USER the ability to enter Foreign (out of state) Domestic        0
                  Violence orders from outside a jurisdiction and ensure they are
                  counted in reports accurately.
CII-110      The system should allow for the identification of frequent party or filers.

CII-110.01       Provide ADMIN USER with the ability to locally define "frequent party"    0
                 table, including PARTY name, address, etc.


      MDEC Procurement K11-0030-29                                                                               September 1, 2010
                                                MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                    ATTACHMENT C
                                                  MARYLAND ELECTRONIC COURT PROCUREMENT                           Page 30 of 249
                                                         FUNCTIONAL REQUIREMENTS

                                                              CASE INITIATION AND INDEXING

      ID                                   Requirement Text                                   Response Code   Comments
CII-110.02       Provide USER with the ability to add frequent PARTY to case from         0
                 lookup, including PARTY name, address, etc.
CII-111      CMS must allow for rule changes in relationship to public access and
             changes on services to parties.
CII-111.01       Provide ADMIN USER with the ability to globally define rules regarding 0
                 public access/confidentiality of case records by CASE TYPE, e.g.
                 confidential/sealed at case initiate.
CII-111.02       Provide ADMIN USER with the ability to define rules regarding service 0
                 on parties, e.g. time for filing response, etc. based upon changes in
                 statute.
CII-112      CMS must be accessible and accommodate all customers with ADA and or
             customers requiring an interpreter. All forms translated for interpretation.

CII-112.01       Provide all USERS with disabilities access to the system alternate      0
                 translations based on disability.
CII-113      Service and manner of notification in all CASE TYPEs must be modifiable
             depending on the case or PARTY TYPE.
CII-113.01       Provide ADMIN USER with the ability to define rules regarding service   0
                 on parties, e.g. time for filing response, etc. based upon CASE TYPE.

CII-114      The system should enable for there to be a case information form that may
             be or may not be required to be filed with each case.
CII-114.01       Provide ADMIN USER with the ability to define rules for requiring the   0
                 filing of a Case Information form for case filings and response.
CII-115      The system should provide the ability to view and print a work flow map for
             any case.
CII-115.01       Provide USER the ability to view and print work flow maps for any case 0
                 or specific business process.
CII-116      The system should enable a user to refuse acceptance of a case based on
             a Maryland Rule.
CII-116.01       Provide ADMIN USER with the ability to define a rule to allow a clerk to 0
                 refuse to accept and file a paper presented for filing.
CII-117      When there are multiple cases such as DV, Juvenile and Criminal, the
             system should allow cases to be heard together or separately.
CII-117.01       Provide USER with the ability to define a rule to allow a cases to be    0
                 heard together or separately.


      MDEC Procurement K11-0030-29                                                                              September 1, 2010
                                                   MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                        ATTACHMENT C
                                                     MARYLAND ELECTRONIC COURT PROCUREMENT                               Page 31 of 249
                                                            FUNCTIONAL REQUIREMENTS

                                                                 CASE INITIATION AND INDEXING

      ID                                    Requirement Text                                         Response Code   Comments
CII-118      Allow case searches by attorney (include court date, courtroom, case
             number, judge in search criteria).
CII-118.01        Provide ADMIN USER with the ability to define a rule for search criteria       0
                  based on a field or combination of fields (including attorney, court date,
                  courtroom, case number, judge).
CII-119      Address detail population, user provides zip code, system provide city,
             state, county, country. (US only)
CII-119.01        AUTOMATICALLY populate address fields based on zip code.                       0
CII-120      Allow entering of confessed, recorded and foreign judgments, bond
             forfeiture and restitution, municipal infractions during case initiate, including
             generating associated notices and entering attorneys.
CII-120.01        Provide ADMIN USER with the ability to locally define rules for                0
                  required/optional modules (screens) that are included in the case
                  initiate process ( e.g. confessed, recorded and foreign judgments,
                  bond forfeiture and restitution, and municipal infractions.
CII-120.02        Provide ADMIN USER with the ability to define a rule for generating            0
                  notices.
CII-121      Allow for flagging cases with pending confessed judgments

CII-121.01       Provide ADMIN USER with the ability to define a rule for flagging               0
                 cases with pending confessed judgments
CII-122      Allow for entering each requested relief based on case category and permit
             each relief to have an associated disposition
CII-122.01       Provide ADMIN USER with the ability to locally define Relief Code               0
                 types.
CII-122.02       Provide ADMIN USER with the ability to locally assign a Relief Code             0
                 type to many Case Category types.
CII-122.03       Provide ADMIN USER with the ability to locally define Relief                    0
                 Disposition Code types.
CII-122.04       Provide ADMIN USER with the ability to locally assign a Relief                  0
                 Disposition Code type to many Relief Code types.
CII-122.05       Provide USER with the ability to assign many Relief(s) to a Case.               0
CII-122.06       Provide USER with choices of Relief Codes that will validate against            0
                 the Case Category Type of the Case.
CII-122.07       Provide USER with the ability to assign many Relief Disposition(s) to a         0
                 Relief.


      MDEC Procurement K11-0030-29                                                                                     September 1, 2010
                                                MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                   ATTACHMENT C
                                                  MARYLAND ELECTRONIC COURT PROCUREMENT                          Page 32 of 249
                                                         FUNCTIONAL REQUIREMENTS

                                                             CASE INITIATION AND INDEXING

      ID                                 Requirement Text                                    Response Code   Comments
CII-122.08       Provide USER with choices of Relief Dispositions that will validate   0
                 against the Relief Code Type of the Relief.
CII-123      The system must enable configuarion of which case events to allow certain
             events to be excluded from the case flow clock performance statistics so
             they are not distorted
CII-123.01       Provide ADMIN USER the ability to configure case events that should 0
                 be excluded from the case age clock so statistics are not distorted.

CII-124      Ability to enter other identifying numbers associated with the case (e.g.
             district court case number, AA agency case number, WCC case number.
CII-124.01       Provide ADMIN USER with the ability to define codes for different      0
                 types of identifying numbers.
CII-124.02       Provide USER with the ability to assign other identifying numbers to a 0
                 case.
CII-125      Receive booking, arrest, custody, bail information with individual
             identification information. (see Case Initiation and Indexing Function)
CII-125.01       INTERFACE other agencies to CASE.                                      0
CII-126      Incorporate CJIS Code (Charging Language) database so that all
             applicable USERs can access. (Commissioners, Clerks, Circuit Court, etc.)

CII-126.01      Provide USER with the ability to view CJIS Code data base.               0
CII-127      Enable CJIS Code database to be updated from one source. Updates
             should then be AUTOMATICALLY updated throughout CMS.
CII-127.01      Security ADMIN grant update privileges to CJIS database from CMS         0
                programs.
CII-127.02      INTERFACE CJIS database to CASE.                                         0




      MDEC Procurement K11-0030-29                                                                             September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                       ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                              Page 33 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                DOCKETING, RECORD KEEPING

     ID                                    Requirement Text                                        Response Code   Comments
DRK-001      Allow easy entry of multiple filings that apply to single case or related cases
             (e.g., consecutive entry of multiple pleadings for single case).

DRK-001.01        Provide USER with the ability to assign many FILINGS to a single       0
                  CASE.
DRK-002      Enter information once and apply to multiple cases or persons upon
             confirmation by user (e.g., single entry for several parties with same
             attorney or address; copy docket entry to related cases; single entry when
             parties or attorneys have different roles in different cases such as party
             who is petitioner in one case and respondent in another case or attorney
             who is counsel in one case or guardian ad litem in another case), including
             checks to ensure changes are not applied to wrong cases or people.

DRK-002.01        Provide USER with the ability to assign a single FILING to multiple          0
                  CASES.
DRK-002.02        Provide ADMIN USER with the ability to define rule for ensuring              0
                  correct CASES are updated when updating multiple CASES at once.
DRK-002.03        Provide USER with the ability to confirm the automatic assignment of         0
                  information to related CASES.
DRK-002.04        Provide USER with the ability to assign with ease new associations           0
                  between existing CASES, PERSONS and EVENTS.
DRK-002.05        AUTOMATICALLY assign new information on a CASE to another                    0
                  related CASE.
DRK-003      Track and display or produce reports on relationship of specific cases and
             parties to one or more service providers, (e.g., domestic relations service
             providers, child support agencies, child welfare agencies, other
             governmental agencies (including referral information such as requester,
             mediator, type of referral [e.g., court ordered or petition], reason for
             referral, date of referral and subsequent report, noncompliance
             information, funds involved) and other participants.
DRK-003.01        Provide USER with the ability to display the relationship between            0
                  CASES and PARTIES to one or more SERVICE PROVIDERS.
DRK-003.02        Provide ADMIN USER with the ability to define types of SERVICE               0
                  PROVIDERS (e.g. domestic relations service providers, child support
                  agencies, child welfare agencies).
DRK-003.03        Provide ADMIN USER with the ability to define types of referrals (e.g.       0
                  court ordered or petition)

     MDEC Procurement K11-0030-29                                                                                    September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 34 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                DOCKETING, RECORD KEEPING

     ID                                     Requirement Text                                      Response Code   Comments
DRK-003.04       Provide ADMIN USER with the ability to define types of referral              0
                 reasons.
DRK-003.05       Provide ADMIN USER with the ability to globally define type                  0
                 associations between SERVICE PROVIDERS and COURT TYPE,
                 CASE CATEGORIES and CASE TYPES.
DRK-003.06       Provide ADMIN USER with the ability to locally define type                   0
                 associations between SERVICE PROVIDERS and COURT TYPE,
                 CASE CATEGORIES and CASE TYPES.
DRK-003.07       Provide USER with the ability to assign referral information such as:        0
                 requestor, mediator, type of referral, reason for referral, date of
                 referral, subsequent report dates, non compliance information, funds
                 involved to a CASE.
DRK-003.08       Provide USER with the ability to assign a relationship between a             0
                 SERVICE PROVIDER and a PARTY.
DRK-004      Provide capability to print or display template forms/notices with and
             without entered data, including partial printing of documents or batch jobs.

DRK-004.01        Provide USER with the ability to display form/notices templates          0
                  containing CASE data.
DRK-004.02        Provide USER with the ability to display form/notices templates without 0
                  CASE data.
DRK-004.03        Provide USER with the ability to display partial documents.              0
DRK-005      Maintain case information originally entered during case initiation in docket
             or register of actions including information on initial filing and basic case
             information, as well as information that supplements these initial entries.

DRK-005.01        Provide USER with the ability to assign additional CASE information         0
                  after completion of case initiation.
DRK-006      Maintain information originally entered during case initiation for parties and
             participants as individuals (e.g., Ann Smith) or organizations (e.g., Acme
             Asbestos Company) with primary contact person if organization.
DRK-006.01        Provide USER with the ability to assign additional CASE                     0
                  PARTICIPANT information after case initiation.
DRK-006.02        Provide USER with the ability to assign organizations as a CASE             0
                  PARTICIPANT.
DRK-006.03        Provide USER with the ability to assign multiple contact persons for        0
                  organizations.

     MDEC Procurement K11-0030-29                                                                                   September 1, 2010
                                                MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                     ATTACHMENT C
                                                  MARYLAND ELECTRONIC COURT PROCUREMENT                            Page 35 of 249
                                                         FUNCTIONAL REQUIREMENTS

                                                              DOCKETING, RECORD KEEPING

     ID                                     Requirement Text                                   Response Code   Comments
DRK-007      Create docket entry and update case information based on occurrence of
             specific events (defined by case type, court, event) that can be completely
             or partially transferred from another function such as hearing scheduled
             (e.g., motion granted or denied; see also Calendaring Function), hearing
             results (e.g., summary judgment; see also Hearings Function), dispositions
             (e.g., disposition date, type of disposition, information on judgment; see
             also Disposition Function and Accounting - Back Office Function), and
             requests for enforcement of judgment.
DRK-007.01        Provide USER with the ability to assign a docket entry to the case.      0
DRK-007.02        Provide ADMIN USER with the ability to define specific events based      0
                  on court type, case category, case type , case sub categories.
DRK-007.03        Provide USER with the ability to assign docket entries to a case based   0
                  on event information completely or partially transferred from another
                  function.
DRK-007.04        Provide ADMIN USER with the ability to define types of events that       0
                  create docket entries
DRK-007.05        Provide ADMIN USER with the ability to define type associations          0
                  between docket entries and events
DRK-007.06        Provide ADMIN USER with the ability to locally define rules for          0
                  configuring docket entry content.
DRK-008      Create docket entry based on electronic documents distributed by other
             functions (e.g., notices, warrants, orders). (see also Document Generation
             and Processing Function, Hearings Function, and Disposition Function).

DRK-008.01       Provide ADMIN USER with the ability to define type of electronic          0
                 documents.
DRK-008.02       Provide ADMIN USER with the ability to define type associations           0
                 between electronic documents and docket entries.
DRK-008.03       Provide USER with the ability to assign docket entry to the case based    0
                 on type of electronic document.
DRK-008.04       AUTOMATICALLY assign a docket entry after generation of electronic        0
                 document.
DRK-008.05       Provide USER with the ability to track referrals to non-court agencies.   0
DRK-008.06       Maintain record of all referrals made to non-court agencies.              0
DRK-008.07       Provide USER with the ability to assign deadlines to agency referrals.    0



     MDEC Procurement K11-0030-29                                                                                September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 36 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                                DOCKETING, RECORD KEEPING

     ID                                    Requirement Text                                      Response Code   Comments
DRK-009      Permit user to identify and retrieve electronic documents by identifying
             them on each detailed list of docket events (e.g., with icon or link adjacent
             to event such as motion for dismissal filed indicating that motion filed
             electronically) and easy display or printout of electronic document (e.g.,
             motion that was filed) as well as simple return to document list.

DRK-009.01       Provide USER with the ability to search case docket entries.                0
DRK-009.02       Provide USER with the ability to sort case docket entries.                  0
DRK-009.03       Provide USER with the ability to display case docket entries along with     0
                 an indicator for electronic documents.
DRK-009.04       Provide USER with the ability to display the content of manually            0
                 selected electronic documents from a list.
DRK-009.05       Provide ADMIN USER with the ability to define display fields                0
                 representing the list of electronic documents.
DRK-009.06       Provide USER with the ability to view the case docket entry list.           0
DRK-010      Allow single event to create multiple docket entries (e.g., event is hearing;
             docket entries are attorney withdrawal and hearing results).

DRK-010.01       Provide USER with the ability to assign multiple docket entries arising     0
                 from a single event.
DRK-010.02       Provide ADMIN USER with the ability to define rules determining the         0
                 docket entries that should be created from a single event.
DRK-011      Enter, maintain, and display or print information on special case processing
             requirements or orders, with proper security (e.g., sealed case or
             document, sealed addresses, sealed parties, etc.), including confidential
             record checks. When accessing a case, alert the judicial officer that
             confidential information exists.
DRK-011.01       Provide ADMIN USER with the ability to globally define rules for            0
                 secured CASE information.
DRK-011.02       Provide USER with alerts when accessing a CASE containing secured           0
                 data.
DRK-011.03       Provide USER with the ability to assign security indicators to a CASE,      0
                 PERSON or EVENT.
DRK-012      Maintain case information as official court record in accordance with state
             and local statutes or rules.



     MDEC Procurement K11-0030-29                                                                                  September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                        ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                               Page 37 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                 DOCKETING, RECORD KEEPING

     ID                                     Requirement Text                                        Response Code   Comments
DRK-012.01        Provide ADMIN USER with the ability to define rules for determining           0
                  what data is to be included in the official Court Record.
DRK-013      Maintain individual information on multiple parties, participants, and
             attorneys in a case such as personal information, status including
             bankruptcy, dismissals, current addresses, address histories, voice and
             facsimile telephone numbers, e-mail addresses, interpreter requirements,
             role, military service status, etc.
DRK-013.01        Provide USER with the ability to assign: party bankruptcy status, party       0
                  dismissal status, address, address history, voice and facsimile
                  numbers, email addresses, interpreter requirements, party type,
                  military service status.
DRK-013.02        Provide ADMIN USER with the ability to define type of party statuses          0
                  (e.g. bankruptcy, military, dismissed).
DRK-013.03        Provide ADMIN USER with the ability to define type of interpreter             0
                  languages.
DRK-014      Enter, change, or withdraw attorneys for specific cases (or groups of
             cases) or parties (or groups of parties) with dates when active and inactive,
             including the ability to remove attorney appearances in batch, either user
             controlled/initiated or automatic.
DRK-014.01        Provide USER with the ability to assign attorneys start date for specific     0
                  cases (or groups of cases) or parties (or groups of parties).
DRK-014.02        Provide USER with the ability to maintain history of attorney                 0
                  appearances.
DRK-014.03        Provide USER with the ability to assign attorneys end date for specific       0
                  cases (or groups of cases) or parties (or groups of parties).
DRK-014.04        Provide ADMIN USER with the ability to define a rule to assign                0
                  attorney end dates.
DRK-014.05        Provide USER with the ability to manually assign attorney end dates.          0
DRK-014.06        Provide ADMIN USER with the ability to globally define rules for              0
                  AUTOMATICALLY assigning attorney end dates.
DRK-015      Maintain information on law firms and associate attorneys and firms,
             including identifying out of state attorneys (e.g., to permit mail to be sent to
             each attorney in a firm, to list all cases being handled by a specific firm or
             attorney).
DRK-015.01        Provide ADMIN USER with the ability to define central repositories for        0
                  ATTORNEY.


     MDEC Procurement K11-0030-29                                                                                     September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 38 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                               DOCKETING, RECORD KEEPING

     ID                                    Requirement Text                                      Response Code   Comments
DRK-015.02        Provide ADMIN USER with the ability to define central repositories for     0
                  ATTORNEY/ LAW FIRMS.
DRK-015.03        Provide ADMIN USER with the ability to define codes to associate           0
                  ATTORNEYS and LAW FIRMS.
DRK-015.04        Provide USER with the ability to report CASES assigned by a specific       0
                  firm or attorney.
DRK-015.05        Provide USER with the ability to assign a unique identifier to             0
                  ATTORNEY (even when the attorney does not practice in the state of
                  Maryland).
DRK-015.06        Provide USER with the ability to search cases and events related to a      0
                  individual or a Law Firm.
DRK-015.07        Provide ADMIN USER with the ability to define to field(s) for querying     0
                  CASES and EVENTS for Attorneys and Law Firms.
DRK-015.08        Provide ADMIN USER with the ability to define fields that are displayed    0
                  in the search results.
DRK-015.09        Provide USER with the ability to search for out of state attorneys.        0
DRK-015.10        Provide USER with the ability to relate Attorneys to one or more Law       0
                  Firms.
DRK-015.11        Provide USER with the ability to assign general information about a        0
                  law firm.
DRK-016      Maintain, or be able to construct in a manner that requires minimal user
             action, information and relationships on multiple cases, judges, attorneys,
             and parties (e.g., option to designate lead attorney, attorney represents a
             single contact, transfer group of cases or parties from one judge or hearing
             date to another in single transaction) and establish relationships among
             parties and cases.
DRK-016.01        Provide ADMIN USER with the ability to globally define types of case       0
                  consolidation.
DRK-016.02        Provide ADMIN USER with the ability to globally define types of Judge      0
                  assignment.
DRK-016.03        Provide USER with the ability to assign consolidation type to a group of   0
                  CASES.
DRK-016.04        Provide USER with the ability to assign an attorney or multiple            0
                  attorneys as a lead attorney(s) for a CASE or group of consolidated
                  CASES.
DRK-016.05        Provide USER with the ability to assign a Judge or multiple Judges         0
                  (see en banc review) to a CASE or group of CASES.

     MDEC Procurement K11-0030-29                                                                                  September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                     ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                            Page 39 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                               DOCKETING, RECORD KEEPING

     ID                                   Requirement Text                                      Response Code   Comments
DRK-016.06        Provide USER with the ability to assign a hearing date (see Calendar)     0
                  to a CASE or group of consolidate or related CASES.
DRK-016.07        Provide USER with the ability to assign a hearing date to a PARTY or      0
                  multiple PARTIES in a CASE or group of consolidated or related
                  CASES.
DRK-017      Permit, with proper authorization (e.g., supervisor approval), deletion of
             specific docket entries and all related data (e.g., deletion of pleading and
             fee information causes related docket and accounting information to be
             deleted).


DRK-017.01       Provide USER with the ability to assign an indicator to any record that    0
                 indicates that the record was entered as error.
DRK-017.02       Provide ADMIN USER with the ability to define rule for displaying          0
                 records that have been marked as error.
DRK-018      Apply a specific change to multiple dockets, parts of dockets, or groups of
             cases as if they were a single docket or case (e.g., correction of fee entry
             causes fee distribution amounts to be modified, change of Judge Smith‘s
             courtroom causes all records containing old courtroom number to be
             changed to new courtroom number, transfer group of cases to new judge
             when former judge retires or conflict arises, transfer group of cases to
             another division).
DRK-018.01       Provide USER with the ability to select one or more CASES and apply        0
                 a specific change to all CASES selected.
DRK-018.02       Provide USER with the ability to select one or docket entries on one or    0
                 more CASES and apply a specific change to all docket entries
                 selected.
DRK-018.03       Provide ADMIN USER with the ability to define a rule on what changes       0
                 to what actions is allowed in interactive batch mode.
DRK-018.04       Provide ADMIN USER with the ability to define field(s) for querying        0
                 CASES or Docket Entries eligible for change.
DRK-018.05       Provide ADMIN USER with the ability to define field(s) that are            0
                 displayed in the search results.




     MDEC Procurement K11-0030-29                                                                                 September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                       ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                              Page 40 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                DOCKETING, RECORD KEEPING

     ID                                      Requirement Text                                      Response Code   Comments
DRK-019      Link and display information on docket entries for events related to current
             docket entry (e.g., ―life cycle‖ of a motion--when defendant files motion that
             opposes previously filed motion of plaintiff, defendant‘s motion would be
             linked to original plaintiff‘s motion filed, and new motion filed would be
             linked to all pending motions in case with information displayed on who
             filed motions, factors involved, and pending decisions).
DRK-019.01        Provide ADMIN USER with the ability to define rules regarding                0
                  relationships between documents based on document type (e.g.
                  complaint, answer, request)..
DRK-019.02        Provide USER with the ability to ―drill down‖ to obtain the details of all   0
                  data relationships to the case.
DRK-019.03        Provide ADMIN USER with the ability to define codes to associate             0
                  decision with document.
DRK-019.04        Provide USER with the ability to assign filing parties to document(s).       0
DRK-019.05        Provide USER with the ability to assign relationship between                 0
                  document(s).
DRK-019.06        Provide USER with the ability to assign decision to document.                0
DRK-019.07        Provide USER with the ability to sort for DOCUMENTS by type,                 0
                  decision, filing PARTY.
DRK-019.08        Provide ADMIN USER with the ability to define field(s) for querying all      0
                  docket entries.
DRK-019.09        Provide ADMIN USER with the ability to define fields that are displayed      0
                  in the docket entry results.
DRK-019.10        Provide USER with the ability to view with ease all relationships            0
                  associated with a selected docket entry.
DRK-019.11        Provide USER with the ability to search for all docket entries.              0
DRK-020      Provide configurable prompts to help users (e.g., locally-defined list of
             codes and translations that apply to data entry situation that currently
             confronts user, updates required in cases related to case being updated).
DRK-020.01        Provide USER with data entry features that offer options based on            0
                  context and allow USER to make one or many selections with ease.
DRK-020.02        Provide USER with data entry feature that offers valid options               0
                  preconfigured by an administrator.
DRK-020.03        Provide ADMIN USER with the ability to map a data entry field to a set       0
                  of options or codes.



     MDEC Procurement K11-0030-29                                                                                    September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                       ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                              Page 41 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                DOCKETING, RECORD KEEPING

     ID                                   Requirement Text                                         Response Code   Comments
DRK-020.04       Provide USER with data entry feature to navigate and select on nested 0
                 levels of code hierarchies, providing only valid options at each level.

DRK-021      Create, maintain, and produce (according to user-specified criteria such as
             selected workstation[s] or selected case[s]) audit trail identifying persons
             who made docket and other entries (including updates) and when they
             made entries (highlighting when filing occurred if filing and entry dates are
             different).
DRK-021.01        Provide ADMIN USER with the ability to locally define rule(s) defining       0
                  action to be taken when entry and filing dates are disparate.
DRK-021.02        Provide ADMIN USER with the ability to locally define REPORT for             0
                  object(s) (e.g. documents, scheduled events, parties, etc.) with
                  information such as entry date, filing date, party-to-object, etc.
DRK-021.03        Provide ADMIN USER with the ability to locally define fields that are        0
                  displayed on the report.
DRK-021.04        Provide USER with the ability to produce report for object(s) (e.g.          0
                  documents, scheduled events, parties, etc.).
DRK-021.05        AUTOMATICALLY assign system USER, create/update date and time                0
                  to every record.
DRK-022      Print or display all, part, or summaries of docket(s) (e.g., events in register
             of actions, all parties, summaries of judgment information, case age) for
             specific case or group of cases and for life of case or specific date range in
             chronological, reverse chronological, or docket sequential number order.

DRK-022.01       Provide USER with the ability to print the displayed view(s).                 0
DRK-022.02       Provide USER with the ability to select one or many CASES and                 0
                 produce selected views.
DRK-022.03       Provide ADMIN USER with the ability to define views of CASE                   0
                 information.
DRK-022.04       Provide ADMIN USER with the ability to define fields for querying on          0
                 different CASE views.
DRK-022.05       Provide ADMIN USER with the ability to define fields that are displayed       0
                 in the different CASE views.
DRK-022.06       Provide USER with the ability to select with ease one or more views to        0
                 display.



     MDEC Procurement K11-0030-29                                                                                    September 1, 2010
                                                   MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                     MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 42 of 249
                                                            FUNCTIONAL REQUIREMENTS

                                                                 DOCKETING, RECORD KEEPING

     ID                                     Requirement Text                                       Response Code   Comments
DRK-023      Support electronic filing (e.g., directly from attorneys‘ offices) of pleadings
             and other documents.

DRK-023.01        See E-FILING                                                                0
DRK-024      Maintain file of input templates available to users to create input
             documents and, as necessary, associated cover sheets (for use when
             pleadings are filed electronically) and relate each template to court event(s)
             (e.g., to correlate templates with events and to allow details of specific
             electronically filed complaint to be inserted into boilerplate text of complaint
             form for hard copy printout).
DRK-024.01        Provide ADMIN USER with the ability to define DOCUMENT templates. 0

DRK-025      Maintain and print or display history of changes in judge assignment
             including those by recusal and showing present and former judges, dates
             of assignment, and reasons for change.
DRK-025.01        Provide ADMIN USER with the ability to codes for types of Judge              0
                  Assignment.
DRK-025.02        Provide ADMIN USER with the ability to define codes for Judge                0
                  Assignment removal to case.
DRK-025.03        Provide USER with the ability to assign a Judge removal code to              0
                  Judge Assignment.
DRK-025.04        Provide ADMIN USER with the ability to define REPORT for Judge               0
                  Assignment history.
DRK-025.05        Provide USER with the ability to produce report for Judge Assignment         0
                  to CASE..
DRK-025.06        Provide USER with the ability to sort on Judge, type of Judge                0
                  Assignment, Assignment Date, Removal Reason, Removal Date.
DRK-025.07        Provide USER with the ability to assign JUDGE ASSIGNMENT to                  0
                  CASE.
DRK-026      Maintain and print or display history of attorney changes for specific case
             or party, including dates active/inactive and reason(s) for removal.

DRK-026.01       Provide ADMIN USER with the ability to globally define codes reasons          0
                 for attorney removal (e.g. case closed/inactivated, striking/substitution
                 of appearance).
DRK-026.02       Provide ADMIN USER with the ability to define REPORT on                       0
                 ATTORNEY/PARTY data.

     MDEC Procurement K11-0030-29                                                                                    September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 43 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                               DOCKETING, RECORD KEEPING

     ID                                   Requirement Text                                       Response Code   Comments
DRK-026.03       Provide USER with the ability to produce REPORT for                         0
                 ATTORNEY/PARTY data.
DRK-027      Enter and maintain information (e.g., document title and identifier,
             defendant and participant, fees collected) and dates on filings and other
             completed events not previously in system (e.g., participant added or
             deleted, plea entered, motion filed, or hearing date set).
DRK-027.01       Provide USER with the ability to assign past dates to events.               0
DRK-027.02       AUTOMATICALLY maintain system date (data entry date) for events             0
                 added to system.
DRK-028      Maintain information on multiple case participants (e.g., status including
             dismissals, consolidations, bifurcations, previously-closed cases that have
             been reopened).
DRK-028.01        Provide USER with the ability to view detailed disposition history for     0
                  one to many CASE PARTICIPANTS.
DRK-028.02        Provide USER with the ability to search for other cases associated with    0
                  a CASE PARTICIPANT (party name) from within the CASE.
DRK-029      Maintain multiple current and historical addresses, with beginning and
             ending dates, for each judge, all attorneys including prosecutor, all case
             participants including victims,plaintiffs/defendants and witness.
DRK-029.01        Provide ADMIN USER with the ability to globally define codes for           0
                  address type.
DRK-029.02        Provide ADMIN USER with the ability to globally define central             0
                  repository for Attorney data.
DRK-029.03        Provide USER with the ability to assign address types, start and end       0
                  dates for PARTY address..
DRK-029.04        AUTOMATICALLY maintain complete history of all address                     0
                  information for every type of entity.
DRK-030      Coordinate with Case Initiation and Indexing Function to enter and track all
             charges, issues and requested relief (initial and modified) filed by any case
             participant at case initiation and subsequently and to link charges to proper
             defendant and incident.

DRK-030.01       AUTOMATICALLY maintain complete history of                                  0
                 CHARGES(Criminal)/ISSUES(Civil Family)/RELIEF(Civil).
DRK-030.02       Provide USER with the ability to link charges to defendant and a            0
                 specific incident

     MDEC Procurement K11-0030-29                                                                                  September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 44 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                DOCKETING, RECORD KEEPING

     ID                                 Requirement Text                                          Response Code   Comments
DRK-030.03      Provide USER with the ability to assign issues/requested relief to a          0
                case.
DRK-031      Record bail and bond events in docket.

DRK-031.01        Provide ADMIN USER with the ability to globally define codes to             0
                  associate bail bond types with BAIL BOND (e.g. cash, corporate,
                  property, etc.).
DRK-031.02        Provide ADMIN USER the ability to globally define codes to associate        0
                  bail bond events with BAIL BOND (e.g. posted, released, reinstated,
                  etc.).
DRK-031.03        Provide USER with the ability to assign BAIL BOND codes to BAIL             0
                  BONDS.
DRK-031.04        Provide USER with the ability to assign bail bond event codes to BAIL       0
                  BONDS.
DRK-031.05        Provide USER with the ability to assign on or many parties to BAIL          0
                  BOND (posted by).
DRK-031.06        Provide USER with the ability to assign bail bond amount to BAIL            0
                  BONDS.
DRK-031.07        Provide USER with the ability to assign bail bond event codes to BAIL       0
                  BONDS.
DRK-032      Track and then produce reports on relationship of specific cases and the
             defendant to criminal and civil support units (i.e., bail, pre-trial services,
             and pre-sentence investigation) (e.g., pre-trial services, pre-sentence
             investigation, restitution, bond forfeitures, municipal infractions, civil
             citations, adult probation), CJ agencies (i.e., law enforcement, prosecutor,
             public defender (defense attorney), and adult probation), and non-justice
             agencies such as social services.
DRK-032.01        Provide ADMIN USER with the ability to globally define a central            0
                  repository for AGENCY.
DRK-032.02        Provide ADMIN USER with the ability to globally define a central            0
                  repository for PARTY[PROFESSIONALS] associated with AGENCY.
DRK-032.03        Provide ADMIN USER with the ability to codes to associate                   0
                  PARTY[professionals] with AGENCY.
DRK-032.04        Provide ADMIN USER with the ability to locally define REPORTS for           0
                  agency/professional to case.
DRK-032.05        Provide ADMIN USER with the ability to globally define codes to             0
                  associate agency/professional relationship to case.

     MDEC Procurement K11-0030-29                                                                                   September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                       ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                              Page 45 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                DOCKETING, RECORD KEEPING

     ID                                Requirement Text                                            Response Code   Comments
DRK-032.06       Provide USER with the ability to assign agency/professional to CASE.          0

DRK-032.07        Provide USER with the ability to produce report for                          0
                  agency/professional.
DRK-032.08        Provide USER with the ability to sort on agency/professional, case           0
                  number, relationship to case, date agency/professional added to case,
                  etc.
DRK-033      Perform locally defined edit and data validation checks such as content of
             each individual data field (e.g., proper format for a date) and relationship of
             data field to other data (e.g., attempt to schedule hearing for cases with
             open warrants and other served documents).
DRK-033.01        Provide ADMIN USER with the ability to define rules for data                 0
                  validations on all fields.
DRK-034      Permit user to obtain audit trail of all charges/issues/requested relief (i.e.,
             from arrest through life of case or from filing to judgment in civil cases) for
             a given participant and case.
DRK-034.01        Provide ADMIN USER with the ability to define report for                     0
                  CHARGE/ISSUES/RELIEF involving a PARTYTOCASE.
DRK-034.02        Provide USER with the ability to produce report for charges/relief           0
                  involving a PARTYTOCASE.
DRK-035      Send request for pre-trial services (ADR, mediation) with associated case
             and participant information and internal investigation to appropriate
             provider electronically.
DRK-035.01        INTERFACE CASE to Pre-Trial Service agencies.                                0
DRK-036      Receive results of research on case participant (prior arrests and
             convictions, prior FTAs, aliases, duplicate identifiers, general activity, case
             numbers) to docket and related individual records.
DRK-036.01        Provide ADMIN USER with the ability to define codes for identifiers          0
                  (e.g. other case ids, a/k/a types, etc.).
DRK-036.02        Provide USER with the ability to assign identifiers to PARTY.                0
DRK-036.03        Provide ADMIN USER with the ability to define field(s) for querying on       0
                  person information across all CASES (person centric view).
DRK-036.04        Provide ADMIN USER with the ability to define field(s) that are              0
                  displayed in the search results.
DRK-036.05        Provide USER with the ability to search with ease for any information        0
                  on a person entity.


     MDEC Procurement K11-0030-29                                                                                    September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                       ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                              Page 46 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                DOCKETING, RECORD KEEPING

     ID                                   Requirement Text                                         Response Code   Comments
DRK-037      Receive information regarding non-compliance of pre-trial intervention (e.g.
             mediation, landlord/tenant rent escrow, jurors) or supervision requirements.

DRK-037.01       Provide non-court USERS (e.g. mediator, probation department) with            0
                 the ability to report program outcomes.
DRK-037.02       Provide USER with the ability to import results of court-ordered              0
                 programs (e.g. mediation, probation, etc.) into current CASE record.
DRK-037.03       INTERFACE Pre-Trial Services to COURT.                                        0
DRK-038      Receive conditions of release including but not limited to, committing the
             defendant to the custody of designated person or organization that will
             supervise and ensure appearance of defendant in court, placing defendant
             under supervision of probation officer or appropriate public official,
             subjecting defendant to reasonable restrictions with respect to travel,
             associations, or residency, requiring the defendant to post bond and with
             conditions specified by a judicial officer: a) without collateral security. b)
             with collateral security equal in value to the greater of $25.00 or 10% of full
             bond; or the larger percentage as fixed by judicial officer. c) with collateral
             security of the kind specified in MR 4-217(e)(1)(A) equal in value to the
             greater of $100.00 or the full penalty amount. If bail is set at $2,500.00 or
             less, the defendant may post with a cash deposit of 10% of the full penalty
             amount. d) with collateral security as specified in MR 4-217(e)(1) with full
             penalty amount. e) with obligation of a corporation that is an insurer or
             other surety in full penalty amount. Ensure appearance of defendant and
DRK-038.01       Provide ADMIN USER to define a set of values for a CASE                       0
                 PARTICIPANT's release from incarceration.
DRK-038.02       Provide USER with the ability to assign conditions for release from           0
                 incarceration for a CASE PARTICIPANT.
DRK-038.03       Provide USER with the ability to track a CASE PARTICIPANT's                   0
                 compliance with conditions of release, (e.g. appearance in court,
                 report to probation officer, etc.) (Tickler system).
DRK-038.04       Provide USER with the ability to report a CASE PARTICIPANT's failure          0
                 to comply with conditions of release from incarceration.
DRK-039      Send information on adult referrals for pre-sentence report.
DRK-039.01       Provide ADMIN USER with the ability to locally define REPORTs                 0
                 (forms) for referral agencies.
DRK-039.02       Provide ADMIN USER with the ability to define codes for referral              0
                 agencies.
     MDEC Procurement K11-0030-29                                                                                    September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                       ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                              Page 47 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                                DOCKETING, RECORD KEEPING

     ID                                      Requirement Text                                     Response Code   Comments
DRK-039.03       Provide ADMIN USER with the ability to define codes for referral type.       0
DRK-039.04       Provide USER with the ability to produce document for electronic             0
                 transmission to referral agencies
DRK-040      Receive pre-trial and pre-sentence information electronically or contents of
             report (e.g., date ordered, date returned, results, extension requests,
             referral reports, injunctions).
DRK-040.01       Provide non-court USERS, (e.g. pre-sentencing investigator) with the         0
                 ability to electronically transmit report(s) on CASE PARTICIPANT.
DRK-040.02       Provide USER with the ability to import information from agency report       0
                 into CASE record.
DRK-040.03       Provide USER with the ability to produce necessary reports from within       0
                 system to appropriate judicial officer.
DRK-041      Add information called for in subsequent Docketing and Related Record
             keeping subfunctions to database files; capture, maintain, and provide
             access to subset of database files for docket or register of actions to
             summarize events for each case and participant.
DRK-041.01       Provide ADMIN USER with the ability to define fields to display for          0
                 register of actions by CASE, PARTY.
DRK-042      Allow or disallow different types of filings or events for each unique case
             category (e.g., types of filings for child abuse and neglect cases differ from
             those for delinquency and status cases).
DRK-042.01       Provide ADMIN USER with the ability to define codes to associate             0
                 document types with case type.
DRK-043      Allow newly-entered events to be inserted as appropriate in docket (e.g.,
             before later entries in chronological event list).
DRK-043.01         Provide USER with the ability to assign date to event.                     0
DRK-043.02         Provide USER with the ability to sort display on date field.               0
DRK-043.03         Provide USER the ability to assign a docket entry to a CASE.               0
DRK-044      Allow user to define, modify, and maintain all relationships noted in Case
             Initiation and Indexing and Docketing and Related Record Keeping.
DRK-044.01       Provide ADMIN USER with the ability to define codes to associate             0
                 PARTYTOCASE with events (e.g. filing party, party type, etc.).
DRK-044.02       Provide USER with the ability to assign PARTIES to events.                   0
DRK-045      Restore any relationship noted above if erroneously modified or deleted.
             (see Security Function)


     MDEC Procurement K11-0030-29                                                                                   September 1, 2010
                                                MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                     ATTACHMENT C
                                                  MARYLAND ELECTRONIC COURT PROCUREMENT                            Page 48 of 249
                                                         FUNCTIONAL REQUIREMENTS

                                                              DOCKETING, RECORD KEEPING

     ID                                     Requirement Text                                   Response Code   Comments
DRK-045.01       Provide USER with the ability to assign PARTIES to certain events.        0
DRK-046      Continue user prompts begun in case initiation when situations exist for
             persons in case that user should be aware of (e.g., outstanding pick-up
             order) and identify situation to extent information in system. Prompts
             should be configurable by case type and provided to users who have the
             capability to act on the prompt.
DRK-046.01       Provide ADMIN USER with the ability to define a rule that establishes     0
                 certain conditions for monitoring changes in PARTY information.

DRK-046.02        AUTOMATICALLY prompt USER when predefined conditions occur on            0
                  a PARTY.
DRK-046.03        Provide USER with the ability to view with ease the detail that          0
                  generated the prompt.
DRK-047      Continue case and person information security and data integrity begun in
             case initiation, such as increased security to social data on case
             participants and their families (e.g., medical, family, SSN, relationships,
             defendants, victims, etc.).
DRK-047.01        Provide ADMIN USER with the ability to globally define codes to          0
                  identify sealed, secret or confidential CASE information.
DRK-047.02        Provide USER with the ability to assign codes to CASE information to     0
                  indicate confidentiality.
DRK-048      Output other views of database information such as on specific case
             participants and his or her family and on participants and other persons
             (e.g., public and private agencies charged with child protection, state and
             local government agencies, state and local government attorneys, law
             enforcement, public and private mental health agencies) related to a case.

DRK-048.01        Provide USER with the ability to sort display of PARTY information by    0
                  party type, family identifier, agency/professional, etc.
DRK-049      Maintain and output history of all relationships established for each case
             participant and his or her family with dated audit trail of changes.
DRK-049.01       Provide ADMIN USER with the ability to define REPORT showing              0
                 PARTY TO CASE relationships, date relationship established (eff.
                 Date) and USER dates (create and update).
DRK-049.02       Provide USER with the ability to produce REPORT showing PARTY             0
                 TO CASE relationships, date relationship established (eff. Date), and
                 USER create and USER update information.
     MDEC Procurement K11-0030-29                                                                                September 1, 2010
                                                   MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                  ATTACHMENT C
                                                     MARYLAND ELECTRONIC COURT PROCUREMENT                         Page 49 of 249
                                                            FUNCTIONAL REQUIREMENTS

                                                                  DOCKETING, RECORD KEEPING

     ID                                       Requirement Text                                 Response Code   Comments
DRK-050      Provide audit trail for all activity contained in each case.
DRK-050.01        Maintain history of all case-related activity (events), including User   0
                  login, User create and User update dates.
DRK-050.02        Provide ADMIN USER with the ability to define REPORT showing User        0
                  create and update information for all events, including User login and
                  dates.
DRK-050.03        Provide USER with the ability to produce/view REPORT of case events      0
                  with User create and User update information, (e.g. User login, User
                  dates).
DRK-051      Ability to relate actions based on a docketed event according to locally
             defined business rules.
DRK-051.01        Provide ADMIN USER with the ability to locally define workflow           0
                  process by event, case type according to local business rules.
DRK-051.02        Provide ADMIN USER with the ability to locally define rules for          0
                  workflow based on event, case type, etc. according to local practice.
DRK-052      Allow the user management team to enter and maintain codes for data
             tables (e.g., CJIS codes, charge codes and descriptions), including history
             of codes and charge tables.
DRK-052.01        Provide ADMIN USER with the ability to globally define codes for         0
                  statutes, including CJIS codes, statute codes, statute descriptions,
                  effective date, rescission date, charging language, etc.
DRK-052.02        AUTOMATICALLY maintain history of changes to CJIS codes, statute         0
                  codes, statute descriptions, effective date, rescission date, etc.

DRK-053      For a charge without a CJIS code, send an alert to COCA.
DRK-053.01       Provide USER with the ability to assign statute code to charges where 0
                 no CJJIS code has been defined.
DRK-053.02       AUTOMATICALLY alert COCA when no CJIS code exists for a charge. 0

DRK-054      Alert commissioner when a charge must be identified as a misdemeanor
             crime (containing a fine and or incarceration under penalty section) and not
             simply a municipal infraction (civil categorization).
DRK-054.01       Provide ADMIN USER with the ability to define codes to associate         0
                 charge(s) with class of offense.
DRK-054.02       Provide USER with the ability to assign an indicate to charge when       0
                 charge involves misdemeanor crime.

     MDEC Procurement K11-0030-29                                                                                September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 50 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                               DOCKETING, RECORD KEEPING

     ID                             Requirement Text                                             Response Code   Comments
DRK-054.03       AUTOMATICALLY alert commissioner when charge is misdemeanor.                0
DRK-055      Ability to determine the charge severity hierarchy and attach lesser
             included charges either manually or with automated assistance; based on
             business rules (certain charging documents cannot be changed).
DRK-055.01        Provide ADMIN USER with the ability to define rules for assigning a        0
                  value (such as weighting) to charges.
DRK-055.02        Provide ADMIN USER with the ability to define rules for assigning          0
                  lesser included offenses to charge with highest weighting.
DRK-056      Ability to change erroneously assigned case numbers with a safeguard to
             prevent inadvertent changes to or deletion of cases.
DRK-056.01        Provide ADMIN USER with the ability to define rules regarding              0
                  deletion/retention of previously assigned case ids.
DRK-056.02        Provide ADMIN USER with the ability to DELETE case ids erroneously         0
                  assigned.
DRK-057      Allow edits to case information for errors made during the case initiation
             and summons processes.
DRK-057.01        Provide ADMIN USER with the ability to define rules regarding what         0
                  CASE information can be edited and/or deleted.
DRK-057.02        Provide USER with the ability to assign (edit) previously entered          0
                  information or to mark previously entred information as having been
                  entered in error.
DRK-058      Provide the ability to join cases (manage two cases as one, although cases
             themselves remain separate) and consolidate cases (merge multiple cases
             into one).
DRK-058.01        Provide ADMIN USER with the ability to globally define types of case       0
                  consolidation.
DRK-058.02        Provide ADMIN USER with the ability to locally define workflow             0
                  process based on type of case consolidation
DRK-058.03        Provide USER with the ability to assign consolidation type to a group of   0
                  CASES.
DRK-059      Allow designation of lead case, and allow for separation and redesignation
             at a later time (lead case settles) docket entries need to be moved to the
             new lead case.
DRK-059.01        Provide USER with the ability to assign an indicator to designate lead     0
                  CASE in a group of consolidated CASES.
DRK-059.02        AUTOMATICALLY link lead case to SUB-CASES.                                 0
DRK-060      Track time periods and/or allowances for notices and motions.

     MDEC Procurement K11-0030-29                                                                                  September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 51 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                                DOCKETING, RECORD KEEPING

     ID                                 Requirement Text                                         Response Code   Comments
DRK-060.01       Provide ADMIN USER with the ability to define codes for TICKLES.            0
DRK-060.02       Provide ADMIN USER with the ability to define workflow process upon         0
                 expiration of TICKLE.
DRK-060.03       Provide ADMIN USER with the ability to define REPORTS showing               0
                 information regarding whether or not certain deadlines have been met.
DRK-060.04       Provide USER with the ability to assign tickle codes to designated          0
                 events.
DRK-060.05       Provide USER with the ability to override (delay) tickle expiration date.   0

DRK-060.06       Provide USER with the ability to search for TICKLES by User-defined         0
                 criteria such as case type, case id, tickle code, tickle expiration, etc.
DRK-060.07       Provide ADMIN USER with the ability to define field(s) for querying on      0
                 TICKLE information.
DRK-060.08       Provide ADMIN USER with the ability to define field(s) that are             0
                 displayed in the search results.
DRK-060.09       Provide USER with the ability to search with ease for TICKLE                0
                 information.
DRK-061      Alert users of upcoming and passed deadlines.
DRK-061.01       AUTOMATICALLY alert USER when certain TICKLES have reached                0
                 date of expiration.
DRK-062      Allow each court location to designate site specific deadlines (by case type,
             case status ).
DRK-062.01       Provide ADMIN USER with the ability to locally define workflow            0
                 process upon expiration of TICKLES.
DRK-063      Allow for multiple issues or processes in a case to be open (e.g., a VOP
             while the case is on appeal), without requiring the one of them to be closed.
DRK-063.01       Provide ADMIN USER with the ability to define rules regarding which      0
                 issues/processes can remain open simultaneously.
DRK-064      Provide the ability to create a separate mechanism for tracking cases or
             specific case information (suspension events) for case flow study
             purposes, such as with the uncertainty when lab results are involved (DNA,
             in particular) having an impact on the case age calculations of these cases.

DRK-064.01       Provide ADMIN USER with the ability to design a rule to define case         0
                 start/stop/suspend events.
DRK-064.02       Provide USER with the ability to assign suspension events to CASE.          0

     MDEC Procurement K11-0030-29                                                                                  September 1, 2010
                                                MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                  MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 52 of 249
                                                         FUNCTIONAL REQUIREMENTS

                                                              DOCKETING, RECORD KEEPING

     ID                                     Requirement Text                                    Response Code   Comments
DRK-065      Allow the commissioner to enter citations.
DRK-065.01        Provide USER [commissioners] with the ability to enter CASE               0
                  information including charging documents and criminal informations
DRK-065.02        Provide USER [commissioners] with the ability to produce orders           0
                  [protective/peace, commitment]
DRK-065.03        Provide USER [commissioners] with the ability to conduct hearings         0
DRK-066      Allow electronic citations to be uploaded to commissioner, in order to avoid
             duplicate entry by commissioner, where e-citations are available.
DRK-066.01        INTERFACE from E-citations                                                0
DRK-067      Provide visibility of who is committed (incarceration, mental health, etc..)
             where and by which court; and provide the ability to capture release
             information if available.
DRK-067.01        AUTOMATICALLY provide USER with commitment status of PARTY.               0
DRK-067.02        Provide ADMIN USER with the ability to define fields to display for       0
                  commitment status of PARTY.
DRK-067.03        Provide USER with the ability to define commitment location,              0
                  committing court to PARTY.
DRK-067.04        INTERFACE from detention centers to COURT.                                0
DRK-068      Electronic transmittals must be supported for requests for service of
             process, warrants, summonses, and other documents that require manual
             service; to police, and notification of service outcome to the Court.

DRK-068.01       Provide ADMIN USER with the ability to define workflow process             0
                 regarding actions to be taken upon receipt of requests for service.
DRK-068.02       Provide USER with the ability to request requests for service.             0
DRK-068.03       Provide USER with the ability to assign service dates.                     0
DRK-068.04       Provide USER with the ability to produce documents for electronic          0
                 notification of service outcomes.

DRK-068.05       Provide USER with the ability to assign service outcome to                 0
                 Documents[Warrants, Summonses, Other Service Documents] when
                 electronic service is not available.
DRK-068.06       AUTOMATICALLY assign service outcome to Documents[ Warrants,               0
                 Summonses, Other Service Documents] after electronic notification of
                 service.


     MDEC Procurement K11-0030-29                                                                                 September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 53 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                               DOCKETING, RECORD KEEPING

     ID                                Requirement Text                                          Response Code   Comments
DRK-068.07       Provide USER with the ability to print Documents [Warrants,                 0
                 Summonses, Other Service Documents] when electronic transmittal is
                 not available.
DRK-068.08       AUTOMATICALLY transmit Documents[Warrant, Summonses, Other                  0
                 Server Documents] Electronically to the proper service agency.

DRK-068.09       Provide USER with the ability to override the default Service Agency to 0
                 Warrant.
DRK-069      Allow attorneys to withdraw petitions electronically.
DRK-069.01       Provide EFILE USER with the ability to request that a document be           0
                 withdrawn electronically.
DRK-070      Track time standards, time periods in connection with event processing,
             scheduling, deadlines, ticklers, etc.
DRK-070.01       Provide ADMIN USER with the ability to define codes for TICKLES.            0
DRK-070.02       Provide ADMIN USER with the ability to define workflow process upon         0
                 expiration of TICKLE.
DRK-070.03       Provide ADMIN USER with the ability to define REPORTS showing               0
                 information regarding whether or not certain deadlines have been met.
DRK-070.04       Provide USER with the ability to assign tickle codes to designated          0
                 events.
DRK-070.05       Provide USER with the ability to override (delay) tickle expiration date.   0

DRK-070.06      Provide USER with the ability to search for TICKLES by User-defined          0
                criteria such as case type, caseid, tickle code, tickle expiration, etc.
DRK-071      Support motions in the mortgage foreclosure process.
DRK-071.01       Provide ADMIN USER with the ability to define codes for documents           0
                 involved in mortgage foreclosure process.
DRK-071.02       Provide USER with the ability to assign codes to documents involved         0
                 in mortgage foreclosure process.
DRK-072      Allow for mandatory mediation in such cases as medical malpractice.

DRK-072.01       Provide ADMIN USER with the ability to define workflow process.             0
DRK-072.02       Provide ADMIN USER with the ability to define rules regarding case          0
                 types/categories subject to mediation.
DRK-072.03       Provide USER with the ability to assign cases to mediation process.         0


     MDEC Procurement K11-0030-29                                                                                  September 1, 2010
                                                   MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                        ATTACHMENT C
                                                     MARYLAND ELECTRONIC COURT PROCUREMENT                               Page 54 of 249
                                                            FUNCTIONAL REQUIREMENTS

                                                                  DOCKETING, RECORD KEEPING

     ID                                  Requirement Text                                            Response Code   Comments
DRK-073      Enable automatic ticklers set for specific filings (e.g., VOP, etc.).
DRK-073.01       Provide ADMIN USER with the ability to define codes to tickles.                 0
DRK-073.02       Provide ADMIN USER with the ability to define rules for tickle                  0
                 expiration dates for specific filings.
DRK-073.03       Provide ADMIN USER with the ability to associate tickles to events.             0
DRK-073.04       Provide USER with the ability to assign tickle codes to designated              0
                 events.
DRK-074      Provide functionality and flexibility in handling criminal charges/civil issues
             and requested relief: entering, correcting (actual errors), amending
             (charges are changed as a part of a plea or other case event), tracking
             changes, tracking dispositions, etc.
DRK-074.01       Provide USER with the ability to assign charges to CASE.                        0
DRK-074.02       Provide USER with the ability to make corrections to                            0
                 charges/issues/requested relief information.
DRK-074.03       Provide USER with the ability to amend charges/issues/requested                 0
                 relief.
DRK-074.04       Provide USER with the ability to assign disposition to                          0
                 charges/issues/requested relief.
DRK-074.05       Provide USER with the ability to produce report of dispositions for one         0
                 to many charges/issues/requested relief per CASE.
DRK-074.06       Provide USER with the ability to view one to many charges for CASE,             0
                 including all amendments, dispositions, etc.
DRK-075      Capture dates correctly by deciphering the difference between effective
             date and entered date and allow for docketing of retroactive filings.
DRK-075.01       AUTOMATICALLY capture system date & time upon entry of event                    0
                 record.
DRK-075.02       Provide USER with the ability to assign filing date independent of date         0
                 of data entry.
DRK-076      Contain all codes for all events or activities and provide for the flexibility to
             add codes.
DRK-076.01       Provide ADMIN USER with the ability to define codes for events.                 0
DRK-077      Support complex sentencing.
DRK-077.01       Provide USER with the ability to assign SENTENCES to CHARGES                    0
                 that consists of many elements (e.g. mixture of concurrent and
                 consecutive sentences, sentence suspensions, etc.)


     MDEC Procurement K11-0030-29                                                                                      September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                     ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                            Page 55 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                               DOCKETING, RECORD KEEPING

     ID                                     Requirement Text                                    Response Code   Comments
DRK-078      Produce cross-tab data for the primary information used in the monthly
             docket review meetings.
DRK-078.01        Provide USER with the ability to run cross tab queries.                   0
DRK-079      Track victim notifications at any point in the criminal or delinquency
             process with alerts to send notifications when new commitments or
             releases are issued.
DRK-079.01        Provide ADMIN USER with the ability to define forms to be used for        0
                  victim notifications.
DRK-079.02        Provide USER with the ability to produce forms.                           0
DRK-079.03        AUTOMATICALLY maintain history of crime victim notifications.             0
DRK-079.04        Alert USER when defendant is committed or released from                   0
                  incarceration.
DRK-080      Provide the ability to track, action and manage resources for mental health,
             family law, family services (home studies, etc.) effectively, including
             support for case notes.
DRK-080.01        Provide USER with the ability to track resources for mental health,       0
                  family lay, family services and other referrals with support for case
                  notes.
DRK-081      Support the ability to secure commissioner‘s and judge's notes to ensure
             that notes are kept confidential.
DRK-081.01        Provide ADMIN USER with the ability to define confidential status of      0
                  events by event type.
DRK-081.02        Provide USER with the ability to assign confidential status to event.     0
DRK-081.03        Provide USER with the ability to view confidential information based on   0
                  security settings.
DRK-081.04        Provide USER with the ability to assign confidential comments to case     0

DRK-082      Allow users to send and track referrals and information about which
             services were ordered and consumed, and the results (SMART
             overlap/exchange).
DRK-082.01       Provide USER with the ability to assign referrals to one to many           0
                 CASES.
DRK-082.02       Provide USER with the ability to electronically notify agency(ies) of      0
                 court-ordered referrals for one or many cases.
DRK-082.03       Provide USER with a means to track referrals and associated                0
                 deadlines.


     MDEC Procurement K11-0030-29                                                                                 September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                    ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                           Page 56 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                DOCKETING, RECORD KEEPING

     ID                                    Requirement Text                                     Response Code   Comments
DRK-083      Support the juvenile summonses needed that are different than those for
             criminal cases.
DRK-083.01        Provide ADMIN USER with the ability to define REPORT (form) for           0
                  custom juvenile summons.
DRK-083.02        Provide USER with the ability to produce custom forms.                    0
DRK-083.03        Provide USER with the ability to select PARTIES summoned.                 0
DRK-084      Ensure that there are enough fields to capture bond amounts and bond
             numbers, rent escrow amounts, and other unique data needs.
DRK-084.01        SEE ACCOUNTING; BAIL BONDS                                                0
DRK-085      Ensure that when the District Court sets appeal bonds and the Circuit
             Court accept the bond, there is a way to relate that bond to the
             case/decision on appeal (Anytime a case moves from district court to
             circuit court, the bond must transfer with case and jail must be notified of
DRK-085.01        commitment).
             new AUTOMATICALLY assign circuit court case number to district court        0
                  bail bond upon transfer of case to circuit court.
DRK-085.02        SEE ACCOUNTING; BAIL BONDS                                             0
DRK-086      Provide automatic alerts to users when protection/peace orders expire and
             if companion orders exist in other jurisdictions, including interim Orders.
DRK-086.01        Provide USER with the ability assign expiration date to                   0
                  DOCUMENTS[protective/peace orders].
DRK-086.02        Provide USER with the ability to globally search for DOCUMENTS            0
                  [protective/peace order].
DRK-086.03        Provide ADMIN USER with the ability to define rules for alerting user     0
                  regarding expired protective/peace orders.
DRK-087      Provide a prompt on Protective and Peace orders for commissioners to
             hold the defendant without bail (HWOB) on cases involving abuse or
             threats of abuse (Excluding any charges without probable cause and all
             Interim Orders).
DRK-087.01        Provide ADMIN USER with the ability to define fields to be used on        0
                  warrant forms to alert service agency of any special conditions
                  affecting Commissioner's decision regarding bail, e.g. Peach Orders,
                  Orders for Protection, etc.
DRK-087.02        Provide USER with the ability to produce warrants with selected fields.   0




     MDEC Procurement K11-0030-29                                                                                 September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                     ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                            Page 57 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                               DOCKETING, RECORD KEEPING

     ID                                    Requirement Text                                     Response Code   Comments
DRK-088      The case management system should handle issues where additional
             task(s) must be performed prior to court event, such as when drug testing
             is outstanding at the time that a case is automatically set for hearing.
             Timeframes need to be allotted and ticklers/notifications set for each task.
DRK-088.01        Provide ADMIN USER with the ability to define rules regarding setting 0
                  of scheduled events, notifications to USER, etc. when conditions
                  precedent to the setting of a scheduled event exist.
DRK-089      Enable data to be applied to case data in batch form (i.e., apply same data
             to multiple cases) or batch data input capability for pre-designated
             outcomes (e.g., pay fine, attend driver safety training, etc).
DRK-089.01        Provide USER with the ability to assign a single action to multiple    0
                  CASES.
DRK-090      Provide an efficient, automatic monitoring of the stet docket. Once a case
             is removed from stet, update case with current information (i.e., inactive
             attorney is not notified of subsequent event).
DRK-090.01        AUTOMATICALLY strike appearance of attorney 35 days from entry of 0
                  STET on docket.
DRK-091      Provide effective handling of multiple VOPs and post convictions.
DRK-091.01       Provide USER with the ability to assign a one or many violation of         0
                 probation and/or post convicition statuses to a case
DRK-091.02       Provide support for multiple VOP and post convictions.                     0
DRK-092      Provide automatic setting of milestones and events or removal of cases
             from queues if no effective delivery(service of required participants) was
             noted by certain dates.
DRK-092.01       Provide ADMIN USER with the ability to locally define tracks for           0
                 differentiated case management, including deadlines for discovery,
                 pleading, and automatic scheduling of hearing/trial.
DRK-092.02       Provide ADMIN USER with the ability to associate tracks for selected       0
                 case types.
DRK-092.03       Provide USER with the ability to assign tracks to one to many CASES.       0

DRK-092.04       Provide USER with the ability to override track milestones for one to      0
                 many CASES.
DRK-092.05       Provide USER with the ability to update track milestones.                  0
DRK-092.06       Provide USER with the ability to modify track assignment for one to        0
                 many cases.

     MDEC Procurement K11-0030-29                                                                                 September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                       ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                              Page 58 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                DOCKETING, RECORD KEEPING

     ID                                    Requirement Text                                        Response Code   Comments
DRK-092.07        Provide a mechanism for reporting compliance with track milestones          0
                  for one to many CASES (statistical reporting).
DRK-092.08        Provide USER with the ability to remove one to many CASES from              0
                  previously assigned track.
DRK-093      Provide a mechanism for searching for cases with a specific condition(s)
             that require clerk action (e.g. eligibility for dismissal according to Md Rules)

DRK-093.01       Provide ADMIN USER with the ability to define report or query criteria.       0

DRK-093.02         Provide USER with the ability to produce report.                            0
DRK-094      Allow for editing of the disposition once it is made with appropriate audit
             trail of changes.
DRK-094.01         Provide ADMIN USER with the ability to define rules for disposition         0
                   updates.
DRK-094.02         Provide USER with the ability to assign updated values to disposition       0
                   within locally defined rules as defined by ADMIN USER.
DRK-094.03         AUTOMATICALLY maintain history of disposition/case status.                  0
DRK-095      Provide a consistent process for disposing all charges/requested relief
             (civil citations, municipal infractions, remand, NP, etc …) when the
             defendant fails to appear in court
DRK-095.01         Provide ADMIN USER with the ability to define appropriate dispositions      0
                   for case type & event.
DRK-095.02         Provide ADMIN USER with the ability to define REPORT showing                0
                   events such as defendant FTA in Circuit Court where action needs to
                   be taken by District Court.
DRK-095.03         Provide USER with the ability to assign appropriate dispositions for        0
                   case type and event.
DRK-095.04         Provide USER with the ability to view cases requiring USER                  0
                   intervention, e.g. further hearing, issuance of warrant, etc. in District
                   Court when defendant FTA in Circuit Court.
DRK-096      System issues a warrant if defendant FTA in circuit court.
DRK-096.01      AUTOMATICALLY generate warrant form in District Court upon entry               0
                of FTA in Circuit Court.
DRK-097      Enable users to send new judgment information electronically.
DRK-097.01       Provide USER with the ability to assign JUDGMENT information.                 0
DRK-097.02       AUTOMATICALLY export new Judgment information.                                0

     MDEC Procurement K11-0030-29                                                                                    September 1, 2010
                                                       MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                 ATTACHMENT C
                                                         MARYLAND ELECTRONIC COURT PROCUREMENT                        Page 59 of 249
                                                                FUNCTIONAL REQUIREMENTS

                                                                          DOCKETING, RECORD KEEPING

     ID                                     Requirement Text                                      Response Code   Comments
DRK-098      Provide the ability to track shelter/non-shelter status of CINA cases.
DRK-098.01       Provide USER with the ability to assign indicator to CASE to show            0
                 whether the case is a shelter or non shelter CINA case.
DRK-098.02       Provide ADMIN USER with the define rules to AUTOMATICALLY                    0
                 assign indicator to CASE for indicating shelter or non shelter CINA
                 cases.
DRK-099      Provide the ability to track multiple plans if present in a case; a child can
             have concurrent plans.
DRK-099.01       Provide USER with the ability to assign one or many permanency plan          0
                 details to CASE.
DRK-100      Provide the ability to collect information on reasonable efforts made to
             prevent removing a child from a home or emergency situation existed.
             Provide the ability to track federal requirements such as ASFA, Title IV E.
DRK-100.01       Provide USER with the ability to assign indicator to CASE to show that       0
                 reasonable efforts were made prior to removing the child from the
                 home.
DRK-101      Provide the ability to collect information on findings (Cts. and Jud. 3-815(d)
             and (e)).- shelter care
DRK-101.01       Provide USER with the ability to assign CINA FINDINGS to                     0
                 SCHEDULED EVENT.
DRK-101.02       Provide ADMIN USER with the ability to define codes for CINA                 0
                 FINDINGS.
DRK-101.03       Provide ADMIN USER with the ability to define codes to associate             0
                 CINA FINDINGS with SCHEDULED EVENT.
DRK-102      Provide the ability to track when DSS develops permanency plans.
DRK-102.01       INTERFACE from DSS to Court                                                  0
DRK-103      Provide the ability to track when the system should be able to track the
             status of those (multiple) plans and whether they need to be modified, etc.
DRK-103.01        Provide ADMIN USER with the ability to define rules for alerting user       0
                  concerning milestones on permanency plans.
DRK-104      Provide the ability to track different types of petitions.
DRK-103.01        Provide ADMIN USER with the ability to define different types of            0
                  petitions
DRK-103.02        Provide USER with the ability to assign different types of petitions to     0
                  the case and track them independently

     MDEC Procurement K11-0030-29                                                                                   September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                        ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                               Page 60 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                                DOCKETING, RECORD KEEPING

     ID                                     Requirement Text                                       Response Code   Comments
DRK-105      Provide the ability to establish and track local case flow time standards,
             Maryland case flow time standards, and federal case flow time standards--
             clock time shall be measured against case flow and federal time standards
             separately.
DRK-105.01        Provide ADMIN USER with the ability to define rules for case                 0
                  start/stop/suspend events.
DRK-105.02        Provide USER with the ability to assign suspension events to case.           0
DRK-106      Provide the ability to prevent users from issuing a writ on judgment for 10
             days (Rule 2-632b)., but also allow for judicial officer override.
DRK-106.01        Allow for administrative/supervisor override of automatic 10-day stay of     0
                  enforcement.
DRK-106.02        Provide ADMIN USER with the ability to define rules for preventing the       0
                  issuing of a writ on JUDGMENT.
DRK-107      Provide the ability to display all cases (including cases outside the county)
             for a participant.
DRK-107.01        Provide USER with the ability to perform global search for all case          0
                  participants by name.
DRK-108      Provide a referral module to track cases referred to all referral programs.
DRK-108.01        Provide ADMIN USER with the ability to define list of agencies.              0
DRK-108.02        Provide ADMIN USER with the ability to define REPORT listing                 0
                  outstanding agency referrals for one to many cases, e.g. all CASES
                  referred to DSS for investigation, etc. where a report has not been filed.
DRK-108.03        Provide USER with the ability to assign one to many CASES to one to          0
                  many agency(ies).
DRK-108.04        Provide USER with a method to track agency referrals, e.g. deadlines         0
                  for agency reports, etc.
DRK-109      Provide statewide warrant visibility for those with appropriate access
             privileges.
DRK-109.01        Provide all USERS with the ability to see warrants issued on any party       0
                  statewide.
DRK-110      Provide the ability for case participants to be tracked as either represented
             by counsel or pro se.
DRK-110.01        AUTOMATICALLY designate PARTY as pro se upon any filing by the               0
                  PARTY when no attorney appearance is entered.
DRK-110.02        Provide USER with the ability to assign pro se status to PARTY.              0


     MDEC Procurement K11-0030-29                                                                                    September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                    ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                           Page 61 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                DOCKETING, RECORD KEEPING

     ID                                    Requirement Text                                     Response Code   Comments
DRK-111      Provide the ability to track writs and warrants for DV contempt similar to
             process performed in criminal.
DRK-111.01       AUTOMATICALLY maintain history of warrants issued in CASE as well 0
                 as warrant disposition information.
DRK-112      Track relationship between the docket entry and associated template form.

DRK-112.01       AUTOMATICALLY associate DOCUMENT to DOCUMENT template                      0
                 that was used to create it.
DRK-113      Provide for a docket entry sequence number to be AUTOMATICALLY
             assigned and displayed or user entered and displayed.
DRK-113.01       AUTOMATICALLY assign sequence number to docket entries.                    0
DRK-113.02       Provide USER with the ability to assign sequence number for docket         0
                 entries when filing is made previous to existing docket entries, e.g. if
                 entries # 4 and 5 exist, allow USER to enter #4.1, etc.




     MDEC Procurement K11-0030-29                                                                                 September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                    ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                           Page 62 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                            SCHEDULING

     ID                                    Requirement Text                                     Response Code   Comments
SCH-001      Resolve scheduling conflicts (including ability to define what constitutes a
             conflict).
SCH-001.01       Provide ADMIN USER with the ability to define rules to determine           0
                 conflicts in calendars.
SCH-001.02       Provide ADMIN USER with the ability to define rules to resolve             0
                 conflicts in calendars.
SCH-001.03       Provide USER with the ability to select case participants for SE,          0
                 invoking rules to resolve conflicts in case participant calendars.
SCH-001.04       Provide USER with the ability to override rules regarding conflicts.       0
SCH-002      Relate each SCHEDULED EVENT to actuating filing or prior event.
SCH-002.01       Provide USER with the ability to assign SCHEDULED EVENTS to                0
                 DOCUMENTS.
SCH-002.02       Provide USER with the ability to assign SCHEDULED EVENTS to                0
                 other prior SCHEDULED EVENTS.
SCH-003      Assist USER in manual schedule overrides or changes for specific cases
             and event(s) (e.g., by allowing USER to enter event type, start date, and
             duration; by displaying allowable completion dates, open time slots, and
             time periods allotted to various case processing stages; and by adjusting
             open time slots to reflect manual schedule entries, changing events from
             judge to master or vice versa).
SCH-003.01       Provide USER with the ability to assign a SCHEDULED EVENT to a             0
                 CASE.

SCH-003.02       Provide USER with the ability to search open slot(s) with the following 0
                 criteria: event Type, start Date, and duration.
SCH-003.03       Provide USER with the ability to view openings based on the following: 0
                 allowable completion dates, open time slots, and time periods allotted
                 to case processing stages.


SCH-003.04       Provide USER with the ability to assign a master or judge to the           0
                 SCHEDULED EVENT.
SCH-003.05       Automatically adjust open time slots after a manual scheduling entry.      0




     MDEC Procurement K11-0030-29                                                                                 September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                    ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                           Page 63 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                                          SCHEDULING

     ID                                    Requirement Text                                    Response Code   Comments
SCH-004      Provide tickler capability based on schedules and statutory requirements:
             identify events coming due or overdue, periods about to expire or expired
             (e.g., guardianship accounting due, answer or response due), events of
             which USER should be aware based on locally defined needs (e.g.,
             approaching maximum number of continuances); prompt or notify USERS;
             and initiate proper functions (e.g., generate statutorily required notice
             regarding termination of support on approaching birthday when child
             becomes an adult, unless special conditions exist that nullify termination,
             such as physically handicapped person).

SCH-004.01       Provide USER with prompt when events are coming due or over due.          0

SCH-004.02       Provide USER with prompt when periods are about to expire or have         0
                 expired.
SCH-004.03       Provide ADMIN USER with the ability to define rules for managing          0
                 ticklers on event due dates.
SCH-004.04       Provide ADMIN USER with the ability to define rules for managing          0
                 ticklers on designated periods.
SCH-004.05       Provide USER with the ability to execute other functions when             0
                 prompted.
SCH-004.06       Provide ADMIN USER with the ability to define workflow based on           0
                 status of periods and event types.
SCH-004.07       Provide ADMIN USER with the ability to define workflow based on           0
                 status of due dates and event types.
SCH-005      Tickler listing should be viewable electronically in the form of a list.
SCH-005.01       Provide ADMIN USER with the ability to define fields for querying         0
                 Events [Ticklers].
SCH-005.02       Provide ADMIN USER with the ability to define fields that are displayed   0
                 in Event [Ticklers] search results.
SCH-005.03       Provide ADMIN USER with the ability to define a rule to perform           0
                 actions on selected Event [ticklers] meeting a certain criteria.
SCH-005.04       Provide USER with the ability to select one or many Event [Ticklers] to   0
                 invoke a rule.
SCH-006      Generate alert when displaying cases or their contents that are not public
             record (e.g., confidential cases). (see also Security Function)
SCH-006.01       Provide ADMIN USER with the ability to define security levels for         0
                 CASES.

     MDEC Procurement K11-0030-29                                                                                September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 64 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                                           SCHEDULING

     ID                                   Requirement Text                                       Response Code   Comments
SCH-006.02        Provide USER with the ability to assign a security level to a CASE.        0
SCH-006.03        Provide ADMIN USER with the ability to define a rule to permit or          0
                  restrict display of CASES depending on security level.
SCH-006.04        Provide USER with alert when a selected CASE has security                  0
                  restrictions.
SCH-007      Schedule events and groups of events (e.g., after case filed, set deadlines
             for service of summons, return of service, filing of answer or response).

SCH-007.01         Provide ADMIN USER with the ability to define rules to prompt for or      0
                   create SCHEDULED EVENTS based on actions in cases.
SCH-007.02         Provide USER with the ability to assign SCHEDULED EVENTS to one           0
                   or more cases based on certain actions in cases.
SCH-008      Initiate schedule of future events based on USER input or occurrence of
             prior events (e.g., after small claims case filed, schedule hearing and
             deadline for sending notices to parties and participants).
SCH-008.01         Provide ADMIN USER with the ability to define rules to prompt for or      0
                   create SCHEDULED EVENTS based on actions in cases.
SCH-008.02         Provide USER with the ability to assign SCHEDULED EVENTS to one           0
                   or more cases based on certain actions in cases.
SCH-009      Allow multiple cases or related incidents and events to have same
             scheduled date and time (e.g., multiple complaints regarding same
             problem to be heard together).
SCH-009.01         Provide USER with the ability to relate CASES to be set on same court     0
                   docket.
SCH-009.02         Provide USER with the ability to schedule related CASES on same           0
                   court docket.
SCH-010      Schedule maximum number of cases for specific time interval by event
             (e.g., hearing) type with the ability for authorized USERS to override.
SCH-010.01         Provide ADMIN USER with the ability to define rules for SCHEDULED         0
                   EVENT load and balance formulas.
SCH-010.02         Provide USER with the ability to override SCHEDULED EVENT load            0
                   and balance formulas.
SCH-011      Apply specific change (e.g., reschedule all cases to be heard by judge who
             is unavailable due to illness) to multiple schedules for group of cases as if
             group was a single case.
SCH-011.01       Provide USER with the ability to select multiple CASES to reschedule        0
                 in batch.
     MDEC Procurement K11-0030-29                                                                                  September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 65 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                            SCHEDULING

     ID                                    Requirement Text                                       Response Code   Comments
SCH-012      Identify and display scheduling conflicts.
SCH-012.01        Automatically identify scheduling conflicts.                                0
SCH-012.02        Provide USER with the ability to view scheduling conflicts.                 0
SCH-013      When multiple schedules change, modify records of all related parties,
             participants, calendars, docket entries, and other data and functions
             including displaying scheduling conflicts, suggesting resolutions, allowing
             USER overrides, and rescheduling only with USER approval and while
             maintaining log of changes.
SCH-013.01        Automatically after schedule changes modify related Party, Calendar,        0
                  Docket and Other records.
SCH-013.02        Provide USER with the ability to view scheduling conflicts.                 0
SCH-013.03        Automatically suggest conflict resolutions.                                 0
SCH-013.04        Provide ADMIN USER with the ability to define rules for resolving           0
                  scheduling conflicts.
SCH-013.05        Provide USER with the ability to override the default rescheduling.         0
SCH-014      Maintain waiting list of cases to be scheduled for specific date, date range,
             judge, courtroom, and other entities.
SCH-014.01        Provide USER with the ability assign a case to a waiting list based on a    0
                  specific date, date range, judge, courtroom or other criteria.
SCH-014.02        Provide ADMIN USER with the ability to define a query for the waiting       0
                  list based on a specified date, date range, judge, courtroom or other
                  criteria.
SCH-014.03        Provide USER with the ability to search the waiting list.                   0
SCH-015      When creating schedules, consider (1) availability of judges, attorneys,
             parties, participants, and court facilities; (2) weekends, holidays, and other
             days generally unavailable for court activities (e.g., training, retreats,
             judicial conferences) and days when specific individuals are unavailable;(3)
             scheduling conflicts to extent information is in system (e.g., all law officer
             and witness schedules will not be in system), (4) pre-defined DCM plan
             that already exists on the case.; (5) consider judge‘s existing ―family"
             designated open case load, but allow manual scheduling at USER
             discretion in spite of conflicts (e.g., conflicts due to judicial absences,
             attorney vacations, law officer schedules).
SCH-015.01        Automatically consider Judge availability when scheduling.                  0
SCH-015.02        Automatically consider attorney availability when scheduling.               0
SCH-015.03        Automatically consider party and participant availability when              0
                  scheduling.
     MDEC Procurement K11-0030-29                                                                                   September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 66 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                                           SCHEDULING

     ID                                  Requirement Text                                        Response Code   Comments
SCH-015.04       Automatically consider court facility availability when scheduling.         0
SCH-015.05       Automatically consider weekends, holidays and other unavailable days        0
                 when scheduling.
SCH-015.06       Automatically consider law officer availability when scheduling.            0
SCH-015.07       Automatically consider all conflicts when scheduling.                       0
SCH-015.08       Automatically consider pre-defined DCM plan when scheduling.                0
SCH-015.09       Provide USER with the ability to override conflicts and schedule Case.      0
SCH-016      Maintain availability information on judges, attorneys, parties, participants
             (e.g., interpreters, out-of-state witnesses), court facilities, and other
             scheduling factors.
SCH-016.01        Provide ADMIN USER with the ability to define central repository for       0
                  judge availability.
SCH-016.02        Provide ADMIN USER with the ability to define central repository for       0
                  attorney availability.
SCH-016.03        Provide ADMIN USER with the ability to define central repository for       0
                  party and participant availability.
SCH-016.04        Provide ADMIN USER with the ability to define central repository for       0
                  court facility availability.
SCH-016.05        Provide ADMIN USER with the ability to define central repository for       0
                  law officer availability.
SCH-017      Relate individual judges and groups of judges to courtrooms, locations,
             departments, department staff (e.g., reporter, bailiff; judge also may be
             considered staff), and case management tracks over permissible
             assignment time frames (e.g., in court with rotating judge assignments, a
             specific judge hears small claims cases in a particular courtroom during a
             given month, allowing ―overlap‖ of resources across judges, courtrooms,
             locations, and departments), and allow USER override.
SCH-017.01        Provide ADMIN USER with the ability to relate judge(s) to courtrooms       0
                  or locations.
SCH-017.02        Provide ADMIN USER with the ability to relate judge(s) to departments      0
                  or department staff.
SCH-017.03        Provide ADMIN USER with the ability to relate judge(s) to case             0
                  management tracks over permissible assignment time frames.
SCH-017.04        Provide USER with the ability to override the default judge assignment.    0




     MDEC Procurement K11-0030-29                                                                                  September 1, 2010
                                                   MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                     ATTACHMENT C
                                                     MARYLAND ELECTRONIC COURT PROCUREMENT                            Page 67 of 249
                                                            FUNCTIONAL REQUIREMENTS

                                                                             SCHEDULING

     ID                                    Requirement Text                                       Response Code   Comments
SCH-018      Assign specific case categories (e.g., tort, contracts, real property rights,
             small claims within civil case type) or specific event types to specific
             departments according to user-defined case/department relationships
             (e.g., business cases assigned to business courts).

SCH-018.01        Provide ADMIN USER with the ability to relate case categories to            0
                  specific departments.
SCH-018.02        Provide ADMIN USER with the ability to relate event types to specific       0
                  departments.
SCH-019      Assign and reassign individual and groups of judges using one or more of
             the following methods: randomly, according to predefined rules (e.g., by
             case category, by case status, by hearing type, by judge rotation policies,
             by judge caseload balancing policies), according to existence of specific
             conditions (e.g., conflict of interest), according to dates and times specific
             judges available to hear specific matters (e.g., motions on Wednesday
             afternoon).
SCH-019.01        Provide ADMIN USER with the ability to define rules for random judge        0
                  assignment.
SCH-019.02        Provide ADMIN USER with the ability to define rules for judge               0
                  assignment based on rotation policy(s).
SCH-019.03        Provide ADMIN USER with the ability to define rules for judge               0
                  assignment based on caseload policies.
SCH-019.04        Provide ADMIN USER with the ability to define rules for judge               0
                  assignment based on other specific conditions.
SCH-019.05        Provide ADMIN USER with the ability to define rules for judge               0
                  assignment according to dates and times specific judges available to
                  hear specific matters.
SCH-020      Assign related cases, as designated by USER, to same judge and group
             together on schedule (e.g., multiple complaints regarding same problem or
             person). (see also Case Initiation and Indexing Function and Docketing
             and Related Recordkeeping Function)
SCH-020.01        Provide USER with the ability to relate CASES to be set on same court       0
                  docket.
SCH-020.02        Provide USER with the ability to schedule related CASES on same             0
                  court docket.
SCH-021      Generate report or display that lists all events due on specific date or date
             range sorted by date, event, or other criteria.

     MDEC Procurement K11-0030-29                                                                                   September 1, 2010
                                                MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                     ATTACHMENT C
                                                  MARYLAND ELECTRONIC COURT PROCUREMENT                            Page 68 of 249
                                                         FUNCTIONAL REQUIREMENTS

                                                                         SCHEDULING

     ID                                   Requirement Text                                     Response Code   Comments
SCH-021.01       Provide ADMIN USER with the ability to define fields for querying the     0
                 SCHEDULED EVENT records (e.g. for SCHEDULED EVENT to be
                 set).
SCH-021.02       Provide ADMIN USER with the ability to define fields that are displayed   0
                 in SCHEDULED EVENT search results.
SCH-021.03       Provide USER with the ability to search SCHEDULED EVENT based             0
                 on date or date range with multi-field sort capabilities.
SCH-022      Automatically prompt USER to schedule predefined related cases (e.g.,
             other complaints regarding same problem). (see also Case Initiation and
             Indexing Function and Docketing and Related Recordkeeping Function
             where relationships are defined to system, some automatically and some
             manually)
SCH-022.01       Automatically prompt USER to schedule related CASES.                      0
SCH-022.02       Provide USER with the ability to relate CASES to be scheduled             0
                 together.
SCH-022.03       Provide USER with the ability to assign SCHEDULED EVENT to                0
                 groups of CASES at one time.
SCH-022.04       Provide ADMIN USER with the ability to define rules for relating          0
                 CASES for scheduling purposes.
SCH-023      Generate alert when approaching maximum number of events or duration
             normally permitted on schedule (e.g., based on differential case
             management category, case type, case category), with ability to override
             maximums.
SCH-023.01       Provide ADMIN USER with the ability to define rules for maximum           0
                 number of events on a schedule.
SCH-023.02       Provide Admin USER with the ability to define rules for duration of       0
                 events on a schedule.
SCH-023.03       Automatically alert USER when schedule is approaching the                 0
                 maximum number of events or permitted duration.
SCH-023.04       Provide USER with the ability to override scheduling rules.               0
SCH-024      Maintain and display information on SCHEDULED EVENTS (e.g., next
             SCHEDULED EVENT, all SCHEDULED EVENTS, interface with docket to
             view past events).
SCH-024.01       Provide admin USER with the ability to define fields(s) for querying      0
                 Schedule Events.
SCH-024.02       Provide ADMIN USER with the ability to define fields(s) that are          0
                 displayed in the SCHEDULED EVENT results.

     MDEC Procurement K11-0030-29                                                                                September 1, 2010
                                                MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                    ATTACHMENT C
                                                  MARYLAND ELECTRONIC COURT PROCUREMENT                           Page 69 of 249
                                                         FUNCTIONAL REQUIREMENTS

                                                                        SCHEDULING

     ID                                  Requirement Text                                     Response Code   Comments
SCH-024.03       Provide USER with the ability to search on SCHEDULED EVENTS            0
                 within a single CASE and across multiple cases.
SCH-025      Enter completed events noted on administrative or clerk‘s calendar into
             docket.
SCH-025.01       Allow ADMIN USER to define rules on automatic creation of CASE         0
                 docket entries from data entered in courtroom.
SCH-025.02       Allow USER to record CASE activity (e.g., SCHEDULED EVENT              0
                 outcomes, charge/issue/relief disposition, party information) while in
                 courtroom.
SCH-026      Track conformance to time standards (e.g., answer or response due 30
             days after service to defendant) including modifications (e.g., move from
             one case management track to another), overrides (e.g., override
             requirement that answer or response due in 30 days and manually enter 60
             days), and suspension (e.g., suspend mental health classification) of time
             counting under certain conditions; and generate alerts for nonconformance.
SCH-026.01       Provide ADMIN USER with the ability to define rules for conformance 0
                 to time standards
SCH-026.02       Automatically track conformance to time standards based on rules      0
                 including modifications, overrides, and suspensions.
SCH-026.03       Provide ADMIN USER with the ability to define fields(s) for querying  0
                 time
                 Standard Conformance.
SCH-026.04       Provide ADMIN USER with the ability to define fields(s) that are      0
                 displayed in the Time Standard conformance data results.
SCH-026.05                                                                             0
                 Provide USER with the ability to search on time standard conformance data.
SCH-027      Support differential case management, ADR (e.g., mediation, arbitration),
             and other case management methods (e.g., schedule events within
             various sets of differential case management rules, schedule ADR events).

SCH-027.01        Provide ADMIN USER with the ability to define rules for scheduling    0
                  events based on DCM, ADR and other case management policies.
SCH-028      Include case age with any display of case status or adherence to
             schedules (e.g., tracking conformance to time standards).
SCH-028.01        Provide USER with the ability to view case age whenever case status   0
                  or adherence to schedule data is displayed.
SCH-029      During manual scheduling and rescheduling display other future events
             and related cases for that case.
     MDEC Procurement K11-0030-29                                                                               September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                    ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                           Page 70 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                            SCHEDULING

     ID                                   Requirement Text                                      Response Code   Comments
SCH-029.01        Provide USER with the ability to view future SCHEDULED EVENTS for 0
                  CASE and related CASES during scheduling of CASE.
SCH-030      Permit USERS to designate CASES with special scheduling needs (e.g.,
             interpreter, disabilities).
SCH-030.01        Provide ADMIN USER with the ability to define Special Scheduling       0
                  Needs codes.
SCH-030.02        Provide USER with the ability to assign special Scheduling needs to a 0
                  case.
SCH-031      Relate individual judges or groups of judges (including visiting judges) to
             departmental staff resources (e.g., bailiff's).

SCH-031.01        Provide ADMIN USER with the ability to define relationships between       0
                  case participants and court facilities and resources.
SCH-031.02        Provide USER with the ability to assign court facilities and resources to 0
                  case participants.
SCH-032      Allow USERS to define structure, content, and intrusiveness of ticklers,
             alerts, and prompts.
SCH-032.01       Provide ADMIN USER with the ability to individually configure the          0
                 structure, content, and intrusiveness of ticklers, alerts, and prompts.
SCH-033      Provide system-defined visual or audio reinforcement (e.g., flashing text,
             colors on screen, or computer icon) to ensure USER sees message.
SCH-033.01       Provide ADMIN USER with the ability to define default visual and/or        0
                 audio properties to highlight certain alerts/messages.
SCH-034      Display lists of all events due on specific date or date range (sorted by
             date, event, or other USER defined criteria) that allows USERS to navigate
             through the application to complete required activities (e.g., court minutes
             due).
SCH-034.01       Provide ADMIN USER with the ability to define fields(s) for querying       0
                 SCHEDULED EVENTS
SCH-034.02       Provide ADMIN USER with the ability to define fields(s) that are           0
                 displayed in the SCHEDULED EVENT results.
SCH-034.03       Provide USER with the ability to search on SCHEDULED EVENT                 0
                 Results.
SCH-034.04       Provide USER with the ability to select one or many SCHEDULED              0
                 EVENTS to invoke actions



     MDEC Procurement K11-0030-29                                                                                 September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 71 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                                           SCHEDULING

     ID                                     Requirement Text                                     Response Code   Comments
SCH-035      Generate alert when displaying pending cases for which there is no
             scheduled next event, or generate report for cases with no scheduled next
             event.
SCH-035.01        Provide ADMIN USER with the ability to define fields(s) for querying       0
                    pending CASES for which there is no SCHEDULED EVENT.
SCH-035.02        Provide ADMIN USER with the ability to define fields(s) that are           0
                  displayed in the Pending CASES with no SCHEDULED EVENT.
SCH-035.03        Provide USER with the ability to search for CASES with no Pending          0
                  events.
SCH-035.04        Provide USER with an alert anytime when a pending CASE is                  0
                    displayed and it has no scheduled next event
SCH-036      Track appearance of parties, status, courtroom, and staff at a hearing as
             needed based on local rules.
SCH-036.01        Provide USER with the ability to assign attendance of case participants    0
                  and court resources to a SCHEDULED EVENT.
SCH-037      Allow supervisor at appropriate level to turn alerts on and off.
SCH-037.01        Provide ADMIN USER with appropriate permissions to turn                    0
                  alerts/messages off and on.
SCH-038      Produce (including ability to reproduce, redisplay, or reprint) schedules for
             various individuals(all case participants) events, hearing types, dates, and
             facilities upon USER request (e.g., judges calendar by day).
SCH-038.01        Provide ADMIN USER with the ability to define fields for querying the      0
                  SCHEDULED EVENT records by specific fields including types of
                  events, dates, court participants and court resources.
SCH-038.02        Provide ADMIN USER with the ability to define fields that are displayed    0
                  in SCHEDULED EVENT search results.
SCH-038.03        Provide USER with the ability to search SCHEDULED EVENT records.           0
SCH-039      Maintain and produce information on SCHEDULED EVENTS for CASE
             (e.g., next SCHEDULED EVENT, all SCHEDULED EVENTS).
SCH-039.01        Provide ADMIN USER with the ability to define fields(s) for querying  0
                  all SCHEDULED EVENTS on a CASE.
SCH-040      Track inactive cases and groups of cases, identify those inactive for
             excessive periods (e.g., no activity for six months pending completion of
             psychological evaluation), prompt USER regarding appropriate action (e.g.,
             schedule hearing, extend dates).



     MDEC Procurement K11-0030-29                                                                                  September 1, 2010
                                                MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                    ATTACHMENT C
                                                  MARYLAND ELECTRONIC COURT PROCUREMENT                           Page 72 of 249
                                                         FUNCTIONAL REQUIREMENTS

                                                                         SCHEDULING

     ID                                  Requirement Text                                     Response Code   Comments
SCH-040.01       Provide ADMIN USER with the ability to define rules for determining      0
                 rules
                 for marking a CASE as having no activity.
SCH-040.02       Provide ADMIN USER with the ability define rules for determining next    0
                 action based on the state of a CASE marked as having no activity.

SCH-040.03        Provide ADMIN USER with the ability to define fields(s) for querying    0
                  CASES with no activity.
SCH-040.04        Provide ADMIN USER with the ability to define fields(s) that are        0
                  displayed in the CASES with no activity.
SCH-041      Prompt USER when persons and resources that should be considered in
             creating schedule have not been considered (e.g., juvenile probation
             officer, child protection case worker, GAL/CASA volunteer).
SCH-041.01        Provide ADMIN USER with the ability to define rules for matching case   0
                  participants and court resources to SCHEDULED EVENTS based on
                  CASE type, category and subcategory.
SCH-041.02        Automatically prompt USER when persons and resources not                0
                  scheduled should be considered.
SCH-041.03        Provide USER with the ability to search on CASE with no activity.       0
SCH-042      Generate alert when attempting operation with outstanding prerequisite
             events (e.g., case closed but adjudication date and result left blank,
             termination of parental rights (TPR) hearing scheduled but TPR motion or
             petition filed, etc.).
SCH-042.01      Provide ADMIN USER with the ability to define rules that set              0
                prerequisites for all events.
SCH-042.02      Automatically alert USER when attempting operation with outstanding       0
                prerequisite events.
SCH-042.03      Automatically prompt USER with the appropriate next action.               0
SCH-043      Generate alert when event scheduled or submitted for closed CASE.
SCH-043.01       Automatically alert USER when attempting to schedule event on a          0
                 closed CASE.
SCH-044      Allow USER management team to define initiation of automated
             scheduling processes based upon locally defined business rules.
SCH-044.01       Provide ADMIN USER to define rules for automatic scheduling of           0
                 CASES based on locally defined business rules.
SCH-044.02       Provide automatic scheduling of CASES.                                   0

     MDEC Procurement K11-0030-29                                                                               September 1, 2010
                                                MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                  MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 73 of 249
                                                         FUNCTIONAL REQUIREMENTS

                                                                          SCHEDULING

     ID                                    Requirement Text                                     Response Code   Comments
SCH-045      Allow for in-courtroom scheduling of the next case event and generation of
             the appropriate notices (i.e. status order, arraignment or judgment
             information, etc.).
SCH-045.01        Provide USER with the ability to assign SCHEDULED EVENTS to a           0
                  CASE while in courtroom.
SCH-045.02        Provide USER with the ability to produce notices for same while in      0
                  courtroom.
SCH-045.03        Provide USER with the ability to produce other court documents while    0
                  in courtroom.
SCH-046      Ability to selectively group multiple cases for scheduling, condition
             monitoring, and obligation fulfillment purposes.
SCH-046.01        Provide ADMIN USER with the ability to define fields(s) for querying      0
                  against
                  CASES and SCHEDULED EVENTS for condition monitoring and
                  obligation fulfillment purposes.
SCH-046.02        Provide ADMIN USER with the ability to define fields(s) that are          0
                  displayed in the CASES and SCHEDULED EVENTS results.
SCH-046.03        Provide USER with the ability to search on CASES/SCHEDULED EVENTS.        0
SCH-046.04        Provide USER with the ability to select one or many results               0
                   to invoke preconfigured actions.
SCH-047      Ability to electronically notify (e.g., email) automated scheduled court dates
             to the court participants (e.g., police and prosecutor,) as well as the
             cancellation or modification of those court dates.
SCH-047.01        Allow USER to assign indicator to case participant to receive electronic 0
                  instead of hard-copy SCHEDULED EVENT notices.
SCH-047.02        Allow system to generate electronic SCHEDULED EVENT notifications 0
                  (scheduling, cancellation, modifications) to case participants.

SCH-048      Permit system-wide date and time default format; System accepts date
             and time in any conventional format (e.g., military time) and converts to
             default format, with prompts for invalid or exceptional dates (past dates or
             dates far into the future).
SCH-048.01       Allow ADMIN USER to set system-wide date and time format default.        0
SCH-048.02       Allow system to convert user-entered date and time to default date and 0
                 time format.
SCH-049      Prompts date and time default values when entering date and time.


     MDEC Procurement K11-0030-29                                                                                 September 1, 2010
                                                   MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                     MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 74 of 249
                                                            FUNCTIONAL REQUIREMENTS

                                                                             SCHEDULING

     ID                                  Requirement Text                                          Response Code   Comments
SCH-049.01       Allow system to prompt for acceptable date and time format when            0
                 unrecognized format is entered by USER.
SCH-050      Allow USER management team to define frequency of prompts at USER
             level; USER can set special alerts and remarks which can be printed on
             calendars and displayed on courtroom display screens.
SCH-050.01       Allow ADMIN USER to customize prompts for USER.                            0
SCH-050.02       All USER with appropriate permissions to print/display special alerts      0
                 and free-form remarks on calendars and court dockets.
SCH-051      Display alert to a USER not authorized to see a portion of or a field within a
             record or omit unauthorized data (e.g. clerk views a sealed document).

SCH-051.01        Provide ADMIN USER with the ability to define security on record and         0
                  field levels.
SCH-051.02        Provide USER with the ability to assign a security level to records and      0
                  fields.
SCH-051.03        Provide ADMIN USER with the ability to define a rule to permit or            0
                  restrict display of record or field depending on security level.
SCH-051.04        Provide USER with alert when a selected record and field has security        0
                  restrictions.
SCH-052      If a violation involves federal or state license holders (such as a
             commercial motor vehicle, and/or the defendant holds a commercial
             driver‘s license (or other professional license such as medical, law, etc.)),
             issue an alert that federal guidelines apply to the case. In this situation the
             system should look-up the federal regulations or State statutes regarding
             commercial driver offenses and provides those to the Judge if requested
             by the Judge (the federal regulations for the commercial driver's license
             program web site link can be found in the Introduction).

SCH-052.01       Automatically provide USER[Judge] an alert if violation involves a            0
                 commercial motor vehicle.
SCH-052.02       Automatically provide USER[Judge] an alert if defendant holds a               0
                 commercial driver‘s license.
SCH-052.03       Automatically provide USER[Judge] an alert if defendant holds a               0
                 professional license.
SCH-053      Provide notice if judge attempts to issue PBJ, when another judge has
             issued Probation Before Judgment (PBJ) in other CASE.


     MDEC Procurement K11-0030-29                                                                                    September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                    ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                           Page 75 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                                          SCHEDULING

     ID                                  Requirement Text                                      Response Code   Comments
SCH-053.01       Provide ADMIN USER with the ability to define a rule for generating  0
                 alerts when a Judge issues a PBJ.
SCH-053.02       Provide USER an alert when VERDICT = PBJ and defendant has a         0
                 VERDICT = PBJ in another CASE.
SCH-054      Alert USER to any active internal warrant on the defendant should a USER
             access data about that defendant.
SCH-054.01       Provide ADMIN USER with the ability to define a rule for generating       0
                 alerts when a USER accesses a Party.
SCH-054.02       Provide USER an alert when local jurisdiction active warrant exists for   0
                 DEFENDANT when PARTY information is accessed.
SCH-055      Alert USER to any extra-jurisdictional active warrant on the defendant
             should a USER access data about that defendant.
SCH-055.01        Provide ADMIN USER with the ability to define a rule for generating      0
                  alerts when a USER accesses a Party.
SCH-055.02        Provide USER an alert when extra-jurisdictional active warrant exists    0
                  for DEFENDANT when PARTY information is accessed.
SCH-056      Permit USER management team to employ "if, then" and "if, then, unless"
             business rule conditional statements in event generation.
SCH-056.01        Provide ADMIN USER with the ability to define conditional workflow       0
                  processes to establish SCHEDULED EVENTS.
SCH-057      Allow USER management team to define hearing load and balance
             formulas based on locally defined business rules.
SCH-057.01        Provide ADMIN USER with the ability to define rules for SCHEDULED        0
                  EVENT load and balance formulas
SCH-058      Allow override of predefined hearing load and balance formulas.
SCH-058.01        Provide USER with the ability to override SCHEDULED EVENT load           0
                  and balance formulas
SCH-059      Ability to view all CASES for a chosen court within a date range.
SCH-059.01        Provide USER with the ability to list CASES with SCHEDULED               0
                  EVENTS for user-defined date or date range.
SCH-060      Ability to easily view the calendar of different courtrooms by day, by week
             or by month.
SCH-060.01        Provide USER with the ability to view courtroom schedules by day,        0
                  week or month.




     MDEC Procurement K11-0030-29                                                                                September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 76 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                                           SCHEDULING

     ID                                     Requirement Text                                     Response Code   Comments
SCH-061      Allow USER management team to define the number of days between
             triggers for differential case management and time standards as needed
             and automatically generate events, alerts and document production.
SCH-061.01        Provide ADMIN USER with the ability to define scheduling rules based       0
                  on DCM and case flow standards.
SCH-061.02        Provide ADMIN USER with the ability to define workflow which results       0
                  in automatic scheduling of events, display of alerts/messages, and
                  creation of documents.
SCH-062      Ability to track and display or print calendar modifications (e.g., judge, or
             other persons, or courtroom reassignments, cases taken off calendar) over
             specific period.
SCH-062.01        System log of modifications to SCHEDULED EVENT schedules.                  0
SCH-062.02        Allow ADMIN USER to define reports/displays of modifications to            0
                  SCHEDULED EVENT schedules.
SCH-063      Ability to add or delete time slots.
SCH-063.01        Provide USER the ability to add or delete time slots in any schedule.      0
SCH-064      Ability to undo re-assignments and/or reset to original with automated
             notice generation for rescheduled CASES.
SCH-064.01        System log of modifications to SCHEDULED EVENT schedules.                  0
SCH-064.02        Provide USER with ability to roll-back modifications to system             0
                  schedules, even after confirmation of changes.
SCH-064.03        Provide automated notice generation after change in schedules.             0
SCH-065      Provide the ability to process no-show cases based on pre-defined
             business rules (e.g., default judgments, suspension) but allow USER to
             override.
SCH-065.01        Allow ADMIN USER to define workflow for CASES meeting no-show              0
                  criteria.
SCH-065.02        Allow USER to select one or more CASES from court docket to                0
                  process based on business rules for instances such as failure to
                  appear.
SCH-065.03        Allow USER to override automated processing for business rules             0
                  involving no-show CASES
SCH-065.04        Provide ADMIN USER with the ability to define rules involving no-show      0
                  CASES
SCH-066      Allow display or reprint of notices from a list of notices.
SCH-066.01        Provide USER with the ability to display or reprint original notices for   0
                  SCHEDULED EVENTS.

     MDEC Procurement K11-0030-29                                                                                  September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                     ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                            Page 77 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                                           SCHEDULING

     ID                                   Requirement Text                                      Response Code   Comments
SCH-067      Ability to schedule one or more CASES to a specified scheduled court date
             by entering a specified court date and then entering the CASE and attorney.

SCH-067.01       Provide USER with the ability to assign many SCHEDULED EVENTS              0
                 to many CASES by selecting a date and then CASE and attorney.

SCH-068      Automatically print, store and docket court documents based on court
             events.
SCH-068.01       Provide ADMIN USER with the ability to define workflow and business        0
                 rules to be invoked based on CASE activity in courtroom.
SCH-068.02       Automated generation and storage of documents based on CASE                0
                 activity in courtroom.
SCH-068.03       Automated docket entries for documents created based on CASE               0
                 activity in courtroom.
SCH-068.04       Ability for USER to override automated workflow or business rules          0
                 based on CASE activity in courtroom.
SCH-069      Provide the ability to change the track of a case among traditional case
             processing and DCM processes, including adding, removing, or altering
             previously SCHEDULED EVENTS and ticklers for the changed track,
             according to business rules.
SCH-069.01       Provide ADMIN USER with the ability to define rules for scheduling         0
                 based on DCM or other required case processing.
SCH-069.02       Provide USER with the ability to change CASE DCM track or other            0
                 required CASE processing with automatic rescheduling of
                 SCHEDULED EVENTS as appropriate.
SCH-069.03       Provide USER with the ability to change CASE DCM track or other            0
                 required CASE processing with automatic changes to ticklers as
                 appropriate for new track.
SCH-070      Allow for motions and appeals to be filed and ruled upon at any point in the
             process.
SCH-070.01       Provide ADMIN USER with the ability to define workflow and business        0
                 rules for filing of motions and appeals
SCH-070.02       Provide USER with the ability to assign Motions and Appeals to the         0
                 CASE at any point in process.




     MDEC Procurement K11-0030-29                                                                                 September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 78 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                                          SCHEDULING

     ID                                    Requirement Text                                      Response Code   Comments
SCH-071      Accommodate the many types of motions and subject matter. Some
             motions, particularly those involving discovery, scheduling and DCM
             matters may follow slightly different processes even within the same Circuit.

SCH-071.01       Provide ADMIN USER with the ability to define motion codes.                 0
SCH-071.02       Provide ADMIN USER with the ability to define workflow and business         0
                 rules for filing of motions based on statutes, Rules, DCM and local
                 court processes for case type, category and subcategory.
SCH-071.03       Provide USER with the ability to override predefined workflow and           0
                 business rules.
SCH-072      Allow for an emergency track for motions that may bypass one or more
             process steps and are required to be ruled upon within a user-defined time
             frame.
SCH-072.01       Provide ADMIN USER with the ability to define workflow and business         0
                 rules for filing of motions based on statutes, Rules, DCM and local
                 court processes for case type, category and subcategory.
SCH-072.02       Provide USER with the ability to override predefined workflow and           0
                 business rules.
SCH-073      Hold the scheduling of CASES on calendars where effective service and/or
             other pre-requisites have not been recorded.
SCH-073.01       Provide ADMIN USER with the ability to define fields(s) for querying        0
                 CASES
                 where effective service and/or other prerequisites has not been
                 recorded for SCHEDULED EVENTS.
SCH-073.02       Provide ADMIN USER with the ability to define fields(s) that are            0
                 displayed in the results for unrecorded service and/or prerequisites for
                 SCHEDULED EVENTS.

SCH-073.03        Provide USER with the ability to search on CASES/SCHEDULED             0
                  EVENTS with unrecorded service and/or other prerequisites.
SCH-074      Provide automatic scheduling and sending of notices including writs (to all
             or select case participants) when postponement decisions are made by the
             clerk or the judicial officer.
SCH-074.01        Provide ADMIN USER with the ability to define rules for automatic      0
                  generation of SCHEDULED EVENT notices and other court
                  documents.


     MDEC Procurement K11-0030-29                                                                                  September 1, 2010
                                                MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                     ATTACHMENT C
                                                  MARYLAND ELECTRONIC COURT PROCUREMENT                            Page 79 of 249
                                                         FUNCTIONAL REQUIREMENTS

                                                                         SCHEDULING

     ID                                    Requirement Text                                    Response Code   Comments
SCH-074.02       Provide automated generation of SCHEDULED EVENT notices and               0
                 other court documents.
SCH-074.03       Provide USER with the ability to indicate one or more recipients of       0
                 SCHEDULED EVENT notices and other court documents.
SCH-075      Enable District Court to access Circuit Court schedules for specified case
             types when a JTP or appeal is requested, according to local jurisdiction‘s
             business rules.
SCH-075.01       Provide ADMIN USER with the ability to define rules on view access by     0
                 USER at different court levels.
SCH-075.02       Provide USER with the ability to view court dockets for different court   0
                 levels according to predefined business rules.
SCH-076      Allow ability to manually classify incoming CASES or initiating filings for
             locally-defined CASE or court types.
SCH-076.01        Provide USER the ability to MANUALLY classify incoming cases based 0
                  on locally-defined CASE or COURT TYPES.
SCH-077      Provide the ability to automatically schedule case in USER's district or
             another district, according to appropriate security and business rules from
             destination district (e.g., criminal cases only heard on certain days of week,
             ensuring VOPs are placed in front of appropriate judicial officer, etc.), with
             ability for USER to override automated scheduling.
SCH-077.01        Provide ADMIN USER with the ability to define scheduling rules which 0
                  allow, with appropriate permissions, for scheduling in another district
                  or location.
SCH-077.02        Provide USER with appropriate permissions ability to schedule events 0
                  in another district or location.
SCH-078      Ability to differentiate between event type scheduled originally by the court
             and event type actually concluded as separate elements.
SCH-078.01                                                                                  0
                  Provide USER with the ability to assign event type to a pending SCHEDULED EVENT.
SCH-078.02        Provide USER with the ability to assign another event type to the same 0
                  SCHEDULED EVENT that was concluded.
SCH-078.03        Provide USER with the ability to view the original result type and result 0
                  type that changed when concluded.
SCH-079      Ability to generate scheduling notices in batch or individually allowing for
             printing using varying media( e.g. using self address stamped mailer
             media). .
SCH-079.01        Provide USER with ability to generate notices individually.               0

     MDEC Procurement K11-0030-29                                                                                September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                       ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                              Page 80 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                            SCHEDULING

     ID                                     Requirement Text                                       Response Code   Comments
SCH-079.02        Provide USER with ability to generate notices in batch.                      0
SCH-080      Ability to distinguish between specially admitted attorneys and general
             Maryland bar. (See docketing and recordkeeping)
SCH-080.01        Provide indicator for specially admitted attorneys.                          0
SCH-081      Ability to maintain a centrally maintain listing of frequently used parties,
             bulk filers, etc.
SCH-081.01        Provide USER with the ability to select Participant from central             0
                  repository of case participants marked as frequent filers etc.
SCH-082      Ability to check incarceration status of case participants and prompt
             issuance of writs with the ability to control which case participants should
             receive writs.
SCH-082.01        Provide ADMIN USER with the ability to define fields(s) for querying         0
                  Participants across incarceration status and SCHEDULED EVENT.
SCH-082.02        Provide ADMIN USER with the ability to define fields(s) that are             0
                  displayed in the Participants /Incarceration/SCHEDULED EVENT
                  results.
SCH-082.03        Provide USER with the ability to search for participants who are             0
                  incarcerated and linked to a SCHEDULED EVENT.
SCH-082.04        Provide USER with the ability to select participants for generating writs.   0
SCH-082.05       Provide ADMIN USER with the ability to define rule for calculating case 0
                 age.




     MDEC Procurement K11-0030-29                                                                                    September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                    ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                           Page 81 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                          DOCUMENT GENERATION&PROCESSING

    ID                                  Requirement Text                                       Response Code   Comments
DGP-001      Allow USER to designate or override computer selection of recipients of
             documents.
DGP-001.01      Provide ADMIN USER with the ability to define rule for designating         0
                recipients of DOCUMENT [notices, forms, other outgoing].
DGP-001.02      Provide USER with the ability to override default selection of             0
                DOCUMENTS [notices, forms, other outgoing] recipients.
DGP-001.03      Provide USER with the ability to manually designate selection of           0
                DOCUMENTS [notices, forms, other outgoing] recipients.
DGP-002    Suppress inclusion of USER-designated confidential and redacted
           information in documents (e.g., mask out confidential addresses for
           notices sent to specific persons).
DGP-002.01     Provide ADMIN USER with the ability to define rule for identifying          0
               confidential information in DOCUMENTS [notices, forms, other
               outgoing].
DGP-002.02     Provide ADMIN USER with the ability to define rule for redacting            0
               information in DOCUMENTS [notices, forms, other outgoing].
DGP-002.03     Provide USER with the ability to assign an indicator to any field (e.g.     0
               address) to denote confidentiality.
DGP-003    Provide ability to override document entries made using the templates and
           standard text.
DGP-003.01        Provide ADMIN USER with the ability to define                            0
                  DOCUMENT[templates].
DGP-003.02        Provide USER with the ability to produce DOCUMENT from template.         0
DGP-003.03        Provide USER with the ability to override template formatting in         0
                  DOCUMENT.
DGP-004      Generate documents (e.g., summons, civil warrants, notices) triggered by
             a specific event (e.g., hearing scheduled).
DGP-004.01        Provide ADMIN USER with the ability to define rule for triggers on one   0
                  to many DOCUMENTS from one to many ACTIONS (e.g. triggers).

DGP-004.02        Provide USER with the ability to produce DOCUMENTS [notices,             0
                  forms, other outgoing] .
DGP-004.03        Provide ADMIN USER with the ability to define codes to associate         0
                  DOCUMENTs with CASE.


      MDEC Procurement K11-0030-29                                                                                September 1, 2010
                                                    MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                     ATTACHMENT C
                                                      MARYLAND ELECTRONIC COURT PROCUREMENT                            Page 82 of 249
                                                             FUNCTIONAL REQUIREMENTS

                                                            DOCUMENT GENERATION&PROCESSING

    ID                                   Requirement Text                                         Response Code   Comments
DGP-004.04    Provide ADMIN USER with the ability to define codes to associate                0
              DOCUMENTS with ACTIONS.
DGP-004.05    Provide ADMIN USER with the ability to define codes to associate                0
              DOCUMENTS with PARTIES.
DGP-005    Generate miscellaneous documents (e.g., for re-scheduled and canceled
           events, plaintiff claims forms, other types of forms).
DGP-005.01        Provide USER with the ability to produce DOCUMENT.                          0
DGP-006    Generate special notices (e.g., judge assignment, courtroom change,
           attorney change, schedule change, other courtesy notices) when
           requested.
DGP-006.01      Provide USER with the ability to produce DOCUMENT[notices].                   0

DGP-007       In cases with multiple active parties, generate single notice for participant
              who represents multiple parties.
DGP-007.01         Provide USER with the ability to produce a single DOCUMENT for             0
                   each unique PARTY/ATTORNEY.
DGP-007.02         Provide ADMIN USER with the ability to define rule for determining if      0
                   PARTY is active.
DGP-008       In cases with multiple active parties, show names and primary (e.g., as
              designated by party or attorney) addresses of all other active parties and
              attorneys on notice to specific active party and show names and primary
              addresses of all active parties on file copy of notice.
DGP-008.01         Provide USER with the ability to produce DOCUMENT for each unique          0
                   PARTY/ ADDRESS.
DGP-008.02         Provide USER with the ability to produce DOCUMENT [file copy]              0
                   containing selected PARTY/ATTORNEY/ADDRESS.
DGP-008.03         Provide ADMIN USER with the ability to define fields that are displayed    0
                   for ADDRESS.

DGP-009    Print documents individually or in batches in local courts or central location.
DGP-009.01     Provide USER with the ability to produce single DOCUMENTs.                  0
DGP-009.02     Provide USER with the ability to produce multiple DOCUMENTs in              0
               batches.
DGP-009.03     Provide USER with the ability to select printer for DOCUMENT printing. 0



      MDEC Procurement K11-0030-29                                                                                   September 1, 2010
                                                   MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                       ATTACHMENT C
                                                     MARYLAND ELECTRONIC COURT PROCUREMENT                              Page 83 of 249
                                                            FUNCTIONAL REQUIREMENTS

                                                           DOCUMENT GENERATION&PROCESSING

    ID                                 Requirement Text                                            Response Code   Comments
DGP-009.04       Provide USER with the ability to specify number of DOCUMENT                   0
                 copies to be printed.
DGP-009.05       Provide USER with the ability to use pre-printed forms such as certified 0
                 mailers or multi-part forms in a sealed packet with NCR copies.
DGP-009.06        Provide USER with the ability to sort DOCUMENTS printed in BATCH             0
                  mode by Zip Code to save postage.
DGP-009.07        Provide ADMIN USER with the ability to define specific printer and           0
                  form/page setup info, including BATCH mode for large numbers of
                  DOCUMENTS to be printed.
DGP-009.08         Provide USER with the ability to override default printer settings for      0
                  DOCUMENTS.
DGP-010      Distribute documents electronically (e.g., documents to be served to
             process server; notices and other documents to litigants and attorneys;
             notices, warrants, and other documents to be entered in docket). (see also
             Multifunction Capabilities and Integration and Docketing and Related
             Recordkeeping Function)
DGP-010.01        Provide USER with the ability to export DOCUMENTS.                           0
DGP-010.02        Interface E-filing                                                           0
DGP-011      Track document service, return of service, proof or certificate of service, re-
             service if necessary, and any other events.
DGP-011.01        Provide ADMIN USER with the ability to define fields that are displayed      0
                  for SERVICE.
DGP-011.02        Provide ADMIN USER with the ability to define codes to associate             0
                  SERVICE with DOCUMENT.
DGP-011.03        Provide ADMIN USER with the ability to define codes to associate             0
                  SERVICE with PARTY.
DGP-011.04        Provide USER with the ability to assign return of service date, re-          0
                  service date to SERVICE.
DGP-011.05        Provide USER with the ability to search for SERVICE.                         0
DGP-012      Perform document generation, printout, and distribution subfunctions for
             group of cases as if group was a single case.
DGP-012.01        Provide USER with the ability to produce multiple DOCUMENTS for              0
                  groups of CASES as if a single CASE.
DGP-012.02        Interface E-filing (distribution)                                            0



     MDEC Procurement K11-0030-29                                                                                     September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                     ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                            Page 84 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                          DOCUMENT GENERATION&PROCESSING

    ID                                    Requirement Text                                     Response Code   Comments
DGP-012.03      Provide admin USER with the ability to define rules for determining       0
                'case groups' for the purpose of producing multiple DOCUMENTS for
                groups of CASES as if a single CASE.
DGP-012.04      Provide USER with the ability to select DOCUMENTS to be included in 0
                the 'case group.'
DGP-013    In conjunction with Docketing and Related Recordkeeping Function, allow
           users to create and maintain files of output templates and standard text,
           including entire paragraphs, and use files to (1) create official court
           documents by inserting text into templates (e.g., civil warrants with text and
           images of court seals and signatures) and (2) create other documents
           consisting of only text (e.g., some types of notices). (see also External
           Interfaces[Appendix A])
DGP-013.01      Provide ADMIN USER with the ability to define DOCUMENT templates. 0
DGP-013.02         Provide USER with the ability to produce DOCUMENTs by inserting         0
                   text into templates.
DGP-013.03         Provide USER with the ability to produce DOCUMENTs containing           0
                   only boilerplate text.
DGP-013.04         Provide USER with the ability to produce DOCUMENTs containing           0
                   inserting graphical (e.g. seals and signatures) elements.
DGP-013.05         Provide ADMIN USER with the ability to define DOCUMENT graphical        0
                   elements.
DGP-014       Maintain only files of standard text and use to create entire documents or
              to insert text into boilerplate court forms; relate each group of text to
              document(s) and court event(s) for which they are used.
DGP-014.01         Provide ADMIN USER with the ability to define codes to associate        0
                   DOCUMENTS to ACTIONS.
DGP-014.02         Provide ADMIN USER with the ability to define DOCUMENT templates.       0

DGP-014.03     Provide USER with the ability to produce DOCUMENTs by inserting             0
               text into templates.
DGP-014.04     Provide USER with the ability to produce DOCUMENTs containing               0
               only boilerplate text.
DGP-014.05     Provide ADMIN USER with the ability to define central repositories for      0
               DOCUMENTs[court generated].
DGP-015    Produce electronic forms and other documents; distribute documents and
           receive responses (e.g., return of service) electronically.
DGP-015.01        Interface E-filing                                                       0
      MDEC Procurement K11-0030-29                                                                                September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 85 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                          DOCUMENT GENERATION&PROCESSING

    ID                                   Requirement Text                                        Response Code   Comments
DGP-016      Generate one notice for a case with multiple future court events to all
             participants.
DGP-016.01        Provide USER with the ability to produce one DOCUMENT containing           0
                  multiple SCHEDULED EVENTS.
DGP-016.02        Provide USER with the ability to produce DOCUMENT with multiple            0
                  SCHEDULED EVENTS to multiple related PARTIES.
DGP-016.03        Provide ADMIN USER with the ability to define rules stating which          0
                  DOCUMENTS are appropriate for which PARTY TYPES.
DGP-017      Provide ability to enter, store, and retrieve postal and electronic mail
             address (and other information pertaining to), for all person who should
             receive specific documents, from various locations in system and database
             as if, from user perspective, they were in same record.
DGP-017.01        Provide ADMIN USER with the ability to define fields that are displayed    0
                  for PARTY.
DGP-017.02        Provide USER with the ability to assign postal and electronic mail         0
                  address to PARTY.
DGP-017.03        Provide ADMIN USER with the ability to define codes to associate           0
                  DOCUMENTs to PARTY TYPES.
DGP-017.04        Provide ADMIN USER with the ability to define rules to 'batch' multiple    0
                  documents for a single party into the same envelope.
DGP-018      Record pertinent information regarding all documents sent or served, and
             track document issuance and follow-up activities including type of process,
             recipient, method of service, date of service, return of service, proof or
             certificate of service, failed service, re-service, any judicial proceedings,
             and status information (e.g., warrant tracking and warrant recall working
             with CJIS interface).
DGP-018.01        Provide USER with the ability to assign issued date, served date, sent     0
                  date, process type, recipient, method of service, date of service, date
                  of return of service, date of failed service, date of re-service to
DGP-018.02        SERVICESERVICE to Public Safety
                  Interface                                                                  0
DGP-018.03        Interface SERVICE to other agencies such as State Prosecutors              0
DGP-019      Allow system to create/record re-issued summonses and warrants due to
             non-service of original summons.
DGP-019.01       Provide USER with the ability to assign re-issue date to                    0
                 DOCUMENT[summons].



     MDEC Procurement K11-0030-29                                                                                   September 1, 2010
                                                   MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                        ATTACHMENT C
                                                     MARYLAND ELECTRONIC COURT PROCUREMENT                               Page 86 of 249
                                                            FUNCTIONAL REQUIREMENTS

                                                            DOCUMENT GENERATION&PROCESSING

    ID                                    Requirement Text                                          Response Code   Comments
DGP-019.02       Provide USER with the ability to produce DOCUMENTS[summons,                    0
                 warrants] by reissuing the original DOCUMENT.
DGP-020      Produce status of documents sent or served.


DGP-020.01        AUTOMATICALLY maintain history of DOCUMENTS generated.                        0
DGP-020.02        Provide USER with the ability to search for DOCUMENTS.                        0
DGP-020.03        Provide ADMIN USER with the ability to define rules for fields to retain      0
                  in DOCUMENT history.
DGP-020.04        Provide USER with the ability to create and store documents that have
                  an unofficial status(i.e. not considered part of the official court record)
                  (e.g. proposed orders)
DGP-020.05        Provide ADMIN USER with the ability to define rules for fields to             0
                  search on in DOCUMENT history.
DGP-021      Create orders resulting from out-of-the-courtroom events to be signed by
             judge in informal setting (e.g., ex parte protective custody orders signed in
             the judge‘s chambers). (see Hearings, Adjudication, and Disposition
             Function for orders that relate directly to formal, calendared event).
DGP-021.01        Provide USER with the ability to produce DOCUMENTS[orders] away               0
                  from the courtroom and to contol whether those documents are
                  considered part of the official court record
DGP-021.02        Provide USER[law clerk] with the ability to produce DOCUMENT[order]           0
                  and save document for later review and signing by the judge

DGP-021.03       Provide USER[judge] with the ability to edit DOCUMENT[orders] ,     0
                 assign signature and assign document an official status
DGP-021.04       Provide USER with the ability to assign signature to DOCUMENT while 0
                 generating the DOCUMENT or after generating the DOCUMENT.

DGP-021.05     Provide ADMIN USER with the ability to define CODES for out-of-                  0
               courtroom orders or other documents.
DGP-021.06     Provide ADMIN USER with the ability to define codes for unofficial               0
               documents
DGP-022    Insert proper address in documents based on document date compared
           with address histories. (see Docketing and Related Record keeping
           Function)


      MDEC Procurement K11-0030-29                                                                                     September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                    ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                           Page 87 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                          DOCUMENT GENERATION&PROCESSING

    ID                                Requirement Text                                         Response Code   Comments
DGP-022.01      Provide ADMIN USER with the ability to define a rule for determining       0
                the current ADDRESS for PARTY.
DGP-022.02      AUTOMATICALLY populate DOCUMENT with address information.                  0
DGP-023    Create notices when attorney, party, or participant changed for case with
           future scheduled event.
DGP-023.01        Provide ADMIN USER with the ability to define a rule workflow for        0
                  actions occurring when new PARTY, ATTORNEY, ADDRESS are
                  added.
DGP-024       Create notices when attorney, party, or participant address changed for
              case with future scheduled event.
DGP-024.01     Provide ADMIN USER with the ability to define workflow for actions          0
               occurring when new PARTY, ATTORNEY, ADDRESS are updated.
DGP-024.02     Provide USER with the ability to generate DOCUMENTS when a                  0
               PARTY is added or PARTY Address changed after DOCUMENTS
               [Notices, etc for a future event] have been printed.
DGP-025    Create file containing customized templates for specific person (e.g.,
           judge) consistent with court rules.
DGP-025.01        Provide ADMIN USER with the ability to define reports for CASE.          0
DGP-025.02        Provide USER with the ability to access file containing customized       0
                  templates to be used by a specific person (i.e. Judge) , with
                  appropriate security.
DGP-026       Allow for USER management team defined automated notifications (e.g.,
              email) based upon business rules governing case tracks.
DGP-026.01      Provide ADMIN USER with the ability to define rule for generating          0
                notifications (e.g. email).
DGP-026.02      Interface Notifications                                                    0
DGP-026.03      Provide ADMIN USER with the ability to define codes to trigger             0
                notification based on business rules for case tracking
DGP-027    Print forms and notices in multiple languages (e.g., English, Spanish, etc.),
           relating different language versions of the same form to one another to
           ensure updates are applied across all languages..
DGP-027.01      Provide ADMIN USER with the ability to define codes to associate           0
                DOCUMENT templates to DOCUMENT templates for the same
                document in a different languages.



      MDEC Procurement K11-0030-29                                                                                September 1, 2010
                                                   MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                     ATTACHMENT C
                                                     MARYLAND ELECTRONIC COURT PROCUREMENT                            Page 88 of 249
                                                            FUNCTIONAL REQUIREMENTS

                                                           DOCUMENT GENERATION&PROCESSING

    ID                                     Requirement Text                                      Response Code   Comments
DGP-027.02       Provide ADMIN USER with the ability to define codes to associate           0
                 party to non-English language requirement for notices and other
                 documents.
DGP-028       Support integration with electronic mail for electronic noticing.
DGP-028.01        INTERFACE Notifications                                                   0
DGP-029       Generate mailing labels.
DGP-029.01         Provide USER with the ability to produce DOCUMENT[labels].                0
DGP-029.02         Provide ADMIN USER with the ability to define fields that are displayed 0
                   on the DOCUMENT[labels].
DGP-030       Ability to print, display and reprint selected notices from a list of notices.
DGP-030.01      Provide ADMIN USER with the ability to define fields that are displayed 0
                in the list of DOCUMENT[notices].
DGP-030.02      Provide USER with the ability to search DOCUMENT[notices].              0
DGP-030.03      Provide USER with the ability to select one to many                     0
                DOCUMENTS[notices] for printing.
DGP-031    Ability to issue warrants, recalls/quash; and returns, and holds.
DGP-031.01     Provide ADMIN USER with the ability to define DOCUMENT[warrants,             0
               recalls/quashes].
DGP-031.02     Provide use with the ability to produce DOCUMENT[warrants,                   0
               recalls/quashes].
DGP-032    Allows for holding; releasing; or recalling of warrants and holds on future
           dates.
DGP-032.01     Provide ADMIN USER with the ability to assign status (e.g. hold,             0
               release, recall) to WARRANT.
DGP-033    Flags special conditions (e.g., post and forfeitable; night service; do not
           release on own recognizance, etc.).
DGP-033.01     Provide ADMIN USER with the ability define codes for                         0
               CASE/PARTY/DOCUMENT special conditions.
DGP-033.02     Provide USER with the ability to assign an indicator to                      0
               CASE/PARTY/DOCUMENT when special conditions (e.g., post and
               forfeitable; night service; do not release on own recognizance, etc.).
               occur in a case.
DGP-034    Reports warrants executed but not returned for filing.
DGP-034.01        Provide ADMIN USER with the ability to define fields for querying         0
                  WARRANT records .

      MDEC Procurement K11-0030-29                                                                                  September 1, 2010
                                                     MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                       MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 89 of 249
                                                              FUNCTIONAL REQUIREMENTS

                                                              DOCUMENT GENERATION&PROCESSING

    ID                                   Requirement Text                                           Response Code   Comments
DGP-034.02         Provide ADMIN USER with the ability to define fields that are displayed 0
                   in the WARRANT search results.
DGP-034.03         Provide ADMIN USER with the ability to define reports for               0
                   WARRANTS.
DGP-034.04         Provide USER with the ability to produce report for WARRANT.            0
DGP-035    Create register of action with information regarding all documents sent or served.

DGP-035.01          Provide ADMIN USER with the ability to define report for REGISTER           0
                    OF ACTIONS.
DGP-035.02          Provide ADMIN USER with the ability to define fields for querying           0
                    REGISTER OF ACTIONS records.
DGP-035.03          Provide ADMIN USER with the ability to define fields that are displayed     0
                    in the REGISTER OF ACTIONS.
DGP-035.04          Provide USER with the ability to produce report for REGISTER OF             0
                    ACTIONS.
DGP-036        Allows multiple recorded warrants per defendant per case; produce alert
               when subsequent warrants are issued for a case. Allow creation of a
               unique number (e.g., Warrant Number) to indicate which is being served
               and presented to the commissioner.
DGP-036.01          Provide USER with the ability to produce one to many WARRANTS for           0
                    one PARTY[Defendant]/CASE.
DGP-036.02          AUTOMATICALLY alert USER when multiple WARRANTS exist on a                  0
                    case.
DGP-036.03          Provide ADMIN USER with the ability to define rules for a unique            0
                    numbering sequence for warrants.
DGP-036.04          Provide USER with the ability to assign unique identifier to WARRANT        0
                    when issued.
DGP-037        Ability to integrate with USER defined word processing package (e.g.,
               Word and WordPerfect) to generate documents.
DGP-037.01          Provide USER with the ability to produce DOCUMENTS that can be              0
                    opened in word processing software.
DGP-037.02          INTERFACE to word processing applications.                                  0
DGP-038        Ability to print date and time in any conventional format (e.g., the default
               format could be mm/dd/yyyy but could be printed as January, 1, 2004).
DGP-038.01          Provide ADMIN USER with the ability to define rule for date format in       0
                    DOCUMENTS.


      MDEC Procurement K11-0030-29                                                                                     September 1, 2010
                                                MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                 ATTACHMENT C
                                                  MARYLAND ELECTRONIC COURT PROCUREMENT                        Page 90 of 249
                                                         FUNCTIONAL REQUIREMENTS

                                                         DOCUMENT GENERATION&PROCESSING

    ID                                Requirement Text                                    Response Code   Comments
DGP-038.02      Provide USER with the ability to choose Date format printing in       0
                DOCUMENTS.
DGP-039      Generate documents, calendars, correspondence in large font.
DGP-039.01       Provide ADMIN USER with the ability to define rule for determining   0
                 font size in DOCUMENTS.




     MDEC Procurement K11-0030-29                                                                            September 1, 2010
                                                      MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                        ATTACHMENT C
                                                        MARYLAND ELECTRONIC COURT PROCUREMENT                               Page 91 of 249
                                                               FUNCTIONAL REQUIREMENTS

                                                                                 CALENDARING

     ID                                     Requirement Text                                           Response Code   Comments
CAL-001    Suppress inclusion of user-designated confidential information in calendars (e.g.,
           mask out information such as juvenile name in adoption proceedings).
CAL-001.01     Provide ADMIN USER with the ability to define rules for display of fields.         0
CAL-001.02        Provide USER with the ability to assign an indicator to fields when those fields 0
                  contain confidential data.
CAL-002       Create, generate, and maintain calendars based on scheduling information
              and incorporate calendar addenda according to pre defined scheduling
              rules, accept electronic import file for the calendar configuration
              information (rotations, assignments out in time) for each type of hearing
              (e.g., jury trial, nonjury trial, motion, conference, dismissal) or mixed
              hearings (e.g., motions and settlements) for specific periods (e.g., daily,
              weekly, monthly) and according to various criteria (e.g., judge, date, time,
              case type, case category, other elements of calendar profiles).
CAL-002.01        Provide ADMIN USER with the ability to define rules for creating calendar       0
                  addenda.
CAL-002.02        Provide ADMIN USER with the ability to define rules for calendar                0
                  configuration by HEARING type.
CAL-002.03        Provide ADMIN USER with the ability to define rules for calendar                0
                  configuration by date range.
CAL-002.04        Provide ADMIN USER with the ability to define rules for calendar                0
                  configuration by other criteria.
CAL-002.05        Provide USER with the ability to assign data to calendar fields.                0
CAL-002.06        AUTOMATICALLY accept calendar information and apply to calendar fields.         0
CAL-003    Transfer easily and quickly between scheduling, calendaring, and other parts of
           the system when creating calendars (e.g., to view information on other cases,
           parties, participants).
CAL-003.01      Provide USER with the ability to navigate to screens for scheduling,              0
                calendaring, and other parts of the system.
CAL-004    Create and maintain judge‘s, master‘s, or administrator‘s notes (i.e., judges‘ notes
           and comments for use with calendar) for judges‘ viewing only in accordance with
           local rules and statutes.
CAL-004.01      Provide USER with the ability to assign data to a field within a DOCUMENT.        0
CAL-004.02        Provide USER with the ability to assign data to a field within a CASE.          0
CAL-004.03        Provide ADMIN USER with the ability to define fields that are associated with   0
                  a DOCUMENT.
CAL-004.04        Provide ADMIN USER with the ability to define fields that are associated with   0
                  a CASE.

      MDEC Procurement K11-0030-29                                                                                        September 1, 2010
                                                         MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                           MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 92 of 249
                                                                  FUNCTIONAL REQUIREMENTS

                                                                                     CALENDARING

     ID                                        Requirement Text                                         Response Code   Comments
CAL-004.05        Provide ADMIN USER with the ability to define rules for display of fields.        0
CAL-005       Distribute calendars electronically (e.g., jury manager, court reporters, sheriff).
CAL-005.01        Provide USER with the ability to send calendar information to another USER.       0

CAL-005.02        Provide ADMIN USER with the ability to define workflow for distribution of        0
                  calendar information.
CAL-005.03        AUTOMATICALLY distribute calendars based on workflow rules.                       0
CAL-006    Generate and display or print summary of upcoming hearings for a judge or in a
           courtroom over a specific period (e.g., a week), including past hearings.
CAL-006.01     Provide USER with the ability to search calendar information.                        0
CAL-006.02        Provide USER with the ability to print calendar information.                      0
CAL-006.03        Provide ADMIN USER with the ability to define "summary" calendar content.         0
CAL-006.04        Provide USER with the ability to generate reports from calendar information.      0
CAL-007       Display or print summary calendar information (e.g., for use in courtroom
              and could contain case number, hearing type, case title or style, hearing
              date and time, and other essential information from calendar) and provide
              interface to other parts of system to access other types of information (e.g.,
              on parties). (see also Management and Statistical Reports Function).

CAL-007.01        Provide USER with the ability to search calendar information.                     0
CAL-007.02        Provide USER with the ability to navigate to other parts of system by clicking    0
                  on data (e.g., party names, case numbers, etc.) in the calendar interface.
CAL-008    Provide flexibility with respect to calendar content and format (e.g., judges notes
           integrated into calendar).
CAL-008.01      Provide USER with the ability to configure data displayed on calendars.             0
CAL-008.02      Provide ADMIN USER with the ability to configure standard calendar formats          0
                for distinct USER TYPES.
CAL-009    Produce calendars individually (e.g., for a judge or courtroom) or batch (e.g., for
           posting throughout courthouse) according to various criteria including date, judge,
           or courtroom.
CAL-009.01      Provide USER with the ability to search calendar information.                       0
CAL-009.02        Provide USER with the ability to generate reports from calendar information.      0
CAL-009.03        Provide USER with the ability to print calendar information.                      0
CAL-009.04        Provide USER with the ability to sort and filter calendar information returned    0
                  from a search.



      MDEC Procurement K11-0030-29                                                                                         September 1, 2010
                                                       MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                       ATTACHMENT C
                                                         MARYLAND ELECTRONIC COURT PROCUREMENT                              Page 93 of 249
                                                                FUNCTIONAL REQUIREMENTS

                                                                                     CALENDARING

     ID                                      Requirement Text                                          Response Code   Comments
CAL-010    Produce calendars and related outputs individually or in batches in local courts or
           central location.
CAL-010.01      Provide USER with the ability to search calendar information.                      0
CAL-010.02        Provide USER with the ability to generate reports from calendar information.     0

CAL-010.03        Provide USER with the ability to print calendar information.                     0
CAL-010.04        Provide USER with the ability to sort and filter calendar information returned   0
                  from a search.
CAL-010.05        Provide USER with the ability to determine parameters for printing calendars.    0

CAL-011    Generate and output, with calendar, summary of user-designated past and future
           scheduled events, docket events, or related cases and persons.
CAL-011.01     Provide USER with the ability to search CASE EVENT information.                     0
CAL-011.02        Provide USER with the ability to retrieve calendar information from data         0
                  returned from a CASE EVENT search.
CAL-011.03        Provide USER with the ability to generate reports from calendar and EVENT        0
                  information.
CAL-011.04        Provide USER with the ability to print calendar information.                     0
CAL-011.05     Provide USER with the ability to sort and filter calendar information returned      0
               from a search.
CAL-012    Track and output calendar modifications (e.g., judge, or other persons, or
           courtroom reassignments, cases taken off calendar) over specific period.
CAL-012.01     AUTOMATICALLY log calendar transactions.                                            0
CAL-012.02        Provide USER with the ability to search and report on calendar transactions.     0

CAL-012.03       Provide USER with the ability to sort and filter calendar information returned 0
                 from a search.
CAL-013      Provide ability to move blocks of cases or user-selected cases between calendars.

CAL-013.01     Provide ADMIN USER with the ability to define rules for assigning data to a         0
               GROUP OF CASES.
CAL-013.02     Provide USER with the ability to assign CASES to a PERMANENT OR                     0
               TEMPORARY GROUP.
CAL-013.03     Provide USER with the ability to assign data to a GROUP OF CASES with a             0
               single process.
CAL-014    Create user-defined partial calendar.
CAL-014.01        Provide USER with the ability to define distinct calendar types.                 0
CAL-014.02        Provide USER with the ability to configure data displayed on calendars.          0

      MDEC Procurement K11-0030-29                                                                                        September 1, 2010
                                                       MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                        ATTACHMENT C
                                                         MARYLAND ELECTRONIC COURT PROCUREMENT                               Page 94 of 249
                                                                FUNCTIONAL REQUIREMENTS

                                                                                  CALENDARING

     ID                                      Requirement Text                                           Response Code   Comments
CAL-015    Record and output nature of proceeding for each case on calendar (e.g., review
           hearing to consider change of placement for neglected child).
CAL-015.01     Provide USER to assign proceeding type to CASE EVENT.                                0
CAL-015.02        Provide USER with the ability to search calendar information.                     0
CAL-015.03        Provide USER with the ability to generate reports from calendar information.      0

CAL-015.04        Provide USER with the ability to print calendar information.                      0
CAL-015.05         Provide USER with the ability to sort and filter calendar information returned   0
                   from a search.
CAL-016      Ability for courtroom management of an electronic calendar and courtroom
             document management.
CAL-016.01         Provide USER with the ability to assign data to the calendar from the            0
                   COURTROOM.
CAL-016.02         Provide USER with the ability to assign DOCUMENTS to the calendar from           0
                   the COURTROOM.
CAL-016.03         Provide ADMIN USER with the ability to define rules for data that may be         0
                   assigned by USER in the COURTROOM.
CAL-016.04         Provide ADMIN USER with the ability to define rules for DOCUMENTS that           0
                   may be assigned by USER in the COURTROOM.
CAL-017      Ability to display case participant check in information on judge‘s bench calendar.

CAL-017.01        Provide USER with the ability to assign a status of "checked in" or "not          0
                  checked in" to a CASE PARTICIPANT.
CAL-017.02        Provide ADMIN USER with the ability to define default check in status.            0
CAL-017.03      Provide USER with the ability to view check-in status of CASE                       0
                PARTICIPANTS from the bench.
CAL-017.04      Provide USER with the ability to assign CASE PARTICIPANT check-in status            0
                to calendar.
CAL-018    No limit on when or how often a calendar may be viewed, produced and printed.

CAL-018.01      Provide ADMIN USER with the ability to define rules for access to calendar          0
                data.
CAL-019    Allow user to review daily, weekly and monthly schedules for departments and
           judicial officers.
CAL-019.01      Provide USER with the ability to define search parameters when retrieving           0
                calendar data.
CAL-019.02      Provide ADMIN USER with the ability to define multiple standard calendar            0
                views for different user types.


      MDEC Procurement K11-0030-29                                                                                         September 1, 2010
                                                    MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                   ATTACHMENT C
                                                      MARYLAND ELECTRONIC COURT PROCUREMENT                          Page 95 of 249
                                                             FUNCTIONAL REQUIREMENTS

                                                                               CALENDARING

     ID                                    Requirement Text                                     Response Code   Comments
CAL-020    Allow for configuring the trials per day on a docket, since scheduling is done
           against dockets, rather than individual judges.
CAL-020.01      Provide ADMIN USER with the ability to define rules for EVENT assignment.   0
CAL-020.02       Provide USER with the ability to assign events to a DOCKET.                0
CAL-020.03       Provide ADMIN USER with the ability to define the objects to which         0
                 SCHEDULED EVENTS may be assigned.




     MDEC Procurement K11-0030-29                                                                                  September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                       ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                              Page 96 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                                             HEARINGS

    ID                                       Requirement Text                                    Response Code   Comments
HEA-001      With computational software and word processing interfaces, enable
             judges to examine implications of hypothetical judicial orders through
             calculations and "what if" scenarios (e.g., tax consequences of spousal
             support and property division; child support amounts for sole, shared, and
             split parenting arrangements; termination of jurisdiction based on minor‘s
             date of birth assist in the development of custody and visitation
             schedules(holidays, etc), emergency family maintenance, sentencing) and
             insert selected option into orders.
HEA-001.01        Provide ADMIN USER with the ability to define fields that are displayed    0
                  for creating an interface where judges can perform calculations and
                  "what if" scenarios.
HEA-001.02        Provide USER with the ability to review calculations and "What if"         0
                  scenarios and select options to populate DOCUMENT[orders].
HEA-001.03        Provide USER with the ability to attach spreadsheet, word processing       0
                  and other documents to orders.
HEA-002      Provide the ability to track whether an individual is serving jail time or is
             merely being detained.
HEA-002.01        Provide USER with the ability to assign an indicator to PARTY              0
                  distinguishing whether the party is serving a sentence or being
                  detained pre-sentence.
HEA-003      Maintain hypothetical analysis and notes separate from the official court
             record (non public view)
HEA-003.01        Provide USER with the ability to assign private notes to CASE that are     0
                  not part of the official court record.
HEA-003.02        Provide ADMIN USER with the ability to define rule for accessing           0
                  private notes on CASE.
HEA-004      Create and print court orders and supporting documents resulting from
             hearings and other judicial and ADR events on-line in courtroom.
HEA-004.01        Provide USER with the ability to produce DOCUMENT[orders, other]           0
                  for SCHEDULED EVENT while on-line in courtroom.
HEA-004.02        Provide ADMIN USER with the ability to create DOCUMENT templates.          0

HEA-005    Schedule subsequent events (e.g., continuances) on-line in courtroom and
           generate appropriate notices, maintaining audit trail of previous event
           including judge‘s name, and other case participant.
HEA-005.01      Provide USER with the ability to assign one to many SCHEDULED       0
                EVENTS to CASES while on-line in courtroom.

     MDEC Procurement K11-0030-29                                                                                   September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                   ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                          Page 97 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                                           HEARINGS

    ID                                   Requirement Text                                    Response Code   Comments
HEA-005.02     Provide USER with the ability to assign JUDGE, PARTY to                   0
               SCHEDULED EVENT.
HEA-005.03     AUTOMATICALLY maintain history of SCHEDULED EVENT.                        0
HEA-005.04     Provide USER with the ability to produce DOCUMENT[notices, other]         0
               while on-line in the courtroom.
HEA-006    Provide the ability to track who requested change to hearing schedule
           (judge, attorney, etc.).
HEA-006.01     Provide USER with the ability to assign "requested by" to                 0
               SCHEDULED EVENT when a request for change is granted.




HEA-007      Employ output templates, standard text, and user-supplied text analogous
             to methodology described in Document Generation and Processing
             Function to generate documents noted above (e.g., standard information in
             minute orders such as judge, court staff, attorneys and parties present
             evidence, witnesses, motions, bench times, judge specific conditions).

HEA-007.01      Provide ADMIN USER with the ability to define DOCUMENT templates 0
                for Court minutes.
HEA-007.02      Provide USER with the ability to produce DOCUMENT[orders, other]         0
                for SCHEDULED EVENT while on-line in courtroom.
HEA-008    Suppress inclusion of user-designated confidential information in
           documents produced during hearing (e.g., record in minutes that ADR
           event occurred on a given date, but mask out confidential statements by
           parties) (see also Security Function).
HEA-008.01      Provide USER with the ability to define rule for displaying confidential 0
                information in DOCUMENTS [all].

HEA-008.02     Provide ADMIN USER with the ability to define rule for identifying and    0
               redacting confidential information in DOCUMENTS.
HEA-008.03     Provide USER with the ability to assign an indicator to any field to      0
               denote confidentiality.
HEA-009    Provide for minute entry using one of the methods noted below.



      MDEC Procurement K11-0030-29                                                                              September 1, 2010
                                                MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                     ATTACHMENT C
                                                  MARYLAND ELECTRONIC COURT PROCUREMENT                            Page 98 of 249
                                                         FUNCTIONAL REQUIREMENTS

                                                                           HEARINGS

    ID                                     Requirement Text                                   Response Code   Comments
HEA-009.01       Provide USER with the ability to assign minutes to SCHEDULED             0
                 EVENT.
HEA-010      Allow for automated and/or manual generation of worksheet, calendar, or
             some other document suitable for on-line, rapid, in-court minute entry.
HEA-010.01       Provide ADMIN USER with the ability to define DOCUMENT templates         0
                 for Court minutes.
HEA-010.02       Provide USER with the ability to produce DOCUMENT[worksheet] to          0
                 assist in rapid in-court minute entry.
HEA-011      Generate and display or print worksheet, calendar, or some other
             document suitable for manually recording minutes. (see also Document
             Generation and Processing Function and Calendaring Function).
HEA-011.01       Provide USER with the ability to produce DOCUMENT[worksheet] to          0
                 assist in manual in-court minute entry.
HEA-012      Enter, store, and display or print minutes recorded on calendar or
             worksheet.
HEA-012.01       Provide USER with the ability to edit, save, display or pritn minutes    0
                 recorded on a calendar or worksheet.
HEA-013      Provide edits and prompts with on-line minute entry capability. (see also
             Security Function).
HEA-013.01       Provide ADMIN USER with the ability to define workflow for capturing     0
                 on-line minute entry.
HEA-014      Enter, store, and document minute orders, including informal minute orders
             when there is no corresponding calendared event (e.g., ex parte matters),
             according to local court rules. (see also List of Code Translation Tables)

HEA-014.01      Provide USER with the ability to assign minutes to CASE even when         0
                there is no Scheduled Event.
HEA-015    Distribute court orders resulting from hearings and other judicial (e.g.,
           mental health) and ADR events electronically to outside parties and
           internally to be entered in docket. And provide the ability to certify the
           dockets with electronic signature or other methods.
HEA-015.01      INTERFACE DOCUMENTS to agencies.                                          0
HEA-015.02      Provide USER with the ability to assign electronic signatures to          0
                DOCUMENTS.
HEA-015.03      Provide USER with the ability to assign a certification to DOCUMENTS.     0



      MDEC Procurement K11-0030-29                                                                               September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                       ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                              Page 99 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                              HEARINGS

    ID                                   Requirement Text                                         Response Code   Comments
HEA-016    Enter information in court orders and judgments resulting from hearings
           and other judicial (e.g., mental health) and ADR events as events in docket
           (if not entered AUTOMATICALLY through previous subfunction).
HEA-016.01      Provide USER with the ability to assign DOCUMENTS and                  0
                SCHEDULED EVENTS to CASE.
HEA-017    Distribute court orders resulting from hearings and other judicial and ADR
           events based upon party‘s preference (e.g., mail, facsimile, e-mail) if
           multiple distribution methods are available.
HEA-017.01      Provide USER with the ability to assign one to many contact            0
                preferences to PARTY.
HEA-017.02        AUTOMATICALLY distribute document according to contact                      0
                  preference for PARTY.
HEA-018      Provide for minute entry suitable for multiple-case and multiple-defendant.
HEA-018.01        Provide USER with the ability to assign MINUTE ENTRY to one or              0
                  many CASES.
HEA-019      Provide USER-defined format for real-time, in-court entry of minutes or
             entry of minutes after judicial proceedings.
HEA-019.01        Provide ADMIN USER with the ability to define fields that are displayed     0
                  for MINUTE ENTRY by court level, court location and case category
                  and case type.
HEA-020      Use events captured in minutes to interface with other functions and
             update records throughout system (case consolidation, address changes,
             etc.) in accordance with state and local statutes, rules, or procedures (e.g.,
             sentencing, accounting, adjournments, continuances, rescheduling, notice
             generation with accompanying docket entries).
HEA-020.01        Provide ADMIN USER with the ability to define workflow surrounding          0
                  further activity based on MINUTE ENTRY.
HEA-021      Create and print (including ability to reprint) jury instructions linked to
             specific charges (criminal) or counts (civil) in jury trials.
HEA-021.01        Provide USER with the ability to produce DOCUMENT[jury                      0
                  instructions] for each CHARGE, ISSUES.




      MDEC Procurement K11-0030-29                                                                                   September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                    ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                          Page 100 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                                            HEARINGS

    ID                                     Requirement Text                                   Response Code   Comments
HEA-022    Send request for investigations and receive materials to and from other
           units to assist in judicial functions as permitted by rules, statutes and
           procedures (e.g., send pre-sentence information to pre-sentence
           investigation unit and receive results of investigation for use in sentencing,
           conviction information to adult probation unit and probation information
           from unit, contents of order for psychological evaluation to non-justice
           agencies and results of evaluation from non-justice agencies, psychiatric
           requests and evaluation and initiation of VOP, child protective services
HEA-022.01 evaluation).
                INTERFACE DOCUMENTS to PARTY.                                             0
HEA-023    Send request for investigations and receive materials to and from other
           units to assist in judicial functions as permitted by rules, statutes and
           procedures (e.g., send pre-sentence information to pre-sentence
           investigation unit and receive results of investigation for use in sentencing,
           conviction information to adult probation unit and probation information
           from unit, contents of order for psychological evaluation to non-justice
           agencies and results of evaluation from non-justice agencies, psychiatric
           requests and evaluation and initiation of VOP, child protective services
           evaluation).
HEA-023.01      INTERFACE bi-directional COURT to AGENCIES.                               0
HEA-024    Compute, or receive from Criminal Support Functions, and enter credit for
           time served (credit can be applied on the case as a whole or on
           consecutive counts) or excludable into sentence imposed for each
           combination of charge and defendant in accordance with state and local
           statutes, rules, or procedures.
HEA-024.01      Provide USER with the ability to assign credit for time served to CASE. 0

HEA-024.02       Provide USER with the ability to assign credit for time served to        0
                 CHARGE.
HEA-024.03       Provide ADMIN USER with the ability to define rule to calculating credit 0
                 for time served.
HEA-025    Compute or receive and enter monetary penalties (e.g., fines, fees,
           restitution) allowing for deferrals and entry of civil judgments based on
           sentence imposed for each combination of charge, Requested Relief
           (civil), and defendant in accordance with state and local statutes, rules, or
           procedures.



      MDEC Procurement K11-0030-29                                                                               September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                            Page 101 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                              HEARINGS

    ID                                 Requirement Text                                          Response Code   Comments
HEA-025.01       Provide USER with the ability to assign monetary penalties to               0
                 CASES/CHARGES/ISSUES/RELIEF.


HEA-025.02        Provide ADMIN USER with the ability to define rule for deferring and       0
                  entering judgments based on SENTENCE.
HEA-026      Provide access to sentencing guidelines for charges in a case.
HEA-026.01        Provide ADMIN USER with the ability to define central repositories for     0
                  CHARGES.
HEA-026.02        Provide ADMIN USER with assign sentencing guideline information to         0
                  one to many CHARGES.
HEA-026.03        Provide ADMIN USER with the ability to define fields to display for        0
                  sentencing guideline information for CHARGE.
HEA-026.04        Provide USER with the ability to search for sentencing guidelines for      0
                  CHARGES.
HEA-027      Compute, (or receive) and enter non-monetary provisions (e.g., work
             program, restitution by services) based on sentence imposed for each
             combination of charge and defendant in accordance with state and local
             statutes, rules, or procedures.
HEA-027.01        Provide USER with the ability to assign non-monetary provision (e.g.       0
                  work program, restitution by services) to CHARGES.
HEA-028      Link charges (criminal) or counts-requested relief (civil) and fine,
             restitution, civil judgment , and bond forfeiture amounts.
HEA-028.01        Provide USER with the ability to assign FINE, RESTITUTION, JUDGE,          0
                  BOND to CHARGES/ISSUE/RELIEF.
HEA-029      Enter other details of sentence (e.g., whether consecutive or concurrent,
             conditions for probation, allow for merging of counts, probation start times,
             re-imposition after appeal is remanded or dismissed, allow for sentencing
             of non count offenses such as enhanced penalties, lesser included
             offenses, surrendering of a licensure and sex offense registration
             mandate) for each charge and defendant.




     MDEC Procurement K11-0030-29                                                                                   September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                       ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 102 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                              HEARINGS

    ID                                      Requirement Text                                      Response Code   Comments
HEA-029.01        Provide USER with the ability to assign other details (e.g., whether        0
                  consecutive or concurrent, conditions for probation, allow for merging
                  of counts, probation start times, re-imposition after appeal is remanded
                  or dismissed, allow for sentencing of non count offenses such as
                  enhanced penalties, lesser included offenses, surrendering of a
                  licensure and sex offense registration mandate) for each charge and
                  defendant.
HEA-029.02        Provide ADMIN USER with the ability to assign CODES for other               0
                  details (e.g., whether consecutive or concurrent, conditions for
                  probation, merging of counts, re-imposition after appeal is remanded
                  or dismissed, allow for sentencing of non count offenses such as
                  enhanced penalties, lesser included offenses, surrendering of a
                  licensure and sex offense registration mandate) for each charge and
                  defendant.
HEA-030      Compute, or receive from Criminal Support Functions, and enter probation
             term and compute, or receive expiration date of probation. (see Criminal
             Support Function)
HEA-030.01        Provide USER with the ability to assign probation terms to                  0
                  CHARGE/PROBATION.
HEA-030.02        INTERFACE Parole and Probation to court.                                    0
HEA-031      Produce minutes recorded on calendar or worksheet; provide the ability to
             copy specified features of the case decision for similar cases of same
             defendants (e.g., comments, attendees, adjournments, extensions, plea,
             or motion).
HEA-031.01        Provide USER with the ability to assign MINUTE ENTRY to one or              0
                  many cases.
HEA-031.02        Provide USER with the ability to assign comments, attendees,                0
                  adjournments, extensions, pleas and motions to MINUTE ENTRY.
HEA-032      Ability to complete data entry on specific data elements to account for what
             has occurred during court proceeding and allow for free form text in a
             remarks field including the ability to indicate whether comments are private
             (either private for court use or private for judge‘s use) or public and update
             records throughout system in accordance with state and local statutes,
             rules, or procedures (e.g., sentencing, accounting, adjournments,
             continuances, rescheduling, notice generation with accompanying docket
             entries).


     MDEC Procurement K11-0030-29                                                                                    September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                     ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                           Page 103 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                                            HEARINGS

    ID                                 Requirement Text                                        Response Code   Comments
HEA-032.01       Provide USER with the ability to assign free form text remarks to         0
                 MINUTE ENTRY.
HEA-032.02       Provide ADMIN USER with the ability to define rule for MINUTE             0
                 ENTRY security allowing for public, court only, or judge's only security.

HEA-033    Provide the ability to process no-show cases based on pre-defined
           business rules. Cases could be processed individually and in batch.
HEA-033.01      Provide ADMIN USER with the ability to define rule for applying           0
                MINUTE ENTRY to one or many cases individually or in batch.
HEA-034
HEA-034.01      Provide USER with the ability to search PARTY and view indicators         0
                regarding party status (e.g., repeat offenders, incarceration status,
                outstanding fees).
HEA-035    Accept secured digitized signatures on the completed form for a specific
           case at a specific hearing.
HEA-035.01      Provide USER with the ability to assign digitized signatures to           0
                DOCUMENTS.
HEA-036    Provide drop down selections (allowing for both statewide and locally
           defined selections),as opposed to typing information in fields, when
           docketing courtroom outcomes.
HEA-036.01      Provide USER with the ability to assign codes to MINUTE ENTRY text        0
                fields.
HEA-036.02      Provide ADMIN USER with the ability to define codes for MINUTE            0
                ENTRY text fields for each court level, location, and case type.
HEA-037    Provide automatic removal of postponed or paid cases from the docket.
HEA-037.01      Provide ADMIN USER with the ability to define rule to removing cases      0
                from the docket
HEA-038    Allow pleas to be entered beforehand and/or group cases together and
           allow multiple charges or cases with the same plea to be disposed as a
           single case (e.g. grouping case for in courtroom processing; only the same
           defendant or multiple defendants or same landlord in landlord/tenant
           processing, all unrepresented parties, etc).
HEA-038.01      Provide USER with the ability to assign pleas to MINUTE ENTRY in          0
                one or many cases/charges.
HEA-039    Capture (and provide a verification method for the captured data) the
           courtroom activities and outcomes that match the judges' worksheets or
           oral decisions.

      MDEC Procurement K11-0030-29                                                                                September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                            Page 104 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                              HEARINGS

    ID                                      Requirement Text                                     Response Code   Comments
HEA-039.01        Provide USER with the ability to assign data to complete the court's       0
                  MINUTE ENTRY.
HEA-039.02        Provide ADMIN USER with the ability to define fields of MINUTE             0
                  ENTRY so that they can be configured to match worksheets or oral
                  decisions.
HEA-039.03        Provide USER with the ability to review MINUTE ENTRY before                0
                  updating the CASE.
HEA-040      Provide visibility to calendars in the courtroom to ensure dates discussed
             are feasible.
HEA-040.01        Provide USER with the ability to search SCHEDULED EVENT in open            0
                  court during proceedings.
HEA-041      Provide the ability to account for/calculate/credit time served for
             commitments, allowing for multiple date ranges for non consecutive
             incarceration terms.
HEA-041.01        Provide USER with the ability to assign credit for time served to          0
                  SENTENCE using on multiple date ranges.
HEA-042      Provide visibility of Circuit Court schedule or calendar regarding JTPs.
HEA-042.01        Provide USER with the ability to search SCHEDULED EVENT in open            0
                  court during proceedings.
HEA-043      Provide a verification process to ensure orders are correct.
HEA-043.01        Provide USER with the ability to review DOCUMENT[orders] before            0
                  updating the CASE.
HEA-044      Provide the ability to scan hand written notes and attach to the case file or
             a specific document, event, or participant in a case.
HEA-044.01        Provide USER with the ability to assign scanned images to CASE,            0
                  EVENT, PARTY.
HEA-044.02        INTERFACE to DMS.                                                          0
HEA-045      Allow judge and clerk to view the same document at the same time.
HEA-045.01        Provide USER with the ability to view one or many DOCUMENTS by             0
                  one or many USERs at the same time.
HEA-046      Provide the ability for the judge and clerk to access 2 cases at once.
HEA-046.01        Provide USER with the ability to view one or many CASES by one or          0
                  many USERs at the same time.
HEA-047      Provide the ability to give a defendant a consolidated plea agreement
             across cases.
HEA-047.01        Provide USER with the ability to assign plea to one or many                0
                  CHARGES/one or many CASES.
     MDEC Procurement K11-0030-29                                                                                   September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                  ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                        Page 105 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                                           HEARINGS

    ID                                    Requirement Text                                  Response Code   Comments
HEA-048    Provide access to marriage licenses.
HEA-018.01     INTERFACE to Marriage Licenses.                                          0
HEA-049    Allow the digital recording of the court record to be attached to the
           electronic case file.
HEA-049.01     Provide USER with the ability to assign digital recordings to CASE.      0
HEA-049.02     INTERFACE to ECM.                                                        0
HEA-050    Allow video files to be attached to the electronic case file.
HEA-050.01     Provide USER with the ability to assign digital video files to CASE.     0
HEA-050.02     INTERFACE to ECM.                                                        0
HEA-051    Provide a mechanism for submission, queuing, and tracking of motions for
           a judge to rule on in chambers.
HEA-051.01     Provide USER with the ability to search MOTIONS on CASES based           0
               on a pre-determined review date.
HEA-051.02     Provide USER with the ability to assign review date to MOTIONS.          0
HEA-051.03     Provide USER with the ability to assign review judge to MOTIONS.         0
HEA-051.04     Provide USER with the ability to sort MOTIONS based on review date,      0
               review judge.
HEA-051.05     Provide USER with the ability to produce notifications to JUDGES         0
               when cases require review.
HEA-052    Provide the ability to track fugitive warrants and transmit status to law
           enforcement agency and notify the clerks.
HEA-052.01     INTERFACE WARRANTS to Public Safety, Other agencies.                     0

HEA-052.02     INTERFACE Public Safety to Courts-WARRANTS.                              0
HEA-052.03     Provide USER with the ability to search WARRANTS on CASE.                0
HEA-053    Allow the judicial officer to review multiple cases/documents in those cases
           to be viewed at the same time even if those documents are not on the
           docket.
HEA-053.01     Provide USER with the ability to search, view DOCUMENTS from one 0
               or many CASEs at one time even if the case is not on the docket.

HEA-053.02      ECM functionality.                                                      0
HEA-054    Allow for judicial officers and other court personnel to be assigned cases
           (e.g. sub curia, chambers work) for review. Case should be presented in
           electronic queues.


      MDEC Procurement K11-0030-29                                                                             September 1, 2010
                                                   MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                     MARYLAND ELECTRONIC COURT PROCUREMENT                            Page 106 of 249
                                                            FUNCTIONAL REQUIREMENTS

                                                                              HEARINGS

    ID                                      Requirement Text                                      Response Code   Comments
HEA-054.01        Provide USER with the ability to assign court personnel to CASE for         0
                  review.
HEA-054.02        Provide USER with the ability to search CASES in electronic queues          0
                  by the assigned court personnel, date assigned, case type, case
                  number or other case elements
HEA-054.03        Provide ADMIN USER with the ability to define fields for displaying         0
                  CASES that are assigned to court personnel for review.
HEA-055       Allow for a report of sub curia cases.
HEA-055.01        Provide USER with the ability to assign an indicator to CASE for            0
                  flagging a case as sub curia.
HEA-055.02        Provide ADMIN USER with the ability to define rule for assigning            0
                  indicator to cases flagged as sub curia.
HEA-055.03        Provide USER with the ability to search and produce report of sub           0
                  curia cases.
HEA-056       Allow for reference to physical evidence by maintaining (location, owner,
              and other details)
HEA-056.01        Provide USER with the ability to assign location, owner, other details to   0
                  EXHIBITS[physical evidence].

HEA-056.02     Provide USER with the ability to assign EXHIBITS to one or many                0
               CHARGES/CASES.
HEA-057    Allow for searching with a single case for a specific motion/filing party/date,
           events, financial date (bond amount) and other keywords.
HEA-057.01     Provide USER with the ability to search CASES by MOTIONS,                      0
               PARTY,SCHEDULED EVENT,ACCOUNTING [transactions], and
               other case components.
HEA-057.02     Provide ADMIN USER with the ability to define fields for searching             0
               CASES by MOTIONS, PARTY, SCHEDULED EVENT,
               ACCOUNTING[transactions] and other case components.
HEA-058    Allow for each document to be identified by a unique reference number
           .(sequence number)
HEA-058.01     Provide USER with the ability assign unique identifier to MOTIONS on           0
               CASE.




      MDEC Procurement K11-0030-29                                                                                   September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                   ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                         Page 107 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                              HEARINGS, ADJUDICATION, DISPO

    ID                                     Requirement Text                                    Response Code   Comments
HAD-001      Give judge, commissioner, masters, and clerk real-time access to system
             (e.g., for judge to examine legal issues).

HAD-001.01      Provide USER with the ability to directly access CMS from the              0
                courtroom.
HAD-002      Real-time update of data returned to users who are not in the courtroom.
HAD-002.01        Provide USER with ability to access data entered in the courtroom in     0
                  real-time.
HAD-003      Create one or multiple minute orders for multiple persons and hearings on
             a given day.
HAD-003.01       Provide USER with ability to create one or more orders for multiple      0
                 persons and hearings on a given day.
HAD-004      Create and print court orders and supporting documents (e.g., notices of
             court orders issued in child abuse cases relating to law enforcement
             registries including sex offender registries, victim impact statements)
             resulting from hearings and other judicial and ADR events individually or in
             a group, immediately or at a scheduled time.
HAD-004.01       Provide USER with the ability to create and print supporting court       0
                 documents resulting from hearings and other judicial and ADR events.

HAD-004.02        Provide USER with the ability to create and print supporting court       0
                  documents individually or in groups.
HAD-004.03        Provide USER with the ability to create and print supporting court       0
                  documents immediately or at a scheduled time.
HAD-005      Associate monetary and non-monetary restitution with specific case
             participant(s).
HAD-005.01        Provide USER with the ability to associate RESTITUTION[monetary          0
                  and non-monetary] with the receiving PARTY(s) (i.e. victim, etc).
HAD-005.02        Provide ADMIN USER to define codes for restitution types.                0
HAD-005.03        Provide User with the ability to assign RESTITUTION[monetary and         0
                  non-monetary] with the PARTY(s) ordered to pay restitution.
HAD-005.04        Provide User with the ability to assign the amount of restitution each   0
                  PARTY is required to pay.
HAD-006      Create multiple judgments (i.e., both multiple judgments for given person
             and multiple recipients for given judgment) in cases involving multiple
             juveniles/defendants/participants and allegations/charges/relief.


     MDEC Procurement K11-0030-29                                                                                September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                       ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 108 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                               HEARINGS, ADJUDICATION, DISPO

    ID                                     Requirement Text                                        Response Code   Comments
HAD-006.01        Provide USER with the ability to assign many JUDGMENTS to a                  0
                  PARTY.
HAD-006.02        Provide USER with the ability to assign many PARTIES                         0
                  to a single JUDGMENT.
HAD-007      Permit electronic referral of case information to public and private agencies
             (e.g., those charged with child protection, state and local government
             agencies, state and local government attorneys, law enforcement, public
             and private mental health agencies, civil mediators and other
             organizations).
HAD-007.01        AUTOMATICALLY export JUDGMENT information to subscribers.                    0
HAD-007.02        Provide ADMIN USER with the ability to define codes for REFERRAL             0
                  SERVICES (i.e. Anger Management, Mental Health Treatment).

HAD-007.03        Provide ADMIN USER with the ability to define codes for REFERRAL             0
                  SERVICES OUTCOME (i.e. completed successfully/unsuccessfully,
                  withdrew).
HAD-007.04        Provide USER with the ability to assign one or more REFERRAL                 0
                  SERVICES to a hearing.
HAD-007.05        Provide USER with the ability to assign one or more REFERRAL                 0
                  SERVICES OUTCOME to a REFERRAL SERVICE.
HAD-008      Capture information for each party associated with a hearing including
             check-in date and time, when hearing began and ended, bench time, when
             party called into hearing, whether party actually appeared in hearing (e.g.,
             may have been outside courthouse when called).
HAD-008.01        Provide USER with the ability to assign hearing information to a             0
                  associated PARTY .Capture check-in date and time, begin and end
                  date for hearing, bench time, when individual party called into hearing,
                  whether party actually appeared at the hearing.
HAD-008.02        Provide USER with the ability to assign a PERSON to a HEARING.               0
HAD-009      Record hearing outcomes for each allegation/offense/relief pertaining to
             each juvenile/defendant/participant or family including information on
             parties, cases, allegations/charges/relief, related cases, and cross petitions.

HAD-009.01       Provide ADMIN USER with the ability to define codes for SCHEDULED 0
                 EVENT OUTCOMES.
HAD-009.02       Provide ADMIN USER with the ability to define codes for Hearing types 0
                 SCHEDULED EVENT types (i.e. hearing, conference, trial).

     MDEC Procurement K11-0030-29                                                                                    September 1, 2010
                                                MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                    ATTACHMENT C
                                                  MARYLAND ELECTRONIC COURT PROCUREMENT                          Page 109 of 249
                                                         FUNCTIONAL REQUIREMENTS

                                                            HEARINGS, ADJUDICATION, DISPO

    ID                                     Requirement Text                                   Response Code   Comments
HAD-009.03       Provide ADMIN USER with the ability to define codes Allegations.         0
HAD-009.04       Provide ADMIN USER with the ability to define codes Offense.             0
HAD-009.05       Provide ADMIN USER with the ability to define codes Relief.              0
HAD-009.06       Provide ADMIN USER with the ability to relate                            0
                 Allegation/Offense/Relief codes to SCHEDULED EVENT Outcome
                 codes.
HAD-009.07       Provide ADMIN USER with the ability to relate Hearing Codes              0
                 to SCHEDULED EVENT Outcome Codes.
HAD-009.08       Provide USER with the ability to assign many SCHEDULED EVENT             0
                 OUTCOMES to each allegation/offense/relief pertaining.
HAD-009.09       Provide USER with the ability to assign many PERSONS                     0
                 or family groups to each allegation/offense/relief pertaining.
HAD-009.10       Provide USER with the ability to assign many SCHEDULED EVENT             0
                 OUTCOMES to a HEARING.
HAD-010      Track hearing results, hearing duration and participants, and scheduled
             and actual occurrence of hearing in conjunction with Management and
             Statistical Reports Function.
HAD-010.01       AUTOMATICALLY use information captured in court proceedings to           0
                 input to the Management and Statistical Reports Function ( hearing
                 results, hearing duration, parties, scheduled and actual occurrence of
                 hearing).
HAD-010.02       Provide ADMIN USER the ability to define codes for Scheduled Event       0
                 Results.
HAD-010.03       Provide USER with the ability to assign Result Code to Scheduled         0
                 Hearing ( continuances and cancellations ).
HAD-010.04       AUTOMATICALLY maintain full history of SCHEDULED EVENTS with             0
                 related results, scheduled event outcomes and referral services
                 outcomes.




     MDEC Procurement K11-0030-29                                                                               September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                    ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                          Page 110 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                             HEARINGS, ADJUDICATION, DISPO

    ID                                     Requirement Text                                    Response Code   Comments
HAD-011      Use information captured in court proceedings to update records on cases,
             juveniles/defendants/participants and other persons,
             allegations/charges/relief, and pleadings throughout system (e.g.,
             information on judgments, attorney withdrawals, adjournments,
             continuances, and cancellations working with Docketing and Related
             Record keeping (for docket updates), Scheduling (for rescheduling of
             hearing), Document Generation and Processing (for notice creation),
             Calendaring (to place on future calendar when scheduled), accounting (for
             monetary judgment data), and other functions; bifurcations (i.e., severed
             cases) working with Case Initiation and Indexing (to initiate new case) and
             Docketing and Related Record keeping (for docket updates) functions; and
             rulings taken under advisement on submitted matters). (see Integration
             Between Functions in Multi-Function Capabilities and Integration)

HAD-011.01       AUTOMATICALLY use information captured in court proceedings to            0
                 input to the Case Initiation and Indexing function (initiate new Case)
                 when there are bifurcations (severed or split cases).
HAD-011.02       AUTOMATICALLY use information captured in court proceedings to            0
                 update related Party information.
HAD-011.03       AUTOMATICALLY use information captured in court proceedings to            0
                 update records on allegations, charges and relief.
HAD-011.04       AUTOMATICALLY use information captured in court proceedings to            0
                 input to Scheduling function ( rescheduling of hearing).
HAD-011.05       AUTOMATICALLY use information captured in court proceedings to            0
                 input to Document Generation and Processing function (notice
                 creation).
HAD-011.06       AUTOMATICALLY use information captured in court proceedings to            0
                 input to the Calendaring function (scheduling future calendar),
HAD-011.07        AUTOMATICALLY use information captured in court proceedings to           0
                 input to Accounting function (monetary judgment data).
HAD-011.08       AUTOMATICALLY use information captured in court proceedings to            0
                 update records other information on CASES.
HAD-011.09       AUTOMATICALLY use information captured in court proceedings to            0
                 input to Docketing and Related Record Keeping function ( information
                 on judgments, attorney withdrawals, adjournments.



     MDEC Procurement K11-0030-29                                                                                September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                    ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                          Page 111 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                            DISPOSITION

     ID                                    Requirement Text                                     Response Code   Comments
DIS-001      Record disposition type (i.e., type of judgment) including those involving
             entire cases, each charge, individual parties, parcels in real property rights
             cases, and cross complaints.
DIS-001.01          Provide USER with the ability to assign DISPOSITION to a CASE.          0
DIS-001.02          Provide USER with the ability to assign DISPOSITION to a CHARGE. 0

DIS-001.03         Provide USER with the ability to assign DISPOSITION to a PARTY           0
DIS-001.04         Provide USER with the ability to assign DISPOSITION to                   0
                   ISSUE/RELIEF.
DIS-001.05         Provide USER with the ability to assign DISPOSITION to Other             0
DIS-001.06         Provide ADMIN USER with the ability to define DISPOSITION for a          0
                   CASE.
DIS-001.07         Provide ADMIN USER with the ability to define DISPOSITION for a          0
                   PARTY.
DIS-001.08         Provide ADMIN USER with the ability to define DISPOSITION for a          0
                   CHARGE.
DIS-001.09         Provide ADMIN USER with the ability to define DISPOSITION for            0
                   ISSUES/RELIEF
DIS-001.10         Provide ADMIN USER with the ability to define DISPOSITION for            0
                   Other.
DIS-002      Provide ―hierarchical‖ dispositions; for cases where ―lead‖ charge is guilty
             and subsequent charges are nolle pros, ensure case disposition is guilty.

DIS-002.01         Provide ADMIN USER with the ability to define a rule to designate a      0
                   lead CHARGE or lead ISSUE/RELIEF.
DIS-002.02         Provide ADMIN USER with the ability to define a rule to assign           0
                   ranking/severity to CHARGE and ISSUE/RELIEF.
DIS-002.03         Provide USER with the ability to assign a rank/severity to a             0
                   CHARGE and ISSUE/RELIEF.
DIS-002.04         Provide USER with the ability to override the default rank/severity to   0
                   a CHARGE and ISSUE/RELIEF.
DIS-002.05         Provide ADMIN USER with the ability to define rank/severity to a         0
                   DISPOSITION.
DIS-002.06         Provide ADMIN USER with the ability to choose how the overall            0
                   CASE disposition is calculated.



     MDEC Procurement K11-0030-29                                                                                 September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                       ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 112 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                             DISPOSITION

     ID                                     Requirement Text                                       Response Code   Comments
DIS-003      Allow for individual disposition of charges (e.g., some charges are
             disposed, and some are sub curia) and allow the case to be held open or
             suspended.

DIS-003.01          Provide ADMIN USER with the ability to define a rule to determine          0
                    Case Reporting Status (See Global Processing Model).
DIS-003.02          Provide ADMIN USER with the ability to define the Case Reporting           0
                    Status (See Global Processing Model).
DIS-003.03          Provide USER with the ability to override the default Case Reporting       0
                    Status.
DIS-004      Identify inactive cases and groups of cases (e.g., no activity for 6 months
             or other USER-definable period) and prompt USER regarding appropriate
             action (e.g., schedule hearing, prepare notice of motion to dismiss, extend
             dates).
DIS-004.01          Provide ADMIN USER with the ability to define fields for querying the      0
                    CASE records (e.g. for inactive cases)
DIS-004.02          Provide ADMIN USER with the ability to define fields that are              0
                    displayed in CASE search results.
DIS-004.03          Provide ADMIN USER with the ability to define a rule to perform            0
                    actions on selected CASEs meeting a certain criteria.
DIS-004.04          Provide USER with the ability to select one or many CASEs invoke           0
                    rule.
DIS-005      Process information (e.g., update docket and other records, if not updated
             AUTOMATICALLY as noted below, through Docketing and Related
             Recordkeeping Function) and produce documents (e.g., judgment form;
             see also Hearings Function) for dispositions (i.e., judgments, civil JTPs,
             remands) by trial, ADR such as mediation or arbitration, default, dismissal,
             withdrawal, settlement, transfer out to another jurisdiction, or consolidation.

DIS-005.01         Provide ADMIN USER with the ability to define workflow based on             0
                   different dispositions.




     MDEC Procurement K11-0030-29                                                                                    September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                    ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                          Page 113 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                                           DISPOSITION

     ID                                    Requirement Text                                    Response Code   Comments
DIS-006      Process information and produce documents (e.g., writ of execution,
             abstract of judgment) on post-judgment activities (e.g., in response to
             requests for execution with information on monetary and nonmonetary
             judgments including parties, damages, nonmonetary awards, pertinent
             dates, assignees, payments, and credits, enter and update records when
             judgments vacated or amended, allow all judgment elements(interest,
             attorney fees, etc.) to be individually modified).
DIS-006.01          Provide ADMIN USER with the ability to define workflow based on        0
                    "post-judgment" (e.g. activities occurring after a judgment is
                    ordered) activities.
DIS-007      Distribute disposition and post-judgment documents noted above
             electronically external to court and internally to be entered in docket. (see
             also Multifunction Capabilities and Integration and Docketing and Related
             Recordkeeping Function)
DIS-007.01          AUTOMATICALLY assign DOCUMENTS [disposition and post                   0
                    judgment] to the docket.
DIS-007.02          AUTOMATICALLY export disposition and post judgment documents. 0

DIS-008      Create, print, and maintain separate judgment indexes (i.e., judgment
             book) that show original and subsequent judgments (e.g., containing dates,
             amounts, modifications, satisfactions, judge) by case and party. (see also
             Case Initiation and Indexing Function and Execution Function)
DIS-008.01         Provide ADMIN USER with the ability to define REPORTS for               0
                   JUDGMENTS.
DIS-009      Update each case in group of disposed (e.g., dismissed) cases as if group
             was a single case. (see also Docketing and Related Recordkeeping
             Function)
DIS-009.01         Provide ADMIN USER with the ability to define fields for querying the   0
                   CASE records (e.g. for inactive cases).
DIS-009.02         Provide ADMIN USER with the ability to define fields that are           0
                   displayed in CASE search results.
DIS-009.03         Provide ADMIN USER with the ability to define a rule to perform         0
                   actions on selected CASEs meeting a certain criteria.
DIS-009.04         Provide USER with the ability to select one or many CASEs to            0
                   invoke a rule.
DIS-010      Record plea, disposition, sentence for entire case and each count of each
             charge/requested relief

     MDEC Procurement K11-0030-29                                                                                September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                       ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 114 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                             DISPOSITION

     ID                                   Requirement Text                                         Response Code   Comments
DIS-010.01           Provide USER with the ability to assign DISPOSITION to                    0
                     ISSUE,RELIEF,CHARGES.
DIS-010.02           Provide USER with the ability to assign SENTENCE or VERDICT to            0
                     CHARGES or RELIEF.
DIS-010.03           Provide ADMIN USER with the ability to define codes for PLEA.             0
DIS-010.04           Provide USER with the ability to assign PLEA to CHARGE.                   0
DIS-010.05           Provide ADMIN USER with the ability to define a rule for determining      0
                     overall.
DIS-011      Prompt to dispose all of charges/relief on a single case.
DIS-011.01           Provide ADMIN USER with the ability define rule for when                  0
                     CHARGES, RELIEF, ISSUE should be disposed.
DIS-011.02           AUTOMATICALLY prompt USER to invoke rule when CHARGES,                    0
                     RELIEF, ISSUE should be disposed.
DIS-013      Maintain and produce disposition and sentence information that show, for
             each case and defendant/participant, original and subsequent
             charges/relief and dispositions and sentences for each charge/relief.
DIS-013.01           Provide USER with the ability to assign DISPOSITION to                    0
                     ISSUE,RELIEF,CHARGES.
DIS-013.02           Provide USER with the ability to assign SENTENCE to CHARGES.              0
DIS-013.03           AUTOMATICALLY maintain history of DISPOSITION for                         0
                     ISSUE,RELIEF,CHARGES.
DIS-014      If the offense is committed by a person with a professional license (e.g.,
             CDL, Medical, law, etc.) and if the case result is guilty, then the case result
             must be sent to the licensing agency.
DIS-014.01           Provide ADMIN USER with the ability to define an indicator to             0
                     PARTY when party is the holder of a professional license.
DIS-014.02           Provide USER with the ability to assign an indicator to PARTY when        0
                     a certain CASE/DISPOSITION is entered.
DIS-014.03           Interface CASE to Licensing Agency.                                       0
DIS-015      If the offense is committed in a Commercial Motor Vehicle by a non
             Commercial Driver's License holder, then the case result must be sent to
             the Motor Vehicle Administration
DIS-015.01           Provide USER with the ability to assign an indicator to a PARTY           0
                     when the party holds a Commercial Driver's License.
DIS-015.02           Provide USER with the ability to assign an indicator to a CHARGE          0
                     when the charge is associated with a Commercial Motor Vehicle.


     MDEC Procurement K11-0030-29                                                                                    September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                     ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                           Page 115 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                                           DISPOSITION

     ID                                 Requirement Text                                        Response Code   Comments
DIS-015.03         Provide ADMIN USER with the ability to define an indicator for a         0
                   CASE when charge is offense is committed in a Commercial Motor
                   Vehicle.
DIS-015.04         Provide ADMIN USER with the ability to define an indicator for a         0
                   PARTY when the party is the holder of a Commercial Driver's
                   License.
DIS-015.05         Interface to CASE to MVA.                                                0
DIS-016      If the offense is CDL or CMV related and the case result is guilty then the
             case result must be sent to the DMV within the federally mandated time
             period (e.g., as of September 30, 2005 the time period is 30 days for out of
             state convictions and 10 days for in state convictions. As of September 30,
             2008 all convictions must be sent to DMV within 10 days).
DIS-016.01         Provide USER with the ability to assign an indicator to a PARTY          0
                   when the party holds a Commercial Driver's License.
DIS-016.02         Provide USER with the ability to assign an indicator to a CHARGE         0
                   when the charge is associated with a Commercial Motor Vehicle.
DIS-016.03         Provide ADMIN USER with the ability to define an indicator for a         0
                   CASE when charge is offense is committed in a Commercial Motor
                   Vehicle.
DIS-016.04         Provide ADMIN USER with the ability to define an indicator for a         0
                   PARTY when the party is the holder of a Commercial Driver's
                   License.
DIS-016.05         Interface to CASE to MVA.                                                0

DIS-017      System should enable USER to amend charges with authority.
DIS-017.01        Provide USER with the ability to assign CHARGES.                          0
DIS-017.02         AUTOMATICALLY maintain history of CHARGES.                               0
DIS-018      System should enable add warrants on other parties even if the case is in
             warrant status.
DIS-018.01         Provide USER with the ability to assign WARRANTS to CASES.               0
DIS-018.02         Provide ADMIN USER with the ability to define rule which allows          0
                   multiple warrants to be issued on a CASE.
DIS-018.03         Provide ADMIN USER with the ability to define an indicator to CASE       0
                   when a warrant is issued.
DIS-018.04         AUTOMATICALLY assign indicator to CASE when warrant is issued.           0


     MDEC Procurement K11-0030-29                                                                                 September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                   ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                         Page 116 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                                          DISPOSITION

     ID                                   Requirement Text                                    Response Code   Comments
DIS-019      Document the representation(attorneys present) for each event in a case
             (At each milestone).
DIS-019.01         Provide USER with the ability to assign ATTORNEYS present to           0
                   each SCHEDULED EVENT .
DIS-020      Provide ability to send dispositions to NCIC/CJIS.
DIS-020.01         Interface DISPOSITIONS to Public Safety.                               0

DIS-021      Provide ability to send Sexual Offender Registration information to
             appropriate agencies.
DIS-021.01         Provide USER with the ability to assign sexual offender registration   0
                   information to PARTY.
DIS-021.02         Interface PARTY, CASE to Public Safety.                                0




     MDEC Procurement K11-0030-29                                                                               September 1, 2010
                                                MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                        ATTACHMENT C
                                                  MARYLAND ELECTRONIC COURT PROCUREMENT                              Page 117 of 249
                                                         FUNCTIONAL REQUIREMENTS

                                                                           EXECUTION

      ID                                  Requirement Text                                         Response Code   Comments
EXE-001       Process requests for execution of judgments accommodating multiple
              judgments on the same case and allow for the selection of the correct
              judgment, and establish cross references for each execution to judgment
              index and judgment screen.
EXE-001.01        Provide USER with the ability to assign execution of JUDGMENT                0
                  information to one or more JUDGMENTS

EXE-001.02         Provide USER with the ability to select with ease multiple                  0
                   JUDGMENTS in order to assign execution of JUDGMENT
EXE-001.03         Provide USER with the ability to view execution of JUDGMENTS and            0
                   their related JUDGMENTS
EXE-002       Use information from criminal case to generate (and populate data for) a
              case in civil, and cross-reference civil case to criminal case.
EXE-002.01         Provide USER with the ability to assign a relationship between an           0
                   existing criminal CASE to a civil CASE
EXE-002.02         Provide USER with the ability to populate (copy and paste) data with        0
                   ease from a related criminal CASE
EXE-003       Process objections to execution.
EXE-003.01         Provide USER with the ability to assign objections to an execution          0
EXE-004       Record fully, partially, and nonsatisfied executions (e.g., all obligations
              satisfied). (see also Case Close Function)
EXE-004.01         Provide USER with the ability to assign execution status ( full, partial,   0
                   not satisfied)
EXE-004.02         Provide ADMIN USER with the ability to define codes for execution           0
                   status
EXE-005       Update each case in group of cases for which execution requested as if
              group was a single case (e.g., same judgment terms and execution
              requirements for each case in group).
EXE-005.01         Provide USER with the ability to select one or many CASES where             0
                   execution has been requested
EXE-005.02         Provide ADMIN USER with the ability to define field(s) for querying         0
                   CASES where execution has been requested and judgment terms and
                   execution requirements are the same
EXE-005.03         Provide ADMIN USER with the ability to define fields that are displayed     0
                   in the CASES with execution results
EXE-005.04         Provide USER the ability to update execution status in batch based on       0
                   selected CASES

     MDEC Procurement K11-0030-29                                                                                   September 1, 2010
                                               MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS     ATTACHMENT C
                                                 MARYLAND ELECTRONIC COURT PROCUREMENT           Page 118 of 249
                                                        FUNCTIONAL REQUIREMENTS

                                                                         EXECUTION
EXE-006       Ability to allow for multiple judgment debtors on the same writ.
EXE-006.01         Provide USER with the ability to assign multiple judgment debtors to a   0
                   writ
EXE-007       Ability to prevent execution activities within a pre-determined time frame,
              and according to pre-defined business rules , allowing for overrides (e.g.
              10 day waiting period).
EXE-007.01         Provide ADMIN USER with the ability to define rules establishing a       0
                   time frame or waiting period before execution activities can be
                   assigned
EXE-007.02         AUTOMATICALLY check a defined rules when USER assigns                    0
                   execution activities to a CASE
EXE-007.03         Provide USER with the ability to override rules when assigning           0
                   execution
EXE-008       Allow for the review of other related judgments from related cases.
EXE-008.01        Provide USER with the ability to view all JUDGMENTS on related            0
                  CASES
EXE-008.02        Provide ADMIN USER with the ability to define fields for querying         0
                  JUDGMENTS on related CASES
EXE-008.03        Provide ADMIN USER with the ability to define field(s) displayed in       0
                  JUDGMENTS on related CASES results




     MDEC Procurement K11-0030-29                                                               September 1, 2010
                                                   MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                          ATTACHMENT C
                                                     MARYLAND ELECTRONIC COURT PROCUREMENT                                Page 119 of 249
                                                            FUNCTIONAL REQUIREMENTS

                                                                               CASE CLOSE

      ID                                    Requirement Text                                            Response Code   Comments
CCL-001       Receive information from Disposition Function and record reason for
              closure (e.g., case disposed after trial, ADR such as mediation or
              arbitration, default, dismissal, withdrawal, settlement, transfer out to
              another jurisdiction, or consolidation), including alert or flag to notify if case
              has been closed (to avoid full review of case history to determine status).
CCL-001.01         Provide ADMIN USER with the ability to define codes for Case Closure             0
                   Reasons.
CCL-001.02         Provide ADMIN USER with the ability to define rule to alert user when            0
                   accessing a closed case.
CCL-001.03         Provide USER with the ability to assign indicator to CASE to identify cases      0
                   that are closed but have pending actions.
CCL-001.04         Provide ADMIN USER with the ability to define rule for determining whether a     0
                   case can be closed.
CCL-002       Establish cross references between consolidated cases for docketing, scheduling,
              notice generation, and other functions.

CCL-002.01        Provide ADMIN USER with the ability to define codes for CASE GROUP       0
                  TYPES.
CCL-002.02        Provide USER with the ability to assign one or more CASES to one or more 0
                  CASE GROUP TYPES [consolidated group type].
CCL-002.03        Provide ADMIN USER with the ability to define a rule for how replicating 0
                  functions (docketing, scheduling, noticing) based on a CASE GROUP TYPES.

CCL-003       Close case (e.g., update docket; generate required forms, notices, reports for that
              case) based upon defined business rules, including the ability to close cases in
              batches
CCL-003.1         Provide ADMIN USER with the ability to define workflow for closing cases.         0
CCL-004       Allow ability to file and docket documents (motions, reports, etc.) to the case
              without re-opening the case.
CCL-004.01         Provide ADMIN USER with the ability to define a rule for allowing update in      0
                   CASES that have been deemed closed.
CCL-005       Generate overall case closure reports (e.g., cases closed over specific
              period with reason closed and other information such as uncollectable
              obligation balance). (see also Management and Statistical Reports
              Function)
CCL-005.01        Provide admin user with the ability to define reports for CASES based on          0
                  case closure.



      MDEC Procurement K11-0030-29                                                                                       September 1, 2010
                                                   MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                          ATTACHMENT C
                                                     MARYLAND ELECTRONIC COURT PROCUREMENT                                Page 120 of 249
                                                            FUNCTIONAL REQUIREMENTS

                                                                               CASE CLOSE

      ID                                   Requirement Text                                             Response Code   Comments
CCL-006       Receive information on defendants and/or case participants who have
              completed installment payments, probation or any programs administered
              by probation, detention or any programs administered by corrections, or
              other programs that would result in case closure under local and state
              rules.
CCL-006.01        INTERFACE Probation Agency/Other agencies to CASE.                                0
CCL-007       Identify activities and conditions that can prevent case from being closed
              and alerts when case close is accepted when those conditions are not
              satisfied (e.g. outstanding or open charge, un-sentenced guilty charge,
              outstanding motions, unpaid fines, etc). A case may be closed when fees
              are still outstanding.
CCL-007.01          Provide ADMIN USER with the ability to define a rule for allowing or            0
                    disallowing a CASE closure.
CCL-008       Provide a facility for re-opening previously closed cases, tracking date and reason
              for reopening, with proper authorization.
CCL-008.01          Provide USER with the ability to assign a Case Reporting Status [Reopen] to     0
                    CASE
CCL-008.02          Provide ADMIN USER with the ability to define codes for Case Reporting          0
                    Statuses.
CCL-008.03          Provide USER with the ability to assign reopen date, reopen reason and          0
                    previous status to Case Reporting Status.
CCL-008.04          Automatically maintain history of Case Reporting Statuses.                      0
CCL-009       Record ultimate resolution for each closed case including request relief,
              allegations; information on juveniles, families, and related cases and petitions; and
              cross-reference to judge‘s order for closure.
CCL-009.01         Provide USER with the ability to assign RELIEF, ALLEGATIONS to CASE.             0
CCL-009.02        Provide USER with the ability to assign PETITIONS to CASES.                       0
CCL-009.03        Provide USER with the ability to assign one to many PARTYs to one to many         0
                  PARTYs in order to form a family relationship.

CCL-009.04        Provide USER with the ability to assign many CASES to many CASES in      0
                  order to create CASE GROUP[related].
CCL-009.05        Provide USER with the ability to assign DOCUMENT [order] to DISPOSITION. 0

CCL-009.06        Provide USER with the ability to assign DOCUMENT to PARTY.                        0
CCL-009.07        Provide ADMIN USER with the ability to define codes to associate                  0
                  DOCUMENTS to DOCUMENTS.

      MDEC Procurement K11-0030-29                                                                                       September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                           ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                                 Page 121 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                              CASE CLOSE

      ID                                     Requirement Text                                           Response Code   Comments
CCL-009.08        Provide USER with the ability to assign DOCUMENT [order] to                       0
                  DOCUMENT[order].

CCL-010       Prompt USER to dispose of open charges relief on a single case before case can
              be closed.
CCL-010.01         Automatically prompt user to close case when CHARGES/RELIEF/ISSUES               0
                   are disposed.

CCL-011       Prompt USER to close case when all locally defined business rule conditions are
              met.
CCL-011.01         Provide ADMIN USER with the ability to define rule for determining whether a     0
                   case can be closed.

CCL-012       Allow USER to manually close case (e.g., change status to closed; update docket;
              generate required forms, notices, reports for that case) according to locally-
              defined business rules.

CCL-012.01        Provide USER with the ability to assign a Case Reporting Status [Closed,          0
                  Reopen].
CCL-012.02         Provide ADMIN USER with the ability to define rule for determining the Case      0
                   Reporting Status.
CCL-013       Alert USER when case accounts are paid in full.
CCL-013.01        Automatically alert user when case accounts are paid in full.                     0
CCL-014       Allow each charge/relief in a case to be tracked separately and allow for multiple
              dates and notices to be sent, including setting a court date for a specific charge or
              part of a case.
CCL-014.01         Provide USER with the ability to search CHARGE/ISSUES/RELIEF on CASE. 0

CCL-014.02         Provide USER with the ability to select one to many                              0
                   CHARGE/ISSUES/RELIEF on CASE.
CCL-014.03         Provide ADMIN USER with the ability to define fields that are displayed in the   0
                   CHARGE/ISSUES/RELIEF search results.
CCL-014.04         Provide ADMIN USER with the ability to define fields for querying                0
                   CHARGE/ISSUES/RELIEF records.
CCL-014.05         Provide USER with the ability to assign one to many SCHEDULED EVENTS             0
                   to one to many CHARGE/ISSUES/RELIEF.
CCL-014.06         Provide ADMIN USER with the ability to define a rule to perform actions on       0
                   selected CHARGE/ISSUES/RELIEF meeting a certain criteria.
CCL-015       Alert users when closing cases if there is a hearing date that needs to be vacated.


      MDEC Procurement K11-0030-29                                                                                       September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                    ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                          Page 122 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                                             CASE CLOSE

      ID                                    Requirement Text                                    Response Code   Comments
CCL-015.01        Provide ADMIN USER with the ability to define rule for disallowing case   0
                  closing if a SCHEDULED EVENT is still outstanding.
CCL-015.02        Provide ADMIN USER to define a rule to warn user of action that must be   0
                  taken in order to close a case.
CCL-015.03        Automatically alert user when CASE has an open SCHEDULED EVENT.           0




      MDEC Procurement K11-0030-29                                                                               September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                        ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                              Page 123 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                            ACCOUNTING

    ID                                        Requirement Text                                       Response Code   Comments
ACC-001      Allow authorized USER to adjust or correct any data supplied
             AUTOMATICALLY by system prior to posting (e.g., default entries, funds
             distribution according to predetermined formula) and provide audit trail of these
             transactions.
ACC-001.01        Provide USER with the ability to override pre-configured data (e.g.. Default   0
                  entries, funds distribution according to predetermined formula).
ACC-001.02        AUTOMATICALLY assign Audit Trail to transactions posted.                       0
ACC-002      Prevent (with supervisory override) financial transactions to be dated and
             posted to a closed accounting period.
ACC-002.01        Provide ADMIN USER with the ability to define rule to prevent financial        0
                  transactions from being dated and posted to a closed accounting period.
ACC-002.02        Provide USER with the ability to override a financial transaction from being   0
                  dated and posted to a closed accounting period.
ACC-003      Comply with generally accepted accounting principles (GAAPs) for
             governmental entities.

ACC-003.01        Provide ADMIN USER to define Judiciary accounting principles GAAPs             0
ACC-003.02        AUTOMATICALLY comply with Generally Accepted Accounting Principles             0
                  (GAAP) for Governmental Entities.
ACC-004      Provide appropriate security and authorization for all accounting functions. (see
             also Security Function)
ACC-004.01        Provide ADMIN USER with the ability to define security for all accounting      0
                  functions.
ACC-005      Generate accounting notices (e.g., for payment) at front counter or in back
             office. (see also Document Generation and Processing Function)
ACC-005.01        Provide ADMIN USER with the ability to define where document for               0
                  [PAYMENTS, NOTICES etc] will be generated (e.g.. Front counter or back
                  office).
ACC-005.02        Provide USER with the ability to produce document for [PAYMENT,                0
                  NOTICES etc.] from different places (e.g.. Front counter or Back office).
ACC-006      Transfer funds and allocations from one case to another case, between
             accounts in a given case (e.g., to rectify error if jury fees posted in court
             reporter fund), or between jurisdictions.
ACC-006.01        Provide USER with the ability to assign adjustments (e.g.. Transfer funds      0
                  and allocations) from one case to another case.
ACC-006.02        Provide USER with the ability to assign adjustments (e.g.. Transfer funds      0
                  and allocations) from one account to another account in same case.

      MDEC Procurement K11-0030-29                                                                                    September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                         ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                               Page 124 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                            ACCOUNTING

    ID                                       Requirement Text                                         Response Code   Comments
ACC-006.03       Provide USER with the ability to assign adjustments (e.g.. Transfer funds        0
                 and allocations) from one jurisdiction to another jurisdiction.
ACC-007      Support trust fund (i.e., moneys held in trust that may be disbursed upon court
             order or for services rendered) accounting (e.g., post trust funds transactions to
             case; track receipts, disbursements, account status; credit interest; process
             refunds and forfeitures). (see also Accounting - Front Counter and Cashiering
             Function and Accounting - Back Office Function)
ACC-007.01       Provide ADMIN USER with the ability to define TRUST FUNDS (i.e.,                 0
                 moneys held in trust that may be disbursed upon court order or for services
                 rendered) for a Case.
ACC-007.02       Provide ADMIN USER with the ability to define TRUST FUNDS (i.e.,                 0
                 moneys held in trust that may be disbursed upon court order or for services
                 rendered) for a Party.
ACC-007.03       Provide USER with the ability to assign TRUST FUND transactions to Case.         0

ACC-007.04       Provide USER with the ability to assign TRUST FUND transactions to Party. 0

ACC-007.05        Provide USER with the ability to assign BANK INTEREST to TRUST                  0
                  FUNDS..
ACC-007.06        Provide USER with the ability to produce document [RECEIPT,                     0
                  DISBURSEMENT] for TRUST FUND.
ACC-007.07        Provide USER with the ability to assign REFUND, FORFEITURES to                  0
                  TRUST FUND.
ACC-008      Establish interface between Accounting (particularly Receipting and
             Bookkeeping) and case Support (particularly Conditions for Release from
             Custody) functions to collect and generate receipts for bail monies, disburse
             funds (e.g., to defendant who posted bail, to court for court costs, to other
             participants, victim(s), or both for restitution), suspend disbursements, record
             bail forfeiture monies as revenue, disseminate bail register.
ACC-008.01        Interface between ACCOUNTING ( e.g.. Receipting, Bookkeeping) and               0
                  Case Activity (e.g.. Conditions for release from Custody) to process monies
                  (e.g.. Bail)..
ACC-008.02        Interface between ACCOUNTING ( e.g.. Receipting, Disbursement,                  0
                  Bookkeeping) and Case Information (e.g.. Case Party, Costs) to process
                  monies (e.g.. Assess Court Costs, Disburse to Defendant).



      MDEC Procurement K11-0030-29                                                                                     September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                       ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 125 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                           ACCOUNTING

    ID                                        Requirement Text                                      Response Code   Comments
ACC-009      Interfaces that allow for the collection and receipting of fines, fees, and bonds
             by non-court persons or companies, must prohibit the deletion or modification
             of financial or other case data within the security matrix.
ACC-009.01        Provide ADMIN USER with the ability to define rule to prohibit Interfaces for 0
                  accounting (e.g.. Collection of fines, fees and bonds) by external agencies
                  from deleting or modifying financial or Case data.
ACC-010      Provide the ability to integrate with accounting and cashiering.

ACC-010.01       Provide ADMIN USER with the ability to define rule to integrate Case           0
                 records with Accounting.
ACC-010.02       Provide ADMIN USER with the ability to define rule to integrate Case           0
                 records with cashiering.
ACC-011      Allow for citations to be paid just prior to court date, to prevent manual
             reconciliation.
ACC-011.01       Priovide USER the ability to accept payment for citations prior to court date. 0

ACC-012      Allow for automatic reconciling of daily receipts and bank accounts, and still
             enable multiple USERs to access the system.
ACC-012.01       Provide USER with the ability to assign reconciliation to End-Of-Day(EOD)     0
                 functions (e.g., Daily Receipts, Bank Deposits).
ACC-012.02       AUTOMATICALLY provide USERs access to system while Accounting                 0
                 Reconciliation is in process.
ACC-013      Support late payments with late charges.

ACC-013.01      Provide ADMIN USER with the ability to define rule for late payments.          0
ACC-013.02      Provide USER with the ability to assign late charges for late payments.        0
ACC-014      Enable the monitoring of the compliance with deferred payment plans.

ACC-014.01       Provide USER with the ability to produce report for deferred payment plans. 0

ACC-015      Allow for the acceptance of penalty deposits according to locally-defined
             business rules.
ACC-015.01       Priovide USER the ability to accept penatly deposits according to locally-    0
                 defined rules.




      MDEC Procurement K11-0030-29                                                                                   September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                        ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                              Page 126 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                            ACCOUNTING

    ID                                        Requirement Text                                       Response Code   Comments
ACC-016      Maintain and track various types of individual (e.g., case or party) and
             combined (e.g., funds held short term by clerk) bank accounts (e.g., interest
             bearing, noninterest bearing, installment, pay-through) and balances by case,
             due date, and party (a few accounts, such as attorney accounts and funds held
             short term by clerk, are case processing; most accounts, such as trusts and
             most escrow accounts, are financial).
ACC-016.01        Provide ADMIN USER with the ability to define Bank Accounts (e.g..             0
                  interest bearing, non-interest bearing, installment, pay-through, and funds
                  held short term by clerk) for a Case.
ACC-016.02        Provide ADMIN USER with the ability to define Bank Accounts (e.g..             0
                  interest bearing, non-interest bearing, installment, pay-through, and funds
                  held short term by clerk) for a Party.
ACC-016.03        Provide USER with the ability to assign accounting transactions to Bank        0
                  accounts.
ACC-016.04        Provide USER with the ability to produce report for Bank Accounts (e.g..       0
                  interest bearing, non-interest bearing, installment, pay-through, and funds
                  held short term by clerk).
ACC-017      Track status of accounts referred to other agencies or organizations (e.g., state
             tax intercept to recover previously waived fees, Parole and Probation, CCU,
             sheriff) for collection and update the status when payments are made.
ACC-017.01        Provide USER with the ability to produce report for COLLECTION                 0
                  ACCOUNTS ( e.g.. state tax intercept to recover previously waived fees,
                  Parole and Probation, CCU, sheriff)
ACC-017.02        AUTOMATICALLY update status on COLLECTION ACCOUNTS when                        0
                  payments received.
ACC017.03         Provide USER with the ability to assign status to COLLECTION                   0
                  ACCOUNTS when payments received from other agencies or
                  organizations.
ACC-018      Produce correspondence such as payment notices and dunning letters. (see
             also Scheduling Function and Document Generation and Processing Function)

ACC018.01        Provide ADMIN USER with the ability to define workflow for document             0
                 generation [payment notice and dunning letters].
ACC-018.02       Provide USER with the ability to produce document [payment notices and          0
                 dunning letters].
ACC-018.03       AUTOMATICALLY produce document [payment notices and dunning                     0
                 letters]

      MDEC Procurement K11-0030-29                                                                                    September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                         ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                               Page 127 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                            ACCOUNTING

    ID                                       Requirement Text                                         Response Code   Comments
ACC-019      Share information with state and local agencies to coordinate collection of court-
             ordered payments (e.g., to recover previously waived fees).
ACC-019.01       Interface with State and Local Agencies for collection of court-ordered          0
                 payments.
ACC-020      Establish, maintain, and track various types of bank accounts (e.g., interest
             bearing, non-interest bearing, installment, pay-through, and funds held short
             term by clerk).
ACC-020.01       Provide ADMIN USER with the ability to define Bank Accounts (e.g..               0
                 interest bearing, non-interest bearing, installment, pay-through, and funds
                 held short term by clerk) for a Case.
ACC-020.02       Provide ADMIN USER with the ability to define Bank Accounts (e.g..               0
                 interest bearing, non-interest bearing, installment, pay-through, and funds
                 held short term by clerk) for a Party.
ACC-020.03       Provide USER with the ability to assign accounting transactions to Bank          0
                 accounts.
ACC-020.04       Provide USER with the ability to produce report for Bank Accounts (e.g..         0
                 interest bearing, non-interest bearing, installment, pay-through, and funds
                 held short term by clerk).
ACC-021      Post interest accruals to bank accounting records (e.g., interest accrued daily
             to overall account, such as for all trust accounts); associate accruals with
             proper bank account.
ACC-021.01       Provide USER with the ability to assign Interest Accruals to Bank Account        0
                 records.
ACC-022      Print system wide daily cash receipts journal.

ACC-022.01         Provide ADMIN USER with the ability to define report for Cash Receipts ( 0
                   e.g.. System wide or by Cash register).
ACC-022.02         Provide USER with the ability to produce report for Cash Receipts.            0
ACC-023      Display or print detailed and summary lists of financial transactions (e.g.,
             receipts, disbursements, interest accruals, voided transactions listed by type or
             chronologically) for specific accounts over specific periods (e.g., daily, monthly,
             for life of case). (see also General Accounting Function and Management and
             Statistical Reports Function)
ACC-023.01         Provide ADMIN USER with the ability to define report for Accounting           0
                   Transactions [RECEIPTS, DISBURSEMENTS, INTEREST ACCRUALS
                   etc].


      MDEC Procurement K11-0030-29                                                                                     September 1, 2010
                                                   MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                         ATTACHMENT C
                                                     MARYLAND ELECTRONIC COURT PROCUREMENT                               Page 128 of 249
                                                            FUNCTIONAL REQUIREMENTS

                                                                             ACCOUNTING

    ID                                    Requirement Text                                             Response Code   Comments
ACC-023.02       Provide USER with the ability to produce report for Accounting                    0
                 Transactions [RECEIPTS, DISBURSEMENTS, INTEREST ACCRUALS
                 etc].
ACC-024      Calculate and record bank deposits.

ACC-024.01        AUTOMATICALLY calculate BANK DEPOSIT.                                            0
ACC-024.02        AUTOMATICALLY assign BANK DEPOSIT                                                0
ACC-025      List bank deposits in various groupings (e.g., totals for cash, check, credit card)
             showing account in which funds to be deposited.
ACC-025.01        AUTOMATICALLY produce report for BANK DEPOSIT [ Cash, Check,                     0
                  Credit Card etc] details.
ACC-025.02        Provide USER with the ability to produce report for BANK DEPOSIT [               0
                  Cash, Check, Credit Card etc] details.
ACC-026      Print bank deposit slips for specific banks and periods.

ACC-026.01       AUTOMATICALLY produce document [BANK DEPOSIT].                                    0
ACC-026.02       Provide USER with the ability to produce document for [BANK DEPOSIT].             0

ACC-027      Compare court record of checks with bank record of checks for specific
             periods; produce list of discrepancies, outstanding checks, and current court
             and bank balances; reconcile bank accounts; produce report listing
             discrepancies for all reconciliations.
ACC-027.01       AUTOMATICALLY assign reconciliation between CHECK REGISTER and                    0
                 BANK ACCOUNT.
ACC-027.02       Provide USER with the ability to assign reconciliation between CHECK              0
                 REGISTER and BANK ACCOUNT.
ACC-027.03       Provide USER with the ability to produce report for BANK ACCOUNT                  0
                 reconciliation.
ACC-027.04       Provide USER with the ability to produce report for outstanding CHECKS.           0
ACC-027.05       Provide USER with the ability to produce report for CHECK REGISTER                0
                 and BANK ACCOUNT balances.
ACC-027.06       Provide USER with the ability to produce report for BANK ACCOUNT                  0
                 reconciliation discrepancies.
ACC-028      Produce list of items that remain open for accounts that carry balance forward
             from one period to next period.
ACC-028.01       Provide USER with the ability to produce report for OPEN ACCOUNTS.                0


      MDEC Procurement K11-0030-29                                                                                      September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                        ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                              Page 129 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                                          ACCOUNTING

    ID                                       Requirement Text                                       Response Code   Comments
ACC-029      Produce trial balance (e.g., at end of month before posting to general ledger)
             and balance reports for each account or specified accounts over specific period.

ACC-029.01        AUTOMATICALLY produce report for ACCOUNT TRIAL BALANCE.                       0
ACC-029.02        Provide USER with the ability to produce report for ACCOUNT balances.         0
ACC-029.03        Provide USER with the ability to produce report for ACCOUNT TRIAL             0
                  BALANCE.
ACC-030      Total and reconcile receipts over specific period for multiple cashiers to
             calculate bank deposits. (see also Accounting - Receipting Function)
ACC-030.01        AUTOMATICALLY total/reconcile RECEIPTS for one/many CASHIERS.                 0
ACC-030.02        Provide USER with the ability to assign total/reconcile RECEIPTS for          0
                  one/many CASHIERS.
ACC-031      Receive bank statements and reconcile bank accounts electronically. (see also
             Multifunction Capabilities and Integration)
ACC-031.01        INTERFACE with BANK for BANK ACCOUNT reconciliation.                          0
ACC-031.02        AUTOMATICALLY assign reconciliation between CHECK REGISTER and                0
                  BANK ACCOUNT.
ACC-032      Debit accounts established by authorized organizations to cover court
             expenses, and credit organizations‘ accounts based on electronic funds
             transfers from their bank accounts, debits from their credit card accounts, and
             on-line check writing. (see also Multifunction Capabilities and Integration)
ACC-032.01        AUTOMATICALLY update BOOKKEEPING for accounting transactions                  0
                  with External Agencies/Accounts for any Payment Type.
ACC-033      Identify instances when balances in draw-down accounts are low and accounts
             require additional funds.
ACC-033.01        Provide USER with the ability to produce report for DRAWDOWN                  0
                  ACCOUNTS that require additional funds.
ACC-033.02        AUTOMATICALLY identify DRAWDOWN ACCOUNTS that require                         0
                  additional funds.
ACC-034      Provide reports showing transactions on draw-down accounts over USER-
             specified period.
ACC-034.01        Provide USER with the ability to produce report for DRAWDOWN                  0
                  ACCOUNTS.
ACC-035      Allow USERs to specify that refunds will be credited to draw-down accounts.

ACC-035.01       Provide ADMIN USER with the ability to define an indicator to                  0
                 DRAWDOWN ACCOUNTS to credit refunds.
      MDEC Procurement K11-0030-29                                                                                   September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                       ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 130 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                           ACCOUNTING

    ID                                            Requirement Text                                  Response Code   Comments
ACC-036      Maintain financial parts of case files and docket (e.g., payments received,
             liabilities with linkage to accounts receivable in finance). (see also Docketing
             and Related Recordkeeping Function)
ACC-036.01         AUTOMATICALLY maintain history of ACCOUNTING transactions for                0
                   CASE RECORDS and DOCKET.
ACC-036.02         Provide USER with the ability to assign ACCOUNTING transactions for          0
                   CASE RECORDS and DOCKET and link to Financial Accounting
                   (Accounts RECEIVABLE).
ACC-036.03         Provide USER with the ability to produce report for ACCOUNTING               0
                   Transactions for CASE RECORDS and DOCKET.
ACC-037      Compute and display costs and fees based on occurrence of a specific event
             (e.g., initial filing, motion filing).
ACC-037.01         AUTOMATICALLY assign COSTS, FEES on the occurrence of CASE                   0
                   EVENTS.
ACC-037.02         Provide ADMIN USER with the ability to define rule to compute COSTS,         0
                   FEES on the occurrence of CASE EVENTS.
ACC-037.03         Provide USER with the ability to override COSTS, FEES on the occurrence      0
                   of CASE EVENTS.
ACC-038      Identify existence of fee waivers or deferrals, display message (e.g., indigent,
             governmental waiver), process appropriately (e.g., case filed but waiver
             deferred pending judicial review).
ACC-038.01         Provide ADMIN USER with the ability to define rule to process Fee            0
                   Waivers and Deferrals on CASE.
ACC-038.02         AUTOMATICALLY identify rule to process Fee Waivers and Deferrals on          0
                   CASE.
ACC-038.03         Provide USER with the ability to assign and invoke rule to process fee       0
                   waivers and deferrals on CASE.
ACC-038.04         Provide USER with the ability to override rule to process fee waivers and    0
                   deferrals on CASE.
ACC-039      Record funds received from other local, state, and private units for payment of
             specific case and party costs, fees, and judgments (e.g., for service of
             summons by law officer for another jurisdiction).
ACC-039.01         AUTOMATICALLY update Accounting/Bookkeeping records for RECEIPT              0
                   of Costs/Fines/Judgments from External Agencies.
ACC-040      Record changes to accounting records that result from court orders (e.g.,
             change in monthly support payment amount) and modify appropriate records.


      MDEC Procurement K11-0030-29                                                                                   September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                       ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 131 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                                          ACCOUNTING

    ID                                       Requirement Text                                      Response Code   Comments
ACC-040.01         AUTOMATICALLY update Accounting/Bookkeeping records from COURT              0
                   orders (e.g.. Change in monthly support payment).
ACC-040.02         Provide ADMIN USER with the ability to define workflow to update            0
                   Accounting/Bookkeeping records from COURT orders (e.g.. Change in
                   monthly support payment).
ACC-040.03         Provide USER with the ability to assign Accounting/Bookkeeping records      0
                   from COURT orders (e.g.. Change in monthly support payment)
ACC-041      Maintain standard tables for court costs and fees. (see also List of Code
             Translation Tables)
ACC-041.01         Provide ADMIN USER with the ability to define codes for Court Costs and     0
                   Fees.
ACC-041.02         Provide USER with the ability to choose codes for Court Costs and Fees.     0
ACC-042      Establish flexible, USER-defined and -maintained individual (e.g., for case,
             single party in case, multiple parties in case) case and party accounts when
             initial fees received for new case. (see also Accounting - Receipting Function)
ACC-042.01         Provide ADMIN USER with the ability to define rule to initiate CASE when    0
                   fees received for new CASE.
ACC-042.02         Provide ADMIN USER with the ability to define rule to initiate PARTY        0
                   Accounts when fees received for new CASE.
ACC-042.03         Provide USER with the ability to assign CASE when fees received for new     0
                   CASE.
ACC-042.04         Provide USER with the ability to assign PARTY when fees received for new    0
                   CASE.
ACC-043      Allow USER to specify multiple party accounts for each case account.

ACC-043.01       Provide USER with the ability to assign multiple PARTY Accounts for each 0
                 CASE.
ACC-044      Allow payment of costs, fees, and other charges assessed to specific party in a
             case by variety of methods (e.g., manual, electronic funds transfer, attorney
             draw-down account debit, and pay-through).
ACC-044.01       Provide ADMIN USER with the ability to define codes for Method of           0
                 PAYMENTS [credit cards,manual, electronic funds transfer, attorney draw-
                 down account debit, and pay-through] for Court Costs/Fees..
ACC-044.02       Provide USER with the ability to choose codes for Method of PAYMENTS        0
                 [manual, electronic funds transfer, attorney draw-down account debit, and
                 pay-through] for Court Costs/Fees.


      MDEC Procurement K11-0030-29                                                                                  September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                       ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 132 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                                          ACCOUNTING

    ID                                       Requirement Text                                      Response Code   Comments
ACC-045      Post case-related receipts to accounting records and docket or register of
             actions (support payment receipts are not usually entered in the docket);
             associate receipts with proper case, party, account, or case activity; interact
             with receipting to accomplish these tasks. (see also Docketing and Related
             Recordkeeping Function)
ACC-045.01        AUTOMATICALLY maintain history of ACCOUNTING                                 0
                  transactions[RECEIPTS] for CASE RECORDS and DOCKET.
ACC-045.02        AUTOMATICALLY assign RECEIPTS to CASE, PARTY, ACCOUNT or                     0
                  CASE EVENT.
ACC-046      Post case-related disbursements to accounting records and docket or register
             of actions (support payment disbursements are not usually entered in the
             docket); associate disbursements with proper case, party, account, or case
             activity. (see also Docketing and Related Recordkeeping Function)
ACC-046.01        AUTOMATICALLY maintain history of ACCOUNTING                                 0
                  transactions[DISBURSEMENTS] for CASE RECORDS and DOCKET.
ACC-046.02        AUTOMATICALLY assign DISBURSEMENT to CASE, PARTY, ACCOUNT                    0
                  or CASE EVENT.
ACC-047      Apply correcting entries without changing or deleting previously recorded
             transactions, record and store adjusting financial entries (e.g., bank
             adjustments for errors or bad checks), and modify amounts due with proper
             authorization.
ACC-047.01        AUTOMATICALLY assign adjustment transaction without changing original        0
                  transaction.
ACC-047.02        Provide USER with the ability to assign adjustment transaction without       0
                  changing original transaction.
ACC-047.03        Provide USER with the ability to assign adjustment transaction with proper   0
                  security.
ACC-048      Maintain and track various types of individual case or party accounts and
             balances by case, due date, and party (a few accounts, such as attorney draw-
             down accounts and funds held short term by clerk, are case processing; many
             installment and pay-through accounts are support payment; most other
             accounts, such as trusts and most escrow accounts, are financial).

ACC-048.01       Provide USER with the ability to produce report for CASE ACCOUNT,             0
                 PARTY ACCOUNT.
ACC-048.02       Provide USER with the ability to produce report for CASE balance, PARTY       0
                 balance or balance by Due Date.

      MDEC Procurement K11-0030-29                                                                                  September 1, 2010
                                                   MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                         ATTACHMENT C
                                                     MARYLAND ELECTRONIC COURT PROCUREMENT                               Page 133 of 249
                                                            FUNCTIONAL REQUIREMENTS

                                                                              ACCOUNTING

    ID                                         Requirement Text                                        Response Code   Comments
ACC-049      Display or print detailed and summary lists of financial transactions (e.g.,
             receipts, disbursements, court cost assessments, fee assessments, monetary
             judgments, voided transactions, indigent fee cost waivers listed by type or
             chronologically) for specific cases and parties over specific periods (e.g., daily,
             monthly, for life of case). (see also Management and Statistical Reports
             Function)
ACC-049.01        Provide ADMIN USER with the ability to define report for Financial               0
                  Transactions [RECEIPTS, DISBURSEMENTS, COSTS, FEES etc] for a
                  CASE for specific periods in time.
ACC-049.02        Provide ADMIN USER with the ability to define report for Financial               0
                  Transactions [RECEIPTS, DISBURSEMENTS, COSTS, FEES etc] for a
                  PARTY for specific periods in time.
ACC-049.03        Provide USER with the ability to produce report for Financial Transactions       0
                  [RECEIPTS, DISBURSEMENTS, COSTS, FEES etc] for a CASE for
                  specific periods in time.
ACC-049.04        Provide USER with the ability to produce report for Financial Transactions       0
                  [RECEIPTS, DISBURSEMENTS, COSTS, FEES etc] for a PARTY for
                  specific periods in time.
ACC-050      Accrue charges to case based on occurrence of specific events (e.g., motion
             filed); periodically apply debits and costs to accounts (e.g., attorney and media
             accounts) and produce account statements.
ACC-050.01        AUTOMATICALLY assign COSTS, FEES on the occurrence of CASE                       0
                  EVENTS.
ACC-050.02        Provide ADMIN USER with the ability to define rule to assess COSTS and           0
                  PAYMENTS to ACCOUNTS periodically (e.g.. ATTORNEY and Media
                  Accounts).
ACC-050.03        Provide USER with the ability to invoke rule to assess COSTS and                 0
                  PAYMENTS to ACCOUNTS periodically (e.g.. ATTORNEY and Media
                  Account).
ACC-050.04        Provide USER with the ability to produce report for ACCOUNT [CASE,               0
                  PARTY].
ACC-051      Generate and print invoices for and document collection of all moneys (e.g.,
             fees for re-service of process).
ACC-051.01        Provide USER with the ability to produce Document for INVOICE [CASE,             0
                  PARTY].
ACC-051.02        Provide USER with the ability to produce Document for RECEIPT [CASE,             0
                  PARTY].

      MDEC Procurement K11-0030-29                                                                                      September 1, 2010
                                                   MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                        ATTACHMENT C
                                                     MARYLAND ELECTRONIC COURT PROCUREMENT                              Page 134 of 249
                                                            FUNCTIONAL REQUIREMENTS

                                                                            ACCOUNTING

    ID                                     Requirement Text                                           Response Code   Comments
ACC-052      Mark case or party account closed or some other designator.

ACC-052.01        Provide ADMIN USER with the ability to define indicator to close CASE or        0
                  PARTY ACCOUNT.
ACC-052.02        Provide USER with the ability to assign indicator to close CASE or PARTY        0
                  ACCOUNT.
ACC-053      Provide capability to adjust receivables when directed by court order (e.g., write
             off uncollected debt when obligor dies).
ACC-053.01        Provide USER with the ability to assign adjustments to RECEIVABLES by           0
                  Court Order ( e.g.. write off uncollected debt).
ACC-054      Produce periodic (e.g., daily, monthly) report or display showing financial
             status, Title IV-D status, and history (e.g., information on transactions, account
             balances, discrepancies, adjustments) for each specified case or party
             account. (see also Management and Statistical Reports Function)
ACC-054.01        Provide ADMIN USER with the ability to define report for                        0
                  Financial/Accounting Transactions [RECEIPTS, DISBURSEMENTS,
                  COSTS, FEES etc] for a CASE for specific periods in time.
ACC-054.02        Provide ADMIN USER with the ability to define report for                        0
                  Financial/Accounting Transactions [RECEIPTS, DISBURSEMENTS,
                  COSTS, FEES etc] for a PARTY for specific periods in time.
ACC-054.03        Provide USER with the ability to produce report for Financial/Accounting        0
                  Transactions [RECEIPTS, DISBURSEMENTS, COSTS, FEES etc] for a
                  CASE for specific periods in time.
ACC-054.04        Provide USER with the ability to produce report for Financial/Accounting        0
                  Transactions [RECEIPTS, DISBURSEMENTS, COSTS, FEES etc] for a
                  PARTY for specific periods in time.
ACC-055      Generate other periodic financial reports based on various criteria including at
             least account aging, audit trail, and journal reports. (see also General
             Accounting Function and Management and Statistical Reports Function)
ACC-055.01        Provide ADMIN USER with the ability to define reports for Finance (e.g..        0
                  Aging, Audit Trail, Journal).
ACC-055.02        Provide USER with the ability to produce report for Finance (e.g.. Aging,       0
                  Audit Trail, Journal).
ACC-056      Create payment schedule, collect payments, apply payments received to
             scheduled amount due (e.g., amount in judgment), and produce reports on
             overdue amounts (e.g., for previously waived fees).


      MDEC Procurement K11-0030-29                                                                                     September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                       ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 135 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                                          ACCOUNTING

    ID                                   Requirement Text                                          Response Code   Comments
ACC-056.01       Provide USER with the ability to assign Payment Schedule to PARTY      0
                 ACCOUNT.
ACC-056.02       Provide USER with the ability to assign PAYMENT to a Payment Schedule. 0

ACC-056.03        Provide USER with the ability to produce report for ACCOUNT balances.        0
ACC-057      Identify (i.e., input or compute) and record arrearages, generate alerts when
             scheduled payments not made (e.g., for unpaid assessments now due), and
             take or prompt USER to take appropriate action (e.g., refer to collection
             agency). (see also Scheduling Function and Execution Function)
ACC-057.01        AUTOMATICALLY identify arrearages on PARTY ACCOUNT, CASE                     0
                  ACCOUNT.
ACC-057.02        Provide USER with the ability to assign indicator for arrearages to a        0
                  PARTY ACCOUNT, CASE ACCOUNT.
ACC-057.03        Provide ADMIN USER with the ability to define rule to alert when scheduled   0
                  payments are not made on CASE.
ACC-057.04        AUTOMATICALLY prompt USER to invoke rule when scheduled payments             0
                  are not made on CASE.
ACC-058      Post (as noted above), process (i.e., tasks noted throughout these accounting
             sections), and track (e.g., principal, costs, attorney fees) garnishments,
             installment payments, and partial payments (e.g., through memorandum of
             credit) from litigants subsequent to judgments. (see also General Accounting
             Function, Disposition Function, and Execution Function)
ACC-058.01        AUTOMATICALLY assign Costs/Fines/Payments from PARTY after                   0
                  CASE DISPOSITION.
ACC-058.02        Provide ADMIN USER with the ability to define workflow to assign             0
                  Costs/Fines/Payments from PARTY after CASE DISPOSITION.
ACC-059      Generate accounting notices (e.g., for payment, overdue payment) receipting
             or bookkeeping. (see also Document Generation and Processing Function)
ACC-059.01        AUTOMATICALLY generate notices for Accounting Functions. (e.g..              0
                  Receivables )
ACC-059.02        Provide USER with the ability to produce notices for Accounting Functions    0
                  (e.g.. Receivables)
ACC-060      Allow flexible, USER-defined and -maintained account structure that permits
             funds to be allocated to appropriate case cost types and other accounts (e.g.,
             for city, county, state, court).



      MDEC Procurement K11-0030-29                                                                                  September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                            Page 136 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                          ACCOUNTING

    ID                                      Requirement Text                                       Response Code   Comments
ACC-060.01       Provide ADMIN USER with the ability to define codes for Chart of              0
                 ACCOUNTS structure that can be allocated appropriately to CASE (e.g..
                 City, County, State, Court).
ACC-061      Place hold on disbursements of funds deposited for a case.

ACC-061.01       Provide ADMIN USER with the ability to define rule to place hold on CASE      0
                 DISBURSEMENTS.
ACC-061.02       Provide USER with the ability to assign hold on CASE DISBURSEMENTS.           0

ACC-062      Disburse funds electronically to recipient bank accounts.

ACC-062.01        Provide ADMIN USER with the ability to define rule to disburse funds         0
                  electronically.
ACC-062.02        Provide USER with the ability to assign and invoke rule to disburse funds    0
                  electronically.
ACC-063      Provide information for disbursement of undistributed or unclaimed moneys
             (e.g., unreturned checks for moneys paid by court), update ledgers, and
             produce reports (e.g., for each check not cleared over specific period).
ACC-063.01        Provide ADMIN USER with the ability to define reports for Unclaimed          0
                  Property. (e.g.. Outstanding checks paid by COURT).
ACC-063.02        AUTOMATICALLY update General Ledger for Unclaimed Property (e.g..            0
                  Outstanding Checks paid by COURT).
ACC-063.03        Provide USER with the ability to produce report for Unclaimed Property for   0
                  DISBURSEMENTS.
ACC-064      Electronically authorize and disburse collected fees to other units (e.g.,
             appellate court for appealed cases). (see also Multifunction Capabilities and
             Integration)
ACC-064.01        INTERFACE with COURT UNITS for collected fees (e.g.. APPELATE                0
                  Court ).
ACC-065      Post noncase-related receipts and disbursements (e.g., for copies or interest)
             to accounting records and associate with proper account.
ACC-065.01        Provide USER with the ability to assign RECEIPTS to non-CASE records.        0
                  (e.g.. Copies, Bank Interest)
ACC-065.02        Provide USER with the ability to assign DISBURSEMENTS to non-CASE            0
                  records (e.g.. Service Charge).
ACC-065.03        Provide ADMIN USER with the ability to define ACCOUNT CODES for non-         0
                  CASE accounting transactions (e.g.. Copies, Interest).

      MDEC Procurement K11-0030-29                                                                                  September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                            Page 137 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                           ACCOUNTING

    ID                                          Requirement Text                                   Response Code   Comments
ACC-066      Compute parts of fees to be allocated to other local and state units (e.g.,
             portion of fees for county parks, county library, and other purposes) according
             to predefined formula.
ACC-066.01         Provide ADMIN USER with the ability to define Codes for Payment             0
                   Allocation to other Entities. (e.g.. Local and State Units)
ACC-066.02         AUTOMATICALLY assign Allocation Codes for Payments to other Entities        0
                   (e.g.. Local and State Units).
ACC-067      Disburse collected fees electronically according to predefined formula either
             periodically (e.g., monthly) or when fees received in conjunction with
             Accounting - Receipting Function. (see also Multifunction Capabilities and
             Integration and Accounting - Receipting Function)
ACC-067.01         Provide ADMIN USER with the ability to define workflow for disbursement     0
                   of Funds by Allocation codes.
ACC-067.02         Interface with other COURT Agencies for electronic Disbursement of          0
                   Funds by Allocation Codes.
ACC-068      Produce report showing allocation formula for disbursing monies to other local
             and state units over specific period, monies disbursed, and how formula was
             used to compute allocation. (see also Management and Statistical Reports
             Function)
ACC-068.01         Provide USER with the ability to produce report for Allocation Codes to     0
                   other Entities ( e.g.. Local and State Units).
ACC-068.02         Provide USER with the ability to produce report for Funds Disbursed to      0
                   other Entities by Allocation Codes ( e.g.. Local and State Units).
ACC-069      Initiate, print, and disburse sequentially numbered checks periodically or on
             demand, stop issuance on checks, void checks, identify and process
             outstanding checks, identify and process checks that have cleared, report on
             above transactions, and record in check register.
ACC-069.01         Provide USER with the ability to produce sequentially numbered CHECKS       0
                   for DISBURSEMENTS.
ACC-069.02         AUTOMATICALLY produce Sequentially numbered CHECKS for                      0
                   DISBURSEMENTS.
ACC-069.03         Provide USER with the ability to assign Stop Payment on CHECKS.             0
ACC-069.04         Provide USER with the ability to assign Voids on CHECKS.                    0
ACC-069.05         Provide USER with the ability to assign INDICATOR to CHECKS in              0
                   CHECK REGISTER. (e.g.. Cleared or uncleared)
ACC-069.06         AUTOMATICALLY assign CHECKS to CHECK REGISTER.                              0


      MDEC Procurement K11-0030-29                                                                                  September 1, 2010
                                                   MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                       ATTACHMENT C
                                                     MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 138 of 249
                                                            FUNCTIONAL REQUIREMENTS

                                                                             ACCOUNTING

    ID                                          Requirement Text                                     Response Code   Comments
ACC-070      Initiate, print, and disburse refund checks individually or cumulatively over
             specific periods (e.g., for filing fees collected in error, bond refunds); record
             checks on check register.
ACC-070.01         Provide ADMIN USER with the ability to define rule to issue CHECKS for        0
                   REFUND.
ACC-070.02         AUTOMATICALLY invoke rule to produce CHECKS for REFUND.                       0
ACC-070.03         Provide USER with the ability to produce CHECKS for REFUND.                   0
ACC-071      Produce precheck register (e.g., to view checks prior to printing register) and
             check register over specific period.
ACC-071.01         Provide USER with the ability to produce PRE-CHECK REGISTER. (e.g..           0
                   View checks prior to printing).
ACC-071.02         Provide USER with the ability to produce CHECK REGISTER.                      0
ACC-072      Apply installment payments to proper account or activity (e.g., to fees, support
             owed, or alimony owed).
ACC-072.01         Provide USER with the ability to assign Installment Payment to PARTY          0
                   ACCOUNT or CASE ACCOUNT.
ACC-073      For specific periods, produce separate reports showing (1) cases for which
             fees received, no fees received, fees waived, no fees due; (2) all adjustments
             to accounts; (3) accounts receivable or payable for each case.
ACC-073.01         Provide ADMIN USER with the ability to define reports for Accounting          0
                   transactions for CASE RECORDS (e.g.. Fees received, Fees waived, No
                   Fees due, Account Adjustments).
ACC-073.02         Provide USER with the ability to produce report for Accounting                0
                   Transactions for CASE RECORDS (e.g.. Fees received, Fees waived, No
ACC-073.03         Fees due).
                   Provide ADMIN USER with the ability to define reports for Finance (e.g..      0
                 Accounts Receivable, Accounts Payable) for CASE.
ACC-073.04       Provide USER with the ability to produce report for Finance (e.g.. Accounts 0
                 Receivable, Accounts Payable) for CASE.
ACC-074      Produce report containing information on fees waived and associated
             payments.
ACC-074.01       Provide ADMIN USER with the ability to define reports for Accounting        0
                 transactions for CASE RECORDS (e.g.. Fees received, Fees waived, No
                 Fees due, Account Adjustments).
ACC-074.02       Provide USER with the ability to produce report for Accounting              0
                 Transactions for CASE RECORDS (e.g.. Fees received, Fees waived, No
ACC-075          Fees due).
             Provide flexible schema of USER privileges for accessing information and
             creating adjusting financial entries. (see also Security Function)
      MDEC Procurement K11-0030-29                                                                                    September 1, 2010
                                                   MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                        ATTACHMENT C
                                                     MARYLAND ELECTRONIC COURT PROCUREMENT                              Page 139 of 249
                                                            FUNCTIONAL REQUIREMENTS

                                                                             ACCOUNTING

    ID                                       Requirement Text                                         Response Code   Comments
ACC-075.01       Provide ADMIN USER with the ability to define security to access Financial       0
                 Information.
ACC-075.02       Provide ADMIN USER with the ability to define security to create                 0
                 Accounting Transactions.
ACC-075.03       Provide ADMIN USER with the ability to define security to update                 0
                 Accounting Transactions.
ACC-076      Produce lists arranged according to USER-selected criteria for financial
             transactions. (e.g., fees and other receipts by date, type, party,
             location(county), date, month to date, calendar year to date, fiscal year to date,
             statewide)
ACC-076.01       Provide ADMIN USER with the ability to define reports for Financial              0
                 Transactions
ACC-076.02       Provide ADMIN USER with the ability to define fields to be displayed on          0
                 Financial Report.
ACC-077      Create positive pay file of check numbers and amounts and send to bank.

ACC-077.01       AUTOMATICALLY provide POSITIVE PAY file to Bank for fraud prevention. 0
ACC-077.02         Provide ADMIN USER with the ability to define rule to provide POSITIVE         0
                   PAY file to Bank for fraud prevention.
ACC-078      Receive bank statements and reconcile bank accounts electronically. (see
             Multi-Function Capabilities and Integration)
ACC-078.01         INTERFACE with BANK for BANK ACCOUNT reconciliation.                           0
ACC-078.02         AUTOMATICALLY assign reconciliation between CHECK REGISTER and                 0
                   BANK ACCOUNT.
ACC-079      Coordinate and track changes in case numbers (e.g., for cases transferred to
             general jurisdiction court), individual identifiers (e.g., across courts, criminal
             support units, CJ agencies, and non-justice agencies), and other identifiers.
ACC-079.01         AUTOMATICALLY coordinate and track changes to case numbers and                 0
                   other identifiers.
ACC-080      Track changes in modified or amended charges from point of arrest or initial
             filing (including associated costs) through completion of sentence while
             remaining linked to incident for disposition tracking purposes.
ACC-080.01         AUTOMATICALLY track modified or amended charges.                               0
ACC-081      Track changes in dismissed charges from point of arrest or initial filing through
             disposition while remaining linked to incident for disposition tracking purposes.
ACC-081.01       AUTOMATICALLY track dismissed charges.                                           0

      MDEC Procurement K11-0030-29                                                                                     September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                       ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 140 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                                          ACCOUNTING

    ID                                     Requirement Text                                        Response Code   Comments
ACC-082      Track pleas entered and their verdicts.
ACC-082.01        AUTOMATICALLY track pleas and verdicts.                                      0
ACC-083      Track sentence compliance and modifications. (see Disposition and
             Compliance functions)
ACC-083.01        AUTOMATICALLY track sentence compliance and modifications.                   0
ACC-084      Maintain sufficient information for sentencing documents (e.g., for jail
             commitment, probation, work referral). (see Disposition Function)
ACC-084.01        AUTOMATICALLY maintain sufficient case information for sentencing            0
                  documents.
ACC-085      Track location, reasons for issuance and resolution, and status of all warrants
             and other served documents (e.g., subpoenas, bench warrants, search
             warrants, warrant recalls, capiases). (see Document Generation and
             Processing Function)
ACC-085.01        AUTOMATICALLY track location, reasons for issuance and resolution,           0
                  status of warrants and other services documents.
ACC-086      Provide a process (e.g. flag cases and the party who presented the check) that
             should include but not be limited to identifying NSF checks, stale checks and
             returned checks.
ACC-086.01        Provide ADMIN USER with the ability to define workflow to identify CASE      0
                  and PARTY for NSF, Stale and Returned checks.
ACC-086.02        Provide ADMIN USER with the ability to define an indicator to CASE and       0
                  PARTY for NSF, Stale and Returned Checks.
ACC-086.03        Provide USER with the ability to assign an indicator to CASE and PARTY       0
                  for NSF, Stale and Returned Checks.
ACC-087      AUTOMATICALLY populate appropriate fees/costs (not fines) based on
             violation and allow for clerk override.
ACC-087.01        Provide ADMIN USER with the ability to define rule to assess COSTS           0
                  based on a violation.
ACC-087.02        Provide USER with the ability to assign COSTS based on a violation.          0
ACC-087.03        Provide USER with the ability to override rule to assess COSTS based on      0
                  a violation.
ACC-087.04        AUTOMATICALLY invoke rule to assign COSTS based on a violation.              0
ACC-088      Populate appropriate fines based on violation and local business rules and
             allow for clerk override.
ACC-088.01        Provide ADMIN USER with the ability to define rule to assess FINES based     0
                  on a violation.

      MDEC Procurement K11-0030-29                                                                                  September 1, 2010
                                                    MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                         ATTACHMENT C
                                                      MARYLAND ELECTRONIC COURT PROCUREMENT                               Page 141 of 249
                                                             FUNCTIONAL REQUIREMENTS

                                                                              ACCOUNTING

    ID                                          Requirement Text                                        Response Code   Comments
ACC-088.02        Provide USER with the ability to assign FINES based on a violation.               0
ACC-088.03        Provide USER with the ability to override rule to assess FINES based on a         0
                  violation.
ACC-088.04        AUTOMATICALLY invoke rule to assign FINES based on a violation.                   0
ACC-089      Ability to establish a priority ranking for funds collected, funds paid out, and for
             reconciliation of all fund categories paid to state and county criminal justice
             agencies.
ACC-089.01        Provide ADMIN USER with the ability to define indicator for priority ranking      0
                  of ACCOUNTS for State/County Criminal Justice Agencies.
ACC-090      Supply financial reports as defined by local jurisdiction reporting needs.
ACC-090.01       Provide ADMIN USER with the ability to define Financial Reports.                   0
ACC-090.02       Provide USER with the ability to produce Financial Reports.                        0
ACC-091      Produce correspondence (e.g., payment notices and dunning letters).
ACC-091.01       Provide ADMIN USER with the ability to define workflow for document                0
                 generation [payment notice and dunning letters].
ACC-091.02       Provide USER with the ability to produce document [payment notices and             0
                 dunning letters].
ACC-091.03       AUTOMATICALLY produce document [payment notices and dunning                        0
                 letters]
ACC-092      Provide capability to adjust receivables on a specific case or account when
             directed by court order (e.g., write off uncollected debt when obligor dies) or
             with administrative approval.
ACC-092.01       Provide USER with the ability to assign adjustments to RECEIVABLES by              0
                 Court Order ( e.g.. write off uncollected debt).
ACC-093      Track installment payments and partial payments.
ACC-093.01       Provide ADMIN USER with the ability to define fields for querying CASE             0
                 records when Partial and Installment Payments are made.
ACC-093.02       Provide USER with the ability to search for CASE records when Partial and          0
                 Installment Payments are made.
ACC-094      Track and age undistributed, unclaimed, or forfeited money and produce aging
             reports.
ACC-094.01       Provide ADMIN USER with the ability to define fields for querying CASE             0
                 records for undistributed, unclaimed and forfeited money.
ACC-094.02       Provide USER with the ability to search for CASE records for undistributed,        0
                 Unclaimed and forfeited money.


      MDEC Procurement K11-0030-29                                                                                       September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                       ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 142 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                           ACCOUNTING

    ID                                     Requirement Text                                         Response Code   Comments
ACC-094.03      Provide ADMIN USER with the ability to define aging report for                  0
                undistributed, unclaimed and forfeited money.
ACC-094.04      Provide USER with the ability to produce aging report for unclaimed,            0
                undistributed and forfeited money.
ACC-095      Support check writing.
ACC-095.01        AUTOMATICALLY provide Check Writing functionality                             0
ACC-096      Provide capability to track cases and accounts which have been placed on a
             payment plan.
ACC-096.01        Provide ADMIN USER with the ability to define fields for querying CASE        0
                  records where PAYMENT PLANS exist.
ACC-096.02        Provide USER with the ability to search for CASE records where                0
                  PAYMENT PLANS exist.
ACC-097      Provide ability to establish a payment plan for one or more cases.
ACC-097.01        Provide ADMIN USER with the ability to define rule to establish PAYMENT       0
                  PLAN for one or more CASE.
ACC-097.02        Provide USER with the ability to assign PAYMENT PLAN to one or more           0
                  CASE.
ACC-097.03        Provide USER with the ability to override PAYMENT PLAN to one or more         0
                  CASE.
ACC-098      Provide ability to establish payment plans with variable terms and amounts.
ACC-098.01        Provide ADMIN USER with the ability to define rule to establish PAYMENT       0
                  PLAN with variable terms and Amount.
ACC-098.02        Provide USER with the ability to assign PAYMENT PLAN with variable            0
                  terms and Amount.
ACC-098.03        Provide USER with the ability to override PAYMENT PLAN with variable          0
                  terms and Amount.
ACC-099      AUTOMATICALLY updates the register of actions for each late payment notice
             generated.
ACC-099.01        AUTOMATICALLY updates the register of actions/DOCKET for each late            0
                  payment notice generated.
ACC-100      Ability to change status within the collection process (e.g., defendant is moved
             from collection to payment plan).
ACC-100.01        Provide ADMIN USER with the ability to define rule to change                  0
                  RECEIVABLE status (e.g.. Collection to Payment Plan).
ACC-100.02        Provide USER with the ability to assign change to RECEIVABLE statue.          0
                  (e.g.. Collection to Payment plan).

      MDEC Procurement K11-0030-29                                                                                   September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                            Page 143 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                                         ACCOUNTING

    ID                                       Requirement Text                                     Response Code   Comments
ACC-101      Ability to remove a case from a payment plan without deleting the payment plan
             for other cases.
ACC-101.01        Provide ADMIN USER with the ability to define rule to remove case without 0
                  effecting other CASES from PAYMENT PLAN.
ACC-101.02        Provide USER with the ability to invoke rule to remove CASE without       0
                  effecting other CASES from PAYMENT PLAN.
ACC-101.03        Provide USER with the ability to override rule to remove CASE without     0
                  effecting other CASES from PAYMENT PLAN.
ACC-102      Ability to add a case to an existing payment plan.
ACC-102.01       Provide ADMIN USER with the ability to define rule to add CASE to existing 0
                 PAYMENT PLAN.
ACC-102.02       Provide USER with the ability to assign CASE to existing PAYMENT PLAN. 0

ACC-102.03        Provide USER with the ability to override rule to assign CASE to existing   0
                  PAYMENT PLAN.
ACC-103      Permit payment to be accepted for cases filed but not docketed completely
             (e.g., all data, such as party names, not entered into system) and recorded by
             entering minimal amount of data (e. g., case number, case type, case
             category, case style or title, name of party submitting payment, date of
             payment, nature of payment) as precursor to full docket entry.
ACC-103.01        AUTOMATICALLY assign PAYMENTS to CASE filed but not INITIATED.              0
ACC-103.02        Provide ADMIN USER with the ability to define rule to receive PAYMENT to    0
                  CASE filed but not INITIATED.
ACC-103.03        Provide USER with the ability to assign PAYMENT to CASE filed but not       0
                  INITIATED.
ACC-103.04        Provide USER with the ability to override rule to assign PAYMENT to         0
                  CASE filed but not INITIATED.
ACC-104      Accept payments by electronic funds transfer (see also Multifunction
             Capabilities and Integration).
ACC-104.01       Provide ADMIN USER with the ability to define rule to accept PAYMENT by 0
                 Electronic Funds Transfer.
ACC-104.02       Provide USER with the ability to invoke rule to accept PAYMENT by       0
                 Electronic Funds Transfer.
ACC-104.03       Provide USER with the ability to override rule to accept PAYMENT by     0
                 Electronic Funds Transfer.



      MDEC Procurement K11-0030-29                                                                                 September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                            Page 144 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                           ACCOUNTING

    ID                                      Requirement Text                                       Response Code   Comments
ACC-105      Accept payments from attorneys by electronic funds transfer from attorney
             bank accounts, debiting accounts established by attorneys to cover court
             expenses, debiting attorney credit card accounts, and on-line check writing.
             (see also Multifunction Capabilities and Integration)
ACC-105.01       Provide ADMIN USER with the ability to define rule to accept ATTORNEY 0
                 PAYMENT from different sources (e.g.. EFT, Draw Down, Credit Card etc).
ACC-105.02       Provide USER with the ability to invoke rule to accept ATTORNEY         0
                 PAYMENT from different sources (e.g.. EFT, Draw Down, Credit Card etc).
ACC-105.03       Provide USER with the ability to override rule to accept ATTORNEY       0
                 PAYMENT from different sources (e.g.. EFT, Draw Down, Credit Card etc).
ACC-106      Allocate fees associated with nonparties (e.g., from couriers, media) that may
             or may not be case related (e.g., for forms, document copies, certified copies)
             and process appropriately (e.g., not docketed if not related to specific case).

ACC-106.01       Provide USER with the ability to assign PAYMENTS which are NON-CASE           0
                 related.
ACC-106.02       Provide USER with the ability to assign PAYMENTS which are not related        0
                 to PARTY on CASE. (e.g.. Courier, Media).
ACC-106.03       Provide ADMIN USER with the ability to define rule to accept PAYMENTS         0
                 which are NON-CASE related.
ACC-106.04       Provide ADMIN USER with the ability to define rule to accept PAYMENTS         0
                 which are not related to PARTY on CASE (e.g.. Courier, Media).
ACC-107      Accept multiple types of payments in single transaction (e.g., cash, check).
ACC-107.01       AUTOMATICALLY assign multiple Method Of Payments to single receipt.           0
ACC-107.02       Provide ADMIN USER with the ability to define rule to accept multiple         0
                 Method Of Payments to single receipt.
ACC-107.03       Provide USER with the ability to assign multiple Method Of Payments to        0
                 single receipt.
ACC-107.04       Provide USER with the ability to override rule to assign multiple Method Of   0
                 Payments to single receipt.
ACC-108      Accept multiple payments for single case with capability to process as either
             single payment or separate payments (e.g., voiding, receipting).
ACC-108.01       Provide ADMIN USER with the ability to define rule to process multiple        0
                 PAYMENTS for single CASE.


      MDEC Procurement K11-0030-29                                                                                  September 1, 2010
                                                   MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                         ATTACHMENT C
                                                     MARYLAND ELECTRONIC COURT PROCUREMENT                               Page 145 of 249
                                                            FUNCTIONAL REQUIREMENTS

                                                                             ACCOUNTING

    ID                                       Requirement Text                                          Response Code   Comments
ACC-108.02        Provide ADMIN USER with the ability to define rule to process multiple           0
                  PAYMENTS for single CASE as a single or separate PAYMENTS.
ACC-108.03        Provide USER with the ability to assign multiple PAYMENTS for a single           0
                  CASE.
ACC-108.04        Provide USER with the ability to assign multiple PAYMENTS for a single           0
                  CASE as a single or separate PAYMENTS.
ACC-109      Accept single payment for multiple cases with capability to process separately
             for each case (e.g., voiding, receipting).
ACC-109.01        Provide ADMIN USER with the ability to define rule to process single             0
                  PAYMENT for multiple CASE.
ACC-109.02        Provide ADMIN USER with the ability to define rule to process single             0
                  PAYMENT for multiple CASE as separate PAYMENTS.
ACC-109.03        Provide USER with the ability to assign single PAYMENT for multiple              0
                  CASE.
ACC-109.04        Provide USER with the ability to assign single PAYMENT for multiple              0
                  CASE as separate PAYMENTS.
ACC-110      Permit payments to be voided and re-entered before daily balancing with
             proper security provisions, with the capability to report on voided payments
             (including reason for void) over a given specified period.
ACC-110.01        Provide ADMIN USER with the ability to define rule to allow PAYMENT              0
                  ADJUSTMENT before End-Of-Day (EOD) closing.
ACC-110.02        Provide USER with the ability to assign PAYMENT ADJUSTMENT before                0
                  End-Of-Day (EOD) closing.
ACC-110.03        Provide ADMIN USER with the ability to define report on PAYMENT                  0
                  ADJUSTMENT before End-Of-Day(EOD) closing.
ACC-110.04        Provide USER with the ability to produce report on PAYMENT                       0
                  ADJUSTMENT before End-Of-Day (EOD) closing.
ACC-111      Generate and print receipts with proper identifiers (e.g., fee code, court location
             and address) based on collections with USER option to receive single or
             multiple copies, noting how many copies were printed.
ACC-111.01        Provide ADMIN USER with the ability to define rule to capture relevant data      0
                  on PAYMENT RECEIPT (e.g.. Account Code, PARTY Address, COURT
                  Address etc).
ACC-111.02        Provide ADMIN USER with the ability to define indicator to specify number        0
                  of copies of DOCUMENT to generate.
ACC-111.03        Provide ADMIN USER with the ability to define indicator to store number of       0
                  copies generated for a DOCUMENT.

      MDEC Procurement K11-0030-29                                                                                      September 1, 2010
                                                   MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                        ATTACHMENT C
                                                     MARYLAND ELECTRONIC COURT PROCUREMENT                              Page 146 of 249
                                                            FUNCTIONAL REQUIREMENTS

                                                                            ACCOUNTING

    ID                                       Requirement Text                                         Response Code   Comments
ACC-112      Generate and distribute electronic receipts for electronic payments. (see also
             Multifunction Capabilities and Integration)
ACC-112.01       Provide ADMIN USER with the ability to define rule to produce Electronic         0
                 DOCUMENT [RECEIPT] for PAYMENT (e.g.. Manual, electronic etc).
ACC-112.02       AUTOMATICALLY produce Electronic DOCUMENT [RECEIPT] for                          0
                 PAYMENT (e.g.. Manual, Electronic etc).
ACC-112.03       Provide USER with the ability to produce Electronic DOCUMENT                     0
                 [RECEIPT] for PAYMENT (e.g.. Manual, electronic etc).
ACC-113      Generate and print receipts with unique, locally defined, sequential receipt
             numbers.
ACC-113.01       Provide ADMIN USER with the ability to define rule to generate unique            0
                 sequential RECEIPT NUMBER at Enterprise or Jurisdiction or Cash
                 Register level.
ACC-113.02       AUTOMATICALLY generate unique sequential RECEIPT NUMBER at                       0
                 Enterprise or Jurisdiction or Cash Register level.
ACC-114      Generate and print multiple receipts from one financial transaction covering
             multiple payments for multiple cases or purposes (e.g., attorney files and pays
             fees for several cases in one trip to courthouse).
ACC-114.01       Provide ADMIN USER with the ability to define rule to process multiple           0
                 PAYMENTS for multiple CASES as one Financial transaction.
ACC-114.02       Provide ADMIN USER with the ability to define rule to produce multiple           0
                 RECEIPTS for multiple PAYMENTS on multiple CASES processed as one
                 Financial transaction.
ACC-114.03       Provide USER with the ability to assign multiple PAYMENTS for multiple           0
                 CASES as one Financial transaction.
ACC-114.04       Provide USER with the ability to produce multiple RECEIPTS for multiple          0
                 PAYMENTS on multiple CASES processed as one Financial transaction.
ACC-115      Generate and print either a single receipt or multiple receipts from one financial
             transaction covering multiple payments for single case (e.g., attorney files and
             pays fees for pleading, forms, and copies for given case in one trip to
             courthouse).
ACC-115.01       Provide ADMIN USER with the ability to define rule to process multiple           0
                 PAYMENTS for single CASE as one Financial transaction.
ACC-115.02       Provide ADMIN USER with the ability to define rule to produce multiple           0
                 RECEIPTS for multiple PAYMENTS on single CASE processed as one
                 Financial transaction.


      MDEC Procurement K11-0030-29                                                                                     September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                            Page 147 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                                         ACCOUNTING

    ID                                      Requirement Text                                      Response Code   Comments
ACC-115.03       Provide ADMIN USER with the ability to define rule to produce single         0
                 RECEIPT for multiple PAYMENTS on single CASE processed as one
                 Financial transaction.
ACC-115.04       Provide USER with the ability to assign multiple PAYMENTS for single         0
                 CASE as one Financial transaction.
ACC-115.05       Provide USER with the ability to produce multiple RECEIPTS for multiple      0
                 PAYMENTS on single CASE processed as one Financial transaction.
ACC-115.06       Provide USER with the ability to produce single RECEIPT for multiple         0
                 PAYMENTS on single CASE processed as one Financial transaction.
ACC-116      Permit receipts to be reprinted with appropriate security (e.g., if printer
             malfunctions during printout) with same receipt numbers but noted as a
             duplicate receipt.
ACC-116.01       Provide ADMIN USER with the ability to define rule to reprint RECEIPT        0
                 with appropriate security.
ACC-116.02       Provide USER with the ability to produce reprint RECEIPT with appropriate    0
                 security.
ACC-116.03       AUTOMATICALLY reprint RECEIPT with appropriate security.                     0
ACC-116.04       AUTOMATICALLY assign any reprinted DOCUMENT [RECEIPT,                        0
                 INVOICE, NTICE] as a duplicate .
ACC-116.05       Provide ADMIN USER with the ability to define rule to assign any reprinted   0
                 DOCUMENT [RECEIPT, INVOICE, NTICE] as a duplicate .
ACC-116.06       Provide USER with the ability to assign any reprinted DOCUMENT               0
                 [RECEIPT, INVOICE, NTICE] as a duplicate .
ACC-117      Record and maintain front-counter bookkeeping information on receipts and
             disbursements (e.g., payer, payee, receipt number, case number, purpose of
             payment or disbursement).
ACC-117.01       AUTOMATICALLY assign Financial Information (e.g.. Payor, Payee,              0
                 Account Code, Case Number etc) to DOCUMENT [RECEIPT,
                 DISBURSEMENT].
ACC-117.02       Provide ADMIN USER with the ability to define rule to assign Financial       0
                 Information (e.g.. Payor, Payee, Account Code, Case Number etc) to
                 DOCUMENT [RECEIPT, DISBURSEMENT].
ACC-118      Provide secure passwords for each cashier. (see also Security Function)
ACC-118.01       AUTOMATICALLY assign secure password for Cashiers.                           0
ACC-118.02       Provide ADMIN USER with the ability to define secure Password for            0
                 Cashiers.

      MDEC Procurement K11-0030-29                                                                                 September 1, 2010
                                                     MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                   ATTACHMENT C
                                                       MARYLAND ELECTRONIC COURT PROCUREMENT                         Page 148 of 249
                                                              FUNCTIONAL REQUIREMENTS

                                                                                 ACCOUNTING

    ID                                        Requirement Text                                     Response Code   Comments
ACC-119      Identify cashier with all transactions (e.g., receipts, reports).
ACC-119.01        AUTOMATICALLY assign CASHIER to RECEIPT transactions.                        0
ACC-120      Compute totals, list transactions, and balance for each cash drawer, register,
             cashier, and fee type.
ACC-120.01        AUTOMATICALLY assign list of transactions and Total for each DRAWER,         0
                  REGISTER, CASHIER and ACCOUNT CODE.
ACC-120.02        Provide ADMIN USER with the ability to define report for DRAWER,             0
                  REGISTER, CASHIER and ACCOUNT CODE.
ACC-120.03        Provide USER with the ability to produce report for DRAWER, REGISTER,        0
                  CASHIER and ACCOUNT CODE.
ACC-121      List contents of each drawer (e.g., cash, checks, credit card receipts, fee
             waivers, money orders).
ACC-121.01        Provide ADMIN USER with the ability to define report for detail of           0
                  INSTRUMENTS in CASH DRAWER.
ACC-121.02        Provide USER with the ability to produce report for detail of                0
                  INSTRUMENTS in CASH DRAWER.
ACC-122      Print summary for each cashier including totals for each type of payment (e.g.,
             cash, checks, credit card receipts, fee waivers, money orders). (see also
             Accounting - Back Office Function)
ACC-122.01        Provide ADMIN USER with the ability to define report for detail of           0
                  INSTRUMENTS in CASH DRAWER for each CASHIER.
ACC-122.02        Provide USER with the ability to produce report for detail of                0
                  INSTRUMENTS in CASH DRAWER for each CASHIER.
ACC-123      List any discrepancies among payments, receipts, and cases over specific
             periods for each cashier for whom above summary shows imbalance for any
             type of payment. (see also Accounting - Back Office Function)
ACC-123.01        Provide ADMIN USER with the ability to define report for discrepancies in    0
                  PAYMENTS processed for each CASHIER.
ACC-123.02        Provide USER with the ability to produce report for discrepancies in         0
                  PAYMENTS processed for each CASHIER.
ACC-124      Suspend cashier operations multiple times during day (e.g., close without
             balancing to permit lunch and other breaks).
ACC-124.01        AUTOMATICALLY suspend cashier operations during day. (e.g.. Lunch,           0
                  Breaks)



      MDEC Procurement K11-0030-29                                                                                  September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                            Page 149 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                            ACCOUNTING

    ID                                       Requirement Text                                      Response Code   Comments
ACC-125      Permit transactions that arrive after cashier closeout to be entered as
             transaction for next day and distinguish between transaction date and closeout
             date. Receipt must be issued for date of transaction.
ACC-125.01       Provide ADMIN USER with the ability to define workflow to allow CASHIER       0
                 to process PAYMENT after End-of-Day(EOD) closeout.
ACC-125.02       Provide USER with the ability to assign PAYMENT after End-Of-Day(EOD)         0
                 closeout.
ACC-125.03       AUTOMATICALLY distinguish between transaction date and closeout date          0
                 for a PAYMENT.
ACC-126      Print systemwide daily cash receipts journal and allow reprinting of journal
             reports.
ACC-126.01       AUTOMATICALLY produce report for Daily Cash Receipt Journal.                  0
ACC-126.02       Provide ADMIN USER with the ability to define report for Daily Cash           0
                 Receipt Journal.
ACC-126.03       Provide USER with the ability to produce report for Daily Cash Receipt        0
                 Journal.
ACC-127      Create and maintain system-defined and USER-customized chart of accounts.
ACC-127.01       Provide ADMIN USER with the ability to define codes for CHART OF              0
                 ACCOUNTS.
ACC-127.02       Provide USER with the ability to choose codes for CHART OF ACCOUNTS.          0
ACC-128      Maintain journal and, if appropriate, subsidiary ledger for each account by
             posting debits, credits, and adjusting entries.
ACC-128.01       AUTOMATICALLY assign journal entries for all accounting transactions.         0
ACC-128.02       AUTOMATICALLY assign Subsidiary Ledger entries for all accounting             0
                 transactions.
ACC-129      Reconcile and balance all accounts.
ACC-129.01       AUTOMATICALLY produce report for ACCOUNT TRIAL BALANCE.                       0
ACC-129.02       Provide USER with the ability to produce report for ACCOUNT balances.         0
ACC-129.03       Provide USER with the ability to produce report for ACCOUNT TRIAL             0
                 BALANCE.
ACC-129.04       Provide USER with the ability to assign reconcile ACCOUNT TRIAL               0
                 BALANCE.
ACC-130      Create general ledger by posting journal entries, subsidiary ledger totals, and
             other information to each account in chart of accounts.
ACC-130.01       AUTOMATICALLY assign General Ledger entries by posting Journal and            0
                 Subsidiary Ledger entries.
      MDEC Procurement K11-0030-29                                                                                  September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                        ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                              Page 150 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                            ACCOUNTING

    ID                                       Requirement Text                                        Response Code   Comments
ACC-131      Populate subsidiary ledger AUTOMATICALLY using data from other parts of
             system (e.g., Disposition Function, Execution Function, other accounting
             functions).
ACC-131.01       AUTOMATICALLY assign Subsidiary Ledger entries for all accounting         0
                 transactions originating from CASE activity.
ACC-131.02       Provide ADMIN USER with the ability to define codes for Subsidiary Ledger 0
                 for Accounting transactions originating from CASE Activity.
ACC-132      Support the automated upload of case financial data reformatted into
             appropriate accounting and chart of account formats to the City/County/State
             Treasurer.
ACC-132.01       INTERFACE with City/County/State Treasurer to provide CASE Financial      0
                 Data.
ACC-133      Provide for the calculation of accounts receivable.
ACC-133.01        AUTOMATICALLY calculate ACCOUNT RECEIVABLE Balance.                            0
ACC-133.02        AUTOMATICALLY calculate ACCOUNT RECEIVABLE Aging.                              0
ACC-133.03        Provide ADMIN USER with the ability to define report for ACCOUNT               0
                  RECEIVABLE Balance/Aging.
ACC-133.04        Provide USER with the ability to produce report for ACCOUNT                    0
                  RECEIVABLE Balance/Aging.
ACC-134      Provide the ability to view the projected future revenues for a given time period
             and account type.
ACC-134.01        AUTOMATICALLY provide Projected Revenues by ACCOUNT from                       0
                  ACCOUNT RECEIVABLE.
ACC-134.02        Provide ADMIN USER with the ability to define report for Projected             0
                  Revenues by ACCOUNT from ACCOUNT RECEIVABLE.
Acc-134.03        Provide USER with the ability to produce report for Projected Revenues by      0
                  ACCOUNT from ACCOUNT RECEIVABLE.
ACC-135      Provide the ability to view and print suspended cash amounts (e.g. suspend
             fines due to incarceration, in lieu of other sanctions) under various parameters
             based on local business rules.
ACC-135.01        Provide ADMIN USER with the ability to define rule to set/identify             0
                  suspended FINES/COSTS for CASE/PARTY (e.g.. Incarceration, in lieu of
                  sanctions).
ACC-135.02        Provide ADMIN USER with the ability to define report for suspended             0
                  FINES/COSTS for CASE/PARTY (e.g.. Incarceration, in lieu of sanctions)



      MDEC Procurement K11-0030-29                                                                                    September 1, 2010
                                                   MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                        ATTACHMENT C
                                                     MARYLAND ELECTRONIC COURT PROCUREMENT                              Page 151 of 249
                                                            FUNCTIONAL REQUIREMENTS

                                                                            ACCOUNTING

    ID                                   Requirement Text                                             Response Code   Comments
ACC-135.03       Provide USER with the ability to invoke rule to set/identify suspended           0
                 FINES/COSTS for CASE/PARTY (e.g.. Incarceration, in lieu of sanctions).
ACC-135.04       Provide USER with the ability to produce report for suspended                    0
                 FINES/COSTS for CASE/PARTY (e.g.. Incarceration, in lieu of sanctions).
ACC-136      Provide the ability to view and print all adjustments made to the defendant
             account (accounts receivable).
ACC-136.01       Provide ADMIN USER with the ability to define fields for querying                0
                 ADJUSTMENT records for PARTY ACCOUNT.
ACC-136.02       Provide ADMIN USER with the ability to define report for ADJUSTMENT              0
                 records for PARTY ACCOUNT.
ACC-136.03       Provide USER with the ability to search for ADJUSTMENT records for               0
                 PARTY ACCOUNT.
ACC-136.04       Provide USER with the ability to produce report for ADJUSTMENT records           0
                 for PARTY ACCOUNT.
ACC-137      Provide the ability to view the costs in unapplied cash amounts under various
             parameters based on local business rules.
ACC-137.01       Provide ADMIN USER with the ability to define fields for querying COSTS          0
                 on CASE that have not been satisfied.
ACC-137.02       Provide USER with the ability to search for COSTS on CASE that have not          0
                 been satisfied.
ACC-138        Provide the ability to send or resend a case participant account to collections.

ACC-138.01        Provide ADMIN USER with the ability to define rule to send CASE/PARTY           0
                  ACCOUNT to collection.
ACC-138.02        Provide ADMIN USER with the ability to define rule to re-send                   0
                  CASE/PARTY ACCOUNT to collection.
ACC-138.03        Provide USER with the ability to invoke rule to send CASE/PARTY                 0
                  ACCOUNT to collection.
ACC-138.04        Provide USER with the ability to invoke rule to re-send CASE/PARTY              0
                  ACCOUNT to collection.
ACC-139      Ability to view all cases for the case participant that are in collection.
ACC-139.01        Provide ADMIN USER with the ability to define fields for querying CASE          0
                  records referred to collection for a PARTY.
ACC-139.02        Provide USER with the ability to search CASE records referred to collection     0
                  for a PARTY.


      MDEC Procurement K11-0030-29                                                                                     September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                        ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                              Page 152 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                            ACCOUNTING

    ID                                         Requirement Text                                      Response Code   Comments
ACC-140      Ability to look up case participant collection information (e.g., collection case
             number, court case number and defendant name).
ACC-140.01        Provide ADMIN USER with the ability to define fields for querying PARTY        0
                  ACCOUNT information referred to collection ( e.g.. Case number, Nam
                  etc).
ACC-140.02        Provide USER with the ability to search PARTY ACCOUNT information              0
                  referred to collection ( e.g.. Case number, Nam etc).
ACC-141      View collection activity statistics based on date range.
ACC-141.01        AUTOMATICALLY provide collection statistics.                                   0
ACC-141.02        Provide ADMIN USER with the ability to define fields for querying collection   0
                  statistics.
ACC-141.03        Provide USER with the ability to search for Collection statistics.             0
ACC-142      Provide the ability to record (e.g., update docket and/or financial records) that
             an account is being worked on by outside collection agency.
ACC-142.01        AUTOMATICALLY provide indicator to CASE/PARTY record, DOCKET                   0
                  that ACCOUNT is referred to Collection Agency.
ACC-142.02        Provide ADMIN USER with the ability to define indicator to CASE/PARTY          0
                  record, DOCKET that ACCOUNT is referred to Collection Agency.

ACC-142.03       Provide USER with the ability to assign indicator to CASE/PARTY record,    0
                 DOCKET that ACCOUNT is referred to Collection Agency.
ACC-143      Accounts in a collection hold or outside collection status will be indicated
             visually on reports and on inquiry functions as being in collections.
ACC-143.01       AUTOMATICALLY provide indicator on Reports/Inquiry if CASE/PARTY           0
                 ACCOUNT is referred to collection.
ACC-143.02       Provide ADMIN USER with the ability to define indicator on Reports/Inquiry 0
                 if CASE/PARTY ACCOUNT is referred to collection.
ACC-144      Support recall of accounts in a collection status.
ACC-144.01       Provide ADMIN USER with the ability to define rule to recall CASE/PARTY         0
                 ACCOUNT from collection status.
ACC-144.02       Provide USER with the ability to invoke rule to recall CASE/PARTY               0
                 ACCOUNT from collection status.
ACC-144.03       Provide USER with the ability to override rule to recall CASE/PARTY             0
                 ACCOUNT from collection status.




      MDEC Procurement K11-0030-29                                                                                    September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                        ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                              Page 153 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                           ACCOUNTING

    ID                                         Requirement Text                                      Response Code   Comments
ACC-145      Provide the ability to make payment adjustments made to cases based on
             collection activity (e.g., record amount collected and charge balance to
             collection fee per local rules).
ACC-145.01        Provide ADMIN USER with the ability to define rule to process adjustment       0
                  on PAYMENTS made on COLLECTION ACCOUNTS. (e.g.. record amount
                  collected and charge balance to collection fee)
ACC-145.02        Provide USER with the ability to invoke rule to process adjustment on          0
                  PAYMENTS made on COLLECTION ACCOUNTS. (e.g.. record amount
                  collected and charge balance to collection fee)
ACC-145.03        Provide USER with the ability to override rule to process adjustment on        0
                  PAYMENTS made on COLLECTION ACCOUNTS. (e.g.. record amount
                  collected and charge balance to collection fee)
ACC-146      Ability to close a collection account when the file is closed by locally defined
             business rules.
ACC-146.01        AUTOMATICALLY assign indicator when Collection account is closed.              0
ACC-146.02        Provide ADMIN USER with the ability to define indicator when Collection        0
                  account is closed.
ACC-146.03        Provide USER with the ability to assign indicator when collection account is   0
                  closed.
ACC-147      System AUTOMATICALLY moves customer accounts into collection based on
             locally defined parameters.
ACC-147.01        AUTOMATICALLY refer CASE/PARTY ACCOUNT to collection based on a                0
                  rule.
ACC-147.02        Provide ADMIN USER with the ability to define rule to refer CASE/PARTY         0
                  ACCOUNT to collection AUTOMATICALLY.
ACC-147.03        Provide USER with the ability to invoke rule to refer CASE/PARTY               0
                  ACCOUNT to collection AUTOMATICALLY.
ACC-147.04        Provide USER with the ability to override rule to refer CASE/PARTY             0
                  ACCOUNT to collection AUTOMATICALLY.
ACC-148      Provide the ability to accept and enter payments for cases which are in
             collection based on locally-defined business rules.
ACC-148.01        Provide ADMIN USER with the ability to define rule to process PAYMENT          0
                  for COLLECTION ACCOUNT (e.g.. Accept payment at COURT).

ACC-148.02       Provide USER with the ability to invoke rule to process PAYMENT for             0
                 COLLECTION ACCOUNT (e.g.. Accept payment at COURT).


      MDEC Procurement K11-0030-29                                                                                    September 1, 2010
                                                    MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                         ATTACHMENT C
                                                      MARYLAND ELECTRONIC COURT PROCUREMENT                               Page 154 of 249
                                                             FUNCTIONAL REQUIREMENTS

                                                                               ACCOUNTING

    ID                                           Requirement Text                                       Response Code   Comments
ACC-148.03        Provide USER with the ability to override rule to process PAYMENT for             0
                  COLLECTION ACCOUNT (e.g.. Accept payment at COURT).
ACC-149      Ability to enter a civil lien (e.g., public defender lien and civil money judgment).
ACC-148.01        Provide USER the ability to enter a civil lien.                                   0
ACC-150      Allow a USER to refund and track overpayments; exonerate; reinstate; waive;
             and forfeit total or partial payments posted to trust funds, bonds or cash bail at
             any point in the accounting period.
ACC-150.01        Provide ADMIN USER with the ability to define rule to process FINANCIAL           0
                  Adjustments (e.g.. Refund, Overpayment, Waive, Forfeit) to Trust Funds,
                  Bonds or Cash Bail.
ACC-150.02        Provide USER with the ability to invoke rule to process FINANCIAL                 0
                  Adjustments (e.g.. Refund, Overpayment, Waive, Forfeit) to Trust Funds,
                  Bonds or Cash Bail.
ACC-150.03        Provide USER with the ability to override rule to process FINANCIAL               0
                  Adjustments (e.g.. Refund, Overpayment, Waive, Forfeit) to Trust Funds,
                  Bonds or Cash Bail.
ACC-151      Ability to track bail and property bonds, including the ability to produce an aging
             report.
ACC-151.01        Provide ADMIN USER with the ability to define fields for querying                 0
                  BAIL/BOND for CASE Records.
ACC-151.02        Provide USER with the ability to search for BAIL/BOND for CASE Records.           0

ACC-152      Ability to transmit accounting records to and receive from the city/county/state
             financial application based on local rules.
ACC-152.01        INTERFACE with City/County/State APPLICATIONS to provide CASE               0
                  Accounting Data.
ACC-153      Ability to generate remittance documents for the state agencies, local agencies,
             and special districts (e.g., amount collected for each code section; total
             remittance; deposit period; and date) based on locally defined parameters.
ACC-153.01        AUTOMATICALLY generate REMITTANCE documents (Total Remittance, 0
                  Period, Date, Amount by Account Code) for Agencies (State, Local,
                  Special District)
ACC-153.02        Provide ADMIN USER with the ability to define REMITTANCE documents 0
                  (Total Remittance, Period, Date, Amount by Account Code) for Agencies
                  (State, Local, Special District)


      MDEC Procurement K11-0030-29                                                                                       September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                       ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 155 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                           ACCOUNTING

    ID                                         Requirement Text                                     Response Code   Comments
ACC-153.03        Provide USER wit the ability to produce REMITTANCE documents (Total           0
                  Remittance, Period, Date, Amount by Account Code) for Agencies (State,
                  Local, Special District)
ACC-154      Ability to AUTOMATICALLY identify traffic cases eligible for amnesty and
             calculate the amount due according to locally-defined business rules.
ACC-154.01        AUTOMATICALLY identify traffic cases elibible for amnesty and calculate       0
                  the amount due according to locally-defined business rules.
ACC-155      Ability for the system to AUTOMATICALLY apply a prepaid deposit (e.g. bond
             forfeiture, escrow for district court appeals) to the appropriate case once the
             judgment has been issued.
ACC-155.01        AUTOMATICALLY process PREPAID DEPOSIT (e.g.. Bond Forfeiture,                 0
                  Dist. Court Appeal Escrow) to CASE costs/Fines on CASE JUDGMENT.
ACC-155.02        Provide ADMIN USER with the ability to define rule to process PREPAID         0
                  DEPOSIT (e.g.. Bond Forfeiture, Dist. Court Appeal Escrow) to CASE
                  costs/Fines on CASE JUDGMENT.
ACC-155.03        Provide USER with the ability to invoke rule to process PREPAID               0
                  DEPOSIT (e.g.. Bond Forfeiture, Dist. Court Appeal Escrow) to CASE
                  costs/Fines on CASE JUDGMENT.
ACC-155.04        Provide USER with the ability to override rule to process PREPAID             0
                  DEPOSIT (e.g.. Bond Forfeiture, Dist. Court Appeal Escrow) to CASE
                  costs/Fines on CASE JUDGMENT.
ACC-156      Ability to enter a request for processing refunds and to print a list of refund
             requests which can be sent to the Finance office for processing.
ACC-156.01        Provide ADMIN USER with the ability to define rule to process Refund          0
                  request for CASE/PARTY ACCOUNT
ACC-156.02        Provide USER with the ability to invoke rule to process Refund request for    0
                  CASE/PARTY ACCOUNT
ACC-156.03        Provide ADMIN USER with the ability to define report to list Refund           0
                  Requests for processing.
ACC-156.04        Provide USER with the ability to produce report to list Refund Requests for   0
                  processing.
ACC-157      Associate payment with proper case and party when monies received. (see
             also Accounting - Bookkeeping Function)
ACC-157.01        AUTOMATICALLY assign PAYMENT to CASE/PARTY records.                           0
ACC-158      Accept full, partial, and installment payments by various methods (e.g., cash,
             check, credit card, fee waiver).


      MDEC Procurement K11-0030-29                                                                                   September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                       ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 156 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                                          ACCOUNTING

    ID                                         Requirement Text                                    Response Code   Comments
ACC-158.01        Provide ADMIN USER with the ability to define rule to process PAYMENTS       0
                  (Full, Partial, Installment) with different METHOD of PAYMENT (e.g.. Cash,
                  Check, Credit Card, Fee Waiver).
ACC-158.02        Provide USER with the ability to invoke rule to process PAYMENTS (Full,      0
                  Partial, Installment) with different METHOD of PAYMENT (e.g.. Cash,
                  Check, Credit Card, Fee Waiver).
ACC-158.03        Provide USER with the ability to override rule to process PAYMENTS (Full,    0
                  Partial, Installment) with different METHOD of PAYMENT (e.g.. Cash,
                  Check, Credit Card, Fee Waiver).
ACC-159      Permit cashier, with proper authority, to override preestablished funds
             distribution priorities.
ACC-159.01        Provide ADMIN USER with the ability to define rule to allow Cashier          0
                  override of preestablished COSTS/FEES/FINES priority.
ACC-159.02        Provide USER with the ability to assign override of preestablished           0
                  COSTS/FEES/FINES priority.
ACC-160      Permit individual cashiers to open and close as needed (e.g., when several
             cashiers work different shifts at same register during same day).
ACC-160.01        AUTOMATICALLY allow Cashiers to Logon and Close registers as needed.         0

ACC-160.02       Provide ADMIN USER with the ability to define rule to allow Cashiers to     0
                 Logon and Close registers as needed.
ACC-160.03       Provide USER with the ability to invoke rule to allow Cashiers to Logon and 0
                 Close registers as needed.
ACC-161      Permit payments to be voided and corresponding adjusting entries to be made
             before daily balancing with proper security provisions. (see also Security
             Function)
ACC-161.01       Provide ADMIN USER with the ability to define rule to allow PAYMENT         0
                 ADJUSTMENT before End-Of-Day (EOD) closing with appropriate security.

ACC-161.02       Provide USER with the ability to assign PAYMENT ADJUSTMENT before             0
                 End-Of-Day (EOD) closing with appropriate security.
ACC-162      Prohibit modification of receipt number sequence and provide audit trail of
             receipt number usage. (see also Security Function)
ACC-162.01       AUTOMATICALLY restrict Receipt number Sequence modification.                  0
ACC-162.02       AUTOMATICALLY assign audit Trail to Receipt Number Usage.                     0
ACC-163      Produce summary reports for each cash drawer, cash register, and cashier.
             (see also Accounting - Receipting Function)

      MDEC Procurement K11-0030-29                                                                                  September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                       ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 157 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                                          ACCOUNTING

    ID                                        Requirement Text                                     Response Code   Comments
ACC-163.01        AUTOMATICALLY assign list of transactions and Total for each DRAWER,         0
                  REGISTER, CASHIER and ACCOUNT CODE.
ACC-163.02        Provide ADMIN USER with the ability to define report for DRAWER,             0
                  REGISTER, CASHIER and ACCOUNT CODE.
ACC-163.03        Provide USER with the ability to produce report for DRAWER, REGISTER,        0
                  CASHIER and ACCOUNT CODE.
ACC-164      Provide integration with financial management systems that support such tasks
             as cash receipting, check disbursement, receivables tracking, and posting of
             collections to the general ledger.
ACC-164.01        INTERFACE with Financial Management Systems (e.g.. Receipting,               0
                  Disbursement, Receivables, General Ledger).
ACC-165      Accept and post on-line payments (e.g., Internet or telephone) and provide the
             ability to track rejected transactions that have associated payments.
ACC-165.01        AUTOMATICALLY process online Payments (Internet, Telephone).                 0
ACC-165.02        Provide ADMIN USER with the ability to define rule to process online         0
                  Payments (Internet, Telephone).
ACC-165.03        Provide USER with the ability to invoke rule to process online Payments      0
                  (Internet, Telephone).
ACC-165.04        Provide ADMIN USER with the ability to define fields for querying rejected   0
                  Online(Internet, Telephone) transactions.
ACC-165.05        Provide USER with the ability to search rejected Online(Internet,            0
                  Telephone) transactions.
ACC-166      Provide distribution of monies collected by the Court according to locally
             defined business rules.
ACC-166.01        Provide ADMIN USER with the ability to define rule for Distribution of       0
                  Funds collected by Court.
ACC-166.02        Provide USER with the ability to invoke rule for Distribution of Funds       0
                  collected by Court.
ACC-166.03        Provide USER with the ability to override rule for Distribution of Funds     0
                  collected by Court.
ACC-167      Allow the receipting and viewing of unidentified payments.

ACC-167.01       Provide ADMIN USER with the ability to define rule to allow RECEIPT of        0
                 unidentified Payments (e.g.. Check in mail that cannot be identified to
                 CASE).



      MDEC Procurement K11-0030-29                                                                                  September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                       ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 158 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                           ACCOUNTING

    ID                                       Requirement Text                                       Response Code   Comments
ACC-167.02       Provide USER with the ability to invoke rule to allow RECEIPT of               0
                 unidentified Payments (e.g.. Check in mail that cannot be identified to
                 CASE).
ACC-167.03       Provide USER with the ability to override rule to allow RECEIPT of             0
                 unidentified Payments (e.g.. Check in mail that cannot be identified to
                 CASE).
ACC-168      Allow the assignment of previously receipted unidentified payments to a
             specific obligation.
ACC-168.01       Provide ADMIN USER with the ability to define rule to associate                0
                 Unidentified Payments (e.g.. Check in mail that cannot be identified to
                 CASE) to specific CASE Costs/Fines.
ACC-168.02       Provide USER with the ability to invoke rule to associate Unidentified         0
                 Payments (e.g.. Check in mail that cannot be identified to CASE) to
                 specific CASE Costs/Fines.
ACC-168.03       Provide USER with the ability to override rule to associate Unidentified       0
                 Payments (e.g.. Check in mail that cannot be identified to CASE) to
                 specific CASE Costs/Fines.
ACC-169      Provide for the accounting of time payments.
ACC-169.01      Provide ADMIN USER with the ability to define rule to assign accounting         0
                for TIME PAYMENTS
ACC-169.02      Provide USER with the ability to assign accounting for TIME PAYMENT.            0
ACC-170      Accept payments by electronic standards (e.g., EFT, XML).

ACC-170.01        Provide ADMIN USER with the ability to define rule to accept PAYMENT by       0
                  Electronic Standards (e.g.. EFT, XML).
ACC-170.02        Provide USER with the ability to invoke rule to accept PAYMENT by             0
                  Electronic Standard (e.g.. EFT, XML).
ACC-170.03        Provide USER with the ability to override rule to accept PAYMENT by           0
                  Electronic Standard (e.g.. EFT, XML).
ACC-171      Provide a process for handling NSF payments based on locally defined
             business rules (e.g., process for creating a docket entry, charge a processing
             fee if applicable, post the current accounting entry and generate an appropriate
             letter to collect the funds).
ACC-171.01        Provide ADMIN USER with the ability to define workflow for NSF payments       0
                  (e.g.. Update Docket, Charge NSF Fee, post Accounting transactions,
                  generate notice to collect fund).


      MDEC Procurement K11-0030-29                                                                                   September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                         ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                               Page 159 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                            ACCOUNTING

    ID                                         Requirement Text                                       Response Code   Comments
ACC-172      AUTOMATICALLY calculates the interest due on judgments and other
             receivables, including bond forfeiture interest.
ACC-172.01        Provide ADMIN USER with the ability to define rule to calculate INTEREST        0
                  (e.g.. Bond Forfeiture).
ACC-172.02        Provide USER with the ability to invoke rule to calculate INTEREST (e.g..       0
                  Bond Forfeiture).
ACC-172.03        Provide USER with the ability to override rule to calculate INTEREST (e.g..     0
                  Bond Forfeiture).
ACC-173      Allow a USER with appropriate security level to correct transactions while
             maintaining an appropriate audit trail.
ACC-173.01        Provide USER with the ability to assign Accounting adjustments with             0
                  proper security.
ACC-173.02        AUTOMATICALLY assign Audit Trail to transactions posted.
ACC-174      Allow adjusting entry to correct a distribution allocation from receipts.
ACC-174.01        Provide USER with the ability to assign Accounting Adjustments to correct       0
                  a RECEIPT distribution Allocation.
ACC-175      All reports should allow reporting by location, date, month to date, year to date,
             county and statewide.
ACC-175.01        AUTOMATICALLY provide for reporting by location, date, month to date,           0
                  year to date, county and statewide.
ACC-175.02        Provide ADMIN USER with the ability to define reports to report by location,    0
                  date, month to date, year to date, county and statewide.
ACC-176      Allow the ability to identify cases with funds being held after a specified period
             (e.g. 3 years) of no activity so that they could be processed as abandoned
             property
ACC-176.01        Provide ADMIN USER with the ability to define field for querying CASE           0
                  records for Funds held by court beyond a certain time (e.g.. 3 years).
ACC-176.02        Provide USER with the ability to search for CASE records for Funds held         0
                  by court beyond a certain time (e.g.. 3 years).
ACC-176.03        Provide ADMIN USER with the ability to define workflow to process Funds         0
                  held by court beyond a certain time (e.g.. 3 years) as Abandoned Property.

ACC-177      Ability to track overages and shortages by cashier.
ACC-177.01        Provide ADMIN USER with the ability to define field for querying    0
                  OVERAGE and SHORTAGE by Cashier.
ACC-177.02        Provide USER with the ability to search for OVERAGE and SHORTAGE by 0
                  Cashier.
      MDEC Procurement K11-0030-29                                                                                     September 1, 2010
                                                   MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                          ATTACHMENT C
                                                     MARYLAND ELECTRONIC COURT PROCUREMENT                                Page 160 of 249
                                                            FUNCTIONAL REQUIREMENTS

                                                                              ACCOUNTING

    ID                                         Requirement Text                                         Response Code   Comments
ACC-178      At case initiation allow for a pre set filing amount or allow for the cost to be set
             manually based on business rules. (e.g. levy in distress)
ACC-178.01        Provide ADMIN USER with the ability to define rule to assess fixed costs at       0
                  CASE Initiation.
ACC-178.02        Provide USER with the ability to invoke rule to assess fixed costs at CASE        0
                  Initiation.
ACC-178.03        Provide USER with the ability to override rule to asses fixed Costs at CASE       0
                  initiation and assess them manually.
ACC-179      Ability to export financial reports to other formats (e.g. excel)
ACC-179.01        AUTOMATICALLY provide the capability to export reports to other formats           0
                  (e.g.. Excel, PDF).
ACC-180      Provide an alert on bond forfeiture cases when the defendant is arrested within
             90 days of issuance of the warrant. Or according to local business rules.
ACC-180.01        Provide ADMIN USER with the ability to define rule to alert when CASE             0
                  DEFENDANT is arrested within 90 days of a Bond forfeiture.
ACC-181      Provide the ability to void invoices with proper security noting the reason for the
             void and provide audit reports.
ACC-181.01        Provide ADMIN USER with the ability to define rule to allow INVOICE to be         0
                  voided with Reason Code and proper security.
ACC-181.02        Provide USER with the ability to invoke rule to allow INVOICE to be voided        0
                  with Reason Code and proper security.
ACC-181.03        Provide USER with the ability to produce Report for AUDIT (e.g.. Void             0
                  Invoice, Void Receipt)
ACC-182      Electronic receipt should print from system after commissioner processes a
             cash bond.
ACC-182.01        AUTOMATICALLY print receipt for cash bonds.                                       0
ACC-183      System should record all bonds processed by a particular commissioner and
             print out a DCA 20 - Commissioner Daily Cash Transmittal upon commissioner
             logging off the system. System can also be programmed to electronically
             transfer a completed DCA 20 to accounting (Return receipt should be required.)
ACC-182.01       AUTOMATICALLY record bonds by commissioner.                                        0
ACC-182.02       Provide USER the ability to print daily cash transmittals.                         0




      MDEC Procurement K11-0030-29                                                                                       September 1, 2010
                                                MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                        ATTACHMENT C
                                                  MARYLAND ELECTRONIC COURT PROCUREMENT                              Page 161 of 249
                                                         FUNCTIONAL REQUIREMENTS

                                                           FILE, DOC, PROPERTY MANAGEMENT

     ID                                    Requirement Text                                        Response Code   Comments
FDP-001      Allow search, retrieval, view, and printing of electronic documents and
             images (e.g., the user should not know or care if the document is imaged
             or created by the court in Microsoft Word; all documents relating to a case
             should show as title of the document and be available for viewing or
             download on demand).
FDP-001.01        Provide ADMIN USER with the ability to define fields for querying            0
                  DOCUMENTS.
FDP-001.02        Provide USER with the ability to search DOCUMENTS images.                    0
FDP-001.03       Provide USER with the ability to select DOCUMENTS for viewing.                0
FDP-001.04       Provide ADMIN USER with the ability to define rules for constructing a        0
                 document title.
FDP-001.05        Provide ADMIN USER with the ability to define fields.                        0
FDP-002      Provide ability to apply electronic signature (e.g., judge‘s signature, clerk‘s
             signature and seal) to a document for all static court documents (e.g.,
             judicial orders) if allowed or required by statute or court rule.
FDP-002.01        Provide ADMIN USER with the ability to define fields that are displayed      0
                  for document search, retrieval and view and printing.
FDP-002.02        Provide ADMIN USER with the ability to define codes for electronic           0
                  signatures for different court personnel.
FDP-002.03        Provide ADMIN USER with the ability to define codes to associate             0
                  DOCUMENTS with electronic signatures.
FDP-002.04        Provide USER with the ability to produce DOCUMENTS containing                0
                  electronic signatures.
FDP-002.05        Provide ADMIN USER with the ability to define rule for electronic            0
                  signatures for different court personnel.
FDP-003      Provide ability to create a digital certificate (i.e. electronic document
             authentication algorithm) for all static court documents (e.g., judicial
             orders) if allowed or required by statute or court rule.
FDP-003.01        Provide ADMIN USER with the ability to define fields that are displayed      0
                  in the DIGITAL CERTIFICATE.
FDP-003.02        Provide USER with the ability to produce DOCUMENTS containing a              0
                  DIGITAL CERTIFICATE.
FDP-003.03        Provide ADMIN USER with the ability to define codes for creating             0
                  DIGITAL Certificate.
FDP-003.04        Provide ADMIN USER with the ability to define fields for querying            0
                  DIGITAL CERTIFICATE.

     MDEC Procurement K11-0030-29                                                                                    September 1, 2010
                                              MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                MARYLAND ELECTRONIC COURT PROCUREMENT                            Page 162 of 249
                                                       FUNCTIONAL REQUIREMENTS

                                                         FILE, DOC, PROPERTY MANAGEMENT

     ID                                  Requirement Text                                      Response Code   Comments
FDP-003.05       Provide ADMIN USER with the ability to define business rules for          0
                 creating DIGITAL Certificate.
FDP-004      Create and maintain electronic documents or content (e.g. video, audio,
             graphical).
FDP-004.01       Provide ADMIN USER with the ability to define codes for                   0
                 DOCUMENT/DIGITAL CONTENT (e.g. video, audio, graphical) types.
FDP-004.02       Provide ADMIN USER with the ability to define fields for querying         0
                 DOCUMENTS/DIGITAL CONTENT records.
FDP-004.03       Provide ADMIN USER with the ability to define fields that are displayed   0
                 for DOCUMENT/DIGITAL CONTENT search results.
FDP-004.04       Provide USER with the ability to search DOCUMENT/DIGITAL                  0
                 CONTENT indices.
FDP-005      Support expungements (including partial expungements) when so ordered.
FDP-005.01       Provide ADMIN USER with the ability to define rule for designating a      0
                 CASE as expunged.
FDP-005.02       Provide ADMIN USER with the ability to define workflow for expunging      0
                 a CASE.
FDP-005.03       Provide USER with the ability to assign an indicator to CASE when the     0
                 case is expunged.
FDP-005.04       Provide USER with the ability to assign an indicator to CHARGE when       0
                 only the charge is expunged (e.g. partial expungements).
FDP-005.05       Provide ADMIN USER with the ability to define fields for querying         0
                 CASE/DOCUMENT/PARTY records that excludes cases that are
                 expunged.
FDP-005.06       AUTOMATICALLY alert USER when accessing an expunged case                  0
                 that the case is not found.
FDP-006      Ensure that data necessary for statistical records is not expunged with
             case.
FDP-006.01       Provide ADMIN USER with the ability to define fields that are displayed 0
                 for expunged CASES.
FDP-007      Allow expunged cases to be re-opened.
FDP-007.01       Provide ADMIN USER with the ability to define workflow for un-            0
                 expunging a case.
FDP-008      Allow partial expungements.


     MDEC Procurement K11-0030-29                                                                                September 1, 2010
                                                MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                  MARYLAND ELECTRONIC COURT PROCUREMENT                            Page 163 of 249
                                                         FUNCTIONAL REQUIREMENTS

                                                          FILE, DOC, PROPERTY MANAGEMENT

     ID                                   Requirement Text                                       Response Code   Comments
FDP-008.01       Provide ADMIN USER with the ability to assign an indicator to         0
                 EXPUNGED CHARGE when only the charge is expunged.
FDP-008.02       Provide ADMIN USER with the ability to define codes to associate with 0
                 the EXPUNGED CHARGE.
FDP-009      Enable users to secure documents if they should not be viewable to users
             outside the court the case is being heard.
FDP-009.01       Provide ADMIN USER with the ability to define codes for DOCUMENT            0
                 security types.
FDP-009.02       Provide ADMIN USER with the ability to define rule for displaying           0
                 DOCUMENTs[secured].
FDP-009.03       Provide USER with the ability to assign one to many document security       0
                 type to DOCUMENT when the document is secure.
FDP-010      Provide the ability to generate forms, notices, and fillable forms, populate
             forms with database information, and view created forms prior to printing or
             docketing.
FDP-010.01       Provide ADMIN USER with the ability to define rules for DOCUMENT            0
                 templates.
FDP-010.02       Provide USER with the ability to produce DOCUMENTS containing               0
                 information from the database.
FDP-010.03       Provide ADMIN USER with the ability to define rules for preview of          0
                 DOCUMENTS before printing.
FDP-011      Enable users to print forms, notices, and orders, and key in events in the
             courtroom or in the office.
FDP-011.01       Provide ADMIN USER with the ability to define rules for DOCUMENT            0
                 templates.
FDP-011.02       Provide USER with the ability to produce DOCUMENTS containing               0
                 information from the database in the courtroom or in the office.
FDP-011.03       Provide ADMIN USER with the ability to define rules for preview of          0
                 DOCUMENTS before printing.
FDP-012      The case management system should provide the ability to handle the
             transfer and disposition to Circuit Court of multiple charge cases to all for
             the disposition of the ―orphaned‖ cases/charges that may be left behind
             when the SAO does not NP or stet the charge(s) they do not want to
             pursue at that time.
FDP-012.01       Provide ADMIN USER with the ability to define rules for transferring        0
                 cases from one court type to another.

     MDEC Procurement K11-0030-29                                                                                  September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                            Page 164 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                            FILE, DOC, PROPERTY MANAGEMENT

     ID                                      Requirement Text                                     Response Code   Comments
FDP-012.02        Provide ADMIN USER with the ability to define workflow for                  0
                  transferring CHARGE/ISSUE/RELIEF to another court type,
                  CHARGE/ISSUE/RELIEF transferred may or may not create a new
                  CASE in the receiving court, not all CHARGE/ISSUE/RELIEF in the
                  sending case may
FDP-012.03        Provide USER with the ability to assign CASE to Court Locations.            0
FDP-012.04        Provide USER with the ability to assign one or many                         0
                  CHARGE/ISSUE/RELIEF to a Court Location.
FDP-013      Maintain and print or display audit trail of each case file location with
             information for file tracking, in addition to length of time file checked out.

FDP-013.01       Provide USER with the ability assign an indicator to CASE indicating         0
                 that a paper file exist.
FDP-013.02       Provide USER with the ability to assign a unique identifier to each          0
                 CASE FILE FOLDER volume.
FDP-013.03       Provide USER with the ability to assign volume number, location, date        0
                 checked in, date checked out to each CASE FILE FOLDER.
FDP-013.04       Provide USER with the ability to search CASE FILE FOLDER records.            0

FDP-013.05       Provide ADMIN USER with the ability to define codes for CASE FILE            0
                 FOLDER locations.
FDP-013.06       Provide ADMIN USER with the ability to define fields to display for          0
                 CASE FILE FOLDER.
FDP-014      Print or display list of filings while manual file checked out so that
             documents can be added to file when it is returned.
FDP-014.01       Provide ADMIN USER with the ability to define an indicator to FILING         0
                 when the manual file is checked out.
FDP-014.02       Provide USER with the ability to assign indicator to FILING when             0
                 manual file is checked out.
FDP-015      Display information on system and equipment (e.g., printer jams in the
             middle of batch printing but system says that notices have been printed)
             malfunctions if information in case processing system. Allow option to
             reprint documents when printing malfunctions.
FDP-015.01       AUTOMATICALLY alert USER on the status of printer connected to               0
                 workstation.
FDP-015.02       Provide the USER with the ability to produce DOCUMENT[all] for               0
                 reprinting.
     MDEC Procurement K11-0030-29                                                                                   September 1, 2010
                                                MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                        ATTACHMENT C
                                                  MARYLAND ELECTRONIC COURT PROCUREMENT                              Page 165 of 249
                                                         FUNCTIONAL REQUIREMENTS

                                                           FILE, DOC, PROPERTY MANAGEMENT

     ID                                    Requirement Text                                        Response Code   Comments
FDP-016      Track location and status of exhibits and other property through each
             borrower (including those external to courts) until returned to clerk‘s office
             relative to location, borrower identifier and other information, identifier and
             total number of similar exhibits or property (e.g., pay stub one of five), date
             removed, reason needed, date returned or transferred, and other data.
FDP-016.01        Provide ADMIN USER with the ability to define codes for borrower,      0
                  location, type of EXHIBITS.
FDP-016.02        Provide USER with the ability to assign borrower, location, type, date 0
                  removed, reason removed, date returned, date transferred, description
                  to EXHIBITS.
FDP-017      Record return, release, or destruction of exhibits and other property,
             including person who received the property.

FDP-017.01       Provide USER with the ability to assign return date, release date,           0
                 destruction date, person released to for EXHIBITS.
FDP-018      Track and print or display court orders pertaining to each exhibit or
             property, including the ability to print a single order for multiple exhibits or
             property items..
FDP-018.01       Provide USER with the ability to produce DOCUMENT[Exhibits orders] 0
                 for one or many EXHIBITS.
FDP-019      Generate labels for manual case files, including bar codes.
FDP-019.01        Provide USER with the ability to produce DOCUMENT[Case label]                0
                  including bar codes.
FDP-019.02        Provide ADMIN USER with the ability to define fields that should be          0
                  displayed as bar codes.
FDP-020      Generate indicators (e.g., color coded labels or reference cards) with
             information on checked-out manual files to replace those files in cabinet.
FDP-020.01       Provide ADMIN USER with the ability to produce DOCUMENT[case                  0
                 reference cards] when a file has been removed.
FDP-021      Track manual case files from time checked out of clerk‘s office through
             each borrower until returned to clerk‘s office relative to location, borrower,
             date removed, reason file needed, date returned or transferred, and other
             data.
FDP-020.01       Provide USER with the ability to assign paper file "check out" details:       0
                 location, borrower, date removed, reason needed, date returned, date
                 transferred and other data

     MDEC Procurement K11-0030-29                                                                                    September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                        ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                              Page 166 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                            FILE, DOC, PROPERTY MANAGEMENT

     ID                                   Requirement Text                                          Response Code   Comments
FDP-020.02       Provide USER the ability to track a case file checked out until it is          0
                 check back in.
FDP-022      Maintain location (e.g. storage facility, location in facility, reel number, and
             location on reel) for manual and electronic archived files.
FDP-022.01      Provide USER with the ability to assign location to CASE FILE                   0
                FOLDER.
FDP-022.02      Provide ADMIN USER with the ability to define codes for CASE FILE               0
                FOLDER locations.
FDP-023      Maintain last location of manual and electronic destroyed files.
FDP-023.01       Provide USER with the ability to assign location to CASE FILE                  0
                 FOLDER.
FDP-023.02       Provide ADMIN USER with the ability to define codes for CASE FILE              0
                 FOLDER locations.
FDP-024      Identify cases to be retained permanently
FDP-024.01       Provide USER with the ability to assign an indicator to CASE to flag           0
                 that it must be permanently retained.
FDP-025      Process files according to local and state rules for becoming archived,
             destroyed, or transferred to storage facility.
FDP-025.01       Provide ADMIN USER with the ability to define rule for CASE                    0
                 destruction, archival and transfer to storage.
FDP-026      Generate and maintain or print reports showing archived and destroyed or
             transferred cases.
FDP-026.01        Provide USER with the ability to produce report of CASE[archived].            0
FDP-026.02        Provide ADMIN USER with the ability to define fields to display for           0
                  CASE[archived].
FDP-027      Perform utility functions (e.g., copy information such as docket entries and
             parties) from one case to another.
FDP-027.01       Provide ADMIN USER with the ability to define rule for                         0
                 /PARTY/FILINGS copying from one CASE to one or many CASEs.
FDP-028      Provide capability to toggle between views of several different documents.
FDP-028.01       Provide USER with the ability to view one or many DOCUMENTS at                 0
                 one time or to allow for toggling between them.




     MDEC Procurement K11-0030-29                                                                                     September 1, 2010
                                               MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                       ATTACHMENT C
                                                 MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 167 of 249
                                                        FUNCTIONAL REQUIREMENTS

                                                          FILE, DOC, PROPERTY MANAGEMENT

     ID                                    Requirement Text                                      Response Code   Comments
FDP-029      Provide capability to interface with electronic content management system
             that is separate from case processing if case processing system excludes
             document management capabilities.
FDP-029.01        INTERFACE to Electronic Content Management.                          0
FDP-030      Provide capability to use same document management system for imaging
             if imaging is included in overall case processing.
FDP-030.01      Provide USER with the ability to assign DOCUMENT images as part of 0
                the case management system.
FDP-031      Support maintenance of electronic or imaged documents (e.g., to produce
             documents that include parts of several electronic or imaged documents).
FDP-031.01        Provide USER with the ability to search for DOCUMENT images.               0
FDP-031.02        Provide USER with the ability to sort for DOCUMENT images.                 0
FDP-032      Record receipt of exhibits and other property (including party submitting,
             exhibit or property description, exhibit or property status such as submitted
             into evidence), generate tag for exhibits and other property, relate to
             specific case, generate receipts.
FDP-032.01        Provide USER with the ability to assign receipt date to EXHIBITS.          0
FDP-032.02        Provide ADMIN USER with the ability to define reports for EXHIBITS.        0
FDP-032.03        Provide USER with the ability to generate DOCUMENT [exhibit tag,           0
                  receipt].
FDP-033      Generate exhibit and property numbers or other identifiers.
FDP-033.01      Provide USER with the ability to assign unique identifier to EXHIBITS. 0
FDP-034      Generate automated notices (1) to reclaim exhibit or property when court‘s
             usage completed and (2) to inform owner that exhibit or property destroyed.
FDP-034.01       Provide USER with the ability to produce DOCUMENT[notices] for              0
                 EXHIBITS when court cases is complete and when EXHIBIT has been
                 destroyed.
FDP-035      Print or display lists of exhibits and other property according to case, party,
             and other parameters.
FDP-035.01       Provide ADMIN USER with the ability to define fields to display for         0
                 EXHIBITS.
FDP-035.02       Provide USER with the ability to search EXHIBITS.                           0
FDP-035.03       Provide USER with the ability to sort for EXHIBITS by CASE,PARTY            0
                 and other parameters.

     MDEC Procurement K11-0030-29                                                                                  September 1, 2010
                                                MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                        ATTACHMENT C
                                                  MARYLAND ELECTRONIC COURT PROCUREMENT                              Page 168 of 249
                                                         FUNCTIONAL REQUIREMENTS

                                                          FILE, DOC, PROPERTY MANAGEMENT

     ID                                    Requirement Text                                        Response Code   Comments
FDP-036      Generate indicators (e.g. color coded labels) to indicate restricted-access
             files (e.g. psychological evaluations) on hard-copy files.
FDP-036.01        Provide ADMIN USER with the ability to define codes for CASE access          0
                  restrictions.
FDP-036.02        Provide USER with the ability to assign access restrictions to CASE.         0
FDP-037      Provide ability to track multi-volume files.
FDP-037.01        Provide USER with the ability to assign location to CASE FILE                0
                  FOLDER volumes individually.
FDP-038      Provide alert capability for hard-copy files or physical property reported lost
             (e.g. alert to screen of terminal accessing associated electronic file).
FDP-038.01        AUTOMATICALLY alert USER when CASE FILE FOLDER is lost.                      0
FDP-039      Retain information from inactive, archived, destroyed, or purged cases or a
             defendant as needed for related cases and a defendant that remain active
             and to retain summary information based on local rules (e.g. indexes) on
             active or inactive files. (see Docketing and Related Record Keeping
             Function)
FDP-039.01        Provide ADMIN USER with the ability to define rule concerning data           0
                  elements that should still display for cases that are archived, destroyed
                  or purged.
FDP-040      Interface with Docketing and Related Record Keeping Function to update
             records of cases and a defendant related to cases transferred to inactive,
             archived, destroyed, or purged status. (see Docketing and Related Record
             Keeping Function)
FDP-040.01        AUTOMATICALLY update the CASE docket when cases are made                     0
                  inactive, archived, destroyed or purged.
FDP-041      Allow for merge and unmerge of files containing information on same
             defendant or case participant. Permit the party to maintain their same
             unique identifier even after the merge. (e.g. commissioner and police
             officer both file charges).
FDP-041.01        Provide USER with the ability to assign one case number to multiple          0
                  cases in order to merge or unmerge them for future updates.
FDP-041.02        Provide USER with the ability to select the unique identifiers after         0
                  merge.
FDP-042      Provide the ability to display an alert when merge and unmerge of files will
             affect multiple records.


     MDEC Procurement K11-0030-29                                                                                    September 1, 2010
                                              MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                     ATTACHMENT C
                                                MARYLAND ELECTRONIC COURT PROCUREMENT                           Page 169 of 249
                                                       FUNCTIONAL REQUIREMENTS

                                                        FILE, DOC, PROPERTY MANAGEMENT

     ID                                   Requirement Text                                    Response Code   Comments
FDP-042.01      AUTOMATICALLY prompt USER regarding records that will be                  0
                affected by merging and unmerging of CASE/PARTY records.
FDP-043      Support input, output, storage (including indexing or an equivalent
             capability), and search and retrieval of electronic and imaged documents.
FDP-043.01       Provide USER with the ability to search for DOCUMENT images.             0
FDP-043.02       Provide USER with the ability to sort for DOCUMENT images.               0
FDP-044      Provide equivalent security for contents of electronic content management
             system, as it exists elsewhere in the case processing system. (see
             Security and Data Integrity Function)
FDP-044.01       Provide ADMIN USER with the ability to define rules for access to        0
                 electronic content.
FDP-045      Provide ability to save, store, and output any document produced by the
             system without requiring the data to be reprocessed.

FDP-045.01       Provide USER with the ability to search for past DOCUMENTs without       0
                 recreating.
FDP-046      Provide ability to reference and track all exhibits when associated with
             multiple cases.

FDP-046.01       Provide USER with the ability to assign one of more EXHIBITS to one      0
                 or more CASES or GROUPS of CASES.
FDP-047      Permit override of system-supplied data on archival, destruction, and
             transfer dates with supervisor approval.

FDP-047.01       Provide USER with the ability to override EXHIBIT and CASE archival,     0
                 destruction and transfer dates.
FDP-048      Identify summary information (e.g., indexes, key elements of case history)
             to be retained in active or semi-active files and documents.

FDP-048.01       Provide ADMIN USER with the ability to define rule concerning data     0
                 elements that should still display for cases that are made inactive.
FDP-049      Permit access to inactive and archived files and documents for information
             and to restore to active status.

FDP-049.01       Provide ADMIN USER with the ability to define rules for access to        0
                 inactive CASES/DOCUMENTS.


     MDEC Procurement K11-0030-29                                                                               September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                            ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                                  Page 170 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                              FILE, DOC, PROPERTY MANAGEMENT

     ID                                Requirement Text                                                  Response Code   Comments
FDP-049.02       Provide USER with the ability to assign Case Archival Status to CASE. 0
FDP-050      Display any printed output, print any screen display, and print any
             document individually or in a group, immediately or at a scheduled time.
FDP-050.01       Provide USER with the ability to print DOCUMENT individually or in    0
                 batches.
FDP-050.02       Provide USER with the ability to print DOCUMENT immediately or at a 0
                 scheduled time.
FDP-051      Maintain and output index of manual paper documents as part of a table of
             contents or case history.
FDP-051.01      Provide USER with the ability to produce Report of                                   0
                DOCUMENTS[manual and electronic].
FDP-052      Create any output periodically when scheduled or on request.
FDP-052.01        Provide USER with the ability to produce report on a schedule or on                0
                  demand.
FDP-053      Support input, output, storage (including indexing or an equivalent
             capability), and search and retrieval of individual and multiple electronic
             and imaged documents based on user-defined criteria (e.g., by case
             number or date range).
FDP-053.01        Provide USER with the ability to search for DOCUMENT images by                     0
                  case number, date range, party, other criteria.
FDP-053.02        Provide ADMIN USER with the ability to define fields for querying                  0
                  DOCUMENT images.
FDP-054      Support retrieval of specific document directly from other parts of system
             (e.g., docket) without intermediate steps (e.g., without scrolling through
             document list to select given document).
FDP-054.01        Provide USER with the ability to select SPECIFIC DOCUMENTS with                    0
                  minimal steps.
FDP-054.02        Provide ADMIN USER with the ability to define field(s) for querying for            0
                  SPECIFIC DOCUMENTS.
FDP-055      Record if and when exhibit or property admitted into evidence.
FDP-055.01        Provide USER with the ability to assign an indicator to EXHIBIT when it            0
                  is admitted into evidence.
FDP-056      Identify location (e.g. storage facility, location in facility) for paper files (e.g.
             ,details about case storage box, including box number, data and box code;
             re-evaluate case information and set a new box date).


     MDEC Procurement K11-0030-29                                                                                          September 1, 2010
                                               MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                 MARYLAND ELECTRONIC COURT PROCUREMENT                            Page 171 of 249
                                                        FUNCTIONAL REQUIREMENTS

                                                          FILE, DOC, PROPERTY MANAGEMENT

     ID                                    Requirement Text                                     Response Code   Comments
FDP-056.01       Provide ADMIN USER with the ability to define codes for location of      0
                 CASE FILE FOLDER.
FDP-056.02       Provide USER with the ability to assign case storage box number, box 0
                 code to CASE FILE FOLDER.
FDP-057      View and print list of cases which are to be moved to off-site storage based
             on user defined parameters.
FDP-057.01       Provide ADMIN USER with the ability to define rule to determine cases 0
                 that should be moved to off-site storage.
FDP-057.02       Provide USER with the ability to produce report of CASES that should 0
                 be moved to off-site storage.
FDP-058      Create a docket entry when a case is archived, destroyed, or purged.
FDP-058.01       AUTOMATICALLY update the CASE docket when cases are made              0
                 inactive, archived, destroyed or purged.
FDP-059      Remove documents from case file when decision has been vacated, with
             audit log and maintenance of historical data.
FDP-059.01       AUTOMATICALLY maintain history of DOCUMENT.                                0
FDP-059.02       Provide ADMIN USER with the ability to define rule for removing            0
                 DOCUMENTS from CASE.
FDP-060      Tag order as being vacated (status), with ability to change back if order is
             reinstated.
FDP-060.01       Provide ADMIN USER with the ability to define codes for                    0
                 DOCUMENTS[order] status.
FDP-060.02       Provide USER with the ability to assign DOCUMENT[order] status.            0




     MDEC Procurement K11-0030-29                                                                                 September 1, 2010
                                               MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                         ATTACHMENT C
                                                 MARYLAND ELECTRONIC COURT PROCUREMENT                               Page 172 of 249
                                                        FUNCTIONAL REQUIREMENTS

                                                            CASE MANAGEMENT NAVIGATION

     ID                                     Requirement Text                                      Response Code   Comments
CMN-001      Provide the ability to designate which cases need to be seen by court
             intervention program (e.g., DWI/Drug Court, pretrial diversion).
CMN-001.01        Provide USER with the ability to assign an indicator to a CASE that         0
                  needs to be seen by court intervention program.
CMN-001.02        Provide USER with the ability to easily select a PERSON when                0
                  assigning associations.
CMN-001.03        Provide ADMIN USER with the ability to define a rule to determine           0
                  what CASES need to be seen by court intervention program.
CMN-002      Provide ability to reclassify cases, maintaining classification history (e.g.,
             change case type).
CMN-002.01        Provide USER with the ability to assign a different case type to an         0
                  existing CASE.
CMN-002.02        Automatically maintain history of case type changes to an existing          0
                  CASE.
CMN-003      Allow the user to change to which court location the case is assigned,
             maintaining history of assignment.
CMN-003.01        Provide USER with the ability to assign a different court location to an    0
                  existing CASE.
CMN-003.02        Automatically maintain history of Court Location changes to an existing     0
                  CASE.
CMN-004      Support the entry of an unlimited number of staff viewable notes regarding
             a case, which can be viewed by other staff with appropriate security.

CMN-004.01       Provide USER with the ability to assign an unlimited number of notes         0
                 to a CASE.
CMN-004.02       Provide USERS with the ability to view notes regarding a CASE that           0
                 are produced by other USERS, with appropriate security.
CMN-005      Provide ability to cross-reference cases (e.g., accommodate multiple
             external case numbers or tracking codes assigned to a case).
CMN-005.01       Provide USER with the ability to assign multiple external case numbers       0
                 to a CASE.
CMN-005.02       Provide USER with the ability to assign multiple tracking codes to a         0
                 CASE.
CMN-005.03       Provide USER with the ability to assign multiple other types external        0
                 identifiers to a CASE.
CMN-005.04       Provide ADMIN USER with the ability to define different types of             0
                 identifiers for a CASE.

     MDEC Procurement K11-0030-29                                                                                   September 1, 2010
                                               MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                        ATTACHMENT C
                                                 MARYLAND ELECTRONIC COURT PROCUREMENT                              Page 173 of 249
                                                        FUNCTIONAL REQUIREMENTS

                                                            CASE MANAGEMENT NAVIGATION

     ID                                    Requirement Text                                      Response Code   Comments
CMN-006      Capture multiple sets of demographic, descriptive, or informational data on
             the same person or business (e.g., one person may use two or more
             Social Security numbers, Dates of Birth, Names, Drivers License Numbers
             or Sets of Address Data or a business may have both a legal name and a
             trade name).
CMN-006.01         Provide USER with the ability to assign multiple Social Security          0
                   numbers for the same PERSON or BUSINESS.
CMN-006.02         Provide USER with the ability to assign multiple Dates of Birth for the   0
                   same PERSON or BUSINESS.
CMN-006.03         Provide USER with the ability to assign multiple Names for the same       0
                   PERSON or BUSINESS.
CMN-006.04         Provide USER with the ability to assign multiple Drivers License          0
                   Numbers for the same PERSON or BUSINESS.
CMN-006.05         Provide USER with the ability to assign multiple sets of address data     0
                   for the same PERSON or BUSINESS.
CMN-006.06         Provide USER with the ability to assign multiple business names for       0
                   the same PERSON or BUSINESS.
CMN-006.07         Provide USER with the ability to assign multiple sets of demographic      0
                   data on the same PERSON or BUSINESS.
CMN-006.08         Provide USER with the ability to assign multiple sets of descriptive      0
                   data on the same PERSON or BUSINESS.
CMN-006.09         Provide USER with the ability to assign multiple sets of informational    0
                   data on the same PERSON or BUSINESS.
CMN-007      Ability to match potential duplicates (e.g., last name, first name, middle
             initial, DOB, SSN, and race) and merge the records once it is verified.
CMN-007.01         Automatically search for potential duplicates when entering new           0
                   PARTY information.
CMN-007.02         Provide ADMIN USER with the ability to define a rule that evaluates       0
                   potential duplicate PARTIES and scope of search.
CMN-007.03         Provide USER with the ability to view potential PARTY duplicates.         0
CMN-007.04         Provide USER with the ability to merge duplicate PARTY records.           0
CMN-008      Ability to accommodate hyphenated names; multiple surnames; individuals
             with only one name (e.g., Sting); doing business as (i.e., DBA); and
             corporate names.
CMN-008.01         Provide USER with the ability to assign party names that are              0
                   hyphenated or with an apostrophe ( e.g. "O'Flanagan" ).


     MDEC Procurement K11-0030-29                                                                                  September 1, 2010
                                               MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                        ATTACHMENT C
                                                 MARYLAND ELECTRONIC COURT PROCUREMENT                              Page 174 of 249
                                                        FUNCTIONAL REQUIREMENTS

                                                            CASE MANAGEMENT NAVIGATION

     ID                                     Requirement Text                                     Response Code   Comments
CMN-008.02        Provide USER with the ability to assign party names with multiple          0
                  surnames.
CMN-008.03        Provide USER with the ability to assign party names with just one word     0
                  (e.g. 'Sting').
CMN-008.04        Provide USER with the ability to assign party names that are 'doing        0
                  business as' (DBA).
CMN-008.05        Provide USER with the ability to assign party names that are corporate     0
                  names.
CMN-009      Provide electronic capability to link person information as AKA to known
             individuals and link cases of AKA to known individuals.
CMN-009.01        Provide USER with the ability to assign an AKA to a PERSON.                0
CMN-009.02        Provide USER with the ability to search CASES by AKA's.                    0
CMN-009.03        Automatically search for known PERSONS(defendants) when entering           0
                  new PARTY information as 'AKA.'
CMN-009.04        Automatically link CASES of an AKA name to known corresponding             0
                  INDIVIDUAL.
CMN-009.05        Provide ADMIN USER with the ability to define rules for matching AKA       0
                  name to known individual name.
CMN-010      Ability to track name and address change history for a given person.
CMN-010.02        Automatically maintain full history of name and address changes for a      0
                  PERSON.
CMN-010.03        Provide USER with the ability to view name and address history for a       0
                  PERSON.
CMN-011      Allow a user to identify and link an existing person record rather than re-
             entering person information for each case or complaint.
CMN-011.01        Provide ADMIN USER with the ability to define rules for linking multiple   0
                  CASES with the same PERSON.
CMN-011.02        Provide USER with the ability to link multiple CASES though the same       0
                  PERSON.
CMN-011.03        Provide USER with the ability to identify multiple CASES through the       0
                  same PERSON.
CMN-012      Allow the association of one or more vehicles to one or more persons or
             businesses.
CMN-012.01        Provide USER with the ability to assign many-to-many associations          0
                  between PARTY and VEHICLE.



     MDEC Procurement K11-0030-29                                                                                  September 1, 2010
                                               MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                         ATTACHMENT C
                                                 MARYLAND ELECTRONIC COURT PROCUREMENT                               Page 175 of 249
                                                        FUNCTIONAL REQUIREMENTS

                                                            CASE MANAGEMENT NAVIGATION

     ID                                   Requirement Text                                        Response Code   Comments
CMN-013      Support address verification against multiple address databases external
             to the case management system (e.g., DMV and Credit Reporting Bureau).
CMN-013.01       Provide USER with the ability to verify ADDRESSES against external           0
                 address data bases such as MVA, Credit reporting bureaus, Board of
                 Elections, or any other reliable ADDRESS data base.

CMN-014      Address validation (e.g., US Postal Service and/or GIS).
CMN-014.01       Provide USER with the ability to validate PARTY ADDRESSES                0
                 through USPS using one or more of the following: NCOA, AEC
CMN-015      Support incorporation of address data and data source information from
             outside databases if, after verification, that data is found to be different
             while retaining data entered from the charging document or booking notice.
CMN-015.01        Provide USER with the ability to verify ADDRESS data from outside           0
                  sources.
CMN-015.02        Provide USER with the ability to incorporate ADDRESS data from              0
                  outside sources while retaining data from CHARGING DOCUMENT or
                  booking notice as history.
CMN-016      Capture and store violation data information (e.g., statutes, blood alcohol
             concentration (BAC), location, date, time, officer badge number, crash
             indicator, personal injury, property damage, fatality), including charges pre-
             and post-conviction and amendments.
CMN-016.01        Provide USER with the ability to assign charge statutes to the              0
                  INCIDENT.
CMN-016.02        Provide USER with the ability to assign blood alcohol concentration to      0
                  the INCIDENT.
CMN-016.03        Provide USER with the ability to assign date and time to the INCIDENT.      0
CMN-016.04       Provide USER with the ability to assign responding officer(s) name and       0
                 Identifier to the INCIDENT.
CMN-016.05       Provide USER with the ability to assign crash indicator to the               0
                 INCIDENT.
CMN-016.06       Provide USER with the ability to assign personal injury indicator,           0
                 property damage, and fatality indicators to the INCIDENT.
CMN-016.07       Provide USER with the ability to assign other violation data information     0
                 to the INCIDENT.
CMN-016.08       Provide USER with the ability to assign pre-conviction, post-conviction      0
                 and charges.

     MDEC Procurement K11-0030-29                                                                                   September 1, 2010
                                                MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                       ATTACHMENT C
                                                  MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 176 of 249
                                                         FUNCTIONAL REQUIREMENTS

                                                             CASE MANAGEMENT NAVIGATION

     ID                                    Requirement Text                                      Response Code   Comments
CMN-016.09        Provide ADMIN USER with the ability to define codes for INCIDENT           0
                  Information.
CMN-017      Provide user with an option to view/update full history of a case in one
             record (e.g. Case moved from District Court to Circuit ) or to limit search
             of records from one particular court/case type/ party type, date etc.
CMN-017.01        Provide USER with the ability to display or update the full history of a   0
                  CASE on one page.
CMN-017.02        Provide USER with the ability to limit search of records to one court,     0
                  case type, party type, date or other delimiter.
CMN-017.03        Provide ADMIN USER with the ability to set search delimiters.              0




     MDEC Procurement K11-0030-29                                                                                  September 1, 2010
                                                       MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                                                    ATTACHMENT C
                                                         MARYLAND ELECTRONIC COURT PROCUREMENT                                                          Page 177 of 249
                                                                FUNCTIONAL REQUIREMENTS

                                                                                   INTEGRATION

     ID                                        Requirement Text                                            Response Code                            Comments
Accounting Integration - This section integrates the inbound and outbound flow of all Case-related Payments, Obligations, Deposits, Disbursements and Adjustments. Also includes
individual accounts moved to Collections (CCU).
Inbound Accounting Processing
INT-001       Index Accounting Documents
INT-001.1         Automatically receive electronic Accounting Documents/Images as attachments          0
                  or links in near real time
INT-001.2         Automatically index electronic Accounting Documents/Images                           0
INT-001.3         Provide Admin User the ability to define rules for indexing electronic Accounting    0
                  documents.
INT-001.4         Provide User the ability to scan and index Accounting Documents                      0
INT-002       Inbound near real-time Accounting processing (implies an inbound queue structure or
              set of api's )
INT-002.1          Automatically consume Accounting data/metadata in near real time                    0
INT-002.2         Automatically assign Accounting information to Case and Case Participant using       0
                  near real time electronic data
INT-002.3         Automatically respond/notify on the success/failure of processing electronic         0
                  Accounting data
INT-003       Inbound batch processing for Accounting
INT-003.1         Automatically import batch data for Accounting information                           0
INT-003.2         Automatically assign Accounting information to Case and Case Participant using       0
                  batch data
INT-004       Inbound monitoring and review for Accounting data imports
INT-004.1         Provide Admin User the ability to define field(s) for querying imported Accounting   0
                  batch data
INT-004.2         Provide Admin User the ability to define fields for viewing imported batch           0
                  Accounting data
INT-004.3         Provide User the ability to select batch records for Accounting data                 0
INT-004.4         Provide User the ability to accept/reject batch records for Accounting data          0
INT-005       Inbound Configuration for Accounting electronic data
INT-005.1      Provide Admin User the ability to define rules for validating electronic Accounting     0
               data
INT-005.2      Provide Admin User the ability to define workflow for processing inbound                0
               electronic Accounting data
INT-005.3      Provide Admin User the ability to map/translate external Accounting data to             0
               internal Charging data for assignment
Outbound Accounting Processing
INT-006       Outbound Batch Processing (Reporting) for Accounting data

       MDEC Procurement K11-0030-29                                                                                                                     September 1, 2010
                                                          MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                                                             ATTACHMENT C
                                                            MARYLAND ELECTRONIC COURT PROCUREMENT                                                                   Page 178 of 249
                                                                   FUNCTIONAL REQUIREMENTS

                                                                                       INTEGRATION

     ID                                          Requirement Text                                               Response Code                                  Comments
INT-006.1          Provide Admin user the ability to schedule exports for Accounting data                 0
INT-006.2          Provide Admin user the ability to export Accounting data in the xml format             0
INT-006.3          Provide Admin user the ability to define fields (elements) for the batch exports of    0
                   Accounting data
INT-006.4          Provide Admin user the ability to define fields for querying Accounting data       0
INT-006.5          Provide Admin user the ability to define query parameters for the batch exports of 0
                   Accounting data
INT-006.6          Provide Admin user the ability to configure export destinations for Accounting data 0

INT-007        Outbound Near real-time processing for Accounting transactions
INT-007.1      Provide the ability to produce/publish to a queue structure in near real-time all          0
               Accounting transactions
INT-007.2      Provide Admin User the ability to subscribe to all Accounting transaction data by          0
               using a subscription service (implies no custom coding)
INT-007.3      Provide Admin user the ability configure one or more queue destinations for                0
               Accounting transactions
INT-007.4      Provide Admin user the ability to direct Accounting transactions to a specific             0
               queue using filtering criteria
INT-007.5      Provide Admin User the ability to define message fields, including                         0
               document/image links, for Accounting transaction data
On-Demand Request/Response API's for Accounting information
INT-008    Provide the ability to request via Web Services all Accounting information by
           parameters
INT-009    Provide the ability to retrieve Accounting Documents/Images
INT-010        Provide the ability to return Accounting information using the ECF 4.0 or NIEM 2.0
               standard
INT-011        Provide API list for retrieving Accounting information, list should include parameters
               and return fields
INT-012        A synchronous response is implied. State conditions when response is asynchronous
               for retrieving Accounting data.
Case Initiation Integration - This section integrates the inbound and outbound flow of all documents and filing transactions that initiate a case. Including, but not limited to, Charging
Documents, Citations, Indictments, Original Complaints and Petitions, Information and Intake sheets.
Inbound Case Initiation Processing
INT-013     Index Case Initiation Documents
INT-013.1          Automatically receive electronic Case Initiation Documents/Images as                   0
                   attachments or links in near real time
INT-013.2          Automatically index electronic Case Initiation Documents/Images                        0

        MDEC Procurement K11-0030-29                                                                                                                               September 1, 2010
                                                        MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                          ATTACHMENT C
                                                          MARYLAND ELECTRONIC COURT PROCUREMENT                                Page 179 of 249
                                                                 FUNCTIONAL REQUIREMENTS

                                                                                     INTEGRATION

     ID                                        Requirement Text                                             Response Code   Comments
INT-013.3         Provide Admin User the ability to define rules for indexing electronic Case           0
                  Initiation documents.
INT-013.4         Provide User the ability to scan and index Case Initiation Documents                  0
INT-014       Inbound near real-time Case Initiation processing (implies an inbound queue structure
              or set of api's )
INT-014.1          Automatically consume Case Initiation data/metadata in near real time                0
INT-014.2         Automatically assign Case Initiation information to Case and Case Participant         0
                  using near real time electronic data
INT-014.3         Automatically respond/notify on the success/failure of processing electronic Case     0
                  Initiation data
INT-015       Inbound batch processing for Case Initiation
INT-015.1         Automatically import batch data for Case Initiation information                       0
INT-015.2         Automatically assign Case Initiation information to Case and Case Participant         0
                  using batch data
INT-016       Inbound monitoring and review for Case Initiation data imports
INT-016.1         Provide Admin User the ability to define field(s) for querying imported Case          0
                  Initiation batch data
INT-016.2         Provide Admin User the ability to define fields for viewing imported batch Case       0
                  Initiation data
INT-016.3         Provide User the ability to select batch records for Case Initiation data             0
INT-016.4         Provide User the ability to accept/reject batch records for Case Initiation data      0
INT-017       Inbound Configuration for Case Initiation electronic data
INT-017.1       Provide Admin User the ability to define rules for validating electronic Case           0
                Initiation data
INT-017.2       Provide Admin User the ability to define workflow for processing inbound                0
                electronic Case Initiation data
INT-017.3       Provide Admin User the ability to map/translate external Case Initiation data to        0
                internal Charging data for assignment
Outbound Case Initiation Processing
INT-018    Outbound Batch Processing (Reporting) for Case Initiation data
INT-018.1         Provide Admin user the ability to schedule exports for Case Initiation data           0
INT-018.2         Provide Admin user the ability to export Case Initiation data in the xml format       0
INT-018.3         Provide Admin user the ability to define fields (elements) for the batch exports of   0
                  Case Initiation data
INT-018.4         Provide Admin user the ability to define fields for querying Case Initiation data     0
INT-018.5         Provide Admin user the ability to define query parameters for the batch exports of    0
                  Case Initiation data

       MDEC Procurement K11-0030-29                                                                                           September 1, 2010
                                                       MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                                                       ATTACHMENT C
                                                         MARYLAND ELECTRONIC COURT PROCUREMENT                                                             Page 180 of 249
                                                                FUNCTIONAL REQUIREMENTS

                                                                                   INTEGRATION

     ID                                        Requirement Text                                           Response Code                               Comments
INT-018.6            Provide Admin user the ability to configure export destinations for Case Initiation   0
                     data
INT-019        Outbound Near real-time processing for Case Initiation transactions
INT-019.1            Provide the ability to produce/publish to a queue structure in near real-time all     0
                     Case Initiation transactions
INT-019.2            Provide Admin User the ability to subscribe to all Case Initiation transaction data   0
                     by using a subscription service (implies no custom coding)
INT-019.3            Provide Admin user the ability configure one or more queue destinations for Case 0
                     Initiation transactions
INT-019.4            Provide Admin user the ability to direct Case Initiation transactions to a specific   0
                     queue using filtering criteria
INT-019.5            Provide Admin User the ability to define message fields, including                    0
                     document/image links, for Case Initiation transaction data
On-Demand Request/Response API's for Case Initiation information
INT-020        Provide the ability to request via Web Services all Case Initiation information by
               parameters
INT-021        Provide the ability to retrieve Case Initiation Documents/Images
INT-022        Provide the ability to return Case Initiation information using the ECF 4.0 or NIEM 2.0
               standard
INT-023        Provide API list for retrieving Case Initiation information, list should include parameters
               and return fields
INT-024        A synchronous response is implied. State conditions when response is asynchronous
               for retrieving Case Initiation data.
Subsequent Filings and Request Integration - This section integrates the inbound and outbound flow of all documents and information filed on an existing case. Including, but not
limited to, Answers, Amended Complaints, Motions and Pleas.
Inbound Subsequent Filings and Request Processing
INT-025     Index Subsequent Filings and Request Documents
INT-025.1         Automatically receive electronic Subsequent Filings and Request                     0
                  Documents/Images as attachments or links in near real time
INT-025.2         Automatically index electronic Subsequent Filings and Request                       0
                  Documents/Images
INT-025.3         Provide Admin User the ability to define rules for indexing electronic Subsequent   0
                  Filings and Request documents.
INT-025.4         Provide User the ability to scan and index Subsequent Filings and Request           0
                  Documents
INT-026       Inbound near real-time Subsequent Filings and Request processing (implies an
              inbound queue structure or set of api's )


       MDEC Procurement K11-0030-29                                                                                                                       September 1, 2010
                                                       MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                           ATTACHMENT C
                                                         MARYLAND ELECTRONIC COURT PROCUREMENT                                 Page 181 of 249
                                                                FUNCTIONAL REQUIREMENTS

                                                                                   INTEGRATION

     ID                                       Requirement Text                                              Response Code   Comments
INT-026.1        Automatically consume Subsequent Filings and Request data/metadata in near             0
                 real time
INT-026.2        Automatically assign Subsequent Filings and Request information to Case and            0
                 Case Participant using near real time electronic data
INT-026.3        Automatically respond/notify on the success/failure of processing electronic           0
                 Subsequent Filings and Request data
INT-027      Inbound batch processing for Subsequent Filings and Request
INT-027.1         Automatically import batch data for Subsequent Filings and Request information        0

INT-027.2        Automatically assign Subsequent Filings and Request information to Case and            0
                 Case Participant using batch data
INT-028      Inbound monitoring and review for Subsequent Filings and Request data imports
INT-028.1        Provide Admin User the ability to define field(s) for querying imported Subsequent     0
                 Filings and Request batch data
INT-028.2        Provide Admin User the ability to define fields for viewing imported batch             0
                 Subsequent Filings and Request data
INT-028.3        Provide User the ability to select batch records for Subsequent Filings and            0
                 Request data
INT-028.4        Provide User the ability to accept/reject batch records for Subsequent Filings and     0
                 Request data
INT-029      Inbound Configuration for Subsequent Filings and Request electronic data
INT-029.1      Provide Admin User the ability to define rules for validating electronic Subsequent 0
               Filings and Request data
INT-029.2      Provide Admin User the ability to define workflow for processing inbound            0
               electronic Subsequent Filings and Request data
INT-029.3      Provide Admin User the ability to map/translate external Subsequent Filings and     0
               Request data to internal Charging data for assignment
Outbound Subsequent Filings and Request Processing
INT-030    Outbound Batch Processing (Reporting) for Subsequent Filings and Request data
INT-030.1         Provide Admin user the ability to schedule exports for Subsequent Filings and         0
                  Request data
INT-030.2         Provide Admin user the ability to export Subsequent Filings and Request data in       0
                  the xml format
INT-030.3         Provide Admin user the ability to define fields (elements) for the batch exports of   0
                  Subsequent Filings and Request data
INT-0304          Provide Admin user the ability to define fields for querying Subsequent Filings and   0
                  Request data


       MDEC Procurement K11-0030-29                                                                                           September 1, 2010
                                                        MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                                                       ATTACHMENT C
                                                          MARYLAND ELECTRONIC COURT PROCUREMENT                                                             Page 182 of 249
                                                                 FUNCTIONAL REQUIREMENTS

                                                                                    INTEGRATION

     ID                                        Requirement Text                                             Response Code                               Comments
INT-030.5          Provide Admin user the ability to define query parameters for the batch exports of   0
                   Subsequent Filings and Request data
INT-030.6          Provide Admin user the ability to configure export destinations for Subsequent       0
                   Filings and Request data
INT-030
              Outbound Near real-time processing for Subsequent Filings and Request transactions
INT-030.1         Provide the ability to produce/publish to a queue structure in near real-time all     0
                  Subsequent Filings and Request transactions
INT-030.2                                                                                               0
                Provide Admin User the ability to subscribe to all Subsequent Filings and Request
                transaction data by using a subscription service (implies no custom coding)
INT-030.3       Provide Admin user the ability configure one or more queue destinations for       0
                Subsequent Filings and Request transactions
INT-030.4       Provide Admin user the ability to direct Subsequent Filings and Request           0
                transactions to a specific queue using filtering criteria
INT-030.5       Provide Admin User the ability to define message fields, including                0
                document/image links, for Subsequent Filings and Request transaction data
On-Demand Request/Response API's for Subsequent Filings and Request information
INT-031    Provide the ability to request via Web Services all Subsequent Filings and Request
           information by parameters
INT-032    Provide the ability to retrieve Subsequent Filings and Request Documents/Images
INT-033        Provide the ability to return Subsequent Filings and Request information using the
               ECF 4.0 or NIEM 2.0 standard
INT-034        Provide API list for retrieving Subsequent Filings and Request information, list should
               include parameters and return fields
INT-035        A synchronous response is implied. State conditions when response is asynchronous
               for retrieving Subsequent Filings and Request data.
External Agency Notice, Request and Response Integration - This section integrates the inbound and outbound flow of documents and information with partner agencies for requests
and notices from the court and notices and responses from partner agencies back to the court. It also includes information for referrals, services and programs order by the court.
Documents and information may include Arrest and Custody information, Pretrial Screening reports, Pre-Sentence Investigation Reports, requests/responses for psychiatric and
competency evaluations, writ lists, child protective services evaluation, DSS permanency plans, information on adult referrals for pre-sentence report, information regarding non-
compliance of pre-trial intervention (e.g. mediation, landlord/tenant rent escrow) . See also Referrals/Services and Referrals/Services Outcomes in Global Processing Profile.


Inbound External Agency Notice, Request and Response Processing
INT-036     Index External Agency Notice, Request and Response Documents
INT-036.1          Automatically receive electronic External Agency Notice, Request and Response        0
                   Documents/Images as attachments or links in near real time



       MDEC Procurement K11-0030-29                                                                                                                        September 1, 2010
                                                        MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                         ATTACHMENT C
                                                          MARYLAND ELECTRONIC COURT PROCUREMENT                               Page 183 of 249
                                                                 FUNCTIONAL REQUIREMENTS

                                                                                   INTEGRATION

     ID                                        Requirement Text                                            Response Code   Comments
INT-036.2          Automatically index electronic External Agency Notice, Request and Response         0
                   Documents/Images
INT-036.3          Provide Admin User the ability to define rules for indexing electronic External     0
                   Agency Notice, Request and Response documents.
INT-036.4          Provide User the ability to scan and index External Agency Notice, Request and      0
                   Response Documents
INT-037       Inbound near real-time External Agency Notice, Request and Response processing
              (implies an inbound queue structure or set of api's )
INT-037.1          Automatically consume External Agency Notice, Request and Response                  0
                   data/metadata in near real time
INT-037.2          Automatically assign External Agency Notice, Request and Response information       0
                   to Case and Case Participant using near real time electronic data
INT-037.3         Automatically respond/notify on the success/failure of processing electronic         0
                  External Agency Notice, Request and Response data
INT-038       Inbound batch processing for External Agency Notice, Request and Response
INT-038.1        Automatically import batch data for External Agency Notice, Request and               0
                 Response information
INT-038.2        Automatically assign External Agency Notice, Request and Response information         0
                 to Case and Case Participant using batch data
INT-039     Inbound monitoring and review for External Agency Notice, Request and Response
            data imports
INT-039.1        Provide Admin User the ability to define field(s) for querying imported External      0
                 Agency Notice, Request and Response batch data
INT-039.2        Provide Admin User the ability to define fields for viewing imported batch External   0
                 Agency Notice, Request and Response data
INT-039.3        Provide User the ability to select batch records for External Agency Notice,          0
                 Request and Response data
INT-039.4        Provide User the ability to accept/reject batch records for External Agency Notice,   0
                 Request and Response data
INT-040     Inbound Configuration for External Agency Notice, Request and Response electronic
            data
INT-040.1        Provide Admin User the ability to define rules for validating electronic External     0
                 Agency Notice, Request and Response data
INT-040.2        Provide Admin User the ability to define workflow for processing inbound              0
                 electronic External Agency Notice, Request and Response data
INT-040.3        Provide Admin User the ability to map/translate external Agency Notice, Request       0
                 and Response data to internal Charging data for assignment
Outbound External Agency Notice, Request and Response Processing


       MDEC Procurement K11-0030-29                                                                                          September 1, 2010
                                                      MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                          ATTACHMENT C
                                                        MARYLAND ELECTRONIC COURT PROCUREMENT                                Page 184 of 249
                                                               FUNCTIONAL REQUIREMENTS

                                                                                  INTEGRATION

    ID                                       Requirement Text                                             Response Code   Comments
INT-041     Outbound Batch Processing (Reporting) for External Agency Notice, Request and
            Response data
INT-041.1       Provide Admin user the ability to schedule exports for External Agency Notice,        0
                Request and Response data
INT-041.2       Provide Admin user the ability to export External Agency Notice, Request and          0
                Response data in the xml format
INT-041.3       Provide Admin user the ability to define fields (elements) for the batch exports of   0
                External Agency Notice, Request and Response data
INT-041.4       Provide Admin user the ability to define fields for querying External Agency          0
                Notice, Request and Response data
INT-041.5       Provide Admin user the ability to define query parameters for the batch exports of    0
                External Agency Notice, Request and Response data
INT-041.6       Provide Admin user the ability to configure export destinations for External          0
                Agency Notice, Request and Response data
INT-042     Outbound Near real-time processing for External Agency Notice, Request and
            Response transactions
INT-042.1       Provide the ability to produce/publish to a queue structure in near real-time all     0
                External Agency Notice, Request and Response transactions
INT-042.2       Provide Admin User the ability to subscribe to all External Agency Notice,     0
                Request and Response transaction data by using a subscription service (implies
                no custom coding)
INT-042.3       Provide Admin user the ability configure one or more queue destinations for    0
                External Agency Notice, Request and Response transactions
INT-042.4       Provide Admin user the ability to direct External Agency Notice, Request and   0
                Response transactions to a specific queue using filtering criteria
INT-042.5       Provide Admin User the ability to define message fields, including             0
                document/image links, for External Agency Notice, Request and Response
                transaction data
On-Demand Request/Response API's for External Agency Notice, Request and Response information
INT-043    Provide the ability to request via Web Services all External Agency Notice, Request
           and Response information by parameters
INT-044    Provide the ability to retrieve External Agency Notice, Request and Response
           Documents/Images
INT-045    Provide the ability to return External Agency Notice, Request and Response
           information using the ECF 4.0 or NIEM 2.0 standard
INT-046    Provide API list for retrieving External Agency Notice, Request and Response
           information, list should include parameters and return fields




       MDEC Procurement K11-0030-29                                                                                         September 1, 2010
                                                         MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                                                          ATTACHMENT C
                                                           MARYLAND ELECTRONIC COURT PROCUREMENT                                                                Page 185 of 249
                                                                  FUNCTIONAL REQUIREMENTS

                                                                                     INTEGRATION

     ID                                         Requirement Text                                              Response Code                                 Comments
INT-047       A synchronous response is implied. State conditions when response is asynchronous
              for retrieving External Agency Notice, Request and Response data.
Charge Activity Integration - This section integrates the inbound and outbound flow of all Charge modifications made to a set of charges after the initial filing. Outbound flow of this
section will be used to trigger notifications to Public Safety.
Inbound Charge Activity Processing
INT-048     Index Charge Activity Documents
INT-048.1          Automatically receive electronic Charge Activity Documents/Images as                 0
                   attachments or links in near real time
INT-048.2          Automatically index electronic Charge Activity Documents/Images                      0
INT-048.3          Provide Admin User the ability to define rules for indexing electronic Charge        0
                   Activity documents.
INT-048.4          Provide User the ability to scan and index Charge Activity Documents                 0
INT-049       Inbound near real-time Charge Activity processing (implies an inbound queue
              structure or set of api's )
INT-049.1          Automatically consume Charge Activity data/metadata in near real time                0
INT-049.2         Automatically assign Charge Activity information to Case and Case Participant         0
                  using near real time electronic data
INT-049.3         Automatically respond/notify on the success/failure of processing electronic          0
                  Charge Activity data
INT-050       Inbound batch processing for Charge Activity
INT-050.1          Automatically import batch data for Charge Activity information                      0
INT-050.2         Automatically assign Charge Activity information to Case and Case Participant         0
                  using batch data
INT-051       Inbound monitoring and review for Charge Activity data imports
INT-051.1          Provide Admin User the ability to define field(s) for querying imported Charge       0
                   Activity batch data
INT-051.2          Provide Admin User the ability to define fields for viewing imported batch Charge    0
                   Activity data
INT-051.3          Provide User the ability to select batch records for Charge Activity data            0
INT-051.4          Provide User the ability to accept/reject batch records for Charge Activity data     0
INT-052       Inbound Configuration for Charge Activity electronic data
INT-052.1          Provide Admin User the ability to define rules for validating electronic Charge      0
                   Activity data
INT-052.2          Provide Admin User the ability to define workflow for processing inbound             0
                   electronic Charge Activity data
INT-052.3          Provide Admin User the ability to map/translate external Charge Activity data to     0
                   internal Charging data for assignment

        MDEC Procurement K11-0030-29                                                                                                                            September 1, 2010
                                                         MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                                                       ATTACHMENT C
                                                           MARYLAND ELECTRONIC COURT PROCUREMENT                                                             Page 186 of 249
                                                                  FUNCTIONAL REQUIREMENTS

                                                                                     INTEGRATION

     ID                                         Requirement Text                                             Response Code                               Comments
Outbound Charge Activity Processing
INT-053    Outbound Batch Processing (Reporting) for Charge Activity data
INT-053.1          Provide Admin user the ability to schedule exports for Charge Activity data           0
INT-053.2          Provide Admin user the ability to export Charge Activity data in the xml format       0
INT-053.3          Provide Admin user the ability to define fields (elements) for the batch exports of   0
                   Charge Activity data
INT-053.4          Provide Admin user the ability to define fields for querying Charge Activity data     0
INT-053.5             Provide Admin user the ability to define query parameters for the batch exports of 0
                      Charge Activity data
INT-053.6             Provide Admin user the ability to configure export destinations for Charge Activity 0
                      data
INT-054         Outbound Near real-time processing for Charge Activity transactions
INT-054.1             Provide the ability to produce/publish to a queue structure in near real-time all   0
                      Charge Activity transactions
INT-054.2             Provide Admin User the ability to subscribe to all Charge Activity transaction data 0
                      by using a subscription service (implies no custom coding)
INT-054.3             Provide Admin user the ability configure one or more queue destinations for         0
                      Charge Activity transactions
INT-054.4             Provide Admin user the ability to direct Charge Activity transactions to a specific 0
                      queue using filtering criteria
INT-054.5             Provide Admin User the ability to define message fields, including                  0
                      document/image links, for Charge Activity transaction data
On-Demand Request/Response API's for Charge Activity information
INT-055         Provide the ability to request via Web Services all Charge Activity information by
                parameters
INT-056         Provide the ability to retrieve Charge Activity Documents/Images
INT-057         Provide the ability to return Charge Activity information using the ECF 4.0 or NIEM 2.0
                standard
INT-058         Provide API list for retrieving Charge Activity information, list should include
                parameters and return fields
INT-059         A synchronous response is implied. State conditions when response is asynchronous
                for retrieving Charge Activity data.
Disposition, Judgment and Conviction Integration - This section integrates the inbound and outbound flow of all documents and information for Case Dispositions, Charge Dispositions,
Issue and Relief Dispositions, and Property Dispositions. Also covered is Dispositions on Case Participants, including subsequent name and address changes. Outbound flow of this
section will be used to trigger notifications to agencies such as MVA, Licensing Agencies, and Public Safety. Changes in Case Reporting Status are included in this section. See Global
Processing Profile for reporting status values and disposition values for Case, Relief, Issues/Allegations and Charges. This section also integrates the inbound and outbound flow for
documents and information involving all Judgment, Post-Judgment, Conviction and Post-Conviction activities.


       MDEC Procurement K11-0030-29                                                                                                                         September 1, 2010
                                                        MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                           ATTACHMENT C
                                                          MARYLAND ELECTRONIC COURT PROCUREMENT                                 Page 187 of 249
                                                                 FUNCTIONAL REQUIREMENTS

                                                                                    INTEGRATION

    ID                                        Requirement Text                                               Response Code   Comments
Inbound Disposition, Judgment and Conviction Processing
INT-060     Index Disposition, Judgment and Conviction Documents
INT-060.1        Automatically receive electronic Disposition, Judgment and Conviction                   0
                 Documents/Images as attachments or links in near real time
INT-060.2        Automatically index electronic Disposition, Judgment and Conviction                     0
                 Documents/Images
INT-060.3        Provide Admin User the ability to define rules for indexing electronic Disposition,     0
                 Judgment and Conviction documents.
INT-060.4        Provide User the ability to scan and index Disposition, Judgment and Conviction         0
                 Documents
INT-061      Inbound near real-time Disposition, Judgment and Conviction processing (implies an
             inbound queue structure or set of api's )
INT-061.1        Automatically consume Disposition, Judgment and Conviction data/metadata in             0
                 near real time
INT-061.2        Automatically assign Disposition, Judgment and Conviction information to Case           0
                 and Case Participant using near real time electronic data
INT-061.3        Automatically respond/notify on the success/failure of processing electronic            0
                 Disposition, Judgment and Conviction data
INT-062      Inbound batch processing for Disposition, Judgment and Conviction
INT-062.1        Automatically import batch data for Disposition, Judgment and Conviction        0
                 information
INT-062.2        Automatically assign Disposition, Judgment and Conviction information to Case   0
                 and Case Participant using batch data
INT-063      Inbound monitoring and review for Disposition, Judgment and Conviction data imports

INT-063.1        Provide Admin User the ability to define field(s) for querying imported Disposition,    0
                 Judgment and Conviction batch data
INT-063.2        Provide Admin User the ability to define fields for viewing imported batch              0
                 Disposition, Judgment and Conviction data
INT-063.3        Provide User the ability to select batch records for Disposition, Judgment and          0
                 Conviction data
INT-063.4        Provide User the ability to accept/reject batch records for Disposition, Judgment       0
                 and Conviction data
INT-064      Inbound Configuration for Disposition, Judgment and Conviction electronic data
INT-064.1        Provide Admin User the ability to define rules for validating electronic Disposition,   0
                 Judgment and Conviction data
INT-064.2        Provide Admin User the ability to define workflow for processing inbound                0
                 electronic Disposition, Judgment and Conviction data


       MDEC Procurement K11-0030-29                                                                                            September 1, 2010
                                                        MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                         ATTACHMENT C
                                                          MARYLAND ELECTRONIC COURT PROCUREMENT                               Page 188 of 249
                                                                 FUNCTIONAL REQUIREMENTS

                                                                                   INTEGRATION

     ID                                        Requirement Text                                            Response Code   Comments
INT-064.3        Provide Admin User the ability to map/translate external Disposition, Judgment        0
                 and Conviction data to internal Charging data for assignment
Outbound Disposition, Judgment and Conviction Processing
INT-065     Outbound Batch Processing (Reporting) for Disposition, Judgment and Conviction
            data
INT-065.1        Provide Admin user the ability to schedule exports for Disposition, Judgment and      0
                 Conviction data
INT-065.2        Provide Admin user the ability to export Disposition, Judgment and Conviction         0
                 data in the xml format
INT-065.3        Provide Admin user the ability to define fields (elements) for the batch exports of   0
                 Disposition, Judgment and Conviction data
INT-065.4        Provide Admin user the ability to define fields for querying Disposition, Judgment    0
                 and Conviction data
INT-065.5        Provide Admin user the ability to define query parameters for the batch exports of    0
                 Disposition, Judgment and Conviction data
INT-065.6        Provide Admin user the ability to configure export destinations for Disposition,      0
                 Judgment and Conviction data
INT-066     Outbound Near real-time processing for Disposition, Judgment and Conviction
            transactions
INT-066.1        Provide the ability to produce/publish to a queue structure in near real-time all     0
                 Disposition, Judgment and Conviction transactions
INT-066.2        Provide Admin User the ability to subscribe to all Disposition, Judgment and          0
                 Conviction transaction data by using a subscription service (implies no custom
                 coding)
INT-066.3        Provide Admin user the ability configure one or more queue destinations for           0
                 Disposition, Judgment and Conviction transactions
INT-066.4        Provide Admin user the ability to direct Disposition, Judgment and Conviction         0
                 transactions to a specific queue using filtering criteria
INT-066.5                                                                                              0
                 Provide Admin User the ability to define message fields, including
                 document/image links, for Disposition, Judgment and Conviction transaction data
On-Demand Request/Response API's for Disposition, Judgment and Conviction information
INT-067     Provide the ability to request via Web Services all Disposition, Judgment and
            Conviction information by parameters
INT-068     Provide the ability to retrieve Disposition, Judgment and Conviction
            Documents/Images
INT-069     Provide the ability to return Disposition, Judgment and Conviction information using
            the ECF 4.0 or NIEM 2.0 standard


       MDEC Procurement K11-0030-29                                                                                          September 1, 2010
                                                        MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                                                    ATTACHMENT C
                                                          MARYLAND ELECTRONIC COURT PROCUREMENT                                                          Page 189 of 249
                                                                 FUNCTIONAL REQUIREMENTS

                                                                                     INTEGRATION

     ID                                        Requirement Text                                            Response Code                             Comments
INT-070       Provide API list for retrieving Disposition, Judgment and Conviction information, list
              should include parameters and return fields
INT-071       A synchronous response is implied. State conditions when response is asynchronous
              for retrieving Disposition, Judgment and Conviction data.
Court Outcome Integration - This section integrates the inbound and outbound flow of all Scheduled Event outcomes and related documents, including but not limited to all Orders,
Temporary Orders, Notices and Decisions. Expungements, Special Access information and Notice of Sealed Case are included in this section. For full list of Scheduled Event outcomes
see Global Processing Profile. This section also integrates the inbound and outbound flow of all Scheduled Event Results which include Cancelled, Continued, Held and Postponed.
(See Global Processing Profile)
Inbound Court Outcome Processing
INT-072     Index Court Outcome Documents
INT-072.1         Automatically receive electronic Court Outcome Documents/Images as                   0
                  attachments or links in near real time
INT-072.2         Automatically index electronic Court Outcome Documents/Images                        0
INT-072.3         Provide Admin User the ability to define rules for indexing electronic Court         0
                  Outcome documents.
INT-072.4         Provide User the ability to scan and index Court Outcome Documents                   0
INT-073       Inbound near real-time Court Outcome processing (implies an inbound queue
              structure or set of api's )
INT-073.1          Automatically consume Court Outcome data/metadata in near real time                 0
INT-073.2         Automatically assign Court Outcome information to Case and Case Participant          0
                  using near real time electronic data
INT-073.3         Automatically respond/notify on the success/failure of processing electronic Court   0
                  Outcome data
INT-074       Inbound batch processing for Court Outcome
INT-074.1         Automatically import batch data for Court Outcome information                        0
INT-074.2         Automatically assign Court Outcome information to Case and Case Participant          0
                  using batch data
INT-075       Inbound monitoring and review for Court Outcome data imports
INT-075.1         Provide Admin User the ability to define field(s) for querying imported Court        0
                  Outcome batch data
INT-075.2         Provide Admin User the ability to define fields for viewing imported batch Court     0
                  Outcome data
INT-075.3         Provide User the ability to select batch records for Court Outcome data              0
INT-075.4         Provide User the ability to accept/reject batch records for Court Outcome data       0
INT-076       Inbound Configuration for Court Outcome electronic data
INT-076.1         Provide Admin User the ability to define rules for validating electronic Court       0
                  Outcome data

       MDEC Procurement K11-0030-29                                                                                                                      September 1, 2010
                                                        MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                          ATTACHMENT C
                                                          MARYLAND ELECTRONIC COURT PROCUREMENT                                Page 190 of 249
                                                                 FUNCTIONAL REQUIREMENTS

                                                                                    INTEGRATION

     ID                                        Requirement Text                                             Response Code   Comments
INT-076.2       Provide Admin User the ability to define workflow for processing inbound                0
                electronic Court Outcome data
INT-076.3       Provide Admin User the ability to map/translate external Court Outcome data to          0
                internal Charging data for assignment
Outbound Court Outcome Processing
INT-077    Outbound Batch Processing (Reporting) for Court Outcome data
INT-077.1         Provide Admin user the ability to schedule exports for Court Outcome data             0
INT-077.2         Provide Admin user the ability to export Court Outcome data in the xml format         0
INT-077.3         Provide Admin user the ability to define fields (elements) for the batch exports of   0
                  Court Outcome data
INT-077.4         Provide Admin user the ability to define fields for querying Court Outcome data       0
INT-077.5        Provide Admin user the ability to define query parameters for the batch exports of     0
                 Court Outcome data
INT-077.6        Provide Admin user the ability to configure export destinations for Court Outcome      0
                 data
INT-078      Outbound Near real-time processing for Court Outcome transactions
INT-078.1        Provide the ability to produce/publish to a queue structure in near real-time all      0
                 Court Outcome transactions
INT-078.2        Provide Admin User the ability to subscribe to all Court Outcome transaction data      0
                 by using a subscription service (implies no custom coding)
INT-078.3        Provide Admin user the ability configure one or more queue destinations for Court 0
                 Outcome transactions
INT-078.4        Provide Admin user the ability to direct Court Outcome transactions to a specific 0
                 queue using filtering criteria
INT-078.5        Provide Admin User the ability to define message fields, including                0
                 document/image links, for Court Outcome transaction data
On-Demand Request/Response API's for Court Outcome information
INT-079    Provide the ability to request via Web Services all Court Outcome information by
           parameters
INT-080    Provide the ability to retrieve Court Outcome Documents/Images
INT-081    Provide the ability to return Court Outcome information using the ECF 4.0 or NIEM 2.0
           standard
INT-082    Provide API list for retrieving Court Outcome information, list should include
           parameters and return fields
INT-083    A synchronous response is implied. State conditions when response is asynchronous
           for retrieving Court Outcome data.



       MDEC Procurement K11-0030-29                                                                                           September 1, 2010
                                                       MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                                                       ATTACHMENT C
                                                         MARYLAND ELECTRONIC COURT PROCUREMENT                                                             Page 191 of 249
                                                                FUNCTIONAL REQUIREMENTS

                                                                                   INTEGRATION

     ID                                        Requirement Text                                            Response Code                               Comments
Scheduling Integration - This section integrates the inbound and outbound flow of all documents and information on court schedule activity and calendars. This section does not
include Writ lists. See the Agency Notice, Request and Response Integration. Examples include Infax courtroom display or dockets being available on the internet.
Inbound Scheduling Processing
INT-084     Index Scheduling Documents
INT-084.1         Automatically receive electronic Scheduling Documents/Images as attachments          0
                  or links in near real time
INT-084.2         Automatically index electronic Scheduling Documents/Images                           0
INT-084.3         Provide Admin User the ability to define rules for indexing electronic Scheduling    0
                  documents.
INT-084.4         Provide User the ability to scan and index Scheduling Documents                      0
INT-085       Inbound near real-time Scheduling processing (implies an inbound queue structure or
              set of api's )
INT-085.1          Automatically consume Scheduling data/metadata in near real time                    0
INT-085.2         Automatically assign Scheduling information to Case and Case Participant using       0
                  near real time electronic data
INT-085.3         Automatically respond/notify on the success/failure of processing electronic         0
                  Scheduling data
INT-086       Inbound batch processing for Scheduling
INT-086.1         Automatically import batch data for Scheduling information                           0
INT-086.2         Automatically assign Scheduling information to Case and Case Participant using       0
                  batch data
INT-087       Inbound monitoring and review for Scheduling data imports
INT-087.1         Provide Admin User the ability to define field(s) for querying imported Scheduling   0
                  batch data
INT-087.2         Provide Admin User the ability to define fields for viewing imported batch           0
                  Scheduling data
INT-087.3         Provide User the ability to select batch records for Scheduling data                 0
INT-087.4         Provide User the ability to accept/reject batch records for Scheduling data          0
INT-088       Inbound Configuration for Scheduling electronic data
INT-088.1      Provide Admin User the ability to define rules for validating electronic Scheduling     0
               data
INT-088.2      Provide Admin User the ability to define workflow for processing inbound                0
               electronic Scheduling data
INT-088.3      Provide Admin User the ability to map/translate external Scheduling data to             0
               internal Charging data for assignment
Outbound Scheduling Processing
INT-089    Outbound Batch Processing (Reporting) for Scheduling data

       MDEC Procurement K11-0030-29                                                                                                                       September 1, 2010
                                                        MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                                                      ATTACHMENT C
                                                          MARYLAND ELECTRONIC COURT PROCUREMENT                                                            Page 192 of 249
                                                                 FUNCTIONAL REQUIREMENTS

                                                                                    INTEGRATION

     ID                                        Requirement Text                                             Response Code                              Comments
INT-089.1         Provide Admin user the ability to schedule exports for Scheduling data                0
INT-089.2         Provide Admin user the ability to export Scheduling data in the xml format            0
INT-089.3         Provide Admin user the ability to define fields (elements) for the batch exports of   0
                  Scheduling data
INT-089.4         Provide Admin user the ability to define fields for querying Scheduling data       0
INT-089.5         Provide Admin user the ability to define query parameters for the batch exports of 0
                  Scheduling data
INT-089.6         Provide Admin user the ability to configure export destinations for Scheduling data 0

INT-090       Outbound Near real-time processing for Scheduling transactions
INT-090.1           Provide the ability to produce/publish to a queue structure in near real-time all 0
                    Scheduling transactions
INT-090.2           Provide Admin User the ability to subscribe to all Scheduling transaction data by 0
                    using a subscription service (implies no custom coding)
INT-090.3           Provide Admin user the ability configure one or more queue destinations for       0
                    Scheduling transactions
INT-090.4           Provide Admin user the ability to direct Scheduling transactions to a specific    0
                    queue using filtering criteria
INT-090.5           Provide Admin User the ability to define message fields, including                0
                    document/image links, for Scheduling transaction data
On-Demand Request/Response API's for Scheduling information
INT-091       Provide the ability to request via Web Services all Scheduling information by
              parameters
INT-092       Provide the ability to retrieve Scheduling Documents/Images
INT-093       Provide the ability to return Scheduling information using the ECF 4.0 or NIEM 2.0
              standard
INT-094       Provide API list for retrieving Scheduling information, list should include parameters
              and return fields
INT-095       A synchronous response is implied. State conditions when response is asynchronous
              for retrieving Scheduling data.
Bail/Bond Integration - This section integrates the inbound and outbound flow of all Bail/Bond documents and activity and such as Bail Settings, Bonds Postings and Forfeiture
Extension, Satisfaction, Stricken or Closed.
Inbound Bail/Bond Processing
INT-096      Index Bail/Bond Documents
INT-096.1         Automatically receive electronic Bail/Bond Documents/Images as attachments or         0
                  links in near real time
INT-096.2         Automatically index electronic Bail/Bond Documents/Images                             0

       MDEC Procurement K11-0030-29                                                                                                                        September 1, 2010
                                                        MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                          ATTACHMENT C
                                                          MARYLAND ELECTRONIC COURT PROCUREMENT                                Page 193 of 249
                                                                 FUNCTIONAL REQUIREMENTS

                                                                                    INTEGRATION

     ID                                        Requirement Text                                             Response Code   Comments
INT-096.3         Provide Admin User the ability to define rules for indexing electronic Bail/Bond      0
                  documents.
INT-096.4         Provide User the ability to scan and index Bail/Bond Documents                        0
INT-097       Inbound near real-time Bail/Bond processing (implies an inbound queue structure or
              set of api's )
INT-097.1          Automatically consume Bail/Bond data/metadata in near real time                      0
INT-097.2         Automatically assign Bail/Bond information to Case and Case Participant using         0
                  near real time electronic data
INT-097.3         Automatically respond/notify on the success/failure of processing electronic          0
                  Bail/Bond data
INT-098       Inbound batch processing for Bail/Bond
INT-098.1         Automatically import batch data for Bail/Bond information                             0
INT-098.2         Automatically assign Bail/Bond information to Case and Case Participant using         0
                  batch data
INT-099       Inbound monitoring and review for Bail/Bond data imports
INT-099.1         Provide Admin User the ability to define field(s) for querying imported Bail/Bond     0
                  batch data
INT-099.2         Provide Admin User the ability to define fields for viewing imported batch            0
                  Bail/Bond data
INT-099.3         Provide User the ability to select batch records for Bail/Bond data                   0
INT-099.4         Provide User the ability to accept/reject batch records for Bail/Bond data            0
INT-100       Inbound Configuration for Bail/Bond electronic data
INT-100.1       Provide Admin User the ability to define rules for validating electronic Bail/Bond  0
                data
INT-100.2       Provide Admin User the ability to define workflow for processing inbound            0
                electronic Bail/Bond data
INT-100.3       Provide Admin User the ability to map/translate external Bail/Bond data to internal 0
                Charging data for assignment
Outbound Bail/Bond Processing
INT-101    Outbound Batch Processing (Reporting) for Bail/Bond data
INT101.1          Provide Admin user the ability to schedule exports for Bail/Bond data                 0
INT101.2          Provide Admin user the ability to export Bail/Bond data in the xml format             0
INT101.3          Provide Admin user the ability to define fields (elements) for the batch exports of   0
                  Bail/Bond data
INT101.4          Provide Admin user the ability to define fields for querying Bail/Bond data           0
INT101.5          Provide Admin user the ability to define query parameters for the batch exports of    0
                  Bail/Bond data

       MDEC Procurement K11-0030-29                                                                                           September 1, 2010
                                                        MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                                                      ATTACHMENT C
                                                          MARYLAND ELECTRONIC COURT PROCUREMENT                                                            Page 194 of 249
                                                                 FUNCTIONAL REQUIREMENTS

                                                                                   INTEGRATION

     ID                                        Requirement Text                                            Response Code                               Comments
INT101.6          Provide Admin user the ability to configure export destinations for Bail/Bond data   0

INT-102       Outbound Near real-time processing for Bail/Bond transactions
INT-102.1             Provide the ability to produce/publish to a queue structure in near real-time all   0
                      Bail/Bond transactions
INT-102.2             Provide Admin User the ability to subscribe to all Bail/Bond transaction data by    0
                      using a subscription service (implies no custom coding)
INT-102.3             Provide Admin user the ability configure one or more queue destinations for         0
                      Bail/Bond transactions
INT-102.4             Provide Admin user the ability to direct Bail/Bond transactions to a specific queue 0
                      using filtering criteria
INT-102.5             Provide Admin User the ability to define message fields, including                  0
                      document/image links, for Bail/Bond transaction data
On-Demand Request/Response API's for Bail/Bond information
INT-103
                Provide the ability to request via Web Services all Bail/Bond information by parameters
INT-104         Provide the ability to retrieve Bail/Bond Documents/Images
INT-105         Provide the ability to return Bail/Bond information using the ECF 4.0 or NIEM 2.0
                standard
INT-106         Provide API list for retrieving Bail/Bond information, list should include parameters and
                return fields
INT-107         A synchronous response is implied. State conditions when response is asynchronous
                for retrieving Bail/Bond data.
Warrant Integration - This section integrates the inbound and outbound flow for documents and information for Warrant Requests, Issues and Recalls. Service request and notice of
Service is not included in this section. See Service Integration.
Inbound Warrant Processing
INT-108     Index Warrant Documents
INT-108.1         Automatically receive electronic Warrant Documents/Images as attachments or          0
                  links in near real time
INT-108.2         Automatically index electronic Warrant Documents/Images                              0
INT-108.3         Provide Admin User the ability to define rules for indexing electronic Warrant       0
                  documents.
INT-108.4         Provide User the ability to scan and index Warrant Documents                         0
INT-109       Inbound near real-time Warrant processing (implies an inbound queue structure or set
              of api's )
INT-109.1          Automatically consume Warrant data/metadata in near real time                       0
INT-109.2         Automatically assign Warrant information to Case and Case Participant using          0
                  near real time electronic data

       MDEC Procurement K11-0030-29                                                                                                                       September 1, 2010
                                                        MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                          ATTACHMENT C
                                                          MARYLAND ELECTRONIC COURT PROCUREMENT                                Page 195 of 249
                                                                 FUNCTIONAL REQUIREMENTS

                                                                                     INTEGRATION

     ID                                        Requirement Text                                             Response Code   Comments
INT-109.3         Automatically respond/notify on the success/failure of processing electronic          0
                  Warrant data
INT-110       Inbound batch processing for Warrant
INT-110.1         Automatically import batch data for Warrant information                               0
INT-110.2         Automatically assign Warrant information to Case and Case Participant using           0
                  batch data
INT-111       Inbound monitoring and review for Warrant data imports
INT-111.1         Provide Admin User the ability to define field(s) for querying imported Warrant       0
                  batch data
INT-111.2         Provide Admin User the ability to define fields for viewing imported batch Warrant    0
                  data
INT-111.3         Provide User the ability to select batch records for Warrant data                     0
INT-111.4         Provide User the ability to accept/reject batch records for Warrant data              0
INT-112       Inbound Configuration for Warrant electronic data
INT-112.1         Provide Admin User the ability to define rules for validating electronic Warrant data 0

INT-112.2      Provide Admin User the ability to define workflow for processing inbound                 0
               electronic Warrant data
INT-112.3      Provide Admin User the ability to map/translate external Warrant data to internal        0
               Charging data for assignment
Outbound Warrant Processing
INT-113    Outbound Batch Processing (Reporting) for Warrant data
INT-113.1         Provide Admin user the ability to schedule exports for Warrant data                   0
INT-113.2         Provide Admin user the ability to export Warrant data in the xml format               0
INT-113.3         Provide Admin user the ability to define fields (elements) for the batch exports of   0
                  Warrant data
INT-113.4         Provide Admin user the ability to define fields for querying Warrant data             0
INT-113.5         Provide Admin user the ability to define query parameters for the batch exports of    0
                  Warrant data
INT-113.6         Provide Admin user the ability to configure export destinations for Warrant data      0

INT-114       Outbound Near real-time processing for Warrant transactions
INT-114.1         Provide the ability to produce/publish to a queue structure in near real-time all     0
                  Warrant transactions
INT-114.2         Provide Admin User the ability to subscribe to all Warrant transaction data by        0
                  using a subscription service (implies no custom coding)



       MDEC Procurement K11-0030-29                                                                                           September 1, 2010
                                                        MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                                                  ATTACHMENT C
                                                          MARYLAND ELECTRONIC COURT PROCUREMENT                                                        Page 196 of 249
                                                                 FUNCTIONAL REQUIREMENTS

                                                                                    INTEGRATION

     ID                                        Requirement Text                                         Response Code                             Comments
INT-114.3      Provide Admin user the ability configure one or more queue destinations for          0
               Warrant transactions
INT-114.4      Provide Admin user the ability to direct Warrant transactions to a specific queue    0
               using filtering criteria
INT-114.5      Provide Admin User the ability to define message fields, including                   0
               document/image links, for Warrant transaction data
On-Demand Request/Response API's for Warrant information
INT-115    Provide the ability to request via Web Services all Warrant information by parameters

INT-116      Provide the ability to retrieve Warrant Documents/Images
INT-117       Provide the ability to return Warrant information using the ECF 4.0 or NIEM 2.0
              standard
INT-118       Provide API list for retrieving Warrant information, list should include parameters and
              return fields
INT-119       A synchronous response is implied. State conditions when response is asynchronous
              for retrieving Warrant data.
Service Integration - This section integrates the inbound and outbound flow of requests and documents for service of process for Warrants, Summonses, Subpoenas and other
documents that require service. Acknowledging receipt of Notification of Service and the Service outcome is also covered in this section.

Inbound Service Processing
INT-120     Index Service Documents
INT-120.1         Automatically receive electronic Service Documents/Images as attachments or       0
                  links in near real time
INT-120.2         Automatically index electronic Service Documents/Images                           0
INT-120.3         Provide Admin User the ability to define rules for indexing electronic Service    0
                  documents.
INT-120.4         Provide User the ability to scan and index Service Documents                      0
INT-121      Inbound near real-time Service processing (implies an inbound queue structure or set
             of api's )
INT-121.1         Automatically consume Service data/metadata in near real time                    0
INT-121.2         Automatically assign Service information to Case and Case Participant using near 0
                 real time electronic data
INT-121.3        Automatically respond/notify on the success/failure of processing electronic       0
                 Service data
INT-122      Inbound batch processing for Service
INT-122.1         Automatically import batch data for Service information                           0
INT-122.2         Automatically assign Service information to Case and Case Participant using       0
                  batch data

       MDEC Procurement K11-0030-29                                                                                                                   September 1, 2010
                                                        MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                          ATTACHMENT C
                                                          MARYLAND ELECTRONIC COURT PROCUREMENT                                Page 197 of 249
                                                                 FUNCTIONAL REQUIREMENTS

                                                                                    INTEGRATION

     ID                                        Requirement Text                                             Response Code   Comments
INT-123       Inbound monitoring and review for Service data imports
INT-123.1         Provide Admin User the ability to define field(s) for querying imported Service       0
                  batch data
INT-123.2         Provide Admin User the ability to define fields for viewing imported batch Service    0
                  data
INT-123.3         Provide User the ability to select batch records for Service data                     0
INT-123.4         Provide User the ability to accept/reject batch records for Service data              0
INT-124       Inbound Configuration for Service electronic data
INT-124.1         Provide Admin User the ability to define rules for validating electronic Service data 0

INT-124.2       Provide Admin User the ability to define workflow for processing inbound                0
                electronic Service data
INT-124.3       Provide Admin User the ability to map/translate external Service data to internal       0
                Charging data for assignment
Outbound Service Processing
INT-125    Outbound Batch Processing (Reporting) for Service data
INT-125.1         Provide Admin user the ability to schedule exports for Service data                   0
INT-125.2         Provide Admin user the ability to export Service data in the xml format               0
INT-125.3         Provide Admin user the ability to define fields (elements) for the batch exports of   0
                  Service data
INT-125.4         Provide Admin user the ability to define fields for querying Service data             0
INT-125.5         Provide Admin user the ability to define query parameters for the batch exports of    0
                  Service data
INT-125.6         Provide Admin user the ability to configure export destinations for Service data      0

INT-126    Outbound Near real-time processing for Service transactions
INT-126.1      Provide the ability to produce/publish to a queue structure in near real-time all        0
               Service transactions
INT-126.2      Provide Admin User the ability to subscribe to all Service transaction data by           0
               using a subscription service (implies no custom coding)
INT-126.3      Provide Admin user the ability configure one or more queue destinations for              0
               Service transactions
INT-126.4      Provide Admin user the ability to direct Service transactions to a specific queue        0
               using filtering criteria
INT-126.5      Provide Admin User the ability to define message fields, including                       0
               document/image links, for Service transaction data
On-Demand Request/Response API's for Service information


       MDEC Procurement K11-0030-29                                                                                           September 1, 2010
                                                         MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                                                           ATTACHMENT C
                                                           MARYLAND ELECTRONIC COURT PROCUREMENT                                                                 Page 198 of 249
                                                                  FUNCTIONAL REQUIREMENTS

                                                                                     INTEGRATION

     ID                                         Requirement Text                                              Response Code                                 Comments
INT-127       Provide the ability to request via Web Services all Service information by parameters

INT-128       Provide the ability to retrieve Service Documents/Images
INT-129          Provide the ability to return Service information using the ECF 4.0 or NIEM 2.0
                 standard
INT-130          Provide API list for retrieving Service information, list should include parameters and
                 return fields
INT-131          A synchronous response is implied. State conditions when response is asynchronous
                 for retrieving Service data.
Sentencing and Probation Integration - This section integrates the inbound and outbound flow for documents and information involving Sentencing and Sentencing Modification
activities. This includes information on Sentence compliance, non-compliance and completion from appropriate agencies.

This section also integrates the inbound and outbound flow for documents and information involving Probation. Integration with the Probation unit will include summary Probation
information (e.g., content of probation order including terms and conditions; type of probation program such as work program, home arrest, jail and work release, alcohol and drug
program; level of supervision; status of probation such as suspended, reinstated, extended, revoked; progress of probation; history of probation). Information from the Probation unit will
include, but not limited to payment, restitution and status reports. This integration section also receives violation of probation information.

Inbound Sentencing and Probation Processing
INT-132     Index Sentencing and Probation Documents
INT-132.1          Automatically receive electronic Sentencing and Probation Documents/Images as 0
                   attachments or links in near real time
INT-132.2          Automatically index electronic Sentencing and Probation Documents/Images      0
INT-132.3          Provide Admin User the ability to define rules for indexing electronic Sentencing    0
                   and Probation documents.
INT-132.4          Provide User the ability to scan and index Sentencing and Probation Documents        0

INT-133       Inbound near real-time Sentencing and Probation processing (implies an inbound
              queue structure or set of api's )
INT-133.1         Automatically consume Sentencing and Probation data/metadata in near real time 0

INT-133.2         Automatically assign Sentencing and Probation information to Case and Case            0
                  Participant using near real time electronic data
INT-133.3         Automatically respond/notify on the success/failure of processing electronic          0
                  Sentencing and Probation data
INT-134       Inbound batch processing for Sentencing and Probation
INT-134.1          Automatically import batch data for Sentencing and Probation information             0
INT-134.2         Automatically assign Sentencing and Probation information to Case and Case            0
                  Participant using batch data
INT-135       Inbound monitoring and review for Sentencing and Probation data imports

        MDEC Procurement K11-0030-29                                                                                                                            September 1, 2010
                                                        MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                        ATTACHMENT C
                                                          MARYLAND ELECTRONIC COURT PROCUREMENT                              Page 199 of 249
                                                                 FUNCTIONAL REQUIREMENTS

                                                                                   INTEGRATION

     ID                                        Requirement Text                                           Response Code   Comments
INT-135.1         Provide Admin User the ability to define field(s) for querying imported Sentencing 0
                  and Probation batch data
INT-135.2         Provide Admin User the ability to define fields for viewing imported batch         0
                  Sentencing and Probation data
INT-135.3         Provide User the ability to select batch records for Sentencing and Probation data 0

INT-135.4         Provide User the ability to accept/reject batch records for Sentencing and          0
                  Probation data
INT-136       Inbound Configuration for Sentencing and Probation electronic data
INT-136.1      Provide Admin User the ability to define rules for validating electronic Sentencing    0
               and Probation data
INT-136.2      Provide Admin User the ability to define workflow for processing inbound               0
               electronic Sentencing and Probation data
INT-136.3      Provide Admin User the ability to map/translate external Sentencing and                0
               Probation data to internal Charging data for assignment
Outbound Sentencing and Probation Processing
INT-137    Outbound Batch Processing (Reporting) for Sentencing and Probation data
INT-137.1      Provide Admin user the ability to schedule exports for Sentencing and Probation        0
               data
INT-137.2      Provide Admin user the ability to export Sentencing and Probation data in the xml      0
               format
INT-137.3      Provide Admin user the ability to define fields (elements) for the batch exports of    0
               Sentencing and Probation data
INT-137.4      Provide Admin user the ability to define fields for querying Sentencing and            0
               Probation data
INT-137.5      Provide Admin user the ability to define query parameters for the batch exports of     0
               Sentencing and Probation data
INT-137.6      Provide Admin user the ability to configure export destinations for Sentencing and     0
               Probation data
INT-138    Outbound Near real-time processing for Sentencing and Probation transactions
INT-138.1      Provide the ability to produce/publish to a queue structure in near real-time all      0
               Sentencing and Probation transactions
INT-138.2      Provide Admin User the ability to subscribe to all Sentencing and Probation            0
               transaction data by using a subscription service (implies no custom coding)
INT-138.3         Provide Admin user the ability configure one or more queue destinations for         0
                  Sentencing and Probation transactions
INT-138.4         Provide Admin user the ability to direct Sentencing and Probation transactions to   0
                  a specific queue using filtering criteria


       MDEC Procurement K11-0030-29                                                                                         September 1, 2010
                                                          MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                                                            ATTACHMENT C
                                                            MARYLAND ELECTRONIC COURT PROCUREMENT                                                                  Page 200 of 249
                                                                   FUNCTIONAL REQUIREMENTS

                                                                                      INTEGRATION

     ID                                          Requirement Text                                               Response Code                                 Comments
INT-138.5       Provide Admin User the ability to define message fields, including                        0
                document/image links, for Sentencing and Probation transaction data
On-Demand Request/Response API's for Sentencing and Probation information
INT-139    Provide the ability to request via Web Services all Sentencing and Probation
           information by parameters
INT-140    Provide the ability to retrieve Sentencing and Probation Documents/Images
INT-141        Provide the ability to return Sentencing and Probation information using the ECF 4.0 or
               NIEM 2.0 standard
INT-142        Provide API list for retrieving Sentencing and Probation information, list should include
               parameters and return fields
INT-143        A synchronous response is implied. State conditions when response is asynchronous
               for retrieving Sentencing and Probation data.
Error, Correction and Deletion Integration - This section integrates the inbound and outbound flow for clerical errors, corrections and deletions for any of the Integration groups. It does
not include accounting adjustments.
Inbound Error, Correction and Deletion Processing
INT-144     Index Error, Correction and Deletion Documents
INT-144.1          Automatically receive electronic Error, Correction and Deletion                        0
                   Documents/Images as attachments or links in near real time
INT-144.2          Automatically index electronic Error, Correction and Deletion Documents/Images         0

INT-144.3          Provide Admin User the ability to define rules for indexing electronic Error,          0
                   Correction and Deletion documents.
INT-144.4          Provide User the ability to scan and index Error, Correction and Deletion              0
                   Documents
INT-145        Inbound near real-time Error, Correction and Deletion processing (implies an inbound
               queue structure or set of api's )
INT-145.1          Automatically consume Error, Correction and Deletion data/metadata in near real        0
                   time
INT-145.2          Automatically assign Error, Correction and Deletion information to Case and Case       0
                   Participant using near real time electronic data
INT-145.3          Automatically respond/notify on the success/failure of processing electronic Error,    0
                   Correction and Deletion data
INT-146        Inbound batch processing for Error, Correction and Deletion
INT-146.1          Automatically import batch data for Error, Correction and Deletion information         0
INT-146.2          Automatically assign Error, Correction and Deletion information to Case and Case 0
                   Participant using batch data
INT-147        Inbound monitoring and review for Error, Correction and Deletion data imports


        MDEC Procurement K11-0030-29                                                                                                                              September 1, 2010
                                                         MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                          ATTACHMENT C
                                                           MARYLAND ELECTRONIC COURT PROCUREMENT                                Page 201 of 249
                                                                  FUNCTIONAL REQUIREMENTS

                                                                                    INTEGRATION

     ID                                         Requirement Text                                             Response Code   Comments
INT-147.1         Provide Admin User the ability to define field(s) for querying imported Error,         0
                  Correction and Deletion batch data
INT-147.2         Provide Admin User the ability to define fields for viewing imported batch Error,      0
                  Correction and Deletion data
INT-147.3         Provide User the ability to select batch records for Error, Correction and Deletion    0
                  data
INT-147.4         Provide User the ability to accept/reject batch records for Error, Correction and      0
                  Deletion data
INT-148       Inbound Configuration for Error, Correction and Deletion electronic data
INT-148.1        Provide Admin User the ability to define rules for validating electronic Error,         0
                 Correction and Deletion data
INT-148.2        Provide Admin User the ability to define workflow for processing inbound                0
                 electronic Error, Correction and Deletion data
INT-148.3        Provide Admin User the ability to map/translate external Error, Correction and          0
                 Deletion data to internal Charging data for assignment
Outbound Error, Correction and Deletion Processing
INT-149     Outbound Batch Processing (Reporting) for Error, Correction and Deletion data
INT-149.1          Provide Admin user the ability to schedule exports for Error, Correction and          0
                   Deletion data
INT-149.2          Provide Admin user the ability to export Error, Correction and Deletion data in the   0
                   xml format
INT-149.3          Provide Admin user the ability to define fields (elements) for the batch exports of   0
                   Error, Correction and Deletion data
INT-149.4          Provide Admin user the ability to define fields for querying Error, Correction and    0
                   Deletion data
INT-149.5          Provide Admin user the ability to define query parameters for the batch exports of    0
                   Error, Correction and Deletion data
INT-149.6          Provide Admin user the ability to configure export destinations for Error,            0
                   Correction and Deletion data
INT-150
              Outbound Near real-time processing for Error, Correction and Deletion transactions
INT-150.1         Provide the ability to produce/publish to a queue structure in near real-time all      0
                  Error, Correction and Deletion transactions
INT-150.2         Provide Admin User the ability to subscribe to all Error, Correction and Deletion      0
                  transaction data by using a subscription service (implies no custom coding)

INT-150.3          Provide Admin user the ability configure one or more queue destinations for Error, 0
                   Correction and Deletion transactions


       MDEC Procurement K11-0030-29                                                                                            September 1, 2010
                                                         MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                           MARYLAND ELECTRONIC COURT PROCUREMENT                            Page 202 of 249
                                                                  FUNCTIONAL REQUIREMENTS

                                                                                     INTEGRATION

     ID                                         Requirement Text                                         Response Code   Comments
INT-150.4       Provide Admin user the ability to direct Error, Correction and Deletion transactions 0
                to a specific queue using filtering criteria
INT-150.5       Provide Admin User the ability to define message fields, including                   0
                document/image links, for Error, Correction and Deletion transaction data
On-Demand Request/Response API's for Error, Correction and Deletion information
INT-151    Provide the ability to request via Web Services all Error, Correction and Deletion
           information by parameters
INT-152    Provide the ability to retrieve Error, Correction and Deletion Documents/Images
INT-153      Provide the ability to return Error, Correction and Deletion information using the ECF
             4.0 or NIEM 2.0 standard
INT-154      Provide API list for retrieving Error, Correction and Deletion information, list should
             include parameters and return fields
INT-155      A synchronous response is implied. State conditions when response is asynchronous
             for retrieving Error, Correction and Deletion data.
Electronic Notification to Case Participants
INT-156      Provide Admin User the ability to define rules for when and what notices can be
             electronically notified
INT-157      Provide Admin User the ability to define rules for when and what Court outcomes can
             be electronically notified
INT-158      Provide Admin User the ability to define rules for what Case Participant types can be
             electronically notified for what notices and outcomes
INT-159      Provide User the ability to assign electronic access information to each Case
             Participant for notifications
INT-160      Provide the Admin User to define codes for Case Participant electronic notification
             types
INT-161      Provide E-Filer, with proper identification, to opt in/out of notification types, such as
             case is continued, dismissed, write is filed, service, judgments
INT-162      Automatically notify registered Case Participants with Court outcomes and notices




        MDEC Procurement K11-0030-29                                                                                       September 1, 2010
                                                    MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                   ATTACHMENT C
                                                      MARYLAND ELECTRONIC COURT PROCUREMENT                         Page 203 of 249
                                                             FUNCTIONAL REQUIREMENTS

                                                                     MGMT AND STAT REPORTS

      ID                                    Requirement Text                                     Response Code   Comments
Workflow / Screen Navigation
MSR-001       Provide the user the ability to navigate directly from a search result item to
              the related detail item.
Query
MSR-002       Provide Admin User the ability to set access levels on all report
              generations.
MSR-003       Provide the user with the ability to view the exhibit information.
Reports
MSR-003       Provide user with the ability to generate statistical reports for a selected
              case type , according to the requirements of the court or other requestor.

MSR-004         Provide user with the ability to generate caseload management reports,
                according to the requirements of the court or other requestor.
MSR-005         Provide user with the ability to generate speedy trial reports, case aging
                reports, or other reports as requested by the individual court or other
                requestor.
MSR-006         Provide user with the ability to generate a case profile/history report for a
                selected case; including defendant information, actions, register of
                actions, and other information about the case.
MSR-007         Provide user with the ability to select sort options to manipulate the
                information presented in case histories, when viewing case histories on-
                line.
MSR-008         Provide user with the ability to select multiple sort options in ascending or
                descending order.
MSR-009         Provide user with the ability to select multiple sort options, in ascending or
                descending order, when preparing to print a case history report.

MSR-010         Allow the user to provide a report of dispositions for traffic violations.
MSR-011         Allow the user to select the location and other parameters when providing
                a report of dispositions for traffic violations.
MSR-012         Allow the user to provide a report of commitment orders.
MSR-013         Allow the user to select the dates, location and other parameters when
                providing a report of commitment orders.
MSR-014         Allow the user to provide a report of warrants issued but not returned to
                the court.
MSR-015         Allow the user to select the dates, location and other parameters when
                providing a report of warrants issued but not returned to the court

      MDEC Procurement K11-0030-29                                                                                 September 1, 2010
                                                MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                   ATTACHMENT C
                                                  MARYLAND ELECTRONIC COURT PROCUREMENT                         Page 204 of 249
                                                         FUNCTIONAL REQUIREMENTS

                                                                 MGMT AND STAT REPORTS

     ID                                    Requirement Text                                  Response Code   Comments
MSR-016     Provide the user with the ability to generate financial reports using
            accounting data for each case.
MSR-017     Provide the user with the ability to select the type of financial reports.
MSR-018     Provide the Admin user with the ability to define the business rules for
            generating the financial reports.
MSR-019     Provide the user with the ability to generate a report of cases with no
            recent activity; i.e. active cases with no court date scheduled, active cases
            with past court date and no disposition, etc.
MSR-020     Provide the user with the ability to generate a report of cases that have
            been closed within a period of time specified with From - To dates.
MSR-021     Provide the Reporting Function with the ability to access audit trail data.
MSR-022     Provide the user with the ability to generate management reports derived
            from audit trail data.
MSR-023     Provide the user with the ability to generate a report of court order
            compliance (e.g., drug treatment court, alcohol programs, traffic school,
            community service, etc).
MSR-024     Provide the user with the ability to generate a report of defendants that
            have failed to appear for court events.
MSR-025     Provide the Admin user with the ability to define the business rules for
            generating failure to appear reports.
MSR-026     Provide the user with the ability to a report of monies collected.
MSR-027     Provide the user to select the parameters for the collection report; i.e.
            From & To dates, Past due accounts, Type of Payment method, and
            others.
MSR-028     Provide the Admin user with the ability to set parameters for collection
            reports.
MSR-029     Provide the user with the ability to display and print a detailed aging report
            of finances for a specific data range.
MSR-030     Provide the user with the ability to display and print a summary aging
            report of finances for a specific date range.
MSR-031     Provide the user with the ability to select the parameters for a detailed or
            summary finance aging report; i.e. all accounts, one defendant's account,
            pay status, time period, or others.
MSR-032     Provide the Admin user with the ability to define the rules for parameters
            for this report.



    MDEC Procurement K11-0030-29                                                                               September 1, 2010
                                                   MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                  ATTACHMENT C
                                                     MARYLAND ELECTRONIC COURT PROCUREMENT                        Page 205 of 249
                                                            FUNCTIONAL REQUIREMENTS

                                                                    MGMT AND STAT REPORTS

     ID                                      Requirement Text                                  Response Code   Comments
MSR-034         Provide Users the ability to produce reports (including ability to reproduce
                or reprint) showing cases that will be or have been archived or destroyed.

MSR-035         Provide User with a report that produces statistics on electronic
                transactions received, accepted and rejected over specific time period.
MSR-036         Provide Users the ability to produce case management reports.
MSR-037         Provide Users the ability to produce statistical reports for all case types
                and filter reports by any field.
Interoperability
MSR-038         Provide Admin User the ability to define additional custom identifiers for
                person, organization and person group entities.
MSR-039         Provide Admin User the ability to define rules for mapping identifiers from
                external systems to internal identifiers.
System features
MSR-040         Provide user with the ability to manage many interactive transactional
                processes simultaneously.
Documents (Forms)
MSR-041         Provide User with the ability to create form templates that enable a user to
                input information.

MSR-042         Provide User with the ability to create form templates for generating court
                documents using existing case data.

MSR-043      Provide User with the ability to generate court documents such as
             pleadings, warrants, and orders using templates.
AD HOC Reporting
MSR-044      Provide Users with the ability to create Ad Hoc Reports.
MSR-045      Provide Users with a report interface to create, save, schedule, and
             publish parameter driven ad hoc reports.
MSR-046      Provide Users with a report interface to create, save, schedule, and
             publish parameter driven standard, custom , and ad hoc reports.
MSR-047      Provide Users with a report interface to create, save, schedule, and
             publish parameter driven ad hoc reports.
MSR-048      Provide Admin Users with a report interface to create, save, schedule,
             and publish parameter driven ad hoc reports.
Report Templates (Creation)
MSR-049      Provide Users the ability to create report templates.

      MDEC Procurement K11-0030-29                                                                               September 1, 2010
                                                   MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                   ATTACHMENT C
                                                     MARYLAND ELECTRONIC COURT PROCUREMENT                         Page 206 of 249
                                                            FUNCTIONAL REQUIREMENTS

                                                                    MGMT AND STAT REPORTS

     ID                                   Requirement Text                                      Response Code   Comments
MSR-050        Provide Admin User the ability to distribute report templates to select sites.

MSR-051        Provide Users with the ability to add tabular listings, Bar Chart, Line
               Chart, Pie Chart, and Multi-way tables features to custom reports.
MSR-052        Provide users with the ability to preview the report layout or design prior to
               generating the report.
MSR-053        Provide users with the ability to add custom multi-line report titles or
               subjects to reports.
MSR-054        Provide users with a report interface that allows the users to sort tabular
               data on a selected column of data.
MSR-055        Provide User the ability to save the report output.
MSR-056        Provide User the ability to retrieve report outputs that have been saved.
MSR-057        Provide User the ability to edit saved report output, if User has the
               authority to do so.
MSR-058        Provide the User the ability save report output and mark as uneditable
MSR-059        Provide the User the ability to view report output before printing or saving.

MSR-060      Provide the users with the ability to sample report output by constraining
             on row results.
MSR-061      Provide the users with the ability to generate report output in various
             formats such as HTML, PDF, XML, RTF and Text formats
MSR-062      Provide Users the ability to distribute report output to different sites or
             locations
MSR-063      Provide User with the ability to create custom reports that utilize the Case
             Management data model for all function groups.
MSR-064      Provide User the ability to create reports that can access exhibit
             information.
MSR-065      Provide User the ability to add a disclaimer message to all reports stating
             that the data used in the report are provisional.
MSR-066      Automatically set the disclaimer message as a default on all reports.
Running Reports
MSR-067      Provide Admin User the ability to define field(s) for querying available
             reports.
MSR-068      Provide Admin User the ability to define field(s) for displaying information
             about existing reports.
MSR-069      Provide User the ability to select one or more reports to generate.
MSR-070      Provide users with the ability to rename a report output filename.

      MDEC Procurement K11-0030-29                                                                                September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                 ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                       Page 207 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                                  MGMT AND STAT REPORTS

     ID                                      Requirement Text                               Response Code   Comments
MSR-071       Provide the User the ability to export data with the CSV format directly to
              file without opening associated application.
MSR-072       Provide the User the ability to export data with the PDF format directly to
              file without opening associated application.
MSR-073       Provide the User the ability to export data with the MS Excel format
              directly to file without opening associated application.
MSR-074       Provide the User the ability to export data with the XML format directly to
              file without opening associated application.
MSR-075       Provide the User the ability to export data with the ASCII format directly
              to file without opening associated application.
MSR-076       Provide the User the ability to export data to SAS directly to file without
              opening associated application.
MSR-077       Provide the User the ability to export data with the HTML format directly
              to file without opening associated application.
MSR-078       Provide Users with a report interface that allows the report data to be
              exported to MS Excel.
MSR-079       Provide Users with a report interface that allows the report data to be
              exported to CSV.
MSR-080       Provide Users with a report interface that allows the report data to be
              exported to PDF.
MSR-081       Provide Users with a report interface that allows the report data to be
              exported to ASCII Text File.
MSR-082       Provide Users with a report interface that allows the report data to be
              exported to SAS.
MSR-083       Provide Users with a report interface that allows the report data to be
              exported to XML Text File.
MSR-084       Provide Users with a report interface that allows the report data to be
              exported to HTML.
MSR-085       Provide User with a report interface that allows the report data to be
              exported to MDB, ADP/MS Access format
Administration of Reports
MSR-086       Provide the User the ability to view existing report templates (layout).
MSR-087       Provide the User the ability to view the data model (query) associated with
              an existing report.
MSR-088       Provide the User the ability to search for existing reports.
MSR-089       Provide the User the ability to edit an existing report template ( layout).


     MDEC Procurement K11-0030-29                                                                             September 1, 2010
                                                MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                  ATTACHMENT C
                                                  MARYLAND ELECTRONIC COURT PROCUREMENT                        Page 208 of 249
                                                         FUNCTIONAL REQUIREMENTS

                                                                 MGMT AND STAT REPORTS

     ID                                  Requirement Text                                   Response Code   Comments
MSR-090     Provide the User the ability to edit an existing report query ( data model ).

MSR-091     Provide the User the ability to delete a report.
MSR-092     Provide the User the ability to create and save a report template and
            query.
MSR-093     Provide the users with the ability to view existing reports using a tree
            structure.
MSR-094     Provide the users with the ability to save report templates for personal
            access only.
MSR-095     Provide the Users with the ability to distribute reports to designated sites
            or locations.
MSR-096     Provide Users the ability to view report templates.
MSR-097     Provide the users with the ability to copy report template from private
            saved area to a designated site or location.
MSR-098     Provide Users with the ability to version report templates.
MSR-099     Provide court and case index as part of individual identification
            information index for courts, criminal support units, CJ agencies, and non-
            justice agencies.
MSR-100     Capture witness and victim information.
MSR-101     Maintain list of eligible attorneys, mediators, or service providers that
            could be selected assignment by judge.
MSR-102     Maintain accounting for attorneys fees paid for assignments by judge.
MSR-103     Allow access to account information involving an individual on probation
            (see Accounting - Bookkeeping Function).
MSR-104     Provide ability to list all the citation numbers associated with a case.
MSR-105     Provide remote access to case information as permitted by local rules or
            statutes.
MSR-106     Provide a Master's report in JD cases.
MSR-107     The user shall be able to define new report objects for use in ad hoc
            reports.
MSR-108     The system shall allow an authorized user to enter the subject of a report
            as a group identified for purposes of summarizing public health data.

MSR-109     The system should include performance reporting capabilities.
MSR-110     The system shall provide operational reports (defined as reports regarding
            the performance of the system).


    MDEC Procurement K11-0030-29                                                                              September 1, 2010
                                              MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                  ATTACHMENT C
                                                MARYLAND ELECTRONIC COURT PROCUREMENT                        Page 209 of 249
                                                       FUNCTIONAL REQUIREMENTS

                                                               MGMT AND STAT REPORTS

     ID                                 Requirement Text                                  Response Code   Comments
MSR-111     The system shall provide the ability to produce the data management
            reports.
MSR-112     System must provide ability to report data at an aggregate level. For
            example, to collect the number of participants in a large educational event
            and of them how many are of particular races or ages. So the system
            shall capture aggregate information (e.g. counts) about the participants of
            an event without any individual level data.




    MDEC Procurement K11-0030-29                                                                            September 1, 2010
                                                MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                     ATTACHMENT C
                                                  MARYLAND ELECTRONIC COURT PROCUREMENT                           Page 210 of 249
                                                         FUNCTIONAL REQUIREMENTS

                                                                     SPECIALTY COURTS

   ID                                       Requirement Text                                  Response Code   Comments
SCO-001      Provide ability to indicate a competency evaluation (CP3-105) is ordered
             and competency treatment (CP 3-106) is ordered, including date and time
             of orders.
SCO-001.01       Provide USER with the ability to assign an indicator to CASE when a      0
                 competency evaluation is ordered.
SCO-001.02       Provide USER with the ability to assign an indicator to CASE when a      0
                 competency treatment is ordered.
SCO-001.03       Provide USER with the ability to assign order date and order time to     0
                 CASE when competency evaluation is ordered or competency
                 treatment is ordered.
SCO-001.04       Provide ADMIN USER with the ability to assign rules for completion       0
                 (receipt of report etc) of competency evaluation order.
SCO-001.05       Provide ADMIN USER with the ability to assign rules for completion       0
                 (receipt of report etc) of competency treatment.
SCO-001.06       Provide ADMIN USER with the ability to define CODES for completion       0
                 (receipt of report etc) of competency evaluation order.
SCO-001.07       Provide ADMIN USER with the ability to define CODES for completion       0
                 (receipt of report etc) of competency treatment.
SCO-001.08       Provide ADMIN USER with the ability to assign date and time for          0
                 completion (receipt of report etc) of competency evaluation order.
SCO-001.09       Provide ADMIN USER with the ability to assign date and time for          0
                 completion (receipt of report etc) of competency treatment.
SCO-001.10       Automate HISTORY of competency evaluation order, competency              0
                 treatment order, receipt of findings for competency evaluation order,
                 completion of competency treatment.
SCO-002      Provide ability to indicate a Drug/Alcohol evaluation (HG8-505 outpatient,
             506 inpatient) is ordered and Drug/Alcohol treatment/commitment (HG 8-
             507) is ordered, including date and time of orders.

SCO-002.01       Provide USER with the ability to assign an indicator to CASE when a      0
                 drug/alcohol evaluation is ordered.
SCO-002.02       Provide USER with the ability to assign an indicator to CASE when a      0
                 drug/alcohol treatment is ordered.




   MDEC Procurement K11-0030-29                                                                                  September 1, 2010
                                                   MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                        ATTACHMENT C
                                                     MARYLAND ELECTRONIC COURT PROCUREMENT                              Page 211 of 249
                                                            FUNCTIONAL REQUIREMENTS

                                                                         SPECIALTY COURTS

   ID                                       Requirement Text                                        Response Code   Comments
SCO-002.03       Provide USER with the ability to assign order date and order time to           0
                 CASE when drug/alcohol evaluation is ordered or drug/alcohol
                 treatment is ordered.
SCO-002.04       Provide ADMIN USER with the ability to assign rules for completion             0
                 (receipt of report, etc) of drug/alcohol evaluation order.
SCO-002.05       Provide ADMIN USER with the ability to assign rules for completion             0
                 (grad/no grad, receipt of report, etc) of drug/alcohol treatment order.
SCO-002.06       Provide ADMIN USER with the ability to define CODES for completion             0
                 (receipt of report etc) of drug/alcohol evaluation order.
SCO-002.07       Provide ADMIN USER with the ability to define CODES for completion             0
                 (grad/no grad, receipt of report, etc) of drug/alcohol treatment order.

SCO-002.08       Provide ADMIN USER with the ability to assign date and time for                0
                 completion (receipt of report etc) of drug/alcohol evaluation order.
SCO-002.09       Provide ADMIN USER with the ability to assign date and time for                0
                 completion (grad/no grad, receipt of report etc) of drug/alcohol
                 treatment order.
SCO-002.10       Automate HISTORY of drug/alcohol evaluation order, drug/alcohol                0
                 treatment order, receipt of findings for drug/alcohol evaluation order,
                 completion of drug/alcohol treatment.
SCO-003      Provide ability to capture the plea prior to disposition (this is required prior
             to NCR examination or entry into drug court).
SCO-003.01       Provide USER with the ability to assign plea to CHARGE prior to                0
                 entering the disposition.
SCO-003.02       Provide ADMIN USER with the ability to define codes PLEA.                      0
SCO-003.03       Provide ADMIN USER with the ability to define rule for making PLEA a           0
                 required entity under certain conditions.
SCO-004      Provide ability to indicate a NCR examination (CP3-111) is ordered and
             NCR commitment (CP 3-112) is ordered.
SCO-004.01       Provide USER with the ability to assign an indicator to CASE when a            0
                 NCR examination is ordered.
SCO-004.02       Provide USER with the ability to assign an indicator to CASE when a            0
                 NCR commitment is ordered.
SCO-004.03       Provide USER with the ability to assign order date and order time to           0
                 CASE when NCR examination is ordered or NCR commitment is
                 ordered.

   MDEC Procurement K11-0030-29                                                                                        September 1, 2010
                                                MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                    ATTACHMENT C
                                                  MARYLAND ELECTRONIC COURT PROCUREMENT                          Page 212 of 249
                                                         FUNCTIONAL REQUIREMENTS

                                                                     SPECIALTY COURTS

   ID                                       Requirement Text                                 Response Code   Comments
SCO-004.04       Provide ADMIN USER with the ability to assign rules for completion      0
                 (receipt of report etc) of NCR evaluation order.
SCO-004.05       Provide ADMIN USER with the ability to assign rules for completion      0
                 (receipt of report etc) of NCR commitment.
SCO-004.06       Provide ADMIN USER with the ability to define CODES for completion      0
                 (receipt of report etc) of NCR evaluation order .
SCO-004.07       Provide ADMIN USER with the ability to define CODES for completion      0
                 (receipt of report etc) of NCR commitment.
SCO-004.08       Provide ADMIN USER with the ability to assign date and time for         0
                 completion (receipt of report etc) of NCR evaluation order .
SCO-004.09       Provide ADMIN USER with the ability to assign date and time for         0
                 completion (receipt of report etc) of NCR treatment.
SCO-004.10       Automate HISTORY of NCR evaluation order, NCR commitment,               0
                 receipt of findings for NCR evaluation order, completion of NCR
                 commitment.
SCO-005      Provide ability to multi-select type(s) of evaluation(s) being ordered.
SCO-005.01       Provide USER with the ability to assign one or many indicators to       0
                 CASE based on evaluations being ordered.
SCO-005.02     Automate HISTORY of evaluations.                                       0
SCO-006    Provide ability to distinguish between Incompetent and Dangerous, and
           Incompetent but Not dangerous
SCO-006.01     Provide USER with the ability to assign an indicator to CASE to        0
               distinguish between Incompetent and Dangerous and Incompetent but
               not dangerous.
SCO-007    Provide ability to indicate whether evaluation (and/or treatment) is being
           performed In Patient, Out Patient, or Residential.
SCO-007.01     Provide USER with the ability to assign an indicator to CASE to        0
               indicate if treatment or evaluation is being performed In Patient, Out
               Patient or Residential.
SCO-008    Provide ability to identify review hearings (e.g. event code listing should
           support distinguishing the event separate from other types of events)..
SCO-008.01     Provide USER with the ability to assign event code to SCHEDULED           0
               EVENT indicating a review hearing.
SCO-009    Provide ability to modify incompetency and Not Criminally responsible
           cases, including the ability to schedule hearings.


    MDEC Procurement K11-0030-29                                                                                September 1, 2010
                                                MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                       ATTACHMENT C
                                                  MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 213 of 249
                                                         FUNCTIONAL REQUIREMENTS

                                                                     SPECIALTY COURTS

   ID                                    Requirement Text                                       Response Code   Comments
SCO-009.01       Provide USER with the ability to assign CASE, PARTY, DOCKET,               0
                 SCHEDULED EVENT, etc to CASE when case is in incompetency or
                 NCR status.
SCO-009.02       Provide ADMIN USER with the ability to define rule for allowing CASE       0
                 activity while incompetency or NCR tasks are occurring on the case.

SCO-010    Provide ability to schedule a hearing in cases with a Not Criminally
           Responsible, closed, or probation disposition.
SCO-010.01     Provide USER with the ability to assign SCHEDULED EVENT to CASE 0
               when the case is NCR, closed or has a probation disposition.
SCO-011      Provide ability to schedule according to local business rules (e.g. review
             hearing intervals may be controlled by the maximum sentence of the
             charge) regular review hearings (annually at minimum) in cases with an
             incompetence status reviews.
SCO-011.01       Provide ADMIN USER with the ability to define rule for assigning           0
                 SCHEDULE EVENTS at regular intervals (e.g. weekly, monthly, yearly,
                 etc.).
SCO-011.02       Provide USER with the ability to assign SCHEDULED EVENT to CASE            0
                 at defined intervals (e.g. weekly, monthly, yearly, etc.).
SCO-012      Provide ability to indicate type of specialty court. For instance: MH-Mental
             Health, DC-Drug/Alcohol Court, Truancy Court, etc (including more needed
             over time).
SCO-012.01       Provide USER with the ability to assign an indicator to CASE when a        0
                 case is being handled by a specific specialty court.
SCO-012.02       Provide ADMIN USER with the ability to define codes for SPECIALTY          0
                 COURT indicators for each court level and each court location.

SCO-013    Provide ability to indicate parties and case participants (including
           parties/participants not directly involved with the court processing such as
           screeners or psychiatrists) involved for these types of cases. E.g. FAST,
           DHMH.
SCO-013.01      Provide USER with the ability to assign PARTY/ORGANIZATIONS to              0
                CASE based on their involvement in specialty court activity.
SCO-014    Provide a seven day calendar tickler report. When a competency
           evaluation is ordered Dept of Health and Mental Hygiene (DHMH) must
           send a findings report within 7 days of the court ordered evaluation to: the
           requesting court, the state‘s attorney, the defense counsel.

    MDEC Procurement K11-0030-29                                                                                   September 1, 2010
                                                MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                       ATTACHMENT C
                                                  MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 214 of 249
                                                         FUNCTIONAL REQUIREMENTS

                                                                     SPECIALTY COURTS

   ID                                Requirement Text                                           Response Code   Comments
SCO-014.01       Provide ADMIN USER with the ability to define TICKLERS to CASE.        0
SCO-014.02       Provide ADMIN USER with the ability to define rule to creating a seven 0
                 day TICKLER on CASE when a competency evaluation is ordered.

SCO-014.03       Interface to DHMH.                                                         0

SCO-014.04        Provide ADMIN USER with the ability to define reports for seven-day       0
                  tickler.
SCO-014.05        Provide ADMIN USER with ability to define a rule for associating report   0
                  (document) with receiving PARTY.
SCO-015      Provide the ability to generate a report 45 calendar days in advance of the
             one-year anniversary of being found Incompetent and in which defendant
             is currently in treatment (CP 3-106B). )
SCO-015.01        Provide ADMIN USER with ability to define reports for CASEs               0
                  approaching the one-year anniversary on being found incompetent and
                  in which defendant is currently in treatment.
SCO-015.02        Provide ADMIN USER with ability to define a rule for associating report   0
                  (document) with receiving PARTY.
SCO-016      Provide a 1 year tickler report. A report shall be generated 45 calendar
             days in advance of the one-year anniversary of being found Incompetent
             and in which defendant is currently in treatment (CP 3-106B).
SCO-017      Provide a DHMH report that indicates whether an in competency finding is
             a result of mental disorder or mental retardation or both. The system must
             be able to indicate: INCOMPETENT-Mental disorder and INCOMPETENT-
             Mental retardation.
SCO-017.01        Provide USER with the ability to assign an indicator to CASE indicating   0
                  Incompetent-mental disorder or Incompetent-mental retardation.
SCO-017.02        Provide USER with the ability to produce Report for CASE showing          0
                  whether competency findings are as a result of mental disorder or
                  mental retardation.
SCO-018      Ability to indicate defendant as ‗Civilly Committed‘ (to support stats
             requested).

SCO-018.01        Provide USER with the ability to assign an indicator to PARTY             0
                  indicating that the party is "Civilly Committed".
SCO-019      Ability to control work flow based on the problem solving court programs:
             truancy court, drug court, mental health court.
   MDEC Procurement K11-0030-29                                                                                    September 1, 2010
                                                MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                  MARYLAND ELECTRONIC COURT PROCUREMENT                            Page 215 of 249
                                                         FUNCTIONAL REQUIREMENTS

                                                                     SPECIALTY COURTS

   ID                                        Requirement Text                                  Response Code   Comments
SCO-019.01        Provide USER with the ability to define workflow for the individual      0
                  problem solving court programs by court level and location.
SCO-020      Ability to flags cases at intake as potential problem solving court
             candidates and provide the ability to list/print these cases for evaluation
             later.
SCO-020.01        Provide USER with the ability to assign an indicator to CASE when the    0
                  case should be considers as a potential problem solving court
                  candidate.
SCO-021      Ability to capture statistics surrounding problem solving activities.
SCO-021.01        Provide ADMIN USER with the ability to define fields for querying        0
                  CASE records where cases have problem solving court activities
                  (presence of indicators).
SCO-021.02        Provide USER with the ability to search CASES having problem             0
                  solving court activities (presence of indicators).
SCO-022      Ability to capture when offers for participation to problem solving court
             programs is denied by the participates.
SCO-022.01        Provide USER with the ability to assign an indicator to CASE/PARTY       0
                  reflecting denial of participation in problem solving court programs.

SCO-023    Ability to relate documents to a specific referral (e.g. allow the judge to
           review all mental health documents together).
SCO-023.01      Provide USER with the ability to assign DOCUMENT to one or many            0
                REFERRALS.
SCO-024    Ability to capture results of problem solving court activities (e.g.
           terminations, graduations, denials, etc).
SCO-024.01      Provide USER with the ability to assign an indicator to CASE/PARTY         0
                reflecting problem solving court disposition milestones (terminations,
                graduations, denials, etc).
SCO-024.02       Provide USER with the ability to assign a date that the problem solving   0
                 court track was offered.
SCO-024.03       Provide USER with the ability to assign a date that the problem solving   0
                 court track was accepted or refused.
SCO-024.04       Provide USER with the ability to assign the acceptance or refusal of      0
                 the specialty court track.
SCO-024.05       Automate HISTORY of all solving court activities (offer,                  0
                 acceptance/refusal, review hearings, outcomes).

    MDEC Procurement K11-0030-29                                                                                  September 1, 2010
                                                MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                    ATTACHMENT C
                                                  MARYLAND ELECTRONIC COURT PROCUREMENT                          Page 216 of 249
                                                         FUNCTIONAL REQUIREMENTS

                                                                    SPECIALTY COURTS

   ID                                       Requirement Text                                 Response Code   Comments
SCO-025    Ability to utilize indicators in the development of court orders for judicial
           officers.
SCO-025.01      Provide USER with the ability to produce DOCUMENT[order] using           0
                problem solving court indicators.
SCO-026    Ability to schedule events in cases regardless of referral status.
SCO-026.01      Provide USER with the ability to assign SCHEDULED EVENT to CASE 0
                when the case is NCR, closed or has a probation disposition.
SCO-027    Ability to specify who received notices of scheduled events. (e.g. specify
           for batch processing or on demand at printing).
SCO-027.01      Provide USER with the ability to assign recipients to DOCUMENTS.         0
SCO-028    Ability to capture sanctions, and release from sanctions(e.g. incarcerations,
           electronic monitoring, etc).
SCO-028.01      Provide USER with the ability to assign sanctions(e.g. incarceration,    0
                electronic monitoring, etc.) to PARTY as a result of Problem Solving
                activities.
SCO-029    Ability to track all credit for time served.
SCO-029.01      Provide USER with the ability to assign credit for time serve to         0
                SENTENCE.




    MDEC Procurement K11-0030-29                                                                                September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                        ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                              Page 217 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                                         MISCELLANEOUS

     ID                                     Requirement Text                                      Response Code   Comments
MIS-001      Maintain a long-term history of relationships (family, cohabitants) of
             individuals and their case involvement, with applicable addresses,
             including start and end date.
MIS-001.01        AUTOMATICALLY maintain a complete history of PERSONS and their              0
                  relationships to other PERSONS.
MIS-001.02        AUTOMATICALLY maintain a complete history of PERSONS and their              0
                  role(s) in a CASE.
MIS-001.03        AUTOMATICALLY maintain a complete history of ADDRESSES for a                0
                  PERSON.
MIS-001.04        Provide USER with the ability to assign a start and end date(s) to          0
                  PERSON to PERSON associations.
MIS-001.05        Provide USER with the ability to assign a start and end date(s) to          0
                  PERSON to CASE associations.
MIS-001.06        Provide USER with the ability to assign a start and end date(s) to          0
                  PERSON to ADDRESS associations.
MIS-002      Provide access to data on residential neighborhoods, e.g. local factors that
             influence decision making.
MIS-002.01        Provide ADMIN USER with the ability to format and structure external        0
                  data on residential neighborhoods.
MIS-002.02        Provide USER with the ability to retrieve data on residential               0
                  neighborhood(s) from external sources.
MIS-003      Provide alerts or ticklers that signal any new involvement of a client with
             the courts anywhere in the State.
MIS-003.01        AUTOMATICALLY INTERFACE with other agencies.                                0
MIS-003.02        Provide USER with the ability to retrieve data on client(s) from external   0
                  sources.
MIS-004      Provide features that prevent information overload and help an individual
             user set related preferences.
MIS-004.01        Provide USER with the ability assign personal workstation preferences.      0
MIS-005      Provide the ability to automatically notify MVA.
MIS-005.01       Provide ADMIN USER with the ability to subscribe to certain events           0
                 and information required by the MVA.
MIS-005.02       AUTOMATICALLY publish information subscribed to for the MVA.                 0
MIS-006      Provide the ability to allow all agencies involved with a case to be able to
             share information electronically.
MIS-006.01       Provide ADMIN USER with the ability to subscribe to any event or             0
                 information produced by the system.
    MDEC Procurement K11-0030-29                                                                                     September 1, 2010
                                           MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS   ATTACHMENT C
                                             MARYLAND ELECTRONIC COURT PROCUREMENT         Page 218 of 249
                                                    FUNCTIONAL REQUIREMENTS

                                                                 MISCELLANEOUS
MIS-006.02    AUTOMATICALLY publish in near real time subscribed information to      0
              a subscriber.
MIS-006.03    Provide ADMIN USER with the ability to subscribe to external events.   0
MIS-006.04    Provide ADMIN USER with the ability to map subscribed external data    0
              to system data.
MIS-006.05    AUTOMATICALLY assign in near real time data from external sources      0
              based on mapping rules.
MIS-006.06    Provide ADMIN USER with the ability to define query and fields for     0
              batch exports of system data.
MIS-006.07    Provide ADMIN USER with the ability to schedule batch exports.         0
MIS-006.08    Provide ADMIN USER with the ability to map external data to system     0
              data for batch imports of external data.
MIS-006.09    Provide ADMIN USER with the ability to schedule batch imports.         0




    MDEC Procurement K11-0030-29                                                          September 1, 2010
                                                   MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                            ATTACHMENT C
                                                     MARYLAND ELECTRONIC COURT PROCUREMENT                                  Page 219 of 249
                                                            FUNCTIONAL REQUIREMENTS

                                                                                COMPLIANCE

     ID                                      Requirement Text                                            Response Code   Comments
COM-001      Obtain information from other system functions (e.g., Hearings, Adjudication, and
             Disposition, accounting, Juvenile Court Support functions) to permit court to track
             and assess compliance.
COM-001.01         Subscribe to external compliance events and automatically assign              0
                   compliance information to a CASE or PERSON.
COM-001.02         Provide USER the ability to assign compliance information                     0
                   to a CASE or PERSON.
COM-001.03         Provide ADMIN USER the ability to define rules for assigning compliance       0
                   information based on information collected in other functional groups.
COM-002      Track program compliance and status for cases with post-judgment activities and
             for related cases and persons. (see Management and Statistical Reports Function)

COM-002.01       Provide ADMIN USER the ability to define field(s) for querying program              0
                 compliance on CASES and/or PERSONS that have post-judgment activities.

COM-002.02         Provide ADMIN USER the ability to define fields(s) that are displayed for         0
                   program compliance on CASES and/or PERSONS that have post-judgment
                   activities.
COM-002.03         Provide USER the ability to search for program compliance on CASES and/or         0
                   PERSONS that have post-judgment activities.
COM-003      Ability to track partial compliance of sentencing conditions (e.g., partial community
             service, traffic school, alcohol school, AA).
COM-003.01         Provide USER the ability to assign partial compliance information of              0
                   sentencing conditions.
COM-003.02         Provide USER the ability to search for partial compliance of sentencing           0
                   conditions.
COM-003.03         Provide ADMIN USER the ability to define field(s) for querying partial            0
                   compliance of sentencing conditions.
COM-003.04         Provide ADMIN USER the ability to define field(s) that are displayed in partial   0
                   compliance of sentencing.
COM-004      Electronically distribute post-conviction information (e.g., documents and data) in
             accordance with state and local statutes, rules, or procedures (e.g., to law
             enforcement, DMV services, and corrections).
COM-004.01         Automatically publish electronically post-conviction information, including       0
                   DOCUMENT meta data to subscriber.
COM-004.02         Provide ADMIN USER the ability to subscribe to post-conviction events or          0
                   activities.
COM-005      Automatically update register of action.



     MDEC Procurement K11-0030-29                                                                                          September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS       ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT             Page 220 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                             COMPLIANCE
COM-005.01         Automatically assign compliance information to REGISTER OF ACTION             0
                   according to defined business rules.
COM-006      Ability to track compliance with family law services (e.g. co-parenting,
             psychologicals, home study, parenting coordination).
COM-006.01         Subscribe to external family law compliance events and automatically assign   0
                   compliance information to a CASE or PERSON.
COM-006.02         Provide USER the ability to assign family law compliance information to a     0
                   CASE or PERSON.
COM-006.03         Provide USER the ability to search for family law compliance.                 0
COM-006.04       Provide ADMIN USER the ability to define field(s) for querying family law       0
                 compliance.
COM-006.05       Provide ADMIN USER the ability to define field(s) that                          0
                 are displayed in family law compliance.
COM-007      System should alert users when scheduling causes case to be out of compliance
             with the time standards.
COM-007.01        Automatically alert USER when a scheduling causes a CASE to be out of          0
                  compliance with time standards.




     MDEC Procurement K11-0030-29                                                                    September 1, 2010
                                                     MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                    ATTACHMENT C
                                                       MARYLAND ELECTRONIC COURT PROCUREMENT                          Page 221 of 249
                                                              FUNCTIONAL REQUIREMENTS

                                                                                 E-FILING
     ID                                       Requirement Text                                      Response Code   Comments
ECF 4.0 General
EFI-001      Provide E-File components that implement the ECF 4.0 core specification ( ECF
             4.0 compliant).
ECF Filing Assembly
EFI-002      Provide the E-File User with the ability to send electronic document(s) and a
             filing message to the court.
EFI-003      Provide E-Filer User with the ability to assign electronic Document to one or
             many CASES.
EFI-004      Provide the E-File User with the ability to electronically serve other existing
             parties on the case who are registered to receive service electronically.
EFI-005      Provide the E-File User with the ability to electronically serve other existing
             parties on the case when other existing parties have other vendor
             implementations of the Legal Service component.
EFI-006      Provide the E-File User with the ability to receive and process return responses
             from the court.
EFI-007      Provide the E-File User with the ability to electronically pay court fees, fines and
             other financial obligations.
EFI-008      Automatically validates information including, but not limited to, case number,
             filing parties, case types, document types, and other elements in accordance
             with court codes.
EFI-009      Automatically provides error messages and correction options if the filing is not
             in accordance with court policies, codes, and requirements including case
             openings.
EFI-010      Provides E-File User the ability to designate shielding of sensitive or confidential
             information.
EFI-011      Automatically deliver certificate of service electronically, indicating which
             participants were served electronically and which participants were served
             manually.
EFI-012      Provide E-File User to set default values, i.e. court, type of suit, plaintiff, etc.
ECF Legal Service
EFI-013      Provide E-Filer with the ability to receive electronic service from other parties in
             a case.
ECF Filing Review
EFI-014      Automatically receive electronic filings from multiple vendor implementations.
EFI-015      Provide Admin User the ability to electronically maintain court policies and rules
             for E-Filing.


       MDEC Procurement K11-0030-29                                                                                  September 1, 2010
                                                  MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                     ATTACHMENT C
                                                    MARYLAND ELECTRONIC COURT PROCUREMENT                           Page 222 of 249
                                                           FUNCTIONAL REQUIREMENTS

                                                                               E-FILING
    ID                                      Requirement Text                                      Response Code   Comments
EFI-016    Provide Admin User with the ability to define codes for electronic filings types
           based on filing metadata, case type, case category, case sub category.
EFI-017    Provide Admin user with the ability to define rule for establishing different filing
           review queues based on filing metadata, case type, case category, case sub
           category.
EFI-018    Provide Admin User the ability to define rules for accepting or rejecting an
           electronic filing automatically.
EFI-019    Provide Review Clerk with the ability to review electronic payment information
           submitted with the filing.
EFI-020    Automatically accept or reject an electronic filing based on rules.
EFI-021    Provide Review Clerk the ability to view electronic filing metadata.
EFI-022    Provide Review Clerk the ability to view the electronic documents.
EFI-023    Provide Review Clerk the ability to accept or reject an electronic filing.
EFI-024    Provide Review Clerk the ability view all electronic filings that were automatically
           accepted or rejected.
EFI-025    Provide Admin User the ability to define additional data entry fields for the file
           review process.
EFI-026    Provide Review Clerk the ability to assign review information and comments to
           any preconfigured fields.
EFI-027    Automatically send a return message to an E-file user confirming the court‘s
           receipt of an electronic filing.
EFI-028    Automatically construct electronic return messages from preconfigured fields.
EFI-029    Automatically notify an E-file user electronically when there is an error accepting
           document[s] and the reason[s] why.
EFI-030    Provide Admin user the ability to define codes for Rejection Reasons.
EFI-031    Provide Admin user to the ability to define rules to determine what electronic
           documents should initiate a new case.
EFI-032    Provide E-Filer User the ability to check on the status of a filing.
EFI-033    Provide E-Filer user the ability to query on the court rules and requirements for
           electronic filing.
EFI-034    Automatically send to the Court Record component that the e-filing has been
           reviewed and accepted.
EFI-035    Automatically receive from the Court Record component that the filing has been
           entered into the Court Record.
EFI-036    Automatically notify an E-file user electronically when the filing has been
           accepted and entered into the Court Record.
EFI-037    Include capability to place visible file stamp on filed document.

      MDEC Procurement K11-0030-29                                                                                 September 1, 2010
                                                     MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                    ATTACHMENT C
                                                       MARYLAND ELECTRONIC COURT PROCUREMENT                          Page 223 of 249
                                                              FUNCTIONAL REQUIREMENTS

                                                                                 E-FILING
     ID                                       Requirement Text                                      Response Code   Comments
EFI-038     Provide the ability to can accept various file and media types and provides a
            method for handling other electronic materials involved in a case, including,
            e.g., transcript, exhibits, and multimedia presentations.
EFI-039     Automatically provide a means to verify the integrity of any electronic document
            received and stored by the court.
EFI-040     Automatically provide an audit log of transactions as appropriate to the court‘s
            needs.
EFI-041     Provide Admin User with the ability to control user privileges to create, modify,
            delete, print, or read electronic records.
EFI-042     Automatically complies with statutes and rules for authentication of electronic
            documents.
EFI-043     Automatically provides authentication of filer identity in accordance with court
            policies.
EFI-044     Provide User the ability to change the confidentiality status for documents or the
            case during the life of the case.
EFI-045     Provide Admin User the ability to define rules for automatically setting a
            document as confidential.
EFI-046     Automatically set confidentiality at the time of electronic document filing in
            accordance with statutes and rules or court orders.
EFI-047     Automatically accommodates payments in accordance with statutes and rules,
            including ability to report on documents rejected for failure to pay.
EFI-048     Provide User with alerts on filings or document entries as appropriate (or entry
            in a work queue) when action on a filing is required.
EFI-049     Provide User the ability to turn filing off for a specific user or require review for
            specific party.
ECF Court Record
EFI-050     Provide Admin user the ability to define rules to determine what electronic
            documents create what docket entry.
EFI-051     Automatically receive electronic documents from the Filing Assembly and index
            into the Document Management System.
EFI-052     Automatically index redacted versions of electronic documents in the Document
            Management System.
EFI-053     Automatically initiate a Case and assign Case field data with message data
            received from the Filing Review component.
EFI-054     Automatically assign Case data to an existing Case with message data received
            from the Filing Review component.
EFI-055     Automatically notify the Filing Assembly component that an electronic document
            has been recorded into the official records.

       MDEC Procurement K11-0030-29                                                                                  September 1, 2010
                                                     MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                        ATTACHMENT C
                                                       MARYLAND ELECTRONIC COURT PROCUREMENT                              Page 224 of 249
                                                              FUNCTIONAL REQUIREMENTS

                                                                                  E-FILING
     ID                                         Requirement Text                                        Response Code   Comments
EFI-056       Provide E-Filer user with the ability to query PARTY notification preference.
EFI-057       Provide E-Filer user the ability to query for names and addresses of parties in a
              case who must be served.
EFI-058       Provide E-Filer user the ability to query court for data and documents held within
              the system and return the appropriate response.
EFI-059       Provide the ability to process electronic payments to the Accounting module.
EFI-060       Automatically creates and dockets in the court‘s case management system a
              certificate of service for the document served.
EFI-061       Automatically provides for archiving of data and documents in accordance with
              approved retention, archiving and destruction policies.
Related E-Filing Services
EFI-062       Provide a method for parties to transmit proposed orders and other proposed
              materials to judicial officers or clerks for consideration, with or without docketing
              the event and committing the document and data to the database.
EFI-063       Provide User [Judicial officer or clerk] to return a modified proposed document
              to the sending parties with or without docketing the event and committing the
              data to the database.
EFI-064       Provide User the ability to deliver case documents for entry and retrieval into the
              court‘s electronic Document Management System and Case Management
              System with ―one-click‖ methods that do not require duplicative work on the part
              of court clerks for record entry into or retrieval from case management or
              document management systems.
EFI-065       Provide user with the ability to assign annotations that are not part of the court
              record, with appropriate confidentiality and access controls (including
              restrictions on who can talk to whom).
EFI-066       Provide the ability to have actor-to-actor communication that is not part of the
              court record, with appropriate confidentiality and access controls.
EFI-067       Automatically keep batches together throughout entire writ process, including
              checking status of individual cases, batch dismissals, and batch filing of writs.
EFI-067.01         Provide E-Filer user with the ability to assign batch identifiers to bulk        0
                   transmissions so that status checking can occur on many cases at one time.

EFI-068        Provide User with dismissal functionality - Allow attorneys to dismiss cases prior
               to hearing; Allow online dismissals vs. fax dismissals; Dismiss case via docket
               checkbox, transmit to court; Cancel multiple cases from a hearing at one time.

EFI-068.01         Provide ADMIN USER with the ability to define rule for allowing attorneys to 0
                   dismiss.
        MDEC Procurement K11-0030-29                                                                                     September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                   ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                         Page 225 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                                               E-FILING
    ID                                       Requirement Text                                  Response Code   Comments
EFI-069    Allow filer to opt in/out of email types, such as case is continued, dismissed,
           write is filed, service, judgments.
EFI-070    Provide ability for law enforcement to bulk enter docket entry.
EFI-071    Integrate with law enforcement handheld devices for return of service.
EFI-072    System provides automatic notice to all parties when filer sends a proposed
           order to a judicial officer for consideration.
EFI-073    System provides automatic notice to all parties when the judicial officer returns
           a modified proposed document to the sending parties.
EFI-074    The system provides the record on bind over or transfers to another court from
           the electronic record in accordance with statutes and rules.
EFI-075    System provides for forward migration of all court documents.




      MDEC Procurement K11-0030-29                                                                              September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                       ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 226 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                                                FORMS

     ID                                     Requirement Text                                      Response Code   Comments
FOR-001      Ability to quickly and easily replicate hardcopy forms in an online format.
FOR-001.01        Provide USER [Form Creator] with the ability to easily and quickly take     0
                  a hardcopy form and convert it to an online form.
FOR-002      Provide an easy to use interface for the creation of forms.
FOR-002.01        Provide USER [Form Creator] with easy interface for creating forms.         0
FOR-002.02        Provide USER [Form Creator] with the ability to define output type for      0
                  the forms e.g PDF, email. Text.
FOR-002.03        Provide USER [Form Creator] with the ability to assign                      0
                  ACCESS/SECURITY level for the form.
FOR-002.04        Provide USER [Form Creator] with the ability to define scope (local or      0
                  enterprise) for DEPLOYMENT of form.
FOR-002.05        Provide USER [Form Creator] with the ability to use and relate any          0
                  table and field to create a form.
FOR-003      The forms tool should not require programming knowledge for form
FOR-003.01   creation.
                  Provide USER [Form Creator] with the ability to create forms without        0
                  programming.
FOR-004      Provide an unlimited number of forms that can be created.
FOR-004.01        Provide USER [Form Creator] with the ability to create unlimited            0
                  number of forms.
FOR-005      Ability to create templates for certain kinds of forms that may vary slightly
             by case type.
FOR-005.01        Provide USER [Form Creator] with the ability to create templates for        0
                  forms that may vary slightly by case type.
FOR-005.02        Provide ADMIN USER with the ability to define codes to associate            0
                  FORM Codes with CASE type.
FOR-005.03        Provide USER [Form Creator] with the ability to assign one or more          0
                  case types to a FORM Code.
FOR-006      Ability to display the form throughout every step of the creation process.
FOR-006.01       Provide USER [Form Creator] with the ability to preview the form while 0
                 creating it.
FOR-007      Allow forms to contain more than just basic text and entry fields using a
             variety of useful data types.
FOR-007.01       Provide USER [Form Creator] with the ability to add more than just           0
                 basic text and entry fields utilizing various useful data types.
FOR-008      Incorporate basic formatting capabilities like boldface, underline, italicize,
             or even change text colors.
    MDEC Procurement K11-0030-29                                                                                    September 1, 2010
                                               MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                     ATTACHMENT C
                                                 MARYLAND ELECTRONIC COURT PROCUREMENT                           Page 227 of 249
                                                        FUNCTIONAL REQUIREMENTS

                                                                           FORMS

     ID                                      Requirement Text                                 Response Code   Comments
FOR-008.01        Provide USER [Form Creator] with the ability to use basic               0
                  FORMATTING capabilities like boldface, underline, italicize, font size
                  and color.
FOR-009      The system forms tool should be object oriented to enable standardizations
             and reusability of form components.
FOR-009.01        Provide USER [Form Creator] with the ability and to create user-        0
                  defined components that are composites of existing components for
                  reuse.
FOR-010      Enable the use of checkboxes, radio buttons, drop-down lists.
FOR-010.01        Provide USER [Form Creator] with the ability to incorporate multiple    0
                  choice lists, checkboxes, radio buttons, drop-down lists.
FOR-011      Ability to set the limit on the number of characters entered in a text entry
             field, or AUTOMATICALLY count the number of characters in a text box.

FOR-011.01       Provide USER [Form Creator] with the ability to limit the number of     0
                 characters entered in a text field.
FOR-012      Provide a simple interface for creating mouse-over instructions and other
             form help documentation.
FOR-012.01       Provide USER [Form Creator] with the ability to access a simple         0
                 interface for creating mouse-over instructions and other help
                 documentation.
FOR-013      Should ensure that data entry formats are enforces to database constraints.

FOR-013.01       Provide USER [Form Creator] with the ability to specify the data entry 0
                 formats using actual database constraints.
FOR-014      Should enable creators to set alerts to the formats of dates, email address,
             decimal numbers, monetary amounts, and whole numbers or other data
             types.
FOR-014.01       Provide USER [Form Creator] with the ability to add custom alert         0
                 messages for validations on data type formats such as decimals, email
                 address and money etc..
FOR-015      Should enable creators to set validations for required fields.
FOR-015.01       Provide USER [Form Creator] the ability to define validation criteria on 0
                 required fields
FOR-016      Should allow creators to add new content, edit existing content, or delete
             content from forms with the click of a button.


    MDEC Procurement K11-0030-29                                                                                September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                        ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                              Page 228 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                                               FORMS

     ID                                       Requirement Text                                     Response Code   Comments
FOR-016.01        Provide USER [Form Creator] with the ability to add, edit or delete          0
                  form content by using the mouse.
FOR-017      Should enable creator to add a file upload or attachment capability to a
             form.
FOR-017.01        Provide USER [Form Creator] with the ability to add a file upload or         0
                  attachment component to form.
FOR-017.02        Provide USER with the ability to easily electronic file the forms that are   0
                  published online.
FOR-018      Ability to easily publish forms.
FOR-018.01        Provide USER [Form Creator] with the ability to easily deploy forms for      0
                  integration with Case Management.
FOR-018.02        Provide USER [Form Creator] with the ability to easily publish online e-     0
                  fillable forms [e-filled online].
FOR-018.03        Provide USER [Form Creator] with the ability to easily publish online        0
                  fillable forms [filled online and then printed].
FOR-018.04        Provide USER [Form Creator] with the ability to easily publish online        0
                  manual forms [printed and then filled manually].
FOR-019      Ensures published forms are ADA compliant.
FOR-019.01        Provide USER [Form Creator] with the ability to verify publish forms         0
                  are ADA compliant.
FOR-020      Provide flexible publishing options, hard copy, online copy, in multiple
             languages.
FOR-020.01        Provide USER [Form Creator] with the ability to choose publishing            0
                  options ( online, hardcopy).
FOR-020.02        Provide USER [Form Creator] with the ability to choose multiple              0
                  language options.
FOR-021      Ability to publish online help documentation.
FOR-021.01        Provide USER [Form Creator] with the ability to publish online help          0
                  documentation.
FOR-022      Manage the inventory of forms.
FOR-022.01        Provide USER [Form Creator] with the ability to easily manage                0
                  inventory of forms.
FOR-023      Manage version control.
FOR-023.01        Provide USER [Form Creator] with the ability to easily manage                0
                  versioning of forms.
FOR-024      Ability to set the start and end dates for the availability of forms.


    MDEC Procurement K11-0030-29                                                                                     September 1, 2010
                                              MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                     ATTACHMENT C
                                                MARYLAND ELECTRONIC COURT PROCUREMENT                           Page 229 of 249
                                                       FUNCTIONAL REQUIREMENTS

                                                                           FORMS

     ID                                   Requirement Text                                   Response Code   Comments
FOR-024.01       Provide USER [Form Creator] with the ability to set availability and    0
                 expiration dates of the forms.
FOR-025      Allow system to assign unique tracking for certain forms. (e.g. DC/CR 2 -
             Statement of Charges, Police Form)
FOR-025.01       Provide USER [Form Creator] with the ability to assign a unique code    0
                 to the form. All Forms within a unique code should be sequenced.

FOR-025.02       Provide USER [Form Creator] with the ability to group and associate     0
                 related forms based on their probable runtime use together.
FOR-026      Provide and authenticate electronic signatures based on an industry-
             standard protocol that provides document integrity.
FOR-026.01       Provide USER [Form Creator] with the ability to provide and             0
                 authenticate electronic signatures based on an industry-standard
                 protocol that provides document integrity.




    MDEC Procurement K11-0030-29                                                                               September 1, 2010
                                                MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                       ATTACHMENT C
                                                  MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 230 of 249
                                                         FUNCTIONAL REQUIREMENTS

                                                                           BAIL BONDS

    ID                                  Requirement Text                                         Response Code   Comments
BBO-001      Capture and maintain data on bail hearings (i.e. bail setting) , by judge or
             commissioner. Include date of hearing, defendant's eligibility for bail, bail
             amount required, requirements for certain type of bond to be posted ( ex.
             Cash bond), percentage acceptable or minimum amount, judge and/or
             commissioner ID and special conditions of release.
BBO-001.01      Provide ADMIN USER with the ability to define codes for the                  0
                DEFENDANT'S eligibility for bail (Held without bail, held in default of
                bond, etc.).
BBO-001.02      Provide ADMIN USER with the ability to define codes for different            0
                types of bonds (cash, corporate, unsecured, etc.).
BBO-001.03      Provide ADMIN USER with the ability to define codes for JUDGE ids.           0
BBO-001.04      Provide ADMIN USER with the ability to define codes for                      0
                COMMISSIONER ids.
BBO-001.05      Provide USER with the ability to assign eligibility for bail to the          0
                DEFENDANT.
BBO-001.06      Provide USER with the ability to assign the required type of bond to be      0
                posted to the Bond.
BBO-001.07      Provide USER with the ability to assign the date of the bail hearing to      0
                the Bail.
BBO-001.08      Provide USER with the ability to assign the amount of bail to be posted      0
                to the Bail.
BBO-001.09      Provide USER with the ability to assign the minimum amount of bail to        0
                be posted to the Bail.
BBO-001.10      Provide USER with the ability to choose codes for the judge id.              0
BBO-001.11      Provide USER with the ability to choose codes for the commissioner id.       0

BBO-001.12        Provide USER with the ability to assign special conditions of release to   0
                  the Bail.
BBO-002      Capture the pre-set bail amount ordered by a judge and/or the indication
             that the bail is to be set by a commissioner when a warrant is issued.
             Relate that bail amount to the warrant.
BBO-002.01        Provide USER with the ability to assign bail requirements to               0
                  WARRANTS.
BBO-002.02        Provide USER with the ability to assign a pre-set bail amount to a         0
                  WARRANT.
BBO-002.03        Provide USER with the ability to choose the judge id for a WARRANT.        0


    MDEC Procurement K11-0030-29                                                                                   September 1, 2010
                                               MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                     ATTACHMENT C
                                                 MARYLAND ELECTRONIC COURT PROCUREMENT                           Page 231 of 249
                                                        FUNCTIONAL REQUIREMENTS

                                                                        BAIL BONDS

    ID                                      Requirement Text                                  Response Code   Comments
BBO-002.04        Provide USER with the ability to indicate when bail is to be set by a   0
                  COMMISSIONER when DEFENDANT is arrested.
BBO-003      Relate bail bond settings and postings to warrants and other bail bond
             related documents(e.g. . Releases, notice of forfeitures, declaration of
             trust, bail bond).
BBO-003.01        Provide ADMIN USER with the ability to assign a bail setting to         0
                  WARRANTS.
BBO-003.02        Provide ADMIN USER with the ability to assign one or more bond          0
                  postings to bail settings.
BBO-003.03        Provide ADMIN USER with the ability to define rules to relate           0
                  DOCUMENTS (notice of forfeiture, declaration of trust, releases) to
                  bonds.
BBO-003.04        Automatically link all DOCUMENTS[bail bond] on a CASE.                  0
BBO-003.05        Provide USER with the ability to assign relationships with all          0
                  DOCUMENTS[bail bond].
BBO-004      Generate a unique ID number (USER defined by type) for each new surety
             insurer, bail bondsmen, property surety, and property agent upon entry in
             the system (allow for acceptance of data in current Bondsmen System).

BBO-004.01       Provide ADMIN USER with the ability to define unique ID numbers for      0
                 each surety INSURER.
BBO-004.02       Provide ADMIN USER with the ability to define unique ID numbers for      0
                 each bail bondsman.
BBO-004.03       Provide ADMIN USER with the ability to define unique ID numbers for      0
                 each PROPERTY SURETY.
BBO-004.04       Provide ADMIN USER with the ability to define unique ID numbers for      0
                 each PROPERTY AGENT.
BBO-004.05       Provide ADMIN USER with the ability to define codes for the type of      0
                 SURETY (corporate, property, mom and pop).
BBO-004.06       Provide USER with the ability to assign a SURETY COMPANY to a            0
                 bond.
BBO-004.07       Provide USER with the ability to assign a bondsmen to a bond.            0
BBO-004.08       Provide USER with the ability to assign a PROPERTY SURETY to a           0
                 bond.
BBO-004.09       Provide USER with the ability to assign a PROPERTY AGENT to a            0
                 bond.


    MDEC Procurement K11-0030-29                                                                                September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                        ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                              Page 232 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                                            BAIL BONDS

    ID                                     Requirement Text                                        Response Code   Comments
BBO-005      Print, display and centrally maintain a list of licensed bail bondsmen in the
             state of Maryland. Include ID number, Maryland Insurance ID, name,
             address, phone numbers, type of bail bondsmen (corporate, property),
             expiration date of license, and status(based on information received from
             Maryland Insurance Administration, cancellation of agent's authorization,
             default, etc.).
BBO-005.01       Provide USER with the ability to assign Maryland Insurance ID to a            0
                 licensed bondsman.
BBO-005.02       Provide USER with the ability to assign a name to a licensed                  0
                 bondsman.
BBO-005.03       Provide USER with the ability to assign an address to a licensed              0
                 bondsman.
BBO-005.04       Provide USER with the ability to assign a type of bondsman to a               0
                 licensed bondsman.
BBO-005.05       Provide USER with the ability to assign a license expiration date to a        0
                 licensed bondsman
BBO-005.06       Provide USER with the ability to assign a status to a licensed                0
                 bondsman
BBO-005.07       Provide ADMIN USER with the ability to define field(s) for querying           0
                 licensed bail bondsman
BBO-005.08       Provide ADMIN USER with the ability to define field(s) that are               0
                 displayed in the search results.
BBO-005.09       Provide USER with the ability to search for licensed bail bondsman.           0
BBO-005.10       Provide USER with the ability to produce a report of licensed bail            0
                 bondsmen in the state of Maryland.
BBO-005.11       Provide ADMIN USER with the ability to define a central repository of         0
                 licensed bail bondsmen
BBO-006      Print, display and centrally maintain a list of surety insurers in the state of
             Maryland. Include company name, surety insurer ID, address, phone
             numbers, contact persons and Federal ID Number (for refunds).
BBO-006.01       Provide USER with the ability to assign a company name to SURETY              0
                 INSURERS.
BBO-006.02       Provide USER with the ability to assign an address to a SURETY                0
                 INSURER.
BBO-006.03       Provide USER with the ability to assign a phone number to a SURETY            0
                 INSURER.


    MDEC Procurement K11-0030-29                                                                                     September 1, 2010
                                                MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                       ATTACHMENT C
                                                  MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 233 of 249
                                                         FUNCTIONAL REQUIREMENTS

                                                                           BAIL BONDS

    ID                                     Requirement Text                                      Response Code   Comments
BBO-006.04       Provide USER with the ability to assign contact persons to a SURETY         0
                 INSURER.
BBO-006.05       Provide USER with the ability to assign a Federal ID number to a            0
                 SURETY INSURER.
BBO-006.06       Provide ADMIN USER with the ability to define field(s) for querying         0
                 SURETY INSURERS.
BBO-006.07       Provide ADMIN USER with the ability to define field(s) that are             0
                 displayed in the search results.
BBO-006.08       Provide USER with the ability to search for SURETY INSURERS.                0
BBO-006.09       Provide USER with the ability to produce a report of surety insurers in     0
                 the state of Maryland.
BBO-006.10       Provide USE with the ability to define a central repository of surety       0
                 insurers
BBO-007      Print, display and centrally maintain, for each corporate bondsman, a list of
             surety insurers for which they can post bonds. Include the power number
             and the maximum dollar amount the bondsman is allowed to post.

BBO-007.01       Provide USER with the ability to assign the max dollar amount to the        0
                 bondsman surety relationship.
BBO-007.02       Provide USER with the ability to assign a power number to the               0
                 bondsman surety relationship.
BBO-007.03       Provide ADMIN USER with the ability to define field(s) for querying         0
                 corporate bondsman and the related surety(s).
BBO-007.04       Provide ADMIN USER with the ability to define field(s) that are             0
                 displayed in the search results.
BBO-007.05       Provide USER with the ability to search for bondsman and surety(s).         0
BBO-007.06       Provide USER with the ability to produce a report of corporate              0
                 bondsmen and the surety insurers for which they can post bonds.
BBO-008      Print, display and maintain a list of "registered properties" (properties
             owned by professional property sureties against which they want to post
             bonds). Include Dept. of Assessment and Taxation's account identifier,
             property address and/or legal description and assessed value.
BBO-008.01       Provide ADMIN USER with the ability to define field(s) for querying         0
                 registered properties.
BBO-008.02       Provide ADMIN USER with the ability to define field(s) that are             0
                 displayed in the search results.
BBO-008.03       Provide USER with the ability to search for registered properties.          0

    MDEC Procurement K11-0030-29                                                                                   September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                        ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                              Page 234 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                                            BAIL BONDS

    ID                                      Requirement Text                                       Response Code   Comments
BBO-008.04        Provide USER with the ability to produce a report of registered              0
                  properties by professional property sureties.
BBO-008.05        Include Dept. of Assessment and Taxation's account identifier,               0
                  property address and/or legal description and assessed value.
BBO-009      Print, display and centrally maintain a list of agents who are authorized to
             post bonds on the behalf of a professional property surety.
BBO-009.01        Provide USER with the ability to assign one or more authorized agents        0
                  to a professional property surety
BBO-009.02        Provide ADMIN USER with the ability to define field(s) for querying          0
                  authorized agents and the related professional property surety(s).
BBO-009.03        Provide ADMIN USER with the ability to define field(s) that are              0
                  displayed in the search results.
BBO-009.04        Provide USER with the ability to search for agents and professional          0
                  property surety(s).
BBO-009.05        Provide USER with the ability to produce a report of agents who are          0
                  authorized to post bonds on the behalf of a professional property
                  surety.
BBO-010      Ability to enter a status for surety insurers and property sureties to indicate
             whether bonds should be accepted from them. (ex. Current, revoked,
             suspended, no longer licensed in Maryland, in Bankruptcy/Liquidation).

BBO-010.01       Provide ADMIN USER with the ability to define codes for the status of         0
                 surety insurers.
BBO-010.02       Provide ADMIN USER with the ability to define codes for the status of         0
                 property sureties.
BBO-010.03       Provide ADMIN USER with the ability to define rules to restrict posting       0
                 of bonds by property sureties dependant upon the status of the
                 property surety.
BBO-010.04       Provide USER with the ability to assign the status of surety insurers.        0
BBO-010.05       Provide USER with the ability to assign the status of property insurers.      0

BBO-011      Ability to relate a professional surety (corporate surety insurer or property
             surety) with each bail bondsmen and/or agent authorized to write bonds for
             that surety.
BBO-011.01        Provide USER with the ability to assign one or more bail bondsman to 0
                  a surety insurer


    MDEC Procurement K11-0030-29                                                                                     September 1, 2010
                                                MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                        ATTACHMENT C
                                                  MARYLAND ELECTRONIC COURT PROCUREMENT                              Page 235 of 249
                                                         FUNCTIONAL REQUIREMENTS

                                                                           BAIL BONDS

    ID                                    Requirement Text                                        Response Code   Comments
BBO-011.02       Provide USER with the ability to assign one or more surety insurers to       0
                 a bail bondsmen.
BBO-011.03       Provide USER with the ability to assign one or more authorized               0
                 AGENTS to a professional property surety.
BBO-012      Provide a status for bail bondsmen and property agents to indicate whether
             they can continue to post bonds for that surety. (ex. Current, revoked,
             suspended, in default).
BBO-012.01       Provide ADMIN USER with the ability to define codes for the status of        0
                 bail bondsmen (current, revoked, suspended, in default).
BBO-012.02       Provide ADMIN USER with the ability to define rules to restrict posting      0
                 of bonds by bondsmen dependant upon the status of the bondsman.

BBO-012.03        Provide USER with the ability to assign the status of bail bondsman         0
BBO-013      Display and/or print reports based on the status and/or specified time
             period (e.g., default, active, suspended, deceased, etc.) of surety insurers,
             bail bondsmen, property sureties, and property agents.
BBO-013.01        Provide ADMIN USER with the ability to define field(s) for querying         0
                  sureties.
BBO-013.02        Provide ADMIN USER with the ability to define field(s) for querying bail    0
                  bondsmen.
BBO-013.03        Provide ADMIN USER with the ability to define field(s) for querying         0
                  PROPERTY agents.
BBO-013.04        Provide ADMIN USER with the ability to define field(s) that are             0
                  displayed in the search results.
BBO-013.05        Provide USER with the ability to search for bondsman and surety(s).         0
BBO-013.06        Provide USER with the ability to produce reports for sureties based on      0
                  the status and/or specified time period .
BBO-014      Restrict posting of property bonds by professional property sureties to
             registered properties only.
BBO-014.01        Provide USER with the ability to assign one or more registered              0
                  properties to professional property sureties.
BBO-014.02        Provide ADMIN USER with the ability to define rules to restrict posting     0
                  of bonds by professional property sureties to registered properties only.




    MDEC Procurement K11-0030-29                                                                                    September 1, 2010
                                                MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                       ATTACHMENT C
                                                  MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 236 of 249
                                                         FUNCTIONAL REQUIREMENTS

                                                                           BAIL BONDS

    ID                                      Requirement Text                                     Response Code   Comments
BBO-015      Capture and maintain data on all property used as collateral for bonds.
             Include owner's names, Dept. of Assessment and Taxation's account
             identifier, property address and/or legal description and assessed value
             and encumbrances. Including accommodation bonds (a.k.a mom and pop
             bonds.)
BBO-015.01        Provide USER with the ability to assign a property to a bond posted.       0
BBO-015.02        Provide USER with the ability to assign an owner's name to                 0
                  PROPERTY.
BBO-015.03        Provide USER with the ability to assign the Dept. of Assessment and        0
                  Taxation's property account identifier to PROPERTY.
BBO-015.04        Provide USER with the ability to assign an address and/or legal            0
                  description of a PROPERTY.
BBO-015.05        Provide USER with the ability to assign the assessed value to              0
                  PROPERTY.
BBO-015.06        Provide USER with the ability to assign one or more bonds posted to a      0
                  PROPERTY.
BBO-016      Print, display and maintain a list of all bonds posted on each property used
             as collateral for bonds. Include date posted, bond amount, case number,
             surety name, address, property identifiers, and total amount secured
             against property.
BBO-016.01        Provide USER with the ability to assign bonds to CASES.                    0
BBO-016.02        Provide ADMIN USER with the ability to define rules to restrict entry of   0
                  bonds on existing CASES only.
BBO-016.03        Provide ADMIN USER with the ability to define field(s) for querying        0
                  bond postings against properties.
BBO-016.04        Provide ADMIN USER with the ability to define field(s) that are            0
                  displayed in the search results.
BBO-016.05        Provide USER with the ability to search for bonds and properties.          0
BBO-016.06        Provide USER with the ability to produce a report of property bonds.       0
BBO-016.07        Include date posted, bond amount, case number, surety name,                0
                  address, property identifiers, and total amount secured against
                  property.
BBO-017      Capture and maintain data on all types of bonds posted. Include bond
             type(e.g. cash, property, personal recognizance, corporate), date posted,
             bond amount, bonding agent, surety company, percent posted, surety
             names, addresses, power number (if applicable), receipt number (if
             applicable), net equity (if applicable).

    MDEC Procurement K11-0030-29                                                                                   September 1, 2010
                                                MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                  MARYLAND ELECTRONIC COURT PROCUREMENT                            Page 237 of 249
                                                         FUNCTIONAL REQUIREMENTS

                                                                         BAIL BONDS

    ID                                      Requirement Text                                    Response Code   Comments
BBO-017.01        Provide ADMIN USER with the ability to define a relationship between      0
                  bonds and PARTIES and/or ASSOCIATED CONTACTS.
BBO-017.02        Provide USER with the ability to choose codes for bond type (case,        0
                  property, personal recognizance, corporate, etc).
BBO-017.03        Provide USER with the ability to assign the date posted on bonds.         0
BBO-017.04        Provide USER with the ability to assign the amount posted.                0
BBO-017.05        Provide USER with the ability to assign a bondsman id to a bond.          0
BBO-017.06        Provide USER with the ability to assign a bonding surety company to a     0
                  bond.
BBO-017.07        Provide USER with the ability to assign the percent posted to a bond.     0
BBO-017.08        Provide USER with the ability to assign a power number to a bond.         0
BBO-017.09        Provide USER with the ability to assign a receipt number to a bond.       0
BBO-018      Indicate whether a forfeited bond was reinstated, include date of
             reinstatement and judge ID, update status of bond.
BBO-018.01        Provide ADMIN USER with the ability to define codes for the status of     0
                  bonds.
BBO-018.02        Provide USER with the ability to assign a date for reinstatement of       0
                  bond.
BBO-018.03        Provide USER with the ability to assign a JUDGE to a reinstatement of     0
                  bond.
BBO-018.04        Provide USER with the ability to assign a status to a bond.               0
BBO-019      Generate docket entries based on all bail processing events.
BBO-019.01        Automatically create DOCKET entries based upon bail hearings.             0
BBO-019.02        Automatically create DOCKET entries based upon bond postings.             0
BBO-019.03        Automatically create DOCKET entries based upon forfeiture of bonds.       0
BBO-020      Allow for multiple surety, bail bondsmen, and property agents names and
             addresses for each bond.
BBO-020.01        Provide USER with the ability to assign one or more sureties to a bond.   0

BBO-020.02       Provide USER with the ability to assign one or more bondsmen to a      0
                 bond.
BBO-020.03       Provide USER with the ability to assign one or more property sureties 0
                 to a bond.
BBO-020.04       Provide USER with the ability to assign one or more property agents to 0
                 a property bond.
BBO-021      Allow for multiple bonds in each singe case.


    MDEC Procurement K11-0030-29                                                                                  September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                        ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                              Page 238 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                                             BAIL BONDS

    ID                                 Requirement Text                                            Response Code   Comments
BBO-021.01       Provide USER with the ability to assign one or more bonds to a CASE. 0

BBO-022      Allow a bond to cover multiple cases (blanket bond) and update all
             associated cases throughout the bond processing.
BBO-022.01       Provide USER with the ability to assign one or more CASE to a bond.           0

BBO-022.02        Automatically create DOCKET entries based upon bail hearings on              0
                  each CASE the bond covers.
BBO-022.03        Automatically create DOCKET entries based upon bond postings on              0
                  each CASE the bond covers.
BBO-022.04        Automatically create DOCKET entries based upon forfeiture of bonds           0
                  on each CASE the bond covers.
BBO-023      Provide for a status of each bond (active, discharged, forfeited,
             surrendered).
BBO-023.01        Provide USER with the ability to assign a status to a bond.                  0
BBO-024      Provide for status updates of the bond when the defendant is surrendered,
             the warrant is served, or the forfeiture is satisfied and maintain a history of
             previous statuses including status date and time.
BBO-024.01        Provide ADMIN USER with the ability to define rules for automatically        0
                  updating the status of a bond depending upon certain activities
                  (posted, defendant surrendered, forfeiture, forfeiture satisfaction).
                  Include status date and time.
BBO-024.02        Automatically maintain a full history of bond status.                        0
BBO-025      Provide the current status date and time of each bond forfeiture (forfeiture
             stricken, satisfied - paid, satisfied - defendant appeared).
BBO-025.01        Provide USER with the ability to assign a status date to a bond.             0
BBO-025.02        Provide USER with the ability to assign a status time to a bond.             0
BBO-026      Ability to track, print, and display forfeited bonds. (allow sorting by surety
             insurer, court location, property surety, forfeiture date).
BBO-026.01        Provide ADMIN USER with the ability to define field(s) for querying          0
                  forfeited bond.
BBO-026.02        Provide ADMIN USER with the ability to define field(s) that are              0
                  displayed in the search results.
BBO-026.03        Provide USER with the ability to search for bonds and properties.            0




    MDEC Procurement K11-0030-29                                                                                     September 1, 2010
                                               MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                     ATTACHMENT C
                                                 MARYLAND ELECTRONIC COURT PROCUREMENT                           Page 239 of 249
                                                        FUNCTIONAL REQUIREMENTS

                                                                        BAIL BONDS

    ID                                     Requirement Text                                   Response Code   Comments
BBO-027      Allow for USER defined ticklers for tracking the 90 day (180 days if
             extended by a judge) forfeiture time period (from the date of the
             defendant's failure to appear) allowing the defendant to satisfy the bond
             without payment of interest.
BBO-027.01       Provide ADMIN USER with the ability to define rules for automatically    0
                 tracking the date a forfeiture must be paid.
BBO-027.02       Automatically notify the USER when a forfeiture due date has passed.     0

BBO-028      Send notices to State's Attorney, bondsman and surety company when a
             bond is forfeited and again if the forfeiture is extended associating all
             documents with the bond.
BBO-028.01      Provide USER with the ability to produce DOCUMENTS (notices)              0
                when a bond is forfeited.
BBO-028.02      Provide USER with the ability to produce DOCUMENTS (notices)              0
                when a bond forfeiture is extended.
BBO-028.03      Provide USER with the ability to assign document (notices) to a Bond.     0

BBO-029      Provide alerts to enter civil JUDGMENT if bond forfeiture is not satisfied
             within time periods allowed by law.
BBO-029.01        Automatically alert the USER when a forfeiture due date has passed.     0
BBO-030      Allow USER to generate a new civil JUDGMENT for an unsatisfied bond
             forfeiture and relate the bond with any new civil CASE number.
BBO-030.01        Provide USER with the ability to assign a civil CASE to a unsatisfied   0
                  bond forfeiture.
BBO-031      Provide for printing on demand of Bail Bond, Affidavit of Bail Bondsmen,
             and Declaration of Trust of Real Estate forms populated with data from the
             case.
BBO-031.01        Provide USER with the ability to produce single DOCUMENTS.              0
BBO-032      Integrate with the Accounting Functions for tracking bond
             deposits(including deposit date, amount, bank account, and payee) and
             disbursements(e.g. refunds).
BBO-032.01        Provide ADMIN USER with the ability to define rule to integrate CASE    0
                  records with Accounting.
BBO-033      Allow for return of bond equity after case adjudication and appeal period
             and document in register of actions.
BBO-033.01        Provide ADMIN USER with the ability to define rule to integrate CASE    0
                  records with Accounting.

    MDEC Procurement K11-0030-29                                                                                September 1, 2010
                                                MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                  MARYLAND ELECTRONIC COURT PROCUREMENT                            Page 240 of 249
                                                         FUNCTIONAL REQUIREMENTS

                                                                           BAIL BONDS

    ID                                       Requirement Text                                   Response Code   Comments
BBO-034           Ability to generate an index and/or provide for recording in Land
                  records of all posted bonds . (index information includes: Property
                  surety or surety insurer, bond posting date, amount, case number (s),
                  current status of the bond (e.g. active, forfeited, released).
BBO-034.01        Interoperability                                                          0
BBO-035      Provide notification to Land records electronically when bond forfeiture is
             satisfied, stricken or closed according to locally defined business rules.
BBO-035.01        Interoperability                                                          0
BBO-036      Provide capability for authorized USERs at DCHQ to create an absolute
             bond forfeiture report, as needed, choose distribution method (e.g., email,
             printed), and format (e.g., pdf, etc.).
BBO-036.01        Provide ADMIN USER with the ability to define field(s) for querying       0
                  forfeited bonds.
BBO-036.02        Provide ADMIN USER with the ability to define field(s) that are           0
                  displayed in the search results.
BBO-036.03        Provide USER with the ability to produce a report of absolute bond        0
                  forfeitures.
BBO-036.04        Provide USER with the ability to choose distribution method of the        0
                  report.
BBO-037      Provide capability for authorized USERs at District and Circuit Court
             locations to print or reprint absolute bond forfeiture reports on an as
             needed basis, after creation by DCHQ.
BBO-037.01        Provide ADMIN USER with the ability to define central repositories for    0
                  search results.
BBO-038      Maintain history on previous bond forfeitures at the case level, defendant
             level, and property surety or surety insurer level.
BBO-038.01        Automatically maintain a full history of bond forfeitures by defendant.   0
BBO-038.02        Automatically maintain a full history of bond forfeitures by surety       0
                  insurer.
BBO-038.03        Automatically maintain a full history of bond forfeitures by property     0
                  surety.
BBO-039      Provide ability to print forfeiture reports by property surety ID and surety
             insurer ID according to USER defined time periods.
BBO-039.01        Provide ADMIN USER with the ability to define field(s) for querying       0
                  bond forfeitures and the related surety(s).
BBO-039.02        Provide ADMIN USER with the ability to define field(s) that are           0
                  displayed in the search results.

    MDEC Procurement K11-0030-29                                                                                  September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                       ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 241 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                                           BAIL BONDS

    ID                                      Requirement Text                                      Response Code   Comments
BBO-039.03        Provide USER with the ability to search for bond forfeitures and            0
                  SURETY(S).
BBO-039.04        Provide USER with the ability to produce a report of bond forfeitures.      0
BBO-040      Ensure system will not allow duplicate entries of a bail bondsmen using the
             same MIA license number. (Bondsmen System currently recognizes if
             license # is in use, and will not allow duplicate entry).
BBO-040.01        Provide ADMIN USER with the ability to assign unique license                0
                  numbers to bondsmen.
BBO-041      Ability to search for bail bondsmen - using name, MIA license #, bail
             bondsmen ID and to search for any surety insurer who authorizes the bail
             bondsmen.
BBO-041.01        Provide ADMIN USER with the ability to define field(s) for querying         0
                  bondsmen.
BBO-041.02        Provide ADMIN USER with the ability to define field(s) that are             0
                  displayed in the search results.
BBO-041.03        Provide USER with the ability to search for bondsmen and related            0
                  SURETY(S)
BBO-042      Allow authorized USERs at DCHQ to enter and update records for surety
             insurer, Bail bondsmen, property agent (including change in status).
BBO-042.01        Provide ADMIN USER with the ability to define rules for access to data      0
                  based upon USER responsibilities
BBO-043      Allow authorized USERS at DCHQ to edit, delete, and update registered
             property records (change assessed value, change bond amount, delete
             bond record entered in error, add bond record not uploaded due to
             technical problem, etc.) and create audit trail to track changes.
BBO-043.01        Provide ADMIN USER with the ability to define rules for access to data      0
                  based upon USER responsibilities.
BBO-044      Allow authorized USERs to generate a report of active civil judgments on
             bond forfeitures by district, court location, and time period.
BBO-044.01        Provide ADMIN USER with the ability to define field(s) for querying civil   0
                  JUDGMENTS on bond forfeitures.
BBO-044.02        Provide ADMIN USER with the ability to define field(s) that are             0
                  displayed in the search results.
BBO-044.03        Provide USER with the ability to search for civil JUDGMENTS.                0




    MDEC Procurement K11-0030-29                                                                                    September 1, 2010
                                                MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                  MARYLAND ELECTRONIC COURT PROCUREMENT                            Page 242 of 249
                                                         FUNCTIONAL REQUIREMENTS

                                                                          BAIL BONDS

    ID                                       Requirement Text                                   Response Code   Comments
BBO-045      Provide ability to search registered properties using predefined identifiers
             and display a list of all outstanding bonds posted that are guaranteed by
             that property (e.g., case number, defendant, bond amount, property
             surety's name, address, and ID, property identifiers, date posted, status of
             bond, total secured amount on property).
BBO-045.01        Provide ADMIN USER with the ability to define field(s) for querying       0
                  registered PROPERTIES.
BBO-045.02        Provide ADMIN USER with the ability to define field(s) that are           0
                  displayed in the search results.
BBO-045.03        Provide USER with the ability to search for registered PROPERTIES         0
                  and related bonds.
BBO-046      Automatically update the list of bonds for registered properties to show
             current status of bond; deduct amounts of bonds that are satisfied or
             closed from aggregate secured amount for registered property.
BBO-046.01        Automatically calculate the secured amount of open bonds for a            0
                  registered PROPERTY.
BBO-046.02        Provide ADMIN USER with the ability to define field(s) for querying       0
                  registered PROPERTIES.
BBO-046.03        Provide ADMIN USER with the ability to define field(s) that are           0
                  displayed in the search results.
BBO-046.04        Provide USER with the ability to search for registered PROPERTIES         0
                  and related bonds.
BBO-047      Allow for consistency of bond entry codes, bond related person entry
             codes, and bond event codes across case types and courts.
BBO-047.01        Provide ADMIN USER with the ability to define codes for types of          0
                  SURETIES.
BBO-047.02        Provide ADMIN USER with the ability to define codes for status of         0
                  bonds.
BBO-048      Ability for authorized USERS (internal and external) to generate and print-
             on-demand a list (sorted alphabetically or by ID) of active surety insurers
             and their authorized bail bondsmen and/or active property sureties with
             authorized property agents for each.
BBO-048.01        Provide ADMIN USER with the ability to define field(s) for querying       0
                  SURETY INSURERS.
BBO-048.02        Provide ADMIN USER with the ability to define field(s) that are           0
                  displayed in the search results.


    MDEC Procurement K11-0030-29                                                                                  September 1, 2010
                                                MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                       ATTACHMENT C
                                                  MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 243 of 249
                                                         FUNCTIONAL REQUIREMENTS

                                                                          BAIL BONDS

    ID                                       Requirement Text                                    Response Code   Comments
BBO-048.03         Provide USER with the ability to search for SURETY INSURERS and           0
                   related bondsmen.
BBO-048.04         Provide USER with the ability to sort on any column in the search         0
                   result screen.
BBO-049      Ability for authorized USERS at DCHQ to enter free-style comments in bail
             bondsmen, property surety and property agent records.
BBO-049.01         Provide USER with the ability to assign one or more COMMENTS to a         0
                   bondsmen.
BBO-049.02         Provide USER with the ability to assign one or more COMMENTS to a         0
                   PROPERTY SURETY.
BBO-050      Ability to store secure notes viewable only by authorized USERs
             (commissioners and clerks) in bail bondsmen, property surety and property
             agent records.
BBO-050.01         Provide ADMIN USER with the ability to define rules for access to data    0
                   based upon USER responsibilities.
BBO-050.02         Provide USER with the ability to assign one or more "secure" notes to     0
                   PROPERTY SURETY.
BBO-050.03         Provide USER with the ability to assign one or more "secure" notes to     0
                   bondsmen.
BBO-051      Alert USER (and reject bond entry) if property being offered as collateral on
             bond does not have sufficient equity to cover bond amount based on
             assessed value of property and other outstanding bonds against the same
             property.
BBO-051.01         Automatically notify the USER when a PROPERTY does not have               0
                   sufficient equity to cover the bond amount being posted.
BBO-052      Allow multiple bonds to be combined to obtain the total amount of the bail
             (i.e. a $50,000.00 bail may consist of a $5,000 cash bond, a $20,000
             accommodation bond and a $25,000 professional property bond.) There
             should only be one bail per case but allow for multiple bonds to equal the
             amount of bail. There should only be one release for the entire amount of
             the bail (allow data field to indicate anyone that posted the bond(s).)

BBO-052.01       Provide USER with the ability to assign one or more bonds to a bail.        0
BBO-052.02       Provide ADMIN USER with the ability to define rules on printing of          0
                 certain DOCUMENTS - document generation.



    MDEC Procurement K11-0030-29                                                                                   September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                        ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                              Page 244 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                               SECURITY AND DATA INTEGRITY

     ID                                    Requirement Text                                        Response Code   Comments
SDI-001      Allow restricted access to security authorization tables that are defined,
             maintained, and controlled by system administrators (e.g., access
             authorization tables controlled by system administrator).
SD1-001.01       Provide ADMIN USER with the ability to define codes for security             0
                 authorization tables that are defined, maintained, and controlled by
                 system administrators
SDI-002      Create and maintain records on access privileges for specific groups of
             users and types of data (e.g., case, defendant, and victim).

SDI-002.01        Provide ADMIN USER with the ability to define reports on access             0
                  privileges for specific groups of USERS and types of data
SDI-003      Provide security if public access is allowed. System should have the ability
             to restrict certain specified data fields from public view, such as social
             security numbers, addresses, or other user-specified information, based
             upon user action or rules for specific case types (e.g., juvenile, adoption,
             etc.).
SDI-003.01        Provide ADMIN USER with the ability to define rules to restrict certain     0
                  specified data fields from public view, such as social security numbers,
                  addresses, or other user-specified information, based upon user action
                  or rules for specific case types (e.g., juvenile, adoption, etc.).
SDI-004      Provide the ability to shield information at specific times of day (i.e., only
             make information viewable during working hours).

SDI-004.01        Provide ADMIN USER with the ability to define rules that shield              0
                  information at specific times of day (i.e., only make information viewable
                  during working hours).
SDI-005      Provide automatic logoff of application after predetermined period of
             inactivity; allow rules for inactivity logoff to be set for roles or individuals,
             within locally-defined minimums and maximums.
SDI-005.01        Provide ADMIN USER with the ability to define a rule to automatically        0
                  lock the screen of application after predetermined period of inactivity;
                  allow rules for inactivity screen lock to be set for roles or individuals,
                  within locally-defined minimums and maximums; and require password
                  to re-enter application.
SDI-006      Maintain and produce audit trail of additions, modifications, deletions, and
             rejected transactions (e.g., filings entered into docket) including who made
             entry, when entry made, whether date entered and date filed differ.

     MDEC Procurement K11-0030-29                                                                                    September 1, 2010
                                                MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                       ATTACHMENT C
                                                  MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 245 of 249
                                                         FUNCTIONAL REQUIREMENTS

                                                             SECURITY AND DATA INTEGRITY

     ID                                       Requirement Text                                   Response Code   Comments
SDI-006.01       Provide ADMIN USER with the ability to define reports of an audit trail     0
                 of additions, modifications, deletions, and rejected transactions (e.g.,
                 filings entered into docket) including who made entry, when entry made,
                 whether date entered and date filed differ.
SDI-006.02       Provide USER ADMIN with the ability to define reports that provide an
                 audit trail of login, logoff, failed logins, and date and time of access.
SDI-006.03       Provide USER ADMIN with the ability to define reports that provide the      0
                 following information: date and time of event, user id, type of event,
                 asset or resource name, success or failure of the event
SDI-007      Support secure access by authorized non-justice agencies for the
             maintenance of compliance data resulting from court orders.
SDI-007.01       Provide ADMIN USER with the ability to define rules for secure access       0
                 by authorized non-justice agencies for the maintenance of compliance
                 data resulting from court orders.
SDI-008      Provide a screen banner notifying authorized users that their activities may
             be monitored by system and management personnel.
SDI-008.01       Provide ADMIN USER with the ability to define a screen banner               0
                 notifying authorized USERS that their activities may be monitored by
                 system and management personnel.
SDI-009      Provide field level security with privileges based on user role and nature of
             the data in the field.
SDI-009.01       Provide ADMIN USER with the ability to define rules for field level         0
                 security with privileges based on USER role and classification of the
                 data in the field.
SDI-009.02       Provide ADMIN USER with the ability define rules for field level security   0
                 based on the classification of the data
SDI-010      Provide security for standard and ad hoc reporting based on user role.
SDI-010.01       Provide ADMIN USER with the ability to define rules for security for        0
                 standard and ad hoc reporting based on USER role.
SDI-010.02       Provide ADMIN USER with the ability to define rules for secure              0
                 distribution of security reports based on user and role
SDI-010.03       Provide ADMIN USER with the ability to define email recipients of           0
                 security and audit reports.
SDI-010.04       Provide ADMIN USER with the ability to define the schedule of security      0
                 and audit reports.
SDI-011      Allow for database backups and restoration on demand.

     MDEC Procurement K11-0030-29                                                                                  September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                      ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                            Page 246 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                              SECURITY AND DATA INTEGRITY

     ID                                      Requirement Text                                    Response Code   Comments
SDI-011.01       Provide ADMIN USER with the ability to define rules for database            0
                 backups and restoration on demand.
SDI-012      Allow for identification of locally defined mandatory fields.
SDI-012.01       Provide ADMIN USER with the ability to define rules for display locally     0
                 defined mandatory fields.
SDI-013      Allow the user to track the complete history of a record by who
             entered/changed a transaction by date/time stamp.
SDI-013.01         Provide ADMIN USER with the ability track the complete history of a       0
                   record by who entered/changed a transaction by date/time stamp.
SDI-014      Ensure modification of electronic records restricted to administrative
             information (e.g., cover sheet) with proper authorization and that electronic
             filings and orders cannot be modified.
SDI-014.01         Provide ADMIN USER with the ability to define rules that ensure           0
                   modification of electronic records is restricted to administrative
                   information (e.g., cover sheet) with proper authorization and that
                   electronic filings and orders cannot be modified.
SDI-015      Allow limited access to certain types of otherwise inaccessible cases and
             data (e.g., sealed cases with identifiers/numbers removed) for analysis.

SDI-015.01       Provide ADMIN USER with the ability to define rules that allow limited      0
                 access to certain types of otherwise inaccessible cases and data (e.g.,
                 sealed cases with identifiers/numbers removed) for analysis.

SDI-016      Suppress inclusion of user-designated confidential information in notices,
             calendars, court minutes, and other documents (e.g., mask out confidential
             addresses for notices sent to specific persons). (see also Document
             Generation and Processing Function, Calendaring Function, and Hearings
             Function)
SDI-016.01       Provide ADMIN USER with the ability to define rules to Suppress             0
                 inclusion of user-designated confidential information in notices,
                 calendars, court minutes, and other documents (e.g., mask out
                 confidential addresses for notices sent to specific persons). (see also
                 Document Generation and Processing Function, Calendaring Function,
                 and Hearings Function)
SDI-017      Ensure only single set of data exists for each person/party (i.e., various
             identifiers for given person must be correlated).

     MDEC Procurement K11-0030-29                                                                                  September 1, 2010
                                                 MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                       ATTACHMENT C
                                                   MARYLAND ELECTRONIC COURT PROCUREMENT                             Page 247 of 249
                                                          FUNCTIONAL REQUIREMENTS

                                                              SECURITY AND DATA INTEGRITY

     ID                                     Requirement Text                                      Response Code   Comments
SDI-017.01       Provide ADMIN USER with the ability to define rules to ensure only           0
                 single set of data exists for each PERSON/PARTY (i.e., various
                 identifiers for given person/party must be correlated).
SDI-018      Provide adequate security for judge‘s and other judicial officer‘s notes. (see
             also Calendaring Function)

SDI-018.01        Provide ADMIN USER with the ability to define rules to ensure that        0
                  adequate security is provided for judge‘s and other judicial officer‘s
                  notes. (see also Calendaring Function)
SDI-019      Provide the ability to redact (or otherwise make unavailable) sensitive
             personal data from accessible case information/documents.
SDI-019.01        Provide ADMIN USER with the ability to define rules that Provide the      0
                  ability to redact (or otherwise make unavailable) sensitive personal data
                  from accessible case information/documents.
SDI-020      Provide ADMIN USER with the ability to define roles, privileges and groups
SDI-021      Provide ADMIN USER with the ability to define codes to associate a role
             and/or privilege to a group
SDI-022      Provide the ADMIN USER with the ability to define codes to associate a
             USER with a group, or groups within groups
SDI-023      Provide ADMIN USER with the ability to define rules for password
             expiration, password min and max lengths, password
SDI-024      Provide ADMIN USER with the ability to define reports for logon, logoff, user
             name, role, group
SDI-025      Provide ADMIN USER with the ability to define LDAP host, port,
             distinguished name and other LDAP parameters so that it is configurable
             and read at run time.
SDI-026      Provide the ADMIN USER with the ability to define a rule for displaying the
             password is about to expire message and time interval for warning(e.g. 10
             days)
SDI-027      Provide the ADMIN USER with the ability to define a rule for displaying a
             message about password lockout and expiration, and contact information (
             helpdesk, security)
SDI-028      Provide the ADMIN USER with the ability to define a report notifying the
             security administrator when user accounts go idle for over three months
SDI-029      Provide the ADMIN USER with the ability to define notification to selected
             users via email that a scheduled security and audit report has been run.


     MDEC Procurement K11-0030-29                                                                                   September 1, 2010
                                               MARYLAND ADMINISTRATIVE OFFICE OF THE COURTS                 ATTACHMENT C
                                                 MARYLAND ELECTRONIC COURT PROCUREMENT                       Page 248 of 249
                                                        FUNCTIONAL REQUIREMENTS

                                                            SECURITY AND DATA INTEGRITY

     ID                                   Requirement Text                                Response Code   Comments
SDI-030     Provide the ADMIN USER with the ability to define audit policies, which
            specify the data access conditions that trigger the audit event.
SDI-031     Provide the ADMIN USER with the ability to define password construction
            and change requirements including (a) ensuring passwords are changed
            every x number of days (b) user ids are disabled after x number of failed
            login attempts, ( c) assuring that the password is not the same as the user
            id (d) password reuse must be prohibited by not allowing the previous x
            number of passwords to be re-used (e) must be a certain specified
            minimum length (f) must contain both numeric and character letters

SDI-032     Provide the USER with the ability to authenticate user name and password
            via SSL using128bit encryption at a minimum. Passwords should be hashed
            with a one way hash so that they can not be reverse engineered.




     MDEC Procurement K11-0030-29                                                                           September 1, 2010
                                            Maryland Administrative Office of the Courts   Attachment B
                                             Maryland Electronic Court Procurement
                                                     Technical Requirements
                                                        Response Codes
Can be Demonstrated
Requires Configuration
Future Release
Requires Customization
Alternative Proposed
Not Proposed




DRAFT 6024\01\157909(xls)||Response Codes                       249

				
DOCUMENT INFO
Description: Filing for Sole Legal Custody Court document sample