My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
2007/10/17 Council Agenda Packet
>
Council Agenda Packets
>
2007
>
2007/10/17 Council Agenda Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/17/2017 11:33:36 AM
Creation date
3/17/2017 11:32:41 AM
Metadata
Fields
Template:
Council Agenda Packet
Date
10/17/2007
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
190
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
12 6.11-11.4.3.2 RFCS Test Bed <br /> a. The Contractor shall provide a test-bed located in the Puget Sound Area. <br /> Equipment representing each Agency's equipment and configuration shall be <br /> assembled in a single test-bed ("RFCS test-bed") to permit interconnection to <br /> simulate the overall RFCS configuration and operation. The RFCS test-bed shall <br /> be used to perform, among other things, device testing, device interface and <br /> integration testing, including systems integration, and configuration data testing <br /> and administration. <br /> It is not required that the Central System or DACS which support financial and <br /> operational data processing be co-located at this site, but it must be possible to <br /> interconnect to them using the telecommunications processes to be used in the <br /> installed system environment. The RFCS central system (clearinghouse, servers <br /> and associated systems and networks) shall be connected to the test bed to <br /> support full operation of all systems and subsystems in the RFCS test bed. The <br /> RFCS testbed also includes the devices, connections and network that enable <br /> Washington State Ferries (WSF) to remotely access an RFCS Release in the <br /> testbed in order to test it in conjunction with other WSF hardware and software <br /> that are integrated with the RFCS. <br /> b. The test-bed shall be established prior to the commencement of System <br /> Integration Testing. Each Agency's actual equipment shall also be utilized in the <br /> RFCS test-bed to perform end-to-end testing prior to delivery of said Agency <br /> equipment to Agency facilities. <br /> c. The Contractor shall be responsible for the test-bed environment until <br /> completion of Contract. <br /> The test-bed shall remain operational through the duration of the Contract and <br /> shall be updated to reflect any changes to the devices, software, system <br /> configuration and/or configuration data. <br /> 2.0 Change to Section 6.11-11.4.7.1 <br /> Section 6.11-11.4.7.1 is amended to read as follows: <br /> 11.4.7.1 Acceptance Testing Settling In Period <br /> The initial period of time following the completion of the Phase II Milestone of <br /> "Completion of Complete System Commissioning" shall be designated as the <br /> Acceptance Testing Settling In period. The Contractor shall archive data created during <br /> development and testing so that the Settling-in period shall commence with clean <br /> databases. <br /> (a) The Acceptance Testing Settling In period will last for at least thirty (30) days <br /> prior to beginning Acceptance Testing. During the Acceptance Testing Settlino in <br /> CCA#3-Attachment B 2 <br />
The URL can be used to link to this page
Your browser does not support the video tag.