Skip to main content

​
Prerequisites

  • The Aerospace Safety Solution is installed and a PowerSheet module exists in your project
  • You have the YAML configuration file name (e.g., Whole RTM Config.yaml) for the module you want to configure
  • You have project administrator access in Polarion

​
Understanding Built-In Views

Each PowerSheet configuration ships with pre-defined views that filter and rearrange columns for specific use cases. The Whole RTM Sheet, for example, includes three views out of the box:
ViewPurposeWhat It Hides
DefaultFull traceability reviewNothing — all columns visible
Without VerificationRequirements-only reviewAll test case columns
SummaryDashboard-style overviewDescriptions and document columns
Specialized sheets such as the DO-160G Environmental Qualification sheet add domain-specific views: Specifications Only, Tests Only, and By DO-160G Section.

​
Step 1 — Open the PowerSheet Module

  1. Navigate to the PowerSheets space in the sidebar.
  2. Open the module you want to configure (e.g., Whole RTM Sheet).
  3. Click Open PowerSheet on the module home page.
The sheet renders dynamically — no work items are stored in the module itself. All data is pulled from the RTM model at render time.

​
Step 2 — Switch Between Views

Once the PowerSheet is open:
  1. Locate the View selector in the PowerSheet toolbar (top-right of the sheet).
  2. Select the view that matches your current task:
    • Use Without Verification when conducting a requirements completeness review — test case columns are hidden to reduce noise.
    • Use Summary when presenting traceability status to stakeholders — descriptions are collapsed for a compact overview.
    • Use Default for full traceability audits before document sign-off.
diagram

​
Step 3 — Collapse Column Groups for Focus

Each requirement level (Customer, System, Subsystem, Design) is organized into a column group. Groups support progressive disclosure:
  1. Click the collapse arrow on a column group header to reduce it to a single summary column.
  2. Expand it again to restore all columns within that level.
This is useful when reviewing a single requirement level — collapse all other groups to stay focused.
Start with the Summary view, then expand only the requirement level you are actively reviewing. This combination gives you the cleanest working surface for level-specific gap analysis.

​
Step 4 — Verify the Module Binding

If a view is missing or columns are not rendering as expected, confirm the module is bound to the correct configuration:
  1. Open the module in Polarion document edit mode.
  2. Check the NextedySheetConfig field — it must reference the exact YAML filename (e.g., Whole RTM Config.yaml).
  3. If the field is empty or mismatched, update it to the correct configuration name and save.
The nextedySheetConfig field value must match the YAML filename exactly, including capitalization and spaces. A mismatch causes the PowerSheet to render with no data or fall back to a default layout that does not match your project’s RTM model.

​
Step 5 — Use Scoped Views for Subsystem Work

When working within a single subsystem, use the Component RTM sheet instead of the Whole RTM Sheet. This sheet applies applyCurrentDocumentTo: SubsystemRequirement, which restricts the view to requirements belonging to the current document only.
  1. Navigate to the relevant subsystem document (e.g., Sensor Interface Module Subsystem).
  2. Open the Component RTM PowerSheet for that document.
  3. The sheet automatically scopes traceability to that subsystem’s requirements — no manual filtering needed.
Loading the Whole RTM Sheet inside a subsystem document will display all requirements across all subsystems. Use the Component RTM configuration when you need document-scoped traceability.

​
Step 6 — Create Test Cases Directly from the Design Verification Sheet

The Design Verification Sheet includes an entity factory that lets you create test cases without leaving the RTM view:
  1. Open the Design Verification Sheet PowerSheet.
  2. Locate a design requirement row with no linked test case.
  3. Click the + cell in the Verification Tests column.
  4. Fill in the test case fields — the new item is created directly in Testing/DesignReqsVerification.
Test cases created through the PowerSheet are saved to the configured Testing module path. They immediately appear in the Verification Tests column and are available for traceability reporting.

​
Verification

You should now see the PowerSheet rendering with the selected view active, column groups collapsing and expanding as expected, and — for scoped configurations — only the requirements belonging to the current document visible in the sheet.

​
See Also

Code: modules/RiskTemplates/DFMEATemplate/module.xml, modules/Risks/DFMEA-CMP-PSU/module.xml, modules/_default/WholeRTMSheet/module.xml, modules/Requirements/CUSTOMER-REQS/module.xml (representative of ~50 module.xml files across all spaces and templates) (0.60) · .polarion/nextedy/sheet-configurations/DO-160G Environmental Qualification.yaml, Component RTM.yaml, Configuration Index.yaml, Design Verification Sheet.yaml, Interface Control Matrix.yaml, Problem Report Tracker.yaml, Process Steps.yaml, Review Action Item Tracker.yaml, SOI Stage Gate Dashboard.yaml, Use Steps Specification.yaml, User Need Validation Sheet.yaml, characteristics.yaml, component-characteristics.yaml, customer-requirements.yaml, design-requirements.yaml, subsystem-functions.yaml, subsystem-verification.yaml, system-elements.yaml, test-verification.yaml (0.51) · .polarion/nextedy/sheet-configurations/Whole RTM Config.yaml (0.46) · .polarion/polarion-project.xml, .polarion/context.properties, .polarion/security/user-roles.xml, .claude/PROJECT.md, TODO.md (0.40) · .polarion/hats/_default/portal/topics.xml, .polarion/hats/admin/portal/topics.xml (0.39) · .polarion/nextedy/sheet-configurations/DO-254 Hardware Design Assurance.yaml (0.39) · modules/Risks/DFMEA-CMP-PSU/attachments/risksheet.json (0.39) · .polarion/pages/spaces/_default/Home/page.xml (0.39) · datasets/sol-aero-ui-walkthrough/summary.md, navigation.md, dashboards/home-dashboard.md, dashboards/role-dashboards.md, dashboards/standards-compliance.md, risksheet-views/risksheet-views.md, work-item-types/data-model.md (0.39) · .polarion/nextedy/sheet-configurations/DO-326A Security Requirements Traceability.yaml (0.38)