Docstoc

Trial Court Organizational Charts

Document Sample
Trial Court Organizational Charts Powered By Docstoc
					State of Indiana                                                               Requirements                                                               PNCO# ACMS-2010
Appellate Court Case Management System                                                                                                                          July 9, 2010



                                Component               Number of Requirements
                1       Case Management                                      189
                2       Document Management                                   42
                3       Conflict Management                                    8
                4       e-Filing                                              73
                5       Technology                                           161
                6       Web Interface                                          6

                        Total                                                        479




 Requirements Matrix Instructions
 Respondents must indicate, in the "Vendor Response" column, whether their proposed offering meets the each individual requirements by assigning a response
 value using the legend listed below. Any requirements that are left blank, or requirements for which responses other than the responses listed below are given,
 will be evaluated as an "NA".

 CD –Custom Development:
 The desired feature or functionality is not available as part of the standard (baseline) software functionality but can be custom built to satisfy the specified
 system requirement. Only use “CD” if the functionality can be custom developed as a “bolt-on” to the primary software without the specified system
 requirement. Only use “CD” if the functionality can be custom developed as a “bolt-on” to the primary software without requiring changes to the underlying
 source code. A brief explanation is required to support any proposed custom development; explanations should be provided in the “Comments” section of the
 matrix. Estimated costs and work effort associated with each custom development effort must be included in the separate cost proposal.

 MA –Major Modification to Source Code Required:
 Modifications meeting either of the conditions listed below must be made to the standard software offering (primary software or third party) to satisfy the
 specified requirement:
 • Estimated work effort for design, coding, and unit testing exceeds 80 hours; or
 • Change to underlying source code.
 A brief explanation is required to support any proposed modification; explanations should be provided in the “Comments” section of the matrix. Estimated costs
 and work effort associated with each modification must be included in the separate cost proposal.




                                                                                                                                                                          1
State of Indiana                                                                 Requirements                                                              PNCO# ACMS-2010
Appellate Court Case Management System                                                                                                                           July 9, 2010




  MI –Minor Modification:
  Minor modifications must be made to the standard software offering utilizing the delivered “Development Toolset” to satisfy the specified requirement.
  Examples of minor modifications include changing a field length and creating a new view. In no case, however, can a modification exceeding 80 hours estimated
  work effort be considered minor, regardless of the development method. A brief explanation is required to support any proposed minor modification;
  explanations should be provided in the “Comments” section of the matrix. Estimated costs and work effort associated with each minor modification must be
  included in the separate cost proposal.

  NA –Cannot Meet Requirement:
  The desired feature or functionality is not available as part of the standard (baseline) software functionality, in the next software release, through
  modification/enhancement, reporting tools, or third party software. The requirement would most likely need to be met by a process workaround or by
  interfacing an existing legacy application.

  NR –Provided in Next Release:
  The next release of the software will provide the requested functionality without screen, code, or design changes. Only use “NR” if the very next release of the
  baseline software will fully meet the requirement. Only formal releases that have been published and are accessible on the Internet shall be considered when
  addressing this requirement. A brief identifier/description of the referenced release should be included in the “Comments” section.

  RQ –Provided through Reporting or Query Tool:
  The software (primary software or third party) supports the data elements necessary for the report/inquiry, but a custom report/inquiry would need to be
  developed to meet the requirement. A brief explanation is required to support any proposed modification; explanations should be provided in the “Comments”
  section of the matrix. Estimated costs and work effort associated with each custom report must be included in the separate cost proposal.

  SF –Standard Functionality:
  The software provides the requested functionality without screen, code, or design changes. The product can satisfy the specification “out-of-the-box” without
  any modification to the standard baseline software offering. Only use “SF” if the baseline software as delivered in the current release fully meets the
  requirement “as is” or through software configuration.

  TP–Third Party Software Required:
  The desired feature or functionality is not available as part of the standard (baseline) software functionality but is a standard feature of third-party software
  proposed to satisfy the specified system requirement. The third-party software, which is fully integrated with the primary system, provides the requested
  functionality without screen, code, or design changes. The proposed third-party product can satisfy the specification “out-of-the-box” without any modification
  to the standard baseline software offering. Only use “TP” if the third party software fully meets the requirement.




                                                                                                                                                                           2
State of Indiana                         Requirements   PNCO# ACMS-2010
Appellate Court Case Management System                        July 9, 2010




                                                                        3
State of Indiana                         Requirements   PNCO# ACMS-2010
Appellate Court Case Management System                        July 9, 2010




                                                                        4
State of Indiana                                                         Requirements Dictionary                                                           PNCO# ACMS-2010
Appellate Court Case Management System                                                                                                                           July 9, 2010

Term                         Description
Active Directory             Active Directory provides the means to manage the identities and relationships that make up network environments.
                             Any person or entity that is involved with an activity (either causes the activity to occur or is impacted in some way by the
                             activity). For example: Clerk's Office personnel receive stamp a brief and send the person filing the brief a notice of defect (the
Actor                        Clerk's office personnel and the person filing the brief are both actors).
                             A group of like items that are to be processed together at a specified time. For instance the user of the case management
Batch                        system may want to identify a group of orders that are to be printed together at the end of the day.
                             Identifies the condition of the case within the Appellate case management system. A status could be: new, in Court of Appeals
Case Status                  administration office, assigned to Judge, opinion circulated, handed-down, closed, etc.
COSCA                        Conference of State Court Administrators: www.cosca.ncsc.dni.us
                             A description of the organization of a database. It usually includes: entity relationship diagrams, table and data element
Data Model                   attributes, etc.
                             Describes the problem associated with a document submitted to the Clerk's Office that does not meet the court specified
Deficiency                   requirements for that document (i.e. correct number of copies, wrong margin size, etc.).

                             An attachment to an electronic message used for security purposes. The most common use of a digital certificate is to verify that
Digital Certificate          a user sending a message is who he or she claims to be, and to provide the receiver with the means to encode a reply.

Drop-down list               This is a data entry screen control that allows a user to select an item from the list. See Look Up Tables and User Defined Tables.
                             Look Up Tables and User Defined Tables can contain an effective date for each record. This indicates that an item is available for
Effective Date               use in data entry on or after that date. See Look Up Tables and User Defined Tables.
                             Any action that is to take place (i.e. response from appellee due, oral argument final calendar due). Events usually have a tickler
Event                        association. See Tickler.
Filer                        A person who is or has submitted a document for filing with an Appellate Court case.

                             National Institute of Standards and Technology generated document named: FEDERAL INFORMATION PROCESSING STANDARDS
FIPS                         PUBLICATION, documenting secured hash algorithms to be used for message transmittal. See Hash Algorithms.
                             This is an indicator identifying a data entry item as having extra information associated with it. For instance an attorney might
Flag/Flagging                be flagged as no longer licensed, this could take the form of being marked in red or grayed out, etc.
                             GUI - Graphical user interface. It is a type of user interface item that allows people to interact with programs in more ways than
GUI                          typing. It offers graphical icons, and visual indicators, as opposed to text-based interfaces.
                             This is a computer software generated mathematical process, used for encryption of data to ensure secure transmission of that
Hash Algorithms              data.
                             HTTPS - Hypertext Transfer Protocol Secure. It creates a secure channel over an insecure network. HTTPS encrypts and decrypts
                             user page requests as well as the pages that are returned by the Web server. The use of HTTPS protects against eavesdropping
HTTPS                        and attacks.
                             A case-related condition that warrants monitoring by a user of the case management system. An example of this could be a
Issue                        prisoner appealing multiple times or indicating a special condition about a case.




                                                                                                                                                                         D5
State of Indiana                                                         Requirements Dictionary                                                          PNCO# ACMS-2010
Appellate Court Case Management System                                                                                                                          July 9, 2010

Term                         Description
                             A term used to describe the electronic transportation of a document to a court and the data accompanying the document. It
                             allows for the transmitted document to be in any format. It was approved as a draft standard by the COSCA/NACM Joint
Legal Envelope               Technology Committee on March 22, 2000.
                             A group of legal and technical experts in a common forum to create standards for the electronic exchange of information.
                             LegalXML is a member section within OASIS, the not-for-profit, global consortium that drives the development, convergence and
LegalXML                     adoption of e-business standards. www.legalxml.org
                             These terms are used when searching for data from the database. They indicate that the item to be searched for is to contain
                             the entered information, not necessarily match exactly. For instance: name search for a name like Ann, could result in: Ann,
Like/Wild Card               Joann, Anna, Joanna being returned in the search results.
                             These are tables that are used during data entry. They can appear as drop-down lists, options, or any other view of list items. It
                             allows the user to select an item rather than having to type it in. These can be the information from the User Defined Tables.
Look Up Table                See User Defined Tables.
Milestone                    A significant event.
Migration Strategy           Transitions to new file formats allowed in filings, to ensure easy and prompt migration to new releases of XML standards.
NACM                         National Association for Court Management www.nacmnet.org
                             The National Information Exchange Model (NIEM) is a Federal, State, Local and Tribal interagency initiative providing a
                             foundation for seamless information exchange. NIEM was launched on February 28, 2005, through a partnership agreement
                             between the U.S. Department of Justice (DOJ) and the U.S. Department of Homeland Security (DHS) and signed by Chief
                             Information Officers. It leverages the data exchange standards efforts successfully implemented by the Global Justice
                             Information Sharing Initiative (Global) and extends the Global Justice XML Data Model (GJXDM) to facilitate timely, secure
                             information sharing across the whole of the justice, public safety, emergency and disaster management, intelligence, and
NIEM                         homeland security enterprise. www.niem.gov

Non-Case Information         Miscellaneous documents received by the court that are not clearly assignable to a specific case at the time of receipt.
                             Null means 'nothing' or without value or consequence. It indicates that a data element has not been given a specific value. For
                             instance, when saving the gender data element, if the user did not specify a value, null would be stored in the database as
Null                         opposed to a M or F if the user had indicated the gender value.
Official Court Document      This is a generic term identifying any documents generated by the Appellate Courts (notices, orders, etc.)
                             This describes a relationship between two items. For instance, a single motion (one item) may end up being used for more than
                             one order (many items), this is a one to many relationship. One to one relationship indicates that there could only be one item
One to Many/One to One       associated to another single item. See Parent/Child Relationship.

                             This is a view of how items are related to each other. For instance you might see a motion and listed with it are the resulting
Parent/Child Relationship    orders. The motion is the parent and the orders are the children. See One to Many/One to One and Threaded.
                             This is the result of the user scrolling over an item or clicking an icon causing a list of related items to appear and allowing the
Pop up/Drop down List        user to select an item from the list.
                             A set of hardware, software, people, policies, and procedures needed to create, manage, distribute, use, store, and revoke digital
Public Key Infrastructure    certificates.




                                                                                                                                                                        D6
State of Indiana                                                        Requirements Dictionary                                                          PNCO# ACMS-2010
Appellate Court Case Management System                                                                                                                         July 9, 2010

Term                         Description
                             When a user accesses a record from the database with the intent of updating that record's information, the database can place a
                             lock on that record so that no other user can take action against that specific record (read only allowed). This prevents users
Record Lock                  from overwriting each others changes to the database.
                             A method of structuring data as collections of tables that are logically associated to each other by shared attributes. Any data
                             element can be found in a relation by knowing the name of the table, the attribute (column) name, and the value of the primary
                             key. For instance an Address table contains records for every address associated with the employees. Each record in the address
Relational Database          table would contain a pointer to the appropriate Employee table record.
                             A method to restrict system access to authorized users. Users are not assigned permissions directly, but only acquire them
                             through their role (or roles). Within an organization, roles are created for various job functions. The permissions to perform
                             certain operations are assigned to specific roles. For instance the Clerk's Office might want a role created allowing only certain
Role-based Security          individuals to have the ability to create a new case.
                             A session is a semi-permanent interactive information interchange, between two or more communicating devices, or between a
                             computer and user. A session is set up or established at a certain point in time, and torn down at a later point in time. An
                             established communication session may involve more than one message in each direction. A session is typically, but not always,
                             stateful, meaning that at least one of the communicating parts needs to save information about the session history in order to
                             be able to communicate, as opposed to stateless communication, where the communication consists of independent requests
                             with responses. Session configurations protect the computer and define custom environments for users who connect to the
                             computer. The session default is the amount of inactive time before the session is dropped.
Session Default
                             SQL - Structured Query Language. A database computer language designed for managing data in relational database
                             management systems (RDBMS). It is used to add, update, and retrieve information from a relational database. SQL queries are
                             commonly used to retrieve information from the database. These queries are usually supplied with information from the user to
SQL                          indicate what information to retrieve (i.e. any one with a last name of Smith).
                             SSL - Secure Sockets Layer. Cryptographic protocols that provide security for communications over networks such as the
SSL                          Internet.
                             This is a user of the case management system that has security rights to perform application actions beyond those of normal
System Administrator         case management users.
                             A thin client can refer to either a software program or to an actual computer that relies heavily on another computer to do most
                             of its work. A thin client is part of a network, and the client software or computer acts as an interface, while the network server
                             computer does all the real work. In the case of a computer, a thin client is unable to perform many functions on its own. A thin
                             client computer may be a machine designed only for online use, sending and receiving email, and surfing the net. A thin client
Thin Client                  computer may also be part of a larger network, at a company or school for example.
                             Case information that is related based on a time line and relationship. For instance: Appellant files a brief, Appellee files a
                             response, Appellant files a response to Appellee brief. These items appear together showing the sequence of the activity and the
Thread/Threaded              parent/child relationship. See Parent/Child Relationship.
                             This is an event that is used to remind a person of a task that is (or should) take place. For instance: Outlook reminder of a
Tickler                      meeting. See Event.
                             Internal court personnel given access to and interacting with the case management system. (i.e. person entering docket
User                         information, adding a case, requesting a report, setting up security rights, etc.)


                                                                                                                                                                       D7
State of Indiana                                                        Requirements Dictionary                                                        PNCO# ACMS-2010
Appellate Court Case Management System                                                                                                                       July 9, 2010

Term                         Description
                             These are database tables that contain data that is defined by the user of the case management system (usually someone with
                             administrative rights). Information that these tables contain could be: Name prefixes, state names, document types, case types,
User Defined Tables          case statuses, etc. See Look Up Tables.
                             World Wide Web Consortium (W3C) is an international community where Member organizations, a full-time staff, and the public
W3C                          work together to develop Web standards.
Web Browser                  A software application for retrieving, presenting, and traversing information resources on the World Wide Web.
                             XML data exchange is critical from electronic filers and to any other entities with which the court shares electronic documents.
                             XML (Extensible Markup Language) enables the transfer of data among automated systems that use different hardware,
                             software, operating systems and applications. It is the nationally accepted standard for both private and public sector
                             information sharing, such as electronic filing. XML inserts “tags” within a document or data stream to identify specific data
                             elements. Software at the receiving end of a transmission reads the XML tags and places the data received in the correct places
                             within its specific database structure. The standard tags for a particular transaction are set forth in a “specification” created
                             according to rules prescribed by the World Wide Web Consortium (W3C).
XML (XML data exchange)




                                                                                                                                                                     D8
   State of Indiana                                                               Requirements                                                     PNCO# ACMS-2010
   Appellate Court Case Management System                                                                                                                July 9, 2010

   ID            Sub-Category               Priority                      Case Management Requirements                           Vendor Response   Comments
                                                       Ability to indicate if a case type, specific case, or specific
                                                       document(s) within a case should have restricted user access .
CM-001 Case Initiation and Indexing     Required
                                                       Case search results shall display (at a minimum): case number, case
                                                       name, case status with a default sort order of case number, case
CM-002 Case Initiation and Indexing     Required       name.
                                                       The case summary shall display a list of issues associated with that
CM-003 Case Initiation and Indexing     Required       case, if any.
                                                       The system shall allow entering of an unlimited number of filings,
CM-004 Case Initiation and Indexing     Required       actions or tickler events per case.
CM-005 Case Initiation and Indexing     Required       The system shall allow for case types specific to the Tax Court.
                                                       The system shall allow the authorized user to change the case
                                                       number or name on any active case along with reason for the
                                                       change, recording date/time of change and user making the change.
CM-006 Case Initiation and Indexing     Required
                                                       The system shall allow the user to easily search for cases based on
                                                       any combination of the following criteria/filters (at a minimum): case
                                                       number/name/status/type, party names, trial court county/case
                                                       number/judge, document filing date, assigned court, Prison ID #,
                                                       attorney name/number, plus any other search criteria. The search
                                                       feature is used in conjunction with the screen display of case list and
                                                       cases to be reported on.
CM-007 Case Initiation and Indexing     Required
                                                       The system shall allow the user to record the filing of disciplinary
CM-008 Case Initiation and Indexing     Required       matters relating to attorneys and judges.
                                                       The system shall allow the user to record the lower court judgment
                                                       date and signing Judge, or in the case of an agency review, the order
CM-009 Case Initiation and Indexing     Required       service date.
                                                       The system shall allow the user to see case history and allow for
                                                       sorting of case history by any history column header in ascending or
CM-010 Case Initiation and Indexing     Required       descending order.
                                                       The system shall allow the user to specify filter criteria for the
                                                       viewing of cases and filter criteria for viewing of specific types of
CM-011 Case Initiation and Indexing     Required       court docket information.
                                                       The system shall generate and assign a case number using a defined
CM-012 Case Initiation and Indexing     Required       format.
                                                       The system shall have security features to restrict access to data at
CM-013 Case Initiation and Indexing     Required       the various organizational levels (by court or office).



                                                                                                                                                               CM 9
   State of Indiana                                                                Requirements                                                       PNCO# ACMS-2010
   Appellate Court Case Management System                                                                                                                   July 9, 2010

   ID            Sub-Category               Priority                      Case Management Requirements                              Vendor Response   Comments
                                                       The system shall know which case types are normally expedited, and
                                                       indicate such cases as expedited as a default value when adding such
CM-014 Case Initiation and Indexing     Required       a case.
                                                       The system shall not allow the user to re-use a case number, nor
CM-015 Case Initiation and Indexing     Required       delete a case.
                                                       The system shall provide the user with the ability to select multiple
                                                       cases for printing of case summary information and optionally their
CM-016 Case Initiation and Indexing     Required       case histories.
                                                       When adding a new case, the system shall have the case number
                                                       default to the next unused case number in sequence for that court.
CM-017 Case Initiation and Indexing     Required
                                                       The system shall allow the user to designate a lead case with an
CM-018 Case Initiation and Indexing     Optional       issue if they desire.
                                                       The system shall allow the user to create a relationship between a
                                                       user defined issue to any number of cases. Also a case can have
CM-019 Case Initiation and Indexing     Desired        multiple issues.
                                                       The system shall allow the user to view an issue name and a list of
                                                       the case numbers and case names associated with that issue.
CM-020 Case Initiation and Indexing     Desired
                                                       A single action (e.g. order or opinion) can resolve multiple filings
CM-021 Filings                          Required       within a case.
                                                       If a filing is being recorded and it is late, the system shall calculate
CM-022 Filings                          Required       the number of days late.
                                                       The system shall allow the user to add comments to all filings and
                                                       indicate the security level of the comment (anyone can view, only
                                                       person making the comment can view, certain groups can view,
CM-023 Filings                          Required       etc.).
                                                       The system shall allow the user to add one to many deficiencies for a
CM-024 Filings                          Required       filing.
                                                       The system shall allow the user to indicate that particular
                                                       deficiencies on a filing were corrected and the date they were
CM-025 Filings                          Required       corrected.
                                                       The system shall allow the user to record for any filing the results of
CM-026 Filings                          Required       any decision on that filing.
                                                       The system shall allow the user to record that a filer on a document
                                                       is not a party, but is some other entity (e.g. Trial Court) which is user-
CM-027 Filings                          Required       defined.




                                                                                                                                                                 CM 10
   State of Indiana                                                                Requirements                                                    PNCO# ACMS-2010
   Appellate Court Case Management System                                                                                                                July 9, 2010

   ID            Sub-Category               Priority                       Case Management Requirements                          Vendor Response   Comments
                                                       The system shall allow the user to record the receipt of a document
                                                       filed in a case, including received date, filed date, document type,
                                                       filer name, attorney number for filing attorneys, and whether timely.
CM-028 Filings                          Required
                                                       The system shall allow the user to relate a filing to another filing on
CM-029 Filings                          Required       the case.
                                                       The system shall allow the user to relate a filing to the filing
                                                       attorney(s), and identify the party(s) represented by that attorney.
CM-030 Filings                          Required
                                                       The system shall allow a user with appropriate security rights to
                                                       override the limiting of a filing to a specific court, at the macro and
CM-031 Filings                          Desired        case-specific levels.
                                                       The system shall allow the flagging of filing types to limit in what
CM-032 Filings                          Desired        court(s) flagged types can be filed.
                                                       The system shall prompt the user to automatically extend a tickler's
                                                       'due date' at the time an Order is entered that is allowing an
CM-033 Filings                          Desired        extension of time for a particular document.
                                                       When a filing is recorded, the system shall display the active ticklers
                                                       on that case and allow the user to indicate any that are satisfied by
CM-034 Filings                          Desired        the filing.
                                                       One Court of Appeals or one Tax Court case may result in zero to
CM-035 Case Relationships               Required       many Supreme Court cases.
                                                       One to many Court of Appeals or one to many Tax Court cases may
                                                       be appealed to the Supreme Court as one Supreme Court case.
CM-036 Case Relationships               Required
                                                       One to many trial court cases may be appealed to the Court of
                                                       Appeals as one Court of Appeals case or appealed to the Tax Court
CM-037 Case Relationships               Required       as one Tax Court case.
                                                       One trial court case may result in one to many Court of Appeals
CM-038 Case Relationships               Required       cases or Tax Court cases or Supreme Court cases.
                                                       The system shall allow the user to consolidate cases, creating
                                                       parent/child relationships, designating one case as the parent case,
                                                       and the others as the resulting (child) cases.
CM-039 Case Relationships               Required
                                                       The system shall allow the user to split apart a case that had been
                                                       consolidated back into its original cases or split some of the cases
CM-040 Case Relationships               Required       back to their original case.
                                                       The system shall allow the user to view related cases as a "thread".
CM-041 Case Relationships               Required


                                                                                                                                                              CM 11
   State of Indiana                                                                Requirements                                                      PNCO# ACMS-2010
   Appellate Court Case Management System                                                                                                                  July 9, 2010

   ID            Sub-Category               Priority                     Case Management Requirements                              Vendor Response   Comments
                                                       When displaying a Court of Appeals or Tax Court case that resulted
                                                       in multiple Supreme Court cases, the system shall allow the user to
                                                       choose which Supreme Court case the user would like to see in
                                                       addition to the Court of Appeals/Tax Court events.
CM-042 Case Relationships               Optional
                                                       When displaying a Supreme Court case that resulted from multiple
                                                       Court of Appeals or Tax Court cases, the system shall let the user
                                                       choose which Court of Appeals/Tax Court case the user would like to
CM-043 Case Relationships               Optional       see in addition to the Supreme Court events.
                                                       The system shall allow the user to merge non-case information into
                                                       an existing case, including events, and parties without adding
CM-044 Case Relationships               Desired        duplicates.
                                                       The system should allow for a listing of all attorneys assigned to a
CM-045 Case Relationships               Desired        hearing officer.
                                                       When a case is decided and if there are cases related to the decided
                                                       case, the system shall display all the related cases and allow the user
CM-046 Case Relationships               Desired        to select cases to update.
                                                       When adding a new Supreme Court Case that is related to a Court of
                                                       Appeals or Tax Court case, the system shall warn the user if there is
                                                       a motion pending in the Court of Appeals/Tax Court case.
CM-047 Case Relationships               Desired
                                                       When user enters an event to a Court of Appeals case or Tax Court
                                                       case, notify that user of any Supreme Court pending matters.
CM-048 Case Relationships               Desired
                                                       If an attorney's address or e-mail address is updated on a case, the
                                                       system shall allow the user to either update that information only
                                                       for that case, update that information for only open cases, or update
                                                       that information on all cases for that attorney.
CM-049 Party Management                 Required
                                                       The system shall (when searches are performed on
                                                       parties/attorneys) display active addresses, and the unique identifier
                                                       for a party (i.e. attorney #, Prison ID #) in order to ensure the correct
                                                       party is attached to a selected case or filing.
CM-050 Party Management                 Required
                                                       The system shall allow all parties on a case to designate carbon copy
CM-051 Party Management                 Required       recipients for case-related communications.
                                                       The system shall allow for categories of persons on a case 1) Litigant;
                                                       2) Attorney; 3) Court Personnel; 4) Interveners; 5) Amici Curiae; and
                                                       6) Interested Persons, etc. and allow authorized users to create new
CM-052 Party Management                 Required       categories.
                                                                                                                                                                CM 12
   State of Indiana                                                                Requirements                                                     PNCO# ACMS-2010
   Appellate Court Case Management System                                                                                                                 July 9, 2010

  ID             Sub-Category               Priority                     Case Management Requirements                             Vendor Response   Comments
                                                       The system shall allow the authorized user to update the e-mail
                                                       address for designated recipients of system-generated e-mail.
CM-053 Party Management                 Required
                                                       The system shall allow the entry of multiple address types with an
                                                       indicator for each type (mailing, billing, personal, business, etc), and
                                                       shall allow the entry of multiple e-mail addresses and allow the
                                                       party to specify to whom each multiple e-mail address belongs.
CM-054 Party Management                 Required
                                                       The system shall allow the user to add a person, business, or an
CM-055 Party Management                 Required       object to a case as a party.
                                                       The system shall allow the user to designate which parties were or
                                                       were not served for each document filed, method served, date/time
CM-056 Party Management                 Required       served.
                                                       The system shall allow the user to enter alias names for any party.
CM-057 Party Management                 Required
                                                       The system shall allow the user to record that an attorney is
CM-058 Party Management                 Required       representing a specific party on the case.
                                                       The system shall allow unlimited number of attorneys representing a
CM-059 Party Management                 Required       party.
CM-060 Party Management                 Required       The system shall allow unlimited parties on a case.
                                                       The system shall carry information about participants who are
                                                       transcript coordinators and transcribers such as name, county(s)
CM-061 Party Management                 Required       assigned, court assignment, contact information.
                                                       The system shall keep a history of all litigants and attorneys on a
                                                       case with their beginning and ending dates of participation. If the
                                                       litigant/attorney remains with the case, the ending date will not
CM-062 Party Management                 Required       have a value.
                                                       The system shall keep and allow the user to add or update a
                                                       person's address including a history of all address changes, the dates
CM-063 Party Management                 Required       they were valid.
                                                       The system shall permit a person (attorney or pro se party) to
                                                       designate a different e-mail address for each case to which that
                                                       person is associated, defaulting to the person's preferred e-mail
CM-064 Party Management                 Required       address.
                                                       The system shall print envelopes and/or labels for parties who
                                                       cannot receive documents by e-mail. (Default is always e-mail.)
CM-065 Party Management                 Required
                                                       The system shall provide for a person-based system, where any
                                                       person is in the system only once, and is associated with multiple
CM-066 Party Management                 Required       cases, if possible.
                                                                                                                                                               CM 13
   State of Indiana                                                                Requirements                                                       PNCO# ACMS-2010
   Appellate Court Case Management System                                                                                                                   July 9, 2010

  ID             Sub-Category               Priority                     Case Management Requirements                               Vendor Response   Comments
                                                       The system shall provide the ability to handle "John Doe" or "Jane
                                                       Doe" situations; some cases will require confidentiality, such as
CM-067 Party Management                 Required       juvenile where name initials are used.
                                                       The system shall provide the ability to record that a party is
CM-068 Party Management                 Required       representing him/herself.
                                                       The system shall provide the user with a results list which includes
                                                       the party, attorney or official's name and the active mailing
                                                       addresses (sort results together if there are city/state matches).
CM-069 Party Management                 Required
                                                       The system shall require all parties on a case to have case specific
CM-070 Party Management                 Required       contact information.
                                                       The system shall separate officials (trial court clerk, trial court judge,
                                                       district attorney, sheriff) and other interested personnel (court staff,
CM-071 Party Management                 Required       media) from parties and attorneys.
CM-072 Party Management                 Required       The system shall store the lower court role for each party.
                                                       To provide for the tracking of attorney disciplinary cases, the system
                                                       shall allow for hearing officer assignments to a case. Multiple
                                                       officers can be assigned to a case but only one can be active.
CM-073 Party Management                 Required
                                                       To provide for the tracking of judicial disciplinary cases, the system
                                                       shall allow for special master assignments to a case. Multiple
                                                       masters can be assigned to a case and a presiding master can be
CM-074 Party Management                 Required       designated.
                                                       When adding a new case , the system shall automatically add the
                                                       trial court/agency's court reporter(s), trial court clerk, transcript
                                                       coordinator, etc. as default participant(s) on the case.
CM-075 Party Management                 Required
                                                       When reviewing a case and its parties, the system shall display all
CM-076 Party Management                 Required       active party names, addresses, and their role.
                                                       The system shall allow a user to display all attorneys on a case or
CM-077 Party Management                 Desired        only display lead counsel.
                                                       The system shall allow multiple names for one person, business, or
                                                       object, identified by name type, but only one designated as the
CM-078 Party Management                 Desired        official name.
                                                       The system shall allow the user to indicate that a party's address is
                                                       no longer valid, and that there is no valid address to put in the
CM-079 Party Management                 Desired        system.
                                                       The system shall allow the user to indicate the attorneys
                                                       representing role on the case (e.g. self-represented, court-
CM-080 Party Management                 Desired        appointed, privately retained, unknown).
                                                                                                                                                                 CM 14
   State of Indiana                                                                 Requirements                                                       PNCO# ACMS-2010
   Appellate Court Case Management System                                                                                                                    July 9, 2010

  ID             Sub-Category               Priority                       Case Management Requirements                              Vendor Response   Comments
                                                       The system shall allow the user to select parties to receive specific
CM-081 Party Management                 Desired        mailings.
                                                       The system shall allow users to designate an individual or entity as
                                                       ineligible to participate on a case (e.g. An Amicus that has been
CM-082 Party Management                 Desired        denied permission to participate in an appeal).
                                                       The system shall keep a record of all attorneys on a case with their
                                                       begin and end date as designations change including, but not limited
                                                       to withdrawal, lead counsel, orally arguing information.
CM-083 Party Management                 Desired
                                                       When an attorney or a party’s address or e-mail address is changed,
                                                       the system shall notify the user of open cases involving that attorney
                                                       or party and update the address information on the cases as
CM-084 Party Management                 Desired        indicated by the user.
                                                       The system shall allow the authorized user to deactivate a case
                                                       making it no longer available for reporting or retrieval, along with
                                                       reason for the deactivation, recording date/time (i.e. started a case
CM-085 Case Status                      Required       not realizing it had already been started).
                                                       The system shall allow the authorized user to reactivate a case that
CM-086 Case Status                      Required       has been closed.
                                                       The system shall allow the user to change the expedited status on
CM-087 Case Status                      Required       individual cases.
                                                       The system shall be able to calculate the duration that a case was in
CM-088 Case Status                      Required       a particular status.
                                                       The system shall store multiple levels of case statuses, to be
CM-089 Case Status                      Required       determined during analysis.
                                                       The system should allow for disciplinary cases to have their own set
CM-090 Case Status                      Required       of case statuses.
                                                       When recording the receipt of a brief, the system shall allow the
                                                       user to indicate if it is the last brief to be filed on the case before the
                                                       case is ready for submission to the court. Ideally the system
                                                       automates this feature and notifies the user of the last item filed
CM-091 Case Status                      Required       and that case is ready for submission
                                                       For reporting purposes, for matters submitted to the Courts, the
                                                       system shall count as separate entities, (at a minimum) cases,
                                                       remands, motions, orders, opinions written on them, whether or not
CM-092 Case Tracking                    Required       they originate from the same case.
                                                       On Motions for Extension of Time, the system shall keep track of the
CM-093 Case Tracking                    Required       number of days requested.
                                                       The system shall allow the user to easily determine the time
CM-094 Case Tracking                    Required       between milestones.
                                                                                                                                                                  CM 15
   State of Indiana                                                               Requirements                                                      PNCO# ACMS-2010
   Appellate Court Case Management System                                                                                                                 July 9, 2010

   ID            Sub-Category               Priority                     Case Management Requirements                             Vendor Response   Comments
                                                       The system shall allow the users to select from a list, events that pre-
CM-095 Case Tracking                    Required       populate the docket with text.
                                                       The system shall store milestones on a case, along with the due date
CM-096 Case Tracking                    Required       of that milestone and achieved date.
                                                       When displaying a case history from multiple appellate courts, the
                                                       system shall show from which court each event occurred.
CM-097 Case Tracking                    Required
                                                       The system shall, when requested, show a projected schedule for all
CM-098 Case Tracking                    Optional       required activities on a selected case.
                                                       The system shall allow the user to add a record on multiple cases at
                                                       one time, with the user being able to validate the case number
CM-099 Case Tracking                    Desired        keyed in by displaying the case name.
                                                       The system shall allow the user to note whether or not a case should
                                                       appear on the Court Conference Agenda (individual agendas for
                                                       Supreme Court, Court of Appeals, Tax Court) along with the date of
CM-100 Case Tracking                    Desired        the conference.
                                                       The system shall provide an efficient means of recording results
                                                       (changes on the case) from Court Conference Agendas (individual
                                                       agendas for each court: Supreme Court, Court of Appeals, Tax
CM-101 Case Tracking                    Desired        Court).
                                                       The system shall provide Spell Check for English and legal languages
CM-102 Case Tracking                    Desired        when entering text details.
                                                       When a user is viewing a case or adding information to a case, the
                                                       system shall display prominently that a filing on that case has been
CM-103 Case Tracking                    Desired        recorded as an emergency filing.
                                                       Once a judge/justice has been assigned to a case, the system shall
                                                       allow for their removal from the case and the assignment of a new
                                                       judge/justice along with recording the date and reason for the
CM-104 Judge/Justice Assignment         Required       change.
                                                       The system shall allow for (at a minimum) 3 or 5 judges/justices to
CM-105 Judge/Justice Assignment         Required       be assigned to a case.
                                                       The system shall allow for one judge or justice or per curiam to be
CM-106 Judge/Justice Assignment         Required       identified as the "writing" entity for a case.
                                                       The system shall allow the user to designate justices/judges who are
CM-107 Judge/Justice Assignment         Required       not eligible (or recused) to be assigned to a case or motion including
                                                       the date of recusal andthe user to specifically assign a justice/judge
                                                       The system shall allow reason.
CM-108 Judge/Justice Assignment         Required       to a case or motion.
                                                       The system shall have the ability to enter 'panel assignments' to
CM-109 Judge/Justice Assignment         Required       cases and motions.
CM-110 Judge/Justice Assignment         Required       The system shall track case assignments to a justice/judge.
                                                                                                                                                               CM 16
   State of Indiana                                                            Requirements                                                    PNCO# ACMS-2010
   Appellate Court Case Management System                                                                                                            July 9, 2010

  ID            Sub-Category             Priority                     Case Management Requirements                           Vendor Response   Comments
CM-111 Judge/Justice Assignment         Required    The system shall track case rehearings by justice/judge.
                                                    The system shall track cases transmitted in/out of court chambers
CM-112 Judge/Justice Assignment         Required    and the judges associated with the transmission.
                                                    The system shall allow the assignment of zero to many law clerks to
CM-113 Law Clerk Assignment             Required    a case.
                                                    The system shall allow for a motions panel schedule, which includes
CM-114 Calendaring                      Desired     the agenda, to be sent prior to the weekly meeting.
                                                    The system shall keep track of unavailable times for judges and
CM-115 Calendaring                      Desired     justices.
                                                    The system shall allow a user to view/print the Court Conference
                                                    Agenda (individual agendas for Supreme Court, Court of Appeals,
CM-116 Scheduling                       Required    Tax Court).
                                                    The system shall allow the user to note events for time periods that
CM-117 Scheduling                       Desired     are scheduled for a courtroom, including non oral argument events,
                                                    so that the courtroom will not be double-booked. and time
                                                    The Oral Argument schedule shall use calendar days
CM-118 Oral Arguments                   Required    periods within each day.
                                                    The system shall allow the user to default time limits for oral
                                                    arguments (e.g. 15, 20 or 30 minutes) specific to the Court and allow
CM-119 Oral Arguments                   Required    for override of the default value.
                                                    The system shall allow the user to indicate that an Oral Argument
CM-120 Oral Arguments                   Required    order should be generated for a particular case.
                                                    The system shall allow the user to view and print specified case
                                                    information of all cases that are scheduled for oral argument.
CM-121 Oral Arguments                   Required
                                                    The system shall e-mail Notices of Oral Argument to those parties
                                                    who have e-mail and fax Notices of Oral Argument for those who do
CM-122 Oral Arguments                   Required    not.
                                                    The system shall identify the origination of an oral argument: Parties
                                                    make a request which is granted, Court schedules an Oral Argument
                                                    Sua Sponte (on its own action), Traveling Oral Argument request
CM-123 Oral Arguments                   Required    from an institution.
                                                    For oral arguments, the system shall allow the user to maintain
                                                    (add/update/delete) which attorneys are arguing.
CM-124 Oral Arguments                   Optional
                                                    When scheduling cases for Oral Argument, the system shall warn the
                                                    user if an attorney is scheduled for more than one oral argument on
CM-125 Oral Arguments                   Optional    the same day.



                                                                                                                                                          CM 17
   State of Indiana                                                               Requirements                                                    PNCO# ACMS-2010
   Appellate Court Case Management System                                                                                                               July 9, 2010

  ID             Sub-Category               Priority                     Case Management Requirements                           Vendor Response   Comments
                                                       Once an oral argument calendar has been designated as final, if
                                                       changes to the oral argument date and/or time for a case are made,
                                                       the system shall e-mail a notice of the change to the appropriate
CM-126 Oral Arguments                   Desired        court staff.
                                                       The system shall allow the authorized user to choose an open oral
CM-127 Oral Arguments                   Desired        argument time slot and assign a case to that time slot.
                                                       The system shall allow the court to record the oral argument dates
                                                       and preferred case types for those dates, the designated panel for
                                                       the time block, and the special location of the oral argument, if
CM-128 Oral Arguments                   Desired        known.
                                                       The system shall allow the user to change an oral argument date and
                                                       record the reason for the change, then have the system move all the
                                                       associated cases to the new day, and generate Notices of Oral
CM-129 Oral Arguments                   Desired        Argument for those cases.
                                                       The system shall allow the user to indicate that a filled time slot on
CM-130 Oral Arguments                   Desired        the oral argument calendar is final.
                                                       The system shall allow the user to record the names and contact
                                                       information (address, location, etc.) and email address of persons
                                                       who should receive a copy of the oral argument calendar.
CM-131 Oral Arguments                   Desired
                                                       The system shall inform designated court administration staff if a
                                                       party does not file an Acknowledgement of Oral Argument by a user-
                                                       defined period of time before the oral argument date. The user-
                                                       defined time period is the default and can be changed.
CM-132 Oral Arguments                   Desired
                                                       The system shall keep a history of oral argument dates/times that
                                                       have been set for a case, along with the reason for any change after
                                                       the first one, for any oral argument scheduled that had a Notice of
CM-133 Oral Arguments                   Desired        Oral Argument generated.
                                                       The system shall show the user the next available oral argument
CM-134 Oral Arguments                   Desired        time slot or all available time slots.
                                                       The system shall track case votes by judge as writing judge and as
                                                       non-writing judge, including vote date and vote comments.
CM-135 Vote Tracking                    Required
                                                       For a bar discipline case, the system shall allow the user to record
                                                       the hearing officer submissions or other discipline writings.
CM-136 Disposition Management           Required




                                                                                                                                                             CM 18
   State of Indiana                                                               Requirements                                                     PNCO# ACMS-2010
   Appellate Court Case Management System                                                                                                                July 9, 2010

  ID             Sub-Category               Priority                      Case Management Requirements                           Vendor Response   Comments
                                                       If the original decision changes due to a disposition from Petition for
                                                       Rehearing or other situation, the system shall record the petition's
                                                       disposition, allow the user to update the original Opinion, and keep
CM-137 Disposition Management           Required       a history of disposition, dates, etc.
                                                       The system shall allow a user to vacate/withdraw/substitute an
CM-138 Disposition Management           Required       opinion and/or judgment.
                                                       The system shall allow an opinion to apply to one or more cases, and
CM-139 Disposition Management           Required       a case to have zero to many opinions.
                                                       The system shall allow for more than one majority opinion per case.
CM-140 Disposition Management           Required
                                                       The system shall allow the user to record that a Supreme Court case
                                                       was remanded to the Court of Appeals or the Tax Court and allow
                                                       the user to enter a new intermediate opinion/judgment when a new
CM-141 Disposition Management           Required       decision is rendered.
                                                       The system shall allow the user to record that the Opinion is being
CM-142 Disposition Management           Required       circulated and the date of circulation.
                                                       The system shall be able to capture case dispositions at a detailed
                                                       level (e.g. affirmed in part, remanded and affirmed, etc.).
CM-143 Disposition Management           Required
                                                       The system shall identify opinions as for publication or not for
CM-144 Disposition Management           Required       publication.
                                                       The system shall keep track of how long it took to dispose of a
CM-145 Disposition Management           Required       motion.
                                                       The system shall provide a process for closing a case that includes
                                                       changing the case status to "Closed", recording the disposition type
CM-146 Disposition Management           Required       and method, and the reason for the closure.
                                                       The system shall track opinions by judge as writing judge and as non-
CM-147 Disposition Management           Required       writing judge.
                                                       Automate the ability to collect appropriate information and send
CM-148 Disposition Management           Desired        electronically to Westlaw.
                                                       Automate the ability to receive from Westlaw (WL) and North
                                                       Eastern Reporter citation numbers assigned to cases and update
CM-149 Disposition Management           Desired        case information with the citation numbers.
                                                       The system shall allow the user to add or update the reporter
CM-150 Disposition Management           Desired        citation information for a case.
                                                       The system shall allow the user to designate the prevailing party or
CM-151 Disposition Management           Desired        parties on a decision.




                                                                                                                                                              CM 19
   State of Indiana                                                               Requirements                                                      PNCO# ACMS-2010
   Appellate Court Case Management System                                                                                                                 July 9, 2010

   ID            Sub-Category               Priority                     Case Management Requirements                             Vendor Response   Comments
                                                       The system shall allow the user to store and retrieve citation and
                                                       publication information about a case, from a legal research provider
                                                       (i.e. North Eastern Reporter, Westlaw (WL), Lexus/Nexus, etc.).
CM-152 Disposition Management           Desired
                                                       The system shall keep disciplinary history of an attorney, including
CM-153 Disposition Management           Desired        the date and type of discipline.
                                                       When a case is disposed, the system shall display all active ticklers.
CM-154 Disposition Management           Desired
                                                       When a case is pending disposition that could affect the outcome of
                                                       other related appeals, the system shall allow a user to identify other
                                                       cases that will be affected by its disposition.
CM-155 Disposition Management           Desired
                                                       When the case is disposed, the system shall alert the user by
                                                       displaying a list of the related open cases, allowing the user to
CM-156 Disposition Management           Desired        update those cases for disposal in the appropriate manner.
                                                       If an e-mail address is stored for a party or their attorney, the
                                                       system shall allow the user to indicate for each document, whether
                                                       to send the notification to the particular party or attorney by e-mail,
                                                       fax, or by snail mail (this can be indicated for all documents or set on
CM-157 Notifications                    Required       a document by document basis).
                                                       On a tickler, the system shall allow the user to edit the due date,
CM-158 Notifications                    Required       event type due, responsible party.
                                                       The system shall allow a user to update, enter comments, or remove
CM-159 Notifications                    Required       system generated ticklers.
                                                       The system shall allow an authorized user to design programmatic
                                                       notifications to be associated with specific event occurrences and for
                                                       the notifications to automatically be canceled on the occurrence of
CM-160 Notifications                    Required       other designated events.
                                                       The system shall allow for court requests to be automatically
CM-161 Notifications                    Required       sent/received between the trial and appellate courts.
                                                       The system shall allow for notification of an out of date event
CM-162 Notifications                    Required       occurring within a user-defined number of days.
                                                       The system shall allow the authorized user to set the types of ticklers
                                                       that are available for each action that is taking place on the case.
CM-163 Notifications                    Required
                                                       The system shall allow the user to change the status of a tickler so
CM-164 Notifications                    Required       that it can be closed or satisfied.




                                                                                                                                                               CM 20
   State of Indiana                                                               Requirements                                                      PNCO# ACMS-2010
   Appellate Court Case Management System                                                                                                                 July 9, 2010

   ID            Sub-Category               Priority                        Case Management Requirements                          Vendor Response   Comments
                                                       The system shall allow the user to create a reminder (tickler) for a
                                                       particular future event due, including the type of event, the date
                                                       due, the person who created the tickler, the date created, and which
CM-165 Notifications                    Required       party is to fulfill the tickler.
                                                       The system shall allow the user to display all ticklers on a case while
CM-166 Notifications                    Required       viewing the case.
                                                       The system shall allow the user to record that a phone call was
                                                       received or made, the date, to whom, the reasons for the call, and
                                                       to associate that call with a case and when applicable, a scheduled
CM-167 Notifications                    Required       due date.
                                                       The system shall allow the user to set the start date for the due date
CM-168 Notifications                    Required       calculation, with the default being the current date.
                                                       The system shall calculate due dates by calendar days or by court
CM-169 Notifications                    Required       business days.
                                                       The system shall calculate due dates in calendar days by adding the
                                                       number of days to the start date. Due dates falling on a weekend or
                                                       holiday, shall be moved to the next business day.
CM-170 Notifications                    Required
                                                       The system shall generate Letters, Notices, and Orders (or any other
                                                       "Official Court Document") with the ability to add task due dates
CM-171 Notifications                    Required       that are stored in the system as ticklers.
                                                       The system shall notify the user if the e-mail address for the party is
CM-172 Notifications                    Required       not valid and of any email transmission errors.
                                                       The system shall send notices, letters, or orders using e-mail if there
                                                       is a valid e-mail address for that participant, allow administrative
CM-173 Notifications                    Required       override to use mail or fax.
                                                       When generating a Notice, the system shall assume (default) that all
                                                       active parties (or their attorney if they have one) to the case will get
                                                       a copy of the document, and that participants and interested
CM-174 Notifications                    Required       persons by default will not get a copy.
                                                       If the tickler date for the court record passes, the system should
                                                       automatically send an e-mail reminder to the trial court and record
CM-175 Notifications                    Optional       that the reminder was sent.
                                                       The system shall allow the user to see whether an e-mail notification
CM-176 Notifications                    Optional       has been read.
                                                       On manually created ticklers, the system shall allow the user to set
CM-177 Notifications                    Desired        the start date for the due date calculation.




                                                                                                                                                               CM 21
   State of Indiana                                                               Requirements                                                     PNCO# ACMS-2010
   Appellate Court Case Management System                                                                                                                July 9, 2010

   ID            Sub-Category               Priority                      Case Management Requirements                           Vendor Response   Comments
                                                       The system shall allow for an e-mail to be sent to the appropriate
                                                       court staff if a motion is filed on a case that is on the oral argument
CM-178 Notifications                    Desired        calendar.
                                                       The system shall allow the user to add a comment to all tickler
CM-179 Notifications                    Desired        events.
                                                       The system shall allow the user to ask for specific tickler events past
                                                       due, and when listed, allow the user to indicate which cases need to
                                                       receive a user-specific type of Notice or Order.
CM-180 Notifications                    Desired
                                                       The system shall allow the user to send requests to the trial court for
CM-181 Notifications                    Desired        the court record by e-mail.
                                                       The system shall send an e-mail notification to the writing
                                                       Judge/Justice office when another Judge/Justice has entered a case
CM-182 Notifications                    Desired        vote.
                                                       When the user requests a list of tickler events, the system shall show
                                                       the case numbers and captions for each case on the list.
CM-183 Notifications                    Desired
                                                       A case shall clearly indicate if the filing fee payment has been
                                                       received and not allow any filings on the case until a fee payment is
                                                       made or Proof of Appointment/Proof of Pauper Status is indicated.
CM-184 Financial Processing             Required
                                                       The system shall allow authorized users to define the default fee
CM-185 Financial Processing             Required       amount of specific types of filings.
                                                       The system shall allow for adding and maintaining fee amounts due
                                                       on a case using default values and allow for authorized users to
CM-186 Financial Processing             Required       override.
                                                       The system shall record fee payments made on a case, payment
CM-187 Financial Processing             Required       method, payment amount, payment date.
                                                       The system shall keep a common receivable identifier number for
                                                       the updating of information between the financial module and the
CM-188 Financial Processing             Desired        Indiana Auditor of the State department.
                                                       The system shall transfer data from the financial module to the
                                                       state's accounting system or from the Indiana Auditor of the State
CM-189 Financial Processing             Desired        department to the financial module.




                                                                                                                                                              CM 22
State of Indiana                                                                  Requirements                                                              PNCO# ACMS-2010
Appellate Court Case Management System                                                                                                                           July 9, 2010]

    ID             Sub-Category           Priority                        Document Management Requirement                                 Vendor Response   Comments
                                                     The system shall allow a Notice to be associated to an order and/or motion.
   DM-001 Document Relationships         Required
                                                     The system shall allow for a motion to be eventually tied to an order. The
                                                     motion/order association can be: one motion to one order, many motions to
   DM-002 Document Relationships         Required    one order, one motion to many orders.
                                                     The system shall allow the user to view the case docket related documents
   DM-003 Document Relationships         Required    together as a "thread".
                                                     The system shall show motions in one color before they are associated with an
                                                     order, and then a different color when they are associated with an order, with
   DM-004 Document Relationships         Desired     colors to be specified by an authorized user.
                                                     The system shall provide the ability to track correspondence information: name
                                                     of sender, trial court cause number, case number, date received, DOC number,
                                                     if related to an open or closed case, if it became a motion, clerk filing date.
   DM-005 Document Relationships         Required
                                                     The system shall allow a user to enter detailed information about archive record
   DM-006 Document Tracking              Required    check outs/in, permanent withdrawals or destruction.
                                                     The system shall allow the user to indicate that a case or motion is on hold and
                                                     to remove the hold, noting the duration of the hold time period (in days).
   DM-007 Document Tracking              Required
                                                     The system shall allow the user to record who received a document or set of
   DM-008 Document Tracking              Required    documents, and the date received.
                                                     The system shall allow the user to record who routed a document or set of
   DM-009 Document Tracking              Required    documents, the date sent, and to whom it was sent.
                                                     The system shall have a file management or inventory control method to track
   DM-010 Document Tracking              Required    the location of case records.
   DM-011 Document Tracking              Required    The system shall keep track of how long it took to dispose of a motion.
                                                     The system shall provide the user the ability to record that an "official court
                                                     document" was received (received date), but not filed (filed date) because of
   DM-012 Document Tracking              Required    non-compliance.
                                                     The system shall record the receipt date of court records and the item(s)
   DM-013 Document Tracking              Required    received.
                                                     The system shall store, in a central location, language used in orders for shared
                                                     purposes by judicial staff to be used for searchable 'like' situations. Also allow
                                                     document language to be searchable and display in preview mode without
   DM-014 Document Tracking              Required    opening each document.
                                                     The system shall track motion information: party filing motion, trial court cause
                                                     number(s), date filed in Clerk’s Office, appellate case number, date received in
                                                     Clerk’s Office, date received in Court of Appeals office, related order, motion
   DM-015 Document Tracking              Required    type.

                                                                                                                                                                       DM 23
State of Indiana                                                                  Requirements                                                            PNCO# ACMS-2010
Appellate Court Case Management System                                                                                                                         July 9, 2010]

    ID             Sub-Category           Priority                         Document Management Requirement                              Vendor Response   Comments
                                                     The system shall track order information: related case, any motion(s) resulting
   DM-016 Document Tracking              Required    from the order, order mail date, order issue date.
                                                     When processing (printing or e-mail) a batch of Notices, if there is any problem
                                                     with printing, the notice event should not be entered into the case register, and
   DM-017 Document Tracking              Required    the user should be notified that there was a problem.
                                                     When recording that transcripts have been received, the system shall show a list
                                                     of all the court reporters on the case and allow the user to indicate whose
   DM-018 Document Tracking              Required    transcript has been filed.
                                                     The system shall allow a particular recipient of records/case files to list on the
                                                     screen the case and the records they should have received, and allow the
   DM-019 Document Tracking              Desired     recipient to check off the records/files actually received.
                                                     The system shall allow the authorized user to determine the document types
   DM-020 Document Tracking              Desired     that may be tracked for routing purposes.
                                                     The system shall keep track of all opinions on the case from the time they are
                                                     assigned to a judge, including opinion status, staff assigned, opinion type.
   DM-021 Document Tracking              Desired
                                                     The system shall provide for the ability to drill down to supporting documents
   DM-022 Document Tracking              Desired     and related transactions from any screen within the system.
                                                     When a signed order is received from a judge, the system shall allow the user to
                                                     update the order's filing date and signed by fields, and change the order status
   DM-023 Document Tracking              Desired     to "Signed".
                                                     When an order is generated that must be signed, the system shall set the order
   DM-024 Document Tracking              Desired     status to "Awaiting Signature".
                                                     When generating an "official court document", the system shall store the
                                                     document in a predefined location and provide a link to that location in the
   DM-025 Document Tracking              Desired     database.
                                                     Any notice or other form, if e-mailed, shall be as an attachment in .pdf format
                                                     (ensuring that any meta data contained with the document is not included in
   DM-026 Generate Documents             Required    the .pdf)
                                                     If a party-document submitted for filing contains deficiencies, the system shall
                                                     note it in the Notice of Deficiency Letter and include any new due dates.
   DM-027 Generate Documents             Required
                                                     The system shall allow for the electronic signature of documents based on user
                                                     password and shall insert a reasonable facsimile wet-ink signature on
   DM-028 Generate Documents             Required    documents where desired.
                                                     The system shall allow notify all parties on the case when a "received"
   DM-029 Generate Documents             Required    document becomes "filed".



                                                                                                                                                                     DM 24
State of Indiana                                                                   Requirements                                                              PNCO# ACMS-2010
Appellate Court Case Management System                                                                                                                            July 9, 2010]

    ID             Sub-Category           Priority                        Document Management Requirement                                  Vendor Response   Comments
                                                     The system shall allow the user to create, edit, or delete a template for "official
                                                     court documents" in MS Office Word, and identify within the document, the
                                                     placement of case management database fields (similar to a mail
   DM-030 Generate Documents             Required    merge/InfoPath function).
   DM-031 Generate Documents             Required    The system shall allow the user to edit any "official court document".
                                                     The system shall allow the user to generate an "official court document" in an
                                                     editable document from a template merged with case management data.
   DM-032 Generate Documents             Required
                                                     The system shall include case title pages for future documents. The title page
                                                     includes case caption, party designations, name of the lower court, lower court
   DM-033 Generate Documents             Required    case number(s), appellate case number(s).
                                                     When an "official court document" is delivered to someone, the system shall
                                                     record the type of document delivered, the date delivered, the user who
                                                     delivered it, the participants who received it, and those who received it as a cc,
   DM-034 Generate Documents             Required    and the delivery method used.
                                                     When printing any documents, the user should see a "print preview" and be
                                                     allowed to select certain page(s) to print.
   DM-035 Generate Documents             Required
                                                     When printing any type of document (notice, report, etc.), the system shall
   DM-036 Generate Documents             Required    allow the user to select the printer and paper source.
                                                     The system shall allow users to print file labels and indicate what case
   DM-037 Generate Documents             Optional    information is to be included on the label.
                                                     In any instance where notices may be generated, the system shall allow the user
   DM-038 Generate Documents             Desired     to transmit the notice to a selected distribution.
                                                     The system shall allow the user to send notices/requests to the trial court for
   DM-039 Generate Documents             Desired     the court record by e-mail.
                                                     The system shall allow the user to store a copy of the e-mail that was sent to
   DM-040 Generate Documents             Desired     parties with a notice, order, or letter.
                                                     The system shall group document templates by subject area and allow the user
   DM-041 Generate Documents             Desired     to select the template from the subject area.
                                                     When an order is being generated, the system shall allow the user to indicate
                                                     whether the order needs the judge/justice signature or is being administratively
   DM-042 Generate Documents             Desired     allowed with signature as the default.




                                                                                                                                                                        DM 25
State of Indiana                                                                   Requirements                                                                 PNCO# ACMS-2010
Appellate Court Case Management System                                                                                                                                July 9, 2010

    ID          Sub-Category             Priority                             Conflict Management Requirements                                Vendor Response     Comments
                                                    The system shall provide the ability for each user of the case management system
CF-001     Conflict Management     Required         to create and maintain their own list of conflict of interest items.
                                                    The system shall provide the ability for users, with the appropriate level of security,
                                                    to create and maintain lists of conflicts for justices, judges, court staff, and other
CF-002     Conflict Management     Required         users.
                                                    A conflict of interest item is composed of at least the following details: Court staff
                                                    member (case management user) that the conflict belongs to, the type of conflict
                                                    (attorney, law firm, administrative agency, party, lower court judge, etc.), name(s)
                                                    associated with the type of conflict, begin/end dates of the conflict.
CF-003     Conflict Management     Required
                                                    The system shall provide the ability to configure case management data elements
                                                    to a corresponding type of conflict of interest. For instance, a conflict type of
                                                    attorney would be associated with the case assigned attorney data element.
CF-004     Conflict Management     Required
                                                    The system shall provide the ability to identify case events (judge/justice
                                                    assignment to a case, issued orders, motion panel assignment, etc.) that trigger a
                                                    check for a conflict of interest and cause an alert if appropriate. For instance,
                                                    assign a justice/judge to a case, the system searches for any conflicts for that judge
                                                    that might relate to the case. The judge has a conflict with a law firm, the system
                                                    would check to see if any of the attorney's assigned to the case work for that law
                                                    firm. If so, then alert the case management user and stop the judge assignment.
CF-005     Conflict Management     Required
                                                    The system shall provide the ability to prevent the continuation of the current case
CF-006     Conflict Management     Required         management activity in the event of a conflict.
                                                    In the event of a conflict, the system shall allow users, with the appropriate level of
                                                    security, to override the conflict alert and continue the current case management
CF-007     Conflict Management     Required         activity. Any overridden event is tracked by the system.
                                                    The system shall provide the ability to search for and display conflicts that exist on
                                                    cases within the case management system. Search ability at a minimum should be
CF-008     Conflict Management     Required         by the data elements used to create a conflict.




                                                                                                                                                                          CFM 26
State of Indiana                                                            Requirements                                                               PNCO# ACMS-2010
Appellate Court Case Management System                                                                                                                       July 9, 2010

     ID                Sub-Category       Priority                                e-Filing Requirement                               Vendor Response    Comments
                                                     Allow registered users to file documents electronically with the clerk's office
                                                     as "approvers" before the document is accepted into the case management
                                                     system. The filing shall appear on the docket as "tentatively filed" until the
EF-001       Case Mgmt. Integration      Required    clerk's office approves the filing.
                                                     System stores information associated with the filing until the clerks office
EF-002       Case Mgmt. Integration      Required    accepts the filing.
                                                     The case management system is used to access or point to the location of
EF-003       Case Mgmt. Integration      Required    documents in electronic court records.
                                                     System provides for review of data and documents by court staff prior to
                                                     inclusion in the court record based on local procedures and rules.
EF-004       Clerk Review                Required
                                                     If the filer must take additional action after clerk review, the system
                                                     provides a method for the clerk to send a notice electronically (by default),
EF-005       Clerk Review                Required    or mail, or fax to the filer.
                                                     System provides provisional confidentiality for specified case types until a
EF-006       Confidentiality             Required    determination on confidentiality is made by the court.
                                                     System allows for changes of confidentiality status for documents or the
EF-007       Confidentiality             Required    case during the life of the case.
                                                     Based on the nature of the document and the nature of case, system
                                                     provides automatic confidentiality at the time of an electronic document
                                                     filing in accordance with statutes and rules or court orders.
EF-008       Confidentiality             Required
                                                     System allows for court judicial officers and court staff to participate in the
EF-009       Court Filings               Required    system as filers.
EF-010       Court Filings               Required    System informs parties of court initiated filings.
                                                     System delivers 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 staff for record entry into or retrieval from case management or
EF-011       Doc. Mgmt. Integration      Required    document management systems.
                                                     System provides a means to verify the integrity of any electronic document
EF-012       Document Integrity          Required    received and stored by the court.
EF-013       Document Integrity          Required    System provides document redundancy (backups).
                                                     Hash algorithms must be provided within receipt and the system must
EF-014       Document Integrity          Required    provide a document history of hashes.
                                                     At a minimum, system must comply with FIPS 180-2 or successors.
EF-015       Document Integrity          Required    (http://www.itl.nist.gov/fipspubs/fip180-2.htm).
                                                     The system provides automatic notice to all parties when a filer sends a
EF-016       Draft Documents             Optional    proposed order to a judicial officer for consideration.


                                                                                                                                                                   EF 27
State of Indiana                                                            Requirements                                                                PNCO# ACMS-2010
Appellate Court Case Management System                                                                                                                        July 9, 2010

     ID                Sub-Category       Priority                                  e-Filing Requirement                              Vendor Response    Comments
                                                     The system provides automatic notice to all parties when the judicial officer
EF-017       Draft Documents             Optional    returns a modified proposed document to the sending parties.
                                                     The system provides a method for parties to transmit proposed orders and
                                                     other proposed materials to judicial officers for consideration, with or
                                                     without docketing the event and committing the document and data to the
EF-018       Draft Documents             Optional    database.
                                                     System provides a method for the judicial officer to return a modified
                                                     proposed document to the sending parties with or without docketing the
EF-019       Draft Documents             Optional    event and committing the data to the database.
                                                     The system shall provide on-line forms (court documents) that interface
                                                     with the case management system using Legal XML and NIEM standards for
EF-020       Electronic Documents        Required    data transfer.
                                                     System records all dates and times needed to apply court rules governing
                                                     the time and date that court filing occurs and informs filer of the data and
EF-021       Electronic Documents        Required    time of filing.
                                                     System accepts the importation of non-electronic documents into the
EF-022       Electronic Documents        Required    electronic court record in accordance with statutes and rules.
                                                     System provides a method for handling other electronic materials involved
                                                     in a case, including, e.g., transcript, exhibits, and multimedia presentations
EF-023       Electronic Documents        Required    made to the jury.
                                                     With the variety of possible implementations, in the event that multiple
                                                     electronic filing front end systems may be used, all documents associated
                                                     with the case and filed through any of the front end systems must be
                                                     viewable as a single electronic record. The system must be capable of
                                                     displaying documents in all formats allowed by the court, maintaining the
                                                     integrity of the content and format of every document.
EF-024       Electronic Documents        Required
EF-025       Electronic Documents        Required    System will produce copies on demand.
                                                     System supports automated docket entries for subsequent filings without
EF-026       Existing Case Filing        Optional    clerk review.
                                                     System allows automated receipt of subsequent filings without requiring
EF-027       Existing Case Filing        Optional    submission of the case to the clerk review queue.
                                                     System accommodates payments in accordance with statutes and rules.
EF-028       Fee Payment                 Required
                                                     Front End Application is able to support the court’s policy on filing when the
                                                     court’s accepting system is down (i.e. front end application makes a record
                                                     of a filer’s attempt to file or otherwise maintains attempted filings in a
                                                     queue for later processing when the accepting system is back up).
EF-029       Filing Acceptance           Required


                                                                                                                                                                    EF 28
State of Indiana                                                              Requirements                                                             PNCO# ACMS-2010
Appellate Court Case Management System                                                                                                                       July 9, 2010

     ID                Sub-Category          Priority                                  e-Filing Requirement                          Vendor Response    Comments
                                                        The system informs the filer of the acceptance or rejection of an electronic
                                                        filing. The receipt must include the reasons for rejection and document
EF-030       Filing Acceptance              Required    hash.
                                                        Acknowledgements of filings must include an address by which the
                                                        document can be accessed for the purpose of linking it to subsequent filings
EF-031       Filing Acceptance              Required    in the same case.
                                                        System supports automated acceptance and rejection of filings and
                                                        documents in accordance with the form and substance requirements of the
EF-032       Filing Acceptance              Optional    court.
                                                        System conforms to existing COSCA/NACM standards and has the flexibility
                                                        to adapt to emerging COSCA/NACM standards found at
EF-033       General                        Required    http://www.ncsc.dni.us.
                                                        System provides a process to inform current users of court policy changes
EF-034       General                        Required    relative to electronic filing.
                                                        System describes unique court filing policies and standards in an XML
                                                        format, accessible free of charge by potential filers, including service
EF-035       General                        Desired     providers.
                                                        System assigns a unique case identifier until assignment of a permanent
EF-036       New Case Filing                Required    case number by the court.
                                                        System allows automated initiation of new cases without requiring
EF-037       New Case Filing                Required    submission of the case to the clerk review queue.
                                                        System supports automated docket entries for initial filings without clerk
EF-038       New Case Filing                Required    review.
                                                        The system shall provide for a secure login feature to access the e-filing
EF-039       Registration                   Required    system.
EF-040       Registration                   Required    System maintains a register of authorized users and identifiers.
                                                        System processes requests and responses to standard queries for court
EF-041       Request for Case Information   Required    records according to the standard protocol approved by COSCA/NACM.
                                                        Every response to a query includes the most current, complete and accurate
                                                        case management and document management records as defined by court
EF-042       Request for Case Information   Required    policy.
                                                        System provides a notice to the person making the query of the currency of
EF-043       Request for Case Information   Required    the information.
                                                        System supports queries of court records and responses to queries of court
EF-044       Request for Case Information   Required    records.
EF-045       Request for Case Information   Required    System notifies appropriate actors of updates to the court record.
                                                        The system provides the record transfer from/to an outside entity from the
EF-046       Request for Case Information   Required    electronic record in accordance with statutes and rules.


                                                                                                                                                                   EF 29
State of Indiana                                                               Requirements                                                                 PNCO# ACMS-2010
Appellate Court Case Management System                                                                                                                            July 9, 2010

     ID               Sub-Category           Priority                                e-Filing Requirement                                 Vendor Response    Comments
                                                        The system provides authentication and verification that the court order in
                                                        the court’s database is the court order received by the requestor.
EF-047       Request for Case Information   Desired
                                                        The system provides for archiving of data and documents in accordance
                                                        with approved retention, archiving and destruction policies.
EF-048       Retention/Archive              Required
                                                        The system provides for forward migration of all court documents. This
                                                        means that the court will be able to maintain forward compatibility of all
                                                        permanent court records. This can be accomplished either by requiring that
                                                        any new automated applications be able to display and print documents
                                                        created or maintained on the equipment and software the new applications
                                                        are replacing, or, alternatively, that all old documents be converted to a
                                                        format readable by the new equipment (i.e. ability to read current archiving
                                                        media and convert from those media to a new archive method)
EF-049       Retention/Archive              Required
                                                        System electronically serves documents and notice to other parties
                                                        participating in the electronic filing system, in accordance with statutes and
EF-050       Service/Notice                 Required    rules
                                                        The system provides for transmission of court generated documents to non-
EF-051       Service/Notice                 Required    electronic filing parties.
                                                        The system automatically creates and dockets in the court’s case
                                                        management system a certificate of service for the document served and
EF-052       Service/Notice                 Required    provides such to parties.
                                                        The system complies with statutes and rules for authentication of electronic
EF-053       Signatures/Authentication      Required    documents.
                                                        The system provides authentication of filer identity in accordance with
EF-054       Signatures/Authentication      Required    court policies.
EF-055       Signatures/Authentication      Required    System provides a method of authenticating judicial officer actions.
                                                        The system shall provide for receiving non-electronic filings (include delivery
EF-056       Submission                     Required    method and date/time of delivery).
                                                        If the court’s case management system is not operational, the front end
                                                        electronic filing system sends a message immediately to the filer and holds
                                                        the filing for submission when the court’s system is operational.
EF-057       Submission                     Required
                                                        Front-end system validates case number, filing parties, case types,
                                                        document types, and other elements required for populating the court’s
EF-058       Submission                     Required    database.
                                                        Front-end system provides error messages and correction options if the
                                                        filing is not in accordance with court policies, codes, and requirements
EF-059       Submission                     Required    including case openings.
                                                                                                                                                                        EF 30
State of Indiana                                                            Requirements                                                              PNCO# ACMS-2010
Appellate Court Case Management System                                                                                                                      July 9, 2010

     ID               Sub-Category        Priority                                e-Filing Requirement                              Vendor Response    Comments
EF-060       Submission                  Required    The system assigns and confirms a unique identifier for each filing.
                                                     The system architecture supports XML data exchange in accordance with
EF-061       System Architecture         Required    standards adopted by COSCA and NACM.
                                                     The system architecture incorporates migration strategies for new releases
EF-062       System Architecture         Required    of XML standards.
                                                     The system architecture provides capabilities for high-volume filers to
                                                     transfer large numbers of documents and attachments at one time (i.e.
EF-063       System Architecture         Optional    mass filing).
                                                     the system has disaster recovery and rollback capabilities consistent with
EF-064       System Architecture         Required    court needs and policy.
                                                     The system uses browser technology and complies with W3C technical
                                                     standards for a variety of platform operating systems and browsers.
EF-065       System Architecture         Required
EF-066       System Architecture         Required    The system complies with W3C web services standards.
                                                     The system supports annotation that is not part of the court record, with
EF-067       System Architecture         Required    appropriate confidentiality and access controls.
EF-068       System Security             Required    The system transmissions are secure.
                                                     The system provides an audit log of transactions as appropriate to the
EF-069       System Security             Required    court’s needs.
                                                     The system must provide for appropriate court staff to have control of
EF-070       System Security             Required    assignment and revocation of security levels and privileges.
                                                     The system provides appropriate processes for court staff to control user
                                                     privileges to create, modify, delete, print, or read electronic records.
EF-071       System Security             Required
                                                     The Legal Envelope and the associated document must both have state-of-
                                                     the-art and robust virus checking applied prior to transmission to the court
                                                     and upon receipt of the transmission at the court.
EF-072       System Security             Required
                                                     The system complies with generally accepted security protocols, including
EF-073       System Security             Required    use of HTTPS and secure socket layer (SSL).




                                                                                                                                                                  EF 31
State of Indiana                                                                   Requirements                                                                  PNCO# ACMS-2010
Appellate Court Case Management System                                                                                                                                 July 9, 2010

   ID        Sub-Category       Priority                                     Technology Requirement                                            Vendor Response   Comments
                                           The system shall allow a user to define and categorize fee types (e.g. filing fees, court costs).
 TE-001 Configurations        Required
                                           The system shall provide the ability to capture and store signatures or be compatible with
 TE-002 Configurations        Required     popular electronic signature software.
                                           The system shall allow for the association of event codes to each other (receive, grant,
 TE-003 Configurations        Required     deny).
                                           The system shall allow the authorized user to define what events are in the case
 TE-004 Configurations        Required     history/docket (differentiate between confidential and public).
                                           The system shall have user-defined tables as much as possible.
 TE-005 Configurations        Required
 TE-006 Configurations        Required     The system shall have user-defined work flows as much as possible.
                                           The system shall allow the authorized user to define case types and which case types are
 TE-007 Configurations        Required     expedited.
                                           The system shall allow the authorized user to define the types of motions, briefs, appeals,
 TE-008 Configurations        Required     notices, petitions, opinions, and orders.
                                           The system shall allow the authorized user to define address types.
 TE-009 Configurations        Required
                                           The system will permit the designation of prefix and suffix names through drop-down
 TE-010 Configurations        Required     selection.
                                           The system shall allow the authorized user to define "official court document" templates.
 TE-011 Configurations        Required
                                           The system shall allow the authorized user to define disposition types for orders and
 TE-012 Configurations        Required     opinions.
                                           The system shall allow the authorized user to define the method used to deliver documents
 TE-013 Configurations        Required     for filings (i.e. over the counter, e-mail, e-filed, facsimile, certified).
                                           The system shall allow the authorized user to define deficiencies for party filed documents.
                                           In addition, define the wording that will appear on the deficiency letter for each deficiency
 TE-014 Configurations        Required     document.
                                           The system shall provide session time-out defaults with the ability to inactivate automated
                                           session time-outs for internal court users. This means that if a user is logged into the
                                           system but has performed no activity within the session default time period, that user will
                                           be logged off of the system and must log back in in order to use the system.
 TE-015 Configurations        Required
 TE-016 Configurations        Required     The system shall allow the authorized user to determine the case statuses.
                                           All code tables shall have effective dates for codes. Examples of code tables are: state list,
 TE-017 Configurations        Required     party roles, types of documents, etc.
                                           The system shall allow the authorized user to define standard notice recipients on specific
 TE-018 Configurations        Required     notice types.
                                           The system shall allow the authorized user to define opinion types and opinion vote types.
 TE-019 Configurations        Required
                                                                                                                                                                             TE 32
State of Indiana                                                                   Requirements                                                                PNCO# ACMS-2010
Appellate Court Case Management System                                                                                                                               July 9, 2010

   ID        Sub-Category       Priority                                     Technology Requirement                                          Vendor Response   Comments
                                           The system shall allow the authorized user to define the party roles (categories of persons
 TE-020 Configurations        Required     on a case).
                                           The system shall allow the authorized user to define attorney roles by case.
 TE-021 Configurations        Required
                                           The system shall allow for the association of case types to different reporting groups (i.e. JV
                                           case type could be considered an Other case type for some reports) and for association of
                                           case types used in one court and associated to a case type in a different court (i.e. lower
                                           court case type mapping to either a Supreme Court or Court of Appeals case type).
 TE-022 Configurations        Required
                                           The system shall allow the authorized user to determine the events on the case that will
 TE-023 Configurations        Required     change a case's status.
                                           The system shall allow the authorized user to record holidays and non-working days for use
                                           by the tickler system, and shall prompt the authorized user to do so on a selected date
 TE-024 Configurations        Required     during the preceding year.
                                           The system shall have access and/or contain information about all the Judges and Justices in
                                           the state (name, role, current status, bar number, county/court assignments).
 TE-025 Configurations        Required
                                           The system shall store law clerk information (name, status, court assignment, active dates).
 TE-026 Configurations        Required
                                           The system shall allow the authorized user to define the judge type (senior, special, etc.).
 TE-027 Configurations        Required
 TE-028 Configurations        Required     The system shall allow the authorized user to define case types.
                                           The system shall allow for disposition types to be associated to reporting groups (see
 TE-029 Configurations        Required     Indiana Court of Appeals Annual Report).
                                           The system shall provide for County and Trial Court maintenance (number, name,
 TE-030 Configurations        Desired      associated courts, etc.) via on-line entry and batch interface
                                           The system shall allow the authorized user to define cost codes and assign them to events.
 TE-031 Configurations        Desired
                                           The system shall generate "official court documents" from templates and case management
                                           data. The resulting document will be stored as a non-modifiable document.
 TE-032 Configurations        Desired
                                           The system shall provide for data entry defaults.
 TE-033 Data Entry            Required
                                           The system shall give a warning for any date that is entered that is earlier than the current
 TE-034 Data Entry            Required     date.
                                           The system shall provide standard data entry edit checking and automatic data formatting.
 TE-035 Data Entry            Required
                                           The system shall warn the user if they associate an attorney to a case and that attorney
 TE-036 Data Entry            Required     does not have an “Active” bar status.

                                                                                                                                                                           TE 33
State of Indiana                                                                  Requirements                                                                PNCO# ACMS-2010
Appellate Court Case Management System                                                                                                                              July 9, 2010

   ID        Sub-Category       Priority                                     Technology Requirement                                         Vendor Response   Comments
                                           When the user is viewing a case or adding information to a case, the system shall
 TE-037 Data Entry            Required     prominently show the status of the case.
                                           The system shall provide clear and meaningful data entry messages (error/warning).
 TE-038 Data Entry            Required
 TE-039 Data Entry            Required     The system shall allow for wild card searches on appropriate text search fields.
                                           The system shall identify if a fee is due from a party and which party.
 TE-040 Data Entry            Desired
                                           When a user is viewing a case or adding information to a case, the system shall prominently
 TE-041 Data Entry            Desired      display to the user if the case is an expedited case.
                                           The system shall provide the ability to schedule routine activities for automatic execution at
                                           specified dates and times (batch processing). Examples of such activities include full
 TE-042 Database Features     Required     database duplicate checks and exports of various ASCII files.
                                           The system shall have name fields that separate the name into first, middle, and last name,
                                           suffix, prefix.
 TE-043 Database Features     Required
                                           The system shall support storage of null values in data fields where null is an accepted
 TE-044 Database Features     Required     value.
                                           The system shall provide for a method to facilitate the transfer of data from the legacy
 TE-045 Database Features     Required     system into the new case management system.
                                           The system shall use an industry-standard, multi-user, relational database with record-
 TE-046 Database Features     Required     locking capability.
                                           The system shall provide rollback functionality. The rollback statement in SQL cancels the
                                           proposed changes in a pending database transaction. For instance, if a user has started to
                                           enter information, that information is not permanently saved to the database until they
                                           press save, if cancel is pressed any temporarily saved information is removed.
 TE-047 Database Features     Required
                                           The system shall maintain database audit trail (add/update/added by/updated by)
                                           information. Each record in the database will contain separate values for the date/time
                                           that the record was added, user who added the record, last date/time the record was
 TE-048 Database Features     Required     changed, user who last changed the record.
                                           The system shall track specified changed database table fields (old value/new value/change
 TE-049 Database Features     Required     date/changed by).
                                           The system shall store dates as date data types and include the century for display of dates
 TE-050 Database Features     Required     and for all mathematical calculations that involve date operations.
                                           The system shall have the capacity to replicate records to facilitate a fully functional
                                           redundant site, with the option to provide delayed or real-time synchronization.
 TE-051 Database Features     Required
                                           The system shall have the capacity to store and manage all information (data) for up to and
 TE-052 Database Features     Required     over one million cases (active, inactive, cancelled).


                                                                                                                                                                          TE 34
State of Indiana                                                                  Requirements                                                             PNCO# ACMS-2010
Appellate Court Case Management System                                                                                                                           July 9, 2010

   ID        Sub-Category       Priority                                      Technology Requirement                                     Vendor Response   Comments
                                           The system shall receive and update attorney information from the Roll of Attorneys on a
 TE-053 Database Features     Desired      nightly basis and on demand.
                                           The vendor shall provide documentation of the data model including all data elements,
 TE-054 Documentation         Required     logical relationships and a data model diagram.
                                           The current case management system, future upgrades and changes shall include complete
                                           technical, database, application, system administration procedures, and end user
                                           documentation that will be delivered and considered an integral part of the system.
 TE-055 Documentation         Required
                                           The system documentation shall contain sufficient database schematic documentation to
                                           identify all of the lookup tables and a description of which tables shall be maintained by
 TE-056 Documentation         Required     court staff.
                                           Error messages should clearly identify the field in error and describe how to enter the
 TE-057 Error Handling        Required     correct information.
                                           The system shall provide the ability for the system administrator to archive and purge the
 TE-058 Error Handling        Required     system error information.
                                           The system shall provide the ability for system administrators to read, search, copy and
 TE-059 Error Handling        Required     print error logs that report error conditions or system failures.
                                           The case management system shall be built to run in a thin client or web browser
 TE-060 External Interfaces   Required     environment.
                                           The system shall be compatible with Microsoft Office 2007 desktop software and Microsoft
                                           Outlook and Lotus Notes e-mail clients and any other desktop software (at least current
 TE-061 External Interfaces   Required     versions or any future version).
                                           The system shall not adversely impact the operation of the concurrently loaded desktop
 TE-062 External Interfaces   Required     suite software.
        External Interfaces   Required     Ability to retrieve, open, and edit documents on portable devices (iPad, tablet PC, etc.).
                                           The system shall perform updating from external batch sources (e.g., other application
 TE-063 External Interfaces   Desired      systems) through a standard interface.
                                           The system shall provide automatic reconciliation of all exported/imported data.
 TE-064 External Interfaces   Desired
                                           The system provides an authorized user with online capability to "drill down" from summary
 TE-065 GUI Features          Required     information to supporting detail information where appropriate.
                                           The system shall have consistent use of controls, function keys and function key names.
 TE-066 GUI Features          Required
                                           The system shall effectively current GUI features such as, drop-down menus, point and click
 TE-067 GUI Features          Required
                                           operations, scroll bars, scrollable list boxes, radio button, etc.
                                           The system shall provide keyboard equivalents for all menu options.
 TE-068 GUI Features          Required
 TE-069 GUI Features          Required     The system shall allow multiple windows to be open at the same time.



                                                                                                                                                                       TE 35
State of Indiana                                                                   Requirements                                                                PNCO# ACMS-2010
Appellate Court Case Management System                                                                                                                               July 9, 2010

   ID        Sub-Category       Priority                                      Technology Requirement                                         Vendor Response   Comments
                                           The system shall provide a link, where there are multiple lines of data in a grid, to view the
                                           detailed information for that document (i.e. filings, motions, dispositions, notices) without
 TE-070 GUI Features          Required     having to open another screen.
                                           The system shall provide immediate transfer of values from "Pop up/Drop down" lists to the
 TE-071 GUI Features          Required     appropriate field when selected and to proceed to the next entry field.
                                           Navigation from one field to the next behaves in the same manner for all input screens (left
                                           to right, top to bottom or top to bottom, left to right).

 TE-072 GUI Features          Required
                                           The system shall allow the user to toggle between active application modules and other
                                           office software applications (e.g., word processor, spreadsheet) through the use of icon,
                                           keystroke and/or menu options without exiting a current application/module.
 TE-073 GUI Features          Required
                                           The system shall have windows that can be minimized and expanded.
 TE-074 GUI Features          Required
                                           The system shall have online prompts or "balloon" help messages and context sensitive
 TE-075 GUI Features          Required     help.
                                           Information returned in search results shall allow for sorting by any column header.
 TE-076 GUI Features          Required
                                           The system shall “Gray out” commands and menu options when not available in the current
 TE-077 GUI Features          Required     context.
                                           The system shall provide a notification when a record has been successfully saved to the
 TE-078 GUI Features          Required     database.
                                           The system shall provide date calendar controls for date fields.
 TE-079 GUI Features          Required
                                           The system shall provide pop-up windows on data entry screens that display field values
 TE-080 GUI Features          Required     and permits selection of field values based upon cursor location.
                                           The system shall allow for paging backwards or forwards through screens.
 TE-081 GUI Features          Required
 TE-082 GUI Features          Required     The system shall provide consistent navigation patterns.
                                           The system shall provide the ability to navigate within multiple input screens without losing
 TE-083 GUI Features          Required     information entered on the original (or header) screen.
                                           The system shall support a list of recent values entered for each field (current session only).
 TE-084 GUI Features          Desired
                                           The system shall provide an extensive online help facility capable of being easily modified by
                                           system management. The help facility will include: window level, field level, error message,
                                           context sensitive, hypertext linked help, Indexed help, definable “wizards”.
 TE-085 Help                  Required


                                                                                                                                                                           TE 36
State of Indiana                                                                  Requirements                                                                PNCO# ACMS-2010
Appellate Court Case Management System                                                                                                                              July 9, 2010

   ID        Sub-Category       Priority                                      Technology Requirement                                        Vendor Response   Comments
                                           The system shall provide for administrative-defined limits on the time a report or query
 TE-086 Reporting             Required     takes to execute and the number of records to be retrieved with the user option to
                                           The system shall provide the ability to search using date range values (begin/end).
 TE-087 Reporting             Required
                                           The system shall be able to provide the annual report information. See the Indiana
                                           Supreme Court Annual Report
                                           (http://www.in.gov/judiciary/supremeadmin/docs/0809report.pdf); Indiana Supreme Court
                                           Disciplinary Commission (http://www.in.gov/judiciary/discipline/docs/0809-annrept.pdf);
                                           Indiana Court of Appeals (http://www.in.gov/judiciary/appeals/pubs.html); Indiana Tax
                                           Court (http://www.in.gov/judiciary/tax/docs/2008-annual-rept.pdf)
 TE-088 Reporting             Required
                                           The report-writing tool shall provide a print preview function for any report.
 TE-089 Reporting             Required
                                           The system shall provide standard views of the database that allow the user to easily query
 TE-090 Reporting             Required     for information.
                                           The system shall allow the user to save a report format and retrieve it later.
 TE-091 Reporting             Required
                                           The system’s ad hoc query capability shall allow the user to download the data into multiple
 TE-092 Reporting             Required     formats (text, excel, .pdf, etc.).
                                           The system's ad hoc query tool shall aggregate data and perform basic calculations as
 TE-093 Reporting             Required     provided by standard SQL queries (e.g. sum, count, average).
                                           The system shall allow the user to copy a report, change it, and save it as another report
 TE-094 Reporting             Required     format.
 TE-095 Reporting             Optional     The system shall update the reporting database on a user defined schedule.
 TE-096 Reporting             Optional     The system shall provide a separate reporting database.
                                           The system shall provide the ability to generate reports that include user-designed graphs
 TE-097 Reporting             Optional     and charts (organizational chart, line graph, pie chart, bar chart, min/mid/max line graphs).
                                           The system shall allow reports to include end-user defined headings, footers, and borders.
 TE-098 Reporting             Desired
                                           The system shall allow for reports to include user-defined control breaks and number of
 TE-099 Reporting             Desired      print lines per page.
                                           The system shall allow users to define a sort order for reports.
 TE-100 Reporting             Desired
 TE-101 Reporting             Desired      The system shall provide the ability to route reports via e-mail.
                                           The system shall provide the ability to create and print reports on special forms.              DELETED,
                                                                                                                                           response is not
 TE-102 Reporting             Desired                                                                                                      necessary
                                           The system shall run on-line reports in the background and allow users to continue
 TE-103 Reporting             Desired      processing.

                                                                                                                                                                          TE 37
State of Indiana                                                                   Requirements                                                              PNCO# ACMS-2010
Appellate Court Case Management System                                                                                                                             July 9, 2010

   ID        Sub-Category       Priority                                     Technology Requirement                                        Vendor Response   Comments
                                           The system shall provide the user with the ability to print specific pages of the report.
 TE-104 Reporting             Desired
                                           The system shall provide the user with the ability to specify the number of copies of the
 TE-105 Reporting             Desired      report to be printed.
                                           The system shall provide the ability for the end-user to view print progress of any report.
 TE-106 Reporting             Desired
                                           The system shall provide for processing reports in batch.
 TE-107 Reporting             Desired
                                           The system shall provide an on-line real-time reporting and query capability with the ability
 TE-108 Reporting             Desired      to reference a data dictionary.
                                           The system shall allow end-users to create and modify report queries on-line.
 TE-109 Reporting             Desired
                                           The system shall allow ad-hoc report/query definitions to be stored in private and public
 TE-110 Reporting             Desired      folders.
                                           The system shall allow the authorized user to exclude a case, or specific information within
 TE-111 Security              Required     a case, from view of any user outside the appellate arena (e.g. trial courts, attorneys,
                                           The system shall provide for the prompting of password expiration at least five (5) days
 TE-112 Security              Required     prior to actual expiration.
                                           The system shall provide the ability to establish a parameter-driven timeframe for which
 TE-113 Security              Required     password will expire if not changed.
                                           The system shall support integration with Active Directory or, in the alternative, the
 TE-114 Security              Required     establishment of user-maintained strong passwords.
                                           The system shall allow for reporting security levels to restrict user access to reports.
 TE-115 Security              Required
                                           The system shall provide the capability to restrict access by an individual user ID (or
 TE-116 Security              Required     identified group of user ID's).
                                           The system shall provide the ability to suspend all user access when a user ID is terminated.
 TE-117 Security              Required
                                           The system shall provide the ability for a security coordinator (a person with high level
                                           system privileges) to log out users when necessary to perform maintenance or other
 TE-118 Security              Required     activities that require users to leave the system.
                                           Standard reports and reports generated by the ad hoc report writer comply with the user's
 TE-119 Security              Required     security profile and not display data that would violate that profile.
                                           The system shall provide multi-level security controls to prevent unauthorized use of system
                                           and corruption of data, restrict access to the database, maintain database process controls,
 TE-120 Security              Required     and log all database transactions.
                                           The system shall provide screen security at the court level.
 TE-121 Security              Required
 TE-122 Security              Required     The system shall mask passwords so that it is not viewed when entered.

                                                                                                                                                                         TE 38
State of Indiana                                                                   Requirements                                                              PNCO# ACMS-2010
Appellate Court Case Management System                                                                                                                             July 9, 2010

   ID        Sub-Category       Priority                                      Technology Requirement                                       Vendor Response   Comments
                                           The system shall support access restriction capability to: screens and tables, data elements,
 TE-123 Security              Required     functions (add, change, delete, inquiry), electronic documents (electronic approvals),
                                           The system shall provide online inquiry into the security table(s) by authorized security
 TE-124 Security              Required     coordinators.
                                           The system shall provide the ability to view or obtain security reports showing:
 TE-125 Security              Required     Unauthorized system use, security profiles by user, security breaches or attempts.
                                           The system shall allow security coordinators to reset passwords without knowing the
 TE-126 Security              Required     existing password.
                                           The security table will be encrypted and not allow for viewing of password information.
 TE-127 Security              Required
                                           Each office or chambers may only see or print reports relating to their own private docket,
 TE-128 Security              Required     in addition to the public docket.
                                           The system shall support standard internet security including, but not limited to: Public Key
                                           Infrastructure (PKI), Digital Certificates/signatures, Secure Socket Layers (SSL), Secure
 TE-129 Security              Required     Hypertext Transfer Protocol (HTTPS).
                                           The system shall allow a system administrator to add or remove users or change security
 TE-130 Security              Required     level.
                                           The system shall provide role-based security including the ability to define both individual
 TE-131 Security              Required     and group access to data and functions.
                                           The system shall allow only authorized users to access information on Justice/Judge case
 TE-132 Security              Required     assignment.
                                           Users only have to log onto the system once to be allowed to access all application modules
 TE-133 Security              Required     for which he/she is authorized to access.
                                           The system shall allow a system administrator to assign users to specific Court(s) and
 TE-134 Security              Required     specific departments.
                                           When a data item is noted as protected at a certain level of security, the system shall
                                           restrict access to that data from a screen, the ad hoc query tool, or a standard report.
 TE-135 Security              Required
                                           The system shall provide the ability to disable log-on capabilities if unsuccessful password
                                           entry is attempted after a parameter-driven number of unsuccessful attempts.
 TE-136 Security              Required
 TE-137 Security              Desired      The system shall provide the ability to establish standard "user profiles" from which
                                           individual user ID's may inherit privileges. multiple users to a single security profile.
                                           The system shall provide the ability to assign
 TE-138 Security              Desired
                                           The system shall provide the ability to assign multiple security profiles to a single user.
 TE-139 Security              Desired
                                           The system shall provide the ability to define user security profiles.
 TE-140 Security              Desired
                                           The system shall provide the ability to maintain security parameter settings in an inactive
 TE-141 Security              Desired      status where security could be re-activated in the future.
                                                                                                                                                                         TE 39
State of Indiana                                                                  Requirements                                                               PNCO# ACMS-2010
Appellate Court Case Management System                                                                                                                             July 9, 2010

   ID        Sub-Category       Priority                                       Technology Requirement                                      Vendor Response   Comments
                                           The system shall issue an alert to the end-user and notify the system administrator after a
 TE-142 Security              Desired      specified number of unauthorized log on attempts.
                                           The system shall deactivate user logon id's after a system administrator defined time of
 TE-143 Security              Desired      inactivity (days/weeks).
                                           The system shall notify users (user responsible and any "management" users) when items in
 TE-144 Workflow              Required     their inbox have gone unprocessed for a user-defined period of time.
                                           The system shall change a case's status upon the addition or editing of particular events on
 TE-145 Workflow              Required     that case.
                                           The system shall allow for reporting of the number of workflow events approved/rejected
 TE-146 Workflow              Optional     for each step of the workflow and overall workflow.
                                           The system shall provide for the routing of workflow to multiple destinations, with options
 TE-147 Workflow              Desired      for parallel and serial flow where needed.
                                           The system shall provide an "inbox" for each user with workflow items to be reviewed.
 TE-148 Workflow              Desired
                                           The system shall support electronic signatures for approvals and rejections.
 TE-149 Workflow              Desired
                                           Workflows may be designated as informational or action (approval required).
 TE-150 Workflow              Desired
                                           The system shall provide for routing of rejected transactions to any prior approver (step).
 TE-151 Workflow              Desired
                                           The system shall provide for approval authority to be delegated to another user for a
 TE-152 Workflow              Desired      specified period of time (to cover vacations, etc.).
                                           The system shall allow the authorized user to define the activities on a case that cause a
 TE-153 Workflow              Desired      milestone to be recorded.
 TE-154 Workflow              Desired      The system shall allow the authorized user to define the milestones on a case.
                                           The system shall provide for steps in the workflow process to be bypassed by allowing
 TE-155 Workflow              Desired      approvers higher in the approval steps to approve transactions before they arrive in
                                           The system shall allow for the attachment of additional documentation to workflow events
 TE-156 Workflow              Desired      (word documents, spreadsheets, etc.).
                                           Workflow destinations may be specified as specific users or classes of users within agency or
 TE-157 Workflow              Desired      other user defined criteria.
 TE-158 Workflow              Desired      The system shall support an unlimited number of workflow steps.
 TE-159 Workflow              Desired      Completion or return to a workflow step could cause a case status to change.
                                           The system shall allow the authorized user to determine the events on the case that will
 TE-160 Workflow              Desired
                                           change a case's status. user defined workflows for any system event.
                                           The system shall support
 TE-161 Workflow              Desired




                                                                                                                                                                         TE 40
State of Indiana                                                                 Requirements                                                      PNCO# ACMS-2010
Appellate Court Case Management System                                                                                                                   July 9, 2010

    ID      Sub-Category       Priority                               Web Interface Requirement                                 Vendor Response   Comments
                                          Available case search criteria should consist of (at a minimum): attorney name,
                                          attorney number, judge/justice authoring opinion, trial court judge, case type,
                                          case name, case number, case results (affirmed, reversed, denied, etc.), case
WB-001 Public Portal        Required      status, dates, date ranges.
                                          Public displayed case information shall be sortable by search results column
WB-002 Public Portal        Required      headings in either ascending or descending order.
                                          The system shall display information on the lower court case(s) including lower
                                          court identifying number, lower court county or agency, file date, and lower
WB-003 Public Portal        Required      court judge.
                                          The system shall have the ability to publish public case information to the Court's
WB-004 Public Portal        Required      public web site upon request and nightly.
                                          The system shall publish all Appellate Court oral argument calendars on the
WB-005 Public Portal        Required      Public Portal web site upon request and nightly.
                                          The system shall show all cases except for those that have been specifically
WB-006 Public Portal        Required      marked as private in the case management system.




                                                                                                                                                               WI 41

				
DOCUMENT INFO
Description: Trial Court Organizational Charts document sample