1.      GENERAL






1.     GENERAL

This document presents the Smart Lane ETS equipment and System Integration Plan (Integration Plan) guidelines. The Integration Plan shall define the activities necessary to integrate the ETS functional software components into the ETS software application system.


The Integration Plan shall contain an overview of the system, a description of the major tasks involved in the integration, including the overall Integrator resources that are needed to fully support the integration effort.


The Integration Plan shall be developed by the Integrator during the system design and development phase and should be updated and used during the Integration and Test Phase.  The final version would be provided in the Implementation Phase for approval by the JPA.  The Integration Plan shall outline the different types of internal Integrator software integration tests that shall be conducted to ensure that the ETS is designed and operates according to the RFP and the other Contract documents.  The Integration Plan shall also identify the roles and responsibilities of each Integrator internal group that will be working on this project.

2.     Roles and Responsibilities

To ensure that the delivered ETS operates according to the Smart Lane RFP and the other Contract document requirements, many parts of the Smart Lane project engineering organization will have various roles and responsibilities.  Listed below are suggested starting points for defining organizational responsibilities pertaining to the system integration activities required to ensure program success.



The JPA ED shall have full contractual responsibility for all Smart Lane equipment and system integration activities, and will work closely with the consultant staff to ensure that the ETS integration is accomplished properly.  The JPA shall review and approve the Integration Plan prior to it being used by the Integrator.


The Smart Lane tolling system consultant staff shall have the following roles and responsibilities:

1.      Review and provide comments on the Integration Plan and all ETS integration methods, integration test plans and procedures, integration schedule, policies and validation procedures for the Smart Lane Project.  It should be noted that the referenced integration tests are internal tests to be conducted by the Integrator and, therefore, are separate from the Smart Lane tests that will be performed by the JPA as identified in the Verification (Test) Plan.

2.      Participate in all facets of integration activities and provide recommendations to the JPA for verification testing during integration stages of the project.

3.      Provide technical assistance to the Integrator and JPA staff during the integration process.

4.      Provide guidance during Integration with live traffic in conjunction with the JPA management staff.

5.      Maintain a liaison with JPA and Integrator staff to incorporate additional Integration testing procedures and additional operational scenario management based on external requirements.


The Integrator systems engineering personnel for the I-680 Smart Lane Project shall have the following roles and responsibilities:

1.      Develop a comprehensive Integration Plan to effectively support the Smart Lane ETS Application system. The Integration Plan shall be approved by the JPA.

2.      Perform all Integration tests described in the plan including performance requirements, and detailing to the JPA/consultant group each procedure that is being conducted and why.

3.      Ensure that the sub-system and end-to-end integration testing requirements and processes satisfy the RFP requirements by utilizing the trace matrix.

4.      Develop a detailed integration report detailing all the integration tests that were run, any problems that were discovered, and how those problems would be corrected.

5.      Perform any required re-integration activities identified by JPA and consultant staff. Re-integration documentation shall be submitted to the JPA.


The Smart Lane ETS Integration Plan shall detail a task-based integration process that will accommodate the various sub-systems of the ETS application system.


The System Integration Plan shall clearly describe the following phases:



Presented below in Figure 1 is a schematic that shows the distinct Smart Lane Project ETS integration phases and how each phase relates with one another.

The field subsystems integration, toll data center system integration, and communications system integration phases support the end to end application integration phase.

Figure 1 – Integration Process




The Integration Plan shall define in detail the integration of each of the field sub-systems of the Smart Lane tolling solution.  This would include, at a minimum:


  1. The electronic tolling system;
  2. The Dynamic Message Sign (DMS) system;
  3. The Vehicle Detection Station (VDS) system;
  4. The Smart Lane enforcement system; and
  5. The Closed Circuit Television (CCTV) system.


The Integrator sub-system integration tests should include, at a minimum, the following test environments to satisfy the functional requirements in the RFP and other Contract documents:


·         Verify data integrity (no loss of data);

·         Verify diagnostic messages;

·         Introduce failures and threats;

·         Degraded mode performance;

·         Verify diagnostic messages; and

·         Normal transaction tests.




The Integration Plan shall define in detail the integration of each of the TDC sub-systems of the Smart Lane tolling solution.  This would include, at a minimum;



The following internal Integrator integration tests, at a minimum, should be identified in the Integration Plan:


·         Verify diagnostic messages;

·         Normal transaction tests;

·         Tolling zone operational tests;

·         TDC trip generation and algorithm process;

·         TDC interface to the BATA RCSC;

·         TDC interface to the Caltrans TMC;

·         TDC interface to the enforcement sub-system; and

·         Proper association of vehicle and transponder.




The Integration Plan shall define in detail the full integration of the entire communications system in support of the Smart Lane solution.  This would include, at a minimum:



The following, at a minimum, internal Integrator communications system integration tests should be identified in the Integration Plan:




The Integration Plan shall define in detail the integration of each sub systems to the others thus constituting an end-to-end Smart Lane solution. The plan shall detail each of the Integration tests that would address the integration of all of the sub-systems in a structured manner to achieve the desired outcome of the Smart Lane application, including, at a minimum, the following:


·         Operation of the TDC, including the dynamic pricing algorithms and the trip generation process;

·         Interface to the Caltrans TMC; and

·         Integration between the TDC and the BATA RCSC.

4.     Integration Plan Components

The basic Integration Plan developed by the Integrator shall contain a series of activities to be executed as part of the System Integration tasks.

Integration testing activities and scenarios shall include complete end-to-end testing of all functions and operations of the Smart Lane System.  This integration testing will involve using live traffic at the Integrator’s production facility.  Additional testing will be conducted with live traffic while the HOV lane is operational as an HOV/MF lane.  It will not be opened to HOT traffic until the field testing is successfully completed.


The following System Integration activities would be identified in the Integration Plan for the Smart Lane ETS application system. These activities would be carried out on all ETS integration tasks and associated integration tests.  The Integration Plan shall describe the following activities in detail to provide a comprehensive audit of the ETS integration task of the Smart Lane Project.

  1. Provide overall planning and coordination for Integrator activities of the ETS application integration;
  2. Provide appropriate training for personnel to carry out the integration;
  3. Provide appropriate documentation on each sub-system  for integration;
  4. Provide audit or review reports;
  5. Document sub-system software unit and database;
  6. Establish integration test procedures;
  7. Conduct sub-system integration  testing; and
  8. Integrate sub-systems into final Smart Lane ETS application system.

The JPA and their representatives shall be permitted to participate in or otherwise observe any and all of these Integration Tasks.  Tentative dates for conducting the various Integration phases shall be included in the Integration Plan document submitted by the Integrator during the system design phase of the Contract.  Reasonable modifications to these dates may be permitted during the course of the work by the JPA provided a written request for such change is made at least two weeks prior to the revised Integration Phase test date.  The actual change approval must be granted, in writing, by the JPA.


This section of the Integration Plan shall provide a detailed description of each major Integrator step required for the full integration of the ETS.  The Integrator shall also develop an internal integration schedule for when these tasks are expected to be completed.

The following information shall be included in the description of each major step, as appropriate:

1.      What the step will accomplish;

2.      Resources required to accomplish the step;

3.      Key person(s) responsible for the step; and

4.      Criteria for successful completion of the step.

Step Accomplishment

This sub-section of the Integration Plan shall describe the expected results of each of the integration steps to be carried out by the Integrator to complete the Smart Lane System application.


Resource Requirements

This section of the Integration Plan shall contain project developed equipment and software products to be integrated, including any support equipment such as special software, test hardware, software drivers, and simulations of sub-systems to be integrated during the system integration task.


Key Integration Staff

This section shall identify the key system integration specialists, including the external system interface knowledge engineers to enable successful integration of major sub-systems of the ETS application system.


Criteria for Step Completion

The Integration Plan shall provide both the Integrator and the JPA a mechanism for verifying and documenting successful integration of all the sub-systems throughout the integration testing.  Testing procedures and scenarios, which will be developed by the Integrator and subject to JPA approval, shall be built upon the previously used unit and sub-system scripts and test steps.


The Integration Plan shall describe the support software, materials, equipment, and facilities required for the integration, as well as the personnel requirements and training necessary for the Smart Lane application integration.

Resources and their Allocation

The plan shall list all support software, materials, equipment, and facilities required for the end-to-end Smart Lane application integration. The Integration Plan shall describe the test environment and any resources needed. The Plan shall describe the number of personnel needed and availability.


The Integration Plan shall identify the training necessary to prepare for the integration and maintenance of the Smart Lane application system.


The Integration Plan shall list all the test requirements for each set of integration test scenarios.  It should include a description for each suite of integration tests, including the data included, procedures for testing, who is responsible for the testing and the internal integration testing schedule.  This could be accomplished in one plan or several, depending on the complexity of the suite of integration tests being tested.

Any failures encountered during integration testing must be resolved and retested before commencement of the Operational Performance Test (OPT), which is described in the Verification (Test) Plan.  The integration problems identified will be tracked by the Integrator and the matrix shall be provided to the JPA, if requested.