 Agency Code Population
|
A standard that was introduced as an interim solution in the drive to assist individual agencies identifying their agency number for a particular piece of business. Product providers allocate agency numbers according to different criteria and each agency may have multiple agency numbers for multiple product providers.
|
|
Bulk Data Download
|
A standard that was developed to ensure provision of summarised contract data by Product Providers to IFAs in a consistent and common format.
|
|
Business Data Content
|
A document that details, at a business level, data that will be contained within a message Standard. The document contains non-technical data definitions, and may be defined for all products, or for agreed product groupings. Where the data capture is being standardised (e.g. where a common look and feel is required), then the Business Content will specify the groupings and sequence of data items along with the actual field captions that are to appear on the screen. This information is provided in addition to the data definitions.
|
|
Business Object
|
A reusable structure, expressed in UML format, which has been identified as being common across a number of domain models e.g. document, company, fund.
|
|
Business Process Model
|
A diagram describing the business activity for which standardisation is being looked at. It contains process descriptions and clearly identified areas for standardisation
|
|
Champion
|
The person within a standards holder organisation who acts as a point of contact and is responsible for promoting the adoption of standards within that organisation.
|
|
Change Control
|
The process that governs the management of change to the Origo Standards.
|
|
Change Request
|
A formal request for a change to a Standard, or the development of a new Standard, submitted for approval to Origo. Change Requests may be raised by a user of the Standard or by Origo on behalf of the industry as a result of legislative changes, industry initiatives, internal analysis etc.
|
|
Client
|
Any member of the public or a company representative who has, or wishes to arrange, a contract agreement with a product provider.
|
|
Commission
|
Commission processing covers the electronic transfer of information relating to commission which is paid to advisors by product providers. The functions that are covered include electronic commission transfer, similar to statements which accompany a transfer of money, and events that impact the amount of commission being paid.
|
|
Community
|
Individuals or companies using or receiving an approved and released Origo Standard.
|
|
Contract
|
A policy or other agreement between a product provider and a client.
|
|
Contract Enquiry
|
A key contract servicing process that allows enquiries, made by different parties (such as IFA or client), that are submitted to Product Providers, either directly or via a third party Service Provider/Portal. Typical enquiries made against existing contracts would cover different types of valuations, such as fund values, surrender values, paid up valuations.
|
|
CSV
|
Comma Separated Values. A way of recording data fields in text format; a comma follows each field.
|
|
Declaration Approach
|
Process of submitting new business using a combination of signed Declaration and electronic message.
|
|
Document Personalisation
|
An Origo Standard that facilitates personalisation of Product Provider literature with IFA details.
|
|
Domain Model
|
A domain model is used to record all the data included in a particular set of processes e.g. Quotes/New Business. The domain models contain class diagrams and data definitions and are used to specify how the physical messages will be structured.
|
|
EDI
|
Electronic Data Interchange. The computer (application system) to computer (application system) exchange of structured data for automatic processing.
|
|
EDIFACT
|
Electronic Data Interchange For Administration, Commerce and Transport. An international standard designed for the automatic exchange of structured information.
|
|
Electronic Message
|
A business transaction transmitted in an agreed electronic format.
|
|
Event
|
A change in the circumstances of a client or a contract.
|
|
Extranet
|
An extranet is a private network that uses the internet protocol and the public telecommunications system to securely share part of a Product Provider's services or operations with IFAs, clients or other businesses.
|
|
Extranet Linking Process
|
A standard process that defines how Portals and third parties link to Product Provider Extranets
|
|
FAQs
|
Frequently Asked Questions
|
|
FSA
|
Financial Services Authority, the single UK statutory regulator directly responsible for the regulation of deposit taking, insurance and investment business.
|
|
Functional Design
|
Used where a further level of detail is required (typically for large Standards Development Projects), this documentation contains more detailed business process models.
|
|
HTML
|
HyperText Markup Language, used to specify web pages.
|
|
HTTP
|
HyperText Transfer Protocol. A protocol that facilitates the transfer of hypertext based files between communicating computers.
|
|
HTTP Message Transmission Guidelines
|
Describes the information and format of the messages as they are sent from sender to receiver using the HTTP 1 POST and HTTP 1 GET methods that contain data in XML format. This Standard intends to be independent of any specific business process; business data content of a message is subordinate and wholly contained within a standard XML structure.
|
|
IFA
|
Independent Financial Advisor. An individual or organisation authorised by the FSA to provide financial advice.
|
|
Industry
|
UK Protection, Pensions and Investment market and any third party which has an involvement in this market such as the Data Protection Registrar, Inland Revenue and DSS.
|
|
ISDD
|
Industry Standard Data Dictionary. A dictionary of data items and data formats developed and agreed as standard by the industry. Also a registered trademark of Origo.
|
|
ISEF
|
Industry Standard E-commerce Framework. Produced by Origo as a publication repository for all Origo Standards, it provides a framework to ensure consistency across the Standards.
|
|
ISML
|
Industry Standard Markup Language. Published as one of Origo's technical standards, it is a computer language that allows the software developer to define the intentions of an electronic form, but not its presentation.
|
|
Keyword
|
A word that is used to define a search.
|
|
LAUTRO
|
Life Assurance and Unit Trust Regulatory Organisation, superseded by the PIA.
|
|
Logical Data Model
|
A logical generic data model encompassing all of the processes and products covered by the Origo Standards. It is used as the starting point in the analysis phase of message standards and provides consistency of data definition across different message services.
|
|
Message Views
|
Message views are subsets of an overall domain model. They are usually defined according to a particular product, or message type. All the data structures and relationships within a message view are consistent with those defined in the overall domain. The purpose of the message views is to further specify only the data that is relevant to a particular message, rather than using the overall domain that contains data for all products and messages within the functional area.
|
|
Messaging Security Solution
|
An overview document that describes the approach a new Trading Partner to the Industry should take to security. It covers data confidentiality, authentication, authorisation, data integrity and non-repudiation.
|
|
MFG
|
Message Functional Guideline. A document within the Origo Message Standards that contains the business rules and data content for business messages. Used in some of the older Origo standards e.g. EDIFACT Commission.
|
|
MIG
|
Message Implementation Guide. A document that defines, at a technical level, the syntax, structure and layout of a particular message, or group of messages. The MIG is typically used by developers when they come to implement a particular message, and often is the main (or only) document that they refer to.
|
|
Migration Mapping
|
Published to assist organisations upgrade to the new versions of standards. This documentation translates from one version of a standard to another, and can be done both forwards and backwards. The documentation is in two forms, the first being a guide containing details of each data item in the 'old' version and explains how it is represented in the 'new' version. The second mapping component is an XSLT mapping which can be used to automatically convert from one version to another of the standards.
|
|
New Business
|
A key part of the sales process, covering the collection of data required for new business proposals and the submission of new business applications. It covers a wide range of products.
|
|
News
|
An item of information published by Origo.
|
|
PAC
|
Product Application Components – electronic application forms used for the submission of New Business.
|
|
PDF
|
Portable Document Format – a file format used by Adobe Acrobat and commonly used for the formatted presentation of documents within web browsers.
|
|
Pension Transfer
|
Covers the transfer of a member from one pension scheme to another. Only one part of this overall process is covered by an electronic message, and that is the Transfer Value message sent by the ceding Product Provider to the new Product Provider. Many more flows of information are required to complete the process and these are carried out by manual completion of paper forms and by other non-electronic mechanisms.
|
|
PIA
|
Personal Investment Authority – industry regulator, subsumed within the FSA in December 2001.
|
|
Portal
|
An organisation that offers a set of web services to its subscribers. Its website is or proposes to be a major starting site that subscribers tend to visit as an anchor site when performing electronic commerce.
|
|
Product Provider
|
A company that provides protection, investment or pension products in the UK.
|
|
Product Type Definition
|
A document that defines the rationale behind the Standard Product Type and Sub Type definitions used within the Origo Standards. Product Types and Sub types are the main data items that define a protection, pension or investment product.
|
|
Proposal
|
Information sent electronically from an IFA to a Product Provider for establishing a new contract.
|
|
Quotation Service
|
A service provided by a third party supplier which, on request, provides an enquirer to that Quotation Service with one or more Quotes based on specific Client Information. A Quote provided directly by a Product Provider to an IFA is not considered a Quotation Service.
|
|
Quote or Quotation
|
An offer from a Product Provider for a contract based on a Quote Request and specific Client Information that may be provided via a Quotation Service or directly from a Product Provider.
|
|
Quote Request
|
A request for a Quote on behalf of a specific Client.
|
|
Remote Publishing
|
A standard that gives Product Providers a common and standard way to distribute documents to their customers, across all Service Providers/Portals and Software Suppliers. In addition, it can be used for publishing documents on their own internal (intranet) and external (extranet) websites.
|
|
Requirements and Principles
|
A document that is produced during the requirements phase of standards development, containing the key business needs that are driving the solution and any principles that should be adhered to. This document will also define the scope of the Standards development.
|
|
Sample Messages
|
For each standard, a number of sample messages are produced to assist the users of the standard in understanding the meaning and structure of the data. The intention is to provide realistic samples, and also as much supporting text and hints as possible within the samples.
|
|
Sentinel
|
An Origo Standard that describes the method by which a Service Provider can tell whether a Product Provider is able to receive and return transactions.
|
|
Service Level Agreement
|
An agreement or contract between a supplier and its trading partner (customer) that sets out details of the service being delivered by the supplier.
|
|
Service Provider
|
Any software house, service integrator or network supplier that offers to provide facilities to aid electronic commerce.
|
|
SIB
|
Securities and Investments Board, superseded by the FSA in October 1997.
|
|
Sponsor
|
A Product Provider who has a shareholding in Origo.
|
|
Sponsor Forum
|
The Origo Sponsor Forum acts as the group that delivers input at Champion level, an agreed view on timescales and priorities for Standards activities and a business context for the Standards Strategy Group.
|
|
Standard
|
A document or procedure standardised across the industry, e.g. a New Business XML message.
|
|
Standard Data Types
|
Each data item used in all of the Origo messages is allocated a data type which determines its format and length. These Standard Data Types are published in ISEF and are shown in a format for use within XML Schemas.
|
|
Standard Values List
|
A number of the data elements and attributes within the Origo Message Standards may only contain values from a prescribed list, the Standard Values List. These are used alongside the XML schema to restrict the values that may be contained within the elements or attributes of a particular Origo standard message.
|
|
Standards Development Methodology
|
An outline of the approach used in the development of the standards, which also describes the type of documents that are delivered at different stages of the development process.
|
|
Standards Governance
|
In developing and maintaining Standards, Origo requires input from the Industry. How this input is sought is defined by the Standards Governance, which details the structures that exist to ensure that the optimum mix of business and technical input is achieved.
|
|
Standards Management
|
The provision of an ongoing support and maintenance function to allow Standards to be adapted and enhanced to meet the growing needs of a trading community.
|
|
Standards Strategy Group
|
This group’s primary role is to agree elements of technical strategy across all of Origo’s Standards. The group has an IT focus, with members’ skill set equivalent to those found in a function, common to many institutions, known as the Technical Design Authority.
|
|
Thread
|
Origo website users may reply to specific postings to ‘Have Your Say’ items, further postings may in turn respond to that reply and so on. Such a chain is referred to as a thread. Threads may branch and continue indefinitely. Each thread may be traced back to one initial posting.
|
|
Topic
|
A categorisation of News or FAQ’s.
|
|
Tracking
|
This standard enables the status of a particular transaction to be communicated by a Product Provider to an interested party, such as an IFA. Tracking can currently be used for monitoring the progress of New Business Submission, and in the future its functionality will extend to Collective Investment ‘buy’ transactions. It will also be extended to provide early notification of commission data.
|
|
Trading Partner
|
One of a trading community exchanging business information in an electronic form.
|
|
UML
|
Unified Modelling Language. A standard notation for the modelling of real objects. Used by Origo in its Business Objects, Domain Models and Message Views.
|
|
URL
|
Uniform Resource Locator – essentially a web address.
|
|
W3C
|
World Wide Web Consortium. A body that exists to realize the full potential of the Web. The W3C is an industry consortium which seeks to promote standards for the evolution of the Web and interoperability between WWW products by producing specifications and reference software. Although W3C is funded by industrial members, it is vendor-neutral, and its products are freely available to all.
|
|
Work In Progress
|
A term that applies to the set of draft standards that are available for a particular process.
|
|
Working Group
|
Working groups consist of representative members of the industry, concentrating on a stream of work relating to the development, implementation or maintenance of standards.
|
|
XML
|
eXtensible Markup Language. A message format used in Origo Standards.
|
|
XML Schema
|
XML Schemas are provided for all Origo XML messages. XML Schemas may be used for XML message validation and define amongst other things, element and attribute names, enumerated lists, data format and the order of element groups and elements that make up the XML message.
|
|
XSLT
|
eXtensible Stylesheet Language Transformation. Used to describe how to change the structure of an XML document into an XML document with a different structure.
|
|
