5 Part 3 Other API marking controls In some cases, there may be instances where other marking controls may be used. These controls are subject to API licensing requirements, API Q1 specification, and other API specifications and requirements. General 1. In the event that an API monogram is to be placed in a location not specified in the API License Agreement, Licensees must notify the API in advance in writing and obtain API approval prior to labeling. Prior to labelling, the licensee enters into an agreement with each labeling party that ensures quality control of the labeling process, and all labeling parties must obtain API approval. (2) All entities involved in a Monogram API Alternative Marking Agreement are subject to API verification at the DISCRETION of the API. 3. API reserves the right to require more frequent audits (at Licensee`s expense) for Licensees with an approved API Monogram Alternative Marking Agreement. 4. API reserves the right to have a representative present at any location when the API monogram is applied. 5.
API reserves the right to refuse or revoke the rights granted under alternative labelling agreements if adequate quality control of the labelling process cannot be demonstrated or maintained by the licensee and/or the labeling party. The Eligible Processes and Products API has found that it can ensure that finished products meet API specifications while meeting the proven need for flexibility in certain circumstances. In some cases, other labelling procedures and controls may be developed and deemed acceptable for specific manufacturing processes or product types. The current processes and products eligible for the API of the Monogram Alternative Marking Agreement are listed in Tables 1 to 3. The points listed are the minimum controls that must be defined and documented by the licensee. Additional controls may be required by the API prior to approval. Applications to apply this alternative labelling program to other product lines will be reviewed and evaluated by API on a case-by-case basis. The API requires support for each request in the form of: (1) documentation of a genuine need for such a labeling program and (2) proof that the original licensee can ensure that the new product meets the API specifications. Contractual relations 1. General: Any company that applies the API (Marking Party) monogram to eligible products must have a contractual agreement with API and the original licensee. There shall be no assignment or delegation of API license rights or responsibilities from the original licensee to the marking part. 2.
Monogram API License Agreement: The Monogram API License Agreement is an agreement between API and Licensee that grants a Licensee, among other things, the right to apply MONOGRAM API to products that meet API product specification requirements and that have been manufactured as part of a quality management system that complies with the API Q1 specification. 3. Labeling Agreement: If the API monogram is applied by a party other than the original API licensee or in an installation not specified in the original API license, as in a scenario described in the following table, the marking party enters into a contractual agreement with the original API licensee that ensures that the final products meet the appropriate API specifications. The characterizing party must also obtain an alternative API monogram marking agreement before marking a product with the Monogram API. 4. Licensee`s Liability: Api Licensee is responsible for any end product that meets an applicable API specification, including any labeling requirements. The identification party is responsible for maintaining sufficient controls to ensure that products marked with the API monogram meet all applicable API product specifications. CONTINUATION >> REVISION 3 FM-011.pdf PAGE 1 OF 2 4 Part 2 GENERAL REQUIREMENTS FOR THE MARKING OF THE API MONOGRAM Each licensee shall control the application of the API monogram in accordance with the following provisions: 1. Each licensee shall develop and maintain an API monogram marking method that documents the labelling/monogram requirements set out in the API product specification that will be used for the application by the licensee of the API monogram duty. The labelling procedure shall determine the place(s) where the licensee applies the API monogram and shall require that the licensee`s licence number and date of manufacture be indicated on the monogrammed products in conjunction with the API monogram. The date of manufacture shall consist of at least two digits representing the month and two digits representing the year (e.B. for May 2008), unless otherwise specified in the applicable API specifications.
If the API product specification does not contain labelling requirements, the licensee shall determine where this information will be used in the labelling process. 2. The API monogram may be affixed at any time during the production process (provided that the product remains under the licensee`s control), but must be removed in accordance with the Licensee`s API monogram marking process if it is later found that the product does not meet the requirements specified by the API. Products that do not meet the requirements specified by the API must not carry the API monogram. 3. Except as described in Part 3 of this document, only an API Licensee may apply the API Monogram and its License Number to products eligible for the API Monogram and the API Monogram may only be applied in the Licensed Entity. 4. The authority responsible for the application and removal of the API monogram shall be determined in the licensee`s API monogram identification procedure. REVISION 3 FM-011.pdf PAGE 1 OF 1 Api Terms of Use Shutterfly Open Shutterfly is proud to introduce the Shutterfly Open API, our collection of application programming interfaces that enable the licensee (you or 3 Part 1) The API monogram program allows an API licensee to apply the API monogram to applicable products that fall within the scope of the program.
The use of the API monogram on these Products constitutes an assurance and warranty by Licensee to purchasers of the Products that the Products have been manufactured on the specified date under a verified quality management system and in accordance with the API Product Specifications in effect at the time of manufacture. Licenses to the Monogram API Program will only be granted after an on-site audit has confirmed that Licensee has demonstrated at all times that it meets the requirements described in api specification Q1 and has demonstrated its ability to meet the requirements of the applicable API Product Specifications and the Monogram API License Agreement. The purpose of this document is to establish requirements for the application of the API monogram to the appropriate products. API holds all rights to the certification mark (hereinafter the API monogram) in connection with the API monogram program. In accordance with the terms of the Monogram API License Agreement, API grants Licensee a non-exclusive, non-transferable license to use Monogram Api for the product types specified in the Certificate of Authorization to Use the Official API Monogram, provided that such products are manufactured in accordance with the requirements of the API Product Specification in effect at the time of manufacture in conjunction with the assigned license number. API Q1 specification, specification for quality programs for the petroleum, petrochemical and natural gas industries and requirements for the API monogram program, including any changes, modifications, substitutions or interpretations. The Agreement applies only to licensee`s products manufactured in licensee`s facilities under the controls specified in the labeling procedures developed and maintained by licensee. However, API recognizes that there are certain manufacturing processes or product types that may lend themselves to other api monogram labeling procedures and controls.
In particular, there may be cases where a licensee wants the API monogram and its license number to be applied in a location (installation) other than that covered by the corresponding API license. .
