# Oleksii Mazur Canonical profile: https://oleksii.almalvs.online/ Software Automation & Agentic Engineering Location: Spartanburg, SC I'm Oleksii Mazur, owner of Smart Control LLC and a technical specialist based in Spartanburg, South Carolina. My work brings together low-voltage systems, network infrastructure, field operations and software development with AI. ## Biography I'm Oleksii Mazur, owner of Smart Control LLC and a technical specialist based in Spartanburg, South Carolina. My work brings together low-voltage systems, network infrastructure, field operations and software development with AI. I started working with video systems and technical operations in 2006. Since then, I've worked in low-voltage installation, system administration, telecommunications and installation management. That experience taught me to understand the equipment and the conditions it has to work in, whether on a job site, in an office or in a client's daily routine. My hands-on work covers IP video surveillance, access control, structured cabling, Wi-Fi, coaxial cable and fiber infrastructure. I handle installation, configuration, troubleshooting, testing and technical documentation. I can take on smaller projects myself or coordinate technicians and subcontractors on larger jobs. I bring that field experience to software projects such as Smart Lead System, Field Operations and LowVoltagePlan. These focus on organizing leads, connecting field crews with the office and defining a clear scope before work begins. I start by looking at who receives information, who makes the next decision, where time gets lost and which tasks are worth automating. AI tools are part of how I research, design, build and test solutions. I work with agent workflows, n8n, APIs, webhooks and service integrations. My software projects use TypeScript, React/Next.js, Python and PostgreSQL. I define the requirements, organize AI-assisted development, check how the system behaves and work through the details needed to get it running. I also work with Linux, Docker, VPS hosting, reverse proxies, HTTPS, backups and recovery. Getting an application online is one part of the job. I also need to know how to check its health, trace a failure and safely restore a previous version. My research projects explore equipment automation, condition monitoring and passive vehicle diagnostics. I keep a clear distinction between an experiment, a working prototype and a system ready for everyday use. I turn technical complexity into tools people can use. I understand the work on site and the questions a business owner needs answered. That helps me build software around both. My aim is to reduce manual work while keeping important decisions in human hands. ## Capabilities ### Workflow automation Clarify handoffs, prepare context and keep accountable review steps visible. Questions to clarify: - Where does work slow down or get lost? - Who needs to review the next decision? - What information must be ready before that handoff? Published examples: - [Smart Lead System](https://oleksii.almalvs.online/work/smart-lead-system#workflow): Product architecture, workflow design and operating QA. Status: In operation. - [Field Operations](https://oleksii.almalvs.online/work/field-operations#workflow): Product design, operational data flow and QA strategy. Status: In operation. - [Invoice System](https://oleksii.almalvs.online/work/invoice-system#workflow): Product and workflow design, system architecture, AI-assisted implementation and operational verification. Status: In operation / scoped payments. ### Practical web tools Build focused, reviewable tools around a real operating process and clear public information. Questions to clarify: - What should a person be able to understand or decide online? - Which details need review before work starts? - What evidence can be published safely? Published examples: - [LowVoltagePlan](https://oleksii.almalvs.online/work/lowvoltageplan#workflow): Field workflow, scope modeling and review-gated product architecture. Status: Controlled pilot. - [Smart Control Website](https://oleksii.almalvs.online/work/smart-control-website#workflow): Business requirements, website direction, AI-assisted development and content review. Status: Live website. ### Equipment and software integration Connect condition monitoring, device workflows and software while preserving clear control boundaries. Questions to clarify: - What condition or device state needs to be visible? - Which routine decision is safe to automate? - Where must a person retain manual control? Published examples: - [EcoGen Automation Controller](https://oleksii.almalvs.online/work/ecogen-controller#workflow): Control workflow, low-voltage wiring, relay integration, controller setup and bench testing. Status: Working prototype. - [Chevrolet Volt Diagnostics Toolkit](https://oleksii.almalvs.online/work/chevrolet-volt-toolkit#boundary): Diagnostics workflow, signal research and safety boundary design. Status: Research & development. ### Technical installation coordination Coordinate teams, site logistics, electrical work and lighting control under practical constraints. Questions to clarify: - What site restrictions affect the installation? - What must arrive, be protected or be returned intact? - Who owns coordination, safety and the next site decision? Published examples: - [My Heart is a Void, the Void is a Mirror](https://oleksii.almalvs.online/work/tosatti-odesa-installation#delivery): Installation Lead: team leadership, site organization, lamp-post installation, electrical work and lighting control. Status: Completed in 2020. - [My Heart is a Void, the Void is a Mirror](https://oleksii.almalvs.online/work/tosatti-odesa-installation#engineering): Installation Lead: team leadership, site organization, lamp-post installation, electrical work and lighting control. Status: Completed in 2020. ## Engagement boundaries - Pricing: Not published. Discuss scope before pricing. - Availability: Not published. Discuss current availability before planning work. - Inquiry mode: draft-only; delivery enabled: false. ## Evidence policy - Project statuses are published as stated and distinguish live work, prototypes, research and completed installations. - Public sources are linked where they are already published. Other details are explicitly marked as the owner's first-hand account. - Screenshots retain their published demo, archive, synthetic-data and test-state boundaries. - No private customer records, hardware identifiers, account access details, pricing or current availability are published. - The reviewedOn date describes this published public record; it is not a new verification of a live runtime or external service. Reviewed: 2026-09-06