[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-241590-105":53,"doc-detail-241590-en":127},{"code":4,"msg":5,"data":6},0,"success",[7,14,19,24,29,34,39,44,49],{"id":8,"doc_module":9,"doc_module_name":10,"category_name":11,"show_sort_weight":12,"slug":13},11,1,"Template","Presentations",90,"presentations",{"id":15,"doc_module":9,"doc_module_name":10,"category_name":16,"show_sort_weight":17,"slug":18},12,"Resumes",80,"resumes",{"id":20,"doc_module":9,"doc_module_name":10,"category_name":21,"show_sort_weight":22,"slug":23},14,"Invoices",70,"invoices",{"id":25,"doc_module":9,"doc_module_name":10,"category_name":26,"show_sort_weight":27,"slug":28},15,"Posters",60,"posters",{"id":30,"doc_module":9,"doc_module_name":10,"category_name":31,"show_sort_weight":32,"slug":33},16,"Social Media",50,"social-media",{"id":35,"doc_module":9,"doc_module_name":10,"category_name":36,"show_sort_weight":37,"slug":38},17,"Forms",40,"forms",{"id":40,"doc_module":9,"doc_module_name":10,"category_name":41,"show_sort_weight":42,"slug":43},18,"Letters",30,"letters",{"id":45,"doc_module":9,"doc_module_name":10,"category_name":46,"show_sort_weight":47,"slug":48},21,"Paper Templates",5,"papers-templates",{"id":50,"doc_module":9,"doc_module_name":10,"category_name":51,"show_sort_weight":4,"slug":52},158,"General","general-158",{"code":4,"msg":54,"data":55},"ok",{"site_id":56,"language":57,"slug":58,"title":59,"keywords":60,"description":61,"schema_data":62,"social_meta":120,"head_meta":122,"extra_data":124,"updated_unix":126},105,"en","change-control-process-version-20-august-23-2000","CHANGE CONTROL PROCESS - Version 2.0 - August 23, 2000","","Change Control Process CCP8_23 document, version 2.0 dated August 23, 2000, defines governance and procedures for managing electronic interface change requests. It includes version change history outlining revisions since earlier issues, with updates to change request types, notification and escalation workflows, cycle times, defect notification and workaround communication, and adjustments to forms and status codes. It also establishes coordination responsibilities for the Change Control Sub-team and references related interfaces, testing environment, dispute resolution, and participation changes.",{"@graph":63,"@context":119},[64,80,102],{"@type":65,"itemListElement":66},"BreadcrumbList",[67,71,74,77],{"item":68,"name":69,"@type":70,"position":9},"https://docshare.wps.com","Home","ListItem",{"item":72,"name":10,"@type":70,"position":73},"https://docshare.wps.com/template/",2,{"item":75,"name":46,"@type":70,"position":76},"https://docshare.wps.com/template/paper-templates/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/change-control-process-version-20-august-23-2000/241590/",4,{"url":78,"name":59,"@type":81,"image":82,"author":87,"headline":59,"publisher":90,"fileFormat":93,"inLanguage":57,"description":61,"dateModified":94,"datePublished":95,"encodingFormat":93,"isAccessibleForFree":96,"interactionStatistic":97},"DigitalDocument",{"url":83,"@type":84,"width":85,"height":86},"https://docshare.wps.com/thumbnails/change-control-process-version-20-august-23-2000/241590.png","ImageObject",442,249,{"name":88,"@type":89},"Sarah ","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-10","2026-09-12",true,{"@type":98,"interactionType":99,"userInteractionCount":101},"InteractionCounter",{"@type":100},"ViewAction",7,{"@type":103,"mainEntity":104},"FAQPage",[105,111,115],{"name":106,"@type":107,"acceptedAnswer":108},"What document is this and what version does it cover?","Question",{"text":109,"@type":110},"It covers the Change Control Process (CCP8_23) and specifies version 2.0 dated August 23, 2000.","Answer",{"name":112,"@type":107,"acceptedAnswer":113},"What major kinds of changes are tracked in the version history?",{"text":114,"@type":110},"The version history records updates to change request types, process steps, notification and escalation rules, cycle times, defect notification/workaround communication, forms, and status codes.",{"name":116,"@type":107,"acceptedAnswer":117},"How are changes coordinated between participating parties?",{"text":118,"@type":110},"The process is jointly developed by a Change Control Sub-team comprised of BellSouth and CLEC representatives, with responsibilities reflected through sections on participants, meetings, and review communication.","https://schema.org",{"og:url":78,"og:type":121,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":123,"canonical":78},"index,follow",{"doc_id":125,"site_id":56},241590,1790625926,{"code":4,"msg":5,"data":128},{"doc_id":125,"user_id":129,"nickname":88,"user_avatar":130,"doc_module":9,"category_id":45,"category_name":46,"doc_title":59,"doc_description":61,"doc_content":131,"file_id":132,"file_url":133,"file_type":134,"file_size":135,"view_count":101,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":136,"language":137,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":138,"faqs":139,"seo_title":140,"seo_description":61,"update_tm":141,"read_time":142},962085320529,"https://ap-avatar.wpscdn.com/davatar_9964176cb1d06d4a9deccf72a44ae3dc","Ccp8_ 23.doc  \nCHANGE CONTROL PROCESS  \nCCP8_23.DOC VERSION 2.0  \nAUGUST 23, 2000  \n\n| Issued: 8/23/00 | Jointly Developed by the Change Control Sub-team comprised\u003Cbr>of BellSouth and CLEC Representatives. |\n| --- | --- |\n\nBellSouth Telecommunications reserves the right to revise this document for any reason, with concurrence of the CLEC/BellSouth Review Board, including but not limited to, conformity with standards promulgated by various government or regulatory agencies, utilization of advance in the state of the technical arts, or the reflection of changes in the design of any equipment, techniques, or procedures described or referred to herein. LIABILITY TO ANYONE ARISING OUT OF USE OR RELIANCE UPON ANY INFORMATION SET FORTH HEREIN IS EXPRESSLY DISCLAIMED, AND NO REPRESENTATIONS OR WARRANTIES, EXPRESSED OR IMPLIED, ARE MADE WITH RESPECT TO THE ACCURACY OR UTILITY OF ANY INFORMATION SET FORTH HEREIN.  \nThis document is not to be construed as a suggestion to any manufacturer to modify or change any of its products, nor does this document represent any commitment by BellSouth Telecommunications to purchase any product whether or not it provides the described characteristics.  \nThis document is not to be construed as a contract. It does not create an obligation on the part of BellSouth Telecommunications or the Competitive Local Exchange Carriers to perform any modification, change or enhancement of any product or service.  \nNothing contained herein shall be construed as conferring by implication, estoppel or otherwise, any license or right under any patent, whether or not the use of any information herein necessarily employs an invention of any existing or later issued patent.  \n\n| Issued: 08/23/00 | Jointly Developed by the Change Control Sub-team comprised\u003Cbr>of BellSouth and CLEC Representatives. |\n| --- | --- |\n\nVERSION CHANGE HISTORY  \nThis section list changes made to the baseline Electronic Interface Change Control Process document since the last issue. New versions of this document may be obtained via BellSouth’s Web site.  \n\n| Version | Issue Date | Section Revised | Reason for Revision |\n| --- | --- | --- | --- |\n| 1.0 | 04/14/98 |  | Initial issue. |\n| 1.2 | 2/28/00 | All | The EICCP Documentation has been modified to incorporate:\u003Cbr>- Multiple Change Request Types (CLEC Initiated, BST Initiated, Industry Standards, Regulatory and System Outages)\u003Cbr>- Incorporated manual process\u003Cbr>- Defined cycle times for process intervals and notifications\u003Cbr>- Defect Notification process\u003Cbr>- Escalation Process\u003Cbr>- Modified Change Control forms to support process changes\u003Cbr>- Changed EICCP to CCP |\n| 1.3 | 3/14/00 | All | The CCP Documentation has been modified to incorporate:\u003Cbr>- Type 6 Change Request, CLEC Impacting Defect\u003Cbr>- Increased number of participants at Change Review meetings\u003Cbr>- Changed cycle time for Types 2-5 Step 3 from\u003Cbr>20 days to 15 days\u003Cbr>- Defined Step 4 of the Defect Notification process to include communicating the workaround to the CLEC community\u003Cbr>- Web Site address for Change Control Process\u003Cbr>- Notification regarding the Retirement and |\n\nIssued: 08/23/00 i  \nJointly Developed by the Change Control Sub-team comprised  \nof BellSouth and CLEC Representatives.  \n\n|  |  |  | Introduction of new interfaces\u003Cbr>- New status codes for Defect Change Requests\u003Cbr>- New status codes: ‘S’ for Scheduled Change Requests and ‘I’ for Implemented Change Requests (types 2-5 Change Requests)\u003Cbr>- Removed reference to EDI Helpdesk.\u003Cbr>Electronic Communications Support (ECS) will be the first point of contact for Type 1 System Outages.\u003Cbr>- Word changes to provide clarification throughout the document. |\n| --- | --- | --- | --- |\n| 1.4 | 4/12/00 | All | The CCP Documentation has been modified to incorporate:\u003Cbr>- Type 1 and 6 Notifications will be communicated to CLECs via e-mail and web posting\u003Cbr>- Step 3 Cycle Time (Types 2-5) changed from\u003Cbr>15 business days to 20 business days\u003Cbr>- Verbiage to Step 10 (Types 2-","cbCaicRjWst2s8ab","https://ap.wps.com/l/cbCaicRjWst2s8ab","pdf",377874,99,"English","# Change Control Process\n## Version Change History\n## Change Control Process Responsibilities and Disclaimers","[{\"question\":\"What document is this and what version does it cover?\",\"answer\":\"It covers the Change Control Process (CCP8_23) and specifies version 2.0 dated August 23, 2000.\"},{\"question\":\"What major kinds of changes are tracked in the version history?\",\"answer\":\"The version history records updates to change request types, process steps, notification and escalation rules, cycle times, defect notification/workaround communication, forms, and status codes.\"},{\"question\":\"How are changes coordinated between participating parties?\",\"answer\":\"The process is jointly developed by a Change Control Sub-team comprised of BellSouth and CLEC representatives, with responsibilities reflected through sections on participants, meetings, and review communication.\"}]","CHANGE CONTROL PROCESS - Version 2.0 - August 23, 2000 | PDF",1789177753,35]