Sr Field Engineer - Low Voltage Cabling

Field Engineering Responsibilities:

1. Closeout
2. Redlines
3. Test Audits
4. Lessons learned
5. Warranties
6. Product Submittals

Redline(s): The leads and superintendents will oversee submitting changes to SoW. Redlines shall be completed and submitted to engineering be Field Engineers. Engineering will create internal calendar to keep track of what needs to be done, and when it needs to finalized.

• Build-out will be the most redlining, given measurements, equipment placements, and grounding/bonding. Field Engineers will check and verify that all infrastructure is installed to design/spec, and if there is any changes, they will finalize redlines for closeout.
• Fiber: The use of an internal tracker will be the key to most of the redlines for ISP. The design given by IES customers will updated to reflect most of the past changes. Field Engineers will check and verify all of the Fiber scope.
• Copper: The internal tracker for copper should provide all the information needed for close-out. The Field Engineer may be the POC to ensure everything is installed to print, and if there is any changes, will redline and submit for review. The Field Engineer will check and verify these before close-out.
• Network: If needed, and confirmed that implementing redlines for Network is needed, the Field Engineer will work with the team to configure the details. If we are to redline these, the Field Engineer will take on most of those responsibilities.
• RFI referencing/implementation: The Field Engineer will be referencing the RFIs on the redlines as a final task before sending for QA review.

Test Audit(s): Everything to do with Audits will be ran and verified by the Field Engineer after the projects are complete. Included in this responsibility is verifying the cable schedule and building the projects in a fashion that is easy for the team, once the audit process begins. 100% verification that the testing projects match the prints. All testing projects should be created and available to the team as soon as the areas are ready. Once the team starts testing, the Field Engineer will start running audits as soon as each post is done. If there are any re-test, he/she will send those out to the team with an expected completion date. Then the Field Engineer will finalize audits once retest are completed. This will all be based upon the schedule in which we will have actualized dates to reference and plan out the project creation phase, and the close-out audit phase. Once each area is completely audited and 100% the Field Engineer will start conforming the testing audit package.

Lessons Learned: Between all engineers and QA this document should be actively updated throughout the actual build. At the end of each project the teams will get together and finalize/review the standardized lessons learned template for submitting. The information used for this document will be coming off of the lessons learned tracker. The installation teams should be actively filling those out throughout the build.

Warranties: These will be done by the Field Engineer. This happens towards the end of the build, in which the Field Engineer will gather all the information to send for processing/completion. A designated team member will send the required documents to receive the required warranties.

Product Submittals: The Field Engineer will complete product submittals. This submittal is the very first one to complete once the RFP is issued. The template is usually copy/paste, with a few additions/subtractions. Verifying the BOM with the POs, as well as obtaining product sheets is required for this submittal.

Labels: The Field Engineer will help print off labels for the installation teams. Ideally, having all the labels printed before installation will help in not wasting time throughout the build. We have bins that are organized per area, and a sign out sheet for the leads. We require an email sent to the engineering teams with any reprints needed, and the reason for the reprint.

RFI’s: A the Field Engineer can, or may, be the main engineer to oversee all RFIs before submission. The Field Engineer will conform and submit, as a collaborative effort for. One important thing to note, when an RFI is issues and there is design related feedback, that will automatically be entered as a lessons learned by the engineering team. Any RFI acceptance/rejections will be formally sent out to the applicable teams, by the Field Engineer.

Design (Shop Drawings): The Field Engineer can, or may oversee all work concerning design. This will include verifying and brainstorming areas of interest (where quality has lacked), reviewing and submitting into BIM360, as well as keeping up with revisions, hyperlinks, etc. Areas of focus:

1. Infrastructure (Grounding/Bonding)
2. Copper
3. Fiber
4. Detail sheet(s)