Revise journey intro

[VeronicaWasson]

This revises the journal introduction according to the ideas in #185, #184. Mainly it's a shift in tone, writing from p&p's perspective rather than "Fabrikam's". Appreciate feedback on this, because the idea is to follow this basic approach for the other journal entries.

connects to #185

[bennage]

Do we want to add more details about how we chose the the them of smart building? We are choosing the scenario based on the observations of Azure CAT, Microsoft Consulting Services, the product groups, and our advisors. We are focusing on some of the basics (ingestion) because they are fundamental to other scenarios. In addition, there are some surprising pitfalls with the basics.

[francischeung]

• Replace “reference architecture” with “reference implementation”

Don’t know how much of this you want in the intro doc:

1. The problem space: Assuming a self-serve provisioning model where a technician can alter the configuration of a device, setting SAS token and EventHub instance URL… it may be important to protect the device from being reconfigured by hackers, providing their own SAS token and evenhub instance URL.
2. Logical arch: We don’t mention adhoc analysis. I wonder if we should.

[VeronicaWasson]

@francischeung: In the logical architecture, ad hoc analysis would point to Warm Storage? (Sibling to Batch Analytics which points to Cold Storage) I could add that.

[francischeung]

When you say Batch Analytics, you mean HDInsights and Hive queries, then YES. Ad hoc analysis (Elasticsearch + Kibana) would point to warm storage (Elasticsearch).