A REPORT ON

“IMPLANT TRAINING”

DIPLOMA IN INFORMATION TECHNOLOGY

AFFILIATED TO MSBTE

Submitted By

Kunalsingh Pardeshi, Vaishnavi Gaikwad, Amulya Kulkarni, Dhruv

Thorat, Anushka Bahirat, Shivam Kotkar, Ayush Gudhekar, Savani
Patki

Under the guidance of

Prof.

DEPARTMENT OF INFORMATION TECHNOLOGY

PIMPRI CHINCHWAD POLYTECHNIC AKURDI,
PUNE.

2025-26

1
 Certificate of Completion of Industrial Training

Maharashtra State Board of Technical Education

Certificate of Completion
Of Industrial Training

This is to certify that Mr. Kunalsingh Pardeshi with enrollment No.

23211000429 has successfully completed Industrial Training (22057) in
Jayshree Pistons pvt Ltd from 02/06/2025 to 23/08/24 for partial
fulfilment towards completion of Diploma in Information Technology
from Pimpri Chinchwad Polytechnic Institute code 0056.

Ms. S. L. Mortale Dr. V. S. Byakod

Head of the Department Head of the Institute

SEAL OF INSTITUTE

2
 Certificate of Completion of Industrial Training

Maharashtra State Board of Technical Education

Certificate of Completion
Of Industrial Training

This is to certify that Mrs. Vaishnavi Gaikwad with enrollment No.

23211000490 has successfully completed Industrial Training (22057) in
Jayshree Pistons pvt Ltd from 02/06/2025 to 23/08/24 for partial
fulfilment towards completion of Diploma in Information Technology
from Pimpri Chinchwad Polytechnic Institute code 0056.

Ms. S. L. Mortale Dr. V. S. Byakod

Head of the Department Head of the Institute

SEAL OF INSTITUTE

3
 Certificate of Completion of Industrial Training

Maharashtra State Board of Technical Education

Certificate of Completion
Of Industrial Training

This is to certify that Ms. Amulya Kulkarni with enrollment No.

23211000495 has successfully completed Industrial Training (22057) in
Jayshree Pistons pvt Ltd from 02/06/2025 to 23/08/24 for partial
fulfilment towards completion of Diploma in Information Technology
from Pimpri Chinchwad Polytechnic Institute code 0056.

Ms. S. L. Mortale Dr. V. S. Byakod

Head of the Department Head of the Institute

SEAL OF INSTITUTE

4
 Certificate of Completion of Industrial Training

Maharashtra State Board of Technical Education

Certificate of Completion
Of Industrial Training

This is to certify that Mr. Dhruv Thorat with enrollment No.

23211000497 has successfully completed Industrial Training (22057) in
Jayshree Pistons pvt Ltd from 02/06/2025 to 23/08/24 for partial
fulfilment towards completion of Diploma in Information Technology
from Pimpri Chinchwad Polytechnic Institute code 0056.

Ms. S. L. Mortale Dr. V. S. Byakod

Head of the Department Head of the Institute

SEAL OF INSTITUTE

5
 Certificate of Completion of Industrial Training

Maharashtra State Board of Technical Education

Certificate of Completion
Of Industrial Training

This is to certify that Ms. Anushka Bahirat with enrollment No.

23211000498 has successfully completed Industrial Training (22057) in
Jayshree Pistons pvt Ltd from 02/06/2025 to 23/08/24 for partial
fulfilment towards completion of Diploma in Information Technology
from Pimpri Chinchwad Polytechnic Institute code 0056.

Ms. S. L. Mortale Dr. V. S. Byakod

Head of the Department Head of the Institute

6
 Certificate of Completion of Industrial Training

Maharashtra State Board of Technical Education

Certificate of Completion
Of Industrial Training

This is to certify that Mr. Shivam Kotkar with enrollment No.

23211000499 has successfully completed Industrial Training (22057) in
Jayshree Pistons pvt Ltd from 02/06/2025 to 23/08/24 for partial
fulfilment towards completion of Diploma in Information Technology
from Pimpri Chinchwad Polytechnic Institute code 0056.

Ms. S. L. Mortale Dr. V. S. Byakod

Head of the Department Head of the Institute

SEAL OF INSTITUTE

7
 Certificate of Completion of Industrial Training

Maharashtra State Board of Technical Education

Certificate of Completion
Of Industrial Training

This is to certify that Mr. Ayush Gudhekar with enrollment No.

23211000504 has successfully completed Industrial Training (22057) in
Jayshree Pistons pvt Ltd from 02/06/2025 to 23/08/24 for partial
fulfilment towards completion of Diploma in Information Technology
from Pimpri Chinchwad Polytechnic Institute code 0056.

Ms. S. L. Mortale Dr. V. S. Byakod

Head of the Department Head of the Institute

SEAL OF INSTITUTE

8
 Certificate of Completion of Industrial Training

Maharashtra State Board of Technical Education

Certificate of Completion
Of Industrial Training

This is to certify that Ms. Savani Patki with enrollment No.

23211000511 has successfully completed Industrial Training (22057) in
Jayshree Pistons pvt Ltd from 02/06/2025 to 23/08/24 for partial
fulfilment towards completion of Diploma in Information Technology
from Pimpri Chinchwad Polytechnic Institute code 0056.

Ms. S. L. Mortale Dr. V. S. Byakod

Head of the Department Head of the Institute

SEAL OF INSTITUTE

9
 ABSTRACT

At the diploma level in computer engineering, fulfilling the requirement set by MSBTE,
industrial training plays a significant role in imparting technical education. As part of
this training, students are expected to prepare and submit comprehensive reports upon
completion. These reports document the engineering experiences, professional practices,
as well as the acquisition of both TECHNICAL and NON-TECHNICAL knowledge and
skills during the 12-week industrial training at Jayshree Piston Pvt Ltd’s from
03/06/2024 to 23/08/2024.

Chapters 1 and 2 highlight the organizational setup, history, products, and departmental
functions of the industry, offering a strong understanding of real-world manufacturing
systems. Chapter 3 emphasizes the critical role of software (CAD, CAM, ERP, QMS) and
hardware (CNCs, VMCs, furnaces, die-casting machines) in precision piston production.
Chapter 4 provides a detailed account of the Skiora project, its architecture, features, and
real-world application in industrial security. Chapters 5 and 6 describe the rigorous testing
methodologies applied, alongside in-depth explanation of project code and design decisions.
Chapter 7 records the challenging experiences encountered—ranging from debugging issues
to workplace adaptation—and the lessons learned. Chapter 8 draws broad conclusions on
personal, technical, and industrial growth, while Chapter 9 presents references and sources
consulted.

The report goes beyond traditional industrial training by blending manufacturing exposure
with IT-based project implementation, thus offering a holistic experience in
multidisciplinary learning. It reflects growth not only in technical domains such as software
development, system integration, and industrial processes, but also in essential non-technical
skills like teamwork, documentation, communication, and adaptability.

10
 ACKNOWLEDGEMENT

I would like to take this opportunity to thank one and all that provided their valuable
advice and guidance without which this seminar would not have been completed. I thank
all who have helped me directly or indirectly but some in particular have to be singled
out since they have given me more than just guidance.

I wish to express thanks to my guide [Link] Lecturer in Department of Information

Technology for his support.

My profound thanks to Ms. S.L. Mortale, Head of the Department of Information

Technology for her invaluable advice and constant encouragement to complete this
Industry Training report in a successful manner.

I would like to express my deep sense of gratitude to our esteemed Principal,

[Link] for her encouragement.
GROUP MEMBERS

Roll. No. Class Enrolment No. Name of Student Signature

7 TY-IF(A) 23211000429 Kunalsingh

Ganeshsingh Pardeshi
61 TY-IF(A) 23211000490 Vaishnavi Ganesh
Gaikwaad
1 TY-IF(B) 23211000495 Amulya Anand
Kulkarni
2 TY-IF(B) 23211000497 Dhruv Pritam Thorat
3 TY-IF(B) 23211000498 Anushka Anniruddha
Bahirat
4 TY-IF(B) 23211000499 Shivam Mohan
Kotkar
8 TY-IF(B) 23211000504 Ayush Anil Gudhekar

13 TY-IF(B) 23211000511 Savani Sudeep Patki

11
 CONTENTS

Chapter Title Page No.

No.
1 Organizational structure of Industry and
General Layout

2 Introduction to Industry Organization(history,type of product

and services,turn over and number of employee etc.)

3 Overview of Major Software and Hardware Used in

Industry

4 Detailed Description of Projects

5 Testing Methodologies of Project

6 Detailed Project Code and Explanation

7 Special/Challenging experience encountered during training

if any

8 Conclusion

9 References / sources of information

12
CHAPTER 1: ORGANIZATION STRUCTURE OF INDUSTRY AND
GENERAL LAYOUT

1.1 INTRODUCTION TO ORGANIZATION STRUCTURE

Jayshree Piston Pvt Ltd’s setup lays out how everything’s arranged from people and machines to
who calls the shots. It’s what keeps things running smoothly across manufacturing, services, and
daily ops by splitting up jobs and making clear who handles what.
For a company like this one—which designs pistons, casts parts, machines them down to spec,
and runs quality checks—a solid structure isn’t optional. Without that clarity in roles and
departments slipping past each other you’d get bottlenecks fast. The real-world impact shows up
in a few key areas. Like communication between production teams and management staying tight
so orders don’t get lost in translation. Workflow moving without hiccups from casting furnaces to
machining stations then over to heat treatment bays. Decisions getting made quicker when
planning shifts or allocating equipment because everyone knows their lane.
Accountability’s another big part here. When you’ve got defined responsibilities for quality checks
or machine maintenance mistakes get caught faster. No overlaps no confusion over who dropped
the ball if something goes sideways during a production run.
The approach they take mixes traditional department setups—like having dedicated teams for
design vs machining—with project-based groups that form around specific client needs or
product lines. Basically it keeps expertise sharp in core areas while still letting different units
collaborate when required. You know how some companies get stuck in silos this hybrid model
tries to avoid that by keeping communication channels open between functions without losing
focus on specialized tasks.
1.2 OVERVIEW OF DEPARTMENTS

The organizational structure of Jayshree Piston Pvt. Ltd. Is divided into specialized departments,
each focusing on a critical area of business and manufacturing. These include:

1. Human Resources (HR Department)

2. Sales & Marketing Department
3. Procurement & Outsourcing Departments
4. Accounts & Finance Department
5. Production/Engineering Department
6. Quality Assurance Department
7. Maintenance Department
8. Research & Development (R&D) Department

13
 9. Store & Inventory Department
10. Designing Department
11. Management Department

1.3 DEPARTMENTAL ROLES AND RESPONSIBILITIES

1.3.1 Human Resources (HR Department)

Handles employee recruitment, training programs, workplace culture stuff, and making sure rules
get followed. Main tasks cover finding skilled workers like machine operators and engineers
through hiring efforts. They set up training for CNC stuff, casting processes, safety protocols too.
Also keeps an eye on labor laws compliance and industry standards meeting requirements. Does
performance reviews sometimes and helps with career growth plans for staff members. The big
picture here is making sure there's enough trained people around to keep production running
smooth without hiccups.

1.3.2 Sales & Marketing Department

Serves as the main link between the company and its clients you know, automotive companies
and industrial buyers mostly. Their gig includes hunting down new customers both locally and
overseas markets. Putting together price quotes gets technical sometimes when making bids or
proposals for projects they handle customer relationships from start to finish basically managing
orders till delivery happens. Works closely with production teams to coordinate dispatch
schedules properly without delays messing things up. At the end of the day this department
makes sure what gets made matches what customers actually want to buy.

1.3.3 Procurement & Outsourcing Department

Manages sourcing materials and outsourcing certain jobs when needed like machining or casting
work maybe. Mainly deals with picking suppliers and buying raw materials think aluminum alloys
steel that sort of thing they check quality before anything hits the production floor obviously
handles subcontracting processes too if there's coating work or heat treatment being farmed out
sometimes significance-wise this keeps costs under control while making sure production doesn't
get stuck waiting for parts or materials.

1.3.4 Accounts & Finance Department

Looks after money matters across all operations from daily transactions to big picture financial
planning deals with payments coming in and going out handles tax compliance stuff like GST
filings income tax regulations budget forecasting for equipment purchases labor costs too their

14
role really boils down to keeping projects profitable while making sure the company's finances
stay stable over time even when market conditions get shaky.

1.3.5 Production/Engineering Department

Runs the technical side of things at Jayshree Piston basically oversees all manufacturing
operations they manage 7 gravity die casting machines 2 pressure die casting units 8 VMCs 19
CNC machines plus heat treatment furnaces precipitation units too supervises piston machining
processes finishing work polishing stages makes sure everything runs efficiently at each step
without quality slipping their work directly impacts whether orders get shipped on time which
obviously affects how happy clients end up being with the whole deal
1.3.6 Quality Assurance Department

Handles all quality control stuff. They check incoming materials, castings, final products. Run
hardness tests and measure every dimension twice. Make sure everything matches ISO/TS certs
before customers audit. Big thing here is catching defects early so bad pistons don't slip through.

1.3.7 Maintenance Department

Keeps the machines alive basically. Does regular checkups on CNCs and furnaces, fixes stuff
when it breaks. Their main job is cutting downtime by having spare parts ready and monitoring
equipment health 24/7. Without them the whole production line grinds to a halt you know

1.3.8 Research & Development (R&D) Department

All about coming up with new piston designs that last longer or save fuel. They experiment with
lightweight metals and special coatings in the lab. Works closely with production teams to turn
concepts into actual parts. This department's why the company stays ahead of competitors honestly

1.3.9 Store & Inventory Department

Manages warehouses full of aluminum ingots, machine parts, finished pistons. Keeps digital
records of what comes in and goes out daily. Their biggest win is making sure production never
stops because someone ran out of materials oh and they sync up with sales teams for shipping
schedules.
1.3.10 Designing Department

Turns engineering specs into manufacturing blueprints using CAD software all day does stress
tests simulating extreme heat and pressure scenarios provides precise machining instructions for
CNC operators Basically creates the roadmap for how each piston gets built.

15
1.3.11 Management Department

Big picture stuff here They set company goals handle expansion plans decide where to invest
money Also create performance targets for other departments Ultimately responsible for keeping
the whole operation profitable year after year Its strategic decisions that keep the lights on long-
term

1.4 General Organization Layout

Facility locations include the main manufacturing plant where they handle casting machining and
finishing work Then theres a separate heat treatment section with housing heat treatment furnaces
and precipitation setups The admin block houses HR finance sales and management all in one
spot R&D and design offices focus on product development and innovation Storage areas handle
raw materials on one end and finished goods ready for dispatch

Workflow starts when a client order comes in and gets approved First step is design where R&D
teams draft piston specs and blueprints Raw material sourcing comes next which goes through
strict inspection processes They use gravity or pressure die casting methods depending on
requirements Machining happens next using CNC machines VMCs lathes you know standard
equipment After that parts go through heat treatment cycles and surface finishing Quality checks
run dimensional tests pressure tests before anything moves forward Final stage involves packaging
everything up and shipping out

Space allocation breaks down like this You've got the raw material yard holding metal alloys and
steel stock Casting bays pack gravity die machines and pressure casting units Machining areas
have rows of CNCs alongside vertical machining centers Heat zones run furnaces nonstop to
tweak material properties Inspection stations dot the production floor with testing gear everywhere
Finished products get stored in locked sections until dispatch Teams move stuff through this layout
daily kinda like clockwork once you get the rhythm down

16
CHAPTER 2: INTRODUCTION TO INDUSTRY / ORGANIZATION

2.1 BACKGROUND OF JAYSHREE PISTONS [Link].

Established in [Year, e.g., 1995/2000], Jayshree Pistons Pvt. Ltd. is a reputed name in the
automotive components industry, specializing in the design, manufacturing, and supply of
precision-engineered pistons, piston rings, and related engine parts. The company caters to a
wide range of industries including automotive, agricultural machinery, industrial engines, and
heavy-duty equipment manufacturers.

The company is headquartered in [City, State], with a state-of-the-art manufacturing facility

equipped with modern CNC machining centers, advanced casting equipment, precision
measuring instruments, and quality testing laboratories. Jayshree Pistons Pvt. Ltd. has built a
strong reputation for reliability, product innovation, and customer-focused solutions.

Over the years, the company has established itself as a trusted supplier to leading automobile
manufacturers and OEMs (Original Equipment Manufacturers) in India and abroad. By
continuously investing in R&D and adopting global best practices, the company ensures high
standards of performance, durability, and fuel efficiency in its piston technology.

2.2 HISTORY AND GROWTH

Since its inception, Jayshree Pistons Pvt. Ltd. has grown steadily by focusing on quality,
innovation, and customer satisfaction.

Initial Phase: Started with a small-scale piston manufacturing unit catering mainly to local
automobile workshops and spare part dealers.

Expansion Phase: With increasing demand, the company expanded its product portfolio to piston
rings, cylinder liners, and connecting rods, entering into partnerships with major OEMs.

Technological Advancement: Adoption of CAD/CAM technology, CNC machining, automated

casting, and computer-aided quality control.

17
Global Presence: Export of products to international markets in Asia, Middle East, and Africa.

Current Status: Recognized as a mid-sized enterprise with a workforce of over [approximate

number, e.g., 250–500 employees], ISO-certified processes, and annual turnover in crores of
rupees.
The company’s growth reflects its strong foundation in precision engineering and its adaptability
to changing industry trends such as emission norms, lightweight design, and sustainability.

2.3 PRODUCT AND SERVICES

Jayshree Pistons Pvt. Ltd. offers a wide range of products and engineering services tailored for
the automotive and industrial sectors.
2.3.1 Core Products:

Pistons: Manufactured using aluminum alloy and cast iron for two-wheelers, passenger vehicles,
and heavy commercial vehicles.

Piston Rings: Designed for high efficiency, durability, and reduced oil consumption.

Cylinder Liners: High wear-resistance and precision finish for long engine life. Connecting
Rods: High strength components for stable engine operation. Customized Components:
Special parts manufactured as per customer specifications.

2.3.2 Engineering Services:

Product design and development using CAD/CAM tools.

Prototype manufacturing and testing.

OEM collaboration for custom engine solutions. Continuous improvement

and cost-optimization programs.

18
2.4 TURNOVER AND MARKET PRESENCE

Jayshree Pistons Pvt. Ltd. has shown consistent financial growth over the years. With a focus on
both domestic and export markets, the company has maintained strong relationships with
automobile giants and industrial equipment manufacturers.
Domestic Market: Supplies to leading automotive companies and after-sales service markets
across India.
Export Market: Supplies precision pistons and engine components to over 15+ countries,
competing with international standards.
Annual Turnover: Estimated turnover of more than INR [insert approximate figure, e.g., 150–200
Crores], reflecting strong demand and market stability

2.5 NUMBER OF EMPLOYEE

The company employs a highly skilled workforce of engineers, technicians, machine operators,
and quality control specialists. Currently, Jayshree Pistons Pvt. Ltd. has an estimated workforce
of [250–500 employees], out of which a significant proportion are qualified mechanical
engineers, R&D experts, and production managers.

The HR policies of the company emphasize skill development, safety, and employee well-being.
Regular training sessions are conducted on lean manufacturing, Six Sigma, Kaizen, and quality
improvement techniques, ensuring that the workforce remains updated with global standards.

2.6 COMMITMENT TO INNOVATION SUSTAINABILITY

Jayshree Pistons Pvt. Ltd. is committed to sustainable growth by adopting eco-friendly

manufacturing practices and focusing on innovation.
Innovation: Continuous investment in R&D for lightweight pistons, improved fuel efficiency, and
emission reduction.
Sustainability: Use of recyclable alloys, waste reduction systems, and energy-efficient machinery.
Quality Certification: ISO 9001:2015 and IATF standards compliance for quality management.
Digital Transformation: Adoption of ERP systems, automated testing equipment, and digital
monitoring of production lines

19
2.7 SUMMARY
Jayshree Pistons Pvt. Ltd. stands as a trusted name in precision piston and engine component
manufacturing. The company’s steady growth, advanced technological setup, skilled workforce,
and commitment to innovation have enabled it to remain competitive in the automotive industry.
With a strong foundation and vision for global expansion, Jayshree Pistons Pvt. Ltd. continues to
deliver excellence in engine performance components, contributing significantly to the progress of
the Indian manufacturing sector.

20
CHAPTER 3 OVERVIEW OF MAJOR SOFTWARE AND HARDWARE
USED IN INDUSTRY
3.1 INTRODUCTION

Manufacturing these days runs on tech hardcore It decides whether you make stuff fast or let
quality slide Pistons especially need crazy exactness They take insane heat and pressure inside
engines all day every day
At Jayshree Piston its all about machines and code They’ve got heavy iron working 24/7 paired
with slick digital tools That combo lets them nail designs fast crank out parts without messing up
and check everything down to the micron
Here’s the thing when hardware and software click you get pistons that don’t quit Plus you save
cash somehow And still hit deadlines like clockwork
Coming up real talk on their gear The CNC rigs measuring gadgets 3D modeling stuff All the
systems that keep this place humming

3.2 MAJOR HARDWARE USED

3.2.1 Gravity Die Casting Machines (7 Units)

1. Produces pistons by pouring molten aluminum alloys into permanent metal molds using
gravity flow.

2. Provides superior surface finish and uniform metallurgical properties, which are essential for
durability.
3. Allows medium-to-large batch production with consistent dimensional accuracy.
4. Used for high-strength pistons in two-wheeler and four-wheeler segments.

3.2.2 Pressure Die Casting Machines (2 Units)

1. Injects molten aluminum into the mold cavity at very high pressure.
2. Results in high production rates and pistons with excellent accuracy.

3. Reduces machining requirements due to the near-net-shape casting process.

4. Used when tight tolerances and smooth finishes are critical for piston function.

21
3.2.3 Vertical Machining Centres (VMCs – 8 Units)

1. Multi-axis machines capable of milling, drilling, boring, and cutting complex geometries.
2. Essential for creating piston grooves, slots, and surface machining with high precision.
3. Equipped with automatic tool changers, reducing downtime and improving productivity.

4. Enhances flexibility in producing both standard and custom piston designs.

3.2.4 CNC Machines (19 Units)

1. Provide micron-level precision machining of piston surfaces, crowns, and skirts.

2. Programmable machines allow easy switching between different piston sizes and designs.
3. Ensures repeatability and consistency across thousands of components

4. Reduces human error and supports high-volume production efficiently.

3.2.5 Heat Treatment Furnace (1 Unit)

1. Performs processes like quenching and tempering to harden pistons.

2. Improves wear resistance, fatigue strength, and thermal stability.

3. Controlled atmosphere furnaces prevent oxidation and distortion.

4. Ensures pistons can withstand extreme engine conditions for long durations.

3.2.6 Precipitation Furnaces (2 Units)

1. Used for age-hardening aluminum alloys, vital for high-performance pistons.

2. Enhances mechanical properties like hardness, toughness, and strength.

3. Ensures pistons have long fatigue life even under continuous stress cycles.

4. Provides stable microstructure, which increases engine reliability.

22
3.3 MAJOR SOFTWARE USED

3.3.1 Computer-Aided Design (CAD) Software

1. Used for creating 2D and 3D piston designs with accurate dimensions.

2. Enables virtual testing of designs before manufacturing, reducing prototyping costs.

3. Allows engineers to experiment with different piston shapes, crown angles, and groove
placements.
4. Ensures manufacturing feasibility by directly linking designs with machining operations.

3.3.2 Computer-Aided Manufacturing (CAM) Software

1. Converts CAD models into CNC codes (G-code, M-code) for machining.
2. Optimizes tool paths, cutting speed, and feed rates to save time and reduce tool wear.

3. Ensures high repeatability and uniformity in machining piston grooves and surfaces.

4. Reduces setup time by automating machining processes for different piston models.

3.3.3 Computer-Aided Engineering (CAE) / Simulation Tools

1. Performs Finite Element Analysis (FEA) to predict piston performance under stress, heat, and
vibration.
2. Identifies potential failure points before physical testing.
3. Allows engineers to modify designs for greater fuel efficiency and strength.

4. Saves cost and time by reducing the need for multiple physical prototypes.

3.3.4 Enterprise Resource Planning (ERP)

1. Connects different departments like Sales, Production, Accounts, and Stores in a single
platform.
2. Helps with material planning, resource allocation, and order tracking.
3. Provides real-time data on stock levels, reducing chances of material shortages.

4. Improves transparency and decision-making across all management levels.

23
3.3.5 Quality Management System (QMS)

1. Maintains inspection records and ensures ISO/TS compliance.

2. Tracks and analyzes defect patterns for continuous improvement.
3. Reduces rejection rates by monitoring quality at every production stage.

4. Provides detailed quality reports for customer trust and audits.

3.4 INTEGRATION OF SOFTWARE AND HARDWARE

The efficiency of Jayshree Piston lies in its ability to integrate software with hardware.

CAD designs are directly converted into machining codes through CAM software, ensuring zero
errors during CNC machining.
Heat-treatment cycles are controlled using digital furnace software for consistent metallurgical
results.
ERP ensures real-time synchronization between sales orders, inventory, and production
schedules.
QMS integrates quality checks into the production line, ensuring that no defective piston
proceeds further.

3.5 CASE STUDY: APPLICATION IN A PISTON PROJECT

During a recent order for automotive pistons designed for high-performance two-wheelers, the
following workflow was implemented:

1. Design Phase – CAD software was used to model the piston crown to optimize combustion
efficiency.

2. Simulation Phase – CAE was applied to test the piston design under high RPM and thermal
loads.
3. Machining Phase – VMCs and CNC machines executed precision grooving and finishing.

4. Heat Treatment Phase – Pistons were treated in precipitation furnaces to enhance mechanical
strength.
5. Quality Phase – QMS software ensured dimensional accuracy and defect-free products.

6. Delivery Phase – ERP tracked the project progress and ensured on-time dispatch.

24
SUMMARY

Chapter 3 discussed the key hardware and software systems used at Jayshree Piston Pvt. Ltd. to
ensure precision and efficiency in piston manufacturing. The company is equipped with Gravity
and Pressure Die Casting Machines, CNCs, VMCs, Heat Treatment, and Precipitation Furnaces,
which form the core of its production process. Alongside this, advanced software tools such as
CAD, CAM, CAE, ERP, and QMS support design, machining, simulation, planning, and quality
management. The integration of these technologies creates a seamless workflow from digital
design to physical production, allowing the company to deliver high-quality, reliable pistons that
meet both domestic and international industry standards.

25
CHAPTER 4: DETAILED DESCRIPTION OF PROJECT

1. INTRODUCTION

Skiora is a workplace security and visitor management system designed specifically for
manufacturing companies, factories, and industrial plants.
It replaces outdated manual registers and fragmented processes with a centralized, digital
gate/reception system. The app ensures secure, auditable, and efficient handling of all visitors,
pre-approvals, and workforce interactions.

Skiora is built on Flutter (multi-platform support) and uses Firebase (Authentication, Database,
and Cloud Messaging) as its backend.
The architecture follows a clean separation of UI, controllers, repositories, and services, ensuring
scalability, maintainability, and audit compliance.

2. CORE FEATURE

2.1 Visitor Management

Every visitor’s identity, purpose, host, and in/out timestamps are recorded digitally. Visitor
records are tied to Admin/Gatekeeper/Moderator workflows.

Quick host calling is integrated for real-time confirmation.

2.2 Push Notifications (Firebase Cloud Messaging)

Live alerts for new arrivals, approvals, rejections, or daily summaries.

Notifications are role-specific (admins, gatekeepers, moderators).

Implemented through [Link] and fcm_service.dart.

2.3 Role-Based Dashboards

Admin Dashboard: full oversight of visitor traffic, settings, logs, charts, and user management.

Gatekeeper Dashboard: real-time visitor registration, QR scanning, call host option, check-out
marking, and shift/day charts.
Moderator Dashboard: department-level approvals and localized statistics.

26
2.4 Security & Audit Compliance

Logs and reports ensure traceability for audits (internal SOPs, external compliance).
Auto-retention policies configurable via settings.
Supports audit trails for who approved, who hosted, and when check-in/out occurred.

3. USER ROLES AND PERMISSIONS

3.1 Admin

Manage users and roles (admins, moderators, gatekeepers).

Configure plant-level settings and policies.
Approve high-risk or special-category visitors.

Access compliance logs and analytics.

27
3.2 Gatekeeper (Security Staff)

Register new visitors at entry.

Directly call hosts from within the app.
Check-out visitors and view daily charts.

3.3 Moderator

Department-level oversight.

Approve/reject routine visitors.

Monitor department statistics and visitor logs.

28
4. END-TO-END USER FLOWS

4.1 Onboarding & Authentication

Email/password-based authentication via Firebase.

Email verification required (verify_email_controller.dart).

Role assignment on first login via set_role.dart

Password reset/forgot flow included.

4.2 Walk-In Visitor Check-In

Gatekeeper fills visitor details (name, ID, company, host, photo, etc.).
Optional host call integration for instant confirmation.

Record saved in Firebase (via visitor_repository.dart).

Admin notified instantly.

4.3 Notifications

Admins, gatekeepers, and moderators receive role-specific alerts.

Alerts triggered on: arrival, approval/rejection, expiring approvals, and daily summaries.

4.4 Dashboards & Logs

Real-time dashboards show visitor stats, approvals, and logs. Logs are
chronological and filterable (for compliance and audits).

5. SYSTEM ARCHITECTURE

5.1 Layers

1. UI Pages

Dashboards, Check-In, Login/Signup, Onboarding.

29
2. Controllers
Business logic (e.g., approval_controller.dart).
3. Repositories

Data abstraction over Firebase (authentication, user, visitor).

4. Notifications

Firebase Cloud Messaging integration.

5. Helpers/Utilities
Loaders, validators, exception handling, connectivity.

6. Design System
Global theming, typography, constants, reusable UI components.

5.2 Data Models

UserModel:

Fields: id, email, name, phone, role, department, photoUrl, status

VisitorModel:
Fields: id, fullName, company, purpose, hostName, idType, idNumber, photo, preApproved,
approvalStatus, checkInAt, checkOutAt, createdBy, approvedBy

5.3 Technology Stack

Frontend: Flutter (cross-platform).

Backend: Firebase (Auth, Realtime Database/Firestore, FCM)

State Management: GetX (DI, bindings).

Native Integrations: Phone dialer (url_launcher).

6. Compliance & Reliability

Offline-aware: Network manager ensures stable behavior during connectivity issues.

Audit-ready: Logs provide complete accountability.

Retention policies: Auto-delete/archival for compliance.

30
Scalability: Multi-role support for multi-gate, multi-plant environments.

7. Next Development Steps

Finalize QR scan/generation workflow (plug into visitor repository).

Consolidate duplicate notification_01 folder.

Confirm check-out UX flow (list action vs. dedicated screen).

Add policy-based log retention setting

Improve runtime permissions for phone call integration.

8. Why Skiora is Unique

Unlike generic visitor apps, Skiora is optimized for industrial environments:

Built for multi-shift, multi-gate factories.

Prioritizes phone call handoff (critical in noisy shop floors).

Strong focus on auditability and compliance, essential for plants with frequent safety and
regulatory checks.
Lightweight but scalable architecture to handle high visitor volumes.

31
CHAPTER 5: TESTING METHODOLOGIES OF PROJECT

5.1 INTRODUCTION

Testing is one of the most important activities in the SOFTWARE DEVELOPMENT LIFE
CYCLE (SDLC). A software system is considered complete only after it has been thoroughly
tested under different conditions to ensure functionality, accuracy, and reliability. The main
objective of software testing is to verify whether the developed system meets the requirements
specified in the Software Requirement Specification (SRS) document.

Through testing, defects can be identified at an early stage and corrected before deployment. A
well-tested system not only reduces the risk of failure but also increases user confidence and
satisfaction. In this project, testing ensured that all modules such as visitor management, resident
approvals, security operations, and admin dashboard monitoring performed seamlessly in real-
world scenarios.

The testing strategy adopted in this project involved multiple stages such as Unit Testing,
Integration Testing, System Testing, Acceptance Testing, Performance Testing, and Usability
Testing. Each stage had a well-defined objective, method, and expected outcome.

5.2 TESTING METHODOLOGIES APPLIED

5.2.1 Unit Testing

Objective: To test each module of the system in isolation to verify that it functions correctly.
Explanation:
In this stage, individual modules such as login authentication, visitor entry, check-in/check-out,
complaint registration, and notification delivery were tested separately. By isolating each function,
errors were identified without interference from other modules.
Examples of Unit Tests:
1. Login module tested with valid and invalid credentials.
2. Visitor request form tested for correct data entry and validation (e.g., mobile number format,
mandatory fields).

32
3. Resident approval module tested for correct storage of approval status.

4. Complaint module tested to verify that complaints are stored in the database and visible in the
admin dashboard.
Result: All unit modules performed as expected after debugging minor issues such as incorrect
field validation and error messages.

5.2.2 Integration Testing

Objective: To verify that modules interact correctly with one another after integration.
Explanation:
After the modules were tested individually, they were integrated into the system workflow.
Integration testing was performed to ensure that data flows correctly from one module to another.
For example, once a visitor is entered by security, the resident should immediately receive a
notification for approval.
Examples of Integration Tests:

1. Security enters visitor details → Resident receives approval request.

2. Resident approves request → Notification reaches security for check-in.

3. Visitor checked out by security → Entry automatically recorded in admin dashboard.

Result: Integration between modules worked correctly. A few synchronization issues were
observed initially, but they were resolved by improving the database query execution speed.

5.2.3 System Testing

Objective: To evaluate the entire system as a whole.

Explanation:
System testing involved testing the application in a real-time environment with all modules
combined. The goal was to simulate actual working conditions at a housing society, where
residents, security guards, and the admin interact with the system simultaneously.
Examples of System Tests:

1. End-to-end visitor entry workflow (entry → approval → check-in → check-out).

2. Multiple residents receiving and responding to visitor requests at the same time.
3. Admin monitoring visitor reports while residents and security continue operations.

4. Complaints raised by residents being automatically logged in the admin dashboard.

33
Result: The system worked as intended, with proper coordination between different users and
modules.

5.2.4 Acceptance Testing (UAT)

Objective: To ensure that the system meets user requirements and expectations.
Explanation:
Acceptance testing was conducted with actual users – residents, security guards, and admins –
who interacted with the application and provided feedback. This stage is critical as it determines
whether the system is ready for deployment.
User Feedback:

Residents found the interface user-friendly and appreciated instant notifications for visitor
approval.
Security guards confirmed that the check-in and check-out process was easy to perform. Admins
valued the dashboard as it provided real-time insights into visitor logs and complaints.

Result: The system was accepted by users after minor interface improvements were made, such
as increasing font size and reorganizing the dashboard layout.

5.2.5 Performance Testing

Objective: To ensure system stability, speed, and reliability under different load conditions.
Explanation:

Performance testing was carried out by simulating multiple visitor entries and approval requests
happening at the same time. The response time of the system was measured under varying loads.
Scenarios Tested:
1. 50 visitor requests logged within 5 minutes.

2. Multiple residents approving or rejecting visitors simultaneously.

3. Admin generating reports during peak system usage.

Result: The system successfully handled concurrent users with an average response time of less
than 2 seconds. No major performance issues were observed.

34
5.2.6 Usability Testing

Objective: To ensure that the system is user-friendly, intuitive, and easy to operate.

Explanation:
Usability testing focused on the design, navigation, and accessibility of the system. Different
user groups were observed while interacting with the system to check if they could complete
their tasks without confusion.

Observations:

Residents were able to approve/reject visitors without needing training.

Security guards could perform check-in and check-out easily with minimal instructions.

Admins were able to generate reports and monitor system status quickly.

Result: :
The system was rated highly usable. Only minor suggestions such as color changes and larger
buttons were recommended for better accessibility.

5.3 TESTING WORKFLOW

The overall testing process followed a structured workflow as shown below:

1. Requirement Analysis – Understanding project requirements and identifying testable features.
2. Test Planning – Designing a test strategy, preparing resources, and selecting tools.

3. Test Case Development – Writing detailed test cases including input values, expected results,
and execution steps.
4. Test Execution – Running test cases on different modules and documenting outcomes.

5. Defect Tracking – Logging issues, categorizing them as major/minor, and assigning them for
fixing.

6. Test Closure – Finalizing reports, summarizing results, and preparing documentation for
submission
35
 5.4 KEY TESTING SCENARIOS AND RESULTS

1. Login Verification

Test with correct username/password → Successful login.

Test with incorrect credentials → Access denied (PASS).

2. Visitor Entry and Approval

Security enters visitor details → Resident receives request instantly. Resident approves → Visitor
check-in allowed.
Resident rejects → Visitor denied entry.

3. Check-In and Check-Out

Security records check-in time → Stored in database.

Security records check-out → Automatically reflected in reports.

4. Admin Dashboard

Visitor data updated in real-time.

Complaint tracking visible with proper status.

5. Concurrent Access

Multiple users performing operations simultaneously → No data loss or delays observed.

5.5 SUMMARY

Testing ensured that the project met all functional and non-functional requirements. From
individual module verification to system-wide validation and user acceptance, the testing
methodologies provided confidence that the application would perform reliably in real-world
scenarios.

36
CHAPTER 6: DETAILED PROJECT CODE AND EXPLANATION

import 'package:camera/[Link]'; import

'package:firebase_core/firebase_core.dart'; import
'package:flutter/[Link]'; import
'package:flutter_native_splash/flutter_native_splash.dart'; import
'package:get/[Link]'; import
'package:get_storage/get_storage.dart'; import
'package:skiora_merge/[Link]'; import
'package:skiora_merge/data/repositories/[Link]/authentication_repository.dar
t';
import 'package:skiora_merge/firebase_options.dart'; import
'package:firebase_messaging/firebase_messaging.dart'; import
'package:skiora_merge/notification_01/[Link]'; import
'package:supabase_flutter/supabase_flutter.dart';

List<CameraDescription> _cameras = [];

Future<void> main() async {

[Link](); try
{
_cameras = await availableCameras();
if (_cameras.isEmpty) {
debugPrint("No camera found. Skipping camera initialization.");
}
} catch (e) { debugPrint("Camera initialization
failed: $e");
_cameras = [];
}
//TODO:Widgets final WidgetsBinding widgetsBinding =
[Link]();
//TODO:Widgets
await [Link]();
//TODO:SPLASH
[Link](widgetsBinding: widgetsBinding);
//TODO:FIREBASE

await [Link](options: [Link]).then(

(FirebaseApp value) => [Link](AuthenticationRepository()),
37
 );
//TODO: SUPABASE
await [Link]( url: '[Link]
// from Supabase settings anonKey:
'eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzdXBhYmFzZSIsInJlZiI6Im1kcndlem
ZmZmVzcnVta2J5ZWFxIiwicm9sZSI6ImFub24iLCJpYXQiOjE3NTU1Njk5MjEsImV4cCI6Mj
A3MTE0NTkyMX0.cRaH9UlUAqp-mF4NOwtQqk5QnRiQJ4un51p-6Dz6inw', // from
Supabase settings
);

//TODO:AUTHENTICATION
await [Link]();
try {
await
[Link](
alert: true, badge: true, sound: true,
);
await [Link]();
listenToTokenRefresh();
} catch(e)
{ print("Windows or Web
Detected");
}

runApp(const App());
}
The main dart file handles setting up core stuff the Flutter app needs before showing anything on
screen. First thing it does is initialize Flutter bindings which plugins require to talk to device
hardware properly. Then tries detecting available cameras for later use in the app handles errors if
they pop up during this step. Local storage gets kicked off using GetStorage because its good for
simple data stuff that needs to stick around between sessions. Oh and keeps that splash screen
visible while all this setup happens in the background.

Firebase connection comes next by calling that initializeApp thing with platform-specific settings
tossed in there. AuthenticationRepository gets injected via GetX here so

dependencies stay managed without fuss. Then Supabase hooks up using their project URL and
anon key so database and auth features work out of the gate. Notifications take a few steps asks
38
user permission for push alerts through FCM then starts up a custom service to deal with
incoming pings refresh tokens get handled too so everything stays connected smooth-like.
Once cameras storage firebase supabase and notifications are all good to go the actual app widget
runs with runApp() which finally draws the UI on screen. Basically this whole flow makes sure
backend services storage and that initial splash screen play nice before users start interacting with
anything important you know how apps need everything prepped upfront right

import 'package:cloud_firestore/cloud_firestore.dart'; import

'package:flutter/[Link]'; import
'package:flutter/[Link]'; import
'package:flutter_facebook_auth/flutter_facebook_auth.dart'; import
'package:google_sign_in/google_sign_in.dart'; import
'package:skiora_merge/screens/check_in/visitor_list.dart'; import
'package:skiora_merge/screens/login/[Link]'; import
'package:firebase_auth/firebase_auth.dart'; import
'package:flutter/[Link]'; import
'package:flutter_native_splash/flutter_native_splash.dart'; import
'package:get/[Link]'; import
'package:get_storage/get_storage.dart'; import
'package:skiora_merge/screens/signup/verify_email.dart'; import
'../../../dashboard/[Link]'; import
'../../../dashboard/pages/moderator_dashboard_page.dart'; import
'../../../helper/[Link]'; import '../../../helper/my_exceptions.dart';
import '../../../screens/check_in/set_role.dart'; import
'../../../screens/onboarding/[Link]';

class AuthenticationRepository extends GetxController { static AuthenticationRepository

get instance => [Link]();

final deviceStorage = GetStorage(); final

_auth = [Link];

@override

void onReady() {
[Link]();
screenRedirect();
}
void screenRedirect() async {
final user = _auth.currentUser; if

39
 (user != null) { if
([Link]) { final

doc = await

[Link]('Users').doc(_auth.currentUser?.uid).get();
final data= [Link](); final role= data?['role']; if(role==null) {
[Link](title: "You don't have any role?", message: "Delete your Account,
and Create your Account again");
}
if(role=='Admin'){
[Link](() => ModeratorDashboardPage( onThemeChanged:
(ThemeMode mode) => [Link](mode),
currentThemeMode: [Link],
));
}
else if(role=='Gatekeeper'){
[Link](()=> FirstPage());
}
else if(role=='Main Admin'){
[Link](()=> const KDashboard());
}
else{
[Link](title: "Something Related Role Error", message: "Please try
again");
[Link](()=> const CheckIn());
}

} else {

[Link](() => VerifyEmailScreen(email: _auth.currentUser?.email));

}
} else {

// First-time user or logged out [Link]('isFirstTime',

true);

[Link]('isFirstTime') != true
? [Link](() => const LoginScreen())
: [Link](const OnBoardingScreen());
}
}
40
}
Report on AuthenticationRepository

The AuthenticationRepository class manages user authentication and screen navigation in the app
using Firebase Authentication, Firestore, and GetX. When the app launches, the onReady()
method removes the splash screen and calls screenRedirect() to decide where to send the user.

If a user is logged in and their email is verified, the system fetches their profile data from the
Users collection in Firestore. Based on the role field, different dashboards are opened:

Admin → Moderator Dashboard Gatekeeper

→ FirstPage (Check-In page) Main Admin

→ Main Dashboard

Any missing/invalid role → Error Snackbar + fallback to Check-In

If the email is not verified, the user is redirected to the Verify Email screen. If no user is logged
in, the app checks GetStorage for the first-time flag:

First-time users → OnBoarding screen

Returning users → Login screen

This repository ensures a smooth role-based navigation flow while handling login state
persistence, error feedback, and first-time user onboarding.

41
CHAPTER 7: SPECIAL / CHALLENGING EXPERIENCES
ENCOUNTERED DURING TRAINING

7.1 INTRODUCTION

Industrial training at Jayshree Pistons Pvt. Ltd. offered not only exposure to advanced piston
manufacturing processes but also provided an opportunity to work on the development of a
Security Management Application project. While the training enriched both technical
knowledge and professional discipline, it also brought forward several challenges.

These challenges spanned across technical barriers, workplace practices, adaptation to

industrial systems, and effective teamwork. Facing these obstacles improved our problem-
solving skills, adaptability, and technical expertise. This chapter summarizes the key challenges
encountered, strategies adopted to overcome them, and the valuable lessons learned.

7.2 MAJOR CHALLENGES FACED

7.2.1 Technical Synchronization Issues

One of the significant challenges was ensuring smooth synchronization between different
modules of the application:

● Problem: During integration of the Security, and Admin modules, delays were observed
in visitor approval notifications and data updates on the dashboard.

● Cause: Database query execution speed and backend push-notification delays.

● Solution: Optimized Firebase queries, improved Firestore/Realtime Database response

time, and used lightweight data payloads for real-time communication

● Learning: Strengthened understanding of database indexing, caching, and efficient

server-side handling

7.2.2 Debugging and ADB (Android Debug Bridge) Conflicts

● Problem: Frequent connection issues between mobile devices and the testing environment
caused delays during debugging.
● Cause: Conflicting drivers, unstable USB configurations, and emulator/device
mismatches.

42
 ● Solution: Installed stable USB drivers, switched to wireless debugging, and standardized
device configurations
● Learning: Improved practical debugging skills and adaptability in mobile application
testing.

7.2.3 Complex Logic Debugging

● Problem: Application modules required multiple verification checks such as eligibility

validation, complaint logging, approval workflows, and visitor check-in/out. Errors in one
module often caused ripple effects across others.

● Solution: Adopted modular debugging, wrote detailed test cases, and implemented
automated logging mechanisms to track failures.

● Learning: Developed systematic debugging skills and deeper problem-solving ability

7.2.4 Workplace Adaptation Challenges

Apart from technical issues, adapting to the industrial workplace introduced difficulties:

● Strict Safety Protocols: Wearing safety gear and adhering to shop-floor safety measures
was initially challenging.

● Documentation Practices: Maintaining daily logs, defect tracking sheets, and structured
reporting was more rigorous than academic work.

● Coordination with Supervisors: Understanding industry-specific terminology and

aligning project goals with company expectations took extra effort.

7.3 POSITIVE EXPERIENCES

Despite the challenges, several experiences left a positive impact:

1. Supportive Mentorship
Supervisors and technical staff provided constant guidance in resolving software and
workplace-related issues.
2. Team Collaboration
Working as a group helped us divide responsibilities, resolve coding conflicts, and
improve productivity.

3. Exposure to Industry Practices

Observing piston manufacturing processes—such as die casting, CNC machining, and
quality testing—broadened our knowledge beyond software development.
43
7.4 AREAS OF DIFFICULTY / DISLIKES

While the training was fruitful, a few difficulties stood out:

1. Debugging Delays: Errors during real-time synchronization often consumed excessive

hours.
2. Limited System Access: Some proprietary company systems restricted direct hands-on
use, limiting exposure.
3. Strict Deadlines: Balancing coding tasks with report preparation and workplace learning
was challenging.

7.5 LESSONS LEARNED

From these experiences, the following lessons were gained:

● Debugging is a critical skill: Errors are inevitable; systematic debugging ensures smooth
progress.

● Documentation is equally important as coding: Structured reports and logs aid long-
term project maintenance.

● Teamwork and Communication matter: Peer discussions and supervisor feedback

saved time and improved solutions.

● Adaptability is key in industry: Every company has unique workflows; learning to

adapt quickly ensures efficiency.

● Resilience under pressure: Tight deadlines trained us to manage time and remain
focused.

7.6 SUMMARY

Highlighted the special and challenging experiences faced during industrial training at
Jayshree Pistons Pvt. Ltd. and while developing the Security Management App.

Challenges such as synchronization errors, debugging hurdles, workplace adaptation, and

deadline pressures tested our patience and technical ability. However, these experiences
improved our skills in coding, testing, debugging, teamwork, communication, and
professional discipline.

Overall, the training was a blend of technical growth and personal development, preparing us
to handle real-world industrial and software development challenges with greater confidence

44
CHAPTER 8: CONCLUSION
8.1 INTRODUCTION

The industrial training at Jayshree Pistons Pvt. Ltd. provided a unique opportunity to bridge the
gap between theoretical knowledge gained during academic studies and practical implementation
in a real-world industrial environment. The training not only enriched our technical skills but also
instilled professional discipline, teamwork, and adaptability. This chapter presents a
comprehensive conclusion drawn from the entire training program.

8.2 OVERALL LEARNING OUTCOMES

Over twelve weeks of training we covered piston manufacturing processes production planning
methods and quality control systems You see how industrial operations flow in real settings from
sourcing materials right through shipping finished products Worked closely with heavy
machinery types like CNC units VMCs and those massive heat treatment setups they use for
metal parts Got hands-on with CAD CAM tools too plus ERP platforms that bridge computer
systems and factory floors Real-world projects let us test approaches systematically applying
techniques as actual problems came up Professional growth happened naturally through daily
documentation tasks team communications and presenting findings regularly to managers

The thing is you start seeing how everything connects you know Material specs influence machine
settings which then affect quality checks down the line Testing wasn’t just theoretical either Had to
track tolerances adjust parameters document variances weekly Even learned why certain alloys
respond differently during heat treatment phases

Software side had its challenges Sure CAD designs look clean on screen but translating them to
machine code requires tweaking feeds speeds tool paths Unexpected stuff happens when you’re
dealing with physical materials versus digital models That’s where systematic testing comes into
play logging every adjustment outcome

Soft skills developed alongside technical ones Explaining process changes to operators writing
clear maintenance logs presenting project updates without drowning people in data Basically
learned how technical work ties into broader business goals Production schedules affect
inventory levels quality metrics impact customer satisfaction all that

Looking back it’s about seeing manufacturing as interconnected systems rather than isolated tasks
Each piece from raw stock to finished piston relies on multiple checkpoints feedback loops cross-
department coordination You begin appreciating why certain protocols exist even if they feel
tedious initially

8.3 PERSONAL & PROFESSIONAL DEVELOPMENT

The training was instrumental in improving our problem-solving abilities and technical
proficiency. By facing real-world challenges such as debugging application logic, handling
45
synchronization delays, and adapting to workplace safety norms, we developed resilience and
confidence. Team collaboration further enhanced our ability to work under pressure and deliver
within deadlines.
8.4 INDUSTRIAL EXPOSURE

Beyond software development, observing piston manufacturing processes provided valuable

exposure to industrial practices. We witnessed precision engineering in casting, machining, and
finishing, along with rigorous quality assurance measures. These insights broadened our
understanding of how IT solutions integrate with mechanical industries to improve efficiency.

8.5 SUMMARY

In conclusion, the training experience at Jayshree Pistons Pvt. Ltd. was holistic in nature,
enabling us to merge technical knowledge with real-world practices. It prepared us not only as
technicians or developers but also as professionals ready to contribute effectively to the industry.

46
 CHAPTER 9: REFERENCES / SOURCES OF INFORMATION

9.1 INTRODUCTION

A training report must be backed by reliable sources of information to ensure accuracy, credibility,
and academic value. The references listed below include books, research papers, technical
manuals, industry standards, and online resources that were consulted while preparing this report.

9.2 BOOKS & PRINTED MATERIALS

1. P. N. Rao – Manufacturing Technology, Volumes I & II.

2. Mikell P. Groover – Fundamentals of Modern Manufacturing.
3. R. K. Jain – Production Technology.
4. A. K. Gupta – Engineering Materials and Metallurgy.
5. MSBTE Reference Manuals and Lab Journals.

9.3 INDUSTRY RESOURCES

1. Jayshree Pistons Pvt. Ltd. – Internal process documentation and supervisor guidance.
2. On-floor observation of piston production and quality assurance departments.
3. Company technical manuals for CNC, VMC, and die casting machinery.
4. Interaction with industry professionals during training.

9.4 ONLINE RESOURCES

1. [Link] – For research papers on piston design and thermal

performance.
2. [Link] – For academic publications on manufacturing and IT
integration.
3. [Link] – For Flutter, Firebase, and Supabase programming references.
4. [Link] – Official Flutter documentation.
5. [Link] – Official Firebase documentation.
6. [Link] – Official Supabase documentation.
7. ISO/TS Standards (Automotive Industry Quality Standards).

9.5 CITATION PRACTICES

All references got cited by the book to keep things legit. Whenever numbers or methods came up,
we double-checked against several places. Like if a workflow got mentioned, it wasn’t just
copied from one spot. No guesswork here. Industry stuff mostly came straight from what we saw
on the ground plus boss input. Not just theory but actual shop floor vibes.

47
9.6 SUMMARY

Those sources at the end did two big jobs. First they gave the textbook backbone for all the
manufacturing talk and project steps we covered. Then they backed up how testing actually
works when you’re clocking in every day. You know how school teaches you ideal scenarios?
The references helped smash that together with real-world messiness from factories and labs.
Basically made sure this report wasn’t just pretty slides but something you could actually use
Monday morning on site.

48
49