Do hedge fund investment strategies matter in hedge fund ...
Launching a Hedge Fund: Technology Considerations
-
Upload
eze-castle-integration -
Category
Entertainment & Humor
-
view
1.712 -
download
0
description
Transcript of Launching a Hedge Fund: Technology Considerations
Launching a Hedge Fund: Technology ConsiderationsSteve Schoener
Vice President of Client Technology
Agenda
Technology Considerations– Infrastructure– Telecommunications– Real Estate– Disaster Recovery & Business Continuity Planning– Compliance & Archiving
Technology Budget
Common Technology Mistakes
Key Takeaways
Investment firms can choose from on-premise solutions or public, hybrid or private cloud services.
Technology Infrastructure
The Cloud
On-Premise Installation
Private Cloud Services
Public Cloud
Hybrid Cloud
On-Premise vs. Hosted Infrastructures
Eze Private Cloud Services Traditional Installation
Delivery Fully Managed & Hosted On-Premise
Turnaround < 3 weeks 4 – 6 weeks
PricingSubscription
(All Inclusive)Perpetual OS/Application Licensing +
Maintenance
Cost Allocation
Expensed (Over Time)
Capitalized (Upfront)
Additional Costs
Additional Users & Resources Desktop Support
CustomizationUpdates/Upgrades
MaintenanceOngoing Support
Platform Multi-Applications & OS
Updates Shorter – Invisible – Defined Larger – Frequent – Ubiquitous
Cloud Computing Considerations
Cost of Ownership
Control
Speed
Security
Availability
Scalability/Flexibility
Systems Integration
Additional Infrastructure Options
With an on-premise technology solution, your firm has two options:– Build and maintain your own Communications Room– Host your infrastructure in our data center(s)
Infrastructure security layers should include:
Firewall Client Site Router
ISP Edge Router
Desktop Server LAN
Telecommunications
Categories to Consider:– Internet service– Point-to-point– Phone & voicemail
• VoIP
– Market data services
Real Estate Options
Determine spacing needs
Explore options– Executive Suites– Hedge Fund Hotels– Sublease– Independent commercial
office space
Office Facilities
Disaster Recovery & Business Continuity Planning
Disaster Recovery ObjectivesRecovery Point Objective (RPO)– The point in time to
which you must recover data as defined by your organization
Recovery Time Objective (RTO)– The duration of time
within which a business process must be restored after a disaster
• Nightly Backups
RPO = 24 hrs
• Snapshots
RPO < 4 hrs
• Continuous Replication
RPO = 0
• Restore from Backups
RTO > 24 hrs
• Hot Standby
RTO < 4 hrs
• High Availability
RTO = 1 hr
Five Steps to Business Continuity Planning
Risk Assessmen
t
Business Impact
Analysis
Plan Creation
Plan & Implement
Plan Test & Maintain BCP
Life Cycle
Compliance & Archiving
Retain emails and IMs for prescribed amount of time by law
Store data in WORM format
Allow for searchable indexing of files
Technology BudgetEnterprise Infrastructure - Data + Networking Year 1 Year 2
Hardware and Software
Email, IM & Bloomberg Archival
Project Labor
Total Enterprise Infrastructure - Hardware
Enterprise Infrastructure - Voice Year 1 Year 2
Avaya Voice Hardware & Labor
Total Enterprise Infrastructure - Voice
Enterprise Infrastructure - 3rd Party Services Year 1 Year 2
Central Copier - Multifunctional Copier
Blackberry Voice & Data Service
Bloomberg Users
Verizon PRI Usage Including Taxes
Total Enterprise Infrastructure - Services
Enterprise Infrastructure - Circuits Year 1 Year 2
ISP A
ISP B
ISP 1 - PRI
ISP 2 - POTS
Bloomberg Circuit
Total Enterprise Infrastructure - Circuits
Additional Services Year 1 Year 2
Disaster Recovery
Monthly Service
Total Enterprise Infrastructure - Misc.
TOTAL EXPENDITURE
Common Technology Mistakes
Looking for the perfect solution
Insufficient planning for the future
Underestimating technology dependencies
Overestimating your capacity to manage technology
Shortchanging the training options and resources
…. and how to Avoid them
Key TakeawaysUptime is top priority – downtime is not acceptable.– Understand the risks your firm faces.
Plan for growth.
Identify your firm’s primary (critical) and secondary apps and business processes.– Knowledge = cost-effective and optimized technology
Remember one size does not fit all.– Understand your options and make sure your technology
provider is prepared to scale with you.
Thank You
Resources:
• Hedge IT Blog www.eci.com/blog
• Knowledge Centers www.eci.com/knowledge-center
• SlideShare Presentations http://www.slideshare.net/EzeCastle
Contact Info:Steve Schoener
Vice President, Client TechnologyEze Castle Integration