[Please Make a Copy] Consolidated Checklist Example

	A	B	C	D	E	F	K	L	M	N	O
1	`	<---- STEP#2 - Using the dropdown filter, Select only cells with an X.			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:	% / %		%	%
3	x	CONTRIBUTION NAME		PROJECT:	<Selection Req'd>	Select License:		0%	0%
4	x	CONTRIBUTING COMPANY		SPECIFICATION Contribution:	YES	OCP-CLA
5	x	ADDRESS		DESIGN Contribution:	YES	OCP-CLA
6	x	CITY, STATE ZIP		OTHER Contribution: (White Papers,Ref Design,etc)	YES	Creative Commons
7	x	COMPANY CONTACT/ Email:		Product Recognition?:	YES	ACCEPTED
8	x	Personal Information Release:	"By making contributions, I acknowledge and accept OCP’s Privacy Policy. I further represent that I have all rights necessary to provide any personal information for myself and others included in my contributions.”	Acknowledgement Required
9	x				YYYY
10	x			STEP#3 - Contributor takes action on all yellow highlighted cells below and notify Project Lead when checklist is completed.			12	0	0
11	X	Section A: LICENSE & MEMBERSHIP REQUIREMENT		Action Required by Contributor	Foundation Approval		Required?	Contributor Completed	PL Approval Completed
12	x	REQUIRED	Submitter must be an OCP member in good standing.	Acknowledgement Required	[Insert link to signed OCP Membership Agreement]		YES	NO	NO	Acknowledgement Required	[Insert link to signed OCP Membership Agreement]
13		NA	Submitter has executed the Copyright License Agreement (CRLA).	Acknowledgement Required			NO	NO		Acknowledgement Required
14		NA	Submitter MUST be a Silver, Gold, or Platinum member and has executed the Copyright License Agreement (CRLA).	Acknowledgement Required			NO	NO		Acknowledgement Required
15		NA	Link to Copyright License Agreement (CRLA)		[Insert link to signed Copyright License Agreement]		NO	NO	NO		[Insert link to signed Copyright License Agreement]
16	x	REQUIRED	Contributor(s) have signed a Contributor License Agreement (either OCP-CLA or OWF-CLA)	Acknowledgement Required			YES	NO		Acknowledgement Required
17	x	Link	Link to OCP Contribution License Agreement (OCP-CLA)	Acknowledgement Required	[Insert link to signed OCP-CLA]		NO	NO	NO	Acknowledgement Required	[Insert link to signed OCP-CLA]
18		NA	Link to OWF Contribution License Agreement (OWF-CLA)	Acknowledgement Required	[Insert link to signed OWF-CLA]		NO	NO	NO	Acknowledgement Required	[Insert link to signed OWF-CLA]
19		NA	Contributor(s) signed an Open Web Foundation Final Specification Agreement (OWFa1.0)	Acknowledgement Required			NO	NO		Acknowledgement Required
20		NA	Link to OWF Final Specification Agreement (OWFa1.0)	Acknowledgement Required	[Insert link to signed OWFa1.0]		NO	NO	NO	Acknowledgement Required	[Insert link to signed OWFa1.0]
21	x	REQUIRED	Contributor has signed a Certification Mark (Logo) License Agreement	Acknowledgement Required			YES	NO		Acknowledgement Required
22		NA	Link to OCP-INSPIRED™ Certification Mark License Agreement		[Insert link to signed Certification License Agreement]		NO	NO	NO		[Insert link to signed Certification License Agreement]
23	x	REQUIRED	Link to OCP-ACCEPTED™ Certification Mark License Agreement		[Insert link to signed Certification License Agreement]		YES	NO	NO		[Insert link to signed Certification License Agreement]
24	x	Section B: DOCUMENTATION AND CONFORMANCE REQUIREMENTS		Action Required by Contributor	Foundation Approval	Project Lead Approval				Action Required by Contributor
25	x	REQUIRED	The contribution license is denoted in the License section of the SPECIFICATION or Contributed document.	Acknowledgement Required	<Approval Needed>	<Approval Needed>	YES	NO	NO	Acknowledgement Required	<Approval Needed>
26	x	Link	Example of correct license section with using the OCP-CLA Contributor License Agreement.
27		NA	Example of a correct license section with using the OWF-CLA and OWFa1.0 License Agreement.
28	x	Link	Example of a license section text for APACHE or Creative Common licenses.
29	x	REQUIRED	The 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>	YES	NO	NO	Acknowledgement Required	<Approval Needed>
30	x	Link	Example README.txt file
31	x	REQUIRED	The project lead has reviewed the proposed contribution (SPECIFICATION, DESIGN PACKAGE, or OTHER) and held sufficient review(s) with the project.			<Approval Needed>		NO	NO		<Approval Needed>
32		NA	The Foundation’s Incubation committee has previously voted and ACCEPTED the Specification for this Design Package.		<Approval Needed>			NO		Verified by Foundation
33		NA	There 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>	NO	NO	NO	Acknowledgement Required	<Approval Needed>
34	x	REQUIRED	Which accepted SPECIFICATION does the ORDERABLE SKU(s) conform with?	INSERT LINK HERE to Specification	<Approval Needed>		YES	NO		INSERT LINK HERE to Specification
35		NA	All the ORDERABLE SKU(s) conform with a previously accepted SPECIFICATION.	Acknowledgement Required	<Approval Needed>		NO	NO		Acknowledgement Required
36		NA	The SKU LIST tab has been completed. 1) all .jpg files have been uploaded and links provided 2) SKU's listed	Acknowledgement Required	<Approval Needed>
37	x	REQUIRED	All the ORDERABLE SKU(s) conform with an accepted SPECIFICATION and DESIGN PACKAGE.	Acknowledgement Required	<Approval Needed>		YES	NO		Acknowledgement Required
38	x	REQUIRED	When 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>		YES	NO		Acknowledgement Required
39	x	REQUIRED	The 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>	YES	NO	NO	Acknowledgement Required	<Approval Needed>
40	x	REQUIRED	The 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>	YES	NO	NO	INSERT LINK HERE to Uploaded Presentation.	<Approval Needed>
41	x		Link to examples of meeting OCP tenets
42	x	REQUIRED	A final copy of the Specification has been uploaded.	INSERT LINK HERE to Specification	<Approval Needed>		YES	NO		INSERT LINK HERE to Specification
43		NA	Submitter 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>		NO	NO		INSERT LINK HERE to Uploaded Product Datasheet
44		NA	Presentation material for the Incubation Committee Review has been uploaded.	INSERT LINK HERE to Presentation	<Approval Needed>		NO	NO		INSERT LINK HERE to Presentation
45		NA	Compliance with the applicable OCP PROFILE for hardware management is highly desired. Please either include the Redfish validator output file if testing is complete, or indicate testing plans and schedule.	INSERT LINK(S) HERE to OCP Profile Validator report	<Approval Needed>		NO	NO		INSERT LINK(S) HERE to OCP Profile Validator report
46		NA	A list of CERTIFICATIONS associated with each ORDERABLE SKU(s) has been uploaded	INSERT LINK(S) HERE to addl Support Files	<Approval Needed>		NO	NO		INSERT LINK(S) HERE to addl Support Files
47		SECTION C: Complete Production Files (e.g. Design Files)		LINK TO FILES	Foundation Approval	Project Lead Approval
48		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. :
49			LINK to Guidelines for submitting and review Design Files	NOTE: Single ZIP file is preferred which contains all requisite materials in Section C.
50		NA	Materials detailing electrical design and composition, including (a) a full CAD- generated system schematic;	Insert LINK to Files	NA	<Approval Needed>	NO	NO	NO	Insert LINK to Files	<Approval Needed>
51		NA	A full CAD-generated system board layout, including timing constraints and stack-up definition;	Insert LINK to Files	NA	<Approval Needed>	NO	NO	NO	Insert LINK to Files	<Approval Needed>
52		NA	A 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 Files	NA	<Approval Needed>	NO	NO	NO	Insert LINK to Files	<Approval Needed>
53		NA	Manufacturing 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 Files	NA	<Approval Needed>	NO	NO	NO	Insert LINK to Files	<Approval Needed>
54		NA	A schematic board component placement map;	Insert LINK to Files	NA	<Approval Needed>	NO	NO	NO	Insert LINK to Files	<Approval Needed>
55		NA	Materials 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 Files	NA	<Approval Needed>	NO	NO	NO	Insert LINK to Files	<Approval Needed>
56		NA	All 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 Files	NA	<Approval Needed>	NO	NO	NO	Insert LINK to Files	<Approval Needed>
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