Major Project -I (ME-706) - Unit 4 Short Notes

4.0 Project Execution, Analysis, and Intermediate Documentation

This unit covers the active implementation phase of the major project, where planned work is executed, progress is monitored, data is analyzed, and intermediate documentation is prepared. The focus shifts from planning to doing, checking, and reporting.

4.1 Revisiting Project Foundations & Detailed Planning

Before deep execution, a final validation of the project's foundation ensures alignment.

• 4.1.1 Final Validation: Re-confirm the problem statement, objectives (SMART criteria), and scope (inclusions/exclusions) with the guide. Any deviation requires a formal change request.

• 4.1.2 Detailed Work Breakdown Structure (WBS): Hierarchical decomposition of the total scope into manageable work packages.

  | WBS Level | Description | Example (for a robotic arm project) | | :--- | :--- | :--- | | 1.0 | Project Title | Autonomous Robotic Arm | | 2.0 | Major Deliverable | Mechanical Structure | | 3.0 | Work Package | Arm Link Fabrication | | 4.0 | Task | CNC Milling of Link 1 |

• 4.1.3 Finalized Scheduling Tools:

  • Gantt Chart: Visual timeline of tasks, durations, dependencies, and milestones.

  • PERT Chart: Network diagram showing task sequences and dependencies.

  • Critical Path Analysis: The longest sequence of dependent tasks determining the project's minimum duration. Any delay on the critical path delays the entire project.

• 4.1.4 Resource Allocation Matrix: Assigns human resources (team members), materials, equipment, and budget to specific WBS elements. Often a RACI matrix (Responsible, Accountable, Consulted, Informed) clarifies roles.

• 4.1.5 Risk Management Plan Review: Re-evaluate the risk register.

  • Mitigation Strategies: Actions to reduce probability/impact (e.g., prototyping, parallel tasks).

  • Contingency Plans: "Plan B" if a high-impact risk occurs.

  • Fallback Plans: Last-resort actions for catastrophic risks.

[!TIP] Exam Focus: Be prepared to draw a simple WBS (2-3 levels) and a basic Gantt chart for a given project scenario. Define critical path and its importance.

4.2 Core Implementation & Development Phase

The hands-on phase of building, coding, or experimenting.

• 4.2.1 Methodology Execution: Follow the approved methodology (e.g., Agile sprints, Waterfall phases, Design of Experiments) step-by-step. Document every step.

• 4.2.2 Prototyping/Fabrication/Coding Milestones: Set and achieve tangible intermediate outputs (e.g., "functional prototype by Week 6," "complete algorithm module by Week 8").

• 4.2.3 Experimental Setup & Calibration:

  • Setup: Detailed schematic of apparatus, instruments, and connections.

  • Calibration: Procedure to ensure measurement accuracy (e.g., zeroing load cell, standard sample test). Document calibration certificates/factors.

  • Data Collection Procedure: Define independent/dependent variables, range, sampling rate, number of trials, and controls.

• 4.2.4 Managing Deviations & Change Control:

  • Deviation: Unplanned departure from baseline (e.g., component unavailable, result inconsistent).

  • Change Control Process: Formal process to modify scope/schedule/baseline:

    1. Identify & document change.

    2. Analyze impact (cost, time, quality).

    3. Seek approval from guide/committee.

    4. Communicate & update all project documents (WBS, Gantt, risk register).

[!TIP] Common Pitfall: "Scope creep" – uncontrolled addition of features/tasks. Always use the change control process.

4.3 Monitoring, Control, and Quality Assurance

Tracking progress and ensuring work meets standards.

• 4.3.1 Progress Tracking (Earned Value Management - EVM): Integrates scope, schedule, and cost.

  | Term | Definition | Formula | | :--- | :--- | :--- | | PV (Planned Value) | Budgeted cost for work scheduled by a date. | $$\displaystyle PV = BAC \times (Planned\ %\ Complete) $$ | | EV (Earned Value) | Budgeted cost for work actually performed. | $$\displaystyle EV = BAC \times (Actual\ %\ Complete) $$ | | AC (Actual Cost) | Actual cost incurred for work performed. | - | | CV (Cost Variance) | Budget vs. actual cost. | $$\displaystyle CV = EV - AC $$ | | SV (Schedule Variance) | Schedule performance. | $$\displaystyle SV = EV - PV $$ | | CPI (Cost Performance Index) | Cost efficiency. | $$\displaystyle CPI = \frac{EV}{AC} $$ | | SPI (Schedule Performance Index) | Schedule efficiency. | $$\displaystyle SPI = \frac{EV}{PV} $$ |

  • Interpretation: $$\displaystyle CV>0 $$, $$\displaystyle SV>0 $$, $$\displaystyle CPI>1 $$, $$\displaystyle SPI>1 $$ are favorable.

  • Forecast: $$\displaystyle EAC = \frac{BAC}{CPI} $$ (Estimate at Completion).

• 4.3.2 Quality Control (QC) Checks: Specific tests/inspections at milestones (e.g., dimensional check of fabricated part, unit test of code module, calibration verification). Use checklists.

• 4.3.3 Progress Reporting & Communication:

  • Regular Team Meetings: Daily stand-ups (Agile) or weekly syncs. Agenda: done, plan, blockers.

  • Progress Reports: Periodic (weekly/bi-weekly) written summaries for the guide.

  • Stakeholder Communication: Tailor detail level (technical for team, summary for guide/sponsor).

• 4.3.4 Team Dynamics: Address conflicts early. Use RACI to resolve accountability issues. Ensure equitable task distribution.

4.4 Intermediate Data Analysis & Interpretation

Transforming raw data into meaningful insights.

• 4.4.1 Data Processing: Organize raw data (tables, logs). Clean data (remove outliers, handle missing values). Use tools: Excel, Python (Pandas), MATLAB, R.

• 4.4.2 Preliminary Analysis:

  • Descriptive Statistics: Mean, median, standard deviation, range.

  • Graphical Tools: Line graphs (trends), bar charts (comparisons), scatter plots (correlations), error bars.

  • Basic Inferential Stats (if applicable): t-tests, ANOVA for comparing groups.

• 4.4.3 Comparison with Theory: Plot experimental vs. theoretical/predicted values. Calculate percentage error:

$$\%\ Error = \frac{|Experimental - Theoretical|}{Theoretical} \times 100$$

• 4.4.4 Troubleshooting Anomalies: Systematically investigate unexpected results:

  1. Check data collection procedure/logs.

  2. Verify instrument calibration.

  3. Review experimental setup for flaws.

  4. Consider unaccounted variables.

  5. Repeat key trials.

[!TIP] Key Skill: Always include error bars in graphs to show data variability/uncertainty.

4.5 Intermediate Documentation & Reporting

Formalizing progress for assessment.

• 4.5.1 Mid-Term/Progress Report Structure:

  | Section | Content | | :--- | :--- | | 1. Introduction | Recap problem, objectives, scope. | | 2. Literature Review Update | Any new relevant studies found. | | 3. Methodology | Detailed, replicable description of implementation. Include diagrams/schematics. | | 4. Results & Analysis | Preliminary data, graphs, tables, statistical analysis. This is the core section. | | 5. Discussion | Interpretation of results, comparison with theory, anomalies, lessons learned. | | 6. Conclusion & Future Work | Summary of achievements, revised objectives for next phase, clear next steps. | | 7. References | Proper citation (IEEE/APA). | | 8. Appendices | Code snippets, detailed calculations, raw data, drawings. |

• 4.5.2 Writing Effectively:

  • Methodology: Write in past tense, passive/active voice consistently. "The specimen was machined to..." or "We machined the specimen..."

  • Results: Present facts only, no interpretation. Use captioned figures/tables.

  • Discussion: Interpret what the results mean. Link back to objectives.

• 4.5.3 Project Logbook/Diary: Legal document. Daily/weekly entries: date, tasks done, observations, data collected, issues, next steps. Sign and date each entry.

• 4.5.4 Version Control (e.g., Git):

  • git init / git clone

  • git add <file> / git commit -m "message"

  • git push / git pull

  • Use branches for experimental features (git branch feature-x).

• 4.5.5 Mid-Term Presentation:

  • Slides: Title, Problem, Objectives, Methodology (key steps), Results (highlight), Discussion, Conclusion/Future Work, Q&A.

  • Oral: Rehearse. Be concise. Know your slides.

  • Q&A: Listen fully, admit if you don't know, offer to follow up.

4.6 Ethical, Safety, and Professional Considerations

Non-technical but critical aspects of engineering practice.

• 4.6.1 Laboratory/Workshop Safety:

  • Identify hazards (electrical, mechanical, chemical, thermal).

  • Use PPE (gloves, goggles, coat).

  • Know emergency procedures (shut-off, first-aid, fire extinguisher).

  • Lockout/Tagout (LOTO) for machinery maintenance.

• 4.6.2 Data Integrity & Plagiarism:

  • Do not fabricate or falsify data.

  • Do not copy code/text without attribution. Cite all sources.

  • Keep raw data and analysis files securely.

• 4.6.3 Professional Conduct: Punctuality, respectful communication, meeting deadlines, acknowledging team contributions.

• 4.6.4 Sustainability: Consider waste disposal, energy consumption of experiments, material choice (recyclability), and life-cycle impact during implementation.

4.7 Preparing for the Final Phase (Unit 5)

Using mid-term learnings to plan the final push.

• 4.7.1 Refine Objectives: Based on intermediate results, adjust objectives if necessary (e.g., "due to time, we will test only 3 materials instead of 5"). Document the reason.

• 4.7.2 Plan Final Validation & Testing:

  • Define final test plan: parameters, setup, acceptance criteria.

  • Plan for comprehensive data collection for final analysis.

  • Schedule consolidation time (writing, final assembly).

• 4.7.3 Outline Final Report/Dissertation: Start drafting Methodology (final version) and Introduction/Conclusion. The final report structure is similar to the mid-term but with complete, conclusive results and deeper discussion.

• 4.7.4 Plan Final Demonstration/Viva:

  • Demonstration: Ensure final prototype/system is robust and presentable. Prepare a 5-10 min demo script.

  • Viva: Anticipate questions on: choice of methodology, comparison with alternatives, limitations of work, future scope, and detailed understanding of every aspect of your project.

[!TIP] Final Preparation: The mid-term report/presentation is a checkpoint, not the finish line. Use feedback to strengthen the final submission. Start the final report's "Methodology" and "Results" sections early with finalized data.