Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

The below article outlines how Facilities Services Construction Services manages small project AMAG installation.

🖱️  Project Initiation

Project request submitted by Project Sponsor (i.e. customer) via the project intake form: https://cgis.uoregon.edu/calllog

Work Control Center process the request creating phases for:

·         D/C - Academic/Auxiliary

·         Construction Services (CS)

Leased properties require preapproval from AiM shop Real Estate

🛠️ Projects referred by D&C to FS Construction Services (CS)

  • CS notifies UOPD (Dir. of Physical Security, Security and Alarm Technician) to review request and weigh-in and approve to move forward

  • Scoping/estimating by Construction Services (CS), Electrical shop (EL) and Lock and Door Shop (LOCK)

    • Include UOPD (Dir. of Physical Security, Security and Alarm Technician in the scoping meeting)

  • AMAG Subcontractor scope/quote via EL

  • If non-standard functionality, involve FASS-IT to make sure it can happen from a tech perspective.

    • Example:  Knight Law, making sure the lockdown buttons can function as intended

  • CS prepares quote for Customer and sends to UOPD (Dir. of Physical Security, Security and Alarm Technician) for review

🛠️ Projects approval/pre construction

  • CS acknowledges approval, advises on schedule (usually still TBD at this point) and asks customer if they already know the lock schedule and user list

    • If not, customer should start gathering info

  • CS notifies EL and LOCK (including Access Control Program Specialist) once work order is set up

    • Work order will includes at least two phases for LOCK: door hardware changes (ex: electric strike) and function change/rekey

  • CS notifies FASS IT about upcoming project via ticket system at fass@uoregon.edu

    • FASS-IT rep will be assigned to project

  • EL & LOCK order materials (including subcontractor services) and advises CS and FASS-IT rep as to lead times

🛠️ Construction

  • EL & LOCK install infrastructure and hardware

    • Includes new data drop by NTS if needed (otherwise, use existing)

  • EL notifies central IT (NTS) about project, jack activation

  • CS, EL, or Contractor request IP via FASS ticket (fass@uoregon.edu), FASS-IT assigns IP addresses. 

    • NOTE: This can also be taken care of earlier in the project as well, once list of devices is known.

  • AMAG subcontractor panel terminations & programming (managed by Electrical)

    • Electrical notifies CS when subcontractor is finished (via WCC note or email)

    • If contractor is doing programming, FASS IT needs to be in the loop.  Most of the time, FASS IT is performing the programming.

🛠️ Post-construction

  • CS notifies customer and LOCK (including Access Control Program Specialist) when AMAG subcontractor is done with programming – ready for user list.

  • LOCK (Access Control Program Specialist) loads user credentials, coordinate with FASS IT if a schedule change is required, and prepares a notification for Work Control to distribute.

    • LOCK makes note of the 30-day waiting period from the notification unless the user requests different.

    • CS take the function change/rekey phase off-hold for LOCK

  • LOCK does function change and rekey after the waiting period.

    • After programming - System verification & punch by UOPD

Who needs to be involved with all project communications? Customer, Facilities Services (Construction Services, Electrical Supervisor, Lock and Door Shop, Access Control Program Specialist), FASS IT rep assigned, UOPD (Security and Alarm Technician, Dir. of Physical Security).

  • No labels