Sample Policy

Who we are

Oxcyon and Centralpoint are in the Gartner Magic Quadrant for Digital Experience Platforms. Centralpoint can be installed On Premise or in the Cloud, empowering it's users with over 220 modules which harmonize your information and how it serves each of your users

securely. Oxcyon is a privately held S Coporation, who successfully competes against Microsoft Sharepoint, OpenText, IBM, Oracle, Adobe, Liferay and others. Our approach of providing a high fidelity Prototype at no cost to our clients, Before they buy, does more than just completely eliminate their risk; it's says everything about our company.

Centralpoint goes (way) beyond enterprise knowledge management, tackling the need to aggregate and index your disparate data. Centralpoint offers unique tools to tranform your organization like Data Transfer, Automating Metadata, Global Login, and over 200 others (seen in our Module Gallery) to empower you with a sound platform. Digital Experience Platforms consolidate and harmonize the many fragmented tools which came before; content, documents, digital assets, products, LMS, videos and serves each user based on their Roles and preferences.

Centralpoint is in use by over 350 organizations including Fortune 1000, Healthcare, Manufacturing and Government. Centralpoint offers a unique bi weekly, Evergreen, remote update allowing Oxcyon to keep up with its growing list of clients either On-Premise or in the Cloud; eliminating obsolesence. Tell us more about your project and let us Prove to you how versatile Centralpoint is by proving it to you.

Oxcyon has enjoyed early market adoption within: Healthcare, Government, Manufacturing, Distribution, Government, Non Profit and Publishing verticals.

05. Use Case Models

5.1 Use Case Descriptions (for selected cases)

Notes:

For all use cases, the user can cancel the use case at any step that requires user input. This action ends the use case. Any data collected during that use case is lost.
For all use cases that require a logged in user, the current login session is updated during the use case to reflect the navigation paths through the use case.

Login User

Use Case Name:	Login User
Summary:	In order to get personalized or restricted information, forms or specialized transactions a user must login so that that the system can determine his/her access level.
Basic Flow:	The use case starts when a user indicates that he wants to login. The system requests the username and password. The user enters his username and password. The system verifies the username and password against all registered users. The system starts a login session and displays a welcome message based on the user's preferences.
Alternative Flows:	Step 4: if username is invalid, the use case goes back to step 2. Step 4: if the password is invalid the system requests that the user re-enter the password. When the user enters another password the use case continues with step 4 using the original username and new password.
Extension Points:	none
Preconditions:	The user is registered.
Postconditions:	The user can now obtain data and perform functions according to his registered access level.
Business Rules:	Some data and functions are restricted to certain types of users or users with a particular access level.

Register User

Use Case Name:	Register User
Summary:	In order to get personalized or restricted information, access forms or do other specialized transactions a new user must register a username and password.
Basic Flow:	The use case start when a user indicates that he wants to register. The system requests a username and password. The user enters a username and password. The system checks that the username does not duplicate any existing registered usernames. The system requests Client expected fields (i.e. name (), street, city, state, zipcode(), password, Employee ID) Items marked by (*) are required. The user enters the information. The system determines the user's location and access level and stores all user information. The system executes use case Forms Gallery. The system starts a login session and displays a welcome message based on the user's preferences.
Alternative Flows:	Step 4: If the username duplicates an existing username the system displays a message and the use case goes back to step 2. Step 5: If the user does not enter a required field, a message is displayed and the use case repeats step 4.
Extension Points:	Register Preferences
Preconditions:	none
Postconditions:	The user can now obtain data and perform functions according to his registered access level.
Business Rules:	A registered user's location is the Department, Role or Region nearest his zip code via SAML/AD. Access levels are 0: A user can access only data classification 0 1: The user can access data classification <= 1 2: The user can access data classification <= 2 The default access level is 0. Classification types will be defined and managed by the Client, Oxcyon will simulate these within it's development portal (at Oxcyon)

Register Preferences

Use Case Name:	Register Preferences
Summary:	This use case allows a registered user to enter or change his preferences.
Basic Flow:	The use case start when a user indicates that he wants to enter or modify his preferences. The system displays all current product lines. It indicates any product lines that the user has currently selected. The user selects/deselects Regional or Topical Interests. The system displays current language preferences. It indicates the language preference currently selected. The user may select a different language preference. The system stores any change to language preference.
Alternative Flows:	none
Extension Points:	none
Preconditions:	The user is logged in.
Postconditions:	The system can customize a welcome message based on the user's revised preferences.
Business Rules:	Language selections allowed are are English (default), French and German, for the Pilot (full license includes all).

Place Order (Customer)

Use Case Name:	Select Form Scenario: Staff member fills out the needed form.
Summary:	This use case allows a registered customer to begin creating a collection by selecting a form (from the form gallery).
Basic Flow:	The use case start when a customer indicates he wants to begin a collection. The system displays the customer's information: name, street, city, zip, phone, email, role, department. The customer may add or change any of the information. The system stores any changes. If the zipcode has changed, the system modifies the customer's location. The system requests which form the user would like. The staff member selects their form. The system displays the appropriate questions and fields based upon that form type. The customer selects the appropriate options they want (selecting from various data sources available to them (for that form). The system completes the form when user selects 'SUBMIT' button. The system shows a 'processing icon' as the collection is created. . The system displays a Document (or asset) completion message and prompts the user to view the completed asset.
Alternative Flows:	Step 9: If the selections (within the form) could not be validated (if a data source is unavailable) , go to step 8 to get another option. Step 10: If the quantity on hand is not sufficient for this form, a message is sent to the customer and the use case is canceled.

Services

Although Centralpoint is the most robust, market ready Digital Experience Platform in the industry, no solution is ever 100% ready out of the box. Your organization, markets, and projects are unique, and that means we will likely need to customize it around your needs. Often times this might mean only the UI or Design, other times, there may be more complex Integration or workflow.

We have had the experience working on over 350 engagements over the past 20 years, and pride ourselves on a no nonsence approach to 'get it done'. Unlike most consultants, we do not prey on the amount of time things take, and can often work much faster than our clients can feed us their data, or instruction.

You can expect absolute professionalism from our staff. We are proud to offer a no nonsense, take charge attitude, without unnecessary paperwork, terminology or nonsense. Building your project is complex, and we bring leading industry experts to help you accomplish the task, starting with your Project Manger. This individual will manage your project from Kick Off to Launch, organizing each task in our Issue Management system, tracking every detail and providing a complete audit trail. Your project manager will work with the internal resources needed such as designers, database engineers, developers and (where applicable) network/server resources; acting as your central point of communication at all times. Our job is to gather the information we need, and get the job efficiently, taking up the least amount of time from your team.

After launch your Project Manager will continue to monitor your project's success, and update you with our Evergreen Updates, guaranteeing it will be just years from today as when it launched.

How to render a Semantic Keywords Tag Cloud - Against an Individual Record (Policies)

Data Sources

Events

Reports Library

Staff

Font Resize

Contrast

Indexed Content, Copy or HTML

Who we are

05. Use Case Models

5.1 Use Case Descriptions (for selected cases)

Notes:

Login User

Register User

Register Preferences

Place Order (Customer)

Services

Taxonomy Detected for his Record

Semantic Relevance for this Record

Document History

Generic A - Standard

Submitted Forms

Sharepoint Records

Photo Galleries

Staff

Navigation