I agree with EricTRA on several levels. My mantra has long been
Lead with Benefits. Follow with Features.
"Benefits" add value to your organization.
"Features" enable business processes that yield those benefits.
"Software" implements those features.
"Hardware" provides and environment for software execution.
A corollary to this mantra says:
You cannot automate a mess.
Can you write a "user story" or "use case" for all of the various departments that you will serve? Remember that these stories might best have a business operational perspective rather than a technology bits and bytes perspective. There will be situations where technical absolutes will appear in your stories. For example, "... connect off-the-shelf laptop ..." mostly means interoperation with whatever MicroSoft is doing. Another example involves intergration with factory or distribution facility machines. They demand whatever they demand so you dance to their tune.
Good luck! Please consider a blog or other e-journal of your efforts. This will make a wonderful deployment story and you can look back and laugh years after the fact.