Course 09: Project Engineering and Technical Integration

Series · Northbank case · Glossary · References

Purpose and preparation

Project engineering coordinates the technical whole. Discipline engineers produce competent contributions. The project engineer establishes how those contributions fit together and satisfy the project basis.

A sound component can become unsuitable in combination. A motor can match its supplier's data while mismatching the site supply. An accessible pump can become inaccessible after piping installation.

Complete Courses 01 to 08 before this course. Bring your project basis, source index, requirements, and execution package. Read Northbank Packets A, B, and C.

After this course, you can:

• Maintain a usable design basis across disciplines.
• Assign technical interface responsibilities.
• Examine supplier information against the project configuration.
• Coordinate construction, operation, and maintenance needs.
• Review the integrated result and propagate technical changes.

Lesson 1: Establish the technical basis

A design basis translates intended use into the conditions needed for technical development. It identifies requirements, operating cases, physical conditions, constraints, adopted decisions, and unresolved inputs.

Keep requirements distinct from assumptions and solutions. Northbank requires 18 litres per second at the distribution header under conditions the project must establish. A particular pump model is a possible solution.

The flow value alone cannot establish pump selection. The mechanical engineer needs suction conditions, required pressure, water properties, and relevant operating cases. Other disciplines need different parts of that same basis.

Identify the source and standing of each input. A checked observation establishes what the observer recorded within the survey's limits. A project approval establishes a commitment within the approver's authority.

A04 establishes a checked observation of the existing connection: 600 V, three phase, 60 Hz. It does not establish spare capacity or protection coordination. Keep those limitations with the value.

Manage open inputs at their point of need. State the decision they prevent, the owner, the required investigation, and the expected resolution. A permitted assumption remains unconfirmed until evidence resolves it.

Use this basis method:

1. Identify the technical decision to be made.
2. List its required conditions and requirements.
3. Locate the applicable sources.
4. Record each source's limitations.
5. Identify unresolved or conflicting inputs.
6. Define the work that can proceed on that basis.

Do not import an attractive value from an unrelated project. Similar equipment or familiar practice cannot establish the missing conditions.

Lesson 2: Allocate ownership across interfaces

An interface is a boundary where contributions interact. It can concern geometry, loads, power, signals, data, operating behavior, or responsibility.

A named discipline boundary does not define the exchanged contribution. “Mechanical to electrical” is too vague. “Selected motor rating and starting requirements” states something the consumer can use.

Give each interface a supplying owner and receiving owner. Identify the contribution, its conditions, point of need, and examination. Name the integration owner who resolves relationships across the whole result.

This is a proposed allocation for the teaching exercise. B03 supplies no accepted owners or required dates. The project must establish those assignments.

The supplying owner checks the contribution before issue. The receiving owner examines whether it meets the stated need. A document's arrival does not establish that the interface is satisfied.

Some design relationships are coupled. Motor selection affects the electrical design. The electrical conditions constrain motor selection. Manage the coupled decision as coordinated work.

Exchange bounded preliminary information when it can support authorized development. Mark its status, uncertainty, permitted use, and revision trigger. Do not let preliminary dimensions quietly become construction dimensions.

The project engineer coordinates resolution. Discipline responsibility remains with the appropriate engineer. Coordination does not grant competence or authority in every technical field.

Lesson 3: Review supplier information as project information

A brochure describes a product family. It may omit the selected model, accessories, ratings, materials, software, and operating cases. These omissions matter when dependent work requires the actual configuration.

Start review with the purchase requirements and identified submission. Compare the submission with the governing basis and required interfaces. Identify evidence that is absent, conflicting, or insufficient.

Check the submission's provenance. A supplier may have copied an outdated input. Repair the source relationship as well as the visible value.

Northbank B01 offers 480 V motors copied from A03. A03 is an archived reference without a field survey basis. A04 records the checked 600 V connection.

This discrepancy prevents an unsupported compatibility conclusion. The electrical engineer must assess the proposed configuration and relevant system conditions. Neither the project manager nor procurement can declare the mismatch resolved.

Supplier review outcomes need clear meaning. For example, a project can distinguish accepted for a stated purpose, revise and resubmit, and information only. Use the actual organization's definitions.

A review disposition should identify the configuration, reviewed scope, findings, conditions, and dependent release. An acceptance stamp without those relationships invites incorrect reliance.

Do not waive technical evidence to preserve a delivery slot. Explain the schedule effect and seek the appropriate decisions. Continue supplier questions and independent package preparation within authority.

C03 forecasts a corrected package and delivery timing. It supplies no corrected technical submission. The forecast therefore cannot serve as the missing pump curve or configuration list.

Lesson 4: Coordinate the whole life of the result

The installation must support construction, operation, and maintenance. Each activity can reveal requirements that component calculations miss.

Construction participants can identify access, lifting, sequencing, connection, and temporary-condition concerns. Operators can identify start, stop, changeover, alarm, and recovery needs. Maintainers can identify inspection, isolation, removal, and spare-part needs.

Invite those participants while change remains practicable. Give them the current basis and a concrete activity to examine. A general request to “review the design” often produces uneven coverage.

Use activity-based questions:

• How will the equipment reach its installed position?
• What must be available before connection work starts?
• How will an operator recognize the relevant abnormal condition?
• What information supports isolation and restart?
• Can the identified component be removed for maintenance?

Record the observation and affected requirement or interface. Assign resolution. Confirm the repair with the participant whose need it affects.

Control the relationship between design and installed configuration. Identify equipment, drawings, settings, software, and other items that define the result. Retain authorized changes and examination evidence.

A site substitution can affect several disciplines. A revised motor can change power requirements, controls, dimensions, and protection checks. Treat the substitution through technical and commercial change arrangements before dependent use.

Avoid duplicate configuration lists with different owners and values. Use an authoritative record with usable references. Document control distributes the right revision; technical owners establish its content and applicability.

Lesson 5: Examine integration and repair connected work

An integrated review examines relationships as well as parts. Start with the approved purpose, current configuration, and identified operating cases. Trace each required interaction across the relevant contributions.

Use both directions. Trace each requirement to its implementation and examination. Trace each implemented feature to an authorized need or decision. This can reveal missing scope and unintended additions.

For Northbank, trace standby behavior from operations' definition through equipment, controls, power, instructions, and planned examination. A complete mechanical drawing alone cannot establish that behavior.

Set the review purpose and competence before the session. Include independent examination where the project or consequences require it. Identify the exact candidate and source revisions.

State findings as observations or conclusions, with their supporting grounds. Distinguish an observed discrepancy from its interpretation. State the affected claim, evidence, consequence, owner, and closure evidence. “Please coordinate” does not identify a repairable defect.

After a change, inspect affected dependencies. Update the technical basis where meaning changes. Notify consumers through the controlled issue process. Confirm adoption in their actual work.

Re-examine the changed behavior and connected evidence. Preserve valid earlier checks where their basis remains unchanged. Do not repeat every check solely because a document received a new revision.

The integration owner closes a finding on evidence or a decision within the decision owner's authority. State whether the response corrects the result, changes the requirement, or limits the proposed reliance.

A disposition does not establish unexamined behavior. It cannot waive an obligation outside that authority. Moving a finding to another list does not satisfy the requirement.

Worked Northbank example

The project engineer prepares a technical release account using A02 Rev 1, A04 Rev 1, B01 Rev 0, and B03 Rev 0.

The account does not conclude that the selected equipment is suitable. No complete selected configuration exists in the supplied packet. A06 also leaves legal applicability open.

The team can prepare review criteria, an interface schedule, and supplier questions. It can arrange the missing investigations. Final selection-dependent release needs the required evidence and decisions.

Suppose a colleague says, “The corrected forecast solves the voltage problem.” The project engineer points to C03's status and content. It forecasts package timing and cost. It does not identify an accepted electrical configuration.

The resulting technical issue stays open. Its owner and point of need become explicit. The schedule receives the real release condition instead of an assumed technical approval.

Transfer example: equipment-room renovation

A ventilation unit can meet its catalogue rating and still fail the room's intended activity. Electrical load, structural support, airflow paths, controls, access, and maintenance interact.

Assign those interfaces before purchase and construction. Examine the combined operating conditions. Trace a changed unit through every affected contribution.

The specific calculations require competent discipline work. Project engineering makes their relationships and examination visible.

Practice

Use A01 to A06, B01 to B03, and C03. Use the exact revisions supplied in the case.

Prepare these outputs:

1. Prepare a technical basis table with sources and unresolved inputs.
2. Assign proposed owners to six Northbank interfaces.
3. Draft five supplier questions that request usable project information.
4. Prepare an integrated review agenda for one construction activity, one operating activity, and one maintenance activity.
5. Trace the effects of a proposed motor substitution across affected work.

Do not invent a selected motor, pump curve, adopted code, or technical approval. Name the work and decisions needed to establish them.

Knowledge check

1. Why is Northbank's flow requirement insufficient for pump selection?
2. What does A04 establish, and what does it leave unresolved?
3. What information turns B03's interface names into usable assignments?
4. Why does a product brochure fail to establish a complete project configuration?
5. How can operations and maintenance review improve design before construction?
6. What must happen after an authorized substitution changes several interfaces?

Assessed assignment

Prepare a technical coordination package for Northbank's existing scope. Include the basis, interface assignments, supplier review position, activity reviews, and a substitution impact route.

Use these five observable criteria:

1. The basis preserves requirement, observation, proposal, and unresolved-input distinctions.
2. Each selected interface has a supplier, consumer, contribution, point of need, and examination.
3. The supplier review identifies configuration gaps without inventing suitability or approval.
4. The activity reviews cover construction, operation, and maintenance relationships.
5. The change route carries consequences into consumers, configuration records, and affected examination.

Explain one interface to both its proposed supplier and consumer. Revise it until both can identify the same required contribution.

Portfolio continuation and reading

Connect your interface package to Course 08's readiness conditions. Carry the current configuration and open findings into Course 10's assurance plan.

Read Field Book §§4–7 and Consolidated v8 §§5.5–5.10 in References. Their dependency, integration, and evidence principles support this course.

The optional NASA technical management readings offer further methods. The Northbank records supply the core exercise basis. NASA's agency procedures do not govern this fictional project.