Cal. Code Regs. tit. 10 § 8310

Current through Register 2024 Notice Reg. No. 45, November 8, 2024
Section 8310 - Application Process for iHub Designation
(a) At its sole discretion, GO-Biz will release a request for proposal for the iHub Program on its website when there is availability to add a new iHub because of a termination of an IHub, an expiration of an iHub or the availability of a region.
(b) The request for proposal shall include a schedule of the following:
(1) The application period;
(2) Designated conference calls for potential applicants;
(3) Deadline to submit a letter of intent;
(4) Deadline for the final proposal;
(5) Timing of the evaluation by the Review Committee;
(6) Date of notification of iHub finalists;
(7) Site visits and interview dates for prospective iHubs;
(8) Notification date of award given to successful iHub applicants; and
(9) Official public notification date and posting of award on GO-Biz website.
(c) GO-Biz may alter the schedule by issuance of a revised request for proposal.
(d) A request for proposal will only be accepted from an Applicant that meets the following criteria:
(1) Is qualified to conduct business in the State of California;
(2) Is in good standing with the Secretary of State, if applicable;
(3) Has not been debarred or had contracts terminated due to a breach by Applicant by the federal government, State of California or local government; and
(4) Has a combination of at least twelve months of current direct or related business technical assistance experience
(e) The Applicant must complete a detailed application, not to exceed nine thousand (9000) words, that addresses and provides for all of the following information:
(1) Cover Sheet, which must include the name of the proposed iHub (Applicant), the name of the iHub coordinator, the names of iHub Partners, the date submitted and summary of the iHub's purpose.
(2) The Applicant's contact information
(3) Table of Contents that outlines each section and includes page references;
(4) Statement of Purpose. The Applicant must define the purpose to be served by the formation of the iHub by identifying which entrepreneurial/business cluster(s) will be targeted for growth or identifying the broader economic development goals of the iHub. If neither of these applies, the Applicant must describe the purpose of the proposed iHub. The explanation of the iHub's purpose should be supported by any similar previous efforts, such as cluster analysis, regional business analysis, statewide economic development reports, or any current information which exists to support it;
(5) Signed Statement of Cooperation. The Applicant must demonstrate that a broad partnership in innovation has been formed. A written statement of cooperation or the equivalent must include a description of the roles and relationships of each entity involved in the iHub partnership and an authorized signature to certify the partner's commitment to the iHub. This formal agreement may be submitted in the form of an operational plan, MOU, partnership agreement or similar document; and
(6) Workforce Development. The Applicant must identify the industry sectors of focus within the iHub physical boundaries. For each of those sectors, the Applicant must describe how it will collaborate with the identified industry sectors to identify occupations that it has determined are vital to the competitiveness of the region. Additionally, the Applicant should, but are not required as part of the application, develop industry-driven occupational standards and credentialing that will be implemented by the iHub and its industry partners, as applicable;
(7) Physical boundary. The Applicant shall include a clear explanation and map conveying the iHub's physical boundary, including reasonable explanation for how and why the boundaries were defined.
(A) An iHub's physical boundary typically includes the immediate geographic areas around or connected to an educational institution, university, laboratory, or research center.
(B) The boundary can include knowledge nodes that are not physically contiguous to the iHub but must link educational institutions via technology, transportation, or resource allocation. A clear identification and explanation of these links must be included in the application narrative, including a description of the proposed links (e.g., business parks, campus, incubators, and research and development facilities).
(8) iHub coordinator. The Applicant shall identify the iHub coordinator who will be responsible for coordinating, tracking and monitoring the iHub partner activities as well as those activities set forth in Government Code Section 12099.2(c).
(9) Location. The Applicant musti dentify a central location that will be used to support iHub efforts.
(10) Goals/Benchmarks. The Applicant must identify the goals to be achieved, steps to reach the identified goals, and measures or benchmarks whereby those goals can be determined and evaluated. These goals must be agreed upon by all members of the partnership and shall be set forth in the MOU.
(11) A list and brief description of local and regional incentives and support programs.
(12) A clearly articulated commercial market focus and plan.
(13) A clearly articulated iHub management structure and plan that may include a description of the capabilities, qualifications, and experience of the proposed management team, team leaders, or key personnel who are critical in achieving the proposed objectives.
(14) A list of iHub assets and resources.
(15) A clearly articulated focus area of the iHub including industry sectors or other targeted areas for development and growth.
(16) A list of specific resources available to support and guide startup companies.
(17) Expectations for job development and business creation.
(18) Defined performance standards agreed upon by the partners involved in the development of the iHub.
(19) Evaluation procedures that will be used to measure the level of achievement for each stated goal.
(20) A plan for sustainability.
(21) Organizational experience including capabilities, related experience, facilities, techniques, unusual resources, or unique combinations of these that are integral factors for achieving the proposed objectives.
(22) Demonstrated experience with innovation programs such as involvement with technology commercialization.
(23) Demonstrated experience with technology transfer or licensing.
(24) Demonstrated experience with intellectual property management.
(25) Evidence of community engagement and support.

Cal. Code Regs. Tit. 10, § 8310

1. New section filed 3-22-2017; operative 3-22-2017 pursuant to Government Code section 11343.4(b)(3) (Register 2017, No. 13).

Note: Authority cited: Section 12099.3, Government Code. Reference: Section 12099.3, Government Code.

1. New section filed 3-22-2017; operative 3/22/2017 pursuant to Government Code section 11343.4(b)(3) (Register 2017, No. 13).