One platform. Every framework you need.
Argis Labs treats the asset and the framework used to assess it as independent, configurable dimensions of the same pipeline - not a fixed bundle. Here's what we assess against today, and how a new one gets added.
Asset, framework, and deliverable - independently configurable
Every engagement is scoped by picking the asset, the framework that governs it, and the deliverable it produces. These aren't bundled - the same tower can be assessed against different standards depending on the engagement.
| Asset | Framework | Typical output |
|---|---|---|
| Roadway pavement | PASER (or similar pavement condition scoring) | Condition assessment & capital planning input |
| Sidewalk & pedestrian network | ADA / PROWAG | Accessibility assessment or full transition plan |
| Curb ramps & crossings | PROWAG | Geometry compliance findings, prioritized by risk |
| Communication towers | TIA-222 | Structural inspection & engineering report |
| Solar & wind assets | Manufacturer / industry O&M standards | Structural & operational inspection report |
| Power transmission | NESC structural standard, NERC vegetation-management standards | Structural & right-of-way condition report |
| Pipelines | Applicable pipeline safety & integrity standards | Right-of-way & structural integrity findings |
| State & local variations | Adopted amendments, bulletins, or stricter local tolerances | Layered on top of the governing baseline automatically |
| Custom asset class | Client-defined framework | Custom assessment deliverable, scoped to the engagement |
Every asset class has a standard. Most have more than one.
Every asset class has a governing framework, but many jurisdictions and organizations layer their own adopted standards, bulletins, and amendments on top. A finding that's compliant against the baseline can still fail the standard your reviewer actually has to cite.
The governing framework
The standard every asset class must meet, applied to every finding as a starting point - ADA/PROWAG, a tower structural standard, a pavement condition standard, or a framework you define.
Adopted-standard variation
Many jurisdictions and organizations layer their own bulletins, amendments, or stricter tolerances on top of the baseline. Those layers are configured once per project, not re-derived by hand each time.
Scored against the standard that governs
Every finding is analyzed and cited against the standard actually in force for that project - not a one-size-fits-all check run against a generic baseline.
Don't see your standard? That's a configuration, not a rebuild.
The detection and measurement layer is asset-driven, not framework-driven - so applying a new or client-defined framework to an asset we already support is a configuration step, not new engineering. If you're responsible for an asset class we don't list here, tell us how it needs to be assessed.
You define the standard
The criteria, thresholds, and citations your reviewer needs the findings scored against - your own framework, or a published one we haven't onboarded yet.
We configure the rules
Your framework is layered onto the existing detection and measurement pipeline for that asset class - no new sensors, no new field methodology.
Every future finding scores against it
Once configured, the framework applies automatically to every asset in scope, and to every future reassessment.
Bring us your standard. We'll show you the assessment.
Whether it's a framework already on this page or one specific to your organization, we'll scope what it takes to assess against it.
Book a discovery call