Phase Plan (P0-P5)

Last Updated: February 17, 2026
Status: P1 InstallShield Sprint ABORTED | Legacy Installer Validated Through Win10x32 | WiX Development Starting | v3.60 Source Recovery COMPLETE — 3 crash paths fixed | Win10 x64 COM fix COMPLETE — both x32 and x64 crash-free

Note: This plan is a working draft. Some technical details (exact file provenance, build parity, vendor timelines, pricing, and Autodesk product capabilities) may need verification as we inventory the full legacy tree and validate behavior in modern environments.

Overview

Your weekly status definitions are the backbone. This plan translates them into:

  • explicit deliverables

  • decision gates

  • staffing assumptions

  • schedule ranges

P0 — VM “Run as-is” (DONE)

Status: ✅ Completed 2026-01-13, Upgraded 2026-01-27
Definition: Runs on VM on new machine; dry run successful in AutoCAD 2000.
Constraints: Not distributable without selling laptop or custom install; version may be behind newest build.

Deliverables

  • Captured VM image + backup

  • “Golden run” demo recording and checklist

  • Initial inventory notes (what features matter most)

P0 Infrastructure Upgrade (Jan 27, 2026) 🆕

ConstructiVision Tower → Proxmox VM Migration:

  • ✅ Tower computer converted to Proxmox VM (only running legacy copy)

  • ✅ Properly backed up with snapshots (can clone/revert safely)

  • ✅ Tailscale VPN configured for secure remote access

  • ✅ LegacyUpdate.net integrated (keeps XP/Vista patched)

  • ✅ Greater Seattle Concrete remote access in progress

Benefits over VirtualBox on Dev Laptop:

Aspect

Before (VirtualBox)

After (Proxmox)

Location

Dev laptop (local)

Dedicated server

Backup

Manual, infrequent

Automated snapshots

Resources

Shared with dev work

Dedicated

Remote Access

None

Tailscale VPN

Customer Testing

Not possible

GSC can access directly

P1 — Installer Modernization (REVISED Feb 13)

Status: InstallShield Sprint ABORTED → WiX Development STARTING
Key Finding (Feb 13): Legacy InstallShield installer works all the way through Win10x32. No need to recompile from .rul.
Decision: Skip InstallShield rebuild, proceed directly to WiX installer using Total Uninstall payload.

P1 Sprint Abortion Rationale (Feb 13)

  • Low ROI: .rul recompilation had issues, wasn’t going smoothly

  • Better Path Found: Total Uninstall backup/restore validated on Win10x32

  • Auto-Config Script: scripts/Configure-ConstructiVision.ps1 handles AutoCAD integration

  • Result: Can build modern WiX installer without touching InstallShield

Current Approach: Total Uninstall + WiX

  1. File Payload: Total Uninstall inventory (152 files, 5.5 MB)

  2. Registry Config: AutoCAD profile settings via PowerShell script

  3. Serialization: License key validation (TBD)

Platform Compatibility (Validated Feb 13)

Platform

AutoCAD 2000

ConstructiVision

Status

Windows XP

✅ Works

✅ Works

Fully Supported

Windows Vista

✅ Works

✅ Works

Fully Supported

Windows 7

✅ Works

⚠️ BHF bug

Limited

Win10 32-bit

✅ Works

✅ Works

Fully Supported

Win10 64-bit

✅ Runs

✅ Works (registry fix)

Supported — requires Wow6432Node COM fix

Phase 1A: Analysis & Setup (✅ COMPLETE)

Timeline: January 21 - February 24, 2026
Focus: Environment baseline, legacy analysis, architecture decisions

Key Discoveries:

  1. ✅ isDcc decompilation success (Completed 2026-01-20)

    • Tool: isDcc v1.22 (Luca Borsato)

    • Input: setup.ins (compiled InstallScript)

    • Output: setup.rul (4,163 lines of readable InstallScript)

    • Now have full source for installer logic!

  2. ⚠️ VLX/FAS cannot be decompiled

    • Compiled Visual LISP format has no reliable decompiler

    • Solution: Recompile from LSP source files using VLIDE

    • All .lsp source files present in v7.0(patch)/ directory

Analysis Workstreams:

Week 1 (Jan 21-27): Legacy Environment Baseline

  • Set up InstallShield 5.x in Windows XP VM

  • Import setup.rul into new project

  • Document AutoCAD detection bug (registry-based, not file rename)

  • Document menu registration bug (detect active profile)

  • Establish baseline build environment

  • ✅ PE Header Analysis Complete (Jan 27):

    • ConstructiVision SETUP.EXE: 32-bit PE ✅ (can run on Win11 with compat mode)

    • AutoCAD 2000 SETUP.EXE: 16-bit NE ❌ (BLOCKED on Win11 x64)

    • AutoCAD 2000 uses 16-bit stub → MSETUP.EXE → 16-bit _ISDEL.EXE chain

    • Workaround: Use P0 VM for ACAD 2000 development; fresh installs require XP VM

Week 2 (Jan 27 - Feb 3): Gap Analysis

  • Analyze v7.0(patch) file structure

  • Document differences between v3.60 and v7.0

  • Create unified source inventory

  • Identify missing components and dependencies

Week 3 (Feb 3-10): Nero Analysis (COMPLETED - Lessons Learned)

  • ✅ Analyzed Nero 1.0 installer to validate isDcc workflow

  • ✅ Critical Discovery: isDcc bytecode output (10,031 lines) won’t compile

  • ✅ Solution Found: InstallShield wizard approach generates clean 606-line .rul that compiles

  • ✅ Documented lesson: Decompiler useful for understanding, not for rebuilding

  • ❌ Schedule Impact: VLX recompilation deferred; multi-OS testing delayed 2 weeks

Week 4 (Feb 10-16): Multi-OS Testing ✅ BREAKTHROUGH

  • ✅ AC2000 installed on XP (VM 104), Vista (VM 106), Win7 (VM 107) from ISO

  • ✅ CV3.60 installed on all 3 VMs — no UAC issues (logged in as Administrator)

  • ✅ 3-tool monitoring (Total Uninstall, Inctrl5, Regshot) captured on all VMs

  • ✅ 8 bugs documented with root cause analysis in CV360-Installation-Analysis.md

  • ✅ 41 files identical across all 3 platforms

  • ✅ Complete v11 installer specification created from monitoring data

  • ✅ Proxmox snapshots: cv360-installed-20260210 on all 3 VMs

Week 5 (Feb 10-17): Win10 Testing ✅ COMPLETE

  • ✅ Win10 32-bit clean install tested (VM 108)

  • ✅ AutoCAD 2000 + CV3.60 working on Win10x32

  • ✅ Auto-configuration script created: scripts/Configure-ConstructiVision.ps1

  • ✅ Win10 64-bit tested (VM 109) — COM fix applied, fully working (see 27-vm109-autocad-x64-registry-fix.md (sensitive))

  • ✅ Total Uninstall restore validated as deployment method

Week 5b (Feb 16): v3.60 Source Recovery & Deployment Pipeline ✅ COMPLETE

  • ✅ 12 missing AutoLISP modules recovered from v3.60 source archive → merged into TB11-01x32 test build

  • ✅ 3 crash paths fixed: wd_dlg (Standard Opening), wc_dlg (Weld Connections), wall_dlg (Wall Line) — light-tested, no crashes

  • ✅ 9 silent startup load failures resolved (weld/warning modules)

  • ✅ TB11-01x32 build: 134 → 195 files (+42 .lsp, +11 .dcl, +8 other)

  • ✅ Nightly deployment pipeline created: SSH deploy keys + Git sparse checkout + directory junction on VMs 108, 109, 201, 202

  • ✅ Scheduled task “ConstructiVision Git Pull” (daily 22:00) on all 4 Win10/Alpha VMs

  • ✅ Manual git-pull.bat on all VM desktops for on-demand updates

  • ✅ Git PATH fixed on VM 109 (C:\Program Files\Git\bin added to system PATH)

  • ✅ Documentation: 26-v360-source-recovery.md

Feb 13 Decision: P1 InstallShield Sprint ABORTED

  • Low ROI on .rul recompilation — wasn’t going smoothly

  • Legacy installer validated through Win10x32 — no rebuild needed

  • Total Uninstall payload + auto-config script = complete installer components

  • New Path: Proceed directly to WiX using validated components

Week 6+ Roadmap (REVISED Feb 17):

  • Feb 16: v3.60 source recovery COMPLETE — TB11-01x32 is the new test build

  • Feb 17: Win10 x64 COM registry fix COMPLETE — both x32 and x64 crash-free

  • Feb 17 - ongoing: Bug fixing and output quality validation on both x32 and x64 builds

  • Feb 17 - Mar 31: WiX Installer development for 32-bit and 64-bit systems

  • March 2026: Alpha/Beta testing with internal resources

  • Target: End of March 2026 for WiX installer GA release

Completed Prerequisites:

  1. ✅ Build environment reproduction (Completed 2026-01-16)

    • Latest known working build captured: v3.60 with v11 hotfix

    • Installation documentation: isos/INSTALLATION.md

    • Deploy-ready packages archived in Git LFS

  2. ✅ Legacy installer analysis (Completed 2026-01-20)

    • Decompiled InstallShield 5.0 installer using isDcc v1.22

    • Documented critical bugs:

      • AutoCAD detection bug (file rename test blocked by UAC)

      • Menu registration bug (hardcoded <<Unnamed Profile>>)

      • Windows Vista+ incompatibility (95%+ failure rate)

    • Decision: Rebuild from setup.rul, then migrate to WiX

  3. ✅ VM-based interim deployment (Upgraded 2026-01-27)

    • Windows XP VMs with v3.60 + v11 working → Proxmox VM server

    • Tailscale VPN + LegacyUpdate.net for remote access

    • Greater Seattle Concrete can now access legacy environment directly

    • Replaced VirtualBox on dev laptop with dedicated infrastructure

    • Properly backed up with snapshots (first time!)

Phase 1B: WiX Installer Development (🚧 STARTING - Feb 13)

Timeline: February 13 - March 31, 2026
Framework: WiX Toolset 4.x (Windows Installer XML)
Prerequisites: ✅ Total Uninstall payload validated, ✅ Auto-config script tested
Status: Starting — P1 InstallShield sprint aborted, proceeding directly to WiX

Why WiX?

  • Total Uninstall provides validated file inventory (152 files, 5.5 MB)

  • Auto-config script handles all AutoCAD integration

  • WiX provides modern MSI format for enterprise deployment

  • Enables Autodesk App Store compatibility

  • Modern, maintainable, code-signable

Components Ready:

  1. ✅ File Payload — Total Uninstall inventory validated

  2. ✅ Auto-Config Script — scripts/Configure-ConstructiVision.ps1 tested

  3. ⏳ Serialization — License key validation (TBD)

Workstreams:

  1. Week 1 (Feb 13 - Feb 20): WiX Foundation

    • WiX project setup and initial MSI structure

    • Import file list from Total Uninstall inventory

    • Basic installer UI and branding

  2. Week 2 (Feb 20 - Feb 27): Core Functionality

    • AutoCAD prerequisite detection

    • File deployment to Program Files

    • Post-install PowerShell script execution (auto-config)

    • Registry configuration

  3. Week 3 (Feb 27 - Mar 6): Advanced Features

    • Registry configuration

    • Uninstall support with clean removal

    • Process detection using Windows Restart Manager

    • acad.rx modification or .bundle approach

    • Code signing validation

  4. Week 9 (Mar 17 - Mar 24): Polish & Branding

    • Custom UI/branding (license, welcome, setup type)

    • Installation type selection (Typical/Custom/Compact)

    • Sample files component (optional)

    • Error handling and rollback

    • Code signing with EV certificate

  5. Week 10 (Mar 24 - Mar 31): Testing & Documentation

    • Test on Windows 7, 10, 11 (using sprint compatibility data)

    • Build automation (CI/CD pipeline)

    • User documentation

    • IT deployment guide (Group Policy, SCCM)

    • MSI validation tests

    • Release candidate build

    • Target: Mar 31, 2026 - WiX installer GA release

Phase 1D: Integration & Bug Fixing (⏳ NEW PHASE - 4 weeks) 🆕

Timeline: April 1 - April 30, 2026
Goal: Validate old ConstructiVision works with modern AutoCAD; fix critical bugs; establish stable baseline
Focus: Functional modernization only (no UI changes)

Workstreams:

  1. Week 11 (Apr 1-7): AutoCAD 2020+ Compatibility Testing

    • Test old ConstructiVision VLX with AutoCAD 2020, 2022, 2024

    • Document compatibility issues and breaking changes

    • Identify required code changes for modern AutoCAD API

    • Test WiX installer on modern AutoCAD versions

  2. Week 12 (Apr 8-14): Functional Modernization (No UI Changes)

    • Update deprecated AutoCAD API calls

    • Fix compatibility issues from Week 11

    • Maintain existing UI/UX (defer visual changes to P2)

    • LSP code updates for modern AutoCAD

  3. Week 13 (Apr 15-21): Bug Fixing Sprint

    • Address critical bugs found during multi-OS testing (Feb)

    • Fix hard errors from menu validation testing

    • Regression testing on XP/Vista/Win7/Win10

    • AutoCAD version-specific bug fixes

  4. Week 14 (Apr 22-30): Stabilization & Testing

    • Integration testing with WiX installer

    • Performance testing and optimization

    • Documentation updates

    • Final regression testing across all supported platforms

    • Target: Apr 30, 2026 - Stable baseline for P2 design improvements

    • Decision Point: Stable baseline achieved → proceed to P2 Design phase

Phase 1C: OS/AutoCAD Compatibility Validation (✅ COMPLETE Feb 13)

Timeline: February 10-13, 2026
Status: COMPLETE — Full compatibility matrix validated

OS Testing Matrix (Updated Feb 13):

OS

Priority

VM

Status

Results

Windows XP SP3

P1

VM 104

✅ PASSED

AC2000 + CV3.60 working

Windows Vista SP2

P2

VM 106

✅ PASSED

No UAC issues as Administrator

Windows 7 SP1

P2

VM 107

⚠️ LIMITED

pcAnywhere BHF path issue (not a CV bug — see doc 22)

Windows 10 32-bit

P1

VM 108

✅ PASSED

Full stack working with auto-config script

Windows 10 64-bit

P1

VM 109

❌ BLOCKED

COM automation fails (IDispatch)

Windows 11

P3

N/A

🚫 Deferred

Need 64-bit AutoCAD first

Win10 64-bit Analysis (Feb 13, RESOLVED Feb 17):

  • ✅ Total Uninstall restore bypasses 16-bit installer

  • ✅ AutoCAD 2000 runs on 64-bit Windows

  • ✅ CV files load successfully

  • ✅ RESOLVED: CSV command works after Wow6432Node COM registry fix

  • Root Cause: Total Uninstall placed COM registrations in native 64-bit hive instead of Wow6432Node

  • Fix: Copy 103 CLSIDs, 104 IAcad Interfaces, and 6 ProgIDs to Wow6432Node (see 27-vm109-autocad-x64-registry-fix.md (sensitive))

  • Additional: Project Files search path must be manually set in AutoCAD Options

AutoCAD Testing Matrix:

AutoCAD Group

Versions

Architecture

VLX Support

Legacy 32-bit

R14, 2000-2006

32-bit only

Original VLX

Transition

2007-2009

32-bit

VLX compatible

Modern 32/64

2010-2013

Both

Test both

64-bit Only

2014-2026

64-bit only

May need rebuild

Workstreams:

  1. Analysis Testing (Feb 10-24 - Weeks 4-5)

    • Test legacy installer on all OS targets

    • Document failure codes and edge cases

    • Build compatibility matrix (OS × AutoCAD version)

    • Performance testing (install time, uninstall clean)

    • Document requirements for Installer phase

  2. Customer Validation (Mar)

    • Deploy working installer to Great Seattle Concrete

    • Gather real-world feedback

    • Iterate based on findings

    • Compare InstallShield vs WiX experience

  3. UI Documentation (Target: Mar 31)

    • Capture screenshots of all menu options

    • Build hierarchical user input tree

    • Create UI reference guide for P3 modernization

Exit criteria for P1

  • ✅ Analysis Exit (Feb 24):

    • Legacy environment fully baselined

    • VLX files recompiled from LSP source

    • Tested on XP, Win 7, Win 10, Win 11

    • Compatibility matrix documented

    • Requirements locked for Installer phase

  • ✅ Installer Exit (Mar 21):

    • WiX installer GA release

    • 95% success rate on Windows 10/11

    • Menu appears immediately (no manual steps)

    • Tested on ≥3 Windows versions with documented compatibility

    • Production-ready MSI distributable

  • ✅ Documentation Exit:

    • Remote access working for beta customers (VM or direct install)

    • Screenshot tree complete for UI modernization planning

    • Failure codes and limitations documented

    • IT deployment guide complete

Decision gate into P2 (Design Improvement)

  • Is legacy environment fully baselined?

  • Which installer approach should be primary (WiX)?

  • Are beta customers satisfied with installation experience?

  • Is VLX recompilation sufficient or do we need source modifications?

P2 — 64-bit AutoCAD + Alpha/Beta Testing (PLANNED - March 2026)

Status: Planned for March 2026
Goal: Internal testing, bug fixing, and output quality validation before customer release

P2-A: 64-bit AutoCAD Compatibility (March 2026)

Action Items:

  1. Purchase 64-bit AutoCAD license (2010+ required for native x64) DEFERRED — AC2000 x64 now working

  2. Install on Win10x64 test VM (VM 109) ✅ AC2000 working on x64 after registry fix

  3. Test CV VLX loading and execution ✅ VLX loads and runs on x64

  4. Determine if VLX recompilation needed for x64 ✅ Not needed — same VLX works on both x32 and x64

  5. Test WiX installer on 64-bit Windows (include Wow6432Node COM fix in installer)

Technical Questions ANSWERED (Feb 17):

  • ✅ Does existing VLX work with AutoCAD 2000 on 64-bit Windows? YES

  • ✅ Does COM automation work on 64-bit Windows? YES — after Wow6432Node registry fix

  • ✅ Is VLX recompilation needed for x64? NO — identical binary works on both architectures

  • 🔜 Should we still pursue modern AutoCAD (2010+)? Yes, for future-proofing (P3)

P2-B: Alpha/Beta Testing (Feb 17 - Mar 14, 2026)

Goal: External alpha testing with GSCI engineers before limited customer release

Alpha Testing: GSCI Engineers (Feb 17 - Mar 14)

Participants: 2 Great Seattle Concrete Inc. (GSCI) engineers
Platform: Win10 32-bit VMs (200, 201) isolated for external access
Access: Tailscale PVE authentication + Remote Desktop

Infrastructure:

  • VM 200: Terry (GSCI) — Panel layout and estimating workflows

  • VM 201: Leon (GSCI) — Detailing and export validation

  • Cloned from VM 109 (validated Win10x32 + AC2000 + CV v11)

  • Isolated “island” for external users (separate from internal VMs 100-109)

Timeline:

  • Week 0 (Feb 13-16): VM setup, user accounts, Tailscale config

  • Week 1 (Feb 17-21): Installation & basic functionality testing

  • Week 2 (Feb 24-28): Real-world workflows with GSCI projects

  • Week 3 (Mar 3-7): Edge cases, stress testing, bug reproduction

  • Wrap-up (Mar 10-14): Debrief, feedback collection, WiX requirements update

Success Criteria:

  • Remote access works (Tailscale + RDP)

  • CV menu loads on first launch (>95% success)

  • Core functionality works (panel creation, calcs, exports)

  • <1 crash per day per user

  • All bugs documented with repro steps

  • User satisfaction >4/5

Deliverables:

  • Installation report and initial bug list (Week 1)

  • Workflow feedback and performance notes (Week 2)

  • Final bug report and enhancement requests (Week 3)

  • Alpha test summary and WiX requirements impact (Wrap-up)

See: alpha-testing-gsci-plan.md (sensitive) for complete details
Checklist: alpha-testing-gsci-checklist.md (sensitive)

P2-C: Customer Validation (April 2026)

  • Deploy working installer to Greater Seattle Concrete

  • Gather real-world feedback

  • Iterate based on findings

P3 — UI/UX Modernization (PLANNED - Q2 2026)

Status: Planned for Q2 2026 (May - Jun)
Goal: Modernize UI/UX, refactor code, and lock a reproducible baseline for production.

P3-A: UI/UX Modernization

  • Review all DCL dialogs for usability improvements

  • Modernize outdated interface patterns

  • Improve error messages and user feedback

  • Update visual styling where possible within DCL constraints

P2-B: Code Refactoring

  • Clean up legacy LSP code structure

  • Improve maintainability and documentation

  • Remove dead code and redundant logic

  • Standardize naming conventions and patterns

P2-C: Documentation

  • Complete user guide with screenshots

  • Installation and configuration guide

  • IT deployment guide for enterprise

  • Developer documentation for future maintenance

Deliverables

  • UI/UX improvement report (before/after comparisons)

  • Refactored codebase with inline documentation

  • Complete documentation suite

  • Versioned baseline “ConstructiVision v26-Baseline”

Exit criteria

  • All dialogs reviewed and improved where feasible

  • Code refactoring complete with no regressions

  • Documentation complete and reviewed

  • Build is reproducible and documented

P3 — Security & Testing (PLANNED - REVISED)

Status: Planned for Q3 2026 (Jun - Sep)
Goal: Comprehensive security hardening and multi-version compatibility testing.
New Objective: Prepare for Autodesk Developer Network (ADN) and App Store distribution
Dependency: AutoCAD 2026 access for validation and packaging.
Estimate: 16 weeks (Jun - Sep)

Workstreams

  1. Multi-Version Compatibility Testing

    • Test on AutoCAD 2024, 2025, 2026

    • AutoCAD API compatibility fixes (LISP/VLISP behavior differences)

    • Performance pass + startup reliability

    • Build comprehensive test matrix

  2. Security Audit & Hardening 🆕

    • Code security review (input validation, file handling)

    • Vulnerability scanning (static analysis)

    • Dependency audit (third-party components)

    • Windows Defender / SmartScreen compatibility

    • Estimate: 4-6 weeks

  3. Autodesk Developer Network (ADN) Preparation 🆕

    • Apply for ADN Developer membership (~$500/year)

    • Request early access to AutoCAD 2027 SDK

    • Review App Store submission guidelines

    • Prepare compliance checklist (security, EULA, privacy policy)

  4. Modern Plugin Format (.bundle Migration) 🆕

    • Convert from acad.rx loading to .bundle structure

    • Enables Autodesk App Store compatibility

    • Improves Windows 11 security compliance

    • Estimate: 3-4 weeks

Exit criteria

  • Clean load and run on AutoCAD 2024, 2025, 2026

  • Security audit passed with no critical findings

  • Regression suite passes on all target environments

  • .bundle format validated and working

  • ADN Developer membership active

  • Ready for code signing and final packaging

Decision gate into P4

  • Is multi-version compatibility solid enough for production?

  • Are all security findings addressed?

  • Do we need ADN Partner tier ($2K-10K) or is Developer tier sufficient?

P4 — Final Release & Demo (REVISED)

Status: Planned for Q4 2026 (Oct - Dec)
Goal: Code signing, App Store submission, owner demo, and production release.
New Objectives: Dual distribution (direct download + Autodesk App Store)
Estimate: 12 weeks (Oct - Dec)

Workstreams

  1. Code Signing & Packaging

    • Obtain EV code signing certificate

    • Sign .bundle package for SmartScreen trust

    • Create final distributable packages

    • Validate on clean Windows installations

  2. Autodesk App Store Submission 🆕

    • Submit to Autodesk App Store (Nov 2026)

    • Address security review findings (allow 2 cycles = 4 weeks)

    • Publish listing (screenshots, description, pricing)

    • Monitor downloads and conversion rates

  3. Direct Distribution Channel

    • WiX MSI installer (completed in Installer phase)

    • Download portal on website

    • Auto-update mechanism

    • IT deployment guide (Group Policy, SCCM)

  4. Owner Demo & Handoff

    • Prepare demonstration environment

    • Create handoff presentation

    • Document operational procedures

    • Knowledge transfer session

  5. Web Developer Onboarding 🆕

    • Hire web developer (Oct 1)

    • Begin AutoLISP → .js/.NET conversion planning

    • Set up development environment

    • Initial prototype work

Distribution Strategy:

Channel

Pros

Cons

Target Audience

Direct Download

Full control, no revenue share

Must market ourselves

Existing customers, referrals

Autodesk App Store

Trusted marketplace, wider reach

30% revenue share to Autodesk

New customers, enterprise IT

Exit criteria

  • EV code signing certificate obtained and applied

  • .bundle package signed and validated

  • Autodesk App Store listing approved and live (or in review)

  • Direct download portal live and tested

  • Owner demo completed successfully

  • Web developer onboarded and productive

  • 🎉 ConstructiVision v26 Released

Decision gate for future (P5)

  • Which distribution channel performs better (direct vs App Store)?

  • Should we invest in ADN Partner tier for co-marketing?

  • Is web conversion viable as primary product direction?

P5 – Web Deployment & AI Enhancements (2027+)

Status: TBD
Goal: Web-based access + AI-assisted automation
Start: Begins Q4 2026 with web developer hire; full deployment 2027+

Web Deployment Strategy (NEW)

Why Web Deployment?

  • Removes AutoCAD desktop dependency for some workflows

  • Enables broader market reach (non-AutoCAD users)

  • Supports mobile/tablet access

  • Enables SaaS subscription model

Technology Options:

Option

Pros

Cons

Effort

Best For

JavaScript (Browser)

Universal access, no install

No native AutoCAD integration

Medium

Standalone tools

APS Design Automation

Official Autodesk API, headless AutoCAD

Per-API-call costs, learning curve

High

Heavy CAD processing

.NET Web API

Strong typing, familiar stack

Requires hosting, no AutoCAD runtime

Medium

Backend services

Recommended Phased Approach:

  1. Phase 5A: JavaScript utilities (form fillers, calculators) - Low risk

  2. Phase 5B: .NET API backend (data services, report generation) - Medium risk

  3. Phase 5C: APS Design Automation (CAD automation as service) - High investment

APS (Autodesk Platform Services) Integration:

  • Design Automation API for headless AutoCAD execution

  • Data Management API for file storage/version control

  • Model Derivative API for viewing without AutoCAD

  • Note: Requires APS subscription (separate from ADN)

AI Enhancements

Deliverables (incremental)

  • AI-assisted form fill (structured extraction + review UI)

  • Panel book generator “EZ Button” (template + rules + traceability)

  • Integrated test output generation (evidence pack per project)

Exit criteria

  • Human-in-the-loop review workflow

  • Audit-friendly traceability (what data → what output)

  • Clear off-switch and fallbacks

Security & Compliance Requirements (NEW)

Code Signing (Required for P1+):

Certificate Type

Cost/Year

SmartScreen

Purpose

Standard Code Signing

$200-400

Builds trust slowly

Development/testing

EV Code Signing

$400-700

Immediate trust

Production release

Recommended Vendors: DigiCert, Sectigo, Certum

Autodesk Developer Network (Required for P3+):

Tier

Cost/Year

Benefits

Developer

~$500

App Store access, basic support

Partner

$2K-10K

Early SDK access, co-marketing

App Store Compliance Checklist:

  • Security review (automated scan + manual review)

  • EULA approved by legal

  • Privacy policy (data collection disclosure)

  • Terms of service

  • .bundle format validated

  • Screenshots and marketing materials

Staffing notes (levers that move the schedule)

  • Core engineer (AutoCAD/LISP/VLISP): required for P1–P3

  • Release engineer / installer: accelerates P1–P3 and reduces support risk

  • Web developer: enables P4 parallelization and earlier P5 starts

  • QA / regression automation: reduces parity risk and accelerates confidence

  • Security/DevOps: Code signing, CI/CD, compliance automation (P3+)