From first project
to final handoff.

CHAPTER 01

Download, install, and identify RC1

FiberAtlas Beta 2.0 RC1 is a Windows evaluation release for OSP mapping and project documentation. Use a small fictional project while learning. The public Trial lasts 14 days from the original first run on the device.

1. Open https://beta.fiberatlas.app/trial. Enter your name and email, add a company only if you want to, and review the download consent.
2. Request the confirmation email. Open the message from FiberAtlas and use its confirmation link within 30 minutes.
3. After confirmation, download Setup for an installed application or Portable for the portable package. The website download session lasts 24 hours; it is separate from the app's 14-day Trial.
4. Verify the filename, SHA-256, and valid signature against the current download page. The certificate signer is John Philipe Kemmler; ordinary application publisher metadata is FiberAtlas Software.
5. Launch the chosen package. Make any location choice yourself. If location is declined, you can navigate the map manually.
6. Open Help, then About FiberAtlas. Record the app version and build ID before asking for support.

CHAPTER 02

Your first project

This walkthrough creates a small practice record: one handhole, a short distribution route, a named folder, a saved project, and a GIS handoff. It does not create an engineered design.

1. Choose Start New or Create new project. Give it a name such as SYNTHETIC - First practice.
2. Draw a Local Project boundary when offered, or set it later from the Local Project menu. A boundary is optional organizational geometry.
3. Choose a handhole point tool and click a suitable practice location. Return to the Select arrow when finished placing points.
4. Choose Distribution. Click the first route vertex, add at least one more, and press Enter to finish. Select the arrow again when finished drawing.
5. Select the point and route in turn. Give them distinctive names and a short note. Check that the selected record in the tree matches the object on the map.
6. Create an Area or Phase folder from the project tree and review its visibility and membership. Review Project Quantities for the intended scope.
7. Save a permanent .fiberatlas file to local storage. Close normally, reopen that exact file, and confirm the names, route, and note.
8. Export a new KMZ using a deliberate scope and sharing profile. Open the KMZ in the intended recipient's viewer and compare the expected records.

CHAPTER 03

Find your way around the workspace

The map, project tree, and properties panel describe the same active project. Selecting an item should keep its identity clear across those views.

1. Use the project tree to find Local Projects, Areas, Phases, type folders, routes, and assets. Expand the intended branch before editing.
2. Use the Select arrow for navigation and selection. Drawing tools can remain active after placing an object; switch back to Select to avoid placing another one.
3. Use the properties panel to inspect and edit the selected record. Check the name and type before applying an edit.
4. Resize the panels to suit your monitor. Use Map Focus, or Ctrl+Shift+M, to temporarily hide the project and properties panels. Use the same command to return.
5. Open Settings for theme, Comfortable or Compact density, units, language, layout, and recovery preferences. Save settings when you want to keep a change.
6. Use Ctrl+K to focus project-tree search. Enter can act on a single exact result; Escape clears or exits the current search or editing context as appropriate.

CHAPTER 04

Save, reopen, and recover your work

The native .fiberatlas file is the complete working record. A GIS export, printed report, or saved layout is a different kind of output and is not a substitute for a native backup.

1. Use Save or Ctrl+S at meaningful milestones. On a new project, choose a permanent local filename and location.
2. Use Save As or Ctrl+Shift+S to create a deliberate copy before experimenting or making a new revision.
3. Check the status message after saving. A failed or cancelled save does not mean the project is safely on disk.
4. Close the application normally, then use Open or Recent to reopen the exact intended copy. Verify the project identity and important records.
5. Keep independent backups of the native file. Make backup copies when the application is closed or when a successful save has completed.
6. After an interruption, review an offered recovery record before saving it. Preserve the permanent file until you have confirmed which version contains the intended work.

CHAPTER 05

Organize Local Projects, Areas, and Phases

Use hierarchy to keep a working scope understandable. Organizational boundaries and folder membership affect review and output; neither defines a legal or approved service area.

1. Choose the intended Local Project in the project tree. Confirm it is active and writable before adding records.
2. Choose Folder and select Area, Phase, or General Folder as appropriate. Name it for the work you need to review.
3. Open Folder Properties to inspect its type, parent, and visibility. Add a child folder only within a supported hierarchy.
4. Draw, frame, edit, or remove an optional boundary from the folder's controls. Finish a polygon with at least three vertices.
5. Review the actual contents and their folder membership. Hiding a parent hides its descendants from the map.
6. Before printing or exporting, check whether the chosen scope uses an organizational boundary, membership, or visible map content.

CHAPTER 06

Draw and edit points, routes, and boundaries

Create only geometry that you intend to document. The available tool name tells you the record category; the application does not turn that choice into an engineering specification.

1. Select the point tool for the intended asset, then click the map to place it. Add its name and properties and return to Select when done.
2. For a route, choose the category, click successive vertices, and press Enter after at least two vertices to finish. Escape cancels an unfinished draft.
3. Select an existing point to inspect it. Use its supported move action when changing location; cancel if the wrong record is selected.
4. Select a route and use the available vertex-edit or extension controls. Review the whole route after a move, extension, or removal.
5. Use Undo and Redo to review a recent change. Save once the intended geometry and properties are correct.
6. Use the Measure tool for a temporary measurement. Finish it with Enter. A temporary measurement does not create a documented cable route.

CHAPTER 07

Names, properties, styles, and numbering

Keep each record understandable without relying on its color or position alone. Names, notes, types, and status should describe what the user knows.

1. Select an object and confirm its name, type, and project before editing its properties.
2. Record the intended name, status, notes, and supported attributes. Leave an unknown value unknown instead of entering a convenient guess.
3. Use the project's style controls when the map needs a consistent symbol, color, or line treatment. Review a representative point and route after the change.
4. Use numbering controls only after reviewing their scope and preview. Check for duplicate or unintended names before applying.
5. Add photographs or supporting notes deliberately. Review the file and its content before placing it in a record that will be shared.
6. Save, then inspect how the record appears in the tree, quantities, and a representative export or report.

CHAPTER 08

Review route associations and service intent

Map associations, housed equipment, strand-level connections, and intended service assignments answer different questions. Review each in its own controls.

1. Select a route and open Route associations. Choose the Local Project, Area, or Phase scope shown in the panel.
2. Review Direct connections and the identities of the listed point assets. Equipment housed at a connected container may appear beneath that container.
3. Review nearby alignment candidates in an older project before using Align. Use Remove connection when an explicit exception is intended.
4. Select a service endpoint and review its intended assignment. A source, cable-end strand, or port must be chosen explicitly where the workflow requires it.
5. Open the appropriate splice or optical-equipment controls to inspect the actual recorded path. Do not substitute a map association for a strand or port connection.
6. Run a scoped Network Test to compare the reached source with the intended source and review any incomplete, conflict, or wrong-assignment result.

CHAPTER 09

Review lengths, slack, quantities, and conduit

Project Quantities summarizes recorded data in the chosen scope. It is useful for reconciliation, but it does not add engineering allowances or create a procurement order.

1. Open Project Quantities when needed; it starts closed to preserve map space.
2. Choose the intended project or folder scope and review the grouping and visibility rules.
3. Compare point counts and route lengths with the records that contribute. Confirm project distance units before interpreting a number.
4. Review documented slack separately. Total documented cable combines mapped length with slack explicitly allocated to the route.
5. For Conduit, Innerduct, or Microduct, choose a nominal type/size before drawing or leave it Unspecified. Presets include 1.25-inch HDPE, 2-inch HDPE, 4-inch Metal casing, and 4-inch PVC.
6. Use Custom for another documented description, up to 80 characters. Edit an existing route through Route documentation.
7. Review any deliberate option to update unspecified existing routes. Already documented routes keep their values. Save and check the resulting quantity groups and route inventory.

CHAPTER 10

Document equipment and container contents

The equipment workspace distinguishes mapped contents from non-spatial inventory and from explicit optical equipment. Choose the kind of record that matches what you need to preserve.

1. Select a supported host container and open its contents or equipment controls.
2. Review mapped contents separately from non-spatial equipment records. Confirm which host owns the record.
3. Add a catalog item or create a custom equipment type using the available form. Enter a clear name, quantity, and documented attributes.
4. Review a custom type before saving or reusing it. Cancel to discard an unfinished change.
5. For a supported optical host, choose Add optical equipment. Select a suitable generic preset or custom device, and inspect its port count, roles, connector and polish information.
6. Use Splice Lab · Equipment to reopen the host's optical devices. Review each device and its explicitly documented connections before saving the project.

CHAPTER 11

Record optical ports and connections

An optical path needs explicit endpoints and internal relationships. The Inside view is a logical schematic; it is not a physical orientation drawing.

1. Open Splice Lab · Equipment for the intended host and select the exact device.
2. Inspect its port IDs, roles, sides, lanes, connector, and polish information. Confirm the input/common side and intended output branch.
3. Record supported internal paths explicitly. For a splitter, inspect the common-to-branch relationships rather than assuming every visible port is connected.
4. Use the connection controls to choose the exact external endpoints. Review occupied, duplicate, unsupported, or dangling-reference messages.
5. Inspect the Inside view. Use selected-path filtering, fit controls, or larger ports where useful for review.
6. Cancel an unintended draft, or deliberately record the intended change. Save the project and use Network Tests to review the documented path.

CHAPTER 12

Open and prepare the Splicing Laboratory

Start by identifying the case, cable ends, and logical tray. A clean preparation step prevents an attractive diagram from hiding the wrong records.

1. Select the intended splice-capable case or container and open the Splicing Laboratory.
2. Review Identify/setup information. Confirm the selected host and the cable ends actually associated with it.
3. Use the cable browser to inspect recorded use, cable-end identity, fiber count, and any occupied or conflicting positions.
4. Select the first cable end, the logical tray, and the second cable end for the Workbench.
5. Inspect the tube and fiber positions on both cable faces. Check direction and the actual selected range, especially when counts differ.
6. Use the tray controls to select or manage the intended logical tray. Review references before renaming, changing, or removing a tray.
7. Keep Suggested Draft work separate from existing recorded splices. Close or cancel a draft when it is not the intended mapping.

CHAPTER 13

Review a draft and apply splice records

Apply Splices is the deliberate step that records reviewed splice mappings. Selecting strands, creating a suggestion, or saving a project is not the same transition.

1. With the exact cable ends and logical tray selected, create the intended strand mapping using the available Workbench or quick-splice controls.
2. Inspect the visible Suggested Draft. Review its first and last strands, range, direction, and tray.
3. Run or read the review results. Resolve duplicates, occupied positions, exclusions, unsupported connections, and other conflicts.
4. Use draft edit, Undo, Redo, or Cancel controls to adjust or abandon the proposal without presenting it as recorded work.
5. Choose Apply Splices only when the reviewed mapping is the one you intend to record.
6. Reinspect the recorded matrix or cable-use view. Confirm the exact cable IDs, strand pairs, case, and tray.
7. Save the native project to retain the recorded change on disk. Review any installed or field-completion state separately.

CHAPTER 14

Quick Light Trace and Network Tests

Quick Light Trace provides a temporary view of modeled continuity. Network Tests adds explicit scenario, lifecycle, source, direction, and service scope for a repeatable check.

1. On a supported source or service endpoint, use the right-click Quick Light Trace action. Inspect the highlighted modeled route.
2. Click away or press Escape to clear the temporary highlight. This does not alter the project.
3. Open Network Tests and choose Recorded design or draft simulation. Select the current documented design or installed-record scope as appropriate.
4. Choose forward or reverse direction. Select exact source positions and the intended service or folder scope. A folder's service selection can still require upstream paths.
5. Run the check. Review each service's intended and reached source, exact path references, and issue details.
6. Treat cancelled, limited, stale, incomplete, and failed results according to their labels. A green reachability result is not automatically a correct assignment.
7. Use cut-impact or two-snapshot comparison controls only in their explicit read-only simulation/review scope.

CHAPTER 15

Review modeled optical loss

Optical review uses the selected path, wavelength, documented lengths, components, and profile. Its result is separate from modeled connectivity and from measured field evidence.

1. Start with an explicitly scoped Network Test and select the service or branch you want to examine.
2. Choose an optical profile and wavelength. Review the profile's source, revision, applicable components, and stated assumptions.
3. Inspect the path ledger for fiber lengths, component losses, connections, and unsupported or missing values.
4. Review minimum, typical, and maximum calculations only for the inputs actually present. A known subtotal is not a complete end-to-end answer when gaps remain.
5. Enter or select reviewed transmitter, receiver, sensitivity, overload, and criterion data only where you have a valid source.
6. Check the exact branch, direction, wavelength, and reference boundaries before exporting the report or comparing a measurement.

CHAPTER 16

Save and reopen network test history

A saved run captures the source and result used for a completed check. Reviewing it later must not rewrite history to match today's project.

1. Complete the intended Network Test, including any explicit optical profile and packet context.
2. Choose Save test run. Cancelled or limited runs cannot be saved, and read-only projects cannot record a new run.
3. Save the project. Save test run is a project edit, not a replacement for the normal Save command.
4. Open Saved runs and select a run. FiberAtlas checks its stored source and result identities before showing details.
5. Read Same current source snapshot or Historical / stale snapshot. Even a matching source is still a historical result.
6. Expand Snapshot details for scope, source and target IDs, time, application/build identity, and report information.
7. Export the historical packet or matrix from that run when needed. Check the historical label and scope before sharing.

CHAPTER 17

Record measurements and field observations

Field evidence preserves what someone entered or imported. A modeled path, a modeled optical ledger, and a measured observation remain three separate signals.

1. Open Network Tests, choose the intended source/service scope, and select Field evidence.
2. Choose the modeled service if known, or retain an unassociated/incomplete record for later review.
3. Select the measurement method and compatible unit. Enter the value, wavelength, direction, and observation time only when known.
4. Review Path scope, setup & reference planes. Keep source and target boundaries, reference planes, setup identity, and reference method exact.
5. Add operator, instrument model and serial number, calibration reference and due date, and uncertainty when supported by the evidence.
6. Choose a saved profile and explicit owner criterion with its source and revision if a comparison is intended.
7. Review original attachments, provenance, and notes. Compare the draft if useful, then choose Record evidence and save the project.

CHAPTER 18

Import field evidence and retain originals

Use the app's current CSV template. Evidence import is preview-first and must preserve incomplete states and original source information.

1. In Field evidence, choose CSV template. Use the exact current headers rather than rebuilding the schema from memory.
2. Where possible, record and export one example first to obtain valid scope IDs. Do not guess fingerprints or match a path by a display name.
3. Prepare UTF-8 comma-separated data using period decimal separators and properly escaped quoted cells. Keep stable IDs and JSON snapshot cells intact.
4. Use an explicit Z or numeric offset for observation timestamps. If the timezone is unknown, retain the original local text in the supported local-time field and mark its timezone unknown.
5. Choose the CSV and review the preview, samples, and issue list. Fix every blocking issue, including those beyond the displayed detail limit.
6. Cancel without changing the project, or commit the validated batch as one history transaction. Save the project to retain the records and embedded original CSV.
7. Use Export register CSV for record data and snapshots. Use the native project when original attachment bytes must travel with the evidence.

CHAPTER 19

Correct, archive, and share evidence

Preserve the history of a field record. A correction should show what changed without erasing the observation it supersedes.

1. Select the evidence record and inspect its current scope, source, status, and original attachments.
2. Use the correction workflow to create a new record that supersedes the earlier one. Do not import another row with the same ID to overwrite it.
3. Review both the earlier observation and the correction. Keep the original time, source, and provenance understandable.
4. Archive a record when it should no longer be treated as active. Review archive and supersession state in the register.
5. After changing the network or criterion, inspect stale-scope information. A previously matching observation must not silently become current for a different path.
6. Use Save original copy to export a hash-verified original as opaque data. Inspect the intended filename and destination.
7. Save the native project. Before sharing it, review its embedded originals and saved-run history as well as its current map.

CHAPTER 20

Compose map sheets in Print Workspace

Print Workspace prepares presentation and report output from a defined source. Review the source and page scope before refining appearance.

1. Open Print from the intended project, folder, Area, or Phase. Check the source, visible geometry, and any organizational boundary.
2. Choose the required paper size, orientation, and layout. Use fit/reset controls to frame the intended content.
3. Use the sheet controls to include, exclude, reorder, duplicate, or remove pages. Review any index, grid, or corridor output in sequence.
4. Position map and information panels deliberately. Use layout Undo/Redo for presentation changes.
5. Open or save a print layout only for the intended purpose. A layout file is not a native project backup.
6. Review preflight messages and selected report sections before generating a PDF.
7. Open the generated PDF and inspect every page for expected scope, labels, legend entries, units, clipping, overlap, and blank or repeated pages.

CHAPTER 21

Print splice matrices and technical packets

Choose the report that answers the reader's question. A case matrix, a project-wide matrix, and a scoped network packet can cover different records.

1. For a splice matrix, select the exact case or the intended folder/project scope and use its Print Splice Matrix action.
2. Review case IDs, cable ends, logical trays, recorded mappings, exclusions, and conflict disclosures. Keep suggested drafts out of recorded instructions.
3. Use booklet output where offered and inspect its page sequence and scope. Do not assume a booklet implies a particular physical binding or imposition.
4. For a current Network Test, select the report context and choose Packet HTML, CSV, or PDF.
5. For a saved run, export from Saved runs so the packet uses the captured source and remains labeled historical.
6. Open the output and compare a few exact path IDs and matrix references with the source. Review every PDF page before handing it off.

CHAPTER 22

Import and export GIS and project data

Choose an exchange format for its intended content. Native project data, GIS geometry, inventory CSV, evidence CSV, and printed reports are not interchangeable.

1. Preserve the original incoming file. Open Import and choose a supported format, such as KML or KMZ, through the actual menu offered.
2. Review import messages, invalid records, scope, and any loss or compatibility disclosure before committing the result.
3. Inspect names, types, coordinates, folders, style references, and counts in the imported project. Do not assume similar names represent the same stable object.
4. Save a native working copy under a new name after review.
5. Open Export and choose the appropriate output: KML/KMZ, GeoJSON, Shapefile ZIP, supported CSV, or scoped native/project output.
6. Choose Basic Sharing or Full Record detail and Entire Project or Visible Map Content where offered. Review any excluded content.
7. Export to a new filename. Open it in the intended recipient's viewer and compare geometry, names, counts, and expected attributes.

CHAPTER 23

Understand Shared Workspace and read-only files

Shared Workspace organizes separate Work Files and aggregate views. RC1's verified support remains local storage; real shared-drive and multi-workstation use still needs testing.

1. Preserve your local project before opening or creating a Shared Workspace.
2. Inspect the listed Local Projects and Work Files. Distinguish the active writable file from a viewed or read-only file.
3. Refresh status before opening a file for work. Respect a lock or ownership message that identifies another active writer.
4. Use one writer per Work File. Other files can be reviewed read-only without becoming editable copies of the same source.
5. Check which source files are available and included before relying on aggregate quantities or printing.
6. Save the active Work File successfully before switching. If switching stops because saving failed, resolve that save instead of assuming the new file is active.

CHAPTER 24

A structured practice session

Use the application's built-in fictional samples to explore without customer information. You are testing software behavior, not validating a construction design.

1. Save and close your current work. Open Help and choose Open Beta 1.7 network trace sample for a synthetic 100-home exercise.
2. Select a source, inspect exact source positions, and run the recorded-design Network Test. Read assignment details rather than only the total count.
3. Use Quick Light Trace from a service endpoint. Check that clearing the highlight leaves the project unchanged.
4. Open the Splice Lab and review a known mapping. On a saved practice copy, create a draft, inspect it, cancel it, and confirm recorded mappings are unchanged.
5. Use Help's Open Beta 1.8 optical sample for a fictional 32-branch PON. Review the branch, wavelength, profile, and known or missing inputs.
6. Save a completed run, save the project, close normally, reopen that exact copy, and inspect Saved runs.
7. Change one documented input on a further copy and compare its history label. Export a historical packet and confirm it still identifies the original source.
8. Write down one confusing step, missing explanation, or useful result and share it through https://fiberatlas.app/feedback.

CHAPTER 25

Troubleshooting by symptom

Preserve the current file and the smallest reproducible example before changing the environment. A failed operation must not be silently counted as completed.

CHAPTER 26

Keyboard and command reference

These are application-shell shortcuts in RC1. Text fields, open dialogs, the Splice Lab, and Print Workspace can consume keys in their own context.

CHAPTER 27

Terms, file types, and capacity limits

Use the label attached to the result. A number or color without its source and scope is easy to misread.

CHAPTER 28

Get help and give useful feedback

Your practical experience helps decide what to improve. Public Trial users can email feedback without an invitation code.

1. Open https://fiberatlas.app/feedback. Choose a bug, an improvement, or what worked well. The link opens a draft in your email app; you review and send it yourself.
2. If an email app does not open, use your usual email service and address the message to fiberatlasapp@gmail.com.
3. For a reproducible issue, include Help > About version/build, Windows version, display scaling, the task, shortest repeatable steps, expected result, and actual result.
4. Optionally use Help > Report a problem - local file. Choose a type, enter the report, select Review report, then Save local report.
5. Read the local note before attaching it to your message. Add a screenshot only when it is useful and you have reviewed what it reveals.
6. If you are an invited tester, you can also use your existing Beta Hub sign-in for tracked reports and missions.

CHAPTER 29

RC1 scope and documentation record

This manual is the task-first reference for the public FiberAtlas Beta 2.0 RC1 Trial. It is based on the matching release source and retained verification records, with application images labeled by their origin.