This is a presentation on a class project that i was a part of . The system is built using java, EJB 3.0 using JBoss 5.1 application server

1. CmpE 275 Fall 2009Project 1Highway Emission Monitoring SystemTeam Name:Ants Dhaval Patel 006500481 Shivanshu Singh 006488300

2. High-level system design

3. High-level system design Measure Materials present in the Air and send this data to the DataRecorder at specific intervals of time.

4. High-level system design Records incoming data from the sensors into a DB

5. High-level system design Sensor Location Management component. It maintains sensor location coordinates.

6. High-level system design Listens to PHS client requests and generates an XML file containing sensor readings for the requested Region and within the requested Timeframe.

7. High-level system design Generates KML files for the snapshot of the entire system at the requested Timestamp.

8. High-level system design Acts as the communication medium, allowing asynchronous communication and Loose Coupling.

9. Deployment Config.java Stores the various configuration parameters which must be set before compiling and deploying. Paths: HOMELOCATION it’s the root of the project location. E.g. if the project name is Project1-Ants and the path of this folder is /Users/shivanshu/LearningSpace/Project1-Ants then HOMELOCATION=“/Users/shivanshu/LearningSpace/Project1-Ants” KML Templates: For use by CCCListener to generate kml files. Store kml template file for each highway at HOMELOCATION/Templates/KML-files Initialization: Run hems.ant.simulation.SensorConfiguration.java Stores the coordinates of sensors in the databse. Jboss: The system supports Jboss 5.1.0 and can be configured for JBoss4.2.3

10. Sensors Two types: CSU – measuring CO2, CO, NO and SO2 ASU – measuring Particulate matter Frequency: Each sensor will send data, which for reasons of modeling the actual system, will be generated in terms of 5 messages per sensor per 0.5 hour. interval of ½ hour is towards giving the server enough time to process requests and persist the data so that an increasing backlog of messages waiting to be processed is not created. can be adjusted accordingly by changing a property in the hems.ant.component.common.Config.java file. Data Packet: TextMessage; format: SensorId,Material,Value,Timestamp System does not verify materialType in the system for flexibility of adding sensors and capabilities of measuring other materials to the sensors and aid adaptability to such changes. SensorId: hhhs-<sensornumber> (case sensitive) sensor sensor sensor sensor

11. Components SCRecorder Main sensor location management component. reads the sensor/location queue for sensor location information TextMessage; format: sensorId,Longitude,Latitude,Altitude Enables the system to be updates on runtime for changes in sensor location.

12. Components SCRecorder

13. Components DataRecorder Records incoming data from the sensor Assumes that the data generation is being done at a set interval of time by all the sensors Timestamp for an instance of data generation will be the same for all the sensors. This is possible if the sensors synchronize their time with a central time sync service. Interval can be set through the SENSORINTERVALMINUTESvariablehems.ant.component.common.Config.java file.

14. Components DataRecorder Checks for Threshold Values. Robust against malformed messages.

15. Components PHSListener Responds to requests (which have to be put into phs/request JMS Queue by the client) Generates XML containing sensor readings for sensors in the given timeframe and region Location: HOMELOCATION/PHS-files/PHS-yyyy-mm-dd-hh-mm-ss.xml Format:<phs_data> <entry>sensorId,materialType,value,timestamp</entry> …. </phs_data>

16. Components PHSListener

17. Components CCCListener Responds to requests (which have to be put intoccc/request JMS Queue by the client) Generates KML for each highway for the snapshot of the system at the requested timestamp. Location: HOMELOCATION/CCC-files/highwayname-yyyy-mm-dd-hh-mm-ss.kml Threshold Values Shows if a certain value goes below or above threshold.

18. Components CCCListener Crosses Threshold Within Threshold

19. Future Work PHS & CCC: Asking the client to specify the file location with the desired filename or actually transfer it to the client. CCC: Currently only 101, 680 and 880 Future work may include generation of KML files for all the highways for which initial kml files are provided, making it a generic tool. DB tuning / alternate persistence and archiving strategies Clustering Web Client for Sensor Location Management