Frameworx

TM Forum Members Only

The full version of this page is only available to members of the TM Forum. Learn more about becoming a member.

In order to access a TM Forum Member only area of the website you must be a registered user and work for a TM Forum Member Company. If this applies to you please login above.

Not a Registered User? Register Now
Registration is free, quick and simple, and will give you access to a large library of TM Forum member content, industry documents, exclusive articles, commentaries, plus our web discussions and event features.

If you experience any problems logging in, please contact us.

RSS

Group Administrators

View the Points Program Details

Resource Links

Open Discussions

Recent Group Members

Blog Archive List

Change Requests

Filter Options

Name: (Title, Contributor, Summary)
Project Work Area:
Status:
Best Practices:
My Contributions:
	Download Search Results to Excel

Frameworx Instrumentation Methodology (Adoption)

Identification of the methodolgy for mapping and generation of metrics/KPI's aligned to industry setors - specific use case security

12/22/2011 11:21:45 AM

Frameworx Instrumentation Mapping to BPMS (Adoption)

Use BPMS as the proposed model to map KPI to Frameworx, specifically eTOM and SID How eTOM and its processes support KPI's including mapping/association to BPMS

12/22/2011 11:17:39 AM

Frameworx Instrumentation (Adoption)

Indetification and understanding of the KPI's that are seen as critical for relevant roles and perspectives within an organisation (eg CIO/CFO) based on industry sectors and members use cases Use defence contribution as the first run at this

12/22/2011 11:14:12 AM

3rd Party interface eco-system (Adoption)

Identify the requirements for the creation of a 3rd Party extended value chain interface eco-system that facilitates the generation of API's/interfaces between both the developer and the consumer aliged to the app store model Note - look to leveraging the mulit-service catalysts work.

12/22/2011 11:09:31 AM

HTML Visualisation of the Information Framework (Adoption)

Reprentation of the imported and exported Information Framework digram structure to be maintained in Visulisation in tooling environment (import/export of digram structure)

12/22/2011 11:01:03 AM

Document via the Website (Adoption)

Explore options to making all of the documentation suite avaliable on line in a browserable manner and also ensure that the navagation though documents and standards is intuative and serachable at the table of contents level (as per google search)

12/22/2011 10:58:48 AM

Document Generation (Adoption)

Auto Generation of complete documenet sets within the tools used to deliver TM Forum standards. This is an improvement on the existing capabilities of the teams, for example 95% of TAM is generated from the tool and this needs to be the aim of all the standards

12/22/2011 10:56:38 AM

Tooling Environment (Adoption)

Centralised "cloud/hosted" enviroment for all tools used in the development of TM Forum Standards, emphasis on RSA and Casewise

12/22/2011 10:55:11 AM

Position in and access to the artefacts via the Web (Adoption)

Making the access to the TM Forum artefacts more user friendly and intuative minamising the navigation through the website. The navigation to the interfaces and solutions needs to be more direct than is currently supported Postioning and access to the artefacts - webiste presentation, accessability

12/22/2011 10:53:25 AM

Quick Start Packs (Adoption)

QSP need to be expanded to cover all of the Frameworx artifacts Update existing QSP to reflect support for SID and TAM

12/22/2011 10:50:41 AM

Single Model File (Adoption)

Creation of a single file which will consist of all the component frameworks model files with where possible cross frameworx mapping. This file will hopefully be be HTML browserable and other formats to be determined. Member distrabution to be determined Merged Frameworx model file (accepting SID ULM will not be complete)

12/22/2011 10:40:59 AM

Implementer Eco-System (Adoption)

Creation of an Implementer Eco System to deliver the support material, documentation, tooling and code to aid the member to in the adoption and usage of Frameworx How to Guide books, Wiki, FAQ's, Themed User Groups, RSA/RSM Migration

12/22/2011 10:34:04 AM

Frameworx Mapping (Adoption)

Continued mapping of the component frameworks for Application Framework to Business Process Frameworx and Business Process Frameworx to to the Information Framework Frameworx Mapping with the appropriate mapping level to be deternied by the relevant teams

12/22/2011 10:25:33 AM

EA Tooling Exchange format for Open Source Tools (Adoption)

Validate the open source EA tool requirements for the exchange format to support the export in to open source tools

12/22/2011 10:15:26 AM

EX Tooling exchange format (Adoption)

Deliver a agreed standard exchange format of the each component Framework with import into EA tools. Improvement of the inter-operability between Frameworks Improve availability and consistancy of export format to EA Tools

12/22/2011 10:11:16 AM

Enforcement policy taxonomy and semantics (Adoption)

Definition and creation of the policy and methodology for the definition of terms Creation of enforcement policy taxonomy and semantics

12/22/2011 9:56:25 AM

Creation of Taxonomy/Semantics Glossary (Adoption)

Use current online glossary for the creation and publication of new agreed glossary of terms

12/22/2011 9:39:00 AM

Frameworx Documentation Alignment (Adoption)

Produce agreed common template for document structure for each common document types and get teams to align documents against the new structure Alignment of the documents structure and presentation across Business Process Framework, Information Framework and Application Framework

12/22/2011 9:01:57 AM

Enterprise Risk Management and Fraud Management En

Extensions, corrections, and detailing of L2-L4 in the overall Enterprise Risk Management L2 porcess descriptions and L3-L4 descriptions in the Fraud Management area, extracted from GB947

11/27/2011 4:59:13 PM

Frameworx Alignment

The key challenges to be addressed, are: •What alignment means and membership benefits? •What Framework artifacts are impacted? •What changes to technical artifacts are needed? •What changes /enhancements to Framework development process and procedures need to be put in place? The draft report(attached) identifies four areas of improvements: •Design Rules: for Component Frameworks; •Integration ...

9/23/2011 5:11:17 PM

Please wait whilst your download is being compiled.

Paid Advertisement