DREAM PoC Accelerators (DPoC) are packaged Industry Scenario DREAM Demos with ARM templates (with a demo web app, Power BI reports, Synapse resources, AML Notebooks etc.) that can be deployed in a customer’s subscription using the CAPE tool in a few hours. Partners can also deploy DREAM Demos in their own subscriptions using DPoC.
Partners can deploy DREAM Demos in their own Azure subscriptions and show live demos to customers. In partnership with Microsoft sellers, partners can deploy the Industry scenario DREAM demos into customer subscriptions. Customers can play, get hands-on experience navigating through the demo environment in their own subscription and show to their own stakeholders Before You Begin
- Please read the license agreement and disclaimer before proceeding, as your access to and use of the code made available hereunder is subject to the terms and conditions made available therein.
- Without limiting the terms of the license , any Partner distribution of the Software (whether directly or indirectly) may only be made through Microsoft’s Customer Acceleration Portal for Engagements (“CAPE”). CAPE is accessible by Microsoft employees. For more information about the CAPE process, please connect with your local Data & AI specialist or CSA/GBB.
- Please note that Azure hosting costs are involved when DREAM PoC Accelerators are implemented in customer or partner Azure subscriptions. Microsoft will not cover DPoC hosting costs for partners or customers.
- Since this is a DPoC, there are certain resources open to the public. Please ensure proper security practices are followed before you add any sensitive data into the environment. To strengthen the security posture of the environment, leverage Azure Security Centre.
- For any questions or comments please email [email protected].
Note: Set up your demo environment at least two hours before your scheduled demo to make sure everything is working.
© 2021 Microsoft Corporation. All rights reserved.
By using this demo/lab, you agree to the following terms:
The technology/functionality described in this demo/lab is provided by Microsoft Corporation for purposes of obtaining your feedback and to provide you with a learning experience. You may only use the demo/lab to evaluate such technology features and functionality and provide feedback to Microsoft. You may not use it for any other purpose. You may not modify, copy, distribute, transmit, display, perform, reproduce, publish, license, create derivative works from, transfer, or sell this demo/lab or any portion thereof.
COPYING OR REPRODUCTION OF THE DEMO/LAB (OR ANY PORTION OF IT) TO ANY OTHER SERVER OR LOCATION FOR FURTHER REPRODUCTION OR REDISTRIBUTION IS EXPRESSLY PROHIBITED.
THIS DEMO/LAB PROVIDES CERTAIN SOFTWARE TECHNOLOGY/PRODUCT FEATURES AND FUNCTIONALITY, INCLUDING POTENTIAL NEW FEATURES AND CONCEPTS, IN A SIMULATED ENVIRONMENT WITHOUT COMPLEX SET-UP OR INSTALLATION FOR THE PURPOSE DESCRIBED ABOVE. THE TECHNOLOGY/CONCEPTS REPRESENTED IN THIS DEMO/LAB MAY NOT REPRESENT FULL FEATURE FUNCTIONALITY AND MAY NOT WORK THE WAY A FINAL VERSION MAY WORK. WE ALSO MAY NOT RELEASE A FINAL VERSION OF SUCH FEATURES OR CONCEPTS. YOUR EXPERIENCE WITH USING SUCH FEATURES AND FUNCITONALITY IN A PHYSICAL ENVIRONMENT MAY ALSO BE DIFFERENT.
- Azure Synapse Analytics Wide World Importers setup guide
- Requirements
- Before Starting
- Task 1: Create a resource group in Azure
- Task 2: Create Power BI workspace
- Task 3: Deploy the ARM Template
- Task 4: Run the Cloud Shell
- Task 5: Create Power BI reports and Dashboard
- Task 6: Working with Power BI to create real-time reports
- Task 7: Modify the CSV to change campaign names, product categories, and hashtags
- Task 8: Publishing the Custom Vision model
- Task 9: Uploading new incident reports
- Task 10: Pause-Resume resources
- Task 11: Clean up resources
- An Azure Account with the ability to create an Azure Synapse Workspace.
- A Power BI Pro or Premium account to host Power BI reports.
- Make sure the following resource providers are registered with your Azure Subscription.
- Microsoft.Sql
- Microsoft.Synapse
- Microsoft.StreamAnalytics
- Microsoft.EventHub
- Please note that you can run only one deployment at a given point of time and need to wait for the completion. You should not run multiple deployments in parallel as that will cause deployment failures.
- Please ensure selection of correct region where desired Azure Services are available. In case certain services are not available, deployment may fail. Azure Services Global Availability for understanding target services availablity.
- Do not use any special characters or uppercase letters in the environment code.
- Please ensure that you select the correct resource group name. We have given a sample name which may need to be changed should any resource group with the same name already exist in your subscription.
- Once the resources have been setup, please ensure that your AD user and synapse workspace have “Storage Blob Data Owner” role assigned on storage account name starting with “dreamdemostrggen2”. You need to contact AD admin to get this done.
Note: Please log in to Azure and Power BI using the same credentials.
-
Log into the Azure Portal using your Azure credentials.
-
On the Azure Portal home screen, select the '+ Create a resource' tile.
-
In the Search the Marketplace text box, type 'Resource Group' and press the Enter key.
-
Select the 'create' button on the 'Resource Group' overview page.
-
On the 'Create a resource group' screen, select your desired Subscription. For Resource group, type 'Synapse-WWI-Lab'.
-
Select your desired Region.
-
Click the 'Review + Create' button.
-
Click the 'Create' button once all entries have been validated.
-
Open Power BI Services in a new tab using the following link: https://app.powerbi.com/
-
Sign in, to your Power BI account using Power BI Pro account.
Note: Please use the same credentials for Power BI which you will be using for Azure Account.
-
In Power BI service click on 'Workspaces'.
-
Then click on the 'Create a workspace' tab.
- Enter the 'Workspace name' and 'Description' and click 'Save'.
Note: Please create a Workspace by the name 'Engagement Accelerators – Manufacturing'.
- Copy the Workspace GUID or ID. You can get this by browsing to https://app.powerbi.com/, selecting the workspace, and then copying the GUID from the address URL and paste it in a notepad for future reference.
Note: This workspace ID will be used during ARM template deployment.
-
Right-click on the 'Deploy to Azure' button given below and open the link in a new tab to deploy the Azure resources that you created in Task 1 with an Azure ARM Template.
-
On the Custom deployment form, select your desired Subscription.
-
Type the resource group name 'Synapse-WWI-Lab' created in Task 1.
-
Select Region where you want to deploy.
Note: Ensure the resource availability for synapse, cognitive services and aml in the region you select.
- Provide environment code which is a unique suffix to your environment without any special characters. e.g. 'demo'.
Note: Please enter the values in compliance with tooltip instructions
-
Provide a strong SQL Administrator Login Password and set this aside for later use.
-
Enter the Power BI Workspace ID, created in Task 2, in the 'Pbi_workspace_id' field.
-
Select Location from the dropdown. Please ensure that this is the same location you selected in Step #4 above.
-
Click 'Review + Create' button.
-
Click the 'Create' button once the template has been validated.
NOTE: The provisioning of your deployment resources will take approximately 20 minutes.
-
Stay on the same page and wait for the deployment to complete.
-
Click 'Go to resource group' button once your deployment is complete.
Open the Azure Portal.
-
In the 'Resource group' section, open the 'Azure Cloud Shell' by selecting its icon from the top toolbar.
-
Click on 'Show advanced settings'.
Note: If you already have a storage mounted for Cloud Shell, you will not get this prompt. In that case, skip step 2 and 3.
Note: If you are creating a new storage account, give it a unique name with no special characters or uppercase letters and it should not be more 10 characters. Note: If you face permission issues while executing the scripts in cloudshell, you also have the option to execute them through your local PowerShell. Before executing the following steps on your local PowerShell, execute the script located [here] ( https://github.com/microsoft/Azure-Analytics-and-AI-Engagement/blob/main/Manufacturing/automation/installer.ps1 ) for the prerequisite installations on your local PowerShell in administrator mode. You may have to execute the the following command to remove execution restrictions on your local PowerShell.
Set-Executionpolicy unrestricted
-
In the Azure Cloud Shell window, enter the following command to clone the repository files.
git clone https://github.com/microsoft/Azure-Analytics-and-AI-Engagement.git MfgAI
Note: If you get File “MfgAI” already exist error, please execute following command: rm MfgAI -r -f to delete existing clone.
Note: When executing the script below, it is important to let the scripts run to completion. Some tasks may take longer than others to run. When a script completes execution, you will be returned to PowerShell prompt. The total runtime of all steps in this task will take approximately 1 hour.
-
Execute the
manufacturingSetup-shell.ps1
script by executing the following commands:cd 'MfgAI/Manufacturing/automation'
-
Then run the PowerShell:
./manufacturingSetup-shell.ps1
Note You will be prompted to confirm that you have read the license agreement and disclaimers. Click on the links to read it if not already done. Type 'Y' if you agree with the terms and conditions in it. Else type 'N' to stop the execution. Also ensure you delete the resources in your resource group if you do not wish to continue further.
-
From the Azure Cloud Shell window, copy the Authentication Code.
-
Click on the link https://microsoft.com/devicelogin) and a new browser window will launch.
-
Paste the authentication code.
-
Select the same user that you used for signing in to the Azure Portal in Task 1.
-
Close the browser tab once you see the below message window and go back to your 'Azure Cloud Shell' execution window.
Note: If you face permission issues while executing the scripts in cloudshell, you also have the option to execute them through your local PowerShell. Before executing the following steps on your local PowerShell, execute the script located [here] ( https://github.com/microsoft/Azure-Analytics-and-AI-Engagement/blob/main/Manufacturing/automation/installer.ps1 ) for the prerequisite installations on your local PowerShell in administrator mode. You may have to execute the the following command to remove execution restrictions on your local PowerShell.
Set-Executionpolicy unrestricted
-
Navigate back to the resource group tab.
-
You will get another code to authenticate Azure PowerShell script for creating reports in Power BI. Copy the code.
-
Click the link (https://microsoft.com/devicelogin).
-
Follow the same steps as in Task 4 steps 7 to 11.
Note: While you are waiting for processes to get completed in the Azure Cloud Shell window, you'll be asked to enter the code three times. This is necessary for performing installation of various Azure Services and preloading content in the Azure Synapse Analytics SQL Pool tables.
-
You will now be prompted to enter the resource group name in the Azure Cloud Shell window. Enter the name of the resource group that you created in Task 1 - 'Synapse-WWI-Lab'.
-
You will get another code to authenticate Power BI gateway. Copy the code.
-
Click the link (https://microsoft.com/devicelogin).
- A new browser window will launch. Follow the same steps as in Task 4 steps 9, 10 and 11.
Open the Azure Portal.
-
Go to the resource group you have created in Task 1.
-
Search the storage account name starts with 'dreamdemo'.
-
Go to the storage account by clicking on its link.
-
Click on 'Access Keys' from the left navigation pane for storage account.
-
Copy the 'key1' to the clipboard and paste the key in a notepad for future reference.
Open the Azure Portal.
-
Go to the resource group you have created in Task 1.
-
Search the Cosmos DB account name starts with 'cosmosdb'.
-
Go to the Cosmos DB account by clicking on its link.
-
Click on 'Keys' from the left navigation pane for Cosmos DB account.
-
Copy the 'Primary key' to the clipboard and paste the key in a notepad for future reference.
-
Open Power BI Services in a new tab using following link https://app.powerbi.com/
-
Sign in to Power BI account using 'Power BI Pro account'.
Note: Please use the same credentials for Power BI that you used for 'Deploy the ARM Template' deployment.
- Select the Workspace 'Engagement Accelerators – Manufacturing'.
Assuming Task 4 got completed successfully and the template has been deployed, you will be able to see a set of reports in the "Content" tab of Power BI. The image below shows the 'Content' tab in Power BI. We can then create a Power BI dashboard by pinning visuals from these reports.
Note: A Dashboard is a collection of tiles/visualization which are pinned from different reports to a single page.
To give permissions for the Power BI reports to access the datasources:
-
Click the 'Datasets + dataflows' tab.
-
Click on the ellipse icon infront of any report in the report list.
- Click on Settings.
-
Click 'Campaign – Option C' Report.
-
Expand Data source credentials.
-
Click Edit credentials and a 'Configure Campaign - Option C' dialogue box will pop up.
Note: If the data-source of the report dataset does not match the SQL pool name, then you may have to update the report dataset using Power BI desktop. For further details refer FAQ.
-
Enter Username as 'ManufacturingUser'.
-
Enter the same SQL Administrator login password that was created for Task 3 Step #6.
-
Click Sign in.
- Click ‘Azure Cognitive Search’ dataset.
- Expand 'Data source credentials'. Click 'Edit credentials' and a dialogue box will pop up.
- Enter the same storage key that was noted down in Step 28 of Task 4.
- Click 'Sign in'.
- Click ‘anomaly detection with images’ dataset.
- Expand 'Data source credentials' and click 'Edit credentials' and a dialogue box will pop up.
- Select 'Key' from 'Authentication method' dropdown.
- Enter the same storage key that was noted down in Step 28 of Task 4.
- Click 'Sign in'.
- Click '6_Production Quality- HTAP Synapse Link' dataset.
- Expand 'Data source credentials'.
- Click 'Edit credentials' and a dialogue box will pop up.
- Enter the same cosmos key that was noted down in Step 29 of Task 4.
- Click 'Sign in'.
Follow these steps to create the Power BI dashboard:
- Select the workspace 'Engagement Accelerators - Manufacturing'.
-
Click on '+New' button on the top navigation bar.
-
Click the 'Dashboard' option from the drop-down menu.
-
Name the dashboard 'Engagement Accelerators Dashboard' and click 'create'.
-
This new dashboard will appear in the 'Dashboard' section of the Power BI workspace.
Follow the below steps to change the dashboard theme:
-
Open the URL in new browser tab to get JSON code for a custom theme: https://raw.githubusercontent.com/microsoft/Azure-Analytics-and-AI-Engagement/real-time/Manufacturing/automation/artifacts/theme/CustomTheme.json
-
Right click anywhere in browser and click 'Save as...'.
-
Save the file to your desired location on your computer, leaving the name unchanged.
-
Go back to the Power BI Dashboard you just created.
-
Click on edit option and Click on Dashboard theme option.
-
Click Upload the JSON theme.
-
Navigate to the location where you have saved the JSON theme file in Step #21 above and Select open.
-
Click Save.
Do the following to pin visuals to the dashboard you just created:
- Select the workspace 'Engagement Accelerators - Manufacturing'.
- Click on the 'Reports' section/tab.
-
In the 'Reports' section, there will be a list of all the published reports.
-
Click on 'Campaign - Option C' report.
- On the 'Campaign – Option C' report page, click the 'Revenue Vs Target' visual and click the pin icon.
-
Select 'Existing dashboard' radio button.
-
From 'Select existing dashboard' dropdown, select 'Engagement Accelerators Dashboard'.
-
Click 'Pin'.
- Similarly, pin 'Profit card' and 'Investment, Incremental Revenue and ROI Campaign Scatter Chart' from the report.
Some of the visuals are pinned from hidden pages. To pin such visuals, follow the below steps.
- Click on Edit.
- Click 'Sales and Campaign' report page.
-
Pin 'Total Campaign', 'Cost of Goods Sold' card visuals to 'Engagement Accelerators Dashboard'.
-
Pin 'Revenue by country' map visual.
Note: Please refer to steps 45-48 of Task 5 for the complete procedure of pinning a desired visual to a dashboard.
- Select the workspace 'Engagement Accelerators - Manufacturing'.
- Open 'Dashboard Images' report.
- Pin all images from above report to the 'Engagement Accelerators Dashboard'.
Note: Please refer to steps 45-48 of Task 5 for the complete procedure of pinning a desired visual to a dashboard.
- Go back to the 'Engagement Accelerators Dashboard'.
To hide title and subtitle for all the images that you have pined above. Please do the following:
-
Click on ellipsis 'More Options' of the image you selected.
-
Click 'Edit details'.
-
Uncheck 'Display title and subtitle'.
-
Click 'Apply'.
-
Repeat Step 58-61 of Task 5 to disable title and subtitle for each image tiles.
-
After disabling 'Display title and subtitle' for all images, resize and re-arrange top images tiles or chicklets as shown in the screenshot. Resize the 'Wide World Importers' logo to 1x1 size. Resize other vertical tiles to 2x1 size.
- Resize and rearrange left images tiles or chicklets as shown in the screenshot. Resize 'KPI' tile to 1x2 size. Resize 'Deep Dive' tile to 1x4 size.
- Refer the screenshot of the sample dashboard below and pin the visuals to replicate the following look and feel.
- Pin the 'Predictive maintenance and Safety Analytics' pillar tiles to the dashboard using the 'anomaly detection with images' report. To do this, follow the same procedure as above.
'Racing Cars' and 'Milling canning' datasets will be automatically created when Azure Stream Analytics jobs start sending data into Power BI services. Once the Dataset has been created in the Power BI workspace, (by Azure Cloud Shell commands executed in Task 3 above) follow the next steps to create the real-time pillars.
Note: For your convenience we have included a few real-time visuals and a few static visuals so that you can complete the dashboard.
Creating the Realtime Operational Analytics pillar:
In this section of the document we will create the 'Realtime Operational Analytics' pillar (screenshot below) of the dashboard. Please note we’ll pin visuals from the static Power BI report. And we will create Power BI visuals using a real-time dataset.
Pin visuals from the static report:
- Click Workspace 'Engagement Accelerators - Manufacturing’.
- Click on Content tab and sort type as Report.
- Search 'Real Time Analytics Static Report’.
- Click 'Real Time Analytics Static Report’.
- Click on 'Real time Operational Analytics’ page.
Hover on the highlighted visuals to pin them to 'Engagement Accelerators Dashboard’.
- Pin 'Machine Status’ card visual.
- Pin 'MTTR/MTBF (Hours)’ card visual.
- Pin 'Alarms/Incidents’ card visual.
- Pin 'OEE and Elements’ visual.
- Pin 'Machine Vibration (mm) Milling-Canning’ visual.
Note: Please refer to steps 45-48 of Task 5 for the complete procedure of pinning a desired visual to a dashboard.
Creating a visual from a real time dataset
- Select the workspace 'Engagement Accelerators - Manufacturing'.
- Click on '+New' button present on the top navigation bar.
- Select 'Report' option from the drop-down menu.
- Click on Pick a published dataset option.
- Enter 'Racing' in the search bar and Select the 'Racing Cars' dataset.
- Click on 'Create a blank report'.
- Select the 'ActiveSensors' field from 'race-cars' Dataset.
- Select 'Card’ from Visualization pane.
- Select drop-down next to 'ActiveSensors'.
- Select 'Average' from the drop-down to get the average of 'ActiveSensors'.
- Navigate to the Visual tab of the Format Visual section and Change the 'Display units' to 'None' by expanding Callout value section.
- With Card visual selected, select the format visual tab and navigate to General section.
- Turn on the 'Title' and expand Title.
- Enter 'Active Sensors' as the title for the card.
- Change the 'Title' color to 'White’.
-
Turn on Background and change the background color of the card.
-
Similarly, the color of the KPI value and title value can be changed by going to the format visual tab. After navigating to the format visual tab, Click on General section and Expand effects and Expand Background to set the color. You can use the Hex code #00222F to achieve the background color of the visual.
Note: All other visuals of the report can be created by following a similar process.
- Click on the 'Save this report' icon.
- Enter the name of the report 'Racing Cars- A' and click on 'Save'.
Creating the Realtime Field and Sentiment Analytics pillar
In this section of the document we will create the 'Realtime Field and Sentiment Analytics’ pillar (screenshot on the right) of the dashboard. Please note we’ll pin visuals from the static Power BI report. And we will create Power BI visuals using a real-time dataset.
Pin visuals from the static report:
- Click Workspace 'Engagement Accelerators - Manufacturing’.
- Click on Contents tab and sort by Report type.
- Search 'Real Time Analytics Static Report’.
- Click 'Real Time Analytics Static Report’.
- Click on the 'Real time Field and Sentiment Analytics report’ page in the previously opened 'Real Time Analytics Static Report’.
Hover on the highlighted visuals to pin them to 'Engagement Accelerators Dashboard’.
- Pin 'Fields Calls-Avg Response Time (in minutes)’ visual.
- Pin 'Alarms and Safety Incidents’ visual.
- Pin 'Real time Anomaly’ visual.
Note: Please refer to steps 45-48 of Task 5 for the complete procedure of pinning a desired visual to a dashboard.
Creating a visual from a real time dataset
- Select the workspace 'Engagement Accelerators - Manufacturing'.
- Click on '+New' button present on the top navigation bar.
- Select 'Report' option from the drop-down menu.
- Enter 'Racing' in the search bar.
- Select the 'Racing Cars' dataset.
- Click 'Create'.
- Select 'Tachometer’ visual from visualizations pane.
- Drag and Drop 'AverageRPM’ under value from race-cars dataset.
- Select 'Average' from the context menu to get the average of 'AverageRPM’.
Note: If you don’t have custom visual tachometer downloaded or don’t know how to use it please refer to the Microsoft tutorial: https://powerbi.microsoft.com/en-us/blog/visual-awesomeness-unlocked-tachometer-gauge-custom-visual/
- Drag and Drop 'AverageRPMStart’ under 'Start Value’ from race-cars dataset.
- Select 'Average' from the context menu to get the sum of 'AverageRPMStart’.
- Drag and Drop 'AverageRPMEnd’ under 'End Value’ from race-cars dataset and follow step #46 to get the Average of 'AverageRPMEnd’.
- Drag and Drop 'AverageRPMR2’ under 'Range2 Start Value’ from race-cars dataset and follow step #46 to get Average of 'AverageRPMR2’.
- Drag and Drop 'AverageRPMR3’ under 'Range3 Start Value’ from race-cars dataset and follow step #46 to get the Average of 'AverageRPMR3’.
- With the tachometer visual selected, click on the format visual tab and go to General section.
- Turn on 'Title'.
- Change 'Title text’ to 'Average Engine Speed’.
- Expand 'Range 1' in the visual section of the Format visual tab.
- Change color for range one to hex code #E3B80F.
- Similarly, the color of the 'Range 2' and 'Range 3' can be changed from the 'Range 2' and 'Range 3' respectively.
Note: For 'Range 2' color you can use hex code #1AAB40 and for 'Range 3' color you can use hex code #EB895F.
- Click 'File’ and select 'Save' from the drop down.
- Type 'Tachometer’ in the text box.
- Click 'Save'.
Note: Once this visual is ready you can pin it to the dashboard using the steps 45-48 of Task 5.
Follow the below step to create Wheel Acceleration tile
- Select the workspace 'Engagement Accelerators - Manufacturing'.
- Click on '+New' button present on the top navigation bar.
- Select 'Report' option from the drop-down menu.
- Enter 'Racing' in the search bar.
- Select the 'Racing Cars' dataset.
- Click 'Create'.
- Click white space on the report.
- Select 'Line Chart' from visualization tray.
- Drag and Drop 'EventProcessedUtcTime' from the race-cars dataset.
- Click on 'Rename' and change 'EventProcessedUtcTime' to 'Recorded On'.
-
Drag and Drop below columns from 'race-cars' dataset to values:
- wheelAccelFL
- wheelAccelRL
- wheelAccelFR
- wheelAccelRR
-
Using Step 70, rename above selected columns- 'wheelAccelFL’, 'wheelAccelRL’, 'wheelAccelFR’ and 'wheelAccelRR’ to 'Front Left’, 'Rear Left’, 'Front Right’ and 'Rear Right’ respectively.
- Expand the 'Filters' pane by clicking on the arrow icon.
- Navigate to the 'Filters on this page' section.
- Select 'Relative Time' from the 'Filter Type' dropdown menu.
- In the 'Show items when the value' section, select 'is in the Last' in the top dropdown menu, enter '5' in the text input box and select 'minutes' from the bottom dropdown menu.
- Click on 'Apply Filter'.
- With 'Line chart' visual selected, select format tab.
- Turn on 'Title'.
- Change 'Title text' to 'Wheel Acceleration’.
- Pin the visual to the dashboard.
Note: Please refer to steps 45-48 of Task 5 for the complete procedure of pinning a desired visual to a dashboard.
- After pinning the visual to the dashboard, click on 'Save’ icon located on the navigation bar at the top, to save the changes made to the report.
- Type 'Wheel Acceleration' in the text box.
- Click 'Save'.
- Upon successful save, click on the workspace name 'Engagement - Accelerators Manufacturing’.
- In the window that opens, click on 'Dashboards’ tab.
- From the list of dashboards that appears, click on the dashboard 'Engagement Accelerators Dashboard’ located under Dashboards tab.
- Resize and rearrange the visuals on the dashboard as per the screenshot below.
- Open Azure Synapse in a new tab using the following link: https://web.azuresynapse.net/
- Log in with your Azure credentials.
- Select the 'Subscription’ and Synapse 'Workspace name’ that got created in Task 3. The Synapse 'Workspace name’ will start with 'manufacturingdemo’.
- Click 'Continue'.
Note: Do not use any confidential customer data. Only use the data which is public available or with prior permission from the customer.
-
Click the 'Data' hub from the left navigation in the 'Synapse Analytics' workspace.
-
Click 'Linked' tab.
-
Expand 'Storage Account/Azure Data Lake Storage Gen2'.
-
Expand the node that starts with 'manufacturingdemo'.
-
Click 'customcsv' container.
-
Double Click 'Manufacturing B2C Scenario Dataset'.
-
Select 'CampaignData.csv'.
-
Click 'Download' button on the top toolbar in Azure Synapse Analytics Studio. The file will download locally.
-
Open the downloaded file in Excel. In case file does not get opened in Microsoft Excel, kindly navigate to the folder where file got downloaded and right click on the file name. Click 'Open With...' and then click 'Excel'.
-
Select 'CampaignName' column (Column B of Excel) and press 'CTRL + H' to replace exisitng campaign name with new campaign name.
-
Replace 'Spring into Summer' (old campaign name) with 'Summer Fashion' (new campaign name).
-
Click 'Replace All'.
-
Pop up will be displayed with 'All done...' replacement message.
-
Click OK.
Note: In this demo, we change one campaign. In real-life you would have multiple campaigns, and you would be inserting campaigns aligned to your customer.
-
Save the file by pressing the highlighted button. Close the file.
-
Go back to your browser window where 'Azure Synapse Analytics' is already open. In case it's not open, kindly follow steps 1 to 8 mentioned above. Once you have followed the steps, click 'Upload' button in 'Azure Synapse Analytics Studio' to upload the file from your local system.
-
Select 'CampaignData.csv' file that you updated above.
-
Click the checkbox for overwriting existing files.
-
Click 'Upload'.
Change the 'Category' in Product.csv file:
- Go back to your browser window where 'Azure Synapse Analytics' is already open. In case it's not open, kindly follow steps 1 to 8 mentioned above.
- Select 'Product.csv'.
- Click 'Download' button on the top toolbar in Azure Synapse Analytics Studio. File will get downloaded in your system locally.
Note: In this demo, we change one category. In real-life you would have multiple categories, and you would be inserting categories aligned to your customer.
-
Open the downloaded file. In case file does not open in Microsoft Excel, kindly navigate to the folder where file got downloaded and right click on the file name. Click 'Open With...' and then click 'Excel'.
-
Select 'Category' column (Column G of Excel).
-
Press 'CTRL + H' to replace exisitng campaign name with new campaign name.
-
Replace 'Hats' (old category name) with 'Gift Cards' (new category name).
-
Click 'Replace All'.
-
Pop up will be displayed with 'All done...' replacement message.
-
Click OK.
-
Save the file by pressing the highlighted button. Close the file.
-
Go back to your browser window where 'Azure Synapse Analytics' is already open. In case it's not open, kindly follow steps 1 to 8 mentioned above. Once you have followed the steps, click 'Upload' button in 'Azure Synapse Analytics Studio' to upload the file from your local system.
-
Select 'Product.csv' file that you just updated.
-
Click the checkbox for overwriting existing files.
-
Click 'Upload'.
To change 'Hashtags':
- Go back to your browser window where 'Azure Synapse Analytics' is already open. In case it's not open, kindly follow steps 1 to 8 mentioned above.
- Select 'Campaignproducts.csv'.
- Click 'Download' button on the top toolbar in Azure Synapse Analytics Studio. File will get downloaded in your system locally.
Note: In this demo, we change one hashtag. In real-life you would have multiple hashtags, and you would be inserting hashtags aligned to your customer.
-
Open the downloaded file. In case file does not get opened in Microsoft Excel, kindly navigate to the folder where file got downloaded and right click on the file name. Click 'Open With...' and then click 'Excel'.
-
Select 'Hashtag' column (Column C of Excel) and press 'CTRL + H' to replace exisitng campaign name with new campaign name.
-
Replace '#welcomespring' (old Hashtag) with '#welcomesummer' (new Hashtag).
-
Click 'Replace All'.
-
Pop up will be displayed with 'All done...' replacement message.
-
Click OK.
-
Save the file by pressing the highlighted button. Close the file.
-
Go back to your browser window where 'Azure Synapse Analytics' is already open. In case it's not open, kindly follow steps 1 to 8 mentioned above. Once you have followed the steps, click 'Upload' button in 'Azure Synapse Analytics Studio' to upload the file from your local system.
-
Select 'Campaignproducts.csv' file that you updated above.
-
Click the checkbox for overwriting existing files.
-
Click 'Upload'.
Update the dataset with this new data:
-
Navigate to 'Integrate' hub from the left navigation in the 'Synapse Analytics' workspace.
-
Expand 'Pipelines' node.
-
Click on '1 Master Pipeline'.
-
Click 'Add trigger'.
-
Click 'Trigger now'.
-
Click 'OK'
-
Navigate to 'Monitor' hub from the left navigation.
-
Click 'Pipeline runs'.
-
Observe '1 Master Pipeline'.
View changes to Power BI:
-
Navigate to 'Develop' hub from the left navigation.
-
Expand 'Power BI'.
-
Expand Power BI Workspace starting with name 'Engagement Accelerators...'.
-
Expand 'Power BI reports'.
-
Click on 'Campaign - Option C' Power BI report.
-
'Campaign Name' should have one of the updated campaign name as 'Summer Fashion'.
-
'Product Category' should have one of the updated category as 'Gift Cards'.
-
'Hashtag' should have one of the updated Hashtag as '#welcomesummer'.
Your Accelerator environment is now set up.
- Go to https://customvision.ai/ and click on 'Sign In'.
- Select 'I agree' checkbox and click on 'I Agree’ button.
Note: If you get any sensitive information related warning then click on 'OK'.
- Select your cognitive service resource from the 'Resource' dropdown starting with name 'dreamcognitiveservices'.
- Select project '1_Defective_Product_Classification'.
- Select 'iteration 1' from the iteration dropdown.
- Click on the 'Performance' tab.
Note: Wait for training to complete if it shows the model is in training.
- Click on 'Publish' button.
- Select 'Model name' and 'Prediction resource' on 'Publish Model' popup and click on 'Publish' button.
- Click on the 'Eye' button.
- Repeat steps 4 to 8 for all the projects.
- Open Azure Synapse in a new tab using the following link: https://web.azuresynapse.net/.
- Log in with your Azure credentials.
- Select the 'Subscription' and Synapse 'Workspace name' that got created in Task 3. The Synapse 'Workspace name' will start with 'manufacturingdemo'.
- Click 'Continue'.
- Click the 'Data' hub from the left navigation in the Synapse Analytics workspace.
- Click 'Linked' tab.
- Expand the storage account / Azure Data Lake Storage Gen2.
- Expand the node that starts with 'manufacturingdemo'.
- Click 'incidentreport' container.
- Click the 'Upload' button in Azure Synapse Analytics Studio to upload the file from your local system.
- Download incident report by clicking following url: https://dreamdemostrggen2r16gxwb.blob.core.windows.net/publicassets/212045001.pdf
- Select the '212045001.pdf' file or any incident report of same format from your local system.
Note: Filename and incident id should be same.
- Check the checkbox for overwriting existing files.
- Click on 'Upload' button.
- Click on the document that got uploaded.
- Click on More.
- Click on Properties.
- Confirm that the Content type of document is application/pdf. If not paste 'application/pdf' in the 'Content Type' of document.
- Click on 'Apply'.
Note: Please perform these steps after your demo is done and you do not need the environment anymore. Also ensure you Resume the environment before demo if you paused it once.
-
Open the Azure Portal.
-
Click on the Azure Cloud Shell icon from the top toolbar.
Execute the Pause_Resume_script.ps1
script by executing the following command:
-
Run Command:
cd 'MfgAI/Manufacturing/automation'
-
Then run the PowerShell script:
./Pause_Resume_script.ps1
-
From the Azure Cloud Shell, copy the authentication code.
-
Click on the link https://microsoft.com/devicelogin and a new browser window will launch.
- Paste the authentication code.
-
Select the same user that you used for signing into the Azure Portal in Task 1.
-
Close this window after it displays successful authentication message.
-
You will be prompted for one more device authentication.
-
Follow steps 3 to 6 again for the new authentication.
- When prompted, enter the resource group name to be deleted in the Azure Cloud Shell. Type the same resource group name that you created.
-
Enter your choice when prompted. Enter 'P' for pausing the environment or 'R' for resuming a paused environment.
-
Wait for script to finish execution.
Note: Perform these steps after your demo is done and you do not need the resources anymore.
Open the Azure Portal.
- Open the Azure Cloud Shell by clicking its icon from the top toolbar.
Execute the 'resourceCleanup.ps1' script by executing the following commands:
-
Run Command:
cd 'MfgAI/Manufacturing/automation'
-
Then run the PowerShell script:
./resourceCleanup.ps1
- You will now be prompted to enter the resource group name to be deleted in the Azure Cloud Shell. Type the same resource group name that you created in Task 1 - 'Synapse-WWI-Lab'.
-
Wait for execution to complete.
-
Navigate to Power BI Workspace.
-
Click on Workspaces.
-
Click on options of the workspace you created in task #2
-
Click on Workspace settings.
-
Click on Delete Workspace.
-
Click on Delete button in popup.