Getting Oriented: Your Current DO-254 Landscape

• How often does your hardware team run formal structural coverage analysis during a design iteration? Options: Daily, Weekly, Per-sprint, At major milestones, Rarely or ad hoc
• Tell me about your typical target device types, for example FPGA, ASIC, or PLD, and the DAL levels you most commonly aim for. Options: FPGAs, DAL A, FPGAs, DAL B or lower, ASICs, DAL A, ASICs, DAL B or lower, Mixed targets
• Explain which HDL languages and versioned toolchains your team currently uses for RTL simulation and coverage collection. Options: VHDL toolchain set, Verilog/SystemVerilog toolchain set, Mixed HDL toolchains, Custom or legacy toolchain
• When was the last time a certification authority or DER questioned the sufficiency of tool-generated artifacts on your program? Options: Within the last 3 months, 3 to 12 months ago, Over a year ago, Never for this program
• Which verification artifacts do you already produce automatically, and which still require heavy manual work? Options: Structural coverage reports, Requirements trace matrices, Configuration management records, Test vectors and logs, Most are manual
• Who on your team owns certification evidence readiness and who manages toolchain configuration? Options: Program certification manager, Hardware verification lead, Configuration manager, Shared responsibility, Other
• Describe a recent verification cycle that missed a coverage goal, and why that outcome mattered to schedule or certification risk.

Where verification routinely falls short for you

• What single verification gap, if not closed, would make you pause certification activities immediately? Options: Unproven requirement traceability, Incomplete structural coverage, Non-reproducible build artifacts, Lack of DER-acceptable evidence
• How does that gap manifest in your artifact set, for example missing MC/DC-equivalent analysis, untraceable requirements, or incomplete configuration evidence? Options: Coverage metrics missing areas, Trace links incomplete, Logs not reproducible, Artifact formats rejected by DER
• Give a concrete example of a test case or module that repeatedly causes coverage to stall; what makes it hard to exercise?
• Which roles or teams most often escalate when coverage runs behind, and what do they ask for? Options: Verification engineers request additional harnesses, Design leads request scope reductions, Certification manager requests more evidence, Program management requests schedule relief
• In practice, how many person-weeks does your team spend closing coverage gaps per release on average? Options: Less than 2 person-weeks, 2 to 4 person-weeks, 4 to 8 person-weeks, More than 8 person-weeks
• Who is typically pulled into DER discussions, and how much of their time is budgeted for artifact review? Options: DER and certification manager, limited hours, DER with full-time reviewer for the program, Ad hoc DER involvement, No DER engagement yet
• If your current verification approach stayed the same, what downstream cost or delay would you expect over the next 12 months?

Readiness realities that determine whether we can proceed

• Identify a single infrastructure gap that would block implementation, for example missing HDL toolchain licensing, locked CI access, or lack of a simulation environment. Options: Toolchain licensing, CI access or tokens, Simulation farm capacity, Security or network restrictions, None of the above
• Do you have repository permissions and CI tokens that allow a third party to run verification jobs, and if not, who must authorize them? Options: Yes, pre-approved, No, requires program manager authorization, No, requires procurement, No, cannot be granted
• List the external systems that must integrate, such as your repository hosting, issue tracker, or simulation farm, and whether APIs are available. Options: Git-based repo with API, Proprietary repo without API, Issue tracker with API, Simulation farm with scheduler API, Other
• Estimate how many engineers on your team have both RTL verification skills and DO-254 experience, and are any available as named points-of-contact for the engagement? Options: 0, 1 to 2, 3 to 5, More than 5
• When must regulatory approvals or program-level reviews be completed before we can begin evidence generation? Options: Within 2 weeks, Within 4 weeks, Within 8 weeks, No fixed window
• Rate the cleanliness and traceability of your requirements repository today. Options: Highly traceable and indexed, Mostly traceable with gaps, Fragmented and inconsistent, No formal requirements repository
• Name the owner of configuration management for HDL artifacts, and state whether they enforce reproducible build hashes for each test run. Options: Configuration manager enforces reproducibility, Configuration manager but partial enforcement, No enforcement currently, Not yet defined
• If test data or design files cannot leave your network, what access patterns can you support for on-prem or air-gapped execution? Options: On-prem execution with remote results, On-prem consultant deployment, Air-gapped execution only, We can allow limited outbound artifacts

The other options your program is weighing

• What would have to be true about your current verification approach for you to keep it instead of bringing in an external partner? Options: Lower cost than external, Clear path to meeting DER expectations, Reduced schedule impact, No change required
• Are there any internal proposals to build this capability, and if so, what is the estimated timeline to production? Options: No internal proposal, Proposal exists, timeline < 3 months, Proposal exists, timeline 3 to 9 months, Proposal exists, timeline > 9 months
• List the external options you have evaluated or are evaluating, including in-house toolchains, third-party verification suites, and consulting-only support. Options: In-house build, Third-party verification suite, Consulting services only, Hybrid approach
• Name the incumbent vendor or in-house solution and describe why it remains the default.
• Specify the minimum outcome or metric the incumbent must deliver to keep you from changing vendors. Options: Specific coverage percentage, DER acceptance of artifacts, Reduced manual effort, Lower total cost of ownership
• Would anyone on your engineering leadership team advocate for solving this without an outside vendor, and who is that? Options: Yes, hardware lead, Yes, verification lead, Yes, program manager, No one currently advocating

What certification success will actually look like

• Identify the minimum certification evidence that, if accepted by your DER, would allow program sign-off this quarter. Options: Complete structural coverage report, Requirement traceability matrix, Reproducible configuration artifacts, All of the above
• Describe how you quantify acceptable coverage for the design, for example percentage of code, functional buckets, or structural conditionals.
• Give an example of a previous audit where tool-generated artifacts were accepted or rejected, and what changed as a result.
• On a scale, how important is automated traceability from high-level requirements to test cases for your certification timeline? Options: Critical, Important, Nice to have, Not required
• Estimate how quickly you could produce additional manual evidence if requested by your DER, and what it would cost in person-weeks. Options: Less than 1 person-week, 1 to 4 person-weeks, 4 to 8 person-weeks, More than 8 person-weeks
• Select the acceptance criteria your certification authority emphasizes most: artifact format, traceability, or coverage depth. Options: Artifact format and exportability, Traceability and links, Coverage depth and gap closure, Configuration reproducibility

Decision triggers that change the timeline

• Point to the single pilot metric that would get you to commit within seven days. Options: Achieve target coverage percentage, DER indicates preliminary acceptance, Successful on-prem integration, Reproducible artifacts for audit
• Explain the budget approval process for a pilot or purchase, and who holds the final sign-off authority.
• Provide the stakeholders who must be convinced of ROI: program certification manager, hardware lead, procurement, or other. Options: Program certification manager, Hardware lead, Procurement, Senior program management, Other
• Indicate the number of vendor evaluation cycles you can run in a quarter before program timelines slip. Options: None, 1, 2, 3 or more
• Should a technical blocker appear in the pilot, who has authority to pause integration work and what conditions would trigger a pause? Options: Program manager can pause for safety, Technical lead can pause for unresolved defects, Contractual review required, No formal pause authority

Timing, milestones, and a realistic next step

• Pinpoint the earliest milestone that, if completed within two weeks, would commit your team to a pilot. Options: DER pre-review sign-off, Access to CI and repos granted, Requirements trace matrix available, All test harnesses in place
• Provide the team members who must be available during a two-week pilot and how much time per week they must dedicate. Options: Design lead 4-8 hours/week, Verification lead 8-16 hours/week, Configuration manager 4 hours/week, DER liaison on-call
• Indicate your preferred pilot start window given program constraints and upcoming reviews. Options: Within 2 weeks, Within 4 weeks, Within 8 weeks, Schedule-dependent
• Select the kinds of evidence you would require at pilot completion to consider the pilot successful. Options: Coverage report and gap list, Traceability matrix and proofs, Reproducible build and logs, DER summary memo
• Specify the budget range pre-approved for pilot and initial deployment. Options: Under $25,000, $25,000 to $75,000, $75,000 to $150,000, Over $150,000
• Would you expect the seller to run the pilot remotely, on-premise, or in a hybrid model? Options: Fully remote, On-premise only, Hybrid on-prem and remote, Flexible depending on constraints
• Single out the main risk that would cause you to delay signing after a successful pilot. Options: DER does not accept artifacts, Unresolved reproducibility issues, Security concerns, Budget hold
• Please share the designated contact on your side who will coordinate logistics and approvals for the pilot, including role and preferred communication channel.

• success_criteria
• desired_state
• decision_readiness
• gaps
• stakeholders
• current_state
• decision_readiness
• current_state
• desired_state
• success_criteria
• gaps
• stakeholders
• desired_state
• gaps
• current_state
• success_criteria
• decision_readiness
• stakeholders
• decision_readiness
• decision_readiness
• decision_readiness
• decision_readiness

• Install HDL verification environment
• Integrate with existing HDL simulator
• Configure structural coverage analyzer (VHDL/Verilog)
• Instrument design for FPGA/ASIC coverage collection
• Implement testbench and stimulus libraries
• Execute automated regression test campaigns
• Run structural coverage campaigns and gap tests
• Generate certification‑ready coverage reports
• Trace hardware requirements to test cases
• Automate evidence package generation for audits
• Export configuration‑management and baseline artifacts
• Prepare DER‑facing evidence briefs and certification binder

Install HDL verification environment

• Do you have a preferred sandbox or continuous integration (CI) environment for installing the HDL verification environment? Options: On-prem CI, Cloud CI, Air-gapped lab, No preference
• Provide the operating system and baseline build image for the target installation (for example Linux distro and version).
• List the HDL source repository locations and branch patterns we will need access to (for example repo URLs or internal paths).
• Identify required user accounts or groups and the access approval workflow for the installation hosts and CI runners. Options: You provide accounts and approvals, We provision accounts with approval, TBD
• Specify any airworthiness or network isolation constraints that affect installation (for example no internet access, whitelisted endpoints only). Options: No internet allowed, Limited outbound only, Full internet access allowed
• Confirm the desired delivery artifact for this module (container image, VM snapshot, reproducible install playbook). Options: Container image, VM snapshot, Install playbook, Combination

Integrate with existing HDL simulator

• Which HDL simulator interface(s) must we integrate with (for example command-line invocation, remote simulation endpoint, scripting API)? Options: Command-line invocation, Scripting API, Remote simulation endpoint, Other
• Do you require waveform capture in a specific format for regression artifacts (for example VCD, FSDB, or alternative)? Options: VCD, FSDB, Both, Other
• How many concurrent simulation license seats or simulator nodes are available for regression campaigns? Options: 1-2, 3-5, 6-10, 10+
• Provide the simulator invocation scripts or CI job snippets we should adapt for integration (attach or paste CI job definitions).
• Identify required simulation models we must support during integration (for example behavioral models, SDF timing back-annotation, vendor IP stubs). Options: Behavioral models, SDF timing back-annotation, IP stubs/mocks, Other
• Specify acceptance on successful simulator integration (for example an automated example run, pass/fail exit code, and waveform generation). Options: Automated example run with pass, Pass/fail exit code present, Waveform(s) generated, All of the above

Configure structural coverage analyzer (VHDL/Verilog)

• Which coverage domains do you require enabled for the analyzer (for example statement, branch, condition/toggle, FSM, register-transfer-level)? Options: Statement coverage, Branch coverage, Condition/Toggle coverage, FSM coverage, RTL/register coverage
• List the HDL file patterns and directories to include or exclude from coverage collection (for example /src/core/*.vhd).
• Define target coverage thresholds per module or design partition (for example 95% statement, 100% FSM) that the analyzer should enforce or report against.
• Describe how you expect synthesized netlist coverage versus RTL coverage to be reported (for example separate reports, combined comparison report). Options: Separate reports, Combined comparison report, Side-by-side diff exports
• Indicate file-format outputs required for certification reviewers (for example coverage XML, human-readable PDF, CSV). Options: Coverage XML, PDF report, CSV per-file coverage, Annotated HDL
• Quantify runtime constraints for analysis runs we must observe (for example maximum analysis time per run or memory limits). Options: Under 1 hour per run, 1-4 hours, 4-12 hours, No strict limit

Instrument design for FPGA/ASIC coverage collection

• Detail the HDL modification policy for instrumentation (for example in-place annotations versus a separate instrumented build branch). Options: In-place annotations, Instrumented branch only, Both options allowed
• Who will own instrumented file diffs and review sign-off in your source control management system? Options: You own and review diffs, We create diffs and you review, Shared ownership
• Attach the list of target device identifiers or process nodes that affect instrumentation and probe feasibility (for example specific FPGA families or ASIC technology nodes).
• Where should instrumentation be inserted for gated clocks, reset sequences, and synthesized registers to ensure toggle coverage is meaningful?
• Explain synthesis or implementation constraints we must preserve when producing instrumented netlists (for example SDC constraints, synthesis pragmas to keep).
• Select the preferred instrumentation method for timing-accurate collection on target hardware (for example pre-synthesis instrumentation, post-synthesis probes, or on-FPGA probes). Options: Pre-synthesis instrumentation, Post-synthesis probes, On-FPGA probes, Hybrid

Implement testbench and stimulus libraries

• Confirm whether an existing testbench harness can be extended for this engagement or whether a new harness must be created. Options: Extend existing harness, Build new harness, Partial reuse
• Enumerate existing reusable stimuli and assertion libraries we can consume (provide file paths, repo tags, or manifests).
• Map each stimulus category to the corresponding low-level requirement identifiers in your requirements traceability matrix (RTM).
• Indicate supported testbench languages and interface wrappers required (for example VHDL, SystemVerilog DPI, Python cocotb). Options: VHDL, SystemVerilog, Python cocotb, Mixed-language
• When planning stimulus generation, what reproducibility measures do you require (for example seed logging, recorded playback)? Options: Seed logging, Recorded playback, Both, No reproducibility required
• Who will maintain the baseline stimulus library during the engagement? Options: You maintain, We maintain, Shared maintenance

Execute automated regression test campaigns

• Outline the regression cadence you require (for example nightly, per-commit, or release testing). Options: Per-commit, Nightly, Weekly, Release-only
• How many test cases per campaign do you estimate will run initially and at steady state? Options: Less than 100, 100-1,000, 1,000-10,000, More than 10,000
• Share the CI/CD endpoints and authentication method we should use for job orchestration (for example git hooks, REST API tokens, or service accounts).
• Set acceptable maximum wall-clock time for a full regression cycle before stakeholders are notified. Options: Under 2 hours, 2-6 hours, 6-24 hours, 24+ hours
• Describe the failure triage workflow and required on-call coverage for regression failures (for example SLAs and notification routing).
• Select test parallelization limits based on available compute resources (maximum parallel jobs). Options: 1-5, 6-20, 21-100, 100+

Run structural coverage campaigns and gap tests

• Enumerate the campaign configurations we should run for gap analysis (for example unit-level, integration-level, gate-level).
• Assign the primary owner in your organization for validating coverage gaps against low-level requirements. Options: Verification lead, Requirements owner, Configuration manager, TBD
• Choose the tracking mechanism for uncovered HDL elements (for example defect tracker IDs, spreadsheet, integrated RTM). Options: Defect tracker, Spreadsheet, Integrated RTM, Other
• Set remediation thresholds that will trigger re-instrumentation or additional tests (for example greater than 5 percent uncovered toggles).
• Detail the artifact outputs you expect for each campaign run (for example coverage delta report, per-file coverage CSV, failed testcase logs).
• Estimate the compute hours required for a full gap analysis of the design at its current size. Options: Less than 10 CPU-hours, 10-100 CPU-hours, 100-500 CPU-hours, 500+ CPU-hours

Generate certification‑ready coverage reports

• What acceptance criteria will confirm coverage reports are certification-ready under DO-254 and AC 20-152 (for example output formats, signed reviewer checklist, meeting coverage thresholds)? Options: Coverage files in tool-agnostic format plus PDF, Signed reviewer checklist included, Specified coverage thresholds met, All of the above
• Define the reviewer annotation and signature workflow for the produced PDF binder (for example who signs, required stamps, and timestamp conventions).
• Pinpoint required cross-references between coverage metrics and low-level requirements that must appear in the report (for example RTM links or trace anchors).
• State allowable coverage file formats and tool-agnostic exports for DER review (for example coverage XML, CSV, annotated HDL). Options: Coverage XML, CSV, Annotated HDL, PDF
• Estimate lead time to produce a signed coverage report package after a passing campaign. Options: Less than 3 days, 3-7 days, 7-14 days, More than 14 days
• Clarify who will maintain the canonical signed coverage archive and the retention policy for certification artifacts. Options: We maintain, You maintain, Shared custody

Trace hardware requirements to test cases

• What defines done for requirements-to-test traceability in your DO-254 requirements traceability matrix (for example every low-level requirement linked to at least one test case and coverage evidence attached)? Options: Every LLR linked to at least one test case, 1:1 trace required, Coverage evidence attached is required
• Attach the source documents and version numbers for system requirements, low-level requirements, and architecture documents to import into the RTM.
• Map the expected RTM export formats required for certification review (for example CSV, XML, DOORS export). Options: CSV, XML, DOORS export, Other
• Name the individual or role who will approve trace links during verification cycles.
• Explain how test case identifiers should be embedded in coverage reports and waveform artifacts for unambiguous cross-reference.
• State whether historical test results must be migrated into the RTM and the acceptable completeness threshold for that migration. Options: Full history migration required, Recent N cycles only, No historical migration required

Automate evidence package generation for audits

• Choose which evidence package templates you require (for example DER pre-brief, full certification binder, or per-requirement folders). Options: DER pre-brief template, Full certification binder, Per-requirement folders, Custom template
• Share the signing and version control workflow for generated evidence artifacts (for example who signs, version tags, and checksum methods).
• Outline retention and archival format requirements for audit artifacts (for example digital signatures, PDF/A, archival checksums).
• Pinpoint automation triggers for evidence generation (for example passing campaign, milestone tag, or manual request). Options: Passing campaign, Milestone tag, Manual request
• Calculate storage capacity and access permissions required for generated evidence packages.
• Declare whether DER-facing pre-briefs with executive summaries should be produced automatically. Options: Yes, auto-generate pre-briefs, No, manual only, Conditional - on request

• Master Services Agreement (MSA)
• Statement of Work (SOW)
• Order Form / Subscription Agreement
• Certification Evidence Acceptance Criteria
• Designated Engineering Representative (DER) Engagement Plan
• Data Access and Authorization Agreement
• Data Processing Agreement (DPA) — Regulated Industry Addendum
• Change Order Procedure
• Acceptance & Handover Certificate
• Non-Disclosure Agreement (NDA)

• Go-live Health Check (weeks 1-4)
• First Measurement Review (weeks 4-10)
• Acceptance Gate (around day 90)
• Quarterly Operational Review (ongoing)
• Annual Lessons Learned and Enhancement Planning

• Publish the quarterly metrics dashboard showing trend lines for open DER findings and artifact acceptance rate.
• Record the formal acceptance decision and archive the accepted evidence packet to the agreed evidence repository.
• Create a remediation tracker for any failed or conditional criteria with dates for re-submission of evidence.
• Notify DER and certification stakeholders of the acceptance outcome and next steps for any outstanding findings.
• Metric trend review
• Ensure the count of open DER findings is decreasing toward the target recorded in Outcome Discovery.
• Maintain or improve the evidence artifact acceptance rate and resolve the highest-priority blockers for the next quarter.
• Agree the prioritized enhancement backlog for the next quarter and the criteria for elevating items to remediation workstreams.
• Reconfirm success criteria and owners
• Update the enhancement backlog with priority, estimated effort, and target quarter for delivery.
• Refresh the shared issue channel escalation contacts and SLA expectations document.
• Year-to-date outcome summary
• Confirm the year-to-date evidence acceptance rate meets or documents variance from the Outcome Discovery expectations.
• Document a prioritized enhancement roadmap that addresses the top lessons learned and recurring blockers.
• Ensure the shared issue and enhancement channel has explicit maintainers, SLAs, and an annual review checkpoint.
• Publish the annual lessons learned report with a consolidated list of process and tool changes recommended for implementation.
• Deliver the prioritized enhancement roadmap with estimated timelines and acceptance criteria for each item.
• Confirm and publish the shared channel operating procedure including escalation contacts and response SLAs.
• Confirm the deployment environments and evidence pipelines are functioning end-to-end.
• Agree owners and timelines for any remediation items preventing artifact generation or access.
• Validate that the list of success criteria from Outcome Discovery is complete and specific for measurement.
• Produce a deployment validation report showing environment endpoints, CI job status, and sample evidence artifacts.
• Compile a short issue log for any blockers with target resolution dates and deliver it to the shared channel.
• Publish initial user onboarding checklist and training completion counts for asynchronous review.
• Present first measurement data against targets
• Establish a clear list of remediation actions that will move structural coverage closure percentage toward the Outcome Discovery targets.
• Agree milestone dates and a monitoring cadence that lead into the Acceptance Gate around day 90.
• Confirm artifact formats and traceability exports meet the acceptance expectations captured in Solution Evaluation.
• Deliver a remediation plan listing failing modules, proposed test additions or tool-config changes, and expected coverage uplift by date.
• Publish updated traceability matrix exports and a sample evidence packet for DER review.
• Schedule the Acceptance Gate meeting and circulate the dataset that will be used for the pass/fail decision.
• Restate numeric acceptance criteria
• Produce a documented pass/fail result for each acceptance criterion recorded in Outcome Discovery.
• Capture a named signatory's formal acceptance decision for enterprise governance.
• Agree a remediation and re-evaluation timeline for any conditional or failed criteria.
• Persistent issues and blocker burn-down
• Lessons learned workshop
• Present outcome data for each criterion
• Diagnose root causes for metric gaps
• Deployment and environment validation
• Enhancement request triage
• Document pass or fail per criterion
• Enhancement roadmap alignment
• Agree corrective actions and timeline to acceptance gate
• Smoke test of evidence pipelines
• Shared channel and escalation confirmation
• Early adoption signals and usage patterns
• Confirm evidence format and DER engagement readiness
• Confirm shared issue and enhancement channel health
• Formal acceptance decision and signatory capture
• Blockers, open issues, and immediate remediations
• Agree closure plan for any failing criteria