00 [Company-Product] Consolidated Checklist
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

 
View only
 
 
ABCDEFGHIJKLMNOPQRSTUVWX
1
`<---- STEP#2 - Using the dropdown filter, Select only cells with an X. [Checklist Start Date]STEP#1 - Select from dropdown menu in the yellow highlighted cells below. Do not modify cells in column K-O
2
x[Checklist Completion Date]CURRENT STATUS:8% / %8%%
3
xCONTRIBUTION NAMEPROJECT:<Selection Req'd>Select License:8%0%
4
xCONTRIBUTING COMPANYSPECIFICATION Contribution:YES<Selection Req'd>
5
xADDRESSDESIGN Contribution:YES<Selection Req'd>
6
xCITY, STATE ZIPOTHER Contribution:
(White Papers,Ref Design,etc)
YES<Selection Req'd>
7
xCOMPANY CONTACT/
Email:
Product Recognition?:YESACCEPTED
8
xYYYY
9
xSTEP#3 - Contributor takes action on all yellow highlighted cells below and notify Project Lead when checklist is completed. 1210
10
XSection A: LICENSE & MEMBERSHIP REQUIREMENTAction Required by ContributorFoundation ApprovalRequired?Contributor CompletedPL Approval Completed
11
xREQUIREDSubmitter must be an OCP member in good standing.YES-Acknowledged by Contributor[Insert link to signed OCP Membership Agreement]YESYESNOAcknowledgement Required[Insert link to signed OCP Membership Agreement]
12
xREQUIREDSubmitter has executed the Copyright License Agreement (CRLA). Acknowledgement RequiredYESNOAcknowledgement Required
13
NASubmitter MUST be a Silver, Gold, or Platinum member and has executed the Copyright License Agreement (CRLA). Acknowledgement RequiredNONOAcknowledgement Required
14
xREQUIREDLink to Copyright License Agreement (CRLA)[Insert link to signed Copyright License Agreement]YESNONO[Insert link to signed Copyright License Agreement]
15
xREQUIREDContributor(s) have signed a Contributor License Agreement (either OCP-CLA or OWF-CLA)Acknowledgement RequiredYESNOAcknowledgement Required
16
NALink to OCP Contribution License Agreement (OCP-CLA)Acknowledgement Required[Insert link to signed OCP-CLA]NONONOAcknowledgement Required[Insert link to signed OCP-CLA]
17
NALink to OWF Contribution License Agreement (OWF-CLA)Acknowledgement Required[Insert link to signed OWF-CLA]NONONOAcknowledgement Required[Insert link to signed OWF-CLA]
18
NAContributor(s) signed an Open Web Foundation Final Specification Agreement (OWFa1.0)Acknowledgement RequiredNONOAcknowledgement Required
19
NALink to OWF Final Specification Agreement (OWFa1.0)Acknowledgement Required[Insert link to signed OWFa1.0]NONONOAcknowledgement Required[Insert link to signed OWFa1.0]
20
xREQUIREDContributor has signed a Certification Mark (Logo) License AgreementAcknowledgement RequiredYESNOAcknowledgement Required
21
NALink to OCP-INSPIRED™ Certification Mark License Agreement [Insert link to signed Certification License Agreement]NONONO[Insert link to signed Certification License Agreement]
22
xREQUIREDLink to OCP-ACCEPTED™ Certification Mark License Agreement [Insert link to signed Certification License Agreement]YESNONO[Insert link to signed Certification License Agreement]
23
xSection B: DOCUMENTATION AND CONFORMANCE REQUIREMENTSAction Required by ContributorFoundation ApprovalProject Lead ApprovalAction Required by Contributor
24
xREQUIREDThe contribution license is denoted in the License section of the SPECIFICATION or Contributed document. Acknowledgement Required<Approval Needed><Approval Needed>YESNONOAcknowledgement Required<Approval Needed>
25
NAExample of correct license section with using the OCP-CLA Contributor License Agreement.
26
NAExample of a correct license section with using the OWF-CLA and OWFa1.0 License Agreement.
27
xLinkExample of a license section text for APACHE or Creative Common licenses.
28
xREQUIREDThe license type (OCPHL-R, OCPHL-P, OWFa1.0) is included in a README.txt file which is co-located with the COMPLETE DESIGN PACKAGE.Acknowledgement Required<Approval Needed><Approval Needed>YESNONOAcknowledgement Required<Approval Needed>
29
xLinkExample README.txt file
30
NAThe project lead has reviewed the proposed contribution (SPECIFICATION, DESIGN PACKAGE, or OTHER) and held sufficient review(s) with the project. <Approval Needed>NONO<Approval Needed>
31
NAThe Foundation’s Incubation committee has previously voted and ACCEPTED the Specification for this Design Package.<Approval Needed>NOVerified by Foundation
32
NAThere will be FUTURE contributor(s) that will produce ORDERABLE SKU(s) that
1) will meet at least 3 tenets on the OCP Principles list, and
2) will meet all criteria in the associated specification, and
3) become recognized in the future as OCP INSPIRED™ or OCP ACCEPTED™ ,
4) will be available within a reasonable timeframe after acceptance, and
5) will be available for purchase by any member company.
Acknowledgement Required<Approval Needed><Approval Needed>NONONOAcknowledgement Required<Approval Needed>
33
xREQUIREDWhich accepted SPECIFICATION does the ORDERABLE SKU(s) conform with?INSERT LINK HERE to Specification<Approval Needed>YESNOINSERT LINK HERE to Specification
34
NAAll the ORDERABLE SKU(s) conform with a previously accepted SPECIFICATION. Acknowledgement Required<Approval Needed>NONOAcknowledgement Required
35
NAThe SKU LIST tab has been completed.
1) all .jpg files have been uploaded and links provided
2) SKU's listed
Acknowledgement Required<Approval Needed>
36
xREQUIREDAll the ORDERABLE SKU(s) conform with an accepted SPECIFICATION and DESIGN PACKAGE. Acknowledgement Required<Approval Needed>YESNOAcknowledgement Required
37
xREQUIREDWhen ORDERABLE SKU(s) are available there will be in place a support agreement and support services for the Product, which are available to end users or solution providers.Acknowledgement Required<Approval Needed>YESNOAcknowledgement Required
38
NAThe Product must be manufactured (i.e., at least one physically available version must exist) and must have a ORDERABLE SKU upon application for certification, and must be available for purchase by any member within 120 days of receiving the OCP INSPIRED™ or OCP ACCEPTED™ recognition marks. Acknowledgement Required<Approval Needed><Approval Needed>NONONOAcknowledgement Required<Approval Needed>
39
NAThe Submitter shall provide engineering evidence that the Product meets 3 of 4 OCP Principles and conforms with an accepted OCP Specification through the submission of engineering documentation, including but not limited to plugfest results, test results, compatibility reports, or other engineering documentation. Use link to example submission. INSERT LINK HERE to Uploaded Presentation.<Approval Needed><Approval Needed>NONONOINSERT LINK HERE to Uploaded Presentation.<Approval Needed>
40
Link to examples of meeting OCP tenets
41
xREQUIREDA final copy of the Specification has been uploaded.INSERT LINK HERE to Specification<Approval Needed>YESNOINSERT LINK HERE to Specification
42
NASubmitter has provide a detailed description of the Product, its features, functions, and components, and how it conforms with an OCP ACCEPTED™ Specification.INSERT LINK HERE to Uploaded Product Datasheet <Approval Needed>NONOINSERT LINK HERE to Uploaded Product Datasheet
43
NA
Presentation material for the Incubation Committee Review has been uploaded.
INSERT LINK HERE to Presentation <Approval Needed>NONOINSERT LINK HERE to Presentation
44
xOPTIONALAdditional support documentation including test and validation reports, AVL, compatibilities reports, etc. INSERT LINK(S) HERE to addl Support Files<Approval Needed>NONOINSERT LINK(S) HERE to addl Support Files
45
xOPTIONALA list of CERTIFICATIONS associated with each ORDERABLE SKU(s) has been uploadedINSERT LINK(S) HERE to addl Support Files<Approval Needed>NONOINSERT LINK(S) HERE to addl Support Files
46
SECTION C: Complete Production Files (e.g. Design Files) LINK TO FILESFoundation ApprovalProject Lead Approval
47
Contributor must decide which outbound hardware license to use and select the license above. After selection above, the requirements will be updated. The “Complete Production Files” aka Design Files means all of the following, in a form sufficient for a person of ordinary skill to manufacture or modify the design of the Product. All materials must be in a machine-readable file format that is (a) based on an open standard or for which a free decoder is widely available without charge; or (b) for CAD- generated system electrical schematics and layout, and mechanical 3D design only, in a form that is commonly in use in the industry and generally commercially available. :
48
LINK to Guidelines for submitting and review Design FilesNOTE: Single ZIP file is preferred which contains all requisite materials in Section C.
49
NAMaterials detailing electrical design and composition, including (a) a full CAD- generated system schematic;Insert LINK to FilesNA<Approval Needed>NONONOInsert LINK to Files<Approval Needed>
50
NAA full CAD-generated system board layout, including timing constraints and stack-up definition;Insert LINK to FilesNA<Approval Needed>NONONOInsert LINK to Files<Approval Needed>
51
NAA full system component bill of materials in a text format (tab-delimited or comma-delimited), including reference designators (e.g., part numbers on the board), manufacturers, manufacturer part numbers, and quantities;Insert LINK to FilesNA<Approval Needed>NONONOInsert LINK to Files<Approval Needed>
52
NAManufacturing files, including
(i) printed circuit board (PCB) manufacturing files in RS-274x or other open format,
(ii) stack-up information in text format, or as an art layer in the RS-274x files, or in a separate file,
(iii) component pick-and-place coordinates in text format and test point coordinates and information in text format;
Insert LINK to FilesNA<Approval Needed>NONONOInsert LINK to Files<Approval Needed>
53
NAA schematic board component placement map;Insert LINK to FilesNA<Approval Needed>NONONOInsert LINK to Files<Approval Needed>
54
NAMaterials detailing mechanical design and structure, including a three-dimensional CAD-generated drawing of the top level assembly, housing, and all parts and subparts in a CAD- neutral format such as STEP or IGES;Insert LINK to FilesNA<Approval Needed>NONONOInsert LINK to Files<Approval Needed>
55
NAAll firmware, tools, and drivers, in binary form, that are required to boot and operate the product within the definition of the Specification and are compatible with at least one major freely or commercially available operating system such as Linux or Windows, including corresponding source code or control interfaces to the extent necessary to enable electrical or mechanical modifications of the hardware design, such as pin reassignment.Insert LINK to FilesNA<Approval Needed>NONONOInsert LINK to Files<Approval Needed>
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
Loading...
 
 
 
CONSOLIDATED CHECKLIST
Reference: OCP Tenets
SKU LIST
Dropdown