Aleksandr Annenkov · Founder & Engineering Systems Architect
Building Eknoros.
A semantic governance layer for engineering requirements.
Eknoros connects legacy standards, domain models, expert decisions, and application evidence, then publishes approved requirement packages to the engineering tools and AI agents teams already use.
01 / 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 for engineering requirements
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 a legacy source and domain model to an expert-approved requirement package, downstream integration, and application evidence.
First end-to-end workflow
- 01Legacy specification
- 02AI-assisted extraction
- 03Domain model
- 04Expert review and disposition
- 05Approved baseline
- 06ReqIF / JSON / YAML export
- 07Deviations and evidence
- 08Next revision
Current stage
The current clean-room interaction prototype demonstrates a synthetic source conflict, an AI proposal, authorized review, publication, downstream impact, and a Word bridge concept. Persistent lifecycle services, exports, integrations, and application-evidence workflows are the next product milestones.
Target product stack: Kotlin/Ktor · PostgreSQL · graph and vector projections · AI-assisted development
Eknoros is being developed as an independent international product. Prior professional projects and sectoral prototypes are presented as evidence of founder experience, not as Eknoros customers, 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 active project.
The goal is to produce an approved, reusable, machine-readable requirement package and measure extraction time, review time, traceability, conflicts, impact analysis, and reuse.
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. Eknoros focuses on the semantic governance layer around them: sources, domain models, applicability, expert decisions, published requirement packages, 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.
May 2026 · Saint Petersburg
NFST 2026
Trustworthy AI in engineering: verified sources, machine-readable requirements, ontologies, expert approval, and auditable recommendations.
Official source ↗Dec 2025 · Moscow
IT-Standard 2025
Creating a road-sector ontology as the foundation of a digital ecosystem, with AI-ready standards and traceable requirements.
Official source ↗Nov 2025 · Voronezh
Road Dialogue: Chernozemye
A long-term view of AI, Big Data, robotics, digital twins, and formalized knowledge systems for road infrastructure.
Official source ↗Oct 2025 · Mineralnye Vody
Road 2025
Presented the structure and applications of a road-sector classification system as a formalized knowledge base for AI, intelligent transport systems, and automated construction machinery.
Official source ↗09 / Education
Perm State University
Master of Geography with Honors · 2007
International focus
Building for global markets
Open to relocation