Loading...
The URL can be used to link to this page
Your browser does not support the video tag.
Home
My WebLink
About
CourtAlert Response Combined
Response to Bozeman City Attorney Case Management System Request for Proposal August 27, 2021 ________________________________ Yaniv Schiller President 42 West 38th Street, New York. NY 10018 (212) 227-0391 yschiller@courtalert.com CourtAlert Response to RFP 2 Contents Executive Summary ..................................................................................................................... 6 Company Profile .......................................................................................................................... 9 Scope of Project ........................................................................................................................ 17 General Requirements .............................................................................................................. 22 Forms Management – These services facilitate the creation, modification, and usage of electronic forms to capture case and name related information in a structured, consistent format. These services, assist with the development and management of electronic forms, including form field design and data entry validation to assist users with entering relevant data. ...................................................................................................................................... 22 Reports Generation – services will include generating many types of reports including from case files, name files, and overall system data. Reports to include data reports, case status reports, discovery reports, calendar reports, and a variety of statistical, system, and performance reports. Report generation services support the organization and presentation of data into a useful, relevant, and interactive format, including stock reports as well as custom built reports. Vendor offers report building services as well as the ability of the City Attorney to create its own reports. .................................................................... 23 Search – These services include the ability for users to search and browse through case, people, and event data to find all records that match the search criteria. Examples include data entered by a certain attorney or cases that were decided in a particular jurisdiction, or records that contain a particular term. ............................................................................ 24 Security and Privacy – These services define the capabilities needed to support effective measures to protect and safeguard information and systems from inappropriate or unauthorized use, alteration, loss, or destruction and include, but are not limited to: ensure continuous observation of security rules and regulations; ensure appropriate level of protection for case related information and data; ensure data is protected against unauthorized modification, use, destruction, or disclosure; and assure confidentiality, integrity, and availability. The LCMS must be CJIS compliant and guarantee security of all data including confidential criminal justice information. ..................................................... 25 Case Data Management – Case file data management services determine what data elements should be captured and how data should be used and stored. These services facilitate the storage, processing, exchange and general administration of case related data in the case file. The case file is utilized to provide management oversight to prosecution, civil litigation and general legal services, e.g., management of case related CourtAlert Response to RFP 3 resources, assignments, authorizations and status changes, including metrics and accomplishments. ................................................................................................................. 26 Paperless environment - these services must provide and support a paperless office solution. ................................................................................................................................ 27 Client Management – The need for services to support the management of day-to-day client relationships and interactions. Clients include other County and City departments such as the police department, county district and justice courts, municipal court and the finance department. ............................................................................................................. 27 Calendaring – Calendaring for multiple people, including cross-access for all department members, multiple cases, schedule entries for upcoming court appearances, filing deadlines, meetings, and hearings for multiple courts, with customized views and printing and tickle events. .................................................................................................................. 27 Performance Measurement – These services are concerned with the development, refinement, and usage of performance metrics. .................................................................. 29 Business Rule Management and Automation – Business rules and workflows are reflected in locally determined practices or procedures that govern the way that routine business activities are performed and automated. ............................................................................. 29 Records Management – Ability to archive and retrieve closed files, and associated data and documents, in an easy and efficient manner. ...................................................................... 29 Document Management – This service will provide the ability to generate, modify, store, retrieve, and archive case and name specific documents within the proposed application and search the same. ............................................................................................................ 30 Discovery – Ability to record receipt and processing of discovery requests electronically, including Bates’s stamping, redacting, and indexing features to expedite process. Ability to record and produce all discovery electronically through LCMS. Preferably a separate discovery management section of LCMS. ............................................................................. 30 Victim services – this service will provide a victim services management section. Preferred features include data collection for grant reporting and text messaging capabilities. ........ 30 This is to meet with many classification features that allow users to classify document types and deadlines that can be used for specific purposes such as grant reporting. Additionally, fee management such as court fees investigation fees etc. can be recorded alongside activity entries. The fee reporting can also be used for grant reporting purposes. ............................................................................................................................................... 31 Legacy Data – this service will import legacy data in a readable, usable format. ................ 31 CourtAlert Response to RFP 4 Customization – This service must have the ability to be customized in order to fully support each area of practice within the department - Prosecution, Civil Litigation and General Legal. ....................................................................................................................... 31 Data Query – the services will be written in SQL language and allow the City Attorney to query its data as needed. ...................................................................................................... 31 System Integrations - This service includes the ability to build integrations between proposed system and other County and City systems hosting relevant case and justice data. System integrations include New World LERMS and Corrections used by the police department as well as the FullCourt Enterprise and efiling system used by the Bozeman county courts, municipal courts and administered by the Montana Judicial Branch. ......... 32 Compatibility – This service must have the ability to interface with other software currently used by the CAO, including but not limited to all Microsoft Office products and AdobePro. LexisNexis research tools preferred but not required........................................ 32 Platform - cloud based LCMS hosted by vendor. Vendor will maintain all City Attorney data on servers in the United States subject to US law. The City Attorney owns all data and vendor shall surrender that data to the City Attorney at the end of any contractual agreement. ............................................................................................................................ 32 Cloud Services Requirements .................................................................................................... 33 1. Service levels: What level of service should we expect? What is the City’s recourse for excessive downtime? Refund of percentage of monthly fee? ....................................... 33 2. Data ownership: Who owns the data we provide and what can be done with the data? 33 3. Data security: How secure is our data and how is it being kept secure? ................... 33 4. Data integrity: What do you do as a vendor to ensure our data maintains its integrity? ............................................................................................................................... 35 5. We require data centers to be located in the United States: What country will our data be located in? ............................................................................................................... 36 6. Responding to legal demands to disclose data: What is your process when someone subpoenas or requests our data from you as a vendor? ...................................................... 36 7. Reporting: What is your protocol for data breaches? ...................................................... 37 7. Disaster recovery: What protections/ protocols do you have in place to mitigate disasters? .............................................................................................................................. 37 CourtAlert Response to RFP 5 8. Business continuity: If you decide to bring your business to an end what happens to our data? ............................................................................................................................... 38 9. Termination rights and consequences: What is your termination policy both for you as a vendor and us as a customer? ....................................................................................... 38 10. Exit: If we exit our relationship what format can we get our data in and what assistance will you give us in transferring our data to us in a usable format? ..................... 38 Related Experience with Projects Similar to the Scope of Services .......................................... 39 Customer References ................................................................................................................ 39 Proposed Implementation Schedule ......................................................................................... 48 Present and Projected Workloads ............................................................................................ 52 Training ...................................................................................................................................... 52 Maintenance and Support ........................................................................................................ 53 List of Appendices ..................................................................................................................... 58 CourtAlert Response to RFP 6 Executive Summary CourtAlert (“the company”) is a leader in the Legal Case Management software and Case Tracking services in the country. The company was established in 1999 and offers the case management software since 2005. The company is headquartered in Manhattan, has an accounting back office in the Bronx, and the clients are nationwide (and some in Europe). CourtAlert is a privately owned company and does not disclose sales volume and it serves most large law firms around the country and many large organizations. CourtAlert provides Case Monitoring tools to large law firms, organizations, and law departments. The Case Monitoring services cover all the jurisdictions requested in this RFP with clear and concise alerts that notify the attorney the exact event that has occurred at the court. Most large law firms and many large law departments utilize CourtAlert services or software and have done so for many years. For example, the New York City Law Department, Con Edison, New York City Transit Authority, the Suffolk County, NY Attorney and the state of Rhode Island rely on this service. These jurisdictions and the alerts are described in detail below. CourtAlert also offers CourtAlert Case Management software (the Software), an easily configurable, off the shelf software used to keep track of your caseload, dockets, calendars and much more. The Software is designed for large law firms and law organizations and can be applied for non-litigation matters. For example, is successfully operating all the various functions of the Suffolk County, New York State Law Department which are tasked with diversified and sophisticated cases, not just litigation cases. All cases, of any type, are uniformity recorded and allowing for easy transfer within the organization and executives’ controls. The Software is also operational at many leading law firms, some with billing over $1 Billion and have diversified needs and categories of work / types of cases. In the contact list, which is enclosed, we will list just a few of these firms. Each firm brings with it its own experience, workflow, history, and policies and thus the Software is designed to be configurable and is capable of change over time with simple configuration changes. CourtAlert Response to RFP 7 CourtAlert offers a proven solution that works over diversified categories and government environment, and it will become operational within few months, not years. While we will provide a detailed description in this proposal, and certainly excited to be invited to demonstrate the Software, we urge the city attorney’s office of Boseman Montana, City Attorney’s Office (“CAO”) representatives to spend time at and with the various CourtAlert clients and watch the Software in action. Both our public sector clients and our private clients are very demanding organizations, and our own history demonstrate our true and unwavering commitment to support. The same commitment is extended to the CAO; please just speak with any of our clients. CourtAlert is also committed to innovation; our clients are the leaders in the marketplace and to maintain this status require ongoing development and enhancements. These enhancements and innovations are offered, in a controlled manner and without additional cost, to all clients. Software Releases can be as frequent as you wish and are implemented with minimal interruptions. CourtAlert’s motto is “We are Committed to Remain the Best”, and the company truly dedicates itself to continued enhancements and innovation to ensure our market leadership. It would be an understatement to say that CourtAlert continuously enhances the case management software system. It would perhaps be more accurate to say that CourtAlert systematically, ongoing, and quickly adds major functionality and features to the system. CourtAlert is also committed to keep being updated on developments in the courts. Our experience with the public sector also includes many years of serving the City of New York Law Department, arguably the largest law department in the world. CourtAlert main office is located Midtown Manhattan, New York City. However, many case management systems are implemented at remote locations, nationwide. We have successfully implemented case management in many states including California, Illinois and CourtAlert Response to RFP 8 elsewhere. Our methodology is designed to minimize the times a person is needed on sight, and this is proven to work very well. CourtAlert Response to RFP 9 Company Profile CourtAlert (“the company”) is a leader in the Legal Case Management software and Case Tracking services in the country. The company was established in 1999 and offers the case management software since 2005. The company is headquartered in Manhattan, has an accounting back office in the Bronx, and the clients are nationwide (and some in Europe). CourtAlert is a privately owned company and does not disclose sales volume and it serves most large law firms around the country and many large organizations. CourtAlert provides Case Monitoring tools to large law firms, organizations, and law departments. The Case Monitoring services cover all the jurisdictions requested in this RFP with clear and concise alerts that notify the attorney the exact event that has occurred at the court. Most large law firms and many large law departments utilize CourtAlert services or software and have done so for many years. For example, the New York City Law Department, Con Edison, New York City Transit Authority, the Suffolk County, NY Attorney and the state of Rhode Island rely on this service. These jurisdictions and the alerts are described in detail below. CourtAlert also offers CourtAlert Case Management software (the Software), an easily configurable, off the shelf software used to keep track of your caseload, dockets, calendars and much more. The Software is designed for large law firms and law organizations and can be applied for non-litigation matters. For example, is successfully operating all the various functions of the Suffolk County, New York State Law Department which are tasked with diversified and sophisticated cases, not just litigation cases. All cases, of any type, are uniformity recorded and allowing for easy transfer within the organization and executives’ controls. The Software is also operational at many leading law firms, some with billing over $1 Billion and have diversified needs and categories of work / types of cases. In the contact list, which is enclosed, we will list just a few of these firms. Each firm brings with it its own experience, workflow, history, and policies and thus the Software is designed to be configurable and is capable of change over time with simple configuration changes. CourtAlert offers a proven solution that works over diversified categories and government environment, and it will become operational within few months, not years. CourtAlert Response to RFP 10 While we will provide a detailed description in this proposal, and certainly excited to be invited to demonstrate the Software, we urge the Bozeman City Attorney Office (“CAO”) representatives to spend time at and with the various CourtAlert clients and watch the Software in action. Both our public sector clients and our private clients are very demanding organizations, and our own history demonstrate our true and unwavering commitment to support. The same commitment is extended to the CAO; please just speak with any of our clients. CourtAlert is also committed to innovation; our clients are the leaders in the marketplace and to maintain this status require ongoing development and enhancements. These enhancements and innovations are offered, in a controlled manner and without additional cost, to all clients. Software Releases can be as frequent as you wish and are implemented with minimal interruptions. CourtAlert’s motto is “We are Committed to Remain the Best”, and the company truly dedicates itself to continued enhancements and innovation to ensure our market leadership. It would be an understatement to say that CourtAlert continuously enhances the case management software system. It would perhaps be more accurate to say that CourtAlert systematically, ongoing, and quickly adds major functionality and features to the system. CourtAlert is also committed to keep being updated on developments in the courts. Our experience with the public sector also includes many years of serving the City of New York Law Department, arguably the largest law department in the world. CourtAlert main office is located Midtown Manhattan, New York City. However, many case management systems are implemented at remote locations, nationwide. We have successfully implemented case management in many states including California, Illinois and elsewhere. Our methodology is designed to minimize the times a person is needed on sight, and this is proven to work very well. Firm name, address, and principal contact for this RFP Yaniv Schiller will be the primary point of contact for this RFI. He has been the Project Manager on projects of a similar scale. Yaniv Schiller, President of CourtAlert 42 West 38th Street, New York, New York 10018 yschiller@courtalert.com CourtAlert Response to RFP 11 (212) 227 – 0391 Senior management of the firm Yaniv Schiller President of CourtAlert (212) 227 – 0391 yschiller@courtalert.com Eytan Schiller Chief Technology Officer (212) 227 – 0391 eschiller@courtalert.com Richard Fine Director of Sales (323) 646-1102 rfine@courtalert.com The primary responsibility for managing the CAO account rests with CourtAlert’s President, Yaniv Schiller. Yaniv has extensive past experiences in successfully managing projects similar to the one that is the subject of this CAO RFP. Mr. Schiller has managed the organic growth and development of the application, its training materials, and its client base for many years. He is uniquely positioned to continue to manage and support the delivery of this important service. For ease of administration, a lead developer and a secondary are assigned to each project. We propose Amit Choudhary and Eytan Schiller to fulfill these roles. Additional developers and Subject Matter Experts will be assigned as necessary. All staff members are well versed in the solution and in the field of Legal Case Management. This is what we do. Their highest qualification is their experience: Employees have experience installing, integrating, and providing training for the proposed solution for other clients. All employees, including the original programmers of the proposed solution, will be available for implementing the solution at the CAO. The resumes of the individuals mentioned (Appendix B – Resumes of key personnel) above will confirm that they are well qualified and experienced to successfully implement and support the proposed solution, train the CAO personnel, and manage the CAO account. Note that some personnel members have been designing and programming custom- systems for decades. CourtAlert Response to RFP 12 The following list of key personnel, description of the organization and organizational chart depicts CourtAlert’s well-defined task assignments: 1. Project Manager - Yaniv Schiller: Mr. Schiller administers and participates in all aspects of the organization and its operations. 2. Chief Technology Officer- Eytan Schiller: Eytan Schiller is the CTO and the product manager for the proposed solution 3. Solution Architects: Amit Choudhary, Sreekumar Neelamana and Divya Anilkumar. 4. Client Customer Support Manager: Anuradha Chaudhary 5. Requirements Definition and User Training - Yael Martin, Esq. 6. Client Customer Support – Kimberly Romano 7. Administration and Accounting - Ariela Shakarchi 8. Relations with the courts - Frank Byrne. After many years of service to the court, Frank has recently retired from State service, and is now working on a part time basis for CourtAlert. 9. Legal and CPA services - CourtAlert retains outside counsel and accountants to provide these services. Programming Team – The entirety of the programming contemplated in support of the services required by the CAO will be accomplished by in-house, full time programmers and not by outside consultants. CourtAlert does rely on consulting services in connection with some development, but not for the developments contemplated by this RFP. The specific assignment of personnel would be made subsequent to getting a full understanding and documentation of the CAO requirements. The determination of which staff members will work locally and remotely will be jointly determined by the CAO and CourtAlert Project Managers. A resume or summary of qualifications, work experience, education, certification, and skills for all key personnel, including any subcontractors, who will perform any aspect of this contract. Include each individual’s anticipated role and years of experience providing services similar to those described in this RFP CourtAlert Response to RFP 13 Key CourtAlert personnel who are deemed to be essential to the successful implementation and maintenance of the proposed service are: CourtAlert Project manager Yaniv Schiller, President Project Development Supervisor Eytan Schiller, Chief Technology Officer Lead Client Training Yael Martin, Training and Court Liaison Lead Developer Amit Choudhary, Solution Architect Secondary Developer Divya Anilkumar, Solution Architect Primary Support Anuradha Chaudhary, Support Manager Location CourtAlert’s main office is located at 42 West 38th Street, New York, NY 10018. Most of the company’s operations are centered and performed there. CourtAlert also has a Bronx office where certain administrative and accounting functions are handled. CourtAlert also has an office in Los Angeles, California. Client Base CourtAlert currently provides a variety of services to organizations with heavy case loads and in the context of organization-specific workflows and procedures: • Large Law Firms: The overwhelming majority of the top 300 law firms in the US use a variety of CourtAlert Software and services. • Law Organizations / Municipalities: CourtAlert Software and services are used by The New York City Law Department/Office of the Corporation Counsel, The State Of Rhode Island (including 26 agencies that fall under the Department of Administration), The Suffolk City Attorney’s Office, Consolidated Edison, and The Port Authority of NY/NJ, etc. Customer Support CourtAlert has always provided and continues to emphasize a strong commitment to customer support. The Customer support team is dedicated to immediately respond to clients’ concerns, customizing to the needs of our clients and to providing training as needed. CourtAlert Response to RFP 14 Our ongoing and long-term relationships with our clients are based on years of dedication to customer support and quality services. CourtAlert encourages the CAO office to contact the references listed in the relevant section of this proposal and welcomes any additional inquiries. It is gratifying and constructive, as well as heartwarming, for us to hear receive client comments. It is an important key to CourtAlert growth and market leadership. The clients CourtAlert serves are the most desired market share by all vendors. These clients repeatedly choose CourtAlert mainly because of its unique and genuine commitment to support. The clients’ endorsement of CourtAlert programming and support quality is also evidenced by the constant stream of clients devoting time and energy to discuss new ideas with CourtAlert. CourtAlert innovation often stems from this process. CourtAlert is considered the market leader in innovation and enhances its software and services at a rate quicker than any other vendor in this marketplace. This is possible due to two factors: (1) CourtAlert resources and (2) the Clients trust that their ideas will be understood and incorporated into solutions and innovations correctly and in a timely manner. User Training CourtAlert provides its clients with extensive user training. Optional Initial training is provided as soon as the client schedules it. Periodic refresher training on new enhancements is also readily available. CourtAlert also provides training for a client’s new employees as part of the client’s employee “on-boarding” process. Yael, who provides the training, has been doing so for several years, with the result that, the process has been fine-tuned so as to deliver valuable training in the shortest practicable period of time. Feedback with respect to training sessions at the NYC Law Department, as captured on the trainee evaluation forms, document a high degree of satisfaction with the training. Upon CAO request, CourtAlert will seek Law Department approval to release copies of feedback forms filled out by the users after each training session. CourtAlert will provide end-user training either remotely or in any CAO location and at the frequency requested by the CAO. CourtAlert Response to RFP 15 Customization The majority of the technical requirements necessary to fulfill the CCAO scope of work are already present in the existing CourtAlert CM/ECF Software. Any technical requirements that are not met with the current product are described and detail in the Technical Specifications section of this proposal. CourtAlert is committed to remain the best and, as such, continuously improves its services by adding new features and enhancing existing services. Methodology of Customization CourtAlert has generally responded by opening a dialogue to refine its understanding of the client’s request, and as soon as deemed feasible, begins programming its systems to fulfill the new requirements. CourtAlert uses a proven integrated method of customization to ensure quality and timely service. The steps in the time-proven method are included in the Approach to Implementation section below. Project control All customization and implementation efforts are document and tightly controlled with a project control software. CourtAlert uses JIRA software. More information regarding this software can be found at the site linked here: https://www.atlassian.com/software/jira. Each week, on a predetermined date of the week, there is a project status meeting. The structure and timing of these meetings are specified at the time of contract formation and typically take place at the client’s location. Project meetings are facilitated by a detailed review of the relevant JIRA reports. The CourtAlert team is well experienced in the effective structure of project meetings and project control to avoid any unnecessary delays and to allow the client a complete and current view of the project status. Use of Subcontractors CourtAlert does not intend to use any subcontractor for the proposed solution, and will obtain pre-approval if, in the future, any subcontractor will be employed in connection with any contract that may be awarded consequent to this proposal. Financial Stability CourtAlert is financially strong and stable. CourtAlert possesses the financial, material and personnel resources necessary to meet and exceed the requirements evident in the CAO CourtAlert Response to RFP 16 RFP. Moreover, because of the centrality of the CourtAlert systems in place at many well- established law firms and other entities as described in this proposal, our income stream remains stable and ongoing. In addition, because the State of New York has invested so heavily in the Office of Courts Administration computer system and because the CourtAlert System works so well in tandem with that system, CourtAlert will maintain a strong consistent income stream that CourtAlert derives from the current client base. CourtAlert has never lacked the financial, material or personnel resources necessary and required by any client in order to implement any system comparable to or larger than that envisioned by and for the CAO. CourtAlert is a privately held corporation with no outside investors and no debt. For the last 10 years CourtAlert has seen a double digit increase of sales over year over year. Company Establishment CourtAlert case management has been implemented since 2005. We have very satisfied customers and have never had a customer leave our case management system. What sets CourtAlert apart from the competition is the ability to support, innovate and further develop the products that are already existing. Whereas most companies make occasional changes, CourtAlert is very committed to ongoing development. The products are being constantly improved and we have a steadfast commitment to client satisfaction through our support team. Some of the features that distinguish CourtAlert • Automatic capture of Electronic Notices and PDFs from court filings • Outlook push of the events to the attorney calendar • Cloaking Cases Performance history CourtAlert has successfully set up the Case Management system and dozens of large law firms and organizations. Only one time in the past 20 years has a customer switch out of our system, and that was due to a firm merger. CourtAlert’s stellar commitment to support and client satisfaction has been proven time and time again. Please reach out to our clients for references. Location CourtAlert’s headquarters are in New York City, Midtown. All personnel are located in the United States. CourtAlert Response to RFP 17 Scope of Project CourtAlert will deliver a Case Management solution that will allow the City Attorney’ s Office to quickly and efficiently enter cases and activity and use the built-in functionality to improve its workflow The Software will meet and exceed your criteria. Setup The hosted CourtAlert solution is easy to set up and is used by many client to capture civil and criminal cases and related details. The system provides a built-in workflow for capturing new activity (“dockets”) and related events (“diaries”) in a highly configurable form that allows for the system to be configured to match your workflow. Configuration of system features Some of the primary goals of the system include: • Provide easily configurable alerts – each docket, which is a record for filing, hearing etc. is linked to one or more diaries, which are deadlines and other dates (or Sine Die). • Case team members, including attorneys and legal staff assigned to the case or CAO employees across other government agencies are notified though several alternatives including: • Email confirmation – Emails at the time of entry that include the PDF of the reference filing, a docket summary and all of the related deadlines • Email reminders – Emails sent on a set schedule days before a scheduled event or deadline. For example, 14,7,1 days before a reply is due. • Outlook events – Automatic synchronization of the deadlines with the attorney’s Outlook Calendar with beautifully formatted appointments • Attorney/staff tickler reports - A weekly summary email sent to every attorney with their upcoming deadlines. Deadlines are optimized for mobile view and a print-friendly PDF is attachment. • Web-based Inquiry module calendar displays and Dozens of different reports over the information in the system such as Calendar reports, workflow report, etc. Access to case information through the dedicated iOS and Android app. The App also allows for case document and status uploads. CourtAlert Response to RFP 18 Effective and efficient collaboration is achieved by numerous screen inquiries and reports (includes custom reports). CourtAlert’s invention of “reconciliation” allows any CAO employee to communicate effectively with the legal staff, including the submission of document, with review before it becomes a production docket entry. This is part of our US Patent 8,996,590. Executive oversight is achieved in the configurable Dashboard and the Inquiry Module, which allow for many ways to inquire and summarize the data. It is the beauty of one case, docket, and diary structure that allows reporting tools to efficiently work over different categories. The Software provides for system-wide full audit: recording of each field that was changed, by whom and when The Inquiry Module provides several user-friendly interfaces for searching and browsing. Consider the following inquiries that are easily answered through the system case lists, advanced searches and knowledge management tools: •Find recent Litigation cases before Judge Suttell •Find recent discrimination cases filed by a specific name •Find previous work product for Real-Estate transactions with the words “Sewer Lease” Powerful statistics are also published through dashboards that can easily display vital case work allocation, department work, forum and venue assignment, case stages and case disposition charts and drill downs. Reduction of data entry is achieved not only by effective keying technique, then also by the use of reconciliation, which allows input from court data, attorneys and staff at the court or otherwise “in the field”, from any authorized CAO employee and review before the data becomes the production docket. The main tools in this area are the Mobile App and the Document Upload Portal, which any authorized CAO employee (and external organizations if desired) can use. If the data is generated by outside organization, such as Electronic Filing emails from the Federal court system, it can be included in the Software with only three clicks using the CourtAlert “reconciliation”. CourtAlert Response to RFP 19 Additional integration with Accounting and Active Directory systems is included to ensure all legal staff are automatically created and access to the statewide directory to look up associated parties. Additionally, the system’s template tool generates letters and forms based on the case types and workflow phase. Mechanism for user friendly and efficient document retrieval is via the Inquiry Module, all linked to the cases, dockets, and diaries: there are dozens of interactive inquiries by names, reference numbers, classifications (unlimited number of classifications per case), staff member (unlimited team members per case, various ranks), dates and more. Numerous reports and custom report writer. All with links to the PDFs. The Software also provides for Knowledge Management system – sample of good legal work and legal precedent. Notes, the term PDF here is just an illustration, any type of computer file can be linked to the dockets: documents, video, audio, images, scans etc. All inquiry screens are optimized for smartphones, as a matter of fact most inquiries are done from smartphones. For example, an attorney receiving an alert advising a deadline can see the docket, the case, and the document from her phone Access to the data is tightly controlled. Users are grouped by “Role” and Role access is defined for every data element and module. Cases can also be “Walled off” with Exclusionary (certain people should not have access) or Inclusionary (only certain people could access) walls. Major Software Features Easy Entry through Reconciliation: Using CourtAlert patented technology, the Software automatically captures incoming notifications from various courts (see below) and brings them into the docketing system. The PDF is downloaded, and the docket text from the NEF is used to bootstrap your docket. This process is called “Reconciliation”. With as little as three clicks of the mouse, the user imports the docket text and the PDF to create a docket in the Software. Once the Docket and PDF are stored in the Software all authorized users can access that PDF from it and do not need to go back to PACER to retrieve the documents. This technology will save the OAG a lot of time currently spent to retrieve documents and more importantly, it will save the cost of retrieving documents from PACER. CourtAlert Case CourtAlert Response to RFP 20 Management clients have saved thousands of dollars off their PACER cost using this feature. Electronic Notifications are captured, and the PDFs are automatically download, from many courts, including: o New York State Electronically Filed Cases (“NYSCEF”) Notifications – NYSCEF continues to expand its coverage. It currently handles emails for all NYSCEF courts: NYS Supreme Court, Surrogates Court, all four Appellate divisions and the Court of Claims. o All PACER courts, every Federal District, Bankruptcy and Appeals and Specialty courts in the U.S. All notices from those cases will be captured by the docketing system for Reconciliation. o CourtAlert Case Tracking Notices – for NY Case Tracking all alerts are sent directly to the attorneys and processed by reconciliation. Note: CourtAlert NY Case tracking includes every NY Supreme County, AD1, AD2 and other jurisdiction requested in this RFP. All alerts from those cases may be added to the docketing system using the Reconciliation feature. o Many additional States and specialized courts (not listed in this RFI) are also supported. The above list shows how reconciliation works well with emails from the court. But the powerful workflow supported by “reconciliation” makes it possible to it automatically import documents from other sources. For example, dockets, documents, and adjournments can be entered on the CourtAlert Case Management Mobile App –used by attorneys at court on a tablet or iPad, and later “reconciled”. Documents can also be uploaded using the provided “Document Portal” that can be used by other state agencies. See Appendix A for a summary of the system overview. CourtAlert Response to RFP 21 Data Conversion The project scope include Data Migration from the CAO current Criminal Case solution, JustWare. CourtAlert has migrated data from dozens of different case management solutions including CompuLaw, ProLaw, Time Matter, E-Docket, MA-3000, Home-grown systems and more. If desired, all of the previously entered data will be migrated. CourtAlert data migrations typically include the capture of information from external sources, such as court data. If such information is accessible it can be used to bootstraps the CAO’s cases with party, judge, and other case details. Additionally, docket and upcoming events are typically imported. This integration allows the CAO to quickly get started on the new system and avoid time consuming data entry User Training CourtAlert provides its clients with extensive user training. Optional Initial training is provided as soon as the client schedules it. Periodic refresher training on new enhancements is also readily available. CourtAlert also provides training for a client’s new employees as part of the client’s employee “on-boarding” process. Yael, who provides the training, has been doing so for several years, with the result that, the process has been fine-tuned so as to deliver valuable training in the shortest practicable period of time. Feedback with respect to training sessions at the NYC Law Department, as captured on the trainee evaluation forms, document a high degree of satisfaction with the training. Upon CAO request, CourtAlert will seek Law Department approval to release copies of feedback forms filled out by the users after each training session. CourtAlert will provide end-user training either remotely or in any CAO location and at the frequency requested by the CAO. Testing Throughout the training and configuration process CourtAlert will provide documented updates on new features and tasks. The CAO team will test and sign off on the changes. If any issues are identified CourtAlert will correct for the next test release. Once the testing of a new version is signed off, CourtAlert will release the changes to production. CourtAlert Response to RFP 22 Go Live After several months of configuring the system to your workflow, testing of system functionality and the training of the users, the CAO will be ready for Go-Live. Typically this is achieved in two stages. Parallel Test Week – CourtAlert will run the data migration in the production environment, for a final week of testing. The goal is to ensure that the system works as expected and that the CAO personnel are fully trained and prepared. The CAO will double enter their entries in their cases in their legacy system and in CourtAlert. Reports will then be run out of both systems to ensure the accuracy. Go Live Rinse and repeat. The same data migration that was run in the prior week is re-run. This time the system is configured with emails enabled and the CAO cab use the system in production. General Requirements The following details the functionality broken down by the scope of services desired by the City Attorney. Forms Management – These services facilitate the creation, modification, and usage of electronic forms to capture case and name related information in a structured, consistent format. These services, assist with the development and management of electronic forms, including form field design and data entry validation to assist users with entering relevant data. The CourtAlert case management system is capable of storing templates which would be commonly used in the COA office. The user would upload all necessary forms and templates and store within the system for further or future use. The CourtAlert’s Case Management Software System is used records “case” information, documents and deadlines. Taking a vantage of entry by other departments and outside information CourtAlert has developed and patented a “reconciliation “module that excepts information from the outside and attaches it to a case for review by staff internal to the department. The reconciliation module works with notices that come from the court, or outside departments. Additionally, case information and new case details can be uploaded into the configurable portal. The poor allows for customizable forms to be accessed from CourtAlert Response to RFP 23 the outside and uploaded to the case management system to the correct case. Information is extracted from the forms and placed in the configured case fields. Reports Generation – services will include generating many types of reports including from case files, name files, and overall system data. Reports to include data reports, case status reports, discovery reports, calendar reports, and a variety of statistical, system, and performance reports. Report generation services support the organization and presentation of data into a useful, relevant, and interactive format, including stock reports as well as custom built reports. Vendor offers report building services as well as the ability of the City Attorney to create its own reports. • Inquiry Reports • Admin Reports • Emailed Reports • Audit Reports • Case Reports • Statistic Reports Case Jacket Report • Attorney Tickler Report • Firm Wide Calendar Report • Eight Day Calendar Report • Case Header Report • Case Summary Report • Ad-Hoc Report – this is an elaborate report-writer tool allowing users to define own reports • Audit Search Report • Calendar Report • Case Report • Daily Work Report • Record File Index Report • Work Report • Case Notes Report • Case Classification Report • Calendar Report by Department • Custom Reports (Excel based reports) • Cases without any Rep CourtAlert Response to RFP 24 • Cases without any Rep or Staff • Cases without any Rep, but has Staff in Case • Cases with no Branch information • Courts and Counties with no abbreviation code • Classification Types in system • Cases without any classification code • Cases without any docket activity within last year • All Types in the system • Open cases without any Judge • Future Diaries on Weekend • Open cases without future diaries • Federal Notices Ignored during Last One Week • Knowledge Management and Case Classifications Search – These services include the ability for users to search and browse through case, people, and event data to find all records that match the search criteria. Examples include data entered by a certain attorney or cases that were decided in a particular jurisdiction, or records that contain a particular term. The CourtAlert case manager contains a wealth of information that can be used for looking up information within a case and to find cases with relevant information. The CourtAlert case system includes a quick search which allows you to search for a term anywhere in the system. For example, search for Boeing and you will find cases with a judge Boeing, Boeing County and cases involving Boeing corporation. The system also includes an advanced search. The advanced search allows you to search by specific fields. For example you can search for any for cases with any party. Cases by any judge. Cases of a particular case type. Cases by classification, the tags associated with the case. Search for cases by Entry date. Search for cases by documents including the ability to search within the document text with certain document management systems are integrated. Within a case it is you can have one or more docket word document and trees associated with it. This is Tim Leslie to quickly filter and sort and filter these documents in the inquiry screens. CourtAlert Response to RFP 25 Security and Privacy – These services define the capabilities needed to support effective measures to protect and safeguard information and systems from inappropriate or unauthorized use, alteration, loss, or destruction and include, but are not limited to: ensure continuous observation of security rules and regulations; ensure appropriate level of protection for case related information and data; ensure data is protected against unauthorized modification, use, destruction, or disclosure; and assure confidentiality, integrity, and availability. The LCMS must be CJIS compliant and guarantee security of all data including confidential criminal justice information. Coral case management system has been available on the cloud since version 11. This system runs on client dedicated infrastructure on Microsoft Azure, which is fed ramp certified. CourtAlert will provides detailed documentation on the Application firewall configuration and other security configurations in a Security Audit. It is notable that CourtAlert runs on PAAS services on Azure and does not spin up its own servers this allows CourtAlert to rely on the security within Azure to provide a high level of security guarantee to our clients. The system is protected with the Azure web application firewalls and is authenticated using your own identity providers. Most clients integrate with Microsoft azure's Active Directory for authentication in the system with Azure’s active directory integration, the City Attorney can ensure that only active permissioned users are able to use the system. The next level of security is within the system. Every case is assigned a case office and the system can be configured so members only members of their office, and certain privileged master users can access case details. The security is achieved on the lowest levels of the database access to ensure the walls are obeyed throughout the system. After that, the next level of security is set manually with any case. The system allows for exclusionary and inclusionary walls to be assigned to any case. These are sometimes called case screens or case cloaking. An inclusionary wall is one that says only the case team can work on the case. No one else, even within that department/agency, can access the details. An exclusionary wall allows you to execute a particular staff member from accessing that case at all. Even if that staff member is in the same agency. Within a case, certain documents can be marked as confidential and certain events can be marked as private. This allows only the case team to see those details and leaving the rest of the documents readable by the rest of the agency. CourtAlert Response to RFP 26 Related to security is the concept of logging and audit. The system maintains all logs for at least 90 days. Logs are stored centrally on the client dedicated environment. Additionally, the system has a low-level audit recording every change made within the system that is available for review in case a problem is detected. Space finally, the most common form of audit is the business logic level audit. Docket entries and cases are noted with the creating and last editing user. this information is displayed on the case, document and calendar screens. Case Data Management – Case file data management services determine what data elements should be captured and how data should be used and stored. These services facilitate the storage, processing, exchange and general administration of case related data in the case file. The case file is utilized to provide management oversight to prosecution, civil litigation and general legal services, e.g., management of case related resources, assignments, authorizations and status changes, including metrics and accomplishments. One of the advantages of the cooler case management system is that the case header screens. These screens allow for all cases to have common fields, such as the case name, the case number, the client and matter number that this is associated with and several other fields that are shared across all case types. Additionally, staff assignments, party and participant Simons, and note fields are common across all case types. Additionally every case type can have its own configurable screens of case type specific fields, for example, a litigation case would want and record the forum, venue, court case number and judge, perhaps additional judges in the case. A contractor would want to record the contract start and stop dates answer the stages for the contractor review. A department of child Youth Services case would want to record the list of all of the various cases. The admin program includes a module for editing the case type layouts. Each case type can be associated with preferred party types, classifications, stages and other configurable dropdowns. Additionally, the layout editor allows you to add any number of fields and the location and type of those fields for each case type. This powerful tool allows court alert to configure and test dozens of case types within weeks at the state of Rhode Island. CourtAlert Response to RFP 27 Paperless environment - these services must provide and support a paperless office solution. The CourtAlert case management system includes several modules that help in office become paperless. Documents are stored as PDFs related to cases. For the Suffolk City Attorney’s office, the CourtAlert team has developed a main module that allows the front office to scan relevant mail and associate that as if it was an electronic notice coming from the outside. The distribution of the electronic notice can follow the physical paper or can be transmitted instead of the actual document. The system includes many tools to download specific or all documents within a case and to access the case information through its online inquiry. Additionally emailed reports notify case teams about deadlines and case information when appropriate. For example, Calendar entries such as deadlines and hearing dates are pushed out to the attorney’s calendars and weekly attorney calendar reports are emailed out to the attorneys. Client Management – The need for services to support the management of day-to-day client relationships and interactions. Clients include other County and City departments such as the police department, county district and justice courts, municipal court and the finance department. The system does a great job in communicating with your clients within the office and outside the office. The system can include any number of staff members and or participants that are internal or external to the City Attorney. Participants can be set up to receive notifications about new documents that are uploaded. The save and notify quote feature allows the City Attorney personnel to notify those select members, internal or external to the agency, about the relevant documents and events that have been worked on. Similarly, upcoming events and deadlines also includes the ability to search the City Attorney's Active Directory for personnel names as an easy look up method in the case participants screen. Calendaring – Calendaring for multiple people, including cross-access for all department members, multiple cases, schedule entries for upcoming court appearances, filing CourtAlert Response to RFP 28 deadlines, meetings, and hearings for multiple courts, with customized views and printing and tickle events. Calendaring is the number one most important feature that reduces the risk of missing a deadline or court appearance. Calendaring can be achieved in multiple forms and is typically done by relating a calendar entry with the activity that triggered it. For example, a deadline to reply to a complaint is calendared alongside the complaint; The date of a hearing is calendared alongside the Scheduling Order; the depositions is often calendared alongside the email scheduling it. Calendaring alongside an activity record allows the attorney to see the triggering source of information alongside of the deadline in Outlook and other inquiry displays. The system also includes a method to add “rules” based on your practice or court rules. These are used to automatically calculate dates on your applicable cases. For example, one can automatically calculate the last day to respond to a complaint or deadlines related to a trial date. This is commonly used for court deadlines and firm-specific internal practices. Another useful calendaring tool is the “adjourn/continue” feature. This allows users to adjourn events easily so that the old deadlines get removed from the calendar and the new deadlines get added in one shot. The Adjournments including an Adjournment trail that show the history of the event. This presents text such as “Trial on 9/30. Last adjourned from 9/15” – a useful indicator to the attorneys on the history of the event. Once an event is calendar there are multiple notifications related to that deadline. First, at the time of entry, the user entering the event will typically send a “Save and Notify” email notification to the entire case team (all of the attorneys and stuff assigned to the case ). This email lists all of the deadlines that were entered/computed and the related activity. For example, a typical workflow would be if a motion was served electronically. First, the “reconciliation” module will pick up that ECF notice and download the document. Then, a secretary or assistant would see that the notice in the software, record the activity in two clicks, and calculate related deadlines, often using the automatic rules. Once this entry is complete they would “save and notify” the underlying motion document and all of the related events and deadlines to the case team. Any of the attorneys assigned to the case can reply back with an update or correction – making this a very effective communication and confirmation tool. The system also automatically pushes out outlook events directly onto the attorneys calendars. This is done without invites so there is no chance of them failing to accept the CourtAlert Response to RFP 29 message. These events include hyperlinks to the case snapshot and the underlying documents that triggered this event. Finally, as the day of the event approaches, optional reminder emails and attorney calendar reports, sometimes called attorney tickler reports, are sent out to each attorney for their upcoming deadlines. Performance Measurement – These services are concerned with the development, refinement, and usage of performance metrics. The system includes a series of reports that report on the performance of the system. These reports include usage statistics that are often helpful in determining workload across different case types and departments. This also help identify gaps in performance. Reports can be generated ad-hoc or scheduled to be emailed periodically. Additionally, interactive reports are available in the inquiry module And the dashboards. Business Rule Management and Automation – Business rules and workflows are reflected in locally determined practices or procedures that govern the way that routine business activities are performed and automated. There are several key features that help clients with automation and rules management. The first is in used in calendaring – the system allows administrator is to create predefined “rules” which are triggered when certain activity takes place. For example, one can enter in a custom rule for court related deadlines or for your own internal policy. Additionally, clients can apply checklists for documents – prompting for documents that should be entered for a given case type. This feature allows users to ensure that all the required documents for a given case are completed. Also, the word template (“mail merge”) feature in the system allows users to generate a Word document merged in with the selected case data. These documents can either be edited further or automatically PDF for emailing. Records Management – Ability to archive and retrieve closed files, and associated data and documents, in an easy and efficient manner. The case management system includes a read only inquiry module designed to easily access all cases, open or closed, and download the related documents. Documents can either be opened one at a time or mass downloaded into a ”binder”. CourtAlert Response to RFP 30 Additionally, the system includes a feature to physically archive cases. A user can use the archive module too assign a box number to a case. Then, when the physical box is full, generate a packing slip for all the cases in that box. When the packing slip is returned with a permanent box location based that information can be updated into the system as well to record the permanent box details. Document Management – This service will provide the ability to generate, modify, store, retrieve, and archive case and name specific documents within the proposed application and search the same. The system allows users (provided they are not cloaked from the case) the ability to store, generate, modify and access case documents. In our system we call this docketing. A docket entry can have one or more documents, typically including exhibits in the same entry as the underlying document. Optionally documents can be uploaded to a secondary location where they can be accessed through county wide or statewide portals or global search tools. For example, clients with iManage, netdocuments or another enterprise Documents Management system may elect to have the documents copied there as well. Discovery – Ability to record receipt and processing of discovery requests electronically, including Bates’s stamping, redacting, and indexing features to expedite process. Ability to record and produce all discovery electronically through LCMS. Preferably a separate discovery management section of LCMS. As the system includes most of the case details, it is often used to produce discovery information. Discovery requests are generally recorded as docket entries as well as discovery deadlines being calendared. At this time the system does not natively redact or bates stamp the produced documents. Clients use their own tools such as Adobe or other PDF editors for these functions. Victim services – this service will provide a victim services management section. Preferred features include data collection for grant reporting and text messaging capabilities. Victims are entered as Parties to a case and include detailed demographic information. Party reporting on the collected date is provided CourtAlert Response to RFP 31 This is to meet with many classification features that allow users to classify document types and deadlines that can be used for specific purposes such as grant reporting. Additionally, fee management such as court fees investigation fees etc. can be recorded alongside activity entries. The fee reporting can also be used for grant reporting purposes. Legacy Data – this service will import legacy data in a readable, usable format. Typically, clients move to the CourtAlert case management system from an existing system. As part of the project we plan and executes a data migration process aiming to import 100% of the data for the timeframe you select. Often legacy data can be a valuable resource for knowledge management and historical searches for activity and experience. Customization – This service must have the ability to be customized in order to fully support each area of practice within the department - Prosecution, Civil Litigation and General Legal. We believe that court alert already supports most of the requirements needed by the City Attorney with the built in screens and functionality. The system is used by many large organization and firms with diverse requests. Often the need arises for additional fields for specific case types. Fields, picklists and layouts can be added with simple configurations and do not require a new version of the system. Additional software customization is encouraged! Features that do not exist and would be suited to match your workflow can be easily implemented for your system and be maintained for future upgrades. Such requests are planned though the project management meetings, tested in a test environment and when approved, made available in the Production environment Data Query – the services will be written in SQL language and allow the City Attorney to query its data as needed. The case management system Runs on Microsoft SQL Server in the back end. CourtAlert commonly creates data extracts and provides web services to access information within the system. Clients do not often request direct database access to the services when they are in the cloud. Often CourtAlert will create a View of the data which can be provided via web service. CourtAlert Response to RFP 32 System Integrations - This service includes the ability to build integrations between proposed system and other County and City systems hosting relevant case and justice data. System integrations include New World LERMS and Corrections used by the police department as well as the FullCourt Enterprise and efiling system used by the Bozeman county courts, municipal courts and administered by the Montana Judicial Branch. The case management system includes a module that automatically captures emails from various sources including federal PACER and many state filing systems such as Tyler hosts and the file and serve express etc. This module can easily be enhanced with new parsers to capture notifications coming from other sources such as the Montana judiciary branch and Bozeman County courts. Compatibility – This service must have the ability to interface with other software currently used by the CAO, including but not limited to all Microsoft Office products and AdobePro. LexisNexis research tools preferred but not required. The system integrates nicely with these client side editors, including Microsoft Office and Adobe. All modern browsers are supported. Additionally, the system integrates with Microsoft Outlook by writing events directly to the attorney calendars using the Microsoft Exchange Server. Platform - cloud based LCMS hosted by vendor. Vendor will maintain all City Attorney data on servers in the United States subject to US law. The City Attorney owns all data and vendor shall surrender that data to the City Attorney at the end of any contractual agreement. Yes. The court lowercase management system will be deployed on a client dedicated Microsoft Azure PAAS services. These services are secured with a dedicated resource group, virtual network and dedicated encryption keys. All the information will be maintained on The United States and all access outside of the United states will be blocked by the Web Application Firewall. We understand that the City Attorney owns all data and court alert will surrender and make easily available the data to the City Attorney at the end of the contract and anytime before. CourtAlert Response to RFP 33 Cloud Services Requirements 1. Service levels: What level of service should we expect? What is the City’s recourse for excessive downtime? Refund of percentage of monthly fee? CourtAlert provides Case Management system hosting for many client include the State of Rhode Island and many top law firms in the United States. These organizations depend on the system for their daily workflow and communication. As a hosted solution CourtAlert guarantees 99.9% uptime at minimum. The system is deployed on client-dedicated resources on Microsoft Azure and is set up with redundancy and backups to achieve a high availability. Prorated monthly support and maintenance fees are refunded for downtime beyond the guarantee. To date no client has experienced significant downtime as to even request such a credit. See Appendix G - Service Level Agreement for details on the support and hosted maintenance agreement 2. Data ownership: Who owns the data we provide and what can be done with the data? The City Attorney owns all the data. All data is kept confidential and can be used by the CAO for any purpose. CourtAlert provides access to database backups as well as live access to the data through APIs. Several organization use the data hosted within the system, such as case party information for integration with other system. For example the Case Party details has been used for integration with Ethical Wall / Conflict Search system. 3. Data security: How secure is our data and how is it being kept secure? Data governance CourtAlert has adopted a Data Governance Policy on 7/15/2018 that addresses the broad goals of data governance within the Company. This includes Case Management/ Client Protected Data information hosted by CourtAlert, where it addresses data isolation. The Case Management System, on-premise or in the cloud often contains public available information as well as information that is confidential. Data access CourtAlert Response to RFP 34 throughout the system is controlled and audited on multiple layers. On the system level, users must be authenticated to access any part of the system. Authenticated users are permissioned to modules (features), that is the role-based security will ensure that only permissioned users can access functionality that they might possibly need. Next, on the Application level, Case level "walls" lock down cases with either inclusionary (only the case team) or exclusionary policies. No individual who is not permissioned to a case will know the case exists. In addition, the system provides auditing on an application level. Every change created by any user is recorded. Easy to access timestamps and "Last Modified By" fields are recorded on every entry. Firewalls CourtAlert uses Azure Application Gateway with Web Application Firewall (WAF). More information can be found at: https://docs.microsoft.com/en-us/azure/application- gateway/waf-overview, included as Appendix 2 - Web Application Firewall. In addition, the log is integrated with Azure Monitor to track WAF alerts and easily monitor trends. CourtAlert Access to Data CourtAlert employs PIM, Privileged Access Management, requiring a manager’s approval before CourtAlert Support or Developer can access any client-data. Two-factor authentication used for administrative control CourtAlert follows the “Baseline Policy” in Azure in “Baseline policy: Require MFA for admins” Physical and electronic access to the log files Logs and Log Analytics are stored in the isolated Azure Resource group requiring the same privileged and audited access as other secure data a. If this is a multi-tenant environment on the same hardware how is our data kept separate and secure from other customers, including any PII (Personally Identifiable Information) that may be gathered? The system is deployed as a single-tenant solution. CourtAlert employs a virtual network and dedicated Resource Group for each client separately. No communication is possible CourtAlert Response to RFP 35 across clients. This is the recommended practice to achieve “ISO 27001 App Service Environment/SQL Database workload” b. If PII is gathered, is it encrypted in transit and at rest? Yes. All data is encrypted with client-dedicated keys and is encrypted at rest (both SQL and File storage) and in transit (HTTPS and SQL communication use TLS 1.2) c. If credit card transactions are occurring is your system fully PCI compliant? No Credit Card information is stored. 4. Data integrity: What do you do as a vendor to ensure our data maintains its integrity? SOC2 A recent Audit report can be found under the Microsoft Azure Service Trust Portal: Microsoft Azure & Azure Government SOC 2 Type II Report (2018-1-1 to 2018-12-31). Yes. For brevity the entire report was not printed in the physical copy. Deployment - The system is deployed using only use Azure PaaS. Microsoft Azure configures and deploys all servers used. Hardened Servers - A recent Audit report can be found under the Microsoft Azure Service Trust Portal: Microsoft Azure & Azure Government SOC 2 Type II Report (2018-1- 1 to 2018-12-31). In the latest Audit from February 2019 Control CM-8 is identified with: The Technical Security Services team develops security configuration standards for systems in the physical environment that are consistent with industry-accepted hardening standards. These configurations are documented in system baselines and are reviewed annually and relevant configuration changes are communicated to impacted teams (e.g., IPAK team). • Inquired of the Cloud and Enterprise Security team that security configuration standards for systems in the datacenters’ environment are based on industry-accepted hardening standards and configurations are documented in system baselines and are reviewed annually. Relevant configuration changes are communicated to impacted teams. • Inspected security configuration standards and technical baseline published in a central location and approvals related to an annual review and ascertained that technical baselines were consistent with the industry standard, approved, and the results were communicated to impacted teams. CourtAlert Response to RFP 36 • Selected a sample of servers and inspected their configuration to ascertain that documented security configuration standards and technical baseline were implemented. How current would the data be (RPO) and what is the restoration time (RTO) of the data that was restored? CourtAlert employs “geo-redundant database backups”. Geo- restore uses a geo-redundant backup as its source and can be used to recover a database even if the database or datacenter is inaccessible due to an outage. Geo-restore from geo-replicated backups RTO: 12 h RPO: 1 h Additional options can be found at https://docs.microsoft.com/en-us/azure/sql- database/sql-database-business-continuity#recover-a-database-to-the-existing-server Testing and Rollback Testing is done after changes are made to servers. Every version of the deployed application is tested in the test environment. After User acceptance the application is deployed to production. A backup is taken immediately before the update for failsafe restore. If there is a problem as a result from installing a patch backup can be used if a fail forward option is not feasible. CourtAlert checks all code for viruses after every build of the software. 5. We require data centers to be located in the United States: What country will our data be located in? United States, Microsoft Azure Public Cloud. Typically resources are deployed in the nearest Azure data center. CourtAlert will likely host the data using the West Central US region which is located in Wyoming. 6. Responding to legal demands to disclose data: What is your process when someone subpoenas or requests our data from you as a vendor? On a legal demand for information CourtAlert will notify the client of such a demand and allow the client to seek remedies for such a request before CourtAlert complies with a response. CourtAlert Response to RFP 37 7. Reporting: What is your protocol for data breaches? The CourtAlert Incident Response Plan was Last Reviewed 10/15/2020. It details the overall plan for responding to information security incidents at CourtAlert. It defines the roles and responsibilities of participants, characterization of incidents, and reporting requirements. The goal of the Incident Response Plan is to detect and react to computer security incidents, determine their scope and risk, respond appropriately to the incident, communicate the results and risk to all stakeholders, and reduce the likelihood of the incident from reoccurring. No security breaches have been identified in the last 24 months. 7. Disaster recovery: What protections/ protocols do you have in place to mitigate disasters? High Availability CourtAlert hosts the services using dedicated Microsoft Azure Resources in zone redundant configurations. Details can be found at Exhibit B - Appendix 3 - High Availability Zone Redundant Backups SQL Database uses SQL Server technology to create full backups every week, differential backups every 12 hours, and transaction log backups every 5-10 minutes. The backups are handled by Microsoft Azure with details in Exhibit B - Appendix 36 - SQL Backup CourtAlert employs “geo-redundant database backups”. Geo-restore uses a geo-redundant backup as its source and can be used to recover a database even if the database or datacenter is inaccessible due to an outage. Geo-restore from geo-replicated backups RTO: 12 h RPO: 1 h Additional options can be found at https://docs.microsoft.com/en-us/azure/sql- database/sql-database-business-continuity#recover-a-database-to-the-existing-server CourtAlert Response to RFP 38 8. Business continuity: If you decide to bring your business to an end what happens to our data? The City Attorney owns all their data. Data backups are provided monthly and on demand. Confidentiality of information survives contract termination. CourtAlert will dispose of all City Attorney Data and backups after contract termination. 9. Termination rights and consequences: What is your termination policy both for you as a vendor and us as a customer? Our typical agreement allows customer to cancel with 90 day notice. CourtAlert’s success is predicated on the success of our clients. No client has left CourtAlert for another vendor. Customer retains access to all their data. 10. Exit: If we exit our relationship what format can we get our data in and what assistance will you give us in transferring our data to us in a usable format? The customer data is stored on sql server and blob storage. CourtAlert would provide the data as a SQL backup and direct access to the blob storage. SQL data can be restored to your own SQL Server or one hosted in the cloud. Blob storage is typically exported as an XML file List and individual files. Blob Storage can be copied directly using AZCOPY, a utility provided by Microsoft. At customer expense, drives can be shipped with the files. More information can be found at https://docs.microsoft.com/en-us/azure/import- export/storage-import-export-data-from-blobs?tabs=azure-portal. CourtAlert Response to RFP 39 Related Experience with Projects Similar to the Scope of Services Most recently, The CourtAlert Case Management system was implemented at the State of Rhode Island, Executive Branch. The state uses across 29 Agencies and covers both Litigation and non-Litigation case types. The breadth of case types and the scale of adoption demonstrate the power of the CourtAlert system and implementation abilities. The project was split up to 4 phases: Phase 1 – Configure the Base System Phase 2 – Litigation workflow (out of the box) setup for 5 Agencies. Phase 3 – Other Case Types for the same 5 Agencies, including Freedom of Information request, Contracts, Real Estate, Probate, Collections, Permitting and more. Phase 4 – Implementation and Training at the remaining 20+ Agencies. Noteworthy, CourtAlert has performed Eight (8) different data migrations from various systems as part of the consolidation that took place in this project. For example, Time Matters, Informix and custom Access Databases. The project was implemented during September 2020-April 2021 (7 Months!) Another project with a scope similar to this proposal was the implantation of the CourtAlert Case Management solution at the Suffolk County, NY City Attorney Office. Suffolk County has a population of 3 million and the City Attorney uses the system for their Litigation (Civil Court, Family Court) and Non-Litigation (Contracts, Leases, FOIL, Subpoena and other) case types. Customer References CourtAlert has not yet had the opportunity to do a JustWare conversion however we have significant experience in dealing with large-scale migrations from Compulaw, E-docket, MA- 3000, JuraLaw, BEC, and in- house grown solutions. Once we get to know your database, we are sure that a conversion from JustWare conversion should be no problem at all. A detailed description of three similar past projects or products provided CourtAlert Response to RFP 40 The law department support in both organizations is diversified and sophisticated and the Software offers both the configurations for each group as well as uniformity of data which allow easy transfer within the organization and executives’ controls. Each of the COA categories, and future categories, may have unique case classifications, screen format, workflow, automatic letter generating, inquiries etc. while still providing one coherent executive “picture”. The Case Management Software has been installed, implemented and through training provided since 2005. The installation are at large organizations with diversified needs. CourtAlert project management methods ensure successful implementation. CourtAlert has implemented its case management system at the state of Rhode Island, the department of administration, across 26 agencies in a very short time frame. CourtAlert was awarded the RFP in July 2020. By September 2020 the system was operational and used for litigation in the department of administration. Within three months it was operational for Litigation and 12 different case types for five agencies additional agencies. By March 2021 it was operational for all 26 agencies under the department of administration. CourtAlert was awarded this contract not just for the software’s capabilities but also our ability to perform the work quickly and at grade scale. The CourtAlert’s Case Management Software System provides a workflow of recording cases participants case details documents, history and deadlines in a very clear and organized fashion. The ability to quickly configure new place types allowed the state of Rhode Island Department of administration to set up the infrastructure for a single case type first and quickly adopt additional case types including caseloads for contracts in the Department of Child services information act cases. Another highlighted feature was CourtAlert’s ability to automatically capture notices from the Rhode Island state court and from the Rhode Island e-filing service, and the Tyler host system.. Documents were automatically downloaded and presented to the case teams. To illustrate the breadth of case types that have already been implemented we will list the agencies are using the CourtAlert Case Management system at the State of Rhode Island: Governor’s Office, Department of Administration - Division of Legal Services, Department of Business Regulation, Department of Corrections, Emergency Management Agency, Department of Environmental Management, Executive Office of Health and Human Services, BHDDH - Department of Behavioral Healthcare, Developmental Disabilities and Hospitals (BHDDH), DCYF - Department of Children, Youth and Families, DOH - Department of Health, DHS - Department of Human Services, DHS -Office of Child Support Services, Office of the Health Insurance Commission, Public Utilities Commission, Public Utilities Division, Department of Revenue, Division of Motor Vehicles, Lottery and Taxation. The following Case Types have been configured with dedicated workflows, layouts and picklists. APA HEARINGS - HEARING OFFICER DCYF_CHILD WELFARE PETITION DOH LITIGATION CourtAlert Response to RFP 41 EOHHS PROBATE DHS LITIGATION BHDDH_FORENSIC-MENTAL HEALTH EOHHS BENEFITS APPEALS BHDDH FORENSIC & MENTAL HEALTH APA -ATTORNEY APRA (FOIL) / Freedom of Information RATE SETTING REAL ESTATE LEASING REAL ESTATE P&S PERMITTING LICENSING CONTRACTS ARBITRATION (LABOR) INVESTIGATIONS- INTERNAL ARBITRATION (NON LABOR) COLLECTIONS INVESTIGATIONS -EXTERNAL APA HEARINGS - ATTORNEY LEGISLATION SUBPOENA POLICY CourtAlert Response to RFP 42 REGULATIONS Suffolk City Attorney, NY In 2014 CourtAlert was awarded the contract for implementing the case management system at the Suffolk City Attorney’s office. Suffolk County population is around 1.5 million, 10 times that of Bozeman County. Despite being bigger, the requirements are very similar. The City Attorney is responsible for several divisions including the municipal law department that handles contracts and legal review and legislation. The tours and litigation divisions and the department of child youth services in each category have their own unique requirements for representing cases and their workflow. Some of the system highlights used by the City Attorney include: The ability to scan physical mail and directed to the appropriate person. The ability to create forms used by outside agencies to interact and provide documents relevant to cases within the system. The ability to record case files, create labels, and record archive locations and generate packing slips for archive boxes. Akin Gump In 2018 CourtAlert provided our case management system to the law firm Akin Gump. Akin Gumpis a nationwide law firm with offices across many different states. The CourtAlert’s Case Management Software System is able a to provide the firm with the ability to capture electronic filing notices from dozens of court systems nationwide and the ability to record deadlines for cases across their state and federal jurisdictions. The system also has the ability to push outlook events directly to the attorneys Outlook calendars, for managers to review, and for attorneys to provide feedback on event entry - overall reducing the risk of an attorney missing a deadline and increasing the communicate throughout the firm. The dates the services/products were provided ***CONFIDENTIAL*** The following is a list of clients and the dates the solution was provided. CourtAlert Response to RFP 43 Account Name Case Management Start Date Faegre Drinker 6/18/2021 McGuireWoods 6/4/2021 Ogletree Deakins 5/25/2021 Fennemore Craig 12/22/2020 Fowler White 10/7/2020 Weil, Gotshal & Manges LLP 7/30/2020 State of Rhode Island 7/24/2020 Keller Lenkner 4/6/2020 Benesch Friedlander 9/27/2019 Carter, Ledyard & Milburn 3/14/2019 Bernstein Litowitz Berger & Grossmann LLP 2/28/2019 Rosenberg & Estis 1/31/2019 Harris Beach LLP 12/31/2018 Allen & Overy 10/15/2018 Cravath, Swaine & Moore LLP 9/4/2018 Lane Powell 9/3/2018 Gibson Dunn & Crutcher LLP 8/9/2018 Akin, Gump, Strauss, Hauer & Feld LLP 7/9/2018 Michael, Best, & Friedenrich 3/6/2018 CourtAlert Response to RFP 44 WilmerHale, LLP 3/5/2018 Friedman Kaplan Seiler & Adelman LLP 11/30/2017 Mound Cotton & Wollan & Greengrass 6/5/2017 Cahill Gordon & Reindel 2/28/2017 Katten Muchin Rosenman LLP 12/6/2016 Fried, Frank, Harris, Shiver & Jacobson LLP 9/29/2016 Kelley, Drye & Warren LLP 5/2/2016 Paul Weiss Rifkind Wharton & Garrison LLP 1/21/2016 Shearman & Sterling, LLP 11/9/2015 Cohen & Gresser LLP 1/20/2015 Suffolk County Department of Law 3/17/2014 Debevoise & Plimpton 2/11/2014 Willkie Farr & Gallagher LLP 3/15/2010 Davis Polk & Wardwell LLP 1/15/2009 Mintz Levin Cohn Ferris Glovsky & Poper. 3/19/2008 Wachtell, Lipton, Rosen & Katz 12/6/2007 Kramer Levin Naftalis & Frankel LLP 12/5/2006 Patterson, Belknap, Webb & Tyler, LLP 11/13/2006 Ropes & Gray LLP 6/28/2006 Cadwalader, Wickersham & Taft LLP 1/2/2006 Greenberg Traurig LLP 10/10/2005 CourtAlert Response to RFP 45 Moses & Singer LLP 1/20/2005 Cleary Gottlieb Steen & Hamilton LLP 1/6/2005 The clients for whom the services were provided. Contact information for the client The following is a partial client list with contact information. State of Rhode Island Jennifer S. Sternick Chief of Legal Services (Litigation) (401)222-8339 Jennifer.Sternick@doa.ri.gov Suffolk County Department of Law Dennis M. Cohen, City Attorney (631) 853-5675 dennis.brown@suffolkcountyny.gov Davis Polk & Wardwell LLP Jennifer Candelario Firmwide Docketing Manager (212) 450-4455 jennifer.candelario@davispolk.com Katten Muchin Rosenman LLP Barry Adler National Docket Manager (212) 940-6614 barry.adler@kattenlaw.com Akin Gump Strauss Hauer & Feld LLP Kelly Owen-Diaz Docketing Manager (212) 872-8051 kowen@akingump.com CourtAlert Response to RFP 46 Cravath, Swaine & Moore LLP Robert Novick Managing Attorney (212) 474-1209 rnovick@cravath.com New York City Law Department (Case Tracking) Daniel S. Margetanski Senior Counsel – Deputy Director of User Services (212) 356-4095 dmargeta@law.nyc.gov The Law Department of Suffolk County, NY requirements are diversified in a manner similar to the CAO; the system provides many different and varying departments or groups. The law firms listed here are huge, most have more than $1 Billion in annual revenue. One main criterion which attracts client to large law firms is the firm ability to handle all aspects of the client’s needs. As a result, this firms are very diversified. The Software is used to docket and report different and varying categories. More clients are listed in the enclosed list, and the CAO is more than invited to contact each of them. None of the clients were told that the CAO may contact them. Why have we chosen these references? (1) The State of Rhode Island demonstrates the potential growth of the system for the County’s needs, and demonstrates CourtAlert’s ability to implement a solution quickly, with customizations and data migrations. (2) The Law Department of Suffolk County, NY requirements are very similar to the City, the system provides many different and varying departments or groups, some of which have very same names as the City categories (3) The law firms listed here are huge, most have more than $1 Billion in annual revenue. One main criterion which attracts client to large law firms is the firm ability to handle all aspects of the client’s needs. As a result, this firms are very diversified. The Software is used to docket and report different and varying categories (4) The City of New York Law Department, Con Edison, the Port Authority of NY and NJ are all many years clients of CourtAlert services and cannot use the Software as they have already invested millions of taxpayer dollars in customizing their legacy system. It is not politically feasible for them to move to a better case management system (they sure say they wish they could). CourtAlert Response to RFP 47 Related Appendixes: Error! Reference source not found. . Some clients do not wish their name used as the view the Software as a business and strategic tool over their competitors. Error! Reference source not found.. The contract was awarded to CourtAlert and the system is being implemented as these lines are written. CourtAlert Response to RFP 48 Proposed Implementation Schedule Work PlanError! Reference source not found. to this proposal is a detailed typical implementation plan. One or two of the case categories or affected departments will be worked on concurrently by the priority assigned by the CAO. To facilitate this support level, the client is asked to agree to: (a) Every email requesting support be copied to Support@CourtAlert.com. This allows for cross training. In addition, CourtAlert executives review each and every email to Support and the responses (b) Weekly on sight or remote meetings at a predefined schedule Approach to All Phases:Error! Reference source not found., the typical implementation plan addresses the steps required to implement the system. Major items to discuss at the Kickoff Meeting and shortly thereafter: Environment and IT support, CourtAlert is offering the solution as a Cloud hosted product. • The priority of Case Categories / Departments for implementations • System wide integration features (Active Directory, HR, Accounting, and other integration that affect all categories) Phase 1 – Environment Setup CourtAlert and the CAO will set up the requisite hardware and data access. CourtAlert offers both a cloud option and an on-premise option. For this RFP the cloud solution is being offered - CourtAlert will set up the appropriate resources on Microsoft Azure. CAO will provide required data feeds. AUthntication will be configured through the CAO Identity Provider (IdP). Phase 2 – A Plan for implementation Over the next several weeks the CourtAlert and the CAO team will develop a detailed plan for implementation. CourtAlert Response to RFP 49 Identify system-wide features and integrations need to be in place before any Case Category / Department Specific implementation. • Develop a best practice for general implementation • Overall structure and communication method • Project participants • Develop a structure for the upcoming Case Category / Department – implementation • Decide on priority, which function first (typically the larger department) Phase 3a – System wide feature Implementation This phase implements features such as Outlook Synchronization, Court Email Mailboxes, Reporting, Deployment methodology with the help of IT and the CAO Project team. For each integration feature: • Identify the SMEs for that feature • Identify the goals and tasks for implementation • Development -> Release -> Testing -> Approval Phase 3b – Case Category Implementation For each Case Category / Department, the CourtAlert and the COA PM will: 1) Identify the SMEs for that Category / Department, decide project participants, 2) Meet to discuss the general workflow of that department and to show the current capabilities of the system (typically 2 hours with the SME). 3) Study of the group requests and what changes if any are required. 4) (CourtAlert) Estimation of effort - CourtAlert PM will propose action items and customizations specific for the department and the COA PM will obtain approval 5) (COA) Approval of effort 6) (CourtAlert) Programming and installation 7) (CourtAlert / COA) Initial Training 8) (COA) User acceptance 9) (CourtAlert) Documentation delivery – CourtAlert 10) There may be more than one round of Development -> Release -> Training -> Testing -> Approval cycles 11) Final approval of the a. functionality, CourtAlert Response to RFP 50 b. proposed migration (if applicable) c. staff readiness 12) (Optional) Migration to production for a parallel test week so the department can enter data in both system and compare the reports in both systems 13) Final Migration – going live. 14) Follow up for support and any additional changes. In the beginning one or two “Categories” will be implemented concurrently. After some time and the system is live for a least one Category, several can be implemented concurrently. The COA will be asked to provide a qualified Project Manager or Managers with both the knowledge and the experience for such project. The COA Project Manager(s) will: i) Plan and coordinate all meetings ii) Provide contact with subject matter expert for each category iii) Decide and agree on priority iv) Provide timely response to CourtAlert request v) Weekly review of the project status and the plans for next week vi) Meetings with various departments and Subject Matter Experts to discuss the implantation of various categories vii) Case type documentation viii) Ongoing feedback and degree of user and management satisfaction. All of the Software implementations were successful and all clients, no exception, later report the project to be much shorter, less effort and certainly more fun than expected. One reason is that clients realize how import the system is and assign top qualified individuals as their project manager(s). Various environments throughout the project phases: Under the leadership of the COA project manager(s) the following steps are typically taken: • Ongoing support – CourtAlert and perhaps internal COA Help Desk • Enhancements, if applicable, are handles as programming assignments: estimation, approval, programming, acceptance, documentation, and support. CourtAlert Response to RFP 51 Post Go-Live Support: As mentioned earlier, most of the world’s largest law firms and law organizations rely on CourtAlert support, and we raise to the occasion. We ask the CAO team to contact any of CourtAlert clients and specifically inquire about the commitment to Support. A note about enhancements: It is very likely that during (and after) the project the CAO might want to implement enhancements that were or are provided to other clients. CourtAlert project manager (“VPM”) will present each enhancement and the CAO Project Manager(s) will present and will obtain approval (or disapproval) from the subject matter experts. The cost of licensing such future enhancements is including in the monthly maintenance charge, but not the cost of implementation and training, which will be pre-estimated and approved by the CAO. Data Conversion CourtAlert does not expect the data conversion to be a major challenge as we have converted data from whole host of systems, including Access and Excel. The methodology to convert the data is documented, tried and true. We will provide data- mapping and multiple variation of data conversion. The CAO project manager(s) will approve the data-mapping. “Data-mapping” is an excel document listing which data element in the source system is to be converted to which data element in the CourtAlert Case Management software. Data Cleansing: In addition to bringing the data over, CourtAlert will provide data cleansing, consisting of: Uniqueness – that every judge, party, attorney, vehicle (if applicable) etc. has one and only one name Checking against external system – for example, downloading from courts database data to validate against the CAO data. CourtAlert Response to RFP 52 Data Augmentation – Downloading external data to enrich the CAO information. For example, Federal court cases information, header type, dockets and PDFs, can be downloaded from PACER. CourtAlert has many existing programs to provide this functionality, at no additional cost. CourtAlert would be excited for the opportunity to conduct as many product demonstrations as requested. Key personnel would also be willing to be interviewed. Due to travel restrictions during the pandemic we request that some interviews and demonstration be conducted online when appropriate. For the Tasks to be completed by vendor and the City please see Appendix E - Typical Implementation Tasks A Typical Implementation Plan is attached as Appendix D - Typical Implementation Plan. Also an overview of the project can be found at Appendix F - Project Management Methodology. CourtAlert estimates that a project of your size would be completed in less than 6 months. This is a very conservative estimate. Present and Projected Workloads The CourtAlert implantation team is working on 4 implementations for Big-Law clients. These projects typically are 3-6 months long and most will complete by year end. CourtAlert has more than enough resources to successfully complete this implementation. Training CourtAlert will provide the CAO with user extensive training. Training focuses on the use of CourtAlert Case Management for the CAO and understanding of the CourtAlert notices and court workflow. Initial training is provided as soon as the client schedules attorneys and other staff together. Periodic refresher training on new enhancements is also readily available. CourtAlert also provides training for a client’s new employees as part of the client’s employee “on-boarding” process. CourtAlert will provide “Cheat Sheets” dedicated to the specific configuration of each case category and department. These serve as reference guides for new and seasoned employees. CourtAlert will also record and transcribe videos on specific features and make CourtAlert Response to RFP 53 them available for unlimited additional viewing from any computer or mobile device. In addition to end users training, which is typically done at groups and when the system is first implemented, CourtAlert will provide “train the trainer” sessions if so desired by the CAO. They typical project plan includes at least 4 training sessions. Training sessions are recorded and made available for future reference. 1) Case Creation and Disposition (Beginner) 2) Docketing and Calendaring (Beginner) 3) Advanced Features and Reporting (Advanced Users) 4) Inquiry module Reporting (Mid-level Users) Documentation CourtAlert provides detailed and illustrated manuals for the Docketing, Inquiry and Administrative modules of the system. The manual will be detailed and through, however most users find the system to be very easy to use and rarely consult the manual. Maintenance and Support CourtAlert’s reputation is founded on the quality of our Support. CourtAlert has successfully set up the Case Management system and dozens of large law firms and organizations. Only one time in the past 20 years has a customer switch out of our system, and that was due to a firm merger. CourtAlert’s stellar commitment to support and client satisfaction has been proven time and time again. Please reach out to our clients for references. CourtAlert guarantees 99.9% uptime with generous Support guarantees. Support request are often responded to in minutes, well before the commitments in our SLA. CourtAlert is committed to the support of our product. The following is typically included in our Maintenance Service Agreement. Updates CourtAlert will notify Customer of Software Updates. CourtAlert will send these notices by email to the designated Customer contacts and with Customer’s assistance CourtAlert will install the Client Software updates. CourtAlert Response to RFP 54 Maintenance includes updates as defined below: A maintenance release is a general software release that may include minor feature and functionality changes and enhancements or bug fixes or patches. A minor version release or patch is a general software release that may include bug fixes, error corrections and/ or other minor changes. A new version contains new functionality, features and bug fixes to prior versions. Coverage includes updates for supported Software portion of the Solution but not for new software available from CourtAlert. CourtAlert at its sole discretion has the right to determine what is “new software”. Support CourtAlert is available for technical support by telephone and email between 9:00 AM and 6:00 PM Eastern Time Monday through Friday, excluding federal holidays (“Service Hours”), in the event that Customer has questions about the software functionality or reports any Error (as such term is hereinafter defined) in the Software. Additionally, CourtAlert shall provide best effort email support for all times that are not Service Hours. “Error” means a failure of the Software to operate in accordance with reasonable expectations and highest industry standards. Response and Resolution Times. CourtAlert shall do its best effort to implement temporary workaround procedures and shall demonstrate to Customer good faith and shall continue diligent initiation and prosecution of corrective measures for all such problems involving the Software within the resolution Support Ticket Severity Response Requirement times set forth below. CourtAlert Response to RFP 55 Support Ticket Severity Response Requirement Critical Any outage(s) of the Software classified as “System Down”, where essential functionality is unavailable and/or substantial data loss is experienced. Under 4 Hours Significant Any issue(s) causing “Restricted Functionality” of the Software where essential functionality is unavailable and/or data loss is experienced but the system is operational. Under 8 Hours Calendar Rules Any issue(s) occurring using the Calendar Rules. Under 1 Business Day Minimal Any issue(s) where minimal errors are occurring in the Software causing minor performance degradation. Under 1 Business Day Nominal Any general questions concerning the Software’s features, functionality, configuration, performance, upgrades, or enhancement requests, product feature requests, known bug status requests, etc. Under 2 Business Days For any Error deemed to be of Critical Support Ticket Severity by Customer, and so agreed by CourtAlert, CourtAlert shall have personnel continuously addressing the Error until such Error is resolved or reduced to Significant (as reasonably determined by Customer). During such period, Customer also agrees to have a knowledgeable representative available to help in the resolution. CourtAlert Response to RFP 56 Support CourtAlert offers email, online, and onsite support throughout each phase of the project from the Project Liaison and the CourtAlert support team in accordance with the Maintenance SLA. Our SLA was never called to task, we simply respond in minutes, not hours and days, and we stay with the issue continuously until resolved. Certainly, there was never any demand for liquidated damages or any similar brutal response from our clients, public or private. Project and Issue Control CourtAlert’s Project management plan provides an agile approach to the implementation of the Case Management system at your firm. Through ongoing communication and evaluation of the priorities CourtAlert is able to quickly and effectively deploy the system and migrate your data. a. Project Management Software: CourtAlert utilizes the project management tool JIRA for project control. (Please see http://en.wikipedia.org/wiki/JIRA for more information on JIRA.) b. Approvals: The Client Project Manager and The Client Docketing Managers and the CAO Project Liaison agree on approval procedures at the outset of implementation. c. Timing: Based on CourtAlert’s experience, the project is expected to take eight to twelve months to complete. It is impossible to guarantee that the project will be completed in this time frame or follow strictly the implementation plan without some revisions due to exigencies outside of CourtAlert’s and The Client Project Team’s control. However, both CourtAlert and The Client Project Team promise to put forth their best efforts to complete the project in five to eight months and to adhere to the implementation plan. d. Task Completion: Together the CAO Project Manager and the CourtAlert Project Manager prepare detailed documentation on each open task identified in the CourtAlert Implementation Plan until marked complete. e. Server Access for CourtAlert implementation team: For the most efficient use of time and resources, CourtAlert has 24/7 remote access, in accordance with The Client’s data security requirements, to the CourtAlert servers and databases through implementation. After implementation, CourtAlert may request remote access on an as- needed basis. f. Customizations: a. The CAO Project Liaison or other CourtAlert team member numbers, documents, and archives each customization request and makes such documentation available to the Project Team. CourtAlert Response to RFP 57 b. The CAO Project Liaison or other CourtAlert team member gathers requirements and specifications for each customization or enhancement request. c. The Client Project Manager and The Client Managers approve or reject each request according to the approval method agreed upon at the outset of the implementation. d. CourtAlert begins programming for any customization upon written approval from The Client Project Manager and The Client Managers. e. CourtAlert performs programming, unit testing and, when applicable, system testing in accordance with its standards. The resulting customization, either a single item or a group of related customizations, is presented to The Client Project Manager. f. The Client Project Team and selected The Client testers perform Quality Assurance testing. g. CourtAlert makes additional changes as necessary. h. When the customization is ready, it is submitted to The Client Project Manager for final approval. CourtAlert Response to RFP 58 List of Appendices Appendix A - Partial List of Clients of the Software Appendix B - Resumes of Key Personnel Appendix C – Organization Chart Appendix D - Typical Implementation Plan Appendix E - Typical Implementation Tasks Appendix F - Project Management Methodology Appendix G - Service Level Agreement Appendix H – Cloud Security Documentation Appendix I - System overview Appendix J – Training Documentation - User Manual Appendix K– Sample Training Checklist Appendix L – Sample screenshots of the Software used for diversified categories Appendix M - Letter from Suffolk County CourtAlert Case Management – Screenshots of Docketing Input Module CourtAlert® Case Management Screenshots of Docketing Input Module This document is the copyrighted and intellectual property of CourtAlert®, and the content is confidential and may not be disclosed to anyone who is not a full-time employee of the intended receiving firm. This document contains screenshots of a typical Docking input module. Many of these screens can be further configured. Only the docketing input module is displayed, not the web-based attorney inquiry module. Table of Figures Figure 1 Typical Home menu _____________________________________________________________________ 3 Figure 2 Sample case list ________________________________________________________________________ 3 Figure 3 Typical “Reconciliation” screen displaying court notices to be reviewed ____________________________ 4 Figure 4 Typical case heading display ______________________________________________________________ 5 Figure 5 Typical Docket entry with PDF attachments __________________________________________________ 5 Figure 6 Typical Event entry ______________________________________________________________________ 5 Figure 7 Typical Trigger selection screen ____________________________________________________________ 6 Figure 8 Typical Event Tools screen, combine tool showing _____________________________________________ 6 Figure 9 Typical Case – General Screen _____________________________________________________________ 7 Figure 10 Typical Case Team Selection Screen _______________________________________________________ 7 Figure 11 Typical Party Selection Screen ____________________________________________________________ 8 Figure 12 Typical Additional information screen displaying structured notes and ethical walls _________________ 9 Figure 13 Optional statistics screen¸ sample configuration ____________________________________________ 10 Figure 14 Typical case Disposition Screen __________________________________________________________ 10 Figure 15 Sample Ethical Wall Exclusionary ________________________________________________________ 11 Figure 16 Box Archiving ________________________________________________________________________ 12 Figure 17 Search and Edit Entity Demographics _____________________________________________________ 13 Figure 18 Sample Appeal Case Details _____________________________________________________________ 14 Figure 19 Sample Case Types in Case List __________________________________________________________ 15 Figure 20 Sample Child Abuse Case Type ___________________________________________________________ 15 Figure 21 Sample Child Support Case _____________________________________________________________ 16 Figure 22 Sample Party and Representation Screen __________________________________________________ 17 Figure 23 Sample Real Estate Contract Case Details __________________________________________________ 17 Figure 24 Sample Contract Case Type _____________________________________________________________ 18 Figure 25 Sample Party Type Drop down __________________________________________________________ 19 Figure 26 Sample Docket Entry __________________________________________________________________ 20 Figure 27 Sample Reconciliation Screen with Court Data ______________________________________________ 21 Figure 28 Sample ERPO Case ____________________________________________________________________ 22 Figure 29 Sample AOT - Mental Hygiene Case ______________________________________________________ 23 Figure 30 Sample Case List with Family - Collections Selected __________________________________________ 24 Figure 31 Sample Case List with Guardianships Cases ________________________________________________ 25 Figure 32 Case List with Forfeiture Cases Watchlist __________________________________________________ 26 Figure 33 Health Covenant Case List ______________________________________________________________ 27 Figure 34 Screen to import Parties _______________________________________________________________ 28 Figure 35 Sample Introductory Resolution Case Types ________________________________________________ 29 CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix N - Page 1 CourtAlert Case Management – Screenshots of Docketing Input Module Figure 36 Sample JD/PINS Case Type ______________________________________________________________ 30 Figure 37 Sample Parties and Representation Screen _________________________________________________ 31 Figure 38 Document Types available for different Categories __________________________________________ 32 Figure 39 Category Specific Party Types ___________________________________________________________ 33 Figure 40 Read-only web view with case details _____________________________________________________ 34 Figure 41 Case List for Sewer Cases _______________________________________________________________ 35 Figure 42 Automatic Templates for a case type _____________________________________________________ 36 Figure 43 Staff selection screen __________________________________________________________________ 37 Figure 44 Calendar Review Tool __________________________________________________________________ 38 Figure 45 Document Entry Screen ________________________________________________________________ 39 CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix N - Page 2 CourtAlert Case Management – Screenshots of Docketing Input Module Figure 1 Typical Home menu Figure 2 Sample case list CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix N - Page 3 CourtAlert Case Management – Screenshots of Docketing Input Module Figure 3 Typical “Reconciliation” screen displaying court notices to be reviewed CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix N - Page 4 CourtAlert Case Management – Screenshots of Docketing Input Module Figure 4 Typical case heading display Figure 5 Typical Docket entry with PDF attachments Figure 6 Typical Event entry CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix N - Page 5 CourtAlert Case Management – Screenshots of Docketing Input Module Figure 7 Typical Trigger selection screen Figure 8 Typical Event Tools screen, combine tool showing CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix N - Page 6 CourtAlert Case Management – Screenshots of Docketing Input Module Figure 9 Typical Case – General Screen Figure 10 Typical Case Team Selection Screen CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix N - Page 7 CourtAlert Case Management – Screenshots of Docketing Input Module Figure 11 Typical Party Selection Screen CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix N - Page 8 CourtAlert Case Management – Screenshots of Docketing Input Module Figure 12 Typical Additional information screen displaying structured notes and ethical walls CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix N - Page 9 CourtAlert Case Management – Screenshots of Docketing Input Module Figure 13 Optional statistics screen¸ sample configuration Figure 14 Typical case Disposition Screen CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix N - Page 10 CourtAlert Case Management – Screenshots of Docketing Input Module Figure 15 Sample Ethical Wall Exclusionary CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix N - Page 11 CourtAlert Case Management – Screenshots of Docketing Input Module Figure 16 Box Archiving CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix N - Page 12 CourtAlert Case Management – Screenshots of Docketing Input Module Figure 17 Search and Edit Entity Demographics CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix N - Page 13 CourtAlert Case Management – Screenshots of Docketing Input Module Figure 18 Sample Appeal Case Details CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix N - Page 14 CourtAlert Case Management – Screenshots of Docketing Input Module Figure 19 Sample Case Types in Case List Figure 20 Sample Child Abuse Case Type CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix N - Page 15 CourtAlert Case Management – Screenshots of Docketing Input Module Figure 21 Sample Child Support Case CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix N - Page 16 CourtAlert Case Management – Screenshots of Docketing Input Module Figure 22 Sample Party and Representation Screen Figure 23 Sample Real Estate Contract Case Details CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix N - Page 17 CourtAlert Case Management – Screenshots of Docketing Input Module Figure 24 Sample Contract Case Type CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix N - Page 18 CourtAlert Case Management – Screenshots of Docketing Input Module Figure 25 Sample Party Type Drop down CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix N - Page 19 CourtAlert Case Management – Screenshots of Docketing Input Module Figure 26 Sample Docket Entry CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix N - Page 20 CourtAlert Case Management – Screenshots of Docketing Input Module Figure 27 Sample Reconciliation Screen with Court Data CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix N - Page 21 CourtAlert Case Management – Screenshots of Docketing Input Module Figure 28 Sample ERPO Case CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix N - Page 22 CourtAlert Case Management – Screenshots of Docketing Input Module Figure 29 Sample AOT - Mental Hygiene Case CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix N - Page 23 CourtAlert Case Management – Screenshots of Docketing Input Module Figure 30 Sample Case List with Family - Collections Selected CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix N - Page 24 CourtAlert Case Management – Screenshots of Docketing Input Module Figure 31 Sample Case List with Guardianships Cases CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix N - Page 25 CourtAlert Case Management – Screenshots of Docketing Input Module Figure 32 Case List with Forfeiture Cases Watchlist CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix N - Page 26 CourtAlert Case Management – Screenshots of Docketing Input Module Figure 33 Health Covenant Case List CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix N - Page 27 CourtAlert Case Management – Screenshots of Docketing Input Module Figure 34 Screen to import Parties CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix N - Page 28 CourtAlert Case Management – Screenshots of Docketing Input Module Figure 35 Sample Introductory Resolution Case Types CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix N - Page 29 CourtAlert Case Management – Screenshots of Docketing Input Module Figure 36 Sample JD/PINS Case Type CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix N - Page 30 CourtAlert Case Management – Screenshots of Docketing Input Module Figure 37 Sample Parties and Representation Screen CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix N - Page 31 CourtAlert Case Management – Screenshots of Docketing Input Module Figure 38 Document Types available for different Categories CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix N - Page 32 CourtAlert Case Management – Screenshots of Docketing Input Module Figure 39 Category Specific Party Types CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix N - Page 33 CourtAlert Case Management – Screenshots of Docketing Input Module Figure 40 Read-only web view with case details CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix N - Page 34 CourtAlert Case Management – Screenshots of Docketing Input Module Figure 41 Case List for Sewer Cases CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix N - Page 35 CourtAlert Case Management – Screenshots of Docketing Input Module Figure 42 Automatic Templates for a case type CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix N - Page 36 CourtAlert Case Management – Screenshots of Docketing Input Module Figure 43 Staff selection screen CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix N - Page 37 CourtAlert Case Management – Screenshots of Docketing Input Module Figure 44 Calendar Review Tool CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix N - Page 38 CourtAlert Case Management – Screenshots of Docketing Input Module Figure 45 Document Entry Screen CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix N - Page 39 CourtAlert® Case Management System Overview Contents CourtAlert® Case Management Software...................................................................................................... 2 I. Benefits of CourtAlert Case Management ............................................................................................ 2 II. Functionality and Key Features ............................................................................................................. 2 a. Docketing Module ............................................................................................................................. 3 Creating a New Docket ......................................................................................................................... 3 Creating a docket from Electronic Court Notifications – Reconciliation .............................................. 5 Calculating Diaries ................................................................................................................................. 7 Adding New Cases ............................................................................................................................... 11 b. Inquiry module ................................................................................................................................ 15 c. Administrative Module ................................................................................................................... 17 d. Integration with 3rd Party Software ................................................................................................ 17 i. Microsoft Exchange / Outlook ........................................................................................................ 17 ii. Human Resources ........................................................................................................................... 17 iii. Accounting ...................................................................................................................................... 17 iv. Autonomy iManage ........................................................................................................................ 18 e. Additional Features ......................................................................................................................... 18 i. Report Writing ............................................................................................................................ 18 ii. Knowledge Management and Case Classifications ..................................................................... 19 iii. Conflict Checking ......................................................................................................................... 22 iv. Attorney Profile Database ........................................................................................................... 23 v. Data Migration ............................................................................................................................ 23 CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix K - Page 1 CourtAlert® Case Management System Overview CourtAlert® Case Management Software The existing CourtAlert® Case Management Software (“CourtAlert CM”) fulfills the vast majority of the County Attorney’s office’s needs and requirements. This software is currently used by the world’s largest law organizations in NY and is designed for environments with a heavy caseload and considerable case management needs. The “out of the box” version of this software, with minor cosmetic changes, would allow the County Attorney’s office to achieve their major business objectives. I. Benefits of CourtAlert Case Management • Maintain structured case details • Maintain clear and organized dockets for each case with a docket sheet and applicable deadlines • Automatically remind users of upcoming deadlines through email Diary Alerts • Increase office productivity by allowing all authorized users to access all dockets and documents anytime, from anywhere. • Streamline management of documents and information related to cases by standardizing workflows, sharing document and uniformed calendaring. • Allow for running dozens of different reports over the information in the system such as Calendar reports, workflow report, etc. • Seamlessly integrate court notifications with the dockets II. Functionality and Key Features This software is currently on Version 6.0. Descriptions herein refer to this version. CourtAlert CM has 3 components: • Case Entry/ Docketing Module: allows users to input data into the system, including case particulars, dockets, PDFs, and deadlines. • Inquiry Module: Browser based system accessible from anywhere. This module allows users to view their cases, dockets, PDF’s stored in the system and calendars. Office wide reports and calendar are also accessible. • Administrative Module: This component allows for running reports, creating customized reports, audit reports, case reports, etc. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix K - Page 2 CourtAlert® Case Management System Overview a. Docketing Module The Docking module is used to input information into the system including: updating existing cases, adding PDFs, calculating diaries and deadlines as well as adding new cases. Creating a New Docket Users are encouraged to include all relevant information about the new docket. There are many data fields that may be filled, all are optional. By using the prescribed data fields the docket texts are uniform and consistent throughout the system. For example, a case is always referred to by the same name, judges are always listed consistently, etc. A. Optional Fields from which the user can determine the Document Type (lookup by any word or entry based on Group, Subgroup and Type), Received /Served, by which part to which party and all the relevant dates. B. This is the text of the docket. The text will be automatically prepopulated based on the user’s selections of the fields in area A. Users may also include their own free hand text to describe the docket or add personal comments. C. Attach the PDF or other relevant document(s). Users may click on the link and the document will open in a new window to allow for verification that the correct document has been added. Note that normally at this point user would calculate the relevant diaries before moving on to section D. D. Save – will save the docket to the system. Save and Notify – will save the docket to the system and will automatically email the case team with the docket text, a link to the PDF attached and the diaries calculated. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix K - Page 3 CourtAlert® Case Management System Overview CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix K - Page 4 CourtAlert® Case Management System Overview Creating a docket from Electronic Court Notifications – Reconciliation Using CourtAlert Patent Pending Technology the CourtAlert CM system automatically captures incoming notifications from various courts (see below) and brings them into the docketing system. The PDF is downloaded and court’s docket text is used to bootstrap your docket. This process is called “Reconciliation”. With as little as three clicks of the mouse, the user can import the docket text and the PDF to create a docket in the CourtAlert CM. Once the Docket and PDF are stored in CourtAlert CM all users can access that PDF from CourtAlert CM and do not need to go back to PACER to retrieve the documents. This technology will save the CA a lot of time currently spent going to PACER to retrieve documents. More importantly, it will save the cost of retrieving documents from PACER. CourtAlert Case Management clients have saved thousands of dollars off their PACER bill using this feature alone. Electronic Notifications are captured from the following courts: 1. All PACER courts, every Federal District, Bankruptcy and Appeals court in the U.S. All alerts from those cases may be added to the docketing system using the Reconciliation feature. 2. New York State Electronically Filed Cases (“NYSCEF”) Notifications – NYSCEF continues to expand its coverage. CourtAlert CM will cover all NYSCEF courts as the requirements of the courts change. Currently, in Suffolk County Malpractice and Commercial Division, cases must be filed electronically. All alerts from those cases may be added to the docketing system using the Reconciliation feature. 3. CourtAlert Notices – for cases being tracked with CourtAlert NY Case Tracking all CourtAlert notifications on cases are also reconcilable. Note: CourtAlert NY Case Tracking includes the thirteen largest counties in NY, including the cases in Suffolk County. All alerts from those cases may be added to the docketing system using the Reconciliation feature. For more information on case tracking please see the NY Case Tracking Section of this proposal. To reconcile a notification the user would perform the following steps. 1. Select which Court notification you wish to reconcile from the list of pending (non-reconciled) notifications. Click on “Reconcile” next to the notification to be reconciled. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix K - Page 5 CourtAlert® Case Management System Overview 2. Determine if the incoming notification pertains to a new docket or to an existing Docket. To create a new docket the user clicks on the blank page icon. 3. The next screen will be the standard docketing screen with all the data elements pre-populated. The docket will now automatically include • Assignment to the case automatically • The text of the docket from the notification • The PDFs that came with the notification CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix K - Page 6 CourtAlert® Case Management System Overview The reconciliation process allows for easy inclusion of updated court data into the Case Management system. The CourtAlert notices precisely describe what has happened to the case and the reconciliation allows for this information to be included in the CA case dockets. Calculating Diaries Use of Diaries in CourtAlert CM: Keeping track of deadlines is a critical component of the CourtAlert CM system. Deadlines are entered by the users and appear throughout CourtAlert CM in the following locations for the team assigned to the case. • Upon entering the deadline, a notification is sent to the case team • On all reminder alerts sent before upcoming deadlines based on a predetermined schedule (e.g. 7 days, 3 days and 1 days before a deadline) • On outlook calendars as appointments, optionally. Including outlook on Mobile devices and phones • On the office-wide calendar / tickler reports • On the attorney’s calendar / tickler reports When entering a diary the user will determine who should receive notification of the diary. The Case Team, any other specific email addresses, etc. Types of Diaries: There are 2 categories of diaries in CourtAlert CM. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix K - Page 7 CourtAlert® Case Management System Overview 1. Diaries associated with a specific Docket. In NY, the overwhelming majority of diaries are triggered from a specific docket. Therefore, most of the diaries would be calculated upon docketing. 2. Diaries associated with a case, but not related to a specific docket. This feature allows users to create a diary for a case that is not related to a specific document. Diary Text: The text of the deadline that appears in the reminders, outlook and reports. Calculating Diaries: There are three tools available for users to calculate diaries / deadlines in CourtAlert CM. 1. Entering the data in manually. This is most often used when the user knows the Resulting Diary Date. E.g. when a scheduling order specifies the date of a particular action. 2. Calculating the deadline based on a known Rule / Statute Using this tool the user can calculate the deadline using the known rule. For example: Today’s Date + 10 Business Days = Resulting Diary Date. This tool differentiates between Business Days and Calendar Days. It factors in court holidays. If the Resulting Diary Date calculated falls out on a weekend the results will appear in Red. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix K - Page 8 CourtAlert® Case Management System Overview 3. Using Automatic Rules (Not recommended for NY based Organizations such as the CA) Using automatic rules is not recommended in NY since there are multiple levels of rules attorneys must consider when calculating deadlines. (e.g. CPLR, Court’s rules and judge’s individual rules). Therefore, this proposal will not elaborate further on this feature. Users contract directly with CalendarRules.com for the rules set. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix K - Page 9 CourtAlert® Case Management System Overview CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix K - Page 10 CourtAlert® Case Management System Overview Adding New Cases Adding a new case into CourtAlert CM requires the user to fill in 4 tabs. Not all data elements are required of the user. Users are encouraged to include as much information as they have available to allow for future inquiry into the case by each data elements. These tabs have many fields which may be customized to the needs of the CA. For example, when adding a case, the user will determine which Unit the case is assigned to. Adding New Cases - General Tab In this tab users input the following data elements: • Forum, Venue and Location • Index Number • Main Plaintiff and Defendants • Nature of Suite, if applicable (Federal cases only) • The case nickname (Referred to as) • Lead case, if applicable • Related Cases in the CourtAlert CM System, if applicable – once cases are marked as related in the CourtAlert CM users are reminded to update the dockets of related cases when creating dockets. • Cases in Other Courts in the CourtAlert CM system , if applicable • Third Party index number, if applicable • Case Status – Open or Closed • ECF or Non-ECF Case Status • Internal Number assigned by the CA • Judge(s) assigned to the case • Unit Assigned to the Case CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix K - Page 11 CourtAlert® Case Management System Overview CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix K - Page 12 CourtAlert® Case Management System Overview Adding New Cases – Staff Tab In this tab users input the following data elements: • Assign a case team – the group of authorized users who are assigned to this case. • Individual Staff members assigned to this case. For each staff member assigned user will determine o Title of the user (associate, paralegal, etc.) o Start Date: Date assigned to the case o Termination Date: date removed from the case o If the user is the Case Manager o Notification preference for the user as it relates to this case: receive dockets and/or receive Diary Alerts CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix K - Page 13 CourtAlert® Case Management System Overview Adding New Cases - Parties Tab In this tab users input the following data elements: • All named parties • Full Title of the Party • Party Type (Plaintiff, Defendant, Appellant, etc.) • The firm and attorney representing each party Adding New Cases – Additional Information Tab In this tab users input the following data elements: • Room/Part in the court where this case is located • Case End Date – if the case is closed CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix K - Page 14 CourtAlert® Case Management System Overview • Notes and Comments – this field is used for internal workflow notes and other case related comments • Case Classifications – user has the ability to assign multiple classifications to a case. Selecting classifications is important for knowledge management and reference. For example, running a report on all cases in the CourtAlert CM that relate to a specific classification. More details on this function are available in the ‘Extra Features’ chapter of this document. • Conflict Checking – this area allows users to exclude specific users from accessing the case. A user that is conflicted out of a case will never see the case information, cannot access the case from eh Inquiry Module, will not see the case on the firm wide calendar and will never receive notifications about the case. More information on the conflict checking in available in the Conflict Checking Section of this document. b. Inquiry module The inquiry module is a web based inquiry available to all authorized users. Using this module, users may view the information in the system, but cannot edit or add new information. Using the Inquiry Module users can view: CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix K - Page 15 CourtAlert® Case Management System Overview • Their own case list • Docket sheet for all authorized cases • PDFs of every docket for all their cases • Personal Calendar • Office Wide Case lists, dockets, and PDFs • Office- wide Calendar • Daily Word reports • Knowledge Management Documents - these are documents flagged in the system as good samples of work. Please refer to the Knowledge Management chapter for more details on this function. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix K - Page 16 CourtAlert® Case Management System Overview c. Administrative Module The Administrative module is used to for backend functionalities, such as: • Run Reports and Report Writing – CourtAlert CM gives users the ability to run dozens of reports and even to create their own report based on their own criteria. Please see the Report Writing section for more details on the types of reports and how to use the report writer. • Define Select fields (e.g. create a new case classification; define a case/unit team, etc.) • Maintain the Attorney Profile Database – please see the Attorney Profile Database section for more details on this feature. d. Integration with 3rd Party Software i. Microsoft Exchange / Outlook CourtAlert CM integrates with Microsoft Exchange / Outlook for Calendaring. Individual users see their diaries as an appointment. If the event that diary is Adjourned, the system automatically adjourns the diary in Outlook calendars as well. Outlook calendars maybe used in any format allowable by Outlook, Desktops, laptops, Smartphones, tablets, etc. Users can also view their on calendar, as well as the office wide calendar, using the Inquiry Module. ii. Human Resources This integration keeps track of all human resources information. This is used to get the staff’s names, hiring dates, termination dates, etc. This information is used throughout the system. For example, when selecting which attorneys are assigned to a case, the user picks the names from the Human Resources list. Furthermore, once a user is terminated, the system alerts the office manager of any cases that are left ‘orphaned’ or unassigned to any attorney. iii. Accounting This integration is a means to feed into Client Matter Numbers, if applicable. At this time there are no plans to integrate the CA cost accounting systems with the case management system, but this could be done in the future. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix K - Page 17 CourtAlert® Case Management System Overview iv. Autonomy iManage In the event that the CA acquires this software, the CourtAlert integration with it allows for the following functionalities: • Document profile created automatically • Includes full text of the entire docket • Matter centric structure supported • Latest version of the document used • PDF files stored in FileSite • Fully accessible from CourtAlert Inquiry Module e. Additional Features i. Report Writing • Attorney Tickler Report • Firm Wide Calendar Report • Eight Day Calendar Report • Case Header Report • Case Summary Report • Ad-Hoc Report – this is an elaborate report-writer tool allowing users to define own reports • Audit Search Report • Calendar Report • Case Report • Daily Work Report • Record File Index Report • Work Report • Case Notes Report • Case Classification Report • Calendar Report by Department Custom Reports (Excel based reports) • Cases without any Rep • Cases without any Rep or Staff • Cases without any Rep, but has Staff in Case • Cases with no Branch information • Courts and Counties with no abbreviation code CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix K - Page 18 CourtAlert® Case Management System Overview • Classification Types in system • Cases without any classification code • Cases without any docket activity within last year • All Types in the system • Open cases without any Judge • Future Diaries on Weekend • Open cases without future diaries • Federal Notices Ignored during Last One Week ii. Knowledge Management and Case Classifications What it does: Through the Inquiry Module users can search for flagged dockets or documents. Flagged dockets or documents are those that deemed to be good work samples, often used to help newer attorneys to draft similar types of documents. Within the flagged document list, users can narrow the search. The search may be narrowed by the following criteria: Forum, Venue, Judge, Author, Case Classification (Cases may have multiple classifications assigned in the docketing software), Document Type and Date Range. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix K - Page 19 CourtAlert® Case Management System Overview How to Flag: Select users are given the authority to flag specific dockets / documents as “good sample”. The user may also optionally add the author of each document. Note: You may also add the Author of the document either in the KM page in the Inquiry Module, or while docketing in the Docketing Module. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix K - Page 20 CourtAlert® Case Management System Overview CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix K - Page 21 CourtAlert® Case Management System Overview iii. Conflict Checking Conflict Checking is an essential tool to ensure that users who have a conflict of interest do not have access to cases they are conflicted out from. Conflict check is selected in the Additional Information Tab when adding a new case. In CourtAlert CM a user that is conflicted out of a case will be able to see the case anywhere throughout the system, including: • Not able to view the case in the Inquiry Module • Not able to see the case in the office-wide calendar or Outlook • Not able to see the case in the tickler reports There are two methods of determine conflicts using CourtAlert CM Exclusive Method: Allows the entire office to have access to the case except for the specific users selected. Those users will be conflicted out. Inclusive Method: No users will be able to access to the case except the approved case team and the approved office managers. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix K - Page 22 CourtAlert® Case Management System Overview iv. Attorney Profile Database The attorney profile database is maintained in the Administrative Module. Using this feature the CourtAlert CM maintains the following information for every user: • States and Courts of Admission • Bar Registration Numbers • Date of Admission • Admission Expiration (includes a reminder email when a user’s admission is up for renewal) • PACER / Electronic Case Filings Login and Password • NY Electronic Filling Login and Password v. Data Migration One method to “bootstrap” the implementation which we have successfully utilized in the past is to migrate the court data for specific cases into the case management database. We can migrate data from the Federal Courts Pacer system and from the NYS Supreme NYSCEF (“Electronic Filing”) system. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix K - Page 23 CourtAlert® CM/ECF User Manual for the Docketing Module CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix L - Page 1 ABOUT THE DOCKETING MODULE ......................................................................................................................... 3 CASE LIST ............................................................................................................................................................... 3 Searching .............................................................................................................................................................. 4 Moving / Resizing / Sorting ................................................................................................................................... 5 Additional Columns ............................................................................................................................................... 5 MASS EDIT ............................................................................................................................................................. 6 CREATING A NEW DOCKET ..................................................................................................................................... 9 CREATE A NEW DOCKET DE NOVO .................................................................................................................................... 9 RECONCILIATION - CREATING A DOCKET FROM ELECTRONIC COURT NOTIFICATIONS .................................................................. 11 RECONCILIATION - IGNORE NOTICES FOR CONSOLIDATED CASES ............................................................................................. 15 DOCKET NOTIFICATIONS (“SAVE AND NOTIFY”) ................................................................................................... 17 CALCULATING DIARIES / DEADLINES .................................................................................................................... 18 USE OF DIARIES / DEADLINES IN COURTALERT CASE MANAGEMENT: ..................................................................................... 18 DIARY / DEADLINE TEXT: ............................................................................................................................................... 18 CALCULATING DIARIES ................................................................................................................................................... 19 Manually Calculating Diaries: ............................................................................................................................. 19 Days Calculator ................................................................................................................................................... 19 Using Automatic Rules with CalendarRules.com ............................................................................................... 21 CALENDAR RULES EXPLORER........................................................................................................................................... 21 Export the results of a Rules Explorer ................................................................................................................. 22 ADJOURNING DIARIES ................................................................................................................................................... 24 Often the need arises to Adjourn or Continue events. This section describes how to adjourn several dates at the same time. .................................................................................................................................................... 24 Mass Adjournment .............................................................................................................................................. 24 Adjournment Trail ............................................................................................................................................... 29 Private Diaries ..................................................................................................................................................... 30 ADDING A NEW CASE ........................................................................................................................................... 31 ADDING NEW CASES - GENERAL TAB ............................................................................................................................... 31 ADDING NEW CASES – STAFF TAB ................................................................................................................................... 32 ADDING NEW CASES - PARTIES TAB ................................................................................................................................. 34 ADDING NEW CASES – ADDITIONAL INFORMATION TAB ...................................................................................................... 36 CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix L - Page 2 About the Docketing Module The Data Entry/ Docketing module is used to input information into the system, including: searching, creating and changing cases, adding a docket (a record of an event, document etc.), adding PDFs or other computer files to the Docket, calculating diaries and deadlines as well as adding new cases. Data entered at the time of case entry becomes automatically available for docketing and inquiry purposes, as described further herein. Case List When a user first logs into the system they are presented with a list of all the cases in the system. This case list is designed to be easy to search and extend with additional columns. Figure 1 Case List (Default View) CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix L - Page 3 Searching The Case List can be searched or filtered in 4 ways: 1) Case Status – The Case Status radio boxes can be used to filter down Recent / All / Open / Closed cases 2) Quick Search – On the top left corner there is a quick Case Search. This search can be used to search Any part of the Index number / Client / Matter/ Any Party Name / Judge. Additionally you can search within Docket and Diary text if the respective checkboxes are marked. 3) Advanced Search – The Advanced Search lets you search only within specific fields 4) Quick Filter – The blank line beneath the column header (column names) can be used to filter cases for a specific criteria. For example, to filter all cases where the Plaintiff name contains “United”, enter “united” in the box directly beneath plaintiff. The searched word is highlighted in the results. Figure 2 Quick Search CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix L - Page 4 Figure 3 Quick Filter row Additionally, When your mouse hovers over a column a Filter button Appears (a down triangle). Use this dropdown to select a filter from the grid. Figure 4 Dropdown filter in case list Moving / Resizing / Sorting • Columns can be moved around by clicking down on a column header and moved to a new location. • Columns can be resized by moving the mouse between the column you want to resize and the one to its right. The mouse cursor will change to a double arrow. While the mouse is still clicked down, drag the column width larger or smaller. • Resize a column to its “Best Fit” by right clicking on the column header and selecting “Best Fit” or “Best Fit (all Columns) • Sort a column by clicking on the column header. This will sort the column in Ascending order (denoted by a gray up triangle). Click again to sort Descending (denoted by a gray down triangle) Additional Columns A user can add additional columns to the grid by right clicking on the header row (column names) and selecting “column chooser”. A Customization dialog appears and additional columns can be selected. Double click on a column to add it to the grid, or drag a column to a specific column location. The following additional columns are available: (Bold are highly recommended) Column Description Case ID The CourtAlert unique Id assigned to each case CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix L - Page 5 Index # The Court Assigned Index Number Plaintiff The Main Plaintiff for the case Defendant The Main Defendant for the case Court The Court / Forum Name Venue The Venue / County Name Client The Client Number assigned to the case Matter The Matter Number assigned to the case Judge The Judge assigned to the case Referred To The Secondary Judge assigned to the case AKA The Case Nickname Source For Power Search - Which Column had the Hit Location The Location assigned to the case Office The Office the case is assigned to Case Manager The Name of the Staff Member that is marked as the Case Manager Case Status Open / Closed - The Case Status Start Date The Date the Case was Opened End Date The Date the Case was Closed Case Type ID The database ID for the Case Type Case Type The Case Type (Text) Case Staff The list of all Active Staff assigned to the case Appeared in Court The list of Staff that are marked as Appeared in Court Classifications The list of all Classifications assigned to the case Stage The Stage (if available) that the case is in Field 1 Custom Field 1 Field 2 Custom Field 2 Field 3 Custom Field 3 Client Name The Client Name Matter Name The Matter Name (Description) Matter Closed Date The Data the Matter was Closed (if available) Diary Count [Statistic] The Number of Diaries / Events Associated with this case Docket Count [Statistic] The Number of Dockets Associated with this case Future Diary Count [Statistic] The Number of Future Diaries / Events Associated with this case Last Diary Date [Statistic] The Last Diary / Event Date Last Docket Date [Statistic] The Last Docket Date Next Diary Date [Statistic] The Next Diary / Event Date Mass Edit If a user wishes to make a certain change to many cases, they can use the Mass Edit feature which saves time of individually editing each case. When the user clicks on Mass Edit on the left panel, a new column with checkboxes pops up to the left of the grid. The user can select the cases they would like to edit and then choose the appropriate action. The user can add staff, terminate staff, replace staff and close cases. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix L - Page 6 Figure 5 Replacing staff using Mass Edit Figure 6 Adding staff using Mass Edit CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix L - Page 7 Figure 7 Terminate staff using Mass Edit Figure 8 Close a case using Mass Edit CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix L - Page 8 Creating a New Docket This program is for recording a new action/event, document of phase in processing a case. Create a New Docket De Novo Users are encouraged to include all relevant information about the new docket. There are many data fields that may be inputted, all of which are optional. The users can also free-format text; spell checking is available. By using the prescribed data fields, the docket texts are uniform and consistent throughout the system. For example, using one name for a specific document means that it will always be referred to with the same name. Figure 5, below, depicts the key elements of the Docket Information Screen. Those elements are: A. This section of the screen shows the Optional Fields from which the user can determine the: Action, Event or Document Type (lookup by any word or entry based on Group, Subgroup and Type), Received /Served (if applicable), by which party to which party and all the relevant dates. B. This section of the screen shows the text of the docket. The text will be automatically pre-populated based on the user’s selections of the fields in area A. Users may also include their own freehand text to describe the docket or add personal comments. C. This section of the screen enables the user to attach the PDF or other relevant file(s). Users may click on the link and the document will open in a new window to allow for verification that the correct document has been added. For example, as taken directly from the RFP, when an Investigator conducts a witness interview, the original transcript and/or notes may be linked to the docket. D. This section of the screen enables the user to save the docket that has been created. “Save” immediately stores the information in the system. “Save and Notify” immediately stores the docket to the system and automatically emails the case team with the docket text. The notification email includes a link to the Video/PDF/Picture etc. that may be attached and the diaries (deadlines) are calculated. The information entered and PDF’s attached are immediately available for inquiry. PDF files are only one example, any type of computer file can be linked and run from the Docketing module, the Inquiry module, and the internal emails produced by the system. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix L - Page 9 Figure 9 Adding a New Docket CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix L - Page 10 Reconciliation - Creating a docket from Electronic Court Notifications In addition to the docketing process described immediately above, the CourtAlert Case Management system’s patent pending technology can automatically capture incoming notifications from OATH, various courts or any outside entities and bring them into the docketing system. The relevant PDF (or any attached file) is downloaded and court’s docket text is used to create the skeletal docket text. This process is called “Reconciliation.” With as little as 3 clicks of the mouse the user can import the docket text and the PDF to create a docket in the CourtAlert Case Management system. Once the Docket and PDF are stored in CourtAlert Case Management, all users can access that PDF from CourtAlert Case Management and do not need to go back to Outlook, court systems, PACER for Federal Cases, NYSCEF, etc.. to retrieve the documents. This technology will save a lot of time and cost. Electronic Notifications are captured from the following courts and or sources: 1. All Federal PACER courts, every Federal District, Circuit, Multidistrict and Bankruptcy court in the U.S.: all alerts pertaining to cases in those courts can be added to the docketing system using this Reconciliation feature. 2. New York State Electronically Filed Cases (“NYSCEF”) Notifications; It is noted here that NYSCEF continues to expand its coverage. 3. CourtAlert Notices: For cases being tracked with CourtAlert NY Case Tracking, all CourtAlert notifications on cases are also “reconcilable” as described above. Note: CourtAlert NY Case tracking currently includes the 13 largest counties in NY, including the cases in Suffolk County. All alerts from those cases may be added to the docketing system using the Reconciliation feature. NY Case Tracking is a separate optional service offered to the DOC. In order to reconcile a notification, the user would perform the following steps: 1. The user selects the Source such as Court notification, they wish to reconcile from the list of pending (non-reconciled) notifications. The user clicks on “Reconcile” next to the notification to be reconciled. Figure 6, below, is a screen shot showing multiple items in this mode. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix L - Page 11 Figure 10 Screenshot - Multiple items to be reconciled. 2. The user determines if the incoming notification pertains to a new docket or to an update to an existing Docket. If the item pertains to what will be a new docket, the user merely clicks on the blank page icon. Figure 7, below, shows the new docket button. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix L - Page 12 Figure 11 Screenshot with ‘New Docket’ button highlighted The standard docketing screen will appear. Figure 8, below, is the standard docketing screen with all the data elements pre-populated. The docket will now automatically include: • Assignment to the appropriate case automatically (case is added to the correct case file by automatically identifying the case file number • The text of the docket, taken directly from the court notification; and • PDFs or other attached files that came with the notification, if any. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix L - Page 13 Figure 12 Docket Information Screenshot Docket information prepopulated based on an externally received notification from court CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix L - Page 14 Reconciliation - Ignore notices for consolidated cases 1) In reconciliation you will see the same docket that was spread out across many cases 2) Filter for the Cases you would like to ignore. You can filter for a common defendant or the common docket text. 3) Once you have the notices selected click the “Mass Ignore” Checkbox on the top of the screen 4) Select All the Notices using the checkbox on the Header Row (the top row) 5) Uncheck any rows for cases you are involved in and would like to docket 6) Click on the “Ignore Selected Cases” button (second from the left) 7) Confirm your case selection in the follow screen CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix L - Page 15 8) Click “Ignore Selected Case” CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix L - Page 16 Docket Notifications (“Save and Notify”) Dockets may be sent via email to the case team or any other users in the network. Click on “Save & Notify” (available while editing a docket), or select multiple dockets from the docket grid and click on “Notify Multiple”. Figure 13 Selecting recipients The Save and Notify Recipients sceen allows you to - Type in additional names in the To box. The list defaults to case team members that are have “docket alerts” enabled. - Click “To ->” and select other staff members from the firm. The list can be easily filtered in the box above. - Select the email content. Include “Docket Text, Diaries and Attachments (as hyperlinks/nrls or as email attachments. - Include an optional note to the recipient(s) CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix L - Page 17 Calculating Diaries / Deadlines Use of Diaries / Deadlines in CourtAlert Case Management: A key strength of the CourtAlert Case Management system is its ability to keep track of deadlines and to notify users timely thereof. Deadlines are automatically calculated from a computerized Workflow or entered by the users and appear throughout CourtAlert Case Management at the following junctures for the team assigned to the case: Upon entering the diary/deadline, an email notification is sent to the case team; • On all reminder alerts sent before upcoming diary/deadline based on a predetermined schedule (e.g. 7 days, 3 days and 1 days before a deadline); • On Outlook / Exchange calendars as appointments, optionally. Includes Outlook on mobile devices, tablets and phones • On the Division Wide calendar / tickler reports; and • On the user’s calendar / tickler reports Figure 11 shows the manual diary entry screen, Workflow generated diaries are discussed below. When entering a diary, the user will determine who should receive notification of the diary. Typically, such recipients include the Case Team and case-specific e-mail addresses. Types of Diaries: There are two categories of diaries in CourtAlert Case Management: 1. Diaries associated with a specific Docket: The majority of diaries are triggered from a specific docket (event or document). Therefore, most of the diaries would be calculated upon docketing. 2. Diaries associated with a case, but not related to a specific docket: This feature allows users to create a diary for a case that is not related to (or triggered by) a specific docket. Figure 14 Adding a new diary / deadline Diary / Deadline Text: Diary text can be written free style. Often, the text of a diary is based on the underlying docket text. For example, with respect to the docket for a deadline to send Form XYZ, the diary alert may be “Last Day to send Form XYZ”. The system allows the user to use the docket text and edit it accordingly in order to easily create a standard diary text. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix L - Page 18 Calculating Diaries Manually Calculating Diaries: Click “Add” to create a diary by hand There are three tools available for users to calculate diaries / deadlines in CourtAlert Case Management: Entering the diary date manually: This is most often used when the user knows the Resulting Diary Date. e.g. when a scheduling order specifies the date of a particular action; Days Calculator (counting business or calendar dates): Figure 12 shows the system screen used for this tool. This tool enables the user to calculate a specific deadline using a known rule. A typical rule, for example, is “Today’s Date + 10 Business Days = Resulting Diary Date.” The tool differentiates between Business Days and Calendar Days. It also factors in court holidays, if applicable. If the Resulting Diary Date results in a weekend date, then those particular results will appear in Red. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix L - Page 19 Figure 15 Screenshot of Deadline Calculator CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix L - Page 20 Using Automatic Rules with CalendarRules.com CourtAlert case management is integrated with CarlendarRules.com court rules and laws. Figure 16 Screenshot of General tab to Add Case Header Procedure: 1. Users are required to enter two data elements: a. Trigger event – users unable to find the Trigger Event on the pulldown may click on ‘Search’ to find the Triggering Event. Results include Triggering Events that have any part of the searched term. b. Trigger Date 2. Click on ‘Go’ button 3. The system automatically pulls the rules in real-time from CalendarRules.com and populates the bottom field 4. The user may deselect the deadlines suggested by CalendarRules 5. Click the ‘select’ button to add the selected deadlines. Calendar Rules Explorer You can user the Rule Explorer feature to “test” the outcome of a trigger Procuedure: 1) From the Home Ribbon select Rule Explorer CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix L - Page 21 2) Select the Jurisdiction, Triggering Event and Trigger Date 3) Click Go 4) View the results on the resulting “Deadlines” tab you can view Export the results of a Rules Explorer When using Rules Explorer it is often useful to explort the results. Procedure: 1) See the above procedure on calculating deadlines using rules. 2) On the Deadlines tab, click “Export to Excel” CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix L - Page 22 3) This will open an Excel with the requested Deadlines. 4) To correct The Reminder Date in the first column a. Select the Reminder Date Column b. Use the Format/Number drop down (or hit CTRL+1) to format it as a “Short Date”. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix L - Page 23 Adjourning Diaries Often the need arises to Adjourn or Continue events. This section describes how to adjourn several dates at the same time. Mass Adjournment 1. Docket the notice of the date change. Follow the steps to Docket “De-Novo” or Docket from reconciliation to record the document that relates to the adjournment. 2. Click on the Diary Tab. 3. Click on "Adjourn Diaries" as seen in the screenshot below 4. Next you are Presented with two methods of adjourning: “Adjourn by hand” (step 5, next page) or “Adjourn using Rules” (step 6, below) CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix L - Page 24 5. “Adjourn by Hand” - revising the dates manually. For example, you have a scheduling order with new dates that you would like to Adjourn, use Adjourn by hand. a. Click on the “Adjourn by hand” button b. Optionally, use the provided filters to identify the diaries you would like to filter. You may find it helpful to sort by date, or by Docket#. i. Tip, CTRL+F will open a Find Dialog which can help find your diary c. Check off the dates that you would like to adjourn in the “Selected” column (the first columns d. Enter the “Adjourn To Date” (column 2) and “Adjourn To Time” (column 3) as follows: i. Enter in a date by typing it in or, ii. Click the down arrow to select it from the calendar, or, iii. Calculate the date using the built in Calculator using the + Icon e. Click on the “Adjourn Selected Diaries” button to save those diaries. Figure 17 Adjourning using the Built-in Calculator – Follow the circled “clicks” above to adding 14 Calendar days from the original date. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix L - Page 25 6. “Adjourn Using Rules” - for deadlines originally calculated using Rules, the trigger and corresponding deadlines can be “Recalculated” using a new date as follows: a. Click on the “Adjourn using Rules” button b. Identify the rows for the trigger you previously used c. Enter in the “Adjourned to Date” and “Adjourn to Time” as appropriate for the new triggering event d. Click on “Go” e. This will re-calculate the events using the new trigger date. f. Note - each deadline is lined up with the original diaries. Previously unselected diaries will remain unselected. 7. Click on the “Adjourn Selected Diaries” button to save those diaries Figure 18 Diaries calculated from a new Trigger date Figure 19 - Adjourn using Rules. Follow the circled “clicks” above to re-calculate the trigger using a new trigger date. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix L - Page 26 Steps to Adjourn a Single Diary This method of adjournment is less effective when docketing with reconciliation. You may consider using the Mass-Adjournment feature above even for a single diary. The method described below allow you to create adjourn a single entry. 1) Identify the Diary to be adjourn Docketing screen is arranged into two sections (sub screens) – Docket and Diary for easy access. a) Select the Diary Screen in docketing section b) Navigate to the Diaries for the Case/Adjourn section c) Locate the Diary to be adjourned By default, the date selection to filter all available diaries for the case will be Today's date. Click on Show button, to display all diaries for the particular date selected in "Diary Alerts for" calendar selection. Click on Show Future button to view diaries of the selected date or future. Click on Show All button to list all diaries of the case for any date. Use Filter option to filter the diaries based on a word in Diary subject, out of entire diary list. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix L - Page 27 d) Select the Diary to be adjourned and click on Adjourn button. 2) Identify the Docket to Associate In this step you decide whether to save the new diary created by adjourning an existing diary to be linked to a brand new Docket or to an existing Docket. Clicking on Adjourn button in last step of section 2.1 would prompt the following pop-up screen. If you select Yes in this prompt, continue reading section 2.2.2. If you choose not to create a new docket by clicking on No, read 2.2.1 3) Adjourn the diary and attach to an existing Docket a) Select the docket to which the new diary should be associated, by clicking on the docket item in tabular display and click on Use the Selected Docket button. b) If the list is too long and you know the Sequence number of the Docket (or the one close to it), to which the new diary should be associated, enter that Docket sequence number in the input box on the screen and click on Use this Docket Seq. Number button to move the docket selection in the list to the chosen Docket sequence number. Click on Use the Selected Docket button to finish the docket selection. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix L - Page 28 4) Adjourn the diary and attach to a new Docket Now Select the new date (or leave the date blank and select Sine Die option to adjourn to Sine Die) and make any other necessary change in Diary text, time, recipients, Part, Room or Judge and click on Save button. If you chose to create a new docket with the new diary, after saving the new diary, click on Back to Docket button and make any necessary changes to the new docket and Save the docket. Adjournment Trail Indication that a diary was adjourned can be found in several ways. 3.1 Changes in Diary Text Diary text changes in both the source diary and the new diary created by adjourn process. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix L - Page 29 Source diary text will have the following additional text appended – "[this has been adjourned to 03/31/2011]" , where 03/31/2011 is the diary date for the new diary created by adjourn process. The newly created diary of 03/31/2011 in the above example will have the following text appended by the program. "[last adjourned from 3/28/2011], (total number of days adjourned:3)" (Please note that this text is editable by the user and if edited, should not be considered for identifying the adjourn trail) 3.2 Changes in Diary list display In the diary list display in "Other Diaries for This Docket" section, if you scroll the list to the right, you can see the additional detail such as the Docket sequence number and diary sequence number of the adjourn trail. Private Diaries Diaries / Events can be marked as Private. These diaries are intended for the MAO / Docketing team only and limits the attorneys access to the diary. 1. Private Diaries are not generally included sent in Attorney Tickler Reports. The exception to this is a private diary for a docketing team member – those are included. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix L - Page 30 Adding a New Case A new file/case is used to open a new collection of events. The case will begin with the Case Initialization Submissions (CIS) or any other method of case intake. The case will be updated as the case moves to other Divisions Adding a new case into CourtAlert Case Management requires the user to fill in four tabs. Users are encouraged to include as much information as they have available to allow for future inquiry into the case by each data element. Adding New Cases - General Tab Figure 15, below, shows the General tab for the basic header when adding a case. This tab enables the user to input the following data elements: • Forum, Venue and Location, if applicable • Index/File Number • Main Parties or name of the case • Main case type/Status. For example: “Waiting Approval for Investigators Supervisor” • The case nickname (Referred to as) • Lead case, if applicable • Related Cases in the CourtAlert Case Management System, if applicable. Once cases are marked as related in the CourtAlert Case Management, users are reminded to update the dockets of related cases when creating dockets. This feature is helpful in when the same party is involved in more than one case. Helpful for docketing appeal cases. • Cases in Other Divisions in the CourtAlert Case Management system, if applicable • Other reference number(s) • Case Status – Open or Closed • Internal Number assigned by the DOC, formatted differently by each Division and automatically assigned. • Tribunal/Judge(s) assigned to the case • Division or Unit (“Office”) Assigned to the Case CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix L - Page 31 Figure 20 Screenshot of General tab to Add Case Header Adding New Cases – Staff Tab Figure 16 is the Staff Tab with respect to adding a new case. This tab enables users to input the following data elements: • Assign a case team • Identify Individual Staff members assigned to this case: For each staff member assigned, the user will determine o Title of the user (associate, paralegal, etc.) o Start Date: Date assigned to the case o Termination Date: date removed from the case o Indicator of the status of the user as the Case Manager o Notification preference for the user as it pertains to this case, including whether or not user seeks to receive dockets and/or receive Diary Alerts. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix L - Page 32 Figure 21 Screenshot of Staff tab to Add Case Header CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix L - Page 33 Adding New Cases - Parties Tab Figures 18 and 19 are screen shots of the two tabs pertaining to Parties in the matter. This tab enables users to input the following data elements: • All named parties • Full Title of the Party • Party Type (Plaintiff, Defendant, Appellant, etc.) • The Union Attorney, firm, attorney and contact information for those representing each party Figure 22 First of two screen shots showing the data elements for ‘Parties’ CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix L - Page 34 Figure 23 Second of two screen shots showing the data elements for ‘Parties’ CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix L - Page 35 Adding New Cases – Additional Information Tab Figure 20 is a screen shot of the Additional Information Tab. This tab enables users to input the following data elements: • Room/Part in the court where this case is located • Case End Date – if the case is closed • Notes and Comments – this field is used for internal workflow notes and other case related comments • Case Classifications – user has the ability to assign multiple classifications to a case. Selecting classification is important for knowledge management and reference purposes. This feature can be an important tool with respect to report generation. For example, this feature enables the running of a report on all cases in the CourtAlert Case Management system that relate to a specific classification. More details on this function are provided in the ‘Extra Features’ section of this proposal. • Conflict Checking – The system provides extensive permission support, which determines if a user is permitted to access/view any given function. In addition, this area allows users to exclude specific users from accessing a given case. A user that is conflicted out of a case will never see the case information, cannot access the case from the Inquiry Module, will not see the case on the firm wide calendar and will never receive CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix L - Page 36 notifications about the case. Figure 24 Additional Information tab, including Case Classifications and Conflict Check CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix L - Page 37 CHANGE HISTORY 2019-01-31 – ADDED CALENDAR RULE EXPORT EXAMPLE CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix L - Page 38 9/13/2019 Azure SQL Database automatic, geo-redundant backups | Microsoft Docs https://docs.microsoft.com/en-us/azure/sql-database/sql-database-automated-backups 1/8 Automated backups 08/21/2019 • 9 minutes to read • +14 In this article What is a SQL Database backup How long are backups kept How often do backups happen Storage costs Are backups encrypted How does Microsoft ensure backup integrity How do automated backups impact compliance How to change the PITR backup retention period Next steps SQL Database automatically creates the database backups that are kept between 7 and 35 days, and uses Azure read-access geo-redundant storage (RA-GRS) to ensure that they are preserved even if the data center is unavailable. These backups are created automatically. Database backups are an essential part of any business continuity and disaster recovery strategy because they protect your data from accidental corruption or deletion. If your security rules require that your backups are available for an extended period of time (up to 10 years), you can configure a long-term retention on Singleton databases and Elastic pools. What is a SQL Database backup SQL Database uses SQL Server technology to create full backups every week, differential backups every 12 hours, and transaction log backups every 5-10 minutes. The backups are stored in RA-GRS storage blobs that are replicated to a paired data center for protection against a data center outage. When you restore a database, the service figures out which full, differential, and transaction log backups need to be restored. You can use these backups to: Restore an existing database to a point-in-time in the past within the retention period using the Azure portal, Azure PowerShell, Azure CLI, or REST API. In Single database and Elastic pools, ７ Note This article provides steps for how to delete personal data from the device or service and can be used to support your obligations under the GDPR. If you’re looking for general info about GDPR, see the GDPR section of the Service Trust portal. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Exhibit O Appendix 6 - Page 1 9/13/2019 Azure SQL Database automatic, geo-redundant backups | Microsoft Docs https://docs.microsoft.com/en-us/azure/sql-database/sql-database-automated-backups 2/8 this operation will create a new database in the same server as the original database. In Managed Instance, this operation can create a copy of the database or same or different Managed Instance under the same subscription. Change Backup Retention Period between 7 to 35 days to configure your backup policy. Change long-term retention policy up to 10 years on Single Database and Elastic Pools using the Azure portal or Azure PowerShell. Restore a deleted database to the time it was deleted or anytime within the retention period. The deleted database can only be restored in the same logical server or Managed Instance where the original database was created. Restore a database to another geographical region. Geo-restore allows you to recover from a geographic disaster when you cannot access your server and database. It creates a new database in any existing server anywhere in the world. Restore a database from a specific long-term backup on Single Database or Elastic Pool if the database has been configured with a long-term retention policy (LTR). LTR allows you to restore an old version of the database using the Azure portal or Azure PowerShell to satisfy a compliance request or to run an old version of the application. For more information, see Long-term retention. To perform a restore, see restore database from backups. You can try some of these operations using the following examples: The Azure portal Azure PowerShell Change backup retention Single Database Managed Instance Single Database Managed Instance Change Long-term backup retention Single database Managed Instance - N/A Single Database Managed Instance - N/A Restore database from point-in-time Single database Single database Managed Instance Restore deleted database Single database Single database Managed Instance Restore database from Azure Blob Storage Single database - N/A Managed Instance - N/A Single database - N/A Managed Instance ７ Note In Azure storage, the term replication refers to copying files from one location to another. SQL's database replication refers to keeping multiple secondary databases synchronized with a primary database. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Exhibit O Appendix 6 - Page 2 9/13/2019 Azure SQL Database automatic, geo-redundant backups | Microsoft Docs https://docs.microsoft.com/en-us/azure/sql-database/sql-database-automated-backups 3/8 How long are backups kept All Azure SQL databases (single, pooled, and managed instance databases) have a default backup retention period of seven days. You can change backup retention period up to 35 days. If you delete a database, SQL Database will keep the backups in the same way it would for an online database. For example, if you delete a Basic database that has a retention period of seven days, a backup that is four days old is saved for three more days. If you need to keep the backups for longer than the maximum retention period, you can modify the backup properties to add one or more long-term retention periods to your database. For more information, see Long-term retention. How often do backups happen Backups for point-in-time restore SQL Database supports self-service for point-in-time restore (PITR) by automatically creating full backup, differential backups, and transaction log backups. Full database backups are created weekly, differential database backups are generally created every 12 hours, and transaction log backups are generally created every 5 - 10 minutes, with the frequency based on the compute size and amount of database activity. The first full backup is scheduled immediately after a database is created. It usually completes within 30 minutes, but it can take longer when the database is of a significant size. For example, the initial backup can take longer on a restored database or a database copy. After the first full backup, all further backups are scheduled automatically and managed silently in the background. The exact timing of all database backups is determined by the SQL Database service as it balances the overall system workload. You cannot change or disable the backup jobs. The PITR backups are geo-redundant and protected by Azure Storage cross-regional replication For more information, see Point-in-time restore Backups for long-term retention Single and pooled databases offer the option of configuring long-term retention (LTR) of full backups for up to 10 years in Azure Blob storage. If LTR policy is enabled, the weekly full backups are ） Important If you delete the Azure SQL server that hosts SQL databases, all elastic pools and databases that belong to the server are also deleted and cannot be recovered. You cannot restore a deleted server. But if you configured long-term retention, the backups for the databases with LTR will not be deleted and these databases can be restored. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Exhibit O Appendix 6 - Page 3 9/13/2019 Azure SQL Database automatic, geo-redundant backups | Microsoft Docs https://docs.microsoft.com/en-us/azure/sql-database/sql-database-automated-backups 4/8 automatically copied to a different RA-GRS storage container. To meet different compliance requirement, you can select different retention periods for weekly, monthly and/or yearly backups. The storage consumption depends on the selected frequency of backups and the retention period(s). You can use the LTR pricing calculator to estimate the cost of LTR storage. Like PITR, the LTR backups are geo-redundant and protected by Azure Storage cross-regional replication. For more information, see Long-term backup retention. Storage costs For single databases, a minimum backup storage amount equal to 100% of database size is provided at no extra charge. For elastic pools, a minimum backup storage amount equal to 100% of the allocated data storage for the pool is provided at no extra charge. Additional consumption of backup storage will be charged in GB/month. This additional consumption will depend on the workload and size of the individual databases. For more information about storage prices, see the pricing page. Are backups encrypted If your database is encrypted with TDE, the backups are automatically encrypted at rest, including LTR backups. When TDE is enabled for an Azure SQL database, backups are also encrypted. All new Azure SQL databases are configured with TDE enabled by default. For more information on TDE, see Transparent Data Encryption with Azure SQL Database. How does Microsoft ensure backup integrity On an ongoing basis, the Azure SQL Database engineering team automatically tests the restore of automated database backups of databases placed in Logical servers and Elastic pools (this is not available in Managed Instance). Upon point-in-time restore, databases also receive integrity checks using DBCC CHECKDB. Managed Instance takes automatic initial backup with CHECKSUM of the databases restored using native RESTORE command or Data Migration Service once the migration is completed. Any issues found during the integrity check will result in an alert to the engineering team. For more information about data integrity in Azure SQL Database, see Data Integrity in Azure SQL Database. How do automated backups impact compliance CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Exhibit O Appendix 6 - Page 4 9/13/2019 Azure SQL Database automatic, geo-redundant backups | Microsoft Docs https://docs.microsoft.com/en-us/azure/sql-database/sql-database-automated-backups 5/8 When you migrate your database from a DTU-based service tier with the default PITR retention of 35 days, to a vCore-based service tier, the PITR retention is preserved to ensure that your application's data recovery policy is not compromised. If the default retention doesn't meet your compliance requirements, you can change the PITR retention period using PowerShell or REST API. For more information, see Change Backup Retention Period. How to change the PITR backup retention period You can change the default PITR backup retention period using the Azure portal, PowerShell, or the REST API. The supported values are: 7, 14, 21, 28 or 35 days. The following examples illustrate how to change PITR retention to 28 days. Change PITR backup retention period using the Azure portal To change the PITR backup retention period using the Azure portal, navigate to the server object whose retention period you wish to change within the portal and then select the appropriate option based on which server object you're modifying. Change PITR for a SQL Database server ７ Note This article provides steps for how to delete personal data from the device or service and can be used to support your obligations under the GDPR. If you’re looking for general info about GDPR, see the GDPR section of the Service Trust portal. ２ Warning If you reduce the current retention period, all existing backups older than the new retention period are no longer available. If you increase the current retention period, SQL Database will keep the existing backups until the longer retention period is reached. ７ Note These APIs will only impact the PITR retention period. If you configured LTR for your database, it will not be impacted. For more information about how to change the LTR retention period(s), see Long-term retention. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Exhibit O Appendix 6 - Page 5 9/13/2019 Azure SQL Database automatic, geo-redundant backups | Microsoft Docs https://docs.microsoft.com/en-us/azure/sql-database/sql-database-automated-backups 6/8 Change PITR for a Managed Instance Change PITR backup retention period using PowerShell ７ Note This article has been updated to use the new Azure PowerShell Az module. You can still use the AzureRM module, which will continue to receive bug fixes until at least December 2020. To learn CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Exhibit O Appendix 6 - Page 6 9/13/2019 Azure SQL Database automatic, geo-redundant backups | Microsoft Docs https://docs.microsoft.com/en-us/azure/sql-database/sql-database-automated-backups 7/8 PowerShell ＝Copy Change PITR retention period using REST API Sample Request HTTP ＝Copy Request Body JSON ＝Copy Sample Response Status code: 200 JSON ＝Copy more about the new Az module and AzureRM compatibility, see Introducing the new Azure PowerShell Az module. For Az module installation instructions, see Install Azure PowerShell. ） Important The PowerShell Azure Resource Manager module is still supported by Azure SQL Database, but all future development is for the Az.Sql module. For these cmdlets, see AzureRM.Sql. The arguments for the commands in the Az module and in the AzureRm modules are substantially identical. Set-AzSqlDatabaseBackupShortTermRetentionPolicy -ResourceGroupName resourceGroup - ServerName testserver -DatabaseName testDatabase -RetentionDays 28 PUT https://management.azure.com/subscriptions/00000000-1111-2222-3333- 444444444444/resourceGroups/resourceGroup/providers/Microsoft.Sql/servers/testserver/data bases/testDatabase/backupShortTermRetentionPolicies/default?api-version=2017-10-01- preview { "properties":{ "retentionDays":28 } } { "id": "/subscriptions/00000000-1111-2222-3333- 444444444444/providers/Microsoft.Sql/resourceGroups/resourceGroup/servers/testserver/data bases/testDatabase/backupShortTermRetentionPolicies/default", CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Exhibit O Appendix 6 - Page 7 9/13/2019 Azure SQL Database automatic, geo-redundant backups | Microsoft Docs https://docs.microsoft.com/en-us/azure/sql-database/sql-database-automated-backups 8/8 Is this page helpful? Yes No For more information, see Backup Retention REST API. Next steps Database backups are an essential part of any business continuity and disaster recovery strategy because they protect your data from accidental corruption or deletion. To learn about the other Azure SQL Database business continuity solutions, see Business continuity overview. To restore to a point in time using the Azure portal, see restore database to a point in time using the Azure portal. To restore to a point in time using PowerShell, see restore database to a point in time using PowerShell. To configure, manage, and restore from long-term retention of automated backups in Azure Blob storage using the Azure portal, see Manage long-term backup retention using the Azure portal. To configure, manage, and restore from long-term retention of automated backups in Azure Blob storage using PowerShell, see Manage long-term backup retention using PowerShell. "name": "default", "type": "Microsoft.Sql/resourceGroups/servers/databases/backupShortTermRetentionPolicies", "properties": { "retentionDays": 28 } } CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Exhibit O Appendix 6 - Page 8 9/13/2019 What is Privileged Identity Management? - Azure Active Directory | Microsoft Docs https://docs.microsoft.com/en-us/azure/active-directory/privileged-identity-management/pim-configure 1/5 What is Azure AD Privileged Identity Management? 04/08/2019 • 4 minutes to read • In this article Why should I use PIM? What can I do with PIM? Terminology What does PIM look like? Who can do what in PIM? Scenarios License requirements Next steps Azure Active Directory (Azure AD) Privileged Identity Management (PIM) is a service that enables you to manage, control, and monitor access to important resources in your organization. This includes access to resources in Azure AD, Azure resources, and other Microsoft Online Services like Office 365 or Microsoft Intune. Why should I use PIM? Organizations want to minimize the number of people who have access to secure information or resources, because that reduces the chance of a malicious actor getting that access, or an authorized user inadvertently impacting a sensitive resource. However, users still need to carry out privileged operations in Azure AD, Azure, Office 365, or SaaS apps. Organizations can give users just-in-time (JIT) privileged access to Azure resources and Azure AD. There is a need for oversight for what those users are doing with their administrator privileges. PIM helps to mitigate the risk of excessive, unnecessary, or misused access rights. What can I do with PIM? PIM essentially helps you manage the who, what, when, where, and why for resources that you care about. Here are some of the key features of PIM: Provide just-in-time privileged access to Azure AD and Azure resources Assign time-bound access to resources using start and end dates Require approval to activate privileged roles Enforce multi-factor authentication to activate any role Use justification to understand why users activate CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Exhibit O Appendix 5 - Page 1 9/13/2019 What is Privileged Identity Management? - Azure Active Directory | Microsoft Docs https://docs.microsoft.com/en-us/azure/active-directory/privileged-identity-management/pim-configure 2/5 Get notifications when privileged roles are activated Conduct access reviews to ensure users still need roles Download audit history for internal or external audit Terminology To better understand PIM and its documentation, you should review the following terms. Term or concept Role assignment category Description eligible Type A role assignment that requires a user to perform one or more actions to use the role. If a user has been made eligible for a role, that means they can activate the role when they need to perform privileged tasks. There's no difference in the access given to someone with a permanent versus an eligible role assignment. The only difference is that some people don't need that access all the time. active Type A role assignment that doesn't require a user to perform any action to use the role. Users assigned as active have the privileges assigned to the role. activate The process of performing one or more actions to use a role that a user is eligible for. Actions might include performing a multi-factor authentication (MFA) check, providing a business justification, or requesting approval from designated approvers. assigned State A user that has an active role assignment. activated State A user that has an eligible role assignment, performed the actions to activate the role, and is now active. Once activated, the user can use the role for a preconfigured period-of-time before they need to activate again. permanent eligible Duration A role assignment where a user is always eligible to activate the role. permanent active Duration A role assignment where a user can always use the role without performing any actions. expire eligible Duration A role assignment where a user is eligible to activate the role within a specified start and end date. expire active Duration A role assignment where a user can use the role without performing any actions within a specified start and end date. just-in- time (JIT) access A model in which users receive temporary permissions to perform privileged tasks, which prevents malicious or unauthorized users from gaining access after the permissions have expired. Access is granted only when users need it. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Exhibit O Appendix 5 - Page 2 9/13/2019 What is Privileged Identity Management? - Azure Active Directory | Microsoft Docs https://docs.microsoft.com/en-us/azure/active-directory/privileged-identity-management/pim-configure 3/5 Term or concept Role assignment category Description principle of least privilege access A recommended security practice in which every user is provided with only the minimum privileges needed to accomplish the tasks they are authorized to perform. This practice minimizes the number of Global Administrators and instead uses specific administrator roles for certain scenarios. What does PIM look like? Once you set up PIM, you'll see Tasks, Manage, and Activity options in the left navigation menu. As an administrator, you'll choose between managing Azure AD roles and Azure resource roles. When you choose the type of roles to manage, you see a similar set of options for that role type. Who can do what in PIM? CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Exhibit O Appendix 5 - Page 3 9/13/2019 What is Privileged Identity Management? - Azure Active Directory | Microsoft Docs https://docs.microsoft.com/en-us/azure/active-directory/privileged-identity-management/pim-configure 4/5 If you're the first person to use PIM, you are automatically assigned the Security Administrator and Privileged Role Administrator roles in the directory. For Azure AD roles, only a user who is in the Privileged Role Administrator role can manage assignments for other administrators in PIM. You can grant access to other administrators to manage PIM. Global Administrators, Security Administrators, and Security Readers can view assignments to Azure AD roles in PIM. For Azure resource roles, only a subscription administrator, a resource Owner, or a resource User Access Administrator can manage assignments for other administrators in PIM. Users who are Privileged Role Administrators, Security Administrators, or Security Readers do not by default have access to view assignments to Azure resource roles in PIM. Scenarios PIM supports the following scenarios: As a Privileged Role Administrator you can: Enable approval for specific roles Specify approver users and/or groups to approve requests View request and approval history for all privileged roles As an approver, you can: View pending approvals (requests) Approve or reject requests for role elevation (single and/or bulk) Provide justification for my approval/rejection As an eligible role user, you can: Request activation of a role that requires approval View the status of your request to activate Complete your task in Azure AD if activation was approved License requirements Using this feature requires an Azure AD Premium P2 license. To find the right license for your requirements, see Comparing generally available features of the Free, Basic, and Premium editions. For information about licenses for users, see License requirements to use PIM. Next steps License requirements to use PIM CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Exhibit O Appendix 5 - Page 4 9/13/2019 What is Privileged Identity Management? - Azure Active Directory | Microsoft Docs https://docs.microsoft.com/en-us/azure/active-directory/privileged-identity-management/pim-configure 5/5 Is this page helpful? Yes No Securing privileged access for hybrid and cloud deployments in Azure AD Deploy PIM CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Exhibit O Appendix 5 - Page 5 CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Exhbit O Appendix 4 - Page 1 CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Exhbit O Appendix 4 - Page 2 CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Exhbit O Appendix 4 - Page 3 CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Exhbit O Appendix 4 - Page 4 CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Exhbit O Appendix 4 - Page 5 9/13/2019 High availability - Azure SQL Database service | Microsoft Docs https://docs.microsoft.com/en-us/azure/sql-database/sql-database-high-availability#zone-redundant-configuration 1/6 High-availability and Azure SQL Database 06/09/2019 • 6 minutes to read • +6 In this article Basic, Standard, and General Purpose service tier availability Premium and Business Critical service tier availability Zone redundant configuration Accelerated Database Recovery (ADR) Conclusion Next steps The goal of the High Availability architecture in Azure SQL Database is to guarantee that your database is up and running 99.99% of time, without worrying about the impact of maintenance operations and outages. Azure automatically handles critical servicing tasks, such as patching, backups, Windows and SQL upgrades, as well as unplanned events such as underlying hardware, software or network failures. When the underlying SQL instance is patched or fails over, the downtime is not noticeable if you employ retry logic in your app. Azure SQL Database can quickly recover even in the most critical circumstances ensuring that your data is always available. The high availability solution is designed to ensure that committed data is never lost due to failures, that maintenance operations do not affect your workload, and that the database will not be a single point of failure in your software architecture. There are no maintenance windows or downtimes that should require you to stop the workload while the database is upgraded or maintained. There are two high-availability architectural models that are used in Azure SQL Database: Standard availability model that is based on a separation of compute and storage. It relies on high availability and reliability of the remote storage tier. This architecture targets budget- oriented business applications that can tolerate some performance degradation during maintenance activities. Premium availability model that is based on a cluster of database engine processes. It relies on the fact that there is always a quorum of available database engine nodes. This architecture targets mission critical applications with high IO performance, high transaction rate and guarantees minimal performance impact to your workload during maintenance activities. Azure SQL Database runs on the latest stable version of SQL Server Database Engine and Windows OS, and most users would not notice that upgrades are performed continuously. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Exhibit O Appendix 3 - Page 1 9/13/2019 High availability - Azure SQL Database service | Microsoft Docs https://docs.microsoft.com/en-us/azure/sql-database/sql-database-high-availability#zone-redundant-configuration 2/6 Basic, Standard, and General Purpose service tier availability These service tiers leverage the standard availability architecture. The following figure shows four different nodes with the separated compute and storage layers. The standard availability model includes two layers: A stateless compute layer that runs the sqlserver.exe process and contains only transient and cached data on the attached SSD, such as TempDB, model database, plan cache, buffer pool and column store pool. This stateless node is operated by Azure Service Fabric that initializes sqlserver.exe, controls health of the node, and performs failover to another node if necessary. A stateful data layer with the database files (.mdf/.ldf) that are stored in Azure Blob storage. Azure blob storage has built-in data availability and redundancy feature. It guarantees that every record in the log file or page in the data file will be preserved even if SQL Server process crashes. Whenever the database engine or the operating system is upgraded, or a failure is detected, Azure Service Fabric will move the stateless SQL Server process to another stateless compute node with CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Exhibit O Appendix 3 - Page 2 9/13/2019 High availability - Azure SQL Database service | Microsoft Docs https://docs.microsoft.com/en-us/azure/sql-database/sql-database-high-availability#zone-redundant-configuration 3/6 sufficient free capacity. Data in Azure Blob storage is not affected by the move, and the data/log files are attached to the newly initialized SQL Server process. This process guarantees 99.99% availability, but a heavy workload may experience some performance degradation during the transition since the new SQL Server instance starts with cold cache. Premium and Business Critical service tier availability Premium and Business Critical service tiers leverage the Premium availability model, which integrates compute resources (SQL Server Database Engine process) and storage (locally attached SSD) on a single node. High availability is achieved by replicating both compute and storage to additional nodes creating a three to four-node cluster. The underlying database files (.mdf/.ldf) are placed on the attached SSD storage to provide very low latency IO to your workload. High availability is implemented using a technology similar to SQL Server Always On Availability Groups. The cluster includes a single primary replica (SQL Server process) that is accessible for read-write customer workloads, and up to three secondary replicas (compute and storage) containing copies of data. The primary node constantly pushes changes to the secondary nodes in order and ensures that the data is synchronized to at least one secondary replica before committing each transaction. This process guarantees that if the primary node crashes for any reason, there is always a fully synchronized node to fail over to. The failover is initiated by the Azure ServiceCourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Exhibit O Appendix 3 - Page 3 9/13/2019 High availability - Azure SQL Database service | Microsoft Docs https://docs.microsoft.com/en-us/azure/sql-database/sql-database-high-availability#zone-redundant-configuration 4/6 Fabric. Once the secondary replica becomes the new primary node, another secondary replica is created to ensure the cluster has enough nodes (quorum set). Once failover is complete, SQL connections are automatically redirected to the new primary node. As an extra benefit, the premium availability model includes the ability to redirect read-only SQL connections to one of the secondary replicas. This feature is called Read Scale-Out. It provides 100% additional compute capacity at no extra charge to off-load read-only operations, such as analytical workloads, from the primary replica. Zone redundant configuration By default, the cluster of nodes for the premium availability model is created in the same datacenter. With the introduction of Azure Availability Zones, SQL Database can place different replicas in the cluster to different availability zones in the same region. To eliminate a single point of failure, the control ring is also duplicated across multiple zones as three gateway rings (GW). The routing to a specific gateway ring is controlled by Azure Traffic Manager (ATM). Because the zone redundant configuration in the Premium or Business Critical service tiers does not create additional database redundancy, you can enable it at no extra cost. By selecting a zone redundant configuration, you can make your Premium or Business Critical databases resilient to a much larger set of failures, including catastrophic datacenter outages, without any changes to the application logic. You can also convert any existing Premium or Business Critical databases or pools to the zone redundant configuration. Because the zone redundant databases have replicas in different datacenters with some distance between them, the increased network latency may increase the commit time and thus impact the performance of some OLTP workloads. You can always return to the single-zone configuration by disabling the zone redundancy setting. This process is an online operation similar to the regular service tier upgrade. At the end of the process, the database or pool is migrated from a zone redundant ring to a single zone ring or vice versa. The zone redundant version of the high availability architecture is illustrated by the following diagram: ） Important Zone redundant databases and elastic pools are currently only supported in the Premium and Business Critical service tiers in select regions. When using the Business Critical tier, zone redundant configuration is only available when the Gen5 compute hardware is selected. For up to date information about the regions that support zone redundant databases, see Services support by region. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Exhibit O Appendix 3 - Page 4 9/13/2019 High availability - Azure SQL Database service | Microsoft Docs https://docs.microsoft.com/en-us/azure/sql-database/sql-database-high-availability#zone-redundant-configuration 5/6 Accelerated Database Recovery (ADR) Accelerated Database Recovery (ADR) is a new SQL database engine feature that greatly improves database availability, especially in the presence of long running transactions. ADR is currently available for single databases, elastic pools, and Azure SQL Data Warehouse. Conclusion Azure SQL Database features a built-in high availability solution, that is deeply integrated with the Azure platform. It is dependent on Service Fabric for failure detection and recovery, on Azure Blob storage for data protection, and on Availability Zones for higher fault tolerance. In addition, Azure SQL database leverages the Always On Availability Group technology from SQL Server for replication and failover. The combination of these technologies enables applications to fully realize the benefits of a mixed storage model and support the most demanding SLAs. Next steps Learn about Azure Availability Zones Learn about Service Fabric Learn about Azure Traffic Manager For more options for high availability and disaster recovery, see Business ContinuityCourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Exhibit O Appendix 3 - Page 5 9/13/2019 High availability - Azure SQL Database service | Microsoft Docs https://docs.microsoft.com/en-us/azure/sql-database/sql-database-high-availability#zone-redundant-configuration 6/6 Is this page helpful? Yes No CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Exhibit O Appendix 3 - Page 6 9/13/2019 Introduction to web application firewall for Azure Application Gateway | Microsoft Docs https://docs.microsoft.com/en-us/azure/application-gateway/waf-overview 1/8 Web application firewall for Azure Application Gateway 05/21/2019 • 7 minutes to read • +1 In this article Benefits Features Application Gateway WAF SKU pricing Next steps Azure Application Gateway offers a web application firewall (WAF) that provides centralized protection of your web applications from common exploits and vulnerabilities. Web applications are increasingly targeted by malicious attacks that exploit commonly known vulnerabilities. SQL injection and cross-site scripting are among the most common attacks. Preventing such attacks in application code is challenging. It can require rigorous maintenance, patching, and monitoring at multiple layers of the application topology. A centralized web application firewall helps make security management much simpler. A WAF also gives application administrators better assurance of protection against threats and intrusions. A WAF solution can react to a security threat faster by centrally patching a known vulnerability, instead of securing each individual web application. Existing application gateways can easily be converted into fire wall- enabled application gateways. The Application Gateway WAF is based on Core Rule Set (CRS) 3.0 or 2.2.9 from the Open Web Application Security Project (OWASP). The WAF automatically updates to include protection against new vulnerabilities, with no additional configuration needed. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Exhibit O Appendix 2 - Page 1 9/13/2019 Introduction to web application firewall for Azure Application Gateway | Microsoft Docs https://docs.microsoft.com/en-us/azure/application-gateway/waf-overview 2/8 Application Gateway operates as an application delivery controller (ADC). It offers Secure Sockets Layer (SSL) termination, cookie-based session affinity, round-robin load distribution, content-based routing, ability to host multiple websites, and security enhancements. Application Gateway security enhancements include SSL policy management and end-to-end SSL support. Application security is strengthened by WAF integration into Application Gateway. The combination protects your web applications against common vulnerabilities. And it provides an easy-to-configure central location to manage. Benefits This section describes the core benefits that Application Gateway and its WAF provide. Protection Protect your web applications from web vulnerabilities and attacks without modification to back-end code. Protect multiple web applications at the same time. An instance of Application Gateway can host of up to 100 websites that are protected by a web application firewall. Monitoring Monitor attacks against your web applications by using a real-time WAF log. The log is integrated with Azure Monitor to track WAF alerts and easily monitor trends. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Exhibit O Appendix 2 - Page 2 9/13/2019 Introduction to web application firewall for Azure Application Gateway | Microsoft Docs https://docs.microsoft.com/en-us/azure/application-gateway/waf-overview 3/8 The Application Gateway WAF is integrated with Azure Security Center. Security Center provides a central view of the security state of all your Azure resources. Customization You can customize WAF rules and rule groups to suit your application requirements and eliminate false positives. Features SQL-injection protection. Cross-site scripting protection. Protection against other common web attacks, such as command injection, HTTP request smuggling, HTTP response splitting, and remote file inclusion. Protection against HTTP protocol violations. Protection against HTTP protocol anomalies, such as missing host user-agent and accept headers. Protection against bots, crawlers, and scanners. Detection of common application misconfigurations (for example, Apache and IIS). Configurable request size limits with lower and upper bounds. Exclusion lists let you omit certain request attributes from a WAF evaluation. A common example is Active Directory-inserted tokens that are used for authentication or password fields. Core rule sets Application Gateway supports two rule sets, CRS 3.0 and CRS 2.2.9. These rules protect your web applications from malicious activity. The Application Gateway WAF comes preconfigured with CRS 3.0 by default. But you can choose to use CRS 2.2.9 instead. CRS 3.0 offers reduced false positives compared with CRS 2.2.9. You can also customize rules to suit your needs. The WAF protects against the following web vulnerabilities: SQL-injection attacks Cross-site scripting attacks Other common attacks, such as command injection, HTTP request smuggling, HTTP response splitting, and remote file inclusion HTTP protocol violations HTTP protocol anomalies, such as missing host user-agent and accept headers Bots, crawlers, and scanners Common application misconfigurations (for example, Apache and IIS) OWASP CRS 3.0 CRS 3.0 includes 13 rule groups, as shown in the following table. Each group contains multiple rules, which can be disabled.CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Exhibit O Appendix 2 - Page 3 9/13/2019 Introduction to web application firewall for Azure Application Gateway | Microsoft Docs https://docs.microsoft.com/en-us/azure/application-gateway/waf-overview 4/8 Rule group DescriptionRule group Description REQUEST-911-METHOD-ENFORCEMENT Lock-down methods (PUT, PATCH) REQUEST-913-SCANNER-DETECTION Protect against port and environment scanners REQUEST-920-PROTOCOL-ENFORCEMENT Protect against protocol and encoding issues REQUEST-921-PROTOCOL-ATTACK Protect against header injection, request smuggling, and response splitting REQUEST-930-APPLICATION-ATTACK-LFI Protect against file and path attacks REQUEST-931-APPLICATION-ATTACK-RFI Protect against remote file inclusion (RFI) attacks REQUEST-932-APPLICATION-ATTACK-RCE Protect again remote code execution attacks REQUEST-933-APPLICATION-ATTACK-PHP Protect against PHP-injection attacks REQUEST-941-APPLICATION-ATTACK-XSS Protect against cross-site scripting attacks REQUEST-942-APPLICATION-ATTACK-SQLI Protect against SQL-injection attacks REQUEST-943-APPLICATION-ATTACK-SESSION- FIXATION Protect against session-fixation attacks OWASP CRS 2.2.9 CRS 2.2.9 includes 10 rule groups, as shown in the following table. Each group contains multiple rules, which can be disabled. Rule group Description crs_20_protocol_violations Protect against protocol violations (such as invalid characters or a GET with a request body) crs_21_protocol_anomalies Protect against incorrect header information crs_23_request_limits Protect against arguments or files that exceed limitations crs_30_http_policy Protect against restricted methods, headers, and file types crs_35_bad_robots Protect against web crawlers and scanners crs_40_generic_attacks Protect against generic attacks (such as session fixation, remote file inclusion, and PHP injection) crs_41_sql_injection_attacks Protect against SQL-injection attacksCourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Exhibit O Appendix 2 - Page 4 9/13/2019 Introduction to web application firewall for Azure Application Gateway | Microsoft Docs https://docs.microsoft.com/en-us/azure/application-gateway/waf-overview 5/8 Rule group Description crs_41_xss_attacks Protect against cross-site scripting attacks crs_42_tight_security Protect against path-traversal attacks crs_45_trojans Protect against backdoor trojans WAF modes The Application Gateway WAF can be configured to run in the following two modes: Detection mode: Monitors and logs all threat alerts. You turn on logging diagnostics for Application Gateway in the Diagnostics section. You must also make sure that the WAF log is selected and turned on. Web application firewall doesn't block incoming requests when it's operating in Detection mode. Prevention mode: Blocks intrusions and attacks that the rules detect. The attacker receives a "403 unauthorized access" exception, and the connection is terminated. Prevention mode records such attacks in the WAF logs. Anomaly Scoring mode OWASP has two modes for deciding whether to block traffic: Traditional mode and Anomaly Scoring mode. In Traditional mode, traffic that matches any rule is considered independently of any other rule matches. This mode is easy to understand. But the lack of information about how many rules match a specific request is a limitation. So, Anomaly Scoring mode was introduced. It's the default for OWASP 3.x. In Anomaly Scoring mode, traffic that matches any rule isn't immediately blocked when the firewall is in Prevention mode. Rules have a certain severity: Critical, Error, Warning, or Notice. That severity affects a numeric value for the request, which is called the Anomaly Score. For example, one Warning rule match contributes 3 to the score. One Critical rule match contributes 5. Severity Value Critical 5 Error 4 Warning 3 Notice 2 There's a threshold of 5 for the Anomaly Score to block traffic. So, a single Critical rule match is enough for the Application Gateway WAF to block a request, even in Prevention mode. But one Warning rule match only increases the Anomaly Score by 3, which isn't enough by itself to block the traffic. ７ NoteCourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Exhibit O Appendix 2 - Page 5 9/13/2019 Introduction to web application firewall for Azure Application Gateway | Microsoft Docs https://docs.microsoft.com/en-us/azure/application-gateway/waf-overview 6/8 WAF monitoring Monitoring the health of your application gateway is important. Monitoring the health of your WAF and the applications that it protects is supported by integration with Azure Security Center, Azure Monitor, and Azure Monitor logs. Azure Monitor Application Gateway logs are integrated with Azure Monitor. This allows you to track diagnostic information, including WAF alerts and logs. You can access this capability on the Diagnostics tab in the Application Gateway resource in the portal or directly through Azure Monitor. To learn more about enabling logs, see Application Gateway diagnostics. Azure Security Center Security Center helps you prevent, detect, and respond to threats. It provides increased visibility into and control over the security of your Azure resources. Application Gateway is integrated with Security Center. Security Center scans your environment to detect unprotected web applications. It can recommend Application Gateway WAF to protect these vulnerable resources. You create the firewalls directly from Security Center. These WAF instances are integrated with Security Center. They send alerts and health information to Security Center for reporting. The message that's logged when a WAF rule matches traffic includes the action value "Blocked." But the traffic is actually only blocked for an Anomaly Score of 5 or higher. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Exhibit O Appendix 2 - Page 6 9/13/2019 Introduction to web application firewall for Azure Application Gateway | Microsoft Docs https://docs.microsoft.com/en-us/azure/application-gateway/waf-overview 7/8 Logging Application Gateway WAF provides detailed reporting on each threat that it detects. Logging is integrated with Azure Diagnostics logs. Alerts are recorded in the .json format. These logs can be integrated with Azure Monitor logs. JSON ＝Copy { "resourceId": "/SUBSCRIPTIONS/{subscriptionId}/RESOURCEGROUPS/{resourceGroupId}/PROVIDERS/MICROSOFT.NETWORK/AP PLICATIONGATEWAYS/{appGatewayName}", "operationName": "ApplicationGatewayFirewall", CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Exhibit O Appendix 2 - Page 7 9/13/2019 Introduction to web application firewall for Azure Application Gateway | Microsoft Docs https://docs.microsoft.com/en-us/azure/application-gateway/waf-overview 8/8 Is this page helpful? Yes No Application Gateway WAF SKU pricing The Application Gateway WAF is available under a new a SKU. This SKU is available only in the Azure Resource Manager provisioning model, not in the classic deployment model. Additionally, the WAF SKU comes only in medium and large Application Gateway instance sizes. All the limits for Application Gateway also apply to the WAF SKU. Pricing is based on an hourly gateway instance charge and a data-processing charge. Application Gateway pricing for the WAF SKU differs from standard SKU charges. Data-processing charges are the same. There are no per-rule or rule-group charges. You can protect multiple web applications behind the same web application firewall. You aren't charged for supporting multiple applications. Next steps See How to configure web application firewall on Application Gateway. "time": "2017-03-20T15:52:09.1494499Z", "category": "ApplicationGatewayFirewallLog", "properties": { "instanceId": "ApplicationGatewayRole_IN_0", "clientIp": "104.210.252.3", "clientPort": "4835", "requestUri": "/?a=%3Cscript%3Ealert(%22Hello%22);%3C/script%3E", "ruleSetType": "OWASP", "ruleSetVersion": "3.0", "ruleId": "941320", "message": "Possible XSS Attack Detected - HTML Tag Handler", "action": "Blocked", "site": "Global", "details": { "message": "Warning. Pattern match \" <(a|abbr|acronym|address|applet|area|audioscope|b|base|basefront|bdo|bgsound|big|blackface|blink |blockquote|body|bq|br|button|caption|center|cite|code|col|colgroup|comment|dd|del|dfn|dir|div|d l|dt|em|embed|fieldset|fn|font|form|frame|frameset|h1|head|h ...\" at ARGS:a.", "data": "Matched Data: <script> found within ARGS:a: <script>alert(\\x22hello\\x22); </script>", "file": "rules/REQUEST-941-APPLICATION-ATTACK-XSS.conf", "line": "865" } } } CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Exhibit O Appendix 2 - Page 8 © CourtAlert 2019 CourtAlert Data Governance Policy Version 4 Effective Date: 7/15/2018 The policy establishes proper standards to assure the quality and integrity of CourtAlert Client data. This policy also defines the roles and responsibilities of CourtAlert staff and its agents in relation to data access, retrieval, storage, destruction, and backup to ensure proper management and protection of data is maintained. 1. Background Information Court and client data is a strategic asset of CourtAlert (CA) and the appropriate governance for management and use of client data is critical to the CourtAlert's operations. Inappropriate governance can result in inefficiencies and exposes the CourtAlert to unwanted risk. A consistent, repeatable, and sustainable approach to data governance is therefore necessary in order to protect the security and integrity of the CourtAlert's data assets. 2. Policy Purpose The purpose of the Data Governance Policy is to: • Define the roles and responsibilities for different data usage and establish clear lines of accountability; • Develop best practices for effective data management and protection; • Protect the CourtAlert's data against internal and external threats (e.g. breach of privacy and confidentiality); • Ensure that the CourtAlert complies with applicable laws, regulations, and standards; and • Ensure that a data trail is effectively documented within the processes associated with accessing, retrieving, reporting, managing and storing of data. • Isolate Client Data for systems running by CourtAlert Hosted/Cloud Solutions 3. Policy Scope This policy applies to all client data used in the administration of the CourtAlert and all of its Organizational Units. It does not cover publicly available Court data unless specified as confidential client data. This policy covers, but is not limited to, institutional data in any form, including print, electronic, audio-visual, and backup and archived data. 4. Definition and Terms To establish operational definitions and facilitate ease of reference, the following terms are defined: CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix O - Exhibit 1 - Page 1 © CourtAlert 2019 Access is the right to read, copy or query data. Client Data is a general term used to refer to CourtAlert's information resources and administrative records, which can generally be assigned to one of four categories: • Public access data: data that is openly available to all staff and the general public. • Internal general data: data used for CourtAlert administration activities and not for external distribution unless otherwise authorized. • Internal protected data: data that is only available to staff with the required access in order to perform their assigned duties. • Internal restricted data: data that is of a sensitive or confidential nature and is restricted from general distribution. Special authorization must be approved before access or limited access is granted. • Client Protected Data: Law-Firm or protected data that is entered by the client for the operation of its business. Excluding information such as reference numbers and Attorney Codes entered on watchlists. Data Governance Hierarchy outlines the access rights, roles and responsibilities of CourtAlert staff in relation to the management and protection of data: • Data Steering Group is the Information Communication Technology Advisory Committee (ICTAC), which is a CourtAlert-wide committee, with members consisting of Data Trustees, Data Stewards and designated Data Users. ICTAC is responsible for approving the procedures related to the Data Governance Policy. ICTAC also assures appropriate data processes are used in all of the CourtAlert's data-driven decisions. • Data Trustee is a Member of the Senior Executive Group with planning and decision-making authority for CourtAlert's institutional data. The Data Trustees, as a group, are responsible for overseeing the continuous improvement of the CourtAlert's data governance and management. • Data Steward is a Member of the Executive, who oversees the capture, maintenance and dissemination of data for a particular Organizational Unit. Data Stewards are responsible for assuring the requirements of the Data Governance Policy and Procedures are followed within their Organizational Unit. • Data Manager has operational responsibilities in assisting Data Stewards with day-to-day data administration activities, including, but not limited to, develop, maintain, distribute and secure institutional data. Data Managers are expected to have high-level knowledge and expertise in the content of data within their responsible area. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix O - Exhibit 1 - Page 2 © CourtAlert 2019 • Data User is any staff or authorized agent, who accesses, inputs, amends, deletes, extracts and analyses data in order to carry out their day-to-day duties. Data Users are not generally involved in the governance process, but are responsible for the quality assurance of data. Data Management Life Cycle refers to the process for planning, creating, managing, storing, implementing, protecting, improving and disposing of all institutional data of the CourtAlert (see Appendix 1). Integrity or data integrity refers to the accuracy and consistency of data over its entire life-cycle. Member of the Executive is defined as the positions which normally report to the CEO, and having staffing and supervisory responsibilities. Quality or data quality refers to the validity, relevancy and currency of data. Security refers to the safety of CourtAlert data in relation to the following criteria: • Access control; • Authentication; • Effective incident detection, reporting and solution; • Physical and virtual security; and • Change management and version control. Senior Executive Group (SEG) is the peak senior strategic forum of CourtAlert. The SEG is chaired by the CEO with members consisting of the CIO and COO. 5. Policy Principles The following principles outline the minimum standards that guide the CourtAlert's data governance procedures and must be adhered to by all CourtAlert staff: 5.1 CourtAlert, rather than any individual or Organizational Unit, is the owner of all data, except Client . A Data Trustee has the responsibility for the management of data assigned within their portfolio. A Data Steering Group, in the form of the Information Communication Technology Advisory Committee is responsible for the overall management of the CourtAlert's data governance. 5.2 Every data source must have a Data Steward who is responsible for the quality and integrity, implementation and enforcement of data management within their Organizational Unit. Data Managers are responsible for ensuring effective local protocols are in place to guide the appropriate use of data. 5.3 Access to, and use of, institutional data will generally be administered by the appropriate Data Manager. 5.4 The Data Steward, having determined the category of the institutional data as confidential, will approve access based on appropriateness of the User's role and the intended use. Where necessary, approval from the Data Trustee may be required prior to authorization of access. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix O - Exhibit 1 - Page 3 © CourtAlert 2019 5.5 Data Manager must ensure the process for the administration of data is in accordance with the Data Management Life Cycle (See Appendix 1). 5.6 Data Users must ensure appropriate procedures are followed to uphold the quality and integrity of the data they access. 5.7 Data records must be kept up-to-date throughout every stage of the workflow and in an auditable and traceable manner. 5.8 Data should only be collected for legitimate uses and to add value to the CourtAlert. 5.9 Extraction, manipulation and reporting of data must be done only to perform CourtAlert business: • Personal use of data, including derived data, in any format and at any location, is prohibited. • Where appropriate, before any data (other than publicly available data) is used or shared outside the CourtAlert, verification with the Data Steward is required to ensure the quality, integrity and security of data will not be compromised. 5.10 Data stored in an electronic format must be protected by appropriate electronic safeguards and/or physical access controls that restrict access only to authorized user(s). Similarly, data in hard copy format must also be stored in a manner that will restrict access only to authorized user(s). 5.11 Appropriate data security measures (see Data Classification Policy and Procedure) must be adhered to at all times to assure the safety, quality and integrity of CourtAlert data. 5.12 The definition and terms used to describe different types of data should be defined consistently across the CourtAlert. 5.13 “Client Protected Data” is never shared, extracted, or summarized by any means other than for the purposes of issue resolution, for that client’s purposes only. 5.14 Cloud Isolation, data should be isolated to different databases and virtual networks and virtual environments where “Client Protected Data” is stored 6. Policy Review This Policy will be reviewed and updated every five (5) years from the approval date, or more frequently if appropriate. In this regard, any staff members who wish to make any comments about the Policy may forward their suggestions to the Responsible Officer. 7. Further Assistance Any staff member who requires assistance in understanding this Policy should first consult their nominated supervisor who is responsible for the implementation and operation of these arrangements in their work area. Should further assistance be needed, the staff member should contact the Responsible Officer for clarification CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix O - Exhibit 1 - Page 4 © CourtAlert 2019 Appendix 1 - Data Management Life Cycle a. (Create) Plan and Design → b. (Store) Capture and Develop → c. (Use) Organize, Store, Protect, → d. (Share) Implement, Monitor, → e. Archive and/or Dispose → ... a. (Create) Plan and Design → ... CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix O - Exhibit 1 - Page 5 CourtAlert Application and Technical Support SLA 1. Software Updates 1.1 CourtAlert will notify Licensee of software updates. CourtAlert will send these notices by email to the designated Licensee contacts. CourtAlert maintenance releases and current documentation for supported Software that the Licensee has licensed are made available by CourtAlert for electronic download. 1.2 Maintenance includes Software Updates as identified below: (i) A maintenance release is a general software release that may include minor feature and functionality changes and enhancements or bug fixes or patches. (ii) A minor version release or patch is a general software release that may include bug fixes, error corrections and/ or other minor changes. (iii) A new version contains new functionality, features and bug fixes to prior versions. 1.3 Maintenance includes Updates, but not New Software. 2. Maintenance Services 2.1 Support: CourtAlert is available for regular support by telephone and email between 9AM- 6PM Eastern Time Monday through Friday, excluding federal holidays (“Service Hours”), to provide support to Licensee in the event that Licensee detects any Error in the Software; CourtAlert shall provide email support for all times that are not Service Hours. “Error” means a failure of the software to operate in accordance with reasonable expectations and highest industry standards. 2.2 Response and Resolution Times. CourtAlert shall implement temporary workaround procedures and shall demonstrate to Licensee the good faith and continue (24/7 hours) diligent initiation and prosecution of corrective measures for all such problems involving the Software within the resolution times set forth below. Support Ticket Severity Response Requirement (from report) Critical Mission Critical Outages of the Software classified as “System Down”. Essential functionality unavailable, substantial data loss experienced Under 4 Hours Significant Issue(s) causing “Restricted Functionality” of the Software where essential functionality is unavailable and/or data loss is experienced but the system is operational Under 8 Hours CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix I - Page 1 2.3 For any Error deemed Critical by Licensee, CourtAlert shall have personnel continuously addressing the Error until such Error is resolved or reduced to Significant (as reasonably determined by Licensee). During such period, Licensee also agrees to have a knowledgeable representative available to help in the resolution. Minimal Issue(s) where minimal errors are occurring in the Software causing minor performance degradation Under 1 Business Day Nominal Any general questions concerning the Software features, functionality, configuration, performance or configuration enhancements, product feature requests, known bug status requests, upgrades, etc. Under 2 Business Days CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix I - Page 2 CourtAlert Case Management - Typical Implementation Tasks Task Name Who Note Servers, Accounts Setting up the server (application and database) requires the most IT work in the beginning of the project. Once set up, please provide CourtAlert with the server and database names and credentials. Build Application Server(s) ( Windows 2012, IIS) (Dev + Prod)Client/IT IIS installation Client/IT SSL Certificate if using HTTPS Client/IT SQl Management Studio Client/IT Deskside / Worksite Client Client/IT Document Storage (Local - 100 GB)Client/IT Service Account - CourtAlertService, Local admin on Application Server Client/IT Provide CourtAlert the Credentials SQL Server ( Enterprise or 2012) (Dev + Prod)Client/IT Crete SQL Account - CourtAlertSQL Client/IT Create CourtAlert Database Client/IT Assign CourtAlertSQL DB_Owner permissions.Client/IT Provide CourtAlert Access to source data Client/IT CourtAlert Remote Access (Securelink / Duo)Client/IT Provide CourtAlert the name of a Docketing Team or Docketing Security Group Client/IT Exchange Tasks Provide SMTP Address - Confirm Whitelist / Authentication Client/IT Create CourtAlert Mailbox (CourtAlertService owner) and provide EWS url Client/IT Provide EWS Address Client/IT Add CourtAlert Mailbox to the appropriate distribution lists Client/IT dedicated mailbox or shared with the team CourtAlertTesters@ email for testing?Optional Exchange / Outlook Sync CourtAlert will provide a PowerShell script that can be used to assign author permissions to the exchange calendar. These permissions can be assigned individually on the Tester's calendars for phase 1. Installation / Configuration CourtAlert Access to Testing Group's Calendar (Author / Publisher if migrating existing)Client/IT Services Installation / Configuration CourtAlert CourtAlert will install and configure the database and services. The system is pre- packaged for simple installation Setup Database CourtAlert Install / Configure Services CourtAlert Test Email output CourtAlert Staff Mapping for Docket History CourtAlert Staff and Team Imports CourtAlert Data Import Task CourtAlert Migration CourtAlert The Migration from Source System Court Name Mapping CourtAlert CourtAlert will provide an Excel with the Court Names used created during migration. The Docketing Team will have the opportunity to clean up the names or revisit the nomenclature (NY Southern District or Southern District of New York). Court Name Mapping Client/Docketing CourtAlert Case Management - Typical Implementation Tasks This document is the copyrighted and intellectual property of CourtAlert®, and the content is confidential and may not be disclosed to anyone who is not a full-time employee of the intended receiving firm. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix H - Page 1 CourtAlert Case Management - Typical Implementation Tasks Judge Name Mapping CourtAlert CourtAlert will provide an Excel with the Judges' names . The Docketing Team will have the opportunity to clean up the names or revisit the nomenclature (First Last or Last, First). Pre-Populate the Federal Judges Judge Name Mapping Client/Docketing Staff Mapping CourtAlert CourtAlert runs a name matching algorithm that associates source system staff with the staff from the HR database. Docketing Team to decide on what to do with unidentified staff (Create as Terminated or Map) Staff Mapping Client/Docketing Client / Matter Cleanup? CourtAlert CourtAlert to run a Client-Matter validation script. Docketing Team to decide on what to do with unidentified Matters. Create or Create under "Legacy" Round 2 Migration CourtAlert Rules Setup and Integration Integrating with CompuLaw can be done at any time. Some training is required Data Mapping CourtAlert Included in above Setup Exclusions CourtAlert TBD if necessary Integration Staff Import Permission to Read Source HR Data Client/IT Staff Import Scripts and Mapping CourtAlert Configure Existsing Scripts Client / Matter Import Permission to Read Source C/M Data Client/IT C/M Import Scripts and Mapping CourtAlert Configure Existsing Scripts Conflicts / Matter Intake Mapping CourtAlert iManage or NetDocuments Integration CourtAlert will configure the iManage integration after some discussions with Security Client/IT Configuration Client/IT Provide Screenshot of profile as to be used for mapping Client/IT Provide Credentials and Server/Database info to CourtAlert Client/IT Mapping Configuration CourtAlert Wall Builder integration CourtAlert Client Applications CourtAlert to provide binaries and dependency MSI CourtAlert CourtAlert to discuss deployment/packaging strategy with IT. For testing it is easiest if the software is manually installed/copied to Tester's desktops or dedicated Testing computers. Other Integration Outlook Sync Optional CourtAlert to configure the Outlook (Exchange) sync in Phase 1 Other reporting Optional Is there any special reporting that should be done for Records? Feature Decisions CourtAlert to discuss each feature in details and decide with Docketing Team/project team which features should be enabled, and if data needs to be imported Inquiry Module CourtAlert/Client KM CourtAlert/Client Portal CourtAlert/Client Attorney Registration / ECF passwords CourtAlert/Client Testing / Training Data Migration Testing Client/IT Testing migration breadth (were all the cases converter) and depth (were all the case details converted) System Testing Client/IT Training Session 1 - Case Lists, Docketing and Calendaring CourtAlert Training Session 2 - Review, Advanced Docketing and other Docketing Features CourtAlert Training Session 3 - Inquiry Module and Admin Features CourtAlert Attorney Training Session - Inquiry Module, Outlook and Reports CourtAlert Train the Trainer Review Docketing Staff Checklist CourtAlert Parallel Test Week Go Live Weekly Meetings CourtAlert Weekly Meetings to discuss progress and features CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix H - Page 2 CourtAlert® Case Management Typical Implementation Plan Project Management CourtAlert offers assistances and support throughout the implementation. We suggest a weekly meeting and always offer email and phone support. CourtAlert’s experience implementing this solution will allow for a seamless implementation and transition. CourtAlert believes that most of [Redacted] requirements can be filled by the existing CourtAlert Case Management software. CourtAlert therefore proposes the following procedure: a. [Redacted] will designate one or more persons as Project Manager of this project. That person(s) will have the authority, background and knowledge to make design decisions on a timely basis. Typically, a Docketing Manager (or Managing Attorney / Managing Clerk) and an IT (Information Technology) Project Leader is involved. CourtAlert will designate a Project Liaison to work closely with [Redacted Client Name] Project Team. b. The [re] Project Manager and the CourtAlert Project Liaison will agree on communication and approval procedures. CourtAlert utilizes the project management tool, JIRA for project control. Please see http://en.wikipedia.org/wiki/JIRA for more on JIRA. c. Together the [Redacted Client Name] Project Manager and the CourtAlert Project Liaison will prepare detailed documentation on each open tasks and customization request. Each customization request will be numbered. CourtAlert will provide cost estimates, if they differ from the cost proposal. The [Redacted Client Name] Project Manager will approve (or disapprove) each request. All customization requests will be documented and archived. d. When the CourtAlert team feels that there are sufficient specifications to start programming and upon [Redacted Client Name] Project Manager approval, programming will start. e. CourtAlert will do programming, unit testing and, when applicable, system testing in accordance with its standards. f. The resulting customization, either as a single item or a group of related customizations, will be presented to the [Redacted Client Name] Project Manager for approval. g. The [Redacted Client Name] Project Team will perform additional testing as deemed necessary. Any changes requested will be made by CourtAlert. When the customization is ready, it will be communicated to the [Redacted Client Name] Project Manager for approval. h. When a new version is ready, customization will be presented to the project team and any additional personnel deemed appropriate by the [Redacted Client Name] Project Manager. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix G - Page 1 CourtAlert® Case Management Typical Implementation Plan Throughout the process, and especially at the beginning, the [Redacted Client Name] Project Team, including the Docketing Team, will have access to the CourtAlert Case Management system on CourtAlert computers, via a remote or GoToMeeting. This means that the [Redacted Client Name] Project Team can always “play” with the system to gain familiarity. i. CourtAlert executives will follow the project tightly. It is proposed that there be at least one project meeting per week at your location. CourtAlert executives will be present in some weekly meetings to verify the [Redacted Client Name] Project Manager’s full satisfaction with the process and outcome in question. j. Training and implementation will be straightforward. By the time the system is ready, many of the Docketing Team / MAO members will already be familiar with it. CourtAlert will provide “One on One” on-site training in cycles or waves on the new system for all Docketing personnel. CourtAlert will provide its existing end user training documentation, technical documentation including server installation instructions, and customizations included in the services performed in this project. Data Analysis CourtAlert will analyze the [Multiple Redacted Systems], looking for Cases, Dockets and Diaries for conversions. Typically, CourtAlert first provides an Excel with the Case Header information extracted out of [Redacted Systems]. CourtAlert and the [Redacted Client Name] Docketing team will analyze the Excel data and use it to confirm with [Redacted Client Name] the data that will be migrated. Typically, this is a good time to review the cleanliness of Forums, Venues, Judge, Case Types, Notes, Classifications and Staff / Teams, Parties, Index Numbers and other data. New York Supreme and Federal Court cases are usually validated syntactically (e.g., index number format) and against Live Court information (e.g., Case Title Matching). CourtAlert has several tools at its disposal to clean up and supplement [Redacted Systems] data with the Court’s Data. Additional case data, including parties, representation, Forum, Venue, Dockets and/or documents may also be imported from NYSCEF and/or PACER depending on your needs. Servers and Infrastructure [Redacted Client Name] IT will provide the hardware as listed in the Hardware specifications. Typically, this consists of • Two Application servers (Testing and Production) to run several CourtAlert Services; including: o Diary Sender – Performs Scheduled Tasks o Mail Relay – Relays mails to Case Teams CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix G - Page 2 CourtAlert® Case Management Typical Implementation Plan o ECF Agent – Processes ECF Notices o Web Inquiry Module – A Web/Read Only Module that enables attorneys to access the data on their cases. Note, some clients run the Web Inquiry module on a separate IIS Cluster. • Two SQL Databases (Testing and Production), • File Repository o Network or Local Storage - to store Documents related to cases, if iManage or net documents is not used. o A typical installation also requires access to: • [Redacted Client Name] SMTP Relay • [Redacted Client Name] Exchange Mailbox that receives copies of Court Notices, to be discussed • [Redacted Client Name] Exchange Web Services access for Calendar Sync CourtAlert is typically granted remote access to client computer servers until implementation. It is assumed that, subsequent to satisfying any data security requirements [Redacted Client Name] may have in this regard, CourtAlert would be granted such access to [Redacted Client Name] servers in order to deliver that which is offered in the proposal. We request remote access to your computer servers until implementation. After implementation, CourtAlert will request access on an ‘as needed’ basis and in the context of any security requirements of [Redacted Client Name]. CourtAlert can suggest a method of requesting access which we believe will be approved by the Information Technology department. Feature Requests and System Output The CourtAlert Case Management software package is a million-code-line package with hundreds optional features. [Redacted Client Name] has established workflow and routines. The efficient and cost-effective bridging between the two will be essential. CourtAlert has built such bridges with a high degree of success and with minimal disruption to the client as is possible. To ensure that we meet [Redacted Client Name]’s goals, two processes will take place: Mainly at your locations, but if you wish at CourtAlert’s offices, CourtAlert will demonstrate every feature of the Case Management software. CourtAlert would help arrange for your team to tour several clients currently using the system to see how they utilize the system in their particular environments. As mentioned earlier, there are numerous additional functions that can be turned on an off. Likewise, the CourtAlert project manager(s) will spend as much time as necessary with designated [Redacted Client Name] staff at your locations. CourtAlert brings many years of experience to the table and believes that these meetings can be very valuable without being overly demanding on the time of [Redacted Client Name] project team. Some of the features to be discussed: • Outlook Appointment Formatting • iManage Desksite / Worksite Integration • Single Sign On CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix G - Page 3 CourtAlert® Case Management Typical Implementation Plan • Integration with HR (Staff Members / Terminations) • Integration with Active Directory (Case Teams) • Ethical Wall Integration • Attorney Registration / ECF Logins Module • Case Classifications • Web Inquiry Module • Attorney Tickler Formatting • Case Lists • Docket Sheets • Calendars • Conflicts – Searches • SharePoint Knowledge Management, an innovative area of the CourtAlert solution, will benefit from the addition of converted existing data. Knowledge Management is a set of programs that allow [Redacted Client Name] personnel to easily locate examples of quality past work products to be used as templates for document drafting in similar matters. Testing / Feature Releases Once a set of features have been selected: 1) CourtAlert will schedule the features into one or several releases/versions. 2) CourtAlert and [Redacted Client Name] IT will release the entire system to a Test environment. a. Optionally, CourtAlert can re-run Migration scripts on a fresh backup 3) [Redacted Client Name] IT will make the Docketing and Admin Test programs accessible to the selected testing MAO team members. 4) [Redacted Client Name] Testers will report back any issues and/or approve the features. This process is meant to be periodic and iterative to allow for quicker feedback. There are expected to be at least 4 deployments, conservatively scheduled as follows: Name Features Expected Initial Version with Cursory mapping of source data Expect to see around 70% of the fields mapped with no cleanup 2-3 weeks after servers and source data are accessible signed. Several iterations of updates and migrations until we get to a 100% Mapped Version with clean data After several weeks’ discussions and cleanup, is expected to be mostly clean. This is a good time to do the training and identify any issues. 2-3 months in CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix G - Page 4 CourtAlert® Case Management Typical Implementation Plan 1 Week - Parallel Testing Version The migration scripts are expected to be perfect by now. This version is used to make sure all reports are running as expected and to make sure everyone is comfortable with the way the data looks and with the software 3-5 months in Go Live Version Over the weekend Go Live, Come in Monday morning and Docket in the new system 3-6 months in Go Live Once the test system is approved for production. • CourtAlert will prepare a configuration file for Production. • [Redacted Client Name] IT will release the Docketing and Admin Programs (Production config) to MAO • Docketing team will stop docketing • CourtAlert will Request a final backup of the [Redacted Systems] data. • CourtAlert will run the migration scripts for the last time and deploy the result into the CourtAlert production database. • Docketing team may begin reconciling and docketing in CourtAlert • Project completion will be based upon Docketing Department final test and acceptance of the CourtAlert Case Management software implementation at [Redacted Client Name]. Celebrate! For further information please contact Yaniv Schiller, yschiller@courtalert.com. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix G - Page 5 CourtAlert® Organizational Chart President Reporting Business Development Alert Services Courts Liason Reporters at courthouse Operations Customer Support Customer Training Customer Site Training CourtAlert Site Training Remote Training Knowledge Base Updates Marketing Customer Relation Weekly Publication Client Events Research and Development Programming -Case Management team Product Manager Project Manager Front-End Programmers Back-End Programmers Testing and Deployment Programming -other services Training One on One Training Sessions Group Training Sessions User Manual Creation and Updates Internal Networks and Backup Infastructure Disaster Recovery Site Administrative Business Stratey and Development Billing Human Resources Outside accounting services Outside legal services CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix F – Page 1 Izzy Schiller- Summary Resume CourtAlert 552 Seventh Avenue New York, NY 10018 Education: BA, 1976, Hebrew University, Israel – Econometrics and Statistics MBA, 1982, Baruch College, CUNY Various educational classes Military: 1970-1974 Israeli Army, Lieutenant, Engineering Corps, Operational Service Badge awarded. Work Experience: • 25 years experience in designing and programming computer systems. • Various computer systems for the State of Israel both in Israel and in the U.S. • A system for an exporter of industrial and military items to NATO which allowed it to bid and support a major project • At IBM request, many years of an IBM Business Partner as a provider of computer systems for several new (at the time) computers: IBM System/32, 34, 36 and 38, IBM AS/400. • Installed and programmed the first Sysetem/38 and AS/400 in the area. • Designed and supervised the programming of major financial computer systems for American Express, Banks • Designed and supervised the programming of major order processing and warehousing computer systems for several distributors and importers. • Designed and supervised the programming of many specialty computer systems for The American Institute of CPAs. • Designed and supervised the programming of computer systems for the NYS Office of Courts Administration (“OCA”) • Designed and supervised the initial programming of CourtAlert • Established CourtAlert and manages it as its President. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix E - Page 1 Yaniv Schiller Profile Creative, motivated systems analyst with experience in identifying and resolving complex data and numerical challenges. Ability to enhance a company’s business flow by applying expertise relevant to application design and development. Utilize academic concepts to real world problems, simplifying complex data analysis, organization and workflow. Experience CourtAlert NEW YORK, NY COO MAY 2012-CURRENT Starting as the product manager and then growing into the role of COO, responsible for the growth of the Case Management Product and other CourtAlert services. Experience in managing large teams of developers and implementations of the Case Management product at many AM-100 law firms Blue Mountain Capital NEW YORK, NY SENIOR DEVELOPER APRIL 2008 – MAY 2012 Developed and integrated multiple front-office and mid-office application responsible for trading and risk across the firm. Highbridge Capital NEW YORK, NY VICE PRESIDENT, FIXED INCOME TECHNOLOGY MAR 2006 – APRIL 2008 Took on the initiative of building a firm-wide Enterprise Service Bus. This workflow over messaging environment processes the trade and security master workflows. Trades, for example, are entered in home-grown or 3rd party trading systems and are immediately mapped to one standard trade format. Trades then follow a workflow across which trades are imported to the books and records, sent to brokers for settlement and/or sent to DTCC for settlement. There are many components to this SOA project. Some services lent themselves to c#, so those were written using ICE proxies to JMS; others were Java, JMS-based. The workflows and exception logic are written in Mule. SAC NEW YORK, NY LEAD DEVELOPER, CONSULTANT JUN 2005 – MAR 2006 On site at SAC Capital Management as a consultant from CodeStreet, I designed and developed a back-office CDS trade booking system. Trades are entered on Bloomberg POMS and flow through a MQ messaging tier to a CDS Processor service. There, the trades are recorded to a position database and an FpML message is generated for confirmation on DTCC. The front-end, an ASP.Net GUI, contains a Position Blotter, Position and Trade Editor and other reporting functions. Developed a series of pricing retrieval applications used by the backoffice to obtain several closing bond prices. CodeStreet NEW YORK, NY SYSTEM ANALYST 2004 – MAR 2006 Developed TeamWork, CodeStreet’s proprietary corporate bond trading platform. Highlighting workflows between sales and traders desks. The application design included a Java server with a C# frontend. Emphasis on usability and information exchange. CourtAlert NEW YORK, NY INTERN / JUNIOR DEVELOPER 2000 - 2004 Designed and developed internals systems for accounting, billing and document retrieval operations using Visual Basic and ASP interfaces. Implemented several systems that generate specific, informative alerts for the customer law firms from data provided by various New York courts. Designing and implemented sophisticated database along with website in ASP to display Court schedules and case snapshots. Education Columbia University NEW YORK, NY MASTERS IN COMPUTER SCIENCE 2003-200 Yeshiva University, Columbia University NEW YORK, NY JOINT B.A. IN COMPUTER SCIENCE AND PRE-ENGINEERING 1999-2003 Academic Awards And Honors MSTA Columbia Fellowship - Spring 2004 ACM Regional Collegiate Programming Contest (2000, 2001, 2003) Dean’s List - Fall 2002, Columbia University Dean’s List - Fall 2001-Spring 2002, Yeshiva University Dean’s List - Fall 2000-Spring 2001, Yeshiva University CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix E - Page 2 Amit Choudhary Senior .Net Developer Experience summary Amit has over 7 years of experience in the software industry. He has experience in the design and development of applications for Microsoft technology stack. He possesses good exposure of end-to-end project lifecycle for application development. He offers experience in domains such as E-Commerce, Energy, Human resource management, Revenue accounting and Social networking etc. Present • Currently working as senior .Net developer (Technical Lead) at Nagarro Inc. since Feb, 2011. Skill set • Extensive experience on object oriented Design, Architecture and Principles, TDD. • Vast experience in design and developing server/client (Tiered) architecture based applications. • Practicing Domain driven design, CQS, CQRS, and Event based architecture with Functional Programming. Programming and scripting languages C#, Javascript, SQL, Asp.net, HTML5, XAML, Shell Scripting, XSLT, Beginner in F#. Web Technologies (server) Asp.net(webForms, MVC4/5), WebAPI, WCF(webhttp), OWIN, KATANA, Asp.net CORE, Beginner Node.js, SignalR, Redis, IIS 6.0/7.0/7.5/8.0/8.5. Web Technologies (Client side frameworks) Javascript, JQuery, Angular JS, Boostrap, CSS3, JSON, XML. Frameworks and libraries .Net Framework 3.5, 4.0/4.5/4.6, TFS CI BuildsLINQ, LinqToSql, EntityFramework 5/6, WCF, SignalR, Ado.net, DI containers(Unity, AutoFac, SimpleInjector), Windsor Castle, Enterprise Library, Caliburn Micro, Automapper, Various Unit testing frameworks(Nunit/MSTest/XUnit), Json.NET, Microsoft Code Analysis (ROSLYN), .Net CORE. Tools Visual Studio(2010/2013/2013/2015), Visio 2010/2013, Enterprise Architect(EA), RedGate Profilers, Red gate .Net and Sql Tools Belt, Resharper. Git Bash, TFS, Tortoise SVN. Cloud Basics of Azure SAAS, PAAS services using Azure portal. Databases and BI SQL Server 2000/2005/2008R2/2012/2014, Oracle8i/9i/10g, PL/SQL, DB2, Mongo DB, SSIS, BI Studio, Pantaho Kettle(Spoon) Devices and OS Window Server 2003/2008R2/2012, Windows 95/98/NT/2000, Vista, Windows 7/Ultimate/8/10 (M) +1 (347) 345-5369 Astoria, New York. 11106 amit_85i@hotmail.com CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix E - Page 3 Education • Masters in Computer Application from Graphic Era Institute of Technology, Dehradun, India. Honors and awards • Technical Community awards – o Awarded as Microsoft - Most Valuable Professional (MVP) for technical expertise in Visual C# in year 2012, 2013, 2014 and Visual studio application development in 2016. o 5 times awarded as C-SharpCorner - Most Valuable Professional (MVP). Current and past work details Vital records management Duration April 2015 – June 2016 Company Nagarro Client New York city wide government agency Technologies Visual studio 2012/2013, TFS 2010/2012, SQL server 2008 R2, Asp.net MVC, WebAPI, WCF, Microsoft Quality Tests, StyleCop, Microsoft Code Analysis, Custom code review reports XML/XSLT, SAML authentication, CodedUI functional testing, Lexus-Nexis payment integration, Geo-location address verification. Business overview Project is to revamp existing system with UI as windows application to responsive UI web application. Also the new system has to be integrated with payment gateways, third party system to receive orders and automation of internal process to reduce manual work and speedup the existing process of Vital records registration. Achievements As a Technical Lead, ▪ Working closely with client and development team to ensure that software development process is meeting all important aspects from process to technology. ▪ Helped development team with reviews of designing and implementations in project. ▪ Helped development team with review and making better Design and documentation of each module architecture. ▪ Helped team to identify PII data and applying technology solution to CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix E - Page 4 meet HIPPA and PCI data compliance. ▪ Helped client with identifying any risks/gaps in business requirement and technology at early stage of development. ▪ Helped development team maintaining Coding standards by intensive manual and automated code reviews. ▪ Helped client to make decision for in-house development vs off-the-shelf commercial products during development. ▪ Worked closely with Architect and DevOps team creating builds continuous integration (CI) and deployment model using Microsoft Team Foundation Server. Sport Betting Duration April 2013 – March 2015 Company Nagarro Client One of largest online Sports betting games terminal builder (Austria) Technologies Visual studio 2012/2013, TFS 2010/2012, SQL server 2008 R2, WPF, Asp.net WebAPI, WCF, Log4Net, NUnit, Microsoft Tests, Business overview Project involved the designing and implementation of various services related to Sports and bets, Including customer card and account management for the session. A remote installation tool for the Sport betting gaming terminals for updates/fresh installation. Achievements • Designed and developed a simulation system which helped developers to use local feeds for ODDs and Events for running games. Even this feed can simulate events on Sport gaming terminal console. • Designed and developed a remote installation system for Gaming terminals to deploy new releases. • Designed and developed auto update service modules for new Gaming terminals. • Designed and developed dynamic workflow wizard for installation on new Gaming terminals. • Worked closely with client at Onsite with offshore team to help them coordinating with ongoing development. • Applied intensive peer review practice to ensure code quality. • Developed and Delivered backend WCF services with Unit tests having 90% code coverage. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix E - Page 5 Facility optimization Duration September 2012 – February 2013 Company Nagarro Client ECOVA energy optimization (USA) Technologies Sharepoint Asp.net webparts, Chart controls, Infragistic win controls, MS SQL server 2008 R2, C#, ASP.Net, JavaScript, IIS 8.0, TFS, Microsoft Visual Studio.Net 2010, Agile development Business overview Project involved the requirement for rebranding of existing sharepoint website with Asp.net webparts. Reporting the auto and manually generated data in reports was main new features developed. The team worked closely with onsite/offshore with Agile/Scrum techniques. Achievements • Helped client with re-branding of existing sharepoint sites • Integrated Asp.net custom webparts with ClientSide plugins to create better dashboards for energy fluctuation/risk/ticket generations reporting. • Design and developed a Multithreaded Windows service handling bulk feed recording from energy monitors installed a various location in USA. • Worked at offsite as agile developer with challenges like working in different Timezone. • Helped client identifying and fixing performance bottlenecks in one of existing web application. Revenue accounting(V2) Duration August 2011 – August2012 Company Nagarro Client One of the largest private RailRoad owner (USA) Technologies MS SQL server 2005, C#, ASP.Net, JavaScript, IIS 5.0 / 6.0, SVN, Microsoft Visual Studio.Net 2008, FitNesse, XML, XSL Business overview Project involved the requirement understanding, designing and development with bug fixing in the module for calculating revenue from non-members of a rail car owner company for a car usage. The revenue to be managed by managing discrepancy in bills and payments. This includes CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix E - Page 6 extensive use of ETL operations with report generation and communication between Enterprise level integrated system using webservices. Achievements • Designed and developed an automated testing framework using Fitnesse tool to test Event server services for data integrity. • Helped automation testing team with training on this new framework. • With this new framework the Integration testing helped identifying a lots of invalid business related scenarios e.g. incorrect sequence of Events coming from event server, lost events etc. • Actively involved in proposing database design being developed for new billing application. E-commerce store Duration May 2011 – August 2011 Company Nagarro Client Lutron store (USA) Technologies AspDotNetStoreFront ML7.0, MS SQL server 2005, C#, ASP.Net, JavaScript, IIS 6.0/7.5, TFS, Microsoft Visual Studio 2010, XML Packages Business overview Project involves the customization and bug fixing like SQL injection attack and other enhancements. It also involves uploading and verification of new products using SSIS package, managing the code and data migration through environments. Achievements • Provided minimal or no knowledge of Design and code of ecommerce store developed with AspDotNetStoreFront ecommerce bundle; I successfully analyzed and learned the existing architecture and structure of application. • Helped client identifying & fixing the security issues like SQL Injection, XSS etc. which were caused by lacking of security in AspDotNetStoreFront ecommerce bundle. • Identified and fixed performance bottlenecks in the store website. • Designed and developed an SSIS package to load new products from Excel sheets to store database. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix E - Page 7 Revenue accounting Duration February 2011 – May 2011 Company Nagarro Client One of the largest private RailRoad owner (USA) Business overview Project involved the development and bug fixing in the module for members/non-members of a cart owner company. It implements the time recording of car hire, car mileage, taxes, rack management, car shop repair etc. Achievements • Understanding of a large business model was a huge challenge in this project. With ongoing bug fixing I learned the system architecture and business domain to avoid bad practices like applying a bug fix with new 99 bug problem. • Helped identifying and fixing performance bottlenecks • Worked closely with architect to restructure/re-design the existing legacy code to decoupled and testable code. • Introduced unit tests methodology to avoid breaking existing working modules during refactoring. Portal reporting configuration tool Duration October 2010 – February 2011 Company Hewitt Associates (AON Hewitt) Project Type In-House product Technologies DB2, C#, Windows Forms, Remoting Business overview Project involved the development of an intranet application which maintains the reporting data for a portal which is used by the client teams to manage the reports on the portal. It involved managing the data by using queries based on roles, restrictions etc. Achievements • Understanding the design and high level documents • Optimized SQL queries loading large amount of data in order to improve performance. • Worked closely with architect to improve performance using Data Virtualization in Windows Grid control paging. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix E - Page 8 • Created and executed Manual unit tests for code changes during bug fixes • Followed organized coding standards using code review checklist. Workbench tool launcher Duration August 2010 – September 2010 Company Hewitt Associates (AON Hewitt) Project Type In-House product Technologies DB2, C#, Windows Forms, Remoting, XML Business overview Project involved the launching of different tool from single interface which is used enterprise wide and the technology was upgraded from COM to remoting. Each and every technical problem for every type of user were resolved which were caused by this migration. Achievements • Involved in understating the exiting design and implementations in project • Involved in client interaction • Resolved data and performance issues • Coding standards and code review checklist • Involved in coding and smoke testing it for correctness • Involved in migration of code from vs2005 version to vs2010 version Shopping portal with integrated social networking Duration February 2009 – July 2010 Company Kalosoft software Pvt. Ltd. Project Type In-House product Technologies MS SQL server 2005, C#, ASP.Net WebForms, Telerik, Javascript, EntityObject ORM, jQuery, HTML, XML. Business overview Project involved the development of a website which provides the online shopping and social interaction to the end users. It is an integrated product that includes the selling product management, user management for CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix E - Page 9 different roles, transactions and integrates all the users to a single platform to interact with each other on its own social network. Achievements • Being this as my first project the biggest challenge was to move my knowledge from Java technology to Microsoft .Net technology. • Learned and applied new technology as Full Stack developer. • Involved in designing and implementations in project • Designed the application architecture • Integrated the shopping site with payment gateway Paypal. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix E - Page 10 EYTAN SCHILLER 4780 Palisade Avenue Riverdale, NY 10471 (646) 209-5587 Eytan.Schiller@gmail.com Education ▪ B.E. in Electrical Engineering, The Cooper Union, New York, May 2011 ▪ GPA: 3.3 Awards ▪ Dean's List - Fall 2007, Spring 2008, Fall 2010 ▪ HKN, Electrical and Computer Engineering Honors Society – President Computer Skills LANGUAGES ▪ Experience in: C#, VB.Net, WPF, Java, C++, Powershell, Matlab DBMS ▪ SQL Server 2008-2017, MongoDB WEB ▪ AngularJS, ASP.Net, HTML, Typescript, JavaScript PLATFORMS ▪ Azure, Windows 2012/2016/2019 Server & Clustering, 7/10, LINUX VIRTUAL MACHINE AND DISK IMAGING ▪ VMware Workstation & ESX Related Experience COURTALERT New York, NY Head of Research and Development April 2016 - Current ▪ Manage and grow the software development team ▪ Drive innovation of the latest CourtAlert Case Monitoring, Client Monitoring and Case Management services ▪ Coordinate client deployments of the CourtAlert Case Management System ▪ Defined cloud architecture for the CourtAlert Case Management Cloud Solution BLUEMOUNTAIN CAPITAL New York, NY Software Developer (Trading Strategist group) August 2013 – April 2016 ▪ Helped design, develop, and maintain the firms Execution Management System (EMS) and Order Management System (OMS) ▪ Built a proprietary execution platform using .Net technologies (including Async and Reactive frameworks) that was used to route the entire firms production order flow ▪ Developed FIX handlers to send No-Touch orders via broker platforms to various executing dealers ▪ Worked directly with the portfolio managers, traders, and operations to deliver a live and robust Order Management System that allowed them to send both simple and complex orders, see live execution status, and set booking and allocation instructions ▪ Built a robust test environment that facilitated faster feature development, safer code, and greater collaboration ▪ Implemented a User Acceptance Testing (UAT) environment that allowed the team to fully test all parts of the system from order entry to mock execution to back-office allocation ▪ Created an auto-allocation process to allocate all trades in hundreds of strategies across over a dozen funds ▪ Re-wrote the stock loan management system to automatically request borrows from brokers and hold trades until borrow was made available ▪ Tech Environment: C#, Rx, WPF, Microsoft SQL Server, RabbitMQ, FIX ALPHABET MANAGEMENT / SAIERS CAPITAL New York, NY Software Developer May 2011 – April 2013 ▪ Designed, developed, and maintained a front-end application to calculate live PL for Equity, Option, and FX positions ▪ Greatly enhanced the firms primary in-house risk application by making it more multithreaded and offloading calculations to a service ▪ Wrote from the ground up a trade feed handler to accept FIX and xml trade messages and flow them throughout the firms systems ▪ Wrote Excel .Net add-ins to push live risk and market data using Excel real-time data (RTD) and user-defined functions (UDF) ▪ Setup and used large MongoDB databases for storing and analyzing large amounts of CDS historical data ▪ Developed a Bloomberg API wrapper to allow function calls to Bloomberg from any of the groups applications ▪ Worked extensively on creating a unified RabbitMQ messaging network for the vast majority of the groups applications ▪ Created a multicast logging framework to broadcast and listen to log and alert messages without any single points of failure ▪ Tech Environment: C#, WPF, Microsoft SQL Server, MongoDB, RabbitMQ, Bloomberg, FIX, Imagine BLUEMOUNTAIN CAPITAL New York, NY Part-Time Development Analyst September 2010 – April 2011 ▪ Developing a research WPF desktop application that integrates in-house research with live market data and risk measures. ▪ Designed and implemented a backend service that emails research and risk snapshots in PDF. Designed in specific for IPad access. ▪ Tech Environment: C#, WPF, Microsoft SQL Server BARCLAYS CAPITAL – PORTFOLIO MANAGEMENT IT New York, NY Summer Development Analyst Summer 2010 ▪ Implemented model for pricing illiquid loans using SQL Stored Procedures and C# executables. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix E - Page 11 ▪ Worked with automated reports to help Loans Desk manage their portfolio. ▪ Tested, packaged, and deployed vendor application for business users. ▪ Tech Environment: C#, Microsoft SQL Server, SQL Reporting Services, Autosys HIGHBRIDGE CAPITAL MANAGEMENT New York, NY Summer Intern Systems Administrator Summer 2008, 2009 ▪ Created a utility to organize the 100+ SQL server instances along with disk configuration of each server ▪ Backend jobs to pool data every hour and front end web UI to view/report collected data ▪ Assisted in organizing Disaster Recovery operations and simulations ▪ Managed multiple Windows 2003 Server Clusters with SQL Server 2005 instances ▪ Set up dozens of Power Distribution Units (PDUs) connectivity along with proper SNMP configurations ▪ Tech Environment: Windows, Windows Clustering, Linux, C#, ASP.net, Perl, Powershell, WMI, Microsoft SQL Server COURTALERT New York, NY Part-Time Systems Administrator 2006 - 2014 ▪ Implemented a firm-wide knowledgebase infrastructure for use by all employees ▪ Setup a virtual environment of 5 ESX servers with dozens of Virtual Machines ▪ Setup a windows Distributed File System (DFS) with replication for the firms entire central file system ▪ Deployed several PFSense firewall appliances with site-to-site VPNs and remote access. ▪ Tech Environment: Windows, VMWare, Microsoft SQL Server, PFSense, OpenVPN, NFS COURSEWORK AND PROJECTS ▪ Computer Programming for Engineers , Advanced Programming Languages , Data Structures and Algorithms I & II ▪ Digital Logic Design , Computer Security, Computer Architecture , Artificial Intelligence , Software Engineering ▪ Signal Processing & Systems Analysis, Digital Signal Processing, Communication Theory, Matlab Seminar ▪ Mechanical Physics , Electro-Magnetic Physics , Modern Physics ▪ Calculus I, Calculus II, Calculus III, Discrete Mathematics, Linear Algebra, Differential Equations, Probability ▪ Digital Tic-Tac-Toe - Two-player electronic tic-tac-toe with win checking and score keeping using CMOS chips. ▪ Othello Computer Game - Designed and developed an Othello game using C# with for an expert multi-strategy computer player. ▪ Artificial Intelligence Neural Network - Coded implemented an artificial neural network using C++ with hidden layers and both forward and backward propagation. ▪ Data Encoder for Noisy Channel - Coded a binary data encoder using Matlab with Reed-Solomon and BCH encoding. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix E - Page 12 Divya Anilkumar 6 Tarry Hill Dr, New City, New York 10956 Phone: 973-444-4178 Email: divea.anil@gmail.com LinkedIn: https://www.linkedin.com/in/divya-anilkumar-25a32822/ Professional Experience Summary • 13 years of experience in complete Software Development Life Cycle (SDLC). • Hands on experience in Windows application and web application development. • Hands on experience in Azure development, Azure Cosmos database with SqL/Mongo, Rabo 3T, Blazor and .Net core technologies. • Strong knowledge of Object-Oriented Programming concepts, Design Patterns, Microsoft Enterprise Library, n-tier architecture, SOLID Design Principles, Dependency Injection. • Designed and Developed applications for complex systems and strong coding experience in UI designing, User controls, ASP.NET, C#.NET, VB.NET, ADO.NET, Web Services, LINQ, AJAX, JavaScript, JQuery. • Exposure to Web Services, SOAP, REST, WCF, WEB API services. • Experience in leading the technical team in offshore/onsite model. • Experience in task estimation and achieving the planned velocity for the team in Agile. • Exposure to Agile Scrum Methodologies and leading the SCRUM practice. • Experience in performing code review, static code analysis for the whole team. • Experience in Window Share Point Service 3.0 and Office Share point Server 2007(MOSS 2007), InfoPath UI design, PowerShell scripting. • Extensively used HTML, CSS, DHTML, XML, and XSL. Experience in manipulating XML, Converting Data between ADO.NET and XML, DTD, Schema, XSL (XSLT, XPath, and XQuery). • Expertise in preparing requirement document specifications, Design documents, UML Diagrams, Flow Diagrams, Class Diagrams, Sequence diagrams, use case diagrams. • Experience in healthcare, financial (Audit, Advisory, and Tax) and Travel domains. • Ability to manage and deliver results on multiple tasks by effectively managing time and priority constrains. • Experience in Interacting with Business/IT customers, Experience in Technical presentations. • Good communication, interpersonal, intuitive and leadership skills. Technical Skills: Operating Systems : MS-DOS, Windows XP/vista/Windows7/8/10, 2003/2008 R2 server, UNIX. Languages/Technologies : .NET Framework 2.0/3.0/3.5/4.0/4.5,.Net Core 3.1, Blazor, Rabo 3T, Azure Development, Application Insights, C#,VB, C,C++,VC++, Pascal, Cobol, InfoPath, WCF, Web services, Workflows, SOAP, REST,WEB API, MVC 4.0, ASP.NET, XML, XSLT, CAML, CSV, XSD, HTML, DTD, Schema, AJAX,JSON, Entity Framework, Razor. SonarQube, ReSharper, Scala Database : SQLServer2005/2008/2012, Oracle, FoxPro, MS Access, SQL Profiler, PL/SQL, T-SQL, SSIS packages, Mongo DB, Azure Cosmos. Programming Environments : Visual Studio.NET 2003 /2005/2008/2010/2012, SharePoint Designer, SharePoint Server2007, WSS 3.0 Reporting Tools : SSRS, Crystal Reports, Power BI Scripting Languages: : VB Script, Java Script, POWERSHELL, Unix shell scripting, JQuery, React, Angular. Source Control : VSS, SVN,TFS, GitHub Testing Tools : xUnit, NUnit, VSTS, Clear Quest, Bugzilla, Postman, Soap UI. Responsibilities: Analysis, Design and Develop applications for Web based, client server applications, data warehousing applications and azure applications using .Net Core, Blazor, ASP.NET, MVC6, C#.NET, VB.NET, ADO.NET, LINQ, OOPS and Design Patterns. Implement Web Services, SOAP, REST, WCF, WEB API services. UI designing with Kendo UI, Razor, Html5, CSS, DHTML. Extensively using Enterprise Library and n-tier architecture. Implement Client side validations using AJAX, JavaScript, and JQuery, AngularJS, KnockOutJS. Exposure to Agile CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix E - Page 13 Methodologies and with scrum experience. Experience in manipulating XML DOM, DTD, Schema, XSL (XSLT, XPath, and XQuery). Expertise in preparing requirement document specifications, Design documents, UML Diagrams, Flow Diagrams, Class Diagrams, Sequence diagrams, use case diagrams. Interact with Business/IT customers, create Technical presentations. Created SQL stored procedures, functions, cursors, triggers, views, temporary tables. Optimize queries for better application performance. Worked on browser compatibility. Application deployment and Production Support in various environments. Employment History Company Position Location Dates Work Hrs Type of business Fareportal Sr Software Engineer 135 W 50th St, New York, NY 10020 Aug 2017 – Till Date 40 Ecommerce Idexcel Sr Software Engineer(.Net Developer) 3 Chestnut Ridge Rd, Montvale, NJ 07645 Feb 2016 – Aug 2017 40 IT Services Fareportal Sr Software Engineer 135 W 50th St, New York, NY 10020 Sep 2014 – Feb 2016 40 Ecommerce UST Global Systems Analyst 20 Enterprise Aliso Viejo, CA 92656 Feb 2007 – Aug 2014 40 IT Services Education: Degree College Dates Percentage Bachelor of Technology in Computer Science & Engineering L B S Institute of Technology for Women Karamana Thirumala Road, Poojapura, Thiruvananthapuram, Kerala 695012, India Jun 2002 – Jul 2006 85% EXPERIENCE OVERVIEW Company: Fareportal Aug2017 to Present Title: Senior Software Engineer • Managing Fareportal's core piece of technology that requires to have daily meetings and interactions with 15 developers in India to ensure the delivery of assignment given by product and business teams. • Collaborates with business teams for the requirements and decisions, works in expanding API technologies. • Works very closely with Product managers for requirement gathering and preparing the project roadmaps. • Responsible for assigning the work to global team of 15, guiding them and ensuring the project delivery. • Converts the Product managers need to technical specification documents. • Responsible for choosing the right technology for delivering the products needs on time. • Works closely with GDS (Global distribution system) like Amadeus and Sabre, direct connects like FareLogix for American Airline, and various other airlines API solutions. Ensures the delivery of quality codes on time. Leads the API development efforts. • Created monitoring systems around the API solution to maintain the performance and keeping the security measures on place. • Responsible for exploring and implementing the new technologies like move the API on cloud, • using latest framework by Microsoft known as .net core 3.1, and Using data technology like Redis, Cassandra etc. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix E - Page 14 Company: KPMG LLP (Idexcel) Feb/2016 to Aug 2017 Title: Senior Software Engineer (.Net Developer) • Analysis, Design and Develop applications for Web based, client server applications, data warehousing applications using ASP.NET, MVC6, C#.NET, VB.NET, ADO.NET, LINQ, OOPS and Design Patterns. • Used Infragistics Grids for various requirements. Involved in creating the standard reports using Crystal Reports. Implement Web Services, SOAP, REST, WCF, WEB API services. UI designing with Kendo UI, Razor, Html5, CSS, DHTML. • Developed business objects for performing Business functionalities and validations. Extensively used Enterprise Library and n-tier architecture. • Extensively involved in integration of developed modules. Implemented Client side validations using AJAX, JavaScript, and JQuery, AngularJS, KnockOutJS. Exposure to Agile Methodologies with scrum experience. • Worked on SQL Profiler Query tuning and Fine-tuning of Stored Procedures to improve performance. • Prepared Unit Test Cases for the Developed functionalities. • Performing offshore coordination and interacting with team for design, development and code review. • Reproducing and performing in-depth analysis of customer issues, determine causes, provide workarounds and long term solutions. • Provided support to the deployed system till stabilized. Worked on to optimize queries for better performance, on browser compatibility, and Obfuscation. • Coordinating with business users for UAT and Production testing. Involved in writing the User Guides. Company: Fareportal Sep/2014 to Feb/2016 Title: Senior Software Engineer • Analyze, Design and implement new features for ancillaries for flight booking and integrate to the main website as services using C#.net, MVC technologies. • Localization of the websites cheapoair.com and onetravel.com for different cultures. • Performed offshore coordination, design, development and code review. • Collaborating with inter-dependent teams (QA, Operations) and peers. • Schedule, support and co-ordinate User Acceptance Testing and complete sign-off. • Worked on design and development of applications using MVC 4 and SOAP / REST /WEBAPI, Razor technologies. • Created SQL stored procedures and complex queries. • Worked on SCRUM methodologies and coordinated the sprint meetings as scrum master for automation projects. • Implemented PayPal services feature on website for optional features like seat and baggage booking services. • Extensively used ADO.NET and entity frameworks for data manipulation. • Involved in implementing the Unit Testing Mock Framework for the Airline ticket reservation functionalities. • Creating Low level and high level Technical Design Documents. Involved in UAT and production deployment processes. Company: UST Global Feb/2007 to Aug/2014 Title: Systems Analyst • Analyze, design, develop, test, implement and maintain Web based, client/server and ETL Business/data warehouse applications using C#, .net, JQuery, AJAX, J2EE, Infragistics technologies, OLTP etc. • Extensively used ADO.NET and entity frameworks for data manipulation. Developed stored procedures, triggers, views and indexes. Designed data models using Oracle Designer. • Created Technical Design Documents, Sequence Diagrams, use case diagrams. • Designing and developing reports using Crystal Reports, SSRS. • Worked in Agile/Scrum model, played scrum master role by organizing and facilitating sprint planning, daily stand-up meetings, reviews, retrospectives, release planning, demos and other Scrum-related meetings. Performing Code Reviews, Preparing Review Defect Trackers. • Reproducing and performing in-depth analysis of customer issues, provide workarounds and long term solutions. Coordinating with business users for UAT and Production deployments. Creation of unit testing frameworks using NUnit, VSTS. Assisted team with making appropriate commitments through story selection, sizing and task definition and participated proactively in developing and maintaining team CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix E - Page 15 standards, created tools and best practices to reduce development time. Certifications • Diploma in Advanced Software Technology, CSC Computer Education, 2002 • Microsoft Certification (070-536 and 070-528) in .Net 2.0 Application Development Divya Anilkumar Contact Details Home Address: 6 Tarry Hill Dr, New City, NY 10956. Primary Phone 973-444-4178 Secondary Phone 201-450-1120 CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix E - Page 16 Jerves Vasco Antao 720 Hamilton Street Unit C Harrison NJ 07029 USA (862) 754-9962 | jerves.antao@gmail.com Objective: With a great academic record and about 4 years of .NET experience including a great learning experience in a startup company, I hope to be a valuable addition to your organization Professional Summary: • Worked extensively on Winforms to create desktop applications along with the setup for installation. • Proficient in using multithreading to improve performance of applications • Worked extensively on Silverlight applications using WCF services and deploying them • Extensive experience in ASP.NET building web applications, many of which used forms authentication along with concentration on secure coding practices • Extensive experience with building SQL Server Databases having designed it from the requirements along with maintenance, deployment and upgrades • Extensive experience creating WCF services and deploying them. These services were used by desktop as well as Silverlight applications • Extensive experience creating deployment packages for all applications including deployment of web services and web applications on IIS servers. • Proficient in database programming with extensive use of ADO.NET, LINQ, Entity Framework and ORM to work with different databases including MS SQL, SQL CE, MS Access and SQLite • Experience using Telerik products including Telerik controls for Winforms, Silverlight and Telerik Open Access • Experience in generating reports using Telerik Reporting • Demonstrated ability to learn new tools and API in a short time including Northwoods GoDiagram and GoXam API designer tools and LogicNP CryptoLicensing API licensing tools • Experience using Microsoft Enterprise Library as a part of secure coding practices like encryption and validation • Experience in a team lead position handling a small teams of developers (1 to 4) • Experience in all phases of SDLC and N-Tier Architecture Technical Skills: • .NET related experience: o C#, Winforms, ASP.NET, WCF, Web Services, ADO.NET, Silverlight, WPF, XAML, LINQ, Entity Framework, XML, IIS 6/7, Deployment and Setup, SMTP, Multithreading, Microsoft Enterprise Library, Secure Development Practices • Other .NET related third party tools used: o Telerik controls for UI (Winforms and Silverlight), Telerik Reporting, Telerik Open Access (ORM), Northwoods GoDiagram API, LogicNP CryptoLicensing API for licensing • Databases: o MS SQL Server, SQL CE, MS Access, SQLite • IDE: o MS Visual Studio 2008/2010, MS SQL Server Management Studio 2008 • Others: o C, C++, HTML, assembly language on 8085 and 8086 microprocessors, Matlab. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix E - Page 17 Work Experience (Summary): • MyAppSecurity Inc. (Hoboken, NJ) – January 2011 to June 2012 ▪ Lead the product development of a threat modeling tool in this startup company. The main products consisted of a desktop application which was a threat modeling tool, a Silverlight application which enabled collaboration between users and a web application that was basically managing data – all of which we designed, developed and managed by me. ▪ Secure development practices was an integral part of coding ▪ Developed the products which included a desktop tool that allows users to work locally and also a Silverlight version that enabled collaboration between different users. The desktop tool also allowed syncing with the centralized server using WCF services. This also included installation and deployment of the applications. ▪ Created, configured and installed all the WCF services that were used by the applications ▪ Designed and built the MS SQL Server database based on our design. SQL CE was used for desktop applications. ▪ Created a web application using ASP.NET called ThreatLibrary and deployed it on IIS server ▪ Participated in the design and architecture of the system all the way from requirements to the deployment ▪ Used the ADO.NET framework along with Telerik ORM, Entity Framework and LINQ for database programming in different applications ▪ Used the Northwoods GoDiagram API to create a designer tool that enabled users to create flowcharts and diagrams ▪ Used LogicNP CryptoLicensing API for licensing of our product – allowing evaluation licenses as well as registered ones ▪ Acted as the product manager for the independent modules that were outsourced for development performing the role of a team lead for small groups of developers • Infosys Technologies Limited (Pune, India) - October 2007 to July 2009 ▪ Designed, developed and maintained a web application based on the .NET Framework ▪ This was an inventory management system which kept a track of all the machines that were in our internal network. It displayed data about the machines, enabled a lot of remote functionality and other user related tasks to be performed. ▪ ASP.NET was used to build the web application and ADO.NET was used for database access to an MS SQL Server ▪ The web application was deployed on IIS server ▪ SMTP was used to send email notifications based on the requirements ▪ The application also enabled generation of reports ▪ The application had a dashboard which displayed data needed by the management. This was created using WPF. Educational Qualification: • MS in Computer Science and Engineering at University at Buffalo – September 2011 ▪ GPA – 3.793 • Bachelor Of Engineering in Electronics and Telecommunication - May 2007 ▪ 73.16% - Distinction grade ▪ 20th in the university (Mumbai University) • Higher Secondary Certificate (Grade 12) in Science – February 2003 ▪ 90.33% - Distinction grade • Secondary School Certificate (Grade 10) – March 2001 ▪ 89.33% - Distinction grade ▪ 1st rank in school CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix E - Page 18 Anuradha Chaudhary 91-18 121 street, Richmond Hill, NY 11418 (646)-944-0207 anuchaudhry90@gmail.com EDUCATION New York University, New York May 2015 Master of Science, Computer Science GPA: 3.57/4.0 Panjab University, India May 2008 Bachelor of Engineering, Information Technology GPA: 3.8/4.0 TECHNICAL SKILLS • Languages : C#.NET, VB.NET, Android J2EE, C, C++,Java • Databases: MS SQL Server 2014, MySQL • Web Technologies: ASP.net, ASP.net MVC5,ASP.net web-forms and win-forms, HTML5, CSS, JSON, AJAX, JavaScript, JQuery, Responsive Web Design using Bootstrap , XML, AngularJS, OData, Angular 4 • Tools: Microsoft Visual Studio 2015 with .net 4.5 framework, Eclipse, Team Foundation Server (TFS), Tortoise Subversion (SVN),Visual Source Safe, GitHub, ADO.net, Entity Framework, SSRS,SSIS,LINQ, Amazon Web Services, Sharepoint 2013, Telerik/Kendo Controls, Dependency Injection Frameworks. • Process Knowledge: Experience in all phases of SDLC i.e. design, development, testing, maintenance. Used waterfall and agile/scrum methodologies in web development projects. Understanding of Web services, Web API, AngularJS and design patterns. GRADUATE COURSES Mobile Application Programming in Android Introduction to Java Design and Analysis of Algorithm Application Security Cloud Computing Human Computer Interaction Computer Networks PROFESSIONAL EXPERIENCE Software Developer, Williams Lea/Bank of America, New York (asp.net MVC5, C#, vb.net, EF6, Moq) Jan 2017 – Aug 2018 • Developed, tested and maintained portal application to be used by bankers to raise service requests using kendo controls. • Involved in maintenance and enhancement of the existing web form application used internally to track status of the received tickets and various internal tasks. • Responsible for gathering requirements, creating storyboards, developing and unit testing a new Quality Assurance web application to be used internally for auditing purposes. The application replaced the existing access based application. • Developed a sharepoint application to automate the onboarding and off-boarding process for employees and maintaining information of new/old employees using AngularJS and sharepoint REST service API’s. Programmer Analyst II, Mount Sinai Health System, New York (asp.net MVC5, C#, EF6, Linq, Jquery) July 2015 – Nov 2016 • Developed, tested and maintained various scheduling applications for doctors in Asp.Net MVC 5/Razor engine enhanced using jquery plugins and twitter bootstrap with Entity Framework to schedule various calls, assignments and timeoff details. • Developed, tested and maintained applications for Queens Hospital of Mount Sinai to schedule calls for doctors and provided a calendar interface to create and drag and drop calls on the calendar directly for better user experience. • Developed a new MVC5 application for the hospital to replace existing access based application for scheduling calls, assignments, timeoffs and daily schedules for attendings, residents and crna adding extra features of exporting and printing. • Developed SSIS job to save XML files generated from stored procedure which was later replaced by console application developed by me. • Developed console applications in C# to save XML files generated from stored procedure for every case happening in department and validate them against an XML Schema and zip the validated file to send it to SFTP server for Anesthesia Quality Institute compliance. The applications were automated to run as windows scheduler tasks. • Developed and tested stored procedure in for payroll calculations to replace Access based system. • Extracted business rules from the stored procedure formed for management to understand the rules. • Responsible for applying new changes coming in from the management and maintaining the payroll system. • Developed SSRS reports and related stored procedures for various modules for department. • Collaborated and developed reports for the pharmacy department to help them work with controlled substance abuse. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix E - Page 19 • Created tableau dashboards for the management for comparing data from previous years. Software Intern, Allianz Global Investors, New York June 2014 – Aug 2014 • Analyzed ETL tools used in the company and helped with mapping documents for existing data feeds. • Tested data feeds and spotted inconsistencies across various data staging area. Software Engineer, Accenture, India (C#.net, asp.net, ado.net, SQL Server) Dec 2010 – Aug 2013 • Analyzed requirements and designed UML diagrams using Visio/Sparx for the use-cases assigned. • Designed webpages/winforms and implemented backend for the stories. • Created and parsed a XML file using XSLT to give access permissions to different types of users based on role. • Implemented code to import from MS-Excel and export to MS-Excel for win-form application. • Created functional test plans and participated in code reviews discussions with clients. • Responsible for developing unit test cases (NUnit/Mock), unit testing and defect fixing of code. • Involved in application maintenance and enhancements for win-form application. • Analyzed performance tuning issues in code and SQL using FxCop, SQL Lint and Fiddler respectively. • Awarded speedster award twice for meeting deadlines in time and saving hours from estimated time. Software Engineer, Infosys, India (C#.net, asp.net, ado.net, SQL Server) Dec 2008 – Dec 2010 • Developed web pages, implemented front end and back end for an internal tool used for employee transfers. • Consumed existing web service to authenticate users. • Developed tables, stored procedures and triggers. The tool was nominated for fame award. ACADEMIC PROJECTS Introduction to Java Fall 2014 Fall 2014 • Implemented assignments to understand OOPS concept, generics, collections, concurrency (multi-threading), and JUNIT. Human Computer Interaction (Study Time Management) Fall 2014 • Interviewed students, professors and teaching assistants to help decide the target audience for the app. • Developed story boards to realize and analyze our scenarios better. • Developed two versions of prototypes for the users to play with the app and give us their feedback. • Responsible for usability testing and heuristic evaluation. Revelio (Mobile Apps -Android Programming using Java) Spring 2014 • The tool helps display the events taking place in NYU- Brooklyn Campus. • Implemented loading of camera view to detect buildings pointed at and overlayed it with list views to display the various events. (GitHub /MVC) ETA (Mobile Apps- Android Programming using Java) Spring 2014 • Designed various activities to create, view and edit trip and updating ETA based on location of persons using JSON. Travel Companion (Cloud Computing using Java) Fall 2013 • The application suggests user the places to visit. • Implemented fetching of user data using Facebook Graph API (REST) and database using Amazon AWS service RDS. Online Test (Java, Undergrad) Fall 2006 • Implemented using applet and swing components and created JDBC connections to connect to database. Linked in: https://www.linkedin.com/pub/anuradha-chaudhary/a2/194/145 CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix E - Page 20 Sreekumar K. Neelamana Summary ▪ 15+ years of Software Development and Systems Analysis experience in United States, United Kingdom and India with extensive computer skills in Microsoft Windows n-tier, Client Server and Web Solutions Programming. ▪ Experience in Analysis, Design, Development, Testing, Implementation, and Training and Support phases of Software Development Life Cycle (SDLC). ▪ Experience Managing and Leading software development teams. ▪ Bachelor’s degree with Major in Computer Science & Engineering. Professional Experience 1. EXPERIENCE I From 3/2002 – Present. CourtAlert. As Programmer Analyst/ Team Leader ▪ Lead a team of developers for CourtAlert CM/ECF, CourtAlert’s Case Management and ECF Interface software. ▪ Developed Client Server and Web Applications for Case tracking, using Visual Basic, SQL Server, ASP, VBScript, JavaScript, HTML, DHTML, IIS, Scan soft Omni page OCR, MS Excel, VBA, ADO, T-SQL, Stored Procedure etc. ▪ Maintained, enhanced and supported websites such as www.CourtAlert.com, NYCLAW.CourtAlert.com and Appeals.CourtAlert.com. ▪ Developed and implemented application for processing NYC Civil decision list and send out email alerts. ▪ Developed and implemented application for processing Appellate Division/1st Dept. decision list, Appellate Division/2nd Department decisions, Appellate Term information and Second Circuit information. 2. EXPERIENCE II From 3/2000 – 2/2002 R Systems Inc El Dorado Hills, CA (A SEI-CMM Level 4 Service company) As Application Programmer ▪ Performed Analysis, design of Detailed Functional Specification, Coding and Testing for PASSGEN, DOCUMENTVALIDATION and CORRESPONSDENCE modules of eCAP product. ‘eCap’ is a check and list processing software ▪ Designed and developed IFOLOADER application for creating Work items and upload documents with index values to FLOWARE activity queues for various clients of ADP, Islip, NY. ▪ Lead the team for customizing Plexus FLOWARE 5.1, a state of the art Workflow automation software, and IMAGEFIRST Office 4.21, an image archival and organizer. ▪ Worked as a Project Leader for Developing IFO Image Retriever and Viewer for On-Line PEND Application. ▪ Developed Health Insurance Claim forms processing system to OCR and process claims like HCFA, UB-92, ADA etc and export captured and edited data to output files for mainframe. ▪ Worked as a Project Leader for developing IFO Image Viewer Enhancements, Application Monitor, CRNCollect ActiveX control for SPEEDFIRST for Scanner, Image Storage and Retrieval System, IFO Upload and Formware Export Modules. 3. EXPERIENCE III CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix E - Page 21 From 7/1996 - 2/2000 DSS InfoTech (P) Ltd. PUNE (An ISO 9001 Certified Company) As Senior Systems Analyst ▪ Lead development team for On-line Process Quality Management System, Version 2.0 for multiple clients. ▪ Lead a development team for Oakwood Systems, London, UK for their software projects in Human Resource Management. ▪ Lead development team for RAPID (Relational Application for Process and Instrumentation Diagrams) for Intelligent Computing Solutions, London, UK. ▪ Developed Production Planning and Inventory Control software for Indian Seamless Steel and Alloys Ltd., PUNE, India. ▪ Developed Online Process Quality Management System (Version 1.0) product for part manufacturing industries all over India. ▪ Part of development team for Statistical Process Control application for Mahindra Sintered Products Ltd., PUNE, India. 4. EXPERIENCE IV From 9/1998 - 3/1999 ICONSOFT Winchester, Hampshire, UK As Systems Analyst • Lead an onsite Development team from DSS InfoTech (P) Ltd., PUNE, INDIA. • Lead enhancements and customizations of multiple Software products of ICONSOFT that were implemented in Cinemas worldwide. • Designed and lead the team for developing Automated Ticketing Machine Software for ticket vending. • Lead development team for Site Voice Server (Interactive Voice Response System). • Lead development team for Concession Server Application. 5. EXPERIENCE V From 8/1995 - 6/1996 VICE BANGALORE, India As Programmer & Center in Charge ▪ Was In charge of the project department. ▪ Developed and guided projects for Government Polytechnic, KORAMANGALA in ‘C’ language. Technical Skills GUI: VB.NET, Visual Basic 6.0/5.0, VC++ 6.0, Formware 2.5/ 4.51 RDBMS: SQL Server 2005/2000/7.0/6.5, Oracle, Access LANGUAGES: VB.net, C#, C, Java, SQL, T-SQL, VBA CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix E - Page 22 NETCENTRIC: ASP.net, ASP, HTML, DHTML, CSS, VBScript, JavaScript, IIS TOOLS: Visual Source Safe, Crystal Reports, PVCS, TOAD, Install Shield OPERATING SYSTEMS: Windows 2003, Windows 7/Vista/XP, Windows 2000, Windows NT 4.0, Windows 9x, Windows 3.x, Unix, MS-DOS Personal Skills ▪ Management Skills ▪ Planning and Organization Skills ▪ Multi-tasking skills ▪ Leadership skills ▪ Team player skills ▪ Communication skills ▪ Time and Resource management skills Education Four - Year degree in Bachelor of Engineering with Major in Computer Science and Engineering Certifications Certified Professional in Visual Basic .NET from Brainbench. CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix E - Page 23 Yael Martin, Esq. 215 West 95th Street Apt. 11H New York, NY 10025 (914) 843-6739 Yael@CourtAlert.com ADMISSIONS Admitted to practice in New York State, 2012 EDUCATION Juris Doctor Brooklyn Law School, Brooklyn, NY, May 2011 Activities: Business and Finance Society, Brooklyn Real Estate Society B.A., Political Science Yeshiva University, New York, NY, May 2007 Awards: Senator Carl Kruger Award for Community Service; Award for Exceptional Leadership and Service; Award for Outstanding Student Leadership Activities: 2007 Class President; Observer (College Newspaper); The Joseph Dunner Political Science Society PROFESSIONAL EXPERIENCE CourtAlert®, New York, NY Client and Court Relations Spring 2007- Present Provide periodic, hands on training sessions and support for CourtAlert clients. Develop and maintain relationships with local courts. New York County Supreme Court, New York, NY Intern for Chief Clerk Hon. John Werner Summer 2006 Worked directly for the Chief Clerk’s office, became familiar with Supreme Court and the other New York courts in the Foley Square area. Drafted briefs on motions for review by judges and court attorneys. Prof. Alan Dershowitz - Harvard University, New York, NY Research Assistant Fall 2006; Spring 2007 Conducted legal research for Professor Dershowitz in New York for motions submitted to the International Court of Justice. Open Tunnel, Jerusalem, Israel Legal Research Intern Summer 2004 Conducted legal research regarding advocacy for women denied divorce. COMMUNITY ACTIVITIES National Council for Disabilities- weekends and holiday programming CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix E - Page 24 CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix D - Page 1 CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix D - Page 2 Partial List of Clients of the Software Confidential Account Name State of Rhode Island* Weil Gothshal & Manges Shaub Ahmuty Citrin & Spratt Keller Lenkner Carter, Ledyard & Milburn Bernstein Litowitz Berger & Grossmann LLP Rosenberg & Estis Harris Beach LLP Allen & Overy Cravath, Swaine & Moore LLP Lane Powell Gibson Dunn & Crutcher LLP Akin, Gump, Strauss, Hauer & Feld LLP Michael, Best, & Friedenrich WilmerHale, LLP Friedman Kaplan Seiler & Adelman LLP Mound Cotton & Wollan & Greengrass Cahill Gordon & Reindel Katten Muchin Rosenman LLP Fried, Frank, Harris, Shiver & Jacobson LLP Kelley, Drye & Warren LLP Paul Weiss Rifkind Wharton & Garrison LLP Shearman & Sterling, LLP Suffolk County Department of Law Debevoise & Plimpton Willkie Farr & Gallagher LLP Davis Polk & Wardwell LLP Mintz Levin Cohn Ferris Glovsky & Poper. Wachtell, Lipton, Rosen & Katz Kramer Levin Naftalis & Frankel LLP Patterson, Belknap, Webb & Tyler, LLP Ropes & Gray LLP Cadwalader, Wickersham & Taft LLP Greenberg Traurig LLP Moses & Singer LLP Cleary Gottlieb Steen & Hamilton LLP * Implementation in progress CourtAlert Response City of Pittsburgh RFP# 20000339 LCMS Appendix C - Page 1 CourtAlert Response to Bozeman City Attorney CMS RFP 1 CourtAlert Case Management System - Cost Proposal There are four components of the cost 1. Licensing Fee - This is the charge to license the Software as is, payable in three installments: a. $25,000 before the Software is installed b. $15,000 when the first Department is operational, the City Attorney will decide which Group is the first one c. $10,000 when the system is completely running in production Total license fee is $50,000. 2. Monthly maintenance/upgrade fee, $2,000 a month, which is $24,000 per year. Monthly maintenance/upgrade fee to start after the Software installation. 3. Hosting: based on the expected usage cost of hosting costs is $800 a month, which is $9,600 per year. 4. Conservative estimated cost of configuration, programming, CourtAlert project management, meetings, travel cost etc. We believe many functions are configurable. The estimated cost is $25,000 on the first year, and we certainly contemplate completing the project within a year. This includes a full-time project manager for the project. We added a reserve of $5,000 budget for each subsequent year for changes of the requirements. CourtAlert Response to Bozeman City Attorney CMS RFP 2 BREAKDOWN BY YEAR Base Contract Years Implementation Fee Year 1 Fee (starting on first Production Use) Years 2+ Payment milestones n/a Installation of the software as is $25,000.00 First Group Operational $15,000.00 Second and Third Groups Operational $10,000.00 Application Support $24,000.00 $24,000.00 Hosting n/a $9,600.00 $9,600.00 Professional Services Estimated Programming, etc. $25,000.00 $5,000.00 (optional) Total $75,000.00 $33,600.00 $38,600.00 CourtAlert: _________________________________ Authorized Signature Yaniv Schiller___________ Print Name President______________ Title 08/27/2021____________ Date Attachment A NONDISCRIMINATION AND EQUAL PAY AFFIRMATION name of entity submitting) hereby affirms it will not discriminate on the basis of race, color, religion, creed, sex, age, marital status, national origin, or because of actual or perceived sexual orientation, gender identity or disability and acknowledges and understands the eventual contract will contain a provision prohibiting discrimination as described above and this prohibition on discrimination shall apply to the hiring and treatments or proposer’s employees and to all subcontracts. In addition, ____________________________________(name of entity submitting) hereby affirms it will abide by the Equal Pay Act of 1963 and Section 39-3-104, MCA (the Montana Equal Pay Act), and has visited the State of Montana Equal Pay for Equal Work “best practices” website, https://equalpay.mt.gov/BestPractices/Employers, or equivalent “best practices publication and has read the material. Name and title of person authorized to sign on behalf of submitter CourtAlert.com, Inc. CourtAlert.com, Inc. Yaniv Schiller President CourtAlert.com