myLPFM v3 - Development Roadmap
Revised 04/11/2023
myLPFM v3.3 is the current release.
Second Adjacent Channel Details
On channel searches with short-spaced second-adjacent channel stations, at the channel level, provide a link to a report that shows the information on second-adjacent channel short-spaced stations, the arriving contour of the short-spaced station, the size of the overlap zone, a Google satellite map showing the radius of the overlap zone over the proposed site and if a height above ground is specified, the potential antennas that can be used to meet the waiver request. Availability: clients only. Priority: high.
Notifications
Add a system that can handle notifications for various events that take place such as application status, reminder of expirations of construction permits and renewals, other events, DIRS activations, etc. For clients, it can provide notifications of new potential encorachments. Availability: all users for most functions. Priority: high.
E-mail Notifications
Add the ability for users to receive emails whenever myLPFM issues a notification on an opt-in basis. Availability: TBD. Priority: high.
Wireless Emergency Alerts (WEA)
Extend the scope of REC's current interface to IPAWS to also include WEA. Since WEA can be geogargeted to much smaller areas than just counties, some emergencies that are sent via WEA never make it to EAS. Build functionality in myLPFM that will allow LPFM stations to specify a monitoring radius around the station (default 5 miles), if a WEA is issued within the monitoring radius, it will be displayed in myLPFM. Also, in coordination with E-mail notifications (see previous project), the system can generate an email to the station in the event a WEA is issued. Stations are not obligated to rebroadcast WEAs but they can be used for newsgathering purposes. Priority: High.
Integration of VPIF into myLPFM
Both the Voluntary Public Inspection File (VPIF) system and myLPFM operate on the same software platform and use shared resources such as the user data. In our effort to make myLPFM more than just a channel search tool, but instead a fully integrated station management tool (which was the original intention of myLPFM), this major development will integrate VPIF into myLPFM where station users would be able to use myLPFM to upload documents and change other information that appears in the public file. The view for the public file would remain at LPFM.ws, but the station's ability to manage their presentation will be through my LPFM. Availability: all users. Priority: medium.
Long move showing.
For proposed moves of over 11.2 km, a map showing the contour of the current LPFM station and the proposed move to assure that contours overlap pursuant to §73.870(a). Availability: clients only. Priority: medium.
Wide Area Availability Map
Map that shows the availability of LPFM channels at various points within 20 miles of the LPFM station. Availability: clients only. Priority: medium.
Self Inspection Checklist
Add the ability for LPFM stations to follow a flow for the Self Inspection Checklist through myLPFM. The REC Self Inspection Checklist is a revised version of the FCC publication which was released in around 2008 and reflects the current rules. The presentation would include "yes/no" questions on various topics and myLPFM will log those entries. This is not an FCC requirement, but it is a good idea for all stations to periodically perform the self-inspection checklist to assure compliance. Availability: all users. Priority: medium.
Proactive Encroachment Checking
Add a new scheduled task where once per week, myLPFM will check for application activity by other stations and warn of potential encroachments that could impact the LPFM operation. Availability: clients only. Priority: medium. Dependent on implementation of notifications and email notifications.
Validation of user through CORES
This is a proposed sign up policy for LPFM stations that do not want to disclose their FRN credentials to REC. Under this concept, users will be able to apply for access to myLPFM and to validate that it is a legitimate request from the LPFM station, they can log into their CORES account and grant REC the ability to maintain their FRN. We would check to see if the station was added and once verfiied, we will grant access and then you are free to remove the maintenance functionality in CORES. Priority: low.
Online Account Upgrades
Allows a user that does not have client access to obtain client access through making a payment to top off their REC spend at the minimum $350 in order to receive client level access to myLPFM features. Availability: non-clients only. Priority: low.
Authorized Agent Program
Permits the ability for an individual using their own login to be able to maintain myLPFM/VPIF on multiple LPFM stations. The Authorized Agent will be able to sign up for an individual account, once approved, they will appear on a list of authorized agents. Using the LPFM station's password, the LPFM station would then log into myLPFM and designate the individual user as an Authorized Agent for that station. When the Authroized Agent logs in on their own password, they will be presented with a list of stations that they have been authorized for and then can access each station individually. Authorized agents can be consultants, contract engineers, attorneys, advocates as well as government and tribal employees who are associated with LPFM licensees that are authorized to have more than one station. Priority: low.
Partial County Alerting
The National Weather Service is getting ready to deploy Partial County Alerting (PCA), which allows EAS to narrow down alerts to a certian portion of the county This is done by using the first digit of the SAME/FIPS code (which is normally a 0) to indicate the portion of the county. This is a modification that will need to be done through the entire universe of REC EAS applications, which includes myLPFM. Availability: Consistent with existing alerting functions. Priority: high.
"Station Visibility" Page
Create a new Station Visibility option off the menu to replace the existing Directory Listing and RadioDNS options. The new Station Visibility option will provide links to the Directory Listing, Update Station Logo and RadioDNS functionality. It would also provide information on other methods available to stations, outside of the myLPFM platform in order to help improve their station's visibility and accessibility, such as Amazon Alexa onboarding. Priority: medium.
Expand social media in directory listings
To keep up with the evolving climate in social media, expand the coverage in both myLPFM and LPFM.us to allow stations to have their links to their social media presence on TikTok, Instagram and Mastodon added. In this same change, we would also expand the accessibility options to also include the station's Roku channel. Priority: medium.
Changes implemented in v3.1
RadioDNS Support
RadioDNS allows compatible receivers to be able to tune in to a broadcast station's live stream once they leave the listening area. RadioDNS also permits stations to have logos and basic station metadata such as station name, description and website links display on compatible consumer receivers.
In order for a station to use RadioDNS, they must have RDS. Stations with HD Radio can also take advantage of RadioDNS. Several car brands are starting to implement RadioDNS. The role myLPFM can play is a place where station logos can be uploaded and served as well as the serving the XML files and appropriate DNS entries necessary to activate the service. For all myLPFM users, stations may set their basic metadata, upload logos and register with RadioDNS. Client users will also be able to specify their station's internet stream to support service following functions.
Channel Report
On channel searches, at the channel level, provide a link to a channel report which shows all co-channel, first-adjacent, second-adjacent and third-adjacent as well as intermediate frequency and Channel 6 TV facilities within specific distances along with the distance and bearing to the other facility, the §73.807 recommended distance for non-interference, the §73.807 or §73.825 required distances and the amount of clearance. Availability: clients only. - Implemented in v3.1.
Advanced geometry functions
Functions to better handle geometry within myLPFM and the rest of the REC Universe. For myLPFM, this will allow us to better determine contour overlap by taking the entire contour into consideration instead of just point to point as the current system works. This will allow for some improvements in the Encroachment Report as well as allow us to better implement some of the planned features on this roadmap. Priority: high. - Implemented in v3.1.
HD Radio evaluation
Checks an LPFM site to determine which level of HD Radio the station can have and what the digital ERP will be. Availability: clients only. Priority: medium. - Implemented in v3.1.
Long move availability.
For proposed moves of over 11.2 km, indication of whether a move would have contour overlap pursuant to §73.870(a). This would not include a map. Availability: all users. Priority: medium. - Implemented in v3.1.
RDS PI Code ifnormation
On the Station Information screen, myLPFM will show the station's Program Identification (PI) code that is to be used with a Radio Data Service (RDS) encoder. Implemented in v3.1.
Changes implemented in v3.2
CAP/IPAWS Interface
REC Networks does have a Memorandum of Understanding with FEMA for access to CAP/IPAWS. We are adding this item to the roadmap in order to build the interface to CAP/IPAWS to support the Emergency Alert System (EAS). We see potential applications using the proposed notification functionality to inform stations of recent RWTs and RMTs (to remind station to check their logs) as well as providing live alert information, such as AMBER alerts to the notifications functionality. - Status: first phase to be implemented in v3.1 with EAS/weather alerts while logged in and client features such as public web pages with alert information, Javascripts to embed alerts on station website and an API for custom station website scripts. - Set for v3.2 release.
Non-adjacent Channel Changes
On channel searches, check the interfering contours impacting the current LPFM and the channel (and location) of the proposed change to determine if there is a reduction in interference under §73.870(a). Availability: clients only. Priority: high - Set for v3.2 release.
