HomeMy WebLinkAboutRE_ Video Detection Camera Revisions COR _BT105_ (2)Compliance letter is attached. Thanks!
Flora Lee, PE, PTOE
Principal Civil Engineer – Operations Signal Engineer/ Project Manager
Public Works Department ¦ Transportation
FLee@Rentonwa.gov <mailto:FLee@Rentonwa.gov>
From: Flora Lee
Sent: Friday, March 13, 2026 9:24 AM
To: Michael Sippo <MSippo@Rentonwa.gov>
Cc: Altchech, Joey <joey.altchech@soundtransit.org>
Subject: RE: Video Detection Camera Revisions COR [BT105]
I can check with the vendor and get back to you shortly.
My apology. The attached was an older model that was replaced with a new model.
Attached is the current model. The camera is the unchanged and the nexus unit has integrated the outside components into the unit.
9 29.18(3) Video Detection System
Section 9-29.18(3) is a new section:
(*****)
Video detection system shall be approved by Transportation ITS and Maintenance Manager, Eric Cutshall, per City’s standardized options. Video detection system shall be site-specific
and completely operable with the City of Renton’s signal systems and maintainable by City of Renton’s Transportation maintenance. [The designer shall confirm the video detection system
during design with Transportation ITS and Maintenance Manager or Transportation Operations (contact Flora Lee, flee@rentonwa.gov <mailto:flee@rentonwa.gov> for updates or questions)].
Video detection system with camera and radar sensor for advanced detection over 600-ft shall be required for intersections with adaptive signal control, posted speeds of 35 mph or above,
or intersections on arterials or network corridors and approved by Transportation Operations.
NOTRAFFIC SPECIFICATIONS:
AI Mobility Platform
This specification defines the minimum requirements for a system that detects, classifies, and tracks traffic at signalized intersections using fusion sensors with video and radar to
power a variety of trajectory-based applications including object detection, counts, adaptive, signal performance measures, and safety analytics. The system includes a cloud portal
for centralized monitoring & management, as well as 24/7 live monitoring & support.
1 Hardware
The system shall comprise three primary hardware components: fusion sensors, cabinet interface units, and sensor power units.
All hardware and material shall be new. All fasteners exposed to the elements shall be Type 304 or Type 316 passivated stainless steel. Primary hardware components shall have permanent
labels that bear the name of the manufacturer, description, part number, date of manufacture, and serial number.
Primary hardware components shall comply with the environmental and operating requirements of NEMA TS 2 Section 2.1.5 (Temperature & Humidity), Section 2.1.6 (Transients, Power Service),
Section 2.1.8 (Nondestructive Transient Immunity), Section 2.1.9 (Vibration), and Section 2.1.10 (Shock) and shall have been tested by an independent third-party laboratory using the
procedures defined in Section 2.2.7 (Transients, Temperature, Voltage, and Humidity), Section 2.2.8 (Vibration), and Section 2.2.9 (Shock/Impact).
To ensure the safety and integrity of hardware in transit, primary hardware components shall be shipped in ISTA 2 certified packaging.
1.1 Fusion Sensors
Fusion sensors will be installed on traffic signal infrastructure (including mast arms, strain poles, and posts) in locations that provide an unobstructed view of approaching traffic.
They shall comprise a video sensor and a radar sensor housed in a single weathertight, environmentally hardened enclosure with an integral 4 in metal saddle bracket for compatibility
with industry-standard traffic signal mounting hardware. They shall operate over a nominal input voltage range of 89 to 264 VAC at 50 or 60 Hz.
There shall be two types of fusion sensor. Fusion Sensor Type 1 shall incorporate a 1080p HD video camera, 60 GHz radar, Nvidia processor, Ethernet receptacle rated to IEC 6100-4-5 (surge
protection), and Wi-Fi radio. Fusion Sensor Type 2 shall be functionally equivalent to Fusion Sensor Type 1 and shall also incorporate a C-V2X module and two external omnidirectional
V2X antennas. Fusion Sensor Type 2 shall comply with FCC regulations for C-V2X roadside units (RSUs). Fusion sensors that employ radar frequencies such as 24 GHz that are susceptible
to interference with 5G communications are not compliant with this specification.
Fusion sensor enclosures shall be certified to IP67 and MIL-STD-810 salt fog. They shall have a removable weathertight cover that provides access to a three-position terminal block for
power conductors and an Ethernet receptacle for communications cable. The cover shall have two weathertight cable glands for power and communications cables.
1.2 Cabinet Interface Units
Cabinet interface units (CIUs) shall comprise a ruggedized computing device housed in a field hardened enclosure that can be rack mounted in 1U of vertical space or shelf mounted in
horizontal or vertical orientations.
CIUs shall incorporate an Nvidia processor, firewall/router with 8 Ethernet receptacles rated to IEC 61000-4-5 (surge protection), Wi-Fi radio, cellular modem, accessory ports, and a
front panel menu-driven user interface with a backlit display and navigation buttons. The accessory ports shall support a variety of accessories that facilitate interoperation and integration
with transportation field cabinets, including synchronous serial communications ports for NEMA TS 2, ITS, and ATC 5301 cabinets, as well as digital I/O for Model 33x and NEMA TS 1 cabinets.
CIUs shall include an external power supply. The DC power connector on the CIU shall be latching.
CIUs shall include Wi-Fi, GPS, and cellular antennas housed in a single (all-in-one), environmentally-mentally hardened, low-profile enclosure that mounts to the exterior of transportation
field cabinets with gaskets that form a weathertight seal.
1.3 Sensor Power Units
Sensor power units (SPUs) shall comprise components that switch, filter, and protect 120 VAC power for up to four fusion sensors, housed in a field hardened enclosure that can be rack
mounted in 1U of vertical space or shelf mounted in horizontal or vertical orientations.
2 Functionality
2.1 Fusion Sensors
Fusion sensors shall detect, classify, and track vehicles and vulnerable road users (VRUs) located between 40 ft and 720 ft from the sensor. Fusion sensors shall classify vehicles and
VRUs as cars, trucks, buses, motorcycles, bicycles, or pedestrians, and track their location and trajectory (direction and speed). To minimize sensor-to-cabinet communications, the
detection, classification, and tracking data shall be processed in the fusion sensor, not the CIU.
All detection, classification, and tracking for an approach shall be performed by one fusion sensor. Systems that require multiple sensors per approach, including but not limited to
systems that use different sensors for stop line and advance detection, systems that require different quantities of sensors for different intersection widths, and systems that use
different sensors for major streets and minor streets, are not compliant with this specification.
Fusion sensors shall fuse video and radar to provide synthesized detection, classification, and tracking data. Non-fused hybrid sensors that only provide separate detection, classification,
and tracking data for video and radar, or otherwise treat video and radar as independent, non-fused sensors, are not compliant with this specification.
2.2 Cabinet Interface Units
Cabinet interface units shall aggregate intersection-level communications, data, and processing. Communications between CIUs and fusion sensors shall occur over a VPN with AES-256 encryption
using Ethernet or Wi-Fi with WPA2-AES security. Communications between CIUs and transportation field cabinets shall use the NEMA TS 2 Port 1 and ITS/ATC 5301 Serial Bus 1 synchronous
serial bus protocols. CIUs shall be capable of logging all communications on the synchronous serial bus including frames transmitted by other secondary stations. They shall automatically
configure synchronous serial communications for either the TS 2 Port 1 protocol or the ITS/ATC 5301 Serial Bus 1 protocol and shall detect any other I/O interface units (BIUs or SIUs)
currently in use to prevent duplicate synchronous serial bus address assignments.
CIUs shall provide browser user interfaces to monitor, configure, and control the CIU, fusion sensors, and sensor power units. Access to CIU browser user interfaces shall be restricted
via username and password authentication.
CIUs shall provide high-definition RTSP video streams, one for each fusion sensor, as well as a quad view of four fusion sensors. Detection zones shall be displayed in video streams
with their actuation state represented by different colors. Signal state (channel state) shall be displayed in video streams using icons labeled with phase or overlap numbers.
2.3 Cloud Portal
The cloud portal shall provide centralized monitoring, configuration, and control of distributed systems, as well as centralized data storage and reporting. Communications between the
cloud portal and distributed systems shall occur over VPNs with AES-256 encryption. The cloud portal shall be hosted on AWS in the US or Canada using a discrete tenant for each infrastructure
owner/operator (IOO), thereby ensuring complete isolation of the IOO’s data from that of any other IOO. Cloud portals employing multi-tenant architecture are not compliant with this
specification.
The cloud portal shall provide a browser user interface. Access to the browser user interface shall be restricted via username and password authentication.
2.4 Object Detection
The system shall detect traffic (vehicles and VRUs) in user-defined zones located in approach lanes, departure lanes, and crosswalks. Detection zones shall support presence and pulse
modes, extension, and delay.
The system shall report the occupancy of detection zones via detector outputs. When a detection zone is occupied, it shall be considered actuated and its detector outputs shall be ON;
otherwise, its detector outputs shall be OFF. The system shall support user-defined zone-to-output mappings, including zones mapped to multiple outputs and multiple zones mapped to
the same output.
The system shall support user-defined mappings between detector outputs and inputs of NEMA TS 1, NEMA TS 2, Model 33x, ITS, and ATC 5301 transportation field cabinets. Transportation
field cabinet inputs will be mapped in actuated signal controllers to detectors, custom logic, and other input functions.
Detection accuracy shall be at least 98% under typical environmental conditions, defined as time with no false actuations (zone actuated but not occupied) or missed actuations (zone
occupied but not actuated) versus total time, expressed as a percentage. Detection accuracy shall have been evaluated at a minimum of six traffic control signals on roads open to public
travel, where each traffic control signal is owned and operated by a different IOO. Traffic control signals on roads not open to public travel including but not limited to those at
test beds/tracks, research laboratories, and signal maintenance facilities do not satisfy this requirement. Upon request, the Manufacturer shall provide engineering reports for the
detection accuracy evaluations that include methodologies and results. The reports shall be attested by a licensed Professional Engineer employed by the Manufacturer.
Upon any anomaly or malfunction that affects its ability to report the occupancy of detection zones, the system shall actuate the affected detection zones by turning their detector outputs
ON and report them as failed via the NEMA TS 2 and ITS/ATC synchronous serial bus protocols by turning their status outputs OFF.
2.4.1 Dilemna Zone Detection
The system shall detect vehicles in the dilemma zone (“Dilemma Zone Detection”). Di-lemma Zone Detection shall be implemented via Dilemma Detection Zones, where a Di-lemma Detection
Zone has a user-defined distance upstream of the stop line, speed range, and extension time. Each Dilemma Detection Zone shall be capable of being associated with one or more inputs
in the transportation field cabinet.
When a vehicle enters a Dilemma Detection Zone and the speed of the vehicle is within the range of speeds for the Dilemma Detection Zone, the system shall actuate the inputs associated
with the Dilemma Detection Zone for the associated extension time. By associating the inputs with extension detectors in actuated signal controllers, phases can be extended until vehicles
are clear of the dilemma zone.
2.4.2 Pedestrian Detection
The system shall detect pedestrians in crosswalks using Ped Protection Zones. The outputs of Ped Protection Zones will be mapped to inputs in actuated signal controllers to extend phases
and intervals to prevent the release of conflicting vehicle traffic, and to implement custom logic for other responses.
2.5 V2X
The system shall support connected vehicle applications and connected intersection operation per relevant industry standards and guidelines including CTI 4001, CTI 4501, J2735, J2745,
NTCIP 1202, and NTCIP 1218. It shall be capable of generating SDSMs for non-connected road users per SAE J3224-1.
2.6 Traffic Counts
The system shall count vehicles and VRUs traversing the intersection using trajectories rather than detection zone actuations. Systems that require setup or configuration of detection
zones specifically for counts are not compliant with this specification.
The system shall provide textual and graphical user interfaces in the cloud portal to view counts for two user-specified periods (for side-by-side comparisons); filter them by maneuver
(left, through, right, U-turn, ped x-ing), class, phase, and approach; and export them to CSV in 15 minute, 1 hour, and 24 hour bins.
The system shall automatically export counts to the MS2 Traffic Count Database System (TCDS) and provide a user interface in the cloud portal to view and edit MS2 TCDS API con-figuration
data including logon credentials and signal IDs.
2.7 Signal Performance Measures
The system shall collect signal performance measures (SPMs) including:
• Average vehicle delay
• Maximum vehicle delay
• Pedestrian delay
• Level of service
• Arrivals on green/red
• Purdue phase termination
• Split monitor
• Peak hour, peak hour factor, design hour factor, and directional factor
The system shall acquire SPM data from trajectories rather than detection zone actuations. Systems that require setup or configuration of detection zones specifically for SPMs and those
that derive SPMs from high-resolution data logs of actuations are not compliant with this specification.
The system shall provide textual and graphical user interfaces in the cloud portal to view SPMs for two user-specified periods (for side-by-side comparisons); filter them by class; and
export them to CSV and PDF.
2.8 Incident Detection
The system shall detect incidents that disrupt the normal flow of traffic, including but not limited to crashes, road work, and disabled vehicles. It shall provide user interfaces in
the cloud portal to view time-stamped incident logs and shall deliver incident notifications via email, text, and phone.
2.9 Video Clip Management
The system shall store 30 days of video in the fusion sensors. It shall provide user interfaces in the cloud portal to upload clips from user-specified fusion sensors for user-defined
dates and times, play uploaded clips, export uploaded clips from the cloud portal to user devices, and delete uploaded clips from the cloud portal.
2.10 Near-Miss Analytics
The system shall detect near-miss events. It shall provide textual and graphical user inter-faces in the cloud portal to view near-miss events for user-specified periods and intersections,
including a heat map of events showing their severity and location superimposed on an overhead view of the intersection. For each near-miss event, the system shall provide post encroachment
time (PET), time to collision (TTC), classes, trajectories, and a video clip.
2.11 Optimization
The system shall provide real-time, trajectory-based, distributed adaptive signal control (“Optimization”). Optimization shall be compatible for all makes and models of actuated signal
controllers and transportation field cabinets. Optimization shall use data from object detection rather than detection zone actuations so as not to require setup or configuration of
detection zones specifically for Optimization.
Optimization shall support a variety of intersection-level and corridor-level strategies including balanced delay reduction, progression, crossing arterial coordination, queue management
during oversaturation, transit prioritization, pedestrian prioritization, maximal throughput, queue management on freeway off ramps, progression of non-through movements, preemption
recovery, and tightly spaced intersection management. Multiple strategies shall be capable of being in effect simultaneously. Cycle lengths shall be optimized and implemented on a per-Intersection
basis so as not to require a common cycle length along the corridor.
The system shall provide textual and graphical user interfaces in the cloud portal to monitor, configure, and control Optimization.
2.12 Red Light Running Analytics
The system shall identify vehicles entering intersections on yellow and red. It shall provide textual and graphical user interfaces in the cloud portal to view yellow and red light running
events for user-specified periods and intersections. For each yellow and red light running event, the system shall provide class, maneuver, lane, approach, signal interval (yellow change,
red clearance, or full red), distance from stop line at yellow, speed, time after yellow, and a video clip.
2.13 Remote Controller Access
The system shall proxy the browser user interfaces of actuated signal controllers connected to CIUs and display them in the cloud portal. The proxied browser user interfaces shall support
all functionality of the native browser user interfaces including but not limited to con-troller status monitoring, timing parameter editing, configuration import/export, and front
panel emulation.
3 Service & Support
3.1 Cloud Portal Access
The system shall include at least ten years of access to the cloud portal for an unlimited number of users.
3.2 Cellular Connectivity
The system shall include at least ten years of cellular data. The system will use this cellular connection to exchange data between the field and the cloud portal.
3.3 Live Monitoring
The system shall include at least ten years of 24/7/365 live monitoring for abnormalities, anomalies, performance, reliability, faults, incidents, alarms, and severe weather events.
Monitoring shall be performed by personnel employed by the Manufacturer using an operations center in North America owned and operated by the Manufacturer. Monitoring performed by on-call
personnel or those otherwise not solely dedicated to monitoring is not compliant with this specification.
3.4 Software Updates
The system shall include at least ten years of over-the-air software updates for the cloud portal and primary hardware components.
3.5 Warranty
The Manufacturer shall warrant the system for at least ten years. The warranty shall start when the equipment is received by the IOO and shall cover material and workmanship defects.
During the warranty period, the Manufacturer or their designated representative shall repair or replace defective equipment at no cost to the IOO. The Manufacturer or their designated
representative shall maintain an adequate inventory of equipment to support warranty claims.
3.6 Installation Support
The Manufacturer or their designated representative shall provide on-site turn-on assistance, Monday through Friday, with a minimum one-week advance notice.
3.7 Technical Support
The Manufacturer shall provide 24/7/365 technical support via email and telephone for ten years or the term specified by the contract documents.
3.8 Documentation
The Manufacturer shall provide electronic manuals in PDF or HTML formats that include installation, configuration, operation, troubleshooting, and maintenance information.
3.9 Training
The Manufacturer shall provide a maximum of two virtual training sessions of a maximum of three hours per session. The sessions shall include installation, configuration, operation,
troubleshooting, and maintenance information. Instructors shall be certified by the Manufacturer.
4 Manufacturer Certifications
The Manufacturer shall maintain SOC 2 Type II and ISO 27001 (Information Security Management) certifications.
5 Measurement and Payment
The system shall be measured on a per-intersection basis in units of each and paid at the contract unit price per each. The price shall include furnishing, installing, integrating, and
testing the following equipment:
• 3 ea. Fusion Sensor Type 1
• 1 ea. Fusion Sensor Type 2
• 1 ea. Cabinet Interface Unit
• 1 ea. Sensor Power Unit
Thank you.
Flora Lee, PE, PTOE
Principal Civil Engineer – Operations Signal Engineer/ Project Manager
Public Works Department ¦ Transportation
FLee@Rentonwa.gov <mailto:FLee@Rentonwa.gov>
From: Michael Sippo <MSippo@Rentonwa.gov <mailto:MSippo@Rentonwa.gov> >
Sent: Friday, March 13, 2026 6:27 AM
To: Flora Lee <FLee@Rentonwa.gov <mailto:FLee@Rentonwa.gov> >
Cc: Altchech, Joey <joey.altchech@soundtransit.org <mailto:joey.altchech@soundtransit.org> >
Subject: FW: Video Detection Camera Revisions COR [BT105]
Flora,
Do you know if either systems are BuyAmerica compliant? I don’t think it ultimately matters because they are a sole source item but will probably require additional paperwork on their
end.
Thanks!
MICHAEL S. SIPPO, Civil Engineer III
City of Renton // Development Engineering
Virtual Permit Center <https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rentonwa.gov%2Fcity_hall%2Fcommunity_and_economic_development%2Fpermit_services&data=05%7C02%7CMSippo%40Re
ntonwa.gov%7Cf647ea314b7945aac36908de81221ffa%7C71014141061148858e98cc96a05e1675%7C0%7C0%7C639090180765228282%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOI
joiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=KErj052fPjBoFEwcQbTgbVnuoA1HOoUQmSrTtbBjij8%3D&reserved=0> // Online Applications and Inspections <https://gcc02.safelinks.protection.outlook.com/?url=
https%3A%2F%2Fpermitting.rentonwa.gov%2F%23%2Fhome&data=05%7C02%7CMSippo%40Rentonwa.gov%7Cf647ea314b7945aac36908de81221ffa%7C71014141061148858e98cc96a05e1675%7C0%7C0%7C639090180765255269%7CUnknown%7C
TWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=K3OW%2B31rFhaQjTt32G20mR%2FYYhQ4EQNoHHs2KdUoPkY%3D&reserved=0>
office 425-430-7298
NOTICE OF PUBLIC DISCLOSURE: This message complies with Washington State’s Public Records Act – RCW 42.56
From: Altchech, Joey <joey.altchech@soundtransit.org <mailto:joey.altchech@soundtransit.org> >
Sent: Wednesday, March 11, 2026 4:02 PM
To: Michael Sippo <MSippo@Rentonwa.gov <mailto:MSippo@Rentonwa.gov> >; Linde, Tom (Contractor) <c-Tom.Linde@soundtransit.org <mailto:c-Tom.Linde@soundtransit.org> >; Robin Tlehhema <Robin.Tlehhema@dk
sassociates.com <mailto:Robin.Tlehhema@dksassociates.com> >; Owen Wang <Owen.Wang@dksassociates.com <mailto:Owen.Wang@dksassociates.com> >; rjh@dksassociates.com <mailto:rjh@dksassociates.com>
Cc: RicardoPargas <ricardo.pargas@hdrinc.com <mailto:ricardo.pargas@hdrinc.com> >; Linde, Tom (Contractor) <c-Tom.Linde@soundtransit.org <mailto:c-Tom.Linde@soundtransit.org> >; Le,
Tri6 (Contractor) <c-tri.le6@soundtransit.org <mailto:c-tri.le6@soundtransit.org> >; BT105 Renton Transit Center <BT105@soundtransit.org <mailto:BT105@soundtransit.org> >; Frost, Greg
(Contractor) <c-Greg.Frost@soundtransit.org <mailto:c-Greg.Frost@soundtransit.org> >
Subject: RE: Video Detection Camera Revisions COR [BT105]
CAUTION: This email originated from outside the City of Renton. Do not click links, reply or open attachments unless you know the content is safe.
Thanks, Mike. Do you know if the “No Traffic” video detection camera system is compliant with BuyAmerica? And/or was the Iteris Apex system BuyAmerica compliant?
@Linde, Tom (Contractor) <mailto:c-Tom.Linde@soundtransit.org> – please make sure to capture this change on the change log.
Adding @Robin Tlehhema <mailto:robin.tlehhema@dksassociates.com> , @Owen Wang <mailto:owen.wang@dksassociates.com> and @Richard Hutchinson <mailto:rjh@dksassociates.com> for awareness
as this will likely make its way to you in the near future as the EOR(s).
Thanks!
Joey Altchech, PMP
Senior Project Manager
Capital Delivery Department
Stride Bus Rapid Transit Program
425-761-5554 (cell)
Joey.Altchech@soundtransit.org <https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2FJoey.Altchech%40soundtransit.org%2F&data=05%7C02%7CMSippo%40Rentonwa.gov%7Cf647ea314b7945aac36908de812
21ffa%7C71014141061148858e98cc96a05e1675%7C0%7C0%7C639090180765272689%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C
&sdata=xraGXeQ20zHUo13bhzQhOYp5Gt3jIimQXii0zALOHOo%3D&reserved=0>
From: Michael Sippo <MSippo@Rentonwa.gov <mailto:MSippo@Rentonwa.gov> >
Sent: Tuesday, March 10, 2026 11:29 AM
To: Altchech, Joey <joey.altchech@soundtransit.org <mailto:joey.altchech@soundtransit.org> >; Frost, Greg (Contractor) <c-Greg.Frost@soundtransit.org <mailto:c-Greg.Frost@soundtransit.org>
>; BT105 Renton Transit Center <BT105@soundtransit.org <mailto:BT105@soundtransit.org> >
Cc: RicardoPargas <ricardo.pargas@hdrinc.com <mailto:ricardo.pargas@hdrinc.com> >
Subject: Video Detection Camera Revisions COR
CAUTION: This email originated from a contact outside Sound Transit. Remember, do not click any links or open any attachments unless you recognize the sender and know the content is
safe. Report any suspicious email by clicking the “fish” button in Outlook. Thank you! ST Information Security
Good morning Joey,
I have been informed by our transportation department that effective immediately we are switching from the “Iteris Apex” to the “No Traffic” video detection camera system due to ongoing
failure issues that have not be resolved by the supplier. I’ve attached the spec sheets. Please have your engineering team review the contract, plans and specs to be aware of the
change and let me know if there are any updates that you would like to supply on your end to ensure that the correct product gets placed.
Just and FYI, A No Traffic video detection camera system is approx $35k vs Iteris Apex $45k per our transportation department.
Thanks,
MICHAEL S. SIPPO, Civil Engineer III
City of Renton // Development Engineering
Virtual Permit Center <https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rentonwa.gov%2Fcity_hall%2Fcommunity_and_economic_development%2Fpermit_services&data=05%7C02%7CMSippo%40Re
ntonwa.gov%7Cf647ea314b7945aac36908de81221ffa%7C71014141061148858e98cc96a05e1675%7C0%7C0%7C639090180765289107%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOI
joiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=juF2eg6AuQNikGoo1tlny3HviQXVpS1UYyeFlMDkFqQ%3D&reserved=0> // Online Applications and Inspections <https://gcc02.safelinks.protection.outlook.com/?url=
https%3A%2F%2Fpermitting.rentonwa.gov%2F%23%2Fhome&data=05%7C02%7CMSippo%40Rentonwa.gov%7Cf647ea314b7945aac36908de81221ffa%7C71014141061148858e98cc96a05e1675%7C0%7C0%7C639090180765304575%7CUnknown%7C
TWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=h4%2BjViucu1vXjM3kGiBt0q8%2F0cVjI3%2F9saijahRzTes%3D&reserved=0>
office 425-430-7298
NOTICE OF PUBLIC DISCLOSURE: This message complies with Washington State’s Public Records Act – RCW 42.56