Systems and methods for coordinating QA events

This invention relates generally to coordination of quality assurance and, more particularly, to network-based systems and methods for coordination of quality assurance events, including witness/hold points and audits.

Quality assurance (QA) events, including witness/hold points, audits, and surveillances of critical or key events during construction or maintenance enhance product control and reliability. Particularly, in government regulated industries, such as construction, nuclear power production and aircraft maintenance, strict procedural compliance is necessary for product performance and safety. Designated quality control engineers (QCEs) monitor QA events. For many assembly packages comprehensive auditing, evaluation and testing of the assembly packages and subassemblies is required during construction or fabrication. Documentation of assembly package and subassemblies pedigree and history is audited by designated QCEs prior to installation or operation. Coordination of QA events by designated QCEs is necessary to minimize delays. Complex projects involve large numbers of designated QCEs, include engineers located off-site. Assigned business-entities and QCEs must coordinate to facilitate minimizing event delays or holds. Coordination of audits and designated QCEs is a complex task for many projects. Failure to properly schedule and perform required QA events, including audits or witness/hold points, can result in delayed system operation, extended or additional maintenance, and increased system cost.

In one aspect of the present invention, a method is provided for coordinating QA event schedules using a network-based system. The system includes a server system coupled to a database and at least one client system. The method includes receiving QA event data and storing the QA event data in the database. The method further includes cross-referencing the QA event data, updating the database with the QA event data and providing information in response to an inquiry.

In a further aspect of the invention, a method is provided for coordinating QA event schedules using a network-based system including a server system coupled to a database and at least one client system. The method includes receiving QA event data including at least one of assigned business-entity data, assigned QCE data, assembly package identification data, initial QA event schedule data, preliminary QA event schedule data, confirmed QA event schedule data, QA event duration data, QA event location data, QA event prerequisites data, QA event results data, QA event description data, QA event comments data, and accommodations data. The method further includes storing the QA event data in the database and cross-referencing the QA event data. Cross-referencing the QA event data includes changing QA event schedules based on a QA event result or a change in related QA event schedules. The method also includes updating the database with QA event data, including adding and deleting information so as to revise QA event schedules. Additionally, the method includes providing information, including at least one of assigned business-entity data, assigned QCE data, assembly package identification data, initial QA event schedule data, preliminary QA event schedule data, confirmed QA event schedule data, QA event duration data, QA event location data, QA event prerequisites data, QA event results data, QA event description data, QA event comments data, and accommodations data, in response to an inquiry. Providing information includes downloading requested information from the server system and displaying requested information on the client system. The inquiry including utilizing at least one of pull-down lists, check boxes, and hypertext links.

In another aspect, a network-based system for coordinating QA event schedules is provided. The network-based system includes a client system with a browser, a database for storing information and a server system configured to be coupled to the client system and the database. The server system is further configured to receive QA event data, store the QA event data in the database, update the database with QA event data, cross-reference the QA event data against a schedule, and provide information in response to an inquiry.

In a further aspect, a computer program embodied on a computer readable medium is provided for coordinating QA event schedules. The program includes a code segment that receives QA event data and then maintains a database by adding, deleting and updating QA event data. The program also generates at least one QA event schedule based on the received QA event data and provides the QA event schedules to users.

Embodiments of the invention will now be described by way of example, with reference to the accompanying drawings, in which: <ul id="ul0001" list-style="none"><li>Figure 1 is a simplified block diagram of a QA event coordination system (QCS) in accordance with one embodiment of the present invention.</li><li>Figure 2 is an expanded version block diagram of an exemplary embodiment of a server architecture of the QCS.</li><li>Figure 3 shows a configuration of a database within the database server of the server system with other related server components.</li><li>Figure 4 is a flowchart of the processes employed by QCS to facilitate use.</li><li>Figure 5 is an exemplary embodiment of a user interface displaying a home page of QCS.</li><li>Figure 6 is an exemplary embodiment of a user interface of QCS displaying business-entity and event type selection options.</li><li>Figure 7 is an exemplary embodiment of a user interface of QCS displaying assembly package selection options.</li><li>Figure 8 is an exemplary embodiment of a user interface of QCS displaying assembly package selection options for a supplier.</li><li>Figure 9 is an exemplary embodiment of a user interface of QCS displaying a QA event schedule for a specific assembly package selection option.</li><li>Figure 10 is an exemplary embodiment of a user interface of QCS displaying an Add Quality Control Engineer template.</li><li>Figure 11 is an exemplary embodiment of a user interface of QCS displaying a Composite View Schedule for a selected plant.</li></ul>

Exemplary embodiments of systems and processes that facilitate integrated network-based electronic reporting and workflow process management related to the QA event Coordination System (QCS) are described below in detail. The systems and processes facilitate, for example, electronic submission of information using a client system, automated extraction of information, and web-based reporting for internal and external system users.

The QCS collects, tracks, schedules, and disseminates real time information regarding QA events. In an exemplary embodiment, a network-based QCS collects, tracks, and disseminates real time information regarding QA events of a boiling water reactor (BWR) plant. In another embodiment, QCS collects, tracks, schedules and disseminates information regarding QA events on other plants or systems including, but not limited to, boiling water reactor (BWR), pressurized water reactor (PWR), liquid metal reactor (LMR), aircraft, ships or other transportation systems. The QA event schedules in the QCS are used by multiple business-entities including customers or buyers, primary contractors, subcontractors, third-party inspectors and regulators.

QA event data relating to each assembly package of a plant or system is received by QCS which stores the information in a database, updates the database with information received, cross-references the information received and provides information in response to an inquiry. QA event data includes, but is not limited to, the identity of each assembly package associated with the event, the procedure number associated with the event, the business-entity designated with responsibility for the QA event, the designated QCE, the scheduled date for the QA event, prerequisites for the QA event, the time allocated to complete the QA event, the QA event location, QA event prerequisites data, QA event results data, QA event description data, QA event comments data, accommodations data, and support facilities available for QCEs at the QA event location. In preliminary stages, QA event data may be incomplete but still provide useful information. The system provides a schedule of future QA events sortable by preset time frame, assembly package, business-entity, or QCE. The system allows access to the most recent information, which was previously not possible. The system also provides a responsive assessment of QA event schedule changes facilitating better utilization of resources. Delays in QA events generate costly plant operability delays and wasted travel expenses for the QCEs involved.

In the QCS, QA event data is stored in the database. The network based QCS provides convenient access to QA event data, including original schedules, preliminary schedules and confirmed schedules. Once into the QCS home page, the user has an option to access information on assembly packages that require QA events. In an exemplary embodiment, for each QA event, an authorized user can access the information.

In one embodiment, the system is a computer program embodied on a computer readable medium implemented utilizing a Structured Query Language (SQL) with a client user interface front-end for administration and a web interface for standard user input and reports. In an exemplary embodiment, the system is web enabled and is run on a business-entity's intranet. In yet another embodiment, the system is fully accessed by individuals having an authorized access outside the firewall of the business-entity through the Internet. In a further exemplary embodiment, the system is being run in a Windows NT environment. The application is flexible and designed to run in various different environments without compromising any major functionality.

The systems and processes are not limited to the specific embodiments described herein. In addition, components of each system and each process can be practiced independent and separate from other components and processes described herein. Each component and process also can be used in combination with other assembly packages and processes.

Figure 1 is a simplified block diagram of an QA event Coordination System (QCS) 10 including a server system 12, and a plurality of client sub-systems, also referred to as client systems 14, connected to server system 12. In one embodiment, client systems 14 are computers including a web browser, such that server system 12 is accessible to client systems 14 via the Internet. Client systems 14 are interconnected to the Internet through many interfaces including a network, such as a local area network (LAN) or a wide area network (WAN), dial-in-connections, cable modems and special high-speed ISDN lines. Client systems 14 could be any device capable of interconnecting to the Internet including a web-based phone, personal digital assistant (PDA), or other web-based connectable equipment. A database server 16 is connected to a database 20 containing information on a variety of assembly packages, as described below in greater detail. In one embodiment, centralized database 20 is stored on server system 12 and can be accessed by potential users at one of client systems 14 by logging onto server system 12 through one of client systems 14. In an alternative embodiment database 20 is stored remotely from server system 12 and may be non-centralized.

Figure 2 is an expanded version block diagram of an exemplary embodiment of a server architecture of a QA event Coordination System (QCS) 22. Components in system 22, identical to components of system 10 (shown in Figure 1), are identified in Figure 2 using the same reference numerals as used in Figure 1. System 22 includes server system 12 and client systems 14. Server system 12 further includes database server 16, an application server 24, a web server 26, a fax server 28, a directory server 30, and a mail server 32. A disk storage unit 34 is coupled to database server 16 and directory server 30. Servers 16, 24, 26, 28, 30, and 32 are coupled in a local area network (LAN) 36. In addition, a system administrator's workstation 38, a user workstation 40, and a supervisor's workstation 42 are coupled to LAN 36. Alternatively, workstations 38, 40, and 42 are coupled to LAN 36 via an Internet link or are connected through an Intranet.

Each workstation, 38, 40, and 42 is a personal computer having a web browser. Although the functions performed at the workstations typically are illustrated as being performed at respective workstations 38, 40, and 42, such functions can be performed at one of many personal computers coupled to LAN 36. Work stations 38, 40, and 42 are illustrated as being associated with separate functions only to facilitate an understanding of the different types of functions that can be performed by individuals having access to LAN 36.

Server system 12 is configured to be communicatively coupled to various individuals, including employees 44 and QCEs 46, via an ISP Internet connection 48. The communication in the exemplary embodiment is illustrated as being performed via the Internet, however, any other wide area network (WAN) type communication can be utilized in other embodiments, i.e., the systems and processes are not limited to being practiced via the Internet. In addition, and rather than WAN 50, local area network 36 could be used in place of WAN 50.

In the exemplary embodiment, any authorized individual or business-entity having a workstation 54 can access QCS 22. One of the client systems includes a senior manager's workstation 56 located at a remote location. Work stations 54 and 56 are personal computers having a web browser. Also, work stations 54 and 56 are configured to communicate with server system 12. Furthermore, fax server 28 communicates with employees located outside the business-entity's 44 and any of the remotely located client systems, including a client system 56 via a telephone link. Fax server 28 is configured to communicate with other client systems 38, 40, and 42 as well.

Figure 3 shows a configuration of database 20 within database server 16 of server system 12 shown in Figure 1. Database 20 is coupled to several separate computer software components within server system 12, which perform specific tasks. Server system 12 includes a collection component 64 for collecting data from users in database 20, a tracking component 66 for tracking data, and a displaying component 68 to display information. Tracking component 66 tracks and cross-references data, including modifying existing data. Server system 12 also includes a receiving component 70 to receive a specific query from client system 14, and an accessing component 72 to access database 20 within data storage device 34. Receiving component 70 is programmed for receiving a query from one of a plurality of users. Server system 12 further includes a processing component 76 for searching and processing received queries against database 20 containing a variety of information collected by collection component 64. An information fulfillment component 78, located in server system 12, downloads the requested information to the plurality of users in response to the requests received by receiving component 70. Information fulfillment component 78 downloads the information after the information is retrieved from database 20 by a retrieving component 80. Retrieving component 80 retrieves, downloads and sends information to client system 14 based on a query received from client system 14.

Retrieving component 80 further includes a display component 84 configured to download information to be displayed on a client system's graphical user interface and a printing component 88 configured to print information. Retrieving component 80 generates reports requested by the user through client system 14 in a pre-determined format. System 10 is flexible to provide other alternative types of reports and is not constrained to the options set forth above. In one embodiment, collection component 64, tracking component 66, displaying component 68, receiving component 70, processing component 76, information fulfillment component 78, retrieving component 80, display component 84, and printing component 88 are computer programs embodied on computer readable medium.

Database 20 is divided into a Plant Information Section (PIS) 90, a QA event Information Section (QAIS) 92, and a Support Facilities Section (SFS) 94. PIS 90 contains information specific to each plant. PIS 90, QAIS 92, and SFS 94 facilitate database 20's storage of QA schedules.

PIS 90 includes information relevant to QA event data for each plant including, but not limited to, plant type data 96 and assembly package data 98. Assembly packages data 98 includes data on assembly packages used in the plant or system. Assembly packages vary from plant to plant, as can QA events. The assembly packages classified in a BWR may be different than the assembly packages classified in a PWR. Even in plants of the same type, assembly packages classified in a first BWR may differ from the assembly packages classified in a second BWR. In an exemplary embodiment, a partial list of assembly packages classified include: RPV Refueling Bellows, Containment Hydrogen Recombiner, ASME Section VIII Heat Exchangers, ASME Section III Heat Exchangers I, ASME Section III Heat Exchangers II, RCIC Drain Tank and Drain Pump, RPV Servicing Equipment 1, RPV Servicing Equipment 2, Main Steam Line Plugs, and RPV Head Stud Tensioner. Classified assembly packages can be further divided into subassembly groups.

QAIS 92 contains includes information relevant to QA event data 100 associated with assembly packages. In one embodiment, QA event data 100 includes assembly package identification data 102 for each assembly package, procedure number data 104 associated with each QA event, assigned business-entity data 106 including the business-entity assigned responsibility for the QA event, assigned personnel data 108, assigned QCE data 110, QA event schedule data 112, QA event duration data 114, and QA event location data 116 regarding the physical location of the event. QA event schedule data 112 includes the date the QA event is anticipated to occur.

This date is subject to change and QA event schedule data 112 can include an initial schedule date, a preliminary schedule date, and a confirmed schedule date. QAIS 92 further contains prerequisites data 118, regarding relationships between different QA events, QA event results data 120, QA event description data 122, and QA event comments data 124, providing details and updates regarding the QA event. On occasions, an assembly package will not satisfactorily complete a QA event or other circumstances will delay the planned performance of a QA event. Related QA events may require a delay or rescheduling before they can be completed. Tracking component 66 applies prerequisites data 118 and the relationships described to revise stored QA event data and QA event schedules based on received QA event data 100, including, but not limited to QA event results data 120 and QA event schedule data 112. Revisions or modifications to one stored QA event schedule can effect other related QA event schedules. The plant conditions can generate conflicts between QA events, the same QAEs may be required for QA events in both QA event schedules, or the same equipment may be required for QA events on different QA schedules. Tracking component 66 also updates database 20 as it revises QA event schedules.

SFS 94 contains QA event data 100 regarding support facilities available for QCEs at the QA event site. In one embodiment, SFS 94 includes accommodations data 126 regarding hotels and lodgings supporting the QA event location. QCEs frequently come from off-site locations and such information facilitates the QA event.

System 10 accumulates a variety of confidential data. Therefore, system 10 has different access levels to control and monitor the security of the system. Authorization for access is assigned by system administrators on a need to know basis. In one embodiment, system 10 provides access based on job functions. In yet another embodiment, system 10 provides access based on business-entity. The administration/editing capabilities within system 10 are also restricted to ensure that only authorized individuals have access to modify or edit the data existing in the system. System 10 manages and controls access to system data and information.

The architectures of system 10 as well as various components of system 10 are exemplary only. Other architectures are possible and can be utilized in connection with practicing the processes described below.

Figure 4 is a flowchart 200 of the processes employed system 10 to facilitate use. Initially, the user accesses 210 user interface 220 of the web site through client system 14 (shown in Figure 1). In one embodiment, client system 14, as well as server system 12, are protected from access by unauthorized individuals. The user is required to log-in 230 to system 10 using a password (not shown) or an employee payroll number for security. User interface 220 displays options 240 available to the user through links, check boxes, or pull-down lists on client system 14. Once the user selects an option 244 (in one embodiment, relating to business-entity and event type) from the available links, the request is transmitted 248 to server system 12. Transmitting 248 the request is accomplished either by click of a mouse or by a voice command. Once server system 12 (shown in Figure 1) receives 252 the request, server system 12 accesses 256 database 20 (shown in Figure 1). System 10 determines 260 if additional narrowing options are available. In one embodiment, additional narrowing options include assembly package selection pull-down lists. If additional narrowing options are available 264 system 10 displays 240 the options relating to the prior option selected to the user on client system 14. The user selects 244 the desired option and transmits the request 248. Server system 12 receives the request 252 and accesses 256 database 20. When system 10 determines additional options 260 are not available 268, system 10 retrieves 272 requested information from database 20. The requested information is downloaded 276 and provided 280 to client system 14 from server 12. The user can continue to search 284 database 20 for other information or exit 290 from system 10.

Figure 5 is an exemplary embodiment of a user interface 300 displaying a home page of QCS 10 (shown in Figure 1). User interface 300 requires the user to provide a valid user name 302 and a valid user password 304 to access QCS 10. User interface 300 allows the user to login system 10 and is linked to database 20. Home Page 300 is the entry point for anyone trying to access QA event database 20 via the web. In another embodiment, the user can login to a selected plant. A "Login" button 308 and a "Reset" button 310 are provided. Selection of the Login button 308 after entry of valid user name 302 and user password 304 provides the next interface. In one embodiment, user interface 300 displays links facilitating the selection of alternative systems 312 or aids 314.

Figure 6 is an exemplary embodiment of a user interface 400 of QCS 10 displaying business-entity and event type selection options 402. In one embodiment, user interface 400 is displayed on the client system 14 once the user has logged into QCS 10 (shown in Figure 5). User interface 400 facilitates filtering QA event data 100 for the selected plant. User Interface 400 provides user selectable hyperlink options 404 to narrow QA event data based on an assigned business-entity 406 and a QA event type 408. In an exemplary embodiment, General Electric (GE) Witness/Hold Point Package Information link 410, Third Party Company (TPC) Witness/Hold Point Package Information link 412, and Supplier Witness/Hold Point Package Information link 414 are provided. GE Supplier Audit Information link 416 and TPC Supplier Audit Information link 418 are also provided by user interface 400. In another embodiment, pull-down list are utilized to narrow the selected QA event data. Selection of a link 410, 412, 414, 416, 418 transmits that selection to system 10, which provides the next user interface.

Figure 7 is an exemplary embodiment of a user interface 500 of QCS 10 displaying assembly package selection options 502. In one embodiment, user interface 500 is displayed on the client system 14 once the user has selected an assigned business-entity 406 and QA event type 408 (shown in Figure 6). In an exemplary embodiment, user interface 500 displays a portion of assembly packages selection options 502 associated with GE Witness/Hold Point Package Information link 410 (shown in Figure 6) in a drop down list for user selection. In another embodiment, system 10 displays assembly packages selection options 502 in a hypertext link format. In one embodiment, each specific assembly package selection option 502 is an active link that can be selected by placing the pointer or mouse cursor on the desired assembly package and clicking or selecting by voice command. A return link 510 is available to return the user to user interface 300. A Composite View link 512 is selectable by the user to facilitate review of QA event data 100 in a composite or time frame display. User interface 500 also provides a Add GE Representative link 514, a Add GE QCE link 516, a Add Responsible Engineer link 518, an Update GE Representative Information link 520, an Update GE QCE Information link 522, and an Update Responsible Engineer Information link 524.

Figure 8 is an exemplary embodiment of a user interface 550 of QCS 10 displaying assembly package selection options 502 for a supplier. Similar to user interface 500, user interface 550 is displayed on the client system 14 once the user has selected an assigned business-entity 406 and QA event type 408 (shown in Figure 6). In an exemplary embodiment, user interface 550 displays a portion of assembly packages selection options 502 associated with Supplier Witness/Hold Point Package Information link 414 (shown in Figure 6) in a drop down list for user selection. User interface 550 provides a Add Witness Hold Point Location link 564, a Add Supplier Contact link 566, a Add Budget Hotel link 568, a Add Medium Hotel link 570, a Add High Range Hotel link 572, a Update Witness Hold Point Location link Information 574, a Update Supplier Contact Information link 576, a Update Budget Hotel Information link 578, a Update Medium Hotel Information link 580, and a Update High Range Hotel Information link 582. Links 564, 566, 568, 570, 572, 574, 576, 578, 580 and 582 facilitate receiving and storing QA event data in database 20.

Figure 9 is an exemplary embodiment of a user interface 600 of QCS 10 displaying a QA event schedule 602 for a specific assembly package selection option 504 (shown in Figure 7). QA event schedule 602 includes QA event data 100 for selected assembly package option 604. User interface 600 is displayed on the client system 14 when the user selects a specific assembly package selection option 504 from user interface 500. In an exemplary embodiment, QA event schedule 602 includes title of the selected assembly package option 604, Witness Point Description 606, GE Hold point type 608, TPC Hold Point Type 610, Witness Location 612, Procedure Number 614, Witness Point Number 616, Preliminary Date 618, Confirmation Date 620, Actual Date 622, Tag Number 624, GE Representative 626, TPC Representative 628, Point Details 630, and Updates 632. In an exemplary embodiment, Point Details 630 and Updates 632 provide links to additional information relevant to the listed Witness Point. User interface 600 also provides Supplier Information 640, Responsible Engineer Information 642 and GE QC Engineer Information 644 for the selected assembly package option 604. User interface 600 also provides return link 510, Composite View link 512, Add GE Representative link 514, Add GE QCE link 516, Add Responsible Engineer link 518, Update GE Representative Information link 520, Update GE QCE Information link 522, and Update Responsible Engineer Information link 524.

Figure 10 is an exemplary embodiment of a user interface 700 of QCS 10 displaying an Add Quality Control Engineer template 702. System 10 provides user interface 700 in response to Add GE QCE link 516 (shown in Figures 7 and 8). User interface 700 facilitates the addition of information regarding a specific QCE. Specifically, information necessary to contact the selected QCE is provided to system 10. In an exemplary embodiment, template 702 allows addition of QCE name 708, QCE Telephone Number 710, QCE Fax Number 712, QCE Address 714, QCE Pager Number 716, QCE Cell Phone Number 718, and QCE Email 720. System 10 provides similar user interfaces in response to Add GE Representative link 514, Add Responsible Engineer link 518, Update GE Representative Information link 520, Update GE QCE Information link 522, and Update Responsible Engineer Information link 524 (shown in Figure 9).

Figure 11 is an exemplary embodiment of a user interface 800 of QCS 10 displaying a Composite View Schedule (CVS) 802 for the selected plant. CVS 802 includes QA event data 100 for assembly package options 502 for a predetermined time frame. User interface 800 is displayed on the client system 14 when the user selects Witness Hold Point Composite View 512 (shown in Figures 7 and 9). In an exemplary embodiment, CVS 802 displays QA event data 100 for witness/holdpoints scheduled for twelve weeks from the system date, sometimes referred to as the initial schedule. CVS 802 includes time frame selectors 804. In an exemplary embodiment, a 2 Week Look Ahead link 806 provides a display of QA event data 100 for witness/holdpoints scheduled for two weeks from the system date, sometimes referred to as the confirmed schedule, while a 6 Week Look Ahead link 808 displays QA event data 100 for witness/holdpoints scheduled for six weeks from the system date, sometimes referred to as the preliminary schedule. User interface 800 also provides return link 510 to return the user to interface 300. In an exemplary embodiment, CVS 802 includes Package Number 820, Witness Location 822, Package Title 824, Preliminary Date 826, Confirmation Date 828, Supplier Name 830, Witness Point Description 832, Witness Point Number 834, Tag Number 836, GE Representative 838, TPC Representative 840, Test Duration 842, and GE Rep Update 844. In an exemplary embodiment, GE Rep Update 844 provides a link to additional information relevant to the listed Witness Point.

As described, QCS 10 includes a database 20 for QA event data related to selected plants and assembly packages, which provides reliable and up-to-date QA schedule information. QCS 10 also provides information regarding supporting personnel and facilities. QCS 10 reduces paper-based information by providing on-line up-to-date current information, which is essential in day-to-day coordination quality control in government regulated industries.

In addition, QCS provides electronic user notification flexibility (not shown) that includes notification of changes affecting QA events including, but not limited to, updated QA event schedules, manufacturer's Safety Information Letters (SILs), and QA event results data. This notification may be in the form of an e-mail that is automatically sent to the user, or a note on a business-entity website.

QCS provides multiple users with access to a single information source including a comprehensive QA event schedule. QCS allows the user to track and evaluate QA event schedule changes and progress. QCS provides valuable, services to the customer, third party companies, QCEs and service personnel who are involved in plant support.

For completeness, various aspects of the invention are set out in the following numbered clauses: <ul id="ul0002" list-style="none"><li>1. A method for coordinating QA event schedules (602) using a network-based system (10) including a server system (12) coupled to a database (20) and at least one client system (14), said method comprising: <ul id="ul0003" list-style="none" compact="compact"><li>receiving QA event data (100);</li><li>storing the QA event data in the database;</li><li>cross-referencing the QA event data;</li><li>updating the database with the QA event data; and</li><li>providing information in response to an inquiry.</li></ul></li><li>2. A method in accordance with Clause 1 wherein receiving QA event data (100) comprises receiving at least one of assigned business-entity data (106), assigned contact person data (108), assigned QCE data (110), assembly package identification data (102), procedure number data (104), initial QA event schedule data, preliminary QA event schedule data, confirmed QA event schedule data (112), QA event duration data (114), QA event location data (116), QA event prerequisites data (118), QA event results data (120), QA event description data (122), QA event comments data (124), and accommodations data (126).</li><li>3. A method in accordance with Clause 1 wherein cross-referencing the QA event data (100) comprises changing a QA event schedule (602) based on QA event results data (120).</li><li>4. A method in accordance with Clause 1 wherein cross-referencing the QA event data (100) comprises changing QA event schedules (620) based on a change in other related QA event schedules.</li><li>5. A method in accordance with Clause 1 wherein updating the database (20) comprises adding and deleting QA event data (100).</li><li>6. A method in accordance with Clause 1 wherein updating the database (20) comprises revising QA event schedules (620).</li><li>7. A method in accordance with Clause 1 wherein providing information comprises: <ul id="ul0004" list-style="none" compact="compact"><li>downloading requested information from the server system (12); and</li><li>displaying requested information on the client system (14) in response to the inquiry.</li></ul></li><li>8. A method in accordance with Clause 1 wherein providing information comprises: <ul id="ul0005" list-style="none" compact="compact"><li>displaying information on the client system (14) identifying at least one of a witness/hold point event and an audit event; and</li><li>receiving an inquiry from the client system regarding at least one of a witness/hold point event and an audit event.</li></ul></li><li>9. A method in accordance with Clause 1 wherein providing information comprises: <ul id="ul0006" list-style="none" compact="compact"><li>displaying information on the client system (14) identifying an option relating at least one of an initial QA event schedule, a preliminary QA event schedule and a confirmed QA event schedule; and</li><li>receiving an inquiry from the client system regarding an option relating to at least one of an initial QA event schedule, a preliminary QA event schedule and a confirmed QA event schedule.</li></ul></li><li>10. A method in accordance with Clause 1 wherein providing information comprises: <ul id="ul0007" list-style="none" compact="compact"><li>displaying information on the client system (14) identifying an option relating to an assembly package (98); and</li><li>receiving an inquiry from the client system regarding an option relating to the assembly package.</li></ul></li><li>11. A method in accordance with Clause 1 wherein providing information comprises: <ul id="ul0008" list-style="none" compact="compact"><li>accessing the database (20);</li><li>searching the database regarding the specific inquiry;</li><li>retrieving information from the database; and</li><li>transmitting the retrieved information to the client system (14) for display (240) by the client system.</li></ul></li><li>12. A method in accordance with Clause 1 wherein providing information comprises providing at least one of assigned business-entity data (106), assigned contact person data (108), assigned QCE data (110), assembly package identification data (102), initial QA event schedule data (112), preliminary QA event schedule data, confirmed QA event schedule data, QA event duration data (114), QA event location data (116), QA event prerequisites data (118), QA event results data (120), QA event description data (122), QA event comments data (124), and accommodations data (126).</li><li>13. A method in accordance with Clause 1 wherein providing information comprises submitting an inquiry utilizing pull-down lists.</li><li>14. A method in accordance with Clause 1 wherein the client system (14) and the server system (12) are connected via a network, the network comprising one of a wide area network (50), a local area network (36), an intranet and the Internet (48).</li><li>15. A method for coordinating QA event schedules (602) using a network-based system (10) including a server system (12) coupled to a database (20) and at least one client system (14), said method comprising: <ul id="ul0009" list-style="none" compact="compact"><li>receiving QA event data (100) comprising at least one of assigned business-entity data (106), assigned contact person data (108), assigned QCE data (110), assembly package identification data (102), initial QA event schedule data (112), preliminary QA event schedule data, confirmed QA event schedule data, QA event duration data (114), QA event location data (116), QA event prerequisites data (118), QA event results data (120), QA event description data (122), QA event comments data (124), and accommodations data (126);</li><li>storing the QA event data in the database;</li><li>cross-referencing the QA event data comprising changing QA event schedules based on a QA event result or a change in related QA event schedules;</li><li>updating the database with QA event data comprising adding and deleting information so as to revise QA event schedules; and</li><li>providing information, comprising at least one of assigned business-entity data, assigned contact person data, assigned QCE data, assembly package identification data, initial QA event schedule data, preliminary QA event schedule data, confirmed QA event schedule data, QA event duration data, QA event location data, accommodations data, QA event prerequisites data, and QA event results data, for a selected assembly package, in response to an inquiry, including downloading requested information from the server system and displaying requested information on the client system, the inquiry including utilizing at least one of pull-down lists, check boxes, and hypertext links.</li></ul></li><li>16. A network-based system (10) for coordinating QA event schedules (602), said network-based system comprising: <ul id="ul0010" list-style="none" compact="compact"><li>a client system (14) comprising a browser;</li><li>a database (20) for storing information;</li><li>a server system (12) configured to be coupled to said client system and said database, said server system further configured to: <ul id="ul0011" list-style="none" compact="compact"><li>receive QA event data (100);</li><li>store said QA event data in said database;</li><li>update said database with said QA event data;</li><li>cross-reference said QA event data against a schedule; and</li><li>provide information in response to an inquiry.</li></ul></li></ul></li><li>17. A network-based system (10) in accordance with Clause 16 wherein said client system (14) further comprises: <ul id="ul0012" list-style="none" compact="compact"><li>a displaying component for displaying at least one of pull-down list, check box, and hypertext link options relating to an assembly package; and</li><li>a sending component to send an inquiry to said server system (12) so that said server system can process and download said requested information to said client system.</li></ul></li><li>18. A network-based system (10) in accordance with Clause 16 wherein said system is configured to be protected from access by unauthorized individuals.</li><li>19. A network-based system (10) in accordance with Clause 16 wherein said server system (12) further comprises: <ul id="ul0013" list-style="none" compact="compact"><li>a collection component (64) for collecting QA event data (100) from users in said database (20);</li><li>a tracking component (66) for tracking QA event data on an on-going basis;</li><li>a displaying component (68) for displaying QA event data on at least one of an option relating to an assembly package;</li><li>a receiving component (70) for receiving an inquiry from said client system (14) regarding at least one of an option relating to an assembly package; and</li><li>an accessing component (72) for accessing said database and causing said retrieved information to be displayed on said client system.</li></ul></li><li>20. A network-based system (10) in accordance with Clause 16 wherein said server system (12) further comprises a processing component (76) for searching and processing received inquiries against said database (20) containing information collected by said collection component (64).</li><li>21. A network-based system (10) in accordance with Clause 16 wherein said server system (12) further comprises a processing component (76) for cross-referencing at least one of QA event schedules (602), QA event results data (120), QCE data (110) and assembly package information (98).</li><li>22. A network-based system (10) in accordance with Clause 16 wherein said server system (12) further comprises a retrieving component (80) to retrieve information from said database (20).</li><li>23. A network-based system (10) in accordance with Clause 16 wherein said server system (12) further comprises an information fulfillment component (78) that downloads said requested information after retrieving from said database (20).</li><li>24. A network-based system (10) in accordance with Clause 16 wherein said server system (12) configured to provide information in response to an inquiry further configured to: <ul id="ul0014" list-style="none" compact="compact"><li>download (276) requested information from a server system; and</li><li>display requested information on a client system (14) in response to said inquiry.</li></ul></li><li>25. A computer program embodied on a computer readable medium for coordinating QA event schedules (602), said program comprising a code segment that receives QA event data (100) and then: <ul id="ul0015" list-style="none" compact="compact"><li>maintains a database (20) by adding, deleting and updating QA event data;</li><li>generates at least one QA event schedule based on said received QA event data; and</li><li>provides said QA event schedules to users.</li></ul></li><li>26. A computer program in accordance with Clause 25 further comprising a code segment that provides at least one of an option (240) to filter QA event schedules (602) based on at least one of assigned business-entity, event type, assembly package, and time frame.</li><li>27. A computer program in accordance with Clause 25 further comprises a code segment that generates a display (240) of at least one of an initial QA event schedule (602), a preliminary QA event schedule, and a confirmed QA event schedule.</li><li>28. A computer program in accordance with Clause 25 further comprising: <ul id="ul0016" list-style="none" compact="compact"><li>a code segment that accesses (210) said database (20);</li><li>a code segment that searches said database in response to an inquiry;</li><li>a code segment that retrieves (272) information from said database; and</li><li>a code segment that causes retrieved information to be displayed (280) on said client system (14).</li></ul></li><li>29. A computer program in accordance with Clause 25 further comprising a code segment that monitors the security of the system (10) by restricting access to authorized individuals.</li><li>30. A computer program in accordance with Clause 25 further comprising a code segment that cross-references the QA event schedule (602) when assembly package information is modified.</li><li>31. A computer program in accordance with Clause 25 further comprising a code segment that cross-references the QA event schedule (602) to at least one other QA event schedule when QA event data (100) is received.</li></ul>