Stuff not included on the course...

 
  • I'm taking a 3 day basic admin. course next week...paying for it out of my own hard earned cash...so basically I want to learn as much as possible over the time I'm there...

    I'm worried that I'll do the course get back and hit a problem straight away...thinking "they never showed me how to do that"...

    So I'd like a bit of feedback from other people who've done the course...
    Is there anything not on the course that I may need to know ?

    If people give me key words I can quiz them on the course...

    I'm not talking advanced stuff here...obviously that'll come later...

    Cheers
    Neil
  • I would have taught you for half of that price and I take pay-pal :-) Thought your company was paying for it...

    Ask how DAC is defined and how the excel sheet loading works.

    Pay attention to the philosophy of database naming convention.

    If global is covered in the course, ask how extract under global environment works, and get a demo for a large database transfer.

    I think your trainer will be cursing me by now...
  • Here are a few things that come to mind… There are many more, I am sure… Don’t expect to walk away an expert though…

    Command Line Syntax for database creation:[/U]

    [INDENT]Depending on Version, this could be helpful for you. 11.6 and earlier has no convention for creating the top level elements (SITE, DEPT, CATA, etc…) inside of Databases. The only way is by entering you module, and doing some PAINFUL MDB order swapping, allowing you to create these elements in the proper database, OR… using command line syntax to create the databases (using this method allows for element creation at the time the DB is created). Note: version 12 now has a convention for doing this through the forms, but it is still useful.[/INDENT]

    Really quiz them about transferring databases between teams (easy, but sometimes overlooked):[/U]

    [INDENT]Some people only create teams for discipline segregation. When you get into multiple locations, sometimes teams can be used to manage work scope split, and is one more level of assigning access rights. When used right, they are helpful.

    Get a full understanding of Extract Levels, and how they work (and how to fix things when they break):

    This is one of the most debated subjects by administrators (please, let’s not debate here – there are posts already about this). They are great when they work and your worst nightmare when they don’t. Gain enough understanding to be informed and knowledgeable when your management says “we want to use this extract thing”.

    Extracts claim data down to lower level children (parent – child relationship). At times claims will need to be dropped, and the normal approach in the modules will fail. Admin intervention will be required. Know how to do it.

    Get AVEVA’s spill on how many levels to use, and their feel for using them.  They used to sell them as a great concept. But after they have spent MANY, MANY hours writing bug fixes to handle many complicated usage scenarios, I would bet they are not so chipper as to suggest their use (btw – never cross locations with extract claims, if you get into GLOBAL usage – It’s worth asking about).[/INDENT]

    Another largely debated topic is the use of Foreign Databases, especially in the area of Catalogs:[/U]

    [INDENT]Some admins love them… some were bitten by them long ago and would never dream of using them. Personally, I am a fan of them, AS LONG AS YOU HAVE GOOD CHANGE MANAGEMENT IN PLACE. If you are with a company where the only 3D Design procedures are for how to cash your paycheck on Friday… you might want to consider doing some soul searching on their use.

    If you get into a global situation, there is a sequence for updating if the Foreign DB’s are non-global…[/INDENT]

    Database Naming/numbering conventions…[/U]

    [INDENT]Learn what they have to say about this topic, then throw that info away. :0)

    Use a naming convention that can support wild card sorting in the filter box (you’ll understand in training)

    Regarding Database split, you will need to learn to balance the number of databases, and the scope of work. This is something that they will largely NOT be able to offer much advise, as they cross many different industries. My rule of thumb for this is consider a discipline split first, then look at how the projects scope of work is arranged (i.e. are the same teams running pipe, or do we have different teams). Also, look at how much potential you have for outsourcing or splitting scope across a Global project.[/INDENT]

    Understand DACS (Data Access Controls)[/U]

    [INDENT]At a minimum, Site and Zone (or DEPT and Regi DACS should be considered). This is another largely argued point. When the argument comes up, ask your designer or manager to go back to their desk and create a SITE in database XYZ/ABC. If they don’t know how to do this, implement DACS quickly… Once things get put into the wrong database, you stand a chance to lose links if you datal out, and in to a new databases (database reference numbers will be different)[/INDENT]

    Hope this is helpful...

    Charles
  • [QUOTE=de_ding;29397]I would have taught you for half of that price and I take pay-pal :-) Thought your company was paying for it...

    Ask how DAC is defined and how the excel sheet loading works.

    Pay attention to the philosophy of database naming convention.

    If global is covered in the course, ask how extract under global environment works, and get a demo for a large database transfer.

    I think your trainer will be cursing me by now...

    De... If you are getting cursed right now, wonder what they are saying about me...
  • Thanks for that ccotton...gives me a few questions to ask the trainer...
    I'll definatly get value for money now...
  • Another good way to get value is to concentrate more on the concepts instead of the specific command syntax or forms. If you make sure you've grasped the concepts everything else will seem easy...

    ...and ask them about their recommended approach for managing the design of a shared workscope across multiple Global locations.

    While you're about it why not ask for detailed information about the Admin requirements for the other AVEVA apps like MOM, CM, DM, MDS etc?

    I'm not sure you'll be able to fit all this in over just 3 days :teeth_smile:
  • Ask them about picture files in draft and "pic"-folder in the project folder.