5.1 Pre-Implementation Review & Finalization
-
Objective: Ensure all planning is complete, resources are secured, and the execution environment is safe and ready before starting the build/development.
-
Key Activities:
-
5.1.1 Revisiting Proposal & Design: Cross-check final approved design drawings, schematics, and specifications. Confirm all design calculations and simulations are validated.
-
5.1.2 Final BOM & Procurement:
-
Create a detailed Bill of Materials (BOM) with part numbers, specifications, quantities, and estimated/actual costs.
-
Procure all components, accounting for lead times and potential supplier issues.
-
-
5.1.3 Final WBS & Schedule: Finalize the Work Breakdown Structure (WBS) into actionable tasks. Develop a detailed Gantt chart with milestones, dependencies, and resource allocation.
-
5.1.4 Safety & Risk Assessment: Conduct a formal Job Safety Analysis (JSA) or Risk Assessment Matrix for all fabrication/assembly steps. Identify hazards (electrical, mechanical, chemical) and define mitigation controls (PPE, guards, procedures).
-
5.1.5 Setup Environment: Prepare workspace (lab/workshop), install required software (IDE, simulation tools), calibrate test equipment (oscilloscope, multimeter), and set up version control repository (e.g., Git).
-
[!TIP] Common Pitfall: Skipping a final design review against the original proposal can lead to scope creep. Always have your guide sign-off on the final BOM and WBS.
5.2 Fabrication, Assembly, or Development
-
Objective: Transform design documents into a physical prototype or functional software system through controlled processes.
-
Key Processes:
-
5.2.1 Component Fabrication:
-
Traditional: Machining (turning, milling), welding, sheet metal work.
-
Additive: 3D Printing (FDM, SLA, SLS) for complex prototypes.
-
Electronics: PCB Etching/Manufacturing (tracing, drilling, soldering).
-
-
5.2.2 System Assembly & Integration: Follow assembly sequences. Use standard operating procedures (SOPs). Implement modular design principles to integrate subsystems (mechanical, electrical, software) step-by-step.
-
5.2.3 Hardware Interfacing: Connect sensors to controllers (e.g., Arduino, Raspberry Pi, PLC), actuators to drivers. Pay attention to signal conditioning, power requirements, and communication protocols (I2C, SPI, UART, CAN).
-
5.2.4 Software Development: Write clean, commented code. Use modular programming. Implement version control (Git) with meaningful commit messages. Adhere to coding standards.
-
5.2.5 Managing Design Modifications: Record all deviations from original design ("redlining" on drawings). Justify and document the reason for change (e.g., part unavailability, performance issue). Get guide approval for major changes.
-
[!TIP] Exam Focus: Be prepared to explain your fabrication process choice (e.g., "Why 3D printing over injection molding?"). Justify with factors like cost, lead time, and geometric complexity.
5.3 Testing, Calibration, and Validation
-
Objective: Systematically verify that each component and the integrated system meets the design requirements and specifications.
-
Structured Approach:
-
5.3.1 Develop Test Plan: Define Test Objective, Test Setup Diagram, Test Procedure, Pass/Fail Criteria, and Safety Precautions for each test.
-
5.3.2 Unit Testing: Test individual modules in isolation (e.g., test motor driver circuit separately from sensor).
-
5.3.3 Integrated System Testing: Connect all subsystems and test overall functionality. Use black-box (input/output) and white-box (internal state) testing methods.
-
5.3.4 Calibration: For measurement systems (load cell, temperature sensor), perform calibration against a known standard. Generate a calibration curve (often linear: $$\displaystyle y = mx + c $$) and determine accuracy and precision.
-
5.3.5 Performance Validation: Compare measured performance (e.g., speed, force, efficiency, response time) against initial design goals/specifications. Use tables/graphs for clear comparison.
-
5.3.6 Troubleshooting: Use systematic methods: Divide-and-Conquer (isolate subsystem), Signal Tracing (follow signal path), Component Swapping. Maintain a debugging log.
-
\boxed{\text{Test Plan Structure:} \ \text{1. Objective} \ \text{2. Apparatus} \ \text{3. Procedure} \ \text{4. Observations} \ \text{5. Results vs. Specs} \ \text{6. Conclusion}}
5.4 Data Collection, Experimentation & Analysis
-
Objective: Generate meaningful experimental data to characterize the prototype's performance and validate theoretical models.
-
Process Flow:
-
Design Experiment: Identify independent (input) and dependent (output) variables. Determine sample size and test conditions (range of inputs).
-
Conduct Trials: Perform repeated trials for statistical reliability. Control all variables except the independent one.
-
Data Logging: Use digital tools (data acquisition systems, Arduino Serial Plotter, Python scripts) for automated, timestamped logging. Maintain a raw data sheet.
-
Preliminary Analysis:
-
Use Microsoft Excel for basic plotting and trendlines.
-
Use MATLAB/Python (NumPy, Matplotlib, Pandas) for advanced analysis, curve fitting, and statistical measures (mean, standard deviation).
-
-
Interpretation: Compare experimental curves with theoretical/simulated predictions. Calculate percentage error. Identify sources of discrepancy (friction, unmodeled dynamics, measurement error).
-
[!TIP] Critical: Always state the uncertainty in your measurements (e.g., "Speed = 1.25 ± 0.05 m/s"). This shows scientific rigor.
5.5 Project Management During Execution
-
Objective: Keep the project on track regarding time, cost, and scope while managing team dynamics and emerging risks.
-
Key Management Tasks:
-
5.5.1 Progress Tracking: Update Gantt chart weekly. Use a traffic light system (Green=On Track, Yellow=At Risk, Red=Delayed) for tasks.
-
5.5.2 Budget Management: Maintain a cost tracking sheet vs. approved budget. Log all expenses (component receipts).
-
5.5.3 Team Communication: Hold regular weekly team meetings with agenda and minutes. Use collaboration tools (WhatsApp group, Trello, Slack) for daily updates.
-
5.5.4 Risk Management: Maintain a Risk Register. For new risks, assess Probability (P) and Impact (I), calculate Risk Score (P×I), and define mitigation action.
-
5.5.5 Contingency Handling: Have a "Plan B" for critical path items (e.g., alternative supplier, simpler design fallback). Document all issues and decisions.
-
5.6 Documentation & Record Keeping (Ongoing)
-
Objective: Create an auditable, continuous record of the project's evolution for reproducibility and final reporting.
-
Essential Documents:
-
5.6.1 Project Logbook/Lab Notebook: Bound, paginated, ink-only. Daily entries: date, tasks done, observations, problems, data sketches. Sign and date each entry. This is a legal/ethical document.
-
5.6.2 Design Change Log: Formal document (or redlined drawings) recording every change: Date, Description of Change, Reason, Approved By.
-
5.6.3 Instructions & Manuals: Draft Assembly Instructions (with exploded diagrams) and a preliminary User Manual (operation, safety, maintenance).
-
5.6.4 Test Reports: For each major test, compile a formal report following the Test Plan Structure (from 5.3.1).
-
5.6.5 Version Control: All digital files (CAD, code, docs) in a Git repository with semantic versioning (v1.0, v1.1). Use branches for experiments.
-
[!TIP] Golden Rule: "If it's not written down, it didn't happen." Your logbook is your single most important evidence for viva.
5.7 Ethics, Safety, and Sustainability in Practice
-
Objective: Conduct the project responsibly, ensuring safety, honesty, and minimal negative impact.
-
Practical Application:
-
5.7.1 Safety Protocols: Strictly follow lab/workshop rules (no loose clothing, proper PPE, lockout-tagout for machinery). Know emergency procedures (first-aid, fire extinguisher).
-
5.7.2 Data Ethics: Never fabricate, falsify, or selectively omit data. Present results honestly, including failures and anomalies. Attribute all sources.
-
5.7.3 Environmental Impact: Consider material choice (recyclability, toxicity), energy consumption of prototype, and waste disposal (e-b waste, chemicals). Document your considerations.
-
5.7.4 Social Implications: Briefly assess how your project could affect society (job creation, accessibility, privacy concerns if IoT-based).
-
5.8 Preparing for Project - II & Final Deliverables
-
Objective: Use the end of Semester I to synthesize progress, identify gaps, and plan for the final semester.
-
Deliverables for Mid-Term/Viva:
-
5.8.1 Prototype Assessment: Honestly evaluate if you have a functional prototype or a working software model. What percentage of core functionality is achieved?
-
5.8.2 Future Work/Gaps: List specific, actionable items for Project-II (e.g., "Improve accuracy by implementing Kalman filter," "Conduct fatigue testing," "Develop mobile app interface").
-
5.8.3 Interim/Progress Report Draft: Structure should include: Introduction, Literature Review (summary), Methodology (detailed implementation), Results (preliminary data), Challenges & Solutions, Revised Timeline, Conclusion.
-
5.8.4 Mid-Term Presentation Prep:
-
Demo: Have a reliable, short demonstration (even if limited).
-
Charts: Prepare clear graphs comparing target vs. actual performance.
-
Narrative: "We aimed for X. We achieved Y. The main challenge was Z, which we solved by..."
-
-
5.8.5 Plan for Final Semester: Outline remaining testing, comprehensive data collection, final documentation (final report, technical paper), and final viva preparation.
-
\boxed{\text{Mid-Term Viva Key:} \ \text{1. Working Demo (Best)} \ \text{2. Clear Data Charts} \ \text{3. Honest Problem-Solving Story} \ \text{4. Concrete Plan for Next Semester}}