Aras PLM Requirements Management

634 views

Published on

Published in: Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
634
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
0
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Aras PLM Requirements Management

  1. 1. BEDIFFERENT ACE GERMANYCopyright © 2012 Aras. All Rights Reserved. aras.com
  2. 2. ACE Germany Aras Requirements Management Rob McAveney Director of Product Management Aras CorpCopyright © 2012 Aras. All Rights Reserved. aras.com
  3. 3. Why Manage Requirements? Requirements are  the voice of your customer  the building blocks of your products  verification that you are building what you intended to build  valuable descriptions of your design and quality goals  YOUR MOST IMPORTANT IP ASSET Without requirements  how do you know your product meets your customers’ needs?  how do you verify you didn’t miss something important?  YOU’RE JUST GUESSINGCopyright © 2012 Aras. All Rights Reserved. Slide 3 aras.com
  4. 4. Key Elements of RM Validation: are we building the correct product?  Have we listened to our customers, and captured their needs?  Are we building what’s ideal for the market? Traceability: are we building the product correctly?  Have we forgotten anything?  Are my products/parts/documents satisfying my requirements? Version Control: are we still building the correct product?  Close the loop – validate with our customers that we are meeting their needs  See how our requirements have historically evolvedCopyright © 2012 Aras. All Rights Reserved. Slide 4 aras.com
  5. 5. Why build RM into PLM? Requirements are the backbone of your product development efforts  Why track the “why” separate from the “who”, “what”, …? Requirements apply across the entire product lifecycle Changes in requirements directly impact everything else you do in PLM Integrating separate RM and PLM systems is difficult  Virtually impossible to achieve the same level of interactivity It’s a natural fit  Workflow, change control, permissions, life cycles, etc. can all be extended to include requirementsCopyright © 2012 Aras. All Rights Reserved. Slide 5 aras.com
  6. 6. Requirements DocumentsDOCUMENT NUMBER: 4131 TITLE: PRODUCT REQUIREMENTSREVISION: A STATE: DRAFT Document Header REQ NO: 121 • Identifying info 1 REVISION: A Introduction STATE: DRAFT • Revision REQ NO: 164 REVISION: B This document details the acceptance standards for the electronics assembly and its components, including • Status1.1 STATE: RELEASED functional requirements, test standards,1.2 REQ NO: 187 REVISION: B References: Content STATE: DRAFT •DEF STAN 59-48 • Text REQ NO: 2121.3 REVISION: B Operation Conditions • Links STATE: DRAFT REQ NO: 214 The product must operate under the following conditions: • Images1.3.1 REVISION: B STATE: DRAFT • Tables Requirement Headers Chapters • Requirement Number • Hierarchical numbering • Individual Revision & Status Copyright © 2012 Aras. All Rights Reserved. Slide 6 aras.com
  7. 7. Aras RM Goals Gather requirements from multiple sources, including customers, regulatory Assembly standards and market research ECO Market Part Part Assembly Research Author requirements Document documents using a rich Part Part user interface Requirement Customers Link requirements to parts, Requirement files, web resources and other requirements Requirement Control the requirements Requirement Regulations configuration using Requirement engineering change workflows Requirement Publish fully formatted Requirement Requirement requirements documents Copyright © 2012 Aras. All Rights Reserved. Slide 7 aras.com
  8. 8. Aras RM Additional FeaturesCopyright © 2012 Aras. All Rights Reserved. Slide 8 aras.com
  9. 9. Aras RM Benefits Summary Achieve real Requirements Management  Requirements validation, traceability and version control  Effectively track both individual requirements and documents Truly integrated Requirements and PLM  Built from the ground up using Aras technology  Reuse your existing workflows, change forms and permissions  Easily link requirements to the Unparalleled ease of use  Rich, web-based authoring environment  Easily create requirements structure and build documents  Directly publish fully formatted requirements documentsCopyright © 2012 Aras. All Rights Reserved. Slide 9 aras.com
  10. 10. Product Availability Pre-release available now (upon request) for demonstrations and evaluations Full release targeted for late Q4, 2012 Available exclusively to Aras Subscribers Follow-on releases planned for 2013 Future Features to include:  Trace matrix capabilities  Integrated change management  Interactive Microsoft Word integration  Requirements reuse and derivation  Customer/supplier portalsCopyright © 2012 Aras. All Rights Reserved. Slide 10 aras.com
  11. 11. ACE Germany Questions ? Rob McAveney Director of Product Management Aras CorpCopyright © 2012 Aras. All Rights Reserved. aras.com

×