Issue 18509: PV1 (DoDAF) Attributes Needed (updm-2-0-rtf) Source: (, ) Nature: Enhancement Severity: Minor Summary: In the current DoDAF Project Viewpoints (PV1) the project element has a start date and an end date. Those attributes are not sufficient for the US JCIDS process. In the incremental development process described by JCIDS, we have increments, blocks and spirals. In the main we don't measure our programs in absolute start and stop dates but rather where they fall in the relative JCIDS process, priority and lifecycle. Start dates are usefull but with a 20-30 year lifecylce, the stop date is not as useful. Having these attributes (increment:string, block: int and spiral:int) in the Project Element would allow us to trace requirements and capability sets to the proper increment, block or spiral. Resolution: Revised Text: Actions taken: February 27, 2013: received issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 27 Feb 2013 17:19:54 -0500 To: Subject: Issue/Bug Report ******************************************************************************* Name: Monte Porter Employer: CSC / PEO MS mailFrom: monte.porterjr@msl.army.mil Terms_Agreement: I agree Specification: UPDM 2.0.1 Section: D.10.3 FormalNumber: formal-13-01-01 Version: 2.0.1 Doc_Year: 2013 Doc_Month: January Doc_Day: 01 Page: 386 Title: PV1 (DoDAF) Attributes Needed Nature: Enhancement Severity: Minor CODE: 3TMw8 B1: Report Issue Description: In the current DoDAF Project Viewpoints (PV1) the project element has a start date and an end date. Those attributes are not sufficient for the US JCIDS process. In the incremental development process described by JCIDS, we have increments, blocks and spirals. In the main we don't measure our programs in absolute start and stop dates but rather where they fall in the relative JCIDS process, priority and lifecycle. Start dates are usefull but with a 20-30 year lifecylce, the stop date is not as useful. Having these attributes (increment:string, block: int and spiral:int) in the Project Element would allow us to trace requirements and capability sets to the proper increment, block or spiral. From: "Levine, Leonard Frederick (Len Levine @ DISA) CIV DISA EE (US)" To: Juergen Boldt , ":monte.porterjr@msl.army.mil" , "'davem@silverbulletinc.com'" CC: "updm-2-0-rtf@omg.org" , "Okon, Walter J CIV (US)" Subject: DoDAF (not UPDM? PV-1/PV-2): OMG issue 18509 -- UPDM 2 RTF issue Thread-Topic: DoDAF (not UPDM? PV-1/PV-2): OMG issue 18509 -- UPDM 2 RTF issue Thread-Index: AQHOFcJm5s+8p+PCr066jClYOy8U9piPZWjQ Date: Thu, 28 Feb 2013 17:30:19 +0000 Accept-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-originating-ip: [214.21.83.188] X-Virus-Scanned: amavisd-new at omg.org X-Brightmail-Tracker: AAAAAA== X-Brightmail-Tracker: AAAAAA== Dear Monte Porter (CSC) (Contractor for PEO MS), I received a copy of UPDM Issue 18509, "PV1 (DoDAF) Attributes Needed". Thanks for the input. We always welcome such. My response has turned out to be lengthy. Let me summarize it and attach a MS-Word Document with details. I refer you to the chief architect of DoDAF, Mr. Dave McDaniel of Silver Bullet, Inc. davem@silverbulletinc.com because UPDM implements but does not control DoDAF. ÂYet, I do note that commercial tools, especially those providing unified support of both DoDAF and MODAF through UPDM, should be able to accommodate the request. I have suggested attention to the View called PV-2, especially with use of Actual Project Whole/Part relationship and elements called Actual Project Milestone(s), Milestone Sequence (MODAF), and Incremental Milestone (MODAF). ÂLen Levine Cc: Walt Okon, DoD-CIO Defense Information Systems Agency (DISA) ATTN: Leonard F. Levine /Code EE31 P.O. Box 549 Ft. Meade, MD 20755-0549 Room A4B57D Telephone: 301-225-7497 Mobile: 703-861-4822 NEW E-MAIL (June 2012): Leonard.F.Levine.civ@mail.mil -----Original Message----- From: Juergen Boldt [mailto:juergen@omg.org] Sent: Thursday, February 28, 2013 9:45 AM To: issues@omg.org; updm-2-0-rtf@omg.org Subject: issue 18509 -- UPDM 2 RTF issue  From: webmaster@omg.org  Date: 27 Feb 2013 17:19:54 -0500  To:  Subject: Issue/Bug Report   *******************************************************************************  Name: Monte Porter  Employer: CSC / PEO MS  mailFrom: monte.porterjr@msl.army.mil  Terms_Agreement: I agree  Specification: UPDM 2.0.1  Section: D.10.3  FormalNumber: formal-13-01-01  Version: 2.0.1  Doc_Year: 2013  Doc_Month: January  Doc_Day: 01  Page: 386  Title: PV1 (DoDAF) Attributes Needed  Nature: Enhancement  Severity: Minor  CODE: 3TMw8  B1: Report Issue   Description:   In the current DoDAF Project Viewpoints (PV1) the project element has a start date and an end date. Those attributes are not sufficient for the US JCIDS process. In the incremental development process described by JCIDS, we have increments, blocks and spirals. In the main we don't measure our programs in absolute start and stop dates but rather where they fall in the relative JCIDS process, priority and lifecycle. Start dates are usefull but with a 20-30 year lifecylce, the stop date is not as useful. Having these attributes (increment:string, block: int and spiral:int) in the Project Element would allow us to trace requirements and capability sets to the proper increment, block or spiral. Juergen Boldt Director, Member Services 109 Highland Ave Needham, MA 02494 USA Tel: 781 444 0404 x 132 fax: 781 444 0320 www.omg.org []  Response to Monte Porter OMG Issue 18509.docx From: "Dandashi, Fatma" To: "Levine, Leonard Frederick (Len Levine @ DISA) CIV DISA EE (US)" , Juergen Boldt , "monte.porterjr@msl.army.mil" CC: "updm-2-0-rtf@omg.org" Subject: RE: DoDAF (not UPDM? PV-1/PV-2): OMG issue 18509 -- UPDM 2 RTF issue Thread-Topic: DoDAF (not UPDM? PV-1/PV-2): OMG issue 18509 -- UPDM 2 RTF issue Thread-Index: AQHOFcJaFLg9oGo+bkekRvwXOhcko5iP2/sAgAKZllA= Date: Sat, 2 Mar 2013 14:18:58 +0000 Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [129.83.31.56] X-Virus-Scanned: amavisd-new at omg.org Monte, In addition to Lenâs email below, the issue you raised will be addressed as part of the normal UPDM RTF open-OMG process. Thank you for raising this issue. Please keep them coming! Best Regards, Fatma Dandashi, PhD Lead, Simulation Modeling Eng, Office: 703-983-7914 The Mitre Corp. Working in the Public Interest From: Levine, Leonard Frederick (Len Levine @ DISA) CIV DISA EE (US) [mailto:leonard.f.levine.civ@mail.mil] Sent: Thursday, February 28, 2013 12:34 PM To: Juergen Boldt; monte.porterjr@msl.army.mil; 'davem@silverbulletinc.com' Cc: updm-2-0-rtf@omg.org; Okon, Walter J CIV (US) Subject: DoDAF (not UPDM? PV-1/PV-2): OMG issue 18509 -- UPDM 2 RTF issue Resending . correction to email addrress of Mr. Porter. Dear Monte Porter (CSC) (Contractor for PEO MS), I received a copy of UPDM Issue 18509, "PV1 (DoDAF) Attributes Needed". Thanks for the input. We always welcome such. My response has turned out to be lengthy. Let me summarize it and attach a MS-Word Document with details. I refer you to the chief architect of DoDAF, Mr. Dave McDaniel of Silver Bullet, Inc. davem@silverbulletinc.com because UPDM implements but does not control DoDAF. Yet, I do note that commercial tools, especially those providing unified support of both DoDAF and MODAF through UPDM, should be able to accommodate the request. I have suggested attention to the View called PV-2, especially with use of Actual Project Whole/Part relationship and elements called Actual Project Milestone(s), Milestone Sequence (MODAF), and Incremental Milestone (MODAF). Len Levine Cc: Walt Okon, DoD-CIO Defense Information Systems Agency (DISA) ATTN: Leonard F. Levine /Code EE31 P.O. Box 549 Ft. Meade, MD 20755-0549 Room A4B57D Telephone: 301-225-7497 Mobile: 703-861-4822 NEW E-MAIL (June 2012): Leonard.F.Levine.civ@mail.mil -----Original Message----- From: Juergen Boldt [mailto:juergen@omg.org] Sent: Thursday, February 28, 2013 9:45 AM To: issues@omg.org; updm-2-0-rtf@omg.org Subject: issue 18509 -- UPDM 2 RTF issue From: webmaster@omg.org Date: 27 Feb 2013 17:19:54 -0500 To: Subject: Issue/Bug Report ******************************************************************************* Name: Monte Porter Employer: CSC / PEO MS mailFrom: monte.porterjr@msl.army.mil Terms_Agreement: I agree Specification: UPDM 2.0.1 Section: D.10.3 FormalNumber: formal-13-01-01 Version: 2.0.1 Doc_Year: 2013 Doc_Month: January Doc_Day: 01 Page: 386 Title: PV1 (DoDAF) Attributes Needed Nature: Enhancement Severity: Minor CODE: 3TMw8 B1: Report Issue Description: In the current DoDAF Project Viewpoints (PV1) the project element has a start date and an end date. Those attributes are not sufficient for the US JCIDS process. In the incremental development process described by JCIDS, we have increments, blocks and spirals. In the main we don't measure our programs in absolute start and stop dates but rather where they fall in the relative JCIDS process, priority and lifecycle. Start dates are usefull but with a 20-30 year lifecylce, the stop date is not as useful. Having these attributes (increment:string, block: int and spiral:int) in the Project Element would allow us to trace requirements and capability sets to the proper increment, block or spiral. Juergen Boldt Director, Member Services 109 Highland Ave Needham, MA 02494 USA Tel: 781 444 0404 x 132 fax: 781 444 0320 www.omg.org []