PowerPoint Presentation

2014 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.AT&T Proprietary (Internal Use Only) Not for use or disclosure outside the AT&T companies except under written agreement.Training and Reference Guide for Assessment Documents Version Date: 06/04/14Slide #Description3Agenda4Deployment Assessment Team5Team Functional Roles6Deployment Handoff Package (HoP) Definition7Getting Started8Initiation Phase - Process Overview 9Charter Certification10-11Certification Turned BAU12HoP Full Checklist13MiniHoP Checklist14-161.0 Deployment Program Charter17-182.0 Deployment RACI193.0 Deployment Document Locations (URLs)20-234.0 Deployment Volumes24-255.0 Deployment Risk Management List 2014 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.AT&T Proprietary (Internal Use Only) Not for use or disclosure outside the AT&T companies except under written agreement.Slide ContentSlide #Description266.0 Deployment Dependencies & Constraints Lists27-287.0 Deployment Issues Log29-30 8.0 High Level End-to-End Process Flow319.0 Workplan3210.0 Status 33Lessons Learned and Addendum34Informational35-38Deployment Program Change Request (CR)39Revision Log 40Unified Collection Application (UCA) 41-42Work Management Standards43HoP Definitions44Q&A45Questions that the HoP Should Answer 2014 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.AT&T Proprietary (Internal Use Only) Not for use or disclosure outside the AT&T companies except under written agreement.Agenda 2014 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.AT&T Proprietary (Internal Use Only) Not for use or disclosure outside the AT&T companies except under written agreement.Cross Organizational Team Memberse2e Front Door Representatives:Sam Nance (sn291j)Area Manager e2e National TeamWes Podsada (wp6493)National Front Door Team FacilitatorAnthony Boyd (tb2399)Central Region Front Door Team RepKathi Falko (ke775m)Northeast Region Front Door Team RepGene Kackley (gk1411)Southeast Region Front Door Team RepSuzanne Valdez (sl2485)West Region Front Door Team Rep

IPMO Portfolio Management Team:Kathryn Plage (kp243s)Area Manager Assessment Team Philip Ferrer (pf8540)Portfolio PMPauline Finnell (pf438s)Portfolio PMEric Johnson (ej9058)Portfolio PMKelly Vachlin (km7170)Portfolio PMDavid McConnell (dm715w)Portfolio PMEnsure all required Program/Project artifacts are created using a standard format and assist clients where necessary prior to execution. ObjectiveAssessment Team 2014 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.AT&T Proprietary (Internal Use Only) Not for use or disclosure outside the AT&T companies except under written agreement.PurposeVet all requests.Manage the Assessment and Issues Lists.Supply standard Charter and HoP artifacts.Provide consultant services in support of the Charter and HoP creation.Ensure completeness and acceptance of Charters and HoPs for Deployments. Accept or request rework of artifacts.Partner with Program/Project Managers and provide training.Provide metrics and volumes to leadership.e2e Front DoorProvide regular communication to Regional e2e Director and Area Managers.Review Program Charters and HoP artifacts for completeness.Work with the Portfolio Team to close Assessment process gaps and maintain Quality Control of the Assessment process.Portfolio TeamProvide regular communication to the AVPs and National PMO Directors. Work with Leadership on assignment of Deployment Program Managers.Establish metrics, volumes and target schedules.Provide consultation and support of the Charters and HoPs.Own standard templates.

Team Functional Roles 2014 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.AT&T Proprietary (Internal Use Only) Not for use or disclosure outside the AT&T companies except under written agreement.Past

No Handoff PackageNew Process

Handoff PackageCloudy handoffs: No clearly defined set of documents for a Deployment Program Manager to provide to the Project Manager.Standard set of deployment documents that contain the level of detail and quality required to execute at the program and project levels.Inconsistency: No clearly defined deliverables for transitioning processes, guides or tools from one organization or team to another.Consistent set of defined deliverables that facilitate the creation and delivery of a HoP.Lacks Measurability: No clear way to ensure that Deployment Program Managers have fulfilled their responsibilities to the Project Manager.Measurable metrics on deliverables (Quality Control).A Handoff Package is a unified collection of documents for any Program that will require PM support. It standardizes the information requested from all Programs and contains all available Program and Project level information.Definition Handoff Package (HoP) Definition 2014 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.AT&T Proprietary (Internal Use Only) Not for use or disclosure outside the AT&T companies except under written agreement.Contact the Portfolio Team when ready to submit the Program. Best Practice is to submit a DRAFT Charter in parallel with the submission of your Program. Send Inquiries to Assessment Team mailbox ASSESSMENT_TEAM.Getting Started 2014 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.AT&T Proprietary (Internal Use Only) Not for use or disclosure outside the AT&T companies except under written agreement.A Requestor submits a Program or Project via email to a Portfolio Team member using the ASSESSMENT_TEAM mailbox.

The Portfolio Team contacts requestor and supplies link to Charter, HoP and Training Guide.The DRAFT Charter is added to the HoP Charter Repository and accepted by the Portfolio Team for completeness.Portfolio Team requests a Deployment Program Manager (DPM) assignment for the program.Front Door Team notifies Area Managers of the Charter for an upcoming Program or Project.The Portfolio Team representative takes the role of consultant through HoP acceptance.

The DPM presents completed HoP first to the Assessment Team, then the Area Managers and obtains acceptance for execution.

Submit Program Request to Assessment Database or A List1.0 Deployment Program Charter 2.0 Deployment RACI3.0 Deployment Document Locations4.0 Deployment Volumes5.0 Deployment Risk Management List6.0 Deployment Dependencies/Constraints7.0 Deployment Issues Log8.0 Deployment End-to-End Process Flow9.0 Deployment Workplan10.0 Deployment Status

Additional MaterialLessons LearnedAddendumInformationalGMOP/SMOPAOTS Change ManagementWMS Standards Gate Approval required Deployment ArtifactsContact Portfolio TeamProgram Submission and supply DRAFT CharterSubmit Charter or HoP for ReviewReview andAcceptance by PM Org.ExecuteInitiating Phase Process Overview

2014 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.AT&T Proprietary (Internal Use Only) Not for use or disclosure outside the AT&T companies except under written agreement.All Certification programs require a Certification DRAFT Charter and will be reviewed by the Assessment Team. The Assessment Front Door Team will notify the Area Managers of accepted Certification DRAFT Charters.

Certification Acceptance will be used to denote acceptance by the Assessment Team of DRAFT Charters for Programs that are currently in the Certification process.

Future continued deployment will require a HoP to be created for the Deployment Phase.

All the HoP artifacts will be completed by the Deployment Program Manager and the Program will be reviewed and completely accepted moving it to Program Deployment and a Closed status within the Assessment Team.

URL: Link to Assessment Training GuideCharter - Certification 2014 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.AT&T Proprietary (Internal Use Only) Not for use or disclosure outside the AT&T companies except under written agreement.The HoP is given to the Deployment Project Managers to provide key information for their projects.Level of artifact completeness will vary depending on when Deployment begins.Certifications require artifact 1.0Certification and Deployment Program Managers will work together to determine documents required in support of the program.Certification turned BAU Programs will require Full HoP.Certification Turned BAUPhase 0Phase 1Phase 2Phase 3Phase 4Phase 5IdeationInitiationPlanningExecutionClosureDG2DG5DG0DG4DG3DG1DG6The Deployment Program Manager is assigned at M0.The Deployment Program Manager will approve the applicable Certification Project Artifacts and is accountable for the creation of the Deployment Artifacts (HoP).In order to get through DG4, the Handoff Package must be accepted by the Assessment Team.This will require the Deployment Program Manager to work with the Certification Project Manager to complete the Deployment Artifacts.

Assignment DPMNTD Draft Program CharterHoP accepted by Assessment Team 2014 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.AT&T Proprietary (Internal Use Only) Not for use or disclosure outside the AT&T companies except under written agreement.Certification Turned BAUHandoff Package ContentsApplicable Certification Project Artifacts:Mob. Eng. Deployment Guide - Only for new equipment/serviceBusiness Process Materials (i.e.): Methods Of Procedures (MOP) End to End Process Flows Job AidsIssues and Lessons LearnedImplementation GuideDocumented Drive/Call Test PlanDeployment Artifacts: (HoP)Deployment Program CharterDeployment Team RACIDeployment Documentation LocationDeployment VolumesDeployment Risk Management Deployment Dependencies & Constraints Deployment Issues Management Deployment End to End Process FlowDeployment Work plan (i.e., PMATT)Deployment StatusWork Management StandardsCertification Project Management leads the creation Deployment Program Management leads the creation1.0Deployment Program Charter2.0Deployment RACI3.0Deployment Document Locations4.0Deployment Volumes5.0Deployment Risk Management List6.0Deployment Dependencies/Constraints7.0Deployment Issues Log8.0Deployment End to End Process Flow9.0Deployment Workplan 10.0Deployment Status-Lessons Learned-Addendum - Additional Certification Project Artifacts (as required)-Informational

URL: Link to Assessment Training GuidePresentations:First review is with the Assessment Team. Notification will be sent to confirm acceptance. Final review is with the Area Managers. Notification will be sent to confirm acceptance. 2014 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.AT&T Proprietary (Internal Use Only) Not for use or disclosure outside the AT&T companies except under written agreement.HoP - Full Checklist1.0Deployment Program Charter2.0Deployment RACI3.0Deployment Document Locations9.0Deployment Workplan-Lessons Learned-Addendum-Informational

URL: Link to Assessment Training GuidePresentations:First review is with the Assessment Team. Notification will be sent to confirm acceptance. Final review is with the Area Managers. Notification will be sent to confirm acceptance. 2014 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.AT&T Proprietary (Internal Use Only) Not for use or disclosure outside the AT&T companies except under written agreement.MiniHoP ChecklistThe Project Charter is an approved document issued by the Sponsor to formally authorize the initiation of a Program/Project and to apply resources to acquire support to the workplan and its milestones/activities.Program Name on the artifact must mirror the ID# and NAME on the Assessment List.The Scope of the Program includes major deliverables and a detailed description of the work involved. It provides a documented basis for making decisions and for ensuring a common understanding among the stakeholders.

1.0 Deployment Program Charter Note: Artifacts are subject to change through Quality Control improvements. Please visit the Portfolio Team website for the most current template versions

Short Description:Identify type of work being requested RAN/Core/Transport/Rehome/Other and then new/upgrade/modification

Start short description here.

2014 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.AT&T Proprietary (Internal Use Only) Not for use or disclosure outside the AT&T companies except under written agreement.1.0 Deployment Program Charter (continued)

Approximating the Complexity/Intensity requirement in the PM Support section allows managers to better address resource leveling.Volumes should be within +/- 10% of the total. 2014 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.AT&T Proprietary (Internal Use Only) Not for use or disclosure outside the AT&T companies except under written agreement. 1.0 Deployment Program Charter (continued)

There are a few programs (such as IP Reclamation and some Core expansions) that are approved but only require IWOS and AOTS tickets. In the Confirm if a budget is required section, answer NO and provide a comment to explain in these instances.Budget allocation is not budget approval. Documented AVP approval is required to proceed if the budget is not approved.Many programs require a separate budget for call testing, such as RAN programs.The Sponsor that works with the Engineers and Vendors can verify if a separate budget is needed for additional validation/optimization requirements.Confirm with the Design Engineer if a separate budget is required for CTAC or other external resource requirements.

2014 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.AT&T Proprietary (Internal Use Only) Not for use or disclosure outside the AT&T companies except under written agreement.2.0 Deployment RACIThis artifact serves a dual purpose as a contact list and a responsibility matrix.Key milestones/deliverables in the left column, responsible teams in the top row (orange) with specific owners below (blue) to include name and UID. Add only key milestones/deliverables as this is a high level document (should match high level workplan 9.0).The Deployment Project Manager column will contain expectations of the supporting PM Organization.

2014 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.AT&T Proprietary (Internal Use Only) Not for use or disclosure outside the AT&T companies except under written agreement.Project Leadership Director Small Cells ProgramDirector EPC ProgramDirector LabNTD Project SponsorTechnical Solution OwnerTechnical Solution ArchitectNTD Project Manager - IPMONTD Program manager - IPMOEPC Project ManagerTechnical Lead Lab Network Planning Network Design Network Implementation Assigned NamesRob Wick Jeewan RamasaroopDavid OrloffAndrew WoodMark SundtSteven HarveyPaul KaramGeorge GuthrieMark MaggioRaja GopalanCiscoNexiusCiscoInitiate Phase ActivitiesDG0 Proposal ApprovalIIIRARIIPlan Phase ActivitiesM1 Scope BaselinedCCCACIIIIIDG1 - Checklist CompleteSAARSISSSIDG1 - Project Initiation Approval Review IIISSSASSIDG2 Requirements and Funding ApprovalSSSSSSASSSDG2 Gold Standard Approval SSSSSSASSIIIIM5 Release CommitIIIIRCAIIIIIIM6 Design CompleteSSSSSSASSSIIIExecute Phase ActivitiesM7 Lab Entry - Execute TestingIIIISSAIIRSSIDG3 Review - Lab ExitSSSSSSASSSSSIDG4 Production Readiness Review/ApprovalIIISSSASSSSSSDG5 Ready for ServiceIIISSSASSSSSSClose Phase ActivitiesDG6 Project CloseoutIIISSSASSSSSS2.0 Deployment RACI (Example)Example is missing ATTUIDsCertification example since there is an S. May want BAU example. 2014 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.AT&T Proprietary (Internal Use Only) Not for use or disclosure outside the AT&T companies except under written agreement.This artifact captures key documents associated with the Program/Project. Document information will change but they should have a common location.

The document name will be listed in the left column while the URL is listed in the right column.

PM organizations may need to request access to applications (SOLAR, PMATT, etc.). 3.0 Deployment Document Locations (URLs)Please add key documents below with URL locations. Documents could change but locations should not. URL Location(s)Handoff Package Draft/Approved HoP location.https://e-bussolutions.web.att.com/sites/Ne2eI/plage/SitePages/Home.aspxGMOP (REQUIRED)URL

Lessons Learned/Best Practices - see Database for more detailshttp://ebiz.sbc.com/cpo-admin/mmtp/LLindex.cfm Add Document NameURLAdd Document NameURL 2014 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.AT&T Proprietary (Internal Use Only) Not for use or disclosure outside the AT&T companies except under written agreement.This artifact captures volumes associated with the Program/Project.

There is no standard template/format associated with this artifact. The tables shown in the HoP template are examples only. The examples will need to be removed and replaced with Program / Project specific information.

The margin of error for the volumes will not be greater than +/- 10%. Refer back to your sponsor or organization if in doubt.

The volume data will be broken out by Quarter / Region / Market / Vendor. The break out needs to include any network elements affected.

4.0 Deployment Volumes 2014 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.AT&T Proprietary (Internal Use Only) Not for use or disclosure outside the AT&T companies except under written agreement.Volumes should have a margin of error of +/- 10%. Change control is not required if your volumes are within the percentage of the program total.Volume must minimally contain information per vendor/ per region/ per market(s). 4.0 Deployment Volumes (CORE) (Example 1 of 3)

2014 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.AT&T Proprietary (Internal Use Only) Not for use or disclosure outside the AT&T companies except under written agreement.Volumes should have a margin of error of +/- 10%. Change control is not required if your volumes are within the percentage of the program total.Volume must minimally contain information per vendor/ per region/ per market(s). 4.0 Deployment Volumes (RAN) (Example 2 of 3)

2014 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.AT&T Proprietary (Internal Use Only) Not for use or disclosure outside the AT&T companies except under written agreement.FFAFFACertification Turned BAUFFA LOCATIONSColumbia, MDHazelwood, MORochelle Park, NJDecatur, GALake Mary, FLCarrolton, TXSanta Clara, CASanta Anna, CASEGW NODESCLMAMDORDMZSR01NWTPMOABDMZSR01RCPKNJ02DMZSR01ATLNGAAC19WF01LKMRFLMF01WF01CRTNTX35DMZSR01SNTDCAUJDMZSR01SNAPCAHHDMZSR01CLMAMDORDMZSR02NWTPMOABDMZSR02RCPKNJ02DMZSR02ATLNGAAC19WF02LKMRFLMF01WF02CRTNTX35DMZSR02SNTDCAUJDMZSR02SNAPCAHHDMZSR02DEPENDENCIES13.3 LTE FFA 1W13.3 LTE FFA 1W13.3 LTE FFA 5W13.3 LTE FFA 5WDHCPv6 - NVP PlatformDHCPv6 - NVP PlatformDHCPv6 - NVP PlatformDHCPv6 - NVP PlatformDHCPv6 - NVP PlatformDHCPv6 - NVP PlatformDHCPv6 - NVP PlatformDHCPv6 - NVP PlatformDHCPv6 - NVP PlatformTEAM ROLE AND RESPONSIBILITIESIPMO SmallCellsPaul KaramPaul KaramPaul KaramPaul KaramPaul KaramPaul KaramPaul KaramPaul KaramSeGW EPC PMMark MaggioMark MaggioMark MaggioMark MaggioMark MaggioMark MaggioMark MaggioMark MaggioSeGW Lab ManagerRaja GopalanRaja GopalanRaja GopalanRaja GopalanRaja GopalanRaja GopalanRaja GopalanRaja GopalanPOC FFA Columbia RDCRon Routh ?Ron Routh ?Ron Routh ?Ron Routh ?Ron Routh ?Ron Routh ?Ron Routh ?Ron Routh ?PM FFA Site - Columbia RDCJennifer Miner- OvereemJennifer Miner- OvereemEquipment Design Engineer - Columbia RDCAllen BoeckerAllen BoeckerAllen BoeckerAllen BoeckerAllen BoeckerAllen BoeckerAllen BoeckerAllen Boeckere2e Project ManagerNANAMaintenance WindowMaintenance WindowMaintenance WindowMaintenance WindowMaintenance WindowMaintenance WindowEQUIPMENTS AND CONNECTIVITYThird SAMI Blade AvailabilityYESYESNONONONONONOFFA REQUIREMENTSExit from AT&T labNA NA NA NA NA NA NA NA Volumes should have a margin of error of +/- 10%. Change control is not required if your volumes are within the percentage of the program total.Volume must minimally contain information per vendor/ per region/ per market(s). 4.0 Deployment Volumes (Certification) (Example 3 of 3) 2014 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.AT&T Proprietary (Internal Use Only) Not for use or disclosure outside the AT&T companies except under written agreement.5.0 Deployment Risk Management ListThis artifact will capture any high level risks associated with the Program/Project. This artifact should never be blank.A risk is any event that can have negative impacts to cost, schedule, volumes or execution.

2014 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.AT&T Proprietary (Internal Use Only) Not for use or disclosure outside the AT&T companies except under written agreement.#Date OpenedRisk TitleRisk DescriptionOwnerRiskLevelH-M-LComments / Updates1xx/xx/xxNetwork Design ErrorDesign specifications are focused on ATM circuits and must include IP technology.NAH030025. Design Engineering review corrected designs and approved final changes.2.xx/xx/xxMME Decom delay could impact SGSNs w/S4 growth Decommission existing MKVI+ MMEs and repurpose them as new Ericsson SGSN with S4 interfaces.NAH- MME Decom work plan was created. x/xx/xx- Santa Clara LT0- LT3 have completed traffic offload.- Santa Ana LT0/LT1/LT3 have completed traffic offload. Santa Ana LT2 still pending eNBs removal. - Santa Clara LT0-LT3 were powered down. 3.xx/xx/xxVoLTE E911E911 Devices: Samsung Wilson and Jade devices do not support E911 at this time. The E911 team will start FFA with a very limited pool of Qualcomm prototype devices until Samsung devices are made available. The prototype devices have been experiencing a high failure rate.NAHEscalation in process to avoid jeopardy.4.xx/xx/xxTransmitting RET CIQ Template information to EricssonThe IWOS ticket completion information currently doesnt provide the RET / SIAD Username and Password information.National RAN IPMO / Edge to Edge RANMNational support of forward logistics has been removed due to leadership and business requirement. Market equipment engineering has completed all EPL order entries 9/20, now in review for accuracy.5.xx/xx/xxTransmitting RET CIQ Template information to EricssonThe IWOS ticket completion information currently doesnt provide the RET / SIAD Username and Password information.National RAN IPMO / Edge to Edge RANMNational RAN IPMO will drive additional communications and explore options for mitigating this risk.

5.0 Deployment Risk Management List (Example) 2014 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.AT&T Proprietary (Internal Use Only) Not for use or disclosure outside the AT&T companies except under written agreement.6.0 Deployment Dependency & Constraints ListThis artifact captures dependencies and/or constraints associated with the Program/Project.A dependency is a logical relationship between activities where a predecessor task(s) must first be completed before starting the next activity(s). Dependencies#Date OpenedDependency TitleDependency DescriptionAssigned toDate ResolvedComments / Updates2/2/2525SoftwareSoftware patch 7.7.2.3 must be applied to MSC.John DoeXX/XX/XX1.A constraint can be any related factor that limits or reduces the progress to a Program/Project or Process.Constraints#Date OpenedConstraint TitleConstraint DescriptionAssigned toDate ResolvedComments / Updates2/2/2525Market ResourcesResource assignments expected to be full and may delay forward progress during 1Q20xx..John DoeXX/XX/XX1.

2014 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.AT&T Proprietary (Internal Use Only) Not for use or disclosure outside the AT&T companies except under written agreement.7.0 Deployment Issues LogThis artifact will capture any issues associated with the Program/Project. This artifact should never be blank.Issue Any unresolved situation within a program or project which requires a solution between stakeholders.Issues do not impact Programs unless matters are left unresolved.

#Issue TitleIssue DescriptionAssigned toTarget Resolution DateComments / UpdatesActual Resolution Date1.BudgetBudget is allocated but not yet approved by the sponsor.John DoeXX/XX/XX12/01/25 - Meetings with sponsor to review budget is ongoing thus no decision to date for final budget approval.XX/XX/XX2.3.

2014 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.AT&T Proprietary (Internal Use Only) Not for use or disclosure outside the AT&T companies except under written agreement.#Issue TitleIssue DescriptionAssigned toTarget Resolution DateComments / UpdatesActual Resolution Date1.SolarSupporting organization do not use or have access to SolarJane Doexx/xx/xx07/07/25 A temporary SharePoint site will be created for the project durations to allow access to key documents.xx/xx/xx2.BudgetBudget is allocated but not yet approved by the sponsor.John Doexx/xx/xx12/01/25 - Meetings with sponsor to review budget is ongoing thus no decision to date for final budget approval.xx/xx/xx3.CASPR SupportEnsuring alignment of Edge to Edge National RAN IPMOxx/xx/xx9/4/2013 final E2E acceptance was reached via final AVP and Director level approval. For the initial run National RAN IPMO will support CASPR updates and E2E will support National RAN IPMO with the required tracking templates and data points needed to updated CASPR.

xx/xx/xx4.Database of RecordIdentifying and acquiring support for integration of the Ericsson Modernization Program with a system capable of supporting the volume and tied to existing processes.National RAN IPMOxx/xx/xxNational RAN IPMO investigated 4 systems and interviewed functional teams and IT SMEs regarding the following options;1.) PMATT as 1st option for the program/projects2.) PACE as 2nd 3.) Spreadsheets Immediately eliminated4.) iPlan / CASPR

Cross-functional agreement was in support of CASPR. 9/4/2013 final E2E acceptance was reached via final AVP and Director level approval. For the initial run National RAN IPMO will support CASPR updates and E2E will support National RAN IPMO with the required tracking templates and data points needed to updated CASPR.

xx/xx/xx7.0 Deployment Issues Log (Example) 2014 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.AT&T Proprietary (Internal Use Only) Not for use or disclosure outside the AT&T companies except under written agreement.

IPv6 eNB Market GovernanceIPv6 Team provides 3 month look-ahead to MarketsMarkets projected to be dual stacked MSN NorthMarket eNB Deployment FactorieseTe Market PMs (28)eTe Market Deconflictors2014 Greenfield eNB Deployment ScheduleMarkets projected to be ready for eNB conversionsIPv6 eNB Market GovernancePhase 3 OAM & Transport-Layer & eNB ConversionsIPv4 Reclamation (Proposal)Markets with elements from MSN North that are Dual Stacked can begin Greenfield Deployments with IPv6 addressesMarkets with elements from MSN North that are Dual Stacked will have eNBs converted, led by IPv6 Program TeamAfter eNB conversions are completed by market, IPv4 Reclamation team will be notified to return IPv4 addresses from CSBH to IPv4 pool8.0 High Level End-to-End Process Flow (Example 1 of 2)This artifact must contain the process flow specifically associated with this Program or Project.There is no standard template/format associated with this artifact, however, we recommend a basic high-level drawing or text with each step. 2014 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.AT&T Proprietary (Internal Use Only) Not for use or disclosure outside the AT&T companies except under written agreement.Open IWOS with TP&E

Include BGCF Form, COST Report, GMLC Form911 Market EngIWOSValidate 911 TGs,Update BGCF Form with 911 TGs(1 day)

TP&EGranite,Etc.Optional IWOSB5.06.0Fill Out BGCF Form (PSAP Agency, 911 RNs)911 Market Eng4.0A911RNs:PSAP Id (R) - GMLC Vendor IdESRK Range or PH 0 TN (R)911RN Type (R) ESRK or 10DLATA (O)MGCF MSC (R) MGCF MSC PC (O)Note: ESRK ranges may be split across MGCF MSCs or defined in more than one MGCF MSC

911 Routes (Network Topology):CA/Switch CLLI (R)E911 TG Route Name (R)SR CLLI (R)TG Type, Dir, Series PSAP ID (s) (R)

PSAP Agency:PSAP Id (R) - GMLC Vendor IdPSAP Type (R) Intrado vs. TCSPSAP Name (R) - GMLC PSAP NamePSAP Phase (R) 0 or 1-2FCC Id (O)PSAP City, State, County (R) - per FCC Registry if applicablePSAP FIPS (O)SR CLLI (R) and other optional SR info

Validate 911 TGs,ESRKs for PSAP8.0 High Level End-to-End Process Flow (Example 2 of 2) 2014 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.AT&T Proprietary (Internal Use Only) Not for use or disclosure outside the AT&T companies except under written agreement.

Core Example only9.0 WorkplanA high level Workplan must first be created and completed before the HoP can be approved and handed to the supporting Project Management organization.For RAN or other non-CORE Programs/Projects, the Workplan can be developed using CASPR, Excel or MS Project (or another approved tool).CORE Programs/Projects will use PMATT. The Deployment Program Manager will be responsible to create a PMATT project. Please make sure you give this task enough lead time as it can take 3-6 weeks to complete. If requesting Maintenance Window PM support ONLY, no PMATT projects will be issued.For all Workplans, specify where Market PM support ends (which milestone)

2014 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.AT&T Proprietary (Internal Use Only) Not for use or disclosure outside the AT&T companies except under written agreement.10.0 StatusIdentify how National updates will be managed.Summarize the expectations of how updates will flow between the Regions/Markets and the DPM.What are the required fields for reporting key milestones/deliverables (from workplan).Identify which tool(s) will need to be used:Preference is an IT supported application so reports can be auto generated.Will there be any special access requirements?If applicable, provide links.

2014 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.AT&T Proprietary (Internal Use Only) Not for use or disclosure outside the AT&T companies except under written agreement.Lessons LearnedMike Watson Directive.Standard practice in Project Management.Helps in reducing costs and other impacts.Value Add - The causes of variances, the reasoning behind the corrective action chosen and other types of lessons learned from quality control need to be documented so they become part of the historical database for both the project and the performing organizationIntervals:The program/project leads will determine review intervals for lessons learned and best practices and will communicate these valuable inputs with the whole teamPMCOE is highly recommended by IPM: For convenience and access by all users, AT&T created the PMCOE Lessons Learned Database to capture and show project lessons learned

AddendumInclude high level diagrams or other value added documents needed for the HoP review 2014 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.AT&T Proprietary (Internal Use Only) Not for use or disclosure outside the AT&T companies except under written agreement.InformationalGMOP (Required for HoP acceptance)/SMOP (Not required for HoP acceptance).BAU Projects will have MOPs created by the supporting organization(s) before project execution beginsCertification turned BAU Projects should provide a GMOP to the Deployment Program Manager per Certification ProcessIf applicable, add URLs to communications slide and add contacts to the RACI artifactContact ATS at (866) 849-9453 for MOP approvals/updates. Utilizing the ATS phone menu select the correct vendor and product to the appropriate ATS contact that will assist

AOTS Change Management Request.Solutions:Use a standard approach to creating CMR tickets in AOTSIdentify the team responsible for initiation of the CMRFollow a standard process for CMR creation using Job Aids providedIdentify all work groups that need to execute a task for the CMRRefer to CMR Creation foldere2e Organization - AOTS/CMR Requiremente2e PMO will open task shell CMRs when it is e2e PMO managing the activity and AOTS system is conditioned to accept shell CMRse2e PMO will not open CMRs for work that other organizations are initiating/managingThe team owning the maintenance window work is responsible for opening the CMR and following standard AOTS technical collision facilitation proceduresPlease refer to the CMR Matrix for Category Type & Item (CTI) information or contact the Portfolio Team for further assistance

How to get a hold of the Assessment Team: ASSESSMENT_TEAM