1
00:00:04,730 --> 00:00:11,150
Now that we know a little about relational databases, SQL, and Transact-sql, it's time to dig in

2
00:00:11,150 --> 00:00:12,260
and put them to work.

3
00:00:12,290 --> 00:00:16,880
A great way to learn new skills is to create a useful project that utilizes them.

4
00:00:16,880 --> 00:00:23,420
We'll be designing a database and then using SQL Scripting and Graphics Designer to create a useful

5
00:00:23,420 --> 00:00:26,480
application that lets us track production defects.

6
00:00:26,510 --> 00:00:31,760
This exercise will expose you to some of the challenges and considerations you will face when developing

7
00:00:31,760 --> 00:00:35,030
database driven applications for your company or customers.

8
00:00:35,030 --> 00:00:38,270
So let's take a look at the current situation.

9
00:00:38,270 --> 00:00:41,210
Introducing the Production Defect Tracking project.

10
00:00:41,210 --> 00:00:46,550
The manufacturing line is missing daily production goals due to high production defect rates.

11
00:00:46,550 --> 00:00:52,280
We'll need to capture and identify the cause of production defects to reduce their impact on our production

12
00:00:52,280 --> 00:00:59,120
goals, operators will need to record production defects via wink screens at the operator stations,

13
00:00:59,120 --> 00:01:03,980
repair technicians should enter notes on existing defects when they analyze them.

14
00:01:03,980 --> 00:01:09,500
The supervisor will identify and resolve supply chain issues that cause these defects.

15
00:01:10,540 --> 00:01:12,910
Now let's take a look at the plant floor.

16
00:01:12,940 --> 00:01:16,840
This is the, I guess, battery production line number one.

17
00:01:16,840 --> 00:01:24,640
There are four operator stations where operators will assemble, power up, test, and pack new batteries

18
00:01:24,760 --> 00:01:25,690
behind them.

19
00:01:25,690 --> 00:01:32,650
There are three repair stations for each defect category cosmetic and packing, electrical and functional

20
00:01:32,650 --> 00:01:34,390
Assembly and mechanical.

21
00:01:34,390 --> 00:01:40,930
We need to capture and record defects from the manufacturing line such as missing or damaged parts,

22
00:01:40,930 --> 00:01:45,520
incorrect assembly, no or low power bad temperature readings.

23
00:01:45,520 --> 00:01:53,080
Power not stable cosmetic damage, packing material issues, box label damage, box tape or seal, bad

24
00:01:53,080 --> 00:01:54,820
or other defects.

25
00:01:54,820 --> 00:02:00,760
There's also a supervisor station where supervisors add comments to defect records that are caused by

26
00:02:00,760 --> 00:02:03,670
operational or supply chain issues.

27
00:02:03,670 --> 00:02:09,970
Our task is to create a database driven application that models the process and allows production defects

28
00:02:09,970 --> 00:02:12,580
to be captured, analyzed, and reported.

29
00:02:12,580 --> 00:02:15,610
Our requirements for this project are as follows.

30
00:02:15,610 --> 00:02:22,180
We need to design a relational database that models process entities to capture defect data, including

31
00:02:22,180 --> 00:02:27,010
staff stations, defect categories, and defect reasons.

32
00:02:27,010 --> 00:02:32,410
We'll add Ansi C screens to allow, add, update and delete functions for all entities.

33
00:02:32,410 --> 00:02:38,710
Operators will record defects and assign a category and a reason, as well as notes that are relevant

34
00:02:38,710 --> 00:02:39,910
to the defect.

35
00:02:40,300 --> 00:02:43,930
Repair technicians will add comments to existing defect records.

36
00:02:43,930 --> 00:02:46,780
Once they've analyzed and corrected the problem.

37
00:02:46,780 --> 00:02:52,090
Supervisors will add comments to defect records that are due to operations or supply chain issues.

38
00:02:52,090 --> 00:02:58,570
Production defects reports should be generated from the database weekly or manually for analysis.

39
00:02:58,570 --> 00:03:04,360
So here is our task list for this project that will cover the next couple of sections of this course.

40
00:03:04,360 --> 00:03:06,670
First, we'll create a production database.

41
00:03:06,670 --> 00:03:10,780
And then we'll define process entities and create relational tables.

42
00:03:10,780 --> 00:03:17,440
We'll learn how to add initial data into the tables via the SQL Server Management Service UI, as well

43
00:03:17,440 --> 00:03:19,210
as doing straight SQL commands.

44
00:03:19,210 --> 00:03:24,580
Then we'll create Wehncke screens and write VB scripts to create our database interfaces.

45
00:03:24,580 --> 00:03:30,910
We'll enter data via these interfaces for testing and then create and refine production defect reports.