[COUNTY(S)], New Jersey



1.      Identification of portions of the ITS architecture being implemented:

[Identify which user services, physical subsystems, information flows, and market packages are being completed as part of the project and how these pieces are made part of the statewide architecture.]


The New Jersey Statewide ITS Architecture serves as the framework for the development of the project architecture.


Market Package(s):

ATMS01   Network Surveillance [Delete if no CCTV or sensors]

ATMS06   Traffic Information Dissemination [Delete if no DMS, HAR or data to SWIFT system]

ATMS08   Traffic Incident Management System [Delete if no coordination with TOC]

ATMS19   Speed Monitoring System [Delete if no sensors]

ATIS1       Broadcast Traveler Information [Delete if no HAR or data to SWIFT system]

MC03       Road Weather Data Collection [Delete if no RWIS]

MC04       Weather Information Processing and Distribution [Delete if no RWIS]

CVO06     Weigh-In-Motion [Delete if no WIMS]


[Expand list of market packages as necessary; delete those pre-entered above that will not be provided by the project]







[Expand subsystem list as necessary; delete those pre-entered above that will not be provided by the project]


Architecture Flow:



[List other agencies or expand architecture flow as necessary to depict information flow and sharing]



2.      Identification of participating agencies roles and responsibilities (Concepts of Operation):


NJDOT will be the lead agency for overseeing the design and construction for the project.  NJDOT will also be the lead agency responsible for operations and maintenance.  NJDOT will share the ITS information with TRANSCOM, NJ Transit, NJ State Police, other regional transportation authorities, adjacent county (or counties), local traffic management and emergency response services.  The appropriate level of information is shared with the public through NJDOT’s SWIFT program through both web and phone based systems.


[Expand discussion as necessary to complete entry. For the user services to be implemented, define the high-level operations of the system, including where the system will be used, functions of the system capabilities, performance parameters, the life cycle of the system, and who will operate and maintain the system.  Establish requirements or agreements on information sharing and traffic device control responsibilities.]


3.      Requirements Definitions:



§         The system shall provide surveillance coverage.

§         The system shall facilitate dissemination of traffic information in advance of critical decision points along the route(s).

§         The system shall be capable of incident detection.


[Continue bullet listing to include other project specific functional requirements, if any; delete those pre-entered above that do not apply to the project.   Based on the concept of operations in Part 2. above, define the “what” and not “how” of the system.  The applicable high-level functional requirements from the Statewide Architecture are a good starting point for discussion]

Device Specific


[Provide description of device specific functional requirements, see example clauses in SERF Instructionst]


4.      Analysis of alternative system configurations and technology options to meet requirements:


NJDOT has guidelines for typical field equipment deployments for CCTV and DMS that will be used to determine the alternative that will allow the system to achieve the functional requirements. System communication alternatives, made available by the present day Information Technologies industry, will be evaluated as part of the project’s High-Level Design (or scoping).  The evaluation will comprise an analysis of performance, cost, operational effectiveness, and compatibility with legacy systems.  The most cost effective configuration will be proposed for the project’s Detailed Design.


[Discuss special systems, if any. The analysis of system alternatives should outline the strengths and weaknesses, technical feasibility, institutional compatibility, and life cycle costs of each alternative. ]



5.      Procurement Options:


The ITS facilities are being deployed through a highway infrastructure project.


The proposed project will be procured through the NJDOT’s standard procurement process, which is “DESIGN - BID - BUILD” with DMS furnished by NJDOT through existing materials contract.


[Verify proposed project procurement with the Department if not part of a standard highway project. Some procurement (contracting) options to consider include: consultant design/low bid contractor, systems manager, systems integrator, task order, and design/build.  Deciding on the best procurement option should consider the level of agency participation, compatibility with existing procurement methods, role of system integrator, and life cycle costs. ]



6.      Identification of applicable ITS standards and testing procedures:


NJDOT ITS standards, including all applicable NTCIP center-to-field communications standards will be incorporated into the project’s design.  Systems verification will be through the various levels of testing required by the NJDOT Standard Specifications Section 704.


[List other ITS standards and testing applicable, if any; i.e., special systems included in Part 4.  Include documentation on which standards will be incorporated into the system design and justification for any applicable standards not incorporated.  The standards report from the Architecture is a good starting point for discussion.]



7.      Resources necessary for operations and management of the system:


NJDOT currently has sufficient, designated staffing and resources to ensure the continuous operation and maintenance of the systems to be integrated and deployed as part of and to expand the capabilities of the current Traffic Operations Center.


[Verify resources with the Department; revise above statement only if and as directed by the DepartmentDocument any internal policies or procedures necessary to recognize and incorporate the new system into the current operations and decision-making processes.  Resources necessary to support continued operations, including staffing and training must also be recognized early and be provided for.  Such resources must also be provided to support necessary maintenance and upkeep to ensure continued system viability.]




Form Approvals


Pre-Design (Scope/Feasibility)



Submitted by: ___________________________________              Date:_________




Approved by: ___________________________________               Date: __________

                        Manager, Traffic Operations (South/North)



 Add other approvals for non-STO ITS deployments as required (ie Manager, Bureau of Data Development for WIMS and TVS)



Final Design Submission


Submitted by: ___________________________________              Date:_________




Approved by: ___________________________________               Date: __________

                        Executive Manager, ITS Engineering






SERF-Programmatic Instructions


This form is for deployment of ITS that meets the requirements for programmatic ITS as defined in Section VIII of the STEWARDSHIP AGREEMENT, see below.  ITS deployments that are not standard and covered under the programmatic definition require additional documentation.


Programmatic Concept of Operations

A. Description: The level of Systems Engineering required for deployment is dependent on the complexity of the proposed system. A programmatic approval is established for those deployments that do not require a Concept of Operations submission before proceeding with the Systems Engineering for the proposed deployment.

B. Project types covered by programmatic approval for compliance with ITS Architecture and 23 CFR 940: Development and deployment of standard ITS systems, individual components or complete systems, within an ITS stand alone project or incorporated within other projects, and the operation and maintenance of existing ITS systems.

C. Standard ITS systems include Traffic Cameras (CCTV), Dynamic Message Signs (DMS), Highway Advisory Radio (HAR), Weigh-in-Motion stations (WIM), Weather Stations (RWIS), Controlled Traffic Signals, and TRANSMIT/Radar/Microwave/loop detectors/other established in-pavement based traffic




1.       Download MSWord.doc and Save As (suggested filename format: “CONTRACT REF” or “PROJECT I.D.” + “- SERF” + “yymmdd”.doc; e.g., CM8005508 SERF 100101).

2.       Enter fully written format (Document Date) where indicated in the document header (if filename date given is “. . . yymmdd.doc” = “. . . 100101.doc”, then date on header should read, “January 1, 2010”).

3.       Complete SERF using the saved document.

4.       Double-click header line to enter Document Date (fully written format), then close header.

5.       Enter project information where required by the form.

6.       Complete Parts 1 thru 7.

7.       Delete all text shown in [red] and Instruction Sheets

8.       Save completed form.

9.       Create PDF copy to be submitted for review and concurrence by Traffic Operations during Scoping

10.    Update Form for any revisions developed during design and submit for review and concurrence by ITS Engineering with the FDS submission.






It is recommended for ITS Designers completing the SERF to gather all reference material developed for the project that would contain the project’s particulars, relevant information, process/design documentation, engineering studies, analyses, etc. that can be summarily used to satisfy the SERF ITEMS tabulated below. 

It is also recommended that the ITS Designer be familiar with the New Jersey Statewide ITS Architecture, the ITS Investment Strategy, and other related documents as available through the NJDOT ITS web site. 

The entries provided in the Programmatic Form template are typical of the Department’s projects deploying ITS for Statewide Traffic Operations and shall be maintained as instructed unless otherwise directed by Traffic Operations or ITS Engineering. 

Discuss with respective ITS SME Unit for projects with deployment of only ITS facilities that are not managed by Statewide Traffic Operations.





COMPLETION GUIDES (instructions, entry examples and reference material)


Market Package(s):

Refer to the latest revision of the New Jersey Statewide ITS Architecture, Part 5 User Needs And Services for various groupings of Market Packages; list all other market packages applicable.


Refer to the latest revision of the New Jersey Statewide ITS Architecture, Part 4 ITS Inventory Statistics for all other possible subsystems; list all other subsystems (or ITS elements) mapped to the statewide architecture.

Architecture Flow:

Refer to the latest revision of the New Jersey Statewide ITS Architecture, Subpart 5.2.3 Technical Approach, for information exchange at the architecture flow level; then refer to the various flow diagrams included in Part 6 Operational Concepts and Agreements; summarize other flow of information based on the project’s stakeholder agreements and concept of operations.




Example clauses to be used for Device Specific requirements.  Designers must coordinate with the respective Traffic Operations Center to define the requirements.  Ensure it addresses ITS work that may be outside the physical limits of the overall project improvement.


Install a DMS on I-80 EB to alert motorists prior to the I-280 interchange to divert traffic to other available routes for delays ahead, and provide travel times for the common destination of the George Washington Bridge to allow motorists to determine travel impacts and potential rerouting. 

DMS – designer to describe not the specific MP location, but the purpose.  


Install CCTV to monitor traffic conditions in the vicinity of the interchange between I-80 and Route 206. Video coverage should provide for at least ½ mile along each approach on I-80 and to the ramp entrances on Route 206.

Install CCTV to monitor the section of I-78 between MP 12 and 14 due to high volumes and roadway geometry.  

CCTV - designer to identify any other specific visual coverage limits.













File: S/TO/OITS/ITSEngineering/DesignManual/ SERF FILL-IN PROGRAMMATIC - v102809.doc