HP³ is a centralized development platform that facilitates all common business operations of High Powered Promotions while remaining agnostic to the technologies that it must interact with.

The goals of centralizing the common business operations are as follows:

· Higher reliability

· Faster product development times

· Higher security

· Improved auditing

· Better reporting, more reporting and more meaningful reports

· More control over business processes

· Easier manageability

· Improved staff productivity

· Improved data insight tools to help us understand our customers

· Better real-time information for monitoring of critical business functions

· Improved “future proofing” of High Powered Promotions technologies

· Allows each HPP property to operate independently while sharing common data between each property

These goals are attained by strongly adhering to established industry standards, normalizing data structures where ever possible and by clearly defining business processes.

Remaining Technology Agnostic

Remaining technology agnostic is a critical part of the goals for HP³. By applying reliable industry standards and remaining agnostic we ensure that future technologies will seamlessly integrate with HP³ technologies.

Currently, all API functionality for HP³ will be built to three standards:

· JSON – This is the most commonly used API standard today, especially with regards to web based products. Almost all advanced web sites employ this technology in some form or fashion. Most commonly as part of the AJAX standard for server-client communications.

· SOAP/XML – This is an older, less supported standard but is still commonly used in the business world. By employing this standard we leave the door open to a number of older but tried and true technologies.

· DAO – This will allow us to design our own custom business products as needed without the overhead of communicating through a wire based API. Although in most cases this would not be suitable for property development, it would be the method of choice for all business operations as it would introduce less overhead and have better performance.

Using these standards will allow us to develop new properties using whatever technologies are best suited for the property as opposed to being locked in to a specific technology that may become defunct in the future.

Current common compatible language technologies are JAVA, Scala, NodeJS, JavaScript, .NET Family (VB.NET, C#, J#, F#), PHP, Python, Ruby, Perl, C, C++, Flash, Unity3D and pretty much any other modern day language.

It should also be noted that ALL modern browsers include support for JSON technologies.

What does HP³ do?

HP³ technology supports and manages a number of business functions.

Unified Credential and Authentication (+Single Sign-On)

HP³ provides a unified credential and authentication system that will track customers across all HPP properties and offers SSO (Single Sign-On) functionality.

This allows for access control across all related HPP properties while allowing each site to operate independently.

Benefits of SSO are:

· Reduced “password fatigue”, customers would not be required to remember an account and password for each individual HPP property

· When implemented correctly, customers would not be required to login separately when moving between HPP properties

· Improved sharing of information between sites (HPP properties)

· Improved customer behavior tracking and demographic information tracking

· Improved Ad placements (presentation)

· Improved customer auditing

Role Management and Access Control

Each user will only need to maintain a single HPP account that can be used for access to all HPP properties. However, the user’s role within that property can be maintained separately for each property. For an example, a user, Fred, could be an administrator on one site but only a customer on another. User roles are completely managed by the HP³ system. These roles can also be used to limit functionality within a property. For example a site might require the use of “Bronze”, “Silver” and “Gold” members. This can easily be handled by HP³ role management with minimal effort.

Unified Credentials

The HP³ credential and authentication system is compatible with third party authentication services and plugins can be built to service:

· Facebook

· Twitter

· Google

· OpenID

· oAuth 1

· oAuth 2

· Microsoft Passport

It should be noted that these third-party authentication vendors can be used without sacrificing any of the other HP³services, such as role management.

Customer Resource Management (CRM)

Customers are managed through a unified HP³ management portal that allows HPP staff access to every customer in the system.

Customer access, role management, demographics, communications, personal data, purchasing behavior, game playing behavior, etc. can all be analyzed and understood from the HP³ management console.

Unified Accounting and Billing

HP³ also manages monetary and non-monetary accounts for each user. Initially this includes a monetary US Dollar account and a non-monetary token account. These accounts are managed using double-entry accounting practices to allow for proper auditing and reporting by the CFO.

Ad Sub-System

HP³ provides highly targeted ad information and will share that information across all HPP properties. This ensures that the HPP ads have the highest conversion rates possible and thus ensures their value in the marketplace (IE: Improved profitability).

Highly detailed customer demographic and behavioral information is tracked and can be used to generate highly targeted ad campaigns in both real-time (IE: on web sites) and on as requested basis (IE: Email or SMS Texting campaigns)

This technology is used for all possible ad types HPP employs (EG: CPA, Email Campaigns, SMS Campaigns, etc.)

Common Data Repository

HP³ also maintains a library of common use data elements. This is used to ensure consistency in data presentation and collection across all properties.

Examples of common repository data include (but are not limited to):

· Country Lists (Names, ISO Codes, Dialing Prefixes, etc.)

· Region Lists (States, Provinces, Territories, Prefectures, etc.)

· Salutations (Mr., Mrs., Miss, Ms., Dr., Prof., etc.)

· Education Levels (High School, Bachelor’s Degree, Masters, etc.)

This will also make translating of these services into other languages much more manageable.