Allied Magnet Assurance

Allied Critical Materials builds software for protected critical-material supply chains. Allied Magnet Assurance helps rare-earth magnet producers, processors, defense suppliers, and allied feedstock companies manage DFARS 7052 evidence, supplier qualification, lot acceptance packages, and mine-to-magnet digital threads.

DFARS 7052 Magnet Workbench

A software workbench for rare-earth magnet and material evidence, supplier qualification, lot acceptance packages, and controlled buyer review. It is designed for processors, magnet makers, defense suppliers, and allied feedstock teams that need to turn scattered records into review-ready evidence packages.

Representative Workbench Preview

This is a demo placeholder, not live customer data. The production surface should let a buyer inspect the evidence model, gap register, lot package, reviewer notes, and downloadable package before trusting the workflow.

DEMO WORKBENCH | Lot package MAG-2027-014
Package status: Review ready with 2 open gaps
Origin evidence: attached | Supplier declaration: attached
Assay certificate: attached | QA/QC record: attached
Transformation record: missing | Reviewer note: counsel review
Review rooms: procurement, quality, counsel, customer
Handoff: generate buyer package PDF + evidence index

What a buyer can inspect in a pilot

A serious buyer should be able to inspect concrete outputs before scaling. A focused pilot should produce artifacts using synthetic, redacted, or approved buyer-provided records.

  • Evidence model. The data fields and relationships for suppliers, facilities, feedstock or material lots, assays, certificates, transformation records, customer requests, and reviewers.

  • Sample lot package. A package structure with lot identity, required records, missing-record flags, reviewer notes, and a downloadable review file.

  • Gap register. A list of missing or weak records, responsible parties, target dates, evidence status, and review notes.

  • Controlled review room. Role-scoped views for procurement, counsel, quality, audit, customer, or program review.

  • Package handoff. A clean evidence package that can be evaluated without giving every counterparty access to the underlying workspace.

What the pilot should prove

  • Traceability. Records connect to a specific package, lot, supplier, facility, and reviewer decision instead of living in scattered folders.

  • Gap visibility. Missing evidence is visible early enough for procurement, quality, counsel, or program teams to act.

  • Review control. Sensitive records can be separated by reviewer need, package scope, and data-handling rule.

  • Handoff quality. The buyer receives an evidence index, package file, open-gap list, and implementation notes.

Processor workflow: feedstock to customer package

The Workbench is useful even when the buyer already has supplier relationships. It organizes evidence around existing counterparties and lots instead of inserting Allied Critical Materials into the physical supply chain.

  • Supplier and feedstock intake. Capture supplier profile, facility records, origin declarations, receipt identity, and buyer-request context.

  • Assay and certificate capture. Attach lab reports, certificates, QA/QC records, and chain-of-custody notes to the lot or package they support.

  • Transformation records. Connect separation, conversion, oxide, metal, alloy, magnet, component, or customer-package records where the buyer needs an evidence trail.

  • Lot genealogy. Show which documents support which output lot, customer package, or review request.

  • Buyer-ready review package. Generate a structured package for procurement, contracts, counsel, quality, audit, customer, or program teams.

Security and data handling

Rare-earth evidence can include sensitive supplier, assay, customer, pricing, and program records. Pilot and production scope should be matched to the buyer's data-handling requirements.

  • Start safely. Early pilots can begin with synthetic, redacted, or buyer-approved sample records until NDA and security review are complete.

  • Access control. Workspaces are scoped by organization, role, package, and reviewer need.

  • Limited sharing. Review views should expose only the records needed for that counterparty or function.

  • Production readiness. Before production onboarding, the buyer and ACM should define hosting model, retention rules, access review, audit-log requirements, and security questionnaire coverage.

Pilot and procurement path

A typical first engagement is a focused two-to-four week pilot around one supplier, material lot, magnet lot, component family, or buyer evidence request.

  • Scope. Select one package, define required evidence, name buyer-side reviewers, and agree on data-handling rules.

  • Inputs. Supplier records, facility history, lot identity, assays or certificates, QA/QC records, declarations, and current buyer requirements.

  • Outputs. Evidence model, gap register, sample lot package, controlled review room, and package handoff.

  • Procurement handoff. Pilot statement of work, NDA/data-handling terms, security questionnaire inputs, success criteria, and production deployment requirements.

  • Success criteria. Faster package assembly, clearer gap visibility, less duplicate evidence handling, and a cleaner handoff to procurement, counsel, audit, customer, or program review.

Evidence support, not legal certification

Allied Critical Materials does not provide legal advice or certify compliance. The platform is designed to organize evidence, flag gaps, and generate review-ready packages for buyers, counsel, auditors, and government-facing teams. Eligibility determinations remain with the buyer, counsel, and responsible program stakeholders.

Boundary: ACM builds assurance software only. It does not take custody of material, perform material production or sale activities, or make eligibility determinations.

The January 2027 deadline changes the evidence burden.

DFARS restrictions for covered magnets expand on January 1, 2027. For buyers and suppliers, the practical problem is evidence: origin records, facility history, transformation steps, chain-of-custody notes, supplier declarations, assays, certificates, QA/QC evidence, and review status need to be organized before a package is under deadline pressure.

What a serious buyer should ask for next.

  • Sample package. A redacted or synthetic lot package that shows the target evidence index, missing-record flags, reviewer notes, and handoff file.

  • Security review inputs. Hosting assumptions, access model, retention expectations, audit-log requirements, and data-segmentation needs.

  • Pilot SOW. A narrow package scope, success criteria, buyer-side reviewers, timeline, and production-decision gate.

  • Responsibility map. A clear line between software evidence support and eligibility decisions made by the buyer, counsel, auditors, or responsible program stakeholders.

Build your first magnet evidence package.

ACM is seeking focused pilot partners across rare-earth processing, magnet production, defense supply chains, and allied feedstock qualification. The first step should be a narrow, inspectable proof package rather than a broad transformation project.