Open AndyClifton opened 5 years ago
FAQs content to be captured here. FAQ delivery to clients will be done by creating FAQs in the CMS - see octue/issues#17
Some thoughts on the Octue FAQ, partly based on:
The FAQ should help push potential customers towards a purchase or trial. It should reduce the amount of work that we need to do, to convert an enquiry into a sale.
At this time (June 2019) the goal of the FAQ should be to answer the basic newb questions. As our market and users mature, we can review the FAQ concept.
The FAQ should be a mixture of “management”-level questions (what am I being asked to pay for?) and “worker”-level questions (how do I use this). They should be real, user-oriented questions, not padding.
The answer should provide actionable information, either e.g. a link to a document or more information, or a “mailto…”
The May 2018 proposal from Tom to NPC contains a lot of useful information that could be used to support the FAQ.
Detailed questions about coding will be pushed to a knowledge base system.
The FAQ should be accessible via www.octue.com.
Answers should also include a thumbs up / down / feedback option (not required on first release!)
First suggested questions, based on questions raised by potential users:
A digital twin is a software version of a real-world system or device. So, like in the real world, your digital twin needs inputs about the environment that it works in, and needs to have a model of how the system responds. If you think of a wind plant, the inputs might be wind speed and direction, the system is the power curve, and so the output might be power. In octue you set up your data streams, link to code that describes your system, and serve the output data to whomever needs it. See this demo for an example.
See also the "What is Octue" slide deck
FAQs help users understand products and services.
We should collect these in one document that can be used on its own, used on the website, and to support marketing activities.
actions