IDEF a comprehensive modelling methodology for the development of manufacturing enterprise

IDEF*:acomprehensivemodellingmethodologyforthedevelopmentofmanufacturingenterprisesystems

ANGCHENG-LEONG{{,KHOOLIPHENG}andGAYROBERTKENGLENG{

Tocompletelydescribeamanufacturingsystem,severalmodelsareusuallycre-ated,eachfromadi󰁎erentviewpoint.Traditionally,thesemodelswerecreatedindependentlyusingdi󰁎erentmethodologiesandindi󰁎erentenvironments.Thisapproachposesmanyproblems,forexample,time-consumption,incompatibilitybetweenmodels,di󰁏cultiesinmodelmaintenance,di󰁏cultiesinensuringaseam-lesstransitioninthesystemdevelopmentlifecycle,etc.Toovercometheseprob-lems,acomprehensivemodellingmethodologyanditssupportingsoftwaretoolhavebeendevelopedatGintic.Themethodology,termedIDEF*,isCIMOSA-compliant,IDEF0-based,andintegrated.Thepurposeofthispaperistointro-ducetothereadersthesefeaturesofthemethodology,andthestructureandcomponentsofthesoftwaretool.

1.Introduction

Modelsaredescriptionsofsystems.Tocompletelydescribeamanufacturingenterprisesystem,severalmodelsareusuallycreated,eachfromadi󰁎erentview-point.AccordingtoCIMOSA(CIMOpenSystemArchitecture)referencearchitec-ture(AMICE1993),manufacturingenterprisesystemscanbeviewedfromatleastfourcomplementaryviewpoints:function,information,resource,andorganisation.Unfortunately,inpractice,modelsfromeachviewpointarebuiltindependentlyusingdi󰁎erentmethodologiesandindi󰁎erentenvironments.However,amethod-ologytailoredtoaparticularviewpointmaybeincompatiblewithanother.Thistraditionalapproachthusposesthefollowingproblems.

(a)Thewholemodellingprocessinvolvesrepeatedcapturingofthesameinfor-mationandistime-consuming(Wangetal.1993).

(b)Itisverydi󰁏culttoidentifythee󰁎ectofchangestoonemodelontheothers

(Kim1996).

(c)Incompatibilitybetweenthedi󰁎erentbutinterrelatedmodels(Wangetal.

1993).

(d)Modelmaintenanceisdi󰁏cultbecauseof(b).

(e)Seamlesstransitioninthesystemsdevelopmentlifecycleisdi󰁏cultbecauseof

(c)(Kim1996).

RevisionreceivedDecember1998.

{GinticInstituteofManufacturingTechnology,71NanyangDrive,Singapore638075.}SchoolofMechanicalandProductionEngineering,NanyangTechnologicalUniversity,NanyangAvenue,Singapore639798.

{Towhomcorrespondenceshouldbeaddressed.e-mail:clang@gintic.gov.sg

InternationalJournalofProductionResearchISSN0020±73print/ISSN1366±588Xonline

http://www.tandf.co.uk/JNLS/prs.htmhttp://www.taylorandfrancis.com/JNLS/prs.htm

#

1999Taylor&FrancisLtd

3840AngC.-L.etal.

(f)Itisdi󰁏cultforsystemusersandsystemdeveloperstocommunicateand

worktogether(Kim1996).

(g)Similarly,itisdi󰁏cultforseveralsystemdeveloperswhohavedi󰁎erentpur-posesandbackgroundsbutwhoareworkingonthesamesystemtocommu-nicateandworktogether(Kim1996).AccordingtoCIMOSArecommendations,acomprehensivemodellingmethodologytermedIDEF*anditssupportingsoftwaretoolhavebeendevelopedatGintictoovercometheseproblems.Thepurposeofthispaperistoexplainthefeaturesandconceptsofthemethodology,andtodescribethestructureandcomponentsofthesoftwaretool.

ThemethodologyistermedIDEF*becauseitisanenhancementoftheIDEF(ICAMDEFinitionlanguage)methodologydevelopedbytheUSAirForce’sICAM(IntegratedComputer-AidedManufacturing)programmeinthe1980sforCIM(Computer-IntegratedManufacturing)andimplementation.TheIDEFmethod-ologycomprisesIDEF0(USAF1981a),IDEF1(USAF1981b),IDEF2(USAF1981c),andIDEF3(Mayeretal.1992)whicharemethodologiesforfunctional,information,dynamic,andprocessmodelling,respectively.TherearetwoversionsofIDEF1:IDEF1(1981)(USAF1981b)andIDEF1x(1986)(Bruce1992,Loomis1986).IDEF1isusedforrequirementsspeci®cation,whileIDEF1xisusedforthedesignofrelationaldatabases.

2.

TheIDEF*methodology

ThemainfeaturesoftheIDEF*methodologyarethatitis:CIMOSA-compliant;IDEF0-based;andintegrated.2.1.

CIMOSAcompliance

TheIDEF*methodologyconformstotheCIMOSAmodellingframework(AMICE1993),whichisadiagrammaticrepresentationofthreemodellingdimen-sions(®gure1).Inonedimension,modellingisdescribedasconsistingofgeneric,partial,andparticularlayers.Inanotherdimension,modellinghasfunction,infor-mation,resource,andorganisationviews.Finally,inthethirddimension,modellingisdescribedashavingrequirementsde®nition,designspeci®cation,andimplementa-tiondescriptionlevelsofdevelopment.Thecombinationofeachofthesethreedimensionsresultsin36di󰁎erentmodellingdomainsCx;y;z(wherex;zˆ1;3;andyˆ1;4)andmanypossible`routes’forenterprisesystemdevelopment.TheIDEF*methodologysupportsthefollowingroutewhichconsistsoffoursectionsandisthoughttobeoneofthe`shortest’intermsofdevelopmente󰁎ort.(i)(ii)(iii)(iv)

C2;1;1!C3;1;1!C2;1;1;!C3;2;2!C3;1;2!C3;3;2!C3;1;2!C4;3;2!

C3;1;2!C3;1;3C3;2;3C3;3;3C3;4;3

Thedevelopmentrouteisbasedonthefollowing:

(a)thewaterfallsystemdevelopmentlifecyclemodelwhichischaracterisedbya

formalsign-o󰁎foreachphasebeforeworkcommencesonthenextphase(Brumbaugh1994,TkachandPutttick1994);

IDEF*modellingmethodology

Organisation Resource3841

Information Function C3,4,2 Y + Generic Partial Particular C3,3,2 X C3,1,1 + Requirements C2,1,1 C3,1,1 C3,2,2 C3,4,3 Definition C3,3,3 + Design CX,Y,Z C3,1,2 C3,1,2 Z Specification C3,2,3Implementation C3,1,3 Description C3,1,3Figure1.CIMOSAmodellingframework.

(b)thepremisethattheinformationsystemofamanufacturingenterpriseaswell

asitsresourcesandorganisationmustsupportitsbusinessprocesses(Vernadat1996).Section(i)ofthedevelopmentrouteinvolves:

(a)customisingapartialfunctionmodelintoaparticularfunctionmodelatthe

requirementde®nitionlevel;

(b)extendingtheparticularfunctionmodeltoenablevisualandcomputerwork-¯owanalysisatthedesignspeci®cationlevel;

(c)furtherextendingtheparticularfunctionmodeltoenablecomputerwork¯ow

executionattheimplementationdescriptionlevel.Section(ii)involvesthederivationofaparticularinformationmodelfromtheparticularfunctionmodelatthedesignspeci®cationlevel,andthedesignofrela-tionaldatabasesattheimplementationdescriptionlevel.Sections(iii)and(iv)involveextendingtheparticularfunctionmodeltoincluderesourceviewandorgan-isationview,respectively,atboththedesignspeci®cationlevelandtheimplementa-tiondescriptionlevel.2.2.

IDEF0-based

IDEF0ischosenasthebasisofIDEF*.Inproducingacompletesystemdescrip-tionmodel,anIDEF0modelisrstbuiltandotherdetailsarethenaddedprogres-sivelytotheIDEF0modelsothat:

(a)functionaldescriptionofthesystemcanbeachievedatanylevelofabstrac-tion;

(b)completesystemdescriptioncanberealisedsequentially;

3842AngC.-L.etal.

(c)modelcompatibilitycanbemaintainedbyusingthesamefunctionsamong

thedi󰁎erentmodels.Throughouttheprocess,theIDEF0modelisusedasthebasisforthecollectionofrelevantdetails.ThishelpstoensurethatmodelsresultingfromtheprocesswillbecompatiblewiththeIDEF0model,andthatonlyfunction-relateddetailsarecol-lected.Thisisincontrastwiththetraditionalapproach,asmentionedinsection1.ThreemainreasonsforchoosingIDEF0asthebasisofthismethodologyarethat:itisoneofthefewfunctionalmodellingmethodologiesthatarepopularwiththeindustrialcommunity(Feldmann1998);itissuperiortomanyotherfunctionalmodellingmethodologiesintermsofsimplegraphics,conciseness,rigorandpreci-sion,consistentmethodology,levelsofabstraction,andseparationoforganisationfromfunction(Hunt1996,Mandel1990);itisinfactadefactointernationalstan-dard,andaUSFederalInformationProcessingstandard(FIPS1993)forfunctionalmodelling.2.3.

Integration

IDEF*isintegrated,meaningthatitachievesfourkindsofmodellingintegration:(a)integrationofvemodelingviews:function,dynamics,information,

resource,andorganisation;

(b)integrationofthreemodelinglevels:requirementsde®nition,designspeci®-cation,andimplementationdescription;

(c)integrationofthreemodelinglayers:generic,partial,andparticular;(d)integrationofenterpriseengineeringandenterpriseoperation.

Thersttwokindsofintegrationareachievedthroughanintegratedmodellingapproachinwhichthedi󰁎erentmodellingprocessessharecommoninformationontheenterprisesystembeingmodelled(seesections3and4).Theapproachwillnotonlyhelptoensurecompatibilitybetweenthedi󰁎erentmodels,butwillalsohelptoreducethetimeande󰁎ortneededtobuildandmaintainthem.Itwillalsoallowsystemusersandsystemdeveloperstoworktogethermoreeasilythanwhenusingmodelsthatarebuiltindependently(Kim1996).

Thethirdkindinvolvestheuseofaknowledge-basedsystemtosemi-automatethegenerationofIDEF0modelsbasedontheconceptofreferencemodels(Angetal.1997)(seesection5).Theknowledge-basedapproachwillhelptoreducemodellingtimeande󰁎ort,andeliminatemodelinconsistency(Luo1998).

Finally,thelastkindisachievedbyextendingtheIDEF0modeltoincludeotherdetails,makingitcomputer-processablenotonlyforwork¯owanalysis(simulation)(Wangetal.1993),butalsowork¯owexecution(Ang1999,ZukunftandRump1996,Johnson1992)(seesections3.2and6).Suchintegrationwillhelptoreducethetimeande󰁎ortofbothsystemdevelopmentandsystemmaintenance.Anychangestosystemoperationscannowbee󰁎ectedsimplybychangingtherelevantpartsoftheextendedIDEF0modelwhichismucheasierthanchangingdirectlythecontrollersoftware.

3.

Integrationofmodellingviews

ThisisachievedthroughanintegratedmodellingapproachinwhichIDEF0ischosenasthebasisofmodelling.ThusanIDEF0modelisrstbuiltandotherdetailsarethenaddedprogressivelysothatacompletesystemdescriptioncanberealisedsequentially.Toful®ltheserequirements,IDEF0isextendedsyntacticallyand

IDEF*modellingmethodology3843

textuallysoastobeabletoaccommodatemodellingfromalloftheveviewpoints(seesections3.1,3.2,3.4and3.5).3.1.

Integrationoffunctionviewwithprocessview

TofacilitatevisualanalysisforBPR(BusinessProcessRe-engineering),IDEF0isextendedsyntacticallysothatitcanalsobeusedtodescribethetemporalprecedencerelationshipsbetweenfunctionalactivities.Heretheprecedencerelationshipsaremodelledwithprecedencelinks(boldarrows)whichconnectfunctionalactivitiesbymeansofAND(&),OR(OR),andExclusiveOR(XOR)junctionboxes(seetable1).Figure2showsanIDEF0diagramanditscorrespondingIDEF0*diagramshowingtheprecedencelinks.

IntheIDEFmethodology,IDEF3(PFD)(theprocess¯owdescriptioncompon-entofIDEF3)(Mayeretal.1992)isintroducedtodescribecontrol¯owwithinabusinessprocess.ItspurposeistocomplementIDEF0,whichisusedtodescribefunctionality,andtosupplementIDEF2,whichisusedtodescribetime-varyingbehaviour.Table2showsthatIDEF0*hasallthefeaturesofIDEF3(PFD).InIDEF0*,alltheinterfacesotherthanprecedencelinkscanbetreatedastherelationallinksofIDEF3(PFD).

A11 A123 A13IDEF0 Diagram A14 OR A11 & A12 OR & Control FlowA13 IDEF0* DiagramA14Figure2.IDEF0andIDEF0*diagrams.

3844

JunctiontypeSynchronisationtypeAngC.-L.etal.

Representation & ANDDescriptionAll preceding processes must becompleted before proceeding forward.Asynchronous OR ORJOINT & ANDOne or more of the preceding processeswill complete.All preceding processes will completesimultaneously.Synchronous OR OR XOR Exclusive OROne or more of the preceding processeswill complete simultaneously.Exactly one of the preceding processeswill complete.All following processes must start. & ANDAsynchronous OR OROne or more of the following processeswill start.SPLIT & ANDAll following simultaneously.processes will startSynchronous OR OROne or more of the following processeswill start simultaneously. XOR Exclusive ORExactly one of the following processes willstart.Table1.IDEF0*junctiontypes(Vernadat1996).

Also,tofacilitatevisualanalysisforTQM(TotalQualityManagement),distinc-tionismadeinIDEF*betweencontrolandauthority,andbetweenthepersonwhoownstheprocessandtheperson(s)whoexecute(s)theprocess.ThepersonwhoexecutesaprocessisaresourcetermedFunctionalityEntityinCIMOSA.Therea-sonsformakingthedistinctionsaregivenbyBorn(1994).IDEF*canthusbeusedtodescribebothbusinessandqualityprocesses,andanIDEF0*diagrammayshow,inadditiontotheAND,OR,andXORjunctionboxes,sevenbasicelements(seegure3)asde®nedbelow.

(a)Process:aseriesofstepsoractionsthattransformanobjectÐfromaninitial

state(input)toanalstate(output).

(b)Processowner:thepersonorotheragentresponsiblefortheexecutionofa

process.

IDEF*modellingmethodology

Control Authority3845

Input OutputProcessProcess Owner/Organisation Cell Mechanisms

Figure3.IDEF0*processnotation.

IDEF0* Relational PrecedenceIDEF3 (PFD)Links Precedence Relational AND, OR, XORJoin/Split logicHierarchyTextGlossaryAND, OR, XORHierarchically decomposed diagrams.Text for each diagram.Glossary of terms used in diagrams.Hierarchically decomposed diagrams.Text for each diagramGlossary of terms used in diagrams.Table2.ComparisonofIDEF3(PFD)andIDEF0*.

(c)Authority:thedescription,speci®cationorjusti®cationofaprocess.Itis

shownenteringtheprocessboxatthetopright.

(d)Control:theconditionsforactivatingaprocess.Itisshownenteringthe

processboxatthetopleft.

(e)Input:anobjectatthepointofentrytoaprocess.(f)Output:anobjectatthepointofexitfromaprocess.(g)Mechanisms:theresourcesusedtoexecutetheprocess.3.2.

Integrationoffunctionviewwithdynamicview

Tofacilitateperformanceanalysis,dynamicsinformationisincorporatedintotheIDEF0modelintheformoftextlesattachedtotherelevantboxesorarrows,andcontainedwithintheTextofthemodel(Ang1999).ThishastheadvantageofnotfurthercomplicatingthealreadycomplicatedIDEF0diagrams.Suchdynamicsinformationasarrivalrate,branchingconditionsorbehaviourrules,processingtime,delaytime,etc.,canbeincorporated.Inordertobeabletohandleproblemsofparallelactivitiescompetingforresourcesorproblemsofsimilarresourcescom-petingforactivities,resourceallocationrulesandselectionrulesarealsoincorpo-

3846AngC.-L.etal.

MeanFlow timeDurationMaxMinTimeEventRequiredCapabilityBehaviour RulesTemporal RulesException Rules Inter-arrival Flow time ti me Order Control Flow time Input (Information)Flow time Output (Information)EnterpriseActivity Input (Material) Flow timeOutput (Material) Resource TypeQuantityCapacitySelectionRulesAllocationRulesFlow timeFigure4.InputtingdynamicinformationintoIDEF0modelsbymeansofpop-upboxes.

rated.Theformergoverntheallocationofagivenresourcetoanactivity;whilethelattergoverntheselectionofaresourcetypeforaparticularactivityfromtwoormoreresourcetypes.Theresultingmodel,whichisanIDEF0-basedIDEF2dynamicmodel,canbesimulatedforwork¯owanalysis(Ang1999,Wangetal.1993).

InthesoftwaretooldevelopedforIDEF*,dynamicsinformationisinputbymeansofpop-updialogueboxesthatappearonthecomputerscreenwhentherelevantfunctionboxesorarrowsaredouble-clickedon(seegure4).3.3.

Integrationoffunctionviewwithdataview

TheIDEF0modelofabusinessdescribesthefunctionsperformedbythebusi-nessprocessandtheirinterfaces,namelyinputs,outputs,controlsandmechanisms.Althoughtheseinterfacescanbeinformationorphysicalobjects,theyarerepre-sentedonlyatthelevelofgraphicallabelsandnoactualinformationstructuresareattachedtothoselabels.AnIDEF1xmodelofthebusinessprocessontheotherhandgraphicallyrepresentstheinformationcontentandstructurerelatedtoabusi-nessprocessoranenterprisesystem.However,accordingtoLeClair(1982)andSmartetal.(1996),itispossibletoderiveanIDEF1xmodelfromanIDEF0modelbyusingtheGlossaryoftheIDEF0modelastheentitypoolforIDEF1x.Apre-requisiteisthattheIDEF0modelmustbeofsu󰁏cientdetailtoenableallofthepossiblecandidateattributesandentitiestobeidenti®ed.

AprocedureforthesystematicderivationofIDEF1xmodelsfromIDEF0modelshasbeenadaptedfromtheworkofAdamandGanopadhyay(1993),Smartetal.(1996),andCarswellandNavathe(1987)bytheauthors(Angetal.1997a).HeretheGlossaryofIDEF0isextendedtoincludecross-referencestotherelevantsourcematerialsforIDEF1x.ThepurposeistoavoidhavingtodecomposeanIDEF0modeltoaveryhighlevelofdetailinordertoensureacompleteentitypoolforIDEF1x.

IDEF*modellingmethodology

Capability SetDesign Authority:

Capabilities

Function Related:Performance related:Objective related:

[Name of person with authority to design/maintainthis particular Capability Set].[Capability elements][Capability elements][Capability elements]

3847

ResourceDesign Authority:Capability Set:Class:Operation Set:Object View:

[Name of person and department with authority todesign/maintain this particular instance]

[Name of Capability Set defining the providedcapabilities of this Resource instance]

[Functional Entity or Resource Cell or Resource Setor Resource Component]

[Functional operations valid for this Resourceinstance]

[Name of Object View instance defining thecharacteristics (capacity, availability, location, etc.)of this Resource instance]

Figure5.Descriptiontemplatesforresourcemodelling.

TheprocedureinvolvesbuildinglocaldatamodelsforthevariousactivitiesoftheIDEF0modelandmergingthemsystematically,activitybyactivityandlevelbylevel,intoaconsistentglobaldatamodel.Tosupporttheprocedure,asoftwaretoolhasbeendevelopedandintegratedintothesoftwaretoolforIDEF*(Angetal.1997a).3.4.

Integrationoffunctionviewwithresourceview

InIDEF*,asinCIMOSA,thetermresourceisrestrictedtomechanismsintheIDEF0sense(Vernadat1996).Forresourcemodelling,thedescriptiontemplatesofthetwoCIMOSAmodellingconstructs,namelyCapabilitySetandResource,areused(AMICEConsortium1993)(seegure5).TheCapabilitySettemplateisusedtodescribetherequiredcapabilitiesofanactivity,whiletheResourcetemplateisusedtodescribetheresourceassignedtothatactivity:thecapabilitiesito󰁎ersandwhereitisintheresourceorganisation.IntheIDEF*softwaretooldeveloped,thetwotemplatesareattacheddirectlytotheIDEF0boxesandareaccessedbymeansofdialogueboxes.TheresultingresourcemodelsarethusIDEF0-based.3.5.

Integrationoffunctionviewwithorganisationview

OrganisationmodellinginIDEF*makesuseofthedescriptiontemplatesoftwootherCIMOSAmodellingconstructsÐOrganisationUnitandOrganisationCell(AMICE1993)(seegure6).AccordingtoCIMOSA,anOrganisationUnitisanorganisationelementde®nedbyitslistofskills,responsibilitiesandauthorities,intheorganisationstructure.Ontheotherhand,anOrganisationCellisanaggrega-tionofOrganisationUnitsand/orotherOrganisationCellstodescribeanorganisa-tionalareaoftheorganisationstructure.Again,intheIDEF*softwaretool,thetwotemplatesareattacheddirectlytotheIDEF0boxesandaccessedbymeansofdia-logueboxes.

3848

Organisation Unit

Design Authority:

AngC.-L.etal.

[Name of person and department with authority to design/maintain thisparticular instance]

Function DescriptionFunctional Entity:Job Unit Description:Skill profile:Responsibilities:Authorities:

[Name of functional entity associated to this organizationunit]

[Textual description of the decision-making or problem-solving job][List of capabilities/skills that are needed to fulfill the job][List of responsibilities given to this organization unit][List of authorities necessary to fill the job]

Structural DescriptionAssigned to

organisation cell:

[Name of organization cell to which the organization unitbelongs]

Organisation Cell

Design Authority:

[Name of person and department with authority to design/maintainthis particular instance]

Function DescriptionCell Description:OperationalAuthority/

Responsibility:ProcessAuthorities/

Responsibilities:InformationAuthorities/

Responsibilities:ResourceAuthorities/

Responsibilities:Organisation Level:

[Textual description of the purpose of the organization cell]

[Organization unit responsible for the organization cell. Mustbe a person]

[List of function view constructs on which this organizationcell has responsibility and authority]

[List of information view constructs on which this organization cell hasresponsibility and authority]

[List of resource view constructs on which this organizationcell has responsibility and authority]

[One of : “Enterprise”, “Plant”. “Shop”, “Cell”, “Workcenter”,or “Equipment”]

Figure6.Descriptiontemplatesfororganisationmodeling.

TheIDEF0-basedorganisationmodelthuscontainssu󰁏cientinformationfortheconstructionofanorganisationmatrix(®gure7).Tofacilitateorganisationalanalysis,IDEF*isfurthersupplementedbythefollowingfourmatrices(®gures8(a)±8(d)).Thesematrix-basedmodelscompensateforoneofthebiggestdrawbacksofIDEF0,whichistheimpossibilityofautomaticallyanalysingandprocessingtheenclosedinformation.

IDEF*modellingmethodology

Tom3849

NelsonHarryGeorgeJohnWilley Staff Authority Line AuthorityKelvinPeter(a)

SubordinateGeorgeJohnXXTomTomNelsonHarryGeorgeJohnWilleyNelsonXHarryXWilleyXKelvinPeterSuperiorYXX X - Line Relationship Y - Staff Relationship

(b)

(a)Organisationchart;(b)organisationmatrix.

Figure7.

(a)Resource/Activitymatrix(®gure8(a)):thisshowswhichactivitiesareper-formedbyeachmemberoftheorganisation.Analysisofthematrixmakesitpossibletoidentifyexcessiveorinsu󰁏cientworkloadscastuponpeopleaswellasactivitiesinwhichtoofew(ortoomany)resourcesareinvolved.Processingthisincidencematrixalsoenablesclustersofresourcesandactiv-itiestobefound,thussupportingtheformationofworkgroups.ThisisanalogoustothewayinwhichmachinesandpartsaregroupedtogetherinProductionFlowAnalysis(PFA)(Burbidge1971).AlgorithmsdevelopedforPFA(e.g.King1980),maybeadaptedfortheanalysisoftheResource/Activitymatriceshere.

(b)Department/Activitymatrix(®gure8(b)):thisissimilartothepreviousone,

butitaggregatesinformationatthedepartmentlevelbyshowingwhichdepartmentsareinvolvedineachactivityandhowmanyresourcesofeachtypeareengaged.Thematrixmaybehelpful,forexample,inspottingwheretosetupinterdepartmentalgroups.

(c)Resource/Resourcematrix(®gure8(c)):thisisusedtoanalyseinformationor

materialsexchangedamongresources.Analysisofthismatrixenablesabetterunderstandingoftheorganisation,andhenceabetterdesignofboththeinformation¯owandthemediawithwhichinformationisexchanged.(d)Department/Departmentmatrix(®gure8(d)):thismatrixissimilartothe

resource/resourcematrixexceptthatitisusedtoanalyseinformationormaterialexchangedbetweendepartments.

3850

Tom1AngC.-L.etal.

Nelson11(a)

Dept A53Dept B79(b)

TomTomNelsonHarryGeorgeNelson352(c)

Dept A1711Dept B21Dept C1161Dept D7Harry91George23Dept C4111Dept D1Harry111George1Activity 1Activity 2Activity 3Activity 4Activity 1Activity 2Activity 3Activity 43Dept ADept BDept CDept DFigure8.

18(d)

(a)Resource/Activitymatrix;(b)Department/Activitymatrix;(c)Resource/

Resourcematrix;(d)Department/Departmentmatrix.

4.Integrationofmodellinglevels

Thissectiondescribestheintegrationofmodellinglevelsforeachofthefourmodellingviews.4.1.

Functionview

Infunctionalmodelling,anIDEF0modelisrstbuiltattherequirementsde®ni-tionleveltode®ne`thingstobedone’.Atthedesignspeci®cationlevel,themodelisthendecomposedandextendedtoincludeprocessview(seesection3.1)anddynamicview(seesection3.2).Thisresultsinthreemodels:adetailedIDEF0functionmodel,anIDEF0-basedprocessmodel,andanIDEF0-basedIDEF2dynamicmodel,ehichcollectivelyde®ne`howthingsaretobedone’.Attheimplementationdescriptionlevel,theIDEF0-basedIDEF2dynamicmodelisfurtherextendedtoincludesuchdetailsasexceptionhandlingrules,activationrules,datacommunicationsaddresses,etc.,toenablecomputerexecutionofthemodelforwork¯owcontrol(seesection6).

IDEF*modellingmethodology

4.2.

3851

Informationview

Databasedesignismorethanjustbuildingentitiesandconnectingthembyrelationshipswhichonlyrepresentthestaticpartoftheinformationsystem.Thedynamicpart,i.e.thewayinwhichdataandinformationaregoingtobeprocessed,mustalsobeconsidered(Vernadat1996).InIDEF*,asinCIMOSA,thestaticpartismodelledbytwoconstructs,ConceptualSchemaandExternalSchema;whilethedynamicpartismodelledbyanothertwoconstructs,IntegrityRuleandDatabaseTransaction.Themodellingframeworkiscompliantwiththethree-schemaapproachproposedbyANSI(AmericanNationalStandardsInstitute)(ANSI1975)whichadvocatesfortheuseofaglobalconceptualschemaimplementedintermsofaninternalschemaandpresentedtothesystemusersviaexternalschema.

Atthedesignspeci®cationlevel,anIDEF1xmodel(anERA-basedconceptualmodel)isrstbuiltandisthenusedtoderivetheexternalschemata.Inaddition,integrityrulesthatconstrainthepossiblevaluestakenbyattributescanalsobespeci®ed.Theserulesareexpressedintermsofnaturallanguageofexpressions.Theycanbederivedfromthedeclarativerulesofbusinessprocesses(seesection4.2),ortheycanbespeci®edbyusersasseparatedetailedinformationrequirements.Oncetheconceptualschemaanditsexternalschematahavebeenproduced,dataanddatabasetransactions,i.e.dataprocessingfunctionaloperationsorqueriesondata,canbespeci®edusingIDEF0*.LiketheM*ProcessDescriptionModel(Vernadatetal.19),theIDEF0*modelisaformalmodelwhichcanbeusedtospecifydatamanipulationoperationstobeexecutedondata,eitherbyapplicationprogramsordirectlybyusersintheformofdatatransactions.

Implementationdescriptioninvolvesbothlogicaldatabasedesignandphysicaldatabasedesign.Inlogicaldatabasedesign,theconceptualschemaismappedontoarelationalschemausingtheconversionrulesdevelopedbyElmasriandNavathe(19).TherelationalschemaisthenimplementedasaninternalschemainphysicaldatabasedesignusingtheStructuredQueryLanguage(SQL).Physicaldatabasedesignalsoinvolvescodingtheintegrityrules,dataanddatabasetransactionsofapplicationsprograms,andon-linequeriesusingSQLfordatamanipulationandquery.SQLisboththedatadescriptionlanguage,andthedatamanipulationandquerylanguageforwell-knownrelationaldatabasesystemslikeOracle,DB2,Ingres,andInformix.4.3.

Resourceview

ThedetailedIDEF0functionmodelasdevelopedatthedesignspeci®cationleveloffunctionalmodelling(seesections4.1)isalsousedforresourcemodelling.ItisconvertedintoanIDEF-basedresourcemodelfordesignspeci®cationbyusingthetwoCIMOSAdescriptiontemplatesmentionedinsection3.4,i.e.CapabilitySetandResource.InIDEF*,thesameIDEF0-basedresourcemodeldevelopedfordesignspeci®cationisalsousedforimplementationdescription.4.4.

Organisationview

ThesamedetailedIDEF0functionmodelisalsousedfororganisationmodelling.ItisconvertedintoanIDEF0-basedorganisationmodelfordesignspeci®cationbymeansofthetwoCIMOSAdescriptiontemplatesmentionedinsection3.5,i.e.OrganisationUnitsandOrganisationCells.Again,thesameIDEF0-basedorgan-isationmodeldevelopedfordesignspeci®cationisalsousedforimplementationdescription.

38524.5.

AngC.-L.etal.

Capabilitytosupportenterprisemodelling

Table3isacomparisonofIDEF*andIDEFintermsoftheircapabilitytosupportfunctional,information,resourceandorganisationmodellingatdi󰁎erentmodellinglevels.Ascanbeseenfromthetable,IDEF0*isablefullytosupportthefourmodellingprocessesatalllevels.IDEFisablefullytosupportfunctionalmodellingandinformationmodellingattherequirementsde®nitionlevel,butonlypartiallyatthedesignspeci®cationandimplementationdescriptionlevels.Itcannotsupportresourcemodellingandorganisationmodellingatalllevels.

5.

Integrationofmodellinglayers

Forfunctionalmodelling,integrationofthethreemodellinglayers,namelygen-eric,partialandparticular,isachievedbymeansofaknowledge-basedsystemforthesemi-automatedgenerationofIDEF0models.Thesystemisacomputerprogramthatincorporatesthedi󰁎erentkindsofhumanknowledgerequiredtobuildIDEF0modelsbasedontheconceptsofreferencemodels

Referencemodelsaremodelsthatrepresentthestructuresandpracticesthataretypicalofaparticularindustryorasetofcompanieswithinthatindustry.Theyarepartialmodelsthatcanbedecomposedorcustomisedintoparticularmodelsofcompaniesandhencecanbesharedandreused.IthasbeenreportedbyBainesandColquhourn(1991),Weaveretal.(1995),andVernadat(1996)thattheuseofreferencemodelscanfacilitateandacceleratethemodellingprocess.

Anoperationalprototypeoftheknowledge-basedsystemhasbeendevelopedandincorporatedintothesoftwaretoolforIDEF*(Angetal.1997b,Luo1998).

6.

Integrationofmodellingenvironments

TointegratethetwomodellingenvironmentsofCIMOSA:namelyEnterpriseEngineeringandEnterpriseOperation,thesameIDEF0-basedIDEF2dynamicmodelasmentionedinsections3.2and4.1isfurtherextended,makingitalsoprocessablebyacomputerforwork¯owcontrol(Ang1999,ZukunftandRump1996,Johnson1992).Itisextendedtoincludesuchdetailsasexceptionhandlingrules,activationrules,datacommunicationsaddressestoindicatetheexactentry

FunctionmodellingInformationmodellingResourcemodellingOrganisationmodellingIDEFRequirementsDefinitionDesignSpecificationImplementationDescriptionIDEF*IDEFIDEF*IDEFIDEF*IDEFIDEF*IDEF0IDEF0*IDEF1IDEF1xIDEF0*IDEF0*IDEF3IDEF0* IDEF1xIDEF1xIDEF0*IDEF0*IDEF0*IDEF1xIDEF0*IDEF1xIDEF0*IDEF0*,, = full support = partial support = none.Table3.IDEFversusIDEF*intermstotheircapabilityotsupportdi󰁎erentmodelling

processes.

IDEF*modellingmethodology3853

pointsforreceiving/sendinginputsandoutputs,channelsandformatofmessagesexchangedamongactivities.TheyareagainattachedtotherelevantIDEF0boxesorarrowsastextles,containedwithintheTextoftheIDEF0model,andinputbymeansofdialogueboxes.

7.

Enterprisemodellingprinciples

IDEF*methodologysatis®estheeightprinciplesofgoodmodellingmethod-ologiesproposedby(Vernadat1996).Theyareasfollows.

Principleofseparationofconcerns:itisunrealistictoconsideramanufacturingenterpriseasawholeduetoitsinherentcomplexity.Itmust,therefore,beanalysedpiecebypiece,eachonecorrespondstoanexistingfunctionalareaordomain.Thus,likeCIMOSA,IDEF*viewsanenterpriseasacollectionofdomains.Adomainisafunctionalareaachievingsomegoalsoftheenterpriseandismadeofacollectionofstand-alonecoreprocesses,calleddomainprocesses,andinteractwithotherdomains.

Principleoffunctionaldecomposition:inIDEF*majorfunctionsarestructuredintosub-functions,sub-functionsintosub-sub-functions,andsooninastepwise-re®nementapproachasoriginallysystematisedinSADT(Ross1977).

Principleofmodularity:tofacilitatemodelmaintenance,IDEF0*modelsaremodularinstructure.Inotherwords,themodelsaremadeofanassemblyofcom-patiblebuildingblockssothattheycanbebuiltona`plug-and-play’basis.HerecompatibilityisensuredbymeansoftheICOMconventions(Ross1977).

Principleofmodelgenericity:althoughmanyactivitiesorcomponentsofanenterprisearedi󰁎erent,theyoftenexhibitidenticalorsimilarproperties.Itis,there-fore,importanttode®nestandardbuildingblocksasgenericclassestofactorcommondescriptiveattributesandbehaviors.InIDEF*thesegenericclassesarethevariousfunctionobjectsandentityobjectsintheframe-basedknowledgemodelswhichhavebeenbuilttofacilitatethesemi-automatedgenerationIDEF0models(Luo1998).

Principleofreusability:inIDEF*,partialmodelsarereusedandcustomisedtoparticularmodelstoreducemodellingtimeande󰁎ort.

Principleofprocessandresourcedecoupling:inIDEF*,theprocesses(i.e.thingsbeingdone)andtheresources(i.e.agentsperformingtheprocesses)aredecoupledinordertopreserveoperational¯exibility.Eachenterpriseactivityde®nedatthedesignspeci®cationstageisrstdecomposedintoelementaryprocessingsteps,calledfunc-tionaloperations.Executingagentsorfunctionalentities(activeresourcesinCIMOSAterm)arethenassignedtothefunctionaloperations.Thisisdonebymatchingrequiredfunctionalitiesofactivitieswithfunctionalitieso󰁎eredbyfunc-tionalentities.

Principleofseparationofbehaviourandfunctionality:enterprisefunctionalityconcernsthe`thingstobedone’byfunctionalentities,whileenterprisebehaviourde®nes`howthingsaredone’(AMICE1993).Thetwoshouldbeseparatedifor-ganisational¯exibilityhastobeenforced.Thiswillallowmodi®cationofonewith-outimpactingtheother,andviceversa.InIDEF0*,thetwoareseparated:functionalityisrstde®nedintermsofenterpriseactivitiesandfunctionaloperationsduringfunctionalmodelling,functionalbehaviouristhenspeci®edintermsofsequenceofactivities,behaviourrules,resourceallocation,temporalrules,etc.(seesection3.2)duringprocessmodellinganddynamicmodelling.

38AngC.-L.etal.

Principleofconformity:thisprincipledealswithsyntaxandsemanticsofthemodelandconcernstheabilityofthemodelaccuratelytorepresentwhatitissupposedtomodel.BecauseIDEF0*incorporatessuchwell-provenandrobustmodellingmethodologiesasIDEF0,IDEF3(PFD)andIDEF1x,thereisnoques-tionthatithastheabilityaccuratelytodescribetheactivitiesofamanufacturingsystem,theirsequentialrelationships,andtheinformationneededtosupportthem.Also,importantinformationonsystembehaviour,resourceandorganisationcanallbeinputdirectlyintotheIDEF0*modelastextualdescriptions.ThusIDEF*is,asaccurateasthemodellercanbe.

8.

ComponentoftheIDEF*softwaretool

TheIDEF*softwaretoolcomprisesthefollowingsixcomponents,whichcanbeusedeitherasstandalonemodulesortogetherasanintegratedsoftwaretool.Theyareintegratedinthesensethatoutputfromtherstcomponentservesdirectlyasinputtotheothers.

(a)Aknowledge-basedsystemforthesemi-automatedgenerationofIDEF0

models.

(b)AsoftwaretoolforthesystematicderivationoftheIDEF1xmodelfromthe

IDEF0model.

(c)AsoftwaretoolfortheconversionoftheIDEF0modeltoboththebusiness

processandthequalityprocessmodel.

(d)AsoftwaretoolfortheconversionoftheIDEF0modeltotheIDEF0-based

dynamicmodelanditsexecutionforsystemssimulationandcontrol.

(e)AsoftwaretoolfortheconversionoftheIDEF0modeltotheIDEF0-based

resourcemodel.

(f)AsoftwaretoolfortheconversionoftheIDEF0modeltotheIDEF0-based

organisationmodel.Detailsoftheknowledge-basedsystemaregivenbyAngetal.(1997b)andLuo(1998).Thesystemmakesuseoftwoexpertsystems:onetoquerytheuserforinformationonthecompany’scharacteristicsandtogenerateautomaticallyanIDEF0partialmodelforthecompany;theothertoquerytheuserbasedonthepartialmodelgeneratedforspeci®cinformationonthecompany’sactivitiesandtotransformautomaticallythepartialmodelintoaparticularmodel(whichistobesubjecttovalidation).

Thesecondcomponentsupportstheprocedurementionedinsection3.3forthesystematicderivationoftheIDEF1xmodelfromtheIDEF0model,andthegen-erationofSQLscriptsfromtheIDEF1xmodelforanumberofwell-knownrela-tionaldatabasesystemslikeOracle,DB2andInformix.

TheothercomponentsareessentiallyenhancedIDEF0modellingtools.ThethirdcomponentisusedtocreatetheIDEF0-basedprocessmodel,whichisanintegratedbusinessandqualityprocessmodel,directlyfromtheIDEF0model.ThefourthcomponentisusedtotransformtheIDEF0modelintotheIDEF0-basedIDEF2dynamicmodel.Italsohasabuilt-inintelligentsimulatorthatcanreadandinterprettheASCIItextleofthedynamicmodel,andoperateineithersimula-tionmodeorcontrolmode.Insimulationmode,thesimulatorisusedtosimulatethedynamicmodelforwork¯owanalysis,whileincontrolmodeitisusedtocontrolactualactivitiesforwork¯owexecution(Ang1999).

IDEF*modellingmethodology3855

IDEF* Software ToolProcessModelsIDEF0ModelsKBS for the Semi-automatedGeneration ofIDEF0 ModelsResource Models IDEF0*8Modelling Tool OrganisationModelsIDEF1xDataModels Case Tool for Derivationof IDEF1x Models fromIDEF0 Models.DynamicModels IntelligentSimulatorWorkflowSimulationProgramWorkflowExecutionProgramFigure9.Systemcomponentsandtheirstructuralrelationships.

ThelasttwocomponentsareusedtocreateIDEF0-basedresourceandorgan-isationmodels.

ThecomponentsoftheIDEF*softwaretoolandtheirstructuralrelationshipsareshowningure9.Thesectionsoftheenterprisesystemdevelopmentroute(seesection2.1)theyeachsupportareshowningure10.

9.

Developmentenvironment

TheIDEF*softwaretoolisdevelopedinaWindows95environmentusinganumberofcommercialcasetools.TheseincludeMetaDesign,Design/IDEFTMVersion3.5,andDesign/OATMofMetaSoftwareCorporation(1992);SoftwareDevelopmentKitandVisualC‡‡ofMicrosoftCorporation;Kappa-PCTMofIntelliCorpInc.(1992).Theworkinvolvesmainly:

(a)thedevelopmentofthemethodologyforthesemi-automatedgenerationof

TM

IDEF0modelsanditsincorporationintoDesign/IDEF;

(b)thedevelopmentusingKappa-PCTMofthereferencemodelsbankthatis

associatedwiththemethodologyanditsincorporationintoDesign/IDEFTM;

3856AngC.-L.etal.

Figure10.UsingIDEF*softwaretooltosupportenterprisesystemslifecycledevelopment.

(c)thedevelopmentoftheprocedureforthesystematicderivationofthe

IDEF1xmodelfromtheIDEF0modelsanditsincorporationintoDesign/

TM

IDEF;

(d)theextensionofDesign/IDEFTMsothatitcanalsobeusedtosupportpro-cess,dynamic,resource,andorganisationmodelling;

(e)thedevelopmentusingVisualC‡‡oftheintelligentsimulatormentionedin

TM

section8anditsinterfacewithDesign/IDEF.Thesoftwaretoolisexpectedgreatlytoenhancethee󰁎ectivenessofIDEF*methodologyasitallowstheentireprocessofenterprisesystemsdesigntobecarriedoutinthesameDesign/IDEFTMenvironment.Figure10showshowtheIDEF*softwaretoolcanbeusedtosupporttheentireenterprisesystemsdevelopmentlifecycle.

10.

AdvantageofIDEF*

TheIDEF*approachhasthefollowingadvantagesascomparedtotheconven-tionalapproach.

(a)Easytounderstand.

(b)Completesystemdescriptioncanberealisedsequentiallyandsystematically.(c)Modelcompatibilitycanbemaintainedbyusingthesamefunctionsinthe

di󰁎erentmodels.

(d)Norepeatedcapturingofthesameinformationonsystemfunctionality

becauseof(c).

(e)Noconsistencycheckingisrequiredbecauseof(c).

(f)E󰁏cientbecauseof(d)and(e),andbecauseacompletesystemdescription

th

canbeaccomplishedinthesameDesign/IDEFenvironment(seesection9).(g)IdealforCIMimplementationorenterprise-wideintegrationbecauseIDEF*

isbasedonIDEF0(seesection2.1).

IDEF*modellingmethodology3857

(h)ConformstointernationalstandardsbecauseIDEF*isCIMOSA-compliant

andIDEF-based.

(i)Modelsareexecutablebycomputerforwork¯owsimulationandwork¯owexecution(seesections3.2,4.1and6).

(j)Systems¯exibilityandhencesystemresponsivenesscanbegreatlyincreasedbecauseof(i).

11.

Conclusion

Inthispaper,acomprehensivemodellingmethodologytermedIDEF*hasbeenproposedforthedevelopmentofmanufacturingenterprisesystems.Themethod-ology,whichincorporatessuchrobustmodellingmethodologiesasIDEF0,IDEF3(PFD)andIDEF1x,conformstotheCIMOSAmodellingframework.Itiscompre-hensiveinthesensethatitsupportsmodellingfromthefourmodellingviewsandatthethreedevelopmentlevelsofCIMOSA.Itisalsointegratedinthesensethatitachievesfourkindsofintegrationasexplainedinthepaper.Finally,italsosatis®eseightimportantprinciplesofgoodmodellingmethodology.WhensupportedbyanappropriatesoftwaretoolsuchastheonedevelopedatGintic,itisexpecteddras-ticallytoreducethetimeande󰁎ortofenterprisesystemsdevelopmentandmain-tenance.

References

Adam,N.R.andGanopadhyay,A.,1993,Integratingfunctionalanddatamodellingina

computerintegratedmanufacturingsystem.IEEE9thInternationalConferenceonDataEngineering,IEEEComputerSocietyPress.

AMICEConsortium,1993,CIMOSAOpenSystemsArchitectureforCIM(Berlin:Springer

Verlag).

Ang,C.L.,1999,EnactmentofIDEF0modes.InternationalJournalofProductionResearch,37,

3383±3397.

Ang,C.L.,Khoo,L.P.,Lieu,A.H.andZhou,J.H.,1997a,IntegrationofIDEF0and

IDEF1x,in-housetechnicalreport,G/SD/WP/IDEF*/97/01,GinticInstituteofManufacturingTechnology.

Ang,C.L.,Luo,M.andGayRobert,K.L.,1997b,Aknowledge-basedapproachtothe

generationofIDEF0models.InternationalJournalofProductionResearch,35.

ANSI,ANSI/X3/SPARC,1975,Studygroupondatabasemanagementsystems:interimreport,

75-02-08.ACMSIGMODNewsletter,FDT,7,No.2.

Baines,R.W.andColquhourn,G.J.,1991,TheuseofagenericIDEF0modeltocapture

processplanningfunctionalinformation,integrationandmanagementoftechnologyformanufacturing.IEEEManagementofTechnologySeries,11(London:PeterPeregrinus).Bernus,P.andNemes,L.,1996,EnterpriseintegrationÐengineeringtoolsfordesigningenter-prises.ProceedingsoftheIFIPTC5WorkingConferenceonModelsandMethodologiesforEnterpriseIntegration,Queensland,Australia,1995(Chapman&Hall).Born,C.,1994,ProcessManagementtoQualityImprovement(Wiley).Bruce,T.,1992,DesigningQualityDatabasewithIDEF1xInformationModels(NewYork:

DorsetHousePublishing).

Brumbaugh,D.E.,1994,Object-orientedDevelopment(Wiley).

Burbidge,J.L.,1971,TheIntroductiontoGroupTechnology(London:Heinemann).

Carswell,L.J.andNavathe,S.B.,1987,SA-ER:amethodologythatlinksstructuredanaly-sisandentity-relationshipmodellingfordatabasedesign.FifthConferenceonERApproach,Dijon,France,ElsevierScience.

Elmasri,R.andNavathe,S.B.,19,FundamentalsofDatabaseSystems(Benjamin/

Cummings).

Feldmann,C.G.,1998,ThePracticaltoBusinessProcessReengineeringUsingIDEF0(New

York:DorsetHouse).

FIPSPUBS,1993,Integrationde®nitionforfunctionmodeling(IDEF0),FederalInformation

ProcessingStandardsPublication183,NationalInstituteofStandardsandTechnology,USA.

3858IDEF*modellingmethodology

Hunt,V.D.,1996,ProcessMappingÐHowtoReengineerYourBusinessProcesses(Wiley).IntelliCorp,Inc.USA,1992,Kappa-PCReferenceManual,Version2.3.

ISO,ISODSI10303-11,1992,TheEXPRESSLanguageReferenceManual,InternationalKAPPA-PCVersion3.0,1992,IntelliCorp,Inc.,USA.

Johnson,E.M,1992,Anintegratedsimulationandshop¯oorcontrolsystem.Manufacturing

Review,5,(3).

Kim,B.O.,1994,Businessprocessreengineering:buildingacross-functionalinformationarchi-tecture.JournalofSystemsManagement,45.

Kim,J.I,1996,Function,information,dynamics,andorganisationintegratedmodellingmeth-odologyforenterprisesystemsintegration.PhDthesis,ArizonaStateUniversity.

King,J.R.,1980,Machine-componentgroupformationingrouptechnology:reviewand

extensions.InternationalJournalofProductionResearch,20,(2).

LeClair,S.R.,1982,IDEFthemethodarchitecture,themeanstoimprovemanufacturing

productivity.SMEtechnicalpaperMS82-902,Michigan,USA.

Loomis,M.E.S.,1986,DataModelingÐtheIDEF1xTechnique.FifthAnnualInternational

PhoenixConferenceonComputersandCommunications,ScottsdaleArizona,IEEE.

Luo,M.,1998,Aknowledge-basedapproachtotheautomatedgenerationofIDEF0models.

PhDthesis,NanyangTechnologicalUniversity,Singapore,inadvancedpreparation.Mandel,K.,1990,GraphicalprocessdescriptionÐviewsanddiagrams.InternationalJournalof

ComputerIntegratedManufacturingSystems,3,(5).Mayer,R.J.,Cullinane,T.P,deWine,P.S.,Knappenberger,W.B.,Perakath,B.and

Wells,M.S.,1992,InformationIntegrationforConcurrentEngineering(IICE),IDEF3ProcessDescriptionCaptureMethodReport,AirForceSystemsCommand,Wright-PattersonAirForceBase,Ohio433,AL-TR-1992-0057.

MetaSoftware,1992,Design/IDEFUser’sManual,MetaSoftwareCorporation,Cambridge,

MA.

MicrosoftCorporation,1993,USA,SoftwareDevelopmentKitUser’sManual,Version3.1.Ross,D.T.,1977,Structuredanalysis(SA):alanguageforcommunicatingideas.IEEE

TransactionsonSoftwareEngineering,3,(2).

Smart,A.,Maull,R.,Childe,S.,Bennett,J.andWeaver,A.,1996,GuidelinesforLinking

ProcessandInformationModelsÐIDEF0toIDEF1x,WorkingPaperWP/GR/J95010-7,SchoolofComputing,PlymouthUniversity.Tkach,D.andPuttick,R.,1994,ObjectTechnologyinApplicationDevelopment(Benjamin/

CummingsPublishingCo.).

USAirForce,1981a,Integratedcomputerintegratedmanufacturing(ICAM)architecture,

PartII,Vol.IVÐfunctionalmodellingmanual(IDEF0),AirForceMaterialLaboratory,Wright-PattersonAFB,Ohio433,AFWAL-TR-81-4023;1981b,Integratedcomputerintegratedmanufacturing(ICAM)architecture,PartII,Vol.VÐinformationmodellingmanual(IDEF1),AirForceMaterialLaboratory,Wright-PattersonAFB,Ohio433,AFWAL-TR-81-4023;1981c,Integratedcomputerinte-gratedmanufacturing(ICAM)architecture,PartII,Vol.VIÐdynamicsmodellingman-ual(IDEF0),AirForceMaterialLaboratory,Wright-PattersonAFB,Ohio433,AFWAL-TR-81-4023.

Vernadat,F.B.,DiLeva,A.andGiolito,P.,19,Organisationandinformationsystem

designofmanufacturingenvironments:thenewm*approach.JournalofComputer-IntegratedManufacturingSystems,2,(2).

Vernadat,F.B.,1996,EnterpriseModellingandIntegration,PrinciplesandApplications

(Chapman&Hall).

Wang,W.,Popplewell,K.andBell,R.,1993,Anintegratedmulti-viewsystemdescription

approachtoapproximatefactorymodelling.InternationalJournalofComputerIntegratedManufacturing,6,(2).

Weaver,A.M.,Childe,S.J.,Maul,R.S.andSmart,P.A.,1995,Thedevelopmentand

applicationofageneric`orderful®lment’processmodel.ProceedingsoftheThirdInternationalConferenceonCIM,Singapore.

Zukunft,O.andRump,F.,1996,Frombusinessprocessmodellingtowork¯owmanagement:

anintegratedapproach.InScholz-Reiter,B(Ed.),BusinessProcessModelling(Berlin:Springer-Verlag).

OrganizationforStandardization,ISOTC184/SC4/WG5,N35.