GID 96 Code Structure
11.8 DEVELOPING THE PROJECT PLAN
RFID Project Management 143
If.a.third.level.were.utilized,.it.would.be.annotated.with.a.second.digit..For.example,.a.particu- lar.type.of.equipment.specification.might.be.represented.by.the.number.4.1.1.identify.RFID.tags..
Another.type.of.equipment.specification.would.be.represented.by.4.1.2.identify.RFID.reader.
The.level.of.planning.in.some.projects.is.so.detailed.that.the.division.of.tasks.into.subtasks.con- tinues.until.the.point.at.which.a.single.work.package.is.reached..A.work.package.is.a.discrete.unit.
of.work.for.which.authority.and.responsibility.can.be.assigned.
11.8.2 LIneAR ResponsIBILIty chARt
Most.business.entities.utilize.an.organizational.chart.to.some.extent..Even.though.a.trendy.organi- zation.may.deny.the.existence.of.such.a.chart,.there.will.still.be.some.sort.of.organizational.frame- work.in.place..These.charts.will.depict.a.hierarchical.relationship.between.organizational.different.
divisions.and.personnel..While.these.types.of.charts.may.be.of.some.value,.an.RFID.project.is.in.
need.of.a.type.of.chart.that.illustrates.the.relationship.between.an.activity.on.the.WBS.and.the.dif- ferent.individuals.involved.in.the.project.
This.type.of.chart.is.commonly.known.as.an.LRC..The.LRC.shows.who.participates.in.each.
activity.and.to.what.degree..For.example,.there.may.be.a.number.of.individuals.involved.in.collect- ing.data,.but.only.one.individual.holds.primary.responsibility.for.completing.the.activity..The.LRC.
can.be.superimposed.on.the.existing.WBS.as.an.x-axis.going.horizontally.across.the.chart..Across.
the.top,.each.individual’s.name.or.title.is.listed..There.is.an.intersection.between.the.vertical.WBS.
tasks.and.the.horizontal.project.personnel.designations..At.each.of.these.intersections,.the.project.
manager.can. place.a. code.corresponding.to.the.individuals’.level.of.participation..Although.the.
RFID.implementation.project.manager.may.choose.any.codes,.the.following.codes.are.commonly.
employed:
•. P.=.Primary.responsibility
•. S.=.Secondary.responsibility
•. W.=.Worker
•. A.=.Approval
•. R.=.Review
Primary.responsibility.means.that.the.individual.has.the.primary.authority.and.responsibility.for.
completing.that.work.package..Secondary.responsibility.is.assigned.as.a.backup.to.the.individual.
with.primary.responsibility..If.utilized.in.the.chart,.W.means.that.the.individual.is.to.assist.the.
primary.responsibility.individual.with.completing.the.task..Approval.involves.going.over.the.end.
results. of. the. task. and. providing. feedback. to. the. primary. responsibility. individual.. Review,. if.
utilized,.may.involve.that.individual.reviewing.the.results.for.possible.effects.on.other.ongoing.
activities..Not.all.tasks.are.so.complex.that.both.a.primary.and.secondary.responsibility.individu- als.are.required..In.addition,.if.an.individual.is.not.involved.in.a.particular.task.at.all,.that.inter- section.is.simply.left.blank.
The.following.table.illustrates.the.use.of.an.LRC.with.the.previously.existing.WBS.
WBS Activity Eng. Mgr. Eng. 1 Eng. 2 Eng. 3
1.0. Problem.formulation 1.1. Orientation 1.2. Problem.statement 1.3. Objectives 2.0. Project.planning
2.1. Work.breakdown.structure 2.2. Linear.responsibility.chart 2.3. Gantt.chart
RFID Project Management 145
(continued)
WBS Activity Eng. Mgr. Eng. 1 Eng. 2 Eng. 3
3.0. System.definition
3.1. .Identify.RFID.components.requirements 3.2. Identify.layout.of.RFID.system 4.0. Equipment.specification
4.1. .Identify.specific.equipment.that.meets.
system.needs
4.2. Acquire.identified.equipment 5.0. Pilot.implementation
5.1. Installation.of.pilot.system 5.2. Testing.and.debugging 6.0. Full-Scale.implementation
6.1. Installation.of.full.system 6.2. Testing.and.debugging 6.3. Operator.training
Note.how.in.this.case,.the.engineering.manager.wants.to.approve.everything..Engineer.1.is.mostly.
responsible.for.planning.and.control.issues..Engineer.2.is.good.at.installing.hardware..Engineer.3.
must.be.junior.to.engineers.1.and.2,.as.well.as.a.skilled.trainer.
11.8.3 gAntt chARt
A.Gantt.chart.illustrates.the.duration.and.relationship.between.different.project.activities..The.dura- tion.of.individual.tasks.is.represented.by.horizontal.bars..The.relationships.between.activities.are.
illustrated.by.connecting.lines.with.arrows.between.the.dependent.activities..With.an.RFID.project,.
the.Gantt.chart.can.be.appended.to.the.right.of.the.LRC.or.interchanged.with.the.LRC.if.presenta- tion.space.is.at.a.premium..This.enables.the.RFID.project.manager.to.identify.the.task,.individuals.
involved,.duration,.and.task.relationships.at.a.glance.
Project. tasks. may. have. what. are. known. as. relationships.. These. are. connections. between. the.
tasks,.which.dictate.what.sequences.must.be.observed.between.a.preceding.task.and.a.succeeding.
task..Common.relationships.include
•. Finish.to.start
•. Start.to.start
•. Finish.to.finish
11.8.3.1 Finish-to-Start Relationship
The.most.common.relationship.is.the.finish-to-start.relationship..In.the.finish-to-start.relationship,.
it.is.necessary.for.the.preceding.task.to.finish.before.the.succeeding.task.may.start..This.type.of.
relationship.occurs.in.an.RFID.project.when.attempting.to.test.the.system..For.example,.in.order.to.
perform.a.startup.test.the.system,.it.is.necessary.to.first.install.both.the.hardware.and.the.software.
Under.most.circumstances,.the.only.way.to.reduce.the.overall.time.for.a.finish-to-start.predeces- sor.and.a.successor.is.to.reduce.the.individual.time.of.either.the.predecessor.or.successor.or.both..If.
the.tasks.could.be.performed.in.parallel,.then.the.relationship.would.not.be.finish.to.start.in.the.first.
place..A.finish-to-start.relationship.is.represented.by.an.arrow.that.leaves.the.rightmost.part.of.the.
predecessor.and.enters.the.leftmost.part.of.the.successor.
11.8.3.2 Start-to-Start Relationship
Less.common.than.the.finish-to-start.relationship.is.the.start-to-start.relationship..The.start-to-start.
relationship.means.that.the.predecessor.and.the.successor.must.start.at.the.same.time..This.sort.
of.situation.may.occur.when.a.single.previous.process.splits.into.two.different.tasks,.which.must.
be.worked.on.simultaneously..In.an.RFID.project,.this.type.of.relationship.can.appear.when.the.
RFID.hardware.components.are.identified..The.RFID.tags,.readers,.and.antennas.can.be.ordered.
simultaneously..It.will.often.be.desirable.to.begin.working.on.a.number.of.tasks.as.soon.as.possible,.
but.it.is.not.absolutely.positively.necessary.to.have.any.start-to-start.relationships..The.start-to-start.
relationship.is.represented.by.two.or.more.arrows.feeding.into.the.leading.edge.of.the.Gantt.chart.
task.bars.
11.8.3.3 Finish-to-Finish Relationship
A.finish-to-finish.relationship.between.a.predecessor.and.a.successor.is.found.when.both.tasks.are.
desired.to.be.completed.at.the.same.time..This.means.that.if.the.tasks.are.of.different.duration,.
then.the.longer.duration.task.must.be.started.before.the.shorter.duration.task..The.finish-to-finish.
relationship.is.most.often.found.in.situations.where.there.is.some.sort.of.limited.life.associated.with.
different.processes.that.must.be.combined.in.a.following.task.at.the.same.time..This.situation.is.not.
necessarily.going.to.exist.in.an.RFID.project..The.finish-to-finish.relationship.is.represented.by.two.
arrows.exiting.the.Gantt.chart.task.bars.
11.8.3.4 Lags
A.possible.variation.to.the.above.relationships.is.the.concept.of.a.lag..A.lag.is.a.required.time.period.
between.the.predecessor.and.the.successor..For.example,.it.may.be.desirable.to.begin.testing.the.
functioning.of.RFID.tags.as.soon.as.possible.after.acquiring.the.tags..In.order.to.begin.the.testing,.
it.is.necessary.to.actually.have.the.tags.to.test..However,.all.of.the.tags.may.not.necessarily.be.avail- able.for.testing.at.the.same.time.due.to.shipment.issues..In.this.situation,.the.project.manager.may.
decide.that.it.is.more.important.to.wait.for.all.of.the.tags.to.arrive.before.beginning.testing..Thus,.for.
project.planning.purposes,.there.could.be.a.small.lag.between.these.two.tasks..Similarly,.it.would.be.
expected.that.the.tag.testing.processes.finish.somewhat.behind.the.tag.acquisition.process.