HubCAP: Difference between revisions
No edit summary |
|||
| (7 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
== <b> | <big><big>[[CAP_Innovation_Hub]]</big> <br/></big> | ||
== <b>HUBCAP</b> <br /> == | |||
=== | === HUBCAP…Announcing CAP’s new Innovation portal! === | ||
Civil Air Patrol’s new innovation ( | Civil Air Patrol’s new innovation (HUBCAP) is focused on honoring the contributions to innovation | ||
our members make every day by highlighting and making accessible innovative solutions that | our members make every day by highlighting and making accessible innovative solutions that | ||
enhance mission execution and/or mission relevance. Designed by the Technical Advisory Group – | enhance mission execution and/or mission relevance. Designed by the Technical Advisory Group – | ||
your Region IT leadership team, | your Region IT leadership team, HUBCAP will serve as an eServices repository where innovation | ||
solutions will be shared with other CAP members. All active CAP members will have the ability to | solutions will be shared with other CAP members. All active CAP members will have the ability to | ||
submit their innovations to the portal, as well as browse the repository for posted solutions that | submit their innovations to the portal, as well as browse the repository for posted solutions that | ||
may meet a local operational challenge. | may meet a local operational challenge. HUBCAP will be deployed in two phases: <br/><br/> | ||
Phase 1: (Launched on 10 December)<br/> | Phase 1: (Launched on 10 December)<br/> | ||
Scope: IT solutions<br/> | Scope: IT solutions<br/> | ||
How it works: Software developers who own a code repository, as are available in services such as | How it works: Software developers who own a code repository, as are available in services such as | ||
GitHub, can submit a request to post a link on | GitHub, can submit a request to post a link on HUBCAP. Members who submit their ideas will certify | ||
that their solution meets CAP regulation requirements and that they agree to allow free use of their | that their solution meets CAP regulation requirements and that they agree to allow free use of their | ||
solutions to other CAP members. The | solutions to other CAP members. The Innovation Pit Crew will perform a security review of | ||
linked code. If no security concerns are notated, the TAG will approve the link. Members will then | linked code. If no security concerns are notated, the TAG will approve the link. Members will then | ||
be able to access the code for reuse to support their local requirements. Members will also be able | be able to access the code for reuse to support their local requirements. Members will also be able | ||
| Line 22: | Line 23: | ||
evaluation of the “goodness” of an idea, no approval gates to pass. The goal is to determine the | evaluation of the “goodness” of an idea, no approval gates to pass. The goal is to determine the | ||
highest value solutions through crowdsourcing by members via their ratings and the volume of | highest value solutions through crowdsourcing by members via their ratings and the volume of | ||
reuse.<br/> | reuse.<br/><br/> | ||
Phase 2: ( | Phase 2: (August 2020)<br/> | ||
Scope: Other Innovation Artifacts<br/> | Scope: Other Innovation Artifacts<br/> | ||
How it works: | How it works: HUBCAP will be expanded beyond IT code, to allow for sharing of other types of | ||
innovative solutions. Again, members who submit their innovations will certify that their solution | innovative solutions. Again, members who submit their innovations will certify that their solution | ||
does not violate CAP regulations and that they agree to allow free use of their solutions to CAP | does not violate CAP regulations and that they agree to allow free use of their solutions to CAP | ||
| Line 31: | Line 32: | ||
there will be no approval gates. These innovations will be evaluated through the same | there will be no approval gates. These innovations will be evaluated through the same | ||
crowdsourcing approach. | crowdsourcing approach. | ||
[[File:HUBCAP Logo.png|200px|thumb|left|HUBCAP Logo]] | |||
<br/> | |||
<big><big>[[CAP_Innovation_Hub]]</big> <br/></big> | |||
Latest revision as of 03:42, 12 August 2020
HUBCAP
HUBCAP…Announcing CAP’s new Innovation portal!
Civil Air Patrol’s new innovation (HUBCAP) is focused on honoring the contributions to innovation
our members make every day by highlighting and making accessible innovative solutions that
enhance mission execution and/or mission relevance. Designed by the Technical Advisory Group –
your Region IT leadership team, HUBCAP will serve as an eServices repository where innovation
solutions will be shared with other CAP members. All active CAP members will have the ability to
submit their innovations to the portal, as well as browse the repository for posted solutions that
may meet a local operational challenge. HUBCAP will be deployed in two phases:
Phase 1: (Launched on 10 December)
Scope: IT solutions
How it works: Software developers who own a code repository, as are available in services such as
GitHub, can submit a request to post a link on HUBCAP. Members who submit their ideas will certify
that their solution meets CAP regulation requirements and that they agree to allow free use of their
solutions to other CAP members. The Innovation Pit Crew will perform a security review of
linked code. If no security concerns are notated, the TAG will approve the link. Members will then
be able to access the code for reuse to support their local requirements. Members will also be able
to rate the repository in order to assist others in identifying high value solutions. It is important to
note that the TAG review is focused on the security of the code, not functionality. There is no
evaluation of the “goodness” of an idea, no approval gates to pass. The goal is to determine the
highest value solutions through crowdsourcing by members via their ratings and the volume of
reuse.
Phase 2: (August 2020)
Scope: Other Innovation Artifacts
How it works: HUBCAP will be expanded beyond IT code, to allow for sharing of other types of
innovative solutions. Again, members who submit their innovations will certify that their solution
does not violate CAP regulations and that they agree to allow free use of their solutions to CAP
members. Approval for inclusion will be limited to cursory review for safety or security concerns but
there will be no approval gates. These innovations will be evaluated through the same
crowdsourcing approach.
