1)User Requirements Gather Downtime and related information on PDAs. Information to be gathered: -Machine ID -Batch number -Campaign number -Fault -Time of fault -Time to resolution -Enter yield data and reconciliation data associated with batch -Capturing data when there is no batch, i.e. Maintenance, Calibrations etc. Reporting mechanism to build reports internally on machine downtime Less than 30 sec data entry time per event. Graphical user interface designed to Microsoft Standards 2)System Description (i)Desktop Application A desktop application will be created: -To setup PDA required tables -As a repository for fault information, downtime information -As a reporting tool for gathered information System will provide shift report log. System will calculate down time and related figures (yet to be specified). (ii)PDA PDA used for data input. Self loading software in case of battery failure. System will gather all downtime events (some limitation would exist due to hardware). When a machine goes down the technician opens a new event by selecting ‘New’ on menu. (iii)Fixed barcode tags (on machines) User scans barcode attached to the machine. Software opens event and assigns start time. Software defaults “production?? when new record is created in field called “Activity??. If during production user must enter batch and campaign number, otherwise select Maintenance/Calibration. User enters batch and campaign number manually. Previous batch number and campaign number will be saved and user will have option to use these. (iv)Fault barcode list User enters downtime reason. List of default downtime reasons will be printed on A4. Each fault will have unique barcode. Fault scanned. User can enter comment. When machine is fixed, user scans machine. System calculates downtime, user confirms. At end of shift/week technician takes PDA and uploads details to desktop application.
1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
2) Deliverables must be in ready-to-run condition, as follows? (depending on the nature? of the deliverables):
a)? For web sites or? other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment.
b) For all others including desktop software or software the buyer intends to distribute: A software? installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request.
3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement).
IE 6 and Windows XP/Server 2003 for desktop application. Pocket PC for PDA application.