# Managed E-Authentication Service (MEAS) Cutover Checklist {#managed-e-authentication-service-meas-cutover-checklist .CH_1}

#  {#section .CH_1}

#  {#section-1 .CH_1}

# GSA Transition Coordination Center {#gsa-transition-coordination-center .CH_2}

#  {#section-2 .CH_2}

#  {#section-3 .CH_2}

#  {#section-4 .CH_2}

#  {#section-5 .CH_2}

#  {#section-6 .CH_2}

#  {#section-7 .CH_2}

# July 30, 2007 {#july-30-2007 .CH_2}

#  {#section-8 .CH_2}

#  {#section-9 .CH_2}

# Prepared for the {#prepared-for-the .CH_3}

# GENERAL SERVICES ADMINISTRATION {#general-services-administration .CH_3}

# Networx Support Services {#networx-support-services .CH_3}

# 10304 Eaton Place {#eaton-place .CH_3}

# Fairfax, VA 22030 {#fairfax-va-22030 .CH_3}

#  {#section-10 .CH_3}

#  {#section-11 .CH_3}

#  {#section-12 .CH_3}

#  {#section-13 .CH_3}

#  {#section-14 .CH_3}

#  {#section-15 .CH_3}

#  {#section-16 .CH_3}

#  {#section-17 .CH_3}

# Contract Number GS00T03AHD0007 {#contract-number-gs00t03ahd0007 .CH_3}

# Order Number GST007NS0023 {#order-number-gst007ns0023 .CH_3}

#  {#section-18 .CH_3}

#  {#section-19 .CH_3}

# Managed E-Authentication Service (MEAS) Cutover Checklist {#managed-e-authentication-service-meas-cutover-checklist-1 .CH_2}

I.  Networx Service Functional Definition: Managed E-Authentication
    Service (MEAS)

> Managed E-Authentication Service (MEAS) provides Agencies with
> electronic authentication services in order to seamlessly conduct
> electronic transactions and implement E-Government initiatives via the
> Internet. The service enables an individual to remotely authenticate
> his or her identity to an Agency Information Technology (IT) system.
>
> Managed E-Authentication Service consists of hardware and software
> components that provide for remote authentication of individual users
> over a network for the purpose of electronic government and commerce.
> The service provides for the electronic validation and verification of
> a user's identity and enables the use of electronic signatures over
> the Internet, the Networx vendor's network and other public networks.
>
> Managed E-Authentication Service uses underlying transport and access
> services for transfer of authentication information. The service will
> connect to Agency networking environments including, but not limited
> to Agency Demilitarized Zones (DMZs) and secure LANs. MEAS will also
> connect to public networks such as the Internet and also allow
> connectivity to extranets.
>
> The core service will provide products and services that enhance the
> security of networked systems and facilitate digital signatures. The
> service will establish the required client and server software,
> hardware, and operational procedures to establish an Agency
> authentication capability.

![](media/image2.wmf){width="6.4875in" height="3.3666666666666667in"}

![](media/image3.wmf){width="2.932638888888889in"
height="0.7097222222222223in"}

Figure 1:

Figure 1 shows a certificate based authorization method. In this
scenario one certificate identifies the resource server while another
certificate identifies the user or client host.

![](media/image4.wmf){width="6.4875in" height="3.4145833333333333in"}

![](media/image3.wmf){width="2.932638888888889in"
height="0.7097222222222223in"}

Figure 2:

Figure 2 shows a token based implementation. In this scenario the token
maintains the keys or certificates and can be used to identify an
individual user or client. Also, some tokens may allow for the creation
of one-time-use pins for added security.

II. Applicable standards include:

Managed E-Authentication Service will comply with the following
standards, as applicable: After award, the Networx vendor may propose
alternatives at no additional cost to the Government that meet or exceed
the provisions of the standards listed below:

1.  DIAMETER Protocol RFC 3588

2.  Federal CIO Federal Identity Credentialing Committee (FICC) Shared
    Service Provider (SSP) program documents suite

3.  GSA eGov E-Authentication Technical Suite

4.  International Telecommunications Union -- Telecommunications Sector
    (ITU-T) Recommendation X.509 version 3 certificates

5.  ITU-T X.500 Series of Recommendations

6.  LDAP v2 or higher for Certificate Revocation List (CRL) retrieval

7.  LDAPS (LDAP Secure, i.e., LDAP over SSL) for CRL retrieval

8.  Liberty Alliance format (currently versions 1.1. and 2.x)

9.  NIST FIPS 140-2 -- Security Requirements for Cryptographic Modules

10. NIST Interagency Report (NISTIR) 6887 -- 2003 Edition, Government
    Smart Card Interoperability Specification (GSC-IS) v2.1

11. NIST Special Publication (SP) 800-63 -- Recommendation for
    Electronic Authentication

12. NIST Special Publication (SP) 800-73 -- Integrated Circuit Card for
    Personal Identity Verification (currently still Draft)

13. Online Certificate Status Protocol (OCSP)

14. PKIX Internet Engineering Task Force (IETF) Request For Comments
    (RFC) 3280

15. Remote Authentication Dial In User Service (RADIUS) Protocol

16. RFC 3647 -- Internet X.509 PKI Certificate Policy and Certification
    Practices Framework

17. Security Assertion Markup Language (SAML)

18. Shibboleth security middleware specification

19. Simple Certificate Validation Protocol (SCVP)

20. Terminal Access Controller Access Control System (TACACS) /TACACS+
    (Cisco) Protocol

21. Web services security language (WS-Security) specification by OASIS

22. X.509 Certificate Policy for the U.S. Federal PKI Common Policy
    Framework

23. All new versions, amendments, and modifications of the above when
    offered commercially.

24. All appropriate Standards for any applicable underlying Networx
    access and transport services.

```{=html}
<!-- -->
```
III. Networx Performance Requirements

The performance levels and Acceptable Quality Level (AQL) of the Key
Performance Indicators (KPIs) for Managed E-Authentication Service are
mandatory

**Managed E-Authentication Service (MEAS) Performance** Metrics

+-------------+------+-------------+---------+-----------------------+
| **Key       | **   | **P         | **Acc   | **How Measured**      |
| P           | Serv | erformance\ | eptable |                       |
| erformance\ | ice\ | Standard\   | Q       |                       |
| I           | Lev  | (T          | uality\ |                       |
| ndicators** | el** | hreshold)** | Level   |                       |
|             |      |             | (AQL)** |                       |
+=============+======+=============+=========+=======================+
| A           | Rou  | 99.99%      | ≥       | MEAS availability is  |
| vailability | tine |             | 99.99%  | calculated as a       |
|             |      |             |         | percentage of the     |
|             |      |             |         | total reporting       |
|             |      |             |         | interval time that    |
|             |      |             |         | the MEAS is           |
|             |      |             |         | operationally         |
|             |      |             |         | available to the      |
|             |      |             |         | Agency. \[Note. It    |
|             |      |             |         | includes that of the  |
|             |      |             |         | various databases and |
|             |      |             |         | servers that are      |
|             |      |             |         | employed (such as but |
|             |      |             |         | not limited to        |
|             |      |             |         | directory, RADIUS,    |
|             |      |             |         | and TACACS) to        |
|             |      |             |         | provide the           |
|             |      |             |         | service.\].           |
|             |      |             |         | Availability is       |
|             |      |             |         | computed by the       |
|             |      |             |         | standard formula:     |
|             |      |             |         | ![](medi              |
|             |      |             |         | a/image5.wmf){width=" |
|             |      |             |         | 2.2909722222222224in" |
|             |      |             |         | height="0.            |
|             |      |             |         | 37430555555555556in"} |
+-------------+------+-------------+---------+-----------------------+
| Event       | Rou  | Within 4    | ≤ 4     | The Event             |
| N           | tine | hours of a  | hours   | Notification (EN)     |
| otification |      | low         |         | value represents the  |
| (EN)        |      | category    |         | elapsed time between  |
|             |      | event.      |         | the detection of the  |
|             |      |             |         | event by the Networx  |
|             |      |             |         | vendor and the        |
|             |      |             |         | notification of the   |
|             |      |             |         | Agency. Events are    |
|             |      |             |         | categorized as        |
|             |      |             |         | follows:              |
|             |      |             |         |                       |
|             |      |             |         | a.  Low --- Events in |
|             |      |             |         |     the Low category  |
|             |      |             |         |     have a negligible |
|             |      |             |         |     impact on service |
|             |      |             |         |     overall. They     |
|             |      |             |         |     include           |
|             |      |             |         |     non-critical      |
|             |      |             |         |     server alerts     |
|             |      |             |         |     that indicate     |
|             |      |             |         |     systems           |
|             |      |             |         |     configuration     |
|             |      |             |         |     problems,         |
|             |      |             |         |     authentication    |
|             |      |             |         |     server hardware   |
|             |      |             |         |     or software       |
|             |      |             |         |     failures that do  |
|             |      |             |         |     not disrupt       |
|             |      |             |         |     service, and      |
|             |      |             |         |     multiple rejects  |
|             |      |             |         |     of an individual  |
|             |      |             |         |     User ID.          |
|             |      |             |         |                       |
|             |      |             |         | b.  High --- Events   |
|             |      |             |         |     in the High       |
|             |      |             |         |     category have a   |
|             |      |             |         |     severe impact on  |
|             |      |             |         |     service and       |
|             |      |             |         |     operations. They  |
|             |      |             |         |     include server    |
|             |      |             |         |     failures that     |
|             |      |             |         |     disrupt service,  |
|             |      |             |         |     suspicious        |
|             |      |             |         |     activities        |
|             |      |             |         |     detected by the   |
|             |      |             |         |     Networx vendor,   |
|             |      |             |         |     and request for   |
|             |      |             |         |     an emergency      |
|             |      |             |         |     reset of PIN to a |
|             |      |             |         |     static password   |
|             |      |             |         |     for a user who    |
|             |      |             |         |     has lost use of a |
|             |      |             |         |     token but needs   |
|             |      |             |         |     to gain access.   |
|             |      |             |         |     These events are  |
|             |      |             |         |     immediately       |
|             |      |             |         |     reported to       |
|             |      |             |         |     Agency designated |
|             |      |             |         |     POCs via such as  |
|             |      |             |         |     but are not       |
|             |      |             |         |     limited to email, |
|             |      |             |         |     pager, and        |
|             |      |             |         |     telephone as      |
|             |      |             |         |     specified by the  |
|             |      |             |         |     Agency.           |
+-------------+------+-------------+---------+-----------------------+
|             |      | Within 30   | ≤ 30    |                       |
|             |      | minutes of  | minutes |                       |
|             |      | a high      |         |                       |
|             |      | category    |         |                       |
|             |      | event       |         |                       |
+-------------+------+-------------+---------+-----------------------+
| Grade of    | Rou  | Within 24   | ≤ 24    | The Grade of Service  |
| Service     | tine | hours for a | hours   | (Configuration        |
| (Co         |      | normal      |         | Change) value         |
| nfiguration |      | priority    |         | represents the        |
| Change)     |      | change      |         | elapsed time between  |
|             |      |             |         | the change request by |
|             |      |             |         | the Agency POC and    |
|             |      |             |         | the change completion |
|             |      |             |         | by the Networx        |
|             |      |             |         | vendor. The elapsed   |
|             |      |             |         | time is measured by   |
|             |      |             |         | logs/reporting.       |
|             |      |             |         | Changes are initiated |
|             |      |             |         | and prioritized by    |
|             |      |             |         | the Agency. Changes   |
|             |      |             |         | initiated by the      |
|             |      |             |         | Networx vendor        |
|             |      |             |         | require Agency        |
|             |      |             |         | consent prior to      |
|             |      |             |         | implementation.       |
|             |      |             |         | Changes are           |
|             |      |             |         | categorized as Normal |
|             |      |             |         | and Urgent            |
|             |      |             |         | (Emergency).          |
+-------------+------+-------------+---------+-----------------------+
|             |      | Within 2    | ≤ 2     |                       |
|             |      | hours for a | hours   |                       |
|             |      | urgent      |         |                       |
|             |      | priority    |         |                       |
|             |      | change      |         |                       |
+-------------+------+-------------+---------+-----------------------+
| Time To     | With | 4 hours     | ≤ 4     | The contractor shall  |
| Restore     | out\ |             | hours   | calculate Time to     |
| (TTR)       | Disp |             |         | Restore (TTR) as the  |
|             | atch |             |         | elapsed time between  |
|             |      |             |         | the time a service    |
|             |      |             |         | outage is recorded in |
|             |      |             |         | the Trouble           |
|             |      |             |         | Management System and |
|             |      |             |         | the time the service  |
|             |      |             |         | is restored minus any |
|             |      |             |         | (1) time due to       |
|             |      |             |         | scheduled network     |
|             |      |             |         | configuration change  |
|             |      |             |         | or planned            |
|             |      |             |         | maintenance or (2)    |
|             |      |             |         | time, as agreed to by |
|             |      |             |         | the Government, that  |
|             |      |             |         | the service           |
|             |      |             |         | restoration of the    |
|             |      |             |         | service cannot be     |
|             |      |             |         | worked due to         |
|             |      |             |         | Government caused     |
|             |      |             |         | delays. Examples of   |
|             |      |             |         | Government caused     |
|             |      |             |         | delays include: 1)    |
|             |      |             |         | the customer was not  |
|             |      |             |         | available to allow    |
|             |      |             |         | the contractor to     |
|             |      |             |         | access the Service    |
|             |      |             |         | Delivery Point or     |
|             |      |             |         | other                 |
|             |      |             |         | customer-controlled   |
|             |      |             |         | space or interface;   |
|             |      |             |         | 2) the customer gave  |
|             |      |             |         | the contractor an     |
|             |      |             |         | incorrect address for |
|             |      |             |         | the SDP; 3) the       |
|             |      |             |         | customer failed to    |
|             |      |             |         | inform the contractor |
|             |      |             |         | that a security       |
|             |      |             |         | clearance was         |
|             |      |             |         | required to access    |
|             |      |             |         | the SDP or            |
|             |      |             |         | customer-controlled   |
|             |      |             |         | space; 4) or the      |
|             |      |             |         | Government required   |
|             |      |             |         | service at a remote   |
|             |      |             |         | site and agreed that  |
|             |      |             |         | a longer transit time |
|             |      |             |         | was required.         |
+-------------+------+-------------+---------+-----------------------+
|             | W    | 8 hours     | ≤ 8     |                       |
|             | ith\ |             | hours   |                       |
|             | Disp |             |         |                       |
|             | atch |             |         |                       |
+-------------+------+-------------+---------+-----------------------+

IV. Features

  ---------- ---------------------- ----------------------------------------------
  **ID       **Name of Feature**    **Description**
  Number**                          

  1          Biometric              The Networx vendor will provide Biometric
             Characteristics        authentication methods including iris scan,
                                    voice, and facial recognition, as required by
                                    the Agency

  2          Encryption/Digital     The Networx vendor will provide and support
             Signature Client       the encryption/digital signature client
             Software               software for the Agency designated POCs.

  3          E-Authentication       The Networx vendor will provide
             Training               E-Authentication training to Agency personnel
                                    as required. This includes but is not limited
                                    to user authentication, PKI, and CAs. The
                                    frequency and nature of training activities
                                    may vary according to Agency needs.

  4          Directory/Repository   The Networx vendor will develop, implement,
             Function               and maintain a Directory/Repository function
                                    that will support the PKI and/or other
                                    e-authentication mechanism chosen by the
                                    Agency.
  ---------- ---------------------- ----------------------------------------------

V.  Interfaces

Managed E-Authentication Service will support the User-to-Network
Interfaces (UNIs) defined in the following Sections, as applicable:

1.  Frame Relay Service (FRS)

2.  Asynchronous Transfer Mode Service (ATMS)

3.  Internet Protocol Services (IPS)

4.  Premises-Based IP-VPN Services (PBIP-VPNS)

5.  Network-Based IP-VPN Services (NBIP-VPNS)

```{=html}
<!-- -->
```
VI. Pre-cutover Activities

+-------------------+--------------------------+-----------------------+
| **Managed         |                          |                       |
| E-Authentication  |                          |                       |
| Service (MEAS)    |                          |                       |
| Checklist\*\      |                          |                       |
| **                |                          |                       |
|                   |                          |                       |
| **PRE-CU          |                          |                       |
| TOVER             |                          |                       |
|                   |                          |                       |
|                   |                          |                       |
|                   |                          |                       |
|               STA |                          |                       |
| TUS            ** |                          |                       |
+===================+==========================+=======================+
| Administrative    | Has an Agency Hierarchy  |                       |
|                   | Code (AHC) been provided |                       |
|                   | to the Networx vendor?   |                       |
+-------------------+--------------------------+-----------------------+
|                   | Have Local Government    |                       |
|                   | Contacts (recommend at   |                       |
|                   | least two per location)  |                       |
|                   | been identified and      |                       |
|                   | contact information      |                       |
|                   | provided?                |                       |
+-------------------+--------------------------+-----------------------+
|                   | Has a Project Specific   |                       |
|                   | Transition Plan          |                       |
|                   | Identifier been          |                       |
|                   | assigned?                |                       |
+-------------------+--------------------------+-----------------------+
|                   | Note (P_OPS) in the      |                       |
|                   | Agency Service Request   |                       |
|                   | Number (ASRN) if this is |                       |
|                   | parallel service         |                       |
+-------------------+--------------------------+-----------------------+
| Pr                | Has the underlying       |                       |
| e-Ordering/Design | access architecture been |                       |
| Decisions         | implemented?             |                       |
+-------------------+--------------------------+-----------------------+
|                   | What authentication      |                       |
|                   | protocols will the       |                       |
|                   | Agencies' devices        |                       |
|                   | support? (RADIUS,        |                       |
|                   | TACACS+, etc.)           |                       |
+-------------------+--------------------------+-----------------------+
|                   | Identify the assurance   |                       |
|                   | level that               |                       |
|                   | authentication services  |                       |
|                   | will be operated under.  |                       |
+-------------------+--------------------------+-----------------------+
|                   | Will a baseline          |                       |
|                   | assessment be performed? |                       |
|                   | This step is part of the |                       |
|                   | information gathering    |                       |
|                   | process that will need   |                       |
|                   | to be performed in       |                       |
|                   | coordination with the    |                       |
|                   | Networx vendor to        |                       |
|                   | complete an accurate     |                       |
|                   | design engineering       |                       |
|                   | strategy.                |                       |
+-------------------+--------------------------+-----------------------+
|                   | Have the Agency and      |                       |
|                   | Networx vendor agreed on |                       |
|                   | the design engineering   |                       |
|                   | and operational          |                       |
|                   | strategies?              |                       |
+-------------------+--------------------------+-----------------------+
|                   | Has the Agency security  |                       |
|                   | policy been reviewed in  |                       |
|                   | regard to user           |                       |
|                   | authentication policies? |                       |
+-------------------+--------------------------+-----------------------+
|                   | Follow any Agency        |                       |
|                   | specific guidelines on   |                       |
|                   | information systems and  |                       |
|                   | or services regarding    |                       |
|                   | certification and        |                       |
|                   | accreditation.\          |                       |
|                   | (Authority to Operate)   |                       |
+-------------------+--------------------------+-----------------------+
|                   | Verify the Networx       |                       |
|                   | Vendor supports the      |                       |
|                   | features and interfaces  |                       |
|                   | specific to the Agency's |                       |
|                   | application.             |                       |
+-------------------+--------------------------+-----------------------+
|                   | Token/Certificate        |                       |
|                   | requirements: Which      |                       |
|                   | method will be used? Are |                       |
|                   | Hardware tokens or       |                       |
|                   | smartcards required?     |                       |
|                   | Will certificates be     |                       |
|                   | issued to users or       |                       |
|                   | equipment?               |                       |
+-------------------+--------------------------+-----------------------+
|                   | Determine HW/SW changes  |                       |
|                   | necessary in the local   |                       |
|                   | applications to          |                       |
|                   | accommodate the planned  |                       |
|                   | cutover strategy         |                       |
+-------------------+--------------------------+-----------------------+
|                   | Determine the Parallel   |                       |
|                   | Operations Period -- all |                       |
|                   | orders for parallel      |                       |
|                   | service will have to be  |                       |
|                   | so noted in the ASRN.    |                       |
+-------------------+--------------------------+-----------------------+
|                   | Identify timeframe for   |                       |
|                   | returning old tokens to  |                       |
|                   | the incumbent or         |                       |
|                   | revoking incumbent based |                       |
|                   | certificates.            |                       |
+-------------------+--------------------------+-----------------------+
|                   | Prepare Fall-Back plan:  |                       |
|                   |                          |                       |
|                   | If software changes are  |                       |
|                   | required, a fallback may |                       |
|                   | include re-installing    |                       |
|                   | original software. If    |                       |
|                   | using a custom Root      |                       |
|                   | Certificate Authority,   |                       |
|                   | the trusted root servers |                       |
|                   | may need updated.        |                       |
+-------------------+--------------------------+-----------------------+
| User Training     | Have users received      |                       |
|                   | training on trouble      |                       |
|                   | reporting, Network       |                       |
|                   | Inventory Code (NIC),    |                       |
|                   | Portal and toll free     |                       |
|                   | reporting, Token         |                       |
|                   | ownership, Token         |                       |
|                   | operation, key           |                       |
|                   | management and           |                       |
|                   | protection, etc.?        |                       |
+-------------------+--------------------------+-----------------------+
| Installation      | Have Certificates, or    |                       |
|                   | software been installed  |                       |
|                   | and tested? Has          |                       |
|                   | directory information    |                       |
|                   | been completed?          |                       |
+-------------------+--------------------------+-----------------------+
|                   | Have tokens or           |                       |
|                   | smartcards been          |                       |
|                   | provided?                |                       |
+-------------------+--------------------------+-----------------------+
|                   | Have any administrative  |                       |
|                   | or reporting portals     |                       |
|                   | been set-up?             |                       |
+-------------------+--------------------------+-----------------------+
|                   | Have authentication      |                       |
|                   | server information, such |                       |
|                   | as IP addresses or host  |                       |
|                   | names, been loaded to    |                       |
|                   | Agency hardware and      |                       |
|                   | software?                |                       |
+-------------------+--------------------------+-----------------------+
| Security          | Provide all new Token or |                       |
| Management        | Certificate information  |                       |
|                   | to the affected          |                       |
|                   | Management Organization. |                       |
+-------------------+--------------------------+-----------------------+
| Documentation     | Provide all security     |                       |
|                   | procedures to site       |                       |
|                   | personnel and to the     |                       |
|                   | affected Management      |                       |
|                   | Organization.            |                       |
+-------------------+--------------------------+-----------------------+
| Execute Tests     | See Examples Below of a  |                       |
|                   | Networx Vendor Networx   |                       |
|                   | Services Verification    |                       |
|                   | Test Plan: Have the      |                       |
|                   | Agency LGC or Network    |                       |
|                   | Management Organization  |                       |
|                   | and Networx vendor       |                       |
|                   | reviewed the results of  |                       |
|                   | this testing to insure   |                       |
|                   | all is ready for the     |                       |
|                   | actual cutover?          |                       |
+-------------------+--------------------------+-----------------------+
| Conduct           | See Examples Below of a  |                       |
| Pre-Cutover       | Networx Vendor Networx   |                       |
| Testing           | Services Verification    |                       |
|                   | Test Plan:               |                       |
+-------------------+--------------------------+-----------------------+

\*Use this checklist in conjunction with Generic Cutover Checklist

VII. Test Examples:

The Agency should insure that all of the features and functions ordered
with the service were delivered and are operational within the seventy
two hour acceptance window. The Networx vendors are to perform
verification testing on the service for each order at the initial
service delivery to an Agency per the Networx service verification test
plan.

-   Verify connectivity via the internet to the service provider portal.

-   Verify the issuance of certificates / tokens by examining the issued
    inventory

-   Verify the ability to assign an available certificate / token by
    binding one to a test user.

-   Verify the ability to suspend an available certificate / token.

-   Verify the ability to revoke a certificate / token.

VIII. Cutover Activities

  --------------------- ------------------------ ------------------------
  FINAL CUTOVER                                  

  Communicate schedule                           
  and status with                                
  stakeholders                                   

  Obtain authorization  GO/NO-GO notification    
  to proceed or delay                            

  Activate new                                   
  service(s)                                     

  Conduct acceptance                             
  test                                           

  The Agency should     Acceptance period of 72  
  notify Networx vendor hours begins upon        
  and TCC of rejection  receipt of the Service   
  of service within 72  Order Completion Notice  
  hours of cutover      (SOCN)                   

  Begin production                               

  Obtain signoffs for                            
  cutover completion                             

  Deactivate legacy                              
  service                                        
  --------------------- ------------------------ ------------------------

IX. Transition Cutover Contact List

# Transition Cutover Contact List {#transition-cutover-contact-list .CH_2}

#    Agency Name:    {#agency-name .H3}

#  {#section-20 .H3}

#  {#section-21 .H3}

# Local Government Contact Personnel: (Include a contact at the CSO Office) {#local-government-contact-personnel-include-a-contact-at-the-cso-office .H3}

Name:   Name:  

Title/Function:   Title/Function:   

Location:    Location:   

Mobile #:   Mobile #:  

Office #:  Office # 

Email:   Email:  

#  Networx Vendor:      {#networx-vendor .H3}

#  {#section-22 .H3}

#  {#section-23 .H3}

# Networx Vendor Key Contact Personnel: {#networx-vendor-key-contact-personnel .H3}

Name:   Name:  

Title/Function:   Title/Function:   

Location:    Location:   

Mobile #:   Mobile #:  

Office #:  Office # 

Email:   Email:  

#  {#section-24 .CH_2}

# Transition Cutover Contact List {#transition-cutover-contact-list-1 .CH_2}

(continued)

#     CPE Vendor:    {#cpe-vendor .H3}

#  {#section-25 .H3}

#  {#section-26 .H3}

# CPE Vendor Key Contact Personnel: {#cpe-vendor-key-contact-personnel .H3}

#  {#section-27 .H3}

Name:   Name:  

Title/Function:   Title/Function:   

Location:    Location:   

Mobile #:   Mobile #:  

Office #:  Office # 

Email:   Email:  

#  Access Vendor:    {#access-vendor .H3}

#  {#section-28 .H3}

#  {#section-29 .H3}

# Access Vendor Key Contact Personnel: {#access-vendor-key-contact-personnel .H3}

Name:   Name:  

Title/Function:   Title/Function:   

Location:    Location:   

Mobile #:   Mobile #:  

Office #:  Office # 

Email:   Email:  

CUTOVER ISSUES LOG

  ----------------- --------------- -----------------------------------------
  **ISSUE \#**      **INITIATOR**   **ISSUE SUMMARY**

                                    

  Priority/Impact   Owner           Target Resolution Date

                                    

  Status            Status Date     Resolution

                                    
  ----------------- --------------- -----------------------------------------