Vendor-neutral requirements governance

Eknoros.

From legacy specifications to approved, reusable digital baselines.

Eknoros helps engineering standards teams transform legacy specifications into approved, reusable and machine-readable requirement packages for the tools they already use.

01 / Founder

Aleksandr Annenkov

Aleksandr Annenkov · Founder

Nearly twenty years turning fragmented engineering knowledge into working systems.

I am an engineering systems architect with experience turning regulations, expert practice, and project decisions into structured requirements, classifications, and digital workflows. I have led projects from stakeholder interviews and process modelling to officially approved information requirements and working engineering environments. I am now building Eknoros.

Requirements engineeringClassification & domain modelsEngineering workflowsDigital twinsAI-assisted product development

02 / Product

Eknoros · Semantic governance layer

Preserve the meaning behind every requirement change.

Engineering teams manage standards, requirements, models, and evidence across Word, Excel, email, ALM, PLM, and QMS. Every change has to be interpreted, reviewed, and transferred between disconnected tools, often losing its source, rationale, and applicability.

Eknoros creates a governed chain from an authoritative source and domain model to an expert-approved digital baseline, one downstream integration, and evidence returned from use.

First end-to-end workflow

  1. 01Authoritative source
  2. 02AI-assisted extraction
  3. 03Domain model & applicability
  4. 04Expert review and disposition
  5. 05Approved digital baseline
  6. 06Machine-readable publication
  7. 07One downstream integration
  8. 08Application evidence & change

Current stage

The current clean-room interaction prototype demonstrates a synthetic source conflict, an AI proposal, authorized review, publication state, downstream impact, and a Word bridge concept. The next milestone is one specification converted into an approved baseline and delivered to one downstream consumer. Persistent lifecycle services and production integrations remain in development.

Long-term governed execution · planned architecture

Beyond text-based agent skills.

A skill defines how to work. Eknoros defines what is authoritative, applicable, and verifiable.

After the core workflow is validated with real application evidence, a planned Agent Procedure would link an approved baseline to a versioned Agent Skill, permitted models and tools, approval gates, evaluation criteria, and rollback conditions.

Eknoros is being developed as an independent international product. Prior professional projects and sectoral prototypes are presented as founder evidence, not as Eknoros customers, market validation, revenue, or product assets.

03 / Research

International customer discovery

Tell me how requirements work breaks in real projects.

If you create, approve, change, or verify engineering specifications and requirements, I would value your experience. The short form asks about one recent workflow, the tools involved, and where the process becomes slow or difficult.

You may also volunteer for an optional 15–30 minute follow-up interview. Please do not share confidential or proprietary material.

04 / Design-partner pilot

Deliberately narrow

One specification. One class. One downstream integration.

1engineering specification
1equipment or asset class
50–150requirements
3–7domain experts

The goal is to produce an approved, reusable, machine-readable requirement package and measure extraction time, review time, traceability, conflicts, impact analysis, reuse, and willingness to provide a second specification or continue as a paid pilot.

Who Eknoros is for

  • Engineering Standards and Specification Managers
  • Requirements and Systems Engineers
  • Knowledge Engineers
  • Discipline Experts and Technical Authorities
  • Digital Engineering and Engineering Excellence leaders

Typical buyers

VP Engineering · Chief Engineer · Engineering Director · Quality or Compliance leader

Discuss a design-partner pilot →

05 / Selected evidence

Evidence that I can move from ambiguity to governed delivery.

Digital transformation

From interviews to an operating system for delivery

Turned 19 management interviews into 31 target business processes, a 789-item classification system, and a 493-page implementation and governance package for a real-estate developer.

Moscow construction requirements

Requirements that reached an approved city framework

Authored four of nineteen information-requirement and classification documents, totaling 149 pages, later included in officially approved Moscow construction requirements.

Road-sector knowledge system

Structured knowledge at sector scale

Initiated and led the development of a road-sector classification and engineering-knowledge system covering hundreds of normative documents and thousands of structured entities.

06 / System fit

Works with the existing stack

Eknoros complements existing engineering systems.

ALM and requirements-management platforms are strong at reviewing, approving, and tracing requirements once they have been created. AI platforms, gateways, observability, and FinOps systems manage agent execution, routing, traces, and cost. Eknoros focuses on the semantic governance layer around them: sources, domain models, applicability, expert decisions, published digital baselines, permitted agent procedures, and evidence returned from use.

07 / Experience

Selected roles

2022 — present

Deputy Head, Infrastructure Information Modeling

FAU ROSDORNII

Coordinate three functional groups and directly manage a five-person team. Develop technical specifications and methodological foundations for road-sector digitalization, information-model requirements, common data environments, classification, and formalized engineering knowledge.

2021 — 2022

Head of Automated Systems Implementation

SODIS LAB

Led engineering-automation, BIM, and engineering information-management work. Audited delivery processes, modeled target workflows in BPMN and IDEF0, and authored standards, regulations, and GOST 34–aligned technical specifications.

2020 — 2021

XML Schema Developer · BIM Manager

Systems & Projects · SBD

Coordinated a five-person working group for machine-readable design documentation and produced more than 50 templates with XML schemas and validation examples. Led BIM requirements, execution planning, common-data-environment procedures, and multi-format model QA.

2017 — 2019

Project Manager · Requirements & Classification Specialist

Systems & Projects · Gravion-Project

Worked on digital transformation of the Moscow Construction Complex, construction classification, BIM standards, information requirements, and implementation concepts for linear, industrial, and major development programs.

2007 — 2017

Product, GIS & Urban-Planning Roles

Consistent Software Distribution · VolgaGeoComplex · 2GIS · Perm administration

Built a practical foundation across Autodesk engineering software adoption, technical training, cartography, municipal planning, and production GIS.

08 / Selected speaking

From industry signals to a requirements-native system.

Four public talks trace the evolution of the idea: from formalized industry knowledge and autonomous systems, through machine-readable standards, to a governed knowledge layer for trustworthy engineering AI.

09 / Education

Perm State University

Master of Geography with Honors · 2007

International focus

Building for global markets

Open to relocation