In Build, we can attach a schedule (e.g., .mpp) and view tasks. However, Doc, where project teams truly centralize information does not natively ingest schedules. As a result, engineering/document control lives in Docs while time (activities) lives elsewhere, fragmenting project governance and slowing coordination. Proposed solution: Enable Docs to natively ingest and surface schedule activities, with options to: Upload schedules at theproject level (support .mpp, .xer, and .csv), exposing activities as addressable objects in Docs. Link documents to activities: allow associating 2D sheets, PDFs, specs, RFIs, submittals, models, markups, and issues directly to a selected activity (one-to-many). Kanban board for activities (optional view in Docs): render schedule activities as cards, with configurable columns (e.g., To Do / In Progress / In Review / Done) and swimlanes (e.g., by WBS, disciplina, CWA/CWP, fornecedor). Drag-and-drop should update the activity status/field mapping. Bi-directional sync: when enabled, keep key fields in sync with the source schedule (ID, name, dates, % complete, responsibility). Offer read-only and write-back modes with audit trail. Templates & rules: mapping presets (e.g., WBS → folders; Discipline → metadata tags). Admins define rules to auto-suggest links (e.g., match activity code in filename). Permissions & auditability: respect ACC permissions; log who linked/unlinked documents, moved Kanban cards, or changed mapped fields. Export logs (CSV).
Show More