Editing C&I Wiki Portal/Criteria

Jump to navigation Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.

Latest revision Your text
Line 1: Line 1:
=FINAL DRAFT - TO GO INTO EFFECT JANUARY 1ST, 2016=


==Terminology==
==Terminology==


*'''Spec''' -- The “on paper” specification.  May include a BoM, mechanical files, board files, add on cards, firmware, each of which increase specificity.
'''Spec''' -- The “on paper” specification.  May include a BoM, mechanical files, board files, add on cards, firmware, each of which increase specificity.
*'''Device''' -- The original or “reference” implementation of the spec, or a secondary implementation.  If secondary, could follow a spec precisely, or be a derivative of the spec
'''Device''' -- The original or “reference” implementation of the spec, or a secondary implementation.  If secondary, could follow a spec precisely, or be a derivative of the spec
*'''Implementation''' -- Amongst particular devices, there may still be differences (e.g. different wire runs in the board, different chip placement, etc), even if they follow the general spec.  The higher the specificity in the spec (items like board files and BoMs are examples of things that increase specificity), the greater the odds that any given implementation will vary from it.
'''Implementation''' -- Amongst particular devices, there may still be differences (e.g. different wire runs in the board, different chip placement, etc), even if they follow the general spec.  The higher the specificity in the spec (items like board files and BoMs are examples of things that increase specificity), the greater the odds that any given implementation will vary from it.
 
 


==OCP INSPIRED Product==
==OCP INSPIRED Product==


All OCP Inspired products must adhere to the following criteria, which are subject to Foundation staff, Incubation Committee leadership, and relevant Project Lead.
All OCP Inspired Products must adhere to the following criteria, which are subject to Foundation staff, Incubation Committee leadership, and relevant Project Lead.
A product may called OCP INSPIRED when the following two groups of criteria are met:
A product may called considered OCP INSPIRED when the following two groups of criteria are met.
 
 
===GROUP 1===


'''OCP INSPIRED GROUP 1 CRITERIA'''
The Product '''MUST''' meet at least one of the following criteria:


The Product '''MUST''' meet at least one (1) of the three (3) the following criteria:
Product MUST fit into a 19 inch rack or Open Rack.  For component-level '''MUST''' fit inside a device designed for either of those racks.


'''(1)''' The Product MUST fit into a 19 inch rack and be related to Open Compute or Open Rack.  If a component (e.g. adapter, memory, processor, disk, etc.), it '''MUST''' fit inside a device designed for either of those racks.
'''OR'''


'''(2)''' The spec associated with the Product '''MUST''' be submitted '''AND''' acknowledged by the following individuals:
The spec associated with the Product '''MUST''' be submitted '''AND''' acknowledged by the following individuals:


*An Open Compute Foundation Staff member
A Foundation Staff member
*The Chair or Vice Chair of the IC
The Chair or Vice Chair of the IC
*The Relevant Project Lead(s) -- (e.g. Server Project Lead(s) for servers, Storage Project Lead(s) for Storage).
Relevant Project Lead(s) -- (e.g. Server Project Lead(s) for servers, Storage Project Lead(s) for Storage).


'''(3)''' The Product must have one of the following licenses assigned, with proof of assignment provided to and acknowledged by the Open Compute Foundation:
'''OR'''
 
The Product must have one of the following licenses assigned, with proof of assignment provided to and acknowledged by the Open Compute Foundation:


*OWF (Open Web Foundation)
*OWF (Open Web Foundation)
Line 30: Line 36:
*OCPHL-R (Open Compute Project hardware License - Reciprocal)
*OCPHL-R (Open Compute Project hardware License - Reciprocal)


'''OCP INSPIRED GROUP 2 CRITERIA'''
===GROUP 2===


The Product '''MUST''' be associated with IT computing, and/or networking, and/or storage.  This association is determined at the discretion of an Open Compute Foundation Staff Member or representative.
The Product '''MUST''' also meet all of the following criteria:
 
 
The Product '''MUST''' be associated with IT computing, and/or networking, and/or storage.  This association is determined by a Foundation Staff Member or representative.


'''AND'''
'''AND'''


The Product '''MUST''' be manufactured (that is, at least one physically available version of it must exist, even if just a prototype or engineering sample).
The Product '''MUST''' be manufactured (that is, at least one physically available version of it must exist, even if just a prototype or engineering sample).


==OCP ACCEPTED Product ==
==OCP ACCEPTED Product ==
Line 42: Line 52:
All OCP Accepted products must aligned to a prior Incubation Committee approved specification (aka SPECIFICATION) that has been submitted to the Incubation Committee and been approved by vote of the Incubation Committee.   
All OCP Accepted products must aligned to a prior Incubation Committee approved specification (aka SPECIFICATION) that has been submitted to the Incubation Committee and been approved by vote of the Incubation Committee.   


Products making the claim of compliance with an approved specification SHALL at a minimum, follow all requirements defined as mandatory by the use of the following keywords in that specification: SHALL - MUST - WILL - REQUIRED.  Such products may also provide ''recommended'' features associated with the keyword “SHOULD” and ''permitted'' features associated with the keyword “MAY”. A product may called OCP ACCEPTED when the following two groups of criteria are met:
Products making the claim of compliance with an approved specification SHALL provide, at a minimum, all features defined as mandatory by the use of the following keywords: SHALL - MUST - WILL - REQUIRED.  Such products may also provide recommended features associated with the keyword “SHOULD” and permitted features associated with the keyword “MAY”.


'''OCP ACCEPTED GROUP 1 CRITERIA:'''


ALL (6) of the following criteria are:  
A product may be called OCP ACCEPTED when ALL (6) criteria is met:  


*'''MUST''' be a product that has been manufactured  
*'''MUST''' be a product that is being manufactured  
*'''MUST''' be available for purchase by any member company within 120 days of receiving OCP ACCEPTED recognition. This will be subject to audit, approval, and, if approval is not met, revocation of OCP ACCEPTED status, by OCP Foundation Staff.  
*'''MUST''' be available for purchase by any member company within xx days. .
*'''MUST''' meet all criteria in the SPECIFICATION described as “SHALL” or “MUST” or “WILL” or “REQUIRED”.  '''NO''' exceptions are allowed.   
*'''MUST''' meet all criteria in the SPECIFICATION described as “SHALL” or “MUST” or “WILL” or “REQUIRED” .  NO exceptions are allowed.   
*The submitter has completed a self-assessment AND attests that EACH SKU (orderable part number) meets the criteria.
*The submitter has completed a self-assessment AND attests that EACH SKU (orderable part number) meets the criteria.
*Submitter / Requestor has sent the self-assessment documentation to the Foundation.
*Submitter / Requestor has sent the self-assessment documentation to the Foundation.
*Submitter HAS provided the Foundation with the list of SKUs and orderable part numbers, and the documentation necessary for a re-assessment to be completed by the Foundation lab director or a 3rd Party designee, and the Foundation Staff.  Acceptable documentation can be links to public information or documentation sent to the foundation.  It is the submitter’s responsibility to provide ALL the documentation to prove that specification criteria is met.
HAS provided the Foundation with the list of SKUs and Orderable P/Ns and the documentation necessary for a re-assessment to be completed by the Foundation lab director or a 3rd Party designee, and the Foundation Staff.  Acceptable documentation can be links to public information or documentation sent to the foundation.  It is the submitter’s responsibility to provide ALL the documentation to prove the SPECIFICATION criteria is met.  
 
'''OCP ACCEPTED GROUP 2 CRITERIA:'''
 
*After a product has met OCP ACCEPTED GROUP 1 criteria, the OCP Foundation will list the SKUs and orderable part numbers, published on the OCP web portal.
 
Upon publication on the OCP web portal, the Submitter may use the term “OCP ACCEPTED” per OCP terms and conditions.


'''OCP ACCEPTED NOTES'''
When a product has met the criteria to be OCP ACCEPTED:
The FOUNDATION will list the SKUs and Orderable P/N’s and will publish this on the OCP web portal. 
The Submitter may use the term “OCP ACCEPTED” per OCP terms and conditions.


If a product does NOT meet the criteria in the SPECIFICATION described as “SHALL” or “MUST”,  the submitter is encouraged to contact the original SPECIFICATION author(s) with a list of differences and non-compliance.  The author(s) MAY create a modification or revision to the SPECIFICATION that would allow the submitter’s product to be reconsidered.  Alternatively, the submitter may author their own specification, get it approved by the relevant Project Groups and Incubation Committee, and submit for OCP ACCEPTED recognition against this new specification.
If a product does NOT meet the criteria in the SPECIFICATION described as “SHALL” or “MUST”,  the submitter is encouraged to contact the original SPECIFICATION author(s) with a list of differences and non-compliance.  The author(s) MAY create a modification or revision to the SPECIFICATION that would allow the submitter’s product to be reconsidered.  Alternatively, the submitter may author their own specification, get it approved by the Incubation Committee, and submit their product against it.
Please note that all contributions to OpenCompute may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see OpenCompute:Copyrights for details). Do not submit copyrighted work without permission!
Cancel Editing help (opens in new window)