7 - EPS System Architecture redacted.pdf
PDF 365 KB Posted
- Attached to
- Lotus Notes
- Solicitation number
- 9531BP-22-RFI-0001
- Issued by
-
Federal Election Commission
View the file
Other files
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Federal Election Commission
CMS Upgrade Project Enforcement Priority System
Architecture
Version 1.0 10/04/2012
Federal Election Commission 999 E Street, NW
Washington, DC 20210
Prepared by Bridgeway, Inc.
Federal Election Commission EPS System Architecture
Document Change History
Date Version Number
Submitted By Change Reference
10/04/12 1.0 Bridgeway Software Original Draft
TABLE OF CONTENTS
Purpose System Name System Owner ................................................................................ Error! Bookmark not defined.
Points of Contact ............................................................................ Error! Bookmark not defined.
System Location System Description System Environment System Interfaces/Interconnections System Operating Times System Software Components System Hardware Components System Inputs System Outputs Business Rules Data Migration Contingency Plan Security Controls ........................................................................... Error! Bookmark not defined.
Purpose
The purpose of this document is to represent the Federal Election Commission’s (FEC) Enforcement Priority System architecture.
System Name
Enforcement Priority System (EPS) is an in-house developed solution which prioritizes cases.
System Location
All servers are physically located in Sterling, Virginia Use Location Backed Up Backup Location
Production Y Production Y Development Y Test Y
System Description
The purpose of EPS is to bring in LM Pro data (staff names, complainant/respondent names, Statute of Limitations dates, Complaint received dates, etc.) into a view for the CELA DOCKET staff person who is reviewing and analyzing a complaint based on legal and other considerations.
When the review is approved in EPS, it is categorized by EPS, and analytical categorization is automatically transferred into LawManager Pro (when the staff person clicks APPROVE in EPS). The analysis remains part of the case file, circulated to the managers and the Commissioners, shortly after the complaint is received. After an initial analysis occurs, a case can be re-analyzed by Enforcement staff after the case is activated (assigned to a staff attorney).
The User Community would include: CELA Docket (as main users of the system), General Counsel staff and Managers (as potential users of the system) and Commissioners and Commissioner EAs (as recipients of the printed rating sheets)
System Environment
System Interfaces/Interconnections
EPS is a Lotus Notes Application on a Domino Server. The User interface is thru Microsoft Edge (users use a web browser accessed through a URL. The User is authenticated through their Domino/Lotus Notes ID (username and password), not through Active Directory. The bridge between the Domino database and Lawmanager Pro is a java servlet on tomcat.
A request is sent from EPS to the servlet. The request contains URL parameters which are used by the servlet to perform SQL operations in LM Pro. The servlet uses the attached to an xml file to determine which SQL operation to execute based on the passed parameters. The servlet then returns the operation results as an xml stream to EPS. EPS then parses and displays the results, displaying the results as URL links using a combination of notes views, css and xsl style sheets.
If a link, or record, is opened in EPS, this either opens a Lotus Notes document or form but either one triggers a request to the servlet to return that individual case data from LM Pro.
Staff then applies ratings to the individual case (via radio buttons, primarily) which automatically accrues the total ratings points. After approval, EPS sends another request to the servlet sending in the final analytical data for the individual case into LM Pro, Cases can also be re-analyzed and these are handled in the same manner. The SQL for these operations (approve and re-approve) are also found in the attached to the xml file.
System Operating Times
Normal Operating Critical Operating Days Times Days Times M-F 7am – 6pm
System Software Components
1. Lotus Domino 8.5.3 (host of EPS system) Microsoft Edge (user interface for EPS system)
2. Apache Tomcat Servlet jtds-0.8 jar (SQL driver) jre 1.4.2_05 (java runtime environment)
System Hardware Components All servers are physically located in Sterling, Virginia
1. FECAS003 – Production Microsoft Windows Server 2003 Intel Xeon CPU 2.40Ghz
2.39 Ghz, 2.0GB of RAM
2. FECAS004 – Cluster Microsoft Windows Server 2003 R2 Intel Xeon CPU 5160 @GHz 3.0Ghz, 3.25GB of RAM
3. FECDS004 - Development Microsoft Windows Server 2003 Intel Xeon CPU 2.80@GHz 2.79Ghz, 1.0GB of RAM
System Inputs
Process Format By Whom/Application
Frequency
Case History Review LawManager Pro Real Time
Users enter information into the Microsoft Edge EPS interface, and this information is passed to LawManager via the servlet.
System Outputs
Process Format By Whom/Application
Frequency
LawManager Pro Java Script EPS Real time triggered by rating updates
Business Rules
Upon receipt of a new case, CELA Docket staff begins entry in LawManager Pro, designating receipt date, known players (complainant, respondent, staff), Statute of Limitations date, and Case Type, Case Number and Case Name. CELA Docket staff then go to EPS, open it up, select the case to rate it, and designate (by picking radio buttons) the severity of the issues. This is the draft analysis sheet. It is (within a short time) approved by a CELA Manager/Staff. Upon manual APPROVAL in EPS, the analysis categories are input into LawManager Pro.
Data Migration Not applicable
Contingency Plan Not applicable
File details come from the government source that posted it. Updated .