4.0Implementation (C.4.4)
The following requirements will apply for those implementation activities that are deemed by the Government to be sufficiently important or complex as to require them, such as large implementation projects or the first implementation of a new or enhanced service. The Government does not anticipate applying these requirements to the routine implementation of limited quantities of mature services.
4.1Implementation Plan (C.4.4.1)
The contractor shall deliver an ImP within 15 calendar days after receiving notice from the Government to begin a specific implementation project. The contractor shall prepare a separate ImP for each set of services to be implemented. Each ImP shall document the contractor’s implementation strategies, including coordination with the user agency(ies). The contractor shall present its approach to optimization of access service (Section C.4.1.6) based on the available traffic information and the existing access circuit arrangements. The ICC, in coordination with the affected agency or agencies, will review the ImP within 15 days after its submission. The contractor shall submit a revised ImP within 15 days after receiving the review from the ICC. The ICC intends to approve a final ImP within 15 days after receiving the revised ImP. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements.
Each ImP shall include an analysis of the key areas of risk entailed in the implementation activities. Each ImP shall describe the contractor’s approach to minimize any impact in order to make the implementation as easy as possible to the users. Each ImP shall address the criticality of the services being implemented and describe the options that the contractor intends to use to assure that mission-critical requirements will be met.
Each ImP shall include a general description of the tasks required to prepare locations for the implementation. It shall describe the means the contractor will use to verify that services are performing satisfactorily after the implementations are completed.
For new or enhanced service(s), the ImP shall describe how, prior to implementation, the contractor will ensure that the service(s) and any necessary support systems (including service ordering and automated billing) will operate correctly. The ImP shall describe how the Government will be able to verify correct operation of the service(s) and support systems prior to implementation. The contractor may use OCDs, trials, or other means to support these requirements.
In conjunction with the user agencies, the ICC will determine the sequence in which agencies will implement their services based on the agencies’ missions. This sequence will then be coordinated with the contractor. The contractor shall incorporate this sequence into its ImP.
The ImP shall include details of:
(a)Implementation schedules
(1)Phasing of service types being implemented
(2)Identifying service locations for the implementations
(3)Identifying the lead-times required for implementations
(4)Identifying the month in which services at each location will be implemented
(5)Identifying the steps required to prepare the locations for the implementations
(6)Identifying the steps required to complete the implementations
(7)Identifying how each type of existing service may be affected during the implementation activities
(b)Identification of the responsible contractor’s subcontractors at a location
(c)Type of Government equipment involved at each location in which services will be implemented
(d)Agency controlling the Government equipment
(e)Originating traffic at each location
(f)Logistics
(g)Emergency procedures
(h)Creation and use of a database (as described in Section C.4.4.5.4)
(i)New construction
(j)Circuit grooming needed at each location
(k)Access service optimization (as described in Sections C.3.8.2 and C.4.1.6
(l)Optimize new services with existing services of the same agency during implementation
(m)Security clearances required for personnel involved in the implementation project
Sprint will develop an Implementation Plan (ImP) for each service to be implemented within 15 calendar days after receiving word from the Government to begin a specific implementation project. Each ImP will document Sprint's implementation strategies, including coordination with the user agency(ies). Sprint will also present our approach to optimization of access service based on the available traffic information and the existing access circuit arrangements. A local committee (Section C.4.4.5.7) will be responsible for reviewing and updating the ImP. The ICC , in coordination with the affected agency(ies) will review the ImP within 15 days after submission, Sprint will submit a revised ImP within 15 days after receiving the review from the ICC. The Government intends to approve the final ImP within 15 calendar days after receiving the revised ImP.
Sprint has a proven track record of successful customer moves. Each ImP will contain all schedules, exceptions, any deviations from the generic procedures in the location-specific implementation plans, Sprint’s Implementation Verification Test Plans (Section C.4.4.4) and an analysis of the key areas of risk entailed in the implementation activities, specific to the implementation of services at the location. Each ImP will be available to the ICC via the CNM function described in Section C.3.2.7.1, organized by months and updated daily, and will describe Sprint's approach to minimizing any impacts to make implementation as easy as possible for users. Each ImP will address the criticality of the services being implemented and will describe the options Sprint intends to use to assure that mission-critical requirements will be met. Each ImP will include a general description of the tasks required to prepare locations for implementation. It will also describe the means Sprint will use to verify that services are performing satisfactory after implementations are completed. For new or enhanced service(s), each ImP will describe how prior to implementation, Sprint will ensure that the service(s) and any necessary support systems (including service ordering and automated billing) will operate correctly. The ImP will describe how the Government will be able to verify correct operation of the service(s) and support systems prior to implementation. In conjunction with user agencies, the ICC will determine the sequence in which agencies will implement their services, based on the agencies' missions. This sequence will then be coordinated with Sprint, and Sprint will incorporate the sequence into our ImP.
Sprint’s initial version of each ImP will begin with the month in which the first implementation activities are scheduled to occur. Sprint will develop an ImP which fulfills the details and requirements specified for implementation, whether domestic or international. The ImP will be similar to the previously discussed ImP for migrations (reference
Section 3.1) and the CTP for transitions (reference Section 2.2).
Sprint will provide weekly summaries of implementation activities to the ICC regarding the progress of pending and concluded implementation activities and the status of activities delineated in each ImP. At a minimum, these weekly reports will contain the following information:
• Implementation schedules, including
1. Phasing of service types being implemented
2. Identifying service locations for the implementations
3. Identifying the lead-times required for implementations
4. Identifying the month in which services at each location will be implemented
5. Identifying the steps required to prepare the locations for the implementations
6. Identifying the steps required to complete the implementations
7. Identifying how each type of existing service may be affected during the implementation activities
• Identification of the responsible Sprint subcontractors at a location
• Type of Government equipment involved at each location for which services will be implemented
• Agency controlling the Government equipment
• Originating traffic at each location
• Implementation logistics
• Implementation emergency procedures
• Creation and use of a database (as described in Section C.4.4.5.4)
• New construction related to implementation requirements
• Circuit grooming needed at each location
• Access service optimization (as described in Sections C.3.8.2 and C.4.1.6
• Optimizing new services with existing services of the same agency during implementation
• Security clearances required for personnel involved in the implementation project
Representatives of Sprint will meet with appropriate Government representatives as deemed necessary by the ICC and Sprint to apprise the Government of progress in completing the implementation schedules and to obtain approval for any type of changes to the implementation activities and schedules as they occur. Sprint will be responsible for coordinating all meetings and establishing an agenda. Where implementation activities at jointly served locations are involved, joint meetings will be held among all interested Sprint and Government personnel.
4.2Implementation Management Plan (C.4.4.2)
The contractor shall develop an ImP consistent with the contractor’s Government approved ImP (Section C.4.4.1) for each implementation project. Each ImP shall serve as a progress report, master log, and a working blueprint for the contractor’s day-to-day activities during the implementation of services at individual users’ locations. The initial version of each ImP shall be submitted to the ICC by the contractor after ImP approval, but no later than 50 calendar days prior to the first scheduled implementation activity for the contractor. A local committee (Section C.4.4.5.7) shall be responsible for reviewing and updating the ImP. The Government intends to approve the final ImP within 30 calendar days after receiving the revised ImP. With the approval of the ICC, implementation activities may begin before approval of the ImP.
Each ImP shall contain all schedules, exceptions, and any deviations from the testing procedures contained in the contractor’s Implementation Verification Test Plans (Section E.2.2.2.3). The ImP shall contain all proposed changes to the existing access service facilities to optimize access service as described in Section C.4.1.6. The contractor shall make the data in each ImP available to the ICC online. Refer to Section C.2.3.7 for the media of delivery and Section F for other deliverable requirements. The contractor shall control access to the ImP through the use of appropriate security techniques such as identification and authentication, for authorized individuals. The ImP shall be organized by weeks, and updated daily. The contractor’s initial version of each ImP shall begin with the month in which the first implementation activities are scheduled to occur.
No later than the second Government business day following the weekly reporting interval, the contractor shall provide weekly summaries of implementation activities to the ICC via the Internet regarding the progress of pending and concluded implementation activities and the status of activities delineated in each ImP. These weekly reports shall contain the following information:
(a)Count and identification of services implemented since last report
(b)Locations at which services were implemented since last report
(c)Number of locations remaining to be completed for all services scheduled for implementation
(d)Number of services remaining to be completed for all services scheduled for implementation
(e)Comparison of services implemented to date with the number and locations of services proposed in the latest coordinated and approved implementation schedule
(f)Description of services (and their locations) for which implementation is in jeopardy of not meeting the current implementation schedule
(g)During the weekly reporting period, reports of service impairment or degraded service quality (together with service failures and service blockage events)
(h)Discussion of any issues affecting the timely completion of all implementation activities
Representatives of the contractor shall meet with appropriate Government representatives as deemed necessary by the ICC and the contractor to apprise the Government of progress in completing the implementation schedules and to obtain approval for any type of changes to the implementation activities and schedules as they occur. The contractor shall be responsible for coordinating all meetings and establishing an agenda. Where implementation activities at jointly served locations are involved, the contractor shall participate in joint meetings held among all interested contractors and Government personnel.
Sprint will develop and maintain an Implementation Management Plan (ImP) consistent with Sprint’s Government-approved CTP. The ImP will serve as a progress report and master log as well as a working blueprint for Sprint’s day-to-day activities during the implementation of services at individual locations. Sprint will submit the initial version of the ImP to the ICC no later than 50 calendar days prior to the first scheduled movement of traffic to Sprint’s network. A local committee will be responsible for reviewing and updating the ImP. Sprint understands the Government intends to approve the initial ImP within 30 calendar days after its submission.
Sprint’s site-specific plans will comprise the ImP and will contain all schedules, exceptions, deviations from the generic procedures in the location-specific plans contained in Sprint’s Implementation Verification Test Plan. Sprint will ensure that the ImP contains all proposed changes to the existing access facilities to optimize access service as described in Section C.4.1.6 of the RFP. The ImP will contain cutover contingency plans for each location at which services are implemented to Sprint’s network, and will be available to the ICC on-line. Access to the ImP will be controlled by Sprint and include the use of appropriate security techniques such as identification and authentication of authorized users. The ImP will be organized by weeks, and updated daily. Sprint’s initial version of its ImP will begin with the month in which the first implementation activities are scheduled to occur. Sprint understands that implementation activities may begin before ImP approval, as long as the ICC approves.
No later than the second Government business day following the weekly reporting interval, Sprint will provide weekly summaries of implementation activities to the ICC.. The summaries will include the progress of pending and concluded implementation activities, and the status of activities delineated in the ImP. As a minimum, these weekly reports will contain the following information, distinguished by service type and agency:
• Count and identification of services cut over since last report
• Locations at which services were cut over since last report
• Number of locations remaining to be completed for all services scheduled for implementation
• Number of services remaining to be completed for all services scheduled for implementation
• Comparison of services cut over to date with the number and locations of services proposed in the latest coordinated and approved implementation schedule
• Description of services (and their locations) for which cutover is in jeopardy of not meeting the current implementation schedule
• During the weekly reporting period, reports of service impairment or degraded service quality (together with service failures and service blockage events)
• Discussion of any issues affecting the timely completion of all cutover activities.
The cutover of a location requires close coordination between parties and clear understanding of the roles and responsibilities of each of the parties supporting the cutover. Sprint’s OIM, with the support of the LGC/DAR is the party primarily responsible for ensuring a successful cutover of each location.
At the earliest possible time after the start of implementation, the Sprint OTM representatives responsible for the cutover of the Government locations will establish and maintain direct lines of communication with the local representatives of the organizations involved in activities supporting site cutover. The open communication channels ensure that any unique site-specific considerations that could adversely affect the cutover are identified early to ensure their effect is minimal, and that Sprint’s plans and procedures for coordinating cutover are understood by all responsible parties. Sprint will also be responsible for coordinating all meetings and establishing meeting agendas.
The local cutover committees will meet, as necessary, at least 60 calendar days before their scheduled cutover dates. Sprint will use the meetings to resolve all cutover issues with committee members. The local cutover committee meetings will be held at locations coordinated with the LGC. They may alternatively be held by telephone for those locations where the cutover is expected to be straightforward. When scheduling local cutover committee meetings, Sprint will make all attempts, when practical, to minimize travel demands on Government personnel and personnel from other organizations outside the local commuting area around the cutover sites.
At all local cutover committee meetings, for the location of interest, Sprint will review the Site-Specific Cutover Plan. To facilitate the timely review and approval of the plans, Sprint will complete drafts of the plans 60 calendar days before the scheduled cutover date. Therefore the local cutover committees will have time to become familiar with Sprint’s cutover plan for the location, prior to the first formal meeting of the local cutover committee.
Sprint will meet with appropriate Government representatives as necessary to apprise the Government of progress in completing the implementation schedules and to obtain approval for any changes to the implementation activities and schedules as they occur. Sprint will also participate in joint meetings among all interested contractors and Government personnel where implementation activities at jointly served locations are involved.
4.3Private Dialing Plan for Implementation (C.4.4.3)
In coordination with the Number Plan Administrator function (Section C.3.2.7.4), the contractor shall develop and administer a plan for implementing stations that require non-commercial agency-specific private numbers (Section C.3.2.7.4.2(a)). This private dialing plan shall be provided to the ICC within 15 calendar days after receiving notice from the Government to begin implementation activities. The dialing plan shall be based on the information provided to the contractor by the Government identifying the service(s) on particular networks to be implemented. The ICC, in conjunction with advice from affected agencies, will provide a review on the dialing plan within 15 days after its submission. The contractor shall submit a revised dialing plan within 15 days after receiving the review from the ICC. The ICC, in conjunction with advice from affected agencies, intends to approve a final dialing plan 15 days after receiving the revised dialing plan. Refer to Section C.3.2.7 for media of delivery and Section F for other deliverable requirements.