<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-GB">
		<id>https://www.bxpsoftware.com/wixi/index.php?action=history&amp;feed=atom&amp;title=Project_Outline_-_System_Setup</id>
		<title>Project Outline - System Setup - Revision history</title>
		<link rel="self" type="application/atom+xml" href="https://www.bxpsoftware.com/wixi/index.php?action=history&amp;feed=atom&amp;title=Project_Outline_-_System_Setup"/>
		<link rel="alternate" type="text/html" href="https://www.bxpsoftware.com/wixi/index.php?title=Project_Outline_-_System_Setup&amp;action=history"/>
		<updated>2026-04-18T14:39:51Z</updated>
		<subtitle>Revision history for this page on the wiki</subtitle>
		<generator>MediaWiki 1.28.2</generator>

	<entry>
		<id>https://www.bxpsoftware.com/wixi/index.php?title=Project_Outline_-_System_Setup&amp;diff=6705&amp;oldid=prev</id>
		<title>Philip Lacey: Created page with &quot;= Overview =   As each system in bxp is unique the setup of each system is unique.  This document provides the significant milestones required for a setup to allow for quotati...&quot;</title>
		<link rel="alternate" type="text/html" href="https://www.bxpsoftware.com/wixi/index.php?title=Project_Outline_-_System_Setup&amp;diff=6705&amp;oldid=prev"/>
				<updated>2016-05-23T09:23:06Z</updated>
		
		<summary type="html">&lt;p&gt;Created page with &amp;quot;= Overview =   As each system in bxp is unique the setup of each system is unique.  This document provides the significant milestones required for a setup to allow for quotati...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;= Overview =&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
As each system in bxp is unique the setup of each system is unique.  This document provides the significant milestones required for a setup to allow for quotation and understanding of timings involved.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Approach = &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
There are three approaches generally speaking when setting up.&lt;br /&gt;
&lt;br /&gt;
* Hands on: the bxp client performs all the work (there will be no time required from All n One)&lt;br /&gt;
&lt;br /&gt;
* Collaberative: there is training session / side by side approach.  Depending on comfort levels, more or less can be done by one side or the the other (bxp client | All n One support team) (times will be 1.5 times those given below)&lt;br /&gt;
&lt;br /&gt;
* Hands off: the All n One team perform all the work  (times will be close to what is given below)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Security = &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Whilst most of the setup requirements are gathered by our team, here is the check list used to ensure we have the basics in place.&lt;br /&gt;
&lt;br /&gt;
* Who is the nominated System Champion(s)&lt;br /&gt;
* As a general approach is this client hands on or off during the setup.&lt;br /&gt;
* Who is the Security Champion&lt;br /&gt;
* As a general approach what is the security appetite of the client (very secure | very accessible)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
With these basics in mind, the first document is the security configuration matrix which must be filled out. [[CC-2-1_Security_and_Custom_Interface_configuration#Matrix]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= User Setup =&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For billing purposees we identify the departments involved and get them set up. (30 mins - 1 hour)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Then we create the organogram from the documentation gathered during &amp;quot;requirements gathering&amp;quot;  (30 mins - 1 hour)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Next we figure out the general &amp;quot;roles&amp;quot; that will be using the system.  user, manager, administrator those kind of titles.  We then create a sample user for each role.  (20 mins per role)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Then depending on the security appetite we configure the security of the system as per the matrix.  If Single Sign On is required budget 8 hours for configuration testing and support.  All other configurations approximately 4 hours.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Form building =&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
As forms can be incredibly complex or very simple the time for doing forms varies greatly.  The following are gross guesstimes.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Build from an Excel sheet. 30 mins.&lt;br /&gt;
&lt;br /&gt;
* Tweak field mapping. 10 mins.&lt;br /&gt;
&lt;br /&gt;
* Optimise search options. 20 mins.&lt;br /&gt;
&lt;br /&gt;
* Create basic outcomes and align to process. 1 hour.&lt;br /&gt;
&lt;br /&gt;
* Create inline tabs to optimise space. 1 hour.&lt;br /&gt;
&lt;br /&gt;
* Tweak interface to allow better access by role. 1 hour.&lt;br /&gt;
&lt;br /&gt;
* AJAX optimisation of a form. 4 hours per AJAX requirement.&lt;br /&gt;
&lt;br /&gt;
* Cross Campaign Listing / Search.  1 hour per listing.&lt;br /&gt;
&lt;br /&gt;
* Email box integration. 2 hours.&lt;br /&gt;
&lt;br /&gt;
* Logic branching. 1 hour per 20 questions.&lt;br /&gt;
&lt;br /&gt;
* Intermediate outcome: configuration including comms and validation. 1 hour per outcome&lt;br /&gt;
&lt;br /&gt;
* Form quality review. 1 hour.&lt;br /&gt;
&lt;br /&gt;
* Advanced outcome : large volume of data or integration with external systems. 4 hours + per outcome&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Then apply 2 to 4 hours of testing to ensure compliance with requirements.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Topic:System management]]&lt;/div&gt;</summary>
		<author><name>Philip Lacey</name></author>	</entry>

	</feed>