1. Consider that this is an experiment only, and not a production project.
2. As the end-user in your team, select an application example which you know is manageable within a 4-6 weeks long test project.
3. Select a 6-8 week time window for your project where you know you can spend at least 2-4 hours per week on average on this experiment.
4. Prepare for the experiment by defining the main goals and describing the needed hardware, software and expertise
5. Once your project is launched, you must complete the required team documents (Project Definition, Key Contacts, Computing Resources, and Software Resources).
6. All preparatory work such as testing of the mesh, boundary and initial conditions, physical parameters, etc., should be done on an in-house system. Only when the test problem runs smoothly on an in-house system it can be moved to a remote system for larger runs with more resources.
7. While thinking about the set-up of the experiment, also start thinking about your next steps. What comes after the experiment if it concludes successfully? Would you be ready for including cloud computing as an option for additional computing needs? If pricing is reasonable, would you consider running production jobs in the cloud? Include these considerations already in your planning and preparation of the experiment test case.
8. As a service provider, provide your services in time, for example access to resources, software, and expertise shouldn't take longer than a few days.
9. Follow up with your team at least once a week. If you can’t be available, announce this to your team well ahead of time.
© Copyright 2014 UberCloud™. UberCloud is a trademark of TheUberCloud, LLC.