Click here to TINA-C home page
compliance.JPG (12678 byte)

TINA Compliance Matrix

Compliance Level


Business Benefits


Alignment In Principle Aligned with first principles of TINA, e.g. the role of intelligent software in setting up services, separation of logical and physical descriptions of services,… The first steps towards enabling a business to provide value added services in a flexible way. It also enables you to organize a business to take on one or more of the TINA business roles without performing them all. Can be hard to distinguish from other initiatives such as DEN. Will require short, skillful explanation.
Concept Conformance Systems that are organized according to top level TINA reference models (such as the retailer model). Organized to perform one or more distinct business roles.

Industry shared recognition of problems with a solid context for dealing with them.

Clarity and completeness of TINA concepts is critical to expressing this. Once concisely expressed these concepts and basic models will be broadly valued and accepted.
Layering/Partitioning Compliance Systems that are functionally decomposed in accordance with TINA. 

TINA reference points exist logically, but do not comply with the TINA specified interfaces..

Ability to execute a TINA business role in the telecommunications services business 

Ability to manage development and maintenance of systems using TINA as a template. Functional programming requirements are a priori known and TINA programming knowledge directly can be applied.

Possible bridging between such systems and other systems at this level of conformance.

Ability to be flexible in defining, deploying, or leveraging telecommunications services.

Clarity and completeness of TINA model will become an issue. The Layering and partitioning requirements will need to be made distinct and enforceable. 
Information Model Compliance Object classes defined according to TINA. Operations defined with semantic equivalence to TINA operations. Bridging among other TINA Compliant third party systems within or external to a service provider is straightforward.  Externalized information model is linked with internal model. Not typically able to unlink internal and external views. 
Technical Compliance Systems that conform to the reference points and can interoperate over these interfaces. [without any extra agreements or interfaces] Have systems that are functionally adequate with assured interworking.

Ability to purchase and deploy third party software solutions an integrate them directly with other TINA systems.

Completeness and adequacy of a reference point must be demonstrated for each reference point interface. Also most interfaces expose internal information models.
Operational Compliance Systems that both technically conform to TINA and can interoperate at a guaranteed service level in terms of responsiveness, availability and other service level guarantees. Ready to inter-operate with any other business with similar TINA compliant systems. The concept of operations and service levels for TINA services themselves is yet to be dealt with. [CORBA does not either!]

No TINA system has demonstrated the ability to operate at this level. TINA will be meaningful once this is proven.

link back to TINA Compliance