Design solution library and automation tools
The designer finds previously verified details, calculations and work tools. Before applying in another project, he can check their assumptions and suitability.
The previous detail or computational methodology is found without its application conditions, review history and the expert responsible. The designer repeats the same search work or shifts the assumption inappropriate for the new project.
How the solution works
- The engineer reviews the previous solution along with its assumptions and the conditions under which it was applied.
- The expert approves the overall application limit, required project verification and version maintenance.
- The designer finds the candidate on the basis of real need and verifies his suitability for the new case.
- The used version and local application are recorded in the project history.
- The library correction puts forward a review of previous uses based on its significance, without rewriting the published projects.
Key challenges
- Previous decisions and details are hard to use
Solution capabilities
A solution with assumptions
The detail or methodology shall indicate its purpose, the conditions of application and the documents on which it is based.
Search by use
The employee selects solutions based on the part of the project, technical conditions and required result. variants not yet approved are clearly marked.
Version maintenance
The expert in charge reviews the change, the validity limit and the need to alert previous users.
Customization History
The project retains the link between the used version of the library and the local replacement; the design edition is stored in its responsible environment.
Repeated action automation
The template or spreadsheet checks that the data provided is suitable for the intended calculation. An incorrect case is passed to a specialist who also performs the required result review.
Business context
- Previous decisions and details are hard to use
- The previous detail or computational methodology is found without its application conditions, review history and the expert responsible. The designer repeats the same search work or shifts the assumption inappropriate for the new project.
- Previous experience helps to prepare the right proposal faster
- The design client expects a reasonable solution and a real working deadline. The accessible library of verified details allows the team to assess what can be adapted and what will need to be redesigned. This makes it easier to plan the cost of the service while maintaining the technical review of a specific project.
Core features
- A solution with assumptions
- Search by use
- Version maintenance
- Customization History
- Repeated action automation
Key integrations
- Design Tool Libraries
- A detail, template or computational tool with its version is used.
- Project Information Environment
- The project used a solution, local changes to it and the result of the review.
- Registers of methodologies and technical sources
- Technical sources, their approvals and significant changes are permitted.
Potential impact (%)
The ranges indicate an illustrative relative change in the metric under the stated assumptions. Results depend on the starting position and actual use of the solution. Percentages for different metrics must not be added together.
Re-work for solution search and development
16–42%Decreasing
This illustrative scenario assumes that 40-70% of information searches and repeated cross-checks can be addressed. That share is assumed to fall by 40-60%. Company data is needed to verify both the addressable workload and the resulting change.
All timings for proper solution selection and customization are compared, including verification.
Repair work on outdated design base
12–36%Decreasing
This illustrative scenario assumes that 30-60% of manual data entry and handover work can be addressed. That share is assumed to fall by 40-60%. Company data is needed to verify both the addressable workload and the resulting change.
Additional work on the use of an approved faulty old part or methodology is measured. Similar-scale projects are compared, separating the implementation of a new requirement.
Conditional calculation scenarios. The assumptions have not been validated against client measurements.
When this solution is relevant
- The designer copies an old detail whose loads or other application assumptions are no longer known.
- After the general calculation tool has been corrected, it is unclear which projects have left the previous version.
Implementation requirements
Specialists describe when a library solution can be applied repeatedly and which versions of it are valid. For automated calculations, the required data, result verification criteria, and actions when information is missing are determined.
Further development options
- Libraries of complementary discipline solutions after verification of their application limits
- Search help providing a response with a specific validated version of the methodology