Michigan State University College of Engineering; Dept. of Electrical and Computer Eng. ECE 480 Capstone Design Course Project Charter

Transcription

1 Michigan State University College of Engineering; Dept. of Electrical and Computer Eng. ECE 480 Capstone Design Course Project Charter Safety Equipment Bar Code Scanner Sponsoring Company/ Organization: ArcelorMittal USA Contact Information: Name: Jim Lang Office: (219) Cell: (219) No Preference regarding best time to call Background Information: Safety devices such as Fire Extinguishers and AED s require periodic inspections and documentation of these inspections. In most instances, these inspections are documented at the location of the device on a paper record or attached tag. If that record is lost, so is the history of the inspections. Also, in many cases, there is no method to confirm that all required devices have been inspected as prescribed. Additionally, inspections such as these are often targets of audits. Audit resources visit the locations of these devices to confirm inspections occur as scheduled; these resources could be more effectively deployed if records were available electronically. Lastly, electronic confirmation of these inspections will alert responsible personnel of inspection failures. Business Case: Audits have confirmed that some of the inspections do not occur as prescribed. This puts at risk the company s OHSAS certification and compromises the integrity of the item not inspected. Some item inspections are tracked via excel spreadsheets that require resources to maintain and are often inaccurate as various personnel perform the inspections and must share that information with the owner of the spreadsheet; that sharing of information does not occur in every instance. Safety equipment is inspected to insure it is reliable when employed. Inspection failures compromise that reliability. Project Intellectual Property Considerations: Will the student Design Team be required to sign a Non-Disclosure Agreement? o No Will the Design Team be able to post their work on the course web site? o Yes Will the student Design Team be working with technology contained in pending patents not yet granted? o No

2 Can the electronic design be shown, but the embedded software protected? o Yes Opportunity Statement: Paper records or tags of inspections at a safety device are often lost or incomplete. Sometimes the tags or papers are lost or the inspection does not occur. The only method to confirm the inspections were executed is via audits manual review of the record attached or adjacent to the device. This is an ongoing issue that can be resolved with the 13 week semester. The initial benefactor of this project will be the ArcelorMittal Safety Division at Indiana Harbor. o The Design Team will deliver the project to either Jim Lang or a representative of the Indiana Harbor Safety Division at the Fall Design Day (December, 2016). The benefits of this project will be that safety devices will be inspected as prescribed in local programs and policies and these inspections will be documents appropriately. The risk of an audit non-conformance due to inspection failures or faulty record keeping will be eliminated. The inspection based reliability of the safety devices will be maximized. Deliverables: Project report as delivered to the Professor of this class. Working prototype - Demonstration (Design Day) that the software and devices work as designed. Software or Application in electronic and written format. User Manual for the Administrator of this software. User Manual for the End User of this user friendly software. Structure for reporting report designs from the data. Goals: Software that is easily deployed to a PC or Phone App. Admin access that is user friendly (See Scope) End user interface that is user friendly. Data base that is conducive to report generation. Examples of reports from this data base such as a failed inspection report sent to the owner of the device. Database/Software will send to the device owner: o if an inspection fails o 7 days prior to the inspection due date (End of the month 7 days) o The day after the inspection was due and was not performed Scope: Devises that scan bar codes to indicate the location of the inspection and the device (Bar coding when deployed at the Plant will be considered standard bar coding and will include the unique device location such as the exact fire extinguisher location that is affixed to that location and a unique bar code

3 identifier affixed to the safety device such as a bar code sticker affixed to the fire extinguisher) can be one of two types: o Smart Phone (Including iphone, BlackBerry, Android) o Stand alone device (capable of taking pictures); commercially available or easily assembled. Data gathered at the inspection site will be stored within the device until it can be transferred via Wi-Fi (preferred) or a docking station. The data may include pictures secured at the inspection site. Not all inspection locations are within Wi-Fi range. The software will allow an Administrator to set up: o The Device Location o Type of device inspected o The owner or person responsible for the device (Name and Address) o Frequency of inspection This is typically monthly and it is by calendar month, not by every 30 days. It could be once a Quarter (Jan 1 March 30 is a quarter = 3 month segments Jan 1-Mar30, Apr 1-Jun 30, Jul 1-Sep 30, Oct 1-Dec 31) Annual is once per calendar year, not once every 365 days. o A series of inspection questions that are answered via Pass/Fail. If a question answer = Fail (Inspection questions included at the end of this document): The user records what caused the failure (text) The user: o can remedy that immediately and record that what was done (test) OR o confirms the device needs attention by the device owner resulting in an to the device owner that includes: Device type Device Location Person who performed the inspection Date and time of inspection (Recorded at the time the record was created) The text of the failure Picture (if applicable) secured by the user Software: Use any free PC based database software like MYSQL Community that is able to upload the fire extinguisher data to a server based system. IN and OUT of Scope for the Design Team: The primary scope of this project would be to read bar code information and perform the audit of the extinguisher. Once the data is transferred from the scanner to the PC based system, generate a report of the daily audits completed and notify the home departments with any deficiencies. What is not part of

4 scope, once the audit reports have been generated, upload the data to a server based system for long term storage and analysis, and generate historical reports. To keep costs down, use any Windows based laptop or desktop PC capable of running MYSQL Community able to accept USB or Wi-Fi communications with the barcode scanner device. An Android or Apple cellphone can be used to read the barcode labels and transfer the audit data to the laptop. Create any reports using Microsoft Office tools, Word or Excel, and send results via using Outlook. Microsoft Professional can be provided by ArcelorMittal. Constraints: List all constraints on the project team. o Examples include: Equipment the team must interface with, past Capstone Designs the team must build upon previous results, chip sets / software team must use in the design, etc. Project Team: (Completed once semester begins) Name Responsibility Faculty Advisor: (Assigned by ECE Dept. based on project requirements) See next page for attachment

5 Overview Instructions & Explanations 1 Extinguishers shall be visible from 75 feet away (Or sign indicating location is visible from 75 feet 1). 1 Where applicable, mount sign feet above the extinguisher 2 Extinguisher is mounted on provided bracket. 3 Access is unobstructed. 4 Tamper seal and pin in place / intact or Tamper Seal without pin. 2 2 Tamper Seal and pin (Left) Tamper Seal without pin (Right) 5 No obvious signs of damage or wear to the body of the extinguisher or the hose / nozzle. 6 If applicable, stored pressure gauge indicates adequate pressure. 3 7 Wheeled Fire Extinguishers: 7.1 Visually inspect that the carriage, wheels, hose and nozzle are in good condition. 3 Pressure Gauge (example on left indicates the extinguisher needs to be charged, drawing on right shows properly charged extinguisher) 8 Extinguishers in service beyond the expiration date indicated on the body of the extinguisher shall be returned to the Fire Department.