Task 29 Scope – Party (L=ChrisH)

Slides:



Advertisements
Similar presentations
Submission doc.: IEEE /XXXXr0 Month Year John Doe, Some CompanySlide 1 Insert Presentation Title Here Date: YYYY-MM-DD Authors: Notice: This document.
Advertisements

Overview Duet Enterprise Feature Pack 1 (FP1). Agenda.
Global Address Book in Microsoft Dynamics® AX 2012
Oracle Fusion Applications 11gR1 ( ) Functional Overview (L2) Manage Inbound Logistics (L3) Manage Receipts.
Oracle Fusion Applications 11gR1 ( ) Functional Overview (L2) Manage Inbound Logistics (L3) Manage Supplier Returns.
Oracle Fusion Applications 11gR1 ( ) Functional Overview (L2) Manage Inbound Logistics (L3) Manage and Disposition Inventory Returns.
Doc.: IEEE /0061r0 Submission June 2011 Mika Kasslin, NokiaSlide 1 Discovery system overview Notice: This document has been prepared to assist.
Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential. 1.
Instructional slide to Partner: REMOVE BEFORE PRESENTING TO CUSTOMER
OGSA Service Classifications
Task 4 Scope – Software (L=ChrisH)
Project: IEEE 802 EC Privacy Recommendation Study Group
Hyper-V Cloud Proof of Concept Kickoff Meeting <Customer Name>
June 2006 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Proposed Scenarios for Usage Model Document.
November 1999 doc.: IEEE /133r0 November 1999
doc.: IEEE <doc#>
Project: IEEE 802 EC Privacy Recommendation Study Group
March 2018 Opening Report Date: Authors: March 2018
Nov Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Implementation Approaches for LPWAN Extension]
TGu Requirements Change Motion
Coexistence of CMs with different decision making algorithms
About this Template Dear Colleague, This template is provided by Valooto to help you communicate the facts about your need for a CPQ (Configure Price Quote)
Feature: Document Attachment - Flow from Master Records
WAC SG November 2016 Opening Report
Possible Action Items Date: Author:
Possible Action Items Date: Author:
Task xx Scope – Connector Pin Strand
June, 2010 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [OFDM PHY Mode Representation] Date Submitted:
Comments to IEEE /68 Date: Authors: September 2009
Task 57 Scope – Job Task Purpose – Specifically –
Entity vs Datatype.
Task 55 Scope – TOSCA Profile
Task 41 Scope – Identity Implementation (L=Nigel Davis)
September 2003 doc.: IEEE /0423 r0 September 2003
Task 36a Scope – Storage (L=ChrisH)
Task 13 Scope – Model Structure (L=ChrisH)
Task 57 Scope – Template and Profile
Task 34 Scope – LTP Port (L=Nigel Davis)
Task 13 Scope – Model Structure (L=ChrisH)
Task 2a Scope – Processing Construct (L=ChrisH)
Task 2b Scope – Processing Construct (L=ChrisH)
Task 36b Scope – CPU & Memory (L=ChrisH)
Task 34 Scope – LTP Port (L=Nigel Davis)
Task 58 Scope – Occurrence Pattern
Task 30 Scope – Location (L=ChrisH)
Task 57 Scope – Profile and Template
Task xx Scope – Expected Equipment
Task 62 Scope – Config / Operational State
Task xx Scope – Model Extensions
Submission Title: TG9ma Agenda for September Meeting
August 2019 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: CID 422 Proposal Date Submitted: 14 August,
Model Aspect Mechanisms
Task 2b Scope – Processing Construct (L=ChrisH)
12/15/2019 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [AWGN Simulation Results] Date Submitted:
Presentation transcript:

Task 29 Scope – Party (L=ChrisH) Purpose – add Party support {Organization (Unit) and Individual} to the model Specifically – add a Party framework model that can be extended as required Includes – party role, contact details, software agent support ? Excludes – Creating a full blown BSS implementation, CRM (customer relationship) support, HRM (human resources) support, user (account), RBAC or other security concerns, Business Interaction, Marketing Demographics, temporal support External Dependencies – none Assumptions – none Risks – none

Team Members Leader - Chris Hartley chrhartl@cisco.com Members ???

IPR Declaration Is there any IPR associated with this presentation NO NOTICE: This contribution has been prepared to assist the ONF. This document is offered to the ONF as a basis for discussion and is not a binding proposal on Cisco or any other company. The requirements are subject to change in form and numerical value after more study. Cisco specifically reserves the right to add to, amend, or withdraw statements contained herein. THE INFORMATION HEREIN IS PROVIDED “AS IS,” WITHOUT ANY WARRANTIES OR REPRESENTATIONS, EXPRESS, IMPLIED OR STATUTORY, INCLUDING WITHOUT LIMITATION, WARRANTIES OF NONINFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Need for Party Model A Party model allows us to centralise all individual and organization related information It answers the question “Who ?” It prevents having the information spread through the model in inconsistent ways This is a common solution for information systems We will provide a simple model that can be extended or replaced by a more comprehensive solution if required

Particular Scenarios we wish to support Site (Location Contact) Equipment support contact Multi-tenant customer / owner details

TMF SID Party model (in party module) The SID Party model is a bit heavyweight for what we need, but may serve as a good starting point Copyright © TM Forum 2014. All Rights Reserved.

Proposed Model – Package Dependencies

Book References Because the Party model is so often used, it is documented in many books and papers. Two of the best books are shown to the right and a few good references have been added below. Dealing with Roles - Martin Fowler https://www.martinfowler.com/apsupp/roles.pdf The Coad Letter: Modeling and Design http://edn.embarcadero.com/article/29661 http://edn.embarcadero.com/article/29605 (UML Version)

Proposed Model

Proposed Model – Linking into the CIM Core Linking the inventory model to the Party model via CD decouples the two modules. It allows inventory items to be grouped, reducing the number of association instances to be managed and also giving more sensible semantics. It also reduces the number of associations in the model. * CdHasRelatedPartyRoles *