none
How to request a contingency? RRS feed

  • Frage

  •  

    如题.

    在 Windows Hardware Logo Program Requirements (WLP-Policies_03-21-08) 这个文档中,Test Failure Contingency Policy 这段提到了"Windows Logo Program Procedures and Information" 中的"how to request a contingency",  但是并没有像其他一样列出可以找到"Windows Logo Program Procedures and Information" 的地址.(只有一个TBD ...)

    原文如下:

    Design and Implementation Notes

    See "Windows Logo Program Procedures and Information" at TBD.

     

     

    不知道这里的朋友有没有"Windows Logo Program Procedures and Information" 这个文档?

     

    或者, 如果有知道 how to request a contingency的, 能否告知下流程,以及需要准备的材料.

     

    在此先谢过了.

     

    SeanGe

    Dienstag, 13. Januar 2009 02:09

Antworten

  • 您需要跟loogfb@microsoft.com联系申请 一个contingency. 或者跟CSS以及TAM联系请他们协助也可以。



    Contingency Policy

     

     

    Submitting Requests for Contingency

     

    Contingencies may be requested when a test failure has been researched by Microsoft and determined to be caused by a problem with the device or device driver being submitted for Logo. Limited exceptions are granted for 30 - 60 days based on an assessment of the technical issue and the related business needs after fully considering the customer impact and the firm commitment from the affected partner on resolving the issues. Not all contingencies are approved.

     

    The typical contingency review process takes anywhere from 4 to 6 weeks, so please plan in advance prior to making any requests. Requests for contingency must include all the information detailed in the "How to request a contingency" section of the Contingency Policy. The information provided must be as complete as possible. Missing or incomplete information will cause a delay in the evaluation of the request.

     

     

    How to request a contingency

     

    The partner is required to provide the following information:

    • Company name
    • Company contact
    • Submission Category - As it appears in the DTM Device Console Submission Wizard or Winqual web portal. For example:
      • If device, Network - LAN or Storage – Removable Media OR
      • If systems, Desktop or Mobile
    • Operating System(s)
      • Windows XP 32bit/64bit
      • Windows Server 2003 32bit/64bit/IA64
      • Vista 32bit/64bit
    • Product names of all affected products – Request should follow one of these formats:
      • One Driver Test Manager (DTM) test failure or Windows Logo Program (WLP) specification compliance issue that affects multiple products
      • One product that is affected by multiple DTM test failures or WLP specification compliance issues
    • Product Plug and Play IDs and/or device enumeration strings of all affected products
    • Failed submission ID and/or verifiable statement that the Partner has completed all DTM tests and that there are no other outstanding test failures or WLP specification compliance issues.
      • Failed submission ID
      • Full DTM kit test execution (full and complete DTM cpk)
    • WLP requirement identification number and the corresponding name of test that has failed
    • Failed DTM test log(s) – As mentioned previously, full DTM CPK is required for contingency request. Excerpt from failed log and/or specific failed log from DTM CPK is acceptable to meet this specific line item.
    • Details indicating what error(s) in the log are of concern – For example: warnings for DTM test preview and/or WLP requirement preview
    • Technical justification for allowing product to ship with failing issue.
    • Business justification for the contingency.
    • End-user (Consumer) impact if product ships with specification compliance issue – NOTE: Logo Program will request as line item of formal contingency agreement the right to publish publicly any and all end-user impact scenarios resulting from stated specification compliance issue. Example of end-user impact:
      • Affected applications
      • Affected game play scenario
      • OS functionality or scenario blocked
    • Plan for mitigating WLP specification non-compliance (proposed solution) – plans must include the following information:
      • Recommended corrective action for WLP specification compliance: Example of corrective actions:
        • Driver – new or updated.  Microsoft will request availability on Windows Update.
        • Firmware – new or updated.
        • Hardware
      • Expected dates for WLP specification compliance:
        • Creation and/or Test date for actual compliant driver / firmware / hardware product
        • Ship date for actual compliant product
        • ‘End of Life’ (stop ship) date for the non-compliant product
        • Submission date of the compliant product; date reflected in Winqual web portal submission
    • As appropriate, copies of email correspondence between Partner and Microsoft regarding discussions, research, and investigation in reference to stated specification compliance issue.

     

    Contingency requests are accepted as feedback with regards to the Windows Logo Program Requirements.  As such, the Partner will submit formal contingency requests to LogoFB@microsoft.com

     

    • Request will be queued for review during the next weekly Contingency Approval Board meeting.
    • Results of the review will be communicated to the Partner by a designated Logo Program team representative and/or the Partner’s TAM.
    • Results may be:
      • Requests for additional details or further investigation
      • Renegotiation of the terms in the formal contingency request
      • Approval or denial with supporting details

     

    If the contingency request is approved, a formal contingency is drafted. The contingency draft is made available online at the secure Winqual web portal. The contingency draft requires the Partner’s Director level signature. The online contingency is then countersigned by Microsoft and a contingency number is issued to the Partner.  The formal contingency is available to the Partner for review at any time via the Winqual web portal.

     

    If the request is denied then the requester if notified and supporting details are provided. The requester may appeal the contingency denial by contacting LogoFB@microsoft.com and escalating to the Logo Program Group Manager.

     

     

    Dienstag, 13. Januar 2009 07:15
    Moderator

Alle Antworten

  • 您需要跟loogfb@microsoft.com联系申请 一个contingency. 或者跟CSS以及TAM联系请他们协助也可以。



    Contingency Policy

     

     

    Submitting Requests for Contingency

     

    Contingencies may be requested when a test failure has been researched by Microsoft and determined to be caused by a problem with the device or device driver being submitted for Logo. Limited exceptions are granted for 30 - 60 days based on an assessment of the technical issue and the related business needs after fully considering the customer impact and the firm commitment from the affected partner on resolving the issues. Not all contingencies are approved.

     

    The typical contingency review process takes anywhere from 4 to 6 weeks, so please plan in advance prior to making any requests. Requests for contingency must include all the information detailed in the "How to request a contingency" section of the Contingency Policy. The information provided must be as complete as possible. Missing or incomplete information will cause a delay in the evaluation of the request.

     

     

    How to request a contingency

     

    The partner is required to provide the following information:

    • Company name
    • Company contact
    • Submission Category - As it appears in the DTM Device Console Submission Wizard or Winqual web portal. For example:
      • If device, Network - LAN or Storage – Removable Media OR
      • If systems, Desktop or Mobile
    • Operating System(s)
      • Windows XP 32bit/64bit
      • Windows Server 2003 32bit/64bit/IA64
      • Vista 32bit/64bit
    • Product names of all affected products – Request should follow one of these formats:
      • One Driver Test Manager (DTM) test failure or Windows Logo Program (WLP) specification compliance issue that affects multiple products
      • One product that is affected by multiple DTM test failures or WLP specification compliance issues
    • Product Plug and Play IDs and/or device enumeration strings of all affected products
    • Failed submission ID and/or verifiable statement that the Partner has completed all DTM tests and that there are no other outstanding test failures or WLP specification compliance issues.
      • Failed submission ID
      • Full DTM kit test execution (full and complete DTM cpk)
    • WLP requirement identification number and the corresponding name of test that has failed
    • Failed DTM test log(s) – As mentioned previously, full DTM CPK is required for contingency request. Excerpt from failed log and/or specific failed log from DTM CPK is acceptable to meet this specific line item.
    • Details indicating what error(s) in the log are of concern – For example: warnings for DTM test preview and/or WLP requirement preview
    • Technical justification for allowing product to ship with failing issue.
    • Business justification for the contingency.
    • End-user (Consumer) impact if product ships with specification compliance issue – NOTE: Logo Program will request as line item of formal contingency agreement the right to publish publicly any and all end-user impact scenarios resulting from stated specification compliance issue. Example of end-user impact:
      • Affected applications
      • Affected game play scenario
      • OS functionality or scenario blocked
    • Plan for mitigating WLP specification non-compliance (proposed solution) – plans must include the following information:
      • Recommended corrective action for WLP specification compliance: Example of corrective actions:
        • Driver – new or updated.  Microsoft will request availability on Windows Update.
        • Firmware – new or updated.
        • Hardware
      • Expected dates for WLP specification compliance:
        • Creation and/or Test date for actual compliant driver / firmware / hardware product
        • Ship date for actual compliant product
        • ‘End of Life’ (stop ship) date for the non-compliant product
        • Submission date of the compliant product; date reflected in Winqual web portal submission
    • As appropriate, copies of email correspondence between Partner and Microsoft regarding discussions, research, and investigation in reference to stated specification compliance issue.

     

    Contingency requests are accepted as feedback with regards to the Windows Logo Program Requirements.  As such, the Partner will submit formal contingency requests to LogoFB@microsoft.com

     

    • Request will be queued for review during the next weekly Contingency Approval Board meeting.
    • Results of the review will be communicated to the Partner by a designated Logo Program team representative and/or the Partner’s TAM.
    • Results may be:
      • Requests for additional details or further investigation
      • Renegotiation of the terms in the formal contingency request
      • Approval or denial with supporting details

     

    If the contingency request is approved, a formal contingency is drafted. The contingency draft is made available online at the secure Winqual web portal. The contingency draft requires the Partner’s Director level signature. The online contingency is then countersigned by Microsoft and a contingency number is issued to the Partner.  The formal contingency is available to the Partner for review at any time via the Winqual web portal.

     

    If the request is denied then the requester if notified and supporting details are provided. The requester may appeal the contingency denial by contacting LogoFB@microsoft.com and escalating to the Logo Program Group Manager.

     

     

    Dienstag, 13. Januar 2009 07:15
    Moderator
  • Ding


    http://msdn.microsoft.com/zh-cn/windows/hardware/default.aspx http://whqlcn.wordpress.com
    Mittwoch, 8. Juni 2011 07:38
    Moderator
  • 要联系CSS开Case,由support engineer协助你申请contingency, 直接联系logofb@microsoft.com 多半会被要求开case。

    有TAM的话会帮助很多


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. Regards, Fred Zhang Microsoft Online Community Support
    Donnerstag, 11. August 2011 09:19