A - PM GSM AoS Discussion v3 Read-Only .pdf

A Combat Support AgencyA Combat Support Agency

Global Information Grid (GIG) Services Global Information Grid (GIG) Services

Management (GSM)Management (GSM)

Mr. James TravisMr. James Travis

PMPM--GSMGSM

28 June 201028 June 2010

GSM RFP Requirements

GSMGSM--O, GSMO, GSM--ETI, GSMETI, GSM--P&SP&S

A Combat Support Agency

GSM Acquisition Objectives

• GSM enterprise level objectives:

– Replace DGS service capabilities with equal or better capabilities

– Align GSM requirements and capabilities based on risk analysis and mitigation

– Support DoD and DISA objectives and plans for future technical integration of networking capabilities

– Use competitive procedures where possible

– Obtain better efficiency in use of funds for services

– Apply ITIL® and comparable best practices to standardize common technical practices

– Shift to performance-based practices where practicable

– While also supporting DoD/DISA goals for subcontracting, reduction of T&M services, use of Wounded Warrior services, etc

GSM Work Allocation

GSM-O Acquisition Objectives

• GSM-O objectives :

– Attain all of the GSM enterprise objectives, plus –

– Provide operations services that integrate smoothly with ETI services

– Mitigate risks of transition period through planning and execution

– Focus on shift to performance-based practices

– Continue to obtain best prices for Warranty Maintenance Agreement support from equipment vendors

– Manage transition of spare/repair parts system from Government-operated to Contractor-operated

– Adapt scope of support as DISN convergence activities integrate capabilities and services

GSM-ETI Acquisition Objectives

• GSM-ETI objectives :

– Attain all of the GSM enterprise objectives, plus –

– Provide ETI services that integrate smoothly into the operations support environment

– Attain some degree of continuity of support while using required fair-opportunity competition procedures

– Focus on shift to performance-based practices

– Adapt scope of support as DISN convergence activities integrate capabilities and services

GSM-P&S Acquisition Objectives

• GSM-P&S objectives :

– Attain all of the GSM enterprise objectives, plus –

– Provide P&S services that can smoothly complement the operations support and engineering environments

– Attain some degree of continuity of support while using required fair-opportunity competition procedures

Performance-Based Context

• Performance-based services are characterized by –

– Outcomes oriented rather than Inputs oriented

– Focus on What-to-do not How-to-do

– Uses measurable standards to determine when performance is satisfactory

• May use Fixed Price contract structure when historical data supports that type of pricing; otherwise some type of Cost-Plus pricing – but not Time and Materials (that is inputs-oriented)

• Requires customer to decide required outcomes in advance;

limits short-term flexibility to redirect the contractor’s work

• One approach does not fit all: some requirements and contexts do not support use of performance-based services

– E.g. Emergency Response services where the outcomes cannot be pre-determined

Application of ITILITIL®® Concepts and Practices

• PWS uses ITIL® terminology, where possible, to describe requirements

• Offeror is encouraged to respond with ITIL® (or equivalent) terminology, concepts and best practices

• Goal: provide services using commercially-recognized best practices, to mitigate risk of gaps in execution and to enable further technical and functional convergence in DISN context

GSM Application of ITIL® Service Management Framework

Requirements

Design

Build

Deploy

Operate

Optimize

Service Strategy

Service Design

Service Transition

Service Operations

Continual Service

Improvements

GSM-O

GSM-P&S

GSM-ETI

GSM-O Operations Constraints

The GSM-O Contractor shall --

• Support installed DISN infrastructure as-is, where-is

• Not use own infrastructure

• Work in Government Ops Centers and facilities

• Not use own facilities unless approved by Government

• Use Government’s Operational Support System (OSS) and

Government’s Configuration Management (CM) system

• Not use own OSS and tools

DISA is the provider of DISN capabilities to its customers; the

Contractor helps DISA to operate and sustain the DISN (comparable to a Government-owned Contractor-Operated capability)

GSM-O PWS Contents (1 of 3)

Para Description

1 Introduction ……………………………………………………………………

2 Scope of this PWS ……………………………………………………………

2.1 Functional Scope …………………………………………………….………

2.2 Technical Scope ……………………………………………………………..

3 Administrative Requirements …………………………….………………..

3.1 General Requirements ………………………………………………………

3.2 Mission Constraints on OA&M Execution ………………………………...

3.3 Definitions ……………………………….……………………………………

3.4 Directives and Instructions ……………………………….…………………

3.5 Performance Levels and Standards ………….…………………..

3.6 Deliverables ……………………………………………..………..………….

4 Program Management Requirements …………………….………………

4.1 Primary Management Documents …………………………..……………..

4.2 Security Requirements ………………………………………..…………….

4.3 Reports and Controls ………………………………………..………………

4.4 Cost Management and Reporting …………………………..……………..

4.5 Business-Related Metrics …………………………………..………………

5 Transition Requirements ………………………………………..…………..

5.1 Contract Initiation Review (CIR) ………………………………..………….

5.2 Transition Plan ……………………………………………………..………..

5.3 Transition Execution ……………………………………………..………….

5.4 Termination Planning ……………………………………………..…………

GSM-O PWS Contents (2 of 3)

6 Network Operation, Administration and Maintenance Requirements .

6.1 GSM-O Execution Conditions and Implementation Modes ……….……..

6.1.1 Execution Conditions ……………………………………………..………

6.1.2 Implementation Modes ……………………………………………………

6.2 GSM-O Stable Conditions Support …………………………………….….

6.2.1 Order Processing & Request Fulfillment …………………………….…

6.2.2 Trouble Management …………………………………………………….

6.2.3 Configuration Management (CM) …………………………………….…

6.2.4 Support to Network Operations Centers and Operational Support Systems (OSS

6.2.5 Performance Management ……………………………………………….

6.2.6 Network Maintenance, Operational Engineering, Administration and Security

6.2.7 Program Integration Services …………………………………………….

6.2.8 Support to Government Development of Functional Applications ……

6.3 GSM-O Contingency/Emergency Response Support ……………………

6.3.1 Nature of Mission Requirements …………………………………………

6.3.2 Functional Activities ……………………………………………………….

6.4 GSM-O COOP Support ……………………………………………………..

7 Net Assurance Operations ………………………………………………….

7.1 Computer Network Defense – Protect Activities …………………………

7.2 Computer Network Defense – Detect Activities ………………………….

7.3 Computer Network Defense – Response Activities ……………………..

7.4 Computer Network Defense Sustainment Activities …………………….

GSM-O PWS Contents (3 of 3)

8 Defense Message System (DMS) ……………………………………….

9 User Selected Services …………………………………………………….

9.1 On Demand End-to-End Service ………………………………………….

9.2 DISA High Availability (HA) Service ………………………………………..

9.3 DISA Real Time Transport Service ………………………………………..

9.4 DoD Messaging Capabilities ………………………………………………

10 Integrated Operations Support Services ………………………………….

10.1 Unified Service Desk …………………………………………………………

10.2 Converged GIG Management ………………………………………………

10.3 Technology Convergence …………………………………………………...

10.4 Process Re-engineering …………………………………………………….

Appendix A – Definitions ………………………………………………………………….

Appendix B – Directives and Instructions ……………………………………………….

Appendix C – GSM-O Acceptable Performance Levels and Standards .……………

Appendix D – CDRLs List …………………………………………………………………

Appendix E – List of Data Capture Reports and Data Extracts ………………………..

Appendix F – List of GSM-O Acronyms …………………………………………………..

These requirements are not within the expected scope of year-1 task orders

Note: Paragraphs 8 through 10.4 contain possible needs, within the scope of an IDIQ contract, may or may not ever be needed, but may be awarded consistent with DISA and warfighter needs.

GSM Technical Scope

• PWS paragraph 5 lists 31 named network/system entities that, together, define the technical scope of the PWS

• Individual task orders will specify which network/system entities from the PWS list comprise the scope of that task order

• DISA may add additional network/system entities to the PWS scope in the future via contract modification

GSM-O Conditions and Modes

* NOTE: Default path is Other-than-Standard [See Standard Change Definition]

GSM-O Execution Conditions

GSM-O COOP Support

GSM-O

Contingency/Emergency Response

Conditions

GSM-O

Stable (but not static)

Condition

GSM-O

Stable Condition

Execution Modes

[If Applicable]

Use non-GSM-O Sources

[See Standard Change Definition]

GSM-O

Other-than-Standard Change action

[See Standard Change Definition]

GSM-O

Standard Change action

GSM-ETI

Sources

GSM-P&S

Sources

PWS 6.1.1

PWS 6.1.2

PWS Work Allocation Table 1

GSM Work Assignment/Allocation Table Read top to bottom steps 1 – 10 in sequence

Step Criterion YES NO

1 Does the work involve Program/ Admin Support; Software development/modification; Training Services?

Refer to Government COR/Task Monitor for Support via non-GSM-O Sources:

PWS 6.1.2a(1)

Go to step 2

2 Has the Government declared the work to be in the Contingency/ Emergency category? E.g. Katrina;

Haiti aid; 9/11 responses; hostile file area

Refer to Government COR/Task Monitor for Support via GSM-O

PWS 6.3

Go to step 3

3 Does the work require changes in facilities, floorspace footprint, power/HVAC? E.g. new node; new equipment

Refer to Government COR/Task Monitor for Support via ETI Sources: PWS 6.1.2a(1)

Go to step 4

4 Does the work change backbone bandwidth at the applicable DISN point of presence?

Refer to Government COR/Task Monitor for Support via ETI Sources: PWS 6.1.2a(1)

Go to step 5

5 Are any requested/needed equipment/capabilities not on the DISA Approved Products List (APL)?

Refer to Government COR/Task Monitor for Support via ETI Sources: PWS 6.1.2a(1)

Go to step 6

6 Has the Government declared that this work is to be done as an Other-than-Standard action via PWS 6.1.2a(2)?

Refer to Government COR/Task Monitor for Support via Other-than-Standard action: PWS 6.1.2a(2)

Go to step 7

7a Is this a repair action? Go to step 8 Go to step 7b 7b Is this a restoration action? Go to step 8 Go to step 9 8 For repair or restoral/workaround actions: does it involve replacement of an item beyond the range of items of equipment up to and including an individual chassis?

Refer to Government COR/Task Monitor for Support via Other-than-Standard action: PWS 6.1.2a(2)

Perform GSM-O Standard Change action: PWS 6.1.2a(3)

9 Has the requesting DISN customer provided approval in accordance with DISN request fulfillment procedures?

Perform GSM-O Standard Change action:

PWS 6.1.2a(3)

Refer to Government COR/Task Monitor for Support via Other-than-Standard action: PWS 6.1.2a(2)

10 Is the requested action not addressed by rows 1-9 above?

Actions not addressed above require a Government determination as to how to proceed (i.e. an uncertain situation is not within the scope of Standard Change by default).

Note the rows apply sequentially

GSM-O Work Allocation Process

Standard Change Actions

Actions in scope of P&S: Training, Admin, SW Maint, etc

Govt declaration: Other-Than-Standard action

Repair action equip above threshold

Customer did not approve IAW procedures (cost, etc)

Use P&S Sources

Use ETI Sources

GSM-O

Standard Change

GSM-O

Other-Than-

Standard action

Govt declaration: Contingency/Emergency action

GSM-O

Contingency/

Emergency action

Action requires Footprint/Power/HVAC changes

Action changes Backbone Bandwidth

Action requires equipment NOT on APL

Prelim

Govt

Analysis

GSM-O Execution Context

GSM-O Execution Modes

GSM-O Execution Conditions

GSM-O COOP Support

GSM-O

Contingency/Emergency Response

Conditions

GSM-O

Stable (but not static)

Condition

Order Processing & Request Fulfillment ['provisioning']

Trouble Management

Configuration Management

Network Operations Center Support

Performance Management

Network Maint, Ops Eng, Admin & Security

Program Integration Services

Spt to Govt Dev of Apps

Use ETI Sources

GSM-O

Standard Change

GSM-O

Other-Than-

Standard action

Prelim

Govt

Analysis

PWS 6.1.2

PWS 6.4

PWS 6.3

PWS 6.2

GSM-O Logistics Support

• PWS 6.2.6 requires contractor to provide all repair parts needed for repair and maintenance of installed infrastructure. PWS does not say how this is to be done.

• Contractor’s logical considerations for planning an approach:

• What are the items to be supported? Where are they? (The GFI asset DB describes this)

• Can some items be procured as needed? Will some need to be purchased and staged? (Look at response times for repair in PWS Standards table; some parts will probably have to be staged.)

• What is the known/projected failure rate for each item, so the need for spare parts can be estimated (as part of fixed price)? (GFI performance data is supposed to provide this.)

• Execution approach alternatives: what to place at a site; what to place near multiple sites; what to house in central location in Region

• Task Orders will require contractor to consider possible use of spare/repair parts from existing Government stocks (to help NS spend down existing parts inventory). (Eventually the Government will close down the existing system and dispose of remaining items.) 19

PWS 6.2.2, 6.2.6

GSM-O Warranty/Maintenance Agreements

• DISA currently has 100+ Maintenance Agreements covering installed equipment and software (e.g. switches, routers, etc)

• The DGS contractor establishes and renews the agreements, not the Government, because the contractor can obtain a lower service premium

• The Government already owns the software licenses where applicable.

• The DGS task order that pays for this support is reissued annually in early January.

• The agreements cannot be transferred to the Government; to minimize duplicate payments, the new GSM-O contractor must time its agreement arrangements to coincide with the expiration of the old agreements.

Therefore the DGS contractor must remain responsible for this function (to keep the agreements in force) through early January 2012.

• DISA will issue the GSM-O task order for repair/maintenance work to give the new contractor time to establish the new agreements and become ready to perform repair/maintenance functions. This will be in fall 2011 as decided by the Government.

PWS 6.2.2, 6.2.6

Acceptable Levels of Performance (Illustrative Example)

100 %

97.5 %

95 %

85 %

97.5 % up to 100% ….. Incentive Earned

95 % up to < 97.5 % = Satisfactory

85 % up to < 95 % = Less than Satisfactory (no penalty yet)

< 85 % …. Negative Incentive (penalty/credit)

PWS App C

Scope of GSM-O PWS and Year-1 Work

Scope of year-1 Work Program

Netwk/Sys 1-17 Netwk/Sys 18-31

T a s k s

T a s k s

To be addressed after year-1

To be addressed after year-1

Technical Scope of Support to be Provided

F u n c ti o n a l

S c o p e o f P

W S

C a p a b il it ie s

To be addressed after year-1

TO-1, TO-2

Overview of RFPs RR GFI Data Files

GSM-O RR Data

GSM-O Added/Other Data

GSM-O ‘Links’ into GIG data

GSM-ETI RR Data

GSM-ETI Other Data

GSM-ETI ‘Links’ - GIG data

B1

A3

A1

A2

B2

B3

GSM-O Initial Task(s)

A1x

GSM-ETI Initial Task(s)

GIG DBs (CM, etc)

GSM-O Must-Have Data

See Notes Pages text for discussion