B. Decision support systems (DSS)

Α. On-line transactional processing systems OLTPs are systems which serve transactions with suppliers, partners and customers, as well as internal business transactions. They support operations throughout the value chain of the Organization:

• Supply Chain Management (SCM)
• Production support (e.g. MRP, Advanced Planning & Scheduling)
• Customer interface management (e.g. sales, order management and billing) (CRM)
• Finance and Accounting (ERP)
• Sales force automation
• Web channel operations (eCRM)
• Internal workflow support systems

1. Clearly specified given that the system serves specific functional needs – the predetermined transactions
2. the determination of a complete requirement set is a challenge, given that there are dynamically changing informational requirements.

1. Current state information is captured (some historical data may exist only to serve potential future transactions)
2. Recent and historical information is captured (current may not be captured, given that data from the OLTP are retrieved at regular intervals)

1. Complex, focused on business entities (in terms of relational databases it is called normalized data structure (e.g. 3NF))
2. Different approaches exist. The simplified denormalised dimensional structure gains momentum, since it allows easier understanding by business users and optimized execution of complex queries.

1. Detailed data per transaction are kept
2. Detailed data are kept in a different structure and are enriched by ‘dimensional’ information which allows analytical processing. Moreover, aggregated data like KPIs (key performance indicators), are calculated and stored in persistent storage.

1. The volume of data is relevant to the size of the Business and the penetration of IT in it.
2. The data volume handled by a DSS, is multiple of that of the OLTP systems
   Easy Fundraisers
   You are probably here searching for information on fundraisers and fundraiser ideas. We want to make your fundraiser easy for you, it doesn’t have to be a difficult task setting up your fundraiser, and in fact the easier it is, the higher your success rate!You know that you would like to host a fundraiser for your company, school or organization to raise funds but how can you set your fundraiser in motion? This fund
   terface management (e.g. sales, order management and billing) (CRM)
3. Finance and Accounting (ERP)
4. Sales force automation
5. Web channel operations (eCRM)
6. Internal workflow support systems
Β. Decision support systems DSS provide management at all levels of the Organisation, with information which supports understanding of the current Business position and taking informed decisions (fact based management). OLTP vs DSS systems Even though OLTP (on-line transactional processing) and DSS (decision support systems) functionalities may overlap (e.g. an OLTP system may provide some operational reporting functionality used for decision support), it is clear that the purpose of the 2 categories differs, given that they serve different functions and different User groups in the Business. Therefore the development philosophy of the two categories differs radically. Specifically, differences are identified on the following criteria (1 for OLTP, 2 for DSS): System functional requirements:
1. Clearly specified given that the system serves specific functional needs – the predetermined transactions
2. the determination of a complete requirement set is a challenge, given that there are dynamically changing informational requirements.
Capture of current and historical information:
1. Current state information is captured (some historical data may exist only to serve potential future transactions)
2. Recent and historical information is captured (current may not be captured, given that data from the OLTP are retrieved at regular intervals)
Data models used:
1. Complex, focused on business entities (in terms of relational databases it is called normalized data structure (e.g. 3NF))
2. Different approaches exist. The simplified denormalised dimensional structure gains momentum, since it allows easier understanding by business users and optimized execution of complex queries.
Information level of detail:
1. Detailed data per transaction are kept
2. Detailed data are kept in a different structure and are enriched by ‘dimensional’ information which allows analytical processing. Moreover, aggregated data like KPIs (key performance indicators), are calculated and stored in persistent storage.
Volume of data:
1. The volume of data is relevant to the size of the Business and the penetration of IT in it.
2. The data volume handled by a DSS, is multiple of that of the OLTP systems
   6 Great Ways to Use E-Technology to Fund Your Business - and When Not to Use It At All
   Beginning with Dible’s Up Your Own Organization several decades ago, business plans have been nearly sacred tools in communicating with potential lenders and investors.Now the electronic age has brought an avalanche of new gizmos to the equation, such as CDs, emails, and online business plans. A cell phone number has become as essential as a business land line.Just how useful are these gizmos, really? In tr
   ) functionalities may overlap (e.g. an OLTP system may provide some operational reporting functionality used for decision support), it is clear that the purpose of the 2 categories differs, given that they serve different functions and different User groups in the Business. Therefore the development philosophy of the two categories differs radically. Specifically, differences are identified on the following criteria (1 for OLTP, 2 for DSS): System functional requirements:
   1. Clearly specified given that the system serves specific functional needs – the predetermined transactions
   2. the determination of a complete requirement set is a challenge, given that there are dynamically changing informational requirements.
   Capture of current and historical information:
   1. Current state information is captured (some historical data may exist only to serve potential future transactions)
   2. Recent and historical information is captured (current may not be captured, given that data from the OLTP are retrieved at regular intervals)
   Data models used:
   1. Complex, focused on business entities (in terms of relational databases it is called normalized data structure (e.g. 3NF))
   2. Different approaches exist. The simplified denormalised dimensional structure gains momentum, since it allows easier understanding by business users and optimized execution of complex queries.
   Information level of detail:
   1. Detailed data per transaction are kept
   2. Detailed data are kept in a different structure and are enriched by ‘dimensional’ information which allows analytical processing. Moreover, aggregated data like KPIs (key performance indicators), are calculated and stored in persistent storage.
   Volume of data:
   1. The volume of data is relevant to the size of the Business and the penetration of IT in it.
   2. The data volume handled by a DSS, is multiple of that of the OLTP systems
      Create a Magic Connection with Clients, Leads, and Business Associates -- Part I
      A few months ago, arriving at a client’s office to begin a group meeting, I discovered that two women, who had committed to joining us, had changed their minds. I knew they were apprehensive, not sure what to expect from someone doing Neuro-linguistic Programming (NLP). I decided to talk with them and see if I could put them at ease. As I walked toward them, I noticed that they were both standing with their shoulders slump
      hallenge, given that there are dynamically changing informational requirements.
   Capture of current and historical information:
   1. Current state information is captured (some historical data may exist only to serve potential future transactions)
   2. Recent and historical information is captured (current may not be captured, given that data from the OLTP are retrieved at regular intervals)
   Data models used:
   1. Complex, focused on business entities (in terms of relational databases it is called normalized data structure (e.g. 3NF))
   2. Different approaches exist. The simplified denormalised dimensional structure gains momentum, since it allows easier understanding by business users and optimized execution of complex queries.
   Information level of detail:
   1. Detailed data per transaction are kept
   2. Detailed data are kept in a different structure and are enriched by ‘dimensional’ information which allows analytical processing. Moreover, aggregated data like KPIs (key performance indicators), are calculated and stored in persistent storage.
   Volume of data:
   1. The volume of data is relevant to the size of the Business and the penetration of IT in it.
   2. The data volume handled by a DSS, is multiple of that of the OLTP systems
      Profit Potential of the Product Life Cycle
      Every product has a life cycle and the various stages of this can produce different profit margins and as such it is best to be aware of the product life cycle when looking at your selling margins going forward, first lets define the Product Life Cycle:The timescale within which a product is introduced leading to a growth in sales, before sales mature and begin to decline, possibly even ending in the product bein
      s momentum, since it allows easier understanding by business users and optimized execution of complex queries.
   Information level of detail:
   1. Detailed data per transaction are kept
   2. Detailed data are kept in a different structure and are enriched by ‘dimensional’ information which allows analytical processing. Moreover, aggregated data like KPIs (key performance indicators), are calculated and stored in persistent storage.
   Volume of data:
   1. The volume of data is relevant to the size of the Business and the penetration of IT in it.
   2. The data volume handled by a DSS, is multiple of that of the OLTP systems on which it is based, given that it maintains multiple historical snapshots
   Copyright 2006 – Kostis Panayotakis