Verification methodology
How we verify every part in your BOM
Each part is resolved to its real manufacturer, traced to dated origin evidence, screened with its ownership chain against federal restrictions, and delivered in an assessor-ready validation workbook with a source behind every finding, plus an official compliance certification for Drone NDAA and C-UAS.
The four-stage verification pipeline
How a raw engineering BOM becomes an audit-ready evidence packet.
Stage 1
Identity resolution
Messy MPN strings, internal part numbers and distributor SKUs are resolved to the canonical manufacturer part number and the legal manufacturer, separating parent companies, subsidiaries and rebranded or white-labeled lines.
Stage 2
Origin and provenance
Each resolved part is checked against authorized distributor records and manufacturer documentation. Country of origin comes only from dated, part-specific evidence: a headquarters address or plant footprint never establishes where a part was made. Self-attestations are labeled as declarations, and missing or conflicting evidence stays “Not established” for your review instead of being guessed.
Stage 3
Statutory and entity screening
The part and its full ownership chain (parent, subsidiary, OEM / ODM) are screened against the federal restrictions that apply to your scan:
Stage 4
Evidence packet and alternates
Every line is exported to an assessor-ready Excel validation workbook with a dated source citation behind each finding, and Drone NDAA and C-UAS assessments include an official, signed compliance certification you can use in bids. Flagged or unresolved parts are paired with candidate compliant alternates from authorized distributors, where one exists.
How we verify and source compliance
What each layer evaluates, where the evidence comes from, and what appears in your workbook.
| Verification layer | What is evaluated | Primary evidence sources | What you receive |
|---|---|---|---|
| 1Part and manufacturer identity | The canonical MPN, the actual manufacturer behind rebranded lines, and its parent companies. | Authorized distributor catalogs, manufacturer datasheets and product pages, CAGE records. | A verified part identity with its manufacturer and ownership mapped. |
| 2Country of origin | Where the exact part was made. Never inferred from a headquarters address or plant list. | Dated distributor origin records and manufacturer documentation for that part. | A dated origin citation marked “Verified evidence for this part”, “Declared for this line” or “Not established”. |
| 3Statutory and covered-list screening | The part and every entity in its ownership chain. | Official list publications from Congress, the Federal Register, FCC, DoD, BIS, OFAC and DCMA / DIU, plus restricted-party data. | Cleared, Restricted, Prohibited or Review required, with the rule and the source behind it. |
| 4Alternates and evidence packet | Compliant replacements for flagged or unresolved parts, and the record behind every decision. | Authorized distributor catalogs and the sources gathered in the earlier layers. | Candidate alternates with distributor links, a validation workbook with Report Matrix, Sources & Provenance and Executive Summary sheets, and an official compliance certification (Drone NDAA and C-UAS). |
Estimated turnaround
How long each service takes from order confirmation to your finished workbook, by the number of distinct parts in your BOM.
| Service | What we check | Up to 500 parts | Up to 1,500 parts | Up to 10,000 parts |
|---|---|---|---|---|
| Drone NDAA compliance | NDAA §848 / §817 origin screening, FY2019 NDAA §889 covered telecommunications checks, DoD §1260H and FCC Covered List cross-referencing, and exact-part country-of-origin evidence. | 24 hours | 72 hours | 1 week |
| Blue UAS readiness | DCMA / DIU Blue UAS Cleared List and Framework matching, hardware revision and CAGE identity checks, NDAA §848 and DoD §1260H screening, and an organized evidence dossier for assessor review. | 24 hours | 72 hours | 1 week |
| C-UAS supply chain | Multi-tier corporate ownership tracing (§889, §1260H, BIS Entity List, OFAC), sub-tier provenance verification, and candidate drop-in alternates for flagged components. | 24 hours | 72 hours | 1 week |
Custom list selections and BOMs above 10,000 distinct parts are scheduled with you when we quote.
Sample 100-row workbooks
Complete 3-sheet Excel deliverables (“Report Matrix”, “Sources & Provenance” and “Executive Summary”) produced from public hardware BOMs across 50+ manufacturers, including negative controls for DoD §1260H and FCC Covered List entities. Internal benchmarks on public data, not client records.
Blue UAS readiness
C-UAS supply chain
Prefer to look in your browser? Explore the 20-part demo reports.
Blue UAS program references
- List management
- DCMA assumed primary responsibility for Blue UAS list management on December 3, 2025, with DIU continuing as a partner on standards and checklists. Read the official transition announcement.
- Recognized Assessors
- Recognized Assessors evaluate NDAA compliance, ownership interests, supply-chain provenance and supporting artifacts. Their assessment and the government’s listing decision are separate from our evidence workbook, which organizes the component evidence they ask for. Recognized Assessor responsibilities.
How we test the engine
We use IEEE 1012 verification and validation (V&V) as the reference framework for testing the engine. Verification checks that outputs meet defined requirements; validation checks that the workflow meets its intended use. Each evaluation records the software version, input population, source systems and acceptance criteria, so every reported result has a defined scope and a traceable basis.
Part matches are scored against reference answers supported by authoritative manufacturer or supplier evidence. Match correctness and coverage are reported separately, and held or unmatched parts stay accounted for rather than dropped, so a reviewer can see exactly which cases a result covers.
Reference standardIEEE 1012-2024 — Standard for System, Software, and Hardware Verification and Validation