Architecture and engineering IT: support large files and design workflows

Trace a model through the project team

Identify where authoritative CAD or BIM files live, how references are linked and how internal and external teams receive updates. List the supported collaboration platforms and the permissions needed for each role. A large file that opens successfully may still be unusable if linked assets or access rights are missing.

Ask the provider to work within the design application’s supported collaboration methods. Consumer-style synchronization or ad hoc file copying may be inappropriate for some workflows. Your design leads and software vendors should help validate the approach before a provider changes storage or sharing arrangements.

Evaluate workstation and network needs together

List design software versions, plugins, hardware requirements and license-management dependencies. Request support for the actual workstation configuration rather than an assumption that every desktop is interchangeable. Clarify who diagnoses graphics, driver or plugin issues and when the application vendor becomes involved.

For remote work, describe file sizes, editing patterns and access methods. Ask what assessment will precede recommendations for connectivity, remote desktops or storage. Performance depends on several factors; a provider should explain its tests and assumptions rather than promise a universal speed improvement.

Coordinate changes with design deadlines

Operating-system, driver and application updates can affect project compatibility. Agree on a test group, approval owner and rollback method before broad deployment. Include license servers, rendering resources and printing or plotting equipment where they are part of the workflow.

Identify deadlines when disruptive changes should be avoided and decide how urgent security work will be evaluated during those periods. The MSP can present risk and technical options, while practice leadership makes the business decision. Document exceptions and follow-up dates instead of allowing temporary deferrals to become invisible.

Recover usable project work, not just files

Ask whether backups include linked assets, libraries and relevant configurations as well as primary models. Request a restoration test that a design user validates. A recovered file without the right version, references or permissions may not restore a project’s working state.

Define how project archives, external collaborator access and cloud-platform data are managed. Retention requirements should be established by the practice with appropriate professional advice. Keep project identifiers and workflow descriptions in a matching request; do not submit confidential drawings or client documents.

Compare specialist boundaries and transition scope

Onboarding may involve an application inventory, workstation assessment, storage review and vendor-support map. Ask for a transition plan that tests representative design tasks before changing the whole practice. Identify which application-specific work requires a separate specialist or vendor agreement.

Compare recurring support with storage migrations, hardware upgrades, license administration and rendering projects. Ensure the firm controls cloud accounts and owns documentation. A strong proposal states what the provider will support, how it collaborates with design leads and which outcomes it cannot guarantee.

Questions for prospective MSPs

1. Which application issues require our software vendor or a specialist?
2. How will you validate large-file collaboration before migration?
3. Does recovery testing include linked assets and usable project versions?
4. How are workstation updates tested around submission deadlines?