| Inobits Migration Packages available |
Level I – Basic |
Level II – Advanced Customized complex migration |
| Criteria |
This level is aimed at smaller companies or limited K2 installations (e.g. departmental) and would cover the following scenarios:
- Non clustered K2 server
- Workflow processes that do not need custom code changes - examples 1) to make required code changes in ASP.net 2) InfoPath changes & BizTalk orchestration 3) custom code in process definition 4) code changes to web services
|
This level is aimed at the high end corporate/enterprise installations and would cover the following scenarios:
K2 servers clustered or non clustered
Workflow processes that need custom code changes – examples 1) to make required code changes in ASP.net 2) InfoPath changes & BizTalk orchestration 3) custom code in process definition 4) code changes to web services
Complex and various workflow processes, utilizing custom coding throughout. Potentially heavy dependence on external processes (SharePoint, BizTalk)
This level is aimed at the high end corporate/enterprise installations and would cover the following scenarios:
- K2 servers clustered or non clustered
- Workflow processes that need custom code changes – examples 1) to make required code changes in ASP.net 2) InfoPath changes & BizTalk orchestration 3) custom code in process definition 4) code changes to web services
- Complex and various workflow processes, utilizing custom coding throughout. Potentially heavy dependence on external processes (SharePoint, BizTalk)
|
| Details |
Assumptions (already installed applications)
- SQL Server 2000 or 2005 with Reporting Services
- Configured in Windows 2003 operating system
- K2 2003 SP4 installed
- Client Workstation available, joined to domain on arrival Client Workstation must have Visual Studio 2005 installed
- New Server must have operating system already installed and joined to domain.
|
Assumptions (already installed applications)
- SQL Server 2000 or 2005 with Reporting Services
- Configured in Windows 2003 operating system
- K2 2003 SP4 installed
- Client Workstation available, joined to domain on arrival Client Workstation must have Visual Studio 2005 installed
- New Server must have operating system already installed and joined to domain.
|
| Dependencies |
- K2 blackpearl™ v. 0807 license purchased
- SQL Server 2005 with Reporting Services license purchased if running SQL Server 2000
|
- K2 blackpearl™ v. 0807 license purchased
- SQL Server 2005 with Reporting Services license purchased if running SQL Server 2000
|
| Deliverables |
- Analysis of current K2.net 2003 processes + environment
- New production environment running K2 K2 blackpearl™ 0807
- All existing K2 2003 process definitions and active process instances migrated.
- InfoPath forms templates and associated XML files reconfigured & migrated if needed.
- Existing K2.net 2003 server can be decommissioned & shut down after migration
- Inobits Migration Toolset for K2
|
- Analysis of current K2.net 2003 processes + environment
- New production environment running K2 K2 blackpearl™ 0807
- All existing K2 2003 process definitions and active process instances migrated.
- InfoPath forms templates and associated XML files reconfigured & migrated if needed.
- Existing K2.net 2003 server can be decommissioned & shut down after migration
- Inobits Migration Toolset for K2
|
| Objectives/Cost justification |
- Effort and Time Savings: Potentially 4-6 weeks
- Related Cost Savings: Potentially $ 16,000 - $ 24,000 (based on cost of $100 per hour)
|
- Effort and Time Savings: Potentially 4-6 weeks
- Related Cost Savings: Potentially $ 16,000 - $ 24,000 (based on cost of $100 per hour)
|
| Project Duration |
Estimated 5 days – determined during initial scoping session. |
Estimated 10 days – determined during initial scoping session. |
| Project Cost |
$15,000 - Includes:
1. Inobits Migration Toolset
2. 1 week (5 days consultation)
3. T & E |
$25,000 - Includes:
1. Inobits Migration Toolset
2. 2 weeks (10 days consultation)
3. T & E |
| Disclaimers |
- Requirements for Technical Personnel.
-
Our personnel must be given Administrative access to all new and old Servers
before arrival.
-
It is strongly recommended that our personnel be given Domain Administrator
access. If this is not possible, we need to have reasonable access (approx. 1-2
hours per day) to a domain administrator for network tasking during the course
of the migration, Domain Administrator will be asked to configure new Service
Accounts for K2 blackpearl™ as well as Configure Authentication and
Authorization in the network for all services which K2 blackpearl™ depends on.
-
All servers with production code, processes, process instances, etc. must have
full backups done prior to arrival or we are not responsible for lost data.
|