GEF Customer Breakout Sponsorship – Abstract Submission

Deadline for submissionOctober 1, 2015.

Please note that all breakout sessions must be vetted by the content review committee. Customer speaker details must be included upon submission of this form*. Priority will be given to stories from the areas of interest below and those incorporating newer technologies and/or innovative uses of those technologies.

If your submission is accepted, a release form will be provided to the customer, and you will be contacted with additional details on the breakout session along with sponsorship forms and terms.

Customer speaker must be confirmed and committed within 14 business days of acceptance of the abstract.

*All fields are required.

CONTACT DETAILS*
SPONSORING PARTNER COMPANY*
PARTNER CONTACT DETAILS* (for abstract and speaker coordination)
Partner Contact Name*
Partner Contact Title*
Partner Contact Email Address*
SPONSOR LEVEL REQUESTED*
☐ / ONYX
☐ / PLATINUM
☐ / GOLD
CUSTOMERCOMPANY NAME*
CUSTOMER SPEAKER DETAILS*
Customer Speaker Name*
Customer Speaker Title*
Customer Speaker Email Address*
Customer Speaker Biography * (100 words or less)
ABSTRACT DETAILS*
Presentation Title*
Business Opportunity*
Business and/or operational problem to be solved.
What has customer done to deal with challenge before this solution?
Roles/Titles of the People Impacted*
Solution Description* (100 words for website)
Overall solution description
Describe the solution in how an End User would describe the solution, and not as an IT description.
Key points in project execution: Methodology, Solution/Partner Differentiation, etc.
Story Details*
(Please include additional details on the business opportunity, solution description, and solution value to customer. These details will help us consider this submission for acceptance.)
Slight technical depth of solution highlighting Partner and Microsoft products used (other customers are interested in how they can leverage their investments in Microsoft products).
  • This should be the first introduction to technology deployed to solve problem/address opportunity – keep simple so that business leader, not just IT, can understand.
Why is solution valuable?
  • Overall benefits of solution (quantitative if possible, if not, qualitative)
  • How does it drive the business? – i.e.: impact on profitability, and not IT (production, safety incident reduction, asset lifecycle extension, etc.) - quantitative if possible, if not, qualitative
  • Expected future benefits
Best Practices/Lessons learned.
Elements of the Microsoft Platform Utilized* (Choose the most appropriate Solution Area, then all product/workloadsthat apply within the category.)
☐ / Connected Operations to Maximize Oil & Gas Production / ☐ / Internet of Things / ☐ / Azure Hybrid Integration
☐ / Azure Compute / ☐ / Azure Machine Learning
☐ / Azure Storage / ☐ / Windows Phones
☐ / Azure Networking / ☐ / Windows Tablets
☐ / Stakeholder Management to Efficiently Manage the Business / ☐ / Dynamics CRM / ☐ / Azure
☐ / Dynamics ERP / ☐ / SQL Server
☐ / Microsoft Project / ☐ / Microsoft Excel
☐ / SharePoint
☐ / Operations Excellence Solutions to Optimize Production, Movements, and Conversion / ☐ / Microsoft Power BI/Power Suite / ☐ / Azure Analytics
☐ / Office 365 / ☐ / Microsoft Excel
☐ / SQL Server
Results/ROI/Anticipated ROI of Project*(Overall benefits of solution - quantitative if possible, if not, qualitative; Expected future benefits)
Deployment Status*
☐ / Completed
☐ / Partially Complete (at least one phase completed with results)
☐ / Proof of Concept