86-155 Earthquake Country Software - Building permit data base systemSC-6'r(-r+43Gti
BY THIS AGREEMENT made and entered into on theday of A -u -9 -u -s t 19 86
by and between the CITY OF CUPERTINO (Hereinafter referred to as CITY) and
Name (1) Earthquake Country Software (2)
Address 1 Biyt hswoodrive City Los Gatos, CA Zip 95030 Phone 08 54-0922
(Hereinafter referred as CONTRACTOR), in consideration of their mutual covenants, the parties hereto agree as follows:
CONTRACTOR Shall provide or furnish the following specified services and/or materials:
Per Attached "System Specifications/Scope of Work"
DELIVERY:
EXHIBITS: The following attached exhibits hereby are made part of this Agreement:
"System Specifications/Scope of Work"
"Specific Terms and Conditions"
TERMS The services and/or materials furnished under this Agreement shall commence on
Date of Signatures
and shall be completed before November 15 , 1986
COMPENSATION For the full performance of this Agreement, CITY shall pay CONTRACTOR:
GENERAL TERMS AND CONDITIONS
Hold Harmless. Contractor agrees to save and hold harmless the City, its officers, agents and employees from any and
all damage and liability of every nature, including all costs of defending any claim, caused by or arising out of the per-
formance of this agreement. City shall not be liable for acts of Contractor in performing services described herein.
Insurance. Should the City require evidence of insurability Contractor shall file with City a Certificate of Insurance
before commencing any services under this agreement. Said Certificate shall be subject to the approval of City's
Director of Administrative Services.
Non -Discrimination. No discrimination shall be made in the employment of persons under this agreement because of
the race, color, national origin, ancestry, religion or sex of such person.
Interest of Contractor. It is understood and agreed that this agreement is not a contract of employment in the sense
that the relation of master and servant exists between City and undersigned. At all times Contractor shall be deemed to
be an independent contractor and Contractor is not authorized to bind the City to any contracts or other obligations in
executing this agreement. Contractor certifies that no one who has or will have any financial interest under this
agreement is an officer or employee of City.
Changes. This agreement shall not be assigned or transferred without the written consent of the City. No changes or
variations of any kind are authorized without the written consent of the City.
CONTRACT CO-ORDINATOR and representative for CITY shall be:
Name Steve Piasecki
Department Planning and Community Developmen
Address 10300 Torre Avenue Cupertino, CA 95014 Telephone 252-4595 x247
This Agreement shall become effective upon its execution by CITY, in witness thereof, the parties have executed this
Agreement the day and year first written above.
CONT •
• , �' i • ., , �7�'
/ Ilft/ %/AI c
(ATTACHMENT))/
e
e •�
/vo / bj --o'go" c 4 .Cff )60, U 0
City of Cupertino
AGREEMENT
NO. 0 1 7 2 3 9
SC-6'r(-r+43Gti
BY THIS AGREEMENT made and entered into on theday of A -u -9 -u -s t 19 86
by and between the CITY OF CUPERTINO (Hereinafter referred to as CITY) and
Name (1) Earthquake Country Software (2)
Address 1 Biyt hswoodrive City Los Gatos, CA Zip 95030 Phone 08 54-0922
(Hereinafter referred as CONTRACTOR), in consideration of their mutual covenants, the parties hereto agree as follows:
CONTRACTOR Shall provide or furnish the following specified services and/or materials:
Per Attached "System Specifications/Scope of Work"
DELIVERY:
EXHIBITS: The following attached exhibits hereby are made part of this Agreement:
"System Specifications/Scope of Work"
"Specific Terms and Conditions"
TERMS The services and/or materials furnished under this Agreement shall commence on
Date of Signatures
and shall be completed before November 15 , 1986
COMPENSATION For the full performance of this Agreement, CITY shall pay CONTRACTOR:
GENERAL TERMS AND CONDITIONS
Hold Harmless. Contractor agrees to save and hold harmless the City, its officers, agents and employees from any and
all damage and liability of every nature, including all costs of defending any claim, caused by or arising out of the per-
formance of this agreement. City shall not be liable for acts of Contractor in performing services described herein.
Insurance. Should the City require evidence of insurability Contractor shall file with City a Certificate of Insurance
before commencing any services under this agreement. Said Certificate shall be subject to the approval of City's
Director of Administrative Services.
Non -Discrimination. No discrimination shall be made in the employment of persons under this agreement because of
the race, color, national origin, ancestry, religion or sex of such person.
Interest of Contractor. It is understood and agreed that this agreement is not a contract of employment in the sense
that the relation of master and servant exists between City and undersigned. At all times Contractor shall be deemed to
be an independent contractor and Contractor is not authorized to bind the City to any contracts or other obligations in
executing this agreement. Contractor certifies that no one who has or will have any financial interest under this
agreement is an officer or employee of City.
Changes. This agreement shall not be assigned or transferred without the written consent of the City. No changes or
variations of any kind are authorized without the written consent of the City.
CONTRACT CO-ORDINATOR and representative for CITY shall be:
Name Steve Piasecki
Department Planning and Community Developmen
Address 10300 Torre Avenue Cupertino, CA 95014 Telephone 252-4595 x247
This Agreement shall become effective upon its execution by CITY, in witness thereof, the parties have executed this
Agreement the day and year first written above.
CONT •
• , �' i • ., , �7�'
/ Ilft/ %/AI c
Specifications Page 1
Approved ( )
City of Cupertino
Building Department Software System
System Specifications/Scope of Work
Ed
The software is described as a building permit data base system written in
Condor. The system is to be designed as close as possible to a turn -key
application.
The BUYER's objectives include:
1.
2.
3.
4.
5.
6.
7.
Minimize data entry
Produce reports
Issue permits
Provide checks for data
conditions.
Eliminate paper
entry errors, holds and special
Track building department applications through the process
Provide item data for purposes of future budgeting efforts
DEVELOP[=/SYSTEM DESCRIPTION
The SOFTWARE will run on an IEM-PC computer with hard disk, under an
operating system called PC -DOS The SOFTWARE will be developed around and
designed to run under an off -the shelf database package called CONDOR.
The SOFTWARE will be roughly divided into 4 phases:
1. Systems analysis. SELLER will work with BUYER to identify the needs
of the BUYER regarding the SOFTWARE. SELLER may offer suggestions
relating to the inclusion or exclusion of data in the overall system
design. After the analysis the BUYER should be able to draft two
sets of specifications, the basic SOFTWARE requirements and the
SOFTWARE acceptance criteria.
2. Detailed specification design. BUYER will work closely with SELLER
to suggest, review, and accept or reject the specifications as they
are defined. Buyer will use all available internal resources to
provide the system overview with inputs and feedback from
management. BUYER will designate a responsible party for system
coordination. SELLER will design the detailed specifications with
the information supplied by BUYER plus incorporate SELLER's
knowledge of business and of database systems to provide the best
overall system. SETS will designate a responsible party for
system coordination.
3. Database development. SELLER will take the detail design and
develop the forms, reports and procedures necessary to operate the
SOFTWARE under CONDOR. Included with the overall system will be
procedures and utilities to allow simple modifications and
alterations at the BUYER's site by BUYER's staff.
�7
A. Testinct/Installation/Training. SETTER will perform initial system
tests for operation as defined by the detail design. BUYER will
perform acceptance testing sufficient to establish that the system
conforms to the detail design. SELLER will install the system at
the BUYER's site. DocLunentation will include flow charts of the
system, formats and attributes of the databases, and source code of
the command procedures (sufficiently documented for later
modification and maintenance) .
All modules will be menu driven. Each module will provide system
controlled interaction with the user via help routines provided as
needed. Modules capabilities will include:
* DATA ENTRY
* UPDATES AND CORRECTIONS
* DISPLAY UPON COMMAND
* GENERAL REPORTS
* SPECIAL REPORTS ACCORDING TO USER SELECTION CRIT=
As various detailed specifications of each module are formatted,
EARTHQUAKE COUNTRY SOFTWARE will check with BUYER for agreement and
modifications. The sequence of events is as follows:
* Design the screen formats
* Define the field attributes
* Provide menus for module action and interaction
* Develop conmand procedures for each section of each module
* Create general reports according to commonly accepted practices
* Create custom reports as required by BUYER management
SCOPE OF WORK/COMPONENTS
The following outlines the general ccirponents of the software system:
1) DATA ENTRY
a) Permit (Includes fees)
b) Plancheck
c) Inspection
d) Final
2) TRACK PLANCHECK
3) MONITOR INSPECTION PROCESS
(Include "tickler" option)
4) RECORD FINAL INSPECTION/OCCUPANCY
5) REPORTS
a) Monthly financial (monitor fees collected and payments
to plancheck, inspection contractors)
b) Monthly report of issued planchecks
c) Building permit activity/status report
(year to date)
1) Permits filed
2) Permits issued
3) Permits finaled and occupancy granted
d) Building plancheck status
e) Building inspection status
f) Lists of permits in each phase including:
1. Applications submitted
2. Permits in plan check including first, second, or third
plan check.
3. Permits which have been issued and are currently in the
inspection phase.
4. Permits which have been issued and have completed all
requisite inspections except the final inspection.
5. Permits which have been issued and finaled should be
sent to an archive file. The information of the
building data should be automatically transferred to
the Planning Departments land use Data Base File.
SOURCE DATA
The data in the permit data base comes from three major sources:
1. The permit application
2. City designed code tables for property descriptions, permit fees,
time deadlines for plan checks, property valuation, and other
ancillary data
3. Transaction slips for plan checks, department transfers,
inspections, holds, conditions, fee receipts, acceptances, and
other ancillary information
The data in the permit data base is stored as static or dynamic data? --Il
sets. A static data set is comprised of records which do not change or
change seldomly. Static data sets include:
Applicant name and address
Contractor name and address
Architect name and address
Permit basic information
Permit fee tables
Property description code tables
Property valuation tables
Inspection code tables
Plan check deadline tables
Dynamic data sets are transactions which indicate the flow of permit
through the system. Transactions include:
Permit application initialization
Permit fees calculated
Permit fees paid
Sent to plan check (or other departments)
Received from plan check (or other departments
Acceptance or rejection of any phase of permit cycle
Applicant action or inaction at any phase of permit cycle
Inspection logs
Permit issued
The permit number is the key which relationally ties the date from each
data set together. Name and addresses have a secondary key which are
applicant social security number, and contractor's and architect's license
number. Transactions have a code key which identifies the type of
transaction.
bldgsoft(B-4)
TRANSITION STAGES
119
There are three transition stages through which building permits car.
travel: I) Application, `) Plan check, 3) Inspection
APPLICATION TRANSITION STATE
START SUBMITTED ACCEPTED REJECTED WITHDRAWN APPROVED
I i I I I I
Inquiry I i
plan fees I i
I I I I
requirements I
(no action) I
I i I
I I I I
-*Flan submitted I I
I I I
i I I I
I *Enter data. i I I I
I !Submit invoice for
iplan check fees I I
i I I
I I I I
f I -*Permit # issued i
I I I
I I I
I I I
I -HOLD not complete* I
1 i
I I I
Fee not paid aF i I
I i I i
I < I
I I
ee returned
I I I I
I *Fee paid
I > I
i I i I I
i I I I I I
I I I I I I
I I I I I
I I I I I I
f i I I i I
i I I I I I
L
Specifications July 8, 1986 Page S approved( )
PLAN CHECK TRANSITION STATE
=TART PLAN CHECK ACCEPTED REJECTED WITHDRAWN APPROVED PERMIT
I I 1 I I I I
*Refer to I I I I I I
departments I I I I )
I *Planning I I I I )
I *Building I I I I I
I *Public Works I I I I I
I *Fire I I I I { I
I *Sanitary I I I I I
I *Health I I I I I I
I I I I I I I
I *Plan returned with ! I I I
I 1cc,mrilent s®,�) I I I I I
I I I I ! I I
I *Doesn't meet p l anw==m==> I I I I
I I I ! I 1 I
Return t applicant, I I I
I 1 1 I I 1 I
I I *All departments accepted
I I I I 1 I I
I I *Invoice inspection fees ) ! )
I 1 I I I I I
Return to applicant* I I
I I I I I I I
< Time expires, Return to applicant* I
I I 1 I I I I
I I I 1 I *Final signature
! I I { I ((special notes)
I I I I I *Final fees
I I I I I I collected I
i I I I I I I
I I( Inspection hold or conditions
f i I I I i 1
I *Hold or condition reviewed > I I
I I I I I I I
I 1 I I I *OK for final
I I I I I I permit
i I I I I I I
1 I I I I *New inspection
I requiredm
I I I I 1 I I
I I I I I I i
I I I I I I I
1 I I I I I I
I 1 I I I I I
I I I I I I I
I I I I I I I
f I I 1 I I I
i I I I I I I
I I I I I I I
i I I I I I I
Specifications July S,106 � page 4 approved( )
INSPECTION TRANSITION STATE
PERMIT REQUEST INSPECTION ACCEPTED REJECTED WITHDRAWN APPROVED ISSUED
I I I I I I I I
*Applicant I
I requests I I I I I I
I inspection
I I I I I I I I
i *Assign next day 1 I I I I
I Iinspections
I I I I I I I I
i I *Not approved.o®===> I I I I
I I i I I I I I
IC Mor problem* i I I
I I(======Applicant verbal request* I 1 I
i I next day inspection I I I I
I 1 I I I I I !
*Reinspection I I i I ! I
i I I 1 I IF I I
I *Check for add fee I I I I I
I I 1 I I I I I
I I *Approved®> I I 1 I I
I I I 1 1 I I I
®� Hold or condition* I i I I
I I I I I I I 1
Inspection i I I I I I I
held I I I I I I I
W>
Hold or condition removed®> I I I 1 I
i I 1 I I I I 1
1 1 1
*All inspections comp 1 et edeo> I I
1 i 1 I No holds or conditions I I
f 1 I I I I I I
I I I I I I *Check for I
! I I I I I I cont ruct i on
I I i i I I I fees I
Return to applicant* I I
I I I I I I I I
Time expires, return to applicant* I
I 1 I I I I I I
1 I I I I I I I
I I I I I I I I
I I i I I I I i
A.
M:39
C.
EARTHQUAKE COUNTRY SOFTWARE
SALES ORDER
TERMS AND CONDITIONS
This is a proposal for software support and will become a SALES
ORDER upon the signature acceptance of both parties. Upon such
acceptance, SELLER agrees to provide and BUYER agrees to buy
software support as described below (hereafter referred to
individually and collectively as the 11SOFTWARE").
This is a Time and Materials SOFTWARE agreement to provide a
Computer Data Base System for the Building Division of the
Department of Planning and Community Development. The
specification of the system outlined on exhibit A. Subsequent
detailing of the system design shall be mutually agreed upon in
the initial design stage.
TYPE OF CONTRACT/RATES
This is a time and materials contract not to exceed a maximum of
$5,000.00. The quotation is based on the information provided to
date (see attached summary of specifications). If additional
requirements arise, the additional time will be calculated and
submitted to BUYER for approval before the additional work can
begin.
The quotation estimate for this proposal is approximately two (2)
man weeks of work billed at rates indicated on exhibit A not to
exceed $5,000.00
SERVICES/PAYMENTS
Payments for work completed will be paid in accordance with the
following schedule:
STEP DESCRIPTION
1
2
3
4
WORK/PAYMENT SCHEDULE
ESTIMATED ESTIMATED PAYMENT
HOURS COMPLETION DUE NOT
DATE TO
EXCEED
Detailed System Design
20
9/30/86
$1,500
System Development
25-35
10/30/86
$1,875
Installation/modification
15-25
11/15/86
$1,125
Training
5-10
11/30/86
500
65-100
Maximum Payment
not to exceed $5,000
EARIHQUAFE COUNTRY SOFTWARE
page -2-
Invoices will be submitted and paid as each step is completed.
Payment shall be made within 45 days of acceptance by City of
each component.
SOFTWARE acceptance will be after training and a sufficient test
sample has been run by BUYER. In no case will the acceptance
date extend beyond 6 weeks after SOFTWARE installation.
D. CHANGES AND CANCELLATIONS
1. No change shall be made relating to the SALES ORDER without
written consent of SELLER and buyer.
2. If any such change increases or decreases the cost of or the time
required for performance of the order, or otherwise affects any
of the provisions of the order, an equitable adjustment shall be
made in the price and/or delivery schedule, and in such other
provisions of the order as may be so affected, and the order
shall be modified in writing accordingly.
E. TITLE/PROPRIETARY RIGHTS
Title and proprietary rights of each and every component of the
computer software system shall not be transferred to any third
party nor marketed by any party to this agreement without the
consent of the other party. It is contemplated that the parties
shall enter into a separate joint venture agreement for the
marketing of said proprietary rights. The above provision does
no apply to the following modules which remain the property of
the seller.
Module Description Copyright Date
V nr 0 0 - R C - C o J &Vt& (q 8S
C It t M - CJ ,,,-A-rGS FICJ.OS ("' C-s.JOoit
A (iG"YS - ri A ✓� 1� ►ter 7C�SJlZ E G J It 01 FAm H 5, ✓ 6 A !r rz�
r(Vk710J-C (Ayp 9t&VCv4C-) Stirs 1 q Sy
C_W ECiC _ REAL 7, 11 E k040, JG A✓O PA0CL-O'dC- 01r -16 -et 19 X73
/`� /� 14. h � rt G E - (' o ,�. ,,.� �. E � z GK s � J'► rr� �� �- 6 � r� 1n.5 l g g �
C4t&LC C Port l4 $ 3
tN56r��,n.(. �oL�/}vt V/3,,,,vyj (ti DoC,.nC•.�zj
AccoUd7, .)4 - CflC-✓cngL �C,�6�.i� rdcco.rp�t1 RC�Gr�/3a� [�1� l4?33
SIA7Cn(--J - 7(;1tC-E L&,/(rt
j A A C (c-, L S `t J 7 C- h
The above modules are standard formats already developed by
seller. All rights to these modules shall remain with seller.
Seller and Buyer agree that said modules shall not constitute
more than 25% of the value of the completed computer software
package.
earthsoft(M-2)
Specifications Page 1
Approved ( ))t_1
City of Cupertino
Building Department Software System
System Specifications/Scope of work
The software is described as a building permit data base system written in
Condor. The system is to be designed as close as possible to a turn -key
application.
Wylffl X4 01W
The BUYER's objectives include:
1. Minimize data entry
2. Produce reports
3. Issue permits
4. Provide checks for data entry errors, holds and special
conditions.
5. Eliminate paper
6. Track building department applications through the process
7. Provide item data for purposes of future budgeting efforts
DEVELOR=/SYSTEM DESCRIPTION
The SOFIWARE will run on an IBM-PC computer with hard disk, under an
operating system called PC -DOS The SOFIWARE will be developed around and
designed to run under an off -the shelf database package called CONDOR.
The SOFIWARE will be roughly divided into 4 phases:
1. Systems analysis. SELLER will work with BUYER to identify the needs
of the BUYER regarding the SOFIWARE. SELLER may offer suggestions
relating to the inclusion or exclusion of data in the overall system
design. After the analysis the BUYER should be able to draft two
sets of specifications, the basic SOFIWARE requirements and the
SOFTWARE acceptance criteria.
2. Detailed specification design. BUYER will work closely with SETTER
to suggest, review, and accept or reject the specifications as they
are defined. Buyer will use all available internal resources to
provide the system overview with inputs and feedback from
management. BUYER will designate a responsible party for system
coordination. SEI -.ER will design the detailed specifications with
the information supplied by BUYER plus incorporate SELLER's
knowledge of business and of database systems to provide the best
overall system. SELLER will designate a responsible party for
system coordination.
3. Database development. SETTER will take the detail design and
develop the forms, reports and procedures necessary to operate the
SOFIWARE under CONDOR. Included with the overall system will be
procedures and utilities to allow simple modifications and
alterations at the BUYER's site by BUYER's staff.
4. Testinq/Installation/Training. SELTER will perform initial system
tests for operation as defined by the detail design. BUYER will
perform acceptance testing sufficient to establish that the system
conforms to the detail design. SELLER will install the system at
the BUYER's site. Documentation will include flow charts of the
system, formats and attributes of the databases, and source code of
the command procedures (sufficiently dociunented for later
modification and maintenance).
All modules will be menu driven. Each module will provide system
controlled interaction with the user via help routines provided as
needed. Modules capabilities will include:
* DATA ENTRY
* UPDATES AND CORRECTIONS
* DISPLAY UPON COMMAND
* GENERAL REPORTS
* SPECIAL REPORTS ACCORDING TO USER SELECTION CRITERIA
As various detailed specifications of each module are formatted,
EARTHQUAKE COUNTRY SOFTWARE will check with BUYER for agreement and
modifications. The sequence of events is as follows:
* Design the screen formats
* Define the field attributes
* Provide menus for module action and interaction
* Develop command procedures for each section of each module
* Create general reports according to coimnonly accepted practices
* Create custom reports as required by BUYER management
SCOPE OF WORK/COMPONENTS V"
The following outlines the general components of the software system:
1) DATA ENTRY
a) Permit (Includes fees)
b) Plancheck
c) Inspection
d) Final
2) TRACK PLANCHECK
3) MONITOR INSPECTION PROCESS
(Include "tickler" option)
4) RECORD FINAL INSPECTION/OCCUPANCY
5) REPORTS
a) Monthly financial (monitor fees collected and payments
to plancheck, inspection contractors)
b) Monthly report of issued planchecks
c) Building permit activity/status report
(year to date)
1) Permits filed
2) Permits issued
3) Permits finaled and occupancy granted
d) Building plancheck status
e) Building inspection status
f) Lists of permits in each phase including:
1. Applications submitted
2. Permits in plan check including first, second, or third
plan check.
3. Permits which have been issued and are currently in the
inspection phase.
4. Permits which have been issued and have completed all
requisite inspections except the final inspection.
5. Permits which have been issued and finaled should be
sent to an archive file. The information of the
building data should be automatically transferred to
the Planning Departments land use Data Base File.
SOURCE DATA
The data in the permit data base comes from three major sources:
1. The permit application
2. City designed code tables for property descriptions, permit fees,
time deadlines for plan checks, property valuation, and other
ancillary data
3. Transaction slips for plan checks, department transfers,
inspections, holds, conditions, fee receipts, acceptances, and
other ancillary information
The data in the permit data base is stored as static or dynamic data
sets. A static data set is comprised of records which do not change or
change seldomly. Static data sets include:
Applicant name and address
Contractor name and address
Architect name and address
Permit basic information
Permit fee tables
Property description code tables
Property valuation tables
Inspection code tables
Plan check deadline tables
Dynamic data sets are transactions which indicate the flow of permit
through the system. Transactions include:
Permit application initialization
Permit fees calculated
Permit fees paid
Sent to plan check (or other departments)
Received from plan check (or other departments
Acceptance or rejection of any phase of permit cycle
Applicant action or inaction at any phase of permit cycle
Inspection logs
Permit issued
The permit number is the key which relationally ties the date from each
data set together. Name and addresses have a secondary key which are
applicant social security number, and contractor's and architect's license
number. Transactions have a code key which identifies the type of
transaction.
bldgsoft(B-4)