Runfile List
Version: v3.0.0 Status: Normative (text), Illustrative (diagrams only) Scope: Viewing, searching, filtering, and navigating processed run files Domain: RUNFILE
Statement
The system shall provide a list-based interface for viewing, searching, filtering, and navigating runfiles that have been processed by the system.
This domain encompasses list presentation with pagination, data retrieval with configurable filtering and sorting, row expansion for viewing mix details, navigation to detailed run reports, and multi-site operation for deployments with multiple laboratory sites.
Behavior Overview (Illustrative)
This diagram illustrates the high-level behavior. It does not specify UI layout, styling, or interaction details.
Definitions
| Term | Definition |
|---|---|
| Runfile | A processed file from a thermocycler containing well data, targets, and mixes |
| Mix | A configured combination of targets and dyes for an assay; runfiles contain one or more mixes |
| Run Status | The aggregate export readiness state of all patient wells in a runfile |
| Resolution Pending | A state indicating wells have errors requiring user resolution before export |
| Archive Tag | A tag designation that moves a runfile from active views to the archived view |
Functional Requirements
List Display (REQ-RUNFILE-001)
FR-RUNFILE-001 Display Runfile List
The system shall display a list of runfiles in tabular format showing relevant metadata for each runfile.
Acceptance Criteria:
Display Content:
- Display runfile metadata including: upload date, modification date, file name, mixes, notifications, run status, resolution pending status, uploader, run creation date, and plate size
- Display mixes in the order defined in Kit Configuration
Pagination:
- Provide pagination controls for navigating large result sets
- Display the current range and total count of runfiles (e.g., "Showing 21-30 of 100")
Refresh:
- Allow users to refresh the list while preserving current filter and sort settings
Error Handling
- No runfiles exist: Display an empty state message
- Data retrieval fails: Display an error message and allow retry
Trace: Source: 3.0.0-Runfile List (Row 2, 3, 20, 23, 24), 3.0.0-Run Files - Ordering Mixes list | Jira: BT-2809, BT-668 | Tests: See scenarios
Row Expansion (REQ-RUNFILE-002)
FR-RUNFILE-002 Expand Runfile to View Mix Details
The system shall allow users to expand a runfile row to view detailed information about the mixes contained within that run.
Acceptance Criteria:
Expansion Behavior:
- Expanded view shall display mix details: Mix name, number of targets, number of wells, number of samples, notifications
- Multiple runfile rows may be expanded simultaneously
- An expanded row shall provide a control to collapse it
State Constraints:
- An already-expanded row shall not offer an expand action
- A collapsed row shall not offer a collapse action
Patient Search Context:
- When accessed via Search Patients, the expanded view shall show Well, Mix, Outcome columns instead of standard mix details
Trace: Source: 3.0.0-Runfile List (Rows 4-12) | Jira: BT-2809, BT-144 | Tests: See scenarios
Search and Filter (REQ-RUNFILE-003, REQ-RUNFILE-004)
FR-RUNFILE-003 Search Runfiles
The system shall allow users to search runfiles by patient identifier or run file name.
Acceptance Criteria:
Search Modes:
- Search by patient identifier shall use exact match
- Search by run file name shall use partial match
Results Behavior:
- Search results shall display only runfiles matching the search criteria
- When no search text is entered, all runfiles matching other filters shall be displayed
- When accessed via patient search, expanded view shall show well-level details (Well, Mix, Outcome) instead of standard mix details
Trace: Source: 3.0.0-Runfile List (Rows 13, 14) | Jira: BT-144, BT-668 | Tests: See scenarios
FR-RUNFILE-004 Filter Runfile List
The system shall allow users to filter the runfile list by multiple criteria to narrow displayed results.
Acceptance Criteria:
Date Range Filters:
- Support date range filtering on: Uploaded Date, Modified Date
Discrete Value Filters:
- Support discrete value filtering on: Mix, Westgard Status, Resolution Pending Status, Uploaded By
- Multiple filter values may be selected simultaneously within a single filter
- Multiple filters may be applied in combination
Filter Visibility:
- Allow users to toggle filter visibility without clearing active filters
- Filter visibility state shall default to shown
Trace: Source: 3.0.0-Runfile List (Rows 15, 16, 19) | Jira: BT-668 | Tests: See scenarios
Sorting (REQ-RUNFILE-005)
FR-RUNFILE-005 Sort Runfile List
The system shall allow users to sort the runfile list by specified columns.
Acceptance Criteria:
Sortable Columns:
- Sortable columns shall include: Date Uploaded, Date Modified, Uploaded By
Default Behavior:
- Default sort shall be Date Uploaded in descending order (newest first)
Sort Interaction:
- Repeated activation of sort on a column shall toggle between ascending and descending
- The system shall indicate the current sort column and direction
- Only one column may be sorted at a time
Trace: Source: 3.0.0-Runfile List (Row 17) | Jira: BT-668 | Tests: See scenarios
Navigation (REQ-RUNFILE-006)
FR-RUNFILE-006 Navigate to Run Report
The system shall allow users to navigate from the runfile list to the detailed run report for a selected runfile.
Acceptance Criteria:
- Selecting a runfile row (excluding expand control) shall navigate to the run report
- The navigation context shall indicate the currently selected run
Trace: Source: 3.0.0-Runfile List (Rows 21, 22) | Jira: BT-2809 | Tests: See scenarios
Customization (REQ-RUNFILE-007)
FR-RUNFILE-007 Configure Visible Columns
The system shall allow users to configure which columns are visible in the runfile list.
Acceptance Criteria:
- The system shall provide a mechanism to toggle column visibility
- All columns shall be visible by default
Trace: Source: 3.0.0-Runfile List (Row 25) | Jira: BT-2702 | Tests: See scenarios
Status Display (REQ-RUNFILE-008)
FR-RUNFILE-008 Display Run Status
The system shall display the current processing and export status for each runfile.
Acceptance Criteria:
Status Values:
- Run Status shall indicate "All wells ready for export" when all patient wells have no errors
- Run Status shall indicate "Some wells ready for export with errors to resolve" when at least one patient well has an error AND at least one can be exported
- Run Status shall indicate "No export - errors to resolve" when at least one patient well has an error AND none can be exported
- Run Status shall indicate "All wells exported" when all patient wells have been exported
- Run Status shall indicate Westgard-related status when applicable (e.g., "Reanalysis required")
Trace: Source: 3.0.0-Runfile List (Row 26) | Jira: BT-3247 | Tests: See scenarios
Multi-Site Operation (REQ-RUNFILE-009)
FR-RUNFILE-009 Support Multi-Site Operation
The system shall support viewing and managing runfiles across multiple sites for users with appropriate permissions.
Acceptance Criteria:
Manager Capabilities:
- Manager users shall be able to filter runfiles by site
- Manager users shall be able to view the site where each runfile was created
Super-Admin Capabilities:
- Super-admin users shall be able to view and select the current site
- Super-admin users shall be able to enable or disable sites
Access Control:
- Users shall not be able to log in to a disabled site
- Non-manager users shall not see site-related functionality
Assumptions:
- Multi-site feature is enabled for the deployment
- At least two sites are configured
Trace: Source: 3.0.0-Runfile List (Rows 27-33) | Jira: BT-3035 | Tests: See scenarios
Tagging and Archive (REQ-RUNFILE-010, REQ-RUNFILE-011)
FR-RUNFILE-010 Manage Run Tags
The system shall allow users to attach, view, and manage tags on runfiles for organization and archival purposes.
Acceptance Criteria:
Tag Display:
- Tags attached to a run shall be visible in the runfile list
Tag Application:
- Users shall be able to attach one or more tags to a run
- Applying new tags shall replace existing tags on the selected run(s)
Bulk Operations:
- When multiple runs are selected and tags applied, the system shall confirm the scope of the operation
- When applying tags to multiple selected runs, the scope confirmation shall offer options: "Apply only one" (applies to initiating row only), "Confirm" (applies to all selected), "Cancel" (no changes)
Archive Visibility:
- When Archive Mode is enabled, users shall be able to toggle visibility of archived runs
Assumptions:
- Tags are configured in the system before use
- Archive Mode configuration exists in client settings
Trace: Source: 3.0.0-Run File List - Attach Run Tags (all rows) | Jira: BT-4300 | Tests: See scenarios
FR-RUNFILE-011 Organize Runfiles into Categorized Views
The system shall organize runfiles into categorized views based on their archival and export state.
Acceptance Criteria:
- Active Runs view shall display runs that are not archived and not fully exported
- Exported Runs view shall display runs that are not archived and fully exported
- Archived Runs view shall display runs with archive tags
Trace: Source: 3.0.0-Separate Run Tabs (all rows) | Jira: BT-4488 | Related: BT-4487 (Epic) | Tests: See scenarios
Non-Functional Requirements (NFR-RUNFILE-001)
NFR-RUNFILE-001 Performance
The system shall meet performance requirements for runfile list operations.
Acceptance Criteria:
- Initial screen population shall complete within acceptable response time
- Screen repopulation after user actions shall complete within acceptable response time
- The interface shall adapt responsively when the viewport is resized
Open Questions:
| ID | Question | Resolution |
|---|---|---|
| OQ-01 | What are the specific acceptable response time thresholds? | Use NFRs (see REQ-NFR-001 for 10-second page load threshold) |
Trace: Source: 3.0.0-Runfile List (NFR Rows 2-4) | Jira: [Pending] | Tests: [Pending]
Configuration Options
| Option | Default | Description | Affects |
|---|---|---|---|
default_filter_visibility | shown | Default visibility state for filter section | FR-RUNFILE-004 |
archive_mode_enabled | false | Whether archive mode and archive toggle are available | FR-RUNFILE-010, FR-RUNFILE-011 |
default_sort_column | date_uploaded | Default sort column for runfile list | FR-RUNFILE-005 |
default_sort_direction | descending | Default sort direction for runfile list | FR-RUNFILE-005 |
items_per_page | [TBD] | Default pagination size | FR-RUNFILE-001 |
Assumptions
- Users accessing this domain have at minimum Junior User role permissions
- At least one runfile has been imported and processed before accessing this screen
- Site configuration is complete for multi-site deployments
- Mixes referenced in runfiles exist in the Kit Configuration
UI Notes (Illustrative)
FR-RUNFILE-001 UI Specifications
Screen Layout:
- Top section: Title ("Run Files"), Filter toggle button, Refresh button
- Second section: Filters and item count display ("Showing X - Y out of Z")
- Third section: Runfile table
- Bottom section: Pagination controls
Display Format:
- Item range display format: "Showing 21 - 30 out of 100"
- Page header displays "Run Files" as title
FR-RUNFILE-002 UI Specifications
Visual Indicators:
- Expand indicator: "+" icon on unexpanded rows
- Collapse indicator: "-" icon on expanded rows
- Visual distinction between expand action (viewing mixes) and row selection (navigating to run report)
Interaction:
- Clicking "+" expands the row to show mix details
- Clicking "-" collapses the expanded row
- Expand/collapse control is in a dedicated column
FR-RUNFILE-004 UI Specifications
Filter Toggle:
- Button labeled "Show/Hide Filters" controls filter visibility
- Default state: filters shown
FR-RUNFILE-006 UI Specifications
Navigation Indicator:
- Selected run name appears as a child item under "Run Files" in the left navigation menu
- Provides visual context for current navigation state
FR-RUNFILE-009 UI Specifications
Multi-Site Display:
- Super-admin users see site dropdown between username and settings button
- Dropdown shows current site name with list of other enabled sites
- Manager users see Site filter (dropdown, multi-select) and Site column
Implementation (Illustrative)
| Component | Type | Location | Requirements |
|---|---|---|---|
| Run | Model | code/app/Run.php | FR-RUNFILE-001, FR-RUNFILE-008, FR-RUNFILE-010 |
| Well | Model | code/app/Well.php | FR-RUNFILE-008 |
| GetRunStatus | Service | code/app/GetRunStatus.php | FR-RUNFILE-008 |
| RunsController | Controller | code/app/Http/Controllers/RunsController.php | FR-RUNFILE-001, FR-RUNFILE-003, FR-RUNFILE-004, FR-RUNFILE-005 |
| WellsController | Controller | code/app/Http/Controllers/WellsController.php | FR-RUNFILE-008 |
| RunAnalyseJob | Job | code/app/Jobs/RunAnalyseJob.php | FR-RUNFILE-001 |
| RunUpdateJob | Job | code/app/Jobs/RunUpdateJob.php | FR-RUNFILE-001 |
| RunDeleteJob | Job | code/app/Jobs/RunDeleteJob.php | FR-RUNFILE-009 |
| RunAnalyzeStarted | Event | code/app/Events/RunAnalyzeStarted.php | FR-RUNFILE-001 |
| RunAnalyseProgressUpdated | Event | code/app/Events/RunAnalyseProgressUpdated.php | FR-RUNFILE-001 |
| RunUpdated | Event | code/app/Events/RunUpdated.php | FR-RUNFILE-001, FR-RUNFILE-010 |
| RunsDeleted | Event | code/app/Events/RunsDeleted.php | FR-RUNFILE-009 |
Frontend (Illustrative):
| Component Type | Location |
|---|---|
| View | views/Runs.vue |
| View | views/RunFilesTable.vue |
| View | views/Tags.vue |
| Components | components/runs/ |
| Components | components/run-files/ |
Traceability Matrix
| Requirement | Title | Verification | Implementation | Test Cases | Status |
|---|---|---|---|---|---|
| REQ-RUNFILE-001 | Display Runfile List | Test | Run, RunsController, Events | BT-601, BT-603 | Draft |
| REQ-RUNFILE-002 | Expand Runfile to View Mix Details | Test | Frontend | BT-601 | Draft |
| REQ-RUNFILE-003 | Search Runfiles | Test | RunsController | BT-602 | Draft |
| REQ-RUNFILE-004 | Filter Runfile List | Test | RunsController | BT-602 | Draft |
| REQ-RUNFILE-005 | Sort Runfile List | Test | RunsController | BT-601 | Draft |
| REQ-RUNFILE-006 | Navigate to Run Report | Test | Frontend | BT-603 | Draft |
| REQ-RUNFILE-007 | Configure Visible Columns | Test | Frontend | BT-601 | Draft |
| REQ-RUNFILE-008 | Display Run Status | Test | GetRunStatus, Well | BT-3684 | Draft |
| REQ-RUNFILE-009 | Support Multi-Site Operation | Test | Run, RunDeleteJob | [Pending] | Draft |
| REQ-RUNFILE-010 | Manage Run Tags | Test | Run, RunUpdated | [Pending] | Draft |
| REQ-RUNFILE-011 | Organize Runfiles into Categorized Views | Test | Run | [Pending] | Draft |
| NFR-RUNFILE-001 | Performance | Test | [TBD] | [Pending] | Draft |
Notes
- Notifications column behavior is defined in the Notifications requirements domain
- Westgard status values and reanalysis behavior are defined in the Westgard/QC requirements domain
- Mix ordering follows the sequence defined in Kit Configuration (Mixes and Targets screen)
Open Questions
| ID | Question | Source | Owner | Date Raised |
|---|---|---|---|---|
| OQ-001 | Confirm response time thresholds for NFR-RUNFILE-001 | NFR Rows 2-4 | @SME-TBD | TBD |
| OQ-002 | Items per page default value needs confirmation | Configuration | @SME-TBD | TBD |
Acceptance Tests
Test: REQ-RUNFILE-001
Test: Verify page sections
Given: User navigates to the Run Files screen
When: The screen loads
Then: The screen shall display title and controls in the top section
And: The screen shall display filters and item count in the second section
And: The screen shall display the runfile table in the third section
And: The screen shall display pagination controls at the bottom
Test: Verify table columns
Given: User is on the Run Files screen
When: User observes the runfiles table
Then: The table shall display columns: Date Uploaded, Date Modified, Run File Name, Mixes, Notifications, Westgard Status, Resolution Pending Status, Uploaded By, Run Creation Date, Plate Size
Test: Verify mix ordering
Given: Run A contains Mix-C, Mix-A, Mix-B
And: Kit Configuration defines order as: Mix-A, Mix-B, Mix-C
When: User views the Run Files screen
Then: Run A shall display mixes as: Mix-A, Mix-B, Mix-C
Test: Verify refresh preserves state
Given: User is on Run Files screen with filters and sort applied
When: User activates refresh
Then: The table data shall be reloaded
And: Filter selections shall be preserved
And: Sort order shall be preserved
Test: REQ-RUNFILE-002
Test: Expand run
Given: User is on the Run Files screen
When: User expands a runfile row
Then: The expanded section shall display columns: Mix, No of Targets, No of Wells, No of Samples, Notifications
Test: Collapse run
Given: A runfile row is expanded
When: User collapses the row
Then: The expanded section shall be hidden
Test: Expand multiple rows
Given: User is on the Run Files screen
When: User expands multiple runfile rows
Then: All selected rows shall display their expanded sections simultaneously
Test: Cannot re-expand
Given: A runfile row is already expanded
When: User observes the expand control
Then: The expand action shall not be available for the already expanded row
Test: Expand from patient search
Given: User found a run using patient search
When: User expands the runfile row
Then: The expanded section shall display columns: Well, Mix, Outcome
Test: REQ-RUNFILE-003
Test: Search by patient identifier
Given: User is on the Run Files screen
When: User enters a patient identifier in the patient search field
Then: The system shall display only runfiles containing the exact patient identifier
Test: Search by run name
Given: User is on the Run Files screen
When: User enters a partial run name in the run search field
Then: The system shall display runfiles with names containing the search text
Test: REQ-RUNFILE-004
Test: Filter by date
Given: User is on the Run Files screen
When: User applies an Uploaded Date filter with a date range
And: User applies a Modified Date filter with a date range
Then: The system shall display only runs matching both date filters
Test: Filter by discrete values
Given: User is on the Run Files screen
When: User applies Mix filter with selected values
And: User applies Westgard Status filter with selected values
And: User applies Resolution Pending Status filter with selected values
And: User applies Uploaded By filter with selected values
Then: The system shall display only runs matching all selected filter values
Test: Show/hide filters
Given: Filters are visible on the Run Files screen
When: User activates the filter visibility toggle
Then: The filter section shall be hidden
When: User activates the filter visibility toggle again
Then: The filter section shall be visible
Test: REQ-RUNFILE-005
Test: Default sort
Given: User navigates to the Run Files screen
When: The screen loads
Then: The table shall be sorted by Date Uploaded in descending order (newest first)
Test: Toggle sort
Given: User is on the Run Files screen
When: User activates sort on the Date Uploaded column
Then: The table shall sort by Date Uploaded in ascending order
When: User activates sort on the Date Modified column
Then: The table shall sort by Date Modified
And: Repeated activations shall toggle between ascending and descending
Test: REQ-RUNFILE-006
Test: Open runfile
Given: User is on the Run Files screen
When: User selects a runfile row (not the expand control)
Then: The system shall navigate to the run report for that runfile
Test: Navigation context shows run name
Given: User has navigated to a run report
When: User observes the navigation menu
Then: The selected runfile name shall appear as a child item under Run Files
Test: REQ-RUNFILE-007
Test: Hide columns
Given: All columns are visible on the Run Files table
When: User opens column configuration
And: User deselects certain columns
And: User confirms the selection
Then: The deselected columns shall be hidden from the table
Test: REQ-RUNFILE-008
Test: Run status values
Given: User is on the Run Files screen
When: A runfile has all patient wells without errors
Then: Run Status shall display "All wells ready for export"
When: A runfile has all patient wells exported
Then: Run Status shall display "All wells exported"
When: A runfile has some errors but at least one exportable well
Then: Run Status shall display "Some wells ready for export with errors to resolve"
When: A runfile has all patient wells in error
Then: Run Status shall display "No export - errors to resolve"
Test: Westgard reanalysis status
Given: Run #1 with 1:2s error (latest date) is imported
And: Run #2 with 1:2s error (earliest date, same patient/mix/control) is imported
When: User opens first imported file and skips auto reanalysis
Then: PC outcome shall be "Control Passed"
When: User activates reanalysis
Then: PC outcome shall change to "Previous westgard fail"
Test: REQ-RUNFILE-009
Test: Manager site filter
Given: User is logged in as a manager
When: User observes the Run Files screen
Then: A Site filter shall be available
And: A Site column shall be visible
Given: User is logged in as junior or senior user
When: User observes the Run Files screen
Then: No Site filter or Site column shall be visible
Test: Super-admin site switching
Given: User is logged in as Super-Admin
When: User observes the application header
Then: A site selection control shall display the current site
When: User activates the site selection
Then: A list of available enabled sites shall be displayed
When: User selects a different site
Then: The selected site shall become the current site
Test: REQ-RUNFILE-010
Test: Tag visibility
Given: Run A has tags: Tag A, Tag B
When: User views the Run Files table
Then: The Tags column for Run A shall display "Tag A, Tag B"
Test: Attach tags
Given: Run A exists with no tags
And: Tags Tag A and Tag B are configured
When: User selects Tag A from the tags control for Run A
Then: Run A shall be saved with Tag A
Test: Bulk tag warning
Given: Run A and Run B exist
And: Tags Tag A and Tag B are configured
When: User selects Run A and Run B
And: User applies Tag A and Tag B on Run A
Then: The system shall display a scope confirmation prompt
When: User selects "Apply only one"
Then: Run A shall have Tag A, Tag B and Run B shall have no tags
When: User selects "Confirm"
Then: Both Run A and Run B shall have Tag A, Tag B
When: User selects "Cancel"
Then: Neither run shall have tags applied
Test: Archive toggle
Given: Archive Mode is enabled in client configuration
Then: An archive visibility toggle shall be available
Given: 5 runs with archive tags and 5 runs without archive tags exist
When: Archive visibility is disabled
Then: Only the 5 non-archived runs shall be visible
When: Archive visibility is enabled
Then: All 10 runs shall be visible
Test: REQ-RUNFILE-011
Test: Tab filtering
Given:
- Run A: has archive tags, has exported wells
- Run B: has archive tags, no exported wells
- Run C: no archive tags, has exported wells (fully)
- Run D: no archive tags, no exported wells
When: User views the Active Runs view
Then: Only Run D shall be visible
When: User views the Exported Runs view
Then: Only Run C shall be visible
When: User views the Archived Runs view
Then: Run A and Run B shall be visible
Related Design Documents
| Design Document | Relevant Sections |
|---|---|
| SDD Architecture | High-level ERD, Well State Model |
| SDD Algorithms | Run Status Calculation |
Appendix: Process Artifacts
Completion Checklist
- All requirements are capability-level (describe behavior, not UI)
- Requirement variants consolidated (no requirement explosion)
- UI details are fully demoted to Illustrative section
- Configuration options are not encoded as requirements
- Acceptance criteria describe behavior, not UI mechanics
- Every requirement has acceptance criteria and source traceability
- Error handling addressed for I/O, validation, and external system requirements
- Open questions documented with owners assigned
- Consolidations documented in Reviewer Notes with reversibility info
- Module can survive a full UI redesign unchanged
- Refinements do not introduce new capabilities
- Traceability matrix is complete
Reviewer Notes
Consolidation: REQ-RUNFILE-003
The following items from the source were consolidated into a single capability-level requirement:
| Original Item | Source Reference | Disposition |
|---|---|---|
| REQ-RUNFILE-003 (Search by patient) | 3.0.0-Runfile List (Row 13) | Merged -> FR-RUNFILE-003 AC (Search Modes) |
| REQ-RUNFILE-004 (Search by run name) | 3.0.0-Runfile List (Row 14) | Merged -> FR-RUNFILE-003 AC (Search Modes) |
Rationale: Both items represent variants of a single search capability that differ only by search field and match type. Consolidation aligns with Phase 0 guidance on avoiding requirement explosion for interaction variants.
Reversibility: To restore original structure, reference:
- Source:
output/pilot/restructured/runfile-list.md - Confluence: 3.0.0-Runfile List (Rows 13-14)
Consolidation: REQ-RUNFILE-001 (Refresh)
The following item from the source was consolidated:
| Original Item | Source Reference | Disposition |
|---|---|---|
| REQ-RUNFILE-007 (Refresh list) | 3.0.0-Runfile List (Row 18) | Merged -> FR-RUNFILE-001 AC (Refresh) |
Rationale: Refresh is a convenience interaction on the list display, not a separate system capability. It describes how the list maintains state during data reload, which is an aspect of list display behavior.
Reversibility: To restore original structure, reference:
- Source:
output/pilot/restructured/runfile-list.md - Confluence: 3.0.0-Runfile List (Row 18)
ID Renumbering
Due to consolidations, the following IDs were renumbered from the source:
| Source ID | New ID | Reason |
|---|---|---|
| REQ-RUNFILE-003 | REQ-RUNFILE-003 | Retained (consolidated with 004) |
| REQ-RUNFILE-004 | (consolidated) | Merged into REQ-RUNFILE-003 |
| REQ-RUNFILE-005 | REQ-RUNFILE-004 | Renumbered |
| REQ-RUNFILE-006 | REQ-RUNFILE-005 | Renumbered |
| REQ-RUNFILE-007 | (consolidated) | Merged into REQ-RUNFILE-001 AC |
| REQ-RUNFILE-008 | REQ-RUNFILE-006 | Renumbered |
| REQ-RUNFILE-009 | REQ-RUNFILE-007 | Renumbered |
| REQ-RUNFILE-010 | REQ-RUNFILE-008 | Renumbered |
| REQ-RUNFILE-011 | REQ-RUNFILE-009 | Renumbered |
| REQ-RUNFILE-012 | REQ-RUNFILE-010 | Renumbered |
| REQ-RUNFILE-013 | REQ-RUNFILE-011 | Renumbered |