Creating CI: (example here)

• Title: Basic description of issue
  • Begin with Unit/Room # or Type
  • [UNIT/ROOM#] - [SHORT DESCRIPTION]
    • When using the VDC Power Bi report for issue tracking, including Unit # in CI title is not required
  • Include trades or components involved when possible
  • e.g.
    • Unit 1201 LR – SA Duct w San Plum
    • Unit Type A2 MBa - FP branch w Mpipe
• Description: twofold usage
  1. more detailed information about the issue
     • e.g. the ductwork coming off the AC closet is conflicting above ceiling in the Living Room with the sanitary line from the kitchen sink above
  2. Details of the assignment/correction for assignee
     • e.g. Ductwork modeler to drop duct down 3" to clear sanitary and then offset back up prior to getting to popup, see markups
• Location: may be as specific as required (Power Bi report filtering allows for this)
  • Be mindful of projects where they have created "Unit Type" Locations at Tier 2
  • When elevating to RFI or Observation:
    • drill down to lowest tier possible on the RFI or Observation
    • Leave the CI at the Level/Area
• Due date: 1 day before next meeting
  • Unless the modeler has agreed/committed to an earlier date, in which case use that date
• Comments: back and forth regarding the details of the assignment
• Type: these cannot be edited or changed or removed. 
  • Click here for Use cases for each type
• Assignee(s): CI are only assigned to coordination team members or KAST On-Site Staff