Our company currently makes use of Sharepoint Foundation 2010 as a basic portal that contains our quality management manuals, induction and other general documents as well as the usual Announcements, contact lists, etc
I have recently been tasked with upgrading and expanding the system.
In the last few weeks I have been playing around with SP 2010 and 2013, both Foundation and Standard and feel SP 2013 Std would be suited for our needs.
Here's what I intend on implementing:
Windows Server 2012
SP 2013 Std Edition:
Single Web Application
3 different Site Collections, reason for this is that want to split the "general" use (announcements, contacts, general doc) from the rest of the deployment:
Site 1 - This would be the landing page for the companies Intranet, would contain, contact lists, announcements, general docs, In/Out Register and some generally used links to external sites. This site would use the 2013 experience Collaboration Team Site
Site 2 - This site would contain the companies Quality Management manual along with our Induction manual and other training material (pictures and videos). The Enterprise Business Intelligence Center template would be used here
Site 3 - Site 3 would contain important project data used by all staff, the data would range from general word documents to CAD drawings. Would use the Enterprise Document Center template for this.
Sites 2 and 3 would require some IRM, each site would require its own set of Site permissions and the sizes of each site would range from couple of MB to around 100GB.
I am aware of the limitations with SQL Express so SQL Standard would be purchased.
To my question.
Does my planned deployment make sense with creating 3 sites?
What kind of hardware deployment would be required to make the sites speedily available to around 60 users?