Plannerly
Create
Log in
Sign up
Feedback
Ideas
Changelog
Boards
Ideas
Powered by Canny
Ideas
Details
Category
Select a category
Showing
Trending
Sort
Trending
Top
New
Filter
Under Review
Planned
In Design
In Progress
Complete
posts in
All Categories
All Categories
Need More Info (2)
Add AI-powered element-to-task linking
For poorly defined models where classification structures or naming conventions aren’t followed, AI-driven element recognition could automate the linking process and leave only final validation to the expert
0
2
Search, filter, tag, or group SmartFields
In case of a larger amount of SmartFields, such functions would make it easier to find and use SmartFields
0
5
Verify feature - Have Reports of the Percentages of the scope generated to Excel or PDF
Have Reports of the Percentages of the scope matching the Models be generated to Excel or PDF in a user-friendly manner. Currently we had to screenshot those number/percentage individually and paste to word or excel and then PDF out as a report.
1
5
Create Scope from an existing 3D model
Reverse engineer scope content from a 3D model by choosing the driving property from the model properties as the task name.
2
13
Global Smartfields that works across Plannerly Modules
The Idea is that now that we have the ability to create Custom scope fields, that we can have the ability for smart fields created in Docs to be added to these Custom scope fields or versa via , created on the scope custom field can be used in other modules like Docs I just want to populate some of my fields in my task with information already on the Docs smartfields :-) maybe with links?
2
4
Alternate AKA Information Requirements Names ("Property Aliasing")
Allow users to add an additional column (or field) for alternate names (e.g. "Name #2" or "AKA") when defining information requirements. This helps support workflows where the same parameter might have different names across multiple modeling platforms. The system should recognize either name when checking against model elements for compliance.
2
·
under review
10
Use AI to define regional verification rules
For example, fire ratings can vary depending on the region or building type. Additionally, the values may be preceded by different symbols or abbreviations depending on the language. Leverage AI to establish these specific rules
0
6
Archive Scope Tasks Before Deleting
In order to avoid accidental data loss, before deleting tasks, first archive them. This function could be extended to archiving Scope folders, task groups, task rows and milestones too
0
4
Enable "Select All" and "Clear All" functions for copy and paste operations within the Scope Grid.
To make the copy and paste operations easier in case of a decent amount of task fields, these functions will be super helpful
0
1
Apply task linking rules to IDS export
Use the task linking rules to apply filters on exported IDS applicability criteria.
0
3
Load More
→
Powered by Canny