Emissions Collection and Monitoring Plan System Project Stakeholder Update February 9, 2006

1. Emissions Collection and Monitoring Plan System Project Stakeholder Update February 9, 2006 Washington, DC By Clean Air Markets Division

2. Meeting Objectives • Overview • Alpha testing update • Review technical architecture • Discuss version management of the ECMPS Client Tool

3. Meeting Objectives (continued) • Review of XML file format • Demo of the ECMPS Client Tool • Discuss categories of checks • Questions and Answers • Wrap up

4. Overview • Create a single, more flexible tool for users to check, store, maintain and submit data • Replaces ETS-FTP, SecuRemote, ETS Mainframe, MDC, some paper forms • Enable users to run checks on their desktop and make revisions, prior to submitting to EPA • Eliminate multiple sets of feedback • Take advantage of newer technology

5. Alpha Testing Update • Plans for alpha testing are on schedule • Testing is scheduled for April through mid-May • Testers include a cross-section of industry and DAHS vendors • EPA estimates it will take approximately 10 hours to test alpha version functionality

6. Alpha Testing Update (continued) • Functionality: • General installation and setup of software including MS SQL Express 2005 • Internet connectivity to the EPA Host System to test web services • File Import of XML files for Monitoring Plan, QA/Cert Test, and Emissions data • File Export of XML files for Monitoring Plan, QA/Cert Test, and Emissions data • Reports, including reports for Monitoring Plan and QA/Cert Test data

7. Alpha Testing Update (continued) • Functionality (continued) • Review of imported Emissions data (prior to evaluation and calculations) • Limited evaluation of Monitoring Plan, QA/Cert Test, and Emissions data • Submission of Monitoring Plan, QA/Cert Test, and Emissions data to the EPA Host System via web services • Retrieval of complete Monitoring Plan from the EPA Host System via web services

8. Alpha Testing Update (continued) • Alpha testing website, accessible to testers with a user ID and password, will allow them to: • Download software • Retrieve test files • Download relevant documents, including a Getting Started guide • EPA website will have a section for non-alpha testers to access questions, comments, and relevant documents related to testing

9. Alpha Testing Update (continued) • Next test period will begin in January 2007 and is expected to last at least six months • All aspects of the ECMPS Client Tool will be available for testing • All stakeholders will be eligible to participate in the next testing period

10. ECMPS Technical Architecture

11. Technical Architecture Components: • ECMPS Client Tool • MS SQL 2005 Database • EPA Web Server • EPA Host System

12. Technical Architecture

13. Technical Architecture Components: • ECMPS Client Tool • Desktop application • Typical software installation • Imports data files (XML file format) • Evaluates data files • Submits data files to EPA Host System • Controls all communication with EPA Host System

14. Technical Architecture Components (continued): • MS SQL 2005 Database • Provides local storage of data for ECMPS Client Tool • No direct connection to EPA Host System • Installed version is MS SQL 2005 Express • ECMPS Client Tool can also connect to MS SQL Server 2005

15. Technical Architecture Components (continued): • EPA Web Server • Hosts web services • Receives communication initiated from ECMPS Client Tool • Provides authentication services • Passes data to EPA Host System • Returns requested data to ECMPS Client Tool

16. Technical Architecture Components (continued): • EPA Host System • Oracle database which stores requested data • Connects to CAMD Business System data • Controls flow of reported data and data requests

17. Technical Architecture • Visual Studio .NET (ECMPS Client Tool, business logic, web services, and server-side processes) • MS SQL 2005 (ECMPS Client Tool database) • Oracle (EPA Host System database)

18. ECMPS Client Tool Two Configurations: • Single workstation • Workstation(s) and database server with MS SQL 2005 Express or MS SQL Server 2005

19. ECMPS Client Tool Configurations

20. Minimum System Requirements Single Workstation with ECMPS Client Tool and MS SQL 2005 Express: • 600 MHz processor, P3 compatible • Windows 2000/XP Pro • 192 MB RAM • 7 GB free disk space

21. Minimum System Requirements MS SQL Server 2005 for Multiple Workstations (Database Server): • 600 MHz processor, P3 compatible • Windows 2000 Server/Server 2003 • 512 MB RAM • 8 GB free disk space

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

23. 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

24. Version Management of theECMPS Client Tool

25. Version Management • Basic Concepts • Handle through the ECMPS Client Tool as much as possible • Provide sufficient notification of version changes • Minimize the number of version changes • Minimal version compatibility required

26. Version Management • Three Levels of Version Management • Major • Minor • Revision • Example 1.2.5 (Major.Minor.Revision)

27. Version Management • Major Version Change • Involves a major modification to a key process or function • Rarely done • Requires reinstallation of ECMPS Client Tool • Requires installation software

28. Version Management • Minor Version Change • A modification which affects all users • Prevents data submission • Requires a patch to be installed • Provide various methods to apply patch

29. Version Management • Revision to a Version • Affects a limited number of users • Does not necessarily prevent submission • Requires a patch to be installed • Provide various methods to apply patch

30. Version Management • Version Compatibility • Check version during login to EPA Host System • Notify of upcoming version changes through alerts • Provide additional information on EPA website

31. XML File Format

32. XML File Format • XML File Types for ECMPS • Monitoring Plan Data • QA and Certification Data • Emissions Data

33. Example XML File

34. XML Basics • XML is for structuring data • XML looks like HTML • XML is text • XML is verbose by design • XML is defined by an XML Schema

35. XML is for Structuring Data • XML provides guidelines for arranging the text to structure the data • XML is NOT a programming language • XML enables computers to generate data, read data, and pass data to other computers

36. XML is for Structuring Data • XML is • Extensible • Platform-independent • Unicode compliant

37. XML Looks like HTML • Similarities • Both use tags • <p></p> • <UnitData></UnitData> • Both use attributes • name=“Value”

38. XML Looks like HTML • Differences • HTML specifies what each tag means • HTML defines how the text between tags is displayed • HTML is used for formatting

39. XML Looks like HTML • Differences (continued) • XML is case-sensitive • XML uses tags to delimit data • XML leaves the interpretation of the data up to the application

40. XML is Text • Data stored as text can be read without application • Text format allows for debugging • XML format is not as forgiving as HTML • Leaving off a tag will cause an error • Applications which use XML are not expected to second-guess

41. XML is Verbose by Design • All the additional tags add up to a larger file • No real disadvantage to larger files because • Disk space is inexpensive • Files can be easily compressed

42. XML File is Defined by an XML Schema

43. XML File is Defined by an XML Schema • Root elements • Nesting • Data element • Type • Nillable

44. XML File is Defined by an XML Schema • complexType • minOccurs, maxOccurs • References • Sequence • Keys

45. XML File is Defined by an XML Schema • simpleType • Data types (e.g., date, string, integer) • Enumeration • Union • Validation

46. XML File is Defined by an XML Schema • Data are defined using XML Schemas • Monitoring Plan • Quality Assurance and Test • Emissions

47. Severity Levels of Checks

48. Severity of Checks • All checks will be assigned a default severity level • The severity level of the check indicates whether the checking process should be continued, aborted, or partially aborted based on the failure of the check • Most errors will not prevent the tool from continuing with the evaluation of the file • However, there are some fatal errors that will abort the remaining checks in that process • The error and severity code are recorded for the evaluation reports

49. Critical Level 1 • Most severe error level • Fundamental error that affects the ability of the ECMPS Client Tool to accurately evaluate dependent records or prevents completion of data checks • Error affects the acceptability of dependent files • MP >> QA/Cert Test >>Emissions • If submitted with critical errors, resubmission of the corrected file and all dependent files is required • Not subject to analyst judgment (not likely to be canceled) • Data are not acceptable for compliance determination

50. Critical Level 2 • Severe error that is subject to EPA analyst judgment (can be canceled if warranted) • Error does not prevent the ECMPS Client Tool from completing data checks • Error does affects the acceptability of dependent files • MP >> QA/Cert Test >>Emissions • If submitted with critical errors, resubmission of the corrected file and all dependent files is required • Resubmission of dependent data may be necessary should EPA cancel an error (Process still being developed) • Data are not acceptable for compliance determination until critical errors are resolved