Tuesday, November 5, 2013

Let's play tic-tac-toe in Autodesk Inventor via Vault

How can we make any training less painfull and more clear for end user? Of cource, by just turning it in game! Sometimes customer needs to take a continious practice in working with PDM system.

I've made some kind of game you'd like: a tic-tac-toe in Autodesk Inventor.
Gameboard and control panel
While playing you can use this assembly to enhance bunch of collaboration and data management skills:
  • check in/check out
  • revisions
  • reviewing
  • life cycles
  • etc.
There's video that demonstrates possibilities of Autodesk Vault in engineering collaboration and assembly modification on a fly within Autodesk Inventor.

The assembly archive is stored in Google Drive in tic-tac-toe.zip.

Wednesday, October 9, 2013

Autodesk Vault DYK: storing enterprise instructions

Meet the first of the Autodesk Vault "Did You Know?"!

Maybe, you'll find some fresh ideas about implementing and improving of PDM/PLM for your customers (if you're System Integrator) either within your Enterprise (while you're System Administrator). So let's start right now!

AVDYK0001: "You could develope and store enterprise instructions for your stuff in special Vault folder".
Here's example algorythm to do this thing:
  1. Create library folder that could be called like "PDM instructions".
  2. Publish your enterprise standards into folder in common format: Word, Excel, Visio, PDF etc.
  3. Create Category definition "Instruction".
  4. Assign Revision scheme to this Category.
  5. Assign Lifecycle to category.
  6. Mark all instructions with "Instructions" Category.
  7. Assign revision "A" to all instructions files.
  8. Manage security for files or whole folder to protect them from uncoordinated editing.
  9. If it's needed, you could create new revisions of standards and/or develope them jointly.
  10. The instructions could be accessed both from Vault Explorer and from web browser.

Thursday, February 7, 2013

Suggestion of "PDM at PLM" model: "conveyor at assembly line"

The understanding of collaborative design process could be represented using assembly line model. In this model PDM as it is, could be represented as conveyer belt. PDM tools - as automated robots. CAD software - as instruments at worker’s hands. Workstation computer - as workbench.
PDM as conveyer at assembly line (AP Photo/Ford Archives)
The conveyor belt is moving from past into the future, and from the start of the project, through the desing process straight to the project closing. It carries “details” (documents, models, drawings), and allows to employees (end users, engineers, project managers, Quality Department) join the process in right time.
Workers are building models, using boxes of parts (components libraries, standard solutions library), that they really need at current stage of project. This conveyor could be branched, for parallel work.

The abstraction of check in (check out) operations with this model becames more comprehensible -- it’s operation of taking (returning) working part by employee from (back to the) belt into (out from) workplace to provide certain operations.

Why is assembly line model useful?

The common submission of PDM solutions and PDM systems of end-users, customers and some of implementors grotesquely represented hereinafter. There is PDM, to which everybody are connected. There is necessity of employees to do their work. But how, why, what for -- there is no common answer and often even there’s no this questions.

Common submission of PDM and PDM
The conveyor model solves this problem: everybody can see what’s he doing as a part of work process within the project and company. It’s easier for integrators to build actual PDM model , using customer’s business process models.

Using of model brings next benefits: becomes possible to use common math and business methods of assembly line theory: atomize big jobs at smaller parts, using less educated personal, etc. At now PDM could be developed as assembly of pre-configured parts, and you can clearly see, which “robots” are you need to include into line to automate handworks. Also it allows to build more flexible solutions and even automatically calculate their models, according to requirements.

I'd like to hear your opinion.