
Raleigh's February 2012 council resolution declared the city's intent to build an open government by favoring open source systems in procurement and by launching an open data catalog of city data in open formats.
What the resolution does
This short resolution of the Raleigh City Council has two operative sections. The first tells the city's IT department to create an open systems procurement policy, so future requests for proposals favor solutions with open source licensing that store and expose public data through industry-standard, open protocols. The second commits the city to an open data website that would serve as a catalog of city data available in open formats.
The preamble lists the familiar goals of open, transparent and accessible government, along with economic development, investment and civic engagement.
Adoption context
Raleigh adopted the resolution early, at a time when only a small group of cities had passed an open data policy. Like Portland's 2009 resolution, it links open data to open source, arguing that peer-reviewed open source software can be high quality, secure and cheaper to integrate.
Key provisions
- An open systems procurement policy with RFP specifications that encourage open source licensing models.
- A requirement that systems expose public data through open, industry-standard protocols.
- A city open data website acting as a catalog of available datasets in open formats.
Which guidelines it reflects
The resolution reflects goals and values, open formats, open code and data portals and websites. Its procurement focus is an early version of an idea later policies developed further: building openness into systems when they are bought, not after.
What happened next
Raleigh went on to run a public open data portal, and the region kept working on the topic. Neighboring Durham adopted its own administrative open data policy in 2015.
Why this matters for your business data
Raleigh's procurement clause makes a point that applies to any organization: data is easiest to share, analyze or license when the systems that hold it can export clean, standard formats. If your software locks records inside proprietary exports, that friction lowers what the data is worth. See how to value your data, or get a bid to learn what buyers look for.
We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.
Frequently asked questions
Is Raleigh's 2012 action an ordinance?
No. It is a council resolution stating the council's intent and directing staff to take specific steps. Resolutions like this set policy direction but generally carry less formal weight than an ordinance codified in the city code.
What does open systems procurement mean?
It means writing technology purchasing requirements so that new systems favor open source licensing and expose their data through open standards. The goal is to avoid buying software that makes public data hard to extract or publish later.
Guidelines this policy reflects
Other policies in NC
Sources
Updated December 31, 2024.