![]() |
||||||||||||||
|
|
||||||||||||||
|
|||||||
| Notices |
| General Discussions For general discussions about rendering, animations, walkthroughs and CGarchitecture |
|
|
LinkBack | Thread Tools | Display Modes |
|
|
#1 (permalink) |
|
Junior Member
Join Date: Sep 2003
Location: India
Posts: 24
Name: samir jadhav |
Any company which has a corporate BG would understand the relevance of a Process documentation as a part of its policy.
'Process' documentation helps us put our knowledge on paper and reduce the dependency on the knowledgable person. The continuity of business is the key criteria. Even if the company is taken over by new mgmt or skilled associates, they can refer to the process documents and continue its business of providing services to its client. I am interested in identifying and documenting process that describe the typical 3d workflow in detail. The process could later be modified to describe specific workflows such as architectural viz process or character design & animation process, visual effects process pipeline etc.. Your feedback will be very helpful.. References / Links also expected. Please share your existing processes / new ideas / suggestions/ recomendations Thanks.. |
|
|
|
|
|
#2 (permalink) |
|
Super Moderator
Join Date: Dec 2001
Location: Cardiff, Wales, UK.
Age: 36
Posts: 6,488
Name: Stephen Leworthy |
i personally think it's overkill. we employ skilled users, give them the client's brief, and we get the job done. it's not a viable use of time or resources to write down our methodology. we all know what the other chap is doing
|
|
|
|
|
|
#3 (permalink) |
|
Veteran Member
Join Date: Mar 2004
Location: Bradford
Age: 27
Posts: 1,280
Name: James Taylor |
i tend to agree with strat.
Although i guess you can come up with a process document that outlines the process from start to finish it can not take into account a persons artistic skills - the bottom line is that 80% if not more is an individuals skills - every artist will employ their own methods and processes to achieve similar results, thats why these forums exist to help us share our skills and leasrn from others |
|
|
|
| Sponsored Links |
|
|
#5 (permalink) |
|
Senior Member
Join Date: Oct 2005
Location: Yorkshire
Age: 23
Posts: 447
Name: Dean Punchard |
i too agree with strat, different people use different techniques, but in the end we come up with the same outcome. for example i apply base textures as i model, where as other people will model everything first, then texture. in a studio environment, it would be hard to have a rule book to follow, and would also squeeze out a lot of the creative and experimental sides to projects.
__________________
Pikcells Animator, Modelling & Environment Designer |
|
|
|
|
|
#7 (permalink) |
|
Veteran Member
Join Date: Jan 2005
Location: Brisbane
Age: 33
Posts: 1,361
Name: Justin Hunt |
I disagree with you guys.
Working in a colabrtive environment it is essential that all users use the same filing, naming and issuing systems. I makes it possible for anyone in the team to pick up any job, at any stage and know what is going on in that file. It also makes it easier to work on projects that have been archived years ago. I have worked with people who had a tendancy to name their file "Fred" or "This is Crap", or save some maps locally and others on the server. We'd spend ages trying to decypher their projects. It also makes it easier for new staff to be able to jump in and start working. It makes to easier to quality control, keep track of projects and cover your ass should anything go wrong legally. Have you ever gone through an audit? Having said that the systems should be flexible enough to accomadate any job and variations thereof. It should be able to evolve as the company grows and new working methodes change. Its not nessesary to be pedantic and rigid. Its also not nessesary to reinvernt the wheel on every project. You only need to document workflows and methods in the brawd sence, not every key stroke. And you certainly dont need to fire anyone not following proceedures to the letter. JHV |
|
|
|
|
|
#8 (permalink) |
|
Junior Member
Join Date: Sep 2003
Location: India
Posts: 24
Name: samir jadhav |
way to go justin..
I do actually agree with others to an extent. but like Justin said, in an organisation where emphasis is laid on collaborative work and business continuity, identifying and documenting processes is a part of the job. If we can share more info on these lines.. it would be so helpful.. keep it up... |
|
|
|
|
|
#9 (permalink) |
|
Senior Member
Join Date: Oct 2005
Location: Yorkshire
Age: 23
Posts: 447
Name: Dean Punchard |
is its not exactly about processes, more about structure and organisation?
here we use several template folder structures, template files, and a naming convention to keep everything structured. these change depending on that kind of project, eg animation, vr and still images.
__________________
Pikcells Animator, Modelling & Environment Designer |
|
|
|
|
|
#10 (permalink) | |
|
Junior Member
Join Date: Sep 2003
Location: India
Posts: 24
Name: samir jadhav |
Quote:
(Maybe in a doc / pdf format.) Last edited by jadhav333; August 11th, 2007 at 06:29 AM. Reason: added some more comment. |
|
|
|
|
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | |
|
|
|
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| work process flow chart | selvaimages | General Discussions | 4 | July 17th, 2007 10:30 AM |
| How is the process of making an architecture animation? | tom yu | General Discussions | 8 | March 20th, 2007 08:33 AM |
| What's your modelling process for a house? | mzagorski | 3ds Max | 3 | November 10th, 2006 06:32 PM |
| default process priority | Wayne Harney | Hardware and Technical Discusions | 6 | October 24th, 2006 01:05 PM |
| Site plan. Your process? | JHalton | General Discussions | 5 | October 28th, 2004 07:39 AM |