Amendment 0003 6913G621R200004.pdf

(x)

6913G621R200004 x x copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted ; or (c) By separate letter or electronic communication which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGEMENT TO BE

RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR

OFFER. If by virtue of this amendment you desire to change an offer already submitted , such change may be made by letter or electronic communication, provided each letter or electronic communication makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

x

6913G6

Cambridge MA 02142-1001 55 Broadway

VOLPE NAT'L TRANSPORTATION SYS CNTR

04/11/20210003

13. THIS ITEM ONLY APPLIES TO MODIFICATION OF CONTRACTS/ORDERS. IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

12. ACCOUNTING AND APPROPRIATION DATA (If required) is not extended.is extended, Items 8 and 15, and returning

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended , by one of the following methods: (a) By completing

The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

FACILITY CODE CODE

10B. DATED (SEE ITEM 13)

10A. MODIFICATION OF CONTRACT/ORDER NO.

9B. DATED (SEE ITEM 11)

9A. AMENDMENT OF SOLICITATION NO.

CODE

8. NAME AND ADDRESS OF CONTRACTOR (No., street, county, State and ZIP Code)

7. ADMINISTERED BY (If other than Item 6)CODE 6. ISSUED BY

PAGE OF PAGES

4. REQUISITION/PURCHASE REQ. NO.3. EFFECTIVE DATE2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO. (If applicable)

1. CONTRACT ID CODE

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

02/25/2021

CHECK ONE A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority) appropriation data, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

E. IMPORTANT: Contractor is not is required to sign this document and return __________________ copies to the issuing office.

ORDER NO. IN ITEM 10A.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

The purpose of this amendment is to:

1) The proposal due date is extended to 2:00 PM Eastern Time on Monday April 26, 2021. The

Contracting Officer for this procurement is changed from Jeffrey Welch to Alexander Luker.

Per this amendment, any reference to Jeffrey Welch is replaced with Alexander Luker. Any reference to Jeffrey.P.Welch@dot.gov is replaced with Alexander.Luker@dot.gov. The change in Contracting Officer is not provided in red font in every section. Offeror's are advised of the change per this Amendment 0003. Proposal submissions shall be sent to

Alexander.Luker@dot.gov.

2) Provide updates to Solicitation Sections L.5.2, L.7.2, M.2.2, Attachment J.2 Labor

Continued ...

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)15A. NAME AND TITLE OF SIGNER (Type or print)

15C. DATE SIGNED 16B. UNITED STATES OF AMERICA 15B. CONTRACTOR/OFFEROR 16C. DATE SIGNED

(Signature of person authorized to sign) (Signature of Contracting Officer)

ALEXANDER LUKER

STANDARD FORM 30 (REV. 11/2016)

Prescribed by GSA FAR (48 CFR) 53.243

Previous edition unusable

Except as provided herein, all terms and conditions of the document referenced in Item 9 A or 10A, as heretofore changed, remains unchanged and in full force and effect .

ITEM NO. SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

NAME OF OFFEROR OR CONTRACTOR

2 30

CONTINUATION SHEET

REFERENCE NO. OF DOCUMENT BEING CONTINUED PAGE OF

(A) (B) (C) (D) (E) (F)

6913G621R200004/0003

Category Definitions and Personnel

Qualifications, and Attachment J.6. Updates are provided in red font within the full text of the updated Sections to aid the reader in identifying changes. Changes from previous amendments remain as red font in this amendment. A new Attachment

J.6 is attached separately.

3) Provide responses to questions received.

Please acknowledge receipt of this amendment with the submission of your proposal. All other terms and conditions of the Solicitation remain unchanged.

Period of Performance: 08/01/2021 to 09/30/2025

NSN 7540-01-152-8067 OPTIONAL FORM 336 (4-86)

Sponsored by GSA

FAR (48 CFR) 53.110

Mission Information Technology Support Services Solicitation 6913G621R200004

Amendment 0003

L.5.2 PROPOSAL SUBMISSION INSTRUCTIONS

1) Proposals are due no later than 2:00 PM Eastern Time on Monday April 26, 2021.

2) Proposals shall be submitted electronically to the following email address:

Jeffrey.P.Welch@dot.gov

Alexander.Luker@dot.gov

Receipt of your electronic submittal will be acknowledged via return email. If you do not receive an acknowledgement you are advised, before the due date and time for proposals, to call the CO at 617-494-3552 as firewall protections may block emails and/or strip attachments.

3) Each volume of the proposal shall be submitted as a separate document (Microsoft Office 2016 compatible format). Offerors shall ensure that their subcontractors also follow the proposal submission instructions.

4) Prices and dollar values shall be stated only in the Cost and Business Proposal (Volume I) and shall be omitted from the Technical Proposal (Volume II) and Oral Presentation Slides (Volume

III).

L.7.2. TECHNICAL PROPOSAL CONTENT

The Offeror’s Technical Proposal (Volume II) shall consist of the following four sections:

SECTION 1 – FACTOR 1 – TECHNICAL UNDERSTANDING AND APPROACH

The Offeror shall provide its technical understanding and approach for the requirements outlined in the SOW; in particular, advanced technical skills and expertise in transportation system analysis, systems engineering, information technology, integration, research, and analysis applicable to transportation systems projects as it relates to the five task areas identified in Section C, as demonstrated by the effectiveness of the Offeror’s written response. The Section C five task areas are:

• Technology Assessments and Modernization

• System Analysis, Development, Deployment, Field Support, and Analytical Research

Analysis

• System Architectures and Framework

• Lab Facility and Operations Support

• MITS Management and Administrative Support Services

SECTION 2 – FACTOR 2 – STAFFING AND MANAGEMENT APPROACH

The Offeror shall provide the approach for its management and administration team, structure, and their roles and responsibilities to perform the requirements identified in Section C.2.5 MITS Management and Administrative Support of the solicitation. Specifically the Offeror’s staffing and management approach for the contract, task orders, and financial and administrative management to achieve technical excellence mailto:Jeffrey.P.Welch@dot.gov mailto:Alexander.Luker@dot.gov on Volpe Center projects through high quality, on time, and within budget deliverables; capability to recruit, employ, and maintain appropriately skilled resources, the Offeror’s Quality Assurance Surveillance Plan to ensure corrective actions are taken when necessary; its approach to managing and forming project teams to satisfy technical requirements as task orders arise; and its approach to project management.

The Offeror’s staffing plan will include LOE of the Prime Contractor, proposed subcontractors, and individuals for accomplishing the contract requirements, including the Offeror’s organizational matrix chart mapping functions identified in the SOW to specific management staff and lines of communication.

The Offeror shall provide resumes for Key Personnel. In addition to Key Personnel resumes, the Offeror shall provide resumes for two Project Managers, two Subject Matter Experts, one Senior General Engineer, one Senior IT Engineer, and one Senior Application Developer. The Offerors will be evaluated based on the depth and breadth of the proposed Key Personnel proposed resumes in terms of management and technical expertise, experience, and education relevant to performing the requirements of the contract.

NOTE FOR FACTOR 2, THE FOLLOWING SHALL APPLY:

The Offeror’s resume submission must be accompanied by a commitment/resume validity letter for all proposed resumes. At a minimum, the resume must include a statement regarding the veracity of the information provided in the by the individual, with signature and date. The letter must include commitment from the individual to perform the work (as required) for the duration of the base period of performance, as established in the SOW. Each letter must be individually signed and dated by the proposed person.

SECTION 3 – FACTOR 3 – TRANSITION (First Task Order)

In this section the Offeror shall provide a Transition Plan that includes the following:

• Resume of the Proposed Transition Manager;

• Approach to meet the requirements described in Section C.4 of the SOW;

• Understanding of current workload, status of ongoing projects, and milestones;

• Management organization, authorities, and lines of reporting during the transition from the incumbent contractor to the successor;

• Approach for coordination with the Volpe Center;

• Description of the transition tasks to be performed;

• Communication strategy with key stakeholders (e.g., incumbent contractor management and staff, and key Government personnel);

• Transition Schedule that identifies the estimated 50 tasks orders to be performed efficiently, accurately, and in a timely manner; and

• Risk mitigation during the execution of sub tasks including minimizing disruption to ongoing tasks, plan for mitigating any potential project disruptions, and staffing plan, if necessary, including retention of percentage of incumbent staff for continuity.

SECTION 4 – FACTOR 4 – CONTRACTOR PAST PERFORMANCE

The Offeror shall submit its past performance information for both the Offeror and each of its major proposed subcontractors that individually represent over 20 percent of the estimated LOE.

Each Offeror will be evaluated on its performance under existing and prior contracts for similar products or services. Performance information will be used both for responsibility determinations and as an evaluation factor. References other than those provided by the Offeror may be contacted by the Government and the information received may be used in the evaluation of the Offeror’s past performance.

The Offeror must provide a list of the five most relevant contracts that it and/or its major proposed subcontractors that represent over 20 percent of the hours in the Cost and Business Proposal are currently performing or have completed for the Federal Government within the past 3 years with a value over $1,000,000. The list should include the involvement of the proposed Key Personnel. Although past performance information from Federal Government sources is desirable, the agency encourages past performance information from any source, including those from State and Local Governments. The Offeror must select the five contracts that it considers the most relevant in demonstrating its ability to perform the proposed effort. The Government will accept past performance for contracts with a value less than $1,000,000 if the Offeror considers the contracts relevant in demonstrating its ability to perform the proposed effort. If the list includes Federal Government contracts in which the Offeror served as a subcontractor, it is the Offeror’s responsibility to obtain all information regarding the Offeror’s performance.

If the Offeror can demonstrate that including information on its five most relevant contracts with the Federal Government over $1,000,000 would create an undue burden on the Offeror, then the list may be reduced to reflect contracts for which data is readily available. The Offeror must describe in its proposal what types of contracts were excluded and what process was utilized to ensure that the most relevant contracts with the Federal Government over $1,000,000 relevant to the SOW were included.

The Offeror’s list of five most relevant contracts must include the following information for each contract:

1. Name and address of customer

2. Contract number

3. Contract type

4. Total contract value

5. Description of contract work

6. CO’s address, telephone number and email address

7. ACO’s address, telephone number and email address (if different from item 6)

8. COR’s address, telephone number and email address

9. List of major subcontractors

10. Assessment of relevance to requirements identified in this solicitation.

11. Whether any final or interim contract past performance report was or has been issued by the contracting agency. Copies of the final or most current past performance report must be submitted for the most relevant contracts as cited by the Offeror. Copies of reports on other than these contracts considered most relevant by the Offeror should not be submitted as part of the proposal but may be obtained by the Government if the Government considers the contracts relevant.

In submitting relevant past performance information, Offerors may include information on problems encountered on the five identified contracts and the Offeror’s corrective actions. The Offeror may include information regarding predecessor companies, proposed personnel who have relevant experience, or subcontractors that will perform major or critical aspects of the requirements such that information is relevant to this acquisition. In the case of a relatively new firm (i.e., established within the last 18 months), the Offeror may submit past performance information for contracts on which its corporate management has performed to supplement any past performance information for the firm itself; this shall be specifically noted in the proposal submission.

The Offeror is responsible for making all reasonable efforts to ensure that a completed evaluation report is provided for each of the five cited contracts by no later than the due date for receipt of proposals. If the contracting activity has completed a contractor evaluation report and provided a copy to the Offeror, particularly those completed in accordance with Subpart 42.15 of the FAR, a copy of this report is sufficient. The Volpe Center uses the Contractor Performance Assessment Reporting System (CPARS) as its primary method for entering past performance information. The Volpe Center can obtain completed past performance evaluations via CPARS. However, the Offeror is responsible for making all reasonable efforts to ensure that copies of the performance evaluation reports (including those found in CPARS) are provided directly to the Volpe Center CO by the appropriate contracting activity's responding official by no later than the due date for receipt of proposals. If the contracting activity has not developed its own past performance evaluation report form, please refer that contracting activity to the Contractor Performance Report format found at the CPARS website. This format, including the associated numeric ratings and criteria, should be used to submit the required past performance information for the proposal. Information contained in the evaluation reports is considered sensitive and will not be released to other Offerors. Failure of the Offeror to demonstrate that it has made all reasonable efforts to provide the required past performance reports may result in an unacceptable rating for this factor.

The Government reserves the right to obtain additional information from any of the referenced contract contacts and from other Government sources. If the Government receives negative past performance information (indicating that performance was less than satisfactory) that is not accompanied by a response from the Offeror, a copy of the adverse information will be provided to the Offeror; and the Offeror will be given a limited period in which to provide a response. If no response is received within the specified timeframe, the negative past performance information will be evaluated as submitted.

If the Offeror has no relevant past performance history or less than the required 5 evaluations, it must affirmatively so state in its proposal. Offerors that state they have no relevant past performance history or less than 5 evaluations and Offerors that are unable to provide past performance reports after http://www.cpars.gov/ making all reasonable efforts will not be evaluated favorably or unfavorably under this criteria in accordance with FAR 15.305. If the Offeror does not include past performance history or does not affirmatively state that no past performance history exists or can be obtained, this factor may be rated as Unacceptable.

It is the responsibility of the Offeror to provide the past performance evaluation reports found in CPARS.

If the Offeror is unable to access CPARS, the Offeror must notify the CO by e-mail at Jeffrey.P.Welch@dot.gov no later than 20 calendar days before the proposal due date.

In the event that a Federal Government reference has not completed an evaluation using CPARS, Offerors can send a Past Performance Questionnaire (Section J Attachment J.7) to those references listed in the five most relevant sources to assist in the timely processing of past performance evaluations. Offerors are responsible for ensuring that Past Performance Questionnaires are completed and returned to the Volpe Center CO by the proposal due date. Completed Past Performance Questionnaires submitted by Offerors will not be accepted for evaluation.

VOLUME III - ORAL PRESENTATION SLIDES

Volume III shall consist of Microsoft PowerPoint slides the Offeror intends to present during its structured oral presentation. Volume III shall include three separate sections: Technical Understanding and Approach; Staffing and Management Approach; and Transition.

Offerors may not change their presentation slides after submission. The Technical Evaluation Team will not be provided with copies of the presentation slides until immediately before each oral presentation.

The purpose of this restriction is to assure Offerors of the fairness and integrity of the oral presentation process.

Slides are intended to aid material presented orally during oral presentations. Accordingly, any material submitted on an oral presentation slide not covered during the oral presentations will not be considered in the evaluation of proposals. If any material on the oral presentation slides conflicts with material presented orally during the oral presentation, the government will consider the material presented orally, not the conflicting material on the slide(s).

The structured oral presentation shall not encompass proposed price, cost, fee, or profit. Oral presentations shall not constitute discussions. All presentations shall begin with the introduction of presenters and other members of the Offeror’s team by name, proposed position, and company affiliation.

Oral presentations will be conducted using Microsoft Teams and the presenter(s) should be prepared to have their cameras turned on and share their screen in order to present and display the slides.

TECHNICAL UNDERSTANDING AND APPROACH

In order to allow a complete evaluation of the Offeror’s technical understanding and approach of each functional area capability under the master contract, the Offeror will have 15 uninterrupted minutes to demonstrate that it has the necessary expertise, experience, and capability to successfully accomplish the scope of work described in the SOW, and can meet these requirements for both on-site and off-site task orders. The Offeror will be asked to respond to one (1) oral question presented to the Offeror’s team during the oral presentation. Each Offeror’s oral presentation responses will be evaluated in its presentation of its understanding of the factor. Each Offeror will have 20 minutes to respond to the oral question.

mailto:Jeffrey.P.Welch@dot.gov

STAFFING AND MANAGEMENT APPROACH

The Offeror will have 15 uninterrupted minutes to describe its organizational structure, roles and responsibilities, and anticipated level of effort; describe its management and administration team and the capabilities and experience resident within the team to successfully accomplish the requirements of the solicitation. The Offeror will be asked to respond to one (1) oral question presented to the Offeror’s team during the oral presentation. Each Offeror’s oral presentation responses will be evaluated in its presentation of its understanding of the factor. Each Offeror will have 20 minutes to respond to the oral question.

TRANSITION (First Task Order)

In order to allow a complete evaluation of the Offeror's capability to manage the transition from the existing on-site SOFITS Task Order as described in Section C.4, the Offeror shall have 15 uninterrupted minutes to demonstrate its understanding and approach to task order transition. The Offeror shall present its transition plan, describe how it plans to meet the requirements of solicitation, and demonstrate that it has the necessary understanding, expertise, and experience to accomplish a successful transition. The Offeror will be asked to respond to one (1) oral question presented to the Offeror’s team during the oral presentation. Each Offeror’s oral presentation responses will be evaluated in its presentation of its understanding of the factor. Each Offeror will have 20 minutes to respond to the oral question.

Oral Presentation Schedule

The following is a summary of the oral presentation schedule and required presenters:

Evaluation Area Topic Time Limit Presenters 1 Technical

Understanding and Approach Presentation

Presentation on Contract Technical Understanding

15 minutes Proposed Program Manager and one member from management team

Technical Understanding and Approach Question

Technical Understanding and Approach Question

20 minutes Proposed Program Manager and one member from management team

2 Staffing and Management Approach Presentation

Presentation on Task Order Management and Administration

15 minutes Proposed Program Manager and one member from management team

Staffing and Management Approach Question

Staffing and Management Approach Question

20 minutes

Proposed Program Manager and one member from management team

3 Transition Presentation

Presentation on Task Order Transition

15 minutes Proposed Transition Manager

Transition Question Transition Question 20 minutes

Proposed Transition Manager

M.2.2 FACTORS FOR EVALUATION

The following are the technical evaluation factors:

FACTOR 1 - TECHNICAL UNDERSTANDING AND APPROACH (WRITTEN AND ORAL)

Evaluation of the factor is based on the Offeror’s Technical Understanding and Approach to the Government’s requirements outlined in the SOW; in particular, advanced technical skills and expertise in transportation system analysis, systems engineering, information technology, integration, research and analysis applicable to transportation systems projects are needed to as it relates to scope and nature of the five (5) task-areas identified in SOW Section C (specific task-areas identified below), as demonstrated by the effectiveness of the Offeror’s written response. Evaluation of this factor will be based on the Offeror’s description of its technical understanding of each individual task-areas as well as the comprehensive integration of all task-areas.

Each task-area will be evaluated independently and are equally weighted. Evaluation of this factor will be based on the Offeror’s description of its technical understanding and approach of each task-area as well as the interrelated nature of the work. The technical understanding of each task-area will also be addressed during oral presentations. Each Offeror’s oral presentations responses will be evaluated in its presentation of its understanding of the factor and its response to the one (1) oral question presented to the Offeror’s team during the oral presentation.

The five task-areas are:

• Technology Assessments and Modernization

• System Analysis, Development, Deployment, Field Support, and Analytical Research

Analysis

• System Architectures and Framework

• Lab Facility and Operations Support

• MITS Management and Administrative Support Services

FACTOR 2 – STAFFING AND MANAGEMENT APPROACH (WRITTEN AND ORAL)

Evaluation of this factor will be based on the following:

The resumes submitted for Key Personnel and other staff as required by the solicitation. The Offerors will be evaluated based on the depth and breadth of the proposed Key Personnel resumes in terms of management and technical expertise, experience, and education relevant to performing the requirements of the contract.

Offeror’s written responses and oral presentation detailing its Staffing and Management Approach for the contract, associated task orders, and financial and administrative management to achieve technical excellence on Volpe Center projects through high quality, on time, and within budget deliverables;

capability to recruit, employ, and maintain appropriately skilled resources, and utilization of corporate resources to fulfill staffing needs; the Offeror’s Quality Assurance Surveillance Plan to ensure corrective actions are taken when necessary; its approach to managing and forming project teams to satisfy technical requirements as task orders arise; and its approach to project management.

Offeror’s staffing plan will include LOE of the Prime Contractor, proposed subcontractors, and individuals for accomplishing the contract requirements, including the Offeror’s organizational matrix chart mapping functions identified in the SOW to specific management staff. Additionally, the Offeror’s organizational structure chart (including subcontractors) and lines of communication proposed for the work under this contract.

Oral presentation and response to one (1) oral question presented to the Offeror’s team. During oral presentations the Offeror shall describe its organizational structure, roles and responsibilities, and anticipated level of effort; describe its management and administration team and the capabilities and experience resident within the team to successfully accomplish the contract requirements.

ATTACHMENT J.2 - LABOR CATEGORY DEFINITIONS AND PERSONNEL

QUALIFICATIONS

The following labor categories and qualifications depict the types of personnel that will typically be required in support of MITS Task Orders.

Experience is considered qualifying when it is progressively responsible; is in areas directly related to the functions and level of the labor category; and clearly provides the candidate with the ability to successfully perform the duties of the position after a normal orientation period.

Education is considered qualifying when it is obtained from an institution appropriately accredited by an organization recognized by the Secretary, U.S. Department of Education.

Transition Manager

Functions:

The Transition Manager shall have the authority to act upon the Government’s requirements, and accomplish all work necessary to successfully facilitate contract transition. The Transition Manager must possess experience to successfully lead transition efforts on large-scale professional support services programs.

Requirements:

Transition Manager: Master’s degree from an accredited school in any business-related subject area or a field related to the MITS Statement of Work (SOW) and a minimum of 15 five years of experience successfully leading transition efforts on large-scale professional support services programs; or

Bachelor’s degree from an accredited school in any business-related subject area or a field related to the MITS Statement of Work (SOW) and a minimum of seven years of experience successfully leading transition efforts on large-scale professional support services programs; or

Ten years of experience successfully leading transition efforts on large-scale professional support services programs.

Contract Program Manager

Functions:

The Contract Program Manager is the Contractor principle point of contact and shall be responsible for the overall management of the technical and business worked performed. The Contract Program Manager shall ensure quality of work, and that work is completed on schedule and within the allocated budget. The Contract Program Manager will be responsible for the overall performance of the contract and allocation of resources amongst tasks.

Requirements:

Contract Program Manager: Master’s degree from an accredited school in any business-related subject area or a field related to the Statement of Work and a minimum of 15 ten years Program Management experience involving transportation systems programs, including working knowledge of applicable federal, state, and local laws, regulations, and guidance involving transportation systems and functions issues; or

Bachelor’s degree from an accredited school in any business-related subject area or a field related to the Statement of Work and a minimum of twelve years Program Management experience involving transportation systems programs, including working knowledge of applicable federal, state, and local laws, regulations, and guidance involving transportation systems and functions issues; or

Fifteen years Program Management experience involving transportation systems programs, including working knowledge of applicable federal, state, and local laws, regulations, and guidance involving transportation systems and functions issues

Project Manager

The Project Manager performs project management for a combination of a few very large projects to several small projects supporting transportation systems. The Project Manager is responsible for the overall project management, and for ensuring that the technical solutions and schedule are implemented in a timely fashion.

From an administrative perspective, the Project Manager works with the Volpe Center to plan, organize, staff, direct, manage, and report the work performance of the Contractor staff to ensure that schedules, staffing, and budgets are appropriately managed to accomplish project objectives. This includes defining suitable performance measures, quality standards, security requirements, and configuration management requirements; identifying and mitigating project risks; and providing support for evaluating project cost and schedule progress.

From a technical perspective, the Project Manager has a strong knowledge of and experience in the principles and activities related to the development and support of transportation systems. This includes knowledge of and ability to implement and manage Federal standards and other guidelines related to the development of secure systems (facility, network, data) and Section 508 compliant systems. The Project Manager is responsible for providing technical and subject matter guidance to project staff, including (but not limited to) monitoring the technical suitability of the methods, tools, and techniques applied in work performance; the technical quality of work performed; and the quality of IT products delivered. The Project Manager has sufficient experience in the development and support of transportation systems to provide subject matter and technical guidance for strategic planning, requirement and data analysis, operational concept development, software and hardware design and integration, database design, development, testing, and deployment efforts. The Project Manager has experience to provide direction in specifying, recommending, and selecting technology architectures suitable for the successful development and support of transportation systems.

Requirements:

Project Manager: Master’s degree and a minimum of ten years of experience with IT development and support.

At least three (of the ten) years of experience must be as a project manager on a system analysis project or major hardware or software design and development program. Qualifying experience must include a minimum of five years of intensive training/experience in an IT area related to work described in the MITS SOW; or

Bachelor’s degree and a minimum of twelve years of experience with IT development and support. At least five (of the twelve) years of experience must be as a project manager on a system analysis project or major hardware or software design and development program. Qualifying experience must include a minimum of seven years of intensive training/experience in an IT area related to work described in the MITS SOW; or

No Degree and a minimum of Fifteen years of experience with IT development and support. At least eight (of the fifteen) years of experience must be as a project manager on a system analysis project or major hardware or software design and development program. Qualifying experience must include a minimum of ten years of intensive training/experience in an IT area related to work described in the MITS SOW.

It is strongly recommended that Project Managers possess and maintain currency with professional Project Management Professional (PMP) certification or equivalent professional certification. as provided thru the Project Management Institute. Managers may be required to possess security level clearances under some task orders.

Subject Matter Expert

The Subject Matter Expert is recognized for strong expertise in subject matter issues (e.g., transportation systems, systems security, communications, emerging and applied technologies) and for understanding, communicating, and implementing common best practices related to their area of expertise. The Subject Matter Expert works with managers and project staff to identify issues and to provide vision and strategic direction as required.

For strategic planning, system framework, and concept development, the Subject Matter Expert has demonstrated expertise with transportation systems and with IT to assess the operational and functional baseline of the sponsor’s organization, and help to define a new direction and strategy. The Subject Matter Expert may influence the determination of IT requirements that affect the sponsor’s ability to support/meet transportation systems goals, and generate functional area strategies for enhanced transportation systems and IT operations and support.

Subject Matter Experts identified for the systems/software development life cycle (SDLC) activities area are recognized for business and/or architectural expertise in adapting transportation systems functional business requirements and processes into technical solutions based on an understanding of the overall enterprise architecture and environment. The SDLC Subject Matter Expert provides insight into IT and technologies that sets the direction and establish an approach for technical solutions and has the expertise needed to perform and resolve functional, system, and architectural gap analyses. The SDLC Subject Matter Expert is current in technology and industry trends that affect transportation enterprise solution sets, including technical platforms and network architectures. The SDLC Subject Matter Expert may lead technical design reviews, validate enterprise approaches, define application systems that support redesigned or improved business processes, recommend technical architectures that lead to comprehensive business solutions, and assess work products. The SDLC Subject Matter Expert has knowledge of and is able to apply Federal standards and other guidelines related to the development of secure systems and Section 508 compliant systems. It is strongly recommended that the SDLC Subject Matter Expert possess training or experience operating at Capability Maturity Model Integration (CMMI) Maturity Level 2 3 or higher; or equivalent as provided thru the CMMI Institute.

Subject Matter Experts identified for the specialized technology activities area are recognized for expertise in at least one technology or scientific domain including, but not limited to, blockchain, artificial intelligence, machine learning, natural language processing, geographic information systems (GIS), safety management systems (SMS), system safety, transportation logistics and data science. The Technology Subject Matter Expert provides insights into applying emerging and specialized technologies to transportation experiments, research and analysis. The Technology Subject Matter Expert has knowledge of and is able to apply Federal standards and other guidelines related to the use of specialized technologies and scientific fields within Federal IT environments.

Subject Matter Experts in the information technology security area demonstrate strong experience in supporting Information Systems Security (ISS) activities in the Federal Government sector in both classified and non-classified environments. ISS Subject Matter Experts demonstrate knowledge of and experience in the application of Federal ISS regulations and guidelines related to the development of secure systems (e.g., facility, network, data). ISS Subject Matter Experts have demonstrated abilities to perform an analysis and evaluation of IT facilities and/or software applications, subsystem and components to identify security risks. IT applications may include Government and commercial common user systems, as well as dedicated special purpose systems requiring specialized security features and procedures.

Requirements:

Subject Matter Expert: Master’s degree and a minimum of ten years of experience with subject matter (e.g., transportation systems, IT, security) of expertise. At least three of the most recent five ten years of experience must be focused in one area to demonstrate expertise (e.g., three of the last five ten years of experience focused in the security area; three of the last five ten years focused in senior-level SDLC activities as network architecture;

three of the last five ten years focused in strategic planning, system framework, and concept development for air transportation systems; three of the last five ten years focused in strategic planning, system framework, and concept development for transportation systems at least one mode of transportation). Subject Matter Experts may be required to possess security level clearances in support of task orders. Subject Matter Experts also may be required to possess professional certification relevant to their field of expertise such as PMP. ; or

Bachelor’s degree and a minimum of twelve years of subject matter experience as described above; or

Fifteen years of subject matter experience as described above.

General Engineer

The general engineer provides engineering advice, guidance, and assistance to program offices or site managers on the interpretation and application of technical requirements and policies, execution of priorities and schedules, implementation of data exchanges and standardization, evaluation of significant modifications and/or alternative approaches, and initiation of revisions or corrective actions as required. The general engineer will apply accepted and emerging analytical approaches to perform complex statistical analysis and conduct tests to determine technical feasibility, commercial viability, operational applicability, and cost effectiveness of improved and new equipment and systems. The general engineer will articulate information through methods such as: fact sheets, project reports, design documentation, discussions, meetings, and briefings or presentations to the project team.

The general engineer will apply technologies and develop and assess their impact on programs for upgrading the performance (e.g. safety, capacity, efficiency, emissions, and resiliency) of a variety of transportation products, infrastructure, fuels, operations, and systems. Areas of work may involve: connected and automated vehicle research, hardware/software/network architectures for transportation and safety systems, software development for cybersecurity/building policies, aviation or maritime systems engineering, applied mechanics, finite element analysis techniques, energy use reduction, fire safety/code compliance, occupational safety, transportation infrastructure improvements, automobile/rail crash-worthiness tests and simulation, or highway/transportation engineering (design, construction, materials, survey and mapping, and asset management).

Requirements:

Senior: Master’s degree and a minimum of ten years of engineering experience involving general or specialized engineering tasks. Experience must include a minimum of five years of successful demonstration of skills in one or more relevant engineering functional areas such as systems engineering, aeronautical engineering, mechanical engineering, electrical engineering; or

Bachelor’s degree and minimum of twelve years of engineering experience involving general or specialized engineering tasks. Experience must include a minimum of seven years of successful demonstration of skills in one or more relevant engineering functional areas such as systems engineering, aeronautical engineering, mechanical engineering, electrical engineering.

Senior Engineers will demonstrate responsibility for successfully executing engineering tasks independently with no required technical supervision.

Mid-Level: Bachelor's degree and a minimum of five six years of engineering experience involving general or specialized engineering tasks. Experience must include a minimum of three years of successful demonstration of skills in one or more relevant engineering functional areas such as systems engineering, aeronautical engineering, mechanical engineering, electrical engineering.

Mid-Level Engineers will demonstrate responsibility for successfully executing engineering tasks independently with little required technical supervision from Senior staff.

Junior: Bachelor’s degree and a minimum of two one years of engineering experience involving general or specialized engineering tasks. Experience must include a minimum of one year of successful demonstration of skills in one or more relevant engineering functional areas such as systems engineering, aeronautical engineering, mechanical engineering, electrical engineering.

Junior Engineers will demonstrate responsibility for performing engineering tasks with some technical supervision by Senior and Mid-Level staff.

IT Engineer

IT Engineer: The IT Engineer demonstrates technical competence and experience in the design, development, and implementation of IT hardware, software, and network infrastructures across multiple platforms and systems. The IT Engineer applies systems engineering principles to investigate, analyze, plan, design, develop, implement, test, and/or evaluate computer systems and to develop documentation to support system engineering and technical analyses, reports, change proposals, and other technical areas.

To varying degrees based on experience, the IT Engineer demonstrates the ability to analyze operational requirements and technical system requirements, conduct design reviews, design and develop large-scale components or subsystems, coordinate the efforts of technical support staff, and apply system engineering experience to perform functions such as system integration, configuration management, quality assurance, and testing. The IT Engineer also may be experienced in the review of literature, patents, and current practices relevant to the solution of assigned projects and may be experienced in collaborating with other technical personnel on feasibility studies and systems planning. The IT Engineer has knowledge of and ability to apply Federal standards and other guidelines related to the development of secure systems and Section 508 compliant systems.

IT Engineers in the data management area have experience in applying an enterprise-wide approach to managing, planning, analyzing, designing, developing and supporting IT systems. This experience includes performing enterprise-wide systems planning, business information planning, and business data analysis; performing process and data modeling using both manual and automated tools; applying reverse engineering and re-engineering disciplines to develop migration planning documents, and coordinating planned system and implementation activities.

IT Engineers in the network and communications area are experienced in engineering computer systems and networks, varying in size from large complex computer systems and/or networks to relatively small systems.

Network IT Engineers apply computer-engineering principles to the design of hardware, operating systems, networks, and processes to solve technical problems. Systems may involve multiple protocols and interfaces, satellite communications, digital or fiber optic networks. Experience in this area includes planning designs or re-designs of existing systems or networks; testing and analyzing network elements (including software, communications devices, lines, modems, terminals, power); ensuring the overall integration of the enterprise network; monitoring and controlling the performance and status of the network resources; identifying and diagnosing highly complex problems and factors affecting network performance; and providing guidance and direction to network support technicians.

IT Engineers in the Software Systems (SS) area develop and apply state-of-the-art methods, theories, and research techniques to the design, development and support of hardware and software for transportation systems, ranging from simple systems to large, complex systems operating across multiple platforms. They have experience to plan, organize, conduct, and direct major projects or phases of projects, based on an assessment of the enterprise architecture and its constraints, and may be called upon to resolve advanced and complex technical problems.

They have experience with the identification, selection and application of new concepts and approaches, definition of complex design specifications, development of major routines and utility programs, and resolution of difficult hardware/software compatibility problems. They also have demonstrated experience in the design, development, maintenance, and analysis of databases, and/or experience with object-oriented programming, new/advanced programming languages, and integrated automation systems.

IT Engineers in the system engineering area operate, supervise, and manage the daily operation, security, and performance of information systems, including (but not limited to) networks, communication systems, databases, web servers, firewalls, and other technologies that require ongoing management. The IT Engineers in the system engineering area demonstrate experience in a range of system administration functional areas, including applying security and update patches and other preventive maintenance; monitoring system performance; performing system performance tuning and trouble-shooting; optimizing system operation and resource utilization; performing system capacity analysis and planning; monitoring event and security logs; ensuring system integrity through regular back-ups, fail-safe, and recovery operations based on standard operating procedures; verifying that systems are in compliance with applicable IT security policies, procedures and guidelines; allocating and managing user accounts and privileges; and operating call logs and/or customer support functions. These IT system engineers should be conversant with and able to apply Federal standards and other guidelines related to the development or operation of secure systems.

Requirements:

Senior: Master’s degree and a minimum of ten nine years of experience with IT engineering, at least five three years of which must reflect extensive and in-depth experience in a technical sub- category of hardware, software, network, or database technology; or

Bachelor’s degree and a minimum of eleven years of experience with IT engineering, at least five years of which must reflect extensive and in-depth experience in a technical sub- category of hardware, software, network, or database technology; or

- a minimum of Fifteen years of experience with IT engineering, at least five years of which must reflect extensive and in-depth experience in a technical sub- category of hardware, software, network, or database technology.

The Senior IT Engineer must demonstrate experience serving as a as a team leader on a system analysis project or major hardware or software design and development program. The Senior IT Engineer must demonstrate experience as a technical resource for mid-level and junior IT Engineers. Senior IT Engineers also may be required to possess professional certifications.

Mid-Level: Bachelor's degree and a minimum of five years of experience in IT engineering, at least three years of which must reflect extensive and in-depth experience in a technical subcategory of hardware, software, network, or database technology; or a minimum of Eight years of experience in IT engineering, at least six years of which must reflect extensive and in-depth experience in a technical subcategory of hardware, software, network, or database technology.

Mid-Level IT Engineer experience demonstrates full responsibility for planning, organizing, and conducting project tasks with minimal direct supervision required by Senior staff.

Junior: Bachelor's degree and a minimum of two zero years of experience in IT engineering and no years of experience; or a minimum of Five years of experience in IT engineering, at least one year of which must reflect extensive and in-depth experience in a technical subcategory of hardware, software, network, or database technology.

Junior IT Engineers will demonstrate some responsibility for planning, organizing, and conducting project tasks under the supervision of Senior and Mid-Level IT Engineer staff.

Application Developer

The application developer performs…