<?xml version="1.0" encoding="windows-1252"?><SEC xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://si.ksc.nasa.gov/sidownloads/xml/specsintactSEC.xsd"><MTA NAME="SUBFORMAT" CONTENT="NEW"/><BRK/>
<HDR><AST/><BRK/>
USACE / NAVFAC / AFCESA /NASA             UFGS-01 45 01.10 (January 2008)<BRK/>
                                          --------------------------------<BRK/>
Preparing Activity:  <PRA>USACE</PRA>                Superseding<BRK/>
                                          UFGS-01 45 02.00 10 (April 2006)<BRK/>
<BRK/>
<HL4>UNIFIED FACILITIES GUIDE SPECIFICATIONS</HL4><BRK/>
<BRK/>
<AST/><BRK/></HDR>
<BRK/>
<SCN>SECTION 01 45 01.10</SCN><BRK/>
<BRK/>
<STL>USACE QUALITY CONTROL SYSTEM (QCS)</STL><BRK/>
<DTE>01/08</DTE><BRK/>
<NTE><BRK/>
<AST/><BRK/>
<NPR>NOTE:  This guide specification covers the requirements for <SCP>use of the Quality 
Control System (QCS) for contract monitoring and administration.</SCP></NPR><BRK/>
<BRK/>
<NPR>Edit this guide specification for project specific requirements by adding, deleting, 
or revising text.  For bracketed items, choose applicable items(s) or insert 
appropriate information.</NPR><BRK/>
<BRK/>
<NPR>Remove information and requirements not required in respective project, whether 
or not brackets are present.</NPR><BRK/>
<BRK/>
<NPR>Comments and suggestions on this guide specification are welcome and should 
be directed to the technical proponent of the specification.  A listing of <URL HREF="http://65.204.17.188/report/ufgs.html">technical 
proponents</URL>, including their organization designation and telephone number, is 
on the Internet.</NPR><BRK/>
<BRK/>
<NPR>Recommended changes to a UFGS should be submitted as a <URL HREF="http://65.204.17.188/projnet/cms/public.html">Criteria Change Request 
(CCR)</URL>.</NPR><BRK/>
<AST/><BRK/></NTE>
<BRK/>
<PRT><TTL>PART 1   GENERAL</TTL><BRK/>
<BRK/>
<SPT><TTL>1.1   Contract Administration</TTL><BRK/>
<NTE><BRK/>
<AST/><BRK/>
<NPR>NOTE:  During preparation of the Project Management Plan, the project delivery 
team should analyze each project/future contract to decide if use of (QCS) is 
necessary.  Its use will be appropriate for inclusion in most construction and 
dredging contracts.  However, it may not be necessary nor beneficial to include 
the (QCS) requirement in small, simple, short duration contracts/delivery orders 
for construction, or for other contracts where its use would not be beneficial 
overall.</NPR><BRK/>
<BRK/>
<NPR>The decision to use or not use QCS should be documented in the project management 
plan for each construction project.  A district-wide internal Standard Operating 
Procedure specifying the criteria for QCS use is also recommended.  Note that 
RMS, the Government version, is to be used for all construction contracts, including 
those where QCS is not required.</NPR><BRK/>
<BRK/>
<NPR>The clauses and sections listed below are closely related to this section and 
must be coordinated with this section.  These clauses and sections should reference 
Section 01 45 01.10 USACE QUALITY CONTROL SYSTEM (QCS) whenever appropriate 
and necessary to require use of QCS by the Contractor.</NPR><BRK/>
<BRK/>
<NPR>  -  Contract Clause, Schedules for Construction - <BRK/>
     Contracts<BRK/>
  -  Contract Clause, Payments<BRK/>
  -  Section <SRF>01 32 01.00 10</SRF> PROJECT SCHEDULE<BRK/>
  -  Section <SRF>01 33 00</SRF> SUBMITTAL PROCEDURES<BRK/>
  -  Section <SRF>01 45 01</SRF> USACE QUALITY<BRK/>
     CONTROL</NPR><BRK/>
<AST/><BRK/></NTE>
<BRK/>
<TXT>The Government will use the Resident Management System for Windows (RMS) to assist in its monitoring and administration 
of this contract.  The Contractor must use the Government-furnished Construction Contractor Module of RMS, referred 
to as QCS, to record, maintain, and submit various information throughout the contract period.  The Contractor 
module, user manuals, updates, and training information can be downloaded from the <URL HREF="http://155.80.93.251">RMS</URL> web site.  This joint 
Government-Contractor use of RMS and QCS will facilitate electronic exchange of information and overall management 
of the contract.  QCS provides the means for the Contractor to input, track, and electronically share information 
with the Government in the following areas:</TXT><BRK/>
<BRK/>
<ITM INDENT="-0.33">Administration</ITM><BRK/>
<ITM INDENT="-0.33">Finances</ITM><BRK/>
<ITM INDENT="-0.33">Quality Control</ITM><BRK/>
<ITM INDENT="-0.33">Submittal Monitoring</ITM><BRK/>
<ITM INDENT="-0.33">Scheduling</ITM><BRK/>
<ITM INDENT="-0.33">Import/Export of Data</ITM><BRK/>
<BRK/>
<SPT><TTL>1.1.1   Correspondence and Electronic Communications</TTL><BRK/>
<BRK/>
<TXT>For ease and speed of communications, both Government and Contractor will, to the maximum extent feasible, exchange 
correspondence and other documents in electronic format.  Correspondence, pay requests and other documents comprising 
the official contract record will also be provided in paper format, with signatures and dates where necessary.  
Paper documents will govern, in the event of discrepancy with the electronic version.</TXT><BRK/>
<BRK/></SPT>
<SPT><TTL>1.1.2   Other Factors</TTL><BRK/>
<BRK/>
<TXT>Particular attention is directed to Contract Clause, "Schedules for Construction Contracts", Contract Clause, 
"Payments", Section <SRF>01 32 01.00 10</SRF>PROJECT SCHEDULE, Section <SRF>01 33 00</SRF> SUBMITTAL PROCEDURES, and Section 
<SRF>01 45 01</SRF> USACE QUALITY CONTROL, which have a direct relationship to the reporting to be accomplished through 
QCS.  Also, there is no separate payment for establishing and maintaining the QCS database; all costs associated 
therewith will be included in the contract pricing for the work.</TXT><BRK/>
<BRK/></SPT>
</SPT><SPT><TTL>1.2   QCS SOFTWARE</TTL><BRK/>
<BRK/>
<TXT>QCS is a Windows-based program that can be run on a stand-alone personal computer or on a network.  The Government 
will make available the QCS software to the Contractor after award of the construction contract.  Prior to the 
Pre-Construction Conference, the Contractor will be responsible to download, install and use the latest version 
of the QCS software from the Government's RMS Internet Website.  Upon specific justification and request by the 
Contractor, the Government can provide QCS on CD-ROM.  Any program updates of QCS will be made available to the 
Contractor via the Government RMS Website as they become available.</TXT><BRK/>
<BRK/></SPT>
<SPT><TTL>1.3   SYSTEM REQUIREMENTS</TTL><BRK/>
<BRK/>
<TXT>The following is the minimum system configuration that the Contractor must have to run QCS:</TXT><BRK/>
<BRK/>
<TXT><HL3><HL1>QCS and QAS System</HL1></HL3></TXT><BRK/>
<BRK/>
<HL4><HL3>Hardware</HL3></HL4><BRK/>
<BRK/>
<ITM>IBM-compatible PC with 1000 MHz Pentium or higher processor</ITM><BRK/>
<BRK/>
<ITM>256+ MB RAM for workstation / 512+ MB RAM for server</ITM><BRK/>
<BRK/>
<ITM>1 GB hard drive disk space for sole use by the QCS system</ITM><BRK/>
<BRK/>
<ITM>3-1/2 inch high-density floppy drive</ITM><BRK/>
<BRK/>
<ITM>Compact Disk (CD) Reader 8x speed or higher</ITM><BRK/>
<BRK/>
<ITM>SVGA or higher resolution monitor (1024x768, 256 colors)</ITM><BRK/>
<BRK/>
<ITM>Mouse or other pointing device</ITM><BRK/>
<BRK/>
<ITM>Windows compatible printer. (Laser printer must have 4 MB+ of RAM)</ITM><BRK/>
<BRK/>
<ITM>Connection to the Internet, minimum 56k BPS</ITM><BRK/>
<BRK/>
<HL4><HL3>Software</HL3></HL4><BRK/>
<BRK/>
<ITM>MS Windows 2000 or higher</ITM><BRK/>
<BRK/>
<ITM>QAS-Word Processing software: MS Word 2000 or newer</ITM><BRK/>
<BRK/>
<ITM>Latest version of: Netscape Navigator, Microsoft Internet Explorer, or other browser that supports 
HTML 4.0 or higher</ITM><BRK/>
<BRK/>
<ITM>Electronic mail (E-mail) MAPI compatible</ITM><BRK/>
<BRK/>
<ITM>Virus protection software that is regularly upgraded with all issued manufacturer's updates</ITM><BRK/>
<BRK/></SPT>
<SPT><TTL>1.4   RELATED INFORMATION</TTL><BRK/>
<BRK/>
<SPT><TTL>1.4.1   QCS User Guide</TTL><BRK/>
<BRK/>
<TXT>After contract award, download instructions for the installation and use of QCS from the Government RMS Internet 
Website.  In case of justifiable difficulties, the Government will provide the Contractor with a CD-ROM containing 
these instructions.</TXT><BRK/>
<BRK/></SPT>
<SPT><TTL>1.4.2   Contractor Quality Control(CQC) Training </TTL><BRK/>
<BRK/>
<TXT>The use of QCS will be discussed with the Contractor's QC System Manager during the mandatory CQC Training class.</TXT><BRK/>
<BRK/></SPT>
</SPT><SPT><TTL>1.5   CONTRACT DATABASE</TTL><BRK/>
<BRK/>
<TXT>Prior to the pre-construction conference, the Government will provide the Contractor with basic contract award 
data to use for QCS.  The Government will provide data updates to the Contractor as needed, generally by using 
the Government's SFTP repository built into QCS import/export function.  These updates will generally consist 
of submittal reviews, correspondence status, QA comments, and other administrative and QA data.</TXT><BRK/>
<BRK/></SPT>
<SPT><TTL>1.6   DATABASE MAINTENANCE </TTL><BRK/>
<BRK/>
<TXT>Establish, maintain, and update data in the QCS database throughout the duration of the contract at the Contractor's 
site office.  Submit data updates to the Government (e.g., daily reports, submittals, RFI's, schedule updates, 
payment requests, etc.) using the Government's SFTP repository built into QCS export function. If permitted by 
the Contracting Officer, e-mail or CD-ROM may be used instead of E-mail (see Paragraph DATA SUBMISSION VIA CD-ROM).  
The QCS database typically includes current data on the following items:</TXT><BRK/>
<BRK/>
<SPT><TTL>1.6.1   Administration</TTL><BRK/>
<BRK/>
<SPT><TTL>1.6.1.1   Contractor Information</TTL><BRK/>
<BRK/>
<TXT>Contain within the database the Contractor's name, address, telephone numbers, management staff, and other required 
items.  Within 14 calendar days of receipt of QCS software from the Government, deliver Contractor administrative 
data in electronic format.</TXT><BRK/>
<BRK/></SPT>
<SPT><TTL>1.6.1.2   Subcontractor Information</TTL><BRK/>
<BRK/>
<TXT>Contain within the database the name, trade, address, phone numbers, and other required information for all subcontractors.  
A subcontractor must be listed separately for each trade to be performed.  Assign each subcontractor/trade a 
unique Responsibility Code, provided in QCS.  Within 14 calendar days of receipt of QCS software from the Government, 
deliver subcontractor administrative data in electronic format.</TXT><BRK/>
<BRK/></SPT>
<SPT><TTL>1.6.1.3   Correspondence</TTL><BRK/>
<BRK/>
<TXT>Identify all Contractor correspondence to the Government with a serial number.  Prefix correspondence initiated 
by the Contractor's site office with "S".  Prefix letters initiated by the Contractor's home (main) office with 
"H".  Letters must be numbered starting from 0001.  (e.g., H-0001 or S-0001).  The Government's letters to the 
Contractor will be prefixed with "C".</TXT><BRK/>
<BRK/></SPT>
<SPT><TTL>1.6.1.4   Equipment </TTL><BRK/>
<BRK/>
<TXT>Contain within the Contractor's QCS database a current list of equipment planned for use or being used on the 
jobsite, including the most recent and planned equipment inspection dates.</TXT><BRK/>
<BRK/></SPT>
<SPT><TTL>1.6.1.5   Management Reporting</TTL><BRK/>
<BRK/>
<TXT>QCS includes a number of reports that Contractor management can use to track the status of the project.  The 
value of these reports is reflective of the quality of the data input, and is maintained in the various sections 
of QCS.  Among these reports are:  Progress Payment Request worksheet, QA/QC comments, Submittal Register Status, 
Three-Phase Inspection checklists. </TXT><BRK/>
<BRK/></SPT>
<SPT><TTL>1.6.1.6   Request For Information (RFI)</TTL><BRK/>
<BRK/>
<TXT>Exchange all Requests For Information (RFI) using the Built-in RFI generator and tracker in QCS.</TXT><BRK/>
<BRK/></SPT>
</SPT><SPT><TTL>1.6.2   Finances</TTL><BRK/>
<BRK/>
<SPT><TTL>1.6.2.1   Pay Activity Data</TTL><BRK/>
<BRK/>
<TXT>Include within the QCS database a list of pay activities that the Contractor must develop in conjunction with 
the construction schedule.  The sum of all pay activities must be equal to the total contract amount, including 
modifications.  Group pay activities Contract Line Item Number (CLIN); the sum of the activities must equal the 
amount of each CLIN. The total of all CLINs equals the Contract Amount.</TXT><BRK/>
<BRK/></SPT>
<SPT><TTL>1.6.2.2   Payment Requests</TTL><BRK/>
<BRK/>
<TXT>Prepare all progress payment requests using QCS.  Complete the payment request worksheet, prompt payment certification, 
and payment invoice in QCS.  Update the work completed under the contract, measured as percent or as specific 
quantities, at least monthly.  After the update, generate a payment request report using QCS.  Submit the payment 
request, prompt payment certification, and payment invoice with supporting data using the Government's SFTP repository 
built into QCS export function.  If permitted by the Contracting Officer, e-mail or a CD-ROM may be used.  A 
signed paper copy of the approved payment request is also required, which will govern in the event of discrepancy 
with the electronic version.</TXT><BRK/>
<BRK/></SPT>
</SPT><SPT><TTL>1.6.3   Quality Control (QC)</TTL><BRK/>
<BRK/>
<TXT>QCS provides a means to track implementation of the 3-phase QC Control System, prepare daily reports, identify 
and track deficiencies, document progress of work, and support other Contractor QC requirements.  Maintain this 
data on a daily basis.  Entered data will automatically output to the QCS generated daily report.  Provide the 
Government a Contractor Quality Control (CQC) Plan within the time required in Section <SRF>01 45 01</SRF> USACE QUALITY 
CONTROL.  Within seven calendar days of Government acceptance, submit a QCS update reflecting the information 
contained in the accepted CQC Plan:  schedule, pay activities, features of work, submittal register, QC requirements, 
and equipment list.</TXT><BRK/>
<BRK/>
<SPT><TTL>1.6.3.1   Daily Contractor Quality Control (CQC) Reports.</TTL><BRK/>
<BRK/>
<TXT>QCS includes the means to produce the Daily CQC Report.  The Contractor may use other formats to record basic 
QC data.  However, the Daily CQC Report generated by QCS must be the Contractor's official report.  Summarize 
data from any supplemental reports by the Contractor and consolidate onto the QCS-generated Daily CQC Report.  
Submit daily CQC Reports as required by Section <SRF>01 45 01</SRF> USACE QUALITY CONTROL.  Electronically submit reports 
to the Government within 24 hours after the date covered by the report.  Also provide the Government a signed, 
printed copy of the daily CQC report.</TXT><BRK/>
<BRK/></SPT>
<SPT><TTL>1.6.3.2   Deficiency Tracking.</TTL><BRK/>
<BRK/>
<TXT>Use QCS to track deficiencies.  Deficiencies identified by the Contractor will be numerically tracked using QC 
punch list items.  Maintain a current log of its QC punch list items in the QCS database.  The Government will 
log the deficiencies it has identified using its QA punch list items.  The Government's QA punch list items will 
be included in its export file to the Contractor.  Regularly update the correction status of both QC and QA punch 
list items.</TXT><BRK/>
<BRK/></SPT>
<SPT><TTL>1.6.3.3   QC Requirements</TTL><BRK/>
<BRK/>
<TXT>Develop and maintain a complete list of QC testing and required structural and life safety special inspections 
required by the International Code Council (ICC), transferred and installed property, and user training requirements 
in QCS.  Update all data on these QC requirements as work progresses, and promptly provide this information to 
the Government via QCS.</TXT><BRK/>
<BRK/></SPT>
<SPT><TTL>1.6.3.4   Three-Phase Control Meetings</TTL><BRK/>
<BRK/>
<TXT>Maintain scheduled and actual dates and times of preparatory and initial control meetings in QCS.</TXT><BRK/>
<BRK/></SPT>
<SPT><TTL>1.6.3.5   Labor and Equipment Hours</TTL><BRK/>
<BRK/>
<TXT>Log labor and equipment exposure hours on a daily basis.  This data will be rolled up into a monthly exposure 
report.</TXT><BRK/>
<BRK/></SPT>
<SPT><TTL>1.6.3.6   Accident/Safety Reporting</TTL><BRK/>
<BRK/>
<TXT>The Government will issue safety comments, directions, or guidance whenever safety deficiencies are observed.  
The Government's safety comments will be included in its export file to the Contractor.  Regularly update the 
correction status of the safety comments.  In addition, utilize QCS to advise the Government of any accidents 
occurring on the jobsite.  This brief supplemental entry is not to be considered as a substitute for completion 
of mandatory reports, e.g., ENG Form 3394 and OSHA Form 300.</TXT><BRK/>
<BRK/></SPT>
<SPT><TTL>1.6.3.7   Features of Work</TTL><BRK/>
<BRK/>
<TXT>Include a complete list of the features of work in the QCS database.  A feature of work may be associated with 
multiple pay activities.  However, each pay activity (see subparagraph "Pay Activity Data" of paragraph "Finances") 
will only be linked to a single feature of work.</TXT><BRK/>
<BRK/></SPT>
<SPT><TTL>1.6.3.8   Hazard Analysis</TTL><BRK/>
<BRK/>
<TXT>Use QCS to develop a hazard analysis for each feature of work included in the CQC Plan.  Address any hazards, 
or potential hazards, that may be associated with the work.</TXT><BRK/>
<BRK/></SPT>
</SPT><SPT><TTL>1.6.4   Submittal Management</TTL><BRK/>
<BRK/>
<TXT>The Government will provide the initial submittal register in electronic format.  Thereafter, maintain a complete 
list of all submittals, including completion of all data columns.  Dates on which submittals are received and 
returned by the Government will be included in its export file to the Contractor.  Use QCS to track and transmit 
all submittals.  ENG Form 4025, submittal transmittal form, and the submittal register update must be produced 
using QCS.  QCS and RMS will be used to update, store and exchange submittal registers and transmittals, but 
will not be used for storage of actual submittals. </TXT><BRK/>
<BRK/></SPT>
<SPT><TTL>1.6.5   Schedule</TTL><BRK/>
<NTE><BRK/>
<AST/><BRK/>
<NPR>NOTE:  If the contract requires a schedule, use Section <SRF>01 32 01.00 10</SRF> PROJECT 
SCHEDULE; if not, use the Contract clause.</NPR><BRK/>
<AST/><BRK/></NTE>
<BRK/>
<TXT>Develop a construction schedule consisting of pay activities, in accordance with Section <SRF>01 32 01.00 10</SRF> PROJECT 
SCHEDULE.  Input and maintain in the QCS database this schedule either manually or by using the Standard Data 
Exchange Format (SDEF) (see Section <SRF>01 32 01.00 10</SRF> PROJECT SCHEDULE).  Include with each pay request the updated 
schedule.</TXT><BRK/>
<BRK/></SPT>
<SPT><TTL>1.6.6   Import/Export of Data</TTL><BRK/>
<BRK/>
<TXT>QCS includes the ability to export Contractor data to the Government and to import submittal register and other 
Government-provided data from RMS, and schedule data using SDEF.</TXT><BRK/>
<BRK/></SPT>
</SPT><SPT><TTL>1.7   IMPLEMENTATION</TTL><BRK/>
<BRK/>
<TXT>Contractor use of QCS as described in the preceding paragraphs is mandatory.  Ensure that sufficient resources 
are available to maintain its QCS database, and to provide the Government with regular database updates.  QCS 
shall be an integral part of the Contractor's management of quality control.</TXT><BRK/>
<BRK/></SPT>
<SPT><TTL>1.8   DATA SUBMISSION VIA CD-ROM</TTL><BRK/>
<BRK/>
<TXT>The Government-preferred method for Contractor's submission of QCS data is by using the Government's SFTP repository 
built into QCS export function. Other data should be submitted using E-mail with file attachment(s).  For locations 
where this is not feasible, the Contracting Officer may permit use of CD-ROM for data transfer.  Export data 
onto CDs using the QCS built-in export function.  If used, submit CD-ROMs in accordance with the following: </TXT><BRK/>
<BRK/>
<SPT><TTL>1.8.1   File Medium </TTL><BRK/>
<BRK/>
<TXT>Submit in English required data on CD-ROM conforming to industry standards used in the United States.</TXT><BRK/>
<BRK/></SPT>
<SPT><TTL>1.8.2   CD-ROM Labels</TTL><BRK/>
<BRK/>
<TXT>Affix a permanent exterior label to each CD-ROM submitted.  Indicate on the label in English, the QCS file name, 
full contract number, contract name, project location, data date, name and telephone number of person responsible 
for the data.</TXT><BRK/>
<BRK/></SPT>
<SPT><TTL>1.8.3   File Names</TTL><BRK/>
<BRK/>
<TXT>The files will be automatically named by the QCS software.  The naming convention established by the QCS software 
must not be altered.</TXT><BRK/>
<BRK/></SPT>
</SPT><SPT><TTL>1.9   MONTHLY COORDINATION MEETING</TTL><BRK/>
<BRK/>
<TXT>Update the QCS database each workday.  At least monthly, generate and submit an export file to the Government 
with schedule update and progress payment request.  As required in Contract Clause "Payments", at least one week 
prior to submittal, meet with the Government representative to review the planned progress payment data submission 
for errors and omissions. </TXT><BRK/>
<BRK/>
<TXT>Make all required corrections prior to Government acceptance of the export file and progress payment request.  
Payment requests accompanied by incomplete or incorrect data submittals will be returned.  The Government will 
not process progress payments until an acceptable QCS export file is received.</TXT><BRK/>
<BRK/></SPT>
<SPT><TTL>1.10   NOTIFICATION OF NONCOMPLIANCE</TTL><BRK/>
<BRK/>
<TXT>The Contracting Officer will notify the Contractor of any detected noncompliance with the requirements of this 
specification.  Take immediate corrective action after receipt of such notice.  Such notice, when delivered to 
the Contractor at the work site, will be deemed sufficient for <NED/>the purpose of notification. </TXT><BRK/>
<BRK/></SPT>
</PRT><PRT><TTL>PART 2   PRODUCTS</TTL><BRK/>
<BRK/>
<TXT>Not Used</TXT><BRK/>
<BRK/></PRT>
<PRT><TTL>PART 3   EXECUTION</TTL><BRK/>
<BRK/>
<TXT>Not Used</TXT><BRK/>
<BRK/></PRT>
    <END/><BRK/></SEC>