<?xml version="1.0" encoding="UTF-8"?>
<?asciidoc-toc?>
<?asciidoc-numbered maxdepth="6"?>
<book xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:lang="en">
<info>
<title>AME Scroll Standards</title>
<date>2015-09-28</date>
<author>
<personname>
<firstname>AME Scroll Standards Team</firstname>
</personname>
</author>
<authorinitials>A</authorinitials>
</info>
<chapter xml:id="_part_numbers">
<title>Part Numbers</title>
<section xml:id="_scope">
<title>Scope</title>
<simpara>The purpose of this technical procedure is to advise and document when and how to assign a new AME scroll machining part number.</simpara>
</section>
<section xml:id="_responsibility">
<title>Responsibility</title>
<simpara>The responsibility of executing this procedure belongs to the designer creating the part.</simpara>
</section>
<section xml:id="_procedure">
<title>Procedure</title>
<section xml:id="_when_to_assign_a_new_number">
<title>When To Assign A New Number</title>
<section xml:id="_all_production_parts_should_receive_an_ames_part_number">
<title>All production parts should receive an AMES part number.</title>
<section xml:id="_production_part_numbers_should_be_used_whenever_a_component_is_intended_to_be_used_in_a_production_environment">
<title>Production part numbers should be used whenever a component is intended to be used in a production environment.</title>

</section>
<section xml:id="_if_you_are_using_a_model_of_a_purchased_component_you_should_still_give_that_part_an_ames_number_and_note_the_manufacturer_and_manufacturer_part_number_in_the_part_model_parameters">
<title>If you are using a model of a purchased component, you should still give that part an AMES number and note the manufacturer and manufacturer part number in the part model parameters.</title>

</section>
<section xml:id="_examples_of_where_you_would_assign_an_ames_part_number">
<title>Examples of where you would assign an AMES part number:</title>
<section xml:id="_designing_a_new_polishing_fixture_for_a_scroll_that_is_limited_released">
<title>Designing a new polishing fixture for a scroll that is "Limited" released</title>

</section>
<section xml:id="_using_a_purchased_part_from_mcmaster_carr_in_an_assembly">
<title>Using a purchased part from McMaster-Carr in an assembly</title>

</section>
<section xml:id="_model_from_a_chuck_supplier_that_you_want_in_teamcenter">
<title>Model from a chuck supplier that you want in Teamcenter</title>

</section>
</section>
</section>
<section xml:id="_conceptual_parts_do_not_require_an_ames_number">
<title>Conceptual parts do NOT require an AMES number</title>
<section xml:id="_conceptual_part_numbers_should_be_used_when_the_model_print_being_generated_is_not_intended_to_be_ready_for_production_use">
<title>Conceptual part numbers should be used when the model/print being generated is not intended to be ready for production use.</title>

</section>
<section xml:id="_a_conceptual_part_number_should_never_be_used_in_a_production_environment">
<title>A conceptual part number should never be used in a production environment.</title>

</section>
<section xml:id="_if_you_want_to_use_an_existing_conceptual_part_in_production_you_should_assign_that_part_an_ames_number_and_clone_the_conceptual_part">
<title>If you want to use an existing conceptual part in production, you should assign that part an AMES number and clone the conceptual part.</title>
<section xml:id="__emphasis_role_strong_note_emphasis_after_cloning_the_concept_part_number_will_still_exist">
<title><emphasis role="strong">NOTE:</emphasis> After cloning, the concept part number will still exist</title>

</section>
</section>
<section xml:id="_it_is_ok_to_generate_conceptual_part_number_prints_and_sent_them_out_to_quote_however_it_should_only_be_used_for_non_production_purposes">
<title>It is OK to generate conceptual part number prints and sent them out to quote. However, it should only be used for non-production purposes.</title>

</section>
<section xml:id="_examples_of_where_you_would_assign_a_concept_part_number">
<title>Examples of where you would assign a concept part number:</title>
<section xml:id="_you_need_a_dummy_model_for_a_simulation_that_will_serve_as_a_visual_representation">
<title>You need a "dummy" model for a simulation that will serve as a visual representation</title>

</section>
<section xml:id="_you_are_designing_platforms_for_an_operator_to_stand_on_and_you_want_to_quote_several_different_options_to_evaluate_cost">
<title>You are designing platforms for an operator to stand on and you want to quote several different options to evaluate cost.</title>

</section>
<section xml:id="_you_need_to_design_a_temporary_fixture_to_machine_some_prototype_scrolls">
<title>You need to design a temporary fixture to machine some prototype scrolls</title>

</section>
</section>
</section>
<section xml:id="_regardless_if_you_are_using_a_conceptual_or_production_part_number_if_you_create_a_pdf_or_dwg_and_deliver_it_to_someone_for_quoting_or_other_purposes_final_status_that_part_before_sending_it_out">
<title>Regardless if you are using a conceptual or production part number, if you create a PDF or DWG and deliver it to someone for quoting or other purposes "Final" status that part BEFORE sending it out.</title>
<section xml:id="_if_a_change_is_made_after_sending_a_part_out_it_should_be_revised_and_the_changes_noted">
<title>If a change is made after sending a part out, it should be revised and the changes noted.</title>

</section>
<section xml:id="_it_is_up_to_the_owning_user_to_maintain_revision_control_on_created_drawings">
<title>It is up to the owning user to maintain revision control on created drawings.</title>

</section>
</section>
<section xml:id="_a_part_number_should_be_assigned_prior_to_the_start_of_modeling_or_before_cloning_an_existing_component">
<title>A part number should be assigned prior to the start of modeling or before cloning an existing component</title>

</section>
<section xml:id="_both_concept_and_production_part_numbers_should_be_created_and_stored_within_teamcenter">
<title>Both concept and production part numbers should be created and stored within Teamcenter.</title>

</section>
</section>
<section xml:id="_before_assigning_a_production_part_number">
<title>Before Assigning A Production Part Number</title>
<section xml:id="_verify_that_the_part_does_not_already_exist_this_could_be_done_either_by_using_the_search_functions_within_teamcenter_or_downloading_a_gdpns_link_xlink_href_http_gdpns_emersonclimate_com_http_gdpns_emersonclimate_com_link_search_to_excel_and_using_the_find_command">
<title>Verify that the part does not already exist. This could be done either by using the search functions within Teamcenter or downloading a GDPNS (<link xlink:href="http://gdpns.emersonclimate.com/">http://gdpns.emersonclimate.com/</link>) search to Excel and using the "Find" command.</title>
<section xml:id="_if_the_part_that_you_need_already_exists_do_not_assign_a_new_number_duplicate_numbers_of_the_same_part_should_always_be_avoided">
<title>If the part that you need already exists, DO NOT assign a new number. Duplicate numbers of the same part should always be avoided.</title>

</section>
<section xml:id="_if_the_part_already_exists_in_teamcenter_in_a_different_cad_system_than_what_you_are_currently_using_then_you_should_create_a_new_revision_for_the_cad_system_you_are_using_under_the_same_item_id_do_not_create_a_new_item_id_number">
<title>If the part already exists in Teamcenter in a different CAD system than what you are currently using, then you should create a new revision for the CAD system you are using under the same Item ID. Do not create a new Item ID number.</title>

</section>
</section>
</section>
<section xml:id="_production_part_number_nomenclature">
<title>Production Part Number Nomenclature</title>
<section xml:id="_the_part_number_consists_of_13_characters_it_is_divided_into_separate_clusters_of_numbers_by_dashes">
<title>The part number consists of 13 characters. It is divided into separate clusters of numbers by dashes.</title>
<itemizedlist>
<listitem>
<simpara>Example: AMES<emphasis role="strong">-</emphasis>###<emphasis role="strong">-</emphasis>X###<emphasis role="strong">-</emphasis>##</simpara>
</listitem>
</itemizedlist>
<informaltable frame="all" rowsep="1" colsep="1">
<tgroup cols="4">
<colspec colname="col_1" colwidth="25*"/>
<colspec colname="col_2" colwidth="25*"/>
<colspec colname="col_3" colwidth="25*"/>
<colspec colname="col_4" colwidth="25*"/>
<tbody>
<row>
<entry align="left" valign="top"></entry>
<entry align="left" valign="top"><simpara>Cluster 1</simpara></entry>
<entry align="left" valign="top"><simpara>Cluster 2</simpara></entry>
<entry align="left" valign="top"><simpara>Cluster 3</simpara></entry>
</row>
<row>
<entry align="left" valign="top"><simpara>AMES</simpara></entry>
<entry align="left" valign="top"><simpara>###</simpara></entry>
<entry align="left" valign="top"><simpara>X###</simpara></entry>
<entry align="left" valign="top"><simpara>##</simpara></entry>
</row>
</tbody>
</tgroup>
</informaltable>
</section>
<section xml:id="_cluster_1_indicates_the_type_type_of_part">
<title>Cluster 1 (###) - Indicates the type type of part</title>
<informaltable frame="all" rowsep="1" colsep="1">
<tgroup cols="2">
<colspec colname="col_1" colwidth="50*"/>
<colspec colname="col_2" colwidth="50*"/>
<tbody>
<row>
<entry align="left" valign="top"><simpara><emphasis role="strong">Value(s)</emphasis></simpara></entry>
<entry align="left" valign="top"><simpara><emphasis role="strong">Type</emphasis></simpara></entry>
</row>
<row>
<entry align="left" valign="top"><simpara>201-288</simpara></entry>
<entry align="left" valign="top"><simpara>Assembly, Sub-Assembly, and Component Parts</simpara></entry>
</row>
<row>
<entry align="left" valign="top"><simpara>289</simpara></entry>
<entry align="left" valign="top"><simpara>Templates</simpara></entry>
</row>
<row>
<entry align="left" valign="top"><simpara>290</simpara></entry>
<entry align="left" valign="top"><simpara>Plant Level Drawings</simpara></entry>
</row>
<row>
<entry align="left" valign="top"><simpara>291</simpara></entry>
<entry align="left" valign="top"><simpara>Cell Level Drawings</simpara></entry>
</row>
<row>
<entry align="left" valign="top"><simpara>292</simpara></entry>
<entry align="left" valign="top"><simpara>System Level Drawings</simpara></entry>
</row>
</tbody>
</tgroup>
</informaltable>
<section xml:id="_please_reference_document_xxxx_for_assigning_the_correct_cluster_1_number">
<title>Please reference Document XXXX for assigning the correct "Cluster 1" number</title>

</section>
<section xml:id="_if_you_feel_the_need_to_add_a_new_cluster_1_number_please_contact_members_of_the_standards_team_with_your_need_and_reason_for_the_addition">
<title>If you feel the need to add a new "Cluster 1" number, please contact members of the standards team with your need and reason for the addition.</title>

</section>
</section>
<section xml:id="_cluster_2_x">
<title>Cluster 2 (X###)</title>
<section xml:id="_the_first_character_x_of_this_series_is_an_alpha_character_that_further_defines_the_cluster_1_series_into_a_sub_series">
<title>The first character (X) of this series is an alpha character that further defines the "Cluster 1" series into a Sub-Series</title>

</section>
<section xml:id="_the_next_three_digits_are_assigned_in_sequential_order_of_the_next_available_number">
<title>The next three digits are assigned in sequential order of the next available number.</title>

</section>
<section xml:id="_please_reference_document_xxxx_for_assigning_the_correct_cluster_2_alpha_character">
<title>Please reference Document XXXX for assigning the correct "Cluster 2" alpha character</title>

</section>
<section xml:id="_if_you_feel_you_need_to_add_a_new_cluster_2_alpha_character_please_contact_a_member_of_the_standards_team_with_your_need_and_reason_for_the_addition">
<title>If you feel you need to add a new "Cluster 2" alpha character, please contact a member of the standards team with your need and reason for the addition.</title>

</section>
</section>
<section xml:id="_cluster_3">
<title>Cluster 3 (##)</title>
<section xml:id="_these_digits_range_from_00_69_and_further_define_the_cluster_2_part_number_although_not_commonly_used_in_scroll_machining_numbers_greater_than_69_have_specific_meanings_in_other_departments_within_emerson_climate_technologies_and_should_not_be_used_in_scroll_machining">
<title>These digits range from 00-69 and further define the "Cluster 2" part number. Although not commonly used in scroll machining, numbers greater than 69 have specific meanings in other departments within Emerson Climate Technologies and should not be used in scroll machining.</title>

</section>
<section xml:id="_see_appendix_a_for_a_list_of_available_cluster_1_and_cluster_2_alpha_numbers">
<title>See Appendix A for a list of available "Cluster 1" and "Cluster 2" alpha numbers.</title>

</section>
<section xml:id="_generally_speaking_the_00_should_be_the_assembly_and_01_02_03_etc_would_be_component_parts_of_the_assembly">
<title>Generally speaking, the 00 should be the assembly, and 01, 02, 03, etc. would be component parts of the assembly.</title>

</section>
</section>
</section>
<section xml:id="_how_to_reserve_a_new_production_part_number">
<title>How To Reserve A New Production Part Number</title>
<section xml:id="_all_new_part_numbers_are_reserved_via_gdpns_link_xlink_href_http_gdpns_emersonclimate_com_http_gdpns_emersonclimate_com_link">
<title>All new part numbers are reserved via GDPNS (<link xlink:href="http://gdpns.emersonclimate.com/">http://gdpns.emersonclimate.com/</link>)</title>

</section>
<section xml:id="_if_you_do_not_have_a_gdpns_account_please_contact_the_gdpns_coordinator_curently_mary_ubach">
<title>If you do not have a GDPNS account, please contact the GDPNS coordinator. (Curently Mary Ubach)</title>

</section>
<section xml:id="_prior_to_assigning_a_number_you_need_to_determine_if_it_will_be_created_as_a_new_part_number_series_cluster_2_or_as_a_new_dash_number_cluster_3">
<title>Prior to assigning a number, you need to determine if it will be created as a new part number series (Cluster 2), or as a new dash number (Cluster 3).</title>

</section>
<section xml:id="_when_reserving_a_new_part_number_series_or_dash_number_you_will_be_asked_to_fill_in_the_required_information">
<title>When reserving a new part number series or dash number, you will be asked to fill in the required information.</title>
<section xml:id="_title_required_this_field_should_match_the_part_name_of_the_component">
<title>Title - (Required) - This field should match the "Part Name" of the component</title>

</section>
<section xml:id="_description_required_this_field_should_match_the_part_description_of_the_component_it_should_contain_more_detail_than_what_was_entered_for_the_title">
<title>Description - (Required) - This field should match the "Part Description" of the component. It should contain more detail than what was entered for the "Title".</title>
<section xml:id="_if_the_component_you_are_creating_a_new_part_number_for_is_a_purchased_part_the_manufacturer_and_the_manufacturer_part_number_should_be_included_in_the_description_field">
<title>If the component you are creating a new part number for is a purchased part, the manufacturer and the manufacturer part number should be included in the description field.</title>

</section>
</section>
<section xml:id="_reference_not_required_this_field_is_not_used_by_scroll_machining_and_should_be_left_blank">
<title>Reference - (Not Required) - This field is not used by Scroll Machining and should be left blank</title>

</section>
<section xml:id="_cad_system_required_this_specifies_the_cad_software_that_the_component_is_modeled_in">
<title>CAD System - (Required) - This specifies the CAD software that the component is modeled in.</title>

</section>
<section xml:id="_layout_reference_not_required_this_field_is_not_used_by_scroll_machining_and_should_be_left_blank">
<title>Layout Reference - (Not Required) - This field is not used by Scroll Machining and should be left blank.</title>

</section>
</section>
</section>
<section xml:id="_how_to_reserve_a_new_concept_part_number">
<title>How To Reserve A New Concept Part Number</title>
<section xml:id="_a_new_concept_part_number_will_be_generated_by_teamcenter_when_the_concept_part_is_created">
<title>A new concept part number will be generated by Teamcenter when the concept part is created.</title>
<section xml:id="_when_you_create_a_new_model_in_nx_next_to_the_number_field_there_is_an_assign_button_that_should_be_used_to_generate_a_new_6_digit_concept_part_number">
<title>When you create a new model in NX, next to the number field there is an "Assign" button that should be used to generate a new 6-digit concept part number.</title>

</section>
<section xml:id="_after_assigning_the_new_part_number_be_sure_to_assign_an_appropriate_item_name_and_000_for_the_revision">
<title>After assigning the new part number, be sure to assign an appropriate Item Name and "000" for the Revision.</title>

</section>
<section xml:id="_naming_key_concept_parts_will_be_assigned_a_unique_6_digit_number_numbers_are_assigned_by_teamcenter">
<title>Naming Key: Concept parts will be assigned a unique 6 digit number. Numbers are assigned by Teamcenter.</title>

</section>
<section xml:id="_the_same_model_rules_as_production_parts_will_apply_with_ip_classification_being_the_only_required_field">
<title>The same model rules as production parts will apply with "IP Classification" being the only required field.</title>
<section xml:id="__emphasis_role_strong_note_emphasis_because_the_concept_part_number_has_no_intelligence_filling_in_the_item_name_and_description_fields_for_concept_parts_is_important_so_that_users_can_use_these_field_s_values_to_search_for_them_in_teamcenter">
<title><emphasis role="strong">Note:</emphasis> Because the concept part number has no intelligence, filling in the "Item Name" and "Description" fields for concept parts is important so that users can use these field&#8217;s values to search for them in Teamcenter.</title>

</section>
<section xml:id="__emphasis_role_strong_note_emphasis_creating_a_folder_structure_inside_your_teamcenter_new_stuff_folder_is_recommended_to_keep_projects_together">
<title><emphasis role="strong">Note:</emphasis> Creating a folder structure inside your Teamcenter "New Stuff" folder is recommended to keep projects together.</title>

</section>
</section>
</section>
</section>
</section>
</chapter>
</book>