Emissions Collection and Monitoring Plan System Technical Architecture

1
Emissions Collection andMonitoring Plan
SystemTechnical Architecture

• Stakeholder Meeting
• May 2, 2005
• David Ward, PQA

2
Requirements

• Replace the use of the mainframe
• Provide a Client Tool that interacts with the
  CAMD database
• Maintain a Client Tool database for local data
  storage and processing
• Synchronize data between the Client Tool and the
  CAMD database
• Leverage existing re-engineered data structures
  and processes

3
Technical Architecture
4
Technical Architecture

• Visual Studio .NET (Client Tool, Business Logic,
  and Server-Side Processes)
• MS SQL Express 2005 or MS SQL Server (Client Tool
  database)
• Oracle (CAMD database)
• ColdFusion MX (Web services on CAMD Web Server)

5
Client Tool Configurations

• Single Workstation
• Workstation(s) and Database Server with MS SQL
  Express 2005 or MS SQL Server

6
Client Tool Configurations
7
Minimum System Requirements

• Single Workstation with Client Tool and MS SQL
  Express 2005 Database
• 300 MHz processor
• Windows 2000/XP Pro
• 512 MB RAM
• 7 GB free disk space

8
Minimum System Requirements

• MS SQL Database Server for Multiple Workstations
  
• 733 MHz processor
• Windows 2000/Server 2003
• 1 GB RAM
• 8 GB free disk space

9
Client Tool Security

• Local Client Tool database security maintained
  through single user
• Client Tool provides access through basic user
  name and password security

10
Access to CAMD Database

• Users registered with the CAMD Business System
  will have access to their data
• CAMD Business System users will be able to
  designate agents to perform specific tasks

11
Technical Concerns

• Processing Performance
• Data Retrieval Performance
• Version Control
• Data Synchronization
• Record Locking