CHAPTER 01 — How to follow this practical masterclass Welcome to the XANDER practical masterclass. We will build a training company and a small fiber network together, then take a field job all the way through to review and reporting. Every action will appear on screen. The narration uses an AI generated voice. The company, people, sites and network records in this course are fictional. We are using an isolated copy of the published application, so these lessons do not change a customer network. Watch the highlighted control and the pointer. I will explain why we need a field, enter an example, save it, and check the result. Pause whenever you want to repeat a step in your own workspace. The course is divided into chapters. Start with account and company setup, then continue to people, customers, assets and connections. The later chapters cover field work, timers, evidence, approvals and exports. CHAPTER 02 — Request a workspace: required fields and options On the sign in screen, choose Request a seven day demo. If your employer already has a workspace, ask its administrator to invite you instead. A new request creates a separate company, not another user inside your existing company. The company name is required. We will use XANDER Academy Demo. Choose a recognizable legal or trading name for a real company. The separate company code is created by the platform. The registration number is optional. It is useful for company identification, but it is not your password or sign in code. This example uses a clearly marked training reference. The country field expects a two letter country code. We will enter B E for Belgium. This registration country is separate from the language of the interface. Enter the name of the person who will activate the Manager account. This course uses Alex Morgan. Later we will create separate employee and user records for the rest of the team. The work email must be valid and accessible. First, I will enter an invalid address to demonstrate the browser check. The form must not submit until the address has a valid email format. Now we correct the address. This example uses a fictional training mailbox captured locally. In a real workspace, use your own work email and check its inbox and spam folder for the activation link. The available languages are English, Dutch, French and German. We will keep English for this course. Language changes presentation; it does not create or move company records. Review the company, country, contact and email before sending. The notice explains the trial and payment conditions. Submit the request once, then wait for the confirmation. The confirmation means the request was accepted. It does not mean the account is already activated. The next step is to open the single use link from the activation email. CHAPTER 03 — Activate your account and handle a password mismatch Open the activation link from the email. The invitation identifies this company and user. The link is private and single use; do not forward it to another person. Choose a username that identifies your own account. We will use trainer for this example. Employee numbers and usernames are different identifiers. Choose a strong password with at least twelve characters. The screen keeps it masked. Use a password manager rather than copying a colleague’s credentials. The confirmation must match exactly. We will deliberately enter a different confirmation and select Continue. This demonstrates a correction on the form before the account is created. The error explains what needs correction. Enter the same password again in the confirmation field. Do not change your intended username just because the password confirmation was wrong. Select Continue again. A successful activation creates the account and returns the company code. Keep that code with your invitation details; you will need it when signing in. CHAPTER 04 — Sign in, correct an error and check your workspace The sign in form asks for a company code or a unique company name, followed by your username or verified email and password. The company identifies the workspace; your account identifies the person. Enter the company code from the invitation. For clarity, we use the exact generated code rather than searching for a similar company name. Now enter the username created during activation. We will use trainer. A verified email may also be accepted where the account supports it. First we will use an incorrect password to demonstrate a failed sign in. The application must keep us outside the company workspace. Check the company, username and password when sign in fails. Repeated guessing is not a recovery method. The Forgot password option uses the correct company and a verified recovery email. We will correct the password and sign in again. The password stays masked throughout the recording. The header shows the training company, account and Manager role. Confirm that this is the intended workspace before creating records. The welcome guide provides a sequence of initial setup tasks. We are now signed in as the training Manager. The following lessons will create the company details, team and customer records that later work depends on. CHAPTER 05 — Navigate, search, change language and return safely The dashboard is the starting point for the company workspace. My actions groups work by priority and due date. An empty view is normal for a new company; it is not an error. The sidebar is organized into groups. Expand Network to find assets, history, archive and labels. Expanding a group does not open or modify a record. Now open Assets. The heading changes to identify the current tool. Use the page title to confirm where you are before entering data. The workspace search in the header helps locate tools. We will search for Planning instead of manually scanning every sidebar group. Clear the search after using it so other tools become visible again. A search filter is a view of the available tools, not a change to your company records. The language menu offers English, Dutch, French and German. We will briefly select Dutch to show the interface change, then return to English. Codes and saved network identifiers remain the same. The Back control returns to the previous workspace when it is available. Scrolling the main page reveals longer forms, while the sidebar has its own navigation area. Keep unsaved changes in mind when leaving a form. If a tool is missing, check your role and subscription with the company administrator. The next lesson separates personal account settings from company configuration. CHAPTER 06 — Personal profile, recovery email and notification choices Open your account menu in the top bar. Profile contains personal details; it is separate from the company profile used on documents. The display name is the human readable name shown beside your actions. We will keep Alex Morgan. Changing this field does not rename the company or change your username. The personal phone number belongs to this account. Use the contact details appropriate for work. It is different from the company’s general contact number. Save the personal profile and wait for the success message. We will then reopen the settings menu to review language and account recovery. Account settings offers interface language, recovery options and password security. The language here is your preference; company defaults and notification language have separate controls. Open Email and notifications. The account is verified because we activated it through its email invitation. A verified address is important for password recovery. The recovery address should remain accessible to you. We will keep the verified training address. Changing an address requires verification before it can reliably be used for account recovery. Email language can follow the company or use one of the supported languages. We will explicitly choose English for the training account. Optional work notifications can be enabled or disabled for this account. This choice does not disable password recovery, and company notification rules still apply. We will enable them and save. For password security, use Change password when you know the current password, or Forgot password when you need a recovery link. Do not put passwords or recovery links in job notes, chat or support messages. This form asks for the current password, a new password and confirmation. Changing it signs out existing sessions. We will cancel this demonstration so the course keeps the same training credentials. CHAPTER 07 — Company profile: identity, contacts, documents and branding Company profile supplies identity details for work documents and other company workflows. It does not replace an employee record or your personal account settings. We will fill the training company carefully and save it once. The company code is read only here. It is the workspace identifier from registration. A clear company name is useful for people, while the code distinguishes the workspace when names are similar. The registration number helps identify the organization. This fictional reference is deliberately marked as training data. Use the correct registered details for a real company. VAT details are optional in this exercise. Enter the actual authorized tax information when your business needs it on documents. An example video should never invent a customer tax identity. The website field is company contact information. It does not change the address of the XANDER application or deploy a website. A logo can be uploaded as PNG, JPEG or WebP within the displayed size limit. We will use the existing XANDER training logo to demonstrate the upload and preview. The general email is the company contact address. It is different from a user’s verified sign in or recovery address. The support email identifies the company contact for support matters. Use the address authorized by your company. The primary company contact can be named on company documents. It does not grant that person an account or a permission. A contact title describes the person’s business responsibility. It is separate from the application security role. Now enter the company telephone number. Our number is fictional and used only to make the form example complete. The company address identifies the organization. Individual field sites can have completely different addresses. Use a consistent city name. Network location filters work best when the same place is not spelled several different ways. The postcode belongs to the company address. Later we will store separate location details on network assets and work sites. The country is human readable company information. This is separate from the two letter country code used in the registration form. Billing email identifies the company’s billing contact. We are not making a purchase or sending an invoice in this setup lesson. The invoice prefix helps identify documents created for this company. Choose a stable convention rather than changing it for every job. Bank account fields should contain only approved company details when needed. We will leave them blank in this fictional exercise. A profile field does not verify that a bank account exists. The public partner profile is separate from your private operational records. Its description and contact fields control the company information intended for partner discovery. We will use an explicit training description. Review the visibility option with your company’s policy before exposing a real public partner listing. The visibility checkbox controls the partner listing. We will switch it off for this training company and save the public profile separately. The time zone should match the company’s operational convention. Consistent time settings help teams interpret schedules, deadlines and work records. The default company language is separate from an individual user’s interface choice. We will keep English, then save the main company profile. Finally, reopen the profile and check that the address and contact details persisted. A form containing typed values is not proof of a successful save. CHAPTER 08 — Create a branch and a department, then verify the hierarchy The organizational hierarchy is company, branch, department or team, then employee. We will create a regional training branch and a fiber operations team. First select Add Branch with empty required fields. The application must refuse an incomplete branch rather than create a record with no useful identifier. A branch code is a stable identifier. We will use ACA BR zero one. Keep the code clear enough to distinguish this branch from another office or warehouse. The branch name is human readable. It can describe the operational location without changing the company name. Branch type offers Head Office, Regional Office, Field Office, Warehouse and Other. Select the type that describes this location. We will choose Regional Office. Enter the branch country. A branch can have its own location even when it belongs to the same company. Enter the branch city. Use a consistent spelling so employee and planning filters remain easy to understand. The branch address is different from a customer work site. Our course uses a fictional operations office. The postcode completes the branch address. Check the location before assigning people to a real branch. The phone is a branch contact number. It does not replace an employee’s own contact details. Use the branch email where your company needs a shared contact. Our training mailbox does not send messages outside the local environment. Save the branch. The table should now contain the code, name, type and location we entered. A department belongs to a branch. Select the branch we just created so the team appears under the correct location. Give the department a short stable code. We will use FIBER for the training operations team. Now enter the team name. An employee can later reference both the branch and this department. Save the department and verify the hierarchy in the table. We now have a branch and a team, but no employees or login accounts yet. CHAPTER 09 — Create technician employee Sam Taylor We will add Sam Taylor as an employee. This creates personnel master data. It does not create a login, verify an email address, or assign the person to a job. The employee or badge number is required and should be unique within the company. Use your organization’s numbering convention. Job title describes the employee’s operational work. In this example it is Technician. The login role will be selected separately when we create the account. Enter the first name. Correct names help the office choose the right person during planning and assignment. Enter the last name. We are using fictional people for all course exercises. The display name is the name used in operational lists. Keep it recognizable and consistent with the person’s account. Add the employee’s work email. This field alone does not verify the email for account recovery or notifications. Phone and mobile can be stored separately. Use the work contact appropriate for field coordination. The mobile field is employee information. Adding a number does not itself send a notification or enroll a device. Select the regional branch and Fiber Operations team. These links keep the employee inside the correct organizational hierarchy. Employment status offers Active, On leave, Inactive and Ended. The status should reflect the actual employment situation. We will keep this training employee Active. Contract type and dates are personnel information. They are not job deadlines. We will label the contract type as a training example. Contract start, contract end and hire date can be recorded when needed. Leave unknown dates empty instead of inventing them. Each date has its own meaning. On Call and its priority help identify employees for coverage. A checked flag does not create an on call schedule by itself. We will mark this technician as eligible. Notes should contain relevant employee information, not passwords or private service keys. This note clearly identifies the fictional record. Save the employee, then check the list for the badge number and name. The success message reminds us that sign in access still needs a user account. CHAPTER 10 — Create supervisor employee Jordan Lee We will add Jordan Lee as an employee. This creates personnel master data. It does not create a login, verify an email address, or assign the person to a job. The employee or badge number is required and should be unique within the company. Use your organization’s numbering convention. Job title describes the employee’s operational work. In this example it is Supervisor. The login role will be selected separately when we create the account. Enter the first name. Correct names help the office choose the right person during planning and assignment. Enter the last name. We are using fictional people for all course exercises. The display name is the name used in operational lists. Keep it recognizable and consistent with the person’s account. Add the employee’s work email. This field alone does not verify the email for account recovery or notifications. Select the regional branch and Fiber Operations team. These links keep the employee inside the correct organizational hierarchy. Employment status offers Active, On leave, Inactive and Ended. The status should reflect the actual employment situation. We will keep this training employee Active. Notes should contain relevant employee information, not passwords or private service keys. This note clearly identifies the fictional record. Save the employee, then check the list for the badge number and name. The success message reminds us that sign in access still needs a user account. CHAPTER 11 — Create a linked local account and inspect role choices People and access lists named accounts separately from employees. We will create a local account for Jordan and link the existing Supervisor employee. Email invitations are the preferred alternative when delivery is configured. Choose Create local account. This route provisions access without an email invitation, so the initial password must be handled securely. Select Jordan’s existing employee record. The application retains the linked personnel details, which helps assignment resolve the actual account behind a name. The display name identifies the local account. We will use the same name as the linked employee. Choose a unique account username. This is not the employee badge number or the company code. Enter a strong initial password. It stays masked. In real onboarding, use an invitation so the user can choose their own password when that workflow is available. The company role determines the base permissions. Review the available roles, then select Supervisor for Jordan. Job title and security role should not be confused. Create the account, then check that Jordan appears as an active Supervisor linked to the employee. This local account’s email may still require verification. CHAPTER 12 — Invite a technician and distinguish pending from active access Now we will invite Sam through email instead of sharing a temporary password. This makes the invitation and account activation separate, visible steps. Select Invite user. The invitation expires and can be revoked before acceptance. Choose Sam’s existing employee record. Linking the correct employee helps preserve consistent names and assignments across the company. Check the full name and work email populated from the employee. A wrong address can prevent the intended person from receiving an invitation. Choose Technician as the company role. A technician executes assigned field work; this is different from preparing or approving all company work. Send the invitation and inspect its pending status. Pending means the person has not accepted it yet; it is not proof that an email reached an inbox. If the wrong person was invited, revoke the pending invitation and send a corrected one. If the person already accepted, manage the actual account instead. We will accept Sam’s training invitation in the next lesson. CHAPTER 13 — Accept the technician invitation and verify access Sam opens the private invitation link received by email. The form belongs to the company that sent the invitation. An invitation should be accepted by its intended recipient. Sam chooses a personal username. We will use sam. A shared crew login would lose the distinction between individual actions. Enter a strong password and confirm it. The recording keeps both entries masked. The user chooses the password during activation. Select Continue to accept the invitation. Wait for the sign in form before proceeding. A pending invitation and an active account are different states. The company identifier is retained on the sign in screen. Enter Sam’s username and password to test the new account. Sam is now signed in as a Technician. Available workspaces follow this role and company permissions. An empty task list is expected before work is assigned. CHAPTER 14 — Understand base roles, custom permissions and account policies We are back in the Manager account. Roles and permissions separates base roles, custom role grants and explicit user access policies. A job title is not a security permission. Create role opens the custom permission form. Navigation permissions control access to workspaces; action permissions control capabilities inside them. A custom role needs a clear purpose and name. We will inspect the form without assigning additional privileges to the training users. Use the description to explain the intended responsibility. Permission choices should follow the person’s actual duties. Each checkbox represents a specific grant. A navigation grant is not a substitute for the action permission. Avoid selecting everything merely to make a screen visible. Cancel closes this example without creating a role. The course will continue with the existing Manager, Supervisor and Technician base roles. User role assignments show the named people and base roles. Custom roles and user access policy are separate controls. Check the effective access after any real permission change. Return to People and access to confirm that Sam is now active. Pending invitations are managed separately from accounts that have already accepted. CHAPTER 15 — Create a customer: identity, billing and additional information A customer is the organization receiving the work. Its contacts and field sites are separate records. We will create one customer and then add both a responsible person and an independent work site. Name is required. Select Save changes with an empty form to see the required field check. The browser keeps the form open so we can complete it. Enter a recognizable customer name. This fictional network operator will be linked to our field job later in the course. Use a stable customer code. A code helps distinguish similar company names and makes imports and searches easier to reconcile. Registration and VAT fields identify the customer organization. We will enter a training registration reference and leave the tax number empty. The customer email is a business contact. It does not create an application account or grant access to your workspace. Add the general customer phone number. A named on site contact may use a different number. The website is contact information. It does not change the application or publish the customer record. This address belongs to the customer headquarters. Do not automatically use it as the location of every field job. Enter the customer city consistently. The work site we create next will have its own location fields. Enter the headquarters postcode. It is independent of the network route coordinates. Enter the customer country. We keep the training example in one country so the later address comparisons are easy to follow. Billing address can differ from the headquarters and the work site. Use the billing information approved for the customer. Billing email should reach the correct accounts team. Saving this field does not send an invoice or charge a payment method. Use notes for relevant customer context. Keep passwords and service credentials out of general business notes. Status can be Active or Inactive. Inactive records remain in history but are not available for new work. We will keep this customer Active. Additional information lets you add a named field instead of placing every detail in one long note. Select Add extra and give the field a clear meaning. Save the customer and wait for the directory to return. Check the name and code before moving on. Open the saved customer. Its details, contacts and work sites are grouped here. This confirms the form was saved rather than merely typed. CHAPTER 16 — Add a named customer contact A named contact records who is responsible at the customer. It is separate from your own employee list and from the customer’s general email. Enter the full contact name. We will use Casey Brooks, the fictional coordinator for this customer. Role or responsibility explains why this person is relevant. It does not grant an application security role. Use the contact’s own work email. Check spelling before using it in operational communication. Phone may identify an office line. Store the appropriate contact for the agreed work process. Mobile is a separate field for field coordination. The course uses fictional numbers. A short note explains this contact’s practical responsibility. Avoid unnecessary personal information. The Active checkbox determines whether the contact can be selected for new work. We will leave it checked and save. The saved contact now appears inside this customer. Another customer’s contacts are not automatically shared with this record. CHAPTER 17 — Create an independent work site and access instructions A work site describes where the technician should go. It can be different from the customer headquarters and billing address. Select Add work site. Give the work site a recognizable name. Later we will choose this saved site on the work order. Enter the actual work location. This example deliberately differs from the customer headquarters. The city belongs to this work site. Consistent location information helps field teams avoid travelling to the billing address. Add the work site postcode. Review it together with the street and city. Select the correct country information for the work location. Latitude and longitude can help locate a site. Our coordinates are training references, not a surveyed network position. Longitude is separate from latitude. Always check coordinate order and the accuracy of your real source data. Access instructions should be actionable. Tell the technician what to do before arriving without storing passwords or secret door codes here. An on site contact can be recorded directly for this location. It may be different from the customer’s general contact. Add the phone number appropriate for this site. Our example matches the coordinator created in the previous chapter. The site contact email is stored with the location. Review it for accuracy before saving. The note clearly identifies this as a training site. Keep operational instructions in the dedicated access field. Save the work site and verify its name appears under the customer. We now have the customer, contact and location ready for a work order. CHAPTER 18 — Create a head end and inspect its generated hierarchy A head end is a structured network asset. Its hierarchy contains cabinets or racks, drawers, cassettes and fiber positions. The structure is distinct from a cable’s physical tube and fiber inventory. Name and code are required. Select Save before entering them to see the validation message. Nothing should be created from an incomplete identity. Enter a descriptive head end name. Use a name the office and field teams can recognize. The head end code is its stable identifier. We will use the same academy prefix as the rest of our training network. Enter the network asset address. The Open map button uses location information; it does not establish a verified cable route. Postcode and city can be entered separately. The Belgian postcode lookup is a convenience when applicable. Use a consistent city value for related assets. This helps searches and exports. Coordinates describe the head end location. Use verified survey data for a real installation. Check longitude separately. Incorrect coordinate order can place an asset far from its actual location. The initial cabinet or rack gets its own code. This code identifies the physical housing inside the head end. Choose two drawers for this compact training head end. The application generates drawer identifiers from the chosen structure. Choose two cassettes per drawer. This is structural capacity; it does not connect a cable or make a fiber live. Fiber positions per cassette offers twelve or twenty four. We will use twelve, giving two drawers times two cassettes times twelve positions: forty eight positions. Save creates the hierarchy. After creation, the structural fields are locked to protect existing fiber identities. Name, code and location remain separate editable details. CHAPTER 19 — Create a real cable: twenty four tubes and two hundred eighty eight fibers The head end workspace separates its cable list from the hierarchy below. We will create a physical cable with twenty four tubes and twelve fibers per tube. Manual entry and saved standard cables are two ways to populate this form. A standard provides repeatable specifications. We will use Manual to show every important field. Give the cable a stable code. This identifies the cable itself, not a route or a work order. Cable type describes its network role. We will use Feeder for the training example. Enter twenty four tubes. The total fiber count updates automatically from tube count multiplied by fibers per tube. Fibers per tube offers several capacities. Choose twelve. Twenty four times twelve is two hundred eighty eight, and the automatic total should now show that number. Over length records spare length for the cable specification. It is not the measured length of every route segment. We will use ten for this exercise. Direction gives a useful destination description. Text alone does not connect network assets. We will create explicit connections later. Destination asset type describes the intended endpoint category. Select ODF. This choice does not silently create an ODF or terminate a fiber. Save stores the cable and returns a fresh form. Next stores it and continues to tube colors. Done stores it and returns to the head end. We will select Next to inspect the generated tubes. Twenty four tube cards now exist. Each card identifies its tube number and fiber range. We will configure colors in the next chapter rather than confusing color with connectivity. CHAPTER 20 — Tube colors, stripes and complete fiber definitions Tube numbers remain stable when colors change. A cable can use a standard color convention, including stripes when colors repeat. Match the actual cable manufacturer’s specification. For this exercise, tube one will be red. The automatic swap prevents an unintended duplicate color in the same color group by swapping the existing color assignment. The Stripe checkbox distinguishes striped tubes from plain tubes. It is not a connection status or a live signal indicator. We will keep tube one plain. Inspect the lower tube cards. The numbers and fiber ranges continue through tube twenty four; the unused capacity is still part of this cable. Save persists the tube color map. Next saves it and opens fiber definitions. Select Next to inspect all two hundred eighty eight fiber definitions. Each fiber has a cable wide number and a position within its tube. The color identifies the physical strand. Do not assume a red strand is always position one in the tube. Find the red strand within tube one. Later we will select it by its actual inventory identity, not by typing a free text color into a route. The fiber definition view is a pre allocation layout. Existing cassette allocations and live states are separate records. We will keep the generated fiber colors and finish. The saved cable appears in the head end. Creating capacity did not create a work order, and it did not make every fiber connected or live. CHAPTER 21 — Create Academy ODF A and its free positions An ODF has its own identity, location and capacity. We will create Academy ODF A as one endpoint of the training connection. The second endpoint must be a separate asset. Open the new ODF form. Manual specifications are useful for a unique asset; a saved standard can populate repeated equipment consistently. Enter the unique ODF code. This identifies the frame independently of the head end and cable. Enter a clear display name. The code and name will help us select the correct endpoint later. The endpoint location can differ from the other end of the cable. Record the actual installation address. Keep related location names consistent for searching and reporting. Latitude describes this endpoint. Our example uses fictional training coordinates. Longitude completes the coordinate pair. A coordinate is not proof of a surveyed route. Frame type describes the physical form of this ODF. Mounting describes how the frame is installed. Keep equipment specifications consistent with the actual unit. The connector type is a physical specification. It does not establish optical compatibility by itself. We will provide twelve ports. This ODF capacity is independent of the cable’s two hundred eighty eight fibers. Splice capacity describes the ODF specification. Only the selected strand will be terminated in our demonstration. Fiber mode is a specification, separate from whether a strand is free, connected or live. Asset status offers Active, Planned, Reserve and Out of service. We will keep the fictional asset Active. Status alone does not apply physical connections. Save the asset and inspect its digital twin. It has an identity, but positions still need to be built before selecting a physical port. Build positions creates the configured capacity. The positions begin Free and Not live. Creating positions does not connect the cable. Select the first position to inspect its action, status, live state and cable selectors. We will leave it unconnected until both endpoints are ready. CHAPTER 22 — Create Academy ODF B and its free positions An ODF has its own identity, location and capacity. We will create Academy ODF B as one endpoint of the training connection. The second endpoint must be a separate asset. Open the new ODF form. Manual specifications are useful for a unique asset; a saved standard can populate repeated equipment consistently. Enter the unique ODF code. This identifies the frame independently of the head end and cable. Enter a clear display name. The code and name will help us select the correct endpoint later. The endpoint location can differ from the other end of the cable. Record the actual installation address. Keep related location names consistent for searching and reporting. Latitude describes this endpoint. Our example uses fictional training coordinates. Longitude completes the coordinate pair. A coordinate is not proof of a surveyed route. Frame type describes the physical form of this ODF. Mounting describes how the frame is installed. Keep equipment specifications consistent with the actual unit. The connector type is a physical specification. It does not establish optical compatibility by itself. We will provide twelve ports. This ODF capacity is independent of the cable’s two hundred eighty eight fibers. Splice capacity describes the ODF specification. Only the selected strand will be terminated in our demonstration. Fiber mode is a specification, separate from whether a strand is free, connected or live. Asset status offers Active, Planned, Reserve and Out of service. We will keep the fictional asset Active. Status alone does not apply physical connections. Save the asset and inspect its digital twin. It has an identity, but positions still need to be built before selecting a physical port. Build positions creates the configured capacity. The positions begin Free and Not live. Creating positions does not connect the cable. Select the first position to inspect its action, status, live state and cable selectors. We will leave it unconnected until both endpoints are ready. CHAPTER 23 — Create route manhole 1 with location and connectivity choices This is manhole 1 of four between our ODF endpoints. A manhole record describes a location and its infrastructure. It is not automatically a fiber splice. Enter a unique manhole code. We will keep the route sequence easy to follow with numbered training codes. Add a readable name. The code remains the stable identifier. Type or standard describes the chamber. A reusable standard can reduce repeated specification entry. A full address is required before connectivity search is enabled. Enter the location of this chamber. Enter the location postcode. It can differ from the company and customer headquarters. Use the same city convention as the related network assets. Enter the latitude from the location source. The example coordinates are training references. Enter the longitude. Once the address and coordinates are present, connectivity choices become available. Connectivity offers Standalone, Continue from another manhole, Between manholes, Multiple connections and Planned. These describe infrastructure relationships; they do not splice a selected strand. We will start with a standalone chamber. The route lesson will explicitly connect the intended assets rather than assuming a connection from similar names or coordinates. Save the manhole and inspect its workspace. Confirm the code and location before using this chamber in a route. CHAPTER 24 — Create route manhole 2 with location and connectivity choices This is manhole 2 of four between our ODF endpoints. A manhole record describes a location and its infrastructure. It is not automatically a fiber splice. Enter a unique manhole code. We will keep the route sequence easy to follow with numbered training codes. Add a readable name. The code remains the stable identifier. Type or standard describes the chamber. A reusable standard can reduce repeated specification entry. A full address is required before connectivity search is enabled. Enter the location of this chamber. Enter the location postcode. It can differ from the company and customer headquarters. Use the same city convention as the related network assets. Enter the latitude from the location source. The example coordinates are training references. Enter the longitude. Once the address and coordinates are present, connectivity choices become available. Connectivity offers Standalone, Continue from another manhole, Between manholes, Multiple connections and Planned. These describe infrastructure relationships; they do not splice a selected strand. We will start with a standalone chamber. The route lesson will explicitly connect the intended assets rather than assuming a connection from similar names or coordinates. Save the manhole and inspect its workspace. Confirm the code and location before using this chamber in a route. CHAPTER 25 — Create route manhole 3 with location and connectivity choices This is manhole 3 of four between our ODF endpoints. A manhole record describes a location and its infrastructure. It is not automatically a fiber splice. Enter a unique manhole code. We will keep the route sequence easy to follow with numbered training codes. Add a readable name. The code remains the stable identifier. Type or standard describes the chamber. A reusable standard can reduce repeated specification entry. A full address is required before connectivity search is enabled. Enter the location of this chamber. Enter the location postcode. It can differ from the company and customer headquarters. Use the same city convention as the related network assets. Enter the latitude from the location source. The example coordinates are training references. Enter the longitude. Once the address and coordinates are present, connectivity choices become available. Connectivity offers Standalone, Continue from another manhole, Between manholes, Multiple connections and Planned. These describe infrastructure relationships; they do not splice a selected strand. We will start with a standalone chamber. The route lesson will explicitly connect the intended assets rather than assuming a connection from similar names or coordinates. Save the manhole and inspect its workspace. Confirm the code and location before using this chamber in a route. CHAPTER 26 — Create route manhole 4 with location and connectivity choices This is manhole 4 of four between our ODF endpoints. A manhole record describes a location and its infrastructure. It is not automatically a fiber splice. Enter a unique manhole code. We will keep the route sequence easy to follow with numbered training codes. Add a readable name. The code remains the stable identifier. Type or standard describes the chamber. A reusable standard can reduce repeated specification entry. A full address is required before connectivity search is enabled. Enter the location of this chamber. Enter the location postcode. It can differ from the company and customer headquarters. Use the same city convention as the related network assets. Enter the latitude from the location source. The example coordinates are training references. Enter the longitude. Once the address and coordinates are present, connectivity choices become available. Connectivity offers Standalone, Continue from another manhole, Between manholes, Multiple connections and Planned. These describe infrastructure relationships; they do not splice a selected strand. We will start with a standalone chamber. The route lesson will explicitly connect the intended assets rather than assuming a connection from similar names or coordinates. Save the manhole and inspect its workspace. Confirm the code and location before using this chamber in a route. CHAPTER 27 — Create a closure: placement, ports, phases and cassettes A closure contains cable entries and splice positions. We will place a training closure in the second manhole. A chamber and the closure inside it are separate assets. Placement offers an existing manhole, a new manhole created with the closure, or Standby for later placement. We already created the chamber, so choose the existing option. Select Academy Manhole two. Verify the code and address rather than selecting the first similar record. Enter a stable closure code. The closure identity stays distinct from the chamber code. A saved standard can fill repeated specifications. We will keep Manual and describe a fictional training enclosure. Manufacturer and model describe equipment. This example does not claim compatibility with a real vendor product. Use the actual model for a real enclosure. Our training model is explicitly fictional. Four physical ports are enough for this exercise. A physical port count is different from a cassette’s fiber splice capacity. An oval window cut pairs ports one and two for a continuing cable. We will choose No for this simpler enclosure, so the lesson does not imply a window cut that was never documented. Phases can be A or A and B. Select A for this exercise. Separate phases are useful when the physical enclosure and work process require them. Create two phase A cassettes. This supplies splice capacity, but it does not connect any strands. Leave phase B cassette count at zero and save the closure. Inspect the resulting ports and cassettes in Closure Studio. The studio separates cable entries, cassettes and splice work. Blue planned work is not the same as confirmed as built connectivity. CHAPTER 28 — Add optical cable inventory and confirm the training installation The head end cable lesson showed the rack cable workflow. This closure workflow creates the optical cable inventory used by the ODF selectors. We will give this separate training cable its own code. Mode offers an existing cable asset or a new cable. Choose Create new cable so the application generates its tube and fiber inventory. This optical cable code differs from the head end example. Clear identifiers prevent two separate records from being mistaken for one physical cable. Record the cable type. It describes the cable’s intended role, not the connection status of every strand. Enter twenty four tubes. The cable will contain a full inventory, including unused strands. Select twelve fibers per tube. Twenty four times twelve gives two hundred eighty eight fiber records. Only available closure ports are offered. Choose port one for this cable entry. A closure cable port and an ODF termination position are different identifiers. Enter a clear direction description. We will select the exact ODF endpoints in Route Builder later. Add the cable and inspect its planned work marker. The cable exists now, but this action has not confirmed field installation. Confirm work done is a significant action. Use it only after actual field work and verification. In this isolated course, we will confirm a fictional training installation; no real optical measurement or physical work is claimed. Select Confirm work done and read the confirmation. This demonstration has no active field job. When a closure belongs to an active job, completion must follow the assigned review workflow. The planned marker is cleared after confirmation. The cable is now available for active optical endpoint selection. Its unused fibers remain available; confirming a cable entry does not splice all of them. CHAPTER 29 — Build a six point optical route and verify both terminations Route Builder selects exact assets and endpoints. We will record a fictional verified connection from ODF A through four manholes to ODF B. New field work should instead be saved as a design for later execution and review. Give the route a meaningful name. A route name does not create missing assets or substitute for selecting the actual fiber. Choose the training city to narrow the asset catalog. This filter affects selection, not ownership or company access. Add ODF A as an endpoint. Select the ODF category, then the exact asset code. Select the active optical cable created in Closure Studio. The cable dropdown is an inventory selection, not a free text label. Choose tube one, which is red in this cable’s color convention. Tube number and color are both visible so you can verify the choice. Choose the red fiber inside tube one. The remaining fibers are not selected for this route. Choose rack one, panel one, position one. Then add the ODF point. This records the exact cable, tube, fiber and termination position in the route proposal. Add manhole 1 as the next route point. The sequence represents the intended path between the two endpoints. Select this manhole’s physical endpoint. Passing through a chamber does not automatically create a splice. We are keeping the same optical strand along this route. Add manhole 2 as the next route point. The sequence represents the intended path between the two endpoints. Select this manhole’s physical endpoint. Passing through a chamber does not automatically create a splice. We are keeping the same optical strand along this route. Add manhole 3 as the next route point. The sequence represents the intended path between the two endpoints. Select this manhole’s physical endpoint. Passing through a chamber does not automatically create a splice. We are keeping the same optical strand along this route. Add manhole 4 as the next route point. The sequence represents the intended path between the two endpoints. Select this manhole’s physical endpoint. Passing through a chamber does not automatically create a splice. We are keeping the same optical strand along this route. Add ODF B as an endpoint. Select the ODF category, then the exact asset code. Select the active optical cable created in Closure Studio. The cable dropdown is an inventory selection, not a free text label. Choose tube one, which is red in this cable’s color convention. Tube number and color are both visible so you can verify the choice. Choose the red fiber inside tube one. The remaining fibers are not selected for this route. Choose rack one, panel one, position one. Then add the ODF point. This records the exact cable, tube, fiber and termination position in the route proposal. Review all six points in order. Remove or move controls allow corrections before building. A similar asset name or nearby coordinate is not enough to identify the correct endpoint. Preview validates the selected endpoint transport and displays warnings. Resolve actual warnings before recording connectivity. Save design is appropriate for proposed new work. Record verified existing connectivity applies existing connections immediately. We will use the verified option only for this explicitly fictional training connection. Enter the verification context. In production this must describe genuine supporting evidence, not a guess or an AI suggestion. Confirm the verified connectivity and wait for the saved route record. This action is independent of creating a work order. The trace shows six points and five connections. Read the transport at both ODF endpoints: the same cable, tube one, red fiber and position one. Open Diagrams and export to inspect the recorded route. A connection diagram documents selected relationships; it is not proof of an accurately surveyed street geometry. CHAPTER 30 — Verify connected fiber inventory and export the route Reopen ODF A after saving the route. Its recorded state now shows the connection. This is a verification of saved data, not just the earlier route preview. Select position one and read the connected cable, tube and fiber. Live state is separate: a recorded connection does not prove that an optical signal is present. Open ODF B and inspect the same position. Both endpoint records should refer to the same selected optical strand. Now open the cable’s digital twin. The full twenty four tube inventory remains present after connecting one strand. Open the first tube’s fibers. The red fiber now shows Connected, matching the saved ODF endpoints. The other eleven fibers in this tube remain Free. A connection records how the network is wired; it does not mean that the fiber carries a live optical signal. The cable still contains all two hundred eighty eight fibers across twenty four tubes. Exactly one strand is connected, and two hundred eighty seven remain Free. Planned work is separate from a confirmed connection: always check reservations before allocating a free strand. Return to the route diagrams. Inspect the first ODF table and its selected position before exporting. Download diagrams PDF produces a readable record of the selected route. We will save the actual generated file locally. Download diagrams Excel creates worksheets for the route stops. Keep the exported file together with the route identity and its revision context. CHAPTER 31 — Add a branch cable for splice planning A splice joins two physical fibers inside a closure. We will prepare a separate blue fiber example, leaving the red endpoint route unchanged. This example remains planned work. Add a second cable to the closure. A splice needs two distinct physical fiber identities, not the same strand selected twice. Use a new cable code for this short branch example. Choose one tube with twelve fibers. The smaller capacity makes the two sides easy to compare. Choose free port two and add the cable. It remains marked as planned until the appropriate work confirmation. Open New Splice. The selectors use actual cables, tubes and fibers linked to this closure. CHAPTER 32 — Select physical fibers, validate a splice and inspect planned work Open New Splice to prepare a change using the two cables now attached to the closure. The current confirmed state remains separate from the proposed change. Select the optical cable on the left, then its first tube. Each selector narrows the physical inventory. Select the blue fiber on the left. We are keeping the red route strand out of this separate splice example. To test validation, temporarily select the identical cable, tube and blue strand on the right. A physical fiber must not be spliced to itself. Validate the selection. The same fiber error should appear and the plan must remain unsaved. Correct the right side to the separate branch cable, then select its first tube and blue fiber. Target location includes cassettes and dark rooms. A new paired splice belongs in an available cassette position. Dark room moves have different requirements when editing an existing fiber. Status distinguishes spliced, pass through, loose, free and reserve. Free and reserve describe an unpaired fiber and require one side to be cleared. We will keep Spliced for this pair. Live state is independent of splice status. Keep both sides Not live unless actual verified evidence supports another state. Value or clamp and customer fields can add context to this splice. We will identify this as a training plan. Validate and plan the corrected splice. The saved result should remain planned until the proper field confirmation. Inspect the planned work in the cassette overview. Do not use Confirm work done merely to remove a blue marker. This plan is intentionally outside the documentation inspection job. CHAPTER 33 — Create a complete inspection job: identity, site, people and scope A work order organizes the requested work, team, location, evidence and review. We will create an inspection of our fictional network documentation. Creating an inspection does not itself change the optical route. Job type offers Repair, Maintenance, Emergency, Installation, Inspection, Survey and New Splice. Choose the category matching the actual work. We will select Inspection. Priority describes urgency separately from the job type. Review Low through Critical. We will keep Normal for this planned training inspection. Project number groups work under a recognizable project reference. We will use Academy Project one. The job reference distinguishes this assignment. Use a meaningful reference rather than putting the full work instructions in the identifier. Due date and due time describe the requested deadline. They do not start the personal work timer. For this unscheduled training exercise we will leave them empty. Open Customer and Site. We will select the saved customer instead of retyping a slightly different name. Choose Academy Network Operator from the saved customer selector. The customer and its related work sites should now be available. Select the saved Academy Fiber Training Site. This uses the field location, not the customer’s headquarters or billing address. Select Casey as the customer contact. Review the populated information before continuing. A saved contact helps avoid repeated typing errors. The site address and access instructions are shown in the work form. We will make the training restriction explicit for the assigned technician. Open Assignment. The employee roster and linked user accounts prepared earlier now allow us to choose real named people in this training company. Select Jordan Lee as the responsible supervisor. The primary supervisor owns the review responsibility for this assignment. Select Sam Taylor as technician. Additional technicians can be selected when the work needs a crew. The first selected technician is primary. Open Network Work Package. It supports multiple asset types. We will attach the exact ODF after creating the order, so this chapter can focus on the preparation fields. The network choices include closures, ODFs, hubs, head ends, cabinets, manholes and cables. Selecting a category is different from linking the exact existing asset. Files can include diagrams, photos and field documents. The measurement library is separate. Use genuine instrument results when the job requires OTDR evidence; a tutorial example is not a measurement. Open Work Instructions. A clear summary, required action and completion requirements tell the technician what success means. The summary explains the objective. It should help the field team understand why the work exists. Required action states what must be done. We are inspecting documentation rather than requesting a live network change. Work scope defines the boundaries. Explicit boundaries help prevent unintended changes outside the assignment. Completion requirements identify the evidence needed for review. A technician should know these requirements before starting. Service impact describes the expected effect of the work. In a real job this should be assessed against the actual network. Safety notes should be relevant to the actual assignment and company process. This software tutorial does not replace field safety training. Dispatch notes highlight coordination information. They supplement the required action rather than replacing it. Review the prepared job before creating it. Check type, priority, site, supervisor, technician and required action together. Create the job once and wait for its workspace. Creation is separate from dispatch, execution, submission and approval. The new work order has its own identity and status. Next we will attach the exact network record and review dispatch readiness. CHAPTER 34 — Attach the exact ODF and review dispatch readiness The job exists but still needs its exact network context. Open the Network section to link the ODF to this inspection. Add an existing ODF. Selecting an asset for a job does not create a duplicate asset or change its connections. Choose Academy ODF A by its code. Confirm the record before adding it to the work order. Add the selected asset, then finish the picker. The work order now references the existing ODF. Open dispatch review. Read the site, assigned team, scope and any blockers before releasing the job. Dispatch is a separate deliberate step. Missing assignment or work instructions must be corrected before proceeding. Our training job has named people and a clear inspection scope. Confirm dispatch and wait for the resulting status. Outbound email is captured locally in this training environment; no real employee receives a notification. The technician can now open the assignment. Dispatch does not mean work has started, and a notification is not proof that the recipient read the instructions. CHAPTER 35 — Planning, dates and on call coverage Planning helps coordinate assigned work and availability. Review the job identity, people and timing together rather than treating a calendar entry as the full work instruction. A due date is a requested deadline. A personal work timer records an individual interval. Changing a schedule does not automatically start or stop a timer. On Call is a separate coverage roster. An employee marked eligible for On Call still needs the relevant schedule and job assignment. Check the date and the designated technician or supervisor before using coverage for an urgent job. A roster should reflect agreed availability, not an assumption that everyone is working. Keep the responsible supervisor and actual crew current when plans change. The job’s recorded scope and evidence requirements continue to apply. CHAPTER 36 — Start a personal timer and stop it from another workspace We are now Sam, the assigned Technician. Read the work objective, access restrictions and completion requirements before recording work. Open My work time. The personal timer belongs to this account and this job. It is separate from dispatch or the job execution status. Enter a meaningful description of the activity. A description helps explain the recorded interval later. Start my timer begins the personal interval. Watch the running timer indicator in the top bar. Move to another workspace. The timer indicator remains available, so you do not have to search through every project to find a running clock. Open the timer indicator. It lists the active project and its work description. Multiple projects can have independent timers; check which interval you intend to stop. Update this interval’s description to reflect what was actually reviewed. Keep descriptions specific to each project. Stop the correct personal timer. Stopping time does not submit the job or approve the work. Return to the job and open work time again to inspect the saved interval. Review time records before using them in cost calculations. The closed interval records a duration and description. If you forgot to stop a timer, follow your company’s correction process rather than treating the entire elapsed period as verified work. CHAPTER 37 — Prepare a second project for the multiple timer example To demonstrate independent timers, we will prepare a second fictional project. It has its own reference and activity description. Enter a distinct site description for the second project. This keeps it recognizable in the timer list. Assign Sam and Jordan again. The people can work across projects while each job keeps a separate identity. Describe the limited task: record a training time interval only. We are not requesting a second physical network change. Review and create the second job. The timer demonstration uses its separate project reference. CHAPTER 38 — Run two project timers and stop each independently Sam will start a separate timer on each project. Start the first project with its own activity description. Open the second project and start its timer with a different description. Starting this interval should not silently replace the first one. Open the persistent timer list. Both running projects should be visible together. Each project retains its own description. Check the project identity before editing or stopping a timer. Stop the first listed interval. The other project should remain running. Now stop the remaining interval. Neither clock should continue unnoticed after this demonstration. Multiple timers are a recording capability, not proof of simultaneous billable work. Review the recorded intervals and apply your company’s time accounting rules. CHAPTER 39 — Upload evidence and verify the saved attachment Evidence should match the assignment. This inspection requires a clearly marked training checklist. Real photos and instrument measurements must come from the actual field work. Open Evidence uploads. Use the technician’s evidence controls so the file stays linked to this assignment. Choose Add files and select the training checklist. A selected filename is not yet proof of a successful upload. Wait until the saved filename appears. We will also verify that the backend file list contains this attachment before continuing. The checklist identifies the ODF, cable, tube, fiber and position, and explicitly says this is a fictional exercise. It does not claim an optical loss measurement or a physical site inspection. For a real measurement requirement, attach the actual supported instrument result and link it to the correct job and network asset. Do not rename an unrelated file to make a requirement appear complete. CHAPTER 40 — Report a field issue and record a supervisor decision If something differs from the approved instructions, report an issue. Do not silently change the network or mark incomplete work as complete. The affected task selector can identify a particular task or the whole job. We will report a documentation question for the whole training inspection. Describe the difference and the decision needed. A precise issue gives the supervisor something actionable to review. Submit the issue. It remains open until an authorized reviewer records a decision, and can block completion. CHAPTER 41 — Resolve the reported issue within the assigned scope The Manager can see the open field issue and the question Sam recorded. Review it against the approved scope before answering. Record a clear decision. A response can clarify the existing scope; a new connection change would require revised engineering work. Resolve the issue and verify it is no longer open. The decision becomes part of the recorded work context. CHAPTER 42 — Submit completed work for supervisor review Review the instructions, linked asset, saved evidence and resolved issues. Submission should reflect the work actually completed. Select Submit for review. The form shows any remaining completion blockers. Enter a completion note with the checked identifiers and evidence reference. State the limits of the training exercise clearly. Our example names Academy ODF A, position one, and the optical cable’s red fiber in tube one. It refers to the uploaded checklist and makes clear that we reviewed documentation only. The note does not claim a physical inspection or an optical measurement. Submit the work. It is now awaiting the authorized reviewer, not automatically approved. CHAPTER 43 — Return work with a specific correction request We are now Jordan, the responsible Supervisor. Review the frozen scope, completion note and evidence. Approval should be based on the requirements, not simply on the presence of a file. Return to technician is appropriate when clarification or correction is needed. We will demonstrate a specific request before approving the training job. Explain exactly what needs correction. A vague instruction such as fix it does not tell the technician how to complete the review. Confirm the return. The technician can now address the request and resubmit; the work is not completed yet. CHAPTER 44 — Correct the completion note and resubmit Sam reads the supervisor’s correction request. The requested change is a clearer evidence reference, not a new network task. Open Submit for review again and enter a corrected note naming the saved checklist. Resubmit the corrected work. The Supervisor will make a new review decision. CHAPTER 45 — Approve the reviewed inspection and confirm completion Jordan reviews the corrected note and saved checklist against the assigned scope. The evidence reference is now explicit. Select Approve and complete only after the recorded requirements are satisfied. An inspection with no proposed network changes should not alter the existing optical route. Record the basis of the review. This note clearly identifies the fictional nature of the exercise. Confirm approval and verify the job status is Completed. The review decision and responsible person are retained in history. CHAPTER 46 — Review the timeline and reporting options The timeline lets another reviewer follow the job lifecycle. Open it after completion to inspect creation, dispatch, field actions and review decisions. The return and resubmission are part of the work history. A completed status does not erase earlier correction requests. Open the report section. Select the content appropriate for the recipient and check the company identity, job reference, scope, time and evidence. A report summarizes recorded information. It does not turn a fictional checklist into an optical measurement or replace missing field evidence. The next chapters cover supporting tools and company exports, so you can find and preserve the records created throughout this workflow. CHAPTER 47 — Search an asset label and save its real QR files The label library provides stable asset identities. Choose the asset family first, then search for the exact code. A label identifies a record; it does not independently prove that the physical asset matches it. Select ODF, Hub and Network assets, then search for Academy ODF A. Preview the matching label. Check the code and stable identifier before printing or attaching a label to equipment. The preview contains an actual QR image and its payload. The stable identity is separate from the descriptive asset name. Save PDF creates a printable file. We will download it locally and verify that a file was produced. Save QR image creates a vector image for the same identity. Use the correct size and test readability when preparing real labels. Print uses the browser’s printing workflow. Send or share prepares a communication. Check the recipient and asset before sending; this lesson saves files locally. CHAPTER 48 — Company PDF identity and document preferences PDF templates use company identity and document preferences. Review these settings before relying on exported reports for customers. The document company name should match the intended issuer. We will identify the fictional Academy company clearly. Header text can clarify the document context. We will mark our exports as training documents. Footer text can state a useful limitation. Our reports describe fictional records and are not field measurement certificates. The verification QR option applies to supported reports. The preview shows the company identity and retained XANDER signature. Check the presentation against the intended use. Save PDF settings persists the document identity. It does not change the network assets or complete a job. Job order preferences can change display labels for project and reference fields. They do not rename existing database identifiers. Keep labels understandable for both office and field teams. The template library lists registered document types. Sample output checks the common layout; a live module export uses its own current records. CHAPTER 49 — Record a fictional cost entry and inspect the totals Job finances separates actual costs, billable amounts and invoices. Time records and work quantities should be checked before financial totals are used. The amounts in this lesson are fictional examples. Add cost opens a manual entry. A saved company rate can populate recurring values, while manual entry is useful for a specific expense. Cost categories include labor, material, transport, equipment, subcontract, On Call and other costs. We will use Other for this training example. Write a clear description. It should explain the source of the cost, not just say miscellaneous. Unit and quantity determine the amount being counted. We will use one training unit. Actual unit cost and billable unit price are different. We will enter ten for the internal example and zero for the billable amount. Tax must be specified explicitly. Zero here is a fictional test value, not guidance for a real transaction. We will also mark the entry as not billable to the customer. Save the entry and check its description in the cost list. The actual cost changes, while this non billable entry should not become a customer charge. Export CSV downloads the cost list for review. Check currency, quantity and description together. Recorded work shows the underlying work and time sources. Avoid charging the same activity twice through automatic and manual entries. Customer invoices are a separate workflow. Review the customer, selected billable work, dates and applicable tax before issuing a real document. This lesson creates no payment or issued invoice. CHAPTER 50 — Smart Job: precise requests, review and current availability Smart Job can prepare supported network and work actions when AI is configured. This recording uses the published application, and AI execution is disabled inside the isolated training environment. We will show request preparation without pretending a live AI response occurred. Specify the desired outcome and exact identifiers. A network asset request should not be confused with a job order request. Write the asset codes, cable capacity, tube, fiber, endpoint positions and intended route. Clear identifiers reduce ambiguity. Prepare proposal would send the request to the configured service. We will not submit it in this offline training environment. In normal use, review the actual proposed actions and missing information before confirmation. Use voice depends on microphone permission and browser speech support. Review dictated text before submitting, especially asset codes and fiber numbers. This chapter does not simulate microphone input. The New import option provides a separate work request import workflow. Imported files still require review; an extracted value is not proof of a correct assignment. Text, source files and assignment instructions are separate inputs. Local analysis is different from a live AI response, and job preview is different from creating or dispatching work. CHAPTER 51 — Job files, measurements and network research Job Files provides a central place to locate work documents. Use meaningful filenames and the correct job reference so another team member can find the intended evidence. The measurement workspace is separate from ordinary file storage. Real OTDR or iOLM evidence must come from the appropriate instrument and be linked to the correct asset. A sample checklist is not an optical trace. Review supported file formats, measurement identity and linkage before treating a result as network evidence. This course does not invent a measurement. Network research searches recorded assets and evidence. Use exact codes to reduce unrelated results. Review source records behind any result. A search result, generated explanation or map line should not override verified field documentation. Fault location and engineering tools depend on trustworthy route and measurement inputs. Their output is only as meaningful as the supplied data and assumptions. CHAPTER 52 — Communication settings, internal mail and support Communication settings separates in application notifications, email and available delivery options. A company event and a user’s personal notification preference are different settings. Delivery history helps investigate notifications. Provider acceptance is not proof that a person read a message or that it reached the inbox. Internal mail is a separate communication workspace. Check recipients, subject, attachments and the related job before sending. A message does not dispatch, submit or approve a work order. Use the dedicated workflow controls for those state changes. Support requests should describe the page, attempted action, expected result and actual error. Do not include passwords, invitation tokens or service keys. Before reporting a problem, confirm the workspace, role and record identifier. Clear details make it possible to reproduce the issue without guessing. CHAPTER 53 — Partner access and subscription review The company directory and public partner profile describe organizations. A listing is not permission to access another company’s operational records. Partner collaboration requires a defined scope. Check the organization, records, permissions and duration before granting access. Your company’s data remains distinct from a partner’s data. Review the exact shared work rather than assuming a broad partnership makes every file available. Subscription and Billing shows the plan, seats, expiry and applicable agreements. Review the current terms in the application before making a purchase. This tutorial does not purchase a plan or sign an agreement. Operational account permissions and subscription availability serve different purposes. Company data export is separate from ordinary use of a paid workspace. The next chapter demonstrates the export access and archive download. CHAPTER 54 — Download the comprehensive company archive Company data export is a separate access path from ordinary workspace use. It is designed to remain available after subscription expiry for an authorized company account. It does not grant access to another company’s records. Enter the exact company identifier. Export scope follows the authenticated company. Enter an authorized account username. We will use the training Manager. Enter the password and sign in for export. The password remains masked. Review the export explanation before downloading. This comprehensive archive is different from a single job report or asset spreadsheet. Request the archive and wait for the download to finish. Large company archives can take time, so do not assume that clicking the button means the export is complete. Keep the downloaded archive in an approved secure location. Check the manifest and included attachments before relying on it as a retained company copy. A downloaded archive is not an automatic import into another system. If an export reports missing files or incomplete content, retain the warning and resolve the cause. Do not rename an incomplete archive to make it appear complete. CHAPTER 55 — History, archive and how to continue learning History helps explain changes to company records. Use the recorded identities, dates and actions when investigating what happened, rather than relying on memory. Archive is separate from deletion and active operational work. Review linked jobs, routes and files before changing the lifecycle of a real asset. The built in guide provides another reference when you return to a tool. Open it from the help control. We have followed a complete training workflow: registration, people and company setup, customer and site records, network assets and connections, work preparation, personal time, evidence, correction, approval and export. Use the video chapters to repeat the part you need. Pause before a save or confirmation, compare your identifiers, and verify the result after the action. Some capabilities depend on configured external services, actual instruments or field evidence. This course labels those boundaries explicitly. Never treat a fictional tutorial record as an as built measurement or customer installation. Thank you for following the XANDER practical masterclass. Start with a small training workflow, confirm each result, and use your company’s approved process when moving to real operational work.