Your SlideShare is downloading. ×
How To Deploy Globally
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

How To Deploy Globally

207
views

Published on

Published in: Technology

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
207
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
10
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Aras Innovator has capability to replicate vaulted files across multiple vault servers, allowing users to retrieve files from their local vault, or from another vault in an order of preference, if a copy exists there, rather than having to get the file from the vault it was originally saved.
  • Transcript

    • 1. aras.comCopyright © 2013 Aras. All Rights Reserved.DOMOREA C E 2 0 1 3
    • 2. aras.comCopyright © 2013 Aras. All Rights Reserved.A C E 2 0 1 3How To Deploy GloballyLearn Aras’s methodology forextending PLM to a global multi-siteenvironment
    • 3. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 3Presentation Outline A Global ScenarioPLM systems tend to – or more realistically – need to grow beyondlocal teams Deployment StepsSpecific steps lead to an understanding of needs and the types ofsolutions that may be offered Customer ExamplesOverview of customer examples to particular use case scenarios Q&A Note: Since this is a tech session we will not talk about globalproject management or implementation methodologies
    • 4. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 4Important Points Global deployments always raises complexity in multipledifferent ways compared to local deployments It is a good idea to prepare for both technical and non-technical aspects of a global deployment In this presentation we discuss the technical aspects ofdeploying PLM in a global setting… however challengesmay not lie in technology… do not under estimate thehuman aspects like reluctance to change and training We recommend doing adequate planning and preparingfor a global deployment or the international extension ofan existing PLM deployment to remote sites Understand bandwidths, latencies, important usecases, heavily used features, user profiles andexpectations
    • 5. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 5A Global ScenarioGlobal deployment:• Two development sites in the US• One development site in Japan• Manufacturing in US, Brazil, Germany and China• WAN traffic• Local concept needs overhaulLocal deployment:• One development site in the US• Aras Innovator, database andvault on the LAN• Often the initial roll-out scenario• Good performance
    • 6. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 6Step 3Step2Step 1Approach Step 1: Use case optimization / globalization» Understand the needs of your users at the remote sites» Optimize through test / measures iterations Step 2: Vault distribution» Local file storage Step 3: Vault replication» Copy / synchronize files between vaults Step 4: Pinpointed measures» Use case dedicated user interface
    • 7. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 7Step 1Use Case Optimization Through Iteration Identify and optimize important use cases that needto perform well in a global deployment Define / identify global use cases Create test cases Investigate Define measures Implement measuresEXAMPLE: A CAD designer in Japan may only login once in the morning, work on 3Dmodels and drawings the rest of the day and logout in the evening. Whereas an employeeon the shop floor may login multiple times a day to look in his or her in-basket.
    • 8. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 8Step 1Use Case Optimization Through IterationRun TestCasesAnalyzeResultsDefineMeasuresImplementMeasuresDefineUseCasesAras InnovatorFramework andSolutionsWAN TopologyEXAMPLE:1. Test login and BOM load inFrankfurt (Germany)2. Analyze data model andmethods on part form andrelation grids3. Analyze WAN between Frankfurtand Detroit4. Adjust load behavior of partform
    • 9. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 9Step 1Use Case Definition Example Primary use case focuses on SKU (Test 1) Login Browse to SKU View SKU Create new SKU (no save) Secondary use case focuses on SKU Feasibility (Test 2) Login Browse to SKU Feasibility Steel Search for Items Browse to SKU Feasibility Alum Search for ItemsEXAMPLE: Customer’s remote team is mainly focused on workingwith SKUs in Aras Innovator
    • 10. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 10Step 2Distributed Vaults Distributed vaults Central application and database (WAN) Files are on-site (LAN)Remote Site Main SiteIISVault 1Vault 2Use cases that suffer from global deploymentstypically involve moving files. EXAMPLE: CADdesigners working with large 3D-CAD assemblies.
    • 11. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 11Step 2Distributed Vaults Aras Innovator architecture allows for independent vault servers separatefrom the Innovator application server In a global deployment, each single site may have a vault server installedto provide secure storage of files on the LAN Aras Innovator uses its central database to manage the metadata aboutthe files stored in the distributed vaults. The vaults do not have they’reown database or login. Users have their default, local vault assigned Vault location is transparent to users (they don’t need to know which vaulthas what file) Aras Innovator API allows for bulk file operations on vaults – e.g.download/upload all files of an CAD assembly directly from/to a vaulthereby reducing traffic to the application server.
    • 12. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 12Step 2Distributed Vault Definition by Admin
    • 13. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 13Step 3Vault Replication Vault replication  Files are synchronized between vaults Aras Innovator knows which is theactual source / copy Replication scheduling & eventsRemote Site Main SiteIISVault 1Vault 2
    • 14. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 14Step 3Vault Replication No “master vault”: files are uploaded to a specific vault basedon a specific user’s selected Default Vault property Aras Innovator can replicate vaulted files across multiple vaultservers Allow users to retrieve files from their local vault, or fromanother vault in any order of preference Replication works in a multi-step asynchronous process Replication rules define what is replicated, when and to whichremote vault(s) Vault Replication works on servers with subscriber licenses
    • 15. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 15Step 3Vault Replication Definition by Admin• Vault definition• Replication Rule(s)• User Read Vault Priority
    • 16. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 16Default Vault and Read PriorityAdmin Tips A user’s Default Vault is the vault server where all files saved by the user are saved. Forsystems configured for Vault Replication, it is also the preferred vault from which files will beretrieved for a given user, unless specific Read Priority vaults are set. Vaults can be specified and prioritized for each user by setting one or more vaults, includingthe User’s Default Vault, on the Read Vaults relationships tab for a User. When a user gets a file, Aras Innovator determines all the vaults with non-stale versions, andwill select the vault to send the file based on (1) if it is the vault with the highest Read Priority(lowest numeric value), (2) it is the user’s default vault (if that vault is not in the Read Prioritylist), (3) it is another vault. Setting the Read Vaults should be done for users to improve performance accessingfiles, based on latency, bandwidth, server load and other considerations. A User’s Default Vault and Read Vault priority is also significant in triggering Replication. Theuser’s Default Vault sets where a file is first saved or changed, so Replication Rules are set onthat Vault to generate onChange Replication Transactions. The Read Priority, and the Vault location(s) of the non-stale version of the file, determineswhich vault Aras Innovator chooses to send the file, and Replication Rules enable the chosenvault to generate onDemand Replication Transactions.
    • 17. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 17Replication RulesAdmin Tips Replication rules define which files get replicated, from where, to where, and when. Replication rules are checked when a file is downloaded from a vault server (this happenswhen users get or view a file), when a file is uploaded to a vault server (this happens whenusers add or modify a file), and when requested programmatically. Replication rules are created for each vault server, and can be written to move files toanother vault server or copy files to multiple vault servers. User Default Vault and Read Priority settings, as mentioned above, interact with Replicationrules, so care must be taken in defining both to work together to give the desired results. Replication rules are checked by the Innovator Server, and any match causes the creation ofreplication transaction record(s) for the specified file and source vault to each target vaultspecified in the rule. These transaction records are regularly checked by the Innovator Server based on thesettings determined in how the Replication Transaction thread was configured, and sent toand executed by the Vault servers per the date/time the transaction is due to execute.
    • 18. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 18Step 3Replication Rule DefinitionSetting DescriptionInitiator Type Defines the initiating event to run this rule – onChange,onDemand, onEvent.Replication Mode Specifies the timing for executing a replication transaction –Immediate, Delayed, Scheduled, Manual.Replication Type Set the execution time specified in the Replication Time fielddefined below.Replication Time UTC time.Timeout Maximum amount of time allowed from when a transactionexecution request is sent to a vault server and acceptedFilter Method Identifies a server method which is used to determine if a filehaving a replication transaction record should be replicated atthe time the replication transaction is just about to execute.File Types Specifies and restricts which types of files will be replicated.Target Vaults Specifies the vault or vaults to copy the file to.
    • 19. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 19Replication RulesAdmin TipsInitiator Type defines the initiating event to run this rule. Choices are – onDemand, for cases where a user belonging in the rule’s related identity tries to get thephysical file. In this case, target vault will be the highest priority ”read” vault of the userinitiating this request, and related Target Vaults (see below) will be ignored. If a file alreadyexists in more than one vault, keep in mind that the rule may or may not create a replicationtransaction, depending on which vault the file is retrieved from. Therefore, you shouldusually have similar onDemand rules for each vault to get consistent behavior. onChange, for cases where the physical file is added or changed by a user belonging in therule’s related identity. onEvent, for cases where a method explicitly requests replication checks be performed. Theuser must belong in the rule’s related identity, or must be granted special temporarycredentials in the method through a GrantIdentity() call. onEvent replication rules arechecked when AML of the form <Item type=File action=replicate id=’…’ /> is sent to theInnovator server for a specific file ID. Optionally, preferred vault(s) to replicate from may bespecified by adding the Located relationship(s) in preference order to the AML. However, ifnone of the vaults specified have a non-stale version, or no vaults are specified, Innovatorchecks for the first vault with a non-stale version. OnDemand and onChange events are automatically checked when a get orupload, respectively, occurs for a specific file on a vault. To replicate files for any situationother than these, use a method to pass File Item ID(s) with a replicate action, and create amatching onEvent rule.
    • 20. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 20Step 4Custom UI Forms Pinpointed Use Cases: Custom UI FormsRemote Site Main SiteIIS
    • 21. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 21Step 4Custom UI Forms Goal: the custom form(s) shall constitute a static UIoutside of Aras Innovator Effect: relative to the specific scenario, eliminateunnecessary requests to the serverSlide 21
    • 22. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 22Step 4Custom UI Forms The main use case for initial deployment if workingwith Documents and CAD assemblies: Standard remote use cases addressed by Aras integrations:1. The CAD Connector will reduce the interaction with the clientperformance when working with CAD Items2. The Office Connector will reduce the interaction with the clientperformance when working with Document Items Other typical remote use cases: Add a custom InBasket to allow votingSlide 22
    • 23. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 23Step 4Custom UI Forms Step 1: heavily used target use cases Search / View 3D model, drawing View part data Edit part data View BOM Step 2: build targeted, optimized, static forms(e.g. smaller HTML / JS footprint) Load UI form once Load data from server on demand (AJAX)
    • 24. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 24Step 4Custom UI Forms – Example Aras Subscriber PortalSlide 24
    • 25. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 25Step 4Custom UI Forms – Example Aras.com Web SiteSlide 25
    • 26. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 26Step 4Custom UI Forms – Example Aras.comProject SiteSlide 26
    • 27. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 27Customer ScenarioSolution OverviewMain use case:Document viewingMain use case:CAD Design Main use case:Document viewingMain use case:CAD DesignMain SiteMain use case:SKU
    • 28. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 28Customer ScenarioPossible Measures Use Case Optimization SKU (Test 1) Fix JavaScript error in SKU form Install and enable Dynamic Compression Change SKU ItemTypes to use Page Size 200, Max Results 1000 Change "Plant Feasibility" (SKU Plant Feasibility) to Tab Order toload as the first relationship tab Update Show/Hide Method used in SKU Forms to reduce waittime to 10ms (Tuned custom JavaScript) Remove foreign properties from the SKU Plant Feasibility andSKU Plant Feasibility Steel ItemTypes Change Starting page per userCustomerExample
    • 29. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 29Customer ScenarioPossible Measures Use Case Optimization Design Sites Use File Replication Configure replication times during low network traffic Use Case Optimization Manufacturing Sites No local vault Implement custom document download/viewing page
    • 30. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 30Step 0Service Pack Newest service pack Service packs may implement issues addressing globaldeployments Check if new service packs enhance your use case beforestarting a global deployment project
    • 31. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 31Global DeploymentNetwork and Non-Technical Aspects Network Configuration (WAN) Bandwidth Latency Gateways and Proxies Network accelerators … Non-Technical Aspects Project Management Methodology Process analysis and design Communication Testing Training Documentation Hotline / User support …
    • 32. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 32Questions?