BPC RiskManager Frequently Asked Questions

From RiskWiki
Jump to: navigation, search
  1. How do I get a copy of BPC RiskManager V6.2.5?
  2. Would it be possible to get a copy of the BPC RiskManager V6 installation guide?
  3. Is there a feature listing for the BPC RiskManager windows client and the browser client? We are looking at the possibility of using a mixed client environment based on user specific needs and where they are.
  4. When are multiple BPC RIskManager server licenses required? We are looking to have RM implemented across a group of companies. They will all be using the same instance with same fields and definitions as the subject matter is the same. Can we use a single server license or will we require multiple server licenses?
  5. Can you please provide information on the cost of licensing and the type of licensing for BPC RiskManager V6.x ?
  6. Does your license include the cost of MS SQL Server ?
  7. I just purchased BPC RiskManager. Will you be sending the install disks, and when?
  8. What will need to be arranged prior to the installing BPC RiskManager?
  9. Does the RiskManager client application work with FireFox browsers?
  10. In what programming language is BPC RiskManager written?
  11. Does the RiskManager plug-in itself have a certificate like a java applet does?
  12. For support, what type of support is available (i.e.: email, phone, onsite, etc...)?
  13. What is the best way to get support?
  14. How do I arrange installation support and what is the timeline?
  15. What support packages are available and at what cost?
  16. Is there a cost associated with telephone support (i.e.: cost per call or issue)?
  17. How do I get custom features added, or request new features for BPC RiskManager?
  18. Is there a User Group Forum?
  19. What type of documentation, technical and user is available for BPC RiskManager?
  20. How does one decide the optimum BPC RiskManager configuration?
  21. Is BPC RiskManager a Client-Server application?
  22. What is the difference between the browser plugin and the windows executable RiskManager client?
  23. Database stability: Is the RiskManager essentially a SQL Server application ported to Oracle?
  24. Database support: Which database choice will give us the best level of support?
  25. Security: What is the most secure architecture for BPC RiskManager?
  26. What is the best client version - the browser or non browser Risk Manager client?
  27. What admin account rights are required to setup a browser plug-in?
  28. How do I configure IE for the RiskManager browser plugin?
  29. We just ported our enterprise system to a new server and I can't login. What do I do now?
  30. How do I port BPC RiskManager from test (or dev) to production?
  31. How do I install BPC RiskManager onto a computer running a 64bit Windows OS?
A Frequently asked Question is...

What support packages are available and at what cost?

Answer

The BPC RiskManager Enterprise License fee includes 24 hours telephone technical support and unlimited general email support during the first 6 months after first installation. After the first 6 months technical support is available under the maintenance subscription agreement. The BPC RiskManager Single User License fee includes unlimited email support and 2 hours telephone technical support during the first 3 months.


The BPC RiskManager maintenance subscription includes the support covering software upgrades and technical assistance. The majority of the subscription is dedicated to developing the software upgrades in the Beta and Production release cycles. Clients with current subscriptions receive technical support of up to 36 hours contact in a year on production versions and an additional 2 hours per beta release installed (and an unlimited additional support during a feature development phase if you are part of the Beta testing stream for a specific feature). Depending on the issues encountered and the context of the direct support, above that level we will probably approach you for some additional fees.


Training, configuration, report writing, survey writing, customisation, database conversion (where required), risk advisory, and similar activities are separately negotiated and quoted outside of the maintenance fee. Your quote should cover rates for the additional items (Canada Office). The maintenance fee is for the purposes of installing upgrades and funding the continued development of the software.


All support packages include priority scheduling of requested enhancements. Only current subscribers download, install or use RiskManager software upgrades. Where you have specific customisations (not configurations) you can either register the request with us for inclusion in a future release - under which arrangement its inclusion and timing of release is at our discretion - but significant priority is given to requests from current subscribers, or you can specifically contract for the modification in which case you can have certainty over timing and inclusion. In either case the universal condition is that ALL customisations are (at our sole discretion) included in the main code base that all clients receive as part of the upgrade cycle. This is to ensure that we only have one code base to manage and that nobody gets 'orphaned' because of their modifications.


"On demand" development of requested end-user reports is NOT part of the maintenance subscription, unless released as part of the Beta or Production software release cycles. Development of custom reports as a separate individual client release is a separately contracted service. In addition to those reports shipped as part of the main product, we also support the user-group open source efforts in report development and system customisation scripting however and we occasionally release additional report templates for public use through the forum.


Charges for maintenance support subscriptions vary depending on the installation, license and components used but are available at their current settings from the product order page.Read More..

<section begin=BackLinks />


BackLinks

<section end=BackLinks />