Skip to main content

CRM

 

class Enquiry(db.Model):
    id = db.Column(db.Integer, primary_key=True)
    enquiry_no = db.Column(db.String(20))
    client = db.Column(db.String(100))
    end_user = db.Column(db.String(100))
    project_name = db.Column(db.String(200))
    # ... other columns ...

    def __init__(self, enquiry_no, client, end_user, project_name, ...):
        self.enquiry_no = enquiry_no
        self.client = client
        self.end_user = end_user
        self.project_name = project_name
        # ... initialize other columns ...

 

 

Sno    
Enquiry No ENQ/TMAE/10000/2024 Red color to increment
Client    
End User    
Project Name    
Project Stage BID to BID,BID to BUY,QUOTE DD
Supply of    
Region UAE,Iraq,Saudi,Oman,Bahrin DD
Sector Name O&G,Infrastructure,Power,Others,Steel,Utility,Water,Water & Electricity.Water Wsste water  
Business Unit    
Status Dropped,Quoted,  
Closing Date for Quote    
Quote Number    
Enquiry Received date    
Quotation Submitted Date    
Rework on a quote already submitted    
Revision Number    
Engineer Quoting    
Approving Manager    
Account Manager(if any)    
Estimated Value in USD    
Estimated Value in AED    
Estimated value for revision 0    
Estimated value for revision 1    
Estimated value for revision 2    
Estimated value for revision 3    
Estimated value for revision 4    
Status of Quote /Reason for Revision    
% of Winning Probablity    

 

Tables:

  1. Customers

    • customer_id (INT PRIMARY KEY): Unique identifier for the customer
    • company_name (VARCHAR(255)): Name of the customer company
    • contact_name (VARCHAR(255)): Name of the contact person at the customer company
    • email (VARCHAR(255)): Email address of the contact person
    • phone_number (VARCHAR(20)): Phone number of the contact person
    • address (TEXT): Billing and/or shipping address of the customer
  2. Contacts (Optional - Can be linked to Customers table for multiple contacts)

    • contact_id (INT PRIMARY KEY): Unique identifier for the contact
    • customer_id (INT FOREIGN KEY REFERENCES Customers(customer_id)): Foreign key referencing the customer
    • first_name (VARCHAR(255)): First name of the contact person
    • last_name (VARCHAR(255)): Last name of the contact person
    • email (VARCHAR(255)): Email address of the contact person
    • phone_number (VARCHAR(20)): Phone number of the contact person
    • title (VARCHAR(255)): Title/designation of the contact person
  3. Products/Services

    • product_id (INT PRIMARY KEY): Unique identifier for the product or service
    • name (VARCHAR(255)): Name of the product or service
    • description (TEXT): Description of the product or service
    • unit_price (DECIMAL(10,2)): Price per unit of the product or service
    • category (VARCHAR(255)): Category of the product or service (e.g., Software, Hardware, Consulting)
  4. Quotes

    • quote_id (INT PRIMARY KEY): Unique identifier for the quote
    • customer_id (INT FOREIGN KEY REFERENCES Customers(customer_id)): Foreign key referencing the customer
    • created_date (DATETIME): Date and time the quote was created
    • expiry_date (DATETIME): Date and time the quote expires
    • total_price (DECIMAL(10,2)): Total price of the quote (sum of all line items)
    • status (VARCHAR(255)): Status of the quote (e.g., Draft, Sent, Accepted, Rejected)
  5. Quote_Items

    • quote_item_id (INT PRIMARY KEY): Unique identifier for the quote item
    • quote_id (INT FOREIGN KEY REFERENCES Quotes(quote_id)): Foreign key referencing the quote
    • product_id (INT FOREIGN KEY REFERENCES Products/Services(product_id)): Foreign key referencing the product or service
    • quantity (INT): Quantity of the product or service included in the quote
    • unit_price (DECIMAL(10,2)): Price per unit for the item in this specific quote (can be different from product price)
    • total_price (DECIMAL(10,2)): Total price for this item (quantity * unit_price)
  6. Bids (Optional - Can be an extension of Quotes table with additional fields)

    • bid_id (INT PRIMARY KEY): Unique identifier for the bid (can inherit from Quotes table if Bids are a specific type of Quote)
    • quote_id (INT FOREIGN KEY REFERENCES Quotes(quote_id)): Foreign key referencing the original quote (can be null if Bids are a separate entity)
    • competitor (VARCHAR(255)): Name of the competitor (if any)
    • bid_price (DECIMAL(10,2)): Total price offered in the bid
    • win_status (BOOLEAN): Flag indicating if the bid was won (optional)

Relationships:

  • A Customer can have many Quotes. (One-to-Many)
  • A Quote belongs to one Customer. (Many-to-One)
  • A Quote can have many Quote Items. (One-to-Many)
  • A Quote Item belongs to one Quote. (Many-to-One)
  • A Product/Service can be included in many Quotes. (Many-to-Many) (Implemented through Quote Items table)
  • A Contact can be linked to a Customer (Optional - One-to-Many)
  • A Quote can be converted to a Bid (Optional - One-to-One)

Comments

Popular posts from this blog

Telecom OSS and BSS: A Comprehensive Guide

  Telecom OSS and BSS: A Comprehensive Guide Table of Contents Part I: Foundations of Telecom Operations Chapter 1: Introduction to Telecommunications Networks A Brief History of Telecommunications Network Architectures: From PSTN to 5G Key Network Elements and Protocols Chapter 2: Understanding OSS and BSS Defining OSS and BSS The Role of OSS in Network Management The Role of BSS in Business Operations The Interdependence of OSS and BSS Chapter 3: The Telecom Business Landscape Service Providers and Their Business Models The Evolving Customer Experience Regulatory and Compliance Considerations The Impact of Digital Transformation Part II: Operations Support Systems (OSS) Chapter 4: Network Inventory Management (NIM) The Importance of Accurate Inventory NIM Systems and Their Functionality Data Modeling and Management Automation and Reconciliation Chapter 5: Fault Management (FM) Detecting and Isolating Network Faults FM Systems and Alerting Mecha...

The Silicon Race: AI Chips and the Future of Competition

  The Silicon Race: AI Chips and the Future of Competition The landscape of Artificial Intelligence (AI) is being reshaped at an unprecedented pace, and at its heart lies a furious competition in the development of specialized AI chips. These miniature marvels, whether powering vast data centers or enabling intelligence on the edge, are the silent workhorses transforming industries, enabling real-time decision-making, and pushing the boundaries of what AI can achieve. The stakes are immense, with the global AI chip market projected to surge from approximately $31.6 billion today to over $846 billion by 2035, highlighting an intense and evolving competitive arena. The Driving Force: Why Specialized AI Chips? Traditional CPUs, the general-purpose workhorses of computing, simply cannot meet the insatiable demands of modern AI workloads. The core operations of machine learning, particularly linear algebra and matrix multiplications, are inherently parallel. This led to the rise of s...

Medical education still in stone age?

## 🚨 ഉണരാനുള്ള സമയം: നമ്മുടെ മെഡിക്കൽ വിദ്യാഭ്യാസം ശിലായുഗത്തിൽ! ഇനി വേണ്ടത് #ടെക്എംബിബിഎസ് ഉം #ടെക്നഴ്സിംഗും! 💉🤖 ചൈനയിലെ **ഡോക്ടർമാരില്ലാത്ത എ.ഐ. കിയോസ്‌കുകളുടെ** (Doctorless AI Kiosks) ഒരു വീഡിയോ ഞാൻ പങ്കുവെക്കുന്നു (ചേർത്തിട്ടുണ്ട്). പ്രാഥമിക ആരോഗ്യ പരിചരണം എത്ര വേഗമാണ് സാങ്കേതികവിദ്യ മാറ്റിമറിക്കുന്നതെന്നതിന്റെ ഞെട്ടിക്കുന്ന ഉദാഹരണമാണിത്. ഇത് ഭാവിയിലേക്കുള്ള കാഴ്ചയല്ല—ഇത് **ഇപ്പോഴത്തെ യാഥാർത്ഥ്യമാണ്**. ആരോഗ്യ സംരക്ഷണ വിദ്യാഭ്യാസത്തിൽ സമൂലമായ മാറ്റം അനിവാര്യമാകുന്ന ഒരു സാങ്കേതിക മുന്നേറ്റത്തിനാണ് നമ്മൾ സാക്ഷ്യം വഹിക്കുന്നത്. എന്നിട്ടും **മെഡിക്കൽ കൗൺസിൽ ഓഫ് ഇന്ത്യ (MCI)** പോലുള്ള സ്ഥാപനങ്ങളും ലോകമെമ്പാടുമുള്ള വിദ്യാഭ്യാസ ബോർഡുകളും ഇപ്പോഴും പഴയ രീതിയിൽ തുടരുന്നു. എന്റെ മകൾ MBBS വിദ്യാർത്ഥിയാണ്. **1000 പേജുള്ള അനാട്ടമി പാഠപുസ്തകം കാണാപ്പാഠം പഠിച്ച്** പരീക്ഷ എഴുതാൻ അവൾ ഇപ്പോഴും നിർബന്ധിതയാവുകയാണ്. എന്നാൽ ലോകമെമ്പാടുമുള്ള AI കാര്യക്ഷമതയുടെ നിലവാരം ഇതാ: * **ഒരു എ.ഐ. ഡോക്ടറിന്** ലോകത്തിലെ എല്ലാ മനുഷ്യ ഡോക്ടർമാരെയും സഹായിക്കാൻ കഴിയും. * **ഒരു റോബോട്ടിക് നഴ്സിന്** 100 മനുഷ്യ നഴ്സു...