Support Customization Steps - Smart3D

Support Customization is an important requirement of Modelling. It not only provides the visual model but also consists of data that is important for fabrication and construction teams. Needless to say that there are many standards and all the projects use different standards. This is one of the crucial activity during the project.

 Support Customization brings a lot of quality output at the table. Following are the important aspects of Customization steps that should always be followed.

Understand Support Standards

 This step is about gathering basic information. Many companies provide best information in their Support Standards, but it is important for the responsible person to go through information and understand that all that she/he needs to at least start are available. All the details, such as guide information, clamp details, section details are readily available. If not, try to get access to it with discipline.

Organize Information

 Now, as we have all the basic information arranged, let’s start organise, prioritise our list. Definitely, time is important to get the support developed, but development is a time consuming process. It’s next to magic, as a lot of Geometry and Trigonometry has to happen. Better discuss the list with discipline about their priorities. Once you’ve priority, look out for better execution. Is there anything that can be done to save some development time?

Development- Shapes and Assembly

 Since we’ve our map and gears ready, let’s hit the road. Some coding, some coffee! Magic of Geometry, Trigonometry, Matrix, Vertex and what not. And in no time, we’ve created (almost) perfect picture (3D Object).

Hierarchies

 Oh wait. Almost forgot! Let’s give an ease to access. Once the bulkload sheets are ready, bulkload them to client specific hierarchy. Yes we can have anything anywhere, but that’ll be a pain for long run. Have Clients specific Folder created and place everything there.

Quality Checks

 It’s always a good idea to test on Project Sandbox. Developers can have their own environment to develop, but testing should be done in environment where the UAT has to happen.

 Now, although developers have tested everything, but it’s always advised to have a User Acceptance Test (UAT) to happen. Modeller from project, who understands the requirements, should place and test before acceptance. Discipline can have a short checklist to test Support.

Deliver

 Now since everyone is happy, dll and bulkload sheets can be delivered to load on production plant. Once all the shapes are customized, source code should be stored safely at one location, where it can be easily retrieved when required.