Prerequisites & Dependencies¶
This document outlines the external requirements and access permissions needed to kick off the building of the Pebble Business Orchestrator.
🔑 1. Identity & API Access¶
These are strictly required for the Sync Engine and Ingestion Layer to function.
| Source | Dependency | Requirement |
|---|---|---|
| Microsoft 365 | Azure AD App Registration | Client ID, Secret, and Tenant ID with Mail.ReadWrite and Mail.Send scopes. |
| Odoo / Zoho | Service Account | API Key / OAuth tokens with Lead creation and Contact write permissions. |
| Focus RT | API Gateway | Access to the REST/SOAP endpoint with Order Lookup capability. |
| Business Central | Environment ID | API access to the specific sandbox/production environment. |
📧 2. Communication Infrastructure¶
The orchestrator relies on mirroring active mailboxes.
- Master Mailboxes: Dedicated access or delegation for
sales@,logistics@, andtender@. - Sender Verification: Access to the company's "Authorized Senders" list to prevent spoofing of internal cards.
- Webhook Listeners: A public-facing URL (Staging) to receive real-time Push Notifications from Microsoft Graph.
📊 3. Master Data Samples¶
To train the Intent Engine and test the Prelead Ingestion, the following data samples are required:
- Historical Emails: 50-100 sample threads (anonymized) representing Sales Enquiries vs. Logistics queries.
- Prelead Sheets: Sample Excel/CSV files from current lead providers (e.g., IndiaMart, TradeIndia).
- Entity Masters: A dump of existing Customer/Vendor IDs from the ERP to test cross-linking logic.
🏗️ 4. Technical Infrastructure¶
| Component | Prerequisite | Notes |
|---|---|---|
| Technical Infrastructure | AWS / Azure / GCP VM | Minimum 4 vCPU, 16GB RAM for AI workers. |
| Local LLM (Ollama) | NVIDIA GPU (8GB+ VRAM) | Required for low-latency local model execution. |
| Domain & SSL | pebble.company.com |
Required for secure Webhook callbacks. |
| Storage (Object) | S3 / MinIO | For archiving email attachments and Tender documents. |
| LLM Credits | Azure OpenAI / Ollama | API Key (Cloud) or Local Endpoint (Ollama). |
🛡️ 5. Compliance & Security¶
- IP Whitelisting: The Pebble Orchestrator IP must be whitelisted in the ERP/CRM firewalls.
- Data Residency: Confirmation on whether email metadata can be stored in the cloud or must remain on-premise.
💰 6. Licenses & Subscriptions¶
Ensure the following accounts are active and have sufficient billing headroom:
- Microsoft 365 Business Standard: Required for mailbox API access.
- Azure/Google Cloud Credits: For running the AI workers (BERT/Vision).
- CRM Licensing: API access requires specific tiers in Odoo/Zoho (e.g., Enterprise/Pro).
- Plane.so (Self-Hosted): Open-source Kanban via Docker Compose. No license cost.
7. Plane.so Deployment (Kanban Board)¶
The Visual Kanban workspace uses Plane.so, a self-hosted open-source project management tool.
Quick Setup:
git clone https://github.com/makeplane/plane.git
cd plane
cp .env.example .env # Configure WEB_URL, API_URL
docker compose up -d
Infrastructure Requirements:
| Component | Requirement |
|---|---|
| VM/Server | 4 vCPU, 8GB RAM minimum |
| PostgreSQL | v15+ (included in Docker Compose) |
| Redis | v7+ (included in Docker Compose) |
| MinIO | Object storage for attachments (included) |
| Reverse Proxy | Nginx/Caddy for HTTPS termination |
| Internal DNS | e.g., kanban.internal.pebble.io |