From corridor to a reviewable railway.

Trainer: allow 2 minutes. Open the designer and a built-in sample before the session. Ask learners what evidence they need to recommend a route. This module is software training, not railway design certification. Screenshots show actual application workflows; older images can have different toolbar layouts. Use the current command labels in the written steps.

Allow 2 minutes. Walk through the stage prerequisites. A compliant calculation is not an approved railway scheme. A missing input cannot be treated as a zero. Distinguish completed software stages from independently approved surveys, clearances and financial decisions.

Allow 2 minutes. Point out the grouped commands in the screenshot, then demonstrate their current positions in the running app. Activity may be indeterminate when an upstream service cannot report a percentage. Do not start the same long operation repeatedly while a request is progressing.

Allow 2 minutes. Open the design limits and show a normal and exceptional limit. Presets are editable starting points. Note that changing a preset may affect derived checks. Confirm units: radius and chainage in metres, speed in km/h, cant in mm, gradient in percent.

Allow 3 minutes. Demonstrate the route workflow with an existing sample so the lesson does not depend on live terrain queries. The older screenshot illustrates a route result and is not evidence that a live service is currently available. Explain why a route can need more development length to achieve the ruling gradient.

Allow 2 minutes. Ask learners to identify a curve and its transition points. Do not equate the design speed with a permitted operating speed. Cant excess on slower traffic and transition comfort criteria can govern even when the radius seems adequate.

Allow 3 minutes. Read a summit or sag, explain VIP and BVC/EVC terminology, and identify the ground profile. A straight line over a missing terrain interval does not create surveyed ground. Check station grades and structure clearances after vertical changes.

Allow 2 minutes. Answers: 7,250 m and 1.25%. Distinguish track gauge from dynamic gauge G in the equilibrium cant equation. A diagram is schematic unless it states a scale. In railway documents always give the unit with a quantity. The project may begin at a nonzero chainage; chainage is not automatically distance from its first point.

Allow 3 minutes. A repair that resolves one rule can worsen another, so rerun the complete checks. Strict mode and project overrides can change the presentation of severity. Review the override register before using a clean report as evidence.

Allow 3 minutes. A generated bridge arrangement is preliminary geometry. Demonstrate how a changed wall or span appears in linked views. Do not describe mapped obstacle levels or proposed support sizes as approved design inputs.

Allow 2 minutes. The screenshot shows the visible portion of an A1 preview, not a complete structural calculation. Drawing dimensions remain numerical facts; a scaled measurement is only valid at the specified print size. Export a reviewed sheet for the class to inspect.

Allow 3 minutes. Explain a component, a plan head and a bill item using the visible editor. The imported or detailed bill is a saved snapshot; changing the alignment does not automatically certify or reconcile every measured quantity. Review charges and GST separately.

Allow 2 minutes. Ask learners to calculate one simple row independently. A rate source is not a locally approved price. Explain that exporting the editor draft can differ from a report built from the applied project snapshot. Check the save destination and date.

Allow 3 minutes. The actual editor shows a 300 m by 10 m island-platform schematic at 20° rotation. Its dedicated geometry and annotation layers remain editable. CAD supports annotations, layout development and exchange; drawing entities do not change the solved railway alignment or its quantities. Save project retains the drawing. Import DXF / DWG is explained in the next lessons.

Allow 3 minutes. Search by component or filter a family. The preview is regenerated from parameter values and extents include annotations. Geometry is in metres; gauge fields use labelled millimetres and paper frames use an explicit 1:N scale. Each insertion is independent editable geometry, not a linked block or live engineered model. Turnouts are schematic rays, clearance envelopes are user studies, and structural outlines are not capacity calculations. Complete the applicable design before adopting a drawing.

Allow 2 minutes. This actual local DWG import expanded three INSERT references and reported sheared and mirrored text approximations. Conversion occurs in the packaged WebAssembly adapter. Supported planar ellipses, splines and hatch loops can remain editable; nested blocks, arrays, dimension graphics and multiline text are flattened. Block and dimension associations are not retained. Three-dimensional solids, meshes, external references and proxy objects are outside the editing model. Conversion warnings and font/layout differences still require review when no entities are skipped.

Allow 3 minutes. The project deck is a technical review starting point, not a claim of a prescribed Indian Railways PEC template or sanction. Confirm every exported figure matches the adopted alternative and cost basis. Add scheme-specific approvals, financing and economics where they are not in the model.

Allow 2 minutes. Railway corporate, Executive review, Infrastructure delivery, Landscape and sustainability, Technical submission, and Print and tender change the applicable covers, headings, tables and infographic treatment. Feasibility and DPR offer Word or PDF in the publication dialog. EPC is Word; tender schedules are Excel with coordinated typography and palette. The selector retains its choice while that dialog remains open, then defaults to Railway corporate next time. It is not a saved project preference. The miniature preview is illustrative and does not contain the project’s quantities. The exports remain review documents requiring the same evidence and completion regardless of layout.

Allow 3 minutes. Examples include employer identity, completion period, securities, eligibility, payment terms and adopted contract conditions. An automatically prepared workbook or Word document is an editable draft. The chosen zonal tender and contract documents govern; verify schedule lettering and prescribed formats for the actual invitation.

Allow 2 minutes. Desktop file icons come from the installed operating-system association; a project file cannot force a custom icon on an unconfigured machine. Mac and Windows keyboard shortcuts differ. A file export is distinct from a cloud save. Keep a dated backup before material revisions.

Allow 5 to 10 minutes as a separate exercise after the teaching module if required. Use demonstration data and label all outputs training. Assessment: can another engineer trace the route, quantities, assumptions and missing approvals? Review shared outputs before describing them as ready for an employer.

Allow 2 minutes. Answers: no, no, no. A compliance report applies the configured rules and cannot replace scheme approval. A saved bill may be a fixed snapshot and needs deliberate revision. Employer and tender-specific conditions require authorised completion and review. Discuss a useful next check for each case.

Allow 1 minute. The manual page is the maintained source. PDF is generated from that page at print time; retain the edition and date with a review package. Use the trainer notes and exercise as a repeatable onboarding session. Ask each learner to name one issue they will verify on their next project.