Check in Check out Work flow In plm Plm &plc

1. We Make The Difference

2. SEDA-D | DR. RANVIR SINGH
Topics
 CHECK IN CHECK OUT
 CHANGE MANAGEMENT IN PLM
 WORKFLOW IN PLM
 VIEWS IN PLM

3. SEDA-D | DR. RANVIR SINGH
INTRODUCTION OF CHECK IN AND CHECK OUT
In Product Lifecycle Management (PLM), the concepts of "check in" and "check
out" are fundamental to managing the creation, modification, and collaboration of
digital assets such as documents, designs, CAD models, and other related files
throughout their lifecycle.
These check-in and check-out processes are crucial for maintaining data integrity,
version control, and collaboration within PLM environments. They enable multiple
users to work on the same files concurrently while ensuring that changes are
tracked, managed, and documented effectively. Additionally, they provide a
mechanism for controlling access to files, preventing conflicts, and facilitating
collaboration among teams involved in product development, manufacturing, and
other stages of the product lifecycle.

4. SEDA-D | DR. RANVIR SINGH
CHECK IN
 Once the necessary changes to a file have been
made by the user who checked it out, they can
then check it back into the PLM system.
 Checking in involves uploading the modified
version of the file back into the PLM repository,
where it replaces the previous version.
 During check-in, users may be prompted to
provide comments or descriptions of the changes
they've made, which helps in documenting the
evolution of the file.

5. SEDA-D | DR. RANVIR SINGH
CHECK OUT
 Once the user has completed their modifications or updates to
the file, they initiate the "check in" process.
 Checking in the file releases the exclusive lock and updates the
PLM system with the latest version of the document.
 During the check-in process, users may be prompted to provide
comments, metadata, or revision notes, documenting the
changes made and the reasons behind them.
 This documentation is invaluable for tracking the evolution of
the document, understanding the rationale for specific
modifications, and maintaining a comprehensive audit trail.

6. SEDA-D | DR. RANVIR SINGH
1.Version Control: Check in/check out functionality ensures that only one user can
modify a file at a time, preventing conflicting changes and maintaining a clear
version history.
2.Collaboration: By allowing users to work on documents concurrently while
controlling access through check-out locks, PLM systems foster collaboration among
team members, suppliers, and partners.
3.Data Integrity: Exclusive editing rights during the check-out period protect against
unauthorized modifications, ensuring data integrity and compliance with regulatory
requirements.
4.Audit Trail: The check-in/check-out process generates a detailed audit trail of
document revisions, including who made the changes, when they were made, and
any associated comments or metadata.
5.Efficiency: Streamlined workflow management and clear visibility into document
status enhance productivity and efficiency, enabling teams to work more effectively
and meet project deadlines.
BENEFITS OF CHECK IN AND CHECK OUT:

7. SEDA-D | DR. RANVIR SINGH
1.Siemens Teamcenter: Siemens Teamcenter is a comprehensive PLM software suite that
includes features for managing product data, processes, and collaboration. It offers robust check
in/out capabilities to control access to files and ensure version control throughout the product
lifecycle.
2.PTC Windchill: PTC Windchill is another leading PLM solution known for its extensive
capabilities in managing product development processes. It provides check in/out functionality to
enable users to claim ownership of files for editing, preventing conflicts and maintaining data
integrity.
3.Dassault Systemes ENOVIA: ENOVIA, part of the Dassault Systèmes' 3DEXPERIENCE
platform, offers a collaborative environment for managing product lifecycle processes. It includes
check in/out features to facilitate controlled access to product data, enabling efficient
collaboration and version control.
4.Autodesk Fusion Lifecycle (formerly PLM 360): Fusion Lifecycle is a cloud-based PLM
solution by Autodesk, designed to streamline product development processes. It includes check
in/out capabilities to manage the creation, editing, and sharing of product data securely.
5.Arena Solutions: Arena Solutions provides a cloud-based PLM platform focused on helping
companies manage their entire product lifecycle. It offers check in/out functionality to control
access to product data, ensuring that only authorized users can make changes.
Examples of PLM Tools with Check In/Out
Functionality

8. SEDA-D | DR. RANVIR SINGH
CHANGE MANAGEMENT FOR PLM
Change in
management
Implement
a-tion
Assessme
nt
Planning
Evaluati
on

9. FEDA-D | DR. RANVIR SINGH
CHANGE MANAGEMENT PROCESS
Change Management Process:
•Change management is a structured approach to transitioning individuals, teams, and
organizations from a current state to a desired future state.
•In the context of PLM, change management ensures that changes to processes, technologies, and
workflows are implemented smoothly and effectively.
Steps Involved:
1.Assessment:
1. Identify the need for change.
2. Evaluate current processes, technologies, and workflows.
3. Determine the scope, objectives, and potential impact of the proposed changes.
2.Planning:
1. Develop a comprehensive change management plan.
2. Define roles and responsibilities of stakeholders.
3. Establish clear objectives, timelines, and milestones.
4. Allocate resources and anticipate potential risks.

10. SEDA-D | DR. RANVIR SINGH
3.Implementation:
1.Deploy changes in a phased approach.
2.Provide training and support to users.
3.Communicate changes effectively and address concerns.
4.Monitor progress and adjust implementation strategies as
needed.
4.Evaluation:
1.Assess the effectiveness of changes implemented.
2.Gather feedback from stakeholders and users.
3.Measure key performance indicators (KPIs) to evaluate the
impact of changes on productivity, efficiency, and quality.
4.Identify lessons learned and areas for improvement.

11. SEDA-D | DR. RANVIR SINGH
WORKFLOWS IN PLM
DEVELOPMENT
DEVELOPMENT
TESTING
DESIGN
RELEASE
APPROVAL
WORKFLOW
PROCESS

12. SEDA-D | DR. RANVIR SINGH
Type Of Work Flows
1.Design:
1. Conceptualization: This stage involves generating ideas and conceptualizing the
product's design. It may include brainstorming sessions, market research, and feasibility
studies.
2. Product Design: Designers create detailed product specifications, drawings, and
prototypes using CAD (Computer-Aided Design) software. These designs are refined
based on feedback and iterations.
2.Development:
1. Engineering: Engineers transform the design specifications into detailed engineering
plans and specifications. They may perform simulations, analyses, and feasibility studies
to ensure the product meets performance requirements.
2. Prototyping: Physical prototypes are built to validate the design and functionality of the
product. Prototyping may involve iterative testing and refinement to address any issues or
deficiencies.

13. SEDA-D | DR. RANVIR SINGH
3.Testing:
1. Quality Assurance: Testing procedures are developed to ensure the product meets quality
standards.
2. Functional Testing: The product is tested to ensure it performs as expected under various
conditions.
3. Compliance Testing: Products are tested to ensure they comply with relevant regulations and
standards.
4.Approval:
1. Regulatory Approval: Products may need approval from regulatory bodies before they can be
released to market.
2. Stakeholder Approval: Key stakeholders review the product and provide approval for release based
on established criteria.
3. Documentation: Necessary documentation, such as user manuals and compliance certificates, is
prepared for release.
5.Release:
1. Manufacturing Release: The final design is released for production.
2. Distribution: Products are shipped to distribution centers or directly to customers.
3. Marketing: Marketing and sales teams promote the product to potential customers.

14. SEDA-D | DR. RANVIR SINGH
FLOW CHART OF VIEWS IN PLM
DESIGN VIEW
MANUFACTURING
VIEW
QUALITY VIEW
SUPPLY CHAIN
VIEW
PROJECT
MANAGEMENT
VIEW
CUSTOMER VIEW
VIEWS

15. SEDA-D | DR. RANVIR SINGH
VIEWS IN PLM
1.Design View:
1. This view provides engineering and design teams with access to detailed product designs,
including CAD models, drawings, and specifications.
2. Engineers use this view to create, modify, and review product designs.
3. Design views may include features like version control and access controls to manage changes
and ensure data integrity.
2.Manufacturing View:
1. Manufacturing teams need specific information to produce the product efficiently.
2. This view includes manufacturing instructions, bills of materials (BOMs), assembly processes,
and work instructions.
3. It may also incorporate information on production scheduling, resource allocation, and quality
control procedures.
3.Quality View:
1. Quality assurance and control teams require access to data related to product quality and
compliance.
2. This view includes quality standards, inspection reports, test results, and non-conformance
records.
3. It may also incorporate tools for statistical analysis and process improvement.

16. SEDA-D | DR. RANVIR SINGH
4.Supply Chain View:
1. Supply chain management involves coordinating activities with suppliers, manufacturers, and
distributors.
2. This view includes information on supplier contracts, lead times, inventory levels, and logistics.
3. It helps stakeholders optimize the supply chain and manage risks associated with procurement
and distribution.
5.Customer View:
1. Customer-facing teams, such as sales and customer service, need access to product information
to support customers effectively.
2. This view includes product catalogs, pricing information, customer orders, and service history.
3. It helps ensure accurate and timely responses to customer inquiries and orders.
6. Project Management View:
1. PLM systems often include project management capabilities to track tasks, milestones, and
resource allocation.
2. This view provides project managers with visibility into project status, timelines, and
dependencies.

17. SUBMITTED BY:- AADARSH RANA(GU-2022-4118-L)
ANSHUL THAKUR(GU-2022-4117-L)
ETTI TYAGI(GU-2022-4120-L)
LAKHVIR SINGH(GU-2021-4110-L)
SUBMITTED TO:-DR RANVIR SINGH