p25 completion metrics

12
P25 Completion Metrics The Industry Consensus 7-November-2005

Upload: beth

Post on 03-Feb-2016

35 views

Category:

Documents


0 download

DESCRIPTION

P25 Completion Metrics. The Industry Consensus 7-November-2005. The 4 Dimensions of Completeness. Interfaces What are the specified objects? Content What’s specified? Scope What kind of systems can be built? Functionality What can they do?. Content. Interfaces. Architectural Scope. - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: P25 Completion Metrics

P25 Completion Metrics

The Industry Consensus7-November-2005

Page 2: P25 Completion Metrics

2

The 4 Dimensions of Completeness Interfaces

– What are the specified objects?

Content– What’s specified?

Scope– What kind of systems

can be built? Functionality

– What can they do?

Interfaces

Arc

hite

ctur

alSc

ope

Content

Function

ality

Page 3: P25 Completion Metrics

3

4 Dimensions: Interfaces The Eight Open Interfaces

– Common Air Interface (U)– 2 Data Interfaces (A,Ed)– Inter(RF)-SS Interface (G)– Console Interface (Ec)– Fixed Station Interface (Ef)– PSTN Interface (Et)– Network Management Interface (En)

Plus Important Functional Interfaces– OTAR (KMF to End-Unit)– Key-Fill (KFD to End-Unit)

Plus Other Interfaces that we may discover

“Internally” we know these are here,

Externally, we may choose to hide them to maintain a

consistent message

Page 4: P25 Completion Metrics

4

4 Dimensions: Content Overview of Services/Classification Messages (Vocabulary) Procedures Conformance Tests

Performance Recommendations Performance Measurement Methods Interoperability Tests

Information that specifies the interface.“Fully Specified”

Information that allows independent testing.“Certifiable”

Page 5: P25 Completion Metrics

5

Radiosw/Ext.

Consoles

ConsolesNMSKMFs

4 Dimensions: Architectural Scope

RFSS

System

FixedStationsRadios PSTN

GWsNMS

WACN

Systems

KMFs

FixedStations

PSTNGWs

RFSSs

Vender SpecificImplementation(Limited Interoperability)

WACNs Network of Networks

Wide Area:Inter-System,Independent Mgmt

Local Area Operation:Mixed Manufacturer,Unified Management

Page 6: P25 Completion Metrics

6

Radiosw/Ext.

Consoles

ConsolesNMSKMFs

4 Dimensions: Architectural Scope

RFSS

System

FixedStationsRadios PSTN

GWsNMS

WACN

Systems

KMFs

FixedStations

PSTNGWs

RFSSs

WACNs Network of Networks

Wide Area:Inter-System,Independent Mgmt

Local Area Operation:Mixed Manufacturer,Unified Management

Vender SpecificImplementation: (LimitedInteroperability)

Interoperable core functions,Interoperable Equipment to the degree that venders publish interfaces and

implement each others proprietary features,Interoperable Agencies to the degree that Agencies co-operate

Fully Interoperable Equipment,Interoperable Agencies through coordinated management

Fully Interoperable Equipment with wide area roaming and independent management.

Interoperable Agencies through coordinated management

Page 7: P25 Completion Metrics

7

4 Dimensions: Architectural Scope Vender Specific Implementation –

– Exists Today, Many venders can build a system that works and is fully functional with proprietary features

Local Area– Exists Partially Today (Radio Interoperability),

with Venders implementing each others features Wide Area

– Specification Incomplete, Extended Identifiers, Wide-Area OTAR, etc

Network of Networks– Not considered

Page 8: P25 Completion Metrics

8

4 Dimensions: Functionality Refers to what the system can do Changes as user requirements evolve

(over time) and are incorporated into the standards

We need to discuss naming (Rev, Release, Version, Slice)

We need to discuss what the names mean– Is “Thing1” the current TSB102 functionality, for

example?

Page 9: P25 Completion Metrics

9

The 4 Dimensions of Completeness

Interfaces

Arc

hite

ctur

alSc

ope

Function

alityLocal Area

Net of Nets

Certifiable

Content

SpecifiedCAI

ISSI etc.P25 is truly complete when all of the interfaces are “certifiable” for Network-of-network operations and the requirements stop changing!

But it’s “usefully” complete when the standards are accepted by industry, industry is building interoperable products, and users accept those products.

Page 10: P25 Completion Metrics

10

Observations This model for completeness,

while accurate, is probably too complex for public display.

P25 will and should continually evolve, and so will never be “totally done”.

We as a community need a way to demonstrate continual progress and useful waypoints.

Page 11: P25 Completion Metrics

11

Example Summary of Status Select TSB102A Functionality, Show Progress on Content for

Interfaces vs. Scope

8 Interfaces + OTAR Vender SpecificOperation

Local Area Operation(Intra-System)

Wide Area Operation

(Inter-System)Common Air I/F (U) Fully Specified by

VendersFully Specified less 1 feature Some Work Required

2 Data Interfaces (Ed,A) Fully Specified (2) Fully Specified (2) Fully Specified (2)Inter(RF)-SS I/F (G) N/A Voice Only, Work OngoingConsole I/F (Ec) N/A Overview Only, OngoingFixed Station I/F (Ef) N/A Conventional Voice Only,

OngoingN/A

PSTN I/F (Et) Fully Specified Some Work RequiredNetwork Mgmt (En) N/A Not Started Not StartedOTAR Full Specified, Nearly

CertifiableFull Specified, Nearly

CertifiableWork Required

Status 5/5 4/9 2/9

Page 12: P25 Completion Metrics

12

Showing Progress, Defining Waypoints, Next Steps

Develop Status Charts for Multiple Views

Choose one that is truthful, and reflects our progress in a good light

Focus on work that meets the real needs of the user community, and shows discernable progress towards filling in the chart