Design Manufactured Assemblies or Plan Manufactured Assemblies?
540558
Design, Design, Design\n\nIf you try to Plan the manufacturing, you will never see the product released. \nPlanning is only going to work with parts which have been properly designed. The design must take in consideration of manufacturability. You can design on paper something that can Never be manufactured.\n\nThe design must follow good manufacturing practices. Be able to be Tested and meet some kind of standard.\nThe design must have Component Eng, Mfg Eng, Quality & Purchasing all working together upfront. Not after the fact.
949730
Always start your project with a concept drawing. Then build your measurements from the Operator's Point of view. ( basic ergonomics and industrial engineering ) produce a sculpted scale version of your design, then reverse your engineering stance and retrofit regular engineering principles to the concept you project to your client peer.
1175942
http://www.stellman-greene.com/aspm/content/view/39/41/\n\nfurther....\n\nCem Kaner, co-author of Testing Computer Software has suggested that test plans are written for two very different purposes. Sometimes the test plan is a product; sometimes it's a tool. It's too easy, but also too expensive, to confuse these goals.\n\nIn software testing, a test plan gives detailed testing information regarding an upcoming testing effort, including\n\nScope of testing \nSchedule \nTest Deliverables \nRelease Criteria \nRisks and Contingencies \n\n#Test plan template, IEEE 829 format\n\n------Outline\nTest Plan Identifier \nReferences \nIntroduction \nTest Items \nSoftware Risk Issues \nFeatures to be Tested \nFeatures not to be Tested \nApproach \nItem Pass/Fail Criteria \nSuspension Criteria and Resumption Requirements \nTest Deliverables \nRemaining Test Tasks \nEnvironmental Needs \nStaffing and Training Needs \nResponsibilities \nSchedule \nPlanning Risks and Contingencies \nApprovals \nGlossary \n\n###Test plan identifier\nThe test plan identifier number is.......( to identify this test plan, its level and the level of software that it is related to. Preferably the test plan level will be the same as the related software level. The number also identifies our test plan to be a smoke test plan. This is to assist in coordinating software and testware versions within configuration management).\n\n\nReferences\nList all documents that support this test plan.\n\n#####Documents that are referenced include:\n\nProject Plan \nSystem Requirements specifications \nHigh Level design document \nDetail design document \nDevelopment and Test process standards \nMethodology guidelines and examples \nCorporate standards and guidelines
229106
It's feasable, but a real pain in the butt. Manufactured homes are actually built stronger tha a lot-built home (required for the moving of the individual pieces), but it would almost seem easier to just have the whole thing moved as a unit, like they do with a standard home.
803655
Planning a design that will go into the future instead of something that works/fits just for today
1047343
manufacturing\nwarehouse worker\nconstruction
102977
symetric designs, ratios from diagram to real material
568757
change designing to design
1088147
Analysis is understanding the problem you're trying to solve. What environment is it in. Who are your customers going be. What behaviors should your solution exhibit. etc.\n\nDesign is figuring out how to organize the solution once you've done the analysis and you understand the problem.\n\nUsing resouces like UML, analysis would be in the requirements, use case, activity diagram arena.\n\nDesign would be in the class diagram, sequence diagram, state diagram section.\n\nArchitecture kind of has a foot in each camp.\n\nGenerally you want to do a fair amount of analysis before design, otherwise you'll start building a solution for a problem you don't truly understand. These solutions usually aren't a good match. They are difficult to fit the problem once you eventually understand it, and they generally aren't as flexible.\n\nHowever, this doesn't mean that analysis has to be 100% complete before design begins. It's just wise to have done a fair amount of analysis first.
756526
CAD = Computer Aided Design\nCAM = Computer Aided Manufacturing, Computer Aided Machining, Computer Aided Management
289437
Yes, why not? You are talking about designing and do your design with whatever thing possible.
1134906
Here's a link to a PDF file I wrote consisting of all the steps involved (though not quick enough to beat the other two answerers...)\n\nhttp://prash4.esmartdesign.com/ans2.pdf
424702
the project management team has a fair idea that whatever be the task at hand, it can be broken down into predictable milestones. \nAnalysis and design are two such milestone. SO the plan just lays them out as to-do's. \nOver time as each milestone is reached the plan is reviewed to account for things that the last milestone reveals about \nthe overall needs/progress.\njainnys\nhttp://www.mindexp.com
639415
(briefly)To utilize a software to make drawings for engineered parts, machines, construction dwgs. etc. This is an evolving process from the engineer to mechanical/architectural contractors to add definition to the design and to utilize the known means of symbols/abbreviations to parlay communication to be used for bidding, approval, detailing, and installing.
586661
There are situations where assembly code is the\n"right" solution -- typically when special instructions\nare needed or on rare occasions when a tiny piece of\ncode is both critical and not sufficiently optimized\nby a compiler.\n\nHowever, for the Sieve of Eratosthenes, a good compiler\nshould be able to generate code which is comparable to\nwhat most humans could write.\n\nI mention this to explain why I would recommend that\nyou take some C source for the Sieve and have your\ncompiler generate assembly code for you.\n\nOn a Linux/Unix/Solaris system, use the "-S" option:\n\ncc -S -O sieve.c\n\nand then take a look at the file "sieve.s".\n\nFast and easy.\n\nIf you want the assembly code to be easier to read,\ndon't optimize the code (ie. don't use the "-O" option).
129172
At one time most machines were hand-crafted including rifles.  You could make part A then make part B that would fit it.\n\nMass production of parts that must fit together require any part A to fit any part B and properly work in any finished machine.  Quality Control may insure that all the materials used are correct to prevent unsafe substitutions.  However, experienced designers establish the tolerances for the needed parts to avoid rejects but insure parts will always function properly with required parts lives.  Often tolerances are propritary info and closely guarded because of the expense required to get it right.  Competitors would love to skip all the bother and make an adequate machine at less cost based on someone else's research and experience.  Machinists manufacture the parts to be within the tolerances specified on mechanical drawings.  Quality Control samples the parts to ensure compliance with the drawings and sometimes checks every part if critical.  If tolerances are set too tight costs will escalate and rejects will abound and if tolerances are too loose, machines may malfunction.  The objective is to strike a happy medium (good quality) to manufacture successful machines at reasonable costs.
922547
Do a project on which product is better