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

Post a Comment

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...
1 comment
Read more

"Depth-Guard" – 3D Spatial Occupancy monitor Challenge -2

  Project Title: "Depth-Guard" – 3D Spatial Occupancy Monitor 1. The Problem In a smart warehouse, a robot needs to know if a loading zone is clear or occupied. A 2D camera alone can’t tell the difference between a "flat picture of a box" on the floor and an "actual 3D box." The Goal: Build a Python-based system that uses Computer Vision and Depth Perception (AI 3D) to identify objects and determine their 3D volume (Size) and Distance from the camera. 2. Intern Tasks Object Detection: Use a pre-trained model (like YOLOv8) to draw 2D boxes around objects. Depth Mapping: Use a depth estimation model (like MiDaS or a simulated Stereo-depth feed) to calculate how far each object is. Occupancy Logic: If an object is closer than 1 meter and larger than a specific volume, mark the zone as "BLOCKED." Alert System: Print a warning if the 3D space is too crowded. 3. Sample Datasets (Simulation) Since interns may not have 3D cameras (LiDAR/RGB-D), pr...
Post a Comment
Read more

Simple Virtual Waiting Room -Challenge 1

   Simple Virtual Waiting Room (VWR) 1. The Problem Our website can only handle 10 users per minute . If more than 10 people try to access it at once, the server will crash. We need a system that: Counts incoming users. Redirects "overflow" users to a waiting page. Admits them back to the main site one by one as space becomes available. 2. Intern Tasks Create a Gateway: A simple script that checks: if (active_users < 10) { allow } else { send to queue } . Build the Queue: Use a simple list (FIFO) to store user IDs. The Wait Page: A basic HTML page that says: "You are number X in line. Estimated wait: Y minutes." Admission Logic: Every 30 seconds, pull the next user from the queue and "admit" them. 3. Sample Datasets (Simulation) Provide these two datasets to the interns. They should write a script to "read" these files and simulate how their system reacts. Dataset A: The Traffic Surge (Input) This file simulates users arriving at the ...
Post a Comment
Read more