Document 7874277
Download
Report
Transcript Document 7874277
Survivable Network Analysis
Oracle Financial Management
Services
Ali Ardalan
Qianming “Michelle” Chen
Yi Hu
Jason Milletary
Jian Song
FMS Mission Overview
Provide financial service applications
Core Financial Applications
Self Service Web Applications
Application Desktop Integrator Applications
Integrate feeder systems
Facilitate billing, reporting, reconciliation
FMP Deployment Requirements
Support all major campus desktop
platforms
Achieve excellent performance on all
platforms
Implement a ‘thin client’
Minimize software installation, distribution
and maintenance
Leverage existing infrastructure
Mitigate any/all security risks
Users
Casual users
Fulltime users
Expense reports, purchasing
Self-service web application
Business managers, accountants
Desktop applications
Feeder systems
Payroll, grants management, charge back
systems
System Architecture
Backend Data Processing
Layer
Application/Presentation
Layer
Customer Interface Layer
Data Processing Layer
System core layer
Oracle database
Accompanied with concurrent processing and
administration Servers
Offsite machine to serve as backup
Data mirrored every 5 minutes
Physical Layout
Production
Server
Fiber link to campus
Disaster/
Recovery
Machine
Development
Server
Cyert Hall
Machine Room
6555 Penn Ave
Application Layer
Intermediate layer
Includes forms, web, and application servers.
Provides different forms of data presentation
to work with diverse applications
Desktop Client Layer
Customer front-end
Includes all major campus desktop users
‘Thin client’
Supports multiple platforms
Microsoft, Mac and Unix
System Impact
Uptime is not mission-critical
Switchover to backup machine comes at a
cost of 2 days
Feeder systems will function on their own
Most affected
General ledger
Billing/invoice generation
Existing Security Measures
Secure Socket Layer (SSL) for transmission
of sensitive data
Secure Shell (SSH) access
Kerberos identification
Separate realm
Firewall
Disaster/Recovery plan
Piecemeal components
Policies and Practices
Internal
Promote knowledge transfer
Access policies
External
Departmental contact responsible for assigning
rights and privileges within department
Heavy reliance on campus-wide policy regarding
appropriate use of computing resources
Team Activities
Weekly meeting
Evaluating progress and milestone
Assigning tasks to team members
Planning for the next step
Analytical sessions
Analyzing system architecture and
components
Next Step
Next joint meeting on October 10
Document request and gathering
Essential service and asset selection
Scenario traces and components
Disaster/Recovery Plan
Security Policies
Oracle Application Integration Methodology
Field trip to the off-site data center
Project Timeline & Milestones
Client Meetings
Presentations
9/25
9/28
Preliminary
Meeting
10/10
(11/6-11/9)
(11/27-11/29)
Meeting # 2
Meeting # 3
Meeting # 4
11/2
11/14
12/5
Preliminary
Presentation
Presentation # 2
Presentation # 3
Presentation # 4
Team Meetings
- Tuesdays 8:30 - 10:30pm & Sundays 2:00 - 4:00pm
Project Timeline
SNA Phase
I.
II.
III.
IV.
Meeting #1
Presentation #1
Meeting #2
Presentation #2
Meeting #3
Presentation #3
Meeting #4
Final Presentation
September
October
November
December
Project Client Contacts
Primary Contact
Mary Ann Carr, Director of Administrative Computing
Business Needs, Policy Issues, Documentation, Direction
Secondary Contacts
Bob Rittager, Development Team Leader
Brian Gallew,
Security Issues, Integration, Roles & Responsibilities
System Administration, Hardware, Disaster Recovery, Security
Massimo Bigliardo, Database Admin.
Database Administration, Software