• 1.  Introduction
• 1.1  Referenced Standards
• 1.2  Summary of Certification Documents
• 1.3  Summary of Web References

• 2.  How to Achieve Certification
• 2.1  Understanding the Program
• 2.2  Confidentiality
• 2.3  Informal Testing
• 2.4  Certification
• 2.5  The POSIX Trademark License Agreement (TMLA)
• 2.6  The Certification Agreement
• 2.7  The Test Suite Agreement

• 3.  Product Registration
• 3.1  Optional Step - Completing the Trademark License Agreement
• 3.2  The Conformance Statement
• 3.3  Submitting Initial Certification Information
• 3.4  Registering your Product
• 3.5  Submitting your Conformance Statement
• 3.6  Obtaining the Test Suites
• 3.7  Formal Testing For Certification
• 3.8  The Final Step - Confirming your Submission & Payment
• 3.9  Completion of Certification
• 3.10  The Appeals Process

• 4.  Renewals and Certified Product Updates
• 4.1 The Renewals Process
• 4.2 Certified Product Updates

• 5.  Certification Checklist

1. Introduction

This document is a guide for suppliers who want to submit products for certification within the POSIX™: Certified by IEEE and The Open Group  Program. This certification program has been jointly developed and is operated by IEEE and The Open Group. This document guides you through all the steps required for certification.

Certification is given to those products or range of products that have been certified by IEEE and The Open Group as having demonstrated their conformance to the applicable Conformance Requirements. The detailed requirements for conformance are identified in the relevant Product Standards. Suppliers of Certified Products may optionally choose to license the POSIX certification trademark for use in connection with their product.

The Certification Policy governs certification. The Certification Agreement covers the terms and conditions of the certification service and the warranty of conformance. You must agree to the terms and conditions outlined in both these documents prior to certification. If you decide to license the POSIX certification trademark, then you must also agree to the terms in the Trademark License Agreement (TMLA). For your convenience, significant highlights of the certification process are outlined below, and the following sections give more comprehensive information.

1. The Certification Authority is The Open Group.
2. The Trademark License Authority is IEEE.
3. Your product will be certified and entered on the certification register when your product has passed the applicable certification Test Suite(s) and you have formally agreed to all the required terms.
4. You will be granted a license to use the POSIX certification trademark in connection with your product when your product has been certified and you have formally executed a Trademark License Agreement with IEEE.
5. A certified product is subject to re-certification on a periodic basis as stated in the Certification Policy.
6. All product information supplied to the Certification Authority will be treated as confidential, as required by the Certification Agreement.
7. The Open Group Certification Authority may, from time to time, request proof that your product remains in compliance with the requirements outlined in the Conformance Requirements, as required by the Certification Agreement.

At the end of this document is a Certification Checklist to help you make sure that your product registration is complete.

Note: In the event of any conflicts, this guide defers to the Certification Policy, the POSIX Trademark License Agreement and the Certification Agreement

1.1 Referenced Standards

The IEEE standards currently referenced for the POSIX certification program are:

• IEEE Std 1003.1™, 2016 Edition
• IEEE Std 1003.1™, 2003 Edition
• IEEE Std 1003.13™, 2003 Edition

This is referenced by the Product Standards (see Section 2.1.2).

You should be familiar with the applicable standard prior to commencing certification. See Section 1.3 for information on obtaining copies of the standards.

1.2 Summary of Certification Documents

This section includes a list of all the certification documents and their purpose.

To become familiar with this certification program, you should read the following program documents:

The Certification Policy
This document is the foundation of the program, providing information on the types of products that can be certified in the program, what it means to be certified, what is required to get a product certified and how to make sure that a product remains certified. See Section 2.1.2 for further information.

The POSIX Trademark License Agreement
(available on request) The POSIX Trademark License Agreement is optional for certification but is required if you wish to use the POSIX trademark in connection with your product. For this version of the program, the POSIX trademark can only be licensed for use with certain Product Standards, see Section 2.5 for further information.

The Product Standards
The Product Standards should then be read to understand the detailed conformance requirements against which a product can be certified. See Section 2.1.2 for further information.

The Certification Agreement
The Certification Agreement defines the certification service and the legal commitment to the conditions of the service. See Section 2.6 for further information.

The Guide to Certification (this document)
This document is a guide for suppliers who want to certify products and provides detailed information on the steps required to take to achieve certification.

Conformance Statement Questionnaires
A questionnaire to be completed during certification. It contains a structured set of questions which when answered describe the way in which the Product meets the Conformance Requirements. It also precisely identifies the product and the environment in which conformance is guaranteed. There is a conformance statement for each Product Standard. See Section 3.2 for further information.

POSIX Conformance Document (PCD)
This is a document required to be produced by suppliers claiming conformance to IEEE Std 1003.1 or IEEE Std 1003.13. It is required when certifying to the 1003.1™-2003 or 1003.1™-2016 Base Product Standard, the PSE54 Multipurpose Realtime 1003.13-2003 System Product Standard and the PSE52 Realtime Controller 1003.13-2003 System Product Standard

1.3 Summary of Web References

A summary of the external web references is given below:

http://get.posixcertified.ieee.org/	The Starting point for POSIX Certified by IEEE and The Open Group
http://get.posixcertified.ieee.org/docs/POSIX_Certification_Policy_v1.1.pdf	The Certification Policy
http://www.unix.org/version4/	The POSIX 1003.1, 2016 Edition Specification (html version)
http://get.posixcertified.ieee.org/certification_guide.html	The Guide to Certification
http://get.posixcertified.ieee.org/register.html	The Certification Register
http://get.posixcertified.ieee.org/prodstandards.html	The Current Set of Product Standards
http://get.posixcertified.ieee.org/docs/testsuites.html	The List of Currently Authorized Test Suites
http://get.posixcertified.ieee.org/PR/	The Problem Reporting System and Database
http://get.posixcertified.ieee.org/posixfaq.html	The Frequently Asked Questions File
http://get.posixcertified.ieee.org/prodstandards.html	The Conformance Statement Questionnaires

---

2. How to Achieve Certification

This guide details the steps you are required to take to achieve certification, and provides information on how to perform each of these steps.

The process involves:

• Understanding the certification program and process
• Testing the product informally
• Applying for certification
• Formal testing and submission of results

2.1 Understanding the certification program

To become familiar with the program, you should read the following program documents:

• The Certification Policy
• The Product Standards

2.1.1 The Certification Policy

It is best to start with the Certification Policy, which is the foundation of the program. It provides information on the types of products that can be certified in the program, what it means to be certified, what is required to get a product certified and how to make sure that a product remains certified.

The Certification Policy describes certification for Products meeting the conformance requirements as specified in a Product Standard (see Section 2.1.2). There are two levels of certification defined:

• Platform Specific Certification
• Product Family Certification

Platform Specific Certification refers to a single defined environment, whereas Product Family Certification is for a binary-compatible family. A defined environment is the combination of hardware and software. Having two certification levels allows you to choose the appropriate level to match your certification needs. If you wish to register a single product on a single hardware platform for certification, then choose Platform Specific, in which case a single set of results is required. If you want to extend your certification across a range of binary compatible hardware and software environments then choose Product Family, in which case you will then need to submit test results from two distinct members of the family to provide the necessary assurance.

2.1.2 The Product Standards

The Product Standards should then be read to understand the detailed conformance requirements against which a product can be certified. Product Standards provide a mapping between certification, the POSIX standards and the test suites needed to demonstrate conformance. Product Standards exist for each type of product that can be certified.

The current Product Standards that products can be certified against are:

• 1003.1™-2016 Base

which is comprised of the following subsidiary Product Standards:

• 1003.1™-2016 System Interfaces
• 1003.1™-2016 Shell and Utilities

Certification is also still possible for the 2003 editions of the above.

The following are standalone Product Standards:

• PSE54 Multipurpose Realtime 1003.13™-2003 System
• PSE52 Realtime Controller 1003.13™-2003 System

You should review Section 3, Conformance of the Certification Policy and the Product Standards and identify those against which you would like to have your product certified. The 1003.1 Product Standards are interrelated. You can register your product for either the 1003.1™-2016 System Interfaces, or 1003.1™-2016 Shell and Utilities, or both. However for the 1003.1™-2016 Base Product Standard, both the subsidiary Product Standards must be registered, either prior or simultaneously, for certification to be achieved. The 1003.13 PSE54 and 1003.13 PSE52 Product Standards can be registered on their own.

2.2 Confidentiality

Your company and product details are confidential between you and the Certification Authority. This is effective once you complete and return the Certification Agreement, which is a prerequisite to registering a product.  The Certification Authority does not make any certification information available to any third party, including employees, consultants or members, without the written permission of the supplier.

Upon successful completion of the certification process, the certified product will be included in the publicly available Certification Register at http://get.posixcertified.ieee.org/register.html. However, to allow for time lag to launch a certified product, you may request that certification remain confidential for up to 6 months from the date of written notification by the Certification Authority that a product has achieved certification. A request that the certification remain confidential can be made in the final step of the product registration (see Section 3.7 below). See Section 12.3 of the Certification Policy for further information.

2.3 Informal Testing

Normally testing your product with the certification test suite(s) is the first activity.  You should read the applicable Product Standard for the product you are considering certifying, referring to the Indicators of Compliance section to identify the required certification test suites.

If you are not an existing test suite licensee then you need to obtain the test suites from the Certification Authority (for the 1003.1 Product Standards they can be obtained once you commence a product registration, see Sections 2.7 and 3.6).

You should in all cases check that the version of the test suite is still authorized (see Section 2.3.1). The test suite should be used, along with any additional method you deem appropriate, to make sure that your product meets the applicable conformance requirements and is ready for formal registration for certification.

2.3.1 Authorized Test Suites

You should note that for formal testing, only currently authorized versions of the certification test suites can be used. So, if after obtaining the test suites, your informal testing takes an extended period you should check back to ensure that the version is still an authorized version. The Certification Authority maintains a list of the currently authorized certification test suites at http://get.posixcertified.ieee.org/docs/testsuites.html.

Below is information on how to find further information on the test suites and where to report any bugs.

2.3.2 Problems and Problem Reporting

For 1003.1 The Open Group provides five days elapsed time initial installation support for the test suites. You may also purchase additional ninety-day periods or an annual support license. The support service is provided by electronic mail and information on the terms of the service and how to obtain it is provided with the test suite when it is made available.

If you have problems outside of the initial free support period with running the certification test suites, please first read the documentation provided with the test suite. If this does not answer your questions, please check the Frequently Asked Questions file at http://get.posixcertified.ieee.org/posixfaq.html.

For 1003.13 PSE54 and 1003.13 PSE52, support is dependent on a support license being in place.

If you are using one of the authorized test suites and getting failures but are certain that your product conforms to the standards, please check the Problem Report information database held at http://get.posixcertified.ieee.org/PR. The online Problem Report database contains known information on existing bugs and interpretations of the standard.  The issue may already be resolved by an existing Interpretation, or by an agreed Test Suite Deficiency.  If it is not, please raise a new Problem Report, see http://get.posixcertified.ieee.org/PR.

For general questions related to certification, but not test suite specific, you can email posix-helpdesk@opengroup.org fully describing the problem. Please note that the Certification Authority helpdesk only handles general questions and is not able to address test suite specific issues.

2.4 Certification

Certification is a formal process.  You, as a supplier of a certified product, warrant and represent by accepting the Certification Agreement that the product meets all the conformance requirements applicable to the Product Standard against which it is certified and implements all the features claimed in the Conformance Statement.

The obligations, terms and conditions of certification are fully set out in the following documents:

• the Certification Policy
• the Certification Agreement

and if you intend to use the POSIX trademark in connection with your certified product:

• the POSIX Trademark License Agreement

These documents are available via the POSIX Certification Web Page at http://get.posixcertified.ieee.org/.

It is necessary to read these documents before you start the certification process in order to fully understand the policies and requirements.

2.5 The POSIX Trademark License Agreement (TMLA)

If you wish to use the POSIX trademark in association with your certified Product, then you need also to execute a trademark license agreement prior to any use of the POSIX trademark. The POSIX Trademark License Agreement is between you and the IEEE and requires signature.

The POSIX trademark can be licensed for use with the following product standards:

• 1003.1™-2016 Base Product Standard
• 1003.1™-2003 Base Product Standard
• PSE54 Multipurpose Realtime 1003.13-2003 System Product Standard
• PSE52 Realtime Controller 1003.13-2003 Product Standard.

A visible notation of whether a product is licensed to use the POSIX trademark is carried on the Certification Register.

The Trademark License agreement only needs to be entered into once per organization. When it is in place multiple certified products can use the trademark without the need to execute another agreement with the IEEE. Trademark licensees with certified products receive a certificate for each applicable product.

2.6 The Certification Agreement

You are required to agree to the Certification Agreement for each product registration.

The Certification Agreement is between you and the Certification Authority. It defines the certification service and the legal commitment to the conditions of the service. This is also where you warrant conformance of your product to the relevant Product Standard.

2.7 The Test Suite Agreement

(This section is not applicable if you are registering a product against the PSE54 Multipurpose Realtime 1003.13-2003 System Product Standard or the PSE52 Realtime Controller 1003.13-2003 Product Standard.)

If you are not already a licensee of the test suite designated as the indicator of compliance for the Product Standard against which your product is being registered then you must agree to the Test Suite Agreement.

The Test Suite Agreement is between you and The Open Group. It defines the terms and conditions for free access to the test suite(s) required for product registration. A Test Suite Agreement is required for each product undergoing registration. The Test Suite Agreement is time-limited and valid for an initial period of 90-days. If during that time the product becomes a certified product then the license period extends to the period that the product remains a certified product.

Note: the Test Suite Agreement is a hardcopy document available from the Certification Authority once you have returned a Certification Agreement to enter the registration process. You must have it signed by an Authorized Signatory and then scanned and emailed back to The Open Group.

---

3. Product Registration

3.1 Optional Step - The Trademark License Agreement

Although not required for product certification in order to be listed on the public Certification Register, if you wish to use the POSIX trademark on or in connection with your product, or you need a formal certificate for your product (which carries the certification mark) then you must execute a POSIX Trademark License Agreement with the IEEE.

If applicable, we recommend you submit a completed POSIX Trademark License Agreement to the IEEE as early as possible in the process. You should download the TMLA from the link provided within the web certification system, and follow the instructions for submitting to the IEEE. Once you have submitted it to the IEEE you should inform the CA of the date of submittal. The CA will then be able to followup with IEEE to find out when the TMLA has been countersigned by them.

Note: For this version of the program, the POSIX trademark can be licensed for use with the 1003.1™-2016 Base Product Standard, the 1003.1™-2003 Base Product Standard, the PSE54 Multipurpose Realtime 1003.13-2003 System Product Standard, and the PSE52 Realtime Controller 1003.13-2003 System Product Standard.

3.2 The Conformance Statement

The next step is to complete a Conformance Statement to describe your product and how it meets the conformance requirements. If your product is being registered for multiple Product Standards you will need to complete a Conformance Statement for each Product Standard. Your Conformance Statement(s) will be linked into the Certification Register entry for the product once it is certified. A template Conformance Statement Questionnaire is available for each Product Standard from http://get.posixcertified.ieee.org/prodstandards.html.

The currently available Conformance Statement Questionnaires are:

• 1003.1™-2016 Base
• 1003.1™-2016 System Interfaces
• 1003.1™-2016 Shell and Utilities
• 1003.1™-2003 Base
• 1003.1™-2003 System Interfaces
• 1003.1™-2003 Shell and Utilities
• PSE54 Multipurpose Realtime 1003.13™-2003 System
• PSE52 Realtime Controller 1003.13™-2003 System

You must complete the relevant questionnaire to create a Conformance Statement for your product. See Sections 1.2, Section 2 and Section 3.3 of the Certification Policy for further information on the purpose of the Conformance Statement.

Conformance Statement Questionnaires are provided as html templates. You should download the template and edit the html, retaining the existing layout.  You must submit the completed Conformance Statement in html format to the Certification Authority. You can submit your Conformance Statement after you have created a company account and started product registration. Conversion to other formats besides html, or changes to the template in sections other than those allocated for Responses are not acceptable and will result in the Certification Authority rejecting your submission.

Conformance Statement Questionnaires have common frontmatter that ask for the following information about your company and the product that you are certifying:

• Submitter Information

  Your organization name and your name as the author of the conformance statement. The organization name must match that which has been entered in the web certification system.

• Product Information

  Enter the product name, version/release number or identifier, and product supplier for each product required to meet the conformance requirements. If more than one product is being registered to meet the Product Standard, please list the additional products, and extend the table if necessary. The product name and version information must match that which has been entered into the web certification system.

  If additional patches or specific package versions are required that are not included in the default product packaging for the version/release of the package declared, then such additional information needs to appear.

• Environment Specification

  Product registration applies to software products operating in a specific hardware or hardware/software environment. A product may be registered either as a single product, known as Platform Specific Certification, or as a family of binary-compatible products, known as Product Family Certification.

  In the case of Platform Specific Certification, registration is on the basis of a single test report. For Product Family Certification, sometimes two test reports from distinct members of the binary-compatible family are required (refer to the test campaign).

  You need to enter the level of Certification (Platform Specific or Product Family). If Product Family Certification then you need to enter a full description of the binary-compatible family covered by the certification. The term binary-compatible family is defined in the Certification Policy. Generally, this will be a range of machines for the same processor architecture, each capable of running the same software executables unchanged. If software has to be recompiled for a specific machine then it is not binary-compatible.

  You also need to provide the precise hardware/software environment (two environments for Product Family Certification) and test suite and version number with which your product's conformance has been demonstrated. Note that whether two results are required to be submitted depends on the test campaign.

The Conformance Statement Questionnaire also contains Product Standard specific questions that must be answered. Submission of the Conformance Statement occurs during the product registration process.

3.2.1 The POSIX Conformance Document

If you are certifying a product to the 1003.1™-2016 Base Product Standard, the 1003.1™-2003 Base Product Standard, the PSE54 Multipurpose Realtime 1003.13™-2003 System Product Standard or the PSE52 Realtime Controller 1003.13™-2003 System Product Standard then you need to produce and submit a POSIX Conformance Document (PCD) to the Certification Authority. This is a requirement from each of the standards, see IEEE Std 1003.1, Base Definitions Volume, Section 2.1.2 and IEEE Std 1003.13, Section 5, Conformance. Unlike the Conformance Statements, there is no prescribed format for the document. The Certification Authority requires it to be submitted during the product registration process in either text, html or Adobe PDF. Other formats such as wordprocessor or typesetter formats are not acceptable. To aid completion of the document templates are provided listing all the required sections to be addressed by the PCD for conformance.

3.3 Submitting Initial Certification Information

Applying for certification requires you to submit some initial information to the Certification Authority.  The initial submission involves completing a  Registration Form (including your company details and contact details),  and accepting the terms and conditions of the POSIX Certification program.

3.4 Registering your Product

When you register your product you are required to provide product details including the product name and version or release information for which conformance has been demonstrated.

You must enter the Product Standard that the product is being registered for on the registration. If a product is being registered against multiple Product Standards, you must submit separate forms. If you are registering the 1003.1™-2016 or 2003 Base Product Standard, you must also register or have previously registered the subsidiary Product Standards.

You must select the level of certification for the product. There are two levels defined:

• Platform Specific applies to a single defined hardware/software environment.
• Platform Family applies to all members of a binary compatible family. In this case test results from two distinct members of the binary compatible family may be required later in the registration process (see the test campaign).

If you wish to provide any notes to the CA about this registration you may do so on this form. Such notes are held confidential between you and the CA. You may also enter a URL for your product which would be presented on the Certification Register.

When submitting a product registration form, you must also submit a signed Certification Agreement in order to proceed with this product registration.

3.5 Submitting your Conformance Statement

The first document that you must submit is the Conformance Statement for your product (see section 3.2)

The next steps are to obtain the test suites, perform formal testing and then submit the test results as a sequence of files to the Certification Authority.

3.6 Obtaining the Test Suites

(This section is not applicable if you are registering a product against the PSE54 Multipurpose Realtime 1003.13-2003 System Product Standard.)

If you are not an existing test suite licensee, you can download the Test Suite Agreement, which must be completed in order to proceed with this product registration. This agreement must be signed by an Authorized Signatory. You must download the document and follow the instructions on its cover page which include where to fax the completed agreement. Once accepted you will be sent details of how to access the test suites.

3.7 Formal Testing for Certification

Formal testing is a self-test activity with results submitted to the Certification Authority for audit, by uploading through the certification system web site. At this point in time you need to make sure you understand the required test campaign, that is, which test suites are required to be used for certification testing (see Section 3.7.2 for details).  You also need to make sure that you have obtained a currently authorized version of the certification test suite(s) (see Section 3.1), since other versions will not be valid for formal testing.

You can obtain help and information as described in the Section 2.3, Informal Testing.

3.7.1 Test Journals

Test results submitted should always include the full journal output from an uninterrupted run of the applicable test suite. If this is not possible, a Problem Report must be raised stating the nature of the problem and you should wait for a response from the Certification Authority before proceeding further.

As part of certification you are required to upload test journals for each applicable test suite.

If there are failed test results then that you will need to resolve by referencing granted waivers.. If there are tests requiring manual resolution you need to resolve those also.

Failed Test Results and Problem Reporting

The failed test results in the test journal that require resolution are those with a status of FAIL, UNINITIATED, UNRESOLVED or NORESULT. The resolution process requires you to enter a valid reference to an approved Problem Report from the Problem Reporting database for each failed test case. An approved problem report is one which has resulted in an agreed Interpretation of the standard, a Test Suite Deficiency or a Certification System Deficiency. These apply to specific versions of a standard, test suite or certification system.

Problem Report IDs must be valid in order to complete the required data entry for this page. IDs have a format of TYPE.PX.NUMBER, where TYPE has the value INT, TSD or CSD (Interpretation, Test Suite Deficiency or Certification System Deficiency), PX is a fixed string, and NUMBER is a four digit decimal number. You must also check that the test suite version is valid for the Product Standard for all PR's referenced.

The test results in the journal that require manual resolution are denoted FIP (further information provided). The resolution process requires you to assert that the test case resolves to a PASS result for your system, and optionally to provide brief commentary. No reference is required to an approved problem report for FIP results.

3.7.2 Test Campaign Definition

For certification the required indicators of compliance are defined in the Product Standards. The test campaign associated with these including conformance statements and required test results are summarized below:

Product Standard	Test Campaign
1003.1™-2016/2003 Base	Completion of the  1003.1™-2016/2003 Base Conformance Statement Mandatory completion of the test campaign for the 1003.1™-2016/2003 System Interfaces , and the 1003.1™-2016/2003 Shell and Utilities Product Standards. Completion of a POSIX Conformance Document.
1003.1™-2016/2003 System Interfaces	Completion of the the 1003.1™-2016/2003 System Interfaces Conformance Statement Test Journal output (TET journal format required) from an uninterrupted run of the VSX-PCTS test suite For the test journal output, any FAIL, UNRESOLVED, NORESULT or UNINITIATED results need to be resolved by reference to associated granted interpretations, test suite deficiencies or certification system deficiences from the problem report database For the test journal output, any FIP results need to be manually resolved to a PASS result. Note that for Product Family Certification two sets of test results are required to be submitted in the system.
1003.1™-2016/2003 Shell and Utilities	Completion of the the 1003.1™-2016/2003 Shell and Utilities Conformance Statement Test Journal output (TET journal format required) from an uninterrupted run of the VSC-PCTS test suite For the test journal output, any FAIL, UNRESOLVED, NORESULT or UNINITIATED results need to be resolved by reference to associated granted interpretations, test suite deficiencies or certification system deficiences from the problem report database For the test journal output, any INSPECT results need to be manually resolved to a PASS result. Note that for Product Family Certification two sets of test results are required to be submitted in the system.
PSE54 Multipurpose Realtime 1003.13™-2003 System	Completion of the PSE54 Multipurpose Realtime 1003.13™-2003 System Conformance Statement For the POSIX_* Units of Functionality and POSIX.1 Option Requirements, Test Journal output (TET journal format required) from an uninterrupted run of the VSPSE54:2003 test suite in POSIX01 mode (it is optional whether results are submitted for POSIX Tracing.) For the XSI* Units of Functionality, Test Journal output (TET journal format required) from an uninterrupted run of the VSPSE54:2003 test suite in UNIX03 mode Test Journal output (TET journal format required) from an uninterrupted run of the VSC-PCTS test suite For each test journal output, any FAIL, UNRESOLVED, NORESULT or UNINITIATED results need to be resolved by reference to associated granted interpretations, test suite deficiencies or certification system deficiences from the problem report database For the test journal output, any INSPECT results need to be manually resolved to a PASS result. Completion of a POSIX Conformance Document in text, html or pdf.
PSE52 Realtime Controller 1003.13™-2003 System	Completion of the PSE52 Realtime Controller 1003.13™-2003 System Conformance Statement For the POSIX_* Units of Functionality and POSIX.1 Option Requirements, Test Journal output (TET journal format required) from an uninterrupted run of the VSPSE52:2003 test suite in PSE52P mode (it is optional whether results are submitted for POSIX Tracing.) For the XSI* Units of Functionality, Test Journal output (TET journal format required) from an uninterrupted run of the VSPSE52:2003 test suite in PSE52X mode For each test journal output, any FAIL, UNRESOLVED, NORESULT or UNINITIATED results need to be resolved by reference to associated granted interpretations, test suite deficiencies or certification system deficiences from the problem report database For the test journal output, any INSPECT results need to be manually resolved to a PASS result. Completion of a POSIX Conformance Document in text, html or pdf.

For initial certifications a complete run of the listed test tools is required for the product standards listed. For renewals and certification updates you should refer to section 4, Renewals and Product Updates for information on the applicable test campaigns.

3.8 The Final Step - Confirming your Submission & Payment

Once you have completed submission of all the required information, you must proceed with the payment or request it be placed on hold pending other registration activity (such as another Product Standard).

You should contact the Certification Authority to confirm the method of payment.

3.8.1 Payment

Payment is required to complete a full submission for registration. Payment may be either by credit card at the time of registration, or by purchase order, check or wire transfer received by the CA in advance of registration.

Note: The CA will not process the registration until payment has been received.

See http://get.posixcertified.ieee.org/docs/docs/posix-fee-schedule-1.3.PDF for the fee schedule. Please note that if you use a payment method other than by credit card, your submission cannot be processed until the payment is received by the Certification Authority.

3.8.2 Submission of Three Product Standards

If you are submitting for certification the three Product Standards required for the 1003.1™-2016 or 2003 Base Product Standard, you need to submit them at the same time.

3.9 Completion of Certification

If your submission is complete, you will be notified of successful certification within 6 business days.  If for any reason the submission was not complete, you will  be notified so that any corrections can be made and resubmitted. Such a resubmission needs to be done within one month unless an extension has been granted by the Certification Authority.  The initial fee covers one set of corrective actions.

The details of the certified product will then be put on the Certification Register, which is a public document, unless you have requested that it remains confidential. To keep the certification confidential, this option must be selected in the web certification system at the time the product is submitted.

When a product certification has been made public, if you are a trademark licensee then you will also be sent a certificate by electronic mail.

You should note that certification is valid for a defined period as stated in Section 8.1, Duration of Certification of the Certification Policy. At the end of that period, if you wish your product to remain certified you will need to renew your product's certification. (See Section 4 below for more information.)

For Product Standards, such as the 1003.1-2003 Base, that are built upon other Product Standards the following rules apply:

• If registration is occurring at the same time as the other Product Standard then the duration of certification is the shorter of the two defined durations.
• Otherwise, if the registration references a pre-existing Product Standard certification for the product then the duration for the additional Product Standard is to the end date associated with the existing certification.

3.10 Appeals Process

You may appeal decisions made by the IEEE or The Open Group Certification Authority as stated in Section 10, Appeals Process of the Certification Policy. Any request for appeal should be sent by electronic mail to the certification authority . Receipt of such a request will be acknowledged within 6 working days by the Certification Authority and the appeals process invoked.

---

4. Renewals and Certified Product Updates

4.1 The Renewals Process

A certified product has a defined period for its initial certification, after which it must be renewed or the product will no longer continue to be certified. Normally, this is one year from the date of initial certificaton.

When a renewal is due the Certification Authority will notify you around two months in advance using electronic mail (so it is important to maintain your contact information). At any time, you may send a request to the Certification Authority to obtain the renewal dates for your certified products.

Renewal implies that your product continues to conform and that you will continue to support your product for the duration of the renewal period.

Renewals are undertaken by contacting the Certification Authority.

You can then elect to renew for the next certification period or, at your option, elect for a shorter period.

4.1.1 Re-testing

You may be required to re-test your product. This depends on whether the Certification Authority is aware of any issues that would highlight the need to re-test. If you are required to re-test, the Certification Authority will confirm the re-test requirements and confirm how you should upload new test results for your product.

4.2 Certified Product Updates

If you make any changes to your certified product, you may be required to re-test or re-certify as required by Section 8, Certification Requirements of the Certification Policy. You should read that section thoroughly since it describes multiple scenarios related to product changes, some of which require a certification related activity.

In some cases a complete "Full certification" is required since the update is equivalent to a new product so far as certification is concerned. For example, if you took your product and moved it to another processor architecture which required a recompilation of the source code, even if your product requires no source code changes, this act of recompilation would constitute a major change and would require a Full certification.

4.2.1 Maintenance Releases

If the change to your product qualifies as a maintenance release (as defined in Section 8.3, Product Maintenance Releases of the Certification Policy) you are not required to contact the Certification Authority. However, please remember that accepting the Certification Agreement commits your company to provide a warranty of continued conformance. So we strongly recommend that you run the conformance tests regularly as quality-assurance tools every time you make a change.

You may request an update to your product's certification information to include the maintenance release. Depending on how you describe the maintenance release, this may be a wise thing to do so as to avoid marketplace confusion regarding which versions of your products are certified. Updates to a product's certification information for a maintainance release can be done by contacting the Certification Authority. The Certification Authority will change the product name on the Conformance Statement and in the Certification Register and issue a new certificate, if a certificate was previously issued.

4.2.2 Renaming a Product

If you wish to rename your product (as defined in Section 8.3, Renamed Products of the POSIX Certification Policy) then please contact the Certification Authority including the details of the required change and a written statement to the Certification Authority indicating that there have been no material changes to the certified product. The Certification Authority will change the product name on the Conformance Statement and in the Certification Register and issue a new certificate, if a certificate was previously issued.

If your product is a submission in progress and has not been submitted for audit to the Certificaton Authority, then renaming the product can be done using the web based certification system. Select the product that you wish to rename, the form with the product details including name and version will then presented for you to update. If you have submitted the product for audit please contact the Certification Authority.

4.2.3 Re-branding a Certified Product

If you wish to re-brand a product (as defined in Section 8.6, Re-branded products of the Certification Policy), locate and read the Conformance Statement for that product to obtain information on the product suppliers policy with respect to re-branding. First, you should find out whether you have the permission required for re-branding. Then proceed into the web based certification system as if you were certifying a new product, except that when you are asked to input information about the product you should select that this is a "Re-branded" product. You will then be presented with a web re-branded product form to complete.

The main difference between a "re-branded" product registration and a new product registration is that no test results are required to be submitted. Upon submission, the Certification Authority will verify that you have permission.

4.2.4 Other Scenarios

Other scenarios are considered as new products and subject to "Full certification" as described in Section 3 of this document.

5. Certification Checklist

The following checklist is provided to assist with completion of your product registration:

Understanding the certification program and process
	Have you read the Certification Policy? Have you read the applicable Product Standard(s)?
Informal Testing
	Have you identified the currently authorized test suites required for your product? Have you read the Certification frequently asked questions file? Have you completed your informal testing? Have you filed all the necessary Problem Reports?
Legal Agreements
	If you intend licensing the POSIX trademark, have you read the Trademark License Agreement? Have you read the Certification Agreement? Have you passed the above agreements to your legal representative?
Product Registration
	If an alternative payment method other than credit card is required for this registration, have you contacted The Certification Authority for more information? If you intend licensing the trademark, has the Trademark License Agreement been completed and submitted to the IEEE? Have you completed the Conformance Statement for your product? If applicable, have you completed the POSIX Conformance Document for your product? Have you completed and signed a Product Registration Form? Have you completed and signed a Certification Agreement? Have you uploaded the Conformance Statement(s) for your product? Have you identified the formal test campaign  required for your product and obtained the currently authorized test suites? Have you completed Formal testing of your product? Have you uploaded the Formal test results ? Have you resolved all non-PASS results by references to Problem Reports resulting in agreed Interpretations or Test Suite Deficiencies? Have you submitted the Formal test results ? Have you resolved all non-PASS results by references to Problem Reports resulting in agreed Interpretations or Test Suite Deficiencies? Have you resolved any FIP or INSPECT results manually? If you require the registration to be kept confidential, have you confirmed that on the registration form?