The following provides detailed information on EPC Server' partnership arrangements with technical software developers.
Software must support analytical problems encountered by professionals who work in the construction business
Typical software might be finite analysis for structural analysis, pressure drop analysis for mechanical analysis, or transmission line load flow for
electrical engineers. But the software need not be only technical in nature. Scheduling software, procurement support software, and project document control packages are just a few ideas which can be placed on our servers. We are not, however looking for general software packages such as word processing or online spreadsheets. The first step in placing software on our server is to fill out aREQUEST FOR SOFTWARE AGREEMENT. We will assess each
request and forward specific instruction if accepted.
Software may be run directly from a web page or through the use of a downloadable pre and/or post processor
Software run directly from a web page usually requires an analysis, which requires limited input by the user, and returns limited output. Click HERE for an example. The analysis
can be quite detailed and still run on a web page. But if the user will be required to build an elaborate model for input and receive volumes of data as
output, a pre and/or post processor will be required. Presently web technology is extremely limited as to the generation of graphics unless JAVA technology
is used. JAVA programs are very slow to load and will only be supported on a limited basis on EPC Server. A good example of a program requiring a pre
and post processor is a finite element analysis for structural steel framing. The program could be developed as follows:
A preprocessor executable is offered for download
The user inputs the geometry and inputs loads and load combinations into the preprocessor. The preprocessor provides graphical feed back to the user.
The preprocessor sends the file to a server for analysis and the server returns the results file.
The post processor reads the file and provides graphical depiction of the results, a tabular listing of results, and the ability to save the results locally.
There are many work arounds to resolve the limitations of web based analysis. The example cited above is only one potential solution.
All screens must contain the "Look and Feel" of EPC Server analysis web pages
Our logo must appear on all web pages with the exception of the final output where the user selects a particular calculation sheet header. This is true
for pre and post processors as well. Software placed on our servers owned by our developer partners may also contain the developers logo. This
logo, however may not contain a clickable link. We want our customers to stay on our site. Our personnel will either develop the web page or provide
the appropriate HTML to the developers.
EPC Server personnel will assist in development of the user interface features
A developer may have existing code developed in C,Visual Basic, or other format, which requires reformatting for web, based applications. If your software
is accepted by EPC Server, our staff will assist in reformatting the code to execute within the constraints of our medium. It will be the responsibility of the
developer to provide input to our staff and to verify the accuracy of the final product. We place a stoplight icon on the lead in screens for each analysis.
A green Light means the analysis is verified as accurate. A red light means verification has not yet been performed. A yellow light means that an unresolved
bug has been reported to us. The yellow light provides a link to the bug report.
A sample analysis is recommended to be developed for viewing on our web pages
A user will not pay for a service unless he/she knows what to expect. The sample analysis can be presented in DEMO format or presented as a series
of screen shots. A demo version would execute the program with predetermined input values. EPC Server's staff can assist in developing the Demo
version of the software.
If deemed necessary, a downloadable users manual must be developed
Simple analysis or analysis developed with explicit prompts will not require a manual. But more elaborate analysis will require one. It is the responsibility
of the developer to provide a manual to EPC Server for his/her program. The manual should always be downloadable (not on a web page). PDF is the
preferred format. EPC Server will assist converting another document format to PDF.
The developer placing software on EPC Server maintains ownership of said software, however removal of software form our servers requires EPC Server's agreement.
Once a working copy of the developers software is placed on EPC Server it will remain on our server unless EPC Server decides to remove it. EPC Server requires that
the software as developed on our server remain exclusive to EPC Server. That is to say a copy of the files cannot be directly placed on another server. We do not, however
require exclusivity on the developers software content. This provides the developer the ability to market his/her software as a stand-alone executable package or to develop
web based analysis on another server. In a nutshell, the program is owned by the developer, but the files developed for the developer's program to run on our server are
the property of EPC Server.
New software placed on EPC Server's systems must be offered free of charge for the first 90 days.
In order to properly market new products we have a "NEW PRODUCTS EMAIL SERVICE" and highlight new products on our front page. New software will
always be free for the first 90 days for users to get aquatinted with your package.
Bugs submitted by users are the responsibility of the developers to resolve. Interface problems developed by our organization will be resolved by EPC Server.
Users have the ability to submit BUGS for any software placed on our server. Bug reports will be automatically routed to the developer via Email. A yellow stoplight will automatically
be placed on the lead sheet to the analysis. If a pre processor is used, the yellow stoplight will show when the user is online. It is the responsibility
of the developer to resolve the BUG. EPC Server's staff will assist with coding changes if required. If the BUG has resulted in inaccurate results then all
users who have accessed the program will be informed via EMAIL with a credit offered for all expenditures in using the program. If a program has too many
BUGS ( as determined by EPC Server) the access to the program will be removed until all problems are resolved. It is imperative that developers spend a great
deal of time debugging their programs for users to maintain a high level of confidence in your product!!!
User Fees for developers software are set by the developer. EPC Server will provide recommendations only.
You should know what your software is worth. We have a good idea of what the market will bear. If you can buy similar software for $100 than your
software is offered more for accessibility than for cost savings. You might want to charge a paltry $5 per use in this instance. The objective of EPC Server
is to offer quality technical software at an affordable per usage price. If your software has had little or no usage and we believe pricing is the issue we will
make pricing reduction recommendations to you. You may even revert to offering the package free of charge for an additional time frame. We review
software package usage on a monthly basis for these evaluations.
60% of the fees go to the developer with 40% retained by EPC Software.
The majority of fees collected are targeted to the developer. Our fee helps pay for the development assistance, marketing, and yes profit.
Remittance of fees to the developer is made on a monthly basis as the monies are received by EPC Server.
There are two ways we collect fees, Credit Cards and Company Accounts. Credit Card services charge a service fee, which is deducted before
the developer and EPC Server revenues are calculated. Credit Cards are automatically credited to our account and thus will be included in any monthly
remittance to the developer. Company Accounts are invoiced monthly and are required to be paid within 30 days. Developers remittance will be
paid at the end of the month when the company account is paid to EPC Server. Every month both remittance and a statement will be mailed to developers
showing usage, remittance value, and accounts payable by company accounts.
No fee will be remitted to the developer if the fee is deemed none collectable by EPC Server.
Most people are honest but not everyone.
Two conditions can occur where a fee is not remitted. A user provides information to his/her Credit Card issuer on a basis on not paying
a charge and the Card Issuer informs us that previous payment is Due back to the Card Issuer. EPC Server will not require monies to be paid by the developer
but the amount, which was required to be repaid by EPC Server, will be deducted from future remittances to the developer.
In the case of a company account, if the amount due is not paid then no remittance is made to the developer.
It is in the best interest of EPC Server for all users to pay for services and we will do everything in our power to collect all monies due.
