1
00:00:03,000 --> 00:00:08,250
Welcome to the XANDER practical masterclass. We will build a training company

2
00:00:08,250 --> 00:00:12,410
and a small fiber network together, then take a field job all

3
00:00:12,410 --> 00:00:17,046
the way through to review and reporting. Every action will appear on

4
00:00:17,046 --> 00:00:17,524
screen.

5
00:00:18,640 --> 00:00:23,450
The narration uses an AI generated voice. The company, people, sites and

6
00:00:23,450 --> 00:00:28,127
network records in this course are fictional. We are using an isolated

7
00:00:28,127 --> 00:00:32,603
copy of the published application, so these lessons do not change a

8
00:00:32,603 --> 00:00:33,739
customer network.

9
00:00:34,840 --> 00:00:39,500
Watch the highlighted control and the pointer. I will explain why we

10
00:00:39,500 --> 00:00:43,749
need a field, enter an example, save it, and check the result.

11
00:00:43,749 --> 00:00:48,067
Pause whenever you want to repeat a step in your own workspace.

12
00:00:49,168 --> 00:00:54,417
The course is divided into chapters. Start with account and company setup,

13
00:00:54,417 --> 00:01:00,376
then continue to people, customers, assets and connections. The later chapters cover

14
00:01:00,376 --> 00:01:04,065
field work, timers, evidence, approvals and exports.

15
00:01:08,168 --> 00:01:11,836
On the sign in screen, choose Request a seven day demo. If

16
00:01:11,836 --> 00:01:16,515
your employer already has a workspace, ask its administrator to invite you

17
00:01:16,515 --> 00:01:21,195
instead. A new request creates a separate company, not another user inside

18
00:01:21,195 --> 00:01:22,586
your existing company.

19
00:01:23,688 --> 00:01:28,733
The company name is required. We will use XANDER Academy Demo. Choose

20
00:01:28,733 --> 00:01:33,777
a recognizable legal or trading name for a real company. The separate

21
00:01:33,777 --> 00:01:36,702
company code is created by the platform.

22
00:01:37,808 --> 00:01:43,374
The registration number is optional. It is useful for company identification, but

23
00:01:43,374 --> 00:01:47,359
it is not your password or sign in code. This example uses

24
00:01:47,359 --> 00:01:49,833
a clearly marked training reference.

25
00:01:50,933 --> 00:01:55,877
The country field expects a two letter country code. We will enter

26
00:01:55,877 --> 00:02:01,270
B E for Belgium. This registration country is separate from the language

27
00:02:01,270 --> 00:02:02,543
of the interface.

28
00:02:03,653 --> 00:02:08,205
Enter the name of the person who will activate the Manager account.

29
00:02:08,205 --> 00:02:13,096
This course uses Alex Morgan. Later we will create separate employee and

30
00:02:13,096 --> 00:02:15,678
user records for the rest of the team.

31
00:02:16,778 --> 00:02:21,016
The work email must be valid and accessible. First, I will enter

32
00:02:21,016 --> 00:02:25,651
an invalid address to demonstrate the browser check. The form must not

33
00:02:25,651 --> 00:02:28,962
submit until the address has a valid email format.

34
00:02:30,063 --> 00:02:35,077
Now we correct the address. This example uses a fictional training mailbox

35
00:02:35,077 --> 00:02:39,549
captured locally. In a real workspace, use your own work email and

36
00:02:39,549 --> 00:02:43,343
check its inbox and spam folder for the activation link.

37
00:02:44,463 --> 00:02:49,450
The available languages are English, Dutch, French and German. We will keep

38
00:02:49,450 --> 00:02:54,571
English for this course. Language changes presentation; it does not create or

39
00:02:54,571 --> 00:02:55,967
move company records.

40
00:02:57,068 --> 00:03:03,028
Review the company, country, contact and email before sending. The notice explains

41
00:03:03,028 --> 00:03:08,262
the trial and payment conditions. Submit the request once, then wait for

42
00:03:08,262 --> 00:03:09,497
the confirmation.

43
00:03:10,598 --> 00:03:15,126
The confirmation means the request was accepted. It does not mean the

44
00:03:15,126 --> 00:03:19,391
account is already activated. The next step is to open the single

45
00:03:19,391 --> 00:03:21,688
use link from the activation email.

46
00:03:25,798 --> 00:03:30,811
Open the activation link from the email. The invitation identifies this company

47
00:03:30,811 --> 00:03:34,619
and user. The link is private and single use; do not forward

48
00:03:34,619 --> 00:03:35,951
it to another person.

49
00:03:37,052 --> 00:03:41,281
Choose a username that identifies your own account. We will use trainer

50
00:03:41,281 --> 00:03:45,748
for this example. Employee numbers and usernames are different identifiers.

51
00:03:46,852 --> 00:03:51,321
Choose a strong password with at least twelve characters. The screen keeps

52
00:03:51,321 --> 00:03:56,272
it masked. Use a password manager rather than copying a colleague’s credentials.

53
00:03:57,373 --> 00:04:03,297
The confirmation must match exactly. We will deliberately enter a different confirmation

54
00:04:03,297 --> 00:04:08,278
and select Continue. This demonstrates a correction on the form before the

55
00:04:08,278 --> 00:04:09,557
account is created.

56
00:04:10,658 --> 00:04:15,228
The error explains what needs correction. Enter the same password again in

57
00:04:15,228 --> 00:04:19,984
the confirmation field. Do not change your intended username just because the

58
00:04:19,984 --> 00:04:21,960
password confirmation was wrong.

59
00:04:23,061 --> 00:04:29,028
Select Continue again. A successful activation creates the account and returns the

60
00:04:29,028 --> 00:04:34,267
company code. Keep that code with your invitation details; you will need

61
00:04:34,267 --> 00:04:35,650
it when signing in.

62
00:04:39,750 --> 00:04:43,341
The sign in form asks for a company code or a unique

63
00:04:43,341 --> 00:04:48,520
company name, followed by your username or verified email and password. The

64
00:04:48,520 --> 00:04:53,285
company identifies the workspace; your account identifies the person.

65
00:04:54,390 --> 00:04:58,560
Enter the company code from the invitation. For clarity, we use the

66
00:04:58,560 --> 00:05:02,917
exact generated code rather than searching for a similar company name.

67
00:05:04,030 --> 00:05:09,732
Now enter the username created during activation. We will use trainer. A

68
00:05:09,732 --> 00:05:14,960
verified email may also be accepted where the account supports it.

69
00:05:16,070 --> 00:05:20,745
First we will use an incorrect password to demonstrate a failed sign

70
00:05:20,745 --> 00:05:25,076
in. The application must keep us outside the company workspace.

71
00:05:26,190 --> 00:05:32,403
Check the company, username and password when sign in fails. Repeated guessing

72
00:05:32,403 --> 00:05:37,900
is not a recovery method. The Forgot password option uses the correct

73
00:05:37,900 --> 00:05:40,927
company and a verified recovery email.

74
00:05:42,030 --> 00:05:46,763
We will correct the password and sign in again. The password stays

75
00:05:46,763 --> 00:05:49,058
masked throughout the recording.

76
00:05:50,158 --> 00:05:55,104
The header shows the training company, account and Manager role. Confirm that

77
00:05:55,104 --> 00:06:00,371
this is the intended workspace before creating records. The welcome guide provides

78
00:06:00,371 --> 00:06:02,555
a sequence of initial setup tasks.

79
00:06:03,655 --> 00:06:07,948
We are now signed in as the training Manager. The following lessons

80
00:06:07,948 --> 00:06:12,689
will create the company details, team and customer records that later work

81
00:06:12,689 --> 00:06:13,394
depends on.

82
00:06:17,495 --> 00:06:22,756
The dashboard is the starting point for the company workspace. My actions

83
00:06:22,756 --> 00:06:27,153
groups work by priority and due date. An empty view is normal

84
00:06:27,153 --> 00:06:29,892
for a new company; it is not an error.

85
00:06:30,992 --> 00:06:37,074
The sidebar is organized into groups. Expand Network to find assets, history,

86
00:06:37,074 --> 00:06:42,050
archive and labels. Expanding a group does not open or modify a

87
00:06:42,050 --> 00:06:42,602
record.

88
00:06:43,712 --> 00:06:48,467
Now open Assets. The heading changes to identify the current tool. Use

89
00:06:48,467 --> 00:06:52,611
the page title to confirm where you are before entering data.

90
00:06:53,712 --> 00:06:58,511
The workspace search in the header helps locate tools. We will search

91
00:06:58,511 --> 00:07:02,824
for Planning instead of manually scanning every sidebar group.

92
00:07:03,924 --> 00:07:08,539
Clear the search after using it so other tools become visible again.

93
00:07:08,539 --> 00:07:12,272
A search filter is a view of the available tools, not a

94
00:07:12,272 --> 00:07:14,375
change to your company records.

95
00:07:15,484 --> 00:07:21,756
The language menu offers English, Dutch, French and German. We will briefly

96
00:07:21,756 --> 00:07:27,777
select Dutch to show the interface change, then return to English. Codes

97
00:07:27,777 --> 00:07:31,624
and saved network identifiers remain the same.

98
00:07:32,724 --> 00:07:37,598
The Back control returns to the previous workspace when it is available.

99
00:07:37,598 --> 00:07:42,404
Scrolling the main page reveals longer forms, while the sidebar has its

100
00:07:42,404 --> 00:07:47,142
own navigation area. Keep unsaved changes in mind when leaving a form.

101
00:07:48,244 --> 00:07:52,235
If a tool is missing, check your role and subscription with the

102
00:07:52,235 --> 00:07:58,695
company administrator. The next lesson separates personal account settings from company configuration.

103
00:08:02,804 --> 00:08:07,709
Open your account menu in the top bar. Profile contains personal details;

104
00:08:07,709 --> 00:08:11,607
it is separate from the company profile used on documents.

105
00:08:12,724 --> 00:08:17,680
The display name is the human readable name shown beside your actions.

106
00:08:17,680 --> 00:08:22,281
We will keep Alex Morgan. Changing this field does not rename the

107
00:08:22,281 --> 00:08:24,547
company or change your username.

108
00:08:25,647 --> 00:08:30,811
The personal phone number belongs to this account. Use the contact details

109
00:08:30,811 --> 00:08:36,534
appropriate for work. It is different from the company’s general contact number.

110
00:08:37,647 --> 00:08:41,739
Save the personal profile and wait for the success message. We will

111
00:08:41,739 --> 00:08:46,014
then reopen the settings menu to review language and account recovery.

112
00:08:47,127 --> 00:08:53,169
Account settings offers interface language, recovery options and password security. The language

113
00:08:53,169 --> 00:08:58,897
here is your preference; company defaults and notification language have separate controls.

114
00:09:00,007 --> 00:09:05,560
Open Email and notifications. The account is verified because we activated it

115
00:09:05,560 --> 00:09:11,617
through its email invitation. A verified address is important for password recovery.

116
00:09:12,727 --> 00:09:16,930
The recovery address should remain accessible to you. We will keep the

117
00:09:16,930 --> 00:09:22,394
verified training address. Changing an address requires verification before it can reliably

118
00:09:22,394 --> 00:09:24,136
be used for account recovery.

119
00:09:25,247 --> 00:09:29,634
Email language can follow the company or use one of the supported

120
00:09:29,634 --> 00:09:34,359
languages. We will explicitly choose English for the training account.

121
00:09:35,459 --> 00:09:40,764
Optional work notifications can be enabled or disabled for this account. This

122
00:09:40,764 --> 00:09:46,688
choice does not disable password recovery, and company notification rules still apply.

123
00:09:46,688 --> 00:09:48,686
We will enable them and save.

124
00:09:49,787 --> 00:09:55,135
For password security, use Change password when you know the current password,

125
00:09:55,135 --> 00:09:59,249
or Forgot password when you need a recovery link. Do not put

126
00:09:59,249 --> 00:10:03,843
passwords or recovery links in job notes, chat or support messages.

127
00:10:04,947 --> 00:10:09,734
This form asks for the current password, a new password and confirmation.

128
00:10:09,734 --> 00:10:14,783
Changing it signs out existing sessions. We will cancel this demonstration so

129
00:10:14,783 --> 00:10:17,865
the course keeps the same training credentials.

130
00:10:21,965 --> 00:10:27,761
Company profile supplies identity details for work documents and other company workflows.

131
00:10:27,761 --> 00:10:32,516
It does not replace an employee record or your personal account settings.

132
00:10:32,516 --> 00:10:36,489
We will fill the training company carefully and save it once.

133
00:10:37,605 --> 00:10:41,594
The company code is read only here. It is the workspace identifier

134
00:10:41,594 --> 00:10:45,884
from registration. A clear company name is useful for people, while the

135
00:10:45,884 --> 00:10:49,269
code distinguishes the workspace when names are similar.

136
00:10:50,369 --> 00:10:57,005
The registration number helps identify the organization. This fictional reference is deliberately

137
00:10:57,005 --> 00:11:01,793
marked as training data. Use the correct registered details for a real

138
00:11:01,793 --> 00:11:02,341
company.

139
00:11:03,449 --> 00:11:08,082
VAT details are optional in this exercise. Enter the actual authorized tax

140
00:11:08,082 --> 00:11:12,902
information when your business needs it on documents. An example video should

141
00:11:12,902 --> 00:11:15,219
never invent a customer tax identity.

142
00:11:16,329 --> 00:11:21,201
The website field is company contact information. It does not change the

143
00:11:21,201 --> 00:11:24,856
address of the XANDER application or deploy a website.

144
00:11:25,969 --> 00:11:30,179
A logo can be uploaded as PNG, JPEG or WebP within the

145
00:11:30,179 --> 00:11:35,637
displayed size limit. We will use the existing XANDER training logo to

146
00:11:35,637 --> 00:11:38,366
demonstrate the upload and preview.

147
00:11:39,466 --> 00:11:43,667
The general email is the company contact address. It is different from

148
00:11:43,667 --> 00:11:46,547
a user’s verified sign in or recovery address.

149
00:11:47,666 --> 00:11:52,388
The support email identifies the company contact for support matters. Use the

150
00:11:52,388 --> 00:11:54,534
address authorized by your company.

151
00:11:55,635 --> 00:11:59,894
The primary company contact can be named on company documents. It does

152
00:11:59,894 --> 00:12:02,875
not grant that person an account or a permission.

153
00:12:03,995 --> 00:12:09,071
A contact title describes the person’s business responsibility. It is separate from

154
00:12:09,071 --> 00:12:10,863
the application security role.

155
00:12:11,964 --> 00:12:16,964
Now enter the company telephone number. Our number is fictional and used

156
00:12:16,964 --> 00:12:19,672
only to make the form example complete.

157
00:12:20,772 --> 00:12:26,873
The company address identifies the organization. Individual field sites can have completely

158
00:12:26,873 --> 00:12:28,214
different addresses.

159
00:12:29,332 --> 00:12:34,345
Use a consistent city name. Network location filters work best when the

160
00:12:34,345 --> 00:12:37,805
same place is not spelled several different ways.

161
00:12:38,906 --> 00:12:43,569
The postcode belongs to the company address. Later we will store separate

162
00:12:43,569 --> 00:12:46,763
location details on network assets and work sites.

163
00:12:47,866 --> 00:12:53,348
The country is human readable company information. This is separate from the

164
00:12:53,348 --> 00:12:57,244
two letter country code used in the registration form.

165
00:12:58,346 --> 00:13:02,668
Billing email identifies the company’s billing contact. We are not making a

166
00:13:02,668 --> 00:13:05,586
purchase or sending an invoice in this setup lesson.

167
00:13:06,706 --> 00:13:11,979
The invoice prefix helps identify documents created for this company. Choose a

168
00:13:11,979 --> 00:13:15,765
stable convention rather than changing it for every job.

169
00:13:16,866 --> 00:13:22,028
Bank account fields should contain only approved company details when needed. We

170
00:13:22,028 --> 00:13:26,545
will leave them blank in this fictional exercise. A profile field does

171
00:13:26,545 --> 00:13:28,997
not verify that a bank account exists.

172
00:13:30,106 --> 00:13:34,919
The public partner profile is separate from your private operational records. Its

173
00:13:34,919 --> 00:13:40,504
description and contact fields control the company information intended for partner discovery.

174
00:13:41,605 --> 00:13:46,740
We will use an explicit training description. Review the visibility option with

175
00:13:46,740 --> 00:13:51,291
your company’s policy before exposing a real public partner listing.

176
00:13:52,405 --> 00:13:57,121
The visibility checkbox controls the partner listing. We will switch it off

177
00:13:57,121 --> 00:14:01,208
for this training company and save the public profile separately.

178
00:14:02,325 --> 00:14:08,420
The time zone should match the company’s operational convention. Consistent time settings

179
00:14:08,420 --> 00:14:12,372
help teams interpret schedules, deadlines and work records.

180
00:14:13,485 --> 00:14:18,933
The default company language is separate from an individual user’s interface choice.

181
00:14:18,933 --> 00:14:22,544
We will keep English, then save the main company profile.

182
00:14:23,645 --> 00:14:29,258
Finally, reopen the profile and check that the address and contact details

183
00:14:29,258 --> 00:14:34,568
persisted. A form containing typed values is not proof of a successful

184
00:14:34,568 --> 00:14:34,947
save.

185
00:14:39,048 --> 00:14:44,923
The organizational hierarchy is company, branch, department or team, then employee. We

186
00:14:44,923 --> 00:14:49,499
will create a regional training branch and a fiber operations team.

187
00:14:50,608 --> 00:14:55,364
First select Add Branch with empty required fields. The application must refuse

188
00:14:55,364 --> 00:14:59,879
an incomplete branch rather than create a record with no useful identifier.

189
00:15:00,980 --> 00:15:05,410
A branch code is a stable identifier. We will use ACA BR

190
00:15:05,410 --> 00:15:10,790
zero one. Keep the code clear enough to distinguish this branch from

191
00:15:10,790 --> 00:15:13,005
another office or warehouse.

192
00:15:14,105 --> 00:15:19,050
The branch name is human readable. It can describe the operational location

193
00:15:19,050 --> 00:15:21,292
without changing the company name.

194
00:15:22,393 --> 00:15:28,631
Branch type offers Head Office, Regional Office, Field Office, Warehouse and Other.

195
00:15:28,631 --> 00:15:34,418
Select the type that describes this location. We will choose Regional Office.

196
00:15:35,518 --> 00:15:39,568
Enter the branch country. A branch can have its own location even

197
00:15:39,568 --> 00:15:41,812
when it belongs to the same company.

198
00:15:42,918 --> 00:15:48,177
Enter the branch city. Use a consistent spelling so employee and planning

199
00:15:48,177 --> 00:15:50,626
filters remain easy to understand.

200
00:15:51,726 --> 00:15:56,113
The branch address is different from a customer work site. Our course

201
00:15:56,113 --> 00:15:58,338
uses a fictional operations office.

202
00:15:59,446 --> 00:16:05,391
The postcode completes the branch address. Check the location before assigning people

203
00:16:05,391 --> 00:16:06,580
to a real branch.

204
00:16:07,686 --> 00:16:12,254
The phone is a branch contact number. It does not replace an

205
00:16:12,254 --> 00:16:14,767
employee’s own contact details.

206
00:16:15,886 --> 00:16:20,472
Use the branch email where your company needs a shared contact. Our

207
00:16:20,472 --> 00:16:25,264
training mailbox does not send messages outside the local environment.

208
00:16:26,366 --> 00:16:31,254
Save the branch. The table should now contain the code, name, type

209
00:16:31,254 --> 00:16:33,031
and location we entered.

210
00:16:34,132 --> 00:16:38,662
A department belongs to a branch. Select the branch we just created

211
00:16:38,662 --> 00:16:41,840
so the team appears under the correct location.

212
00:16:42,940 --> 00:16:46,981
Give the department a short stable code. We will use FIBER for

213
00:16:46,981 --> 00:16:48,872
the training operations team.

214
00:16:49,980 --> 00:16:54,389
Now enter the team name. An employee can later reference both the

215
00:16:54,389 --> 00:16:56,221
branch and this department.

216
00:16:57,340 --> 00:17:01,776
Save the department and verify the hierarchy in the table. We now

217
00:17:01,776 --> 00:17:05,870
have a branch and a team, but no employees or login accounts

218
00:17:05,870 --> 00:17:06,143
yet.

219
00:17:10,260 --> 00:17:14,709
We will add Sam Taylor as an employee. This creates personnel master

220
00:17:14,709 --> 00:17:18,700
data. It does not create a login, verify an email address, or

221
00:17:18,700 --> 00:17:20,466
assign the person to a job.

222
00:17:21,580 --> 00:17:25,867
The employee or badge number is required and should be unique within

223
00:17:25,867 --> 00:17:29,649
the company. Use your organization’s numbering convention.

224
00:17:30,750 --> 00:17:35,613
Job title describes the employee’s operational work. In this example it is

225
00:17:35,613 --> 00:17:40,285
Technician. The login role will be selected separately when we create the

226
00:17:40,285 --> 00:17:40,797
account.

227
00:17:41,910 --> 00:17:46,152
Enter the first name. Correct names help the office choose the right

228
00:17:46,152 --> 00:17:48,522
person during planning and assignment.

229
00:17:49,630 --> 00:17:54,817
Enter the last name. We are using fictional people for all course

230
00:17:54,817 --> 00:17:55,615
exercises.

231
00:17:56,715 --> 00:18:00,379
The display name is the name used in operational lists. Keep it

232
00:18:00,379 --> 00:18:03,636
recognizable and consistent with the person’s account.

233
00:18:04,755 --> 00:18:09,332
Add the employee’s work email. This field alone does not verify the

234
00:18:09,332 --> 00:18:12,250
email for account recovery or notifications.

235
00:18:13,355 --> 00:18:18,326
Phone and mobile can be stored separately. Use the work contact appropriate

236
00:18:18,326 --> 00:18:19,851
for field coordination.

237
00:18:20,955 --> 00:18:25,910
The mobile field is employee information. Adding a number does not itself

238
00:18:25,910 --> 00:18:28,557
send a notification or enroll a device.

239
00:18:29,675 --> 00:18:34,891
Select the regional branch and Fiber Operations team. These links keep the

240
00:18:34,891 --> 00:18:38,627
employee inside the correct organizational hierarchy.

241
00:18:39,728 --> 00:18:45,418
Employment status offers Active, On leave, Inactive and Ended. The status should

242
00:18:45,418 --> 00:18:51,392
reflect the actual employment situation. We will keep this training employee Active.

243
00:18:52,492 --> 00:18:58,058
Contract type and dates are personnel information. They are not job deadlines.

244
00:18:58,058 --> 00:19:01,912
We will label the contract type as a training example.

245
00:19:03,013 --> 00:19:08,258
Contract start, contract end and hire date can be recorded when needed.

246
00:19:08,258 --> 00:19:13,429
Leave unknown dates empty instead of inventing them. Each date has its

247
00:19:13,429 --> 00:19:14,315
own meaning.

248
00:19:15,416 --> 00:19:20,765
On Call and its priority help identify employees for coverage. A checked

249
00:19:20,765 --> 00:19:25,149
flag does not create an on call schedule by itself. We will

250
00:19:25,149 --> 00:19:27,600
mark this technician as eligible.

251
00:19:28,701 --> 00:19:34,729
Notes should contain relevant employee information, not passwords or private service keys.

252
00:19:34,729 --> 00:19:38,079
This note clearly identifies the fictional record.

253
00:19:39,181 --> 00:19:43,269
Save the employee, then check the list for the badge number and

254
00:19:43,269 --> 00:19:47,681
name. The success message reminds us that sign in access still needs

255
00:19:47,681 --> 00:19:48,654
a user account.

256
00:19:52,755 --> 00:19:57,635
We will add Jordan Lee as an employee. This creates personnel master

257
00:19:57,635 --> 00:20:02,013
data. It does not create a login, verify an email address, or

258
00:20:02,013 --> 00:20:03,951
assign the person to a job.

259
00:20:05,052 --> 00:20:09,339
The employee or badge number is required and should be unique within

260
00:20:09,339 --> 00:20:13,121
the company. Use your organization’s numbering convention.

261
00:20:14,222 --> 00:20:19,137
Job title describes the employee’s operational work. In this example it is

262
00:20:19,137 --> 00:20:23,858
Supervisor. The login role will be selected separately when we create the

263
00:20:23,858 --> 00:20:24,375
account.

264
00:20:25,476 --> 00:20:29,718
Enter the first name. Correct names help the office choose the right

265
00:20:29,718 --> 00:20:32,088
person during planning and assignment.

266
00:20:33,196 --> 00:20:38,383
Enter the last name. We are using fictional people for all course

267
00:20:38,383 --> 00:20:39,181
exercises.

268
00:20:40,281 --> 00:20:43,945
The display name is the name used in operational lists. Keep it

269
00:20:43,945 --> 00:20:47,202
recognizable and consistent with the person’s account.

270
00:20:48,321 --> 00:20:52,898
Add the employee’s work email. This field alone does not verify the

271
00:20:52,898 --> 00:20:55,816
email for account recovery or notifications.

272
00:20:56,921 --> 00:21:02,137
Select the regional branch and Fiber Operations team. These links keep the

273
00:21:02,137 --> 00:21:05,873
employee inside the correct organizational hierarchy.

274
00:21:06,974 --> 00:21:12,664
Employment status offers Active, On leave, Inactive and Ended. The status should

275
00:21:12,664 --> 00:21:18,638
reflect the actual employment situation. We will keep this training employee Active.

276
00:21:19,738 --> 00:21:25,766
Notes should contain relevant employee information, not passwords or private service keys.

277
00:21:25,766 --> 00:21:29,116
This note clearly identifies the fictional record.

278
00:21:30,218 --> 00:21:34,306
Save the employee, then check the list for the badge number and

279
00:21:34,306 --> 00:21:38,718
name. The success message reminds us that sign in access still needs

280
00:21:38,718 --> 00:21:39,691
a user account.

281
00:21:43,792 --> 00:21:49,123
People and access lists named accounts separately from employees. We will create

282
00:21:49,123 --> 00:21:54,120
a local account for Jordan and link the existing Supervisor employee. Email

283
00:21:54,120 --> 00:21:58,784
invitations are the preferred alternative when delivery is configured.

284
00:21:59,885 --> 00:22:06,123
Choose Create local account. This route provisions access without an email invitation,

285
00:22:06,123 --> 00:22:09,677
so the initial password must be handled securely.

286
00:22:10,777 --> 00:22:16,766
Select Jordan’s existing employee record. The application retains the linked personnel details,

287
00:22:16,766 --> 00:22:20,718
which helps assignment resolve the actual account behind a name.

288
00:22:21,818 --> 00:22:26,481
The display name identifies the local account. We will use the same

289
00:22:26,481 --> 00:22:28,430
name as the linked employee.

290
00:22:29,749 --> 00:22:34,693
Choose a unique account username. This is not the employee badge number

291
00:22:34,693 --> 00:22:36,085
or the company code.

292
00:22:37,394 --> 00:22:42,716
Enter a strong initial password. It stays masked. In real onboarding, use

293
00:22:42,716 --> 00:22:47,454
an invitation so the user can choose their own password when that

294
00:22:47,454 --> 00:22:49,058
workflow is available.

295
00:22:50,158 --> 00:22:55,583
The company role determines the base permissions. Review the available roles, then

296
00:22:55,583 --> 00:23:00,280
select Supervisor for Jordan. Job title and security role should not be

297
00:23:00,280 --> 00:23:00,875
confused.

298
00:23:01,975 --> 00:23:06,994
Create the account, then check that Jordan appears as an active Supervisor

299
00:23:06,994 --> 00:23:12,692
linked to the employee. This local account’s email may still require verification.

300
00:23:16,792 --> 00:23:20,862
Now we will invite Sam through email instead of sharing a temporary

301
00:23:20,862 --> 00:23:25,904
password. This makes the invitation and account activation separate, visible steps.

302
00:23:27,004 --> 00:23:33,669
Select Invite user. The invitation expires and can be revoked before acceptance.

303
00:23:34,770 --> 00:23:40,689
Choose Sam’s existing employee record. Linking the correct employee helps preserve consistent

304
00:23:40,689 --> 00:23:43,244
names and assignments across the company.

305
00:23:44,344 --> 00:23:48,599
Check the full name and work email populated from the employee. A

306
00:23:48,599 --> 00:23:53,509
wrong address can prevent the intended person from receiving an invitation.

307
00:23:54,624 --> 00:23:59,953
Choose Technician as the company role. A technician executes assigned field work;

308
00:23:59,953 --> 00:24:04,097
this is different from preparing or approving all company work.

309
00:24:05,198 --> 00:24:10,233
Send the invitation and inspect its pending status. Pending means the person

310
00:24:10,233 --> 00:24:13,811
has not accepted it yet; it is not proof that an email

311
00:24:13,811 --> 00:24:14,937
reached an inbox.

312
00:24:16,038 --> 00:24:20,829
If the wrong person was invited, revoke the pending invitation and send

313
00:24:20,829 --> 00:24:25,823
a corrected one. If the person already accepted, manage the actual account

314
00:24:25,823 --> 00:24:30,615
instead. We will accept Sam’s training invitation in the next lesson.

315
00:24:34,718 --> 00:24:39,470
Sam opens the private invitation link received by email. The form belongs

316
00:24:39,470 --> 00:24:44,222
to the company that sent the invitation. An invitation should be accepted

317
00:24:44,222 --> 00:24:45,914
by its intended recipient.

318
00:24:47,015 --> 00:24:51,894
Sam chooses a personal username. We will use sam. A shared crew

319
00:24:51,894 --> 00:24:56,541
login would lose the distinction between individual actions.

320
00:24:57,655 --> 00:25:02,391
Enter a strong password and confirm it. The recording keeps both entries

321
00:25:02,391 --> 00:25:06,075
masked. The user chooses the password during activation.

322
00:25:07,575 --> 00:25:12,457
Select Continue to accept the invitation. Wait for the sign in form

323
00:25:12,457 --> 00:25:18,505
before proceeding. A pending invitation and an active account are different states.

324
00:25:19,615 --> 00:25:24,576
The company identifier is retained on the sign in screen. Enter Sam’s

325
00:25:24,576 --> 00:25:27,790
username and password to test the new account.

326
00:25:28,899 --> 00:25:33,698
Sam is now signed in as a Technician. Available workspaces follow this

327
00:25:33,698 --> 00:25:38,634
role and company permissions. An empty task list is expected before work

328
00:25:38,634 --> 00:25:39,457
is assigned.

329
00:25:43,557 --> 00:25:48,774
We are back in the Manager account. Roles and permissions separates base

330
00:25:48,774 --> 00:25:53,991
roles, custom role grants and explicit user access policies. A job title

331
00:25:53,991 --> 00:25:56,093
is not a security permission.

332
00:25:57,197 --> 00:26:02,957
Create role opens the custom permission form. Navigation permissions control access to

333
00:26:02,957 --> 00:26:07,244
workspaces; action permissions control capabilities inside them.

334
00:26:08,357 --> 00:26:12,204
A custom role needs a clear purpose and name. We will inspect

335
00:26:12,204 --> 00:26:16,682
the form without assigning additional privileges to the training users.

336
00:26:17,797 --> 00:26:23,892
Use the description to explain the intended responsibility. Permission choices should follow

337
00:26:23,892 --> 00:26:25,813
the person’s actual duties.

338
00:26:27,477 --> 00:26:31,803
Each checkbox represents a specific grant. A navigation grant is not a

339
00:26:31,803 --> 00:26:36,809
substitute for the action permission. Avoid selecting everything merely to make a

340
00:26:36,809 --> 00:26:37,736
screen visible.

341
00:26:38,837 --> 00:26:44,233
Cancel closes this example without creating a role. The course will continue

342
00:26:44,233 --> 00:26:48,778
with the existing Manager, Supervisor and Technician base roles.

343
00:26:49,878 --> 00:26:55,345
User role assignments show the named people and base roles. Custom roles

344
00:26:55,345 --> 00:27:01,268
and user access policy are separate controls. Check the effective access after

345
00:27:01,268 --> 00:27:03,318
any real permission change.

346
00:27:04,418 --> 00:27:08,879
Return to People and access to confirm that Sam is now active.

347
00:27:08,879 --> 00:27:14,923
Pending invitations are managed separately from accounts that have already accepted.

348
00:27:19,023 --> 00:27:23,712
A customer is the organization receiving the work. Its contacts and field

349
00:27:23,712 --> 00:27:28,079
sites are separate records. We will create one customer and then add

350
00:27:28,079 --> 00:27:31,612
both a responsible person and an independent work site.

351
00:27:32,712 --> 00:27:37,325
Name is required. Select Save changes with an empty form to see

352
00:27:37,325 --> 00:27:41,939
the required field check. The browser keeps the form open so we

353
00:27:41,939 --> 00:27:43,110
can complete it.

354
00:27:44,211 --> 00:27:49,559
Enter a recognizable customer name. This fictional network operator will be linked

355
00:27:49,559 --> 00:27:51,972
to our field job later in the course.

356
00:27:54,451 --> 00:28:00,059
Use a stable customer code. A code helps distinguish similar company names

357
00:28:00,059 --> 00:28:03,924
and makes imports and searches easier to reconcile.

358
00:28:05,025 --> 00:28:09,893
Registration and VAT fields identify the customer organization. We will enter a

359
00:28:09,893 --> 00:28:13,774
training registration reference and leave the tax number empty.

360
00:28:16,193 --> 00:28:20,624
The customer email is a business contact. It does not create an

361
00:28:20,624 --> 00:28:24,421
application account or grant access to your workspace.

362
00:28:26,235 --> 00:28:30,752
Add the general customer phone number. A named on site contact may

363
00:28:30,752 --> 00:28:32,326
use a different number.

364
00:28:35,435 --> 00:28:40,253
The website is contact information. It does not change the application or

365
00:28:40,253 --> 00:28:42,100
publish the customer record.

366
00:28:43,201 --> 00:28:48,485
This address belongs to the customer headquarters. Do not automatically use it

367
00:28:48,485 --> 00:28:50,856
as the location of every field job.

368
00:28:53,721 --> 00:28:58,673
Enter the customer city consistently. The work site we create next will

369
00:28:58,673 --> 00:29:00,696
have its own location fields.

370
00:29:02,577 --> 00:29:07,988
Enter the headquarters postcode. It is independent of the network route coordinates.

371
00:29:10,304 --> 00:29:14,539
Enter the customer country. We keep the training example in one country

372
00:29:14,539 --> 00:29:17,640
so the later address comparisons are easy to follow.

373
00:29:18,744 --> 00:29:23,049
Billing address can differ from the headquarters and the work site. Use

374
00:29:23,049 --> 00:29:26,080
the billing information approved for the customer.

375
00:29:27,184 --> 00:29:33,293
Billing email should reach the correct accounts team. Saving this field does

376
00:29:33,293 --> 00:29:37,072
not send an invoice or charge a payment method.

377
00:29:38,184 --> 00:29:44,555
Use notes for relevant customer context. Keep passwords and service credentials out

378
00:29:44,555 --> 00:29:46,551
of general business notes.

379
00:29:47,664 --> 00:29:53,228
Status can be Active or Inactive. Inactive records remain in history but

380
00:29:53,228 --> 00:29:58,328
are not available for new work. We will keep this customer Active.

381
00:29:59,428 --> 00:30:04,358
Additional information lets you add a named field instead of placing every

382
00:30:04,358 --> 00:30:08,356
detail in one long note. Select Add extra and give the field

383
00:30:08,356 --> 00:30:09,422
a clear meaning.

384
00:30:10,522 --> 00:30:15,107
Save the customer and wait for the directory to return. Check the

385
00:30:15,107 --> 00:30:17,294
name and code before moving on.

386
00:30:18,402 --> 00:30:23,314
Open the saved customer. Its details, contacts and work sites are grouped

387
00:30:23,314 --> 00:30:27,620
here. This confirms the form was saved rather than merely typed.

388
00:30:31,722 --> 00:30:35,990
A named contact records who is responsible at the customer. It is

389
00:30:35,990 --> 00:30:41,046
separate from your own employee list and from the customer’s general email.

390
00:30:42,162 --> 00:30:46,706
Enter the full contact name. We will use Casey Brooks, the fictional

391
00:30:46,706 --> 00:30:48,711
coordinator for this customer.

392
00:30:49,811 --> 00:30:54,540
Role or responsibility explains why this person is relevant. It does not

393
00:30:54,540 --> 00:30:56,839
grant an application security role.

394
00:30:57,939 --> 00:31:02,541
Use the contact’s own work email. Check spelling before using it in

395
00:31:02,541 --> 00:31:04,275
operational communication.

396
00:31:05,379 --> 00:31:10,263
Phone may identify an office line. Store the appropriate contact for the

397
00:31:10,263 --> 00:31:11,620
agreed work process.

398
00:31:12,739 --> 00:31:18,433
Mobile is a separate field for field coordination. The course uses fictional

399
00:31:18,433 --> 00:31:19,033
numbers.

400
00:31:20,139 --> 00:31:25,030
A short note explains this contact’s practical responsibility. Avoid unnecessary personal information.

401
00:31:27,553 --> 00:31:32,922
The Active checkbox determines whether the contact can be selected for new

402
00:31:32,922 --> 00:31:35,825
work. We will leave it checked and save.

403
00:31:36,925 --> 00:31:42,397
The saved contact now appears inside this customer. Another customer’s contacts are

404
00:31:42,397 --> 00:31:45,100
not automatically shared with this record.

405
00:31:49,205 --> 00:31:53,206
A work site describes where the technician should go. It can be

406
00:31:53,206 --> 00:31:58,476
different from the customer headquarters and billing address. Select Add work site.

407
00:31:59,577 --> 00:32:04,032
Give the work site a recognizable name. Later we will choose this

408
00:32:04,032 --> 00:32:06,020
saved site on the work order.

409
00:32:07,137 --> 00:32:12,615
Enter the actual work location. This example deliberately differs from the customer

410
00:32:12,615 --> 00:32:13,473
headquarters.

411
00:32:14,577 --> 00:32:19,899
The city belongs to this work site. Consistent location information helps field

412
00:32:19,899 --> 00:32:22,997
teams avoid travelling to the billing address.

413
00:32:24,098 --> 00:32:29,227
Add the work site postcode. Review it together with the street and

414
00:32:29,227 --> 00:32:29,615
city.

415
00:32:30,716 --> 00:32:34,776
Select the correct country information for the work location.

416
00:32:35,877 --> 00:32:41,217
Latitude and longitude can help locate a site. Our coordinates are training

417
00:32:41,217 --> 00:32:44,351
references, not a surveyed network position.

418
00:32:45,451 --> 00:32:50,573
Longitude is separate from latitude. Always check coordinate order and the accuracy

419
00:32:50,573 --> 00:32:52,116
of your real source data.

420
00:32:53,217 --> 00:32:58,593
Access instructions should be actionable. Tell the technician what to do before

421
00:32:58,593 --> 00:33:02,743
arriving without storing passwords or secret door codes here.

422
00:33:03,857 --> 00:33:08,170
An on site contact can be recorded directly for this location. It

423
00:33:08,170 --> 00:33:11,820
may be different from the customer’s general contact.

424
00:33:12,937 --> 00:33:17,342
Add the phone number appropriate for this site. Our example matches the

425
00:33:17,342 --> 00:33:20,071
coordinator created in the previous chapter.

426
00:33:21,177 --> 00:33:26,218
The site contact email is stored with the location. Review it for

427
00:33:26,218 --> 00:33:28,002
accuracy before saving.

428
00:33:29,103 --> 00:33:35,089
The note clearly identifies this as a training site. Keep operational instructions

429
00:33:35,089 --> 00:33:37,278
in the dedicated access field.

430
00:33:38,383 --> 00:33:42,604
Save the work site and verify its name appears under the customer.

431
00:33:42,604 --> 00:33:46,632
We now have the customer, contact and location ready for a work

432
00:33:46,632 --> 00:33:47,016
order.

433
00:33:51,116 --> 00:33:55,949
A head end is a structured network asset. Its hierarchy contains cabinets

434
00:33:55,949 --> 00:34:01,245
or racks, drawers, cassettes and fiber positions. The structure is distinct from

435
00:34:01,245 --> 00:34:04,290
a cable’s physical tube and fiber inventory.

436
00:34:05,396 --> 00:34:09,847
Name and code are required. Select Save before entering them to see

437
00:34:09,847 --> 00:34:15,029
the validation message. Nothing should be created from an incomplete identity.

438
00:34:16,129 --> 00:34:20,193
Enter a descriptive head end name. Use a name the office and

439
00:34:20,193 --> 00:34:21,955
field teams can recognize.

440
00:34:23,055 --> 00:34:26,797
The head end code is its stable identifier. We will use the

441
00:34:26,797 --> 00:34:30,348
same academy prefix as the rest of our training network.

442
00:34:31,455 --> 00:34:37,029
Enter the network asset address. The Open map button uses location information;

443
00:34:37,029 --> 00:34:40,204
it does not establish a verified cable route.

444
00:34:41,305 --> 00:34:45,763
Postcode and city can be entered separately. The Belgian postcode lookup is

445
00:34:45,763 --> 00:34:47,546
a convenience when applicable.

446
00:34:48,665 --> 00:34:54,044
Use a consistent city value for related assets. This helps searches and

447
00:34:54,044 --> 00:34:54,650
exports.

448
00:34:55,750 --> 00:35:01,154
Coordinates describe the head end location. Use verified survey data for a

449
00:35:01,154 --> 00:35:02,469
real installation.

450
00:35:03,569 --> 00:35:08,927
Check longitude separately. Incorrect coordinate order can place an asset far from

451
00:35:08,927 --> 00:35:10,234
its actual location.

452
00:35:11,335 --> 00:35:15,503
The initial cabinet or rack gets its own code. This code identifies

453
00:35:15,503 --> 00:35:18,054
the physical housing inside the head end.

454
00:35:19,154 --> 00:35:24,121
Choose two drawers for this compact training head end. The application generates

455
00:35:24,121 --> 00:35:26,915
drawer identifiers from the chosen structure.

456
00:35:28,034 --> 00:35:33,693
Choose two cassettes per drawer. This is structural capacity; it does not

457
00:35:33,693 --> 00:35:36,561
connect a cable or make a fiber live.

458
00:35:37,674 --> 00:35:41,836
Fiber positions per cassette offers twelve or twenty four. We will use

459
00:35:41,836 --> 00:35:46,712
twelve, giving two drawers times two cassettes times twelve positions: forty eight

460
00:35:46,712 --> 00:35:47,307
positions.

461
00:35:48,407 --> 00:35:54,807
Save creates the hierarchy. After creation, the structural fields are locked to

462
00:35:54,807 --> 00:36:02,261
protect existing fiber identities. Name, code and location remain separate editable details.

463
00:36:06,367 --> 00:36:11,477
The head end workspace separates its cable list from the hierarchy below.

464
00:36:11,477 --> 00:36:16,027
We will create a physical cable with twenty four tubes and twelve

465
00:36:16,027 --> 00:36:17,147
fibers per tube.

466
00:36:18,248 --> 00:36:23,172
Manual entry and saved standard cables are two ways to populate this

467
00:36:23,172 --> 00:36:28,892
form. A standard provides repeatable specifications. We will use Manual to show

468
00:36:28,892 --> 00:36:30,485
every important field.

469
00:36:31,586 --> 00:36:36,408
Give the cable a stable code. This identifies the cable itself, not

470
00:36:36,408 --> 00:36:38,135
a route or a work order.

471
00:36:39,235 --> 00:36:43,154
Cable type describes its network role. We will use Feeder for the

472
00:36:43,154 --> 00:36:44,179
training example.

473
00:36:45,279 --> 00:36:51,368
Enter twenty four tubes. The total fiber count updates automatically from tube

474
00:36:51,368 --> 00:36:54,178
count multiplied by fibers per tube.

475
00:36:55,279 --> 00:37:00,811
Fibers per tube offers several capacities. Choose twelve. Twenty four times twelve

476
00:37:00,811 --> 00:37:05,399
is two hundred eighty eight, and the automatic total should now show

477
00:37:05,399 --> 00:37:06,209
that number.

478
00:37:07,319 --> 00:37:12,016
Over length records spare length for the cable specification. It is not

479
00:37:12,016 --> 00:37:16,185
the measured length of every route segment. We will use ten for

480
00:37:16,185 --> 00:37:17,111
this exercise.

481
00:37:18,211 --> 00:37:24,243
Direction gives a useful destination description. Text alone does not connect network

482
00:37:24,243 --> 00:37:27,790
assets. We will create explicit connections later.

483
00:37:28,891 --> 00:37:36,303
Destination asset type describes the intended endpoint category. Select ODF. This choice

484
00:37:36,303 --> 00:37:40,767
does not silently create an ODF or terminate a fiber.

485
00:37:41,868 --> 00:37:46,919
Save stores the cable and returns a fresh form. Next stores it

486
00:37:46,919 --> 00:37:52,051
and continues to tube colors. Done stores it and returns to the

487
00:37:52,051 --> 00:37:57,020
head end. We will select Next to inspect the generated tubes.

488
00:37:58,120 --> 00:38:03,141
Twenty four tube cards now exist. Each card identifies its tube number

489
00:38:03,141 --> 00:38:08,018
and fiber range. We will configure colors in the next chapter rather

490
00:38:08,018 --> 00:38:10,815
than confusing color with connectivity.

491
00:38:14,920 --> 00:38:18,913
Tube numbers remain stable when colors change. A cable can use a

492
00:38:18,913 --> 00:38:24,341
standard color convention, including stripes when colors repeat. Match the actual cable

493
00:38:24,341 --> 00:38:26,275
manufacturer’s specification.

494
00:38:27,376 --> 00:38:32,025
For this exercise, tube one will be red. The automatic swap prevents

495
00:38:32,025 --> 00:38:36,742
an unintended duplicate color in the same color group by swapping the

496
00:38:36,742 --> 00:38:38,519
existing color assignment.

497
00:38:39,619 --> 00:38:44,717
The Stripe checkbox distinguishes striped tubes from plain tubes. It is not

498
00:38:44,717 --> 00:38:49,136
a connection status or a live signal indicator. We will keep tube

499
00:38:49,136 --> 00:38:49,815
one plain.

500
00:38:50,916 --> 00:38:55,678
Inspect the lower tube cards. The numbers and fiber ranges continue through

501
00:38:55,678 --> 00:38:59,868
tube twenty four; the unused capacity is still part of this cable.

502
00:39:00,969 --> 00:39:05,034
Save persists the tube color map. Next saves it and opens fiber

503
00:39:05,034 --> 00:39:10,389
definitions. Select Next to inspect all two hundred eighty eight fiber definitions.

504
00:39:11,490 --> 00:39:16,091
Each fiber has a cable wide number and a position within its

505
00:39:16,091 --> 00:39:21,230
tube. The color identifies the physical strand. Do not assume a red

506
00:39:21,230 --> 00:39:24,450
strand is always position one in the tube.

507
00:39:25,570 --> 00:39:29,869
Find the red strand within tube one. Later we will select it

508
00:39:29,869 --> 00:39:34,526
by its actual inventory identity, not by typing a free text color

509
00:39:34,526 --> 00:39:35,458
into a route.

510
00:39:36,570 --> 00:39:42,381
The fiber definition view is a pre allocation layout. Existing cassette allocations

511
00:39:42,381 --> 00:39:47,282
and live states are separate records. We will keep the generated fiber

512
00:39:47,282 --> 00:39:48,542
colors and finish.

513
00:39:49,650 --> 00:39:53,969
The saved cable appears in the head end. Creating capacity did not

514
00:39:53,969 --> 00:39:58,025
create a work order, and it did not make every fiber connected

515
00:39:58,025 --> 00:39:58,549
or live.

516
00:40:02,650 --> 00:40:08,093
An ODF has its own identity, location and capacity. We will create

517
00:40:08,093 --> 00:40:13,700
Academy ODF A as one endpoint of the training connection. The second

518
00:40:13,700 --> 00:40:16,504
endpoint must be a separate asset.

519
00:40:17,610 --> 00:40:23,294
Open the new ODF form. Manual specifications are useful for a unique

520
00:40:23,294 --> 00:40:29,061
asset; a saved standard can populate repeated equipment consistently.

521
00:40:30,170 --> 00:40:36,160
Enter the unique ODF code. This identifies the frame independently of the

522
00:40:36,160 --> 00:40:37,718
head end and cable.

523
00:40:38,819 --> 00:40:42,753
Enter a clear display name. The code and name will help us

524
00:40:42,753 --> 00:40:45,060
select the correct endpoint later.

525
00:40:46,179 --> 00:40:50,764
The endpoint location can differ from the other end of the cable.

526
00:40:50,764 --> 00:40:53,515
Record the actual installation address.

527
00:40:54,619 --> 00:40:59,307
Keep related location names consistent for searching and reporting.

528
00:41:00,419 --> 00:41:05,469
Latitude describes this endpoint. Our example uses fictional training coordinates.

529
00:41:06,579 --> 00:41:11,353
Longitude completes the coordinate pair. A coordinate is not proof of a

530
00:41:11,353 --> 00:41:12,362
surveyed route.

531
00:41:13,463 --> 00:41:17,875
Frame type describes the physical form of this ODF.

532
00:41:18,983 --> 00:41:25,323
Mounting describes how the frame is installed. Keep equipment specifications consistent with

533
00:41:25,323 --> 00:41:26,425
the actual unit.

534
00:41:27,543 --> 00:41:32,341
The connector type is a physical specification. It does not establish optical

535
00:41:32,341 --> 00:41:33,836
compatibility by itself.

536
00:41:34,943 --> 00:41:39,503
We will provide twelve ports. This ODF capacity is independent of the

537
00:41:39,503 --> 00:41:42,279
cable’s two hundred eighty eight fibers.

538
00:41:43,383 --> 00:41:49,167
Splice capacity describes the ODF specification. Only the selected strand will be

539
00:41:49,167 --> 00:41:51,452
terminated in our demonstration.

540
00:41:52,553 --> 00:41:58,143
Fiber mode is a specification, separate from whether a strand is free,

541
00:41:58,143 --> 00:41:59,581
connected or live.

542
00:42:00,681 --> 00:42:06,060
Asset status offers Active, Planned, Reserve and Out of service. We will

543
00:42:06,060 --> 00:42:12,185
keep the fictional asset Active. Status alone does not apply physical connections.

544
00:42:13,286 --> 00:42:18,059
Save the asset and inspect its digital twin. It has an identity,

545
00:42:18,059 --> 00:42:23,280
but positions still need to be built before selecting a physical port.

546
00:42:24,380 --> 00:42:30,564
Build positions creates the configured capacity. The positions begin Free and Not

547
00:42:30,564 --> 00:42:34,533
live. Creating positions does not connect the cable.

548
00:42:35,634 --> 00:42:40,648
Select the first position to inspect its action, status, live state and

549
00:42:40,648 --> 00:42:46,085
cable selectors. We will leave it unconnected until both endpoints are ready.

550
00:42:50,194 --> 00:42:55,453
An ODF has its own identity, location and capacity. We will create

551
00:42:55,453 --> 00:43:00,871
Academy ODF B as one endpoint of the training connection. The second

552
00:43:00,871 --> 00:43:03,581
endpoint must be a separate asset.

553
00:43:04,681 --> 00:43:10,365
Open the new ODF form. Manual specifications are useful for a unique

554
00:43:10,365 --> 00:43:16,132
asset; a saved standard can populate repeated equipment consistently.

555
00:43:17,241 --> 00:43:23,231
Enter the unique ODF code. This identifies the frame independently of the

556
00:43:23,231 --> 00:43:24,789
head end and cable.

557
00:43:25,890 --> 00:43:29,824
Enter a clear display name. The code and name will help us

558
00:43:29,824 --> 00:43:32,131
select the correct endpoint later.

559
00:43:33,250 --> 00:43:37,835
The endpoint location can differ from the other end of the cable.

560
00:43:37,835 --> 00:43:40,586
Record the actual installation address.

561
00:43:41,690 --> 00:43:46,378
Keep related location names consistent for searching and reporting.

562
00:43:47,490 --> 00:43:52,540
Latitude describes this endpoint. Our example uses fictional training coordinates.

563
00:43:53,650 --> 00:43:58,424
Longitude completes the coordinate pair. A coordinate is not proof of a

564
00:43:58,424 --> 00:43:59,433
surveyed route.

565
00:44:00,534 --> 00:44:04,946
Frame type describes the physical form of this ODF.

566
00:44:06,054 --> 00:44:12,394
Mounting describes how the frame is installed. Keep equipment specifications consistent with

567
00:44:12,394 --> 00:44:13,496
the actual unit.

568
00:44:14,614 --> 00:44:19,412
The connector type is a physical specification. It does not establish optical

569
00:44:19,412 --> 00:44:20,907
compatibility by itself.

570
00:44:22,014 --> 00:44:26,574
We will provide twelve ports. This ODF capacity is independent of the

571
00:44:26,574 --> 00:44:29,350
cable’s two hundred eighty eight fibers.

572
00:44:30,454 --> 00:44:36,238
Splice capacity describes the ODF specification. Only the selected strand will be

573
00:44:36,238 --> 00:44:38,523
terminated in our demonstration.

574
00:44:39,624 --> 00:44:45,214
Fiber mode is a specification, separate from whether a strand is free,

575
00:44:45,214 --> 00:44:46,652
connected or live.

576
00:44:47,752 --> 00:44:53,131
Asset status offers Active, Planned, Reserve and Out of service. We will

577
00:44:53,131 --> 00:44:59,256
keep the fictional asset Active. Status alone does not apply physical connections.

578
00:45:00,357 --> 00:45:05,130
Save the asset and inspect its digital twin. It has an identity,

579
00:45:05,130 --> 00:45:10,351
but positions still need to be built before selecting a physical port.

580
00:45:11,451 --> 00:45:17,635
Build positions creates the configured capacity. The positions begin Free and Not

581
00:45:17,635 --> 00:45:21,604
live. Creating positions does not connect the cable.

582
00:45:22,705 --> 00:45:27,719
Select the first position to inspect its action, status, live state and

583
00:45:27,719 --> 00:45:33,156
cable selectors. We will leave it unconnected until both endpoints are ready.

584
00:45:37,265 --> 00:45:40,639
This is manhole 1 of four between our ODF endpoints. A manhole

585
00:45:40,639 --> 00:45:44,829
record describes a location and its infrastructure. It is not automatically a

586
00:45:44,829 --> 00:45:45,537
fiber splice.

587
00:45:46,637 --> 00:45:50,571
Enter a unique manhole code. We will keep the route sequence easy

588
00:45:50,571 --> 00:45:52,931
to follow with numbered training codes.

589
00:45:54,037 --> 00:45:59,034
Add a readable name. The code remains the stable identifier.

590
00:46:00,134 --> 00:46:06,030
Type or standard describes the chamber. A reusable standard can reduce repeated

591
00:46:06,030 --> 00:46:07,523
specification entry.

592
00:46:08,624 --> 00:46:13,623
A full address is required before connectivity search is enabled. Enter the

593
00:46:13,623 --> 00:46:15,289
location of this chamber.

594
00:46:16,390 --> 00:46:21,019
Enter the location postcode. It can differ from the company and customer

595
00:46:21,019 --> 00:46:21,854
headquarters.

596
00:46:22,955 --> 00:46:28,526
Use the same city convention as the related network assets.

597
00:46:29,635 --> 00:46:35,644
Enter the latitude from the location source. The example coordinates are training

598
00:46:35,644 --> 00:46:36,460
references.

599
00:46:37,561 --> 00:46:44,009
Enter the longitude. Once the address and coordinates are present, connectivity choices

600
00:46:44,009 --> 00:46:45,269
become available.

601
00:46:46,369 --> 00:46:53,848
Connectivity offers Standalone, Continue from another manhole, Between manholes, Multiple connections and

602
00:46:53,848 --> 00:47:00,329
Planned. These describe infrastructure relationships; they do not splice a selected strand.

603
00:47:01,449 --> 00:47:06,291
We will start with a standalone chamber. The route lesson will explicitly

604
00:47:06,291 --> 00:47:11,597
connect the intended assets rather than assuming a connection from similar names

605
00:47:11,597 --> 00:47:12,592
or coordinates.

606
00:47:13,692 --> 00:47:19,181
Save the manhole and inspect its workspace. Confirm the code and location

607
00:47:19,181 --> 00:47:21,964
before using this chamber in a route.

608
00:47:26,064 --> 00:47:30,483
This is manhole 2 of four between our ODF endpoints. A manhole

609
00:47:30,483 --> 00:47:35,971
record describes a location and its infrastructure. It is not automatically a

610
00:47:35,971 --> 00:47:36,898
fiber splice.

611
00:47:37,998 --> 00:47:41,932
Enter a unique manhole code. We will keep the route sequence easy

612
00:47:41,932 --> 00:47:44,292
to follow with numbered training codes.

613
00:47:45,398 --> 00:47:50,395
Add a readable name. The code remains the stable identifier.

614
00:47:51,495 --> 00:47:57,391
Type or standard describes the chamber. A reusable standard can reduce repeated

615
00:47:57,391 --> 00:47:58,884
specification entry.

616
00:47:59,985 --> 00:48:04,984
A full address is required before connectivity search is enabled. Enter the

617
00:48:04,984 --> 00:48:06,650
location of this chamber.

618
00:48:07,751 --> 00:48:12,380
Enter the location postcode. It can differ from the company and customer

619
00:48:12,380 --> 00:48:13,215
headquarters.

620
00:48:14,316 --> 00:48:19,887
Use the same city convention as the related network assets.

621
00:48:20,996 --> 00:48:27,005
Enter the latitude from the location source. The example coordinates are training

622
00:48:27,005 --> 00:48:27,821
references.

623
00:48:28,922 --> 00:48:35,370
Enter the longitude. Once the address and coordinates are present, connectivity choices

624
00:48:35,370 --> 00:48:36,630
become available.

625
00:48:37,730 --> 00:48:45,209
Connectivity offers Standalone, Continue from another manhole, Between manholes, Multiple connections and

626
00:48:45,209 --> 00:48:51,690
Planned. These describe infrastructure relationships; they do not splice a selected strand.

627
00:48:52,810 --> 00:48:57,652
We will start with a standalone chamber. The route lesson will explicitly

628
00:48:57,652 --> 00:49:02,958
connect the intended assets rather than assuming a connection from similar names

629
00:49:02,958 --> 00:49:03,953
or coordinates.

630
00:49:05,053 --> 00:49:10,542
Save the manhole and inspect its workspace. Confirm the code and location

631
00:49:10,542 --> 00:49:13,325
before using this chamber in a route.

632
00:49:17,425 --> 00:49:21,688
This is manhole 3 of four between our ODF endpoints. A manhole

633
00:49:21,688 --> 00:49:26,983
record describes a location and its infrastructure. It is not automatically a

634
00:49:26,983 --> 00:49:27,876
fiber splice.

635
00:49:28,985 --> 00:49:32,919
Enter a unique manhole code. We will keep the route sequence easy

636
00:49:32,919 --> 00:49:35,279
to follow with numbered training codes.

637
00:49:36,385 --> 00:49:41,382
Add a readable name. The code remains the stable identifier.

638
00:49:42,482 --> 00:49:48,378
Type or standard describes the chamber. A reusable standard can reduce repeated

639
00:49:48,378 --> 00:49:49,871
specification entry.

640
00:49:50,972 --> 00:49:55,971
A full address is required before connectivity search is enabled. Enter the

641
00:49:55,971 --> 00:49:57,637
location of this chamber.

642
00:49:58,738 --> 00:50:03,367
Enter the location postcode. It can differ from the company and customer

643
00:50:03,367 --> 00:50:04,202
headquarters.

644
00:50:05,303 --> 00:50:10,874
Use the same city convention as the related network assets.

645
00:50:11,983 --> 00:50:17,992
Enter the latitude from the location source. The example coordinates are training

646
00:50:17,992 --> 00:50:18,808
references.

647
00:50:19,909 --> 00:50:26,357
Enter the longitude. Once the address and coordinates are present, connectivity choices

648
00:50:26,357 --> 00:50:27,617
become available.

649
00:50:28,717 --> 00:50:36,196
Connectivity offers Standalone, Continue from another manhole, Between manholes, Multiple connections and

650
00:50:36,196 --> 00:50:42,677
Planned. These describe infrastructure relationships; they do not splice a selected strand.

651
00:50:43,797 --> 00:50:48,639
We will start with a standalone chamber. The route lesson will explicitly

652
00:50:48,639 --> 00:50:53,945
connect the intended assets rather than assuming a connection from similar names

653
00:50:53,945 --> 00:50:54,940
or coordinates.

654
00:50:56,040 --> 00:51:01,529
Save the manhole and inspect its workspace. Confirm the code and location

655
00:51:01,529 --> 00:51:04,312
before using this chamber in a route.

656
00:51:08,412 --> 00:51:12,957
This is manhole 4 of four between our ODF endpoints. A manhole

657
00:51:12,957 --> 00:51:18,602
record describes a location and its infrastructure. It is not automatically a

658
00:51:18,602 --> 00:51:19,555
fiber splice.

659
00:51:20,655 --> 00:51:24,589
Enter a unique manhole code. We will keep the route sequence easy

660
00:51:24,589 --> 00:51:26,949
to follow with numbered training codes.

661
00:51:28,055 --> 00:51:33,052
Add a readable name. The code remains the stable identifier.

662
00:51:34,152 --> 00:51:40,048
Type or standard describes the chamber. A reusable standard can reduce repeated

663
00:51:40,048 --> 00:51:41,541
specification entry.

664
00:51:42,642 --> 00:51:47,641
A full address is required before connectivity search is enabled. Enter the

665
00:51:47,641 --> 00:51:49,307
location of this chamber.

666
00:51:50,408 --> 00:51:55,037
Enter the location postcode. It can differ from the company and customer

667
00:51:55,037 --> 00:51:55,872
headquarters.

668
00:51:56,973 --> 00:52:02,544
Use the same city convention as the related network assets.

669
00:52:03,653 --> 00:52:09,662
Enter the latitude from the location source. The example coordinates are training

670
00:52:09,662 --> 00:52:10,478
references.

671
00:52:11,579 --> 00:52:18,027
Enter the longitude. Once the address and coordinates are present, connectivity choices

672
00:52:18,027 --> 00:52:19,287
become available.

673
00:52:20,387 --> 00:52:27,866
Connectivity offers Standalone, Continue from another manhole, Between manholes, Multiple connections and

674
00:52:27,866 --> 00:52:34,347
Planned. These describe infrastructure relationships; they do not splice a selected strand.

675
00:52:35,467 --> 00:52:40,309
We will start with a standalone chamber. The route lesson will explicitly

676
00:52:40,309 --> 00:52:45,615
connect the intended assets rather than assuming a connection from similar names

677
00:52:45,615 --> 00:52:46,610
or coordinates.

678
00:52:47,710 --> 00:52:53,199
Save the manhole and inspect its workspace. Confirm the code and location

679
00:52:53,199 --> 00:52:55,982
before using this chamber in a route.

680
00:53:00,082 --> 00:53:04,299
A closure contains cable entries and splice positions. We will place a

681
00:53:04,299 --> 00:53:08,637
training closure in the second manhole. A chamber and the closure inside

682
00:53:08,637 --> 00:53:10,023
it are separate assets.

683
00:53:11,123 --> 00:53:16,290
Placement offers an existing manhole, a new manhole created with the closure,

684
00:53:16,290 --> 00:53:21,189
or Standby for later placement. We already created the chamber, so choose

685
00:53:21,189 --> 00:53:22,532
the existing option.

686
00:53:23,643 --> 00:53:30,288
Select Academy Manhole two. Verify the code and address rather than selecting

687
00:53:30,288 --> 00:53:32,446
the first similar record.

688
00:53:33,563 --> 00:53:38,860
Enter a stable closure code. The closure identity stays distinct from the

689
00:53:38,860 --> 00:53:39,804
chamber code.

690
00:53:40,923 --> 00:53:45,657
A saved standard can fill repeated specifications. We will keep Manual and

691
00:53:45,657 --> 00:53:48,216
describe a fictional training enclosure.

692
00:53:49,323 --> 00:53:55,588
Manufacturer and model describe equipment. This example does not claim compatibility with

693
00:53:55,588 --> 00:53:57,137
a real vendor product.

694
00:53:58,243 --> 00:54:03,735
Use the actual model for a real enclosure. Our training model is

695
00:54:03,735 --> 00:54:05,536
explicitly fictional.

696
00:54:06,643 --> 00:54:11,160
Four physical ports are enough for this exercise. A physical port count

697
00:54:11,160 --> 00:54:14,659
is different from a cassette’s fiber splice capacity.

698
00:54:15,763 --> 00:54:19,762
An oval window cut pairs ports one and two for a continuing

699
00:54:19,762 --> 00:54:24,234
cable. We will choose No for this simpler enclosure, so the lesson

700
00:54:24,234 --> 00:54:27,894
does not imply a window cut that was never documented.

701
00:54:29,003 --> 00:54:33,027
Phases can be A or A and B. Select A for this

702
00:54:33,027 --> 00:54:40,270
exercise. Separate phases are useful when the physical enclosure and work process

703
00:54:40,270 --> 00:54:41,432
require them.

704
00:54:42,533 --> 00:54:47,445
Create two phase A cassettes. This supplies splice capacity, but it does

705
00:54:47,445 --> 00:54:49,082
not connect any strands.

706
00:54:50,182 --> 00:54:55,689
Leave phase B cassette count at zero and save the closure. Inspect

707
00:54:55,689 --> 00:55:00,027
the resulting ports and cassettes in Closure Studio.

708
00:55:01,142 --> 00:55:06,869
The studio separates cable entries, cassettes and splice work. Blue planned work

709
00:55:06,869 --> 00:55:10,520
is not the same as confirmed as built connectivity.

710
00:55:14,622 --> 00:55:19,847
The head end cable lesson showed the rack cable workflow. This closure

711
00:55:19,847 --> 00:55:25,371
workflow creates the optical cable inventory used by the ODF selectors. We

712
00:55:25,371 --> 00:55:29,252
will give this separate training cable its own code.

713
00:55:30,353 --> 00:55:34,910
Mode offers an existing cable asset or a new cable. Choose Create

714
00:55:34,910 --> 00:55:39,677
new cable so the application generates its tube and fiber inventory.

715
00:55:40,793 --> 00:55:45,952
This optical cable code differs from the head end example. Clear identifiers

716
00:55:45,952 --> 00:55:50,840
prevent two separate records from being mistaken for one physical cable.

717
00:55:51,953 --> 00:55:56,654
Record the cable type. It describes the cable’s intended role, not the

718
00:55:56,654 --> 00:55:58,874
connection status of every strand.

719
00:55:59,993 --> 00:56:05,982
Enter twenty four tubes. The cable will contain a full inventory, including

720
00:56:05,982 --> 00:56:07,180
unused strands.

721
00:56:08,281 --> 00:56:13,373
Select twelve fibers per tube. Twenty four times twelve gives two hundred

722
00:56:13,373 --> 00:56:15,256
eighty eight fiber records.

723
00:56:16,361 --> 00:56:21,900
Only available closure ports are offered. Choose port one for this cable

724
00:56:21,900 --> 00:56:27,516
entry. A closure cable port and an ODF termination position are different

725
00:56:27,516 --> 00:56:28,439
identifiers.

726
00:56:29,539 --> 00:56:34,551
Enter a clear direction description. We will select the exact ODF endpoints

727
00:56:34,551 --> 00:56:36,088
in Route Builder later.

728
00:56:37,188 --> 00:56:41,513
Add the cable and inspect its planned work marker. The cable exists

729
00:56:41,513 --> 00:56:45,257
now, but this action has not confirmed field installation.

730
00:56:46,358 --> 00:56:50,755
Confirm work done is a significant action. Use it only after actual

731
00:56:50,755 --> 00:56:55,414
field work and verification. In this isolated course, we will confirm a

732
00:56:55,414 --> 00:57:01,255
fictional training installation; no real optical measurement or physical work is claimed.

733
00:57:02,358 --> 00:57:07,804
Select Confirm work done and read the confirmation. This demonstration has no

734
00:57:07,804 --> 00:57:12,685
active field job. When a closure belongs to an active job, completion

735
00:57:12,685 --> 00:57:15,585
must follow the assigned review workflow.

736
00:57:16,686 --> 00:57:21,522
The planned marker is cleared after confirmation. The cable is now available

737
00:57:21,522 --> 00:57:27,058
for active optical endpoint selection. Its unused fibers remain available; confirming a

738
00:57:27,058 --> 00:57:29,604
cable entry does not splice all of them.

739
00:57:33,704 --> 00:57:39,305
Route Builder selects exact assets and endpoints. We will record a fictional

740
00:57:39,305 --> 00:57:44,169
verified connection from ODF A through four manholes to ODF B. New

741
00:57:44,169 --> 00:57:49,033
field work should instead be saved as a design for later execution

742
00:57:49,033 --> 00:57:49,844
and review.

743
00:57:50,944 --> 00:57:54,964
Give the route a meaningful name. A route name does not create

744
00:57:54,964 --> 00:57:58,854
missing assets or substitute for selecting the actual fiber.

745
00:57:59,954 --> 00:58:04,932
Choose the training city to narrow the asset catalog. This filter affects

746
00:58:04,932 --> 00:58:07,864
selection, not ownership or company access.

747
00:58:08,964 --> 00:58:14,948
Add ODF A as an endpoint. Select the ODF category, then the

748
00:58:14,948 --> 00:58:16,672
exact asset code.

749
00:58:17,772 --> 00:58:23,691
Select the active optical cable created in Closure Studio. The cable dropdown

750
00:58:23,691 --> 00:58:27,458
is an inventory selection, not a free text label.

751
00:58:28,572 --> 00:58:32,953
Choose tube one, which is red in this cable’s color convention. Tube

752
00:58:32,953 --> 00:58:36,897
number and color are both visible so you can verify the choice.

753
00:58:38,012 --> 00:58:43,017
Choose the red fiber inside tube one. The remaining fibers are not

754
00:58:43,017 --> 00:58:44,837
selected for this route.

755
00:58:45,938 --> 00:58:51,024
Choose rack one, panel one, position one. Then add the ODF point.

756
00:58:51,024 --> 00:58:56,736
This records the exact cable, tube, fiber and termination position in the

757
00:58:56,736 --> 00:58:57,910
route proposal.

758
00:58:59,018 --> 00:59:03,685
Add manhole 1 as the next route point. The sequence represents the

759
00:59:03,685 --> 00:59:06,513
intended path between the two endpoints.

760
00:59:07,618 --> 00:59:13,423
Select this manhole’s physical endpoint. Passing through a chamber does not automatically

761
00:59:13,423 --> 00:59:17,633
create a splice. We are keeping the same optical strand along this

762
00:59:17,633 --> 00:59:18,016
route.

763
00:59:19,117 --> 00:59:23,850
Add manhole 2 as the next route point. The sequence represents the

764
00:59:23,850 --> 00:59:26,719
intended path between the two endpoints.

765
00:59:27,837 --> 00:59:33,642
Select this manhole’s physical endpoint. Passing through a chamber does not automatically

766
00:59:33,642 --> 00:59:37,852
create a splice. We are keeping the same optical strand along this

767
00:59:37,852 --> 00:59:38,235
route.

768
00:59:39,336 --> 00:59:44,168
Add manhole 3 as the next route point. The sequence represents the

769
00:59:44,168 --> 00:59:47,097
intended path between the two endpoints.

770
00:59:48,216 --> 00:59:54,021
Select this manhole’s physical endpoint. Passing through a chamber does not automatically

771
00:59:54,021 --> 00:59:58,231
create a splice. We are keeping the same optical strand along this

772
00:59:58,231 --> 00:59:58,614
route.

773
00:59:59,715 --> 01:00:04,157
Add manhole 4 as the next route point. The sequence represents the

774
01:00:04,157 --> 01:00:06,849
intended path between the two endpoints.

775
01:00:07,955 --> 01:00:13,760
Select this manhole’s physical endpoint. Passing through a chamber does not automatically

776
01:00:13,760 --> 01:00:17,970
create a splice. We are keeping the same optical strand along this

777
01:00:17,970 --> 01:00:18,353
route.

778
01:00:19,454 --> 01:00:25,438
Add ODF B as an endpoint. Select the ODF category, then the

779
01:00:25,438 --> 01:00:27,162
exact asset code.

780
01:00:28,262 --> 01:00:34,181
Select the active optical cable created in Closure Studio. The cable dropdown

781
01:00:34,181 --> 01:00:37,948
is an inventory selection, not a free text label.

782
01:00:39,062 --> 01:00:43,443
Choose tube one, which is red in this cable’s color convention. Tube

783
01:00:43,443 --> 01:00:47,387
number and color are both visible so you can verify the choice.

784
01:00:48,502 --> 01:00:53,507
Choose the red fiber inside tube one. The remaining fibers are not

785
01:00:53,507 --> 01:00:55,327
selected for this route.

786
01:00:56,428 --> 01:01:01,514
Choose rack one, panel one, position one. Then add the ODF point.

787
01:01:01,514 --> 01:01:07,226
This records the exact cable, tube, fiber and termination position in the

788
01:01:07,226 --> 01:01:08,400
route proposal.

789
01:01:09,508 --> 01:01:14,440
Review all six points in order. Remove or move controls allow corrections

790
01:01:14,440 --> 01:01:19,304
before building. A similar asset name or nearby coordinate is not enough

791
01:01:19,304 --> 01:01:21,533
to identify the correct endpoint.

792
01:01:22,633 --> 01:01:29,340
Preview validates the selected endpoint transport and displays warnings. Resolve actual warnings

793
01:01:29,340 --> 01:01:31,436
before recording connectivity.

794
01:01:32,553 --> 01:01:38,581
Save design is appropriate for proposed new work. Record verified existing connectivity

795
01:01:38,581 --> 01:01:44,263
applies existing connections immediately. We will use the verified option only for

796
01:01:44,263 --> 01:01:47,450
this explicitly fictional training connection.

797
01:01:48,553 --> 01:01:54,367
Enter the verification context. In production this must describe genuine supporting evidence,

798
01:01:54,367 --> 01:01:56,367
not a guess or an AI suggestion.

799
01:02:11,913 --> 01:02:17,220
Confirm the verified connectivity and wait for the saved route record. This

800
01:02:17,220 --> 01:02:20,546
action is independent of creating a work order.

801
01:02:21,646 --> 01:02:27,548
The trace shows six points and five connections. Read the transport at

802
01:02:27,548 --> 01:02:33,280
both ODF endpoints: the same cable, tube one, red fiber and position

803
01:02:33,280 --> 01:02:33,618
one.

804
01:02:34,726 --> 01:02:40,503
Open Diagrams and export to inspect the recorded route. A connection diagram

805
01:02:40,503 --> 01:02:46,737
documents selected relationships; it is not proof of an accurately surveyed street

806
01:02:46,737 --> 01:02:47,421
geometry.

807
01:02:51,526 --> 01:02:56,011
Reopen ODF A after saving the route. Its recorded state now shows

808
01:02:56,011 --> 01:03:00,566
the connection. This is a verification of saved data, not just the

809
01:03:00,566 --> 01:03:02,084
earlier route preview.

810
01:03:03,184 --> 01:03:08,183
Select position one and read the connected cable, tube and fiber. Live

811
01:03:08,183 --> 01:03:13,254
state is separate: a recorded connection does not prove that an optical

812
01:03:13,254 --> 01:03:14,539
signal is present.

813
01:03:15,640 --> 01:03:20,584
Open ODF B and inspect the same position. Both endpoint records should

814
01:03:20,584 --> 01:03:23,550
refer to the same selected optical strand.

815
01:03:24,650 --> 01:03:30,306
Now open the cable’s digital twin. The full twenty four tube inventory

816
01:03:30,306 --> 01:03:33,762
remains present after connecting one strand.

817
01:03:34,862 --> 01:03:39,938
Open the first tube’s fibers. The red fiber now shows Connected, matching

818
01:03:39,938 --> 01:03:44,541
the saved ODF endpoints. The other eleven fibers in this tube remain

819
01:03:44,541 --> 01:03:48,873
Free. A connection records how the network is wired; it does not

820
01:03:48,873 --> 01:03:52,257
mean that the fiber carries a live optical signal.

821
01:03:53,358 --> 01:03:57,966
The cable still contains all two hundred eighty eight fibers across twenty

822
01:03:57,966 --> 01:04:02,511
four tubes. Exactly one strand is connected, and two hundred eighty seven

823
01:04:02,511 --> 01:04:07,430
remain Free. Planned work is separate from a confirmed connection: always check

824
01:04:07,430 --> 01:04:10,232
reservations before allocating a free strand.

825
01:04:11,333 --> 01:04:16,170
Return to the route diagrams. Inspect the first ODF table and its

826
01:04:16,170 --> 01:04:18,775
selected position before exporting.

827
01:04:19,893 --> 01:04:25,080
Download diagrams PDF produces a readable record of the selected route. We

828
01:04:25,080 --> 01:04:28,165
will save the actual generated file locally.

829
01:04:29,265 --> 01:04:35,090
Download diagrams Excel creates worksheets for the route stops. Keep the exported

830
01:04:35,090 --> 01:04:39,621
file together with the route identity and its revision context.

831
01:04:43,721 --> 01:04:48,483
A splice joins two physical fibers inside a closure. We will prepare

832
01:04:48,483 --> 01:04:53,875
a separate blue fiber example, leaving the red endpoint route unchanged. This

833
01:04:53,875 --> 01:04:55,905
example remains planned work.

834
01:04:57,006 --> 01:05:01,216
Add a second cable to the closure. A splice needs two distinct

835
01:05:01,216 --> 01:05:05,426
physical fiber identities, not the same strand selected twice.

836
01:05:09,301 --> 01:05:12,681
Use a new cable code for this short branch example.

837
01:05:20,461 --> 01:05:25,532
Choose one tube with twelve fibers. The smaller capacity makes the two

838
01:05:25,532 --> 01:05:27,126
sides easy to compare.

839
01:05:30,901 --> 01:05:34,864
Choose free port two and add the cable. It remains marked as

840
01:05:34,864 --> 01:05:38,035
planned until the appropriate work confirmation.

841
01:05:39,141 --> 01:05:46,746
Open New Splice. The selectors use actual cables, tubes and fibers linked

842
01:05:46,746 --> 01:05:48,412
to this closure.

843
01:05:52,513 --> 01:05:56,606
Open New Splice to prepare a change using the two cables now

844
01:05:56,606 --> 01:06:01,926
attached to the closure. The current confirmed state remains separate from the

845
01:06:01,926 --> 01:06:03,017
proposed change.

846
01:06:04,118 --> 01:06:08,832
Select the optical cable on the left, then its first tube. Each

847
01:06:08,832 --> 01:06:11,826
selector narrows the physical inventory.

848
01:06:12,926 --> 01:06:16,619
Select the blue fiber on the left. We are keeping the red

849
01:06:16,619 --> 01:06:19,794
route strand out of this separate splice example.

850
01:06:20,895 --> 01:06:25,974
To test validation, temporarily select the identical cable, tube and blue strand

851
01:06:25,974 --> 01:06:29,847
on the right. A physical fiber must not be spliced to itself.

852
01:06:30,948 --> 01:06:35,975
Validate the selection. The same fiber error should appear and the plan

853
01:06:35,975 --> 01:06:37,390
must remain unsaved.

854
01:06:38,508 --> 01:06:42,984
Correct the right side to the separate branch cable, then select its

855
01:06:42,984 --> 01:06:44,696
first tube and blue fiber.

856
01:06:45,908 --> 01:06:51,336
Target location includes cassettes and dark rooms. A new paired splice belongs

857
01:06:51,336 --> 01:06:57,112
in an available cassette position. Dark room moves have different requirements when

858
01:06:57,112 --> 01:06:58,922
editing an existing fiber.

859
01:07:00,028 --> 01:07:05,858
Status distinguishes spliced, pass through, loose, free and reserve. Free and reserve

860
01:07:05,858 --> 01:07:10,316
describe an unpaired fiber and require one side to be cleared. We

861
01:07:10,316 --> 01:07:12,510
will keep Spliced for this pair.

862
01:07:13,628 --> 01:07:18,401
Live state is independent of splice status. Keep both sides Not live

863
01:07:18,401 --> 01:07:22,261
unless actual verified evidence supports another state.

864
01:07:23,361 --> 01:07:28,555
Value or clamp and customer fields can add context to this splice.

865
01:07:28,555 --> 01:07:31,781
We will identify this as a training plan.

866
01:07:32,882 --> 01:07:38,119
Validate and plan the corrected splice. The saved result should remain planned

867
01:07:38,119 --> 01:07:40,537
until the proper field confirmation.

868
01:07:41,642 --> 01:07:46,769
Inspect the planned work in the cassette overview. Do not use Confirm

869
01:07:46,769 --> 01:07:51,822
work done merely to remove a blue marker. This plan is intentionally

870
01:07:51,822 --> 01:07:54,869
outside the documentation inspection job.

871
01:07:58,970 --> 01:08:04,249
A work order organizes the requested work, team, location, evidence and review.

872
01:08:04,249 --> 01:08:09,594
We will create an inspection of our fictional network documentation. Creating an

873
01:08:09,594 --> 01:08:13,069
inspection does not itself change the optical route.

874
01:08:14,170 --> 01:08:21,521
Job type offers Repair, Maintenance, Emergency, Installation, Inspection, Survey and New Splice.

875
01:08:21,521 --> 01:08:27,034
Choose the category matching the actual work. We will select Inspection.

876
01:08:28,135 --> 01:08:34,085
Priority describes urgency separately from the job type. Review Low through Critical.

877
01:08:34,085 --> 01:08:38,076
We will keep Normal for this planned training inspection.

878
01:08:39,176 --> 01:08:44,896
Project number groups work under a recognizable project reference. We will use

879
01:08:44,896 --> 01:08:46,363
Academy Project one.

880
01:08:47,464 --> 01:08:52,796
The job reference distinguishes this assignment. Use a meaningful reference rather than

881
01:08:52,796 --> 01:08:56,044
putting the full work instructions in the identifier.

882
01:08:57,144 --> 01:09:01,977
Due date and due time describe the requested deadline. They do not

883
01:09:01,977 --> 01:09:07,616
start the personal work timer. For this unscheduled training exercise we will

884
01:09:07,616 --> 01:09:08,861
leave them empty.

885
01:09:09,961 --> 01:09:14,144
Open Customer and Site. We will select the saved customer instead of

886
01:09:14,144 --> 01:09:16,297
retyping a slightly different name.

887
01:09:17,401 --> 01:09:22,659
Choose Academy Network Operator from the saved customer selector. The customer and

888
01:09:22,659 --> 01:09:25,673
its related work sites should now be available.

889
01:09:26,773 --> 01:09:31,769
Select the saved Academy Fiber Training Site. This uses the field location,

890
01:09:31,769 --> 01:09:35,300
not the customer’s headquarters or billing address.

891
01:09:36,413 --> 01:09:43,023
Select Casey as the customer contact. Review the populated information before continuing.

892
01:09:43,023 --> 01:09:46,811
A saved contact helps avoid repeated typing errors.

893
01:09:47,912 --> 01:09:51,941
The site address and access instructions are shown in the work form.

894
01:09:51,941 --> 01:09:56,385
We will make the training restriction explicit for the assigned technician.

895
01:10:00,312 --> 01:10:05,531
Open Assignment. The employee roster and linked user accounts prepared earlier now

896
01:10:05,531 --> 01:10:09,477
allow us to choose real named people in this training company.

897
01:10:10,592 --> 01:10:16,399
Select Jordan Lee as the responsible supervisor. The primary supervisor owns the

898
01:10:16,399 --> 01:10:19,448
review responsibility for this assignment.

899
01:10:20,552 --> 01:10:26,117
Select Sam Taylor as technician. Additional technicians can be selected when the

900
01:10:26,117 --> 01:10:30,291
work needs a crew. The first selected technician is primary.

901
01:10:31,392 --> 01:10:36,498
Open Network Work Package. It supports multiple asset types. We will attach

902
01:10:36,498 --> 01:10:40,924
the exact ODF after creating the order, so this chapter can focus

903
01:10:40,924 --> 01:10:42,694
on the preparation fields.

904
01:10:43,795 --> 01:10:50,053
The network choices include closures, ODFs, hubs, head ends, cabinets, manholes and

905
01:10:50,053 --> 01:10:56,085
cables. Selecting a category is different from linking the exact existing asset.

906
01:10:57,195 --> 01:11:01,935
Files can include diagrams, photos and field documents. The measurement library is

907
01:11:01,935 --> 01:11:06,502
separate. Use genuine instrument results when the job requires OTDR evidence; a

908
01:11:06,502 --> 01:11:08,699
tutorial example is not a measurement.

909
01:11:09,800 --> 01:11:16,355
Open Work Instructions. A clear summary, required action and completion requirements tell

910
01:11:16,355 --> 01:11:18,859
the technician what success means.

911
01:11:19,960 --> 01:11:25,482
The summary explains the objective. It should help the field team understand

912
01:11:25,482 --> 01:11:26,935
why the work exists.

913
01:11:30,019 --> 01:11:35,245
Required action states what must be done. We are inspecting documentation rather

914
01:11:35,245 --> 01:11:37,727
than requesting a live network change.

915
01:11:41,979 --> 01:11:48,351
Work scope defines the boundaries. Explicit boundaries help prevent unintended changes outside

916
01:11:48,351 --> 01:11:49,368
the assignment.

917
01:11:52,939 --> 01:11:58,914
Completion requirements identify the evidence needed for review. A technician should know

918
01:11:58,914 --> 01:12:01,264
these requirements before starting.

919
01:12:07,859 --> 01:12:12,203
Service impact describes the expected effect of the work. In a real

920
01:12:12,203 --> 01:12:15,769
job this should be assessed against the actual network.

921
01:12:16,869 --> 01:12:21,504
Safety notes should be relevant to the actual assignment and company process.

922
01:12:21,504 --> 01:12:25,236
This software tutorial does not replace field safety training.

923
01:12:27,485 --> 01:12:33,643
Dispatch notes highlight coordination information. They supplement the required action rather than

924
01:12:33,643 --> 01:12:34,460
replacing it.

925
01:12:38,299 --> 01:12:44,304
Review the prepared job before creating it. Check type, priority, site, supervisor,

926
01:12:44,304 --> 01:12:47,198
technician and required action together.

927
01:12:48,299 --> 01:12:53,310
Create the job once and wait for its workspace. Creation is separate

928
01:12:53,310 --> 01:12:56,995
from dispatch, execution, submission and approval.

929
01:12:58,099 --> 01:13:02,490
The new work order has its own identity and status. Next we

930
01:13:02,490 --> 01:13:07,477
will attach the exact network record and review dispatch readiness.

931
01:13:11,579 --> 01:13:16,221
The job exists but still needs its exact network context. Open the

932
01:13:16,221 --> 01:13:19,807
Network section to link the ODF to this inspection.

933
01:13:20,908 --> 01:13:25,286
Add an existing ODF. Selecting an asset for a job does not

934
01:13:25,286 --> 01:13:29,136
create a duplicate asset or change its connections.

935
01:13:30,237 --> 01:13:35,415
Choose Academy ODF A by its code. Confirm the record before adding

936
01:13:35,415 --> 01:13:37,062
it to the work order.

937
01:13:38,163 --> 01:13:43,097
Add the selected asset, then finish the picker. The work order now

938
01:13:43,097 --> 01:13:45,191
references the existing ODF.

939
01:13:46,291 --> 01:13:52,203
Open dispatch review. Read the site, assigned team, scope and any blockers

940
01:13:52,203 --> 01:13:54,201
before releasing the job.

941
01:13:55,301 --> 01:14:00,413
Dispatch is a separate deliberate step. Missing assignment or work instructions must

942
01:14:00,413 --> 01:14:04,735
be corrected before proceeding. Our training job has named people and a

943
01:14:04,735 --> 01:14:06,135
clear inspection scope.

944
01:14:07,235 --> 01:14:12,427
Confirm dispatch and wait for the resulting status. Outbound email is captured

945
01:14:12,427 --> 01:14:17,686
locally in this training environment; no real employee receives a notification.

946
01:14:18,795 --> 01:14:22,918
The technician can now open the assignment. Dispatch does not mean work

947
01:14:22,918 --> 01:14:26,867
has started, and a notification is not proof that the recipient read

948
01:14:26,867 --> 01:14:27,854
the instructions.

949
01:14:31,955 --> 01:14:37,568
Planning helps coordinate assigned work and availability. Review the job identity, people

950
01:14:37,568 --> 01:14:41,919
and timing together rather than treating a calendar entry as the full

951
01:14:41,919 --> 01:14:42,991
work instruction.

952
01:14:44,092 --> 01:14:49,137
A due date is a requested deadline. A personal work timer records

953
01:14:49,137 --> 01:14:55,347
an individual interval. Changing a schedule does not automatically start or stop

954
01:14:55,347 --> 01:14:55,968
a timer.

955
01:14:57,069 --> 01:15:01,267
On Call is a separate coverage roster. An employee marked eligible for

956
01:15:01,267 --> 01:15:04,926
On Call still needs the relevant schedule and job assignment.

957
01:15:06,029 --> 01:15:11,201
Check the date and the designated technician or supervisor before using coverage

958
01:15:11,201 --> 01:15:15,726
for an urgent job. A roster should reflect agreed availability, not an

959
01:15:15,726 --> 01:15:18,054
assumption that everyone is working.

960
01:15:19,154 --> 01:15:24,890
Keep the responsible supervisor and actual crew current when plans change. The

961
01:15:24,890 --> 01:15:29,818
job’s recorded scope and evidence requirements continue to apply.

962
01:15:33,918 --> 01:15:38,942
We are now Sam, the assigned Technician. Read the work objective, access

963
01:15:38,942 --> 01:15:43,338
restrictions and completion requirements before recording work.

964
01:15:44,439 --> 01:15:49,386
Open My work time. The personal timer belongs to this account and

965
01:15:49,386 --> 01:15:54,486
this job. It is separate from dispatch or the job execution status.

966
01:15:55,599 --> 01:16:00,867
Enter a meaningful description of the activity. A description helps explain the

967
01:16:00,867 --> 01:16:02,467
recorded interval later.

968
01:16:12,279 --> 01:16:17,682
Start my timer begins the personal interval. Watch the running timer indicator

969
01:16:17,682 --> 01:16:18,721
in the top bar.

970
01:16:20,730 --> 01:16:25,269
Move to another workspace. The timer indicator remains available, so you do

971
01:16:25,269 --> 01:16:29,203
not have to search through every project to find a running clock.

972
01:16:30,304 --> 01:16:34,637
Open the timer indicator. It lists the active project and its work

973
01:16:34,637 --> 01:16:40,612
description. Multiple projects can have independent timers; check which interval you intend

974
01:16:40,612 --> 01:16:41,138
to stop.

975
01:16:42,238 --> 01:16:48,472
Update this interval’s description to reflect what was actually reviewed. Keep descriptions

976
01:16:48,472 --> 01:16:50,148
specific to each project.

977
01:16:52,118 --> 01:16:57,427
Stop the correct personal timer. Stopping time does not submit the job

978
01:16:57,427 --> 01:16:58,943
or approve the work.

979
01:17:00,044 --> 01:17:04,382
Return to the job and open work time again to inspect the

980
01:17:04,382 --> 01:17:10,091
saved interval. Review time records before using them in cost calculations.

981
01:17:11,204 --> 01:17:15,713
The closed interval records a duration and description. If you forgot to

982
01:17:15,713 --> 01:17:20,786
stop a timer, follow your company’s correction process rather than treating the

983
01:17:20,786 --> 01:17:23,229
entire elapsed period as verified work.

984
01:17:27,329 --> 01:17:33,290
To demonstrate independent timers, we will prepare a second fictional project. It

985
01:17:33,290 --> 01:17:36,749
has its own reference and activity description.

986
01:17:38,376 --> 01:17:43,919
Enter a distinct site description for the second project. This keeps it

987
01:17:43,919 --> 01:17:46,339
recognizable in the timer list.

988
01:17:51,096 --> 01:17:55,746
Assign Sam and Jordan again. The people can work across projects while

989
01:17:55,746 --> 01:17:58,071
each job keeps a separate identity.

990
01:17:59,176 --> 01:18:04,396
Describe the limited task: record a training time interval only. We are

991
01:18:04,396 --> 01:18:07,925
not requesting a second physical network change.

992
01:18:21,938 --> 01:18:27,219
Review and create the second job. The timer demonstration uses its separate

993
01:18:27,219 --> 01:18:28,487
project reference.

994
01:18:32,587 --> 01:18:37,145
Sam will start a separate timer on each project. Start the first

995
01:18:37,145 --> 01:18:40,135
project with its own activity description.

996
01:18:44,871 --> 01:18:49,325
Open the second project and start its timer with a different description.

997
01:18:49,325 --> 01:18:53,291
Starting this interval should not silently replace the first one.

998
01:18:58,311 --> 01:19:04,243
Open the persistent timer list. Both running projects should be visible together.

999
01:19:05,351 --> 01:19:10,885
Each project retains its own description. Check the project identity before editing

1000
01:19:10,885 --> 01:19:12,219
or stopping a timer.

1001
01:19:13,320 --> 01:19:18,104
Stop the first listed interval. The other project should remain running.

1002
01:19:19,204 --> 01:19:24,498
Now stop the remaining interval. Neither clock should continue unnoticed after this

1003
01:19:24,498 --> 01:19:25,392
demonstration.

1004
01:19:26,492 --> 01:19:31,511
Multiple timers are a recording capability, not proof of simultaneous billable work.

1005
01:19:31,511 --> 01:19:36,231
Review the recorded intervals and apply your company’s time accounting rules.

1006
01:19:40,332 --> 01:19:45,780
Evidence should match the assignment. This inspection requires a clearly marked training

1007
01:19:45,780 --> 01:19:50,856
checklist. Real photos and instrument measurements must come from the actual field

1008
01:19:50,856 --> 01:19:51,166
work.

1009
01:19:52,266 --> 01:19:58,970
Open Evidence uploads. Use the technician’s evidence controls so the file stays

1010
01:19:58,970 --> 01:20:01,122
linked to this assignment.

1011
01:20:02,226 --> 01:20:07,875
Choose Add files and select the training checklist. A selected filename is

1012
01:20:07,875 --> 01:20:10,699
not yet proof of a successful upload.

1013
01:20:11,800 --> 01:20:16,786
Wait until the saved filename appears. We will also verify that the

1014
01:20:16,786 --> 01:20:21,326
backend file list contains this attachment before continuing.

1015
01:20:22,440 --> 01:20:27,779
The checklist identifies the ODF, cable, tube, fiber and position, and explicitly

1016
01:20:27,779 --> 01:20:31,931
says this is a fictional exercise. It does not claim an optical

1017
01:20:31,931 --> 01:20:35,029
loss measurement or a physical site inspection.

1018
01:20:36,129 --> 01:20:41,524
For a real measurement requirement, attach the actual supported instrument result and

1019
01:20:41,524 --> 01:20:45,269
link it to the correct job and network asset. Do not rename

1020
01:20:45,269 --> 01:20:48,824
an unrelated file to make a requirement appear complete.

1021
01:20:52,929 --> 01:20:58,297
If something differs from the approved instructions, report an issue. Do not

1022
01:20:58,297 --> 01:21:02,817
silently change the network or mark incomplete work as complete.

1023
01:21:03,929 --> 01:21:08,574
The affected task selector can identify a particular task or the whole

1024
01:21:08,574 --> 01:21:13,817
job. We will report a documentation question for the whole training inspection.

1025
01:21:14,929 --> 01:21:20,206
Describe the difference and the decision needed. A precise issue gives the

1026
01:21:20,206 --> 01:21:23,201
supervisor something actionable to review.

1027
01:21:29,049 --> 01:21:33,606
Submit the issue. It remains open until an authorized reviewer records a

1028
01:21:33,606 --> 01:21:35,821
decision, and can block completion.

1029
01:21:39,929 --> 01:21:43,966
The Manager can see the open field issue and the question Sam

1030
01:21:43,966 --> 01:21:48,201
recorded. Review it against the approved scope before answering.

1031
01:21:49,301 --> 01:21:54,357
Record a clear decision. A response can clarify the existing scope; a

1032
01:21:54,357 --> 01:21:58,827
new connection change would require revised engineering work.

1033
01:22:15,941 --> 01:22:20,534
Resolve the issue and verify it is no longer open. The decision

1034
01:22:20,534 --> 01:22:23,596
becomes part of the recorded work context.

1035
01:22:27,701 --> 01:22:34,441
Review the instructions, linked asset, saved evidence and resolved issues. Submission should

1036
01:22:34,441 --> 01:22:37,079
reflect the work actually completed.

1037
01:22:38,181 --> 01:22:43,443
Select Submit for review. The form shows any remaining completion blockers.

1038
01:22:44,544 --> 01:22:50,225
Enter a completion note with the checked identifiers and evidence reference. State

1039
01:22:50,225 --> 01:22:55,352
the limits of the training exercise clearly. Our example names Academy ODF

1040
01:22:55,352 --> 01:22:59,717
A, position one, and the optical cable’s red fiber in tube one.

1041
01:22:59,717 --> 01:23:04,429
It refers to the uploaded checklist and makes clear that we reviewed

1042
01:23:04,429 --> 01:23:09,348
documentation only. The note does not claim a physical inspection or an

1043
01:23:09,348 --> 01:23:10,733
optical measurement.

1044
01:23:11,834 --> 01:23:16,733
Submit the work. It is now awaiting the authorized reviewer, not automatically

1045
01:23:16,733 --> 01:23:17,298
approved.

1046
01:23:21,399 --> 01:23:27,488
We are now Jordan, the responsible Supervisor. Review the frozen scope, completion

1047
01:23:27,488 --> 01:23:33,057
note and evidence. Approval should be based on the requirements, not simply

1048
01:23:33,057 --> 01:23:34,987
on the presence of a file.

1049
01:23:36,088 --> 01:23:41,726
Return to technician is appropriate when clarification or correction is needed. We

1050
01:23:41,726 --> 01:23:46,539
will demonstrate a specific request before approving the training job.

1051
01:23:47,648 --> 01:23:52,443
Explain exactly what needs correction. A vague instruction such as fix it

1052
01:23:52,443 --> 01:23:56,121
does not tell the technician how to complete the review.

1053
01:24:04,182 --> 01:24:09,670
Confirm the return. The technician can now address the request and resubmit;

1054
01:24:09,670 --> 01:24:11,837
the work is not completed yet.

1055
01:24:15,942 --> 01:24:21,501
Sam reads the supervisor’s correction request. The requested change is a clearer

1056
01:24:21,501 --> 01:24:24,415
evidence reference, not a new network task.

1057
01:24:25,516 --> 01:24:30,701
Open Submit for review again and enter a corrected note naming the

1058
01:24:30,701 --> 01:24:31,958
saved checklist.

1059
01:24:47,716 --> 01:24:52,607
Resubmit the corrected work. The Supervisor will make a new review decision.

1060
01:24:56,716 --> 01:25:02,938
Jordan reviews the corrected note and saved checklist against the assigned scope.

1061
01:25:02,938 --> 01:25:05,934
The evidence reference is now explicit.

1062
01:25:07,036 --> 01:25:12,845
Select Approve and complete only after the recorded requirements are satisfied. An

1063
01:25:12,845 --> 01:25:18,583
inspection with no proposed network changes should not alter the existing optical

1064
01:25:18,583 --> 01:25:19,008
route.

1065
01:25:20,116 --> 01:25:25,518
Record the basis of the review. This note clearly identifies the fictional

1066
01:25:25,518 --> 01:25:27,197
nature of the exercise.

1067
01:25:39,878 --> 01:25:45,475
Confirm approval and verify the job status is Completed. The review decision

1068
01:25:45,475 --> 01:25:48,937
and responsible person are retained in history.

1069
01:25:53,038 --> 01:25:58,212
The timeline lets another reviewer follow the job lifecycle. Open it after

1070
01:25:58,212 --> 01:26:03,596
completion to inspect creation, dispatch, field actions and review decisions.

1071
01:26:04,696 --> 01:26:10,312
The return and resubmission are part of the work history. A completed

1072
01:26:10,312 --> 01:26:14,382
status does not erase earlier correction requests.

1073
01:26:15,496 --> 01:26:20,747
Open the report section. Select the content appropriate for the recipient and

1074
01:26:20,747 --> 01:26:25,384
check the company identity, job reference, scope, time and evidence.

1075
01:26:26,496 --> 01:26:32,013
A report summarizes recorded information. It does not turn a fictional checklist

1076
01:26:32,013 --> 01:26:36,288
into an optical measurement or replace missing field evidence.

1077
01:26:37,388 --> 01:26:41,527
The next chapters cover supporting tools and company exports, so you can

1078
01:26:41,527 --> 01:26:45,149
find and preserve the records created throughout this workflow.

1079
01:26:49,268 --> 01:26:54,946
The label library provides stable asset identities. Choose the asset family first,

1080
01:26:54,946 --> 01:26:59,308
then search for the exact code. A label identifies a record; it

1081
01:26:59,308 --> 01:27:03,739
does not independently prove that the physical asset matches it.

1082
01:27:04,839 --> 01:27:11,707
Select ODF, Hub and Network assets, then search for Academy ODF A.

1083
01:27:13,079 --> 01:27:18,227
Preview the matching label. Check the code and stable identifier before printing

1084
01:27:18,227 --> 01:27:20,415
or attaching a label to equipment.

1085
01:27:21,519 --> 01:27:26,339
The preview contains an actual QR image and its payload. The stable

1086
01:27:26,339 --> 01:27:30,152
identity is separate from the descriptive asset name.

1087
01:27:31,252 --> 01:27:36,479
Save PDF creates a printable file. We will download it locally and

1088
01:27:36,479 --> 01:27:39,013
verify that a file was produced.

1089
01:27:40,132 --> 01:27:44,795
Save QR image creates a vector image for the same identity. Use

1090
01:27:44,795 --> 01:27:49,605
the correct size and test readability when preparing real labels.

1091
01:27:50,706 --> 01:27:55,674
Print uses the browser’s printing workflow. Send or share prepares a communication.

1092
01:27:55,674 --> 01:28:00,232
Check the recipient and asset before sending; this lesson saves files locally.

1093
01:28:04,346 --> 01:28:10,031
PDF templates use company identity and document preferences. Review these settings before

1094
01:28:10,031 --> 01:28:12,713
relying on exported reports for customers.

1095
01:28:13,826 --> 01:28:18,617
The document company name should match the intended issuer. We will identify

1096
01:28:18,617 --> 01:28:21,013
the fictional Academy company clearly.

1097
01:28:22,114 --> 01:28:27,185
Header text can clarify the document context. We will mark our exports

1098
01:28:27,185 --> 01:28:28,779
as training documents.

1099
01:28:29,880 --> 01:28:35,485
Footer text can state a useful limitation. Our reports describe fictional records

1100
01:28:35,485 --> 01:28:38,460
and are not field measurement certificates.

1101
01:28:39,560 --> 01:28:45,524
The verification QR option applies to supported reports. The preview shows the

1102
01:28:45,524 --> 01:28:52,481
company identity and retained XANDER signature. Check the presentation against the intended

1103
01:28:52,481 --> 01:28:52,787
use.

1104
01:28:53,888 --> 01:28:59,101
Save PDF settings persists the document identity. It does not change the

1105
01:28:59,101 --> 01:29:01,490
network assets or complete a job.

1106
01:29:02,608 --> 01:29:08,432
Job order preferences can change display labels for project and reference fields.

1107
01:29:08,432 --> 01:29:14,543
They do not rename existing database identifiers. Keep labels understandable for both

1108
01:29:14,543 --> 01:29:16,196
office and field teams.

1109
01:29:17,297 --> 01:29:23,705
The template library lists registered document types. Sample output checks the common

1110
01:29:23,705 --> 01:29:28,077
layout; a live module export uses its own current records.

1111
01:29:32,178 --> 01:29:37,639
Job finances separates actual costs, billable amounts and invoices. Time records and

1112
01:29:37,639 --> 01:29:42,775
work quantities should be checked before financial totals are used. The amounts

1113
01:29:42,775 --> 01:29:45,245
in this lesson are fictional examples.

1114
01:29:46,346 --> 01:29:50,972
Add cost opens a manual entry. A saved company rate can populate

1115
01:29:50,972 --> 01:29:56,032
recurring values, while manual entry is useful for a specific expense.

1116
01:29:57,146 --> 01:30:03,834
Cost categories include labor, material, transport, equipment, subcontract, On Call and other

1117
01:30:03,834 --> 01:30:07,502
costs. We will use Other for this training example.

1118
01:30:08,602 --> 01:30:13,031
Write a clear description. It should explain the source of the cost,

1119
01:30:13,031 --> 01:30:14,790
not just say miscellaneous.

1120
01:30:20,282 --> 01:30:25,213
Unit and quantity determine the amount being counted. We will use one

1121
01:30:25,213 --> 01:30:26,214
training unit.

1122
01:30:32,129 --> 01:30:37,091
Actual unit cost and billable unit price are different. We will enter

1123
01:30:37,091 --> 01:30:41,549
ten for the internal example and zero for the billable amount.

1124
01:30:42,650 --> 01:30:47,546
Tax must be specified explicitly. Zero here is a fictional test value,

1125
01:30:47,546 --> 01:30:52,022
not guidance for a real transaction. We will also mark the entry

1126
01:30:52,022 --> 01:30:54,260
as not billable to the customer.

1127
01:30:55,370 --> 01:30:59,579
Save the entry and check its description in the cost list. The

1128
01:30:59,579 --> 01:31:04,331
actual cost changes, while this non billable entry should not become a

1129
01:31:04,331 --> 01:31:05,417
customer charge.

1130
01:31:06,530 --> 01:31:12,104
Export CSV downloads the cost list for review. Check currency, quantity and

1131
01:31:12,104 --> 01:31:13,664
description together.

1132
01:31:14,770 --> 01:31:20,038
Recorded work shows the underlying work and time sources. Avoid charging the

1133
01:31:20,038 --> 01:31:23,988
same activity twice through automatic and manual entries.

1134
01:31:25,090 --> 01:31:31,223
Customer invoices are a separate workflow. Review the customer, selected billable work,

1135
01:31:31,223 --> 01:31:36,581
dates and applicable tax before issuing a real document. This lesson creates

1136
01:31:36,581 --> 01:31:38,625
no payment or issued invoice.

1137
01:31:42,730 --> 01:31:47,349
Smart Job can prepare supported network and work actions when AI is

1138
01:31:47,349 --> 01:31:53,347
configured. This recording uses the published application, and AI execution is disabled

1139
01:31:53,347 --> 01:31:59,758
inside the isolated training environment. We will show request preparation without pretending

1140
01:31:59,758 --> 01:32:01,688
a live AI response occurred.

1141
01:32:02,789 --> 01:32:08,041
Specify the desired outcome and exact identifiers. A network asset request should

1142
01:32:08,041 --> 01:32:10,699
not be confused with a job order request.

1143
01:32:11,799 --> 01:32:18,992
Write the asset codes, cable capacity, tube, fiber, endpoint positions and intended

1144
01:32:18,992 --> 01:32:22,633
route. Clear identifiers reduce ambiguity.

1145
01:32:31,016 --> 01:32:35,816
Prepare proposal would send the request to the configured service. We will

1146
01:32:35,816 --> 01:32:40,551
not submit it in this offline training environment. In normal use, review

1147
01:32:40,551 --> 01:32:45,221
the actual proposed actions and missing information before confirmation.

1148
01:32:46,336 --> 01:32:52,277
Use voice depends on microphone permission and browser speech support. Review dictated

1149
01:32:52,277 --> 01:32:58,011
text before submitting, especially asset codes and fiber numbers. This chapter does

1150
01:32:58,011 --> 01:33:00,084
not simulate microphone input.

1151
01:33:01,184 --> 01:33:06,141
The New import option provides a separate work request import workflow. Imported

1152
01:33:06,141 --> 01:33:10,107
files still require review; an extracted value is not proof of a

1153
01:33:10,107 --> 01:33:11,284
correct assignment.

1154
01:33:12,385 --> 01:33:18,150
Text, source files and assignment instructions are separate inputs. Local analysis is

1155
01:33:18,150 --> 01:33:22,762
different from a live AI response, and job preview is different from

1156
01:33:22,762 --> 01:33:24,729
creating or dispatching work.

1157
01:33:28,829 --> 01:33:34,378
Job Files provides a central place to locate work documents. Use meaningful

1158
01:33:34,378 --> 01:33:39,631
filenames and the correct job reference so another team member can find

1159
01:33:39,631 --> 01:33:41,258
the intended evidence.

1160
01:33:42,359 --> 01:33:47,799
The measurement workspace is separate from ordinary file storage. Real OTDR or

1161
01:33:47,799 --> 01:33:52,820
iOLM evidence must come from the appropriate instrument and be linked to

1162
01:33:52,820 --> 01:33:54,076
the correct asset.

1163
01:33:55,176 --> 01:33:59,763
A sample checklist is not an optical trace. Review supported file formats,

1164
01:33:59,763 --> 01:34:04,907
measurement identity and linkage before treating a result as network evidence. This

1165
01:34:04,907 --> 01:34:07,201
course does not invent a measurement.

1166
01:34:08,301 --> 01:34:14,051
Network research searches recorded assets and evidence. Use exact codes to reduce

1167
01:34:14,051 --> 01:34:15,329
unrelated results.

1168
01:34:16,429 --> 01:34:22,582
Review source records behind any result. A search result, generated explanation or

1169
01:34:22,582 --> 01:34:26,933
map line should not override verified field documentation.

1170
01:34:28,034 --> 01:34:33,273
Fault location and engineering tools depend on trustworthy route and measurement inputs.

1171
01:34:33,273 --> 01:34:37,560
Their output is only as meaningful as the supplied data and assumptions.

1172
01:34:41,674 --> 01:34:48,720
Communication settings separates in application notifications, email and available delivery options. A

1173
01:34:48,720 --> 01:34:54,592
company event and a user’s personal notification preference are different settings.

1174
01:34:55,692 --> 01:35:01,322
Delivery history helps investigate notifications. Provider acceptance is not proof that a

1175
01:35:01,322 --> 01:35:04,548
person read a message or that it reached the inbox.

1176
01:35:05,652 --> 01:35:12,442
Internal mail is a separate communication workspace. Check recipients, subject, attachments and

1177
01:35:12,442 --> 01:35:14,657
the related job before sending.

1178
01:35:15,772 --> 01:35:20,263
A message does not dispatch, submit or approve a work order. Use

1179
01:35:20,263 --> 01:35:24,192
the dedicated workflow controls for those state changes.

1180
01:35:25,293 --> 01:35:32,206
Support requests should describe the page, attempted action, expected result and actual

1181
01:35:32,206 --> 01:35:37,530
error. Do not include passwords, invitation tokens or service keys.

1182
01:35:38,631 --> 01:35:44,235
Before reporting a problem, confirm the workspace, role and record identifier. Clear

1183
01:35:44,235 --> 01:35:48,572
details make it possible to reproduce the issue without guessing.

1184
01:35:52,672 --> 01:35:57,564
The company directory and public partner profile describe organizations. A listing is

1185
01:35:57,564 --> 01:36:01,305
not permission to access another company’s operational records.

1186
01:36:02,405 --> 01:36:08,880
Partner collaboration requires a defined scope. Check the organization, records, permissions and

1187
01:36:08,880 --> 01:36:11,038
duration before granting access.

1188
01:36:12,138 --> 01:36:17,996
Your company’s data remains distinct from a partner’s data. Review the exact

1189
01:36:17,996 --> 01:36:23,855
shared work rather than assuming a broad partnership makes every file available.

1190
01:36:24,955 --> 01:36:30,818
Subscription and Billing shows the plan, seats, expiry and applicable agreements. Review

1191
01:36:30,818 --> 01:36:34,949
the current terms in the application before making a purchase.

1192
01:36:36,049 --> 01:36:41,074
This tutorial does not purchase a plan or sign an agreement. Operational

1193
01:36:41,074 --> 01:36:46,308
account permissions and subscription availability serve different purposes.

1194
01:36:47,409 --> 01:36:51,815
Company data export is separate from ordinary use of a paid workspace.

1195
01:36:51,815 --> 01:36:56,158
The next chapter demonstrates the export access and archive download.

1196
01:37:00,259 --> 01:37:05,774
Company data export is a separate access path from ordinary workspace use.

1197
01:37:05,774 --> 01:37:11,587
It is designed to remain available after subscription expiry for an authorized

1198
01:37:11,587 --> 01:37:17,027
company account. It does not grant access to another company’s records.

1199
01:37:18,139 --> 01:37:25,475
Enter the exact company identifier. Export scope follows the authenticated company.

1200
01:37:26,579 --> 01:37:31,416
Enter an authorized account username. We will use the training Manager.

1201
01:37:32,517 --> 01:37:37,461
Enter the password and sign in for export. The password remains masked.

1202
01:37:38,997 --> 01:37:45,193
Review the export explanation before downloading. This comprehensive archive is different from

1203
01:37:45,193 --> 01:37:47,896
a single job report or asset spreadsheet.

1204
01:37:48,997 --> 01:37:53,844
Request the archive and wait for the download to finish. Large company

1205
01:37:53,844 --> 01:37:58,344
archives can take time, so do not assume that clicking the button

1206
01:37:58,344 --> 01:38:00,352
means the export is complete.

1207
01:38:12,639 --> 01:38:18,073
Keep the downloaded archive in an approved secure location. Check the manifest

1208
01:38:18,073 --> 01:38:23,159
and included attachments before relying on it as a retained company copy.

1209
01:38:23,159 --> 01:38:27,897
A downloaded archive is not an automatic import into another system.

1210
01:38:28,999 --> 01:38:34,138
If an export reports missing files or incomplete content, retain the warning

1211
01:38:34,138 --> 01:38:38,601
and resolve the cause. Do not rename an incomplete archive to make

1212
01:38:38,601 --> 01:38:39,886
it appear complete.

1213
01:38:43,999 --> 01:38:50,368
History helps explain changes to company records. Use the recorded identities, dates

1214
01:38:50,368 --> 01:38:56,130
and actions when investigating what happened, rather than relying on memory.

1215
01:38:57,239 --> 01:39:03,210
Archive is separate from deletion and active operational work. Review linked jobs,

1216
01:39:03,210 --> 01:39:07,797
routes and files before changing the lifecycle of a real asset.

1217
01:39:08,897 --> 01:39:12,666
The built in guide provides another reference when you return to a

1218
01:39:12,666 --> 01:39:14,723
tool. Open it from the help control.

1219
01:39:15,823 --> 01:39:21,836
We have followed a complete training workflow: registration, people and company setup,

1220
01:39:21,836 --> 01:39:28,198
customer and site records, network assets and connections, work preparation, personal time,

1221
01:39:28,198 --> 01:39:31,134
evidence, correction, approval and export.

1222
01:39:32,235 --> 01:39:36,313
Use the video chapters to repeat the part you need. Pause before

1223
01:39:36,313 --> 01:39:41,220
a save or confirmation, compare your identifiers, and verify the result after

1224
01:39:41,220 --> 01:39:41,921
the action.

1225
01:39:43,035 --> 01:39:49,355
Some capabilities depend on configured external services, actual instruments or field evidence.

1226
01:39:49,355 --> 01:39:55,142
This course labels those boundaries explicitly. Never treat a fictional tutorial record

1227
01:39:55,142 --> 01:39:58,601
as an as built measurement or customer installation.

1228
01:39:59,715 --> 01:40:04,667
Thank you for following the XANDER practical masterclass. Start with a small

1229
01:40:04,667 --> 01:40:10,272
training workflow, confirm each result, and use your company’s approved process when

1230
01:40:10,272 --> 01:40:12,357
moving to real operational work.