Submit Your Suggestions for Viewpoint Team

RFI Workflow

There are a number of issues with the workflow of the RFI module. Generally speaking...

1. Subcontractor creates a RFI and sends to a General Contractor

2. RFI is reviewed by the GC, at which point it is only visible to the Subcontractor and GC. The GC has the option to promote it to a GC RFI (3b) or answer it (3a).

3a. If it is answered by the GC, the Architect would never see it. The Sub is notified of the answer.

3b. If it is forwarded to the Architect, the Architect will review and may (4a) or may not (4b) forward to a Design Partner (Engineer).

4a. If the Architect forwards it to a Design Partner, the Design Partner can provide comments and return them to the Architect. However, the Design Partner should not be able to answer the RFI.

4b. If the Architect answers it, it is returned to the GC who then accepts the answer and notifies the Sub.

The way the module is currently written...

A. Subcontractor can create and send the RFI to anyone without GC review.

B. Anyone can answer an RFI. RFI should only be answered by the Architect.

C. The Architect can see unfiltered Comments/RFIs from Subcontractors

  • Gravatar Amanda Simantel
  • May 24 2017
  • In Review
Company
Walsh Construction Co
Job Title / Role
I need it...
Yesterday...Come on already
  • Attach files
  • Admin
    Aaron Jost commented
    May 26, 2017 07:29

    Comments added inline bolded


    There are a number of issues with the workflow of the RFI module. Generally speaking...

    1. Subcontractor creates a RFI and sends to a General Contractor  [AJ]:  Subs are able to log in and create RFIs.  With the update coming next week we have streamlined the sub's (collaborator's) experience on the fields they can fill in for the GC.

    2. RFI is reviewed by the GC, at which point it is only visible to the Subcontractor and GC.  [AJ]:  Correct - only the sub and GC are able to see the RFI at this point.  The GC has the option to promote it to a GC RFI (3b) or answer it (3a).

    3a. If it is answered by the GC, the Architect would never see it. The Sub is notified of the answer.  [AJ]:  Yes -- solution supports this

    3b. If it is forwarded to the Architect, the Architect will review and may (4a) or may not (4b) forward to a Design Partner (Engineer).  [AJ]: system supports forwarding on to the Architect.  Architect can subsequently forward on to design partner (prerequisite is the the design partner is a user of Team).  Coming in the next release is the ability of the GC to create a related RFI and send it to the Architect.  This separates the upstream from the downstream - where with a Forward, the sub is still a participant on the RFI.

    4a. If the Architect forwards it to a Design Partner, the Design Partner can provide comments and return them to the Architect. However, the Design Partner should not be able to answer the RFI.  [AJ]:  If the GC has created a related RFI and sent to the architect, the architect can forward on to design partner...design partner can 'Respond' to the RFI - and the GC still owns the decision that the RFI has been answered. 

    4b. If the Architect answers it, it is returned to the GC who then accepts the answer and notifies the Sub.  [AJ]: Using the 'Create Related' capability, the GC can get the answer from the architect separately and pass that through to the sub.



    The way the module is currently written...

    A. Subcontractor can create and send the RFI to anyone without GC review.  [AJ]: Delivering this month project settings for RFIs that will allow you to default who the RFI is sent to based on the 'Type' of RFI.  You can set it up so the Sub's RFIs always go to the GC.

    B. Anyone can answer an RFI. RFI should only be answered by the Architect.  [AJ]: Let's walk through this - it is likely an authorization thing that will be resolved through the role the different participants are.

    C. The Architect can see unfiltered Comments/RFIs from Subcontractors  [AJ]: Using 'Create Related' the comments are specific to the RFI and the architect's comments would not be seen by Subs.

  • Gravatar

Dear Viewpoint Suggestion Box contributor;

We at Viewpoint sincerely thank you for your contribution to Suggestion Box on how we can improve Viewpoint products. While we can’t do everything at once, we rely upon your feedback to help guide the prioritization of our product improvements, and Suggestion Box is a critical tool for us to understand and prioritize our customers’ needs. Viewpoint reviews Suggestion Box regularly for all of our products and updates statuses, adds comments, and performs various house-keeping (including deleting) as needed to ensure that Suggestion Box is maintained as a productive environment for product enhancements requests.