AL FATEH UNIVERSITY ODAC

Division 14 Mechanical Work Section 14700

Division 14 - Conveying Systems

Section 14700 – Lift System Software

Part 1: General
1 01 Work Included

A. Comply with all documents referenced in Section 14200 and in this Section.
B. Provide equipment with either:
1. Control systems manufactured by third-party sources, using relatively generic
software which, along with detailed documentation that permits the Owner’s
own competent elevator mechanics to service and re-adjust the various lift
systems, or
2. A comprehensive software package, including all related hardware information
for competent technicians to readily understand system functions in order to
facilitate third-party maintainers undertaking the servicing, adjusting and
altering of equipment systems, as the Owner may require from time to time.
C. Provide complete documentation, illustrating functions of software systems,
including:
1. General system overview.
2. High-level functional description.
3. Source code listing with commentary (in assembler or higher level
language, as suited).
4. Hierarchy of sub-routines (charts of lineage).
5. Main sub-routine listing, with descriptions.
6. Sub-routine cross-references.
7. Parameter cross-references.
8. Parameter listings.
9. I/O tables and charts, showing output bus and input signals.
10. Applicable technical manuals for adjusting, including drive control adjustment,
terminal characteristics for diagnostic work, and user procedures.
D. Where items are referred to in the singular it is intended that such reference
apply to as many submissions as needed to obtain the desired effect and
result, for the entire set of system installations.

1 02 DEFINITION OF TERMS

A. The term ”Software Engineer” as used herein, refers to an agent of the Owner
who is empowered to interpret the Software Package and confirm that all
related materials and procedures have been fully complied with by the
contractor (and Lift Sub-contractor).

1 03 MATERIALS, SYSTEMS & WORKMANSHIP

A. Provide necessary information covering all software and related hardware

systems, so that the architecture, purpose and function of each system are
fully documented.

Al LABINA / AL MANAR
in partnership with Hamza/ ECH/ LCE JV
AL FATEH UNIVERSITY ODAC
Division 14 Mechanical Work Section 14700

1 04 COMPLETION AND DELIVERY

A. Provide a final Software Package within six (6) months after successful
completion of Final Acceptance Inspections and Tests of each elevator
group.
B. Deliver a Software Package for storage by a Legal Trustee selected by the
mutual agreement of the Owner and Elevator Sub-contractor.
C. Arrange a “right of access” by the Owner’s representative and the Software
Engineer, that will include full use of all materials held in trust by the Legal
Trustee, in the event of “default” by the Elevator Sub-contractor or
Maintenance Contractor, under terms of the Maintenance Agreement for
Elevators.

PART 2: PRODUCT

2 01 SOFTWARE PACKAGE MATERIAL

A. Provide for final review by the Owner’s representative:

1. Hard copy listings of all documentation including: source code, software
manuals and other manuals requested herein. Designate all documents
with headers, indicating: elevators covered, nature of control, number of
pages and (for source codes) the number of lines and date/time of the
listing generation.
2. Reproduce all hard-copy documents on microfilm, with document
designations used by the film agency transposing the materials. Include, at
the start of each filmed document, a document header and the film
agency’s designation.

2 02 GENERAL SYSTEM OVERVIEW

A. Provide a descriptive overview (to help understanding the system) prior to

proceeding with the next level of detail, including but not limited to:

1. How the elevator system software makes use of sub-systems.

2. Function of each sub-system, with explanations of microprocessors used.
Provide outline descriptions of each computer that is used by the lift
system, including: a car computer, dispatch computer, sequence circuit, A/I
or learning computer, backup computer, drive computer, position dictation
computer, peripheral control computer, communications computer, and any
other computer, microprocessor or sub-systems specific to the elevator
system being described. Include configuration and function of signal panels
and other such user interfaces.
3. Description of interfaces among sub-systems, including explanations of
hardware, computer inputs/outputs, addressing schemes, related control
panels, relationships of parameters to external circuits, bit values and their
meanings, all as related to the flow or disposition of control.

2 03 HIGH LEVEL FUNCTIONAL DESCRlPTION

A. Show how each sub-system can be decomposed into functions and sub-
functions. For each high level functional description:
1. Explain what is to be performed.
2. Detail the hierarchy of software down to sub-function level.
3. Identify activation requirements of functions.

Al LABINA / AL MANAR
in partnership with Hamza/ ECH/ LCE JV
AL FATEH UNIVERSITY ODAC
Division 14 Mechanical Work Section 14700

4. Describe inter-functional interfaces and identify parameters to be passed.

5. Cross reference relevant subroutine names.
6. Describe the database structure.
B. Provide information for each computer comprising the system, organized by
separate chapter headings. To the extent possible, use a structure such as:
1. General: Introductory comments for the system.
2. General Structure: Outline the configuration and the flow of logic programming
that controls each computer, illustrating the software as an aggregate of
routines. Include:
a. General flow chart with routine module names, indicating the main loop
repetition rate. Show main function blocks (core sub-routines) in the general
flow chart that controls respective functions and detailed sub-routines (show
hierarchy tables) centered around and subjected to the individual core
routines.
b. Indicate changes in processing routes resulting from items as: operational
modes (suspend, inspection, independent service, fire emergency service,
fully automatic operation, operation status [acceleration, deceleration, stop,
etc.] or door status [open/closed]), as well as for shunting routes to allow the
development of optimal logic.
c. Where required to clarify lift system operations, explode the logic flow of core
routines to indicate all internal routines and routing.
d. Discuss the address and algorithm structures, data structures and control
structures, indicating their order of execution, to prevent contradiction.
3. Program Hierarchy:
a. Discuss each main sub-routine in main Program flow chart, indicating the
purpose of the main sub-routine, its function and activation requirements.
b. Provide a chart for each main sub-routine. Show hierarchy (parent/child)
relationship between a main sub-routine and associated sub-routines.
Arrange charts to show main sub-routines in alphabetic order.
c. Reference all sub-routines by their program names.

4. Explain Sub-routines: Describe the purpose of each. Arrange the presentation

in chart form, listing the program name of each sub-routine alphabetically.
5. Explain Inputs and Outputs: Describe the relationship between the processor
and lift system hardware. Indicate parameters that are ‘input to’ and ‘output
from’ the program. Identify all hardware devices and points, including relay
contacts and terminals, to give a clear understanding of the interface between
software and system hardware. Identify all parameters by their program
names and discuss ‘bits’, ‘flags’ and their meanings. Arrange the presentation
in chart form with parameters in alphabetic order. Provide a description of the
output bus and input signals.

6. Explain Main Parameters (Data Dictionary): Alphabetically list all main

parameters used in the program and describe their purposes.
7. Explain Relays: Provide an alphabetic list of all relays used in each controller,
contacts associated with each relay, location of each relay in the wiring
diagram, and describe the purpose of each relay.
8. Provide a memory map.
9. Cross-reference: Provide a cross-reference for all sub-routines and parameters
used in the program. Arrange all sub-routines and parameters in alphabetic
order (by name). Include:
a. Sub-routine Tables: Indicating:
i. Sub-routines called.
ii. Sub-routines referred to.
iii. Parameters set by the sub-routine.
iv. Parameters, which are referred to by the sub-routine.
b. Parameter Tables: Indicating:
i. Sub-routines, which set the parameter.
ii. Sub-routines, which refer to the parameter.
3

Al LABINA / AL MANAR
in partnership with Hamza/ ECH/ LCE JV
AL FATEH UNIVERSITY ODAC
Division 14 Mechanical Work Section 14700

2 04 SOURCE CODE LISTINGS

A. Provide complete listings for all microprocessor devices, reflecting the “as built”
condition of the elevator system. Include for each listing:
1. Parameter initialization values and locations.
2. Designation and English language description of the purpose of sub-
routines.
3. English language commentary, indicting the processing function
accomplished by lines of code.
4. Main Sub-routine cross-reference, located at the end of the listing.
5. Parameter Cross-reference, located at the end of the listing.
6. Parameter List, located at the end of the listing.
7. Load Map.

2 05 SOURCE CODE DOCUMENTS

A. Provide a complete list of all source code documents, indicating:

1. File number of the listing.
2. Type of computer covered.
3. Building name.
4. Elevator number.

2 06 ADJUSTMENT MANUALS

A. Provide complete manuals listing all procedures used to adjust lift systems.
Include:
1. Hardware data indicating the function, settings and tolerance for each
device possibly requiring adjustment, including: drive, machine, relays,
shaft equipment, car equipment and pit equipment. Include all mechanical
devices having electrical settings.
2. Procedural flow charts for operational sequences that may involve user-
initiated action, safety check sequences, or devices that interface with
elevator users. Include, on procedural flow charts, the names of software
routines used in the procedure.

2 07 GUIDE TO BASIC FUNCTIONS

A. For each Supervisory Control System, provide a guide to its basic functions.
Include those defining the basic operating configuration and features of the
system, as well as optional features, including but not limited to:
1. General overview.
2. A/I or learning functions.
3. Other operational features of the group, including but not limited to:
a. Preference given to long-wait hall-calls.
b. Preference given to floors by-passed by fully loaded car(s).
c. Backup systems.
d. Zoning, or home-landing operation.
e. Out-of-service monitoring.
f. Independent Service operation.
g. Attendant operation.
h. Executive operation.
i. Emergency power operation.
j. Fire Emergency recall.
k. In-car Emergency operation.
l. Diagnostic and traffic survey capabilities.
4

Al LABINA / AL MANAR
in partnership with Hamza/ ECH/ LCE JV
AL FATEH UNIVERSITY ODAC
Division 14 Mechanical Work Section 14700

4. List of other features for system type, available from elevator Sub- contractor.

PART 3: EXECUTION

3 01 SAMPLES FOR REVIEW & CORRECTION

A. Submit for review by the Software Engineer and the Owner’s representative
hard copy samples of each documentation-type requested herein, prior to
delivering the Software Package.
B. Advise the Software Engineer of locations and times at which documentation
samples may be reviewed, giving at least four (4) weeks advanced written
notice of the dates.
C. Assist the Software Engineer and Owner’s representative with their review
process and respond to specific requests for documentation changes. Re-
submit corrected samples until the Software Engineer and Elevator Sub-
contractor have a mutually satisfaction: set of understandings as to the final
content of a Software Package.
D. Provide the Software Engineer with:
1. A full set of hard-copy documents.
2. A full set of microfilmed documents.
3. Microfilm viewing equipment.
4. Access to Elevator Sub-contractor’s background documents, needed for a
review.

3 02 LONG-TERM ACCESS

A. Deliver the final Software Package to a legal Trustee, selected by mutual

agreement between Elevator Sub-contractor and Owner. Arrange a ”right of
access” to material by the Owner (Includes full use by Software Engineer) in
the event of a ”default” by the Elevator Sub-contractor (or by the Maintenance
Contractor) under terms of the Elevator Maintenance Agreement.
B. Assist, as necessary, the Software Engineer’s future review process and
provide:
1. A full set of hard-copy documents.
2. A full set of microfilmed documents.
3. Microfilm viewing equipment.

END OF SECTION 14700

Al LABINA / AL MANAR
in partnership with Hamza/ ECH/ LCE JV