Access routes and dated changes ↓
Connections already documented
Start with an existing network, then select an organization to inspect its contribution, access route and evidence. Each view shows the selected entity’s direct relationships captured in this draft.
Relationship evidence
Find capability across Colorado
Entities appear once under a primary function. Many contribute in several ways. Geography describes a location or service area, not a limit on eligibility.
Five ideas for discussion
Each combines existing capabilities around a concrete result. These ideas are unvalidated: participants, sponsors and delivery owners have not agreed to them.
Begin by testing the gap with the organizations already doing the work. Choose a pilot only when the problem, additional contribution, access and sponsor are clear.
A map that can earn trust
This version documents a starting set of entities and relationships from public sources. Partner validation and real service journeys are the next evidence layer.
Our inclusion standard
An entry needs a concrete Colorado role and primary evidence of creating, enabling or meaningfully adopting a new technology, product, process or service. It must identify a specific activity: research, product development, commercialization, a pilot or deployment, or a named facility, funding, policy or coordination program that directly supports that work.
Jobs, business size, ownership, affiliation, regional representation and general business support alone do not qualify. The same test applies across sectors and organization types. An evidence gap can justify withholding an entry; it does not establish that the organization never innovates.
What the evidence means
- Publicly documented: an official source describes the entity or relationship.
- Dated documentation: a historical announcement supports the relationship; present scope needs confirmation.
- Published referral route: a source identifies a possible coordination path, without proving an active project.
- Idea for discussion: a possible collaboration that requires validation. These ideas were developed with AI assistance and are separate from the documented relationship data.
A partner logo, grant announcement or shared address does not establish procurement, spare capacity or a working service pathway. Reported organizational impacts have not been audited here.
Keep the unit of analysis clear
Organizations, campuses, consortia and programs are separately identified. Parent links prevent treating a host and its program as independent institutions. The entity count is not a count of unique legal organizations.
Showcase participation establishes an eligibility route, not a completed investment. The NIST manufacturing-extension relationship belongs to national NIST; its Boulder presence is the research anchor in this map.
Coverage and blind spots
Coverage is selective. It includes Front Range research anchors and qualifying activities in rural Colorado. Regions with few entries are research priorities; geography alone does not qualify an entry. These are not complete regional networks.
Priority additions include further tribal-led innovation, agriculture and Extension coverage, additional universities, arts and outdoor industries, civic organizations, philanthropy, corporate R&D teams, procurement owners and later-stage finance. A regional intermediary does not represent a tribe’s authorization.
What must be learned directly
Actual available equipment hours, prices, eligibility, contracting time, IP/data terms, funding runway, decision authority, customer needs and completed outcomes.
Use a small sample of real company and community journeys to distinguish missing services from poor navigation, insufficient capacity, funding constraints and useful specialization.
Maintain one evidence base
- Keep stable entity, relationship, opportunity and source IDs.
- Ask a named partner to validate only its own records.
- Update the claim and source date together; retain corrections in a change log.
- Recheck active opportunities monthly and stable profiles quarterly as a proposed cadence.
- Retire stale relationships from current views without deleting their historical evidence.
CII checks public sources daily for additions and corrections that meet this inclusion standard. Entries withheld during review require new qualifying evidence before they can return. Updates retain each record’s source and check date. Partner validation and a wider reporting cadence remain separate proposals.
Build on existing inventories
Use CO-LABS for research discovery, Elevate Quantum and CUbit for quantum, Startup Colorado for rural entrepreneurship, SBDC for advising locations, and EDCC/EDCs for regional entry points. Engage Colorado adds a technology-company and investor directory.
The CU 2016–2017 ecosystem graphic is a historical design reference only. This map does not carry its entries forward as current organizations.
Download complete map data Entity register Relationship register
Sources and dates
Source check dates are shown individually. The October 10 inclusion review assesses the documented role; it does not reset earlier source-check dates or confirm current capacity. “Undated” means no publication date was established. A live page may describe older work.