Traffic Control Plans and SFMTA Special Traffic Permits

Traffic Control Plans and SFMTA Special Traffic Permits

Our services of Network Route Design and Municipal Fiber Planning require the access of underground structures in the city of San Francisco and the Bay Area. These structures are located on busy roads where pedestrian, vehicular and public transportation has the potential to be impacted. Because of this, Traffic Control Planning is a critical step in Network Route Design to allow for access to these structures while mitigating potential impacts to the public and while minimizing workers’ exposure to traffic.


Rapid Systems Engineering (RSE) provides Traffic Control Plans (TCP’s) for San Francisco Municipal Transit Authority, as well as many Bay Area Municipalities. RSE TCP’s produce high detailed plans that modify vehicular, bicycle and/or pedeTCP-3strian traffic safely around construction areas, work-zones, and bike and pedestrian paths. We adhere to 2014 California Manual on Uniform Traffic Control Devices (MUTCD) and the SFMTA “Blue Book”. RSE will submit TCP’s to the SFMTA, as part of a Special Traffic Permit Application, or other permitting applications based on client’s needs.

TCP’s are created using RapidPlan, traffic control planning software which enables roadway and construction areas to be created quickly using CAD, GIS, or Integrated mapping that produce detailed TCPs. The TCPs display all elements for the construction and traffic scenario with details needed for controlling traffic such as traffic cones, construction signs, roadway workers, etc. Along with the plan, a succinct summary of the project indicates what the TCP is going to accomplish. This allows for quick jurisdictional approval.

This slideshow requires JavaScript.

Traffic Control Plans and SFMTA Special Traffic Permits

Mobile Application for DAS Networks Data Collection – Client Success Stories: Phase 3 Communications


Phase 3 Communications (P3 Comm) are specialists in design and installation of Fiber Optic Networking. In our increasingly competitive and mobile driven business world, Distributed Antenna Systems (DAS) networks have seen accelerated deployment in San Francisco and the Bay Area by all major carriers: AT&T, Verizon, T-Mobile.

In the race to get DAS nodes online,
proper documentation must be collected at every step in the process, which can be especially challenging in the construction phase.

P3 Comm Challenges

Carrier Node Construction Requires quick and efficient construction, data collection, and documentation. P3 Comm used employee mobile devices and a server for storage of photos of node construction.  Nicolas DeZubiria, the President of Phase 3 Communications, sought a solution for more efficiently collecting the data in the field, delivering information to the office team, and finally to the customer.

Rapid Developed Solutions

Rapid Systems Engineering (RSE) met with field personnel to gather insights on current processes while simultaneously working with office personnel to develop an agile system and process to meet the needs of Phase 3 Communications customer node construction requirements.

RSE developed and deployed a mobile iOS and web application into the field that was tested simultaneously by us and key P3 Comm personnel.  The solution allowed for real-time data capture and upload of all test data and photos.  An automated process was developed server side to collate the data and combine into formatted finished reports based on Carrier requirements.

This solution allowed P3 Comm to deliver Close-Out Documentation to carriers, allowing for critical information to get their assets online. It was also a key requirement that P3 Comm maintain the ability to be adaptive to the changing requirements of Carriers and node construction.  Phase 3 Communications is on the forefront of network expansion for all carriers and future applications like 5G, cell site densification and IoT applications, such as the Revolution11 first place AT&T Hackathon mobile application.

Have Questions?

Rapid Systems Engineering 1.707.515.0807 •

Phase 3 Communications 1.408.946.9011 •

Download a PDF of this blog: RSE_P3_ClientStory

Mobile Application for DAS Networks Data Collection – Client Success Stories: Phase 3 Communications

Utilizing Twilio and ThingSpeak API in IoT Applications

For this project, we needed a device that detected motion and sent a text message notifying us of the motion via. With the increasing integration of web services and APIs, solutions like this can be further automated from the integration of embedded sensors and connected devices.

We integrated Twilio and ThingSpeak API’s with a Wi-Fi enabled microcontroller and a Passive Infrared Sensor to detect motion and notified us via text message, with the help of Using Revolution11’s Twilio Blog Post, a solution that allows their clients to send small audio/video files and text message via Twilio. They used an HTTPS request and the Insert From URL script step in FileMaker.  For this project, we needed a device that detected motion and sent a text message notifying us of the motion.


Twilio is a cloud communications platform that can send and receive global SMS, MMS, and IP messages from any app, with a simple and powerful API.


ThingSpeak is an open data platform and API for the Internet of Things (IoT) that enables you to collect, store, analyze, visualize, and act on data from sensors or actuators, such as Arduino, NodeMCU, Raspberry Pi, and other hardware. For example, with ThingSpeak you can create sensor-logging applications, location-tracking applications, and a social network of things with status updates, so you could have your home thermostat control itself based on your current location.

Hardware Summary

  • NodeMCU ESP-12E. The NodeMCU is an open source IoT platform that uses Lua scripting language as well as the Arduino
  • PIR Motion Sensor: Pyroelectric (“Passive”) Infrared Sensor

Software Summary

For this project, we wrote a sketch, the name the program’s code is written to and uploaded onto Arduino boards. The Arduino Sketch was uploaded onto the NodeMCU which uses Twilio and Thingspeak APIs to send notifications by text message when motion was detected.


  1. Register for a Twilio account ( and get your API Credentials. These will include an [AccountSID] and [AuthToken]
  2. Register for a free ThingSpeak ( We will set create HTTP request with the ThingHTTP app. The ThingHTTP app is meant to simplify device communication with web services and APIs and embedded sensors.
  3. Set up ThingSpeak ThingHTTP Request:


  • Sign into ThingSpeak
  • Click Apps
  • Select ThingHTTP
  • Click Create New Request
  • Enter a Name for your new request: Twilio Test
  • Enter the Twilio Rest API URL:                                           {AccountSid}/Messages,json
  • Enter your AccountSid under HTTP Auth Username
  • Enter your Auth Token under HTTP Auth Password
  • Select POST method
  • Enter Content Type: application/x-www-form-urlencoded
  • Under Body enter the required parameters of From, To, and Url:                                         To=+{phonenumber}&From=+{TwilioVerified_Number}&Body={Message}
  • Click Save ThingHTTP and you’ll be given an API Key used in the HTTP request

You can now send your ThingHTTP request and view the response using the following URL:


The PIR_Twilio (download the Sketch)

The Hardware:


When a motion is detected!



1.707.515.0807 •

Download a PDF of this blog: Utilizing Twilio and ThingSpeak API in IoT Applications

Utilizing Twilio and ThingSpeak API in IoT Applications