u.s. general services administration federal acquisition service network services 2020 enterprise...
TRANSCRIPT
U.S. General Services Administration
Federal Acquisition Service
Network Services 2020 Enterprise Infrastructure Solutions (EIS)
Government/Industry Information ExchangeApril 27, 2015: Session 1
Integrated Technology ServicesFederal Acquisition ServiceGeneral Services Administration
April 2015
Fred Haines, EIS Program Manager
Ray Lewis, EIS Deputy Program Manager
Tim Horan, EIS Contracting Officer
Michelle White, EIS Contract Specialist
Robert Sodano, Jim Russo, Ward Fisher, Dinaira Borba, Terri Stoddard – Team Leads
Introductions
2
GSA is a provider of Federal demand Provide a total solution telecommunications vehicle for all Government
clients
o Add new capabilities (cloud, managed mobility, labor…)
o Provide agility, flexibility, scope, and contractual elements sufficient to satisfy today’s complex requirements
Reduce redundancy in Government contracting
Combining local (regional) and enterprise contracts
Leverage the Government’s buying power
Drives cost savings for all agencies
Adequate competition pool
Support for Federal mandates and regulations (“Safe Harbor”)
EIS Objectives
3
Industry RFP Comments by Section
4
RFP Section Number of CommentsSection A 6Section B 171Section C 505Section D 3Section E 24Section F 9Section G 206Section H 61Section I 50Section J 85Section K 1Section L 67Section M 29
EIS Characteristics
Fewer mandatory requirements Fewer deliverables Time & Materials 15-year period of performance Core-Based Statistical Areas (CBSAs) Construction clauses No compliance matrix:
Contractors must agree to all RFP Terms and Conditions or take exception prior to proposal submission
Requirement for task orders and DPAs Minimize contract modifications:
Use of catalogs Task Order Unique CLINs (TUCs) for solutions
5
6
Draft EIS RFP Feedback – Pricing
Pricing Comments by Draft RFP Section
Majority of comments address price tables and specific services A number of comments address new EIS pricing concepts:
Pricing principles (PHubs, PCLs, access pricing, etc.) Catalogs
Voice (with associated access) has the most comments for any single service
7
Section Topic # Questions
B Overall 4B.1.1 Overview 1B.1.2 General Pricing Principles 38B.1.3 Catalog Pricing Requirements 11B.2 Pricing Tables 109B.3 National Security Emergency Preparedness 1B.4 General Pricing and Other Requirements 7Total 171
Common Pricing Themes
Industry requested additional clarification and detail on: Pricing Hub (PHub) and Physical Concentration Location (PCL) Minimum entry criteria:
• Core-Based Statistical Areas (CBSAs)• Mandatory services
Optional services criteria for acceptance Required CLINs to be priced per service:
• Bandwidth (BW)• Features
Voice service Catalogs:
• Service Related Equipment (SRE)• Cloud Services• Commercial Mobile Satellite Service• Wireless Service (MMS) • Managed Security Services (MSS)
8
9
Draft EIS RFP Feedback – Technical
Mandatory and Optional EIS Services
10
Service Area Service (Mandatory services are in red)Data Services Virtual Private Network Service (VPNS), Ethernet
SONET, OWS, Private Line Service, Dark Fiber, IPS
Voice Services Voice ServiceCSDS, Toll Free, IPTel
Contact Center Services Contact Center Services
Data Center Services Data Center Services
Cloud Services Infrastructure as a Service, Platform as a Service, Software as a Service, Content Delivery Network Services
Wireless Services Wireless Service
Satellite Service Satellite Service
Managed Services Managed Network ServiceWeb Conferencing Service, Unified Communications Service, Managed Trusted Internet Protocol Service, Managed Security Services, Managed Mobility Service, Audio conferencing, Video Teleconferencing
Service Related Equipment Equipment
Service Related Labor Labor
Cable and Wiring Cable and Wiring
Access Arrangements Access Arrangements
Comments by Technical Service
Cloud Services CommentsIaaS 85PaaS 9SaaS 5CDNS 4Total 103
Managed Services CommentsMNS 15Web Conferencing 9UCS 41MTIPS 7MSS 23Managed Mobility 16Audio Conferencing 10Video Conferencing 19Total 140
Sections CommentsBackground 21SDN 6Security and National Policy 12VPNS 42Ethernet 29OWS 8PLS 10SONET 13Dark Fiber 8IPS 10Voice Basic 22CSDS 5Toll Free Service 7IPTel 17Contact Center Service 14Colocated Data Center 2Wireless 3Commercial SatCom 4SRE 2SRL 1Cable and Wiring 1Access Arrangement 17Transition and 508 8Total 262
505 Total Comments
11
Summary of Technical Comments
We appreciate the identification of obsolete language that appeared in the draft (references to dial-up and PVCs)
We received advice on making some features and capabilities optional instead of mandatory:
Continued viability of legacy capabilities Commercial availability of new capabilities
We received some suggested changes to RFP language to make the Government’s intent more clear
12
Common Technical Themes
GSA should not over-complicate or over-specify its requirements
Industry is moving away from circuit-switched services (TDM) and moving to IP solutions: The demand for TDM services is dropping TDM services may not be commercially available in the future
13
Planned Technical RFP Changes
No major changes to mandatory service requirements: VPNS, Ethernet, Voice, and Managed Network Services will
remain mandatory
Correct/delete obsolete requirements Complete or consolidate service requirements:
Voice MTIPS Wireless Managed Network Services
Relax requirements for some mandatory service features and capabilities
14
15
Draft RFP Feedback – Management and Operations
Summary of MOPS Comments by Impact
Section Number
SectionName
TotalComments
G.1 Introduction 1
G.2 Contract Administration 7
G.3 Ordering 36
G.4 Billing 30
G.5 BSS 35
G.6 Service Assurance 8
G.7 Inventory Management 14
G.8 SLA Management 50
G.9 Program Management 9
G.10 Training 10
G.11 NS/EP 4
G.12 Sustainability 2
E Inspection & Acceptance 24
J.2 CDIP 62
Total (All MOPS Sections) 313
16
Common MOPS Themes
Ordering: Clarify the distinction between Task Orders and Service Orders
SLA Management: Concerns with performance standards (KPIs), provisioning
categories, and automated credits
BSS Requirements: Concerns with the government-specific BSS requirements (as
opposed to commercial offerings) and their cost implications
BSS Inspection and Acceptance: Concerns with the BSS testing timeframes
Contractor Data Interaction Plan (CDIP): Prefer vendor-defined data formats and government-defined
application programming interfaces
17
Key Actions
SLA Management: Automated (Proactive) Credits: Primary Concern:
• Industry anticipates many challenges implementing the automated credits requirement
GSA Action:• Remove automated/proactive credit requirements• Evaluate SLA credit process based on customer needs and
government systems capability
Data Dictionary: Data Elements: Primary Concern:
• Provide greater clarity for data field definitions GSA Action:
• Assess and improve data field definitions for all data elements in the Contractor Data Interaction Plan (CDIP)
18
19
Questions
Next Steps
One-on-one industry meetings: In person or via remote conference
60 minutes
May 28 meeting: Further discussion of RFP updates
June 30 meeting: Proposal instructions and timing
20