1. Annex J Single-designation of Documents

2. Action Item (TSSC, Apr. 24) Single Designation Numbering and Annex J – Herb reported that the original Annex J revision was approved by the TSSC and implemented by TIA Staff with no record of TC ballot, TC approval or ANSI notification. Recognizing that the TSSC-approved version is dated and in need of some updates already discussed, it was proposed that the process start from scratch with a new revision to Annex J. Document -021 has a summary of the situation. Document - 022 is a “clean” version of the revision for TSSC review and comment. To facilitate the discussion, document -026 is a “red-line” version of the original and document -027 is the original (as approved by the TSSC). ACTION: Herb Congdon will coordinate a conference call for interested participants to review these Annex J contributions and other contributions from Engineering Committees in the latter part of May. Jane Brownley requested that TR-45 be included on the invitation. – TSSC-2012Apr24-029d_Meeting_Report

3. Situational Summary (TSSC-2012Apr24-021b_Annex_J_Revision_Proposal_Cover) It is noted that the ANSI Essential Requirements, in Section 4.4 (www.ansi.org/essentialrequirements/ ), state:www.ansi.org/essentialrequirements/ – “… American National Standards shall be identified by a unique alphanumeric designation (e.g., ANSI/ASD 123- 2004). Multiple designations should be avoided. If a standard has multiple designations, an attempt shall be made by those concerned to arrive at a single designation...” Further, it is noted that ANSI noticed our non-compliance with respect to double-designation numbering. Accordingly, TIA Standards Secretariat proposed changes (TSSC- 20101027-005r1) to Annex J which were approved by the TSSC on Wednesday, October 27, 2010 (TSSC-20110315-002). These changes were implemented by TIA Standards Secretariat in January 2011.

4. Situational Summary (TSSC-2012Apr24-021b_Annex_J_Revision_Proposal_Cover) Further, it is now noted in Clause 14, Changes to the TIA Engineering Manual, of the TIA Engineering Manual (5th Edition) that: – “This proposed text for updating the Manual or an Advisory Note shall then be circulated among members of the TSSC for comments and suggestions and balloted within the Technical Committee to achieve approval of the revised text. Upon such approval, the updated Manual or the Advisory Note shall be effective within TIA and sent to ANSI for its review.”

5. Situational Summary (TSSC-2012Apr24-021b_Annex_J_Revision_Proposal_Cover) A subsequent review of the meeting report from the Technical Committee meeting on Thursday, October 28, 2010 (TC-20110316- 002) shows only the following: – “The TSSC also discussed a series of administrative changes and improvements implemented by the standards Secretariat staff including the development of a new TIA document numbering system.”

6. Situational Summary (TSSC-2012Apr24-021b_Annex_J_Revision_Proposal_Cover) With no evidence that the Technical Committee balloted or achieved approval for the revised text in TSSC-20101027-005r1, nor that any revised text was sent to ANSI, TIA Standards Secretariat proposes a new revision to Annex J that represents the current practice already implemented and requests circulation among the TSSC for comments and suggestions in preparation for balloting and approval in the Technical Committee.

7. Situational Summary (TSSC-2012Apr24-021b_Annex_J_Revision_Proposal_Cover) Four contributions were provided to the TSSC in support of this proposal: 1.This letter from TIA Standards Secretariat TSSC-2012Apr24-021b_Annex_J_Revision_Proposal_Cover 2.A clean version of the proposed new Annex J revision TSSC-2012Apr24-022_Annex_J_New_Revision_Proposal_Clean 3.A “red-lined” version of the original revision as approved by the TSSC TSSC-2012Apr24-026_Annex_J_New_Revision_Proposal_Redline 4.A clean version of the original revision as approved by the TSSC (TSSC-20101027-005r1) TSSC-2012Apr24-027_Annex_J_Revision_Original_Approved_by_TSSC

8. Key Questions

9. Wouldn’t we want to be compliant with ANSI Essential Requirements and retain ANSI accreditation? Wouldn’t we rather operate using a single- designation rather than a double-designation? – Imagine the reverse - if we were using single- designation and told to go to double-designation

10. Definitions

11. For consistency in this discussion: – Document Number – the base three or four digit number of the published standard Ex: the “1234” in ANSI/TIA-1234-B-2 The document number is consistent through the life of the document – Published Standard Number – the complete alphanumeric designator of the published standard including year of publication Ex: ANSI/TIA-1234-B-2-2011 – Project Number – the project identifier, which contains “PN” and the document number Ex: TIA-PN-1234-B-2 a.k.a. “single-designation project number” Note: TIA is no longer using “SP”, only “PN” – Double-designation Project Number – a project number, assigned before single-designation project numbering, with a different base three or four digit number than the document number Ex: TIA-PN-4321-B-2 for document number “1234”

12. TR-45 Comments Those Related to Support of Annex J

13. TR-45 Summary of Comments - 1 (TSSC-2012Apr24-031_TR-45_Correspondence_to_TIA_on_Doc_Numbering) Only completely new projects should be assigned numbers using single-designation numbering – Legacy documents should retain the double-designation project number and document numbers, as they evolve through addenda, revisions, and reaffirmations When a multi-part document is updated, the updated project should retain the original project number unless all parts are being updated simultaneously TIA Comments – Unfortunately, these positions are not in compliance with ANSI Essential Requirements – Use of double-designation for reference in Engineering Committees is allowed

14. TR-45 Summary of Comments - 2 (TSSC-2012Apr24-031_TR-45_Correspondence_to_TIA_on_Doc_Numbering) Changes to the numbering nomenclature of legacy documents would: – Cause undue confusion internally and externally – Result in an excessive administrative burden – Increase the complexity of tracking and maintaining the documents over time – Result in a loss of familiarity with the individual specifications over time

15. TR-45 Summary of Comments - 2 (TSSC-2012Apr24-031_TR-45_Correspondence_to_TIA_on_Doc_Numbering) TIA Comments – Many of these issues are because of the complexities inherent with double-designation – TIA recognizes the potential for confusion during the migration process – That migration process is basically well underway (since January 2011) – On many levels, operating with single-designation will prove to be less confusing, simpler, and more recognizable than double-designation

16. TR-45 Summary of Comments - 3 (TSSC-2012Apr24-031_TR-45_Correspondence_to_TIA_on_Doc_Numbering) Annex J does not address joint (J-STD) standards (i.e., both TIA and ANSI J-STD standards.) Annex J does not address “enhanced addenda” nomenclature TIA Comments – TIA agrees that adding content for J-STD (TIA and ANSI) would be an important improvement to the proposal and has added content – TIA notes that “enhanced addenda” are not defined in the Engineering Manual, so referring to them in Annex J is problematic TIA proposes to refer to these as “Revision with Change Marks as Addendum” Examples for Revisions with Change Marks as Addendum have been added to the proposal

17. TR-45 Summary of Comments - 4 (TSSC-2012Apr24-031_TR-45_Correspondence_to_TIA_on_Doc_Numbering) Documents with existing references to double- designation project numbers (PNs or SPs) would not be accurate TIA Comments: – This is also a consequence of double-designation – A single-designation positively improves this situation as every document becomes identifiable by it’s document number moving forward – TIA will continue to maintain associations between old project numbers and the document number to address any searches or requests for older documents during the migration and after – Staff can assist

18. TR-45 Summary of Comments – 5 (TSSC-2012Apr24-031_TR-45_Correspondence_to_TIA_on_Doc_Numbering) Not all parts in an update package would have the same PN number TIA Comments – This, too, appears to be a consequence of double- designation – A single-designation positively improves this situation as every document becomes identifiable by it’s document number moving forward – All new projects in an update package will have its recognizable document number

19. TR-45 Summary of Comments - 6 (TSSC-2012Apr24-031_TR-45_Correspondence_to_TIA_on_Doc_Numbering) Trying to keep track of older material through these changes will be even more complex if the tracking numbers are modified in the middle of the life cycle TIA Comments – This, again, appears to be a consequence of double- designation – A single-designation positively improves this situation as every document becomes identifiable by it’s document number moving forward – Engineering Committees may still refer to the double- designation project numbers

20. TR-45 Summary of Comments - 7 (TSSC-2012Apr24-031_TR-45_Correspondence_to_TIA_on_Doc_Numbering) Moving forward TR-45.3 wishes to retain the “hyphens” only TIA Comment – a note in the proposed Annex J indicates that published standard numbers will retain the same format with respect to dots and dashes

21. TR-45 Summary of Comments - 8 (TSSC-2012Apr24-031_TR-45_Correspondence_to_TIA_on_Doc_Numbering) Reaffirmation ballots will use the new numbering schemes (not the old project number). This means legacy documents reaching the reaffirmation stage will have their double-designation changed to single- designation, requiring additional administration/coordination between standards.

22. TR-45 Summary of Comments - 8 (TSSC-2012Apr24-031_TR-45_Correspondence_to_TIA_on_Doc_Numbering) TIA Comments – A note in the Engineering Manual indicates that the project numbers for reaffirmation ballots “shall” be the double-designation project numbers – ANSI has admitted, in their review of this matter, that the content in the Engineering Manual on reaffirmations violates their requirements and should not have been approved by ANSI – Separately, an Advisory Note to change the Engineering Manual is being prepared – Reaffirmation ballots will use single-designation

23. Proposed Annex J

24. Proposed Annex J (Changes Highlighted) (TSSC-2012Jul31-006b_Annex_J_New_Revision_Proposal_Clean) TIA (only) Documents for Document Number 1234 Project Number (PN)ExplanationPublished Standard Number TIA-PN-12341 st (Letter) BallotTIA-1234- TIA-PN-1234-D11 st Default Ballot, subsequent default ballots are designated in a numerical, sequential manner (e.g., TIA-PN-1234-D2) TIA-1234- TIA-PN-1234-R11 st Re-Ballot, subsequent re-ballots are designated in a numerical, sequential manner (e.g., TIA-PN-1234-R2) TIA-1234- TIA-PN-1234-1Addendum 1 to TIA-1234TIA-1234-1- TIA-PN-1234-2Addendum 2 to TIA-1234TIA-1234-2- TIA-PN-1234-ARevision 1 of TIA-1234TIA-1234-A- TIA-PN-1234-BRevision 2 of TIA-1234TIA-1234-B- TIA-PN-1234-A-1Addendum 1 to TIA-1234-ATIA-1234-A-1- TIA-PN-1234-A-2Addendum 2 to TIA-1234-ATIA-1234-A-2- TIA-PN-1234-B-1Addendum 1 to TIA-1234-BTIA-1234-B-1- TIA-PN-1234-B-2Addendum 2 to TIA-1234-BTIA-1234-B-2- TIA-PN-1234-B-3 [E]Revision with Change Marks as Addendum 3 to TIA-1234-B TIA-1234-B-3-[E]- TIA-PN-1234.001Part/chapter 1 of TIA-PN-TIA-1234TIA-1234.001- TIA-PN-1234-RF11 st Re-affirmation of TIA-1234TIA-1234- (R) (see note 1)

25. Proposed Annex J (Changes Highlighted) (TSSC-2012Jul31-006b_Annex_J_New_Revision_Proposal_Clean) ANSI/TIA Documents for Document Number 1234 Project Number (PN)ExplanationPublished Standard Number ANSI/TIA-PN-12341 st (Letter) BallotANSI/TIA-1234- ANSI/TIA-PN-1234-D11 st Default Ballot, subsequent default ballots are designated in a numerical, sequential manner (e.g., ANSI/TIA-PN- 1234-D2) ANSI/TIA-1234- ANSI/TIA-PN-1234-R11 st Re-Ballot, subsequent re-ballots are designated in a numeric, sequential manner (e.g., ANSI/TIA-PN-1234-R2) ANSI/TIA-1234- ANSI/TIA-PN-1234-1Addendum 1 to ANSI/TIA-1234ANSI/TIA-1234-1- ANSI/TIA-PN-1234-2Addendum 2 to ANSI/TIA-1234ANSI/TIA-1234-2- ANSI/TIA-PN-1234-ARevision 1 of ANSI/TIA-1234ANSI/TIA-1234-A- ANSI/TIA-PN-1234-BRevision 2 of ANSI/TIA-1234ANSI/TIA-1234-B- ANSI/TIA-PN-1234-A-1Addendum 1 to ANSI/TIA-1234-AANSI/TIA-1234-A-1- ANSI/TIA-PN-1234-A-2Addendum 2 to ANSI/TIA-1234-AANSI/TIA-1234-A-2- ANSI/TIA-PN-1234-B-1Addendum 1 to ANSI/TIA-1234-BANSI/TIA-1234-B-1- ANSI/TIA-PN-1234-B-2Addendum 2 to ANSI/TIA-1234-BANSI/TIA-1234-B-2- ANSI/TIA-PN-1234-RF11 st Re-affirmation of ANSI/TIA-1234ANSI/TIA-1234- (see note 1) ANSI/TIA-PN-1234.001Part/chapter 001 of ANSI/TIA-PN- TIA-1234 ANSI/TIA-1234.001- ANSI/TIA-PN-1234-B-3 [E] Revision with Change Marks as Addendum 3 to TIA-1234-B TIA-1234-B-3-[E]-

26. Proposed Annex J (Changes Highlighted) (TSSC-2012Jul31-006b_Annex_J_New_Revision_Proposal_Clean) NOTE 1: A published standard that is reaffirmed retains the original publication year in the “ ” field. A separate notation on the cover page indicates the reaffirmation date.

28. Proposed Annex J (Changes Highlighted) (TSSC-2012Jul31-006b_Annex_J_New_Revision_Proposal_Clean) NOTE 2: When a published standard is revised, it incorporates all addenda from the previous revision, as well as any additional changes made by the committee. For example, if TIA- 1234 has two (2) addenda (TIA-1234-1 and TIA-1234-2), TIA-1234-A includes content from the two addenda and any additional changes made by the committee.

29. Proposed Annex J (Changes Highlighted) (TSSC-2012Jul31-006b_Annex_J_New_Revision_Proposal_Clean) NOTE 3: A multi-part document standard has a core document standard against which chapters/parts are published. This core document has the suffix “.000” (e.g., TIA-1234.000). Each part can be balloted separately and revised separately; however, when any other part is updated, the core document (“.000” document) is also updated appropriately to reflect the changes made to the other parts. NOTE 4: Published standards retain the assigned document number.

30. Proposed Annex J (Changes Highlighted) (TSSC-2012Jul31-006b_Annex_J_New_Revision_Proposal_Clean) NOTE 5: Standards added to a published (as of February 2011) series retain the assigned alphanumeric numbering (including dots and dashes) in that series. (e.g. the TIA-102 series standards retain the four- character, alphabetic extension for new Standards in the series rather than changing to the decimal/three digit extension). NOTE 6: All Standards have the same document number (e.g. 1234 in the tables above) throughout its lifecycle, from project inception through publication, addenda and updates.

31. Proposed Annex J (Changes Highlighted) (TSSC-2012Jul31-006b_Annex_J_New_Revision_Proposal_Clean) NOTE 7: Technical Standards Bulletins (TSBs) follow the same single-designation numbering for TIA (only) documents, except “TIA” is replaced with “TSB” in all instances. NOTE 8: Software distribution Standards include “[SF]” at the end of the Project Number and at the end of the Published Standard Number. (For example, TIA-PN-1234 [SF] / TIA-1234 [SF])

32. Proposed Annex J (Changes Highlighted) (TSSC-2012Jul31-006b_Annex_J_New_Revision_Proposal_Clean) NOTE 9: Project numbers for a Joint Standard (J-STD) follow the same single-designation numbering using “J-STD” in place of “TIA” in all instances. When another Standards Development organization is the lead developer, the alphanumeric numbering of that developer will be used (for example, Joint Standards where ATIS has the lead use a lower case alphabetic rather than numeric indicator for an addendum).

33. Proposed Annex J (Changes Highlighted) (TSSC-2012Jul31-006b_Annex_J_New_Revision_Proposal_Clean) NOTE 10: Projects initiated prior to February 2011 will retain their double-designation project number until the end of the project.

34. Proposed Advisory Note – Reaffirmations (-014) In order to comply with ANSI Essential Requirements regarding single-designation numbering and to clarify any confusion from having normative text in a “note”, the following change is made to the 5 th edition of the TIA Engineering Manual: – Clause 7.1, Item (3) Note Delete “Reaffirmation and withdrawals shall use the same project number that was used to publish the document.”

35. Next Steps Comments and review of -006b and -014 are welcome Per the Engineering Manual – Circulated among members of the TSSC for comments and suggestions – Balloted within the Technical Committee – Once approved, becomes effective – Sent to ANSI for review

37. Addendum – a document which supplements an existing standard and – i. Adds technical requirements to an existing standard that do not change previously published requirements; or – ii. Revises one or two portions of a large existing standard.

38. EM 7.2.1 Note: When additional technical requirements need to be added to an existing Standard without changing the previously published requirements, or when only one or two portions of a large existing Standard need to be revised, a Formulating Group may propose an addendum instead of a complete revision. When the Standard is next revised, the addendum is incorporated in the revision.