Jump to content

All Activity

This stream auto-updates

  1. Yesterday
  2. Now how do I convince colour blind horses that the water is clean and safe to drink? 😛
  3. Sorry - the above was a more generic prompt for ALL brokers - particularly those who need to review their risk appetite - not aimed at you guys per-se Ditto for this - and to make sure everyone is aware they can't blame or claim from, their supplier for their own inadequate security analysis and prevention I feel your pain with the horses - but at least you found the water - that's half the battle
  4. Not mine and I have lead so many horses to the water but I can't get them to drink. Putting it out here in public view is a last straw / venting action.
  5. Last week
  6. Tbf - I’d be interested in comparing how the competition / alternative OGI solution aka Virtual Cabinet, manages the same situation. That’s the real benchmark / leverage. If cyber is a concern - or a requirement of your BI - I’d suggest taking a serious look at those security functions in both. Then make your choice. #whosheadisontheblock
  7. Sounds like the usual "Let's wait until it happens and then we will do something about it" kind of approach That approach went well with the NHS too ...
  8. Had a fun chat with OGI about Open Attach and Ransomware ... Currently, OA uses SYSTEM to modify and create folders and files. However, it uses the User's permissions to read and open files. This means that I can help prevent ransomware from encrypting the data but not prevent it from exfiltrating the client documents. They decided that getting someone to finish the other half of the job was a bespoke contract. Told them we can wait, far more likely another broker is affected and kicks up a storm that affects OGI rather than us.
  9. It was initially fired across our bow as a full replacement, something that would address all the shortcomings of Tripos + Java and Open-I would be phased out in a few years. Those few years have already come and gone of course.
  10. LOL 😆 - I've heard their software called somethings, but never this! Anybody who is an entrenched OGI User would find Mobius falling short in lots of areas methinks and tbf - it's not meant as a replacement. I was told once, the answer to the question "what are the differences / what are the gaps?" was met with "It's irrelevant - they are different". Not sure that approach would ever win over any existing Core user
  11. We have a full OGI buffet, including ICP, ODP, binders and so forth. Mobius simply doesn't offer enough to be remotely enticing right now.
  12. Ooo - was this Mobius Rating Engine or just the cloud version of Core Admin Platform?
  13. https://www.theguardian.com/technology/2021/jun/14/ransomware-is-biggest-online-threat-to-people-in-uk-spy-agency-chief-to-warn I recommending reading the full article but what might be on the horizon:
  14. We recently revisted migrating to Mobius. There is no local server hosting. It is limited to consumer only. We frequently get news flashes that there are problems with the current Open-I Cloud solutions. Performance is worse with Exchange 365 than locally hosted Exchange 2013 (that we previously had). Integrated products, Open Attach working with Outlook and thefore MS mainframes has been frustrating and cost us a lot in productivity. We might revisit this in two years time. I doubt I will be recommending it as the way forward at that time.
  15. Earlier
  16. There will be issues whichever way - so you need to pick the right way for you at get it right first time. In short - and from experience on both sides - I'd say transfer now to your server, as separate branches. This may involve some logistics for connectivity (I don't know your set-up) but on the face of it - is better than running multiple servers and multiple business processes. You'll thank yourself in the long run Moving / migrating / transferring / consolidating to one branch - on the same server - is far, far easier to manage once the data is on one platform. Trust me on this.
  17. We were thinking to merge on our system but can well foresee a few issues 🙂
  18. not to any great extent so this shouldn't be a problem but thanks again
  19. Sorry Sandra - Are you planning to merge the branches on THEIR system - or merge and migrate to your server? The first is as everyone has said above - the latter is potentially a whole new world of complexity - x 10!
  20. Just thought, do you/they use Open Attach?
  21. Thank you Karl - I thought this was the case and good idea to stamp the notes!
  22. I’ve done this many years ago. If you merge branches into one, bear in mind client/policy references which are already taken on the target branch will get a new number. Therefore, if you have direct debit with a finance provider such as Premium Credit, you may have to provide them with a cross reference list. We also got OGI to stamp the BPY notes with the original ref.
  23. Thanks for your reply John - Yes it is OGI to OGI (broker acquisition and they have 2 separate branches whereas we have only one) and we are aware of the complexities in respect of the settings etc - may well be better to keep the two extra branches separate then drip feed onto one branch at renewal maybe? We realise policy modules etc will differ and just wondered if anyone had migrated, what actually happens if two clients have the same reference number? Will certainly keep you updated
  24. Hi Sandra Big question - and lots to consider. You haven't said, but I presume this is to do with an OGI to OGI transfer, with branches already on the same server? If so - and to help kick this off, top 5 tips below from me: Specification - Make sure you have a spec of what will - and what wont - be transferred Settings - Check that all your settings are the same. Many are branch independent and you really need to check all of these for future use. This includes source codes, exec codes, Database Reports, User Access authorities, Broker Record / Prospect record settings, Regulation Module options, Document / letter templates to name a few from a long long list Prospects - Do you use APM / Prospects - and what will happen with these records Accounts and EDI - If it's OGI>OGI then EDI should be OK, but you do need to have a plan for the accounts. For both, will the old branches be in run-off or transferred en-bloc / big-bang? If Run-off - how are you maintaining both sets of data? Why? - Revisit why are you doing this anyway - quite often it's not the only solution - and I'd be interested more in what you are trying to achieve and why you think branch consolidation is the answer I'm sure Open GI will have already asked all the above questions - and more - to get to the right solution for your business. But always worth taking advice on a big change Hopefully others will have input as well Good luck and let us know how you get on!
  25. Has anyone here had a data migration done by OGI where 2/3 branches have merged and have any tips, comments or advice of what to expect? Thanks Sandra
  26. Hour and a half for us. Microsoft's Hyper-V doesn't leverage host CPUs very well at all.
  1. Load more activity
  • Create New...