C001 SMIT CDRL_Network Transition and Convergence Plan.docx
DOCX document 33 KB Posted
- Solicitation number
- N00039-18-R-0005
About this file
This document contains a Contract Data Requirements List (CDRL) and details of a related federal contract opportunity. The CDRL outlines requirements for a Network Transition and Convergence Plan deliverable, including components of the plan, assumptions, organizational structure, risk management approach, and dependencies. It requires the plan to be submitted within 30 business days of request and updated every 15 business days until approved.
The related federal contract opportunity is a pre-solicitation notice for the Service Management, Integration and Transport (SMIT) requirement under the Next Generation Enterprise Network Recompete. The Space and Naval Warfare Systems Command intends to release a request for proposal on or around July 31, 2018, with a closing date of October 1, 2018. The contract will be awarded as a single-award IDIQ with both fixed-price and cost-reimbursement line items. The period of performance is a five-year base with three one-year options. The services required include network operations, service operations, service integration, and transport/productivity support for the Navy Marine Corps Intranet, Outside Continental United States Enterprise Network, and Marine Corps Enterprise Network.
View the file
Other files
Show 40 more
Latest 50 of 77 listed here. See the rest on GovTribe.
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
CONTRACT DATA REQUIREMENTS LIST
(1 Data Item) Form Approved OMB No. 0704-0188
Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO.
B. EXHIBIT
A
C. CATEGORY:
TDP ____ TM ____ OTHER __X_______
D. SYSTEM/ITEM
NEN
E. CONTRACT/PR NO.
Service Management, Integration and Transport (SMIT)
F. CONTRACTOR
1. DATA ITEM NO
C001
2. TITLE OF DATA ITEM
Network Transition and Convergence Plan
3. SUBTITLE
4. AUTHORITY (Data Acquisition Document No.)
N/A
5. CONTRACT REFERENCE
PWS Paragraph 5.2.2.b
6. REQUIRING OFFICE
PMW 205
7. DD250 REQ
XX
9. DIST. STATEMENT
REQUIRED
F
10. FREQUENCY
ASREQ
12. DATE OF FIRST SUBMISSION
See BLK 16
14. DISTRIBUTION
a. ADDRESSEE
b. COPIES
8. APP CODE
A
11. AS OF DATE
N/A
13. DATE OF SUBSEQUENT SUBMISSION
See BLK 16
DRAFT
FINAL
| Reg |
| Repro |
16. REMARKS:
Block 4: Contractor format is acceptable; however, it is expected that the deliverable will be formulated utilizing industry best practice and contain all required items listed below.
Transition and Convergence POA&M/Schedule Develop a summary-level milestone chart graphically depicting the schedule of events associated with accomplishing each Assumption of Full Operational Responsibility (AFOR) milestone.
Develop a detailed POA&M including the schedule of events associated with accomplishing each transition event. Include:
1. Milestones to achieve AFOR dates
2. Transition and/or Convergence activities, description and durations
3. Schedule of all deliveries due during Transition or Convergence period, including for each event, Readiness to Transition / Converge Package and Transition / Convergence Close-out Report
4. Transition / Convergence kick-off meeting (may be separate)
5. Transition / Convergence close-out meeting (may be separate)
6. Readiness to Transition/Converge Review (RTCR) meeting milestones
7. SMIA activities
8. Knowledge transfer activities
9. Change management activities, as needed
10. Critical path
11. Management activities associated with Transition
12. Others, as defined by the Contractor
13. The timeline of the updated delivery of the following CDRLs with initial being during convergence:
a. A015 Program Protection Implementation Plan (PPIP)
b. A020 Monthly Status Report
c. A023 Core Build Plan
d. A024 Continual Service Improvement Report
e. A040 Service Management Integration Activity (SMIA) Report
f. A051 Service Design Package (SDP)
g. A052 Systems Engineering Management Plan (SEMP)
h. A062 Asset Management Implementation Plan (AMIP) Transition and Convergence Plan components include:
1. The basis for development of this plan, including assumptions, such as experience, results of surveys or any other source of information used to develop the plan
2. Organizational structure to include lines of control, roles and responsibilities and interfaces with the Government
3. Dependencies (predecessor/successor relationships)
4. Dependencies on Government actions
5. Risk Management of Transition and/or Convergence events
6. Pre-convergence survey results including regions and sites visited, organizations, agencies and personnel engaged, observation data, knowledge obtained, assessment and analysis results
7. Alternatives or exceptions to the NMCI service model and Service Level Requirements (SLRs), if needed
8. Methods to ensure readiness for start of executing under the NMCI business model for each convergence event
9. Planned outcomes and metrics that will be used to show progress toward and achievement of convergence events
10. Dependencies (predecessor/successor relationships); including Government actions
11. Service Management Integration Activities (SMIA) and integration with the Government’s Operating Model
12. Transition of software licenses, data, assets, supplier agreements, warranties, maintenance agreements, work-in-progress (open projects, tickets, etc.), and facilities/property, as applicable
13. Any technical or process changes needed to complete convergence and meet SMIT minimum contract requirements and SLRs following SMIT change management processes; if technical changes are necessary, the plan shall conform to the Contractor’s approved Network Transformation/Modernization Process (CDRL A053)
14. Asset inventory and delivery of inventory data in accordance with PWS Section 3.3.7.4.3 Asset Management for each convergence event
15. Service Operations in accordance in accordance with SMIT PWS Section 3.3.5.1
16. Service Desk in accordance with SMIT PWS Section 3.3.2.1
17. Collaboration with other service providers (Government and Contractor) and/or organizations to support convergence
18. Planned outcomes and metrics that will be used to show progress toward AFOR References Refer to the following documents (not limited to) to assist with planning the convergence:
1. Government Furnished Facilities (GFF)
2. CDRLs
3. Process Guides
Block 8: The Government shall have 30 business days after receipt of the Network Transition and Convergence Plan to review and comment.
Block 9: Distribution Statement F. Further distribution only as directed by PMW 205 or higher DoD authority; 1 Jun 2018.
Block 12: Submit the Network Transition and Convergence Plan no later than 30 business days after request.
Block 13: Revise and resubmit the updated Network Transition and Convergence Plan for Government approval 15 business days after receiving comments. Subsequent submissions are as required until is approved.
Block 14: Electronically delivered-reproducible Microsoft Office format (unless otherwise approved by the Government) to the PMW 205 CDRL Management Portal.
See BLK 16
15. TOTAL
G. PREPARED BY
PMW-205
H. DATE
18 Oct 2018
I. APPROVED BY
J. DATE
DD FORM 1423-1, FEB 2001 PREVIOUS EDITION MAY BE USED PAGE 3 OF 3
File details come from the government source that posted it. Updated .