Sunday, May 2, 2010
May 2 Meeting
Adam
Arnaldo
Topics:
Blog and Web page
Conclusion:
The web page has not been updated and neither has the blog. The meeting notes should be transcribed to the blog.
The web page should receive an updated.
Work to update both has been divided between each member.
Apr. 28 Meeting
Arnaldo
Adam
Topics:
Thirds Oral Test
Conclusions:
Documentation has not been met to the standards and must be scribed to the correct locations as indicated by previous documents. Also code needs to be documented.
Apr. 9 Meeting
Adam
Arnaldo
Topics:
Work Status
Conclusion:
Software is completed
Hardware is on time with Gantt Chart will be completed before Justas
Mar. 25 Meeting
Adam
Arnaldo
Topics:
Grades on previous Tests
Discuss what where the shortcomings.
Discuss what could have been improved on the progress report
Conclusions:
Progress Report needed to had been compiled earlier.
Some requirements are not understood.
Mar. 22 meeting
Adam
Arnaldo
Topics:
The progress report to hand in.
Status update
Conclusion:
Adam was late his items.
Progress report was divided on equal parts to be written.
Mar. 7 Meeting
Adam
Arnaldo
Topics:
Items completed
Items to be presented for oral exam
Verification of hardware and how it works
Conclusion:
Luminary is doing what is supposed to be doing
Demonstration environment is working
First parts of software are complete and working well
Feb. 23-24 meeting
Adam
Arnaldo
Topics:
Progress Report
Discuss Items needed to hand in for first milestone
Conclusion:
Decided tools to use for generating block diagrams, ER Diagrams
Finished Block Diagrams
Hardware area is reading over data sheets and requirements
Feb 16. Meeting
Adam
Arnaldo
Topics:
Finalize work distribution
Prepare for Proposal Presentation
Conclusions:
Arnaldo will work on the software and manage the over all project.
Adam will work on the hardware and other areas delegated to him.
Jan. 29 Meeting
Adam
Arnaldo
Topics:
Proposal Completion
Executive Summary
Abstract
Risk Management
Tuesday, January 26, 2010
Team Information
Adam Hidalgo
Arnaldo Rivera, Project Manager
Team Meatings:
Will be online Mondays and Wednesdays at 9pm via skype
Project Background:
Project: Industrial Fuel Dispensing Control System
Antecedents:
In industrial and government environment, usually fuel is bought in large quantities and dispensed in small quantities as the need arises. This model of distribution results to be convenient for this type of environment, but leads to other problems that must be controlled in order to have a successful operation and avoid losses.
Problems that may be found in the operation of this model:
• Use of resources by not authorized entities.
• Misuse or abuse of resources by authorized entities.
• Accountability problems – Resources cannot be tracked or assigned as cost to specific projects.
• The responsibility of storing the fuel becomes part of company or government’s responsibility. Making it necessary to create check and balance systems in order to avoid bleeding of fuel.
• It becomes difficult for paper systems to compare data with historic data in order to establish systems, which may lead to avoid abuse of resources.
• It is difficult for remote parties to coordinate fuel purchases.
There are in the market several systems addressing these problems, but in the past had been unpopular because of several reasons among we may find:
• There are huge restrictions in the dispenser equipment that may be used with the system.
• These systems usually are too expensive for the benefits they provide.
• There is lack of software tools to analyze the data collected.
• The currently available systems don’t provide methods for accessing the data through the Internet or exporting data in order to be used in currently popular accounting systems used by these companies.
• If there is more than one dispensing unit, they may not communicate with each other in any way.
• The software and hardware of currently available products work with proprietary hardware and software, creating the disadvantage of having to replace equipment that may still be used.
Deliverables:
• A system capable of controlling and dispensing fuel products in industrial environments.
• A system capable of handling several dispensing units independently of their location.
• Modules that can be integrated with currently available dispensers.
• Powerful reporting tools.
• User account control with privileges.
• Internet connectivity for accessing data and/or reports.
• Data export utilities making it easy to integrate with other software or hardware products.
• User accounts, privileges, vehicle information and other information may be controlled and edited off-site.
Competitive advantages:
• Remote data management tools.
• Lower TCO, using open source software, widely available hardware and giving several options to the users.
• Possibility of integrating with other hardware or software, to customize the system for the needs of the company.
Monday, January 25, 2010
HW 3 and Proposal Meeting
Attendees:
Arnaldo Rivera
Adam J. Hidalgo
Agenda:
HW 3 Duties
Proposal Duties
Discuss project
Decisions:
· HW 3
o Repository has been requested
o Photo shall be taken early on Wednesday
o Adam will make the logo
o Arnaldo will do the project description
o Arnaldo and Adam will each find standards for the project
§ ieee standards
§ C# Standards
§ Web 2.0 Standards
§ RS232.
§ IEEE 802.15.4
§ Serial Standards
§ Wireless through gas stations?
§ Check pei.org for more standards and information
o Adam will bring camera for picture on Wednesday
o Arnaldo will host the website on his server
· Proposal
o Adam will make risk assessments
o Arnaldo will make Gantt Chart
o Arnaldo will find previous projects and competition
o Make project use wireless Ethernet
o Priorities in building project will be screen and keypad
§ Wireless
§ Web page
§ Device Shell
§ PC program
§ PC components
o Arnaldo will work with budget
o Will use open source SW to reduce costs