Starting a Global PLM Implementation using an Agile Deployment Methodology with Aras

ACE 2011 International

Starting Your
Starting Your
PLM Implementation

Methods for success
Methods for success
www.aras.com 300 Brickstone Square
Suite 904
Andover, MA 01810
Andover, MA 01810
[978] 691‐8900
www.aras.com

Copyright © 2011 Aras All Rights Reserved. aras.com

Agenda

Getting Organized
Resources
Getting Started
Project Breakdown
Some Tips
Some Tips
How Things get Sideways
Our Recommendations
Our Recommendations

Copyright © 2011 Aras All Rights Reserved. Slide 2 aras.com

Getting Organized

Organize your thoughts !
Gather all relevent materials
Existing forms
Flow charts
SoPs
Identify Resources
Keep an open mind with regards to change
Square Peg in a Round hole


Resources
Who do you need
Role Responsibility
Project Manager • Direct Implementation resources
• Manage project schedules
Manage project schedules
• Track Status
• Resolve conflicts and issues
Business Process Owner(s) • Provide project priorities and objectives
• Direct participation of resources
• Resolve business process issues
Subject Matter Experts • Communicate current process
• Provide information details
• Support user community during rollout
I.T. System Support • Support site infrastructure
• Extract legacy data
Extract legacy data
• Provide technical expertise
Technical Resources • Configure application
• Develop customizations
Develop customizations
• Provide technical expertise


Getting Started
Develop a Project Charter if you need funding
Lets management know what you will do and will not do
g y
Defines a goal and an endpoint to measure success
There are plenty of examples on the web
p y p
Develop a Project Plan
Lets resources know what is expected of them
ets esou ces o at s e pected o t e
Sets the schedule for the project
Get Trained
Get Trained
The team needs to understand Aras Innovator
Review the standard Aras Innovator Solutions
Review the standard Aras Innovator Solutions
Required for effective gap analysis

Organizing your Project

Break your project
down into phases
down into phases
Requirements & Design
Construction
C t ti
Transition
Phases can overlap
Ph l
Work is done in a serial
fashion but you don’t
f hi b t d ’t
need to finalize a phase
before moving on
before moving on


Elaboration Phase
Requirements & Design

Develop a Requirements Document
Develop Use Cases
Conduct Gap Analysis
Develop design document or functional spec


Requirements Documents
Uggggh ! Really?
They are not a waste of time even if you are the
developer
This includes “What” & “Why” for the system
“What” are the system requirements
“Why” are they requirements
Should include high level use cases
Intended for technical resources to understand
business case
Used as a foundation for other documents


Use Cases
Pay me now or pay me later
More detailed than in Requirements Document
Documents the interaction between user and system
Start at a high level and add detail as visual
prototype evolves
Don’t worry about getting these 100% correct
Shoot for 70‐80%, then iterate with visual prototype
These are used later to build test plans, training
These are used later to build test plans, training
materials & user documentation
Provides a point of reference for change
Provides a point of reference for change
management later

More on Use Cases

Always build an index of use cases
Need to be reviewed by Business Process resources
Samples are available on the web
A good reference
Writing Effective Use Cases by Alistair Cockburn
You will likely write 2 types of use cases
High level (Clouds)
g ( )
Detailed (Sea Level)


Use Case Samples
Implementation UC
Phase Number Use Case Name
Sample Index Phase 1
Phase 1
UC0001
UC0002
Create Engineering Change Request
Maintain Engineering Change Request
Phase 1
Phase 1 UC0003 Create Engineering Change Notice
Create Engineering Change Notice
Phase 1 UC0004 Maintain Engineering Change Notice
Phase 1 UC0005 Process Engineering Change Request
Phase 1 UC0006 Create new part/document
Phase 1 UC0007 Maintain Design Part
Phase 1 UC0008 Maintain Document
Phase 1 UC0009 Approve Change via Fast Track
Phase 1 UC0010 Approve Change via CRB (Change Review Board)

Sample Document
Sample Document Adobe Acrobat
Document


Design Specifications

This is the “How” to address the requirements
You can determine how detailed this needs to be
Documents data model changes
Use Itemtype definition report to document items
Document all the Events and methods required
This will save time later when trying to diagnose issues
Used for long term understanding and maintenance
g g
Very important if you plan to subcontract any work


Construction Phase
Visual Prototypes
Primarily used for validating use cases and user feedback
Behavioral Prototypes
Adds automation and customizations
Data Migration
Integrations and Interfaces
Integrations and Interfaces


Visual Prototypes
Putting it all together

This is just building things with Aras Innovator
Items, Forms, Workflows, Lifecycles, etc
Used to solicit user feedback
Built in conjunction with use cases and requirements
May cause you to revisit use cases and specifications
Should not include automation (significant automation)
Spend significant time reviewing these with users
p g g


Making it all work

Adds automation to the Visual Prototype
Will likely cause you to revisit use cases and specifications
Will introduce changes to the Visual prototype
Includes building interfaces and integrations
Includes unit testing
Everything you need to begin full system test


A Complete Look
Disciplines Activities Phases
Inception Elaboration Construction Transition
Initial Parts Change Parts Change Interface T1 T2
Install Test Environment
Project Startup Train Project Team
Kickoff Meeting
High Level Requirements
Discovery workshop(s)
Business Modeling SoW
Project Charter & Solution Overview
High Level Use Cases
Requirements Workshops
Requirements Requirements Document(s)
Gap analysis
Use Case Development
Solution Design Doc
Analysis & esign
Analysis & Design Functional specs for customizations
p
Screen Mockups
Visual Prototypes
Import Users
Configure Items
Configure Forms
Configure Workflows
Implementation Configure Roles & Permissions
Develop Data Migration
Develop Data Migration
Interface development
Develop Customizations
Prepare Test Plan
Test Unit Test
Full System Test
Prepare User Docs
Develop User Training
Deployment Deliver User Training
Build & Deploy Prod Env
B ild & D l P d E
Production Data Migration
Packaging
Configuration Management Migrate Dev‐QA‐Prod
Change Management
Initial Project Plan
Project Management Initial Risk Analysis
Project Planning & Design Review

Milestones

TIME


Some Tips

Keep permissions wide open to start
make a world can edit permission to facilitate the first user
reviews then implement permissions
Start with your items in a single folder on the toc
Start with your items in a single folder on the toc
Allow world to create most items
Adjust form sizes in the beginning
it’s a better user experience
Don’t worry about getting it 100% right
You Wont…. And Aras Innovator is good at making change


How Things Get Sideways

Lack of requirements understanding or agreement
on requirements
on requirements
Lack of understanding of the standard Innovator
solutions
sol tions
Lack of Training
Understanding the impact of change
Workflow or Lifecycle changes can impact method
Biting off too much!


Our Recommendations

Training is a MUST
Engage Aras or a partner for jump start activities
Requirements review
Leverage our experience to recommend approaches or
discuss what has been done before
Use case development
U d l t
Initial Design Review
Periodic reviews and questions
Periodic reviews and questions
Solve a real problem and move on to the next


Final Thoughts
Do’s and Don’ts

DO
Create visual prototypes and get user validation before
developing any method code
Develop accurate Use Cases and keep them up to date
Develop accurate Use Cases and keep them up to date
• They will save you time down the road !!
Look for “Small Wins” that provide business value
p
DON’T
Spend a significant amount of time developing specs w/o
Spend a significant amount of time developing specs w/o
prototyping the solution
Worry about not getting 100% of the detailed
requirements up front: Iterate !


Starting a Global PLM Implementation using an Agile Deployment Methodology with Aras

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (20)

Semelhante a Starting a Global PLM Implementation using an Agile Deployment Methodology with Aras

Semelhante a Starting a Global PLM Implementation using an Agile Deployment Methodology with Aras (20)

Mais de Aras

Mais de Aras (20)

Último

Último (20)

Starting a Global PLM Implementation using an Agile Deployment Methodology with Aras