The Standard VTU 4-Page Synopsis Structure
In Visvesvaraya Technological University (VTU) Belagavi and premier autonomous engineering institutions across Karnataka (such as RVCE, BMSCE, PES, MSRIT, Dayananda Sagar, NIE, and Siddaganga), the Phase-1 Project Synopsis is the formal gateway document. A rejected synopsis delays your hardware procurement by weeks and damages your internal assessment (IA) score.
Review committees enforce a strict 4 to 5 page budget. A disorganized 15-page document is rejected immediately. Adhere strictly to the university formatting specifications:
• Font Family & Sizing: Times New Roman; Main headings 14pt Bold Title Case; Subheadings 12pt Bold; Body text 12pt Regular.
• Spacing & Margins: 1.5 line spacing throughout; Left margin 1.25 inches (to allow binding); Right, Top, and Bottom margins exactly 1.0 inch.
• Header & Footer: University logo and college name on top header; "Department of [Branch] Engineering, 2026–2027" with page numbering "Page X of Y" in footer.
• Mandatory Document Sections: 1. Project Title & Batch Details, 2. Introduction & Background, 3. Problem Statement & Quantified Objectives, 4. Literature Survey (Minimum 4 IEEE papers), 5. Proposed System Block Diagram, 6. Hardware & Software Requirements (BOM), 7. Methodology & Work Plan (Gantt Chart), 8. Expected Societal / Industrial Outcomes, 9. References (IEEE citation standard).
Formulating an Unrejectable Problem Statement & Objectives
The number one reason college project coordinators reject initial synopses is "Vague or Generic Problem Statement." If your proposal sounds like a high school science fair project ("To build a smart home using Arduino to help elderly people"), it will be rejected on sight.
To pass review committees on the first try, your problem statement must include: 1) The existing engineering bottleneck, 2) The proposed technological intervention, and 3) Quantifiable target performance metrics.
| Rejected Generic Proposal | Upgraded VTU-Approved Problem Statement | Key Engineering Metric |
|---|---|---|
| Smart irrigation system using IoT | Distributed Micro-Climate Telemetry Network with Multi-Depth Soil Moisture Probing and LoRa Link Budget Optimization | Packet transmission range > 2 km; Sub-GHz RF link; Battery endurance > 90 days on 2S 18650 Li-ion cells. |
| Accident detection system using Arduino and GPS | Vehicle Impact Telemetry System with 6-Axis IMU Crash Kinematics Logging, CAN Bus Integration, and Instantaneous Fallback Cellular SMS | Crash detection threshold > 4.5G; Alert latency < 3.5 seconds; Hardware brownout tolerance down to 2.8V. |
| Solar tracking panel using LDR and Servo | Dual-Axis MPPT Solar Irradiance Maximizer with Active Current Shunt Telemetry and FreeRTOS Motor Step Tracking | Power generation efficiency increase of ≥ 28% over static mounts; Standby parasitic power < 120mW. |
The IEEE Literature Survey & Research Gap Table
Your literature survey is evaluated for academic rigor. University guidelines mandate citing between 4 and 6 papers published in IEEE Transactions, IEEE Access, Springer, or Elsevier between 2023 and 2026.
Do not simply copy-paste paper abstracts into bullet points. College review panels expect a synthesized Literature Review Comparison Matrix highlighting the specific limitation (Research Gap) that your project solves:
1. Paper Citation: Author name, paper title, journal/conference name, year of publication.
2. Methodology Utilized: What algorithms, microcontrollers, or cloud pipelines did the authors implement?
3. Key Results: What throughput, accuracy, or efficiency did they achieve?
4. Research Gap / Limitation: Where did their system fail? (e.g. "Authors relied on high-cost industrial PLCs ($1,200) without wireless edge battery operation", or "Simulation conducted in MATLAB without physical circuit validation").
5. How Our Project Bridges the Gap: Your specific hardware adaptation (e.g. "Our system ports the detection algorithm to an ESP32-S3 microcontroller costing under ₹600 with local INT8 inference").
Layered System Architecture & Hardware Block Diagram
Your block diagram is the most heavily scrutinized graphic in your 4-page synopsis. Hand-drawn sketches or messy MS Paint boxes with single-headed arrows are guaranteed red flags.
A professional engineering system block diagram must clearly depict four structural architectural layers:
1. Sensing & Input Layer: Explicitly label exact sensor part numbers (e.g. DHT22, MPU6050, ACS712-30A, VL53L0X Time-of-Flight) and bus connections (I2C SDA/SCL, SPI MOSI/MISO/SCK, Analog ADC0).
2. Compute & Processing Core: Specify the exact microcontroller board (e.g. ESP32-S3 Xtensa Dual-Core @ 240MHz, STM32F401 Black Pill ARM Cortex-M4) and real-time operating system / firmware environment.
3. Power Distribution Rail: Differentiate high-current motor/actuator rails (7.4V/12V) from sensitive logic rails (3.3V/5.0V) using buck converters (LM2596/MP1584) and opto-couplers.
4. Telemetry, Actuation & Output Layer: Differentiate physical actuators (relays, stepper motors, solenoids) from wireless telemetry antennas (SX1276 LoRa, 2.4GHz Wi-Fi/BLE) and user interfaces (0.96" OLED display, MQTT Cloud Broker).
Bill of Materials (BOM) & Sourcing Feasibility
College guides reject proposals where students specify exotic components that cannot be procured in India or exceed reasonable student budgets. Including a verified Bill of Materials (BOM) with active Indian distributor pricing proves feasibility instantly.
Calculate your budget using our free Live Hardware BOM Cost Estimator to get realistic distributor prices from Robu.in, Quartz Components, and Zbotic:
| Component Description | Part Number / Specification | Sourcing Distributor | Approximate Unit Cost (INR) |
|---|---|---|---|
| Microcontroller Unit | ESP32-S3 WROOM-1 (N16R8, 16MB Flash, 8MB PSRAM) | Robu.in / Robocraze | ₹620 – ₹750 |
| Precision Multi-Sensor Unit | BME280 (I2C Digital Temp, Humidity, Pressure) | Quartz Components | ₹380 – ₹450 |
| Long-Range RF Transceiver | Ai-Thinker Ra-02 LoRa SX1278 (433MHz/868MHz) | Zbotic / Ktron | ₹390 – ₹490 |
| Regulated DC-DC Buck Converter | MP1584EN Ultra-Small 3A Step-Down Module | Robu.in | ₹65 – ₹95 |
| Rechargeable Power Pack | 2S 18650 2600mAh Li-ion Cells with 2S 10A BMS Board | Local Distributor / Zbotic | ₹550 – ₹750 |
| Custom 2-Layer Prototype PCB | 100mm x 100mm FR4 HASL Double-Sided Board | JLCPCB / PCBPower | ₹800 – ₹1,200 |
Implementation Methodology & Milestone Timeline
Section 7 of your synopsis outlines the step-by-step technical methodology and the Gantt chart timeline spanning the entire semester (Weeks 1 to 16):
• Phase 1 (Weeks 1–4): Literature Survey & Hardware Requirement Freezing: Procuring components, reading datasheets, breadboard validation of individual sensor I2C addresses.
• Phase 2 (Weeks 5–8): Firmware Development & Subsystem Testing: Developing modular C++/Python drivers, FreeRTOS task scheduling, local Wi-Fi/MQTT telemetry streaming, and Phase-1 guide review presentation.
• Phase 3 (Weeks 9–12): Hardware System Integration & Perf-Board Soldering: Transitioning breadboard circuits to soldered perf-boards or custom PCBs, power rail load testing under stall current, chassis fabrication.
• Phase 4 (Weeks 13–16): Bench Validation, Report Documentation & External Viva Defense: Finalizing experimental readings, error graphs, Turnitin plagiarism check (< 10%), project exhibition, and university viva demonstration.
Review Committee Red Flags & Pre-Submission Checklist
Before submitting your printed synopsis document to your Head of Department (HOD) or project coordinator, verify every point on this checklist:
• Plagiarism Check: Run your synopsis draft through Turnitin or DrillBit. Ensure similarity score is under 10% (excluding references). Guide committees reject any synopsis with high similarity.
• No Pre-Made Toy Kits: Ensure your title and block diagram do not sound like pre-assembled SP Road kit modules. Highlight custom firmware, telemetry, or mathematical filtering.
• Clear Scope Boundary: Does your synopsis clearly demarcate where hardware stops and cloud/software starts? Avoid claiming you will build a complex hardware robot, an autonomous drone, an iOS app, and a custom blockchain in 12 weeks.
• Guide Signature & Acknowledgement: Never submit a synopsis directly to the coordinator without getting your internal guide’s preliminary signature on the rough draft.