title: "TICKET_035: Odoo Module Installation & Base Configuration"
type: ticket
status: ready
priority: P0
sprint: S001_base_and_mvp1
assignee: "Sonnet 4.6 (Coder Swarm) + Founder (Odoo admin)"
estimated_hours: 4
depends_on: []
blocks: [TICKET_036, TICKET_037, TICKET_038, TICKET_039]

TICKET_035: Odoo Module Installation & Base Configuration

Objective

Install all required Odoo Enterprise modules and configure the base infrastructure for the ISO 19650 compliance service on the existing Odoo.sh instance.

Context

Tasks

Task 1: Install Core Modules

Log into Odoo.sh admin panel and install the following modules:

Client-facing:

Task 2: Configure CDE Document Workspace Template

In Documents module, create a template workspace:

  1. Create workspace: "ISO 19650 CDE Template"
  2. Create folder structure:
    • 01_WIP/ (tags: S0)
    • 01_WIP/Architecture/
    • 01_WIP/Structural/
    • 01_WIP/MEP/
    • 01_WIP/Civil/
    • 02_SHARED/ (tags: S1, S2, S3, S4)
    • 03_PUBLISHED/ (tags: A1, A2, A3, A4, A5, A6)
    • 04_ARCHIVED/
    • 05_BIM_MODELS/
  3. Create document tags for ISO 19650 status codes:
    • S0 (Work In Progress)
    • S1 (Suitable for Coordination)
    • S2 (Suitable for Information)
    • S3 (Suitable for Review/Comment)
    • S4 (Suitable for Stage Approval)
    • A1 (Accepted — Stage 1)
    • A2 (Accepted — Stage 2)
    • A3-A6 (subsequent stages)
    • CR (As-Constructed Record)

Task 3: Configure Quality Module for ISO 19650

Create quality control points:

  1. Quality point: "BEP Completeness"

    • Check: Does BEP contain all required sections per ISO 19650-2 §5.3?
    • Type: Pass/Fail checklist
    • Sections: Information management functions, delivery strategy, LOIN, software/hardware, IT security
  2. Quality point: "EIR Completeness"

    • Check: All required fields per ISO 19650-2 §5.2 populated
    • Type: Pass/Fail checklist
  3. Quality point: "File Naming Convention"

    • Check: Files follow National Annex naming convention
    • Type: Text validation
  4. Quality point: "CDE State Transition"

    • Check: Proper approval before state change
    • Type: Approval workflow trigger

Task 4: Configure Products & Pricing

In Subscriptions + Accounting:

  1. Create subscription plan: "ISO 19650 Compliance"

  2. Create products:

    Starter:

    • Setup product: "ISO 19650 Starter Setup" — $1,500 (one-time)
    • Subscription product: "ISO 19650 Starter Monthly" — $250/month
    • Description: 1 project, 5 users, 5GB, Generic ISO, Document-level compliance

    Professional:

    • Setup product: "ISO 19650 Professional Setup" — $3,000 (one-time)
    • Subscription product: "ISO 19650 Professional Monthly" — $500/month
    • Description: 3 projects, 25 users, 50GB, UK+IE+AU, Document+Model compliance

    Enterprise:

    • Setup product: "ISO 19650 Enterprise Setup" — $6,000 (one-time)
    • Subscription product: "ISO 19650 Enterprise Monthly" — $1,000/month
    • Description: Unlimited projects, unlimited users, 500GB, All annexes, Full compliance

Task 5: Configure CRM Pipeline

Create pipeline stages:

  1. Lead (new inquiry / free trial signup)
  2. Qualified (confirmed need, budget, timeline)
  3. Demo Booked
  4. Proposal Sent
  5. Negotiation
  6. Won
  7. Lost (with lost reason tracking)

Task 6: Configure Stripe Payment Acquirer

  1. Create Stripe account for STRUXIO (if not exists)
  2. Configure Odoo Stripe payment acquirer
  3. Enable for Website Sale and Subscriptions
  4. Test with Stripe test mode

Task 7: Configure Knowledge Base

Create initial articles:

  1. "What is ISO 19650?" — Public article for client onboarding
  2. "Understanding Your CDE" — Public article explaining the 4-state workflow
  3. "File Naming Conventions" — Public article with examples per National Annex
  4. "STRUXIO Internal: Rules Database" — Internal article (staff only)

Acceptance Criteria

Execution Notes

This ticket is primarily manual Odoo admin work done by the Founder through the Odoo.sh web UI. No code changes required — this is all configuration via the Odoo interface.

For tasks that need Python module development (custom CDE logic, IFC integration), separate tickets will follow.

Test

# Verify Odoo.sh is accessible
curl -s -o /dev/null -w "%{http_code}" https://struxio-platform-main-29652199.dev.odoo.com
# Expected: 200

# After module installation, verify via Odoo XML-RPC (optional):
# python3 -c "import xmlrpc.client; print(xmlrpc.client.ServerProxy('https://struxio-platform-main-29652199.dev.odoo.com/xmlrpc/2/common').version())"