In our postagem anterior, we outlined an approach for training users to make the transition from another CAD system to BricsCAD. In that post we stressed using familiar contexts, like a project that has been completed previously, to isolate training content to just the software differences by removing as many variables as possible. 

In this post, we’ll assume that the first phase of training has been completed and that users are becoming familiar with the overall look and feel of BricsCAD. Now we’ll pivot to demonstrating some key differences, new features, and strategies you can use to make users more at home yet aware of cool new features in BricsCAD that can boost their productivity. Let’s see how. 

Usar um Pouco Mais de LISP

Some commands in BricsCAD function very much like commands in other programs but don’t use the same command name. Here are a few examples to get the conversation started: 

ORBIT.AutoCAD® users are used to a command called ORBIT which is very much like BricsCAD'sRTROT . Assim que você mostrar a um usuário do AutoCAD® o comando 3DROT, ele se sentirá em casa.
CAMADA. AutoCAD® users expect the LAYER command to bring up a floating (modeless) palette that can be left open while working. In BricsCAD the default implementation of LAYER brings up the Drawing Explorer command set to the Layers tab (see Figure 1) but this is a modal that does not allow the user to keep working. Enter the BricsCAD LAYERSPANELOPEN command which looks apenas like an AutoCAD® user would expect (see Figure 2) – so our challenge is to substitute the LAYERSPANELOPEN command for the LAYER command and AutoCAD® users will again feel right at home. 

Figure  1 – The EXPLORER command has several applications in BricsCAD – including layer management.

Now go back to our blog post on LISP Concepts for Easy Migration e você verá como colocamos o código no arquivo STANDARDS.LSP para criar os comandos ORBIT e LAYER/CAMADA para que atendam às expectativas do usuário do AutoCAD®. 

Figure  2 – The LAYERSPANELOPEN command works in a modeless (floating) fashion very much like AutoCAD®’s LAYER dialog.

Vamos expandir um pouco mais essa lógica, considerando as funções do Alias.

Replicar Alias de Comandos

Users who’ve used AutoCAD® for a long time typically know not just the command they want to use (like LINE or ERASE), but they often use an alias shortcut to access them (like L or E, respectively). Replicating those aliases can also be a great way to make AutoCAD® users feel at home in BricsCAD. 

Aqui estão algumas funções de alias que os usuários perguntaram durante o treinamento: 

ADC. This is short for Design Center which BricsCAD emulates with the EXPLORER command. We could easily add this code to our STANDARDS.LSP file to get the same result:

(defun C:ADC ()
(command “EXPLORER”)
(princ)
)
BE. This is short for Block Editor which BricsCAD handles with the REFEDIT command. We could easily add this code to our STANDARDS.LSP file to get the same result: 

(defun C:BE ()
(command “_REFEDIT”)
(princ)
)

Edite o software para se adequar ao usuário em vez de treinar o usuário para aprender um novo software. 

The idea here is that rather than teaching AutoCAD® users what a similar command in BricsCAD is, you can just make the keystrokes the AutoCAD® users already know launch into the right command and bypass training altogether. My general rule is to edit the software to fit the user rather than train the user to learn new software, and replicating command aliases is a great way to follow this rule. 

Comandos Somente do BricsCAD®

When migrating to BricsCAD it is, of course, our first task to make users comfortable, but we must also be sure to point out commands BricsCAD has those other CAD systems don’t. Here are a few that I’ve used which novos BricsCAD users seem to really enjoy: 

BLOQUIFICAR Automatic recognition of repetitive sets of geometry will be recognized and “Blockified” for easy subsequent editing. Think about opening a drawing of a building where all the door blocks had been exploded and what a pain it would be to deal with that mess? BLOCKIFY pode limpar desenhos assim em segundos e comprimir substancialmente os tamanhos de arquivos DWG ao fazê-lo. 
QPRINT Saída rápida de impressão usando os dispositivos e configurações padrão associados a um desenho/layout, sem exigir de uma viagem ao comando Publicar. 
PDF System variables. A wide variety of system variables (SYSVAR’s) that control default parameters for PDF files can be saved in template files, thus saving a trip to the PageSetup . 

These are just a few suggestions and you’re sure to find more your users value as you dig into BricsCAD's full feature set. Whilst I don’t want to overwhelm new BricsCAD users with too many new features all at once, I do want them to see what’s possibleand how much more productivity they have access to. 

Apimentando o Treinamento com alguns novos comandos

À medida que você conduz os usuários pelo processo de treinamento, pode ir lançando novos comandos de vez em quando, em contexto que faça sentido. Aqui estão alguns exemplos que você poderia usar: 

Quando está pronto para imprimir Mention that the QPRINT command could save keystrokes and time and illustrate the use of it after the users have mastered basic print/plot functions.
Quando editar camadas Take time to show the users how the EXPLORER command gives them access to all the editable parameters in their drawing – not just layers. Most users I’ve trained say, “Oh, that’s different but I really like having everything en one screen!” 
Quando fizer uma pausa Show the users an example of BLOQUIFICAR just so they see the capabilities. While they may not deal with a bunch of exploded blocks every day, they will save tons of time using BLOQUIFICAR when they do. 

Again, these are only a few suggestions. The main point is to introduce new features gradually rather than overwhelming users with a bunch of new commands at the start. I’ve found that once users see what is available, they’ll start digging into BricsCAD's command vocabulary independently and find applications I’d never thought of demonstrating. 

Resumindo

I hope this 5-part series on how to manage the migration to BricsCAD has illustrated how you can use system tools, LISP, and well-designed training to make the process easier for both you and your users. In future articles, we’ll continue to look at more features that CAD managers can leverage to make BricsCAD productive as well as digging into customization and programming topics. 

Pronto para experimentar o BricsCAD?

Fácil de experimentar, fácil de comprar, fácil de manter. Isso é o BricsCAD. Experimente todos os nossos produtos, gratuitamente por 30 dias em www.bricsys.com/pt-br/. Liberdade de escolha, além de licenças perpétuas (permanentes) de produtos que funcionam em todos os idiomas, em todos os lugares. Você vai adorar o que construímos para você com a família de produtos BricsCAD V21.

Mais Histórias da Confraria dos Gerentes de CAD

  1. Mecânica de Instalação de Rede - Parte 1
  2. Mecânica de Instalação de Rede - Parte 2
  3. Conceitos LISP para Fácil Migração
  4. Treinamento Mínimo para Aprendizagem Máxima - Parte 1
  5. Treinamento Mínimo para Aprendizagem Máxima - Parte 2
  6. Três Etapas para a Adoção do BricsCAD
  7. Preparar para Implementação - Parte 1
  8. Preparar para Implementação - Parte 2
  9. Preparar para Implementação - Parte 3: O Campo de Provas
  10. Preparar para Implementação - Parte 3: Materiais de Treinamento
  11. Preparar para Implementação - Parte 3: Dicas de Treinamento Remotas
  12. Preparar para Implementação - Parte 6: Desenvolvimento e Suporte