provisioning.md

+Provisioning process - all the software/hardware related steps that we should take to get device ready for shipment to the customer, e.g. downloading the software/content, software installation. Venue specific configuration will be a customer's "out of the box" experience.
+ 
+Qbert Provisioning will be taking place in Buzztime offices/warehouses, i.e. in a secure environment with the ethernet connection. Therefore we can use the same approach as we use for Scorpio provisioning. Right now the build generates the manifest so should be implemented along with the Handshake. For now while build process is not ready we can have a static manifest.
+ 
+New initial provisioning call have to be implemented:
+*  one-time call which is separate from the handshake and not available outside of Buzztime networks.
+  *   obtain what device needs for provisioning & setting itself up, e.g.:
+*   initial credentials needed for handshake/manifest
+*   software / content to be downloaded & installed
+ 
+Pre-provisioning steps
+1.      [one time] update equipment tracking process
+2.      [one time] add new device type to Netsuite & DB
+3.      [one time] configure site in NetSuite
+4.      [per device] assign the tablet's Serial Number to the site in Netsuite's Sales Order
+5.      [per device] pass the devices/serial numbers for provisioning 
+ 
+Qbert provisioning steps:
+1.      make initial provisioning call
+2.      get initial credentials needed for handshake/manifest
+3.      get the list of software / content to be downloaded & installed (manifest ?)
+4.      download software / content
+5.      install software
+6.      confirm that all is installed and working properly
+7.      shut down  - go to "out of box" mode, i.e. next time device boots it expected to be at the customer's site
+8.      perform handshake , i.e. apply all the features, payment & network settings etc.
+ 
+Action Items:
+-----
+| Who | Item |
+| --- | --- |
+[Alex] | Create a ticket: Initial provisioning call implementation
+[Alex] | Create a ticket: Define the content of the static manifest to be used before the build process is ready.
+[Alex] | Create a ticket: Define the content of handshake based on the values that are being passed currently
+[Mark] | Define & update the  ticket (QBERT-29) with the data that we should  move into secure provisioning step and what to keep in the handshake.
+[Shan/LaShawn] | Decide on "out of the box" process step: does the device expected to be connected via Wifi or ethernet for the initial configuration step
+