Pushing Storyline Limitations

I thought with that caption, maybe I could catch someones eye!
Heres what I am endeavoring to do:
Scenario..
Working in an industrial plant area, and need to have a system in place that the maintenance folks can follow.

Will write and publish the content so that the worker(s) can have a 'pad' with them, with the downloaded content on it. The content will identify what and where they are to work that day (as there are specific maintenance areas); and whether it is a daily task, weekly task, or whatever the schedule requires. Within the content, it will identify what needs to be maintained, and how. Then, once the task is completed, a way to 'sign off' on as having done the required task, and then move on to the next task.
Would probably 'dock' the pads daily when work is completed, for recharging, and for downloading the completed and uncompleted task lists. This way we can keep critical time line documentation on what work was done to what item on what day. Mangagers could then review the work,  identify trends, and schedule future maintenece and repairs..

Has anyone gone this direction with storyline?

Thoughts? Concerns? Warnings?