The Hong Kong Polytechnic University · S1 2026 · FACULTY OF ELECTRICAL ENGINEERING

EE535 Maintenance and Reliability Engineering

- one subject, every graph, every model, every mark
10 Chapters47-page Bible
Our own words - no uploaded lecturer files
Built to mirror S1 2026 · updated this semester
The Complete Exam Bible · Semester 1, 2026/27

EE535 Overview

Maintenance and Reliability Engineering
— Connect asset objectives to evidence, intervention and verified closure.
  • The Hong Kong Polytechnic University
  • Semester 1, 2026/27
  • Postgraduate course
  • Electrical Engineering
  • Three published assessment components

What the course connects

EE535 treats maintenance as part of asset management rather than as an isolated repair function. An engineering asset exists to deliver value through a service or organisational outcome.

  • Assessed by An assignment worth twenty per cent, a test worth twenty per cent and an examination worth sixty per cent.
  • Core skill Tracing an asset decision from stakeholder need and objective through evidence, intervention, verification and review.
  • Operational spine Stable asset identity, controlled work orders, feasible schedules, complete closure records and analysis that changes later work.
Why read this guide

What you get in the full EE535 Exam Bible

  1. 10 chapters, 47 pages — every examinable topic
  2. 31 original practice questions, each with a model answer in the Examination format
  3. 10 worked examples, solved the way EE535 marks
  4. 13 computed figures, redrawn from the course’s own numbers
  5. Exam-morning plan for the Examination (60%) — what to revise last, where marks are lost

Free on this page: assessment table, chapter map, one worked example, key terms, FAQ. The rest is in the full exam bible.

EE535 · The Hong Kong Polytechnic University
An independent, AskSia-authored study guide. AskSia is not affiliated with, endorsed by, or sponsored by The Hong Kong Polytechnic University; the course code and name are used for identification only.
Assessment

How EE535 is assessed

ComponentWeightFormat
Assignment20%Current task covers maintenance schemes, risk ratings, ISO 55000 concepts and CMMS explanations
Test20%Format, duration, date, coverage and permitted materials are not published in the current materials
Examination60%Format, duration, date, coverage and permitted materials are not published in the current materials

The current course introduction publishes the three weights and they total 100%. The current materials do not publish the test or examination duration, format, date, coverage or permitted materials. Confirm those operational details on the current course site.

Assessment structure

20%20%60%AssignmentTestExamination

Segment widths reproduce the published percentage weights and total 100%.

Other students are asking · EE535

What other students are asking about EE535

Where can I find lecture notes or study guides for EE535 at PolyU?
The EE535 study guide in AskSia Library covers Maintenance and Reliability Engineering in 10 chapters, with the assessment table, a chapter-by-chapter topic map, key terms and a worked example, free to read on this page.
Is there a final exam in EE535, and how much is it worth?
Yes. In the offering this AskSia Library guide is built from, Examination carries 60% of the EE535 mark; the full split is Assignment 20%, Test 20%, Examination 60%.
What does EE535 cover on stakeholders, policy and asset objectives?
In AskSia Library's EE535 guide, the Stakeholders, Policy and Asset Objectives chapter explains stakeholder needs, organisational context, asset policy, objectives and measurable alignment.
What does EE535 cover on iso 55000 framework and samp?
In AskSia Library's EE535 guide, the ISO 55000 Framework and SAMP chapter explains document roles, management-system alignment, SAMP and the top-down and bottom-up route.
What does EE535 cover on lifecycle plans, portfolio and performance?
In AskSia Library's EE535 guide, the Lifecycle Plans, Portfolio and Performance chapter explains lifecycle planning, portfolio evidence, intervention timing, performance measures and review.
Weights, dates and every chapter are set out with their sources further down this page.
Current dates · verify in LMS

Current EE535 dates

DateItemControl
30 October 2026Assignment deadlineDate stated in the current assignment document for Semester 1, 2026/27.

The assignment document states the 30 October 2026 deadline. Check the current course site for submission settings or later notices.

Contents · every chapter, one map

What EE535 covers

Ten chapters connect lifecycle value and ISO 55000 asset management to CMMS records, work control, scheduling, risk, criticality and reliability-centred decisions.

01

Engineering Assets and Lifecycle Value

asset purpose, requirement classes, lifecycle stages, value and whole-life comparison

Start with the value the asset enables

An engineering asset is not valuable merely because the organisation owns it. Value appears through the service, capability or outcome the asset supports.

  • Asset value through service and organisational outcomes
  • Performance, functional, interface and maintenance requirements
  • Lifecycle stages and early commitment of maintenance consequences
  • Capital, operating and replacement cost on a common basis
  • Feasible-option screening before numerical ranking
  • Performance feedback and decision review
In the full guide: 4 pages · 2 practice questions · 2 figures
02

Stakeholders, Policy and Asset Objectives

stakeholder needs, organisational context, asset policy, objectives and measurable alignment

Stakeholders create the reason for control

Asset decisions affect customers, operators, maintainers, owners, regulators, neighbours, suppliers and other parties differently.

  • Stakeholder identification and competing expectations
  • Organisational context and direction
  • Asset management policy as principles and commitment
  • Measurable asset management objectives
  • Top-down alignment and bottom-up operational evidence
  • Decision-linked performance measures
In the full guide: 4 pages · 2 practice questions · 1 figure
03

ISO 55000 Framework and SAMP

document roles, management-system alignment, SAMP and the top-down and bottom-up route

The three documents have different jobs

ISO 55000 supplies the overview, principles and terminology for asset management. ISO 55001 states management-system requirements. ISO 55002 gives guidance on applying those requirements.

  • ISO 55000 overview, principles and terminology
  • ISO 55001 management-system requirements
  • ISO 55002 application guidance
  • Management-system elements and feedback
  • Strategic asset management plan purpose and contents
  • Top-down direction and bottom-up evidence
In the full guide: 5 pages · 2 practice questions · 2 figures
04

Lifecycle Plans, Portfolio and Performance

lifecycle planning, portfolio evidence, intervention timing, performance measures and review

Plans translate objectives into interventions

An asset management plan identifies the asset or portfolio, the result required, current performance and condition, demand and risk evidence, proposed interventions, timing, resources, responsibilities and measures.

  • Asset management plan contents
  • Condition, performance, demand and risk evidence
  • Timing of maintenance, refurbishment and renewal
  • Portfolio prioritisation and common criteria
  • Mandatory boundaries before value comparison
  • Outcome measures and response rules
In the full guide: 3 pages · 2 practice questions · 1 figure
05

Railway Maintenance Operating Model

maintenance schemes, triggers, inspection, execution, verification and operational learning

Maintenance starts from function and consequence

A railway asset supports a service inside a tightly connected system.

  • Railway assets as service-supporting systems
  • Corrective maintenance and defensible run-to-failure conditions
  • Scheduled preventive maintenance by time or usage
  • Condition-based maintenance and measurable precursors
  • Resource, access, competence and interface constraints
  • Verification and close-out evidence
In the full guide: 5 pages · 2 practice questions · 2 figures
06

CMMS Functions and Core Components

register, work, resources, materials, scheduling, history and management information

A CMMS is an information control system

A computerised maintenance management system brings together the information required to identify assets, control work, allocate resources, manage materials, capture costs and analyse history.

  • CMMS purpose and information control
  • Asset register as the transaction anchor
  • Planned and corrective work management
  • Labour, competence, tools and access
  • Materials, spares, purchasing and cost
  • Maintenance history and management reporting
In the full guide: 3 pages · 2 practice questions · 1 figure
07

Asset Registers, Hierarchies and Chainage

stable identity, location, parent-child structure, linear position and usable maintenance history

The register answers what exists

An asset register is the controlled list of assets and the attributes required to manage them.

  • Asset register purpose and controlled attributes
  • Hierarchy levels from service to maintainable unit
  • Functional location and equipment identity
  • Installation, replacement and retirement rules
  • Chainage and linear position references
  • Classification for comparable analysis
In the full guide: 3 pages · 2 practice questions · 1 figure
08

Work Orders from Request to Closure

request validation, planning, priority, scheduling, execution, verification and close-out quality

A request describes a need, not yet an authorised job

A work request can originate from a failure report, inspection finding, planned trigger, condition alert or engineering decision.

  • Work requests and initiation routes
  • Validation, duplication and asset identity
  • Priority from consequence and urgency
  • Planning scope, resources and readiness
  • Scheduling, dispatch and field execution
  • Actual findings, cause, action and materials
In the full guide: 3 pages · 2 practice questions · 1 figure
09

Maintenance Scheduling, CBM and Field Service

short and long horizons, resource constraints, condition triggers, dispatch and mobile feedback

Scheduling works on several horizons

Long-range planning shows expected jobs, workload, materials, competence, access and budget over future years.

  • Long, medium and short scheduling horizons
  • Labour, materials, access and dependency constraints
  • Opportunity maintenance and competing work
  • Calendar, usage and combined triggers
  • Condition measurements, trends and action states
  • Field service, mobile forms and dispatch
In the full guide: 4 pages · 2 practice questions · 1 figure
10

Risk, Criticality and RCM Decisions

risk response, ALARP, service criticality, value, task review, assurance and validation

Risk links evidence to a required response

Risk-based asset management focuses attention by considering consequence and occurrence evidence while balancing safety, service, performance, cost and organisational responsibilities.

  • Risk evidence and response categories R1 to R4
  • ALARP and proportional risk reduction
  • Service criticality C1 to C4
  • Value, priority and non-negotiable boundaries
  • Function, functional failure and failure mode
  • Technically applicable and worthwhile maintenance tasks
In the full guide: 3 pages · 2 practice questions · 1 figure

That value depends on decisions across the lifecycle, from requirements and acquisition through operation, maintenance, renewal and disposal. The course therefore joins strategic questions about stakeholder needs, policy and objectives with operational questions about asset identity, work control, resources, condition and risk.

The recurring discipline is traceability: a task should be linked to a function and consequence, a plan to an objective, and a measure to a decision someone can change.

Engineering Assets and Lifecycle Value

The first chapter asks what the asset is for before asking what work it needs.

It separates performance, functional, interface and maintenance requirements because a cheap option that fails a mandatory requirement is not a feasible alternative. Lifecycle comparison combines acquisition, operating, maintenance, replacement and disposal consequences on a common basis, but the arithmetic comes after requirement screening.

The practical result is a decision that can explain both value and feasibility instead of treating lowest initial price as an engineering conclusion.

Stakeholders, Policy and Asset Objectives

Stakeholder needs become useful only when they are translated into direction the organisation can measure and act on.

Policy establishes principles and commitment; objectives state the results assets and the management system must achieve; measures reveal whether performance is moving toward those results. The chapter follows that chain in both directions.

Top-down alignment prevents local optimisation from defeating organisational purpose, while bottom-up evidence prevents strategy from becoming a set of statements disconnected from asset condition, capability and work history.

ISO 55000 Framework and SAMP

The ISO 55000 family has distinct roles.

ISO 55000 provides overview, principles and terminology, ISO 55001 contains management-system requirements, and ISO 55002 offers application guidance. Keeping those roles separate matters whenever an answer makes a requirement or assurance claim.

The strategic asset management plan connects organisational objectives to asset management objectives and sets the framework for asset plans, decision criteria, responsibilities, resources and review. It is valuable as a route of alignment, not as a document produced for its own sake.

Lifecycle Plans, Portfolio and Performance

Asset management plans convert direction into interventions across time.

They need an asset or portfolio scope, current performance and condition, demand and risk evidence, options, resources, responsibilities, timing and measures. Portfolio thinking compares claims on common criteria while preserving non-negotiable obligations. Performance review then tests whether interventions produced the expected service, cost, risk and capability effects.

A measure is useful when it changes a decision, and a plan remains alive only when new evidence can revise its assumptions.

Railway Maintenance Operating Model

Railway maintenance combines preventive, corrective and condition-based routes within an environment constrained by service, access, safety, competence and interfaces.

A maintenance scheme needs a trigger, an action, a controlled work record, execution evidence, verification and closure. The best scheme can differ by failure mode within one asset. Corrective work can be rational where consequence is low and failure is visible; scheduled work suits evidenced time or usage relationships; condition-based work needs a measurable precursor and a response threshold.

None of them is automatically superior.

CMMS Functions and Core Components

A computerised maintenance management system integrates the information required to control assets and work. Its components include the asset register, work management, planning and scheduling, labour and competence, materials and spares, cost and history, and management reporting. Software creates no benefit by itself.

Stable identifiers, ownership, coding, mandatory fields, workflow controls and closure discipline determine whether the database supports decisions or merely stores inconsistent records.

Implementation should begin with decisions and responsibilities, then configure data and workflow to support them.

Asset Registers, Hierarchies and Chainage

An asset register answers what exists and what the organisation needs to know about it. A hierarchy supplies context by linking system, location, equipment and maintainable unit. For linear infrastructure, chainage adds a controlled position reference.

The choice of level determines whether work history is too broad to diagnose a component or too fragmented to understand a service.

Stable identity must survive replacement and movement rules, while location and parent relationships need governance so history follows the correct object and remains comparable.

Work Orders from Request to Closure

The work order is the controlled record that converts a need into authorised, planned, executed and verified action.

A sound flow captures the request, validates asset and scope, sets priority from consequence and urgency, plans resources and controls, schedules and dispatches, records actuals, verifies restoration and closes with meaningful findings. Closure such as fault fixed destroys learning because it omits the observed condition, cause, action, test and residual state.

High-quality closure makes repeat-fault analysis and task review possible.

Maintenance Scheduling, CBM and Field Service

Scheduling works across horizons. Long-range planning exposes workload, budget, competence and material demand; medium planning prepares packages and resolves procurement, access and interfaces; short-range control sequences executable orders against actual people, parts, permits and windows.

Calendar and usage triggers should remain distinct unless an operating assumption justifies conversion. Condition monitoring adds measurements and action states, while mobile field service carries controlled information to technicians and returns actuals without paper delay.

The information chain still needs ownership and validation.

Risk, Criticality and RCM Decisions

Risk-based asset management uses consequence and occurrence evidence to focus effort while balancing safety, performance, service, cost and other organisational responsibilities.

The captured case defines four response categories from R1, where reduction is required except in exceptional circumstances, to R4, where risk is acceptable. Service criticality is related but separate because customer disruption can be high without creating the same safety consequence.

Reliability-centred review begins with function and functional failure, examines credible failure modes and consequences, and selects a technically applicable, worthwhile action with assurance and later review.

How the assessment evidence should shape study

The published structure assigns twenty per cent to the assignment, twenty per cent to the test and sixty per cent to the examination.

The assignment divides one hundred internal marks across maintenance schemes, risk ratings, ISO 55000 ideas and CMMS functions. That combination points toward explanation with application: define the concept, state the decision it controls, use evidence from the case, and finish with an action or review rule.

The current materials do not publish test or examination logistics, so avoid building revision around an assumed number of sections, duration or permitted-materials rule.

How to use this guide

Start with one asset case and carry it through all ten chapters.

State the service outcome, write the requirement set, create the objective chain, place the asset in a hierarchy, open and close a work order, choose a trigger, schedule the work and challenge the intervention with risk and criticality. Complete every practice item before reading the model answer. Marks shown in this guide are AskSia study allocations and do not represent a University marking scheme.

Confirm current submission and assessment logistics on the course site.

Worked example · free

Compare two lifecycle options without losing the requirements

Q [8 marks]. Not a University marking scheme: AskSia assigns these study marks. AskSia-authored practice. Option A has capital cost 52, expected operating and maintenance cost 41, and replacement cost 18. Option B has corresponding values 61, 30 and 15. Compute the two lifecycle totals on the stated common basis, identify the lower total and state the engineering check required before recommending it. The marks shown are an AskSia study allocation.
Segment width follows the printed fictional values.Segment width follows the printed fictional values. Capital, operating and replacement costs sum to the lifecycle total, so a smaller purchase price is not automatically the cheaper choice.A fictional HK$100m lifecycle caseCapex 40Opex 35Replace 2540 + 35 + 25 = HK$100m
Segment width follows the printed fictional values. Capital, operating and replacement costs sum to the lifecycle total, so a smaller purchase price is not automatically the cheaper choice.
  • 3Calculate each total and show the components.
  • 2State the cost difference and provisional ranking.
  • 3Explain the feasibility check before recommendation.
Option A totals 52 + 41 + 18 = 111 cost units. Option B totals 61 + 30 + 15 = 106, so B is lower by 5 on the stated common basis. The ranking remains provisional until both options are shown to meet the same performance, functional, interface, safety and maintenance requirements over the same horizon. If one option fails a mandatory requirement, its lower calculated total cannot make it the preferred feasible option.
Sia tip — Write the requirement screen before the cost line. Lifecycle arithmetic ranks feasible alternatives; it does not make an incomplete option feasible.
Glossary

Key terms

Engineering Asset
An item, system or facility managed to deliver value through a service or organisational outcome.
Lifecycle
The stages through which an asset passes, from requirements and acquisition through use, maintenance, renewal and disposal.
Asset Management Policy
The organisation's principles and commitments for managing assets in alignment with its direction.
Asset Management Objective
A measurable result that assets or the asset management system are expected to achieve.
SAMP
The strategic asset management plan that connects organisational objectives to asset management objectives and planning.
CMMS
A computerised maintenance management system used to control asset, work, resource, material, cost and history information.
Asset Register
The controlled record of assets and the attributes needed to identify, manage and report on them.
Asset Hierarchy
A structured parent-child view linking service, system, location, equipment and maintainable units.
Work Order
The controlled record authorising and documenting planned or corrective maintenance from request to closure.
Condition-Based Maintenance
Maintenance initiated from measured condition evidence and a defined response state rather than time alone.
Service Criticality
The importance of an asset or failure to customer service and related organisational consequences.
RCM
Reliability-centred maintenance, a method that selects tasks from required functions, failure modes, consequences and applicable controls.
FAQ

EE535 FAQ

What are the published assessment weights?

The course introduction assigns 20% to the assignment, 20% to the test and 60% to the examination. The three figures total 100%. The assignment separately allocates its internal marks across four tasks, but those internal marks do not alter the course-level percentage.

What examination or test format should I expect?

The current materials do not publish a duration, section structure, question format, coverage boundary, date or permitted-materials rule for the test or examination. Confirm these details on the current course site and revise transferable decision chains rather than relying on an assumed paper format.

What is the difference between ISO 55000, ISO 55001 and ISO 55002?

ISO 55000 gives overview, principles and terminology. ISO 55001 contains asset management system requirements. ISO 55002 provides guidance for applying those requirements. A requirement claim should therefore be tied to ISO 55001, while the shared language and principles come from ISO 55000.

Why is the SAMP important?

The SAMP connects organisational direction to asset management objectives and to the framework for asset plans, resources, decision criteria, responsibilities and review. Its value is traceable alignment. A polished document that cannot show how an asset intervention supports an objective has not performed that function.

Does installing a CMMS improve maintenance automatically?

No. Improvement depends on stable asset identity, clear ownership, controlled coding, usable workflow, mandatory close-out evidence and measures tied to decisions. Without those controls, software can centralise poor data and make inconsistency faster rather than make maintenance more effective.

How detailed should an asset hierarchy be?

It should be detailed enough to attach work and condition to the object that failed while still preserving the system and service context. Too broad a level hides repeat component faults; too fine a level fragments history. Start with the decisions and reports the hierarchy must support.

What makes a work-order closure useful?

A useful closure states what was observed, the cause found, the action taken, parts or resources used, the verification result and any residual condition or follow-up need. This structure allows later analysis to distinguish symptoms, causes and interventions rather than counting vague completed jobs.

How should risk and service criticality be used together?

Keep them distinct. Risk addresses consequence and occurrence evidence with a required treatment response, while service criticality highlights customer and operational importance. They may point in the same direction or differ. The recommendation should explain how each changes priority, control, assurance or investment.

Does RCM always lengthen maintenance intervals?

No. Reliability-centred maintenance reviews functions, functional failures, failure modes, consequences, evidence and applicable tasks. It may extend some intervals, retain others, shorten safety- or reliability-critical tasks, redesign an item or improve information. Selective change is the method; blanket extension is not.

Are the practice questions University questions?

No. The worked examples and practice items in this guide are independently authored for study. They are not past papers, sample examination questions, model answers or marking schemes issued by the University. Any marks shown are AskSia study allocations used to structure a complete response.

Chapter questions

Questions students ask in each EE535 chapter

Why can the lowest capital cost be the wrong choice?
Capital cost captures only one part of the lifecycle and may hide higher operating, maintenance, replacement or service consequences. It can also belong to an option that fails an interface or maintainability requirement. Screen for feasibility first, then compare totals on the same horizon and scope. Chapter 01 · Engineering Assets and Lifecycle Value
How is a stakeholder need different from an objective?
A need describes an outcome or expectation from a stakeholder perspective, such as dependable access. An objective translates that need and organisational direction into a measurable result with ownership and a horizon. The translation makes the need govern plans, priorities and performance review rather than remain a general aspiration. Chapter 02 · Stakeholders, Policy and Asset Objectives
Which ISO document contains requirements?
ISO 55001 contains asset management system requirements. ISO 55000 supplies overview, principles and terminology, while ISO 55002 offers application guidance. Keep those roles visible in any compliance, audit or improvement argument so the evidence carries the correct level of authority. Chapter 03 · ISO 55000 Framework and SAMP
What makes an asset management plan more than a project list?
It explains the objective, current state, evidence, option, timing, resources, responsibilities, measures and review logic for each intervention. That structure allows another person to understand why the work exists and what would change it. A project list shows intended activity but not controlled reasoning. Chapter 04 · Lifecycle Plans, Portfolio and Performance
Is corrective maintenance always poor practice?
No. It can be rational for visible, low-consequence failures with rapid restoration, available resources and adequate redundancy. It becomes weak when consequence is high, detection is delayed, restoration is slow or repeated failures impose avoidable cost. The choice needs controls and a review trigger. Chapter 05 · Railway Maintenance Operating Model
What is the core purpose of a CMMS?
Its core purpose is to provide a controlled information route for assets and maintenance work, connecting requests, plans, resources, execution, history and reporting. It supports decisions but does not make them automatically. Good use depends on defined ownership, stable identity and evidence-rich closure. Chapter 06 · CMMS Functions and Core Components
How deep should an asset hierarchy go?
Go to the lowest level that receives a meaningful maintenance, condition, failure, cost or replacement decision. Stop before creating objects that technicians cannot identify consistently or that never receive distinct control. Test the hierarchy against real work orders and reports before broad deployment. Chapter 07 · Asset Registers, Hierarchies and Chainage
What is the difference between a request and a work order?
A request reports or creates a need. Validation then confirms identity, scope, duplication, immediate controls and the appropriate route. A work order is the controlled, authorised record used for planning, scheduling, execution and closure. Treating every request as schedule-ready bypasses essential decisions. Chapter 08 · Work Orders from Request to Closure
Why separate long-range planning from weekly scheduling?
The long view exposes future workload, budget, competence and material needs, while weekly control resolves actual orders, people, parts and access. One without the other creates either strategy without execution or a busy schedule that conceals future capacity failure. Actuals should update long-range assumptions. Chapter 09 · Maintenance Scheduling, CBM and Field Service
What action belongs to each captured risk class?
R1 must be reduced except in exceptional circumstances. R2 must be reduced if reasonably practicable. R3 is tolerable but should be reduced when doing so is cost-effective. R4 is acceptable. R2 and R3 occupy the proportionality region described in the case. Chapter 10 · Risk, Criticality and RCM Decisions
Study strategy

How to study for the exam

Build one continuing asset case and revise through retrieval rather than rereading. First write the service outcome, four requirement classes and a lifecycle cost boundary. Next translate a stakeholder need into an asset objective and measure, then place the decision inside the ISO 55000 family and a SAMP route. Create a simple register and hierarchy, open one work order, plan its resources and write a complete closure.

Choose corrective, scheduled or condition-based treatment separately for each failure mode and explain the trigger. Finally classify consequence, service criticality and the reliability-centred decision without inventing numerical evidence. After each pass, cover the guide and reproduce the chain in five sentences: purpose, evidence, decision, verification and review.

Use the integrated practice case to expose missing links, then return only to the chapter that repairs that link. Confirm current assessment logistics on the course site because the available materials publish weights but not test or examination format.

Study EE535 with AI

Your AI Electrical Engineering tutor for EE535

Stuck on a hard EE535 question? Sia is AskSia’s AI Electrical Engineering tutor — ask any EE535 Maintenance and Reliability Engineering question and get a clear, step-by-step explanation grounded in how the course is actually taught and assessed. Read this whole study guide free, then take your hardest questions to Sia.

A+Everything unlocked
Unlocks this Bible + all 24 of your subjects at The Hong Kong Polytechnic University, plus 1,000+ more Bibles across the AskSia library.
Sia - your EE535 tutor, unlimited, worked the way the exam marks it
The full 47-page Bible + practice bank with worked solutions
Chrome extension - sync your LMS so Sia knows your deadlines
Bilingual EN / Chinese on every Bible and every Sia answer
$0.99 Trial
30-day money-back · cancel in one tap · how it works