Skip to content

Commit 1c6aec4

Browse files
Merge pull request #275 from microsoft/wkshop-data-change
chore: Workshop data change
2 parents f565b9c + dfba16e commit 1c6aec4

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

42 files changed

+4287
-3938
lines changed

data/default/_generated_script.py

Lines changed: 61 additions & 615 deletions
Large diffs are not rendered by default.
Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
1-
{
2-
"_comment": "This file is populated when you run 02_create_fabric_items.py",
3-
"lakehouse_id": null,
4-
"lakehouse_name": null,
5-
"ontology_id": null,
6-
"ontology_name": null,
7-
"solution_name": null,
8-
"created_at": null
1+
{
2+
"_comment": "This file is populated when you run 02_create_fabric_items.py",
3+
"lakehouse_id": null,
4+
"lakehouse_name": null,
5+
"ontology_id": null,
6+
"ontology_name": null,
7+
"solution_name": null,
8+
"created_at": null
99
}
Lines changed: 49 additions & 223 deletions
Original file line numberDiff line numberDiff line change
@@ -1,224 +1,50 @@
1-
{
2-
"scenario": "telecommunications",
3-
"name": "Network Operations and Outage Tracking",
4-
"description": "Management of telecommunications network operations with outage tracking and trouble ticket management",
5-
"tables": {
6-
"customers": {
7-
"columns": [
8-
"customer_id",
9-
"name",
10-
"city",
11-
"signup_date"
12-
],
13-
"types": {
14-
"customer_id": "String",
15-
"name": "String",
16-
"city": "String",
17-
"signup_date": "Date"
18-
},
19-
"key": "customer_id",
20-
"source_table": "customers"
21-
},
22-
"technicians": {
23-
"columns": [
24-
"technician_id",
25-
"name",
26-
"department",
27-
"hire_date"
28-
],
29-
"types": {
30-
"technician_id": "String",
31-
"name": "String",
32-
"department": "String",
33-
"hire_date": "Date"
34-
},
35-
"key": "technician_id",
36-
"source_table": "technicians"
37-
},
38-
"network_nodes": {
39-
"columns": [
40-
"node_id",
41-
"node_type",
42-
"location",
43-
"status",
44-
"last_maintenance_date"
45-
],
46-
"types": {
47-
"node_id": "String",
48-
"node_type": "String",
49-
"location": "String",
50-
"status": "String",
51-
"last_maintenance_date": "Date"
52-
},
53-
"key": "node_id",
54-
"source_table": "network_nodes"
55-
},
56-
"tickets": {
57-
"columns": [
58-
"ticket_id",
59-
"customer_id",
60-
"technician_id",
61-
"node_id",
62-
"priority",
63-
"status",
64-
"issue_type",
65-
"date_created",
66-
"date_resolved"
67-
],
68-
"types": {
69-
"ticket_id": "String",
70-
"customer_id": "String",
71-
"technician_id": "String",
72-
"node_id": "String",
73-
"priority": "String",
74-
"status": "String",
75-
"issue_type": "String",
76-
"date_created": "Date",
77-
"date_resolved": "Date"
78-
},
79-
"key": "ticket_id",
80-
"source_table": "tickets"
81-
},
82-
"outages": {
83-
"columns": [
84-
"outage_id",
85-
"node_id",
86-
"start_date",
87-
"duration_hours",
88-
"severity"
89-
],
90-
"types": {
91-
"outage_id": "String",
92-
"node_id": "String",
93-
"start_date": "Date",
94-
"duration_hours": "BigInt",
95-
"severity": "String"
96-
},
97-
"key": "outage_id",
98-
"source_table": "outages"
99-
},
100-
"work_orders": {
101-
"columns": [
102-
"work_order_id",
103-
"ticket_id",
104-
"technician_id",
105-
"type",
106-
"status",
107-
"date_created",
108-
"date_completed",
109-
"duration_hours"
110-
],
111-
"types": {
112-
"work_order_id": "String",
113-
"ticket_id": "String",
114-
"technician_id": "String",
115-
"type": "String",
116-
"status": "String",
117-
"date_created": "Date",
118-
"date_completed": "Date",
119-
"duration_hours": "BigInt"
120-
},
121-
"key": "work_order_id",
122-
"source_table": "work_orders"
123-
},
124-
"maintenance_records": {
125-
"columns": [
126-
"maintenance_id",
127-
"node_id",
128-
"technician_id",
129-
"maintenance_type",
130-
"date_performed"
131-
],
132-
"types": {
133-
"maintenance_id": "String",
134-
"node_id": "String",
135-
"technician_id": "String",
136-
"maintenance_type": "String",
137-
"date_performed": "Date"
138-
},
139-
"key": "maintenance_id",
140-
"source_table": "maintenance_records"
141-
},
142-
"service_sla_metrics": {
143-
"columns": [
144-
"sla_id",
145-
"ticket_id",
146-
"response_time_hours",
147-
"resolution_time_hours"
148-
],
149-
"types": {
150-
"sla_id": "String",
151-
"ticket_id": "String",
152-
"response_time_hours": "BigInt",
153-
"resolution_time_hours": "BigInt"
154-
},
155-
"key": "sla_id",
156-
"source_table": "service_sla_metrics"
157-
}
158-
},
159-
"relationships": [
160-
{
161-
"name": "ticket_customer",
162-
"from": "tickets",
163-
"to": "customers",
164-
"fromKey": "customer_id",
165-
"toKey": "customer_id"
166-
},
167-
{
168-
"name": "ticket_technician",
169-
"from": "tickets",
170-
"to": "technicians",
171-
"fromKey": "technician_id",
172-
"toKey": "technician_id"
173-
},
174-
{
175-
"name": "ticket_node",
176-
"from": "tickets",
177-
"to": "network_nodes",
178-
"fromKey": "node_id",
179-
"toKey": "node_id"
180-
},
181-
{
182-
"name": "outage_node",
183-
"from": "outages",
184-
"to": "network_nodes",
185-
"fromKey": "node_id",
186-
"toKey": "node_id"
187-
},
188-
{
189-
"name": "workorder_ticket",
190-
"from": "work_orders",
191-
"to": "tickets",
192-
"fromKey": "ticket_id",
193-
"toKey": "ticket_id"
194-
},
195-
{
196-
"name": "workorder_technician",
197-
"from": "work_orders",
198-
"to": "technicians",
199-
"fromKey": "technician_id",
200-
"toKey": "technician_id"
201-
},
202-
{
203-
"name": "maintenance_node",
204-
"from": "maintenance_records",
205-
"to": "network_nodes",
206-
"fromKey": "node_id",
207-
"toKey": "node_id"
208-
},
209-
{
210-
"name": "maintenance_technician",
211-
"from": "maintenance_records",
212-
"to": "technicians",
213-
"fromKey": "technician_id",
214-
"toKey": "technician_id"
215-
},
216-
{
217-
"name": "sla_ticket",
218-
"from": "service_sla_metrics",
219-
"to": "tickets",
220-
"fromKey": "ticket_id",
221-
"toKey": "ticket_id"
222-
}
223-
]
1+
{
2+
"scenario": "telecommunications",
3+
"name": "Network Operations",
4+
"description": "Tracking outages and trouble tickets.",
5+
"tables": {
6+
"tickets": {
7+
"columns": [
8+
"ticket_id",
9+
"customer_name",
10+
"issue_description",
11+
"priority",
12+
"status"
13+
],
14+
"types": {
15+
"ticket_id": "String",
16+
"customer_name": "String",
17+
"issue_description": "String",
18+
"priority": "String",
19+
"status": "String"
20+
},
21+
"key": "ticket_id",
22+
"source_table": "tickets"
23+
},
24+
"inspections": {
25+
"columns": [
26+
"inspection_id",
27+
"ticket_id",
28+
"result",
29+
"score"
30+
],
31+
"types": {
32+
"inspection_id": "String",
33+
"ticket_id": "String",
34+
"result": "String",
35+
"score": "BigInt"
36+
},
37+
"key": "inspection_id",
38+
"source_table": "inspections"
39+
}
40+
},
41+
"relationships": [
42+
{
43+
"name": "ticket_inspection",
44+
"from": "inspections",
45+
"to": "tickets",
46+
"fromKey": "ticket_id",
47+
"toKey": "ticket_id"
48+
}
49+
]
22450
}
Lines changed: 19 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -1,20 +1,19 @@
1-
=== SQL QUESTIONS (Fabric Data) ===
2-
1. How many open tickets are currently assigned to technicians in the Repair department?
3-
2. What is the average duration in hours of work orders classified as Emergency Repair?
4-
3. Show the count of outages grouped by severity level for the last six months.
5-
4. Which technician has the highest number of resolved tickets in the last three months?
6-
5. What is the monthly trend of network node maintenance activities performed?
7-
8-
=== DOCUMENT QUESTIONS (AI Search) ===
9-
1. According to the Network Operations Policy, what is the maximum time allowed for ticket resolution?
10-
2. What are the required safety procedures technicians must follow during field operations?
11-
3. Which communication channels are specified for notifying customers about outages in the Outage Management Guidelines?
12-
4. How often must network nodes undergo scheduled maintenance as described in the Maintenance Scheduling and Standards?
13-
5. What penalties apply if SLA response time commitments are not met, according to the SLA Policies?
14-
15-
=== COMBINED INSIGHT QUESTIONS ===
16-
1. Are any outage durations exceeding the limits set in the Outage Duration Thresholds of the Network Operations Policy?
17-
2. Which work orders have durations longer than allowed by the Work Order Duration section in the Technician Work Order Procedures?
18-
3. Do any tickets have response times that violate the Response Time Commitments stated in the SLA Policies?
19-
4. Which network nodes have not received maintenance within the 90-day period required by the Maintenance Scheduling and Standards?
20-
5. Are there technicians whose quality inspection pass rates fall below the minimum threshold described in the Quality Assurance Manual?
1+
=== SQL QUESTIONS (Fabric Data) ===
2+
1. How many tickets are high priority?
3+
2. What is the average score from inspections?
4+
3. Show tickets grouped by status.
5+
4. Which ticket has the highest priority?
6+
5. How does inspection result distribution compare across ticket statuses?
7+
8+
=== DOCUMENT QUESTIONS (AI Search) ===
9+
1. What constitutes a failed inspection?
10+
2. What are the requirements for handling customer tickets?
11+
3. How quickly should high priority tickets be resolved?
12+
4. What actions are required for tickets not meeting feedback standards?
13+
5. How often must failed inspections be reviewed?
14+
15+
=== COMBINED INSIGHT QUESTIONS ===
16+
1. Do any inspections violate quality control standards in our Inspection Procedures?
17+
2. Are there any tickets that require follow-up assessments based on our Inspection Procedures?
18+
3. What is our average inspection score, and does it meet the minimum standard outlined in our Quality Control Standards?
19+
4. How many tickets are open and exceeding response targets set in our Ticket Management Policy?

0 commit comments

Comments
 (0)