- Respective program managers
- Eliminates flaws with issue and receipt of inventory.
- Increases focus on other aspects of respective programs.
- Increases the chances of getting a award which could help with promotion.
- Easier to hold people accountable for inventory checked in or out.
- Quickens end of shift ATAF (All Tools Accountable For).
- Issuing and Receiving Personnel
- Makes the checkin and checkout processes easier.
- Prevents mistakes from happening in logbook.
- Less to do at the end of shift.
- Inspectors
- Easier to evaluate each program.
- Decreases the amount they have to dig for flaws.
Much like the HPU Working Student Scheduler I think using the existing databases already being used by various personnel within this particular shop is the way to go. My only concern is that all the data is stored on a few MS Access databases and I am uncertain if Ruby could be used to work with them. Also I know MS Access isn't as scalable as other database management systems. If Tom and Revelyn are open to work together on a project I am willing to as well.
I believe Ruby can talk to MSAccess if it has too, but I wouldn't worry too much about that. The key value offering of ruby on rails is that once you've mastered the basics you can create a prototype site very fast. What the final solution might be is another matter. What you want is to work quickly through a series of prototypes from paper sketches, html mockups and fast interactive prototypes in ruby on rails in order to really understand how users will interact with your system and make sure it does what they need it to do. Legacy data issues are another concern, but I wouldn't worry about them too much while prototyping - and pretty much any language can talk to any database, or some data conversion mapping can be created when necessary.
ReplyDeleteWell that's a relief. At times it's hard for me to visualize how all of these things work together.
ReplyDelete