BEDIFFERENT                       ACE 2012 I NTERNATI O NAL




Copyright © 2012 Aras. All Rights Reserved.                      aras.com
ACE 2012
                                              INTERNATIONAL




 Aras Requirements
 Management

 Nathan Brown
 Director, Product Management
 Aras www.aras.com



Copyright © 2012 Aras. All Rights Reserved.            aras.com
Why Requirements
   Management?
    Requirements are…
             The voice of your customer
             The building blocks of your products
             Verification that you are building what you mean to build
             Defining and validating design and quality goals
             A CRITICAL IP ASSET




Copyright © 2012 Aras. All Rights Reserved.   Slide 3                     aras.com
Why RM in PLM?

    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 evolved

Copyright © 2012 Aras. All Rights Reserved.   Slide 4                        aras.com
Aras RM Vision

    Managing Requirements in Aras Innovator

             Allow relating multiple disciplines to the definition and
              validation functions of requirements management

             Easy to use interface to enter and manage requirements

             Leverage workflow, lifecycle, and configuration
              management capabilities for enhanced requirements
              management

             Integrated processes



Copyright © 2012 Aras. All Rights Reserved.   Slide 5                     aras.com
Anatomy of a Requirements
   Document
    Document Header information
             Product identification
    Chapters
             Structure for the document
                      • Text- items to describe product

    Documents, Chapters, and text can be linked to:
             From other Aras Innovator items for tracebility e.g. Part that
              satisfies a Requirement
             External URL’s
             Files
             Other Requirement objects in other Requirement Documents
Copyright © 2012 Aras. All Rights Reserved.      Slide 6                 aras.com
Requirements Documents




Copyright © 2012 Aras. All Rights Reserved.   Slide 7   aras.com
Enhanced Editing UI




Copyright © 2012 Aras. All Rights Reserved.   Slide 8   aras.com
Enhanced Editing UI




                                                        Browser-based
                                                        Rich Text Editing




Copyright © 2012 Aras. All Rights Reserved.   Slide 9                 aras.com
Enhanced Viewing UI




Copyright © 2012 Aras. All Rights Reserved.   Slide 10   aras.com
External Links- Requirements




Copyright © 2012 Aras. All Rights Reserved.   Slide 11   aras.com
External Links- URLs




Copyright © 2012 Aras. All Rights Reserved.   Slide 12   aras.com
External Link- Files




Copyright © 2012 Aras. All Rights Reserved.   Slide 13   aras.com
External Links- Items




Copyright © 2012 Aras. All Rights Reserved.   Slide 14   aras.com
Requirements Search




Copyright © 2012 Aras. All Rights Reserved.   Slide 15   aras.com
Aras Requirements
   Management
    Unified PLM data model
    Versionable Requirements Documents
    Capture requirements as formatted text, tables
    Link Requirements to other Requirement
     Documents
    Link Requirements to Files, URL’s, Parts
    Extended content UI for ease of entering and
          editing requirements
    Export Requirements Documents to PDF

Copyright © 2012 Aras. All Rights Reserved.   Slide 16   aras.com
Aras Requirements
   Management
    Updated enhanced authoring UI/Dojo
    Text with inline vault-based images
    Text with inline item property links
    Trace Matrix Capabilities
    Import/Export from Word
    Requirement Document Change Order/Process
    Requirements as affected items
    Requirement link to any Itemtype


Copyright © 2012 Aras. All Rights Reserved.   Slide 17   aras.com
Aras Requirements
   Management
    Drag-and-Drop trace linking
    License Manager update enabling trial version
    Requirement Re-use/Derivation
    Customer/Supplier portal




Copyright © 2012 Aras. All Rights Reserved.   Slide 18   aras.com

Aras PLM Requirements Management

  • 1.
    BEDIFFERENT ACE 2012 I NTERNATI O NAL Copyright © 2012 Aras. All Rights Reserved. aras.com
  • 2.
    ACE 2012 INTERNATIONAL Aras Requirements Management Nathan Brown Director, Product Management Aras www.aras.com Copyright © 2012 Aras. All Rights Reserved. aras.com
  • 3.
    Why Requirements Management?  Requirements are…  The voice of your customer  The building blocks of your products  Verification that you are building what you mean to build  Defining and validating design and quality goals  A CRITICAL IP ASSET Copyright © 2012 Aras. All Rights Reserved. Slide 3 aras.com
  • 4.
    Why RM inPLM?  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 evolved Copyright © 2012 Aras. All Rights Reserved. Slide 4 aras.com
  • 5.
    Aras RM Vision  Managing Requirements in Aras Innovator  Allow relating multiple disciplines to the definition and validation functions of requirements management  Easy to use interface to enter and manage requirements  Leverage workflow, lifecycle, and configuration management capabilities for enhanced requirements management  Integrated processes Copyright © 2012 Aras. All Rights Reserved. Slide 5 aras.com
  • 6.
    Anatomy of aRequirements Document  Document Header information  Product identification  Chapters  Structure for the document • Text- items to describe product  Documents, Chapters, and text can be linked to:  From other Aras Innovator items for tracebility e.g. Part that satisfies a Requirement  External URL’s  Files  Other Requirement objects in other Requirement Documents Copyright © 2012 Aras. All Rights Reserved. Slide 6 aras.com
  • 7.
    Requirements Documents Copyright ©2012 Aras. All Rights Reserved. Slide 7 aras.com
  • 8.
    Enhanced Editing UI Copyright© 2012 Aras. All Rights Reserved. Slide 8 aras.com
  • 9.
    Enhanced Editing UI Browser-based Rich Text Editing Copyright © 2012 Aras. All Rights Reserved. Slide 9 aras.com
  • 10.
    Enhanced Viewing UI Copyright© 2012 Aras. All Rights Reserved. Slide 10 aras.com
  • 11.
    External Links- Requirements Copyright© 2012 Aras. All Rights Reserved. Slide 11 aras.com
  • 12.
    External Links- URLs Copyright© 2012 Aras. All Rights Reserved. Slide 12 aras.com
  • 13.
    External Link- Files Copyright© 2012 Aras. All Rights Reserved. Slide 13 aras.com
  • 14.
    External Links- Items Copyright© 2012 Aras. All Rights Reserved. Slide 14 aras.com
  • 15.
    Requirements Search Copyright ©2012 Aras. All Rights Reserved. Slide 15 aras.com
  • 16.
    Aras Requirements Management  Unified PLM data model  Versionable Requirements Documents  Capture requirements as formatted text, tables  Link Requirements to other Requirement Documents  Link Requirements to Files, URL’s, Parts  Extended content UI for ease of entering and editing requirements  Export Requirements Documents to PDF Copyright © 2012 Aras. All Rights Reserved. Slide 16 aras.com
  • 17.
    Aras Requirements Management  Updated enhanced authoring UI/Dojo  Text with inline vault-based images  Text with inline item property links  Trace Matrix Capabilities  Import/Export from Word  Requirement Document Change Order/Process  Requirements as affected items  Requirement link to any Itemtype Copyright © 2012 Aras. All Rights Reserved. Slide 17 aras.com
  • 18.
    Aras Requirements Management  Drag-and-Drop trace linking  License Manager update enabling trial version  Requirement Re-use/Derivation  Customer/Supplier portal Copyright © 2012 Aras. All Rights Reserved. Slide 18 aras.com