0% found this document useful (0 votes)
24 views25 pages

Installation Guide

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
24 views25 pages

Installation Guide

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 25

Table of Contents

1. System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Client / Standalone Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
ShipConstructor Client Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Client/Standalone Recommended Hardware Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Server / Standalone Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Server Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Microsoft SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Server Hosting Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Server Recommended Hardware Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2. How To Install ShipConstructor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Installation Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Network Installation - Single Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Network Installation - Multiple Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Standalone Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Installing ShipConstructor ............................................... 13
Installing and Configuring Microsoft SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Configuring Microsoft SQL Server 2008, SQL Server 2008 R2, or SQL Server 2012 . . . . . . . . . . . . . . . . . . . 14
Configuring Windows Firewall ............................................................. 15
Install ShipConstructor Client, Server, or Standalone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Connecting to your first project ........................................... 19
3. Modify or Remove ShipConstructor . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Modify ShipConstructor Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Remove SSI Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Removing ShipConstructor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
4. Updating ShipConstructor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Downloading the Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Applying the Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Update a Project Database Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
5. Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
SSI SOFTWARE LICENSE AGREEMENT

THIS LICENSE AGREEMENT GOVERNS THE PROVISION AND USE OF ALL SOFTWARE AND ANY RELATED MATERIALS, INCLUDING
DOCUMENTATION, UPDATES, UPGRADES, REVISIONS, FIXES AND MODIFICATIONS (THE “LICENSED MATERIALS”), LICENSED BY
YOU (“YOU” or “LICENSEE”) FROM SHIPCONSTRUCTOR SOFTWARE INC. dba “SSI”, A BRITISH COLUMBIA CORPORATION HAVING ITS
OFFICES AT #304-3960 QUADRA STREET, VICTORIA, BC, CANADA V8X 4A3 (“SSI”).

PLEASE READ THIS AGREEMENT CAREFULLY. BY CLICKING THE BOX BELOW INDICATING YOUR ACCEPTANCE, YOU
ACKNOWLEDGE THAT YOU HAVE READ, UNDERSTOOD, AND AGREE TO BE BOUND BY THE TERMS AND CONDITIONS OF THIS
AGREEMENT. ANY QUESTIONS REGARDING THIS AGREEMENT MAY BE DIRECTED TO SSI AT: INFO@SSI-CORPORATE.COM

IF YOU ARE ENTERING INTO THIS AGREEMENT ON BEHALF OF A COMPANY OR OTHER LEGAL ENTITY, YOU HEREBY REPRESENT
THAT YOU HAVE THE AUTHORITY TO BIND SUCH ENTITY TO THE TERMS AND CONDITIONS OF THIS AGREEMENT, AND “LICENSEE”
SHALL MEAN SUCH ENTITY. IF YOU DO NOT HAVE SUCH AUTHORITY, OR YOU OR SUCH ENTITY DO NOT AGREE TO THE TERMS
AND CONDITIONS SET OUT IN THIS AGREEMENT, YOU MUST NOT ACCEPT THIS AGREEMENT AND NEITHER YOU NOR SUCH ENTITY
MAY USE THE LICENSED MATERIALS.

TRIAL, R&D, OR ACADEMIC LICENSES: IF YOU REGISTER FOR A FREE TRIAL, R&D OR FOR AN ACADEMIC LICENSE FOR THE
LICENSED MATERIALS, THIS AGREEMENT WILL ALSO GOVERN THOSE LICENSES, PROVIDED THAT: (I) ANY TERMS REFERENCING
WARRANTIES SHALL NOT APPLY TO SUCH LICENSES, AND IN ALL CASES THE LICENSED MATERIALS ARE PROVIDED ON AN “AS IS”
BASIS; (II) YOUR RIGHT TO USE THE LICENSED MATERIALS SHALL BE LIMITED TO THE TRIAL PERIOD OR THE TERM OF THE
ACADEMIC LICENSE; (III) LICENSED MATERIALS LICENSED PURSUANT TO A TRIAL OR R&D LICENSE MAY BE USED FOR INTERNAL
TESTING AND EVALUATION PURPOSES ONLY UNLESS OTHERWISE EXPRESSLY AGREED BY SSI; (IV) LICENSED MATERIALS
LICENSED PURSUANT TO AN ACADEMIC LICENSE MAY BE USED ONLY FOR THE PURPOSE OF TEACHING, TRAINING USERS OR
UNDERTAKING RESEARCH; (V) LICENSED MATERIALS LICENSED PURSUANT TO A TRIAL, R&D OR ACADEMIC LICENSE MAY BE
USED ONLY AT THE PREMISES SPECIFIED IN THE ORDER CONFIRMATION; (VI) USE DURING ANY SUCH LICENSE PERIOD IS AT
YOUR OWN RISK, AND SSI DISCLAIMS ANY LIABILITY IN RESPECT THEREOF; AND (VII) LICENSED PRODUCTS WHICH ARE SUBJECT
TO A TRIAL, R&D, OR ACADEMIC LICENSE MAY NOT BE USED FOR ANY COMMERCIAL OR OTHER REVENUE-GENERATING
PURPOSES WITHOUT SSI’S EXPRESS PRIOR CONSENT.

1. License Grant. SSI grants to Licensee a limited, non-exclusive, non-transferable right and license to download and use the Licensed
Materials specified in Licensee’s accepted purchase order or request, during the Term specified in Section 6, solely for Licensee’s
internal purposes.

2. Restrictions on Use. Licensee agrees to use its best efforts to protect the Licensed Materials from unauthorized use, reproduction,
distribution or publication, and to use the Licensed Materials only in accordance with the terms of this Agreement and any applicable user
documentation provided by SSI. Without limiting the generality of the foregoing, Licensee may not, and may not permit any third party,
to (i) modify or create derivative works of the Licensed Materials; (ii) copy the Licensed Materials except as necessary for Licensee’s
installation and use of the Licensed Materials as specifically permitted under this Agreement; (iii) permit the simultaneous use of any
licensed software by more than one user; (iv) use the Licensed Materials in conjunction with any hardware, software or system not
approved by SSI; (v) except as specifically permitted by applicable law, reverse engineer, decompile, disassemble or otherwise attempt
to derive the source code for any licensed software; (vi) distribute, encumber, sell, rent, lease or sublicense the Licensed Materials, or
use the Licensed Materials in a timesharing or service bureau arrangement, or otherwise transfer any rights in or to the Licensed
Materials; (vii) remove, alter, obscure, destroy or attempt to circumvent any notices, proprietary codes, security mechanisms, means of
identification, digital rights management information, copyright or other proprietary rights marks or legends, including any reference to
SSI’s name or trademarks, contained in or on the Licensed Materials; (viii) permit or assist any other person to use the Licensed
Materials in a way that would constitute a breach of this Agreement; or (ix) take any actions that would cause any licensed software to
become subject to any open source or quasi open-source license terms.

3. Ownership and Intellectual Property Rights.

a. The Licensed Materials are licensed and not sold. SSI retains title to and exclusive ownership of any and all copies of the
Licensed Materials. Licensee acknowledges and agrees that the Licensed Materials constitute valuable intellectual property of
SSI and its third party suppliers, and are protected by Canadian, United States, European and other international laws, including
without limitation copyright and trademark laws and international treaty provisions. All proprietary rights in all intellectual and
industrial property contained in the Licensed Materials, including any corrections, improvements, upgrades, updates, bug fixes
and modifications to, and derivative works of, such intellectual and industrial property, shall be and remain the exclusive property
of SSI, and Licensee shall have no rights or interests therein except for the limited right to use as set forth in this Agreement.
Licensee covenants not to permit the use of the Licensed Materials by unauthorized persons, and to use its best efforts to
prevent the exportation of the Licensed Materials, or any portion thereof, into any country which does not have adequate
copyright and other intellectual property laws to protect SSI's rights in the Licensed Materials. Licensee shall reproduce any
proprietary rights notices on any full or partial copies of the Licensed Materials.

b. Licensee recognizes and acknowledges the great value of the goodwill associated with SSI’s name and trademarks, and the
identification of SSI’s goods or services therewith. Licensee agrees that it obtains no rights, title or interest of any kind in or to
any trademarks, tradenames, logos, service marks or other markings belonging to SSI.

c. As between the parties, Licensee will remain the owner of any Licensee data that it inputs into the Licensed Materials or which it
generates through the use of the Licensed Materials. Licensee shall be solely responsible for the accuracy, quality, security,
integrity and legality of its data, and the means by which it acquires its data (including, but not limited to, compliance with all
applicable privacy, security and export legislation).

d.

3
c.

d. SSI is granted an unlimited, perpetual, irrevocable, royalty-free, worldwide right and license to use and sublicense any ideas,
suggestions, recommendations, comments, enhancements, improvements and other feedback (“Submissions”) provided by
Licensee, including its personnel, with respect to the Licensed Materials or any other propriety information provided by SSI to
Licensee. All Submissions shall be given voluntarily and without expectation of, or requirement for, compensation. Specifically,
Licensee covenants that it will not provide any Submissions that are subject to license or other restrictions, or that may require
any SSI product, technology, service or documentation to be licensed or otherwise shared with any third party.

4. Licensee Responsibility. The Licensed Materials are intended for use in the modeling and construction of ships and offshore structures,
and must only be used by persons having the requisite expertise and knowledge in that field. Licensee acknowledges that it has had the
opportunity to evaluate the Licensed Materials for a designated trial period at no charge. Licensee agrees that it is solely responsible and
liable for: (i) the selection of the Licensed Materials to achieve Licensee’s intended results, and for all data, designs and other output
generated through its use; (ii) obtaining, provisioning, configuring, maintaining, and paying for all equipment, software and services
necessary for the installation and use of the Licensed Materials, including compliance with any system configuration requirements
specified in the SSI user documentation (“System Configuration”); (iii) all data used in association with the Licensed Materials, including
the implementation of adequate backup procedures to avoid any loss of files and data; (iv) providing a safe and suitable location for the
installation and use of the Licensed Materials; and (v) scanning for and preventing the receipt and transmission of viruses and other
destructive or disruptive components. Licensee acknowledges and agrees that the Licensed Materials require independent confirmation
of the reliability and accuracy of all designs, drawings and other Licensed Materials output. At Licensee’s request, an SSI representative
may be made available under a separate consulting agreement to provide training and consultation on the operation and/or integration of
the Licensed Materials. Licensee shall be solely responsible for, and shall hold SSI, its officers, directors and employees harmless from
and against all loss, damage and liability arising in connection with any use or misuse of the Licensed Materials, and from any claims
arising from or in relation to any designs or other output generated through Licensee’s use of the Licensed Materials, including a claim
that any such materials infringe or misappropriate the intellectual property rights of any third party.

5. Security. Licensee acknowledges that the Licensed Materials may include security elements which support the detection of unauthorized
use or copying of the licensed software and which may report such unauthorized use or copying to SSI and, if applicable based on
Licensee’s configuration, may report back specific user information such as the user’s name and email address.

6. Term of License. The license granted hereunder shall become effective upon Licensee agreeing to be bound by the terms of this
Agreement (“Effective Date”). Thereafter, unless earlier terminated in accordance with Section 14, the license shall continue in effect: (i)
until the expiry of the specified license term (in the case of monthly software rentals or leases, and trial or academic licenses), or (ii) if no
term is specified, indefinitely, provided that Licensee is not in breach of this Agreement. If Licensee chooses to change from a software
lease to an indefinite term license, 60% of the Licensee’s prior monthly lease payments received by SSI may, at Licensee’s option, be
applied towards the purchase of the indefinite term license.

7. Fees and Payment. Licensee shall pay to SSI all applicable license and other fees for the Licensed Materials as set out in SSI’s invoices.
Fees are exclusive of all taxes, duties and levies of any kind, including any sales, use, excise, value-added and other applicable taxes,
withholdings, and governmental charges (collectively, “Taxes”). Licensee shall be solely responsible for the payment of all applicable
Taxes, other than taxes on SSI’s income. If SSI pays any such amounts on behalf of Licensee, Licensee shall reimburse SSI upon
presentation of proof of payment. If Licensee is required by law to withhold any amounts for Taxes or otherwise, Licensee agrees to pay
SSI an amount equal to the gross amount that would have been received by SSI had such Taxes and other amounts not been required to
be deducted and withheld. Licensee shall pay interest on any invoiced amounts which are unpaid after 30 days at a rate of 2% per month
(24% per annum, effective rate) or the maximum amount allowed by law, whichever is less, from the date such amounts become due
and payable. Licensee also agrees to pay all costs incurred by SSI to collect any overdue amounts.

8. Limited Warranty.

a. SSI warrants that during a period of 90 days from the Effective Date (the “ Warranty Period”), the Licensed Materials will perform
substantially in accordance with the specifications set out in the applicable user documentation, when used in accordance with
this Agreement on a properly operating System Configuration. SSI’s sole obligation under this warranty, and Licensee’s
exclusive remedy, shall be SSI’s reasonable commercial efforts to correct any breach of the above warranty through fixes or
workarounds. If SSI determines that it is unable to make the Licensed Materials perform substantially as warranted, Licensee
may terminate this Agreement and receive a refund of a prorated portion of any prepaid license fee, rental or lease amounts.

b. This limited warranty will be void, and SSI shall have no liability, to the extent that any failure of the Licensed Materials to
conform to the specifications results from accident, abuse, alteration, misuse, unauthorized use or misapplication of the Licensed
Materials (or any of them), or from Licensee’s failure to use any updates, upgrades or fixes provided by SSI. SSI provides no
warranties with respect to any third party software embedded in or provided as part of the Licensed Materials.

9. ENTIRE WARRANTY. THE LIMITED WARRANTY CONTAINED IN SECTION 8 IS IN LIEU OF ALL OTHER WARRANTIES AND
REPRESENTATIONS OF ANY KIND. WITHOUT LIMITING THE GENERALITY OF THE FOREGOING, SSI AND ITS THIRD PARTY
SUPPLIERS DISCLAIM ALL OTHER REPRESENTATIONS, WARRANTIES AND CONDITIONS, EXPRESS OR IMPLIED, WHETHER
ARISING UNDER STATUTE, FROM A COURSE OF DEALING, USAGE, CUSTOM OF THE TRADE OR OTHERWISE, REGARDING
THE LICENSED MATERIALS AND ANY OTHER PRODUCTS OR SERVICES PROVIDED OR FAILED TO BE PROVIDED UNDER
THIS AGREEMENT, INCLUDING, BUT NOT LIMITED TO, ANY IMPLIED WARRANTY OR CONDITION OF MERCHANTABLE
QUALITY, MERCHANTABILITY, DURABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, ACCESSIBILITY,
OR THAT THE OPERATION OF ANY LICENSED SOFTWARE WILL BE ERROR FREE, CONTINUOUS OR UNINTERRUPTED.

10. Services. Fees for EnterprisePlatform software include standard maintenance, support and upgrade services. Licensees of
ShipConstructor® software may purchase annual maintenance, support and upgrade services from SSI in accordance with and subject to
the terms of SSI’s standard Subscription Agreement. SSI may, but shall not be obliged to, provide support for any non-current versions of
the Licensed Materials. All other services, including installation, consulting, training and implementation services, may be provided by

4
10.

separate agreement between Licensee and SSI at SSI’s then-current time and materials rates therefor.

11. Modifications. SSI may, from time to time, provide Licensee with revisions to the Licensed Materials (the “Revised Licensed Materials”)
. Licensee shall test any external applications using the revised API before implementing a new version. While it is SSI’s intention that
any Revised Licensed Materials will be compatible with the immediately preceding version of the Licensed Materials, SSI does not
guarantee or warrant backwards compatibility, and SSI shall not be liable to Licensee or to any other party for any failure of the Revised
Licensed Materials to be compatible with any prior version or release of the Licensed Materials. SSI may, but shall not be obliged to
make any modifications to the Licensed Materials requested by Licensee, and any such modifications agreed by SSI shall be subject to
the agreement of the parties as to scope and cost. Ownership of all Revised Licensed Materials and any Licensed Materials
modifications shall vest in SSI, and their use shall be subject to the terms and conditions of this Agreement.

12. Confidential Information. A party may use the other party’s confidential information only for the purpose of exercising its rights and
performing its obligations under this Agreement. A receiving party shall not disclose the other party’s confidential information to any other
person except to its employees, contractors and advisors having a “need-to-know”, but only after they have been advised of its
confidential and proprietary nature and have agreed to protect same on terms no less onerous than the terms of this Agreement. This
Section 12 shall not apply to confidential information which: (i) is or has become readily available to the public in the same form other
than by an act or omission of the receiving party; (ii) was lawfully obtained in the same form by the receiving party from a third party not
under an obligation of confidence to the disclosing party; (iii) was in the receiving party’s possession in the same and material form prior
to its receipt from the disclosing party and did not otherwise originate from the disclosing party; or (iv) is required to be disclosed by
operation of law.

13. Audit Rights. SSI shall have the right, upon not less than ten (10) days prior written notice, to inspect Licensee’s facilities to verify
Licensee’s compliance with this Agreement. Any such inspection or audit shall be conducted either by SSI or by representatives
authorized by SSI to complete the inspection. If such inspections or audits disclose that Licensee has installed, accessed or permitted
access to the Licensed Materials in a manner that is not permitted under this Agreement, then Licensee shall be liable to pay for any
unpaid license fees as well as the reasonable costs of the audit. All information disclosed and the results of the audit shall be “confidential
information” for the purposes of Section 12.

14. Termination. Licensee may terminate this Agreement at any time upon written notice to SSI. Time limited licenses shall expire upon the
expiry of the applicable license, lease or rental period, unless expressly extended by SSI. Either party may terminate this Agreement
immediately upon written notice if: (i) the other party makes an assignment for the benefit of its creditors or becomes bankrupt or makes
an application for relief under the provisions of any statute now or hereafter in force concerning bankrupt or insolvent debtors, or (ii) if a
receiving order or receivership order is made against the other party, or (iii) any action whatsoever, legislative or otherwise is taken to
effect the winding up, dissolution, suspension of operations or liquidation of the other party. This Agreement may also be terminated by
SSI upon thirty (30) days written notice to Licensee if Licensee commits a breach of any material provision of this Agreement, including a
failure to make payment when due, and fails to correct or rectify such breach prior to the expiry of the notice period. Termination shall be
in addition to, and not in lieu of, any other rights or remedies that SSI may have at law or in equity. Further, Licensee agrees that SSI may
include time-lock devices and other disabling features in the Licensed Materials that will become effective in the event that Licensee fails
to comply with any of its material obligations hereunder.

15. Effect of Expiry or Termination. Upon the expiry or termination of this Agreement for any reason, Licensee shall immediately cease using
the Licensed Materials, and remove or destroy all full and partial copies in Licensee’s and its personnel’s possession or under their
control, including on any computers and systems. All unpaid amounts due in respect of the Licensed Materials up to and including the
effective date of the expiry or termination shall, at SSI’s option, become immediately due and payable. The provisions of Sections 2, 3, 4,
7, 8, 9, 12, 13, 15, 16, 17, 18, 19, 20, 24 and 30 shall survive the expiry or termination of this Agreement for any reason. Any termination
shall be without prejudice to the accrued rights and liabilities of either party arising prior to the effective date of expiry or termination.

16. Limitation of Liability; Exclusion of Damages.

a. TO THE MAXIMUM EXTENT PERMITTED BY LAW, SSI’S AND ITS RESPRESENTATIVES’ TOTAL COLLECTIVE LIABILITY
ARISING UNDER OR IN CONNECTION WITH THIS AGREEMENT, AND/OR ANY PRODUCTS OR SERVICES DELIVERED
OR FAILED TO BE DELIVERED UNDER THIS AGREEMENT, SHALL BE LIMITED TO THE ACTUAL DIRECT DAMAGES
SUFFERED BY LICENSEE, NOT TO EXCEED THE AMOUNT ACTUALLY PAID BY LICENSEE FOR THE PRODUCT OR
SERVICE GIVING RISE TO THE CLAIM. IN NO EVENT WILL SSI BE LIABLE FOR ANY INDIRECT, SPECIAL,
CONSEQUENTIAL, INCIDENTAL, PUNITIVE, EXEMPLARY OR AGGRAVATED DAMAGES OF ANY KIND WHATSOEVER
INCLUDING, BUT NOT LIMITED TO, DAMAGES FOR LOSS OF USE OF SYSTEMS OR EQUIPMENT, DATA, INCOME,
BUSINESS, PROFIT, GOODWILL, ANTICIPATED REVENUE, FAILURE TO REALIZE EXPECTED SAVINGS, OR
OTHERWISE. THE FOREGOING LIMITATIONS SHALL APPLY REGARDLESS OF THE CAUSE OF ACTION, WHETHER
ARISING UNDER CONTRACT, TORT (INCLUDING NEGLIGENCE AND GROSS NEGLIGENCE), PRODUCT LIABILITY,
INDEMNIFICATION, FUNDAMENTAL BREACH OR OTHERWISE, AND REGARDLESS OF WHETHER SSI OR ITS
PERSONNEL KNEW, OR SHOULD HAVE KNOWN ABOUT THE POSSIBILITY OF SUCH DAMAGES.

b. NO ACTION, REGARDLESS OF FORM, ARISING OUT OF THIS AGREEMENT MAY BE BROUGHT BY LICENSEE MORE
THAN TWELVE (12) MONTHS AFTER THE FACTS GIVING RISE TO THE CAUSE OF ACTION HAVE OCCURRED,
REGARDLESS OF WHETHER THOSE FACTS BY THAT TIME ARE KNOWN TO, OR OUGHT REASONABLY TO HAVE
BEEN DISCOVERED BY, LICENSEE.

c. LICENSEE AGREES THAT THE LIMITATIONS OF LIABILITY SET FORTH ABOVE ARE FUNDAMENTAL ELEMENTS OF
THIS AGREEMENT, WITHOUT WHICH SSI WOULD NOT HAVE ENTERED INTO THIS AGREEMENT AND/OR AGREED TO
PROVIDE THE LICENSED MATERIALS UNDER THE CURRENT TERMS (INCLUDING FEES).

d. BECAUSE THE LAWS OF SOME JURISDICTIONS DO NOT ALLOW THE LIMITATION AND/OR EXCLUSION OF LIABILITY,

5
d.
THE ABOVE LIMITATIONS AND EXCLUSIONS MAY NOT APPLY TO ALL LICENSEES. IN SUCH JURISDICTIONS, THE
PARTIES AGREE THAT SSI’S LIABILITY SHALL LIMITED TO THE FULLEST EXTENT PERMITTED BY LAW.

17. US Government Users. If Licensee is, or is acquiring the Licensed Materials on behalf of, a US government unit or agency, or a US
Government contractor (at any tier) the following provision applies: The government unit or agency acknowledges SSI's representation
that the Licensed Materials were developed at private expense, and are “Commercial Computer Software” and “Commercial Computer
Software Documentation” as defined in 48 FAR 12.212 or 48 CFR 227.7202, as applicable (or successor provisions). Consistent with 48
CFR 12.212 or 48 CFR 227.7202-1 through 227.7202-04, as applicable, the Commercial Computer Software and Commercial Computer
Software Documentation are being licensed to US Government end users: (i) only as Commercial Items, and (ii) only with “restricted
rights”, and any use shall be solely in accordance with the terms of this Agreement. The government unit or agency acknowledges that
all right, title, and interest including all proprietary and intellectual property rights in and to the Licensed Materials, and updated versions
(including but not limited to any images, photographs, animations, video, audio, music, text, and plug-in components incorporated into the
Licensed Materials) any accompanying printed materials and any copies of the Licensed Materials, reside in or are owned by SSI.
Unpublished rights are reserved under US and foreign copyright laws. The owner of the Licensed Materials is ShipConstructor Software
Inc. dba SSI, having its head offices at #304-3960 Quadra Street, Victoria, British Columbia, Canada V8X 4A3.

18. Applicable Law. This Agreement shall be subject to and construed in accordance with the laws of the Province of British Columbia and
the laws of Canada applicable therein, but excluding conflicts of laws rules. The application of the UN Convention on Contracts for the
International Sale of Goods is hereby expressly excluded.

19. Dispute. Except as provided in Section 20, if any dispute arises under this Agreement, a good faith attempt to resolve the dispute will be
made by senior management of both parties. If the parties are unable to reach an agreement within 30 days after a request for such
meeting, the dispute shall be referred to arbitration in English, before one arbitrator in Victoria, British Columbia, Canada, in accordance
with the Commercial Arbitration Act of the British Columbia.

20. Equitable Relief. Licensee acknowledges and agrees that any breach by it of any of the terms of this Agreement is likely to result in
serious and/or irreparable harm or damage to SSI for which monetary damages will not be an adequate remedy. Accordingly, in the
event of a breach or threatened breach by Licensee, in addition to any and all remedies available at law, and notwithstanding any other
provision of this Agreement, SSI shall have the right to obtain an injunction, specific performance or other equitable relief in any court
having competent jurisdiction.

21. References. SSI shall be allowed to incorporate Licensee’s name in SSI’s customer reference list and to use it for marketing.

22. Amendment. Any amendment of this Agreement must be in writing and signed by duly authorized representatives of both parties.

23. Waiver. Any consent by a party to, or waiver of, a breach by the other party, whether express or implied, shall not constitute a consent
to or waiver of any other, different or subsequent breach.

24. Export Control. The Licensed Materials and other technology made available by SSI, including any modifications or derivatives thereof,
may be subject to the export control laws of Canada, the United States and other jurisdictions. Licensee warrants that it and its affiliates
are not named on any Canadian or United States government restricted party list, and agrees that it will not import, export, use, access or
permit the import, export, use or access of the Licensed Materials, or any of them, in violation of any applicable Canadian, United States
or other applicable laws and regulations.

25. Assignments. Licensee may not assign or transfer this Agreement or any of Licensee’s rights or obligations under this Agreement without
SSI’s prior written consent, and any such assignment or transfer without consent shall be null and void. A transfer of all or substantially all
of the voting stock of Licensee shall constitute a transfer for these purposes and shall be subject to SSI’s prior written consent. This
Agreement will bind and enure to the benefit of the parties and their respective successors and permitted assigns.

26. Independent Contractors. The parties are independent contractors. Nothing in this Agreement shall be construed to create any
employment, agency, partnership, joint venture or other relationship between the parties.

27. Severability. If any provision contained in this Agreement is found by a court of competent jurisdiction to be invalid, illegal or
unenforceable in any respect, it shall be deemed severed from this Agreement and the remaining provisions of this Agreement shall not
be in any way affected or impaired thereby and shall continue in full force and effect.

28. Third Party Content – Acknowledgement and Terms. The Licensed Materials may use or include third party components, content and/or
other copyrighted or publicly licensed material. Acknowledgments, licensing terms and additional disclaimers for such components,
content, and/or materials are contained in the respective components documentation, and Licensee’s use of such third party components,
content or material is governed by their respective terms and conditions.

29. Force Majeure. Except as related to Licensee’s obligation to make payments to SSI, neither party shall be liable for delays or
non-performance if such delays or non-performance are beyond such party's reasonable control. A delayed party shall promptly notify
the other party in writing stating the cause of the delay and its expected duration and shall use commercially reasonable efforts to remedy
a delay or non-performance as soon as reasonably possible.

30. Non-Solicitation. For a period of one (1) year from the Effective Date, Licensee will not, directly or indirectly, employ or solicit for
employment any employee or contractor of SSI without SSI’s prior written consent. If Licensee violates this provision, it agrees to pay
compensation to SSI in an amount equal to the employee or contractor’s gross wages over a twelve (12) month period. Licensee agrees
that such compensation is a fair estimate of the economic loss that would be suffered by SSI as a result of a breach of this provision, and
that this provision is reasonable given: (i) the highly specialized skills of SSI’s employees and contractors, and the considerable cost that
SSI has incurred in recruiting and training them; and/or (ii) the unique nature of SSI’s technology and the highly competitive market in

6
which it operates.

31. Notices. All communications and notices provided for herein shall be in writing and shall be delivered to the recipient by email, or by
registered or certified mail with return receipt requested, postage prepaid, and addressed: (i) to SSI at the address set out at the head of
this Agreement, and (ii) to Licensee at the address appearing on the order form(s) for the Licensed Materials, or at such other address as
either party may designate by notice to the other. Notices shall be deemed to have been delivered when physically received; provided,
however, that notices received after 6:00 pm local time, or on a Saturday, Sunday or public holiday in the place of receipt, shall be
deemed to have been received at 9:00 am on the next business day.

32. Entire Agreement. This Agreement contains the entire agreement between the parties and shall supersede all prior discussions and
agreements between the parties regarding its subject matter. Any additional or conflicting terms and conditions contained in a Licensee
purchase order shall be deemed to be expressly superseded and of no force or effect.

33. Language. It is the express will of the parties that this Agreement and related documents be prepared in English. C’est la volonté
expresse des parties que la présente Convention ainsi que les documents qui s’y rattachent soient rédiges en anglais.

7
1. SYSTEM REQUIREMENTS
A ShipConstructor implementation consists of the following software components:

ShipConstructor client software


ShipConstructor server tools – Tools for providing licensing and administering project databases on Microsoft SQL Server.
Microsoft SQL Server – One network accessible instance is required to host ShipConstructor project databases.

It is recommended that the server hosting the ShipConstructor project database be hosted on a separate machine from the ShipConstructor
client. Standalone installations are only recommended for a single-user environment.

Important
A software license is required to run ShipConstructor products. Without a license all products will run with limited functionality.

Client / Standalone Installations


ShipConstructor Client Software Requirements
Windows
ShipConstructor 2016 client and standalone installations require either 64-bit Windows 7 SP1 or Windows 8.1

.NET Framework
Microsoft .NET Framework 4.5.1 will be installed automatically by the ShipConstructor installer, if it is not already installed.

AutoCAD
ShipConstructor 2016 is compatible with:

AutoCAD 2013 SP1.1


AutoCAD Mechanical 2013 SP1
AutoCAD Electrical 2013 SP1
AutoCAD P&ID 2013 SP1
AutoCAD Plant 3D 2013 SP1
AutoCAD 2014 SP1
AutoCAD Mechanical 2014 SP1
AutoCAD Electrical 2014 SP1
AutoCAD P&ID 2014 SP1
AutoCAD Plant 3D 2014 SP1
AutoCAD 2015 SP2
AutoCAD Mechanical 2015 SP2
AutoCAD Electrical 2015 SP2
AutoCAD P&ID 2015 SP2
AutoCAD Plant 3D 2015 SP2
AutoCAD 2016
AutoCAD Mechanical 2016
AutoCAD Electrical 2016
AutoCAD P&ID 2016
AutoCAD Plant 3D 2016

ShipConstructor server tools, ShipCAM and NC-Pyros are not dependent on AutoCAD.

Compatibility
ShipConstructor 2016 can be installed side-by-side with any previous major ShipConstructor version. ShipConstructor cannot be installed
side-by-side with the ShipConstructor Object Enabler: before installing ShipConstructor, the ShipConstructor Object Enabler must be uninstalled;
before installing the ShipConstructor Object Enabler, ShipConstructor must be uninstalled.

8
Client/Standalone Recommended Hardware Specifications
ShipConstructor – Heavy Modeling
Outlined here is a recommended client workstation for a ShipConstructor user involved in heavy modeling and output generation:

Processor Intel® 64-bit Core i7 Processor (4 Cores) (8M Cache) @ 2.8 GHz or
better

Memory 8-16 GB

Graphics Card Any AutoCAD supported and recommended graphics card with a
supported and recommended driver.

*For a list of AutoCAD supported and recommended graphics cards


please see www.autodesk.com/autocad-graphicscard

Disk Space Minimum of 5GB available

ShipConstructor – 2D Design
For users who are largely involved in minor 3D design, 2D schematic design, drawing annotation, BOM management and other operations which
are not as resource intensive on the client, a lesser machine similar to the following will suffice

Processor Intel® 64-bit Core i5 Processor (2 Cores) (4M Cache) @ 2.8 GHz or
better

Memory 4-8 GB

Graphics Card Any AutoCAD supported and recommended graphics card with a
supported and recommended driver.

*For a list of AutoCAD supported and recommended graphics cards


please see www.autodesk.com/autocad-graphicscard

Disk Space Minimum of 5GB available

Server / Standalone Installations


Server Software Requirements
Windows
ShipConstructor 2016 server installations should be installed on a 64 bit version of one of the following Operating Systems:

Windows Server 2008


Windows Server 2008 R2
Windows Server 2012

.NET Framework
Microsoft .NET Framework 4.5.1 will be installed automatically by the ShipConstructor installer, if it is not already installed.

Microsoft SQL Server


All ShipConstructor 2016 implementations require at least one instance of Microsoft SQL Server installed.

Attention
Microsoft SQL Server 2005 is no longer supported in ShipConstructor 2016. Any existing ShipConstructor projects hosted on Micro
soft SQL Server 2005 will need to be transferred to a supported SQL server. See the Transfer a Project to Another Server section
of the Project Management manual for further instructions.

A free licensed version of Microsoft SQL Server 2012 SP1 Express Edition is packaged with ShipConstructor 2016. However, for larger projects
(5 or more users) a full version of MS SQL Server 2008, SQL 2008 R2, SQL 2012, or SQL 2014 is recommended to overcome the limitations of
Microsoft SQL Server 2012 SP1 Express. A full version increases the amount of RAM and the number of CPUs that can be used, as well as the

9
maximum relational Database size. This is crucial for servers hosting many projects or projects of large size.

Attention
It is possible to restore a database created in an older version of SQL Server into a newer version of SQL Server. However it is not
possible to restore a database created in a newer version of SQL Server into an older version of SQL Server. For this reason, the
SQL Server version used by any partner offices or subcontractors should be considered when choosing the SQL Server version to
use.

Server Hosting Recommendations


There are three categories of items that must be served to support a ShipConstructor project:

Project Databases
Project Drawing Files
Software Licenses

In all but enterprise implementations it is recommended that all three components be hosted on the same server hardware to reduce setup and
administrative overhead. It is also recommended that all projects be kept on the same project server to make administration tasks easier.

Server Recommended Hardware Specifications


These specifications are recommended for satisfactory performance. Specifications better than those outlined below can offer better performance.
A gigabit network connection is recommended between each element in the ShipConstructor system. This includes all connections to the client
workstations.

1 - 5 Users

Processor Intel® 64-bit Core i7 Processor (2 physical Cores) (8M Cache) @ 3.0 GHz or better

Memory 8 GB

Disk Configuration Disk Array Data Purpose Minimum Storage Recommended Storage
Configuration Required Required

RAID 1 (2 Disks) Operating System 150 GB + (100 GB per 300 GB + (200 GB per
or SQL Server binaries, project) project)
RAID 5 (3 Disks) SQL Server
Database data files
(MDF)
SQL Server
database log files
(LDF)
ShipConstructor
Project Files
Navisworks
etc...

Disks should be high performance SATA or SAS disks (15k RPM)

10
5 - 10 Users

Processor Intel® 64-bit Core i7 Processor (4 physical Cores) (8M Cache) @ 3.0 GHz or better

Memory 12-16 GB

Disk Configuration Disk Array Data Purpose Minimum Storage Recommended Storage
Configuration Required Required

RAID 1 (2 Disks) Operating System 50 GB 100 GB


or SQL Server binaries
RAID 5 (3 Disks)

RAID 5 (3 Disks) SQL Server 100 GB + (100 GB per 300 GB + (300 GB per
or Database data files project) project)
RAID 10 (4 Disks) (MDF)
SQL Server
database log files
(LDF)
SQL Server tempdb
ShipConstructor
Project Files
Navisworks
etc...

Disks should be high performance SATA or SAS disks (15k RPM)

10 - 20 Users

Processor Intel® Xeon® Processor (8 physical Cores) (8M Cache) @ 3.0 GHz or better

Memory 16-32 GB

Disk Configuration Disk Array Data Purpose Minimum Storage Recommended Storage
Configuration Required Required

RAID 1 (2 Disks) Operating System 50 GB 300 GB


SQL Server binaries

RAID 10 (4 Disks) SQL Server 50 GB + (50 GB per 100 GB + (100 GB per


Database data files project) project)
(MDF)
SQL Server tempdb

RAID 5 (3 Disks) SQL Server 50 GB + (50 GB per 100 GB + (100 GB per


or database log files project) project)
RAID 10 (4 Disks) (LDF)

RAID 5 (3 Disks) ShipConstructor 100 GB per project 200 GB per project


or Project Files
RAID 10 (4 Disks) Navisworks
etc...

Disks should be high performance SATA or SAS disks (15k RPM)

> 20 Users
Please contact SSI for hardware recommendations

2. HOW TO INSTALL SHIPCONSTRUCTOR

11
Installation Types
ShipConstructor offers users multiple ways in which users can configure their installation. Although a Standalone installation method is offered, it
is recommended to either do a Single Server or Multiple Server installation to achieve best performance.

Network Installation - Single Server


A Single Server network installation follows basic client-server architecture.

One machine houses the Microsoft SQL Server, the ShipConstructor Server files, the project database, project files and the License Server.
Workstations then communicate with the server.

Installed on the Server:


ServerTools
ShipConstructor Administrator, for project maintenance
ShipConstructor Server Setup, for configuring Microsoft SQL Server
ShipConstructor License Server, for network licensing
License Utilities for License management
ShipConstructor Project Files

Installed on the Client(s):


ShipConstructor
Report
NC-Pyros
ShipCAM

Network Installation - Multiple Servers


To optimize performance note that it may be desirable to separate the SQL Server, the File Server and the Licensing Server onto two or three
different computers.

Installed on the Licensing Server:


ShipConstructor License Server, for network licensing
License Utilities for License management

Installed on the SQL Server:


ServerTools
ShipConstructor Administrator, for project maintenance
ShipConstructor Server Setup, for configuring Microsoft SQL Server

12
Installed on the Client(s):
ShipConstructor
Report
NC-Pyros
ShipCAM

Installed on the File Server


ShipConstructor Project Files

Standalone Installation
Standalone installations are typically used in a single-user environment. In this configuration, a single machine acts as both server and client. In
order to achieve satisfactory performance with a standalone installation, a multi-core CPU and 8GB of RAM is recommended.

Note, in a multi-user environment, a network installation should be used instead of a standalone installation since performance is improved if
server and client workload are distributed onto different computers. A network installation also allows more flexibility as changes to the server
such as location or network drive mappings will not affect the clients. Furthermore, a network installation allows the project server to be replaced
without any work needed on the client machines and can make it easier to work with multiple project servers.

Installing ShipConstructor
The basic process of installing ShipConstructor for a Network Installation involves the following steps:

1. Install and/or Configure SQL Server


2. Install ShipConstructor Server Files
3. Install ShipConstructor Client Files
4. Update SSI Licenses

Installing and Configuring Microsoft SQL Server

Attention
The following steps are only required if installing SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, or SQL Server 2014. If
you plan to use the pre-configured SQL Server 2012 Express Edition included with ShipConstructor skip to the Install
ShipConstructor Client, Standalone, or Server section.

13
After installing any of the supported versions of SQL Server as per Microsoft's instructions you will need to go through the following configuration
steps to make SQL work with ShipConstructor. These steps will:

Enable TCP/IP and Named Pipes Protocols


Turn on the SQL Server Browser Service
Enable Remote Connections
Configuring Microsoft SQL Server 2008, SQL Server 2008 R2, or SQL Server 2012

Enable TCP/IP and Named Pipes Protocols


1. Go to your Start menu and choose All Programs->Microsoft SQL Server 2008->Configuration Tools (or All Programs->Microsoft
SQL Server 2012->Configuration Tools ) and click on SQL Server Configuration Manager.

Note
You may be required to restart your server after making these changes. Please restart before installing the
ShipConstructor Server files to ensure that the settings are up to date.

2. Under SQL Server Configuration Manager (Local) expand SQL Server Network Configuration.
3. Select the Protocols for <Instance Name> node in the tree on the left.
4. Click on the Status for Named Pipes and change it to Enabled.

5. Click on the Status for TCP/IP and change it to Enabled.

Turn on the SQL Server Browser Service


1. Select the SQL Server Services node under SQL Server Configuration Manager (Local) from the tree on the left.
2. In the right side pane, right click on SQL Server Browser and choose Properties from the right click menu.
3. In the SQL Server Browser Properties window that appears, click on the Start button to start the service if it isn’t already started.

4.

14
4. Click OK to save the changes and close the SQL Server Browser Properties window.

Specify The Proper Service Account

Note
By default SQL Server installs itself configured to run as the NETWORK SERVICE account. This account does not have
permission to access necessary folders on the server, such as the backup folder. Instead the SQL Server should be changed to run
as an account with the necessary permissions. It is recommended that you create an unprivileged user account with access to the
Data, Log, Backup, TempDB and WorkShare folders you will be using for your server.

1. Select the SQL Server Services node under SQL Server Configuration Manager (Local) from the tree on the left.
2. In the right side pane, right click on the SQL Server and choose Properties from the right click menu.
3. On the Log On tab select This account: and enter the username and password for the desired account. Click OK to save the changes.
4. Click Restart to start the service under the proper account. Click OK and then close the SQL Server Configuration Manager.

Enable Remote Connections


1. Under Select a page click on Connections.
2. Under the Remote server connections section, ensure that Allow remote connections to this server is checked.
3. Click OK to save the changes and close the Server Properties window.

4. Close the SQL Server Configuration Manager window to complete the configuration of your SQL server. Your SQL Server is now ready
to be setup using ShipConstructor ServerSetup 2016 (see Step 5 of the Install ShipConstructor Client, Standalone, or Server section
of this guide). If you are unable to run ServerSetup, or to setup your SQL Server manually please contact our support team at support@s
si-corporate.com, or consult the relevant Knowledge Base article:
To Manually Setup SQL Server 2008 - http://kb.ssi-corporate.com/x/NgA6
To Manually Setup SQL Server 2012 - http://kb.ssi-corporate.com/x/TwBa

Note
You may be required to restart you server after making these changes. Please restart before installing the ShipConstructor
Server files to ensure that the settings are up to date.

Configuring Windows Firewall


If a firewall is turned on but not correctly configured, attempts to connect to SQL Server might be blocked. If this is the case, consult www.microso
ft.com for instructions regarding manually configuring Windows Firewall.

15
Install ShipConstructor Client, Server, or Standalone
1. After unpacking the self-extracting archive containing the ShipConstructor installer, run Setup.exe on the computer you would like to
install ShipConstructor on. If you are performing a Server or Standalone installation use the computer that will be hosting Microsoft SQL
Server. If a User Account Control prompt is displayed, click Yes.

2. The Installation menu will be displayed. To specify a custom installation directory, click Browse and select a folder.

3. Select one of the following configurations to be installed


a. To perform a ShipConstructor Client installation check ShipConstructor, NC-Pyros and ShipCAM.
b. To perform a ShipConstructor Server installation check ServerTools, SSI License Server, and optionally SQL Server Express
2012. If you followed the steps in the Installing and Configuring Microsoft SQL Server section of this guide you do not need
to install SQL Server Express 2012. (Note: the SQL Server Express 2012 option will be disabled if SQL Server 2012 has already
been installed).
c. To perform a ShipConstructor Standalone installation check ShipConstructor, NC-Pyros, ShipCAM, ServerTools, SSI License
Server, and SQL Server Express 2012.
d. To perform an EnterprisePlatform installation check either PublisherLT or PublisherLT CNC Profile Edition.
4. Click Next, then check I Accept on the ShipConstructor End-User License Agreement and click Install. Installation will begin.

16
5. If ServerTools 2016 was selected for installation ShipConstructor ServerSetup 2016 will launch, prompting you to configure your SQL
Server instance.

6. Under the SQL Server Connection section, choose your Server Instance from the dropdown list. If you checked SQL Server Express
2012 in Step 3 the SQL Server instance will be listed as SHIPCON_SQL12.

Note
If you do not see the desired instance in the drop-down list, ensure that the server is currently running and running on the
same machine. If it is not, start the service then click . If the server name still does not appear, type it in manually.

7. Ensure that the Use Integrated Security box is checked if you are running ShipConstructor ServerSetup as a machine administrator
(typical). Otherwise, enter a SQL server username and password for any user that has a sysadmin role.

17
Note
Microsoft SQL Server creates an account called “sa” by default during setup. In the bundled SQL Server 2012 Express
Edition the password is “ShipCon1”. For full versions of SQL you will need to use the password you supplied for the “sa”
user during setup.

8. Verify the details in the SQL Server Configuration Section. Match the Data, Log, Backup, and TempDB Paths to those used by your
SQL installation. If you checked SQL Server Express 2012 in step 3 the default paths will be correct.

Note
TempDB is a system database responsible for a high number of random IO operations, and will benefit from being on a
hard drive with low latency and improved throughput. It is highly recommended to move TempDB to a hard drive which will
handle the load, such as a Solid State Drive (SSD).

9. Changing the TempDB path requires that the SQL Server service be restarted for changes to take effect. In the event that the TempDB
path changes, ShipConstructor ServerSetup will prompt you to provide the ability to restart the SQL Server service as part of the setup
otherwise you can restart the service at a more convenient time.

Note
Once the SQL Server service has been restarted, the tempdb.mdf and templog.ldf files in the old location can be safely
deleted. To confirm which files are not in use, compare with the filename column in the result set of the following SQL
statement on every SQL Server instance for that machine:

USE tempdb GO sp_helpfile GO

10. If you intend to use ShipConstructor’s WorkShare functionality, or plan to Package and Deploy projects, check the Create
WorkShare share folder box.

Note
The WorkShare shared folder on the server is writable by everyone. If security is a concern you may limit the folder’s
security, however it must be shared with and writable by the following users:

a. The account your SQL Server is running as (typically the Local System account or an NT Service account)
b. Any domain user who will perform WorkShare operations or will be creating or Deploying project Packages

11. Leave the Disable SQL Authentication box unchecked.

Note
If SQL Authentication is disabled, your server is set to Windows Authentication Only mode and will be inaccessible via SQL
Authentication.

12. Under the ShipConstructor User section, enter and confirm the user password for the ShipConstructor user that will be created in the
database. Note this password down as it will be required to connect to any ShipConstructor project you create.

Note
If you do not specify a password when creating the ShipConstructor user the default password of “ShipCon” will be used
instead.

13. Click Setup to have ShipConstructor ServerSetup perform the following tasks.
a. Set the server’s Authentication Mode. By default it will verify that the selected instance of Microsoft SQL Server supports SQL
Authentication. If your Microsoft SQL Server is set to Windows Authentication Only, it will change the setting to Mixed Mode
which supports both Windows Authentication and SQL Authentication modes.
b. Connect to the server using the specified account.
c. Add the user ShipConstructor with the password ShipCon1 as a sysadmin account.
d. Enable the xp_cmdshell stored procedure.
e. Set the server’s default log, data, and backup folders.
f. Create the WorkShare shared folder (if checked). This folder is shared with and writable by ALL users by default.
14. Click OK to close the window and complete the ShipConstructor Server installation. You may have to restart your server before you can
run ShipConstructor 2016. Click Done to complete the installation.

18
Connecting to your first project
ShipConstructor requires a project to be stood up to use ShipConstructor. You may need to create a new project in ShipConstructor.

1. Go to the Start menu and choose All Programs >ShipConstructor 2016 and click on ShipConstructor 2016 to launch the program. If
you have multiple supported versions of AutoCAD installed you will see the AutoCAD Selection dialog. Select the desired AutoCAD
instance, check Remember my selection if you do not want to be prompted in future, and click Start ShipConstructor. To later change
your selected AutoCAD instance, go to your Start menu and choose All Programs >ShipConstructor 2016 and click on Configure
ShipConstructor 2016.

Note
AutoCAD Mechanical instances must be run in “Vanilla” mode. In this compatibility mode AutoCAD Mechanical will behave
like regular AutoCAD, with all Mechanical-specific commands and functionality disabled.

2. From the ribbon bar choose New Project. The New ShipConstructor Project dialog will open.

19
3. Click on the ... button next to the Project Folder text box then choose a folder to store your project in. This can be on your computer or
another computer on your network.
4. For the Project Server choose the machine on your network that has your SQL server installed. For Standalone installations choose
your computer. This will be listed in the format <Machine Name>\<Sever Name>
5. Under Template Project(s) put a checkmark in the Use the same template for all areas.
6. Under the .PRO or .XML Template File heading, click on the ... button beside Users, Settings & Ranks. Navigate to the ShipConstruc
tor 2016->ProjectTemplates folder and choose MetricTemplate or ImperialTemplate from the dialog box. Click Open.

7. After a few seconds you should see that all of the templates have been populated with the path and template file that you just chose

20
8. In the User Name text box in the Administrator Login section, enter ShipConstructor. Then, in the Password text box, enter the
password that you used for this user during installation.

Note
If you do not specify a password when creating the ShipConstructor user the default password of “ShipCon” will be used
instead.

9. Click OK to create the project. The project creation will take several minutes to complete.
10. Once the New Project Created dialog box pops up press OK to close it.
11. You will now need to connect to project that you just created. Click on the Navigator button in the ribbon to bring up the Register
Project window.
12. Click on the newly created project and enter ShipConstructor for the User Name. Then enter your password for the ShipConstructor
user. Click on Open to open the project. The Licensing window will automatically open. If you are using standalone licenses skip to
Step 16.

13. Click on the Server button to open the Server Configuration window.

21
13.

14. Enter the machine name or TCP/IP address of the server where your license server is set up.
15. Click OK to close the Server Configuration window and to retrieve the license information. You will return to the Licensing window.

16. If your licenses have been successfully retrieved you will see all of the available products as well as their status. Click the checkbox next
to each license you require.
17. Click OK to close the Licensing window. The ShipConstructor Navigator will load. Click Close to close the ShipConstructor
Navigator. You have now successfully installed ShipConstructor on your network.

Note
If you have other machines on your network that need to have ShipConstructor installed you can re-run the client
installation and activate licensing steps on each machine

3. MODIFY OR REMOVE SHIPCONSTRUCTOR

Modify ShipConstructor Installation


To add or remove features from a ShipConstructor 2016 installation

1. Open the Control Panel from Windows' Start Menu.


2. Open Programs and Features.
3. Find ShipConstructor 2016 in the list of installed applications.
4. Click Change. The Change/Repair/Uninstall screen will be displayed

22
5. Click Change. The Customize Installation menu appears.

6. Check/Uncheck the Components you want to Add/Remove to your ShipConstructor installation and then click Next. You will see a
progress screen.
7. When the new components have finished installing, click Done.

Remove SSI Licensing


To remove an installation of SSI Licensing

SSI Licensing handles licensing for all ShipConstructor products. You should only remove this if you are removing all ShipConstructor products.

1. Open the Control Panel from Windows' Start Menu.


2. Open Programs and Features.
3. Find SSI License Server in the list of installed applications.
4. Click Uninstall. The confirmation window will appear.
5. Click Yes to remove SSI Licensing.

Removing ShipConstructor
To remove an installation of ShipConstructor 2016

1. Open the Control Panel from Windows' Start Menu.


2. Open Programs and Features.
3. Find ShipConstructor 2016 in the list of installed applications.

23
3.

4. Select it and click Uninstall.

4. UPDATING SHIPCONSTRUCTOR
It is possible to update existing installations of ShipConstructor whenever a new version is released. By doing this you can receive the newest
enhancements without a lengthy reinstall process. If you are using ShipConstructor in a network environment the server and all client workstations
should be updated at the same time since doing so ensures that the project databases on the server are in sync with the software on the client
machines.

Downloading the Update


To download the files necessary to apply the update, visit the SSI website and find the updates section. You will need the latest version of the
update for the product you want to update.

Applying the Update


1. Run the update executable on the machine you want to update. The file should be named SC2016-Update###.exe where ### refers to
the update version you have downloaded. The update installation initializes and the installer appears.
2. Click Install to continue.
3. When the update is complete, the installer shows a completed message. Click Done to conclude the update process.
4. You may need to reboot your computer at this time. If the Installer Information window appears, click Yes to reboot your machine now.

Note
This will complete the updating of the software portion of ShipConstructor on this computer. After you have updated all of the
machines on your network, you will need to update the project databases for use with the updated software.

Update a Project Database Version


Each updated software release may include a new version of the ShipConstructor database. Once the update is applied, you can update your
ShipConstructor projects to the required database version.

Note
Updating a project database converts a project created with a previous version of ShipConstructor into the newest version. Newer
project databases are not backwards compatible with older versions of ShipConstructor.

To update a project database version:

1. In Administrator (Start Menu > All Programs > ShipConstructor 2016 > Utilities > Administrator 2016), select the projects you
want to update.

2.

24
2. Choose Project > Update to open the Update Project Databases window.

3. Select the database version you want to update the projects to.
4. Click Start. ShipConstructor automatically creates a backup of the selected projects in the default backup directory at <SQLDataRoot>\B
ACKUP\<database name><current date&time>.bak. Once the update has completed, to view a log file of the update, click View Log.
5. Click Close.

5. TECHNICAL SUPPORT
SSI offers technical support as part of Subscription.

Office hours: 7:00 am - 5:00 pm Pacific Time

Toll-free: 1-888-210-7420

Phone: 1-250-479-3638

Fax: 1-250-479-0868

Technical Support: www.SSI-corporate.com/support/technical-support

Knowledge Base kb.SSI-corporate.com

Web: www.SSI-corporate.com

25

You might also like