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

Slides:



Advertisements
Similar presentations
Multivendor Interoperability
Advertisements

Evolution of NGN and NGA scenario in Nepal Nepal Telecommunications Authority.
IIS HL7 Interface Testing Process
Standardizing Access to Information from Onboard Mobile Mining Equipment Mark Bartlett Presented at: CIM Annual Meeting May, 2013 Mining Standards and.
TETRA Inter System Interface (ISI)
SBC in NGN Architectures Jonathan Cumming. Copyright © 2006 Data Connection Limited All Rights Reserved.2 SBC in NGN Architectures NGN Standardisation.
Systems Engineering in a System of Systems Context
1 Independent Verification and Validation Current Status, Challenges, and Research Opportunities Dan McCaugherty IV&V Program Manager Titan Systems Corporation.
Jerry Shih1 MMS Evolution Past, Present, Future Jerry Shih.
© 2005 Prentice Hall7-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
Ivy Equipment Inventory System Jaein Jeong Barbara Hohlt Kris Pister.
DITSCAP Phase 2 - Verification Pramod Jampala Christopher Swenson.
API WG Update 16th Eurofiling Workshop Wednesday 12 December Herm Fischer.
Definitions, Concepts and Applications of TETRA Hannu Villpunen Nokia
State Services Commission Crown Copyright 2006 RADIO COMMUNICATIONS – APCO P 25 TECHNICAL STANDARD SUITE It is recommended that the e-GIF committee Approve.
MPLS Consortium Charter Meeting Welcome to UNH Durham, New Hampshire February 7, 2000.
© 2005 Prentice Hall14-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 27 Slide 1 Quality Management.
Principles of Object Technology Module 1: Principles of Modeling.
12.
UML - Development Process 1 Software Development Process Using UML (2)
Object-Oriented Analysis and Design Iterative Development and the Unified Process.
December 5, 2003FG3 Report FOCUS GROUP 3 Interoperability Report to NRIC VI Council December 5, 2003 Cliff Naughton (Boeing)
IWCE Conference - Project 25 Compliance Assessment Program and Beyond Wednesday, March 26, 2014 – 4:15-5:30 PM Chris Essid Deputy Director DHS Office of.
1 IBM Software Group ® Mastering Object-Oriented Analysis and Design with UML 2.0 Module 1: Best Practices of Software Engineering.
Packetizer ® Copyright © 2008 H.325 Beyond Today’s Second Generation Systems Paul E. Jones Rapporteur, ITU-T Q12/16 1.
AIMS Workshop Heidelberg, 9-11 March 1998 P717 & P805: SIRTE Study for Internet Roaming Throughout Europe Franco Guadagni - Telecom Italia / CSELT
Summer school Jukka Heikkilä Professor, vice dean The faculty of Information Technology University of Jyväskylä P.O. Box 35 FIN JYVÄSKYLÄ FINLAND.
Chapter 8 – Software Testing Lecture 1 1Chapter 8 Software testing The bearing of a child takes nine months, no matter how many women are assigned. Many.
Coordination Group for Meteorological Satellites - CGMS Climate Monitoring Architecture: Status and way forward Presented to CGMS-41 plenary session.
OmniRAN Specification – Structuring the effort Document Number: Omniran Date Submitted: Source: Max Riegel
© 2005 Global Grid Forum The information contained herein is subject to change without notice Leading the pervasive adoption of grid computing for research.
1-1 System Development Process System development process – a set of activities, methods, best practices, deliverables, and automated tools that stakeholders.
GSC-19 Meeting, July 2015, Geneva Project 25 Overview Stephanie Montgomery Vice-President, Technology and Standards, TIA Document No:GSC-19_110 Source:TIA.
Component Technology. Challenges Facing the Software Industry Today’s applications are large & complex – time consuming to develop, difficult and costly.
1 Guiding Principles for Nationwide Interoperability A Brief Overview of Recent Efforts and Progress.
How to achieve real interoperability Peter Clemons Clemons Consulting.
QUALITY ASSURANCE PRACTICES. Quality Plan Prepared and approved at the beginning of project Soft filing system approach followed. Filing location – –
1 | 3GPP2 TSG-S | 11 May 2009 | Version Summary of SC.P the “3GPP2 Vision for 2009 and Beyond”
Agile SOA Agile EAI How do we achieve agility in Enterprise Integration?
J. Scott Hawker p. 1Some material © Rational Corp. Rational Unified Process Overview See and use the RUP Browser on lab machines.
Strategies for Knowledge Management Success SCP Best Practices Showcase March 18, 2004.
Chapter 8 Lecture 1 Software Testing. Program testing Testing is intended to show that a program does what it is intended to do and to discover program.
6. Protocol Standardization for IoT 1.  TCP/IP  HTML and HTTP  The difference between the Internet and the World Wide Web The Internet is the term.
Foundational Program Overview September  2004 Copyright RosettaNet. RosettaNet Foundational Programs Program Overview ProgramPhase InvestigateDesignImplement.
May 2007 Registration Status Small Group Meeting 1: August 24, 2009.
OOI CI LCA REVIEW August 2010 Ocean Observatories Initiative Sensing and Acquisition Subsystem Arjuna Balasuriya Life Cycle Architecture Review La Jolla,
Software Engineering Lecture 8: Quality Assurance.
ESW 7 – NENA Standards Roger Hixson - NENA We are mid-way through documentation development for NG9-1-1, with a number of documents published and more.
Setting the record straight :-) Why is it all those CIO’s are saying “we’re using CORBA” ? Because they are – every enterprise-wide distributed heterogeneous.
Association of Enterprise Architects International Committee on Enterprise Architecture Standards Jan 23, Collaborative Expedition Workshop #57aeajournal.org.
Bearer Control for VoIP and VoMPLS Control Plane Francois Le Faucheur Bruce Thompson Cisco Systems, Inc. Angela Chiu AT&T March 30, 2000.
March Project 25 Technology Interest Group International Wireless and Communications Expo NPSTC Meeting March 20, 2014 Las Vegas, Nevada Project.
Supplier Corrective Action Request (SCAR) Supplier Training
1 OPEXSHARE Implementing and Effective Operating Experience Program DOE OEC Workshop October 29, 2015 Las Vegas, NV.
XML Interoperability & Convergence ISO XML Working Group (WG 10) XML on Wall Street November 20th, 2001 John Goeller.
Requirements for IP Based UMTS A Consensus View from the Industry
AX LICENSING & NICS Topics: 1 – License File
Object-Oriented Analysis and Design
IEEE 802 OmniRAN Study Group: SDN Use Case
TIA TR-8 Mobile and Personal Private Radio Standards
ESMF Governance Cecelia DeLuca NOAA CIRES / NESII April 7, 2017
Version 3 April 21, 2006 Takahiro Yamada (JAXA/ISAS)
PSAP Radio Communications Today and Tomorrow
Wireless Access including RLANS & ad-hoc Networking
Software Interoperability.... Same game, same rules?
Standards and Interoperability Do they matter for ETPs?”
Database Processing: David M. Kroenke’s Chapter Twelve: Part One
Overview Activities from additional UP disciplines are needed to bring a system into being Implementation Testing Deployment Configuration and change management.
DRAFT ISO 10006:2017 Revision Overview Quality management systems - Guidelines for quality management in projects ISO/TC176 TG 01.
Presentation transcript:

P25 Completion Metrics The Industry Consensus 7-November-2005

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 Architectural Scope Content Functionality

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

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”

5 Radios w/Ext. Consoles NMSKMFs 4 Dimensions: Architectural Scope RFSS System Fixed Stations Radios PSTN GWs NMS WACN Systems KMFs Fixed Stations PSTN GWs RFSSs Vender Specific Implementation (Limited Interoperability) WACNs Network of Networks Wide Area: Inter-System, Independent Mgmt Local Area Operation: Mixed Manufacturer, Unified Management

6 Radios w/Ext. Consoles NMSKMFs 4 Dimensions: Architectural Scope RFSS System Fixed Stations Radios PSTN GWs NMS WACN Systems KMFs Fixed Stations PSTN GWs RFSSs WACNs Network of Networks Wide Area: Inter-System, Independent Mgmt Local Area Operation: Mixed Manufacturer, Unified Management Vender Specific Implementation: (Limited Interoperability) 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

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

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?

9 The 4 Dimensions of Completeness Interfaces Architectural Scope Functionality Local Area Net of Nets Certifiable Content Specified CAI 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.

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.

11 Example Summary of Status  Select TSB102A Functionality, Show Progress on Content for Interfaces vs. Scope 8 Interfaces + OTARVender Specific Operation Local Area Operation (Intra-System) Wide Area Operation (Inter-System) Common Air I/F (U)Fully Specified by VendersFully Specified less 1 featureSome Work Required 2 Data Interfaces (Ed,A)Fully Specified (2) Inter(RF)-SS I/F (G)N/AVoice Only, Work Ongoing Console I/F (Ec)N/AOverview Only, Ongoing Fixed Station I/F (Ef)N/AConventional Voice Only, Ongoing N/A PSTN I/F (Et)Fully SpecifiedSome Work Required Network Mgmt (En)N/ANot Started OTARFull Specified, Nearly Certifiable Work Required Status5/54/92/9

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