210 likes | 268 Views
This dossier covers the DAT project for Academic Personnel tracking at UCLA, focusing on objectives, technology development, and next steps. It includes information on project background, technical architecture, development partners, and project timeline.
E N D
Dossier Action Tracking (DAT) Project Overview CSG Technical Review Presentation Office of Information Technology Rose Rocchio
Presentation Outline Background Technology Next Steps Q & A
Background Technology Next Steps Q & A
BackgroundBusiness Challenges • No ability to track the Academic Personnel (AP) process across organizational boundaries • No electronic official “historical record” • Duplicate data entry (4X) • Difficult to enforce campus deadlines (1500 reviews/year) • Complex appointments are increasing (joints/splits)
BackgroundDAT Project Objectives • Facilitate AP review process by creating a single action tracking data repository • Create an official electronic “historical record” • Eliminate duplication of data entry • Provide automation for eligibility business rules • Consolidate AP databases to seed new db
Background Technology Next Steps Q & A
TechnologyDevelopment Partners • The Life Sciences Division • Dossier system had 38% of planned data model • Partnered to provide a more powerful suite of tools • Engineering • They had just consolidated their data into the Dossier system & had a developer eager to help • The College • Providing a .NET development environment • Will host the production version
Client Tier Application Tier Data Tier RDBM TechnologyApplication Architecture • Web-based application for accessibility • 3-tier architecture for scalability • MS .NET technology for interoperability IIS 6.0 Web Application Server Farm Browser .NETFramework OS
Database Server TechnologyTechnical Architecture Dev & Test Environment ( College Information Services /LS computing) Internet Test Server Firewall with Dev Web Server ( DB & File ) VPN Access only e n o b k c a B Production Environment B DAT Development Team ( College Information Services) G - 2 s u p m a C A L Backup C Internet U Firewall Web Server Farm Hourly transaction log backups – Nightly 2 stage backup End Users
TechnologyHardware Specifications (current production – have project $ earmarked for upgrades) • Up to 250 active execution tasks
ISIS (AIS) LEAD (AIS) Info Ed (ORA) Web Svc. SOM (Access/ SQL Server) PP-QDB (CHR) Faculty Department Dean’s Office APO CAP TechnologyIntegration with other UCLA systems DOSSIER (The College) DAT (The College) QDB (AIS)
Project Background Technology Next Steps Q & A
2004 Q2 Analysis & Design Creation of detailed functional specifications 2004 Q3 Development Embarking on Development phase 2004 Q4 Test / Training Will Beta test each module with a pilot user team 2005 Q1 Production User acceptance and system deployment Next StepProject Timeline
Next StepsImmediate Tasks • Functional Team: • Design of remaining modules (Dean’s Office, APO/CAP & Sys Admin) • Development Team: • Develop AT department & faculty modules • Analyze and design interfaces to UCLA systems • Database Consolidation Team • Import all available history (QDB, Access Systems, Spreadsheets)
Project Background Technology Next Steps Q & A
Q & A Questions & Answers
Thank You! Rose Rocchio (x5-3981) rrocchio@oit.ucla.edu